yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

So, after clean installing then flashing "Full build", I noticed that my Aroma settings weren't applied (init.glitch.rc permissions are missing execution, preventing aroma settings restoration as well as sdcard backup, that explains your issue with flashing "Pure"), but all Synapse files were in place as well as everything else. Synapse required a data cleanup before it started working (not detecting uci support without that). Everything else worked fine out of the box like camera and kernel adiutor.

So it does look like I have some work to do with the "Full" build. I'll definitely add clean install to my testing process :p

I will also make the "Pure" build completely standalone so it doesn't complain that there's no settings backup on sdcard.

Thanks for helping me making this kernel better :) Stay tuned for a new build soon.
[Nexus 7 (2013) Original Android Development] shantam3108:
Haha Glad to know buddy.. :)

Will be waiting for the new release.

You can count me anytime :)

---------- Post added at 03:48 AM ---------- Previous post was at 03:05 AM ----------

Hey buddy upon changing my RGB to 236 248 256 my whites were Complete yellow on on 256 256 256 they whites had shade of black. Only default 255 255 255 works
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I'll check if I can limit the values in Synapse.. But don't go past 255. The range for each channel is 0-255.

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

r530 "stable" release is available !

We're now getting to a milestone.

I've made countless clean installs of various roms, with various configurations, and it should finally be more or less universal. The only untested thing is Aroma settings application when running stock CyanogenMod root (because I'm pretty sure it won't work for some CyanogenMod reason) Indeed it doesn't work. Flashing SuperSU is needed if you want to get your profile applied at boot on CM (and/or you don't want to use Synapse).

14/09/2016 - r530 :

- Modified rom injection/flash time mods logic to be more robust and universal. Fixes inconsistent boot or even bootlooping on hybrid F2FS roms like CyanogenMod or PureNexus THIS CHANGE MAY FORCE YOU TO REFLASH YOUR ROM TO BE ABLE TO BOOT (even on a non-hybrid rom - no wipe required)

- Fixed settings not applying after setting them through Aroma/glitch-settings.conf

- Security patch to avoid invalid access to ashmem area

- Security patch for vulnerability CVE-2016-2059

- Removed deprecated binary injection code

- Default thermal presets calibrated for better efficiency and performance (they were too aggressive in r520)

- Little naming change for the builds. Full is still "Full", but "Restore" is now "Pure". Pure edition is now fully standalone and doesn't require a previously generated profile from Full edition (but will gladly restore it as before if found during install). It can be fully tweaked through config file and/or Synapse like Full edition.

- Nougat build "Full edition" now has a Nougat themed splash screen for Aroma

- Synapse presets are now working. Make sure to press apply when Synapse comes back if you want to keep it (you'll get it once you try it) ! (Make sure to clear Synapse data after first boot to force a regeneration !)

- Small things you won't notice

"Enjoy" will probably sound better now :p

Feel free to report any issue you may encounter as always. Thanks !
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Same as IP addresses...?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's so quiet around here !

Are you satisfied with r530 [MENTION=5863767]SHABBYLEA[/MENTION] ? :o

Anybody with a deb to confirm that radio is back/working by the way ?
[Nexus 7 (2013) Original Android Development] quickdraw86:
That just means that it's working well and that the people are happily glitched.
[Nexus 7 (2013) Original Android Development] gangrenius:
Or that peeps are moving to 7.0
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4471805]quickdraw86[/MENTION]

Probably :)

I have to admit my to-do list for next releases has only three entries right now (that's a first).. I can even "spoil" them : adding the missing drivers and their settings to the infamous hotplug drivers tab in Synapse, implement some load/load migration calculation patches for slightly better CPU power management, and add sdcardfs (and the scripts to make it work with everything).

Apart from these three, I'm completely happy with the kernel for the first time since the first release, 530 revisions later.

[MENTION=7298419]gangrenius[/MENTION]

Well, I have made a specific version for 7.0, and if I'm not mistaken, it's the only one right now to be compatible with Multirom. And considering 7.0 is young and still W.I.P. on our devices, I'm surprised not to get reports of issues on the 7.0 kernel. Though.. I'm using Nougat daily myself on this tab and I'm pleased with it, so I assume it's the same for my users ! I hope so :)
[Nexus 7 (2013) Original Android Development] gangrenius:
That N firmware is definitely a beast.

