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

INFO: BATTERY AND LIGHT or PROXIMITY SENSOR

i posted this in the mdjeey thread but i don't if it is of any use i will repost it here
" i thank mdj for his work , this morning i noticed something that could explain the eratic battery drain of our device , when i was filming for a friend some configuration instructions ( which is by the way , by far simple than writing it ). the proximity sensor emits flashing lights permanently ( not seen by eye but only with the film) thing i could not reproduce on wm.
my radio is the latest one , my wm rom the latest of dutty, my android build the mdj sense hd 4.4 with 7.7 kernel.if someone treated the subject before excuse then if not, has somebody noticed this , mdj what do you think about it ?
edit :http://www.youtube.com/watch?v=BkyYFLUjzaM and http://www.youtube.com/watch?v=M1hdqIFzquw "

You just might be on to something here...
I just tried this myself with the built-in iSight of my iMac. Apparently the proximity sensor is an infrared sensor, which uses ir light pulses to calculate distance.
Within Android it starts emitting pulses as soon as you unlock the phone. It stays pulsing until the phone falls asleep. So, that I can confirm.
Within Windows Mobile (see my WM ROM in my signature), it doesn't show up. However, I noticed, that my proximity sensor doesn't work anymore in WM. I don't use WM anymore, that's why I installed a minimal build.
Could someone check with a stock ROM when the proximity sensor is working (just keep it in front of your webcam to check). I suspect it only works when you're using the dialer, or when a call is in progress.
If the devs would be able to limit the activity of the proximity sensor to the dialer or use it in conjunction with the g-sensor, it might decrease the drainage.
Sincerely,
Mac

I just tried for myself and I can also confirm this. Build is NexusHD2 v1.6 by tytung. Kernel hastarin 8.1. Also, this is not visible by naked eye but is visible when filmed with camera.
update.
Just updated to v1.8, kernel hastarin 8.5.3_oldcam and same behavior occurs. In meantime I tried WM and sensor is offline until call is established

dusko_m said:
I just tried for myself and I can also confirm this. Build is NexusHD2 v1.6 by tytung. Kernel hastarin 8.1. Also, this is not visible by naked eye but is visible when filmed with camera.
update.
Just updated to v1.8, kernel hastarin 8.5.3_oldcam and same behavior occurs
Click to expand...
Click to collapse
Do you have stock WM ROM to check it's behaviour?

No. Energy cookie rom here. As I said before, in WM this "IR blinker" is off until I establish call. then goes off again after call is finished.

That is a really good catch and I can confirm that my HD2 in android also does the same thing. When I press the end call key for it to go in standby the light goes off as soon as I press the end call button to wake it up it starts flashing again.
Edit: I should also note that I'm using MDJ 4.3 Android build, and Windows Mobile is stock from TMOUSA

I've seen this mentioned before. I hadn't thought of using my webcam to view it.
I'm unsure if this is a bug with the kernel, or a side affect of the way Android works.
I've noted it on my list but unfortunately kernel development seems to have stalled lately and I'm not sure the main devs are even looking at my list.
Hopefully things pick up again in the new year.

I think it is the same chip that handles light and proximity sensing, called cm3602, so as long as you have auto backlight enabled, you will see the blinking.

drizztje said:
I think it is the same chip that handles light and proximity sensing, called cm3602, so as long as you have auto backlight enabled, you will see the blinking.
Click to expand...
Click to collapse
i am not an expert in the domain of electronics, so i'll take the thing about the chip for granted, but the thing about autoblacklight , i don't think is the answer cause the autoblacklight in WM is on and that blicking thing does not happen !
and my purpose was not to incriminate this or that , but to say just that ,that thing could be the reason why the battery drains so fast on android builds (other than the permanent internet connection )

sbibif said:
i am not an expert in the domain of electronics, so i'll take the thing about the chip for granted, but the thing about autoblacklight , i don't think is the answer cause the autoblacklight in WM is on and that blicking thing does not happen !
and my purpose was not to incriminate this or that , but to say just that ,that thing could be the reason why the battery drains so fast on android builds (other than the permanent internet connection )
Click to expand...
Click to collapse
I didn't make a hard statement, I just said what I think, so you should not take it for granted. I didn't test it extensively in WM, but I saw the blinking in WM for a short period before EBL started android boot. Are you 100% sure that the blinking is not there in WM even if the light sensor is working? I tried to find some info about cm3602, it seems to be a dumb device without any configuration interface.

check dmesg if it is full of "intr_status=0x02".
The problem is that when you use toolchain other than 2010q1 (http://www.codesourcery.com/sgpp/lite/arm/portal/release1293) ,
proximity sensor driver doesn't work properly. After its first activation, it just doesn't stop. It continuously polls in an infinite loop. That's why you see those blinkings which are probably infrareds. It was causing too much current drainage (65mA) for me even in suspend. Now, i used the above toolchain to compile the kernel and it is around 10mA in suspend.
So; if you are compiling your own kernel, use the above toolchain. If you are using someone else's kernel, tell him to use it.
EDIT: I realised that this isn't the problem that you observe, this was just another problem that I faced.

this need to be a sticky or in dev section.....imo

i saw a video of how proximity sensor work on a HD7
http://www.youtube.com/watch?v=wpvaEAJguWA&feature=player_embedded

vua777 said:
i saw a video of how proximity sensor work on a HD7
http://www.youtube.com/watch?v=wpvaEAJguWA&feature=player_embedded
Click to expand...
Click to collapse
Our problem is, proximity sensor is running even if there is "no call". It should be online only during the call for power saving purposes.

dapoharoun said:
this need to be a sticky or in dev section.....imo
Click to expand...
Click to collapse
+1 on this

Seeing this problem in miui builds when getting ~60ma standby

Should I be able to see it when recording with a regular hdv camcorder? I tried it but don't see the light.
Edit: My mistake, it is there just very small and I had to zoom way in. It's on as soon as the screen turns on and stays on. It does turn off though when the screen goes off. It does explain that I get good standby power drain but when typical useage time is not nearly as good as winmo.

oh man .. this is really good stuff .. if this is true .. and this really solves the high battery drainage on andriod(on HD2) .. i would be so damn happy .. no reason to sell my HD2 and get the Desire HD anymore.
thanks to threadstarter

I couldn't find anything to disable the proximity sensor but I found a small program that reports the sensor readings.
When I put my finger over the sensors, the light sensor takes about 2 seconds to go from 160lux to 10lux, while the proximity sensor changes instantly from far to near.

the blinking does not make the screen react more quickly when in call

[App] Power Switch - screen off by closing your case

Guys, im the developer of Power Switch, an app that switches off your tablet's screen when you shut the case.
The main thread can be found here:
http://forum.xda-developers.com/showthread.php?t=1277712
Ive had reports of problems with the tab's light sensor, so would appreciate some debugging feedback.
You can use the lite version to test, it has all the features, but just wont save as much juice.
Thanks in advance. Feel free to reply here or in the main thread, i read both regularly!

Do you guys not have a light sensor or something?

ftgg99 said:
Do you guys not have a light sensor or something?
Click to expand...
Click to collapse
Yes we do. Maybe if there was some incentive to be your testers, like a free full edition, you might get some to actually be your "guinea pigs"

It works, but it will be much better if we can have a locking sound...

l3enjamin said:
It works, but it will be much better if we can have a locking sound...
Click to expand...
Click to collapse
Oh wow, thats a great idea, never thought of it... i will definitely add this in the next release.

Almost done!

Updated, added screen locking sound

I just ordered a case, so I will gladly test this out once I receive it.

Just to let you know, I did try the full version of your app, but ultimately refunded it. It's a great concept, but just didn't work well on my A500. I don't know if our light sensor sucks or what, but the app wasn't detecting the cover being closed.

Anyone else having problems? Problems not related to not reading the instructions?

I'll try again with the Lite version, and see if I can configure it better. I did read the instructions, maybe I was just too quick to dismiss it.

I tried this on my Acer and the Acer cover, but didnt seem to work. Also tried the lite version. I did play around with the settings abit but still nothing. Sorry

Hey I have a suggestion. I apologize if this is already a feature as I did not see it in the other thread. But if you're able to trigger screen locks and sounds and such, why not also add the ability to have it turn off/on wifi and/or 3g?

Interesting... i will look into it, thanks!

Any issues to report?

Anything to report?

[Q] Proximity/light sensor turns of my screen

Hi!
Ive had a problem with the screen turning of, during calls only, for a couple of months. I think it happend somewhere in July/August.
Now, this question have been asked but there has been no answer that solves this.
There is a solution for Desire HD http://forum.xda-developers.com/showthread.php?t=951858.
I have tried the Proximity screen off http://forum.xda-developers.com/showthread.php?t=624206 for the HD2 but that does not deal with my problem, it did not work for me.
The problem only occurs during calls, the screen shuts of no matter if Iam close to it or not.
The screen does not shut off if I plug in the headset before/in the call and also if there is very very much light before I answer/make a call to the time where I hang up/the other person hangs up.
The screen does not wake up for along time after the call has been ended, unless I put it very very close to a light source ( LED does not work so good, light bulb would do the trick),or the usb charger. If I plug in the headset after the call has ended, the screen is till turned off.
I only have this problem when Iam in android. I have been using AmeriCanAndroid ever since I got the phone in May.
Regarding the Proximity sensor off, I made about 90 different setting combination, Screenoff triggered/not triggered with lockscreen delay immediately/several minutes (CM7 settings) with different values when the screen is covered/uncovered with Advanced task killer on/off.
No matter what I tried the result was either the same or worse.
The interesting thing I found out was the screen (at least for the first seconds) turned off each other time, i.e did not shut off for the first ~10 sec, the next call it shut off immediately.
Is there someone who could create an app/setting for the HD2 so that whatever reaction the phone gives when plugged to charger/headset, regarding the sensor(s), but without actually connecting it, would be a life saver.
This problem is very annoying when Iam in a call and want e.g use the dial/check messages/check the time.
Thank you

Go to your settings, and look for something dealing with your proximity sensor

GSM4ever said:
Go to your settings, and look for something dealing with your proximity sensor
Click to expand...
Click to collapse
Thanks for trying to help me, but I have checked everything on the phone.
Anyways, I think this problem is with the proximity sensor because the light sensor seems to work just fine (automatic brightness/backlight settings is responding to the amount of light)
Thanks!

Default settings on CM7 WITH TYPHOONS roms does not have this problem. Perhaps re-create system since it is same since may. Fresh install and all should be well.
Otherwise check for dirt or finger grease smudging over the proximity sensor.
Used to have this problem too on typhoon. Task29 and starting from scratch solved the problems.

Thanks for your reply!
But I dont know anything about TYPHOON roms, and I dont have a reason to change from americanandroid except for the proximity sensor problem.
Iam writing this in hope somebody can include an app or a setting for the HD2 so one can shut off the proximity sensor, I think that would be the best an easiest solution.

Still suggesting you might wipe everything. When I had issues appearing, I started fresh and it fixed it 99% of the time.
Backup your stuff first if needed, then install the newest American Droid and start from scratch.
You might do a nandroid backup before, then if a fresh install doesn't work, you can restore back right before you backed up.

I have the same problem & I couldn't fix it!
using all the sensor monitors in the Market I can't ge any readings from the light & proximity sensors!
in "Phone tester" the sensors read:
Proximity = Near
Light = 10.0 lx
This for covered & uncovered phone - near or far - dark or light!
I'm using: AmeriCanAndroid 110711(sd)
Radio: 2.15.50.14
I think the file /system/lib/hw/sensors.htcleo.so is the problem.

wh_hsn said:
I think the file /system/lib/hw/sensors.htcleo.so is the problem.
Click to expand...
Click to collapse
The reason why removing that file, fix the problem, is because you basically tell the system that there are no sensors at all.
Now that would be a good enough solution for me, only downside is that the sensor wich tells the phone to go in landscape mode also stop working.
I think if somebody could edit the script to tell the phone to stop using the proximity/lightsensor then the problem would be solved.
I saw a post where archagel got scripts from HyperDroid
Here
I checked the files, but the names did not match with my files, perhaps someone knows more about this?
archagel said:
I had the same problem, so I got libsensors source from HyperDroid, commented out lines that do proximity sensor initialization and got sensors.leo.so that shows to phone that there are no proximity sensor.
There are 3 identical files in the attachment - simply copy them over into /system/lib/hw on the device.
But, actually, repairing sensor would be better solution...
Click to expand...
Click to collapse

[Solved]Sensor on KF?

In the top left corner of my KF there seems to be a sensor. Anyone know what it is for? It doesn't seem to do anything when I cover it.

It is a light sensor that could be used to automatically adjust the screen backlight for example.

Yea but it doesn't seem to do that. I cover it and the screen brightness doesn't change. Is there a setting I am missing?

interesting - i think to remember there was a setting in settings->display called "auto brightness" in stock 6.2 and it was not activated by default - not shure but i think so
this setting seems to be gone in 6.2.1
found that:
http://forum.xda-developers.com/showthread.php?t=1351077
and
http://forum.xda-developers.com/showthread.php?t=1366894
and
http://www.amazon.com/forum/kindle?_encoding=UTF8&cdForum=Fx1D7SY3BVSESG&cdThread=Tx1A25EP3Z5BWB9
maybe i got mine with 6.0 ...
and here a picture of old times:
http://attachments.xda-developers.com/attachment.php?attachmentid=791845&d=1321998472

It should be a light sensor, but on my cm7 fire...it seems not functioning.

-Zeta- said:
It should be a light sensor, but on my cm7 fire...it seems not functioning.
Click to expand...
Click to collapse
It does not work currently on CM7, see post from whistlestop...
http://forum.xda-developers.com/showpost.php?p=21300591&postcount=820

I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful

nateware said:
I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful
Click to expand...
Click to collapse
See same post I listed above. It says that they haven't got the light sensor working in ICS either.

It worked originally in the Kindle Fire 6.0 release but was removed in the 6.1 update and has not been re-enabled in any version ROM that I know of.
Those that had the KF with 6.0 said it didn't work well which is why the most likely disabled it.

The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...

Thanks everyone, that explains it!

fallingcowdude said:
The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...
Click to expand...
Click to collapse
Doubtful. One the KF doesn't come with a case and many cases have the hole for it. Mine does. More likely, there is a hardware issue.
I also note that many phones which have the same thing work better by turning the auto off. Using auto uses more battery on my Dinc, so I just turn it off.

They removed it because it was like watching a bad monitor with a low flicking refresh rate.... it was sampling like 3-5 times a second and adjusting. I thought I was going to have a seizure until it updated
Sent from my Kindle Fire using xda premium