Database Users

[Q] HTC HD2 running android.

So, i have a htc hd2 running on android and i love it.
However, when lock my phone using the end call button or something.
I would look back at it after a while and the screen will stay black.
I try pressing the keys and nothing happens.
When i call the phone, it rings but i can't use the touch screen or see it.
It happens quite frequently. The android i have is darkstone froyo.
So it works but pretty frequently, the screen would go off and stay black.
What do i do?

Unfortunately threads like this are completely pointless unless you were to elaborate on which version of HD2 you have, which RADIO you have, which build you have, the current zImage, which Windows ROM you have.....

imtimduh said:
So, i have a htc hd2 running on android and i love it.
However, when lock my phone using the end call button or something.
I would look back at it after a while and the screen will stay black.
I try pressing the keys and nothing happens.
When i call the phone, it rings but i can't use the touch screen or see it.
It happens quite frequently. The android i have is darkstone froyo.
So it works but pretty frequently, the screen would go off and stay black.
What do i do?
Click to expand...
Click to collapse
I wanted to see if Android would work on my HD2 before flashing a rom and changing my phone but I have this same problem as well.
I boot up Android and eventually I put the phone to sleep with the end call button and I can see the screen goes black but I can tell the backlight is still on. Then I try to unlock my phone and it never wakes up no matter which buttons I press. I eventually have to take out the battery to reset the phone back to windows mobile
Then again... I am also just running the U.S. T-mobile version with stock windows mobile 6.5 out of the box with no flashed rom with radio version 2.10.50.26
I will be looking over the sticky thread and doing the full conversion today but if anyone knows why it does this I would like to know so it doesnt happen even after I do it the correct way.

ooops. accidently replied by accident.

Same problem here.. I'm using chuckydroidrom, shubcraft 1.5 , radio 2.10.50.26 , have tried almost all the builds, radio versions, but result the same... would really like to know if anyone else has the same problem.
Sent from my HTC HD2 using XDA App

Same problem here. I tried on two hd2 phones. Everything is works fine but i cant end a call because the phone freezing. I'm using 2.15.50.14 radio and magldr113.

I gave up on the sd androids and went with a nand build, much more stable much better battery! Research builds READ THE POST and find one folks have the least trouble with.
I am currently using Motoman234's Moto-Mytouch4G V3.3 based on Iced Glacier by teamsilence. Shear brilliance in my opinion! i have tmous as well this nand for me is flawless. Everything works great and my battery will easily last the day. I had been using Darkstone SuperRAM FroYo v1.5 but the battery drain was murder. Great build beautiful and feature packed but not usable for me due to enormous battery drain. Ya installing them takes more (install hspl then magldr, then clockwork mod THEN the nand) but well worth the effort plus once all that is done you can change builds easily.

so far the core Droid series is great the v1.4 is fast and stable!! i can get up to 2500 on quadrant scores love it so much

pburstrom said:
I gave up on the sd androids and went with a nand build, much more stable much better battery! Research builds READ THE POST and find one folks have the least trouble with.
I am currently using Motoman234's Moto-Mytouch4G V3.3 based on Iced Glacier by teamsilence. Shear brilliance in my opinion! i have tmous as well this nand for me is flawless. Everything works great and my battery will easily last the day. I had been using Darkstone SuperRAM FroYo v1.5 but the battery drain was murder. Great build beautiful and feature packed but not usable for me due to enormous battery drain. Ya installing them takes more (install hspl then magldr, then clockwork mod THEN the nand) but well worth the effort plus once all that is done you can change builds easily.
Click to expand...
Click to collapse
Actually, if you know what you're doing and make sure there's not anything unnecessarily draining your battery, SD builds and NAND builds have pretty much the same battery life. You may be able to get slightly better battery with nand, but not a noticeable amount. I get 3-6ma battery drain on standby with most SD builds I've used. Performance isn't much different with SD builds, either. Main pros of using NAND is you can use clockwork recovery and can change SD cards while using android. If you're not going to use winmo or wp7, you might as well use NAND android, but if you still use winmo or wp7, it's probably not worth losing those for the small bonuses you get with NAND.
I used NAND android for a month when it was first released, but I'm back to SD builds because I have WP7 on my NAND... and I can notice no difference in the performance and battery life.

