[One (M7) Original Android Development] Rad ryan:
LOL :D

Agreed. And

PRESERVATIVE PRESERVATIVE PRESERVATIVE PRESERVATIVE PRESERVATIVE :D :D :D :D

Oh yeah, I almost forgot... PRESERVATIVE :D

Did you set Android Tuner to apply the settings on boot or init.d? That results in what you are experiencing. It's not bc of the mod, it happened to me before. Instead you should save a profile with the settings you want to apply and then do it manually after reboot by loading the profile. I think I know why they are not being set by init.d script on boot (thanks poondog). For AT not starting, clear it's data and cache. If it still is not starting then Uninstall and reinstall it. If you did set AT to apply settings at boot through init.d then go to system ect init.d and find a file named 99_cpu or 01_cpu or something like that and delete it.

OR... The easiest way would be to use your nandroid, especially considering your last post, if there isn't anything that has changed that you wouldn't want to lose by reverting to your nandroid. Also I wrote the response to your last post before I wrote this paragraph bc all of my replies above the last one I actually wrote earlier but I guess it didn't go through. Thank you "Type Machine" (a great app) , it saved me from having to retype all the replies again or not have posted them at all. :)

Thanks

Ok thanks. Did you reset your gsam estimates so that your times are not mixed with the ones you had bf? It will take at least a day or so for the new settings to settle in. As of now, I'm saving anywhere from 3-6%/hr :D If you still feel it's a little sluggish you can raise the down differential to 10 lower, Sampling rate to 20000, and if still want more speed lower the up thresholds by 5 each. If still want more put in the stock settings I sent you. Alternatively, you could keep pnpmgr on and it will help with the smoothness of us. :D I'll send you a new zip that will leave pnpmgr intact, and it will help me too bc I haven't really tested with pnpmgr on that much. :) After another day or so I'll make you one with a little more muscle if you want :)

Can you post a logcat for me (or just keep reading and try what I wrote below) ? Start it when you try to open the app that's giving problems and then stop it right after. You can also do the screen recorder and post a link to it if you want. The mod shouldn't be affecting any of the things your having problems with. I use xposed framework and xMultiWindow and they both work fine for me. I'll come up with a different way to install it for you and then I'll pm the necessary files and directions in a little bit (probably between 20min - 30min).If I had to guess off the top of my head, I would say that something got out of whack during flashing, which happens to everyone from time to time.

The easy way which may fix is to Uninstall xposed through the xposed installer. After it's uninstalled, wipe the data of apps giving you problems (unless it takes a while for you to set them back up bc wiping the problem apps data is like an extra step that may or may not help). Then go to recovery and wipe the dalvik cache and cache. Reboot your phone, after its booted go and reinstall xposed from the xposed installer and reboot. If it still doesn't activate it could be a permissions problem, and if it is you can do fix permissions in TWRP. It's under advanced tab/menu/button. You can do the fix permissions at the same time you wipe the caches if you want, but I put it as an extra step at end bc it may not be necessary so it's up to you as to when/if you do fix permissions. :)

If that fails, or if you just don't want to do that, you can go recovery wipe the dalvik cache and cache and then dirty flash your ROM (meaning flash without wiping data). Reboot phone and then install xposed and flash kangaroo kernel. :)

The first option seems longer but takes considerably less time than doing dirty flash, ect.

PS Did you get the Android Tuner problem sorted out? It could be the reason for your troubles also bc I'm thinking that you didn't have any issues until AT problem started. :( Rule of thumb: never use Android Tuner to set any cpu settings at "boot", it will cause issues galore, but I think the init.d option works mostly. I personally don't set any cpu options on boot/init.d with AT, other than that it's a great app.

---------- Post added at 03:46 PM ---------- Previous post was at 03:31 PM ----------

Son of a B!+ch that was a loooooonnnnngggggg post :D