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
Related
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
Hi all!
I noticed a strange problem with proximity sensor:
When display is on and ONLY with an android rom,both SD and NAND(all android rom that i have tried have this strange problem) there is a light flashing on the proximity sensor like infrared light. The light is very weak, if you want to see it go in a dark place and look carefully the proximity sensor because light flashing is very fast.
This problem is not present if display is off or when the phone is off.
This strange problem is only with android rom and is NOT present in wm6.5.
Someone else have this problem?
Thank you all!
Doesn't do it on mine. The only time I've seen that is on videos that have picked up the proximity sensor (which is what it is).
TBH, I'd just ignore it.
Why do you call it a problem? If it's that weak that you have to make a conscious effort to go into a dark place and look really hard for it, then you're basically saying you'll never see it otherwise.
Thanks for you reply.
johncmolyneux said:
Why do you call it a problem? If it's that weak that you have to make a conscious effort to go into a dark place and look really hard for it, then you're basically saying you'll never see it otherwise.
Click to expand...
Click to collapse
I call it a problem because this does not happen in wm6.5.
I meant that it was easier to see in the dark, but you see even in daylight, not strong but is still visible.
Why this happen only in android rom?
Thanks
Thanks for observation. I think this is one of the side efects which are with proximity sensor at some devices.
Aparently reason for additional power drain when device is on. For me sensor is not working at all, but in WM it was without problem.
Before there was always advices to change Android build, WM build, radios, Android boot loader etc. because some combination of them could be a problem but since NAND build are present, we all have almost same combination of HSPL,radio and also kernels used in build are prety much the same in this matter.
Well I hope some clever head will get some idea
Thanks for your reply!
I also think that this problem is a possible explanation of battery drain when the phone is not in stand-by and this explain,in my opinion,because there is a reasonable battery drain on stand-by(when the flashing light is not present).
I think also that this flashing light contribute on power consumption.
This problem is not present only in NAND rom, but is present also in SD rom.
I think this is a general problem that is present in ALL HD2 android rom(SD and NAND).
I saw some video on youtube which shows differencies in proximity sensor behavior between EU and TMOUS devices. I think this differencies has to be somehow included or patched into Android kernel otherwise there will be always problems with some devices.
http://www.youtube.com/watch?v=OKCRqFYtLMs
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?
I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port
It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english
I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.
Bump!
Anyone? :/
I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13
Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.
Your setup works for me as well - until we`ll see a fix for it this will do
Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat
with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make
try to change the kernel. that works for me
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired
Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.
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 folio'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!
Thank you for it.
Are you saying things work properly?
I've played a bit with this app now and I can't get it to work properly.
Here are the two things I've encountered:
1. In the notification bar it says - Power Switch is active, tap here to configure. This doesn't do anything. To open the app/configuration I have to access it from a shortcut or from the app drawer.
2. The light sensor doesn't seem to work. Only response I get from the app is when it's turned up side down. Then it will switch off the screen.
I'm currently running it on FolioMod 1.4
Android 2.2
Kernel 2.6.32.9
What else can I do to help you?
1 - ill fix this, seems to be some sort of funky error
2 - thats sounds like a kernel problem, try using sensorlist app from mareket to check sensor...
Okay, well I think I know why the light sensor is giving us/you such a problem
There is no light sensor
I've seen it being listed in ads and reviews, but mine doesn't seem to have one.
I've got:
* tegra_accelerometer
* AK8975 3-axis Magnetic Field sensor
* AK8975 Orientation sensor
* tegra_tmon
Do you have auto brightness?
No.
I think Auto brightness was available in the Folio3x ROM (Honeycomb) but if it was active and actually working I don't know.
See that means its your rom/ kernel combo thats broken... surely every modern tablet has a light sensor?
I'll give the Honeycomb ROM another go next week and will let you know how it works.
Is anyone else missing a light sensor?
I have taken for granted that this device doesn't feature a light senator... Does anyone have any indication of that there should be one?
Do you have auto-brightness?
I think that we have and I had problem with SOD before I installed this app. Now I only put it in case and after par seconds it turn off screen and when I want to use it I don't have SOD problem. Thank you very much, lite version is OK for me but I'll might buy full version.
Sent from my FolioComb 0.4 using Tapatalk
What is sod?
SOD=Sleep Of Death
That means if you go to hibernation, you can't turn on screen and you must pull out your battery or long press power button(not fo all devices)
Well there apis an auto-shutdown setting...
Well? Any comments?
ftgg99 said:
Well there apis an auto-shutdown setting...
Click to expand...
Click to collapse
as allways. But noone can reproduce SOD - I can't even if I have seen it few times. For me helped long press on power button. Looks like bug in device dependent code - betelgeuse patches for kernel.
I sure can reproduce SOD. More often then not my folio reacts that way. I am currently not turning it of but just dim the screen when I put it away for awhile. Have tried a lot of things but my specimen is "a bit of a bastard". Still I'm hoping someone will come up with a way to circumvent the problem with some software patch. Guess it would have to be done in the kernel...
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