yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Lagarde:
That worked! Not sure why it was being so fussy about selinux, but the update fixed it.
[Nexus 6 Android Development] neobuddy89:
For some reason - stock roms and multirom not compatible with selinux modification to permissive. Will check later.
[Nexus 6 Android Development] jbaumert:
Stock ROM/Magisk/Stock Camera. Still getting the camera errors/crashes that require a reboot to fix. Appreciate the effort as this kernel works well.
[Nexus 6 Android Development] neobuddy89:
As mentioned earlier by somebody, please clear data of camera instead restarting device.
[Nexus 6 Android Development] donkeypunch1257:
I/O Read Ahead

Why is the i/O schedulers read ahead set to 128kb? This seems extremely low. Is this an oversight or intentional?
[Nexus 6 Android Development] tsjanda:
I'm not sure if this has been asked but will this work with Lineage os?
[Nexus 6 Android Development] wavedashdoc:
I'm just going to save the OP some time...

Per OP:

"This should work on any LOS-based nougat ROM and most AOSP nougat ROMs."
[Nexus 6 Android Development] tsjanda:
I mainly asked those on lineage if this works. I should have been more clear
[Nexus 6 Android Development] velishka:
front camera is broken in the latest build
[Nexus 6 Android Development] d3vilskid:
Works fine for me.
[Nexus 6 Android Development] nick491:
No problems here either.
[Nexus 6 Android Development] heisenbergfromIN:
Given the clear and concise description, and the positive feedback given by many(if you happen to go through the thread), it should work. The developer is not known for publishing incompatible, unstable, or unfinished software. So, rest assured, the kernel works. Cheers!
[Nexus 6 Android Development] neobuddy89:
Intentional. Values taken from CAF based ROMs.

Overall benchmark wasn't affected by this change. Is there anything else to check impact on Nexus 6 (not theories on net)? Let me know.
[Nexus 6 Android Development] donkeypunch1257:
I didn't mean to cause offense. I've been using the kernel for a while and have never seen it below 512.
[Nexus 6 Android Development] neobuddy89:
No offence taken.. I was curious..
[Nexus 6 Android Development] athulele:
I'm still having camera issues.

LineageOS latest weekly + sigma 8.9

I've attached log when it works (both cameras) and a log when none of those work, not even the flash.

the flashlight option is greyed out..i tried clearing camera app data but it didnt work.

thank you
[Nexus 6 Android Development] neobuddy89:
I will check
[Nexus 6 Android Development] donkeypunch1257:
The camera issues returned for me with the 8.9 update. Tried the regular fixes to no avail. Returned to 8.8 and all is well.
[Nexus 6 Android Development] neobuddy89:
I have reset all camera changes in below test build:

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

Please clear data of camera app from App Info and test. Tested official release build and test build on LOS, crDroid and PureNexus - no issues for me. :/
[Nexus 6 Android Development] athulele:
It's still showing me the same signs :/

I've uploaded logs where front cam didn't work and no camera worked
[Nexus 6 Android Development] shamu17:
Just re-flash zip
[Nexus 6 Android Development] velishka:
Loving the kernel and using it from early builds. But 8.9 is not stable, got a bootloop, camera issues ... rolling back to 8.8 - rock solid.
[Nexus 6 Android Development] neobuddy89:
Check 8.9 test build posted above.
[Nexus 6 Android Development] Lagarde:
I have to agree with the others. 8.9 even after the test build, isn't as stable. I've never had the camera issues, but on 8.9 I get reboots if the phone sits idle for too long (deep sleep issue). No such problem on 8.8.
[Nexus 6 Android Development] termax 14:
conservative governor its having the core 4 locked at 2649Mhz also having random shutdowns while the screen is turned off. kernel version 8.8
[Nexus 6 Android Development] enzoevo:
2 quick questions. 1. Are the latest September security updates included in the latest version of sigma? 2. Do the kernel patches address the blueborne vulnerabilities? Or are they more than just kernel based?

Thanks.
[Nexus 6 Android Development] heisenbergfromIN:
September's security patches address the Blueborne vulnerabilities and the latest version of Sigma doesn't include those patches. Perhaps in the next update, but who knows? The developer is working hard on Oreo as well. So, all you can do is hope for a final Nougat build before he fully migrates to Oreo development.
[Nexus 6 Android Development] neobuddy89:
Update!

And wait is over for new update. Here you go. sigma 9.x is meant only for Nougat ROMs. So, better not to be a hero. Recommended to use with selinux permissive especially if not on crDroid ROM or using on secondary ROM via multirom.

