Database Users

The Unofficial CyanogenMod Series - added aokp-jellybean test build

Hi all I will be working this a little. But don't expect anything to great. I don't have a whole lot of time to work on this. I bricked my phone and not having much luck getting it replaced. So I won't be working on this to much until I can get a new phone as I will be spending all my time working.
Most stuff posted here is probably gonna be untested.
I will be posting cm7, cm9, and cm10 builds here.
Idk if any of these work.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
CyanogenMod 7:
Code:
[CENTER]
[B][U][COLOR="Blue"][SIZE="2"]Download:[/SIZE][/COLOR][/U][/B]
[URL="https://www.dropbox.com/s/1ct15i6fxbprpjj/cm-7-20120720-UNOFFICIAL-captivatemtd.zip"]cm-7-20120720-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][SIZE="2"][COLOR="Blue"]Google Apps for Gingerbread:[/COLOR][/SIZE][/U][/B]
[URL="http://goo.im/gapps/gapps-gb-20110828-signed.zip"]gapps-gb-20110828-signed.zip[/URL][/CENTER]
CyanogenMod 9:
Code:
[CENTER][B][U][COLOR="Blue"][SIZE="2"]Downloads:[/SIZE][/COLOR][/U][/B]
[URL="https://www.dropbox.com/s/p0n6myyedm7pyx4/cm-9-20120720-UNOFFICIAL-captivatemtd.zip"]cm-9-20120720-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][SIZE="2"][COLOR="Blue"]Google Apps for ICS:[/COLOR][/SIZE][/U][/B]
[URL="http://goo.im/gapps/gapps-ics-20120429-signed.zip"]gapps-ics-20120429-signed.zip[/URL][/CENTER]
CyanogenMod 10:
Code:
[CENTER][B][U][COLOR="Blue"][SIZE="2"]Download:[/SIZE][/COLOR][/U][/B]
[URL="http://www.mediafire.com/?ndt440n4ux0ctaz"]cm-10-20120727-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][COLOR="Blue"][SIZE="2"]Old builds:[/SIZE][/COLOR][/U][/B]
[URL="http://www.mediafire.com/?2n75vev3qvcl417"]cm-10-20120723-UNOFFICIAL-captivatemtd.zip[/URL]
[URL="http://www.mediafire.com/?d89z35acc2cpaxr"]cm-10-FIXED_RECOVERY-captivatemtd.zip[/URL]
[SIZE="2"][B][U][COLOR="Blue"]Google Apps for JellyBean:[/COLOR][/U][/B][/SIZE]
[URL="http://goo.im/gapps/gapps-jb-20120726-signed.zip"]gapps-jb-20120726-signed.zip[/URL]
[URL="http://www.mediafire.com/?xje9p4hl1qv56qz"]inverted_gapps2-jb-20120715.zip[/URL]
[/CENTER]
Recovery:
Code:
[CENTER][B][U][SIZE="2"][COLOR="Blue"]Fake Flashes:[/COLOR][/SIZE][/U][/B]
Touch recovery 6 Fake flash: [URL="http://www.mediafire.com/?k240g28o332apgy"]touch_recovery_fake_flash.zip[/URL]
This is a preview most ways to navigate doesn't work. Normal recovery functions work though
Thanks to:
[URL="http://forum.xda-developers.com/member.php?u=2492461"]sk8erwitskil[/URL] for the source
[/CENTER]
Install instructions:
Code:
[CENTER]Make a backup......
Factory reset........
Mounts and storage > format system.......
Advanced > Wipe Dalvik Cache.......
Install Rom......
Install gapps.....
Reboot......
Go to Rom Manager and fix permissions......
Reboot......
Your all set.........[/CENTER]
Upgrading From a Previous Version:
Code:
[CENTER]Reboot to Recovery
Go to mounts and storage and format system...
Flash latest rom....
If coming from a different build like from cm9 to cm10
then follow the install instructions
When going from cm10 to cm10 flash latest cm10 zip
When going from cm9 to cm9 flash latest cm9 zip[/CENTER]
AOKP- JellyBean test build
Code:
[CENTER][SIZE="3"][B][U]Download:[/U][/B][/SIZE] [URL="http://www.mediafire.com/?9eud3x8c4pq4atd"]
AOKP-JB-captivate-b1.zip[/URL]
[SIZE="3"][B][U]Doesn't work:[/U][/B][/SIZE]
Rom Control force closes Settings
Messaging force closes
Still being tested. Please provide feedback[/CENTER]

cm7 builds:
cm-7-20120720-UNOFFICIAL-captivatemtd.zip
gapps-gb-20110828-signed.zip
Click to expand...
Click to collapse
what's different from Official version this unofficial version?
p.s: sorry for my english

Someone please confirm but I thought releases weren't supposed to be put on xda without the op having a device to test it on? Just curious...
Sent from my SGH-I897 using xda premium

I have this device. I bricked my skyrocket
Sent from my SGH-I897 using Tapatalk 2

levanr said:
what's different from Official version this unofficial version?
p.s: sorry for my english
Click to expand...
Click to collapse
I'm not sure. I just like making my own builds and I figured I'd post them.
Sent from my SGH-I897 using Tapatalk 2

levanr said:
what's different from Official version this unofficial version?
p.s: sorry for my english
Click to expand...
Click to collapse
"unofficial" is beta version that has some problem, "official" is perfect version that has no problem.

gmillz said:
Hi all I will be working this a little. But don't expect anything to great. I don't have a whole lot of time to work on this. I bricked my phone and not having much luck getting it replaced. So I won't be working on this to much until I can get a new phone as I will be spending all my time working.
Most stuff posted here is probably gonna be untested.
I will be posting cm7, cm9, and cm10 builds here.
Idk if any of these work.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
Click to expand...
Click to collapse
-Downloading
If they wont work... you need a logcat or something .. am I right ?

How to install: ?
Features: ?
Sent from my GT-I9000 using xda premium

Are these the same available on get.cm?

unnecessary (sorry)
Sent from my GT-I9000 using Tapatalk 2

Gore785 said:
How to install: ?
Features: ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
if you dont understand how to install please leave the area lol

What's the point of this thread?
CheesyNutz said:
if you dont understand how to install please leave the area lol
Click to expand...
Click to collapse
I've honestly lost count of all your posts that offer absolutely nothing helpful or relevant to the discussion.

I understand theres not much of a point to this. The main reason for this thread is cm10 as all the other cm10 roms don't have the stock cm kernel. But since I build the other ones anyways i figured I'd post them. And I'll post install instructions.

kevinnol said:
-Downloading
If they wont work... you need a logcat or something .. am I right ?
Click to expand...
Click to collapse
Definitely. Logcats would be great

CheesyNutz said:
if you dont understand how to install please leave the area lol
Click to expand...
Click to collapse
Meant that as in anything we should do in specific before, during, or after install Like fix permissions?
Sent from my GT-I9000 using xda premium

johnnyrichter said:
What's the point of this thread?
I've honestly lost count of all your posts that offer absolutely nothing helpful or relevant to the discussion.
Click to expand...
Click to collapse
gmillz said:
I understand theres not much of a point to this. The main reason for this thread is cm10 as all the other cm10 roms don't have the stock cm kernel. But since I build the other ones anyways i figured I'd post them. And I'll post install instructions.
Click to expand...
Click to collapse
So...if you understand there's not much of a point, why post at all? Also, FYI, in regard to your OP: "to" is not the same as "too", and "infact" is not a word. Just sayin'.

adzidek said:
So...if you understand there's not much of a point, why post at all? Also, FYI, in regard to your OP: "to" is not the same as "too", and "infact" is not a word. Just sayin'.
Click to expand...
Click to collapse
Because this is the only cm10 rom with the stock cm kernel. I meant there was not much reason to post any of the other builds

gmillz said:
Because this is the only cm10 rom with the stock cm kernel. I meant there was not much reason to post any of the other builds
Click to expand...
Click to collapse
You'll likely receive a lot of flak over re-hosting/posting stuff as you've seen thus far, but if you're offering something you've re-worked in any way(which is what I understand you're doing) then I'd stick with just that and link to other threads in your OP if necessary.

If you compiled from CM10 source here we have CM10 kernel for Captivate (no datadata partition).
This is very interesting.
Thank you very much: if compiling went well this is really an important step for JB on Cappy and now we can run also official Pawitp builds.

Monfro said:
If you compiled from CM10 source here we have CM10 kernel for Captivate (no datadata partition).
This is very interesting.
Thank you very much: if compiling went well this is really an important step for JB on Cappy and now we can run also official Pawitp builds.
Click to expand...
Click to collapse
Yes this is compiled from source specifically for the captivate.
And compiles with no errors

New File System By Samsung

a new Linux file system from Samsung that is faster than existing ones when running on flash storage devices, submitted in a clean, easy-to-apply manner. This will be great for Android-based systems.
#source: G+

ithunter said:
a new Linux file system from Samsung that is faster than existing ones when running on flash storage devices, submitted in a clean, easy-to-apply manner. This will be great for Android-based systems.
#source: G+
Click to expand...
Click to collapse
Look at this.. XDA users are on the case already!
I like the idea behind this filesystem!

As the OP of the thread said, it is possible but we would need a new recovery and edit the kernel to add F2FS (that's the name, right?) formatting and detecting support. What I'm confused about is whether or not we are gonna need USB drivers if we use this. Please explain.

Is this lwn.net/Articles/518718/ what you're talking about?
Sent from my rooted tomato using xda app

I dont have a single ideea what f2fs means but i smell nAa-15 kernel.
Sent from my X8 using xda app-developers app

Hmm, interesting... wonder what advantages it has compared to YAFFS2.

i guess efficient flash storage, that is if Sammy doesn't screw it up like they did with RFS.
i hope it's good. i also hope it can be made to work with the X8.
fingers crossed.

We can get this working on the x8.. It's just a matter of compiling it into the kernel, editing the ramdisk and recovery.
Kernel & ramdisk bits are really simple..
I haven't found yet what needs to be edited in the recovery. Anyone any leads on this?
This will give us much higher sd read & write with less overhead so the sdcards will last much longer and will fragment less.
They don't have a fsck for it yet but it has full logging and journaling..

Can even choose to only convert system and data and leave bootimage/recovery as is.
Sent from my GT-I9300 using xda premium

yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)

sgt. meow said:
yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)
Click to expand...
Click to collapse
The source is already available.. I might just do that!

sgt. meow said:
yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)
Click to expand...
Click to collapse
So the kernel in recovery needs to support it, problem solved.
Sent from my GT-I9300 using xda premium

yes but the recovery binary that we have in the kernel is compiled from a regular CM tree and settings have to be changed there (not sure which) before compiling the binary. maybe nAa, alfsamsung, CtrlAltDelIrl, other devs or a team of devs can come up with one such recovery and kernel.

It is not that hard, when you have that kernel compiled and in device sources (or build it during the progress like we do on LG P500) you can build a recovery which supports it.
Sent from my GT-I9300 using xda premium

_Arjen_ said:
It is not that hard, when you have that kernel compiled and in device sources (or build it during the progress like we do on LG P500) you can build a recovery which supports it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
exactly what i meant.

[ROM] [FIND5] [4.2.2] [cfX-Toolchain 4.8.y+] codefireXperiment

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

CAF problems list

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.

4.3 kernel sources released! grab them here

http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/

Wow man latest news isn t it?? Using Internet Explorer??

And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk

It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app

Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?

ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?

What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?

granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse

dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited

granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.

rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.