Database Info

[ROM][4.4.4] Carbon ROM [UNOFFICIAL][HEADS UP/HOVER][12/08/2014]

{
"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"
}
Carbon ROM​
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project.
We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub and on our Gerrit
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
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! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
How to install
-Requires Unlocked Bootloader, CWM & Root
1) Place ROM & Gapps in your virtual SD
2) Reboot in Bootloader Mode
3) Go to "Recovery" (Vol -) and confirm (Vol +)
4) Select (Vol +/-) "Wipe Data/Factory Reset" and press Power button | For a clean
5) Select (Vol +/-) "Yes - Wipe all user data" and press Power button _| installation
6) Select (Vol +/-) "Install Zip", "Choose zip from /sdcard"
7) Go where you placed the ROM zip, select it and confirm
8) Re-do 7 and 8 with Gapps zip
9) Now "reboot system now"
Known Bugs
-SystemUI Crashes on XT1033 variant
Download
Dev-Host (old builds)
AndroidFileHost
Sources
CarbonDev on Github
Device tree (branch Carbon-4.4)
XDA:DevDB Information
Carbon ROM, ROM for the Moto G
Contributors
Alberto97, dhacker29, razrqcom-dev-team, Team CyanogenMod, Team Carbon
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Created 2014-01-25
Last Updated 2014-08-12

