Database Info

List of Active Development Custom ROMs for ROM Cooker

In Alphabetical Order
AOSP ROM
ABC
Aquari
Benzo
Google+
Bliss
Google+
BlissRoms-Devices
Carbon
Google+
Copperhead
Cyanide
Google+
CyanideDevices
DarkKat
Elixir
Evervolv
Google+
Euclidean
Google+
Krexus
Google+
LiquidDeath
Google+
LiquidNougat
Master-Branch
Minimal
Google+
Nitrogen
Google+
nitrogen-os-devices
noobbuilds
PureNexus
Google+
SAOSP
Google+
Screw'd
Google+
Sheve
TorMan
TwistedCore
Google+
UBERROMS
Google+
UnholyDevs
Unlegacy-Android
Velvet
YAOSP
Google+
AOSP+CAF ROM
AICP
Google+
Anonymity
AOKP
Google+
AospExtended
Google+
BeanStalk
Google+
Candy
Google+
CandyDevices
Cardinal
Google+
Cardinal-devices
CMRemix
Google+
Cosmic
Google+
Crap
crDroid
Google+
crdroid-devices
Cypher
Google+
Darkness-reDefined
Discovery
Emotion
FireHound
Google+
FireHound-Devices
***** Ground Zero ROMs *****
GZR Google+
Tesla
TeslaROM-Devices
Tipsy
TipsyOs-Devices
Validus
ValidusOs-Devices
***** Ground Zero ROMs *****
Heritage
Hexagon
Google+
Hexa-Project
Lineage
Google+
Liquid Dark
Google+
LiquidDark-Devices
Mokee
Google+
NetHunter
Newel
aliceteam
Next
Nuclear
Google+
Oct
Google+
Team-OctOS-Devices
Omni
Google+
Orion
Google+
TeamOrion-Devices
PNougat-CAF
Reaper
RR
Google+
ResurrectionRemix-Devices
Scarex
Slim
Google+
Slim-Mimorin
StonedOSP
SudaMod
Google+
SudaMod-devices
Suicide-Squad-OMS
UB
Google+
UltraDevs
UOS
Google+
Vanir
Google+
Vertex
VertexOS-devices
Viper
XenonHD
Google+
XOSP
Google+
XOSP-devices
XPe
Google+
CAF ROM
AOSIP <= CAF
Google+
AOSiP-devices
AOSParadox
Google+
Athene <= CAF
BORG <= CAF
Citrus-CAF <= CAF
Cirtus-CAF n-8916 <= CAF
Cirtus-CAF n-8952 <= CAF
Cirtus-CAF n-8996 <= CAF
Google+
Exodus <= CAF
Google+
Halogen <= CAF
Google+
Infinitive <= CAF
Google+
InfinitiveOS-Devices
KodeParadise <= CAF
Omega <= CAF
Paranoid <= CAF
Google+
Phenex <= CAF
Phenex OS
XesKi <= CAF
Zephyr <= CAF
Google+
ZephyrOS-Devices
Note : ROMs that are not to be shared when you build them
AOSP
Flash
SkyDragon
AOSP+CAF
Broken
Google+
DU
Google+
Device specific
8890dev
AOSPlusone
AscendToDev
AquaXP
DakTak
Elixium
Exynos5420
FullGreen
FunRom
HUAWEI-MSM8916
J5-Nougat
JDC
LG_Volt-Lineage
Kenzo-CAF
Lineage-onyx
MSM8930-Samsung
Morph
MyAOSP
N3xtBit
nAOSP
Naosp
Nexus4ever
Google+
Omni-onyx
OnePlusOSS <= CAF
PixN
PURE AOSP
Pure-Hammerhead
S4
Slimbit
SM-G361F
SonyAosp
SultanXDA
TeamButter
Tesla-Unleashed
SonyM4
WeedZ
ROMs that has yet to be released
Nameless
Google+ <= Source
Vanilla-Coding <= Source
ROMs that may or may not be updated
aosp-op2
AOSP-RRO
Beltz
Dominion
Exotic
F-ASOP
Mainly
Maple
Google+
Marsh
Google+
n2o
Noise
Purity
Google+
Quantum Droid
Scorpion
SOKP
Google+
SOS
Turbo
Google+
Xylem
Theming/ App
Substratum
Custom ToolChains
UberTC
Linaro => More info here
SaberMod​
If you found any ROMs not listed here, mention my name in your reply with the link & i'll update OP, Thanks... :good:
How & Where to look for Newly Develop/ Latest Android Custom ROMs
Open any browser => github.com => Type manifest => Press ENTER
Select => Recently updated
XDA:DevDB Information
List of Active Custom ROMs, ROM for all devices (see above for details)
Contributors
yuweng
ROM OS Version: 7.x Nougat
Based On: AOSP, AOSP+CAF, CAF
Version Information
Status: Testing
Created 2017-01-27
Last Updated 2017-02-13

