Database Info

[OOS][Oreo] Enable Google Daydream VR Support

For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"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"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏

Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?

lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.

Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.

CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!

CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••

Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.

CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.

I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..

Anybody got it working? I saw the set today at a store and thought about buying it...

This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.

OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?

aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk

t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.

aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?

EDIT: see post #19

I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.

Updated for Oxygen OS 5.1.3

Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.

M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.

[ROM] [Unofficial] [11] RevengeOS 4.0 Stable

{
"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"
}
RevengeOS is an operating system based on Android Open Source Project, built with a unique look and performance in mind. It's daily usage ready, lightweight and elegant.​
FEATURES
RevengeOS exclusive features:
- Battery health checker
- Brand new RevengeUI, built to be different, built to be elegant (Best when i can get Official)
- Brand new media controller
- Systemwide gradients
- New lock screen clock styles
General features:
- In call haptic-feedback
- Kill app button
- Toggle battery percentage in status bar
- Resume media from Quick Settings
- Playback control from volume buttons
- Wake up with volume buttons
- Quick camera launch from sleep
- 3-button navigation system
- Pill navigation system
- Swipe to screenshot
- Wake on charge
- Proximity sensor check when waking up
- Systemwide sensor block
- And so much more!
DOWNLOADS
SourceForge
INSTALLATION
1. Flash ofox_universal.img through qfil on boot_a & boot_b OR fastboot boot <drag and drop ofox_universal.img over the cmd>
2. Format Data ( Go to Trash Icon in ofox -—> format data —-> type yes )
3 .Flash the rom using adb sideload ( go to 3 lines in the bottom right corner and select adb sideload then swipe, now you go in adb tools open the cmd and type adb sideload < drag and drop the zip over the cmd> )
4. Flash ofox zip the same way through adb sideload, it will automatically reboot to ofox after flashing done
- Optional: flash NikGApps (Basic recommended)
- Reboot
- Optional: flash Magisk (if you want to root your device as well) (it's recommended to flash Magisk post first boot)
Telegram Support
Important
Hi guys, we're posting this message today to talk about RevengeOS. We want to talk about the developers of our project.
There are just three developers that hard-worked every day for you, to deliver optimization, exclusive RevengeUI, media controller, etc. We want to make this project more and more exclusive, and we want to improve everything. And lastly, we want their users to be happy while using it. But there is a problem, three developers can't do much. So, we're here to ask if you - if you're a developer, and if you want to join us, you may do so. We have the following requirements:
Knowledge of Android and Java
Desire to be innovative
Be mad
Think you're good enough? Contact us via email!
Email: [email protected]

Thanks for the rom but can make calls but can't hear nothing on the receiver or phone speaker. Does it require certain firmware for this rom? I'm using ULM converted to N 30g.

sinkoo1979 said:
Thanks for the rom but can make calls but can't hear nothing on the receiver or phone speaker. Does it require certain firmware for this rom? I'm using ULM converted to N 30g.
Click to expand...
Click to collapse
Based on DotOS trees, I would say the recommended firmware is 30f, anyway i'll see if is a recurrent problem and try to fix, thanks man

sinkoo1979 said:
Thanks for the rom but can make calls but can't hear nothing on the receiver or phone speaker. Does it require certain firmware for this rom? I'm using ULM converted to N 30g.
Click to expand...
Click to collapse
Bro HOW TO CONVERRT ULM TO N?

AbboSSoft said:
Bro HOW TO CONVERRT ULM TO N?
Click to expand...
Click to collapse
follow this guide https://forum.xda-developers.com/t/...g7-g7-dual-sim-thinq-except-t-mobile.3915303/

this ROM is very good on games, but the phone signal is suddenly lost, and comes back after hours.
i use the canadian 30d rom.

Google Pay works without Magisk?

Astur13 said:
Google Pay works without Magisk?
Click to expand...
Click to collapse
it wont

Shykan003 said:
this ROM is very good on games, but the phone signal is suddenly lost, and comes back after hours.
i use the canadian 30d rom.
Click to expand...
Click to collapse
did you use airplane mode ? if yes then its a visual bug what's happening with signal, in fact you do have signal. if its not that then maybe try another firmware, check dotos thread for the recommended firmwares.

EmanuelCN said:
it wont
Click to expand...
Click to collapse
Thanks! I supposed it. I used to use Magisk long time ago but at present, does it fails often when SafetyNet update? When happens, does it take too much time until Magisk fix it? It is crucial for me knowing about this, thanks you a lot. Excuse me the off topic

Astur13 said:
Thanks! I supposed it. I used to use Magisk long time ago but at present, does it fails often when SafetyNet update? When happens, does it take too much time until Magisk fix it? It is crucial for me knowing about this, thanks you a lot. Excuse me the off topic
Click to expand...
Click to collapse
Enable magisk hide in magisk settings and its fixed. Also do not use magisk to check for safetynet use Safetynet Evaluation on playstore. Magisk's checker is broken it will show not passing no matter what, which is because the checker itself its broken not safetynet.

Hi. I built CherishOS using the same dotOS device tree, but I had mobile data not working issue. Do you have any idea?

Sorry that i have few knowlege...
The question is: How can I extract boot.img?
For now I am struggling installing magisk. I was warned by xda gudiance that the method of magisk in recovery is abandoned, and the method of re-package boot.img is recommended. Is it same with official stock? or should I use recovery.img instead?
Sorry I am not good as English as well, and sincerely thanks for your efforts!

I need a new rom. Can anyone give advice?

USB Tethering working ?

i think this is the best rom for our lg. thank you for you work

Sony Z3 Plus D6653

Hi I've unlocked the bootloader, what's the next step to root & flash twrp?

Hey there, what rom are you hoping to run? I'm on the D6603 and there hasn't been a new twrp for over a year (muppets release).
I'm running Lineage 18.1-20211230 rom & recovery for about an hour now.
Magisk would not install via flash for me, despite claiming success.
Digging around the issues threads I found the 'canary' or debug file works fine.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Specific issue (worth a read, you might face this again and you could always edit the boot_patch.sh yourself)
Magisk 21.2 cannot be installed on Sony Z1c with Android 10 Lineage 17.1 · Issue #3636 · topjohnwu/Magisk
Description The last Magisk version that could be correct installed was 20.4. All versions after 20.4 fail (from the first canaries to 21.2 magisk-debug_6d88d8ad). 1.1 Flashing magisk-debug_6d88d8a...
github.com
Good luck

Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
[MagiskInit] Support init.real on some Sony devices
Click to expand...
Click to collapse

z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others)
Click to expand...
Click to collapse

