yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] sizzlers:
Nvm,mistake from my side,fixed and flashed it ;)
[Nexus 7 (2013) Original Android Development] averagegeek:
No, I didn't.. But on CM Rom, issue isn't there.. It works perfectly fine. The issue was there when I was using an AOSP ROM (Dirty Unicorns 5.0.2)
[Nexus 7 (2013) Original Android Development] limzm:
Nope, I didn't use the permissive patch.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Definitely strange.. Maybe some kind of wakelock on Dirty Unicorns then. Thanks, I'll see what I can do.

Ok, thanks for the input. Probably the fstab then. I'll experiment and push a hotfix if I'm successful.
[Nexus 7 (2013) Original Android Development] Jâgôôô:
hejj guys...

Sorry for the stupid question.. but witch kernel i must download?? for cm 12 .

i think the glitch 307 cm? or the glitch 307?

Thx anyway
[Nexus 7 (2013) Original Android Development] tetakpatak:
The question is really stupid, but there is some hope left as you have partly answered yourself. ;)

Why don't you read the first posts? What if somebody advices you to flash a wrong kernel version?

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Original Android Development] bmccoy11:
Has Cyanogenmod made any kernel changes in the last few weeks? I'd like a rebuild for CM because it's been a while since r307 was compiled. Also, I noticed Cyanogenmod added native double tap to wake/sleep in the settings, but double tap to sleep is the only option showing up with this kernel. The double tap to wake option is available when searched for, but doesn't show up when you try to get to that setting.
[Nexus 7 (2013) Original Android Development] poondog:
There have been a few minor changes, nothing more than a few bugfixes.

Also there is no native 2w supported in CM's kernel

https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-12.0
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
You suggesting users read the OP?

Mad talk...can only end in disaster...
[Nexus 7 (2013) Original Android Development] iaTa:
On many differet ROMs (Freak SlimLP, Screw'd, Rasta) I'm seeing hours and hours of 'suspend_backoff' and 'qcom_rx_wakelock' wakelocks.

I see this was an issue with a buggy base 6 months ago (link), could it be the same thing causing a problem now?
[Nexus 7 (2013) Original Android Development] limzm:
Looking forward for the USB-OTG bug to be fixed.

This kernel has to be the best to date for Nexus 7 2013.

Currently using other kernel and disliking the way it performs.
[Nexus 7 (2013) Original Android Development] SerJo87:
Hello. Who can share this great kernel settings for the best energy efficiency, without compromising the smoothness? Thank you
[Nexus 7 (2013) Original Android Development] bmccoy11:
I've been getting lots of random reboots and horrible slow downs with this kernel, so I switched to ElementalX and now Cyanogenmod seems to be running a lot more smoothly. I believe the ondemand governor is causing the reboots, but I haven't really looked into the logs after the slow downs. I think it is a memory leak.

http://review.cyanogenmod.org/#/c/89528/

There have been some other changes in the Cyanogenmod kernel lately, so a rebuild would be nice.

I'd also like a flashable .zip that automatically restores settings from the SD card without having to go through the Aroma installer for every ROM update. Can you make that a thing, Tk-Glitch?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
"suspend_backoff" is from S2W/DT2W and "qcom_rx_wakelock" is from wifi. Disabling S2W/DT2W or setting a timeout for it should fix the first one, and disabling the two "always on" wifi features (always + in sleep) should fix the second one. I'll see if I can do something to help for the wifi part on the kernel side.

I'm working on CM12 updates, and I hope it'll at least fix most issues. BTW the patch you linked isn't for the kernel ;)

I still have a hard time finding time to continue my work on the non-aroma update. I'll keep you all informed when I'm closer to something that works.
[Nexus 7 (2013) Original Android Development] iaTa:
That's odd as I always disable S2W/DT2W in the kernel setup procedure.

Thanks for looking at the wifi though.
[Nexus 7 (2013) Original Android Development] farenteria:
Everything default with screen-off settings turned off
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION] Is my problem related to the kernel or to the ROM? I got a problem with my FAT32-formatted pendrive - when I plug it in, tablet is recognizing it fine, it tries to mount, but fails everytime. After that, I'm unable to use it anywhere because of the damaged partition
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I think it's linked to some of my (old) ramdisk modifications.

