[KERNEL] [L-preview LPX13D] [Code_Blue r1196-L]

Status
Not open for further replies.
Search This thread

eng.stk

Senior Member
Mar 29, 2011
6,788
58,581
OnePlus 5T
OnePlus 6
Can I use Synapse with the L version, or do you guys recommend another app to control the kernel??
Synapse needs update to work with L. There's alternatives chck OP.

yes, stock rom with no modifications, and using the latest test build.

I would suggest a clean flash. Backup your stuff with TiBu for instance.

- Fastboot ROM (or use Vomer's zip), boot 1 time.
- Flash Code_Blue, flash SuperSu 2.16, boot, install busybox.
- Reboot and install your apps. I recommend people install just what needed, lot's of root and non root apps need updates to work in LP and can do unwanted behavior.
 
  • Like
Reactions: -sheldor-

marf28101995

Senior Member
Nov 6, 2012
1,137
1,598
25
Paris
OnePlus 7 Pro
Why do people keep saying this. I see plenty of people and kernels running it just fine.
Why do people keep being dumb ?I see plenty of people that know that synapse only works on L if you're using se Linux modified... Kernels that don't compromise your security like this one or fk won't work with synapse because the app need to be updated...
 
Last edited:

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,597
Why do people keep being dumb ?I see plenty of people that know that synapse only works on L if you're using se Linux modified... Kernels that don't compromise your security like this one or fk won't work with synapse because the app need to be updated...
I suggest you reading about the restrictions in L before making any kind of claim about security and calling the author of said application (yes that's me) dumb.

For anybody else having issues with SE contexts I suggest opening an issue in the tracker, but since nobody has done so I guess you have it figured out.
 
Last edited:
  • Like
Reactions: fitz420

eng.stk

Senior Member
Mar 29, 2011
6,788
58,581
OnePlus 5T
OnePlus 6
Why do people keep saying this. I see plenty of people and kernels running it just fine.
You're right and you're wrong.

I could say something similar just because it's easy: there's kernel apps that work on L and others don't.

Just kernel wise works, some full material apps even: Kernel manager, kernel tweaker, TrickstetMOD, FKU, faux kernel manager, flar2 kernel app, etc


In most cases, some popular root apps like TiBu, Root Explorer, TricksterMOD and others that didn't work updated in order to.

The deal is: when google introduced selinux in 4.3 i think, lot's of changes had to be done to root (even recoveries needed to because of permissions and security contexts). At that time selinux was in permissive mode.

In 4.4 google made selinux enforcing, which didn't create much that fuss because rules were similar, just more strict.

In L, google introduced dalvik emulation, more restrictive security contexts such as PIE, selinux rules for services and not just apps, etc.

Lollipop 5.0 was released and SuperSu was updated, some changes were done in order to make things work.
And only the needed changes.
Roots apps updated and most work fine. Even non root apps needed updates like in every other Android iterarion.


When Lollipop 5.0 preview was launched, enthusiasts made permissive selinux so all apps work without updates. That's why some kernels "work" and others don't.
I and most security concerned developers understand that chainfire path is the right one to follow.

Permissive and changing hacked binaries is fine for a initial test, but not for the long term: changes that shuts down a great deal of security don't make sense.
People need to update their apps like most of us already updated our kernels.

Hope to se UKM and Synapse on Lollipop ;)

Sent from my Lollipoped Code_Blue Nexus 5 using Tapatalk
 
Last edited:

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,597
I and most security concerned developers understand that chainfire path is the right one to follow.
I can update the call to the su binary to be called within the init context but that has absolutely no guarantee that the app will work because Synapse is a sandbox app and developers can do whatever they want within the action shells, and there is absolutely no way that I'm supposed to open up the shell in the needed context. Kernel devs have the luxury to edit selinux policies as they see fit and in the aspect of Synapse is the preferred way of dealing with things.

Trying to maintain root and selinux integrity at the same time is in my opinion a foolish quest and waste of time. If you want it to work I'm open to it and you can open a GH issue on it to discuss it, but without even knowing what other OEMs will do it's going to be a goose chase for months at an end.
 

eng.stk

Senior Member
Mar 29, 2011
6,788
58,581
OnePlus 5T
OnePlus 6
I can update the call to the su binary to be called within the init context but that has absolutely no guarantee that the app will work because Synapse is a sandbox app and developers can do whatever they want within the action shells, and there is absolutely no way that I'm supposed to open up the shell in the needed context. Kernel devs have the luxury to edit selinux policies as they see fit and in the aspect of Synapse is the preferred way of dealing with things.

Trying to maintain root and selinux integrity at the same time is in my opinion a foolish quest and waste of time. If you want it to work I'm open to it and you can open a GH issue on it to discuss it, but without even knowing what other OEMs will do it's going to be a goose chase for months at an end.

Well I did the first L kernel in xda and at the time some people said it was a waste of time. And here we are...

root has been living with selinux and other security contexts just fine for 2 or 3 Android iterations. Yes, changes were needed but everything does now or later.
I see Google and other players going this path, don't see they come around. Maybe google will loosen things up a bit or not, idk.
For instance, In the past PIE was enabled in AOSP and then disabled because of issues. Now it's back, so for me I see a pattern here.
Let's see how the scene reacts to this, but probably this won't go away. I remember CM stricken up selinux even when google was more loosen so...

About synapse I understand your point. By design, powerful and general tools tend to be more complicated to work with when ground rules change.
I brought UKM and synapse to Nexus 5 world and I can test what you need, but I don't have the time to involve actively on app development.
We have a developer in N5 original development section that tweaked UKM alot, @neobuddy89, maybe he can give a hand.
When you say edit the contexts, you mean adding files/services to the contextx files? If you can share what is needed I can try it, sure.

I think that your idea is a good place to start. Remember the essential: for me synapse and it's scripts are just a way of visually read/write tunables.
 
Last edited:

yyz71

Senior Member
Mar 27, 2011
2,563
715
Somewhere in Canada ;)
The strangest thing flashed L-preview LPX13D] [Code_Blue r1196-L] I'm using Pure•White•LightNesS-5.0™ [Lollipop] [LRX13C] [24/10/14] rebooted my phone my sdcard looked like it was touched.. still shows 11.2gb left before i flashed and after.. I just can't find anything and nandroid seems to be missing was using ElementalX-2.00-test :confused:


NVM I found it :good::D
 
Last edited:

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,597
but I don't have the time to involve actively on app development.

When you say edit the contexts, you mean adding files/services to the contextx files? If you can share what is needed I can try it, sure.
I'm not asking you to do anything in the app itself. The changes need are just a single line in the app itself but the problem is that it may vary from security policy from ROM/kernel to another and it's not possible for me to do something that is guaranteed to work for everything for exactly reasons I stated earlier. The policy is inside the sepolicy file and the contexts in file_contexts.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 138
    n9B794


    Hi guys! Here comes the first custom kernel in xda for L-preview :)

    I'm presenting my personal kernel Code_Blue, that started as an addon for Purity ROM, called Purified Kernel.
    Some of you that know me from other Nexus devices asked me to bring back the project, so I (finally) did.
    My releases are Dragon_Shield powered and I'm going to share them with you.

    All I want is full smoothness, performance and battery on my hammerhead, so I build always with Linaro optimized Cortex A15 toolchains.
    This time I aim for a "stockish" feel lean build and for stability purposes I will stay with GCC 4.9.2 for now.
    Code is based of android-msm-hammerhead-3.4-l-preview, forked from android/kernel_msm.
    Useful and powerful picks are mandatory :cool:

    Be sure to join Code_Blue users G+ community
    You keep the spirit alive!


    Kernel features:

    • Build on Ubuntu 14.04.1 x86_64 (Dragon_Shield VPS @ www.servercore.com.br - thanks @ChristianLetti)
    • Build with toolchains 2014.09 Linaro Cortex-A15 GCC 4.9.2 by @Christopher83
    • Full -Ofast+graphite support with device and target flags enhanced, linaro build improvements, etc
    • Based on android-msm-hammerhead-3.4-l-preview + own commits & cherry-picks on demand from several top devs, code aurora, linaro...
    • Kernel compressed with LZ4-r123, custom tweaked RAMdisk with GZIP (faster boot times)
    • Removed some debug and logging options
    • Enhanced performance and battery patches
    • Several CPU Governors (blu_active own governor is default)
    • Voltage Control UV_mV_table by @franciscofranco (UV down to 700mV possible)
    • Enhanced TCP methods (westwood is default)
    • Network and Wifi tweaks
    • Several I/O control (FIOPS is default)
    • Removed stock mpdecision and thermald
    • blu_plug: Dynamic hotplug for hammerhead (based in dyn_hotplug from @stratosk), with screenoff battery saving (max_freq 1190400 @ max dual core)
    • powersaver_mode available (switch usefull on light tasks, set max_freq 1728 MHz @ single core)
    • L msm_thermal by @franciscofranco
    • Optimized RWSEM, AES and SHA1 routines
    • Vibrator Strength tunable (60% default)
    • KGSL fixes and reworked GPU driver (removed doubled freqs, goes to idle @ 27MHz)
    • Gamma Control by @myfluxi, Piereligio_TrueRGBv7 profile by default)
    • LCD_KCAL driver added (RGB calibration by @savoca)
    • Tuned min manual brightness
    • OTG USB flash drives support FAT32, ExFAT and NTFS: use stickmount
    • CDROM emulation added to mass_storage (Drive Droid compatible)
    • Kexec (multirom) full support by @Tasssadar
    • Faux Sound Control, with In-call and headphone volume controls by @faux123 (must use FauxSound beta app v1.2.3 and up)
    • doubletap2wake available (0:disabled, 1:enabled, 2:enabled fullscreen), option to disable with power button or after wake_timeout (based on @flar2 and @showp1984 work)
    • USB Fast Charge (USB mode up to 900mA with MTP, by @flar2), Increase battery charging current to use higher input current (on AC mode by @faux123), proprietary charger detection
    • init.d support (busybox run-parts required)
    • Kernel cleaner script by @neobuddy89
    • Compatible with Kernel Manager, Kernel Tweaker, TricksterMOD, Franco Display Control and FauxSound Control
    • Featured on Rom Directory by @tFrost

    Download latest Code_Blue Kernel zip on Test folder, flash in recovery and profit :highfive:
    No mirrors allowed. Don't post hardlinks, use original links.
    Changelog is available @ website also.


    Builds are coded as follows:
    • test only for now on tests folder, no changelog, build with Linaro Cortex-A15 4.9.2 to minimize issues in troubleshoot.


    Warning: If you come from other kernel, you should dirty flash your ROM before flashing Code_Blue zip to avoid problems.
    Reflash ROM -> flash SuperSU -> Boot device -> flash Code_Blue.
    Also uninstall or clean data of any kernel control app you're using.


    If you like my work and wish to donate, just hit one of the buttons:
    In €

    In $



    Thanks to @franciscofranco, @faux123, @LaboDJ @show-p1984, @flar2, @anarkia1976, @stratosk, @neobuddy89, @myfluxi, @Christopher83, @Cl3Kener
    Special thanks to @DariosF and @ciprianruse88, for the friendship, initial push, knowledge and art.

    Awesome graphics and design by @ciprianruse88

    git source
    38
    Code_Blue r1196-L

    All right crew!

    Just pushed an update, Release Candidate.
    We are now at a stable point, maybe next week I will begin to push into mainline branch.
    In November, Lollipops everywhere :fingers-crossed:

    Changelog (incremental):
    Code:
    [LIST]
    [*]cpufreq: Always allow update of user policy
    [*]ARM: dts: msm: Increase OCMEM BW request for video decode
    [*]ext4: fix memory leak in xattr
    [*]msm: kgsl: Add an input handler to power up the GPU on a touch event, Allow GPU start to run in a high priority queue, Fix nice level for higher priority GPU start thread
    [*]ARM: dts: msm: increase adsp heap size for msm8974
    [*]arm/dt: msm8974: Increase "ib" values for VIDC DDR bandwidth request
    [*]net: loopback: set default mtu to 64K
    [*]gpiomux-8974: Modify direction of suspended GPIO
    [*]lower GPU volt constraints a bit
    [*]USB: Set power supply online status to false after cable disconnect
    [*]fastcharge: USB Fast Charge for Nexus 5 (USB mode up to 900mA with MTP), Increase battery charging current to use higher input current (on AC mode), Enable proprietary charger detection (e.g. iPhone/iPad charger) and treat it as AC power source
    [*]exFAT support
    [*]msm: thermal: add my Thermal solution (compatible with new L thermal framework, by franciscofranco)
    [*]Removed flash drive automount (use stickmount, ROM doesn't have mount/unmount in storage which can be dangerous)
    [*]RD Tweaks
    [/LIST]

    Get involved, test, play, donate, help, contribute.
    You keep the spirit alive!


    Keep it real, keep it true, keep it #Code_Blue
    37
    Code_Blue r1185 L-Preview

    All right crew!

    Here's the first release for l-preview LPX13D :highfive:

    I preferred to take some time to rebase and clean my source, less is more in this case!
    Hope you appreciate all the work me and my beta posse had on this release.

    I will use Chainfire root approach because it's more neutral. Doesn't mean I will not use permissive in the future, but so far my needed root apps work so I'm fine with it.
    I want to see how the community will adapt to this latest changes and we go from there.
    I prefer to maintain all the security I can get, I think root apps (and normal ones too) need to update to all the new stuff Android L: it´s just the way it is, it was like so in the past on major Android release and L is not an exception.

    Other than that I decided to remove simple gpu governor, powersaver cpu governor, fast charge and fsync toggle.
    Why? I don't use/need them ;p All the rest stays intact Blue style!

    You may have a reboot on first boot if you come from an permissive kernel.
    Changelog is at git source.

    Get involved, test, play, donate, help, contribute.
    You keep the spirit alive!


    Keep it real, keep it true, keep it #Code_Blue
    29
    Are we ready for Android 5.0 Lollipop (LPX13D)?

    Code_Blue_r1181-L-beta_hammerhead.zip created
    Build completed in 5 minute(s) and 57 seconds.

    Keep it real, keep it true, keep it #Code_Blue
    27
    Code_Blue r1034 L-Preview

    Hey guys!

    Just pushed r1034 to test folder.

    This will be the baseline for some time. I will play play awhile with franco sound, maybe we can use while faux sound is out of business.

    Changes:
    • Performance improvements and fixes
    • Tweaked intelliactive tunables
    • Enabled logger by default
    • RAMdisk tweaks

    Keep it real, keep it true, keep it BLUE
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone