[Q] How to debug Infuse restarting randomly? - Samsung Infuse 4G

Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.

It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium

psal217050 said:
It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hmmm, the power button seems to work alright. But if the power button is always pressed, I shouldn't be able to press it again and make it function properly, right? All the functions of the power button seem to be doing OK, i.e. menus pop up and it puts the phone to sleep mode, etc.
Is there anything more I can check to confirm that it is not the power button?

Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern

mccloud35 said:
Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern
Click to expand...
Click to collapse
Try to get a logcat using aLogcat from the marketplace.

mccloud35 said:
Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.
Click to expand...
Click to collapse
I have the exact same problem. Please let me know what you and people come up with.
Battery drops at least 4 or 5% after those random reboots.
I put liquid smooth JB on the infuse and was able to reduce the reboots to maybe 1 or 2 a day but the battery drain is still insane. from full to empty in 7 hours (but the battery usage says 17hrs, so please dont be confused, its really only 7hrs), texting, checking emails but nothing else. no music, or gps or anything that it intense.
The battery usage shows a constant battery drain, everything is at either 5 or 10% usage, except the screen which is at 42 - 60%
{
"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"
}
Any ideas?

I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??

mccloud35 said:
I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??
Click to expand...
Click to collapse
I ordered a new battery and hope that this will fix the problem, if anyone knows anything else please let me know. the battery is only 1 year old.

I had similar symptom (reboot followed by battery indicating lower) once when I had applied too much undervoltage applied.

I've had the same things happen with my phone.
1) the huge drops in battery isn't an actual drop. 99% of the time if you don't plug in a charger the battery will start 'charging' on it's own until it gets to the right amount.
2) just because the power button works doesn't mean there isn't something wrong. The infuse is notorious for messed up power buttons. There is a thread around here somewhere about fixing it. I've not done it because I managed to get things under control.
3) I've noticed that the reboots seem to occur more frequently when a large number of apps ( popular or not) are installed, or apps that are resource intensive. For instance I bought minecraft because my daughter has become adducted to it. Sometimes its fine other times it freezes and reboots. My solution is to only keep apps I use on my phone. I will most likely uninstall minecract until a later date.
4) For me smaller ROMs work better. The current slimrom works the best for me. Also finding time to remember to reboot my phone once a day no matter how it is running helps.
I'm down to a reboot every one or two days now. Unless I try to play minecraft. I blame those damn creepers. Good luck!
Sent from my SGH-I997 using xda app-developers app

OK so my reboots were because of my power button, I sent it in to mobiletech and they repaired it.
Now it's fixed and I have not had a single reboot.
Sent from my SGH-T999 using xda premium

Glad to hear that. Thanks for sharing your results.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Related

[Q] Stuck on Asus boot screen