---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------

You said you had a 7.0 kernel for it. Where? Are you holding out haha!
[Nexus 7 (2013) Original Android Development] Nevermindthelabel:
In downloads, the N kernel is for Nougat. Running it on my 7.0 now, pretty smooth!
[Nexus 7 (2013) Original Android Development] yosmokinman:
^Yeah I'm running Swifts 0.6 with 530. All stock settings I can pick from Aroma. I'm trying to compare to stock kernel.

I think it works great in the couple days I've run it. Seems the same as the stock kernel with the following things I've noticed:

The old APW twitter widget that I still use scrolls much smoother than the stock kernel where it's really janky. The app is outdated but it works better with this. So why is this? All other scrolling "things" are fluid. I know it's the app but why jerky with stock and smoother with 530 when I didn't overclock?

My play services "*net_scheduler*" wakelock I been having has all of a sudden been behaving itself where stock kernel it was randomly draining pretty bad, sometimes ok.

I know ^that doesn't really tell you anything but it is performing better than the stock kernel for me. Just my impression. Thanks!

Edit: I haven't tried the overclocking stuff yet on N. Previously I try'd it but didn't think it need it yet. We'll get there where it needs it maybe not with N. Running nice :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4873279]yosmokinman[/MENTION]

Keeping everything stock on Glitch with no overclocking is still an enhancement versus stock. You should also see better benchmark results with Glitch. Why ? Well, the list is long after 3 years, but for example you get kernel-based CPU hotplug and thermal drivers instead of the default binary based ones. It's both faster and more energy efficient. The CPU scaling drivers, I/O schedulers, network, display, memory management... etc. Many things have been tuned and optimized for better performance and efficiency (and many bugs present in the Google sourcecode fixed). Overclocking then can really shine. As it's a brute force way of getting more performance it'll always give a boost, but if the kernel is inefficient the boost won't be as nice as it could be and power consumption will skyrocket. Overclocking is not required for this tablet to be smooth in most non-heavy scenarios, but a slight one makes it as snappy as a Snapdragon S800 based device with all the tweaks I talked about previously (one of my friends with a N5 is even jealous of my N7's smoothness).

I'm glad you like it !

[MENTION=7298419]gangrenius[/MENTION]

So my title isn't clear enough I guess :D But yeah, everything is in the download section. "MM" kernels are for 6.0.x and "N" are for 7.0, as [MENTION=5996385]Nevermindthelabel[/MENTION] said.

Any ideas for a better/clearer title guys ?

Edit : I did try something.
[Nexus 7 (2013) Original Android Development] vbaros:
I usually do not post when I'm not complaining. I guess it is true for many users. I've put a custom ROM on my N7 for the first time after having stock from the beginning. I flashed Nougat WIP and it is truly great but with your custom kernel it flies. I just flashed the pure edition and I'm satisfied with level of speed up. BTW what would you recommend should I play with to get it even faster without affecting the battery too much?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3853700]vbaros[/MENTION]

If you did flash latest SuperSU along with your ROM you have the best balance between speed and power consumption already. If you didn't, you could do that. It will enable a service that requires root access to apply a kernel configuration that feels like the best balance to me. You can try installing Synapse and see if some features may interest you, or push the overclock slightly (one or two steps further won't have too much impact on battery life).
[Nexus 7 (2013) Original Android Development] vbaros:
I did flash after the ROM: gapps, SuperSu and your kernel. Everything works great. Occasionally I get some application force closes. I can't seem to pinpoint the reason. Maybe it's just 7.0 compatibility issue.

I'll try pushing the clock 2 steps further.

Thanks for your hard work!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3853700]vbaros[/MENTION]

Yep, the force closes are most likely related to 7.0 compatibility, as well as issues related to the port for now. I'm sure everything will get fixed in the near future.
[Nexus 7 (2013) Original Android Development] Mysterion1:
Great kernel for N! No issues so far, I'm very confident with your work as always [MENTION=3847629]Tk-Glitch[/MENTION]

