yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] sushi247:
that was crazy funny. anyway awesome kernel. also seems I have a great tablet, currently running r499 + latest dirty unicorns at glitch(last setting/max) l2 + 2ghz on cores, but It gets kinda hot. still not as hot as lg g3 stock for example. it's rock solid, absolutely perfectly stable and needless to say buttery smooth but I don't know if the throttling can keep me safe or if I should be worried about 70-90c Temps. what do you guys think?

I pushed it to 2.2 GHz doesn't break a sweat, but I can make fries on it so I stayed at 2.0. how does this thermal throttle work? I mean at 2.2 I think it jumps well over 100c, when will it throttle, at 150? rofl
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7272871]sushi247[/MENTION]

Thanks for the input/report man, and gratz for your nice chip !

If you didn't tweak the thermal driver settings, it should throttle down by steps starting as soon as 75C° if my memory's right (first to 1.5GHz, then lower and lower if the temp keeps rising). If it doesn't, then something's wrong with the thermal driver and I'll have to fix it asap. I'm pretty conservative on my OC with 27-30C° room temp these days so I didn't notice issues @1.7GHz (and as you said, my G3 is incomparably hotter) but I'll push that back to 2GHz+ and do some stress testing right now. 70-90C° is what I get with stock kernel/rom on a hot day if I'm running some 3D games so I wouldn't worry too much about that, as long as it doesn't stay at 90C° on something like youtube or web-browsing. Though 100C°+ for a long period is definitely not healthy and while the CPU or GPU could handle it for some time, everything else around them may not. I'm on it.

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

Well.. Here is the new release.

Everything feels better with it, it seems... Except the hotplug and presets tabs in Synapse. My brain just refused to look at them many times so for now, if you really want to switch hotplug drivers, do it using the old ways (Aroma or glitch settings). I'll fix them at some point, yet the kernel doesn't lose any functionality.

24/08/2016 - r520 :

- Rebase from latest AOSP sources

- Synapse support with many more features and personnalization available than ever before ! Aroma settings are a joke compared to what you'll have in Synapse. Don't flash UKM on top by the way, and make sure to clear Synapse data if you've flashed one of the previews. Even more to come soon.

- Updated Neobuddy89's msm_limiter driver to latest from Nexus 6

- Updated Neobuddy89's state_notifier driver to latest from Nexus 6

- Moved to Faux123's Intelli-thermal driver - [MENTION=7272871]sushi247[/MENTION] you'll be able to fine tune it in Synapse to suit your needs, and it works very well

- Added some memutils optimizations and more for performance

- Updated Xbox One gamepad driver - Thx [MENTION=4684315]flar2[/MENTION] for waking me up

- Removed loads of dead code and buggy merges

- Switched to Linaro 4.9.4 toolchain - After weeks of testing, my tab runs cooler ( [MENTION=7272871]sushi247[/MENTION] will like that), stabler, and longer than with 5.x for an invisible performance difference. Worth it !

- Things I may have forgotten

I hope you'll like it as much as I do.

Enjoy guys !
[Nexus 7 (2013) Original Android Development] sushi247:
hello! sorry for my late response, was a little caught up last days, im just flashing this now,

many thanks, it's like cookies to me man. will edit this soon with feedback!!!

l.e. allright first things first you cannot be sorry since you do so much for us, so thank you alot for that.

Now, i've used same settings as before everywhere. l2@glitch, 1998mhz, 450 gpu as I know for sure these are stable under any circumstance and I used msm hotplug. So after boot I loaded synapse, put 4 cores online, 4 cores boost (to make her really hot fast and see if and how she'll throttle), but I could not make her go over 1512 mhz(synapse system status). So I went to thermal and put frequency throttle at 100, core throttle at 100 just to eliminate thermal throttling. didnt mess with the 2 bars under as i dont know what they are (sorry, newbie). So what i get now is 1512 mhz on cores and 50c max temps. I rebooted.. synapse sais the same thing. I DISABLED core control, still locked at 1512 mhz, tablet is cool as ice. will come back with more news
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7272871]sushi247[/MENTION] The thermal presets I've made are probably too conservative (especially when overclocking) - most likely because of your previous report which influenced me, ahah - but everything is tweakable easily. The "critical" settings are understandable enough for someone who likes my kernel and its tweakability, I suppose. I'll make them more relaxed with the next update (Synapse polishing and functional presets/hotplug).

