yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Fivesack622:
No, not to my knowledge. As far as I know, the only entry under BBS relating to my problem was System Update Service and it is under partial wakelocks, not kernel wakelocks. I never checked under kernel wakelocks however... Give me a few minutes to disable my Tasker profile and reboot so the wakelock shows up again and I'll let you know if I see anything under kernel wakelocks.

EDIT: So I do have a kernel wakelock keeping my device awake as well when I don't enable and then disable SystemUpdateService. My kernel wakelock is called "PowerManagerService.WakeLocks" and I see nothing related to "Suspend Backoff". From what I understand, Suspend Backoff is related to Wi-Fi.

I think it might be worth your time to try my suggestion. It's not going to hurt anything to try. If it works, you know that's what the problem is. If it doesn't work, I would go to the BBS thread and do some searching there for the "Suspend Backoff" wakelock , and if you don't find an answer, then post a dump file there and see if anyone can help you.

Out of curiosity, do you have any unusually high Alarms or Partial Wakelocks?
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Awesome,wuh that option was hiding from me from years!

•Hit thanks if I helped you..:)
[Nexus 7 (2013) Original Android Development] Ænimal:
It should say "http://tasemnice.eu/multirom-test/manifest.json" by the way..
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5478526]Ænimal[/MENTION]

Indeed you're right. Thanks for pointing it out.
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Is there any way to get Ubuntu files outside app and faksh manually on recovery?

Asking here because not getting reply from tassadar.

•Hit a thanks if I helped or bringed you a smile somehow!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5652234]AnkeshReborn[/MENTION]

Well, supposedly, yes : https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/

Though the real question would be : is it worth the time and effort ?

It's much simpler and quicker from MultiRom manager app (and that's why it's been added).
[Nexus 7 (2013) Original Android Development] richardkemp:
I'm losing root when flashing v320-cm on the latest cm12 nightly on my n7 deb. This occurs whether setting selinux permissive or not. It also happens with elementalx... Any ideas?

Edit: I reflashed supersu and it seems fine except settings FCs when I open it. Still curious why I had to do this though, kernels normally preserve root.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=269556]richardkemp[/MENTION]

CM probably changed their root implementation lately. Or something's broken in the last nightly. I'll check.
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Splash screen during boot not coming on my android 5.1primary system with dirty unicorns which have kexec support. [MENTION=3847629]Tk-Glitch[/MENTION]

And does glitch supports 5.1?

TIA ":D
[Nexus 7 (2013) Original Android Development] joeyddr:
Looking for a glitch 5.1 kernel myself since the Roms are starting to come out.
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
The 5.1 roms that are out are using 5.02 kernel and blobs. I'm using this kernel on Euphoria-OS 1.1 which is Android 5.1
[Nexus 7 (2013) Original Android Development] joeyddr:
Cm or aosp?

NM aosp worked well
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Aosp, I haven't liked any of the CM based roms on Lollipop with either of my Nexii.

Euphoria-OS is pure butter with Glitch ?
[Nexus 7 (2013) Original Android Development] LucentBirch:
See, my tablet would reboot several times a day on 5.1 with both stock and elementalx kernel...didn't try glitch, but that sort of thing shouldn't happen regardless. Back to 5.0.2 and no reboots
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
I haven't had a single reboot with Glitch on 5.1 which I've been using a week now.
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
I haven't faced a single reboot too,using aosp v on dirty unicorns

:D

•Hit a thanks if I helped or bringed you a smile somehow!
[Nexus 7 (2013) Original Android Development] akaHardison:
In few versions ago,I can edit settings in glitch.conf in /system/etc.But right now I upgrade to Android 5.0 and I can't find this files anymore.I can't edit it in init.d,too.
[Nexus 7 (2013) Original Android Development] hardwareadictos:
Bello guys! Has this kernel any personal governor tweaked specially by the developer? And is it posible to use it with UKM? Thanks un advance :)
[Nexus 7 (2013) Original Android Development] THRUSTer:
L2 Cache and Bus Bandwidth

What does changing the L2 cache even do?

What does changing the bus bandwidth do?
[Nexus 7 (2013) Original Android Development] Blue305:
I use the cm version with ukm and it works just fine :)
[Nexus 7 (2013) Original Android Development] asp2010:
It increases the memory frequency and enables more data to be transferred per cycle. This should mean you need to wait less for some things to happen, so you get a performance boost.