Changelog & Download
Changelog & Download
CLICK ON DATE TO DOWNLOAD
For OFFICIAL Carbon Rom changes (when I write "sources update"), see here
No Dual-SIM support actually
11/08/2014
-3.4.102 Kernel
-Fixed Audio bug (you don't have to enable DSP Manager to hear something anymore) thanks @medic
-Sources Update
21/07/2014
-Sources Update
-KTU84Q (Just build number change, no new other changes from Google)
-Heads Up Update
24/06/2014
-O3 Optimizations
-Added Heads Up as Unofficial feature --> PLEASE, READ THE POST BELOW BEFORE POSTING!
-Sources Update (Just little changes)
20/06/2014
-Sources Update
-Android 4.4.4
-New DSP Manager interface (omni themed)
-Fixed 1194MHz frequency bug
13/06/2014
-Sources Update
-Hover!
09/06/2014 (I suggest a wipe data)
-Sources Update (Android 4.4.3)
-Fix GPE device detection
01/06/2014
-Big Sources Update
-Lots of new features!
-Linaro Toolchains 4.9.1 Compiled!
17/04/2014
-Sources Update
-Please, test another time if it works also on XT1033
04/04/2014
-Sources Update
-Please, test if it works also on XT1033
18/03/2014
-Sources update
28/02/2014
-Sources Update
-Pocket Mode works now!
23/02/2014
-Google Play Edition Compatible now
-Sources Update
-Come back FM Radio!
-DSP Manager now works!
16/02/2014
-Sources Update
-PIE Controls Added
07/02/2014 (One build for all variants from now, thanks to dhacker29)
-Sources update
-More features
-More translations
25/01/2014: XT1032 | XT1034
-Initial release

Floating Notifications (Heads Up/Hover)
Floating Notifications Disabled
Floating Notifications Enabled (If you enabled Heads Up from Settings --> Display & lights, it means this, else Hover is enabled)
NOTE: If you enabled Heads Up, you can't disable floating notifications by tapping on the icon above, first you have to disable Heads Up and then you can disable floating notifications
NOTE2: If you enabled Heads Up but it isn't working, try tapping on the icon above or/and a reboot

So what is different from http://forum.xda-developers.com/showthread.php?t=2618396
Hey wait wait. wait.. wait... wait....
Sent from my mmmmuuuuffffffffiiiinnnn

HUNTER said:
So what is different from http://forum.xda-developers.com/showthread.php?t=2618396
Hey wait wait. wait.. wait... wait....
Sent from my mmmmuuuuffffffffiiiinnnn
Click to expand...
Click to collapse
Anyone, for now...

Alberto97 said:
Anyone, for now...
Click to expand...
Click to collapse
Sorry I didn't understand you.
Hey wait wait. wait.. wait... wait....
Sent from my mmmmuuuuffffffffiiiinnnn

HUNTER said:
Sorry I didn't understand you.
Hey wait wait. wait.. wait... wait....
Sent from my mmmmuuuuffffffffiiiinnnn
Click to expand...
Click to collapse
I downloaded sources before him, but I didn't have time to release a build so I didn't want to waste time and work
EDIT: First release for XT1032 Uploaded!

Isn't this rom already on the other section? I mean, even if you merged sources before a1pha, he released it first...

anerik said:
Isn't this rom already on the other section? I mean, even if you merged sources before a1pha, he released it first...
Click to expand...
Click to collapse
I did all by myself, simply check my sources

Alberto97 said:
I did all by myself, simply check my sources
Click to expand...
Click to collapse
Not to be harsh mate, but I think you may be posting this on the wrong section on xda. I'm not 100% sure myself actually. I think it should be in the Android Development section and not in the Original Android Development section.

akash3656 said:
Not to be harsh mate, but I think you may be posting this on the wrong section on xda. I'm not 100% sure myself actually. I think it should be in the Android Development section and not in the Original Android Development section.
Click to expand...
Click to collapse
Since I'm on XDA I always saw source built roms in Original Android Development section

Alberto97 said:
Since I'm on XDA I always saw source built roms in Original Android Development section
Click to expand...
Click to collapse
Well on the Nexus devices, a source built but kangs or unofficial self built or fork of a ROM usually ends up in the "Android Development" section so yea. Not sure if it applies on every device on XDA though.

I think unofficial and kangs go in the normal development section, or only kangs i dont remember. But still this rom was already released, no matter what section both roms are the same. Only one of them should be here unless one of the 2 roms were modified to add or delete features

akash3656 said:
Well on the Nexus devices, a source built but kangs or unofficial self built or fork of a ROM usually ends up in the "Android Development" section so yea. Not sure if it applies on every device on XDA though.
Click to expand...
Click to collapse
In this case I don't know, I saw phones like Galaxy Mini, S Advance, Ace II etc. These aren't officially supported phones from all ROMs
EDIT: Sorry, you were right:
The following are most likely “Original Development”:
-Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
-Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
-A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
-Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
-Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
-Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
-Your own “unofficial” stock build of your favourite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
-Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
-Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
-Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
-A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
-A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Click to expand...
Click to collapse
Thread already reported!

Alberto97 said:
Changelog & Download
25/01/2014: XT1032 | XT1034
-Initial release
Click to expand...
Click to collapse
Thanks for your work.I hope you continue to work on your roms and to try to keep them updated.
Enviado desde mi XT1032 mediante Tapatalk

i flashed it , now its just on Carbon bootanimation , i cant get recovery also ., what to do ?

Jwtiyar said:
i flashed it , now its just on Carbon bootanimation , i cant get recovery also ., what to do ?
Click to expand...
Click to collapse
Sorry, I was very busy with S Advance development. Does it work now?
New build! Download and changelog at second post!

Alberto97 said:
Sorry, I was very busy with S Advance development. Does it work now?
New build! Download and changelog at second post!
Click to expand...
Click to collapse
Thank you for reply ,No because all Roms same issue and stuck at bootanimation . i dont know whats wrong with my device.
Sent from my XT1032 using Tapatalk

Jwtiyar said:
Thank you for reply ,No because all Roms same issue and stuck at bootanimation . i dont know whats wrong with my device.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Restore to factory, boot but don't run OTA update. Then install CWM for 4.3 bootloader and try again.

Installed this, all fine. GPS works. the only issue is the intermittent screen not reminding on unlock.

[ROM][DS]CarbonRom KitKat [MOTO E/CONDOR][03-11-2014]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
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! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed 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.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every peny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
ROM Banner
{
"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"
}
​
XDA:DevDB Information
CarbonRom, ROM for the Moto E
Contributors
vishal_android freak
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest firmware
Based On: AOSP, CyanogenMod, SlimRom
Version Information
Status: Stable
Stable Release Date: 2014-10-24
Created 2014-10-24
Last Updated 2014-11-03

Changelogs, Instructions, Sources, Credits
Changelogs
Code:
Nightly #2:
-fixed 6 bar signal FC in carbon fibers
-fixed Sim settings FC in dialer settings
Code:
Nightly #1:
- initial build
Bugs?
-None that I am aware of.. You can tell me if you find any..
Instruction for flashing CarbonRom for the first time:
Boot into recovery
take nandroid backup of your current rom (to avoid any mishap)
Wipe data/factory reset, cache and dalvik cache
Flash rom zip and appropriate gapps
Reboot
Instruction for upadting to latest build:
Boot into recovery
Wipe cache and dalvik cache
Flash rom zip
reboot
Sources:
Device Tree
Kernel Tree
Vendor Blobs Tree
Credits:
CarbonRom team
CyanogenMod team
percy_g2
Tsukishiro
Shardul Niphade
percy_g2 said:
GENERAL COMMENT AND REQUEST:
We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"
Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).
We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.
Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.
Click to expand...
Click to collapse

