I have not heard of no one posting this problem I am about to post. I hope I can get help with it. The last Standlone android build I used that worked for me was the first one by dan1j3l called LeoFroyo-1.0. I have been trying to test out everyone's android build and for some reason for each build after it creates the data store and I see the boot screen the android screen say's "powering down" and my hd2 automatically shuts off and then i have to turn it back on which then makes it go back to windows mobile. It is annoying to having tried each build and the end result is my device auto- shutting down on me after the boot screen. What should I do to resolve this problem.
This problem reccurs on every single build you use? odd.
and it actually boots into android? past the boot logo/splashscreen?
Hmmm... its most likely not androids fault, make sure youve HSPL'd your device, update your radio ROM to something past 2.08 and throwing on ChuckyROMdroid (as your windows mobile ROM) would perhaps help.
Also, format your SD card to FAT32 BEFORE using any android build, and make sure your battery is charged?
My personal setup is:
HSPL3
ChuckyROMdroid
2.10 radio
ShubCRAFT 1.4c
make sure to run clrcad before HaRet, and that's about as much help as i can give off the top of my head
I have a Tmobile hd 2. It has hard spl on it. Can I go higher than hdspl 1 on my tmobile hd2? I tried the formatting numerous tiimes. I thiught it had to do with something in the startup file. It's just weird how as soon as the boot screen finish loading and I see the android screen interface my device vibrates then it notifies me on the android screen that it is powering down or it just vibrated then power down automatically. It's a real tease.
It is mind-boggling that this single model can cause so many different type combination of problematic behavior, isn't it?
Makes me feel guilty sometimes, that I suffer no serious setbacks running android with my combination so far.
Sent from my HTC Desire using XDA App
Same with me, the so called robot voice, never had it once. And I've been using android from the beginning, also every build have always loaded up for me with no problem.
What battery are you using.. i had the same issue with the official extended battery.. it;'s a known issue if it's that ...
The whole time I have been using the official extended battery. I think when I started using the very first build I had the original battery. I will swap it and see if any there is any change. That is a good point.
There are some workarounds for extended batteries though:
You could ignore the readings from the battery in the kernel
Pro's: No need to swap batteries, able to charge while running android
Cons: Unsafe to charge while running android, inaccurate battery readings if they work at all
http://forum.xda-developers.com/showpost.php?p=7700703&postcount=1
Or you could cover the middle pin of the battery with a little piece of paper or tape
Pro's: Completely safe
Con's: you won't be able to charge under android, you'll have to reinsert the battery and boot windows every time you want to charge, inaccurate battery readings
It worked. Who would have thought the official Htc exteded battery would cause somethng like that to happen. I hope future builds have a way around this problwm. I am suprised nobody posted spmething regarding this. This phone is the best yet but I know having an extended battery is essential to it's longevity use in the day.
extended battery BP-E400 caused the Auto-Shutdown problem
hi guys, I got exactly the same problem you you guys encountering. I accidently swap back the original SLIM battery and the Android Froyo boot smoothly without auto-shutdown. I can somehow confirmed that the auto shutdown is caused by the extended battery BP-E400.
New ROM eliminated Auto-Shutdown problem
try this Android Mdeejay Froyo Sense v2.3 NextSense ROM:
(sorry, the link cannot be posted. Moderator disallowed. But you can google around with the keyword above.)
Works flawless with my extended battery. No more auto-shutdown. YeeHah....
Related
If you're like me, a subpar or incomplete Android 2.2 on HD2 experience was NOT an option. I've been through pretty much every combination, followed everyone's advice and always ended up unhappy for one of several reasons :
1. The ROM I installed was missing features, like the camera or other features that crashed.
2. The dreaded "Sleep of Death"
Not to say anything against any of the ROM chefs, because these guys are hard-working geniuses and they do this for free... for us...
But having said that, I had to keep trying. I'm obsessive compulsive when it comes to my gadgets and once I had a taste of Android on the HD2, I knew I wouldn't be happy until I found that elusive combination that made it work the way I wanted it to.
If you're having trouble making Android work on your HD2, listen up... Because now mine works like a charm and here's how it happened...
1. You absolutely HAVE to get rid of the stock Windows Mobile 6.5 that comes on your HD2. I never found a way around that. Until I flashed a custom ROM, it never worked 100%. To do this you need to flash HSPL to your HD2. This allows the installation of custom ROMs.
2. You have to strip Windows Mobile down to next to nothing. If you plan on using Android 2.2 as your daily operating system, you don't need it anyway. I tried lots of versions, but face it - you won't need WinMo anymore once you get Android working 100%. For this, use Chuckydroid, hands down. It is stripped down to next to nothing - no Sense 2.5, nothing fancy in Windows Mobile. BARE. BONES. Chuckydroid can also be set up to autoboot into Android!
3. After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
4. For my Android ROM, I chose Mdj revolution 1.5, and updated to the S1 Linux kernel. It was one of few builds that had all features working as they should. The S1 kernel patches a lot of issues that might arise with the MDJ build.
5. Lastly, I noticed I didn't have 3G signal after all this and discovered that at some point my APN information (which tells the phone how to connect to data services) had been wiped out. I am a TMoUSA customer, so I found the information for the USA servers and added it manually to the phone. (System/Wireless & Networks/Mobile Networks/Access Point Names)
I know this isn't every piece of information you need, but if you read each point and investigate on your own, you'll find there's a wealth of information out there to guide you through each step, but to clarify :
1. Flash HSPL (I used HSPL 3, but follow the directions when you find it)
2. Install Chuckydroid (No other custom ROM worked and I tried them all)
3. Flash Radio 2.15
4. MDJ Revolution 1.5 w/ S1 kernel (Most stable and complete I could find)
5. Manually configure APN
Again I'll close with the fact that I have a fully-working Android 2.2 HD2 device. All features, all functions, no errors, no robot voice, no SOD, no gremlins... It just works. Good luck! If you have any additions to this plan, let me know! I'd like to know that I was using the newest 100% WORKING(!!!) Android built with all the best features.
I'd also like to add that, given my luck, now that it's taken me over a week to get Android 2.2 working flawlessly on my HD2, in the next day or so we'll see one of four things :
1. A flashable Android 2.2 ROM that completely replaces WinMo as the Operating system
2. A flashable Android 2.3 (3.0) Gingerbread ROM
3. A flashable Windows Phone 7 ROM
4. The return of Christ
Zaron3d said:
4. The return of Christ
Click to expand...
Click to collapse
That's it That's all...
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
noris08 said:
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
Click to expand...
Click to collapse
Well I tried a lot of these "quick shortcuts" to make things work and nothing did. Believe me, I've been down every road to make this happen...
and yeah I guess I put this in the wrong section now that I look at it. Sorry!
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
vysus said:
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
Click to expand...
Click to collapse
try this combo:
- wm - energy nov 8 21684 cht 1.8.5
- radio - 2.15
- android - mdeejay revolution 1.5
- kernel - mdeejay s2
i have only 6% battery drop over 9 hours of standby, all data transfers closed and gsm only, not 3g
all things i tested works flawless
i think you missed the most important thing...
--> hard format your SD card before trying
Camillo
Format or not the SD makes non differences, I have huge battery drain in every situation.
I've had several issues running mdeejay builds, so I prefer FroyoStone 3.2 by Darkstone. I've never tried Chucky ROMs before, so I'd like to flash the brand new one
@camillo
no i didn't forget format card. i just don't do that, formatted first time and never again since then
@vysus
do whatever you want. i just suggested a combo that works very well for me
noris08 said:
@vysus
do whatever you want. i just suggested a combo that works very well for me
Click to expand...
Click to collapse
You're welcome
Unfortunately, NRG ROMs and PPP builds are not suitables for italian providers: using the first ones I had battery drain, trying the seconds I have had continuos data drops, missed calls & SMS, HUGE and nearly incredible battery drain.
I still would like to know which version of Chucky fits better with android, it's the last chance, after that I prefer to let go...
i think an correctly configured setcpu is the most important fact for battery life.
my combo:
winmob:http://forum.xda-developers.com/showthread.php?t=793814
radio: 2.12.50
Droid: hyperdroid 1.7 (nexusHD2 since yesterday cuz of new harastin kernel)
sdcard: transcent class6 sdhc
battery drain without setcpu (overnight, 8h): 40%
with : 3%
TBH I have found no difference between a fully featured winmo rom (laurentius V4 or Energy nov 8th) versus Ozdroid which was stripped down.
I have found that of course the kernel makes the most difference - currently on S2 and it seems rather peachy.
As for battery drain I have found that it is fine even without setcpu on this kernel - however - once in a while, especially at the end of the day, the battery drains super fast - I believe there is an errant process or data transfer that messes it up (perhaps whatsapp?).
I stillhowever have PPP disconnects regardless.
I haven't had one since I disabled the stock widget though.
i only have ppp disconnects if i kill all my tasks. if not, it works fine
I start off my android adventure few weeks back and now I found my treasure and have stop searching.
Here is my combination,
WM ROM: vbn clarity
Android rom: mdj froyo revolution 1.5
Kernel: mdj s2
I have tried some other build and the battery life can only last me half a day but with this combination after more than 12 hours of usage, I still have 40%. (Usage: check email every 30 mins, check xda app every 30mins, moderate web surfing, a few calls)
So for those still struggling to find the combination, you might want to try my combination. Enjoy
Sent from my HTC HD2 using XDA App
A different spin on Android Issues
I too was having issues with SOD, random freezing/rebooting, robot voice etc and basically gave up on having a usable version of Android working on my device.
But then I had a slight lapse in judgement and came up with another hair-brained idea... I decided to attempt to get T-Mobile to let me just switch to a different phone like the Galaxy S / G2 / or MyTouch 4G.
So I task 29'ed the phone, flashed back to the OEM rom, then removed HSPL while not at work... Over the next 2 hours I began to notice that I was having issues even on the default OEM rom.
I got curious, removed the SD card, re-installed HSPL, re-downloaded the T-Mobile Official Rom from their website, and task 29'ed the phone again, reinstalled the OEM rom, and removed HSPL again just to make sure that I hadn't just got a corrupt download or something.
Within 20 mins of loading the T-Mobile rom back on the phone, my phone randomly rebooted itself. Later while I was in the middle of a phone call the phone just made a weird buzzing sound and froze. The buzzing sound would not go away until I removed the battery and restarted. I was also having many of the issues I was seeing in all of the Android builds that I had tried like the screen taking forever to come back on after being locked, the screen being non-responsive etc...
I had attributed all of these problems to the Android roms I was using and Android not being 100% and stil too buggy for the HD2 when it actually was a problem with the device itself.
I went to T-Mobile last night and they are sending me a new phone (probably a refurb) by the beginning of next week. I'm hoping that the new device will clear up all of the issues.
Just thought I would share my experiences, maybe some of you that are having issues with the Android builds could actually just have a bad device like I did...
Zaron3d said:
After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
Click to expand...
Click to collapse
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
vysus said:
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
Click to expand...
Click to collapse
Uhhh... what? It depends on what you have running I guess. Mine seems to be running fine. Off the charger for about 3 hours and only down to 90%.
Since I've just had my HD2's screen replaced, I'm still on the stock ROM from when I got the phone back from HTC. I just popped my SD card back in and off I went. The stock ROM works perfectly with Android for me. The radio is the one they installed (see sig).
I'm not sure that WM ROM has that much effect tbh. With the ppp wrapper patched and running the S2 kernal from MDJ, I managed a 320 mile trip with Google Navigate running the entire time. I never had a single data drop or problem with the phone. I was connected to my car stereo via bluetooth too.
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
matthewharmon102 said:
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
Click to expand...
Click to collapse
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
eenbox said:
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
Click to expand...
Click to collapse
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
matthewharmon102 said:
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
Click to expand...
Click to collapse
What I did was reformatting under multimedia card reader - I do not think it matters but that's what I did.
I did find some registry tweaks that manages sd card power a while ago and tried them under stock rom and radio - it did not work but I never bothered to go back since my battery is not really getting drained - lasts enough for me.
I only installed BSB Tweaks and disabled EVERYTHING and left only power-saving ON. I have no clue whether this helps at all or not but just did it as a preventive measure ... also, make sure auto-lock is DISABLED under Windows. That was one of the old issues to get un-wake-able screens ... however, so far I have not really had any problems.
Keep in mind: if you want to install many apps that you would like to test - do not do it in massive installations one after another. Some apps are known to screw up battery life and stand-by mAs. Therefore, install couple at the time - after reboot if you get low mA - then app is not draining the battery.
So far I have experienced Extended power widget to drain the battery a lot and also any type of news browsers like e-buzz, pulse, etc - they seem to constantly pull data and remain active. However, they may work for you if you have data disabled for the most part (which is probably not the case) - forgot to mention mine is on 3/3.5G at all times.
- Background Data is checked (ON);
- Auto Sync is unchecked (OFF);
- Brightness disabled under very strong light (110 lumens of my flashlight hihihi) and set on 35-40% I think - somewhere around there.
- I have three home-screens and do not feel I need more
- Weather widget, current widget and google search widget - I do not have any clocks for simple reason - when the phone is locked I can easily see the time by clicking the hardware buttons - so what's the point of the background one ...
If I remember any other tips and tricks I'll let you know.
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've switched from windows to android for my htc hd2 and I've been experiencing a lot of freezing/hanging issues. I had no choice but to pull out my battery to restart my phone a lot of times.
Does anyone encounter the same problem after they change to android? Or is it like this? It's like, when i play a game, it'll hang sometimes. playing music halfway, it'd hang. or even using GPRS and it'll hang. =.= help!
btw, i'm using the SD builds. It doesn't really matter which sd builds cuz i tried quite a few and I'm still getting a lot of hangs randomly here and there.
evilwz said:
I've switched from windows to android for my htc hd2 and I've been experiencing a lot of freezing/hanging issues. I had no choice but to pull out my battery to restart my phone a lot of times.
Does anyone encounter the same problem after they change to android? Or is it like this? It's like, when i play a game, it'll hang sometimes. playing music halfway, it'd hang. or even using GPRS and it'll hang. =.= help!
btw, i'm using the SD builds. It doesn't really matter which sd builds cuz i tried quite a few and I'm still getting a lot of hangs randomly here and there.
Click to expand...
Click to collapse
Care to tell us more ?
Radio?
WM ROM ?
Android ROM version ?
Hi, I've been experiencing the same problems. I'm booting android through WM 6.5 through the SD card method. I've tried the AmericanAndroid (http://forum.xda-developers.com/showthread.php?t=957652), a HTC sense ROM (http://forum.xda-developers.com/showthread.php?t=954030), a MIUI ROM (http://forum.xda-developers.com/showthread.php?t=1058809) and Darkstone's superRAM froyo. They all tend to crash randomly after a while, and there's no way to solve the problem but pull out the battery... One reason suggested on the forums was that hot weather tends to make the HD2 overheat and crash, which makes some sense because I live in Singapore (that's tropical, btw). But my WM6.5 doesn't crash nearly as often...
O another thing: whenever I boot into android through SD, I tend to get high battery drains of about 60mA. One solution I've found was to shut down the phone, then hold the volume down button while booting in WM6.5. This brings me into a multi coloured screen (is it called the bootloader or something?), and I pull out the battery. After which I boot into WM6.5 normally and boot android from the SD card. That normally brings down the battery drain to about 10mA, but I'm not sure how this works/why it works that way/what side effects this may have... Besides this I follow all the standard procedures, so I'm not sure why android crashes on me so often...
Flash NAND Android ROM and all your troubles will disappear.
Please ensure rom you flashed is the appropriate one. Check ur devicd model, choose rom for ur device, read faq/explanation from chef who built thd rom. Check recovery partition required for your choosed rom. Yesss flash nand rom and flash into ur nand. If u prefer sd rom ensure ur sdcard is in good condition
Sent from my HTC Incredible S using XDA App
likewei92 said:
Hi, I've been experiencing the same problems. I'm booting android through WM 6.5 through the SD card method. I've tried the AmericanAndroid (http://forum.xda-developers.com/showthread.php?t=957652), a HTC sense ROM (http://forum.xda-developers.com/showthread.php?t=954030), a MIUI ROM (http://forum.xda-developers.com/showthread.php?t=1058809) and Darkstone's superRAM froyo. They all tend to crash randomly after a while, and there's no way to solve the problem but pull out the battery... One reason suggested on the forums was that hot weather tends to make the HD2 overheat and crash, which makes some sense because I live in Singapore (that's tropical, btw). But my WM6.5 doesn't crash nearly as often...
O another thing: whenever I boot into android through SD, I tend to get high battery drains of about 60mA. One solution I've found was to shut down the phone, then hold the volume down button while booting in WM6.5. This brings me into a multi coloured screen (is it called the bootloader or something?), and I pull out the battery. After which I boot into WM6.5 normally and boot android from the SD card. That normally brings down the battery drain to about 10mA, but I'm not sure how this works/why it works that way/what side effects this may have... Besides this I follow all the standard procedures, so I'm not sure why android crashes on me so often...
Click to expand...
Click to collapse
hi,
1. try booting into WM6.5 stock rom, w/o any modifications. you should be able to download through the htc website
2. try using WM6.5 a while, see if it hangs/restarts itself. there shouldn't be the case if you're using stock rom.
3. if you still face the restarting/freezing problems even using stock WM6.5 rom. send your phone for servicing.
As my warranty was still valid, i sent my phone for servicing and they changed the whole motherboard of my HD2. Now my phone is running smoothly on both WM6.5 and Android.
The service that HTC offers in Singapore is quite good. You can call them to come to your house and collect the phone personally. If you need, you can ask for a loan phone. They'll repair and return your phone to your doorstep in about a week's time. I'm pretty happy with their efficient service Tell me which company will come and collect your phone at your doorstep and send it back to you when it's all good. Thumbs up all the way for them!
Hope this helps.
Thanks for the replies. I switched to NAND with hyperdroid by pongster, but the crashing persisted for a while. It seems that the connection between the SD card and the phone is the problem. There was once that I got ~60mA of battery drain, then I pulled out the SD card and the drain went down to ~10mA (I was running on NAND of course). I then went on to try a difference SD card (a 4GB sandisk), and the the HD2 stopped crashing. It has also never crashed with the SD card removed. Moral of the story: a very stable SD connection is essential if you want to use SD builds...
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83