Related
Since May, I've been having this persistent issue with my data not connecting. At least 5-10 times a day, I will have to either reset my phone, attempt to connect the data several times, or turn the radio off & on to get it to connect to data. I have flashed several different radios, the most current one being the 2.12.50.02.2 radio, all to no avail. Things will be fine for a while, but invariably I will start getting connection errors again.
Then, after trying Android, I noticed something- I got ZERO data errors while running Android. Same data speeds, same radio, etc. But NO errors until I booted back to WM, which leads me to believe that my ROM is the problem. I'm using the stock T-Mo 2.10 ROM, simply because I find it to be stable, quick, and perfect for my use(2.13 sucks). But it is apparently the cause of the data errors, so I'm going to flash something else tomorrow & see what happens. I'm not ready to make Android my full-time OS yet, not until it's perfected, so I'm gonna try the VBN ROM first since it's supposed to be good on battery.
Just thought I'd post, just to see if anyone else has noticed this.
P.S. can anyone recommend a good total backup program that can back up all my settings & reg edits & whatnot? I've tried Sashimi but it always crashes out when I try to backup my registry & settings.
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.
HD2 NANDROID is out, and I am stoked. Its been a while since I visited this part of XDA, and now that it out I can go dust off my ol'HD2 and put it back to use.
Thank you Devs.
But, are there any major underlying issues that still exist? Any Touch-Screen or System Lag issues? How stable and reliable are the data connections? How much of an improvement over battery life do we get?
I was experimenting with SD builds up until November, but could not find one daily user build so I put the phone away and bought a vibrant.
Are the builds at least 95% daily use ready or is it too early?
The two major things that prevented me from using any SD build were the very unreliable data connections and horrid battery life.
Thanks will be given out liberally for helpful replies =)
i have been using http://forum.xda-developers.com/showthread.php?t=893620 for a couple of weeks now with no major problems. had to enter the apn for tmous manually (settings are in the thread somewhere), MAGLDR wouldnt work on XP had to use a vista or win7 pc to flash. wireless tether works fine, gsensor works great (i used to have probs with that on SD loads), no robot voice with radio 2.15 but low in-call volume which the so-called "fixes" in the thread have not worked for me. just read the instructions clearly and you shouldnt have a problem, go ahead and give it a try if you haven't already chosen one.
edit: i dont know about battery life, ive never paid attention to that because i leave mine plugged in a lot.
update
i used the low in-call volume fix listed in this thread http://forum.xda-developers.com/showthread.php?t=858448 and so far it is working great.
Here is one of issue - all wifi sharing and explorer doesn't work in 80% of roms... :/
http://forum.xda-developers.com/showthread.php?t=939853
Hello wise xda guys.
Any ideas why my hd2 freezes after some time, when I use gps with osmand or maverick (or a couple of other software I tried before and unistall). It freezes completely, and I have to remove the battery. While it is working (before freezing) everything works fine.
[Another symptom (maybe irelevant) is the very slow gps fix (the first time), which deosn't really bothers me (I'm a patient person). I'm just writing it here because maybe there is a relation]
I use: Froyo 2.2.1, mod: Cleandroid 2.55, MAGLDR 1.13.
Otherwise the telephone is more or less stable
thnx
Same issue it seems...
Going to re-flash WinMo and test there.
I'm having the exact same issue lately and it is not funny/safe at all.
I first had it happening in google navigation all the time and now in iGO and Waze.
Can this be from Rafpigna's undervoltaged kernel or be a hardware issue?
Unfortunately the device freezes completely and doesn't give any error.
Does a log exist somewhere?
Any help is more than appreciated!
Yeap, still the same problem and I can't figure out why.
I've tried more than 10 different apps, but allways the same. After some time the phone freezes. I remove the battery, start the app and after a while, the same.
I tried working with battery only or with car charger only, still the same.
I removed and brought back all my apps with titanium backup, still the same.
I have a suspicion that when it stacks and after rebooting, if I leave it in peace (I mean don't do anything with the phone, just keep it without running any app), for some time (10-20 minutes), then it starts and keeps the gps app more time, than the time of the initial freezing. Maybe this is a symptom that could ring a bell to an experienced guy...
Anybody, any ideas?
I think mine is related to heat.
Left it in my pouch and placed iGO in demo on a long roadtrip. After 15 minutes the phone was warm and the screen was frozen so I had to get the batt out again.
More than frustrating since I have a 700km trip to do on Thursday.
Not sure about the heat
I had the same suspicion, that the heat was causing the freezing ) funny language ah?).
So I tested it while keeping it cool (I protect it from the sun and remove the car charger), but still the same happened. After some time it froze again. (the phone was cold)
I have a suspicion that a possible reason is the rendering of the maps. I've noticed that I have the problem, mainly when driving a car, where the maps images should change more often. I kept it in my pocket and made a few hours trekking, with no problems. Though in my pocket I had the app running in the background and I only open it a few times, just to add some points on the map.
Another sister thread
There is also this thread, by Crash-nl, with the same subject (more or less) so we can combine powers.
Check it out
http://forum.xda-developers.com/showthread.php?p=12391898
I'm also having GPS freezing issues, but probably way worse than you guys. I just got my phone from service center, but the issue still exists. I just quote my comments from an another topic:
I've now got back my HD2 from the service center. The GPS is now working, but not in Android. When I was using WinMo 6.5 with WWE 3.14 and 2.15.50.14, the GPS worked great. Fast lock, TomTom worked well and Google Maps worked fine. Then I decided to get Android again and after I installed everything, I discovered, that I had the same exact issue like prior the repair. The GPS starts looking the signal, if it doesn't find it, nothing bad happens, but when it does find the signal, it causes the phone to freeze. Instantly after the signal is found, it causes instant freeze. Screen stays on, nothing happens. What can cause this? I haven't yet tampered with the gps.conf settings, but I don't even think that it could fix the issue. I'm really going crazy with this.
Yeah, I'm thinking also its a driver issue. My current Android build is RAFDROID 4.0.2. And since this issue seems to be exatly the same, like before the repair, the GPS probably doesn't work in the earlier versions of RAFDROID. However something has changed in my phone, because the GPS has worked with nand Android builds in the past and even with RAFDROID 3.0. Now however, it doesn't matter which build I use, the issue always exists. Could it be caused because of the GPS module? I mean, does the WinMo 6.5 QuickGPS app save the AGPS data directly to the GPS module? So could there be some kind of corruption in the GPS module? I was having some sudden reboots, while using Google Maps and TomTom in the WinMo, but I was able to fix them, by hard resetting the device.
First time I started having this issue was, when I updated from RAFDROID 3.0 to 3.1. After that, the GPS has always caused instant freezing, when using GPS in the Android. Even downgrading back to 3.0, didn't solve the issue. Now I'm having this issue with all Android builds.
It's possible that my GPS module or "chip" could be somehow broken physically, but it's no point sending the device back for repair, because they send it back and say, "there's nothig wrong with the GPS". I'm really hoping it's not a hardware issue, because if it is, there's really nothing that can be done. I have still about a year left from the warranty and changing the module myself, will void the warranty. I just cannot understand why does the GPS still work in WinMo, but not in Android? Because if the module was somehow broken, should the GPS be defective also in WinMo?
I have tried flight mode, Wifi and 3G off etc. and the GPS DOES WORK. So the chip is not dead.
Just did some more testing on mine to try to find the issue.
I have always had a freez when I used google navigation with the sat image from the start in Android. But last week it happened in iGO and Waze which scared me a bit.
As a matter of test I installed WinMo again last night. Fantastic OS btw! and installed iGO.
Everything was up and running at 2am and I decided to let it do a demotrip of about a 1000km. The demo also sets the GPS receiver active.
I placed the HD2 it next to the fan of my laptop which is always on to generate some extra heat.
This morning at 10am the demo was still running perfectly.
Just reinstalled Android on it again. After 3km's in iGO 'gps signal lost' . I cannot get it back in any way. The GPS symbol is stuck in the bar above even if you disable GPS in the settings. So reboot is the only way.
This is getting very frustrating for me since my phone needs to work as GPS and may not fail.
Also a funny one is that it doesn't seem to matter on mine if the gps.conf file is on there or not ;-) lock time when the hd2 works is approx 1min
lukesan said:
Just reinstalled Android on it again. After 3km's in iGO 'gps signal lost' . I cannot get it back in any way. The GPS symbol is stuck in the bar above even if you disable GPS in the settings. So reboot is the only way.
This is getting very frustrating for me since my phone needs to work as GPS and may not fail.
Click to expand...
Click to collapse
I'm having this same exact issue! However I just discovered that the local service center did not change the GPS module or antenna. So this might be the reason why my GPS doesn't work. The service center was fooled that the GPS works, because they didn't test the GPS thoroughly. YOU HAVE TO ENABLE FLIGHT MODE OR TAKE THE SIM CARD AWAY TO TEST THE GPS!. If you don't do this, you are being fooled believing, that your GPS is working, but it's not.
You guys should test your GPS, by going back to WinMo 6.5 and leave your sim card away from the phone. If your GPS can find the signal even without the sim card, congrats, your GPS is working. If you want to be double sure, enable flight mode and try again. If your GPS cannot find signal, your GPS module and/or antenna is broken and needs to be replaced.
Well my module is working.
Easy way to test it and no need to take out your sim or so.
Just use the cab file attached to this post. If you will start it the first time it will scan the ports so you can end up with a small error in regards to BT but it not a real error.
The tool will continue to com port 4 where the gps mod is active on.
Go stand outside and voila, mine starts to show bars like it should be.
I'm taking a different approach now.
Ckeared everything and also took a fully fresh formated sd-card .... (as I type now not working)
lukesan said:
Well my module is working.
Easy way to test it and no need to take out your sim or so.
Just use the cab file attached to this post. If you will start it the first time it will scan the ports so you can end up with a small error in regards to BT but it not a real error.
The tool will continue to com port 4 where the gps mod is active on.
Go stand outside and voila, mine starts to show bars like it should be.
I'm taking a different approach now.
Ckeared everything and also took a fully fresh formated sd-card .... (as I type now not working)
Click to expand...
Click to collapse
Thanks! You just saved my time a lot! I downloaded and installed that app and I was able to get a succesfull GPS connection and now I can even get GPS lock, when flight mode enabled or sim card removed. This was impossible before installing this app.
However it seems that we are both suffering from the same issue. GPS does not work for me in Android. It has worked in the past, but nowadays, it doesn't matter, which Android build I use, it either freezes the phone and only way to fix this, is by removing the battery or it doesn't find the signal at all. Sometimes the GPS stays on, even if I turn it off. The blinking GPS icon goes away only by restarting the device.
If you are using gps navigation software on sd card, try format micro sd card with FAT32 and DEFAULT ALLOCATION SIZE option, do not choose allocation size such as 32,64 or any other except DEFAULT.
Try it and GL.
colosos said:
If you are using gps navigation software on sd card, try format micro sd card with FAT32 and DEFAULT ALLOCATION SIZE option, do not choose allocation size such as 32,64 or any other except DEFAULT.
Try it and GL.
Click to expand...
Click to collapse
Did anyone try this method? Looking at other threads I see people saying that only a warranty repair will fix the issue.
freezes
Hi. I had the same problem, i try everything formating sd, different builds and kernels. I disable "use wireless networks" and GPS work with no freeze.
Do you have a freezes on games?
did any one found the answer ?
is it a hardware problem ?
or a software ?
Thought I'd throw in that I'm having the same problem running hyperdroid rom on a telstra hd2. GPS finds a lock, works for about 2 mins then freezes requiring battery to be taken out to restart. I'm leaning away from a hardware issue as copilot worked perfectly on the same phone when I was running windows 6.5...
Just an update, after installing the new GPS fix from this link http://forum.xda-developers.com/showthread.php?t=1100114
[28.May.2011][Dev] GPS Libraries v1.0 for HD2 Gingerbread the GPS freezing problem is fixed. Full credit to the developer
Sent from my GT-P1000 using XDA Premium App
But the problem still occurs when using Google maps, Google navigation is now fixed
Sent from my GT-P1000 using XDA Premium App
Hi all,
I'm facing the same issue reported in post #12. I'm actually using latest Rafdroid HD (Froyo Sense) build on SD. Do you think I can try the fix in post 18, also if it is for Gingerbread builds? Please advise.
Thank you.
If I download from mobile network for an extended period of time, my phone will eventually freeze. The buttons will have no effect and I need to remove the battery.
Here is a way to reproduce it:
There is a game on the market called 'Contract Killer'. Download and run it.
It will then ask you to download ~250Mb of data, and where to save it.
If you choose 'SD Card' and download over mobile network, the phone will eventually freeze (after downloading about 95 Mb, sometimes less sometimes more).
At first I thought it was the SD Card but I changed that and it made no difference since it doesn't seem to happen when I save to the internal memory. I then switched on WiFi and used that instead and had no problems.
Also, sometimes this happens when I download a large app from the market. I tend not to use WiFi since I have an unlimited data plan.
Can someone with a large data plan please test this and see if they get a similar problem?
As a wild guess, I think that maybe using mobile data and writing to SD card together causes overheating. I tried underclocking my CPU to ~500Mhz and it made no difference.
I am using HyperdroidGBX-v12.
I have radio version: leo 2.15.50.14.
If there is a developer and you have any questions or need any debug information, please let me know.
FYI, if it helps any, for a test I just downloaded a 414mb file, saved to SD card, and had no issues, twice in succession.
I'm using tyween's TyphooN CM7 nightly (3.3.3), Magldr 1.13, & CWM. Radio 2.12.50.02_2
I tried switching my radio to 2.12.50, and I tried 3 different SD cards. It didn't help. I switched back to 2.15.50.
I don't know if it makes any difference but my signal is low (2 asu).
I also tried clearing all my data/dalvik cache/cache (after backing up of course). Then I installed HyperDroid-CM7-v2.1.0. It made no difference.
Anyone have any clues what could be wrong? Is it a hardware problem? I know I originally said it could be overheating but even happens when the phone is barely warm.
Also, if there is a way to turn off HSDPA that could be something I could try (although my network only supports 3G so I can't turn off 3G completely).
I am also having the same problem you described exactly,,,,verified with the Contract killer game.
And at first I also thought it was a hardware issue but freezes are not dependent on the phones heat status...and my HD2 is somewhat overheating from any network-SD card usage.
By the way,,,,I have changed through 7 different Android roms and problem still persists...
Mine also does the same thing and I hate to be the bearer of bad news but it is a hardware issue. My phone can not and will not endure any prolonged use of the internet, and or any apps what so ever. It used to only happen when i was using the mobile network now it does not discriminate, from my understanding its due to excessive overheating and from the BSA joint coming undone from the main cpu. There is a thread about it somewhere not sure where.