Skip to main content

Allview Speed City/Onda 701 touch screen replacement

After about a year of use (and some hard drops) the touchscreen in my Allview Speed City tablet (Onda 701 clone) stopped working in a 1/3 region of the screen. I could still use the tablet by rotating it when I needed to tap in the broken area, but I needed to replace the touchscreen.

I got a replacement touchscreen from here: http://www.gsmnet.ro/touchscreen-uri-telefoane/touchscreen-allview-alldro-speed-city-original--81391 for about $30.

I followed the replacement guide in this video: http://www.dailymotion.com/video/x17mxag_touch-screen-replacement-onda-v701-v702-v703-v701s-tablet-disassembly_lifestyle

The disassembly (and reassembly process) took me about 2 hours, but was not very difficult. The first thing to do is to remove the rubber caps on top of the screws in the back of the tablet (use a needle/pincer). You can unscrew the screws (small phillips head).

The tablets back cover is glued on (the screws don't hold it actually). You will need something like a credit card to separate the back cover from the tablet chassis.



Next, you can separate the screen unit from the chassis by inserting the credit card between them (start with a side). The screen detaches quickly once you manage to separate one clip.


At this point I still had the tablet turned on and I could test the connectors (to see if the touchscreen connector was loose). I took out the connector and replaced it with the new touch screen and tried out the new touch screen before removing the old one.

Here are some more images of the tablet's internals:
Mainboard overview

Processor and RAM
Internal storage FLASH chip and screen (left) and touchscreen (right) connectors. In the bottom left you can see some solder points for something that looks like a serial port (haven't tested it).
Top part - camera connection and radios (you can see a Realtek chip)

When you are ready, detach the touchscreen + screen from the mainboard (2 connectors). The touchscreen is glued onto the screen and it will take a while to detach. Use a knife and start at a corner. As you can see, the touchscreen has 2 layers - a transparent plastic on top and an adhesive plastic between the top and the screen. You will need to detach the adhesive plastic completely! It may look like glass, but it's not. You should not be able to cut yourself in it, but take care because it breaks into small shards.

Touchscreen layers. You can see some of the circuitry for the touch sensors
Old touchscreen detached (and broken in the process). Some debris are left on the screen mount.


Once the top comes off you can add the new touchscreen (after you've cleared all the residues from the panel. Before gluing the top on, make some alignment tests - you want the touchscreen to be perfectly aligned on top of the screen. Prior to the attachment make sure to clean both the screen and the back side of the  touchscreen with a cloth to remove any finger marks or debris.


Try out to position and align the touchscreen correctly before removing the white bands

Remove the paper protections on the new touchscreen and glue it on the screen mount. Once it is glued on, connect the ribbon cables back to the motherboard and try it out. If everything is ok, reassemble the tablet (you may need to use some glue to hold the back case in place).

Overall the operation is not difficult to perform. The end result was satisfying, but the replacement touchscreen has some "blind spots" - regions where it doesn't easily register touch events. I could see these spots before when testing the new touchscreen. In terms of alignment I was about 1.5mm off (the touchscreen is about 1.5mm too high), and I have a small open region in the bottom of the tablet. It doesn't impact functionality in any way.

Cosmetic alignment fault (1.5mm off).


Good luck with your replacement!

Comments

Popular posts from this blog

Home Assistant + Android TV = fun

Here's a quick setup guide for controlling your Android TV from within Home Assistant. I've used it to control a genuine Android TV (Philips 7304) and an Odroid N2 running Android TV. For this to work you need ADB access. It can usually be enabled from within Developer Settings. The great part is - you don't need root access! The most important things are described in the androidtv component for Home Assistant: https://www.home-assistant.io/integrations/androidtv/ Make sure you go through the adb setup. My configuration is simple (inside configuration.yaml): media_player:   - platform: androidtv     name: TV Bedroom ATV     host: 192.168.1.61     device_class: androidtv Once Home Assistant restarts, your TV might require you to accept the connection (adb authentication). This happens only once (or until you reset your ATV to factory settings). Once running the integration will show you the current ATV state (on or off) and allows you to turn it on or off.

SmokePing + InfluxDB export + docker + slaves + Grafana = fun

I've been working for a while on this project - with the purpose of getting SmokePing measurements from different hosts (slaves) into InfluxDB so that we can better graph them with Grafana. The slaves run multiple Smokeping instances inside Docker so that they have separate networking (measure through different uplinks, independently). This will not be a comprehensive configuration guide, but a quick "how to" to handle setup and basic troubleshooting. It assumes you already know how to set up and operate a regular Smokeping install with or without slaves and that you are fluent in Smokeping configuration syntax, know your way around Docker and aren't a stranger from InfluxDB and Grafana (sorry, there's a lot of information to take in). 1. Getting Smokeping with InfluxDB support - you can get it either from the official page (most changes have been merged) - https://github.com/oetiker/SmokePing (PR discussion here: https://github.com/oetiker/SmokePing/issues/

Installing Home Assistant Supervised on an old 32bit HP laptop

 I've received a challenge from my former boss: an old HP laptop that was born in 2005:  an HP-Compaq NC6220 ( https://www.pocket-lint.com/laptops/reviews/hp/68181-hp-compaq-nc6220-notebook-laptop/ ). The specs are abysmal: So, i386, 1.7GHz single-core CPU (remember those?), 1G of DDR2 RAM (2x512M) and a 40GB ATA (not SATA!) drive. But hey, at least it has a serial port!  The challenge is to install HomeAssistant ( https://www.home-assistant.io/ ) on it so that he can monitor some Zigbee temperature sensors and relays (via a gateway). The first hurdle was to remove the BIOS password - following this nice guide: https://www.youtube.com/watch?v=ZaGKyb0ntSg Next-up - install HASSOS. Unfortunately, it doesn't support i386, but only x86_64... So, I went the Home Assistant Supervised route, and installed Debian 11 i386 edition from a netinstall USB ( https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-11.6.0-i386-netinst.iso ).   Once Debian was up and running (didn't