Database Users

Walking dead.... I can't be the only one

Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App

try the desire v5's zimage, no freeze at all

Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.

might be a screen rotation issue

Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..

miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.

I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App

when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on

I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...

Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.

I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?

I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.

hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all

Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App

The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App

shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...

Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan

Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.

Try to calibrate the g sensor

Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App

Which is the fastests Anroid Port

Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall

thatg said:
Looking to stick an android rom on my hd2, wondering if you guys can help me out looking for one. which is this smoothest running and has the least issues. whether its 2.1, froyo with or without sense. thanks yall
Click to expand...
Click to collapse
Any build that I have used from Darkstone has been smooth and fast. You can download the latest "clean" froyo build or the "sense" themed froyo build here:
http://gamesquare.co.uk/froyostone.htm
Imho, the clean froyo build is a bit faster.

i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device

pbleonidus said:
i used the max energy co0kie energy ROM for win mo, used hardspl 3, the latest radio, and used the latest froyostone sense build, and the jmz dual boot .cab, everything is working pretty good... when i turn the phone on, i can boot co0kie energy win mo, or android 2.2. now im pretty happy with my device
Click to expand...
Click to collapse
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.

ryan562 said:
awesome. your voice calling and speakerphone are working? i almost have the same setup as you except i'm using chucky's rom. voicecalling works perfectly. no echoes no robotic voices. i may try energy rom some time this week although i like chucky's + gtx white theme.
Click to expand...
Click to collapse
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...

pbleonidus said:
i havent been able to try any sort of calling on the android os yet, but everything works great on co0kie energy win mo os...
Click to expand...
Click to collapse
cool, let me know if the voice calling works.
btw, here's a thread over on the android hd2 development section consisting of a growing a list of the fastest and most stable build+ rom combinations including a running list of what does/doesn't work on some builds
http://forum.xda-developers.com/showthread.php?t=749110
this should help the OP of this thread as well.

calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)

pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
i'm experiencing the same exact thing but the froyostone dev has stated that this is a known issue and it will be fixed upon the next build

would the next build the fix is in be the agust one, or the next one as of todays date? because yesterday the agust build came out, and i beleive that is the one i have installed, is there a way for me to check which release date i have?

Shubcraft cm6 v1.2 is very fast and stable and 98% off the things work on it...and i think the theme is pretty neat...
Sent from my HTC HD2 using XDA App

pbleonidus said:
calls sound great, speaker phone works, camera works, camcorder works, bluetooth turns on (havnt tested any pairing yet) flash works, everything seems to work execpt the folowing:
flashlight only works on brightest setting
and when i put the phone to sleep, the keypad led lights stay on, but i read from froyo on a different build that this happens to some people, it could also be a problem with the .cab i installed on win mo, i have it set that whenever win mo is being used/ doing something, the leds stay on, instead of shutting off after 10 seconds, so it could be win mo still is doing some task, like running sense (i have the sense version of android) and thats why the stay on... ill try to figure out the problem soon. (and this doesnt happen when running win mo...)
Click to expand...
Click to collapse
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all

Before you boot into Android make sure the bottom keys aren't lit. That's keep your keys from turning on at all in Android.
Sent from my HTC Desire using XDA App

d0ug said:
I would suspect that whatever the CAB is you have installed probably changes a register (not registry) in the micro controller that controls the keypad and its lighting. As long as this microcontroller doesnt get a reset signal or power loss it is going to keep that register set even when booted into android.
As far as i know when using HARET WinMO is no longer running, but please correct me if im wrong, ive tried to find some detailed info on how HARET works, but haven't found much to date. I always wondered if android was truly running all on its own, or if HARET was something like a vmware translating android calls to winmo api calls with winmo still running the show under it all
Click to expand...
Click to collapse
Yes, haret completely shuts down winmo and boots linux. There is nothing else running when you're using android.

Dual Boot
Can someone help me? I am trying to dual boot but it is not working. I read somewhere that you need to change HKLM/init launch 52 to Launch 62 but there is no Launch 52 on my phone.

(Possible solution) Freezing Issues

