[Galaxy Note II Original Android Development] Pafcholini:
Recommended settings & FAQ

Balance between performance and battery

I'm using Synapse (highly recommended)

Read ahead buffer: 1024

IO scheduler: row or zen

Frequency Lock: ON

CPU min freq: 200MHz

CPU max freq: 1600MHz for battery / 1800-1920MHz for performance

CPU governor: Lulzactiveq for both

CPU voltage: -50uV or -100uV (

Be careful!! If you low voltages much you can get boot loop or battery drain

.)

CPU idle Mode: AFTR+LPA

TCP: westwood for both

Dynamic FSYNC: ON

F.A.Q

Note/Tip: Nadians if there is nything that is missing please PM me I'll add it and in future if you feel anything needs to be added please tag me in that post I shall update it.

Use Synapse Trickster Mod, Devil Tools or Devil Kernel Manager

In case you loose root just flash Super SU

at the beginning of the second post.

[youtube]reAE4C80EJk[/youtube]

[youtube]dCgx_tAKMc8[/youtube] thanks to [MENTION=3892104]klurosu[/MENTION]

You can use Synapse, trickster mod, devil tools or Devil Kernel Manager

Go to play store and Reinstall affected app again and do a reboot, done. Don't mess/uninstall anything.

OR

If you have titanium backup just restore specific affected app from it.and reboot your device

Thanks to [MENTION=4282282]optimusPRIME[/MENTION]

Yes, sometimes pegasusq can cause this.

Switch your governor to either lukzactiveq or Zzmove to have good battery and no skipping music along with smooth performance.

I'll give the reason as to why this happens - Pegasusq is a governor designed to handle multicore systems only and it does an efficient job at the smoothness and battery life with those. But the problem is that it isn't designed to optimize and ramp up the single core systems properly so it tries to push the remaining core into deep sleep, which causes occasional stutter in many background tasks like music. Now for that you'll need a governor which can handle multicore and single core systems at the same time and efficiently, while many governors can do the job, but none is as smooth and optimized as pegasusq in a multicore system. Ondemand is suggested by many for the skipping music problem, but the problem with ondemand is that it was made for single to dual core systems only and this leads to lag and slower ramping of frequencies in a multicore system, but provides a battery life comparable to pegasusq.

While all of this might cause confusion for which governor to choose, lukzactiveq is optimized for more battery but smoothness at same time, and ramps up sliwer but preserves battery life when screen is on; while Zzmove ramps quickly and gives a more snappy experience, the battery life a a bit less.

So choose what you want and enjoy [MENTION=5697564]KNIGHT97[/MENTION] thanks for the detailed explanation.

It's a feature which will allow you to wake your device when it gets locked after screen timeout.

Try this unlock your device wait for it to auto lock not just tap on display and your device will wakeup no need to push the unlock key.

Fix is: flash your desire rom...take a pic with your camera and a video...then reboot in recovery mode and install nadia kernel.

Thanks to [MENTION=3892104]klurosu[/MENTION]

Open trickster mod go to 4th screen. There you will find section mpu voltages. There you can change it. [MENTION=5194609]mohit141785[/MENTION]

Also try with different governors and I/O schedulers. Increase the SD cache to 1024 or 2048 (more than that has no effect and is wasted) and then try, it can sometimes give higher score in the storage I/O, which increases the total score too [MENTION=5697564]KNIGHT97[/MENTION] thanks for the detailed explanation.

Go to /system/etc/init.d using any root based file manager and delete.

Note: There is an important one related to superSU and if you remove it by mistake you're gonna have trouble with root permissions. [MENTION=5697564]KNIGHT97[/MENTION]

Use Wanam Xposed and turn off DVFS or user DVFS Module(standalone) (dynamic voltage and frequency scaling), this feature was kept in touchwiz for benchmark boosting purposes and will confkict with any undervolting and custom governors because it scales the voltages and frequency on regular intervals and is framework integrated, so gets a higher priority than kernel based voltage and scaling controls.

For people who don't know what is DVFS please refer Wikipedia.

check [MENTION=2596418]mattiadj[/MENTION] thread for more details. [MENTION=3562083]wanam[/MENTION] [MENTION=2596418]mattiadj[/MENTION] [MENTION=5697564]KNIGHT97[/MENTION]

Yes, you can check [MENTION=2473722]mat9v[/MENTION] thread

First make sure you have set on boot and set on boot notification enabled. If after a reboot you see this notification

Then set on boot was run.

You might have scripts, other apps, or ROM settings override Synapse settings. In this case Set on boot delay might help if it's for settings at boot otherwise you need to track down and disable the app/ROM settings

A1: If you're using chainsdd's superuser switch to koush's superuser or SuperSU.

A2: Make sure you are not using another tweaking app or your ROM has setting that overrides our boot configuration. In that case, “Set-On-Boot delay” feature might help.

Otherwise or if you still have problem, see below

A3: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel service that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues. Unfortunately, it can't be fixed from app side.

A4: DON'T use a reboot app, they effectively force reboot your phone like a system crashes. If you really have to use it, then do it after the apply grace period or disable grace period by setting it to 0.

A5: You might have scripts, other apps, or ROM settings override Trickster MOD settings. In this case Set on boot delay might help.

A6: Don't force close the app (e.g. in Android Settings). It puts the app in a state that it can't start at boot until user starts the app normally again.

A7: Don't use app like Greenifier to greenify Trickster MOD. Doing so will prevent it to run at boot to apply Set-On-Boot.

A8: The Android BOOT_COMPLETED broadcast might be borked because of theme, mods, or after a few dirty flash. In this case reinstall ROM with a data wipe is needed. This solution is confirmed by our users and as this issue is because of deteriorating ROM with ORD, nothing we can do about it on our side.

A9: If it still doesn't work, please do in in app bug report using the option in the app menu right after Set on boot was run. You can enable Set on boot notification to know that.

Source: Trickster MOD FAQ.

Lux Auto Brightness

Here

By default Android logger is disable. Go to Synapse > CPU DRIVERS and enable Logger Mode.