FAQ
What is AOSP ROM ? What is CAF ROM ? What is HAL ? There are only two types of Android sources, AOSP ROMs uses google source, Eg. here while CAF ROMs uses codeaurora, Eg. here. Do take note that CAF also have different branches, for Eg. AOSPA CAF branch uses 89xx, it won't boot on my MSM8916 or wouldn't even build.
View attachment 4019415
Source
The only custom CAF ROMs that boots on my MSM8916 uses this
View attachment 4019440
Source
Q : How do i know which custom ROMs will build & boot on my Android device ?
A : As RD Santhosh M once told me, you'll never know until you build them & flash it to your device. Generally, from the custom ROM manifest.xml, you'll see whether it is supported. Eg. My Android device uses MSM8916 & if a particular custom ROMs doesn't have that, even though it build but it won't boot. Best is to directly ask the ROM Developer via pm, most of them are active here on XDA or post at their Google+
Q : Which custom ROM shall i build ?
A : Each custom ROM is unique in their own way. i don't plan to review each of them, you'll have to build them & flash it to your device to know its feature. From experience at performance & battery life, 50% is from the kernel & balance is from the ROM, thats why some custom ROMs feels snappier than the other. While some offers custom toolchain too. More info then refer to here
Q : i wanna learn how to build custom ROMs, where do i start ?
A : There are tons of guides here on XDA & elsewhere. Personally, i use BBQLinux, more info then refer to my thread here
Q : i have a slow PC & slow connections
A : Try out Google Cloud for free, more info then refer to nitin.chobhe thread
Misc Tips
Syncing ROM Source
Code:
mkdir -p ~/AOSP/LineageOS
cd ~/AOSP/LineageOS
repo init -u git://github.com/LineageOS/android.git -b cm-14.1
repo sync -fcj68 --force-sync
Source Eg. For my kiwi. Each custom ROMs may be different, refer to their manifest for further build info
More info on syncing source here & info on fixing sync corruption here <= Misc Tips
Code:
cd ~/AOSP/LineageOS
prebuilts/misc/linux-x86/ccache/ccache -M 100G
export USE_CCACHE=1
export LC_ALL=C
export JAVA_HOME=/usr/lib/jvm/default
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
source build/envsetup.sh
brunch kiwi 2>&1 | tee ~/AOSP/LineageOS/compile.log
My BBQLinux build-script
Fixing build error
From experience after building about forty custom ROMs, most of the time is either the ROM source or device tree. On some custom ROMs, you may need to replace certain projects in order for it to work, more info on using local_manifest.xml. Eg. below
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<[COLOR="Blue"]remove[/COLOR]-project name="android_hardware_qcom_audio" />
<project path="hardware/qcom/audio-caf/msm8916" name="LineageOS/android_hardware_qcom_audio" remote="github" revision="cm-14.1-caf-8916" />
<[COLOR="blue"]remove[/COLOR]-project name="android_hardware_qcom_display" />
<project path="hardware/qcom/display-caf/msm8916" name="LineageOS/android_hardware_qcom_display" remote="github" revision="cm-14.1-caf-8916" />
<[COLOR="blue"]remove[/COLOR]-project name="android_hardware_qcom_media" />
<project path="hardware/qcom/media-caf/msm8916" name="LineageOS/android_hardware_qcom_media" remote="github" revision="cm-14.1-caf-8916" />
</manifest>
If a particular ROM is based on Lineage & Lineage developers there has added a new feature or fix some codes & this particular custom ROM developer haven't updated it yet then most of the time it will cause build error. So either wait for a few days until those changes has been merged then only build again.
Or refer to their github & gerrit to see what are the changes that might causes the build error. Then you can either revert those changes so that the ROM can be build. An Eg. here & the build error hints something about power.h then you can revert the change as below
Code:
cd ~/CustomROM/hardware/libhardware
git revert --no-edit [COLOR="Blue"]f29cb1fd95ee6e5b371d2d6a85c1aeac708b19a6[/COLOR]
View attachment 4034126
Every custom ROMs is unique so refer to their device tree for reference. Eg. Custom MSM8916 flags & dependencies on Omnirom for my kiwi
Another common build error & fixes
Code:
ninja: error: '/home/yuweng/5x/AOSP/Omni/out/target/product/kiwi/obj/SHARED_LIBRARIES/[COLOR="Blue"]libqmiservices[/COLOR]_intermediates/export_includes', needed by '/home/yuweng/5x/AOSP/Omni/out/target/product/kiwi/obj/EXECUTABLES/[COLOR="blue"]wcnss_service[/COLOR]_intermediates/import_includes', missing and no known rule to make it
make: *** [build/core/ninja.mk:149: ninja_wrapper] Error 1
Code:
[COLOR="Red"][B]#[/B][/COLOR] TARGET_USES_QCOM_WCNSS_QMI := true
OR
Code:
TARGET_PROVIDES_WCNSS_QMI := true
Either remark it or just delete that whole flag or add an additional new flag above will fix the build error on omnirom.
While some custom ROMs require additional flags for certain feature to work, always refer to their github device tree for reference. For Eg. on my kiwi, on DU, sliding the BT switch won't work, it will switch on but it won't detect nearby bluetooth devices & in a short while, it will auto switch off. All needed was an additional flag
Code:
BLUETOOTH_HCI_USE_MCT := true
Source
If you are still not able to solve those build errors or a certain function doesn't work on your device then try asking for help at their google+. Some provide realtime on IRC Freenode too. Eg. TWRP & omnirom, always check out the timezone first. Eg. You should be able to catch hold of Dees_Troy TWRP Lead Developer( very nice & approachable developer ) at 9am to 5pm & there won't be anyone around at 3am in the morning obviously !
Ethics
Gives Credit Where Credit is Due
Over the years, i've seen alot of fights & arguments here on XDA & elsewhere regarding taking the work of others. Most developers already shared/ public their work to the world, all you have to do is to show your gratitude by mentioning their name in your work when you share them, thats all they want, to be acknowledged & recognized for their work ! When you don't meaning you are stealing from them, end users wouldn't have known & they will think that you do all the work all by yourself. Gives Credit Where Credit is Due
Detail info then refer to here & here
Official Support
Most ROM Developers doesn't support devices that they don't own. If you do want to maintain a particular ROM for your device then talk to them & see how to work things out !
Example of a Basic requirement of a Device Maintainer
Code:
As a Maintainer you are expected to:
1. Be able to build for your device and provide users with regular builds.
a. You must own the device you wish to maintain. Blind builds and ports are NOT allowed!
b. Exceptions may be made (family/friend's devices with direct access and variants of devices etc) and are to be requested BEFORE submitting your patchset to Gerrit!
c. A Co-Maintainer may be elected for your device by you if wanted. He/she must follow the same rules as you and submit their own commit to Gerrit.
d. Maintainers will have merge permissions to their device and kernel specific repositories and are expected to keep their device in working order. Whether this done by; doing basic upkeep with upstream changes for fixes and updates, starting for an upstream base and doing original work (pushing upstream when you can), or a mixture of both. The main concern is following proper procedure and keeping your device(s) functioning. Additionally, common and shared repositories will be worked on together by the Maintainers; they will still be controlled and merged by the PAC Team. In this respect, teamwork among Maintainers with common devices will not only be encouraged, in some cases, it may be necessary.
2. Threads are to be compared to our templates regularly for updated topic and content changes.
a. Templates are to be used exactly as they are with NO alterations aside the foreseen places like Title, Installation, Updating, Not working, Other info, and additional credits below the current list if any, unless permitted otherwise.
b. Custom additions (custom builds, kernels, patches, software packages etc) are tolerated and may be distributed from the PAC-ROM thread's Downloads section of the first post.
c. Information about any custom additions is to be posted in the 2nd post of both threads.
d. Custom additions are your responsibility, and are not supported by the PAC-ROM Dev Team.
e. The PAC-ROM Dev Team may change, remove, disable, or tell you to delete ANY custom additions or infringing content for any reason, at any time, in our sole discretion.
f. If unsure, ask the reviewer you contacted.
3. Maintainers MUST create an account on our [JIRA] (http://jira.pac-rom.com/). Users will be able to submit issues and find contact information on the Maintainer for their device such as PAC/XDA Threads. Maintainers will be required to upkeep their JIRA support.
4. To maintain proper support and device usability across the PAC-ROM community, if a device is: abandoned, unsupported, unkempt, or devices where the Maintainer has; sold, broken, lost, no longer has and will not be replacing [within the grace period of 4 weeks], or no longer cares to maintain the device for PAC, then the device will be removed. Remember, if the device is removed and it gets further support, from someone else, then it can be resubmitted later as new.
a. Be fair to the users, if you can not maintain the device anymore for whatever reason, please try to find a follow up maintainer, have them submit their take over changes to Gerrit, and have your threads transferred if possible. If this is not possible, please remove the device and submit your cleanup to Gerrit.
5. Prereleases
* Only Maintainers may publish Alpha/Prerelease builds.
* Alpha/Prerelease build version tag should be set to UNOFFICIAL
* Users/Unofficial device Maintainers may NOT release/post our Prerelease builds.
* Permission for Maintainers may be revoked anytime for a Maintainer or global for all Maintainers.
* Alpha/Prerelease builds are to be uploaded to BB/codename/Unofficial.
* Alpha/Prerelease builds are NOT supported by PAC Dev Team or Maintainers.
* Maintainers are to check their XDA device category for threads posting Prereleases/Unofficial builds and have them removed/closed.
* Maintainers can use this opportunity to test and bring up their devices, users can play with cutting edge test builds and return feedback for the Maintainer at their own risk.
* Community/Forum posts about ETA's, Prerelease device compatibility, broken or missing features, or any other acquisition of Prerelease information and support will be deleted/directed toward the Maintainer.
6. As a Maintainer, you will be able to:
* Get official, clean built, and automated nightly/weekly builds from Jenkins.
* Use our file hosting for builds.
* Use our OTA for pushing your own builds.
* Join in on our discussions, get support from the Dev Team and other Maintainers.
* There is no cake, it's a lie!
* Devices that get less than 35 downloads a week are considered low activity and will be moved to weekly.xml.
7. This page is subject to change without notice! Check back regularly here for changes.[/hide]
Original Source
Build Server
Recently a good friend of mine shoxxy from Germany is so kind for letting me try out his build server... :good:
View attachment 4071930
repo sync completed in about 35 minutes only instead of 8 to 10 hours on my home 10MB broadband !
View attachment 4071931
speedtest 200MB/s while my home typically only 8 to 9MB/s !
How this works is that you are actually still using your PC to connect to the build server via terminal ssh, Eg. ssh [email protected] & you'll be prompt for password. shoxxy has already setup the OS so i only need to sync the source & start building ! There is absolutely no GUI only command line so you need to be familiar with nano to edit your device tree.
View attachment 4071955
Copy/ paste from your PC to build server terminal works. Some of the common nano shortcut key is ctrl + k = cut & ctrl + u = paste or you can also use your mouse to highlight that particular line then ctrl + k to cut it & copy whatever you need to replace from your PC to the terminal & right-click mouse to paste it. More info on nano keyboard commands
View attachment 4071985
Build completed successfully. You can also use gdrive to upload your build to google drive... :good:
View attachment 4071988
Use nano to check for build error. nano shortcut key to end of file is Ctrl + w + v
View attachment 4071992
Very important to use screen before you start building or your build will stop when connection is lost !
{
"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"
}
You can even connect directly from your Android device too !

Always wanted something like this . Glad to see you again @yuweng.

How are you my friend, indeed it has been quite awhile since our last chat... :highfive: Back in our early MTK days, absolute nothing can build from source, we have to resort to ROM porting to get the so called custom ROM on our device... Now i can see M.A.D Team are making some progress but not all MTK devices are supported. Mid of last year, i have made the decision to move to Qualcomm SoC, we have close to 50 custom ROMs build from source, Thanks to our device tree bring-up team, crpalmer & BadDaemon, we have 3 generations of Android on it, cm-12.1 (LP), cm-13.1 (MM), cm-14.1 (N) & now we have Official Support too... And Yes, with the exact same device tree, i alone was able to built about 40 of them...
The first custom ROMs database started back in 2013, very detail list but no longer updated, i don't plan to go so deep into it, just links to their source & Google+, you'll have to sync the source, build them, flash them to your device to know what those custom ROMs has to offer, all you need is your device tree, kernel source & vendor tree & last but not least, of course, a MSM SoC not MTK... :laugh:

yuweng said:
How are you my friend, indeed it has been quite awhile since our last chat... :highfive: Back in our early MTK days, absolute nothing can build from source, we have to resort to ROM porting to get the so called custom ROM on our device... Now i can see M.A.D Team are making some progress but not all MTK devices are supported. Mid of last year, i have made the decision to move to Qualcomm SoC, we have close to 50 custom ROMs build from source, Thanks to our device tree bring-up team, crpalmer & BadDaemon, we have 3 generations of Android on it, cm-12.1 (LP), cm-13.1 (MM), cm-14.1 (N) & now we have Official Support too... And Yes, with the exact same device tree, i alone was able to built about 40 of them...
The first custom ROMs database started back in 2013, very detail list but no longer updated, i don't plan to go so deep into it, just links to their source & Google+, you'll have to sync the source, build them, flash them to your device to know what those custom ROMs has to offer, all you need is your device tree, kernel source & vendor tree & last but not least, of course, a MSM SoC not MTK... :laugh:
Click to expand...
Click to collapse
Hehe yeah, the good old MTK days. I still have the same device that you helped me with back in the day and I've done quite some work on my own too, built all the available recoveries, custom kernels and tried two ROMs (CM11 and CM12.1). They don't boot (libs issue) but haha it was a nice experience. I know you switched from the MTK scene for a while now and are working with the Honor device :silly:. M.A.D team is doing something great because a lot of other developers are coming out and getting other devices supported too!!. Sadly it's only the newer generation chips (MT67XX) while I still have the old MT65XX :laugh:. If I ever get a Qualcomm device, I'll be sure to continue following this thread .

Can i know which ROMS would get built for exynos devices?

rohit9757 said:
Can i know which ROMS would get built for exynos devices?
Click to expand...
Click to collapse
Not the purpose of this thread and the developer of that device is who you should be asking that question.

kirito9 said:
Not the purpose of this thread and the developer of that device is who you should be asking that question.
Click to expand...
Click to collapse
Apologies read it wrong and took your post in a wrong way.
Deleted.

rohit9757 said:
I agree I am a noob. Started learning stuff very recently. The device which i own is not an easy device for ROM building but am trying. Saw this wonderful post and thought would get help. But thats ok mate you can talk all about your golden days here[OFF-TOPIC] and I will take help from somebody else as xda is quite big.
Peace.
@OP:-Wonderful thread thank you.
Click to expand...
Click to collapse
I never said anything about not offering help but alright xD.
You do have a point about the OT part tho, a question like that isn't quite as OT as my post.

Theoretically all, as all of them are actually a fork of Android however, having said that, RD codeworkx has ceased development on it since 5 years ago !
Source
rohit9757 said:
Can i know which ROMS would get built for exynos devices?
Click to expand...
Click to collapse

[Unoffical] Xenon-Hd Android 8 Build Out

What is XenonHD?
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 15.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
MAIN FEATURES :
XenonHD Changelog
NovaLauncher, Adaway, Kernel Adiutor, SuperSU
Root, adb, dev options, advanced reboot & installing apks enabled by default
Pixel UI, Pixel Navbar + Animation, Wallpaper
Material sounds & icons
Day/Night theme
Network indicator & battery bar in status bar
Live Volume Steps
DT2S on lockscreen
Custom Quick Settings Tiles
Removed unnecessary things
Under the hood improvements and optimizations
...and more on the way!
BUG :
Volte
HOW TO FLASH
Install latest TWRP recovery on your device.
Make a backup of your current ROM.
Wipe system, data, cache and dalvik.
Flash ROM.zip and Googleapps.zip.
Reboot system and setup!
Download :https://drive.google.com/file/d/0B72tZGCxrlDicjJHWG0wV3VLdWM/view?usp=sharing
CREDITS
Team Horizon and Xenon HD Team for the rom source
@[email protected]
XDA:DevDB Information
[Unoffical] Xenon-Hd Android 8 Build, ROM for the Xiaomi Redmi Note 4
Contributors
ZH_Alone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Beta
Current Beta Version: V 1.0
Beta Release Date: 2017-10-07
Created 2017-10-07
Last Updated 2017-10-07

Thanks for your work. Definitely going to test it now. Just one thing : you forgot to add a space after the ":" so the link is not clickable

Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway

dadi11 said:
Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway
Click to expand...
Click to collapse

thanks for sharing but please remove it. if anyone is to build oreo based xenon hd, it' s @dadi11 not you or anyone else. He is the official maintainer and developer and no one builds it better than he does. So, keep it for yourself and delete your post please.

Wait so bug is only Volte??
How about goodix fp???

jack_hunter97 said:
Wait so bug is only Volte??
How about goodix fp???
Click to expand...
Click to collapse
Please read #3 : https://forum.xda-developers.com/showpost.php?p=74067496&postcount=3

No link?

Thread closed
First NO placeholders are allowed. All ROM threads must have a download link at time of posting
Second always seek permission to build and post someone else's work as per rule 12 the developer can request take down:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!

[ROM][10][violet] CarbonROM [cr-8.0][UNOFFICIAL][Enforcing]

{
"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.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Be respectful to each other and don't ask for ETAs, it's considered as being rude!
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! These builds are experimental and can contain Bugs (as listed above). Make sure to do backups.
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) Read our FAQ, which can be found on our website. Carbon FAQ
3) 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.
4) Join our Discord server! 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.
5) Please keep bugreports to this thread or Discord. Do NOT create a Jira ticket. This is still in early development so we don't accept any bugreports yet.
Download ROM here for your device!
Violet
Code:
[b]-We recommend Ofox Recovery
1. Wipe data, system, dalvik, caches.
2. Flash Firmware (Mostly latest)
3. Flash the ROM file. (Gaaps Not Included)
4. FCRYPT zip (optional)
5. Reboot .
6. Enjoy
[First boot will take a few minutes! Have patience]
Clean Flash is always recommended![/b]
If you want any bug to be fixed please write here on xda in detail. Give Logcats, mention your device name, mention if any mods and kernels, if used and please be specific about it. By helping us, you are helping yourself too.
Visit our Website,. Subscribe to our Telegram Channel. Also join our Telegram Group Chat!
Join our Violet Group
Telegram Group Chat!.
Checkout this ROM!
YOUR ATTACHMENTS COMES HERE FOR SCREENSHOTS
@Myself5
Big thanks to @Dyneteve & @merothh & @Venkatesh Siva & everyone else in the Community for helping me,supporting me & testing the ROM!​
Kernel Source: https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150
XDA:DevDB Information
CarbonROM, ROM for the Xiaomi Redmi Note 7 Pro
Contributors
Rainstalkker, Dyneteve, merothh, VenkieTheNub
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.9.3
Version Information
Status: Beta
Beta Release Date: 2019-12-15
Created 2019-12-02
Last Updated 2019-12-14