Also, don't even be sorry mate, I've been away from this thread for months before r498 release. I'm the one who can be sorry.

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

For the adventurous !

Devbuilds with preliminary Android 7.0 Nougat support are available here (r521 "N").

It'll run with the early Nougat builds available from Zaclimon's thread as well as DevSwift1's thread, (go thank the guys for the first Nougat roms on N7 2013 if you didn't already btw). It's basically r520 with added patches to make it boot on Nougat. It should also enable multirom to boot on secondaries since Nougat needs to be installed as primary for now (not yet tested). Thanks [MENTION=4217103]zaclimon[/MENTION] and [MENTION=4318865]DevSwift1[/MENTION] !

Edit : confirmed multirom booting Nougat both as primary and, as secondary with both Nougat or Marshmallow as primary. Now we need a way to flash it as secondary.

Forcing selinux permissive from aroma or glitch-settings may be required to fix camera.
[Nexus 7 (2013) Original Android Development] aigaming:
Whenever i install this kernel over the pure nexus project rom i got slow boot animation and then tablet boots and i have no display but tablet work's,with stock kernel everything is fine ;)

What could be an issue?(have it also on latest elementalx) Thank you in advance
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Are you flashing the CM version of the two kernels? Pure Nexus is AOSP based
[Nexus 7 (2013) Original Android Development] aigaming:
Yes m8,one is for stock and other for cm based rom's.i'am flashing the one for cm based rom's,verry strange thing :confused:
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Not strange because Pure Nexus is NOT CM. Try the one for "stock" ?
[Nexus 7 (2013) Original Android Development] aigaming:
You where right,i was shure that was based on cm but i was wrong,tnx again :good:
[Nexus 7 (2013) Original Android Development] tungdil:
Well ... there is the dirty way to edit the updater script: Find the following line

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") [COLOR="Red"]||
abort("E1001: Failed to update system image.")[/COLOR];

and remove the "|| abort ..." portion (marked in red).

At least this worked for me. 1.) flash the ROM, 2.) flash the kernel 3.) reboot. While flashing the ROM there are still two error messages. No idea if there are any unwanted side effects. So, do it at your own risk.
[Nexus 7 (2013) Original Android Development] cardula:
No, using the AOSP based kernel. Never tried the CM one.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Looks right to me.

Indeed, this will not work as you need the kernel to rewrite the file required to mount your f2fs partitions. Also, after the /data partition is formatted to F2FS, your internal SD will be blank, so you'll want to restore any backup and the files you need to flash next if you're not using an external usb disk.

Why not power+vol up for recovery instead of using the bootloader to go there ? The full wipe will break some kernel functions as some files are written to /data partition at flash time btw, and to be even safer you may want to flash the kernel first, format the partitions you want as F2FS, reboot recovery, then reflash rom, kernel(so it is able to write to /data as F2FS), gapps and at last supersu. Don't do a full wipe after that.

This one is strange. Did you let it reboot "cleanly" ? Or did you force it ?

And if you flash the kernel without changing your partitions to F2FS, is the same thing happening?

Thanks for your detailed report !

In the CPU tab in Synapse, what's the Max/Min freqs reading for each core ? If it's set to stock (1512/384), try to force them to your desired values there and try again without changing any other setting. That should do the trick.
[Nexus 7 (2013) Original Android Development] cardula:
Thanks for the reminder. However, I don't think my issue is related to F2FS, since the same issue reared its ugly head even after reformatting /data and /cache to ext4, then making a full wipe and re-installing ROM, Kernel, gapps and SuperSU. Also, the problem vanished once I again made a full wipe, then just installed Pure Nexus, gapps, and superSU.

