Jump to content


Photo

HELP ME PLEASE ( TOUCH SCREEN PROBLEM ) flash issue


  • Please log in to reply
27 replies to this topic

#1 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 13 February 2012 - 10:49 AM

hi i have an allwinner tab similar hardware to ainol novo 7 advanced

i flashed few firmwares on it of different tabs( ployer momo 9 , ly f1) and they were working good

except novo 7 advanced firmwares ( touch was not working at all )

then i flashed a different firmware(onda v140) on it and the screen went white when powered on .
then again i flashed my default firmware everything is working now but touch screen is responding very differently . this is a capacitive touch . i have even tried flashing those firmwares which were working perfectly before but now the problem is common in all firmwares i flash .

see the video



then after that i tried flashing onda firmwares for 7 inch tablet that has auto recalibration of screen function after flash.

the touch points changed from previous one.

now my question is since this is a software/drivers issue how can i get it back


is my tablet bricked ? any chance f bringing it back to life.
rest everything is working fine including camera. and i am able to use adb on pc and run commands easily ..
please help anyone

Edited by rishabh, 18 February 2012 - 06:10 AM.


#2 wa3pnt

wa3pnt

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 37 posts
  • LocationChino Valley, AZ

Posted 14 February 2012 - 12:34 AM

When you flashed the Firmware, did you select the FORMAT option? If not, reflash and select it.

Also, try doing a Factory RESET - After reflashing.

George

#3 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 14 February 2012 - 09:11 AM

i always select format option.
tried doing factory reset also

#4 FezzFest

FezzFest

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 19 February 2012 - 03:05 PM

I need the exact type of your tablet. There's a line in the config file (script.bin) that defines this behaviour.

Edited by FezzFest, 19 February 2012 - 03:07 PM.

  • rishabh likes this

#5 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 20 February 2012 - 09:12 AM

thanks sir for your reply but sorry i did not get you . do you need all information about my tablet ?

allwinner a10 cpu
512 mb ram
capacitive touch
8 gb
android 2.3.4

link for my tablet
http://www.geartaker...d-2-3-tablet-pc


on running command cat /proc/cpuinfo
here is the response

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 1005.97
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : sun4i
Revision : 0000
Serial : 0000000000000000

#6 FezzFest

FezzFest

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 20 February 2012 - 02:43 PM

Flash this ROM and tell me if the touchscreen works correctly. If not, I'll give you another one to try. You are familiar with flashing through LiveSuite?
  • rishabh likes this

#7 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 21 February 2012 - 08:51 AM

