Latest update: 2018-06-12 To view a changelog, you can visit https://review.lineageos.org/#/q/status:merged+branch:cm-14.1 for a rough idea up to the build date.
Hi all. I was able to compile this stock build of LOS 14.1 thanks to the efforts/hard works of Skrilax_CZ, bhb27, the folks who created RR, and those over at Lineage OS/CyanogenMod. It takes some minor features from RR (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock LOS 14.1 and I use this daily. The other authors/devs and I assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings -> More -> Cellular networks -> Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
Also if on Verizon, you should most likely select VZWINTERNET as your APN under Settings -> More -> Cellular networks -> Access Point Names (might not show up at first, but eventually loads)
My recommendations to install:
Install TWRP if you haven't already
3.1.1 - https://www.androidfilehost.com/?w=files&flid=39562 (forum:http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308)
Perform a backup of your current system/ROM (if coming from another ROM).
Perform a factory reset/wipe (if coming from another ROM).
Install the .zip
Install the appropriate google apps.
http://opengapps.org/. I would think nano or micro is best, ARM, and 7.1
Wipe dalvik/art cache if you install another kernel. I highly recommend BHB27 kernel
https://www.androidfilehost.com/?w=files&flid=135512
Reboot and enjoy
Here is the link to the latest ROM on the hosting website:
[2018-06-12]https://androidfilehost.com/?fid=746163614322270411
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=128790
Optional Components:
Remove SU/Root: https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip (Lineage OS extras:https://download.lineageos.org/extras)
BHB27 Kernel: https://www.androidfilehost.com/?w=files&flid=135512 (forum:http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526)
BHB27 Kernel Adiutor: https://www.androidfilehost.com/?w=files&flid=48767
iSU: https://www.androidfilehost.com/?w=files&flid=120360 (forum:http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348)
TurboToast: https://play.google.com/store/apps/details?id=com.bhb27.turbotoast
I'll be back to post updates fairly regularly (~ every few weeks), but I also work full time in addition to being a dad (those of you who are know how that is ) and won't really be able to respond to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109 (device, vendor, and kernel trees). Thanks and God bless.
Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk
hpbrasil said:
Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk
Click to expand...
Click to collapse
Thanks. No I didn't change anything about the kernel. There isn't a good alternative (that I know of yet) so I just used it straight from bhb for now.
How do I disable the capacitive buttons and use on screen nav bar instead?
Sent from my DROID Turbo using Tapatalk
My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.
The rom is almost 100%, the battery is well lasting me .... 1 screen time every 10% quietly, the only problem I really noticed was sending images on whatsapp that is not 100%, you send catch screen and photos taken by whatsapp ... now send images from the gallery do not know why, it just outside joys and once again thank you for your development. @calsurferpunk
eddiemc12 said:
My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.
Click to expand...
Click to collapse
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk
{
"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"
}
Root ok
muhammadtalha-13 said:
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).
If not bother you wanted to report a small simple mistake that can not encomodar only to warn even ... In Menu> Settings> Developer Options> animator duration scale, the second option is 0.5x and there is 5x....When I click on the Home screen and select background he simply FC, that's Gallery problem equal to whatsapp that has pictures not ...
The maintainer of CrDroid said I do not know how to use the Android and it really is a problem of rom and he would not listen to me and said she did not like my attitude. @calsurferpunk
calsurferpunk said:
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).
Click to expand...
Click to collapse
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU? I actually tried developer option after flashing SuperSU. Maybe that's why it didn't work. Let me know if I am right then I'll try the correct procedure.
Sent from my Pixel XL using Tapatalk
muhammadtalha-13 said:
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).
Just as a quick update, next time I post an updated build I believe I know how to skip including iSu and kernel auditor by default. I'll make sure to include a way to download them and include them separately if this is successful. The goal of this is to keep it as close to stock CM 14.1 and still be functional so that anything you want to add can be done by your own free will .
calsurferpunk said:
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).
Click to expand...
Click to collapse
Okay got it now. I'll try again later tonight and will confirm here.
Sent from my Pixel XL using Tapatalk
no super su, i enabled root in developer setting and it works fine.
太棒了
Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.
Hlcpereira said:
Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.
Click to expand...
Click to collapse
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.
Shooting Star Max said:
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.
Click to expand...
Click to collapse
No man, the problem still at the music player which goes installed in the ROM.
Related
JB AOSP 4.3 alpha 1 by LeTama
{
"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"
}
*** DISCLAIMER ***
I'm not responsible if it breaks your device! Don't install it if you want something stable.
*** /DISCLAIMER ***
Be careful, this is a very preliminary build. Backup your stuff and expect problems.
DON'T TRY TO FORMAT any unformated external USB drive/key with OTG cable, it could format internal storage instead !!!
Introduction
Here is my port of JB AOSP 4.3 for our Xperia S. This is a work in progress, it's currently missing few of the patches I used in 4.2.X and few things are completely untested.
Installation and downloads
You need unlocked bootloader and a working recovery.
Download installation zip from here, mirror thanks to @androidlover007 (I know, uploaded.net is not the fastest of the earth, multipload mirrors coming soon. I'm not against posting any other mirror).
Copy it to internal storage
Wipe Data/Cache
Install gapps for 4.3. Currently, we don't have "official" gapps from CM team, I used PA ones with good success.
Reboot and let the rom settle down a bit
Important: Current release has a recovery with broken offline charging, you should flash a fixed one after installing the rom to avoid any trouble. Check this post.
Kernel source code is here (branch jb-4.2-experimental).
Note: this rom flashes its own kernel that comes with TWRP recovery and last version of Boot Manager. Just use volume up/down to navigate boot manager menu and power to select if you want to go to TWRP. Don't play with Boot Manager options if you don't know what you're doing.
Status
Working:
Display / 3D (with some stuttering, under investigation)
Audio (without LPA, won't add it)
Calls / SMS / MMS / Data
Camera (Pictures / Videos)
Bluetooth
Wifi
Wifi Tethering
Sensors
GPS
Hardware video encoding/decoding
Offline charging
NFC
SELinux
WIFI EAP. (untested, can anyone confirm ?)
Not working:
FM radio: I won't implement it in aosp with current proprietaries as they will conflict with 4.2+ bluetooth.
HDMI.
Auto brightness (disabled now)
And probably more, let me know
Missing
TRIM Support
Known issues
1080p video stuttering (waiting for new Sony firmware)
voip audio disabled, voip is going through normal channels (waiting for new Sony firmware)
Wifi direct disabled (waiting for new Sony firmware)
subway surfers game is not working
SuperSU not working. You can flash a working one here.
Changelog
2013/08/07 - Alpha 1
- SELinux added
- Media server crash on audio notification fixed
- Move to SD fixed
- Ril crash on some mvno fixed.
- SuperSU updated to 1.51
- 12 and 9M camera size
- Panorama fix
- Google backup selected as default
- EAP finished
2013/08/03 - Alpha 0
FAQ
Can I flash any kernel with it ?
No. This rom is using Nexus 4 proprietaries and requires matching video drivers. You must use embedded kernel.
Something is not working, crashed, whatever, how can I help ?
Please provide logs! Description is not enough, I need at least logcat and ideally dmesg. If phone reboots, go to recovery, get the /proc/last_kmsg file and provide it to me.
Dev options are missing ?
No, they're just hidden, it's now the default behavior in 4.2.x. To enable it, go to settings / about and tap multiple times on build number, menu will be enabled and stick after reboot.
* reserved, now you can go on *
Great And Fast Work.
Omg you are fast man
Sent from my LT26i using xda premium
Is there need to report bugs or it is too early for such thing?
Anyhow, I'm downloading right now, will report back with observations.
Log:
- Booting seems fine, some glitches but nothing to worry about...
- Font is kinda different, I like it, very much. It is even more close to Helvetica and for me it is very nice typeface porn
- Touch vibration is kinda shorter, more direct but weaker.
- Developer tools are updated with very nice features, everything mentioned at Google I/O 2013.
- Animations are smoother. It's not that "new ROM" smoothness, transitions between screens appear like constant 60fps, without that lag that sometimes occurs regardless on hardware.
- There are some differences in first time configuration, nothing radical but still...
- Google Play Store wont open, close it and relaunch and then it will show TOS. It lags a bit.
- Is it me or DPI is kinda different? Everything seems to be bigger. Icons in drawer, Google play apps... SystemUI feels kinda same. EDIT: 320dpi.
- AOSP keyboard icon is different. RAM usage is same, no lower usage or anything special. Available RAM - 622 MB.
- Touch responsivness seems a bit better.
- Texdroider DPI (DPI changer) doesn't work. On 4.2.2 it would work with OpenSEMC, but it's not the case on 4.3.
SuperSU does not work (no su binaries), this ROM is unrooted. To root it again do the following:
Download SuperSU 1.51 from here
Move it to your root folder on your phone
Turn your phone off, boot it into recovery
flash that zip you copied to your root folder "SuperSU 1.51"
Reboot to system.
Voila!
damn your way ahead of me
letama
Click to expand...
Click to collapse
Damn your way ahead of me,aw whell , ill try in 4.4 xD
PS did you use the google 4.3 source code or did you use Sonys Aosp source code... or did you port this from XZ??
still learning....
i love that warning about formatting otg drives d:
great
mirhl said:
i love that warning about formatting otg drives d:
Click to expand...
Click to collapse
i am so happy,now a android 4.3 developing for our xperia s.hope it is soon capable of daily use.THANK YOU to all developers :laugh: i love yall very much
switzerland92 said:
Is there need to report bugs or it is too early for such thing?
Click to expand...
Click to collapse
Yes, please do. I didn't run it for a long time, I really need feedback.
Envious_Data said:
Damn your way ahead of me,aw whell , ill try in 4.4 xD
PS did you use the google 4.3 source code or did you use Sonys Aosp source code... or did you port this from XZ??
still learning....
Click to expand...
Click to collapse
This is google 4.3 code, with my 4.2.x device tree and proprietaries. I'll take a shot at merging 4.3 kernel drivers soon.
mirhl said:
i love that warning about formatting otg drives d:
Click to expand...
Click to collapse
Burnt once! I didn't include 4.2 patch. Code changed, so it could work properly, but I have to test it first with a good backup
Ty bro
letama
Click to expand...
Click to collapse
hopefuly soon i will know as much as you
lets see if sony make a 4.3 or a 4.4 (sony themed)
i will definatly try to port that to an older device
Hey awesome letama! Are you going to release the ROM for loop? Tried your script but it didn't work. Thanks
letama said:
Yes, please do. I didn't run it for a long time, I really need feedback.
Click to expand...
Click to collapse
To keep it on one place and as organized as possible I'll edit my post with new info for you and others that are afraid to flash it right away
EDIT: Well, I don't have root. SuperSU says I must manually re-root and I must, quote, "consult the relevant forums for your device" which in this case is your thread
Someone please mirror i can never use uploaded.net
Sent from my 4.2.2 PAC powered Xperia S via Tapatalk
Noob question: Can adreno 220 ever support OpenGL ES 3.0 ?
skifyr123 said:
Hey awesome letama! Are you going to release the ROM for loop? Tried your script but it didn't work. Thanks
Click to expand...
Click to collapse
Yes, script can't work. I will upload it tomorrow, it's prepared but untested.
switzerland92 said:
EDIT: Well, I don't have root. SuperSU says I must manually re-root and I must, quote, "consult the relevant forums for your device" which in this case is your thread
Click to expand...
Click to collapse
Check first posts, known issues sections, SuperSu is not up to date in the rom. There is a link to one that can be flashed and works...
I'm going to download as soon as I get home. About performance, similar to 4.2.2?
Enviado desde mi Xperia S usando Tapatalk 4 Beta
Ben36 said:
Someone please mirror i can never use uploaded.net
Click to expand...
Click to collapse
Electricity problem here, I lost my multiupload I'll restart tomorrow.
{
"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"
}
What This Is
This is a personal project to get Lineage OS running on my Pixel 3a. As such it is provided as is, though I will endeavor to provide regular builds and offer limited support as I am able.
What's Been Tested
This is my daily driver, so I've flashed ElementalX kernel and openGapps Pico over stock.
T-Mobile (at least), camera, wifi, bluetooth, gps are used regularly without issue.
What Was Not Tested
Root
Squeeze sensor
Gapps beyond Pico
Known Issues
eSIM doesn't work and has been removed
If flashing Gapps, an app downloaded at first-time setup Data Transfer Tools will crash constantly and needs to be uninstalled. This may mean you can't transfer data from an old phone to this one via setup.
Downloads
Lineage OS 16.0 Unofficial
Installation
I have not had success with an installable zip for TWRP yet, so the rom images must be flashed via fastboot. You should be familiar with fastboot before attempting to install this rom. It is recommended that you back up your current OS before installing a new one.
Installing this or any rom will void your warranty.
After unlocking OEM and your bootloader, boot into bootloader either with fastboot reboot bootloader or by holding VOLUME DOWN + POWER from power off, plug your phone into the computer.
If running on a linux machine with fastboot installed you can execute the flash-all.sh script included in the download. Alternatively or otherwise:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w (to wipe cache and data)
After installing, Gapps (ARM64, 9.0, see note in Known Issues), kernels, Magisk (UNTESTED) and other zips can be installed as normal via TWRP.
I Wanna Go Back
Up-to-date stock images are provided by Google and can be reflashed from bootloader.
Just follow the instructions at the top of the page.
Sources
LineageOS
Vendor proprietary packages (thanks to Dirty Unicorns and ZVNexus)
Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!
gee one said:
Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
Click to expand...
Click to collapse
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how) wifi calling works fine on T-Mobile, and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
koichirose said:
Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!
Click to expand...
Click to collapse
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working works with Google Photos installed. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.
pipyui said:
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how), and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.
Click to expand...
Click to collapse
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
Nevermind @koichirose, camera Motion works fine once I installed Google Photos. :good:
gee one said:
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
Click to expand...
Click to collapse
It's odd that it only shows up when I connect to logcat via adb. Local terminal logcat doesn't show me these squeeze errors.
Also, wifi calling working on T-Mobile :good:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
Chronzy said:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
Click to expand...
Click to collapse
I ran into this same issue - had to remove Data Transfer Tools (don't need root for this, since it was downloaded by gapps) and do a cache wipe to be able to download apps again. I think it blocks you from using the play store until you complete google's first-time setup, and this app blocks that (not to mention it crashes frequently).
I'll test out Magisk when I'm able. You may need to enable root access to apps in dev settings, but I'm unsure.
OMG thank u so much! Was waiting for this forever, hope you can make twrp zip
Getting "Sim not Found" on both rooted and unrooted
Tiebe said:
Getting "Sim not Found" on both rooted and unrooted
Click to expand...
Click to collapse
Have you checked OP? eSIM doesn't work. Need physical SIM
Uzephi said:
Have you checked OP? eSIM doesn't work. Need physical SIM
Click to expand...
Click to collapse
I have a physical sim. I solved the problem tho. I just had to reflash the stock radio image
Thanks for putting a build together! Provides even more incentive for me to make the switch over to a 3a Keep up the good work.
Is the device showing as certified without root?
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
Unstroofy said:
Is the device showing as certified without root?
Click to expand...
Click to collapse
It is not certified.
Dreamsocks66 said:
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
Click to expand...
Click to collapse
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
Geo411m said:
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
Click to expand...
Click to collapse
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
pipyui said:
It is not certified.
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
Click to expand...
Click to collapse
I'll test for you
Neat, I'll get a build together for ya tonight then.
Any chance of a flashable zip for the official twrp?
{
"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 for your device also attempting to bringing many of the best features existent today
Features: Get from HERE
Flashing Instructions: Check This Post
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel Source
Download:
ROM: Click HERE
GAPPS: Already included
Changelog: Click HERE
crDroid Community Telegram.
If you like my work, consider a donation: My PayPal
Get flashing Instructions: HERE
This instruction is only for Windows user.
Linux user can execute commands manually.
Follow instruction properly.
Always take backup of your data before flashing
Once more
Hi, anyone tested if Android Auto works?
Installed this yesterday, the rom is very stable, works fast and has a lot of customization options.
Haven't found many bugs, all in all, great rom to try if you want to use android 11
Only major bug seems to be that NFC isn't working for me
NFC looks to be working now, not sure why in wasn't initially
NFC seems to still be spotty.
Sometimes it works properly, sometimes it can't be turned on
Not sure what it is, but a reboot "fixes" it (albeit temporarily)
Allways had CRDroid on my OP5T and my and my girlfriend has it on her OP6. At this moment i have XtendedRom 5 on my OP7TPro. If i change to this version, lost my encryption data?. Can i install it from fastboot without problems with my data or sdcard ?. THANKS.
New update is available now.
ElHechicero said:
Allways had CRDroid on my OP5T and my and my girlfriend has it on her OP6. At this moment i have XtendedRom 5 on my OP7TPro. If i change to this version, lost my encryption data?. Can i install it from fastboot without problems with my data or sdcard ?. THANKS
Click to expand...
Click to collapse
I've also flashed without loosing my internal data, But I can't take guarantee same will be haapen with you, So first take backup of internal before proceeding. First I've executed these commands:
fastboot erase system
fastboot erase odm
fastboot erase product
fastboot erase vendor
Then flashed CRDroid and no data loss. But still take internal data backup first just in case.
Really great rom thank you, i only have one bug so far, the right/left balance slider option don't work with Bluetooth ear buds.
How's the battery backup, anyone has any data for that?
madscenes said:
How's the battery backup, anyone has any data for that?
Click to expand...
Click to collapse
Excellent.
mukesh22584 said:
Excellent.
Click to expand...
Click to collapse
I tried the first build but had many UI glitches. Have they been fixed as I'm really temped to try out this ROM. (I went back to oos10)
Also a couple of questions:
1) Can I install OnePlus dialer? I like the raise to accept feature
2) Is the OP oos 11 camera app included or do I have to flash it myself. If so how?
3) OnePlus buds support? Can I just use the oneplus buds app or do I have to use something else?
Thanks for building for this phone!
mukesh22584 said:
New update is available now.
Click to expand...
Click to collapse
Fantastic news, can we get a changelog for the release?
Things I like to mention which probably aren't device specific but could be improved:
- Slide statusbar for brightness only goes down to 33%, not to 1%
- Fingerprint is misaligned in a lot of apps (so you see 2 FODs)
- Hold back to kill app doesn't seem to work properly, device vibrates as if an action was performed but the app doesn't get killed
- Hold power to enable flashlight doesd work, but would be better if a vibration was added for haptic feedback to the user
- NFC is still hit and miss, sometimes it does work, somtimes it doesn't
- Warning about SELinux every boot
- as an added option: Automatic enablement of DC Dimming under 15% screen brightness
Abaddon said:
Hi, anyone tested if Android Auto works?
Click to expand...
Click to collapse
Seems to work fine, tho I don't have an android auto compatible car, so I can't test it entirely..
The app seems to work tho
rom is great. smooth, customisable, didn`t found any bugs until now but have one issue that I quess is rom related, can`t install usb audio player from playstore, says app isn`t compatible with this version. I guess there are other apps that have this issue. other than that I like it very much! thanks dev!
SohrabHamza said:
I tried the first build but had many UI glitches. Have they been fixed as I'm really temped to try out this ROM. (I went back to oos10)
Also a couple of questions:
1) Can I install OnePlus dialer? I like the raise to accept feature
2) Is the OP oos 11 camera app included or do I have to flash it myself. If so how?
3) OnePlus buds support? Can I just use the oneplus buds app or do I have to use something else?
Thanks for building for this phone!
Click to expand...
Click to collapse
Please tell me what type of UI glitches.
1) No you can't install untill someone modded to use with custom rom.
2) No oos cam included and you can't flash/install.
3) I don't have oneplus buds so can't confirm.
Giblet-dono said:
Fantastic news, can we get a changelog for the release?
Things I like to mention which probably aren't device specific but could be improved:
- Slide statusbar for brightness only goes down to 33%, not to 1%
- Fingerprint is misaligned in a lot of apps (so you see 2 FODs)
- Hold back to kill app doesn't seem to work properly, device vibrates as if an action was performed but the app doesn't get killed
- Hold power to enable flashlight doesd work, but would be better if a vibration was added for haptic feedback to the user
- NFC is still hit and miss, sometimes it does work, somtimes it doesn't
- Warning about SELinux every boot
- as an added option: Automatic enablement of DC Dimming under 15% screen brightness
Click to expand...
Click to collapse
Your all provided info is correct, I'll try to improve as much as possible. Just get logs for Nfc if possible. Thanks for your info.
darkoj2007 said:
rom is great. smooth, customisable, didn`t found any bugs until now but have one issue that I quess is rom related, can`t install usb audio player from playstore, says app isn`t compatible with this version. I guess there are other apps that have this issue. other than that I like it very much! thanks dev!
Click to expand...
Click to collapse
I've tried and OTG USB Video Audio player installed without any issue.
mukesh22584 said:
Please tell me what type of UI glitches.
1) No you can't install untill someone modded to use with custom rom.
2) No oos cam included and you can't flash/install.
3) I don't have oneplus buds so can't confirm.
Your all provided info is correct, I'll try to improve as much as possible. Just get logs for Nfc if possible. Thanks for your info.
I've tried and OTG USB Video Audio player installed without any issue.
Click to expand...
Click to collapse
usb audio player pro*
can`t install it no matter what, clear play services, playstore with no luck
mukesh22584 said:
Please tell me what type of UI glitches.
1) No you can't install untill someone modded to use with custom rom.
2) No oos cam included and you can't flash/install.
3) I don't have oneplus buds so can't confirm.
Your all provided info is correct, I'll try to improve as much as possible. Just get logs for Nfc if possible. Thanks for your info.
I've tried and OTG USB Video Audio player installed without any issue.
Click to expand...
Click to collapse
Can we get a changelog?
fingerprint is not working so well some times. It said my finger moved too fast.
clean flash and works properly still not working
{
"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"
}
Google Pixel 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.[/CENTER]
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 2.
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.
walleye
walleye - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
gah, in the unofficial I included _too new_ a google camera. Will be fixed in next build.
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
New build is up - fixed.
> New build is up - fixed.
Confirmed working. Thanks!
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
I downloaded a software from Chrome.When I try to install it.The system rebooted.
dcshallot said:
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
Click to expand...
Click to collapse
yup, it's verifying, leave it and wait for it - or try a different cable.
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
cognid said:
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
Click to expand...
Click to collapse
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
is this build stable for daily usages?
galibalmasanick said:
is this build stable for daily usages?
Click to expand...
Click to collapse
of course
npjohnson said:
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
Click to expand...
Click to collapse
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
cognid said:
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
Click to expand...
Click to collapse
Yeah, Snap is gone. Only Camera2 now.
My unofficial ship with Google Camera.
npjohnson said:
yup, it's verifying, leave it and wait for it - or try a different cable.
Click to expand...
Click to collapse
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
dcshallot said:
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
Click to expand...
Click to collapse
What small issue?
I can't fix it if I don't know what it is lol
npjohnson said:
What small issue?
I can't fix it if I don't know what it is lol
Click to expand...
Click to collapse
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
dcshallot said:
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
Click to expand...
Click to collapse
1. I have no idea why your apps report huge size. That's not a Lineage thing tho.
2. That's... Odd what router do you have?
3. That is definitely an app bug, VPNs work here.
1.As you see, Open Camera show a huge size. But actually, at first, the size was normal. Well, before Open Camera, it was Nova Launcher. It just need some time that the LOS make it so.
2. I'm in China, and I use a VPN service built by myself but it's not located in US. 26.26.26.1 is a US IP, right?
Should I make a clean LOS install? I'm not sure after the adb no response accident, has something went wrong? I don't want to download & backup & restore, that's horrible.
Hi,
I've just installed this ROM. Thanks for the work !
I just have a problem with the customization menu in the settings. The activity is crashing instantly.
It's the menu "Fond d'écran et style" in french (don't know the exact name in english :s).Tthe one allowing to change home and lockscreen background.
Is it working for you ?
{
"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"
}
Google Pixel 3a
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 3a .
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.
sargo - Official builds - Potentially coming soon!
sargo - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Works very well Android 13 it's weird but it's very snappy and fast! Although I found that flashing the new recovery broke the WiFi so I went back to 19,1 recovery and now everything works.
The download links are dead at the moment, for me anyway. I was just about to attempt to upgrade.
EDIT: working again now
I have installed it but every time it starts up I get a notification:
Trust - System security
SELinux is not enforcing, your security has been weakened
Glenn2 said:
I have installed it but every time it starts up I get a notification:
Trust - System security
SELinux is not enforcing, your security has been weakened
Click to expand...
Click to collapse
You can disable that notification in the setting
But seriously: I also had this after upgrading from 19.1 with 19.1 recovery. Then it was gone after clean flashing with 20 recovery.
Awesome ROM! Thanks a lot OP!
gibbsnich said:
You can disable that notification in the setting
But seriously: I also had this after upgrading from 19.1 with 19.1 recovery. Then it was gone after clean flashing with 20 recovery.
Awesome ROM! Thanks a lot OP!
Click to expand...
Click to collapse
When you say clean flash you mean wipe the data and start over?!
Or did you mean, load the new recovery and flash from that?
I just did what the instructions on the website say and sideloaded it using the existing recovery.
I don't want to wipe data unless I really, really have to, it is otherwise working fine (so far anyway).
EDIT: I dirty-flashed it again with adb sideload from the 20 recovery and SELinux is still disabled.
I upgraded to 20.0-20221101-UNOFFICIAL from 19.1-20220909-UNOFFICIAL without wiping data. Then SELinux began to show notification. After updating to 20.0-20221105 the notification disappeared.
I updated and flashed the new 11/05/22 recovery and the WiFi issues were fixed so everything is functional, although I'm still seeing SElinux disabled, of which I have no idea. But I'm really liking this new rom regardless, it's a bit frustrating that some apps downloaded 3rd party are just flat out broken, they don't even attempt to run in some cases
jmat2240 said:
I updated and flashed the new 11/05/22 recovery and the WiFi issues were fixed so everything is functional, although I'm still seeing SElinux disabled, of which I have no idea. But I'm really liking this new rom regardless, it's a bit frustrating that some apps downloaded 3rd party are just flat out broken, they don't even attempt to run in some cases
Click to expand...
Click to collapse
What apps are broken?
Selinux permissive is a temporary thing
npjohnson said:
What apps are broken?
Selinux permissive is a temporary thing
Click to expand...
Click to collapse
The apps I'm talking about are modded , none of the play store official apps, but like SL Bridge, Ram Cleaner, even when I give them all permissions to include accessibility, but yes this is very minor, it's few and far between and my guess is because they are modified packages is all.
Hi - can you guys check if your wifi is running at full speed?
When I do a Speedtest (via Ookla app) my download speed starts off high then quickly drops to half, every time (50M then drops to about 25M). Upload speed is half too.
From other devices (including a Samsung tablet on LOS18.1) this does not happen.
It didn't happen previously with my 3a either. It seems to have coincided with the change to LOS20 but it could of course just be a coincidence that's why I want to check with other users of the ROM.
EDIT: I have discovered that it's the location stuff that cripples the speed. If I turn off the location permission for the Speedtest app or just switch off the 'precise location' switch, the speed is back to normal. Must be an Android 13 'feature'. (The green dot in the corner is always on during the speedtest.)
npjohnson said:
What apps are broken?
Selinux permissive is a temporary thing
Click to expand...
Click to collapse
For me, Bitwarden does not work at all. It instantly closes as soon as you try to login.
EDIT:
The Fdroid version works fine
Can anyone check if selinux enforcing on lasted build?
Clearall2 said:
Can anyone check if selinux enforcing on lasted build?
Click to expand...
Click to collapse
It is not
Now "adb shell getenforce" returns "Enforcing" after updating to 20.0-20221119-UNOFFICIAL. Thanks a lot.
I would like to know if the Google One backup (that include calls history, SMS and all the OS system & apps setting) works with this custom ROM.
kerpert said:
I would like to know if the Google One backup (that include calls history, SMS and all the OS system & apps setting) works with this custom ROM.
Click to expand...
Click to collapse
yup.
Hello!
Wow I really like this build.
I reccomend everyone to run this command in bootloader mode
Code:
fastboot -w
in order to wipe your userdata for a fresh install.
Anyway, I would love a degoogled version, just like lineageos 19.1 ones. I don't like to use google services, and I may not be the only one.
That would be great.
Keep up your work. Cheers!
SkippyDream said:
Hello!
Wow I really like this build.
I reccomend everyone to run this command in bootloader mode
Code:
fastboot -w
in order to wipe your userdata for a fresh install.
Anyway, I would love a degoogled version, just like lineageos 19.1 ones. I don't like to use google services, and I may not be the only one.
That would be great.
Keep up your work. Cheers!
Click to expand...
Click to collapse
Officials won't have google apps.
'Select' button in recent apps view does not work.