Good point, thanks! Honestly I rarely boot to recovery from being powered down haha. I usually either boot from recovery from advanced reboot options or from bootloader after flashing a new version of TWRP. I honestly don't have a lot of experience with f2fs so that's good to know. This is only my 2nd time trying f2fs, (first time was on my Nexus 9) and the 1st time I was up and running first try.

I did a reboot system from TWRP, then that was when I got stuck at the google logo. Strange this is, when I tapped "reboot system" from TWRP, there was about a 5 second delay before the screen went black and the google logo came up. With the stock Pure Nexus kernel, there's no delay. It reboots to the google logo almost immediately. To answer your question, yes I let it reboot "cleanly" the first time, which got me stuck. I had to force reboot it in order to get the OS to boot. It was strange because the google logo looped 2 or 3 times before the OS actually booted.

You're welcome, thanks for responding! Yes, the same thing is happening. The last thing I tried before returning to Pure Nexus with the stock kernel (which is where I'm at now), was reformatting /data and /cache back to ext4, making a full wipe then flashing ROM, Kernel, gapps and SuperSU. Unfortunately, the issue persisted afterwards until I did yet another full wipe and installed ROM, gapps and SuperSU.

UPDATE: Tried this kernel with official cm13 August 20 snapshot build, (cm version, of course) works great! Thanks! Only strange thing is, it still loops 2-3 times during the Google logo. Rebooting can take a long time; however, boot time is normal once the boot animation starts. I've rebooted well over a dozen times (both from recovery and cold boot) and each time it has booted the OS successfully.
[Nexus 7 (2013) Original Android Development] idCyber:
R521 works great with "Flo AOSP N 7.0" v0.4 ROM. Thank you so much for sharing with us your kernel!

[MENTION=3847629]Tk-Glitch[/MENTION] it seems r521 breaks auto rotation (sensors) that have been fixed in the new version of the ROM.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4821463]cardula[/MENTION]

One of my mods/injections done at flash time is probably breaking Pure Nexus. I'll install it and find what could be different on this rom versus others. It seems unlikely that your tab just "don't like" this kernel.

Thanks mate ! I'll probably PM you a test build so we can see if it fixes the issue on your device.
[Nexus 7 (2013) Original Android Development] bugers:
deb - no sim card

[MENTION=3847629]Tk-Glitch[/MENTION] - would you please look for sim card support for deb.

I don't see device tree in your repo, dunno which you are using but I've installed your kernel on clean CM13 but it says now that there is no sim card.

If you need some testing, let me know.

BTW. Great job with kernel - deb works much faster now ;)
[Nexus 7 (2013) Original Android Development] Chrisis25:
I post it in other thread.

Thanks to all devs in XDA, without them our devices would not be the same.

Antutu 53295!! :D

This kernel is perfect in cm13 roms
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
You said you flashed R521 for N, but I can't find it in OP.

Could you give me a pointer?

Thanks.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Post 2565 of this thread...
[Nexus 7 (2013) Original Android Development] pss34:
One issue w/ pure nexus: sometimes after using YouTube display sticks in orientation, no way to rotate screen. Fixed by reboot only.

:x!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6603503]pss34[/MENTION]

I'll work on fixing Pure Nexus compatibility asap. I was away from home for two weeks, so hopefully I'll be able to work on it this week.

Something must have changed recently in the cm13 tree as it was already fixed not too long ago by adding fstab entries for radio.. Probably an easy fix. Thanks, I'll send you a dev build in the next few days.

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

New "something" to play with ! YAY !

12/09/2016 - Devbuild r529

What's in :

- Modified rom injection/flash time mods to be more robust - Hopefully this will fix deb radio again as well as Pure Nexus issues. THIS CHANGE MAY FORCE YOU TO REFLASH YOUR ROM TO BE ABLE TO BOOT (no wipe required)

- CPU clocks not applying after setting them through Aroma/glitch-settings.conf is fixed

- Security update to avoid invalid access to ashmem area

- 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". Since the Pure edition can be fully tweaked through config file and/or Synapse, while being able to keep your previous settings generated with the Full edition independently of the rom, it deserved a better name.

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

- Small things you won't notice

