yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] htb2050:
I am currently using AICP. Tried AOSP based but they aren't usually updated much and have a lot of bugs with cm based you can be sure of getting updates every month including security patches and any point releases. Currently on AICP because its the only available one currently and the developer provides weekly updates so its going to be supported. And the guy who runs AICP rom has a deb too so that will be well supported when CM does an official deb update.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Using a private beta build ATM...
[Nexus 7 (2013) Original Android Development] nokiagye:
Where is the 7.1 aicp link can't find it nowhere
[Nexus 7 (2013) Original Android Development] htb2050:
Nice!!! For which rom?
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Darkkat. (7.0).

Cheers.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Right here.
[Nexus 7 (2013) Original Android Development] HatchetEgg:
I have a tried to install this on my device, but unfortunately the performance goes right down to the floor, I. Have to wait a good 10 minutes to boot. I have also tried other kernels but they too have the same issue. Any support would be appreciated
[Nexus 7 (2013) Original Android Development] brolic925t:
You need to flash the cm varient if youre on aicp
[Nexus 7 (2013) Original Android Development] HatchetEgg:
I'm on the exodus rom which I think is based on ASOP
[Nexus 7 (2013) Original Android Development] nokiagye:
Thanks but the threat is deleted any other link?
[Nexus 7 (2013) Original Android Development] htb2050:
It's working here dude. Stay with stock.
[Nexus 7 (2013) Original Android Development] nokiagye:
http://xdaforums.com/showthread.php?t=2013
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4795439]nokiagye[/MENTION]

My link definitely works. Yours definitely doesn't. Something's wrong on your side it seems. Using the old XDA app maybe ?

Your link :

My link :

http://xdaforums.com/nexus-7-2013/development/rom-aicp-12-0-n-7-0-0r14-unofficial-t3481229 (xdaforums.com/nexus-7-2013/development/rom-aicp-12-0-n-7-0-0r14-unofficial-t3481229)

[MENTION=4730318]HatchetEgg[/MENTION]

Checked Exodus sources. It's definitily based on CyanogenMod, so AOSP kernel won't work. Grab the CM variant of my kernel and try again. Also, since latest Exodus nightlies are 6.0, you'll need the "MM"(Marshmallow) kernel.

Please tell me how it goes, thanks :)
[Nexus 7 (2013) Original Android Development] HatchetEgg:
[MENTION=3847629]Tk-Glitch[/MENTION]

Ok thanks for letting me know, I will give you an update some time soon, thanks for your help.
[Nexus 7 (2013) Original Android Development] brolic925t:
Meh... Have the worst luck with this device.. doesnt even get to the bootanimation when i flash 533 cm varient for cm14.1 latest nightly
[Nexus 7 (2013) Original Android Development] HatchetEgg:
[MENTION=3847629]Tk-Glitch[/MENTION]

All seems to be working well now. :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4730318]HatchetEgg[/MENTION]

Great news :)

[MENTION=4347548]brolic925t[/MENTION]

I'll check this out asap.
[Nexus 7 (2013) Original Android Development] Link0909:
Awesome Kernel! Won't use anything else on my N7 nothing comes close to the speed I get with this. Do you support any other Nexus devices? Just wondering. Scored a 45,000 on AnTuTu benchmark killer!
[Nexus 7 (2013) Original Android Development] brolic925t:
Did you ever figure our the problem?
[Nexus 7 (2013) Original Android Development] Icewyng:
Confirming that the latest nightly from CM (19112016) get stuck at the google screen. Was doing the same thing with 17112016.

Looking forward to be able to flash it back. Love your work Tk-Glitch.
[Nexus 7 (2013) Original Android Development] wantowan2:
Some issues with the caf based aicp (latest nov build) ROM too.

-Launcher items not drawing correctly (malformed app drawer icon etc,.)

-Kernel Adiutor FCing (sysfs?)

-boots most of the time but freezes randomly sometimes @ unblanking display

-I dont think I got any logs but I can check (my USB port is pooched so pulling them on a struggling device sucks...)

Tried

Glitch-N.flo.r533-CM-Pure

Glitch-N.flo.r533-CM-Full
[Nexus 7 (2013) Original Android Development] poondog:
Cm changed their kernel base for 14.1

