yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] MarceloSiciliano:
Xileforce it would be cool if when i download a new version of the kernel using the app it came with a changelog
[Nexus 6 Android Development] Xileforce:
Yup we were talking about a way of doing this. Not sure when it will be implemented I'll bug jamcswain :)
[Nexus 6 Android Development] MarceloSiciliano:
When the kernel is downloaded a text file was downloaded together
[Nexus 6 Android Development] Xileforce:
I believe that text file just contains the name of the latest build so it knows what to download. But I would guess we could have it read a text file like that
[Nexus 6 Android Development] Xileforce:
Well played sir lol
[Nexus 6 Android Development] Megaflop666:
I was stating that it did work.
[Nexus 6 Android Development] USA-RedDragon:
Yessir. It's to cross reference what you have downloaded/running with what's on the server
[Nexus 6 Android Development] stevepick2:
Yeah, none of the betas have worked on Chroma since T7
[Nexus 6 Android Development] angiest:
Chroma is not CM based.
[Nexus 6 Android Development] Xileforce:
It doesn't necessarily need to be cm based. Just incorporate some of the cm12.1 ramdisk changes. For instance theme manager is a cm thing which required aosp ROMs to merge some cm ramdisk changes in order to work.
[Nexus 6 Android Development] angiest:
I think there are almost no CM pieces in Chroma. But there have been some recent ramdisk changes.
[Nexus 6 Android Development] wrongway213:
Which kernel were you using? I tried the T7 test build of 2.1 and it would not boot for me on latest Temasek CM12.1 - waited a solid fifteen minutes and decided the amount of heat coming from my phone could only mean bootloop time, lol.
[Nexus 6 Android Development] jiv101:
https://drive.google.com/folderview?id=0B0B7GGyONhT2c2JkZ2xJSUlxRFk

I've been having reboots today
[Nexus 6 Android Development] Xileforce:
Next test should fix reboots. I talked with bbedward about it.,
[Nexus 6 Android Development] sparksco:
arm-eabi-6.0 is on gitlab
[Nexus 6 Android Development] Xileforce:
That's a real thing???
[Nexus 6 Android Development] sparksco:
Yup lol

https://github.com/SaberMod/GCC_SaberMod/commit/2d444913351f6386df286eef76e5b67e56fecf74

Took me by surprise. I caught it about 15 minutes after they pushed it.
[Nexus 6 Android Development] Xileforce:
Lol just pushed a build with it on pushbullet and through the app. Seems very smooth. Although I'm guessing ATM, there's not much change yet because its merely a branch of GCC 5 that's only got like one day of development difference?
[Nexus 6 Android Development] Steady Hawkin:
Gotta give it up to you, the last two test builds have been idling like a dump truck on a warm summers eve. Battery life and performance are outstanding, and I've yet to encounter any issues at all. Push bullet support has also been great. Keep up the good work, excited to watch this evolve!
[Nexus 6 Android Development] sparksco:
Yeah not much difference. I'm sure they added specific changes for gcc6 although I'm not sure what exactly. I'll check more later on the commits when I get home.

