I have downloaded the kingklick kernel and there is OC'ing available. It is capable of being OC'ed around 1.1ghz or so. Now I purchased the SetCPU from the market and I was wondering what to do next? Im afraid to just try to fool around with some stuff and mess up my phone. Anyone able to help?
go to setCPU and and click the about tab (i think thats what its called) the dev put a nice info page together that describes the ropes.
Other than that, it is pretty basic (although full of awesomeness). Just set the governor (how the cpu scaling is performed) and set the min max.
But the info page should describe most. There is also information around somewhere that goes more in-depth I am sure
this page helped me
http://www.pokedev.com/setcpu/#7
also, if you search around for 'setcpu profiles' and such, you can see where folks have posted their configs. look around in the thread of your favorite ROM, chances are folks are playing with setcpu in there...look for a couple that sound like they have a clue and ask them if they use setcpu (i'm thinking a direct message, not a thread posting) if they'd send you a screenshot to help jump start your understanding of the app.
Anyone have a good explanation of the governer scaling for newer selections (smartassV2,smartass,powersave,interactive) There was a prior post I had seen I think on the captivate forum that spelled it out to people who don't understand the linux commands
Also I apologize if this has already been asked and answered search revealed nothing for me
PS: Anyone have a radio firmware package that seems to pull better signal than others they've tried?
Weselers said:
Anyone have a good explanation of the governer scaling for newer selections (smartassV2,smartass,powersave,interactive) There was a prior post I had seen I think on the captivate forum that spelled it out to people who don't understand the linux commands
Also I apologize if this has already been asked and answered search revealed nothing for me
PS: Anyone have a radio firmware package that seems to pull better signal than others they've tried?
Click to expand...
Click to collapse
-the smartass governor is based on the interactive governor and tries to get the best performance while keeping power consumption in check.
-powersave governor always keeps the CPU at the minimum set frequency
Hello folks, I'll make this first post temporary, and let everyone know that this Kernel hasn't been developed or tested yet, I just bought my TF300T a couple days ago. I am starting this thread because I initially want some requests/ideas for a new kernel. I am mostly working on this for my own personal use, but at the same time I love to share with the community, so all of my source code and all releases will be posted up on XDA and github.
I want to base this work off of my previous kernels that I developed for the Acer A100/A200/A500 devices. The reason is that I want to include the options for several different OverClock steps, several optional 3rd party Governors, Zram support, AutoGroup Scheduling for Android, Extra / Optional I/O Schedulers, Cleancache + Zcache support, if necessary mmc_cap_erase delete (brick prevention; may not be necessary with this device??).
Here is an example link to my acer kernel: http://forum.xda-developers.com/showthread.php?t=1818924
I plan to port a lot of the features over to this device, but it will take some time to get things right and stable. I am looking for ideas, volunteers, or even partners (team members) to help with this project so that we can bring TF300 users the most stable and feature rich kernel possible. Also this kernel source may be ported to work with other Asus Transformer devices or clones, but since I personally own the TF300T, it will be the only "supported" kernel unless others wish to join the team and help with porting the kernel to work with other devices.
So people, let me know any ideas you have for a new kernel, and any features you'd like to see added. I want to get community input PRIOR to development instead of developing a test build and getting tons of requests for things that may be useful but incompatible with the work already done. Hopefully this makes sense to everyone, and I really look forward to working with a new community and bringing EVERYONE a feature rich kernel that works with stock roms as well as CM/AOKP etc..
undervolting would be cool
Spark1223 said:
undervolting would be cool
Click to expand...
Click to collapse
Definitely, undervolting is of high priority in this project.
Basically any bonus feature I added to my acer kernels in the thread I mentioned above, will be considered for this kernel and added unless there is a major conflict somewhere. I intend the kernel to boot for all users with as close to stock settings as possible, but users may use init scripts or apps such as CPU Master to change default boot settings / profiles / governors. That way it keeps one kernel for everyone, and gives people who aren't extreme OC'ers benefits of the kernel, as well as those who want extreme performance and extreme control tons of features.
As you said in the other thread a combination of clemsyn and unters would be great. Also have a look what _that has done with the tf700 kernel (compatible with tf300) by adding cifs, iso, Fsync and row scheduler support.
Underclocking would be great as well. Clemsyn's elite battery saver kernel on the nexus 7 was fantastic but didn't support 4.2.1 once everyone upgraded.
Also not sure if you are aware but you can mess with the asus cpu scripts inside system/etc to set different clock speeds and limits like I do in my kernel installer for CROMI.
Welcome aboard!
Are you planning to keep develop unters kernel or start one of your own?anyway id like to see pegasusq governor and deadline i/o
sbdags said:
As you said in the other thread a combination of clemsyn and unters would be great. Also have a look what _that has done with the tf700 kernel (compatible with tf300) by adding cifs, iso, Fsync and row scheduler support.
Underclocking would be great as well. Clemsyn's elite battery saver kernel on the nexus 7 was fantastic but didn't support 4.2.1 once everyone upgraded.
Also not sure if you are aware but you can mess with the asus cpu scripts inside system/etc to set different clock speeds and limits like I do in my kernel installer for CROMI.
Welcome aboard!
Click to expand...
Click to collapse
I've been doing a bit of researching on the device before jumping into the coding, so every little bit of insight helps, I know the tf700 and tf300 share the same kernel sources for the most part, but are the devices backward compatible kernels completely? Just from what I have read on a few threads, there are some issues with some hardware and the tf700 kernels with the tf300.. I'm not familiar with the row scheduler yet, is it an I/O scheduler or is it a kernel task scheduler such as BFS/CFS/Autogroup? I had intended to include the Autogroup scheduler for this device, as it has been well tested on my other devices, and improves overall stability, speed, responsiveness (and yes those benchmark scores will raise a very noticeable amount haha). Autogroup was originally for linux, and use the TTY task grouping, which isn't compatible with android, in my Acer kernels I patched it so that it used UID task grouping, and like I mentioned, everyone was very pleased with it (although most people don't completely understand the concepts)
About setting clock speeds in init scripts, thats completely common, and usually its the strategy that most apps take too, they just automate script writing/editing process. I actually want to go in the kernel's sources and edit the cpu freq tables for the highest stable overclock combination possible, yet keep a default clock for the kernel that is known to work and not cause problems. Then of course users can use the init.d scripts as you mentioned to set cpu frequencies at boot, or per event cpu freq as they please.
Governors are an important thing seems to be left out in the tf300t community from what I have seen. I personally want to try to get the preferrered governors I am experienced with working with this device such as, Smartass(v2), Savagedzen, Intellidemand, Wheatley, Lulzactive, Lionheart, and all the stock standard GPL governors.
For I/O Schedulers I'd like to add: BFQ, CFQ, SIO, DEADLINE, and V(R) (based on stability and performance on other devices I have developed with, I'd expect the default I/O scheduler to be V(R), however its hard ot say at this point as no testing has been done yet).
For underclocking, you mean undervolting? If so then: We'll most likely have to just see what the device likes with trial and error on a few test runs, although this shouldn't be hard to achieve. If you mean underclocking, I'm not sure I exactly understand what you'd be trying to accomplish as this feature is already achievable with stock kernels???
I really appreciate all the hard work that you have put into this community, as well as the other devs, and appreciate all the great welcomes!! Thanks!! Keep up the good work and I look forward to working with you guys!
Artic89 said:
Are you planning to keep develop unters kernel or start one of your own?anyway id like to see pegasusq governor and deadline i/o
Click to expand...
Click to collapse
My plan is to take the stock kernel sources and implement the features that I speak of. Also I will probably be referencing other kernel devs sources throughout this process, but my current intention is to base my kernel from stock, and put most of the work I put in myself and if there is anything that the other devs add that I haven't added I will patch those in as well. Generally it is much easier to work with a stock kernel and manually implement features, than to take someone elses work and try to guess at things they have done. If sources are all on git servers, then it will make referencing a whole lot easier, but if sources to most kernels are just zipped/tarred up then it makes comparing things a PITA.
As for the Pegasusq governor, that shouldn't be a problem, as long as it plays well with our processor/board. I am all about as many governors as possible Just sometimes so many options makes debugging harder when people are experiencing stability issues. I will keep anything mentioned here open for implementation, and we'll justs have to see what works and what doesn't.
I appreciate all the great pointers and ideas guys. Like I said I look forward to working with you all. For now its bed time in KY. Night guys!
Can't wait to see how this kernel progresses.... On thing that would be incredible is, my note 2 has a app called st tweaks that you can change cpu/gpu voltage and speed with a lot more options. To have something like that on the TF300 would be great. Most of us run our gpu oced to 650 or 700mhz....
Sent from my SCH-I605 using Tapatalk 2
Yes undervolting. Typod underclocking
sounds interesting
Sent from my magic machine and written by my trained pet monkey with a sprinkle of fairy dust
Great to see new development to our beloved devices!
+1 Very curious to how this pans out! Seems promising :good:
Welcome Sir
Will you also develop 4.2 kernels or will you stick to 4.1 only?
Please add gpu overclock to 700mhz and the possibilty to manage gpu frequencies
This sounds very interesting!!! What I would like you to do is name one for CyanogenMod 10.1 (android 4.2) since I am using that ROM right now.
Sent from my TF300T using Tapatalk HD
My main requests would be GPU OC and i/o improvements.
Just to add to the discussion I'm curious as to why people use other governors on jellybean other than interactive. I am all for choice and customization but you kinda remove something important from jellybean when you don't use the interactive governor in jellybean.
Sorry if this sounds rude I'm just genuinely curious :laugh:
To add to the suggestions things I would thoroughly like to see are 1) cm10.1 support 2) Row scheduler support 3) interactive governor patches.
Notes regarding the third suggestion: Google updated the interactive governor when 4.2 was released to make things significantly smoother and more battery friendly. Though things must be tuned on a per device basis but if people use this kernel enough there should be a decent amount of people to test things and tune it it in just right for this tablet.
Welcome on board, can't wait to see the results.
i would like to see data2sd support for uhs-1 support.
Zadeis said:
Just to add to the discussion I'm curious as to why people use other governors on jellybean other than interactive. I am all for choice and customization but you kinda remove something important from jellybean when you don't use the interactive governor in jellybean.
Sorry if this sounds rude I'm just genuinely curious :laugh:
To add to the suggestions things I would thoroughly like to see are 1) cm10.1 support 2) Row scheduler support 3) interactive governor patches.
Notes regarding the third suggestion: Google updated the interactive governor when 4.2 was released to make things significantly smoother and more battery friendly. Though things must be tuned on a per device basis but if people use this kernel enough there should be a decent amount of people to test things and tune it it in just right for this tablet.
Click to expand...
Click to collapse
Pegasusq is made for quad core devices... Runs great on my note 2
Sent from my SCH-I605 using Tapatalk 2
OK, my wish list:
- CPU freq management
- GPU freq management (preferably live)
- Color management (incl Trinity & OMAP Gamma management)
- Governor management (incl governor settings)
- i/o management (I WANT row scheduler)
And an app to control this. Preferably your own app. Make that App a paid App. (I'd buy it it in a heartbeat).
Have fun!
---------- Post added at 08:44 PM ---------- Previous post was at 08:34 PM ----------
Oh and support both 4.1 and 4.2 ...
Lots of good suggestions and ideas I have read so far. I'm surprised at all of the replies on here so quickly, thats great!
The things I see brought up on here the most that people are wanting are GPU userland control and the ROW scheduler. I mentioned previously that I wasn't familiar with ROW scheduler, but after doing a bit of research, it makes sense as the mainline linux patch wasn't submitted until August. Glad to see that ROW scheduler is just another Block/IO Scheduler too, that makes my plan of implementing my own flavor of Autogroup for Android still valid and possible.
I have seen a few people mention about Interactive Governor and Jelly Bean, I think there is a bit of confusion about Jelly Bean relying on Interactive to work properly. I think this confusion came from the Nexus 7 and Jelly Bean development, as the N7 had the interactive governor rewritten for better OS integration with JB, however JB doesnt exactly depend on it, and you can always base/rewrite new governors off of the Interactive that JB supported kernel source(s) have used.
Most likely the interactive governor will remain the default governor with my kernel, yet the 'option' will be available for several other cpu governors also. This should help people who don't like to rely on cpu profiles, and vice versa.
The main things right now I see people want are:
*1.8+ ghz CPU OC
*650/700 + GPU OC
*Userland GPU control (may be easier said than implemented)
*Userland CPU/GPU Voltage Control
*Added CPU Governors (including backporting N7 interactive governor for better scaling performance with Jellybean)
*Added Block I/O Scheduler Support (i.e. ROW, Deadline, VR, NOOP, BFQ, etc)
*CIFS/Samba FS Support
*NTFS R/W support (high speed) - I need to research the NTFS support provided with stock roms and 3rd party roms. NTFS-3G (fuse) would be the best option if it doesn't break compatiblilty with the stock rom's VOLD
*Backwards compatibility throughout roms including stock roms, CM10, CM10.1, aokp, etc (4.0, 4.1.x, 4.2 base)
Some things I haven't seen many or any people mention that I personally would be interested in including support for (which may or may not be included in stock kernel source / configs):
*ZRAM
*CleanCache + Zcache
I've mentioned a lot about Autogroup scheduler in the previous posts, I'm sure that most people probably don't fully understand what it is for and what the other options are. If you have ever had a device with a custom kernel that supported BFS (brain f*ck scheduler) then you know of the performance increase overall with BFS. As far as I know the Acer Tabs that I integrated Autogroup into the kernel was the first android tablet to fully support Autogroup on Android, as the original Autogroup mainline patch was developed for GNU Linux distributions that use per-tty task scheduling, android doesn't use this, instead I patched Autogroup kernel source to use UID task scheduling (per user/root) instead, and the results were quiet astonishing versus the standard CFS (completely fair scheduler). Autogroup is very well known for outperforming BFS also, and BFS had been used with android devices previously to get around the sluggishness from CFS, since Autogroup didn't work properly out of the box with Android. To help sum things up, here is a link explaining more about how Autogroup helps process/task scheduling at the kernel level: http://www.phoronix.com/scan.php?item=linux_2637_video&num=2&page=article
Right now I'm still in the research phase of this project, and learning more about the actual hardware inside the device, and what methods our stock roms / custom roms use to interact with the hardware. I'm planning on getting my sources for my new kernel started sometime tomorrow, but as much as people get their hopes up for things like this, I will say that I'm not going to rush into throwing out releases or putting things together in a hurry. I'm all for a quality kernel here, and with that said - it will take some time to get everything in line. Please don't ask for ETAs or if I have any beta/test versions. As soon as I have a test kernel zimage available it will be posted and available on my github.
I appreciate everyone's collaboration and cooperation greatly! Many good things to come guys!
Hands down if you can make this happen I will give you 10 bucks.
Hello guys,
I am writing this to convey to you my wish for an updated Kernel Standalone. I recently started playing with the ramdisk, edit and creating my own kernel profiles. But I need more.
Of the current kernels out there, the one that caught my attention the most was the xd-kernel, I don't know if it will be because its forum topic is very striking and such ... But it was the first. I have been investigating, and I have realized that the version that I use (1.7) does not bring the CAF files. I didn't know what the CAF files were, until I came across a folder containing 3 sd845.dbt files in zip 2.0.2 of the xd-kernel.
That's when I realized that those files are direct kernel updates for our SOC.
I quickly realized that although I believed that the 1.7 kernel was better because it could raise the gpu frequencies above 710mhz, it was an outdated kernel and without direct SOC support as such.
The TNO kernel has not been tested yet by me, its forum post is very simple and it did not catch my attention ... but today I checked that it has CAF files and that it was published in December.
I have doubts about this kernel ... can gpu be overclocked?
Does it bring recent optimizations such as improvements to the CPU_governor?
Improvements to the Schedutil?
Drivers improvements?
In short ... What this kernel brings, that the xd-kernel does not have (not counting the CAF files).
And finally I wanted to ask for help ...
As I see that no one has the intention at the moment to update those kernels, or to create a new one ...
I would like someone to tell me where to start, for me to create my own kernel for this soc, tips to improve the soc (like the issue of Wakelocks, Oc, implement CAF files ...).
I do not intend to create a kernel that everyone should install. I have never programmed and they seemed to me like gods doing things to a kernel, like putting spectrum and things like that. But there is always a first time for everything, and this time it was my turn to begin to understand how a kernel worked, how spectrum is implemented and what settings are related to governors and I / O schedulers. But I need more, I need to compile a kernel that I say: Damn, if this kernel looks like a kernel from the "pixel3" forum, very complete and well-founded.
Hopefully someone will listen to me and teach me where to start, considering that I have not done this in my life. But reading and reading I have ended up here trying to be better. I think that if I have the necessary means (documentation and links on how to create a proper kernel) I could create something good that will work for all of us much better, but I am satisfied that it works well for me (as I said I cannot pretend that everyone uses my job).
Well guys, sorry for my english, thanks for reading and a hug to everyone (with mask hahaha).
Some questions what you should ask yourself are:
You want to create kernel for stock system? Or for some certain rom? To Android 9 or 10? What improvements do you want to bring?
I know you want to made it for yourself, but you can share your work to other people if you want.
ShadoV90 said:
Some questions what you should ask yourself are:
You want to create kernel for stock system? Or for some certain rom? To Android 9 or 10? What improvements do you want to bring?
I know you want to made it for yourself, but you can share your work to other people if you want.
Click to expand...
Click to collapse
Thanks for the reply
I would like to create it for the Stock Rom as the Evolution X team is doing a great job on AOSP.
I would mainly focus on Pie, I think it has more support currently, twrp ..., and then it can be ported to 10.
Improvements:
-Unlock CPU / DDR / GPU frequencies
-Import current CAF files for sd845
-SlimBus OC
-Wireguard
-Spectrum / Franco Kernel implementation
-Latest Schedutil governor uptades
-add good governors and I/O schedulers
-add support for misc features like zram compress formats, latest linux security patches...
And can be imported other features from kernels with same SOC devices like pixel or oneplus6.
I would have no problem sharing work with someone, I would rather have someone correct me for what I do wrong, than have a noob direct the project alone. I know there are many here that I am proposing, they do it in 5 seconds, but I don't have much idea and I need time and reading.
Hugs bro.
When I flashed the TNO kernel it gave me issues. My status bar would flicker non stop. Performance increase wasn't noticable and there is no overclocking the GPU. Most importantly, it didn't give me the options of different governors like the XD Kernel, and I/o schedulers.....having Zen and Maple with the XD is great. The one thing the TNO Kernel did have that the XD kernel lacks is Wireguard support, but I never got into that anyway. I would like to see another Kernel that gives us some of the options available to the V30 users, with RCTD disabled already. Beast Kernel, Konverged Kernel....others have so many options!
Yeedatoy said:
When I flashed the TNO kernel it gave me issues. My status bar would flicker non stop. Performance increase wasn't noticable and there is no overclocking the GPU. Most importantly, it didn't give me the options of different governors like the XD Kernel, and I/o schedulers.....having Zen and Maple with the XD is great. The one thing the TNO Kernel did have that the XD kernel lacks is Wireguard support, but I never got into that anyway. I would like to see another Kernel that gives us some of the options available to the V30 users, with RCTD disabled already. Beast Kernel, Konverged Kernel....others have so many options!
Click to expand...
Click to collapse
Wow thank you for the reply!!
Ill see these kernels, but my doubt is the compatibility with our device, is the same SOC, ok, but we have different screen for example. What do u think about this?
If it really works, it would be a great idea to port a v30 kernel. Looking at xda, I realize that the xd kernel looks a lot like one called SmurfKernel or something like that, from the OP6 device,
I would even say it is a port.
I found that kernel is not the same, is SD835... f*ck
Ill search on v35 forum
Update: Have 5 or 6 threads in v35 development :'( and saw 7 pages on v30 forum, what a forum lol.
Hey buddy! Long time no talk! I hardbricked the G7 so I took 2 broken moto G6's and made one working one into a 64bit beast running Android 11. Ive been really busy but finally found the time to revive the G7 with QFIL. Starting from scratch, I flashed the TNO kernel, which wiped out Magisk, but after a reflash it actually runs really smoothly. The XD kernel has too many errors to count. It's built completely wrong. If you monitor your gpu, you'll see the worst of its flaws. The TNO kernel runs really well, and although it doesn't have all the bells and whistles other kernels have, it works correctly. I must have had too many modifications already yheyr'=[