hardik119 has found out that going to account & sync and disabling background data has stopped his device from freezing and it has also stopped mine afer 1 hours use. Before it was freezing about every 5 minutes. With doing this I have also disabled setCPU, auto screen rotate and removed gsensor.dll in windows mobile. Please try this out and respond if this has worked for you because maybe we can get a perminant solution. Thanks and also thanks to hardik119 for his extensive testing and possible solutions he is finding all the time Android is usuable on my device hopefully will be for everyone else aswel. Also sorry for opening another thread but there doesn't seem to be any action on hardik119's original thread.

maybe suggested solution works...but...wot is android without data background?

If you disable background data, doesn't that like stop gmail and weather and such updating automatically??

leginag said:
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
Click to expand...
Click to collapse
Yep...sure does..

the_scotsman said:
Yep...sure does..
Click to expand...
Click to collapse
As has been suggested above...that is kind of /fail.
I'd prefer to live with the occasional few second freeze than not have constant updates.

I applied the RC 7 and my screen freezes are gone. Using this image with mattc nexus 1.0 rom,
http://forum.xda-developers.com/showthread.php?t=756513.

Pretty sure he's just looking for testers to confirm the association. That way developers can narrow down the cause of the issue and possibly fix it. Stop whining about the "solution" he suggested.

Touchscreen freezes still exist

No freezing issues as long as you get the right WM build and android port. Mine is 100% freeze free thanks to the awesome devs here at Xda.
I have auto screen rotate on and still no freezing or SOD. I am using Darkstone's 2.1 build full time now.
Fyi.
Sent from my Hd2 using XDA App

Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)

Thanks for the tips currently using maths 1.5b Rom with 23rd kernel
Hspl3 & radio .12 aswel also tried with calibration on the g sensor in winmo and also deleting sensor.dll also using energy light but have also tried with Miri light the only build I haven't tried so far is the one you mentioned so will give it a go. Thanks
Sent from my HTC Desire using XDA App

Hi I can confirm the disable background sync fix works for me.
Running
- Android O.K. v2.6 [Kumars Leo Touch Premium]
- Mattc 1.6
- Radio 2.12.50.02

LondonTownGuy said:
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Click to expand...
Click to collapse
where to fing the original zimages not the overclocked

touch screen freez reason
I nenarly identified the reason of touch screen freezing ,,it is possibly in the touchscreen kernel ,download figure race from market and the touch screen fresez due to random pess of touch screen with both hands ,I think this is the main problenthl

hoss_n2 said:
where to fing the original zimages not the overclocked
Click to expand...
Click to collapse
http://oe.netripper.com/files/htcleo_autobuild/
23rd august is very stable, you also get usb sinc working and HTC sync.
You need to download the corresponding modules to extract the BCM and TUN files for wi fi to work.

[Q] G-sensor of HD2 doesn't work when installed andriod

My G-sensor function of HD2 can't use after installed Andriod. I changed many other ROM versions to try if its available ,but still it doesn't work. The game teeter show that can't find G-sensor facility in your phone and will quit..
Could you please help me and suggest me some solution, it depressed so much.
My radio version is 2.15.50.14.version FRG33
only HTC, not T-mobile.
THANK YOU!

me too ,it diever me crazy!!!
help!!!!!!!!

Try Calibrating the G-sensor in windows mobile, maybe that would work

it does work in WP6.5 ,but when I switch to Andriod ,no matter which version,system can't find G sensor... I depress me so much,cus it seems like a brick without gravity function.

Why dont you post which android version you are using and or ask for help in that versions thread?

I have the same problem, I've done all that I was able to do but nothing happened..
G-sensor works in WM but doesn't into android.
HTC HD2 LEO
Radio : 2.15.50.14
excuse my poor english

Well I am using the T-Mo US HD2 and have HSPL-ed it and put Android on it using the Evo Carbon Rom from Motoman, and the G-Sensor Calibration works perfectly to set it, and Teeter works flawlessly as well (Just tried both after reading the thread).
I would have to agree with the above postings, you might want to look at the threads of the roms and see the whats working, whats not, or check to see if a app you installed might have corrupted or changed the default app. But if you have tried multiple roms and still have this issue, and not in WinMo, I would have to speculate you didnt clean your SD card of prior files.

same problem here. need help!
I got the exact same problem. mine is a tmo-us hd2. g-sensor works fine under wm no matter if it's stock rom or custom roms. cannot detect g-sensor when switch to android. tried several different android roms resulting the same.

