Database Users

Getting androiod to work on different roms!

I have done a lot of testing receintly and have found a few things that may help people who are having issues getting android to work, eg not booting or robot voice. This is what I have come up with so far.
Getting android working properly seems to depend on two things. Both windows rom and radio.
I have found the following in testing.
Having the wrong radio will stop haret from booting. I installed the standard htc hd2 o2 stock rom which is ver 1.72. I then tried to boot using the default radio which was 2.7.51.22
When I booted android it got to the stage just before linux loads and hung at that point.
I then simply installed the radio 2.12 and it booted perfectly also there was no robot voice and worked very well.
I also tried a couple of tmous roms and it did not seem to be compatable. It would boot up and run ok but I got robot voice. I built a standard rom using standard hd2 stock rom 1.66 and cured the robot issue.
I then built a tmous rom to get the 576mb hack with the same settings as the 1.66 using the same radio and got the robot voice again.
If anybody knows how to fix this that would be great. I know there are 576mb enabled roms out there that are android compatable I would be interested to know how they work. Eg thinking of energy roms!
Hope this helps when you are trying to get android working. I am currently using 1.4 which is awsme and the work that has been carried out so far in such a short amount of time is staggering. Keep up the good work folkes!!!

I don't personally see how the Windows Rom would effect anything with the Android side of things. I used a stock T-Mobile US rom until a few days ago and nothing has changed since I flashed a different WinMo rom. The only logical thing that COULD effect Android performance is the radio.

Breakthecycle2 said:
I don't personally see how the Windows Rom would effect anything with the Android side of things. I used a stock T-Mobile US rom until a few days ago and nothing has changed since I flashed a different WinMo rom. The only logical thing that COULD effect Android performance is the radio.
Click to expand...
Click to collapse
I was wondering about this as well. I have got Robot Voice from day one on every single build. I updated my Radio from 2.10 to 2.12 and still RbV. (I do get better battery life now though - go figure)
Anyway. I'm really confused as to what the ROM would have to do with it. As far as I know, the ROM is just some software windows uses to get everything non-radio working on your phone. Sense Haret completely shuts down Windows when it launches Android, how can the ROM have anything to do with it?
Someone please explain this!
I have seen pretty much every combination on both sides say it works, and then others that say it doesn't.
Something is amiss, and I wish I knew what it was.

YEah. I would like some more info on this as well.

I am just reporting what I heave lernt over the last couple of weeks, some not all tmous roms do seem to cause robot voice. As I said I built both a tomus rom and and 1.66 release rom with exactly the same settings and radio yet I got robot voice when using tmous and didn't when I used the 1.66 rom!
It is a very odd issue
Both were built using the same windows os 2189

phone call = unresponsive phone

okay so i've used the phiremod skinnyEVO1.5 and Mdeejay eVo Sense Stock and i've had the same problem with both. Whenever i make a phonecall/receive a phonecall, as soon as the person and i end the call my phone goes completely unresponsive. the screen goes completely black, and none of the hardware keys light up
the only thing ive found that can get the phone to come back 'to life' so the speak is to call the phone again and end the call on my phone with the end button.this doesnt always work though.
im running the Chunkydroidrom in WM and have radio 2_12_50_02
i even updated the kernel on the Mdeejay build and it still happens
is there anything that can be done to fix this?
please help me guys

different build, but same issue, nexus one by ummmmmmmmm matc forget which version. radio 2.15, wm chunky gtx sense with that CHT 2.0 i think..................

so far our windows mobile rom is the same cook, could be where to start im about to change my winmo rom

i just changed my windows mobile rom to ozdroid and im still having the same problem, and when i use the included bootloader i get robotic/froggy sounds in phone calls. maybe its not running clrcad correctly so ill try it the old fashioned way and see what happens

please
bump
can someone pleasee help?

good luck in finding help. Ive had some of the same issues i believe. My phone will completely freeze during a call for now apparent reason. it'll working fine in the call in the just freeze during my call. I tried different winmo roms that are suggested for droid builds. i believe i tried every radio available for tmo and about every build of driod and the problem is still there. It may run fine for a day then it starts freezing. I've posted a question about this yesterday and 97 people have viewed it and one person suggested i return the phone. I don't believe that its a hardware issue, more like a software issue. I guess i better learn how to pull the logs and then i may get a reply. i just haven't found a place that it explains it well enough for me to do it myself. My persistence will prevail though, cause I'm addicted.

