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

Status
Not open for further replies.
Search This thread
By:
Advanced…
A

abacus0101

Senior Member
Jul 17, 2012
154
9
TheDarkDefender said:
Could you try the old build from the downloads tab and tell me if it still persists.

Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
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.
 
  • Like
Reactions: TheDarkDefender
N

nikr123

Senior Member
Jul 10, 2011
183
39
MidnightDevil said:
Does someone know the differences (besides being proprietary) between CAF and AOSP from a practical and technical point of view?
Click to expand...
Click to collapse

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
 
  • Like
Reactions: MidnightDevil
TheDarkDefender

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
MidnightDevil said:
Does someone know the differences (besides being proprietary) between CAF and AOSP from a practical and technical point of view?
Click to expand...
Click to collapse

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).
Click to expand...
Click to collapse

Sent from my Nexus 4 using Tapatalk
 
  • Like
Reactions: Macchinista
MidnightDevil

MidnightDevil

Senior Member
Apr 2, 2012
3,135
1,252
London
Redmi Note 9
Google Pixel 6 Pro
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

poondog

Inactive Recognized Contributor
Dec 11, 2011
14,998
12,953
Melbourne
TheDarkDefender said:
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.
Click to expand...
Click to collapse

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 :p 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

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
poondog said:
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 :p 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
Click to expand...
Click to collapse

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
 
  • Like
Reactions: poondog
TheDarkDefender

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
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
 
  • Like
Reactions: aftermath85, nikr123, cheezusweezel and 4 others
MidnightDevil

MidnightDevil

Senior Member
Apr 2, 2012
3,135
1,252
London
Redmi Note 9
Google Pixel 6 Pro
TheDarkDefender said:
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
Click to expand...
Click to collapse

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 ?
 
A

aftermath85

Senior Member
May 24, 2013
309
88
Manila
& 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

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
aftermath85 said:
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 :(
Click to expand...
Click to collapse

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
 
TheDarkDefender

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
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://xdaforums.com/devdb/project/dl/?id=4373
 
  • Like
Reactions: Samuel Holland, taadow1030, danaff37 and 2 others
TheDarkDefender

TheDarkDefender

Senior Member
Aug 5, 2012
4,092
6,434
33
Reston, VA
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.
 
Last edited:
  • Like
Reactions: habylab
Status
Not open for further replies.

Similar threads

followmsi
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
Replies
4K
Views
1M
osm0sis
osm0sis
Scott
[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1
Replies
2K
Views
370K
S
Suici Doga
DJLamontagneIII
[ROM][CM10.2][4.3][CyanogenMod Kangs][DJL10.2][SM-Toolchain][LINARO][2013/09/29]
Replies
2K
Views
310K
dscribe
dscribe
Scott
  • Locked
[ROM][10/27] CleanROM 7.1 -★| Marshmallow! | MRA58U !| Aroma! | Clean! | Stable! |★-
Replies
7K
Views
1M
Scott
Scott
teeseeuu
Euphoria-OS 1.1 Nexus 7 (2013) (Flo)
Replies
316
Views
286K
S
SHABBYLEA

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 18
    TheDarkDefender
    TheDarkDefender
    original thread and dev: http://xdaforums.com/showthread.php?t=1797109

    Check out the video here https://www.youtube.com/watch?v=QJ2wrpolSWc

    NOTE

    This is an UNOFFICIAL build of CM11 (CyanogenMod 11) for flo and this is NOT my work. I am just compiling from CM & temasek's source and 100% credit goes to all coders who contributes to CyanogenMod and of course, @temasek, for bringing in tons of features from different ROMs.

    This is similar to a nightly from CM but has some extra goodies baked in. If you can't handle some things possibly being broken, please don't use this.

    DISCLAIMER
    Code: 
    /*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
 */


    I hope all of you like this ROM. Remember to VOTE this thread if you like it.



    • Do NOT expect daily builds. I'll build when I'm free.
    • Do NOT use this unofficial build and ask for support at the official threads.
    • Do NOT be rude.
    • Respect all users
    • If you see a NOOB question and you don't feel like replying, DON'T, just ignore that post. If you do reply, good for you.....and be nice in your reply.



    Please use the latest official TWRP recovery. CWM is fine too, but I believe TWRP is more stable (plus, TWRP is better imo).

    Read this first -> CLICK ME

    1st Time Installing
    • Download the zip
    • Download Gapps
    • WIPE DATA/FACTORY RESET
    • Install the update zip from recovery
    • Install gapps
    • Reboot

    Already installed CM11.0
    • Download the zip
    • Install the update zip from recovery
    • Reflash gapps (if you are using pa gapps)
    • Reboot

    FAQ

    Changelog (I suggest checking github for what is included up to the ROM date)
    http://xdaforums.com/showpost.php?p=29339092&postcount=2
    https://github.com/temasek - contains many features from different roms, check frameworks-base & settings repos for more details.

    DOWNLOAD SITES:

    USE CAF KERNELS ONLY

    Feb - 26 : http://xdaforums.com/showpost.php?p=50667935&postcount=79

    Old :
    http://xdaforums.com/devdb/project/?id=2863#downloads

    * mirrors are welcome, but please keep track of the download count in the mirror (if possible or if the DL count is available on the mirror site). I may be asking how many have downloaded the ROM from time to time. just curious :p. thanks!


    CREDITS

    temasek
    bruce2728
    Google
    Oracle (for VirtualBox)
    Ubuntu
    Ricardo Cerqueira aka rmcc
    XpLoDWilD
    entropy512
    David van Tonder
    TeamDouche
    SlimROM
    OmniROM
    AOKP
    CarbonROM
    ChameleonOS
    ParanoidAndroid
    Yank555
    AndreiLux
    AndiP71
    DerTeufel
    PartimusPrime (bootanimation for temasek builds)
    MisjudgedTwat (contributor to github sources)
    Cristiano Matos
    ex-temasek kernel stweaks master in-chief
    SleepinDevil (his assistance to troubleshoot/fix bugs)
    morckx for his contributions towards making stweaks available to temasek kernel
    MrxSiN & MiracleM4n for his stweaks contributions
    Vadonka (sponsor of temasek.hopto.org server)
    powwow88 (creator of my custom cm10 bootanimation)
    paour (contributor to github sources)
    All other coders for making CM possible!



    XDA:DevDB Information
    temasek UNOFFICIAL Builds, a ROM for the Nexus 7 (2013)

    Contributors
    TheDarkDefender, temasek, Cyanogenmod
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    Based On: CyanogenMod

    Version Information
    Status: Beta
    Current Beta Version: 44.1
    Beta Release Date: 2014-02-10

    Created 2014-02-11
    Last Updated 2014-02-27
    View
    7
    TheDarkDefender
    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
    View
    6
    TheDarkDefender
    TheDarkDefender
    Glad that you all like the rom. All credits to @temasek .

    Btw, I'm trying to build it free of CAF stuff with bruce2728's help. Hope it goes well. :)

    Sent from my Nexus 4
    View
    5
    TheDarkDefender
    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://xdaforums.com/devdb/project/dl/?id=4373
    View
    5
    TheDarkDefender
    TheDarkDefender
    Update : 02/17 - V46

    - 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.

    Note: The above changes are just temporary. I'm still unsure about this decision. Have to see the device's behaviour for a while before I can make this change permanent.

    -Build Bricked kernel along with rom, thanks to @show-p1984
    -Build kernel with LINARO 4.7

    ~~ Again, thanks a ton to @bruce2728 for being kind enough to allow me to use his repos and for solving build errors. Wouldn't have made it non-CAF nor built it with Linaro without his support.

    Other adds by temasek:

    - Merge upstream with CM11
    - SlimPie + fixes
    -Lockscreen notification updates
    -TRDS fixes
    - update Spanish translations
    -and more minor changes.. check temasek's git.

    If you wanna show some support, direct your donations to temasek and bruce2728, or Cyanogenmod... cos this is all their work. I'm just an impatient flashaholic who likes to build.

    That's all for now! Have fun!

    Download here http://xdaforums.com/devdb/project/dl/?id=4188

    View

New posts