Its based on zwliew rebase

You'll have to rebase :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I'm on it guys.

Edit :

29/11/2016 - r534 :

This kernel will only work with AOSP 7.x and latest CyanogenMod 14.1 based roms. If you get incorrect colors and slow UI, rollback to r533 CM.

- Rebased using CM14.1 tree

- Updated color controls to mimic CM's PCC implementation (Thanks [MENTION=4684315]flar2[/MENTION])

Edit2 : Something happened during the last compilation it seems. Re-releasing in a few.

Edit3 : Re-released r534. Everything should be fine now.

Edit4 : Well. Running latest CM14.1 nightly, it works, then it doesn't, then it works again. I'm tired. I'd say using r533 AOSP (so, non-CM) is better on CM14.1 as of now.

Edit5 : Or not. Same behaviour. It worked, then after a few reboots it wasn't anymore as well.

Edit6 : Currently updating my scripts to work similarly to latest EleX as it seems to fix settings restore on CM. I'll also check last nightly as it seems the required "fix" is now built-in and may fix boot inconsistency with r533. Also working on a "second pass" to my rebase to fix old issues.
[Nexus 7 (2013) Original Android Development] brolic925t:
Sooo... Are we safe to download r534.. lol
[Nexus 7 (2013) Original Android Development] pss34:
I'm on it. All is OK.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4347548]brolic925t[/MENTION]

It's stable on AOSP. I'm not satisfied with it on CM14.1 though, so next update will fix that (and will offer much better performances in many cases, too). I have a few merges to bring back and some work to do on the installers (especially Aroma). You can expect the update to be available either later today or tomorrow.

Here's my to-do list before release :

- Bring back HAVE_HW_BREAKPOINT feature flag
- Disable stacktrace/tracing again ?
- Add ElementalX governor + gboost
- Verify MSM_LIMITER hooks
- Merge cpufreq / re-enable smartmax

- ramdisk
- Rework (remove ?) Synapse init script

- release
- Update default .conf profile

- Aroma :
- Cleanup
- Update values
- Add flar2 DT2W/S2S... options
- Add FSYNC switch
- Updater script

- Synapse :
- Add flar2 DT2W/S2S... options
- Add FSYNC switch
- Update profiles(thermal, high perf -> hotplug 2 cores min ?)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks for the continued support TK. Very much appreciated....

Cheers
[Nexus 7 (2013) Original Android Development] coremania:
Selinux permissive patch still avaible in the new aroma release for cm14.1 ?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
New release is out!

04/12/2016 - r540 :

Due to some of the changes in this build, restoring settings from sdcard backup (by flashing Pure Edition or restoring through Aroma) may lead to different settings being applied depending on what you set before. It is strongly suggested to use the Full installation at least once to update your settings or delete glitch-settings.conf on the root of your sdcard before flash to use the default preset.

- Post CM14.1 merge cleanup pass. It was definitely needed ! Including, but not limited to :

- Removed Lazyplug and Intelliplug hotplug drivers (due to conflicts leading to performance issues)

- Removed Dynamic Fsync / Added switch to disable Fsync (after corrupting ~15 installations with DynFsync, I don't feel like it's worth the slight I/O perf boost)

- Replaced Showp1984's DT2W by flar2's S2W/S2S/DT2W (the touchscreen issues I faced with it aren't reproducible anymore)

- Removed LZ4 and use XZ compression instead

- Removed WQ_POWER_EFFICIENT (couldn't see a measurable gain with it enabled)

- Removed ROW ioshed

- Rollback'd to older Intellidemand governor​

- Reworked settings application and restoration system to work with CM14.1/without SuperSU and load it early during boot by init hooking (CM14.1 PCC livedisplay related race condition "fix" included). Note : MultiROM users, you may want to disable MultiROM menu if you have it enabled to further reduce the chances to trigger the issue (completely fixed it on my side). Feel free to report your findings on the matter.

- Added flar2's ElementalX governor

- Updated default profile (the one you get while flashing Pure package or using restoration option in Aroma without sdcard backup)

- Updated thermal profiles

- Updated available options in Aroma

- Updated busybox to 1.25.1 YDS and moved from /sbin to the more convenient and standard /system/xbin

- Updated Selinux switches to work with more roms (now working on CM14.1

because

of [MENTION=7213002]coremania[/MENTION] :o)

- Moved Synapse files from /data/synapse to /res/synapse in ramdisk

- Updated Synapse presets

- Updated Synapse settings (Aroma installer will give more gestures-related options though, at least for now)

Enjoy guys !
[Nexus 7 (2013) Original Android Development] coremania:
:good: thanks !!!

Just flashed on clean cm14.1, works great so far, but set selinux to permissive with Aroma, cm stays enforce after boot.

For my understanding, does it only gives me the possibility

to run permissive by setting up with kernel auditor mod for example, or does it simply not work ? I thought it should force the rom to run permissive. On my nexus 6 with permissive kernel cm 14.1 is forced to run permissive, and Dolby works ;)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7213002]coremania[/MENTION]

