yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Poojan Patel:
Encountered a bug on this kernel.

phone freezes and reboots on selecting simple_ondemand governor for gpu.(checked twice)

build kernel r4.5

Rom: Cataclysm rom
[Nexus 6 Android Development] chairshot215:
Congrats on finding the super secret Easter Egg!!

Actually after reading your post was able to reproduce fairly easily. I compiled and flashed a pure AOSP kernel without any changes made to the code and it also did not work so looks like the AOSP Kernel just does not like that configuration for some reason. Figured out why and am about to post a fix as 4.5.1.

https://github.com/Starship-Android...mmit/2a908df12511c7e88d4166e4ed50eeb39d3add3c
[Nexus 6 Android Development] chairshot215:
The above mentioned issue has been addressed and the fix has been posted to allow simple_ondemand to be set as a gpu governor without causing a reboot. Thanks to Flar2 for the find by as doing so is broken in the AOSP kernel source. Also thanks to yellowman82 for pointing out that the configuration caused an issue. Otherwise did a bit of stability testing before posting and all looks good. Have not updated the date name for the OP as this update addresses only one very minor bug for a configuration that has been downloaded now a few hundred times and has not caused any previously known issues so can actually skip the update unless you plan on setting simple_ondemand as the gpu governor as this is the only difference between 5.1 & 5.1.1 and that’s it.
[Nexus 6 Android Development] mp3geek:
Couldn't get this kernel to boot, using f2fs. Using Chroma/Benzo without issue.
[Nexus 6 Android Development] crashercarlton:
I was just curious if this is just another warp 9 kernel or if it actually breaks the warp 10 barrier...:p:p
[Nexus 6 Android Development] chairshot215:
I'm not sure breaking warp 10 definitely one of the worst Voyager episodes and there is a lot of those.
[Nexus 6 Android Development] chairshot215:
I am aware of the Chroma Rom and the Benzo Kernel but am a bit confused about Chroma/Benzo, Is this a different Rom or variant?
[Nexus 6 Android Development] mp3geek:
Using the Chroma Rom + Benzo Kernel is fine, but using Chroma Rom + Starship Kernel fails to boot for me.
[Nexus 6 Android Development] chairshot215:
Release 5.0 mainly adds some power saving opportunities.

I have not put much time into investigating the issue reported by mp3geek booting into Chroma using f2fs. Outside of stock and pure AOSP builds would go crazy testing every feature with every Rom. I do have a few ideas though and have otherwise heard a decent amount of good things using Starship and Chroma together that it may be worth looking more into assuming I can reproduce. Would be very helpful if could give me a few details like what method was used for booting into f2fs or if Benzo had been installed first before starship. I have not dug much further than a few things as have been trying to focus on the Starship Rom.
[Nexus 6 Android Development] chairshot215:
I have merged all the 6.0.1 mr1 changes into the Starship Kernel and released under version 6.0 in the OP.

Yesterday I had included in this post an issue I was experiencing with TWRP reverting back to stock after using fastboot to flash the 6.0.1 factory images. At the time I found that before flashing TWRP if I had used fastboot to flash the full Starship boot.img TWRP did not revert. I again tried to create the issue today but used an older version of TWRP, 2.8.5.0 instead of 2.8.7.1 and had no issue with TWRP reverting back with the Stock boot.img extracted from the 6.0.1 factory image. Anyhow just thought I would share.
[Nexus 6 Android Development] chairshot215:
Nothing Huge for 6.02. With previous release just wanted to add changes made in the 6.0.1 code to insure there would be an option for those at the time had updated from 6.0 to 6.0.1. Kernel. The kernel version has been updated to 3.10.94 from 3.10.93. Added a few PM commits that should show a small difference in performance. Otherwise added a few things to remove compile errors and log error spam.
[Nexus 6 Android Development] chairshot215:
For the new year decided to test out a few Toolchains for release number 7.0. The posted version is using Linaro 4.9 but also testing Hyper-toolchains Hybrid SaberMod and Linaro Optimized Toolchain so will find a link below if would like to try 7.0 using the Hyper-toolchain Hybrid. If happen to try both and have an opinion on the better of the two let me know. Is late but also may post the OG Google toolchain build as well. Otherwise let me know what you think???