I am using a SD build and have no problems with it. As long as you're smart with it you will be fine.
To answer the op's question, I would upgrade your radio first. It's too low of a version.
Second, what rom are you using?

naturesbless said:
I am using a SD build and have no problems with it. As long as you're smart with it you will be fine.
To answer the op's question, I would upgrade your radio first. It's too low of a version.
Second, what rom are you using?
Click to expand...
Click to collapse
Your do realize this thread is about 6 months old

Upgrade your radio its solving your problem.. just try that trust me it works ...
HD2 TMOUSA
rom : TyphoonCyanogenMod 7
radio: 2.15.50.14
LINTEAM LEADER(gpu dev)

It was near the top of my unread threads page? Somebody replied to it, not me and I found that nobody answered the op and were instead discussing the pro/cons of NAND vs SD.
Sorry that I didn't check the date of the thread before posting.

zarathustrax said:
Actually, if you know what you're doing and make sure there's not anything unnecessarily draining your battery, SD builds and NAND builds have pretty much the same battery life. You may be able to get slightly better battery with nand, but not a noticeable amount. I get 3-6ma battery drain on standby with most SD builds I've used. Performance isn't much different with SD builds, either. Main pros of using NAND is you can use clockwork recovery and can change SD cards while using android. If you're not going to use winmo or wp7, you might as well use NAND android, but if you still use winmo or wp7, it's probably not worth losing those for the small bonuses you get with NAND.
I used NAND android for a month when it was first released, but I'm back to SD builds because I have WP7 on my NAND... and I can notice no difference in the performance and battery life.
Click to expand...
Click to collapse
While I agree SD is better if you want to keep windows I disagree strongly on the battery life, at least on the SD builds I used. I would shut down bg data, wifi, bluetooth, location, and data when it was not in use but still had horrible battery drain (50 to 60 ma sleeping) and could never make a full day with out a charge. Now wifi and bg data stays on always I seldom NEED a recharge most days I can get nearly 2 days out of my battery. I tried different "battery savers" to no avail, applied every patch the developers suggested and researched extensively.
IMO "Know what you're doing" is a rather obnoxious statement.

In my experience, it seems to depend on the build. It may seem trite, but there are tradeoffs in all the available builds and different people do fine on those that suck juice, because certain features they want are there. I like the SD versions because sometimes I need WinMo, and it's easy to move between them.

[Q] After a day with Android on HD2

I'm half way through my 2nd day using Android on my HD2 and this thread is for me to say what issues i've found. Not to complain, just because most of them may have fixes or other people may have the same issues. These ROMS haven't long been out and i'm sure the developers here will fix many issues.
ROM: NRGZ28 Energy ROM
Radio: .12
Android Build: Desire v5
Battery Life:
Compared with WinMo, Android appears to be less optomised on battery. I put the phone on a full charge at 7pm last night, at this time(10:25am) with very little use, 1 3 minute call and a quick check on Facebook) the battery only has 50% left just over
Unresponsive Screen:
Occasionally the screen will stop responding, however pressing a hardware button usually clears the problem up
Photo Uploading:
I took 2 photos yesturday and went to upload them to Facebook, however the progress bar stays at 0% on the notification bar and no way to remove it
No Mic/Audio:
I've made another thread for this and I found the problem, with my Windows Mobile ROM it doesn't automatically load CLRAD.EXE before HaRAT.EXE, so when starting up the phone, i have to take out SD Card, use File Explorer to start CLRAD.exe, put SD Card in then launch HaRAT.exe
I've heard changing to the Titanium WinMo ROM fixes many issues compared to Energy so I may try that tonight

your rom should be fine to run android.
desire v5 is not the best choice, cause its one of the first builds.
you should take an new build before doing anything else...
if you like sense, give mattc 1.6 a try. if you not like sense take a look at darkstones newest froyostone.
there have been many many kernel updates since desire v5 was released. you will notice a huge difference in speed and response...

Bimme said:
your rom should be fine to run android.
desire v5 is not the best choice, cause its one of the first builds.
you should take an new build before doing anything else...
if you like sense, give mattc 1.6 a try. if you not like sense take a look at darkstones newest froyostone.
there have been many many kernel updates since desire v5 was released. you will notice a huge difference in speed and response...
Click to expand...
Click to collapse
Thanks for the tip, I may try Mattc 1.6, is that 1.6 the version of the ROM or is it Android 1.6?