You may want to branch off of both gcc5 and gcc6 for testing to see which one is better.
[Nexus 6 Android Development] Xileforce:
I had to add a compiler-gcc6.h file BTW. I just used the gcc5 one but renamed it and it compiled fine and runs very well.
[Nexus 6 Android Development] sparksco:
Yeah I did the same thing.
[Nexus 6 Android Development] Megaflop666:
I'm on the latest vindicator build on 4-13 temasek cm12.1. Everything works great and is smooth as silk. One problem, after I reboot the phone and open synapse, it displays a parsing issue, JROC or something like that. If I uninstall synapse and reinstall it, everything works perfectly until the next reboot and then I have to start it over again. Any thoughts?
[Nexus 6 Android Development] Xileforce:
That's awesome man! And bbedward has some cool stuff coming down the pipe to make bfs even more awesome. I'm actually running with conservative governor ATM and its still smooth! A word of warning I noticed though. If you mess with simple GPU governor be careful. It can cause lag by not letting the GPU ramp up to the needed frequency. I noticed I had some lag when pulling down my status bar in a certain app. Turns out it wasn't going above 110mhz. Just needs to be adjusted properly but if u hit issues I suggest rolling with normal msm adreno tz. If you really want performance simple on demand is a nice choice but expect higher battery drain. I've found it favors the upper frequencies a lot.
[Nexus 6 Android Development] Xileforce:
Synapse is just a weird app. I've had that issues on occasion. Usually it only happens to me when I try to open it right after boot very quickly. To fix it I just force close it.
[Nexus 6 Android Development] Megaflop666:
Ya I know it's a weird app. Actually hate it's bugginess. I'll try your solution next time.
[Nexus 6 Android Development] oOflyeyesOo:
I am excited with all the changes that seem to be happening. I am waiting to switch to bliss once a stable build comes out that runs good on CM12.1 based ROMS.
[Nexus 6 Android Development] cjharris1985:
Question, do you have to disable encrypt before flashing this or can you do it with this Kernel? Thanks!
[Nexus 6 Android Development] jackpollard:
If your encrypted, you will still be encrypted. If your un-encrypted, you will still be un-encrypted. You have to go thru "the process" to un-encrypt if you want that. http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
[Nexus 6 Android Development] Xileforce:
This will leave u encrypted if u are encrypted or it will leave u unencrypted if u are unencrypted. However, you should be able to use the kernel to become unencrypted. To do this backup everything to a PC, then you would go into twrp, flash the kernel, and then I believe you would format the data folder. Not wipe, format. If u just wipe it won't work. Make sure u flash the kernel first!! If u don't its gonna wipe ur data which means wherever you have the kernel stored is gone too. I haven't done it since the day I bought my phone though so you may want to double check my steps lol.
[Nexus 6 Android Development] Xileforce:
One of the people in our testers chat who's working with the bliss guys says they r reverting their ramdisk changes so the kernel may once again be usable on it.
[Nexus 6 Android Development] stevepick2:
Decided to look for a new ROM since the new beta is having compatibly issues. Came across a new ROM called AOSIP. Seems to be devoploping really quickly and is 100% stable. Even though it came out on the 6th. Already has a large and friendly Google Plus community of 301 members.

Great job with these updates. Everything running smoothly
[Nexus 6 Android Development] jackpollard:
You learn something new everyday! I had no idea you could un-encrypt except by following the process outlined in http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715. Very cool.
[Nexus 6 Android Development] Xileforce:
Yup all the boot IMG does is change a file in the ramdisk AFAIK which is what tells the phone to encrypt or not. Same as any kernel. Just gotta format that userdata :)
[Nexus 6 Android Development] angiest:
FWIW, I'm using Device Control from NamelessROM.
[Nexus 6 Android Development] lainemac:
Is this kernel using BFS like zen?
[Nexus 6 Android Development] tdamocles:
Are you talking 2.0sm5 vindicator?. I can't get it to boot on the latest temasek.
[Nexus 6 Android Development] Xileforce:
The stable build is not. The test builds are though. The current version is lean kernel based. The tests are based on zen. Hope that helps. You can grab the test builds from either the ota app on the OP or through the push bullet. Both are at the top of the op.
[Nexus 6 Android Development] Megaflop666:
Yup. That one. Vindicator2.0sm5.zip
[Nexus 6 Android Development] tdamocles:
Are you on the temasek 4/13 ? because your screenshot shows 4/08 build.
[Nexus 6 Android Development] Megaflop666:
Oops. Old screenshot.

Here...
[Nexus 6 Android Development] tdamocles:
What are the steps that you took to get it to work on temasek? I really want to get it working for me.
[Nexus 6 Android Development] Megaflop666:
Nothing unusual. I already has 4-8 installed obliviously. I dirty flashed latest build. Flashed Minimal gapps for 5.1, and flashed vindicator, and rebooted. Took 10 or 15 minutes for first boot.
[Nexus 6 Android Development] tdamocles:
Maybe that's it... I haven't waited that long yet. I'll try again.
[Nexus 6 Android Development] sparksco:
Wow that's a long time to boot. You must have a lot of apps installed.
[Nexus 6 Android Development] stevepick2:
Latest beta works with a clean flash of Chroma
[Nexus 6 Android Development] Xileforce:
Running fine here on latest euphoria ninja build. Took like 5 mins to get past boot animation. Maybe longer then optimized all my apps and I was good to go. Dirty flash BTW. Just flashed euphoria, kernel and su
[Nexus 6 Android Development] Megaflop666:
No, Not a lot of apps. first boot just took a bit.
[Nexus 6 Android Development] stevepick2:
Already looking amazing! Running extremely cool too
[Nexus 6 Android Development] wrongway213:
DId you happen to flash Hydra kernel first? I can't get it working either, but if you flashed Hydra before trying Vindicator I think I understand how it is working for ya.. if not I am clueless. I waited until my phone felt like it was gonna explode it was so hot lol
[Nexus 6 Android Development] Megaflop666:
No, had vindicator running on the 4-8 build and it had all been from a clean install of temasek and vindicator. Dirty flashed the latest 4-13 (theres a 4-14 now), and reflashed vindicator. Idk if it makes any difference but I use minimal gapps 5.1 from here and my phone is also running multirom. I don't know how either of those variables could matter but I'm throwing them out there. After flashing, I wiped dalvik and cache.