Short changelog

September 2017 security patches patched in.

SDCARDFS updates from google.

Fixes for serial driver (BT) from CAF upstream.

Misc bug fixes from linux mainstream.

P.S. I see changes in camera driver from google in Sept patch. Good luck for those having issues, hope they will be gone now.

Downloads

v9.0: https://www.androidfilehost.com/?fid=673368273298985896

Older builds -

v8.9: https://www.androidfilehost.com/?fid=745425885120759287

v8.8: https://www.androidfilehost.com/?fid=745425885120758086

v8.7: https://www.androidfilehost.com/?fid=889764386195922343

v8.6: https://www.androidfilehost.com/?fid=673368273298977757

v8.5: https://www.androidfilehost.com/?fid=817550096634791428

v8.4: https://www.androidfilehost.com/?fid=961840155545586986

Commits

https://github.com/neobuddy89/shamu/commits/cm-14.1

Cheers!
[Nexus 6 Android Development] cujo6801:
Thanks as always

"Sent from the Dog Pound"
[Nexus 6 Android Development] donkeypunch1257:
I'm a little confused, is the kernel permissive by default?
[Nexus 6 Android Development] neobuddy89:
Kernel copies permission policy of your existing ROM from command line.
[Nexus 6 Android Development] donkeypunch1257:
Thanks for clearing that up.
[Nexus 6 Android Development] jbaumert:
Hate to tell you, but front camera is still "randomly" missing. Stock ROM (Sept build). Clearing data alone will not restore function. Rebooting fixes.
[Nexus 6 Android Development] athulele:
+1, I'll get you logs in a few minutes.
[Nexus 6 Android Development] athulele:
[MENTION=3795148]neobuddy89[/MENTION]

These lines show up in all cases, even when camera works, so not sure what's wrong here:

[ 14.774935] camera_v4l2_open : posting of NEW_SESSION event failed

[ 14.774943] camera_v4l2_open : Line 585 rc -110

These show up only when all cameras don't work:

[ 23.933358] MSM-CPP cpp_load_fw:927 CPP FW Version: 0x10060000

[ 23.981016] camera_check_event_status : event_data status out of bounds

[ 23.981037] camera_check_event_status : Line 71 event_data->status 0X10001

[ 23.981052] camera_v4l2_open : checking event status fails Line 592 rc -14

Can't find anything else that makes sense to me in the log where only front came doesn't work

Attached 3 logs with all cameras working, only the rear working, and none of them working.

I'm on latest LineageOS nightly.
[Nexus 6 Android Development] velishka:
Same here. I am on Vanilla rom
[Nexus 6 Android Development] neobuddy89:
Thanks, guys. I will test this on Nitrogen for entire day to debug.
[Nexus 6 Android Development] neobuddy89:
1 hour of testing - no hiccups.

Logs you posted doesn't tell much.

By any chance would you have system logs too? That would be last resort.
[Nexus 6 Android Development] athulele:
I can get you more logs.

Do you need logcats?

Also, ones the camera is loaded up (both work) there's no problem until I reboot. If I reboot and it doesn't work, then it doesn't work until I reboot again.

---------- Post added at 11:23 AM ---------- Previous post was at 10:39 AM ----------

[MENTION=3795148]neobuddy89[/MENTION]

Here is the logcat:

http://paste.ubuntu.com/25538595/
[Nexus 6 Android Development] neobuddy89:
In my tests, I have rebooted 4 times so far. :crying:

On side note, which gapps package do you use?
[Nexus 6 Android Development] neobuddy89:
Logcat is helpful! Can check something now. Hope, few users are up for test tonight maybe.

09-15 11:15:19.674 E/mm-camera-intf(335): mm_camera_open: cannot open control fd of '/dev/video3' (Bad address)

09-15 11:15:19.674 E/mm-camera-intf(335): camera_open: mm_camera_open err = -1
[Nexus 6 Android Development] athulele:
Let me know if you need to test :)

Thanks!
[Nexus 6 Android Development] neobuddy89:
Please test:

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

Long shot.
[Nexus 6 Android Development] athulele:
I'll test it in a few. AFH is giving me the No Mirrors Found error

I use the latest BeansGapps Full. (20170725)
[Nexus 6 Android Development] athulele:
Hey, could you kindly upload it somewhere else?

AFH is acting weird.

Thank you!
[Nexus 6 Android Development] Lagarde:
Try again. AFH finally seems to have fixed their mirrors.
[Nexus 6 Android Development] athulele:
Unfortunately it still does the same :/

dmesgs are same as before so getting logcats.