The trigger that makes the switch at boot time on CM14.1 needs root access, like Synapse. I suppose you have root disabled so the trigger doesn't run at all. CM built-in root(enabled from developer options) was what I've been testing with though SuperSU should work just as good.

I will see if I can make this work without root for the next update.
[Nexus 7 (2013) Original Android Development] coremania:
Yes, I flashed together with clean rom, so it's disabled, but usually I'm on root. It's cm14.1 related, that's right, on any other

asop rom you can switch any kernel with app to permissive and everything which needs to be permissive runs well, but not on cm. On my Nexus 6 I use blackbird kernel, which is permissive out of the box and I'm good with it
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7213002]coremania[/MENTION]

Then you want to give the user the possibility to select some options, to enable/disable stuff, so you make a config file with scripts to read from it, then you add Aroma, then you want to preserve original ramdisk files, so you add flashtime ramdisk editing to some more scripts, then you make some scripts to write some other scripts depending on the user's choices, then you find out that what works on this rom doesn't on another one, so you add some checks to your scripts to write scripts differently to work with different roms, then you want to add some kind of backup + restoration system, then you build two packages, then four to support both AOSP and CAF based roms, then two again because CM backdashed, then you link your scripts to the scripts that made some scripts to edit scripts to make some other scripts work, to find out that CM don't like it, so you have to make some more scripts and potentially break what was working everywhere else so CM is happier.

The "hack" I'm using atm for Selinux switch is very inelegant, so you can be sure I'll try to find a better way. At least it works on CM14.1 builds for flo/deb... for now :laugh:

While I'm not a genius by the likes of flar2, Faux123, franciscofranco, Showp1984, neobuddy89 and many others around here, I'm relentless. As long as there is an ounce of energy in me I'll learn and try my best to fix stuff, be it this N7 kernel or a friend's heart. So we'll find a way for sure :)

As long as [MENTION=5863767]SHABBYLEA[/MENTION] pings me out of death every time, I suppose it's worth the trouble :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

Haha ;)

I guess you thanked me more than anyone ever did, making the effort of posting to do so, very frequently.. I'm smiling at the sight of your nick in my mailbox. Thank you, whoever you are. That helps more than you might think, even though I said that already in the past.

BTW, told ya !

I think I've found the cmdline combo I was searching for. No more need for root to enable/disable SElinux permissive and no more need to trigger some post-boot scripts. Thanks [MENTION=7213002]coremania[/MENTION] , you put me on the right track. I'll be able to sleep better tonight, that's nice!

r541 on its way.

Edit : It's up !
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
OK... Thanks again...?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Now that's hilarious :laugh:

My pleasure !
[Nexus 7 (2013) Original Android Development] coremania:
Made my day, works fine, so another big thanks ;)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
?

On a more serious note, have you noticed an increased battery drain on r541 as opposed to r540?

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