I'm currently reviewing it all and cleaning it up. It'll be much more robust and should help for the future non-aroma installer as well.

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

New update guys ! It should fix most issues with permissions, OTG, as well as CM based roms.

Feel free to report any problem you may encounter, as always.

Here's an overview of the changes :

07/03/2015 - r320 :

THIS UPDATE WILL NEED YOU TO REINSTALL YOUR ROM AND TO MAKE A FULL INSTALLATION OF THE KERNEL IF YOU'RE COMING FROM A PREVIOUS GLITCH RELEASE

- Updated F2FS implementation and bumped to latest

- Various scheduler optimizations - Better hardware use means potentially lower max OC !

- Improved boot times (At least with EXT4. F2FS mounting time feels a bit longer with the updated F2FS implementation)

- Reverted Slimbus OC as some users got issues with it

- Removed some ramdisk mods interfering with permissions

- F2FS/EXT4 detection script rewrite to preserve rom's fstab structure

- Added another permissive switch to disable SELinux enforcing (it will be enabled if you tick the permissive patch in aroma)

- Removed wifi patch from Aroma as it's now useless with lollipop

- Added some security patches from CM source

- CM kernel rebased on Glitch AOSP (again) - Looks good after a few days of intensive use

- A few little glitchy tweaks

- Updated toolchain to Cortex A15 optimized Linaro GCC 4.9.3-2015.02

Enjoy !
[Nexus 7 (2013) Original Android Development] atlharp:
Awesome. Nice to see this updated! ?
[Nexus 7 (2013) Original Android Development] matcho13579:
Can confirm that OTG works brilliantly, thank you Glitch!
[Nexus 7 (2013) Original Android Development] tetakpatak:
Amazing update, [MENTION=3847629]Tk-Glitch[/MENTION] :)

Hey, I'm glad to see you working, so are you feeling any better in general finally? All best for you, mate!

tetakpatalked from N7100
[Nexus 7 (2013) Original Android Development] pk-sanja:
[MENTION=3847629]Tk-Glitch[/MENTION] thank you Glitch for your hard work. Wonderfoul update for an awesome Kernel. Do you change your settings with r320 :)?
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
[MENTION=3847629]Tk-Glitch[/MENTION] overwhelmed by the update, awesome work dude!

Works flawlessly!

Sent from my Resurrected flo powered by elemental x and kanged by Xposed with power of MultiROM!
[Nexus 7 (2013) Original Android Development] andyman_187:
Awesomeness!! Just to clarify, is it ok to dirty flash current ROM then install r320?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4219722]andyman_187[/MENTION]

Indeed, a wipe isn't required. A dirty flash of the ROM is enough :)

My personnal settings are the same as before :)

Thank you sir. I'm feeling better indeed. It should only get better and better :)
[Nexus 7 (2013) Original Android Development] matcho13579:
One question - is it possible to have more than one USB flash drive mounted at the same time?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3845051]matcho13579[/MENTION]

Android can do it, though the limited power coming from USB on the Nexus 7 2013 could be a limiting factor. If it doesn't work as is, you may want to try with a powered hub.
[Nexus 7 (2013) Original Android Development] Szighy:
what if I'm on stock rom, should I reinstall that too? how am I supposed to do that? :P
[Nexus 7 (2013) Original Android Development] VictorLapin:
Reflash stock kernel :p
[Nexus 7 (2013) Original Android Development] habylab:
Hoping this fixes my screen off deaths!

Cheers!

Sent from my Nexus 9 (2015). My phone is a HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION] Weird.. msm_otg is waking up the device: https://www.dropbox.com/s/zwwlha98upg4s0o/Screenshot_2015-03-09-08-45-31.png?dl=0

EDIT// I came up with the cause of the wakelock - tablet was plugged in the charger when I booted it last time. I rebooted and it's fine now
[Nexus 7 (2013) Original Android Development] habylab:
Deep sleep issues fixed, so happy! Using ondemand now, maybe better than intellidemand even!

