Sup people,
I posted a thread last week on here,
http://forum.xda-developers.com/showthread.php?t=1349334&page=2
about my battery drain issue and since then ive even replaced the battery for a new one.
My phone still eats through battery life and its showing "android OS" and being the biggest drain in the battery stats.
I have had this problem across loads of Roms and Kernels, I went to the new ICS build the other day and im still having issues.
Can anyone tell me what my options are from here? What is their left that could be doing it? im baffled.
Im not sure if its related but recently ive had a few instances were the phone would jump back to the "enter pin" screen even though it was on and sometimes in use at the time.
I appriciate any help on this guys.
When you are flashing new roms, are you reloading all your previous apps?
If so, I would start fresh. Maybe stock rom, no backed up apps. Let it run, and monitor hat might be draining. I know this happened to me a while ago, and YouTube as the culprit. I removed and reinstalled, issue fixed.
I have done, but with the last few roms I didn't restore anything from the previous rom. I didnt even sign into my google account with it, sync was disabled, wifi too.
That's whats baffling me about it. I cant imagine there's anything left on it that was there from the previous rom so I'm stuck for ideas as to whats causing the drain.
I've wiped everything in Clockwork Mod too with no success.
Is it possible the phone has a hardware problem?
Is it possible to go back to stock rom and stock recovery? Im thinking about returning the phone if there's a hardware problem.
Spectre Nine said:
Is it possible to go back to stock rom and stock recovery? Im thinking about returning the phone if there's a hardware problem.
Click to expand...
Click to collapse
as i have just written in another thread. to return to complete stock, you can use Odin, a Samsung tool, that you can download on their support section, just google it...the respective rom-image you can find here in the forum. just search a little, i found it quite easily when i had to return my phone due to a hardware problem...
good luck!
try using the launcher fron the link below...it dropped my battery usage for "android OS' to 2%
http://forum.xda-developers.com/showthread.php?t=1121294
Dark Launcher2 For CM7.1.0 Install with CWM to against (Android System) battery drain
Sent from my Nexus S 4G using XDA Premium App
I think I wrote this in your other thread but download Better Battery Stats from the market and look at your partial wakelocks since unplugged. this will tell you exactly what is eating the battery and what percent it accounts for.
In the battery use graph in android do you have a lot of time spent awake when the screen is off. You said you didnt sign in to your google account and wifi was disabled. Did you connect to your mobile netowrk though? Searching for a network can really drain the battery fast. Do you still have a lot of drain in airplane mode?
How fast does your battery drain? Can you put up a screenshot of the battery graph from 100% charge to somewhere below 50%
hi, thanks for the reply,
I tried to get the battery stats app but couldnt find it in the market. i get the drain when connected to 3g, when in airplane mode, when connected to wifi, when not connected to wifi.
I'll get some more pics of the battery stats, it basically drains in around 5-7 hours when not used at all, much less if it is actually used.
@petarsson Oh i didnt think odin worked with the nexus s, i thought it was only for samsungs own branded phones. I'll look into that.
PS, i dont know if its related but i have a lot of files on the sd that are generated by themselves and are called "radio_dump_20111123123340.bin" etc. Anyone know what these are about and why i have so many of them?
I have 481mb of them since yesterday'ish.
Spectre Nine said:
PS, i dont know if its related but i have a lot of files on the sd that are generated by themselves and are called "radio_dump_20111123123340.bin" etc. Anyone know what these are about and why i have so many of them?
I have 481mb of them since yesterday'ish.
Click to expand...
Click to collapse
Those are generated when your radio crashes. What radio are you using. If your problem persists on different rom's and kernels it very well could be the radio.
Its called betterbatterystats in the market and it costs like $2
---------- Post added at 09:34 PM ---------- Previous post was at 09:12 PM ----------
This is what I suggest you do
- in android go to settings> privacy factory reset data
- go to settings>storage and erase USB data
-boot to recovery and wipe data/factory reset and format SD card
-wipe cache and wipe dalvik
-flash a stock rom like blandroid
-flash the kf1 radio
-boot up don't sign in to Google account and go right in to airplane mode
-if you still have battery problems its most likely a hardware defect
thanks again mate, its pretty late here at the moment but ill give it a go in the morning. cheers.
I'm having similar issues. I had great battery life but lately i have a lot of awake when the phone is off.did change kernels around a bit but always wiped cache and dalvik and I've been using titanium to freeze new apps i though could be causing it but i cant seem to find it. Going back to original kernel i was running hasn't solved the problem.
BetterBattery stats shows SyncManagerHandlesSyncAlarm and AlarmManager as keeping the phone awake a lot.
I am on stock and latest glados kernel.
red_skittles said:
This is what I suggest you do
- in android go to settings> privacy factory reset data
- go to settings>storage and erase USB data
-boot to recovery and wipe data/factory reset and format SD card
-wipe cache and wipe dalvik
-flash a stock rom like blandroid
-flash the kf1 radio
-boot up don't sign in to Google account and go right in to airplane mode
-if you still have battery problems its most likely a hardware defect
Click to expand...
Click to collapse
Hiya mate,
Im gonna give this a go later on since i have the time. At the moment I have my phone fully restored to 2.3.6 with stock recovery and locked bootloader as I was about to return it to the shop.
Can you answer me this though, Would the radio.img be updated with each rom I install? Or is the same radio image left untouched when i flash a rom?
cheers.
Related
So the excitement of the nexus s is still flowing through my veins. I have now switched 2 radios and 3 roms.
I recently went from SuperOSR to Zulugen. Yesterday I had a MAJOR crash. My google voice froze up sending a text. Even after a reboot it was stuck in a sending loop. I then decided to turn off data and see if that worked but that only made it worse as i couldnt turn my data back on. I then force closed it which started bombarding my phone with force close errors.
THEN CRAAAAAAAAAAASH force close errors every 2 secs, no data (even after the *#*# reset.
I tried restoring to an earlier image i took but forgot it crashed during that too and the image was bad. I then just restored back to the base rom and redid my phone after doing the *#*# baseband settings just for good measure.
these are the apps i THINK were responsible for the crashing. Proton Voltage, Cache Cleaner NG, PREY
I will stay away from Proton for now, and have put CC NG back on but removed certain system actions and apps i DONT want it to touch. As of now prey is on it but not active.
anyway here is my question
When you change your base-band radio do you ALWAYS have to do the *#*# or just if you lose your 3?
Can the wrong radio cause issues with a certain ROM? I am running UCKD1 as of now with zulugen. second time around it seems good but who knows and I always wipe data between roms.
I have asked the question earlier but in the wrong section, as Im still getting the hang of where to post things here but anyone from the New England area have a good suggestion on a specific radio? Im in ct near the water, the dead zone of signal ESPECIALLY for ATT
If I flash my E! radio back (either the image i took or the one form the thread) it states to back up your EFS which i did. But why does it ask this, should i worry going back to the original E1 radio?
Do i have nice shoes?
thanks
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.
beavermjr said:
I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.
Click to expand...
Click to collapse
You mean Tweaked 3.2, right... if not first upgrade to the 3.2 version of the ROM... it is the current FP5 option.
There is a build.prop thing commented out at the bottom that should force launcher into memory (supposed to help with screen redraw issues, but might also help with general responsiveness). I think you could do it from root explorer, just edit the file, scrool down, read comments, when you find one that sounds like what I said just remove the "#" from the line below it.
re-installing tweaked might really help...
but you might try going into CWM and wiping cache only... NOT data & cache... JUST CACHE... that helped me when i had "funky" things going on on a different device/ROM worth a try.
Finally, you should always take a CWM backup, Nandroid, before poking around....
Also... check swappa for relatively cheap phones with no ties to VZW contract it is where i picked up the GN2 (if it is rooted and you don't want to show it off at the corp store, just call customer support say you are too busy store hours. They will send you the micro/mini SIM via FedEx.
Of course take what I say with a grain of salt... I am just a crazy guy from the internet
(oh great XDA... please correct me if I've misspoken)
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
I will never tell someone "don't say it click the button"... However, I'm like pavlov's dog clicking the button is appreciated...
Not sure about a dirty flash... Never tried it. I got turned on to Root and Such well after FP5 and Tweaked 3.2 came out.
If you give it a go... You could retain much via Titanium Backup. Or just send a CWM Backup/Nandroid on the SD Card before playing around.
Either way...
There has to be a proper stop notification how to thread around here somewhere!
Cliffs Notes:
From a Root Friendly File Explorer (Like Root Explorer HERE, it is worth the $)
edit a line in "/system/build.prop"
Find
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP5:user/release-keys
replace the FP5 with FP8 so it reads:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP8:user/release-keys
NOTE: BE VERY CAREFUL NOT TO HOSE THE PERMISSIONS (If I recall some of the other "freebie" root file explorers break the permissions... Best to find that a real thread with all the details if you are not 100% confident.)
Also feel free to double check my facts... I'm just a crazy guy from the internet!
Good luck!
Edit Alert:
PS. While poking around at the tweaktools back-end, I noticed there were some mods that specifically addressed lag (I have little to no experience with them though... Just FYI...
beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
yes, you can flash tweak 3.2 over 3.0 without wiping data. not sure if it comes with the updated kernel, but I would certainly do that as well.
in terms of lag, try the crossbreeder mod on XDA - worked for my charge!
i just got my note pro 12.2 wifi version (international) a few days ago and already experiencing problems, firstly the wifi was so slow so i updated it OTA to the latest stock firmware i can't remember what it is but it's the latest official 4.4.2 they have and that improved the wifi but now i'm encountering issues of rebooting randomly after using facebook app. it's always after i lock the screen it suddenly reboots after 2 mins or something especially if i have say been using a lot of memory for it.. ie if i scroll down 4000 friends that's when it always reboots once i lock the screen. is this liekly to be hardware or software issue or an app issue?
i have only had it a few days so haven't managed to play with it enough to test it to the max.
just now it rebooted and i played one youtube HD video and used multi window to use the facebook app (old version 7.0 - i like this version).. but i hadn't used the facebook app that much while on, the only thing i did different was i plugged in my samsung s3 charger into the note pro to test how long it would take to charge using a usb 2.0 connection instead. it's official charger official cable, is that likely to cause reboot issues?
previously it was just after using facebook for a long time for a ram intensive amount, i also tested it after reboot and using facebook a bit and locking screen and it didn't reboot so it made me think ok it's just when facebook is being used a lot and all the ram and memory is exhausted caching 4000 friends viewing so i didn't think anything of it.
is this likely to be hardware or software issue? are hardware issues ever the main problem with rebooting?
I know the usual tests, having to use odin to flash official firmware, trying a different facebook version, removing and not using facebook at all and see if it still reboots and lastly factory reset.
ideally i'd like to avoid all of those things as it is a major hassle and i can live with the reboot issue provided it isn't a hardware problem. is there anyway to test it to know for certain it is hardware and not software and the app?
edit: it keeps rebooting even if i dont use the app
seems to happen when i lock the screen sometimes it just reboots randomly.
anyone else have this?
You could try to remove that facebook app and see if that fixes the problem.
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
pete101 said:
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
Click to expand...
Click to collapse
Could it be a bad sector on the SD card? I'd long format it using a pc to be sure.
Sent from my SM-P900 using Tapatalk
it's not the faceboook k app i've realised now it just coincidentally seemed to be that as it is ram intensive.
i factory reseted and then put the app back on but didn't log in. 3 times it has rebooted by itself over different scenarios.. 1 plugging in a samsung usb 2.0 charger from a samsung s3, 2 when unmounting sd card, 3 when closing the screen when any ram intensive app is in the background (there's still like 500mb of ram left!! i dont know why it's rebooting like this.
i can't figure it out. is anyone else having these issues? im not sure if it's a kitkat 4.4.2 issue.. reading forums from other users with different devices i'm seeing the reboot issue coming up alot especially on the s4.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046/page22
but i dont know for certain if it's a hardware issue.
my next steps which i really want to avoid is to factory reset AGAIN and not load any apps (the problem with this is it requires a certain amount of ram intensity to be used before it randomly happens.. if i dont add any apps like instagram or facebook or tumblr i can't get it back to the state where it reboots randomly)
i've also enabled all apps (i usually disable all the bloatware i can without being rooted) but it does bring up errors of android.core.process has stopped etc and some gapps errors (im hoping this is the cause of the reboot) and see if it reboots. it's difficult recreating the scenario consistently.
i udnerstand it might reboot if you've overused the memory but it clearly shows lots is free so i can't figure out what is causing it?
my next step after all this is to flash the latest version of stock so i can't put it down to the OTA updates that is causing it. if that fails i revert to odin to flash the original 4.4.2 it came with.. and failing that i'll have to return it
does anyone have any ideas whether it is hardware (maybe the power button is slightly off so when you press down it in a certain angle it triggers a restart?)
or is the motherboard or corrupted sector of the memory which when it writes over it causes the reboot?
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
If it were me I would yank the microsd card out, factory reset, set up just my gmail without allowing auto backup/restore and apply all updates. I'd then let the tablet run for a full day and use it just for web browsing and Youtube to see if the problem is still there. I would not install anything for at least a day, including the microsd card. This would be as stock as one could get and rule out the possibility of it being any software that I installed or the microsd that I was using.
I suspect it's software but the only way to know is to be patient and test it out for sure.
Sent from my SM-P900 using Tapatalk
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
orobin said:
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
Click to expand...
Click to collapse
Assuming you have custom recovery installed as well; have you tried wiping dalvic? It will force applications to recompile and possibly fix a corrupted application or its associated files.
Hi,
I just checke.…
I was thinking that the root method was not setting the knox flag, so i was thinking there is no recovery in the file flashed… .
I was wrong.
My waranty is void, knox is set. I still have no custom recovery : in the file provided by chainfire, there is a recovery which is probably coming from samsunG…
So i will install a new recovery and try to wipe all caches dalvik.etc.
Hi,
since my knox is set now :
I tried to install TWRP recovery, which allow me to do a wipe of the cache AND dalvik Cache.
it did not resolved anything. the tablet still reboots randomly.
then, I decided to restart from scratch :
I flashed the same firmware I had, using ODIN, and do not root it.
this is this firmware : http://www.sammobile.com/firmwares/database/SM-P900/XEF/
I will keep you updated if it solve the reboot issue or not.
thanks
Olivier
pete101 said:
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
Click to expand...
Click to collapse
Hi
I had the same problem and also thought it was the power button that was faulty but then I flashed the previous firmware then tried to use it a bit and no reboots since so I guess samsung released a new firmware that solved the slow wifi problem but then boosted it a little too much or so it seems judging by the reboots whenever there's too much overload.
So I guess for now I will stick with an older firmware
oops... it rebooted while I was surfing the play store so I guess I spoke too soon
Hello!
I'm on Holiday and have a big problem with my OPO. I use Lineageos 14.1 (Build from march) and after the battery was empty yesterday I have a lot of problems today:
- no wifi connection. It is not possible to switch it on or off. No wlan is recognized.
- it is not possible to reboot or shutdown the phone. I need to press the powerbutton for 10seconds
- the battery monitor shows nothing. No power usage of the apps and no battery chart.
- the phone is getting hot and has a really high battery drain.
This problems occured after the empty battery yesterday.
I already wiped dalviak and Cache and updated to the latest build. No change.
Do you have an idea? As I said I am on holiday and the day befor my wife laptop's SSD died- so I have very limited possibilities. As wifi is not working, I write this with an IPhone, which is no fun
I downloaded the update on my OPO by cellular which is still working but no good idea because of limited data plan...
Many thanks for your help!
El-Chico said:
Hello!
I'm on Holiday and have a big problem with my OPO. I use Lineageos 14.1 (Build from march) and after the battery was empty yesterday I have a lot of problems today:
- no wifi connection. It is not possible to switch it on or off. No wlan is recognized.
- it is not possible to reboot or shutdown the phone. I need to press the powerbutton for 10seconds
- the battery monitor shows nothing. No power usage of the apps and no battery chart.
- the phone is getting hot and has a really high battery drain.
This problems occured after the empty battery yesterday.
I already wiped dalviak and Cache and updated to the latest build. No change.
Do you have an idea? As I said I am on holiday and the day befor my wife laptop's SSD died- so I have very limited possibilities. As wifi is not working, I write this with an IPhone, which is no fun
I downloaded the update on my OPO by cellular which is still working but no good idea because of limited data plan...
Many thanks for your help!
Click to expand...
Click to collapse
Factory reset?
That would hopefully help- but I will loose all my apps...
A question: will my pics and downloads still be there? Maybe I make a Titanium backup, do a factory reset, restore the backup and everything will be fine?
What data will I loose?apps and the folder "Android"?
And: reset in Anroid or TWRP?
Many thanks!
It works! It seems, that the wifi settings were corrupt. I read a solution here: https://android.stackexchange.com/questions/28567/how-to-reset-wi-fi-settings
I deleted the file /data/misc/wifi/wpa_supplicant.conf , rebooted and now wifi is connected again.
I See the battery chart and can reboot with the restart menu
El-Chico said:
That would hopefully help- but I will loose all my apps...
A question: will my pics and downloads still be there? Maybe I make a Titanium backup, do a factory reset, restore the backup and everything will be fine?
What data will I loose?apps and the folder "Android"?
And: reset in Anroid or TWRP?
Many thanks!
Click to expand...
Click to collapse
If you factory reset from TWRP, internal storage won't be touched hence photos and files will remain. But data partition will be wiped and that contains the apps and their saved info.
El-Chico said:
It works! It seems, that the wifi settings were corrupt. I read a solution here: https://android.stackexchange.com/questions/28567/how-to-reset-wi-fi-settings
I deleted the file /data/misc/wifi/wpa_supplicant.conf , rebooted and now wifi is connected again.
I See the battery chart and can reboot with the restart menu
Click to expand...
Click to collapse
Glad to know it worked without factory reset.
Factory reset when on holidays is hectic anyway.
Enjoy your holidays!
Thanks I don't wanted it hectic, my wife was already nerved by repairing my phone
And another information: before the phone was empty, I installed the facebook APP and allowed the Option "show nearby wifi" (I don't know the real english translation for this).
Maybe this had to do with the damaged wifi settings...
El-Chico said:
Thanks I don't wanted it hectic, my wife was already nerved by repairing my phone
And another information: before the phone was empty, I installed the facebook APP and allowed the Option "show nearby wifi" (I don't know the real english translation for this).
Maybe this had to do with the damaged wifi settings...
Click to expand...
Click to collapse
I doubt,even if it is,it's limited to fb app only.