hey, I'm asking you two things for help .. :crying:
So, this started when I wanted to change the custom ROM, before I used ROM Miroom, then I switched to ROM Mi Globe, I have followed all the procedures ..
After I changed to the latest version of Miglobe ROM, suddenly the sensor on my 9T Mi completely died, the gyroscope, the Proximility sensor all didn't work.
And the second problem is that the stabilizer on my 9t mi camera is not as smooth as the default stock ROM, I see the difference, on the custom ROM, the stabilizer on my camera when I record, there is almost no stabilizer effect on the camera..
now I use the stock ROM mi 9t global version 11.0.4, and it does not affect the two problems above .. I feel tired because I have not found the answer
is there any solution ? thank you
Your persist partition got corrupted. Did you do a backup before installing the custom ROM?
no, I never backup persist. every time i replace a different rom i don't experience this problem.
well atleast you know that next time you will.
You can try this: https://www.youtube.com/watch?v=omjoGI3VpPM&t=169s
Basically do a backup of persistbck partition and flash it to persist partition. Altho it my not work. If you expirience some bad behaviour than flash the original (broken) persist back and you will be where you started. If this dont fix your issue than you will have to flash persist.img from fastboot rom. You will lose L1 DRM permanently after doing so.
Related
Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
macnow30 said:
Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
Click to expand...
Click to collapse
You can try to delete /data/system/users/0/fpdata/user.db and /data/system/0/users/settings_fingerprint.xml. Then reboot.
Another possibility is to reflash stock rom, not restore backup!
I have also been through the same situation. Restoring the COS 12.1 will freak out the Fingerprint scanner and camera issue as well. The best option is to flash the Stock ROM COS 12.1.
Happened to me aswell.
I did this:
http://forum.xda-developers.com/zuk-z1/help/fingerprint-stopped-t3290228/post69030576#post69030576
macnow30 said:
Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
Click to expand...
Click to collapse
You can't downgrade android version via backup because each Android version needs different firmware files so if you want to roll back from mm to lollipop you must flash the needed firmware files, you can do that flashing cos12.1 via twrp or fastboot.
Enviado desde mi ZUK Z1 mediante Tapatalk
Hello, since i have restored the stock rom in my A1, the camera (photo/video) started to open really really slow, only after 30 second of black screen the camera starts.What it can be ? I lost my imei before the stock rom restore, maybe is a problem in eis partition
Install module MI A1 Camera Lag Fix Oreo in magisk.
thank u a lot
These lags refer to different camera API used by Google's camera.
Hey guys,
I'm having an issue when updating my Mi A1 with Pixel Experience. After some updates, the FingerPrint stops working. If i'd like to keep it working, i need to downgrade the rom version to the one that was before update.
Anyone is having this issue? There is a fix without clean flash every time that it happens?
I guess its the EFS partition issue (with the data of sensors), if you have a backup, try restoring it in the TWRP, otherwise try flashing stock Pie.
Hello everybody. I have a issue that is litterally making me go crazy. Basically, on every custom rom i've tried so far (Pixel experience both normal and plus, HavocOS, CRDROID, every one of them in their latest versions) video recording through any kind of camera app doesn't work, except for the ANXCamera_Unity_157, where the video recording works, in a very smooth way, but it has a bad video quality, looking like it has a very low bitrate. I unlbocked the bootloader while i was on miui 11.04 global, i wiped everything and formatted DATA through OrangeFox recovery, i'm saying this because i saw that nobody has wiped out the Internal Storage during a custom rom installation. Thanks in advance.
--UPATE--
I tried to flash the miui 10.3.10 through fastboot, and the camera didn't work at all at first, then it asked for permissions and started working, however i still can't record any videos, except for short videos. I tested the hardware and the hardware is okay. Before this i tried to restore a backup that i made on orangefox before any rom flash, and the backup doesn't work. I tried to flash the miui 11.04 global (the rom i had at the beginning of everything) from the recovery, and camera didn't work completely, along the wifi connection (i open the wifi, click on "activate" and it stalles, then turns itself off and makes the phone laggy) i don't completely know what to do, i've been searching for fixes for a bit now and it looks like i'm the only one on the entire world who has this issue. I do really need some help or at least an advice or something
--UPDATE (FINAL)--
While i was too concerned about the video recording i didn't notice that there wasn't a single sensor that was working, so i figured out that the persist partion was corrupted. I fixed everything, video recording included, just by flashing the stock MIUI (11.05) through Fastboot, and then, from the same .tgz file (the fastboot flashable rom, you can find that if you search on the internet), i took the persist.img and flashed it using orangefox recovery, and it's done, i fixed that.
After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.