About SoilWork
SoilWork is a mod created by @RogerF81, originally for the HTC 10, which features a Snapdragon 820. I've ported this mod to work with both OnePlus 3 and 3T devices. While the mod keeps the same name, the scripts used have been modified to best adapt to our devices! All the tweaks used in these scripts are made to work on any android and kernel version. If you are using an HMP kernel or an EAS one, there is no problem, as SoilWork will do the job of identifying your kernel and applying the tweaks accordingly.
Check out RogerF81's original thread here.
How to install/use this mod
If you use any of the Magisk modules provided in the download section, you just need to flash it in TWRP or in Magisk Manager and reboot. All the setting will be applied 30s after boot, to prevent any possible interference. Boosters Disabler is the only one which will run 45s after boot to prevent interference with the other profiles. (They can be installed alongside!)
If you want to use the .sh file provided in the download section, you can simply run it in a terminal emulator with these three simple lines:
Code:
su
cd /path/to/file.sh
sh *name of file*.sh
If you use the terminal method, rename the script, as parentheses aren't recognized from the terminal, use backslashes or the tab button combination (Vol+ and T) to complete the name of the script, which will also correct the name before you make it run. This is an error which won't be needed in the next update as the scripts will have a different name. Guess what? Fixed it.
Alternatively, use any other app which can run the script as root. At every reboot, however, the tweaked tunables will reset to the default values. The scripts already have a sleep time of 30 seconds (45 for Boosters Disabler), so it's not needed to add one. If you, by any means, remove it, please add from the app's settings a delay of at least 30 seconds in order for everything to work as it should.
If you're using a script manager app, as EXKM, please note that these apps seem to have problems in reading large files. Even if the file size has been reduced from the previous release, these apps may have these problems anyway. If that's the case, copy and paste the script to a new file created within the app.
Note: The script will not print anything on the console (it'll print grep checks) or output any file (as the previous versions) this is because all the scripts have been checked and are known to run without problems. If you still want to check if the script runs correctly, check the output from the app you are using to run the script (Magisk users run the script as stated above), since the console will output error messages (if any)
Note for Magisk users: The latest module is compatible with Magisk v15.0. Older versions are not supported anymore and are most likely to be moved to a folder tagged "OLD" in my AFH's Magisk folder.
Known bugs
Some Oreo ROMs seem to not react well under the battery profile (Cardinal Xtended seems to be excluded from this issue)
Available profiles (more to come)
Battery: Enhanches battery life without ruining user experience. It ruins your experience anyway? Try Battery LightWeight!
Battery LW: Also known as Battery LightWeight, this profile is the same as the Battery one, but has less impact than its predecessor.
Balanced: Gives a balanced experience between performance and battery.
Boosters Disabler: Disables any kind of CPU boosters in your kernel (Vox Populi, Input Boost, CPU Boost).
Downloads
MEGA | GDrive
AFH Main Directory
├ Magisk 13.x directory
└ Magisk 14.0 directory
Since AFH doesn't support the sh file extension, the scripts will only be available with GDrive or MEGA.
I'll use AFH as a repository - check it out if you want an older zip. If you search for an older script, just download any of the magisk zip and extract the script under /common/service.sh and you'll get the script.
Changelog
Battery profile
HTML:
v2.0
-Cleaned and fastened the script
-Added smartmax governor as a suggestion of a good tester
Battery LW profile
HTML:
v2.0
-Initial release
-Not bad for a version jump, uh?
Balanced profile
HTML:
v2.0
-Same as battery for this version
Boosters Disabler add-on
HTML:
v2.0
-The only change is the version number. Maybe.
Old changelogs
Battery profile
HTML:
v1.4
- Tweaked some EAS values
- Deadline over noop if maple is not present
v1.4.1 (will still show as 1.4)
- Fixed an error in the code
v1.3:
- Fixed flash problem via TWRP
- Fixed version
- Implemented more tweaks for EAS kernels (HMP too, but little was done)
v1.2:
- Optimised integration with blu_spark kernel
- Squashed some bugs
v1.1:
- Fixed tweaks which caused the device to stutter
- Optimised some tweaks to make the profile even more battery friendly
v1.0:
- Initial release (unavailable)
Balanced profile
HTML:
v1.4
- Tweaked some EAS values - more battery, same performance
- Fixed a GPU code-related problem
v1.3:
- Fixed flash problem via TWRP
- Fixed version
- Implemented more tweaks for EAS kernels (HMP too, but little was done)
v1.2:
- Optimised integration with blu_spark kernel
- Squashed some bugs
v1.1:
- Fixed an error in the code which made GPU values to not apply on OP3
- Optimised some tweaks to make the profile more balanced
v1.0
- Initial release (unavailable)
Boosters Disabler
HTML:
v1.0:
- Initial release
Credits
@RogerF81 for the original script and idea
@joshuous and @RenderBroken for their help with kernel related questions
@boyd95 and @ZeroKool76 for trying the script out before the release
@soniCron @Alcolawl @Freak07 @Asiier
@Mostafa Wael @patalao @Senthil360 @TotallyAnxious @Eliminater74
@ZeroInfinity @Kyuubi10 @ivicask @DeeZZ_NuuZZ
ROMs which include SoilWork (or any of it)
ZeNiTy [EAS] since 30.09.17 build - Thanks to @ZeNiXxX and @SKULSHADY for the inclusion and for their awesome work! Check out the full post here.
Version info
Version: 2.0
Status: stable
Date of creation: 20/09/2017
Date of last update: 29/12/2017
Note for the developers of custom ROMs: Yes, you can use my script in your ROM, but give credits and PM me so I can add your ROM in this OP.
Are you wondering which profile to use? Seek answers no more, here's a detailed (?) insight of them!
Battery: This profile is excellent if you're using Nougat. No one is experiencing lags on Nougat because of this profile, and if anyone is, the wrong kernel is being used (check at the end of the post). The tweaks in this profile tweak almost everything regarding your CPU's governor. Another module (the one below) has been made for you if you don't like this approach (but don't expect the same results). On Oreo, there seems to be a problem, for now, as many kernels doesn't seem to tolerate the tweaks it does. On some ROMs there are no problems, in some there are. Try it yourself and let me know how it goes. If you are experiencing lag on Oreo, please try the module which is described below before posting known issues.
Battery LW: This profile, which full name is "Battery LightWeight" has seen light because the impact on Oreo and some kernels seemed too much. This won't tweak the same amount of things as the one described before, and seems to run better than the Battery profile on Oreo. As for Nougat, consider using this module if you're experiencing lags. This module is also for everyone which runs a kernel with enhanced battery features (see the end of the post). Even if it has been tested on a couple of them, please do note that it's not easy to cover them all. If you're experiencing problems, revert to stock settings.
Balanced: This profile is for everyone who wants some battery tweaks but doesn't want to slow down the phone by any means. On Oreo it doesn't seem to have any problems like the Battery profile has, but it's still a beta on Oreo. On Nougat, it runs smoothly. Use this profile if you want a balanced experience between performance and battery saving options.
Boosters Disabler: This profile is for who wants even more battery. Do you feel like CPU boosters aren't needed in your setup? Use this profile.
Anyway, what's this issue with Oreo ROMs / Battery enhanced Kernels?
Oreo ROMs, being still worked on, change rapidly how they function. This means that some script parts may adapt, may not. Particularly, it has been reported that NitrogenOS may have some problems when the script is used and may not be compatible for the time being. Do note that when all ROMs settle to a stable version, the tweaks will be rewritten and adapted.
Battery enhanced kernels are already optimized by the developers to have the best battery life. Adding custom scripts may ruin your experience.
FAQs
Q: Does this script support the ROM/kernel I'm currently using?
A: Yes. The script supports any kernel, even the one provided with your ROM. This being said, I won't help people using heavily modified kernels, such as Franco kernel or BoefflaKernel. As they state in their threads, modding those kernels with 3rd party app is discouraged. The scripts will work with your kernel anyway, but I can't help anyone facing issue with the mods since it's an incompatibility I can't change.
Q: Apart from flashing the module or using the script, do I need something else to make it work?
A: No, you don't need anything else to make this mod work! Just flash the module or run the script from terminal or other sources. You can, however, use KA, EXKM or open the "soilwork_op3.txt" file on your sdcard root to see if the settings got applied correctly.
Q: This script has overridden my settings! How can I make it not do that?
A: If you think this is an error, please report it to me, so I can change the script. However, if these settings are your personal settings, change them with any kernel manager and set them to apply at boot, setting the delay of the settings higher than 30 seconds (a value equal or higher than 40 seconds is reccomended).
Q: Can you add these settings to the *name of profile* profile?
A: Sure! Make your suggestions in this thread, and if after some testing they prove to be effective, I'll add them in the script. Please test them yourself before posting them.
Q: How can I uninstall the mods I'm currently using?
A: You can uninstall the mods with Magisk Manager if you are using the Magisk module. If you modified system files to make the script run at boot, simply delete the lines you've added. If you are using a third party app... You should know how. Whatever method you use, reboot your phone to see the effects.
Q: My phone's battery stats are the same! What went wrong?
A: If you're using Oreo, that's widely possible. Even if some people got great battery stats on Oreo, Oreo is still being worked on, so don't expect astronomic results. (Plus, these screenshots are also old. If you guy posted some more... )
Q: Can these tweaks make my phone waterproof, make it explode or fix VoLTE?
A: No.
More coming soon... If something is unclear, let me know
Screenshots
Check the attached thumbnails! This section is still a work in progress. Post your best sot and battery stats and they'll be posted here!
Note: If in a screenshot is tagged with the letter "A" the next one tagged with "B" is another screenshot with more detailed battery use.
Screenshots are from: @boyd95 and @Nagi2195. Thank you for the precious help!
I will try it out and tell about the battery life in few days
Can i get the video tutorial on this! Magisk is not available for android 8 so only su i have... How to install?
Gauravlonkar said:
Can i get the video tutorial on this! Magisk is not available for android 8 so only su i have... How to install?
Click to expand...
Click to collapse
Download the .sh file of your preference from the links in the download section, then install a terminal emulator and follow the guide in the op. Alternatively, to have it apply at every reboot, use any app that can run the script at boot, like EXKM, Boot Manager or apps like these ones. You can also append the scripts to your init.d. Check xda for tutorials on this one.
Nice to see your work finally released! Very good work
Great job
VoxPopuli is only for EAS kernels and roms that has it, right?
Can u provide uninstall as sometimes needed for changing profiles.
theduke7 said:
VoxPopuli is only for EAS kernels and roms that has it, right?
Click to expand...
Click to collapse
Yes, you are right
abhi0502 said:
Can u provide uninstall as sometimes needed for changing profiles.
Click to expand...
Click to collapse
You mean an uninstaller for the magisk modules? I could, but it's already a function of Magisk Manager. Go to Magisk Manager>Modules and click the rubbish bin icon to remove it. Since to install another one you have to reboot, simply install it via Magisk Manager, remove the old one and reboot. The new module will be functional at reboot and the old one will be removed. To erase the custom settings, just remove the modules you've applied and they will reset to the default ones -- the ones which came with your ROM.
i added the balanced one to Magisk on Flash kernel using Blu_Active governor and fastlane active on big cluster... so far so good, will report back after the end of this battery cycle.
This mod will work on op5?
is VoxPopuli BFP works with RenderKernel EAS?
morfances said:
This mod will work on op5?
Click to expand...
Click to collapse
Probably not, because op5's paths might differ from the ones op3/t has. You can try, but I can't guarantee that it will work
cet90 said:
is VoxPopuli BFP works with RenderKernel EAS?
Click to expand...
Click to collapse
Yes, it should work. To be sure check if Vox Populi is included in the Kernel, but if you are using a recent version of the kernel, you won't have problems
cet90 said:
is VoxPopuli BFP works with RenderKernel EAS?
Click to expand...
Click to collapse
it should work on RenderZenith (it's essentially the same but with vox), also both projects are now merged i think, both devs will produce 1 kernel from now on
morfances said:
This mod will work on op5?
Click to expand...
Click to collapse
This is written for sd820 and 821, with specifically the 3 and 3t in mind. Since the op5 has sd835 I don't think that will work well.
theduke7 said:
it should work on RenderZenith (it's essentially the same but with vox), also both projects are now merged i think, both devs will produce 1 kernel from now on
Click to expand...
Click to collapse
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
cet90 said:
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
Click to expand...
Click to collapse
Same story, tried battery and balanced versions.
cet90 said:
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
Click to expand...
Click to collapse
yes i noticed the same on an HMP kernel as well with balanced profile.
it does improve battery though, specially when the screen is of , it's almost 0.5% an hour which means last night i lost 4% only while i was asleep (very good) , i think it needs to be optimized for when the screen is on to have less lag (it's more of a stutter)
Related
We have moved support away from this thread and into the main thread at Android General. The info in the second post is accurate as of 12/3/12.
Development on the Auto-Patcher continues, I have just stopped adding Nexus 7 specific features as this device's users didn't express any interest.
If I could close the thread, I would. But if something tickles your fancy, come see us at the above link.
The Auto-Patcher 2.4.7 (Bismuth)
by pastime1971 and mateorod.Trouble with Android 4.2? See here.
Current version and changes: Auto-Patcher 2.4.7 is out
Improvements include:
Pdroid for CM7, after a long battle, should finally be working
Internal script improvements.
Pdroid and Pdroid2.0 are incompatible and cannot be applied to the same rom!. If you are switching from one Pdroid to another, go to data/system and delete everything with privacy in the name.
The Auto-Patcher
The Auto-Patcher is a smali patching utilty that can be used to port mods, framework changes, themes and more across ROMs and devices by patching files and outputting a flashable zip.
We hope that this tool can help developers get their work to a wider audience and help users easily try programs that may call for skills or time they don't have. In one command, you can have all the power and utility of the mods/programs listed below, with no specialized knowledge.
Supports
ClockworkMod and Aroma installers
Cyanogen [CM7, CM9, CM10] (cm)
AOKP (aokp)
AOSP (aosp)
ParanoidAndroid (pa)
Evervolv (aosp)
...and many others.
We do not support system.img, Odexed roms or Sense, TouchWiz or other OEM-skinned AOSP at this time.
If you have a build environment and build for TW or Sense, consider joining the team. Additionally, Quarx's CyanogenMod roms are not currently supported. A maintainer would be welcomed for that as well.
Supported PlatformsThe Auto-Patcher runs on Linux and MacOSX terminals. Project contributors kobik77 and wbedard have helped us add Windows support as well.
Kobik77 has developed a stand-alone GUI for Windows called ApG. The most current version of ApG can be downloaded here. Note: ApG has some trouble with some virus software. It has no elevated permissions and is demonstrably safe. Here are some anti-virus tips from long-time user Grayfoxmg1
The Available Mods
Unless there are hardcoded reasons they conflict, all of the mods below can be combined, so you could get all of the programs and tweaks in one shot. If you use other premade patches or zips, you would have to choose between them.
The Auto-Patcher is the only non-destructive way to get these enhancements, short of building your own ROM and/or applying your own changes to the code.
The name is paranthesis is the MODS for use on the command-line. See usage below if that confuses you. It isn't hard, really.
PDroid (pdroid):
The one where we make our bones, PDroid is an advanced privacy app, one that allows you to deny system and user apps permissions they usually need to function. PDroid changes the information passed by permission requests instead of denying it like other apps. That means no FC's or misbehaving apps. PDroid allows you to set custom phone numbers or IMEIs as well. PDroid is only officially supported through GB. The Auto-Patcher makes it an option for ICS and Jellybean ROMs as well.
PDroid is available in the Google Play Store, although you may have trouble installing it from there. It is available from its release thread by svyat, PDroid's sole developer. Discussion about PDroid efficacy and operation for ICS/JB is usually best at pastime1971's port/build patch thread.
PDroid 2.0 (pd2.0): NEW!
CollegeDev's update of the core PDroid app and framework. There is a separate app you will need as well. You can get the app and read about PDroid2.0 and get the .apk here. This mod is only for Android 4.1.2+
V6 Supercharger (v6supercharger):
Most likely needs no introduction to any regular XDA member. The Auto-Patcher will edit your services.jar for you. Our patches contain zeppelinrox's most recent edits. You will still need the script, which you can get at his OP. Only for Android 4.0.0+!
Insecure Boot.img (insecure):
This should work for just about every ROM, giving you true root shell access, enabling adb push of system files and adb remount commands. It can truly save your bacon if you are the type to play with system files and flashing. Some ROMs come with this feature already, so if this patch fails, it just means you already have one.
Secure boot.img (secure):
The opposite of the above. There are advantages to both, and what you want depends on what you do. I haven't seen any other way to secure a boot.img, with so many roms now having insecure by default.
Swap internal and external storage (external_internal):NEW!
This swaps your app storage from an sdcard to internal storage. This allows you to use all apps, even w/o an sdcard!
TabletUI (tabletUI):
Based on findings by barmullio, this allows users of the "Phablets" UI to switch from the stock phone or phablet layout to Tablet user interface. I personally like the tab interface because it allows me more regular access to the status bar. Lockscreen rotation has been enabled as well. Confirmed working on all devices!.
NEW
Mods for Wifi-only Tablets.
3G Dongle (3gdongle):
This allows users of Wifi tabs to use their 3G dongles on their tablets, allowing them to have data on the go. This is a pretty involved mod, and the development is still on-going. We would like to stress that you read up at developer trevd's thread for best practices and troubleshooting. A growing list of confirmed supported dongles can be found there as well.
Google Voice (voice):
As popularized by bongostl, this allows users to use Google Voice to make outgoing calls. It changes your framework-res to recognize that the tablet is voice capable. This allows you to recieve calls as well and has other call quality advantages over things like GrooveIP.
OTG support- Coming SOON.
Usage
Designed to run on Linux, OSX and Windows (using Cygwin)
The Auto-Patcher has become completely open-source, and no one has gotten more out of that than our Windows users. kobik77 and wbedard have come aboard and brought Windows support to our formerly *nix-only utility.
Kobik has also crafted the first Auto-Patcher GUI! Here is his post with download link and features description (including auto-update from Github!)
Requirements for execution: Java (JDK), cpio, patch
Help
For usage and patch availability, place a rom.zip into this directory and try
Code:
$./auto_patcher <ROMNAME>.zip -h
This will check our various dependancies and provide some useful information. It is not the prettiest thing in the world yet, we're working on it...
To patch a ROM
Code:
./auto_patcher <[FONT="Courier New"]ROMNAME[/FONT]>.zip <[FONT="Courier New"]MODS[/FONT]>
example:
Code:
./auto_patcher cm10-encore-fat-tire.zip pdroid,tabletUI
You can have any number of mods applied at the same time, just separate them with a comma and NO SPACES!
The only thing you may need will be a romtype. The patcher will detect and display the ROMTYPE it thinks you have. If the patches fail, just append your ROMTYPE to the end of the command. The only available ROM types are:
pa
cm
aosp
aokp
Don't worry if your rom doesn't have a type; most roms in XDA are derivatives of one of the above, and tell you which one in their release threads.
Code:
./auto_patcher pa-2.23-mateorod.zip pdroid pa
98% of the time, that is all you need to know!
If you would like to see some of our more advanced usage, please see the third post.
Debugging
There is never any need for any wiping or restoring of a backup! If you encounter any problems, simply reflash the generated restore.zip or your ROM over the install, preserving all data and settings!
In the Auto-Patcher directory you will see a logfile that is generated with each run of the program. Please attach the entire logfile in order to get the best support we can offer.
Current and past versions available at our download page on techerrata
Download
You can also clone from our github. See the README because there is actualy a lot extra there.
Contributors
pastime1971
mateorod
kobik77 (ApG developer/cygwin maintainer)
wbedard (cygwin/AOSP pd2.0 maintainer)
Maintainers
FFU5y (Maintains pd2.0 AOKP)
KickNGuitar (OSX testing)
poncik (Evervolv maintainer)
Thanks
eyeballer and kevank with Team Win for web hosting
Svyat
CollegeDev
tonyp
krylon360
inportb
chainfire (for faapt)
zeppelinrox
trevd
rathian, and TheMatrix2000 (for OSX testing)
romracer and greenblue for 4.1.2 fixes
ninno_mx
The Auto-Patcher is a fully open-source utility, and we welcome new contributors.
If you are a developer, themer or script writer who has code-level edits you walk your users through, let us know and we can get together and create a package for you. A message to developers is here, which also touches on our donation policy.
changelog
12.05.00. (v0.1)
# ...........
# 2012.05.12. (v0.2) allows user to specify a different version of patches
# 2012.05.13. (v0.3.0) force "patch -N", remove temp upon failure, generate log output
# 2012.05.13. (v0.3.1) revised the generation of updater-script (SGS2)
# 2012.05.15. added AOSP patches
# 2012.05.15. added crespo-aosp patches, added device-specific patching if patch exists
# 2012.05.15. remove restore.zip upon failure
# 2012.05.15. (v0.4.1) added CM7 (GB) patches
# 2012.05.18. (v0.4.2) added checking for tool commands
# 2012.05.21. (v0.4.3) apply device-specific patche only when it is specified
# 2012.05.26. added task title to log
# 2012.05.31. (v0.4.4) CM9 patches updated, crespo-aosp added
# 2012.06.04. (v0.4.5) added checking tools and rom, added aroma installer support, add patch outputs reroute
# 2012.06.15. CM9 patches updated
# 2012.06.16. (v0.4.6) AOKP patches updated, patch versions restructured
# 2012.06.17. (v0.5.0) patcher script reorganized, removed build.prop
# 2012.06.17. (v0.6.0) auto patcher script for pdroid and v6 patches
# 2012.06.19. (v0.6.1) add patches for CM7.2 Final
# 2012.06.20. (v0.6.2) updated CM 7.2 patches
# 2012.06.23. (v0.6.3) fix symlinks
# 2012.06.26. (v0.6.4) add CM7 nightly patches (0618 or latest). Removed faulty 7.2 patches (0619)
# 2012.06.27. (v0.6.5) added new CM9 patches (20120626)
# 2012.06.27. (v0.6.6) added CM7 nightly patches (20120625) (finally!)
# 2012.07.02. (v0.7.0) Redid AOSP/AOKP; add Windows support (using Cygwin). Thanks kobik77!
# 2012.07.06. (v0.7.1) updated CM9 patches (20120706)
# 2012.07.08. (v0.7.2) updated AOKP (20120707) and CM9 (20120708) pdroid patches
# 2012.07.11. (v1.0.0) reworked script works on Linux, Mac OSX, and Windows (on Cygwin);
# " " added new ICS/JellyBean support for the new V6-Supercharger
# 2012.07.18. (v1.0.1) updated pdroid patches for CM7/CM9 (20120718)
# 2012.08.06 (v1.5.0) updated smali/baksmali binaries to 1.33
# 2012.08.06 Added Pdroid/V6supercharger support for CM10 Jellybean!
# 2012.08.06. (v1.6.0) added aokp-jb patches for pdroid/v6supercharger, script update
# 2012.08.17. (v1.9.5) Added support for pdroid_addon, by CollegeDev.
# Added insecure boot.img mod
# Added support for aosp-jb (This needs testing, and may not be a wide patch due to large variation between AOSP roms.)
# -Please report all experiences!
# Updated all v6supercharger patches w/new edits to ProcessList
# Major script overhaul in preparation for additional mods!
# 2012.08.20. (1.9.6) Conditional support for Official cm10 and aokp-jb builds
# 2012.08.23. (1.9.7) Final/confirmed pdroid support for Official CM10 and AOKP-JB
# 2012.09.04 (1.9.8) Bundled cygwin-compatible tools (original was corrupt).
# For Cygwin, replaced h2b function with simple bash math
# conversion (req'd for compat w/ Cygwin tools).
# 2012.08.26. (2.0.0) Added .apk patching
# Added 3G Dongle support for Nexus 7
# TabletUI support for Nexus 7 (maybe more)
# Google Voice support for Nexus 7
# mods are 3gdongle, tabletUI, voice, or Nexus7 (for all)
# Added provisional file copy menu to widen patching base
# 2012.09.11. (2.0.1) Cygwin support fixes
# 2012.09.11. (2.0.2) Bugfix for 3gdongle (all)
# 2012.09.16. (2.1.0) Significant restructuring of core operations; added edit text file
# Fix for "method-cap" errors in pdroid.
reserved
Nice to see you and pastimes and your work here as well - and I absolutely love the new Nexus 7 additions as i finally got mine as well
Btw: Are there any news on decompiling the jars and applying these fixes on an android device, without having to use the PC?
It's not important, I'm just interested.
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Cetin said:
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Click to expand...
Click to collapse
Well, that is interesting, actually. There are a bunch of ways that you could get the update.zip on your tablet, but there isn't support for custom kernels yet. You can patch any rom, but if the patch needs to change the boot.img, flashing a new kernel will remove that part of the patch.
I think I know a way to add it though. I will try to add custom kernel integration to the next update.
But you CAN get the 3gdongle working on your rom, just put it through the patcher and transfer it through adb or email or dropbox.
Code:
./auto_patcher paranoidandroid2.2.1.zip 3gdongle
replacing paranoidandroid2.2.1 with the actual name of the zip.
The stock kernel is pretty awesome, bttw. But I think I can add this to the autopatcher. It is needed anyway.
Edit: I must be really tired. You can do this. The kernels are distributed as boot.imgs. Just open up the kernel installer zip, take out the boot.img. Then replace the boot.img in whatever rom you are using.
Then run it through the Auto-Patcher, using any options you like.
You will ONLY need to replace the boot.img of your rom if you are applying the 3gdongle, insecure,secure, or pdroid-aosp-jb modtypes and would like to use a custom kernel that doesn't come bundled with your rom.
I will add some version of this to the autopatcher's next update though, so it is easy to do from the command-line/GUI.
Cetin said:
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Click to expand...
Click to collapse
If you need more info than that, you can ask and I will be more specific, I just reread your post and realized maybe I wasn't thorough enough...
Update Because this seemed so vital to the Nexus 7 community (because we have everyone and their mother with a custom kernel here...) I went and looked through the installers.
It looks most people: faux,_motley, clemsyn et.al. use the AnyKernel updater. Those updaters use some of the same binaries we do to preserve ramdisk edits. They don't want to overwrite mods of this sort any more than we want them to.
A couple devs, franco and some new one from today, Thoravuuk or somethin', just package a boot.img. In those cases you will need to place the custom boot.img (and title it boot.img) in the ROM you would like to patch with the Auto-Patcher.
In all cases, there is existing methods to preserve all support and features with nothing more than winzip or any other archive manager. Drag and drop.
So we will see how we end up handling this in the Auto-Patcher in the future. There are a bunch of methods to distributing kernels which make it tricky, but the more responsible Android devs already are prepared for the fact that you may have modified your ramdisk and want to keep it that way. Using Koush's AnyKernel is a great way to accomplish that.
For franco you will habe to briefly drag and drop for now.
tonyp said:
reserved
Click to expand...
Click to collapse
Just saw this part, tonyp. I hope this means you might have something planned for us...
Hey man, thanks for your big support!
I will try like you said.
As I understand correctly the boot.img keeps untouched by your patch. So I can patch my Rom flash the zip and use any custom kernel by flashing it with fastboot flash boot command?!
NEXUS 7
I tried patching but there´s is a problem:
How to choose the right file and which one is it?
Code:
### applying boot.img patch ###
... applying init.dongle.rc patch ...
... applying init.rc patch ...
The text leading up to this was:
--------------------------
|diff -Npru ramdisk/init.rc 3g-ramdisk/init.rc
|--- ramdisk/init.rc 2012-08-27 00:25:58.749201521 -0500
|+++ 3g-ramdisk/init.rc 2012-08-27 00:24:51.012865613 -0500
--------------------------
File to patch: 3g-ramdisk
3g-ramdisk: No such file or directory
Skip this patch? [y] n
File to patch: 3g-ramdisk/init.rc
3g-ramdisk/init.rc: No such file or directory
Skip this patch? [y] n
File to patch: init.dongle.rc
1 out of 1 hunk FAILED -- saving rejects to file init.dongle.rc.rej
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed patching init.rc
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cetin said:
I tried patching but there´s is a problem:
How to choose the right file and which one is it?
Click to expand...
Click to collapse
You're using a Mac correct? That is probably the least tested upon platform, although it should be fine. In your autopatcher folder, there is a logfile. Would you attach it please? I can know a bunch more with that file.
Thanks for reporting back.!
tonyp said:
Btw: Are there any news on decompiling the jars and applying these fixes on an android device, without having to use the PC?
It's not important, I'm just interested.
Click to expand...
Click to collapse
Oh yeah, once 2.0 gets stable (and I solve this new pdroid problem, that is soooo irritating. I predicted this was coming waay back in pastime's port thread, when we first ran into trouble with the build patches) that is the next thing I am going to work on.
I think pastime is going to lead the charge getting a linux GUI and I am going to work on getting the Android front-end. That is going to be wild, most people have just accepted it can't be done.
noob here! i just want to apply 3g dongle patch on my nexus 7 stock rom (rooted ofcourse) help please
thanks
rufh_s said:
noob here! i just want to apply 3g dongle patch on my nexus 7 stock rom (rooted ofcourse) help please
thanks
Click to expand...
Click to collapse
Well, we don;t support system.img modding here yet, mostly because it is so device specific. This tool works on all roms and devices, so adding something for each device would be a real pain. I am going to keep looking at perhaps adding the Nexus 7 system.img, though.
What you can do is look for a deodexed stock rom in the rom page. There are several available, I believe scrosler has one, and maybe a couple more. These are basically stock roms, but with deodexing and unpacking of the system.img already done.
The main advantage to using custom roms is their customizability, (if that is even a word...). All the other stuff is a result of that.
If you want the 3gdongle support, you will probably have to try one of the flashable stock roms.
Very useful mod. Thanks for bringing this here.
Quick question to clear up something:
The tablet mode or 3g dongle, can I just flash them through twrp and be done? Or does the untethered way need your manual method you described above for untethered installation?
I'm running stock rom with trinity kernel(anykernel i believe) BTW. I alternate between motleys and trinity. Sometimes Faux one also.
Edit: I see the above post basically answers my question. Won't work on stock rom. Needs a deodexed stock base rom. Will wait till you hopefully add img. Support. My nexus 7 runs great on stock rom with custom kernel. Waiting for custom roms to mature more before I go flashing.
mateorod said:
Well, we don;t support system.img modding here yet, mostly because it is so device specific. This tool works on all roms and devices, so adding something for each device would be a real pain. I am going to keep looking at perhaps adding the Nexus 7 system.img, though.
What you can do is look for a deodexed stock rom in the rom page. There are several available, I believe scrosler has one, and maybe a couple more. These are basically stock roms, but with deodexing and unpacking of the system.img already done.
The main advantage to using custom roms is their customizability, (if that is even a word...). All the other stuff is a result of that.
If you want the 3gdongle support, you will probably have to try one of the flashable stock roms.
Click to expand...
Click to collapse
Well I have downloaded the rom deodex by scrosler,but I am getting the error,have attached log cat.text
Thanks
rufh_s said:
Well I have downloaded the rom deodex by scrosler,but I am getting the error,have attached log cat.text
Thanks
Click to expand...
Click to collapse
I should make a note of this in the top post, the only way to combine the 3gdongle and the Voice hack is to substitute the list of all the mods separately with
Code:
Nexus7
The voice and 3gdongle have separate edits to the bools.xml that are right next to each other. So applying one makes it so the next patch cannot find its context.
I made the Nexus7 patches by hand, so you get all three mods that way. The good news is that going by your log, that's the only problem. So you are basically done!
Edit: And as for the above stock system.img issue, well I may try and add system.img support. But it is a huge pain in the butt, requiring all sorts of manufacturer-specific stuff. I also like stock, though, and alternate between that and straight CM10. But I deodexed the stock.img as well, strictly to make use of all of the cool development that goes down around here.
You can manually deodex, then redex and all that, but I didn't really see a performance drop personally. I am pretty sure all the kernels you listed use koush's anykernel method, which is compatible with the Auto-Patcher and its methods.
mateorod said:
I should make a note of this in the top post, the only way to combine the 3gdongle and the Voice hack is to substitute the list of all the mods separately with
Code:
Nexus7
The voice and 3gdongle have separate edits to the bools.xml that are right next to each other. So applying one makes it so the next patch cannot find its context.
I made the Nexus7 patches by hand, so you get all three mods that way. The good news is that going by your log, that's the only problem. So you are basically done!
Edit: And as for the above stock system.img issue, well I may try and add system.img support. But it is a huge pain in the butt, requiring all sorts of manufacturer-specific stuff. I also like stock, though, and alternate between that and straight CM10. But I deodexed the stock.img as well, strictly to make use of all of the cool development that goes down around here.
You can manually deodex, then redex and all that, but I didn't really see a performance drop personally. I am pretty sure all the kernels you listed use koush's anykernel method, which is compatible with the Auto-Patcher and its methods.
Click to expand...
Click to collapse
Alright I am off to sleep now... will just patch 3g dongles and see...
Well I got to know this is not just n7 specific in your earlier post itself
This is for all devices that's really great,also I just got my n7 so wanted to be stock as much I can,yep I also prefer it..
Let's see, I ll keep you posted
Thanks again for the great work, will also test it on my phone if it works (droid 3) it would give me lot choices to use my data plan
and yeah I also see otg coming soon,all the best for the concept its perfect for noobs like me
Sent from my Nexus 7 using xda app-developers app
apparantly patching only "3gdongles" patch didn't worked either attached log, may be i ll try this with some rom or try to find some other "stock" similar, can you suggest some?
thanks
rufh_s said:
apparantly patching only "3gdongles" patch didn't worked either attached log, may be i ll try this with some rom or try to find some other "stock" similar, can you suggest some?
thanks
Click to expand...
Click to collapse
Okay, this isn't the fault of your rom. Your log shows that it is failing rebuilding your ramdisk. A user reported a corrupted .exe binary, but when I tried to investigate further I haven't heard back.
But since everything else appears to be working for you that may indeed be the case. Give me a minute to look and then I will put out a hotfix.
This will only affect WIndows users who are patching 3gdongle, insecire/secure and aosp-pdroid. I happen to know for a fact that the program runs fine on Cygwin, so I will checkout some new binaries and you should be okay.
Update: We have fixed the final issues with Cygwin and those selct mods. Thanks for your report, 1000+ downloads of 2.0 in the 24 hours or so and you were the one that aimed me towards the fix.
Thanks! Should be up later tonight, after I put my son to bed.
Okay, update is ftp'ing its way up to techerrata as we speak. Maybe 20 mins or so.
I went and got my hands on a Cygwin terminal, and as far a I can tell, everything works as it should. We were having a hell of a time with the binaries, they just seemed to check out fine right up until we uploaded the package and then they crapped out on us.
But the new update has all working pieces. If you were using cygwin and had an issue, give it another shot. Writing a program to run on all three major platforms has been a major learning experience for me, let me tell you.
I am probably going to add the 720p video shooting next update, so if there is anything else you know and want, let me know. It doesn't have to be limited to this forum, there isn't much we can't tackle at this point.
Oh, and we strengthened the voice and 3gdongle patches, now you should be able to apply them both anyway you want, including the Nexus7 command.
** Note: This kernel is end-of-life and will no more be maintained. There will be no LineageOS 15.1 or newer kernel be available anymore **
Hi all,
some of you know me from the Samsung devices area, where I provide my kernels already for more than two years to Galaxy S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.).
Maybe you also know me from my OnePlus One kernels I added in winter last year to my portfolio.
Finally I got a Samsung Galaxy S5 afew weeks ago and decided to port my kernel also to this device. This is a sponsored device, so I want to say a big thank you to the people that made it possible, namely the ones in the German Smartphone Forum www.hubo.in !!!
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
For the Samsung Stock Boeffla-Kernel, please go HERE.
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official LineageOS/Cyanogenmod and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for CM14 kernels: CLICK HERE
Change log for CM13 kernels: CLICK HERE
Change log for CM12 kernels: CLICK HERE
Change log for CM11 kernels: CLICK HERE
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove (Note: not considered stable at the moment, you might face reboots!!!), intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, nightmare, lionheart, pegasusq
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Wake up gestures implemented (double-tap-to-wake, swipe to wake)
Boeffla-Sound engine (Headphones and speaker volume configurable)
Configurable vnswap
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency configurable, touch boost switch (all boosts removed by Lineage team in December 2016)
CPU Overclocking up to 2.84 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support
Show GPU frequency usage per frequency in Boeffla-Config
Color control to adjust RGB color space + inverted mode
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported (default is off)
Android logger (logcat) configurable
Kernel logger (dmesg) configurable
Charge rates for AC charger, USB and wireless charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Swap supported (but not recommended, use zRam instead)
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Insecure kernel (adb has root privileges)
Automatic EFS backup
Kernel survival mode by Boeffla-Config app to survive CM rom flashes
Full support for mpdecision for best compatibility and smoothness
(Important: use Boeffla-Config to configure min/max CPU frequencies + governors + schedulers only - or explicitely allow other apps/processes to overwrite this in Boeffla-Config settings, but expect weird side effects)
Integrated full busybox 1.23.1 (own compilation)
Auto-Root by kernel possible by request, not recommended for CM however (latest su included)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Google gcc 4.8 toolchain used for best stability
Always using latest Initramfs
Always based on latest Galaxy S5 sm-g900f kernel sources by CM
Kernel runs with SELinux enforcing by default, just as CM12 stock kernel for S5 - but can be configured to work in permissive mode in Boeffla-Config settings
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the Galaxy S5 kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are on Samsung Stock, CM12 or CM11 !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.1.72 or higher for the Galaxy S5 Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Yank555
* ktoonsez
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Entropy512
* Faux
* Ak
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
LineageOS 14.1
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm14.0/changelog.htm
CM13.0
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm13.0/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/galaxy-s5/general/unofficial-boeffla-kernel-profile-t3139530
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Hi all,
Great kernel
Works very fine
Check this out..
Thanxxxx to the Lord for the hard work in the last week's
Now i love my S5 G900F
[emoji7]
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Cannot comment for Temasek, as written.. it is for official CM12. And it is only tested by me with official CM12.
If it runs with Temasek - fine. If not, you need to search why it reboots for you. Then Temasek seems not 100% compatible.
Andi
Flashed fine on AICP.
Only heard good things about your kernel!
superleeds27 said:
Flashed fine on AICP.
Only heard good things about your kernel!
Click to expand...
Click to collapse
Thanks.
But also let's be realistic. It is version 1.0-beta1. So for sure some more way to go
Andi
@Lord Boeffla
Hi Andi, a big neverending thanks for providing us with an S5 (G900F/klte) kernel.
Coming from my i9300 which ran the whole time with your wellknown and imho best kernel for the i9300 I am familiar with your fine app and highly appreciate your new work for the S5.
And btw: Due to so far not working TRDS for LP/cm12 I still run kitkat for s5 (same with my i9300) using FusionRom which is mostly based on cm11.
Now with Boeffla-cm11 for G900F based on FusionRom 4.4.4 I feel happy again - fast-stable-easy to handle 1A+++
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
vulfgar said:
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
Click to expand...
Click to collapse
Fingers crossed it will stay like that
Andi
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Me too. If not I'll have to change rom.
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Just to be tested, my friend thanks for everything
Lord Boeffla said:
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
Click to expand...
Click to collapse
I was the user
You must delete in root/system/app/com.ktoonsez.KTmonitor.apk and com.ktoonsez.KTweaker.apk.
Additionally, in Int SDcard the KTKernel Folder with profiles and scripts.
First, install the Boeffla Config, then go into recovery and flash the kernel. Wipe cash and Dalvik and reboot.
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
Sorry for my bad English, with this kernel for lollipop tw viper4android work or not? Now i have flashed this kernel and boeffla apk
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Hi, I've tested the kernel on Temasek and on a few different Rome.
Bliss Pop Rome, Fusion, Darko ... CM12 unofficial
It's like Horsti G says everything must be deleted from the kernel KT otherwise there are problems. but I have only the KT monitor at run without problems
Especially on the Temasek Rome had 2 people tested the kernel for quite some time without any problems.
Unfortunately the support for other roms is not possible because there are always errors and differences with other roms.
a Idde would make a thread for all other roms. since one could then afford support?
@ cranio84
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
sorry for the translation with the googel translator
kind regards
Jakkomo 77
Ok i deactive boeffla sound setting, but where is a guide to install viper4android, because I have tried with more kernel on tw rom and don't work
For sure there are specialised threads for viper4android.
But wrong in this thread to discuss that...
Andi
Ok, i discute un this 3d because your kernel is correlate for me
After maybe a month of working in the kernel.
I guess it's about time to release the kernel for testing.
Downloads in the second post are only there for easy follow ups.
Please read all the sections below before trying out this kernel first.
This kernel comes with absolutely no warranties whatsoever, period.
XDA:DevDB Information
This field is required., Kernel for the Samsung Galaxy Star
Contributors
psych.half
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-15
Last Updated 2017-10-12
Downloads
Latest : kernel-mint2g-trilogy-stable-r10.zip
The latest version is tested to be booting on :
Stock JB4.1 with CWM 6.0.5.3 by @dabakale
CM-10.1 with Philiz recovery by @medved197938
CM-11 with TWRP 3.0 by me
If you are getting status 7 errors, while flashing.
Try with a different recovery, and if that doesnt help upload the /sdcard/liverepack.log along with recovery.log from your recovery.
Changelog:
Code:
==================================
r10 : Apr 7, 2016
- Added and fixed custom voltage control, It could be errornessly set lesser than 650mV.
- Added underclocking. Needs to be enabled manually, see post #
- Removed 1400Mhz and 1500Mhz frequencies, as it causes crashes on many devices.
- MTP should now work on both Stock/CM rom (needs testing )
- Fixed battery level getting stuck issue.
- Fixed brightness/constrast bug in stock ROM.
- Initial stable* release of trilogy version.
Extra downloads
camctl : script to enable/disable camera for RAM
How this thread is organized.
The OP has been broken down into sections. The first 20 posts reserved for info/wiki sort of.
So when things get updated/added it'll all be in the first few pages for everyone to see.
Each section will be short and to the point so you're having problem with one section.
And you're the type who just has to quote posts you might do so without getting on other people nerves.
And normally I just just ignore the forum's usual craptalks, but at this early stage of development, try to keep the noise minimal
Let's make some things clear first.
This kernel is not for you if you want a stable kernel.
CM11 should already include the stable version of this kernel, so you should just stick to that.
This kernel is only for CM11. No other roms will be supported or even considered.
This kernel is higly experimental. Freshly made, straight from the lab.
So expect some breakage of functionality, random reboots, bootloops and explosions (unlikely, but I gotta cover myself).
Flashing
The zip makes no backup of your current kernel as of now.
So if you wanna go back to shipped CM11 kernel you have two options.
i) Manually move the original modules to system and restore just the boot image from TWRP.
ii) Restore/flash the entire ROM.
As for flashing the zip, you should burn it on a CD, and choose boot from CD in your PC by keep pressing F10/F12 at BIOS screen.
Well no but, you should at least be familiar with flashing and backups.
Breakages
Camera:
Well, it's due to updated ION drivers, which are not compatible.
In the meant time I have disabled memory allocation for camera.
Which should give some extra free memory.
If there's any other stuff broken here but not while using CM11 kernel.
Post it here instead of there. But not the stuff broken in shipped CM11 too.
What are not bugs.
24mb of less RAM:
Linux ate the RAM, no really.. linux eats RAM http://www.linuxatemyram.com
Well it's due to enabling memory cgroups.
Android says keep it enabled for low ram devices.
As per https://source.android.com/devices/tech/config/low-ram.html
Also, see the below sections for frequency scaling
Bug reporting
You know you won't get help the next time from a kernel dev if you give them a logcat.
So get the dmesg or no help for you.
And /proc/last_kmsg is not working due to ram console issues.
So if you're gonna be reporting random reboot issues, make it reproduceable.
And make it precise. If the issue is caused because you have installed, some 10 or 20 other mods.
Good luck solving it.
What are in the kernel.
You get your usual stack of IO schedulers, governors, dynamics and mods. They won't be included in the change log below.
I don't even know what half of those are.
So don't ask me what/which one to use. See them for yourself.
You also get some usual tweaks, which can be changed with any kernel control app you like.
Same don't ask what/how to tweak.
If you want something to be added that you don't find. Let me know, and I'll see what I can do.
Frequency scaling
Frequency scaling is already included from r3 onwards. So the previous instructions no longer applies.
The default min and max frequency is 1Ghz and default governor performance. ie. same as stock.
Any change to that is your own choice.
And your own loss if something goes wrong.
There are some limits to it.
i) It can be only changed 10 times a second, so it might cause lag sometimes.
So choose your governor and scaling wisely. Battery or performance. You decide.
Underclocking has been removed.
Going below 1000Mhz makes no sense, as the core voltage is the same.
There is no point in reducing frequency, if the power consumption is constant.
Overclocking has it's own section. See below
Overclocking
First if you were using the older broken cpufreq driver and were in the impression that you were at 1.6Ghz you're gonna damage your device.
The driver written by me, really overclocks the cpu and the whole system, yeah mines fractured too. Nothing I can do about it.
So use at your own risk. And don't discuss about the safe overclocking frequency. There isn't any.
Issues caused by overclocking are not issues. or bugs.
I won't give you any overclocking advice. But here's one anyway.
Overclock only when necessary and do not keep the values persistent at boot, "Set at boot" in apps.
Changes from stock:
A lot of thing has been updated, changed, modified. I will have to go through source again.
A short list of changes I can think right now will be posted soon.
- The you know, built with some GCC-5 Linaro toolchain and O2.
- Cherry picked upgrades from various kernel sources.
- Disabled a whole lot of Samsung debugging.
But there's more... see the Github repo.
reserved
#Reserved
#Reserved
#Reserved
Source
kernel:
https://github.com/halfpsych/kernel_mint2g
cpufreq-driver: https://github.com/mint2g/kernel_module_cpufreq-driver
Contributing.
Any contributions to both source and wiki are always welcome.
You can help fix typos or better clarify some sections or even help to write new ones.
Credits
For bringing CM11 to this device
- corphish
- Dreamstar
- TeamButter
- All others involved in CM11 mint2g project
Initial testers and bug reports:
- Dark Knight Begins
Custom OxygenOS OneplusX - COSX ROM
Intro
First of, I'm not a developer. I'm just a guy who put a couple of things together. I'm a bit above noob-level, so dont excpect high end stuff like some prestigious developers. That being said, I have put this ROM together because of the lack of ROMS based on our original software for the OneplusX. Don't expect to much, the most things happen under the hood. So no shiny backgrounds or boot screens.
Disclaimer
You know the drill, flashing happens under own responsibility. I have tested everything on two devices, and will not put anything online that can possibily harm or damage our device in any way. This being said, if you need support, ask in this thread.
Open Source
The ROM i have created is for the community, which in my opinion also means it should be fully open source. You can edit everything you want. You can use it as base for whatever you like. No need to ask permission or give reference. Seeing the amount of customized original software, I would be happy to see more custom oos roms pop up. No need to put restrictions on anything. Please just don't bother me with antutu benchmark related complaints.
ROM
Now lets talk business
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
perhaps more, cant remember everything
Instructions
1 Obtain Root access and Custom Recovery
2 Download zip file from link
3 Boot into recovery
4 Install zip from sdcard
5 Wipe data and cache
6 Reboot phone
7 Wait for system deodexing (+/- 10 min)
8 Restart phone again
Download
Link will be provided later on
Thanks
- Thanks to everyone buying this phone and making the community what it is today
- Thanks to everyone in the past learning me how to soup a rom together
- Special thanks to Boeffla for providing his kernel and support of integration in this ROM
- If I forgot someone, Thank-you:good:
XDA:DevDB Information
COSX ROM, ROM for the OnePlus X
Contributors
winesh
ROM OS Version: 5.1.x Lollipop
Based On: OxygenOS
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2016-04-04
Created 2016-04-04
Last Updated 2016-04-03
Notifications
- Link will follow in the evening
Changelog
-x-
What's next
- This is version V1. If you have wishes or requests for a future version, please reply. I will see if i can add it in version V2 or upcoming versions.
- Everything is confirmed working. If you by any chance run into bugs, please report them.
So what's different about this rom than stock OOS? I'd give this a shot!
Interesting, I am waiting for the download link and changelog / feature list to give it a go.
Finished compiling, link will be axailable within couple of hours.
@joey24z1 for difference see rom details
@batam for feature list see rom details
Deodexed
Click to expand...
Click to collapse
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
By theming support you mean layers? Or what..?
namquang93 said:
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
Click to expand...
Click to collapse
http://codeversed.com/deodexed-vs-odexed-rom/
Hi. @winesh...
I think placeholder threads are not allowed as per the rules...
However, thanks for your contribution ..looking for download link ASAP
Sent from my ONE E1003 using Tapatalk
I think OP managed to put most of the tweaks one can do to the Stock OOS and created a zip flash package.
IIRC, I did pretty much similar things on my Stock OOS before moving over to CM13.
Good Job OP saving a lot of time for those who want to enjoy the stock experience.
Coud you post a benchmark test?
solidwave643 said:
Coud you post a benchmark test?
Click to expand...
Click to collapse
Did you read the op? Flash the rom and run the test yourself....
Get the link..
winesh said:
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
Click to expand...
Click to collapse
Good work :good: Might try this as I kinda liked OOS but I'm currently running Marshmallow and CM based crDroid, so also might not go back to Lollipop
Biggest issues I had with the stock OOS 2.2.0 were:
1. Camera in low light situations. I think it's fixed here with Snapdragon camera?
2. Random rebooting, sometimes few times a day, sometimes few days without. Mostly occurred when playing any game with stock ROM. Is this custom OOS more stable?
3. I could not assign Menu action to HW buttons e.g. long pressing and this led to situation where I had to install Xposed framework and some module to get Menu in Titanium Backup to change backup location to SD card. Is this fixed here with Custom Hardware keys remap?
I know I should test this ROM myself, just pointing out biggest issues I had with stock OOS.
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
coolasnju1993 said:
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
Click to expand...
Click to collapse
Same request here. :fingers-crossed:
Thanks for your work!
So proximity wake up ambient display works in this rom ?
And what type of themes are supported ? Layers or CM ?
Theme support
So OP, You have provided Layers or CM theme engine into rom?
Though Layers supported Stock OOS 2.2.0(Partially not all the themes were working) .
anshu goel said:
http://codeversed.com/deodexed-vs-odexed-rom/
Click to expand...
Click to collapse
I said that deodexed is slower than odex rom. So that means this rom is slower than original OOS right ? Please correct me if I'm wrong.
Waiting for download link...
Will give a shot today...
This thread may be under construction, watch out!
An introduction to my new Oreo sauce...
This is a modified LineageOS 15.1 ROM meant to fill my personal needs, including my minimalistic Lambda Kernel out-of-the-box and a few customizations to provide a different, privacy-focused, Android experience, just for you.
What are the very best features included?
~> Always latest vanilla LineageOS 15.1 codebase;
~> Root virginity preserved, unrooted;
~> SafetyNet bypass out-of-the-box;
~> Google PlayStore device certification;
~> Privacy oriented Bromite web browser;
~> Compiled with SDClang LLVM 4.0 toolchain;
~> Dex-preoptimization of boot image and system server;
~> Minimalistic Lambda Kernel, more information right down below.
What does this magical Kernel support?
~> Cleanly built on top of the latest QCOM reference Kernel for MSM8996;
~> Up-to-date camera_v2 driver stack according to Nougat (LA.UM.5.5) code base;
~> Proper OEM Kernel code adjusted per target (ZL1/X2) and adapted to the new base;
~> Adjusted headset detection framework to account for Type-C adapter;
~> Optimized and adjusted for the -O2 GCC compilation flag;
~> Minimal configuration with the bare minimum drivers needed;
~> Safe fast charging input, regulated per stock Kernel definitions;
~> A little bit faster panel wake up and touchscreen initialization;
~> Unlocked bootloader state bypass, reports green.
What are the known issues so far?
?> Ambient display feature makes the panel wake up a bit funky, you'll see it when compared to the disabled state, which doesn't have that funkiness.
?> Time registering is broken, the daemon doesn't write properly to the Kernel for some reason and ends up not having the correct time after a reboot with the internet turned off.
?> CDLA sometimes has some pops in the background when not listening to anything, pretty minor though.
Nice, where are the downloads?
The downloads are available in the dev release tag in my Github's lineage_releases repository, there you'll find the zip file for installation and the md5sum for checking the file's integrity.
#WelcomeToOurWorld
XDA:DevDB Information
LineageOS Pro for the Le Max2, ROM for the LeEco Le Max 2
Contributors
GalaticStryder, Sultanxda
Source Code: https://github.com/GalaticStryder/android_vendor_patcher
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Chinese 26S
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2018-05-05
Created 2018-04-05
Last Updated 2018-05-05
Reserved
Mine.
Did anyone mention FAQ?
A series of questions, answers, and wonders about all the things she I said in case you didn't get it already.
&> Q. Why isn't this a new project instead of just a simple variant of LineageOS? There are already a ton of them...
&> A. I think there's already a ton of Android "projects" and I don't feel like nor have time to create yet another one that I probably wouldn't be able to maintain for long.
&> Q. How much time will this "variant" be supported?
&> A. Only future wilt tell us but most likely our brave "variant" will resist at least one Android cycle starting from now, all the way through P, even after LineageOS officially drops it we can still have some OEL support if other developers keep the game going.
&> Q. How does it diverge from official LineageOS builds?
&> A. This one aims at providing a snapshot-like experience - if you remember CyanogenMod gold era - which uses the non-debugging user flavor instead of userdebug as Google keeps pushing their draconian restrictions to have access to their apps and services, we need to fake it to avoid forfeiting.
&> Q. My device is "certified" on Google PlayStore, how?
&> A. The bootloader green check in Kernel and user flavor made it possible. I'm not sure how much longer will it take to Google before they go with something deeper to restrict the access of their services by custom ROMs unconditionally. This is a trick though, your device will never be certified with an unlocked bootloader and non-OEM ROM.
&> Q. Will you ever include root support out-of-the-box?
&> A. No, never. You can flash Magisk if you want it, the latest the better in this case. Not sure about the addonsu from LineageOS itself as I never used it.
&> Q. Will you include Dolby Atmos, ViperFX, $(insert_nice_name_here) out-of-the-box?
&> A. No, not at all.
Heeyo! Are you using official LineageOS trees for building your variant?
prajjwal.laad said:
Heeyo! Are you using official LineageOS trees for building your variant?
Click to expand...
Click to collapse
Synced today, no fools included
Well cause i liked your kernel i will try out this rom also!
Nice timing tbh. Just bricked my current rom rn.
True. I've been using his kernel since 24 hours and damn it is the best kernel for x2. My phone's battery temperature doesn't cross 42°C even though my country's normal temperature outdoors is around 38-40°C these days. I get around 20%/hour drain on medium usage which is awesome for my 15 month old battery. Will definitely flash your rom and give feedback.
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
This is Awesome! The legend is back!
I am so pumped right now! :d:d
@GalaticStryder
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
cloche;76136607 [user=6175749 said:
@GalaticStryder[/user]
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
Click to expand...
Click to collapse
First: Big THX @GalaticStryder for this awesome build.
Tested it for an hour now and everything seems perfect. Sound quality is excellent (through Headphones). Rom itself very smooth.
Will report battery Backup later.
Gapps are NOT included, Root is NOT included.
Heyyo, congrats on the release GalaticStryder! She sounds super promising!
A request
I am going to make a very dumb request, can you create an overclocked kernel for this build? Would it be possible?
Thanks so much
Has same bugs as official (eg slow motion video recording not working)?
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
maylton said:
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
Click to expand...
Click to collapse
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Tell me, how about Vulcan drivers? Are they present in yours build? If not, do you plan add them?
Thx 4 ur work
N-Gage4ever said:
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
Click to expand...
Click to collapse
why the **** you go on ranting on every roms about this, already GalaticStryder has explained u regarding this in his lambda kernel
I've been trying since last night, unfortunately I noticed freez and random reboots.
Fp is very very slowly.
TheMichalos said:
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Click to expand...
Click to collapse
Yes, that would be the best choice for everyone.