Hey folks, need a bit of help here.
I have a weird problem. I took my TF off of charge a few hours ago and laid it on the table. I just came back to it now, and its on the "ASUS - Inspiring Innovation. Persistent Perfection" and stuck. The progress indicator is about half way around.
I press and held the power button for 5-10 seconds, then 30 seconds, then a minute, no change. I press and held the Vol- and power for 10/30/60 and no change. It just won't budge from this screen way now.
Is there a way to forcefully power off the tablet? Or do I have to wait for the battery to drain out?
It was working fine before this, and I didn't make any changes recently except ran a few application updates last night. Any suggestions?
I'm rooted with Revolution HD rom on it. I can't get into recovery, and no response from ADB. Its just stuck where it is.
So you can't even get into recovery with the manual button combo?
What about your serial number? NVFlash compatible?
baseballfanz said:
So you can't even get into recovery with the manual button combo?
What about your serial number? NVFlash compatible?
Click to expand...
Click to collapse
I can't get any response out of it all. Serial number on the bottom is B60K**, its nvflash compatible (I did a restore back to stock with nvflash not too long ago), but, I can't get it to "reboot" at all to put it into APX mode.
I'm assuming once the battery dies and the thing shuts off I may have a few more options, but right now I'm stuck here.
Edit: Here is the screen its stuck on (progress ring at the bottom is frozen)
{
"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"
}
Holding just the power button should eventually power it off
Sure the power button is working ?
*Detection* said:
Holding just the power button should eventually power it off
Sure the power button is working ?
Click to expand...
Click to collapse
Well, I guess at this point I can't gaurentee 100% that its working. However, the power button was always working until this happened. I haven't had any other issues other than the deep sleep issue with ICS.
Yeah holding down your power button should turn it off I had this happen to me like a week ago.
Thats working fo me, but it keeps coming back every day, very annoying.
Sent from my Transformer TF101 using xda premium
tegezee said:
Yeah holding down your power button should turn it off I had this happen to me like a week ago.
Click to expand...
Click to collapse
I wish it was that easy for mine, no matter how long I hold the power button, nothing happens. I'm sitting here now waiting for the battery to drain out. Will probably take a few days seeing that I just finished charging it when this happened.
Just to give an update, I left it for overnight, and when I woke up this morning, the battery had finally died. So, I plugged in the charger, and the tablet booted up fine.
Power button, volume buttons, etc, work fine. I have no idea what caused this problem, but i'm glad its working now.
Should I go back to stock to be safe? Or am I fine with ARHD?
My t101 has done the exact same thing. I woke up an hour ago from a nite of charging and now it is stuck at the ASUS loading logo. It was at first loading, the wheel spinning, then it stopped. I can not turn it off nor enter recovery . It cannot do anything. adb will not recognize it at all. I havent tried nvflash.
Rooted & running cwm.
Any suggestions or am I sol until it manually dies form no juice?
8milerd said:
My t101 has done the exact same thing. I woke up an hour ago from a nite of charging and now it is stuck at the ASUS loading logo. It was at first loading, the wheel spinning, then it stopped. I can not turn it off nor enter recovery . It cannot do anything. adb will not recognize it at all. I havent tried nvflash.
Rooted & running cwm.
Any suggestions or am I sol until it manually dies form no juice?
Click to expand...
Click to collapse
Sounds like the exact same issue I had. Nvflash wasn't possible for me either because when it was stuck on the loading screen with the spinner frozen, I couldn't power it off, enter recovery, or anything.
I have no suggestions other than wait for the battery to die. My only fear was that the logo and spinner being lit on the screen for such a long period of time would cause some sort of burn-in. But, luckily, screen technology these days that doesn't seem to be an issue. Mine suffered no ill-effects.
Thank you for the help. I tried NVFlash and it was a no go as well. My battery was at 100% when this happened, hopefully it isnt a 2 day wait to drain it. I have only had the thing since the 19th of this month so I may just return it for another one as they have a 15 day return policy. I also wrote Asus about it. Seems they are aware because they on their support site have this listed as an issue.
Either way lesson learned. I will no longer leave it connected to the keyboard dock charging all night...
---------- Post added at 03:42 PM ---------- Previous post was at 02:49 PM ----------
Update:
Ok, I got it to reboot.
Using Windows 7 I hooked up the tf101 with the it attached to the Keyboard dock to the usb
I went to device manager, options, Add legacy hardware.
Clicked Choose from list
Added Android ADB interface, Android adb composite interface.
Then added Android adb bootloader interface.
Restart pc
Held power and it finally powered down.
I had android sdk installed before hand as well.
Hope thi helps anyone if it happens to them.
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
chadcspencer said:
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
Click to expand...
Click to collapse
Yeah, I tried that as well at the time, no luck.
So, just to update. After this happened the first time, I let the tablet battery die out, after which it booted up fine. About a week later, the exact same thing happened again. So, thinking it for some reason was related to the custom rom i was running, I nvflashed back to stock. However, I still have the issue from time to time. Its very frustrating, and I'm not quite sure if its a software issue or a hardware issue.
I'm gonna leave it for a little bit, but if it continues to happen on a regular basis, I'll have to call Asus.
chadcspencer said:
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
Click to expand...
Click to collapse
This does not do anything here
Same boat, 3rd time coming back from RMA. My other has absolutely no issues, Asus refuses to repair or fix the one which has had all the issues...
Stuck on this all the time, and I'm on stock :/
cquilliam said:
Yeah, I tried that as well at the time, no luck.
So, just to update. After this happened the first time, I let the tablet battery die out, after which it booted up fine. About a week later, the exact same thing happened again. So, thinking it for some reason was related to the custom rom i was running, I nvflashed back to stock. However, I still have the issue from time to time. Its very frustrating, and I'm not quite sure if its a software issue or a hardware issue.
I'm gonna leave it for a little bit, but if it continues to happen on a regular basis, I'll have to call Asus.
Click to expand...
Click to collapse
When using some custom kernels/roms the boot process stucks after the Asus logo when the tablet is connect to a PC or power supply.
To solve this disconnect the USB / powercable before booting.
Or flash a 9.2.2.3. based kernel like guever-test13 (or higher).
Had the same problem here. I tried to solve this myself, but after 4 days I nvflashed all stock and RMA'd it.
They sent me a new tab... But now it's all okay! I just can't exactly remember how I bricked my tab and this is frightening me.. I don't want to do the same error!
Sent from my Transformer TF101 using XDA
I have actualy had the same problem occor and what i did was hold power then boot holding power down then switch to press up to enter CWM recovery then just select reboot device now... works great, had to use this method 3-4 times once today
Sent from my Transformer TF101 using XDA Premium App
I'm having this problem with my non-rooted Transformer on ICS.
Usually holding the power button down will get it boot normally.
But then randomly when I leave it alone for a while, it will re boot but then get stuck in a loop at the 'Eee Pad' screen with the screen going off every 15 seconds or so. To then get it to re boot then I have to hold the power down button when the screen is off until it comes back on, and then hold the power button down again afterwards for about 10 seconds when it is on for it too boot normally again.
I was hoping that rooting would fix that issue, but it seems not.

