yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2912951]commuterbox[/MENTION]

This is not a good idea. Better to just disable input-boost if you want sticking min freq in apps ;)

BTW as said already, min frequency setting in TricksterMod/CM should be ignored as it'll interfere with Aroma settings.

Plus it's basically useless to have a "sticking" min frequency, as it'll still drop to it when no input is detected (unless you're looking at your screen several minutes doing nothing while touching it.. Unlikely I'd say).
[Nexus 7 (2013) Original Android Development] commuterbox:
I agree thank you im just giving them an option. It does not bother me that my min freq in trickster is 918 coz I know in aroma I inputted 162 and it will also reflect on CPU stats.

I love your kernel, only kernel I have used for so long and never really had problems.

Sent from my Nexus 7 CM11
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
So, for anyone interested, here's an update on the random performance drop bugfixing on the CM compatible kernel..

A good one : I was able to fix it.

A bad one : It did resurrect the ugly buzzing bug present on the CM CAF base (at least I now know it's related to either GPU or memory allocation changes the CM team has made).

I'm not giving up yet though, and I still have a few ideas to hopefully fix it for good. Wish me good luck..

EDIT :

So all in all, I was finally able to fix it. Next release coming shortly ! ;)

Thanks [MENTION=842211]Grondinm[/MENTION] for the testing and moral support ! :D

EDIT 2 :

New release ! Welcome r130 :)

23/01/2014 - r130 :

- Faux123's LCD color control driver updated to Flo version (thanks to him to make it opensource), adding gamma control. (You'll need FauxClock to tweak it - color is still available from TricksterMod)

- Some GPU driver related bugfixes

- Implemented LoUIS API for cache maintenance operations

- Update base to Linux 3.4.77

- Revert some CAF updates (fixes some L2 corruption that could lead to random reboots / black screens)

- Battery life improvements

- Some cleaning

CM kernel only :

- Fixed color control

- Fixed random heavy GPU performance drop

- Changed memory allocation to be in line with CM

- Changed naming in Aroma to differentiate from "pure" AOSP

Hopefully we'll all forget CAF base in the end.. Enjoy !
[Nexus 7 (2013) Original Android Development] nokiagye:
Yea yes finally we heva gamma thanks..
[Nexus 7 (2013) Original Android Development] gautampw:
Can someone suggest a good colour preset? The one is Faux OP seem to be for Nexus 4
[Nexus 7 (2013) Original Android Development] nokiagye:
On gamma the default is 100 I have it 160 on all but if it's very black for you 140 is good

Be careful every time you set it again first you must press the stock button close the screen and open and after you can set a new.

---------- Post added at 01:16 PM ---------- Previous post was at 12:56 PM ----------

Tk

Is there any way to increase the touch sensitivity?
[Nexus 7 (2013) Original Android Development] NYCHitman1:
Hey Tk - just wanted to say that I'm LOVING your Glitch kernel on my DU ROM. Great work, broheim. :good:
[Nexus 7 (2013) Original Android Development] bmccoy11:
There's a horrible... well... glitch..., whenever I'm casually surfing the web and I type something in, it sometimes randomly locks up and a black bar moves from the top to the bottom of the screen. However, once the black bar is gone, it usually just force closes the app and continues on. I have tested on Chrome and Dolphin browser's, Chrome was definitely the worst. I'm not sure if it's this kernel that's causing it, it could be Cyanogenmod, too. I'm running the latest nightly, at the time of this post. The OS didn't do this before kernel version r130. My keyboard is Swiftkey, and my main browser is Chrome, but I'm using Dolphin browser until this gets fixed.
[Nexus 7 (2013) Original Android Development] bsw11:
Can someone give me a link to the faux app needed to tweak the colors etc? The one in the play store says it's for the n4. Is that the one to use?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=332610]bsw11[/MENTION]

This is the one : https://play.google.com/store/apps/details?id=com.teamkang.fauxclock

[MENTION=5637619]bmccoy11[/MENTION]

By any chance, did you overclock L2/cache ? If you didn't, I'd like your last_kmsg if possible. Thank you :)

(And if you did, try to lower it to the next step)
[Nexus 7 (2013) Original Android Development] bmccoy11:
I actually did overclock the L2

After a bit of looking, here's what's happening when it freezes, I can't copy and paste very much because it scrolls way too fast for ADB to handle it. I know that this is the kernel's fault, now.:

http://pastebin.com/hyiyH2Ew

