Develop Bugs

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy Tab S4 - T830/T835

Unofficial release -TWRP recovery for the Galaxy Tab S4 2018 - SM-T830/T835 MSM8998
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 21/9/2018
Beta build released.
Current status - Beta (tested working)
Treble supported
Pretty much everything is working except for ADB and MTP at the moment.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP) ]
2. Run ODIN and uncheck Auto reboot.
3. Load the file below into the AP slot and hit start.
twrp_3.2.3-1_t830_26918
4. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
*****OREO ROOT INSTRUCTIONS:*****
Note: A MicroSD card is required to install the files below to your device.
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
TabS4_oreo_forced_encryption_disabler
2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Enjoy your rooted device.
DEVICE TREE: https://github.com/ashyx/TWRP_Samsung_GTS4LWIFI
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @ianmacd. Huge thanks to Ian for his full support and testing, helping patch the kernel and providing everything needed to get this done.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
I don't expect this to even boot as I have been forced to use the stock kernel and even if it does there is likely to be problems mounting partitions or accessing certain parts of the file system.
This is due to Samsung's current kernel source being totally borked causing many compiler errors I have not yet managed to fix.
Click to expand...
Click to collapse
Let me be the first to say thank you for this, @ashyx.
I don't have time to flash it until later in the day, but you mention having to use the stock kernel, so I wanted to point you at my repo of Samsung's kernel source for firmware revision ARGH. Samsung hasn't released the source of a more recent version yet.
I built this before I even had the device (before it had even been released in Europe, in fact), so it's also untested, but I did fix all of the compile errors before committing it. You can either clone this repo, or just cherry-pick the commit that fixes all of the compile errors (e1af7e420d4d1eb0a3302d65bb1b6e8e54f7f36b). The defconfig is as released by Samsung, so probably needs a number of config options turned off before it will produce a kernel that will even boot as an unofficial build.
Thanks once again for all of your hard work (often on devices you don't even own).

ianmacd said:
Let me be the first to say thank you for this, @ashyx.
I don't have time to flash it until later in the day, but you mention having to use the stock kernel, so I wanted to point you at my repo of Samsung's kernel source for firmware revision ARGH. Samsung hasn't released the source of a more recent version yet.
I built this before I even had the device (before it had even been released in Europe, in fact), so it's also untested, but I did fix all of the compile errors before committing it. You can either clone this repo, or just cherry-pick the commit that fixes all of the compile errors (e1af7e420d4d1eb0a3302d65bb1b6e8e54f7f36b). The defconfig is as released by Samsung, so probably needs a number of config options turned off before it will produce a kernel that will even boot as an unofficial build.
Thanks once again for all of your hard work (often on devices you don't even own).
Click to expand...
Click to collapse
Ah good stuff.
Yep most of them were include and tracepoint errors. Had pretty much fixed most of them by the looks of it, but got fed up after a while and got stuck at multiple tracepoint defines errors.
Honestly sometimes Samsung just release any old rubbish source code just to comply with the GPL.
No way is this the actual source code used in the stock kernel.
Many thanks for the link to the kernel source. I'll ensure you get some credit for the commits.

ashyx said:
Honestly sometimes Samsung just release any old rubbish source code just to comply with the GPL.
No way is this the actual source code used in the stock kernel.
Click to expand...
Click to collapse
Yes, I wouldn't be a bit surprised if we're never able to produce a bootable custom kernel for this device, as with the Tab S3. Once we have TWRP up and running, however, I shall certainly give it my best shot.

ianmacd said:
Yes, I wouldn't be a bit surprised if we're never able to produce a bootable custom kernel for this device, as with the Tab S3. Once we have TWRP up and running, however, I shall certainly give it my best shot.
Click to expand...
Click to collapse
It's ridiculous. Many times I have had to debug Samsung kernel sources. As you have discovered some just do not boot the OS no matter what.
I had an issue with the Tab A a while back where no matter what I couldn't get the kernel to boot.
I put a complaint into Samsung's open source dept. and threatened to report it to the GPL for releasing unbootable source code.
Lo and behold the next source code release booted perfectly.

ashyx said:
Current status - UNTESTED
This is really only intended for users who have fair knowledge of flashing custom stuff. I do not recommend for novices until the build is proved stable and proper instructions are available.
I don't expect this to even boot as I have been forced to use the stock kernel and even if it does there is likely to be problems mounting partitions or accessing certain parts of the file system.
Click to expand...
Click to collapse
I've flashed this now, @ashyx, and there's both good and bad news.
The good news is that it boots!
The bad news is that, although I didn't swipe to allow modifications, it's no longer possible to boot back to system. dm-verity appears to have been triggered. Interestingly, it takes as long as a full boot before the system finally reports Verification failed, so possibly this can still be bypassed by making the right edits from TWRP.
That's all I've done with it at this point. Let me know which steps you would like me to carry out. I'll leave it as is now until I hear from you.
Photos attached. Note the newly appeared open padlock and Custom in the second photo.

ianmacd said:
I've flashed this now, @ashyx, and there's both good and bad news.
The good news is that it boots!
The bad news is that, although I didn't swipe to allow modifications, it's no longer possible to boot back to system. dm-verity appears to have been triggered. Interestingly, it takes as long as a full boot before the system finally reports Verification failed, so possibly this can still be bypassed by making the right edits from TWRP.
That's all I've done with it at this point. Let me know which steps you would like me to carry out. I'll leave it as is now until I hear from you.
Photos attached. Note the newly appeared open padlock and Custom in the second photo.
Click to expand...
Click to collapse
Great.
Now I know it boots I'll fix the DM-VERITY issue.
I take it DATA is unmountable until FORMATTED?

ashyx said:
Great.
Now I know it boots I'll fix the DM-VERITY issue.
I take it DATA is unmountable until FORMATTED?
Click to expand...
Click to collapse
I hadn't done any more with it, but I've just tried and data is indeed unmountable.
Less expected is that all other file-systems (system, efs, cache, etc.) are also unmountable. Or is that the result of dm-verity having been tripped?

ianmacd said:
I hadn't done any more with it, but I've just tried and data is indeed unmountable.
Less expected is that all other file-systems (system, efs, cache, etc.) are also unmountable. Or is that the result of dm-verity having been tripped?
Click to expand...
Click to collapse
As I mentioned previously I expected the file system to have access issues due to the kernel.
Will have to patch the kernel to fix that. However no part of DATA will be accessible until formatted.

ashyx said:
As I mentioned previously I expected the file system to have access issues due to the kernel.
Click to expand...
Click to collapse
Sorry, I was rushing out the door and keen to answer you before I left. As soon as I was outside, I remembered what you had written about expecting file-system access to be impaired.
Sent from my SM-G965F using XDA Labs

So...anyone succesfully rooted this device with TWRP help ? Step-by-step procedure requested. Thanks !!

ianmacd said:
Sorry, I was rushing out the door and keen to answer you before I left. As soon as I was outside, I remembered what you had written about expecting file-system access to be impaired.
Sent from my SM-G965F using XDA Labs
Click to expand...
Click to collapse
Ok have recompiled TWRP with the patched kernel and created a patched boot to disable dm-verity and a flashable zip to disable forced encryption.
twrp_3.2.3-1_t830_test_r2
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Install the patched boot below. This can be installed with ODIN or extract the boot.img and flash with TWRP:
T830XXU1ARH8_dmverity_patched_boot
2. Boot to TWRP
3. Install the Forced encryption patch: TabS4_oreo_forced_encryption_disabler
4. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
5. Reboot and check DATA is mountable
Done.

crissx said:
So...anyone succesfully rooted this device with TWRP help ? Step-by-step procedure requested. Thanks !!
Click to expand...
Click to collapse
The thread is only 2 pages, rather than asking you could have read the posts. If you would have read the thread you would see that the recovery is still being developed and has bugs being worked out. There are ways to root your device without twrp. If you need a step by step guide, hold off, because you may need another step by step guide to unbrick your device.

ashyx said:
Ok have recompiled TWRP with the patched kernel and created a patched boot to disable dm-verity and a flashable zip to disable forced encryption.
twrp_3.2.3-1_t830_test_r2
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Install the patched boot below. This can be installed with ODIN or extract the boot.img and flash with TWRP:
T830XXU1ARH8_dmverity_patched_boot
2. Boot to TWRP
Click to expand...
Click to collapse
Thanks, @ashyx.
I'm afraid can't boot this version of TWRP. At first, I thought it was because dm-verity was tripped yesterday, so I first performed the factory reset demanded by the device, and then tried again, but no joy.
Instead of TWRP, it boots me into download mode, but rather than the familiar turquoise download screen, I get a mixed splash screen/diagnostic text display. Nevertheless, it is definitely download mode.
From there, I tried reflashing test2 of TWRP followed by the dm-verity patched boot image, but rebooting afterwards always puts me back in download mode. The only way I can seem to get out of it again is by flashing stock firmware.
I can't post a log, obviously, but I've attached a photo of the screen in question.
UPDATE:
I tried reinstalling yesterday's initial build of TWRP, just to see if I could still get into that, and it appears that I can.

ianmacd said:
Thanks, @ashyx.
I'm afraid can't boot this version of TWRP. At first, I thought it was because dm-verity was tripped yesterday, so I first performed the factory reset demanded by the device, and then tried again, but no joy.
Instead of TWRP, it boots me into download mode, but rather than the familiar turquoise download screen, I get a mixed splash screen/diagnostic text display. Nevertheless, it is definitely download mode.
From there, I tried reflashing test2 of TWRP followed by the dm-verity patched boot image, but rebooting afterwards always puts me back in download mode. The only way I can seem to get out of it again is by flashing stock firmware.
I can't post a log, obviously, but I've attached a photo of the screen in question.
UPDATE:
I tried reinstalling yesterday's initial build of TWRP, just to see if I could still get into that, and it appears that I can.
Click to expand...
Click to collapse
It could either be the custom kernel or the dtb, as I have modified both.
However regarding the dtb, I had issues splitting the dtb with aik, so had to use an alternative method.
I will compile twrp with the stock dtb and custom kernel and see how that goes.
Thanks

ashyx said:
It could either be the custom kernel or the dtb, as I have modified both.
However regarding the dtb, I had issues splitting the dtb with aik, so had to use an alternative method.
I will compile twrp with the stock dtb and custom kernel and see how that goes.
Click to expand...
Click to collapse
As you know, I had started work on a version of TWRP for this device myself, but not got very far. Like you, I had run into the issue of the embedded DTB. When I mentioned this to a developer on Telegram, he pointed me at this splitting tool. Before I could use it, however, you announced your build of TWRP, so I never tried it, but perhaps it can be of some use to you now.

ianmacd said:
As you know, I had started work on a version of TWRP for this device myself, but not got very far. Like you, I had run into the issue of the embedded DTB. When I mentioned this to a developer on Telegram, he pointed me at this splitting tool. Before I could use it, however, you announced your build of TWRP, so I never tried it, but perhaps it can be of some use to you now.
Click to expand...
Click to collapse
Yes thats one of the tools I've used to split the dtb.
It's not the splitting that's the issue I think it's the appending back to the kernel or the custom kernel itself.
Thanks anyway
EDIT: Compiled this one with just the custom kernel and stock dtb.
https://androidfilehost.com/?fid=1322778262904007632

ashyx said:
EDIT: Compiled this one with just the custom kernel and stock dtb.
https://androidfilehost.com/?fid=1322778262904007632
Click to expand...
Click to collapse
This one yields the same result, I'm afraid. I can't get into TWRP and am stuck in download mode until I flash stock firmware again.

ianmacd said:
This one yields the same result, I'm afraid. I can't get into TWRP and am stuck in download mode until I flash stock firmware again.
Click to expand...
Click to collapse
I hope it's not the kernel. I'm going to repack the stock kernel and dtb the exact same way and see if that boots.
I have a suspicion there's some special way Samsung are appending the dtb.
I'm also going to contact @osm0sis as he's a whizz at this stuff
Are you ok with the testing?

ashyx said:
I hope it's not the kernel. I'm going to repack the stock kernel and dtb the exact same way and see if that boots.
I have a suspicion there's some special way Samsung are appending the dtb.
I'm also going to contact @osm0sis as he's a whizz at this stuff
Are you ok with the testing?
Click to expand...
Click to collapse
No worries, my friend. I'll test whatever you ask me to.
The device is wiped and unusable now anyway without reinstallation, so I have everything to gain and nothing to lose.

[ROM][Lineage 16.0 Unofficial][Pixel 2 XL/Taimen][06-09-19]

Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached

A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.

Any known bugs?

pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.

I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!

Can't even get this to boot.

LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.

I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.

LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722

calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!

Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.

Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!

Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.

On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.

It's amazing! I like it! Thank you so much

Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.

I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.

Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.

[OFFICIAL] LineageOS 18.1 for the Moto G7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto G7.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
river
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sdm632

I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
In my case, at the moment it is working well, I am still testing it.
You should try to report the bug:
"Find any? Report them according to this guide"

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
Only on really really old devices like bacon , etc.

npjohnson said:
Only on really really old devices like bacon , etc.
Click to expand...
Click to collapse
Thanks for letting me know. I decided to go with a clean flash anyway just because I think my encryption on my data partition was preventing boot and restoring from a 17.1 nandroid backup broke the system completely. So far, the ROM is very good and I'm happy that I'm now on Android 11!

I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk

One thing I'm starting to hate about 18.1 is they dropped the option to Kill App by holding back button in developer settings. This may actually be a deal breaker for me, I dont think I can make it without this feature.. Shiat!

Droid4200 said:
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
Click to expand...
Click to collapse
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.

PMDPhD said:
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
Click to expand...
Click to collapse
Yes the zip makes it so much easier now. If you use the lineageos built in update process you will lose TWRP, download the zip and you can very quicky just reboot to recovery after a lineageos update, then install the twrp.zip . you will lose root so you just reinstall majisk(if you use majisk, it'll keep your modules and settings). There may be a twrp retain script, but I haven't messed with them yet, the reinstall of twrp and majisk is pretty fast (plus I'm used to doing it the old way, sort of like you with the .IMG)

Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...

Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?

TomOehser said:
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
Click to expand...
Click to collapse
New issue - seems I get into a situation where the notification light and a notification sound are coming without any notifications - even if "use notification light" is disabled... mystified at what is doing this so far, trying to figure it out. Also, Lawnchair mysteriously seems to be working...

FoxShadow said:
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?
Click to expand...
Click to collapse
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.

Working fine after a week of daily use. Upgrade from 17.1 was simple by following the instructions.
The only issue I had was with Magisk. When I installed version 22.0 after upgrading successfully to 18.1, the device would get stuck on the LineageOS boot logo. After removing all modules using adb ("adb wait-for-device shell magisk --remove-modules", then boot the device), things got back to normal. Reinstalling the modules in Magisk did not create any more issues.
Overall, a very good ROM. Thanks for the effort of creating and maintaining it.

I have an issue with "Do Not Disturb" schedules not turning off. They turn on fine but are still running the following day after the supposed end-time. I'm getting round it with Tasker, so it's not a big deal.
Thanks for maintaining the ROM and updating to version 11.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
much easier - Updater app in Settings, three dot menu, "Update recovery alongside OS"

kelue said:
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
Click to expand...
Click to collapse
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1

FoxShadow said:
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
Click to expand...
Click to collapse
For me, if it happens, it happens shortly after booting, then a quick reset by changing the color setting will fix it, and it won't happen again until the next reboot. I noticed it happen once after plugging the charger in a minute or so after boot so maybe it's hardware related, I don't know.

Question What's the best way to install latest chinese beta?

Greetings!
I'm currently using the latest Stable rom for global (12.5.1), I'm rooted and I have TWRP, everything is working fine.
Don't ask me why lol, but I want to install the latest chinese beta (miui_ALIOTH_21.6.2_6d346564dd_11.0, https://xiaomifirmwareupdater.com/miui/alioth/weekly/21.6.2/), I copy the file to internal storage, boot into twrp, flash it, clean cache and reboot.
After those steps, the phone reboots and it enters in a semi-bootloop on the poco logo. The phone restarts a few times (like 5-6) and after that, it boots succesfully.
When it boots, it boots into the stable rom (12.5.1) and not the recently flashed chinese beta (21.6.2), does anyone knows why this happen? D=
Also as extra info, my device is global, so, there's no issue if I try to install a chinese beta, right?
Have an awesome day! =D

i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot. then, after both slots are flashed, factory reset typing 'yes' then boot to system...
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck

reg66 said:
i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot.
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck
Click to expand...
Click to collapse
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=

Kimbaroth said:
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=
Click to expand...
Click to collapse
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.

reg66 said:
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.
Click to expand...
Click to collapse
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.

Kimbaroth said:
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.
Click to expand...
Click to collapse
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.

4Style said:
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.
Click to expand...
Click to collapse
I flashed the pack for the lates fw, and I got some random reboots the first 2-3 times it booted, but after that it seems to be steady.
I can confirm that the proximity sensor issue is aaaaaaalmost gone, it stills fails but way less that before. The blutooth issues I still haven't tested em yet (I need to get into my car to do that).
So, yeah, it's safe to flash the latets fw: https://xiaomifirmwareupdater.com/firmware/alioth/weekly/21.6.2/
=)

Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks

sty2009 said:
Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks
Click to expand...
Click to collapse
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)

hmm... just realised the weekly China (xiaomi EU) that i downloaded is different. didn't check your link in OP...
mine is xiaomi.eu_multi_HMK40_POCOF3_21.6.2_v12-11.zip from here
i usually check here xiaomi.eu for updates. if i were only flashing stock roms, i would only use the exact rom for my model/device ie poco f3 from here. other than that, for latest roms i would stick with xiaomi.eu roms...
anyway, i'll shut up now lol, i am a bit worse for wear and just waffling!!!

我使用的改名法，成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.

丶铭丿昱 said:
我使用的改名法，成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.
Click to expand...
Click to collapse
Does anyonw know what's the rename method?

Kimbaroth said:
Does anyonw know what's the rename method?
Click to expand...
Click to collapse
as a guess it's where you download the latest zip and rename it to 'update.zip' then put it in folder called 'downloaded_rom' and then update from settings or perhaps wait for prompt if set to auto update. can't say for sure though, haven't tried this method.
actually, just read, you can also rename the rom to update.zip and put in root of storage, then update via stock recovery... but again, i've not tried this method
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here

reg66 said:
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here
Click to expand...
Click to collapse
This is how I updated from 12.0.3 to 12.5.1, but only works from global to global (or same region to same region), if you try global to chinese, it doesn't work. =(

If CN ROM has a fastboot version u can use MiFlash tool (for safeness). Or TWRP for recovery ROM.

Kimbaroth said:
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)
Click to expand...
Click to collapse
can you please guide how to flash latest chinese beta 21.7.13 here through TWRP and which TWRP is recommended and how to flash it on both of phone slots (A and B)?

Just intall Xiaomi.eu weekly ?
Why bother with an ad- and "analytics" infested unmodified china rom ?

The "Semi-bootloop" happened, because the bootloader detected that after a few trials Slot A is simply not bootable, so it switched to Slot B.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Development [ROM] PixelExperience [UNOFFICIAL] [12.1.0] [raven]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Google Pixel 6 Pro[raven]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher mod, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to bootloader
4. Apply Magisk Boot ( Patched Magisk Boot v25.2 )
5. Start
Donate
Not needed but always welcomed
Keep in touch
Telegram channel
PixelExperience blog
Android OS version: 12.1
Kernel Source

Awesome to see PE on the 6 Pro! Any chance it becomes Raviole or if there will be a Pixel 6 Oriole build as well?

Pixel-ception right there, experiencing Pixel on a Pixel lol

Always wanted to get a pixel experience on my pixel!

device and kernel source ?
@alvin14
​

Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Currently, you cannot dual boot multiple roms. I remember with OP6T, there was a guy/gal that provided us with a recovery that allowed dual boot for two different roms. It was a wip, but functioned pretty well. Can't recall the Dev's name.
Concerning screenshots of custom settings, I'm sure it's similar to other Pixel Experience roms for other devices. I can't provide any, because I'm not using this particular custom rom at the moment.

@alvin14 Please check your PM inbox. Thank you.
-Regards: Badger50

@alvin14, to sideload you'll need to provide both the boot.img and vendor_boot.img, otherwise we can't use adb sideload since stock recovery will reject it and it's looking pretty unlikely we'll get twrp anytime soon. For those of us who are technically minded, grabbing the 2 .img files I mentioned isn't too hard, but I'm guessing there's some who likely can't.
Also, you might want to provide your kernel source as per XDA rules like the mod has likely PMed you about. This thread will likely get removed/locked and your links taken down if you don't.

Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.

alvin14 said:
Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.
Click to expand...
Click to collapse
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.

dragynbane222 said:
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.
Click to expand...
Click to collapse
Boot not needed. After flashing vendor_boot via fastboot you can select boot bootloader and it goes straight in. Magisk Boot is also provided should anyone still need the boot image.

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.

alvin14 said:
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.
Click to expand...
Click to collapse
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on. The ideal scenario for me is to be able to switch roms without wiping data, but I need to have a backup fallback or else it's going to take me hours of tweaking and setting management to be comfy(not to mention any ROM-specific settings that have crazy amounts of time-consuming customizations)

Ulyaoth said:
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on...
Click to expand...
Click to collapse
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool

Wifi calling is missing in action..

yyz71 said:
Wifi calling is missing in action..
Click to expand...
Click to collapse
I don't have that feature in my country so I never looked into that.
Thanks will look into it.

alvin14 said:
I don't have that feature in my country so I never looked into that.
Thanks will look into it.
Click to expand...
Click to collapse
Thanks great ROM

BMHater12 said:
Pixel-ception right there, experiencing Pixel on a Pixel lol
Click to expand...
Click to collapse
dex2grigg said:
Always wanted to get a pixel experience on my pixel!
Click to expand...
Click to collapse
Awesome contribution! For all you give to the community i would like to buy you both lunch!
What is it exactly that trolls eat by the way?

NippleSauce said:
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool
Click to expand...
Click to collapse
I recommend Swift Backup. I've been using it for quite awhile and it backs up everything!! Call logs, messages, apps and their data. You can backup to the device and transfer to pc for safe keeping or you can even have the option to backup and restore from the cloud. You can also do what I do and get a OTG cable and backup and restore right from that which is much faster.