ns404art said:
do you have a contact i can call?
Click to expand...
Click to collapse
Not sure what you mean by this. Posting a quick answer. I'll edit it with more:
Magisk can be downloaded from; https://github.com/topjohnwu/Magisk
It is the ONLY place you should get it from!
Edit:
If you were hoping for a one-to-one, I'd rather type it out, just in case anyone else should come looking.
To be honest, you haven't provided enough information about your phone model or your desired goals for me to give you a straightforward answer.
I have experience with the D6603 only. I've been using lineage for about a year with different recoveries and, in my opinion, for the path of least resistance you should probably use a recovery and rom from the same project. (When I had twrp as recovery, OTA updates would fail, but not say so. It was only when commenting on a reddit thread, I thought I'd add my version number and discovered I'd gone months on the same rom. Manually flashing the latest rom broke stuff in all sorts of ways. So...)
Probably best to treat it as a rolling release and stay up to date or else lock-in to one you're happy with.
If using lineage, check update news first, if 'planned for next release' includes rollback of features just added - probably skip that update.
Gaining root was the last step for me. I have no experience of rooting SONY rom.
(My desired goal was to cut out google and play store).
Rooting was just;
1) Download Magisk
2) Rename .apk to .zip (DO NOT zip IT UP)
3) adb sideload, ignore checksum failure and choose install anyway.
The recent Magisk update has made it easier though. I was able to patch the boot file from within the app, so you possibly don't need to sideload anymore.
Right, that's a wall already. If you need more please include details such as;
Phone model :Sony Z3 Plus D6653 (2nd edit - oops just saw this)
Desired goal
Desired rom
/Edit

z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
Click to expand...
Click to collapse

I've unlocked the bootloader, what steps should I take to root and I'm planning to install a carbon rom
{
"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"
}

