Database Info

And then there was 5, the beta 5

Q Beta Folks,
Time to rejoice, its out!!
https://developer.android.com/preview/download.html
Let's see what's not working...root et al
Update:
So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing significant performance improvements compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!
5. A quick settings button is added for Dark theme. Nice! You can now toggle it quickly for some of those pesky apps which behave weird with forced dark mode.
I will keep editing this post in case I find something worth sharing.

Does anyone know if the same procedures that were used to root Q4 work for Q5?
Sent from my Pixel 3 XL

Eudeferrer said:
Does anyone know if the same procedures that were used to root Q4 work for Q5?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Works just fine. Updated and rooted in short time.

What the hell is new? ?

Do you have to flash back the stock boot.img before updating?

Sunnyschlecht said:
Do you have to flash back the stock boot.img before updating?
Click to expand...
Click to collapse
no, I was using root stock boot image and updated thru phone, grabbed new boot img rooted it rebooted phone, saw that everything was fine, then I booted into bootloader and flashed the new rooted stock boot image and booted up normally.

Anyone want to share a magisk ready boot for the lazy?

arrrgh said:
Anyone want to share a magisk ready boot for the lazy?
Click to expand...
Click to collapse
Here you go.
https://mega.nz/#!Bt1nEALa!mXmp1GNKshVFGCyZSP9EVTtTvMbaDNwpy7NeH_lCBoU

Somehow I'm having issues when flashing the patched image. I'm just using fastboot flash boot_a and boot_b with the image. It just gets to the loading screen and doesn't boot. Any recommendations?

Step x step root instructions?
Looked in the beta 4 thread, but couldn't find rooting or TWRP install instructions anywhere. Apparently it works on beta 5 as well. Could someone post them or a link to them?
Tia

Can someone confirm if the Chase Bank app is working on rooted Q5?

Anyone seeing an issue where if you are using a third party launcher and click on the recent app button you cycle between a regular preview and a huge preview of the apps?
{
"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"
}
Sent from my Pixel 3 using Tapatalk

Looks like Beta 5 has been pulled for all devices, just like the first round of Beta 4.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
Looks like Beta 5 has been pulled for all devices, just like the first round of Beta 4.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Is that only the OTA installations issues or are the beta images have been pulled as well? I still see them available for download.

devsk said:
Is that only the OTA installations issues or are the beta images have been pulled as well? I still see them available for download.
Click to expand...
Click to collapse
Just the OTA
Sent from my Pixel 3 XL using Tapatalk

I guess I got lucky. I was able to download OTA and installed it without problems.
Sent from my Pixel 3 XL

So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing performance improvement compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!

devsk said:
So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing performance improvement compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!
Click to expand...
Click to collapse
How did you root?Did you have to clean wipe from previous beta to 5 or installed ota then follow the magisk/root procedures all over again?

Jiggs82 said:
How did you root?Did you have to clean wipe from previous beta to 5 or installed ota then follow the magisk/root procedures all over again?
Click to expand...
Click to collapse
I just flashed the beta5 image without -w flag in flash-all.sh from bootloader. Booted normally. I then extracted boot.img from the image zip, fed it to Magisk and asked it to patch it. After that I flashed the patched boot.img from bootloader using fastboot, and got the root. No need to clean wipe. You keep your apps and data.

devsk said:
I just flashed the beta5 image without -w flag in flash-all.sh from bootloader. Booted normally. I then extracted boot.img from the image zip, fed it to Magisk and asked it to patch it. After that I flashed the patched boot.img from bootloader using fastboot, and got the root. No need to clean wipe. You keep your apps and data.
Click to expand...
Click to collapse
Oh ok thx, I did installed the ota regularly from beta 4 with magisk installed/ rooted , so I will try the other stuff and see if I can still boot fine wish me luck ???

Development [CLOSED][ROM][OFFICIAL] AOSPK - The Kraken Project [Android 11][vayu/bhima]

