hi,..
i own a HTC legend with A1 (Austria) Branding and made a 2.2 Over the air update. when i started to use it i thought that it would be faster but this has now rly changed.
Last thursday i could use my legend properly but then - 2 hours later the touchscreen didn't work any more .
i tried to unlock it but only the right side of the TS worked.
so i already tried some of the tips of some threads of XDA like hardreset , refreshing the update , and now it is a bit more useable , so i can slide the homescreen pages on different points but i cant start apps with touching..
Does anyone have a solving for this problem ?
I have no idea if the froyo update is responsible for this but I have the same problem. The top part of the screen is no longer responsive. I cannot slide the notification bar down and sometimes crazy things happen on the screen without tapping anywhere. This makes the phone practically unusable until I reboot and it usually works for some time even though the top part is not responding (notification or letter 'q' when in landscape).
Can I try something or I have to visit service? I cannot find the link where they explain how to change the refresh rate as you mention could you please provide it? also I found a couple of other threads dealing with similar problems and it looks like there is no solution am I correct ?
thanks
same thing happened to my Legend. After two months, the thing appeared, next few days all was good. Another two months and it came back. I had to send for service: they DIDN'T KNOW WHAT WAS WRONG and DIDN'T KNOW WHAT TO DO, anyway, after they sent it back to me, it's working again (until now, which is almost another two months)
My guest: there's some weird thing with the range/sensitivity of the touch screen, maybe a problem of the screen being magnetically/electronically charged without being discharged (as it should), after a while (e.g. a week) the problem disappears.
I far as I know, there's no solution. I have even found a clip on youtube (search for 'htc legend touch screen problem' or something) describing the same situation, maybe you should take a look there to for a abetter description of the case.
Anyone, please, if you know a way out of this, please, post it!
I have the same problem, the top notification bar cannot be pulled down in portrait and in all orientations I cannot use the touchscreen near the HTC logo. Mine is an unbranded and the problem just started this morning. I am running a custom rom from here and have been running the same one for a while so I don't believe the ROM is responsible.
Edit after using multitouch visible test from the market, it turns out I can't get a response that is higher than pixel 57 vertically.
I have already sent mine for service under warranty. I hope everything turns out well, because I really like my legend (form factor/design/specs). After the slow down I experienced with the froyo upgrade this problem came to spoil all these months of happiness. I will keep you posted.
EDIT:
I got my Legend back from service 3 days ago and everything looks fine at the moment. I hope that my bad froyo experience has ended.
According to the documents I received they just performed a ‘software upgrade’. This means that the problem was related to software. I guess some files could have been corrupted during the OTA froyo update. Maybe that also explains the sluggish froyo experience.
I can only suggest that before any critical updated a factory reset should be performed and hope for the best. I will update this thread if this serious problem with the touchscreen ever returns.
yeah i sent i to the warranty service too . But they said that the problem has mechanical reasons. So they suggested to repair it for 218(!!) Euros . -.-
I had exactly the same problem HTC have repaired it under waranty, so must have been a software issue, looks lik eits happening to quite a lot of poeple, pretty unacceptable consideringhow long it took them to release the Froyo update, not sur ethey bothered to test before releasing
Solution for screen problem ( HTC LEgend)
I had this problem also with my phone
touch screen works only for certain part of my screens
the top part where i cannot access
Solution
I change digitizer and
everything works well
only buy the digitizer from ebay and replace with the one that is not working
and everything should be fine after that
good luck
if you have question
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
I flashed (NAND()my HD2 a while back with the first built by DFT. worked like a charm for a few months. it was stuck on the locked screen, i flashed it back to stock it was working perfectly again. so i flashed back to the desire, it worked for about a day and stopped responding again on a lock screen. any one have this type of issue and is there a fix?
Mine did this a couple of months back, did exactly as you did with swapping the roms until finally it died even with stock rom wasnt brave enough to try replacing digi myself so sent it to repairmydevice (cant post links yet cos im a virgin ) can highly recommend them.
i think its a hardware problem
2 -3 month ago my htc leo was the same problem and i went to service and changed only one day
if it has a warrant you will broke it u change your digitilazer or touch screen , if it is not you can change your digitilazer or touch screen , u find how to change video in youtube it will lead u
Hi guys,
first of all I want to thank everyone that has and is still developing for our phone, GT540 is my first android phone and I am simply amazed with its potential which wouldn't be possible for one to use without the help of people like mike gapinsky, mur4ik, miroslav_mm, tejas, among others that aren't least important than the ones mentioned.
Well, on with the matter of this post, can someone please me why the touchscreen works perfectly on stock 2.1 roms and with ported 2.2, 2.3 and 4.0 ported roms it's completely impossible to allign?
After some research, I found out that the screen is faulty and lg managed to bypass it with kernel source code... or so I believed because today, I found about TeamWinner's touch recovery and I thought "this is great, i'll try it right away but, i'll probably go back to CWM due to allignment issues..."
So if the screen is faulty, has TW found a way to bypass that? because, when I tried it the touch screen worked perfectly, like on a stock rom!!!! I doubt that TW compiled some sort of code to bypass this problem and make it work perfectly so, what makes the screen go crazy on custom roms?
Thanks in advance to all of you.
It is most likely the (library?) they use to interpret touch that causes issues
The only people that can produce fully working (lol) code is the OEM..
I get that the issue is probably in the libs but,if so why does the touch works fine in recovery and not in the OS? And is it that difficult to try to resolve this issue having correctly working source code?
I'm at the time initiating on Linux and I'll give it a go at android development soon cuz I have advanced knowledge at C programming and I'll try to take a look at it... meanwhile if someone discovers anything useful we could try to resolve this issue.
You wanna calibration?
it posible to bring in serveal ways, but devs too lazy to make this
So, any suggestions?
I have the same problem. Any answer?
There's nothing you can do about screen calibration, unless you're some advanced programmer ( that's the only way to make calibration, port it from android 2.1 )
So if you really wanna calibration the only way to have it, is to go back to 2.1.
I use LSsetting and Touch Calibration for calibration, but I can't understand if they are really working or is just placebo
Anyway, I find calibration on Miroslav ICS a lot better than on previously roms; sometimes it doesn't get the touch, but when it does it's a lot more sensitive.