Well please if you ever figure it out please let me know as this can get quite annoying
Sent from my HTC HD2 using XDA App

Disable Auto-Rotate in the Settings>Display.
See if that helps.

I had the same problem. I have Advanced Task Killer installed and it was set to kill apps on screen off. I turned off the option to kill apps on screen off and so far it solved my phone call = unresponsive phone.

I have theese issues only if i have certain call recorder softwares installed .. try uninstalling them , and if nothing helps delete ur data.img and do a fresh start(u can back it up tho if it prooves unusefull)

@souljaboy
what exactly do you mean by certain call recorder softwares installed? such as which ones?
@JonSolo
i disabled auto rotate and i still experienced the problem during phonee calls
@mike91t
i changed my auto kill to every 4 hours, so i'll let you know what happens with that over the course of the week

Same problem here, I've turned off screen autorotate, and I don't have any task killers installed. Everything works fine, and even a call or two, then it stops working and audio during calls doesn't work, and phone app becomes unresponsive.

have you tried a different radio rom?! maye 2.14 will help.

fruchtfliege said:
have you tried a different radio rom?! maye 2.14 will help.
Click to expand...
Click to collapse
well i waws thinking about changing to 2.14 but the android build im using recommends certain roms for best performance so i was going to keep using the radio rom and see if anything improved, so far i dont really think its working, so i might change to 2.14 because people seem to be having the less problems with it

[Q] [help] G-sensor problem

Hi,
I'm using a Tmous HD2, Energy for WM, shubcraft 1.5 for Android.
G-sensor worked fine in both OS, until one day I got stuck with the rain without the raincoat and my HD2 was wet a little bit. I dried it for one night. Everything still works ok but the G-sensor in Android.
I checked it again in WM. There's no problem with G-sensor (I can play games with it or rotate the pictures in gallery tab), but when I turned back to Android the problem still there so I assumed that it should be software's trouble. I booted again into WM, tried to do the callibration, turned on and off the G-sensor. Android's g-sensor kept not working. Home screen (Launcher Pro), browser, games, etc. can't use it either.
After that I downloaded another ROM of Android (JDMS 1.5), erased the old one, hard reset WM's ROM, installed JDMS 1.5: it didn't work as well.
What I haven't tried yet is trying another WM's ROM or re-installing Hard SPL.
So what do I need to do now?!

Can any one help me?

already reinstalled HSPL 3, nothing happened.

Vladikox said:
already reinstalled HSPL 3, nothing happened.
Click to expand...
Click to collapse
Did you try having Android build a new data.img just to test default settings?

jmmmmm said:
Did you try having Android build a new data.img just to test default settings?
Click to expand...
Click to collapse
I have deleted all of Android's files in SD card, then copy the original one --> problem not solved.

I am having the exact same problem. The G-sensor works in WinMo but not Android. I've tried re-formatting the SD card and doing a fresh Android install.
Were you ever able to find a solution or does anyone else have any other ideas of things to try?

My problem has been solved few weeks ago.
At that time I was going to lose hope and came to a decision of giving up trying and willing to say good bye to Android's g-sensor. I turned off the auto-rotate in Android for (about) a week. One early morning waked up, turned it on again and a wonderful thing happened: it was in land-scape mode.
In next few days the sensor was not working so well (but at least it worked). Now it run smoothly and I don't get trouble with it anymore.
Wish you can fix it successfully!

I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.

pvdw50 said:
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
Click to expand...
Click to collapse
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?

I've also got this issue after installing a new kernel and no matter what combination I use now it won't work again. I've tried all of my previous working combinations and none of them have fixed this, I've tried turning off auto-rotate and on again but again nothing happens. This is pretty useless if it's stopping on multiple people for no reason.
Anyone know the script in g-script lite to enable and disable the g-sensor to see if this works as I've used this in the past on one of darkstone's builds but don't have the script anymore?
Thanks

RenaissanceMan said:
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
Click to expand...
Click to collapse
I'm using Sergio's core droid V0.8 desire wich is very stable and the camera is working, but I tried many others and I never had any BSOD's.
Can anyone tell us where the G-sensor hardware is located in the HD2? there should be a logical explanation to this problem.

Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.

AvRS said:
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
Click to expand...
Click to collapse
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.

RenaissanceMan said:
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
Click to expand...
Click to collapse
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.

AvRS said:
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
Click to expand...
Click to collapse
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!

Up .......

