Related
Hi everyone,
I bugged HMD about not releasing more recent source code for the Nokia 8 and a few days ago they updated their site with links to code for the Android 9 builds. Note they still haven't published the latest build (5.150) nor and 4.88 builds nor any Android 7.1x builds.
I checked the archives and they are different from the previous 4.84 release, but I've no idea if they are buildable. They still look like they might be missing some useful bits, from my limited knowledge. Those of you who know what to do with this can test it and see if it's useful to you.
Let me know if you would like me to keep bugging them about the 4.88 build's code, or even any earlier 3.x builds.
Have fun!
Cheers
Thanks for bugging them!
Sadly it still contains the same device tree typos that the previous NB1 and even A1N sources contained, so without fixing them those trees do build but won't work correctly as the display won't be accessed correctly (half the screen will be white IIRC).
To be clear, this is what I mean: https://github.com/resident-nokia/u...f68ad2f#diff-6ea71fa79b281dd80cbab0bea96d9472
Also, as a funfact: A quick diff I did showed that the 5140 source is identical to the 4120 kernel source from Nokia 8 Sirocco that was released around December if I am not mistaken (minus the device tree files and some places where device names were hardcoded). That would mean that our kernel hasn't seen an update since December (actually even September, since thats the first CAF tag (Qualcomm upstream) that has changes you can find in those sources). Customer service I guess ¯\_(ツ)_/¯
Hi @THMSP!
Thanks for checking it out, shame it's still got errors in it. That's very interesting about the comparison with the Sirocco and the last change being in September. I suppose a new build doesn't automatically mean a new kernel though.
Since both the Android 8 and 9 source contain errors my only wonder is if the Android 7 source would also have errors, or if it might actually work?! I will ask them for it.
Cheers
EDIT: So the device tree is there after all? I had obviously misunderstood some of the other conversations I'd read, I had always thought it was missing. So it seems the device tree is there, but broken? Or only partially there, and what is there is broken?
The device tree files are all there, but they contain four serious typos that cause them to not actually work when you boot your compiled kernel. The rest of the source code does work. Correcting those typos is not much of a deal, but it is annoying (and personally I wonder how on earth they even maintain these sources).
The other annyoing issue is that for any custom or mismatching kernel the wifi driver won't load (because of signature enforcement for kernel modules), so if you want to make a kernel that doesn't break wifi, you need to add the Qualcomm wifi driver yourself (which then requires additional patches to actually work as well).
When you do those two things, the kernel will work just like the one that Nokia is shipping. For example, my TWRP builds for NB1 actually use the kernel source code for Sirocco, but with the (corrected) device tree files from NB1, and a patched version of the qualcomm wifi driver compiled into the kernel directly.
I am not sure if the nougat sources would help that much to be honest. It's not like those sources are broken because HMD / FIH don't know how to fix them, I bet they break them on purpose (or they get broken by the tool they use to package them). So any further release by them will probably contain the same stupid errors.
Wow! That's a lot to do to make them usable. I agree that I have many questions about QC and QA in the software for these phones, not only because of the source code releases.
You did very well making the device tree for the NB1 then and getting TWRP running, well done! And thanks
Like many I'm interested in the possibility of running other OSes on the NB1, particularly /e/ and any that run on Halium. I presume it will still take a lot of work to get another OS running on the NB1, but is it doable? I think in all cases these projects start from a LOS base.
Cheers
madb1lly said:
Wow! That's a lot to do to make them usable. I agree that I have many questions about QC and QA in the software for these phones, not only because of the source code releases.
You did very well making the device tree for the NB1 then and getting TWRP running, well done! And thanks
Like many I'm interested in the possibility of running other OSes on the NB1, particularly /e/ and any that run on Halium. I presume it will still take a lot of work to get another OS running on the NB1, but is it doable? I think in all cases these projects start from a LOS base.
Cheers
Click to expand...
Click to collapse
Most of the work regarding TWRP and the kernel was actually done by @dg28gadhavi - I just tried to update everything a bit and adapt it to all the new bootloader bugs features that were introduced over time. He deserves all the credit, otherwise I would've had nothing to learn all this stuff from.
Regarding custom ROMs: Sure it is possible. But it is a huge amount of work, that requires you to risk your device (Snapdragon chips are unbrickable, but you couldn't use it as a daily driver), with potentially very few people actually caring (or even donating etc.). When you reached the point where you are able to port a ROM, you have the knowledge to make the changes that you need yourself with Magisk as well. So the only real reason to port a ROM is to give something to the community. And the Nokia 8 community simply isn't big enough that anyone would do that, imo.
Well thanks for @dg28gadhavi as well then!
Yes, I have read that Magisk can do most of what a custom Android ROM might have done. I have some reservations about Magisk, since it's not open source I don't know if I fully trust it, but that could also be the case for most of the software I use! Personally I'm interested most in /e/, which is currently built of a LOS base, but I don't know if all the customisations they've done (mainly to remove any communication with Google services) can be done with Magisk.
As for Halium-relate OSes (Ubuntu Touch, Plasma Mobile, Sailfish OS, LuneOS... some others too), Magisk can't recreate those as they're basically completely different from Android, they just run off the Android kernel and use libhybris to interface with the Bionic library drivers; the rest of Android is not used.
Anyway, this is all beyond my available time at present, so I will just have to carry on with stock Android maybe with some Magisk customisations until my phone breaks!
Cheers
madb1lly said:
I have some reservations about Magisk, since it's not open source I don't know if I fully trust it
Click to expand...
Click to collapse
Magisk is completely opensource, it has always been: https://github.com/topjohnwu/Magisk
You might be thinking about SuperSU which was / is indeed closed source
Hello, I am officially downgrading back to Oreo now due to not seeing bugfixes from Xiaomi for several months on common problems reported by many people to Xiaomi ever since Android Pie update was pushed. They did not fix anything, and it does not look like they will either.
Let me debunk for you my thoughts on Android One and how Xiaomi has handled it:
- We are guaranteed two major updates and security patches, but we are not guaranteed any stability or bugfixes! This is just a cheap update to Android Pie with only security updates being pushed, and I find it absolutely unacceptable. Xiaomi probably does not want to give resources to such a unpopular not profitable or well-selling device (compared to their other devices and MIUI) and are just delivering the minimal they have to in order to stick to and fulfil the conditions set in the Android One project.
- I noticed not only lower battery lifetime, but also several bugs. This includes completely random MASSIVE lags in for example something as simple as using Google Maps (nothing else being used on my phone when lagging!)
- My Wi-Fi not working well at all taking a long time to scan and connect, not being able to connect to hidden networks AT ALL
- Random crashes even when I was on my way to an important exam and even "freezing" up in calls and weird buzzing screeching noises in calls.
- I have LTE, but I cannot call over VoLTE or VoWiFi, because this phone does not have the support for my carrier. My phone calls now go through 2G! While my Apple, Samsung and Huawei friends are laughing at me.
- My friend reported one of his speakers DIED on him not even half a year after the purchase.
Note, I have done factory resets, I have tried to give it a chance, but it just doesn't improve. This is a horrible device, and that is my 2 cents.
You should not buy phones just from the specifications you see it has, you should care about plenty a other things that might be wrong. I have decided to go back to Oreo, and at least have a decent device, and I think you should too, which is why I am sharing this with you. Will I buy another phone from Xiaomi? I am not so sure after this ...
How you do it is simple, you just download the latest Oreo OTA: V9.6.10.0.ODLMIFF, do OEM unlocking and flash it using flash_all_lock_crc.sh on Linux or the flash_all_lock_crc.bat on Windows (will erase all data NB)
Join me downgrading to Oreo, WARNING: Only at your own risk!
Need drivers, download the fasboot package binary for Linux or Windows from Google and install Xiaomi ADB/Fastboot drivers, for Linux it is not necessary when I tried it:
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
1. Download the latest 8.1 OTA http://bigota.d.miui.com/V9.6.11.0....0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
2. Enable developers options by tapping the build number in about phone multiple times, and in developer options enable OEM unlocking
3. Shut the phone down, hold the volume down when plugging it into the PC or hold the volume down + power to enter fastboot mode (you should see it say fastboot and the Mitu mascot).
4. OEM unlock using command "fastboot oem unlock" WARNING: Full data wipe, unless you hold volume down you might be able to stop this, look for other threads on xda-developers for this.
5. Flash using flash_all_lock_crc.sh on Linux or the flash_all_lock_crc.bat on Windows, maybe you can use the ones without data wipe, again you should take backup of your important data!
6. Enjoy a not so terrible device
Now I just have to figure out how to stop auto-downloading of May OTA and notifications about updating, probably needs root?
EDIT:
Can go into Developer Options and disable Automatic system updates
I complete agree with you bro, Android One is almost like we are beta testers for all the time. My Mi A2 lite give me some annoying issues:
1) Bluetooth don't work proprely with my sound car system (freeze the music when I take in my hands or the road shake the device);
2) Autofocus don't work for Gcam in low light and even in the stock app camera the focus isn't correct edge to edge, making some softness in the corners;
3) Hotspot wifi router works for some minutes and for nothing the mobile data stop.
4) Ram management is a rubbish, just opening the camera any other application reload;
After all I understand Samsung and others Brands for delay updates, at least is not full of bugs like Xiaomi (same with MIUI).
if you only downgrade, without patches or fixes, android 8.1 will be a pain in the ...
the anti-roll back politic of xiaomi only makes harder to downgrade...
NeoZX58 said:
if you only downgrade, without patches or fixes, android 8.1 will be a pain in the ...
the anti-roll back politic of xiaomi only makes harder to downgrade...
Click to expand...
Click to collapse
And about customs ROMs? They are more stable and bugfixeds than stock or not reliable yet? Actually I prefer to install Pixel Experience (Pie) and not downgrade to Oreo.
I like pir granted I never use stock ROM custom is the way to go
Yep pie OS definitely consumes more battery than oreo and I'm almost tempted to role back to oreo just to have more battery life.
I'm currently using lineageos by 33bca it's very stable, I recommend you to give it a try. The only thing I hate is that the ram management is really awful (both with stock and custom rom), most of the time the phone has to reload the applications even if I only have 2 applications opened.
Are you having some problem with sim/network? Because I saw in some post a fix to use after downgrading from pie to oreo.
I never upgraded from Oreo to Pie. Looks like i made the right choice.
gatomestre08 said:
I complete agree with you bro, Android One is almost like we are beta testers for all the time. My Mi A2 lite give me some annoying issues:
1) Bluetooth don't work proprely with my sound car system (freeze the music when I take in my hands or the road shake the device);
2) Autofocus don't work for Gcam in low light and even in the stock app camera the focus isn't correct edge to edge, making some softness in the corners;
3) Hotspot wifi router works for some minutes and for nothing the mobile data stop.
4) Ram management is a rubbish, just opening the camera any other application reload;
After all I understand Samsung and others Brands for delay updates, at least is not full of bugs like Xiaomi (same with MIUI).
Click to expand...
Click to collapse
Seems like more of the same issues I have experienced, it is simply not good enough for what would be expected of day-to-day use. I think we got exactly what we paid for with this device, sadly, and from what I know the Pie update already released to for example S8 and it is working perfectly well and stable for those. But, again, much more popular and well-financed device than our cheap A2 Lite.
NeoZX58 said:
if you only downgrade, without patches or fixes, android 8.1 will be a pain in the ...
the anti-roll back politic of xiaomi only makes harder to downgrade...
Click to expand...
Click to collapse
For me this has been the easiest device to downgrade. Xiaomi hosts the OTA officially, OEM unlocking simply by an easy command no phone or e-mail verification just like the Pixel(Probably Android One related), and they made the script to downgrade it for you. I had much more trouble before on other devices. like Samsung using ODIN, Xiaomi with MIUI and similar, having to go through a verification by e-mail to unlock at HTC etc etc. I do not get what you are on about?
Also, why is it a pain without patches or fixes? It is much better than what you get with Pie so far, at least that is for me. There is way more lacks of patches and fixes for Pie than for Oreo ...
Remember, this was the last version released just before the May Pie update, it is very recent in itself only by some 7 months ...
anzhaki said:
Yep pie OS definitely consumes more battery than oreo and I'm almost tempted to role back to oreo just to have more battery life.
I'm currently using lineageos by 33bca it's very stable, I recommend you to give it a try. The only thing I hate is that the ram management is really awful (both with stock and custom rom), most of the time the phone has to reload the applications even if I only have 2 applications opened.
Are you having some problem with sim/network? Because I saw in some post a fix to use after downgrading from pie to oreo.
Click to expand...
Click to collapse
I really wanted to try the custom ROMs, but I have banking apps that complain to me if my device is rooted or similar, and refuses to run. These are important apps for paying for goods and services that you need in order to go about your life normally. I can get around it using Magisk Hide, but I would rather not
SIM/network problems actually worked fine on Oreo and Pie (official ROM) for me all the time. I can use 4G LTE band20 perfectly and other bands to access internet, and it immediately connects to 2G/3G(3G being closed in my country soon for 4G and 5G improvement) for calls when it needs to. Coverage is also well in my country. My company use Ericsson base stations and not Huawei ones, but not like that matters.
gatomestre08 said:
And about customs ROMs? They are more stable and bugfixeds than stock or not reliable yet? Actually I prefer to install Pixel Experience (Pie) and not downgrade to Oreo.
Click to expand...
Click to collapse
pixel experience, AOSiP and Lineage are the best custom Roms so far, but, my issue is from RAM management in android Pie (custom or stock).. after hours of use the phone becomes unusable... :/
courfazor said:
For me this has been the easiest device to downgrade. Xiaomi hosts the OTA officially, OEM unlocking simply by an easy command no phone or e-mail verification just like the Pixel(Probably Android One related), and they made the script to downgrade it for you. I had much more trouble before on other devices. like Samsung using ODIN, Xiaomi with MIUI and similar, having to go through a verification by e-mail to unlock at HTC etc etc. I do not get what you are on about?
Also, why is it a pain without patches or fixes? It is much better than what you get with Pie so far, at least that is for me. There is way more lacks of patches and fixes for Pie than for Oreo ...
Click to expand...
Click to collapse
nope, if you only do this, you don't have RIL, can't record videos from camera and only one sim works...
i told you because i did it, you need a several fixes for sim, modify files in the official OTA to flash more files and need the modem pie img and flash it too...
i agree that the android one program wont ever give us a solid flawless build, after all it is ment for lower to mid range devices that will be quickly overlooked after release , i must admit this a2 lite is the best phone i have had so far even with the instabilities but thanks to the xda community i have been able to make the device truly mine and how i like it. i had to get this device after my nexus 5x broke during in a motorcycle accident, it was all i could afford and it performs well for my needs, i did install twrp and Butterfly for Daisy to fix the GCam mis focus issues, eventually i gave in and installed magisk to manage tge kernel with arduitor and increase battery life. i never had the luxury to run Oreo on this devixe because as soon as i got it i unlocked the bootloader and when it restarted it booted into the updated pie partition and i decided to run with it. i dont think xiaomi or Google will actually fix any bugs but we are on XDA and DIY is always an option.
NeoZX58 said:
pixel experience, AOSiP and Lineage are the best custom Roms so far, but, my issue is from RAM management in android Pie (custom or stock).. after hours of use the phone becomes unusable... :/
Click to expand...
Click to collapse
Not good. I think this was the same massive lagging issue I experienced, I just did not know it was due to bad RAM management. Is this a fix that needs to be done to the ROM directly or only the kernel? I am not familiar with custom ROM/kernel development that much, but I have experienced some kernels on devices working much better than others like ElementalX.
NeoZX58 said:
nope, if you only do this, you don't have RIL, can't record videos from camera and only one sim works...
i told you because i did it, you need a several fixes for sim, modify files in the official OTA to flash more files and need the modem pie img and flash it too...
Click to expand...
Click to collapse
I am able to record videos from my camera perfectly, it works very stable. I used this version of Oreo just some months ago and it worked great. I have the version with 4GB RAM and 64GB eMMC. I think the reason I experience no issues is because I only use one primary SIM for 4G and calling in SIM slot 1, and do not have a use for the 2nd SIM slot so for me, it is perfect, but too bad for the people that actually needs this feature like you About updates to RIL I assume the firmware used for modem/calling, which for me works so any updates are not that needed for me to have it working perfectly.
Azatecas said:
i agree that the android one program wont ever give us a solid flawless build, after all it is ment for lower to mid range devices that will be quickly overlooked after release , i must admit this a2 lite is the best phone i have had so far even with the instabilities but thanks to the xda community i have been able to make the device truly mine and how i like it. i had to get this device after my nexus 5x broke during in a motorcycle accident, it was all i could afford and it performs well for my needs, i did install twrp and Butterfly for Daisy to fix the GCam mis focus issues, eventually i gave in and installed magisk to manage tge kernel with arduitor and increase battery life. i never had the luxury to run Oreo on this devixe because as soon as i got it i unlocked the bootloader and when it restarted it booted into the updated pie partition and i decided to run with it. i dont think xiaomi or Google will actually fix any bugs but we are on XDA and DIY is always an option.
Click to expand...
Click to collapse
But it was actually working well enough for me too on some of the builds, but I do agree that it is probably not a phone that was meant to be supported for long. Another person I know has the A2 model, and he says it has been working perfectly well for him for all this time even on latest Android Pie. I do not know if there are much differences between them, but I do know the A2 is a much more popular device. Personally I prefer the A2 Lite just for the audio jack, and I still like the legacy MicroUSB. People would call me mad for this, but haha, that is just who I am.
I am afraid this device is not nearly as popular to get enough DIY effort into making a custom ROM/kernel, I am certainly not anyone who knows enough to get into development of it. I hope it will go well and that somebody will take the challenge, or maybe it has already happened?
courfazor said:
I am afraid this device is not nearly as popular to get enough DIY effort into making a custom ROM/kernel, I am certainly not anyone who knows enough to get into development of it. I hope it will go well and that somebody will take the challenge, or maybe it has already happened?
Click to expand...
Click to collapse
i actually think the mi a2 lite is more popular than the regular A2, it has more features and a better battery for a cheaper price so it is more accessible to more people and therefore more reach developers. Butterfly for Daisy is a great Custom Kernel that fixes some issues including the GCam focus issue among other things on Pie, i highly suggest you read that thread to see if it offer solutions to some of your issues with the device. im still running stock Rom with the custom kernel and everything works great. others have reported Resurrection Remix/Puxel Experience/ and Lineage Os bring additional stability and fixes in coordination with the kernel. i havent found the need to try a custom rom yet but development is very active on the device. however it is a low end phone and QA is not as good so some devices might be lemons straght out of the factory and not perform as good.
I have almost no issues with my Mi A2 Lite. No slowness except what I expect from a $159 phone, GPS works, bluetooth works albeit I hate that they removed AAC, WiFi is perfectly fine and maxes out my connection with bluetooth on. Only thing I don't like is how crap calling is, but I figured that would be the case when I bought it at again, $159 and knew some American bands were missing. Battery life is 8-11 hours of SOT with regular usage. I use the IR blaster to control my stereo receiver, FM radio is nice. Glass has some light scratches, but again I expect that for $159.
I have a brand new never opened Oreo Mi A2 Lite in my desk drawer still in the box that I haven't felt the need to pull out yet. I think as someone else has pointed out, there may be two hardware revisions because mine is fairly flawless.
I downgrade my Mi A2 Lite to Oreo V9.6.6.0.ODLMIFF (August 2018) and was surprised how good and perfect is this version, looks like I have an new Smartphone. Now Bluetooth works perfect, Gcam Autofocus is accurate, fine RAM mannagement, battery life is great, only miss FM Radio.
Mi A2 Lite was arruined by Android Pie.
Shame on you Xiaomi, I'm very disappointed with the crap updates that we received from you, seems like your only purpose is for the users buy an new one device.
anzhaki said:
Yep pie OS definitely consumes more battery than oreo and I'm almost tempted to role back to oreo just to have more battery life.
I'm currently using lineageos by 33bca it's very stable, I recommend you to give it a try. The only thing I hate is that the ram management is really awful (both with stock and custom rom), most of the time the phone has to reload the applications even if I only have 2 applications opened.
Are you having some problem with sim/network? Because I saw in some post a fix to use after downgrading from pie to oreo.
Click to expand...
Click to collapse
For the ram management... open your kernel 'tweaker' app and disable 'Adaptive Low Memory Killer', it seems to like killing apps on background, even with enough ram to spare... It'll make no magic, but definately helps :highfive:
Sorry, needing Help.
Could you please post a tutorial for this, or a good noob Xiaomi step by step? I have unlocked my phone a few months ago. I don't remember how I did it. I have since moved to another phone. I have installed twrp and had it rooted with majisk. a factory reset took care of majisk. I would love to go back completely to stock oreo.
I only need one slot on the sim so this should be ok.
Your directions for install sound good but seems like something might be missing. I'm new to the xiaomi devices. They seem way more comlicated than all the Samsungs I've had.
PLEASE, and thank you:good::good:
Rev10eight said:
Could you please post a tutorial for this, or a good noob Xiaomi step by step? I have unlocked my phone a few months ago. I don't remember how I did it. I have since moved to another phone. I have installed twrp and had it rooted with majisk. a factory reset took care of majisk. I would love to go back completely to stock oreo.
I only need one slot on the sim so this should be ok.
Your directions for install sound good but seems like something might be missing. I'm new to the xiaomi devices. They seem way more comlicated than all the Samsungs I've had.
PLEASE, and thank you:good::good:
Click to expand...
Click to collapse
All your data on phone will be lost , take back-up on PC if necessairy.
For full stock rom , download Miuflashtool zip. extract and install on your PC, download stock rom for your phone on your PC and extract it , boot into fastboot and connect your device to PC ,in flashtool click on refresh, your device should appear ( numbercombination 225cc80.... or something like that) click browse in the left corner and select the extracted stock rom file, hit flash and wait till you see succes in green on the right . Your device will take about 10 min to boot . You're now on stock rom, locked bootloader, no root and stock recovery . I flashed my device MiA2 lite) yesterday with latest Pie stock rom after I had bootloop
bricked it. I don't now about oreo stock rom , there could be issues with network connection, video playback and swapped simcard because of anti rollback protection.
Thank you so much.
That was super simple and super quick. I am back to stock Pie, unrooted and and the boot loader is locked again. I used OREO and the phone works fine. Make sure you disable update or it will update to pie. I need to redo it to go back to oreo.
I want to downgrade. What about second sim slot OREO error ??? What version is the best? And what version havent bluetooth/wifi/gps issue? I dont remember what version I was at last on oreo.
Howdy all! I've dug out a couple old Nexus 5's that I stopped using a while back when I got PH-1 and am looking to reflash one of them for a friend who needs a phone and can't afford to buy new. When I was using them last I was running LineageOS 14.1. I'd like to set him up with something stable that he can use as a daily driver for a while and was looking for suggestions. It looks like a ton of ROMs have been updated and I was hoping someone could point me in the right direction for a good current setup that will be easy on the battery and have the most features without compromising stability. Is there a commonly accepted "best" Nexus 5 build? I'm good at following directions, but a lot of the technical stuff is over my head, so trying to research everything I've missed for the last couple years is making my head spin lol. Any assistance would be greatly appreciated!
Stable ROM for Nexus 5
Hey,
I have found AOKP to be really good for my Nexus 5. It has the stability of Lineage 14.1, but also has a few nice little additions: OMS support for Substratum, customisable navbar, a few tweaks here and there. And it is still being developed, and receives regular updates.
Not too heavy on the fancy stuff, so for me it's a nice tradeoff between "stock" AOSP/Lineage, and a few little enhancements.
Also the Nexus 5 is officially supported by the developers, which is important to me.
I've tried Android O and Android P ROMs on my Nexus 5, but I still find Nougat ROMs seem to run the best.
I also have a Nexus 7 (2013) tablet, and the ROM is also available for that as well. As I have OCD, I "need" both my phone and tablet to run the same system, and AOKP gives me this.
Just my suggestion, anyway. Give it a try, and see what you think.
Cheers
Shaun
Thanks! I will check it out
if you like simpler thing i would suggest LOS 14.1 even tho our hammerhead are not supported officially you can use unofficial build by razorloves here https://forum.xda-developers.com/showpost.php?p=80268653&postcount=3145 or another one here https://forum.xda-developers.com/showpost.php?p=80210774&postcount=3 they updated it once a month at least with security updates each months
also if you want tor try LOS 14.1 CAF you can try this https://forum.xda-developers.com/showpost.php?p=80340013&postcount=753
I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.
petersaints said:
I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.
Click to expand...
Click to collapse
Hey Peter - thanks for the nod
I acknowledge that AOKP's security patch level is a bit dated, but having used LineageOS for a long time, I found some of the features AOKP throws into Lineage, I'm willing to sacrifice that for the extra goodies AOKP offers.
I have decided to stick to Nougat for as long as I can. I tried Oreo and Pie, and had noting but trouble with Bluetooth. It's such a shame when they bring out such a solid, stable release of Android like Nougat, and then stop supporting it because it's not "the latest".
Just as an aside, I have recently been using MicroG (Nanodroid package) instead of GAPPS on my N5 (and my N7 2013 as well), and have found it to be very usable now. Google Pay does not work, but aside from that, I get much better battery life than using GAPPS. In fact, my location accuracy seems to be better, and I've got Play Store working a treat.
Hi there, I have the same problem, my N5 stayed on last security patches from the official rom in Feb 2019. Then Lineage ended official support. Did someone try to install the unofficial version (made by razerlove) over the last official build. Would that work? Any hints?
I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------
Oh, and I dont know if it fits without the UA repartition mod, but I can attest to it working since I've modified most units with the mod at this point.
ha7msterx said:
I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
Click to expand...
Click to collapse
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
jstoner said:
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
Click to expand...
Click to collapse
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
V0latyle said:
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
Click to expand...
Click to collapse
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
jstoner said:
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
Click to expand...
Click to collapse
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
V0latyle said:
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
Click to expand...
Click to collapse
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
jstoner said:
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
Click to expand...
Click to collapse
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
V0latyle said:
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
Click to expand...
Click to collapse
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
neat_moss said:
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
Click to expand...
Click to collapse
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
dcarvil said:
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
Click to expand...
Click to collapse
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
neat_moss said:
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
Click to expand...
Click to collapse
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
dcarvil said:
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
neat_moss said:
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
Click to expand...
Click to collapse
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
dcarvil said:
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
Click to expand...
Click to collapse
Thank you much! I'll likely be trying this soon enough
V0latyle said:
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
Click to expand...
Click to collapse
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
In addition to the OCT21 rels:
SP1A.210812.015
SP1A.210812.016.A1
I can now see JAN22 / FEB22 rels:
SP1A.210812.016.A2
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
After reading some positive feedback on v12, I think I will be updating to that latest version
But I want an 'unbranded' ROM. So it would make sense to go for "SP1A.210812.016.C1", right?
I really hope that if this is one of the last v12 releases for P3, it is at least as stable as my latest v11 build. It would be nice to have those extra privacy features, but stability on that phone is no1 prio...
jstoner said:
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
Click to expand...
Click to collapse
As I stated previously, Google only committed to 3 years of software updates on most of the Pixel line. The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
The 3a and 3aXL will be sunsetted in May of this year.
My Pixel 5 will receive its last update on Oct '23, and my wife's 5a will be supported up to Aug '24.
Software updates on Pixel devices
That being said, Pixel devices use AOSP, so it wouldn't be hard for someone to build updated firmware for the Pixels using the latest AOSP release. Google even makes the driver binaries available. The only caveat to this is that TWRP often doesn't keep up with the newer devices, so the update would have to be in the same format as either an OTA file, or factory image.
V0latyle said:
The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
Click to expand...
Click to collapse
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
jstoner said:
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Click to expand...
Click to collapse
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
jstoner said:
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Click to expand...
Click to collapse
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
jstoner said:
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
Click to expand...
Click to collapse
Probably.
V0latyle said:
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
Probably.
Click to expand...
Click to collapse
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Are those not supposed to be releases to public? (only for Devs?)
jstoner said:
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Click to expand...
Click to collapse
Pixel Update Bulletins | Android Open Source Project
source.android.com
These are general topics across the board and not device specific so I have no idea what is different in the P3 updates. This article provides more information, looks like it's mainly a security update and bug fixes.
jstoner said:
Are those not supposed to be releases to public? (only for Devs?)
Click to expand...
Click to collapse
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
V0latyle said:
Pixel Update Bulletins | Android Open Source Project
source.android.com
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
Click to expand...
Click to collapse
According to that source, that FEB22 update, is almost certainly the last for P3 + P3 XL
And as it turns out, my initial assumption about a major bug fix was actually true - it was the 911 calling issue (which due to life critical scenarios) was handled with priority
So it would seem that SP1A.210812.016.C1 is the one to go for P3. No need to wait further, as there won't be any more rels. From what I also read on Reddit, v12, despite only being introduced for P3, is decent enough. No major bugs so far. So I guess it is stable
For this device that I need it for, stabi is more important than security. Don't know if that changes anything or whether I should not move to v12..
I have been using OOS 10.3.8 on my OP 7Pro (GM1917) ever since that OS version came out.
I'm reluctant to upgrade to any OOS 11 versions due to the complexities and headaches with Magisk and TWRP which exist with A11+ OS's. However, I'm starting to think that I might be willing to upgrade to OOS 11 and bite the bullet with Magisk and TWRP, **if** there are any clear advantages in using OOS 11 over OOS 10.
Could anyone who has upgraded from OOS 10 to OOS 11 on this same device share their thoughts about what might be better in OOS 11 than what is available in OOS 10?
Although I'm generally happy with OOS 10, one complaint that I do have is that its battery-saving procedures are very good at preventing me from receiving timely push-notifications from certain apps (for example, Gmail and LINE Messenger, and I think a number of others). Is this the same in OOS 11, or has this gotten better in OOS 11? ... or could it be that they even "improved" (ha-ha) their battery-saving procedures in OOS 11 to the point where these push-notifications now arrive in an even **less** timely manner?
For me, battery-saving is not very important, while functionality is indeed the most important thing. So am I likely to be better off in this regard with OOS 11?
Thank you very much in advance for any thoughts that any of you are willing to share.
From what I've read by experts on the telegram channel, the only difference is that the quick view buttons are different on a11, and that's it. That there isn't much difference on the gui. Underneath? I don't know.
Scoped storage and forced encryption are fully active in 11.
Not sure how well OP's UI runs on 10, but with 11 it will be harder for them not to make significant changes that don't impact functionality.
Rule#1 if your OS is fast, stable and fulfilling its mission... let it be. If this is the case you have very little to gain and worlds to lose.
blackhawk said:
Scoped storage and forced encryption are fully active in 11.
Not sure how well OP's UI runs on 10, but with 11 it will be harder for them not to make significant changes that don't impact functionality.
Rule#1 if your OS is fast, stable and fulfilling its mission... let it be. If this is the case you have very little to gain and worlds to lose.
Click to expand...
Click to collapse
Thank you. I wholeheartedly agree with your Rule #1, which I've been living by.
I'm just wondering if OOS 11 might do a better job of delivering timely push-notifications than OOS 10, which does it annoyingly badly. That would be the *only* factor which might motivate me to go to OOS 11.
HippoMan said:
Thank you. I wholeheartedly agree with your Rule #1, which I've been living by.
I'm just wondering if OOS 11 might do a better job of delivering timely push-notifications than OOS 10, which does it annoyingly badly. That would be the *only* factor which might motivate me to go to OOS 11.
Click to expand...
Click to collapse
The notification issue may just be on OP's flavor of 10 rather than the 10 base code it's self being buggy. Or purely a settings issue, power management is a prime suspect. Or something in the notifications settings.
I can run my old copy of WPS office on 10, but 11 would puke on it. I have no issues with accessing files on the SD card on 10 either or with constant annoying permission pop ups. Samsung however heavily modified 10 to make it as functional as 9. Both my Notes, one on 9, the other on 10 operate almost identically. However the 10 variant has dozens of new small Samsung system apps to achieve this. They seem to consume very little resources though.
I was amazed when I first saw how many there were... too many to easily count.
The Samsung 11 variant though I doubt would be as happy a story.
At least research it heavily on forums and feedback from users rather than mainstream "yes man" reviews. Fake news is very much alive in tech news/reviews... for a few dollars more.
Ever notice how all new Fold models have glowing reviews when first released then a half year or so later the truth comes out
blackhawk said:
The notification issue may just be on OP's flavor of 10 rather than the 10 base code it's self being buggy. Or purely a settings issue, power management is a prime suspect. Or something in the notifications settings.
I can run my old copy of WPS office on 10, but 11 would puke on it. I have no issues with accessing files on the SD card on 10 either or with constant annoying permission pop ups. Samsung however heavily modified 10 to make it as functional as 9. Both my Notes, one on 9, the other on 10 operate almost identically. However the 10 variant has dozens of new small Samsung system apps to achieve this. They seem to consume very little resources though.
I was amazed when I first saw how many there were... too many to easily count.
The Samsung 11 variant though I doubt would be as happy a story.
At least research it heavily on forums and feedback from users rather than mainstream "yes man" reviews. Fake news is very much alive in tech news/reviews... for a few dollars more.
Ever notice how all new Fold models have glowing reviews when first released then a half year or so later the truth comes out
Click to expand...
Click to collapse
I've done lots of work investigating the push-notification issue that I have described, and it's not related to settings nor power-management configuration. It's definitely a known problem with OOS, including OOS 10.
OnePlus hypes their low battery usage, and this push-notification problem is one of the side-effects ... which they do not hype, of course. I don't trust OnePlus to have improved this with OOS 11, and if anything, they could even have made it worse in OOS 11. This is why I am researching here in this forum as to whether anyone has experienced any issues with notifications in Gmail, LINE Messenger, or any other apps under OOS 11 on the OP 7Pro.
PS: LINE Messenger and Gmail do *not* have this push-notification problem under A10 and A11 crDroid ROMs on the OP 7Pro. So, this is definitely a OnePlus OOS issue, and it can't be blamed on those apps.