Sent from my Nexus 9 (2015). My phone is a HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
I got screen off deaths on xenon HD ROM too.

Sent from my Resurrected flo powered by elemental x and kanged by Xposed with power of MultiROM!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
No OC I suppose ?

If you're using S2S/S2W/DT2W, could you please try to disable them and see if it fixes your issue ?

Using CM12, stock and AOSP roms it didn't fail on me once, either during development, testing phase or now after release - though, I'm not using any of these features.
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
I switched from xenon HD(CAF) ROM to Simple AOSP(AOSP) ROM now and using kernel with OC (1.9Ghz for CPU and 550MHZ for GPU) and D2TSW feature, not getting any screen off deaths.

Earlier on xenon HD I used the same settings but got screen off deaths, maybe a ROM fault?

Sent from my Resurrected flo powered by elemental x and kanged by Xposed with power of MultiROM!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Well, maybe.
[Nexus 7 (2013) Original Android Development] Chief_Death:
Hi, I use Glitch kernel with CM nightly builds, data & cache are F2FS. My tablet doesn't seem to want to go to deep sleep (stays awake almost continuously in battery view). It has been happening since 307 but 320 didn't fix it. In addition it seems to randomly (when screen off) reboot every couple of hours (just reboot no bootloop).

I don't have any OC or UV and I have tried disabling S2S/S2W/DT2W settings but it didn't work. Any idea on what might be causing that?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I'd say my incompetence at working with CM sources on the N7.

Though it works fine on my side with a CM12 nightly from early March so I'm lost here.

I may end up dropping support for good. It's really not worth the hassle if you ask me.
[Nexus 7 (2013) Original Android Development] habylab:
My issue was fixed with the new release! Now I can keep my tablet on! Thanks

Sent from my Nexus 9 (2015). My phone is a HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] Impact7:
Maybe I'm stupid but why does the new kernel force me to reinstall my ROM?

If I install the kernel and afterwards the ROM wouldnt this overwrite the kernel?

And flashing kernel after ROM is the same as keeping the current ROM and flash the kernel.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
You're right to ask if you want to understand :)

Easy answer : you need to restore the ramdisk that came with your rom as well as some system files potentially modified by an older version of the kernel.

Complete answer :

Before r320, the kernel didn't come with a complete ramdisk, but only one critical file (fstab.flo, responsible for the partitions mounting). Other modifications to the ramdisk were done by editing current ramdisk files directly via script. Depending on your choices during installation, some system files could be replaced as well.

The problem with that is the fstab.flo file I made was non-standard, with two lines for system, data and cache partitions instead of one (one for EXT4, the other for F2FS). At flash time, a script was reading the format of each partition to comment or uncomment the required line, so it mounts with the correct filesystem at boot.

Now with r320, it comes with even less of a ramdisk as I'm not replacing fstab.flo anymore. I'm first reading the format as before, then once I know, I'm checking in the current fstab.flo if the line for each partition corresponds to the format. If it isn't, I'm replacing the line with the correct one depending on the format. This way it won't break potential mods made to this file by the rom cooker and can survive forks, CM, AOSP, stock, and Android updates.. As long as this file is responsible for partition mounting. After that, other modifications to the ramdisk are done as before - but - many of them were generating issues, so they were removed.

Since the kernel only modifies your current ramdisk, it'll keep the mods made by r307 or older and try to work with them. But it just can't. You'll end up either with an unbootable system or with some ramdisk-linked issues that came with r307.

BTW, flashing the kernel then the rom will indeed overwrite the kernel.

Since most users don't care about that technical part, it's safer to just say "please reflash your rom before updating to r320" but I'm glad some are asking.
[Nexus 7 (2013) Original Android Development] bigknowz:
SOD

Also getting SOD with Purity ROM. I'll try disabling S2S/DT2W.
[Nexus 7 (2013) Original Android Development] _delice_doluca_:
Thanks for the beautiful kernel. I am using it on 1.9 GHz with -75mV and GPU 600MHz with -25mV, without any further tweaking other than disabling the magnetic cover thing. It passed all the CPU and GPU benchmarks without getting too hot or turning off.

