yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Neo:
Same here guys :) I have been entertaining the idea of packaging EX with the weekly RR builds I do for shamu, since it has 8.1 compatibility, with your permission as well [MENTION=4684315]flar2[/MENTION].

[MENTION=4450173]camcory[/MENTION], it was brought to my attention by another member some time back that your androidx builds have the most stability on shamu due to your device bringup vs what is being used in other rom variants. I have long since been a supporter of maximum tweaks and mods in a rom until building out your androidx rom and experiencing that stability and fluidity for myself.

It has now placed me in a funny position where I no longer care to produce other works and wanting only to build out your rom, yet adding a few tweaks of my own that I can not part ways with.

With your permission also, should I ever choose to do so, I would like to be able to provide modified versions of your androidx rom to the public. I haven't really made up my mind yet if this is something I want to do and I apologize flar that this is request is taking place in your thread rather than a PM to Cory. I saw you guys as a package deal from my request and wanted to hit you both in this single message. Call me lazy :P
[Nexus 6  Original Android Development] magnamentis:
i know it's against the rules but this is worth a crosspost ( i hope at least ) else don't bite me, intention is good

from march 16th and younger builds are in danger to fail googles latest safety test (playstore certification) hence be careful with clean flashes, you have only 100 different IDs to circumvent the problem by manually certify (register)

bad for clean flashers and early adopters. the 100 limit is per device because it's about device certification

https://www.androidpolice.com/2018/0...xemption-roms/

i think each user has to be aware of this change before falling into the trap, original post is in neo's rom thread for shamu / oreo / 8.1

also read this because i dunno which is the original, i think this is it : https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/
[Nexus 6  Original Android Development] flar2:
Anyone can feel free to use ElementalX in their builds
[Nexus 6  Original Android Development] Neo:
Good to hear, thank you sir.
[Nexus 6  Original Android Development] magnamentis:
a great move IMO, only thing i'm missing is EX, using it for more than 5 years on any of my devices where it is/was available mostly nexi :good::good::good:

didn't try to flash on 8.1 because i wouldn't have the time to fix things and/or fiddle too long right now, certainly sound familiar to NEO
[Nexus 6  Original Android Development] wavedashdoc:
I am concerned about this too. I just cleaned flashed Beltz (before it was pulled) but didn't come across any warning about being uncertified.

I'm wondering if this isn't being triggered wide scale yet. And or if it has to do with using an older GAAPs package from before March 16th.

Hopefully we'll get official word from Google, because I'm hoping this isn't the end of custom development and being able to run Google Software.

Sorry if this is off topic.
[Nexus 6  Original Android Development] magnamentis:
seemingly magisk is solving this for now but that would mean to first root and then flash gapps which in the past could cause issues.

i'm still positive that there will be workarounds for some time to come but all this ever tightening rope thingy i've seen coming for years while my early remarks about it were often bashed with fanboyish stuff.

look at the rom scene and one can see the results. imagine where we would be without LOS and what if they throw the towel ?

as i said, it will go on somehow but ever more restricted and more difficult ( substratum is at risk to now work in "P") and generally i hate to see when gigantism and arrogance kills of the communities that made them big.
[Nexus 6  Original Android Development] wavedashdoc:
With as many excellent Devs that are out there, I believe you are right. It's interesting, I think Google has played this quite well (minus the timing). Once Nougat came out officially from Google on my Nexus 6 I didn't see a reason to run custom roms again, everything worked well. Then the 7.1 update was delayed, and delayed and then delayed again. So I once again jumped back on the custom rom scene. But now, IMO, is the strongest and most friendly the custom rom scene has ever been. (Minus the early Oreo 8.0 drama, with a few communities)

I think Google picked a poor time to implement this new device limiting change,especially with all Nexus devices EOL. And I think they are going to see a huge backlash from the community. As more and more users flock to custom roms for continued support. And, I think for the first time, I won't rush to flash P. It offers nothing of interest and actually takes away quite a lot of what makes Android, Android. Oreo had matured so fast that we have stability and some great custom rom features to go with it. Of course time will tell.

All in all, I hope this doesn't discourage anyone. And yes I use Magisk 16 and it works great. Device shows certified in the Playstore and I can run Netflix and YouTube TV without issue. So for me, all my needs are met. And I will continue to update the OP so users can continue to discover more great Devs and their ROMs.
[Nexus 6  Original Android Development] Elektroschmock:
Since this commit the kernel only works on ROMs which adapted their fstab to early mount support.

