UNOFFICIAL AOKP Nightly Builds​
Since AOKP development has started picking up with their addition of their new Gerrit server, I've decided to release nightly builds for AOKP. These should be released every day anywhere from 6-9pm depending on when I get time to do it. Also, some days I might not get the time. However, it should be almost every day that a new build comes out.
All credits go toward the entire AOKP team for their efforts in making one of the most customizable builds out there right now. It is absolutely fantastic.
You can download it by sorting by date uploaded right here on my goo.im profile:
http://goo.im/devs/rohan/tenderloin/aokp_nightlies
Note: These downloads are provided untested. This might break your system so be sure to keep a backup handy. Nightly builds are usually more unstable than any other type of ROM, but if you want the latest features then use this. I do not take responsibility for anything that may happen to your system.
Another note: These downloads do not come with any sort of support. Do not ask for help in IRC for aokp if you are running these nightlies. They are not official and thus are not officially supported. So don't go and give roman and the other devs a headache
And another note: They don't come with gapps, download those separately from goo.im or some other source.
You should just be able to download and install the zip in CWM, then wipe caches. Reboot and enjoy. No other wiping is needed, only caches.
Right now I am building on my personal PC (I don't have a server) so I apologize if it takes a while to get builds up! My system isn't the fastest at making builds haha
I will be making these ROMs updateable via the goo.im app probably this weekend, I don't have much time right now to figure out how it works.
If you want to find out when I release the new nightly, follow me on twitter: http://twitter.com/rohanXm
Looking forward to it!
Is there a changelog like the CM nightlies?
What exactly is aokp?
Ventus_zx said:
What exactly is aokp?
Click to expand...
Click to collapse
http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
AOKP is pretty awesome. I run it on my Epic 4G and I agree it's more customizeable than CM9 and pretty solid in terms of reliability . Thanks for these Touchpad Nightlies Rohan! Installing it as we speak!
Nburnes said:
Is there a changelog like the CM nightlies?
Click to expand...
Click to collapse
You can find what was merged here:
http://gerrit.sudoservers.com:8080/#/q/status:merged,n,z
It will display some other device stuff, though most AOKP stuff from that gerrit is for the entire AOKP as a whole and not device specific.
Can I flash the cm nightly 120 dpi patch or will it break things?
rsalinas1 said:
Can I flash the cm nightly 120 dpi patch or will it break things?
Click to expand...
Click to collapse
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.
rohan32 said:
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.
Click to expand...
Click to collapse
I just changed it under general ui with rom control settings. Thanks though, its very smooth so far.
Anybody else get a System UI has closed error. Weird, hopefully it was a one time thing. Flashing the 4/20 now. Hopefully that fixes it, I did a full wipe and will wipe again
Sent from my aokp_tenderloin using XDA
SUPREME Mods v1.5
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
I would assume that the nighties don't use either of those things.
Nabobalis said:
I would assume that the nighties don't use either of those things.
Click to expand...
Click to collapse
OK thanks, just asked as both are by rohan32, will try with and without to see if any difference.
BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.
rohan32 said:
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.
Click to expand...
Click to collapse
The Supreme mods work fine but the xenon kernel broke my wifi (not had any wifi issues on any build) so back to cyanogen kernel and everything is working
The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!
is this wifi driver included in the nightlys?
http://review.cyanogenmod.com/#/c/15570/
matteebee said:
The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!
Click to expand...
Click to collapse
I tried both the 05/07 and 05/08 AOKP nightlies and the screen off/sound bug is still there just like any other ROM I have tried. Are you sure that you have the volume turned up enough?
can has new build?
Related
maxdamage2122 has set up a buildbot and will be making nightlies. I haven't had the time to read the sticky for cm7 nightlies for a few days, and am glad I did. My builds will be discontinued so that we don't have a plethora of threads with different builds.
Here is the page with maxdamage2122's statement: http://forum.xda-developers.com/showthread.php?t=1064775&page=30
Mods, please close this thread so that the real rom dev threads get bumped up.
changelog
NOTE: Flash Gapps afterward for market,gmail,etc.
Known bug(s):
--dsp manager fc erratically
----FIX: settings->applications->manage applications->all->dsp manager->clear data will stop the fc (thanks dodo99x!)
Release 6-21-11
-repo sync @~7:10 P.M Pacififc
-should include all changes up to: Add vivo (HTC Incredible S) support (android_vendor_cyanogen) (Not for our device, just stating last item in changelog)
-Download Link: http://www.multiupload.com/8PL7BUOEII
Release 6-20-11:
Should include all changes up to:
Workaround for blackscreen after unlock with electron beam. (android_frameworks_base)
from http://cm-nightlies.appspot.com/?device=harmony
Link: http://www.multiupload.com/GHIXTGU1D8
Release 6-19-11:
Should include all changes up to:
libaudio: Add missing GB function (android_hardware_msm7k)
from http://cm-nightlies.appspot.com/?device=harmony
Just flashed....thanks
Sent from my GTablet using XDA Premium App
Whats the difference between nightly and stable?
TheMuffStuff said:
Whats the difference between nightly and stable?
Click to expand...
Click to collapse
Generally, when a release has been tested thoroughly and shows no signs of having any major bugs(e.g. camera not working, no touchscreen interaction) it is considered stable and usable as a daily driver for most people. The nightly builds of CM7 are considered unstable, because as new features are added on a daily basis, there is a possibility that those features/corrections may break some functionality in the device. This is not always the case, but it can happen.
This build seems pretty stable to me at least. Have at it and tell me/everyone what you think.
Issues?
Anyone test this out yet? Are there still issues with camera res, etc? How about Netflix playback?
thanks.
will you keep building?
tjsooley said:
thanks.
will you keep building?
Click to expand...
Click to collapse
I'd like to. I'm going on vacation in a few days, so after Wednesday I may not do a build for a week. Until then I'm planning on doing a release every night, contrary to what I stated in the OP. I'm not one for thorough testing/debugging/fixing though, so I will not attempt to patch/add anything to these releases other than what a nightly repo sync adds.
ubufugu said:
Release 6-20-11:
Should include all changes up to:
Workaround for blackscreen after unlock with electron beam. (android_frameworks_base)
from http://cm-nightlies.appspot.com/?device=harmony
Link: http://www.multiupload.com/GHIXTGU1D8
-Severe Bug: DSP manager force closes at erratic inervals. Not sure if it's just me or this build.
--FIX: uninstall with titanium backup, take dsp manager from previous nightly and place it in /system/app with proper permissions and reboot.
Release 6-19-11:
Should include all changes up to:
libaudio: Add missing GB function (android_hardware_msm7k)
from http://cm-nightlies.appspot.com/?device=harmony
NOTE: Flash Gapps afterward for market,gmail,etc.
Click to expand...
Click to collapse
The nightly list for Harmony is huge; however they do not seem to be packaging up for release like the other devices... anyone know why or when the harmony nightly will be packaged up and released (it has been almost a month since the last nightly was released!) ?
GTablet said:
The nightly list for Harmony is huge; however they do not seem to be packaging up for release like the other devices... anyone know why or when the harmony nightly will be packaged up and released (it has been almost a month since the last nightly was released!) ?
Click to expand...
Click to collapse
Start reading about 3/4 down: http://forum.cyanogenmod.com/topic/20070-cm7-discussion-of-nightlies/page__st__60
essentially(at least as far as I understand) The Gtablet build was renamed from harmony to smb_a1002 under the malata name/platform. This broke the buildbot for us for the nightlies, which has not been fixed yet. I have not yet seen an eta on when nightlies for us will be up again.
ubufugu said:
Start reading about 3/4 down: http://forum.cyanogenmod.com/topic/20070-cm7-discussion-of-nightlies/page__st__60
essentially(at least as far as I understand) The Gtablet build was renamed from harmony to smb_a1002 under the malata name/platform. This broke the buildbot for us for the nightlies, which has not been fixed yet. I have not yet seen an eta on when nightlies for us will be up again.
Click to expand...
Click to collapse
ubufugu,
Thank you for the reply and link; both were VERY helpful !!!
Rick
GTablet said:
ubufugu,
Thank you for the reply and link; both were VERY helpful !!!
Rick
Click to expand...
Click to collapse
Damn it, they need to get the quote and thanks button away from each other. I guess you got a free thanks there GTablet.
Well, was quoting to say same from me, I was going through nightly withdrawals.
Cyanogenmod official nightlies have started so im creating a thread so that we can try out the new nightlies and discuss what is new and what problems we have and help each other out
WHAT IS CYANOGENMOD : http://wiki.cyanogenmod.com/index.php?title=Main_Page
At the moment this is only for GSM only hopefully cyanogenmod will support CDMA soon
These are the new nighties
DOWNLOAD : http://download.cyanogenmod.com/?typ...ly&device=zeus
MD5Sum : check the md5 under the files named associate with your build version before flashing it
And here are the gapps and new Gtalk app
GOOGLE ADDON :http://forum.cyanogenmod.com/topic/3...2-24-oct-2011/
USEFUL : http://wiki.cyanogenmod.com/wiki/Barebones clean your rom to make space
CHANGELOG : What's new in this version :http://cm-nightlies.appspot.com/?device=zeus
Any problems flashing this rom WIPE ALL and try again.
UPDATE CHECK THE NIGHTLY CHANGELOG ICS BEING MERGED
This thread has been moved from Development forum because DooMLoRD shouted at me
can you give us an introduction to what it is?
garner said:
USEFUL : http://wiki.cyanogenmod.com/wiki/Barebonesclean your rom to make space
Click to expand...
Click to collapse
Typo: should be:
USEFUL : http://wiki.cyanogenmod.com/wiki/Barebones clean your rom to make space
LiveWallpapers should be fixed in the next nightly. Looks like they were removed by mistake:
zeus: added missing LiveWalpappers
on prop layout change we accidentaly removed them so now we enable them again
Click to expand...
Click to collapse
http://cm-nightlies.appspot.com/?device=zeus
fxp046 brings vibration, bluetooth and wifi back
could someone that's has updated should say something? camera stills hangs?
I'm using 046 with doomkernel right now and its running great! Everything works the only thing I've noticed is that when you turn on bluetooth with wifi it just errors out so it'll probably be fixed when doom releases a new kernel
Sent from my R800i using XDA App
thatsupnow said:
I'm using 046 with doomkernel right now and its running great! Everything works the only thing I've noticed is that when you turn on bluetooth with wifi it just errors out so it'll probably be fixed when doom releases a new kernel
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Yes the bt problem is known about he is making a new kernel to fix the issus im just wanting to get a fix on the touch pads then ill be as happy as a pig in sh*t
http://forum.xda-developers.com/showpost.php?p=19376992&postcount=41
Has anyone flashed 046 with the original kernel? does touchpads work ie dead space etc???
I did a first time install of 7.2.0 yesterday using the supplied kernel (as Doomlord is stil working on an optimal one). I'll report back with findings once an update to that is released.
The latest nightly changelog suggests ICS is st starting to be merged
Okay but what does it exacty mean? I mean in the changelog.
Sent from my R800i using XDA App
IE-coRe said:
Okay but what does it exacty mean? I mean in the changelog.
Sent from my R800i using XDA App
Click to expand...
Click to collapse
That parts of the ICS source code are being merged into the next nightly
By the look of it now parts of the ICS framework signal indicator etc
nice
what do you think when will arrive first nightliys of cm9?
IE-coRe said:
nice
what do you think when will arrive first nightliys of cm9?
Click to expand...
Click to collapse
Its hard to say I don't think it will be long giving how long it took them to code gingerbread to my nexus one
keep folowing the changelog, they're doing a great job!
i saw they've started to merge ICS stuff, by that mean the CM7 will become CM9 if they'll merge the ICS source code?
They may be merging ICS source with CM source, but they won't be releasing it for devices for quite some time. I expect the first nightlies to be around January / February time
I still don't understand the difference between the nightlies and the progress the team free xperia makes here in the boards with their FXP0xx releases :/
Which one is better / more up to date ?
Thanks,
iCEQB
SE_iCEQB said:
I still don't understand the difference between the nightlies and the progress the team free xperia makes here in the boards with their FXP0xx releases :/
Which one is better / more up to date ?
Thanks,
iCEQB
Click to expand...
Click to collapse
The nightlies are compiled everyday and contain any additions to git from that day. The FXP releases are usually around a weekly release cycle.
The nightlies contain more recent code changes so are "more up to date", but you run the risk of using not fully tested code and so may be buggy (I've encountered a boot-loop with CM nightlies before, so fresh backups are needed).
There is no "better" version, just whichever you prefer.
garner said:
Has anyone flashed 046 with the original kernel? does touchpads work ie dead space etc???
Click to expand...
Click to collapse
With 046 + doomkernel, doesn't work the touchpad anywhere or only in certain games? Thanks...
liester said:
With 046 + doomkernel, doesn't work the touchpad anywhere or only in certain games? Thanks...
Click to expand...
Click to collapse
The touch pads work in every game I've been using at least and I remember reading on the cm thread that touch pads don't work for ANY of the ea games.
Sent from my R800i using XDA App
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....
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.
So for whatever reason, Cyanogen has removed all CM11 nightlies from their servers. Some people are quite upset at this. I know I was. The last Slimkat stable gave me problems, and the CM12 nightlies are a work in progress. I eventually gave in and began sampling various Lollipop ROMs. Now I've found out that someone was kind enough to post it on Google Drive. Here's the link:
cm-11-20150105-NIGHTLY-bacon.zip
I checked the integrity of the file. The MD5 matches up to the one listed on Cyanogen's website. Enjoy. Here's the MD5 to see if it downloads OK on your side.
md5sum: 7cb44264cc5386dba24c8687c0e8e4cb
If this link goes down, I will repost the file myself.
Oh, and I ask any and all devs who want to screw with this nightly to go right ahead. If it has any problems or features you want added, it's up to the community to add them.
BUGS:
-The screen has a really hard time waking up both through DT2W and the power button. This can be fixed by turning "Prevent accidental wake-up" off in Display settings. This bug is also present in the last Slimkat stable. >_<
And now, some addons!
CM11S (44S) Addons for CM11 nightlies
[APP][NO ROOT][Jan/31/2015]CameraNext Modded
notyu1459 said:
And now, some addons!
CM11S (44S) Addons for CM11 nightlies
Click to expand...
Click to collapse
Thanks for the addons,
I've been tryring a lot of different keyguard.apk and I like yours the best
How did you manage to make it compatible with the latest nightly?
waterdaan said:
Thanks for the addons,
I've been tryring a lot of different keyguard.apk and I like yours the best
How did you manage to make it compatible with the latest nightly?
Click to expand...
Click to collapse
Actually, I can't stake credit for the 44S addons. I can't remember where I got them from; they didn't have a dedicated thread. As far as I can remember somebody wanted them and somebody else threw together this zip. I'm assuming that the fact that they are sourced from the last KitKat OTA helps with the compatibility part.
thanks! .. curious how this differs from the latest cm11s?
I'm sorry, but the link is dead :'(
dionisius1 said:
I'm sorry, but the link is dead :'(
Click to expand...
Click to collapse
I still have it, here is the link for 20150105 Nightly.
https://drive.google.com/open?id=0B7Z5Mrhb24KwTjdXeXlhdjNOU3c
Or
This one is an updated CM11 Nightly 20150810 Unofficial Nightly by @Lanchon
http://forum.xda-developers.com/showpost.php?p=61929478&postcount=587
soralz said:
I still have it, here is the link for 20150105 Nightly.
https://drive.google.com/open?id=0B7Z5Mrhb24KwTjdXeXlhdjNOU3c
Or
This one is an updated CM11 Nightly 20150718 Unofficial by @Lanchon
http://forum.xda-developers.com/showpost.php?p=61929478&postcount=587
Click to expand...
Click to collapse
that was the "final" build (so called by CM), but now i made a newer one, stagefright and all...
Lanchon said:
that was the "final" build (so called by CM), but now i made a newer one, stagefright and all...
Click to expand...
Click to collapse
That 0810 build? Nice I will update it when I reach home. Thanks for your work
Awesome
Awesome guys. I was looking for the CM 11 update. Lollipop sucks for battery life. Hope this thread will updated if any changed occurs. So 10th August is that Final build for now ?
Aki07 said:
Awesome guys. I was looking for the CM 11 update. Lollipop sucks for battery life. Hope this thread will updated if any changed occurs. So 10th August is that Final build for now ?
Click to expand...
Click to collapse
Keep an eye on the thread below.
http://forum.xda-developers.com/showthread.php?t=2840393