Thanks!!! ???
[Nexus 7 (2013) Original Android Development] Extreemator:
Battery drain like 10% a night with WI FI off. While I get 0% drain on blue spark nexus 5. Why
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
As QD mentions below, its precisely because I have had no issues, that I have not posted...?.

Been, running on N since you uploaded...no probs at all so far...?

Thanks TK.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
With wifi off ? I get generally 2-3% lost over night with wifi on at worst, so check for wakelocks and crappy apps. For your N5 it's simply a lie, most likely either aging battery or rom related. N5 has horrible battery life, independently of rom or kernel.
[Nexus 7 (2013) Original Android Development] matcho13579:
I don't know if it's app, ROM, kernel or settings-related, but when I watch YouTube videos using YouTube app, video keeps freezing while sound continues, I have to rewind the video to unfreeze it, it's starting to be pretty annoying when I have to do it like 10 times per 5 min video
[Nexus 7 (2013) Original Android Development] sciamanozx:
thanks :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3845051]matcho13579[/MENTION]

Interesting ! I will need more details on this one to try to reproduce it. Any video is impacted, in any resolution ? What ROM ? Any OC/uV on the CPU, the GPU, bus/L2 ? Did you change I/O scheduler or readahead values ?

Thanks :)
[Nexus 7 (2013) Original Android Development] matcho13579:
Any video, any resolution, PureNexus ROM, improved setting in Synapse, -5 mV undervolt CPU all freqs, GPU undervolt by one step lower (in Aroma), improved bus, ROW I/O with no modification. But I'm using ParrotMod so the I/O scheduler might be modified by this, might this be the cause?

EDIT// Just did a bit of a testing and it's freezing on 720p only now, very weird. As soon as I switch to 480, it stops freezing
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
This bit is very interesting. I'm on it.
[Nexus 7 (2013) Original Android Development] Extreemator:
It doesn't look like a lie. Battery isn't too bad yet too. It seems true after extensive checking and installing different roms, and I saw exactly same reports too. 0-1% lost with no radio and wi fi*

Nexus 7 losing 6% minimum a night with no wi fi, fresh installation purenexus rom. We'll will wait until nougat developers will fix all up, these early builds are never good
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4190491]Extreemator[/MENTION]

6% over night is huge for sure and nowhere near what I get since mid-2013 on my device. I'm not using purenexus at all so I don't know if it's related.

Though about the N5, if we're talking about 1% over night (and that a night is about 8 hours long) it would mean about 800 hours - so more than a month - battery life in standby. If it was half a percent we're talking about 2 months and a week. If that's not a lie I don't know what it is.
[Nexus 7 (2013) Original Android Development] Extreemator:
Who knows maybe it's 2 percent de facto (I imagine it will be more complex due to short runmeasurement error and battery charge self attrition in the long run) . A month of battery looks attainable when the phone is in doze with radio off, but no reason proving because I will never have a chance to check it, maybe you know better. All I know that stand by is very battery efficient now, and I am surprised because all of my android devices have had bad standby life over years.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4190491]Extreemator[/MENTION]

Yeah, I'm neither trying to prove anything nor asking you to. I'd like to believe, but my experience prevents me to. Radio on with data disabled has a really small impact on battery life (as long as the device works properly) compared to radio off. Wifi may or may not drain battery depending on the device and eventual bugs in the source. I've had issues with wifi drain on standby with all the previous Nexus devices I have used except this one (though there's an issue with wifi on while not connected to an access point since LL). The best I've been able to get on a phone in standby was about 220 hours (radio on, data off) on MM, and that's with a 3000mah battery. The battery jauge feedback was the same as what you get, so between 0 and 1% per 8-10h. I didn't check the graphs so I don't know if it just died at some point while still showing "some" battery life remaining or if the capacity calculated fell on some steps. But anyway, even 800 hours standby on a N5 with a 2300mah battery doesn't seem anywhere near achievable at all to me. I may be wrong. And that would be awesome to say the least.

