[Solved]Sensor on KF? - Kindle Fire General

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

Related

[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?

[App] Power Switch - screen off by closing 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 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...

[Q] Gingerbread Horizontal Calibration

So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
DroidApprentice said:
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
Click to expand...
Click to collapse
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
machx0r said:
So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Click to expand...
Click to collapse
machx0r said:
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
Click to expand...
Click to collapse
offtohavasu said:
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Click to expand...
Click to collapse
Yeah, I used to use /system/bin/sensorcalibutil_yamaha as well, and it worked very well for increasing the speed/sensitivity of rotation, but seems to be gone in CM7 (Which is built upon AOSP GB 2.3.5). I brought it up in another topic & one of the devs (I forget who) said that there is no known fix right now.
I'll try offtohavasu's tip, but I'm not gonna hold my breath! I've used it before with no success, but I haven't tried it with CM7 yet. Cross your fingers that this is the fix we need!
EDIT: no luck. I tried both the "Compass calibration" (which I didn't expect would do anything for rotation speed/sensitivity, but I tried anyway) and "Calibrate Pitch and Roll," and neither one had any impact.
not working for me either.
My rotation lag is terrible as well, and the upside down / display calibration option has not fixed it. I thought it was just me as this popped up on the last two GB leaks for me. I would love to be able to rotate my phone properly again.
Hate to tease but if I had a computer I could probably whip up a possible fix if I had my computer:/
Sent from my Samsung Legen-wait for it-dary! 4g
This certainly seems to be somewhat hardware related (as in, variations in production quality). I had issues back on Eclair or one of the first froyo leaks, including the bacwards compass that initially lead me to the upside-down calibration discovery, but my rotation speed has been fine since sometime around the release of EC05.
But how long of a delay do we each define as lag? When I had issues, I actually had to shake the phone to get the rotation to register... now, it still hesitates for about a second, but I see that at as a check to make sure it was an actual rotation instead of an incidental, momentary tilt of the phone - I would be annoyed if my screen rotated every time the motion sensor detected the slightest movement
Edit: a full second is an exaggeration, I'm seeing more like half a second of hesitation... Just trying to remain accurate
2nd edit - damn swypos, lol
Sent from my SPH-D700 using XDA App

Notification light

Hi Nexus 10 owners,
Love my Nexus 10 but I have an issue with the notification light under the screen.
It was working fine when I first got it on Friday, with it dimming on and off when an email is received.
But since yesterday, it hasn't light up at all, for any notifications, and I do have the "Pulse Notification Light" checked in setting.
So I was wondering if anyone else have any problems with the notification light? Could it be a bug, or perhaps my light broke after the first day?
Thanks in advance for any response.
I might suggest trying https://play.google.com/store/apps/details?id=com.coolbeans.ledtester&hl=en to see if your light still works
espionage724 said:
I might suggest trying to see if your light still works
Click to expand...
Click to collapse
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
imistw said:
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
Click to expand...
Click to collapse
Yea it might be possible that app doesn't work; may want to see what an actual N10 owner has to report though
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
So I guess it's really just my N10 then.
Thanks though.
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
UPDATE
Just reset my N10 and now the notification light works again.:victory:
Guess it must have been one of the app interfering with the light.
BTW, when I tested it with a LED tester app, it can actually show green, red, blue and purple lights.:good:
alias_neo said:
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
imistw said:
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
Click to expand...
Click to collapse
If I understand right, he just flashed a factory 4.2 image from Google, without any OTA updates.
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Wow, I did not know about the factory software from the Google developer site. Guess i learned something new today. :laugh:
UPDATE #2
The notification light is not working again
Reset my N10 again, then performed a LED light test each time I install a new app.
Until the last app installed, the notification light was working, then after a few minutes it stops working again.
So I guess it's not really caused by 3rd party apps.
So I ask again, has anyone had problem with their N10's notification light?
Still hoping that it's a bug instead of just me having a defective unit.
Thanks again!
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
hefferman said:
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
Click to expand...
Click to collapse
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
I think you are right. LED notifications were working ok when I had a freeze in google now. I restarted (on battery) and tested the notifications - no LED. I plugged in the charger, restarted the system and retested - LED working again. Looks like we have a workaround and a confirmed software bug rather than a hardware fault.
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
alias_neo said:
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
Click to expand...
Click to collapse
I'm not entirely sure, there are people who are claiming that their LED works 100%.
kftrav said:
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
Click to expand...
Click to collapse
Just tried this but still nothing.
Called Google today and they are sending me a replacement.
Ok, this is ridiculous.
Just unplugged my N10 and now the notification light is working.
So apparently it's working randomly.
Hopefully my replacement device works 100% of the time.
BTW, are replacement devices new, or refurbished?

Two fire tablets showing different brigtness

Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt
amti366 said:
Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt
Click to expand...
Click to collapse
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?
amti366 said:
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?
Click to expand...
Click to collapse
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.
Davey126 said:
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.
Click to expand...
Click to collapse
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt
amti366 said:
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt
Click to expand...
Click to collapse
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).
Davey126 said:
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).
Click to expand...
Click to collapse
Ok thanks for your help Davey126

Categories

Resources