RenaissanceMan said:
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Click to expand...
Click to collapse
I've never seen any files called that on my device so what I'd try is first make a backup of that file then rename it to sensors.qsd8k.so and then restart. All of my files in that folder are all .qsd8k. With some builds/kernels they name things differently and say to rename according to your device for example when you get lights.htcleo.so which you need to rename to lights.qsd8k.so to make it work. If this doesn't work definitely try a different build to see if it's working in that and if it is try going back to your one you're on now and maybe it'll wake it up again.

Hi, I have same problem with sensors on my HTC HD2.
A downloaded Sensor Test app from Marketplace and it give me this values:
Accelerometer (BMA150)
Accel X Waiting... M/S
Accel Y Waiting... M/S
Accel Z Waiting... M/S
Magnetic Field (AK8973)
Mag X Waiting... Deg
Mag Y Waiting... Deg
Mag Z Waiting... Deg
Orientation (AK8973)
Az Waiting... Deg
Pitch Waiting... Deg
Roll Waiting... Deg
Proximity (CM3602)
Near/Far Waiting... Prox
Light (CM3602)
Light Waiting... Lux
Battery
Charge 94 %
Temp 35 Deg
Voltage 4.1 V
It looks like a problem with some communication bus or something like that. Can someone try Sensor Test app and check values.
All of these sensors are not working and I dont know how to fix them
Last edited by pawlish; Today at 02:57 PM..

I'm in the same boat as yall. Sensor works in WM 6.5 and even Windows Phone 7, but still no Android. I have also noticed that the proximity sensor isn't working as well. Do yall think the 2 might be related?

[Q] Andriod -_-

Every Andriod build I try always has some BIG issue for me.
Mjeey's builds don't hardly work, HD 3.7 start force close all my apps, Revolution had Way to many problems, That red one with the numbers wouldn't get past the lock screen, The sense one didn't have any internet.
Dark stone dosen't have Navigation
Nexus build, just deteriated and started force closing, soding me all the time.
I want a build that works, 3g,wifi,Has to have Navigation, Camera, etc
I'm currently running Chunky rom the dark one
Radio 2.15.50.14
I've switched radios roms, reformated card between androids, tasked 29 and everything can someone please give me some advice

Jsnipe4 said:
Every Andriod build I try always has some BIG issue for me.
Mjeey's builds don't hardly work, HD 3.7 start force close all my apps, Revolution had Way to many problems, That red one with the numbers wouldn't get past the lock screen, The sense one didn't have any internet.
Dark stone dosen't have Navigation
Nexus build, just deteriated and started force closing, soding me all the time.
I want a build that works, 3g,wifi,Has to have Navigation, Camera, etc
I'm currently running Chunky rom the dark one
Radio 2.15.50.14
I've switched radios roms, reformated card between androids, tasked 29 and everything can someone please give me some advice
Click to expand...
Click to collapse
MDJ's builds work perfectly for me, 3g, WiFi, Navigation & Camera all work for me.
They all worked on Darkstone's too for me.
My advice would be stick with WinMo if you're not happy with what's on offer

Get mattc's 1.8 and hastarin 8.1. With Chucky ROMs this runs smooth like butter. And everything is working.

sounds like force close issues due to trying to restore data from other builds? or leftover data being picked up off the card causeing corupted files.
all the builds you mentioned are pretty reliable builds, that leads me to belive issues lie on your end.
if it was me?
id do a full format, not the quick format in windows. better yet, do it in gparted! a linux machine will do a much better/cleaner job.

Help with Telstra HD2 & Android

hey guys. ok ive searched and searched and gone through thread after thread to try and find a working android build for an AUSTRALIAN TELSTRA HD2.
im still using the phone on the telstra network and have yet to find a rom/radio/android combination that works.
so far most ones ive tried have the problems where i cant answer half of my calls since the screen was so moody or other ones the battery would drain in just a few hours.
i keep hearing that mdj's latest desire hd build is fantastic so if anyone has a good combination of a rom + radio + android build that would work for my hd2 then i will love you forever!!!

Hi,
I have a t9193 as well but first thing I did was flash a custom rom.
I am using Dutty's v9 on the windows mobile side and Mdeejay's 4.3 desire hd on the android side. It works fine but it needs a little time to get going. Also, you will need to set your apn info manually in Android so take note of it in windows. I am using the latest radio 2.15.50.14 without problems. T9193 is able to support most roms out there contrary to the t-mobile version.
Miri's v25 on htcpedia.com also works great.
Good luck.

