{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys,
let me present to you my Moto G Kernel. Its based upon the stock Moto G kernel source and was build for the stock ROM.
The main goal for this kernel is to improve battery life while keeping up a reasonable performance.
Features;
Added my own hotplug-driver (disabled mpdecision)
Improved and updated interactive governor with touchboost
Simple ondemand GPU governor
Vibrator control with additions from me
Real Voltage Control
It just works and is stable (on all devices for stock ROM)
Many small improvements e.g. updated subsystems and fixed memory leaks
I tried to keep this kernel as clean as possible with useful features. Always make a backup before installing and if you are coming from
a different kernel keep in mind that you'll need to reflash the stock modules (if changed). This kernel should work for all stock roms (dual sim as well as GPE).
How-To-Install;
be sure to make a backup first
via fastboot; fastboot flash boot /path/to/boot.img or fastboot boot /path/to/boot.img (if you just want to try it without flashing)
via zip; install zip in your favorite recovery
Keep in mind that /system/lib/hw/power.msm8226.so should be renamed or deleted if flashed via fastboot (zip does it automatically).
Download
Changelog
Looking for the CM-Kernel? Head over to this thread!
If you want to tweak it, you can also do with my own app.
If you like this work and want to donate something;
Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]
Click to expand...
Click to collapse
Enjoy!
How-To-Build:
Go to my Github (kernel as well as ramdisk source are available).
Code:
git clone https://github.com/Blechd0se/kernel-moto-g.git
cd kernel-moto-g
git checkout kitkat-mr2-release-falcon
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.7/bin/arm-eabi-
export ARCH=arm
make msm8226_defconfig
make -j64
I use googles default 4.7 toolchain as well as 64 jobs, you might change this value depending on your system.
Once build, you'll need to repack the ramdisk.
For repacking the boot.img i use the following;
Code:
mkbootimg --pagesize 2048 --base 0x10000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' --kernel kernel-moto-g/arch/arm/boot/zImage-dtb --ramdisk kernel-moto-g/ramdisk/ramdisk.cpio.gz -o /output/boot.img
How does the hotplug driver work here?
My hotplug driver is based upon @franciscofranco idea to keep minimum two cores online while the screen is on.
In addition to this there are load counters on both of those cpus. If they reach a certain threshold another core gets onlined.
So cpu0 is bound to cpu2 and cpu1 is bound to cpu3 in terms of onlining. If onlined, cpus stay a certain amount of time
online before they consider to eventually go down again. Since hotplugging is kind of an intensive and expensive operation and threads
might be migrated my algorithm always offlines the lowest load core.
If screen is off, there is only one core online.
Here is a quick overview about the hotplug driver tunables;
all_cpus_threshold:
The threshold for the average load of all currently onlined cpus to online the next core. If you lower this value, cores can get more easily online.
hotplug_sampling:
The sampling rate of the hotplug driver. Lower this value and decisions will be made quicker in regards if a core should be onlined or not.
min_online_time:
To prevent core off-/onlining when they are near the threshold. This is the minimum online time for a core.
single_core_threshold:
The threshold for a single core to online another one. For example; if core 1 is at 100% and the average load is above 60% core 3 will get online.
low_latency:
If enabled (1) it let's the hotplug driver react really quickly to short load spikes (100% CPU load) and onlines cpus accordingly.
up_frequency:
The minimum cpu frequency to start hotplug operations. If the current frequency is below this value, no hotplug operations will perform.
Default is the maximum frequency.
battery_saver:
If enabled (1), only one core will stay active as soon as you turn off your screen. If you are getting strange audio quality while the screen is off, try
switching it off via 0. This will let both core stay active during suspend.
Click to expand...
Click to collapse
.
Why do i have to rename/delete this lib?
Because it interferes with my changes to the interactive governor. You can keep it, but it might produce very strange issue. You can just
rename the file if you want to restore it later.
Can i tweak this kernel or do i have to?
Of course you can. You can use any of your favorite kernel tweaker app. I have also made one if you might want to use it, here is the
play store link.
You don't have to tweak it. It ships with well tested values and is already preconfigured.
As always, just enjoy your device.
How can i control the vibrator strength?
This option is not yet available in my kernel app. The actual sys path is; /sys/devices/virtual/timed_output/vibrator/vtg_level
The default value should be 18, the maximum is 31 and the my lowered minimum is 10.
e.g. echo 10 > /sys/devices/virtual/timed_output/vibrator/vtg_level
Coming from a different kernel?
If you come from a different kernel its likely that your modules are overridden. This kernel uses stock modules. You can
use this flashable zip by @justjr to restore your modules.
How to use color control?
Use the following in your terminal; echo 255 230 210 > /sys/devices/platform/kcal_ctrl.0/kcal
First value are reds, second value are greens and last value are blues.
Turn your display off -> on and profit
Very nice! Competition is always welcomed. I'll follow this development. Seems promising so far.
Good to see a second kernel for stock rom.
The vibrator control alone is making me want to switch.
Oh man!, great, it's awesome to have you here developing for Moto G, I'm gonna test your kernel right away, I have a question though, I'm coming from faux kernel, what would be the safe procedure then? You recommend me to re flash the stock images of kernel and system or just install your kernel via recovery it's enough?
[*]Vibrator control with additions from me
Does this mean that we're able to adjust the vibration intensity? If so you're my hero
Nice to see another stock rom kernel xda! I will have an eye to this topic and your development...
Bye Flamey
Gesendet von meinem XT1032 mit Tapatalk
Bleak3993 said:
Oh man!, great, it's awesome to have you here developing for Moto G, I'm gonna test your kernel right away, I have a question though, I'm coming from faux kernel, what would be the safe procedure then? You recommend me to re flash the stock images of kernel and system or just install your kernel via recovery it's enough?
Click to expand...
Click to collapse
I just did this. Hope you did a nandroid backup so you can restore boot and system. Then install this this kernel.
Sent from my XT1034 using Tapatalk
guapinoy said:
I just did this. Hope you did a nandroid backup so you can restore boot and system. Then install this this kernel.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I have a backup of stock boot and system already, so, is there any problems of installing over faux kernel?
Bleak3993 said:
I have a backup of stock boot and system already, so, is there any problems of installing over faux kernel?
Click to expand...
Click to collapse
Should be no problems.
Sent from my XT1034 using Tapatalk
Sorry for the question but will this kernel work on GPE Moto G or just the stock from Motorola?
how the heck did you do 64 jobs??? that should of totally blown up your computer and only one i know of that could take that is cyanfox's server. over at drdevs we max out at 32 for one person thats crazy abuse of your computer.
Well, I had to use the backup to recover the wifi modules, then I installed the kernel, and now is everything working perfect. Now, can I configure the vibration vibrator control?
Edit: will there be an OC version?
Hey! Welcome to the club.
I would really like to know
1) which model does it supports (i have xt1033, quarx should be having tge same)
2) which rom does it supports (stock ot aosp)
Very good blech, nice to see you developing for the Moto G.
Would like to try the kernel, but unsure wich .imgs I should flash to get stock kernel and wifi modules back, coming from faux, as nobody has provided any wifi modules files yet (not in faux kernel thread). I don't have a backup with stock stuff, my bkps also have faux modules on it.
abhifx said:
Hey! Welcome to the club.
I would really like to know
2) which rom does it supports (stock ot aosp)
Click to expand...
Click to collapse
Stock
cool
Thank you for this kernel, does not have choice for the stock, now have a choice, the other custom kernel for stock having problems autonomy at the moment, so I'll test it
And not pay to be able to control the kernel is really appreciable, thank you
So... I know it kinda has been answered already, but can anybody give a step by step guide how to flash this most effectively over faux kernel?
Do I just have to flash stock modules and kernel via mfastboot before fishing the zip file for this kernel via TWRP?
Where can I find those files?
I am on stock German version btw...
Gesendet von meinem XT1032 mit Tapatalk
confirmed not working on dual sim XT1033.
have to wait for a kernel which works on stock XT1033
Bleak3993 said:
Well, I had to use the backup to recover the wifi modules, then I installed the kernel, and now is everything working perfect. Now, can I configure the vibration vibrator control?
Edit: will there be an OC version?
Click to expand...
Click to collapse
The sys path is; /sys/devices/virtual/timed_output/vibrator/vtg_level
Default value should be 18, the maximum is 31 and my lowered minimum is 10. I'll add this later to the startpost
About OC; not sure yet, i dont feel its necessary, have to experiment with it.
Cameron581 said:
how the heck did you do 64 jobs??? that should of totally blown up your computer and only one i know of that could take that is cyanfox's server. over at drdevs we max out at 32 for one person thats crazy abuse of your computer.
Click to expand...
Click to collapse
I always use -j64, linux can handle it pretty nicely. It wont slow down the whole system, SSDs help a lot
abhifx said:
confirmed not working on dual sim XT1033.
have to wait for a kernel which works on stock XT1033
Click to expand...
Click to collapse
Could you explain this a little bit more? As far as i know kernel is the same for all devices. The only difference could be in ramdisk which is easily fixable.
Are you using motos stock rom?
Gesendet von meinem Nexus 7 mit Tapatalk
Related
Hi all again!
I've created this thread in order to add fixes and add-ons for Nova v8 ROM.
* Wrong OC Fix:
- This fix restores default freq/volt config in order to restore a blocked system from a exagerated OC/UV.
- Download it form title, flash it at CWM and that's all.
* Huexxx's Nova v8 Mod v1.4:
- This mod modifies nova script in order to:
· Make the navigation inside the script a little bit faster
· Directly view the currently active preset from presets submenu
· Simplifies the custom preset submenu. Now you only have to set the 4 frequencies
· Simplifies too the preset and simple overclock. Now voltages are auto established. (v1.1)
· Adds the possibility to enable/disable AUV (AutoUnderVolt) script on boot
· Adds the possibility to set the Auto UV Depth to control the voltage drop on boot (v1.3)
· Now you can view auvlog instead to run UV once (v1.4)
· Directly view the currently active freq/volt config from overclock submenu. It shows freq(vsel/calib) for each state. (v1.3)
· Directly view the currently active governor from governor set submenu
· Directly view the currently active I/O scheduler from scheduler set submenu
· Optimize a little bit the general aspect- Adds AUV script:
· Avoid to undervolt the max frequency if it's greater than 1GHz (v1.1)
· Take the lower voltage values from calibrating-recalibrating process to ensure the best UV (v1.2)
· AUV script uses the specified auto UV depth. Setting it to 0 the script ensures that the calibrated voltages are the minimum recommended by smartreflex system without do any undervolting on it (v1.3)
· Optimized timmings to ensure the calibration values are correctly stablished (v1.4)- Modifies /system/etc/init.d/11nov script to support AUV feature
- If you are using AUV you can see the log at /data/nova/auto/auvlog or within nova script's overclock submenu (v1.4)
- Adds /sdcard/nova/ocfix.zip to flash it if OC goes wrong and get a bootstuck
- Automatically disables SBT on installation (v1.1)
- I recommend to keep disabled SBT (Standby battery tweak) if you're going to use UV or AUV features.
- Feel free to use this mod altough you are not planning to use UV or AUV.
- Download it form title, flash it at CWM and that's all.
* Stock Nova v8 Restorer:
- This package restores default nova scripts and deletes all the extra stuff added by my mod.
- Updated to ensure all is restored with mod v1.3 or later version.
- Download it form title, flash it at CWM and that's all.
* Superuser downgrader:
- This package downgrades Superuser to latest stable 2.3.6.3 version.
- Download it form title, flash it at CWM and that's all.
* Nova v8 Kernel Source Code:
- Nothing to comment, it speaks by itself.
- Thanks to knzo.
Regards!
UV Testing:
* 6 serial Quadrant Standard with Power Tutor Monitoring
I've tested the battery consumption with and without UV in order to see the differences.
The test consists in a 6 serial Quadrant run and 3 times repeated for each configuration.
The common parameters are: 900, 700, 500, 300, InteractiveX, sio, wifi enabled, data connection enabled, wcdma only. In all cases I've rebooted and waited until governor had been settled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking at the results, the power consumption with AUV activated is lower than the stock situation. LCD and WiFi consumptions are linked to parameters that aren't related to the MPU voltaje; then the interesting results are the power drained by the CPU. Also, the absolute mean quadrant scores shows that there isn't a descent on performance, or better said, the descent on performance is negligible taking into account the fluctuation in quadrant scores.
* Battery lasting with light use
Parameters are: auto UV on boot enabled, 900, 700, 500, 300, InteractiveX, sio, wifi disabled, data connection disabled, gsm 2g only. The use consists on: two or three vioce calls per day, some sms, some photos, some visits to the gallery, the alarm every morning, radio allways on.
Regards.
Thanks, I will download it later
Sent from my LG-P970 using Tapatalk
Hi!
I've added some new stuff to first post!
knzo, feel free to grabs whatever you deem appropriate for your releases.
To say that I'm using UV on boot from two days ago and everything run fine.
Regards!
Hi there I just want to know what do I get basically if I use this mod? haha please answer me as simple as you can bud not that good with this stuff . TIA bud
awesome work!!
Huexxx said:
knzo, feel free to grabs whatever you deem appropriate for your releases.
Click to expand...
Click to collapse
Thanks but no need.
I will completely redo the script for next version.
knzo said:
Thanks but no need.
I will completely redo the script for next version.
Click to expand...
Click to collapse
I hoped this answer!
denclaud said:
Hi there I just want to know what do I get basically if I use this mod? haha please answer me as simple as you can bud not that good with this stuff . TIA bud
Click to expand...
Click to collapse
Basically you get:
- A little bit modified nova script. Little bit faster, with certain things simplified, but fully operational.
- The possibility to try my UV and AUV scripts (If you want...)
- The possibility to restore default OC if things go wrong flashing /sdcard/nova/ocfix.zip
Thats all at the moment.
how make this?
can u explain for me how i put fix mod
jamespvz said:
can u explain for me how i put fix mod
Click to expand...
Click to collapse
Do you have Nova v8 installed?
If positive answer... install this stuff the same way you installed Nova v8... from recovery... install zip from sdcard... select the zip and flash it!
Regards!
Question,
Huexxx, do you have kernel source of Quasar v8?
redy2006 said:
Question,
Huexxx, do you have kernel source of Quasar v8?
Click to expand...
Click to collapse
I just saw your PM while I was about to reply to you here.
Yes, I'll upload it. Give me 30m.
knzo said:
I just saw your PM while I was about to reply to you here.
Yes, I'll upload it. Give me 30m.
Click to expand...
Click to collapse
Thanks. Few days ago when I asked it, I was forgot to PM you... because lots of reading post on XDA forum
Thanks again
http://www.multiupload.com/Z40ZNZAUVI
This FIX/MOD solves the problem with the SU? Today, probably, the 25-th time returned with Nova-8 on Nova-4.5, because on a level place hung Dolphin browser. Just once in a run SU-application.
PaulBort said:
This FIX/MOD solves the problem with the SU? Today, probably, the 25-th time returned with Nova-8 on Nova-4.5, because on a level place hung Dolphin browser. Just once in a run SU-application.
Click to expand...
Click to collapse
No........
PaulBort said:
This FIX/MOD solves the problem with the SU? Today, probably, the 25-th time returned with Nova-8 on Nova-4.5, because on a level place hung Dolphin browser. Just once in a run SU-application.
Click to expand...
Click to collapse
If still having problem with SU, then it's better to downgrade SU, because Nova v8 including SU beta version, so perhaps you can use the stable version. Can you apply that, PaulBort?
PaulBort said:
This FIX/MOD solves the problem with the SU? Today, probably, the 25-th time returned with Nova-8 on Nova-4.5, because on a level place hung Dolphin browser. Just once in a run SU-application.
Click to expand...
Click to collapse
Look at first post.
I've repacked the latest stable version of Superuser.
Try it and comment.
Huexxx said:
Look at first post.
I've repacked the latest stable version of Superuser.
Try it and comment.
Click to expand...
Click to collapse
It's not help.
Sometimes bugs present.
For me nova 4.5 last stability version.
Hello everybody,
Based on the kernel from DooMLoRD and FXP and wanting to make a more clean kernel in relations to Stock Kernel and add some personal changes, I make my own kernel that I am posting below.
He is based on 4.0.2.A.0.61_62 source kernel, and adding the follow changes:
v1.0:
New Governor Option:
SmartAssV2
Smartass
Smoothass
BrazilianWax
Interactive
Savaged-Zen
Scary
I/O Schedulers:
Noop (default)
Anticipatory
Deadline
CFQ
Overclock option to 1.9 Ghz
Enabled SWAP support
Enable some file systems:
EXT2
EXT3
EXT4
NTFS (Read & Write)
CIFS
DoomKernel Ramdisk:
With autorooting (prerooted)
init.d scripts/binaries execution support
support /sd-ext backup/restore
modCWM-v04 TouchEdition Recovery
and other (see http://forum.xda-developers.com/showthread.php?t=1172885 for full changelog of DoomKernel Ramdisk)
Default Sony Xperia boot logo.
v1.1:
Have the same features that v1.0, only bug fix on compiler configuration.
v1.2:
Improve battery life
Change Sony source code base, now base on 4.0.2.A.0.61_62 source
v1.3:
Great improve of battery life by disable NETWORK_FILESYSTEMS (CIFS and NFS)
v1.4:
Enable CPU undervolting options (the kernel frequencies is not undervolted, but you can undervolt (recommend using IncrediControl)
WiFi undervolting
v1.5:
Disable duplicate voltage scaling frequency, for better manager of cpu frequency and better battery life.
From FreeXperia: salvage some more ram by removing unused pmem_adsp_cache
From FreeXperia: salvage some more ram by removing unused pmem_audio
Disable verbose procfs contents
Adding scripts for better battery life and overall performance:
Internet speed tweaks
Misc kernel tweaks
Battery tweaks
Journali smoff
Defrag DB
Loopy smoothness
Sick
Zipalign
Zipalign Defrag DB
Change sched_latency_ns to 600000
Change sched_wakeup_granularity_ns 400000
v1.6:
WiFi Power Management Tweak
Increase CPU voltage of some frequency for better stability
CPF Frequency Tweaks and Enable CPU AVS (Adaptive Voltage Scaling)
Revert: change sched_latency_ns to 600000
Revert: change sched_wakeup_granularity_ns 400000
Enable EXT3 and EXT4 Posix ACL and XATTR
Disable YAFFS ECC Check
Enable YAFFS empty lost and found folder at mount
Disable YAFFS block refreshing
Change pll2_fixup onverclock control
New compiled WiFi modules
WiFi modules included in Ramdisk
In general this version is for improve the battery life and resolve the problems of WiFi don't work because of user using not default WiFi modules (DoomKernel Modules)
Ps. For user with WiFi don't work just restart twice.
v1.7:
Enable 1200Mhz frequency
Add IO SCHEDULE BFQ
Add CM torch interface (base on Blendkernel v02 from Jason Stain)
Use disable_irq_nosync() from within irq handlers (base on Blendkernel v02 from Jason Stain)
Prepare I/O context code for BFQ
Custom tweaks in kernel config
v1.8:
Revert change in acceleration sensor support. Fix acceleration sensor error.
v1.9:
Upgrade busybox to fix the execution of user script (init.d).
Remove some scripts that were causing problems.
The instalation is the same from other kernel:
Code:
fastboot flash boot boot.img
PS.: for CPU undervolting I recomend using IncrediControl (https://market.android.com/details?id=com.incredicontrol)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to warn that THIS IS A TEST KERNEL, so he may have some bug.
By
Adriano Martins
-----------------------
Source at https://github.com/AdrianoMartins
I'm testing... thanks.
Just flashed it! I will report soon! Thanks for sharing!
Subscribed....
Sent from my LT15i
kindly tell me what do u mean by a
less "invasive" kernel in relations to Stock Kernel
Click to expand...
Click to collapse
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
DooMLoRD said:
kindly tell me what do u mean by a
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
Click to expand...
Click to collapse
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
DooMLoRD,
DooMLoRD said:
kindly tell me what do u mean by a
Click to expand...
Click to collapse
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
DooMLoRD said:
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
Click to expand...
Click to collapse
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
DooMLoRD said:
try get some more features to Xperia 2011 device kernels...
Click to expand...
Click to collapse
I don't want new features, that is the point....
DooMLoRD said:
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
Click to expand...
Click to collapse
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the feedback.
I don't have this problem but, I'll see what can be.
iridaki said:
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
Click to expand...
Click to collapse
Iris u have known me since X10 days... so thanks for ur post...
adrianom said:
DooMLoRD,
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
I don't want new features, that is the point....
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
Click to expand...
Click to collapse
very interesting point of view...
this is not the first time such a thing is happening and may be i am a bit edgy today... anyways...
FYI, kindly read
12. Using the work of others.
Click to expand...
Click to collapse
REF: http://forum.xda-developers.com/announcement.php?f=965
regards,
DooMLoRD
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
adrianom said:
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
Click to expand...
Click to collapse
That was fast! I'll update this post with my findings!
Thanks!
iridaki said:
That was fast! I'll update this post with my findings!
Thanks!
Click to expand...
Click to collapse
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
adrianom said:
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
Click to expand...
Click to collapse
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
I think version 1.1 was the same problem that version 1.0.
I was led to understand that was not happening because of what I think is a bug in BetterBatteryStats. It change the name of the wifi wakelock to deleted_wake_locks when wifi is disable. I'll keep looking, now for the wifi problem.
Thanks.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
+1
I'll test your kernel for a few days and give a feedback.
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
superlimau said:
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
Click to expand...
Click to collapse
Just bear in mind that when you wipe batterystats, you might notice battery percentage decreasing faster at first or inconsistently, so test the kernel for at least 2 battery cycles.
iR¡[email protected]!* via Tapatalk
Doing so now.
Sent from my LT15i
Made test with 1.0. I think battery drain here too.
my settings that i only changed is:
122Mhz - 1.4Ghz
smartass v2
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
tRippinthehead said:
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
Click to expand...
Click to collapse
It's Fast Dormancy, a network feature. Does your provider support it?
iR¡[email protected]!* via Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12
Reserved
Reserved
Last one.
Great job! Amazing to see a dedicated thread for this beauty.
Will report the experience
V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .
will test on omni,thanks
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.
Awesome
Sent from my GT-I9300 using Tapatalk
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?
Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
This kernel is made based on @bauner's CM 12.1 NightOwl ROM, LineageOS 13 with a few changes,. Originally based on my preference in what features I want added, I thought the rest of the Note 1 users might benefit from a bit more variety on his projects.
Just flash the kernel and you're done, make sure you're on the latest ROMs by bauner. As always, I'm not responsible if you brick your device due to some freak accident.
What's new:
V3
Merged kernel patches from bauner's commits
Redo some optimisation flags
V2
Did some optimisations
Tweak Interactive codes
Fix possible memory leaks
Please refer to my commits for more detailed info
V1.5
Set Westwood as TCP default
V1
Set Interactive as the default governor
Undervolt by 50mV
13-step CPU frequency
Download links:
CM 12.1
LineageOS 13
I did not test LineageOS 13, so please have a copy of the original NightOwl kernel on standby before flashing.
Credits:
bauner for his amazing work with the Note 1
Christopher83 for those toolchains
GeeckoDev for the War Kernel r3 sources
XDA:DevDB Information
Manjuu Kernel for CM 12.1 / LineageOS 13, Kernel for the Samsung Galaxy Note GT-N7000
Contributors
AutumQueen92
Source Code: https://github.com/AngryManjuu/android_kernel_samsung_tw_n7000/tree/cm-12.1
Kernel Special Features: Compiled with GCC toolchain optimised for our CPU (ARMv7 Cortex-A9)
Version Information
Status: Stable
Current Stable Version: V3
Stable Release Date: 2017-03-17
Created 2017-02-15
Last Updated 2017-03-21
Some kernel tweaks you might like:
Download Kernel Adiutor Mod since it's easier for this.
Set governor as Interactive and in CPU Governor Tunables, add according to this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The target loads do not need to make a new line, one spacing for each of them is the way it is written.
For example, write it as: 95 200000:60 300000:33 and so on.
For better multitasking:
I'm getting lags on MM, too. Might just "upgrade" back to LP and give your kennel a try...
may i ask where the download link is ?
dreamteam said:
may i ask where the download link is ?
Click to expand...
Click to collapse
At the top, there is a tab for downloads.
AutumQueen92 said:
At the top, there is a tab for downloads.
Click to expand...
Click to collapse
???
Must be blind...
temporarium said:
???
Must be blind...
Click to expand...
Click to collapse
You can see it in the attached image
bauner said:
You can see it in the attached image
Click to expand...
Click to collapse
So I can't download it using the XDA Labs app? Ok. Will use a browser....
Could you add some more CPU Governor in the future releases?
surVfate said:
Could you add some more CPU Governor in the future releases?
Click to expand...
Click to collapse
It depends. What governor, where is the commit for it, what makes it so special.
Updated to V2, refer to my commits for detailed changed/additions
AutumQueen92 said:
Updated to V2, refer to my commits for detailed changed/additions
Click to expand...
Click to collapse
Hi AutumQueen92,
I would like to ask you a few questions, if you don't mind...
- Have you tried a Forest-LP kernel ?
- If „Yes“, what is the difference between those two... ?
- Is your kernel overclocked ?
- What is your experience between those three kernels when you compare them (Bauner's, Forest-LP and your own) ?
- Don't be too polite and then not to write about your kernel too... [emoji2]
Thanks in advance.
Cheers ! [emoji481] [emoji481]
Sent from my GT-N7000 using XDA-Developers Legacy app
Oh my, double posting is amazing
Boombastical said:
Hi AutumQueen92,
I would like to ask you a few questions, if you don't mind...
- Have you tried a Forest-LP kernel ?
- If „Yes“, what is the difference between those two... ?
- Is your kernel overclocked ?
- What is your experience between those three kernels (Bauner's, Forest-LP and your own) ?
- Don't be too polite and then not to write about your kernel too... [emoji2]
Thanks in advance.
Cheers ! [emoji481] [emoji481]
Sent from my GT-N7000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
1. Yeah I've tried it.
2. If you mean this kernel and his, we both used different toolchains (compilers). I'm not sure what UberTC does but the one I used is made to optimise the Note's CPU itself so it works better. But then Forest's kernel has some kind of overclocked display panel, I'm not sure what that is. It's been a long time since I used his kernel so mine is more updated since it's based on Bauner's.
3. Nope, I don't want overclock. Apps these days are made for quad-core CPUs, so overclock will do nothing except hurt your hardware.
4. I haven't been using Forest's kernel very long, I preferred War kernel or Bauner's stock kernel better. By combining those two to make mine, I feel that it's faster now although I want to do a longer usage without rebooting. Lately I've been rebooting a lot to stabilise the kernel and make some fixes, but the first usage is already showing good results. I'm trying to implement my custom tweaks, if I can't embed it into the kernel I'll post a small section for it in next month's update. Right now battery usage is about the same but better performance.
5. ??? You mean I should post a more detailed explanation about the kernel?
AutumQueen92 said:
1. Yeah I've tried it.
2. If you mean this kernel and his, we both used different toolchains (compilers). I'm not sure what UberTC does but the one I used is made to optimise the Note's CPU itself so it works better. But then Forest's kernel has some kind of overclocked display panel, I'm not sure what that is. It's been a long time since I used his kernel so mine is more updated since it's based on Bauner's.
3. Nope, I don't want overclock. Apps these days are made for quad-core CPUs, so overclock will do nothing except hurt your hardware.
4. I haven't been using Forest's kernel very long, I preferred War kernel or Bauner's stock kernel better. By combining those two to make mine, I feel that it's faster now although I want to do a longer usage without rebooting. Lately I've been rebooting a lot to stabilise the kernel and make some fixes, but the first usage is already showing good results. I'm trying to implement my custom tweaks, if I can't embed it into the kernel I'll post a small section for it in next month's update. Right now battery usage is about the same but better performance.
5. ??? You mean I should post a more detailed explanation about the kernel?
Click to expand...
Click to collapse
No, thanks !
Everything is clear now !
I already have downloaded your kernel last week and I'm gonna flash it now, cause I'm already few months using Forest-LP OC kernel and it is very stable kernel ... With no „reboots“ at all...
I'll report my experience after few weeks with your kernel...
Thanks again for explaining your work. [emoji106]
Sent from my GT-N7000 using XDA-Developers Legacy app
Boombastical said:
No, thanks !
Everything is clear now !
I already have downloaded your kernel last week and I'm gonna flash it now, cause I'm already few months using Forest-LP OC kernel and it is very stable kernel ... With no „reboots“ at all...
I'll report my experience after few weeks with your kernel...
Thanks again for explaining your work. [emoji106]
Sent from my GT-N7000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
After less than a day of using your kernel I'm amazed with working of it, but I use „performance“ governor and it works great. How difficult for you is to OC this one to 1,6 GHz ?
Sent from my GT-N7000 using XDA-Developers Legacy app
Boombastical said:
After less than a day of using your kernel I'm amazed with working of it, but I use „performance“ governor and it works great. How difficult for you is to OC this one to 1,6 GHz ?
Sent from my GT-N7000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
That's very hard to believe because performance governor just clocks your CPU at max frequency the entire time. Also very impossible, I don't want OC on the Note 1. If you want it so badly you can try building your own kernel and adding it.
Boombastical said:
After less than a day of using your kernel I'm amazed with working of it, but I use „performance“ governor and it works great. How difficult for you is to OC this one to 1,6 GHz ?
Sent from my GT-N7000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The performance governor is not a good idea.
As @AutumQueen92 said it will run the cpu at the highest clock all the time.
After a very short time it will reach the thermal throttling temperature and then it will constantly switch between 800 and 1400Mhz
You can see it with this app
https://play.google.com/store/apps/details?id=com.yanyan.cputemp
Using V1 right now and it is very stable, should I flash the V2? Also one more thing is it possible to tweak the minimum brightness value to 1 without changing the source value and rebuild the whole kernel afterward? Thanks!
bauner said:
The performance governor is not a good idea.
As @AutumQueen92 said it will run the cpu at the highest clock all the time.
After a very short time it will reach the thermal throttling temperature and then it will constantly switch between 800 and 1400Mhz
You can see it with this app
https://play.google.com/store/apps/details?id=com.yanyan.cputemp
Click to expand...
Click to collapse
I know that thermal throttling is something what can be a problem but I have monitoring app which show me all the time what is a current temperature of processor and untill now I have no problem at all except that battery life is half of what it should be normaly...
Actually, when I wrote last post I was on „Ineractive“ governor and now I use „Performance“ governor and „cfq“ scheduler with 256 kb „read ahead“ value on the internal memory and also on the SD card. So I'll update you how far I will be satisfied with this combo. In the next few weeks I also will flash new from the scratch again your LP rom and again test it with your kernel and then again with Forest LP kernel and then at least with this one kernel...
Sent from my GT-N7000 using XDA-Developers Legacy app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OnePlus 8 Pro / OnePlus 8
Concept
Flash and be happy out of the box!
The kernel provides 4 Spectrum profiles and 3 Franco Kernel Manager profiles for most usecases. Balanced / Battery / Performance (default) / Gaming. For choosing another profile as Balanced please install Spectrum from the Google PlayStore.
If you want to modify the profiles just run a kernelmanager like EX Kernelmanager and change what you want.
The Android 10 version comes with autoinstalling Magisk module and autoinstalling config app made by Senior member xXx and Senior member tanisch2k09!
To preconfigure the kernel uses a config file made by well known Senior member @xXx
Many thx to both for this oustanding contribution to this project!!!
The Android 10 version supports Magisk 20.3 or higher only!
These are the tunables you could modify:
Defaults in [ ]
Profiles battery, balanced, [performance], gaming
SELinux [permissive] / enforced
CPU minimum frequency little 300, 403, 518, 614, [691], 787, 883, 1075
CPU minimum frequency big [710], 825, 940, 1056, 1171
CPU minimum frequency prime [844], 960, 1075, 1190
GPU minimum frequency 200, [305], 400
GPU Input boost off 305, [400], 441
GPU maximum frequency up to 900 MHz (comes with 600 MHz frequency set!)
etc.
!!! WARNING !!! 700, 800and 900 MHz are GPU OC frequencies and NOT stable on all devices!
The SmurfKernel configuration file is placed in /sdcard/SmurfKernel: If you want to use the kernel with it's default configuration just flash it!!! For custom changes please edit the SmurfKernelConfigurationEditor by @tanish2k09. The settings are applied saving the config. Your actual configuration is written to smurf.kernel.bootlog.
It's recommended to use my kernel paired with
xXx NoLimits thread
Telegram channel
Features
OOS and CUSTOM ROM support
UNIFIED
GPU OC up to 900 MHz
GPU Input boost (305 / 400/ 441MHz)
GPU / CPU sleep frequency setting
Refresh rate setting 60 / Auto / 90/120
CPU minimum 300-1075 MHz silver cluster
CPU minimum 710-1171 MHz gold cluster
CPU minimum 844-1190 MHz prime core
Power efficient workqueue setting
Scheduler tunables presets
Adrenoboost
Klapse Livedisplay 5.0 by @tanish2k09
Stune boost
Devfreq boost
Devfreq boost DDR
Devfreq boost GPU
Input stune boost extender
Load based boosting mode
ZSWAP / VBSWAP
Ultra / High / Medium / Low boost presets
Multiqueue io-scheduler: none, mq-dealine, kyber
Dynamic fsync
Advanced color control (RGB, hue, saturation, contrast)
Wakelock blocker
Wireguard
Wake Gestures
USB fastcharge
Vibration control
Spectrum and FK profiles support
Information about Klapse Livedisplay
Installation
Just flash!
Reboot to TWRP and flash kernel only, if you're already on SmurfKernel.
You can use exkm, fkm to flash it too. For first install USE TWRP and read below!
You can flash the kernel using TWRP
If you need to flash Magisk, flash it before flashing the kernel.
Coming from stock kernel, or any other kernel it is recommended to flash kernel, magisk, kernel.
If you encounter a ramdisk update error please reflash TWRP, magisk, reboot TWRP and flash magisk, kernel.
Download
GoogleDrive folder
MEGA folder
Bootanimations
Flash as Magisk module
Bootanimation 1
View attachment 4780411
Bootanimation 2
View attachment 4780412
Bootanimation 3
Bootanimation 4
All credits for these awesome bootanimations go to @JJay666, Pas and @Duncan1982
Contributors
Pappschlumpf
Source
https://github.com/pappschlumpf/SmurfKernelOP8
Many many many thx to all users that made buying this device possible with their donations. An awesome community !!!
Credits
@DespairFactor for his great base
@nathanchance for this great reference
@flar2
@tbalden
@ZeroInfinity for great pwrutilx governor
Joe Maples for electroutil
Team Helix for the great helix_schedutil governor
@difr for SimpleSpectrum
@frap129 for original Spectrum
@Tkkg1994 for always being so helpful
@DroidShift79 for the outstanding logo picture!
and all other great kernel devs on xda
XDA:DevDB Information
[KERNEL][GPU OC][OOS] SmurfKernel 1.1.0, Kernel for the OnePlus 8 Pro
Contributors
pappschlumpf
Kernel Special Features: GPU OC
Version Information
Status: Stable
Current Stable Version: 1.1.0
Stable Release Date: 2020-08-12
Created 2020-08-09
Last Updated 2020-08-12
Ready to flash with franco kernel manager and exkm?
Thanks.
golf60 said:
Ready to flash with franco kernel manager and exkm?
Thanks.
Click to expand...
Click to collapse
For first install use TWRP and flash kernel, Magisk and kerrnel again. I extended the OPs installation procedure guidelines. Have fun
Been using the rc versions of this for a while, hyped to flash the stable one
Now we are going somewhere , always used your awesome kernel on op7 pro , thanks for making one on op8 pro
Sent from my [device_name] using XDA-Developers Legacy app
Hell yeah!
Really cool to see Smurf kernel for the op8pro! Thanks for your hard work!!
The holy grail has been released
Many thx! And a very big thx to the users donated the device. All thx should go to the about 30 really generous donators!
I hope you enjoy the kernel ?
pappschlumpf said:
For first install use TWRP and flash kernel, Magisk and kerrnel again. I extended the OPs installation procedure guidelines. Have fun
Click to expand...
Click to collapse
Sad... Not using TWRP at this stage. Prefer falsh by magisk and use local update of the OOS.
golf60 said:
Sad... Not using TWRP at this stage. Prefer falsh by magisk and use local update of the OOS.
Click to expand...
Click to collapse
A kernel is not a Magisk module. Well coming from stock Magisk preserve can fail, because of that's an uncompressed image. That could happen with any other kernel too. After kernel flash Magisk is gone. You can flash it with exkm or fkm, and flash Magisk afterwards again with the installer. Afterwards the kernel again. That should do the job too. Updates don't need this procedure for sure.
pappschlumpf said:
A kernel is not a Magisk module. Well coming from stock Magisk preserve can fail, because of that's an uncompressed image. That could happen with any other kernel too. After kernel flash Magisk is gone. You can flash it with exkm or fkm, and flash Magisk afterwards again with the installer. Afterwards the kernel again. That should do the job too. Updates don't need this procedure for sure.
Click to expand...
Click to collapse
My mistake. Flashing with franco kernel manager or EXKM., not magisk. But you have the anykernel script inside your file so why it's not possible to flash with these tools? And why install magisk again afterwards and the kernel for a second time?
All other kernels flashed once with franco and running without issues also without flashing magisk again afterwards?
golf60 said:
My mistake. Flashing with franco kernel manager or EXKM., not magisk. But you have the anykernel script inside your file so why it's not possible to flash with these tools? And why install magisk again afterwards and the kernel for a second time?
All other kernels flashed once with franco and running without issues also without flashing magisk again afterwards?
Click to expand...
Click to collapse
Well i've seen Magisk preserve fail many times coming from stock and especially after installing OTA. I recommend to do it this way to avoid further support actions. If you're an advanced user you can deal with it i guess. And now just flash it.
That's a modified script, just view it. It needs to install the Magisk module for the kernel etc.
pappschlumpf said:
Well i've seen Magisk preserve fail many times coming from stock and especially after installing OTA. I recommend to do it this way to avoid further support actions. If you're an advanced user you can deal with it i guess. And now just flash it.
That's a modified script, just view it. It needs to install the Magisk module for the kernel etc.
Click to expand...
Click to collapse
So flash your kernel with franco... Reboot... Install magisk to both slots.... Reboot... Install your kernel again with franco... Reboot and be happy?
golf60 said:
So flash your kernel with franco... Reboot... Install magisk to both slots.... Reboot... Install your kernel again with franco... Reboot and be happy?
Click to expand...
Click to collapse
Just try to flash it without any further actions. A user in my channel reported that he had no issues coming from another kernel.
Does this kernel work with lineage os
new phone. flashed kernel, magisk, kernel via TWRP as always with OP phones. about 10 minutes after boot, phone is burning hands. Tried reboot, phone won't boot now. Any amount of button pushing does nothing, phone is ded. Guess its true, flash at own risk. hopefully can get another new phone.
EBeatFLA said:
new phone. flashed kernel, magisk, kernel via TWRP as always with OP phones. about 10 minutes after boot, phone is burning hands. Tried reboot, phone won't boot now. Any amount of button pushing does nothing, phone is ded. Guess its true, flash at own risk. hopefully can get another new phone.
Click to expand...
Click to collapse
Absolutely impossible man, phone works cold and nice here and did the same on many test phones over a bunch of weeks. Mandatory is for sure Magisk works, because of needed brain service shutdown! But well even that not working would let it run hot, but for sure not kill your device.
Hold all three buttons and select recovery from fastboot menu. Flash Magisk and kernel again from TWRP.
EBeatFLA said:
new phone. flashed kernel, magisk, kernel via TWRP as always with OP phones. about 10 minutes after boot, phone is burning hands. Tried reboot, phone won't boot now. Any amount of button pushing does nothing, phone is ded. Guess its true, flash at own risk. hopefully can get another new phone.
Click to expand...
Click to collapse
Testing the kernel for weeks now, never had that issue, everything is running super fluid and cool.
How do I find the FKM (Franco) profiles, and how to enable them?
Flashed directly through FKM coming from another kernel. no issues except not seeing any profiles.