Reserved

#Changelog for CARBON-CR-8.0-PAX-UNOFFICIAL-violet-20191129-1709.zip
- Enforcing Build
- Upreved to gralloc 3.0 ( Faster GCAM processing overlay but it's not limited only to gcam )
- Fixed mic in voIP calls for some users
- Various tweaks and fixes

Thanks for the update

New Update!!!!!!
#Changelog
-Merged R18(December Security Patch).
-Added Themepicker.
-Fixed Whatsapp & Youtube lags & crashes.
-Fixed few missing icons.
-More Under The Hood Fixes & Source Side changes.

have swipe to screenshot?

I have tried CARBON-CR-8.0-PAX-UNOFFICIAL-violet-20200117-0530 - got Error 7 in TWRP.
CARBON-CR-8.0-PAX-UNOFFICIAL-violet-20200103-0729 installed without errors.

[ROM][OFFICIAL][10] BlissRoms v12.10 [jasmine_sprout/Mi A2]

{
"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"
}
team bliss is pleased to present to you
bliss rom based on Android 10
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
AIO Thread
Bliss Source
https://github.com/BlissRoms
BlissRoms Device Sources
https://github.com/xiaomi-sdm660
Bliss Device Downloads
Bliss Download
As of Now NikGapps is Suggested for the Mi A2 and is found below
NikGapps
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom. Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Make sure you are rooted
Make sure you have a custom recovery installed(TWRP is the preferred recovery and preinstalled in this rom)
Download the latest Bliss Rom & the latest GApps package
Boot into recovery
Backup your current ROM
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash Bliss Rom
Switch Slot and Reboot recovery
Flash Google Apps package
Flash Root of your choice(Unless OP states otherwise)
First boot may take up to 10 minutes. This is due to Gapps and root optimization.
[*] None
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
After downloading the Catlog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving.
As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the forum with a brief description of the error.
@Jackeagle @electrikjesus @rwaterspf1 @Makaveli_da_dev @ElfinJNoty @BitOBSessiOn @customworx
@nilac @sixohtew @aclegg2011 @Roger.T @T.M.Wrath @kanttii @rev3nt3ch @techfreak243 @SuperDroidBond @USA_RedDragon @bcrichster
@deadmanxXD @krittin98 @BlackScorpion @techexhibeo @droidbot @siphonay @pacer456 @nitin1438 @theGeekyLad @kunalshah912 @regalstreak @lordarcadius
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Team Bliss aims to develop and maintain various OS & software projects for educational and the Android community building purposes. Team membership consist of and provides:
training, development opportunities, design opportunities, build servers, download servers, design & development software,as well as professionals and mentors in all fields revolving around Android development.​If someone wants to donate, please do so via this PayPal link:
PayPal Link
WE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
We receive a small donation each time you make a purchase with “Amazon Smile”:
https://smile.amazon.com/ch/82-3580195​
Notice
The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.
We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
Please do not ask for ETA's
We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts
Team Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.​
Website
https://blissroms.com
Official Platform Links
https://www.facebook.comBlissFamilyOfROMs
https://twitter.com/Bliss_ROMs
https://www.instagram.com/blissroms
Thank you for using Bliss! And as always: #StayBlissful​
XDA:DevDB Information
[ROM][OFFICIAL] BlissRoms [jasmine_sprout/Mi A2], ROM for the Xiaomi Mi A2
Contributors
rcstar6696
Source Code: https://github.com/xiaomi-sdm660
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Bliss
Version Information
Status: Beta
Created 2020-01-21
Last Updated 2020-07-25

Reserved

Reserved

Welcome Bliss Rom. Nice to test you

So good to see Bliss for our device. Nice selection Max. :highfive:

???

We need telegram group. . .

BlissRom V12.2 Jasmine_Sprout (Mi A2)
?*? by @rcstar6696
? ROM | OFFICIAL | BETA
Version: 10.0 Q
? Build date: 28.01.2020
Link:
- https://sourceforge.net/projects/rc...jasmine_sprout-OFFICIAL-20200128.zip/download
CHANGELOG:
- Intial Release
- https://sourceforge.net/projects/bl...jasmine_sprout-OFFICIAL-20200128.zip/download
TWRP Included
No Gapps preinstalled
? Known Bugs:
- None
? XDA:
https://forum.xda-developers.com/mi-a2/development/rom-blissroms-v12-2-t4038259

rcstar6696 said:
BlissRom V12.2 Jasmine_Sprout (Mi A2)
* by @rcstar6696
ROM | OFFICIAL | BETA
Version: 10.0 Q
Build date: 28.01.2020
Link:
- https://sourceforge.net/projects/rc...jasmine_sprout-OFFICIAL-20200128.zip/download
CHANGELOG:
- Intial Release
- https://sourceforge.net/projects/bl...jasmine_sprout-OFFICIAL-20200128.zip/download
TWRP Included
No Gapps preinstalled
Known Bugs:
- None
XDA:
https://forum.xda-developers.com/mi-a2/development/rom-blissroms-v12-2-t4038259
Click to expand...
Click to collapse
Do you have a telegram group or channel?

paul222008 said:
Do you have a telegram group or channel?
Click to expand...
Click to collapse
He is more active here https://t.me/A26XOfficial so you will get faster support.

Hello very good day, I have been able to try the ROM for a couple of days and I loved it, but I have not been able to keep it using the following that I could find:
1) The battery consumption is higher than other rom.
2) Upon receiving a call, the flashlight turns on and off without stopping until you reset the phone.
In general it is just that, everything else I would say is perfect.
Thank you very much for your great work and dedication with this rom.