Logcats:

All cameras work: http://paste.ubuntu.com/25541166/

other log:

http://paste.ubuntu.com/25541370/
[Nexus 6 Android Development] jm9843:
I'm on stock 7.1.1 (August patch level) with twrp and Sigma kernel v8.7 (awesome work btw). What's the recommended way to apply the latest OTA for the September patches? I'm comfortable with adb/fastboot and will, obviously, be flashing Sigma kernel again if it's overwritten in the process or v9.0+ is required.
[Nexus 6 Android Development] neobuddy89:
Thanks. Another test blind build. This build has few fixes from CAF upstream with camera open-close routine and is compiled with 4.8 toolchain.

DL: https://www.androidfilehost.com/?fid=673368273298986404 (Test build)
[Nexus 6 Android Development] athulele:
Nope :/ its still doing the same.

Logcat - http://paste.ubuntu.com/25548091/

I've attached the dmesg.

Thank you for your efforts man!

EDIT: I've rebooted like 10 times now. It seems that either both cameras work or both error out. Front facing isn't "missing" like before. I'll let you know if that happens. Thank you.
[Nexus 6 Android Development] enzoevo:
9.0 release working like a charm on PureNexus. No issues with cameras here. My idle battery was at 1.58% overnight which is the best ever. Can't wait to flash crDroid Oreo goodness. Thanks [MENTION=3795148]neobuddy89[/MENTION]!

---------- Post added at 09:43 AM ---------- Previous post was at 09:43 AM ----------

9.0 release working like a charm on PureNexus. No issues with cameras here. My idle battery was at 1.58% overnight which is the best ever. Can't wait to flash crDroid Oreo goodness. Thanks [MENTION=3795148]neobuddy89[/MENTION]!
[Nexus 6 Android Development] athulele:
[MENTION=3795148]neobuddy89[/MENTION] -

The front cam went 'missing' after a reboot again. But it rarely happens now.

Here's the log - http://paste.ubuntu.com/25558909/

Hope it helps :)
[Nexus 6 Android Development] rignfool:
So... I have a real stupid question....

Are you "clumsy" as in does your device bounce off the ground a lot...

It sounds to me more like an intermittent connection than a straight up software problem... Like sometimes it doesn't init the camera due to a fault connection...

If you have taken your N6 apart before... Do it again and make sure all the connections are properly seated...
[Nexus 6 Android Development] athulele:
Heh, i thought of it before. But I've dropped my device just once and that was almost a year ago. Also never taken it apart.

Plus it works fine with other kernels so issue isn't with hardware i guess
[Nexus 6 Android Development] rignfool:
Ok... I just had to ask... When things don't init proper... Sometimes it's just hardware...

Good to know...
[Nexus 6 Android Development] cutefuzzybunny:
I have the same front camera issues. Clearing dalvik/cache helps for a few hours. I'm on an older version though so I'll try updating to the new one and see if it fixes. Kernel is on latest purenexus.
[Nexus 6 Android Development] espionage724:
Should this be flashed by anyone not caring about potential camera issues? Also, is only this test build built with the 4.8 toolchain, or will future builds also be built with it?
[Nexus 6 Android Development] donkeypunch1257:
Experiencing same camera issues as the others. Tried with stock camera on Lineage, camera nx, open camera, camera zoom fx pro, and camera fv-5. Camera FV-5 wouldn't open returning error "camera in use by another application", the stock and camera nx work after clearing data until a reboot, then forced close. Neither allowed use of front camera. Open camera seemed to work after reboot but again front camera refused to work. I got these results on both the main release kernel and the test build. Flashing back to previous non-sigma kernel resolved my camera issues.
[Nexus 6 Android Development] johnb380:
Anyone having camera issues see if you have any blacked out photos or videos in storage. If so delete them also after doing that clear data of all camera apps then reboot to see if cameras now work.

Make sure all permissions are set to on for all cameras after the reboot!

If that doesn't work for you try backing up any videos or photos taken with the camera that are stored on local storage then delete them and clear data of all camera apps and reboot and that should make camera work.

Make sure all permissions are set to on for all cameras after the reboot !

For some reason these have worked for me recently to get cameras and or flashlight to come back to life.

Good luck.
[Nexus 6 Android Development] donkeypunch1257:
This seems to have helped. Camera is at least surviving reboots. However front camera is still hit or miss. After rebooting it sometimes works. If it doesn't work it will remain out of service until rebooting again and that still doesn't guarantee that it will work.
[Nexus 6 Android Development] espionage724:
Not related to this kernel, but someone reported that a battery replacement made their camera disappear, and another report that says it should come back: https://www.reddit.com/r/nexus6/comments/72dgve/replaced_battery_no_cameraflash/