Linaro 4.9 toolchain

https://www.androidfilehost.com/?fid=24352994023705095

Hyper-toolchain Hybrid Build

https://www.androidfilehost.com/?fid=24352994023705101
[Nexus 6 Android Development] ancidroide:
Tested the ione compiled with hyper-toolchain and I can say that is very smooth... Keep your good job ;)
[Nexus 6 Android Development] chairshot215:
OK so the 7.0.5 build had intended on being an 8.0 release but at the last minute broke the build so posted 7.0.5 that contained most of what I was testing with 8,0.

With tool chain testing have found so far Linaro in my experience the best all around but still not conclusive so I am again posting the hyperMod build along with just a pure SaberMod build for testing 8.0.

Linaro-4.9-Toolchain

https://www.androidfilehost.com/?fid=24352994023708464

Hyper-Toolchain Hybrid SaberMod and Linaro

https://www.androidfilehost.com/?fid=24352994023708488

SaberMod-Toolchain

https://www.androidfilehost.com/?fid=24352994023708487
[Nexus 6 Android Development] NolenUmar:
Thank you!! :D
[Nexus 6 Android Development] chairshot215:
Thanks have started updating the Op as at this point the Starship Kernel for Shamu is well beyond just sprucing up the Stock / ASOP Kernel for a few friends and family. Going to also start doing my best to update the feature list with each update. Once again starting up the Rom as had just about finished up the Frameworks overlay images when not paying attention installed Ubuntu on the still plugged in USB external instead of my new SSD. So learned my lesson about not committing on the regular. Doing as much as I can using overlays in a Starship common device directory so can easily port over to just about any device with a working AOSP Port mainly by adding the common directory path into the device files.

Anyhow finding that if I download the Source on the insanely large USB drive and setting the new SSD as the output directory using .ccache on the SSD also builds are finishing in just under an hour. Is about what I had expected just using the SSD for everything. So one nice surprise came out of my débâcle. Not much but Ill take it, saving lots of space and can now use the drive for a few other things as figured it would be an Android project only drive.
[Nexus 6 Android Development] ztotherad:
just because if i read this right, you're creating a starship rom for shamu now? definitely can't wait to try it out if that's the case.
[Nexus 6 Android Development] chairshot215:
Yup:fingers-crossed: Rom is in development
[Nexus 6 Android Development] ztotherad:
can't wait!
[Nexus 6 Android Development] B@RRY78:
Great kernel only mis multirom patch
[Nexus 6 Android Development] S0UTHPAWK1LLA:
I hope this kernel catches on. It's solid. Thank you for putting it together.
[Nexus 6 Android Development] chairshot215:
One of these days will look into it. Honestly have just never used it so will need to take a look.

Otherwise have started posting CM-13.0 specific versions of the Starship Kernel in the OP. Testing has been limited and have not yet added all the features used in the Stock/AOSP releases as of yet but have flashed with the last few nightly releases and self compiled versions of CM-13 and so far have gone through a run-down of tests and everything is looking good.
[Nexus 6 Android Development] chairshot215:
Took down the CM link as experienced data black outs for LTE after wandering around beyond home and work. Will probably be back up soon. May be my restored backup as not having issues after flashing the Rom again.

I put the same link back up again for the CM Kernel. Not sure but after reinstalling CM I can not reproduce any data drops. Only after restoring a backup I made at work.. Looks like a better chance the issue was either caused by a bad backup or a not so stable nightly than it would the kernel. Is otherwise late so will look more into it tomorrow but as of now have not seen the issue since flashing the 01/26 nightly I had in storage.

Anyhow did some reading and looks to be a CM bug. Read a few articles about LTE not starting up after reboots and restores and required a one time airplane mode toggle to fix the issue after reboots. Performed a test and restored my backup from last night. Experienced the same issue loosing LTE so toggled airplane once as was described in my reading and all has been well with the backup since. Forgot how much jumping the gun on these things suck thinking you may have broke somthing then learning you haven’t but still testing things to be sure.
[Nexus 6 Android Development] chairshot215:
Updated Stock / AOSP Kernel as 8.7. https://github.com/Chairshot215/starship_kernel_moto_shamu/commits/M

Includes a decent amount of net, wireless improvements.