Actually wait a bit on mattc 1.6. It currently has issues. mattc 1.5b is my fulltime build right now. I haven't used WinMo in 2 weeks. As a matter of fact, I'm going to load on a light version of WinMo, like Chucky's. Why have a bloated WinMo when you're not using it?

geon106 said:
Thanks for the tip, I may try Mattc 1.6, is that 1.6 the version of the ROM or is it Android 1.6?
Click to expand...
Click to collapse
I said to you to upgrade as desire is an older build. In regards of clfcad it should be on your SD card in the android folder along with haret so why is it stored elsewhere? Plus you always have to click clrcad before running haret unless you use an android launcher like mskips which does this automatically.

So OP other than your experiences with highly known problems. What was your experince with android overall.
Did you like it? Did you use it to is full potential? Did you try out the new voice search? What did you think of qik? or any other note worthy apps?
I know you are probably already aware but I just wanted to say
these things.
The battery life improves with use of setcpu. Considering the phone was never designed to run android I am ok with it.
Unresponsive screen is solved right now by disabling screen rotation.
there is also a slight delay built in I believe.
Uploads were a big problem untill the recent ppp fix.
You shouldnt ever have a problem with sound running aslong
as clrad.exe is being properly ran.
I wanted to address these because I believe android on the hd2 needs a fair chance. If we dont take into account these minor flaws we wont see the greatness.

11calcal said:
I said to you to upgrade as desire is an older build. In regards of clfcad it should be on your SD card in the android folder along with haret so why is it stored elsewhere? Plus you always have to click clrcad before running haret unless you use an android launcher like mskips which does this automatically.
Click to expand...
Click to collapse
Those files are in the Android folder on the SD card, but I thought the WinMo ROM as it has a button built in to launch Android would be scripted to run CLFCAD.exe and HaRAT.exe automatically, wrongly assumed on my part though.
hmm, mskips you say? May give that a go.
Yeah i've been told by a few people to upgrade the Android rom i have, the reason I started with this one is because i figured the HTC Desire is a similar phone to HD2. I'll try in a bit a new WinMo ROM and Android ROM but with the same radio

hazard99 said:
So OP other than your experiences with highly known problems. What was your experince with android overall.
Did you like it? Did you use it to is full potential? Did you try out the new voice search? What did you think of qik? or any other note worthy apps?
I know you are probably already aware but I just wanted to say
these things.
The battery life improves with use of setcpu. Considering the phone was never designed to run android I am ok with it.
Unresponsive screen is solved right now by disabling screen rotation.
there is also a slight delay built in I believe.
Uploads were a big problem untill the recent ppp fix.
You shouldnt ever have a problem with sound running aslong
as clrad.exe is being properly ran.
I wanted to address these because I believe android on the hd2 needs a fair chance. If we dont take into account these minor flaws we wont see the greatness.
Click to expand...
Click to collapse
Don't get me wrong this isn't me complaining about it. I knew there would be "niggling" issues of course.
Well personally, I love it. I want to use it as my main OS. It is suprisingly stable, it looks good, it runs reasonably well(i.e above issues). I love the Android Marketplace, i've given Layar a go(which runs well and is fun) i enjoy Latitude and using it with Google Buzz.
I am hugely grateful for the work people are putting into these ROMs, its fantastic and as they get improved and issues get fixed well, I can imagine great things

sorry I didnt mean to imply anything. I just wanted to see what you enjoyed. I am glad to see you are enjoying it.
I knew these guys were smart so i bought it even before I knew about the project.
Dreams really do come true lol.

hazard99 said:
sorry I didnt mean to imply anything. I just wanted to see what you enjoyed. I am glad to see you are enjoying it.
I knew these guys were smart so i bought it even before I knew about the project.
Dreams really do come true lol.
Click to expand...
Click to collapse
I agree, I will be keeping a close eye on the ROMs and as they get improved more and more, our experiences with Android will only get better. Right now i'm experimenting with different builds to see which one suites me best

[Q] Is there a build with no dropped 3G, no SOD and no touchscreen pauses?