Edit: Is it a problem with msm_mpdecision???
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5637619]bmccoy11[/MENTION]

That's perfect. Thanks man.

Looks like the fight isn't over yet.. I'll do my best to fix it quick.

This is the delicate part that did bring back the buzzing crap during my bugfixing attempts. I hate it :D
[Nexus 7 (2013) Original Android Development] bmccoy11:
Thanks. If anyone wanted a GIF of the crash, you can find it here :laugh:.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5637619]bmccoy11[/MENTION]

Ahah nice gif :D

No, nothing to do with msm_mpdecision. It has to do with GPU driver memory handling changes in CM. Fixing the slowdown bug generated this one. Doesn't look as bad though. At least this one shows up in logs. Strange that I was unable to trigger it.. Maybe time to get a recent nightly !

I'd like to be able to push the update today (6:30AM here). Will do my best.
[Nexus 7 (2013) Original Android Development] bmccoy11:
Thanks, hopefully this can be fixed sometime in the next day or two. I don't want to have to use another kernel! :(

For now, I'll just stay away from browsing the web on my Nexus.
[Nexus 7 (2013) Original Android Development] 3dawg:
After flashing this kernel today, most of my data just disappeared from the device. It's as if I did a factory reset but my apps are still there. Why did this happen?

Also, off topic but does anyone know if ART runtime survives a cm nightly flash? It seems to have reset to dalvik after flashing the latest nightly. Or is that related to the weird data loss I got from Glitch kernel?
[Nexus 7 (2013) Original Android Development] mus1mus:
Some consistency on 130. :laugh: :laugh: :laugh:

Great work TK..
[Nexus 7 (2013) Original Android Development] commuterbox:
Awesome update as usual. Yikes the buzzing video issue is gone. Thank you so much for your hard work sir. Well done. I am amazed of what this kernel have done to my nexus 7.

Sent from my Nexus 7 CM11
[Nexus 7 (2013) Original Android Development] 3dawg:
I can confirm after reflashing glitch kernel that it does indeed seem to be causing the runtime to revert to dalvik. It doesn't happen every time but this is the second time it's done it today. Anyone else experience this?
[Nexus 7 (2013) Original Android Development] melander:
[MENTION=3847629]Tk-Glitch[/MENTION]

flashed the updated kervel r130 for AOSP, running cleanrom.

i've set battery saver to 93% in aroma

still reaches a 100%, unit is charged while it is ON.

tried it twice and always goes to a 100%.
[Nexus 7 (2013) Original Android Development] HTC Venom:
It thinks that once it reached 92‰ it reached the upper limit of the battery and. All ROMs display the Max limit with 100% , so that's totally Norma l, don't be afraid
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3087734]3dawg[/MENTION]

Nothing to do with the kernel itself, but maybe Aroma malfunction with your recovery or just unstable settings caused your data partition to be corrupted/wiped. The installer doesn't write anything on /data btw.

I'm running ART as well on CM nightlies and never encountered such issue as data loss or VM reverting to Dalvik.. What recovery are you using ?

[MENTION=4412573]melander[/MENTION]

Could you please make sure you have /etc/init.d/99glitch.sh file as well as /etc/settings.conf with your correct BLE setting in it ?

If you are both running the latest "standard" TWRP recovery, it seems it's acting up with Aroma.. Hopefully the overhaul will make things smooth.
[Nexus 7 (2013) Original Android Development] melander:
with previous kernel version it did not reach 100% with the same battery saver settings

[MENTION=3847629]Tk-Glitch[/MENTION]

BLE setting is "2" checked settings.conf.

im using twrp 2.6.3.0
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4412573]melander[/MENTION]

Could you send me your /proc/last_kmsg file please ? Thank you.
[Nexus 7 (2013) Original Android Development] hakcenter:
I have no idea what people are talking about losing data or art. I've been flashing this kernel right over even cyandelta updates for months without issues.
[Nexus 7 (2013) Original Android Development] 3dawg:
Actually, the problem has occured both times when the settings I chose in Aroma caused bootloops on the CM logo. I guess I shouldn't choose those settings then.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3087734]3dawg[/MENTION]

It confirms what I was thinking. The settings you did select were unstable (too high OC or too high uV), breaking boot and corrupting some random data on boot attempt. Try with some more conservative settings, and if you want to push your hardware, do it step by step, slowly, and testing for stability at each increment :)
[Nexus 7 (2013) Original Android Development] 3dawg:
Thanks for the tips. This kernel makes my N7 seriously fly. Incredibly good performance so thank you :D Now if only there was a version for the Nexus 5 or 4 :p