Now that I've been thinking about your issue with your N7, I thought about DT2W. Did you flash Pure kernel without any tweak ? If you did, you may want to disable DT2W as it's enabled by default. I don't like the way flar2 did it on EleX so mine is always on as long as it's enabled, and will drain battery by keeping the touch panel always on. I'm using it on some of my secondary roms, but not my main, so I didn't think about that at first. Tell me how it goes if you're still on Glitch.

[MENTION=3845051]matcho13579[/MENTION]

Looks like Google f*cked up Youtube app recently. When I talked about the issue with some friends they all told me that they got the same problem (various devices from LG, Samsung, and a Nexus 6). Depending on the video, 720p (especially 720p60 and up it seems) will freeze after a few seconds while sounds still plays in background. Eventually it'll start to play if you go forward/backward in the video, but it may freeze again at some point. 480p plays fine in most if not all cases. Exactly what you described isn't it ? And I was able to reproduce it consistently. I'll try to find an older version of the Youtube app to see if the problem persists. Though it doesn't look like the kernel is the issue for now. I'll ping my dev friends about that.
[Nexus 7 (2013) Original Android Development] matcho13579:
Yes, this is the exact issue, thanks for testing this. So basically we know that it's not the ROM/kernel issue
[Nexus 7 (2013) Original Android Development] gangrenius:
I hate to ask this but what's the difference between this kernel and EkementalX for nexus 7 2013.
[Nexus 7 (2013) Original Android Development] shantam3108:
It must be 720p 60 fps video.. Thets why It would have froze 60 fps freezes on nexus 7
[Nexus 7 (2013) Original Android Development] buhohitr:
If you're running Androd 6 MM, they both almost the same, custom kernel tunned for performance, battery life with users tweaks enabled. However, if you are running N7 rom then you need to use this kernel since EkeX only support MM6.0
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It seems pretty natural to me for someone to ask :)

Well, it mostly depends on you. Both are performance oriented and feature packed kernels.

Glitch has more options available to the user, larger overclocking boundaries, and lets you use kernel-based hotplug drivers.

EleX is "simpler" for the user, and uses the default binary based hotplug driver from Qualcomm. At default settings, Glitch should be faster at same frequencies than EleX, but EleX may be a bit easier on battery (Qualcomm's driver is available in Glitch too btw).

After tweaking everything for your own usage, Glitch should be faster for a similar battery life as long as you're not using DT2W (if you do, it's equal to not using the power button suspend option on EleX). Also, S2S is not available on Glitch.

So my conclusion would be that if you want to push things and if the available screen features (S2S/DT2W) are enough for you, Glitch is the way to go (and now that you can select presets in Synapse - and I may add more in next updates - Glitch is less of a headache to tweak for specific needs).

If you want to just install and forget, without tweaking stuff to improve your experience further, EleX is probably better.

That's my point of view though and I suppose it's best to try both for a few days each and see if one or the other feels better to you, unless some options are really a must on one or the other.

I hope I'm objective enough :D
[Nexus 7 (2013) Original Android Development] Extreemator:
[MENTION=3847629]Tk-Glitch[/MENTION]

Battery drain randomly diminished after a few days and now about 3%, didn't even used tablet at all. 2taptowake was off all the time of course.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Which version are you using?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4190491]Extreemator[/MENTION]

Funny. Must have to do with the clean install of your rom I suppose. A few days needed for everything to settle down.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Just checking in...last build for flo N still rock solid...

Excellent work...

Thanks.
[Nexus 7 (2013) Original Android Development] Steven Chen:
Screen can't rotate automatically

I install Glitch-MM.flo.r530-CM-Pure.zip on Cm13 snapshot and nightly, screen just can't rotate by itself.
[Nexus 7 (2013) Original Android Development] pss34:
I have the same issue with aosp full package, but reboot always help me. After some time device have lost orientation sensors.

Tested on pure nexus 7.0 and saosp 7.0.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6603503]pss34[/MENTION] [MENTION=7576402]Steven Chen[/MENTION]

Only happening with my kernel ?