Interesting question. To be honest, I did not notice any difference. Considering the only thing that changed that could impact power consumption is the script that was triggered on r540 for Selinux + Synapse init, r541 should even use less power (yet the difference should be negligible at best). Though since the flashing script is wiping cache partition, you will notice higher battery drain for a few hours up to a day or two, depending on your usage. Give it more time and see if everything goes back to the levels you're expecting.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Just before I saw your post, I was going to post that I'll keep an eye on it (after flashing many ROMs/kernels I think it's best to let things bed down). Anyway, you're right...Batt usage back to normal, by which I mean excellent...

Thanks.
[Nexus 7 (2013) Original Android Development] jordiiB:
Hello guys, I glitched my N7 with r541 and I've noticed that the lowest screen brightness is almost dark, I can't even see it in a dark room... Does it only happen with me ? I'm running cm14.1 btw
[Nexus 7 (2013) Original Android Development] coremania:
Everything working, with and without adaptive and live on

Edit: runing cm14.1 too
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
This is one of the features available in the kernel. You have a few options to disable this and get stock brightness. You can :

- Untick "backlight dimmer" in the Aroma installer during flash with the Full package. This will stick as long as you're not overwriting your settings with Aroma.

- Edit glitch-settings.conf on the root of your sdcard, by setting a value of 0 for "BLD" entry, then reflash the kernel using either the Pure package or using the restoration option in Aroma with the Full package. This will stick as long as you're not overwriting your settings with Aroma.

- Install Synapse from the Play Store, go to the "GPU & display" tab and move the slider for "Backlight Dimmer Control" to the left (for a value of 0). This will be tied to Synapse and you'll have to do it again if you update your rom.

I hope that was clear enough :)
[Nexus 7 (2013) Original Android Development] jordiiB:
Yes, it was. But I don't think you understood what I meant ^^

I want the backlight dimmer, I had it with ElementalX too. But the value of minimum brightness is too low compared to the one I had with EX... Maybe a clean install will solve my problem, I'll try it this weekend
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4924418]jordiiB[/MENTION]

Oh I see. You may want to try a lower value then. It's 4 by default. Maybe 2 would do the job for you :)
[Nexus 7 (2013) Original Android Development] coremania:
Are you gonna merge december security???
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7213002]coremania[/MENTION]

From what I've seen, nothing to merge. r541 contains these fixes already when it applies.
[Nexus 7 (2013) Original Android Development] coremania:
:good:
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks again for the latest Glitchbo...
[Nexus 7 (2013) Original Android Development] coremania:
:good: Short report: works absolut stable and great on latest cm nightly
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Merry Christmas to you and the ones you love guys. See you next year !
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Same back...?

Thanks for all your hard work...
[Nexus 7 (2013) Original Android Development] wantowan2:
Hey, you too man! Thank you and all the best.
[Nexus 7 (2013) Original Android Development] Extreemator:
Warning to chromecast users: this kernel might not be compatible with mirroring and cause all casting to stop working, can also break the rom on CM. Might be the hotplug issue.
[Nexus 7 (2013) Original Android Development] coremania:
No issues with chromecast on cm,los or aosp works great,

I had some problems with cm, sometimes the screen wouldn't

turn back on, doesn't matter which way I choose dt2w or buttons.

But I flashed los nightly yesterday and it works perfect with this kernel, hope the dev continuous, booting permissive still great for dolby :good:
[Nexus 7 (2013) Original Android Development] Extreemator:
Aosp mirroring performance is horrendous. Cm is much better. I spend 2 days installing and reinstalling roms going nuts to figure out that this kernel was causing incompability specifically to mirroring. With my nexus and very likely with others
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
I'm running an AOSP based ROM on Glitch 543 and I've experienced no issues whatsoever when casting. I'm not saying you've had no issues, but sometimes it's very hard to pin these things down....It may not be a kernel problem at all.

Cheers.
[Nexus 7 (2013) Original Android Development] Extreemator:
Oh i pinned it down clear enough, spent three days. Aosp mirroring works with this kernel, just it's very laggy (i am assuming it's the aosp fault not kernels but i didn't compare) and please be specific. Casting always worked, mirroring what's breaks (on cm) .
[Nexus 7 (2013) Original Android Development] coremania:
As I mentioned no issues on los and aosp
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
As far as I can remember, mirroring has always been fairly laggy (on xxx Roms), however, I'll test this issue in more detail...

Cheers.
[Nexus 7 (2013) Original Android Development] AlmostIdiot:
After I installed it with aroma, settings are not sticking. Only with synapse
[Nexus 7 (2013) Original Android Development] wantowan2:
2 cents here. As a former dev I can say that these tips may trigger a memory of some commit that may be causing problems or something random. Logs. Kmsg, dmsg or logcat. Anything that shows the issue. They aren't always easy to read but they are easy to get. Paste the contents at pastebin, paste the link here. On Linux, the easiest way is just [ adb logcat ] the buffer fills. Tons of apps that pull these too.

