[Galaxy Note 4 Android Development (Exynos)] Sapphire999:
Sure, but I'll be told again being the last asshole reporting bugs here. Problem is, that OP(please stop telling me, that I'm an idiot, I don't argue, I just report bugs and try to help), that OP mixed conflicting packages in his ROM and paid not much attention to it, it seems.

So, how to get Samsung stock player working(song scrolling + GN4 similar SoundAlive working, unfortunally SoundAlive+ etc not working, but at least get beloved SoundAlive back and stock player working with no bugs and crashes).

So, let's go. Ah, one last off topic, if I'm so hated here for giving advices, OP tell me to stop commenting and I'll go away simply. So let's go.

0) Get "System app remover from google playmarket(since you need to delete system apps). This app is recommended, since you can easily restore deleted apps. They are simply moved into trashcan. You can restore them at any time.

1) You need to delete KNOX apps. At least 5 of them exist(see me previous posts you'll see APK list). Also reboot device and wipe cache/dalvik, cauze knox remains there still).

2) Now, since OP included GoogyMax kernel, but seems didn't know about it's mixer conflicting with Samsung's sound system, open GoogyTweaks, go to Sound section(tab) and UNCKECK EVERY CHECKBOX!!! If any of it checked, then kernel level mixer used and making sound system locked causing high-level apps(like SoundAlive) to crash. You'll need to reboot again(no wipes needed this time).

3) Now. There are more conflicting packages in this ROM. You'll have to delete them too.

3.1) There's package called "SplitSoundService". DELETE it. It's incompatible with SoundAlive. Have no idea what it does, but it makes SoundAlive to crash. Reboot device and try SoundAlive. If it works fine and you hear differences after changing SoundAlive settings, try different ones, try switching songs etc. If no crash and SoundAlive working - you're done, ignore next step. If crashes, use 3.2 too.

3.2) Sorry, I use Russian language, so forgive me, if pack name isn't correct, since it's marked in Russian for me, so I will translate. In translation to English it will sound something like "Optimize sound" or something similar. I guess it's something similar to AdaptSound of GN4. Maybe it's compatible, maybe not. Don't know. Delete it only in case you fail making SoundAlive work with previous step.

4) You're done. Enjoy. SoundAlive and Samsung's stock player(if KNOX deleted now) should work brilliant.

Now for the ones who want to get Samsung's original PowerManagement back(to see apps using battery, graphs, time running on battery and approx remained), then delete package "SmartManager". Since it has antivirus etc on board, I don't like it and it's resource expensive(IMO). Fast charging is unswitchable, sorry.

If anyone or OP are angry about this post - report abuse to moderator or message me, I'll delete it on my own.

If it helped somehow to someone - enjoy. If not, then sorry, then it worked only for me for some reason. As for me, I got fully functional Samsung's player and SoundAlive. (SoundAlive+ etc, which is some extra not regular for GN4, still don't work). There are more these conflicting packages I guess, but I'll be told being "to calm down" and to stop sending bug reports.

So no matter, if it helped - enjoy. What's up to OP - I didn't share any part of your work, so I didn't break any point of agreement. You're free to use or ignore my advices and bug reports. With all respect.

Goodnight, everyone!

---------- Post added at 03:51 AM ---------- Previous post was at 03:48 AM ----------

If still fails to run SoundAlive normally, I just found out, that I also deleted "AudioConnectionService". Not sure, if it counts. And I didn't check if some of this packs can coexist with SoundAlive without making it die :) So, if you have time, can use different combinations to find exact package that makes SoundAlive die.

No, it's not only kernel job. ROM contains KNOX apks that can be deleted without any harm to ROM device or system. But for unknown reason, OP didn't do it. Maybe simply forgotten. Who knows.