[ROM][10.0][UNOFFICIAL] Nexus Stock for Xiaomi Mi Pad 4 [clover] - Xiaomi Mi Pad 4 ROMs, Kernels, Recoveries, & Other

[ROM][10.0][UNOFFICIAL] Nexus Stock for Xiaomi Mi Pad 4 [clover] - Xiaomi Mi Pad 4 ROMs, Kernels, Recoveries, & Other

Reserved

In LineageOS 17.1 on mi pad 4 wifi, there is a little section for xiaomi and then a section on thermals, but when i change those, the cpu frequency does not change, nor the governor.
Is it the same on Nexus ROM ?

Can't install this. I get error 7 at flashing. I'm wrong? Is this for mi pad 4 wifi (non plus)? I wipe everything like always, i'm coming from carbon rom, i wanna try this, seems good, but....

blue whale said:
In LineageOS 17.1 on mi pad 4 wifi, there is a little section for xiaomi and then a section on thermals, but when i change those, the cpu frequency does not change, nor the governor.
Is it the same on Nexus ROM ?
Click to expand...
Click to collapse
That should be the same as for the underlying LineageOS 17.1 build, since I haven't touched that area at all.

25agosto said:
Can't install this. I get error 7 at flashing. I'm wrong? Is this for mi pad 4 wifi (non plus)? I wipe everything like always, i'm coming from carbon rom, i wanna try this, seems good, but....
Click to expand...
Click to collapse
The update script is looking for "ro.product.vendor.device=clover", which should be true on the latest LineageOS and Carbon. I am noticing now that the property is called "ro.vendor.product.device" on stock OEM, so I'll add that. I didn't pick up on the transposition last night, but I believe that "ro.vendor.product.device" is deprecated in API 28 and later.
Stand by for an update script update.

Magendanz said:
The update script is looking for "ro.product.vendor.device=clover", which should be true on the latest LineageOS, and Carbon. I am noticing now that the property is called "ro.vendor.product.device" on stock OEM, so I'll add that. I didn't pick up on the transposition last night, but I believe that "ro.vendor.product.device" is deprecated in API 28 and later.
Stand by for an update script update.
Click to expand...
Click to collapse
Nice! Can't wait to test!

25agosto said:
Nice! Can't wait to test!
Click to expand...
Click to collapse
Okay, the link above has been updated. Since the actual build hasn't changed, I made it a "rolling update"...which is a sneaky term we used at Microsoft for silent updates with no version change.
Also, make sure you're using the latest TWRP for clover because that's what I've used for testing. We're up to v3.4.0-0 now. Some older versions might not map partitions to /dev/block/by-name or correctly handle system-as-root.

This need to be tested. thanks!

Can not install
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Updater error:7
already use twrp 3.4.0-0

gaoxieen said:
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Click to expand...
Click to collapse
That's because the update script is unable to read the vendor build.prop, which it needs to confirm it's on the target hardware. Did you erase it, by any chance?

New problem
Magendanz said:
That's because the update script is unable to read the vendor build.prop, which it needs to confirm it's on the target hardware. Did you erase it, by any chance?
Click to expand...
Click to collapse
Thank you for your reply. I format the data and install again. I think this time the script read the .prop.
But it shows
Failed to unmount /system_root: No such volume
So I checked system_root and it is blank.

Very good ROM, thanks.
I cannot access the SD card, unable to proceed "Allow to access SD card", saying app not found.

gaoxieen said:
Thank you for your reply. I format the data and install again. I think this time the script read the .prop.
But it shows
Failed to unmount /system_root: No such volume
So I checked system_root and it is blank.
Click to expand...
Click to collapse
Try downloading now. I made a tweak to the update script that should address this issue.

Chrome and webview
gaoxieen said:
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Updater error:7
already use twrp 3.4.0-0
Click to expand...
Click to collapse
I tried several Roms as a base before installing this one (lineage, MiUi 12, EU dev) and finally installing on top of the latest cDroid worked ?.
Great Rom ?
I've had a problem with all the Roms I've mentioned above, and this one, when I load eBay.co.uk on Chrome, it crashes after a few seconds, think it's something to do with loading up webview, anyone else had this?
Have tried turning location off, and also using Chrome beta...

Wow, I remember using your Beelink TV Box ROMs. I'd probably still be using a Beelink today if DRM hadn't ruined all of the China boxes.
Glad to see you here.

gorilla p said:
Wow, I remember using your Beelink TV Box ROMs. I'd probably still be using a Beelink today if DRM hadn't ruined all of the China boxes.
Glad to see you here.
Click to expand...
Click to collapse
Yeah, it really is a shame how WideVine L1 and Netflix whitelists crippled those Chinese TV boxes. I made the switch to tablets for the Samsung Galaxy Tab A 10.1 (2019) and hopefully will have a little better luck at keeping the budget Android tablet segment alive. Right now it's probably more neglected than the Android TV platform was.

Magendanz said:
Yeah, it really is a shame how WideVine L1 and Netflix whitelists crippled those Chinese TV boxes. I made the switch to tablets for the Samsung Galaxy Tab A 10.1 (2019) and hopefully will have a little better luck at keeping the budget Android tablet segment alive. Right now it's probably more neglected than the Android TV platform was.
Click to expand...
Click to collapse
Yeah after a lot of research, this tablet was arguably the best value available based on the hardware that you get for the money. I paid 168 for the WiFi version.
My only gripe was that immediately after, Xiaomi stopped supporting it. They released it and dropped it almost immediately. Luckily there has been decent custom ROM support to keep this thing alive.
For the TV boxes, I have both a MiBox 3S and an eMatic Jetstream 4K. I have been happy with the JetStream 4K. I just wish they would release something with better hardware, but not go overboard like the nVidia shield so it costs 180.
A L1 Netflix supported GT King would be perfect.

I don't suppose anybody has tried google family link and is working on this Rom before I try it?
many thanks

New release is posted:
Downloads:
Nexus_Stock_LQ-20201011-clover.zip
Change Log:
20201011:
Switched to the Xiaomi OEM camera app from GoogleCamera v4.4, which still had some compatibility issues.
Updated to lineage-17.1-20201011-UNOFFICIAL-clover.
Latest Google apps from OpenGApps Stock variant (20201010)

Related

