Vibrate Broken? - One (M8) Q&A, Help & Troubleshooting

Has anyone else managed to break the vibrate function on their phone?
Mine just randomly stopped vibrating the other day (I may or may not have dropped it....). No vibrate on anything, even on reboot (so it can't be a "settings" thing).
Not important enough to try to fix but a bummer.

Mine too! I'm thinking it'a an app update.. I didn't drop mine. No vibrate at all... Stopped maybe three days ago. Odd.
I tried testing vibrate using diagnostics via code *#*#3424#*#* no dice tho

digitalcoder said:
Mine too! I'm thinking it'a an app update.. I didn't drop mine. No vibrate at all... Stopped maybe three days ago. Odd.
I tried testing vibrate using diagnostics via code *#*#3424#*#* no dice tho
Click to expand...
Click to collapse
I have the same problem.
I tried to install a program that controls the operation of hardware and tells me that it works but when I go to actually try the vibration does not give signs of life.
well I think that's any update app that make problems with the vibration component

digitalcoder said:
Mine too! I'm thinking it'a an app update.. I didn't drop mine. No vibrate at all... Stopped maybe three days ago. Odd.
I tried testing vibrate using diagnostics via code *#*#3424#*#* no dice tho
Click to expand...
Click to collapse
Wow, that's really interesting. I'm always flashing things, but haven't put any new firmware or a new ROM on for a week or more.... Outside of a firmware I can't imagine anything else affecting vibrate to such a fundamental level (ie doesn't even happen on hard reboot). Thanks for the feedback.

What firmware are you guys on and what ROM s-off?

spinninbsod said:
What firmware are you guys on and what ROM s-off?
Click to expand...
Click to collapse
3.28.401.9, ARHD 22.0 for me.

was thinking it could have been an app update, but that is too low-level to kill off a hardware function. I'm completely stock for once,
software # 2.23.710.1
android 4.4.3,
htc sdk api level 6.25
s-on
hboot 3.18.0.0000
Radio 1.19.21331147a1.09g

android 4.4.3
sdk api 6.25
android revlution hd 11.2
kernel 3.4.0

Mine just upgraded to 4.4.4, still broken...

I noticed that sometimes it will work normally.
quickly turns off again.
ps
upgrade to 4.4.4 with cyano

sheva7_ said:
I noticed that sometimes it will work normally.
quickly turns off again.
ps
upgrade to 4.4.4 with cyano
Click to expand...
Click to collapse
Yup... mine just did this too

guys...
Today while I was "playing "with smartphone I start "No-frills CPU Control" and it set me (automatically i suppose) the frequency of the cpu:
1.19ghz min
2.266ghz max
Vibration has restarted to go and there are now 10h and 3 reboots that works ok.
Now I try to lower the frequency hoping that the vibration continues to function.
so I think to use some of your battery
If someone try to change frequency let me know with result

im glad others have this problem...
I thought it was just me and have actually replaced the vibrator motor and still doesn't work. Did anyone find out what was the cause of problem? Latest ARHD rom with latest firmware installed....

As of yesterday my vibration stopped working as wel. Running ARHD 22.2
I have the feeling that it has something to do with my phone battery going totally dry yesterday. After i charged it again the problems started.
Once in a while it does vibrate, but very randomly.
When i try the *#*# command it doesn't work either, but reading the posts here I'm very reluctant to believe it's a hardware problem.
Gonna try flashing a different rom and kernel and see what happens..

sheva7_ said:
guys...
Today while I was "playing "with smartphone I start "No-frills CPU Control" and it set me (automatically i suppose) the frequency of the cpu:
1.19ghz min
2.266ghz max
Vibration has restarted to go and there are now 10h and 3 reboots that works ok.
Now I try to lower the frequency hoping that the vibration continues to function.
so I think to use some of your battery
If someone try to change frequency let me know with result
Click to expand...
Click to collapse
tried this, but didn't work for me

I was IC rom when it happened to me the other day. My vibrate worked fine until I hit power saver and then it quit. It will occasionally work for one or 2 pushes a day... If that.
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
I've flashed different roms, kernals, wiped, restored from known working backup, and etc. Nothing has fixed it for me yet.

Xtincthed said:
As of yesterday my vibration stopped working as wel. Running ARHD 22.2
I have the feeling that it has something to do with my phone battery going totally dry yesterday. After i charged it again the problems started.
Once in a while it does vibrate, but very randomly.
When i try the *#*# command it doesn't work either, but reading the posts here I'm very reluctant to believe it's a hardware problem.
Gonna try flashing a different rom and kernel and see what happens..
Click to expand...
Click to collapse
This.
I also let my phone go all the way out of battery because I was on a bus trip and there was no electric outlet to charge. And a day after that I experienced vibration problem too

Related

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?
Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..
Which ROM?
I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?
Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):
Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....
Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone
Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.
rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks
rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.
are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...
Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).
I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...
After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.
You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

