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

That's always like that isn't it ? :D
[Nexus 7 (2013) Original Android Development] hello247:
'Get back some stability in a few cases for sensible devices since previous update's performance boost'

stability in what way? whilst gaming??
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Two users encountered some stability problems since the performance update in r103. You're one of them :p

So I did try to get a bit more general stability when overclocking either the GPU, CPU or L2/cache. I hope it'll be enough.. Keep me informed ;)
[Nexus 7 (2013) Original Android Development] hello247:
my glitch kernel configuration for r118 had to stay the same as r103. cpu at 1.836ghz and gpu at 600mhz with l2cache at glitchy settings. any higher cpu frequency will cause asphalt 8 to close on new kernel update. no undervolting applied.
[Nexus 7 (2013) Original Android Development] cryostasis25:
Gets stuck on google screen after flashing just used same setup from previous version
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3939352]cryostasis25[/MENTION]

CM11 or AOSP ?
[Nexus 7 (2013) Original Android Development] marck1991:
CM11 version running fine here ... Thank you!! :)
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Omg omg omg... I love r118 :) :)

Highest yet!
[Nexus 7 (2013) Original Android Development] cryostasis25:
Currently running aosp (slimkat lte)

Send from inside my Sexy... TARDIS.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
DEB then.. Hmm I'd like another DEB user to confirm that before I start digging what could break DEB compatibility.
[Nexus 7 (2013) Original Android Development] poondog:
Hi, you think the L2/CPU freq sync does much good for the battery and performance?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
For performance, yes, it does have a pretty large impact. Basically it'll improve CPU, GPU and RAM performance. About battery it should have little impact compared to CPU or GPU OC.
[Nexus 7 (2013) Original Android Development] :
Deb user here and everything's working fine. I didn't overclock or undervolt though.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Thanks man. Maybe he didn't make a complete installation or something, I've sent him a PM to know more.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Love that a Dev is so involved with the end users, truly inspiring ;)
[Nexus 7 (2013) Original Android Development] cryostasis25:
[MENTION=3847629]Tk-Glitch[/MENTION] will reflash kernel and post the settings i have selected if i get stuck on google logo again brb.

Send from inside my Sexy... TARDIS.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
When you do things for yourself, you don't have to care. But when you want to share it with others, you give them a bit of you.. I'm probably a bit too involved but I'm as I am. It's like : since I did make the choice to share my stuff with you, it has to be nicer than if it was only for me.

I'm the kind of guy who eats pastas with butter when I'm alone and who cook homemade foie gras when someone comes home :D
[Nexus 7 (2013) Original Android Development] cryostasis25:
Set cpu core - Default

Cpu frequency - 1728

Cpu optimization - improved (1.19)

Auto Undervolt - 800

-Full install-

Min Cpu Freq - 384

Hotplug Driver - Show1984

Thermal Settings - Run cool

Gpu Freq - 450

Gpu Governor - ondemand

Gpu undervolting - none

Bat life extender - 4.2

Here are my selected settings.

Update : It now boots dunno why it was not booting on my previous flash I remember choosing gpu undervolting to -50 will try again to recreate it. But thanks for the support tk-glitch ^_^ Also what are your recommended settings for internet and gaming?

Send from inside my Sexy... TARDIS.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3939352]cryostasis25[/MENTION]

I'm glad it worked at last.

Pretty normal settings here.. I don't see anything that could potentially lead to an unbootable state.

GPU uV @ -50mV shouldn't kill boot btw (you should even be able to push it around -100mV as you're running 450 MHz).

I'll check my scripts just to be sure it's not something weird in aroma. Thanks for letting me know.

Edit : about internet/gaming settings, you could bump the L2/cache to the next step and the GPU freq to 500 or 545 MHz, with as much uV as it can take. Still, it all depends on your needs versus your actual user experience.
[Nexus 7 (2013) Original Android Development] animania260:
This kernel really is a work of art. I was using your 103 AOSP release base to add showp's touchscreen fixes, and I updated the WiFi to the .1 version revision up (tiny small change..). Since you already had all the hotplug options and all the other commits from Faux123, Flar2, Franco, etc. Plus your own awesome additions.

