[Q] Archos 80 G9 Turbo motherboard replacement - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Hello! My tablet not boot.
Once in the browser, the screen flashed white and the tablet was able to bootloop. After the logo 'Archos' screen flashes white color and tablet restarts. This occurs in cycles. Term of warranty repair expired. I can go into recovery mode and even download different firmware, but the result is the same - bootloop. I figured that the problem is in the motherboard. i'm found a donor (ARCHOS 80 G9 Turbo) and did transplant motherboard from him. My motherboard revision V2.5 (109376V25), the motherboard donor V2.4 (109376V24). The tablet can boot, but the touch control is not working. The implementation of touch controls on my plate, and the donor is visually different, but I think the functionality has not changed
Please tell me whether there is a difference in the versions of the touch control for different motherboard revision? Or is it my touch control failed ?
My touch control:
http://forum.xda-developers.com/attachment.php?attachmentid=3331847&stc=1&d=1432613829
Donor touch control:
http://forum.xda-developers.com/attachment.php?attachmentid=3331846&stc=1&d=1432613829

Yep, this tablet has different touch screen digitizer chips in different editions of the same model. Try to buy USB OTG cable and turn on Android USB debug in settings using mouse. Then connect your tablet using USB cable (from charger) to your PC. Install android tools and run "adb devices", if your device is there, than run "adb shell". Then you can try to exec "lsmod" there to see which modules are running. You'll find out there your "old" touch screen digitizer driver. Then you can take a look at available touch screen drivers of this model "ls /lib/modules/". You can try to remove old one and load new one (rmmod/insmod) but I haven't tried it yet. I have the same touch screen problem, and haven't tried to root my device yet to check this thing out.
P.S. It looks like you had TR16C0 and Tango F48 chips in your old cover of tablet. And the new one is probably cypress_tma340, but your picture is bad to recognize. Also, touch screen boards are on different plate or cover of tablet with its motherboard. They are connected with ribbon cables to Archos motherboard. Also, have you tried to recalibrate touch screen in Engineer menu (Power button + volume + on start -> Repair -> ...)? If your volume button doesn't work than it means that touch screen cable connection is bad.

Hey, I found the solution to the problem of different touch screen digitizer. Take a look at this file:
adb pull /mnt/rawfs/tags tags.bin
And then give me your tags.bin. Also see this file:
https://github.com/archos-sa/archos...6f53/arch/arm/include/asm/feature_list.h#L224
and this file too:
https://github.com/archos-sa/archos...arch/arm/mach-omap2/board-archos-a80s.c#L1558
Also read this topic on FTAGs.
http://forum.xda-developers.com/showthread.php?t=1711864
Ask if you need any help.

Hi, this problem is solved.
During boot various parameters are initialized, including touchscreen model, namely checks in the service area of the presence of the tag memory "feature_tag_touchscreen" (if (! Tsp || (tsp-> vendor == 0))), if the tag is not found or vendor = 0, then the driver is used for touchscreen "cypress_tma340", otherwise the driver "tr16c0_tsp". My own motherboard was tied to the touchscreen "tr16c0_tsp". Donors motherboard was tied to "cypress_tma340". Because of this, my own touchscreen does not work on the donor's motherboard. In the service area of a memory of donor's mother board had to add the tag "feature_tag_touchscreen" with own touchscreen (tag structure described in "feature_list.h"), to select a correct driver. After reboot touchscreen started working !
I understand that the motherboard has to be tied to their controllers and memory chips, but do not understand why "Archos" did bind to the touch screen, because it is not a component of the motherboard and can be replaced. This greatly complicates the process of replacing. Those who replace the screens and touch panels must know about this.
Thanks to everyone who tried to help and who helped me !

Related

Screen connector differences and rebuilding displays

I have a problem with my XDA2 whereby the 22 pin connector at the bottom of the device has become detached from the main board (after being dropped! outch!)
I have managed to resolder the connector back onto the board, however it appears that a couple of tracks have become detached from the board along with the connector which now means that the serial and usb ports no longer work!! - and there appears to be no way to tell where these pins connect to..
In an attempt to obtain a replacement board i have got hold of a damaged XDA2 from ebay which has a broken screen. However the connector on the board for the screen in this XDA2 is completely different to the one in my XDA2 making it impossible to swap the boards over (or the screens for that matter).
Does anyone know if it is possible to disassemble these displays so that i can produce a display that works with the right connector attached? I know that it's posible to replace the touch screen on these displays but i've no idea how - and i dont want to damage my working display!!
Any help would be apprecated
Rich

htc touch plus digitizer problem

