Database Info

Xiaomi Mi A1 Android 8.0 Oreo FAQ / How to install the latest update for MI A1

Q: I haven't received the lastest security update, how can I get it?
A: Just wait. Updates may take up to two weeks to reach your smartphone.
Edit: there's now an official way to force install updates:
Download and install the latest version of Google Play Services - it's an official signed version, 12.2.17 (448-186052348) (12217448).
Check for updates - you'll receive an update immidiately.
Q: What's the current build number?
A: As of March 1, 2018, the current build is OPR1.170623.026.V9.5.4.0.ODHMIFA Security patch level: February 1, 2018. Kernel version: 3.18.66-perf-g90e3040 [email protected] #1 Mon Feb 26 11:58:45 WIB 2018
Q: Does Picture in picture mode work?
A: It does but only a few apps currently support it: e.g. VLC (it must(!) be enabled first in VLC settings), Google Chrome (for desktop mode), YouTube (YouTube red subscription is required), Google Maps (only in navigation mode) and WhatsApp (during a video call).
Q: What are the known bugs?
A: Check this topic.
Q: Where can I get a firmware image to flash offline (fastboot ROM)?
A: Check this page for updates.
Q: Are there EIS or Camera2API? Has low light camera performance been improved?
A: Sadly, both are still missing and low light camera performance is still horrible.
Q: How can I improve low light camera performance?
A: Root your phone, enable EIS/Camera2API, install Google Camera with HDR+.
Q: Can I use/install Google Camera with HDR+?
A: No. (Yes, if you're willing to root your phone and enable EIS/Camera2API).
Q: I've heard about Quick Charge in Oreo, is it indeed present?
A: No, this has been verified by many people, some of whom used multimeters.
Q: What about the Google Phone (dialer) and Google Messages apps?
A: They are now both stock straight from Google.
Update: The latest version of Google Phone is incompatible with the MI A1 for unknown reasons but it's Google who made this decision.
Q: How can I hide the X mark for mobile networks?
A: You can disable WiFi or you can install a substratum theme, "Hide X".
Q: My favourite app or game crashes under Oreo.
A: Factory reset your phone, install just this game/app - check if it crashes. If it does, contact its developer. If it doesn't then some other app or your settings have broken the app/game.
Q: How can I disable/hide/remove App is running in background notification?
It's a "feature" of Android 8. There are three methods to get rid of this nuisance.
Source: http://en.miui.com/thread-1316545-1-1.html

Please share you tips in this topic.

How to root Oreo,?

mhdsanto85 said:
How to root Oreo,?
Click to expand...
Click to collapse
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.

birdie said:
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.
Click to expand...
Click to collapse
Does It wipe?
And how to go back to stock again to receive otas?

mhdsanto85 said:
Does It wipe?
And how to go back to stock again to receive otas?
Click to expand...
Click to collapse
No. If you install Magisk you will be able to receive and install OTA updates. You'll just have to reinstall Magisk after each update.

birdie said:
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.
Click to expand...
Click to collapse
There is not fully working TWRP for Oreo as of now.
Magisk can be used by flashing patched boot.img, which already contains Magisk or follow a bit complicated TWRP guide.

birdie said:
No. If you install Magisk you will be able to receive and install OTA updates. You'll just have to reinstall Magisk after each update.
Click to expand...
Click to collapse
Are you sure about this?

I got this Decryption Unsuccessful on side B (updated to Oreo on side A), while the side A is working just fine. Can anyone assist me with this?

varben said:
Are you sure about this?
Click to expand...
Click to collapse
You have to restore stock boot before OTA installation, currently that's possible probably only manually.
tensaigandy said:
I got this Decryption Unsuccessful on side B (updated to Oreo on side A), while the side A is working just fine. Can anyone assist me with this?
Click to expand...
Click to collapse
Oreo changed the encryption scheme, only the latest TWRP version or Oreo system supports it. Nougat system and older TWRP versions will have problems with decryption.

_mysiak_ said:
Oreo changed the encryption scheme, only the latest TWRP version or Oreo system supports it. Nougat system and older TWRP versions will have problems with decryption.
Click to expand...
Click to collapse
I tried flashing my phone with latest Nougat, both locked and unlocked bootloader. All fine and good, then I updated to Oreo on my partition B. Worked just fine but I cant boot into partition A as the encryption failed.
Not sure what I have to do on my phone.

Has anyone noticed this thing where if we open a slightly darker or dark image, the display boosts up the brightness in the dark areas ? Sort of like the sunlight display on some phones. I tried to record an instance but it doesn't show it clearly.
https://gfycat.com/MemorablePotableKarakul
Is it just me or Has anyone else noticed it ? Is it something that's built-in or can I disable it ?

Ok so my A1 is rooted bootloader unlocked but for some reason the google camera is not working on this and it used to work on 7.1.2 i enabled HAL3 but still no result can anyone help me

tensaigandy said:
I tried flashing my phone with latest Nougat, both locked and unlocked bootloader. All fine and good, then I updated to Oreo on my partition B. Worked just fine but I cant boot into partition A as the encryption failed.
Not sure what I have to do on my phone.
Click to expand...
Click to collapse
What are you trying to do? Once you upgrade to Oreo, you can't safely boot Nougat system. Even if data wouldn't be encrypted, many apps would force close due to changes between these systems. If you want to downgrade, factory reset is probably inevitable.

_mysiak_ said:
What are you trying to do? Once you upgrade to Oreo, you can't safely boot Nougat system. Even if data wouldn't be encrypted, many apps would force close due to changes between these systems. If you want to downgrade, factory reset is probably inevitable.
Click to expand...
Click to collapse
I dont know LOL
So A/B partition thingy is not a thing anymore on Oreo ?

tensaigandy said:
I dont know LOL
So A/B partition thingy is not a thing anymore on Oreo ?
Click to expand...
Click to collapse
There are still A/B partitions. Could you describe what are you trying to achieve? I simply don't understand why do you try to boot into Nougat once you have successfully upgraded to Oreo.

can future security updates fix these issues as well? monthly updates are provided by google or xiaomi? please answer and add this info to original post

sarfaraz1989 said:
can future security updates fix these issues as well? monthly updates are provided by google or xiaomi? please answer and add this info to original post
Click to expand...
Click to collapse
I could have added the answer but I don't have it.

It is somehow possible to hide/disable update to Oreo? My phone is not rooted.

What about this?

CLT-L29C432B131 firmware improvements

Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot

Well, that's definitely new!

tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places át lower screen part, they changed the circld into square.
More impressions After testing.
CLT-L29C432B131 Camera
Click to expand...
Click to collapse
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???

Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine

halleyrokz said:
Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine
Click to expand...
Click to collapse
From FirmwareFinder:
This update optimizes system performance and stability.
Optimizes power consumption for longer usage.
Improves system performance and stability for smoother operations.
Optimizes the wallpaper display for a better experience.
Fixes an issue where the other party's voice was occasionally delayed when answering calls while using OK Google.
1. This update will not erase your personal data, but we recommend that you back up any important data before updating.
2. The system will restart after the update. This will take about 5 minutes.
3. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.

tsiglas said:
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???
Click to expand...
Click to collapse
OK. Sure.
But it will take time.
I'm not a professional shooter, so basically I probably won't notice the differences too fast.
One thing I have observed is that the portrait selfie mode was improved, it's more natural.
Others I will test.
But again: with HuRupdater you can update easely.
(downloading 3 of 4 files from update packages: the choice is between clt-l09 and clt-l29, after that renaming and flash via twrp. See corresponding thread)

Interesting.. so it seems indeed that many of the under the hood changes are not always mentioned in the change log.
Yeah please keep us posted on the camera improvements and performance and power consumption.
tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot
Click to expand...
Click to collapse

I updated it to it yesterday but besides the zoom button form nothing changed the selfie camera still creey as before and the video recording also no stabilisation for 4k and no 60 f0s for 4k, huawei is doing nothing

tamaskurti said:
So far they have included camera improvements.
Click to expand...
Click to collapse
How about the front-camera, can you turn off beauty mode? i set it to 0 but still on almost the same.

I've just tried to update using the HuRUpdater method but wasn't able to boot afterwards. Tried flashing twice but it just wouldn't boot to system. I've restored the TWRP backup I made before flashing and got back into system, now settings says I'm on .131 but I can't be if I just restored a .128 backup, right?
What's everyone's update method? Did you place custom recovery in the folder too or flash without? Wipe cache/dalvik after? Boot to system first before flashing Magisk or just flash directly after HuRUpdater script?
Want to try again but just wanted to check if I've missed something? Thanks!

just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches

kaiowas82 said:
just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches
Click to expand...
Click to collapse
Reckon it would be safe to flash using the NoCheck Recovery method?

danifilth4king said:
Reckon it would be safe to flash using the NoCheck Recovery method?
Click to expand...
Click to collapse
i don't know mate, i used hurupdater, as i said before, and all went smooth...

kaiowas82 said:
i don't know mate, i used hurupdater, as i said before, and all went smooth...
Click to expand...
Click to collapse
Did you use official or unofficial TWRP?

You need to use unofficial twrp as only that one can decrypt storage (remove security settings first: no pin/ fingerprint).

danifilth4king said:
Did you use official or unofficial TWRP?
Click to expand...
Click to collapse
unofficial

kaiowas82 said:
unofficial
Click to expand...
Click to collapse
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/

danifilth4king said:
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/
Click to expand...
Click to collapse
I created a new folder with inside the hurupdater script and the three zips downloaded from firmware finder, no recovery img or else.
flashed the script, wiped cache and dalvik and rebooted straight to system.
rebooted to fastboot to reflash the praetoriano recovery, reboot to recovery to flash magisk and that's it.
I'm afraid i cannot help further

I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?

isko01 said:
I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?
Click to expand...
Click to collapse
The cn firmware was updated too to version B123.
Remember, they have different numbers. Ex. Their B123 version is newer than our B131.
Look at production numbers in Fw.

Android 10 OTA released again.

I just got ota update released again, it is 1.15 GB, i will wait with update.
I am located in Eastern Europe. Good luck

Have received the notification.
Can confirm the size.
Will not install it for now.

I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.

underdoq said:
I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.
Click to expand...
Click to collapse
I'm also on Pie. I have received the notification am the size is what you mention (1.15gb) but since is brting problematic, I will not install for now.

I just got it too, should i update?

Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install

AnonymousAL said:
Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install
Click to expand...
Click to collapse
Is it the same update as few days ago?
11.0.4? If yes ,then I wonder why they stop the OTA just to start it over without changing/fixing anything...
It's like xiaomi devs are a bunch of amateurs who doesn't own this device therefore unable to test their updates and just hope for the best when they release one...

Yes it's the same 11.0.4.0

AnonymousAL said:
Yes it's the same 11.0.4.0
Click to expand...
Click to collapse
Thanks for the reply!

gonna update until they pull it back again

I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.

digitri said:
I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.
Click to expand...
Click to collapse
There's a process for applying the OTA or a fastboot image you can use to upgrade.
I expect you'll get a OTA offer soon anyway. I just missed it last time but got it now. OTA from 10.0.20.0

Thread closed
Please use existing threads like this
strongst
Forum Moderator

Worth it to upgrade from Android 10 Sept 2020 to Android 11 right now or wait?

Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!

I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk

I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.

I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.

I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.

I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.

Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.

A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.

qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.

Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.

kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11

New StatiXOS OFFICIAL 4.2 build for Essential PH-1

StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"

For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.

Thanks you very much
I will test

Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.

aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?

Just a question, does StatiXOS have slim recents included?

Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.

Is anyone else having issues with sending a text message with this rom?

vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off

vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off

Double Post

Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.

chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..

The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.

SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.

kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.

SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.

aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...

This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?

chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.