But now you have those touchscreen fixes as well ?, the .1 revision update to Prima/WiFi is un-noticable really. I think it was just a configuration change.

Anyway, the new SlimBus OC is awesome. I didn't think I would notice, but there actually is a noticeable difference in Audio quality. It seems the surround sound especially "pops" out more.

Just wanted to say thank you for this amazing kernel, Glitch!

Options, and options! ?

r118 really is just a work of art man!

Keep it up brother!

Also, do you plan to keep updating the kernel to the latest 3.4.y's ?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] SynnyG:
Wow, the v118 CAF kernel is really awesome ! It's incredibly smooth, the difference between the v103.1 is really noticeable in Order and Chaos online game, keep this awesome way TK and thanks for your work :)
[Nexus 7 (2013) Original Android Development] marck1991:
I don't know where it comes from, but I haven't noticed that in other versions...

I'm on the newest release and I noticed a bug.

When you leave the device for about 5-8 seconds and then press a virtual button, only the half of the button sound ("knock") is played.

For example: You are on the homescreen, then you go into the menue where all apps are listed -> you wait 5-8 seconds, then you press the back button. The "knock" sound of pressing the button will only be played half ... but when you press it again, it will be played well.

Can you reproduce that?

Edit: I'm on CM11
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5209763]animania260[/MENTION]

I don't know what to say to that ! Except the big old thank you.

About the 3.4.y's updates, that's what I'd like. It can be time consuming though, especially when you have two bases to maintain. I'll do my best.

Thanks again !

[MENTION=2859745]marck1991[/MENTION]

Can't reproduce this on stock 4.4.2 at least.. It could be linked to the SLIMbus OC if it didn't happen before. Anybody able to reproduce that ? I'll ask my testers to try. Thanks for the report.
[Nexus 7 (2013) Original Android Development] poondog:
Well, 3.4.76 is out recently so you've got a lot of patching ;) Good thing is though, on AOSP/CAF kernels, generic 3.4.y diffs tend to apply cleanly.. on HTC One, they have stripped out comments in the kernel so after upstream diff there are always like 8 .rejs that need to be fixed...much easier on flo :D

This should not be linked to SLIMbus OC. It really has nothing to do with it, SLIM is more to do with media processing eg. audio, video playback etc
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4379011]poondog[/MENTION]

I do agree, it's much easier on Flo than what I was used to with Samsung ! :D

SLIMbus can "cut" then "reconnect" the bus dynamically, what you shouldn't notice when all works. If it cuts for some reason when it shouldn't it could lead to something like that don't you think ? Okay it's a plain audio file for this.. I'll probably have to learn more on it :p

I don't see hotplugging doing that anyway.
[Nexus 7 (2013) Original Android Development] poondog:
When its overclocked, running from ~23MHz to 27+MHz there should not be much of a problem. Yes, clocks have almost been maxed out but if anything it should impact battery (which it doesn't) not introduce stutters or whatever. I don't think at the moment, that they are related

Maybe see here

http://www.mipi.org/specifications/serial-low-power-inter-chip-media-bus-slimbussm-specification
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4379011]poondog[/MENTION]

Argh I'm out of thanks !

Thank you man :good:
[Nexus 7 (2013) Original Android Development] poondog:
haha dw mate, hope you find it useful
[Nexus 7 (2013) Original Android Development] SynnyG:
I've noticed a bug on v118 CAF kernel. When my N7 is locked since 30sec, the s2w/dt2w doesn't work. Only after some try (may be 10) the device wake up :confused:

It's really bad, the performance side is really improved on this version but this bug is really annoying :/

Does someone have this issue ?

More annoying: after some try, my N7 wake up but for... Tell me that my device is going to be shutdown...
[Nexus 7 (2013) Original Android Development] mus1mus:
Highest 3D Mark I ever got.. Glitchy Cache, Max GPU, no UV, RH..On 103

If you guys dig 3DMark, you'll know that to get a high score you need to play a lot with the OC. Certain combinations provide different results.

I'm gonna try the latest build..

Thanks TK
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

Not having such issue with stock 4.4.2/AOSP kernel, even after some hours of sleep..

I'll try to reproduce your issue on CM11.
[Nexus 7 (2013) Original Android Development] SynnyG:
May be is related to the CAF tree so :confused:

