I would like to thank for all help and support
Shabbypenguin, interloper, chris41g and Talustus from dream kernel team.
Now to the kernel.
This kernel is for TW (stock based) JB roms only.
It will not work/boot with any of AOSP/AOKP/CM roms.
Kernel is based on L720 MDL source.
Kernel works with MDL and MF9 roms.
Linux version is 3.4.66
Our big thanks to Talustus from Dream Team. We have full native ExFat filesystem support back.
- Build with Dream 4.7.4 optimazed tool chain.
- Available Schedulers
NOOP, CFQ, DEADLINE, ROW, SIO, BFQ, FIOPS, VR, ZEN - init.d support
- custom bootanimation support
- WiFi confirmed working.
- Auto Root
- Available governors.
Conservative, Interactive, Ondemand, Performance, Powersave, Userspace, Adaptive, SmartassH3, Wheatley, badass, slp, asswax, smartmax, intellidemand, dancedance - 64 GB ExFat SD Card support. ExFat fuse updated to latest version 1.0.1. (Talustus)
- Samsung's/MS ExFat modules.
- qcom's propritary mpdecision service disabled ( Talustus)
- OC'd to 2.1 GHz
- UC'd to 162 MHz
- Boot frequencies are set to stock.
- GPU OC to 533 MHz
- frandom module. Kernel will check for fandom module and if present will run it.
- Unsecure ADB.
- May be something else I can't recall.
Just in case someone needs or wants it here is TWRP recovery that has been modified and edited by Talustus from DreamKernel team and compiled for GS4 by me.
I don't know what edits have been done to it but I'm using this recovery for more than 2 months and didn't have a single problem with it
DREAM_TWRP.ZIP
Now back to kernels.
Here are the links:
v0.5.2
Source clean up. Cleaned ramdisk from residual exfat_fuse stuff not needed any more. Change compression method. Update to Linux 3.4.66
AGAT_GS4_v0.5.2.zip
v0.5.1
Fixed dual camera issue (Thanks Ktoonsez for tip). Update to Linux version 3.4.64
AGAT_GS4_v0.5.1.zip
v0.5.0
Update to Linux 3.4.55, enabled full native ExFat support
AGAT_GS4_v0.5.0.zip
v0.4.0
Cleaned up source. Fixed bootloop issues.
AGAT_GS4_v0.4.0.zip
v0.3.3
Update to Linux version 3.4.49. Supports MDL and MF9 based roms.
AGAT_GS4_v0.3.3.zip
v0.3.0
Fixed reboot problems. Added few governors and I/O Schedules. Lot of optimizations to list here.
AGAT_GS4_v0.3.0.zip
v0.2.2
Updated to Linux 3.4.20. Added SmartassH3, Adaptive and Wheatley governors. Unsecure ADB.
Link is temporary down pending some fixes.
Sorry.
v0.2.1
GPU OC to 533 MHz. Force kernel to boot with stock frequencies. Some source clean up.
AGAT_GS4_v0.2.1.zip
v0.2.0.
OC/UC 2.1 GHz/162 MHz. Added ExFat file system support. File system is supported has been tested on 64 GB card.
AGAT_GS4_v0.2.0.zip
v0.1.9
Added framdom module. Kernel tested. Module works.
AGAT_GS4_v0.1.9.zip
MDL Root.
This kernel has been compiled with stock MDL source without any additions to it except auto root.
You can flash this kernel over full stock MDL firmware via ODIN and it will give you root.
Wifi is working and 64GB exfat card should be supported as well.
AGAT_GS4_MDL_ROOT.tar
v0.1.8
Added auto root to kernel. On boot it will check if su binary is present and if not it will flash su and superuser.apk.
So if for any reason you loose your root simple reboot will fix that.
AGAT_GS4_v0.1.8.tat flash with odin. Can be flash on fully stock rom and that will provide root.
AGAT_GS4_v0.1.8.zip flash in recovery.
v0.1.6
Added voltage control table. It shows up and works with system tuner.
AGAT_GS4_v0.1.6.zip
v0.1.5
Update to Linux 3.4.10. Added fast charge (hopefully it works). Minor edits.
No 64Gb exFat support.
AGATgs4_v0.1.5.zip_
v0.1.4
Upgrade to Linux 3.4.6. Fixed the wifi issue. It works now. Intruducing ROW scheduler has changed kernel symbols. So 2 versions of dhd.ko
were in conflict. That has been fixed but till we figure out a way for Kernel to load it's own modules our option to flash is limited to CWM zip
files only.
AGAT_GS4_v0.1.4.zip
v0.1.3
Added ROW scheduler. This scheduler was specifically written for mobile devices and ROW stands for Read Over Write.
Did work very well with Ktoonservative governor on GS2 and GS3.
AGAT_GS4_v0.1.3.tar
AGAT_GS4_v0.1.3.zip
v0.1.2
Build on new MDL source released by Samsung.
Updated to Linux 3.4.4, added SIO scheduler. Added modified Ktoonservative governor.
AGAT_GS4_v0.1.2.tar
AGAT_GS4_v0.1.2.zip
v0.1.1. L720 source build.
Update to Linux 3.4.4. Added SIO I/O scheduler
AGAT_GS4_v0.1.1.tar
AGAT_GS4_v0.1.1.zip
v0.1.0 (i9505 source build)
AGAT_GS4_v0.1.0.tar
AGAT_GS4_v0.1.0.zip
Installation instructions:
You can flash the zip file in any working recovery.
Tar file can be flashed with ODIN or
You can pull the boot.img out of either of the files and use heimdall to push it to phone.
I have tried the zip in recovery and heimdall method only. Have not flashed with PC ODIN.
For now to get rid of that nasty pop up message I've used the BloatwareFreezerFree app from play store.
In System bloatware find seandroid and freeze it. You can use any other app that's capable to freeze system apps.
Please report any issues and/or problems here so we can try to fix them.
my source can be found here:
https://github.com/agat63/AGAT_L720_kernel
(use MDL_Test branch).
Thanks
Sent from my PG86100 using Tapatalk 2
After installing the kernel, I get a "Detection information" pop up message saying "The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot." then I have 2 options, reboot now, or reboot later. Reboot now, takes me back to CWM where I get:
E: Invalid command argument
E: Invalid command argument
Any suggestions, I flashed via the zip you've provided.
jsmcmahon89 said:
After installing the kernel, I get a "Detection information" pop up message saying "The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot." then I have 2 options, reboot now, or reboot later. Reboot now, takes me back to CWM where I get:
E: Invalid command argument
E: Invalid command argument
Any suggestions, I flashed via the zip you've provided.
Click to expand...
Click to collapse
I get the same message. I wasnt sure if it was root causing it or the kernel because I flashed stocked rooted rom and kernel at the same time.
Sent from my Samsung Galaxy S4 using Tapatalk 2
jsmcmahon89 said:
After installing the kernel, I get a "Detection information" pop up message saying "The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot." then I have 2 options, reboot now, or reboot later. Reboot now, takes me back to CWM where I get:
E: Invalid command argument
E: Invalid command argument
Any suggestions, I flashed via the zip you've provided.
Click to expand...
Click to collapse
Highway 55 said:
I get the same message. I wasnt sure if it was root causing it or the kernel because I flashed stocked rooted rom and kernel at the same time.
Sent from my Samsung Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Not to defend the kernel or so.
It's first attempt and based on different source but this has been found on the web:
http://teamuscellular.com/Forum/top...an-application-attempting-unpermitted-access/
It's not just our device or may be it has been triggered by the source I uses.
Both is possible.
This is just FYI.
I'll continue work with this source till official SPH-L720 dropps on sammies site.
Thanks for feed back.
Just checked Samsung's site and source for SPH-L720 is available.
I'll try to make a new kernel tonight with the right source and we will see if that
annoying pop up message will go away.
Removed duplicated message.
jsmcmahon89 said:
After installing the kernel, I get a "Detection information" pop up message saying "The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot." then I have 2 options, reboot now, or reboot later. Reboot now, takes me back to CWM where I get:
E: Invalid command argument
E: Invalid command argument
Any suggestions, I flashed via the zip you've provided.
Click to expand...
Click to collapse
settings >>> more >>> developer options >>> uncheck "verify apps via USB" >>> profit.
if developer options aren't listed in more you'll need to enable them:
settings >>> more >>> about device >>> tap "build number 7 times" >>> do the above >>> profit.
A little more insight: This is caused by the app "SEAndroid" or "security enabled android" aka big brother seeing that you're playing with the kernel. you can either freeze the app in TiBu or do the above proceedure. Both will accomplish the same result.
rawintellect said:
settings >>> more >>> developer options >>> uncheck "verify apps via USB" >>> profit.
if developer options aren't listed in more you'll need to enable them:
settings >>> more >>> about device >>> tap "build number 7 times" >>> do the above >>> profit.
A little more insight: This is caused by the app "SEAndroid" or "security enabled android" aka big brother seeing that you're playing with the kernel. you can either freeze the app in TiBu or do the above proceedure. Both will accomplish the same result.
Click to expand...
Click to collapse
I tried that.
Still getting the pop up.
Did force stop and disable the SEAndroid app as well.
No dice.
Since I start seeing this pop up with source build kernel and never had seen it before and users from other thread are having that pop up with stock kernel I hope the problem is in the kernel source.
If so with right source it should go away.
agat63 said:
I tried that.
Still getting the pop up.
Did force stop and disable the SEAndroid app as well.
No dice.
Since I start seeing this pop up with source build kernel and never had seen it before and users from other thread are having that pop up with stock kernel I hope the problem is in the kernel source.
If so with right source it should go away.
Click to expand...
Click to collapse
odd. it totally fixed my issue. I've never seen the message again.
agat63 said:
Just checked Samsung's site and source for SPH-L720 is available.
I'll try to make a new kernel tonight with the right source and we will see if that
annoying pop up message will go away.
Click to expand...
Click to collapse
Very nice. ty
Build the kernel with L720 source.
Kernel name is now showing correctly but the nasty pop up is still there.
Trying to find out if I can disable it from the source.
agat63 said:
Build the kernel with L720 source.
Kernel name is now showing correctly but the nasty pop up is still there.
Trying to find out if I can disable it from the source.
Click to expand...
Click to collapse
Can you link the source you're using?
---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------
NVM I grabbed it from the OSRC.
agat63 said:
Build the kernel with L720 source.
Kernel name is now showing correctly but the nasty pop up is still there.
Trying to find out if I can disable it from the source.
Click to expand...
Click to collapse
I started a thread in Q&A about removing bloatware. Somebody directed me to this link: http://forum.xda-developers.com/showthread.php?t=2210784 After removing a lot of the .apks listed in the OP of that thread I no longer get the warning message. I do not know which app was causing it, but I havent gotten the message for almost 3 hours. I was previously getting it every 5 minutes.
I do realize that this is probably only a bandaid fix, and that the kernel is the source of the problem (pun intended).
Sent from my SPH-L720 using Tapatalk 2
Highway 55 said:
I started a thread in Q&A about removing bloatware. Somebody directed me to this link: http://forum.xda-developers.com/showthread.php?t=2210784 After removing a lot of the .apks listed in the OP of that thread I no longer get the warning message. I do not know which app was causing it, but I havent gotten the message for almost 3 hours. I was previously getting it every 5 minutes.
I do realize that this is probably only a bandaid fix, and that the kernel is the source of the problem (pun intended).
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Check to see if SEAndroid is still there. I'm betting it isn't. Look in TiBu
rawintellect said:
Can you link the source you're using?
---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------
NVM I grabbed it from the OSRC.
Click to expand...
Click to collapse
you can find source on:
opensource.samsung.com
type the phone name in top field and start search.
sph-l720
Version v0.1.1 is up and running.
OP updated links posted.
Kernel is based on L720 source by Samsung.
Wasn't able to get rid of that pop up tho.
For now to get rid of of that message I've used the BloatwareFreezerFree app from play store.
In System bloatware find seandroid and freeze it. You can use any other app that's capable to freeze system apps.
You can use any other app that is capable of freezing system apps.
I'll continue my attempts to find where and how it triggered and hopefully can fix it soon.
Till then we will have to freeze the SEAndroid app.
Running smooth for me buddy. I haven't gotten any pop up yet. What does the pop up say?
opz187 said:
Running smooth for me buddy. I haven't gotten any pop up yet. What does the pop up say?
Click to expand...
Click to collapse
A warning about some app attempting unpermitted access and suggesting reboot.
You can dismiss the message as well but it comes up every few min.
At least on my phone.
But I have flashed so many things (not exactly working) and so many times that it might be my phone by now and not common.
agat63 said:
A warning about some app attempting unpermitted access and suggesting reboot.
You can dismiss the message as well but it comes up every few min.
At least on my phone.
But I have flashed so many things (not exactly working) and so many times that it might be my phone by now and not common.
Click to expand...
Click to collapse
Yea I been running it now for about an hour with no message. Every thing is smooth as butter
Related
Well, the time has come that I think my kernel is ready for public consumption.
THIS IS ONLY FOR THE USA VERSION OF THE GALAXY PLAYER 5.0 (YP-G70). If you have a mechanical home button instead of capacitive buttons at the bottom, do not flash this (rumirand has a kernel for you)! If you have a 4.0, do not flash this (SteveS has a kernel for you)!
Read the first three posts of this thread COMPLETELY before asking questions - if you ask a question that is answered in the first three posts, you WILL be flamed.
I'm continuing my Daily Driver name, even though it isn't as good of a name as it used to be. It is my daily driver - but what kernel dev doesn't use their own kernel as a daily driver? It made more sense in the Infuse days when I was running my own unreleased kernel for months and a few people asked for it. Oh well, I'm lazy - same name for now.
This is going to be maintained in the same manner and spirit as my other Daily Driver releases for the Samsung Infuse and Samsung SGH-I777 (AT&T Galaxy S II) - http://forum.xda-developers.com/showthread.php?t=1212795 and http://forum.xda-developers.com/showthread.php?t=1289460
It is built from sources at https://github.com/Entropy512/linux_kernel_galaxyplayer and initramfs at https://github.com/Entropy512/initramfs_yp-g70
Current features:
coolbho3k's Samsung Sleep of Death patch - allows stable use of screen-off profiles with limits below 800 MHz in SetCPU
netarchy's conservative governor tuning patch - Reduces the polling interval, allowing conservative to ramp up/down faster. Over in I9100 land they're calling this "lionheart" and it's all the rage. (It makes me sad when people won't accept a governor until it's renamed and hyped up way beyond what it is...) As an example, a GSII would take 0.4 seconds to ramp from 200 to 1200 MHz with the default conservative governor, it can go all the way in 0.1 second with this patch.
conservative set to default governor - use SetCPU or a similar app to change it
jhash3
TinyRCU
CIFS and Tunneling modules included
ext4 partition mounting support in kernel and initramfs thanks to rumirand - ghetto Lagfix baby!
CWM 5.0.2.7 based recovery - Mostly tested, seems working, but may have a few bugs still to work out, rumirand helped a lot on this one
Insecure kernel - gives you automatic root in ADB shells
Per-file fsync() disable capability - see "dangerous features" documentation below
Standard bootanimation (/system/media/bootanimation.zip) support
Charginghacks - faster charging at low battery, slightly slower near the end, overall faster charging while trying to minimize battery stress
CPU core voltage control - use SetCPU or a similar app
CPU overclock to 1.2 GHz - use SetCPU or a similar app
Planned features, short-term:
Pull a few other bugfix commits from my other kernels
Clean up CWM implementation
Planned features, mid-term:
Proper Voodoo Lagfix support (Automatic partition conversion instead of manual)
Planned features, long-term:
Overclock beyond 1.2 if people prove they can handle 1.2 with maturity (Infuse community couldn't handle any OC in a responsible manner...)
Features not planned:
Anything that has a high risk of trading off stability for performance, unless it can be completely disabled by default
Alternative governors - They almost always cause wacky behavior in some cases, and they don't offer anything that can't be done with a combo of SetCPU profiles and tuning the conservative governor now that the minimum poll rate has been dropped.
How to flash .tar releases:
Linux/MacOS:
I forgot that Heimdall doesn't like this particular device - you will need to use a Windows virtual machine with USB passthrough support (like VirtualBox) and Odin, or root the device using the zergRush exploit and follow the "rooted device" instructions. (Ambrice has a fixed version of heimdall, but it must be compiled from source. If you know how to do that you don't need tips on how to use it. )
Windows:
Enter download mode - Power off your device completely, hold VolDn, and insert the USB cable
Use Odin - Google it or search these forums for details - try AdamOutler's resurrector thread in this Development forum
Any rooted device:
Extract the zImage from the .tar file of the release. On Linux, it can be the following (which should work in an ADB or Terminal Emulator shell on the Player itself.)
Code:
tar xvf <releasefile>.tar
From a shell with root access (ADB or Terminal Emulator), do the following:
Code:
dd if=zImage of=/dev/block/mmcblk0p11
How to flash .zip releases:
Put it on your sdcard, enter CWM, flash the .zip using CWM
If you do not have CWM, install an older .tar release then flash, or follow the "Any rooted device" instructions above, but extract the zImage from the .zip instead of a .tar
3/5/2012 Release:
Overclocking to 1.2 GHz (use SetCPU or a similar app to enable)
Support for running scripts in /system/etc/init.d
3/3/2012 Release:
Voltage control (no overclock yet, coming next)
1/29/2012 Release:
charginghacks from Infuse: Charging current on a wall adapter raised to 800 mA at lower battery, dropping to 700, then 600 (stock), then 550 (slightly below stock) as battery voltage reaches maximum. This gives overall lower charge times while trying to not stress the battery too much.
Also, final charge termination happens earlier - while this results in slightly less battery capacity per charge, it will help the battery retain capacity over time.
1/23/2012 Release:
Initramfs: Standard bootanimation support. Place a standard bootanimation in /system/media/bootanimation.zip - Note: The "stock" bootup sound still plays.
1/22/2012 Release:
A few bugfixes and power management improvements pulled in from other kernels
Ability to disable per-file fsync() - good for benchmark epeen, potentially dangerous for your data
1/14/2011 Release:
Initial release
FAQ
Q: Why does CWM default to my external SD card for backup/restore/flashing ZIPs?
A: This is the standard for Android devices going forward - internal on /emmc and external on /sdcard
Q: How do I enter CWM?
A: Until ROMs come out that have extended power menu mods: Power off your device, then:
Hold VolUp
Hold Power
Release Power when the SAMSUNG screen appears (continue holding VolUp)
Release VolUp when CWM appears
Q: I'm still not rooted?
As stated in the features, an insecure kernel only provides root in an ADB shell. Either use ADB to push /system/bin/su and /system/app/Superuser.apk and chmod them to the correct permissions, or take the easy way out and flash ChainsDD's Superuser package in CWM - http://androidsu.com/superuser/
Q: I used ROM Manager to do something, and something weird happened/went wrong. Why?
A: ROM Manager has not worked properly on any device I have ever owned. It softbricked any Infuse that had Voodoo Lagfix enabled, and never works properly on the SGH-I777. The only thing I've ever seen it do right was install gapps on CM7 on the I777.
Q: My battery will never charge past 80%, why?
A: The way Samsung estimates state of charge on our devices is extremely primitive and, in general, poor. Instead of a dedicated fuel gauge IC, they have tried to estimate battery directly from voltage with some funky compensation offsets depending on current operating state - the offset for wall charging is so high that it is impossible for the battery to read higher than 80% when on a wall charger unless you're putting the device under heavy load to activate some of the other compensation offsets. Sometimes it seems like the compensation code doesn't "kick in" when plugging in a charger, allowing you to see a higher number, other times it'll get "stuck on" even after removing the charger. The general thing, though, is that any percentage estimates of battery state are WILDLY inaccurate.
Q: Can you implement Voodoo Sound?
A: No - We have the same audio chip as the Galaxy S2 and Galaxy Note (Yamaha MC1N2) - Voodoo Sound requires a Wolfson WM8994.
Documentation on "dangerous" features:
Per-File fsync() disable:
This allows you to disable per-file write forced syncs. (e.g. if an app tries to force a write straight to disk, it'll just go to cache). This achieves the same goal as the modded sqlite hacks seen in tweaks such as USAS, however it can be disabled at runtime.
WARNING: THIS CAN CAUSE DATA LOSS OR CORRUPTION IN A CRASH
To enable, do the following in a terminal, or add it to an init.d script (look at my ondemand script as an example):
Code:
echo "1" > /sys/module/sync/parameters/fsync_disabled
And to disable (return to the default):
Code:
echo "0" > /sys/module/sync/parameters/fsync_disabled
Good for around 200 points of epeen in the database benchmarks in Antutu or 500-600 points of epeen in Quadrant. Real-world benefit: Probably not worth the data integrity risk, but you've got a choice now.
*reserved for whatever the heck I forgot above*
Thanks a ton Entropy512!! Been waiting for this.
Going to have to buy you a six pack via the Donate button!
Congrats Entropy512. I'm really thankful for your cooperation.
Its finally here!! Thanks so much entropy
Nice job entropy! Good to see that there is at least some development going on for these devices. This makes me wish I got a 5.0 instead..but I'm stuck with a 4.0.
Sent from my YP-G1 using Tapatalk
Thank You
I myself along with others appreciate you developing for the Galaxy Player 5.0 it is a great music player and it falls in the Galaxy family its a good device
Sent from my Galaxy Nexus using Xparent Blue Tapatalk
Says we can use Odin...do see put this in a phone or pda slot
Zei said:
Says we can use Odin...do see put this in a phone or pda slot
Click to expand...
Click to collapse
PDA - only modems go in phone I believe.
Just like flashing any other kernel in Odin.
Edit: CRAP I have Heimdall instructions but Heimdall won't work on the Player... I'm so habitually used to Heimdalling...
Would a factory stock image + root + this be good enough to post if done w/ the backup/restore feature?
Zei said:
Says we can use Odin...do see put this in a phone or pda slot
Click to expand...
Click to collapse
Yes when you use odin you will need to put the rom in PDA slot.If yiu use heimdall you will need to extract and flash the files separatly.
I hope this helps.
---------- Post added at 11:53 AM ---------- Previous post was at 11:53 AM ----------
Entropy512 said:
PDA - only modems go in phone I believe.
Just like flashing any other kernel in Odin.
Edit: CRAP I have Heimdall instructions but Heimdall won't work on the Player... I'm so habitually used to Heimdalling...
Click to expand...
Click to collapse
Heimdall does work on the player. I use it.
Hmm... odd, I tried to use it and it gave me some odd errors I've never seen before (I forget what at the moment) and then put me into forced download mode. I know a pit-dump has some rather odd looking results. Maybe if I just try and flash a kernel it will work.
I'll try again later today, and edit the instructions if it works.
I have my Player shut off for most of today - I've been having strange battery drain problems on my GSII for the past week or so, only when at home - and it seems like it started when I got the Player. So I'm shutting it off to see if it actually is affecting my phone.
Edit: Heimdall still isn't working for me
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...
After I flashed your kernel it won't let me connect to the market, my Wi-Fi is turned on and I connect to the browser just fine but not the market, help?
That's strange - no problems with market connections here. (Edit: Just updated BetterBatteryStats...)
Try rebooting?
Or wait a bit - sometimes the Market just goes down.
Entropy512, I've been studying your github and how you enable ext4 support in the kernel. Could you explain how you did it? I know it has to do with editing "/ arch / arm / configs / yp_g70_usa_defconfig" but I can't find that file in samsung's source or on Steve'S github. And after you do that you just edit the mount points in init.rc, right? I'm asking because I'm gonna try to get ext4 (lagifx) for my 4.0!
Thanks.
P.S. sorry if I'm a noob
klin1344 said:
Entropy512, I've been studying your github and how you enable ext4 support in the kernel. Could you explain how you did it? I know it has to do with editing "/ arch / arm / configs / yp_g70_usa_defconfig" but I can't find that file in samsung's source or on Steve'S github. And after you do that you just edit the mount points in init.rc, right? I'm asking because I'm gonna try to get ext4 (lagifx) for my 4.0!
Thanks.
P.S. sorry if I'm a noob
Click to expand...
Click to collapse
yp_g70_usa_defconfig was copied from venturi_usa_defconfig prior to modifying it - I decided to start maintaining my own defconfig rather than overwriting the original one.
Galaxy Player 4.0 is palladio instead of venturi. SteveS also uses a renamed defconfig though - something like steves_blahblahblah_defconfig
To change things for a 4.0, it would be something like
Code:
make steves_blahblahblahwhateverthisis_defconfig
make menuconfig (enable ext4 support in the menus here)
cp .config arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git add arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git commit
Entropy512 said:
yp_g70_usa_defconfig was copied from venturi_usa_defconfig prior to modifying it - I decided to start maintaining my own defconfig rather than overwriting the original one.
Galaxy Player 4.0 is palladio instead of venturi. SteveS also uses a renamed defconfig though - something like steves_blahblahblah_defconfig
To change things for a 4.0, it would be something like
Code:
make steves_blahblahblahwhateverthisis_defconfig
make menuconfig (enable ext4 support in the menus here)
cp .config arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git add arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git commit
Click to expand...
Click to collapse
Cool thanks! Will definitely try it out.
SleekAI kernel for the LG G Pad 8.3 V510 (GPE)
Updated 1-22-2015 CURRENT Sleekai8.1
Both kernels updated to Fsync off (again) and a couple of small changes to code. Also changed the versions to match numerically.
Also added a new 88sleektweaks file for init.d that has preset values for voltage control undervolting, See second post for instructions and zip file. Use Trickstermod if you want fsync on.
Both Lollipop And Kitkat Versions
(Lollipop version also works with CyanogenMod12)
Features:
Flash Through Recovery!
Interactive Governer as default
Row IO Scheduler as default
Wheatley Governer added as option (Lollipop only)
Knock_on enabled by default (Lollipop) or with
My app in the third post down (KitKat)
Sweep2Sleep enabled as an option
LCD screen control using Trickster Mod
Compiled using Linaro Toolchain cortex a15-4.9.3
o3 Compile optimizations
init.d support (zip align, etc...)
Faux Sound Control added
USB Fast Charge added
Frandom replacing Urandom
Fsync On/Off using Trickstermod
Tethering for bluetooth and usb
Exfat support for sdcards
User Space Voltage Control TricksterMod to change
Five new IO schedulers for Lollipop! Trickstermod to change
And more!
The kernel source and Commits that show the changes used for sleekai can be found here: Github
Prerequisites
Unlocked bootloader
Root
Install Busybox for init.d support
TricksterMod is recommended for changing settings
How does this work?
Start by making a backup of your boot in recovery, then:
Flash the latest version in Recovery . Proceed to the downloads below, download to your tablet, reboot into recovery and install the zip --That simple!
if you want to build your own kernel start to finish with complete instructions, you can follow my guide for rolling your own kernel HERE
Please hit "Thanks" to show your support!
DOWNLOAD HERE:
ATTACHED FILES
TO USE INIT.D SUPPORT ON YOUR DEVICE
Busybox must be installed for the init.d support file to work! (in the playstore)
You will need to add a folder named init.d to /system/etc/ in order to use this support
One example is to have your apps zip aligned on boot.
Another is to use my 88sleektweaks script to save battery
This includes undervolting values that you can adjust as neccesary, and a few WiFi tweaks.
Unzip the file to reveal the zip-align script. Then:
Copy the script to your /system/etc/init.d folder, change the permissions if needed, and reboot. Thats it!
You can tell you have it right by looking in /data for the zip align db files after you reboot.
You should change your permissions on any file in init.d to rwx r-x r-x (755)
Sleektoggle - For Knock_on and Sweep2Sleep
I made a small application using tasker that will enable Knock-on and Sweep2Sleep on devices using the kitkat kernel.
Knock-on is enabled by default in my Lollipop kernel - no app required.
The application works as a toggle, and will need to be "enabled" after every boot to use these features.
This is for your protection, as knock-on will freeze your device if enabled before or during boot.
This keeps you from having to enable these manually by adjusting the files yourself.
The knock-on feature should work on ANY 510 device, as it is native to the device.
To use:
Download and install the apk.
Put the icon from your apps somewhere on your home screen
after boot/reboot, press the icon, allow root privilages, and you are done!
You should only need to enable root the first time.
To use the features:
Simply knock twice in the center of the screen to wake up your device from standby
To put it to sleep, swipe from right to left on the lower portion of your screen.
Pressing the icon a second time does not disable the features. Restarting your device does!
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
edru said:
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
Click to expand...
Click to collapse
Excellent! You can expect the first reboot to be slow, as well as the first opening of some apk's as the kernel repopulates the files. Let me know!
A lone V510 dev emerges!!! Thank you!
Sent from my LG-V510 using Tapatalk
-Updated kernel for ability to pull the .config from the device, and shorter idle time before sleep.(battery saver). With this comes an updated name change to sleekai2.
--Update--
Kernel recompiled using the latest Linaro toolchain 4.9.3
Gamma corrected on the tablet with no further optimization needed
And the latest Antutu benchmark for the 510 with the latest Lollipop kernel: 31,526 See attachments.
going to give this a go right now.
---------- Post added at 01:57 PM ---------- Previous post was at 01:49 PM ----------
Gamma looks GREAT!
nice job sir. Thank you.
Just flashed on my V510. Thank you so much for your hard work!
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
this is awesome! It feels like a brand new device!
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
schalmers said:
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
Click to expand...
Click to collapse
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
kdog350 said:
this is awesome! It feels like a brand new device!
Click to expand...
Click to collapse
Excellent! Glad to hear it!
general_z said:
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
Click to expand...
Click to collapse
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
-Update-
Kernel Added
Changelog 22 Feb 14
general setup-perf-changed to sleekai3
compiled with -o2 for optimization of code/better battery life, maybe.
general setup-kernel log buffer size changed to 14
Note* sleekai3 is pretty much the same thing as sleekai2 except the specific use of the optimize flag for the gcc compiler. Does it really change anything? Don't know yet. Wouldn't worry about changing unless you just can't resist. If I see noticable battery savings I'll let ya know. Of course, changing is easy too . . ..
sleekmason said:
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
Click to expand...
Click to collapse
How thoughtful of you. In what file(s) is the gamma fix or where is the changelog that shows it?
I'm thinking that It may be quite easy to just to mod another kernel for the v500 and put it in (like dyn.Kernel v3).
sleekmason said:
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
Click to expand...
Click to collapse
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
schalmers said:
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
Click to expand...
Click to collapse
Yes, I did the fix as well. The sleekai3 is only the optimized sleekai2 (using flag -o2), so there really is not much difference.
SO, here we go, I looked up problems with the 64 bit card as I remembered reading something about them in a samsung forum. What I found this time I searched was here: http://forum.archosfans.com/viewtopic.php?f=84&t=66346 and here in our own forum: http://forum.xda-developers.com/showthread.php?t=2575043
Basically what "they" say is that the Sandisk 64 bit cards have issues with exfat. The solution is to format in fat32. you lose a gig or two with the different format, but it works. The above link also suggests ext4 as an option, but it will not work on our device, neither will ext2. At least not mine!
Long story short is to copy your files to your computer, reformat to fat32 and put them back!
The longer story is of more interest to me. As sleekai3 is based off the original kernel source for the 510, and because I have made no changes to areas that should/could effect the reading of your card, WHY does the stock kernel you have allow it? (yes, I switched it and am assuming it is unreadable by every kernel for the sake of argument.)
This is entirely a permissions issue as far as I know. frustrating. One thing I cannot do with my card is download a file, say a zip file, to my external sd card. I can copy it after it's downloaded, I can use link2sd with no problem, everything shows up well. This indicates the need for root access by Dolphin Browser.
I had thought to edit the fstab file and simply add "users" to the options but that doesn't work. I also tried many variations of the fix in the /permissions/platform.xml as well.
I'm going to have to study permissions for the device and see what I can do to fix it for everybody if I can. I'm afraid that adding the card to root could allow for an exploit. maybe.
Anyway, reformat to fat32 and let me know how it goes! regards, sleekmason
[kernel][v3.5] leanKernel: minimalistic kernel (1/28/16)
leanKernel is not for everyone.
My philosophy is to keep the kernel footprint as small as possible by trimming as much fat as possible, and at the same time keeping it stable, power efficient, and fast. leanKernel is designed to be a drop in replacement for stock kernel, and so it tries not to deviate too far from stock.
You will find that it's lacking some of the bells and whistles of other custom kernels, so if you like features you came to the wrong thread.
Here's a longer post on what leanKernel is about.
Also folks, please read the FAQ before asking questions.
INSTRUCTIONS
If you like to stay as close to stock as possible: 1) Download and flash the normal leanKernel build here (find the latest zip file) in recovery. 2) Reboot and enjoy better performance and battery life (hopefully). That's it! There's no need to flash stock kernel first, or to wipe caches.
If you like to customize, read through the feature list below, the FAQ (post #2), the changelogs, and optionally the entire thread. Then you'll know what to do.
DOWNLOAD (flash in recovery)
v1.x is for Android 5.0, and v2.x is for Android 5.1
main download
mirror (may need to refresh browser to see latest)
PREREQUISITE
Unlocked bootloader, custom recovery installed
Push bullet channel: imoseyon
FEATURES
custom voltage control - use your favorite app
updated to latest 3.10 Linux
interactiveX - screen_off_maxfreq support (default 2.2Ghz)
sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)
latest Linaro gcc 4.9 toolchain (optimized for a15 - thanks to Christopher83)
fat trimmed and various performance tweaks
f2fs support (updated to latest source from Samsung)
force encryption turned off (changed to encryptable)
overclocked to 2.9ghz (experimental - available as a separate build for now)
underclocked to 223mhz (experimental - available as a separate build for now)
Async Fsync
init.d support
cpu-boost control - enable/disable via lkconfig
lkconfig script for customizing leankernel (open terminal app, become superuser, then type "lkconfig" without quotes)
patched mpdecision to prevent changing min/max freq provided as flashable zip (in util directory)
color control (thanks to @savoca)
charging led support
a lot of unnecessary stuff removed from stock kernel
some components updated to Linux 3.18
random generation optimization including e/frandom support
pc/usb charging with boosted current ~300-400mA
some selinux fixes, selinux is enforced by default - staying true to stock (you can easily disable using lkconfig)
SLUB allocator updated to Linux 3.18
wake gesture control from flar2, modified for leankernel (also disabled in-call)
vibe strength control
much of the code is up to date with latest from CodeAurora
(mostly for devs) /sys/module/selinux/parameters/force_audit sysfs node to audit all/hidden selinux denies.
power aware cpu scheduling
faux sound enable/disable by sysfs (and lkconfig)
wakelock control (smb135x, wlan_rx, msm_hsic and sensor_ind)
leanKernel core control script
user option to prevent mpdecision/msm_thermal from changing min/max frequencies: frequency mitigation preventer
supports kexec for multirom
LKCONFIG
You can use lkconfig script to make custom changes to leanKernel (along with popular apps like Kernel Tweaker and Trickstermod). To run lkconfig, open terminal app, "su" (without quotes) to become superuser, enter, and then type "lkconfig" without quotes, then enter.
Code:
[email protected]:/ $ su
[email protected]:/ # lk
leanKernel configurator
---
0) display current settings
1) cpu frequency control
2) wake gesture control
3) wakelock control
4) charging led
5) rgb/picture control (advanced)
6) rgb/picture control (simple)
7) vibe strength
8) power saving mode for cpu scheduler
9) faux sound control
10) selinux mode
11) min/max freq change prevention
21) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit):
CHANGELOG
https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog
Thanks to @guitarshredder87, @Wera750, @akellar, and @grisha1 for testing test builds!
XDA:DevDB Information
Leankernel: Minimalistic Kernel, Kernel for the Nexus 6
Contributors
Imoseyon
Source Code: https://github.com/imoseyon/leanKernel-shamu
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-26
Last Updated 2016-01-31
FAQ
I'm having trouble waking the phone sometimes. Help!
We haven't really figured out exactly what's causing it - but there seems to be evidence that it's not limited just to leanKernel. One thing to try: if your ROM has a feature that prevents accidental wakeups, disable it!
I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?
* Read this post: http://forum.xda-developers.com/showpost.php?p=58135730&postcount=1474
* Short version: This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.. Launch lkconfig, choose core control, and choose one of the options in core control.
Will flashing leankernel decrypt my phone storage?
If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you format data. Once you format you will stay decrypted until you decide to encrypt again (see below). If you're already decrypted, leanKernel will not force encrypt automatically.
What do I do to encrypt again?
There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):
Code:
[email protected]:/ # start encrypt
You will see the phone hot boot and once it comes up you will be encrypted again. Keep in mind that if you want to decrypt again you'll have to wipe.
How do I check the PVS BIN of my cpu?
Code:
[email protected]:/ # cat /proc/cpu/msm_acpu_pvs
The number you get should range between 0 and 15 (inclusive). If you ended up with 15 congratulations. If you ended up with 0, go get it exchanged! Stock frequency/voltage table: http://pastebin.com/ZyGA9Tec
Which kernel control app do you recommend?
When v1.0 gets released it should come with "lkconfig" for tweaking some of the options. Otherwise, I tried Trickster and KernelTweaker, and they both seem to work ok.
What are ondemandX and interactiveX?
ondemandX and interactiveX are very very close to "stock" ondemand and interactive governors, respectively. The only difference is screen_off_maxfreq sysfs support. This means that it gives you the ability to limit phone's max frequency when screen is off. This feature could be effective in reducing battery usage, especially if you have a misbehaving app (or two) that consume cpu cycles while screen is off. The default value is 2265600 - if you change the value to your top speed you're effectively disabling the feature and restoring stock behavior completely. You can use an app like Trickster or Kernel Tweaker to modify screen_off_maxfreq.
HELP! I messed up with lkconfig - how do I go back?
Do not fret. Flash lkconfig_cleaner.zip from the "util" directory.
(If you want to do this manually), reboot the phone into recovery, mount /data, and delete everything in /data/data/leankernel. Once things are back to normal, re-run lkconfig to re-do your settings.
What is cpu-boost?
Read this post: http://forum.xda-developers.com/showpost.php?p=57215289&postcount=535
What is the best RGB setting?
http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620 (old)
http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017 (new)
What is power aware scheduling?
Read this post: http://forum.xda-developers.com/showpost.php?p=58313978&postcount=1651
I missed your kernel when I switched to N5. Glad to have you here
hmm.. a kernel. since its the first one posted here, im trying it out
Hell yeah. Ready to flash
Sent from my AOSP on Shamu using XDA Free mobile app
If I flash this it will decrypt right cool
digweed4me said:
If I flash this it will decrypt right cool
Click to expand...
Click to collapse
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
What app should we use to control? I remember you used to have your app right
holy **** Imoseyon. you made my Thunderbolt usable way back when. so glad to see you developing for the N6 now
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
Flashed it and yes decrypted thanks a lot
IMO!! Good to see ya again man. Can't wait to run your work again.
Appreciate it!
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
You mean lkconfig? Yeah that's coming later (along with a whole lot more).. If you're talking about f2fs, you'd want to use custom recovery but TWRP for shamu doesn't support f2fs yet - i had to do everything manually.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
i am still encrypted, and did not decrypt after flashing. so, all worked as it should.
Can we flash on stock ROM or is a custom ROM required?
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
I'm on a stock ROM.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
AFAIK, there's no way to decrypt without having to wipe unfortunately. Going the other way (unencrypted to encrypted) is super easy though, and no data loss.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
im on rastapop, an aosp based custom rom.
simms22 said:
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
Click to expand...
Click to collapse
Thanks for your quick response. Wipe what tho? Cache, dalvik, and what else? Hope you don't mean all my data.
You don't buy a Mustang for the gas mileage.
This is a kernel module that disables write protection on the system partition while running the stock kernel.
This module was written by @far2 for the htc one M8 and Desire 816 its source code can be found on his git here: https://github.com/flar2/wp_mod
So credit goes to him.
I have just checked to see if it would be compatible and compiled it against A3UL 1.31.401.3 kernel source. It has been tested to load and work fine with all stock kernels.
This is for stock kernels only and is of no use if you are running JMZ kernel. It will allow you to keep your stock kernel (for better compatibility across regional rom versions) but same as JMZ kernel it allows you to modify the system partition and install mods and fixes that will stick through a reboot without having to do them through recovery.
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Once rebooted check that the /system/wp_mod_test.txt file you just created has stuck through reboot.
MiniBlu
MiniBlu said:
This is a kernel module that disables write protection on the system partition while running the stock kernel.
This module was written by @far2 for the htc one M8 and Desire 816 its source code can be found on his git here: https://github.com/flar2/wp_mod
So credit goes to him.
I have just checked to see if it would be compatible and compiled it against A3UL 1.31.401.3 kernel source. It has been tested to load and work fine with all but the latest at&t kernel (as I don't have a copy of the latest at&t kernel to test it with but I think it should work for it as well).
This is for stock kernels only and is of no use if you are running JMZ kernel. It will allow you to keep your stock kernel (for better compatibility across regional rom versions) but same as JMZ kernel it allows you to modify the system partition and install mods and fixes that will stick through a reboot without having to do them through recovery.
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Once rebooted check that the /system/wp_mod_test.txt file you just created has stuck through reboot.
MiniBlu
Click to expand...
Click to collapse
Just to be clear...this is not a kernel but a mod for the kernel? And it has not been tested with the latest rom--1.53.502.11? Thats what I'm currently running. Thanks
KLit75 said:
Just to be clear...this is not a kernel but a mod for the kernel? And it has not been tested with the latest rom--1.53.502.11? Thats what I'm currently running. Thanks
Click to expand...
Click to collapse
Thats right. This zip just adds a loadable kernel module(wp_mod.ko) to /system/lib/modules and a script(install-recovery-2.sh) to /system/etc. Once its installed the supersu script will run the script which loads the module during boot. As there has been no major kernel version jump it should work fine with your at&t kernel but I have been unable to test it. If you could test it that would be great. If it doesn't work for you it can be easily removed by just deleteing those 2 files it creates from recovery(or I can post a zip to remove it)
MiniBlu
MiniBlu said:
Thats right. This zip just adds a loadable kernel module(wp_mod.ko) to /system/lib/modules and a script(install-recovery-2.sh) to /system/etc. Once its installed the supersu script will run the script which loads the module during boot. As there has been no major kernel version jump it should work fine with your at&t kernel but I have been unable to test it. If you could test it that would be great. If it doesn't work for you it can be easily removed by just deleteing those 2 files it creates from recovery(or I can post a zip to remove it)
MiniBlu
Click to expand...
Click to collapse
I will but been waiting for a chance to flash the slimrom. Cant believe its been 11 months ive owned this and both your kernel mod and slimrom post on the same day! But most likely ill have a better chance of using yours as a daily driver. Ill probably post results in a few days. Thats usually enough time to give you an accurate bug report.
Btw--if i test slimrom 1st, should i do a full wipe, restore backup then flash kernelmod in one shot?
Still waiting on a response to my gapps question in the other thread...i haven't flashed it yet. Want an opinion on which gapps to use. Theres no link posted and its not mentioned in install instructions.
Thanks, I've had jmz kernel but had a backup of stock kernel and went back to stock because jmz doesn't support exFAT SD cards , I tested it everything is working, FYI European carrier.
Ok so no obvious fix on the headphone issue with slimrom so I'm ready to test this. I just have a few questions
1. Can I just flash it with my stock backup I made earlier today (factory reset, flash rom, flash wp_mod, reboot system)? This backup already has supersu installed, busybox, etc.)
2. I had already made some modifications flashed through recovery and also altered wifi tethering which you helped me with. Do you foresee any problems having it already setup like this or should I just start from scratch?
I guess thats it for now. Actually just asking because you made it a point to flash su even though I'd imagine most people who are here are already running a rooted stock version. Thanks again!
KLit75 said:
Ok so no obvious fix on the headphone issue with slimrom so I'm ready to test this. I just have a few questions
1. Can I just flash it with my stock backup I made earlier today (factory reset, flash rom, flash wp_mod, reboot system)? This backup already has supersu installed, busybox, etc.)
No. That should be fine.
2. I had already made some modifications flashed through recovery and also altered wifi tethering which you helped me with. Do you foresee any problems having it already setup like this or should I just start from scratch?
No. It will have no affect on things that are already installed.
I guess thats it for now. Actually just asking because you made it a point to flash su even though I'd imagine most people who are here are already running a rooted stock version. Thanks again!
Click to expand...
Click to collapse
As long as you have a fairly recently updated supersu install it should be fine. If it's not working for you then just flash the latest supersu and and check again.
MiniBlu
Flashed it just now with my backup and everything went fine. Itll take a few days to find bugs (if any). This is really cool. Thanks!
*****Update****Nice job. Its running as good as ever with no obvious flaws. I did have one random reboot but ive been messing with quite a few xposed mods. Overall, its been excellent for nearly 48 hours. Thanks again.
@MiniBlu has anyone tested your kernel mod with the new slimrom?
KLit75 said:
@MiniBlu has anyone tested your kernel mod with the new slimrom?
Click to expand...
Click to collapse
I don't know. Not that I've heard of anyway. I've been meaning to have a look at it myself but haven't had time yet. From some of what I've read I think changes to the system drive are already sticking on slimrom so I think it might be runing a kernel based on JMZ kernel. I also haven't seen any link to there slimrom device tree or kernel source which hopefully we can find as could really help to finish of the CM builds I've been struggling with.
MiniBlu
I can confirm now slimrom is able to write to system.
Mod edit: Thread closed on owner's request.
exNoShadez-EAS Kernel
Hey Pixel XL forum. I'm a Pixel/Sailfish owner, who also enjoys hacking on kernel code. I recently released a Kernel in the Google Pixel forum => but we are all using the same kernel, sooo.... I thought after pushing my second stable release, that I should probably post on the XL forum too.
My kernel is a bit different than most kernels available, you will quickly notice. Lots of interesting features and some unique ones too.
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard (VPN) kernel module support
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on not supporting TWRP below => 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/MarlinStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/marlin/twrp-3.2.2-0-marlin.img
WARNING: This shouldn't need to be said, but we did have someone on the Pixel forum who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as oppsed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation.
Therefore; I do NOT support installing TWRP....
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
spr33 said:
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
Click to expand...
Click to collapse
No. like I said. I don't/won't support installing twrp. it would require reverting a bunch of patches/ work that I've already put in... and also not using linaro GCC 7.2.1 compiler, either...
the time invested would be a complete waste for me and I would have maintain another separate branch. test another build, etc, etc'... i'm not doing it. my current goal is to reduce my branches into one single branch/build;. ... which will end up hopefully being binder_rt... not create more.
feature wise, pretty much a 'best of' what any other custom kernel offers for Marlin, all of the hardening stuff (I think I'm the only Marlin kernel on XDA with that), etc... afaict, I'm the only one rolling in EASv1.4, cpu-boost, dynamic stune boost; all of which I've ported myself... some of the audio driver stuff I personally ported (more coming) and binder_rt is my baby; I ported aosp binder and researched / Inplemented all of the changes to Binder...
in my yet-to-be-released binder builds I also have backported a large chunk of the linux locking, workqueues and scheduling code and some other bits from newer mainline linux kernels (which allow me to pull in some new features and use them).
so I'd rather work on this kind of stuff, over caring about twrp, doubling my workload to support running synthetic benchmarks between gcc's -Os vs. -O2 optimization levels...
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
housepabldroid said:
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
Click to expand...
Click to collapse
haha. pixel community isn't too bad. there's just not a lot of custom oreo ROMs.... myself, I wouldn't want to run any of those custom roms anyway. they usually are built without odexing or proper signiture key signing = less secure and way less optimized... Stock ROM is great, just needs root and a few apps to modify / customize it a bit.
for me, the kernel has always been the issue. lol... therefore, roll my own. lol....
ya, for sure give it a try... I honestly would say binder_rt is the best build... the 'stable build' is a bit of a misnomer - all of the builds are stable, just the binder ones are running more experimental code... binder_rt blows the socks off any other Marlin kernel for certain kinds of workloads... I'm aiming fir it to become my default build...
Donric13 said:
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
Click to expand...
Click to collapse
yup. I have to wait until kernel sources are released. you got it!. but when they are / 8.1 is released; I will be upgrading to 8.1, so no worries - there will be an 8.1 version...
I've heard heard that battery life is pretty good on 8.1, there's a thread in the pixel forum about it... but by what they were saying, it didn't seem that much better than what I see from my kernel.....
I'm more interested to see what performance improvements are in 8.1 kernel sources... I've found stock kernel to be a bit crappy for some stuff...
well, if at some point you are bored and want to test my kernel on 8.1, go for it. ya never know: maybe it will work. the reason I say that?
IIRC - it was tested with my old kernel / sources build... could've been a bug, not present in the new one.... or something else. IdK.. being as I'm on 8.0 I can't even look into why that might be or have been...
just make sure if u do ever try it, keep the stock boot.IMG for 8.1 around, in case it doesn't work..... and report back, if it does work. lol
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
JS.zip said:
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
Click to expand...
Click to collapse
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
nine7nine said:
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
Click to expand...
Click to collapse
Thanks that's what I thought. The bad boy "Binder RT" lol
JS.zip said:
Thanks that's what I thought. The bad boy "Binder RT" lol
Click to expand...
Click to collapse
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
nine7nine said:
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
Click to expand...
Click to collapse
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
AlkaliV2 said:
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
Click to expand...
Click to collapse
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a download/link to me, so I can add it in. thx
nine7nine said:
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a downlink to me, so I can add it in. thx
Click to expand...
Click to collapse
No problem, I download every Marlin release so I'll just update my AFH folder to include the monthly kernel release and users can download it from there. You can either link to my folder or download from it to add to your repository; either one is fine with me Thanks, and I do appreciate what you're doing but I have a 'verify first' stance since these devices are a big part of people's lives. I'm going to give your kernel a spin now, I appreciate you getting back to me so quickly. If only AFH was this fast, I just spent 25 minutes trying to get it to create an empty folder...
Link to Marlin Stock Images: https://www.androidfilehost.com/?w=files&flid=231142
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
AlkaliV2 said:
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
Click to expand...
Click to collapse
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
nine7nine said:
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
Click to expand...
Click to collapse
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
AlkaliV2 said:
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
Click to expand...
Click to collapse
Yup. TWRP can't be installed along side. Running it from RAM has to be used. ie: I don't support TWRP installations. lol
Flashing the factory boot.img DOES get rid of TWRP for good ~ you just have to make sure to use the TWRP fastboot boot.img for flashing my kernel after (since fastboot/twrp doesn't install to the boot partition)...
I've added a link to the OP to Marlin's twrp fastboot boot.img....
I also updated all of the download links and double-checked to make sure that all of the Marlin zips are packed properly with AnyKernel2 + relabelling every file on my github (by re-packing all of them all... This is mostly just paranoia on my part - but now that I'm supporting 2 devices, best to make sure that nothing gets tangled together.)
@everyone
just a few notes, since you guys are just getting exposure to my kernel, the way I do things; in regards to development, etc.
-> I post test builds (this usually happens when I make big changes.). reports are helpful on these builds.
-> Development happens fast; *I routinely add new features, bug fixes, etc and i'm almost always ahead on LTS updates over the Stock kernel.
examples;
=> lts -3.18.83 build available on the day of release
=> my Binder_rt branch is currently 140+ commits (code changes) ahead of the the other branches.
(changes since in the current downloads/releases)
=> There are a number of bug fixes, a few added features (mostly in-kernel stuff), some optimizations *and* there are massive upgrades to parts of the kernel's subsystems. (100+ commits are related to that)...
(changes since the current downloads/releases)
NOTE: The binder Branch (non-rt) will see the majority of the above changes code, but the Stable branch will only see a subset of these commits + bug fixes.
I probably won't roll out a test build for Binder_rt builds, until I've had the newest code running for a couple of days.... At that point, once things have proven to be stable good ~ i'll roll out a test build for anyone who wants to help out and dogfood test builds....
Then, I will push back changes back into the Binder builds, Stable, etc... I usually try and line up actual releases to LTS and/or => more importantly monthly android security / firmware updates....
**So the gist is; there will be frequent updates. Update as you see fit - anyone who wants to help out - run test builds and report back issues.
So pending a detail or two, I likely will be phasing out my other builds in favor of the Binder_rt build.
- I've had quite a lot of feedback via the Pixel forum, PMs and email (and a couple of friends using it too).
- The Binder_rt build seems to be very stable for everyone.... not too mention just all around better.
- there seem to be no drawbacks and quite a few benefits to that build over the others.
The one thing I'm waiting on is; I've joined the Android Kernel Developers Google Group and am currently waiting to see if I can't get some help with porting a missing Kernel function into Marlin's sources ~ this particular kernel function is what's stopping me from having Binder be sync'd with the AOSP binder implementation.... I'm hoping to resolve this sooner than later, at which point I will be able to merge in those commits (and test them).
In the meantime I'm working on a few backports to the audio driver and a few other bits (taken from Wahoo/Pixel 2 kernel sources). I've also pulled in a few fixes to binder from Wahoo, as well....
So I might post a test build for Binder_rt tomorrow - as it's accumulated a number of changes, bug fixes, etc.... I'm not sure If I will have any resolution to the missing kernel function - but that doesn't affect pushing a test build....