Else it may be time to open your back cover to check the shielding and reseat the connector. This tab has some kind of "hardware issues" you can fix (at least it did fix touch/sensors & buzzing sound on all the 2013 released N7s I've "modified" that way, and no issue for 3years+ since then). [MENTION=4827892]Gorgtech[/MENTION] has made a nice tutorial last year, and you can find it here if you're interested. Reseating the touch panel connector seemed to be enough to fix touch & sensors on the devices I've worked on, so you can try that. Be extra careful if you choose to do so btw.
[Nexus 7 (2013) Original Android Development] pss34:
Yes. And it is not a touchscreen problem. I have orientation sensors lost only. Touch works well, same as gps.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6603503]pss34[/MENTION]

As far as I can tell, it seems you're the only one who is facing such issue (btw if anyone else is suffering from the same problem, I'd like to know. Thanks) and it was happening on 6.0.x too, right ? So I'll need your last_kmsg as well as your glitch-settings.conf files please :) (pm or attach files to a post). If you have made some tweaks using Synapse (especially enabling/switching hotplug drivers), it may help me to know that as well. Thanks !

[MENTION=7576402]Steven Chen[/MENTION]

I'll check if I can reproduce on latest CM13. Make sure autorotation isn't disabled btw.

Edit : I couln't reproduce your issue with latest CM13 nightly on three different devices. Autorotation was even 50-100% more reactive versus stock CM kernel.

Edit 2 : [MENTION=6603503]pss34[/MENTION] [MENTION=7576402]Steven Chen[/MENTION]

I'm starting to think you may have, if not the same, a very similar issue.

If you're using high overclocking settings (L2/bus concerned too), you may want to try stock clocks for a little while just to make sure it's not a simple instability caused by too high OC.
[Nexus 7 (2013) Original Android Development] madsurgeon:
I can confirm its a hardware issue, this has happened to me on so many different occasions on so many different roms, nothing even remotely software related . I've done the hardware mod the dev mentioned earlier and the orientation issues went away, for a long while. It reappeared when i placed the rear against a magnet, forgetting that i had the mod installed. What finally pushed me into doing the mod was the emergence of touch screen issues.
[Nexus 7 (2013) Original Android Development] brolic925t:
So apparently faux is too busy to update his app.. so what can we use to control gamma? Faux sound n clock crash on nougat
[Nexus 7 (2013) Original Android Development] gyakusetsu1215:
Kernel adiutor mod. Can find it here in xda. Brilliant app.
[Nexus 7 (2013) Original Android Development] brolic925t:
Think im doing something wrong.. custom values arent showing n profiles dont work :(
[Nexus 7 (2013) Original Android Development] gyakusetsu1215:
Profiles work fine for me after a reboot. Not sure what's going on in your situation.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
You running a custom kernel?
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Just checking in TK...have to say no issues with your kernel...the best AFAIK.

Many thanks...
[Nexus 7 (2013) Original Android Development] vbaros:
Flashed it on the 7.1 build. No issues.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Same here...running great...
[Nexus 7 (2013) Original Android Development] shantam3108:
Could you make the kernel compatible for aicp 12 too :)

Thanks in advance
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Definitely.

Next update should be available in the next few days.
[Nexus 7 (2013) Original Android Development] shantam3108:
:highfive:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
New release out: r533. Now building CM variants for N too !

Since there are additions/changes to Synapse, you'll need to clear the app data to get them.

07/11/2016 - r533 :

- Added SDCardFS support

- Fix for CVE-2016-3903

- Fix for CVE-2016-3934

- Fix for CVE-2016-7117

- Added LazyPlug switch and settings to Synapse (hotplug tab)

- Added DT2W switch to Synapse (misc tab)

- Fix GPU voltage range formatting in Synapse

- Fixes regarding power efficiency

- Contextual fixes and speedups

- Now building CM variant of the Nougat kernel too. AICP is the first N rom on this device to require a CM compatible kernel.

Enjoy guys.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks again TK...as I've said many times, my fav kernel...

?
[Nexus 7 (2013) Original Android Development] nokiagye:
Thanks my friend,
[Nexus 7 (2013) Original Android Development] vbaros:
Flashed it on 7.1.1 builds. Works perfectly.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Ditto...
[Nexus 7 (2013) Original Android Development] androidmichael:
Glitch,

thanks for continuing to develop on the N7!

What 7.1 ROM are y'all using?

Any bugs or issues?