Nexus S Charging Indicator Issue (While the phone is off)

Nexus S - ICS 4.0.4 - rooted + ClockWorkMod + SuperUser
I have a big issue with my phone. The charging indicator, while my phone is turned off, doesn't stop progressing even when I have unhooked my phone from the wall-USB charger (From both sides I tested this). When I quick-press the power button to check the indicator, although the phone is totally disconnected from its charger, the charging indicator displays as if the phone is attached to a charger.
This happens only when the phone is turned off. When I turn on the phone, the ICS battery charging indicator works correctly.
And also the phone randomly reboots while it goes into sleep mode. This is so bad that I can't actually use the phone. It reboot every 1-2 minutes!
I have figure out this indicator malfunction is the reason for random reboots of the phone while in sleep mode (when no charger is attached to it)
{
"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"
}
--------------
UPDATE: ISSUE RESOLVED
I switched back to the stock Samsung wall charger ( bought a new charger) and bought a new battery.
The phone has not restarted in two weeks.
Try reflashing the kernel wiping cache and dalvik. If you haven't flashed a different kernel, try one out. They all react different from phone to phone but I have the best luck with Air Kernel.
Sent from my Nexus S 4G using xda premium
.OmEgA said:
Try reflashing the kernel wiping cache and dalvik. If you haven't flashed a different kernel, try one out. They all react different from phone to phone but I have the best luck with Air Kernel.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
So is this battery indicator showing while the phone is off related to the kernel? I tried to reflash a new ROM (ICS 4.0.3 and then upgrade to 4.0.4), wiped everything and the issue is still there.
Its a good place to start. Plus it wouldn't hurt at all flashing a better kernel than stock. If that doesn't take care of it, only other thing I can think of is returning it to completely stock (unroot and all) and see if the problem still persists. Then you know it could be some sort of hardware issue some how. But for now just make a nandroid of your current set up, find a kernel you want to run, clear cache and dalvik cache then flash your kernel.
Sent from my Nexus S 4G using xda premium
.OmEgA said:
Its a good place to start. Plus it wouldn't hurt at all flashing a better kernel than stock. If that doesn't take care of it, only other thing I can think of is returning it to completely stock (unroot and all) and see if the problem still persists. Then you know it could be some sort of hardware issue some how. But for now just make a nandroid of your current set up, find a kernel you want to run, clear cache and dalvik cache then flash your kernel.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Thanks. Where can I get these Kernels for Nexus S ICS?
If you have a GSM Nexus visit the Nexus S development forum. If you have the 4g variant, visit the Nexus S 4g development forum. You'll want to look for topics with [kernel] in the thread title. Matr1x and Air Kernel are few of the popular ones.
Sent from my Nexus S 4G using xda premium
Clean your micro USB port with a tooth brush(dry) and some compressed air...had this same issue u can flash all u want but I bets its the dirty slut usb
Sent from my Nexus S using XDA
Dirty USB port was the cause of this and the crazy reboots.
b1337 said:
Clean your micro USB port with a tooth brush(dry) and some compressed air...had this same issue u can flash all u want but I bets its the dirty slut usb
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Exactly! this was the issue. I used some tissue and electronic board cleaning spray to dampen the tissue. Also, I raised the lower edge of the ubs port towards its top a little. After plugging in the charger and playing a little the Crazy charging indicator went away. No Reboots so far!
But why would this happen? I read somewhere that Galaxy Nexus is also infamous for this hardware bug. Is this normal? (My phone is 8 months old)
i think there may be a ics bug that the charge indicator is wonky, i have been to lazy to roll back to gb to see, it charges just doesn't always show on the battery icon but in stats it is charging
b1337 said:
Clean your micro USB port with a tooth brush(dry) and some compressed air...had this same issue u can flash all u want but I bets its the dirty slut usb
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Cleaning it worked till last night I again turned the phone off the fully charged it using the wall charger (I am using a Nokia Charger with the same specification of the Stock charger).
Turning the phone on today, it started rebooting again. Now in 5 minute cycles while in sleep mode.
I plugged in the USB connector of the computer and plugged it out. The charging indicator went crazy again!
I really doubt I could count on this phone as a "phone" any more. This is so bad.
Same here, completely disassemble it and a little bit of cleaning and rising the pins.
So far (4h from now) no problems.
But im expecting it again, since the problem is hardware related, and all day im charging and using usb ...
nexus s random restart
Hi experiencing same problem from couple of weeks. phone show charging indicator even not connected to charger and random restart. some time battery drain like crazy even phone in completely shutdown state. I think some thing short in hardware end which eating battery power. phone is in stock with ics 4.0.4
You have a USB port problem bring it back to Samsung to fix
Sent from my Nexus S using Tapatalk 2