Bumps up BFQ IO Scheduler from version 7r7 to 7r8.

Linux Version also takes a bump from 3.10.94 to 3.10.95. Version 3.10.96 is listed but rather large

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.10.y

So will probably not have a chance until next time around so will see how it plays out.
[Nexus 6 Android Development] razrlover:
Awesome gonna check this one out again. Thanks
[Nexus 6 Android Development] chairshot215:
Difference between 8.7 & 8.7.5 is really that 8.7.5 includes Linux 3.10.96
[Nexus 6 Android Development] chairshot215:
Well the Valentines Day special edition names would definitely serve me up for a good old High School ars whooping. Otherwise cementing what is probably already known, I’m a Dork. Greek or Nerd will unfortunately not due in this case but Dork about sums it up as the others usually imply some sort of intelligence. If have no idea what I am talking about please move below there is nothing worth reading here.

OK so on first try with the CM version used a nightly maybe 2 or 3 back and had an issue with Play Music stating not enough space available when selecting a song for streaming. Songs I had in storage mostly the few purchased through Amazon had no problems nor did any other type of streaming service I tested just Play Music. Anyhow before looking at anything I did a clean wipe and flashed the 2/14 nightly, checked upstream for anything new not that I found anything in any repository that would effect the Kernel that I noticed but everything works fine now with today’s dated nightly. Not sure what had been the issue but is resolved so have not done much digging past that a nightly can at times be buggy. Also and should fit into the OP the CM-13 version of the Kernel although has pretty much all the Stock/AOSP features at this point is totally based from the CM Kernel. It is not a Kernel with a few changes to become CM compatible but started with the CM code and will continue to check upstream for anything added or changed in the code by the CM team to stay current for better or worse but hopefully more the first one. Otherwise is the long way of saying that any code that does not merge clean with the CM code for the Kernel will either not be added or reverted.

Happy V Day & in the immortal words of Sean Price, P!
[Nexus 6 Android Development] NolenUmar:
(old galaxy victory fan) Just wanted to stop by and tell you that you're doing an amazing job with this! Cannot wait for the ROM :)
[Nexus 6 Android Development] wolfeyes30:
Force encryption disabled on the AOSP/Stock kernel?

Thank you
[Nexus 6 Android Development] chairshot215:
Yeah I was loosing it for a sec trying to figure out what the deal had been because I never had an issue with disabling encryption in the past going back to the Nexus 5 and this Kernel before Marshmallow. Was driving me nutty as I was still using the same fstab set to "encryptable=" I was using with Lollipop and no matter what I wiped including data, storage and caches the dam thing kept coming up encrypted. So anyway did not make any changes, actually thinking it was broke may have released two versions that I just either did not care or pulled the fstab from a Rom or Kernel that had advertised encryption disabled.

https://github.com/Starship-Android/android_device_moto_shamu/blob/lollipop/fstab.shamu

https://github.com/Starship-Android/android_device_moto_shamu/blob/M/fstab.shamu

