Related
had it about 2 months.
been great so far up till this week, when texting and typiung anywhere its slow as a badger...e x t rem el yyyy slow...........
takes forever..whys this??
havent upgraded firmware since buying it, should i?
should i delete my existing texts?
duno?
please advise...thanks!
ash213 said:
had it about 2 months.
been great so far up till this week, when texting and typiung anywhere its slow as a badger...e x t rem el yyyy slow...........
takes forever..whys this??
havent upgraded firmware since buying it, should i?
should i delete my existing texts?
duno?
please advise...thanks!
Click to expand...
Click to collapse
Does it also happen when you reboot youre phone? If not, you might be running out of memory. If there is a update availble for youre phone, its always adviced tot do a upgrade.
Yes when i reboot my phone i still have the same problem :-(
ash213 said:
Yes when i reboot my phone i still have the same problem :-(
Click to expand...
Click to collapse
Well, then i am not able to advice you further. Maybe as you stated you should clean-up some text-messages. Or do a factory restore or update. But the last two suggestions are really drastic. You loose all youre data.
Hope some other member is able to help you
Did you notice this issue after installing a certain application?
If push comes to shove try TouchPal.
Free app on market.
i have the same issue sometimes. even after the rom update, or even moreso.
many times putting in text will be laggy and i have to wait. this wasn't the case in the beginning so i'm wondering too what is causing this lags...
install a app manager (Taskiller) will do and post the list of running apps, I suspect there will be something running in the background that is the culprit.
yeah i sometimes get the same issue - especially annoying when typing and I press the space bar, and it doesn't register the spacebar.
Huey85 said:
yeah i sometimes get the same issue - especially annoying when typing and I press the space bar, and it doesn't register the spacebar.
Click to expand...
Click to collapse
I fixed this by re calibrating the keyboard to my finger.
I came on here tonight to ask about the very same problem and found this thread.
My version of the problem is slightly different:
Usually when I've just turned on the phone texting is OK. After a while it becomes very slow and laggy, I mean glacial. If, for example I receive a text and want to reply straight away I'll hit 'reply' and it will take several seconds for the text entry screen to appear. Then the keyboard is laggy, literally two seconds delay after hitting a key before the letter shows on the screen.
Sometimes though, it will start off slow, like I just said and then half way through the message normal response will be resumed.
I did have Touchpal installed but this became very, very slow. Reverting to the standard keyboard improved things but still very slow as described.
I thought maybe it's something running in the background slowing things up but how can I tell what's running? Is there a good app for monitoring running apps?
I've just installed taskiller.
Amazing how many bits and pieces are running really.... anyway, killing a few running programs has improved things just now.
I'll keep an eye on it.
hi yeah i had the same problem as you when i was using the modaco rom
but then i changed to the updated rom
HTC Generic 2.73.405.5 with radio 63.18.55.06EU_6.35.06.18
on this website... first post
http://android.modaco.com/content/h.../03-09-hero-roms-radios-in-update-zip-format/
and all was fine
You will have this problem with many phones... On the hero it does not lag that much imho, it just takes a while to load many messages, like 100 and above will take a while, and sometimes the keyboard takes a while to load, that is true and I can confirm the same thing here :/
xTuX said:
You will have this problem with many phones... On the hero it does not lag that much imho, it just takes a while to load many messages, like 100 and above will take a while, and sometimes the keyboard takes a while to load, that is true and I can confirm the same thing here :/
Click to expand...
Click to collapse
Well, when it is slow it is glacial on mine!
If it's misbehaving it can be five seconds from hitting the messages icon to actually getting anything on the screen, then a further five seconds after selecting the appropriate thread, then two or three seconds to get a useable text box to type into and then each letter takes a couple of seconds to register in the text box.
It's taken me a couple of minutes before now to actually get a two or three word reply sent off! Irritating in the extreme when you're really busy and just want to fire off a quick text.
I think you haven't updated to the lattest release of HTC for the Hero?
Then do so since it will fix your problems.
As people said here if it has to do with apps running in the background this is much better handled on Hero.
Android OS keeps all apps that you start in the background and begins to close apps if memory is getting short.
cheeriot said:
I think you haven't updated to the lattest release of HTC for the Hero?
Then do so since it will fix your problems.
As people said here if it has to do with apps running in the background this is much better handled on Hero.
Android OS keeps all apps that you start in the background and begins to close apps if memory is getting short.
Click to expand...
Click to collapse
Mine's the T-Mobile G2 variant which I'm keeping stock (for the time being). The latest HTC ROM update has not yet been released by T-Mobile!!!!!
The problem I constantly get is some keys registering as a long touch, so I get the secondary symbol instead of the letter I intended. I press the key as long as all the others, but the phone seems to hesitiate for a second, then insert the symbol instead of the letter.
Sausageman said:
The problem I constantly get is some keys registering as a long touch, so I get the secondary symbol instead of the letter I intended. I press the key as long as all the others, but the phone seems to hesitiate for a second, then insert the symbol instead of the letter.
Click to expand...
Click to collapse
I sometimes get this also, but only in combination with the slow behaviour described above. If the phone is performing at normal speed then the long press problem doesn't occur.
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape,
SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZING AND LAGGING BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then Physically turned the HD2 around and Back to Portrait orientation, AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG OR FREEZE.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 back around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
thesweeney said:
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape, SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZES BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then turned the HD2 Back to Portrait mode AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
Click to expand...
Click to collapse
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
ala380 said:
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
Click to expand...
Click to collapse
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol keep with the testing though I didn't figure that much out
Hmmm this is def the prob for my touch screen issues. I tested a bit using the latest mattc Leo + Froyo w/Sense 1.5 version, with latest FULLRAM. I found that while on the sense home screen if I hold the phone out in front of me either landscape and portrait it's ok, and I can do whatever I want at full speed no lag at all. THEN if I lay the phone flat, It freezes. I did this like 20+ times and every time It would freeze whether I was playing a game or reading an email.
This also happen to me. Using Mattc 1.5 Froyo, it happens when using internet browser. The screen will freeze or not response right after i turn from Portrait to Landscape or sometimes have to wait for few seconds. I have to turn my device from Landscape to Portrait, and back to Landscape again, then the screen responses back to normal. This also happens in Copilot app when using in Landscape mode.
I turned off the screen rotation
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
robrob777 said:
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
Click to expand...
Click to collapse
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
thesweeney said:
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
Click to expand...
Click to collapse
I want to know too! disabling auto rotation doesnt mean completely stop the g-sensor running.
Bimme said:
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
Click to expand...
Click to collapse
Please tell me....
Did you fresh install 1.5 or upgrade 1.4>1.5?
I had quite a few freezes on 1.4.
Then I upgraded to 1.5 and kept my apps etc from 1.4.
I HARDLY HAD ANY FREEZES AT ALL
Then I did a fresh install of 1.5 and started getting LOTS of freezes.
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
I have the occasional screen freeze on landscape, but not very often using froyostone.
Bimme said:
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
Click to expand...
Click to collapse
Cheers for that ^
+1 for the Gsensor polling intervals seeming very slow.
THIS CAN BE SEEN VERY CLEARLY USING THE 'VR TUNNEL' LIVE WALLPAPER.
Here the cubes move smoothly at a good fps while the tunnel moves around at what appears to be 4/5 fps.
ala380 said:
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
Click to expand...
Click to collapse
Hehe, Thanks for that ^.
I dont feel quite so stupid now
For a moment there, before I found out it was a known issue... I thought I had discovered the Androids very own penicilin or something equally as important... but as usual I was behind the times lol.
Jealousy said:
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
Click to expand...
Click to collapse
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Do the G-sensor and the Dgital compass 'interlink' or communicate in any way? Is it possible that the screwed up compass output is screwing with the g-sensor output?
I ask this because the game 'hungry shark' thought that my phone was flat whent the usb port was pointed down towards the floor.
Dont know if that makes sense but for me it seems like the g-sensor is fubar as well as the digital compass.
trilbyfish said:
I then used even bigger and bolder letters to emphasize my points!
Click to expand...
Click to collapse
[SARCASM]Very helpful buddy[/SARCASM]
I did the font size thing for people who just wanted to skim through the long post.
thesweeney said:
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Click to expand...
Click to collapse
Well ofc, it wouldn't freeze when it's COMPLETELY hold still, but I guess that shouldn't be the point of daily usage.
Now when it comes to spontaneous outside actions, you are trying to pick up a call using touchscreen cuz ur used to it or trying to shoot out a text in hurry, and your device will just go sleep for some time. I mean, how'd you hold still if you're moving (fast)?
If you ask me thats pretty much a major bug, not to forget the 3g data thing. I'm not moaning around, just want to attain more focus on this. I notice people losing themselves in some benchmark trolling - just time waste.
There is already a thread for that (walking dead)
Just found a possible solution, please repport if it is better for you too :
- boot windows mobile, calibrate the g-sensor in settings (i did it 2 or 3 times, but i don't think its important)
- do a proper shutdown of wm
- restart wm + android
Sent from my HTC HD2 using XDA App
After disabling "Auto-rotate screen" I haven't had a freeze yet, so good so far.
I've tried 3 different roms and while in standby my phone freezes. The screen goes black and won't come back on, and eventually the buttons won't even light up. Is this a known issue or could I be doing something wrong? I am running all stock windows mobile.
Thanks in advanced.
should post this in the Android thread.
However, I'll give you my $0.02. I've noticed there is a lag in my build as well. Sometimes it won't seem to wake up. Often I just need to wait a bit and it wakes. I've read that two things can be causing this: 1) autorotate in android (you can turn off in settings, but I kinda like it) and wrong ROM. Peruse the 'droid threads for good ones, everyone likes Miri's.
This happens to me too. I've tried a few of the recent builds and when I put it on standby and wait 5 minutes I get a black screen and nothing but backlight.
EDIT: Reformated storage card and so far so good. Give this a shot
Been months since i last was on xda, is there a ****tional android rom now? SWEET! Where do I finde it, wasnt able to find anything by searchin on the forum.
Had same problem. And got solved after reflash my radio to 2.11.50.26_** and ROM to ChuckyROM GTX + CHT 1.8.5. Also formatted SDCard(so i also used a fresh android build).
So i would also suggest formatting your SDCard to FAT32
I formatted the SD and the problem remain. I noticed that (in my case) if i start android from WM Explorer, i dont have the problem. If i start android from Android Windows Boot, the phone freeze in standby. Give it a try, dont have to modify anything. Good luck!
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.
Hi, I know people are usually looking for opposite, but this happened to me yesterday: was playing score oriented game without save option for 3 hours going for personal best, still not dying and it was 2 AM. So I just left it running with pause and screen off. It was working that way whole day for me. But in those long 8 hours of innactivity phone automaticly killed it, started loading like newly launched app. I was so mad I instantly uninstalled game and wanted to smash that phone. I have my hands to clear my ram manually when I really need it, no need for this nobrain automatic cleaning. When I pause app running I want it to stay there unless I decide to kill it, no matter what. Dont care about some lag or battery life. For me only reason to buy expensive phones like this instead of 150€ phones is gaming, portable console (actually phonecalls and SMS are like 3% of my phone usage). On my computer when I leave singleplayer game minimalised its there (even after few days) as I left it. Is there any way to make it possible on android? Smashing clear ram manually 150 times per day is better option for me than this auto clearing bull***t. My phone is rooted, but I am noob in android, have no idea if its even possible to do.
EDIT: Sorry, bad section, didn't notice Q&A, thought this is just offtopic general discussion about anything S7 related. Can you please move it?
The phone shouldn't kill any apps by itself unless...
1. You have some memory clearing apps that do that.
2. Your phone run out of memory. Some ****ty app or game that is poorly written can cause memory leak which continuously taking more and more memory until process being killed when the phone run out of memory.
3. Your phone restarted when you sleep.
Also memory clearing apps are useless on android and can actually slow down your phone a lot.
Sent from my SM-G935F using Tapatalk
Thx for reply, i did not download any memory cleaners but there is some default samsung app for it, must check it for settings. I dont think phone restarted - it might, but it never happened to me on this version of rom during day. Memory leak from some apps or something wrong with this app - that might be the case. Or maybe I screw something in aroma while installing rom where I chose some batery/performance tweeks without description what they actually do.
*Telcontar* said:
...
EDIT: Sorry, bad section, didn't notice Q&A, thought this is just offtopic general discussion about anything S7 related. Can you please move it?
Click to expand...
Click to collapse
Hi,
Done, thread moved in Q&A section.
Friendly advice: next time, use the report button to ask the thread to be moved, any moderator affected to the area you post will handle this. We moderators don't read every threads so if you only write "Can you please move it?", good chance it won't be noticed
Thanks!