[Q] G2X Keeps Turning off -- Needs Charger to turn back on

Hi Everyone:
I am getting an issue with G2X that it randomly shuts off and that pulling the battery won't do anything. I would need to plug the charger into the phone in order to turn it back on. Last night I left the charger and I found this morning that it turned off while charging. Battery read 100% after I turned it on.
Originally I rooted it with CM7 Stable and the only problem was that whenever I called someone or someone called me, it sounded like a helicopter on the phone.
I flashed with NVFlash, cleared cache, all data, davlik, and then installed CM7 stable.
I tried it again and everything worked out great.
Last week I changed my room. NVFlash, Cleared Cache, All Data, Davlik, and installed HellsFire Rom with the CPU OCed to 1.5 Ghz.
The issue I ran into was that it drained power really fast. I ran out of power within 4 Hours.
I got tired of this and then I went back to CM7 Stable.
I began to have the issue where the phone keeps thinking there is no battery power and the phone keeps turning off. When I try to turn it on, it goes to the White LG Logo, and then Blue LG Logo, and then it turns off. I need the charger to turn the phone on. When the phone turns on it says "60% Power Left".
And then later on (5 Minutes at most) it will turn off, try to reboot, White LG/Blue LG, turn off. When it does turn on with the charger it will say "10% battery left please connect charger" and then it will turn off. When I remove the charger and turn it back on, it will have the battery symbol in grey with an exclamation point.
I thought I would try to do everything again, I booted into ClockworkMod and then it turned off.
What I tried after was maybe it was the Kernel. I reflashed and deleted everything, and then installed the CM7 stable rom and then TRINITY Kernel. The phone would not load on Trinity Kernel. It was stuck on the Trinity loading screen for like 5 minutes and I turned it off and Reflashed/Redeleted everything. I then reinstalled CM7 Stable and it loaded up.
I changed to a new ROM after it worked. I downloaded a new ROM yesterday, I am using Mokee Rom right now.
The issue still happens. Every few minutes the phone will turn off. Sometimes the phone would attempt to reboot and the White LG Logo comes up, and goes off, and loops this.
I have no apps on my phone currently.
The gray battery with the ! is there when I pull the battery and try to reboot.
I need the charger there to get the phone going.
Anyone have any suggestions of what I should do? The phone isn't even 2 years old yet.
Thank you.
N1rve said:
Hi Everyone:
I am getting an issue with G2X that it randomly shuts off and that pulling the battery won't do anything. I would need to plug the charger into the phone in order to turn it back on. Last night I left the charger and I found this morning that it turned off while charging. Battery read 100% after I turned it on.
Originally I rooted it with CM7 Stable and the only problem was that whenever I called someone or someone called me, it sounded like a helicopter on the phone.
I flashed with NVFlash, cleared cache, all data, davlik, and then installed CM7 stable.
I tried it again and everything worked out great.
Last week I changed my room. NVFlash, Cleared Cache, All Data, Davlik, and installed HellsFire Rom with the CPU OCed to 1.5 Ghz.
The issue I ran into was that it drained power really fast. I ran out of power within 4 Hours.
I got tired of this and then I went back to CM7 Stable.
I began to have the issue where the phone keeps thinking there is no battery power and the phone keeps turning off. When I try to turn it on, it goes to the White LG Logo, and then Blue LG Logo, and then it turns off. I need the charger to turn the phone on. When the phone turns on it says "60% Power Left".
And then later on (5 Minutes at most) it will turn off, try to reboot, White LG/Blue LG, turn off. When it does turn on with the charger it will say "10% battery left please connect charger" and then it will turn off. When I remove the charger and turn it back on, it will have the battery symbol in grey with an exclamation point.
I thought I would try to do everything again, I booted into ClockworkMod and then it turned off.
What I tried after was maybe it was the Kernel. I reflashed and deleted everything, and then installed the CM7 stable rom and then TRINITY Kernel. The phone would not load on Trinity Kernel. It was stuck on the Trinity loading screen for like 5 minutes and I turned it off and Reflashed/Redeleted everything. I then reinstalled CM7 Stable and it loaded up.
I changed to a new ROM after it worked. I downloaded a new ROM yesterday, I am using Mokee Rom right now.
The issue still happens. Every few minutes the phone will turn off. Sometimes the phone would attempt to reboot and the White LG Logo comes up, and goes off, and loops this.
I have no apps on my phone currently.
The gray battery with the ! is there when I pull the battery and try to reboot.
I need the charger there to get the phone going.
Anyone have any suggestions of what I should do? The phone isn't even 2 years old yet.
Thank you.
Click to expand...
Click to collapse
I think your battery is dead. Try another battery if not already.
-- The noob says:
Sent to the Facebook of cellular phones.
mansa_noob said:
I think your battery is dead. Try another battery if not already.
-- The noob says:
Sent to the Facebook of cellular phones.
Click to expand...
Click to collapse
I will try that. Thanks.
Same boat.
I am also having that same problem, I just bought a OEM (original equipment manufacturer) battery on Amazon will receive by hopefully next wednesday or thursday. i'm still using weapon g2x. I'm comfortable with it, after messing around with other roms a year ago. I just got lazy and stayed with it.
40zJuice said:
I am also having that same problem, I just bought a OEM (original equipment manufacturer) battery on Amazon will receive by hopefully next wednesday or thursday. i'm still using weapon g2x. I'm comfortable with it, after messing around with other roms a year ago. I just got lazy and stayed with it.
Click to expand...
Click to collapse
Could you tell me if this fixes the issue? If it does I'm going to buy a new battery than a new phone lol.
Here is a graph of my battery stats.
{
"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"
}
battery came in!
N1rve said:
Could you tell me if this fixes the issue? If it does I'm going to buy a new battery than a new phone lol.
Here is a graph of my battery stats.
Click to expand...
Click to collapse
Okay so good news people, I received my battery on saturday june 15, 2013 from OEM4less in 2 DAYS!. I charged it up at 100% before using. I have not experienced any sudden reboots, or my screen going completely black, nor my screen only being lit up half way (yes it happened, litterally halfed the back of my screen was dim). I did experience my phone freezing but that was cause i was TEXTING someone back, WHILE commenting on FB, then I received a CALL, so total overload.
It has been approximately 16-18 hour of use, a total of approximately 8 hours constant reading pdfs, using fb, instagram, twitter, AND NO SUDDEN SHUTOFFS.
I HAVEN'T tried HOTSPOT, cause t-mobile be whining and *****ing.
I HAVEN'T tried BLUETOOTH cause I don't have any device that needs to use it.
So far the problem was the battery. I checked my old batteries VOLTAGE it read 4 volts, which is fine cause voltage can be approximate.
I did NOT check it's amperage levels which is strength or pressure of the voltage being spread into the phones circuits/body.
ill check later on the amp reading.
I have read online that its BAD to use your phone while it charges, WHICH i found out too f-ing late. BUT YES! problem so far fixed, will keep updating status on my phones behavior.