I seem to be having very good luck where others do not. First with lean kernel and now with this kernel...
[Nexus 6 Android Development] wrongway213:
Well, I am at a loss. Obviously based on the screenshots no on can dispute it's working for you, I'm using minimal GAPPS and MultiROM myself.. Banks minimal GAPPS but still.. I just don't understand. Lucky you I suppose? Haha
[Nexus 6 Android Development] Megaflop666:
Idk. Guess I got the magic phone from tmo...

It is my 5th nexus 6 since they kept sending me defective factory refurbs. I had to finally file with the BBB to get a brand new unopened, working nexus 6 since that's why I'd paid for. Knock on wood, everything has been perfect since I got this one a couple weeks ago.

Did you get vindicator to work on the 4-8 build? That was my initial setup and then it was just dirty flashing after that. One very goofy thing I recall after dirty flashing to yesterday's build with this kernel, it sat at the Google splash screen for about a good 3 minutes before booting into multirom. Hasn't done it since, but it was weird
[Nexus 6 Android Development] wrongway213:
I couldn't get it to set up on 4/8 build. I like to think I can recognize the difference between a slow initial bootup and a bootloop type situation - my phone was hotter than it ever has been on the charger after about fifteen minutes of trying to boot. I did see the super slow bootup setting up with Hydra kernel, but never could get Vindi working.
[Nexus 6 Android Development] Megaflop666:
I'll be damned, idk then. I'll be flashing the latest build here shortly after this boring meeting
[Nexus 6 Android Development] Xileforce:
I have no idea why it would work for one person and not another lol.
[Nexus 6 Android Development] Megaflop666:
I'm still going through everything in my head to make sure I didn't have something else I did that I'm forgetting... but the pictorial proof is here in the thread that it is working for me.
[Nexus 6 Android Development] Xileforce:
Pictorial....I like it. Imma have to start using that word now.
[Nexus 6 Android Development] wrongway213:
You know? It'd be one thing if I was the only user who couldn't get it working or if I was new... but I'm inclined to think that the hundreds of flashes I've put this phone through already should be no different than this. MultiROM is new, but it has no issues with Unicornblood or Hydra and the issue I'm facing is not a kexec issue, but a failure to boot at all. I'd really be curious to hear some more trial/error... cuz this is just seemingly illogical (and to be honest I follow this thread and finally feel like this kernel is in a place where I want to run it through the gauntlet)
[Nexus 6 Android Development] Xileforce:
Yea and its an issue where we can't get logs to help see :/ I've seen the weirdest issues on this phone... Like right now I've got one guy who is running the same ROM as me but he bootloops when he flashes the test kernel. And he's a bin 7 while I'm a 5...makes no sense. Oh well. Hopefully we can figure out something. I'll try merging in the latest Hydra ramdisk changes. Maybe that will fix it. Also got some cool stuff from bbedward for bfs that I wanna merge when I get home. Should be faster and more battery efficient
[Nexus 6 Android Development] wrongway213:
Well now you're just being a tease with that bfs stuff since I can't even get the kernel to boot :p Seriously though, I appreciate you trying to look into the issue, especially given we literally cannot produce logs to even help you see what the problem is - obviously this puts any developer at a serious disadvantage when trying to solve an issue. I personally am just thankful you are still going to take the time to attempt to blindly fix it... some users may not be aware how much more (exponentially more) time a single problem can take to solve without a log, but there are those of us who are aware - we are just grateful you're trying to work with CM changes instead of limiting the kernel to AOSP and stock(gasp) users. Take your time - I'm sure when it's booting for people other than [MENTION=5867243]Megaflop666[/MENTION], (who I really hope doesn't mind helping me pick out my lottery numbers this week :p) it'll be awesome - reviews indicate it is anyway. I already know I loved he crazy features of this kernel.. just been waiting for the stability to catch up and it sounds like on 2.0 it finally has. I'll be waiting/watching.
[Nexus 6 Android Development] Megaflop666:
What's so interesting about that word? Lol. Simply refers to the pictures I posted as proof earlier on the thread.

---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------

Have you hooked it to your computer to pull a log through adb during boot?

07 12 23 36 44 09

