I used to be a on a stock KG2 carrier specific ROM until i realized the battery was unbearable and thus flashed to the stock KI3 ROM
"GT-I9100_XEU_I9100XXKI3_I9100XXKI3_I9100XEUKD1" specifically with the "CF-Root-SGS2_XX_OXA_KI3-v4.1-CWM4" kernel; things were great including battery life, performance (HSPA performance was a tad worse than the stock KG2 but nothing major), however, I would randomly get these restarts every now and then -which, knowing Android and the fact that it wasn't stock and all, were understandable- but recently I tried these new batteries (Anker 1900mAh) for the GS2 and well as soon as I tried them (both), the phone went into a boot loop (not just rebooting without booting up but it would load everything, including homescreen and media scanning etc and then restart - continuously).
Thankfully I had made a nandroid backup of my phone right before trying then new batteries and well even after restoring that or reflashing the KI3 ROM/kernel etc it still won't fix the issue.
Is there any solution besides wiping and factory reset? Took me months to set up my phone and I really can't afford to take a hit.. again.. (had issues with custom ROMs before and had to wipe it all) and no.. I don't even have a Titanium backup (up-to-date at least - perhaps a way I could still make that with this reboot issue? ..could make things easier).
Check out the various random reboot threads.
Might not be anything at all to do with your software.
Could be hardware like battery terminal connections etc.
Sent from my GT-I9100 using XDA App
I've heard about phones doing these kind of things when used with bad third party batteries that could be whats happening. I would only stick a samsung battery into the precious galaxy s2 for fear of it combusting.
Related
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
First backup data and factory reset .
Still a problem reinstall the firmware.
Checkfus will let you download it and flash via Odin .
Or take it to a service centre is the other choice .
jje
factory reset m8 if ur carrying ur bckup frm gb ,than some apps r not fine wiv ics...jus use ur ics wivout ur bckup of apps and download betterybattstat and some apps to c wats draining,ull get some idea.
magosalas said:
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
Click to expand...
Click to collapse
I am having exactly the same problem. This has started just after upgrading to ICS. (I have an unlocked S2 CSC:XEU). Never had this problem before. I tried hard reset but the problem is still there.
I have upgraded using Kies.
I have the same problem on unlocked S2 CSC:XEU. not rooted...
reset didn't work. full wipe - the same problem
ics problems
hi, i have the following problems after updating to official ICS,
wifi sometimes gets stuck between on/off
sometimes phone goes to sleep and does not respond
wake up is slower than in GB
after numerous hard resets and re-flashing ICS with odin these issues persist.
I recommend re-flashing the official GB version and wait till samsung sort their crap out.
all these issues are kernel related. the wifi issue is reported to be a faulty stock kernel and the black unresponsive screen also is a kernel issue I faced with some beta kernels.
my tip, before you hesitate to go back to GB, give one of the custom kernels a try. Siyah, Speedmod, ... just for the moment don't tweak anything and make sure you really flash an ICS kernel (!!). Just flash one of these kernels and give it a try, you don't even have to do it with odin and thus increase the counter, but you can use that variant. When you are in CWM, instead of flashing the SU zip file, flash the custom kernel zip which will root your phone, too.
Now give the custom kernel a try and see if your issues are gone.
If you don't like it, just flash the stock kernel with odin and uninstall SU and Busybox, and you are back to stock ICS.
I had the same problem. Kernel. Flash the latest siyah kernel and sleep of death will dissapear
Sent from my GT-I9100 using XDA
I'm getting the exact same issue running Siyah 3.3.2 and CM9. Also happened with stock ICS.
First few times it happened the phone was in my pocket and I felt it get warm. Only way to recover it was to hold power button in for about 10 seconds and it then reboots. I thought the screen was unlocking in my pocket and it was switching off due to overheating... but
Happened again today whilst I was using the phone. Screen went black and phone started getting hotter and hotter. I now think something is causing some kind of loop that causing the lockup / heat up and the phone is actually still on until I press and hold the power button.
I'm currently trying a "record" with CatLog but I can reproduce the problem easily apart from it happening 4 times in the 4 weeks I've had the phone.
(Its a I9100P if that makes any difference)
Hello all,
I've been experimenting with custom roms lately. First I tried resurrection since it got lotsa attention and then I tried sensation, all causing the same problem.
I was lucky to have a NAND backup so I quickly went back to my stock rom. But now I am wondering why are these roms causing heating problems but not the stock rom? Interestingly, many people are using them without any complaints.
I thought this might be a problem with my phone. I contacted amazon and asked for a replacement, they were nice to replace the product even after 3 months! (kudos to them).
But now I'm wondering if this will solve my problem. Moreover, I sometimes had heating while charging the phone, bolstering my thesis that the phone is faulty. Any ideas anyone?
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
atifsh said:
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
Click to expand...
Click to collapse
Lol calm down! I've not returned it, I am going to replace it. I've had heating problems with stock rom as well, especially while charging. I've changed the battery, thinking the problem was the battery but it didn't help at all. Also today, after being back to stock rom, it still heats up even with simple tasks. So I assume there is some kind of fault.
It's normal for your phone to heat up. If it heats up its perfectly normal because the cores are working fine. If u got battery heating warnings or any other phone heating warning thats the problem and you should investigate =D
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
pneuma00 said:
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Jimmy_Christ said:
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Click to expand...
Click to collapse
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
pneuma00 said:
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
Click to expand...
Click to collapse
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, you're right...
I did wipe the battery stats, let it drain completely and did a full recharge. For the kernel, I don't really know much about these stuff (yet). This is the ROM I use : http://forum.xda-developers.com/showthread.php?t=1259739. Im my phone info menu it says 2.6.32.9-perf [email protected] #23 (no idea what this means) so I don't know if it's a custom kernel or a stock one. For clock values I use min: 30MHz max: 600MHz (which is the stock value if I'm not wrong). I don't know what you mean by voltage tables, I'd appreciate if you could explain that.
Thanks so far.
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yes, I haven't touched anything in the ROM I'm using currently.
I've been searching the forums for days before starting this thread, without success.
What I noticed about the reboots is that it occurs almost exclusively when making / receiving a phone call and when the phone is idle.
*edit: I forgot to mention that I'm using Segoe font, not sure if that makes a difference though. I have replaced almost every font in the /system/fonts folder (droid sans+bold+mono and even droid serif+bold+italic+bolditalic)*
I'm getting rather fed up with my Rezound. My battery life has been poor, and I am constantly dealing with all sorts of crashes and glitches. I've gone from Sense to AOSP and back again, and since JB came out with working Bluetooth have stuck with JB. I've wiped and started from fresh so many times, and though everything works fine at first, it seems to just be a matter of time. I don't want to nuke all my Titanium Backup backups but I'm getting to the point where I don't know what else to do.
To the point: Is there a way to test and confirm the integrity of the phone's hardware? I know that some PCs can test hardware via BIOS, so I imagine something similar might be possible with mobile devices. This is most likely something that could not be done while running Android, due to the compartmentalization and sandboxing implemented in the OS. I want to test the RAM, NVRAM, and the CPU (possibly with a stress test though this can be done through Android via apps) and find out if there are any hardware issues.
On the other hand, if I'm going in the wrong direction, please let me know. As aforementioned, I'm running JB AOSP, been going back and forth between Wildstang83's CM10 build and Neo's RAGE (currently Infection). I've stopped trying different kernels as my battery life sucks either way. Recovery is AmonRa 3.15, HBOOT is 2.27.xxx, baseband is 2.22.10.0801r/2.22.10.0803r.
Problems include screen freezing on wake (soft keys light up, screen stays dark and doesn't respond); System UI crashing, generally followed by whatever app I'm trying to use such as Messaging, and often results in wallpaper resetting to default; ANRs in Maps and other apps; Phone crashing when trying to make an outbound call; poor battery life (I've killed all startups and stripped down idle run apps to bare minimum, it doesn't help, I replaced the battery about 6 months ago) and various other issues.
Phone has never been wet and has no significant damage; it has worn rather well for being over a year old.
Kernel tuner for "bios" type stuff and stability test for stress testing. Undervolting helps save battery for me. I also use dancedance/badass governor. Idk about your bug problems though, I have had issues with restoring data from old ROMs that completely made a new ROM unusable
Sent from my ADR6425LVW using xda app-developers app
You got a good point. I've just tried a fresh setup, restoring only data for user apps. We'll see how things go.
Title says it all, made the mistake of upgrading to Oreo and now stuck with relentless battery drain issues. Tried everything short of reflashing so far and failed. Nearly everything is disabled even after full wipe and reset (hard) and its still pretty bad in terms of battery life. So I signed up here looking for ways to salvage the hardware, perhaps by downgrading back to Nougat if I still can or installing something better and different altogether. I've read folks having luck with the cell standby drain by installing a nougat/oreo mash but couldn't find specific details on how to do this. Also this doesn't seem to fix the android system drain issue but its at least a start. I have basic experience using Kies and Odin, helped a couple relatives with boot looping tabs in the past. Please advise on the best path forward to make use of my new phone.
Have you tried installing 7.0?
What version of Oreo did you install? I myself installed a TMO Ver G930TUVU4CRI2 but running on ATT network. I rooted and debloated and I am blown away how smooth this runs with fantastic battery life.
Read Here Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
edwardmorris said:
Title says it all, made the mistake of upgrading to Oreo and now stuck with relentless battery drain issues. Tried everything short of reflashing so far and failed. Nearly everything is disabled even after full wipe and reset (hard) and its still pretty bad in terms of battery life. So I signed up here looking for ways to salvage the hardware, perhaps by downgrading back to Nougat if I still can or installing something better and different altogether. I've read folks having luck with the cell standby drain by installing a nougat/oreo mash but couldn't find specific details on how to do this. Also this doesn't seem to fix the android system drain issue but its at least a start. I have basic experience using Kies and Odin, helped a couple relatives with boot looping tabs in the past. Please advise on the best path forward to make use of my new phone.
Click to expand...
Click to collapse
I feel your pain. I was in the same situation, spending days to find a solution to these battery drain while stuck on this buggy version. And I tried everything...basic battery saving related stuff, disabling pretty much everything on the phone, monitoring everything, even changing the battery.
For now, the only thing that fix the problem for me was using a 3rd party app to force the phone to connect to none LTE network. I don't know where the bug lies: android, samsung or att side? or maybe it is because I'm out of US on another carrier who is using other freq but it is a shame. I don't think there will ever be a fix for that unfortunatly...