Develop Bugs

Sleep of death?

Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk

I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.

Evostance said:
Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.

mskip said:
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.
Click to expand...
Click to collapse
Good point.
Wonder what app it is

Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium

SweetPAIN225 said:
Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off

Thanks! I made a wrong assumption!
Sent from my Galaxy Nexus using xda premium

Evostance said:
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off
Click to expand...
Click to collapse
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App

matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Exactly, it is way way too likely that turning your CPU down will result in 'Sleep of death'

matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well its still worth noting. SetCPU never did this on my DHD

I had exactly the same thing last night, I even made my own thread
http://forum.xda-developers.com/showthread.php?t=1360847&page=2
I even wrote a simple app for logging the battery temperature and time, so I'll leave it on next night and I'll see what happens. Because I'm pretty sure my phone switched off due to overheating, as it was really,really hot in the morning, after I switched it on the battery was at 46C.

I'm afraid I can confirm that I have experienced the same "sleep of death" problem twice now. I can't remember what I was doing the first time, but the second time I was only browsing and I know I didn't have any apps installed because I had previously reset my phone. I've only had the phone for two days now and if it does it again I might have to send it back.
I expected a glitch or two, but with the volume bug and other annoying things like the lack of flash and poor camera quality, I'm beginning to regret my purchase. Although I love the ice cream sandwich experience, I'm now thinking of getting the Galaxy Note instead, and waiting for ICS to arrive on that next year. At least then I will be able to watch iPlayer in the meantime.

Mines done it about 4 times. Pre installed Movie maker seems to induce it.

Rawkode said:
I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.
Click to expand...
Click to collapse
Had a sleep of death for the first time yesterday - the only "different" thing I did during the day was use spotify so there maybe something in that!

Same again last night, woke up this morning and phone was on but wouldn't wake. Notification light was on solid. Was plugged in at wall all night, didn't seem too warm when I held it.
Time to start debugging I guess

I've had this issue twice too.
I do not have spotify installed, and the phone was NOT hot at all. Not even warm!
I was just in gmail, sent a mail, then pressed the home button, and black.... gone.
Had to pull battery.
Thinking of having phone replaced by Handtec. I know this is probably a software glitch, but the volume bug, and the fact my unit was one that handtec had "tested" etc, I might just ask for a brand new one from the new flashed batch due next week.

Wtf! Just how wide spread is this??? Seems like too many people are having this issue.
Phone hasn't even arrived yet and I'm already starting to question my purchase.

1 more bug and im cancelling my order !

Well, it's the first device with ICS so I expect there will be a few bugs in the future which will need to be fixed. That's the reason why I'll go for the Nexus ... it's a nice piece of hardware but even more important is that it will be the device which gets the fixes first.

Did anyone check to see if you've had an OTA for the volume ghost fix and this problem has spawned instead? Seems like a fairly new problem if you have followed the forum.
Sent from my X10i using xda premium

Defective Touchscreen?

