Gyroscope not working properly on Mi 9T - Redmi K20 / Xiaomi Mi 9T Questions & Answers

I have been using my Mi 9T for about a month and I have just realized my gyroscope is not working well.
Maybe is not just a hardware problem because some apps like Xiaomi's Compass or Auto-Rotate are working perfectly for me and they rely on the gyroscope. But on apps like Pokemon GO's AR, StarWalk 2 or watching VR videos on YouTube I can't get the gyroscope working.
I have entered engineering CIT and even installed some apps to see the calibration of the gyro and they detect it but don't even get feedback from it so I can't calibrate it.
I'm on Stock MIUI Global 10.3.11 with locked bootloader and non-root.
Hope you guys can help me figure out if there is a fix for this. Thanks.

RatonDeArmario said:
I'm on Stock MIUI Global 10.3.11 with locked bootloader and non-root.
Click to expand...
Click to collapse
Hi, you wrote you are on Stock MIUI. Did you had updated from computer with Fastboot, TWRP or other OTA updates. Did you have ever seen your compass working correct?

Aliosa007 said:
Hi, you wrote you are on Stock MIUI. Did you had updated from computer with Fastboot, TWRP or other OTA updates. Did you have ever seen your compass working correct?
Click to expand...
Click to collapse
Hi, and thanks for the reply.
I'm on Factory Stock MIUI. I haven't updated from computer.
I think I haven't seen my gyroscope working properly ever, except for the tasks it does work (auto-rotate basically), but VR or AR apps and gyroscope feedback do not work.
I'm waiting to see what happens when I update to official Global MIUI 11 and if it fixes up. If it doesn't I guess I will claim warranty on my device, because I haven't seen anyone experiencing the same issues like me with this device.

Facing gyro issue
My gyro is in slow feedback and even lagging sometime. Xiaomi compass have same issue what to do?

Fix %99 if xiaomi issue with factory reset
Hi.
Make factory reset and never change any settings. Install your program and report us what happend?

Related

MX5 Camera issues

Hello,
Got strange problem with my Meizu MX5 camera, which I´m not sure is software or hardware based. My back camera isn´t working anymore at all, front camera works but image is upside down. Used System Droid app from store to check my phone, and it doesn´t recognize back camera at all, it will only find back camera.
But what happened. Camera ceased to work at same time I changed from test rom to stable 5.1.1.0. After that, camera didn´t work. Changed back to test rom (something in December version) with clear data option, same problem. Once more to stable 5.1.1.1 version with clear data and still camera isn´t working. Does that mean it is hardware problem that just occurred at same time I changed rom or it is possible there is still some problems with software and so it is possible to fix it? And how?
I can confirm that camera app works on MX5 and 5.1.1.0A stable ROM dowloaded from flyme.cn
Could be hw malfunction with your device

Proximity sensor issue m3 note

