yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=4988866]tdhite[/MENTION] My apologies, I may have missed your post about it if I was just skimming thru. Thank you for trying man, it sucks it went that way with Samsung. But thanks for considering checking it out in the future! Again, once I get the time and patience to setup Nougat, I'll be super glad to know I'll be covered by your kernel! I want to go ahead and do it but I have relied in Xposed for so many years that I don't want to be without it, but I fear that a couple of my current issues could be being caused by it. I'll figure it out lol. Thanks again! :)

Chuck
[Sprint Samsung Galaxy S6] asafegous:
Could we flash magisk after this kernel?
[Sprint Samsung Galaxy S6] Trippyy Doee:
Did you not read 4 posts up ? Lol
[Sprint Samsung Galaxy S6] Tekken Lord:
Guys, I lost Wifi password and the battery was draining after I flashed SU to install the latest N kernel. Can anyone help? TIA.
[Sprint Samsung Galaxy S6] tdhite:
Reset Synapse and reboot. I have phenomenal battery.

Also, do you happen to have another init.d manager? Because I moved all startup to init.d processing, so if there is another it will cause constant spawning of crond and that chews serious battery.
[Sprint Samsung Galaxy S6] seneko:
Using the beta 4.99 N build, enabling the CIFS module causes instant reboot.

Hope to get a stable CIFS in the next release, it's one of the main reasons I'm enjoying SkyHigh kernel :D
[Sprint Samsung Galaxy S6] ChubbbySquish:
Well, enjoy it for it's phenomenal speeds, and battery life improvements too. It's a kernel, not an app, it does a lot you don't see. I'm just waiting for some Magisk to be ready, then I'll move back this route. Keep it up [MENTION=4988866]tdhite[/MENTION] ?
[Sprint Samsung Galaxy S6] tdhite:
Yea, there are some security games taking place that I have to work around. I bet you don't have working Bluetooth either (secure storage issues). WiFi passwords getting stomped too I think.

N added much more security around things and I want to keep it all to the extent possible.

Hang with me, working all these things.
[Sprint Samsung Galaxy S6] tdhite:
I will put up a next beta tomorrow, it is all Magisl now. V12 is quite stable.

Two bugs remain that I can see, both related to SecureStorage. Seems Samsung apps no longer honor disabling it.
[Sprint Samsung Galaxy S6] Nye-uhls:
So we're all in agreement that [MENTION=4988866]tdhite[/MENTION] should include his paypal link in the OP so we can flood it with donations for all the hard work that's going into this kernel?
[Sprint Samsung Galaxy S6] tdhite:
[KERNEL] [ROOT][MM | N] [SM-G920P] [29-May-2017] SkyHigh Kernel (Port) [v4.99]

I certainly appreciate the support! We are close! If you do want to donate, look for the "Donate To Me" to the left of any of my posts. I'll add it to the OP in case mobile users can't quite see it, my signature should have it as well.

With that said -- we're not done quite yet, but seriously, darned close. The kernel now sports full Magisk (v12) support. I dropped SuperSU because Magisk is a superior model for kernels, imho, particularly given the module model (which I now use to configure the kernel instead of init.d scripts). SecureStorage, however, is mystifying me in terms of overcoming it to get Bluetooth and WiFi passwords to stick. I'll get it figured, it's just that the Samsung apps are no longer honoring the system properties that the system apps are. How odd! I've seen other cases in the kernel regarding modified parameters in the sources, yet makefiles and defconfig files are not synced (I've fixed all of those I have seen so far).

You can download the new beta (Magisk enabled) kernel from the OP.

Please let me know how it goes. As always: READ THE DISCLAIMER!

BTW -- if you are wondering why Magisk v12.0 instead of the v13 snapshots, the latter are not always good builds and tracking that would require me to track daily builds and re-release this kernel. v12.0 is quite good, v13 will be better (when done) and I'll update immediately when it releases.

:cool:

-------------- edit -- IMPORTANT for early downloaders ------------

There was a slight error in the flash updater-script that allowed the prior kernel setup scripts to stick in /system/etc/init.d/00-SkyHigh -- I have uploaded a new flash, but for those that happened to pick up the early one, just go delete that file with Root explorer, or if you're not ok with that, feel free to download again and reflash. It's no big deal in reality, just two crond services get run, only one is needed. In any event, do one or the other of the above. If you downloaded after 6PM CDT on May 29th, 2017, you are fine. It may take a half hour or so for the new flash to show up, so just hang with it.
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=4988866]tdhite[/MENTION] You are amazing with this kernel, sir!! Im now on Nougat as of yesterday evening with your 4.99n kernel and loving it! I am disappointed with the secure storage issue however, and I know that's not your fault and you're working on it. I know I don't speak for myself when I say I have total faith that you will figure this out. I don't use Wi-Fi quite enough for it to be a deal breaker and same with Bluetooth, but I do hope it gets sorted out soon. I do have a weird issue with the Unknown Sources setting in Security options turning itself off at times, not sure if that's related to your kernel or if it's a native Nougat thing but I have removed every system app that is not needed by me, especially the Sprint stuff as I am on T-Mobile with this phone and I might have fixed that issue, not sure yet. Now with all that said, I have what is probably a dumb question. I am not familiar with this Magisk. I take your word for it that's it's superior to Super SU, and in that case I would like to use it. Since I am on your 4.99 kernel, which has SuperSU, what is the procedure to 'convert' to Magisk? Is it as simple as flashing this new kernel? Should I wait for a stable non-beta build? Thank you again for all the time and effort you have done for this phone, you are a Godsend! :)