{
"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"
}
Project Proposals
Based on AOSP with improvements from many other projects! GApps included! The proposal is to provide the best experience in using a pure Android with only basic customizations. Focused on battery stability and fluidity.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
Lights
Sound/vibration
Known issues
You tell me
D O W N L O A D
Install Instructions:​
​First time installation / from MIUI:
Remove any fingerprint, PIN, or password in MIUI.​
Unlock the bootloader.​
Transfer ROM to internal storage or SD Card.​
Flash latest TWRP.​
Flash ROM zip file + (Optional) Gapps + (Optional) Magisk.​
Format Data > type "yes" and press enter. (different from the "wipe data" option)
Reboot to system.
Flashing Instructions from any custom ROM:
Backup all your data.​
Boot/reboot to latest TWRP.​
Flash recommended MIUI stock ROM (12.5.X.X). You can find them here. If you're already on it, you can skip this step.​
Flash ROM zip file + (Optional) Gapps + (Optional) Magisk.​
Format Data > type "yes" and press enter. (different from the "wipe data" option)​
Reboot to system.​
Source code: https://github.com/AOSPK
Kernel Source: https://github.com/kleidione/kernel_xiaomi_vayu
ROM Developer: kleidione

08/08/2021
Changelog
August Security Patch
Requires MIUI 12.5 firmware (any region)
These builds include custom vendor
Update blobs from V12.5.3.0.RJUINXM
Address denials and cleanup unneeded policies
Fix crackling sound on some loud ringtones
Address slow charging text issue, now it should show rapid charging with stock charger
Further debloat power and camera drivers in kernel
Fix screen selection issue on touching fp sensor
Misc changes and improvements
Thanks @kubersharma for tree and kernel

Reserved

Anyone tried it?

0b4 said:
Anyone tried it?
Click to expand...
Click to collapse
Yep.

DarthJabba9 said:
Yep.
Click to expand...
Click to collapse
Well, can you share your thoughts and experiences pls?

