Related
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
while im no genius when it comes to this stuff, somehow i would suspect that people here are already looking into this.
i could be wrong tho lol
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
jlevy73 said:
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
Click to expand...
Click to collapse
But where is he...??
G2X
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
crisis187 said:
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
Click to expand...
Click to collapse
Please don't try to load O2x software on your G2x.
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
GideonX said:
Please don't try to load O2x software on your G2x.
Click to expand...
Click to collapse
have you tried it yet though is my question
im not worried if i flash a kernel and it doesnt work i can reflash my old kernel if it doesnt work and gets stuck into a bootloop
crisis187 said:
have you tried it yet though is my question
Click to expand...
Click to collapse
Someone in another thread tried this and it messed up their baseband. A restore doesn't fix it apparently.
Big rush dog, the tiamat kernel guru and Guy getting engadet headlines for oc the xoom to 1.7 ghz has gpu oc in his kernels. I will be honest though, I can't tell the difference except maybe video streaming works a little smoother. I personally don't think it is worth the devs time...
Sent from my LG-P999 using XDA App
Howdy! I'm the developer of that kernel
To be honest the GPU overclocks aren't all that beneficial. There is a little bit of a speed bump (I managed to get the highest score on nenamark2 for example). But the difference is was 27fps vs 32fps. If someone is interested in incorporating that into the g2x I'll be happy to show them the changes I've made. I haven't released the source because I'm lazy but there isn't too much to it.
Actually, if you look at the voltKernel sources for the O2X you'll see the same changes there.
chuckhriczko said:
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
Click to expand...
Click to collapse
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Great!
@ fallout0 thank you i hope that you can help out one of our devs on this.
morfic said:
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Click to expand...
Click to collapse
thanks morfic i hope everything goes smooth with your kernel, i would love to test it out once u feel it is ready. and thanks for not rushing it.
faux123 said:
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
Click to expand...
Click to collapse
You should talk to Fallout0 he seems like he got past the system bus/GPU locked issue. both of you can maybe learn something new from each other. & it would be awesome if the both of you can work on a kernel together.
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Would overclocking the gpu help run nds4droid any better? What else would ocing the gpu do? Everything seems to be very fast as it is lol
Sent from my LG-P999 using XDA Premium App
dkb218 said:
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Click to expand...
Click to collapse
Pushing cpu more I don't see useful other than keep up with your buddy's Nexus S' quadrant scores and make sure your hands stay warm in a cold Chicago winter.
I build kernels usually when things stutter or otherwise annoy me. The pushing the OC usually comes by request of those who just want more more more.
I do like to remove bottle necks.
The hardwired clocks. Well the.cpu ones are hardwired too.
The gpu/bus oc works, until boost and throttling kick in, where again values are compared to hardwired values. using offsets after the comparison would be the way around without killing boosting and throttling.
Guess main thing that stopped me is the heat at 1.5ghz, and the frowns over 1.2ghz and 1.3ghz kernels, without further "what else is in there"
Still hoping fallout can share what he/she has, it'll help making this a reality, sooner.
It's tedious. Most of all.
I've finally managed to get the 6210 kernel to compile AND work with the standalone kernel modules that samsung didn't bother to provide source for (ar6000 and j4fs.) It seems that the source on opensource.samsung.com uses different config flags than the source they used to compile for the shipping tablet.
The question is: Now that I can recompile it, what do I do with it? Well, I'll think about that and come up with some interesting answers. Probably a few efficiency tweaks, modifying the init.rc to allow for init.d parsing, and.. well, I don't know what else.
(I can find the source for the ar6000 adapter and j4fs, but I was extremely determined to get things working with the existing modules. I'm stubborn.)
Take care
Gary
Good luck gary!
Can you get overclocking enabled?
Sent from my GT-P6210 using xda premium
excellent job gary. bravo!
Excellent work. I might try my hand at this kernel development stuff. I did a lot of work with pascal a number of years back. Some c on the side. I might be able to add features that others have pioneered? We'll see... time is the enemy I believe. Sorry about the ramblings.
Sent from my GT-P6210 using xda premium
I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary
posted in the development section
garyd9 said:
I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary
Click to expand...
Click to collapse
Hey, users can throw stuff in init.d themselves!
(although most are too lazy to do so...)
i would like my ext partition on my sdcard to mount itself if you can do that gary! thanks and good luck!
I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?
deezomaxima said:
I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?
Click to expand...
Click to collapse
Please find the thread(s) in the dev subforum referring to ODIN and/or stock firmware.
Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.
deezomaxima said:
Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.
Click to expand...
Click to collapse
No problem.
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
I'm not familiar with that, but I'd be happy to investigate it. I'll add it to my 'todo' (but no promises on a timeline.)
maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
Actually... It appears that 'tun' is already compiled into the kernel (directly - not as a module.) You should be able to use it without loading "tun.ko".
Can you please check this out?
Gary
Gary,
Correction on my assessment of your kernel. It's fine.
I'm back to stock and it's still doing what it was doing at moments and I've come to 2 conclusions:
1. The email widget I'm using on one page with a few icons
2. The Facebook widget I'm using on another page.
Pages with just icons seem to run fine.
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?
deezomaxima said:
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?
Click to expand...
Click to collapse
Only very non-scientific ones. (It's extremely difficult to ensure that exact same number of messages are pushed to my phone in a given period of time, that various forms of wifi interference are causing the same increases in power, etc.) That being said, I'm getting slightly better time on my battery with wifi set to "always on" compared to what I got on the stock kernel with wifi set to "never turn off when plugged in." (tablet was left in range of an AP in both cases.) I drop perhaps 5% in a 16 hour period with little to no screen time.
However, I'm also undervolting a bit with the custom kernel (values used are posted in another thread in this subforum), and have no active widgets beyond a single WX one that polls once/hr. I also changed the governor on my own to conservative at default settings (which saves a bit of battery as well.) Default for the kernel is ondemand which gives slightly better "snappiness."
Take care
Gary
Does it make a huge difference? Of course not. The undervolting is probably the only thing making much of a difference at all.
BTW, some of the tradeoffs between ondemand and conservative can be reduced by making some tweaks to the conservative governor:
https://github.com/Entropy512/linux_kernel_sgh-i777/commit/3b92eb76e72bbaa88aa8d87d306d1b61c9485912
Should be easy to port to .36
Main thing there if you don't want to change defaults is the stuff that reduces the minimum polling interval - the MIN_SAMPLING_RATE_RATIO lines - everything else is just tuning more aggressive (performance-tuned) defaults.
Thanks for the reply Gary.
So, I'm back on your kernel and installed SetCPU. I'm still messing with the settings to see what I get as far as battery life. I've had my Tab off charge since 7am this morning and it's now 1320 and Juice plotter is showing I have 67 hours of run time (95%) as opposed to seeing numbers in the 40s before hand. My device now wakes up out of sleep as it should instead of going into a non-responsive state sending me to reboot the whole device.
Everything is looking good now.
Team Fah-Q Presents...
Scorched Kernel for Blaze ICS v1.0.29
Built with the Linaro Toolchain v4.7, the purpose of this kernel is to fix bugs, add features, add performance, and hopefully save some battery where possible. However, battery life will most likely not be as good as stock, since the device is overclocked and DVFS (dynamic frequency and voltage scaling) is turned off. I have done my very best to squeeze every ounce of battery life out of this device.
It includes a brand new CPU Governor called Scorched, developed by me and based on the lagfree governor. It focuses on saving power and reducing the usage of the higher CPU frequencies unless necessary, while still keeping responsiveness and performance intact.
The kernel should work with any ROM that is derived from the stock Samsung ICS release IMM76D.LH5, however I recommend using it with the Tweaked ROM, as that is what I develop it against.
This is a kernel several months in the making. Hope you like it
It is STRONGLY advised to do a full nandroid backup in CWM before installing the kernel,
as the installer will overwrite kernel modules in /system/lib/modules. You've officially been warned
NOTE: This thread is reserved for bug reports, logcats, and other development related discussion. General discussion, questions, etc should be posted in this threadKernel Features
IO Schedulers:
zen (NEW)
vr (NEW)
sio (NEW)
deadline
cfq
noop
CPU Governors:
scorched (NEW)
lagfree (NEW)
interactive (NEW)
ondemand
conservative
userspace
powersave
performance
Other Features:
Overclocked to 1.72 GHz
Voltage control support
Support for init.d scripts, added automatically during installation of the kernel.
ZRAM support with Google Snappy compression, with a default size of 64 MB.
Other tweaks and fixes, too minor to note. Check the Google Code site if you're interested.
Credits/Thanks
withere2 - Endless testing, testing, ideas, more testing, scripting support, more testing. Did I mention testing?
erikmm - Pulling me into kernel development
showp-1984 - Lots of initial help getting off the ground with kernel development
faux123 - Some source code from his Samsung GS2 github repo
Changelog and Downloads
Changelog and Downloads
2012-12-21 - Version 1.0.29 - tfq-scorched-kernel-ics-1.0.29-signed.zip
ADB now runs as root. Not as easy as you might think to do it properly...
2012-12-17 - Version 1.0.22 - tfq-scorched-kernel-ics-1.0.22-signed.zip
Initial public release of kernel
Resolved issue with battery life. Standby time should be almost double that of version 1.0.20
The source code for this kernel can be found on Google Code:
http://code.google.com/p/scorched-kernel-t769-ics/
All previous release versions of the kernel can be found on the Scorched Google Code site
http://code.google.com/p/scorched-kernel-t769-ics/downloads/list
FAQ
FAQ
What is the Scorched CPU Governor?
The Scorched CPU governor is rather similar to the lagfree governor both in its source code and its purpose. The difference is that while lagfree seeks to give performance-on-demand by increasing immediately to the maximum CPU frequency, Scorched jumps immediately to a mid-point frequency and then gracefully increases or decreases the CPU frequency as required. This provides both performance-on-demand as well as extended battery life.
multi core support
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all
awesome finally some scorchness for the blaze
merwin said:
Changelog and Downloads
2012-12-17 - Version 1.0.22 - tfq-scorched-kernel-ics-1.0.22-signed.zip
Initial public release of kernel
Resolved issue with battery life. Standby time should be almost double that of version 1.0.20
The source code for this kernel can be found on Google Code:
http://code.google.com/p/scorched-kernel-t769-ics/
All previous release versions of the kernel can be found on the Scorched Google Code site
http://code.google.com/p/scorched-kernel-t769-ics/downloads/list
Click to expand...
Click to collapse
Many thanks for your hard work.
However I've been using this kernel for a couple of days now with tweaked 2.1, and deleted battery stats but my battery life is really poor.
I've left the system essentially in standby for several full charge cycles but I only get 10 hours with next to no use, if lucky.
With stock kernel and Blz3r v3 and with heavy usage I would easily get 14 hours.
I'm still going to keep on using it and characterizing it and hope it gets better.
Sent from my SGH-T769 using xda app-developers app
theshowman said:
Many thanks for your hard work.
However I've been using this kernel for a couple of days now with tweaked 2.1, and deleted battery stats but my battery life is really poor.
I've left the system essentially in standby for several full charge cycles but I only get 10 hours with next to no use, if lucky.
With stock kernel and Blz3r v3 and with heavy usage I would easily get 14 hours.
I'm still going to keep on using it and characterizing it and hope it gets better.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Not sure what to tell you. I've attached an image with my stats on it. That's 7 hours, mostly standby, dropping 30%, with wifi calling, exchange sync, gmail sync all on.
And this is more of a general Q&A thread topic also
soldier1184 said:
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all
Click to expand...
Click to collapse
Please ask this in the general questions thread.
Using just CPU0
soldier1184 said:
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all
Click to expand...
Click to collapse
This app will let you use 1 core, both or link them together as one:
PC Link: https://play.google.com/store/apps/...sMSwyLDEsInJzLnBlZGphYXBwcy5LZXJuZWxUdW5lciJd
nickmcminn60 said:
This app will let you use 1 core, both or link them together as one:
PC Link: https://play.google.com/store/apps/...sMSwyLDEsInJzLnBlZGphYXBwcy5LZXJuZWxUdW5lciJd
Click to expand...
Click to collapse
In my own testing, I have found that it is often worse to turn off a core completely, than to aim for a lower clock speed on both active cores. My theory is that the increase of speed with multithreading speeds up processing over the single corr, thus staying at a higher frequency for less time.
Just a personal observation.
I'm New
I'm sorry if i sound like an idiot, but Does this work on the stock ICS rom? I'm rooted btw
and does it support undervolting?
Thank you, Very stable and responsive kernel. Only issue I've had after installing the kernel is that when I try to send an app from play.google.com to my phone it doesn't show up. I can still install from within the phone itself just not website to phone, not sure if it's related to this Kernel or not but started after flashed it.
Again I'm not 100% positive that it's related so will need to do some more testing...
techclan said:
Thank you, Very stable and responsive kernel. Only issue I've had after installing the kernel is that when I try to send an app from play.google.com to my phone it doesn't show up. I can still install from within the phone itself just not website to phone, not sure if it's related to this Kernel or not but started after flashed it.
Again I'm not 100% positive that it's related so will need to do some more testing...
Click to expand...
Click to collapse
Looks like the problem with the apps not getting pushed to the devide was a stuck process, my "smooth calendar" was at 83% cpu utlization and app pushes were being halted.
Android ICS 4.0.4 UVLH5 + Scorched Kernel ICS v1.0.29
techclan said:
Android ICS 4.0.4 UVLH5 + Scorched Kernel ICS v1.0.29
Click to expand...
Click to collapse
That's about right for the benchmark. I'm considering going a slightly different route with the kernel that may reduce performance a bit but should up battery life significantly.
Sick 2 year old at home so I've had limited time to play, unfortunately.
merwin said:
That's about right for the benchmark. I'm considering going a slightly different route with the kernel that may reduce performance a bit but should up battery life significantly.
Sick 2 year old at home so I've had limited time to play, unfortunately.
Click to expand...
Click to collapse
Hope your 2 year old gets well soon. Yes sacrificing a bit of performance to up the battery is definitelyitly worth it. Also seems like your scorched will outilizelize 384 and above, not sure how much battery can be saved but basic call functions and such can perfectly work on 192Mhz
roms
does this work on pacman rom 4.1.2 for the blaze please respond quickly my current kernel is random rebooting and this worked when i was on stock rom
No its for ICS
Sent from my SGH-T769 using xda premium
Welcome to decimalman's kernel playground!
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.
Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.
Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode
This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
PsiPhiDan said:
This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
freelunch is absurdly simple, but does its job well. Let me know what you think. Happy flashing!
aypeeootrek said:
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
Click to expand...
Click to collapse
I don't run TW, so I don't have any plans to release a TW kernel. If there's enough interest, I suppose I could get to work on one though.
Interesting. Looks cool man, will check it out
Sent from my SCH-I535 using Tapatalk 2
I'm excited to give this a shot!
Sent from my SCH-I535 using xda app-developers app
flashaholic commencing flash!
Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2
Love this kernel! Freelunch is amazing
Sent from my SCH-I535 using xda premium
This kernel run pretty good!!
Sent from my SCH-I535 using xda app-developers app
masri1987 said:
Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's the recommended tuner app, and plenty of people are using it (mostly on Sprint and AT&T). It shows some options that are completely bogus (like GPU governor), but I've added a few extras that only Trickster supports.
Thanks for the encouraging feedback, everyone! It's much appreciated. :good:
Kudos on this kernel. It has been perfect for me so far.
Running good on my d2usc! What scheduler do you recommend?
Sent from my SCH-R530U using Tapatalk 2
New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
More edit: I'm building a 3.0 kernel with trinity colors support and GCC 4.8.0 now. It should be up shortly.
decimalman said:
New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
Click to expand...
Click to collapse
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2
trvbone said:
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Thanks for the expl I'll flash tomorrow morning and give it a whirl! Great job BTW. This is now my daily driver!
Sent from my SCH-R530U using Tapatalk 2
decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Giving it a go now. Do you have any test methods you use to test the stability of a kernel other than the everyday use approach? Thanks for the support, looks sweet:good::good::good:
This is my Shield Kernel, focused on the security and stability of Android OS, you can flash it using TWRP. This use the last CM sources of MSM8916 SOC, your bug reports are important for the better stability of Android.
The Kernel was tested on XOSP ROM (based on AOSP), may be it works on stock and CyanogenMod ROMs, so it's for Marshmallow ROMs.
Note
This Kernel is only for Moto G 2015 (osprey), I am not responsible of your bricked devices, flash at your own risk.
Features
Builded with Uber 4.9 optimized
Lastest wlan drivers with size optimized
Cleaned up defconfig
Correct permissions for GENTLE SLEEPERS
ThunderPlug
LCD Notify
KCAL control calibration color (thanks @savoca)
Enabled some TCP congestions
-BIC
-CUBIC
-WESTWOOD
-HYBLA
-ILLINOIS
-YEAH
-LP
-SCALABLE
-VENO
-VEGAS
-HTCP
-HSTCP
Optimized sfck compression
Low Memory Killer by default
Marshmallow ROMs support
Lionfish Governor (thanks to @squid2)
Last zram documentation
Optimized SHA routines 256/224
Optimized some task of Shed
Silenced many log_spam
Some fixes of memory leaks
Shed controls
Writeback fixes
Reduced some wakelocks
Optimized shed domains
Cleaned some dead code
Optimized apply_slack (PERFORMANCE)
Improves on shed.h about LOAD_FREQ
Some specific optimizations for cortex A53
Many USB and WiFi IDs for correct use
CRC toogle for more performance
Used last repo sources from CyanogenMod
Arch Power enable for speed
Release history
Code:
r5: September 04, 2016
- lib: crc32: clean up spacing in test cases
- initramfs: support initramfs that is bigger than 2GiB
- sched: Use swap() macro in scale_stime()
- kernel: Add required TetherStats definitions
- arm/dt: msm8916: Enable bam_dmux fast shutdown
- lib: align source before using optimized implementation
- ANDROID: restrict access to perf events
- rcu: Move SRCU grace period work to power efficient workqueue
- net: wireless: move regulatory timeout work to power efficient workqueue
- firmware: use power efficient workqueue for unloading and aborting fw load
- workqueue: Add system wide power_efficient workqueues
- workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented workqueues
r4: July 30, 2016
- Support for all Marshmallow ROMs
- powerpc: Align TOC to 256 bytes
- arm: crypto: Add optimized SHA-256/224
- zram: update documentation
- cpufreq: implement lionfish gov
- sched/rt: Reduce rq lock contention
r3: July 25, 2016
- timer: optimize apply_slack()
- sched: LOAD_FREQ (4*HZ+61) avoids loadavg
- Writeback sync fixes
- Added KCAL control calibration color
- xsched: Optimize build_sched_domains() for saving first SD
- zlib: clean up some dead code
- Reduced WakeLocks
r2: July 22, 2016
- Added some TCP advanced [B](the names it's avalaible on the Features section[/B]
- xz: Optimize Sfck Compression
- Added Thunderplug
- fs/pipe.c: skip file_update_time on frozen fs
- msm: mdss: Silence log spam
- fs/namei.c: fix potential memory leak in path_lookupat
- sched: Optimize task_sched_runtime()
- drivers: lmk: enable adaptive lmk by default
- Added LCD NOTIFY from LG
r1: July 20, 2016
- Initial release for users
Flash instructions
1. Download kernel zip and go to TWRP
2. Flash kernel zip without wipes
3. Reboot and enjoy
Downloads
New folder for download the last release of Shield Kernel
XDA:DevDB Information
shield-kernel-g3, Kernel for the Moto G 2015
Contributors
TechnoAnder
Source Code: https://github.com/ShieldKteam/shield_osprey
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r5
Stable Release Date: 2016-09-04
Created 2016-07-21
Last Updated 2016-09-04
Hi, I think it's a good kernel, but can you add some stuff like DT2W, CPU governors/hotplug and optional underclock (19MHz on the GPU in idle) and overclock? With these things it will be the best kernel for me.
I am going to try it now
PD: Greetings from Spain!
EvilHowl said:
Hi, I think it's a good kernel, but can you add some stuff like DT2W, CPU governors/hotplug and optional underclock (19MHz on the GPU in idle) and overclock? With these things it will be the best kernel for me.
I am going to try it now
PD: Greetings from Spain!
Click to expand...
Click to collapse
Yeah, in next release will have new things
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
Click to expand...
Click to collapse
Any way to add voltage control?
Sent from my MotoG3 using Tapatalk
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Click to expand...
Click to collapse
Can you add CPU governors such as impulse & alucard, as well as GPU & CPU OC such as the 1881 MHz for CPU and 650/720 MHz for GPU? For some reason though, the GPU OC seems to be really fidgety. Maybe you can take a crack at it?
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Just keep it minimal, like Optimus
Acidfire.TM said:
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Click to expand...
Click to collapse
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
@acejavelin
You already said all of this, wow, defensive much?
How about you go use optimus then. Or even better.
Stock CM13 KERNEl
Red flags??. There was one user asking for some OC.... yeah,! RED FLAGS!
Also.. MotoG3 is not over locked at 1.36(1.4).
The motoE and others are underclocked at 1.2 & 1.3.
And overclocking.. Unstable??... Hotter CPU?? Less battery??
Maybe you don't know how to set up an OC properly but I haven't had any of those problems unless I'm being really cheeky and max out the frequency.
I run over clocked without hot plug at 1.6ish
And run cooler than on the stock kernels.
I'm also benchmarking all the time, so I know I'm
Getting the performance
increase also.
PS. I agree with you about the dt2w, I don't use it.
[
One suggestion if building a kernel for battery. The lionfish governor is great for battery. I've been testing this governor and battery is good for Moto G3.
Sent from my MotoG3 using Tapatalk
dazeone said:
[
One suggestion if building a kernel for battery. The lionfish governor is great for battery. I've been testing this governor and battery is good for Moto G3.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I would like to do what acejavelin suggested
And build upon firekernelv4.
I like lionfish gov, and people want advanced TCIP
. it would be battery life oriented, with performance options
.
Acidfire.TM said:
I would like to do what acejavelin suggested
And build upon firekernelv4.
I like lionfish gov, and people want advanced TCIP
. it would be battery life oriented, with performance options
.
Click to expand...
Click to collapse
That sounds good. Any hot plugs that you're thinking of to use?
Sent from my MotoG3 using Tapatalk
Acidfire.TM said:
@acejavelin
Also.. MotoG3 is not over locked at 1.36(1.4).
The motoE and others are underclocked at 1.2 & 1.3.
Click to expand...
Click to collapse
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
acejavelin said:
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
Click to expand...
Click to collapse
Looking back, I was about off centre myself this morning, apologies.
acejavelin said:
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Again thanks mate
Henriquefeira said:
Just keep it minimal, like Optimus
Click to expand...
Click to collapse
Yes, sure I will do it.
Acidfire.TM said:
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Click to expand...
Click to collapse
Thanks
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
Yes, you opinion I like a lot, may be I wrong saying "users, what features you want for this Kernel?", no problem, this forum is for say the opinion of each one, I will work focused on the battery and security, thanks for your opinion.
acejavelin said:
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
Click to expand...
Click to collapse
I had the same suspect months ago, so I did a research and I found that osprey uses MSM8916 board of course, but its second revision which supports 1.363 GHz. Just to be clear, I'm not talking about snapdragon 412 but just about a 410 hardware revision; exactly like happened for snapdragon 810 (Qualcomm released a new 810 revision to fix the overheat issue for those who can't remember).
Motorola definitely didn't overclock it.
Source: Motorola's commit picked from qcom.
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
Click to expand...
Click to collapse
Ultra fast charge
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
Sounds like a cracking kernel why don't you compile it
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
acejavelin said:
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Dunno if u got the memo but our device does not support doze
skooter32 said:
Ultra fast charge
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
Sounds like a cracking kernel why don't you compile it
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
Dunno if u got the memo but our device does not support doze
Click to expand...
Click to collapse
Lol... Yeah, I knew, it's a typo. Supposed to say "that doesn't support doze'. My bad
Sent from my XT1575 using Tapatalk