What's pending : Hotplug driver selector in Synapse, Presets, Deb and Pure Nexus users feedback concerning previous issues.

Enjoy, and feel free to help by reporting any issue you may encounter (especially with deb or pure nexus rom). Thanks !
[Nexus 7 (2013) Original Android Development] ranaxda200:
I'm on [MENTION=4318865]DevSwift1[/MENTION] 's nougat. Does this latest build fix the camera issue?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5293792]ranaxda200[/MENTION]

What camera issue ? Except for the very low video capture quality, my camera works fine on this rom.
[Nexus 7 (2013) Original Android Development] ranaxda200:
You mean r521N is for Nougat, right?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5293792]ranaxda200[/MENTION]

r521 N and r529 N are for Nougat indeed.

You need at least the version 0.5 (0.4 and lower will have issues with camera and sensors on my kernel as I didn't want to add hacks with questionable security). On 0.5 and now 0.6 version of this rom and using one of my Nougat kernels, camera works (with low quality video recording) as well as sensors.
[Nexus 7 (2013) Original Android Development] shantam3108:
Hey buddy.. For me kernel aduitor hangs whenever I change anything on Deb and synapse doesn't work
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

Force close then clean Synapse data and restart it. Should work.

For kernel Adiutor I have no idea. It works well for me on the flo roms (0.5 & 0.6). Are your using the latest SuperSU (2.78) ?
[Nexus 7 (2013) Original Android Development] shantam3108:
Yeah been using latest. With synapse I get json configuration parsing failure everytime
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

Did you install another Synapse supported kernel before on the same rom, or something like UKM ?
[Nexus 7 (2013) Original Android Development] shantam3108:
Ummm... Nope.. I thought ukm in integrated in the kernel.. Could you give the link :o
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
No you indeed don't need it. But it could have created issues if you did install it. The error you get means you either have a problem with root or with permissions/access to /data/synapse folder or that it even doesn't exists. Please could you verify that the folder is there, and that it contains data ? Also, what version of Glitch kernel did you use ? Full or Pure ?

Thanks.
[Nexus 7 (2013) Original Android Development] crypticc:
Even fix permission shouldn't be required.

Lost count of how many months since last did fix permission. Think was when my /data/media/0 and sdcard directories became separated and then that didn't work.
[Nexus 7 (2013) Original Android Development] galaxykeks:
Does this Kernel include this 'patch'?

http://xdaforums.com/showthread.php?t=2469261

Send from the N7²
[Nexus 7 (2013) Original Android Development] penguin449:
It's all just good practice, fixing permissions will mean i am 90% less likely to have problems then you ^.^
[Nexus 7 (2013) Original Android Development] nikr123:
Don't think so. At least not yet.
[Nexus 7 (2013) Original Android Development] galaxykeks:
[MENTION=3847629]Tk-Glitch[/MENTION]

Would u consider to take it in?

Send from the N7²
[Nexus 7 (2013) Original Android Development] xbs:
Option to disable S2W/DT2W w/ HW power button

Is it possible to have an option to disable S2W/DT2W if the user presses the HW power button and only have these features enabled when display goes off based on the time specified in settings or when the display is shut off by using the magnet switch?

This would be pretty handy for over night or long periods of inactivity and therefor saving battery.

TIA
[Nexus 7 (2013) Original Android Development] flar2:
I will be releasing this feature shortly on my github. Ibe been testing it all week and it makes a big difference.
[Nexus 7 (2013) Original Android Development] xbs:
Oh yeah!

Thank you for introducing this feature.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3299331]timrock[/MENTION]

You'll need to remove the 99glitch file in your etc/init.d/ directory to kill the sticky settings when you're switching kernels.

[MENTION=2867785]galaxykeks[/MENTION]

Yeah sure. I'll add it in next release.
[Nexus 7 (2013) Original Android Development] timrock:
thanks, so any idea why this isnt working?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3299331]timrock[/MENTION]

Not yet. I'll have a look as soon as possible ;)
[Nexus 7 (2013) Original Android Development] jordirpz:
For me, double tap works in 10/9 version cm nightly