hi
i have a htc touch plus or as they call it htc touch dual.digitizer issue it stoped responding so i bought new one fitted in and still the same problem .i think is a software problem i guess driver software for touch screen .if any one can help please
thanks
Touch Dual digitizer
Hi Saliml2
Not convinced it is a software issue. My digitizer on T-Mobile Touch Plus did the same thing. It stated behaving erratically and then stopped responding altogether. I replaced the digitizer (via eBay) and it work for a few days and then stopped again.
I have read around the internet and have tried several ROM updates etc (currently running a WM 6.5.5 found in other area of this forum) but this has not solved the problem.
It seem to be an alignment issue - i.e. screen alignment is outside the screen area, but there seems to be no way of getting it back. Could be a fault on the phone mainboard (?) but there doesn't seem to be any info around apart from sending it to HTC for repair (not viable as the phone value negates this)
My phone is still not working, I might try opening it up again and reseating the digitizer cable but have done this twice already.
Have you try change the flex cable?
I had one to, with the same problem, and after changing the flex everything was ok...
Good luck!
Hi Amokh Just to clarify, what is the flex cable? The digitizer has a cable already attached to it that plugs in to a zif connector on the mainboard - I assume that this controls the data flow for the digitizer.
Any help would be appreciated.
deepthought2471 said:
Hi Amokh Just to clarify, what is the flex cable? The digitizer has a cable already attached to it that plugs in to a zif connector on the mainboard - I assume that this controls the data flow for the digitizer.
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe this is helpfull http://www.pdacenter.ru/razborka/razbor_htc_touch_dual/
Goodluck
Flex cable, i was mean the cable between the mainboard and the lcd block, you can see it in the previous link, picture 20. Have you try it to change?
hello guys how did you manage to put the digitizer cable in place mine doesn t seem to get in place do i need something to hold the connector in place???

[Q] USB host external touchscreen?