[Q] reboot random

Hello,
I had random reboot before with my leedroid 2.3b, and I had one also 30 minutes ago with AuraxTSense, so I'm asking if the cause is the rom or not.
When he reboot, he's not hot, I see it reboot sometimes and the phone was at normal temperature (approximately with my hands lol). it reboots max 1 time per day.
So I'm tellng myself that's it could be due to:
- radio
- S-OFF
- one app
For radio, I try tu update from 32.48.00.32U_5.11.05.14 to 32.47.00.32U_5.10.05.23, and I'll see.
For apps, the problem is that I would have not to restore all my apps, to see if one app cause it.
What do you think of it?
Thanks
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
Or as fnotsje said, could be hardware related
fnotsje said:
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Click to expand...
Click to collapse
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
eden2812 said:
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
It's installed but not configured in smatass mode, you advise me to uninstall it and to test?
Or as fnotsje said, could be hardware related
Click to expand...
Click to collapse
What is surprising, that if it's that, i t should reboot many more times than one time per day no?
Thanks
thierry_b said:
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
Click to expand...
Click to collapse
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
fnotsje said:
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
Click to expand...
Click to collapse
Yes and always only one time per day, just one time maybe 2.
I desinstalled SetCPU, it changes nothing.
What do you advise me to do?
Wipe and install minimum apps, and see if I've that, and little by lttile, reinstall one new app...test few days again...?, it will be long :-(
Thanks.
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
GoogleJelly said:
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
Click to expand...
Click to collapse
With the minimum of apps, for example to see if it reboot or not?
Because if t's an hardware problem due to the radio, it censed to reboot even with few apps no?
For carrier as I'm at Orange like you, I think, they could change fastly my phone maybe. I will try that if anything works. You think that if I do that, I've to find an orange rom? I'm asking myself if they accept an HTC even restored with RUU.
Thanks
I have the same issue and ITS DRIVING ME MAD!!!!!!!!!!!!
I never experienced this with my stock ROM... so I firstly tried a gingerbread ROM... when it started... i then moved to a Sense Rom and still reboots occured... I'm now on my 2nd cooked sense ROM and still having reboots!!
WTF? is there a quick sollution?
thank you!
SO MANY follks seem to be having problems with [email protected]! Is there seriously no sollution to this or a common cause..?
had the same problem & is with HTC getting fixed
there are a few posts about it if you search - the only fix seems to be to send it to HTC for a new motherboard as some presume that it's overheating.
11 march still waiting on return of my Desire
I can relate to your issues. Mine kept rebooting when I tried to use the GPS. Like you I had mine rooted, S-off and was using a custom ROM.
After many tests, I downloaded a stock RUU, installed a different navigation app and once again, it rebooted.
Bottom Line: take it back. Its probably defective. Just make sure you're running a stock ROM. Download an RUU.

Blank screen on my Desire on pretty much any 2.3 ROM