https://github.com/flar2/shamu/commit/fdd8b32cf1996cff40a873493f9f1132c90230f3

Like I did for LineageOS her:

https://github.com/LineageOS/androi...mmit/f1e246ba37075026144f5be8e132b7f3ae4628ac
[Nexus 6  Original Android Development] NLBeev:
Nexus 6 unencrypted. Beltz with Ex5.14 built-in dirty flashed over previous version.

No issues running smoothly. Thx
[Nexus 6  Original Android Development] provolinoo:
I tried to install "LOS 15.1 beta 4 + OpenGApps 8.1 + ElementalX 5.08 + Magisk 16.3" (in this order, using TWRP 3.2.1-0) but my Nexus got stuck on Google logo :(
[Nexus 6  Original Android Development] camcory:
Just looking at commit history I believe you need 5.10 or above due to the commit you just quoted by [MENTION=3383960]Elektroschmock[/MENTION]
[Nexus 6  Original Android Development] wavedashdoc:
Speaking of [MENTION=3383960]Elektroschmock[/MENTION] looks like he fixed the soft reboot issue at first boot in his newest kernel for Lineage 15.1 beta 4. ?

Awesome work, all dev's are really doing an amazing job supporting Shamu.
[Nexus 6  Original Android Development] ikramii:
Does DU12 work with latest exkernel manager?
[Nexus 6  Original Android Development] ajaynsurana:
No it doesn't. What I mean is you can change kernel settings but can't install elementalx kernel
[Nexus 6  Original Android Development] Sanabil:
Hi

I am having trouble with setting any other governor in The official ElementalX manger app other then elementalx , if i choose on demand any game or app i use stops working , crashing.

I tried other governor within app like interactive but no luck.

I am on stock Nougat 7.1 with Magisk 16 rooted and also flashed Official Elemental kernel.

Any idea what i am doing wrong? I tried searching but could not find any answer.

Thanks
[Nexus 6  Original Android Development] RingooXDA:
does 5.08 kernel for oreo 8.1 work fine on rr 8.1
[Nexus 6  Original Android Development] magnamentis:
not booting on my N6 with RR but better verify, there are various versions and it's quite easy to restore from nandroid, gets stuck on ROM-Level not on boot-level, means will pass google logo but doesn't boot into system.

i got the impression that [MENTION=4203241]Neo[/MENTION] is considering to include EX in one of his future builds but then who knows, perhaps i got that wrong, would be nice though.
[Nexus 6  Original Android Development] ardonhs:
My phone throttling / snore when I have 50% battery or less :(

Nitrogen 8.1
[Nexus 6  Original Android Development] RingooXDA:
thank you the same not boot it go to rr bootanimation but not boot
[Nexus 6  Original Android Development] Neo:
That was my intent, but I haven't built with it yet for RR and I'm on vacation for a week :)
[Nexus 6  Original Android Development] gothy.gothy:
You'll build just in time when April security patches will emerge...
[Nexus 6  Original Android Development] mugendon:
never mind
[Nexus 6  Original Android Development] ahmedkordofani:
Latest EX tested with Official LOS 15.1 build no luck:(
[Nexus 6  Original Android Development] ExpertMC:
Latest being 5.08?
[Nexus 6  Original Android Development] ahmedkordofani:
5.16
[Nexus 6  Original Android Development] magnamentis:
5.16

EDIT: [MENTION=8134656]Josephson47[/MENTION] your post is on next page on my setup, hence the ninja post, better twice than none :) :highfive:
[Nexus 6  Original Android Development] SteveYoungs:
And it's not just you, I can confirm. It gets to the boot animation and no further.
[Nexus 6  Original Android Development] jtwebfusion:
I tried searching for this but didn't find anything. When checking for updates in the manager, it's says there's an update available even though I'm on the latest. I wasn't sure if this was a manager or rom issue. I'm on Nitrogen 8.1.
[Nexus 6  Original Android Development] cujo6801:
It's an app thing

that's why I put mine on manual check for updates..

"Sent from the Dog Pound"
[Nexus 6  Original Android Development] magnamentis:
this usually happens if you deleted or moved the zip from the EX folder on your storage. many move the kernel zip instead of copying it which makes the app believe it's not downloaded.

not saying this is it but it's the most common reason for this to happen
[Nexus 6  Original Android Development] flar2:
I just needed to change the kernel version on my server.

It should work properly now.
[Nexus 6  Original Android Development] rodritoledo94:
5.16 still doesn't work with LOS 15.1 on my nexus 6 :(
[Nexus 6  Original Android Development] disiz:
Thanks again for this kernel I used since Pure Nexus Marshmallow, I've tested 5.08 with AospExtended 5.3 that is aosp based, but after google logo nothing happen. But thanks for still being here and for updates man :)

Edit : I've now flashed the last nitrogen that include your last kernel, but how to configure Dt2w and else now ? Previously I think it was system/etc and edit elemental.conf file. Thanks.
[Nexus 6  Original Android Development] provolinoo:
As claimed by [MENTION=3383960]Elektroschmock[/MENTION] the use of custom kernels is highly not recommended on Oreo ROMs like LOS 15.1

https://xdaforums.com/showpost.php?p=76125661&postcount=36
[Nexus 6  Original Android Development] Neo:
If you like your kernel to remain stock and LOS modified without all the added goodies, then sure :p

However, Flar's kernel works just fine on "primarily" Google sourced builds.
[Nexus 6  Original Android Development] magnamentis:
good kernels that boot are very much recommended always and if it doesn't boot it does not need to be "not recommended" because

it's impossible to use it ;)

as it seems many already forgot or are too young to remember the same situation not that far back when CM Roms were mostly incompatible with AOSP based and/or close to stock Kernels, only then it was an official approach by CM and the incompatibilities were the same across the board so that many dedicated kernel devs had two kernels per device in the portfolio, one for AOSP based and one for CM based roms.

this time they just did it and it's different on different devices so that it's too messy to cover all kinds of devices with 2 kernel versions.

after all i do not fully understand why kernel devs mostly stick to AOSP version because there are not many AOSP based roms left as compared to a few years ago and the majority of custom roms are now based on LOS (exCM) hence if i would be a kernel dev i'd either do both or choose LOS variant where the majority of custom roms are coming from.

of course the above does less apply to currently fully supported nexus and pixel devices but again, that's a minority.
[Nexus 6  Original Android Development] michele72:
5.16 works fine in the latest unofficial Screw'd (Aosp based) , as a matter of fact they baked it in natively. However I just tried the 5.17 update and it says in TWRP that the zip file has invalid format. Downloaded some times to make sure, so not due to broken download.
[Nexus 6  Original Android Development] SteveYoungs:
5.17 is not working with official LOS 15.1. Same as 5.16, it gets to the boot animation and no further.
[Nexus 6  Original Android Development] jtwebfusion:
5.17 is throwing an invalid zip error when installing in twrp. Tried downloading it twice through the ex manager. Currently running 5.16 on Nitrogen.
[Nexus 6  Original Android Development] gothy.gothy:
5.17 works great on latest NitrogenOS
[Nexus 6  Original Android Development] wavedashdoc:
I too also get the error on Beltz 4/5/18 build. A work around is to flash the "express" version. Then it installs fine. Closer inspection of the zip reveals that 5.17 is missing the "meta-inf" folder.
[Nexus 6  Original Android Development] ajox:
Also getting "invalid zip" Error on latest Aosip. Running 5.16 ans want to Upgrade to 5.17 with paid and latest ElementalX App.

Please fix that :)
[Nexus 6  Original Android Development] cujo6801:
5.17 works fine with AOSiP

