yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I did, some years ago. That was the starting point of the whole "Glitch" thing as a dev (it was some kind of private joke between me and my friends before). Great memories for me and I guess anyone who followed me :) We made some great stuff together.

Then I was forced to slow down then stop because of my health and my i9000 got stolen.. The kernel "spirit" (really that was just that) and the team that formed itself pretty naturally tried to make it survive, in case I would be back at some point.

Then here I am :cowboy:

It's been added for this purpose (balance), though some users would find it slow.. So I kept ondemand as default, but indeed it's in to be used !

Enjoy :)
[Nexus 7 (2013) Original Android Development] Grondinm:
Good times those where. Still so glad that you are back and working on Nexus 7
[Nexus 7 (2013) Original Android Development] cosmoskymaster:
Does anybody know if this kernel has any issue with mando rom?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I don't see why it wouldn't work as it should on this rom.
[Nexus 7 (2013) Original Android Development] azndan2:
I can't get double tap to wake or sweep to wake to work when the device is deep sleeping. It works fine once I've turned the tablet on and off. Does anyone else have this problem?

Alternatively, the inability to wake may be occurring when I've used the power button to turn the screen off. Either way, does anyone know how to deal with this issue?
[Nexus 7 (2013) Original Android Development] lippol94:
Great memories indeed! :)

I do remember those times when my I9000 used to warm my car sits :P

But yeah, I used to be your follower there, I9000 was my first smartphone and Android phone, started developing ROMs in those times and I had one of my best experiences ever! Loved that community :)

I'm glad you're fine now, we were all worried about your healthy issues.. :highfive:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
If the whole problem is linked to the power button thing, it's a feature. When enabled, it will disable the whole S2W/DT2W functions to lower power consumption when you make the choice to use the power button. You can disable the feature in /etc/settings.conf by changing the "PWR_TOGGLE" value to 0, or reinstalling the kernel (complete installation) and make sure the check-box is unticked.
[Nexus 7 (2013) Original Android Development] timbohenry:
charging threshold

The device charges up until full battery capacity (100%) although threshold is set to 4.2 (~93%). Did I miss any necessary adjustments in trickster mod, which I set to run on boot?
[Nexus 7 (2013) Original Android Development] Porobu:
For that to work you need to charge your tablet while on. Did yoi charge it while off?

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] timbohenry:
I did turn it off to charge over night. I'll keep that in mind for the next charge and post back here. Thank you!
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Is anyone else having problems with s2s? I have s2s and s2w enabled. But the tablet sleeps when I pull down the quick settings in portrait mode. Any way to fix this?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3611149]karanrajpal14[/MENTION]

You may want to change S2S orientation settings either from /etc/settings.conf or complete installation in Aroma.