Chuck

EDIT : Never mind, I see the instructions on how to switch to Magisk in the original post. Disregard my dumb question haha :)
[Sprint Samsung Galaxy S6] asafegous:
I had an issue today where the screen would not turn on. I tried adb logcat, but it wasn't authorized. Not sure if that's SecureStorage issue. Adb is always on on my devices. Adb and apps.
[Sprint Samsung Galaxy S6] seneko:
Magisk support is amazing! Thanks for your nice work.

As the CIFS issue, the new 4.99 kernel doesn't shows MODULE page in the Synapse, so I think I'll wait for the next release :good:.
[Sprint Samsung Galaxy S6] tdhite:
[KERNEL] [ROOT][MM | N] [SM-G920P] [29-May-2017] SkyHigh Kernel (Port) [v4.99]

If adb fails security, go to developer options and revoke all keys, then disable/enable USB debugging. You can usually, instead, just adb kill-server, then remove your ~/.android directory, then adb shell in again.

I have not seen this error, so need to know what ROM, tweaks made, and a log file will help me see what might be the issue, if the kernel.

Thanks for the feedback.
[Sprint Samsung Galaxy S6] tdhite:
[KERNEL] [ROOT][MM | N] [SM-G920P] [29-May-2017] SkyHigh Kernel (Port) [v4.99]

No need to wait, all file systems are built-in now, no modules needed.
[Sprint Samsung Galaxy S6] asafegous:
Kill severs could have been useful. I got stuck at liveboot screen so no chance of reseting anything. Three finger recovery was not responsive. Holding the volume down (download mode) got me out. I may try to regenerate my experience later.
[Sprint Samsung Galaxy S6] t-bob:
This has happened to me a couple of times also on MM with skyhigh. Like you, my only way out was download mode. No idea why it happened.
[Sprint Samsung Galaxy S6] tdhite:
If it's rare -- the likelihood of a kernel bug is slim, but stranger things have definitely happened. Rarities are difficult to track -- so many things in the mix that can cause the kernel to lock a thread of activity (e.g., modems, sd cards, firmware activities -- lots of things) but the fact that the kernel is still operating (adb is available) suggests it is not failing, rather something is preventing the screen 'up'.

With that said -- if such a thing ever happens again, you can go ahead and reboot, but there will exist a file -- /proc/last_kmsg -- that will be the log up and to the time of shutdown so we can see what is going on from the kernel's perspective. Grab that next time and let me have a look at it.
[Sprint Samsung Galaxy S6] t-bob:
Thanks. Definitely very rare and no idea how to reproduce, but if it happens to me again I will grab the log file. And thanks tdhite for all your great support of this device.
[Sprint Samsung Galaxy S6] Nye-uhls:
That happened to me few times on marshmallow, it was always while using skyhigh, so i can't say for sure if it was related.

It was always after charging overnight. It was almost like system ui was in deep sleep and just couldn't wake itself up to show the lockscreen, my notification tone would go off and led would blink.

Volume down + home + power button always worked.

