[ROM][CM11][4.4.2][LINARO][Flo] temasek UNOFFICIAL Builds [Feb-26]

[abacus0101]

Could you try the old build from the downloads tab and tell me if it still persists.

Sent from my Nexus 4 using Tapatalk

TheDarkDefender. So I downloaded the previous version of this rom along with the Pa-Gapps file. I installed it, same as I did the current one and guess what, no problems at all. It didnt crap out all over the place. Google now works. Halo works...so i will stick with that for now. I did try to install a flo verison of elementalx but ended up with weird colored checker board..nothing legible..and it messed up the rom. From what i've read that kernel doesnt work well with Cyanogenmod, so i just did a dalvik and system wipe reinstalled and it was back. Nice rom im glad it working thank you for your help. If you ever figure out why the other gave me such problems i'd be interested in knowing.

 

[aftermath85]

Does someone know the differences (besides being proprietary) between CAF and AOSP from a practical and technical point of view?

you can look to it here https://www.google.com.ph/search?q=caf+vs+aosp&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-USfficial&client=firefox-a&gfe_rd=cr&ei=N_4GU5DhHeuJ8Qegi4Ao
^_^

 

[nikr123]

Does someone know the differences (besides being proprietary) between CAF and AOSP from a practical and technical point of view?

Basically:
AOSP: Google's official release. (Android Open Source Project)
CAF: Open source Qualcomm kernel. (Code Aurora Forum)

People for some reason are really against cm's to change to CAF. I think it is a good move for quick ports to new devices.

Sent from my Nexus 7 using Tapatalk

 

[TheDarkDefender]

Does someone know the differences (besides being proprietary) between CAF and AOSP from a practical and technical point of view?

Quoting faux :

Geek Talk Below:

CAF == Qualcomm's open source branch.

CAF's kernel sources are 100% open as required by GPL. Their libraries, however, are under Apache which means you can use them as you see fit, but not all are open (some are strictly as proprietary lib files).

For ALL NON-Nexus Qualcomm devices, CAF's kernel + libraries will be the closest to AOSP experience (Even Google's AOSP still depends heavily on these proprietary libraries from various vendors including Qualcom/CAF).

Historically, Qualcomm often creates a separate less optimized version of their proprietary libraries for Google to use on Nexus devices (I guess because Google didn't pay them to be their premium partners like Samsung, HTC and LG), but this didn't stop Google from turning these basic libraries and create amazing experiences on their Nexus devices (HTC's Nexus One, Google's Nexus 4, Google's Nexus 7 2013 and the upcoming Nexus 5).

So now you know there are two distinct branches of libraries, AOSP and CAF's own version. Although both were created by CAF, but there exist some differences between the two (These differences are what creates bugs when you mix match the libraries and kernel source).

For reasons unknown, CM has decided to ditch the less optimized libraries and opted for CAF's own libraries for Nexus 7 2013... This created a massive headaches for many novice users and developers. If you load the AOSP kernel on CM ROM, you now have a mismatching kernel / library combination which led to video glitches and broken Slimport on Nexus 7 2013.

It looks like for Nexus 4, they are slowly doing the same thing by replacing the AOSP libraries with CAF versions... over time, the AOSP kernel will no longer be 100% compatible with CAF based ROM... This will eventually lead to fragmentation of Nexus kernels (just like Nexus 7 2013  )

I am HIGHLY AGAINST this move towards CAF for pure Nexus devices. Nexus devices already work quite well with what's given, and it enjoyed wide compatibility with ALL AOSP derived ROMs. By moving towards using CAF libraries on Nexus devices creates unnecessary FRAGMENTATION and incompatibilities within a Nexus device family!

Also I am not sure about the legality of using CAF libraries... Basically if you build a ROM based from it, you are redistributing the Qualcomm proprietary blobs and Qualcomm has EXTREMELY strict redistribution clause with their binary blobs (basically they need to grant you explicit permissions) where as AOSP it is less stringent than Qualcomm. Whenever you deal with proprietary libraries in general, you are in the gray area of legality and you have to tread very carefully. (This legal issue was what kept Nexus 7 2013 from releasing their factory images for a while between Qualcomm and Google. This is also what eventually led to JBQ leaving Google).

Sent from my Nexus 4 using Tapatalk

 

[MidnightDevil]

Thank you so much for the explanations.

I'm all for AOSP, but choosing that, we are ditching CAF optimizations and far as we are aware, we don't know what we are ditching but it can improve quality, stability, performance or user experience.

I wish that Qualcomm and Google get their heads out of their arses and work together in order to:
1 - Mitigate the fragmentation caused by this move.
2 - Have a open source kernel, improved, optimized with all the whistles and bells aosp wishes to introduce.

By doing that, cyanogen move would have no impact on the users.

 

[poondog]

Remove all CAF.
Yes, AOSP Kernels are now fully compatible. Tested elementalX.
Franco kernel is also compatible, but it breaks Theme Engine and Superuser. If you don't care for themes,freeze/disable Theme engine apk, flash a superuser zip and you're good. Glitch kernel AOSP should be good too. Others you gotta test and let me know.

Hi mate

sorry to bump this.. but is theme engine support baked into ramdisk? Have you tried to flash franco kernel with the ramdisk from your ROM? Maybe this is the reason, as Franco uses his own ramdisk.. just a thought but you have probably passed it because I know superuser is ramdisk

and about this CAF vs AOSP.. is it possible that someone benchmarks the exact same ROM and setup (besides CAF/AOSP) and see which is higher? On my One, I get 25k on antutu stock Sense and 27k on CAF CM ROM. But then thats CAF vs Sense not really a fair test.. anyone got good benchmarks? I have used AOSP for the whole time and now I use AK kernel on AOSP (AK kernel is CAF bbase)
I know benchmarks are not everything, but they do show a difference when there is a code change on a rom/kernel on the same device and setup.. then imo benchmarks can be a fair test

 

[TheDarkDefender]

Hi mate

sorry to bump this.. but is theme engine support baked into ramdisk? Have you tried to flash franco kernel with the ramdisk from your ROM? Maybe this is the reason, as Franco uses his own ramdisk.. just a thought but you have probably passed it because I know superuser is ramdisk

and about this CAF vs AOSP.. is it possible that someone benchmarks the exact same ROM and setup (besides CAF/AOSP) and see which is higher? On my One, I get 25k on antutu stock Sense and 27k on CAF CM ROM. But then thats CAF vs Sense not really a fair test.. anyone got good benchmarks? I have used AOSP for the whole time and now I use AK kernel on AOSP (AK kernel is CAF bbase)
I know benchmarks are not everything, but they do show a difference when there is a code change on a rom/kernel on the same device and setup.. then imo benchmarks can be a fair test

Hey man,

No, I never tested it that way, just a usual flash. I could test a modded ramdisk using the ramdisk tool but I've dropped the non caf idea anyway, so don't really care for it now.

I tested benchmarks on non caf vs caf but different kernels though, so i dont think it was fair. Caf gave an additional 2k in the result,fyi. I'm sure caf would lead any time cos it has those optimizations added by cm and aosp just uses the Linux kernel as it is, IIRC.

Sent from my Nexus 7 using Tapatalk

 

[TheDarkDefender]

New build : V47.1

- Add back CAF ( feels better this way )
-Retain Building with LINARO 4.7 toolchain
-Update with CM commits
-update omni switch
-Show live wallpapers in the recents view on high-end devices
-Speed up boot dex opt on multicore devices
-core: fix volume panel more button transparency
-Pie fixes
and more minor changes.

The rom is NOT NON-CAF anymore. Flash CAF KERNELS ONLY.

Switching to androidfilehost for now. Download here http://www.androidfilehost.com/?fid=23329332407573311

 

[MidnightDevil]

New build : V47.1

- Add back CAF ( feels better this way )
-Retain Building with LINARO 4.7 toolchain
-Update with CM commits
-update omni switch
-Show live wallpapers in the recents view on high-end devices
-Speed up boot dex opt on multicore devices
-core: fix volume panel more button transparency
-Pie fixes
and more minor changes.

The rom is NOT NON-CAF anymore. Flash CAF KERNELS ONLY.

Switching to androidfilehost for now. Download here http://www.androidfilehost.com/?fid=23329332407573311

Hi,
I just flashed the updated version but when I flash the latest Glitch CAF kernel, it doesn't go further than the boot animation.
The same thing happens with AOSB.
Were there any recent CAF changes that broke compability with Glitch CAF ?

 

[Lazy79]

If you flash glitch with enabling dalvik patch try to flash the kernel without the optimized dalvik patch. This worked here

 

[MidnightDevil]

If you flash glitch with enabling dalvik patch try to flash the kernel without the optimized dalvik patch. This worked here

Alright, so same thing but with no Dalvik optimizations. Will try that.
Did anyone had the same issue with the optimizations?

 

[Lazy79]

Had the same on my lg g2 so I think it has something to do with the recent changes.. Also on S4 its the same. Boot loop with dalvik patch, working without

 

[MidnightDevil]

Had the same on my lg g2 so I think it has something to do with the recent changes.. Also on S4 its the same. Boot loop with dalvik patch, working without

Booted fine with no optimization! Cheers!

 

[aftermath85]

& about the OTG USB

CM has no problem with otg, & also the 1st release..
but after i flash the new one(the caf & non-caf) my pendrive cannot be detected by stickmount, not until ireboot..But it works fine in feb10 version.. will you look in it if you have time,thank you so much..^^
is it aboiut the supersu? or kernel??

im in the same kernel( glitch,)same setting.. )
hoping you could help me here

 

[TheDarkDefender]

CM has no problem with otg, & also the 1st release..
but after i flash the new one(the caf & non-caf) my pendrive cannot be detected by stickmount, not until ireboot..But it works fine in feb10 version.. will you look in it if you have time,thank you so much..^^
is it aboiut the supersu? or kernel??

im in the same kernel( glitch,)same setting.. )
hoping you could help me here

Could you try with stock cm kernel and check.
I don't think anything related to this has been tampered with.

Sent from my Nexus 4 using Tapatalk

 

[MidnightDevil]

@TheDarkDefender, can you tell me how to change the lockscreen handle?
I resized a picture, tried png, ico, bmp, jpg, and "the app did not return a valid icon or does not support resizing"...

I'm trying to use a doge picture

 

[TheDarkDefender]

@TheDarkDefender, can you tell me how to change the lockscreen handle?
I resized a picture, tried png, ico, bmp, jpg, and "the app did not return a valid icon or does not support resizing"...

I'm trying to use a doge picture

Pick up a larger picture then. The format doesn't matter I guess.

Sent from my Nexus 4 using Tapatalk

 

[MidnightDevil]

Pick up a larger picture then. The format doesn't matter I guess.

Sent from my Nexus 4 using Tapatalk

I've tried, actually tried a bunch of them, but same msg is given.
Oh well, no worries

 

[TheDarkDefender]

Update:

V50 - FEB-26

-Updated with Cyanogenmod
-Change density on the fly - from slimroms
-Day and week on data usage
-screenrecorder: check for supported video encoder resolutions
-Live Volume Steps
- Re-do contextual notification header images …
-Add evening time to header
-Notification Reminders from slimroms
-ActiveDisplay (rework interface) …
-ActiveDisplay: Fix for flo and other devices
-Wakelock Blocker
-speed up booting on multicore devices.
-Show owner info creation if no owner is set for UserTile
- Show default profile name if no profile exists … and more!

download here http://forum.xda-developers.com/devdb/project/dl/?id=4373

 

[TheDarkDefender]

Closing this thread as there's no activity and I'm not interested in spending time on this anymore. Builds stopped on temasek's request.