Anyhow don’t remember what version of TWRP I had been using during this hell but flashed the dam Starship Kernel with the original unchanged fstab and then booted into bootloader and flashed the cache and userdata images and once booted back up was not encrypted:o. Managed to stay unencrypted until some time over the weekend I guess I must of flashed a Rom test forgetting I was testing new device files but noticed my phone was encrypted:(. Guess timing was at least on my side as I take updates for my daily by fastboot flashing the system.img and cache.img every time a new Factory Image is posted so before doing so this time flashed yesterdays Kernel and added userdata with the system image I was abouts to flash anyhow. Figure it was about time as I had been restoring backup after backup with Rom testing and noticed my test Roms had increasingly started getting much better. At first thought it was just I was doing a good job with the Rom but part of that was definitely backing up and restoring 50-100 times. Even with all the hash checking I have now reinstalled all my apps and settings and everything is much, much, faster. Sucks but sometimes a clean start does wonders. lol, so that’s my what the frack is up with encryption walk down memory lane rant.
[Nexus 6 Android Development] bupkis:
This kernel and Benzo ROM with F2FS is working really well as a stable daily use setup with great battery life. Keep it going.:good:
[Nexus 6 Android Development] chairshot215:
Well followed through with updating at the same time using the same number:D

Also I don’t get as much time with the CM-13 Kernel as Stock/AOSP so feedback is very much welcome.

Otherwise battery life has been pretty good. The last few days testing the latest versions have been charging for about a half hour a day in the A.M and have not come close to running out of power.
[Nexus 6 Android Development] chairshot215:
About to post Starship-Kernel The Next Generation. The new kernel series still has all the features as TOS kernel but is soooo much faster. Is like going from warp 6 up to warp 9. Battery life is about the only thing down. With that said and am sure everyone has a different experience had been going a day or two with the last few builds and had been wondering how much speed has been sacrificed and if had to charge once a day over two so things would be more snappy is a trade I was willing to make. Like I said I am sure everyone differs based on apps, accounts and use. Myself have been synchronizing 3 accounts with about 100 apps in total using heavily from say 9-6 but after work tend to spend more time using my tablet and may loose 10% from5 pm to 5 am the next day. Most days do not even remember taking the charger home from work or even over the weekend and have not had any power issues running Starship-Kernel. So decided to cut down a bit on battery savings. Using Antutu as an example stock Nexua 6 has an average score of 71500. The last Starship Kernel after running 10 times had an average score of 74686. TNG Kernel after ten runs is 78543. Battery still seems better than average but still have the ability to increase the battery life pretty drastic. Actually work in an office so not sure why I had been on a mission to squeeze as much juice as I could considering I can charge just about all day so figure will leave up to the Kernel users. If anyone would like more battery life I still have a decent of room to play with so just let me know. Otherwise think will be happy with the new version of the Kernel as pretty much started from the beginning with a much better understanding of everything I had used in the original so have a much better understanding of how to manipulate things for desired effects. Again please no Jinx Knocking on the wood and not talking my desk. Otherwise be a posting once finished, compiling that is. Yeah maybe building would have been a better choice of word. Still if think battery is fine as is still have a few things left that can make things even faster than is now with TNG Kernels.

Decided the Rom is being moved into N. If used a Starship Rom pre Lollipop would notice just about every image and colour is changed so with the crazy early preview decided to start now in hopes of releasing days after the first official release and not just for the Shamu but have been constructing the Rom with a common device directory so will be able to hit up any device running AOSP from the start. Will just need to talk with a few devs about using custom Kernels for devices I don’t own but have the 5.6.9 and player down. Just started a player Kernel and definitly a challenge as is probably the only none ARM based Android Kernel like ever. Seriously though not sure Google now not giving a definitive answer and done with reading for the day.
[Nexus 6 Android Development] t3chn0s1s:
[MENTION=4310179]chairshot215[/MENTION] I must say... I have yet to try your kernel although I look forward to doing so. But, I must say I'm LOL at all the ST references. I am an enormous Trekker (done conventions but never in costume) and all around nerd so the title of this kernel alone appeals to me. ?
[Nexus 6 Android Development] bupkis:
I haven't had any luck booting Benzo or Chroma with F2FS data/cache on any kernel newer than r8.8.1.

Clean flash with it will initial boot within a minute or so, any kernel newer just hangs on ROM boot animation for 10 minutes, when I give up.

Just me or some basic change to these newer kernels?
[Nexus 6 Android Development] smclaughlin3:
This kernel says hw encryption, does that mean it's still encrypted? Thanks!
[Nexus 6 Android Development] chairshot215:
Yes but is a different method then the software encryption and does not have a performance impact.

http://nelenkov.blogspot.com/2015/05/hardware-accelerated-disk-encryption-in.html?m=1
[Nexus 6 Android Development] chairshot215:
Is a different method then the software encryption and does not have a performance impact. That said had not included in new Kernel Version. Must have missed removing from the OP last night.
[Nexus 6 Android Development] chairshot215:
Will look but Google has recently made a few changes to the AOSP kernel. Honestly have not looked all of them but will see what has changed between 8.8.1 and newer Kernels.
[Nexus 6 Android Development] andrewjt19:
Hey buddy it appears that both kernel links are the same? Is there a different edition for CM versus Stock/AOSP?

tApPeD fROM mY nExUs 6
[Nexus 6 Android Development] chairshot215:
They are different I just posted the wrong link but has been corrected.
[Nexus 6 Android Development] chairshot215:
Looking into this now have you tried the older Kernel with the latest Rom versions? Just trying to rule out any Rom changes.

I know it had not been compatible with Benzo back before November and 8.8.1 released in February so at least have a time frame of commits to narrow down. Otherwise am in investigation stage as nothing just pops out.

Also why looking at all possibilities what recovery are you using? Why testing would like to stick with what had been working for you why trying to reproduce.
[Nexus 6 Android Development] bupkis:
using this TWRP, not the multirom version-

http://xdaforums.com/nexus-6/themes-apps/recovery-twrp-3-0-f2fs-multirom-t3313292

I am willing to test clean flash either Benzo or Chroma with your kernel version choice- link me to the kernel you would like me to try with F2FS data/cache... v8.8.1 has not failed me yet :good:
[Nexus 6 Android Development] chairshot215:
New version is probably the most snappy to date and battery is also just as good as ever
[Nexus 6 Android Development] omaralkha99:
noobish question, the features that come with the kernel mentioned in the op, do I have to do anything else after flashing to implement them (auditor?) or are they applied once flashed?
[Nexus 6 Android Development] slimdizzy:
Couldn't find the for sure yes or no to this so .... does this kernel force encryption or no?

Thnx
[Nexus 6 Android Development] chairshot215:
At the moment everything for the most part is set for flash and go. Have removed f2fs support from the feature list as has not been working with Benzo & Chroma over the last few builds. Have not had much success in determining why but am still working on it as previously f2fs support with the Kernel had been widely compatible with just about any Rom. Big thanks to bupkis who has been helping me out by doing a lot of f2fs testing. Technically the code is still in place but compatibility from Rom to Rom is such that going foreword am not including as a feature. I will make a post if the status on this changes. Otherwise without changing to an f2fs file system the only other feature that would require doing anything special besides just flashing is encryption which leads into the next question.

No the Kernel does not force encryption but if currently encrypted will require a full wipe after flashing.
[Nexus 6 Android Development] chairshot215:
Only real difference between version posted on 04/04/2016 v 04/02/2016 is Kernel Version has been bumped up to version 3.10.101. Few other very minor changes that dont have time to explain and most likely would not care.

So like Sean Price, P!
[Nexus 6 Android Development] omaralkha99:
Hey, Im using the previous build of the kernel and the cpu wont go over 1.7 ghz upon changing it on kernel auditor. Using audiophile rom btw. Any ideas?
[Nexus 6 Android Development] chairshot215:
Have not yet done an exact reproduce as in after reading the comment I did a test with pure AOSP and the current version of the Kernel and did not run into this problem. If have a chance tonight will flash the previous version and check again. Have been using updated fast charge USB code Cherry picked from Elemental X for a few version now. May help in reproduction attempts if could let me know if you experienced this why charging over USB or AC. Also if had only tested why charging or if had persisted after charging?Keep you updated but does not seem to effect the current version using Stock or AOSP.
[Nexus 6 Android Development] omaralkha99:
ok will try again soon once I flash another rom, I was on a stock rom and wasnt charging at the time of trying to change the frequencies..
[Nexus 6 Android Development] chairshot215:
Thanks,

Like I said this was current version on Stock.

Let you know what else I come up with.

If anyone else experiences this issue let me know as have not been unable to reproduce it so the more information provided the better.
[Nexus 6 Android Development] chairshot215:
Updated the Stock Kernel as F2FS seems to be back in business. Going to see about extending battery life but know some had been happy with F2FS compatibility so posted the update as SMTNG6. Again, Thank you bupkis for doing most of the testing.

Also Bench Mark from AnTuTu is pretty good with this version.

Going to see about increasing battery life making as few compromises as possible.
[Nexus 6 Android Development] arif9m9:
Wrong kernel. Sorry.

[MENTION=4310179]chairshot215[/
[Nexus 6 Android Development] arif9m9:
Will Xsposed V81 cause any conflicts? And is it best to use the Chroma or the Pure Nexus Rom with this kennel?
[Nexus 6 Android Development] omaralkha99:
whats ur rom and settings, and any mods as well?
[Nexus 6 Android Development] chairshot215:
Honestly not tested but do not see reason it would cause any issues. With that said if you give it a try let us know.