I ve seen this adressed but upgrading to Flyme 6 does not solve the problem for me. Proximity sensor works occasionaly then not. With sensor utility it works like 5 times out of ten. I tried all G versions of Flyme 5, Flyme 6, chinese betas, problem still persists.
Does anyone have an idea or had a similiar issue. Thnx
tommyboy7 said:
I ve seen this adressed but upgrading to Flyme 6 does not solve the problem for me. Proximity sensor works occasionaly then not. With sensor utility it works like 5 times out of ten. I tried all G versions of Flyme 5, Flyme 6, chinese betas, problem still persists.
Does anyone have an idea or had a similiar issue. Thnx
Click to expand...
Click to collapse
If you update to new firmwares with clear data ticked then this will not happen, if you update with clear data ticked then Flyme 6 has an option to calibrate the proximity sensor and sccelerometer under the settings app. (Settings>Accessibility if i'm not wrong). Try doing it, if that doesn't help too then it most definitely is a hardware issue.
My phone is gionee f103(not pro) and rooted . For installation of custom rom,I followed the instructions in this guide and installed the zip from TWRP. It installed without any issues. But when I rebooted, the device got stuck in bootloop. I was not able to use either recovery or factory mode. Please tell me , what do i now , please.......

Fingerprint suddenly disappeared

hello friends,
I am using custom rom in which my fingerprint working fine for some days but suddenly some day it disappeared .Unable to found fingerprint option anywhere in my zuk z1 device.I tried clearing credentials and unmarking android device manager etc and tried flashing with another customer roms still no solution at all. I am using lineage os 7.1.2 custom rom currently .if anyone have solution please help me in this.
thank you .
srk2521 said:
hello friends,
I am using custom rom in which my fingerprint working fine for some days but suddenly some day it disappeared .Unable to found fingerprint option anywhere in my zuk z1 device.I tried clearing credentials and unmarking android device manager etc and tried flashing with another customer roms still no solution at all. I am using lineage os 7.1.2 custom rom currently .if anyone have solution please help me in this.
thank you .
Click to expand...
Click to collapse
One possible solution is to flash zui 2.5. If that won't work a hardware fault can be the nearest problem as your problem is known and leads to that.
thanks strongst sir,I tried flashing zui and i am getting add fingerprint option but while doing fingerprint clicks for setting fingerprint lock my sensor not detecting my finger clicks.So i think it might be hardware problem .
srk2521 said:
thanks strongst sir,I tried flashing zui and i am getting add fingerprint option but while doing fingerprint clicks for setting fingerprint lock my sensor not detecting my finger clicks.So i think it might be hardware problem .
Click to expand...
Click to collapse
As I mentioned, the faulty fp hardware a widely known problem of the zuk z1

Sleep of death in all Nougat ROMs

The global trouble with all nougat firmware
Hi guys. I amn't alone, I met 10-15 users at 4pda with such problem.
We have the bug at all nougat roms by any devs with different trees...
The sleep of death.
Personally I notice it after/during mobile internet using, but I'm not sure. For long time at home(for a week, for example) with WiFi I have no troubles. But if I am anywhere without WiFi and use 3g(don't have LTE in my country), my phone "sleeps" for some times during just one day... It isn't powered off as it's needed 10-15 seconds of button pressing to turn it on at least.
As the ROM and developer has no meaning I guess that here are the errors in the kernel. @fir3walk says that here are many bugs in our nougat tree and perhaps the trouble is involved in last_dmesg... Or some system force stopes, dozes work improperly.
Not many users have this trouble but it exists an a fact. So it would be great to detect an error and try to fix it. Perhaps not in nougat, at least in new Oreo(I haven't tried it yet so no information about this bug there). We have many ROMs, they are updated for some times a week, new roms are rolling out... But the bug stays still.
If someone else has such problem, write here. Perhaps somebody has any ideas and together we will be able to find solution...
So, all the devs who can detect an error, write us... Any tests, information, logs, etc.
P.S. By the way it is impossible to write logs of powering off(deep sleeping) via logcat or another's. If I run the logging I have no "sleepOFdeath".
It is really global trouble so let's try to fix it together.
I'm sorry for your trouble.
Lets start by figuring out which device is in question
I have a 3s prime and never saw this issue.
So do you have a 3s or 3x or 3s prime?
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
i face it in rr rom but no in dnd rom
Guys did anyone here with the sod, flash global stable/developer in edl mode?
leyD said:
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
Click to expand...
Click to collapse
Hello. No, I didn't try miui based on nougat.
But other users say that they notice such trouble at miui(7 android) as well.
So it isn't the cause...
Also about my phone:
Redmi 3s, 2/16, 2016030, FPC, aa1 motherboard.
bekcicandrej said:
Guys did anyone here with the sod, flash global stable/developer in edl mode?
Click to expand...
Click to collapse
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Dmytox said:
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Click to expand...
Click to collapse
17.5 h of SOT on what ROM?

problem with Samsung s8 (Sm-G950F)

guys i rooted my phone and i installed the linearge but the fingerprint sensor stopped working there is any solution ???
reddevil63 said:
guys i rooted my phone and i installed the linearge but the fingerprint sensor stopped working there is any solution ???
Click to expand...
Click to collapse
perhaps a kernel issue? in all honesty, it has to be a kernel issue as that is the chunk of software specifically designed to allow the OS to talk to the hardware. Reflash the ROM, im betting part of it failed even if it said that it didnt
I'm currently on LOS, fingerprint works great here, but a couple months ago it just wasn't implemented. Maybe try reflashing?

Categories

Resources