yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] matcho13579:
Ha! I knew it! I'm proud of myself :D

[MENTION=3847629]Tk-Glitch[/MENTION] Interesting, what do you think?

https://github.com/facebook/conceal

Don't know if it can be installed when installing kernel, it would be great

http://facebook.github.io/conceal/

http://www.wired.com/wiredenterprise/2014/02/facebook-conceal/
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
As promised, the installation process as been fixed when some settings are unticked. No more missing file error. r140.1 is live on Androtransfer, and soon on mirrors.

08/02/2014 - r140.1 :

- Fix the updater script and configuration generation to fix missing files errors when some settings aren't selected. Also, set a fallback to Qualcomm MPDEC hotplug when nothing was configured.
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
Just a short feedback.

After I installed this zip I've seen that trickster doesn't show any of my preferences.. Above all I think that there is something wrong with the settings in the aroma.. In fact during the installation I selected s2s only in portrait and while I was cancelling a facebook chat, passing with the finger from the top edge to the bottom the screen turned off.. I tried again and again.. So yes ..the s2s is working also in landscape.. Is not a big deal.. I'm just saying it because I think is a proof that the settings during the aroma don't stick after boot.

I love your work btw. <3
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4700008]JeanEatsWorld[/MENTION]

I'm not sure yet what the problem is for you and crazyyyk, but it seems the script in charge of applying all the settings doesn't run for you. For him, renaming the 99glitch script (in init.d folder) to "00test" made it work after a reboot. I've not been able to reproduce the issue, but I'll continue to search for a logical reason behind that. I'd be grateful if you could try as well and check if it worked. Thank you :)
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
Mmmm something wrong I guess
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4700008]JeanEatsWorld[/MENTION]

Something's wrong indeed..
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
You know what.. Im just realizing that everytime I install any of your kernels (even elementX of I don't go wrong) my tab turns off by itself right after the Flash.. May this affect the setting up of my settings?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4700008]JeanEatsWorld[/MENTION]

TWRP recovery I suppose ? Check the FAQ in OP of this thread, there is a note about this behavior with TWRP and how to fix it. If it does indeed fix the script issue let me know ;)

Thank you.
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
I'm such a stupid.

Sorry man.

And thanks for your support.

Love you.

<3
[Nexus 7 (2013) Original Android Development] :
Forgive me if this sounds like a stupid question, but I was wondering (and for the benefit of others)...

Do we need to wipe cache/dalvik cache after flashing r140 and up?

##Particularly when the optimized dalvik and bionic setting in aroma is enabled.##

I know it's recommended to perform the usual cache wipes after flashing the patches manually, but I'm not sure if you've included a script that automatically does this when installing the kernel, or if the user needs to do it.
[Nexus 7 (2013) Original Android Development] animania260:
You have to wipe dalvik cache when flashing the optimized dalvik patch. Otherwise its pretty optional. I usually wipe dalvik cache/cache every 4 or 5th flash just to kind of keep things clean, but you really don't need to wipe dalvik/cache unless flashing optimized dalvik patch.

Tk-Glitch could provide more details on this I'm sure, if need be. ?
[Nexus 7 (2013) Original Android Development] darkmage1991:
um, so i was running an earlier version and everything seemed to be working fine with my external dac, i updated the kernel and rom, then all the sudden the right channel was the one only working, i tried flashing the latest kernel and carbon rom, it still the same way. am i missing something with the new kernel? i verified the dac works fine using the computer. its the tablet all the sudden not feeding a left channel, and the right channel is very gargled. any ideas?

i installed elementalx kernel, it fixed the issue with only 1 channel out through the dac. but the gargled audio is still there. i reflashed elementalx so i could use mass storage to transfer the kernels and roms i was gonna try, (had to reflash without having otg charge enabled for mass storage to work) and it fixed the gargled noise. but with your kernel i have both issues...
[Nexus 7 (2013) Original Android Development] hakcenter:
Thanks for updating the installer with scheduler and governors
[Nexus 7 (2013) Original Android Development] whytechapel_x:
Can I flash this kernel coming from another kernel? Or do I need to do anything special?
[Nexus 7 (2013) Original Android Development] melander:
I usually turn off trickster mod before updating the kernel, after device is fully booted then i set back my desired settings in trickster,
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4708802]whytechapel_x[/MENTION]

Coming from Franco kernel it's recommended to reflash the rom to restore stock kernel, then flash the new kernel (mine or any other one).