I would follow the lineage install guide and change filenames where appropriate.
https://wiki.lineageos.org/devices/z3/install
If you intend to push on with twrp as recovery. see;
TWRP 3.3.1-Z3 Build 2020-02-12
This is the latest TWRP 3.3.1 build by The Muppets. This TWRP supports Android 8-10 for now. ROM recommended: LineageOS 16.0, LineageOS 17.1 and CarbonRom 8.0 Download: TWRP 3.3.1-Z3 or Mirror How to install: First of all you MUST flash...
forum.xda-developers.com
Which recommends, amongst others; Carbon 8. So old version
You could try latest lineage recovery & Carbon 9.
Your best bet is to ask within the Carbon thread;
https://forum.xda-developers.com/t/11-official-carbonrom-cr-9-0-enchilada.4313373
good luck

How To Guide Update from Rooted Android 12 to Rooted Android 13 and Keep Data

Introduction
This is a guide for updating from Android 12 (rooted) to Android 13, maintaining root and keeping data. I followed this method with success after having a difficult time finding clear instructions. Hopefully it helps someone.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
Notes
Method uses Pixel Flasher
Updates both slots to Android 13 as suggested by V0latyle
One caveat with flashing patched boot.img directly (this method) is that you won't be able to revert back to take OTA updates.
To work around this, you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app.
These two methods would replace the method that this post covers.
Process
Make sure you have the most up to date version of Pixel Flasher, Platform Tools, and Google USB Driver
Download factory image of Android 13
Flash using Pixel Flasher following these steps and screenshot (see corresponding numbers in screenshot)
Browse to your platform tools folder
Reload adb connected devices
Select your device from dropdown
Browse to Android 13 factory image zip file
Click to process factory image (gets boot file from image)
Select factory boot image
Patch factory boot image
Select patched boot image
Select keep data
Select flash to both spots
Push 'flash pixel phone' button
{
"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"
}
Wait for process to complete. it will take some time since it has to flash both slots. your phone will reboot to Android 13 as normal once it’s complete
Enjoy A13
Troubleshooting
Only issue I ran into was Pixel Flasher couldn't detect my device when in bootloader-fastboot mode. ADB commands were registering fine.
To fix this,
Plugged in my phone
Booted to the bootloader screen
Opened device manager in windows 10
Updated the driver for the android device/pixel 6a/unknown device using the latest google usb driver
Future OTA Updates
To take future OTAs without an original boot.img, you can either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root with Magisk.
Thanks
topjohnwu for Magisk
badabing2003 for Pixel Flasher
psychedel!k for help with OTA update info

Thank you for the tutorial!
I have a doubt... Currently I'm already on A13 with root but I'm not very clear about the steps to follow when the next update comes out and I want to flash it already with root through pixel flasher...
- Should I follow these same steps except check that I update both slots?
- Should I check both "disable" boxes? (What are these two options for?)
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!

dannyzamora said:
- Should I follow these same steps except check that I update both slots?
Click to expand...
Click to collapse
I don't believe you need to update both slots if you've already done that when moving to Android 13. If you didn't, it would probably be good to update both slots like i show in my screenshot
dannyzamora said:
- Should I check both "disable" boxes? (What are these two options for?)
Click to expand...
Click to collapse
i would recommend reading about these two. i'm not an expert and can't provide much info without doing research myself. I chose to go with the defaults and recommendations i saw while researching the process.
dannyzamora said:
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!
Click to expand...
Click to collapse
after you click the patch button, Pixel Flasher will do the installation. you don't need to install the factory image with magisk afterward. all magisk modules should persist through the update.
happy to help the best i can.

Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app

psychedel!k said:
Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app
Click to expand...
Click to collapse
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?

R.Suave said:
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?
Click to expand...
Click to collapse
correct and to take OTAs without an original boot.img you could either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root

just wanted to say thank you for this guide and detailed instructions. amazing!!

Questions
1. When I try to run APT 34 it says it won't work, so I have to use 33?
2. I have the roms in a folder but it will not find any images.
3. Do I need to reboot to bootloader and use magisk? It's greyed out.

Development [Discontinued][ROM][13.0][Unofficial][Bluejay][Lineage OS 20.0][Feb-13-2023]