That being said, make sure the feature in settings > display "keep screen turned off - prevent screen from turning on while the device is in a dark place such as a bag or pocket" is turned off. It never happened to me after turning that off, could be coincidence, idk.
[Sprint Samsung Galaxy S6] ChubbbySquish:
It sounds very strange, and worrisome. But at least everyone had knew how to get out of it. ?
[Sprint Samsung Galaxy S6] asafegous:
I heard the shutter sound when the flash was going off. I'll try this. Thanks
[Sprint Samsung Galaxy S6] digitalchaos1980:
Hi y'all again, I have got to start by saying other than the SecureStorage issues, I am seriously loving Nougat and this kernel!! Like WOW! Battery life is good, boot up speed in phenomenal, and with some heavy tweaking I have system RAM usage down as low as 550mb on boot and rarely goes over 1.2gb used. That leaves plenty for my many apps that run, those being the ones I want running anyways. I have removed every system app possible without breaking the essential stuff I need and use. For instance I don't and probably will never use any of the Samsung or Android Pay stuff. It's gone. Removed all the Sprint bloat, as I said before I'm on T-Mobile with this phone. Not only have I removed system apk's, but their corresponding data folders, odex files and any other files tied to the apps I have removed. And I didn't stop there. I've used Disable Services app to turn off certain services I don't use and it hasn't broken anything yet. I'm very happy so far. [MENTION=4988866]tdhite[/MENTION] You are truly gifted man, thank you again for all you do! Now with that said, I've tried to do some tinkering and research on this SecureStorage issue. I know you know what you are doing but I couldn't leave well enough alone lol. I've tried many build.prop tweaks to see if I could circumvent the issue. No luck. I read that the Note 5 guys have their Bluetooth and Wi-Fi working and they have virtually the same hardware and they're mostly on Nougat now too. It has to be something crazy stupid or simple, at least I am hoping. So what makes their system different from ours?? I also read about going into the /efs folder and backing up the ss_data file and then deleting it and rebooting and then restoring and rebooting again but that didn't make any difference either. I guess either way I'm learning more as I go lol. I got faith in you [MENTION=4988866]tdhite[/MENTION] but I wanted to see if I could help in any way. I hope I haven't forgot something related to this.

Now on to my question. When I do go over to Magisk, should it pretty much play nice with the apps that require SuperSU? I know you haven't been able to implement Nethunter support but I've made some wicked headway in getting the stock Wi-Fi chip to go into monitor mode but I know the Nethunter app is weird about SuperSU and I want to make sure functionality will still be there when I go to Magisk. If not then I'll probably stick with SuperSU as long as I can, but I would much rather go forward with progress lol. Thank you for your time reading this long post but I wanted to try to help and also ask about that. Oh and I had mentioned so many posts back that my Unknown Sources kept changing back to off on me at odd times but that problem has been solved. It must have been part of a system app I removed that was causing it. It works fine now. :)

Chuck
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=4988866]tdhite[/MENTION] Man if we can figure this "skip call" thing out that could be the key. I will admit now I've never done anything in-depth with an Android kernel but I'm not dumb with this tech stuff. I'll learn as I go and see if I can at least try to come up with an idea or ideas that could be tried. And with that said, since the Note 5 is so similar, and you think it could be in the libraries, have you thought of maybe seeing if the libraries from the Note 5 could work possibly? If I am way off and don't know it then I apologize lol. But it is the first thing I can think of so far. This whole thing has me going crazy, I honestly didn't think I'd miss my Bluetooth as much bit between that and having to re-enter my Wi-Fi password every time it's driving me bananas. One thing I wasn't able to figure out was when I was trying different things in build.prop yesterday, such as changing ro.selinux= from 1 to 0 and other properties for example, I did end up trying to change the SecureStorage property back to true but when I would change it in default.prop it would always change back to false after a reboot so I wasn't able to fully test how I wanted to. Also to note there were some other solutions for a couple other phones (make and models I cannot recall atm) that had people changing their secure storage property back to true to bring functionality back. It's definitely an ODD problem and a new one in this Nougat system. I am going to read up on this JNI thing a little and see if I can get some brainstorm action going and I'll pass along anything I can possibly come up with to you. I don't have a setup to make or rebuild your kernel to try different setups but I will definitely be willing to test since I have my Nandroid backup already made in case I mess something up with my tweakings lol.

If there's anyone else out here in this forum who is knowledgeable let's see if we can brainstorm together and get this crazy issue fixed! :)

