yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Mikes30000:
Thanks for your help. If it makes you feel any better, even the kernel that comes with CM11 freezes up for a few seconds every once in awhile. Maybe I just need to go back to a nice AOSP ROM. I can't decide, just too many to choose from!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3615715]Mikes30000[/MENTION]

Yeah, some small bugs are known and related to either the CAF kernel or CM based roms (I get this freeze bug even on my Galaxy S4 with stock kernel using CM11, but not on AOSP/Google Edition or stock based roms), though, still, I've seen much more bugs.. I would actually be ashamed to make a list of what I've seen :eek:
[Nexus 7 (2013) Original Android Development] melander:
Its nice to be a stock junkie, lol. Thanks for the update, really satisified with this kernel, ?
[Nexus 7 (2013) Original Android Development] JayanWarden:
So that means for example, if I set the minimum voltage for 702MHZ to , say, 750mv, the kernel can still, like, change the voltage to , say, +50mv to prevent a crash due to too much undervolting
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4341753]JayanWarden[/MENTION]

It's a bit different. More like, if we have 900mV for 702MHz at stock for example, it may jump to 925 or drop to 875 if the load (high or low) permits it on a given binning. If we are applying -100mV uV, now giving 800mV, it'll be used as the new starting point, so the jump will now be at 825mV and the drop at 775mV. It'll give you a plain -100mV uV versus stock and it sticks, it's just a bit different than a fixed value that will never move. It makes OC more delicate but supposedly enhance power efficiency.
[Nexus 7 (2013) Original Android Development] hello247:
Nice. I can only push mine down by -100mv while using stock cpu frequency on n7( acpu pvs 3).
[Nexus 7 (2013) Original Android Development] mus1mus:
Just a noobishness, does it mean that UV'ing applies only to the minimum frequency the CPU is at? Or does it also apply to the Max value set?

It could really be amazing if UV'ing also applies to OC'ing. Being an overclocker ( Desktops ), I think it will also be very beneficial if a user can be given those option in the kernel itself. Not just with apps like Trickster and stuff.

Is there a way to do that other than apps?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5559267]mus1mus[/MENTION]

The uV you can select in Aroma is only for the lowest freq, though you can uV any step with TricksterMod or FauxClock (even overclocked ones). When you say "in the kernel itself", do you mean in the Aroma installer ?
[Nexus 7 (2013) Original Android Development] mus1mus:
Sort of.. I know it can be tricky as it may not be the best for everyone. And considering chip binning, what works on some might not work on others, still that can be a bit of plus on the kernel side. But if that is too much, can anyone modify those settings without using Trickster and FauxClock?

Sorry very new to android thingy.. :angel:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5559267]mus1mus[/MENTION]

You'd need to make a script to apply your settings at boot, but that's indeed possible.

I'll think about the best way to add such a feature in Aroma :)
[Nexus 7 (2013) Original Android Development] nikr123:
Why would you even try. Aroma + Trickster/FauxClock and you have got almost every feature covered. You most really hate these apps. ;)
[Nexus 7 (2013) Original Android Development] mus1mus:
That's a great gesture on the OP's part. :good: :good: :good:

Honestly though, there's really nothing wrong with the kernel I should say. Power Savings on this kernel is top-notch. Better than anythings else I have tried.

But if a feature like that can be added, power savings will truly be magical.
[Nexus 7 (2013) Original Android Development] SynnyG:
I'll wait this release impatiently :)

But don't be ashamed, your kernel is really good but it need just some adjustments for the caf base ! These issues are related to the CM kernel tree or it's just caused by some tweaks added by you ?
[Nexus 7 (2013) Original Android Development] mus1mus:
Not that I hated those. I just noticed a better performance and power savings using just the installer TBH. Besides, if you have been overclocking a PC, you must have known that it should better be done on the BIOS other than softwares. Not sure if that is also the case for Android but I just got used to doing that way. No software intervention, No software eating your RAM, and just simply settings sticking to what you assigned (PC speak)