OK nice, and I've forgotten to say that I'm on the last CM 11 nightly ;) I'll wait some news from you :)

Thanks again
[Nexus 7 (2013) Original Android Development] tibere86:
I think this is a hardware issue. This is the same reason CM11 hasn't include volume to wake on the Flo. It takes multiple times wake up the table with the volume keys when it's in deep sleep.
[Nexus 7 (2013) Original Android Development] SynnyG:
The strange things is that on the previous version these functions worked very well :confused:
[Nexus 7 (2013) Original Android Development] hello247:
just tried using the gpu undervolting. any benefits except lower temp and battery life?

using 450mhz with -100 uv. suprised its stable at this uv. :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

I have a question for you.

Did you get touchscreen issues with r103 ? (I mean touchscreen slowness or freezes)

Thanks !

[MENTION=3563924]hello247[/MENTION]

No other benefit than lower temp and power consumption (it will also enhance the lifespan of the chip, but the battery would be replaced ten times before it'd die anyway).
[Nexus 7 (2013) Original Android Development] SynnyG:
No, this version was perfect. I only have these issues after the upgrade to v118 ! If you have a question don't hesitate ;)

EDIT: The user Sedge.One have the same issue as me (for some reasons he can't repply to this thread but he has PM me)

Second edit: Now my N7 has freeze during typing the screen and even reboot :/ I think the v118 has a serious issue with the touchscreen :/
[Nexus 7 (2013) Original Android Development] hello247:
[MENTION=3847629]Tk-Glitch[/MENTION]

Out of curiosity, do you use stock rom whilst using your kernel?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

Fixed. Go grab r118.1 on Androtransfer ;)

[MENTION=3563924]hello247[/MENTION]

Yes. Was using CM10.2 when I got the tab and released the first kernel for Flo, then moved to stock since CM11 release. I was relying on my testers for CM11 kernel testing, and testing AOSP kernel myself. Though an hour ago I installed multirom.. This way I'll hopefully be able to fix more bugs on the CM11 kernel in the next updates.
[Nexus 7 (2013) Original Android Development] SynnyG:
Really nice, I love this !!! I'm going to download it and tell you if it's good :)

Just for curiosity, what was the issue ?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

Some of the Showp1984's patches did break it, as touchscreen driver is a bit different on CAF base compared to AOSP.

I was able to reproduce your issue instantly, and it doesn't happen anymore on r118.1 :)

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

So here's a little update for CAF kernel users :

10/01/2014 :

CAF only :

- Revert some Showp1984 patches to fix S2S/DT2W functions

Thanks to [MENTION=5066986]SynnyG[/MENTION] for letting me know

Edit : Up on all mirrors as well now.
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
I flashed 118 (CAF) over today's CM11 nightly 2 hours ago and hadn't any issue with DT2W :silly:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Ahah ! Love it :laugh:
[Nexus 7 (2013) Original Android Development] SynnyG:
Upgraded and no more issue related to s2s/dt2w :)

But now I've a bigger issue :(

First when opening Xda app my N7 has completely frozen and I had to press the power button for rebooting

Second when typing this repply, same freeze !

Now no more freeze, I hope this will continue ^^ but thanks for your fix !
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5066986]SynnyG[/MENTION]

Are you using high L2 or CPU OC ? Or even high GPU uV ? If you got a very little instability before, it may be revealed now with the performance improvements that came with the update. Try some slightly more relaxed settings and see if it happens still (or if you didn't OC I'll have to try to reproduce it on my end).
[Nexus 7 (2013) Original Android Development] Sedge.One:
Here I am, needed 10 posts to participate in the Dev-Setion ?

CM11 M2, now on r118.1 - dt2w and s2w don't work :( because of these features I flashed this kernel (it's the first time I flashed a kernel)

CPU and GPU slightly OC, L2 slightly improved.

Not sure if I did everything right, or if I missed something (e.g. settings in TricksterMOD)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4114014]Sedge.One[/MENTION]

Probably something wrong on your side indeed. Make sure not to turn off the tab using the power button as it will disable S2W/DT2W by default (unless you did uncheck this behavior in Aroma). Also you need to swype from right to left on the navigation bar to trigger S2S.

I hope it'll help.
[Nexus 7 (2013) Original Android Development] Sedge.One:
Jup, that was it: works perfectly! Thanks a lot!
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
This kernel, newest rev with the dalvik improvements [MENTION=3847629]Tk-Glitch[/MENTION] recommended, and my benchmarks are up almost 5000 points from stock ;)

Thank you for this amazing kernel!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4114014]Sedge.One[/MENTION]

I'm glad it helped ! Enjoy :)

[MENTION=5392006]SwoRNLeaDejZ[/MENTION]

I knew you'd like it ! ;)

I'm out of thanks guys, sorry !
[Nexus 7 (2013) Original Android Development] Sedge.One:
You've got my attention ? where can I find these recommendations?
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
Pretty sure he's talking about this :good:
[Nexus 7 (2013) Original Android Development] SynnyG:
For the L2 I have the default settings that is checked in aroma (and I don't really know what is L2 :confused: )

CPU OC at 1.890 GHz

No GPU uV but OC at 504 MHz

The thing that is strange is that on the previous version I didn't had any bug with these settings, it appears that they are the more stable settings for me ! But I only have two big freeze and after that no more issues, your kernel work like a charm now :)

I think that the freeze are due to the hazard, or to CM (in this moment they have some issue I find), I will tell you if this happen again ;)
[Nexus 7 (2013) Original Android Development] animania260:
Yes indeed time consuming. I'll clone your AOSP base and cherry-pick, then squash the commits and send you a pull request. I'll get started Sunday. ?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
That is exactly what I was referring to :D
[Nexus 7 (2013) Original Android Development] cryostasis25:
I used or just flashed that bionic something the two zip files battery was improved and speed and response was the same i think using ut together with glitch kernel.
[Nexus 7 (2013) Original Android Development] Batfink33:
Best kernel for the N7!! Thanks TK-Glitch!
[Nexus 7 (2013) Original Android Development] mus1mus:
What are the frequencies involved with this?? What ROM too if I may ask?
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Stock 4.4.2, 2.106 GHz, 384 MHz, performance, cfq, no undervolt, GPU I think is at 545? Don't quote me on that.
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
I'm running into annoying micro-lag using the CAF version (118.1 on latest CM11, but it happened since I used this kernel, ie 103)

Before thinking it was the kernel, I did some testing to rule out other factors such as ART vs Dalvik.

Using stock CM kernel, I have no issue, on ART or dalvik

Using Glitch kernel, I have issue with both ART and dalvik

The settings I used (cf attachment) are what I thought the closest to stock.

I took a short video to explain the issue : Video Link

It happens just before the end, there's a micro-lag mostly noticeable because of the buzzing sound.

Any advice ?
[Nexus 7 (2013) Original Android Development] Mikes30000:
Unfortunately I see the same micro-lag and buzzing during gameplay. I'm on the latest CM11 and 118.1 This happened on the last version of the Kernel as well. My settings are a tad bit more aggressive, but it seems like that is a non-factor if it is happening on pretty much stock kernel settings.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Anyone having problems with audio? I get extremely glitchy and choppy audio. Music playback is really bad when screen is locked. Can't even hear a word. Anyone else has this problem?
[Nexus 7 (2013) Original Android Development] tibere86:
I do notice audio issues when running CM11 based ROMs. AOSP/Google based ones don't present any audio issues for me. I'm currently the latest Glitch with 384mhz min, 1.7ghz max, GPU 450mhz w/ -50uv, Smartmax governor settings. Running these exact same kernel settings on CM11 ROMs gives me audio issues but no issues on AOSP based ones FWIW.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Well purity is AOSP based and I'm running the AOSP kernel and I still face issues. Really hard to tell whether it's due to the kernel or something else. But I face the problem with every ROM I've tried so I thought I'd ask here.
[Nexus 7 (2013) Original Android Development] tibere86:
I'm running the latest RastaKat and don't have an issue. Give it a try, battery life and performance are great.
[Nexus 7 (2013) Original Android Development] Purplezigar:
And I was the other ;) I'll test this out as soon as I get home and flash this. Looking forward to some smooth gaming :D
[Nexus 7 (2013) Original Android Development] hello247:
Try raise your minimum cpu freq.
[Nexus 7 (2013) Original Android Development] SynnyG:
I've this issue too. I can't see your video but with your explanation I can see what you talk about. Sometimes these lag can be up to 5s for me and the bzzzzzzzzz is really annoying !

But before your message I thought that this was an issue related to my N7, sorry but I'm "happy" to see that I'm not the only one ^^ [MENTION=3847629]Tk-Glitch[/MENTION] do you have seen on your device these lag with the bzzzzzzzzz sound on your CAF kernel ?
[Nexus 7 (2013) Original Android Development] karanrajpal14:
I'll give it a shot. Thanks!

How do I do that?
[Nexus 7 (2013) Original Android Development] yzweixy1029:
Serious lag with sound break

I'm sorry that my English is poor...cause i'm a Chinese student...And i will try my best to describe the problem i met well...

My nexus 7 2013 is a 32GB Wifi Version,it was product at 2013.8.

The rom i use is CM11 01.11 Nightly and the Glitch kernel is the only kenrel that i flashed.

I used all default settings to flash this kernel for the first time... After I reboot my device,many problems come.

First of all,when i slide on my lanuch page,it often lag and seizing-up for a little while...when I play video(use MX player),it will also seizing-up for about every 10mins...together with the sound seizing-up too...the sound comes from my headset is zizizizizizizizizi~~~...

This situation happens quite frequent,nearly drives me mad...

Then I thought maybe my nexus 7's CPU is not strong enough to run at a high frequence...Then i flashed this kernel again,this time i used 1512Mhz for CPU ,No L2 boost and 400Mhz for GPU...

However,after i reboot my device,all the problems were still there...

I have no choice but to give up,so I flashed the CM11 rom again for recover the stock kernel,and all the problems dieappered...

Hope you,devs,could understand what i said...
[Nexus 7 (2013) Original Android Development] hello247:
During the aroma installer. Changing min frequency using trickster will not stick thats why.
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
Sounds like what I reported yesterday here, some other users (at least 2) using CAF version (with CM11 mostly) confirmed it.

Let's wait for Tk-Glitch acknowledgement, maybe he has an idea about what is the cause of this issue ;)
[Nexus 7 (2013) Original Android Development] mus1mus:
LOL.. It seemed I'll still will..

Anyway, how was the battery drain going with the set-up?

I have just been tweaking this kernel after being an EX kernel user for quite a while. And I noticed a big jump in Battery Life compared to EX even when using a massive 627 MHz of GPU Freq, 1898 MHz max and 384 MHz on the CPU; L2 and the rest maxed out and without UV'ing. Gentle Sleepers work??

I should say I love this Kernel. But there's a lot more I should be looking at with this. Only been using it bone-stock ( I meant no softwares like FAUX123 or Trickster MOD ) I just can't understand tweaking them yet.

Anyway, 30K Antutu could already be reached with 1998 just saying. :D
[Nexus 7 (2013) Original Android Development] JayanWarden:
I am recently going through the process of finding out how low I can push the voltage on the snapdragon 600 of your beloved Nexus 7.

But I someow get the impression that the voltage is not sticking after setting it.

Why you may ask?

Because I am running on 486 MHZ and 700mv. thats like, -275mv of stock., although it may be possible because I have a ACPU BIN 6 CPU (yay!) so it should in theory undervolt better.

Added a screenshot of TricksterMod.

Now to my question: Is it possible for the CPU to operate at this low undervolt? Or are my voltages not sticking?

PS: I am running on the lates Glitch Kernel
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4341753]JayanWarden[/MENTION]

Voltages are sticking and -275mV on low freqs is not incredible on this chip. The different thing to note is that there's a layer that will change the voltage dynamically in a predefined range to help stability, depending on the binning (it's a feature in these SoCs). The iV you apply is just like a starting point for this layer. The lower the volts, the lower the range. I hope it's understandable.

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

After installing Multirom and CM11 along my beloved stock rom, I was astonished by the number of bugs and inconsistencies on my CAF kernel compared to my AOSP kernel.. The CAF base has gone bad, definitely. It's a horrible mess :D

Glad I've now seen it and I'll do some massive bugfixing today, and if it's not ready for release, you guys will probably have to wait until tomorrow. I'll be back to you ASAP.