"Sent from the Dog Pound"
[Nexus 6  Original Android Development] flar2:
I'm re-uploading it now
[Nexus 6  Original Android Development] NLBeev:
Ex 5.17 works with Beltz 180405

Updated with Ex manager without issues.
[Nexus 6  Original Android Development] wavedashdoc:
Re-uploaded version works now ? thanks [MENTION=4684315]flar2[/MENTION]
[Nexus 6  Original Android Development] michele72:
Thank Flar2, now though it says "download failed". I tried hundreds of times. I deleted the previous file from the folder but still no luck. Edit: I cleared the data of the app and rebooted, and now it worked! So all good! Cheers
[Nexus 6  Original Android Development] adm1jtg:
Which version has April patches if any
[Nexus 6  Original Android Development] flar2:
5.17
[Nexus 6  Original Android Development] kol1124:
Thinking about why my phone is always stucked at 1497 Mhz, in case that I changed it to 300 Mhz... no deep sleep... Any resolution to solve this problem?
[Nexus 6  Original Android Development] SteveYoungs:
This version won't boot for me on LOS 15.1. It gets to the boot animation and no further. Is this a known issue or is there maybe something screwy with my device / set up? (IOW, anyone else seeing this on LOS?)

I don't suppose there's a way to display kernel messages instead of a boot animation so I could get a clue as to where it is stopping?
[Nexus 6  Original Android Development] LunaticSerenade:
I'm hoping it works with today's build, since the kernel is April patches and last week's LOS wasn't.