I wonder; perhaps the camera disappearing at random could be related to some kind of hardware suspend/sleeping?
[Nexus 6 Android Development] rignfool:
If that were really his issue... It would happen on all ROMs and kernels... Because it would be hardware... And he is insisting that it is the kernel because it works in others...
[Nexus 6 Android Development] Superior Sandbox:
Will this work on the October security patch?
[Nexus 6 Android Development] heisenbergfromIN:
Of course, it would work with a ROM with October security patches.
[Nexus 6 Android Development] neobuddy89:
Final Update!

Hey all,

In case you missed my post, I am moving on to another device (OP5) and therefore, my projects on Nexus 6 are discontinued. Here is the last one (best one for last?) This kernel is pretty much slimmed down and based on latest bring up I did for Oreo. It includes latest from upstream and Oct security patches.

What's removed compared to previous version? Backported Ext4, Newer devfreq structure, Hotplugging drivers, MultiROM support, backported libs, compress offload changes. (See OP)

What's included for sure? Stable, bug fixes from mainstream and google, friendly BCL and thermal hotplug, zram support, better interactive governor with CPU boost, F2FS, sdcardfs, improved CPU idling and scheduling, KCAL driver, Wake gestures, State notifier, etc.

The kernel was blended carefully in last 2 months for stability, performance, and long lasting battery. BCL hotplug will ensure no sudden shutdown, so it's important. Thermal hotplug will work with it to ensure low temp all the time! Do not disable them. If you want to rely on something for long and you don't crave for things that aren't in, this kernel is for YOU.

sigma Kernel 9.2 FINAL for Nougat:

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

sigma Kernel 10.0 FINAL for Oreo:

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

Thank you. This marks last release of sigma Kernel for Nexus 6. Until next time!

Cheers. :cool:
[Nexus 6 Android Development] duttyend:
Thank you so much for everything you did for this device... We will miss you badly
[Nexus 6 Android Development] :
Thread closed by OP request.
[Nexus 6 Android Development] rignfool:
You know better than to ask for ETAs...

C'mon man!

Now... This here... Is awesome... A custom kernel... That can still use mpdecision so my phone will last all day...

A million thanks... The mpdecision void left by [MENTION=3357040]Imoseyon[/MENTION] has been filled on my phone...

---------- Post added at 09:53 AM ---------- Previous post was at 09:14 AM ----------

Ok... Let's see if I can learn something here...

I see we have the noop-suspend io scheduler thing...

So... I'm wondering... Of the schedulers currently available.... Which one is the performance one?

I've seen lots of posts about saving battery and using noop... But never a post like "I want my device to smoke the tires off the rims so I use..."

I know bfq has some other advantages... And I remember row being performance oriented...

Any thoughts?
[Nexus 6 Android Development] gothy.gothy:
You liked, didn't you, ring?
[Nexus 6 Android Development] rignfool:
Actually... I haven't even tried CrDroid... I've been using Pure Nexus cuz it's the only one I can get ok Google to work on...

I did use DU... But I tend to try to shy away from CM based ROMs since you never know what the CM guys will merge
[Nexus 6 Android Development] II_DiE_4:
?? I thought you know what you are talking about? DU is AOSP based, pretty much like PN with their own developed tweaks ans kernel.

CRdroid is CM based, which in turn is again AOSP based. So, what the hell are you talking about?
[Nexus 6 Android Development] nathanchance:
CM isn't entirely AOSP based, there is a lot of CAF additions (and I believe they even rebased on CAF a little bit ago). That's why people usually make the distinction between AOSP and CM/CAF, as there are a lot of addition changes to things like the build dir and hardware/framework repos. The DU bit is spot on though.
[Nexus 6 Android Development] neobuddy89:
Few notes on why we don't have many hotplug drivers:

I see few users opt for kernel with continuous hotplug. This isn't good idea with newer Android versions reasons being:

1. Starting with marshmallow - we have CPUSETS enabled in ROM and KERNEL. CPUSETS decides what tasks run on how many and which cores. With hotplug into picture, tasks will start getting migrated and this will affect overall performance.

2. This kind of auto scheduling hotplug introduces overhead which makes hotplugging a expensive process and adds very little value.

3. Few kernels are not properly upstreamed and this makes them vulnerable to bug where task is lost when CPU gets unplugged.

4. Few hotplugging drivers locks up cores making them unavailable for other drivers and kernel scheduler to lock.

