EDIT: This failed, just ignore...
If you're like me, you sometimes pickup your phone and it's stuck at the boot animation and the animation is grayish.
Well I think that this problem as nothing to do with custom rom or custom kernel but in fact is a Nexus S hardware issue. I think that when the NS reach a certain temperature the CPU stop intentionally so no damage is done to the phone. The problem is that when the CPU stop, the phone reboot but at boot uses a lot of CPU than overheats again than just get stuck in a reboot loop. That's my theory.
I also think that the problem comes from the NFC antenna. The rubbery texture of the NFC antenna seems to keep the heat in the handset.
So to try to fix the problem, I added a copper plate between the NFC antenna and the battery to try to dissipate the heat. The result, my NS runs a good 4C less than it use too and I haven't had a reboot loop yet.
If you have reboot loop problems, try a similar solution and let me know if it fix it for you...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloops commonly happen from too much undervolting, unstable overclock, phone/battery gets too hot. Looks interesting though. NFC still work?
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Bootloops commonly happen from too much undervolting, unstable overclock, phone/battery gets too hot. Looks interesting though. NFC still work?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm taking off undervolt and overclock out of the equation because I assume that someone has tested those thoroughly before setting them at boot.
I'm focusing on the fact that when your OC/UV is stable, you shouldn't have boot loops. I even think that some ppl are experiencing bootloops with stock kernel which has no OC/UV ...
As for NFC, it still works! I've been running my phone 4 days strait without any reboot and the phone definitely feel cooler to the touch. Temperature never went higher than 35 Celcius. My phone used to be constantly at 37+ Celcius.
Interesting information thanks for the insight.
Sent from my Nexus S
p00kienrayray said:
Interesting information thanks for the insight.
Sent from my Nexus S
Click to expand...
Click to collapse
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
steve.garon said:
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
Click to expand...
Click to collapse
i dont think its a heat issue because ive got my ns up to 123F without a problem, without a bootloop. and i regularly run at 105-115F torturing my phone testing out kernels.
steve.garon said:
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
Click to expand...
Click to collapse
Try the oxygen rom. I haven't encounterd a boot loop or random reboot since switching to oxygen. Use to get bootloop or random reboot several times a day with cyanogen rom.
Sent from my Nexus S using XDA App
No bootloops with cm7 latest nightly and netarchy
Sent from my Nexus S 4G using xda premium
Related
I've had my Nexus 4 16GB for almost a month with no problems.
I plugged in my phone and went to shower for 10 minutes.
When I came back, I turned on the screen, and now I have a constant dim flickering over my entire display!
I've restarted twice and the problem persists.
How can I determine if this is a software or hardware issue?
If it is a hardware issue, do I have to remove the root (done about a week or 2 ago) before I send it to Google for a replacement?
Likely software. Some other phones I've had have also had screen flicker. If you do RMA it and it turns on and boots you should probably unroot and relock the boot loader.
Sent from my Nexus 4 using Tapatalk 2
Aoude. said:
I've had my Nexus 4 16GB for almost a month with no problems.
I plugged in my phone and went to shower for 10 minutes.
When I came back, I turned on the screen, and now I have a constant dim flickering over my entire display!
I've restarted twice and the problem persists.
How can I determine if this is a software or hardware issue?
If it is a hardware issue, do I have to remove the root (done about a week or 2 ago) before I send it to Google for a replacement?
Click to expand...
Click to collapse
Try flashing another ROM and see what happens. (Make a android backup first). To send it back to Google you're going to need to revert back to stock.
Sent from my Nexus 4 using xda app-developers app
Update for anyone who might get this problem randomly. I turned the phone of for a little while and then turned it back on and it was fine. I've since switched from stock to CM10.1, and it's still fine.
Sent from my Nexus 4 using xda app-developers app
Aoude. said:
Update for anyone who might get this problem randomly. I turned the phone of for a little while and then turned it back on and it was fine. I've since switched from stock to CM10.1, and it's still fine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Strange, I've got the exact same issue right now... flickering is present in recovery/boot so I thought it maybe hardware failure.. will try CM10 instead of MCR once I've backed up! For reference:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you have something like this too? Did you wipe when to fix the issue?
r5ingh said:
Strange, I've got the exact same issue right now... flickering is present in recovery/boot so I thought it maybe hardware failure.. will try CM10 instead of MCR once I've backed up! For reference:
Did you have something like this too? Did you wipe when to fix the issue?
Click to expand...
Click to collapse
That's not exactly what mine looked like, the flicker was more of a flashing of the entire screen. That very well could be a hardware issue, but don't take my word for it. I never flashed a ROM or wiped anything to fix the problem. I simply turned the phone off a few times for around 10 or 15 minutes each time, and I just didn't see any more flickering. Hope yours can be fixed this way too
Doesn't look like it, I left it off for about 6 hours, still pretty stuffed. This is definitely hardware... looks like my night just went from bad to worse. :/
Oh that sucks
Hopefully you can get a replacement quickly.
Good luck
Sent from my Nexus 4 using xda app-developers app
Hi all
Hope someone can help with this problem.
Tonight my phone just randomly turned off. I wasn't doing anything strange..just texting. I sent a text and placed my phone down. Looked at it and hour and half later and it wasn't responding. I held down power and it powered on but noticed my battery dropped quite a bit.
I'm bone stock 4.2.2, no root and locked boot loader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
Mysteries like this one are not uncommon.
Text message couldn't be sent, phone kept re-trying, got hot, turned off?
Signal loss, connection derp, overheating, turned off?
Who knows. I'd lean towards overheating..
If it's only happened once, what's the issue? It could have restarted for a multitude of different reasons but if it's not doing it on a regular basis then it's not really an issue in my eyes.
Mine did this for the first time today after 2 and 1/2 months of flawless performance too. Really weird, wouldn't respond to any buttons,charger, or USB cable. No red flashing LED. Battery was at about 50%. Wasn't doing anything with it beforehand, it was asleep.
After about 15 minutes of nothing, it recognized the charger and booted back up.
Jim Beam5 said:
If it's only happened once, what's the issue? It could have restarted for a multitude of different reasons but if it's not doing it on a regular basis then it's not really an issue in my eyes.
Click to expand...
Click to collapse
I'm more concerned about the battery. Why the sudden drop off from 90% to 70%
Sent from my Nexus 4 using Tapatalk 2
SeraldoBabalu said:
Hi all
Hope someone can help with this problem.
Tonight my phone just randomly turned off. I wasn't doing anything strange..just texting. I sent a text and placed my phone down. Looked at it and hour and half later and it wasn't responding. I held down power and it powered on but noticed my battery dropped quite a bit.
I'm bone stock 4.2.2, no root and locked boot loader.
View attachment 1769700
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I think the 4.2.2 OTA may have corrupted the battery stats file for some users.
I had a similar thing happen where it went from 30% then dropped to 2% after a simple reboot.
Based on my usage at that time, I should have had a lot less than 30%.
Now if your phone gets unusually HOT, you have bigger issues and may end up with the RED light of death
See this post for more info:
http://forum.xda-developers.com/showthread.php?t=2166250
SpookyTunes said:
I think the 4.2.2 OTA may have corrupted the battery stats file for some users.
I had a similar thing happen where it went from 30% then dropped to 2% after a simple reboot.
Based on my usage at that time, I should have had a lot less than 30%.
Now if your phone gets unusually HOT, you have bigger issues and may end up with the RED light of death
See this post for more info:
http://forum.xda-developers.com/showthread.php?t=2166250
Click to expand...
Click to collapse
phone gets warm but not hot. usually when i'm watching a video it'll get warm.
My issue was different, no heat or battery issues. Was at about 50% when it blanked out and 48% by the time it came back.
If phone becomes hot, theres a defense mechanism in which our kernel will make phone run at lower clocks which eventually gets our phone into sleep of death. So try one thing. If ever ur phone gets hot, dnt lock the screen and keep it on a cold surface, and once it get cold, press the lock button. See the diff!!
Sent from my Nexus 4 using xda app-developers app
thx everyone. i'll wait it out and see if it happens again.
if it does, i'll flash a fresh stock image.
SeraldoBabalu said:
thx everyone. i'll wait it out and see if it happens again.
if it does, i'll flash a fresh stock image.
Click to expand...
Click to collapse
Hopefully not! If you do, follow the guide in my signature.
just for good measure, i went back to bone stock 4.2.1 and installed the 4.2.2 update when it got pushed through and the same thing happened again. i didn't even install any apps - just what was in the factory google image. i was just lightly texting, locked my phone and looked at it a few mins later and it was off. this time my battery didn't change and i took notice of the temp of the phone and it was cool.
this only happened after the 4.2.2 update as for the couple of months of 4.2.1, i never had this issue. i've only had stock 4.2.2 for a little over a week.
i'm going back to stock 4.2.1 or maybe will try out a custom. if it does this on 4.2.1 stock, it's gotta be a h/w defect but i'm pretty confident it won't.
thx again all for your suggestions and help.
Running aokp with stock kernel, also paranoid android before and it did this. Any help or ideas to fix these spikes? Battery reading has gone crazy and obviously it's not charging but it bumps up the battery level though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4
KCuadrado said:
Running aokp with stock kernel, also paranoid android before and it did this. Any help or ideas to fix these spikes? Battery reading has gone crazy and obviously it's not charging but it bumps up the battery level though
Sent from my Nexus 4
Click to expand...
Click to collapse
What the hell??? Ok, u have to charge the phonte till 100% and then delete the file:
Code:
data/system/[B]batterystats.bin[/B]
Use the phone normally for a couple of days and report if the problem persists.
KCuadrado said:
Running aokp with stock kernel, also paranoid android before and it did this. Any help or ideas to fix these spikes? Battery reading has gone crazy and obviously it's not charging but it bumps up the battery level though
Sent from my Nexus 4
Click to expand...
Click to collapse
Clear Dalvik + cache and let it charge to 100%. OR charge it while the phone is off and do a battery cycle.
luiseteyo said:
What the hell??? Ok, u have to charge the phonte till 100% and then delete the file:
Code:
data/system/[B]batterystats.bin[/B]
Use the phone normally for a couple of days and report if the problem persists.
Click to expand...
Click to collapse
sigma392 said:
Clear Dalvik + cache and let it charge to 100%. OR charge it while the phone is off and do a battery cycle.
Click to expand...
Click to collapse
Thanks guys. The batterystats.bin file didn't work, also it's a new fresh install of AOKP so the whole data partition got wiped before installing. I think the battery got fried because it's way too hot where I live and the phone heated some times way more than normal.
I'm trying the charge withouth powering on now to see if it cures the problem.
KCuadrado said:
Thanks guys. The batterystats.bin file didn't work, also it's a new fresh install of AOKP so the whole data partition got wiped before installing. I think the battery got fried because it's way too hot where I live and the phone heated some times way more than normal.
I'm trying the charge withouth powering on now to see if it cures the problem.
Click to expand...
Click to collapse
Battery cannot get fried at room temperature.Ok does the battery charge linearly?
ashishv said:
Battery cannot get fried at room temperature.Ok does the battery charge linearly?
Click to expand...
Click to collapse
With the phone powered off it didn't charge. If I turn it on it says 0% and then it ramps it up to 22 or any other value higher than what I think it really is. That's the spikes on the screenshot
KCuadrado said:
With the phone powered off it didn't charge. If I turn it on it says 0% and then it ramps it up to 22 or any other value higher than what I think it really is. That's the spikes on the screenshot
Click to expand...
Click to collapse
Did u try to wipe dalvik/cache? Flash another ROM then and try again. If that doesn't work then ur battery is fried...
luiseteyo said:
Did u try to wipe dalvik/cache? Flash another ROM then and try again. If that doesn't work then ur battery is fried...
Click to expand...
Click to collapse
I believe it is. It doesn't charge, and it's not even hot but look what it says
Sent from my Nexus 4
KCuadrado said:
I believe it is. It doesn't charge, and it's not even hot but look what it says
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, I would say it's broken
Update: I opened the phone, cleaned the battery cable and reconnected it and it is working way better than when it was new. Battery definitely lasts longer
Sent from my Nexus 4
This suddenly happened on my phone this Eve of Christmas. It was never dropped, wet nor bent.. It just happened while I was trying out voicemate. I think this is not software related as it is the same when I'm in recovery mode. Sometimes the display is correct and is not garbled but after a few seconds of touching it it acts this way again, if I try to turn off the screen it goes away but returns immediately after. Sometimes the screen won't turn on but I can feel that it is actually on thru the vibration feedback it is giving when trying to press randomly in the screen. I'm still going to try to revert to stock Rom as I am on rayglobe and rooted in case I need to send it in for warranty. I have already reflashed the Rom but still the same.. I just can't believe this is happening hours before Christmas and a few days before the new year.. I'm sure repair services of LG will take time.. Coincidentally, last year when I was using Samsung S3, the motherboard of the phone broke down on New Year's Eve..
Any thoughts what part of the hardware is failing? And what else can I try to troubleshoot before bringing this is to repair? Appreciate your comments. Thank you!
Charles
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk
guys any thoughts what caused this?
upon observation, this is more of a heat issue. if the unit is rested in a cold place it takes more time before the screen gets distorted like this but after a while of having the screen on it starts acting like this.. i hope LG repairs this fast!
Sent it for repair man,nothing else you can do as it seems.I wanted to ask if you had it modded or something,to see if there was something that caused it.But it seems the hardware is failing.
Definitely faulty hardware. Have it sent in for repairs. Looks like a faulty flex cable. Or it could be the main board though.
Sent from my LG-D801 using Tapatalk
This just happened to me
reycharlesconrad said:
This suddenly happened on my phone this Eve of Christmas. It was never dropped, wet nor bent.. It just happened while I was trying out voicemate. I think this is not software related as it is the same when I'm in recovery mode. Sometimes the display is correct and is not garbled but after a few seconds of touching it it acts this way again, if I try to turn off the screen it goes away but returns immediately after. Sometimes the screen won't turn on but I can feel that it is actually on thru the vibration feedback it is giving when trying to press randomly in the screen. I'm still going to try to revert to stock Rom as I am on rayglobe and rooted in case I need to send it in for warranty. I have already reflashed the Rom but still the same.. I just can't believe this is happening hours before Christmas and a few days before the new year.. I'm sure repair services of LG will take time.. Coincidentally, last year when I was using Samsung S3, the motherboard of the phone broke down on New Year's Eve..
Any thoughts what part of the hardware is failing? And what else can I try to troubleshoot before bringing this is to repair? Appreciate your comments. Thank you!
Charles
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Hey mate, this just happened to me
i was wondering how you went about fixing it. Did you sent it to the repair centre.
rakinisbat said:
Hey mate, this just happened to me
i was wondering how you went about fixing it. Did you sent it to the repair centre.
Click to expand...
Click to collapse
So what did you end up doing? This just happened to me as well.
Just happened the same to me, did you fix it? what was it?... My observation is that when it's charging the screen stabilizes
Hey guys. I know XDA is filled with battery threads, and I've done numerous searches around the forums and across the internet. Nothing seems to be helping me.
Recently, the battery life on my Nexus 4 hasn't been so great. I've attached a few screenshots of GSAM. Any ideas on what is causing the significant drain? I'm down 15% in 1 hour and have barely touched my phone. Using stock 4.4.2, rooted with some Xposed modules (none of which seem to correlate to being installed near the time of the battery life becoming crap).
Here is a dump from GSAM as well: https://www.dropbox.com/s/z6uo3q5059mcwhu/02-26-14.txt
Edit 2: After just over 4 hours, I'm down to 50% with a ton of wakelocks. This is the part that I can't find any helpful info about. Here's the new log: https://www.dropbox.com/s/tv01k9tbmo38gbv/02-26-14 2.txt
Edit: Trying to fix the images yet again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4
Shot in the dark but have you tried a battery calibration app?
Bilge656 said:
Shot in the dark but have you tried a battery calibration app?
Click to expand...
Click to collapse
You know, I haven't ever on this device. I had on my Samsung Captivate and Nexus S, but have yet to use any sort of battery calibration on my Nexus 4. And now that you mention it, I've had some strange behavior with going from 35% to 25% rapidly, rebooting, and then having it at 30%.
Do you think it's worth a shot? If so, any good apps for this? When I did it on old devices, I just used the CWM option to delete battery stats and then charged/discharged fully. Seems that TWRP (which I have installed) doesn't have this option.
jwkicklighter said:
You know, I haven't ever on this device. I had on my Samsung Captivate and Nexus S, but have yet to use any sort of battery calibration on my Nexus 4. And now that you mention it, I've had some strange behavior with going from 35% to 25% rapidly, rebooting, and then having it at 30%.
Do you think it's worth a shot? If so, any good apps for this? When I did it on old devices, I just used the CWM option to delete battery stats and then charged/discharged fully. Seems that TWRP (which I have installed) doesn't have this option.
Click to expand...
Click to collapse
Follow this app's instructions - https://play.google.com/store/apps/details?id=com.nema.batterycalibration
Bilge656 said:
Follow this app's instructions - https://play.google.com/store/apps/details?id=com.nema.batterycalibration
Click to expand...
Click to collapse
Thanks a lot, hopefully this works!
what the app does it deletess batterystats.bin
but google already stated that its just placebo, this file is only for the batteryicon
thats why cwm removed it.
second those wakelocks are just seconds. so its normal
third. do you have any sync service?(skype,facebook,email, or even google) if so
try disabling temporaly
if dosent work you may wanna try the xposed + xposed module called disable critical shutdown
then wait till phone turns off and charge for minimum 8hours
if not
change rom/kernel
if still not
its your battery(if so, and you still have warranty, you can get an rma if you live in a google area or get money back if you live in a area where lg controls,or buy another battery
opssemnik said:
what the app does it deletess batterystats.bin
but google already stated that its just placebo, this file is only for the batteryicon
thats why cwm removed it.
second those wakelocks are just seconds. so its normal
third. do you have any sync service?(skype,facebook,email, or even google) if so
try disabling temporaly
if dosent work you may wanna try the xposed + xposed module called disable critical shutdown
then wait till phone turns off and charge for minimum 8hours
if not
change rom/kernel
if still not
its your battery(if so, and you still have warranty, you can get an rma if you live in a google area or get money back if you live in a area where lg controls,or buy another battery
Click to expand...
Click to collapse
Hadn't read about it being a placebo, thanks for the info. I downloaded BBS and think the issue is actually the (common) msm_hsic_host issue. It had several hours today. I'm flashing Matr1x kernel right now, so we'll see if that takes care of the issue.
jwkicklighter said:
Hadn't read about it being a placebo, thanks for the info. I downloaded BBS and think the issue is actually the (common) msm_hsic_host issue. It had several hours today. I'm flashing Matr1x kernel right now, so we'll see if that takes care of the issue.
Click to expand...
Click to collapse
Oh nice. handn´t see this wakelock since 4.2.1 lol
btw:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
opssemnik said:
Oh nice. handn´t see this wakelock since 4.2.1 lol
Click to expand...
Click to collapse
Yeah, I remember reading about it way back when, and thought "oh, that's not affecting me at all." And now it looks like it very well may be causing issue -__-
opssemnik said:
btw:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
Click to expand...
Click to collapse
Well that pretty much clears that up, thanks!
Try going back to stock android and check the performance. It can be that one of the Xposed modules is causing you the problem.