Custom Kernel development is all but dead for CM on those devices :(
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
My pleasure. I'm glad you like it as it'll just get better and better in next planned updates.

About Nexus 5 support, Grondinm did start a project floating around on youcaring.com. You may want to search for his post if you're interested to participate. It doesn't look good as it is (it has basically no visibility, so obviously it feels dead somewhat), but I suppose that if some users are able to share it, it would work. I don't think adding a link in OP would respect XDA rules, but maybe one user could make a thread for that, I don't know..

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

Note to all CM users : the "black caterpillar bug" is completely gone, along with a few other stalling/stuttering problems. Global performances are also up. I think it's now okay to drop CAF base completely and forget about it until CM team breaks more stuff :D

Revision 132 is up on Androtransfer, and soon on XDA and Dev-Host mirrors. This is THE build to get for CM users.

25/01/2014 - r132 :

Performance and stability improvements :

- Enhanced memory management

- Lower CPU overhead

- Improved I/O speed in many cases

- Improved ondemand governor behavior

- Fix a memory leak

- Fix some msm_bus bugs

- Fix a false error report in Aroma log

CM kernel only :

- Fixed the "black caterpillar" bug

- Improved GPU performance consistency
[Nexus 7 (2013) Original Android Development] Medel-Silver:
Hello Tk!!! I see new version on AOSP, but it say cm11... Why?

Thanks in advance;)

Edit: I say nothing... Waiting for uploading finish...

Thanks!!!

Edit2: I have it!!! Flashing time!!! New kernel & rom (purity):D
[Nexus 7 (2013) Original Android Development] fulcsa:
Hi,

Thank you for supporting our device, you did a lot for users who uses CM. I prefer CM because its more customizable than the pure AOSP, so I used CM11 for a while, but it wasn't too stable, so i switched back to the stable CM 10.2. Will you make/compile this or any next kernel version for CM 10.2? I know that CM 10.2 is not the newest version, but it is the last stable and it works fine.

Thanks again, I think we all appreciate your work. :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5074163]fulcsa[/MENTION]

I will most likely release a last cm-10.2 kernel when I'll be done changing how the Aroma installer works (next release, unless a new strange bug shows up). Depending on how much work it represents, it may take a bit more time than for the regular AOSP/CM11 releases though. I'll do my best.
[Nexus 7 (2013) Original Android Development] evilSuRGe:
r130 has been great these past couple of days. Gonna flash r132 now
[Nexus 7 (2013) Original Android Development] koller1994:
I am using the CAF version. Please let me know that how can I set the values for my device to get great performance as well as good battery life? I dont know how to set these value so I just go with default? Is it ok?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5667926]koller1994[/MENTION]

The "default" settings I've set in Aroma are supposedly a good balance between performance and battery life, so yes it's okay :)
[Nexus 7 (2013) Original Android Development] nokiagye:
The tab now flying thanks
[Nexus 7 (2013) Original Android Development] Lazy79:
Indeed. Fast :) I've glitch'ed my tab. I guess it's becoming a new verb. ;)
[Nexus 7 (2013) Original Android Development] nokiagye:
162-1700 -25v 450gpu all other stock
[Nexus 7 (2013) Original Android Development] nokiagye:
And this photos is with 130

With 132 is much better
[Nexus 7 (2013) Original Android Development] slyr114:
In having a small issue, for some reason my min cpu freq seems locked at 9800 or something like that and when i set it to 384 or similar it does not save, if i exit the kernel program and open it again it reverts back to 9800? Anyone have any ideas?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4290569]slyr114[/MENTION]

You probably meant 918 MHz. It's a normal behavior. If you want to understand better, the answer is in the FAQ in OP :)
[Nexus 7 (2013) Original Android Development] slyr114:
Haha completely missed that somehow, thanks!
[Nexus 7 (2013) Original Android Development] matcho13579:
Which ROM are you using?
[Nexus 7 (2013) Original Android Development] nokiagye:
Slim
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4290569]slyr114[/MENTION]

You're welcome :)
[Nexus 7 (2013) Original Android Development] vince2008:
I was comparing between tk-glitch 103 vs 132 mind blowing performance, CPU @ 1998 MHz, stock ROM. 103 got top results but I'm sticking with 132 due to recent tweaks. Thanks
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
That's a 1.5% difference in score btw. :D