Reserved

Downloading Now, was waiting for this.

[Stable] But Battery Drain Is Quite High.

most awaited rom back again!!
Status: stable!!!!! Hope thats true!! Gonna flash it, the most sleek,smooth and elegant rom!!
Thankful to the new dev!!

I had 2 reboots using the keyboard and using the crhome app. And in Carbon site says it has 100% Portuguese translation, but Carbon Fibers is only in English.

Fails every time wifi is switched off, only works for a moment

I'm trying to make this ROM fail, and fortunately I am unable to do so until now.
The only thing I cannot do so far is to get a lock on the GPS, but I am on Manhattan, so it is hard even on Stock.
I cannot be more grateful with the OP for releasing this ROM.

phone.apk fc on dual sim settings...

AshuGite said:
phone.apk fc on dual sim settings...
Click to expand...
Click to collapse
Get a logcat instead of a screenshot.. I know how a FC window looks.. That's just gona make me understand why or what is causing the issue

vishal_android freak said:
Get a logcat instead of a screenshot.. I know how a FC window looks.. That's just gona make me understand why or what is causing the issue
Click to expand...
Click to collapse
log attatched...
also cm torch is useless app..

Tested on XT1022 . So far no issues stable...

-when applied a theme and again reverting back to default requires a reboot to take affect to see the changes!
All over the rom is stable! In my XT1022

thanks for making carbon rom for us....... but fc in carbon fibers-->statusbar-->general-->enable six bar signal and carbon fibers-->statusbar-->general-->signal status style seems not to working.
attaching log

Which file to download out of the three files?

smith44 said:
Which file to download out of the three files?
Click to expand...
Click to collapse
This one: https://s.basketbuild.com/devs/vishal_android_freak/carbon/condor/

furnace kernel working or not??
Anyone tried the furnace kernel in this rom?? Is it working?? Cuz wen i tried, WIFI dint seem to work!!!

prince trishi said:
Anyone tried the furnace kernel in this rom?? Is it working?? Cuz wen i tried, WIFI dint seem to work!!!
Click to expand...
Click to collapse
Same thing for me. On Spirit and Carbon.

doubt!
SirRhor said:
Same thing for me. On Spirit and Carbon.
Click to expand...
Click to collapse
This rom is based on CyanogenMod, aosp nd slimrom where cm nd aosp built rom r easily compatible wid the furnace kernel but then y not dis!

[ROM][UNOFFICIAL][Lollipop 5.1.1][Tate] PAC-ROM