[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][ALPHA][10] LineageOS 17 for OnePlus 7 Pro [20191230]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Instructions
- You must be on OOS 10 Release (10.0.GM21AA) before flashing this ROM.
Note: if you fail to boot this, make sure you are on OOS 10 Release (10.0.GM21AA) on BOTH slots, or at least the other slot that you are flashing this ROM to. If you flashed OOS 10, then rebooted to flash this ROM, you will be on the original slot again, which was not on OOS 10.
- Download latest build here and anything else you need (you can use beta OpenGapps for Android 10 from here)
- Flash the latest build using latest TWRP by mauronofrio
- Reboot to recovery again
- Flash the other stuff like Magisk and OpenGapps
Known issues
- There *might* be some crashes here and there because it's in very early stage. Future updates can also break compatibility, so be aware before flashing any of these alpha ROMs.
- SELinux is still permissive Enforcing since 20191107
- MTP (USB storage mode) and USB tethering doesn't work. Something about USB is probably broken. fixed since 20191012
- If OpenGapps somehow crashes, that's not a bug of the ROM. I have already introduced dirty hack to make it somewhat work but it can still crash from time to time. (if Google's SetupWizard crashes on first boot and drops you back to boot logo, just wait until it gets into it again. Finish the setup without choosing anything fancy. You can alternatively choose to remove SetupWizard entirely from Recovery)
- Fingerprint sensor does not work in Always-on-Display mode. fixed since 20191012
- sensors might not work fixed since 20190925
- DRM (Digital Rights Management) is dead. No netflix for now. fixed since 20190925
- There might be other broken stuff but for me it seems that I have a mostly usable phone now.
Downloads
20191230-1: https://www.androidfilehost.com/?fid=4349826312261688031
20191107-1: https://www.androidfilehost.com/?fid=4349826312261621843
- Updated LOS 17 code
- Fixed Wi-Fi tethering
- SELinux is now set to enforcing.
20191012-1: https://www.androidfilehost.com/?fid=1899786940962606188
- Rebased kernel and vendor blobs to OOS 10 Release 10.0.GM21AA
- Fixed USB MTP and tethering support
- Fixed support for touchscreen gestures
- Fixed fingerprint sensor in Always-on Display (actually this was a feature accidentally introduced by the touchscreen gestures)
- Updated LOS 17 source code
20190929-1: https://androidfilehost.com/?fid=1899786940962596983
- Updated kernel & vendor blobs to OOS 10 OpenBeta 2 (since the kernel source code for release hasn't been released yet when I started working on this)
(this could break stuff, if anything breaks please upload your logs and revert back to older versions)
- Fixed display-breaking issues with Google Maps
20190925-1: https://www.androidfilehost.com/?fid=1899786940962593202
- Fixed sensors stalling (not responsive) when auto brightness is enabled or light sensor is requested
- Fixed DRM (widevine) support
- Synced LOS17 updates
20190922-1: https://www.androidfilehost.com/?fid=1899786940962591077
Source code
All available on my GitHub https://github.com/PeterCxy
Maintainers
luk1337, PeterCxy

thank you , downloading right now

Excellent downloading now

Can this be installed on the T-Mobile version?

doughill526 said:
Can this be installed on the T-Mobile version?
Click to expand...
Click to collapse
Yes only if you flash the international msm file to your phone

NickMidd91 said:
Yes only if you flash the international msm file to your phone
Click to expand...
Click to collapse
I have international on my phone now. If i flash this will i have data because I lost data flashing other roms

doughill526 said:
I have international on my phone now. If i flash this will i have data because I lost data flashing other roms
Click to expand...
Click to collapse
Yes you should

As android 10 has native support for 5G, would this work on the 7 Pro 5G?
Sent from my [device_name] using XDA-Developers Legacy app

speedyjay said:
As android 10 has native support for 5G, would this work on the 7 Pro 5G?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Probably not, since it's temporarily using a pie vendor and blobs.

Nice done, thanks, I can't wait to try

Good god this alpha build is good. Total daily driver material. Very very slight bugs, but they're cosmetic. Congrats on the first 10 rom to boot properly with magisk!

I have issue with dpi it's keep changing to small and big number like from 304 to 620 alone , even when I set it to 411 after reboot it change

Can anybody share their way of booting this rom? I tried the method stated and can t get it to boot.

While using it, it shuts down and enters recovery. Is there something that I'm pressing or it just crashes?

shooterlgk said:
Can anybody share their way of booting this rom? I tried the method stated and can t get it to boot.
Click to expand...
Click to collapse
Try this
1. Flash OOS 9.5.11
2. Flash LOS 17
3. Flash Twrp 3.3.1-65 unofficial
4. Reboot to twrp
5. Flash Gapps 10.0 unofficial
6. Format data (if it doesnt boot)
7. Reboot to system

bursuk2007 said:
While using it, it shuts down and enters recovery. Is there something that I'm pressing or it just crashes?
Click to expand...
Click to collapse
Mine's not shutting down at all. I'm using F2fs, decrypted, and using Magisk 19.4 stable.

SugouNobuyuki said:
Try this
1. Flash OOS 9.5.11
2. Flash LOS 17
3. Flash Twrp 3.3.1-65 unofficial
4. Reboot to twrp
5. Flash Gapps 10.0 unofficial
6. Format data (if it doesnt boot)
7. Reboot to system
Click to expand...
Click to collapse
After I tried formatting data it still don't boot lol idk what im doing wrong

shooterlgk said:
After I tried formatting data it still don't boot lol idk what im doing wrong
Click to expand...
Click to collapse
Flash twrp than flash twrp installer .. i think u miss that one !

shooterlgk said:
After I tried formatting data it still don't boot lol idk what im doing wrong
Click to expand...
Click to collapse
Not sure... It worked for me and I didn't even have to format data, coming from Pixel Experience Pie. Maybe try flashing a pie rom first, booting it up, then flashing this.

Fairly stable rom so far. Had 1 force reboot right after setup but hasn't happened again. Magisk 19.4 working. Warp charge works despite not showing up on mine.

[ROM][12.1][grus] LineageOS 19 for Xiaomi Mi 9 SE [UNOFFICIAL]

Reserved

Hello, thanks for your work. What about contributing to an official LineageOS release?

Hello, thanks for your work. I find this rom pretty stable and usable; FOD is fast. With Magisk 24.1 + Safetynet fix the bank apps work, and even Google Pay.
Are you going to add f2fs support for data and cache partitions in a next build? Fingerprint sensor is always enabled, even with screen off. It will be possible to enable it only when screen is on?
Thank you

After 2 days, I can say: the ROM is very good, but there are some lags when you unlock the phone via fingerprint (an animation displayed on unlock slows down the entire phone) and when you use Telegram. I think there is a problem related to graphic driver

Stribianese91 said:
Hello, thanks for your work. I find this rom pretty stable and usable; FOD is fast. With Magisk 24.1 + Safetynet fix the bank apps work, and even Google Pay.
Are you going to add f2fs support for data and cache partitions in a next build? Fingerprint sensor is always enabled, even with screen off. It will be possible to enable it only when screen is on?
Thank you
Click to expand...
Click to collapse
Hello, thank you for your feedback. For supporting FOD on AlwaysOnDisplay, fingerprint sensor is always enabled. See https://github.com/kyasu/android_device_xiaomi_grus/commit/2e8c936638cf0c5869e495b44dcea4d6125bef0f

It is so coooool! I am gonna give it a try. I was waiting for such support of Android 12, mb Android 12L soon ^^

kyasu said:
Hello, thank you for your feedback. For supporting FOD on AlwaysOnDisplay, fingerprint sensor is always enabled. See https://github.com/kyasu/android_device_xiaomi_grus/commit/2e8c936638cf0c5869e495b44dcea4d6125bef0f
Click to expand...
Click to collapse
Hello,
When stable version will be released?
Other question, if I install LOS 18 A11, will I have to clean flash when upgrading to LOS 19 A12?

rulon332 said:
Hello,
When stable version will be released?
Other question, if I install LOS 18 A11, will I have to clean flash when upgrading to LOS 19 A12?
Click to expand...
Click to collapse
Do not ask for ETA. LOS 19 itself is not official yet.
I think dirty flash is OK, but clean flash is recommended.

I uploaded the new build (lineage-19.0-20220312-UNOFFICIAL-grus.zip).
See changes: https://github.com/kyasu/android_device_xiaomi_grus/commit/ea9c8e7ff29a4c036c46400f82cc0e60f0885de2

kyasu said:
I uploaded the new build (lineage-19.0-20220312-UNOFFICIAL-grus.zip).
See changes: https://github.com/kyasu/android_device_xiaomi_grus/commit/ea9c8e7ff29a4c036c46400f82cc0e60f0885de2
Click to expand...
Click to collapse
Thank you for this update. In order to use it after your first build, I must use adb sideload / wipe dalvik cache / reinstall gapps?
Because I have just installed it without wipe dalvik and witouht gapps, had a lineage start llo, reinstalled the lineage os + dalvik cache + gapps, it started but now google telephone, messages and play store bugs.
Sorry, it has been a long time since the last time I did something like this (samsung a3 2016)

Stribianese91 said:
Hello, thanks for your work. I find this rom pretty stable and usable; FOD is fast. With Magisk 24.1 + Safetynet fix the bank apps work, and even Google Pay.
Are you going to add f2fs support for data and cache partitions in a next build? Fingerprint sensor is always enabled, even with screen off. It will be possible to enable it only when screen is on?
Than
Click to expand...
Click to collapse

kyasu said:
Hello, thank you for your feedback. For supporting FOD on AlwaysOnDisplay, fingerprint sensor is always enabled. See https://github.com/kyasu/android_device_xiaomi_grus/commit/2e8c936638cf0c5869e495b44dcea4d6125bef0f
Click to expand...
Click to collapse
Can you add f2fs support for twrp? Thanks..

kyasu said:
Safetynet can pass on this ROM (without magisk).
Regardless of the actual security update date, android security update is always displayed as 2021-04-01 for safetynet passing.
Click to expand...
Click to collapse
Hi kyasu, I installed the ROM today and it runs really smoothly, thanks for the great work. My only issue is it doesn't seem to pass SafetyNet: it passes basic integrity but not CTS profile match. Google Pay doesn't work either. I followed your installation instructions exactly except I flashed the firmware (which the instructions didn't mention) right before wiping. I've tried installing Magisk and the SafetyNet Fix but they didn't change anything. I'd really appreciate any help on this.

liu-shuyuan said:
Hi kyasu, I installed the ROM today and it runs really smoothly, thanks for the great work. My only issue is it doesn't seem to pass SafetyNet: it passes basic integrity but not CTS profile match. Google Pay doesn't work either. I followed your installation instructions exactly except I flashed the firmware (which the instructions didn't mention) right before wiping. I've tried installing Magisk and the SafetyNet Fix but they didn't change anything. I'd really appreciate any help on this.
Click to expand...
Click to collapse
Could you tell me your hardware information?
Please install any terminal emulator app and type the following:
getprop | grep ro.boot.hwc
GLOBAL or CN should be shown as a result.
Thank you.

kyasu said:
Could you tell me your hardware information?
Please install any terminal emulator app and type the following:
getprop | grep ro.boot.hwc
GLOBAL or CN should be shown as a result.
Thank you.
Click to expand...
Click to collapse
The command returns [ro.boot.hwc]: [CN], and indeed the devices was bought in China. I thought firmware was the only difference between regions but look like this is not the case!

liu-shuyuan said:
The command returns [ro.boot.hwc]: [CN], and indeed the devices was bought in China. I thought firmware was the only difference between regions but look like this is not the case!
Click to expand...
Click to collapse
I uploaded the new build (lineage-19.0-20220315-UNOFFICIAL-grus.zip) which returns the GLOBAL fingerprint even on the CN model. Please try this build and tell me the safetynet result.

kyasu said:
I uploaded the new build (lineage-19.0-20220315-UNOFFICIAL-grus.zip) which returns the GLOBAL fingerprint even on the CN model. Please try this build and tell me the safetynet result.
Click to expand...
Click to collapse
Thank you! The new build passes SafetyNet. G Pay adds cards fine too.

Hi! Thank you very much… it’s very nice ROM.
I’ve notice the status bar circle battery icons on the right aren’t the same as the clock on the left.
EDIT:
Noticed the same thing on GSI version… it’s for the privacy dot?

I have not tried for a long time any ROMs. Is widevine lost, by installing a different rom?
Will Netflix, Amazon, Disney work?
Thx

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.

Development [ROM][OFFICIAL] RisingOS Android Project v1.1 [BLUEJAY][6/19/23]

{
"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"
}
Proudly Presenting RisingOS for Google Pixel 6a [Bluejay] !!!
What is RisingOS?
RisingOS is a Open Source Aftermarket Android Operating System that aims to deliver unique and refreshing android experience.
Based on Android 13 | Tiramisu QPR2 | with LineageOS
Screenshots
What's working?
- Everything should be working. If theirs a bug, please grab a locat.!! Or specific instructions to replicate the issue.
Build Variations
- Google Apps Build : 05/18/2023 and so on
- Core Builds : Coming Soon.!
- AOSP/Vanilla Builds : 5/20/2023 and so on
Installation Notes : FASTBOOT Method Avaliable Now !!
Rom should be able to be flashed over any rom now via fastboot method.
1. reboot from into bootloader ( power off device and hold volume down + power, must have unlocked bootloader )
2. Flash Rom with this command ( May remove -w flag to save user data , but we dont support dirty flash bug reports )
fastboot -w update path/to/rom.zip
Click to expand...
Click to collapse
3. Start First Boot
Downloads :
Mirror 1 : SourceForge
Mirror 2 ( Old Builds ) : Google Drive
Android OS version: 13.0.0_r44
Security patch level: May 2023
Build author/Device Maintainer: Austin Young ( EliteBlackKaiser)
Device tree source code: https://github.com/LineageOS/android_device_google_bluejay
Device vendor source code: https://gitlab.com/the-muppets/proprietary_vendor_google_bluejay/-/tree/lineage-20?ref_type=heads
Kernel source code: https://github.com/LineageOS/android_kernel_google_gs101
Firmware source code: https://github.com/risingTechOSS
Firmware created by: The risingOS Team & ME

Came from crdroid and works fine
1.error
Pixel Launcher crashes but can be fixed by installing rising Launcher

update is out, new flashing instructions.! Enjoy bluejay users!

Good job

All time restart

Max0nchik said:
All time restart
Click to expand...
Click to collapse
Please make sure your device is on latest official April firmware. ( Bootloader, radio etc... ) And then make sure your using the 5/2 GAPPS build.
Also has been confirmed that majority of custom kernels don't work and if you do find one that boots it , theirs still a possibility it'll give issues.

This is the best custom ROM I've tried so far, great performance, battery life, and plenty of customisations, congratulations dev!! Thanks.
My only problem is Android auto is not working and Bluetooth sometimes fails.
Is anyone having the same problem?

Currently only Core with Core GAPPS
Click to expand...
Click to collapse
What about integrating the Data Restore Tool app to restore apps and data from google account?
I tried to fastboot update from April firmware without wiping data => it bootloops.
I made factory reset. SetupWizard crashes when touching button on restore page (probably because no Data Restore Tool found).
I can install Data Restore Tool from Google Play. How to run SetupWizard again?
System partition doesn't have enough space to place the Data Restore Tool in it manually and wipe data again. Running using Activity Launcher allows me even to select apps to restore, but nothing happens then, aclivity closes.

I'd like to try this soon. Would be first time for me, but will read myself through before i begin anyway.
Just a question: is it possible to disable the google search bar on home screen in rising launcher? I currently use the "nova launcher" for this feature. But apart from that, in free version it is not as cool as i was hoping for.

peety02 said:
I'd like to try this soon. Would be first time for me, but will read myself through before i begin anyway.
Just a question: is it possible to disable the google search bar on home screen in rising launcher? I currently use the "nova launcher" for this feature. But apart from that, in free version it is not as cool as i was hoping for.
Click to expand...
Click to collapse
Yes, you can disable the search bar.
After you try it, please let me know if you have problems running Android auto, thanks.

a1ex2k said:
What about integrating the Data Restore Tool app to restore apps and data from google account?
I tried to fastboot update from April firmware without wiping data => it bootloops.
I made factory reset. SetupWizard crashes when touching button on restore page (probably because no Data Restore Tool found).
I can install Data Restore Tool from Google Play. How to run SetupWizard again?
System partition doesn't have enough space to place the Data Restore Tool in it manually and wipe data again. Running using Activity Launcher allows me even to select apps to restore, but nothing happens then, aclivity closes.
Click to expand...
Click to collapse
For 5/02 build and lower it's required too have at least April's firmware. And I'm unsure why you're bootlooping as each build is tested by me. But each build I use the flag
fastboot -w update
Click to expand...
Click to collapse
Because i do clean flashes for each build. To ensure that when Im booting it that it is a clean install.. it's mentioned that you can remove the -w flag but if issues arise that I can't help unless I'm able to replicate the issue or a log cat and or kernel log.

RisingOS v1.1 Babylon has been released with Mays security patches. Enjoy.

thank you so much for this genius rom for bluejay - have it on my pixel now + it looks fn great!
tip: better extract with 7zip in windows, cause windows explorer doesn't recognize the way to extract these zips... . always extracts to another zip ( 10 times) . in windows 11 insider preview build.

thimprfct said:
thank you so much for this genius rom for bluejay - have it on my pixel now + it looks fn great!
tip: better extract with 7zip in windows, cause windows explorer doesn't recognize the way to extract these zips... . always extracts to another zip ( 10 times) . in windows 11 insider preview build.
Click to expand...
Click to collapse
Be sure to update to the latest 5/10 build as their was many fixes by source devs in the last few days.

Hi, how is the battery life of the Rom compared to the stock os? improved or the same, and does it have VoLTE enabled?

Nemeroz said:
Hi, how is the battery life of the Rom compared to the stock os? improved or the same, and does it have VoLTE enabled?
Click to expand...
Click to collapse
Asking about battery compared to stock is all user dependent , and have gotten no feedback from telegram group about a battery drain so it should be fine and yes we have Vo5g so I'd imagine we support VoLTE

Ghostcain said:
Came from crdroid and works fine
1.error
Pixel Launcher crashes but can be fixed by installing rising Launcher
Click to expand...
Click to collapse
Where can I find this launcher? Can it be installed on stock pixel ROM if rooted?

I'm on the May update on stock. Can I still flash this ROM or do I have to down grade to April?

EliteBlackKaiser said:
RisingOS v1.1 Babylon has been released with Mays security patches. Enjoy.
Click to expand...
Click to collapse
Thanks a lot to bring this beautiful ROM to Bluejay.
Can you help to look into the shortcut icons as QR Code scanner shows disabled to select in shortcuts even after installing google camera and so is the device controls.

Madaevena22 said:
I'm on the May update on stock. Can I still flash this ROM or do I have to down grade to April?
Click to expand...
Click to collapse
No if your on may firmware then flash the may build (5/10) and you should be good to go.

Database Info

welcome