Sent using the XDA mobile app
[Nexus 7 (2013) Original Android Development] hugo_bjk:
otg + charging

hi all

i installed elementalx kernel over stock 5.0.2 but having otg charging issues. want to try this kernel but does otg charging works properly? anyone tried it before?
[Nexus 7 (2013) Original Android Development] asp2010:
For me, ot was working a while ago on 305 aosp, so it probably still works. Give it a try and find out :D

Sent using the XDA mobile app
[Nexus 7 (2013) Original Android Development] pk-sanja:
5.1 is up. I know we all wait for Glitch 5.1 :)
[Nexus 7 (2013) Original Android Development] animania260:
Looks like Glitch is uploading/building it now :)

Thanks Glitch! Finally got 5.1 on the Nexus 7 2013.

much smoother and fluid than the initial Lollipop release.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
New update is available !

Aroma is still there for the "full/initial" installation process, but you can now skip it for system/kernel updates. I hope you'll like it !

16/04/2015 - r327 :

- Merge with android-5.1.0_r0.10 changes

- Updated F2FS implementation using Motorola's sources

- Cleaned up permissive ramdisk patches (fixed related SODs with it enabled)

- Introducing "restore" builds. You can now update your Glitch setup without Aroma using these builds. Your settings will be restored from the SDcard backup made by a previous Glitch installation, so if you don't have a "glitch-settings.conf" file in the root of your SDcard, please use a full build first to generate it ! The "full" builds are using Aroma as before.

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

Enjoy guys !
[Nexus 7 (2013) Original Android Development] pk-sanja:
Yeah finally, thank you [MENTION=3847629]Tk-Glitch[/MENTION] . Happy flashing all :)
[Nexus 7 (2013) Original Android Development] jbrantley130:
Thank you for the latest update [MENTION=3847629]Tk-Glitch[/MENTION]! Working flawlessly on latest Chroma for Flo!
[Nexus 7 (2013) Original Android Development] akipapa:
Thanks for your hard work as always!

The new 327 version works great but takes longer boot time:

(Google logo screen)

r320. 25s

r327. 55s

Is that normal?

[Spec]

Nexus 7 2013 WIFI(flo)

TWRP 2.8.6

Kernel Glitch for Flo/Deb - r327

CM12 Nightly

Pa gapps

/Data /Cache=f2fs

/System = ext4
[Nexus 7 (2013) Original Android Development] matcho13579:
Same for me. I was afraid for a moment whether the tablet boots or not :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Mount options changed for F2FS, that's why. I'll have to play with them a bit to find out how I can improve mounting speed.
[Nexus 7 (2013) Original Android Development] akipapa:
Thanks!

So there's no performance loss after the boot process?
[Nexus 7 (2013) Original Android Development] bart.found:
Just flashed your Kernel!!! Great Job man!! All I need in a kernel is here!!! Synapse works correctly almost with all features.. A full synapse support and this kernel will hit the perfection! :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
No, indeed. Only the boot process is slower. By the way, it's not true on every setups either. It looks like CM is suffering while AOSP is faster to boot with this configuration than r320. I think I've found a way to get similar gains on both AOSP and CM and the update will get released soon.

This is in my "to do list" for some time now. It does require more time than I currently have to make it as I want it, but it's definitely something I'll do when I'm able to. Thanks for the kind words and I hope you'll enjoy tweaking as far as you can with Glitch, as I do ;)
[Nexus 7 (2013) Original Android Development] bart.found:
Wow! Thanks!!

I'll wait for updates! I know that development takes a lot of time and mine was more a hope than a feature request.. But It's good to know that it was already in your to do list! ;)

I like this kernel because Flo has the same SoC of my Nexus 4.. And I'm glad to find almost all the same tweaks that I use in my phone's kernel! :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Dear Glitch users, a new release is available !

19/04/2015 - r330 :

After breaking my partitions while attempting to improve F2FS mounting time, I was forced to format everything. After my backup restoration and system reinstallation, r327 F2FS implementation is now booting faster than EXT4 on my tab (with mounting times of ~5sec versus 30+ before). So I've then decided to revert the planned F2FS changes for r330 (which made it 1sec faster before formatting, but much slower after) as it didn't make sense. If F2FS mounting time is bothering you, fully formatting your partitions and restoring your data will give you a nice performance reward in return.

- Added flush_merge to F2FS mount options for faster flushing

- Added "transparent compression" support (CM sync)

- Added back optimized ARM RWSEM algorithm

- Enabled back unaligned memory access

- Switched to SIO ioshed (from ROW) at boot time as well as others small tweaks for possible further boot time improvements and smaller file size

I hope nobody will be disappointed !

Enjoy guys :)
[Nexus 7 (2013) Original Android Development] matcho13579:
Gonna try to flash it, but I'm too lazy to do backup, format, restore etc., so I'm just gonna check if the boot time is better, will report in a minute

EDIT/ Okay, I assume that I HAVE TO format partitions to reduce the boot time :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3845051]matcho13579[/MENTION]

I have to admit that was pretty bad news for me to have to tell you (my dear users) that. But well, there's no better option as far as I know. I was trying to improve mounting times with F2FS for months with low success and I couldn't understand how Motorola wasn't having such issue. At least we are aware of that now (and that's logical in the end). I will keep the current implementation as long as it's maintained to limit such problem to rise again.

Also, Multirom will add (even without secondary rom installed) about 10 seconds overhead.
[Nexus 7 (2013) Original Android Development] akipapa:
Thanks, full format isn't a problem, but I have a problem with restoring /data.

http://xdaforums.com/nexus-7-2013/n...d-successfully-dataf2fs-t3079055#post60170684

Any idea about this?

Thanks a lot.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6565284]akipapa[/MENTION]

I was searching for some kind of answer to that or at least a theory to explain it but it looks like [MENTION=3845051]matcho13579[/MENTION] found out what could be the issue here. Thanks to him !

Here's the link if anyone asks : http://xdaforums.com/showpost.php?p=60245143&postcount=10
[Nexus 7 (2013) Original Android Development] bmccoy11:
Any kernel changes for flo in 5.1.1, or anything newer than 5.1-r1?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5637619]bmccoy11[/MENTION]

5.1.1 isn't yet officially available for flo. We can build AOSP, but we're missing potential binaries/kernel changes.

For now we have nothing newer than 5.1.0_r0.10 sources for flo. We'll see if there's any change when it's out :)

https://android.googlesource.com/kernel/msm.git/+refs
[Nexus 7 (2013) Original Android Development] aircooledbusses:
Might not be official yet, but feels good on the tablet. Can Install your latest kernel? Or is it something I should try for myself and see? Please be gentle, I mean no harm.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4773115]aircooledbusses[/MENTION]

You can install my latest kernel on 5.1.1 for sure. I have yet to encounter any issue with it myself.

We're all gentle in this thread, don't fear us :)
[Nexus 7 (2013) Original Android Development] bart.found:
Hi, I have sometimes random reboots with this kernel.. when I check last kmsg it says: last reboot reason watchdog

What should I check to find the cause of these reboots?
[Nexus 7 (2013) Original Android Development] joeyddr:
for some reason i cant get it to boot the lates AICP release which is cm based.
[Nexus 7 (2013) Original Android Development] jbrantley130:
Did you make sure to flash the caf version?
[Nexus 7 (2013) Original Android Development] joeyddr:
yes of course.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5735314]bart.found[/MENTION]

Multiple things could be the source of your random reboots :

- Too high CPU uV leading to unstable CPU

- Too high CPU OC frequency leading to unstable CPU

- Too low lowest CPU frequency leading to unstable CPU

- Too high GPU OC frequency leading to unstable GPU and RAM corruption

- Too high GPU uV leading to unstable GPU and RAM corruption

- Too high bus OC frequency leading to RAM corruption

- Slide to sleep can lead to crashes for some (DT2W seems unaffected)

- The PIE patch available in Aroma can lead to various crashes depending on your rom base and will be removed in the next update

- Hardware issues showing up with some roms/kernel updates making better/heavier use of the hardware (random reboots reports skyrocketed since stock Lollipop rom update on this tab..). Some of the settings I'm using in my source could be a bit too aggressive for your tab, as well as hotplugging driver in use for example.

A combination of some/all of them will be even more unstable. I hope it'll help to some degree. Good luck !

