[Q] Nexus S overheating issue - Nexus S Q&A, Help & Troubleshooting

I've been trying different ROMs (SlimICS, CM9, MIUIv4, Brainmaster's CM9, CyberGR-MOD), kernels (Air, Matrix), other stuff (Fidelity 2.0, changing screen DPI to 182 and 200).
First, after flashing fidelity restore zip I noticed that my phone started to get warmer than usual when I was listening to the music (regardless of player used, deep idle on or off). It was SlimICS which had several more bugs, so I flashed another ROM, and the problem seemed to be gone (but still there was some extra heating during music playback).
After that, my phone started heating when using noinnon's gReader. I thought it was some issue with this app, so I just removed it, and again I thought the problem was solved.
After that, I wasn't using my phone for about 3 weeks (it was fully charged and switched off). When I started using it again, I noticed some heat when using the phone (just screen on, some data usage, regardless of app).
Another day I used Wi-Fi AP for a few hours (while charging) and I was shocked: my phone got so hot I could barely hold it. It wasn't the battery (battery temp was 45 degrees). I thought it was some issue with the radio, so I tried flashing KD1 and even KB3, but doing that didn't make significant difference. I also tried doing full wipe (wiping all partitions I had access to using CWM Recovery, wiping battery stats, Dalvik cache) and flashing stock ICS, CM9, CM7.2, and even unrooting and flashing stock 2.3.6 GB - no difference.
Now it got even worse. Battery life is terrible (barely 8 hours on full battery with about 1 hour of screen on and few hours of music), and my phone heats up even if I just navigate the menu.
Does that mean my hardware is messed up? Is there any way to fix this?
P.S. Though I still have 1 month of warranty, it's not valid in my country (there were no official Nexus S sales), so I can't return my phone.

Did you also format /system and /boot (CWM -> mounts and storage) partitions?
Also, i'd advise flashing the factory images via fastboot. Commands can be found within the archive (flash-all.sh). I would do this:
-backup EVERYTHING on the phone (efs too if you havn't done so already, search for more info)
-download/extract 4.0.4 image for your particular model
-boot to fastboot, plug in usb, type commands in order as shown in the .sh file
-reboot, and hopefully your overheating problems are gone

Have you tried to switch off 3g data traffic? Try to switch to airplane mode and then turn on wifi and look what happens.
Probably the cell radio causes the heat!

Installed ICS OTA update and I think it helped. Didn't get to use my phone as usually, but battery life got better and there's no overheating during music playback. Still not sure if the problem is gone completely.
Thanks everyone for feedback

The original overheating issue beforehand could probably be traced to a rogue app.

I had the same problem and I tryed to wipe everything, but unfornately my battery lifeare lowered compared to some months before..
Now I flashed back via ODIN, the oficial ROM and updated from GB to 4.0.4, to see if that fix the problem....
View attachment 1177499

chronophase1 said:
The original overheating issue beforehand could probably be traced to a rogue app.
Click to expand...
Click to collapse
As I mentioned before, I tried wiping everything and flashing stock ICS, CM9, CM7.2, and even unrooting and flashing stock 2.3.6 GB. The only app common between these ROM's is SuperUser (I didn't install back my usual apps)... but 2.3.6 I flashed didn't have it.

Make sure nothing is overclocked. Try another battery also. Worth a shot
Edit: didn't see you have it sorted. OTA solved it.
Sent from my Nexus S using xda premium

Related

BAMF Sense 3.0 GB RC2 (I Busted Something)