[MENTION=3308323]darkmage1991[/MENTION]

I don't understand the mass storage problem, but about the dac it could be many things.. I'd need more details about the "earlier version" you're talking about for example, to review the changes since.

[MENTION=5163087]Protomartyr[/MENTION]

Installing the optimized Dalvik patch should trigger a cache regeneration by itself so it's not "required". Doesn't hurt though.
[Nexus 7 (2013) Original Android Development] azvlean:
Great update, the new settings are useful !

___________________________________________________________

Phone : LG P-700 running Carbon

Tablet : Asus Nexus 7 2013 stock rooted with Glitch Kernel.
[Nexus 7 (2013) Original Android Development] darkmage1991:
im not worried about the mass storage thing, im used to that as it seems to be a problem with otg charging enabled. but the dac thing started after flashing the 12/22 version i am not exactly sure what version i was on before that :\
[Nexus 7 (2013) Original Android Development] whytechapel_x:
Just flashed the kernel and its awesome. One question guys, how does USB otg work? I have my meenova connected but it doesn't get read by my phone..
[Nexus 7 (2013) Original Android Development] poondog:
you will need rom side support too. Which ROM you using? SlimKat has no issues with OTG
[Nexus 7 (2013) Original Android Development] whytechapel_x:
I'm using sinless Rom. But I thought it says in the op that otg works out of the box or did I misunderstand lol. I can stickmount so no biggie. Just curious.
[Nexus 7 (2013) Original Android Development] poondog:
OTG requires ROM side changes (to vold, ramdisk etc) so unless they are changed in kernel zip (some kernels for some devices do)
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
https://play.google.com/store/apps/...google&utm_medium=organic&utm_term=stickmount

Try to install that
[Nexus 7 (2013) Original Android Development] xanthrax:
yup, this works perfectly

sent from my Darkside of Nexus 7 LTE
[Nexus 7 (2013) Original Android Development] digweed4me:
I am really wow by this kernel running slimkat and this kernel awesome performance and battery life and gpu overlcock to 600mhz really shines while u gaming almost equal performance to my nexus 5 with s800 + 330 gpu. thanks for all your hardwork glitch but my question is why this kernel not available for nexus 5?
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
I'm trying ak because of the lower frequency.

It's the first kernel for n7 which I see with 81hz as low frequency.

It looks like is doing great.. Have you ever considered to implement it in your kernel?

Also I wanted to tell you I had few little issues with your last one. After few hours without touch the tab when I tried to use it, the screen didn't turn on and I had to hard reboot it.. It happens twice out of 2 times I left the tab on the desk for some hours..
[Nexus 7 (2013) Original Android Development] hello247:
Have you undervolted? It could be issue why the device is not waking
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
Nope
[Nexus 7 (2013) Original Android Development] hello247:
Whats settings did you apply when you installed glitch?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
[MENTION=3847629]Tk-Glitch[/MENTION]

Could you point me to the commit needed to make an Aosp kernel to cm compatible?

Thanks

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] mus1mus:
@ TK-Glitch

I have just one thing to ask.

Could it be possible to lower the GPU Frequency further from 320 MHz? 270 or 300 I guess??

I noticed every single game I have plays without hiccups on 320 MHz. Even with the Maximum UV.

I guess 270 wouldn't hurt games. But the goal is a much cooler TAB..
[Nexus 7 (2013) Original Android Development] genocide_ru:
Hey there,

Can anyone advise settings for what I'm trying to achieve?

Want to have screen-off music with lowest freq possible.

And to turn it "full speed" freq when play games.

Tried ElementalX, but no matter what I do, music is choppy when screen-off, even with stock 1026 freq

Thank you.
[Nexus 7 (2013) Original Android Development] animania260:
I've used the lowest 162mhs frequency on this kernel (with -75 uv) and no stuttering at all when screen off while playing music.

You should just select whatever highest frequency you want, then use showp' msm_mpdecision, 162 lowest frequency. And select at least a slight L2/Bus over clock like the 2nd or 3rd option.

Undervolt at least -50 on all CPU frequencies. Really helps with battery and small heat savings. Also I recommend disabling Input Boost.
[Nexus 7 (2013) Original Android Development] killflaker:
Ok, now i need coffee (more coffee) and after the F1 GP i test this.

My N7 boot at 2.2Ghz, and tested at 2.05Ghz/487Mhz.

Cpu run perfect at 1.9ghz, i just want to push the gpu over 487mhz.

