• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][UNOFFICIAL][4.4.4] DeCAF Cyanogenmod 11, Release 1

donjuro said:
Been a while since any things been posted. Any progress? Any bugs squashed?
Click to expand...

there has been a lot of trying and failing. the time i do get, i make progress with decaf cm11 and lose it by not being very organized. thinking about dropping this rom soon, and just trying to take on a support role with bad_mofo_33 since his rom is either at or above this in terms of functionality. it has always been about getting a stable cm11 so we can get slimkat, paranoid, omni, eventually cm12, etc so im not afraid to admit defeat in my own dealings and start on another rom with his source.

mofo's caf cm11 has a lot of less hackish things going on than this does, especially with sound, and looks more like something we could submit to cm in the future.

on an interesting note, apparently even quarx2k's official w7 cm11 has issues with video recording and nfc, so i really dont feel too bad about those not working. shinobisoft's rom too, and also zaaap's for the lg g2 mini.

gps has been a pain, i got a 3d lock with device only once and since then it just refuses to do it even with things set up the same way i had them when i got the lock. sms/mms has proven to be a real bear, there is some funky stuff going on with apns and framework still that logic tells me shouldnt be, but i guess my logic is pretty flawed. tried a lot and failed a lot. emotional_led (ring around home button) is in the framework files somewhere, ive just been too busy with a bunch of other things to track it down.

i dont have data anymore since im around wifi all the time, but i think i have it to the point where it should be working correctly with ehrpd and handing off from ehrpd-cdma to ehrpd-lte with bad_mofo's caf source. im probably wrong, as i am usually known to be. thats not to say that lte works, its hard to test lte since where im living now doesnt get 4g. (only place in town, also right next to a college, thanks sprint.)

so thats whats going on. at this point i just feel lucky i got this far with it, and if i make some breakthroughs and keep going with decaf cm11, thats awesome, but if not, i have no real emotional attachment to this rom. i said it above and ill say it again, it was all about getting a good base for cm11 and ports. we are almost there, just a few more things to check off the list.
 
Sorry if this was covered earlier in the thread, I don't have time to read all of it. I apologize. Is it currently possible to overclock the CPU (and GPU) with this ROM / kernel set up?
 
quickdraw996 said:
Sorry if this was covered earlier in the thread, I don't have time to read all of it. I apologize. Is it currently possible to overclock the CPU (and GPU) with this ROM / kernel set up?
Click to expand...
No, overclocking requires a specially coded kernel. The priority right now is to get a custom ROM 100% working first.
Then, someone might delve into making an OC kernel.
 
bg4m3r said:
No, overclocking requires a specially coded kernel. The priority right now is to get a custom ROM 100% working first.
Then, someone might delve into making an OC kernel.
Click to expand...

Yeah, I know about the kernel part, I just wasn't sure if it had been modified for over clocking yet, as I am unfamiliar with what the "caf" kernel is, whether it was custom or not, etc. I know the SD 400 can do better than 1.2ghz.

Thanks.
 
quickdraw996 said:
Yeah, I know about the kernel part, I just wasn't sure if it had been modified for over clocking yet, as I am unfamiliar with what the "caf" kernel is, whether it was custom or not, etc. I know the SD 400 can do better than 1.2ghz.

Thanks.
Click to expand...
---
Before compiling, simply edit cpu config file: /kernel/arch/arm/mach-msm/acpuclock-8226.c (attached; delete .txt; ZV5 source unmodified)
---
Dunno about caf cm11 for volt. Decaf had not been modified yet. If you can compile kernel, it's easy to overclock. Here is a brief youtube video on modifying one single config file to overclock (before compiling kernel). Nothing more is required than this, then you can use standard overclock apps available in the playstore.
Here is the link to ls740 LG Volt kernel source:
http://opensource.lge.com/osSch/list?types=NAME&search=ls740
So easy....probably the single best modification a phone could have to improve performance too. :)
 

Attachments

Last edited:
whoshotjr2006 said:
Unfortunately no. I discontinued this about a month ago, and started working on caf cm11 builds more heavily and now omnirom. Check bad_mofo's caf cm11 thread for updates.

I should probably put a discontinued tag in the title in the future.
Click to expand...

Could you also post a link to your new work once it becomes available, please. It would be greatly appreciated!
 
whoshotjr2006 said:
Unfortunately no. I discontinued this about a month ago, and started working on caf cm11 builds more heavily and now omnirom. Check bad_mofo's caf cm11 thread for updates.

I should probably put a discontinued tag in the title in the future.
Click to expand...
Been meaning to ask what the difference between caf and decaf is
 
CrimsonToker said:
Been meaning to ask what the difference between caf and decaf is
Click to expand...

Me too. Here's a explanation that I googled (I take no credit for it):

CodeAurora (CAF) - These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.

Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.

So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.

Starting with 4.3, CM started mixing code between CAF and AOSP. They put some CAF features/capabilities into their baselines for AOSP-supported devices (Nexus devices), and started putting AOSP patches into their baselines for CAF devices.

Source:
http://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
 
I keep getting this error when flashing.
 

Attachments

  • Screenshot_2015-02-23-22-15-08.png
    Screenshot_2015-02-23-22-15-08.png
    33.7 KB · Views: 129
Sorry for the late reply, but the rear camera DOES WORK! I wasn't able to get it on CM12, but I can with this ROM. This is my new daily driver. I lost LTE in the stock ZV5, I still don't have it here, but I didn't expect to. Good job dev!
 
You must log in or register to reply here.
Back
Top Bottom