btw, i did format my card every time before installing new android rom. when i put my card in my friend's HD2. g-sensor works fine under android on his phone. clearly, something is not right on my phone, but everything works fine under wm.

Me TOO ~~~~~~~~~

i have the same damn issues at first i was using a custom rom then i stock back my leo phone then try installing android using MOTOMAN234 EVO CARBON REMIX V0.5 but still no G-SENSOR !!! I Dont see hows its the phone when evrything works right when im in windows mobile DOES NE ONE KNOW HOW TO FIX THIS???

Thanks a lot for your suggestion ,Let me try if it available on my phone.

UP please ! I'm going to be crazy.. Same issues :'(

I also have the same problem on my replacement TMOUS HD2. Both G-sensor and light sensor is not working on Android but works flawlessly on WM. On the original HD2 I didn't have any of these problems. Did you all recently purchase the HD2 or got a replacement of it? Anyone knows if there is a recent change of hardware in the HD2? I got my replacement right before Christmas.

Same problem here its definitely not SD related as I'm running from nand now and still nothing has anyone figured it out yet.........

Is there any developers reading that could possibly offer us their knowledge? I just don't understand why it doesn't work for such a small handful of users,
Sent from my HTC HD2 using Tapatalk

whynot66 said:
Is there any developers reading that could possibly offer us their knowledge? I just don't understand why it doesn't work for such a small handful of users,
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Same here. Looks like we are not the only one who has this problem. Hope there is a developer can notice this problem.

The compass on wm 6.5 doesn't seem to work either on my replacement TMUS HD2 am I the only one?

Need Help
Could someone (a dev) please take notice of this thread and maybe take some time to see what the issue might here? We would also like to enjoy fully functional Android on our HD2's
Would be much appreciated...

giurca said:
Could someone (a dev) please take notice of this thread and maybe take some time to see what the issue might here? We would also like to enjoy fully functional Android on our HD2's
Would be much appreciated...
Click to expand...
Click to collapse
UP i hope some one can see

[HELP] Weird Accelerometer problem in HD2. Please Help!

I purchased a used HD2 a few months ago which was preinstalled with Android 2.1 Sense. Everything was working perfectly (also the accelerometer). Then, after a few days of purchasing the touch screen digitizer was not working (i mean, no touch), so I gave it for repair and it was fine. But, the accelerometer was not working on the Android build (Nexus HD2 ICS v2.1 NAND) I was using (previously it worked before repair). So, I installed WinMo just to confirm and found that the accelerometer was working fine. Then, I installed WP7 Rom (HD2o) and again the accelerometer was working fine. I booted Android from SD (ParanoidAndroid) and the accelerometer was not working. I tested a few more builds and it was not working.
As it is working in Windows, I guess it is not hardware issue.
The Great folks at XDA, Please Help!
I think this is an Android related problem, so I posted here.

So how can we help you? Most of people got working accelerometer out of box on android, so don't get too fast assumptions, it MIGHT be hardware issue(it's more complicated than it's working or NOT)
As for help, try using several kernels, start especially with stable ones, like Tytungs then go off for another kernels.
By this service, are you sure they havent replaced more parts, like motherboard etc? What version of radio and HSPL have you used before and are using now?

As I mentioned, the Accelerometer was working PERFECTLY in WP7 and Windows Mobile.
What is the issue with Android ?

netchamp.faris said:
used HD2 a few months ago which was preinstalled with Android 2.1 Sense. Everything was working perfectly
Click to expand...
Click to collapse
So I'm assuming it WORKED in android. Try using GPS status app or Tricorder, they show info about accelerometer data, then you'll know if it's working partially or not.
Oh, there is a chance that in repair service they replaced some parts in your HD2 with china counterfeit and drivers are not working correctly under android. But hell knows.
Check if it's working anyway.

actually, you're not the only wich have that problem, in this POST, much people, including me, are trying to do work the g sensor

berseker1 said:
actually, you're not the only wich have that problem, in this POST, much people, including me, are trying to do work the g sensor
Click to expand...
Click to collapse
Well, its not a g-sensor calibration problem.
Its just that the accelerometer doesn't work in any of the android builds.
Sent from my HTC HD2 using xda premium