This new Android distribution treats development differently than any other.
CLICK HERE FOR THE ROM, THREAD, CHANGELOG, AND DISCUSSION.
A post detailing our team and new developers from TeamEOS can be found in the OP linked.
ntroducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either. We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!
Here's a bit of info you may want on this project for how we do things differently:
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Enjoy, and thank you for choosing codefireXperiment
XDA:DevDB Information
[ROM] [AOSP] [4.2.2] [cfX-Toolchain 4.8.y+] codefireXperiment, ROM for the Oppo Find 5
Contributors
anders3408
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: JDQ39E-20130
Stable Release Date: 2013-08-11
Created 2013-09-04
Last Updated 2014-08-18
Nice team you assembled there, looking forward to trying it out. openpdroid patches failed for me, oh well, gotta get more experience with xprivacy anyway.
BTW, didn't see it on your site so far, featurelist somewhere(espacially in terms of the kernel in use)?
any screenshot
S.D.Richards said:
BTW, didn't see it on your site so far, featurelist somewhere(espacially in terms of the kernel in use)?
Click to expand...
Click to collapse
look at the Github link to the kernel source
Sent from my HTC One X+ using xda app-developers app
maxwen said:
look at the Github link to the kernel source
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
https://github.com/codefireXperimen.../arch/arm/configs/cyanogenmod_find5_defconfig
Hard looking through that looking for pieces if you don't know the specific CONFIG_xxx name.
Anyway, in a quick scroll through, I fell over some enabled (=y) USB OTG stuff - I was under the impression the device doesn't support it?
Nightly is blazing fast. Quickest boot times ever. Even the first boot was super fast.
Sent from my Find 5 using xda app-developers app
Sorry to ask, I probably missed it somewhere... is this AOSP based, or other? Max's kernel is going on this bad boy if I try it... unless... it's already in there
no idea what this is, but i will flash it and take a look
Pure aosp based. For now not as many features as the other codefirex, but things are being added. Kernel is cm based with a few changes from maxwen and faux123, thanks both. Credits thread will come up.
Sent from my Find 5 using XDA Premium HD app
charlatan01 said:
Sorry to ask, I probably missed it somewhere... is this AOSP based, or other? Max's kernel is going on this bad boy if I try it... unless... it's already in there
Click to expand...
Click to collapse
Not tested maxwen kernel on it but you should be ready to reflash then, not totally sure it will work. Early tests did bootloop on maxwen kernels.
Sent from my Find 5 using XDA Premium HD app
anders3408 said:
Not tested maxwen kernel on it but you should be ready to reflash then, not totally sure it will work. Early tests did bootloop on maxwen kernels.
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks... I will hold off on flashing his kernel for the time being. It would be nice to get that working if possible.
charlatan01 said:
Thanks... I will hold off on flashing his kernel for the time being. It would be nice to get that working if possible.
Click to expand...
Click to collapse
Just tested, you should be able to boot maxwen kernel on cfxe, at least it does with cfxe ramdisk
test it out and tell how it wents
I do have some random reboots after +-10 minutes with this ROM. Can I provide you a logcat Anders?
anders3408 said:
Just tested, you should be able to boot maxwen kernel on cfxe, at least it does with cfxe ramdisk
test it out and tell how it wents
Click to expand...
Click to collapse
need to take a look at your ramdisk
if something special is required I can provide prebuilts with your ramdisk
Sent from my Find 5 using xda app-developers app
mavaee said:
I do have some random reboots after +-10 minutes with this ROM. Can I provide you a logcat Anders?
Click to expand...
Click to collapse
are you on the default kernel in this rom , and did a full wipe ?
Sure you can make a logcat , paste it via here
you can also submit a bug : here but please add log also
have not had a single random reboot at all, so its a bit wierd
anders3408 said:
are you on the default kernel in this rom , and did a full wipe ?
Sure you can make a logcat , paste it via here
you can also submit a bug : here but please add log also
have not had a single random reboot at all, so its a bit wierd
Click to expand...
Click to collapse
Yes I used the default kernel and coming from CM10.1 with a full wipe. I have to say I didn't experienced a reboot after all this afternoon so maybe it was just the ROM settling down.
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
Logcat:
http://logcat.scheffsblend.com/view?id=285002
mavaee said:
Yes I used the default kernel and coming from CM10.1 with a full wipe. I have to say I didn't experienced a reboot after all this afternoon so maybe it was just the ROM settling down.
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
Logcat:
http://logcat.scheffsblend.com/view?id=285002
Click to expand...
Click to collapse
What happens when you made that logcat? I'm not seeing any reboots? Hopefully you won't see such reboot again.
Sent from my Find 5 using XDA Premium HD app
Nice ROM.
Voice to text isn't functioning... I was going to try the app install from the Slim ROM site, but I know that doesn't work with the CM kernel. I know it works with Max's.
Anyway, other than that it's been stable for me. Wifi tethering worked, Battery seemed good for only running it 24 hrs or so.
charlatan01 said:
Nice ROM.
Voice to text isn't functioning... I was going to try the app install from the Slim ROM site, but I know that doesn't work with the CM kernel. I know it works with Max's.
Anyway, other than that it's been stable for me. Wifi tethering worked, Battery seemed good for only running it 24 hrs or so.
Click to expand...
Click to collapse
Its also using the CM's kernel. Can you send me a link to that app and I'll have a look.
Sent from my Find 5 using XDA Premium HD app
^ sure thing. Src install is found (thanks to the folks at Slim!) here
Related
Just like king23adrianc's CM7 Kang thread, here's one for CM9 Kangs.
Kangs are unofficial Cyanogen builds built by members of the community. They're not supported by the CM team at all, and in many cases aren't supported by the person who cooked the kang.
Kangs can contain features (cherry picks) that haven't been committed into the official nightlies, so you get some pretty cool cutting-edge features that aren't in the official rom. Sometimes these features get built-in to the official CM roms, sometimes they don't.
If you're not familiar with flashing roms, this probably isn't the place for you. Read up on it a bit, make yourself familiar with what you're doing and ALWAYS make a backup of your rom, in case something goes wrong.
For the latest kangs, start at the end of the thread.
To start, here's a link to the euroskank kangs for CM9:
http://fitsnugly.euroskank.com/skankwich/?id=crespo
Sweet! Lets get it started..
Here's a CM9 (alpha) kang I just compiled @ 6pm PST 11/29/11.
No Cherry Pick: Download (deleted)
Cherry pick version: Download (deleted)
-Dialer Landscape Mode
-Preferences: initial Preferences Activity, Provider and XML
-v3 RIL: another getDataCallState fix
-Revert "Bug 5003361: No Android Dreams in Settings / Display"
I appreciate those who make them without cherry picks. Thanks a lot
Also don't forget everyone that you need to fix super user after every flash and should also flash gapps everytime for the time being.
Sent from my Nexus S using xda premium
Any chance of an NS4G version?
Sent from my Nexus S 4G using xda premium
xsteven77x said:
I appreciate those who make them without cherry picks. Thanks a lot
Also don't forget everyone that you need to fix super user after every flash and should also flash gapps everytime for the time being.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
What about SU needs fixing each time?
sixstringsg said:
What about SU needs fixing each time?
Click to expand...
Click to collapse
I haven't noticed any SU problems with any ICS build.
EDIT: Brenix, nice tease on the launcher preferences. Functional or not I like having it.
tehgeekguy said:
Just like king23adrianc's CM7 Kang thread, here's one for CM9 Kangs.
Kangs are unofficial Cyanogen builds built by members of the community. They're not supported by the CM team at all, and in many cases aren't supported by the person who cooked the kang.
Kangs can contain features (cherry picks) that haven't been committed into the official nightlies, so you get some pretty cool cutting-edge features that aren't in the official rom. Sometimes these features get built-in to the official CM roms, sometimes they don't.
If you're not familiar with flashing roms, this probably isn't the place for you. Read up on it a bit, make yourself familiar with what you're doing and ALWAYS make a backup of your rom, in case something goes wrong.
For the latest kangs, start at the end of the thread.
To start, here's a link to the euroskank kangs for CM9 for the Nexus S (not 4G):
http://fitsnugly.euroskank.com/sammich/crespo/
Click to expand...
Click to collapse
thank you
---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------
xsteven77x said:
I appreciate those who make them without cherry picks. Thanks a lot
Also don't forget everyone that you need to fix super user after every flash and should also flash gapps everytime for the time being.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
have you updated your superuser app?
irishrally said:
EDIT: Brenix, nice tease on the launcher preferences. Functional or not I like having it.
Click to expand...
Click to collapse
I noticed that too.. I believe it came from one of the cherry picks or commits.. not fully there yet..heh its definitely bleeding edge
Sent from my Nexus S using XDA App
brenix said:
I noticed that too.. I believe it came from one of the cherry picks or commits.. not fully there yet..heh its definitely bleeding edge
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
thanks for these kangs, i'll try today. Coming from Fitsnugly or Gearhead one, do i need to wipe all ?
kptnk said:
thanks for these kangs, i'll try today. Coming from Fitsnugly or Gearhead one, do i need to wipe all ?
Click to expand...
Click to collapse
Usually you won't have to wipe, since it's the same base. It never hurts though.
brenix said:
Sweet! Lets get it started..
Here's a CM9 (alpha) kang I just compiled @ 6pm PST 11/29/11.
No Cherry Pick: Download
Cherry pick version: Download
-Dialer Landscape Mode
-Preferences: initial Preferences Activity, Provider and XML
-v3 RIL: another getDataCallState fix
-Revert "Bug 5003361: No Android Dreams in Settings / Display"
Click to expand...
Click to collapse
Every time you reboot it says formatting SD card in the notification bar. Was I glad when I figured out that that message is wrong LOL.
brenix said:
Sweet! Lets get it started..
Here's a CM9 (alpha) kang I just compiled @ 6pm PST 11/29/11.
No Cherry Pick: Download
Cherry pick version: Download
-Dialer Landscape Mode
-Preferences: initial Preferences Activity, Provider and XML
-v3 RIL: another getDataCallState fix
-Revert "Bug 5003361: No Android Dreams in Settings / Display"
Click to expand...
Click to collapse
Does anyone have a mirror of the cherry pick ROM? I've tried downloading it four times this morning, and it has failed at around 90% each time
Sent from my Nexus S
Thanks for CM9 KANG thread
The most urgent CherryPicks, just my thought (CM7s have these)
- /system/etc/init.d/ for custom scripts
- status bar widget (power control widget)
btw KANG, abbreviation for what?
sixstringsg said:
What about SU needs fixing each time?
Click to expand...
Click to collapse
If you click on the actual super user app it will force close until you remove it and download the one from the market. You can use root apps if you dont want to do all that but you can't click the super user app itself.
Sent from my Nexus S using xda premium
Works for me, I always disable notification on install
xsteven77x said:
If you click on the actual super user app it will force close until you remove it and download the one from the market. You can use root apps if you dont want to do all that but you can't click the super user app itself.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
New version
@fitsnugly: #euroskank #sammich Crespo 11302011-0905 http://goo.gl/31YPz
Shared via TweetCaster
Can you guys tell me how is this rom?
I use koushik cm9 11.
Wifi? 3g/2g? mms? calendar sync? data usage? thetering? google talk video?
What else...
Is it smooth? What about cherry picks?
Whats the difference?
Why there is nothing in nexus s android dev forum? (many persons tell this rom is great)
What about the UI? Stock ICS? Launcher? Stock?
Sorry for asking u so many questions but I couldnt find anything
Thanx
what i've noticed about the euroskank builds so far:
CM power button options (screenshot, reboot recovery, ect).
Data usage seems broken, at least with the stock kernel. edit: kernel related, flashed different one and fixed.
I use the latest, seemingly unrleased gapps from http://download.clockworkmod.com/test/gapps-ics-20111128.zip
I delete the Maps.apk from the gapps zip before flashing so I can install latest from market (or else you will be stuck with old version and wont be able to upgrade).
edit: rename or delete superuser.apk in /system/app/ and download from market. the one included in the rom forcecloses. No reboots necessary.
Ns4g???
Sent from my Nexus S 4G using xda premium
I've noticed each kang/release is getting smaller and smaller. I remember we started out at around 175mb.
Anyone know what's going on? Lots of code cleanup, duplicates being deleted maybe?
Just curious....
This thread is for discussing aosp roms, like Slim, Carbon, etc. except for CM though since it has its own thread. This is meant to keep the unhelping chit-chatter out of the development threads where bug reports best reside. When posting here, clarify what aosp rom you're on. Do not post bug reports here, post them in their respective development threads!
One more thing! While this thread progresses, use search and/or read the faq to see if your question has already been posted before, to avoid repetitiveness and us older lads becoming grumpy.
F.A.Q: (frequently asked questions)
I would like to dualboot, what should I do?
Flash siyah kernel
Help! I flashed siyah and now my rom doesn't boot!
It's because whatever rom you use has a newer mali driver which most kernels aren't updated for. Especially siyah which hasn't seen some dev love in ages.
What rom should I flash?
We don't know, you have to try them out yourself!
What's gapps, and is this inside xx rom?
Gapps is short for google apps, which is the Play store and some other apps you sorely need. Go too http://goo.im/gapps and download the gapps package for whatever version you have. Newer aosp roms are most certainly 4.2.2. Some roms, like Slim, have their own separate gapps packages specially made for those roms. In those cases, the standard gapps from goo.im will not work!
Help! I flashed xx rom but now it doesn't boot!
Try making a factory reset in the recovery and reflash whatever rom you were on. Also, in most cases, CWM works better for rom installations. Twrp craps out for unknown reasons.
Help! I wiped data and reflashed the rom but it still doesn't boot!
That sounds like a rom issue. Try flashing an earlier version of the rom.
Help! Something screwed up and now my phone doesn't boot anymore!
Well, reboot into recovery and see if a reflash helps. It is always recommended to regularly keep your system backed up in case something nasty happens. Perform a nandroid backup every once in a while.
What is a nandroid backup?
It's like a screenshot of your current state which you can return to if something bad happens. A nandroid backup backs up the system, boot (kernel) and data and, if specified/selectable, it also backs up cache and recovery. Maybe even efs (in twrp). However, it doesn't back up the modem!
I flashed xx kernel and I now get a black screen upon reboot!
That is because the rom you flashed has the new mali driver from the 4.2.1 leak and the kernel you flashed isn't updated with this driver. Stay on the provided kernel for now.
Thanks to:
I forgot to give thanks where due, and I'm so sorry for that. If I got an advice from you, hit me up and your name goes on this list.
C_tho; for mentioning the mali driver stuff.
Noble Sir Slaphead20; for suggesting I'd maintain an FAQ and suggesting I'd make an entry covering gapps.
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Re: Aosp roms discussion thread.
kevinarjun said:
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Click to expand...
Click to collapse
Nope, only siyah
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
@Theshawty....maybe as the thread develops you can add a FAQ?
kevinarjun said:
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Click to expand...
Click to collapse
Only Siyah, and Siyah only supports the older aosp roms.
Speaking of aosp, I just had an urge to flash Carbon. Think I'll do it, because I'm a bit bored of running touchwiz and I've run CM for so long I need change. I didn't like RootBox that much (too many settings, lol. I like a "leaner" setup) and there's no official aokp for our device. I also didn't like Slim, so I'll give Carbon another go.
slaphead20 said:
Nope, only siyah
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
@Theshawty....maybe as the thread develops you can add a FAQ?
Click to expand...
Click to collapse
Yeah, I had in mind to add a smaller faq.
would suggest you also try JellyBam...
kevinarjun said:
would suggest you also try JellyBam...
Click to expand...
Click to collapse
not gonna happen
jellybam isnt a welcome rom here
kevinarjun said:
would suggest you also try JellyBam...
Click to expand...
Click to collapse
DSA said:
not gonna happen
jellybam isnt a welcome rom here
Click to expand...
Click to collapse
What DSA said. We do not welcome JellyBam here anymore because the developer broke a lot of rules of XDA. Plagiarism and violating the gpl, amongst others.
----------
I updated the op with a small faq. More to come in the following days.
In the Faqs it might be worth mentioning in the gapps bit that some Roms ie slim, have their own gapps, and others won't work
Just flashed Carbon 1.5, not regretting it thus far! This ROM gives the word buttery smooth a whole new meaning!
Sent from my GT-I9300 using Tapatalk 2
Not sure this goes here, but ill give it a go anyways.
In the Slimbean thread there was a lot of talk about mali drivers. Now could someone please give me some info on the matter cause seems like I missed something.
Basicly what im wondering is whats up with the mali drivers and why do I want them?
Sorry if this is off-topic or has been answered somewhere else.
Sent from my GT-I9300 using Tapatalk HD
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
Slim is definitely worth a go as well
slaphead20 said:
Slim is definitely worth a go as well
Click to expand...
Click to collapse
Agreed, running it now with no problems.
Carbon is nice as well..
Sent from my GT-I9300 using xda app-developers app
Jns said:
Not sure this goes here, but ill give it a go anyways.
In the Slimbean thread there was a lot of talk about mali drivers. Now could someone please give me some info on the matter cause seems like I missed something.
Basicly what im wondering is whats up with the mali drivers and why do I want them?
Sorry if this is off-topic or has been answered somewhere else.
Sent from my GT-I9300 using Tapatalk HD
Click to expand...
Click to collapse
They fix the graphics glitches and completely without memory leaks.
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
I think you should give Carbon a try, it's THE definition of buttery smooth and come with some neat customization.
Sent from my GT-I9300 using Tapatalk 2
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
The only problem with SuperNexus is it is updated very slowly. Also Faryaab has exams to do now, so it will not get updated at least until he is done with them.
If you want a super light rom I would reccomend SlimBean it's fast, and light, battery is acceptable, and it's easy to change settings like screen density and navbar settings without having to edit build.prop and decompile framework-res.apk, which you will have to do on SuperNexus.
what about the smoothness of it?
Another one there to vouch for Carbon, running it on both phone and tablet
Sent from my Nexus 7 using xda app-developers app
I love AOSP Roms and thank you for starting this thread. Unfortunately I am afraid that I can't use such Roms as a daily driver because of the camera problems. Bluetooth also seems to be a problem for some users.
Guys I am facing Memory leak problem with the Slim bean 4.2.2.....is it normal? cant seems to find any solution....
you'd be better off asking in the slim thread
Hi!
So, recently, I've noticed that CyanogenMod (CM) has adopted CodeAuroraForum (CAF) code, which is causing incompatibilities with AndroidOpenSourceProject (AOSP) code.
Problem #1:
Also, one of the common problems due to this is that flashing custom kernels (AOSP based), leads to color-display problems.
To fix this, a colorfix.zip has been provided by someone in the AOKP thread.
Also, there is poll in the AOKP website, about a shift to CAF code.
Now, AFAIK, this overwrites "liboverlay.so", in /lib. If this is all that need to be done to fix it, then how is a code problem?
Does this file have to be updated? What exactly does this file do?
What are the other problems associated with CAF code adoption?
Please contribute your opinions and list any other problems.
not happy with CAF.. stop using cm. there are plenty of better roms out there for you to choose from.
Agrees cm has gone to the poop house now.
Sent from my Nexus 4 using XDA Premium 4 mobile app
arvindch said:
Hi!
So, recently, I've noticed that CyanogenMod (CM) has adopted CodeAuroraForum (CAF) code, which is causing incompatibilities with AndroidOpenSourceProject (AOSP) code.
Problem #1:
Also, one of the common problems due to this is that flashing custom kernels (AOSP based), leads to color-display problems.
To fix this, a colorfix.zip has been provided by someone in the AOKP thread.
Also, there is poll in the AOKP website, about a shift to CAF code.
Now, AFAIK, this overwrites "liboverlay.so", in /lib. If this is all that need to be done to fix it, then how is a code problem?
Does this file have to be updated? What exactly does this file do?
What are the other problems associated with CAF code adoption?
Please contribute your opinions and list any other problems.
Click to expand...
Click to collapse
The issue with liboverlay.so is code incompatibilty between the ASOP source (custom kernels) with CM ROM using the CAF driver blobs. It's like a Chinese person speaking Chinese to an English only speaker. The fix is replacing the liboverlay.so with the ASOP liboverlay.so and back out that portion of the CAF. It's not a long term solution because it may cause other problems down the road.
There are some advantages using CAF, but it cause a divergence in kernels for the custom ROMs which may not be a good idea and causes maintainance headaches for the open source dev. For now lets just see what CM does with CAF.
Sent from my Nexus 4 using xda app-developers app
simms22 said:
not happy with CAF.. stop using cm. there are plenty of better roms out there for you to choose from.
Click to expand...
Click to collapse
kthejoker20 said:
Agrees cm has gone to the poop house now.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I agree that a solution is not using CM and CM-based ROMs. :|
However, I've started this thread to compile a list of problems that CAF code is causing and possible fixes, and to discuss the outcome of CAF code usage.
AtrixShan said:
The issue with liboverlay.so is code incompatibilty between the ASOP source (custom kernels) with CM ROM using the CAF driver blobs. It's like a Chinese person speaking Chinese to an English only speaker. The fix is replacing the liboverlay.so with the ASOP liboverlay.so and back out that portion of the CAF. It's not a long term solution because it may cause other problems down the road.
There are some advantages using CAF, but it cause a divergence in kernels for the custom ROMs which may not be a good idea and causes maintainance headaches for the open source dev. For now lets just see what CM does with CAF.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What are the advantages to CAF code usage?
I read somewhere that Qualcomm contributes better, optimized code to the CAF, and hence, performance/quality may be better than AOSP. I don't have the source link, though.
Any ideas?
arvindch said:
What are the advantages to CAF code usage?
I read somewhere that Qualcomm contributes better, optimized code to the CAF, and hence, performance/quality may be better than AOSP. I don't have the source link, though.
Any ideas?
Click to expand...
Click to collapse
That's what I read, too. It's hard to say for now because I don't think CM is done with their CAF implementation. Let wait and see. The bottom line for me is using what works well on my Nexus 4. The headaches for the open source community does suck though. I used faux kernel since my first smart phone (Atrix 4g)
Sent from my Nexus 4 using xda app-developers app
AtrixShan said:
That's what I read, too. It's hard to say for now because I don't think CM is done with their CAF implementation. Let wait and see. The bottom line for me is using what works well on my Nexus 4. The headaches for the open source community does suck though. I used faux kernel since my first smart phone (Atrix 4g)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hmmm.
Same here - I've been using Franco.kernel since forever - I even bought the FKU pro app. It's giving me great performance and battery-life.
I don't want to stop using it! However, the features offered by SlimBean are too useful for me to ignore, as well.
Hence, if SB adopts the CAF code CM is using, since SB is based off CM, then I will have an extremely hard decision to make.
Not sure if anyone's noticed but you should check out your dmesg if reverting to an earlier liboverlay.so. I didn't notice any drastic changes in performance / battery life as a result, but that's not something I'm thrilled with.
For the time being, I've made some test builds with the two YCBYCR commits (from Oct 1)
It's based on Franco's r191.
The zips include the full OTG patch (kernel + ramdisk + ROM-side changes), but if you don't want the ramdisk/ROM-side features, just flash the boot.img or strip out the (non-)relevant parts from updater-script. It will still have the "otg code" in the kernel, but it shouldn't be something that'd affect usage at all.
4.3: 2013.10.13 0401ET r191: [JWR] [JSS/JLS]
Again, these have the two relevant commits cherry-picked and will require the recent liboverlay.so.
Just a temporary solution. I am curious though about how many other ROMs are affected by this-- CM forks. If say all new JLS/JSS ROMs require this, I might as well just keep on cherry-picking since that's the entire userbase practically. Obviously JWR will be a much tougher one.
ziddey said:
Not sure if anyone's noticed but you should check out your dmesg if reverting to an earlier liboverlay.so. I didn't notice any drastic changes in performance / battery life as a result, but that's not something I'm thrilled with.
For the time being, I've made some test builds with the two YCBYCR commits (from Oct 1)
It's based on Franco's r191.
The zips include the full OTG patch (kernel + ramdisk + ROM-side changes), but if you don't want the ramdisk/ROM-side features, just flash the boot.img or strip out the (non-)relevant parts from updater-script. It will still have the "otg code" in the kernel, but it shouldn't be something that'd affect usage at all.
4.3: 2013.10.13 0401ET r191: [JWR] [JSS/JLS]
Again, these have the two relevant commits cherry-picked and will require the recent liboverlay.so.
Just a temporary solution. I am curious though about how many other ROMs are affected by this-- CM forks. If say all new JLS/JSS ROMs require this, I might as well just keep on cherry-picking since that's the entire userbase practically. Obviously JWR will be a much tougher one.
Click to expand...
Click to collapse
This seems useful! :good:
Is this a patched franco kernel that works on CAF roms?
Could you clarify what this does? I'm sorta confused by all this.
from wat i know.. JSS faster than jwr but aosp jss has deadlock issues.. and caf solves deadlock issue..
Andre_Vitto said:
from wat i know.. JSS faster than jwr but aosp jss has deadlock issues.. and caf solves deadlock issue..
Click to expand...
Click to collapse
Really? I didn't know that. OK. One advantage then.
arvindch said:
Really? I didn't know that. OK. One advantage then.
Click to expand...
Click to collapse
JSS is a dev branch and has some GPU optimizations
== Sent from my CarbonMako ?? ==
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
I have decided to quit CM as well due to their dumb decision about CAF
Now using Carbon ROM and to be honest it is non-bull**** one, packed with useful features, with wide group of fans and still developing for loads of devices
== Sent from my CarbonMako ?? ==
MaxFTW said:
\
[/COLOR]I have decided to quit CM as well due to their dumb decision about CAF
Now using Carbon ROM and to be honest it is non-bull**** one, packed with useful features, with wide group of fans and still developing for loads of devices
== Sent from my CarbonMako ?? ==
Click to expand...
Click to collapse
Hard to find stable roms on 4.3 these days.. PA is down the drain.. no update since a month.. too less features.. AOKP wont boot up for most ppl.. PAC is inherently unstable. I'm currently stock rooted.. seems like the most stable for me now..
AOKP nightly boot find for me, and I assume most other N4 have the same hardware as I do. "Official" AOKP don't put out nightlies that can't boot. People just need to not flash incompatible kernels and know what they're doing.
MaxFTW said:
JSS is a dev branch and has some GPU optimizations
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
[/COLOR]I have decided to quit CM as well due to their dumb decision about CAF
Now using Carbon ROM and to be honest it is non-bull**** one, packed with useful features, with wide group of fans and still developing for loads of devices
Click to expand...
Click to collapse
Slimbean is also based off CM code and I love Slimbean's feature set.
Luckily they haven't merged CAF changes YET. :fingers-crossed:
I'm also testing crDroid, since I like Halo; however, they're based right off CM 10.2, so I need to flash colorfix.zip to get it working with Franco.kernel.
Andre_Vitto said:
Hard to find stable roms on 4.3 these days.. PA is down the drain.. no update since a month.. too less features.. AOKP wont boot up for most ppl.. PAC is inherently unstable. I'm currently stock rooted.. seems like the most stable for me now..
Click to expand...
Click to collapse
eksasol said:
AOKP nightly boot find for me, and I assume most other N4 have the same hardware as I do. "Official" AOKP don't put out nightlies that can't boot. People just need to not flash incompatible kernels and know what they're doing.
Click to expand...
Click to collapse
Hmm.
I've never tried 'pure AOKP'. I've use ROMs which kang stuff from AOKP sources though. Same goes for CM - I've never used pure CM. I love using hybrid ROMs - Best of all worlds!
I agree. Sadly, PA is stuck on an RC2 since a month.
I read that they're waiting for 4.4 to drop, but IMO, atleast they could release another RC in the meanwhile, to fix bugs.
Some ROMs have merged all the latest Halo commits and have fixed some bugs I encountered on PA 3.99RC2, so I'm using them (hybrid ROMs) instead.
OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?
So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!
I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?
i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app
Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So now I share with oneplus 3. After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.15.1
Optimized Build with custom toolchain on ROM and Kernel
Proguard 5.3
Snapdragon Camera
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
As you might know, all credits go to CyanogenMod Team.
ROM:
Source Code
kernel:
https://github.com/CyanogenMod/android_kernel_oneplus_msm8996
If you like my work, please consider a donation.
Thank you very much man 5 stars from me.
@jgcaap
Is there f2fs support in the kernel?
And have considered adding any of @arter97 fixes and improvements from his cm13 kernel
Thanks for your work
jgcaap said:
Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So now I share with oneplus 3. After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.15.1
Optimized Build with custom toolchain on ROM and Kernel
Proguard 5.3
Snapdragon Camera
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
As you might know, all credits go to CyanogenMod Team.
ROM:
Source Code
kernel:
https://github.com/CyanogenMod/android_kernel_oneplus_msm8996
If you like my work, please consider a donation.
Click to expand...
Click to collapse
How I missed you... I was a fan on OPO, and definitely on OP3.... ROM working flawlessly, no FC's, smooth and fast, pixelfy, magisk and pokemon go working great... Awesome isn't enough to describe you...
BBuZZ said:
How I missed you... I was a fan on OPO, and definitely on OP3.... ROM working flawlessly, no FC's, smooth and fast, pixelfy, magisk and pokemon go working great... Awesome isn't enough to describe you...
Click to expand...
Click to collapse
Plz dont quote the whole thread
Loved your builds on oneplus one when I was using it for month.
I will try soon.
Between stock cm from 13 till now, having strange bug fp scanner, sometimes fp sensor stop working, we need manually turn on screen.
If same happens, I will report back.
Also same was in stock cm13 but not happening in @Sultanxda rom.
also, this is not happening in aosp based roms, so its deep in cm.
.
thanks,
Jgcaap has always been my inspiration , and one of the reasons I optimize my ROMs heavily . Gonna surely give this a try , bud
Hey its good to see
flashed it yeah
ROM Flashing steps please..
Opengapps should be OK? The Gapps link in AFH in the OP post #1 doesn't seem to be a valid link.
Also FW version recommended? 3.5.5?
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
hrishikeshgramani said:
ROM Flashing steps please..
Click to expand...
Click to collapse
Will be same as any other CM14 ROM, do give a try!
Open gapps are ok use nano or pico 7.1
http://opengapps.org/
Original CM 14.1 is 586.22 MB why yours is 673.1 MB, instead of slimming it; what have you added?
Sent from my Pixel XL using XDA-Developers mobile app
oriveradel said:
Original CM 14.1 is 586.22 MB why yours is 673.1 MB, instead of slimming it; what have you added?
Click to expand...
Click to collapse
Just try it you won't be disappointed
I am dissecting it need to know what was added
Sent from my Pixel XL using XDA-Developers mobile app
oriveradel said:
I am dissecting it need to know what was added
Click to expand...
Click to collapse
ROM is odexed that's why it has bigger size + many more optimizations for speed and battery
RohanAJoshi said:
Loved your builds on oneplus one when I was using it for month.
I will try soon.
Between stock cm from 13 till now, having strange bug fp scanner, sometimes fp sensor stop working, we need manually turn on screen.
If same happens, I will report back.
Also same was in stock cm13 but not happening in @Sultanxda rom.
also, this is not happening in aosp based roms, so its deep in cm.
.
thanks,
Click to expand...
Click to collapse
@jgcaap : as mentioned earlier, there is same but in your rom also.
Fingerprint sensor stops working some time, need to wake screen manually.
Also, torch gesture not working.
Please fix these issues.
Nothing happen when switching profiles by built-in button. Any idea how to fix that? I trying to change in settings few options but without solution.
Used your ROMs on the OPO.
Everything working great for now apart from the known CM bugs. FPS fails sometimes and alert slider not working?
racesupport said:
Nothing happen when switching profiles by built-in button. Any idea how to fix that? I trying to change in settings few options but without solution.
Click to expand...
Click to collapse
Use notification slider APP from playstore, as a tempory workaround
Mine is working. After few reboot, it was alive.
So for now, the only bug is cm bug I think ( battery icon cannot be changed )