You have three choices : both portait and landscape, only portrait, or only landscape. Keep in mind it's not dependent of the tablet orientation, meaning if you set only portrait for example, you'll need to swipe on the bottom of the screen (next to the usb port) even if the tab is actually in landscape (I hope it'll make sense).

By the way, next update will bring a little modification of the swipe "area" so it should be harder to trigger accidentally.
[Nexus 7 (2013) Original Android Development] hello247:
Anyone play asphalt 8? The game force closes. But doesn't on stock kernel.

Using 1.7ghz cpu max frequency with gpu at 450ghz.

Tried clearing data and reinstalling it too. Im guessing it's because I'm using extreme l2 cache oc

EDIT: used stock l2 cache oc and still force closes as soon as i reach main menu
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Probably instability, yes (either due to L2/cache settings or too much undervolting). The game runs fine here with "glitchy" L2/cache on both my tab and my friend's one though. Check your uV then try to lower L2.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Oh alright. I get it now. Thank you for the explanation. I changed the settings. I have another question, I just got an OTG cable and it seems that I'm unable to write to NTFS file system based flash drives. I googled a little and I read that there is some kernel level patching required. Is this so? I read that faux kernel supports NTFS read and write. If its so could you include those patches too?

Thanks again for the great job with the kernel. Loving it so far!
[Nexus 7 (2013) Original Android Development] nikr123:
I don't think it has anything to do with the kernel but rather KitKat since it includes better security you can turn it off by setting setenforce 0 with superuser in a terminal or you can download a app like: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
NTFS R/W is enabled in my kernel as well, using the same linux implementation. It's buggy though and may or may not work depending on a few factors. It would require the use of NTFS-3G module and I must admit I didn't look at this yet. I'll consider starting to work on that. You may find a way to your goal on xda though.. ;)
[Nexus 7 (2013) Original Android Development] coolek33:
Try USB otg helper. It's working for me with NTFS. It FCs after mount but I can do read /write from solid Explorer for example.
[Nexus 7 (2013) Original Android Development] bland.life:
Tested with Sonic Dash, OnDemand GPU Governor seems to work better with the game.

Interactive causes the game to lag bad at some points, while lagging it will have a honking sound.

At first I thought it was the CPU overclock but it seems to be the GPU Governor.

I also tested the non-CAF CM11 build that comes with Bricked Kernel.

It was super smooth compared to offcial CM11 with Glitch.

But I stuck to the official build to get timely updates.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Thanks. I'll try it out. Don't have a flash drive handy currently.

Oh ok. I have the NTFS 3G

but I'm still unable to write to it. Its buggy that's for sure. Look into it if you get the time. I did a lot of searching, a few things worked and a few didn't. Haven't found a sureshot way yet.

I'll give it a shot. Thank you so much.
[Nexus 7 (2013) Original Android Development] hello247:
any tips on how i can diagnose what's the actual problem with asphalt 8 ?

This is what i have tried. i have done a full wipe install of aospa and glitch kernel at stock settings except l2 cache at glitchy settings. (also tried it at stock and balanced setting) But had no luck. i can remember i used to play asphalt 8 on glitchy setting before so this behaviour is strange to me, I have no under volt set up and also gpu is left at 450 and stock cpu settings. I do not get any force closes when i play other games such as dead trigger.

I also flashed my rom using the stock kernel and asphalt works fine for first time but next time i attempted it forced closed.

I noted that it force closes when it tries to load data on the tournament tab when i open the game up.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

By any chance, are you using an adblocker ? I remember that most if not all adblockers are killing Asphalt 8 one way or another for some time now. Force close or no touch input detected or various random problems..
[Nexus 7 (2013) Original Android Development] hello247:
no adblocker used. i get the "unfortunately asphalt 8 has stopped".
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

If you could get me a log, it would probably help.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Dumb question here... Is this kernel compatible with stock 4.4.2?

Edit: because when I install it on my stock n7 the screen goes black as soon as I exit the aroma installer
[Nexus 7 (2013) Original Android Development] SubwayJrd:
Are you using TWRP to install it?

If so: Find the option in TWRP settings (booted into the Recovery) to disable your screen timeout.

The problem is something like the Aroma installer "jumps out of" the Recovery in some way that lets TWRP run into its screen timeout, then when you exit Aroma it doesn't want to wake up from the timeout.

You can also just press and hold to power your device off and back on again, and it will boot just fine (because once you're out of the Aroma installer the kernel is in place.
[Nexus 7 (2013) Original Android Development] El Nino1977:
With your CM10.2-flo-Glitch-20130919.0904.zip all was great. The ability to mess with cpu speeds (running 19xx was fine) , UV, gpu etc was great. But just flashed r17 and it reboots once I unlocked. So dropped to stock settings in aroma and yes it boots, various attempts and different chosen aroma options it seems if I choose anything above 17xx with stock UV the reboots occur. It's no issue as the said zip runs perfectly for me, just curious what has changed since as my device can run higher speeds just not with r17.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Something is wrong with aroma and flar2 stuff on my side. But basically voltages changed much and r20 will fix this part, but still the script doesn't send frequencies higher than 1728 for some reason. I'll fix it asap.
[Nexus 7 (2013) Original Android Development] dictionary:
About 14 hours of airplane mode, on stock settings. Using the 9.19-904 build on psx ROM. 12+ hours screen on time. 5.5 hours of which have been with WiFi on. Just leave this here.
[Nexus 7 (2013) Original Android Development] airmaxx23:
I'm getting some serious lag while gaming on the r17 kernel, I'm going to try r15 and see if it's still there.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
r20 feels great guys. I think I was able to fix what was broken since aroma integration, plus added nice stuff. Dynamic fsync for example. Also the "faster" setting for bus speed as been pushed nicely, enhancing the mem bandwidth considerably. The disabled debugging is helping as well to smooth things plus lower drain on battery and ram. For the OC lovers, base voltages are now higher (much like previous builds), so you should be able to get nice freqs.

If your device can handle it, try the "faster" setting for the bus and tell us what you think =)

Enjoy guys
[Nexus 7 (2013) Original Android Development] El Nino1977:
I've never been a fan of aroma :eek::p I'll give r20 a bash and see what happens. :D

All good on r20, cheers man. Smooth as always!
[Nexus 7 (2013) Original Android Development] sageDieu:
oh man, imagine my surprise when I saw this glitch logo...

how is your health tk? I haven't seen you around since the fascinate days like two years ago. glad to see you are still working your magic especially on a device I have! switching to the kernel ASAP, I would trust your work over anyone else based on previous experience working with you man.

are you still doing anything with your app? i remember using that for updates back in the day.

also I used to be a beta tester for you guys btw, if you're wanting any for this device (or galaxy s4 as that's my phone now) I would love to get back in the game with you guys. I probably still have the credentials to the old server lying around!

good to see you.
[Nexus 7 (2013) Original Android Development] lpachuong:
Same here. Also tried r20 but still laggy in games settings. Please correct me if I am wrong in gaming setting:

- MP Decision OFF

- Governance INTERACTIVE

- GPU 500-600 (though they don't seem to make any difference)

- CPU 1.7Ghz

- Temp Throttle OFF

Though i set these settings up, playing A8 is laggy and not as smooth as ElementX. I think it suffers from the temp throttle bcz my tablet temp never goes above 70degree.
[Nexus 7 (2013) Original Android Development] Crwolv:
DAAAAAAAAANG, thanx tk, no other kernel has gotten me that high result' thank you for your hard work bro!!! And that's only 600gpu and 1.9 GHz cpu
[Nexus 7 (2013) Original Android Development] Crwolv:
Heads up,its improper to name another kernel (or ROM on ROM thread) on someone's thread on XDA. I'm sure nothing was meant by it but we should all know the rulz(its uncouth). Not being a meanie at all just letting ya know(I've been there done that and had to be reminded by a Mod) just helping.
[Nexus 7 (2013) Original Android Development] dictionary:
While I agree to an extent, some mods are just pissy. This user wasn't complaining, and was just giving a baseline example. Constantly speaking about another kernel and singing its praises, maybe he'd be wrong. Just giving a quick comparison with detailed information though? Hardly. I don't think he meant anything negative by it. Perhaps just so that tk could take a look at elemental in regards to the issue he's having.
[Nexus 7 (2013) Original Android Development] Crwolv:
I already said im sure he meant nothing by it and although I agree with u also somewhat all I was doing was letting him and other know. Heck some op's dont care/some do. The rule ISNT vague because people can get around things and still do it in a round about way while trying to be a douche that's why the rule is there. Like i said I agree with u. Was just giving a heads up in a nice way.your message in fact can be misconstrued as trying to make me look bad although I don't think you were anyway I was just trying to help out my fellow peeps
[Nexus 7 (2013) Original Android Development] dictionary:
If someone twisted what I said, into somehow making you look bad, that's one heck of a reach, lol. I concur with you and I know you were only doing it for good reasons. *thumbup*
[Nexus 7 (2013) Original Android Development] Crwolv:
No problemo, awesome friggen kernel isnt it though?
[Nexus 7 (2013) Original Android Development] dictionary:
Absolutely. Like I posted my results. 12 hours on screen time, even though 6 of it was with Wi-Fi off, and still had 34 something percent left. Amazing
[Nexus 7 (2013) Original Android Development] jordirpz:
[MENTION=227267]glitch[/MENTION]

Deep sleep works? Because this last night, dosnt work for me( i think is because led is on)

Enviado desde mi Nexus 7 usando Tapatalk 2

---------- Post added at 09:01 AM ---------- Previous post was at 09:01 AM ----------

[/COLOR [MENTION=227267]glitch[/MENTION]

Deep sleep works? Because this last night, dosnt work for me( i think is because led is on)

Enviado desde mi Nexus 7 usando Tapatalk 2

---------- Post added at 09:02 AM ---------- Previous post was at 09:01 AM ----------

[/COLOR [MENTION=227267]glitch[/MENTION]

Deep sleep works? Because this last night, dosnt work for me( i think is because led is on)

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] lpachuong:
Hi guys sorry I didn't mean to compare. I was trying to say with those settings I experienced some lags. Yes we used to have this issue before on other kernel duw to thermal throttle. With version r20, we can only set 1 step for temp >80 to 1.2ghz which does cause some drop in performance. If this can be improve, this kernel is my heaven :)

Again my apologies for the confusion.
[Nexus 7 (2013) Original Android Development] jordirpz:
Confirm that deep sleep in r20 doesnt work for me.

Can you fix it please?

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Really guys be peaceful in here. I know the rules, I know many are pissed to repeat them again and again to others, but still.

We all want to get the best out of our devices, and I'm sure [MENTION=4684315]flar2[/MENTION] is thinking the same. If I'm able to help anyone, dev or not, I'll be pleased to do so.

[MENTION=4684315]flar2[/MENTION] found out that the GPU OC code in my kernel was interesting and started working on it, probably thanks to the people here talking about his work.

I'm in no way against any dev around here and if our shared work can lead to better stuff for the N7.2 I'm in.

Peace guys =)

[MENTION=5068754]jordirpz[/MENTION] Tonight my led was on and my tablet has been sleeping like a baby with wifi enabled. Try to look for wakelocks, I'll do some testing on my other device.

[MENTION=1202914]ipachuong[/MENTION] The two tabs I have aren't suffering from thermal throttling even at 2 GHz+ CPU and 600 MHz+ GPU gaming for an hour or two so I didn't thought about such issue. I'll gladly improve this part.

BTW "faster" mode bus can lead to lower performances even if stability doesn't look bad. If RAM is erroring a bit the device won't necessarily crash but speed will start to be erratic with heavy load. If you're using this setting, try to lower it to "fast" (that's already equal to "ultra" setting from Elemental X).
[Nexus 7 (2013) Original Android Development] hello247:
Sure thing

http://pastebin.com/N0tEMdkb

Dmesg log attached below. :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

There we have it..

<qeglDrvAPI_eglChooseConfig:827>: EGL_BAD_ATTRIBUTE

and

signal 11 (SIGSEGV)

The first one may not lead to a force close, but it's either GPU OC or GPU driver at fault most likely.

The second one is an invalid memory access (either because of a permission restriction or corrupted memory zone). It could be RAM corruption because of bus speed OC (L2), unstable CPU OC, or just a bug in the game. The strange thing is that you say it does happen even with stock kernel, so it sounds more like a game bug. CM11 isn't it ?
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Wow. That's all I can muster on that one... Thank you for the advice ;) worked like a charm. Never thought it could be something so silly.. Must have flashed it five times thinking it was incompatible.. I'm an idiot :P
[Nexus 7 (2013) Original Android Development] hello247:
[MENTION=3847629]Tk-Glitch[/MENTION]

Not cm11, using aospa beta.

EDIT: I wiped data and now the game works fine on stock kernel.

Also it works fine on elementalx 2.5 kernel with elementalx l2cache overclock applied with -25mv undervolt on all frequency. ( any higher undervolt it stops working).

could i ask if u undervolt at all? From my understanding its not advisable to be undervolting when applying l2 cache oc.

I think i figured out what the problem is. trickstermod does not make frequencies stick to stock values if i install the kernel using cpu oc values then scale it down later. For that reason it makes asphalt force close. so i have to choose stock cpu in the installer to get asphalt to run. Guess 2.0ghz dont work well when only gaming on asphalt 8 lol
[Nexus 7 (2013) Original Android Development] SubwayJrd:
No, you're not an idiot, it's just a WEIRD problem.
[Nexus 7 (2013) Original Android Development] Robshr:
great work

This is by far the best kernel for the n7 super fast I have an lg g2 and didn't think my n7 would compare as far speed but with this kernel there equal

I got an antutu score of 25463 [MENTION=3847629]Tk-Glitch[/MENTION] Would you consider building a kernel for the lg g2
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Indeed, CPU clock is jumpy if the limits aren't hardcoded, that's why I'm using Flar2's Aroma based system as you can limit the CPU clock at the source so it won't jump, but you need to select the real frequency you want in the installer, not a higher one.

About overclocking, it'll all depend on your chip. I'm undervolting with glitchy L2 OC running 1.94GHz CPU and 600 MHz GPU (also undervolted, you'll have the ability to do it in next release) and it's running great with very low heat output.

2GHz/627MHz is also perfectly stable but the voltage required for that is a bit higher than I'd like. But that's how my SoC works, and only this one. Yours may (will) respond differently to OC/uV, so you need to tweak and test what works best for your hardware.

BTW keep in mind "elementalx" l2/cache OC is the same as my "improved" setting (1.19GHz-4.26GBps), so using "extreme" (1.43GHz-4.80GBps) or "glitchy" (1.49GHz-4.96GBps), while much faster, is also pushing the hardware much higher (to the stability limits of the best SoCs concerning the "glitchy" level), and may lead to unstable behaviors. I know it's tempting to push all the settings available to the max, but that's not how it works :D If you really want to push your hardware to the max it can do, test each setting's stability and start with some relatively conservative values till it crashes, then lower it by one step and test longer, etc.

Good luck mate :)

Useful note to everyone concerning L2/cache OC (I'll eventually add that to OP) :

stock (1.13GHz-4.26GBps)

improved (1.19GHz-4.26GBps) --> equal to "elementalx" setting in Flar2's kernel

balanced (1.22GHz-4.66GBps) --> equal to "ultra" setting in Flar2's kernel

fast (1.35GHz-4.66GBps)

extreme (1.43GHz-4.80GBps)

glitchy (1.49GHz-4.96GBps)

Thank you :) I'm glad you like it !

Also if you're not using ART you may want to use this : http://www.xda-developers.com/andro...optimized-kitkat-dalvik-and-bionic-libraries/

It will not only boost benchmarks but make the device even snappier when using Dalvik VM.

About the G2, as it seems the Nexus 5 project will fail, raising two times more money for a G2 seems unlikely. But if you know enough people who would be interested by Glitch kernel on G2, feel free to make some kind of fund collecting project to send me one ;)
[Nexus 7 (2013) Original Android Development] ptesmoke:
I would love you on the g2 and the n5 ? I'd have a perfect trifecta
[Nexus 7 (2013) Original Android Development] hello247:
thanks a lot [MENTION=3847629]Tk-Glitch[/MENTION]