BlissRom V12.3 Jasmine_Sprout (Mi A2)
?*? by @rcstar6696
? ROM | OFFICIAL | BETA
Version: 10.0 Q
? Build date: 11.02.2020
Link:
- https://sourceforge.net/projects/bl...jasmine_sprout-OFFICIAL-20200211.zip/download
CHANGELOG:
- https://sourceforge.net/projects/bl...jasmine_sprout-OFFICIAL-20200211.txt/download
TWRP Included
No Gapps preinstalled
? Known Bugs:
- None

rcstar6696 said:
BlissRom V12.3 Jasmine_Sprout (Mi A2)
* by @rcstar6696
ROM | OFFICIAL | BETA
Version: 10.0 Q
Build
Click to expand...
Click to collapse
The updater in the rom is giving an error and not downloading the rom! do i have to dirty flash the new update?

jugaaru said:
The updater in the rom is giving an error and not downloading the rom! do i have to dirty flash the new update?
Click to expand...
Click to collapse
Yes ota will work from next build only

Hi Dev, I'm trying your rom and I like so much all in this, but I think the animations are very fast, making the system a little strange.
Congratulations on the work done at rom, everything works perfectly. I will wait anxiously for updates.
I would also like to know if these icons are in the right position? There are strange ways over there, I don’t even know if it’s you who define this, I just wanted to know

