yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] TunedFish:
I use CF-Bench to find the highest oc frequency. Depending on where in the test it reboots, I adjust my settings to make it stable or lower frequency.
[Nexus 7 (2013) Original Android Development] notoriouspk:
official aokp with latest 9 Oct kernel for Cm only running smooth thanks
[Nexus 7 (2013) Original Android Development] timrock:
Magnetic on/off is not working for me. I left it unchecked and it did not sleep when I closed my case. So I flashed again and checked the option and its still the same.
[Nexus 7 (2013) Original Android Development] farmer bobathan:
Magnetic on/off works fine for me.
[Nexus 7 (2013) Original Android Development] MoooN:
[MENTION=227267]glitch[/MENTION]

Im using carbon nightly with your non cm kernel

Watching Standart 720p h264 videos with mx player hardware decoding
[Nexus 7 (2013) Original Android Development] Grondinm:
Hey TK. I'm being a pain i know.....Any chance/possibility of integrating/switching to BFS?
[Nexus 7 (2013) Original Android Development] commuterbox:
Same problem I'm having using mxplayer. I'm on 10/07 CM, I did not have this problem when i was on 9/28 cm with 9/25 r15 glitch.

Sent from my Nexus 7 CM10.2 Glitch kernel
[Nexus 7 (2013) Original Android Development] timrock:
i will try reinstalling again, and leaving the box unchecked.

what rom are you using? im on PA.

edit: yep, it doesnt sleep.
[Nexus 7 (2013) Original Android Development] farmer bobathan:
I'm using the CyanogenMod kang by DJL.
[Nexus 7 (2013) Original Android Development] timrock:
yeah, there is something wrong. I just flashed Carbon. I didnt flash Glitch though. And when i closed my case, it went to sleep. So installed the kernel, and now it doesnt sleep. So now i have had this issue with PA and Carbon. And the funny thing is, if i flash a different kernel, i will still have this issue. Only way to fix it, is a hard reset.
[Nexus 7 (2013) Original Android Development] penguin449:
Because you probably disabled the magnetic on/off option in Aroma :rolleyes:

Use trickster mod and see if there's an option for it in "screen wake" or whatever it is :p
[Nexus 7 (2013) Original Android Development] timrock:
i didnt disable it. i left everything as is. There is no option in Trickster. I checked. Only for sleep2wake. Also checked Faux Clock.
[Nexus 7 (2013) Original Android Development] penguin449:
Wipe caches, flash kernel, fix permissions, reboot ;) try again and if not, choose a different kernel bro /:
[Nexus 7 (2013) Original Android Development] timrock:
yep, did all that too. only thing with choosing a different kernel, is now i have to hard reset again.

what do you mean "fix permissions"?
[Nexus 7 (2013) Original Android Development] Grondinm:
So i have noticed with the latest version(Oct-09) that double tap to wake seems to not be as responsive. Maybe it's just me...anyone else noticing issues with double tap to wake?
[Nexus 7 (2013) Original Android Development] penguin449:
Advanced>fix permissions in your chosen recovery.. And no you dont? O.o you can flash any kernel over any kernel.. Just wipe caches, flash kernel, fix permissions, reboot :p
[Nexus 7 (2013) Original Android Development] timrock:
im going to try that, but what i meant was, in order to get that functionality back (sleep when closed), i will have to hard reset.
[Nexus 7 (2013) Original Android Development] farmer bobathan:
It may be that I am using the AOSP version of Glitch, not the CAF version.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I was moving to another city these last days, so it was hard to answer sooner. Sorry about that.

Thank you to volunteer. If I'm in need I'll think about you (strange way to say it but well..).

I tried (and I'm not the only one it seems), but it doesn't really work. So no.

Do you happen to have more about this ? I couldn't find the changes myself. Though keep in mind my kernel is using anykernel and the only file I'm replacing in ramdisk is fstab.flo.

Thank you !
[Nexus 7 (2013) Original Android Development] bmccoy11:
Sorry, I can't find it either. I just read this and thought I should post it here. I haven't tested this kernel on the latest 12.1 nightly, so I'm not sure if it works or not...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5637619]bmccoy11[/MENTION]

Let's dig then !

Edit : No issue so far with latest CM 12.1 and r344.
[Nexus 7 (2013) Original Android Development] masri1987:
hey [MENTION=3847629]Tk-Glitch[/MENTION],

I had to roll back to Kitkat, where can i find the latest AOSP kk kernel?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2694397]masri1987[/MENTION]

