[Samsung Galaxy Note 8 ROMs, Kernels, Recoveries, &] Kamikaze_Ice:
The video was not just to demonstrate the rotation kickback sillything, but also to show the notification/toast bubble that always pops up about "IronControl Free was granted Superuser rights". Any thoughts on that?

And thanks for the link. I'll see if I can understand how it works and give it "the old college try" when I have extra free time.

---

Yes, I've done that.

Does not work for me at all, and there is no difference when using either of the SystemUI options.

---

Yes, I've been using your Kernel on other roms prior to great effect.

I was directing one part of that post towards you: I was just saying that picking up one of the cheap DeX alternatives is a great idea for development purposes (checking for any major issues with your kernel and rom development and debugging without complete reliance on user feedback/reports. Samsung asks way to much for their DeX dock so I shared the cheap one I use ($10 when I got it on sale, and other similar devices go on sale often).

The part about a patched kernel being required was for others reading the thread. I can't find that post I saw for a device that has or emulates the chip in Samsung's DeX dock, which does not require a patched kernel and thus tripping Knox.

---

I didn't explain it very well, but I tried to explain what and where I noticed this, and the steps I took to reach my solution = Don't set "The intensity of the darkening filter" to "0".

I assumed when you were customizing rom control that you were assigning a value range to the rom control interface elements to be compatible with the full range of what the mod itself allows--Basically rom control acting as a front end to edit config files of mods. With this assumption, I figured all you had to do was change something in Rom control so the slider would go from 1-200 instead of 0-200 (with no actual changes to the functionality of Rom control or the mod).

---

****typing this out gave me an idea, see bottom of post.****

Regarding CSCs, I'd like to add to this (just to be safe):

Note: I'm not satisfied with what I've written below, I think I'm making this sound worse than it really is. Sorry.

The unencrypted CSC files I pulled from the N950U1 AT&T firmware have some lines specifically for Snapdragon, naturally, as that's the only variant sold my carriers in the USA.

I've not tried EVERY firmware, but all others so far have been encrypted so we can't see what is in the cscfeatures.xml files but it's safe to assume that there are lines for exynos models from carriers who sell them.

And to make things slightly more complicated, I've seen TWO different file structures (T-Mobile is Snapdragon, and has same "omc" layout as stock N950N from Korea variants.)

If you've looked at the T-mobile carrier aggregation/CSC threads there are a few of us who have had problems with restoring stock firmware CSC (even using Odin and EFS clear/partition wipes due to ramdisk always having a "last known good" backup it wants to use).

There may be remnants of any user flashed CSCs, which is a problem for people who want to keep the stock recovery for Knox.

With a clean, total wipe, repartitioned with official firmware, the next boot the phone tries to apply a system update which fails at 32% (it looks for the file \cache\recovery\sec_omc.zip (contents are CSC files) but fails find it for some reason. Every time you enter stock recovery it will fail to find it until it is deleted.

And yes this file DOES exist and can be manually flashed via TWRP, but you're still left with remnants of the previous CSC.

Manually flashing then re-flashing stock firmware doesn't work as expected (phone sees the same csc and basically reuses what's on the ramdisk and not what was flashed, meaning any remnant files never get deleted.

Example of what I attempted to describe above (sorry, I'm not good at putting my thoughts into words):

I'm on AT&T with a Korean N950N. I used Tkkg1994's CSC Selection tool (modified for Note 8 support as per THIS post). When I do a complete wipe and return to stock firmware via Odin, the stock recovery will still say I have an AT&T csc even when there is nothing but Korean CSCs in \system\omc\.

If a CSC file DID cause problems for someone they may need to do more than simply reflash a stock/backup/different CSC package.

This poses a problem for those of you keeping Knox

*Please let me know if this truly is not a problem for Knox keepers or Snapdragon users, as I can't exactly check this myself anymore.

*********

I just realized I've only seen ONE firmware that has a "csc" layout, and it was the N950U1 AT&T firmware files, which

was unencrypted

. What do I mean by this?

What I call a "csc" layout = \system\csc\<carrier code>\system\csc\cscfeature.xml

What I call an "omc" layout = \system\omc\<carrier code>\cscfeature.xml

As much as I would like to, I simply cannot download a ton of firmware files just to check the CSC firmware. So I'd like to ask, does anyone have a "csc" layout on their phone (Snapdragon or Exynos)? If so, could you share what firmware you have? Or better yet check your own cscfeature.xml for encryption (open it as a text file). If you can read it, please share that and your cscfeature_network.xml with us.