Is there a build with no dropped 3G, no SOD and no touchscreen pauses?
I absolutely love Mattc's build and all the effort everyone has put into them, especially the kernel devs. I think it's incredible these work as well as they do and I'm using the mattc Evo Leo version as my every day OS....
I ask this question because mattc Leo + Froyo with Sense seems to have the screen pause and occasional SOD. I switched to the new mattc's EvoLeo which fixed the pause and SOD completely, but now my 3G dropps randomely. Usually when I'm using it heavily, it drops once every 15 minutes or so, but I've gone hourse without a drop as well..... Anyhow, I was just hoping there was a build, that fixes these or a tweak or kernal replacement that fixes these...
Also, The Evo Leo build is so stable that I don't see any reason why you would bother booting from NAND. Boot once from Windows Mobile and stay in Android as long as you want.... Its nice to, at least, have the option to boot WM... Maybe there are other reasons to put Android on the NAND?
Thanks,
Kevlar The Great

KevlarTheGreat said:
Is there a build with no dropped 3G, no SOD and no touchscreen pauses?
I absolutely love Mattc's build and all the effort everyone has put into them, especially the kernel devs. I think it's incredible these work as well as they do and I'm using the mattc Evo Leo version as my every day OS....
I ask this question because mattc Leo + Froyo with Sense seems to have the screen pause and occasional SOD. I switched to the new mattc's EvoLeo which fixed the pause and SOD completely, but now my 3G dropps randomely. Usually when I'm using it heavily, it drops once every 15 minutes or so, but I've gone hourse without a drop as well..... Anyhow, I was just hoping there was a build, that fixes these or a tweak or kernal replacement that fixes these...
Also, The Evo Leo build is so stable that I don't see any reason why you would bother booting from NAND. Boot once from Windows Mobile and stay in Android as long as you want.... Its nice to, at least, have the option to boot WM... Maybe there are other reasons to put Android on the NAND?
Thanks,
Kevlar The Great
Click to expand...
Click to collapse
lol not yet so far

yes there is more infor here

I've been using the following setup and it works very well for daily use (no SOD etc)
mdeejay Froyo Sense v. 2.2 with kernel from hastarin, v4.1
radio 2.14.50.04
winrom artemis 34.5 (not that i think it matters)
hspl3
Just be careful how you use SetCPU/ATK Froyo and other applications that interfere with the OS since this isn't a device with Android at it's core.
Oh, as for SetCPU, I set 384MHz min/max, userspace, while screen is off and I get ~5-6 mAh consumption while screen is in standby with WiFi off and about 60mAh with it on. I know it's not the lowest freq but it should be a good trade-off since my phone wakes up very fast.

OMG there totally is! I can't believe you haven't found that post! I also can't believe all of these other devs haven't found that post and copied the solution too! Lucky me that I found this next to the pot of gold at the end of this rainbow sitting next too Santa Claus and the Easter Bunny.

I have one!
Mdeejay 3.1 Desire HD
Nothing to say....smooth and fast....no drops on 3G or everything else.
the only issue is the camera.

With everyone using a different WinMo ROM, radio, hspl (maybe), and even some hardware differences, it's impossible to say.
I just played with different builds until I found one that works for me. Currently running HyperDroid 1.6

Phiredrop Skinny EVO has been perfect!
I used the beta version for days with no problems and now have the 1.1 version and it is perfecto!

pack21 said:
I have one!
Mdeejay 3.1 Desire HD
Nothing to say....smooth and fast....no drops on 3G or everything else.
the only issue is the camera.
Click to expand...
Click to collapse
u got a link to this build?

i use hyperdroid 1.5 stockified is almost perfect, i have minimal issues. the only major for me is that it uses rmnet instead of ppp. ppplease?

RmNet builds work for practically everybody with no dropped connections. Touchscreen pauses have not been completely eliminated yet, but they can be almost completely eliminated in regular use by either disabling the G-Sensor, or disabling home-screen orientation through ADWLauncher or LauncherPro.
PPP builds still drop connections for many people. A common workaround is to enable/disable airplane mode to soft-reset the connection.
EVO-based kernels use PPP. Nexus-One kernels use RmNet. Therefore, to avoid dropped mobile connections, use any Nexus-One based build.
Since you like MattC's builds, the last build of his that was RmNet based was 1.7. If you don't have a copy of it saved, you can download it here: (RapidShare link) http://rapidshare.com/files/416256755/mattcfroyosense1.7rmnet.zip
Personally, I am using HyperDroid 1.6 This build uses RmNet and is quite reliable. I've used it with Radios 2.12 and 2.14, with the VBN WM Rom, and have not experienced any SoDs, dropped 3g, or touchscreen freezes. Links are still on the front page of this forum.