no sir the touch did not work correctly with this rom :(

#8 FezzFest

FezzFest

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 24 February 2012 - 09:59 AM

No problem, that's what I expected. Please try this ROM. It is exactly the same, but I reversed the touch points in the config. Tell me if it behaves differently.
  • rishabh likes this

#9 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 24 February 2012 - 12:17 PM

wow , yes sir the touch points got reversed with this rom .

but now how to get the right configuration for touch ? so that it works only where i touch

thank a lot sir for your time and help

#10 FezzFest

FezzFest

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 24 February 2012 - 04:23 PM

but now how to get the right configuration for touch ? so that it works only where i touch


I don't really understand. Touch points are reversed, but it still doesn't work like it should?

#11 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 26 February 2012 - 09:36 AM

yes sir the touchscreen does not work the way it should ,
like i press the right centre of the screen and the touch happens at the bottom left ,
middle part of the screen is not resposive and the capacitive buttons does not work at all

by the way can you tell me how you changed the screen touch points the procedure so that i can at least try to change the touch points as maximum as possible so that the device can be operated thanks

#12 nhwestra

nhwestra

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 31 posts

Posted 26 February 2012 - 09:27 PM

yes sir the touchscreen does not work the way it should ,
like i press the right centre of the screen and the touch happens at the bottom left ,
middle part of the screen is not resposive and the capacitive buttons does not work at all

by the way can you tell me how you changed the screen touch points the procedure so that i can at least try to change the touch points as maximum as possible so that the device can be operated thanks


I have a similar problem. I have N7A. I slid off my desk and hit end on (left side) to the floor 2+ weeks ago. It has been working fine until yesterday.
The top glass has .25 centimeter distortion that looks like a crack in a windshield that WILL NOT splinter. Most things work fine for a few minutes. Then the ADW launcher acts up and wants to know what action I want to take. If go into standby via the power button, then hit the power button again and unlock the slide everything is ok for about 2 minutes then the symptoms repeat. If I use the browser or anything need the keyboard, the p sometimes registers/types q.
I don't know if the digitizer is junk or if I screwed up the screen calibration (if such a thing exits). I reflashed (and formatted) to 2.0 Feiyu mod. No change. I checked for rootkit virus too.....why...I have used non-market games/apps. Nothing found via 3 different AV packages.
just to reiterate...the screen is not broken. The black outer edge about .2 centimeters from the case frame has a distortion that looks like the laminate underneath pulled away.


Can anyone lend a hand to solve this? any informed opinion is greatly appreciated.

#13 varun981

varun981

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 46 posts

Posted 26 March 2012 - 09:28 PM

Hi...I am having the same problem with my MOMO9. It was working all fine until I flashed one of the Custom ROM. I went back to official Android 2.3 and Android 4.0 firmwares. I also did the factory reset. But, there is no improvement in the touch screen. It's still mis-calibrated. Any suggestions?

#14 Wovec

Wovec

    Newbie

  • Jr. Member
  • Pip
  • 6 posts

Posted 16 April 2012 - 10:09 AM

Sorry for the English (translate by Google).
I join with a similar problem that occurs. :(

Analog device: GoClever TAB A73
http://goclever.com/goclever_tab_a73

(Momo9, LY-1, EKEN T01/T02, Bmorn B11, benton BT-M740, teXet TM-7025) - almost similar to the device.

I would be grateful for any help. :)

#15 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 16 April 2012 - 02:42 PM

this occurs when a firmware for ips screen tablet (eg ainol aurora) is flashed on a tablet which does not have ips screen .
Then a white screen appears on the tablet and some thin coloured lines on the tablet divides the tablet vertically into 3 parts
like
! 1 ! 2 ! 3 !
And then if we flash the stock rom again (everything works normally except touch)

The middle part no 2 ( in fig ) is totally not responsive

when we touch in part 1 area the touch happens in part 3 with mirror effect (eg when we swipe from left to right screen moves from right to left horizontally, though vertical orientation is ok) and vice versa i.e
touch in part 3 area touch happens in part 1 area with mirror effect

I HOPE SOMEDAY SOMEONE POST A SOLUTION TO THIS PROBLEM PLEASE

#16 jpcastle

jpcastle

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 95 posts

Posted 16 April 2012 - 03:32 PM

Found this article. it's specifically for the gTab so it probably won't work, but I ran it on mine and it didn't do anything bad so it might be worth a try.

In any case, this thread and all the related threads have some interesting information. From what I can gather, the chip that controls the digitizer has some settings. I'm guessing these settings were messed up for you guys. There may be a way to simulate what was done in these threads, on this tablet.

XDA thread

Another one
ainol NOVO 7 Advanced - ICS 4.0.4 (IVI) CM9

Some people are wise... Some are otherwise.

#17 Wovec

Wovec

    Newbie

  • Jr. Member
  • Pip
  • 6 posts

Posted 17 April 2012 - 02:14 PM

Thank you for your participation.
If there are even any experience in this area - please unsubscribe.
Dig himself too - but to no avail.

PS: Maybe the theme kudato elsewhere to make? (Devices that other little flash + other)

#18 rishabh

rishabh

    Member

  • Jr. Member
  • PipPip
  • 25 posts

Posted 17 April 2012 - 03:35 PM

thanks though i tried again but the recalibration app didnt and wont work because capacitive touch screens are calibrated from factory whearas resistive screen is manually calibrated.
What i think is that the rom for ips screen that we flashed has changed the screen hardware id from non ips to ips screen .
that is why even after flashing stock rom it is detectd as ips screen and it is behaving unusually .
Though I could be wrong also
does anybody here knows anyone who could help us out ?
Thanks

#19 Wovec

Wovec

    Newbie

  • Jr. Member
  • Pip
  • 6 posts

Posted 17 April 2012 - 03:42 PM

An interesting suggestion.
All the same problemma as for me in software - so I think will be the solution.

I have not the English.
Maybe you will make a separate topic. If yes - please provide a link here.

By the way Ainol Novo 7 Advantsed of iron and firmware differs from its predecessors.

#20 Wovec

Wovec

    Newbie

  • Jr. Member
  • Pip
  • 6 posts

Posted 08 May 2012 - 11:47 AM

There is a partial solution. (Post in Russian)
Principle the work is already possible :)

http://4pda.ru/forum...0#entry12972207
  • rishabh likes this