Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey
voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey
voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'
I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey
voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.
voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.
Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey
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.
First, I am straight vanilla on my EVO--stock ROM, no root, etc. But I have noticed a behavior pattern in Android that reminds me of Windows 95. I am not a heavy or light user, just standard. But I have noticed that after a month or so, the UI begins to get clunky or jerky or sporadic (put your own word here). But if I pull the battery for a complete restart, it runs as smooth as silk again for about another month, when I have to repeat the process.
This reminds me of the old days of Windows when even Microsoft recommended PC's and servers be periodically restarted to clean up memory issues.
You went a whole month without rebooting your phone??
I've noticed a little lag after a few days but I rarely go even that long without restarting for one reason or another. I always though periodically rebooting was just something that was good to do anyways.
That is pretty standard for smartphones. I restart mine every morning when I get out of bed.
the fact that you can go a full month without rebooting your smartphone says something I think.
Well, I haven't been tracking the interval on a calendar, but a month (plus or minus a week) seems about right. But I am astounded that this battery-pulling process is "common" knowledge or that anyone would would think that doing it every morning is an acceptable practice!! Seems that people that b*tch about wifi speeds and light leak would be putting a gun to their heads if they had to reboot every morning...LOL.
You are "stock" not "vanilla". The two are not interchangeable. Vanilla implies AOSP non-sense which is what you want if that ui is bogging you down. Try adw or launcher pro and that sense ui lag will be a thing of the past. A custom ROM like cm6, fresh, or baked snack will fix you right up.
Swyped on my EVO
I am pretty sure none of the people who answered pull the battery for a restart. It's as simple as getting a program (quickboot) from the market to do it or long press on the power button. That is not a hassle at all, and really, every smartphone should be rebboted from time to time. This phones are now mini computers and as such from time to time will need rebooting to keep things smooth.
+1, pulling the battery is not necessary to reboot. I don't know why Sprint would suggest that is any different than just rebooting..
whats the name of the App in the market that will reboot your phone for you at a specified time/date/interval?
I know its in the market (and requires root) but i cant remember the name
dmc971989 said:
whats the name of the App in the market that will reboot your phone for you at a specified time/date/interval?
I know its in the market (and requires root) but i cant remember the name
Click to expand...
Click to collapse
I saw the thread about someone asking if an app like that exists, I didn't think it had been made yet.
I can see how someone who is not rooted could go a month with out restarting there phone. I mean most of my restarts happen because i am flashing a new kernel or rom or some combination of the 2.
What others listed is true though almost all smart phones need a reboot from time to time. Even newer PCS with win 7 you should reboot now and then so this wasn't only windows 95.
Also as stated above you dont need to pull the battery just power down and power back on and you should be good to go.
I think having to reboot your phone is a ridiculous notion. Just because it has the functionality of a mini computer doesnt mean that shortcomings of computers should be forgiven...
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
icantdrawanime said:
I think having to reboot your phone is a ridiculous notion. Just because it has the functionality of a mini computer doesnt mean that shortcomings of computers should be forgiven...
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
Click to expand...
Click to collapse
hahahahaha...
good one
a power cycle is unavoidable, thats when your system cleans up and wipes whatever isnt needed like temp files and what not, even regular cellphones from time to time require a restart, all computers require restart, what im more interested in is how android handles memory fragmentation, in ubuntu, they recently released a kernal upgrade that allowed for ubuntu to handle huge file sizes but now requires defrag to be able to compensate for fragmentation caused by using such large files and i was told that android has some sort of 2gig limitation on the overall os and i believe apps have a 15mb write limit or something of that sort, would that be to try and avoid memory fragmentation??
icantdrawanime said:
I mean, hell, portable gaming systems are getting more and more popular, but no one says hey its okay for my ds to overheat because its becoming more like an xbox 360...
Click to expand...
Click to collapse
That's not a fair comparison at all. Overheating is something that can damage an electronic device. I've never heard of a phone getting damaged by rebooting it.
Hell, for all we know, the OP doesn't even need to reboot. Running a task kill might have been enough to fix his problems.
IDK about you guys, but my battery dies so often and quickly, I don't think I can go more than a day without it dying at least one...
Whats the big issue with restarting? Takes like 1 minute.
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.
Problems I've got with the Acer A500:
GPS is very weak. I get the best reception with the back of the unit facing the sky but in normal orientation I'm lucky to get 5 sats.
Compass doesn't work, always 90deg off
Digitizer unresponsive 3 times, had to power off each time. Strangely enough, the last time this happened the buttons at the bottom (home, menu, etc) still worked but nothing responded when tapped on the main screen area.
Have to be careful about plugging and unplugging items while the device screen is off. The headset icon is still showing in the tray after having disconnected a cable last night when the screen was off. Have seen problems where external USB devices aren't scanned if the screen is off.
System shut down 1 time after showing a low power notice. I was at 80%. Haven't had this happen again.
Market, Maps, Firefox crash a lot. The latter is probably Mozilla's fault but the core apps shouldn't be this crash-happy.
Bluetooth sharing only shows visible devices and not paired devices. What's the F-ing point of pairing if I have to make a device visible before I can send a file to it?
No media scanner notification. It takes a while to scan external USB media and there's no indication the scanning is going on. The only indication that it's done is when media starts appearing in apps like gallery. On older revs of the OS there is a notice that scanning is ongoing.
Copy/paste annoying. Especially that you can't paste if there's no text in your editor!!! In 2.2 you tap once to bring up the picker/caret (don't know what the google term is) and you tap that to get a popup menu for copy/paste/delete. On the Acer you have to double-tap to select text and only then do you get a menu on the top of the screen. Trouble is, if you have no text in your document you can't paste because there's no text to select!
Can't turn the d**n sound off on the camera.
Have to drill down into the settings turn the "ringer" off to mute the system. Why isn't there a dropdown icon for that?
Some of these are certainly Acer's fault and are related to hardware specific to this device. The UI elements I'm left wondering about. This is the only Gingerbread device I've really used and I can't tell how much is default behavior and how much Acer messed with the OS and borked it.
It's possible I've become spoiled by the devs on XDA. I'm coming from a Vibrant and the dev action is furious with that device. I've regularly upgraded my device with new ROMs on the order of every 2-3 weeks since October and I'm currently using 2.2.1 on my phone.
Given that the bootloader is locked (and encrypted?) I'm thinking dev action isn't going to happen real soon and I'm further thinking about returning this. I hate the idea of doing that because in a lot of ways this is a really nice tablet. It's got the form factor and weight I want. It's responsive. wifi is good enough for my purposes and I can carry it throughout home and work with no connection problems. I've found ways to make it part of my device chain (doc markup, blogging, reading, music playing) and the price was was low enough for me to give it a try. For the most part I like the device.
Trouble is, the bugs are like having someone standing next to you randomly poking you in the ribs. It's not enough to call the police but if he doesn't stop I'm going to punch him in the nose. With the Acer the bugs aren't bad enough for me to throw it out the window but they're getting bad enough that this thing may get returned.
For those in the know, how much of what I've complained about is normal Gingerbread and how much has Acer likely borked?
For reference my kernel is 2.6.36.3-00001-g9b3ce2b and build is Acer_A500_1.104.02_COM_GEN1
michaelh99 said:
Problems I've got with the Acer A500:
GPS is very weak. I get the best reception with the back of the unit facing the sky but in normal orientation I'm lucky to get 5 sats.
Compass doesn't work, always 90deg off
Digitizer unresponsive 3 times, had to power off each time. Strangely enough, the last time this happened the buttons at the bottom (home, menu, etc) still worked but nothing responded when tapped on the main screen area.
Have to be careful about plugging and unplugging items while the device screen is off. The headset icon is still showing in the tray after having disconnected a cable last night when the screen was off. Have seen problems where external USB devices aren't scanned if the screen is off.
System shut down 1 time after showing a low power notice. I was at 80%. Haven't had this happen again.
Market, Maps, Firefox crash a lot. The latter is probably Mozilla's fault but the core apps shouldn't be this crash-happy.
Bluetooth sharing only shows visible devices and not paired devices. What's the F-ing point of pairing if I have to make a device visible before I can send a file to it?
No media scanner notification. It takes a while to scan external USB media and there's no indication the scanning is going on. The only indication that it's done is when media starts appearing in apps like gallery. On older revs of the OS there is a notice that scanning is ongoing.
Copy/paste annoying. Especially that you can't paste if there's no text in your editor!!! In 2.2 you tap once to bring up the picker/caret (don't know what the google term is) and you tap that to get a popup menu for copy/paste/delete. On the Acer you have to double-tap to select text and only then do you get a menu on the top of the screen. Trouble is, if you have no text in your document you can't paste because there's no text to select!
Can't turn the d**n sound off on the camera.
Have to drill down into the settings turn the "ringer" off to mute the system. Why isn't there a dropdown icon for that?
Some of these are certainly Acer's fault and are related to hardware specific to this device. The UI elements I'm left wondering about. This is the only Gingerbread device I've really used and I can't tell how much is default behavior and how much Acer messed with the OS and borked it.
It's possible I've become spoiled by the devs on XDA. I'm coming from a Vibrant and the dev action is furious with that device. I've regularly upgraded my device with new ROMs on the order of every 2-3 weeks since October and I'm currently using 2.2.1 on my phone.
Given that the bootloader is locked (and encrypted?) I'm thinking dev action isn't going to happen real soon and I'm further thinking about returning this. I hate the idea of doing that because in a lot of ways this is a really nice tablet. It's got the form factor and weight I want. It's responsive. wifi is good enough for my purposes and I can carry it throughout home and work with no connection problems. I've found ways to make it part of my device chain (doc markup, blogging, reading, music playing) and the price was was low enough for me to give it a try. For the most part I like the device.
Trouble is, the bugs are like having someone standing next to you randomly poking you in the ribs. It's not enough to call the police but if he doesn't stop I'm going to punch him in the nose. With the Acer the bugs aren't bad enough for me to throw it out the window but they're getting bad enough that this thing may get returned.
For those in the know, how much of what I've complained about is normal Gingerbread and how much has Acer likely borked?
For reference my kernel is 2.6.36.3-00001-g9b3ce2b and build is Acer_A500_1.104.02_COM_GEN1
Click to expand...
Click to collapse
I'm not sure if you know this or not, but tablets and Honeycomb are pretty new.
rorytmeadows said:
I'm not sure if you know this or not, but tablets and Honeycomb are pretty new.
Click to expand...
Click to collapse
Yeah, I'm aware. How does that apply to my questions & issues with the A500?
michaelh99 said:
Yeah, I'm aware. How does that apply to my questions & issues with the A500?
Click to expand...
Click to collapse
Well, I think your thread is misleading. Tablets are new and there are going to be flaws in new products. That's why you don't buy the first new model of a car. But if you're going to, then understand there is always risk.
1. I have had no problems with the GPS.
2. I have had problems with the compass, but nothing unusual for a digital compass.
3. Unresponsiveness happens with pretty much every device. Mine has been unresponsive like 5 times already, but a power down and then up again fixes it beautifully. It's like a nice reminder to clear the system and make it run faster. This doesn't necessarily have anything to do with Acer. It could be Honeycomb.
4. Apps crashing. Happens. I'd think that it's Honeycomb, rather than Acer.
5. I've seen the headset icon on when I didn't have any headphones in. Oh no! Stop the presses! This occurs, sure, but that could be Honeycomb, not Acer. Also, are we sure it's not the music icon?
6. Bluetooth profiles are limited. Sure. But maybe that's a reminder to us all that Bluetooth is awful technology. This one is probably Acer.
7. Copy and paste, although annoying, isn't Acer.
8. Right now, it's not proper to open the bootloader for everyone. Don't hold that against any company.
Most of the things you mentioned really might have to do with Honeycomb rather than Acer. So don't trash the wrong company.
Now given that it's Honeycomb instead, it's new. It will have bugs and problems. Sit and wait or learn the trade and get in there and fix it.
Or wait until a future generation product.
Problems I've got with the Acer A500:
Digitizer unresponsive 3 times, had to power off each time. Strangely enough, the last time this happened the buttons at the bottom (home, menu, etc) still worked but nothing responded when tapped on the main screen area.
NEVER OCCUR for me
Have to be careful about plugging and unplugging items while the device screen is off. The headset icon is still showing in the tray after having disconnected a cable last night when the screen was off. Have seen problems where external USB devices aren't scanned if the screen is off.
NEVER OCCUR for me
System shut down 1 time after showing a low power notice. I was at 80%. Haven't had this happen again.
NEVER OCCUR for me
Market, Maps, Firefox crash a lot. The latter is probably Mozilla's fault but the core apps shouldn't be this crash-happy.
Just restore to factory default or clear the data in "manage application" can solve the problem
Can't turn the d**n sound off on the camera.
Root the device and remove the sound using root explorer
Have to drill down into the settings turn the "ringer" off to mute the system. Why isn't there a dropdown icon for that?
when you press vol +/-, there is a small icon on the right and you can adjust 3 volume settings
....
Ya, I'm pretty much in the rorytmeadows and ardatdat camp. Considering Acer did very little to their OEM copy, I'd place the blame for a lot of the issues on HC.
The compass is definitely finicky. I've only ever got a solid read when my GPS was tracking - when it's not, the compass is definitely off (using GPS Essentials here which could also be an app issue). If there is a common degree variance, this can be coded in/out. Also, orientation matter - whether you have it in portrait, facing you, landscape facing up... There's a difference and the gyro checks.
I understand where some of you guys are coming from re. new releases having bugs. I can't accept that viewpoint. I paid for this device and while a few bugs are to be expected these days, some of the problems amount to beta level bugs that should have never left the factory.
If there were going to be regular releases of updates I'd feel differently but it seems clear that releases will likely only come from the devs and only after jumping through the hurdles and hoops that Acer has put in their way.
I think the A500 was worth trying but I'm still not sure it's worth keeping.
A BETA bug is something that is consistent (across all testware) and repeatable. Nothing you listed falls near that.
gammaRascal said:
A BETA bug is something that is consistent (across all testware) and repeatable. Nothing you listed falls near that.
Click to expand...
Click to collapse
I think we'll have to agree to disagree. The general level of bugginess shown by the complaints in this forum alone cause me to classify this (and many other android devices) as beta.
With so many people willing to be paying testers, the manufacturers don't have any incentive to behave differently.
michaelh99 said:
I think we'll have to agree to disagree.
Click to expand...
Click to collapse
Ya, but... Nothing you listed is consistent and repeatable... Where exactly is the disagreement?
The general level of bugginess shown by the complaints in this forum alone cause me to classify this (and many other android devices) as beta.
Click to expand...
Click to collapse
I don't see it. Maybe I'm biased *shrug* The majority (not all, of course) complaints or issues with the a500 (be them HW, SW or HC related) on this (and other) forum are sporadic and inconclusive. Not a lot of serious testing happening and a complaint like 'my gps can't see any satellites' doesn't mean a whole lot without more granular info. It doesn't help and it certainly shouldn't be used as part of a rationale. You gotta take those kinds of half-thought out complaints with a grain of salt.
With so many people willing to be paying testers, the manufacturers don't have any incentive to behave differently.
Click to expand...
Click to collapse
I read this all the time - with games mostly, but the argument is the same.
How when a new game is released (pick your poison) you're bound to get a very small, thought vocal, minority who dig their nails into the support section complaining about 'players are paying to be testers' - or - 'their computer should be able to play it' etc. The argument being, 'it's suppose to act the way I want it to act' when in fact, that is never the case. With games, with hardware - software. 'It's suppose to act the way they want it to act' - We're just consumers. We consume. They create, we consume.
Now, I'm not trying to discount the importance of your view (I know it reads like I am but I'm not trying too - just trying to further the discussion). You're obviously having issues with the a500 and far be it for me to make lite of them. I think what is key here is that, for the majority of us, there aren't any of these kinds of issues and that, of the ones you listed, few are consistent and repeatable.
So I chalk it up to one of two things - you got a bum tablet or it's user error.
gammaRascal said:
Ya, but... Nothing you listed is consistent and repeatable... Where exactly is the disagreement?
Click to expand...
Click to collapse
Most of the problems are very repeatable on my machine. In the end, that's the only one I care about and the only one that matters to me.
Not a lot of serious testing happening .. You gotta take those kinds of half-thought out complaints with a grain of salt.
Click to expand...
Click to collapse
You're mistaking brief descriptions for incomplete testing or "thoughts.". I haven't described my testing methodology nor put down all the tests I've done because I'm not game for writing a paper on the subject.
I've been around quite a while and have been in development for decades and done my time in QA. I know how to test. Which is part of the point. I'm not running into these problems while doing things that qualify as something a user shouldn't do and I'm really not interested in helping Acer or Google iron out the bugs in their system.
Hell, I just did a factory reset and without installing any apps I had the Market crash twice while just browsing my paid apps list.
The argument being, 'it's suppose to act the way I want it to act' when in fact, that is never the case. With games, with hardware - software. 'It's suppose to act the way they want it to act' - We're just consumers. We consume. They create, we consume.
Click to expand...
Click to collapse
Yeah, know where you're coming from. My complaint isn't the same.
I want it to behave the way it used to
My UI complains stem from behavior that was present in 2.2x and is very different but harder to use in 3.x. They futzed with the UI for no good reason IMO.
So I chalk it up to one of two things - you got a bum tablet or it's user error.
Click to expand...
Click to collapse
Well, it's not user error
I've just factory reset the thing and I'm going to spend a few hours using just the apps I can't live without and leave off the questionable utilities that might be destabilizing the system (widgetlocker, stuff like that) and see where that gets me.
So far it's not good though. 2 market crashes with a stock system.
All very fair and understandable. I've had my share of freezes/lockups and FC. There is no doubt that updates are needed. I'm just not convinced the majority of the issues are Acer related, but rather, Honeycomb related.
Hey Michael do us a favor and return it. I am having none of the issues you have listed with mine with the exception of some FC apps, but I attribute this to the apps not being optimized for HC since the tablet specific apps work perfect.
Sounds like you got a bum tablet, so you have 3 options. 1) keep it and keep complaining and hope you or another dev can fix your problems. 2) exchange it for a new 3) return it and wait a year or so til HC is more stable and out of this "beta" phase.
Sent from my Droid using XDA Premium App
michaelg1030 said:
Hey Michael do us a favor and return it.
Click to expand...
Click to collapse
Do you a favor? In other words, stfu?
BTW michaelh99, I appreciate the fact that you're not flying off half-cocked and taking anything I (or others) have said out of context. It's important for mature and focused discussion to stay calm and proactive - with the goal being, resolution - not argument.
If bugs were completely out of technology before it was released to the public then we wouldn't have technology.
gammaRascal said:
BTW michaelh99, I appreciate the fact that you're not flying off half-cocked and taking anything I (or others) have said out of context. It's important for mature and focused discussion to stay calm and proactive - with the goal being, resolution - not argument.
Click to expand...
Click to collapse
Thanks.
I'm not really expecting people to supply resolutions to the problems I've seen. It looks like most of them are problems with the first release. Some could be due to my personal usage patterns (apps I have installed) but others are clearly out of box bugs.
It may be that I need to bite the bullet and get a larger version of my phone (Samsung), which I've been very happy with. Like many people I wanted to pay as little as I could. May be that I went too low for my expectations.
rorytmeadows said:
If bugs were completely out of technology before it was released to the public then we wouldn't have technology.
Click to expand...
Click to collapse
If I can crash the market by browsing my paid apps after having done a factory reset and without having installed anything I would say they haven't met the minimum necessary to release the device.
The market is a core component of the system. If that's unstable, the whole device is suspect.
Why did you start this thread knowing that no matter what good things are said about the tablet, nothing would change your mind. If you are not happy with the device then return it and go on. The majority of the owners here are very satisfied with both the hardware and software of the Acer. I don't think anyone was expecting HC to run as smooth as apple os and if these were your expectations then you will never be happy for the time being.
Again, I'm assuming you started this thread hoping someone would agree with you, but the fact is that most of us do not. Your problems are way out of the ordinary and for all intended purposes unacceptable in this device. So again, return it. Your not doing yourself any service by keeping a faulty product.
Sent from my Droid using XDA Premium App
Good point michaelg1030.
michaelh99 said:
If I can crash the market by browsing my paid apps after having done a factory reset and without having installed anything I would say they haven't met the minimum necessary to release the device.
The market is a core component of the system. If that's unstable, the whole device is suspect.
Click to expand...
Click to collapse
michaelh99 have you considered posting a bug report to Google? For what it's worth, it may at least bring the issues you're having to their attention. It's placating but it can't hurt.
http://code.google.com/p/android/issues/list
New NC w/1.3 did BN stock update to 1.41, confirmed all working. Then I applied the manual nooter 5-12-20 using CWM sd with no errors or issues in installing/rooting/booting. A couple issues/observations after successful booting.
Posting here as new user hoping other new users in same boat without enough time on forum to be allowed to post to the dev thread (I've read every page of the thread and every post since 5-12-20 was released mult times so can say these questions/observations are either not observed or observed and not definitively answered that I could find).
A couple observations and questions:
1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine. I, however like others saw many common apps simply not there like Google's own Voice app, facebook app, etc. Maybe someone can tell me, should my rooted nook color NEVER even see those 2 apps in the market? If it should, something went wrong. **Yes, I went back to page 1 of that thread and applied the "market visibility fix" which really needs to be updated to say you MUST uninstall the market "update" to roll it back to the original rooted market then apply the steps - then yes, it worked in the sense that all apps EXCEPT for some pretty BIG ones like facebook, google voice, etc are listed. This one is the primary reason I'm rooting and I've read a LOT of different "fixes" of changing DPI, fingerprint, build.props, etc. yet in any of the original root instructions seen an indication that this is a STANDARD action every rooter needs to take. Why do some need this "workaround" of hacking dpi and props and some don't? Is it simply that those that don't are not using these very common apps like facebook? Someone could make my day by helping out with this as I really hate doing things half-assed and having something half-working.
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Again, you guys rock and I love the NC, any help on these would be greatly appreciated!
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Thanks but as I stated only after the manual nooter is the wifi dropping - no need to get out wireshark when 4 other wifi devices including a non-rooted nook in the same room without dropping but thanks for the suggestion!
BTW, I should ask are you rooted and which version, etc?
WyldWolf said:
[...] 1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
Click to expand...
Click to collapse
I did not experience this issue. In fact, on B&N 1.4.1, my wifi was more dependable than on CyanogenMod. I suspect a lot of has to do with specifics on your wifi setup, including router make, security used and so forth. You could try tweaking parameters to see if it helps. Was it dropping as much before you ran MN? I wouldn't expect what was done with MN to make a difference. Are you using Dalingrin's kernel or anything similar?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine.
Click to expand...
Click to collapse
Hmm. I never got around to trying Google Voice, and have no use for Facebook, so can't say for sure those were there. I've since nuked 1.4.1, so can't test now either. I can say that I had well over 100 apps that I commonly use on CM loaded, and didn't find any that I weren't visible in Market without any tweaks. It did take a long time for Market to update, but after that, it worked smoothly. You might try accessing the Market via the web interface and see if those apps will install from there. I did that a few times. Maybe that trips something?
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
Click to expand...
Click to collapse
My power consumption was initially very good, but after a week or so, I started seeing the battery drain go to 3-5% per hour. Unfortunately, 1.4.1 hobbled a lot of troubleshooting tools, so I wasn't able to nail down the culprit. This is what ultimately drove me to abandon 1.4.1 for CM again.
I did try renaming phone.apk and others that have been recommended, but my NC seemed to get very unstable thereafter. Lots of spontaneous reboots and the like. I put them back and really didn't see a big difference one way or the other that I can attribute to these. From everything I've read, they're not likely to cause noticeable drain, but some other standard functions depend on them.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
Click to expand...
Click to collapse
Cost is probably the main factor. Netflix from B&N supposedly supports HD while the Market version does not. On a 7 inch screen, I couldn't care less. Netflix off of the Market looks pretty good, so I'm happy.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Click to expand...
Click to collapse
What you do to stock is pretty much independent of dual-booting.
Bobstro,
Thanks so much for the input! As for the wifi, it does seem very specific to after I ran the MN on 1.41, in fact it never once dropped and I went back to stock 1.41 for the last day and haven't seen it drop again (my wife's is stock 1.41 and doesn't drop either when my MN does so unless it's a hardware issue I'm guessing it's something in the MN process, driver, etc.)
One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked. Also, unlike the 1.3-1.41 upgrade, when I flashed right to 1.41 a couple things came up that didn't after upgrading mine and my wife's to 1.41, namely netflix right on the home screen touch to install, and the nook friends app right on the home screen.
Have you come across anything that would indicate why my touchscreen went dead no matter how many times I rebuild the CWM card, formatted the nook partitions correctly and flashed without error? It really made me worry I had a bad unit but like I said worked out of box, worked after 1.41 upgrade, worked after latest MN, only once I returned to 1.3 stock did it die until flashing 1.41 directly.
Interesting about the market, I did have thousands of apps just not some of the most common big ones and I did try through browser it told me facebook was incompatible with my device which led me to all the "hack the dpi, props file, etc." threads I just didn't want to be part of a minority for for some unknown reason had to hack workarounds if 99% of folks running the MN could simply install facebook and google voice from market without workarounds.
Thanks again!
Edit: on the dual boot I thought there was a way to install CWM or something to internal to allow dual internal booting from stock (nootered) and CM7 - I'll keep looking.
WyldWolf said:
Thanks so much for the input!
Click to expand...
Click to collapse
I'm happy to help where I can. The smart folks here on XDA have helped me tremendously, so I trying to pay it forward as best I can!
[...] One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked.
Click to expand...
Click to collapse
EDIT: Sorry about that strange post. I wanted to point you to the thread about the hardware having changed with more recent NC versions. 1.4.1 includes the newer drivers. Depending on where you get your older versions from, they may or may not work.
Well that 'kinda" makes me feel better that I at least don't have bad hardware, had I known the 1.3 that's posted was "different" then the 1.3 that came on my newer unit apparently must have had the newer screen drivers I would have backed it up - surprised someone hasn't posted it. I mean, mine came with 1.3 installed and the screen worked so it must have had the newer driver until I wiped it, right?
Also, do you have the links you referred to for the screen issues thread?
Thanks again!
The ongoing discussion I referred to is here. On page 2 or so, I've got a link the the original post.
HimWill said:
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Click to expand...
Click to collapse
Do look at WiFi, Once I Locked it on channel 1 it is rock solid reliable.
Bobstro,
I'm guessing your battery life must be a typo, at 10% an hour discharge would be 10 hours of runtime - they advertise 8. 3-5% sounds awfully low. Mine out of box is at about 10% an hour with wifi on and screen at 30% with constant online web browsing, maybe an app or two install, launching in and out of system apps, etc. - constant "activity" on my part not just flipping book pages or watching a video, etc.....I hope my unit is on par with others.
I also noted that my wife's refurb bought about thanksgiving that does not have the "new" screen hardware mine does actually looks side by side more blue/white with mine slightly yellower tinge which annoys me a bit. I know from years of jailbreaking and swapping iphones that there was definitely a difference in screen colors as they went from the 3g to the first 3gs I had, same thing blueish/whiter to a more yellow tinge - I can't win! LOL
Ah, sorry for the ambiguity. That was 3-5% while idle with screen off, which is far worse than normal. I expect to see 4-6% drop while idle with screen off overnight, max.
While in use, consumption is roughly 10% per hour, and mostly due to screen, which I usually run at 25%.