Bangster v1.4 (self-modified)
#hastarin r6 kernel
#vbndroid winmo rom
#2.14 radio with hspl3
#stock 16g sdcard formatted with 32k cluster size
RESULT
#only 3mA batery usage during standby with wifi off!!
#great data speed and no dropped connection using PPP.
#no SOD, robot voice touchscreen freezes whatsoever.
#no issues with bluetooth
#802.11n Wifi with hastarin r6 kernel
#great graphic performance with darkstones graphic tweaks(included in hastarin kernel)
Hope this helps.
Sent from my HTC HD2 using XDA App

This is my setup.
WM Rom: Elegancia GTX
http://forum.xda-developers.com/showthread.php?t=654218
Android Build:mccm v1.5
http://forum.xda-developers.com/showthread.php?t=773790
Using Radio 2.12
Been using for more than a week and no SOD, 3G works fine.
I did a lot of trial & error with different WM Roms and Android builds and this has been the most stable choice for me.

You may wanna play with this one too:
# [BUILD][29.09.2010][FroyoStone Sense - V3.1][Kernel: darkstone]
darkstone's in the same league as mattc so this may turn out to be one of the perfect ones hopefully!.
Installed it over mattc leoevo 1.1 (due to data issues) and been running it with no issues so far..btw i have only tested data both wifi and cellular n some other stuff therefore the rest will still have to be checked out.

I second the phiremod build, definitely is a daily rom for me. I used to get SODs from every rom until I started using his.

I have very good usage with MIUI beta4 and mdeejay 1.5evo . These 2 roms are close to perfect , no screen freeze, no drop 3G, no touch screen issues, no sod
I am on stock rom 1.66 asian rom and radio 2.12
Of these 2 miui is best and fantastic fast very stable . Only issue is the ipone like ui. It's additional features is way ahead of htc desire hd new sense which I tested too.

