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!
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Rudjgaard said:
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Click to expand...
Click to collapse
yeah, i noticed in viber screen doesn't turn off when you put your phone enxt to your ear. i dont have any other apps that use proximity sensor other than phone app, but that one works without issues.
the issue persists in stock as well as custom roms. no idea how it was on ics, though
It also appears on stock?! wow never would've thought...
It's a pretty considerable bug to have never been mentioned before...
all problems with proximity encountered so far always seemed caused by bad calibration..
this kinda sux :S
Devs and wise people, do you think this could be caused by the fact that the 'near' state is set at 3cm reading and 3rd party apps look for 0 distance with 0% tolerance to have widespread compatibility?
Do you think it is possible to change these settings?
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Info
vetko said:
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Click to expand...
Click to collapse
factory Reset ur phone and then use PC companion app to Repair Firmware...
this can wipe current data and install fresh firmware on ur device
:good:
Hi,
I have the same problem. Only the x axis of the accelerometer seems to be affected : it show a value around 1 instead of 0 while the phone is sitting flat. Y and Z display normal values.
All the software solutions I have tried have had no effect at all... It seems the built-in test reads raw data from the accelerometer. It is hard to imagine how this can be a hardware problem though...
Anyway, in my case I believe a software fix (x=x-1) would do the trick but I have no idea how to do such a thing ! Any help ?
@vekto : Have you solved the issue by any chance ?
Would anyone care to try the accelerometer tests and post their results ?
Typing *#*#7378423#*#* will get you on the service menu. The two significant tests are "accelerometer" and "gyroscope".
I'd post some screenshots myself but I'm not allowed yet...
I'm having the same problem now. It seems one axis is affected. Haven't found a way around so far. This is sad because it affects the images taken with Google Camera Sphere mode. The images are badly aligned together with glitches in between. My phone wasn't like this before.
Either a SW fault - might be able to calibrate with GPS Status & Toolbox app, for example - or a FW fault - and reflashing ROM might help (highly unlikely) - or HW fault - the sensor has moved on the board (which is a bad sign anyway, might be on the way to disconnecting itself).
I sent mine to Xperia Care and got it back with the accelerator fixed. Still unclear if it's a HW problem...
It came back with a white spot on the screen (near the power button) though... so I sent it back again
I'm also having issues with the gyroscope. Installed Bubble app to calibrate the gyro. It showed the gyro was of a couple of degrees. Unfortunately the bubble app calibration doesn't work in a game like Need for Speed. It's very difiicult to achieve good times in the game right now since I have to hold it tilted to the left to go straight ahead.
So if anyone has a fix or workaround... Please do post.
Same problem, Seems after factory reset whith wipe dalvik cache.
any solution?
02nd March 2017, my autorotate has completely stopped working, restart, safe-deposit and reset do not fix. Diagnostics show Gyroscope Light Sensor and accelerometer failed testing, 3 years of same issue, surely there must be a fix that works by now?? ( please note, " turning it off and on again " does not fix it )
Helps Please
I have the same issue. Since last week, gyro, accelerometer, light and proximity sensors stop working. I've tried reflashing stock ROM without success. I have not warranty (almost 3 years old), so I even try to disassemble , disconnect an reconnect every flex (I don't know exactly were the sensors are located on the board). After that I get almost 8 hours of fully functionally sensors and then, they stop working again, so I'm almost sure it's a hardware issue.
Same problem for 3 years
I'm just now getting around to doing something about this. As my power button stopped working I can't post requested screenshot without going to the pc. I have been shopping new (fall 2018) phones after having the Z3+ since release. In my research I'm finding the phone still is better than Samsung, LG, and the pixel3 for me because the 3.5mm phone jack is mandatory for me using my device with an i-rig midi requiring both that port and the USB at the same time. I'm going to do everything I can to keep using this phone till it falls to dust. It's one of 4 Sony I've bought since the day Z1 came out of t-mo. I look forward to testing solutions. :good:
Some time after my post, I bought a new jack/proximity sensor flex and replace it. This solved the issue, but weeks later, the bottom portion of the touch screen becomes unresponsive. May be I have done something wrong... may be programmed obsolescence...
Hi I'm facing a problem of my gyroscope I don't know which one is not working a gyroscope or accelerometer. My gyroscope is so delay when I play pubg mobile and I can't also calibrate my Gsensor it always says FAIL but I put in a perfect flat surface please please please help me with this problems
So my display after being replaced 2 times in 6 months started flickering. My phone is very hard to be turned on because of the green flickering.
I just want to upgrade to a S6,S7 Edge or non edge. i just want to know if they have the save problem with displays ? I want to have a phone at least 2 years, can you recommand me a phone like that ?
I was just considering switching to a iPhone even though i prefer android on phones ... o how are S6,S7s displays ? Samsung still have the same problems?
Samsung improved a lot on screen quality in S6 and after, so you should be okay
Dieexe said:
Samsung improved a lot on screen quality in S6 and after, so you should be okay
Click to expand...
Click to collapse
So no more sudden flickering problem ? I mean i didnt even dropped the phone or something like that.
RootNightmareX said:
So my display after being replaced 2 times in 6 months started flickering. My phone is very hard to be turned on because of the green flickering.
I just want to upgrade to a S6,S7 Edge or non edge. i just want to know if they have the save problem with displays ? I want to have a phone at least 2 years, can you recommand me a phone like that ?
I was just considering switching to a iPhone even though i prefer android on phones ... o how are S6,S7s displays ? Samsung still have the same problems?
Click to expand...
Click to collapse
green flickering problem just for auto brightness problem (some custom Roms have this issues) if u will untick the auto brightness u will not have this problem
Not really, it has more issues on this "display green flickering " , on my S5 i dont get display on if the temperature around it getting cold .
Sent from my Samsung Galaxy S5 using XDA Labs
atakan1986 said:
Not really, it has more issues on this "display green flickering " , on my S5 i dont get display on if the temperature around it getting cold .
Sent from my Samsung Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Wow that's amazing. Been using samsung s5 exynos version for the last 1yr. Never had that kind of problem till date. And it have the same display as snapdragon version. And on comparison I found that this is by far the best display out there when compared to other brands.
Maybe perhaps you might be having a faulty unit from the begining.
Sent from my SM-G900H using Tapatalk
I have the same problem here with the display and it's not a software problem (same by original os 6 and same by cyanogenmod 14).
After the temperatures are under 10 C. i can't open my s5 with home button i must do it over the power button.
Using S5 for more than 28 months still I have not faced any issue. I just had to buy new charger apart from that not a single problem and yes I mess up with my phone so much but I still working and no display failure yet. And also I have dropped it many times, it still refuses to die.
You are just having a defective model or some internals of the phone are messed up. Because Samsh*t produces one of the best displays..
shurupi said:
I have the same problem here with the display and it's not a software problem (same by original os 6 and same by cyanogenmod 14).
After the temperatures are under 10 C. i can't open my s5 with home button i must do it over the power button.
Click to expand...
Click to collapse
So when its over 10C its ok ? Then i should sell the phone when its summer )
nikhil007.n2 said:
Using S5 for more than 28 months still I have not faced any issue. I just had to buy new charger apart from that not a single problem and yes I mess up with my phone so much but I still working and no display failure yet. And also I have dropped it many times, it still refuses to die.
You are just having a defective model or some internals of the phone are messed up. Because Samsh*t produces one of the best displays..
Click to expand...
Click to collapse
At least for s5, the internet is full of this faulty displays, even my friends have same problem.
RootNightmareX said:
So when its over 10C its ok ? Then i should sell the phone when its summer )
Click to expand...
Click to collapse
Very simple but good idea my friend : )
Sent from my Samsung Galaxy S5 using XDA Labs
RootNightmareX said:
At least for s5, the internet is full of this faulty displays, even my friends have same problem.
Click to expand...
Click to collapse
This may be problem for Snapdragon variant then.
nikhil007.n2 said:
This may be problem for Snapdragon variant then.
Click to expand...
Click to collapse
Maybe thats a point, but shouldnt only the processor be different? I assume the display is.the same for both...
nikhil007.n2 said:
This may be problem for Snapdragon variant then.
Click to expand...
Click to collapse
Nope, Exynos variant have this same problem
Im also facing green flickering and blinking at low brightness.
Sent from mySM-G900F using Tapatalk
baseer_IF said:
Im also facing green flickering and blinking at low brightness.
Sent from mySM-G900F using Tapatalk
Click to expand...
Click to collapse
Its not a good sign. Try disabling your light sensor. Even then if you experience such a problem than it means that your flex cable that attaches the screen with the motherboard needs to be changed.
Sent from my SM-G900H using Tapatalk
redhotiron2004 said:
Its not a good sign. Try disabling your light sensor. Even then if you experience such a problem than it means that your flex cable that attaches the screen with the motherboard needs to be changed.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
I try to disable Auto brightness. but in manual the problem is persist when when brightness is full low .
if brightness is normal it is normal
Sent from my SM-N9300 using Tapatalk
RootNightmareX said:
At least for s5, the internet is full of this faulty displays, even my friends have same problem.
Click to expand...
Click to collapse
Hi,
Yes and expect the same problems with the following generations. It's an amoled screen thing. The green colour happen when there's a colour displayed on the screen for a very long time (for example, I have a green on my screen of the size of my keyboard).
I think a solution to this problem is to set the display to turn off after 30s (it saves battery too) and maybe, if you're using a custom keyboard, change the colour from time to time. Use the brightness of the screen to a lowest which would still be comfortable to you (and auto unticked).
This last tip alone is enough to prevent greening. My flickering happened after an incredible fall (it had a tempered glass so the screen was safe). The flickering showed green what it had in memory.
Samsung has a 2-year guarantee for its products so you shouldn't worry for that period of time. Problem not solved, replacement.
Best of luck
Superlion721 said:
Hi,
Yes and expect the same problems with the following generations. It's an amoled screen thing. The green colour happen when there's a colour displayed on the screen for a very long time (for example, I have a green on my screen of the size of my keyboard).
I think a solution to this problem is to set the display to turn off after 30s (it saves battery too) and maybe, if you're using a custom keyboard, change the colour from time to time. Use the brightness of the screen to a lowest which would still be comfortable to you (and auto unticked).
This last tip alone is enough to prevent greening. My flickering happened after an incredible fall (it had a tempered glass so the screen was safe). The flickering showed green what it had in memory.
Samsung has a 2-year guarantee for its products so you shouldn't worry for that period of time. Problem not solved, replacement.
Best of luck
Click to expand...
Click to collapse
The funny thing is i already did "by mistake" all the tips you said and still have this. Never dropped the phone though. This problems seems very big though, i expected a burn in to be the biggest problem, but to have flickering at a level that i cant turn on the phone. I wanted recently to switch to a Nexus 6p, but knowing that it uses Amoled too, its a bad ideea. So the only "solution" is to switch to IPS screens? (btw i want a phone that holds on for at least 3 years)
In my research thus far, the AMOLED screen technology is to blame. When the display circuits get old or damaged, they don't sustain current at low power settings. In LED screens, a back light controls brightness, but AMOLED screens send current to each pixel for brightness control. If the circuit is damaged, or any corrosion has built up inside, this could attenuate the current below the point required to sustain light flow. I see this problem with some LED and CFL lights on motion sensor switches. Just enough current goes through the motion sensor to keep it's circuits active, and that current causes a flicker in the light.
With the screen though, since the problem is only resolved when you increase the brightness just a bit above minimum, it seems anything that lowers the display power (auto brightness for example) will cause it to flicker if this setting gets too low. I also noticed that before the screen locks on timer, it dims to low power for a few seconds and flickers as a result. There are apps that attempt to resolve this by putting a translucent black screen over your desktop and apps. This keeps the power up on the pixels but adds a black overlay, kind of like a screen filter. You can adjust the darkness if you need it to save your eyes when reading in the dark but it doesn't help save power any. They also require a rooted device, which could void warranties. The reason for this I believe is because apps are supposed to operate in a way they don't intrude on each other, and a filter that lays over your screen does in fact alter the output of your display rendering. With the added security concerns of these apps possibly collecting screen shots and sending them to another site, I would avoid this. Best to use a physical screen overlay you can put on or remove as needed as long as it doesn't interfere with your touch screen options.
Ultimately, these devices were meant for replacement every 2 to 3 years so if you're like me and you like to make your investment last, best thing to do is apply any work around you can come up with. A repair shop may be able to wipe the circuit boards down with a solution that clears away corrosion, but it won't repair any weakened pixels. I'm still using a Samsung S5 G900F
- And i finally got this fixed. it sounds like the reason for this is that since the latest update your phone cannot decide whether to use hardware or software back light settings. I managed to make the problem go away by doing this:
Go to settings >> system >> About device.
Find "Build number" and click 6 times fast on it.
You will then get the message saying: "You are now a developer"
and then go back to Settings >> system >> Now you will see the "Developer Options"
Now go to Developer options >> Drawing Section or Rendering Section >> Find "Turn off hardware overlays" or "disable hardware overlays" >> This will force the phone to always use GPU for screen adjustments. no more flickering.
but If I turn the brightness ALL the way down, it still flickers like crazy, however, if that's the only time it'll do it, I consider that a win.
Read More :good: