Database Users

[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

Screen becomes over sensitive (reponds without touching)

Part of my screen becomes over sensitive after I use my streak for more than 5 minutes. It registers keys when I hover my fingers over it. A restart temporarily fixes this issue. I had this issue even when I was using 1.6 (now upgraded to 2.2). Is anybody facing the same issue? I tried investigating into it with no luck ..
Also I am not sure how to replace this device since I bought it from craiglist...I m still hunting the person who sold me streak..

I've noticed that happens to me too sometimes. Usually not that big of an issue.
Sent from my Dell Streak

Have you tried touch calibration as pointed ut here;
http://support.dell.com/support/top...&s=gen&docid=870C8DC7568D4DDFE040AC0A64E93F03
/Per

I have the same issue - it is seriously affecting my typing speed. I have tried a screen recalibration to no avail. Good to know it happens on the stock OS, as I didn't notice it when running 1.6 and have since installed DJ_Steve's 2.2 (v 1.5.1). I'm interested in any news regarding this issue.

Yup dude, the screen calibration works !!! Thanks a lot...

Slider unlock sometimes doesn't work with incoming call

Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?

Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.

I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?

question... are the phones plugged in to a wall charger when this happens?

Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).

DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place

ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).

cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there

My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers

I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.

Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.

problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel

Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App

swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago

I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?

Touchscreen problem on CyanogenMod 9 by sfc3001

Hei!
I am new to xda forums so please don't go crazy on me if I don't do something good in explaining this.
1st of all - i had a motorola milestone 1 before with CM7.2 so i have just a bit of experience with CM ROM.
2. Now (bought a few days ago) milestone 2 with 2.2.2 android and flashed (not sure if i used the correct term) it through Motorola Software Update (via USB) to GingerBread 2.3.4 official.
3. After searching the forum i found that CM9 Nightly (by sfc3001) reached a final release being more stable than buggy for Milestone 2.
4. after rooting my device with superoneclick -> I flashed CM9 using Caesarivs tutorial: http://forum.xda-developers.com/showthread.php?t=1758271 .
5. So after installing CM9 chinese kernel (i don't know if it's a good one - i would have prefered the EU one but everyone wrote on the forums that CH is less problematic) i started using the device properly for a few days.
Problem appeared at first with the brightness (automatic) - in direct sunlight it does no go on full brightness.
But now (since yesterday) when I touch one spot of the screen it registers multiple touches on the same vertical line (clicked the Pointer Location and Show touches box in the settings->developer options menu to see what is wrong with the screen).
Another problem with the touchscreen is that when I am scrolling (going up and down with the finger on the screen) it registers multiple touches also instead of just seeing one touch going up and down (sometimes opening apps without me wanting it)
I have to say that I used the stock android for 2 days and did not have these problems.
Could someone please help me? Maybe I followed the wrong steps in installing.
Thank you.
P.S. - I already did a factory reset once and reinstalled CM9 Chinese again - but after a few hours the problem starts.
P.S. 2 - My Milestone 2 is overclocked to 1220 mhz (58vsel) from bootmenu.
L.E. another problem with scrolling is that is a bit slower than it was on GingerBread. And sometimes when i try to scroll left/right it scrolls till half of the page and then goes on the opposite page (e.g. 1 - 2 - 3 > i try to go from homescreen 2 to homescreen 3 - goes halfway to homescreen 3 and then bounces to homescreen 1 when i take my finger from the screen) - this happens also when I try to scroll in different apps up/down.

