yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] ikaster17:
Great

i would really like to thank tk-glitch, the kernel is great... Running Slimkat Rc1 and the kernel is just Sick <3 loving the performance and would really ask the people to use this kernel if they are curious to try it out :D

Good Deep Sleep and almost no wakelocks (: will test more and give my reviews....
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
He is using the right kernel, else it wouldn't even boot correctly. My "CM" kernel is for CAF only roms, I thought it was clear enough :p

I'm not experiencing such issue on an older nightly, so you may be right.
[Nexus 7 (2013) Original Android Development] abc123pro:
Have you tried using the app greenify to hibernate Netflix? I did that and it stopped the problem for me (also use Chromecast constantly).

Also thanks so much glitch, been looking around this devices page since I got the deb the other day and this looks like the one to try. I decided to root the stock rom, but gonna flash this kernel on it now!!

---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------

Update: what is caf? Noob I know, but I tried searching around and can't find a definite answer.

---------- Post added at 03:12 AM ---------- Previous post was at 03:05 AM ----------

Update 2: I believe non caf = stock which is compatible with the aosp version of this kernel? Okay trying it out :D
[Nexus 7 (2013) Original Android Development] nikr123:
In short. Use caf kernel for cm based ROMs and aosp (most common) on everything else. Download both if unsure. Them if it doesn't boot you flash the other...
[Nexus 7 (2013) Original Android Development] abc123pro:
Thanks man. Booted just now with the aosp :D now to test the uv limits of this baby.. Hope i got lucky with a FAST device
[Nexus 7 (2013) Original Android Development] szale9001:
Yea, I use Greenify on Netflix. Still wakelocks as long as it plays though. However, it did reduce the wakelock time. I have just accepted it as a part of Netflix's criminally bad coding charm, and I figured a max frequency would help curb the battery loss a bit while the screen is off.
[Nexus 7 (2013) Original Android Development] tibere86:
Thanks for the reply :) I plan to do a clean wipe and install of M2 this weekend.
[Nexus 7 (2013) Original Android Development] valence23e:
Howcis the battery life of your n7 when using this kernel? Im at stock and gets up to 5 hrs SOT. Planning to switch kernel. Thanks guys
[Nexus 7 (2013) Original Android Development] jeremyandroid:


---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------
[Nexus 7 (2013) Original Android Development] pingaan:
Does the kernel run on both 4.3 and 4.4?
[Nexus 7 (2013) Original Android Development] chrisgestapo:
As far as I know, last versions that support 4.3:

AOSP: r57

CAF: r86
[Nexus 7 (2013) Original Android Development] pingaan:
Great, cheers! Anyone who can 2nd this?
[Nexus 7 (2013) Original Android Development] 3dawg:
This kernel makes my N7 absolutely FLY. Honestly, it's been so fast these past couple of weeks that it actually makes my N5 feel slow :/ We need Glitch on Nexus 5!

I'm OC'ed to 2Ghz. Why does it feel so much faster than my N5 @2.3Ghz? N7 with Glitch also beats my N5 on sunspider, it's ridiculous how much faster this kernel makes it.
[Nexus 7 (2013) Original Android Development] NYCHitman1:
Benchmarks mean nothing in real world performance. Truth be told, I do love Tk's work. It has been a revelation on our beloved Flo. However, when I see some users clocking past 2GHz - I can't help but think that people have no idea what they are actually doing. It runs just as smooth on 1.7GHz as it does on 2GHz. Options are great, but I think people need to educate themselves more about the aforementioned options before jumping to conclusions about what xyz does.
[Nexus 7 (2013) Original Android Development] 3dawg:
Somewhat unrelated response but thanks anyway.

I don't clock past 2Ghz. It doesn't run just as smooth on 1.7Ghz. Not anecdotally anyway, 2Ghz is the point where it stops making a difference on my device; no stutter or slowdown anyway. Nevermind only smoothness, speed is important to me too. It makes the N5 feel slow. Think about that for a second, an S4 Pro (closer to s600 but w/e) making an s800 feel slow.

They have the same resolution screen so that's not the answer here. What is it? Why is it so much faster, despite being clocked lower and running on an older architecture? The governor is the same as far as I can tell. Probably some kernel enhancements/optimisations somewhere.

Last I heard there was a kang project to get Glitch on N5 but I think it has been abandoned.
[Nexus 7 (2013) Original Android Development] nokiagye:
Same here when I bye the n7 it was slower much slower than my moded n4 but with this kernel the 7 is classes faster of n4
[Nexus 7 (2013) Original Android Development] NYCHitman1:
It's not faster than the N5 and you've gotta be taking some kind of drug(s) to think that it is. In fact, the two don't even remotely compare in terms of overall performance/speed.

