From time to time my N910F falls into a state of being permanently awake.
The symptoms:
1. Battery drain
2. On the standard Android Battery Statistics page, Android OS and Android system are the major battery consumers (normally it's either the Display or Cell standby)
3. Standard Android Battery Statistics page shows that the phone is NOT always awake (the corresponding line is NOT all blue). So according to the standard Battery page the phone IS sleeping.
4. Programs like BetterBatteryStats and WakeLock Detector show that the phone is AWAKE 100% of the time. The sleeping time is ZERO.
The ONLY solution is to reboot, after which the phone is back to normal. It can stay that way for several hours or even several days, but sooner or later (usually within a couple of days) it falls into that battery-draining-always-awake state again.
Looks like I've tried almost everything: freezing different apps, switching off and on WiFi, Mobile Data, NFC, GPS etc., putting the phone into Airplane Mode, charging the phone, uninstalling some apps... Nothing worked - the phone stays awake until you reboot it. I don't know where else to look! Desperate! Need help badly! Please, help!
Did you try a factory reset?
5parc said:
Did you try a factory reset?
Click to expand...
Click to collapse
You could say I did.
The thing is I had the exact same problem on the previous ROM (Germany 4.4.4 KitKat). To get rid of the problem I decided to take some drastic steps and flashed a new ROM (United Kingdom 4.4.4 KitKat). Before I did that, I formatted System, Data and Internal Storage. So it was a 100% brand new and clean ROM. And then, after I installed all my usual apps, the problem came back... :crying:
I'm enclosing Betterbatterystats logs (see the attachment) during this non-sleeping mode. Hope it'll help somebody to help me...
Looks like the problem is not fixable
First of all, I figured out what causes the phone to go into this non-sleeping mode. It's uploading large size photos (from camera) to one of the online services via cellular network (3G). Uploads via WiFi don't seem to be affected. Uploading small size photos also doesn't seem to cause any problem.
Some of the apps causing the problem:
1. Endomondo (if you attach a photo from camera to your workout and then upload it, you'll enavitably get that no-deep-sleep mode)
2. Kate Mobile (for VK) - if you choose not to reduce the size of photos before uploading them, you'll get the problem 100%. If the size is reduced before uploading, the problem doesn't show up.
3. Viber (sending one photo doesn't usually cause the problem, but sending several at once will defifnitely put the phone into no-deep-sleep state)
I'm sure there are many other apps that will cause the problem if used to upload files via 3G - those above are just the ones I'm using
And now comes the saddest part
I did the following:
1. Cleared everything (including formatting system, data, internal and external SD-cards
2. Flashed a new stock ROM (different from the one I had before)
3. Rooted the phone
4. Installed BetterBatteryStats (to be able to spot the problem) and Kate Mobile for VK (to be able to cause the problem)
5. Uploaded one full size photo from camera via 3G network
6. ... and I got that f***ing no-deep-sleep mode
So the problem exists even on a freshly flashed, brand new ROM
There arу no wakelocks but the CPU never goes into Deep Sleep staying on the lowest frequency of 300Mhz
I'm totally disappointed
Other than that the phone is absolutely perfect... But this problem
Do you think there's still something I can do? Like disabling Fast Dormancy or something?
have you sorted this ?
the problem with mine is similar, terrible battery life and a real problem is getting the phone to wake up so that I can make a call or send a text.
this happens more when I am on the phone and really do struggle with hanging up due to not being able to access any of the soft buttons
will rooting or rom flashing fix?
Scott
Related
Hello,
I have some issues with my phone behaving strangely and forgetting settings after long power-up times without reboot.
I am on rooted Adam kernel 1.6 knox-free with stock 4.2.2 rom XXUDMH5. I only flashed Adam kernel because whatever i tried, I lost Wifi with stock kernel after I tried CF-Auto-Root (got no clue why, but I am not the only one). Phone normally works quite fine, and after greenifying some apps and disabling some bloatware I normally get battery times of four days+ with moderate use (I am not a power-phoner).
However, after some days of power-on time, the phone starts behaving strangely. I got issues with screen auto brightness not working (screen staying on lowest brightness level all the time), touch screen not reacting properly, apps not starting etc. Two times the phone got hot while charging, apparently something running on heavy duty, with the result that after hours of charging battery power increased only little, if at all. Normally those issues went away after re-booting the phone.
Today, after charging over night, I found the phone with screen on, and looking into power history I found that it had been on for six hours. Apart from the hardware damage this might bring (screen burn-in), the other issue is that after the re-boot, I lost almost all settings. I had to enter passwords again for Samsung account etc., and I had to re-configure everything from keyboard settings, vibration feedback, screen turn-off delay, and remote access features.
When I tried to login to Tomtom live services, I had to enter the password again, too, and then the app told me that my account was already associated with another phone (which it was not, of course). Fortunatelly it allowed me to transfer to my "new" phone.
My questions are: Are those settings (screen turn-off delay, keyboard, remote access etc.) kernel or rom related? Does anybody know where those are stored (some xml file perhaps)? Can I make a backup (I have titanium backup) and restore only those settings if need be?
Many thanks in advance!
One addition: When I started Titanium backup, it notified me that the Android ID has changed and if I want to keep the new one or restore the previous one from a backup. Also, the lockscreen personalization (I replaced that "Live Companion" text) was lost.
So, after being on for more than four or five days the phone is forgetting all settings. Am I really the only one?
Hi,
I am new to this forum and do not know much of the technical terms. So here is my problem as best as I could say...
I have a unlocked Samsung S4 purchased last Sept (Philippines/SE Asia version, I think). The phone worked fine until the latest upgrade to Kitkat 3 weeks ago.
A week after the upgrade, the phone started rebooting itself. After checking this forum, it looked like a battery problem. On checking, it did have a swollen battery. At the same time, the S4 stopped working as a phone - meaning I could browse, use apps, but could not make calls.
First changed the battery with an original from Samsung, hoping everything would sort out. Unfortunately, it did not. The phone still kept restarting and the network signal showed as not available. So I went to my provider and got a new SIM card and changed it.
Unfortunately, that has also not solved my problem.
Now, my phone keeps rebooting itself. If I connect it to the charger, then the phone starts successfully. At times, it behaves well, but suddenly/randomly, if I touch an app (any app, no pattern) it will reboot again. Once it starts rebooting, it keeps doing that in the screen which has the samsung music comes - it would turn off again and keep restarting until that screen reaches again. Only if I connect to the charger would it start. Again, there is signal at times and there is no signal most of the times. My area has good network signal, so that should not be the problem.
I tried clearing the cache and clear all data/apps, but still no luck. Also, my battery still has / holds charge - so that is not the problem.
Could somebody please help me!!! Please let me know if you need any other details regarding this.
TIA.
Baseband version: I9505XXUFNBE
1. Sig & log in Sammobile.com
2. Download ur firmware: HERE
3. Unzip it
4. Phone in DOWNLOAD MODE
5. Flash the firmware through ODIN like the pic attached
It has nothing to do with your battery...but yes a swollen battery can be dangerous. Follow the steps told by @Joku1981 and don't upgrade to kitkat. Wait for a stable release from samsung.
Hi,
I have already upgraded to kitkat, so cannot downgrade now.. . I had the request to upgrade to kitkat by the phone (Samsung).
As mentioned by Joku1981, I downloaded the Philippines firmware and did as mentioned. However, the phone was still randomly shutting down on opening some apps (esp Gallery, Playstore, Chrome) and failed to reboot.
I also tried to download the pit file and flash it again as mentioned in http://forum.xda-developers.com/showthread.php?t=2265477. Still no lock.
I tried with UK's version of firmware, still same problem.
The phone can be restarted only if connected to the usb cable.
The "No Signal" issue seems to have been solved, but the rebooting randomly seems to be a real pain now.
After my latest flash, while i was in the third screen setting up the phone for language/accessibility --> "wi-fi setup" --> "Accept Samsung t&c's", the phone shut down again...
Is there any counter to identify the number of times the phone is flashed? Would it cause any problem?
Thanks
Also No Service now!
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
akpreets said:
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
Click to expand...
Click to collapse
Though you flashed, do a factory reset one more time to be on the safe side - make sure the phone is 100% charged, and given your case do NOT touch the phone until the reset has completed.
One more thing to try - from experience some batteries are bigger than others and you said your previous one became swollen. This may cause the power pins to become too compressed causing the new battery to lose contact. This manifests on the phone as rebooting at the slightest of movement/flexing, try this:
1. Remove the battery
2. GENTLY pull out slightly the power pins on the phone - don't pull too hard.
3. Put the battery back, put a piece of cardboard or something at the bottom of the battery to make sure there's good contact
Let us know of the results
Nothing seemed to work but only got worse. The phone could not stay on even for a few hours. Finally gave it to the Samsung Service centre yesterday. They sad it might take upto 3 weeks if there was a motherboard change needed.
Fingers crossed...:crying:
I have the problem that my Galaxy S4 (rooted) becomes laggy or totally unresponsive after fully charging. If I only charge to around 85% and disconnect the charger there's no problem. I can do this several times over days and the phone works fine. But if the charge level reaches something around 90% or more (hard to check the exact number, but it does not have to be 100%) the phone starts to lag. Sometimes the phone locks up completely (pushing the power button a long time reboots it; I did not yet have to remove the battery), but most times it's just very unresponsive. Menu/back button hardly work (light up, but are mostly ignored), the home button most times triggers the task manager and does not go to the home screen.
If I can get as far as to start "OS Monitor", I can see a "/system/bin/mpdecision" process using up to 25% CPU (essentially hogging one core). Killing the process (a new mpdecision process, that uses below 1% CPU, restarts immediately) makes the phone alittle bit more responsive, but not back to normal. If I try to check information about the CPU cores OS Monitor hangs at "gathering information" about the cores (works without problems before the lag).
The only thing that fixes everything is a reboot of the phone.
I've tried a factory reset, even reflashed the firmware with odin, but that didn't change anything. What else can I do? Currently it's very annoying that I have to babysit the phone and reboot it as soon as it's fully charged.
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505ATOGNF1
Have you tried changing to another kernel (eg. Googy) or Rom (eg. GoldenEye) ?
Have you deleted all the Knox files?
Is there an app that causes this?
MPdecision is a kernel governor.
So in 60 hours my battery went from 100% to 30%, which is quite good considering I never turned the phone off, had maybe 1 hour of call time, took a few photos and showed them around and browsed the internet via WIFI for some time. The battery seems ok and the phone didn't have any random reboots nor did I have to reboot the phone. I charged the phone from below 30% to almost 70% and had no problem after disconnecting. Then charged further to around 85% and it happened again. I now also saw that one "kworker/0" process is taking 6-8% of CPU, which normally isn't there. "OS Monitor" also let me see the logs for mpdecision easily and it tells me "Error 38 setting online status to 1 for cpu2" every second. Any idea where that's coming from?
Yes, I have deleted all KNOX files. Does not make a diference though. I doubt it is any of the apps I have installed. I have none installed that do any "optimizing" (which most of those advertised don't) or interfere with battery managment (just things like supersu, busybox, catlog, TB, ES file explorer, OS Monitor). And all the other apps I use don't run anything until I tell them to either.
Can I run another kernel without having to reset the whole phone? Since Kies backup only really does a backup of the useless stuff that's almost as easy to backup by just copying the files by hand, but misses all the important and tedious to set settings, I'd rather not do a full wipe again if possible. Or is there a way to make a backup of the current state of the phone that I can flash back, so ALL settings/apps/configurations are preserved? (In essence I want to go back to me current state, if any of my experiments go wrong)
Lupin III. said:
Can I run another kernel without having to reset the whole phone? Since Kies backup only really does a backup of the useless stuff that's almost as easy to backup by just copying the files by hand, but misses all the important and tedious to set settings, I'd rather not do a full wipe again if possible. Or is there a way to make a backup of the current state of the phone that I can flash back, so ALL settings/apps/configurations are preserved? (In essence I want to go back to me current state, if any of my experiments go wrong)
Click to expand...
Click to collapse
Yes. There's a kernel cleaning script that you can flash before to delete all settings of the kernel.
It sounds to me you're not on a custom recovery yet. Search for TWRP or Philz recovery and flash them with Odin. (Kill Kies process on your computer first. Switch off phone before going into download mode. )
With those recoveries you can take a backup of your complete rom.
Then you can flash a custom rom, but you'll have to do a full wipe.
You can also use Titanium backup to backup your programs and settings.
I sync my contacts, call log and SMS with Samsung. Apps are automatically reinstalled by Play store after logging in, but without their settings. With Titanium I restore their settings. But it's been a while since I've done that.
My Note4 was updated to Lollipop about 2 weeks ago and it was running ok until 3 days ago where it keeps on restarting, freezing up, not responsive etc.
The last application that I installed was "FACEBOOK GROUP" but I'm sure this isn't the problem because of the factory reset as explained below.
I have done a factory reset, but I reinstalled all the applications (except Facebook Group), but the problem still persists. It even restarting without it's being touched. Per day, it could restart up to 15 times.
Most of the problem appears when the phone goes into an idle state and won't turn on unless I do a battery pull (like Blackberry).
But sometimes it would respond from the idle state after a 20-30 seconds.
I did find an article that the motion and gestures are causing the unresponsive issue, in which I have followed and disabled all the motion and gestures, this doesn't help. Problem persists.
I have talked to the Samsung Tech support and they told me that I would have to bring it to the service center in Singapore (I live in Jakarta) and they would need to diagnose it. I did mentioned that I want a new phone but they said that they don't have exchange policy. This is really bad because Iphone has an exchange policy, why doesn't Samsung have one too??
Anyone in Singapore maybe have the same issue? or have a knowledge about the exchange policy?
Have you tried uninstalling Facebook Group from your Note 4? It seems to me that the Facebook Group App must be causing some sort of problem with your Note 4.
DarkGuyver said:
Have you tried uninstalling Facebook Group from your Note 4? It seems to me that the Facebook Group App must be causing some sort of problem with your Note 4.
Click to expand...
Click to collapse
After I did a factory reset. I didn't install Facebook Group
UPDATE 1 :
I uninstalled DU Speed Booster, and the problem seems to be better, but still hangs after unplugging from charger.
Does anyone use DU Speed Booster with Lollipop?
bankir said:
UPDATE 1 :
I uninstalled DU Speed Booster, and the problem seems to be better, but still hangs after unplugging from charger.
Does anyone use DU Speed Booster with Lollipop?
Click to expand...
Click to collapse
OK, seems like DU Speed Booster may have messed with the system settings of your phone somehow. Are you using the stock firmware that came with your Note 4?
DarkGuyver said:
OK, seems like DU Speed Booster may have messed with the system settings of your phone somehow. Are you using the stock firmware that came with your Note 4?
Click to expand...
Click to collapse
Yes sir, it is the stock rom.. and it's not rooted. Still original except that it has been updated to Lollipop.
Uninstalling DU Speed Booster seems to make it a little better, but occasionally it still freezes and restart but it's not as many times as before.
If the system setting has been messed up, then I will do another hard reset tonight and see if that would fix the issue. I'm tired of waiting for the phone to come alive after idle or when it restarts by itself.
UPDATE 2 :
I did a factory reset last night and left it to sleep while it was updating stock applications (I have not installed any of my application).
This morning when I woke up. I couldn't turn on the phone. It was frozen and it has a solid red LED light on the top left. This happens quite frequently before too. So I'm not sure what the issue is. Btw, my note 4 is the first batch. Bought it when it first came out.
I had to take the battery out and started the update again.
Then it got restarted when I tried to swipe my finger to enter the homepage.
Why doesn't Samsung give an exchange policy? their rival Apple does..
Yeah, I think you need to return your device to Samsung for repairs. As for why Samsung doesn't have a exchange policy, because retailer's tend to have a exchange policy where if they can't fix your device they will replace it with another one. Since retailer's give you a 1 year standard retailer's warranty with the purchase of any electronic device. Apple has a exchange policy, because as well as being a device manufacturer they are also a retailer for their own devices.
My Note 4 has been a lot better since I reseated the SD Card. I did that before too.
I'm starting to think that my SD Card was not reseated properly causing the system to hang / freeze.
As of now, I think the culprit is the SD Card.. I will monitor and update again.
I think I posted too quicky.
The problem still persists, so it is not the 'reseating' of the SD Card.
I notice though, the problem with hanging, restarting, MOSTLY occurs when the battery is less than 40%. And sometimes, it won't even start / turn on even after I take out the battery. But when it is succeeded, sometimes, it would come out with the message (shown in the attachment). Every time this comes out, I have to take out the battery and wait 30+ seconds before trying again.
I really don't know what is the problem with the phone and this phone is bought overseas. Local Samsung Store can't fix it because they don't have the base band or software.
Please note that this phone has never been dropped / root. I have taken care of it carefully.
I'm really disappointed.
It does seem like a hardware error either with the internal memory chip or the battery. You could try replacing the battery to see if that would fix the problem, I doubt that would work. But I would prefer to just send it back to Samsung for repairs as they have the equipment to fix the problem.
Alternatively you could install Kies 3 from the Samsung website onto your computer and use that to do a firmware reinstall of your Note 4 and see if that helps. If that doesn't work then you really don't have much of a choice other than sending back to Samsung for repairs.
Similar Problem
My Note 4 has locked up three times after a full charge.. I noticed a solid RED LED after the phone fully charged and attempts to turn it on are unsuccessful, it's frozen. Nothing I do can wake it up short of removing and replacing the battery. The Lollypop update was done over a month ago so I doubt that is the cause. I'm still checking things out but it has occurred to me that if this happens to the S6, what would one do if you can't remove the battery?????
Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.