You guys are becoming as extremist as I am !
[Nexus 7 (2013) Original Android Development] ak:
@ Tk-Glitch

I'm following this thread from a long time ago ... Very good people for a great developer ....

I have one question:

Have you try to merge faux gamma into caf cm source?

For me kernel always bootloop.

Thank a lot.

Ak

AK&4&7
[Nexus 7 (2013) Original Android Development] marsaltito:
Thx Tk-Glitch, nice one with latest cm11 ,your work gives hope to CM .

Just did install:

TWRP 2.6.3.0

-latest CM11 (25.01.2014)

-kk gapps

-Glitch kernel CM11

Everything perfect ,after aroma boot back to twrp .

Thx again! ?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3685904]ak[/MENTION]

Thank you good sir.

I have seen a few thanks from you and was patiently waiting for more :)

Yes, I did try and it did bootloop with just color control (before Faux released gamma control) so I was forced to revert it. I was planning to debug it but another way was more tempting, as you probably know. It obviously has something to do with some GPU or display driver changes in the CAF source, though I don't know exactly what's wrong.
[Nexus 7 (2013) Original Android Development] ak:
I have pm faux , but he doesn't have time for investigate. The only comment was: "you have to check into fb drivers" but I don't have for now a solution.

AK&4&7
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3685904]ak[/MENTION]

PM'd you ;)
[Nexus 7 (2013) Original Android Development] koller1994:
It is a great kernel. After flashing latest version of CAF, the battery life is really awesome, tablet idle (approximately 8h) loses only 1% of battery. Thanks so much for doing this great kernel :D

Sr: I am Vietnamese so my English isnot great :D
[Nexus 7 (2013) Original Android Development] BAleR:
132 running great on Slimkat2.4

Cpu's @1.7Ghz Undervolt ~ 800

Gpu @ 450 undervolted 50mv

Faux Inteliplug

Cache default 1.2

Deadline

No s2w

No dt2w

Disabled magnet on/off

And battery life is the best ive seen yet! Thank you for all your hard work. Its devs like you that make me proud to own an android device.
[Nexus 7 (2013) Original Android Development] ak:
[MENTION=3847629]Tk-Glitch[/MENTION]:

first implementation for CAF kernel aka Kcal:

https://github.com/anarkia1976/AK-xGenesis-Flo/commit/f52b91e39104dccff6c2d6d636bc3a608005fc46

:D
[Nexus 7 (2013) Original Android Development] Batfink33:
A quick question. I know that there's always a danger in OCing but I noticed on the Elemental kernel that OCing the GPU past 504 was not recommend. My N7 seems to run fine at higher GPU levels with Glitch. Is there any danger in OCing the GPU higher than 504?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5211228]Batfink33[/MENTION]

If the heat is under control, it's not a problem. GPU uV is you friend here if you think the heat is a bit on the high side.
[Nexus 7 (2013) Original Android Development] Batfink33:
Ahhhhh OK, thanks. Haven't had any problems with heat and OC.
[Nexus 7 (2013) Original Android Development] optimusG:
For me the tablet is already fast as hell so it runs at stock freqs (cpu: 1,5ghz - gpu: 400mhz) with a little bit of u/volting. :good:

Would you guys have enabled the option of force 2d rendering with GPU under developer options?
[Nexus 7 (2013) Original Android Development] NYCHitman1:
I do.
[Nexus 7 (2013) Original Android Development] melander:
Thanks for the responsr, pm sent.

It seems there is a new rev, flahing time again, hehe

