Develop Bugs

[Q] Vibrate/Haptic Feedback Randomly Stops Working (Evo 4G)

I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.

mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.

Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.

Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.

Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens

infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....

infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.

Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?

I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!

plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....

Random data/signal losses... Will custom Rom Fix?

Hey guys... as it says in the title, I am having issues with my G-nex randomly losing connection/signal but then coming back again. From what I have read, this is a common problem... anyone have any tips? Also wanting to know if I flash a custom ROM if that would possibly fix the problem. Thanks!

Not necessarily the ROM, but the radios. Try that.
There are a few 4.0.4 ROMs for the LTE GNex out now you could try as well if you want to go the ROM route.

Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.

XanderDelores said:
Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.
Click to expand...
Click to collapse
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!

in_dmand said:
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!
Click to expand...
Click to collapse
Hmm.. interesting. The problem here is that this started on March 24th... :/ But, still trying Airplane mode, even though I'm not optimistic..
I emailed my provider, asking them for info, but a friend of mine has been working beside me for the past few days, on the same network with the same phone, without problem. So I guess it's time to bring it in..

Thanks for the info! I may try to put the latest rom/radio on it and see if that helps... if not i'll un-root it and send it in I guess.

I'm having a similar issue with my GSM model, It started when my phone was updated to 4.0.4. Phone signal suddenly drops and comes back again in less than 10 seconds. Sometimes it happens with 1 minute intervals between signal losses, sometimes 5 or 20 minutes, it's very random. After noticing the issue thanks to "Light Flow" that blinks the notification light in white when there is a signal loss, I installed this app (https://play.google.com/store/apps/details?id=com.smartandroidapps.missedcall&hl=en) to track it properly. The results are very frightening, I'm about to do a full wipe in hopes that the issue will be gone :|
ps: like you guys, I did notice that it's very most likelly to happen while the screen is off. Actually, it has never happened while the screen was on.

Same here, post 4.0.4 update on my GSM GNex.

Found this explanation....

[Q] Glide freezing up

Hello,
I've been experiencing annoying freezing up issues with my second-hand Glide. In all cases, the freeze happens with the screen off and a race condition ensues discharging the battery (even when plugged into power). Searching around, I've seen a good number of references to this problem:
androidforums.com/samsung-captivate-glide/462710-freeze-ups-anyone.html
gsmarena.com/samsung_i927_captivate_glide-reviews-4071.php
comparecellular.com/cell-phones/galaxy-s-glide
but I have not been able to find any resolution. Sometimes I feel like this: xkcd.com/979 . In essence I'm trying to determine if this is a hardware fault or something which can be fixed by software. Seeing minimal Glide development does not help since there are very limited options for ROMs. Since this device did get a nod for ICS, there's still hope in that, but until then have to suffer.
Anyone seen a resolution other than exchange? Warranty?

Unfortunately, this is quite common but there are few users that did not had any freezes since day one of their Glides.
One issue is, you have your Google calendar sync and you have "Auto Sync" active. This leads for the Calendar to Sync improperly during sleep mode resulting in a sync loop, which makes the device unresponsive thus, wont wake up upon pressing power/lock key. Solution, uncheck the "Auto Sync" function in Settings, Manually sync everything, or uncheck the "Sync Calendar on your Google account.
The other thing which is very common, is leaving wifi on while charging. This results on the same issue above but the reason is not clear. I experience this one in 1 out of 5 chances, so I turn wifi off or set the wifi sleep policy to "when screen turns off" in Settings. Happens on stock and custom ROM(s), except when Cranium Kernel is flashed.
In conclusion, I never thought that these are hardware issues ATM, for my previous Samsung devices also have these, but is eliminated by updating firmware, or flashing a custom ROM.

Thank you for the suggestions. I will verify wifi sleep policy as well as disable calendar sync to see if it helps. And now that there is some activity regarding ICS for this unit, maybe I'll get to test a new ROM to see if it helps.
thanks again

Neither unsynching google+calendars, or the WiFi+charging solutions worked for me.
Is there any hope for those of us with no immediate remedy?
Has Samsung even acknowledged that this is an issue?
When do you predict us getting an ICS update that will solve the issue?
Its a damn shame since I'm ****in loving this phone so far, yet i can't even use it when I want to sometimes.

Well yeah....I can confirm. I reflashed my device and restore my apps...did not do any mods and whatnot. Used it for a day and charged it overnight, no internet. And bam! Sleep Death. Like i said, this is common, and does not think that this is a hardware issue for a lot is experiencing it. So for now, dont left your glide charging overnight, or if you will, download a night clock, or use the stock desk clock. You will have a clock beside you and will keep your device awake all night.

Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?

wLnston said:
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
Click to expand...
Click to collapse
The issue you addressed is so called "sleep death." A few weeks past, ATT announced that 10 of their devices will get ICS in less than a month (including the Glide). No word from Rogers when will they update their version of the device.

Unfortunately AT&T did not state when they would push the update as well they only named the devices that will get it.

Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?

wLnston said:
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
Click to expand...
Click to collapse
I believe Samsung is already knowledgeable about the issue....unfortunately, it is not that easy to make a software update just to solve 1 problem (on the contrary to the Captivate SGH-I897 with GPS issues on Eclair, ATT immediately released a FW update within less than 2 weeks to fix it). And, even though I said the Sleep Death is quite common, not all of the users have this, so again, maybe unless a considerable large number of users (or all users) experience this, they might look into it. So I also believe that Samsung (along with ATT/Rogers) will correct the issue on the next update. When? Heaven knows.
If you are experiencing the sleep death more than twice a day, without doing anything, or if you believe non of your installed programs is at fault, and you are still in your return period, I suggest you exchange your device. You might get a unit that is unaffected. My Sleep Death only occurs when I left the phone charging for extended periods of time, like charging overnight which I always do. As I've mentioned, I keep the device awake like installing a night clock application or activating the stock desk clock app.

Well I'm going to try turning on the night clock app this night and see if that stops the sleep death.
And I bought the phone second hand off craigslist. Even if its within the 90-day period, I doubt I'll get any warranty/return ability as I am not the original customer.

interesting problem, will this should hold me back from buying it when my friends will be in the states?

taiber2000 said:
interesting problem, will this should hold me back from buying it when my friends will be in the states?
Click to expand...
Click to collapse
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day (on the contrary of the OP's post). In fact, my last sleep death was 10 days previous....it's been reliable and does the job.

gabby131 said:
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day. In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
Click to expand...
Click to collapse
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.

dudejb said:
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
Click to expand...
Click to collapse
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).

i have a therory about that, as some other user mentaioned when they useed adracat kernel (that is OC) the problem is gone. maybe samsung uses a underclocked tegra2 prossesor and that tha problem.

gabby131 said:
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
Click to expand...
Click to collapse
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.

dudejb said:
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
Click to expand...
Click to collapse
this is exactly what I am experiencing....and I can replicate this issue about 8/10 times....well this should hopefully be fixable via FW update (like my SGH-I896 from 2.1 to 2.2).
Yes I have CWMR installed and is very handy....I am now going back to flash OsiMood ROM for I think I already know what triggers the Sleep Death specially in stock ROMs....

Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!

wLnston said:
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
Click to expand...
Click to collapse
Some people have stated that once you install a Rooted Rom you will no longer get pushed the updated from your service provider. They stated this from Gingerbread 2.3.5 to 2.3.6
In order to go back to stock you have to somehow back up what you have before you flash anything or find it on the web. I am not sure about this but have heard of others doing this.
Your other option is use a ROM that someone cooks with ICS when it becomes available. I have heard of many people toying with getting this set up.

Post issues found in the ICS Leak (I927UCLG9)

its real nice to finally have some ICS goodness on my phone, but i have found some issues.
my Motorola Roadster 2 bluetooth speakerphone does not work well with this version of ICS. will not let me use the call/text button.
i am finding some apps not working correctly, i.e. Pushover - the notifications do not make a sound. Not sure if that is an app issue, or an ICS issue.
*edit* ok so it seems that i am not getting any notification sounds. sms, voicemail, etc...
also the volume in general does not seem as loud as the 2.3.6 firmware was.
anyone else find any issues?
*UPDATE* after wiping within cwmr most of my issues were no longer present. the only problem i had still was that notification sounds didnt work after a couple hours. i dont know the cause, but i used audio manager widget and set the profile to loud, and restarted phone. havent had them go out since.

I have all these issues except tue bluetooth thing
Sent from my SGH-I927 using xda premium

jayjayjoker2 said:
I have all these issues except tue bluetooth thing
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
atleast it is not me.
i am going to reflash my phone to see if it may be an issue with not clearing out the phones memory and storage first...

My wifi didn't work for a while. It would see my access point but wouldn't connect. Reset the router and everything went back to normal. GPS works, Stereo BT/OBEX works, 4G works, camera works. Those were my big items, as I'm sure they are most people's.
My only issues are that I can't switch to 2g (At&t rom....) and how friggin Touch-wizzy everything is. I was expecting them to embrace the whole holo thing a lot more, but all the buttons feel like they belong in GB, same with the notification menu and the settings icons.
EDIT: I am on rogers, in case any rogers people see this so they know that everything works on our network

i wiped via cwmr and reflashed the ics rom. notifications work again. have not rooted yet, wondering if that may have been an issue with it...

Changing the lcd DPI causes the rom to corrupt i guess, since when i do it, after the reboot, i get to the samsung "logo" and then black screen, and it feels like the device has shut down. The only app that would say "success" when i change the value is Lcd Density Modder.
- i had the notification sound bug, but then i changed the notification sounds to my likings, and then i used Audio Manager widget to set the volume loud, no problems ever since.

ok rooted and all is fine. maybe i just had a bad flash. my bluetooth speakerphone still doesnt work, but that is an issue that i will have to research

For me, i had the only issue with ICS (excluding the known thing with the keyboard not flashing) - timezones from 2011 year with wrong summer times.
Luckyly fixed it with timezone fixer from google play.

Tethering doesn't work, seems to be broken and results in a blackscreen.. Both Usb and Wifi Hotspot give this issue.. Anyone else getting this

One weird thing my phone does is when it's been asleep for a while, the lockscreen clock will fall behind and when I wake it up, it'll catch up a couple dozen minutes at a time.
~Azrael's Kiss~

Wifi is slooow, getting 800k when I should be getting 20mbs
Sent from my SGH-I927 using xda premium

My wifi still not working
Tyfighter said:
My wifi didn't work for a while. It would see my access point but wouldn't connect. Reset the router and everything went back to normal. GPS works, Stereo BT/OBEX works, 4G works, camera works. Those were my big items, as I'm sure they are most people's.
My only issues are that I can't switch to 2g (At&t rom....) and how friggin Touch-wizzy everything is. I was expecting them to embrace the whole holo thing a lot more, but all the buttons feel like they belong in GB, same with the notification menu and the settings icons.
EDIT: I am on rogers, in case any rogers people see this so they know that everything works on our network
Click to expand...
Click to collapse
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.

jvuong said:
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.
Click to expand...
Click to collapse
I've rogers version but unlocked and working with a local carrier. Wifi is not a problem at all, i'm getting the same speed and used wifi continuously for over 2 hrs to download all my apps back after the update.

When typing with the keyboard, pressing the alt. Key once makes it select all the special characters. I liked the older one where if you press it once, it operates just once when selecting the special character, and pressing it twice makes it select more than one. Not that big of an issue but to some people it may be.
Also, the brightness thing. When I turn off the screen, and turn it on again, it flashes from the highest brightness to the current.
Sent from my SGH-I927 using xda premium

jvuong said:
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.
Click to expand...
Click to collapse
On AT&T here, and having wifi issues as well... Once the phone drops wifi at idle, it doesn't want to pick it back up unless I turn wifi off and back on again. Setting the wifi to never sleep has been my only workaround.
Also having some issues with the button backlights. If I don't touch the phone long enough for the button backlight to turn off, touching the buttons won't turn the light back on. Touching the screen turns the backlight on again, but it's slightly annoying.

I haven't noticed any wifi issues and I use my Glide exclusively as a wifi device. I'm copying my backup of Inception v2 back right now though because the battery drain on the ICS ROM is definitely an issue. Losing like 10% an hour with my phone just sitting there with the screen off.

bobbinthreadbare said:
I haven't noticed any wifi issues and I use my Glide exclusively as a wifi device. I'm copying my backup of Inception v2 back right now though because the battery drain on the ICS ROM is definitely an issue. Losing like 10% an hour with my phone just sitting there with the screen off.
Click to expand...
Click to collapse
so weird everyone having battery problems. mine runs better than it did on stock 2.3.6 and the battery lasts longer....

inthepit said:
so weird everyone having battery problems. mine runs better than it did on stock 2.3.6 and the battery lasts longer....
Click to expand...
Click to collapse
Have you ever took note of your battery life with a custom ROM or kernel? When I picked up my Glide it had a stock ROM but I only had it for an hour before I put a custom on it. I didn't mess with the stock one at all so I can't compare to stock 2.3.5/6. But with Inception v2/ardatdat, it was definitely better.
I was going to restore my backup but copying it back to my phone made me realize how painful it is to copy backups with CWMR 6 compared to 5. That new blobs folder makes so many files that it took 3 hours to copy 3 of my backups over USB. Ouch.
But since last night, the battery life seems to be behaving better. Its been sitting here and not just dying. I'm wondering if it could be the battery stats file. Maybe I'll try wiping it. I'm sure once we get a lower voltage kernel and I can underclock with profiles for the screen-off and stuff, it'll be fine again.
Unrelated but has anyone taken a screenshot with the ROM yet? ICS is supposed to have it built in, power button + volume down at the same time for a few seconds from what I read, but didn't seem to work.
Edit: Its home + power button at the same time.

ninthsense said:
I've rogers version but unlocked and working with a local carrier. Wifi is not a problem at all, i'm getting the same speed and used wifi continuously for over 2 hrs to download all my apps back after the update.
Click to expand...
Click to collapse
Damn i hope its not my phones wifi:crying:

bobbinthreadbare said:
Have you ever took note of your battery life with a custom ROM or kernel? When I picked up my Glide it had a stock ROM but I only had it for an hour before I put a custom on it. I didn't mess with the stock one at all so I can't compare to stock 2.3.5/6. But with Inception v2/ardatdat, it was definitely better.
Click to expand...
Click to collapse
when you flashed ICS did you wipe everything then run the ics installer? my first install sound and such didnt work, so i wiped the phone in cwmr and reflashed ics and it is better that it was on 2.3.6

[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…)