LOL
[Nexus 7 (2013) Original Android Development] nikr123:
I wouldn't say so. It would almost work the same way. RAM isn't a problem on a android device with 2gb RAM. The kernel has a priority list and kills apps if needed. And about the settings sticking you have to turn on set on boot.

---------- Post added at 06:44 PM ---------- Previous post was at 06:37 PM ----------

@mus1mus

Here is a post about android RAM Management

http://mobworld.wordpress.com/2010/07/05/memory-management-in-android/
[Nexus 7 (2013) Original Android Development] mus1mus:
Well, seemed like I really have to do a lot of research in the field. :)

Honestly, I am just a lazy hog that prefers doing it simpler. Besides, there are things I am very new at and terribly not in the know with all the settings Faux or Trickster have.

Going back to UV'ing, if Max clock UV'ing feature can be added through Aroma, it will make things simpler for all of us, don't you think? Except the OP, I guess.

Anyway, this kernel have been better than anything else. Thanks TK

Edit: Not trying to start a flame with this but: It has been said a million times before that a normal computer user wouldn't notice the difference between a computer running with 4GB of RAM compared to another with 32 GB of RAM. But look at the world now, 8GB has been the minimum OS requirement nowadays. Though not really directly related to android, and going back to you statement about Android RAM management, imagine if you can always squeeze every bit of MB out of your RAM. :)

And there's must be a reason why the new Nexus has been built with 2GB of RAM compared to the previous one with how much?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

It's both together that made this mess as ugly as it is, though obviously my additions killed the thing :D

[MENTION=4167897]nikr123[/MENTION]

Well, I can understand that one may want not to use an app if he doesn't need to tweak anything but uV.

[MENTION=5559267]mus1mus[/MENTION]

It's a bit different in this case as most settings the user selects won't be written "in the rock" (CPU max clock, L2/cache OC and lowest freq uV being the exceptions), to let the user the ability to tweak them afterward (by modifying the /etc/settings.conf file).

The installer will create a list of things you selected, eventually renaming some system files at flash time, then on boot this list will be passed through a script (99glitch, present in init.d) to set everything as you asked.

An app would basically do the same, though you're right, the script is executed by the "system" itself so it'll save a bit of memory indeed.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
My battery life is amazing. When I bring my nexus to work with me and leave it in my laptop case, and it goes into deep sleep, it will stay at 100% for my entire eight hour shift. According to BBS, I lose about 2%/hour with normal use, and about 4.2%/hour with video and gaming involved. Most of the time, when I'm not using it for labor intensive things, I set the governor to interactive or intellidemand.
[Nexus 7 (2013) Original Android Development] superleeds27:
Still having a few issues random fc's. I changed back to stock L2 values

Will attach logcat!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Just a quick update on what's up on my side :

CAF based kernel is much stabler and globally closer to what you and I would expect now, though many things are acting up weirdly still. I did try a rebase but even stock source is giving me very strange results..

So instead of starting a war and going crazy I decided to update my "AOSP based kernel for CM"(Frankenbuild) to be compatible with CM11. It did fix color tweaking to begin with, but is also much smoother overall, and even got a slightly better Antutu score using the same settings as with the CAF based kernel. Logs are looking nice and I couldn't find any critical issue with it.

I'll clean a few things and make it public as an experiment for all of you dear users running CM11 or CAF based roms.

Note : I must admit I'll be very amused if you like this kernel more than the previous CAF based kernel.. That would be really Glitchy :cool:
[Nexus 7 (2013) Original Android Development] optimusG:
Just a question. At aroma installer I checked to install showp1984's hotplug driver but via trickster I can enable the intelliplug by faux also. Is that correct? 2 hotplug drivers simultaneously? Something I am missing.

Sent using Tapatalk
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4423342]optimusG[/MENTION]

