Hello,
In the recent few months, my phone keeps rebooting by itself, even when it is on the desk for hours without getting bothered.
The funny thing is that this is a soft reboot, because there isn't any Google splashscreen. The problem persist through different ROMs and kernels.
Things I tried already:
- swap ROM (PureNexus 7.1 -> NitrogenOS 8.1)
- swap kernel (Franco kernel -> ElementalX kernel)
- factory reset, wipe caches
- decrypt device
- use 3G instead of 4G
- swap radio
- increasing and decreasing CPU voltage and clock
- changing CPU governor
I attach two logs from two different reboots, also the related .rc file.
In the logs, you can see a line similiar to this:
Code:
[310842.492056] init: processing action (sys.shutdown.requested=*) from (/init.shamu.rc:578)
What causes the reboots? Could it be a defective battery issue?
Not a defective battery, but a tired one. Batteries wear out after being used constantly for two years. I know this because I too get the random reboots, though mine does not occur daily like yours apparently does. You can clear the bootloader logs and immediately recharge for a temporary fix, but you will eventually want to replace the battery.
I just replaced my battery yesterday with a new OEM one. Had my phone for 2.5 years so I thought why not. When I took my old one out, it was actually in very good condition but there were some bubble marks around it indicating it overheated at some point.
Nevertheless, I've had random reboots, but the new battery so far hasn't rebooted m phone yet. The process to replace very pretty simple, just need a tool to pry the back cover off and carefully make sure you don't pull it off with too much force. Then there are 22 T4 torx screws.
In my case I'm simply going to live with it, because I plan on switching to a Pixel 2XL later this year. In any event I can't be certain mine is a battery issue as I only encountered this after using Android 8.x ROMs. I just haven't bothered to delve into it.
Oh, I forgot to mention that I tried to wipe the bootloader logs too. No success so far.
I think I order a replacement battery and try to sell the phone with that.
I also plan to switch to a newer model. It seems it is time to switch.
Thanks for the help, guys!
Related
Hello xda!
Lately my phone has been acting real crazy. I've been on Cognition rom for about a month and I never experienced any issue. However, after flashing SpeedMod k12t, my phone kept freezing while on sleep after 1-2 hours of use. I decided to reflash firebird 2 to make sure it wasn't the new kernel, but my phone recently froze in screen off. I am now sure this has nothing to do with a specific kernel. I have been trying to figure out what's wrong with my phone. I am pretty sure it has nothing to do with my modem either, since I have been using jk4 for about a week or three and this issue never came up until now.
All I'm really thinking of would be my setcpu settings. I recently started to use profiles with the following settings :
Screen off : 200-200 performance (now 400)
Charging : 1000
Battery < 101% : 800 - 1000 conservative
Battery < 39% : 400 - 800
I am thinking the screen off settings are causing all of this trouble. I only started using these a day or two before all of this started. Back then I was testing out a couple different kernel (suckerpunch, gb's kernel, firebird, speedmod). I had a rather poor uptime with suckerpunch because it took a while for me to find the correct settings, and when I did, I remember getting a sleep death that I blamed on the kernel because of the history of charge death it had back then.
Also, my original kernel was firebird and my phone was quite stable during the 3 weeks I've used it. I'm leaving the possibility of a bad kernel away because of this.
So here's my question, xda : What's up with my phone? Is reflashing back to stock and back to Cognition the only possible fix for this? Could me flashing kernels without disabling voodoo be the cause of all of this? Could disabling voodoo and reflashing the kernel fix this? Can set cpu be the cause of all of my trouble (i disabled it for now).
Thanks,
I have the same exact problem and it drives me insane. I have no solution for it except if your last 4 IMEI numbers (under your battery) are below 6000. Mine is 8355 so i dont know.
The last four numbers under my battery are 6, 5, 5, and 9. 6559. This only started a day or two ago. I've only had this phone for a month. So far the problem seems gone, but I've noticed my battery went from 67% to 80 after rebooting my phone to check the numbers under my battery. I recently wiped my battery stats though.
I've only had my phone for about a month too, so i don't know any more than you do. The only thing different for me is the shutdowns were already happening, and the the ROM I flashed just increased it.
Yeah, my phone also seems to freeze when alseep but only if its charging. Sometimes if i disconnect it, it will freeze or if i get a phone call while its charging.
My Captivate had sleep death (randomly) and charge death on some ROMs. After flashing several combinations of ROM/kernel/modem, it seems ok now. I think I will keep on finding a better combination.
SetCPU has some issue with OC/UV kernel on my Captivate, so if you have the same problem try to disable SetCPU first and see if the problem goes away.
Hi
On Thursday I received a new battery in the post (my current battery life was abysmal) anyway i changed the battery to charge the new one. After starting the phone i had to select a new language etc. and found that a huge number of my apps were giving the a force close errors. I decided to factory reset my phone, re-downloaded the apps and found the problem resolved.
However earlier today i switched batteries again (wasn't sure that was the cause last time) and it has happened again. Any Suggestions on what is causing it and how to avoid it in the future (other than simply not replacing the battery) or how to rectify it.
Fake/Faulty battery.
jje
No the battery is genuine samsung from a reputable retailer.
If you have to select a new language, it probably means your phone's internal battery has died. Try taking out the battery for 5 minutes, and see if the clock is still accurate.
knowledge is Power. Guard it well.
reallymoreish said:
Hi
On Thursday I received a new battery in the post (my current battery life was abysmal) anyway i changed the battery to charge the new one. After starting the phone i had to select a new language etc. and found that a huge number of my apps were giving the a force close errors. I decided to factory reset my phone, re-downloaded the apps and found the problem resolved.
However earlier today i switched batteries again (wasn't sure that was the cause last time) and it has happened again. Any Suggestions on what is causing it and how to avoid it in the future (other than simply not replacing the battery) or how to rectify it.
Click to expand...
Click to collapse
Are you sure you are letting the phone shut down properly?? When you think it's shut down, press one of the capacitive buttons, if they light up wait until phone vibrates and lights go out, then swap battery. Had the same happen to me a couple of times.
Hello! Me and some other people had similar issues. Read this thread:
forum.xda-developers.com/showthread.php?t=1022044
It looks impossible but I start to believe that a faulty (or a cheap noname) battery can cause problems like this.
I have two spare cheap ebay batteries. I always pop the battery out with the phone still turned on and never a problem...
Device: Samsung Galaxy S GT i9000
Symptoms:
When Charging Device is hot to the Touch in the upper half of the screen and on the rear between the camera and the heat vent.
Battery drains at around 15-25% per hour when IDLE. 15% when in deep sleep in airplane mode with ALL APPS KILLED. 25% when I leave ALL network connections open and allow sync.
Phone was new less than 2 months ago. Still under warranty and I will send it back if no ideas come from this but wanted to see if anyone had a solution as I have noticed HUNDREDS of similar posts all vaguely scattered through different threads on different sites around the web and this seems like the definitive place to come to see if anyone can put their finger on it.
When did this occur?:
A short while after (days) of flashing CM9 nightly from the beginning of June (05/06 I think but can't recall exactly).
Tests performed:
Purchased new battery and fully charged - no change.
Flashed stock GB ROMs where the issue had not occured - no change.
Cleared battery stats several times - no change.
Tried different modems/radios including Nexus S radios- no result
Current ROM: CM 7.2
Kernel: Glitch 13.1
Other ROMs/Kernels where the same results were achieved...
CM9 (latest nightlies)
Stock JVU, JVS, JW4 and JW5
Semaphore Kernel, Devils Kernel
I use Voodoo Sound/Colour kernels apart from the testing I did with stock ROMs
Will leave it on over night after clearing stats so you can see for yourselves.
Any questions ask away.
I should add:
Used OS Monitor and one of the more detailed CPU monitors to look at what was going on.
Did not appear at any time to be using what I would consider high CPU utilisation, typically trending between 0 and 30ish. No background apps running, all radios turned off.
The only anomaly that stuck out at me is that system_server was using ~105% of RAM which I would have thought was rather difficult. Made me wonder if there was something loading/unloading itself from RAM.
As I am a heavy music user I have tested the Mediaserver issue where corrupt files are continually scanned by mediaserver process. Removed all media files from both my external and internal storage then formatted both while on a stock ROM (JVU and JW4). There was no change.
EDIT: I should add - The thing that makes this so strange to me is that the battery decreases at a rapid rate when Battery stats regarding usage DO NOT CHANGE. The percentages for the apps that WERE using the battery - i.e. winamp/mediaserver/android system do not change.
The reason I have posted this is that i have seen literally HUNDREDS of people posting this very same issue but never in the same place and never getting an answer.
Also - Thankyou to the kind mod/admin who approved my account so I can edit stuff. It was getting a bit annoying for the first week there.
Re
Hi,
To be honest I never heard/read of the problem you are describing. Most users report high battery drain on a certain ROM/kernel/modem but you say you have tried quite a lot.
If the phone is new, the only thing that comes to mind is that the USB charging socket is faulty. It may not charge properly or even have some bad connectors that are damaging the battery.
In any case, Samsung support is the way to go here.
Hope this helps
OMG, im having the same exact problem... the phone is super hot on the back where the sim card is inserted. I did everything as you, still no change, my battery lasts like 7 hours on deep sleep. Guess our phone is broken. super crap.
Anyone knows how to fix this? Is there anyway that my phone has some files from previous custom roms even though used odin to flash samsung original ones?
Had the same problem when my device was only 6 months old, the battery was becoming faulty, got a new battery and problem solved.
I bought a new battery and i still have the same problem... which battery did u get?
streakpt said:
I bought a new battery and i still have the same problem... which battery did u get?
Click to expand...
Click to collapse
An official samsung battery from Amazon, re flash you device with another rom and wipe battery stats.
Did all that, the problem still continues... mega battery drain and the phone is at 44C degrees... is there any tool i can use to diagnose the problem?
Hi snaleman,
You could try BetterBatteryStats, to help diagnose your issue further, there is a paid version on the market (Google Play Store). There is also a thread on this forum, from the dev....hint
I tried winamp for android, ages ago, but had similar issues. (This player might well be your issue.) So I now use "PowerAmp". Neutron MP is cool too.
Also, do you use lippol94's kernel cleaning script. I use this every kernel/ROM change.
Search here for this:
ultimate_kernel_cleaning_script
Hope this info helps your baby.
Hey
U can try to flash a stock rom from sammmobile.com..
Use it for a few days and check...may help u..
Cheers
Sent from my GT-I9000 using xda app-developers app
Backup your apps with titanium backup or something else.
Make a backup from CWM recovery
Wipe data/cache/dalvik
Restore user apps and not system app
If your problem is not fixed you can restore your CWM backup
Nothing you guys posted worked... battery lasts 11 hours on sleep...
Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.
If you are using the Voodoo sound app that may be the cause. I've noticed on my phone that deep sleep no longer works when the voodoo app is installed, most likely the app is holding a partial wake lock and not releasing it.
See if it happens with the app uninstalled or frozen.
Sent from my Nexus 7 using Tapatalk 2
Signal Strength¿
streakpt said:
Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.
Click to expand...
Click to collapse
You've just made me think of something else that it may be.
Do you have 4 or 5 bars of signal strength?
I've found when in certain areas (very close to "deadspots" in network reception), that if I use another frequency, [eg. 900 & 2100 (for my network), yours may be different] I can get a better signal, also much better battery life, as the phone is not struggling to reach the network.
If you use your dialer to enter this code
*#*#197328640#*#*
Then
[1] DEBUG SCREEN
THEN
[8] PHONE CONTROL
then
[7] NETWORK CONTROL
then
[2] BAND SELECTION
you will then have a selection of frequencies available. The asterisk * will tell you what one(s) is/are active.
"Google" your network service providers frequency bands. I found mine were on a "Wiki" page.
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch. Betterbatterystats gave a temperature of 52C and avg of 50. Needless to say, my battery also runs out very quickly like this, also dropping about 5% an hour when the screen is off.
Another thing I've noticed is that SDcard takes 25% of my battery usage, and when I go to storage settings, it will infinitely calculate. I mounted my storages and chkdsked them, fixed some corrupted files but the problem still persists. The only storage I haven't mounted is the internal storage, which I'm unable to do. I can't seem to connect to adb from recovery and mounting /data alone does nothing. After about 10 mins of using the phone, it becomes too hot(burns my hand) and it will shut down.
I've replaced 2 batteries so it's very unlikely that it's a battery issue. Also tried other chargers and wiping everything.
Phone OS: 4.1.2 stock LT5 before.
Did factory wipe/dalvik wipe + flash to CM11 4.4.4 and the problem is still present.
Betterbatterystats doesn't indicate a draining app, just high temperature.
Removing the external SD card and sim card had no impact.
I'm getting deep sleep when I turn off the screen, so it's not media scan being stuck. Mediascan disabled and problem still persists.
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Poopfeast said:
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch.....
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Click to expand...
Click to collapse
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
julian67 said:
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
Click to expand...
Click to collapse
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
edit: just flashed to omnirom and it's still burning my hand.
In the team win recovery repairing internal storage gives me the error: unable to repair /emmc, so I just wiped it, problem is still there.
Poopfeast said:
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
Click to expand...
Click to collapse
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
julian67 said:
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
Click to expand...
Click to collapse
Thanks for taking your time to write this. I've already disabled GPS/sync and turned on power saving. Clearing the storage now lets android calculate properly, and the Media/sdcard is gone from battery usage. But it's still running very hot and draining. CPUspy says 20% on 1400 and the rest on 800mhz when I'm using it. The system is freezing often and generally really slow.
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.
Temperature seems to drop to a reasonable 35C when I'm in airplane mode.
With everything on and sync off it's not going above 40C even when watching videos or something, so I guess it's all good now.
So basically what I've done to fix it:
Wipe internal storage and repair all partitions
Flash to OmniROM
Turn off Sync/GPS
Problem seemed to be mainly on the internal storage corruption, maybe related to my bugged chip.
Poopfeast said:
.....
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.......maybe related to my bugged chip.
Click to expand...
Click to collapse
According to eMMC Brickbug Check my Note is exactly the same as yours - supposedly "Insane chip" but Memory check passed with no problems, and guess what? It works 100% perfectly running 4.1.2 rooted. I have the full capacity of storage available to me, apps do not freeze, everything works as good as new. It is absolutely stable and reliable and terribly boring (just how I like it). It never surprises me or does any weird stuff at boot or crashes or freezes. All the hardware features work, all the supported video and audio codecs and formats work, the networking is rock solid, I can rely on my VPN when away from home, GPS gets a fix in no time, battery life is excellent, video playback is great etc. etc..
I bought my 16GB GT-N7000 a few months ago, a used item on ebay. It is an unlocked retail UK item (boxed with all manuals, paperwork, accessories etc) so no network/vendor bloatware but it was supplied by the seller with Supernexus ROM installed and was obviously suffering from the usual problems often described by users of custom ROMs on exynos. After various frustrating episodes and trials of different ROMs I used ODIN 3.09 to flash an official Samsung ICS 4.04 firmware and 16GB pit file to restore the partition table and stock firmware. Then I ran Kies on Windows XP on the "virgin" restoration. It recognised the hardware and the firmware and notified me of the update to 4.1.2. I went ahead and updated over ethernet and also captured the official 4.1.2 firmware for purpose of backup.
Since then I have tried out various ROMs and have always been able to revert to stock Samsung 4.1.2 via ODIN and without going back to the scary brickbug "insane" ICS versions. As far as I can tell the brick bug is irrelevant if you aren't stuck on ICS. After trying numerous ROMs of various android versions I am in no doubt at all that if you spend half the time setting up a rooted stock Samsung firmware as most people spend setting up ROM X/Y/Z you actually get a much more reliable and useful device.
If you need a known-good pit file for a 16GB GT-N7000 you can use this: ftp://takla.linuxd.org/Q1_20110914_16GB.pit
I had a similar issue lately. Go to developer settings and activate the cpu load display. Processes and their cpu load along with a bar graph will appear on the screen. I found out that google's music app was hanging on my phone. This did not show up in BetterBatteryStats!!!
I have had my international unlocked M7 for almost 2½ years now. For the past 6 months or so I have had weird battery problems.
When on the lower half of the percentage, i.e. below 50%, sometimes it drops incredibly fast, and the phone just dies. At times it goes from 30% to nothing for instance. When I add the charger it lists the battery as 2-5% or something.
Nothing gets hot, and I have tried to use the saver functionality. I don't think there are any apps that cause this, I have tried to keep an eye on it.
I have also tried GSAM, but it didn't tell me anything new - I can install it again and post some logs, if that would be helpful.
What I have done:
* Recently I went to a shop and had the battery replaced, since I assumed this was the problem (battery getting old), but it didn't changed anything. There is, of course, a remote chance that the shop screwed up and didn't replace the battery and screwed me - I have no way of telling...
* I have also recently rooted/unlocked/wiped all caches and installed a ROM from here (Eragon), but that didn't change anything either...
My only conclusion is that this must be a hardware problem - am I correct in assuming that?
Any help/tips are welcome!
Thanks!