Hello together,
at first: sorry about my english
since today i get touchscreen settings
despite the fact that everything worked, it suddenly appears as of today.
but also between the normal operation can not use my touch screen
sometimes i need 10-20 few times more than 30 tries to get back in system...
im on blanc build actually
i have testet this builds (today only!!!)
Mdeejay FroYo HD v.3.7 (this is actually on my card)
Mdeejay FroYo HD v.3.6
Mdeejay Froyo Sense v. 2.4.2
Mdeejay_eVo_Sense_v._1.8
Mdeejay_eVo_Sense_v._2.0
this programs are installes by default on first installation:
Superuser, root explorer, es file explorer, gscript lite
actually im on 7.6 - kernel
Radio Rom: 2.15.50.40 (but i have tested the 14 too)
the deactivation of my G-Sensor with the known script wont work too
i have tried to format my sd cards, u tried 3 cards, that cant be the problem there...
please help me *cry* i wont go back to wm6.5
soundclub said:
Hello together,
at first: sorry about my english
since today i get touchscreen settings
despite the fact that everything worked, it suddenly appears as of today.
but also between the normal operation can not use my touch screen
sometimes i need 10-20 few times more than 30 tries to get back in system...
im on blanc build actually
i have testet this builds (today only!!!)
Mdeejay FroYo HD v.3.7 (this is actually on my card)
Mdeejay FroYo HD v.3.6
Mdeejay Froyo Sense v. 2.4.2
Mdeejay_eVo_Sense_v._1.8
Mdeejay_eVo_Sense_v._2.0
this programs are installes by default on first installation:
Superuser, root explorer, es file explorer, gscript lite
actually im on 7.6 - kernel
Radio Rom: 2.15.50.40 (but i have tested the 14 too)
the deactivation of my G-Sensor with the known script wont work too
i have tried to format my sd cards, u tried 3 cards, that cant be the problem there...
please help me *cry* i wont go back to wm6.5
Click to expand...
Click to collapse
It seems to be a hardware problem rather than software or Android problem Did you remember if your HD has fallen in the last days? Try to make it work in Windows or try to hard reset your Phone if everything goes wrong. Maybe you are lucky. With my previous phone I had similar problems.
it isnt a hardware-problem, in windows mobile is no problem, i have tried the last 30 minutes without freeze
and no, my hd2 has not fallen, till yesterday 5 pm were everything ok, without any freeze in last months
I get that occasionally too. I have just reported sometimes as many as 3 times before it behaves.
Sent from my HD2 using XDA App
me too
happens to me too, from time to time.
freeze last about 2 secs max.
Im using evo kernel (20?, oct) and the android 2.2.1 build.
okay....it was a silent death of my TS ...
now under windows mobile wont work too (with original wm build...)
i wrote htc support for repair/change of the phone...i hope they will answering fast *cry*
iAm also having this problem, iThought it was my android build at first but iTried a different one and it still continued to freeze. Then iUsed wmo for a whole day and the freezing attacks continued.
I am having the same problem myself!
Whenever I use the red power button, whether it is for waking up out of standby or using a long press to activate the Phone Options menu, the touch screen stops working.
I have found that waking up the phone, then quickly putting it back to sleep and waking it up again gives me about a 90% chance of it working. So I have to press the power button 3 times in quick succession to wake up my phone now.
I hope I won't have any serious long term effects on my phone, but I'm definitely going to be talking to HTC and T-Mobile about this soon.
it happenned with me also when im using 16 gb memory that come from the phone. but when im using smaller one (8gb class 2), it work fine. maybe 16 gb took long time to read.my suggestion try it with smaller capacity or you can buy new one with higher class(6 or maybe 10)
joeispopular said:
iAm also having this problem, iThought it was my android build at first but iTried a different one and it still continued to freeze. Then iUsed wmo for a whole day and the freezing attacks continued.
Click to expand...
Click to collapse
Most annoying posting style ever.
iRecommend selling your HD2 and buying an iPhone.
Have you wifi on ? If I use wifi or wifi hotspot then after the phone wakes up I always get a touchscreen freeze it's definitely not the hardware.
Tried G sensor fix? i.e. editing AK8973Prms.txt
This has something to do with android on the hd2 eventually causing it, I work for tmo n see all the issues with the hd2 n this has never been an issue so I thought it was just me when it happened to me I just exchanged my hd2 and its fixed but now I see more people having the issue n the only thing thats common is we use android
Sent from my GT-I9000 using XDA App
apallohadas said:
Most annoying posting style ever.
iRecommend selling your HD2 and buying an iPhone.
Click to expand...
Click to collapse
iRecommend for you not to replay if you dont have a solution to the problem at hand.
I think it's due to the G Sensor. I have meet this before and have some test on my HD2. I found that if some application running on G Sensor, it may cause the freeze, ie GPS, Google Map， Compass. I am not sure this is due to my setting.
I shut down the G Sensor by Gscript and the script below found in XDA and seems this help. I hope this can help you too.
1. Create a script name 'Stop'.
SU is required, input
mv /system/bin/akmd /system/bin/akmd2
killall akmd
save this script and run, it will shut down the G Sensor.
2. Create a script name 'Start'
SU is required, input
mv /system/bin/akmd2 /system/bin/akmd
/system/bin/akmd
save this script, and you can run this to restart the G Sensor while u need it again.
I dont' know whether there is some widget or application to control the G Sensor better, but you can try this first to check if G Sensor cause this problem.
I found if shut down G Sensor, the GPS won't work. If anyone have idea how to make GPS work without G Sensor please advice.
apallohadas said:
most annoying posting style ever.
Irecommend selling your hd2 and buying an iphone.
Click to expand...
Click to collapse
hahahahahahahahahhahahaha
Turn your WIFI off then put it to sleep, works for me 100% of the time.
Same problem here. All ROMS based on HTC Sense freeze. Press the turn off button once and wait for 5 or 10 mins, and then the phone doesn't come back from lock anymore. This issue doesn't seem to be happening with any Nexus one Roms.
I have tried all possible solution, WM roms change, SetCpu, etc...
Jade.N said:
Same problem here. All ROMS based on HTC Sense freeze. Press the turn off button once and wait for 5 or 10 mins, and then the phone doesn't come back from lock anymore. This issue doesn't seem to be happening with any Nexus one Roms.
I have tried all possible solution, WM roms change, SetCpu, etc...
Click to expand...
Click to collapse
If press turn off button while it's freeze, it's hard to come back from lock. While it's not freeze, press any key while the phone is locked, if the screen is not come back, I still can touch the screen and the unlocked screen will be come back again.
I think it's a problem that the screen won't turn on immediately after we press the button, but at that moment, the phone can receive our control by touch the screen. If it's freeze, touch screen is not work, so keep dark. But if it's not freeze, the screen will be on. So I think it's the problem to solve the freeze problem.
HD2 t9193 touchscreen repair
Anyone know where I can buy this part?
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
Hi everyone.
I got some trouble with my Samsung Galaxy S II.
The home button (the physical one just under the screen) sometimes work and sometimes doesn't want to work anymore.
I'm trying to understand why it works or doesn't.
I'm going to try to reset the firmware and put the original kernel back.
If someone got some advices,
Thanks.
Update : Still doing the trick, Back to original fw and kernel changed nothing.
How can a that expensive phone have a button that sometimes works, sometimes doesn't ?
It is an hardware problem i guess ...
Noone faced the same problem ?
hi
can anyone please help me?
i have had an atrix for almost a year now and have had no issues with it. recently i took a big step and decided to get the cm10 rom by th3bill onto my atrix!
all worked fine for a few weeks until about a week ago. i noticed that my lockscreen pattern wasnt entering as normal. the pattern would not connect to the dots i wanted it to. on the main screen if i tap on the central button to get to the menu for my apps it will automatically respond my touch to the right/left icon and take me onto my contacts/sms instead. also while typing certain letters e.g "t" will not be recognised and instead "r" will show up instead.
somehow i managed to remove my pattern lock but the other issues are still present.
i thought that it may be a bug with the rom so i decided to go back to cm7.2 which was running perfectly on the phone thinking that this may be the solution, but even that rom is now giving me the same problem :crying:
can someone please advise me as to what the problem is/what i should do?
thnx in advance
Ok so i also had/have this problem. You can find a temporary solution and info here http://forum.xda-developers.com/showpost.php?p=27595402&postcount=1
I replaced my digitizer and the dead zone changed position.So know that replacing the digitizer might help or might not help...
Good luck
Oh and always search the Solutions to common problems thread before posting!
I have a Lenovo z2 plus whose bootloader I recently unlocked, installed twrp, installed viper os (android - 7.1.2) and rooted it. whenever I try to use my phone (since the last evening) , the touch works for about 2 seconds and then stops working(every time) . I was thinking it might be a software/rom issue but when I close the Screen and before opening I keep my thumb at the portion near the front camera/speaker part pressed and then open the phone, then the touch works fine till I remove my thumb from there. When I remove my thumb, then again the touch stops working. Then to make the touch work for more than 2 sec again , I need to shut the screen off and do the thumb thing again. Due to this I'm thinking this might be a hardware issue but it were a hardware issue, then why does the touch stop working exactly about after 2 seconds without the thumb thing and touch starts working every time I open the screen with the thumb thing again till the time I remove it . And due to that timing thing it seems like it might be a software issue. All the other buttons are working perfectly. I really don't want the factory reset the phone till it's really necessary due to all the data and stuff. Can anyone please tell me what the problem is and how to fix it.
Thanks,
Manan
Are you able to fix now?
Manan12 said:
I have a Lenovo z2 plus whose bootloader I recently unlocked, installed twrp, installed viper os (android - 7.1.2) and rooted it. whenever I try to use my phone (since the last evening) , the touch works for about 2 seconds and then stops working(every time) . I was thinking it might be a software/rom issue but when I close the Screen and before opening I keep my thumb at the portion near the front camera/speaker part pressed and then open the phone, then the touch works fine till I remove my thumb from there. When I remove my thumb, then again the touch stops working. Then to make the touch work for more than 2 sec again , I need to shut the screen off and do the thumb thing again. Due to this I'm thinking this might be a hardware issue but it were a hardware issue, then why does the touch stop working exactly about after 2 seconds without the thumb thing and touch starts working every time I open the screen with the thumb thing again till the time I remove it . And due to that timing thing it seems like it might be a software issue. All the other buttons are working perfectly. I really don't want the factory reset the phone till it's really necessary due to all the data and stuff. Can anyone please tell me what the problem is and how to fix it.
Thanks,
Manan
Click to expand...
Click to collapse
HI Manan,
Are you able to fix permanently? I tried to hold between speaker and front camera but not seeing that touch is working. Can you please share some pic pointing where exactly to touch? Also are you pressing hard or lightly? Please share how to do that?
Also later are you able to resolve the issue? Did you change digitizer etc. Did it worked normally? Please let me know.
Regards
Anil
Workaround
I tried one workaround indicated by someone else on another thread. Follow below steps
Press power button to put screen off
Hold phone in left hand and put left thumb on screen
Press power button to start screen
Touch with right hand fingers
It will work till left thumb is there on screen..
If touch is lost follow from step one
Atleast this helps alot instead of only 2-3secs stuff..
Thanks to one who indicated this workaround
abalanag said:
HI Manan,
Are you able to fix permanently? I tried to hold between speaker and front camera but not seeing that touch is working. Can you please share some pic pointing where exactly to touch? Also are you pressing hard or lightly? Please share how to do that?
Also later are you able to resolve the issue? Did you change digitizer etc. Did it worked normally? Please let me know.
Regards
Anil
Click to expand...
Click to collapse
Manan12 said:
I have a Lenovo z2 plus whose bootloader I recently unlocked, installed twrp, installed viper os (android - 7.1.2) and rooted it. whenever I try to use my phone (since the last evening) , the touch works for about 2 seconds and then stops working(every time) . I was thinking it might be a software/rom issue but when I close the Screen and before opening I keep my thumb at the portion near the front camera/speaker part pressed and then open the phone, then the touch works fine till I remove my thumb from there. When I remove my thumb, then again the touch stops working. Then to make the touch work for more than 2 sec again , I need to shut the screen off and do the thumb thing again. Due to this I'm thinking this might be a hardware issue but it were a hardware issue, then why does the touch stop working exactly about after 2 seconds without the thumb thing and touch starts working every time I open the screen with the thumb thing again till the time I remove it . And due to that timing thing it seems like it might be a software issue. All the other buttons are working perfectly. I really don't want the factory reset the phone till it's really necessary due to all the data and stuff. Can anyone please tell me what the problem is and how to fix it.
Thanks,
Manan
Click to expand...
Click to collapse
@Manan12 @abalanag What did you do to fix this issue ?
Not_James_Bond said:
@Manan12 @abalanag What did you do to fix this issue ?
Click to expand...
Click to collapse
As said in above post, please follow workaround if you are getting issue still.
For my case after couple of days, it started working normally. Sometimes that issue comes again, but i use workaround to use the phone.
I have the same issue! Please provide where you found this solution and workaround. Did you have to change screen?