Change Radio and HSPL
atifhassan said:
You may wanna play with this one too:
# [BUILD][29.09.2010][FroyoStone Sense - V3.1][Kernel: darkstone]
darkstone's in the same league as mattc so this may turn out to be one of the perfect ones hopefully!.
Installed it over mattc leoevo 1.1 (due to data issues) and been running it with no issues so far..btw i have only tested data both wifi and cellular n some other stuff therefore the rest will still have to be checked out.
Click to expand...
Click to collapse
I've been using this build too. It's BEAUTIFULLY smooth and works just fine.
Also, I believe (someone please correct me if I'm wrong) the SOD's have more to do with radio and hspl than anything. I was using a 2.08 radio and hspl 2 and I was getting SOD all of the time. As soon as I upgraded to 2.12 radio (and now 2.14) as well as hspl3 I have not had SOD once. During this process I was using the same Android and WM builds, so it seems it was the radio and hspl.

Im new to all this and still experimenting.
So far Hyperdroid 1.6 is doing the best job for me. I have had a few issues with 3G here and there, And getting this Touchscreen freeze problem a couple of times a day..
I am running
Latest Chuckyrom
Radio 2.14
8gb Sandisk Class 6 SDcard formatted 32kb cluster size
I am wondering how much influence windows mobile rom has on these android builds? I am happy with hyperdroid 1.6, without going rom flash crazy if someone could recommend a base windows mobile that plays well with this I will give it a whirl.

pack21 said:
I have one!
Mdeejay 3.1 Desire HD
Nothing to say....smooth and fast....no drops on 3G or everything else.
the only issue is the camera.
Click to expand...
Click to collapse
Nismo300zx said:
u got a link to this build?
Click to expand...
Click to collapse
Yeah, I'm with pack21 on this build - it's been great on my combo (see sig'), but I do however suffer from occasional data drops. It's great for daily use otherwise!
As for a link, that's a bit tricky seeing as the thread containing it was 'lost' when xda suffered it's server issues the other day. It was only up for about 24 hours, and I've not seen a link for it reproduced since. It would be worth your while searching for it though - I think you'll find it would be worth the hassle!

Thanks everyone (except maybe robkoehler) for your very helpful feedback. I was wondering if maybe some people had gotten a version of mattc to work without screen pauses or data drops, but it sounds that hasn't really happened.
I hope I can find Mdeejay 3.1 Desire HD because it sounds like thats a good one to try....
I've been using HSPL2, do you guys really think I'd have better luck with HSPL3? I just hate to mess with HSPL because ... it seems like the most risky thing we have to do to our phones...
I really appreciate the advice and I'll continue to monitor this thread for any more feedback.

[ALL BUILDS] Having problems with a "black SOD"?

I noticed that a LOT of people on these Android Development threads are complaining of a "black SOD" they receive even AFTER reformatting their SD cards and reinstalling everything properly. Basically this is an SOD except the screen backlight is on but there aren't any icons.. Similar to the back-lit screen you see before the unlock screen appears, except the phone isn't locked (sometimes, it is).
I noticed this problem when I first started using Android, and let me tell you, it was quite frustrating!! I tried everything. All different WinMo ROMS, multiple Android ROMs, radios; you name it, and I probably tried it. Until one day...
... I finally came upon the solution: the SD card!! For some reason, I wanted to try out a different SD card other than the stock 16GB one. I don't exactly remember the thread or the URL, but I do recall reading a bit of info that helped lead to this conclusion. For me, I switched to the 2GB from my BlackBerry and haven't had one single "black SOD" since that change.
I am posting this thread in the development forum because I constantly see people with the same frustration.. Which in turn leads to them blaming the build itself. I urge the dev's to post a note in their threads with this solution, as it will help diminish unnecessary bickering/bashing/posting that these dev's must deal with regarding this issue. Also, I am posting it here because I tried MULTIPLE 'Droid builds and this was the only solution that worked for me.
Let me know if this helps anybody with their dreaded black SOD!! And a big thank you to all the dev's for their extraordinary hard work and dedication in bringing the amazing Android OS to our beloved HD2's.

maff1989 said:
I noticed that a LOT of people on these Android Development threads are complaining of a "black SOD" they receive even AFTER reformatting their SD cards and reinstalling everything properly. Basically this is an SOD except the screen backlight is on but there aren't any icons.. Similar to the back-lit screen you see before the unlock screen appears, except the phone isn't locked (sometimes, it is).
I noticed this problem when I first started using Android, and let me tell you, it was quite frustrating!! I tried everything. All different WinMo ROMS, multiple Android ROMs, radios; you name it, and I probably tried it. Until one day...
... I finally came upon the solution: the SD card!! For some reason, I wanted to try out a different SD card other than the stock 16GB one. I don't exactly remember the thread or the URL, but I do recall reading a bit of info that helped lead to this conclusion. For me, I switched to the 2GB from my BlackBerry and haven't had one single "black SOD" since that change.
I am posting this thread in the development forum because I constantly see people with the same frustration.. Which in turn leads to them blaming the build itself. I urge the dev's to post a note in their threads with this solution, as it will help diminish unnecessary bickering/bashing/posting that these dev's must deal with regarding this issue. Also, I am posting it here because I tried MULTIPLE 'Droid builds and this was the only solution that worked for me.
Let me know if this helps anybody with their dreaded black SOD!! And a big thank you to all the dev's for their extraordinary hard work and dedication in bringing the amazing Android OS to our beloved HD2's.
Click to expand...
Click to collapse
+1... and i believe it's not just the SOD that our SD card is causing.. even the music stuttering, which some people are blaming the problem with the build, kernel and now the enabling of stagefright.. it's not consistent as only some people would have certain issues while most others don't.. i myself have fixed the SOD and music stuttering by replacing the sd card or just by simply fomatting the card.. so i think until we run the full Android on NAND, we would see a lot of incosistencies on the issue of the builds.. unless of course if the problem was something like "camera" for the desire HD build doesn't work.. that you can blame on the kernel as everyone has the same problem therefore consistency on the issue..

I already knew that it was the sd card. Since I never had any sod since august 1. (Started android using there)

I have been getting these alot recently. But it doesnt seem to be the SDcard for me. I can play music just fine without any stuttering. Im also been sufferring alot from touch screen freezes which is at its worst when walking on foot, yet its not so bad when on the move in a vehicle. strange.

+1 for me too.
Had exactly the same with an 8gb SD card but, since switching to a 4gb SD card, I've had no issues whatsoever. All my WINMO and Android installs work straight away with the new card but the Android especially would, 90% of the time, fail to load up on the larger card!

I currently have a temporary black and white sod, but it boots through.

I've got this Black-SOD only in Mdeejay Froyo NextSense 2.5. (No Wake up from Stand-By).
In Versions 2.1 to 2.4.2 are no BlackSod's for me.
I'm using a Kingston 16gbc10.

hey i too had the problem with SOD. i got it all fixed by changing the radio version to 12.50 it works fine i wouldnt blame the poor SD card btw what can u do wit a 2gb sd card... useless

i just replaced my stock TMOUS sd card and put in a 4gb card and loaded the Core Droid 0.5 and it seems to be working fine ( fingers crossed ), no SODs. And i'm also looking at low power consumption as well. Thank God.

pillai.raul said:
hey i too had the problem with SOD. i got it all fixed by changing the radio version to 12.50 it works fine i wouldnt blame the poor SD card btw what can u do wit a 2gb sd card... useless
Click to expand...
Click to collapse
The 2GB I'm using was mainly for testing purposes.. but I'm still using it until I can buy a larger one. Better to have little space with a working build, eh?

Well I'm not sure one way or another about the black screen SOD, but I am sure that the "skipping" is not related to the sdcard. Some cards, faster ones, seem to do it a lot less (I currently have 7 sd cards, different sizes, speeds, and makes, and have had some downtime at work so I did a bit of testing), but they do it on the evo kernels. Disabling stagefright does work, but it causes other issues with video, so i wouldn't suggest it.

Turn off auto-brightness it will disappear
Sent from my HTC HD2 using XDA App

I just performed a little experiment.
Bangsters 1.5, fresh install on my 16gb class 4... SOD present, hard.
Copied the contents of the card to my 2gb card... no SOD. can rapidly sleep\wake phone with no issues at all.
*sigh*

I have narrowed down Wake-up death screens to two Apps actually since I had no other MicroSD cards to test out...
AutoKiller - any preset you choose you will get SOD (wake-up SOD) - I don't use it anymore and no SODs (this may be actually MicroSD card as all those apps are on it lol);
Ummmm forgot the other one - URGH ... wait ... can't remember now ... once I do I will update my post...

I fixed my SOD problem by updating kernels. The one working for me now is the netripper nexus oct 8 one. I'm on TMO stock and Shubcraft 1.5

fflakes said:
I fixed my SOD problem by updating kernels. The one working for me now is the netripper nexus oct 8 one. I'm on TMO stock and Shubcraft 1.5
Click to expand...
Click to collapse
can you describe where to get, and\or how to upgrade to this?

Here is my solve
I have been experimenting with these Android builds sine day one. I saw many SOD's for the first few months though haven't seen one yet since I replaced my SD. Went from stock TMOUS 16GB Class ? to a Adata 4GB Class 4. I try a new build almost 3 times a week and since seen no SOD's. Now, my SOD's previously would appear normally under heavy loads or wake/sleep. I have had different WM ROM's and Radio's during this process so I dont think its due to the WM build present in the phone.
Im now running the latest eleg WM build and the HyperDroid latest Android build. Great simple non-sense Shub/CM based ROM with no issues. Definitely a daily user. Oh, and i keep my auto brightness on.
I will say i did see one SOD during trying a new EVO based ROM. But, i tried the "hold phone up to light bulb" and the display came right back. I dont know this is the ABSOLUTE remedy to this issue, but worth a try. I changed to a different ROM immediately though because that one had some data issues...But other than that I can say im completely satisfied with using android as a daily and not returning back to WinMo anytime soon.
...Thanks Dev's

[Q] Temperature = SOD/Freeze?

So, maybe it's just the way I'm installing my builds, but a lot of the latest builds are giving me an SOD or a freeze. And it always seems to happen when the temperature near where the battery is gets pretty hot. And I use the new builds the same way I used the builds back in November and I don't recall this ever happening to me. Although, my first HD2 died of screen hardware failure and I have a new one, so maybe it's a new model of HD2 that could be doing it. I don't really know, I'm just trying to suggest possible reasons. I'm using the stock 3.14 rom and 2.15 radio and this has happened on the SuperRAM, MDJ Froyo HD, HD2ONE, and MDJ Gingerbread. Any thoughts?