April Update is out now - Google Pixel 3 Guides, News, & Discussion

installing..,

Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.

Any idea what fixes are in this one?

davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/...019-04-01.html
https://source.android.com/security/...language=zh_cn

davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2019-04-01.html

Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!

I am dling the factory image now, but boot.img should be in there. Are you sure it was not a bad dl?
-Boot.img is in there. Extract the zip then open the "image-blueline....zip" it is in there. If it is not then something is wrong with your dl.

sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.

FilthyFord said:
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
Click to expand...
Click to collapse
Native tethering. This method works on my 3 XL as well as my wife's "little" 3 on T-Mobile.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662

atu567 said:
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue, cant find stock kernel either.
extracted the zip, fastboot flash boot boot.img, fixed.
jk didnt work oddly enough.
got to login then wouldnt let me use my screen. no touch input.
edit again: update platform tools fixed problem. https://dl.google.com/android/repository/platform-tools_r28.0.2-windows.zip

sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’

wssxzzzz said:
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
Click to expand...
Click to collapse
No problem with safetynet here.

sliding_billy said:
No problem with safetynet here.
Click to expand...
Click to collapse
Ok, thank you, I think that is my problem.

wssxzzzz said:
Ok, thank you, I think that is my problem.
Click to expand...
Click to collapse
What is the problem?

Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!

benj! said:
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
Click to expand...
Click to collapse
Def the cam app I noticed too and I'm on Jan update, it's nice tho!

I installed the April update to fix the flashing bug of the ambient display, bit it is still there. Any body else having this issue? Also, is there any fix for this?

Related

Unbelievably, the N factory image has been posted!

https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX

Root thread (US & EU) requests welcome! Oreo boot added

This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?

[resolved] No imei / nck code asked

