Related
Posted a few other places with no answer...
Is there a way to calibrate the accelerometer? Mine is WAY off.
My friend has the HTC Incredible and he can do a quick accelerometer calibration by placing his phone on a flat level surface and hitting a calibrate button.
there's a game called "papijump". it let's you calibrate your accelerometer. works great.
cheers
Great app for calibration is Advanced Bubble Level. You can calibrate the accelerometer on all sides. You just need level surface.
Sent from my GT-I9000 using XDA App
The problem about Advanced Bubble Level or any bubble app, it only calibrates the app your using, and doesnt calibrate the system accelerometer, therefore when using another app that doesnt give the option for calibration such as the game ASPHALT 5, you'll end up being stuck again, with no way of calibrating the accelerometer.
I've contacted Samsung regarding this and they told me to go to the service centre as this is a hardware issue. If it is possible to correct it on site (which they told me is very unlikely) they will do so, if not, they will send the phone back to Samsung so it can repaired/exanched.
there is a script you run to calibrate search on this forum
Also, in JP3 firmware, there's calibration in the Settings, so it's obviously coming with Froyo.
My Galaxy S acts like its accelerometer is not calibrated. However, I checked with the internal hardware test. Dialed *#0*# then entered Sensors dialog, and my readings on x y z axis' went to 0 when put on a level surface. In spite of that, Layar and Asphalt5 still thinks my phone rolls to the left when on a level surface. Pretty strange.
It is very frustrating, that Samsung lacks the calibration feature. I think I will return my phone, not because the hardware is broken, but the soft(firm?)ware surely is.
bivanbi said:
My Galaxy S acts like its accelerometer is not calibrated. However, I checked with the internal hardware test. Dialed *#0*# then entered Sensors dialog, and my readings on x y z axis' went to 0 when put on a level surface. In spite of that, Layar and Asphalt5 still thinks my phone rolls to the left when on a level surface. Pretty strange.
It is very frustrating, that Samsung lacks the calibration feature. I think I will return my phone, not because the hardware is broken, but the soft(firm?)ware surely is.
Click to expand...
Click to collapse
My Layar rolls slightly as well but that must be a software problem. I'm sure there will be a fix with FroYo or something. My Asphalt5 plays fine though.
This has been discussed extensively before... it is fixable only through root. You just need to run the sensorcalibutil_yamaha tool, which is in /system/bin .
Here is the thread: http://forum.xda-developers.com/showthread.php?t=712439
Layar and everything else is completely "cured" doing this. As it was said, there is a problem with factory calibration.
Correction: hardware test has so low resolution, that it displays zero in a wide angle.
SOLVED!
Before launching the
Code:
su
/system/bin/sensorcalibutil_yamaha
from the terminal:
try this http://forum.xda-developers.com/showpost.php?p=9876929&postcount=42
Then do the calibration.
DONE!!
SOLVED!!
Before launching the
Code:
su
/system/bin/sensorcalibutil_yamaha
from the terminal:
try this http://forum.xda-developers.com/showpost.php?p=9876929&postcount=42
Then do the calibration.
DONE!!
Or in 2.2..
Menu -> Settings -> Screen -> Horizontal calibration. Hey presto, it's calibrated!
(I've translated the labels here, so it might be a bit off )
Does the menu->settings->display->horizontal calibration appear in all 2.2+ phones, or is it SGS-specific?
If I'm writing an app that measures the phone's pitch, should I include my own calibration option?
PS: Hi! First post.
PersonOfKnownOrigin said:
Posted a few other places with no answer...
Is there a way to calibrate the accelerometer? Mine is WAY off.
My friend has the HTC Incredible and he can do a quick accelerometer calibration by placing his phone on a flat level surface and hitting a calibrate button.
Click to expand...
Click to collapse
dude i wanna kiss you, i really do lol
i had a problem with the accelerometer for two days, i tried everything to fix it but i couldn't, until i read your post, so i placed the phone on a flat level surface and hit the calibrate button and it worked like a charm!!!!
thanks a lot man
Guy's,
The accelerometer on my rooted 2.2 suddenly stopped working. It was working fine one moment then the next it just stopped. I've tried it in several applications including the Bubble app and everything just displays in portrait. If I try to play a game which uses the accelerometer it either fails to launch at all (Asphalt5 tries to launch, vibrates a few times then shuts down) or it just doesn't play e.g. in Labyrinth Lite the ball just stays put regardless of how I move the phone.
I've been into settings -> Display -> Auto-rotate screen to make sure that's ticked and it is and I've also performed a Horizontal Calibration in the same menu with confirmation that the phone has been "Calibrated". I also did several battery pulls without success.
Seriously confused.com here.
Any ideas?
Ben
Hey guys. I have looked around and can find no info on some of the tabs sensors. From what i understand the chipset is straight out of the galaxy s phones, which is the reason i see the existence of a proximity sensor but dont see any data from it.
Anyone have a clue whether it actually exists?
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
triplex76 said:
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
Click to expand...
Click to collapse
Doesn't need and doesn't have are different things. Point is, if it was stated that the tab has a proximity sensor, where is it?
I'm pretty sure it has one, in the unofficial CM build Technomancer says he fakes i at 10CM
There is no proximity sensor in Galaxy Tab.
My CM7 sensors driver pretends there is one and reports 10CM distance so the Phone app behaves better.
Thanks mate, that's what you said in the last thread back in October, but why do all the sensor pingers see it? Are they checking code rather than hardware?
Also, is there a working, sensitive light meter anywhere for the tabs ambient light sensor? The couple I've tried refuse to work...
There is working light sensor in the Tab. Both my CM7 and Samsung ROMs support it just fine. It has range from 0 to 6000 Lux snapped to one of several levels in the kernel driver. You can actually read it from sys interface.
The proximity sensor in my CM7 sensors driver is just software reporting constant 10cm to the system. The sensors test apps in my CM7 (I uses Sensor Test and Plot http://www.appbrain.com/app/sensor-test-and-plot/com.golborne.android.SensorTest) just reports 10cm from my fake sensor.
I think there is some leftover code in Samsungs sensors driver that may report presence of proximity sensor.
Yep, i use it as well, but my issue is with the three avaliable states the driver seems to report.
I get 5, 22 and 75. Are there only three levels then? And no way to modify them outside the kernel?
I can get up to 6000lux using strong LED flashlight directly on the sensor.
There is another sys device that can read unprocessed data that has values not snapped to 5,22,75 etc... but Samsung's driver uses the snapped device (and so is mine).
This is very annoying... im trying to make an app that needs a proximity sensor to work as intended so the light sensor as well as the sleep mode implementation are really no substitute.
In any case, im sure it will be quite usefull for all tablet owners running 2.2 and up and using a case. I will have a closed beta for xda members by the end of the day, so people can test it over the weekend.
Would you like a shot, mancer?
I don't know what would you do but if I understand why not to use the g-sensor ... just like in samsung omnia...put backwards enable silent courtesy mode.
the proximity sensor will be useful if you use the leather case to close the screen when touches the screen , like ipad 2 and galaxy tab 10.1 V they have proximity sensors , but i noticed that the sensor exists using sensor applications they see it exists but not giving readings
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
ftgg99 said:
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
Click to expand...
Click to collapse
Thanks I already bought it from market and it's great
Sent from my GT-P1000 using XDA App
Great! Im working on an update that will help improve the accuracy of the light sensor functions... been getting some flack for not updating it
Watch this space!
Anyone seen their light sensor get 'stuck' or just badly calibrated?
Mine reports super low values unless you hold it right up to a light bulb, then it says 'dim room' or something similar lol.
'
This all started happening after I tested out killswitch application (which uses the light sensor) which I think killed it. I've uninstalled and rebooted but now my light sensor is stuck in above state.
Anyone know how to recalibrate?
Bump and even more confusingly, I'm now on overcome 2.0 rc1 and even full restock and flash to new rom didn't fix it. What the...
Sent from my GT-P1000 using Tapatalk
Its a known Issue to samsung light sensor auto brightness is screwed. They fixed it with Galaxy S2 upgrade. I wish someone would port it for our tabs
oh snap it was working OK before that app broke it, no joking.
And the broken-ness carried across a full restock and upgrade from Overcome 1.45 to Overcome 2.0 (froyo --> gingerbread). So something is very weird, I hope you're right and that its a SW problem not hardware.
Also lightsensor problem with brand new Tab 7.7
I also have a problem and nSamsung doesn't even answer to my cries for help (Samsung Belgium redirected me to Samsung the Neteherlands and they do not reply at all).
I downloaded different luxmeter apps and general sensor apps they give as measurement result 12, 120 or 1200 lux (seems they output the range or lower or upper limit of the range the sensor is on, not the actual value). The sensor datasheet says it has a resolution of 1 lux.
Any solution would be much appreciated, I intende to use the sensor as a luxmeter and write an app for it taht needs the luxvalue ! But as it is now, the tablet is completey useless for this because the OS/driver software not working properly
Gsam Battery Monitor is reporting something called 'sensors.qcom' as being one of the things that is using up my battery (only 2.1%) but it is the only thing on the list that xda and google hasn't been able to explain to me; aside from some forums linking it to the accelerometer. The thing is, I am not using anything that requires the accelerometer... The battery life on the phone is very good, but this might be kepping it from being great.
Can any of you good people enlighten me as to what sensors.qcom is and how it can be quelled?
sensors.qcom is a process used to activate the sensors on all qualcomm based phones, sounds to me like either you're using an app that is using the sensors often, or an app that is using the sensors doesn't shut down the sensor once it finished using it.
meaniez said:
sensors.qcom is a process used to activate the sensors on all qualcomm based phones, sounds to me like either you're using an app that is using the sensors often, or an app that is using the sensors doesn't shut down the sensor once it finished using it.
Click to expand...
Click to collapse
Thanks for the reply. I don't think I am using any apps that need sensors but I will examine my apps and see what turns up.
Could it be the camera? Aside from the camera the apps I use don't require anything but the touchscreen (tap-to-wake is not on and neither is adaptive brightness).
Hi all,
Been quite a few years since I posted anything here!
I have just received my pixel 5 and have noticed that dead center of the notification tray when in portrait, there is a flickering dot, especially in low light it flickers white or if not flickering leaves a faint grey dot over whatever is on the screen (stays in the same place even if I rotate the phone or watch a video)
If I reboot I can't see it for a minute or so until it then appears.
Factory reset doesn't solve it.
Has anyone else noticed this? I'm thinking it might be the ambient light sensor under the display but it is really irritating, possibly mine is faulty?
Cheers!
It's the underscreen proximity sensor.
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Not showing on mine
I have it constantly when KinScreen is running, I saw someone having it with cpuz
I hadn't noticed until I saw this thread. I did wonder where the proximity sensor was. It's only visible when on a phone call for me.
Is the light sensor under the screen also? You can usually see that on a lot of devices when you tilt the screen slightly.
Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
Mine only shows when on a call
You probably have some apps using it. Possibly something like Tasker that happened to have proximity sensor based profiles configured, etc.
Mine went mental during Google Play downloading all my apps on initial phone setup. Then it went out and I've not seen it since.
Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
I got the same Problem after installing notifybuddy. There must be some Bug where the sensor gets started the moment an overlay is shown. I can reproduce the Bug over and over again. Install notifybuddy and Start the App give all permissions and than Pull down notificationscenter (its an overlay). To solve the Problem, uninstall notification Apps That are using overlays.
Mine is working fine. Only during a call or listening to voice messages.
akpe said:
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
Click to expand...
Click to collapse
Hit the nail on the head there!
It was the Home assistant app causing it (even though it had installed after restoring from my backup, I had never opened it yet since having this phone). Uninstalled home assistant and it has stopped flashing!
Thanks so much for the replies all!
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
Go to the gestures options (don't know exactly where the specific one is located, it could also be at the Digital Wellbeing settings) and disable the Flip to Shh one. See if that helps.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk
Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Couldn't find that was causing the issue. After a restart it would be fine but once unlocked and apps started loading it would go crazy. Went through all my apps but couldn't find the cause so just reset my phone. Hopefully it doesn't show up again.
Seems to.be software issue so hopefully google will do something about it
Joshhudsy said:
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Click to expand...
Click to collapse
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
jimv1983 said:
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
Click to expand...
Click to collapse
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
MasterBelch said:
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
Click to expand...
Click to collapse
If what you are saying is true then why can't you see the sensor flashing on any phone when in a phone call or when the "Flip To Shhh" feature is enabled with just your eyes?
And if that is true about the Pixel 5 then there will be no way to use the "Flip To Shhh" feature without always seeing the sensor flashing which I can do with my Pixel 2 XL.
Here is a video of my Pixel 2 XL taken with the camera on my tablet. You can see that the tablet picks up the flickering sensor when "Flip To Shhh" but the sensor goes off when I turn the feature off. That's because the feature uses the proximity sensor to work. However, the flickering is ONLY picked up by the camera on my other device. I can't see it with just my eyes looking at the phone even though the sensor is active.
https://streamable.com/z30mgx