darrengladysz said:
Hi,
I have a t9193 as well but first thing I did was flash a custom rom.
I am using Dutty's v9 on the windows mobile side and Mdeejay's 4.3 desire hd on the android side. It works fine but it needs a little time to get going. Also, you will need to set your apn info manually in Android so take note of it in windows. I am using the latest radio 2.15.50.14 without problems. T9193 is able to support most roms out there contrary to the t-mobile version.
Miri's v25 on htcpedia.com also works great.
Good luck.
Click to expand...
Click to collapse
alright ive put on that combination exactly and it still has a problem where sometimes it DOESNT come back from the black screen when locked. is there any fix for this as its been my main android problem since the beginning T-T

You need to change the radio rom to something that ends in .50. Telstra radio roms seem to end in .51. I use 2.15.50.14 and it seems to work ok.
I'm using MDJ_FroYo_HD_v._4.3_MDJ_S7.5HD with my wm being Cheetah Rom 3.14 base. I've been running this for a few days now and its pretty stable.
Good luck with your Android, gingerbread (Android 2.3), will probably be available soon too, waiting for that...
Cheers....

ultramag69 said:
You need to change the radio rom to something that ends in .50. Telstra radio roms seem to end in .51. I use 2.15.50.14 and it seems to work ok.
I'm using MDJ_FroYo_HD_v._4.3_MDJ_S7.5HD with my wm being Cheetah Rom 3.14 base. I've been running this for a few days now and its pretty stable.
Good luck with your Android, gingerbread (Android 2.3), will probably be available soon too, waiting for that...
Cheers....
Click to expand...
Click to collapse
yeh im using a .50. type radio and STILL having problems its like my phone doesnt want to do android at all and its really starting to frustrate me. almost to the point of wanting another phone. do i need to be doing anything else or doing a few more restarts???

karasu666 said:
alright ive put on that combination exactly and it still has a problem where sometimes it DOESNT come back from the black screen when locked. is there any fix for this as its been my main android problem since the beginning T-T
Click to expand...
Click to collapse
Hi,
I had this issue initially on 1st and 2nd boot or so. Don't forget that Android is run from sd card. You have to give 1-2 seconds to get going and load up the info from the sd.
When this happens, hit the end call button until the keypads light up and wait a few seconds. Make sure your keypad is lit up as it sometimes closes again. You can hit the call button and middle button as well.
Also, make sure that you uncheck auto intensity for display in windows mobile and I set the display time out to 10 minutes in Android.
Here is a trick and use and it seems to work. I let android sit for about 15-30 minutes on first boot to allow it to be stabilized and allow all the syncs to take place (the hd rom actually will download and re-install all marketplace apps - have a look in marketplace under downloads to see this). I then restart it a few times after that and even let it sit a bit to finalize everything. Don't ask me why but this helps a lot. Android seems to get faster each time. You also may want to postpone sync with exchange/outlook and also htc sense until your 4-5 boot.
Lastly, when you first start an application (each time you boot up) there is a slight lag so exercise some patience. After that it is very fast.
Hope this helps. If you want a faster build that is non desire hd based you can try mdeejay evo sense revolution build. It is not as fancy as the hd build but is lightning fast.

karasu666 said:
hey guys. ok ive searched and searched and gone through thread after thread to try and find a working android build for an AUSTRALIAN TELSTRA HD2.
im still using the phone on the telstra network and have yet to find a rom/radio/android combination that works.
so far most ones ive tried have the problems where i cant answer half of my calls since the screen was so moody or other ones the battery would drain in just a few hours.
i keep hearing that mdj's latest desire hd build is fantastic so if anyone has a good combination of a rom + radio + android build that would work for my hd2 then i will love you forever!!!
Click to expand...
Click to collapse
I also happen 2 own an Australian HD2 off Telstra and use both Telstra and Vodafone sims. Check my sig for the Win Rom/ Android combination. It works well for me, I've tried most of Mdj's Android roms as well but have found Sergio's Core Droid to be the most stable. Any of NRGZ28's Windows Roms will work well with Android, give it a go. I also downgraded my radio from 2.15 to 2.12 and that seems 2 work better for me. Hope that helps

My Telstra HD2 is running Android perfectly.
However, I want to watch Foxtel on it but says it doesn't recognise my HD2 as a Telstra device.
It is a T9193 from Telstra, but there must be a setting somewhere that's not right.
Any help would be awesome.
Cheers,
Dev