5. Loading increases on a single core when we are suppose to distribute load equally on all cores. This makes core run on higher frequency for more amount of time - consuming more battery and offsetting value add by hotplug driver.

6. Interferes with hotplugging of other drivers like thermal, BCL, etc.

7. If hotplugging was real value add, I believe SOCs would have not discontinued continuous hotplug by mpdecision.

With the help of few good devs, we had worked on enhancing many hotplug drivers in past - namely msm_hotplug, intelli_hotplug, alucard_hotplug, and so on. But most of us now believe to go with stock as much as possible.

Sigma kernel uses a hotplug alternative called state helper. Salient features are:

1. There is not auto-scheduling within driver. This eliminates overhead unlike others.

2. Instead of auto-scheduling, we have triggers by other drivers. State notifier driver informs when screen is turned off - so that state helper can put sibling cores to sleep. Thermal driver tells when device is heating up and wants to put core to sleep so that state helper won't interrupt. Battery driver tells when battery is low so that state helper can put 2 cores to sleep switching into eco mode.

3. You can customize parameters by using apps like KA MOD.

4. It is battery friendly.

To conclude, we get best of all worlds when it comes to hotplugging. Cheers.

Have a great day.
[Nexus 6 Android Development] neobuddy89:
There are some good guides available on XDA that explains different IO scheds. Like this one:

https://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

Newer devices with CAF uses BFQ and didn't face any downside compared to others - reason why we are using BFQ.
[Nexus 6 Android Development] espionage724:
Any chance this kernel could get a toggle for fsync and the ability to set the vibration strength? On FrancoKernel, the respective paths are /sys/module/sync/parameters/fsync_enabled and /sys/drv2605/rtp_strength
[Nexus 6 Android Development] rignfool:
Regardless whether he puts that toggle in or not...

You can get a similar result by switching on laptop mode in the 'virtual memory' screen of most kernel tuning apps...

It's not exactly the same thing... But it's very close
[Nexus 6 Android Development] Thunderbolt69:
You can adjust the vibration strength.
[Nexus 6 Android Development] espionage724:
I'm not sure if it was fixed in sigma Kernel 7.3 or if my set-up was causing the problem, but USB Tethering works fine now on the same crDroidAndroid version and 7.3 :)
[Nexus 6 Android Development] nick491:
OK, with the latest sigma kernel 7.3 I wasn't having any problems at first but now my device is not charging correctly ("not charging").

Even after unplugging the device it still shows "not charging" in Ampere but then after about 5 seconds it shows correctly, "discharging". Even with the device completely turned off it shows as charging but never actually charges.

I used 3 different chargers last night and turned off the device overnight. The third charger actually charged the device from 34% to 40% this morning, then the device actually fully charged on my Motorola turbo 3 charger this morning. Now I'm completely unable to charge my device at all. When I go into recovery the battery changes to 40% instead of 54% in the ROM (then back to what it says in recovery after checking power in that one).

I'm using a Nexus 6 with the latest crDroid 3.4.

I even tried flashing the sigma kernel again but the issue persists. I would hate it if this is an actual hardware issue and hoping it's purely a software issue.

As a side note, also my device says charging like in the third screenshot but is not actually charging, dropping the percentage slowly as if its not even plugged in.

Also the MPDecision was on yesterday but today after flashing sigma it shows as turned off (MPDecision). I turned it back on but still no change.

Should I turn on even trying "AutoSMP" or "USB Fast Charge" in Kernel Adiutor?

Any help\tips would be super helpful. Thank you!
[Nexus 6 Android Development] neobuddy89:
To make sure this isn't hardware issue, flash stock images/ROMs after backup.

For me, I had issue of slow charging - I simply changed connector that connects device with Moto Turbo charger and I am good again. On crDroid, lockscreen shows whether it's slow charging or rapid charging, I used that as indication.
[Nexus 6 Android Development] rignfool:
This is probably my fault... Or something...

I know what base the ROMs mentioned are... I just probably worded it poorly... The jist was I ain't used CrDroid since I don't like cm base...

But this kernel... On a ROM that still has mpdecision's touchboost enabled... Best battery life I've ever had... With all Google services enabled... I'm still averaging under 3% per hour...
[Nexus 6 Android Development] andrewjt19:
I still can't get this to boot. I'm using multirom TWRP and PN latest release. Flash the kernel, bootloop at Multirom selection.
[Nexus 6 Android Development] garywojdan81:
What version of twrp and multirom? I'm running multirom twrp 3.0.3.2 and multirom v33b, both from captain throwback, and it works fine for me.