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.
It went from extremely rarely doing it to three or four times just the other night in the span of a few hours. I can't reproduce it on command but it happens when I lock the screen and put it in my pocket. Then sometimes when I take it out it is entirely non-responsive, even the power button doesn't work. I have to remove and reinsert the battery.
It could be ADW Launcher or WidgetLocker since those are the only two programs always running, but I was hoping someone else experiences a similar issue. It hasn't happened when I normally lock it yet though, so it could also be the proximity sensor maybe?
Having the same issue (on Bell as well), but not running either of those two apps. Was almost to the point of returning the phone and then installed JM7 and it's been better, although not perfect. Last night it locked up with NoLED displaying an icon, so I've deleted that app to see if that's the issue. It hasn't locked up today, but it did reboot a few hours ago seemingly at random. :shrug:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
clubtech said:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
Click to expand...
Click to collapse
Oh, that doesn't sound pleasant at all...
I'm outside of Bell's 30 day exchange period plus I've talked for over 30 minutes, so I'll have to go through Samsung if it completely breaks. On the plus side, a phone from them should be three button recoverable.
Although I can't be without a phone for weeks, I hope it's not the SD card.
Mine Lags like crazy once every few days till the point I need to restart it. Any idea why this is do?
Sent from my GT-I9000 using XDA App
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
AllGamer said:
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
Click to expand...
Click to collapse
All gamer has a good sugestion here BUT we are going to get people flaming the fact that Android shouldnt need task managers.....
Ho hum..
TBH in my experience, I have found (after a couple of hard resets) that there appears to be a size limit for installed apps. Once I get over this size limit, I get LAGTASTIC, phone slows to a snails pace, then I remove a few of the apps and I am back at light speed again....
I cant say what the limit is, but I know when I have hit it - I would then uninstall a lame app or two and get back running.
Yes a lot of people "claims" that, but yet you do a search in Android Market, you see LOTS of Task Manager / Killer apps for every phone.
they were not designed for Galaxy S, they were designed long ago for all the other phones that had and still have the same problems of memory management causing lags
Android is not robust enough to survive without one
heck not even Windows 7 or Windows Mobiles phone
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Frostshock said:
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Click to expand...
Click to collapse
i don't think that is the case with the Galaxy S
however back then my Treo 650 did suffer from that.
if you believe that is the problem then try this
http://forum.xda-developers.com/showpost.php?p=7999389&postcount=28
more cool apps here http://forum.xda-developers.com/showthread.php?p=7999389
So, my phone has been running fine for weeks (it was at I think like 600+ hours uptime before I had to reboot it for the first time two days ago). I'm running Apex 1.4.1, with no custom modifications. I was using it one day, then a little later it just started freezing for several seconds anytime I tried to do anything, then unfreezing for a couple seconds, then freezing, etc. I rebooted it, then it was fine for a little while. Then I was texting someone back and forth for an hour or so, and all of a sudden it stopped sending my messages. I rebooted, and it was able to send again. Now today apparently she isn't getting them again, because she asked the same question I already replied to, over an hour later (I mean, she could have just not seen the reply, but with the other recent problems I'm not betting on it...).
Has anyone seen issues like this? Also, come to think of it, Yahoo Mail has been acting just retarded...it keeps disabling status bar notifications on its own (twice so far), but regardless, when it IS notified, it's not letting me know when I get new emails, I have to go in and look. My batteries been dying a LOT faster, and my data usage has been steadily climbing over the last couple days (I haven't downloaded anything, and my normal usage recently has only been very basic) and I have a feeling Yahoo Mail has been constantly trying to connect but failing, except for when I manually go into it? But that's just a guess.
This is all just bugging me, so any suggestions would be helpful. I can just backup my needed apps, wipe and re-flash Apex, but if anyone has any other suggestions I would love to hear them. Thanks
Well I think you went wrong when you didn't shut it off for over 600 hours. Did you really need it to be on at that time? Even at night?
But anyway that's just my rant. Reflashing apex would be a good place to start. And make sure you just wipe everything. If that doesn't work, you may want to go completely back to stock and then back to apex
So you're saying this OS is not as stable as Windows? Because I've had Windows OS's stay running for months without issue. Gee, if Android isn't is good as Windows, maybe I should look into getting a WP7 phone... /sarcasm
If there aren't issues, then there's no reason to turn off your phone. Shutting it down at night is good if you don't want to charge it, but it really shouldn't be a requirement unless if Android isn't ready for prime-time (and no, I'm not saying that's the case). I had an issue, I rebooted, I had another issue, I rebooted, I had ANOTHER issue, rebooted, and so far it's been good since yesterday afternoon.
I really think it was the Yahoo Mail app though I don't know why it would have prevented sending text messages... I did a force stop, cleared it's data, removed it, rebooted, and then reinstalled the app. So far, it's been working OK from what I can tell. The data usage has slowed, battery life seems to be good again, and I'm getting notified of new Yahoo emails.
Actually I am not at all concerned with the software. I was talking about the hardware. Would you leave your computer running for 600+ hours?
Like I said, I have. My file server (Windows Server 2003) has been running (except for a few brief shutdowns for hardware upgrades/swaps) for over 2 years. My main PC (Windows 7) has been running, for the most part, except for a few times when I just felt like shutting it down, for probably the last 6 months.
Ok well if it works for you, then great keep doing it. But I'm just saying, as a computer guy, that is just a general bad idea
Nice to know, but I'm also a "computer guy" (professionally) and as a rule of thumb I keep my office computer on 24/7/365, as well as my home computers.
sfreemanoh said:
Nice to know, but I'm also a "computer guy" (professionally) and as a rule of thumb I keep my office computer on 24/7/365, as well as my home computers.
Click to expand...
Click to collapse
Since you are a computer guy, could you please explain how there aren't any adverse effects on your hardware from keeping it running? Primarily on the cpu and fans? No chance you could burn something out?
Jmoney47 said:
Actually I am not at all concerned with the software. I was talking about the hardware. Would you leave your computer running for 600+ hours?
Click to expand...
Click to collapse
Why would you shut it off? I don't think leaving it on all the time is the issue. why shut your cell phone off? I think that's stupid. Then again I'm a midnighter so I guess things are different for me. I never shut off my cell phone or PC.
Jmoney47 said:
Since you are a computer guy, could you please explain how there aren't any adverse effects on your hardware from keeping it running? Primarily on the cpu and fans? No chance you could burn something out?
Click to expand...
Click to collapse
It's designed to run like that. I'm a big PC guy as well. I do a few custom builds here and there. Seriously turning it off and on all the time it going to cause more damage (especially to your HDD) then keeping it on all the time. It's like a car being in stop and go traffic versus highway mileage. I think the last time I shut my PC off was around Christmas cause I had to reformat and couldn't get it done before I went to work so since my network wasn't up yet no reason to keep it on.
Computers aren't like cars..."gunk" and "sludge" (and yes, I'm getting these highly technical terms from TV because I know crap about cars) don't build up in computers. Pieces wear out, sure. But that can happen just as easily from frequent turning on and off. Like I said, my two computers at home stay on almost constantly, and I don't exactly dust or vacuum frequently. The last thing I had to replace was in my gaming PC, and that was the video card since it was two years old and couldn't play Crysis 2 well enough.
sfreemanoh said:
Computers aren't like cars..."gunk" and "sludge" (and yes, I'm getting these highly technical terms from TV because I know crap about cars) don't build up in computers. Pieces wear out, sure. But that can happen just as easily from frequent turning on and off. Like I said, my two computers at home stay on almost constantly, and I don't exactly dust or vacuum frequently. The last thing I had to replace was in my gaming PC, and that was the video card since it was two years old and couldn't play Crysis 2 well enough.
Click to expand...
Click to collapse
I don't know much about cars either. Maybe I wasn't using the correct tone, but I actually agree with you. Like I had said in my post I keep my machines running 24/7 usually same with cell phone. I don't know crap about cars either the only reason I used the comparison is that wear and tear from city driving or stop and go traffic (when compared to turning your pc on and off frequently) is worse than freeway or long distance without stop driving (as referring to keeping your PC on) So yea we are pretty much saying the same thing
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Jmoney47 said:
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Click to expand...
Click to collapse
Well...yeah, obviously. But if someone tries to call me in the middle of the night for an emergency, and I don't get the call because my phone was off, well, that would suck. But with Apex, I've went to sleep on, for instance, 80% battery, woke up, and the battery still said 80%. As for my computers, well, yeah, that costs me a little more per month, but it's not breaking my bank, so it doesn't bother me.
cstrife999 said:
I don't know much about cars either. Maybe I wasn't using the correct tone, but I actually agree with you. Like I had said in my post I keep my machines running 24/7 usually same with cell phone. I don't know crap about cars either the only reason I used the comparison is that wear and tear from city driving or stop and go traffic (when compared to turning your pc on and off frequently) is worse than freeway or long distance without stop driving (as referring to keeping your PC on) So yea we are pretty much saying the same thing
Click to expand...
Click to collapse
Lol Sorry, I wasn't referring to your posts (we just both happened to use car references).
Jmoney47 said:
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Click to expand...
Click to collapse
Yea but honestly if your pc isn't super holy **** beast mode it isn't going to be that noticeable. I have a nice higher-end PC and it isn't that bad on my bill.
original roms dont seem to suffer from these issues.
every custom rom i tried(nand and SD) had same issues after battery went dead.
isnt there a safety shutdown feature that can be added to prevent this?
Nand roms shouldn't be so bad, I have run my battery dead a bunch of times on my phone with UD 3.0.0 RC1, and never has it caused a problem. But running the battery dead on an SD build is where you can get big problems, because the entire system loads from the SD card, and by letting the battery run dead, Android doesn't get a chance to unload properly, as the card is still being written to when shutdown takes place, alot of the time corrupting the sd card or the Android directory or the data.img
Sent from my HTC HD2 using XDA App
The issue isnt the ROMs, its a MAGLDR bug. Phone cant charge under magldr.
Workaround: Boot into MAGLDR and then into CWM. Charges under CWM.
OR
Change from MAGLDR to CLK
Andy
Boradan said:
The issue isnt the ROMs, its a MAGLDR bug. Phone cant charge under magldr.
Workaround: Boot into MAGLDR and then into CWM. Charges under CWM.
OR
Change from MAGLDR to CLK
Andy
Click to expand...
Click to collapse
Wasn't the question...
Anyway, some apps store data on the sd card, when it shuts down suddenly due to empty battery, this data can get corrupted (That's why most roms don't use DATA2Ext but App2SD+, to prevent this). That's why most (if not, all) NAND Roms don't have this issue (at least, It never occurred to me) but SD roms do, as huggs explained.
isnt it possible to make an app that shuts off the phone i nstead of letting it die?
I use an ext4 with DarkTremor's A2SD script and never had corruption from running out of battery. I could just be lucky, idk.
Sent from my HTC HD2 using XDA App
man this is BS it has to be plugged inconstantly in order to keep it alive its like my sony laptop with a 2.4 ghz pentium processor and bigass screen.
the battery only lasted 3 hours.
i go to work and leave the phone untouched for the whole day the battery goes to half thats the ONLY way i can make it last till the end of work day.
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
and sometimes i dont have a charger so the phone dies because it cant shut down on its own.
and to add to that theres a GREAT!!!!! feature that conveniently turns the screen on and turns off all the power saving features such as dim screen.
so it turns the phone on starts buzzing and screen on full brightness, to let me know that my battery is dying WTF really???
fuzzysig said:
man this is BS it has to be plugged inconstantly in order to keep it alive its like my sony laptop with a 2.4 ghz pentium processor and bigass screen.
the battery only lasted 3 hours.
i go to work and leave the phone untouched for the whole day the battery goes to half thats the ONLY way i can make it last till the end of work day.
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
and sometimes i dont have a charger so the phone dies because it cant shut down on its own.
and to add to that theres a GREAT!!!!! feature that conveniently turns the screen on and turns off all the power saving features such as dim screen.
so it turns the phone on starts buzzing and screen on full brightness, to let me know that my battery is dying WTF really???
Click to expand...
Click to collapse
We at XDA made Android available for an aging phone of yours at *NO COST* involved, If you have a problem live with it until we learn how to fix it. And if this seems too unbearable, just STFU and stay with HTC stock WM6.5 rom.
if you make a ruler you make it exact.
even if you give it away for free.
you dont make a ruler that measures 1 inch short...because people depend on it.
i just hate all these BS claims about the system beeing stable when its not even close.
i installed android because i thought it was ok for everyday use by someone that doesnt sit here on this board for hours trying to keep up to speed with all the latest updates.
im very happy that this android development extended the life of a factory crippled phone but dont tell me that im the only one having this issue.
u have no idea how many times this thing freezes up right when i need it. when im in the car driving and need to use google maps but cant because this **** is bugging out.
or now for example it doesnt even load up sense it gives me the com.htc.bgp force close.
im very fn tired of this loading and unloading of cooked roms and actually looking for a phone that came with android.
like i said if you make something, EVEN IF ITS FREE, you are still responsible for making it work because people depend on it. and i dont have 2-3 hours a day to spend reading through this board trying to make my phone work again.
you can hate me or disagree i dont give a faq this is my opinion.
fuzzysig said:
if you make a ruler you make it exact.
even if you give it away for free.
you dont make a ruler that measures 1 inch short...because people depend on it.
i just hate all these BS claims about the system beeing stable when its not even close.
i installed android because i thought it was ok for everyday use by someone that doesnt sit here on this board for hours trying to keep up to speed with all the latest updates.
im very happy that this android development extended the life of a factory crippled phone but dont tell me that im the only one having this issue.
u have no idea how many times this thing freezes up right when i need it. when im in the car driving and need to use google maps but cant because this **** is bugging out.
or now for example it doesnt even load up sense it gives me the com.htc.bgp force close.
im very fn tired of this loading and unloading of cooked roms and actually looking for a phone that came with android.
like i said if you make something, EVEN IF ITS FREE, you are still responsible for making it work because people depend on it. and i dont have 2-3 hours a day to spend reading through this board trying to make my phone work again.
you can hate me or disagree i dont give a faq this is my opinion.
Click to expand...
Click to collapse
Wow, you're an ungrateful bastard (to quote the 'you are a noob on XDA Developers video) IMO. How can you not appreciate what the Devs here are doing? They put in hours and hours of work, and you still don't appreciate how brilliant it has made the HD2?! Please, make us a perfect ROM, and share it with us, so that you can show us your perfect skills. Don't you read up on the issues of each ROM before flashing it?
Also, the system is EXTREMELY stable. My CM7 HD2 is far faster than my friend's DesHD. I get better battery life and it's just faster in general. You should really be more appreciative of the hard work of the brilliant devs here and also, before accusing people of BS and lying, think about whether it may be a problem with you.
Please, give your HD2 to someone with the mental capability to use it.
fuzzysig said:
the battery only lasted 3 hours.
...
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
Click to expand...
Click to collapse
fuzzysig said:
u have no idea how many times this thing freezes up right when i need it.
Click to expand...
Click to collapse
faulty phone/battery.
yea thats what comcast says every time i make a trouble call
oh ur modem is bad... only to find out that their network has problems again and again.
my battery is fine and so is the phone.
it worked without a hitch for 4-5 months untill battery died first time. since then the problems just been piling up.
and finally today it wouldnt even show the home screen.
so again for the 4th time i lost all my new contacts and whatever information i had on it because it cant shut down properly when its dead.
im picking up an htc sensation that has android already on it so i dont have to deal with this bs no more.
and **** you MR public defender i never said i hate the developers and in any way ungratefull. i was trying to figure out how to deal with this problem untill people started accusing me of beeing ungratefull.
i know what it takes to make this work and have alot of respect for people that do it. but you put urself in my shoes maybe for a second.
i have my office on this phone and whenver it doesnt work i cant do **** anymore.
i had txt messages, notes, phone numbers etc saved here that i wasnt able to recover and had to reset my phone in order to make it work again.
spent 5 hours trying to make it work since yesterday so now tell me how the faq am i supposed to feel after dealing with this crap.
i switched to this phone because everyone claims its STABLE. yea stable untill your battery dies and then **** starts happening...
i went through 6 different roms that means every time i have to spend hours setting my customizations etc and saving the data that i have on it.
how convenient is that.
beeing faster doesnt mean its more stable btw...
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