Related
Hi guys.
I don´t really know what´s going on with my LEO
Since I got android on it, it goes off at least once per day suddenly...
I´ve changed ROM´s, I tried 5 different ones, (now I got chuckydoid), format the SD card (eaven I changed it for another one) but still doing it again and again.
What coul be the problem?
It could be the build you are using or some app you installed in Android
elmonch said:
Hi guys.
I don´t really know what´s going on with my LEO
Since I got android on it, it goes off at least once per day suddenly...
I´ve changed ROM´s, I tried 5 different ones, (now I got chuckydoid), format the SD card (eaven I changed it for another one) but still doing it again and again
What coul be the problem?
Click to expand...
Click to collapse
does it get hot before it reboots, are you using an overclocked kernel?
Temperature is normal, I have a non overclocked build.
It happens to me with every build, but I thinking that maybe it is an aplication I installed last days...Do you have any problems with "whats app"?
Keep in mind what type of apps you're install and using to find the culprit. Also, try to keep apps to a minimum to see if it helps.
Another thing. Please describe what you were doing when it shuts off. Were you online? Listening to music? What was your battery status?
The battery in Android is not fully calibrated. For example, mine will shut off at 10% almost all the time. When I power it back on, winMO will list the battery as >1%.
The other way round for me....
since I am using Android on my Leo I don't have to reboot any more!!
The other day I ran our of battery and it was weird to see WM again!!
I use FroyoStone Sense -just incase it helps-.
I would just like to know if you experts here at XDA know a solution to this. I am using the UnOff 3.0 ROM, I seriously have next to almost no apps installed, but I do have the last version of Android that Darkstone created (3.2 I believe), HSPL 3.0 and I have installed Hastarin to overclock my phone. My phone just keeps overheating and rebooting, I can't use my phone to use apps or watching videos.
I am willing to delete every file on my SD card and phone memory to fix this problem, but this is obviously my last option.
Please help me XDA, and I am very sorry if this similar situation has been solved here before, if so, please link me.
help me please
This is a known problem with the HD2 and I was suffering this during summer time when using it as navi in my car
When batt-temp rises over some 46 °C and in cahrging cradle lights start to blink orange-green and not charging any more, when temp rises further HD 2 freezes and/or reboots.
Gets worse when android runs
No solution to this yet.
It started on my HD2 (ex) last month. Came from nowhere, did not install anything or made any changes, no drops or whatsoever (in otterbox by the way) Shipped it back and got a new one (I assume refurbished)
I would recommend the same, I tried, flashing rom, clean install, (no install at all) even if you go back to factory settings, it reboots watching transformers.
Now i run wmo + android (darkstone ram edition- crazy fast) at the moment android draws 300 ma even with that no reboots at all.
CGCR said:
I would just like to know if you experts here at XDA know a solution to this. I am using the UnOff 3.0 ROM, I seriously have next to almost no apps installed, but I do have the last version of Android that Darkstone created (3.2 I believe), HSPL 3.0 and I have installed Hastarin to overclock my phone. My phone just keeps overheating and rebooting, I can't use my phone to use apps or watching videos.
I am willing to delete every file on my SD card and phone memory to fix this problem, but this is obviously my last option.
Please help me XDA, and I am very sorry if this similar situation has been solved here before, if so, please link me.
Click to expand...
Click to collapse
i have highlighted what i think might be the problem in your quote above.
when overclocked, the device will generally shutdown/reboot when the CPU is mildly stressed if the CPU can't handle the voltage/frequency combination. running your CPU overclocked to the edge of stability CAN damage your hardware. usually, removing the overclocking makes the system stable again, unless some sub system has been damaged, perhaps due to prior overclocking.
see if any of the above might have happened with you. sounds plausible...
You do know what "overclocking" means, right OP?
same problem with my mates phone it was overheating and rebooting by itself.it was a hardware problem,because its under guarantee for 12 months he send it to tmobile in uk.and they send it to htc,they changed the hardware.the only reason i know they changed the hardware because his phone was unlocked and had a different i.m.e.i number.when the phone came back it was locked also.only hardware problems has 12 months guarantee.if your phone is less then a year try this,they fix it for nothing.its htc guaranteed.
make sure you flash back the original rom and get the hspl out.if they find out they wont fix it,and charge you money to send the phone back to you.
shame this is happened,i hope you sort it out a.s.a.p
I recently noticed that when I remover the battery for more than a minute, the clock (after starting up) would be late. The more I leave the battery out, the more the battery will be late. I recently tried several Android NAND roms & WP7. I have returned back to WM.
I don't remeber noticing this before, I have Hard-Reset the phone, re-flashed, HSPL, Task29, and still the same.
Is it my HD2 only? a Hardware problem (covered by warranty)? Or is it something normal?
Thanks for any feedback.
The internal battery on the board of your HD2 has run dry. You can send it back to HTC to get it repaired...but really all it does is run the internal clock, so it's not a huge deal if you can stand resetting the clock when restart your phone.
I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?
omar302 said:
I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?
Click to expand...
Click to collapse
It's not possible to replace it, unless you buy a new phone, because it's not really a battery, it's more like a small chip and its fix integrated on the motherboard. There's no way to change it without buying a new motherboard. I would say, this problem is not big enough to pay so much for it. And maybe you could think about it, if it's necessary to remove the battery. Unless you want to replace the SIM Card you don't have to. SD-Card Slot is not under the battery and for rebooting you have a reset button, and if you have to flash your phone, you have to set up everything so it's not a problem to also set up your time ^.^
Best regards
Is it something that should be covered under warranty?
I baught my HD2 from Clove.co.uk from 1 year back & at the time, warranty used to be 2 years from purchase.
Also, if it is a problem of the Inernal Battery, wouldn't the time reset to ROM date & time? My problem is that the time actualy goes back.
For example, it is 9:15pm & I remove the battery for 1 minute, the phone starts & time is 9:11pm. The more the battery is out, the more the time will be back.
Yeah I have this problem too! *feels less alone*
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
I'm not really into sending it to warranty, my HD2 works great and sometimes they come from warranty worse than they go...
DeadVirus said:
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
Click to expand...
Click to collapse
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.
omar302 said:
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.
Click to expand...
Click to collapse
I'm starting to think that it is related... Another guy complains about something similar after using Android SD...
Yes... Normally it should reset it.
But if you say it's only one year old, there's another hardware problem because such a battery has a lifetime from approximately 2 years.
Maybe - or better they must - will change it under the warranty conditions.
And I don't think that it has something to do with AD SD builds. I also used them for a long time and never encountered something like this.
Hello there.
I have the same problem with my HD2, which runs on a cooked ROM.
What I have noticed is that it actually goes back to the date and time of it's last boot (in fact the time and date SET after the last boot, since it changes and I have to reset it every time, by syncing or manually), regardless of the way the reboot was done. It is a little strange I guess...
Just thought to add this little piece of information.
Oh, and my phone is also quite "young", I have it for less than a year (don't remember the exact date of purchase).
Interesting. I was about to post a similar issue.
I had been using (SD) Android for about 3 weeks continuously. Had a crash and rebooted. I have some problems in Android now following this (corrupt Data.img I think) so booted back into WinMO and found the date was now 2nd Feb 2010 and some random time!
Reset the time and restarted and for some reason it refuses to recognise we are in BST (and I can't see how to change it to GMT +BST)
Same date/time showed when I booted into Android (doesn't seem to be getting the correct details from Network?)
Slightly better after a few reboots so that now everytime I reboot with a battery pull it is setting an older time (but correct date).
I have the same issue using WP7. The time changes backk like 6 hours or so to a completely random time.
And the annoying thing is that the phone seems to think its the right time, and theres no way to 'force' and automatic time update on its self, so i have to disable automatic update and enter the correct time manually!
That's the thing that gets me most - you can move between time zones and the phone gets the local time from the Network operator, but will not "check" if it is wrong by so much....
It must be the internal battery thingumijiggy.
Just confirmed that it only happens after a battery pull.
as long as no one has posted a theory yet, i'm gonna give it a shot!
i think the phone might have TWO regions of memory for storing the current date/time:
1. a "volatile" one (good as long as battery is present)
2. and another "non-volatile" one (survives between battery pulls)
my theory is, WM6.5 ROMs have something hidden in them that allows the date/time to be (periodically?) written to the non-volatile region in case the battery is pulled, following which the system might need to recall the last reliable date/time, as opposed to resetting to an arbitrary default date/time.
the volatile region is good as long as the battery isn't removed. the volatile region is initialized by the non-volatile region and is subsequently kept updated by the RTC (real time clock) chip, whether or not an OS is running (like android or WM or WP7).
but perhaps the little piece of logic that updates the non-volatile region is somehow absent in our android builds?
I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App
Dmxnet said:
I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I also use clocksync in android. But it doesn't solve the problem... :S
I have an HD2(of course)...i have tried many many roms but am stuck with the same issue..I have random freezing issues..i have tried different radios, different classes of sd cards..tried adjusting the vm heap. but to no avail..i am currently using frankenstine rom it seems to be the smoothest but i still have freezing issues..when this occurs i can only pull the battery to reset it and sometimes when i do this i must pull battery 3-5 times to get it past the magloader screen.
i have asked this question in many of the rom threads that i have used but have never gotten a clear and definite fix..can someone enlighten me on how to cure this issue it is really becoming quite frustrating.. thanks in advance to anyone..
When do you have these freezing issues?
When you're watching a web video? Playing a game and listening to music at the same time?
If so, it's cuz you've run out of ram, so your phone will lagg to death. So get a task manager to close those apps.
If not Iunno what your problem is.
Note: Try not to pull out your battery, instead use the soft reset button. If you keep pulling out your battery, you'll mess up the pins.
b14ckd34th said:
I have an HD2(of course)...i have tried many many roms but am stuck with the same issue..I have random freezing issues..i have tried different radios, different classes of sd cards..tried adjusting the vm heap. but to no avail..i am currently using frankenstine rom it seems to be the smoothest but i still have freezing issues..when this occurs i can only pull the battery to reset it and sometimes when i do this i must pull battery 3-5 times to get it past the magloader screen.
i have asked this question in many of the rom threads that i have used but have never gotten a clear and definite fix..can someone enlighten me on how to cure this issue it is really becoming quite frustrating.. thanks in advance to anyone..
Click to expand...
Click to collapse
Have you tried a task29 prior to flashing?
Kailkti said:
When do you have these freezing issues?
When you're watching a web video? Playing a game and listening to music at the same time?
If so, it's cuz you've run out of ram, so your phone will lagg to death. So get a task manager to close those apps.
If not Iunno what your problem is.
Note: Try not to pull out your battery, instead use the soft reset button. If you keep pulling out your battery, you'll mess up the pins.
Click to expand...
Click to collapse
it doesnt seem to be specific on when it freezes..but usually when only using 1 program at a time..i do use task manager.i recently installed words with friends and almost every time i try to open it, it will freeze.
h.nocturna said:
Have you tried a task29 prior to flashing?
Click to expand...
Click to collapse
yes the last time i flashed i used task29..someone once told me it was my radio..which ive tried to downgrade to an earlier version but that didnt help either..
I think it's ram. Reason being, if it is from opening an app, it may be the app is using too much memory for it to handle, eg. mega jump is one
Never tried words before though, but it doesn't sound like something that uses a lot of memory but Iunno.
Do you use desire hd or z builds? Those leave very little ram left.
Kailkti said:
I think it's ram. Reason being, if it is from opening an app, it may be the app is using too much memory for it to handle, eg. mega jump is one
Never tried words before though, but it doesn't sound like something that uses a lot of memory but Iunno.
Do you use desire hd or z builds? Those leave very little ram left.
Click to expand...
Click to collapse
my current rom is a desire build..what build would leave more ram?
i am going to try yet again to reflash this phone and task29 it..
Any non sense build will give you 210+ ram free.
what radio are you using? had some freeze moments when i first started fiddling with android. upgraded my radio to 2.15 and never had a freeze ever since.
Robson said:
what radio are you using? had some freeze moments when i first started fiddling with android. upgraded my radio to 2.15 and never had a freeze ever since.
Click to expand...
Click to collapse
yea i got this radio also...
ok i rewiped, reflashed, task29'd it last night and thought everything was a-ok until a few minutes ago when yet again it froze. i cant wait till tmobile comes out with an htc phone with the same screen size as the hd2 but native android cuz ill be all over it..this crap gets old quick..i cant believe i am the only one with this unfixable issue.
did you also fully refresh you sd card? not much point task29'ing, reinstalling android and starting over if your sd card is still full of cache/droid system folders/EXT/Dalvik and what not.
that being said, if you have had the phone since way back last year, a good proportion of the early ones had freezing problems, regardless of rom.radio, and a quick warranty swap was usually the answer.
samsamuel said:
did you also fully refresh you sd card? not much point task29'ing, reinstalling android and starting over if your sd card is still full of cache/droid system folders/EXT/Dalvik and what not.
that being said, if you have had the phone since way back last year, a good proportion of the early ones had freezing problems, regardless of rom.radio, and a quick warranty swap was usually the answer.
Click to expand...
Click to collapse
i did use the recommended panasonic formatter..and also the cmw format,dalvik and cache wipe...
your other comment kinda makes sense..i have had this since i think February of last year.
so after speaking with tmobile, and actually reflashing windows 6.5 and having it freeze on me twice and today it got stuck in a reboot loop, I am getting a new HD2..i sure hope this one does not freeze as much as my current model..if tmobile would come out with an android phone with this big of a screen i would switch.
For the last several months I noticed that my Androind builds are hunging up, sometimes several times a day, sometimes once a month. While using it might just stuck/freeze and it doesn't react at all until I remove the battery and instert it back.
Recently I decided to browse the forums and read about possible bad sectors on my NAND memory. Somebody mentioned that I should use MTTY and do >task 2a, which actually confirmed that I have a bad block, bud it's only one. The issue is that now being tired of MIUI ICS which hungs quite often, and ICS CM9 builds which are quite stable but at some point are freezing as well, I decided to move to WP7, which earlier was running perfectly on my phone and was able to install those ROMs without any problems. Today I found out that while flashing WP7 ROMs I can't get over Flashing Partition 7, same error with 3 different builds..
Also today I flashed an original WM 6.5 build, which was installed correctly but after 5 minut had an unexpected reboot...
I trying everything I know, Task 29, reinstall HSPL, reinstall MAGLDR, different partitions for CWR, looks like nothing helps..
Does anybody has any ideas or hints?
hey
seems your battery was fault?
I have the same problem
anyway if you find how we can know if there any bad sector tell me..
for me I realize that after charging battery outside it restart
thxs
What I noticed that under normal usage (basic applications, internet browsing, email and listening to music) nothing bad happens, at least on ICS CM9 with HWA.. It freezes when it gets warm. Under heavy usage it might get stuck and while it's still hot I can't really load the system properly, as it will freeze instantly. Once it settles down, in about 15minutes, the system would work like nothing happened. I actually discovered yesterday that I still have 2 months of warranty left, maybe I should just return to the shop. But that means I need to flash back WM 6.5
nand problems or heat problem ?
hi
i have many freeze system on a day when working on my hd2
i tried many systems wm and android nand and sd its always the same problem
i have to remove battery and wait for a minimum of 20 minutes i f i want to boot correctly
can somebody help with a program to remove bad blocks on the nand of hd2 ?
thanks
I dont thing it's possible to fix bad nand memory blocks.
I'm guessing that the only way is to change the main board.
My HD2 works perfectly with stock WM6.5 and android, so i might not have any memory problems, but i have been reading about it and it seems that is not that uncommon.
Regardless, if there is a way to recover/block these bad sectors by some software tool, i would like to know also.
Well, in the end I had to return my phone to the shop today, as it's still under warranty.
I'm curious if there are going to do something with it, fix it, replace, or just return back, as I'm not really sure if they will find any errors, but I hope they will.
Just in case, I flashed the original WM RUU from HTC, and yesterday, while playing with it for a while, it rebooted a couple of times, and was quite hot as well.
Last week-end I've been to Lisbon, were we had 32 degrees at some points, so my phone was freezing every 5 minutes, when I put it in front of the blowing AC fan from the car it could work like that for hours without any issues, but I suppose it should work like that always and in all conditions. This made me understand that the overheating due to a faulty board could be the root cause of all problems. I suppose that even the bad blocks appeared after the overheating issue appeared
I will write here an update when I'll get my phone back from the service.
nickriley said:
Well, in the end I had to return my phone to the shop today, as it's still under warranty.
I'm curious if there are going to do something with it, fix it, replace, or just return back, as I'm not really sure if they will find any errors, but I hope they will.
Just in case, I flashed the original WM RUU from HTC, and yesterday, while playing with it for a while, it rebooted a couple of times, and was quite hot as well.
Last week-end I've been to Lisbon, were we had 32 degrees at some points, so my phone was freezing every 5 minutes, when I put it in front of the blowing AC fan from the car it could work like that for hours without any issues, but I suppose it should work like that always and in all conditions. This made me understand that the overheating due to a faulty board could be the root cause of all problems. I suppose that even the bad blocks appeared after the overheating issue appeared
I will write here an update when I'll get my phone back from the service.
Click to expand...
Click to collapse
What happened in the end? I'm facing the same problem, 5 bad blocks...how do I know where those bad blocks belong? I mean, which partition? Thx