Related
Well, this is frustrating...
Sitting in church with my family on Easter Sunday, I felt a short vibrate from my phone. Figured it was just an email coming in, so I didn't pay it much attention. But by the fourth time, I started wondering why I was getting such a flood of email, especially on a Sunday morning.... That's not a typical pattern for that email account.
So I discreetly slid my phone out of my pocket to take a peek, and it was on the boot screen. Since then, my phone has been periodically rebooting itself for no reason that I can think of.
Unfortunately, it never does it with the USB cable connected, so I haven't been able to capture a logcat of what's going on when it reboots. It also doesn't seem to every do it while I'm using the phone, only while it's sleeping.
Searches haven't been much help. A few promising leads, but they all seem to end up getting blamed on apps that I've never had installed.
It also seems to be getting slowly less frequent. Only happened twice yesterday, and my phone made it through the night with no reboot.
I've uninstalled most of the apps I had on the phone. The only ones left are things I've been running since my first day with the phone, so I have a high degree of confidence that they're not the problem.
For completeness, I'm running DC v2.05, PRI 1.70_003, PRL 60663. I have no reason to think it's the specific rom causing a problem, but it's always good to include information that could be relevant... I'm also running radio version 2.42.00.03.10. (Doubt that's the culprit since I flashed it after this problem began.)
Are there any likely causes that my searches aren't turning up that would be worth looking at? More to the point, is there a way to view the logcat from before the phone rebooted? From what I can tell, it only shows me the log from the point where the phone booted up.
And as a last resort, aside from an RUU are there any steps I should take before having the Sprint store replace the phone?
I had my phone reboot on its own the other day as well, also unplugged. It's only happened once so far that i've noticed. I'm running the new fresh 2.0d.
subliminalurge said:
And as a last resort, aside from an RUU are there any steps I should take before having the Sprint store replace the phone?
Click to expand...
Click to collapse
I would take your battery into consideration here, it might possibly be shorting out? That's one thing to look at.
Also, if you wouldn't mind, do post your logcat -- it'll help us diagnose a possible problem you haven't caught.
Also, try this comand: adb bugreport > errorlog.txt and also look at these sets of commands:
Filtering Log Output
Every Android log message has a tag and a priority associated with it.
* The tag of a log message is a short string indicating the system component from which the message originates (for example, "View" for the view system).
* The priority is one of the following character values, ordered from lowest to highest priority:
o V — Verbose (lowest priority)
o D — Debug
o I — Info
o W — Warning
o E — Error
o F — Fatal
o S — Silent (highest priority, on which nothing is ever printed)
So try to run a command like this: adb logcat *:W -- This will show any messages that have a level of "warning" or higher.
More info HERE
Same thing happened to me yesterday. Had the phone sitting on the counter for a few hours. Didn't get a call that I was expecting. Hit the power button and the phone booted. The battery was not low and I don't know why it was off. I'm on Fresh 2.0d
Ive got two heros on fresh 2.0d. Happened on one while I was exiting camera. Thats the one and only time though.
pseudoremora said:
I would take your battery into consideration here, it might possibly be shorting out? That's one thing to look at.
Also, if you wouldn't mind, do post your logcat -- it'll help us diagnose a possible problem you haven't caught.
Also, try this comand: adb bugreport > errorlog.txt and also look at these sets of commands:
Filtering Log Output
Every Android log message has a tag and a priority associated with it.
* The tag of a log message is a short string indicating the system component from which the message originates (for example, "View" for the view system).
* The priority is one of the following character values, ordered from lowest to highest priority:
o V — Verbose (lowest priority)
o D — Debug
o I — Info
o W — Warning
o E — Error
o F — Fatal
o S — Silent (highest priority, on which nothing is ever printed)
So try to run a command like this: adb logcat *:W -- This will show any messages that have a level of "warning" or higher.
More info HERE
Click to expand...
Click to collapse
+1 on the battery suggestion. Ordered a battery from Ebay and that's what happened to me. Stopped using the battery, problem ended
USB is a sign...
pipskicks said:
+1 on the battery suggestion. Ordered a battery from Ebay and that's what happened to me. Stopped using the battery, problem ended
USB is a sign...
Click to expand...
Click to collapse
Good thought. I'm still using the stock battery, so it wouldn't be anything to do with an aftermarket, but...
A few weeks ago I flashed a beta rom to test it out, and when I woke up in the morning my phone was too hot to comfortably hold in my hand.
Wondering if the battery got radically overcharged and is finally starting to flake out... Might have to swap my battery with my wife's tonight and see if the problem follows the battery or stays with the phone.
(Be cool if that's the problem, been wanting a higher capacity battery and this would be just the nudge I've needed to pull the trigger on one....)
Maybe its because you brought it into church. its needs to be exercised.
j/k
It has happened to me as well
tyrnight said:
Maybe its because you brought it into church. its needs to be exercised.
Click to expand...
Click to collapse
Well, I did comment to my wife on the way out that "Wow, I didn't even melt when he splashed the holy water on us...."
The battery idea sounds good. Plus, the battery on EBay for $10 is a good deal...that's what I'm currently using and I haven't had any problems so far. YMMV.
My wife just told me she has the same problem. It's a battery from ebay, oem. She went back to her regular stock battery - no problems. She's on fresh 1.5 rom v1.1.
Well, I swapped the batteries between my and my wife's phones last night, and so far neither one has rebooted itself. So the results are still inconclusive.
But, as I said, the problem was fairly intermittent, so I guess I'll just have to keep an eye on them for the next day or two....
I get random reboots every so often myself and I only use the stock battery. Currently running Damage Control v2.05 based off the Sprint leak. Does logcat need to be done immediately once the reboot happens? Because it's been about two days since it last happened.
I haven't had a chance to fully read up on how logcat work. It's at the top of my todo list, but the past few days have been crazy busy....
As far as I've been able to tell from a little poking around, the log gets cleared when the phone is rebooted. I'm strongly hoping I'm wrong about that, but as I said, it might be a day or two before I get a chance to educate myself more in depth on how logging is done on Android.... (the normal linux log directory doesn't seem to be present, either in the normal location, or a few obvious alternatives I've looked at....)
I noticed my phone reboot after I picked it up the other day as well. I'm running Fresh Rom 2.0d with a ebay battery. This was before I installed the new radio though so I don't know if that makes any difference.
Any one else notice that after a random reboot, the phone constantly stays awake 100% of the time and eats away at battery life?
Austin3600 said:
Any one else notice that after a random reboot, the phone constantly stays awake 100% of the time and eats away at battery life?
Click to expand...
Click to collapse
Actually, I hadn't noticed that, but I'll be sure to keep an eye on it from here on out....
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Try calling HTC?
vzontini said:
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Click to expand...
Click to collapse
I agree, the only time my phone gets hot is when I leave it in my landscaping truck while I'm mowing, but I think any phone would have problems when it's 112 degrees outside and probably 140 in the truck.
Sounds like a bad phone. The only time my N1 rebooted was when I had an experimental rom on it.
Sounds like something is just borked, I use my phone all day it only reboots because I want to go into recovery.
Are yur using custom recovery? Wipe the cache and dalvik-cache.
Same as the above poster, mine never rebooted spontaneously even when hitting over 40C degrees. Only does so when I'm running some cutting-edge alpha kernels/ROMs, and then very rarely.
I was thinking it was specific to my device as well. I then googled "Nexus One overheating" and was overwhelmed by the number of people with the same issue. I also own over a dozen HTC devices, I've had ZERO problems with any of them. I've wiped my cache quite a few times. I've even wiped the phone and started fresh.
I've googled every specific issue I have had and found many others complaining about the same thing. Overheating/locking up the device when charging overnight - check. Rebooting/overheating when using GPS - check.
Lately, I've been uninstalling anything that runs in the background that isn't an essential part of the OS. Makes no difference. When I first got my N1, I used the GPS and Car Home app to drive an 8 hour trip. Not a single problem. The very first time I tried to use Car Home after going to Froyo it rebooted after just a few minutes and it's been that way since. I found MANY posts that confirmed this on Google's forums.
Personally, I think my device is fine. I suppose it's always possible that an app is causing the reboots. For example, the Weather Channel app is always running and that's not the most beautifully coded app I've ever seen...
Any suggestions, keep 'em coming. I'm not thrilled with Windows Mobile 7 yet.
Here's my installed apps (I love that program BTW). If you see anything as a possible suspect, let me know:
Adobe Flash Player 10.1 (v10.1.92.8)
andLess (v1.2.3)
Android Agenda Widget (v1.3.5)
AT&T myWireless Mobile (v6.0)
Audalyzer (v1.14)
Barcode Scanner (v3.4)
BlueRSS (v3.0.4)
Chrome to Phone (v2.0.0)
eBay (v1.1.2.3)
eBuddy (v1.8.1)
Ethereal Dialpad (v2.5.2)
FCC Test (v1.0.7)
Flashlight (v2)
FREEdi Video Download Helper (v1.3.1)
FrostWire (v0.3.7)
Google Translate (v1.1.1)
GPS Status (v3.2)
gStrings (v1.0.5)
HistoryEraser (v2.1.1)
HTC_IME mod (vv.27)
JScreenFix (v2.0)
Keyboard Calibration (v2.10)
Linda Manager (v1.5.12)
Listen (v1.1.3)
Log Collector (v1.1.0)
Music Junk (v3.0.4)
My Battery Status (v2.0.8)
MyAppsList (v1.4 BETA)
Network Info II (v0.3.4)
Note Pad (v1)
OSMonitor (v1.1.6)
Pandora (v1.3)
Penguin (v1.2.0)
RealCalc (v1.4.1)
Scanner Radio (v1.9.2)
Secrets (v1.9.2)
Shazam (v2.0.2-B70005)
Shopper (v1.12)
Solo Lite (v1.25)
Terminal Emulator (v1.0.12)
Tetronimo (v1.5.1)
The Weather Channel (v2.3.17)
Titanium Backup (v3.4.2)
Trapster (v1.6.3)
Tricorder (v5.11)
TTS Service Extended (v2.0)
Universal Androot (v1.5.3)
Voice Recorder (v2.0.7)
Wifi Analyzer (v2.4.8)
WiimoteController (v0.3b)
XDA (v1.2.1)
Device Summary
Device: HTC Nexus One
Android Version: 2.2
Build: FRF91
List Generated By: MyAppsList (market://search?q=com.boots.MyAppsList)
By the sound of it, it's not an app. The phone should be able to take a good amount of heat and not reboot - the only time I got it to reboot was under direct sunlight in a car, it was probably hitting 50 degrees Celsius. If yours reboots every time you do anything - it's time to nandroid, take out the battery and clean the battery contacts really well (on the battery and the phone, using alcohol), flash a bone stock FRF91 or something really close to it, try to repeat the things that made it reboot (shouldn't be very difficult), and if the reboots continue - then I'm sorry, but you have a lemon. And if they don't - change to your favorite ROM and start incrementally installing stuff in small packs, until your testing shows reboots again. Defining anything other than Google account (like Exchange account) is also considered "installing something".
E-Mail quirks are taken care of by E-Mail clients. Exchange server push might be draining the hell out of your battery and heating your phone, check the relevant thread. I really hope you find the problem in SW, but it doesn't look very much like it.
P.S. There are so many ways to get a WinMo phone stuck (my wife has one, I regularly practice using the reset button when doing something with the system) it's not even funny.
thanks for the tips. I'll give them a shot. I read in a couple different threads that HTC has been sending replacement batteries to those with overheating issues. I have a hard time believing it's the battery but what do I know?
One thing I forgot to add about WinMo, I soft reset my device every morning on the way to work. Just a habit I got into with Windows.
-Mc
Yeah sounds like you got a faulty device. If the above suggestions don't work, call HTC and they should do a swap for you
went to the Google "Device Troubleshooter" support page: http://google.com/support/android/bin/answer.py?hl=en&answer=185837
Step 1: What are you having an issue with?
selected: A hardware problem I'm having with the Nexus One
Step 2: A hardware problem i’m having with the Nexus One
selected: My device overheats
Then it said this:
It is normal for your phone to get warm after an extended period of continual usage, such as a long phone conversation. If your phone becomes so warm that you cannot hold it comfortably, please try removing the battery and waiting until the phone cools off before replacing it.
If your phone overheats to the point of shutting itself off repeatedly, there may be a hardware defect with your phone's battery. Please visit our warranty information page.
Click to expand...
Click to collapse
So I called support (open 7 days a week - nice) and they are shipping out a new battery tomorrow and if that doesn't work, I'll send it in for repair. Didn't want to replace it because it was engraved.
I really hope this fixes it. I do like Android and I love the community work. iOS blows and Windows Mobile 7 just doesn't have me wanting one.
I'll update this thread when the new battery arrives and if necessary, after the repair work...
I used to have the same problem, but i don't think it was rom specific for me. I had a black case on my phone and my car mount was a black universal one mounted on my windshield. I would use GPS nav and play music at the same time and sometimes make phone calls and it would reboot pretty frequently. Through SetCPU i noticed that the temp was somewhere between 45-50degrees C. only way i was able to use my phone was to remove the battery and stick it in my AC vent along with the phone itself.
So since then i got myself a AC mounted carmount and no longer use my case and its been fine ever since. When ever it gets hot in my car i usually have AC on and the phoen gets cooled by it also. Average temp was around 15-18degrees C while i was using GPS/Music/Calls.
lulz, sounds like your phone had a hardware issue if it was rebooting all the time like that.
I have had my phone on for literally weeks at a time with out a reboot. Android is rock solid stable.
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
McHale said:
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
Click to expand...
Click to collapse
Your phone is defective. I've NEVER experienced a spontaneous reboot.
uansari1 said:
Your phone is defective. I've NEVER experienced a spontaneous reboot.
Click to expand...
Click to collapse
Same here** (only when I played with different kernels )
GldRush98 said:
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
Click to expand...
Click to collapse
you're not much of a reader, are you?
JCopernicus said:
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
Click to expand...
Click to collapse
Fact: Windows Mobile still does several things much better than Android. And those things are important to me on my primary device.
I get what you're saying though. Despite a few issues, Android is dominating everything in it's wake. But instead of Android spending so much time with new flashy features, they should focus their attention getting the basics right first. Their contact and email handling B L O W S. How about proper email folder handling and a basic undelete function...
I agree with the rest. To be honest, I didn't get my Nexus new, it has had two users before me. It came with Cyanogen Mod, and to be honest I find it gives better battery life and performance compared to the stock OS. If I were you I'd try it out once you get the Nexus back.
I use ROM manager to download and install ROMs, give it a try.
Is it safe to remove the dmservice apk if I don't plan to do OTAs? Does this app do anything else besides check for updates (if that's truly the purpose of this app)?
Sincitybronze said:
Is it safe to remove the dmservice apk if I don't plan to do OTAs? Does this app do anything else besides check for updates (if that's truly the purpose of this app)?
Click to expand...
Click to collapse
Do you really want to risk it? Why do people have a compulsion to start erasing stuff off their phones? Are you running out of space? Does the presence of unused programs just bug you?
Maybe he is trying to save some RAM or something?? Who knows...but I would check if it interferes with any important system apps/processes first. If he has no need for the OTA updates then I don't see the issue. Maybe a more informed person can help this person out.
deez1234 said:
Maybe he is trying to save some RAM or something?? Who knows...but I would check if it interferes with any important system apps/processes first. If he has no need for the OTA updates then I don't see the issue. Maybe a more informed person can help this person out.
Click to expand...
Click to collapse
Has anyone ever run out of RAM using a Vibrant? I've never dropped below 60mb free. From talking to G1 owners, this is pretty amazing.
I am curious for an answer too, I am rooted and running the JI6 that I flashed from here. Today my phone now displays "Connecting to DM server.......". It has been like this for several hours now. I can't seem to make the process not come back. t continues to autostart. Any ideas anyone????
Kubernetes said:
Has anyone ever run out of RAM using a Vibrant? I've never dropped below 60mb free. From talking to G1 owners, this is pretty amazing.
Click to expand...
Click to collapse
I agree that it is very hard to run out of RAM, I was just stating that because maybe the OP just wants to free up whatever he can. It's not gonna hurt anyone if the OP does it...or maybe it will, judging from some of the responses. All i wanted to do was help this person get their question answered. Harmless if you ask me! This is in no way a personal attack by the way, lol. It's quite hard for me to sense sarcasm through text...unless IT'S IN ALL CAPS.
I don't see any reason for it to hurt anything. I am running a backup now so that I can remove it and see what happens. I will update once it has been removed with a status.
Yeah, I just generally go by two rules of thumb: (1) If it ain't broke, don't fix it, and (2) If you don't know what it does, don't mess with it. There are plenty of services that run but are not obvious as to their purpose. I just wouldn't mess with it unless you feel like it's detrimental to your phone.
Typically I wouldn't, but this seems to be causing some battery drain. I will experiment, if anything goes wrong I can always restore my backup.
That's completely understandable. I agree once again. I think the OP may just be looking at the running process and thinks removing it and any future update will be beneficial. I am not quite sure of the motive but some people look at things differently. Maybe the OP will chime in with some of the reasons other than just disabling updates. That is yet to be seen, so until he posts unfortunately we won't know.
Ok, so here is the process I went through.
Went to Settings>Applications>Running Services>
Saw this:
DMService
com.wssyncmldm
***** RUN A BACKUP BEFORE RUNNING THESE COMMANDS! I am not responsible for anything that happens to your phone blah blah blah.....*******
Connected to the phone via adb
Ran the following commands:
su
# busybox mount -o remount -rw /dev/block/stl9
# rm wssyncmldm.apk
# rm wssyncmldm.odex
# rm wssyncmlnps.apk
# rm wssyncmlnps.odex
DM immediately stopped.
Rebooted the phone with no issues.
Will continue to monitor for issues.
So far so good.
Let us know how it affects your battery life or if it does anything nice for you at all. Thanks for being the guinea pig! Seems as if you did it more properly than I would have, lol.
No worries, I wouldn't think it would hurt anything to remove it. But, I have been known to be wrong before. Anyway, it should make quite a difference on the battery, my phone had been trying to connect to the DM Server for several hours and I was seeing a consistent drain. About 10% per hour. Now it seems to have settled a bit. With normal usage I haven't seen any FC's. WI-FI, BT and GPS are all working. It doesn't seem to have affected anything yet. Yeehaw...
Yes, battery life is the reason I'm interested in this. I removed the media hub and drm and experienced improved battery life. I thought eliminating dmservice might have a similar effect.
So far it seems to have made a difference. But the only time it was causing drain was wen it was trying to connect to the DM Server. I haven't yet seen it start back up, it appears as though it is completely gone.
Nice, hopefully this helps some people who are interested and are having issues with the service.
Sent from my SGH-T959 using XDA App
aksoutherland said:
So far it seems to have made a difference. But the only time it was causing drain was wen it was trying to connect to the DM Server. I haven't yet seen it start back up, it appears as though it is completely gone.
Click to expand...
Click to collapse
Thank you so much for testing this. I uninstalled with titanium.
Titanium pro & freeze it
Vibrant + xda app
aksoutherland said:
I am curious for an answer too, I am rooted and running the JI6 that I flashed from here. Today my phone now displays "Connecting to DM server.......". It has been like this for several hours now. I can't seem to make the process not come back. t continues to autostart. Any ideas anyone????
Click to expand...
Click to collapse
Aks: is there an app you use to see which processes are actively trying to connect to a server? How can I get information like this? Thank you.
Using Titanium backup, I froze the DMservice and a few other DRM services and the media hub. I'm running bionic fusion if that matters. I have not noticed any adverse reactions and battery life does seem a bit better. I have not seen the error trying to connect to the dm service since doing this. If you just use the task manager, the service will start back up again after some period of time. Other threads about battery life have stated that these services are known to drain the battery. Freezing seems a good inbetween step to see how things go.
Edit Update.
So my extremely subjective interpretation of battery life is that its better and by simply freezing the services, they don't return. Maybe they do upon reboot; not sure. Before freezing the services, my phone would lose approximately 4% of battery within 1.5 hours of unplugging from power. Not the case this time. I have been unplugged for almost 2 hours and have lost negligible amount. I also turned off a bunch of update/notification services from seesmic, facebook, gtasks, etc.
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
I've got a problem with my S8 which is running latest, official, non-rooted XEO firmware. Specifically, it uses battery like crazy and heats up whilst doing nothing. This smells like a virus / malware infection or just... well, the last update was in December 2021 so it's also possible some system component is wonky OR... <shivers> some rootkit? I'm generally rather careful when installing apps, most of which will be coming in from official sources (Google Store) or at least fairly trusted sources.
Every so often I'll get a warning that a system component is using too much CPU and I should restart the phone - which obviously doesn't help at all. Also the battery drain is reported primarily by Android System and System Core (29 and 15% respectively). Battery usage stats generally don't add up because the listings don't add up to 100%. :/
I know the S8 is an old phone... and I know there are probably steps I should take prior to asking here - like a factory reset. But I'm really sceptical of doing a factory reset simply because I've got so much stuff on the phone that, while not impossible to backup, is certainly annoying (authenticator or banking apps for example - and I don't think the standard backup tools like those available from Google or Samsung backup such apps).
So I'd rather try some solutions or methods of dealing with the damned thing without resetting the phone first. Is there anything I can do?
You need to find the root cause. It may be a 3rd party using one or more of the Samsung system apps running under Android services, lol Legend for there are many... all lumped together.
A firewall with logging can help. Karma Firewall is what I use, uses almost no battery. Being rooted you have more options... use them.
Malware is always a possibility.
3rd party apps can cause hell. I don't allow any social media apps on the phone, ever.
Try in safe mode... if things calm down it's likely a 3rd party app. If so start going through the installed apps.
Clear system cache.
blackhawk said:
You need to find the root cause. It may be a 3rd party using one or more of the Samsung system apps running under Android services, lol Legend for there are many... all lumped together.
A firewall with logging can help. Karma Firewall is what I use, uses almost no battery.
Click to expand...
Click to collapse
Will try that, thanks!
blackhawk said:
Being rooted you have more options... use them.
Click to expand...
Click to collapse
The phone is NON-rooted.
blackhawk said:
Malware is always a possibility.
3rd party apps can cause hell. I don't allow any social media apps on the phone, ever.
Try in safe mode... if things calm down it's likely a 3rd party app. If so start going through the installed apps.
Clear system cache.
Click to expand...
Click to collapse
Oh, safe mode! I'll try that too! Thanks!
Shaamaan said:
Will try that, thanks!
The phone is NON-rooted.
Oh, safe mode! I'll try that too! Thanks!
Click to expand...
Click to collapse
Sorry about the root thing, my bad.
If you're running on Android 9 or lower Karma Firewall's logging feature is fully active otherwise not. Samsung store>Galaxy Labs> Battery Tracker can be useful.
I use Accubattery's history page to get a quick idea of charge/discharge rates.
I use Device Care>storage>clean as well.
Make sure no cloud apps are running in the background.
Update: in safe mode the phone doesn't heat up and battery usage seems normal. So it's probably some app.
Alas, the firewall wasn't very helpful - it seemed that apps that attempted accessing the internet were your usual suspects - Play Store, One Drive or other sync apps, Vanced.
Any other suggestions on possibly nailing down the culprit?
PS. I've also decided to send Samsung an error report via the Members app - I don't know what their reply times are and I honestly don't expect much from them but who knows? Perhaps they'll come through.
Shaamaan said:
Update: in safe mode the phone doesn't heat up and battery usage seems normal. So it's probably some app.
Alas, the firewall wasn't very helpful - it seemed that apps that attempted accessing the internet were your usual suspects - Play Store, One Drive or other sync apps, Vanced.
Any other suggestions on possibly nailing down the culprit?
PS. I've also decided to send Samsung an error report via the Members app - I don't know what their reply times are and I honestly don't expect much from them but who knows? Perhaps they'll come through.
Click to expand...
Click to collapse
Why other than maybe text messages is anything syncing? Take out the trash and go from there.
The ones that are connecting every minute or more when not open are prime suspects.
Some apps like Brave browser need to be closed out when not in use or they eat battery.
You can also try a hard reboot.
Update!
I left the phone in safe mode overnight. I mean, it seemed like things were better, so at least I'd have a stable phone.
Well, in the morning I was greeted with a severely depleted battery (went from 100 to 40 in the span of 6 hours) and I got the "high CPU usage" warning popup. The phone wasn't as hot to the touch tho.
So... Whatever is going on seems to happen also in safe mode, albeit less often? Or perhaps it's less "severe" where it doesn't heat up the phone but the drain is still there? But since safe mode is affected it's probably NOT an app, right?
At this point I'm completely baffled. Any other ideas?
Shaamaan said:
Update!
I left the phone in safe mode overnight. I mean, it seemed like things were better, so at least I'd have a stable phone.
Well, in the morning I was greeted with a severely depleted battery (went from 100 to 40 in the span of 6 hours) and I got the "high CPU usage" warning popup. The phone wasn't as hot to the touch tho.
So... Whatever is going on seems to happen also in safe mode, albeit less often? Or perhaps it's less "severe" where it doesn't heat up the phone but the drain is still there? But since safe mode is affected it's probably NOT an app, right?
At this point I'm completely baffled. Any other ideas?
Click to expand...
Click to collapse
Hard reset... hold power button until it powers off.
Try temporarily disabling Google play Services at night, see what that does.
OK, I'm baffled. I feel like I didn't really do anything but the phone is now running fine. Battery drain now might be better than ever!
Warms up on usage, obviously, but when idle it's nice and cool and battery drain seems minimal. I'll... leave it for a few days to see how this develops. It's very difficult to tell what the heck's the case here.
Shaamaan said:
OK, I'm baffled. I feel like I didn't really do anything but the phone is now running fine. Battery drain now might be better than ever!
Warms up on usage, obviously, but when idle it's nice and cool and battery drain seems minimal. I'll... leave it for a few days to see how this develops. It's very difficult to tell what the heck's the case here.
Click to expand...
Click to collapse
Retrace what you did. Reason being you may need to do it again. Really most times all you need to do is just "play" with it a bit (a lot). Almost impossible to crash a stock load, so explore and learn by playing with it. You are what you load and download; be careful with 3rd party apps they are the biggest potential hazards.
Once you have a fast, stable OS that's fulfilling its mission, let it be. Don't update or upgrade it.
Updates can and do break Sammy's. This N10+ is still running on Pie, current load is over 2yo. Rock solid stable and it runs like a bat out of hell with minimal maintenance. Security isn't an issue.
blackhawk said:
Retrace what you did. Reason being you may need to do it again. Really most times all you need to do is just "play" with it a bit (a lot). Almost impossible to crash a stock load, so explore and learn by playing with it. You are what you load and download; be careful with 3rd party apps they are the biggest potential hazards.
Click to expand...
Click to collapse
I have a suspicion this might have been some Samsung app (my bet's on Bixby) since those are likely still able to run in Safe Mode that got updated and then fixed...? Does that make sense?
blackhawk said:
Once you have a fast, stable OS that's fulfilling its mission, let it be. Don't update or upgrade it.
Updates can and do break Sammy's. This N10+ is still running on Pie, current load is over 2yo. Rock solid stable and it runs like a bat out of hell with minimal maintenance. Security isn't an issue.
Click to expand...
Click to collapse
I'm concerned about the last bit. I mean, upgrading to a new Android version is one thing but security updates are common, no?
Shaamaan said:
I have a suspicion this might have been some Samsung app (my bet's on Bixby) since those are likely still able to run in Safe Mode that got updated and then fixed...? Does that make sense?
I'm concerned about the last bit. I mean, upgrading to a new Android version is one thing but security updates are common, no?
Click to expand...
Click to collapse
Kill wittle bixby... you read it EULA?☠
It's more than one apk though. Takes a while to optimize a Sammy the first time
Well... if it's set up and used right Android 9 will run securely in the real world. No saving dumb bunnies anyway; they'll still get tagged even with the latest version
The proof is in my hand. Loaded over 2+ years ago and this N10+ UI version 1.5 is running clean like a bat out of hell. If I do get malware I can't erraticate in an hour or so, factory reset and change passwords.
My data is redundantly backed* up 4+ times, plus the onboard SD card used as a data drive. I'm ready to reload right now if I have to...
A malware forced reload is still less trouble than constantly updating and having the updates screw things up. That means more troubleshooting, finding new work arounds and still maybe needing a factory reset on top of all that. No.
Not vaxed either... not buying the hype.
*critical data must be redundantly backed up or sooner or latter it will likely be lost. Never encrypt data drives as you are the most likely to be locked out!
blackhawk said:
Kill wittle bixby... you read it EULA?☠
Click to expand...
Click to collapse
Oh I'd love that - but it's a system app and removing those without root is kind of... impossible? I can look into disabling it completely however - I never use it anyway. Since it's not a single app - any chance you got a link to the list of apps that need manual disabling?
Anyway, I'm still getting those damned warnings. The phone isn't constantly hot however, which is some improvement.
Shaamaan said:
Oh I'd love that - but it's a system app and removing those without root is kind of... impossible? I can look into disabling it completely however - I never use it anyway. Since it's not a single app - any chance you got a link to the list of apps that need manual disabling?
Anyway, I'm still getting those damned warnings. The phone isn't constantly hot however, which is some improvement.
Click to expand...
Click to collapse
Package Disabler kills bixby proper.
You can also disable it with an adb edit. That's one of the first things I do.
Bixby is a hot mess best dump along the interstate... like Google Assistant it needs external servers for many of its functions. I may change my mind but it's eula is like eating dry hardtack for breakfast.