r226 was the last Kitkat release. You should be able to find it on all mirrors in OP.
[Nexus 7 (2013) Original Android Development] CYoung234:
I installed r344 on my Nexus 7 yesterday. When I woke up this morning, my tablet would not wake up. I dirty flashed the ROM to get back to the stock kernel. Attached is a logcat, but I am not sure it will show anything. I had to zip the logcat, as it exceeds the size limit here on xda. I was running 1728MHz max frequency, a 2048kb cache size and 545MHz for the GPU max. These are all values that have run well in the past. I was having a similar problem with r330.
[Nexus 7 (2013) Original Android Development] creeve4:
What other settings are you running? Any gamma adjustments, UV, what's your min CPU freq, etc...?
[Nexus 7 (2013) Original Android Development] CYoung234:
Everything else was default values. I will post the settings file if I kept it. I am not sure if that shows all of the settings, though. Everything else was defaults.
[Nexus 7 (2013) Original Android Development] magarto:
I have the same problem. Battery on gone. I am waiting for it to charge a few to be able to boot it again
[Nexus 7 (2013) Original Android Development] bart.found:
I had a SOD too.. same settings was working on previous version..
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Can I flash this update directly overt the last update?
[Nexus 7 (2013) Original Android Development] jmsaye:
I'm using the latest r344 CM version and most of the governors are missing. The only governors showing up are: intelliactive, interactive, conservative, userspace, ondemand, and performance.

I did a full install of the kernel on a fresh version of CM--well, sort of. I updated the nightly so it had default kernel, let it boot, then when back to recovery and installed the full aroma installer version (not the restore one) making sure to do the full install. I even selected smartmax as the default governor to see if that would install it, but it was still missing. I also checked with several different kernel management apps (Trickster, Kernel Adiutor) on the off chance that it was just a bug in the app, but still no go.

Am I doing something wrong or is it a bug? Or were they removed and I just can't find that in the changelog?
[Nexus 7 (2013) Original Android Development] MaddMaxx636:
having problems left and right on the latest CM12.x nightlies

Ive been running on the same settings for weeks more like months. My kernel setup settings are

Min: 81

Max:2.16GHz

L2: Glitchy (1.49GHz-4.80GBps)

GPU: 545MHz

Undervolting: GPU -75mv CPU: -150mv

Note: these i cant remember every detail about the settings. So i guessed for the undervolting settings i use!

Ive been using these setting stable for months and had no problems but after a date on the CM12.1 nighties i was having crashing left and right. Like Apps crashing, Apps freezing, crashing (Soft Booting) to black screen, sound would randomly soft playing and then the app would crash, and any other things involving the system being unstable.

Has anyone else had these problems? i'm running 06-20-2015 nightly but it started a few nightlies ago.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Where is [MENTION=3847629]Tk-Glitch[/MENTION]? He said he was moving, but hope he's okay and well...
[Nexus 7 (2013) Original Android Development] playitlouder:
Is anyone else experiencing a Soundcloud crash when trying to play a song?

Using Glitch with f2fs.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Did you consider that possibly it's just a soundcloud issue? I use an older version of the app for better upload functionality and viper compatibility. Try this one to test...

https://www.dropbox.com/s/asqtfq95s91jf3e/com.soundcloud.android.apk?dl=0

And also consider adjusting your OC and OOM values to ensure it's not just a matter of the app being killed by android's RAM manager...
[Nexus 7 (2013) Original Android Development] freddienuxx:
When I flash latest Glitch over blisspop I lose data!

Is there a fix for it? I tried using boot permissive mod from beanstalk rom/deb and no dice. I would appreciate the help Thx In advance

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] akipapa:
I keep encountering freeze / reboot issue with glitch + cm 12.1, and quanta kennel acts the same.

My memory is not so clear but I think this started with recent nightlys.
[Nexus 7 (2013) Original Android Development] quickdraw86:
If you have issues with two different custom kernels on a nightly ROM build, it's likely the ROM, not the kernels. Dirty flash your ROM onto itself to rewrite the stock kernel, see if you experience any issues on stock, or try a different ROM.
[Nexus 7 (2013) Original Android Development] akipapa:
Yeah, that makes sense.