{
"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"
}
* By flashing this, you automatically void your warranty!
* If your phone breaks, blows up or runs away from you, do not cry to us!
* Do not ask for ETAs!!
​
* Download the ROM and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the ROM and then GApps
* Reboot your phone
* Enjoy
​
* PAC-ROM Download
* Open GApps Nano 5.1
​
* PAC-ROM Sharing Policy
* PAC-ROM Site
* PAC-ROM Forum
* PAC-ROM Gerrit
* PAC-ROM Changelog
* PAC-ROM JENKINS
* PAC-ROM Bug Reports/Feature Requests
* PAC-ROM Github
* PAC-ROM Stats
* PAC-ROM Google+
* PAC-ROM Facebook
* PAC-ROM Twitter
* Want to become a device Maintainer for PAC-ROM?
* PAC-ROM Central - Questions and Features broken down and seen by all PAC Devs on XDA
​
* PAC-ROM Team
* Cyanogen Team
* AOKP Team
* Paranoid Android
* SlimRoms
* RootBox
* Carbon ROM
* Vanir
* ChameleonOS
* Omnirom
* Paranoid SaberDroid
* Special thanks to all our Build Bot Providers (see Contributors list for all names)
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names)
* And of course, thank you for your love and support!
​
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
Status: Unofficial Release
NOTE: THIS IS ONE AND THE LAST ONE 5.1.1 (LMY49J) BUILD.
AFTER INSTALLATION:
GO TO SETTINGS - PAC SETTINGS - MISCELLANEOUS - PAC STATS
AND UNCHECK THIS BOX <ENABLE REPORTING>
OPTIONAL:open build.prop file (requires root) and change string "ro.build.display.id=cm_tate-userdebug 5.1.1 LMY49J..." to "ro.build.display.id=pac_tate-userdebug 5.1.1 LMY49J..." (watch screenshot #1)
Personal Modifications:
- Bootanimation is replaced with MM bootanimation
- Old fashioned Calendar replaced with Google Calendar
- Added missing OmniSwitch

@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.

alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.

alexander_32 said:
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.
Click to expand...
Click to collapse
I have the same issues when building for jem. If you don't mind PMing your build errors (preferably the whole build output if you have it), I can try to patch file_contexts until transi fixes the file to resolve the build errors. Also, you may later get an issue with make_recovery_patch; if you do, let me know and I'll tell you how to fix it. transi's been quite helpful when I started building my custom CM ROM for jem; I tried contacting him about the latest issue with file_contexts, but he hasn't responded yet.
Sent from my Amazon Jem using XDA Labs

Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.

xWolf13 said:
Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.
Click to expand...
Click to collapse
Yep, I guess that Git is not up to date.
Thank you xWolf13.

alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:

vasolini said:
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:
Click to expand...
Click to collapse
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.

alexander_32 said:
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.
Click to expand...
Click to collapse
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'm gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.

alexander_32 said:
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'll gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.
Click to expand...
Click to collapse
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Alright, we'll see what happens.

Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.

mikeataol said:
Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.
Click to expand...
Click to collapse
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.

alexander_32 said:
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.
Click to expand...
Click to collapse
Fixed it as you expected it would, Thanks!

mikeataol said:
Fixed it as you expected it would, Thanks!
Click to expand...
Click to collapse
No problem

That is the last one Lollipop release (LMY49J), by the way. Forgot to add it before.

[ROM][i9305][6.0.1][GELLO] Temasek's UNOFFICIAL CyanogenMod 13 [UNOFFICIAL]

{
"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"
}
INTRODUCTION | DOWNLOAD AND CHANGE LOGS | FAQ, BUGS, AND KNOWN ISSUES | CREDITS AND THANKS
temasek's UNOFFICIAL CM13 BUILDS
This is an unofficial maintainer thread for all current and future unofficial builds of CM13 created by @temasek. This thread was created on his behalf and will be maintained accordingly. Please report any bugs or issues that you see; when applicable, please follow the bug reporting format found in post #3. Download links, changelogs and other important information can be found in post #2. Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* 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. Hard. A lot.
*/
STOP!
If you do not read EACH and EVERY "OP" POST made by me (i.e. the first 5 posts) and post rudely, report bugs incorrectly, or ask for ETAs/feature requests, you WILL be called out for it.
You have been warned. Most, if not, any information you may be looking for can be found either in among these 5 posts or by performing a simple search using good key words. Think before you post. Thank you.
Download Links and Changelog
FAQ and Trouble Shooting
Credits and Thanks
The lastest version TWRP (3.0.2-1) is recommended.
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Dirty Flash/Update
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK.
3. Install the update zip from recovery.
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
3.2. FLASH AGNI AGAIN IF YOU ARE USING SUPERSU INSTEAD STOCK SU due to update zip flashing stock kernel.
3.3. Right after flashing ROM zip, flash updated GApps package. Flash the GApps right after to prevent "Setup Wizard has stopped working"
4. WIPE DALVIK/CACHE (for good measure).
5. Reboot Device.
[email protected]
Also consider donating to @PartimusPrime for making our amazing boot animation!: http://forum.xda-developers.com/donatetome.php?u=4620435​
Source Code:
https://github.com/limjh16/roomservice/blob/temasek13.0/roomservice.xml
XDA:DevDB Information
Temasek's UNOFFICIAL CyanogenMod 13, ROM for the Samsung Galaxy S III I9300
Contributors
limjh16, rodman01, p.a.n, Temasek, Trafalgar Square, Arter97, and whoever else who helped me!
Source Code: http://github.com/temasek/android
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.8
Stable Release Date: 2016-08-15
Created 2016-05-22
Last Updated 2016-08-15

Reserved
My AFH Folder for Temasek ROM
My Google Drive Folder for Temasek ROM
Open GApps [6.0.1]
MD5 file for ROM can be found on AFH.
Flash this to enable root access
SuperSU
CM13 Build
Build Version: v10.8
Android Version: 6.0.1_r61
For the most up to date changelog please visit:
Temasek’s CM13 Github Commits
I will also be including my own changelog in future builds.No difference from Temasek changelogs.​

Reserved
Multiple RIL Implementation
Since I am using @p.a.n sources multiple RIL implementation is active. However changes were made to both device, kernel and vendor sources which may have broken some things, because it did break RIL for me (Sometimes).
Multiple RIL implementation
In this ROM, there are more then one RIL implementations. None of them is perfect, but you can choose, which one of them works better for you. The first RIL implementation is the usual CM 12.1 based one (this is the default one), the second one is based on proprietary files extracted from stock 4.4.4 ROM downloaded from sammobile.com (I9305XXUFOB2_I9305PHNFOB2_I9305XXUFOA1_HOME.tar.md5), the third is based on proprietary files from TheMuppets, with one small change (see here for details). To switch between them open shell (over adb, or using the build in app, or whatever you like) and execute command ril. You will see something like this:
Code:
Select RIL implementation:
* 1 - CM 12.1 based
2 - Stock 4.4.4 based
3 - TheMuppets based
x - quit
?
I recommend you to change and play with the different implementations, however do keep in mind some things:
1. Stock 4.4.4 based IS NOT WORKING. You will notice RIL dies after reboot.
2. I personally use TheMuppets, but CM 12.1 is occasionally better. Do note that this is my personal preference, so do play with both implementations.
Titanium Backup - External SD Card problems (This Folder is NOT Writeable)
http://www.titaniumtrack.com/kb/tita...-not-writeable
Q: Is this ROM Stable?????? A: Yes. Unless stated as experimental.
Q: F2FS PLSSSSSS???? A: No.
Q: WHY NOT BOOT??? / WHY BUG???? A: Read below, and under "known issues"
Q: NEW BUILD PLS PLS PLS???? A: The weekend when Temasek finishes a new version
Some other issue?​You can't just say 'x is broken!' and expect me to magically find the bug and fix it.
Here's what I need:
Steps to reproduce - I don't care if "it's simple". I want to know exactly what you were doing at the time of the bug. How'd it happen? Does it only happen on Tuesdays when watching a specific YouTube video? Include it *all*
What happened - in what way is this *not* the expected behaviour? Don't just say "it didn't play/upload/whatever". Did the entire phone crash? Did it show an error? Did it just show an endless progress indicator? Again, I need specifics here.
Logcat/last_kmsg - Include the whole thing please, and if your phone's been running for a while, give me a rough region of time when the issue happened. Use last_kmsg if your device reboots unexpectedly, otherwise use a logcat.
For more FAQ, please visit @p.a.n 's thread here and read the OP as I used his sources.
HOWEVER PLEASE DO NOT POST QUESTIONS THERE. Just check whether your question is already answered.
I will answer all bug reports/questions to this ROM on this thread however please read above and adhere.
If you want SuperSU instead stock SU, Please flash Agni Kernel smdk4412 version or Boeffla Kernel.
If you want to install GApps after bootup, please follow the steps below:
1st method
Go to recovery and wipe /system
Flash ROM, then GApps
2nd method (If you want to update GApps)
Go to recovery and follow dirty flash instructions above
Tell me​

Reserved
@rodman01 @Trafalgar Square I did it haha
@p.a.n Thanks so much for source code
@temasek @arter97 for being creators of the ROM
and of course, to CM Slim AOKP Omni and whoever else helped in this ROM​

Last one, just in case.

What are the differences compared to normal CM?

dawidd6 said:
What are the differences compared to normal CM?
Click to expand...
Click to collapse
Check the change log. There are a lot of features kanged from other ROMS
Why not try it out and see for yourself?

with f2fs support will be Perfect

So many roms for our beloved s3. This is awesome.
I think that bug with gapps "setup wizard" crashing is depending on the gapps package and not the roms fault. :good:

JD. A said:
So many roms for our beloved s3. This is awesome.
I think that bug with gapps "setup wizard" crashing is depending on the gapps package and not the roms fault. :good:
Click to expand...
Click to collapse
Yeah it only happens with open gapps, but I don't recommend bank or Delta gapps because it's not tested haha... apparently the updater script is in the ROM, but I'm outside so I'm lazy to post instructions... will do when I get home

M4tEUSh said:
with f2fs support will be Perfect
Click to expand...
Click to collapse
Nope I'm sorry. I'm not a supporter of f2fs, I can't test it due to me being lazy to backup data/media )) and lastly it doesn't compile (main problem)

Thanks!
Add this to cm.mk
Code:
# Custom unofficial build tag
TARGET_UNOFFICIAL_BUILD_ID := temasek
Then you ZIP name will be cm-13.0-20160522-UNOFFICIAL-temasek-i9305-V8.6.zip

Trafalgar Square said:
Thanks!
Add this to cm.mk
Then you ZIP name will be cm-13.0-20160522-UNOFFICIAL-temasek-i9305-V8.6.zip
Click to expand...
Click to collapse
Why thank me? Anyways noted, will do that in next build.

@limjh16 root access works without flashing supersu. Just enable in developer options. The rom seems to be working fine.

JD. A said:
@limjh16 root access works without flashing supersu. Just enable in developer options. The rom seems to be working fine.
Click to expand...
Click to collapse
Yeah I did mention if u want to opt for SuperSU instead stock su

limjh16 said:
Yeah I did mention if u want to opt for SuperSU instead stock su
Click to expand...
Click to collapse
Oh I must have misunderstood then. The rom works great, had some random reboot at startup when selecting language. Other than that it's cool. I really like that you used p.a.ns multiple ril implementation too. It seems to be working better for me than the other roms.

JD. A said:
Oh I must have misunderstood then. The rom works great, had some random reboot at startup when selecting language. Other than that it's cool. I really like that you used p.a.ns multiple ril implementation too. It seems to be working better for me than the other roms. ????
Click to expand...
Click to collapse
Well, if that's so enjoy your stay! I will be regularly providing builds though don't expect any optimisations as I'm busy with another rom now haha

I will not be providing v8.8 due to problems in kernel by cm sources which disallows wifi to be connected.

congratulations @limjh16 been waiting for you to release your temesek:good:

alias_ z3d said:
congratulations @limjh16 been waiting for you to release your temesek:good:
Click to expand...
Click to collapse
Thanks! Finally fixed my errors lol

[ROM][7.1.2_r33][AOSP+CAF][UNOFFICIAL][16/08/17]halogenOS for Honor 8

{
"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, Reimagined.
For the best experience, view the thread on a web browser like Chromium or Firefox.
Desktop: Brilliant. Mobile: Good. Tapatalk: OK. XDA-Labs: Horrible.
Code:
/*
* The modifications performed to your device are
* performed by yourself, thus you must perform the
* leap of fate and accept the inevitable outcome, the
* responsibilities of what to do with your device are passed to you.
*
* We are of no responsibility for any damages, data loss
* or results of unexpected outcome, if you have **SERIOUS**
* problems with this software, do not hesitate to contact
* the developers or maintainers of your device port.
*
* We are not liable for anything that happens with your
* device. Shall you somehow screw up and take the leap of faith
* you may find that some companies may do indeed still honour
* warranties, although we cannot give one ourselves.
*
* Don't be stupid and bet on that generosity of companies though,
* please be responsible for what you do with your device.
* Do not try overclocking up to glorious 1337 GHz thinking an OEM
* would replace your glorious space heater only matched by the GTX480 etc.
*
* We recommend you to take the advice above regardless.
*/
XOS is a new generation Android-based cutting-edge OS based on the Android Open Source Project and Code Aurora Forum releases.
What is XOS?
halogenOS, also known as XOS is a new Android ROM which ships with the global aim to
become a modular ROM which keeps as high as potentially possible operating
performance on your mobile device while still maintaining a sufficient feature
base of nice, small and minimal features that would not be available via any
external feature base, extension, mod or plugin.
We hope you have a truly halogenified experience!
Internals of XOS
At core, the ROM is composed mainly of components from the
Android Open Source Project (AOSP) and Code Aurora Forum (CAF),
with extremely minor set of components from LineageOS (LaOS or LN) which
have been added to source in order to allow for better cross-device compatibility.
Our LOVE to others
A huge thanks goes to those behind the AOSP and CAF, the LineageOS Project and all of its
contributors for the sources used in the development of the base ROM which we
started with inclusive of all the work and dedication their team puts in order to
keep us updated on the awesome contributions that they make.
We will be keen on ensuring that we be up to date with the code from our base sources,
with regular ROM updates hopefully coming from time to time.
Please do not ask for ETA's (else you shall be spooked by Mr Skeltal). Almost all of us are
students, and with the current lifestyles and routines we have, it is not that easy to acquire
time to develop the ROM, though we'll be sure to keep you updated and release OTAs as
soon as they are available and ready for publication. If you want to be really updated quick,
then join us on Telegram: http://telegram.me/halogenos
Visit our website for features such as: Downloads, Information etc.
http://halogenos.org
Although no data should be lost or damaged by the flashing process,
we advise you to follow the following steps if you are coming from another ROM:
Code:
* Please take a full [I]Nandroid[/I] backup!
* Please copy your back up to an external device.
* Backing up your [I]Internal Storage[/I] is also recommended.
* When completed, [I]clean flash[/I] the build!
Although you usually may dirty flash halogenOS over other ROMs, considering the other
ROM is built upon the same Android version, it is not guaranteed.
In case of performance issues or crashes please do a clean flash.
You can dirty flash halogenOS 7 (Nougat) over halogenOS 6 (Marshmallow)
without any problems. Although we cannot promise that it will work for you,
although we don't recommend it, we can tell you that this has been tested.
Overall as a ROM, XOS is very stable. Our mission statement has always been of maintaining a clean and properly maintained ROM.
We take proper priority with ensuring that performance and stability are put first, features are considered an extra topping on the cake.
More details are marked by square brackets [x] and listed below
All Builds/Devices/Maintainers
Substratum Theming Support
Custom Lockscreen Visualizer
SuperUser Capable
Dexpreopt Enabled
Equipped with latest Busybox
Support for 3rd Party Webviews
Support for Modern Services e.g. Google Assistant
Long Press Home for Assistant
Enhanced Booting Speed [1]
System UX & Performance Optimizations [2]
Minor Audio Tweaks [3]
Enhanced Media Support [4]
I/O Tweaks [5]
Select Devices/Maintainer Dependent
Functional Vulkan API Implementation [6]
Code:
[1] Performed via implementation of additional multi-threading on boot etc.
[2] Tweaked [I]`surfaceflinger`, `inputflinger`, `System Server`[/I] & more...
[3] We do not ship 3rd party EQs or other [I]crap[/I] you may sometimes find.
Our sound system is completely clean and thus provides great soundmod
support if that's what one really wants.
[4] Enabled via FFMPEG & additional codecs.
[5] Example: Disabled Access Time
| Waste of write cycles and impacts I/O performance on random writes.
[6] Vulkan is available if the chipset/SOC's GPU supports Vulkan.
Installing for the first time
Code:
* Download the current version of XOS for your device.
* Reboot into a compatible Android Recovery solution. (Note: We recommend TWRP)
* Wipe [B]'/system', '/data' & '/cache'[/B].
[I](Optional: For `Dirty Flash`, do not wipe anything)[/I]
* If you are coming from the EMUI 5.x other than the latest one, then first flash Full LineageOS, or Full RROS by OpenKirin team.
* After that again boot into recovery and factory reset.
* Select the appropriate ROM zip and flash the current ROM build.
* Want Google Apps? Obtain and flash the latest GApps from http://opengapps.org/
* Flash any other system modifications you may want e.g. SuperSU/phh's SuperUser.
* Reboot.
Manually updating the ROM
XOS ships with an OTA updater built-in which should automate the downloading and flashing process,
however should your wish be to manually update the ROM, you should be our guest.
Code:
* Download the current version of XOS for your device.
* Reboot into a compatible Android Recovery solution. (Note: We recommend TWRP)
* [b]Please do not[/b] wipe anything, including Cache/Dalvik/ART, the ROM has you covered.
* Select the appropriate ROM zip and flash the current ROM build.
* Reflash any system modifications e.g. SuperSU/phh's SuperUser.
* Reboot.
You do not need to wipe Cache/Dalvik.
You do not need to flash Google Apps again*.
You do not need more than 5 minutes.
* Just make sure that you don't wipe system before flashing.
Screenshots
Currently right now, halogenOS will only include the stock Android theme.
We may one day decide to use a custom theme as soon as that theme is working perfectly fine.
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema
Download Links
Download XOS Here
ROM Sources
All Sources | ROM, Kernel, Trees etc. @ XOS GitHub Organisation.
Honor 8
Kernel source
Device tree
Vendor tree
Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group
Code Aurora Forums, CyanogenMod, Grarak, OpenKirin Team (XePeleato, surdu_petru, OldDroid) for bringing up the base device, kernel, vendor trees.
And everyone else who contributed and helps us!
In case you feel left out here, please contact us!
​
XDA:DevDB Information
halogenOS, ROM for the Honor 8
Contributors
DigiGoon
Source Code: https://github.com/halogenOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android N (EMUI 5.x)
Based On: AOSP+CAF
Version Information
Status: Testing
Created 2017-08-16
Last Updated 2017-08-21

Changelog
Changelog​
16/08/2017
Initial release.

Bugs
Bugs​
16/08/2017
NFC not working
Hotspot not working

DigiGoon said:
Changelog
16/08/2017
Initial release.
NFC not working
Hotspot not working
Click to expand...
Click to collapse
What does this mean? NFC not working and Hotspot not working means bugs or already fixed since it's in changelog?
Sent from my Honor 8 using XDA Labs

adriansticoid said:
What does this mean? NFC not working and Hotspot not working means bugs or already fixed since it's in changelog?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
They are bugs, sorry I forgot to put them in the bugs post, I'll put them now. Thanks.

Seems interesting and vulkan is working good ? Tried ?

Which kernel optimization are you talking about?

Vulkan libraries for great gaming experience.
I dont know which it relates to.

venugopalu007 said:
Vulkan libraries for great gaming experience.
I dont know which it relates to.
Click to expand...
Click to collapse
Did you try the ROM?

venugopalu007 said:
Vulkan libraries for great gaming experience.
I dont know which it relates to.
Click to expand...
Click to collapse
i flashed the rom and i played the game clash royale and it loaded up faster and ran smooth asf, faster then stock or any of the other roms i have used. so i think the Vulkan libraries work bro.

damenbm said:
i flashed the rom and i played the game clash royale and it loaded up faster and ran smooth asf, faster then stock or any of the other roms i have used. so i think the Vulkan libraries work bro.
Click to expand...
Click to collapse
bro can you try need for speed no limits ? please try and report

venugopalu007 said:
bro can you try need for speed no limits ? please try and report
Click to expand...
Click to collapse
Srry bro I didn't test that. I went back to RROS cus on this rom I wasnt getting notifications on what's app till I opened the app. I did test a few others like asphalt Xtreme and N.O.V.A 3 and it ran it smooth.

joe2k01 said:
Which kernel optimization are you talking about?
Click to expand...
Click to collapse
Ask the ROM developers, that line about various kernel optimizations is added by them.
No optimizations done from my side.

DigiGoon said:
Ask the ROM developers, that line about various kernel optimizations is added by them.
No optimizations done from my side.
Click to expand...
Click to collapse
So no optimizations at all

joe2k01 said:
Which kernel optimization are you talking about?
Click to expand...
Click to collapse
joe2k01 said:
So no optimizations at all
Click to expand...
Click to collapse
None from my side, but the ROM devs do it in the source code only, all the ROMs have a bit of developer specific optimizations.
That's why a ROM feels battery friendly and some feels performance friendly.
I hope you get it what I'm saying.
Regards,
DigiGoon

DigiGoon said:
None from my side, but the ROM devs do it in the source code only, all the ROMs have a bit of developer specific optimizations.
That's why a ROM feels battery friendly and some feels performance friendly.
I hope you get it what I'm saying.
Regards,
DigiGoon
Click to expand...
Click to collapse
I don't get what you are saying because optimizations in this ROM are CAF only

joe2k01 said:
I don't get what you are saying because optimizations in this ROM are CAF only
Click to expand...
Click to collapse
Okay, then just know this: No optimizations in this ROM, it's compiled as clean as it is.

DigiGoon said:
Okay, then just know this: No optimizations in this ROM, it's compiled as clean as it is.
Click to expand...
Click to collapse
Then remove optimization from OP

joe2k01 said:
Then remove optimization from OP
Click to expand...
Click to collapse
Dude please, like please, I'm literally begging you. Please read the OP again, and if you wanna try this then try, if not it's your choice. But please read OP carefully, and at least try to understand whats written there.
Regards,
DigiGoon

DigiGoon said:
Dude please, like please, I'm literally begging you. Please read the OP again, and if you wanna try this then try, if not it's your choice. But please read OP carefully, and at least try to understand whats written there.
Regards,
DigiGoon
Click to expand...
Click to collapse
I read again. I can read Kcal, upstream patches and kernel optimizations. If you use Openkirin's source code, everything I stated above is missing. So please remove this from OP