{
"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
Related
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.
{
"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 11, 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. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/instantnoodle/install
Downloads :
https://download.lineageos.org/instantnoodle
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Kernel source: https://github.com/LineageOS/android_kernel_oneplus_sm8250
{Mod edit: Link to kernel source added on request of OP}
Donate:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
thank you for making op8 officially
niceeee
mattie_49 said:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
Click to expand...
Click to collapse
Am planning to take the dip... which is the correct Gapps to use? And if you can spare time to write the steps to install them would be appreciated.
sjgoel said:
Am planning to take the dip... which is the correct Gapps to use? And if you can spare time to write the steps to install them would be appreciated.
Click to expand...
Click to collapse
Still unknown. NikGapps work fine but break "hey google". Working with ultranoob one of the maintainers to get sorted out. I'll lyk asap. Use Nikgapps if you don't use your assistant hands free. Adb sideload name of package. Through Lineage recovery
Install LineageOS on instantnoodle | LineageOS Wiki
wiki.lineageos.org
mattie_49 said:
Still unknown. NikGapps work fine but break "hey google". Working with ultranoob one of the maintainers to get sorted out. I'll lyk asap. Use Nikgapps if you don't use your assistant hands free. Adb sideload name of package. Through Lineage recovery
Install LineageOS on instantnoodle | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Ok. Did you try to use the suggested gapps on the lineageOS website MindTheGapps for lineageOS 11 ?
sjgoel said:
Ok. Did you try to use the suggested gapps on the lineageOS website MindTheGapps for lineageOS 11 ?
Click to expand...
Click to collapse
Yes and Nikgapps both
mattie_49 said:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
Click to expand...
Click to collapse
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
mvmike said:
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
Click to expand...
Click to collapse
Tried going to official from unofficial and didn't like it. Had to clean flash to work.
Stoked to have an official build! It installs & runs great, thanks to all who made this possible for OP8!
It's nice to know it will always be updated and maintained - I was on DOT OS and loved it with Hasty kernel but the thread appears dead so here I am.
mvmike said:
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
Click to expand...
Click to collapse
I did the copy partions zip only because im coming from fresh msm then unlock. And only had oos on one side.
Copying bugs from the closed thread with some additions:
1) Display is too light on minimal brightness, it's not comfortable to use in darkness. Also, it seems its too dark on maximum brightness, but I am not sure.
2) Phone speaker too loud on minimal volume. Everybody in room can hear my interlocutor.
3) Gravitation sensor work fine in apps like SatStat, but not in camera apps: OpenCamera and GCam. While making a photo, horizontal line in camera react to position change very, very slowly. It take about 15 seconds to display real horizon.
4) Not sure its a software problem, but nevertheless: Acc daemon + AccA app cannot limit battery charging voltage. This feature is very usefull to prolong battery live.
5) Phone setting to check Proximity settings before activation is not working, so, phone aims to go active in pocket. Proximity sensor itself is working (proved with SatStat app).
6) May be related to (1). Light sensor shows illumination value about 2..6 times more that it should be (tested with SatStat on a few devices). Error multiplicator not so big in dark place and grows with illumination level.
passion8059 said:
Tried going to official from unofficial and didn't like it. Had to clean flash to work.
Click to expand...
Click to collapse
Same issue here, but hey, another factory reset it's worth it if we end up with a supported official build
Is it possible to get Magisk or something else like it installed with this? I'd like to root and prevent apps from knowing, so they all function as normal.
Guys do i need to copy partitions a and b if im changing from Pixel Experience?
chriswcs said:
Is it possible to get Magisk or something else like it installed with this? I'd like to root and prevent apps from knowing, so they all function as normal.
Click to expand...
Click to collapse
Lineage never had any issue with Magisk, have both nikgapps (core) + Magisk working perfectly.
Just follow the instructions and remember to let system boot once after fresh install before
mvmike said:
Lineage never had any issue with Magisk, have both nikgapps (core) + Magisk working perfectly.
Just follow the instructions and remember to let system boot once after fresh install before
Click to expand...
Click to collapse
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
chriswcs said:
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
Click to expand...
Click to collapse
Search for payload dumper. Can be used in Windows as a standalone program, or making use of Python3 under Linux as well. Doing so, you will be able to extract the boot.img to be patched with Magisk. Very good explanations on howto, here on XDA.
chriswcs said:
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
Click to expand...
Click to collapse
Although made for Nokia, the steps in this thread generally apply. You have to download your Oneplus OTA of course.
[Guide] How to extract payload.bin from OTA
This is guide for extract payload.bin from OTA zip file ----------------- Pre-requirement: - Python3 ----------------- For extract OTA update Please flow step by step instruction Step 1: Get a OTA for Nokia 7 plus -> here Step 2: Download...
forum.xda-developers.com
{
"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"
{
"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.
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
official builds can be found here = https://sourceforge.net/projects/crdroid/files/coral/9.x
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCES
Kernel: https://github.com/putzwon/android_kernel_google_msm-4.14
Device tree: https://github.com/putzwon/android_device_google_coral
Vendor: https://github.com/putzwon/proprietary_vendor_google_coral
ElmyraService: https://github.com/putzwon/android_packages_apps_ElmyraService
putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
what about flame? is it updated build?
cRdroid rocks the PX4!!! Thank you putzwon!!!
what the different with this version..?
link
Thank you so much sir
putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
thaaaaaaaaaaaaaaaaaaaaaanks
can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?
very good
{
"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"
}
anonras said:
what the different with this version..?
link
Click to expand...
Click to collapse
This is the latest Android 13 (crDroid-v9.0 android 13.0), your link is the older 12.1 Android
vlbr said:
can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?
Click to expand...
Click to collapse
It might work, but stick with OP steps, those 110% WORK, but up to you. I gave up on TWRP when A/B partitions came out and chose to just stick with and use stock ROM recovery. That will always work, TWRP, maybe not so much, IDK, it might, but you wont get the same type of help if you choose your own path (TWRP).
Also, just an FYI on nomenclature, this isn't firmware, but ROM, firmware contains all partitions, drivers, ETC., this is just the OS (ROM).
Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time
tonyhieu said:
Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time
Click to expand...
Click to collapse
huh?
GROOVYJOSHCLARK said:
huh?
Click to expand...
Click to collapse
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.
tonyhieu said:
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.
Click to expand...
Click to collapse
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.
@putzwon, I have used this OS (ROM) since Friday, and thoroughly testing EVERYTHING! WOW, I am literally floored at how well EVERYTHING works!!
I have NO ISSUES, NO BUGS, NO SHOWSTOPPERS, nada. Even Now Playing works, I am floored by all of this! It is amazing, and I rarely say that about a ROM (with no bugs also being reported - at the same time), and as I noted earlier, in the past, cRdroid wasn't great for me (random bugs, and/or missing features I rely on). NOT this version, this version IS GREAT FOR ME, I have EVERY SINGLE possible tweak I want/need/use, PLUS functional services / RIL (Radio Interface Layer) I.E. CALLs/TXT/MMS, PLUS no bugs, or FCs, or anything that would keep me away!
Normally, I use LOS, and LOS only (while testing all other ROMs for users and myself), but always landing back with LOS, not this time! I am STICKING WITH cRdroid for the foreseeable future, it is my DailyDriver and will remain so until something changes (but doubtful at this point)!! I have everything I need, baked right into the ROM, so I don't even need my LSPosed modules (other than SafetyNetFix once ROOT'ng)!
EXTREMELY WELL DONE and THANK YOU FOR THIS ROM!!!! For the rest of XDA users, this ROM WORKS! It works EXTREMELY WELL, is bug-free (from my extensive testing and standpoint). I haven't found any bugs yet (not a single one)!
GROOVYJOSHCLARK said:
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.
Click to expand...
Click to collapse
Yes, this is a type of 4XL, it's cheaper to 20% .
Installed it yesterday and almost everything is working perfectly. The only feature that seems to be missing Soli which is a shame since it's a fun novelty.
best rom ever love you
thaaanks
Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks
ojessie said:
Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks
Click to expand...
Click to collapse
it is easy
i do it everytime I flash a custom rom
you need to root your phone using magisk
then instal
Migrate - ROM backup 5.0.1from play store
open it and take a full backup of your installed apps
copie this backup to your laptop
and after flashing this perfect rom
copie the backup from the laptop to the phone
and root the phone again
and instal
Migrate flasherfrom play store
open it
and flash the file you backed up
this way you will have allll your apps including your banking apps with all your data
you will not have to instal anything twise...
good luck
it is easy
don't worry..