(is that enough numbers? )

---------- Post added at 04:47 PM ---------- Previous post was at 04:17 PM ----------

@wrongway213 - latest build is working with this kernel as well...if you want to try again.
[Nexus 6 Android Development] stevepick2:
Not able to flash RB28. Makes recovery reboot
[Nexus 6 Android Development] BrianTX:
RB28 working fine on chroma.
[Nexus 6 Android Development] Xileforce:
Awesome! Did RB26 work too?
[Nexus 6 Android Development] Xileforce:
Done! Added you :)
[Nexus 6 Android Development] taranfx:
My phone rebooted every few minutes. Not sure if it was 98mhz min setting or what.

Went back to Franco
[Nexus 6 Android Development] Xileforce:
I could've used a log :/ something was definitely severely wrong. Hard to say what though. Nobody else has reported an issue of that severity. There is one reboot bug that should be fixed in the coming update related to 98mhz though.
[Nexus 6 Android Development] clnzx2:
I would love to help, kyle.a.morris@gmail.com
[Nexus 6 Android Development] Xileforce:
Added ya! Welcome to the club!
[Nexus 6 Android Development] Swamphound:
I had a reboot last night and for a time my Fauxclock app would only say "kernel not supported.". When I woke up it seems to be fine. I hope these logs are helpful and please let me know if I don't submit them properly.https://www.dropbox.com/sh/32cftge8ihgn27p/AADXmW6pNz6rwIofQodTVtMEa?dl=0
[Nexus 6 Android Development] papikev:
Can you add me to the kool kids club.... K.Malesic.71@gmail.com :)
[Nexus 6 Android Development] Mistertac:
I added you my friend.
[Nexus 6 Android Development] Xileforce:
Added you thanks for joining us! OK guys that's probably all I need for noe. I'll b sure and let you knownif we are going to take more.
[Nexus 6 Android Development] zenxaero:
Dang it if only I didn't have to be at school ?
[Nexus 6 Android Development] Xileforce:
Lol if u want to be a beta tester...I'll let u be the last one.
[Nexus 6 Android Development] cdub50:
Had a kernel panic posted log to hastebin link below. Not much in the log for the kernel panic, but hope it helps.

hastebin.com/emapaqidoz.xml
[Nexus 6 Android Development] Xileforce:
Thanks! The beta testers have been reporting that same one. I'm going to let them testba new build that I'm hoping will fix it. If all goes well I'll release here :)
[Nexus 6 Android Development] cdub50:
Sweet if you need any more testers let me know. Would be willing to try out the new build.

Thanks again for your kernel has all of the features I am looking for with minimal cruft.
[Nexus 6 Android Development] Xileforce:
Lol I guess I can accept one more. Just post ur hangouts or message me it and I'll add u
[Nexus 6 Android Development] cdub50:
Sent you a pm with my email.
[Nexus 6 Android Development] zenxaero:
Thank you so much!! zenxaero@gmail.com ?
[Nexus 6 Android Development] Mistertac:
So ahhh... Everyone is just chilling in Hangouts now... No need for a thread?!?

[emoji43]
[Nexus 6 Android Development] Xileforce:
Added you! Welcome to the group!
[Nexus 6 Android Development] stevepick2:
I'm on Chroma too, but not able to flash. Could it be because I'm using the multirom recovery?
[Nexus 6 Android Development] BrianTX:
Yes, 26 worked also. Only had a couple reboots, but I'm running -65 mV so that's probably the reason. Battery life is incredible BTW!
[Nexus 6 Android Development] Xileforce:
Likely a bad download. I have the multirom recovery too
[Nexus 6 Android Development] Xileforce:
Wow -65! If I was a betting man, I'd say that's where your issue lies xD
[Nexus 6 Android Development] stevepick2:
Probably.... Finished downloading in about 2 seconds

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

Is it me or has google been removing tweaking apps from the play store? My faviritie app was recently removed, but luckily I was able to get an apk
[Nexus 6 Android Development] Xileforce:
Well it is only like 6mbs :P someone in the beta thread said google is cleansing the play store ATM for some reason. Idk why I wasn't really paying attention.
[Nexus 6 Android Development] jackpollard:
RB28 flashed smooth and is humming on Benzo.
[Nexus 6 Android Development] wrongway213:
Anything that touches SELinux is now violating ever-changing policy. Here you go, this is the info about it http://xdaforums.com/marketing-analytics/app-stores/apps-modify-selinux-forbidden-google-t3068805 SELinux Mode Changer got removed, Kernel Adiutor had to remove its SELinux toggle - Synapse should be safe according to apb_axel as the SELinux toggle is not part of Synapse, but UKM, which is obviously not on the Play Store. According to ak all of that falls under GPL so Synapse should have no worries I hope. Last page of the UKM thread if you're interested in that conversation
[Nexus 6 Android Development] Xileforce:
Wow thanks for clarifying. U must be omniscient or something lol. I've been defaulting to permissive for the bast few builds because I noticed hydra does that and I think it likely reduces the problems people will run into. I'm still indecisive on the issue tho :/
[Nexus 6 Android Development] Megaflop666:
Latest 2.1rb28 your app said to download is up and running great on temasek cm12.1