Official support is now here! You can flash right over your old installation if you are coming from this ROM (no factory reset needed).
https://download.lineageos.org/bluejay
Lineage OS 20.0 - Unofficial - Pixel 6a
{
"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"
}
​Hi all. I noticed that there isn't official Lineage OS support for our Pixel 6a, so I decided to build it until then (if it happens). Since it appears to be working correctly, I wanted to share it with anyone else who has an interest. I'm not changing anything about it (other than making the updater allow unofficial updates) and building straight from the Lineage OS sources. I'll attempt to build it roughly 1x per month, usually around the middle to allow for most security updates to take effect. I daily drive the ROM, so I'll try to only post updates as long as basic functionality is working.
Latest ROM and Recovery:
ROM
Recovery
(Don't worry about the page saying Pixel 6. It wouldn't let me select 6a as an option)
Optional Latest Bootloader and Radio:
Bootloader
Radio
(Update with the fastboot flash bootloader / fastboot flash radio command respectively)
Old Releases:
Old
Optional Google Apps:
MindTheGapps
(Use Lineage 20 (Android 13) MindTheGapps link -> MindTheGapps-13.0.0-arm64-20XXXXXX_XXXXXX.zip)
Follow the "official" directions in order to flash the ROM and recovery files:
https://lineage.youd.dev/340458/41/devices/bluejay/install
OTA Support:
I modified the built in updater to support updates from my unofficial source for all flashed builds. I added an option under preferences to go back to the official source in the event that official builds are started. Just go to Settings -> System -> Updater to check. I plan on uploading to OneDrive and Dropbox for these updates (bandwidth might be temporarily limited). You can always manually flash without it from a PC.
Sources:
https://github.com/LineageOS
https://gitlab.com/the-muppets/proprietary_vendor_google_bluejay
https://github.com/calsurferpunk/android_packages_apps_Updater
https://github.com/calsurferpunk/lineageos_update
(roomservice.xml attached to this post for reference)

Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?

Thx!
Face unlock built in?

CrazyLyte said:
Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?
Click to expand...
Click to collapse
I'm just supporting the 6a/bluejay since that's what I have. If there were a lot of requests, I could attempt it, but I would have no way to test it (and the updater wouldn't be able to use the unofficial sources since I have limited space/bandwidth to share the updates from Dropbox/OneDrive).
lucky58 said:
Thx!
Face unlock built in?
Click to expand...
Click to collapse
I don't think face unlock is supported on any of the 6 series and I've seen no reference in the Lineage OS source/ROM.

Just picked up a 6a, but I'm going to run it stock for a bit just to see what that's like (I don't think I've run stock Android for at least a decade). Can confirm, the stock ROM does not have face unlock. It does have "Screen Attention" which is supposed to delay locking the screen if you're looking at it.
Looking forward to trying out your work Cal

Nice work. Thanks a bunch ..

Bruh, i accidentally flashed the android TV gapps package

New ROM update is available. You can either download it manually or use the built in updater if coming from the earlier version. You might want to update your bootloader/radio as well (optional and links are on the original post). The bootloader/radio img files are extracted from the latest official Google updates.

Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.

2mnml said:
Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.
Click to expand...
Click to collapse
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?

calsurferpunk said:
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?
Click to expand...
Click to collapse
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?

2mnml said:
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?
Click to expand...
Click to collapse
I updated my radio and bootloader first, but doing so is optional. I don't know how much it actually affects.

Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org

phuzz11 said:
Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
I just saw the XDA article as well. Thanks for the update. I tried downloading the official through the updater but got a verification failed message. I'm not sure if it's a problem with the updater or actual official .zip.
If anyone manually downloads the official update, can you let me know if it works? I had an issue happen once before with my older OnePlus 8 Pro phone to where there was a problem with the first official download. I'm a little hesitant.

I just verified the official ROM. I was able to flash it right over the existing unofficial ROM without any trouble. Just follow the same instructions as for the unofficial:
1) Boot to recovery
2) Flash official ROM .zip
(optional)
3) Reboot to recovery again
4) Flash Google apps
5) Flash Magisk
6) Reboot system
I noticed there were some odd warnings when flashing the Google apps/Magisk (other than signature verification). Google apps seemed to error out at first (never seen that before) but I just flashed it again immediately and it finished.
Thanks to all for their support and the official Lineage OS team.