(sorry for my english, i'm french)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5208931]killflaker[/MENTION]

I'm french as well and my english is poor.

No worries man ;)

I didn't touch GPU voltage so unless you're pushing high volts into the CPU, the GPU won't get that much hotter than stock.
[Nexus 7 (2013) Original Android Development] El Nino1977:
The genius known as faux has hacked the gamma on the flo, with gamma control, the speed and fluency of your kernel. There will be a beast in the horizon... :sly::cool:;)
[Nexus 7 (2013) Original Android Development] killflaker:
Always stock voltage or little undervolt! Never overvolting!

(Merci l'ami, ne t'inquiète pas je pousse pas comme un fou, si ça passe pas je force pas :D)
[Nexus 7 (2013) Original Android Development] thunderger:
After upgrading to r22 build my N7 doesn't boot successfully anymore. Often it hangs in cm logo but sometime it comes to "android is upgrading" dialogue. At this point it dies. With r20 build there are no boot issues.

Now, I've upgraded from CM 09-21 to CM 09-22 running "stock" kernel so my N7 hopefully will boot again so I don't have to make a full new installation. :(
[Nexus 7 (2013) Original Android Development] lpachuong:
would love to know if you have a proper solution for this. I had no choice but had to roll back using NANDROID backup :(
[Nexus 7 (2013) Original Android Development] thunderger:
unfortunately, no. :( I've to do a factory reset and to flash CM again, loosing all apps and settings. Glitch r20 is running OK, r22 is boot looping. So at the moment I use stock CM kernel.
[Nexus 7 (2013) Original Android Development] menissalt:
At least it's not just me, I just caught on to this kernel and 22 was my first attempt. I've been up all night playing with it, fixing it, and trying it again. On occasion I could get 22 to boot, but the flash/wipe process was convoluted and the rom kept freezing.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Issue spotted, fixed in next build.

Sorry for that.

----------

Today's r15 is fixed. Sorry for the delay.
[Nexus 7 (2013) Original Android Development] angieri918:
The same thing happened to me. And now I can't get titanium to restore my backups.. did you run into this issue or has anyone else?
[Nexus 7 (2013) Original Android Development] jordirpz:
Hi,r15 fix is better r20?

Enviado desde mi B1-A71 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Only up to 24 builds per day. So today 's r15 is newer than r20 from two days ago.
[Nexus 7 (2013) Original Android Development] thunderger:
I ran in this bootloop issue. :( At the moment I'm waiting for less builds per day.

[MENTION=227267]glitch[/MENTION]:

What do you think about creating "alphas" - like now - "daily betas" and sometimes "stable" builds. At the moment it is like "russian roulette" as we say in Germany. :D

I like your kernel and I'll test and report issues but it shouldn't break devices as reported three times. :)
[Nexus 7 (2013) Original Android Development] jordirpz:
Glith ,je t'aime. Jajajaja

Enviado desde mi Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Hi Used Glitch with PA. but All the Games Stutter when playing, switched back to Elementalx and all is well.. any suggestion?
[Nexus 7 (2013) Original Android Development] Alucardis666:
Gonna give this a go. Make my Nexus the speed demon I always knew it could be. thanks so much
[Nexus 7 (2013) Original Android Development] nikr123:
I'm not sure but isn't PA based on aosp?
[Nexus 7 (2013) Original Android Development] -Jesco-:
yes PA is based off AOSP
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I do agree with that, though it was my fault really. It shouldn't have been breaking boot.

I'll push less frequent updates and release only the best/stablest builds so it won't happen again.

I did start already to rework my testing protocol since the boot breaking drama leading to nandroid.

-----

Just constated that Dev-Host bugged on the upload of yesterday's r15 release, adding many 0 Byte files.. Removed all of them.

Adding alternative link for downloads (Androtransfer), thanks to [MENTION=1700264]sixstringsg[/MENTION]

-----

Added back IRC informations to OP, just like good old times.
[Nexus 7 (2013) Original Android Development] TunedFish:
The expanded thermal controls on 23.r17 is just what I needed. Also, I was having problems with the top frequency sticking on 22.r15 but that is solved in 23.r17. BTW I'm running pa r2, 1728 cpu 600 gpu.
[Nexus 7 (2013) Original Android Development] genocide_ru:
Thanks for details, will try your settings and check music. Can you tell what frequency your CPU is on when music plays with screen-off?

Thank you.
[Nexus 7 (2013) Original Android Development] animania260:
No problem. I believe it usually stays right around 162-386. I think it only bumps up to 386 because of other background processes or when switching songs.
[Nexus 7 (2013) Original Android Development] optimusG:
Wow... With the latest aosp glitch my nex looses 0.25%/hour idling with wifi/sync, viber always on. :cyclops:

Great kernel mate! :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
If you can get that to happen again, a copy of your /proc/last_kmsg file would help (as I'm not having it). Thank you.

About 81MHz CPU step, it's added in my dev tree, so it'll be available in next release.

I'll make a rebase soon as many of my commits are either monolithic or unclear..

If you're a dev, you may want to go check the CM tree and merge the GPU driver and ION changes in your AOSP tree. You'll then need to fix a few issues by yourself as it won't build as is or could be buggy, but nothing too hard to repair ;)

You don't need me to do that. Okay, it's not available in Aroma, but easily achievable by modifying 99glitch script in init.d. Head to the #GPU Clock settings section, and change the value for 320 MHz (320000000) to another valid step (below 320, it's either 200 or 128MHz (200000000 or 128000000), then save it, reboot and... done.

You could do that with an app as well btw.

The same process can be used to change GPU voltages to whatever you want - though overvolting it may kill it, so be careful.

NOTE : you can't use the frequency you want, it HAS to be a valid frequency for the GPU.

Here are the valid frequencies : 128, 200, 320, 400, 450, 504, 545, 600 and 627 MHz.
[Nexus 7 (2013) Original Android Development] antypas:
Well, no offense to anyone but the idle times of the stock kernel are much better. No custom kernel has managed to match the stock kernel in idle times. If I remember correctly it is 1% per 12 hours...
[Nexus 7 (2013) Original Android Development] optimusG:
Yup. It may be true but the stock kernel is not optimized for performance (overclocking etc).

Sent using Tapatalk
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
1% per 12 hours is just not possible as it would mean 50 days of uptime and there's no way this tab can do it, even with no wifi and absolutely zero screen on time. No offense either, but it's more than likely a false reading. Like the i9505 GE giving virtually awesome "battery percent drop per hour " at high percentages, then drops faster and faster til 20% where it'll drop almost 10 times faster than at 21%..

As a user I'm having very similar idle time versus stock, but better SOT. I prefer it this way anyway :p
[Nexus 7 (2013) Original Android Development] just lou:
I never got drain results like that using the stock kernel even with WiFi off during sleep. I got around 0.25%-0.5% per hour.
[Nexus 7 (2013) Original Android Development] schlager:
does this kernel have the ability to charge at bootup with an OTG+Charge cable? on ElementalX and bruce2728, my charger is not recognized when I boot up with my OTG y-cable.

someone else mentioned this problem on this thread, but it was in reference to the Qi charger... i was actually thinking of using that to fix my problem..
[Nexus 7 (2013) Original Android Development] antypas:
I constantly got these kind of idle drains (0.1% per hour) with the stock kernel.
[Nexus 7 (2013) Original Android Development] PlasmaPump:
Thanks! Will try it tonight and let you know how 140.1 performs on JB 4.3.1 SlimBean.
[Nexus 7 (2013) Original Android Development] Skinpipe:
nexus 7 2012 has idle like that but not the 2013 model i have both and the old n7 idle is amazing
[Nexus 7 (2013) Original Android Development] genocide_ru:
So, here is what I did:

Core separate settings - no

CPU overclock - 1728

opt level - balanced, Minumum CPU - 384, Undervolt - -50

hotplug - Showp1984

Thermal - default

GPU - 450, Ondemand, -25V

CPU Governor - Ondemand

I/O - row, read ahead - 256KB

No wake/sleep options, no Batt life settings, No Misc Options enabled (Input boost disabled)

Result is, right after I turn Off screen music start stuttering every few seconds. CPU Spy shows 384 freq when screen is off with music

What settings should I change to prevent stuttering? BTW I use Play Music and flac

PS: Probably, it is flac related issues. Will try with 320 mp3 and update post
[Nexus 7 (2013) Original Android Development] genocide_ru:
Thank you for advise, but eventially I switched back to mp3 from Flac and this issue gone away. I knew that decoding Flac takes more resources, but it is too much drain as I can see.

Anyway, will check if Flac can be played with 384 on screen-off with Interactive I/O and read ahead set to 128 some time.

Wait, isn't I/O provided by row/deadline/... etc options? irc Interactive is Governor mode.
[Nexus 7 (2013) Original Android Development] thenetvines:
I couldn't find info on this question using search :(

Does anyone know if this Kernel plays nice with this popular ROM that seems to be based on Cyanogenmod?

[ROM][4.4.2] AOSB Project (ProBAM ROM) 1.2.9 [MULTIWINDOW] 13/02/2014

I mainly want to have a way to be able to use OTG without many issues. If there is another way, I'd appreciate the info. Thanks!
[Nexus 7 (2013) Original Android Development] danaff37:
I'm actually using this kernel on that Rom now. Running good.
[Nexus 7 (2013) Original Android Development] RealSlimShadyMC:
Woah D: that's insane!
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION]

Why 2nd, 3rd and 4th core's clocks are @ 2,052 GHz if I set it @ 1,62 GHz using FauxClock app?
[Nexus 7 (2013) Original Android Development] nikr123:
You have read the FAQ?
[Nexus 7 (2013) Original Android Development] matcho13579:
EDIT// Oh, I see it now, sorry
[Nexus 7 (2013) Original Android Development] nikr123:
OK, it was just to make sure that you didn't have input boost enabled.
[Nexus 7 (2013) Original Android Development] matcho13579:
Actually, there is the question for it in FAQ
[Nexus 7 (2013) Original Android Development] optimusG:
So you say that tegra is more battery efficient than snapdragon. Can't say so... Also you forget that 2012 model has larger battery.

Sent using Tapatalk
[Nexus 7 (2013) Original Android Development] Skinpipe:
no im not saying that, purely talking about idle not actual use, and how much a device drains per hour has nothing to do with battery size.

sorry for the OT
[Nexus 7 (2013) Original Android Development] optimusG:
I don't think that is true. For instance, 1% drain is different in batteries which have different capacities. Do the math.

To end this OT, I would say, without having the previous nexus 7 and performance wise, the tablet's idling eficiency is great with this kernel.
[Nexus 7 (2013) Original Android Development] akaHardison:
Will this kernel will post for nexus5?This kernel is awesome.Many Plug,many governor and less battery.
[Nexus 7 (2013) Original Android Development] RealSlimShadyMC:
[MENTION=3847629]Tk-Glitch[/MENTION] kernel panic, it was a watchdog bark. All settings stock apart from smartmax governor, showp mpdecision and 'improved' on all settings which is stable on other kernels. https://www.dropbox.com/s/sv6wa5k40x8uxc4/last_kmsg
[Nexus 7 (2013) Original Android Development] timbohenry:
Latest update seems to drain the battery a lot faster than two versions before. Anyone experiencing the same?
[Nexus 7 (2013) Original Android Development] Divine_Madcat:
Not really, no. have you dont any checks to see if you have a program holding a wake lock?
[Nexus 7 (2013) Original Android Development] kingston73:
Just curious, if I flash an aosp version on a cm ROM or the other way around, what will happen? Easily reversible or really bad?
[Nexus 7 (2013) Original Android Development] :
Some have not lived to tell their tale....

Lol from what I've heard it will either not boot or colors will be messed up.

A quick boot to recovery and flashing the correct version does the trick.
[Nexus 7 (2013) Original Android Development] kingston73:
Thanks, is wanted to make sure.
[Nexus 7 (2013) Original Android Development] bmccoy11:
Same exact problem with me. I've contacted TKGlitch about it. It has to do with the SmartMax governor. For now, I would recommend disabling it.
[Nexus 7 (2013) Original Android Development] Medel-Silver:
I have smartmax (with my configuration) 2 months ago and no problem, I can't report any problem :confused:
[Nexus 7 (2013) Original Android Development] bmccoy11:
I'm pretty sure it's related to the latest Cyanogenmod nightlies, so the bug may or may not be there depending on your exact configuration.
[Nexus 7 (2013) Original Android Development] beats4x:
[MENTION=3847629]Tk-Glitch[/MENTION] haven't stopped by in a while, been teaching myself java and how to build roms n cherry pick, just saw r140.1. Instantly downloaded and flashed. Dude, it just keeps getting better and better! Loving this kernel man. Keep up the great work sir ????

Sent from my Nexus 7.2
[Nexus 7 (2013) Original Android Development] treehugger38294:
I'm new to the Nexus 7 sorry, but I'm rooted with stock ROM and franco. should I still reflash?