Related
Thanks to Leshak , AndSecTest, mimocan, Unhelpful, xan, Supercurio and husq510 for the help.
This project started based on information found here:
http://forum.xda-developers.com/showthread.php?t=740514
But is has soon revolved into more fixes, patches and hacks. Thanks to all the developers involved and do buy them beers so they can continue to work on the fixes.
I've tested it to work on my phone but i cannot guarantee it will work on yours or if it will damage your phone so use it at your own risk. See known issues below if the problems have been resolved
Primary Features
- ext2/3/4
- Support I/O Scheduling for CFQ (stock), Noop, Deadline and Anticipatory
- Overclock and Undervolt support
- Overclocking for better performance. If you do not want to OC, use SetCPU to set Max at 1Ghz and enable checkbox Set on boot
- User defined Undervolt to save battery especially at lower frequencies. Use Xan's app for easy GUI control - here
- Also use Xan's app to change IO scheduling
- Rooted ADB shell for Android commander compatibility
Requirement
- i9000
- For Eclair 2.1 Only (Will not work on Froyo firmware)
My setup for cross compile without wakeup lag
- Use ct-ng crosstool
- Copy config file from arm-unknown-linux-gnueabi
Download
See attachment
Stock Kernels for reverting
Stock JM3 v3 kernel
Stock JM2 kernel
Stock XWJM5 kernel
Instructions:
- Extract the tar file from .7z
- Load tar file in PDA using ODIN and flash
- Do not check repartition and do not use pit file
- Use SetCPU to adjust frequencies
Reporting Problems
Please provide information below to help me understand:
kernel version: (eg oc120uv2-ctng)
UVLF setting (if kernel supports): (eg 50)
UVHF setting (if kernel supports): (eg 25)
descriptions:
Known Issues
- ondemand setting is unstable (need more verifications)
TO DO LIST
- BFS scheduling
- kernel modules (submit request)
Changelog
oc120_voodoo_b4.2
- enable CWM support even with voodoo ext4. Caveats: CWM will unmount /data after nandroid backup, you will not be able to remount /data in ext4 until you reboot back to recovery. Also, restore does not work when trying to restore /data.
- fixed check for debug_mode (it used to create logs in /sdcard/Voodoo/logs regardless if you enable*debug in /sdcard/Voodoo/)
oc120_voodoo_b4.1
- BLN patch v4 from neldar (http://forum.xda-developers.com/showthread.php?t=772672)
- All credit goes to author
- Signed update.zip format so rename file to update.zip and copy to /sdcard
- use recovery to flash
oc120_voodoo_b4
- updated to voodoo b4 (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120_voodoo_b3.1
- fixed init.d not working
oc120_voodoo_b3
- remove performance governor from startup cos i9000 dont need that
- added init.d support
oc120_voodoo_b2
- Use stock GPU ~200mhz table
- Voodoo2 lagfix (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120uv2
- Unhelpful patch for GPU table (http://github.com/Unhelpful/linux-galaxy/commit/5a729d3e2189159a20b00e0c331f0b112490e075)
- Interactive governor (http://github.com/Unhelpful/linux-galaxy/commit/aea72a98a2f261901d6f28f2d1deae3921d35948)
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 50mV for 1-1.2ghz)
- Setting increment of 25 (eg 25,50,75,100). Anything out range may hang
- Anything above 100 will be set to 100 (but I doubt you can get 100mV without crashing)
- After setting, do ur benchmarks and if everything is stable, you can add the command above into your init script depending which lagfix you have, add into your script.
Thanks!
Some questions:
1) the first thread about oc mentioned 1.2ghz, was this unstable for you?
2) Is this over-volted, under-volted, or no changes in voltage?
3) I'm guessing if I update to this kernal, I will loose any features of other kernals, like the lag-fix kernal?
I hope you can persuade the other devs to include this in their roms.
It this just for the unbranded SGS or does it work for TMO vibrant too?
Novek said:
It this just for the unbranded SGS or does it work for TMO vibrant too?
Click to expand...
Click to collapse
the kernel is just for the international version
it is just a test, i hv not test the limit yet.. this is a new phone so want to take it easy
i kept the voltage stock so just overclock a little and if its stable, will do more . More testing and reading is needed before i touch on the voltage.
it does not include mimocan's mod, i will work on it next release
Not Work
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Sir-ay said:
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Click to expand...
Click to collapse
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Nice job cant wait to see how high the new hummingbird cpu can go. The galaxy s 2 has same cpu and is running at 2 ghz (if the leaked info is correct). I hope we can push it up to 2ghz with out to much voltage/heat increase.
[[ Cold ]] said:
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Click to expand...
Click to collapse
upps
I will OC!!!!!!!!!!
Do you notice the postive effects of the overclock in any way? What does it do with benchmarks? Also do you test for (temperature) stability with some games as well, as they use the graphics card a lot which is on the same chip. Even when not overclocked the SGS can get prettty warm.
Installs nicely, oc ok to, but dont see that much increase in linpack.
Nice work tho.
Any chance to have ext 4 support in next update?
Thanks :
updated to v2
raspdeep said:
updated to v2
Click to expand...
Click to collapse
you're fast, lol. Thanks.
INeedYourHelp said:
your fast, lol. Thanks.
Click to expand...
Click to collapse
update before i go to bed
Guys, how do I use SetCpu?
Was 1.2ghz unstable?
Sent from my SGH-T959 using XDA App
interested in this... Allthough the phone does seem to get hot during heavy use, it doesn't get 'too' hot.
I have seen about 47 degrees celcius max read from battery temp (which seems to be cpu temp on our phones as my battery was stone cold)
Hi any possibility get v1 without mimocan.
Got samset including it nd sgs wnt boot cause of mimocan included.
thanks
I am using JM2. Does this make my phone any faster? Does it maked it lag free?
After tested this oc.. i am bit unsure: i get no performance increase... Is it confirmed that its functional?
CPUFreq Successfully Installed and Running
Please visit my website for additional information
After receiving alot of positive results from my Kernel and several releases later. We have arrived at RLS 5.9, a prototype build incorporating CPUFreq for CPU Scaling and Idle control, and a modified version of Power Management. We are at a release stage of this Alpha build, and approaching Beta, where it is as follows:
Each build that is released that has an update to CPUFreq will have an update to the first subversion in the build version (eg. RLS5.9.1.0)
Each build that is released that has an update to Power Management will have an update to the second subversion in the build version (eg. RLS 5.9.0.1)
And of course each upgrade to a specific subsystem of the Kernel will up the version number of that specific subversion.
Current Release: RLS 5.9.2.2
RLS 5.9.2.2 will mark the beginning of the Beta stage out of Alpha stage. This release is showing far more promising results than my initial CPUFreq release.
I just want to personally thank all who have been supporting me and reporting any and all bugs that have been coming in, as I have been squashing them left and right in preparation to improve our Kernel for our phones to make them more feasible for everyday use.
Currently Being Tested:
Power Management - Reverted some old changes to the power management code, switched too Apps Sleep. Made some minor changes to the original pm.c source code and results are promising. Running VanijlEclair RLS11, and in rare cases the phone still crashes while sleeping, which I believe is related to the phone hiccuping when going to sleep, which in theory could completely blow up the timer that Apps Sleep uses for sleeping. I will investigate this part further, but so far, RLS 5.9.2.2 is much more stable than my previous release.
CPUFreq - No changes to the source code, still attempting to modify permissions so Android can modify the files that are required.
HAReT Users - Thanks in large part to V3rt!g(o) HAReT users can now boot the Kernel. I have made a slight modification to the default.txt file provided in the RLS 5.9 HAReT archive that uses Apps Sleep instead of Power Collapse. From what was reported, the Kernel takes about 2 minutes to initialize from WinMo, but after about 1min30sec to 2min, Android should begin loading.
Radio ROM - Currently Testing Radio 1.71.09.01, and so far it seems very stable and provides better battery usage.
Current Release (RLS5.9.2.2):
Kernel - HTC Polaris support re-introduced.
CPUFreq - Has been installed, and working inside the Kernel only. Android does not recognize CPUFreq correctly.
Processor - MSM-7201 processor increased from 384MHz to 528MHz
Stability - Has been improved further. Phone correctly sleeps and wakes properly. Still occasional crash occurs, but is random. Could go a full day without a crash, or could crash every 4hrs. Issue might be related to how much the CPU is being utilized at the time of wake up.
Power Management - Power Management restored to near WinMo states, still not as good as RLS5.7, but within range. Phone will last a full day of occasional use, and about 80% of the day on moderate use.
Initrd - New BootLogo has been made, and inserted into initrd. Unfortunately boot menu is not accessible. Made install scripts to compensate.
YAFFS2 - Exclusively does ECC checking on it's own without any help from the NAND driver. This should help with data corruption, but is not a permanent solution.
YAFFS2 - Disabled Forced erase chunk checking, slight increase in response time and decrease in read-time.
MTD - Disabled Verify NAND Page Writes
MTD - Disabled GPIO NAND Driver
EXT - EXT2 is currently disabled inside the Kernel. EXT4 has been fully enabled, aside from journaling, and is fully supported in the kernel and install scripts.
System - Switched from DG (High Resolution) Timer, to GP (Low Resolution) Timer.
System - Fully disabled High Resolution Timer -- Provided a decrease in kernel size without loss of performance.
sysfs - Enabled configfs. This will unavoidably increase RAM usage, but allow easier access to sysfs.
MSM - Performance Counter Driver enabled.
FrameBuffer Driver - Decreased fake-vsync delay from 10 to 5. Less times snow effect appears.
Known Issues:
Internal CPUFreq coding is unable to scale the processor, but the hacked msm_cpufreq_* functions are able to control the processor speeds. This will explain why CPUTuner and other Android software is reporting the CPU running at max speed. Will continue to investigate and work out problems with the coding.
JIT Compiler causes issues with framework.acore. Avoid using if possible.
CompCache not the cause of untracked PID errors -- Still investigating cause, though now understanding that it is related to data corruption.
Possibly depending on Radio, GPS takes quite awhile to acquire if not at all. -- Will investigate by flashing an older/newer radio.
Standby code not fully working due to being incompatible with clock code changes. Attempting to re-write power management code to be better compatible with the new clocks code.
CPUFreq Specifics:
Governors - Currently CPUFreq supports the following governors and can be changed while in Android using the Terminal: ondemand, conservative, powersave, performance. Userspace is currently disabled inside the Kernel.
Frequencies - Baseline frequencies the CPU will scale to but not limited too are: 81920 (82MHz), 122880 (123MHz), 245760 (246MHz), 384000 (384MHz). These are just placeholders to control where the CPU needs to scale too base on usage, it will go between lets say 82MHz and 123MHz or use one of the two.
Userspace - Until I can verify CPUFreq is fully operational without any issues, I will not enable Userspace Governor at this time.
Kernel Modules
File Attached to this Post, see below.
This Kernel has been tested with the AT&T Tilt variant of the Kaiser. Using it on any other Kaiser would in theory produce the same results, but due to minor changes in the hardware of each variant of the Kaiser, I'm still going to stress caution when using this Kernel with any other variant of the Kaiser
Things to note about EXT4: This file system will increase read/write cycles to your SD Card. Use with caution as it will decrease the life of your SD Card. Though since Journaling is disabled, read/write cycles will have decreased, but they are still higher than what they would be if EXT2 was used. If you do not feel comfortable having EXT4 on your SD Card, do not use this Kernel as there is no way to use EXT2. You have been warned.
Things to take note with this Kernel: Do not enable JIT compiler under Settings, as this has produced constant FCs with the acore framework. It is recommended that you enable CompCache and set it to the default 18%, as this provides a significant performance boost, and decreases Home screen closures while running other apps.
USE THIS KERNEL AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR ANY DAMAGES DONE TO YOUR PHONE WHILE USING THIS KERNEL.
Woohoo ! First Post!
Thank you Krazy-Killa! Will definitely try this now will post after testing!
I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?
Hello Krazy-Killa,
Appreciate your effort !
I just installed it on my TYTN II and so far going well -edited .ngh to change the key mapping to normal.
3G works fine. yet to see BT,WiFi &GPS and overall otherwise.
I have tried Scoot's CM7 RLS1 build 2 days ago.is there any major changes you did - i feel some audio notification alerts changed w. r. t. Scoots.
how can i use those audio files if reqd-i mean can copy&dump to a specific folder and repack.
but its not really matter..
At the moment 'push' works fine and eager to see any 'server connection' problem will occur later with the email client.
i have radio 1.70.19.09
Thanks once again for the post.
Cheers !
cerebralgenius said:
I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?
Click to expand...
Click to collapse
I will release the modules as a seperate androidupdate file this evening.
@chandra_100,
All my testing shows BT, WiFi, and GPS working. This Scoots CM7 build I released is just repackaged with my built modules for easy install.
Sent from my AT&T Tilt using XDA App
“Removed support for HTC Polaris”
That’s too bad，poor Polaris，555555555555555~
The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault
dark_prince said:
The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault
Click to expand...
Click to collapse
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.
Krazy-Killa said:
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.
Click to expand...
Click to collapse
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.
for me kernel can't find data.img
Ive go some kind of problem. Im using fresh froyo and when I installed your modules update than I got hang in boot. Excatly at "adb_open" line. Without update everything is ok except wifi.
Sorry for my poor english
Neo2SHYAlien said:
for me kernel can't find data.img
Click to expand...
Click to collapse
I'll look into it. Though I may know the reason why, so I'll do some more testing, and will release once I have it fixed.
scooter1556 said:
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.
Click to expand...
Click to collapse
I'll update my local bootenv, thanks.
Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device
MaRekRM said:
Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device
Click to expand...
Click to collapse
That was mentioned in the known issues, don't worry my next release will fix that (currently testing). Plus it'll add full EXT4 support like with clemsyn's kernel but you can format your SD card with the device now as I have updated initrd.
Sent from my AT&T Tilt using XDA App
Flashing
I'll try... flashing right now.
what about ipv6 support?
*EDIT* nevermind, i just saw that ipv6 is implemented.
Cannot restore databackup.img trough install menu...
I think this kernel canot handle the img fs. Mount is failing.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.
Backup FS
Krazy-Killa said:
It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.
Click to expand...
Click to collapse
Probably the script that is generating databackup.img still using ext2.
tiagoclc said:
Probably the script that is generating databackup.img still using ext2.
Click to expand...
Click to collapse
Yep, it was exactly that. Just made the necessary changes, and compiled a new kernel. I'll go ahead and throw it out, but for now I'll point out that I haven't tested it so, please let me know the results.
Init itself is already setup to mount all loopback and SDcard partitions as EXT4 where applicable.
Just use atools to configure the kernel to use /system and/or /data on NAND or SDCard.
Why did you remove polaris support? I think that are plenty of polaris users that want to test your kernel
Thanks
[15.July.2011][ROM][GSM][2.3.3] ◄► Overcome ROM v3.0.1-JUPITER ◄► Kernel v3.3.0 ◄►
DISCLAIMER: You know the drill, I am not responsible if loading this rom makes your Tab melt, explode, disintegrate, or cause harm to anyone near it. (I am fairly certain none of that will happen though )
Change log in second post.
ROM FEATURES
BGJP4 Base Rom - ANDROID 2.3.3
Overcome kernel v3.3.0 included
No Modem is included - due to a variety of personal preference I decided to leave that a la carte
Fully Deodexed
Fully Zipaligned
Rooted with busybox installed
Reboot/Recovery/Download options added to the power menu
Accurate battery mod with gingerbread styling
Blur removed across system (i.e. behind power option menu) - significantly improves performance
Power Off confirmation disabled
Screen off animation enabled
Overscroll Glow effect enabled
Added AppWidgetPicker
CSC set to XEU
Ads Blocked
Updated Market to 3.0.26
Updated Maps to 5.7.0
Flash Player removed due to compatibility issue - install from market and you'll be all set.
Updated GMail to 2.3.4
Updated YouTube to 2.1.6
Updated SamsungApps to 2.5.039
Updated StreetView to 1.6.0.6
Updated Thinkfree Office Suite
Removed Startup/Shutdown sounds
Cool boot animation
A2DP Bluetooth Connection Fix Integrated
SIP calling enabled over 3g AND WiFi
Fugutweaks integrated
Browser mods (enabled "Default Zoom" in settings, added "User Agent" in settings, set plugins to "on demand" by default)
KERNEL FEATURES
Support RFS/EXT2/EXT3/EXT4
OC/UV with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Replaced kernel jhash2 with jhash3
Adjusted kernel HZ value to improve smoothness
Optimized lowmemorykiller values
Optimized compiler flags
Voodoo Sound v10 (courtesy of supercurio)
Voodoo Lagfix (courtesy of supercurio)
Overcome CwM Recovery v4.1.0.9 (Custom built Clockworkmod v4.0.0.9)
Full support of internal/external SD cards in Recovery
Simple I/O Scheduler added and set as Default
Kernel tweaks to VM and Scheduler for better performance
Built in CIFS/TUN/SlowWork support
Touchscreen Undervolting (courtesy Koxudaxi)
RAM Undervolting
Stochastic Fair Blue (SFB) Network Scheduler
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications (Thanks to Neldar for the mod and Koxudaxi for the patch)
INSTALL GUIDE
http://www.teamovercome.net/?page_id=64
DOWNLOADS
http://www.teamovercome.net/?page_id=558
TIPS AND TWEAKS
http://www.teamovercome.net/?page_id=68
FAQ's
http://www.teamovercome.net/?page_id=66
SOURCES
https://github.com/alterbridge86
The best is yet to come!
ROM AND KERNEL CHANGE LOG
http://www.teamovercome.net/?page_id=171
Overcome v3.0.1-JUPITER
Overcome Kernel v3.3.0 Included
Themeing tweaks (Thanks to DarkPal and friends)
Market updated to 3.0.26
CSC Changed back to that from JQ1 (this should resolve the issue with downloading zinio/kobo/etc.)
Overcome Kernel v3.3.0
Built using CodeSourcery 2011.03 toolchain (faster and more power efficient code)
Overcome CwM Recovery Updated to v4.1.0.9 (Based off ClockworkMod Recovery v4.0.0.9)
[CWM] Option under Tweaks to enable/disable shortened backlight fix
[CWM] Nandroid restore no longer borks the kernel
[CWM] No more annoying "back button disabled" (Hooray!)
[CWM] Shortened Yes/No confirmation menus
[CWM] Make /dbdata wipe when executing "factory reset/data wipe"
[CWM] Make /emmc/.android_secure wipe when executing "factory reset/data wipe"
[CWM] Complete restructuring of menus
[CWM] Streamlining of commands and elimination of some never used features that were cluttering the interface
Updated to Voodoo Sound v10
Numerous upstream patches
Add V(R) I/O Scheduler
Increase voltages to pre-Icarus levels
Removed device detection script (should resolve all issues with some users getting hung at Samsung screen or having no conversion/cwm)
Tweaks to lowmemkiller behavior
Added arm enhancement to allow CPU-supported unaligned accesses
New release - new thread! Idea behind this is to keep the amount of posts people have to crawl through down to a minimum. Enjoy!
OH WOW!!!!!!
You're Great AB86 and all the OC team
Thanks
Sent from my GT-P1000 using XDA Premium App
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Pharaohnough said:
OH WOW!!!!!!
Click to expand...
Click to collapse
thanks friends
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
theduke89 said:
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Click to expand...
Click to collapse
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
alterbridge86 said:
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
Click to expand...
Click to collapse
Understood, thanks it was less complicated then I thought
Feedback coming soon for Jupiter!!! You are great, friend
Just drop by to say thanks that the jupiter kernel now works on my set up (DXJPE /w ext4). I'm going to drop off to sleep too as it's over 2am here, will post impression later.
sohrab1985 said:
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
Click to expand...
Click to collapse
I don't know what you're talking about
(It has the proper changelog now )
This looks and works beautiful. Thanks!
Remember, for every whiner there are hundreds of satisfied users which never say a word.
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
chevy383surfing said:
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
Click to expand...
Click to collapse
Had the same problem, made factory reset in CWM and then it worked.
Peter Unger said:
Had the same problem, made factory reset in CWM and then it worked.
Click to expand...
Click to collapse
I just tried a factory reset and it crashed. I just now got done going through the whole procedure again. I did a factory reset under privacy in the settings. Should I be doing a factory reset from within clockwork recovery?
I actually just got it working! Thanks again for the rom!
darkness1414 said:
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
Click to expand...
Click to collapse
Look, theming is really personal preference. Its impossible for us to satisfy everyone's taste. The team thinks that black notification bar rocks so that's that. If you wanna change it to white, you either..
1. Apply stock theme patch
2. Learn how to theme and change it to white yourself
Sent from my GT-P1000 using XDA App
Lovely work, once again, guys. Updated using the no-wipe method. No problems at all everything working fine. Love the signal and wifi icons. Looking forward to your next offering. Thanks heaps.
Sent from my GT-P1000 using XDA App
Thanks Alterbridge and Team.
Just installed JUPITER (no wipe) over ICARUS and everthing seems to be working A-1. Love the new boot screen and the ROM is very fast and very smooth!
Just for those that may encounter the same issue:
Had a little anomaly the first time I flashed. All seem to go as it should and everything worked as it should, however, under 'SETTINGS' > 'ABOUT DEVICE', it said that the kernel was 3.3.0 (#79), but the build number was still 3.0.0- Icarus (Also, on initial boot up the boot screen was still the old Icarus screen). So, I repeated the no wipe flash procedure and everything is now working as it should. Correct kernel and build number in settings.
Thus far everything is working A-1 on this super fast and smooth ROM.
Many thanks again to Alterbridge and the Team.
*** This kernel is now end-of-life, not supported and developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than three years to OnePlus 3, 2, one and X, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
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).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS 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 !!
To add: An open beta (aka community build) is NOT an official build supported here. If you use a community build and have issues, don't complain or even report. I am not merging any kernel changes from open betas into my kernels !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app (outdated at the moment).
I will refuse to give support if you do any undervolting/overclocking 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.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for OxygenOS 4.x.x kernel - Click here
Change log for OxygenOS 3.x.x kernel - Click here
Known issues
none
Features
Note: This kernel only runs on OOS 3.x.x for the OnePlus 3T - nothing else !!!
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.4.21 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: Impulse, zzmoove, elementalx, conservative, ondemand, blu_active
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, zen, maple
No CPU overclocking and voltage interface, no GPU overclocking and voltage interface
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Boeffla touchkey LED control (LEDs fully off, LED on screen touch, configurable duration)
CPU core profiles to restrict number of CPU cores being used (the OP3 does not hotplug based on load)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine: Headphone volume and speaker volume (only lowering volumes for speaker)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control
Swipe2sleep gestures
Boeffla generic wakelock blocker V1.1.0 (documentation)
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (only when data volume is formated with ext4, stock default is f2fs)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Hardware touch keys are locked as long as screen is in use (touched) for better usability
Swap supported
Doze mode switchable
Verifiedbootstage flag remove to avoid triggering safetynet
Various minor kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Entropies configurable
Automatic EFS backup
Integrated full busybox 1.27.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Security patches included, which are not in the official repo
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/androi...neplus_msm8996)
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 OnePlus 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
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 kernel only if you are running a compatible rom !!!
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.4.21 or higher for the OnePlus 3T 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
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
* Osm0sis
... 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 log:
OOS4
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos4xx/changelog.htm
OOS3
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos3xx/changelog.htm
--- Reserved 2 ---
Here we go!
First beta is online for you guys.
As always, find everything on www.boeffla.de
And just to stress it again: It is the VERY FIRST beta, so expect bugs!
Have fund
Andi
nice! downloading right now!
so happy to see you again andi! your kernel was simply the best on my galaxy S5 and I missed your affords in my S7!
so happy flashing to everyone!
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again, and I think Boeffla provides the best support of all. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
PS: I was probably the first person to like and subscribe to this thread. (within 5 minutes of thread creation)
Edit: Flashable stock kernels? Perfect, thank you @Lord Boeffla ! Does it revert any custom kernel to stock kernel?
Been with Boeffla since S3 and via OPO this will be my third phone with the kernel.
Thanks!
Skickat från min ONEPLUS A3003 via Tapatalk
knpk13 said:
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Click to expand...
Click to collapse
This is not possible on OOS in a clean way.
The kernel comes with modules which are placed in /system/lib/modules too.
So only flashing stock boot.img would not replace the kernel modules by stock ones. So it is only a "half-good" solution.
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
knpk13 said:
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
Click to expand...
Click to collapse
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
EDIT: Just tried it - cannot replicate that. Maybe your /data partition is indeed formatted in ext4???
(you can check by firing the following command in a terminal: mount | grep data)
Andi
Lord Boeffla said:
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
Andi
Click to expand...
Click to collapse
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off automatically every time, so I guess it's working fine. Yes I'm sure I'm on f2fs.
knpk13 said:
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off, so I guess it's working fine.
Click to expand...
Click to collapse
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I love ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Ok guys, evening hours here in Germany.
I am off for today. If you have any questions, you can also move over and read in the OP3 thread. The devices are - concerning my kernel - 99,99% the same.
So you would most probably find all answers to your questions already there.
Tomorrow I will catch up again.
Andi
Lord Boeffla said:
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I live ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Click to expand...
Click to collapse
I'm sure I'm on f2fs. Even TWRP says I'm on f2fs. 3T comes stock with f2fs. This is the output of mount | grep data, but since I'm using magisk I think the output has many partitions and I can't make sense of it.
I think the ext4 tweaks toggle is working fine since it reverts to off automatically when the app is restarted. Thanks!
Here is the output: https://hastebin.com/iwokiramek.hs
Welcome to the 3t Lord Boeffla.. Enjoyed having your kernels and support on the s5 when I was running that phone.. Look forward to the same here..
Sent from my ONEPLUS A3000 using Tapatalk
Lord Boeffla said:
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
Click to expand...
Click to collapse
nice, been waiting for this since day one. :good:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
inzaghi75 said:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
No. OOS 4 has not yet been officially released and no kernel source has been released.
christmas is here since andi is our santa.
welcome to the 3T world.
loyalists like me have been waiting for you perhaps since the device was launched.
glad OnePlus and XDA did such an awesome thing to distribute devices to devs.
been following your work for a while now.
your kernel turned my OpO into a beast.
just flashed onto my 3T.
will report issues as and when(and if) I can find them.
cheers
Glad to see you here Andy!
finally you will develope on 3T:good:
Glad to see you here Andi:victory:
I use your kernel since Galaxy S3, also flashed it on my opo and my wife's opt.
:good: Now the kernel it's running very well on my new op3t.
initial thread here, further clarifications in recently added posts below OP/1st post
Lunar-Kernels
tl;dr - too long didn't read / first things first
Stock ROM kernels are attached in posts #1-4 or link to Google Drive
AOSP/LineageOS kernels are attached in post #5 or folder
simply dropping the folder with kernels here (Stock ROM):
https://drive.google.com/open?id=1xL5gEiG-fjzTuSGM_kUDsrOKy-jTtGr1
Description: 3 sub-folders (thus kernels) available:
"old" shouldn't really be used, this is a very bare to LG stock source kernel and (probably) using outdated ramdisks which prevent FM Radio, Mirrorlink, etc. from working
"stable" stable has gotten more testing (or more recent fixes) and is deemed fit for daily driver usage
"bleeding edge" is newest branch, very experimental changes/fixes or just the very latest kernel (if those don't end up in "stable" already)
Stable and bleeding edge are the
Further notes for "eas":
From the tests so far - it has turned out that power consumption ALWAYS was higher compared to HMP and/or the default shipped LG kernel (tweaked HMP)
So the best results up until now was to underclock CPU, underclock GPU (or keep at lowest 1-2 levels) and add tweaks to shut phy power source off for display, this is similar results like anandtech with Exynos EAS/HMP tests: https://www.anandtech.com/show/12620/improving-the-exynos-9810-galaxy-s9-part-2/3
Meaning: NO EAS kernels until further notice - only HMP kernels will be developed/provided right now
Usage case: [outdated]
"old": should work pretty reliable, everything is built conservatively & close to stock one of the first kernels
"stable": probably great daily driver material - FM Radio & MirrorLink, etc. still broken
"bleeding edge": just the latest and greatest from upstream, security, tuning, etc. - features might break in the process
eas [attached here]: daily driver, long running for lots of reading, lots of watching videos, high SOT demand ; suitability for gaming has yet to be evaluated
NOT working and probably will NOT in the near future (or at all): [outdated]
- FM Radio (broken with "old", "stable" kernels - those use v300 ramdisk)
- MobiCore - thus MirrorLink, etc. (broken with "old", "stable" kernels - those use v300 ramdisk)
- FM Radio & MirrorLink currently works with bleeding edge kernels
Notes (Kernel):
This kernel is built first and foremost FOR ME and shared with the community to benefit from that work,
you don't owe me anything and I don't owe you anything
like with Sony (yeah, even Sony !) and other vendors with their modified, proprietary non-AOSP ROMs - kernel development is extremely bothersome, each few commits kernel doesn't boot or compilation fails, so don't expect e.g. 4.4.137 kernel or catchup with latest codeaurora changes since that takes simply too much time and work (time, effort, nerves, etc.)
tested on H930 (Europe) V30 ONLY, test at your own risk on H930DS (dual SIM) or other devices; ramdisks and device configs WILL differ (global defconfig used - so compatiblity should be higher, limitations/compatibility issues with US, Korea and other models possible)
You need to have knowledge how this device behaves in case of flashing broken kernels, filesystem corruption and other worst-case scenarios
You must:
stay calm all of the time while flashing and must NOT do anything rash or chaotic
know how to get into bootloader/fastboot mode via USB-cable (when device is off) OR via adb command from a running system
know how to force the device to turn off (it will turn on again but that might help in certain cases) - this way you easily can get into fastboot/bootloader again
know and/or have a basic understanding that the device will settle most issues on its own
have your device charged to a battery level AT LEAST to 50-60% in case boot loops take longer (it is caught in boot loop) and you can't quickly turn the device off anymore
know/expect that flashing Magisk and other mods most certainly will lead the device too boot several times ("artificial bootloop") and might get you uneasy or confused, we need to figure out how to speed up the process that it finally boots into the ROM
potential issues & potential remedies/fixes: [up-to-date]
might have high load unless rctd disabler is flashed (root detection tool) => flash rctd
might not boot unless no-verity is flashed, custom ROM => flash no-verity
might not boot or work with encrypted phone or encrypted anything => should be self-explanatory, don't use LG encryption on custom ROMs/mods
some security functionality might not work => TEE/qseecom/lgecrypto_module might not work, encryption safe, folder encryption, etc. might be broken (if applicable)
might not boot or bootloop microSD with exfat is cause of LOT of trouble => in doubt remove microSD before flashing custom Kernels or ROM mods to avoid having additional trouble-maker to troubleshoot
phone boot-"loops" several times => seems to be default bootloader behavior for LG V30 (and/or other LG phone)
phone boot-"loops" several times => might need a few times to "settle" to boot the ROM up
booting up takes long => might actually rebuild dalvik cache or do some filesystem checking
SIM PIN isn't request and WiFi is dead as well => several reboots might fix it;
SIM PIN isn't request and WiFi is dead as well => permission corruption might have occurred, (need root) try to fix via: https://stackoverflow.com/questions...acct-uid-10064-read-only-file-system-in-emula
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => "no OS" , Kernel might not actually be bootable , kernel issue, system partition issue
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => might have incompatible ramdisk, no-verity was not flashed
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => Kernel might be broken (totally not work or be compiled with non-compatible features)
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => OS/Android might be broken (filesystem corrupted, etc.)
Flashing rctd & no-verity/verity-disabler is only necessary for LG Stock-based ROMs !
Not necessary for AOSP, LineageOS, etc. !
prepare kernel for flashing : [up-to-date]
rename the zip-file to 7z (file size limit)
extract the 7z (needs 7z that support PPMd compression)
rename it into boot.img
suggested flash : [up-to-date]
Get into fastboot mode (turn off => connect cable end to phone => hold VOL down => connect PC end of cable)
fastboot flash boot boot.img
fastboot boot TWRP.img (keep USB cable connected ALL of the time)
flash rctd disabler
flash no-verity
(optional) flash Magisk
disconnect USB cable
(optional) wipe /cache
(optional) dalvik cache
reboot system
Help:
Forcing the device to reset usually is done via Power + VOL DOWN - keep both pressed for several seconds, then the screen should turn off
the device is set up to (re)boot again - so have the USB cable, a PC/phone [on the go] with fastboot ready to connect the cable immediately when it was off
.
If you plan on using the microSD more extensively and are on non-Stock (e.g. AOSP, LineageOS, dot os, etc.) - [backup your data !] then format the microSD to ext4 in TWRP, that should give you 2x the write performance of exfat and also somewhat faster read performance
As a bonus of using ext4 on the microSD - access to your files should be available when flashing/trying out the GSIs (Project Treble)
Kernel boot test (DEVs):
[Kernel testing or if you want to try] I usually do a fastboot boot boot.img first to see if the bootanimation is successful (boots into bootanimation [non-Stock] or it boots into the ROM itself with reduced functionality [Stock ROM])
After that I do a real flash of the kernel via fastboot flash boot boot.img
Quirks (V30* phones compared to others & bootloader/boot(loop) behavior):
After first flashing - the kernel might fail at 1st boot, then reboot device and properly boot into the ROM
with Magisk it can be more reboots (I counted at least 3-4).
.
.
If the bootlooping is much longer - force reset the device (Power + VOL DOWN), that should usually allow the device to recover after 1-3 (re)boots
.
If that still doesn't help - remove the microSD - until you've successfully booted the kernel up, the exfat driver is known to cause trouble and make things much less predictable and irritating
To make things more predictable (and exclusively using AOSP/LineageOS-based ROMs) - you can format the microSD to ext4, that might help a bit with the amount of (re)boots during flashing)
FIXME:
additional notes, warnings, guides, etc.
(theory) while the device seems to bootloop after flashing Magisk or other "bigger" modifications - occasionally press the volume down button while you see the LG V30 ThinQ logo (boot splash/image) to speed up booting (input = boosting = quicker everything ?)
Kernel Source:
android_kernel_lge_msm8998/branches
lunar-kernel_II_WIP5_boot-work [current "bleeding edge"]
other/older kernels are earlier states of latest bleeding edge branch
Kudos:
Linus Torvalds, Linux Kernel devs
Greg Kroah-Hartman our favorite upstream Kernel LTS maintainer <3
Google kernel & other Android devs
codeaurora, linaro & all other devs working on qualcomm goodies
LG kernel & other devs
nathanchance for his kernel, toolchain and other reference work
sonyxperiadev & devs
sultanxda
freak07
franciscofranco
andip71
frap129
GreyLeshy
SGCMarkus
the XDA , 4PDA and all other android communities
all other devs & folks to be mentioned
last edited:
28.06.2018, add attachment: specifically built kernel for ls998, US sprint V30 model (US firmware, US998)
28.06.2018, add attachment: uploaded II_EAS_I_stable , EAS kernel on early ported EAS state, should be pretty efficient, deemed stable material, read notes: at its announcement post
06.07.2018: updated text for bleeding-edge added link to it https://forum.xda-developers.com/showpost.php?p=76996622&postcount=88
12.07.2018: attached latest HMP kernel to OP (1st post), removed EAS kernels since those had a bug with frequency being stuck at max frequency
26.10.2018: removed older attached HMP kernels, newer ones are in posts below
#1
"old", barebones kernel with absolute minimum changes (from LG) will be here
#2
"stable", only minimum additional functionality & fixes will be here
if not mentioned otherwise these are ONLY for LG Stock-based ROMs (Boombox, A.I.S., Stock, debloated Stock, etc.)
Checksums (md5sum):
d0c4572563a389ec495f1c661332c185 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K.img
f29fc429d32de4fd79d3117642d39137 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
6307cd6d40e97404a3c66bf78d20437f boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D.img
f181f7589ecb3426006fa0d15c1e161d boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D_PPMd_7z.zip
f31791fcd8b57db7e3b91ba5e4755bf3 boot_H930_21A_oreo_I_6_WIP4_LG_stock.img
d77c0504c9119f2d86880dd74d8fc0cd boot_H930_21A_oreo_I_6_WIP4_LG_stock_PPMd_7z.zip
Source:
https://github.com/zachariasmaladro...mmits/oreo_I_6_WIP4_stock__H932__US998_spr_US
#3
"bleeding edge", current development branch & WIP (work-in-progress) drops
Stability troubleshooting:
disable zram
set lowest CPU frequency and max CPU frequency to default
lower GPU max frequency
...
change each setting separately and see if that improves stability then please report your results
oreo_I_6_WIP7_3_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP7_3_stock
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
91273b50c1126bf44e2fa9b7d3eb00bb boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K.img
859fa1eb9948f19821110da85d2d996a boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
e20bb8036273960e99316cb7bac57c78 boot_H930_21A_oreo_I_6_WIP7_3_stock.img
0a360f4dd4cedf6cf95ded2dbd78fa1d boot_H930_21A_oreo_I_6_WIP7_3_stock_PPMd_7z.zip
0b7fc9259836f9a79c2e1715ba7bd79a boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D.img
9c1d1f917f7cd9ba50c2464a2b8b4bb0 boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP8_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP8_stock
Changes:
faster initialization of kgsl/3d adreno graphics driver (quicker boot)
removed (for now): DTS Eagle - caused more noticeable humming/buzzing/whirring of sound at lower volume levels with aqstic (internal) DAC
timers: fix for lock contention and failing
CIFS/SMB: security fixes up-to-date [driver not used right now]
qcacld-3.0: updated WiFi driver & firmware to latest revision for Android 8.1
removed: LiveDisplay driver (only used in LineageOS; RR, etc. ?)
[eval] switched to 300Hz tickrate from 1000Hz tickrate which tends to be quite unstable on LG Stock ROMs
wcd934x: (internal DAC) a few fixes & improvements
removed/reverted: change that caused horizontal line of AOD display
several other changes
Click to expand...
Click to collapse
Known issues:
inverted color on AOD display [needs investigation] - e.g. red equals to turquoise for whatever reason
md5sum checksums:
8acd26556f1f6afe1659cff54fe61efc boot_H930_21A_oreo_I_6_WIP8_stock.img
32b8e679cdb8c066cdb945785334822c boot_H930_21A_oreo_I_6_WIP8_stock_PPMd_7z.zip
a29bda002d9c70f617180f3a955cb066 boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K.img
b06ddaba4f4c0124448b81ff78f479ba boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
3c46f82d1bb45e2fe3dfe5fc55f8b815 boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E.img
e7d42505842abcb08e3ec0c90c26924d boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP9_7_5_2_stock
Leaving this here for a bit (from the Telegram Group https://t.me/LGEV30 ):
New experimental/WIP kernel for Stock LG ROMs [regression fix, headset detection might stop working after a while]
internet max throughput should be 25-30% higher than before, ZZMoove governor is onboard along with other custom ones (cultivation, impulse, blu_active), MPTCP got updated, additional fixes & improvements to cut down latency & raise stability, ppp subsystem has been updated and enhanced (potentially fixing VPN connection issue), peripheral-loader, slimbus, glink subsystem updated; camera actuator updated - uses boost to make zooming smoother, several other subsystems updated, cpu_input_boost used - screen output smoothing/boosting, oom handling fixed/improved, HSWAP (swap + lmk + page_alloc LG in-house variant) disabled in favor of upstream lmk, binder fixes and improvements, regulator fixes & improvements, mempolicy got updated, eliminated a few battery drainers (idle drain should be lower)
H930/H930DS, 21A:
https://drive.google.com/open?id=1iyX8yY8QuX1ZJv8VcUn9CEpx4bOtaU98
US998, 20E:
https://drive.google.com/open?id=1ne06IAK4AJ7k22OYiD91yicjkp0nGtZ-
H932, 20K:
https://drive.google.com/open?id=1s6y8YSEdh5QXheqPrEaqdSiiYdc6QsO-
open towards suggestions on how to reduce battery consumption of WiFi usage further
Click to expand...
Click to collapse
Kernel source branch:
oreo_I_6_WIP9_7_stock__H932__US998_spr_US
Click to expand...
Click to collapse
Note:
Attached file is a 7zip (PPMd compression) renamed to zip due to filesize limitation
rename to .7z and extract - some archiver can handle the file without renaming ...
#4
due to attachment size limitations - the file was packed with 7z PPMd (max) compression, then renamed to .zip, so: rename to .7z and unpack
afterwards flash the boot.img either
via fastboot flash boot boot
via TWRP
oreo_I_6_WIP7_3 (almost identical to current LG Stock ROM kernel)
Branch:
pie_I_6_WIP7_3
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
0639cd649bd4d8aa27bf2db5ed065761 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018.img
3807e6991580b96ec796836c8c1f1bb7 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018_PPMd_7z.zip
9ecaafd28851c2471c4c4de0dbd8e6be boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018.img
f148bd763cbb606508ac332b45ef15a7 boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018_PPMd_7z.zip
d9ead2f72bd19d02d50a9bf12bb85a79 boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018.img
59aee22119d981b8aa91c1c846a5075e boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018_PPMd_7z.zip
2a60f4130b4005736fdba05981cff408 boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018.img
f7643c6f30c61755f7e066b4ff4d5fae boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018_PPMd_7z.zip
Click to expand...
Click to collapse
these 4 different Kernel releases are needed because the ramdisk/init content is fundamentally different preventing the phone/ROM from booting if it doesn't match
Dirty Unicorns 9.0-based Kernels (06.10.2018 build):
see attachment
Checksums (md5sum) :
be498bf45017a28d7ead8ccada514868 boot_pie_I_6_WIP3__DU_9.0__06.10.2018.img
30c34e1566fece2ac8721868fa89b88c boot_pie_I_6_WIP3__DU_9.0__06.10.2018_PPMd_7z.zip
a4425bb19177033622d402c3b6795a4d boot_pie_I_6_WIP4__DU_9.0__06.10.2018.img
f89adcd02831700eed629195639497c7 boot_pie_I_6_WIP4__DU_9.0__06.10.2018_PPMd_7z.zip
please also take a look at the "experimental" folder if there are newer ones there (currently: 26.10.2018 - there are none newer ones)
edit (01.09.2018):
removed the attached kernel since 3 different kernels, depending on ROM, are needed to avoid confusion
edit (26.10.2018):
added updated kernels for recent AOSiP, lineageOS 15.1, Resurrection Remix Oreo 6.1.0, dotOS 2.5 builds (all Android Oreo, 8.1)
Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?
XCaliburX said:
Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?
Click to expand...
Click to collapse
Not sure what you mean with "solely through clean rom flashes"
Just do a TWRP backup of each partition separately: /boot, /system, /data
then get into fastboot:
boot into bootloader (adb reboot bootloader)
turn phone OFF, connect USB cable to phone, hold volume down - connect other end to PC
First test-run to see if it boots for you:
Code:
fastboot boot boot.img
then
Code:
fastboot flash boot boot.img
after that boot into TWRP and flash Magisk.
I've had Magisk installed before and after each kernel flash you, of course, need to install Magisk again (Magisk Mods probably, too - that at least was the case I tried NanoMod/microG via Magisk).
tl;dr
bootloops or longer booting would/could still happen no matter ROM state - ideally you should be able to flash or fastboot boot the new kernel without issues
Magisk always needs to be re-installed after new kernel (boot.img) flash, same applies to Magisk modules
Thanks
Nvm.
Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk
XCaliburX said:
Nvm.
Click to expand...
Click to collapse
Thanks for your comment (before replacing it )
You ran into any issues ?
The stable kernel/branch is more suitable to gain battery savings since it has the phy-off change included that allows the phy power supply to be turned off during idle state and the scheduler change (the "old" one doesn't - it constitutes the absolute bare minimum).
The scheduler change effectively reduces battery consumption during usage by approx. by half (confirmed with e.g. music playback with PowerAMP).
The flashing is actually quite straight-forward, the notes in OP / first post matches with the previous (incomplete) understanding I had how the device behaves and needs to be amended once I further understand how to most efficiently
do all the steps ...
The device (or bootloader) seems it's set up that way to bootloop (when a broken kernel/boot.img is flashed) - returning to the warning screen that the bootloader is unlocked - and once the phone was turned off (via Power button), it'll immediately boot successfully via the existing kernel on the boot partition to the ROM.
So with the boot.img files I offer actually non of the bootlooping should happen (after flashing Magisk, it'll reboot once but should boot into ROM afterwards).
There are additional power savings possible e.g. sending the GPU off to nap once it's idle but that needs careful tuning to reduce lag/non-smoothness - which I currently don't have time to do,
also we're limited to using the enhanced HMP kernel for now - EAS is off limits, so that should prevent further power savings and enhanced smoothness with high efficiency.
guigui33 said:
Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk
Click to expand...
Click to collapse
I haven't tried doing that yet,
but if that possibility is there it most probably should work - please give it a try
Merci
No problem flashing .img via TWRP. flashed the "stable" Kernel 2h after OP posted the links. Running fine for now w/o problems. Smooth as butter und more battery friendly than stock
Great work i have to say.
Cheers
Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.
XCaliburX said:
Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.
Click to expand...
Click to collapse
Both "old" and "stable" kernels use the "stock" modified ramdisk from SGCMarkus which was working fine while flashing his debloated (Korean origin) Stock ROM,
it could be that the device nevertheless is reacting allergic to modifications/deviations from a kernel which is very close to stock.
Can't really tell what could be the reason for it to react up - HOWEVER nothing in "old" kernel looks suspicious to can cause that.
tl;dr:
no idea
in case of doubt use completely stock kernel
don't forget to use rctd-disabler & no-verity/forced-encrypt disabler
once you have a working base, go from there
As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks
MetaMaverick said:
As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks
Click to expand...
Click to collapse
That's an AT&T/Time Warner model, right ?
it uses a different mode of operation/has changes in ecryptfs
runs in FIPS mode
has an in-built VpnClient security module which supports an "interceptor" netfilter module
doesn't seem to have multi-path (MPTCP) vs. the global model (or at least kernel config)
it comes with an enhanced TrustZone/qseecom driver "to enable Periodic Kernel Monitoring driver for LG IMA" (PKM)
adds support for "ccaudit logging using additional fifth buffer" (which doesn nothing ?)
haven't seen the ramdisk yet (boot.img ?)
but I guess there might be interference as soon as the kernel strays too much from stock since qseecom/TZ is involved which pretty quickly can lead to a non-booting kernel on Stock ROM (had it happen on Z5).
There might very well be additional changes from the global (H930) model - I've only looked at the main files so far ...
I have flashed the bleeding version, and it seems to be hard to boot with and to make a battery drain.
I'm on the stock twrp rom.
I flash then the stable kernel, and lt's better, the boot is fast and it seems to have no battery drain.
In case of problem, can you join the stock kernel in the topic to be flashable as image or zip via twrp ?
Good work !
Envoyé de mon LG-H930 en utilisant Tapatalk
Using the stable on ls998 stock and boots nicely...no issues so far...hopefuly be able to squeeze a bit of extra battery life out with it...thank you and great work...on another note i flashed as an image through twrp without issues
Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.
TotallyAnxious said:
Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.
Click to expand...
Click to collapse
Thanks for the feedback,
nope though:
Linux version 4.4.78-perf+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #11 SMP PREEMPT Sat Mar 24 22:16:32 CET 2018
Click to expand...
Click to collapse
that one's from SGCMarkus.
Can you post more info how your system is set up ?
zacharias.maladroit said:
Thanks for the feedback,
nope though:
that one's from SGCMarkus
Click to expand...
Click to collapse
I'm having trouble figuring out a way to get a kernel log then. The phone reboots too soon for adb. Any ideas? Google has only shown me ways when the phone is working normally and reboots.
---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------
zacharias.maladroit said:
Can you post more info how your system is set up ?
Click to expand...
Click to collapse
Debloated from latest kdz Oreo. Magisk 16.4. I flash the img, flash magisk 16.4 then reboot. I've tried keeping wifi off (didn't change anything). I've tried with and without my personal magisk mod. All that's left is magisk mods like BusyBox and other utilities.