In this kernel you have the choice between 3 hotplug drivers (stock Qualcomm's mpdecision, Showp1984's msm_mpdecision and Faux123's Intelli-plug). The thing is that stock is binary-based (a file executed on the system partition), while both Showp1984 and Faux123 drivers are kernel based. TricksterMod can't see stock binary anymore if you select one of the kernel-based drivers because the file is just renamed by the installer, but obviously it can see both of the kernel-based ones support in the kernel. So yes, if you want them to collide and get inconsistent results you can enable both by enabling for example intelli-plug after you did select msm_mpdecision in Aroma, or enabling it from TricksterMod (it's a button below led settings). Not recommended though, as you may have noticed :p

-----------------------------

[MENTION=5066986]SynnyG[/MENTION] [MENTION=5265482]yzweixy1029[/MENTION] [MENTION=4194466]Fr33L4nc3r[/MENTION] [MENTION=3615715]Mikes30000[/MENTION] and CAF users in general

So as promised, here's the new AOSP based kernel for CM11 based roms.

You can download it only from androtransfer for now, either from the N7-CAF or N7-AOSP4CM folders. The results of this testing may lead to a drop of CAF based kernel.

13/01/2014 :

**Glitchy release !**

- Updated AOSP4CM Frankenbuild to do some mass testing versus CAF base - Fixed color tweaking interface, buzzing seems gone, hotplugging weirdness looks fixed as well (...)

This new build is based on AOSP, though it is only compatible with CAF based roms (CM11 and variants).
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION] Wow, I haven't seen a better developer, every dev should be like you, hats off!
[Nexus 7 (2013) Original Android Development] yzweixy1029:
Wow,Great

I downloaded the latest kernel(N7-119 CM11.XP), flashed and tested, I played games and videos,No more buzzing!!!

Really really thank you. Cause the buzzing problem has bothered me for quite a long time(from the middle of December),and my roommates even jeered at me that I bought a "second hand" Nexus(They all use nexus5:mad:)

Whatever,i wanna say thank you again...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5265482]yzweixy1029[/MENTION]

Thank you for your patience. I wish I will be able to enhance your experience even further in the future !
[Nexus 7 (2013) Original Android Development] SynnyG:
You're the man !!!

I wish I could be a dev like you !!!

A big thanks for your work, after my job I will DL it and test it but with the other comments, I don't doubt about the quality of this version ;) I'm impatient !! ^^
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
A little update on top of the update before I'm gone sleeping for two or three hours (4:22AM..) !

Pushed a small update, this time for both AOSP and the new XP builds :

-----> Updated to r121 eXPeriment, updating Linux base from 3.4.60 to 3.4.76, also reduce stuttering on I/O heavy cases and enhance stability a bit (at the cost of a tiny impact on performances).

- Also update the regular AOSP kernel in sync (except for the Linux base update, only up to 3.4.63 for now, thanks to [MENTION=5209763]animania260[/MENTION] for his nice help).

Night guys ! Hope you'll like it.
[Nexus 7 (2013) Original Android Development] gravedigger76:
Hi guys

I'm seeing two versions today for N7-CAF

What is the difference and which one should I try with nightly CM11 ROM?

r121 or r119?

Thanks
[Nexus 7 (2013) Original Android Development] farenteria:
121
[Nexus 7 (2013) Original Android Development] gravedigger76:
[MENTION=3847629]Tk-Glitch[/MENTION]

Awesome kernel and thank you very much for all you're work!

Was just wondering maybe a dumb question....

Is there a way to maybe combine you're caf and non-caf kernels into one and somehow make it auto sense what to use?

I too use multiboot like you tried it..

My primary is CM11 nightlies..

I try other Roms from time to time as multiboot. Some are CM11 based and I can share kernel. Some are AOSP based and same kernel for CM does not work.

It would be fantastic if one kernel can rule them ALL :))

Thank you!
[Nexus 7 (2013) Original Android Development] cryostasis25:
Another update? Wow this kernel is really moving quickly. Gonna flash cm11 was trying cm 11 nightly on my device :p
[Nexus 7 (2013) Original Android Development] nikr123:
It would be great but I don't think it's gonna happen for now. There would have to go a lot of work in to making the drivers compatible and in the end I wouldn't say it was very much worth it. It's not the end of the world to spend 10 mb extra space to have both versions.
[Nexus 7 (2013) Original Android Development] SynnyG:
Good night mate ;)