I'm considering to roll back to earlier CM nightly builds or try another ROM.

The thing is I formatted /Data and /Cache to f2fs, so I don't have too many choices.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Yeah, that's the thing with nightly builds, they are compiled and released, sometimes automatically, no testing or promise of stability whatsoever.

If you mean that you don't have many choices on the ROM side, you could always modify the install script of the ROM you want to run to mount the data and cache partitions as/in F2FS. If you reboot into recovery, you'd only have to perform a clean wipe, flash the ROM with the modified install script, flash an f2fs enabled kernel, and reboot...
[Nexus 7 (2013) Original Android Development] akipapa:
Thanks for the info, I will do some homework when I got some time to catch up on what you said.

For now, I will test a few more nightly builds to see if things are going to change.

Once I met a stable build, I'd keep it out of the CMUpdate folder, or it will be automatically removed and the CM update server only keep really few latest builds... I was trying to download an earlier build but most of old builds are gone :(
[Nexus 7 (2013) Original Android Development] quickdraw86:
Hmm... The website has nightlies going back all the way to 4/29/2015...

http://download.cyanogenmod.org/?device=flo
[Nexus 7 (2013) Original Android Development] playitlouder:
How is your battery life (especially standby) with CM12.1 offical?

I had horrible battery drain the other day (just got a day of battery life) and now it has been going for 2Days and 3h (48min Display) with 28% remaining.

I am using double tap to wake (does this really drain battery?) and f2fs, so testing battery life on stock kernel is kinda out of question.

EDIT: [MENTION=3847629]Tk-Glitch[/MENTION] can you get rid of that touch_boost thing that is spamming the logcat because it cannot communicate to the Google Power HAL?
[Nexus 7 (2013) Original Android Development] akipapa:
Thanks, but most of those links gave me a 404 error.

The earliest build I could get was 6-21.

Hope they would push a stable build in the near future.
[Nexus 7 (2013) Original Android Development] poondog:
About the power HAL message, you will find this info useful :)

http://xdaforums.com/showpost.php?p=46507552&postcount=2

Its the powerhal on the rom side complaining that the kernel isn't responding to its cries to boost (because the boost drivers have been replaced and the binaries in the rom have not)
[Nexus 7 (2013) Original Android Development] quickdraw86:
That's too bad... There is a device maintainer for flo, so not improbable even for a stable build in the future.
[Nexus 7 (2013) Original Android Development] pk-sanja:
I smell a new release :D

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Hatshipuh:
And it works! It booted at least and running fine so far...for the past few minutes ;)

Don't know if it's a placebo or if it has anything to do with the kernel at all, but touchscreen feels a lot more responsive.

Tap-a-talked from my Nexus 7
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's time for a new release !

Nothing major but well needed fixes and updates as well as a feature a few users asked for. Here are the changes :

02/07/2015 - r350 :

- Merged with android-5.1.1_r0.13 changes

- Fixed missing governors from previous release

- Added native support for Xbox One controller from Linux 3.17

- Fixed a potential instability case in idle state

- Updated base to linux 3.4.108

- Under the hood fixes

- CM and AOSP kernels are now sharing the exact same base for better stability and maintenance

Note : I'm well aware of the power HAL spam on the rom side. I'll try to find a solution to this that suits me.

It is not critical and shouldn't impact user experience or stability btw.

I can't upload to xda servers ATM, but you will be able to find the new release on both mirrors.
[Nexus 7 (2013) Original Android Development] tetakpatak:
Awsome, CM and AOSP kernels sharing the same base now! :)

tetakpatalked from 1+One
[Nexus 7 (2013) Original Android Development] freddienuxx:
Don't get it 344 and 350 I flash cm version and no data for N7lte

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Does it work with other kernels and same rom ? I don't have a deb to experiment with but if it's something on my side it should be fixable.
[Nexus 7 (2013) Original Android Development] echoot:
Yeah. Me too. The selinux patch still installed although i not tick that option. On chroma rom. Clean flash.

---------- Post added at 02:24 AM ---------- Previous post was at 02:07 AM ----------

Data works on stock kernels on chroma. Also with elementalx.
[Nexus 7 (2013) Original Android Development] freddienuxx:
Where is that patch [MENTION=4089490]echoot[/MENTION]?