For the record, the post wasn't unrelated. You're just a little bent out of shape because you were wrong. It's ok though. It happens to the best of us sometimes. Whatever you want to believe is fine with me, but you shouldn't go spreading false information.
[Nexus 7 (2013) Original Android Development] 3dawg:
Right, don't go throwing insults now because I have differing opinions. To claim they don't even remotely compare in speed is also a complete farce - "in fact" suggests you have some evidence to provide, care to share? Even at their stock speeds they compare in performance/speed. There is arguably less than a generational gap between the two.

I've already had one person echoing my finding that the N7 with Glitch is on another level of snappy/fast, even edging out the Nexus 5 at stock.

After some quick rough tests, my N7 is clearly opening all apps quicker than my N5 does (approx 0.25-0.5s depending on the app), it loads web pages as quickly as, or quicker than the N5 and finally, it switches between apps quicker by a similar margin as was observed when opening apps.

EDIT: I just saw your edit on your previous post. Please, for the sake of the XDA community; grow up or leave. Stop acting like a child, disagreeing with people on baseless terms. For me to have been "wrong" (about what? an opinion?), you would have had to refute what I was saying with facts, not your own opinion.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4795439]nokiagye[/MENTION] [MENTION=3087734]3dawg[/MENTION] [MENTION=2489052]NYCHitman1[/MENTION]

Well, our main bottlenecks here on the pure N7 versus N5 comparison in terms of performance are the CPU clock and the bus/RAM speed. Our Adreno 320 GPUs are theoretically as fast as the S800's Adreno 330 once overclocked to 600 MHz (a frequency many should be able to use, even with a bit of undervolting to lower heat output).

Adreno 330 contains 128 АLU (32 x Vec4) :

32 x 9 (2 Vec4+1) x 0.450(MHz) = 129.6 GFLOPS @ 450 MHz

Our Adreno 320 contains 96 АLU (24 ALU x Vec4) - Just like the S600 version

24 x 9 x 0.400 = 86.4 GFLOPS @ 400 MHz

So at 600 MHz :

24 x 9 x 0.600 = 129.6 GFLOPS - Same as the Adreno 330

The "true" S4 Pro version of the Adreno 320 (found in the Nexus 4) has only 64 ALU (16 ALU x Vec4) = 57.6 GFLOPS @ 400 MHz - So it's obviously slower than what we have.

About the CPU, our Krait 300 cores performance per clock is closer to the Krait 400 cores found in the S800 than to the Krait 200 from "true" S4Pro (Nexus 4), but our bus speed is much lower, bottlenecking both GPU and CPU performance. Overclocking the bus (L2) alleviates the bottleneck though S800 speeds still aren't attainable. However, S800 suffers more from heat than our S4Pro/S600, so in some high load cases our devices may end faster, especially if GPU, CPU and bus are OC'd.

I can confirm that.
[Nexus 7 (2013) Original Android Development] 3dawg:
Great breakdown, thanks for that. This is all in theory of course and assuming raw performance leads to linear gains/perceivable gains in performance/speed. Whatever you're doing with this kernel, keep it up because it works wonders. :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3087734]3dawg[/MENTION]

Indeed. And kernel / drivers / toolchain optimizations aren't taken into account here, while they can give a nice "palpable" boost.