I'll install AICP and see what could be the problem.
[Nexus 7 (2013) Original Android Development] bart.found:
Thanks for your reply... I don't use overclock.. And all the features are stock.. Only thing I do is undervolt.. I raised all voltages (tested with stability test) by 25 mV.. But still have some reboots.. I'll try to test stock voltages for a while! ;)
[Nexus 7 (2013) Original Android Development] Hatshipuh:
Random Reboot, almost missed it, but just saw it booting up while sitting idle on the desk.

Euphoria OS, default settings installed, only changes were switching off dt2w and enabling fast charge.

Last_kmsg attached.
[Nexus 7 (2013) Original Android Development] JoseRebelo:
I don't have a log, but just wanted to say i've also been experiencing 1~2 random reboots during the day, even when the tablet is not in use, on the latest cyanogen nightly. No overclocks, mostly default kernel settings.
[Nexus 7 (2013) Original Android Development] bmccoy11:
5.1.1 images are now available for flo. Any changes?

(direct link)

https://dl.google.com/dl/android/aosp/razor-lmy47v-factory-a58e6175.tgz
[Nexus 7 (2013) Original Android Development] NYCHitman1:
Some minor changes.. https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-lollipop-mr1.1

3 commits to be exact.

https://www.codeaurora.org/cgit/qui...1&id=894341cd2526eaa8d71b5dcdf568c6680bf3cb04

https://www.codeaurora.org/cgit/qui...1&id=547e1e2c76fb70654e39dc1f2bc8a8458761116b

https://www.codeaurora.org/cgit/qui...1&id=0baf67b70346a2a1da67ec75cdfab8c92add2186

I'm a bit curious why they want Flo to go back to their 4.6 gcc though.
[Nexus 7 (2013) Original Android Development] joeyddr:
have you tried aicp?
[Nexus 7 (2013) Original Android Development] tetakpatak:
Possibly for searching the reason why so many N7 bricked after OTA update to LP (100% stock, locked devices)

tetakpatalked from 1+One
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Looks like display gamma/color tweaking driver is breaking latest CM. I'm on it.

To everyone : I think the random reboots are - finally - fully fixed (I was able to experiment with it). A few features will be removed/replaced until I'm absolutely certain they aren't generating issues. Currently I have observed 3 different issues : random reboots, sleep of death (tab is on but screen stays black), and touch freezes/delay. I'm still testing things out but it looks like they are fixed for good (all three). Next release approaching.
[Nexus 7 (2013) Original Android Development] nokiagye:
The black screen is from gamna if you can fix it it would be great??
[Nexus 7 (2013) Original Android Development] creeve4:
In the changelog for r343 you list that the intelliactive governor was added, but it was already in r330?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Thanks, this changelog has been changed a few times during testing and I missed this one.

It's release time btw ! Starting to upload the new update.

