Originally Posted by gooberdude
Well I am using Gnabo Rom V3.0 SE. It has a few tweaks and bugs that are inherent with the Gnabo V8 system. I am able to run it smoothly, and much better than with the KK runner 1.1 kernel it came with. As KK runner had a few issues that were built into its operation that I could not live with. Since I am not a developer I am forced into trouble shooting and tweaking from modding with other ROM components developed by various sources. So many it is hard to keep track, and never was intended to in the first place. Since they for the most part keep ther there work to themselves and wont share in custom ROMs not part of their development. So... I am Frankinstining for my personal use.
Ok, now to answer the best that I can... away from Xposed, as I have had issues wity modules since KK was released on my 2nd Note 8.0, as you can tell with my sig, that I am proud of my 1st Note 8.0. Even though it is JB it is rock solid and a breeze to mess with and is trouble free whith most mods, compared to KK.
Issue number 1... deep sleep can only function with DS battery Saver. Though I did try every revision of your Kernel, I think I or u 427 the early Kernel was able to deep sleep just never solidly looked into it as I had been focused on Miracast. Not sure, but I think reverse engineering the App will point how diverse its calls to deep sleep. Maybe you can inject older style deep sleep function, maybe not. As you are limited by tool chain.
Issue number 2... The Boeffola utility. I know you have no control over it, but it has a timing issue or flushing of registers issue when changing through profiles. This happens randomly with 5.0 on up Kernels. When it does happen lockup or reboots ransomly happen after profile has been set and app closes. Sometimes one will have to clear cache in recovery to allow boot without issues or start the utility before the delayed load to clear the settings. I recommend 35 second delay at the minum.
Issue number 3... Charging is slower with Kernels 5.0 and above. I have thrown the kitchen sink at the issue. What seems to help is using Profile Adjuster as a secondary to the Boeffola utility. Must set a delay so Boeffola finishes clean with loading kernel parameters. Out side of adjusting charging capabilities to 2amps I set my CPU min frequency to 600 for miracast perposess with vaious content being streemed. Though just about every utility has issues properly showing cpu usage without triggering idle jumps. Which is part of how poling and screen writes are handled. It shows for the better programmers over the rest so to speak.
Issue number 4... which is probably ROM related is early call routines during boot fail with Netd. Notice them in logcat.
Issue number 5... I want more from you! Damn you, now I am expecting way too much. Ha!
I admit that most may not have to be so picky with miracast and network connectivity in selecting a kernel. As most newer tech seems to play easier than mixing dinosaurs with chickens. It appears to me the newer and faster kernels are multi-tasking better than older versions. Since I have no idea what can be done to scale background tasks to be equal with forground tasks to assist older revision kernels I am stuck with using your lastest and greatest kernel.
To give example of what I am dealing with...
Most roms have set scan supplicant to 15 in the build.prop.... a big change over the old 150. Donno, if this was a typo that carried over to collaborating developers or a true fix for the kernel they run with. I found 90 to 100 to be my max at home on my old router. Was able to run down to 50 but now with my sysctl.conf file with IVP4 tweaks, 75 is my setting. Seems that lowering cleans up miracast a wee bit.
Though it is the cumilative mix of various network tweaks and kernel settings to allow net streeming and miracast to play well.
Most don't go digging into worst case scenarios but I am forced. So troubleshooting deep into Miracast compatibility with online streeming will always be my priority over games and battery life. Though it goes hand in hand, as miracast tests the full spectrum of kernal operation.
What works well... BBC Iplayer, Xfinty TV, WatchESPN, FoxNow, FSGO, ABC, TV player, All4, and YouTube.
Live Extra seems to have frame skips in 200 to 300ms intervals. Shows up well with scrolling banners at the top or bottom. Though accumulative, will make 1 to 2 frames skip every 1 to 2 seconds. I notice it is inhearant with the player and is being amplified by miracast delay in processing. Miracast will jump frames to keep up with streeming input.
All videos MT2S, AVI, MKV, WMV, MPEG, MP4, and H264 are a breeze. Just my limitations with the streemed content at home. I do have 50mbps but my router does 25 at best with wireless, so my data is fragmented and tablet is not fully opitmized for connectivity. Basically I am optimized to work with a not so good connection. Though with that said, once my router is replaced with new, such issues will be to the way side. Just to see such differences between kernels would be difficult if not impossible to detect depending on their use. Especially seeing what TCP congestion settings has to offer, being strengths in weaknesses.
Originally Posted by gooberdude
Update... I ended up tossing DS Battery Saver, as it broke once I messed with some settings. Plus the app is huge! So I did some snooping and remembered a few tricks. 1st the tried and true Air Plane mode. Yep, it works for all governors.
Later on I will try a S6 trick... flash a stock recovery and clear cache. Will report back once I get it done and tested.
So now I will cotinue to dig deeper into the charging issue. Will be obtaining a new charger and cable soon 24awg high current cables are not the best, until they start making 22awg cables replacing them once a year is good practice.
I can live with air plane mode before turning off the screen if the S6. Edge root fix does not work.
Originally Posted by gooberdude
Ok, found that all Gnabo ROMs have quirks beyond compare as to Xposed. Had done a full wipe and clean install of 3.0 SE, and then loaded your kernel for release, as time permits I will move on and load your Beta versions until sleep breaks again. Not sure if this ROM is touchy with the kernels, as to save data that can't be cleared without wiping, but it is clear from past tests it can go bad from the initial install if rushed. Some times it is smooth on first load, sometimes it locks up and must be shutdown and have the reload done again. This time i waited too long and lost root. Explain that one.
Well sleep works and for using the release version it is the smoothest i have seen it. Maybe it is a trial and error thing for me on such a ROM. But it is the only rom that i can find that has a fully functional miracast with custom kernel. All the others fail or are too buggy.
Though i am heavly dependant on xposed modules, so it could be just how i have them load and their settings. Still have a random issue with the Boeffola Utiltiy, that i may have cleared up by making sure here is a good delay to wait for boot to finish completly for the home screen and background processes. I may keep it at 60 seconds for good measure.
Now i can only hope that the next utility update has 2.0 amp charge capability. As it seems to be one of the best utilities out there for kernels.
ok now finally i have some time to "answer" your questions: i just have to state here some things: i know u rely on that rom but Boeffla Kernels for < CM12.1 are EOL and were made for stock roms mainly, your used rom is a PORT (!) and u are using XPOSED there actually is nothing wrong with that i used it too without problems but on stock roms (!). But i think u are aware of possible xposed troubles
. sooo yes u would really have to search in the rom area, i cannot help here much also not with your "not sleeping issue" as this is a typical rom issue
About the 2A charging current setting: this actually would be a kernel change not a app change so it will not come per update from lord boeffla. and before the question pops up: i stayed away from that high setting for security reasons, i think a max of 1,8A is enough, so sry that will happen neither
as far as i can read from your reports, u already fixed/workarounded most of your problems
and yes boot delaying in boeffla app often helps on stock TW roms, i had that freezing problems too from time to time (very rarely) but never was able to find what exactly is causing it. now this is a obsolete bug as the kernels are EOL and i never had that on CM12.1. so i stopped investigating. but anyway keep the app updated, lord boeffla constantly improves it, next update comes soon and it includes improvements regarding applying stuff after boot, maybe it helps