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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Hello
I have created this rom using the Lineage sources and a fix from the creator of the rom of this page: http://customromz.proboards.com/thread/11/crdroidandroid-9-marlin-v5-zip?page=1&scrollTo=16. I don't have too much knowledge in how the rom is developed so perhaps I won't be able to solve all your questions.
Please let me know if you have any issue.
Regards
SourceTree
LineageOS
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your google pixel, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Install stock rom
2) Copy crDroid zip, gapps zip and twrp zip to your device
3) Boot into Recovery
4) Wipe cache, system, & data (or just cache & system for a dirty flash).
5) Flash ROM
6) Reboot into recovery
7) Flash gapps
8) Boot up
9) when the setup wizard starts execute the following command to allow it to connect to wifi
adb shell pm grant com.google.android.apps.pixelmigrate android.permission.WRITE_SECURE_SETTINGS
10) Open the contacts and phone apps and accept the permissions requests
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
you tell me...
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Joe pacino
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
I might take a look at this, what have you done since the last build in the main thread?
GeTex said:
I might take a look at this, what have you done since the last build in the main thread?
Click to expand...
Click to collapse
Hello
Thanks for your answer. What your are interested in is the process I follow to compile the rom ?. I can post the script I use, that is one I have created from the crdroid sources: https://github.com/crdroidandroid/crdroid_build.
Regards
Why not post this in the Pixel Development forum? Would gain more traction there.
PapaSmurf6768 said:
Why not post this in the Pixel Development forum? Would gain more traction there.
Click to expand...
Click to collapse
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
jontxo said:
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
Click to expand...
Click to collapse
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
PapaSmurf6768 said:
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
Click to expand...
Click to collapse
It is the rom that I use in my phone in a daily basis and I haven't found any issue yet.
Are anyone try this rom? How was the performance and battery life? Any problems?
SoKa1993 said:
Are anyone try this rom? How was the performance and battery life? Any problems?
Click to expand...
Click to collapse
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
PapaSmurf6768 said:
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
Click to expand...
Click to collapse
You are welcome. And thanks for trying it.
Regards
jontxo said:
You are welcome. And thanks for trying it.
Regards
Click to expand...
Click to collapse
Suitable for daily driver? How frequent will it to be update?
SoKa1993 said:
Suitable for daily driver? How frequent will it to be update?
Click to expand...
Click to collapse
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
jontxo said:
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
Click to expand...
Click to collapse
Thanks. Will try it tonight and give feedback to you.
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
kkjb said:
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
Click to expand...
Click to collapse
I am glad everything is OK.
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
SoKa1993 said:
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
Click to expand...
Click to collapse
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
After a few days on this I can say this is easily the best Pie ROM I've put on my phone. Features are great and no problems to report in my day to day use.
Couple notes I had; I had to flash the Mini Gapps since the Stock package said it was too large for the partition. After booting, the trick to get WiFi to work during setup didn't work immediately but did work after clicking around a bit. Then Photos was crashing on start so I deleted it as a system app and just installed it from Google Play. That works fine, and I haven't had any other apps do this.
Thanks again OP, will be on this one for a while.
jontxo said:
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
Click to expand...
Click to collapse
I just flash it and it work like usual. Maybe something wrong when u flash the rom file. Did u clean flash it or dirty? Mine clean flash. After flashing the rom, i boot it to system. Then install gapps, magisk. Boot it again. Then franco. Work like a charm. Btw, this rom is smoother than other roms. Love the extra setting on this rom. Thanks for ur work.
New version of crdroid- 5.8
Hello
I have uploaded a new version of the room, the 5.8.
https://androidfilehost.com/user/?w=settings-dev-files&flid=298676
Greetings
Related
{
"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"
}
For
Motorola Atrix
What is King Kang?!?
King Kang is essentially a hybrid ROM - its a mixture of AOKP, CyanogenMod, and ParanoidAndroid, bringing all their customizations to one rock solid and quick ROM. These numerous features combine to create a blend of features not seen anywhere else before. Make the user interface yours with this ROM. Change the DPI the ROM runs at, tweak the interface to your hearts content, while enjoying great battery life and stability. Never before have these features combined to create a ROM as feature-packed as King Kang. Credits for the features goes directly to the teams responsible - AOKP and CM for their respective work, and ParanoidAndroid for their wonderful DPI on-the-fly modifications. Without these teams, this ROM would not be possible.
Click to expand...
Click to collapse
How To Flash
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid
Install Rom: Wipe INSIDE ROM
When you select "Reboot Not", you'll get a CWM error, IGNORE IT
Install OPTIONS or Gapps
WIKI/FAQ Located: To be reworked
Click to expand...
Click to collapse
PLEASE NOTE: I will NOT provide ParanoidPreferences.apk in this ROM zip. The devs of that great ROM have asked that the particular apk NOT be included in NON-PA zips. They put in the work, so I respect their wishes. That being said, I will NOT link the file nor do I want to see it linked here.
To get it, do the following:
Boot into King Kang and set up Gapps
Download Paranoid Android ROM zip
Download Root Browser
Use Root Browser to extract the file from the PA zip
Place it into /system/app
Set permissions to RW, R, R
Reboot
Click to expand...
Click to collapse
To successfully set Tablet mode in King Kang, follow the following steps....
Go into settings
Go into ROM Control
Go into Navigation Bar and enable bar, allow SU
Go back and go into General UI
Click Force Tablet UI and reboot manually
Once you come back from the reboot, go into Settings
Go into Paranoid Settings
Go into Workspace
Click on what mode y
Click to expand...
Click to collapse
Bugs??:
KNOWN ISSUES:
Videocamera : Use VideoCam Illusion
Slight Lag possible on screen transitions
USB tether
The graphics related issues are due to not having proper drivers to use for this. Don't ask for an ETA on a fix. Moto won't be giving us the drivers, so there is no fix
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
Version you're using
What type of fwipe you did and what ROM you came from
Have you restored any data from something like Titanium Backup
What app is misbehaving and what you were doing when it started
Logcats<--THIS IS PREFERRED.
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
Click to expand...
Click to collapse
Downloads:
ROM file is Located HERE
Options Chooser is Located HERE
My latest CWM: V1 as well as Aroma-Prep
can be downloaded HERE
Click to expand...
Click to collapse
Credits:
AOKP, Paranoid Android, Cyanogenmod, and King Kang Teams-Without all of them, this ROM doesn't exist
scott.hart.bi=for helping me with source building
Jokersax11-for being my initial inspiration on Atrix, being a cool guy, and helping me along in my early days
Amarullz=for creating the Aroma Installer
Spleef-for collaborating on those first builds that got me into Android
Alcapone263-for donating an Atrix coming to a home near me
All my testers and users
Anyone else I may have forgotten
Click to expand...
Click to collapse
Kernel Source: HERE
Click to expand...
Click to collapse
Mine
Mine 2
Th3Bill said:
Mine 2
Click to expand...
Click to collapse
Mine 3
Bill just wanted to thank you, like everyone else that will be flooding this thread. Thanks for sticking around and continuing such great development!
jeffreygtab said:
Mine 3
Bill just wanted to thank you, like everyone else that will be flooding this thread. Thanks for sticking around and continuing such great development!
Click to expand...
Click to collapse
Way I look at it, these 2 devices (Photon and Atrix) were the ones I started with, so as long as we can make viable roms on it, I'm going to
Pretty Slick so far. Will run for a couple days. Thanks th3bill
Sounds AWESOME
Just waiting for some screens to give it a chance ;3
Sounds awesome; where will I find the corresponding gapps?
Regards
redThd said:
Sounds awesome; where will I find the corresponding gapps?
Regards
Click to expand...
Click to collapse
Can either use Options overflash or the Gapps by EPinter. There are also some by Justinbean that are pretty good too
I'm getting 'set_perm:some changes failed' at the end of the installation process :crying::crying::crying::crying:
I'm getting the same fault on liquid as well so I think I have put the saved logs here?
Hardware acceleration is not worikng, wright??
barry_ said:
I'm getting 'set_perm:some changes failed' at the end of the installation process :crying::crying::crying::crying:
I'm getting the same fault on liquid as well so I think I have put the saved logs here?
Click to expand...
Click to collapse
Ill fix tonight
Sent from my LG Optimus G
WiFi not turning on at all for me no matter what configuration chosen during installation and with all possible wipe combinations Pressing WiFi does nothing.
Newest AOKP does not have this issue, running it now.
I installed it over latest cm10 from the bill. Just wiped cache and dalvik. The Rom is running fast and smooth without any issues, every thing is ok including WiFi.
Sent from my MB855 using xda app-developers app
Must be me then....
I think he is saying try AOKP then flash this rom. It's worth a try.
Sent using my Jelly fingers.
I never use WiFi much so I didn't notice. Its borked as stated above.
Other than that nice ROM.
I can confirm, also, that WiFi does not turn on with this ROM. Th3Bill did post in the Liquid Smooth thread that he would be posting a fix for this very soon.
Thanks Th3Bill!!
Thanks for the ROM, nothing to report other than a thanks.
redThd said:
WiFi not turning on at all for me no matter what configuration chosen during installation and with all possible wipe combinations Pressing WiFi does nothing.
Newest AOKP does not have this issue, running it now.
Click to expand...
Click to collapse
homerwasa said:
I never use WiFi much so I didn't notice. Its borked as stated above.
Other than that nice ROM.
Click to expand...
Click to collapse
blumenthala said:
I can confirm, also, that WiFi does not turn on with this ROM. Th3Bill did post in the Liquid Smooth thread that he would be posting a fix for this very soon.
Thanks Th3Bill!!
Click to expand...
Click to collapse
Unless a new build is up, wifi is working for me as normal.
I was able to finally get wifi to work. I installed paranoid android first and then installed KingKang and everything works beautifully - including wifi!!!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+ with treble support https://forum.xda-developers.com/showpost.php?p=78708796&postcount=2
- backup everything before install including efs partition
- wipe cache and vendor partitions before install
Install:
- Flash zip in compatible TWRP
- Don't forget about gapps (arm 9.0)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Doesn't work:
RIL
Download:
0207 build
T710: https://drive.google.com/open?id=1VScAyyvr8WcAseGAFVmIM4DPd2-Q1Us6
T715: https://drive.google.com/open?id=1q7oHTyV_JJGG3B56h0Wd_QiUsKn6hVzg
Device sources:
https://github.com/bonuzzz
treble-enabled twrp
t710: https://drive.google.com/open?id=1d0YycDthOxo7IM1b5gZbNI7zCdlu2Cix
t715: https://drive.google.com/open?id=1wrZKDMQcosQRrZGDypIG27Oqv-zL6m2G
known issues:
info on data partition is not accessible
Hi, thank you for the build, awesome! I was going to install LOS 15 but now I'll go directly for this one. I'll tell you how it goes
Sent from my Aquaris M5 using Tapatalk
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Hockron said:
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Click to expand...
Click to collapse
Unfortunately it's not so simple. So no new builds for t810/t815 at least in near future (several months). I focus on t710/t715 only.
as usual gr8 job ma8 considering. We got los15.1 stable finally seeing this beta makes me really happy so, keep up the good work...
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
bonuzzz said:
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
Click to expand...
Click to collapse
Its very sad for everyone that you abandoned the rom, but I understand what not having the time and the energy means. Thank you very much for the build. In any case I installed as I said before.
I haven't tested it much but for the time being its running pretty smooth. I installed some apps and no crashes so far. Just an error message at boot saying something happened, after closing it everything OK.
I add some screenshots here.
Ill keep posting issues if I find any. Do you think I could compile your sources in my computer?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-T710 using Tapatalk
what to do when you are sick and staying at home? answer is simple:
new lineage16 builds are uploaded.
all hw stuff has been brought up except ril on t175, so no mobile network support yet. everything else should work.
links are in first post.
How much work should it be done to port this onto T810? And do you know anybody is doing it?
frankieboy1233 said:
How much work should it be done to port this onto T810? And do you know anybody is doing it?
Click to expand...
Click to collapse
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
T815 plzz. I have no knowledge about porting roms, but if by any way I can help u in porting this to T815 plzz let me know...
sweet, i saw your trebel twrp in the other forum, freaking fntastic
#1. Loaded trwp and ROM only no root
Excellent power 97 percent remain after 13 hours
No 5gz WiFi. But because I had nothing else loaded I couldn't see the nvram_net.txt settings.
So I tried to load pico and lineageos add-on su, and had several boot up and setup issues with the play services kept crashing. After bypassing lots of stuff, gave up and reloaded, I was able to see the root permissions in the developer settings, but lineageOS extras shows only arm 15.1 no 16 for root. Thought that was an issue. Silly me I didn't do a logcat. Before I did #2
#2nd try wipe , load, pico and magisk 17 . no magisk 17 in apps.
Did a bypass load apps to get to desktop. Had a couple " this device has errors, please contact manufacturer "
Play store was able to install apps, but I had no access to my paid apps. See #1 I wanted to fix my 5gz WiFi files. And I use es file explorer pro, but since I didn't have root... Well.
Play store recovered my programs am going to try magisk 18 . BRB
Looks nice, a couple of google play store bugs, an actuall desktop black out.
In conclusion, awesome ! Work !
Will fiddle some more. couldn't get a logcat
Downloaded all my gapps, and I found an unofficial root for lineageos 16 in another forum.
Trying again. Cheers
https://androidfilehost.com/?fid=11410963190603875495
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
bonuzzz said:
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
Click to expand...
Click to collapse
i have an 815 to test as well
---------- Post added at 05:35 AM ---------- Previous post was at 05:17 AM ----------
bonuzzz said:
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
Click to expand...
Click to collapse
Same here.
I got 5gz to work . I changed
Code:
ccode=US
regrev=69
Based on several posts over the years, I researched what regrev is in related to the ccode
It relates to what frequencies and I believe power outputs for different countries legal free and open radio frequencies.
The clues are in the driver for the wireless device source code.
Here is a broadcom driver for the 3.10 kernel
https://android.googlesource.com/ke...drivers/net/wireless/bcmdhd/dhd_custom_gpio.c
In there is a small database that should be consulted when you boot up your device and your country code should be selected when the driver is accessed
This has never worked properly for any lineageos based ROM.
Also most stock ROMs do not have this in their correctly.
All the files in /system/vendor/etc/wifi that have nvram in their name ( total 6 files ) need updated manually with an editor with root access.
As soon as I enter codes and reboot, I see all the 5 gz and many other networks that normally are too far away.
Kind of a chore to do this on every reloaded device, but that's what it takes.
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
samw52000 said:
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
Click to expand...
Click to collapse
Same here I cant flash Gapps with out it sticking on Samsung's boot logo
@samw52000 @legojoe8 read the first post carefully, in particular about twrp
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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your MOTO G 2015, or coming from another ROM: <--THESE MAY NEED UPDATING FOR YOUR PARTICULAR DEVICE; BE THOROUGH IN INSTRUCTIONS-->
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip <--& vendor img, if applicable--> to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
NONE !!!!
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google (obviously)
- LineageOS (secondarily)
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
Device source code
-------------------------
source
For download, check crdroid.net/osprey
Link for 11/04 build
https://androidfilehost.com/?fid=1395089523397939170
Gdrive for 03/04 build
https://drive.google.com/file/d/1dpk6EFHlZ-FoAEiGotzXoKUiPWpMUvaA/view?usp=drivesdk
Here's gdrive mirror of 29/03 build
https://drive.google.com/file/d/1-RpqLO-4x7xniJILIXACTbvX9M-5ciYm/view?usp=drivesdk
Change log (03/04)
----------------------------
Updated device tree
Se is now fully enforcing
Apn issue with certain carriers fixed
Themes issue fixed
Fixed random reboot for XT1543 ( few users reported)
Changelog ( 29/03)
-------------
Added back volte icon
Settings menu revamped and material designed
Battery menu designed
Volte working fine
SeLinux is now enforcing
PS - a lot of thanks to chil and aki for their contribution to msm8916 devices especially osprey
Going to test it.. thanks
Hi, I want to test this, but I don't understand the vendor image and the link for this is dead.
Can you help?
Thanks for the work.
Pat
pbonamy said:
Hi, I want to test this, but I don't understand the vendor image and the link for this is dead.
Can you help?
Thanks for the work.
Pat
Click to expand...
Click to collapse
Ah ...it's there in thread itself as by default... It's not for osprey as clearly mentioned.. out vendor comes prebuilt with the rom zip itself... Anyhow am removing it from o.p
Thank you
anisgvr said:
Ah ...it's there in thread itself as by default... It's not for osprey as clearly mentioned.. out vendor comes prebuilt with the rom zip itself... Anyhow am removing it from o.p
Thank you
Click to expand...
Click to collapse
Hi,
Install is OK,
Thanks
error 7 when installing
edit: apparently sorry the rom was not downloaded well
Best rom in pie for osprey.. great work developer anisgvr .. smooth rom .. volte and working.. Iam just loving it
---------- Post added at 07:26 AM ---------- Previous post was at 07:21 AM ----------
Will post a full review soon...
Just flashed it.
UI was very laggy after first boot so I did a restart and that fixed the lag.
It is smooth now with a bit of glitches here and there but smooth for most of the times.
There are no major bugs.
Everything is working fine.
Best pie ROM for osprey no doubt.
Will post if I found any bugs.
flash_15 said:
Just flashed it.
UI was very laggy after first boot so I did a restart and that fixed the lag.
It is smooth now with a bit of glitches here and there but smooth for most of the times.
There are no major bugs.
Everything is working fine.
Best pie ROM for osprey no doubt.
Will post if I found any bugs.
Click to expand...
Click to collapse
Cool
Hi, I install yesterday, all was good but this morning my phone didn't response and I need to power off with long press on the power button, after the boot all the system parameters goes to default, I configure one more time and after one hour same problem. I return to the old rom . It's a pity.
It is a excelent rom but it is not recommended to osprey with 1GB from RAM, very laggy in my XT1543. As recommendation is to include a option to remove the search bar, it is ugly and unnecessary, I think.
Hello everyone, does anyone notice that mms (image text message) is not working on any pie rom? I tried 3 different latest pie rom and same problem each time. You can send text but not images! Changing APN is useless or not working.
Except that, it seems that you've done a great job with latest rom , everything else works great ??
Gapps Link Broken
Gapps link is not working. Please provide.
Data services not working in roaming. Using jio in India.
rb.00082 said:
Gapps link is not working. Please provide.
Click to expand...
Click to collapse
Why do you need a link for that!
Go to opengapps.org and download it
Its arm, 9.0 and pico or nano or mini whichever you prefer.
pbonamy said:
Hi, I install yesterday, all was good but this morning my phone didn't response and I need to power off with long press on the power button, after the boot all the system parameters goes to default, I configure one more time and after one hour same problem. I return to the old rom . It's a pity.
Click to expand...
Click to collapse
For me it's working fine .
Help me with logs so I can look into it
pbonamy said:
Hi, I install yesterday, all was good but this morning my phone didn't response and I need to power off with long press on the power button, after the boot all the system parameters goes to default, I configure one more time and after one hour same problem. I return to the old rom . It's a pity.
Click to expand...
Click to collapse
figg2blet said:
Hello everyone, does anyone notice that mms (image text message) is not working on any pie rom? I tried 3 different latest pie rom and same problem each time. You can send text but not images! Changing APN is useless or not working.
Except that, it seems that you've done a great job with latest rom , everything else works great
Click to expand...
Click to collapse
Can't sent an MMS ...sorry
anisgvr said:
For me it's working fine .
Help me with logs so I can look into it
Click to expand...
Click to collapse
Hi,
Sorry I can't give you logs because I need my phone and with jour ROM I can't use it.
Regards.
{
"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 Z2 Force
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 Z2 Force.
Join our Moto Z2 Force Discord!
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.
nash
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.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in LineageOS, as the normal proximity sensor works fine.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
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 nash 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_msm8998
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.
npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly
Very good upgrade, thanks for the hard work and making this real
Thank you for not letting our device die
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
The clock app is not working and I think usb tethering is not working.
Vibration is not working
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.
vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?
npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?