Let's go for the new release ! Most issues are fixed (SoD/RR/touch freezes) and performances are up - though AICP still doesn't boot (I don't think it has anything to do with my kernel in itself though as latest CM12.1 works nice). Here are the changes :

08/05/2015 - r343 :

- Merge with android-5.1.1_r0.10 changes

- Removed UKSM

- Disabled KSM

- Removed transparent compression support

- Replaced Flar2's S2W/DT2W by showp1984's DT2W

- Various F2FS changes from arter97 and Jaegeuk Kim

- Various backported drivers from arter97

- Updated Intelli-Plug

- Cleaned up base and bumped back to latest 3.4.y (3.4.107 atm)

- Removed PIE bypass patch from Aroma

- Added Motorola's Qualcomm optimized memutils

- Added BFQ v7r7 ioshed

- Updated Intelliactive governor

- Fstab patching changes to fix boot on some non-standard roms

- Updated Random

- Updated toolchain to Linaro GCC 5.1.0 with LTO support

- Added LTO optimizations

I hope you'll like it. Enjoy !
[Nexus 7 (2013) Original Android Development] odub303:
Just had a random reboot, boot reason listed was Watchdog. Running Robbie's UberCM rom.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=715348]odub303[/MENTION]

No OC/uV I suppose ? It seems I'll have to remove more optimizations.
[Nexus 7 (2013) Original Android Development] odub303:
Installed with the default uv, no oc. I'm going to reflash with no uv and see what happens.
[Nexus 7 (2013) Original Android Development] animania260:
New release is awesome Glitch! So much smoother now. I was beginning to think I would just have to deal with Lollipop running a tad slow on the Nexus 7 2013 (until the next Android release anyway as I figure Google will hopefully focus on cleaning up the performance and stability instead of adding 1000 new features in 1 year. I guess they normally do this feature release, then stabilize/performance focus with a few new features? Anyway back to the praise), with the UI slowness (even switching to Interactive and enabling touch boost at 1.5 GHz didn't help much, with no UV. Keeping 2 cores online, etc.) even on the stock kernel - started to feel like the original Nexus 7 :( Though 5.1 did help and 5.1.1 feels a little better.

With your new release it damn near feels like good old KitKat 4.4 now! Smooth!

Anyway just wanted to say thanks very much for your work as usual! Love it!
[Nexus 7 (2013) Original Android Development] creeve4:
No issues or reboots running r343 with rastapop. Thanks tk!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Here's a little hotfix that will - I hope so - fix everything (except AICP..).

08/05/2015 - Hotfix - r344 :

- Rolled back various GPU driver patches to fix some Chrome scrolling lockups and possible RR linked to the underlying bug linked to them ( [MENTION=715348]odub303[/MENTION] : could be your fix hopefully.. Fingers crossed !)

- Send enforcing=0 to kernel command line if you're using the permissive ramdisk mode (may fix boot on some non-standard roms - AICP still not booting for me though.. If you know why I'm all ears)

- Modify fstab.flo file in ramdisk even when using CM kernel (enables some non-standard CAF based roms with no "multi-mount fstab" support to boot - it mustn't exist, but better safe than sorry)

Enjoy guys !
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
A small request if I may. Would it be possible in a future release to reinstate the pie patch fix?

No biggie...

Thanks...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

Added the 5.1.x version to downloads section. Is it enough, mate ? :p
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
You are a star..thanks.

The only reason I requested this was I had the original patch-pie.zip but stupidly deleted it a while back and couldn't find the DL link again...

Anyway, thanks again....
[Nexus 7 (2013) Original Android Development] jimbob_sf:
For flo, any version past 330 won't boot the factory image for 5.0.2 (rooted). It either hangs on a black screen just after boot or the animation just slowly ticks away (almost like I tried to install a caf kernel). I haven't tried to play with the install settings to see if an option is doing something odd, but I just wanted to get this back to you. I didn't try 343, but 344 definitely did it. I went back into recovery and did a full install of 330 and its working fine.

I've got another flo running 5.1.1 (also factory) with 330 and no problems there either. I'm doing some tests between the 2 using factory images, so I have this comparison between factory versions.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

That was easy enough for me to make a flashable zip of it. You're welcome.

And look ! You're not the only one who needed it, so in the end thank you for asking as it was clearly something I should have done. Your request was more useful than you thought ;)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Well everyone's a winner then...?

Cheers mate...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2752553]jimbob_sf[/MENTION]

Thanks for the report. I didn't try 5.0.x but various 5.1.0 and 5.1.1 roms (except AICP) are running smoothly. It's a bit odd but well, I'm following Android updates. I'll check some 5.0.x roms to see if I can do anything still.
[Nexus 7 (2013) Original Android Development] akipapa:
343 is amazing, very fast and I feel it even resolved chrome scrolling freezing problem.

F2fs also works fine without booting delay!

Thank [MENTION=3847629]Tk-Glitch[/MENTION] very much!

I'm going to install 344 to see if there is gonna be some change.
[Nexus 7 (2013) Original Android Development] jbrantley130:
[MENTION=3847629]Tk-Glitch[/MENTION] you are one humble and cool Dev. R343 running smooth on my Flo with Opti-Pop(5/7/2015). No random reboots, freezes, or bsod's for me. About to flash R344 and try it out.
[Nexus 7 (2013) Original Android Development] jimbob_sf:
I'll test if you make revisions if you like. PM if you want.
[Nexus 7 (2013) Original Android Development] Anta:
Hello Glitch, do you think will be DVB-T support in future Releases? :)
[Nexus 7 (2013) Original Android Development] bmccoy11:
There have been changes made to the RAMDisk in recent CM12.1 nightlies, could we get a rebuild? :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3299331]timrock[/MENTION]

If you're using the official PA, it's CAF based so the "CMLatest" kernel is what you want. If you're using the unofficial one, it's AOSP based, so you'll need the other one (the one you have downloaded).
[Nexus 7 (2013) Original Android Development] Grondinm:
Dualboot support is fixed. Thank you again.