Related
It went from extremely rarely doing it to three or four times just the other night in the span of a few hours. I can't reproduce it on command but it happens when I lock the screen and put it in my pocket. Then sometimes when I take it out it is entirely non-responsive, even the power button doesn't work. I have to remove and reinsert the battery.
It could be ADW Launcher or WidgetLocker since those are the only two programs always running, but I was hoping someone else experiences a similar issue. It hasn't happened when I normally lock it yet though, so it could also be the proximity sensor maybe?
Having the same issue (on Bell as well), but not running either of those two apps. Was almost to the point of returning the phone and then installed JM7 and it's been better, although not perfect. Last night it locked up with NoLED displaying an icon, so I've deleted that app to see if that's the issue. It hasn't locked up today, but it did reboot a few hours ago seemingly at random. :shrug:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
clubtech said:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
Click to expand...
Click to collapse
Oh, that doesn't sound pleasant at all...
I'm outside of Bell's 30 day exchange period plus I've talked for over 30 minutes, so I'll have to go through Samsung if it completely breaks. On the plus side, a phone from them should be three button recoverable.
Although I can't be without a phone for weeks, I hope it's not the SD card.
Mine Lags like crazy once every few days till the point I need to restart it. Any idea why this is do?
Sent from my GT-I9000 using XDA App
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
AllGamer said:
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
Click to expand...
Click to collapse
All gamer has a good sugestion here BUT we are going to get people flaming the fact that Android shouldnt need task managers.....
Ho hum..
TBH in my experience, I have found (after a couple of hard resets) that there appears to be a size limit for installed apps. Once I get over this size limit, I get LAGTASTIC, phone slows to a snails pace, then I remove a few of the apps and I am back at light speed again....
I cant say what the limit is, but I know when I have hit it - I would then uninstall a lame app or two and get back running.
Yes a lot of people "claims" that, but yet you do a search in Android Market, you see LOTS of Task Manager / Killer apps for every phone.
they were not designed for Galaxy S, they were designed long ago for all the other phones that had and still have the same problems of memory management causing lags
Android is not robust enough to survive without one
heck not even Windows 7 or Windows Mobiles phone
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Frostshock said:
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Click to expand...
Click to collapse
i don't think that is the case with the Galaxy S
however back then my Treo 650 did suffer from that.
if you believe that is the problem then try this
http://forum.xda-developers.com/showpost.php?p=7999389&postcount=28
more cool apps here http://forum.xda-developers.com/showthread.php?p=7999389
Background:
The devs have had some major breakthroughs in getting Android ported over to our HD2s lately. Just a bit ago, they finally got Bluetooth working and I decided it was time to give it a shot. I was pleasantly surprised at the stability of the version I ran and have actually been using it as my primary ROM for five days as of this writing.
My biggest problem was in wading through the myriad of techno-speak and complaints piled on top of vague references to a non-existent thread over on the Leo forums. However, once I got things figured out, I was good to go and haven't looked back!
Please see post 2 for some tips and tricks and "Don't do's" that I learned along the way.
You absolutely MUST HAVE data access to install Android. If you have WiFi, that might work, but if you may be able to talk a friend with a data account to lend you their SIM card for a few minutes
For the curious, I did initially install Android on my 16gb C2 microSD card that came with the phone. See post 2 for why I am no longer doing so
Read "Steps" for the fast and easy version, "Details" if you're a bit nervous or want to see how neurotic I can be with explanations.
And so, without further ado, here is the simple method for locating, download, installing and running Android on your HD2!
Steps:
I recommend finding a nice, stable ROM and flashing it fresh after a Task29 before moving forward. Be sure to hard reset (or use Clear Memory under Settings) and then soft reset your phone to ensure the ROM is stabilized.
If you are using a stock radio you may have issues, the radio I am using is: 2.10.50.26.
Once your phone is up and running, go to Settings Tab->Sound & Display: Single Volume On (100%), Pocket Mode On, then click Backlight: Ensure "Automatically adjust backlight" is NOT checked, adjust your screen brightness to optimal levels, then un-check the other four boxes.
Exit Settings and make a call using the Speaker Phone, then turn the Speaker Volume to 100%.
Visit GameSquare by clicking this link and scroll to the bottom of that page, look for the "Download" link at the bottom. Save the file (currently it is named "HD2Froyo_V2.1.7z") to your computer.
At this point, it would be a brilliant idea to backup the contents of your microSD card and reformat it.
Once your microSD card is ready, place the file you downloaded from GameSquare on the root of the card ("root" means don't put it in any folders you might have on the card) and extract the contents.
If you removed the card to reformat or unzip the file, put it back in the phone. It is a good idea to go ahead and soft reset the phone at this point, just in case some of the hardware has developed some issues while you were working.
Open File Explorer and navigate to Storage Card->Android, then click on CLRCAD.exe (it won't respond, but then it's not supposed to, click it anyway), then click haret.exe. Always run CLRCAD.exe before haret.exe to ensure you can actually hear phone calls
You phone should now show the HTC Penguin and a ton of text. The phone may hang a few times, but it's fine, just let it run.
Once Android has booted, follow the customization prompts. It may seem to take forever to boot, but let it go.
Once Android has completely booted and you can see the Home Screen, wait for the icon on the top left (sd card scan) to disappear and then soft reset and reboot Android. If you have run Android or used Google Backup in the past, wait for the sync icon to disappear before soft resetting the phone.
You should now be able to fully load Android and make calls, texts, data connections etc. Enjoy!
Details:
Myself, I chose to ignore the google location, facebook - twitter - youtube logins and weather; this is because I never intend to actually use the Windows Mobile ROM anyway
You may or may not have luck with a different radio, but I know people running stock are complaining and looking for replacements. I will not explain where to find or how to flash radios in this thread, use the search button above to find one that will.
My screen brightness is set to 50%, which is optimal for me. Un-checking the boxes will prevent your phone from darkening the screen while Android is running!
This seemed to help when I had issues with a very quiet speaker and ringtones running Android.
I will not link directly to the build because (1) it's not my site or work and (2) there are important messages on that page that DarkStone1337 wanted everyone to read. For your edification, the original thread: [BUILD] [18.08.2010] [darkstone HD2Froyo V2.1] [kernel: darkstone 2.6.32.9 #36]
I haven't used a stock ROM in forever, but all of the customs I have run had a "Format SD Card" app in the Start->Tools folder. If you use your PC to format it, be sure to use Fat with a 32 cluster (or allocation) size. Formatting your card will help to eliminate issues that some have been having (I had the same issues and reformatted later). I found that formatting the card via Windows allows for a less-buggy system.
This will create a new directory named Android and a small text file. You can read the "readme.txt" file if you want, but don't move anything around. Unlike the original builds, HaRET is located in the Android folder and should stay there.
If I get a call, text or email on my phone before I get Android booted, I go ahead and soft-reset again. It may be a pain in the butt, but it helps to narrow down any issues you might have to just the Android build.
Android may reboot your phone before you see any prompts, and if so just go back and run CLRCAD.exe and then haret.exe as before.
If you have any issues, reformat the card and start over. Here is where you need that initial data (internet) access. Android does not require you to always have internet, but if you reset or re-install it, you will always need it at this point.
You can turn off the phone by holding the "End Call" button (that's the red one ) and choosing "Power Off" from the popup menu.
Of course, you don't have to enjoy Android, that's just a suggestion
This tutorial is subject to updates and bug fixes in the future, but no promises
Be sure to read Post 2 for lessons I learned along the way!
Tips and Tricks
Format and Content of this post may change, depending on how I feel and what I learn along the way (respectively).
SD Card Care:
I would recommend you to always reformat your microSD card before installing or re-installing Android on it. This is the same as doing a Task 29 on your phone before installing a new ROM.
I don't know much about Android, but I've been using Linux on my personal computers at home for over 10 years. Android seems to continually read and write data to the SD card while the system is running. If it is in "write" mode and you change something on the card or reset the phone, it can damage your SD card. So far, I have managed to get through this by reformatting my card, but you can easily wipe the card by removing the battery or hitting the reset button instead of using "Power Off" via the Android menu.
Never attach your phone to the PC and activate "Turn on USB storage". When I say, "Never", I really mean, "If you ever, ever do this, your children will despise you." Writing to the card while Android is in "write" mode will cause data that is being written by Android to be misplaced and this is a very bad thing.
Do not use the "transfer to sd card" option that some of the apps may offer. For the same reason as the last tip, it will really screw your card up.
Android was not meant to run on external card like your microSD card. Some geniuses here on xda have managed to trick it into doing so, but it will never be safe. Some day the devs may actually manage to hack into the phone's NAND memory and then we can have real Android ROMs running without an SD card, but until then we have to use this system. You do risk ruining your card, but I feel that it is worth the risk
Stability:
Just after running HaRET, hit the back arrow key. This will cause your buttons to light up momentarily. I'm not sure exactly why, but this seems to help the battery drain issue a lot.
The current crop of Froyo (Android 2.2) builds all seem to cause issues with our phone's hardware. Specifically, the screen is often unresponsive, sometimes never waking up after being turned off and necessitating a hard reset or battery pull.
Bluetooth works, but you may have to cycle the service by hitting "Bluetooth" in a call twice, once to turn it off and then again to turn it back on. I have had to do this several times, particularly after a hard reset.
I find that a task killer is particularly helpful. I found a free one called "Advanced Task Killer Free" in the market and it works just fine for my needs. When I need to turn off the screen, I run the killer and wait a few seconds before hitting the End Call button. Using this method, I have reduced the non-responsive screen issues somewhat.
Another trick I have learned is to turn off the lock screen. Even the simple slider seemed to cause issues, so I found "No Lock", a free app in the market that, when activated, will turn off the lock screen. If you keep your phone in your pocket (bad idea, you're gonna scratch or break it!), this is not a solution you will be able to tolerate after a few butt-dials.
Some people over on the Leo forums report that turning off the Live Wallpaper helped with the non-responsive screen issues. I haven't really tried this because I really, really like the wallpaper interaction. Of course, since my issues haven't totally gone away, I gave that a shot, but it didn't seem to help.
I switched ROMs, trying to find a WinMo ROM that was lighter but still up-to-date and every call I made with the phone thereafter caused the "robot voice" (some call it the "android voice"). I am now flashing a new ROM that I found on the T-Mobile USA HTC HD2 ROM Development forum that said "Android" in the title. The chef claims it is "Android Safe" and so I've flashed it, but left the Android installation alone. The "robot voice" is definitely gone, so that's awesome. Not sure what else may have improved, but at least I can make phone calls
I've noticed a trend over on the Leo forums to shy away from "Best WinMo ROM for Hosting Android". Not sure why this is, but I will carry that trend on until I am better informed. That being said, I have flashed three different ROMs to my phone and only one has actually produced a stabilizing effect on my Android. You can find it in the T-Mobile USD HTC HD2 ROM Development forum, just search for "Android"
Apps:
Having trouble getting your apps to install? Try going into Settings - SD Card and "Unmount" your card and then try the install again. This worked for me when installing Angry Birds and Pocket Legends (two very awesome games).
"No Lock": This app disables the default sliding-lock screen. I had some issues early on with the screen locking up as I tried to turn it on. This has helped tremendously.
"Advanced Task Killer": Although cnet says this is rarely needed, they are not running Android from the SD card as we are You will need some sort of task killer because your phone can't handle the RAM drain every day activity brings.
"SlideIT Keyboard": Replacement for Swype. I've used Swype for so long that I consider this app a poor replacement, though you might disagree. It's better than nothing!
More to come!
Snarksneeze said:
Coming Soon!
This is just a placeholder while I get the real deal written. Please be patient, I have a 2yo to care for and my keyboard time is hard to justify these days.
Click to expand...
Click to collapse
Snarksneeze said:
Reserved.
Will put some lessons I learned in here later.
Click to expand...
Click to collapse
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?
Paten said:
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?
Click to expand...
Click to collapse
Sorry, I accidentally submitted my first post instead of previewing it. Had to work fast before I looked like a complete idiot. Guess I wasn't fast enough, eh?
Thank you for this post, Ive been wanting to do this for a while but the other threads were very confusing to me...
sound dll of 2.13.xxx.xx problem
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
אםזגםנש said:
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??
Click to expand...
Click to collapse
I actually had a custom ROM installed on my HD2 that caused the "robot voice". This ROM: {ROM}13Sep Omega WM6.5.x24634 Base3.04 manila2018#XT+Dinik+GTX+MaxSense+Black#Android is the only one I've been able to get a decent run of Android on.
We really, really need more than one option when it comes to ROMs that give Android good support, so if anyone else knows of one, this is a good thread to link it to.
szfjcr said:
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
Click to expand...
Click to collapse
I tried two different stocks: The one my phone came with way back in June and the new one at tmobile.com/wm_update. I was able to make calls, but the other person couldn't hear me.
I would recommend the ROM I linked to in the post just before this one; it's working great for me so far!
gonna try it thanks
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
dementievafan said:
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
Click to expand...
Click to collapse
You might want to check this out: http://forum.xda-developers.com/showthread.php?t=723200
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again
I'm one of the lucky ones!
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.
dementievafan said:
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again
Click to expand...
Click to collapse
Apologies to everyone for not responding to this thread while on vacation in Arkansas.
In order to install Android on the HD2 as a regular ROM we would need access to the NAND processor, which we do not have at this time. We may never be able to get Android to flash that way. In the meantime, we can run it via Linux by using HaRET (Hardware Reverse-Engineering Tool). As far as I can tell, this is the API version of Froyo, the one that can be run via an emulator and downloaded from Google. So it's not really the phone version of Android, but from a user's standpoint, there is no difference.
electshrimp said:
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.
Click to expand...
Click to collapse
Thanks for your feedback
You mentioned that you could not have completed the install without other tutorials. Would you mind linking to them or telling me what I am missing?
To write this, I reformatted my SD card and installed a fresh ROM, then detailed each step I made along the way. I have looked back but can't see anything that I might have missed.
I see that you are running Froyo Sense. I linked to the regular Froyo, since it was the version that ran without any issues for me. Would this TUT be better if I were to link to the other builds as well?
Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.
wackywalt said:
Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.
Click to expand...
Click to collapse
Glad things worked out for you!
Keep us informed of any issues, tips or tricks you stumble upon as you enjoy your new Android
i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated
rukhi said:
i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated
Click to expand...
Click to collapse
Stock simply doesn't work for Android. You can boot up, but can't make calls or hear external sound.
In order to get Android running, you will have to (1)Flash HSPL and (2)Flash an Android-friendly ROM.
I am far from being an expert on Android or Windows Mobile, so there may be something that I don't know about. If you are dead set on keeping stock, you might contact one of the Android-friendly chefs and ask them what changes they made to their versions.
Don't forget: Flashing your T-Mobile HD2 is dangerous. Never flash a ROM unless you found it here: T-Mobile USA HD2 ROM Development.
The original (Leo) HD2 is incompatible with the T-Mobile version and it is easy to get confused. Some websites aren't even bothering to mention the incompatibility and lot of folks are bricking their phones as a result.
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.
I noticed lately that when I get a phone call, I can't slide to answer when the phone is locked also when it is sitting for awhile charging or not, when I slide the lock button, the touch screen freezes and takes a few minutes to recover before I am able to make calls, text or use any application.
My DX is rooted andI am running leaked Gingerbread, however I was having the same issue with the Stock rom. I do not use any task killers.
I have installed Droidwall and Titanium back up.
Any help will be greatly appreciated.
rdeluis said:
I noticed lately that when I get a phone call, I can't slide to answer when the phone is locked also when it is sitting for awhile charging or not, when I slide the lock button, the touch screen freezes and takes a few minutes to recover before I am able to make calls, text or use any application.
My DX is rooted andI am running leaked Gingerbread, however I was having the same issue with the Stock rom. I do not use any task killers.
I have installed Droidwall and Titanium back up.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Are you overclocking?
Sent from my ADR6400L using XDA App
No overclock, no task killers. I use titanium back up and did not freeze or remove any apps. It is strange and reminds me of a laptop coming back from the hibernate estate, it takes a few minutes to reset and then is good to go.
Mine has been doing the same exact thing!
I have removed fancy widgets which is a nice Clock/Weather combo widget but I have a feeling that it might be the culprit.
I'll keep posting any findings and again help from the experts will be greatly appreciated.
We need to compare our installed apps to see if there is a common one. I don't have fancy widgets but I have MUIU clock/weather app and it seems really wonky.
I have pretty much traced this down to a bad MicroSD. Oddly, my PC will still be able to use them. My Nexus One wouldn't even touch the SD card that was freezing my Droid X.
Looks to me like Motorola left something out of its SD or FAT driver.
Is there a fix?
Right on the dot. I removed the SD card and "voila" no more slow downs. I guess must be something. related to the drivers, as you mentioned.
Today, I put back the Sdcard and gotfrom the Market place an overclock applicatkon called Droid Over lo k. So far is going good and very fast, however overclocking is always risky and shortens the life of any processor.
I'll keep you updated.
didn't work for me... seemed to help at first but I got the lock ups again today. About to move on from Motorola.
OK! After trying different combinations such as SD card, no SD card, Rooted, UN-Rooted etc.
Finally, out of desperation, I got my old HTC and pulled out the 16G SD card, put it on my DX and used it for 3 days with no freezes or lock ups so far. The funny thing is that this SD card that I put in, is a low end cheap Polaroid brand.
I'll keep you updated
It is a known fact that the SD cache is low on the Droid X. Higher class cards will have problems unless the cache size is raised. Even than, it's not a guarantee for success. I have a Class 10 card that caused crashes daily until I installed a mod for the cache size. Didn't solve all of my issues, but it stop the crashes.
You are absolutely right. I have been doing ok with the low end card. Recently I got from the market an app called SD Speed which raises the card cache and no matter which card I use now the systrm runs very smooth.
Thank you all for the help and feedback.
Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey
voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey
voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'
I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey
voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.
voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.
Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey