[KERNEL] CM Specific Basic Kernel - BroadcomCM[TASSVE][v4.0 - 07/3/2014]

Search This thread

bieltv3

Senior Member
Jun 12, 2012
1,299
9,879
Barcelona
CyanogenMod 7.2 Specific BASIC Kernel - Tassve

We are planning to release a kernel that con work on both devices, a BCM21553-common kernel, but that is hard work, as we must compare all the files from kernel, and test everychange.


FEATURES:

Due to the kernel is pretty advanced, we are not talking of a TO-DO list, we are talking about a FEATURES list, so the FEATURES are:
  • Kernel just compatible with CM7
  • Specific Basic - Samsung official not-modded sources
  • EXT4 support
  • CWM Inclluded on kernel with EXT4 support too
  • Images of CWM patched to show good colors
  • Bluetooth and Wifi configs added to work with CM7
  • Common ramdisk used based on kissingmylove and PsychoGame
  • Ramdisk optimized for CM7 and EXT4
  • Compressed through LZMA
  • IMEI working on CM7
  • Offline charging working on EXT4 CM7
  • Added our new temp. CWM as default


SOURCES:

KERNEL SOURCE (GPL) is the official samsung kernel, as it is a specific BASIC kernel:
I needed to modify the configs to get a BT, Wifi, and EXT4 working, this is not included on Samsung stock kernel, so I leave here the config source:
Ramdisk has been also modd to create a bcm21553-common ramdisk that all users could use. SOurces to ramdisk can be found extracting from my kernel (LZMA) or also on github.


If other kernel developers want to contribute on this, shot me a PM, and I'll talk with you.

Thanks, Biel.
 

bieltv3

Senior Member
Jun 12, 2012
1,299
9,879
Barcelona
CHANGELOG

Version 4.0
  • Same build as version 3.0 , #7
  • Bigger cleanup ever made on ramdisk, to match CM7 and CM9 requiriments.
  • Added new BroadcomCM temp. CWM, with colors fixed.
  • Reduced booting time
  • Built with first 100% BCM21553 common ramdisk working based on AOSP ROMs.

Version 3.0
  • Clean Ramdisk as always :)
  • Included EXT4 and RFS (for not causing bricks) mounts on init.charge.rc
  • Start EXT4-fix in init.charge to mount syste, data, cache on inir.charge.rc and solve offline charging.

Version 2.1
  • Cleaned Ramdisk
  • Added permissions to camfash - for CM7
  • New built from same source and config

Version 2.0
  • Re-built ramdisk based on kissingmylove ramdisk
  • Delete all tweaks he added - BASIC KERNEL
  • EXT4 file system support for CM7
  • Hacked CWM Images to have a good color (no blues anymore)
  • Added some bootscripts to have better compatiblity with EXT4
  • Recovery has been updated to CWM 5.0.2.8
  • Mount USB mass storage is now working
  • CWM "HD" Edition, much more clear and tiny
  • Much more faster recovery

Version 1.0
  • First release of this kernel builded from source
  • First kernel with my name on it
  • Added new modify it ramdisk
  • Compressed throug LZMA using Lopicl.00 kitchen
  • Added CONFIG_SENSORS_COOPERVE=y
  • Added all the configs necessary to use Bluetooth on CM
  • Bluetooth working on new CM7 release, which should be RC1
  • Fixed CM7 bootanimation - thanks Prototype-U

Version 0.1
  • First release of this kernel
  • Not builded from source
  • Using Hell-lock kernel (Prototype-U) as zImage base
  • Modify lopicl.00 ramdisk and ad it to this kernel
  • Used LZMA to compress ramdisk
  • Fixed WIFI and torch on the ramdisk CM7.2
  • Not compatible with STOCK!
 

Gisha 7

Senior Member
Feb 1, 2013
306
103
Baltisk
4pda.ru
Why only two frequencies? And I like governor "lagfree"..
And on CM 7 by Percy BT not work..
 

Attachments

  • shot_2014-03-07_21-47-12.png
    shot_2014-03-07_21-47-12.png
    24.1 KB · Views: 485
  • shot_2014-03-07_21-47-33.png
    shot_2014-03-07_21-47-33.png
    25.6 KB · Views: 479
Last edited:

bieltv3

Senior Member
Jun 12, 2012
1,299
9,879
Barcelona
What sense in only two frequencies?
And at me not work wipe and format /data on kernel recovery..

I am not a kernel expert, so I just wanted to made the basic (stock kernel) compatible with ext4, lzma, and CM/AOSp roms. There are kernels better? Yes, but not with this compatibility

EDIT: wiping data working on my kernel amd CM7 (on ace-i, verified)

Enviado desde mi Nexus 7 mediante Tapatalk
 

thebiggboss180

Senior Member
Aug 25, 2013
456
54
28
amman
i installed the kernal...i got a problem that the data partition not mounting while using the phone normal

i cant install apps to the data parition and when i do reboot the device make a reset
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    CyanogenMod 7.2 Specific BASIC Kernel - Tassve

    We are planning to release a kernel that con work on both devices, a BCM21553-common kernel, but that is hard work, as we must compare all the files from kernel, and test everychange.


    FEATURES:

    Due to the kernel is pretty advanced, we are not talking of a TO-DO list, we are talking about a FEATURES list, so the FEATURES are:
    • Kernel just compatible with CM7
    • Specific Basic - Samsung official not-modded sources
    • EXT4 support
    • CWM Inclluded on kernel with EXT4 support too
    • Images of CWM patched to show good colors
    • Bluetooth and Wifi configs added to work with CM7
    • Common ramdisk used based on kissingmylove and PsychoGame
    • Ramdisk optimized for CM7 and EXT4
    • Compressed through LZMA
    • IMEI working on CM7
    • Offline charging working on EXT4 CM7
    • Added our new temp. CWM as default


    SOURCES:

    KERNEL SOURCE (GPL) is the official samsung kernel, as it is a specific BASIC kernel:
    I needed to modify the configs to get a BT, Wifi, and EXT4 working, this is not included on Samsung stock kernel, so I leave here the config source:
    Ramdisk has been also modd to create a bcm21553-common ramdisk that all users could use. SOurces to ramdisk can be found extracting from my kernel (LZMA) or also on github.


    If other kernel developers want to contribute on this, shot me a PM, and I'll talk with you.

    Thanks, Biel.
    11
    CHANGELOG

    Version 4.0
    • Same build as version 3.0 , #7
    • Bigger cleanup ever made on ramdisk, to match CM7 and CM9 requiriments.
    • Added new BroadcomCM temp. CWM, with colors fixed.
    • Reduced booting time
    • Built with first 100% BCM21553 common ramdisk working based on AOSP ROMs.

    Version 3.0
    • Clean Ramdisk as always :)
    • Included EXT4 and RFS (for not causing bricks) mounts on init.charge.rc
    • Start EXT4-fix in init.charge to mount syste, data, cache on inir.charge.rc and solve offline charging.

    Version 2.1
    • Cleaned Ramdisk
    • Added permissions to camfash - for CM7
    • New built from same source and config

    Version 2.0
    • Re-built ramdisk based on kissingmylove ramdisk
    • Delete all tweaks he added - BASIC KERNEL
    • EXT4 file system support for CM7
    • Hacked CWM Images to have a good color (no blues anymore)
    • Added some bootscripts to have better compatiblity with EXT4
    • Recovery has been updated to CWM 5.0.2.8
    • Mount USB mass storage is now working
    • CWM "HD" Edition, much more clear and tiny
    • Much more faster recovery

    Version 1.0
    • First release of this kernel builded from source
    • First kernel with my name on it
    • Added new modify it ramdisk
    • Compressed throug LZMA using Lopicl.00 kitchen
    • Added CONFIG_SENSORS_COOPERVE=y
    • Added all the configs necessary to use Bluetooth on CM
    • Bluetooth working on new CM7 release, which should be RC1
    • Fixed CM7 bootanimation - thanks Prototype-U

    Version 0.1
    • First release of this kernel
    • Not builded from source
    • Using Hell-lock kernel (Prototype-U) as zImage base
    • Modify lopicl.00 ramdisk and ad it to this kernel
    • Used LZMA to compress ramdisk
    • Fixed WIFI and torch on the ramdisk CM7.2
    • Not compatible with STOCK!
    10
    DOWNLOADS

    Last kernel verison download:
    http://www.mediafire.com/download/v5q74y90hg348iu/kernel_CM7_v4.0_tassve.zip

    THANKS
    BroadcomCM Team
    • Spacecaker
    • Lopicl.00
    • Kissingmylove
    • Percy-g2
    Others:
    • Savie
    • Prototype-U
    5
    Issues with the kernel:
    • SIM contacts reading
    • Sometimes CWM can not find cache/recovery/log