One thing bothers me though; I know its not gonna turn into a S800 chip by only OCing but I would expect more performance, at least on the Dead Trigger 2 game. It runs on "low" graphics, slightly lagging on "medium" and unplayable on "high". Other games like Asphalt 8, Real Racing 3 and Subway Surfers seem just fine.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Asphalt 8 and RR3 are both using a frame limiter where Dead Trigger 2 doesn't, so depending on your chip it could be some throttling. Too high of a bus OC can lead to RAM corruption, too. While not necessarily leading to a "clean" crash, it can slow down things heavily as the memory is shared between GPU and system.

It's been a while since the last time I played Dead Trigger 2 though I remember it was playable on many levels at ultra settings (spoofing Tegra 4 with GLTools), though hardly playable on others. High was mostly smooth though (I'd say between 30 and 60 fps depending on the scene complexity), but that was on Kitkat. I'll check again on Lollipop with various settings and keep you updated on my findings.

Have a nice day !
[Nexus 7 (2013) Original Android Development] idCyber:
Can you please post all your Aroma settings that you use?

Edit: No SOD here on AOSP ROMs.
[Nexus 7 (2013) Original Android Development] pk-sanja:
I'm not the badass Tk-Glitch [emoji14], but i use his Settings too. He uses 1,7 GHz for thr CPU with 1025mV, GPU 600mhz with -100mv, OC BUS Glitchy and swipe to wake and everything else off. Hope it helps and i'm correct :).
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
So, I played through a few levels (damn it's a completely different game now !) and found out that basically, they made the "high" settings the same as the old "ultra" (and I guess the current "ultra" is now scaled for the Tegra K1 instead of the Tegra 4), so our devices aren't powerful enough to be able to play at "high" settings smoothly, even with an heavy overclock. Following the same path, "medium" is the old "high" and should be the best compromise between visuals and smoothness for the N7 2013. An overclock will help to go from "playable" to "mostly smooth" at this level of detail. The new "low" is the old "medium" as well, so I suppose many entry-level devices are now unable to run the game.

But in the end, yes, "medium" is what you should use on the current version of the game, on the N7 2013.

You are correct indeed.
[Nexus 7 (2013) Original Android Development] _delice_doluca_:
My friend you are the most concerned, most helpful developer I have ever seen. Thank you very much, really. You installed and played a game just to understand a user's problem which could have not even be related to your kernel. Thank you.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I'm glad to be helpful when I can, and understanding things at the same time is even better.

Thanks to you to be the nice person you are. That's the people like you who makes the well hidden great community of XDA forums.

I'm pleased to see that many nice people on this thread. Stay awesome guys !
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
I can't resist you are an awesome guy!

Sent from moto e (condor)

---------- Post added at 04:15 PM ---------- Previous post was at 04:13 PM ----------

I remember you, you are the current record holder for the antutu score, you whooped a jaw dropping 35000+ score on my thread in general section.

Can you post configurations you use!

Sent from moto e (condor)
[Nexus 7 (2013) Original Android Development] pk-sanja:
Yes of course :),

I use 1,7Ghz for the CPU with 1050mV, OC-BUS glitchy and 600mhz for the GPU with -150mV, everything else off. Hope it helps :).
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
The 35k record you did hit wasn't on 2.2GHz and was at 1.7GHz?

If it is its impressive,BTW I think higher OCs than 1.9 can lead to instability and scores fell off,benchmarks looks good on papers but for real time usage I think your config is great!

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] pk-sanja:
Yes the 35K Benchmark was done with 2,1Ghz if i remember.

You,re right, above 1,7Ghz the CPU doesn't scale well anymore in my case. With my current settings, which i think are the best, i get 34000 in Antutu every turn. It doesn't make sense to go higher. I think these settings are perfect for this perfect Kernel :).
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Sure,yeah.

Thanks for letting me know the best settings :).

•Hit thanks if I helped you..:)

---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------

I can't get more than 30k+ with your current settings..