After originally sending Tillus a PM as he had a similar issue with another ROM I thought I had better post here.
I have tried Oxygen, CM7 and Redux but I get this problem with all of them. Everything runs fine for a few days and then I go to unlock my phone and the screen stays blank. The keys light up but the screen stays just blank. Tried Back-Trackball-Vol down (as suggested in post linked to in PM below) but it didn't work. I then have to take out the battery and restart.
Once it starts happening the gaps between it happening get smaller and smaller. It has happened 4 or 5 times today alone.
First time, on Oxygen, my phone eventually wouldn't turn on any more and I had to get HTC to fix it under warranty.
Then I tried Redux where it happened after a few days. Someone on here suggested I look at the CPU settings. I did and saw that Redux had a power save mode, so I tried that and it seemed to work but after a few more days the same thing happened. Although this was after a reboot so perhaps the phone didn't retain power save mode afterwards.
On Sunday I loaded CM7. Worked for about 24 hours before the blank screens started.
Running ONDEMAND governor, Min 245 Mhz, Max 998 Mhz.
Any ideas?
Here is the PM I sent to Tillus for info:
Tillus said:
d10brp said:
Tillus,
Hope you don't mind me sending you a PM. I noticed you had the same issue as me (screen not turning on from lock screen http://forum.xda-developers.com/showthread.php?p=9652281#post9652281). Did you ever find a permanent solution? I'm getting this issue with Oxygen, Redux and CM7.
Thanks
Alan
Click to expand...
Click to collapse
Hi,
uhm, I think this was a specific Auraxtsense issue which was resolved eventually. I never experienced this fault again - neither in a later auraxtsense version nor in oxygen (2.0.3) which I am using now.
Are you overclocking your cpu? Maybe you set the screen-off frequency too low? Or are you using a undervolt-kernel with very low settings, especially in low cpu frequencies?
As I said, I haven't experienced this issue for a while now.
Click to expand...
Click to collapse
Did you try keeping the power button pressed for a few seconds? I know, it sounds silly
Are you sure you don't have this problem on a 2.2 rom? I don't see you mentioning it in your post. Only that you have this issue with 2.3 roms.
What kernel do you use? Try a SVS kernel, don't use a HAVS kernels for now.
Also are you sure you tried the latest version for let's say Oxygen? From the oxygen changelog:
v2.0.3
Fixed font bug introduced in previous version
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
Click to expand...
Click to collapse
I'm fairly new to this so I have only tried 2.3 ROMs since rooting. Obviously phone has been running official sense just fine on both 2.1 and 2.2 for about a year.
Also, apologies for this, but I don't know what the kernal is. Just followed the noob video tutorial. Is it Alpharev?
Haven't tried Oxygen since RC7 so I might try it out.
Seems to be memory related as just after I posted, something slightly different happened, I pressed the lock button and the lock screen appeared but then froze. After a couple of minutes the screen eventually locked again with a very slow jerky animation. So I have just removed a couple of apps that seem to be running all of the time, App protector pro and StumbleUpon. No crashes since then (2 hours).
Sent from my HTC Desire using XDA App
So that worked for about 2 days. Now thinking maybe it is the SD card. Ordered a new one.

[Q] HTC one V g-sensor not working

All of the sudden my screen wouldn't auto rotate in both apps and normal interface, i haven't downloaded any app recently so i don't think it is caused by an app.
Things i've done to try and fix it: - turn auto-rotate off\on in quicksettings notification bar, did the same in screen settings and again in accessibility
- calibrated g-sensor, which doesn't give any errors
- rebooted phone after calibration or auto-rotate setting change(multiple times)
- downloaded phone tester app and it can't find the g-sensor
I'm on the last update of Suprimou rom with titanium kiss kernel and have been on this rom for a few months now.
Any suggestions?
E=shaggydiamond;41864191]All of the sudden my screen wouldn't auto rotate in both apps and normal interface, i haven't downloaded any app recently so i don't think it is caused by an app.
Things i've done to try and fix it: - turn auto-rotate off\on in quicksettings notification bar, did the same in screen settings and again in accessibility
- calibrated g-sensor, which doesn't give any errors
- rebooted phone after calibration or auto-rotate setting change(multiple times)
- downloaded phone tester app and it can't find the g-sensor
I'm on the last update of Suprimou rom with titanium kiss kernel and have been on this rom for a few months now.
Any suggestions?[/QUOTE]
HTC one x had the exact same problem which you are saying ..there were a few solutions which worked temporarily well so u can search Google for the same problem but just mention one x, u will find some solutions ...try this my frnd also had a one x he tried the solutions which worked fr a week but ultimately he had to sell his phone...good luck..
http://forum.xda-developers.com/showthread.php?p=40067389
Here's a link with problems and a few suggestions..
Hope ur g sensor starts working and this s*** doesn't happen with me and other HOV users..
Thanks, im trying some methods out now, really want it to work again because i don't think htc would like it if i'd send a phone in with unlocked bootloader and this kind of problem.
Update, It's working again! not sure how long it will work.
I rebooted several times while holding down volume up button, then turn it off and let it sit for 10 min.
Now it's working
happened same thing to me so returned to the stock then it was fine now again I'am rooted
shaggydiamond said:
Thanks, im trying some methods out now, really want it to work again because i don't think htc would like it if i'd send a phone in with unlocked bootloader and this kind of problem.
Update, It's working again! not sure how long it will work.
I rebooted several times while holding down volume up button, then turn it off and let it sit for 10 min.
Now it's working
Click to expand...
Click to collapse
could you please notify me if it sops working actually i am very concerned about this problem...
glad that your g-sensor started working again good luck for future...
Pranav Sharma (PS) said:
could you please notify me if it sops working actually i am very concerned about this problem...
glad that your g-sensor started working again good luck for future...
Click to expand...
Click to collapse
Will let you know. But so far so good it is still working, let's hope it was a one time experience eh:good:
shaggydiamond said:
Will let you know. But so far so good it is still working, let's hope it was a one time experience eh:good:
Click to expand...
Click to collapse
Yes let's hope so i love this phone..:good:

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Categories

Resources