0b4 said:
Well, can you share your thoughts and experiences pls?
Click to expand...
Click to collapse
I only used it for a about an hour (while flashing a zillion ROMs to see what they look and feel like). It was as good as any other (ie, no obvious issue or problem, during the short period that I had it).
However, I must have been very impressed by it, because I made a backup of it (I didn't make a backup of any other, save the stock MIUI).

Dude, the custom ROM is freaking awesome, the best battery life i have seen so far, buttery smooth, and it is the smoothest ROM I have tried for games, I have tried Conquer OS, Arrow OS, Paranoid OS, Evolution X, Havoc, Android 12 beta 4 and 3, Corvus and PixelPlusUI, but AOSPK is the best of all.
Thanks for this great ROM mate.

Forgive my ignorance. Is it necessary or a good idea to unlock (Mi unlock) the device first? I just got my device this morning. First device not running Android One in my case. Appreciate your help.

madfade35 said:
Forgive my ignorance. Is it necessary or a good idea to unlock (Mi unlock) the device first? I just got my device this morning. First device not running Android One in my case. Appreciate your help.
Click to expand...
Click to collapse
Necessary for non-official adjustments.
Read my guide for informations:
https://forum.xda-developers.com/t/4288121/

pl1992aw said:
Necessary for non-official adjustments.
Read my guide for informations:
https://forum.xda-developers.com/t/4288121/
Click to expand...
Click to collapse
Thanks the help. Are wait times always a week? Seems completely arbitrary to me. Guess I'll have to debloat for now and use the phone.

madfade35 said:
Thanks the help. Are wait times always a week? Seems completely arbitrary to me. Guess I'll have to debloat for now and use the phone.
Click to expand...
Click to collapse
Always, once you unlocked bootloader follow the guide https://forum.xda-developers.com/t/...-custom-roms-root-xiaomi-poco-x3-pro.4288121/

k3lcior said:
Always, once you unlocked bootloader follow the guide https://forum.xda-developers.com/t/...-custom-roms-root-xiaomi-poco-x3-pro.4288121/
Click to expand...
Click to collapse
Thanks! Going to start the debloat process now and then wait for the timer to run down.

thanks for this great rom, working flawlessly so far!
i have a question about something that happened during flash. The same red colored messaged showed up on the screen saying something similar to "unable to mount cache" or something like that. Should i reflash the rom or is there no problem?
edit: fixed by wiping cache through twrp
another question tho. is there a way to auto accept pin code when unlocking screen? there's nothing in screen lock options. miui had this and i'm finding this to be very annoying

emaz1ng said:
another question tho. is there a way to auto accept pin code when unlocking screen? there's nothing in screen lock options. miui had this and i'm finding this to be very annoying
Click to expand...
Click to collapse
That's actually a convenience feature of Miui, but since i'm using fingerprint so there's no need for auto log in anyway.
Btw does anyone knows a way to access Android/data? My favourite app to manage files is X-plore and new AOSP roms seems to restricted this app from accessing Android/data. Miui don't have this problem.
I already know many apps that can do that like Root Explorer but i kinda wanna stick with X-plore.
Also i'd love it if you could get rid of the restriction in the first place.

Interesting, will follow this project too since it have vanilla. Is possible to have a list of system apps installed in the vanilla version? It have the two tap to wake up issue too? SD card work or i'm forced to format it to be recognized?
I'm on vanilla ArrowOS atm, need really to install MIUI stock before flash it or i can simply flash over ArrowOS and then format data? Just wondering if is mandatory the MIUI and TWRP installation (since MIUI will overwrite TWRP with stock revovery). Thank you mate for your work.

Timuela said:
Btw does anyone knows a way to access Android/data?
Click to expand...
Click to collapse
Check permissions for X-plore. I added "files & media" manually. I'm not sure if this is enough, since I already granted access to data/ folder and X-plore can browse without this permission.

Hello,i am experiencing laggy scrolling in the play store and in chrome,and sometimes in the settings menu and in the ui in general,i ve not tweaked anything besides installing magisk,also tried 2 other roms and did not have this problem,battery life is the best on this one,but the scrolling issue is a big annoying,it feels like its not hardware accelerated,any way i can enable smooth scrolling myself or something like that?

type c otg telling me to format the device
Between it's working on the TWRP and others phone

Download link is dead "download.aospk.org/vayu"

[OFFICIAL] LineageOS 18.1 for the Moto Z Play

{
"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 Z Play
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 Z Play.
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.
addison
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
Volume may be lowered when locking and unlocking the device
Non-original touchscreens may fail to respond
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.
Official Lineage OS builds for addison ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8953

Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.

Touch2Fin said:
Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.
Click to expand...
Click to collapse
Yes, it does as it's based on the same trees
Also don't report the fact that pressing the fp will lock the screen as a bug, it's an intended feature, what's not intended is the fact that for some reason it can't be disabled right now

- Is there a minimum firmware base requirement?
- Which GSI variant is supported?

VR25 said:
- Is there a minimum firmware base requirement?
- Which GSI variant is supported?
Click to expand...
Click to collapse
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?

marcost22 said:
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?
Click to expand...
Click to collapse
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.

Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp

@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!

Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip this one will work !!​

VR25 said:
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.
Click to expand...
Click to collapse
Thanks!
Also funny finding you here
Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also you are expected that if you are able to install a rom, you are able to do a little googling and reading
bunt009 said:
@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!
Click to expand...
Click to collapse
Yes, as all my roms it is a 64bits rom

marcost22 said:
Thanks!
Also funny finding you here
Click to expand...
Click to collapse
I also find funny the fact that you opened this thread just two days before my Z Play got out of the repair store. Nice timing!

Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?

Nelsobrinho said:
Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?
Click to expand...
Click to collapse
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before

marcost22 said:
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before
Click to expand...
Click to collapse
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?

Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
Do you by any chance have the chinese (XT1653-03) variant? If not, can you grab me a logcat of the behaviour so i can check it?

Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1635-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.

joaoantonioe said:
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1653-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.
Click to expand...
Click to collapse
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time

marcost22 said:
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time
Click to expand...
Click to collapse
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC

Nelsobrinho said:
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC
Click to expand...
Click to collapse
What is your variant?

My variant is XT1653-02

Development [ROM][13][Unofficial][Bluejay] crDroid v9.0 [01.15.2023]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device.
You have been warned.
crDroid is designed to increase performance and reliability over stock Android. You will find many custom features implemented from the Android custom ROM community over the years. Enjoy!
Flashing Instructions:
You must be coming from latest Google factory image
Reboot into bootloader mode
From a terminal run "fastboot -w update rom.zip" Do not use quotes and replace rom.zip with the actual name of the zip you are going to install
There are two versions GApps and Vanilla
[/B][/B][/SIZE]
Known Issues:
You tell me
Sources:
ROM
Kernel
Download:
HERE
ROM OS Version: Android 13
ROM Kernel: Linux 5.10.x
Visit official website @ crDroid.net
NugTowersHQ Telegram

Reserved

Hey thanks for sharing. Xda isn't what it once was, but it's still nice to see roms and kernels for bluejay popping up here.

Hello everyone! Updating the build again tonight. This build will address the adaptive connectivity FC when making calls on some carriers and fixes monet. I have also started compiling user builds. I would suggest a clean flash in any situation. Thank you.

Is this ROM ready to be used on a daily? Any major bugs/issues?

how to install it?
is it enough to open bootloader or I need to open critical botloader?
and do I need to flash vendor or vbmeta?

yamabokra1 said:
how to install it?
is it enough to open bootloader or I need to open critical botloader?
and do I need to flash vendor or vbmeta?
Click to expand...
Click to collapse
Instructions are right n the OP....
Flashing Instructions:
Reboot into bootloader mode
fastboot -w update rom.zip (this command will completely wipe your device)
This build includes gapps
And yes, you need an unlocked bootloader to use fastboot

Lada333 said:
Is this ROM ready to be used on a daily? Any major bugs/issues?
Click to expand...
Click to collapse
I am using as my DD. There are a couple issues that have been reported so far but I am not able to reproduce.
* Some users experiencing front facing camera issues (no log provided yet)
* VoLTE reported not working on TELUS (no log yet)
* Wallpaper and Monet issues have been fixed in latest build
* If you are having issues with adaptive connectivity force closing when making calls, disable it in network settings

ctfrommn said:
Instructions are right n the OP....
Flashing Instructions:
Reboot into bootloader mode
fastboot -w update rom.zip (this command will completely wipe your device)
This build includes gapps
And yes, you need an unlocked bootloader to use fastboot
Click to expand...
Click to collapse
I wrote my question after training the instructions in the first post and failed.
So do I need to open only bootloader or critical bootloader?

yamabokra1 said:
I wrote my question after training the instructions in the first post and failed.
So do I need to open only bootloader or critical bootloader?
Click to expand...
Click to collapse
Can you share your error?

yamabokra1 said:
I wrote my question after training the instructions in the first post and failed.
So do I need to open only bootloader or critical bootloader?
Click to expand...
Click to collapse
Just the bootloader.
fastboot flashing unlock
My guess though is if you have a flashing error it's related to having an old version of adb/fastboot. You need like v32 at least on these devices.

Google apps are there but will not let me sign in

Here's my log

Happy to see crdroid for the 6A, but why to include gapps ?

BreckZeBoulay said:
Happy to see crdroid for the 6A, but why to include gapps ?
Click to expand...
Click to collapse
Difficult (impossible?) to flash GApps with no custom recovery, no?

Lada333 said:
Difficult (impossible?) to flash GApps with no custom recovery, no?
Click to expand...
Click to collapse
True !
But no need gapps to have a functional android device

stebomurkn420 said:
I am using as my DD. There are a couple issues that have been reported so far but I am not able to reproduce.
* Some users experiencing front facing camera issues (no log provided yet)
* VoLTE reported not working on TELUS (no log yet)
* Wallpaper and Monet issues have been fixed in latest build
* If you are having issues with adaptive connectivity force closing when making calls, disable it in network settings
Click to expand...
Click to collapse
I recall I had the same issue with volte not working on Telus (using p6p). I had to flash a magisk module to resolve that. I can try and see if I saved it, if someone needs it. (I'm no longer using Telus though)

Theripper91 said:
Google apps are there but will not let me sign in
Click to expand...
Click to collapse
Clean install the latest version of the ROM that includes gapps. I updated the build last night

I know the only way to find out the actual answer to my question is to try it myself, but here goes anyway:
I have not had any issues with my 6a while on A12. After upgrading to A13, and a few weeks passing by, I've been noticing connectivity issues. Random apps randomly telling me that I have no internet connection, mainly. Can this be a hardware issue? (Since it wasn't present when I started using the phone, I wouldn't think so?)
Would flashing this ROM possibly fix that issue? Or would I only need to do a factory reset, maybe flash a custom kernel?

stebomurkn420 said:
Clean install the latest version of the ROM that includes gapps. I updated the build last night
Click to expand...
Click to collapse
Thanks for the reply. I got it working after I reflashed it. Both times were clean installs tho. It was most likely a module for magisk that was causing it because both Facebook and messenger messed up on the second install. They acted exactly like Google play services did from the first install.

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.