I have been using builds versions of the Android OS for several months now and I don't even think about going back to WM. Since the SOD and the G-Sensor freezes I only had the following problem.
The problem is that the data connection freezes occasionally. This happens in PPP builds. It occurs more frequently in the place where I live where the signal is not strong and the connection shifts from 3Gt o edge and back. When the freeze occurs, the radio arrow indicators freeze as well. The up arrow remains solid white while the down arrow is grayed out. In order to get around the problem I have to disable and enable radio and some times kill all processes that are hunging on the radio through TasKiller.
I have tried a number of builds, kernels and radio combinations. From darkstone, mdeejay, matc, hastarin, michiprima, 2.7. 2.10, 2.12. 2.14., 2.15 you name it. The problem is always there.
I would like to ask if anybody else has this issue on a regular basis. If there are any recomendations of things to try, or I should just wait until it is fixed like the G-Sensor bug.
My current configuration is:
WM : Miri HD2 WM6.5.X (23139) ROM :: V 22.0
BUILD: mdeejay NextSense v.2.4.2
Radio : 2.15.50.14
Kernel : Hastarin r7.4
Network : TMOUS
attractor said:
I have been using builds versions of the Android OS for several months now and I don't even think about going back to WM. Since the SOD and the G-Sensor freezes I only had the following problem.
The problem is that the data connection freezes occasionally. This happens in PPP builds. It occurs more frequently in the place where I live where the signal is not strong and the connection shifts from 3Gt o edge and back. When the freeze occurs, the radio arrow indicators freeze as well. The up arrow remains solid white while the down arrow is grayed out. In order to get around the problem I have to disable and enable radio and some times kill all processes that are hunging on the radio through TasKiller.
I have tried a number of builds, kernels and radio combinations. From darkstone, mdeejay, matc, hastarin, michiprima, 2.7. 2.10, 2.12. 2.14., 2.15 you name it. The problem is always there.
I would like to ask if anybody else has this issue on a regular basis. If there are any recomendations of things to try, or I should just wait until it is fixed like the G-Sensor bug.
My current configuration is:
WM : Miri HD2 WM6.5.X (23139) ROM :: V 22.0
BUILD: mdeejay NextSense v.2.4.2
Radio : 2.15.50.14
Kernel : Hastarin r7.4
Network : TMOUS
Click to expand...
Click to collapse
I wrote these instructions after I finally found a stable build without SOD and high battery drain. Give it a shot: http://leoandroid.com/viewtopic.php?f=212&t=168
Related
I have been troubleshooting this issue for some time now and have narrowed down to 'my HD2 unit' which has an issue only on 2.10+ base roms. Apparently this does not affect most users and appreciate any ideas for resolution.
When using 2.10+ base roms:
Receiving calls, the screen blanks off which is ok for calls but when I try to access the phone during the call, no buttons can light the phone except the end call which of course ends the call.
When any other buttons pressed, the button light just turns on for a split second and turns off, nothing else. Volume buttons seemed to work as volume can be changed but screen just remains blank. After the call is complete, the screen turns back on automatically.
Strangely out going calls are fine and do not exhibit this symptom.
What I have tried and does not help:
Different radios (both 576mb & non 576mb versions)
Different HSPL (1.42, 1.66, 2.08)
MTTY, fresh rom install, hard reset everytime and test immediately before any application install
One more note is that my unit was one of the early batches which I ordered from expansys.co.uk but should be from HK.
Thanks in advance...
Are you enabling Tap Time or Screen Sensitivity using BsB Tweaks? If so switch them off and see if that resolves the problem.
ClydeB1 said:
Are you enabling Tap Time or Screen Sensitivity using BsB Tweaks? If so switch them off and see if that resolves the problem.
Click to expand...
Click to collapse
Nope. I have been using Topix all the while and tested each rom from a fresh install, no additional apps.
Currently I have downgraded to Topix 1.6 (1.72 base rom) and the issue was resolved
coatercup said:
Nope. I have been using Topix all the while and tested each rom from a fresh install, no additional apps.
Currently I have downgraded to Topix 1.6 (1.72 base rom) and the issue was resolved
Click to expand...
Click to collapse
so you've not tried other 2.10 based roms, just the topix?
maybe try another rom based on 210 to see if you get the same effect?
fards said:
so you've not tried other 2.10 based roms, just the topix?
maybe try another rom based on 210 to see if you get the same effect?
Click to expand...
Click to collapse
Yes, I did try. in fact originally I thought the 2.10 rom by zenkinz had problems so I switched back to Topix then 1.6+ roms. now I know it is due to 2.10 rom compatibility...
coatercup said:
Yes, I did try. in fact originally I thought the 2.10 rom by zenkinz had problems so I switched back to Topix then 1.6+ roms. now I know it is due to 2.10 rom compatibility...
Click to expand...
Click to collapse
Strange thing is I never heard that before. You say more users experience these problems but at least it was never mentioned in the topix thread nor did I read about it in other threads. Did you ever flash back to stock and perform a task29?
You can check 2 things.
1- Older radios caused problems when 3g mode was set to auto. 2.10 radios don't have this problem.
2- Could be a problem with the proximity sensor hardware or settings. Try to test the proximity sensor by some other means.
kwbr said:
Strange thing is I never heard that before. You say more users experience these problems but at least it was never mentioned in the topix thread nor did I read about it in other threads. Did you ever flash back to stock and perform a task29?
Click to expand...
Click to collapse
Probably a good idea to try. I will try and feedback once I download the stock...
Well the stock flash did not work.
Tried to flash back to stock, hard reset
Re-HSPL, mtty, Topix 1.6.4, hard reset
Problem still exists, running out of ideas now...
I had the same problem...-My- solution was...
...turning off the -Face mobile down to stop ringing- feature...
FW-ROM v1.66 -hTC-
I Had exactly the same problems with miris 2.10 based roms. After some requests he built a 1.72 based rom. After flashing radio 2.10.50.19_2 a task 29, Installing HSPL 1.66 and flashing miris 1.72 rom the problem was gone. i also noticed a big improvement in in call audio quality and data connection stability. I am using his new v15.1 rom with the 1.77 base and it is great His roms are available at htcpedia.
Hope it helps
hey,
i am just interested what combination of rom, hspl, radio-rom and android version everyone of you is using. I am reading that some persons have no problems, other have big problem and they are using the same android version. So if you want to give everyone some information, just write down something like:
ROM – HSPL – Radio_ROM – Android_version – what is not working
If you don’t like the thread, you simple should not answer. But I think that people who have problems are interested, what combinations the persons have who are using android without problems.
My combinations:
Chuckydroidrom 5.8.10 – HSPL 2.08 – Radio 2.12.50.02_2 – Mattc1.4
everything works fine, but the market for example is still laggy (and I have the problems everyone has who is using mattc1.4)
sorry for my bad English, I am german and my last lesson is years ago
Artemis V25 FRA – HSPL 2.08 – Radio 2.12.50.02_2 – MattcFroyorc1.4
All features works as designed but huge latency sometime with the interface : phone blocked for 3 or 5 sec then I got control back.
When enabling audio speaking when calling sometime the call failed or the audio speaker is not working : I've to recall my contact.
thanks a lot for your work. I had a G1 before HD2 and I'm glad to experiment again the Droid adventure. This I couldn't not do without all the "Droid members" and "Linus Torvald".
Keep on going
Kind regards
After many tweaks and tries... I am 100% happy. NO ISSUES except camcorder of course.
It is rock solid, fast, and most of the time I forget this is not a "true" android loaded device.
HD2 T-Mobile US
AxLor DF1 XLITE (23128) ROM
Darkstone HD2 FROYO v1 Build
Cotulla 2.6.32.9#71 Kernal
Radio 2.10.50.28_2
HSPL 2
Android Loader v4.0
SetCPU 998 Max 614 Min
That's about it. Other than the system2.ext replacement for the GPS, there is nothing else.
Calls are loud and clear, no robot talk, data pulls from 3G and HSPSA and switches seemlessly between my WiFi spots I hit throughout the day.
Also, if it matters... in WinMo is have all switches on under Comm Manager. Data, Phone, 3G, WiFi. And Data Roaming is on in Android.
Loving it.
---
Sent from my HD2 DROID with XDA.
SicDroid
Could you possibly give me a link to
Cotulla 2.6.32.9#71 Kernal
AxLor DF1 XLITE (23128) ROM and
Android Loader v4.0
It would be appreciated, I'm trying combos and i would like to see how that works
mystik610 said:
I too suffered SOD on several different Android builds, ROMS, and Zimages.
I finally have a set-up where I'm not getting SOD anymore
Also, no robot voice (never had it), no 3G problems, and GPS works...though it takes a while to lock on my location (I know how to fix it, just haven't gotten around to it).
These settings are for TMOUS:
WM ROM: Chucky Rom
Radio Build: 2.12.50.02.2.
Android Build: darkstone
1GB userdata.img
Zimage: 08/02
I've been using Android consistently for 2.5 days. Battery life still sucks, but its reasonably fast, and very stable.
Click to expand...
Click to collapse
Here's the set-up I'm using now.
To expand on this a bit, I'm using a class 2 SD card. I have a class 10 in my Digital SLR, but would much rather keep that there.
llgtrainll said:
SicDroid
Could you possibly give me a link to
Cotulla 2.6.32.9#71 Kernal
AxLor DF1 XLITE (23128) ROM and
Android Loader v4.0
It would be appreciated, I'm trying combos and i would like to see how that works
Click to expand...
Click to collapse
Here are the links, I don't have my bookmarks restored yet so I can't find the link for the latest zimage... very important you use the 08/03 release (volume). It is posted around the forum.
ROM: http://forum.xda-developers.com/showthread.php?t=743464
FROYO Build: http://forum.xda-developers.com/showthread.php?t=735532
RADIO: http://www.megaupload.com/?d=89K700TT
GPS System2.EXT: http://rs117.rapidshare.com/files/409499714/system.ext2
Android Loader v4: http://forum.xda-developers.com/attachment.php?attachmentid=370121&d=1280534026
ZIMAGE: (VOLUME) 08/03
---
Sent from DROID HD2.
---
Sent from my HD2 DROID with XDA.
Chucky droid
2 10 50 26
latest shubCraft with cotulla #103
That works like a dream
Thanks SicDroid, greatly appreciated
llgtrainll said:
Thanks SicDroid, greatly appreciated
Click to expand...
Click to collapse
You bet.. just tried the FROYO Stone build. I am coming back to this one with a few tweaks.
.
Let me know how it works for you.
Sent from my HTC Desire using XDA App
Hi all,
Having a problem getting Android to run on my Telstra HD2. I do the following:
+ Run CLRCAD; all good
+ Run HARET; all good until -- 5 or 6 lines of the linux screen appear and then it hangs, or the screen goes blank depending on the Android build that I try running.
I have an Australian HD2 with the following specs:
Model: T9193 (Telstra)
OS: 5.2.21869
R: 2.07.51.22_2
G: 15.32.50.07u
D: 1.72.82124
I am using the standard SanDisk 16Gb Micro-SD card. I have tried a number of Android builds from gamesquare.co.uk with no luck.
Can anyone suggest what I need to do to get this running on the stock Telstra ROM?
Any help is greatly appreciated,
Peace..
Probably need to upgrade your rom
and radio. Look at some signatures of people who say their build is working good.
I didn't really want to upgrade the ROM and radio since it'd void my warranty..
RE: Telstra woes
I notice you are running 2.07.51 radio. I reckon it's your radio to be honest. I run 2.12.50.02_2 on mine. I have had problems with radios other than x.xx.50.xx radios. There is a link somewhere in here to all the working radios (I think in the definitive guide. Don't worry about warranty issues, if you ever need to deal with that, just flash back to the factory rom (but I take no responsibility .
Cheers
Definitely need to change the radio. You need a .50 radio. That also means you need to put HSPL on the phone. However, be aware that Android is not very stable yet. I couldn't get WiFi working and had all sorts of problems getting it to talk with Outlook. Went back to stock Rom highly modified (CHT etc)
Hmmm indeed the radio could be the problem. I use the 2.07.50.22_2 radio (although my G and and D values are also different from yours) and I've had no problems.
This way if anything catastrophically goes wrong with your phone and you're unable to flash the old radio back hopefully they won't notice
EDIT: Forgot about HSPL, thanks iandg.
Thanks for the replies.
I'm going to bite the bullet... I've just installed HSPL; no problems.. Now to find a radio update..
iandg said:
Definitely need to change the radio. You need a .50 radio. That also means you need to put HSPL on the phone. However, be aware that Android is not very stable yet. I couldn't get WiFi working and had all sorts of problems getting it to talk with Outlook. Went back to stock Rom highly modified (CHT etc)
Click to expand...
Click to collapse
really? you had that much problems with it dude? I'm still a noob here but I must say that I'm having a really good experience with it at the moment.
My config seems to be working pretty good. Try this....
ROM is NRGZ maxsense rom:
http://forum.xda-developers.com/showthread.php?t=591784
Radio:
2.12.50.02_2
Android build is [BUILD][25.08.2010][mattc Leo + Froyo w/Sense 1.6b][Kernel: michyprima 2.6.32.9 #70]:
http://forum.xda-developers.com/showthread.php?t=736545
I have actually been using this as my main OS for the last 2 builds and it is really usable now. I have it syncing direct to my outlook server at work no probs at all (IT have hijacked it with security policies, but this is understandable). Other than that I reckon the DEVs here are absolute geniuses with how well this stuff is running.
Hope this is of some help
e1design said:
Thanks for the replies.
I'm going to bite the bullet... I've just installed HSPL; no problems.. Now to find a radio update..
Click to expand...
Click to collapse
e1design, I have the same phone in the States on AT&T. Feel free to use my links below in my sig to get what I'm using. It works just fine. I haven't been on WinMo in weeks.
Done
Firstly, thanks for the replies in this thread.
I have to say that I've read it many times before: "Try the search function" - well it works wonders. With the information posted in thtis thread I was able to piece it all together and I now have Android on my HD2!
There are still a couple of things to iron out [WiFi, battery life and such] but in all a very worthwhile exercise.
Thanks again to the thread responders, and if you're in the same place as I was a week ago wanting to get Android on your HD2 - search on the keywords in this thread and you'll find it's as easy as can be.
Androis on T9193
Am totally thrilled to learn Android can be installed on the T9193.
Where are the best locations to source ROMs?
Suggestions on which are better and why?
Steps to Android..
Look at my sig and go from there..
I know I'm reviving an old thread here, but I'm wondering if any of you using a Telstra HD2 on AT&T (Cingular for me) here in the US have a stable Android install? I've been struggling with this for a long time now. I love Android but I can't get a configuration that will run longer than about 10 hours most of the time. I've gone through all the radios from 2.12.50.02_2, 2.14.50.02, and 2.15.50.14. I've switched my Windows Mobile ROM from Dutty CDLC v15 to OzDroid v1.11, I've switched my Android build from mattc froyo sense v1.8 to froyostone sense v3.2. I've gone through a couple different Linux kernels, currently on hastarin #8. No matter what I do I end up with about a 10 hour life before the device hangs. I have seen improving PPP performance with the different radios and kernels, but the overall device stability is the biggest problem. Could anyone using the Telstra HD2 for Android please post the configs that worked from them on their devices and include what kind of uptime you've achieved? I'm hoping this would really help me. Thanks in advance.
Ok For me I have the telstra HD2 and this is my Config.
Pretty much the latest of everything
- MAGLDR1.13
-Latest HSPL
-TyphoonN_CM7_v2.4.4.zip
- Radio 2.15.50.14
- Clockwork mode recovery v1.3
Just follow this: http://forum.xda-developers.com/showthread.php?t=933951
Hope that helps.
This is going to be a growing list of Android builds compatible with the 3.14 stock TMOUS ROM. This list pertains to those that want to keep a stock ROM on their device and use Android.
Tested by me:
1) [BUILD][21.09.2010][mattc Leo + Froyo w/Sense 1.8][Kernel: 2.6.32.15 #5]
2) [BUILD][02.10.10]Mdeejay FroYo Z v.1.0a|1.22.405.1|kernel: hastarin R7.1
User reported:
1) [UPD][BUILD]05.10.10|Mdeejay Froyo Sense v. 2.4.2|2.14.207.1|[kernel: huanyu #21]
__________________________________________
Please note this list is not complete. Maybe you can help complete it by testing builds and reporting here?
__________________________________________
Every build here is compatible with TMOUS 3.14
I think it's going to move soon.
justwonder said:
Every build here is compatible with TMOUS 3.14
I think it's going to move soon.
Click to expand...
Click to collapse
I tried schubCRAFT 1.5 and it had audio issues. (and a few more whose names I don't remember)
good info, i've had the issues as well with the 3.14...luckly nrg rolled back to avoid the audio issues and other problems
rr5678 said:
I tried schubCRAFT 1.5 and it had audio issues. (and a few more whose names I don't remember)
Click to expand...
Click to collapse
What kind of audio issues you're talking about?
I have used radio 2.14.50.4 comes with stock 3.14, but it gave me some echoes with some builds, then I reverted back to 2.12.50.02 and didn't any problems with it.
justwonder said:
What kind of audio issues you're talking about?
I have used radio 2.14.50.4 comes with stock 3.14, but it gave me some echoes with some builds, then I reverted back to 2.12.50.02 and didn't any problems with it.
Click to expand...
Click to collapse
The robotic voice and subsequent audio loss
radio 2.14.50.4 comes with stock 3.14 : Mdeejay Froyo Sense v. 2.4.2|2.14.207.1|[kernel: huanyu #21] running perfect.
boyhandsome said:
radio 2.14.50.4 comes with stock 3.14 : Mdeejay Froyo Sense v. 2.4.2|2.14.207.1|[kernel: huanyu #21] running perfect.
Click to expand...
Click to collapse
Ok, I will add this to the list.
Audio issues
I dont know whether it is audio issues or due to signal interference,this is what i did and found out
1) i installed the miri rom that froyostone recommends and the radio 2 14 50 04, i called my friend who was in the same house (with my home wireless on) there was a lot of echoing as soon as i turn the speaker mode on on either phones(other phone is samsung highlight).there was minimal echo present when i did with speaker off.
2)i flashed the new energy rom standard build and installed the radio 2 10 50 26 , and the froyostone 3.1 android build and called my friend who was at home with home wireless on.there was minimal echo with both or either phone speakers on when calling but none with speakers off. Then i did the same after my friend returned to his home and i called him from my phone(hd2) with either / both speakers on there was no echo on either ends.
Conclusion i dont know why i was getting the echo in my house, is the us version slightly different in hardware other than the rom/ram on it. Or the radio signal frequency interference, you can try this at home and please let me know what happens.
I dont know whether darkstone uses us hd2 or non us hd2.but the
energy rom is highly specific for us hd2 model ,i dont have any issues with it now.
US HD2
I think it will be good for all us hd 2 users to use the us hd2 specific roms for android testing for better results
I tested many Android ROMs... as some one already said.. some builds has robo voice issues.. so you can't say that all android builds are OK with TMOUS
Keep testing and update the thread
I've tested these two builds and are working superb!!
[BUILD][02.10.10]Mdeejay FroYo Z v.1.0a|1.22.405.1|kernel: hastarin R7.1
[UPD][BUILD]05.10.10|Mdeejay Froyo Sense v. 2.4.2|2.14.207.1|[kernel: huanyu #21]
gallant_suri said:
I've tested these two builds and are working superb!!
[BUILD][02.10.10]Mdeejay FroYo Z v.1.0a|1.22.405.1|kernel: hastarin R7.1
[UPD][BUILD]05.10.10|Mdeejay Froyo Sense v. 2.4.2|2.14.207.1|[kernel: huanyu #21]
Click to expand...
Click to collapse
Those are on the list already
phiremod is running awesome on stock 3.14 for me.
T-mobile stock
i am running [BUILD] [DISCONTINUED] [darkstone HD2Froyo V3] [kernel: darkstone] works flawlessly a few data issues here and there but very fast and smooth.... BTW i am running hastrin r 8.2
safe
i am runnin nexus hd2 android buil and is very stable and i have no issues with it only the battery life but las at lis 10 hours
donkey which android rom are you talking about? with what radio and kernel. Battery backup has improved a lot in all the ROMs... try having good radio and Kernel combination and test
BTW I love ur name .. no homo
any other working builds?
xtian63 said:
any other working builds?
Click to expand...
Click to collapse
It seems as if every current build works with TMOUS 3.14 - this thread is obsolete
Obsolete list? t-mous stock ROM still having issues with new android builds.
ROMS tried and failed due to robo voice:
hyperdroid1.7/CM6-michyprimaR11
mattc LEO+froyo sense 1.8
HD2ONE0.3.2/CM6.1
bangstersv.1.5
Currently running successfully on stock t-mous ROM 3.14, 2.15.50 radio, HSPL 2.08, 8GB class 4 microSD :
M-Deejay froyo sense clean v. 2.4-kernel MDJ S6.1 with the green camera tint fixed with M-Deejay's desire based build.prop.
1. format your sd card to fat32. Copy the android folder to SD.
2. unload all today plugins including sense.
3. turn off voice command in settings.
4. reboot, run clrcad.exe and haret.exe as soon as possible after boot up.
I manage 4-5 mah draw in standby, 12-14 hours of use with normal usage (30 minutes of calls, 20 to 30 SMS, 30 minutes of web browsing). If you wait too long to run clrcad.exe and haret.exe, the minimum power drain was 54 mah in standby. YMMV
Ok i have had a few versions on Android running now but seem to have the same issue with every one, which is ramdomly loosing data connection although it is showing that it has. My question is has it got anything to do with the WM ROM and Radio etc im Running or is it going to be the Android Build.
I have
ChuckyRom WWE
Radio 2.15.50.14
No android on there at the Mo as I have just formatted the card I did have Mdeejay Evo Sense v.23 Revolution
Can you help ?
TommyHD2 said:
Ok i have had a few versions on Android running now but seem to have the same issue with every one, which is ramdomly loosing data connection although it is showing that it has. My question is has it got anything to do with the WM ROM and Radio etc im Running or is it going to be the Android Build.
I have
ChuckyRom WWE
Radio 2.15.50.14
No android on there at the Mo as I have just formatted the card I did have Mdeejay Evo Sense v.23 Revolution
Can you help ?
Click to expand...
Click to collapse
If you have had all PPP builds (which I suspect you have), these data drops are normal. There are ways to improve stability, look around in the development section and your build thread, or switch to an RMNET build if you really want a stable (but slower) connection. If you're on RMNET already, you'll need someone more advanced to help you but your build's thread would be a good starting point.
Ok cheers, are my ROM and Radio ok as far as you know ?
The ROM and Radio is ok. In the android dev section you'll find this wrapper. Try it out. And I recommend you to use hastarin 8.5 kernel. Seems to improve the connection stability again.
Edit: Hastarin 8.5