I must have screwed something up as my phone is stuck in some sort of power cycle. Everything seemed to be working fine including several restarts after doing configurations and learning how the LCD density works. I do a shutdown of the phone I see the shutdown animation, but the screen still has the backlight on. It never seemed to actually shutdown so I hit the power button and the screen goes out. I go to boot into recovery to create a backup of my settings and like a moron i didn't delete the MR2 upgrade. I answered no to the install up the upgrade and reboot the phone. This is when the power cycles actually started I see no signal, 1x the phone locks up then restarts. I reflashed the radio in case it become corrupted and no change. I cleared the cache and the Dalvik to see if that would work NOPE now it's stuck on the DAS BAMF the baddest! boot screen. I did install the latest dreamkernal for the bluetooth options. Other than starting to install apps I can't think of what I may have done to do this. I don't have a problem reflashing, but I hate to cause this problem again. I did wipe 4x the factory, cache, Dalvik before flashing the rom and verified the md5. I know it's probably not possible without knowing exactly what I did, but any ideas or suggestions?
You've got wiping data/cache/dalvik/bat stats covered. I think 4 times is overkill, but certainly not hurting anything.
When you flash a ROM, are you flashing anything else....other mods, etc., before letting the phone restart?
Do you have a good radio? Try MR2 if you're not already, some have reported bugs or issues with MR2.5.
Check the md5 of both the ROM and Radio.
I would try to shut down the phone then pull the battery then boot bootloader and reinstall radio. If that don't work I would try a full wipe and reinstall
Sent from my BAMFBOLT using XDA Premium App
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Can you restore from a backup?
dms76 said:
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Click to expand...
Click to collapse
AFAIK all phone run fine at 245, its the 184 that doesn't play nice with some phones. Also turn off fast boot in the Settings>Applications menu, some people seem to have random problems when that is turned on.
I was in the process of trying to make a backup when something broke. It was actually easier to start over because then I could go setting by setting to see what I did wrong. I think it was just how I shut it down that fubar the whole darn thing. It seems to be working correctly now and I created a backup as well.
184 not 245 gotcha and thanks! That could save some battery life I would assume. No matter how well built there is still a better idiot!

Phone shuts off all the time

Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.

[Q] Bootloops after battery empties

