Related
Can anyone help me please !
I've got some problems with my touchscreen.
So.. it works perfectly but time after time (approx. 2-3 hours) the touchscreen adjust itself! This means, when I touch the mini keyboard for a word (e.g. "e") the "r" is highlighted! For a better view I took ScummVM to watch with the cross and it seems to me, like there is a failure in the touchscreen!
Has anybody the same problem?
How can I fix it ?!?!?
I send it back where I bought it, but the result is the same as before!
Thanks!!!
Hi mt2002,
Does re-aligning your screen (settings->system->screen) help, or does this only lasts for a few hours too?
Think you've got to send it back again, they didn't solve your problem in the first place and this feels to me like a warranty issue.
I have the same problem, and I cannot fix it, too.
by Avers
Touch screen issues
Yeh had the same issue. Just seems ot be fairly randomm for me.
Hi, same problem here. I tested with a hard reset, another Rom flashing and instaling and desinstalling programs. The best thing I discover is that software like batti (add a line in the top of the screen with battery %) and vbar (task manager) accelerate the alignment problems.
I had ROM 1.11 and now 1.12 (no 1.13 in spanish language) and know I have less problems than before.
Another thing I realized is that the dealignment is not the same in all the screen: sometimes is ok in the upper part and a little bad on the bottom one and sometimes is the other way.
Anyway now I can work with it with no more than 2 realigments a day, depending on the use.
Hasta luego!
I am facing the same problem. Reinstalled the OS with version 1.11, and then 1.12 but both doesn't help.
After hard reset or reinstallation, the screen is ok for a while. But then disalignment happens. Re-aligning works for a while, and then sucks.
I think there is a problem with the hardware, not the softwares.
Do you think?
Try pressing on the back of the unit with your other hand,
(Holding edges with thumb and other fingers and pressing your first finger on the back)
While using the screen.
Also try making a new note and just drawing a grid pattern (Like a huge tic-tac-toe board)
many of us having the same problem. i was using android nand rom for last two monts, everything was perfect. I did a screen replacement last week, and after that 'g sensor' is not working with android. not pnly g sensor, also proximity sensor and magneto sensor. but the thing is, every sensor is working with winmo 6.5, even with wp7.
i have tried several build, changed hspl...nothing worked. many of us are having the same problem.
all you brilliant people, someone help us man.
This seems to be a general problem After a screen replacement the G-Sensor in Android stops working.
Can anyone can tell us how we can fix this, i.e. what info can we supply to the ROM chefs and kernel gods to help them get to the bottom of this?
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
Dont know if this helps...but I had my Hd2 screen replaced few months back...and dont have this problem... screen is much better than before though with beter colour saturation....check with HTC as this might be an error on their part..
Sent from my HTC HD2 using XDA App
G-Sensor Not Working after Screen Replacement
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
I have this same problem with one of my HD2's that had the screen replaced.. Everything works perfectly except the "G-Sensor"...
I posted the problem in this thread http://forum.xda-developers.com/showthread.php?t=902129 a while ago, and been watching ever since... Havent seen any solutions, but more reports of the same problem been added to it daily... I'm also assuming that they changed the G-Sensor hardware along with the screen... Beacause it works perfectly in WinMo, and it dont in none of the Android Builds I've tried (CMYLXGOs all versions, Imilka's all versions, RAFDROID, CyanogenMod, etc)...
Everything works good on my Primary HD2, no problems at all... I'm hoping some Chef/Kernel developer might just take some time to check this out...
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
T-Macgnolia said:
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
Click to expand...
Click to collapse
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
cmcmyers said:
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
Click to expand...
Click to collapse
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
T-Macgnolia said:
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
Click to expand...
Click to collapse
It's a good point You have there... But I would be assuming that was the problem if the G-Sensor wasnt working in Windows Mobile... Everything works perfectly in WinMo, including the calibration... Thats another reason we have come to believe its a hardware upgrade or something similar...
I have the same problem. I bought an HD2 from someone in the Marketplace, and I can see from the pry marks on the bezel and the broken adhesive that the screen had been replaced at one point. I also believe there must have been some hardware revision that is still compatible with WinMo, as the same driver works unilaterally, but not with Android. Definitely tried most of the recent ROMs and different combinations of kernels, and cLK/MAGLDR, but it never works.
Charnsingh alludes to the G-Sensor code in the kernel in his [DEV] thread here: http://forum.xda-developers.com/showthread.php?t=1049170 (don't post unless you're a dev though), and says that it's pretty minimalistic. So maybe there's a solution out there, but the developers haven't gotten to the bottom of it. I'm watching that thread intently to see if there's anything cooking or if there's something I can help with.
I think there are quite a few users who are suffering from this.
If the devs need anything they have plenty of people to ask for debug info, etc.
I just wish someone had the time to have a look at this
have got the same issue, new screen, sensors stopped working, all the sensors that is, light, proximity, g-sensor, compass. and everything works in winmo (except the compass, don't know why) the interesting thing is, the proximity sensor does work, it just doesn't turn off the screen, but it does turn off the touch screen, and the g-sensor actually seems to work, i can calibrate, and the relevant files are updated (in /data/misc the bma150_usr and the akmd files are created and/or updated) and if i move during calibration, it is aborted. it seems as if there is something broken in software because the chip data is still being read and used somehow, just not piped to the right places...
Every sensor work fine here with except the g sensor
I guess its a kernel issue and not hardware relates
it work perfectly on wm6.5,but not work on any andriod rom.
i have the same issue
so no one is helping us???
i have the same issue too...
Same here works fine in windows but android will not work.
Also have screen replacement
SOLVED
my issue is solved now after motherboard replacement.
a few notes:
- as i eventually discovered, there was in fact a problem with the compass (aka the magnetic field sensor) which didn't work in any os. with this issue i had a good reason to send the phone back to the repair shop and they replaced the motherboard under warranty.
- i don't know what solved the issue, it's either [A] the working compass (which is somehow needed for auto-rotation to work - in android) or the new motherboard (which does not have compatibility issues with the new screen - in android).
so, please check wheather your compass is working or not.
if not, reflash to stock and send it back for a warranty repair.
I replaced the digitizer in my phone myself and the G-sensor works for me in Android.
LOOOOOOOOOOOOOOOOOOTS of threads and posts since 6 months and still nothing. About those sensors problems / screen replacements and still nothing... It's so sad, the HD2 is dying slowly. Lolz, let's keep the faith!!
+1 same problem...
Any solution???
Thx.
Same.
perfect on Windows.
not working, gyroscope, compass, screen rotation on any android.
no problem with proximity and light sensors.
I had tried screen rotations witout main flex (that holdss, vibration, camera, volume, wifi, buzzer)
And the sad point is I had replaced LCD-Digitizer together these are taken from a dead hd2. So my replaced LCD is 100% orijinal. I did not seperate chasis-button flex also.
Hello Everyone!
Long time now, i have an issue with the Touchscreen of my MB526. From time to time it generates random clicks ... if i then send it to standby and wake it up, everything is fine again. I thought it may be a hardware-problem or a problem with the custom roms around, but when i posted this issue today on the Defy-Facebook-Group, i found someone with the same issue on the stock unrooted 231 Rom (BL7). The Same BL as mine ...
So may be, that there is an unidentified bug in our mobiles? may be some driver problem? Or is it an hardware-issue like the speaker of the MB525, that affects more users?
Maybe some of the Rom-Devs could try to find something related to the Wake-Up precedure what resets the touchscreen and clears this issue?
We need some help here ...
EDIT: There is now one more on the Facebook-Group with the same issue but on a MB525 ... so it's Defy in general and not only Defy+ ...
The same problem here
First of all thanks for addressing this problem. I thought i was the only one.
Ok so I'm currently on W.R.1.7, Defy mb525
And i experience the same problem. random touches and to reset it i have to lock my screen and switch it on again.
I haven't (and wont do till 5 more months) tried this on other roms. but it always starts after 1 week of installing wr 1.7.
I flashed the rom again thinking that it will solve the problems (this and batterry drops) it did but after a week it was back!
:crying:
Had that just today, for the first time.
Was playing Hill Climb Racing, when suddenly the gas pedal (on screen touch area) got stuck, then flickered irregularily 3 or 4 times a second for like 15 seconds. My defy didn't register the back button or the home button during that time. Switching off and on helped. It happened again like a minute later, but not as long. Didn't happen again since then, but if it does in another app I'll report back.
There is no demo function in Hill Climb Racer as far as I know, so the pressed gas pedal could only have originated from the touchsceen / driver side, not from faulty code in the game.
My Defy, MB525 (Green), has 2 years old and I have this issue since always, I didn´t use my warranty because I've rooted since i bought it, but just happens sometimes (the same issue on stock 2.1, stock 2.2, MIUI, CM7, CM9, CM10...).
OK, so this themes to be an issue that affects more than just a few users ...
there was a guy in the facebook group, that reported, that he had this issue to, but it stoped since he used a screen protector ... so this may solve this issue ... but i think this is not all ... The screen is (for sure) not designed to be only useable with an screen protector
and because of the Lockscreen / Wake up solve, this is not happening due to dirt on the display or something i think ...
would be nice, if some dev could answer this post, so we would know, that we are not alone and may maybe get some help in some time ...
@ MadMooney ... i also found this annoying in Hill Climb Racing It's exactly the gas-Pedal that is "locked" then .. bit it happend in other apps (by writing an sms fpr example) to ... so it may be some fingerpoint that we both have exactly the same issue with the same game and the same affected screen area ...
DJ_Synergy said:
OK, so this themes to be an issue that affects more than just a few users ...
there was a guy in the facebook group, that reported, that he had this issue to, but it stoped since he used a screen protector ... so this may solve this issue ... but i think this is not all ... The screen is (for sure) not designed to be only useable with an screen protector
Click to expand...
Click to collapse
Even i use a screen protector (Amzer one) but that doesn't help in solving the ghostly touch problem..
Its definitely a software issue
Sent from my MB526 using xda app-developers app
I have the same problem with mine, i thought it was because since 6 months back i totally cracked my screen and havent changed it because it still works as it should except looking terrible. What i have noticed thou is that i can absolutely not use my phone while charging it because that will to a 100% result in my screen going wild
I am also facing this issue. I mildly heat the screen using heater the problem solve for one or two weeks then It again appear. I found another thing that this issue may solve if press the right side of speaker hardly. Please try these and report
Sent from my MB526 using Tapatalk 2
Same here. It happens when my screen is a bit oily so if I clean it it doesn't do it anymore.
Happens to me too, exactly as OP said, Bayer MB525
Happend with CM7.2 and CM10, I don't remember having this in stock Froyo 2.2.1
EDIT: Things that make it happens more often:
1. Any kind of liquid over screen (mainly water)
2. While connected to an USB
WOW ... such a mass of users with the same issue ... and no one ever told that before?!
OK, so we are facing an big issue with all roms and all kinds of devices / displays ... so maybe it is a driver problem, beacause it is solved if you turn screen of and wake up again ...
the issue with the charger is named here too ... i also had this problem ... with low battery and charger the screen reacts like an resistive touchscreen, not like an capacitive ... maybe these are all the same issue ...
No dev here, that can pick this thing up and have a look at it?
DJ_Synergy said:
@ MadMooney ... i also found this annoying in Hill Climb Racing It's exactly the gas-Pedal that is "locked" then .. bit it happend in other apps (by writing an sms fpr example) to ... so it may be some fingerpoint that we both have exactly the same issue with the same game and the same affected screen area ...
Click to expand...
Click to collapse
Then let me add that right when it happend, i saw a tiny sweat droplet on the screen. I wiped it away instantly, but the effect stayed for another couple of seconds. Might really be that the touchscreen/driver-combo gets temporarily overloaded from the continuously moist spot.
I had that effect on other phones too, always capacitive screens. If that's all there is to it, there's probably not much we can do about it to solve it other than to make the driver less sensitive, but that would be a bad thing, if you ask me. I like that it reacts at the lightest touch.
Yeah, it reacts fine. But the idea of overload is nice ... Maybe it could be solved by setting up the Multi-Touch-Points to 5 e.g. ???
I think we need an update zip from our great developers to reduce the sensitivity of our touch screen especially for those who realy suffering due to this defect. We can find lot of topics regarding this issue in various headings like !My phone become crazy, touch screen malfunction etc! In QA section
Sent from my MB526 using Tapatalk 2
Yeah, for sure .. but if there is no dev reading this posts, there won't be any zips ...
and with the xda-board-rules you can't open a thread for that in the Dev-Section -.-
So ... we will be alone thanks to the admins and the board rules, cause no dev will read the Q&A Section ...
My phone Defy+:
I had this issue on cm7.2 tried following solution but none of them works.
1) Changed to cm10 thought it might be Rom issue but no i have ghost touch on cm10 too.
2) I applied screen guard to see if it wrks but not it does not wrk i still have ghost touch.
P.S. While charging the phone GT disappears.
Try to heat ur touch screen lightly using a hair drier
Sent from my MB526 using Tapatalk 2
Hi All,
I recently noticed that my auto-brightness wasn't working any longer.
I installed GPS Status&Toolbox and it indicated that my light sensor was reading 0 lux.
Assuming that it was a ROM bug I flashed CM10.1 . Sadly this has not solved my problem. I still get a reading of zero lux . My Nexus only has a screen protector on and I can see nothing blocking the sensor.
I can't imagine it is a very complicated component and in it's isolated position i find it hard to believe that it was damaged.
Has anyone else experienced any problems and do you have any idea how to fix this?
Thanks in advance
A kernel is what bridges hardware and software. Try flashing a different one.