Hi to all
My honor7 was perfectly functional until this night
But i don't know why, when i screen on it asked me a nck code
It's the first time
The phone is unlocked and rooted since 2 years already
I checked the imei, it was incorrect with 15x0
000000000000000
I checked with other sim Card same issue
Any help ?
nmen00vb said:
Hi to all
My honor7 was perfectly functional until this night
But i don't know why, when i screen on it asked me a nck code
It's the first time
The phone is unlocked and rooted since 2 years already
I checked the imei, it was incorrect with 15x0
000000000000000
I checked with other sim Card same issue
Any help ?
Click to expand...
Click to collapse
Did you try factory reset?
Finally It's resolved
Magisk is in fault, I repatched boot image again and it rework
nmen00vb said:
Finally It's resolved
Magisk is in fault, I repatched boot image again and it rework
Click to expand...
Click to collapse
Good to hear.. :good:
Seems like Magisk badly wrote to the boot image... it also asked for me for a NCK code.
ShadixAced said:
Seems like Magisk badly wrote to the boot image... it also asked for me for a NCK code.
Click to expand...
Click to collapse
You too having the same issue??
hassanjavaid8181 said:
You too having the same issue??
Click to expand...
Click to collapse
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
ShadixAced said:
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
Click to expand...
Click to collapse
Ohhk.. Thats good.
ShadixAced said:
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
Click to expand...
Click to collapse
Thank you!
I was facing the same issue after updating to the latest Magisk! so i revert back to ver 15 and ignored all latest update.
Finally - Referring to your method - solving the issue. :good:
Big Thanks!
fiezwan said:
Thank you!
I was facing the same issue after updating to the latest Magisk! so i revert back to ver 15 and ignored all latest update.
Finally - Referring to your method - solving the issue. :good:
Big Thanks!
Click to expand...
Click to collapse
Glad I could help.
Huamei Mediapad M2-803L
ShadixAced said:
Glad I could help.
Click to expand...
Click to collapse
I have the same issue. May I know whether I should:-
(1) flash stock boot.img;
(2) reflash Magisk v16; or
(3) revert back to Magisk v15
I have done (1) and (2) but still need NCK code.
Thank you!
Were you able to get it working again? Also tried all these steps on my mediapad x2 and grabbing for anything that might help. Even tried hcu and dc unlocker but to no avail. Any help appreciated.
Thanks.
to resolve the problem, you must flash twice magisk
when you flash , the log show an error about space, if you have that be sure you will have the issue
if he passed this message you are ok and you dont need to flash the boot again
twlai said:
I have the same issue. May I know whether I should:-
(1) flash stock boot.img;
(2) reflash Magisk v16; or
(3) revert back to Magisk v15
I have done (1) and (2) but still need NCK code.
Thank you!
Click to expand...
Click to collapse
Hello there and sorry for the long-time answer.
Normally you should have only flashed Magisk v16, since the error resides on the framework.
(actually, it is a "ramdisk" error, making it impossible to allocate all the space needed into the ramdisk to be rebuilded, @topjohnwu if you know anything about this )
Dude, thank you so much for writing this down. I have been facing the same problem today. Staying with Magisk 14
Hi. I'm facing the same issue. My imei is 000000000000 and its asking for the NCK code.
I extracted the stock boot image from the rom. flashed it. then installed magisk. patched boot, and flashed patched boot but the problem still persists.
when you say flash magisk twice what do you mean exactly?
thanks!
ShadixAced said:
Hello there and sorry for the long-time answer.
Normally you should have only flashed Magisk v16, since the error resides on the framework.
(actually, it is a "ramdisk" error, making it impossible to allocate all the space needed into the ramdisk to be rebuilded, @topjohnwu if you know anything about this )
Click to expand...
Click to collapse
Flash Magisk from recovery, it seems that it works when done so.
Try this :
1) Flash the stock boot image back
2) Flash Magisk FROM recovery.
Optional : wipe cache and dalvik.
Try again and see.
i dont have a recovery.
should i install twrp? thanks.
ShadixAced said:
Flash Magisk from recovery, it seems that it works when done so.
Try this :
1) Flash the stock boot image back
2) Flash Magisk FROM recovery.
Optional : wipe cache and dalvik.
Try again and see.
Click to expand...
Click to collapse
Yes you can install TWRP. (I do think it's the only one available ?)

December update is out

It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse

Disable force encryption after installing custom rom

I somehow forgotten flashing disable force encryption before installing rom. Now my phone is encrypted. How can I decrypt it again?
I think you have to flash stock rom.
i never had success with decrycpting after i booted. If youre once stuck with an non working encryption you need to factory reset via twrp
(not sure if this is the only way, but it's the only way it worked for me.)
Perzikk said:
i never had success with decrycpting after i booted. If youre once stuck with an non working encryption you need to factory reset via twrp
(not sure if this is the only way, but it's the only way it worked for me.)
Click to expand...
Click to collapse
Yep I tried a couple of times and it show corrupted zip
Odd man said:
Yep I tried a couple of times and it show corrupted zip
Click to expand...
Click to collapse
Try new clean install, than recover the data from a backup...
Perzikk said:
Try new clean install, than recover the data from a backup...
Click to expand...
Click to collapse
Yep, trying a new room later. Looking forward to Pixel experience
Odd man said:
Yep, trying a new room later. Looking forward to Pixel experience
Click to expand...
Click to collapse
Just... Do IT ?
PE is for me the best rom so far,
Use treble v18, works Just fine with the dfe, even If you Update.
Just disable all modules, remove Fingerprint etc, and updating should be no problem. (Firmware and Rom)
Magisk should reinstall itself.
Perzikk said:
Just... Do IT ?
PE is for me the best rom so far,
Use treble v18, works Just fine with the dfe, even If you Update.
Just disable all modules, remove Fingerprint etc, and updating should be no problem. (Firmware and Rom)
Magisk should reinstall itself.
Click to expand...
Click to collapse
Have you tried Lineage Os before? Lineage Os is kinda below my expectations cus it is one of the most developed and matured Os. Does Pixel experience have a proper dark mode?
Odd man said:
Have you tried Lineage Os before? Lineage Os is kinda below my expectations cus it is one of the most developed and matured Os. Does Pixel experience have a proper dark mode?
Click to expand...
Click to collapse
Yes realy Like the PE DARK Mode, With a nice launcher Just eyecandy ... Since Yesterday im trying MIUI and Missing darkmode already...
Only downside in PE so far is a workaround to use more than one audiomod with Bluetooth...
Think i gonna flash Back to PE this evening and try this "workaround"
edit: used this thread to clear my prob with BT, only had to delete sondfx folder in vendor/lib because "crackle" sound
https://forum.xda-developers.com/poco-f1/how-to/guide-how-to-make-audio-mods-amazingly-t3929593
PE is for my use the best rom so far

Categories

Resources