Related
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.
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.
Hey guys Im a EVo user and my girl has an Epic.
Now the next statement is with either running stock or a custom rom
Her phones slows way down and reboot its required, wifi is odd sometimes a reboot to connect, and today her battery became rather hot over 100 F.
Is there anything I can try out on her phone?
Sounds like a specific phone harware issue, i dont get overheats or slow downs, no matter how many apps are running at the same time and even if i charge and use mobile ap all the time, still no overheats here.
Ive Done this on both stock and custom roms and no overheats or slow down..
darn, thankyou for a reply, guess I'll update her ROM and start her off fresh
I don't get slow downs either. I leave my wifi on all day and don't have issues connecting. I only overheated once. Shortly after I got my phone I was downloading stuff left and right, playing graphics heavy games like radio ball, and trying to charge my nearly dead battery all at the same time. When I got the overheat message I figured it was a sign that I needed to turn the phone off and walk away for a little while.
Either the phone has a problem, or your girl does. (which were pretty much your choices to begin with)
Yep no issue at all here usually always on wifi and I'm a heavy user. I get no slow down or anything and I'm on stock rom with bloatware removed.
Sent from my SPH-D700 using XDA App
My phone does slow down after about 2-3 days of uptime. I'm 100% stock, not rooted. Reboot resolves the issues.
After @ 2-3 day uptime the following happens:
1. I've had issues when rotating between home screens where all my widgets & icons disappear, then come back to normal.
2. Also, sometimes my swiping isn't recognized when trying to cycle home screens.
It's difficult to reproduce on demand, thus making my case to Sprint for replacement even more difficult. So I said screw it, just hoping 2.2.1 will resolve the problems whenever its rolled out OTA.
Sent from my SPH-D700 using XDA App
You may be right. I would get a different girlfriend and see if the overheating/rebooting problem continues. If it stops, we know where the problem was. If the problems continue with the new girlfriend, it may be you.
Sometimes my phone will get very unresponsive such that any action takes many seconds to show up, and everything is very choppy. Often I see this when I wake up in the morning, but it happens often enough in general. It's so bad that I can't shut it down normally because it would take over 10 min (I've actually never waited to see exactly how long it would take). Thankfully I just found out about the three finger reset (volume up, camera, power), so I shouldn't have to pull the battery anymore, but it's still a problem.
I don't remember this happening before using custom roms. It happens with both DK28 roms I've tried - Bonsai and Viper. I believe it also occurred on the 2.1 Epic Experience, although I'm not sure. I guess I should try flashing to DK28 stock to see if that works, but it's a pain to set up everything each time. I figured I'd ask here to see if anyone else has had this problem and found a way to fix it. Also, I have a feeling this could be related to WiFi being turned on, but can't confirm yet.
My phone was stuttering yesterday.
But that was only after installing smartbench and using theonscreen keyboard.
However, since I've upgraded to dk28, the phone does take (relatively) forever to shutdown.
It'll go black but the bottom lights would still be on and then like a minute or two later it vibrates and actually cuts off
Sent from my SPH-D700 using XDA App
When my phone does this, it reminds me that I like to have SeePU installed. It's pretty useful in pointing out the apps that are hogging CPU and most likely slowing down your phone.
For me it's often Touchdown, and I kill it and things are back to normal.
I have found a few things that are useful. When I need to reboot my phone I use quick boot from the market. Works every time. In between I use fast reboot also from the market. Try them and see how they work.
Sent from my SPH-D700 using XDA App
Thanks for the app suggestions. I like the taskbar icons for SeePU. It's always been useful on my Mac (stats from iStat). Quick Boot makes things easier as well.
Next time my phone hangs, I'll see if some process is taking 100% CPU.
The phone hung again, and it seemed like something was taking 100% CPU, if the taskbar SeePU icon is to be trusted. I wasn't able to figure out what the culprit was though, because the phone pretty much stopped responding. Otherwise I would have loaded Android System Info to check.
can the epic 4g run this lag fix? if not, do we have any other ways to fix the lag?
http://forum.xda-developers.com/showthread.php?t=784691
edit: nvm
So I was able to view Android System Info while my phone was hanging, but it did now show any processes taking 100% CPU, although the total CPU usage was 100%. My guess then is that the Android 2.2 OS is buggy.
However, I did find people who said leaving USB debugging on would fix it, so I'm going to try that.
For reference:
http://forum.xda-developers.com/showthread.php?t=826507
http://androidforums.com/desire-hd-support-troubleshooting/244553-100-cpu.html#post2140890
My phone hasn't hung for a while, so apparently enabling USB debugging prevents the hang / lag / crash / 100% CPU. Weird but I'm glad it works
Now the only problem is kswapd0 eating CPU sometimes. I think this is caused by lack of memory, but I'm not sure what I can do about it.
Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?
I have had similar issues a well, maybe happens once a week though. Mainly when I have my cassette adapter running and doing other things at the same time. Haven't gotten too bad to try repairing it yet though.
Sent from my DROIDX using XDA App
MrWall said:
Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?
Click to expand...
Click to collapse
Only time I ever had an issue like this was one of 2 things happened... either the phone overheated, or I ran the memory out... do you use a task killer? I personally like using a task killer, even though they say GB automatically shuts down background apps when needed, I always found my phone faster and more responsive using a task killer. Just a preference but TaskXP for multitasking works very well for me and it is free on the market. If you have any questions about setting it up you can pm me.
On another note... if you are using so many apps to listen to audio, I'm assuming you probably have it hooked up in your car, maybe on a dash mount... check and see how warm your phone gets, as my DX runs pretty warm too, I had to modify my mount to allow for heat dissipation and I never had a problem after that.
SGT+CM7=:-D
I don't use a task killer mostly as you stated because gb is supposed to manage it well enough but also because it doesn't suppress apps so I kept noticing things restarting right after the app killer did it's thing.
actually I mostly get around on motorcycle and I'm not a fan of using headphones while riding. for the most part, when I'm listening to my dx that's all I'm doing with it because I'm usually preoccupied with something else at the same time.
So in short, when it crashes it's when it's only playing audio
Good suggestions though since I didn't cover what I was doing when it crashes
Sent from my DROIDX using XDA App
A factory reset will cure this.
rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
one would think but I've tried that a few times with the first DX and it didn't resolve the situation.
rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
I'm sure there is more than one issue that could lead to the unexpected reboots, so I doubt there is any easy and universal panacea, much as I wish there were. Factory resets haven't worked for me on either of my 2 DX's, and I can guarantee that overheating is not relevant on mine. It comes and goes, and I thought that perhaps I had it beat, but it's still there.
I've been through a number of SBF's, cache clearing, data clearing, factory data resets, etc., app removals with no resolution. It's most prone to spontaneous reboots while running audio apps, or navigating with Google Maps.
I am not too familiar with some of the acronyms used here but I am having the same problem. The reboots started to happen after I downloaded the latet OS update code. So far Verizon has been unable to help me fix the problem,. I will be going back to Verizon today and will update you with the outcome. So far Verizon has not been all that helpful.
Verizon reloaded the OS yesterday. I will know if that cured the problem after I do an hour on the bike this morning in the gym.
Same issue
I'm having the same issue; it happens when using Google Listen or Audible, more frequently with the latter. I've noticed the problem happens most frequently when I hit the power button to turn off the screen; about a half-second after the screen turns off, the phone crashes. Sometimes it reboots itself, but most of the time I have to remove the battery and then turn it back on. This happens only when listening to audio, and it doesn't matter whether it's through the audio jack, Bluetooth or the speaker. I've formatted the SD card and done multiple hard resets, but the problem continues.
I noticed that my DroidX only seems to do it when the screen is off. As far as I can tell if you keep the screen on it should not crash.
Nobody seems to know what to do about it. Verizon knows about it but Motorola seems to be clueless. Their crappy tech support only said it was a problem with the phone, but didn't know if it was a hardware or software bug. I have has the issue across 2 Droid X devices so I figure it is more likely just Motorolas crappy software.
I have installed the latest revnumbers daily build and it hasn't conked out yet.
Verizon is of course happy to keep swapping them out under extended warranty coverage at no cost. Not that it actually helps much.