I have a 10 inch touchscreen monitor with a composite input and usb touchscreen. Can the Archos 32 utilize the touchscreen through usb host mode? After I heard the Gen 8 devices support usb host, I started brainstorming an in-car system. My plan was to use my 10 inch touchscreen for the main interface, Archos 32 for the brains, bt or usb gps dongle (do usb gps dongles work?) and maybe some external storage. I would run the audio through my existing stereo.
So, is this at all possible, or am I just pipe-dreaming? I can't seem to find any info on anyone trying an external touchscreen or usb gps dongles.
Nice idea! I think it's all just a matter of time, will and coding power
If you have the time, the will and the coding power you should be able to hack and compile some drivers (if they're not already existing) to support the touchscreen.
check if your touch screen does work with a normal linux computer and verify if the driver is available, open source and included in kernel 2.6.29 or even may be backmergeable from a newer kernel.
The touch drivers will not be the hardest part (Archos do it, so maybe nothin' to do) but for the screen i'm not sure ... the graphics over USB will be hard (i think)
eagleofdeath13 said:
the graphics over USB will be hard (i think)
Click to expand...
Click to collapse
graphics goes over composite! A32IT has a composite output instead of miniHDMI like A101IT. so graphics shouldn't be the problem either
It just so turns out I'm running Ubuntu right now. So you're saying if my touchscreen works normally on my computer, it should be trivial to get working on the A32, maybe even function out of the box?
throughtheblack said:
So you're saying if my touchscreen works normally on my computer, it should be trivial to get working on the A32, maybe even function out of the box?
Click to expand...
Click to collapse
Depending on the kernel version in which the driver for your touch screen was initially included. Archos uses kernel version 2.6.29 (AFAIK, released in march 2009). if it's already included work will be trivial and it may even work out of the box.
Yes, it's possible, maybe not with Android but wit Ubuntu or Debian (modules aren't the same, so if they are in Ubuntu maybe they aren't in Android, the only thing to do is trying ^^)
well, I did a quick test with Ubuntu 11.04. The touchscreen does work (kinda) out of the box. The only problem is that the x and y axis appear to be backwards (left=right, up=down) and the overall calibration seems to be off. It is detected as an eGalax touchscreen, usbtouchscreen module appears to be loaded.
great! ok, documentation of kernel sources which archos made public says:
USB Touchscreen driver for:
- eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
- PanJit TouchSet USB
- 3M MicroTouch USB (EX II series)
- ITM
- some other eTurboTouch
- Gunze AHL61
- DMC TSC-10/25
- IRTOUCHSYSTEMS/UNITOP
- IdealTEK URTC1000
- GoTop Super_Q2/GogoPen/PenPower tablets
Click to expand...
Click to collapse
I've compiled the module for you: download (not tested, I don't have my tablet with me )
This module will only work with the newest Archos firmware! (2.3.26)
1) root your device (see my root thread)
2) unzip the file to your internal storage
3) load the module by terminal:
Code:
$ su
# insmod /mnt/storage/usbtouchscreen.ko
4) connect your touchscreen by usb
5) wait some seconds and then check if it's getting recognized:
Code:
$ dmesg
And for the X/Y problem, i think it's just a Xorg configuration problem ^^
Thanks Chulri! I don't actually own an A32 yet, as I was gaging the likelihood of this working before spending the money. Now with what I've found with Ubuntu and your module, I think I'm gonna try to pick one up this weekend and if I have time, see what happens.
Great! I'm looking forward to your further reports welcome to the archos community
And post pictures of your instalation
Picked up a '32 yesterday. I haven't had much time to play around with it yet, but I must say the touchscreen is impressive for being resistive. Not quite the same as capacitive, but a close approximation.
Anyway, couldn't find a USB host cable or a proper A/V cable. Tried making a USB host cable out of extra cables lying around, no luck. Can't get it to work. Don't know what I'm doing wrong... (ground pin 4 according to what I have read) I bought a cheap A/V cable for an Ipod, since it was the only 3.5mm to RCA A/V cable I could find. Hacked apart an old VCR for it's RCA ports and used it to cobble together an adapter to make this cable work.
I now have functioning video out. The image fit the screen best in PAL Widescreen format, although the cursor turns all blocky in this mode when moved. It also seems a bit flickery. Is this normal? Hopefully it's because of the cobbled adapter situation.
That's about all I had time to do. I'm gonna have to order a proper A/V and USB host cable before I go any further, so that's probably about a 2 week wait.
Update
Good news! I finally got my usb host cable today. A quick test confirmed usb host now working. I used chulri's guide to gain root access, and installed his supplied module. I plugged in the screen. Video is working decent, touchscreen is working... kinda. Similar to when I tried it in Ubuntu, the axis seem to be all messed up (Left = Up, Right = Down, Up = Right, Down = Left). I have no idea how to fix this, so any help is appreciated. Thanks to chulri and everyone else for the help already.
so if you touch the screen in the upper right corner it will recognize the push event in the bottom right corner?
in the end: 90° rotated?
chulri said:
so if you touch the screen in the upper right corner it will recognize the push event in the bottom right corner?
in the end: 90° rotated?
Click to expand...
Click to collapse
Yes, exactly. Also, when I touch the upper portion of the screen, it activates the volume + and -. I guess those buttons are mapped as part of the touchscreen area.
throughtheblack said:
Good news! I finally got my usb host cable today. A quick test confirmed usb host now working. I used chulri's guide to gain root access, and installed his supplied module. I plugged in the screen. Video is working decent, touchscreen is working... kinda. Similar to when I tried it in Ubuntu, the axis seem to be all messed up (Left = Up, Right = Down, Up = Right, Down = Left). I have no idea how to fix this, so any help is appreciated. Thanks to chulri and everyone else for the help already.
Click to expand...
Click to collapse
Bump on this thread. Any progress since? Could you take a video of it working, if you still have the setup. Thanks!
I have firmware 2.4.81 and not 2.3.26. So the module does not work...
what can i do ???
Thanks

[Q] flashing 2.3 on phone with broken USB

i have 2 X10s, one with a broken usb, and one with a broken circuit somewhere that controls the display (no screen using tested working screens).
what i'd like to know.
A is there any known way to cut off the USB part of the PCB and jumper it to another board?
B does anyone know of a fix to a the broken display problem ive described (countless googling found nothing)
C is there a way to exchange the chip holding all the BB and firmware data after flashing with the board with no display?

[Q] Archos 80 g9 Touch Screen Issues

Hi
I'm hoping someone can help me. I have an Archos 80 G9 given to me as it wasnt charging, the connector had come off the board but I have re soldered it back and now charges fine.
However whilst I had the tablet was apart the touch screen no longer works, (whether a connector is broke or not I am unsure.) I am hoping someone has a picture of how the inside is supposed to look like or take a picture then I can begin the process of elimination.
Many Thanks
Hi,
I had a similar problem with an Archos, it turned out the screen just needed to be configured again
Hold power and volume up on boot till the white screen
Repair system
Force touch screen calibration
---------------
If this doesn't work check your connection on the two ribbons connected to te motherboard that is the only two connectors from screen to the board, the other two white and black wires are power and signal for wireless.
Good luck

Categories

Resources