Thanks man :)
[Nexus 7 (2013) Original Android Development] pingaan:
I installed r86 on 4.3 and it works just fine.. All except the WiFi! I don't suppose anyone have a "dePRIMAtor.zip" working for 4.3 lying around? That should do the trick, right?
[Nexus 7 (2013) Original Android Development] BAleR:
Tk, i see your O/C'ed to 2Ghz and 625Mhz, so how much are you undervolting your cpu/gpu? Im only at 1.7Ghz and gpu at 400Mhz, but U/V cpu at 800 and gpu down 50. But i know i can overclock much higher
[Nexus 7 (2013) Original Android Development] WhiteWidows:
My first time using this kernel. I'm running cm11 I know caf is needed but which one? the standard or optimized. I also have art enabled. will that negate the optimizations on the delvik version?
[Nexus 7 (2013) Original Android Development] vince2008:
Tk-glitch kernel awesomeness results.....CPU @1.998, GPU @ 600mhz
[Nexus 7 (2013) Original Android Development] pingaan:
I've been browsing the thread and I can see that this issue was fixed in r62, or something. Is this correct? Any ideas to why my WiFi won't turn on then?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Did you grab the CM10.2 version for your CM10.2 based rom ? (http://androtransfer.com/get.php?p=TkGlitch/N7-OLDER-BUILDS/Glitch-N7-r86-CM10.2.zip)

It should work. If you have the CM11 version (or if you're running CM11 with the CM10.2 kernel installed), wifi won't work.

Running CM11, you don't need to use optimized dalvik if you're on ART as it just won't have ANY effect (good or bad) until you switch back to DalvikVM. On AOSP though, optimized bionic will give a boost even on ART (CM bionic is optimized already).

Looks like I'm lucky with my PVS3 chip (supposedly not that good batch) :p

I'm using -100mV uV on all freqs (and 700mV on 162MHz step), as well as -100mV on the GPU for 600MHz or -50mV for 627MHz (running 600 these days considering the nice uV).
[Nexus 7 (2013) Original Android Development] pingaan:
I didn't, I could try though but I'm running stock, no custom rom. I think I did pick the right one, at least according to the other guys who helped me a few pages back. Do you think I have to go further back than r86?
[Nexus 7 (2013) Original Android Development] koller1994:
when do we have the new update for the kernel ?
[Nexus 7 (2013) Original Android Development] spartacus279:
Amazing benchmark, what ROM where you using? I'm afraid of oc higher than 1.8 due to heating , did you have any problems ?
[Nexus 7 (2013) Original Android Development] nokiagye:
A mistery think the batt temp won't go up of 29 but the CPU temp go 60 easy
[Nexus 7 (2013) Original Android Development] poondog:
Put it in the microwave should work
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Oh you're on stock 4.3 then ? This would be the one you need : http://androtransfer.com/get.php?p=TkGlitch/N7-AOSP/Glitch-N7-r57.zip

For AOSP, anything past r60 is 4.4 only (the last public build in this range was r57).

I'll try to see if making a "PRIMAtor" patch would let a user run a recent kernel on stock 4.3.
[Nexus 7 (2013) Original Android Development] nokiagye:
You misunderstood me..I mean why the CPU temp goes so hi..

On my n4 if the batt is 35 the CPU will be 50
[Nexus 7 (2013) Original Android Development] poondog:
Try an oven then

Might be because the n4 is smaller, parts are closer together so CPU heat well heat everything. N7 is much bigger so it disperses heat better, you can see sgs4 vs n7 stock thermal graphs and you'll see

CPU goes higher because of your thermal settings and clocks + cpu activity
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Larger device, larger battery, and similar sized SoC. The battery will obviously heat far less as it's larger (easier to dissipate heat) for pretty much the same power consumption. It's just physics. The CPU is not the same as the Nexus 4 and it does indeed heat up more (like a S600 in fact.. My S600 SGS4 CPU is hotter than my N7's thanks to the poor dissipation in such a "small" form factor). The S800 heats up even more, so does the Tegra 4.

Nothing wrong here - at least for now. Hopefully new ARM CPUs will be cooler.

It shouldn't be asked. I'll answer this time though. The next update will be later today ;)
[Nexus 7 (2013) Original Android Development] Compwxr:
Great news [MENTION=3847629]Tk-Glitch[/MENTION], ready to test the awesomness of your new upcoming kernel ;)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
r140 update is out ! Aroma overhaul with many new features.. Enjoy !

It's HIGHLY RECOMMENDED to make a full installation first, so the new scripts and new Aroma sets everything the right way. Else you'll get stock settings applied.

You'll then be able to restore your preferences from SDcard to other roms or after a system update/wipe.

07/02/2014 - r140 :

- Update to Linux 3.4.79

- Switch to XZ compression

- Add kernel mode NEON support as well as NEON accelerated AES & XOR implementations

- Fix CPU load miscalculation

- jbd2 and ext4 optimizations

- Add max screen off frequency support - Thanks to Flar2 (if disabled in Aroma, changing frequency in apps won't have any effect)

- Add UKSM 0.1.2.2 support

- Add dynamic management of dirty page writebacks

- Enable Wiimote HID support

- Enable USB printer support

- Bugfixes

Aroma installer overhaul :

- Reworked installation process to be clearer and more customizable

- Added an automatic backup of your settings to the root of your internal SDcard

- Added a restoration mode to get your settings from internal SDcard backup back on any rom (cross-compatible with Glitch kernel variants)

- Renamed /system/etc/settings.conf to glitch-settings.conf to make it more obviously glitchy

- Removed the need to set CPU OC, L2/cache OC and auto-uV again when keeping previous settings (now reading it from your settings at flash time. Note : editing this part in /system/etc/glitch-settings.conf requires a reflash using the "already glitched" option)

- Added Qualcomm optimized Dalvik/Bionic libraries into the installer (bionic only on CM variant) so you can install/restore them with the kernel

- Added I/O scheduler, CPU governor, read-ahead buffer size, fast charge, max screen off frequency and maximum multi-core power savings to available settings

- Fixed how the min CPU clock is applied to make it more robust and work better with governors

- Fixed how the min CPU freq uV is applied to make it work independently of the min freq (by subtracting the uV amount to the original voltage instead of forcing plain values) - Also, make it capable of setting uV for all freqs for future use.

- Changed the auto-uV menu to reflect the internal changes

- Fixed some permissions issues

- Added hotplug driver check so it's possible to restore it as well from settings without interference

- Change theme
[Nexus 7 (2013) Original Android Development] koller1994:
I have the problem that when I go with the default and then click install, it said " no such logs and directory" and installation failed.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
What do you mean by "default" ? Did you untick everything or did you click next til the end ?
[Nexus 7 (2013) Original Android Development] Compwxr:
Well, just installed the kernel and tested a bit, all I can say is that it's working flawless and great!

The new aroma features are great and very userfriendly ui :)

Keep on great work with our's Nexus7 2gen [MENTION=3847629]Tk-Glitch[/MENTION], your work is just awesome in all ways!

Sent from my buttery smoth Nexus powered by TK-Glitch Nitro-powered Kernel!!! :P
[Nexus 7 (2013) Original Android Development] xI mEzMeRiZe Ix:
Nice to see the thread title get cleaned up too. No more 1337z hacker stuff. Can't wait to try the new build.
[Nexus 7 (2013) Original Android Development] crazyyyk:
I installed the new kernel, and selected some settings. But after reboot, in Trickster MOD (apply settings on boot is disabled) I saw absolutely different settings. Is it normal? What should I believe to?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
1 - What was different ?

2 - Did you let your device boot completely before opening TricksterMod (wait ~1 minute) ?

You can check your settings in the /system/etc/glitch-settings.conf file to make sure it's all good.
[Nexus 7 (2013) Original Android Development] crazyyyk:
What I selected:

SWEEP2WAKE=0

PWR_TOGGLE=0

SHORTSWEEP=0

DT2WAKE=0

S2S_ORIENTATION=0

LID=1

OTGCM=0

##### Input-booster Settings ######

# 1 to enable Input-boost

# 0 to disable Input-boost

INPUTBOOST=0

GFSLEEPERS=1

THERM=1

##### Max GPU Clock #####

# 1 320 MHz

# 2 400 MHz

# 3 450 MHz

# 4 504 MHz

# 5 545 MHz

# 6 600 MHz

# 7 627 MHz

GPU_OC=1

##### GPU Governor #####

# 1 Ondemand (default)

# 2 Interactive

# 3 Performance

GPU_GOV=1

GPU_UV=7

##### CPU governor #####

# 1 ondemand (stock)

# 2 interactive

# 3 intellidemand

# 4 smartmax

CPU_GOV=3

IOSCHED=2

READAHEAD=2

FAST_CHARGE=0

SCROFF=4

MC_POWERSAVE=1

BLE=1

MAXF_CPU0=1512

MAXF_CPU1=1512

MAXF_CPU2=1512

MAXF_CPU3=1512

MINF=384

UV_LEVEL=6

L2_OC=0

##### Hotplug driver Settings #####

# 0 to enable qualcomm mpdecision (stock)

# 1 to enable msm_mpdecision (recommended)

# 2 to enable intelli-plug

HOTPLUGDRV=2

What I saw:

---------- Post added at 11:21 PM ---------- Previous post was at 11:19 PM ----------

I rebooted couple times and I was waiting before open TricksterMOD

I wrote my settings from glitch-settings.conf file
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Could you please check that your /system/etc/init.d/99glitch file is in place, and with full permissions ?

It seems the script didn't run at all.. That's strange. Unless your rom doesn't have init.d support.
[Nexus 7 (2013) Original Android Development] crazyyyk:
99glitch file is in place and with full permissions!

I have stock ROM with gravitybox. How can I check my rom have init.d support?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Could you try to execute 99glitch with script manager or root explorer and check TricksterMod again (after killing it completely) ? Thank you
[Nexus 7 (2013) Original Android Development] crazyyyk:
when I manually run script from init.d TricksterMOD shows correct settings.

Why is it not set on startup?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Pm'd you
[Nexus 7 (2013) Original Android Development] nokiagye:
The kernel is great thanks. The trickster here works properly. when I open the tab Pop up the usual message I say yes and the old settings are back.

One question only, on trickster I can set min CPUs max CPUs I have it 1-4 I want to set it 2-4 and with screen of 1-4 how can I do this? I don't see any option for that
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4795439]nokiagye[/MENTION]