I could also be desperately grasping at straws, who knows.
[Nexus 6  Original Android Development] SteveYoungs:
I guess it is possible although that scenario never caused any issues for me with EX 4.x. I share your hopes. :)
[Nexus 6  Original Android Development] Elektroschmock:
Really? I don't see any ASB-2018-04-01 changes.
[Nexus 6  Original Android Development] LunaticSerenade:
Looks like it's not booting with the 4.12 LOS 15.1 build. :(

Just sits at the splash screen.
[Nexus 6  Original Android Development] manish_bhaumik:
I have the same experience with this and the Pure Z kernel (stuck at splash). Still looking for a Kernel which works over LOS 15.1. Trying to get over the sluggish CPU performance (cores going offline) on low battery.
[Nexus 6  Original Android Development] SteveYoungs:
5.18 + LOS 15.1 = Nope :(
[Nexus 6  Original Android Development] magnamentis:
as we know this kernel does not work with LOS and LOS based rom and i think there is no need to repeat this for each rom and on each page separately. once someone has this kernel running on a rom where it didn't boot before is the right time to post again on the matter.
[Nexus 6  Original Android Development] SteveYoungs:
You're right. I'm sorry.
[Nexus 6  Original Android Development] :
well i dont know if you meant this concerning specifically nexus 6, but on nexus 5 the newest ex kernel works just fine with LOS 15.1 so im still hoping it's gonna become true for nexus 6 as well and appreciate and consider SteveYoungs attempts to run it each time there is an update helpful :)
[Nexus 6  Original Android Development] magnamentis:
my post has nothing to do wiith any specific rom, device or anything hardware and software. it's generally about proper communication, about what we find in a thread when coming back and go to last unread and each time see the same. this applies to any kind of communication, it's called "till further notice" means it's as it is as long as nothing has changed and hence it does not have to be repeated frequently while a statement of the "status quo" is totally ok.

there is also no given or stict limit. what do one call a heavy rain or a flood, it's relative but the moment the water will fill your cellar and get to your neck you certainly know that it's a flood, no matter where each individual would set his own limit :)

what interests me much more is whether it will be possible for [MENTION=4684315]flar2[/MENTION] to make a kernel that is compatible with the vast majority of the currently available custom roms that are based on LOS 15.1 ?

as it seems there is not much to adapt and we've been there already in the past. even though i think that like CM at that time LOS should not divert non-necessarily from the norms but then if no side gives in we're somehow cornered with no or very limited kernel choice which ultimately cannot be in developers interest as well. user-base is finally key to new app-sales and building/keeping a certain standing.

of course this only is a valid point of view if the effort is as small as it currently looks to us laymen ;) ;) sorry if that proves to be an illusion :highfive:
[Nexus 6  Original Android Development] Elektroschmock:
We're not breaking compatibility intentionally. We're just going forward in development.
[Nexus 6  Original Android Development] magnamentis:
if you mean bad intention with intentionally i say sorry if it sounded that way. of course everyone has his reasons for doing things in a certain way.

that said and looking at the ever more difficult and longar lasting rom development and the ever reduced number of available and even less good custom roms, it's somehow necessary that developers start to interact instead of each doing his thing "lonely wulf" like.

further and just in case language barrier kept me from submitting my message correctly, my heading was towards kernel devs to adopt a bit where necessary because there are dozens of devices running custom roms that are based on LOS 15.1 and AOSP based roms for devices that are out of google's support window get less and less. this makes me think that to join forces by talking to each other and adopting/adapting the remaining custom approaches will sooner or later become a must, else this community will die away even faster as it already does.

may i remind some about jelly bean times LOL

ever since things got more difficult and hence joining efforts becomes more important. i remember times when my nexus devices could be run on 5-10 custom roms within 2-3 days after the releas of factory images and other devices were able to join suit. nowadays it takes month to adapt to new API versions and then when we finally get there compatibility lacks to to a hand full of commits.

