Database Users

Anyone using CyanogenMod or Desire Rom encounter touch screen problem?

Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en

helloworld1 said:
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
Click to expand...
Click to collapse
happens occasionally, but now rarely (almost never) with the latest cyanogenMod (5.0.3.1) - turn off the screen and turn on fixes it.
i think it will be eradicated completely with the next offical (and cm update)

yes, it is better for me too with CyanogenMod 5.03.01, I feel it is more due to the new .32 kernel

Now that you mention it--yeah, the problem has all but disappeared ever since I flashed CM and now Modaco's Desire. I think I encountered it a grand total of once in two-three days, though admittedly I still haven't spent enough time with the Desire ROM.

I wonder whether the touch screen driver in CM is the same as the one in the official ROM>

No problems at all with Desire image and rarely using latest cyan. It was making my stock unusable.

Ha, id totally forgot about that issue, I havent experienced it at all since switching to Cyan, atleast not that I can remember

I noticed that the alignment/calibration problem has been improved. not perfect...but improved.

I've been actively trying to palm-wrap and tilt the screen at an angle that usually gave me calibration problems on stock. Nothing; touch alignment etc remains perfect. I guess it was a software and not hardware issue after all!

So the CM does not eliminate the problem. I hope google will fix the driver in the source code, or the problem will not be gone.

i have a question, does it fix the 3g dropping/switching to edge problem?

I still have it on cyanogen 5.0.3. Actually quite often and this really annoys me, I did a wipe install.

(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.

[UPD][Tracking] Andriod HD2 Open Issues

Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.

Hi depakjan, This is great, thanks for tracking these issues.

can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.

i think the bsod is fixed with 2.12 radio and above..

Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...

depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem

Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..

Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.

Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.

Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.

badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).

Led Notification is not functioning, especially on Sense build.

backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen

jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2

hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!

Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.

Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy

Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto

Kernel with Sensor Fix?

Hi
I know, was discussed so many times...but because of just this, I'm confused as hell. Whenever my batterycharge is quite low, my phone starts to hang pretty frequently...the touchinputs at least. I noticed, that this happens, when I walked a bit with my phone. So my guess would be, that the g-sensor is overloaded and that freezes the touchscreen. I know, there are Kernels that deactivate the g-sensor, but it's a handy tool for screenorientation. So, is there a fixed kernel which leaves the g-sensor activated but removes the touchscreen-freeze bugs?
Hope someone can help me.
Greetings
NessD

wow ... i didnt know the battery charge has play in this ... i guess ill keep it better beefed up ... thanks for da tip

Its still a mystery to me. Because a lot of people seems not having this issue anymore.... Not me, with the last radio, trying wm roms and several builds. Like you, it is very hard to walk typing a sms. Ok I will not be hit by a car but its still frustrating hehe

Yeah, I just noticed that I get those problems when 2 cases are given: Low Battery Charge (full battery is no problem) AND when the HD2 moves around alot. I get touchscreen freezes then. Either one for it's own is no problem, but both keep producing the freezes.

I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.

No kernels have fixed this yet, some builds claim "no g-sensor freezes" but they do. (or at least they do for me, i'm not doing something wrong am i?)

mmduluth said:
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
Click to expand...
Click to collapse
Hastarin r8 does not work for me...using Hyperdroid v1.7, can't get data to work...

Experimental kernel released that (should) fix this.
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140

I can confirm it finally works. Today is a great day for the community

Screen doesn't work in the cold (Android ONLY)

When running my phone with android, the screen gets really wierd in the cold. It won't register all my presses, sometimes acts as though i'm holding a letter down, and is just generally very ****ty. I've used a number of different android builds, all to no avail though in WM6.5 it works 100%.
Any potential fixes? It boggles my mind as to how a change of operating system could effect the utility of the screen in varying temperatures.
Just wanted to make sure the dev's knew about this so maybe they could figure out a way to fix it.

yes, I have experienced this problem as well. Try the on-phire build, my friend is telling me he is experiencing the touch screen problem less frequently.

That's been a known and cooking issue with hd2s screen since it was released. I'm not sure why you'd have problems in android and not winmo.
Sent from my HTC HD2 using XDA App

Happens to me too on all builds i have been using. But using the kernel from hastarin, it has yet to happen.
http://forum.xda-developers.com/showthread.php?t=787588
Just no working camera for me now.