Enviado desde mi Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] Grondinm:
It works. Sometimes tho it seems not to respond on first try...
[Nexus 7 (2013) Original Android Development] xbs:
+1
[Nexus 7 (2013) Original Android Development] Grondinm:
Hey TK. sorry to be a pain again but could you add this patch to fix a bug in multiboot.

http://xdaforums.com/showthread.php?p=45920207#post45920207
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=842211]Grondinm[/MENTION]

Sure mate. Added in next build.

About the double tap to wake, shortsweep was always off before but now it's on by default in aroma. Are you experiencing the same behaviour with it on and off ? Because I don't see what else it could be for now.
[Nexus 7 (2013) Original Android Development] Grondinm:
Thanx. I turn of sweep2wake and sweep2sleep. I will try with them on with next build.
[Nexus 7 (2013) Original Android Development] MBQ_:
Next up:

Bash2Wake

Simply bash your head on the N7 and it'll wake. ;D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Release time guys ! Enjoy ;)

13/10/2013

- Updated kexec support to fix it when used on CM base (the one I'm using obviously)

- Fixed shortsweep

- Fixed magnetic on/off

- Fixed some aroma settings not sticking

- Added tni.andro's battery life extender support / configurable with aroma

- Update sweep2wake/doubletap2wake from flar2, adding new options :

- Added new S2W/DT2W/S2S options configuration in aroma
[Nexus 7 (2013) Original Android Development] shantam3108:
I am using full version. Their is no folder for me.

I tried uci commands and got this may be this could help
[Nexus 7 (2013) Original Android Development] shantam3108:
Here
[Nexus 7 (2013) Original Android Development] shantam3108:
After running uci commands folder showed in synapse was Glitch which was empty
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

Thanks. Can you try to flash the Pure version and tell how it goes ? I'll check on my side if I nuked the Full version.

(edit your message next time when nobody yet answered to the thread, instead of making a new one. Mods may bite :p)
[Nexus 7 (2013) Original Android Development] shantam3108:
Thanks :} will flash and let ya know.
[Nexus 7 (2013) Original Android Development] shantam3108:
Didn't flash.. Got error while flashing..

:p I know to edit it but xda labs app doesn't show upload picture option on editing the post so had to do. Again :p
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

So the sdcard backup is missing as well... Meaning the glitch script didn't run after the first boot after Full flash, explaining why Synapse doesn't work (but at this point, none of the Aroma settings will work if the script doesn't run). Could you check your /init.rc to see if the line "import /init.glitch.rc" exists, as well as if the /init.glitch.rc file is present ? That's the trigger for everything else. Thanks.
[Nexus 7 (2013) Original Android Development] shantam3108:
Sorry was night here... Just woke up

One thing more when changing governor with ka tab hangs everytime

The permissions are 750 to this file
[Nexus 7 (2013) Original Android Development] shantam3108:
Sorry was night here... Just woke up

One thing more when changing governor with ka tab hangs everytime
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

No problem mate, I should have gone sleeping a while ago myself.

I tried right now with every single governor available and kernel adiutor applied them without problem. No hang for me..

What's your recovery ? TWRP 3.0.2.0 ? Did you overclock your CPU or L2/cache during setup and to what kind of values ? Unless I get more reports of such issues, I'll assume it's down to your setup.
[Nexus 7 (2013) Original Android Development] shantam3108:
I set everything on default while flashing the kernel didn't change anything except the io scheduler to deadline and Reade ahead to 1024kb

Edit just restarted synapse it started working now :D lol

Didn't touch the tablet for the night and now this
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=6812813]shantam3108[/MENTION]

Doing a clean install of DevSwift1's latest rom right now to see if I can reproduce any of your issues.

Edit: What the H ? It makes no sense :D
[Nexus 7 (2013) Original Android Development] shantam3108:
LOL I don't even no.. I didn't do anything but now it's working.. Just tried flashing pure version that's it.. And i may add it's working very great.. The device is working smooth as butter with no heat at all.. :laugh:

No Issues.. No hangs... No lags... Just awesome