Hi everyone, I've got a Nexus S 4g, SPH-D720.
This is the second time this happened to me: my phone's battery reached 0% and turned off, I turned it back on after plugging it in, and it turned off again for some reason. Tried to turn it back on, got stuck in a bootloop.
(I was running Apex 1.1.2 at the time that this happened, but it has happened before when I was on CM 9 v4.0 as well. The first time, I was using a calibrator app that told me I had more battery left than my phoen was displaying, so after it powered off I took the battery out and put it back in multiple times to see if the phone would turn on. It didn't. However, I did not do that this time, but the same thing happened.)
I tried clearing cache and flashing the same rom over the current one, but the loop persisted, and the only way to get my phone back was to do a data wipe/factory restore and reinstall everything from scratch.
The first time this happened, I had last backed my app up via Titanium 2 days prior. After the first time, I set Titanium to make backups every night, so the only thing I lost were a few text messages.
Now, I'm afraid to turn my phone if the battery dies in case this happens again and I have to erase everything. Is there any way I can figure out what the problem is? I suspect it is the ClockworkMod Touch Recovery (v 5.8.0.2), but has anyone else had this issue?
I appreciate you taking your time to read all the way through this.
What setting do you have cpu at? If its set too high your system cant handle the boot process correctly. If theres no power to handle the load itll reset itself. Wait until you get at least a solid bar or completely full and start your phone. Dont trust apps to properly tell you your battery percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
I forgot to add. The recovery is not causing the problem it has to do with battery and/ or rom/ kernel. And its not good for battery to constantly be run to zero. Thats why theres a warning to plug your phone in at a certain percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
Processor is set to 100 min 1200 max. Yeah, I did have the same kernel so that's probably it. I'll try not to turn my phone on until it's charged while off. Thanks!
(btw, the "app" I was using was a battery calibrator script)
Your welcome and i was having issues the same way and turned off set on boot and it didnt happen again. Some of these phones are touchy! im sure you know about scripting if you did it! Lol
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium

Battery with 4.4.4 update

Sorry if this has been discussed previous.
Since applying the 4.4.4 OTA update 2 weeks ago I've noticed a very noticeable downturn in my battery life.
My usage has remind the same or gone down along with my routine everyday. I could easily before go 36+ hours and still have ~20% charge left. Now I'm lucky if I go 12 hours before I get a low battery alert.
Anyone else in the same boat?
chowner said:
Sorry if this has been discussed previous.
Since applying the 4.4.4 OTA update 2 weeks ago I've noticed a very noticeable downturn in my battery life.
My usage has remind the same or gone down along with my routine everyday. I could easily before go 36+ hours and still have ~20% charge left. Now I'm lucky if I go 12 hours before I get a low battery alert.
Anyone else in the same boat?
Click to expand...
Click to collapse
Im right there with you, i havent been able to fix it as of yet. Though i am in the process of flashing my phone back to stock 4.4.3 and trying to take the ota again to see if something might of gone wrong the first time around.
I'd try factory data reset if I were you ... It's not likely you had a bad flash.. usually a bad flash results in a failed flash.
Ive done factory resets. Ive tried different roms. But every 4.4.4 rom that isnt aosp just gives really crappy battery life. Ive been trying to get different kernels but the only one i could find was buckmarbles kernel and my phone would keep freezing then restarting after a few seconds after boot..... So yeah i gave up on getting a 4.4.4 sense or gpe rom working
weird. I haven't seen any change in battery life on my One m8.
I feel like my battery life has gotten worse as well, mainly idle life. I'll be down to 90% in three hours which I would normally still be at 95-96 depending on how busy work is. If I don't use my phone I would still be at 99-100% after those three hours. Idk what happened but it bugs me
I've been having the same kind of issues. Though while still being a student I can't use my phone too freely in class, but it still drains to roughly 75% after my 3 hours in the morning, straight off the charger. I limit it to playing music occasionally but otherwise it's just on and in my pocket.
Just saw an idea on another thread. Someone said that doing a factory reset on a custom recovery doesnt touch the radio, and that factory resets on a stock recovery does. It is definitely possible something wrong with the radio could affect battery life so im gonna try to factory reset after returning to stock revocery seeing as ive only ever done it with TWRP
deadrider1 said:
Just saw an idea on another thread. Someone said that doing a factory reset on a custom recovery doesnt touch the radio, and that factory resets on a stock recovery does. It is definitely possible something wrong with the radio could affect battery life so im gonna try to factory reset after returning to stock revocery seeing as ive only ever done it with TWRP
Click to expand...
Click to collapse
Ive been trying various 4.4.4 based roms on my phone and been using trickster kernel mod to look through my cpu usage, and on every rom thats 4.4.4 based my cpu is constantly maxed...... and idea why this is happening, even on stock this happens and its really irritating me that i cant use any of the new roms that are coming out and im scared i wont be able to use the lollipop update when it comes out.
Sorry about double post, thought i was editing my old post
deadrider1 said:
Ive been trying various 4.4.4 based roms on my phone and been using trickster kernel mod to look through my cpu usage, and on every rom thats 4.4.4 based my cpu is constantly maxed...... and idea why this is happening, even on stock this happens and its really irritating me that i cant use any of the new roms that are coming out and im scared i wont be able to use the lollipop update when it comes out.
Sorry about double post, thought i was editing my old post
Click to expand...
Click to collapse
There's an app called SystemPanel that will show you what's using your cpu. If you look at the picture farthest to the left, you'll see a little vertical bar to the left of the app or process name. That bar will show you how much cpu the process is using. The more gray in the bar, the more usage. If nothing shows up as using all of your cpu, you probably have to go into the settings and set it to show system processes (it doesn't by default).
If you don't want to install that, there's a built in tool that may show you what you want to know. You have to enable developer options in settings. Then go to advanced, then enable the option that says "show cpu usage". If you do that, an overlay will appear on the screen . If there's one app or process at the top of the list most of the time, it's more than likely the culpit.
Try going into:
settings>
wifi>
advanced>
then uncheck scanning is always available
I noticed my battery life was cut nearly in half after upgrading to 4.4.4.
Now its not back to where it was before, but its around 90% of what it was before.
Hope it helps.
Well i finally fixed my issues. Turns out i had some bad media on my phone that was causing the media scanner to go out if wack.
deadrider1 said:
Well i finally fixed my issues. Turns out i had some bad media on my phone that was causing the media scanner to go out if wack.
Click to expand...
Click to collapse
What media are you talking about? Like in your SD card or internal storage?
My awesome HTCm8 has gone from being a ph with great battery to one that is down to 20% by end of day.
I did wipecache on recovery mode then finally did factory reset yesterday.
Still not much luck. Android system and Android OS and cell radio consume most battery. Before the update my battery usage would only show cell standby and WiFi and phone idle. Now it's a long list including Android system and Android OS. Before update I could go 2 days without charging.
Anything I can do? Do I need to factory reset again? I want my awesome phone back. Btw I was forced to update due to constant update notification which kept plumetting my battery by keeping the phone awake orelse would never update.

Random reboots.

Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037

Categories

Resources