Related
I have a screen freezing after unlock or call problem for months, tried differnt things like changing ROMs, lockscreen apps but none of them worked, my screen was still unresponsive for a while after unlocking screen, then i saw senaia's post about TP Calibration and tried, the problem is gone so i wrote this tutorial to help the others.
I take no responsibility for any DAMAGES or BRICKED phone, do it at your own risk
WARNING: This will ERASE all of your data, applications, sd card, messages, contacts etc. so make backups of them.
Here is step by step guide
DONT FORGET TO BACKUP
1. Make a goldcard using tutorial in this thread
2. Unrar attached file to the root of Goldcard
3. Power off phone, boot to bootloader with volume down and power button pressed
4. Wait for while it will search for files
5. Then a screen will show up like
Power => Reflash
Vol-Dn => DIAG
6. Press Volume Down for Diag
7. You will see a screen asking you to put phone on a flat surface, do what it says
8. Once that is done you will see a menu about Clear S58 Data, Ignore it, pull the battery and reboot
9. Repair is done, problem should be solved now
This is my first tutorial for XDA, so any suggestions are welcome
Thanks to senaia, he showed how to do
IT works, finally!
I can confirm that the tutorial made by mstfkaratas is working.
Thank you, I cannot describe how much i appreciate it, my beer money is on it's way!
thanks for beer
nevermind
It seems like i got a bit too emotional on this, and my previous post was a little rushed.
The screen freezing gradually comes back in 24 hours. The waiting times become longer and longer. After i did the above steps the lag was gone, but unfortunately it comes back. Especially after i set up to sync with my google account. I also tries to make a new accont, but without success.
I had this issue but admittedly it had just about disappeared when I upgraded to 2.3.5, but still had the odd freeze when receiving a call but not as bad, I did this tutorial and have not had 1 freeze since, may I suggest your problem is hardware (digitizer) Ivaxona?
hi ivaxona your problem can be hardware related or an app you installed, i can suggest you install apps one by one and check the problem
i cant help you more than this because i am not an expert this solution helped more than 5 phones AFAIK
Sent from HTC WFS
Hi, thanks for the response, i also thought that it may be a touchscreen problem, but it got me thinking, that how could be this possible, when after a short time it start to work absolutely perfect.
I also tried to create a new google account just for testing so the possibility of a 3rd party application causing the problem is eliminated.
I have to mention though that after i place the first call the performance response time degrades significantly. That's why i think that it could be a radio problem as well.
I have to admit that i just recently purchased this digitizer on ebay, and it looked like a second hand unit so i might jut got screwed up.
As a last try before i try to change the digitizer once again, i'll try to upgrade to 2.3.5 as it was suggested.
I'm still on a stock ROM, i suppose there is no 2.3.5 official ROM so i'll have too ROOT the phone, right?
once again thanks for your help!
http://www.filefactory.com/file/c0a...5.3035H_7.53.39.03M_release_225747_signed.exe
this is 2.3.5 EU RUU from shipped roms thread, you can try this, if this doesnt work, there should be tutorials for how to install in this forum. i hope this helps
edit: here is a thread about upgrading 2.3.5 http://forum.xda-developers.com/showthread.php?t=1363693
Thank you very much, got my brothers device to work now
after i upgraded to 2.3.5 the fix is working! Thanks a lot!
Solved!!
Many many thanks!
Ciao.
Thanks brother
thanks brother..!!!
After many months of searching for solution, it is finally fixed.
It's a relief it's not a hardware issue. I am using custom 2.3.5 and it worked.
Thanks.
thanks brother, you saved my cel phone, I wonder which phones this works ???? I tried it with my wildfire s and is worked
nathatheboss said:
thanks brother, you saved my cel phone, I wonder which phones this works ???? I tried it with my wildfire s and is worked
Click to expand...
Click to collapse
the diag file used for this process is only compatible with wildfire s, i dont know if other phones have that kind of diag files
Sent from my HTC Wildfire S
Thanks for your how-to...
Sadly it didn't help for me, although I've successfully performed the DIAG boot on my S-OFF WFS. I'm running the latest version of alquez's Cyanogenmod 7.2.0-RC1-marvel-KANG (03-24).
I'm also not sure if I have the problem that is described in this thread.
Whenever I power on the phone and try the unlock-slide the first time, the slider jumps back after some pixels. Everytime, it's really nasty.
Maybe this is something else and I should start a new thead for it?
Thanks!! This really works!!! I had replaced the screen, but it only worked the left side. After applying your method, this little wilfire s works!!! My girlfriend will be very happy!!!
Thanks for the tut.
Sorry, i still have this proble in my phone, one question.
To do this tutorial, we must be S-OFF?
Thx
no need to be s-off, i have positive feedbacks with s-on devices
Sent from my Wildfire S using Tapatalk 2
It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
makeoutactics said:
It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
Click to expand...
Click to collapse
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
hell_lock said:
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
Click to expand...
Click to collapse
Never been dropped. Yeah restarting resolves it temporarily,for me, then it will come back again.
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
kurotsugi said:
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
Click to expand...
Click to collapse
Oh. wrong post? Can mods merge it? or perhaps delete this thread.
kurotsugi said:
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
Click to expand...
Click to collapse
Thanks, i will try it. I'm out of thanks. Will press it tomorrow.
no need to do that...give your thanks for the real dev instead of me
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this (PLEASE NOTE THIS IS Version 2 and please use this version to revert successfully previous version had some flaws in it): http://www.mediafire.com/?d4n1fx3cj446k1l)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
5pace said:
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this: http://www.mediafire.com/?muiza8fbwidq69d)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
yuryvrn said:
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I have the stock JOP40D, yakju, the phone is rooted. My sensors.tuna.so is attached. I am new to android, did I understand you correctly all I have to do is to replace the original sensors.tuna.so by the modified file you will send back? Or I need to apply your patch as described in the 1st post (since my ROM is stock)?
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
I have this issue too. I am on CM 10.1 EuroSkank on stock kernel. Is there a zip file I can flash? Thanks for the fix!!!
Sent from my Galaxy Nexus using xda premium
PaXGeN said:
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
Click to expand...
Click to collapse
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
LKNim said:
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can try the Fix, if it doesn't work properly you can restore the backup with the Un-Fix :good:
Proximity Sensor Blues!
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I'm new to this forum, so bear with me. I've been having the Proximity Sensor Blues lately and am in need of a cure. I've got a Verizon GNex (rooted and unlocked) running JB Sourcery 4.0 (soon to be 4.1 unless you tell me different) with their most recent "stock" kernel. I've attached the two files you requested, but have not tried the fix yet.
Considering the ROM I'm running and the attached files, is it OK for me to try the fix? Should I try a different kernel? Does it matter if I have TWRP instead of CWM? Please help!
Everything its ok
Sent from my Galaxy Nexus using xda premium
Sorry guys, I didn't have much time to reply this topic I had exams plus real life hassles to deal with, again I am sorry for the delay.
I've attached flashable zips files and appended your appropriate usernames with them, you can download and flash these files as per your usernames. If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
On a side note I knew about the app (even before making this mod), but I wanted my proximity sensor to be disabled without depending upon an app so I eventually came up with disabling it through lib file which was far more efficient. And these files aren't supposed to disable all the other sensors, using other ROM libs on another ROM will stop the functioning of other sensors, it's just because every ROM is unique in it's own way so these files require to be modded according to their respective ROMs source files. And yeah, again I do not guarantee this mod would work because after applying it to my Nexus, it still rebooted but the reboots were less occurring as compared to when the proximity was enabled.
P.S. I re-purchased Galaxy Nexus, the old one was a C8 (White color), and luckily the new one was a C2 (Black color) and it can do wonders in overclocking and undervolting.
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
bacekoko said:
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
Click to expand...
Click to collapse
You may want to try this:
5pace said:
If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
Click to expand...
Click to collapse
If it doesn't help in your case, then I am sorry as I am out of ideas.
So far, so good. Got fed up with the PS on my phone and tried this today. The sensor is disabled as far as I can tell. THANKS!
It worked for me, thanks.
All sensors are Off
Thakyou for this fix.
Not even a single call drop since i installed but none of the sensors are working.
I don't want any sensors but just the Camera so please if u can make it work I'll be very thankful.
Currently I'm on 4.1.1 JRO03C
I tried it on JDQ39 (4.2.2) it disabled only the proximity but calls were still dropping.
If possible then please make a fix to disable all sensors on 4.2.2 except camera and sound.
Thanx again.
I've a gnex with installed custom rom( minco v5 4.1.2 )
I've tried your mod for proximity sensor fix and it worked but it disabled light sensor too. I've tried app on playstore but it does the same.
I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?
thank's,
Daniele.
My sensor PLS
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
ryza666 said:
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
Click to expand...
Click to collapse
I've use PaXGeN's sensors modified by you 5pace and there are working on my CM 10.1 M3 ( on every kernel ). I think PaXGeN pack sensors will work on every single custom rom based on jb 4.2.2. My proximity sensor is disabled but everything else is working smooth. I've checked efficiency by Android Sensor Box. Thanks for this thread.
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
hi
Whenever I open my wireless and connect to network, I loose control on my phone! it started behave illogical, button pressed, screen dancing and preventing me from doing anything on it. the solution, each time, is to remove the battery and reboot!
I did a full wipe and flash, nothing changed. Tried several ROMs and still nothing changed. scan the device with antivirus (android app and from the computer) nothing changed too!
I faced it recently, but I don't know how to find the problem, isolate it, and fix it! it's driving me crazy!
can anybody help me with this?
Thanks
banditboy13 said:
hi
Whenever I open my wireless and connect to network, I loose control on my phone! it started behave illogical, button pressed, screen dancing and preventing me from doing anything on it. the solution, each time, is to remove the battery and reboot!
I did a full wipe and flash, nothing changed. Tried several ROMs and still nothing changed. scan the device with antivirus (android app and from the computer) nothing changed too!
I faced it recently, but I don't know how to find the problem, isolate it, and fix it! it's driving me crazy!
can anybody help me with this?
Thanks
Click to expand...
Click to collapse
One thing you could try is the auto rotation fix guide
http://forum.xda-developers.com/showthread.php?t=1970972
I know its not an auto rotation problem your having but basically the guide instruct you to flash the latest official rom with updating all the internal drivers so may be a fix that works for you to? - cant hurt to try!
tonylee000 said:
One thing you could try is the auto rotation fix guide
http://forum.xda-developers.com/showthread.php?t=1970972
I know its not an auto rotation problem your having but basically the guide instruct you to flash the latest official rom with updating all the internal drivers so may be a fix that works for you to? - cant hurt to try!
Click to expand...
Click to collapse
I tried your suggestion. till now I face no problems. I should wait a couple if days to see if this problem happen again
thanks
Sent from my Desire HD using xda premium