found out that setting i had to use for asphalt to work was cpu at 1.836ghz and gpu at 600mhz with gltchy l2 cache oc. even though my other games work fine at 2.0ghz . :laugh:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
New r118 build is up on androtransfer (uploading soon on mirrors) !

Many changes and an interesting new feature : GPU voltage undervolting. Prepare for crashes until you find what your device likes :P

Enjoy guys !

09/01/2014 - Complete installation recommended.

- Various performance improvements

- Get back some stability in a few cases for sensible devices since previous update's performance boost

- Add configurable GPU voltage and make some uV presets selectable through aroma and /etc/settings.conf (if you want to tweak the values, go check 99glitch script in your init.d folder)

- Quicker load to sleep transitions, improving battery life

- Some GPU driver bugs fixed, leading to better GPU usage/scaling in various situations (thanks to FranciscoFranco)

- Optimized Deadline io scheduler for better performances

- Adjusted shortsweep distance to make it harder to trigger accidentally (thanks to flar2)

- Updated Aroma binaries to 2.70RC2

- Fix renaming back Qualcomm's mpdecision binary when enabled in Aroma after it's been disabled

- Force disable input-boost when selecting Qualcomm's mpdecision in Aroma, as it has it's own input-boost

- Add back 400 MHz GPU frequency

- Update toolchain to Sabermod 4.8.3

- Various bugfixes

- SLIMbus OC by ZeroInfinity and Poondog

- More touchscreen patches from Showp1984, fixing more touchscreen issues

AOSP only :

- Updated ROW io scheduler from codaurora (already merged in CAF base)

CAF only :

- Sync with upstream (camera_v1: Fix the post-processor)

- Fixed ondemand governor inconsistencies/bugs that could lead to massive power drain and/or performance issues
[Nexus 7 (2013) Original Android Development] hello247:
haha as soon as i find what my device likes for asphalt, theres a new update :laugh:

Cheers for the update, time to test :good: