Related
Hi. I am at a loss on how to fix my GPS on my device. When using Lineage 7.1.2 I can use Google Maps without issue and use navigation to get me places. When I try and use ANY Oreo ROM I can get a GPS lock only on my current location however I can not use navigation; the device stays locked to the start point and will not follow me. When Oreo first came out I was able to upgrade to Oreo and use Maps without issue. I am somewhat a flashaholic and like trying different ROMS to see how they work day to day so I have flashed GZOP, Cardinal, Omni, Lineage 15. I have tried all different Firmware updates by Lord Boeffla trying 4.1.7 (Which I am currently using and Lineage 7.1.2 navigation works) 4.5.0 and 4.5.1 to try and rectify this but it does not matter. No matter what firmware I try and use the results are the same. Lock but will not follow At one point I even tried downgrading to Stock 3.5.4 firmware and software to which I was able to flash but the system would not boot only would bootloop. At this point I am not able to flash any stock OOS ROMS and I must use a custom built ROM such as Lineage to get the phone to boot. I have tried many GPS fix apps such as AGPS to try and force clear GPS cache and reset they system but the results are the same. Lock and no follow. Any ideas on what else can be tried to resolve this? I fear I may have damaged the device throuh flashing the firmware so many times and I will be stuck with Nougat forever with the current phone.
All Oreo ROM's are in Alpha/Beta build stages. I've experienced similar results on many Oreo ROMs. The best course of action you can take is providing logs to the developers of the consecutive ROM, and let them work.
Different firmware versions don't make any difference to the GPS. ROM's are built on top of the firmware, and such. Flashing different firmware's will not fix the issue. Go back to Nougat if you want a stable system.
The issue here is you're complaining about bugs on Alpha/Beta ROM's.
I have been facing the same problem in Nougat Roms too. I think it has been introduced in 4.1.7
The only course of action would be to get it fixed in Beta OOS by providing the logs to the devs.
Here's a related thread :
https://forum.xda-developers.com/oneplus-3t/help/poor-gps-oos-4-1-7-t3664864
Had same issue, refresh latest beta firmware.
I've no issue using gmaps on ob 17 I use it daily.
Hi, I'm facing this issue with my oneplus 3T on custom roms. Doesnt matter if its a 9.0 custom rom or an oreo rom, it still happens and has become very difficult for me to use. I've tried Havoc 9.0, Nitrogen OS 9.0, OmniROM 8.1, Pixel Experience 8.1 but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. How can i fix this? My method of flashing a ROM is:
Wipe Cache/System/Internal Storage/Dalvik etc.
Install oneplus 3t firmware (5.0.6 oreo)
Install Custom ROM.
Install Gapps
Reboot.
P.S. It works absolutely fine on Oxygen OS (5.0.6)
Looking for help. Thanks!
shraey96 said:
Hi, I'm facing this issue with my oneplus 3T on custom roms. Doesnt matter if its a 9.0 custom rom or an oreo rom, it still happens and has become very difficult for me to use. I've tried Havoc 9.0, Nitrogen OS 9.0, OmniROM 8.1, Pixel Experience 8.1 but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. How can i fix this? My method of flashing a ROM is:
Wipe Cache/System/Internal Storage/Dalvik etc.
Install oneplus 3t firmware (5.0.6 oreo)
Install Custom ROM.
Install Gapps
Reboot.
P.S. It works absolutely fine on Oxygen OS (5.0.6)
Looking for help. Thanks!
Click to expand...
Click to collapse
Just a couple of ideas.
Try an older Firmware when you flash a custom ROM. 5.0.4 perhaps.
Double check that you're using the correct Gapps. Opengapps 8.1 or 9.0 depending on ROM, ARM64 Pico. Or try without Gapps.
Ensure TWRP is latest Official.
Do you Format Data when you 'Wipe'?
5.0.4 Firmware
Dirk said:
Just a couple of ideas.
Try an older Firmware when you flash a custom ROM. 5.0.4 perhaps.
Double check that you're using the correct Gapps. Opengapps 8.1 or 9.0 depending on ROM, ARM64 Pico. Or try without Gapps.
Ensure TWRP is latest Official.
Do you Format Data when you 'Wipe'?
5.0.4 Firmware
Click to expand...
Click to collapse
I'm using TWRP 2.3.2
Also, GAPPS are according to ROM, 8.1 or 9.0 ARM64 PICO.
Yes i Format Data when I 'Wipe'!
Still haven't got any fixes for this issues yet
got the exact same problem, on twrp 3.2.3-1, on 5.0.8 firmware and lineageos 16 rom.
it also happens in twrp (after screen timeout after 1 minute, it will stay black).
works fine on oxygenOS, also otherwise works perfectly, until screen lock is ever enabled...
I just bought it used, are you sure you have the original screen? something seems fishy about mine.
I had a regular Oneplus 3 (non-T) before, the fingerprint sensor definitely seems different (deeper down, as if there was a glass protector or the screen was thicker). Maybe that's normal. But the fingerprint sensor also isn't reacting very well - the one on my old Oneplus 3 was MUCH better.
edit:
https://imgur.com/a/Ndvptqg
oneplus 3 on the left, my 3t with the problem on the right. gsmarena lists both models as 7.4mm thickness, so I guess the 3T definitely has a non-standard screen still sad that it works fine on oxygenOS, is there a way to provide helpful logs?
I started experiencing this issue when i replaced my screen for one on Ebay. The notification light and the screen is somewhat dimmer. You can tell its not original.
Hello everybody,
I was just wondering if there's any daily driver Treble roms out there that you would suggest, Thanks ?
I'm using phhtreble AOSP 9.0 v111 (with gapps) on top of Xiaomi.eu 9.1.24 and it's working flawlessly. Only thing I can't test is the screen cast thing, since I don't have an enabled tv and VoLTE since my carrier doesn't use it. Also GCam crashes when trying to use slow mo. One last thing, I'd recommend using Magisk Canary 18.2 since that works. Cheers.
liquid or descendant, im using liquid tho
guglicap said:
... on top of Xiaomi.eu 9.1.24 ...
Click to expand...
Click to collapse
How did you flash MIUI 9.1.24. What I mean did you remove Firmware Update folder from the ZIP or leave it be? I am currently on MIUI 8.7.5 and affraid to get Anti Rollback protection. So I remove this Firmware Update just in case, but after flashing such ZIP my MI8SE doesn't want to boot. It stucks on MI Unlocked logo, it is not even a bootloop.
Doman said:
How did you flash MIUI 9.1.24. What I mean did you remove Firmware Update folder from the ZIP or leave it be? I am currently on MIUI 8.7.5 and affraid to get Anti Rollback protection. So I remove this Firmware Update just in case, but after flashing such ZIP my MI8SE doesn't want to boot. It stucks on MI Unlocked logo, it is not even a bootloop.
Click to expand...
Click to collapse
I think Xiaomi.eu roms shouldn't trigger anti rollback anyway. If you want to be safe flash a China Pie rom, then Xiaomi.eu 9.1.24 then whatever. I think I did china 9.1.3, eu 9.1.24 and PE 190111, but I'm not sure
@guglicap
Thanks for all the tips. Before I had MIUI EU 8.7.5 as a base. I could run most treble GSI, but with some problems and issues (like phone reboot after trying to make call or a few reboots before the system finally started). With MIUI EU 9.1.24 as a base they seems to run much better. I will try to test more features soon.
A few remarks from myself for anyone who wants to try treble GSI:
1. Flash full MIUI EU zip, do not remove Firmware Update folder as I tried before. Firmware Update contains some necessary files to be flash to run latest builds. Regarding the Anti Rollback protection... I had a FALSE response for fastboot getvar anti on MIUI EU 8.7.5, and after MIUI EU 9.1.24 I have anti:1... so it is still safe.
2. Use MIUI 9.1.24 (xiaomi.eu_multi_MI8SE_9.1.24_v10-9) as a base, not the newer builds, as they did not work for me. Also use TWRP 1227 for this build.
3. You can also use MIUI stable 10.2.2 (xiaomi.eu_multi_MI8SE_V10.2.2.0.PEBCNXM_v10-9), but this build works with TWRP 1217.
4. The precedure to run GSI is as below:
a) preferably clean: System, Data, Cache, Dalvik-Cache
b) flash MIUI EU as above, make sure it boots
c) flash treble GSI as System Image (there is many available, I prefer Resurrection Remix, LiquidRemix, HavocOS, AEX, AOISP... I find them the most customizable)
d) clean Cache, Dalvik-Cache, Data (or format Data as an option)
e) disable dm-verity in TWRP => Advanced => RM-dm-verity (very important, as most of the GSI will not run without this step)
What I still need to figure out is:
- encryption (that is a must have for me, so far with no luck on MIUI nor on treble GSI ROMs using the system build in option)
- camera (either working MIUI Camera or GCam, as the AOSP cameras are really bad)
Doman said:
@guglicap
Thanks for all the tips. Before I had MIUI EU 8.7.5 as a base. I could run most treble GSI, but with some problems and issues (like phone reboot after trying to make call or a few reboots before the system finally started). With MIUI EU 9.1.24 as a base they seems to run much better. I will try to test more features soon.
A few remarks from myself for anyone who wants to try treble GSI:
1. Flash full MIUI EU zip, do not remove Firmware Update folder as I tried before. Firmware Update contains some necessary files to be flash to run latest builds. Regarding the Anti Rollback protection... I had a FALSE response for fastboot getvar anti on MIUI EU 8.7.5, and after MIUI EU 9.1.24 I have anti:1... so it is still safe.
2. Use MIUI 9.1.24 (xiaomi.eu_multi_MI8SE_9.1.24_v10-9) as a base, not the newer builds, as they did not work for me. Also use TWRP 1227 for this build.
3. You can also use MIUI stable 10.2.2 (xiaomi.eu_multi_MI8SE_V10.2.2.0.PEBCNXM_v10-9), but this build works with TWRP 1217.
4. The precedure to run GSI is as below:
a) preferably clean: System, Data, Cache, Dalvik-Cache
b) flash MIUI EU as above, make sure it boots
c) flash treble GSI as System Image (there is many available, I prefer Resurrection Remix, LiquidRemix, HavocOS, AEX, AOISP... I find them the most customizable)
d) clean Cache, Dalvik-Cache, Data (or format Data as an option)
e) disable dm-verity in TWRP => Advanced => RM-dm-verity (very important, as most of the GSI will not run without this step)
What I still need to figure out is:
- encryption (that is a must have for me, so far with no luck on MIUI nor on treble GSI ROMs using the system build in option)
- camera (either working MIUI Camera or GCam, as the AOSP cameras are really bad)
Click to expand...
Click to collapse
About camera, this works well for me https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_MI8_V2b_plus3.apk
you need to flash a Magisk module for the fix which is in another thread. Even slow mo works.
Also, I never had a problem with dm-verity, could you elaborate on that? I'm curious now.
guglicap said:
... Also, I never had a problem with dm-verity, could you elaborate on that? I'm curious now.
Click to expand...
Click to collapse
phhtreble AOSP 9.0 v111 ROM worked out-of-the-box, with dm-verity untouched. But for many other ROMs I got bootloop. You need to disable dm-verity to make those ROMs to boot properly.
phhtreble v111 with magisk on top of miui pro seems to work without any problem.
The only bug i experience is that google camera crashes when entering slow-mo mode. Also, notification light works only for charging battery.
Geekbench 4 shows the same results as on miui, battery life seems pretty solid.
Currently using it as daily driver, no problems so far.
adrian.boata.7 said:
phhtreble v111 with magisk on top of miui pro seems to work without any problem.
The only bug i experience is that google camera crashes when entering slow-mo mode. Also, notification light works only for charging battery.
Geekbench 4 shows the same results as on miui, battery life seems pretty solid.
Currently using it as daily driver, no problems so far.
Click to expand...
Click to collapse
does double tap to wake work on you ?
twentyfourinc said:
does double tap to wake work on you ?
Click to expand...
Click to collapse
Hi, apparently it doesn't.
So, after i've spent few days with phhtreble v111, i've noticed the following bugs:
-Bluetooth call doesn't work (the phone rings, music stops playing, but the call runs through the phone speaker)
-Double tap to wake doesn't work
-LED lights up only when charging (Lightflow and other apps designed to take control over it are unable to do it)
-Front facing flash is dead
-Slow motion crashes camera app.
In rest, everything else seem to work fine, even the notch cutout.
Battery and performance are rock solid, substratum is fully compatible.
For camera, i use BSG's Google Camera, which excepting front flash and slow-motion, works like a charm.
Since those bugs are not critical or annoying, at least for me, i currently recommend it as a daily driver.
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
I posted this in the Q&A thread but it looks pretty dead, I can delete that if needed but hoping to get some help on this one.
I had an Android 10 update this morning, and ever since the person on the other end cannot hear me at all. No way to fix, reset etc.
I don't think I can roll back right? My only solution might be to unlock BL and flash custom, because I cannot wait for a patch to fix this.
Anyone have this same issues? Is there an alternative to going custom? If I do go custom what is the closest to stock that actually fixes this?
This sounds like the problem I have been having since December with still no permanent fix. A temporary fix is to turn on the loudspeaker and then back off and the other caller can hear you. Seems the bug will never get fixed after waiting 3 months now for a fix now.
I decided to use a custom Rom (Ion OS is what I'm using, but any AOSP Rom will do), which fixes the issue altogether. Or you could downgrade back to MIUI 10, which I can confirm it also fixes the call audio issue. So, yes you'll need to unlock the bootloader. I tried other MIUI Roms like Mi-globe, Xiaomi.EU, and ROS-MIUI, and all give the same issue. Well, the ones that's base on android 10 give the call audio issue, the ones based on android 9 don't.
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
Hello orangekid, am on the same situation as you was. The 2 mic Works flawlessly when i rec a vidéo or audio memo but when its on call other hear me with buzing and muffling sound.
I am on custom rom Android 11 (EvolutionX 5.3).
Can u plese give me a link to the modem that you flashed in order to ride off this issue.
Thanks in advence
Sld_Ultra said:
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
Click to expand...
Click to collapse
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Sindalf said:
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Click to expand...
Click to collapse
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Thanks for
Sld_Ultra said:
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Click to expand...
Click to collapse
Thanks for the reply, i was with official MIUI 12 globale version , now i am using évolution x 5.3, i have also replaced my screen and only some twrp Works.. the issue it not related to hardware because when i rec a vidéo or audio memo its Works normally, but when calling the sound is muffled and buzing.. i will try to get back to an android 9 rom ? I will try and will see