Chuck
[Sprint Samsung Galaxy S6] tdhite:
.

Magisk? Or SuperSU rooted? That makes a difference. The Magisk module I added for the kernel sets the property to false. Look at /magisk/skyhigh/system.prop -- that's where it gets reset to false.

That is possible, but as soon as that happens, the SecureStorage layer refuses to run because the kernel is 'not in sync with the platform binaries.' That means, basically, Samsung is locking out custom kernels by checking them and finding out they are not the same as the 'stock kernel.'

The files of interest (to me at the moment) are:

/system/bin/secure_storage_pm
/system/bin/secure_storage_daemon
/system/etc/secure_storage
/system/etc/secure_storage/.vendor.lib.libsecure_storage.so
/system/etc/secure_storage/.vendor.lib64.libsecure_storage_jni.so
/system/etc/secure_storage/.vendor.lib64.libsecure_storage.so
/system/etc/secure_storage/.vendor.lib.libsecure_storage_jni.so
/system/etc/secure_storage/.system.bin.secure_storage_pm
/system/vendor/lib64/libsecure_storage.so
/system/vendor/lib64/libsecure_storage_jni.so
/system/vendor/lib/libsecure_storage.so
/system/vendor/lib/libsecure_storage_jni.so

I plan to build a few different kernel versions as well to test out various commits added to reach Linux 3.10.105, though the Nemesis kernel (G920F, et al) does the same and apparently is ok with secure storage. Looking around since this is very odd.
[Sprint Samsung Galaxy S6] digitalchaos1980:
I am still using the SuperSU kernel at the moment. I'm thinking of going ahead and making my current Nandroid and switching over and getting that set up before I continue. I now realize you probably made that property to purposely revert after a reboot so that someone doesn't totally screw up the Secure Storage any more than it already is at the moment lol.

That totally makes sense to me. Figures they gotta kill the fun of a custom anything lol.

Yea I see this with the G920F. It's definitely odd because the phone is the same hardware, same chips and all. The only thing I can see being different would either be the libraries you posted above or the bootloader of our Sprint variant itself possibly. Once again I'm going to make a Nandroid. I'm wondering if I were to download that International rom and extract those library files you listed and then put them in place of mine if it would work or cause a nuclear meltdown lol. I just don't see how theirs works and ours doesn't. It's crazy! Do you happen to know if any other variants work fine, such as the ATT, T-Mobile, or Verizon models? Like I said above I wonder if it could possibly be the bootloader. As an FYI I did manage a few months back to load another couple roms on this phone from other variants and just flashed your kernel to it and they booted ok and seemed to work. Wonder how that could turn out if nothing else......?

Chuck
[Sprint Samsung Galaxy S6] Noxxxious:
The fix is simple, yet all N s6+ phones suffer from it.

PM me for your solution.
[Sprint Samsung Galaxy S6] digitalchaos1980:
Don't tease! I cannot wait. I'm quite curious myself lol :)

Chuck
[Sprint Samsung Galaxy S6] tdhite:
The issue turns out as I surmised -- the property ro.securestorage.support is no longer supported on our device (in fact, apparently all S6 devices). A big thanks to [MENTION=4587002]Noxxxious[/MENTION] for the pointer. Turns out it is the lower level libs to which I was on track to debug, but the pointer saved me a solid couple days of debugging so I have a weekend to play instead of debugging and rebuilding code bases :).