this does not judge who is right or wrong, it's basically a pledge to better fine tune the scene for best compatibility. not even a complaint, just brainstorming, my devices are all running well and there is no reason to jump very high but then i admit that i miss this kernel on my nexus 6,

reason is not cosmetic, since oreo i face random reboots which i know this kernel would help me avoid them.

again i want to stress that no offense, demand or complaint is meant here, just thinking that the future will be a bit less individual than it was when the choice of quality roms and kernels was huge.

nice weekend [MENTION=535343]all[/MENTION] users

EDIT: check this link and it's clear what i mean, very few commits to get in sync really: https://xdaforums.com/showpost.php?p=76227688&postcount=828
[Nexus 6  Original Android Development] L.F.B.:
I was ready to flash the new LOS 15.1 for shamu...

bummer... EX kernnel not work...

So Ill stay with my PN 7.1... it is very hard to find a good Oreo rom and EX kernnel to make a double...?
[Nexus 6  Original Android Development] rfactor117:
Nitrogen OS is right for you, it's rock solid and totally EX Kernel compatible.
[Nexus 6  Original Android Development] cujo6801:
AOSiP.....

EX Kernel built in...

No random reboots...

Netflix work out the gate...(W/Magisk)

And nice options..

Sent from the "DOG" pound
[Nexus 6  Original Android Development] mingaldrichgan:
No Always-On Ambient Display, though. :(
[Nexus 6  Original Android Development] FReaX908:
Sorry for off topic....

But may I ask you if you're using aosip? Would you check if long pressing for torch while screen off is working? Thank you :cool:
[Nexus 6  Original Android Development] giannis_mathiou:
Works great for me at least [emoji39].. I'm also in latest AOSiP with latest EX
[Nexus 6  Original Android Development] billteeth:
Have you found anything that works?
[Nexus 6  Original Android Development] NLBeev:
Did you leave Beltz?
[Nexus 6  Original Android Development] giannis_mathiou:
Oreo made me flashaholic [emoji39]... Currently I'm back to Beltz. Beltz and AOSiP are the two ROMs that work for me the best...
[Nexus 6  Original Android Development] NLBeev:
I read that AOSiP is no longer supported for Shamu. So no may security patches.
[Nexus 6  Original Android Development] Topaz8:
Lineage OS 15.1?

:confused::cowboy:

Please, can I flash this on LOS 15.1?
[Nexus 6  Original Android Development] Berlino:
The answer is on previous page: https://xdaforums.com/showpost.php?p=76221936&postcount=8334
[Nexus 6  Original Android Development] Sanabil:
I use to run my processor at 2.9ghz using ex manager on custom flashed ex kernal. But i am not able to do it in nitrogen rom 8.1. Is there a way to do it?

The rom has baked in ex kernal but it shows max frequency at 2.6ghz .

Can i flash ex kernal manually via twrp and adjust clock speed using intial setup? I once tried but it won't boot.

Any clue?
[Nexus 6  Original Android Development] flar2:
The kwrnel might have diverged if it's built-in to the ROM. You can try flashing it, just do a backup first.
[Nexus 6  Original Android Development] :
Camcory is running the show now. Just had a build yesterday and it was amazing.
[Nexus 6  Original Android Development] mingaldrichgan:
Any thoughts comparing it to Screw'd? ? These are my top two choices at the moment, but I only tried the 4/9 build of AOSiP.
[Nexus 6  Original Android Development] :
It's stable and amazing. Love his work, But screwd has more customizable features. Same kernels.
[Nexus 6  Original Android Development] NLBeev:
Because the kernels are the same it could be possible to switch to Screwd with a dirty flash.
[Nexus 6  Original Android Development] Sanabil:
Bro I tried flashing the kernel I set everything according to my liking and when setup was finished it is stuck on Google logo screen.

What do you think is conflicting? I really want it to be at 2.9ghz ?
[Nexus 6  Original Android Development] :
I wouldn't recommend it. Screwd is built for performance and features. Conflicting system files would happen and impede those things. Clean flash.
[Nexus 6  Original Android Development] pinkfloyd3:
Im noob as u know noob ask noob question :D

Why we have 3.x instead of 4.x ?

Sorry for my bad English
[Nexus 6  Original Android Development] king:
Because nexus 6 came with 3.10.x,the max we could get was 3.10.108(which we currently have now) 4.x is not there because google never made this version for nexus 6.
[Nexus 6  Original Android Development] pinkfloyd3:
ohhh ok thanks mate :)