How to do self-diagnostics on accelerometer? - Galaxy Tab S2 Q&A, Help & Troubleshooting

My wife has a problem with her SM-T815 regarding screen orientation. At times it will flip the wrong way without having been moved.
She's running the German 6.0.1 build.
I wanted to enter the menu in the dialer to check and recalibrate the gyroscope and accelerometer - you know, *#code#* etc, but I can't seem to find these codes anywhere.
Does anyone have some advice on how to do this?
Regards,
LosserKlosser
Sendt fra min SM-T815 med Tapatalk

Factory hardware test *#0*#
But there are apps out there that can do further tests.

Related

[Q] Problem with screen rotation (sensor)

Hello,
I have strange issue with my Xperia Z. I used to use many android based phones, so i believe Z's behaviour is incorrect. How it works - i.e. I have my Z laying on the table, when I launch some app supporting screen rotation i.e. browser, mail etc., it automatically rotates to landscape mode. When it's in landscape mode and I am lifting it up (keeping the device in portrait position) it doesn't switch into portrait mode at all or it's very very delayed. I haven't found any calibration settings in the software, so have no idea what I can do in order to let the screen rotate smoothly after physical position change.
Quick update - both orientation sensor in portrait mode and gyroscope are giving wired results. Can it be calibrated somehow?
Any advice appreciated!
Best regards,
MCC
Dial *#*#7378423#*#* there is calibrations.
This is only available in 4.2.2
Sent from my C6603 using xda premium
I have 4.1.2 and the menu is there - i could calibrate gyroscope, but accelerometer calibration was unsuccessful - Error Code 1.
Anyhow after calibration of gyroscope result is the same - horizontal orientation sensor is shifted to the right ;( PLS see attached screenshot.
Best regards,
MCC
I just tried it and it's good on my phone,i don't know if it's a hardware issue.
You try another firmware maybe it's a software problem and maybe if you can update to 4.2.2
Sent from my C6603 using xda premium
Sent from my C6603 using xda premium
Hi,
is there any option to reach reset menu on 4.3?
BR,
MCC
hi guys
i have the same problem for a while and i'd like to share my experience !
suddenly the auto rotation problem disappear when i install asphalt 8 and play it then i unistall it and wait for a day ! weird huh ?
regards
yassine_phi said:
hi guys
i have the same problem for a while and i'd like to share my experience !
suddenly the auto rotation problem disappear when i install asphalt 8 and play it then i unistall it and wait for a day ! weird huh ?
regards
Click to expand...
Click to collapse
By any chance the rotate problem appeard when you had asphalt 8 installed? I had this problem for over 2 months and 2 weeks ago I deleted asphalt 8 and that problem dissapeared...I think this games has some error in it that affect some phones
screen rotation,gyro,proximity,accelerometre not working
Hi guys;
My xperia z sensors are not working. I install android 5.0.2, 5.1.1 and 4.3 or 4.2 but don't solution.
Only light sensor and notification LED are works correct.
I dont understand this problem?
Please help me.
I try other sensor modul but it is not work.
What is my problem?
My english is poor, sorry.
Thanks your advice..

proximity sensor issue during phone calls

when I talk with my XZ1, and I should activate the proximity sensor with my ear, it often fails
often, the display light keeps ON and I activate with my ear all the possible functions (for example I had to turn off my airplane mode shortcut off to avoid to lose calls in progress pressing it with my ear!)
the only way to save all my calls is.... to remember to lock my screen before answering
do you know how can I fix it? :angel:
anybody had the same problem?
I'm having the same issue, really frustrating as I have ended calls several times and also muted, called extra calls etc...
Not happy about this at all
the same for me !
it's really annoying :'(
I just noticed. If I cover the sensor before making the call, the screen turns off when I press call, and comes back when I remove the cover.
I however can not make the screen turn off once I have removed the cover.
I get the same problem, I also had similar experience with my HTC One, I've found out if I lock the screen after dialing number/contact it helps, a bodge job I know but stops me going through the menus with my ear lol!
Sent from my C6903 using Tapatalk
I'll try the new firmware
guybrush2099 said:
I'll try the new firmware
Click to expand...
Click to collapse
What is the latest firmware ?
.257
Inviato dal mio C6903 con Tapatalk 4
I've got problem with sensibility of the sensor some times.
I thinks i don't use the good position for the phone.
With xperia T i've used "pimp my rom" to lower the distance for proximity sensor. It was a lot better.
May be it's not the same problem as you cause it was not on every call.
BTW i've an other question about proximity sensor. I need to have it working with other app. i don't have try every option on pimp my rom and now my Z1 is back to root.
where's the "pimp my ROM" function to tweak proximity sensor?
guybrush2099 said:
where's the "pimp my ROM" function to tweak proximity sensor?
Click to expand...
Click to collapse
In the app go to :
-> tweaks -> telephony -> proximity sensor delay
Edit :
since .257 proximity sensor don't work...
maybe do you need a rooted device?
Inviato dal mio C6903 con Tapatalk 4
guybrush2099 said:
maybe do you need a rooted device?
Inviato dal mio C6903 con Tapatalk 4
Click to expand...
Click to collapse
Yes, pimp my rom need rooted device but i've read after upgrading.
So i loose root...
I don't have time to test root on .257 now
I've just tested "proximity screen off" (by playstore) on my. rooted. 257. It perfectly works No more problems during the calls
Inviato dal mio C6903 con Tapatalk 4
Had this problem. Just hold your phone properly wherein you touch the proximity sensor.
Sent from my C6903 using XDA Premium 4 mobile app
I had a bit different issue. When I dial a call, immediately the screen goes blank (proximity sensor is activated), but the call goes through well.
I powered off the phone and turned ON again, the issue did not occur. I have the latest software update
-------------------------------------------------------------------
Xperia Z1 (C6902) India
SW version: C6902 14.1.G.2.257 Generic IN
dial *#*#7378423#*#* there is a calibration of sensor but for me when trying timeout error
you need to factory reset
a good solution without root is... to use the right ear talking on the phone. The problem seems to be sensor's position
Inviato dal mio C6903 con Tapatalk 4

screen wakes during call

Sometimes screen wakes during call for a second and it repeating that, but a have the phone close to my ear. (I'm using stock (root) firmware). What do you think it's a problem? (if i test promiximity sensor in hide menu-"promiximity wakelock" for a longer time all is OK)
Try with another rom.
clesuite said:
Sometimes screen wakes during call for a second and it repeating that, but a have the phone close to my ear. (I'm using stock (root) firmware). What do you think it's a problem? (if i test promiximity sensor in hide menu-"promiximity wakelock" for a longer time all is OK)
Click to expand...
Click to collapse
The stock firmware for our phone has some problems with the proximity sensor. Iodak's kernel and p880-sources built ROMs have a fix for it included. Not sure about CM based ones, but I guess they'll work fine too! So yeah, that about anything but stock you could try
Greetings from my Nexus 7 FHD!
If another rom doesn't help, there could be some dust or something else on the sensors way... I had similar problems with HTC Desire HD, which was resolved with some intense sensor cleaning... The rom change is easier to complete though, as the sensor is not in visible place
Problem with sensor is rare, so i think, The same as mcgangsta is easier to change Rom
Wysłane z mojego LG-P880 przy użyciu Tapatalka
proximity is kernel related not rom

Problem with gyro sensor

I bought my Moto Maxx with my carrier (Tim) here in Brazil. Recently I've noticed some problems with the gyroscope when I'm on google street view or when trying to take a photosphere or panorama. I was able to diagnose the problem in an app that shows the sensor data in a graph and now I know how to reproduce it: rotate the phone steadily and then stop. The result is that it then starts "rotating" in the opposite direction by itself. If necessary I can capture it for you guys. I would just like to know if it's possible to fix this or if I should try to get a replacement.
Thanks in advance
Update: I contacted motorola and we weren't able to fix it. I tried multiple apps, I did a factory reset and nothing. When I move it very slowly, it suddenly starts pulling in the opposite direction. Is this normal? Software or hardware? Is it just trying to compensate for what it thinks is just malfunctioning (me moving it slowly)?
Please, guys, ideas
That may be the compass, not the gyro. Download the google compass app, calibrate it and try again
Enviado desde mi XT1225 mediante Tapatalk
Using the Sensor Kinetics app, I ser the problem in the gyro's graph. But can you link me to this google compass? Btw, thanks for the reply

Auto brightness not working correctly after 6.0.1 update

Several users (including myself) have pointed out that the automatic brightness doesn't work as before the 6.0.1 update.
Here are some of the reports:
kom-pakt said:
One of the few drawbacks I noticed just today is that the auto brightness seems a lot less responsive. For example it's very sunny today and most of the time when pulling the phone out of my pocket the display was still stuck on low brightness. It might just be a conflict with xposed or something else I'm running.
Click to expand...
Click to collapse
GFixx said:
I have a bug with automatic screen brightness, if I unlock the phone at the sun I do not see almost nothing
G800F ITV 1CQA1
Someone can confirm?
(GPS and Volume seems fine)
Click to expand...
Click to collapse
milad9896 said:
I also have this problem sometimes
Click to expand...
Click to collapse
So far I've tried running the phone without anything on it like Xposed or any apps beside the stock ones and it hasn't fixed the issue. What I do know is that it's definitely not a hardware issue since the light sensor works as it's supposed - you can test yours by entering the service menu by typing *#0*# from the dialer. I am currently running the German DBT firmware but I'm currently in the process of flashing the South East Europe SEE firmware which is different only in the security patch, so if the problem persists then I will know for sure it's not a DBT-only problem.
How many of you have this issue as well? Also, which version of the firmware are you running?
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Myke72 said:
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
Click to expand...
Click to collapse
I am currently running the South East Europe (SEE) firmware but I haven't tested it extensively so I can't say if it's any better.
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
So Samsung's solution for this is to use manual brightness? Really Samsung?
I have the same after upgrade to 6.0.1, it's unbelievable such a bug in official release
any fix for this?
I installed Auto Brightness app, but it seems Samsung display goes above 100% in sun, third party apps can't do it
Does anyone have realy bad battery Problems too? (See my thread...)
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
I have the same problem - I made a video of it below. It's a serious usability problem - makes it very hard to use in sunlight.
As a kind of workaround you can put your thumb over the light sensor as you wake it up, then it will wake up dim but still visible. Eventually it will adjust and brighten to match the sunlight. But this is slow and awkward and needs two hands.
The reply you got from Samsung is ridiculous. For a start, the stronger the external light source, the stronger the brightness of the device - they have it the wrong way around. Anyway, it is obviously a major usability problem and I can't believe they are dismissing it. (And manual brightness is not an answer of course.)
Phone specification:
Model number: SM-G800F
Android version: 6.0.1
Baseband version: G800FXXU1CQA1
Kernel version: 3.4.39-10294723 [email protected]#1 Wed Jan 4 12:03:16 KST 2017
Build number: MMB29K.G800FXXU1CQA1
SE for Android status: Enforcing SEPF_SECMOBILE_6.0.1_0033 Wed Jan 04 12:28:05 2017
It works fine on my G800H with latest Polish stock ROM
I don't use to write in the forum, but I must say 'me too'. If someone knows a working Marshmallow ROM for the G800F. The thumb "workaaround" is the only one working for me..
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
kom-pakt said:
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
Click to expand...
Click to collapse
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
alex3453 said:
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
Click to expand...
Click to collapse
Use the official Samsung website (for your region) to report the issue. Browse a bit and you'll find the form.
It's strange that the number of people affected by this issue seems relatively small, keeping in mind that XDA is a forum where a typical user is usually a power user. Also it's not a region-specific issue or caused by an app or something else. For example I thought that maybe Xposed is causing a conflict so I did a complete wipe and flashed a fresh firmware, used the phone like that without any apps for a couple of days but the autobrightness issue was still there. Tried a different firmware version as well but nothing helps. Again, it's definitely not a hardware issue - test yours by typing *#0*# from the dialpad to enter the service menu and test the sensor yourself.
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
ffoucault said:
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
Click to expand...
Click to collapse
bravur said:
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Click to expand...
Click to collapse
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
foulke said:
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
Click to expand...
Click to collapse
Did you try the basic stuff like reflashing the firmware and such?
kom-pakt said:
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
Did you try the basic stuff like reflashing the firmware and such?
Click to expand...
Click to collapse
No. I don't want to use Odin for the moment.
By the way I installed Lux, and it works fine.
I'm surprised you're happy with Lux, official Samsung can do much more brighter screen in strong sun then Lux
By the way, I removed Lux since. Because it requires too much app permission than I think it should (contacts...)
So I'm looking for an another solution
Good news!
Yesterday I jus tried to install the latest firmware available on sammobile (for G800F) - the one for nordic countries -.. and now the brightness control is working perfectly!
Seems that this 'not' problem was fixed in latests releases :good:

Categories

Resources