:(

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Depending on your luck at the silicon lottery, your SoC could be either unstable or throttling, or you may have some processes eating up ressources in the background.

If you're not using this setting already, you can try to set the throttling temperature higher (either from Aroma or glitch-settings.conf) and see if it helps. The highest setting I've set is still in the safe range hardware wise if you didn't tweak the script.

For information, here's what kind of scores you should hit on Antutu 5.6.x with a stable and non-throttling N7 2013 running r320 on AOSP or stock, using "Glitchy" bus OC, Fluxi's MSM hotplugging driver, 600MHz GPU clock with ondemand governor as well as deadline iosched using 2MB read-ahead buffer :

between ~32 and ~33k @ 1.512GHz,

between ~33 and ~34k @ 1.728GHz,

and more or less 35k @ 1.89GHz.

Anything stable or not throttling past this is just luck.

Keep in mind the GPU can get hot @ 600MHz, heating the CPU in the process and ending up forcing it to throttle. Also, an unstable GPU can corrupt RAM, slowing down the CPU.

Finding the perfect settings for your device can be a long task, and will need some tweaking and testing :D

Hope it helps !
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
You've wrote a theory, awesome!

I will try to test and tweak and find myself a perfect setting and if any doubt I'll be back to the thread!

Thenks!

I wish just numerically I can beat 35.5k score of pk sanja,lol!

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5652234]AnkeshReborn[/MENTION]

I wish you good luck ;)
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
[MENTION=3847629]Tk-Glitch[/MENTION] and others I seem to have issue with multi ROM with this kernel or the last update.

Anyone facing same issues?

I tried to flash many Roms which worked on earlier kernel versions but now it don't biits and bootloops to recovery again and keep restarting it every time done so,seems to be an issue with hardboot kexec patch.

I request OP Tk-Glitch to please look into the issue,I'll be too grateful to get multi boot working again with my favorite kernel.

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5652234]AnkeshReborn[/MENTION]

Multirom V31 never worked for me with any kernel and killed my previously working V30 setup.

V30 still works btw. V31y works as well (latest test version). Nothing to do with my kernel me thinks.

Either rollback to V30 or upgrade to the latest test version to fix your issue :)
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Well!

:)

Edit:Can you give me link for V31 test build,I can't find it,its being hidden from me.

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5652234]AnkeshReborn[/MENTION]

Open MultiRom manager app, go to settings, tap the version number 7 times (should be 1.177). It will then say you're a developer. Scroll down, check the box next to URL modification setting and tap on the manifest URL.

Change it from "http://tasemnice.eu/multirom/manifest.json" to "http://tasemnice.eu/multirom-test/manifest.json" then apply.

Go back to the main screen of the app and refresh. You should then get both MultiRom and recovery test updates.

Edit : Fixed, thanks [MENTION=5478526]Ænimal[/MENTION]
[Nexus 7 (2013) Original Android Development] Fivesack622:
If the wakelock keeping your tablet from entering deep sleep is called System Update Service, then this has nothing to do with the kernel... This is a known issue with the newer Google Play Services on some custom roms and currently impacts CM. It has to do with the SysytemUpdateService. If you look at CM's Github, they are currently working on a fix. Here's a link if you want to read the comments about it... http://review.cyanogenmod.org/#/c/91021/

As a temporary solution, you can use a program such as MyAndroidTools and go into Google Play Services and check and then uncheck the service called SystemUpdateService. You will need to do this every time you reboot. Alternately, if you have Tasker you can automate this process at boot by following the directions in this link....

https://plus.google.com/112425488314892935797/posts/VqubRkcTpEE

Hope this helps...

[MENTION=3847629]Tk-Glitch[/MENTION] Please do not drop support for CM. It is working perfectly for me and is my favorite of all the available kernels for the Nexus 7 2013. Thanks for your outstanding work.
[Nexus 7 (2013) Original Android Development] Chief_Death:
Hi, from BetterBatteryStates, the thing that is keeping my tablet awake is one of the kernel wakelocks "suspend backoff". Is this also related to the problem you're describing?