[HD2 Android Q&A, Help & Troubleshooting and Genera] Dr.Move:
I'm tired of new question threads always asking about the same problem, so this is a list of most common problems in Android and how to solve them. I'll add more things as I read more and I also would appreciate your feedback, I'm using SD without MAGLDR and probably will keep on using Android this way so I'd also appreciate any feedback about how to solve problems regarding MAGLDR and NAND, though some of the solutions here might apply to them as well.

hopefully this will get stickied so new Android users will find it fast.

there's a small FAQ at the buttom, which will be improved and expanded in the future.

This thread is tagged with Android Troubleshooting

for easier search

feel free to ask your questions here, I'll try to answer them, and will post only the answers that work here, so I would appreciate it if you say which solution worked for you. Do not post questions, however, that are already included here before you try these solutions.

Before you start, make sure you have the newest Radio, 2.15.50 because it supposedly handles power consumption better, so if you have power problems, try to flash it. look in windows 6.5 section for how to do this. the red number is mandatory, flashing a non .50 radio will not enable you to run android.

also, make sure you format your SD using the SD card formatter 2.0 or 3.0 http://www.sdcard.org/consumers/formatter_3/ choose full(overwrite) with size adjustment ON, or at least fully format it FAT32 using 32KB allocation unit size. Note that some cards don't work this way, but if you have Kingston, SanDisk, A-Data, Transcend or Team you should be fine. if it works with a card other than the ones mentioned please let me know.

My card fails to mount after I ..../ Card error, etc

it's mostly caused by files system errors, some are small so android will disregard them, and some are not, and thus is will ask you to remove the card. Most slow cards give this issue, if you want to know how fast your card is, benchmark it here: here a card with fast random read/write will probably not give these errors, or at least it will get them rarely (personal experience)

Solution #1

here's a fast solution: use any tool to check for file system errors, the native windows tool will do, there's also a similar option in minitool partition wizard and in plenty of other disk tools. in windows, all you have to do is right click the drive icon -> properties -> tools -> error checking and make it automatically repair the errors because it's more convenient.

Solution #2

if you still encounter the problem frequently, backup your data then format the card using the panasonic SD card formatter, or just google for SD formatter, you might stumble upon the official SD association which also offers a similar tool. in options set full(overwrite) with size adjustment ON. I recommend deleting all android cache files before you resore your files to the SD, even the image thumbnail folders.

Solution #3

if your device has these lags from time to time, don't start overwhelming it with extra commands, leave it to rest for a few seconds and then start again, I found this decreased the errors on my device.

Solution #4

try another SD card, preferably from another brand.

My device stuck on [fill in the blanks] after I started android for the first time

I'd recommend first rereading the whole developer's build page and see the FAQ on their page, check if you've missed something somewhere.

Solution #1

make sure you have at least 1.5 GB on the card after you've copied your android folder and make a fresh install again after you check your card for errors.

Solution #2

check if the build you want needs special partitioning, as far as I know, most builds run on unpartitioned SD, but make sure you read the build page thoroughly.

Solution #3

Wait for more time. Depending on the speed of your SD it may take longer to create the Data.img file or to convert needed system files, but normally shouldn't take more than 30 minutes. if it fails, reset and check the Android folder, if it has a data.img file but still smaller than 512/1024 MB (depending in the build) then you should probably wait for a longer period, or just try another build ;)

Solution #4

some build require a config.txt file to be created before they can run, make sure you have the right confing.txt for the build and that you haven't misspelled a thing here or there. I once set the data.img size to 1MB accidentally and gladly I checked that before asking the developer ;p

I have a high battery drain on wakeup/standby

we'll start from easy solutions to more extreme ones.

Solution #1

lower the CPU speed using setCPU, this also sloves the heating up issue -> freezing. I've used my device with normal CPU speed without freezing, but wakup power consumption really decreased with lower CPU speed. however, setCPU caused my standby power consumption to increase four folds, so I removed it. Probably build-related.

Solution #2

make sure you let WinMo settle before running android, that means let sense load fully and wait for a minute or so. also Try to load android with flight mode on.

Solution #3

install a monitoring app so you could see which apps are consuming more power, some beta apps use your processor even in standby, mainly beta apps, uninstall those apps and it might solve your problem. I've found that in my case, setCPU caused a high standby consumption. Also perfect viewer1.4, Circle launcher, and some widgets also cause me high standby drainage. Killing Perfect Viewer solves it, but I had to uninstall the other apps.

Solution #4

Flash a new Radio/ a different Radio. I've used 2.10.50 without a problem on Super RAM Froyo, but 2.15.50 definitely improved things on sense builds. some users repost 2.12.50 to work fine as well. Try different radios and see what works best for you.

Solution #5

Try another build ;)

Solution #6

Try a different SD card. Cards differ in their power needs, so search for one that consumes less power.

FAQ

Q- Which android build is the best/ I want an android build that has….etc.

A- Every and each android build is the best to someone. Developers spend long hours to make their builds better, faster and more stable, each with strengths and weaknesses. So to make it more simple, you have to look at each build page, see if it has what you need, then try it. If it doesn’t work, try another until you find something that suits your needs best. Here’s a page that lists all the builds for you:HTC HD2 Android Roms

each one is worth try, and believe me, asking which one is best will NOT save you time.

Q- which SD card class is better to install android?

A- All! the class means the device can write faster on the card, and probably read faster as well. But it all really depends on how fast can the device access info on the card, it's called Access time or something.. the lower the time the better, so two cards of different classes may have the same access time, so the only difference you'll notice is the speed of file transfer. look it up and you'll see what I mean

Q- My device lags after installaing apps

A- You probably have a senseHD build based on DesireHD. the original device has a similar lag so it's normal to have a lag on that build. Don't stress your device with clicks and just wait for 20 seconds after each app installation then tap open or done.

Q- I have a wakeup lag/lock screen of death

A- It's mostly SD dependent since users report not having a lag with higher classes, though I never had a lag with my SanDisk 2GB C2, and I have a small lag with my A-Data 8GB c4, so it's probably the card access time again. you can try setting the brightness to max, or never stress the device, if you do, it'll freeze and when the screen turns off, you'll never get it on again sometimes.

If you encounter a wakeup lag after a call, it's proximity sensor-related, there's a tool on this site to recalibrate the proximity sensor. I've never needed it though.

Q- Do I have to use task killers?

A- In Froyo, you don't. Froyo handles files differently, in a way that won't affect performance or battery consumption. if an app uses more power, then it's tha app's problem, uninstall it. If you kill it, Froyo will load it a few minutes later if it feels like being used frequently or so. but be my guest and try it for yourself.

I found some of the solutions here by myself, and read the others everywhere on the site. since it's hard for me to name all the people who found those solutions, I would like to thank them all, whoever they are. I could never have done this without the XDA community.