Hey
I had some issues with the Touchscreen of my GNex, i thought it was nothing special, because i had something similiar on my xoom too but it only occurred 1 time on it.
Then i've tested the GNex for some Days and i'm now very sure it's a hardware defect, but i want to know what you think of it.
I'll try to describe it a bit:
Sometimes (i sadly don't know when or why) it launches a line of touch-inputs rapidly on the right side of the screen. It's really annoying because it starts a bunch of apps or commands...it even shuts down my alarm in the morning sometimes.
The big problem is, i'm on Vacation for 2 weeks soon...means i can't give it back to warranty now...maybe there is a way to disable the sensetivity of the touchscreen because these inputs are very light. With a testapp i was able to see that it's half as "heavy" as when i tap the screen with a finger.
I've attached a vid of it, maybe someone could say if this happens on their GNex too...i doubt no. (The vid is not that good, please apologize)
Link: http://goo.gl/QnTy7 (Sorry Attachment doesn't work somehow)

No one out there with a idea what's wrong with my gnex? :-(

I would go to verizon and see if there is anyway they could give you a replacement considering your circumstances. Or maybe they would give you a loaner phone while yours is being serviced.

Does it look a bit like this behavior?
https://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium

I would get a replacement phone from T-Mobile but that would be a real old phone and I have a nexus s here so maybe use this.
But would be nice to know if it's a hardware defect or if it's fixable....
I'll try to exchange it after my vacation.
Yes it's the same behaviour as in that video. I uploaded one too in the first post and mine is only a bit more right on the screen...
I'm really disappointed because my nexus s has some defects too and I'm curious if all Google devices has some defects....
Thanks for the answers

0 defects on my Nexus S
0 defects on my Galaxy Nexus

damn thats gotta suck :s
maybe flash any custom rom? hope you have your bootloader unlock or any pc close

I'm using CM9 since I got the GNex, will try reflashing it tomorrow with full wipe. Will report then.
Hope it's only the ROM, the screen works perfectly aside from this.

I didn't know you were running I custom rom, I would definitely try and do a full wipe and load the rom again or a different one.

The problem on my gnex went away after the ota update from 4.0.1 to 4.0.2.
Sent from my Galaxy Nexus using xda premium

Petrovski80 said:
The problem on my gnex went away after the ota update from 4.0.1 to 4.0.2.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm using CM9, latest nightlys. Did a full wipe and reflashed from scratch, same problem... maybe try stock or other rom when i'm back home..

Proximity sensor issue..

Okay so I've had this issue on every jb ROM and Franco and Trinity kernel. Idk what else to do.
Proximity sensor doesn't work on the phone. But shutting the screen on and off works during phone call using the power button.
Downloaded an app. It recognizes the sensor and says I have one.
Proximity sensor works for a little while when I reset it by pulling the battery. Then it randomly stops working again until I pull the battery and do another reset.
What should I do? It's really annoying. The fact it works up until a certain uptime of me using the phone and such makes me think maybe something's conflicting with it? No screen protector is on blocking BTW.
I do have Verizon insurance and my phones under warranty. But I'd rather not... because nexus is banned. And I don't want a g3
Sent from my Galaxy Nexus using Tapatalk 2

does it happen on ICS? if the answer is no, go back to stock and wait for the official JB from VZW

I don't know. I rooted day 1
Sent from my Galaxy Nexus using Tapatalk 2

imablackhat said:
I don't know. I rooted day 1
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
then go back to stock ICS and see

Meh. I'd prefer not to have to revert entirely back to stock. Seeing his other people I know are on the same phone and ROM don't have this issue
The light sensor works. Is that build into proximity sensor or separate. ?
Sent from my Galaxy Nexus using Tapatalk 2

One thing to consider is that the proximity sensor only makes the screen turn off if the phone is held in an upright, vertical orientation. If held horizontally, the screen won't turn off during calls when the sensor is covered. No idea why this is, but maybe they assume that if you're holding the phone horizontally you're doing something with the sceen rather than holding it up to your ear, and thus the screen doesn't turn off if your hand gets too close to the sensor?
Anyway, are you positive this isn't what's going on?

Held up right. Put up to your ear or put hand over nothing happens. But when I pull the battery and reset the sensor it works flawless for a little while.
Sent from my Galaxy Nexus using Tapatalk 2

imablackhat said:
Meh. I'd prefer not to have to revert entirely back to stock. Seeing his other people I know are on the same phone and ROM don't have this issue
The light sensor works. Is that build into proximity sensor or separate. ?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i gave you a solution to see if its the phone or the rom/kernel. if it happens on stock, get a replacement. otherwise.. deal with it, or stick to ICS for now.

imablackhat said:
Meh. I'd prefer not to have to revert entirely back to stock. Seeing his other people I know are on the same phone and ROM don't have this issue
The light sensor works. Is that build into proximity sensor or separate. ?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No one is saying you need to unroot your phone. They are saying that the way to see if there is a problem with your sensor or phone is to check it against the stock image. Make a NAND backup, revert to stock and test. Once you have an answer, restore from backup to your favorite ROM.
If this keeps occurring on stock, then you have a warranty case.

Is there an easy way to completely disable the sensor. I'd rather have it like that so I can turn the screen on and off during phone calls vs rely on something that doesn't work.
Sent from my Galaxy Nexus using Tapatalk 2

imablackhat said:
Is there an easy way to completely disable the sensor. I'd rather have it like that so I can turn the screen on and off during phone calls vs rely on something that doesn't work.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Why wont you just make a Nandroid Backup in CWM and try a stock ICS ROM as was mentioned to you to try? You have nothing to lose by doing this and you can go right back to where you are now once you try it by restoring your Nand. At least then you will know for sure if its ROM related, possible Hardware issue, etc and THEN you can dig deeper from there.
Start at step one my friend and dont try to jump directly to step 10. Remember... Rome wasnt built in a day...

imablackhat said:
Okay so I've had this issue on every jb ROM and Franco and Trinity kernel. Idk what else to do.
Proximity sensor doesn't work on the phone. But shutting the screen on and off works during phone call using the power button.
Downloaded an app. It recognizes the sensor and says I have one.
Proximity sensor works for a little while when I reset it by pulling the battery. Then it randomly stops working again until I pull the battery and do another reset.
What should I do? It's really annoying. The fact it works up until a certain uptime of me using the phone and such makes me think maybe something's conflicting with it? No screen protector is on blocking BTW.
I do have Verizon insurance and my phones under warranty. But I'd rather not... because nexus is banned. And I don't want a g3
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You aren't the only one who has experienced this. I had the same thing happen to me. I think it was a piece of dust in there causing it to malfunction. I reflashed the stock rom, and a couple others. I even tested it with a couple of apps, etc. Just out of the blue it randomly started working again! It happened several months ago, just once, and has been behaving normally ever since - beats me!! ::knocks on wood::
Edit:
Since when is the nexus banned??? It is back up for sale now as far as I know - it's available on Google's Play Store. Try lightly shaking the phone to see if it jolts any specks of dust out of the way of the sensor under the glass.

This is kind of why I'm against going back ICS. Plus my friend has the same phone and has followed me to every different jb ROM and doesn't share this same issue..
I did recently today pull the battery for a minute and let then phone sit to reset the proximity sensor this works every time. Now I'm at 5 hours uptime. When it stops working again that's when I'll try your shake method.
I do have apps to also test the sensor. And right now it works perfect. Clearly. Because I just calibrated it. It usually messes up within a 12 hour period.
If its dust in there. Don't you think the phone would stay off and not wake up seeing how its blocking the sensor
I really don't want to go back ICS. I'm hooked on paranoid android. And every ROM shares the same issue. And its not like I can just flash ICS to test it seeing how it takes a while for something to mess it up
Maybe there's an app conflicting with it?
Sent from my Galaxy Nexus using Tapatalk 2

After 14 hours uptime it doesn't work again. But now my light sensor works. Using android sensor box. Its either one or the other works. I know everyone is going to say just install stock ICS and see if it does the same thing... -_- i dont have a ics stock backup. The shaking method because of dust possibly didn't work either.
Sent from my Galaxy Nexus using Tapatalk 2

imablackhat said:
After 14 hours uptime it doesn't work again. But now my light sensor works. Using android sensor box. Its either one or the other works. I know everyone is going to say just install stock ICS and see if it does the same thing... -_- i dont have a ics stock backup. The shaking method because of dust possibly didn't work either.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where did you buy the phone? If you have warranty, you can just get it replaced

imablackhat said:
This is kind of why I'm against going back ICS. Plus my friend has the same phone and has followed me to every different jb ROM and doesn't share this same issue..
I did recently today pull the battery for a minute and let then phone sit to reset the proximity sensor this works every time. Now I'm at 5 hours uptime. When it stops working again that's when I'll try your shake method.
I do have apps to also test the sensor. And right now it works perfect. Clearly. Because I just calibrated it. It usually messes up within a 12 hour period.
If its dust in there. Don't you think the phone would stay off and not wake up seeing how its blocking the sensor
I really don't want to go back ICS. I'm hooked on paranoid android. And every ROM shares the same issue. And its not like I can just flash ICS to test it seeing how it takes a while for something to mess it up
Maybe there's an app conflicting with it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I will say this.. mine mucked up using Paranoid Android - coincidence, I have no idea? That was back when PA was ICS based though. The apps I used to test the sensor always showed the sensor as being blocked if I remember correct. When I made a phone call the screen would never turn off. The funny part is that if I tapped around the sensor lightly or lightly shook the device it would cause the screen to flicker a few times randomly. After flashing a few roms (ended up sticking with CM9), it just randomly started working again. I can't make any rhyme or reason from it.

What cm are you using can you link? I just tried cm 10 king build
Sent from my Galaxy Nexus using Tapatalk 2

imablackhat said:
What cm are you using can you link? I just tried cm 10 king build
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It was CM9 that i used. I'm currently on stock Jelly Bean w/ trinity kernel.

Cm9 rc1 rc2? They still make nightly for 9 don't they? When 10 is out? Idk I'm confused
Sent from my Galaxy Nexus using Tapatalk 2

I'm having this issue right now with stock rooted Jelly Bean.
I never tried ICS because I only have few weeks with the phone and went straight away to JB.
I think it's a combination of faulty hardware and software because by using "Proximity Sensor Finder" app I can tell the sensor is not working. BUT, if I turn the phone off (not battery pull, just power off by holding power button) and turn it on, the sensor it's working again. So, I can tell that it's something when the uptime reaches some hours that the sensor stops working.
Maybe, something on the hardware side triggers this behavior in the software side, I don't know.
In conclusion, I just need to power off the phone and turn it on again and the sensor works.
Cheers!

Random Airplane mode?

Hey every one. My wife has a totally stock Note 2. Its fully up to date from the last OTA. Its actually a warranty exchange since her first hand sets microphone stopped working..
So since yesterday her device has been randomly gong into airplane mode.. You can turn it off but it will switch back again in just a few minutes. She has had it just over a week and this just started yesterday.
She barley has any apps installed. And hasn't downloaded aided anything has permissions for changing that state..
I factory reset it. But that doesn't seem to have helped.
Any ideas? Should we just exchange it again?
Sent from my Nexus 4.

OK.. I see you guys are real helpful over here..
I just exchanged it.
Sent from my Nexus 4.

PJcastaldo said:
OK.. I see you guys are real helpful over here..
I just exchanged it.
Sent from my Nexus 4.
Click to expand...
Click to collapse
50 minutes might be a bit small for a time window to judge helpfulness... that being said I would say you made the right call. It definitely should not be doing that, and it seemed you already ruled out any sort of app or custom tinkering that may have driven such odd behavior. Hope the "third time's the charm" idiom holds for you on this one!

dwitherell said:
50 minutes might be a bit small for a time window to judge helpfulness... that being said I would say you made the right call. It definitely should not be doing that, and it seemed you already ruled out any sort of app or custom tinkering that may have driven such odd behavior. Hope the "third time's the charm" idiom holds for you on this one!
Click to expand...
Click to collapse
Haha yeah.. I'm impatient..
And I hope so. I consider this phone to be a top dog device.. Of it goes wrong again I might just have T-Mobile switch her to something different.
Sent from my Nexus 4 using xda app-developers app

Touch Issues

I've had my nexus for a while now and as much as I enjoy using it there is a really big issue that keeps coming back. The touch sensitivity on my screen is terrible. It won't recognize half of my touches from time to time and its really frustrating. I have tried fixing it using the ts files and will work for a while then it will start with its issues again.
I also flashed almost every ROM I could think of trying to see if i t fixed the issue however it did not. I always flashed the unlock for the ts after so it would not stick in the new Roms hoping that it would get better. I have also done a full factory reset and wipe without any luck. Currently I'm running Android L lpv81( the second release) and I'm not ropted. I was using 4.4.4 with twrp earlier but it doesn't matter as long as I can get this touch issue fixed.
I looked around the forum for a while and used every fix I could find but none lasted long enough for me to enjoy it. I would really appreciate any help with this, I'm not afraid to mess around with some things to fix this issue.

My stock one year old Nexus will also occasionally not respond to my touch. Not enough to be really annoying.
Sent from my Nexus 7 using XDA Free mobile app

lmacmil said:
My stock one year old Nexus will also occasionally not respond to my touch. Not enough to be really annoying.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It happens more often than not, in fact its enough to make typing hard and or frustrating at times. I have a feeling that it's a hardware issue, but unless there's a fix I'll just had the nexus 8 when our comes out.

Pilz said:
It happens more often than not, in fact its enough to make typing hard and or frustrating at times. I have a feeling that it's a hardware issue, but unless there's a fix I'll just had the nexus 8 when our comes out.
Click to expand...
Click to collapse
Some people just can't afford to pay for every new device out there and have to deal with a malfunctioning device or try to fix it.
We're so lucky we have a community behind us that solves our problems.
Here you are:
http://forum.xda-developers.com/showthread.php?t=2428133

Pilz said:
I've had my nexus for a while now and as much as I enjoy using it there is a really big issue that keeps coming back. The touch sensitivity on my screen is terrible. It won't recognize half of my touches from time to time and its really frustrating. I have tried fixing it using the ts files and will work for a while then it will start with its issues again.
I also flashed almost every ROM I could think of trying to see if i t fixed the issue however it did not. I always flashed the unlock for the ts after so it would not stick in the new Roms hoping that it would get better. I have also done a full factory reset and wipe without any luck. Currently I'm running Android L lpv81( the second release) and I'm not ropted. I was using 4.4.4 with twrp earlier but it doesn't matter as long as I can get this touch issue fixed.
I looked around the forum for a while and used every fix I could find but none lasted long enough for me to enjoy it. I would really appreciate any help with this, I'm not afraid to mess around with some things to fix this issue.
Click to expand...
Click to collapse
It's a hardware problem. RMA if possible.
If not possible, try the TS drivers that the above post likely links.

Aerowinder said:
It's a hardware problem. RMA if possible.
If not possible, try the TS drivers that the above post likely links.
Click to expand...
Click to collapse
I might have to RMA it, I've already tried all of the ts drivers. Do I send it to Asus?

Pilz said:
I might have to RMA it, I've already tried all of the ts drivers. Do I send it to Asus?
Click to expand...
Click to collapse
I sent mine to Google.

Aerowinder said:
I sent mine to Google.
Click to expand...
Click to collapse
Is there a link to where I get the info the the RMA process? I tried googling it, but it wasn't very helpful.

Pilz said:
Is there a link to where I get the info the the RMA process? I tried googling it, but it wasn't very helpful.
Click to expand...
Click to collapse
It's been a while since I did it, but I think you start here: https://support.google.com/googleplay/answer/2411741?ref_topic=3237699/#ts=4626603,4626497