5.1.1 Update / Phone shuts off automatically

Can someone please help me. After the 5.1.1 OTA update my phone randomly shuts off (like pulling the plug off an appliance). I already did the factory reset and it still has this problem.
I have the same problem, and the only way to switch it back on, is to plug it in the charger, wait for the battery icon to appear, and then try to switch it on.
It shut off twice while I was using the camera, and I thought it was caused by the HDR+ bug, but it also happened twice later, while idle in my pocket.
Anyone else seen this?
Android 5.1.1, stock, Rooted.
Sent using Tapatalk.
Same
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
igimmi said:
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
Click to expand...
Click to collapse
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
kted said:
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
Click to expand...
Click to collapse
Are you running 5.1.1?
I'm afraid to update my wife's Nexus 4 to 5.1.1.
Damn 5.1.1
I had no issues with 5.1.1, so you all probably should just flash factory images through fastboot.
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
I wonder if we have to wait for an official bug fix from Android.
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
HEY!!!
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
igimmi said:
I wonder if we have to wait for an official bug fix from Android.
Click to expand...
Click to collapse
tesla45 said:
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
Click to expand...
Click to collapse
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
beekay201 said:
HEY!!!
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
Click to expand...
Click to collapse
The thing is it started all of a sudden, a week ago...
Sent using Tapatalk.
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
GripR said:
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
Click to expand...
Click to collapse
Safe mode didn't work for me.
My problem is not the same, it seems.
It happens one in every two times I take a photo with HDR+.
The phone switches off instantly, and the only way to switch it on again, is to plug it into a charger.
Sent using Tapatalk.
Safe mode didn't work...
I have the same issue.
Started like a week ago while came back from M preview to cataclysm. Was very frustrating and made a clean install of stock, reboot continued, more accurately it seems like a reboot with the Google logo, and then it turns off.
Happens with and without xposed.
What I have noticed though is that it happens much much less when WiFi is off.
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... ?)
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
strainhunter said:
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... )
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
I also think it's the battery. I will be be changing the battery soon. if there is any improvements after that I will provide update.
So today, my phone kept dying when the battery was around 40%. So I said screw it and got the battery replaced.
The old battery (on the right) looked bloated compared to the new one. The battery could have been the cause of all our problems.
{
"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"
}

