Related
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.
I am having a screen bleeding issue in my pixel experience rom 11/21
Magisk flashed
nothing else
the screen bleeding does exist in twrp as well
Can anyone tell me the solution ?
P.S.: I'm not allowed to send screenshots being a new member.
Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)
htchd2sucks said:
Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)
Click to expand...
Click to collapse
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
DarkLegend_1943 said:
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
Click to expand...
Click to collapse
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.
htchd2sucks said:
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.
Click to expand...
Click to collapse
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....
DarkLegend_1943 said:
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....
Click to expand...
Click to collapse
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?
htchd2sucks said:
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?
Click to expand...
Click to collapse
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.
DarkLegend_1943 said:
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.
Click to expand...
Click to collapse
https://in.c.mi.com/thread-714161-1-0.html
Seems easier than going through twrp. Although flashing latest miui rom should not trigger arbV4 protection so should not brick anything.
htchd2sucks said:
https://in.c.mi.com/thread-714161-1-0.html
Click to expand...
Click to collapse
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version ??
DarkLegend_1943 said:
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version
Click to expand...
Click to collapse
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
freezing msa will disable adds I guess!
DarkLegend_1943 said:
freezing msa will disable adds I guess!
Click to expand...
Click to collapse
https://mi-globe.com/rom-builder-features/?codename=whyred&img=redminote5pro.png&realname=RedMi+Note+5+Pro
I think that was the link, not entirely sure, I never found it again.
In that link it talks about installing ad blocker. I kind of remember that we could turn off some ads service in the MIUI rom custom thing...
Well that seems a good workaround anyway!
It even have clear instructions from TWRP:
https://mi-globe.com/globerom-rom-builder/
htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?
DarkLegend_1943 said:
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?
Click to expand...
Click to collapse
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).
htchd2sucks said:
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).
Click to expand...
Click to collapse
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.
DarkLegend_1943 said:
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.
Click to expand...
Click to collapse
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
pannel is from official vendor
htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
now facing screen burning ! I'm installing miui today I guess that's the most optimised rom.
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.
Just received this
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Oh no, seems like I have to stuck in version 10.0.10.0 forever ... :crying:
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Hopefully we will get it back with Android 10. I'm using superior os 10 till we get it.. so far it works pretty nicely.
Also got the update. The size looks ok for a simple security patch and minor fixes so nothing major.
Phone starts ok, no problems so far.
This is the first update that no one is complaining about yet... so it's a change in the right direction for the Xiaomi OTAs.
Xiaomi Mi A2 users (they got it 3 days earlier) said that it even works fine with Magisk.
I had 2 odd things happen as a result of installing this OTA.
1) USB Debugging was turned off. No other developer things seem to have changed, just that toggle was off.
2) My timezone was changed. Almost like the phone temporarily forgot I didn't want to use network-provided timezone (it often picks the neighbouring state, which has a 1-hour offset from here).
I've never had this happen with previous OTAs.
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
My dad didn't have this issue. Make sure it isn't your network provider having this problem
If you don't enroll your fingerprint before updating to v 10.0.16 ,you can't do it after the update
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
Hello, if someone is experiencing the same problem, I resolved it flashing the official stock rom with Miflash tool. Cheers
This update has definitely done something to the signal mine is falling onto 2G a lot, before that I was steady on 4G. Once it hits 2G it stays on it regardless of the signal strength until you restart the phone. It is very annoying.
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
downloadonlyaccount said:
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
Click to expand...
Click to collapse
This sounds like the known issue with new/fast cards. There's a thread where it was discussed.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
That's a problem that sometimes occurs since Pie came out. Restarting the mobile should fix it.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
My multitasking seems to be very bad after the update...
Hello,
I have Mi A2 lite with magisk installed, and I am unable to perform the november OTA update.
here is what I do:
1. In magisk : Uninstall > restore images
After doing this, magisk still looks the same:
2. Launch the OTA update.
I first have this screen:
red message translation: "Install will resume when the phone is not active. Click on resume to finish installation now"
3. Clicking on resume will start the installation, but it fails after some moment:
4. After that, I go back to Magisk: Install > Direst install to avoid having Magisk uninstalled after reboot. When doing this, here is the screen:
I don't understand why my OTA is refused...
Is there something to setup in magisk hide ? In order to hide magisk from the OTA updater ? or anything else ?
/system could have been modified, you can try flashing only that partition to solve the issue
nehuy said:
/system could have been modified, you can try flashing only that partition to solve the issue
Click to expand...
Click to collapse
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
takhama said:
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
Click to expand...
Click to collapse
The upgrade tool writes a log to logcat. It says which partition it does not like.
adb logcat | grep update_engine
There have been no fastboot image released for 10.0.15.0. I have backups of both system and vendor (since they both seem to be modified every OTA for me). If you can confirm that either of these is needed I can try to upload it somewhere. Note that these are very large partitions.
Alternatively, you could use the 10.0.13.0 fastboot and OTA from there. Make sure to backup data before doing this.
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
applesucksLmao said:
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
Click to expand...
Click to collapse
Hey, did you ever find out something?
I just got that problem too
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Captain_cookie_200 said:
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Click to expand...
Click to collapse
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Mighty_Rearranger said:
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Click to expand...
Click to collapse
i see..