For the wondering eyes, the issue is at the libsecure_storage libraries (which are those I referenced above). Sucking out the strings from the libs and comparing with the Note devices (which apparently don't suffer the ripped out property support), we find this:

S6 secure storage libs:

$ strings lib/libsecure*.so | grep ro.securestorage
.ro.securestorage.version

Note libs:

$ strings lib/libsecure*.so | grep ro.securestorage
.ro.securestorage.version
getprop ro.securestorage_hybrid.support
getprop ro.securestorage_lite.support
[B]getprop ro.securestorage.support[/B]

The same result applies to lib64 (64 bit libraries). So, whether by accident, or by intent -- I have no clue which -- a carrier or manufacture move has been made that limits the ability of we developers to make things work. It will probably get worse with future releases, so one might surmise the day of dev'ing kernels (minimally) and possibly ROMs themselves may be on the way out for Samsung devices. Apparently (per [MENTION=4587002]Noxxxious[/MENTION]), this problem has hit S8 devices as well, if that's an indicator of the future 'lock down' efforts.

Regardless, a kernel update is coming soon that resolves the bluetooth and wifi password store issues (not to mention other things depending on secure storage.

:good:
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=4988866]tdhite[/MENTION] Well this is awesome news!! It definitely looks like you were on the right track with the problem at hand. I do wonder what would have happened had I extracted those libraries from the G920F rom and replaced mine with them. I imagine it wouldn't have been that simple lol. I reckon I will start gearing up for the conversion to Magisk since I assume the new release will be Magisk-only. I need to make sure a couple of my apps will still function afterward since I have some files in the /su/bin and /su/xbin directories. Cannot wait though for the SecureStorage fix! :)

With that said I also want to thank [MENTION=4587002]Noxxxious[/MENTION] for the help with getting us on the right track, thank you very much Man! I do wish I could have helped more because these guys on this site have helped me so much over the years and it would have been nice to give back, but I'm sure there will be other times ahead. Thanks to all you guys who do this for us. I'm good at what I can do with this stuff, but I hate to admit I've never done a kernel. It is something I eventually want to get time to do.

Chuck
[Sprint Samsung Galaxy S6] mahdi72:
if i flash this kernel, Secure Folder and S Health will work?

i have nougat on Galaxy S6. i edited build.prop now s health work but secure folder not.

i heared this kernel can run secure folder but this not for g920p.
[Sprint Samsung Galaxy S6] digitalchaos1980:
This SkyHigh kernel is not yet fixed for SecureStorage but as [MENTION=4988866]tdhite[/MENTION] mentioned a few posts up, the update is coming soon that will fix it all. Hang in there, it is coming! :)

Chuck
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=4988866]tdhite[/MENTION] Sorry to bother you with this as I realize you are probably busy with things, but I just followed your directions for going from the SuperSU kernel to the Magisk kernel and it flashed fine and booted up fine but theres no root access to any of my apps. I opened Magisk Manager like it stated and it prompted me to open Play Store to update but when I click it, Play Store shows the app no longer on there. Did it violate their TOS or something and get taken down? I'm going to try to find a newer version somewhere on the web and see if that does it, but the way the directions stated, I thought I would have root once I booted up initially after flashing the kernel. Thank you in advance for any help or suggestions from you, or anyone else who may reply! If nothing else works then I will restore my Nandroid and keep using SuperSU. :)

Chuck
[Sprint Samsung Galaxy S6] t-bob:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Sprint Samsung Galaxy S6] digitalchaos1980:
Thanks for that, but I was already there and the link to the Magisk Manager takes you to the Play Store where it shows it is not there. But good news, just a moment ago I remembered I had download the newest release of Magisk Manager days ago when it was still on the Play Store and I was able to update the app and now I have root to my apps! I havent granted root to every app as of yet, but so far several of them work fine. Hopefully Google Play will get the manager back soon. Now to finish granting root to the rest of my apps. Thanks again! :)

Chuck
[Sprint Samsung Galaxy S6] tdhite:
Magisk manager was kicked out of the play store. Next update of the kernel is v13 and it installs it all. Just uninstall the magiskmanager app and hang for few hours while I get the update out.
[Sprint Samsung Galaxy S6] digitalchaos1980:
Well shoot, I was already successful in getting it all to work, even my Nethunter and Nexmon stuff works amazingly. But, when the kernel comes then I will just uninstall the manager app. Will that work also?

Chuck
[Sprint Samsung Galaxy S6] tdhite:
Yup. :)

Edit: [MENTION=5382499]digitalchaos1980[/MENTION] -- I altered course. v13 is simply not ready for prime time. It will be one day, but so many things are broken that the kernel needs (e.g., /system/vendor overlay so original library files are left unharmed, post-data-fs script execution, and even service script execution -- all of which are broken in most recent v13 builds).

In the end, this kernel has been about stability on releases and in that vein v12 is stable, v13 is not. So be it -- for those that want to play with v13 you will have to install it after the fact and I will not support failures of the kernel or anything else after that until v13 is released, or at the very least I find a version that I build into the kernel install flash that works.
[Sprint Samsung Galaxy S6] Noxxxious:
Secure folder fix should be done rom side.
[Sprint Samsung Galaxy S6] ChubbbySquish:
Buddy, Magisk Manager got taken down. It's now on XDA instead.

EDIT: My apologies, for some reason the thread opened up last page.