Phone shuts down and will not boot when charging [SOLVED]

This trouble started about a month ago. The phone was rooted but I unrooted, factory wiped and then did the ota update last week. The trouble did not go away, unfortunately.
If I am using the phone, and plug the charger in, after a couple seconds it will immediately power off and go to the green charging screen. If I try and power on from there, it will power off again around the time the blu animation plays. Sometimes, it will get to "Android is starting.... Optimizing apps (number) of (number)" It won't get very far into that before it shuts down again. My girlfriend also has a Pure XL and I get the same result when trying to use her charger.
Any ideas what could be causing this?
Thanks!
edit: SOLVED!
Here is what happened: When I first got this device in december, I rooted it the day after it arrived. A week or so later, the phone randomly got stuck in a boot loop. No amount of button presses and or holds helped. The only thing i could think to do was a battery pull. As I was pulling the battery, I tore the ribbon cable in half. Within an hour I had soldered in some kynar to patch the tear. It booted right up and charged no problem at all and didn't give me any trouble until these recent charging issues. Tonight I decided to open it up and check the connections again. Lo and behold, a solder joint had failed in the center (thinnest) part of the patch job. I de-soldered everything, cleaned up the old solder, split the cable up and was able to do a much better patch job this time around. Everything is up and running just like new again. Thank you folks for helping me troubleshoot.
For anyone wondering what the heck I am talking about, here is an image of a similar ribbon cable patch job. This ribbon has 6 tracks. The Pure XL battery only has 3.:
{
"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"
}
hexagonlux said:
This trouble started about a month ago. The phone was rooted but I unrooted, factory wiped and then did the ota update last week. The trouble did not go away, unfortunately.
If I am using the phone, and plug the charger in, after a couple seconds it will immediately power off and go to the green charging screen. If I try and power on from there, it will power off again around the time the blu animation plays. Sometimes, it will get to "Android is starting.... Optimizing apps (number) of (number)" It won't get very far into that before it shuts down again. My girlfriend also has a Pure XL and I get the same result when trying to use her charger.
Any ideas what could be causing this?
Thanks!
Click to expand...
Click to collapse
load up app called ampere; and see if its an over current or voltage problem
tbirdguy said:
load up app called ampere; and see if its an over current or voltage problem
Click to expand...
Click to collapse
just over 4 volts when charging. max went to 2970ma then dropped to about 2600 before it shut off again. battery temp was right at 30 degrees c.
hexagonlux said:
just over 4 volts when charging. max went to 2970ma then dropped to about 2600 before it shut off again. battery temp was right at 30 degrees c.
Click to expand...
Click to collapse
All that seems within spec;
Id try reloading the rom using spflash tool (read the unbrick thread, its full of information)
or if that seems too major of undertaking, maybe pull some adb logcats and see what exactly is causing the reboot
tbirdguy said:
All that seems within spec;
Id try reloading the rom using spflash tool (read the unbrick thread, its full of information)
or if that seems too major of undertaking, maybe pull some adb logcats and see what exactly is causing the reboot
Click to expand...
Click to collapse
Yeah I rooted it again for logcat access. I used an app called catlog to see the logs (in real time?) Will checking the logs via adb show me the stored logs and hopefully whats happening just before crash?
At what point after powering the phone on does it actually start logging?
hexagonlux said:
Yeah I rooted it again for logcat access. I used an app called catlog to see the logs (in real time?) Will checking the logs via adb show me the stored logs and hopefully whats happening just before crash?
At what point after powering the phone on does it actually start logging?
Click to expand...
Click to collapse
Logcat should start logging as soon as its service starts, which is early in the booting stage so it should be logging everything that the system spits out while the phone is booting up and while running.
If you know exactly what to look for and how to troubleshoot Android systems, then you can try to debug the issue yourself. If you don't, just post the log(s) and let someone experienced and helpful check it out. Logs should be the files stored in /dev/log.
SOLVED!
Here is what happened: When I first got this device in december, I rooted it the day after it arrived. A week or so later, the phone randomly got stuck in a boot loop. No amount of button presses and or holds helped. The only thing i could think to do was a battery pull. As I was pulling the battery, I tore the ribbon cable in half. Within an hour I had soldered in some kynar to patch the tear. It booted right up and charged no problem at all and didn't give me any trouble until these recent charging issues. Tonight I decided to open it up and check the connections again. Lo and behold, a solder joint had failed in the center (thinnest) part of the patch job. I de-soldered everything, cleaned up the old solder, split the cable up and was able to do a much better patch job this time around. Everything is up and running just like new again. Thank you folks for helping me troubleshoot.
For anyone wondering what the heck I am talking about, here is an image of a similar ribbon cable patch job. This ribbon has 6 tracks. The Pure XL battery only has 3.:
hexagonlux said:
SOLVED!
Here is what happened: When I first got this device in december, I rooted it the day after it arrived. A week or so later, the phone randomly got stuck in a boot loop. No amount of button presses and or holds helped. The only thing i could think to do was a battery pull. As I was pulling the battery, I tore the ribbon cable in half. Within an hour I had soldered in some kynar to patch the tear. It booted right up and charged no problem at all and didn't give me any trouble until these recent charging issues. Tonight I decided to open it up and check the connections again. Lo and behold, a solder joint had failed in the center (thinnest) part of the patch job. I de-soldered everything, cleaned up the old solder, split the cable up and was able to do a much better patch job this time around. Everything is up and running just like new again. Thank you folks for helping me troubleshoot.
For anyone wondering what the heck I am talking about, here is an image of a similar ribbon cable patch job. This ribbon has 6 tracks. The Pure XL battery only has 3.:
Click to expand...
Click to collapse
Something I've wondered about soldering on those flex cables, does the soldering iron melt the plastic, I've got a few things that could be fixed if I had the balls to try it
Of the admittedly few flex cables I have soldered on, I can't recall the plastic ever melting. I always use some kind of blade to scrape the top layer and expose the metal tracks underneath. If they are really small and or close together, carefully cutting the plastic between the tracks can make the job easier as you can individually lift and solder them one at a time.
Hey. I'm having a similar issue with my phone. How do you get the cable out for the battery? I just purchased this phone with issues from someone and it looks like they tried to remove the battery and I'm having similar issue to you but I'm not able to get the battery out and I don't want to destroy the cable. Thanks.
How do you remove the battery?

Categories

Resources