rockerdudelive wrote:First off I'm new to the note 3 and I love all the options we have for it. But I'm having a problem with the screen not turning on after it turns off. Sometimes it takes a looong time to turn on and sometimes it doesn't come on and I'll have to pull the battery.
I was wondering if anyone knew a possible solution to this? I have been messing with various settings over the last few days and I was wondering if anyone knew the most likely cause of this? I had my touchboost turned down to 300mhz so i turned it up and it has still had the same results. Everything else is mostly on stock except for I disabled mp decision for intelliplug (all stock settings in aroma i didn't mess with them) and intellithermal (again, stock)
are those the reason to blame?
Nope, touchboost onlt has effects when the device is on and acrively used.
rockerdudelive wrote:I'm also removing trickster and faux123 so they don't conflict with your settings. I Haven't tried that yet so thats my next try. I did search this post where I can find the file in the system/etc to see the settings, I just like to have a "kernel tuner" type app to see my current standings, so removing them was my last ditch effort. I noticed faux123 had some settings that were strange. Like it said touchboost was disabled (when I'm sure it is enabled because I have no set at boot settings on faux123) so maybe that app is to blame.
I have fauxclock on mine, no issues as long as you don't tick set on boot, as then you may get either what you set in faux or in Aroma (the last tomapply will win, script or fauxclock).
Also there is freq. touchboost (by Samsung which I just made customizable) and touchboost for intelliplug, I think you're mixing them up
![Wink ;)](./images/smilies/icon_e_wink.gif)
rockerdudelive wrote:Does anyone have any suggestions for why the screen won't turn on sometimes? Or for what tuning app plays nice with this kernel? does yank use anything in specific or does he just flash options in aroma and leave it? Thanks all you guys rock!
You can try setting CPU screen off max freq higher.
I just use Aroma, as said above, but run fauxclock to check settings.
rockerdudelive wrote:edit: I also followed the instructions in the post right above me about when to reboot in twrp and not using the aroma reboot option.
This is very important, else NO settings will be applied from what you chose in Aroma, this was not the case when using CWM and only applies to TWRP.
JP.
Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.5 kernel.