pnkye said:
Hei!
I am new to xda forums so please don't go crazy on me if I don't do something good in explaining this.
1st of all - i had a motorola milestone 1 before with CM7.2 so i have just a bit of experience with CM ROM.
2. Now (bought a few days ago) milestone 2 with 2.2.2 android and flashed (not sure if i used the correct term) it through Motorola Software Update (via USB) to GingerBread 2.3.6 official.
3. After searching the forum i found that CM9 Nightly (by sfc3001) reached a final release being more stable than buggy for Milestone 2.
4. after rooting my device with superoneclick -> I flashed CM9 using Caesarivs tutorial: http://forum.xda-developers.com/showthread.php?t=1758271 .
5. So after installing CM9 chinese kernel (i don't know if it's a good one - i would have prefered the EU one but everyone wrote on the forums that CH is less problematic) i started using the device properly for a few days.
Problem appeared at first with the brightness (automatic) - in direct sunlight it does no go on full brightness.
But now (since yesterday) when I touch one spot of the screen it registers multiple touches on the same vertical line (clicked the Pointer Location and Show touches box in the settings->developer options menu to see what is wrong with the screen).
Another problem with the touchscreen is that when I am scrolling (going up and down with the finger on the screen) it registers multiple touches also instead of just seeing one touch going up and down (sometimes opening apps without me wanting it)
I have to say that I used the stock android for 2 days and did not have these problems.
Could someone please help me? Maybe I followed the wrong steps in installing.
Thank you.
P.S. - I already did a factory reset once and reinstalled CM9 Chinese again - but after a few hours the problem starts.
P.S. 2 - My Milestone 2 is overclocked to 1220 mhz (58vsel) from bootmenu.
Click to expand...
Click to collapse
Please refer to step 4 in my turorial, it says you must use EU kernel if you are on 2.3.6
4. For CM9 download latest European GB Kernel version this thread: http://forum.xda-developers.com/show....php?t=1623385 and latest ICS gapps from http://goo.im/gapps/ and put both zips on your SD Card
Click to expand...
Click to collapse
That should fix your issues

Caesarivs said:
Please refer to step 4 in my turorial, it says you must use EU kernel if you are on 2.3.6
That should fix your issues
Click to expand...
Click to collapse
OK - I will try that right now and come back with some news later, thank you very much!

pnkye said:
OK - I will try that right now and come back with some news later, thank you very much!
Click to expand...
Click to collapse
CH kernel is for Froyo... use EU Kernel for GB

Caesarivs said:
CH kernel is for Froyo... use EU Kernel for GB
Click to expand...
Click to collapse
Well i did what you told me and yes everything works very good for now, except:
1. a few random restarts (and overheated upper part of the case at those times, so i taught that might have been the cpu so i increased max vsel from 56 to 58 at 1,2ghz overclock)
2. but the touchscreen still has the same problem (multiple touching) if i use my phone while plugged for charging, and the problem persists for a few minutes after i unplug it.
So what could that be?

pnkye said:
Well i did what you told me and yes everything works very good for now, except:
1. a few random restarts (and overheated upper part of the case at those times, so i taught that might have been the cpu so i increased max vsel from 56 to 58 at 1,2ghz overclock)
2. but the touchscreen still has the same problem (multiple touching) if i use my phone while plugged for charging, and the problem persists for a few minutes after i unplug it.
So what could that be?
Click to expand...
Click to collapse
That's a known bug for this phone (crazy touchscreen while plugged), it happens even with stock firmware (It happened to me before even creating an accound here )

Caesarivs said:
That's a known bug for this phone (crazy touchscreen while plugged), it happens even with stock firmware (It happened to me before even creating an accound here )
Click to expand...
Click to collapse
Oh., well thank you then for the information.
Too bad that no one can do something for the problem but I'll work something out through the bug.....

[Q] Motorola Defy touch working wierdly

While on the stock ROM the defy the touch did run properly and after rooting initially it worked fine.but now it is giving problems.
Points on touch click automatically.
while typing on the keyborad sometimes without doing anything the keys starts pressing on own.
While playing games sometimes i face the problem.
so conclusion the touch is giving wierd problems when the above problems are faced i need to turn off the screen(not turn off the phone) and turn it on again to make things work properly.
I have used CM9 and WIUI v4 ROMS and both giving the same problem.
Is it a problem with the ROM or something wrong with hardware.
Is there anything to solve this problem...
Kindly help

Iam also having same problem

can anyone advice or provide link to the post where i might find a possible solution.My defy is working awesome except this touch issue.

Samuel7k said:
can anyone advice or provide link to the post where i might find a possible solution.My defy is working awesome except this touch issue.
Click to expand...
Click to collapse
I am also faced this issue during rainy season. But now it works perfectly. Lightly Heating the front screen using hairdrier was solved it for few days or few weeks.
But last 3 months i am not faced this issue becouse atmospheric temperature arround 35 to 40 now! !!
Sent from my Motorola Electrify using Tapatalk 2