ronaldornd said:
Hi Dev, I'm trying your rom and I like so much all in this, but I think the animations are very fast, making the system a little strange.
Congratulations on the work done at rom, everything works perfectly. I will wait anxiously for updates.
I would also like to know if these icons are in the right position? There are strange ways over there, I don’t even know if it’s you who define this, I just wanted to know
Click to expand...
Click to collapse
Try setting animation scale from 0.25x to 0.6x under developer settings, reboot the device and see if that improves!
EDIT: You can also set animation scale to 1.0x which is usually a default value in most of available custom rom afaik..
And as far as icon position / order is concerned, that is source thing and you will find this order almost identical to each and every other custom rom available out there that offers their own sets of customization!

Thanks for explaining, I had already changed the values ​​of the animations, I only questioned it because I thought it was above normal.

I'm having trouble trying to rename the sim card

ronaldornd said:
I'm having trouble trying to rename the sim card
Click to expand...
Click to collapse
It seems a visual glitch...ig OP is aware of it and probably it will be fix in next update.

This ROM is great! But, the sound from video recording heard very quiet. If you can fix it, it'll be perfect.

[CLOSED][ROM][13.0][Crystal] Android Open Source Project [Tiramisu] [18/08/2022]

{
"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"
}
Android Open Source Project for Nokia 7.1
About AOSP
Android is an open source operating system for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android OS, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
As an open source project, Android's goal is to avoid any central point of failure in which one industry player can restrict or control the innovations of any other player. To that end, Android is a full, production-quality operating system for consumer products, complete with customizable source code that can be ported to nearly any device and public documentation that is available to everyone.
Just as you can contribute code to AOSP, you can also contribute to AOSP documentation—and we want your input! Android's flexibility and ever-changing codebase means this site needs your feedback to keep content fresh, accurate, and relevant to Android implementors. We encourage you to check the changelog for details on recent AOSP updates and to report bugs or offer suggestions using the Site Feedback at the bottom of every page.
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint
FM radio
Sound
vibration
Known issues ?
You tell me
Installation process
Note - I don't recommend to flash any other custom kernels on this rom, just to avoid issues .
Click Here for Installation process
Credits
* AOSP for source
* Nokia for kernel source & vendor
* Moderators (For Giving Freedom To Post Threads)​​
Download Rom {Mod edit: Link removed}
Android OS version: 13.0
Security patch level: 2022-08
Build author: Raghu varma
Kernel Source code: android_kernel_nokia_sdm660
Source code: https://android.googlesource.com

