Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
Related
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)
READ CAREFULLY BEFORE YOU START! THE PATCH IS NOT A ROM/MOD/KERNEL
{
"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"
}
ABOUT
Rethink about Android customizations. Make it Yours!
The Light Patch ZIP File is a advanced multifunctional Utility, based on the famous AROMA for custom recovery Replacements like TWRP. It comes with everything that is needed to fully unleash the Potential of Your Device. Advanced Techniques from Google, Sony, HTC, Qualcomm and many Others combined into a single Package which fits for all Snapdragon Flagships running the very latest Android Versions. One to rule them All! Use a AOSP System as Base and get the Quality of a Stock Firmware, decide about the System Content, gain extra functionalities and enhance Your Device on a unsuspected Way. Everything is based on Years of intensive Research and deep going Changes on Android which You will find nowhere else. There are to many Features and Changes to list them all, but take a look at the Feature List and check out the insanely long Changelog which includes the Changes of Hundreds of Releases. Or just give it a try now, read the Instructions and Start off! AROMA will guide You thru the whole Patch Utility...
FEATURES
AROMA 3.0 POWERED BASE
OPTIMIZED MAGISK INCLUDED
OPTIMIZED SUPERSU INCLUDED
OPTIMIZED GAPPS INCLUDED
OPTIMIZED BUSYBOX INCLUDED
DEVICE TRANSFORMING OPTIONS
DPI/DEVICE UI TYPE OPTIONS
LIGHT EXCLUSIVE EXTRA OPTION
OPTIONAL DEBLOATING OPTIONS
UI SOUND OPTIONS
STORAGE WIPE OPTIONS
BOOTANIMATION OPTIONS
LIGHT AUDIO SYSTEM OPTION
4K AND HDR SUPPORT ENABLED
PARTITION TRIMMING ENABLED
USEFUL INIT.D SCRIPTS ENABLED
EXCLUSIVE PIXEL FEATURES
EXCLUSIVE OEM FEATURES
SETUP WIZARD ROTATION
LOCKSCREEN ROTATION
HOMESCREEN ROTATION
ENHANCED UI QUALITY
SMOOTHER UI RENDERING
ENHANCED APP RENDERING
ENHANCED GAMING HANDLING
ENHANCED SENSOR HANDLING
ENHANCED NETWORK HANDLING
ENHANCED ENERGY CONSUMPTION
ENHANCED STORAGE HANDLING
ENHANCED VOICE RECOGNITION
ADVANCED BLUETOOTH SERVICES
ADVANCED AUDIO HANDLING IN/OUTPUT
VARIOUS PERFORMANCE IMPROVEMENTS
ADVANCED VISUAL HANDLING IN/OUTPUT
EXTRA QUALCOMM SERVICES ENABLED
EXTRA STORAGE FEATURES ENABLED
ADVANCED ANDROID SERVICES ENABLED
CONFIGURATION OF NOT EXISTING SETTINGS
BATTERY DRAINING LOGS/SERVICES DISABLED
BATTERY CALIBRATION AFTER CHARGING
ZYGOTE HANDLING OPTIMIZED
VM HANDLING OPTIMIZED
DEX2OAT OPTIMIZED
SERIAL NUMBER UNDER SETTINGS
FORCED ENCRYPTION DISABLED
DM VERITY DISABLED
(YOU ARE FOLLOWING A DEVELOPMENT PROJECT HERE)
GOOGLE APPS
OPEN GAPPS SUPER LIGHT VERSION
CONTAINING
CHROME/WEBVIEW
DIALER/CONTACTS
SEARCH/ASSISTANT
PLAY STORE
STORAGEMANAGER
AND ALL NEEDED EXTRA SERVICES
WHICH ARE NOT VISIBLE IN THE LAUNCHER
ROOTING
SUPERSU BETA
SUPERSU STABLE
MAGISK BETA
MAGISK STABLE
(WITH DISABLED ENCRYPTION)
(OR CHOOSE NO ROOT FOR NO DECRYPTION)
REQUIREMENTS
TWRP RECOVERY REPLACEMENT
DECRYPTED DATA ACCESS
UNLOCKED BOOTLOADER
64BIT SNAPDRAGON SOC
AOSP BASED ROM/OS
(SNAPDRAGON 810+ AND 4GB+ RAM RECOMMENDED)
DOWNLOAD
INLIGHTNING WEBSITE / LIGHT
(READ THE FIRST THREE POSTS OF THIS THREAD BEFORE DOWNLOADING THE PATCH)
(SHARING DIRECT LINKS TO MY FILES OR MIRRORING MY WORK IS NOT DESIRED)
AND LAST BUT NOT LEAST
ENJOY THE PATCH AND FEEL FREE TO SHARE YOUR FEEDBACK/PATCH/DEVICE/OS CONFIG
STAY CONSTRUCTIVE, FRIENDLY AND RESPECT OTHERS
XDA:DevDB Information
LIGHT PATCH, Tool/Utility for all devices (see above for details)
Contributors
Miustone
Version Information
Status: Stable
Created 2017-11-23
Last Updated 2018-01-01
Q&A
Q1: HOW TO USE THE PATCH?
A1: TAKE A LOOK ON POST #3!
Q2: CAN I USE THE PATCH ON MY STOCK DEVICE FIRMWARE?
A1: DEPENDS ON THE OS. TEST BY YOURSELF AND GIVE FEEDBACK FOR OTHER USERS!
Q3: WHICH PATCH WIPE OPTION SHOULD I CHOOSE?
A1: IF YOU'VE CLEAN FLASHED A ROM/OS CAN YOU CHOOSE THE BASIC WIPE!
A2: IF YOU'VE NOT WIPED AND FLASHED A NEW ROM/OS BEFORE USE THE CLEAN OR FULL WIPE!
Q4: THE DISPLAY IS FROZEN WHILE PATCHING, WHAT TO DO?
A1: NO WORRIES, THE PATCH WILL INSTALL TWRP HAS JUST SOME PERFORMANCE ISSUES.
A2: JUST TAP THE RIGHT BOTTOM EDGE WHERE THE NEXT BUTTON IS AND PRESS IT A FEW TIMES.
A3: YOUR DEVICE SHOULD VIBRATE WHEN YOU HIT THE NEXT BUTTON. 4 VIBRATIONS AND YOU'RE DONE!
A4: DETACHING USB AND NOT CHARGING THE DEVICE DOES HELP TO AVOID THAT PROBLEM
Q5: SOME APPS ARE CLOSING OR NOT RECEIVING MESSAGES WHILE SCREEN OFF, WHY!?
A1: MAKE SURE YOU'VE CONFIGURED THE SMART BATTERY APP / PUT THEM TO NEVER SLEEP!
Q6: HOW TO SET UP SMART BATTERY?
A1: USE THE MORE SHORTCUTS APP AND START THE SMART BATTERY ACTIVITY!
A2: OR JUST WAIT FOR A NOTIFICATION FROM THE APP. IT COMES WHEN THE SCREEN IS OFF!
Q7: MY WALLPAPERS ARE GONE AFTER WAKING THE DEVICE UP, WHATS WRONG?
A1: MAKE SURE YOU'VE WHITELISTED GOOGLE BACKGROUNDS IN SMART BATTERY!
Q8: I DON'T FIND HELP ON THIS THREAD, WHAT TO DO?
A1: CHECK THE OTHER LIGHT PATCH THREADS. ONE PATCH FOR ALL DEVICES!
Q9: WHAT DOES THE PATCH DO?
A1: GO BACK TO THE FIRST POST AND START READING FROM THERE!
Questions left? Ask @Miustone
Instructions:
BOOT TO THE RECOVERY/TWRP
WIPE DATA, SYSTEM AND THE CACHES
FLASH A AOSP OS/ROM/FIRMWARE/KERNEL
GO TO THE REBOOT MENU AND SELECT RECOVERY
FLASH THE PATCH BEFORE BOOTING INTO THE SYSTEM
REBOOT TO THE SYSTEM NOW. THE FIRST START MAY TAKE SOME TIME
And that's it! If You don't want to flash a new ROM, just choose the Clean or Full Wipe within the Patch. But avoid to flash a new Patch over a old One. Each Version is a own Thing, not just an Update.
One More...
New Thread, new Luck... :angel:
The next Patch is coming soon. Including a whole new AROMA Layout and a lot more Features besides some new Services and Functions. Hope You can live with 1.6 for now...
BR
Finally .. looking forward for more updates in the future .. wish you a best luck and thanks for this amazing Masterpiece .
smarter than newton said:
Finally .. looking forward for more updates in the future .. wish you a best luck and thanks for this amazing Masterpiece .
Click to expand...
Click to collapse
Thank YOU for the nice Words!
Hope the Thread here goes well after not being allowed to Post on Device Specific Forums. Could look bad to have that many closed Threads in the Back. One more Reason for a new Thread...
BR
Hi OP
Welcome back. I have been waiting for your come back.
I am enjoying the Goodies of 1.6 with my OP5 installed after a clean flash of xXx No limits ROM which is stock based ROM.
Just a request. Please keep your G+ posting open for comments. I wanted to respond several times on your postings but none of them were accepting comments.
Thanks again.
Sent from my OnePlus 5 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:18 AM ----------
Hi
I can't find a download link in the loaded G+ page.
Sent from my OnePlus 5 using Tapatalk
Hi Miustone,
good to see you are back. And thanks for your Lights Patch! I'm running it on my Axon 7 (A2017 4/128), DarkRom, Magisk, for months now. It's stable, super smooth with Sot up to 5 hrs, which is great, as I'm using 2 Sim cards, BT and wifi all the time.
I can confirm that the (muted speaker) call bug is back with Light Patch 1.6. It was solved beginning with version 1.2. Toggling speaker on/off doesn't help, WhatsApp calls have muted speaker too, Skype is working ok. Strange!
Please let know, if you need some logs. I will wait and check LP 1.7 anyway.
Keep on with your great work!
May i install this patch to CM11 Gt-I8552? i want try it! looking good
smohanv said:
Hi OP
Welcome back. I have been waiting for your come back.
I am enjoying the Goodies of 1.6 with my OP5 installed after a clean flash of xXx No limits ROM which is stock based ROM.
Just a request. Please keep your G+ posting open for comments. I wanted to respond several times on your postings but none of them were accepting comments.
Thanks again.
Sent from my OnePlus 5 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:18 AM ----------
Hi
I can't find a download link in the loaded G+ page.
Sent from my OnePlus 5 using Tapatalk
Click to expand...
Click to collapse
I'm aware of the G+ Comments, but it's the best Way to keep You informed while keeping discussions here on XDA. See it as a Blog / Pushbullet Channel
And Hope You found the Download Link on My Website. Let Me know!
Choobilsky said:
Hi Miustone,
good to see you are back. And thanks for your Lights Patch! I'm running it on my Axon 7 (A2017 4/128), DarkRom, Magisk, for months now. It's stable, super smooth with Sot up to 5 hrs, which is great, as I'm using 2 Sim cards, BT and wifi all the time.
I can confirm that the (muted speaker) call bug is back with Light Patch 1.6. It was solved beginning with version 1.2. Toggling speaker on/off doesn't help, WhatsApp calls have muted speaker too, Skype is working ok. Strange!
Please let know, if you need some logs. I will wait and check LP 1.7 anyway.
Keep on with your great work!
Click to expand...
Click to collapse
I've read the comments on the Axon 7 AICP and Linage Threads. I told them that i can fix it without the Patch but they prefer ignorance and trolling over fixing lol The Problem will be fixed with the next Patch. Need to find the fix step by step again since i've added a lot of new Audio Stuff...
Some Clean Logs could also Help If You want to make some! Thanks for Your Feedback anways!
zharif93 said:
May i install this patch to CM11 Gt-I8552? i want try it! looking good
Click to expand...
Click to collapse
Only Android 7.1.2+ ARM64. Sorry My Friend :angel:
BR
BTW: Check out the G+ Light Patch Page Folks. Spoiler Alarm
Well i try it out =)
Using Redmi note 3 Pro with the new ABC Rom which looks like more aosp - Pixel version.
Alles gute Dir! und Danke für den Patch!
Google pixel xl 8.1 DP2
Miustone said:
READ CAREFULLY BEFORE YOU START! THE PATCH IS NOT A ROM/MOD/KERNEL
ABOUT
Rethink about Android customizations. Make it Yours!
The Light Patch ZIP File is a advanced multifunctional Utility, based on the famous AROMA for custom recovery Replacements like TWRP. It comes with everything that is needed to fully unleash the Potential of Your Device. Advanced Techniques from Google, Sony, HTC, Qualcomm and many Others combined into a single Package which fits for all Snapdragon Flagships running the very latest Android Versions. One to rule them All! Use a AOSP System as Base and get the Quality of a Stock Firmware, decide about the System Content, gain extra functionalities and enhance Your Device on a unsuspected Way. Everything is based on Years of intensive Research and deep going Changes on Android which You will find nowhere else. There are to many Features and Changes to list them all, but take a look at the Feature List and check out the insanely long Changelog which includes the Changes of Hundreds of Releases. Or just give it a try now, read the Instructions and Start off! AROMA will guide You thru the whole Patch Utility...
FEATURES
AROMA 3.0 POWERED BASE
OPTIMIZED MAGISK INCLUDED
OPTIMIZED SUPERSU INCLUDED
OPTIMIZED GAPPS INCLUDED
OPTIMIZED BUSYBOX INCLUDED
DEVICE TRANSFORMING OPTIONS
DPI/DEVICE UI TYPE OPTIONS
LIGHT EXCLUSIVE EXTRA OPTION
OPTIONAL DEBLOATING OPTIONS
UI SOUND OPTIONS
STORAGE WIPE OPTIONS
BOOTANIMATION OPTIONS
LIGHT AUDIO SYSTEM OPTION
4K AND HDR SUPPORT ENABLED
PARTITION TRIMMING ENABLED
USEFUL INIT.D SCRIPTS ENABLED
EXCLUSIVE PIXEL FEATURES
EXCLUSIVE OEM FEATURES
SETUP WIZARD ROTATION
LOCKSCREEN ROTATION
HOMESCREEN ROTATION
ENHANCED UI QUALITY
SMOOTHER UI RENDERING
ENHANCED APP RENDERING
ENHANCED GAMING HANDLING
ENHANCED SENSOR HANDLING
ENHANCED NETWORK HANDLING
ENHANCED ENERGY CONSUMPTION
ENHANCED STORAGE HANDLING
ENHANCED VOICE RECOGNITION
ADVANCED BLUETOOTH SERVICES
ADVANCED AUDIO HANDLING IN/OUTPUT
VARIOUS PERFORMANCE IMPROVEMENTS
ADVANCED VISUAL HANDLING IN/OUTPUT
EXTRA QUALCOMM SERVICES ENABLED
EXTRA STORAGE FEATURES ENABLED
ADVANCED ANDROID SERVICES ENABLED
CONFIGURATION OF NOT EXISTING SETTINGS
BATTERY DRAINING LOGS/SERVICES DISABLED
BATTERY CALIBRATION AFTER CHARGING
ZYGOTE HANDLING OPTIMIZED
VM HANDLING OPTIMIZED
DEX2OAT OPTIMIZED
SERIAL NUMBER UNDER SETTINGS
FORCED ENCRYPTION DISABLED
DM VERITY DISABLED
(YOU ARE FOLLOWING A DEVELOPMENT PROJECT HERE)
GOOGLE APPS
OPEN GAPPS SUPER LIGHT VERSION
CONTAINING
CHROME/WEBVIEW
DIALER/CONTACTS
SEARCH/ASSISTANT
PLAY STORE
STORAGEMANAGER
AND ALL NEEDED EXTRA SERVICES
WHICH ARE NOT VISIBLE IN THE LAUNCHER
ROOTING
SUPERSU BETA
SUPERSU STABLE
MAGISK BETA
MAGISK STABLE
(WITH DISABLED ENCRYPTION)
(OR CHOOSE NO ROOT FOR NO DECRYPTION)
REQUIREMENTS
TWRP RECOVERY REPLACEMENT
DECRYPTED DATA ACCESS
UNLOCKED BOOTLOADER
64BIT SNAPDRAGON SOC
AOSP BASED ROM/OS
(SNAPDRAGON 810+ AND 4GB+ RAM RECOMMENDED)
DOWNLOAD
INLIGHTNING WEBSITE / LIGHT
(READ THE FIRST THREE POSTS OF THIS THREAD BEFORE DOWNLOADING THE PATCH)
(SHARING DIRECT LINKS TO MY FILES OR MIRRORING MY WORK IS NOT DESIRED)
AND LAST BUT NOT LEAST
ENJOY THE PATCH AND FEEL FREE TO SHARE YOUR FEEDBACK/PATCH/DEVICE/OS CONFIG
STAY CONSTRUCTIVE, FRIENDLY AND RESPECT OTHERS
XDA:DevDB Information
LIGHT PATCH, Tool/Utility for all devices (see above for details)
Contributors
Miustone
Version Information
Status: Stable
Created 2017-11-23
Last Updated 2017-12-01
Click to expand...
Click to collapse
Hi! Thanks for this Patch!!! Does it work on Android 8.1 DP2 on Pixel XL? Or on Android 8.0 Stock too?
Maximaro said:
Well i try it out =)
Using Redmi note 3 Pro with the new ABC Rom which looks like more aosp - Pixel version.
Alles gute Dir! und Danke für den Patch!
Click to expand...
Click to collapse
Hope You enjoy it
Und danke dir für die netten Worte! Grüße aus Bad Oeynhausen!
TotoBerto02 said:
Hi! Thanks for this Patch!!! Does it work on Android 8.1 DP2 on Pixel XL? Or on Android 8.0 Stock too?
Click to expand...
Click to collapse
8.0 is supported but not sure about 8.1. I would appreciate any feedback about it!
BR
BTW. STILL SEARCHING FOR A TEAM MATE
Watch this Post for more Informations: https://plus.google.com/+MariusYeezus/posts/34mnEBYfX5c :angel:
Miustone said:
READ CAREFULLY BEFORE YOU START! THE PATCH IS NOT A ROM/MOD/KERNEL
ABOUT
Rethink about Android customizations. Make it Yours!
The Light Patch ZIP File is a advanced multifunctional Utility, based on the famous AROMA for custom recovery Replacements like TWRP. It comes with everything that is needed to fully unleash the Potential of Your Device. Advanced Techniques from Google, Sony, HTC, Qualcomm and many Others combined into a single Package which fits for all Snapdragon Flagships running the very latest Android Versions. One to rule them All! Use a AOSP System as Base and get the Quality of a Stock Firmware, decide about the System Content, gain extra functionalities and enhance Your Device on a unsuspected Way. Everything is based on Years of intensive Research and deep going Changes on Android which You will find nowhere else. There are to many Features and Changes to list them all, but take a look at the Feature List and check out the insanely long Changelog which includes the Changes of Hundreds of Releases. Or just give it a try now, read the Instructions and Start off! AROMA will guide You thru the whole Patch Utility...
FEATURES
AROMA 3.0 POWERED BASE
OPTIMIZED MAGISK INCLUDED
OPTIMIZED SUPERSU INCLUDED
OPTIMIZED GAPPS INCLUDED
OPTIMIZED BUSYBOX INCLUDED
DEVICE TRANSFORMING OPTIONS
DPI/DEVICE UI TYPE OPTIONS
LIGHT EXCLUSIVE EXTRA OPTION
OPTIONAL DEBLOATING OPTIONS
UI SOUND OPTIONS
STORAGE WIPE OPTIONS
BOOTANIMATION OPTIONS
LIGHT AUDIO SYSTEM OPTION
4K AND HDR SUPPORT ENABLED
PARTITION TRIMMING ENABLED
USEFUL INIT.D SCRIPTS ENABLED
EXCLUSIVE PIXEL FEATURES
EXCLUSIVE OEM FEATURES
SETUP WIZARD ROTATION
LOCKSCREEN ROTATION
HOMESCREEN ROTATION
ENHANCED UI QUALITY
SMOOTHER UI RENDERING
ENHANCED APP RENDERING
ENHANCED GAMING HANDLING
ENHANCED SENSOR HANDLING
ENHANCED NETWORK HANDLING
ENHANCED ENERGY CONSUMPTION
ENHANCED STORAGE HANDLING
ENHANCED VOICE RECOGNITION
ADVANCED BLUETOOTH SERVICES
ADVANCED AUDIO HANDLING IN/OUTPUT
VARIOUS PERFORMANCE IMPROVEMENTS
ADVANCED VISUAL HANDLING IN/OUTPUT
EXTRA QUALCOMM SERVICES ENABLED
EXTRA STORAGE FEATURES ENABLED
ADVANCED ANDROID SERVICES ENABLED
CONFIGURATION OF NOT EXISTING SETTINGS
BATTERY DRAINING LOGS/SERVICES DISABLED
BATTERY CALIBRATION AFTER CHARGING
ZYGOTE HANDLING OPTIMIZED
VM HANDLING OPTIMIZED
DEX2OAT OPTIMIZED
SERIAL NUMBER UNDER SETTINGS
FORCED ENCRYPTION DISABLED
DM VERITY DISABLED
(YOU ARE FOLLOWING A DEVELOPMENT PROJECT HERE)
GOOGLE APPS
OPEN GAPPS SUPER LIGHT VERSION
CONTAINING
CHROME/WEBVIEW
DIALER/CONTACTS
SEARCH/ASSISTANT
PLAY STORE
STORAGEMANAGER
AND ALL NEEDED EXTRA SERVICES
WHICH ARE NOT VISIBLE IN THE LAUNCHER
ROOTING
SUPERSU BETA
SUPERSU STABLE
MAGISK BETA
MAGISK STABLE
(WITH DISABLED ENCRYPTION)
(OR CHOOSE NO ROOT FOR NO DECRYPTION)
REQUIREMENTS
TWRP RECOVERY REPLACEMENT
DECRYPTED DATA ACCESS
UNLOCKED BOOTLOADER
64BIT SNAPDRAGON SOC
AOSP BASED ROM/OS
(SNAPDRAGON 810+ AND 4GB+ RAM RECOMMENDED)
DOWNLOAD
INLIGHTNING WEBSITE / LIGHT
(READ THE FIRST THREE POSTS OF THIS THREAD BEFORE DOWNLOADING THE PATCH)
(SHARING DIRECT LINKS TO MY FILES OR MIRRORING MY WORK IS NOT DESIRED)
AND LAST BUT NOT LEAST
ENJOY THE PATCH AND FEEL FREE TO SHARE YOUR FEEDBACK/PATCH/DEVICE/OS CONFIG
STAY CONSTRUCTIVE, FRIENDLY AND RESPECT OTHERS
XDA:DevDB Information
LIGHT PATCH, Tool/Utility for all devices (see above for details)
Contributors
Miustone
Version Information
Status: Stable
Created 2017-11-23
Last Updated 2017-12-01
Click to expand...
Click to collapse
Hey can u add huawei apps ??
toussaintjames said:
Hey can u add huawei apps ??
Click to expand...
Click to collapse
please do not quote the whole post
Can you make this for Mediatek devices?
toussaintjames said:
Hey can u add huawei apps ??
Click to expand...
Click to collapse
What is the benefit of them? Any special Ideas about which Apps?
SkaboXD said:
Can you make this for Mediatek devices?
Click to expand...
Click to collapse
The most of it is based on Qualcomm Tech and Ports. I'm not advanced with Mediatek but know that there are "similar" Techs available for them. I would prefer to let that others do, but i'm willed to help porting it if someone has interest on making a second Light Patch for Mediatek exclusively... What i never would support is Exyons, which is the biggest trash ever in My Eyes. Hardly closed sourced and not as much advanced as i want it to...
I'm btw. working recently on the next Patch System (V4). There will come a lot of changes, keep an eye on the Changelog if You like Spoilers :angel:
BR, Miu
So much work left... But i'm satisfied about the new Layout and Options. Much more to choose from besides some cool new Ideas which where long enough in My Backhead since some Version. I'm also working on ROM/OS injection Support and a One Click Option which flashs the Patch like i use it without the need to fight thru the whole Setup.
The OS Injection will be a Option and runs automatically on the One Click Installer, the first Release of it needs a unpacked/repacked OS which needs to be copy and pasted into the root of the Patch (Or just a ZIP inside the Patch, dunno yet). My Scripts are doing the Rest. Planned is a Injection Method of external Zip Files for the next Releases. I need to find a Solution for that and the Handling of ROM/OS Scripts in the Patch. Complex stuff but i think this could be a big Thing at all...
Any Help with it would be much appreciated!
All the Best! Miu
Miustone said:
So much work left... But i'm satisfied about the new Layout and Options. Much more to choose from besides some cool new Ideas which where long enough in My Backhead since some Version. I'm also working on ROM/OS injection Support and a One Click Option which flashs the Patch like i use it without the need to fight thru the whole Setup.
The OS Injection will be a Option and runs automatically on the One Click Installer, the first Release of it needs a unpacked/repacked OS which needs to be copy and pasted into the root of the Patch (Or just a ZIP inside the Patch, dunno yet). My Scripts are doing the Rest. Planned is a Injection Method of external Zip Files for the next Releases. I need to find a Solution for that and the Handling of ROM/OS Scripts in the Patch. Complex stuff but i think this could be a big Thing at all...
Any Help with it would be much appreciated!
All the Best! Miu
Click to expand...
Click to collapse
Hello Miu im looking your thread and cheking it often and waiting the new version i didn`t flash 1.6 because you mentioned you gona release new one and i read the changelog and i get even more excited about that. Im not So big at development patches but i have few questions and or maybe a suggestion.
In the Changelog i read about the Audio Optimization and thanks to AndroidBoy So i guess one of the echancment is pushing the SnapDragon DAC in Performance Mode? is this correct im interested in what kind of Audio Exhancment the Patch will inlude im a HTC 10 Owner now im set with Sauron.
Also what will be beneficial to ecchange the Snapdragons to the posible ever VIDEO/Image i mean the Best Posible quality watching Video, Pictures or whatever related to media this will be really beneficial for everyone.
Also before in the past years when we was still roling older Android build everyone know the tricks with build.props editing and so on in case to make something better or just to improve.
Now is a litle more different with the new Androids version and i think the things become much more advanced will be beneficial to have improvement of the SIGNAL WIFI Network if you want whatever all related things to the Chipset.
I wish if you have it already a link to read more detailed changelog for example how something is acomplishing and will have an idea whats really going on with the device applying that patch.
Thank you and keep doing LIGHT
tsalta said:
Hello Miu im looking your thread and cheking it often and waiting the new version i didn`t flash 1.6 because you mentioned you gona release new one and i read the changelog and i get even more excited about that. Im not So big at development patches but i have few questions and or maybe a suggestion.
In the Changelog i read about the Audio Optimization and thanks to AndroidBoy So i guess one of the echancment is pushing the SnapDragon DAC in Performance Mode? is this correct im interested in what kind of Audio Exhancment the Patch will inlude im a HTC 10 Owner now im set with Sauron.
Also what will be beneficial to ecchange the Snapdragons to the posible ever VIDEO/Image i mean the Best Posible quality watching Video, Pictures or whatever related to media this will be really beneficial for everyone.
Also before in the past years when we was still roling older Android build everyone know the tricks with build.props editing and so on in case to make something better or just to improve.
Now is a litle more different with the new Androids version and i think the things become much more advanced will be beneficial to have improvement of the SIGNAL WIFI Network if you want whatever all related things to the Chipset.
I wish if you have it already a link to read more detailed changelog for example how something is acomplishing and will have an idea whats really going on with the device applying that patch.
Thank you and keep doing LIGHT
Click to expand...
Click to collapse
Hey, haven't much time to reply right now. But i really appreciate Your interest and Your Post here. I don't know You, but are You advanced with making ROMs or something with Android?
https://plus.google.com/+MariusYeezus/posts/528dEumjwKU
I'm still searching Team Members! Anyone with knowledge about Android is welcome... Especially App and ROM Developers!
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.
{
"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 9 Pie
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.
Notice
- READ: 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;
- We encourage users to contribute towards this project, and we're openly accepting applications for others to join Team Bliss
First, a little bit about this project...
Starting in Android Pie, Bliss OS will be taking a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, we have reworked a good majority of the commits from Android-x86 Project and Bliss OS's Oreo release, and packaged it up so that it can work a bit more dynamically. The result was something we could integrate into a single source, along side normal device builds. This is much like our Treble builds that use PHH's Treble methods, and Intel's Project Celadon's EFI builds. Both of which are also buildable directly from the BlissRoms-x86 source: https://github.com/BlissRoms-x86/manifest
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well. For now though, you can stay tuned to this thread for updates on all that.
ROM Porting Details:
Like we mentioned already, things this round will be done a bit differently using the patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, https://github.com/Android-PC and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
https://github.com/Android-PC/platform_build/commit/eda2e16b0018c5554f98acaa708f8200a171f206
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so
We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.
AIO Thread
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
BlissRoms-x86
https://github.com/BlissRoms-x86
Bliss' Android-PC Project
https://github.com/Android-PC
Open Gapps Project
!!CONSIDER THESE AS DEVELOPMENT BUILDS FOR NOW!!
These are not to be considered stable in any way shape or form. Please continue at your own risk. Developers and experienced users suggested
This release is a work in progress, and will take community effort in order to iron out all the bugs.
There are no IPTS builds for the Surface devices yet, and there won't be until I am able to fix my SurfaceBook. Sorry :'(
Read the documentation first:
https://docs.blissos.org
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with available installation options before attempting to install the OS.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Download the ISO file
Use Rufus or similar to burn to USB drive
Disable Secure Boot, Bitlocker, and any other boot security
Boot into the USB drive.
Run Bliss OS in Live mode to test things out, if all is well, continue to next step
Boot into the USB drive, and choose Bliss OS Install
Pick your poison, but please do this with caution, making sure to fully understand what you are doing.
These are beta builds, so please take that into consideration when reporting issues. We want all the info possible
Packages Manager sometimes crashes the system. This will require you to wait, then open a terminal and use $ su && svc wifi disable , and when it comes back, $ su && svc wifi enable
Screenshots aren't working yet
Video playback does not work right as of yet
Sound issues on many machines still
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.
-You can also open trouble tickets on our website for bugs.
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!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
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 team
when 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.
Thank you for using Bliss! And have as always: #StayBlissful
XDA:DevDB Information
Bliss OS - Pie for PCs (development Beta Preview), ROM for the ROM Central
Contributors
electrikjesus, ElfinJNoty
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: x86 Arch
Version Information
Status: Beta
Current Beta Version: 20181018
Beta Release Date: 2018-10-18
Created 2018-10-19
Last Updated 2019-07-23
The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates
Build Types Explained:
Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux)
-gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
Q: OK, So I have a BlahBlah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie 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...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io
Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Does not work on Asus t101ha (cherrytrail)
wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable
electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?
electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.
electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install
Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?
Hello
For the past couple (weeks) I've been trying to compile Android 10 for tenderloin using the Android 9 sources but it's not going so well. First thing I ran into multiple sepolicy errors and I feel as if I fixed them in inappropriate ways but the errors went away. Other errors regarding camera and audio and such, that are regarding that tenderloin no longer uses the legacy audio format. Made me confused because I used the device sources form Evervolv and DIrty unicorns and if i'm correct they built it exactly the same way they uploaded it. After these errors were wrapped up, I got a error at zipping the rom that it could not zip due to failure of being able to read build.prop. This made me believe that the sources are not correctly formatted. If anyone can help me find a manifest, I can build for all you guys. Please keep tenderloin alive!
Now, I did something and I'm getting plenty of perl errors. Maybe I'm just very unlucky. I'm gonna attempt to reinstall on a fresh drive on my server.
If its anyone's concern, I was building lineage 17.1. I noticed for example, Lineage's "qcom-device" repo was shaped completely differently than Evervolvs qcom-device repo.
This led me to thought that Android 10 is going to be extremely difficult because of all the upstream dev changes that was pushed to Q. If any of you would like, I could probably push out March patches Pie rom because over there I'm mostly safe of complying with the source.
My manifest shape
DirtyUnicorn's device-tree
DirtyUnicorn's device-tree-common
DirtyUnicorn's htc-msm8960-kernel
Evervolv's vendor
And dirty unicorn's atheros wlan driver
I have been changing up the device tree so much, it almost looks ridiculous . From what I heard lots of properties on the device tree haven't been touched for years. Maybe tomorrow I can try Evervolv's Q rom. If you guys can help me build up my manifest, we can push out a fully working Q rom for tenderloin. And it would be just in time when Android 11 comes out. Thank you everyone!
I wish that I could offer any help, but I never tried to compile any Android ROM or for the HP_TP.
To my knowledge the only users that I know that could offer some insight on the process would be:
@flintman
@elginsk8r
Also the LuneOS project could offer some help:
https://pivotce.com/tag/luneos/
If Android Q(10) can not be ported to the HP_TP, then at least P(9) is a good ROM to keep updating that could provide many years of App support.
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
djared704 said:
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
Click to expand...
Click to collapse
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
HP_TOUCHPAD said:
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
Click to expand...
Click to collapse
When I look at the tenderloin source, the script to gather the camera driver is disabled. Camera isnt a huge deal though because its only 1.3 MP. However we use the MSM 8960 kernel from HTC and that is the one m7,, but the one m7 is a SD 600 device so it loses sense. I was gonna get some help with one of my kernel developer buddies to dev a kernel for android 10 for tenderloin. If you see the one m7 has Lineage 17.1 available and even though it doesnt have same chipset, if im correct both chipsets went off of the same assembly line process. Lineage 17.1 for the one m7 also packages it as a "uimage" which is what we use. I believe this was only a very small select of devices. Yeah about that ive been getting so many complaints during build about "mkimage" which should've been a prebuilt tool in the lineage source. Don't know why they removed it, or if our developers added it in by their selves, etc. Anyways I fixed that error by just "allowing" mkimage in one of the permission files in my environment. But yeah i went as far as the build packaging the ROM and it complaining it cannot read build.prop. Note the build.props are generated by the environment , not the source (even though the device data is gathered by the source, its not what im talking about). I even go to the directory it was complaining about and it was all there. One of my friends suggested a permission error. I changed permissions to 777 (rw to all users) and it would still output that error. By that point I trashed my build meaning I may of done something wrong early on. I will let someone else continue building 10 but I will continue building 9 with latest patches.
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
HP_TOUCHPAD said:
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
Click to expand...
Click to collapse
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
djared704 said:
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
Click to expand...
Click to collapse
I have only recompile the Kernel and all of them work, but the correct branch must be use. I can not say about building a ROM, never done it.
But Evervovs Pie by elginsk8r works very well and stable as it uses the same kernel, but the framework is different. I guess elginsk8r will be the only that can guide you on the right direction or flintman.
Have fun learning, it takes a lot of TIME!