~~~~~~~~~~~~~~~~~~~~~~`~~~~~~~~~~~~

Currenty on 132, battery saver working again, testing performance now,

Seems battery life is much better also

sent using a "Glitch'd" Nexus7
[Nexus 7 (2013) Original Android Development] cryostasis25:
^ agree with the battery life.. what i like most i have underclocked both gpu and cpu to the lowest and it still works have not experience any lags or stutterin. Currently on cm11 nightlies

Sent from my very own T.A.R.D.I.S
[Nexus 7 (2013) Original Android Development] optimusG:
What is battery saver? The eco mode?

Sent using Tapatalk
[Nexus 7 (2013) Original Android Development] nokiagye:
Yes

---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------

You can do 3 thinks undervolt CPU GPU and set the max frequency s low
[Nexus 7 (2013) Original Android Development] Batfink33:
Just like to push the boundaries a little. I find it slightly laggy with stock values also.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
He was talking about "BLE" (Battery Life Extender) function.
[Nexus 7 (2013) Original Android Development] optimusG:
Is eco mode working properly for our device? Coz I read it has to do with 2 core optimization.

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

Eco mode will disable the use of cores 2 and 3, yes. It may require the use of intelli-plug hotplug driver btw. I know it does work with it, but not sure about msm_mpdecision.
[Nexus 7 (2013) Original Android Development] hello247:
Anyone had success changing gamna settings with faux clock?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Don't forget to turn off/on the screen after applying settings.
[Nexus 7 (2013) Original Android Development] hello247:
Sorry I meant if anyone had good values to try out.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Oh ! Sorry then :D

If you want some more contrasted/profound colors, you can try 120 or even 130 on each channels.
[Nexus 7 (2013) Original Android Development] tibere86:
Using Trickster, set colors to 120 or 130/250? I'll try this when I get home.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
TricksterMod can't tweak gamma for now on our device as far as I know, only colors.

And I don't have good color settings to give for now as I didn't experiment much with it.
[Nexus 7 (2013) Original Android Development] matcho13579:
If I got it right, eco disables 2 CPU cores completely?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Basically, yes.
[Nexus 7 (2013) Original Android Development] szale9001:
Hey [MENTION=3847629]Tk-Glitch[/MENTION] , do you think you could add an adjustable Max Screen Off Freq parameter? I think flar has one implemented as an aroma option in the elementalX kernel and I'd love to be able to limit the CPU when the screen is off on this kernel.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I don't see the point myself (maybe because I don't have any wakelock), but sure, I can add it.
[Nexus 7 (2013) Original Android Development] szale9001:
Thanks man. Yea, I have most of my wakelocks under control but the one that kills me the most is Netflix. I use it with Chromecast and for whatever reason, while Netflix is playing on Chromecast it wakelocks my tablet until it is done. Apparently it is a known problem (and a stupid one).
[Nexus 7 (2013) Original Android Development] SupWiz17:
Does it run your tablet at max frequency? I use my tablet to play Netflix on my chromecast and I have never looked for a wake lock because I just figured any better drain is better then what I would drain if I was watching it on the screen. Do you think it will cause he playback to stutter if you capped the frequency?
[Nexus 7 (2013) Original Android Development] szale9001:
I don't. As far as I know, the Netflix app is acting as a remote of sorts to the Chromecast. The tablet isn't streaming it to the Chromecast, which is why the Wakelock on the tablet makes no sense and is more than likely bad coding on Netflix's part. Also, capping to 700 or 1.0Ghz shouldn't cause any stuttering as they are pretty reasonable frequencies.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's not included (yet) in the installer, so you'll need to flash it separately.

About your 3DM score, it seems a bit low for the settings used, though it may be in the margin of error.

Try to use 1.89GHz CPU and see if the score moves at all. If it doesn't, your CPU is most likely slightly temperature limited.

Using GPU uV is a great way to lower heat output in games/graphic benchmarks by the way(better than CPU uV).
[Nexus 7 (2013) Original Android Development] PlasmaPump:
Thanks... been looking for an update for a while now. CM11 or more accurately AOSP 4.4.x has nothing new I need and 4.3 is perfectly stable for me. :)
[Nexus 7 (2013) Original Android Development] ikaster17:
listen can anyone let me know, im running Slimkat build 2.5 RC1 and 4.4.2 kitkat if people dont understand :P can i use this kernel with Slimkat or it will have problems? and which one should i use with slimkat AOSP or CAF ?? :S
[Nexus 7 (2013) Original Android Development] nokiagye:
Aosp and you won't have problems I am to on rc1
[Nexus 7 (2013) Original Android Development] ikaster17:
Removed
[Nexus 7 (2013) Original Android Development] nokiagye:
Now with the gamma is the best
[Nexus 7 (2013) Original Android Development] tibere86:
Decided to be adventurous last night and flash the latest CM11 nightly (20140129) + Glitchy CM version. Video playback is laggy as all heck. I'm using the same Glitchy settings I had while running RastaKat + Glitchy AOSP version. Is the video playback issue a CM11 issue?

EDIT: Looks like there's a memory/RAM issue in latest nightly. Read about it in the CM11 Nexus 5 thread.
[Nexus 7 (2013) Original Android Development] HTC Venom:
With CM11 official nightlies you can only use CAF version of the kernel