Changelog Thu Aug 18 17:39:49 UTC 2022
============================
• Based on android-13.0.0_r2
• Improved system stability
• User interface enhancements
• Google security patch 2022-08

Gapps included in ROM or what ?

Hi Raghu Verma Ji, Gapps is available for android 13 or what. Because other gapps is creating issue.

System Navigation... switch app option not working

First of all, thank you for your work.
Everything works fine except the bluetooth
I can't connect a bluetooth headset or speaker.
And why did you write that FM works if it is not available hardware?
The rom also doesn't have a built in sms app.

KonstantIMP said:
First of all, thank you for your work.
Everything works fine except the bluetooth
I can't connect a bluetooth headset or speaker.
And why did you write that FM works if it is not available hardware?
The rom also doesn't have a built in sms app.
Click to expand...
Click to collapse
which gapps use, can you share me the link. because in my device incoming call screen not showing....

arun7129 said:
which gapps use, can you share me the link. because in my device incoming call screen not showing....
Click to expand...
Click to collapse
Use LiteGapps. Don't forget to swap slots when flashing gapps in recovery.
https://sourceforge.net/projects/litegapps/files/litegapps/arm64/33/lite/v2.6/%5BRECOVERY%5DLiteGapps_arm64_13.0_v2.6_official.zip/download