Looks like you slimmed down the synapse controls...
[Nexus 6 Android Development] wrongway213:
Lmao @ omniscient haha naw man, I jus love Android like you probably do, but I know I can't do what you do because my mind doesn't work that way. I'm a speed reader though (not an expession, it's an actual thing some people can do with training but I taught myself because I'm werid), so I read a lot of threads and respond to tons of posts as my way of getting "involved". I never took the plunge to learn to dev because I know my math skills are awful - I can't do algorithms and I'm pretty sure you need to have a basic understanding of those to do any real programming, so I never even gave it a shot. Me being everywhere is how I get involved since I'm not a mod or a dev or anything like that - I just post lots and try to have useful stuff like links or info when I do lol.

As for your decision, I honestly don't think Hydra has defaulted to enforcing for a long time now. It's been a while since I've "clean flashed" a Hydra kernel so I might be wrong but I thought neo changed that like, I dunno when but I'd say over a month ago I thought it was changed - if not that's when it was basically said that there's no need for permissive with SEPolicy being nice to V4A and Xposed working around ART restricions. The implementation in Hydra was for Xposed - it implemented permissive boot as opposed to permissive once Synapse was given root to sum it up. I believe the kernel defaults to enforcing now but I could be wrong on that I suppose - I know the way it's set up is meant to run in enforcing though.
[Nexus 6 Android Development] Xileforce:
Yup its because the test builds are from the rebase which is basically started from scratch on zen kernel. So I've been slowly re adding vital features. It should give better battery and performance but may be unstable. Im about to push RB29 with a few fixes. RB28 may have had a few crash issues.
[Nexus 6 Android Development] Megaflop666:
No crashes a/o yet. I'll for rb29. Thanks for all the great work
[Nexus 6 Android Development] sparksco:
[MENTION=4517211]Xileforce[/MENTION] apparently there's a new graphite flag in newer gcc versions.

-floop-unroll-and-jam

https://gitlab.com/SaberMod/android...mmit/19c0d89323ed7486c46de1903539aabae50dcec7
[Nexus 6 Android Development] Xileforce:
You I was looking at that like a month ago. I can't recall if I tried it. Regardless. I can't use graphite with sabermod ATM :(
[Nexus 6 Android Development] sparksco:
You can't use it at all even with pthreads disabled? If you can't use both you could test which one is better? You could add -fno to the files that have internal compiler errors the same way you do with strict but turn off every graphite flag for those files like I did in that commit I linked in my last post...
[Nexus 6 Android Development] Xileforce:
I never thought of that. I guess I could try disaing it on mm. Disabling pthreads doesn't fix it. I also beencrwadig and people seem to be conflicted on floop-parallelize-all apparently it doesn't actually check whether or not its beneficial to parallelize a loop which can actually deteriorate performance for the majority of loops. But idk enough of about it. Have u heard anything about that?
[Nexus 6 Android Development] sparksco:
A little but I never understood why people thought that... Maybe in older gcc versions but I doubt gnu would leave it broken.
[Nexus 6 Android Development] Xileforce:
Just read this https://gcc.gnu.org/wiki/AutoParInGCC looks like adding -ftree-parallelize-loops=4 is required to actually use the parellization of loops. I also tried disabling graphite on the erroring module with no luck :(
[Nexus 6 Android Development] sparksco:
I just tried building your kernel but you never included patches for gcc5 or gcc6 compilers... Any reason you never committed those changes?
[Nexus 6 Android Development] Xileforce:
The current repo I'm using now is Vindicator Rebase. And gcc5 is included with Linux 3.10.59 as I recall. As for gcc6 I added that myself and its in the new repo ;)
[Nexus 6 Android Development] sparksco:
Ah, well I sent you a pull request, graphite works fine for me... If you want I can send you the kernel binary.
[Nexus 6 Android Development] Xileforce:
How does adding the flags to cc work?