I'll flash this asap. I've one thing that I don't understand about these new builds. In the description of the Frankenbuild, it's written that these builds are compatible with both AOSP and CAF Roms that's true ?

And in the changelog of the last two builds you have wrote that from now, the XP builds are based on AOSP but are only compatible with CAF based Roms like CM, how do you transform an AOSp kernel base into a CAF compatible ???

Edit: wow, incredible responsiveness Oo . For the moment the XP build is better than the CAF base and a lot ! I've set the same settings as the CAF base, I'll do some benchmark for testing the perf !

Edit 2: nice score in AnTuTu, 27000 :) same as CAF and even a little bigger (CPU of at 1.890, GPU of at 504 MHz, CPU gov is on demand, same as GPU, no uV)... Nice work, thank you :)
[Nexus 7 (2013) Original Android Development] SynnyG:
I've my N7 for about one month and I'm facing an issue. (I don't know if this is related to the kernel (I don't think as I've read comments of a lot of stock ROM and kernel user so sorry about the "out subject")) but I'm hearing a constant "chhhhhhhhhhhhhht" like a rain,that is covered at high volume...

Do you have this problem ?

One more time, sorry about the out of thread !
[Nexus 7 (2013) Original Android Development] cryostasis25:
^ try updating to newer kernel version
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
[MENTION=3847629]Tk-Glitch[/MENTION]

Thanks for the update. I'll try ASAP when I get home tonight :)

Almost feel guilty for bringing up the issue and having you work most of the night on it :p

If this is the constant noise at low volume, I think it's normal, I saw some sound expert on XDA saying that Google / Asus chose a cheap software volume implementation instead of an hardware one (to reduce the costs).

But this was like one month after the tablet was available, so maybe there are some workarounds since then. I'll be interested if there is any :good:
[Nexus 7 (2013) Original Android Development] animania260:
Stock ROM AOSP 121. With the Dalvik and Bionic Qualcomm enhancements. GPU at 504 with -25 UV. -50 UV on CPU.

Default Aroma settings, except all s2w stuff disabled. ?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] bland.life:
121 is nice!

Didn't have any lag or the honking/buzzer sound anymore.

All smooth.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Thanks for the kind words :)

About your idea, I think that would be possible though it does look like a large amount of work to do something like that. Just the detection of a CAF based rom versus AOSP based rom would be problematic I suppose. I'll take note of the idea, and you never know.. It may end up being done at some point ;)

There has been two Frankenbuilds. One AOSP based for CAF roms, and one CAF based for AOSP roms. So no, they aren't compatible with both AOSP and CAF roms in the end, you still need two different kernels. CAF based for AOSP has not been updated for 4.4.2 though, even if it works using dePRIMAtor patch.

About the "transformation" of an AOSP based kernel to be compatible with CAF based roms, well, I guess "Frankenbuilds" naming talks for itself :p

I feel like a mad scientist playing with this, trying some unnatural transplantations.. Ghiahaha !

I guess my users could see that as a Glitchy secret. Though most devs around will understand with the two previous sentences ;)

When I think it was supposed to be this way for a long time.. Well, at least it works now. If it ends up having many good reviews I'll just stop releasing CAF based kernels completely. That would be nice..

About your sound issue, this humming sound coming from the speaker is sadly an issue since N7 2013 came out. It's better since 4.4.1 though, it was really horrible on 4.3. Not related to my kernel btw, sorry.
[Nexus 7 (2013) Original Android Development] SynnyG:
Haha, you're crazy :P you killing me !

About stop releasing the CAF, I think it would be easier for you, it make less version to manage ! Also the XP builds works better so it would be crazy to continue the CAF version (I think but you're the chief ^^)

Thanks to all of you about the explanation ! The day when I bought my N7 I directly installed CM11 so I haven't tested 4.3 on this (I'm happy for this, I wanted to sell it immediately !). It's too bad that Google have done this choice, but even with this issue, we have a beast in our hand :)

You're not to be sorry, I'm happy for you ^^
[Nexus 7 (2013) Original Android Development] JayanWarden:
I am actually getting pretty decent Undervolts on this. Btw, I am still on 1.5GHZ max.

I havent maxed out everything to the nonplusultra on undervolts, but this is how far I can go until my tablet becomes unstable.

I am interested if anyone has tried undervolting too and what you have achieved in terms of undervolting.
[Nexus 7 (2013) Original Android Development] hello247:
Is it on top of undervolting gpu too. That's impressive.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Soooo on r118 I started to get some random reboots when pushing the device to its limits a little. Just installed r121 and with all the same settings it doesn't seem to still be experiencing the same problems, so I'm not sure what the issue was..
[Nexus 7 (2013) Original Android Development] lmulli:
Non Aroma Version?

Any chance you could consider a non aroma version of your kernel in order that I can use it with the Open Delta updater in Omnirom without the necessity of having to manually go through the options?

Thanks.
[Nexus 7 (2013) Original Android Development] vince2008:
WoW this kernel flies like a rocket, can't get any better than this. thanks.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Nothing stops you from getting the "glitch.zImage" from the zip and flash it as is. The problem is that it'll use stock settings for two things you can't tweak afterward : CPU max freq (that will be locked @ 1512 MHz) and L2/cache OC. If I could throw Aroma away and keep as much personalization as right now, I'd do it for sure.
[Nexus 7 (2013) Original Android Development] matcho13579:
What's your setup and which ROM are you using?

[MENTION=3847629]Tk-Glitch[/MENTION] I'm using your kernel and got some problems - see screenshot (it's a kernel wakelock, so I assume it's kernel-related)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3845051]matcho13579[/MENTION]

This is S2W/S2S/DT2W.
[Nexus 7 (2013) Original Android Development] matcho13579:
Oh, well, it's okay then :D Thanks
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
My pleasure ^^
[Nexus 7 (2013) Original Android Development] masri1987:
Which one is for Omni
[Nexus 7 (2013) Original Android Development] matcho13579:
It should be an AOSP version AFAIK
[Nexus 7 (2013) Original Android Development] masri1987:
Thank you, I wish this was available for the g2
[Nexus 7 (2013) Original Android Development] animania260:
Hopefully Tk-Glitch won't mind this, but I've been running a new build of Tk-Glitchs kernel for a day now. No issues. So I'm posting it.

We're up to 3.4.73 kernel version/updates. Plus Tk-Glitch committed some GPU fixes and a work queue fix.

****This is for AOSP ONLY!!!****

Updated to 3.4.73 (only 3 versions behind mainline! Lots of fixes)

edac: Don't try to cancel workqueue when it's never setup

msm: kgsl: Protect against a potential overflow in

msm: kgsl: avoid zero length scatterlist allocation

https://docs.google.com/file/d/0B22ZNBermHGrakNWekdfRVU2OWc/edit?usp=docslist_api

Just replaced the zimage in the zip. Everything is the same, just updated build.

Sorry Glitch! Just an update junkie. But I tested it for a full day, at least.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I don't mind, I'm just waiting until I'm able to fix a critical bug one of my testers did find on the CM compatible variant.
[Nexus 7 (2013) Original Android Development] animania260:
I figured you were waiting on something.

Do you want me to finish off the rest of the updates to 3.4.76 tonight, or do you just want to merge your already updated commits?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5209763]animania260[/MENTION]

3.4.73 to 3.4.76 commit is already done, not yet pushed. It should be done before I'm gone sleeping (in two to three hours).
[Nexus 7 (2013) Original Android Development] akaHardison:
Amazing combined all things kernel.Come from Bricked
[Nexus 7 (2013) Original Android Development] hakcenter:
Hey glitch, any reason not to add some of the other governors into the aroma installer ?

Intellidemand comes to mind.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4538670]hakcenter[/MENTION]

You can't select any CPU governor from Aroma atm, only GPU ones. That's why. Though if a few users would like to be able to select CPU gov I can add it.
[Nexus 7 (2013) Original Android Development] georgecarstoiu:
Thought I had found a bug with the front camera but it seems that I was wrong. Nevermind this post....
[Nexus 7 (2013) Original Android Development] hakcenter:
Certainly would like it ;)

Even io schedulers