I'm sorry, I don't understand the question. Could you please explain further ? Thank you :)
[Nexus 7 (2013) Original Android Development] nokiagye:
OK I change the question. The max cpus min cpus option on trickster change it when the tab is on.With tabs screen of?
[Nexus 7 (2013) Original Android Development] nokiagye:
Ok I find this option on kcontrol

Sorry for misunderstanding

Thanks
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Little piece of information for anyone interested (thinking about [MENTION=4573440]pingaan[/MENTION] for example) :

I've made a "PRIMAtor" patch for AOSP/stock 4.3 users who don't want to upgrade to Kitkat so they can still use my latest kernels - at least for now - with wifi working.

You can grab it from here : http://androtransfer.com/?developer=TkGlitch&folder=Tools-Misc
[Nexus 7 (2013) Original Android Development] Batfink33:
I keep getting errors when i try to flash with 140. Something about the voltage file not existing.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5211228]Batfink33[/MENTION]

Could you tell me the exact error message please ? Thanks :)
[Nexus 7 (2013) Original Android Development] Batfink33:
Its

File get prop: failed to stat temp/aroma/s2ws.prop no such file or directory
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5211228]Batfink33[/MENTION]

Did you untick S2W/S2S/DT2W options ?
[Nexus 7 (2013) Original Android Development] Batfink33:
Yes, I did.
[Nexus 7 (2013) Original Android Development] poondog:
Bricked mpdecision will change your min/max constantly thats the way it boosts. Don't worry about it.

The settings are:

min cpus when screen is on (so it can be fixed dual core etc)

max cpus

when screen off it will limit to single core.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Let it ticked and disable everything when it asks for options. It'll fix it (I was able to reproduce your issue).

I'll fix the script tomorrow so it doesn't look for this file (and potentially others) to finish the process.

Thanks for your report :)
[Nexus 7 (2013) Original Android Development] Batfink33:
Great, thanks.Great kernel BTW.
[Nexus 7 (2013) Original Android Development] koller1994:
Yah, I click next til the end. Now, I can solve this problem. It is because I install this kernel while I connect the device with the laptop :v
[Nexus 7 (2013) Original Android Development] darkmage1991:
edited
[Nexus 7 (2013) Original Android Development] nokiagye:
I I'll make a video compassion between n4 and 7

The tab is 5 times faster thanks Tk-
[Nexus 7 (2013) Original Android Development] SynnyG:
Wow, the changelog looks really good ! I'm so excited to flash it on my n7 :) nice to see max screen off freq option !
[Nexus 7 (2013) Original Android Development] pingaan:
Neat, thanks! Really nice of you, works like a charm! <3

And now for a request.. Is it possible to add NFS support in the near future?? ;)

Cheers!
[Nexus 7 (2013) Original Android Development] crazyyyk:
Tk-Glitch, what settings do you recommend for maximum battery life? If I don't care for performance...
[Nexus 7 (2013) Original Android Development] Tim4:
Noticed this long time ago, but since no one asking here is my question:

What the Aroma installer supposed to do after the installation complete?

Ive noticed that device will shutdown after execution and not return to recovery if L2 speed is different from stock or the fast, is this normal behavior?

Also it says status 7 error on CM 140.

Something is missing
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION] I got a black screen after first installation. Then I come up with an idea. I raised TWRP screen timeout and tried to install it again(speedy install to fit into the timeout I set) and it worked! But I'm not sure if exactly this helped or it was random.. :D
[Nexus 7 (2013) Original Android Development] sgs9:
hi,

my part from log :

CPU optimization: improved

script aborted: file_getprop: failed to stat "/tmp/aroma/minfreq.prop": No such file or directory

file_getprop: failed to stat "/tmp/aroma/minfreq.prop": No such file or directory

Installer Error (Status 7)

will wait for ;) tomorrow version.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
The FAQ in op has an answer for you :)

Lowest CPU freq for both min and max, lowest GPU freq, smartmax or intellidemand governor, intelli-plug hotplug driver, S2W/S2S/DT2W disabled and multicore power savings enabled. Everything else default.

The FAQ in op has an answer for you :)

I'm on it ;)