Sometimes it will look like a specific hardware item but ends up being no permission given in vendor .

I don't mean to be one of those guys. Its just really the best/fastest way to get the answer/fix your looking for. If you pulled a log at the beginning of those 3 days before you figured out a maybe, the dev might have seen the log that night, posted a fix 2 days before you finished your testing.

Anyway, good luck.

Edit:

Have you tried a few clients. Mirroring, I think you mean strait casting. Your device screen on TV. That said there are few apps that might take over from the ROMs casting back end.

Reinstall the casting dongle and try say:

Google Home or

localcast

Both of those are fairly robust and my also add threads to the process giving more bandwidth
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Good advice. I find localcast to be a great app, and rock solid...

Cheers.
[Nexus 7 (2013) Original Android Development] coremania:
I noticed that on los with r543 the activation of adaptive brightness leads to turn off screen, and I'm not able to turn on screen again by touch or buttons after that. I usually don't use adaptive brightness, that's why I notice this so late.
[Nexus 7 (2013) Original Android Development] boom1982:
Good kernel...but gps does not work)
[Nexus 7 (2013) Original Android Development] qlver:
So you got r543 work on your flo (or deb) with Lineage OS 14.1?

I flashed r543 with TWRP (with the default set of kernel) to my flo with Lineage OS 14.1, but it just went boot loop.

Wondering what's going wrong...
[Nexus 7 (2013) Original Android Development] coremania:
It was running well on my flo with los, I think it could be the battery saving option in livedisplay which leads to my issue.

Btw I flashed 543 after a clean los install, may you retry.

Hope the dev continues this kernel.
[Nexus 7 (2013) Original Android Development] qlver:
I thought there were some difference between LOS and CM, but seems not.

I'll give it a try to do a clean install. Thanks for your reply :D
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Sorry for the delay, life happened. I've been reading your comments and issues, but wanted to take the time to answer as good as possible.

[MENTION=4190491]Extreemator[/MENTION] About chromecast, I don't have one to test to begin with, but I didn't do anything that I see that could interfere with the base. As the kernel has been moved to the zwliew rebase (LineageOS), such issue might have more to do with the base or rom rather than my additions/mods. If the behavior is different from stock LOS kernel or EleX (same base), then it could be my fault. It doesn't seem likely though, at first glance.

[MENTION=7213002]coremania[/MENTION] I tried many times in different ways, but couldn't reproduce your issue. Did you set the backlight dimmer to enabled maybe ? Though it shouldn't appear completely black, unless you were right under hard light out on a sunny day I guess. If you flashed the Pure package, that might be it. I've been reading that some of these N7s has a different panel than others and it could be that the backlight on these has a lower default value. I couldn't find specific informations about this so it's only a theory at this point. I should disable the option by default if I get more clues about the matter.

[MENTION=7890918]boom1982[/MENTION] GPS works well on the two devices I'm working with. Maybe more to do with your rom ? Does it happen on any rom ?

[MENTION=7918241]qlver[/MENTION] The kernel is based on the latest LineageOS kernel source. Since nothing has changed in the source since Dec 22, 2016, r543 is 100% compatible with the latest LOS and LOS/CM based roms. It might have been either a bad download, a bad nightly, incorrect/unstable settings or incompatible cache/data requiring a full wipe. I've been running LOS since before official nightlies started with zero issue myself. Currently running the 20170221 nightly as my primary OS.

[MENTION=5678172]AlmostIdiot[/MENTION] That's definitely strange if you've installed r543. What rom are your running ? None of the settings are sticking or just some of them ? And if so, which ones ? Thanks !
[Nexus 7 (2013) Original Android Development] coremania:
Yes, turn off backlight seems to be solution for me.

Bus oc is so nice, carbon runs like hell on my flo :good:
[Nexus 7 (2013) Original Android Development] BlackJack'89:
Nice kernel, work well on last LOS

Inviato dal mio Nexus 7 utilizzando Tapatalk