I tried the one from Beanstalk thread n7lte an it didn't work

Sent from my Nexus 6
[Nexus 7 (2013) Original Android Development] echoot:
The option of the patch is in glitch kernel installer itself. You can find it there.
[Nexus 7 (2013) Original Android Development] TheC92:
Bug?

Rom : 5.1.1(LMY48G) Stock
[Nexus 7 (2013) Original Android Development] freddienuxx:
Oh OK thx

Sent from my Nexus 6
[Nexus 7 (2013) Original Android Development] masri1987:
what's everyone using for kernel control? fauxclock?
[Nexus 7 (2013) Original Android Development] aoaleman:
Kernel Adiutor.
[Nexus 7 (2013) Original Android Development] masri1987:
wow this app is so much better than fauxclock already.

jesus

thank you man
[Nexus 7 (2013) Original Android Development] tibere86:
I'm still partial to Trickster.
[Nexus 7 (2013) Original Android Development] bart.found:
Ukm+synapse
[Nexus 7 (2013) Original Android Development] kodora:
+1 on that combo and so far no problems at all [emoji1]
[Nexus 7 (2013) Original Android Development] CYoung234:
For me Kernel Adiutor. I have used trickster and UKM / Synapse in the past.

On another note, I discovered yesterday that using Glitch on my ROM affects playing videos. I use Miracast to do presentations, and found that when I had Glitch installed with my ROM (Exodus right now), that videos do not play correctly. With some ROMs it seems to only affect sound, but yesterday, it simply said it could not play the video. The stock ROM plays it fine. I was overclocking but only to 1728 with the GPU at 545. and the buffer size set for 2048. I will look at it further and can provide a log cat later.
[Nexus 7 (2013) Original Android Development] klaust58:
If I remember correctly, I had timeing problems with 545 MHz GPU when playing games. This is too much and does not improve.

Yes! Kernel adiutor is fine! Or trickster. I personally don't like synapse....

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] CYoung234:
Thanks. I will do some more testing at stock clocking to see if that helps. I will also post a logcat later. I have a presentation to do later today though, so not until I finish that...
[Nexus 7 (2013) Original Android Development] masri1987:
not sure why double tap to wake isn't surviving a reboot of the tablet. I have to set it every single boot.
[Nexus 7 (2013) Original Android Development] CYoung234:
UPDATE:

Attached are several log cats for this problem. I have found that installing Glitch R344 or R350 is killing the sound at a minimum in video playback, and often causes the video player app to say: Cannot play video. This is true with both Exodus and Dirty Unicorns. I have not tested it on other ROMs yet. Also, the GPU frequency appears to have no effect. The problem occurs at stock frequencies as well.
[Nexus 7 (2013) Original Android Development] bart.found:
I have a little issue with this kernel... My flo doesn't charge over 85% even if I flash the full version of the kernel without selecting battery life extender option... Can you help me?
[Nexus 7 (2013) Original Android Development] quickdraw86:
You need to delete the glitch settings backup file from the root of your SD card reflash a full version, and reconfigure as you wish in aroma to change the setting. Otherwise, a full version will restore from the settings backup file that was created when you installed a full version and it booted successfully. Look for the full filepath for the backup file you need to delete in the OP, all the information you need is there.
[Nexus 7 (2013) Original Android Development] masri1987:
any ideas guys?
[Nexus 7 (2013) Original Android Development] quickdraw86:
There's no need to quote yourself. I replied to your original post, if that didn't get it working for you, I'm sure others would chime in if they had an idea to share.
[Nexus 7 (2013) Original Android Development] masri1987:
sorry, i didn't see where you responded? I still don't see it
[Nexus 7 (2013) Original Android Development] quickdraw86:
It was post #2444 in this thread, the post before you quoted yourself. Try desktop view in a browser if you're having trouble seeing posts.
[Nexus 7 (2013) Original Android Development] masri1987:
ah didn't recognize itw as for me because i wasn't quoted, someone else was (surely by mistake). I will try this out and re-test.

Have you any idea regarding what kernel app i should use, kernel auditor is what i'm using right now
[Nexus 7 (2013) Original Android Development] quickdraw86:
Fauxclock and trickstermod are the apps recommended in the OP. I use trickstermod myself, but I'm sure kernel adiutor is fine too.
[Nexus 7 (2013) Original Android Development] montbazon:
My n7 doesn't fall to deep sleep.

Anyone has this same problem?

I'm using cm12.1 29 July and glitch r350 for cm.
[Nexus 7 (2013) Original Android Development] neo_1221:
Nope, working fine for me - on Xenon HD r2b6.
[Nexus 7 (2013) Original Android Development] montbazon:
Hmmm.. I'll factory reset asap and report again.
[Nexus 7 (2013) Original Android Development] tungdil:
[MENTION=4089490]echoot[/MENTION] could you solve this problem? I have -- since long -- tried using r350 on AICP with the same problem. Actually I tried both, Glitch-N7-r350-CM-restore.zip and Glitch-N7-r350-CM-full.zip with the same result. In glitch-settings.conf I find:

##### Enforce Selinux #####
# 0 for default
# 1 to enable permissive Selinux

PERMISSIVE=0
[Nexus 7 (2013) Original Android Development] echoot:
Nope [MENTION=5098312]tungdil[/MENTION]. I think its still persist. Lets the dev [MENTION=3847629]Tk-Glitch[/MENTION] fix this bug.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Glitch has been updated to r353... I wouldn't have noticed if I hadn't looked right at the thread title as I was scrolling... Have a look at the changelog if you use the CM version... Will try new version tonight, thanks for the update.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's time for a new release ! I've been hard at work so it was hard to find the time for this but well.. I hope you'll like it ! Enjoy !

09/09/2015 - r353 :

Note : CM related issues some are encountering aren't adressed with this update. CM team is breaking more and more stuff while using AOSP bases for the kernel and I won't make a CAF based version again. The updated toolchain and added fixes in this release may or may not help, but I won't provide support for CM related issues anymore. Sorry for the inconvenience.

- Fixed SELinux switches (You'll need to use the restore function in full package or just the restore package to switch between permissive and enforcing modes. Enabling it in glitch-settings.conf isn't enough for it to work.)

- Disabled Android Logger by default for less overhead

- Updated toolchain to Linaro GCC 5.2.0 with LTO support

- Tiny fixes
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks for the update... Will give it a whirl tonight...
[Nexus 7 (2013) Original Android Development] akhi24nick:
After flashing it on latest Chroma. Sim doesnt get detected. Should I clean flash? or is it a known issue?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Phase two, more "major" update than the tiny last one. It should fix various issues (on the CM side of things as well btw).

13/09/2015 - r360 :

- Merged with android-5.1.1_r0.17 changes

- Added Lazyplug hotplug driver by Arter97 (you may need to make a full installation first if you want to switch to this driver)

- Updated F2FS

- Updated BFQ to v7r8

- Added experimental Nvidia relaxed power savings

- More fixes and various optimizations regarding performance and efficiency

Enjoy !

Note : I can't upload to XDA currently (server I/O error), but the update is available on both mirrors.
[Nexus 7 (2013) Original Android Development] JeanEatsWorld:
You are awesome. Period.
[Nexus 7 (2013) Original Android Development] brolic925t:
I was losing hope in my beloved flo
[Nexus 7 (2013) Original Android Development] treehugger38294:
Kernel looks great but I have a question. I just set the GPU to 504 Mhz in AROMA. When I enter the ElementalX app, it says that both the max and min gpu frequency is 504. Is this correct or is the app wrong because I think this will drain a lot of battery?
[Nexus 7 (2013) Original Android Development] quickdraw86:
In my case, i set my GPU max to 504 max in aroma as well (I'm using r360 AOSP), and am using kernel adiutor. Kernel adiutor doesn't have information about a GPU min, but my average GPU frequency seems to be 128.

That said, I haven't tried the latest CM version, and have no idea which version you're using, release number? AOSP? CAF?

But, in any event, I would at least try a different kernel app to see what values it reports before considering that there may be a problem with the kernel. Just my opinion.
[Nexus 7 (2013) Original Android Development] treehugger38294:
I tried the app you mentioned and it seems the frequency changes so ElementalX must just be malfunctioning.
[Nexus 7 (2013) Original Android Development] nazfalas:
I am getting no radio on deb with the 360-CM version on Exodus ROM.