Raghu varma said:
Android Open Source Project for Nokia 7.1
About AOSP
Android is an open source operating system for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android OS, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
As an open source project, Android's goal is to avoid any central point of failure in which one industry player can restrict or control the innovations of any other player. To that end, Android is a full, production-quality operating system for consumer products, complete with customizable source code that can be ported to nearly any device and public documentation that is available to everyone.
Just as you can contribute code to AOSP, you can also contribute to AOSP documentation—and we want your input! Android's flexibility and ever-changing codebase means this site needs your feedback to keep content fresh, accurate, and relevant to Android implementors. We encourage you to check the changelog for details on recent AOSP updates and to report bugs or offer suggestions using the Site Feedback at the bottom of every page.
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint
FM radio
Sound
vibration
Known issues ?
You tell me
Installation process
Note - I don't recommend to flash any other custom kernels on this rom, just to avoid issues .
Click Here for Installation process
Credits
* AOSP for source
* Nokia for kernel source & vendor
* Moderators (For Giving Freedom To Post Threads)​​
Download Rom
Android OS version: 13.0
Security patch level: 2022-08
Build author: Raghu varma
Kernel Source code: android_kernel_nokia_sdm660
Source code: https://android.googlesource.com
Click to expand...
Click to collapse
Hi raghu verma Ji, I am using Nikgapps 13 full.. Incoming Call and Sms (Incoming & Outgoing not working)... Can you help me how to fix it.. Please..

Hansie00 said:
Use LiteGapps. Don't forget to swap slots when flashing gapps in recovery.
https://sourceforge.net/projects/litegapps/files/litegapps/arm64/33/lite/v2.6/%5BRECOVERY%5DLiteGapps_arm64_13.0_v2.6_official.zip/download
Click to expand...
Click to collapse
In your device Incoming Call & Sms (In & Out) working or not....

Hello Users, Don't download this rom.. this is totally buggy, Raghu Verma not fixing this issue here... {Mod edited and screenshot deleted}

arun7129 said:
Hello Users, Don't download this rom.. this is totally buggy, Raghu Verma not fixing this issue here... {Mod edited and screenshot deleted}
Click to expand...
Click to collapse
Control your sugar and thank you for your feedback in a positive way on day 1 and rubbish feedback on day 7. Anyway before you write reviews in your style i request you to first note down one thing "snapdragon 636 doesn't even fit for Android 11". But i managed for every Android version to bring up on day 2 after aosp drop by Google. So for me pushing latest Android versions is my target no matter if it has lag or drag or trash , at the end i should boot latest Android version and upload to public as first. Rest i repeat we don't even consider bugs or feedbacks.
On top of it we are not employees to work for public to make them satisfy by taking positive feedbacks or negative feedbacks because at the end we don't get anything except time waste by reading comments first but still we do and make them control their sugar. Moreover to run development we need financial support from community like donations. When you are unfit to donate then don't use my work. We don't run any useless business here. I repeat this is my work and my wish , if you feel you can then use if you feel it is useless then move on with other works. Or do by your own.
Note - my private project is not affiliated to any place including XDA. so no point of pushing unauthorised screenshot here. At the end this thread is actually belongs to aosp project and downloadable zip already linked here. So you better use that or move on with some other work.
Thank you!!

From now i repeat i don't even fix single bug because of this useless guy who demanded me to work as employee.
arun7129 said:
Hello Users, Don't download this rom.. this is totally buggy, Raghu Verma not fixing this issue here... {Mod edited and screenshot deleted}
Click to expand...
Click to collapse

Thread provisionally closed due to investigation!
Regards
Oswald Boelcke
Senior Moderator

arun7129 said:
Hello Users, Don't download this rom.. this is totally buggy, Raghu Verma not fixing this issue here... {Mod edited and screenshot deleted}
Click to expand...
Click to collapse
@arun7129 I've edited your post and removed the screenshot that was attached. Please don't bring drama from the outside, which we don't control, to XDA. However, I can understand your frustration because I see that you (like others) didn't receive support in this thread in regard to the problems you've mentioned.
Raghu varma said:
Moreover to run development we need financial support from community like donations. When you are unfit to donate then don't use my work. We don't run any useless business here.
Click to expand...
Click to collapse
@Raghu varma Thread remains closed, and I've removed the download link due to the missing support in the thread and because obviously means have been implemented that donations are required to be able to use your work bug free.
Regards
Oswald Boelcke