yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] ticktock666:
great performance so far, just wondering how can I change the profiles in zzmove ?

it shows "profile list", "profile" and "profile number" at the bottom, I can't seem to be able to click on profile number being always a zero, so how can I change that ? I want to try #6 but can't :s, hopefully this is not some silly question with me missing the obvious.
[Galaxy Note II Original Android Development] KNIGHT97:
Type a profile number 5-6 times

Close synapse

Open synapse

Profile set
[Galaxy Note II Original Android Development] glynnpel:
This kernel just keeps getting better and better. Been using r5 since release and not a single hiccups. Synapse works really good.
[Galaxy Note II Original Android Development] Austtin:
Well said. I pm to pafcho because I felt really sorry about all this. And I apologize if something was missunderstood. I only gave my feedback. Not in a demanding way only on a constructive way. I really want to help, not only me if not other. That's the beautiful part of it, help between us and people who visit this forum.

I'm on R4 again and everything is ok regarding to the undervolting I used to use in nadia kernel. And once again sorry guys :(

---------- Post added at 04:45 AM ---------- Previous post was at 04:29 AM ----------

Guys i found something. if you flash mat9v script (any version) synapse stops working, lol. Btw I think synapse is a super complete kernel tool. There's so many features you can manage. Really good job with this! Time ago i saw a couple of kernels handling Undercloking to 100mhz, is it possible? Just saying...

And how can I know if my phone support 2ghz? It has asv1 chip. It's not recommended to daily usage right? Thanks! Keep the good working mates
[Galaxy Note II Original Android Development] Austtin:
Yes in r4 I can reach that values.

-75mv at all levels and the values listed below

200mhz》775

300》800

400》825

500》850

It has good performance and battery.

Btw if for some reason I decide to move to r5 what cfg is better for performance and saving some battery too?
[Galaxy Note II Original Android Development] myaslioglu:
C'mon please.. i of course did that. There should be sth else with my rom or sth. I think i need a clean flash.

Which i am reluctant to do.. but will inform you when i did.
[Galaxy Note II Original Android Development] Pablo87:
Why I have this error?
[Galaxy Note II Original Android Development] KNIGHT97:
Use android tuner instead of that......synapse has a bit of problem with voltage settings....it shall be fixed soon
[Galaxy Note II Original Android Development] klurosu:
:good::good::good::good::good::good::good::good::good:

Impressive.

very very thank you buddy

---------- Post added at 11:40 AM ---------- Previous post was at 11:36 AM ----------

Dude give us a snapshot of your current scripts in init.d so we can help you as you deserve.

otherwise we will continue talking without knowing
[Galaxy Note II Original Android Development] myaslioglu:
Well as aforementioned nothing to impede..

This is before flash..

I also tried without zipalign if you may suggest to delete it..

Also without supersu and with it..
[Galaxy Note II Original Android Development] klurosu:
Ok, much better with pics.

Seems like your init.d folder is nice and clean so...enter in recovery, wipe dalvik & cache and flash r4 method must work...mmm

keep us posted
[Galaxy Note II Original Android Development] myaslioglu:
First r4 then r5 ? Will now try.

Edit 1:

Nope still no go.. soft and hard buttons make the device vibrate 3 short 1 long..

r4 does not boot either btw.

well I will try with twrp

Edit 2:

No go with twrp either.

stock kernel does not boot also.

what may he have changed that I cannot get another kernel?

Maybe I should ask him tho..
[Galaxy Note II Original Android Development] dollyaja:
Try wipe system-flash ur current rom ( if custom) - wipe cache dalvik - flash kernel- reboot
[Galaxy Note II Original Android Development] takkk7:
I think the problem lands in Agni Kernel , look here for a possible solution:

http://xdaforums.com/showpost.php?p=53800252&postcount=2824
[Galaxy Note II Original Android Development] myaslioglu:
Thank you very much mate! Good clue!

Formatting /preload solved the issue :)

Now no problem.. OP may be noted about this, because once you flash agni you have preload swap
[Galaxy Note II Original Android Development] Pafcholini:
I need to fix some small issues in synapse. Also I'll try to provide some good configs for wolson sound, etc.

Regards, Paf.
[Galaxy Note II Original Android Development] tyagi2014:
N some configs for a blend of performance and battery like u did for trickstermod in the previous version, if possible. Will be highly appreciated.

M still using the same values, plz lemme know if i need to change anything on rhis kernel.
[Galaxy Note II Original Android Development] KNIGHT97:
And fir the advanced users (with text reading that, in red color) some ABB settings would be good too ;)
[Galaxy Note II Original Android Development] mohit141785:
Knight just open any of mat9v s script as a text file and look for abb. It will give you an idea.
[Galaxy Note II Original Android Development] KNIGHT97:
I know about abb usage...but just wanted a bit of some values to test, just sone recommended by OP, like for initial testing and usage. ...rest I can do on my own
[Galaxy Note II Original Android Development] mohit141785:
Yup knight I am sure you do that's why I said to look into mats script. It contains some value that he chose . And by comparing the diff values the different versions of his script contains we can get some idea about it.

Cheers
[Galaxy Note II Original Android Development] mat9v:
To make it short. There are no differences between ABB values in my OC scripts: they are 800, 1000, 1100 and 800 for slices 1-4 respectively. That is because I have no time to test all the additional variables of power use and from Samsung documentation it's easy to find that above 1200Mhz there is no advantage in keeping ABB value high. Body Bias is designed to minimize static power leakage and that happens the most at low frequencies. It's like that:

- when cpu is idle it automatically decrease frequency to minimum to lower power use

- at this point the power used by cpu is mostly wasted by static leakage

- ABB is designed to eliminate it on very deep hardware level by manipulating body voltage of the transistor

- when we give something for cpu to do it uses power differently - more of it is used by actual data processing

- the higher the frequency, the higher the ratio of power used by processing vs power lost due to static leakage

- we must remember that ABB also uses power to counteract the leakage of transistors

- at some point the power savings from counteracting leakage are equal to power losses due to applying additional voltage to transistor body

- from Samsung documents that happens around 1200Mhz point

We could ask Samsung why isn't the default configuration (which is 750mV across all frequencies) tuned the way some of us do? The answer is that every chip is different and Samsung probably has no time to test the chips individually. If that was not the case, then every chip would come with it's own voltage profile and we could not undervolt at all.

Now, I'm thinking about slightly modifying ABB slices to better account for this behavior but for that I need some volunteers to gather some data and test stability and power savings of different configurations. Please PM me if anyone is interested.
[Galaxy Note II Original Android Development] ticktock666:
anyone having stuttering in audio ? the only gov that works fine for me is lulzq, all profiles from zzmove cause stuttering, when all other settings remain unchanged
[Galaxy Note II Original Android Development] klurosu:
No stuttering in audio confirmed (in my N7100) with:

Lulzactive, zen, AFTR+LPA and -25 UV

Works like a charm :good:

edit: Must say that i delete the old trickster apk nad only use synapse apk
[Galaxy Note II Original Android Development] paulove:
Removing trickster apk and use synapse like you. My phone got a lot less laggy and no more random reboots.
[Galaxy Note II Original Android Development] klurosu:
Wich governor (and settings) you use?

greetings
[Galaxy Note II Original Android Development] paulove:
I have only changed governor to Lulzactive.
[Galaxy Note II Original Android Development] klurosu:
Pleas give me 5m... i'm uploading a simple video-tutorial of synapse and r5 settings.

thx
[Galaxy Note II Original Android Development] klurosu:
Best setup config for Nadia Kernel R5 (Synapse method)

Please, unninstall Trickster apk first:

(subtitles in spanish/english)

[YOUTUBE]reAE4C80EJk[/YOUTUBE]

P.S. Very thx to Pafcholini

EDIT: (thx KNIGHT97)

In Wolfson, enabling DAC direct and FLL tuning can save some battery during audio playback and also reduce distrotions on high volumes, music can be made clearer at the expense of just a bit more battery life usage (still less than DAC direct off) by turning on 128x oversampling.
[Galaxy Note II Original Android Development] KNIGHT97:
Just a small tip but,

In Wolfson, enabling DAC direct and FLL tuning can save some battery during audio playback and also reduce distrotions on high volumes, music can be made clearer at the expense of just a bit more battery life usage (still less than DAC direct off) by turning on 128x oversampling.

And btw, quite nice video and great efforts, many of the configs you showed there, even I'm using and they really wornk great ;)
[Galaxy Note II Original Android Development] klurosu:
Very thx for the intel buddy.

Added to the youtube video-tutorial.

p.s. you rocks dude!
[Galaxy Note II Original Android Development] ticktock666:
Lulzq & sio (same as mat9v choice in his scripts), but if I change to zzmove the stuttering starts, and also happens with pegsus gov.

also, synapse shows an update from the play store, should we go for it ? or is the version included with the kernel heavily modified ?
[Galaxy Note II Original Android Development] klurosu:
At present day...lulzactiveq is the best choice for our n7100 :good:
[Galaxy Note II Original Android Development] KNIGHT97:
Synaps can't be heavily modified, it just acts as a GUI to the kernel itself if the right mapping to certain features is detected and UCI support if present in kernel (advanced linux stuff). So yeah, update the synapse without worrying.

And for the stuttering, you have a choice of different profiles in Zzmove which you can try (by changing the profile number from 0 to any other, following the numbers mention just 2-3 lines above)

And explanation for pegasusq stuttering is goven in the FAQ
[Galaxy Note II Original Android Development] ph03n!x:
Didn't want to spam this thread with longish posts and then a ton of questions, so posted this in the general section - hope it helps :)
[Galaxy Note II Original Android Development] KNIGHT97:
Good clarification.

Will include that in my signature and recommend to people wanting to learn advanced kernel tuning.

A great thanks for clear writeup.

While I understand much if it, I'm not good at presenting things, and you wrote the things I wanted to speak, plus some more, so yeah a thousand thanks for that.

Really great guide.

---------- Post added at 12:35 AM ---------- Previous post was at 12:07 AM ----------

To all the users -

Kindly do this once -

1) using synapse change governor to zzmove (you'll notice that you can't use any profiles)

2) Navigate to /sys/devices/cpu/cpufreq/Zzmove (hidden folder, make a search in ES or root browser for Cpufreq once in /devices folder)

3) scroll down and set the permissions of 'profile' and 'sampling_rate_current' to RW-R-R.

This'll allow you to use the Zzmove profiles normally.

Tested and Confirmed by me and [MENTION=4824728]Pafcholini[/MENTION]
[Galaxy Note II Original Android Development] SaschaHa:
R5 does not work 4 me. Device will not boot after flashing. Ditto Note 3 5+, used latest Agni kernel before tried using this one :(

Does this kernel support sixaxis controllers? Is the only reason 4 me to go away from Agni
[Galaxy Note II Original Android Development] myaslioglu:
Use philz.. turn off preloadswap from agni tool. Then reboot to recovery. Format /preload

Flash kernel r5..

Wipe dalvik and cache
[Galaxy Note II Original Android Development] hamer221:
This kernel gives me best battery life I have ever had. Congratulations to the developer, amazing work.
[Galaxy Note II Original Android Development] rapboy91:
With which configuration?
[Galaxy Note II Original Android Development] tyagi2014:
Thanks mate,

I never altered the usb charging values before, although the phone is charging faster now, just wanted to know if there is a possible threat of altering it? Also, what is the difference between row and zen? I was using row before n now after watching ur video changed to zen.... What difference should i be looking at using the two?

[MENTION=5697564]KNIGHT97[/MENTION] any idea mate?
[Galaxy Note II Original Android Development] hamer221:
Luzactive, zen and after + lpa
[Galaxy Note II Original Android Development] klurosu:
:good::good::good::good::good::good::good::good::good:
[Galaxy Note II Original Android Development] ticktock666:
folder cpufreq does not exist ? is this because of a bad flash ?
[Galaxy Note II Original Android Development] Pafcholini:
R5.1 is coming. Is small update fixing some issues.
[Galaxy Note II Original Android Development] gshahrawat:
And I'm waiting!!!!:D
[Galaxy Note II Original Android Development] ph03n!x:
Never knew r5 had any issues, been using it since the the 4th of July :)
[Galaxy Note II Original Android Development] KNIGHT97:
It is a hidden folder, once you navigat to /sys/devices just tap search button and search for cpufreq 2 folders should show up, one of them will have a folder named Zzmove, the files for permssions correction are in there.

---------- Post added at 11:05 PM ---------- Previous post was at 11:00 PM ----------

A bit of annoyances in synapse, 2 files responsible for the Zzmove profiles didn't have correct permissions and also touchboost was usable but synapse showed error, same was with undervolting (though for some users only) where each step would just apply random voltages on selection of different values.

So the permssions have been corrected and much is working now.
[Galaxy Note II Original Android Development] tyagi2014:
Anybody?
[Galaxy Note II Original Android Development] KNIGHT97:
Row provides a higher priority to read task as compared to write tasks, so expect fast read and slow write speed.

Zen schedules the child process to the main process and suspends others before deep sleep state, priority for write is higher and read is just a bit lower.
[Galaxy Note II Original Android Development] Dbj.Dhaval:
Well I have few questions

1. Should I flash r5 normally or clear cache? (I am already using r4)

2.before flashing r5 should I delete mat9v scripts from /etc/int.d i. e normal delete or flash remove zip??
[Galaxy Note II Original Android Development] Pafcholini:
1. Delete data of trickster mod.

2. Delete trickster mod apk

3. Delete mat9v scripts

4. Flash the r5 ( r5.1 in few hours)

5. If everything goes well flash your favorite mat9v script.
[Galaxy Note II Original Android Development] aukhan:
Mine is also same :)) cheers

Team Emotroid.

Rom: Emotion Revolution 7.0
[Galaxy Note II Original Android Development] jallenhayslett:
Is f2fs support working properly yet?
[Galaxy Note II Original Android Development] Pafcholini:
Not yet, this days I'll work around f2fs.
[Galaxy Note II Original Android Development] James62370:
Thanks so much for this kernel. I have the t-mobile variant sgh-t889, after flashing this kernel I lose baseband. Any one get this working on the t-mobile note 2?
[Galaxy Note II Original Android Development] dollyaja:
I think its only for N7100
[Galaxy Note II Original Android Development] James62370:
Oh... that's too bad, it seem to run very smooth. Would have love to be able to test it a bit longer. Appreciate your reply.
[Galaxy Note II Original Android Development] aukhan:
********Small update*********

July- 09 -2014 nightly r5.1

Fixed touchboost frequency in synapse.

Fixed zzmoove permissions

Fixed uV Issue faced by few users.

Current Versions:

r5.1 Media Fire

Note:

Dirty Flash Over V5.

----------------------------------------------------------------------------------------------------------------------------------------
​

***Updated FAQ***

​

Note:

ABB shouldn't be used unless the user knows what it is and what different values can do, becuase many would like experiemnting with it and do some crazy stuff. When testing UV and ABB, turn multicore power saving to extreme so that synapse is using only 1 core and thus single core test can be done, when fully stable continue to moderate and then you are able to test 2 cores, when fully stable and near to the single core stability values, turn to performance and repeat make sure values don't deviate much.

This will ensure much stable device amd high battery life.

P.S. - ONLY FOR ADVANCED USERS.

Thanks for the info @KNIGHT97

1. Delete data of trickster mod.

2. Delete trickster mod apk

3. Delete mat9v scripts

4. Flash the r5.1

5. If everything goes well flash your favorite mat9v script.

http://xdaforums.com/galaxy-note-2/general/undervolting-abb-to-t2808368

If coming from Agni follol these steps.

Use philz turn off preloadswap from agni tool.

Then reboot to recovery. Format /preload

Flash kernel r5.

Wipe dalvik and cache

Trickster Mod can be deleted.

[MENTION=4824728]Pafcholini[/MENTION] updated on post#2
[Galaxy Note II Original Android Development] dollyaja:
Is the script necessary to flash after kernel,or just the kernel itself?
[Galaxy Note II Original Android Development] aukhan:
Just the Kernel, Script is Optional
[Galaxy Note II Original Android Development] KNIGHT97:
[MENTION=5132493]aukhan[/MENTION] do mention this -

When testing UV and ABB, turn multicore power saving to extreme so that synapse is using only 1 core and thus single core test can be done, when fully stable continue to moderate and then you are able to test 2 cores, when fully stable and near to the single core stability values, turn to performance and repeat make sure values don't deviate much.

This will ensure much stable device amd high battery life.

P.S. - ONLY FOR ADVANCED USERS
[Galaxy Note II Original Android Development] aukhan:
[MENTION=5697564]KNIGHT97[/MENTION], [MENTION=5194609]mohit141785[/MENTION]

As reported earlier Enabler and Disable logger is by default taking Enabled even you select Disabled and apply settings and reopen it still shows Enabled.

In this case select Disabled and apply settings.

Using Root Explorer navigate to Sys/Kernel/logger_mode open the file with text editor, It show 0=Disabled.
[Galaxy Note II Original Android Development] KNIGHT97:
I'll have a look at that file. Thanks for that info I was trying to figure out which while is resposible for the logger.

I'll check and see if I can myself find the fault.

Btw much of ny newer bencmarks for r5.1 is done, just a bit left, so expect the performance report by this weekend ;)
[Galaxy Note II Original Android Development] dollyaja:
Sorry,can someone upload another link for latest version,seems cant download from mediafire ( try with stock,boat,and chrome) on my phone. Thank u
[Galaxy Note II Original Android Development] ph03n!x:
Makes sense why I didn't have any issues - I use lulzactiveq, do not use touchboost and create my own scripts for UVing (in fact do not use Synapse or Trickster or anything else for the matter of fact ;) )

So except for these three changes, the kernel is untouched and I can stay in v5? :)

Umm.. on the contrary, I suggest advanced users to put the phone in a state where it uses the maximum power for any given frequency. This is from experience - everything would be fine with the UV voltages I select, and then when I do something new (like connect to WiFi, stream audio through BT, or play a HD movie), the phone will freeze - the culprit was of course the UVing - and the voltage I had selected was good enough for normal use but not for the additional stuff I started doing after finalizing the voltages :(
[Galaxy Note II Original Android Development] KNIGHT97:
[MENTION=5132493]aukhan[/MENTION] the file shows 0 (disabled), so I guess that logger is turned off now.

But seems touchboost can't be turned off and is set to 600 everytine I close synapse, so can you mention the file resposible for that, so I can have a look
[Galaxy Note II Original Android Development] klurosu:
How to safe undervolting in Nadia Kernel (synapse method)

[YOUTUBE]K7sP9PqMC5c[/YOUTUBE]
[Galaxy Note II Original Android Development] ph03n!x:
/sys/devices/virtual/misc/touchboost_switch/touchboost_switch
/sys/devices/virtual/misc/touchboost_switch/touchboost_freq
[Galaxy Note II Original Android Development] KNIGHT97:
Seems it is disabled already.....

Maybe a syanapse issue, I checked and touchboost now turned off.

But anyways, thanks a lot for pointing that out, will help me when sometime in future maybe.
[Galaxy Note II Original Android Development] rebel.mindset:
Thanks mate. I've been following your ideas and implementing it. They're very effective. Getting a good performance. :thumbup:
[Galaxy Note II Original Android Development] klurosu:
All the thanks goes to Pafcholini and the nadia crew buddy.

I only post my own experiences :)

sent from a far far galaxy n7100
[Galaxy Note II Original Android Development] portalXHD:
Thanks Emotion team for the great Kernel...

:) Sharing:

This is my kernel setting using Synapse (base on my personal experiencing, this setting quite stable and get Antutu at least 22k above for myself). Battery life so far so good, I am a heavy user...

Model: N7100

ROM: Emotroid 7.0 (TW Kitkat)

Kernel: Nadia Kernel V5.1

ASV Info: ASV1

1) CPU - GOV

CPU MAX = 1800

CPU MIN = 200

CPU Governor = zzmoove

2) CPU Voltage

1800 = 1225mV

1704 = 1225mV

1600 = 1200mV

1500 = 1175mV

1400 = 1125mV

1300 = 1075mV

1200 = 1050mV

1100 = 1000mV

1000 = 975mV

900 = 950mV

800 = 938mV

700 = 925mV

600 = 900mV

500 = 888mV

400 = 875mV

300 = 863mV

200 = 850mV

3) GPU

only change GPU Step 5 = 640

4) I/O

both change to = zen

5) CPU Drivers

IDLE Mode = AFTR+LPA

Logger mode = disabled

6) ABB

Slice 1 Voltage = 650

Slice 2 Voltage = 650

Slice 3 Voltage = 650

Slice 4 Voltage = 750

6) BATTERY

Dedicated Charging Port & A/C Input Current = 2000mV

Dedicated Charging Port & A/C Charging Current = 2000mV

Standard Downstream Port Input Current = 1300mV

Standard Downstream Port Charging Current = 1200mV

Charging Downstream Port Input Current = 1350mV

Charging Downstream Port Charging Current = 1250mV

Ignore 100mA Step Safety Margin = Yes

Ignore Unstable Power Detection = Yes

7) SOUND

Enable Wolfson Sound = Yes

Enable FLL Tuning = Yes

DAC Direct = Yes

Enable Speaker Equalizer = Yes

8) MDNIE

MDNIE Mode = MOVIE

MDNIE Scenario = 5

*this is the only changes I make.
[Galaxy Note II Original Android Development] ph03n!x:
Do you realize that this setting may actually result in higher current drain for a ASV 1 device? And did you check if the 650 mV that you are applying actually gets applied? IIRC in the original ABB implementation, 700 mV was the least value possible - values below that will be ignored...
[Galaxy Note II Original Android Development] mat9v:
Please read in my thread what exactly ABB is used for and how it should be configured. The way it is now, you will have higher battery consumption then with stock settings.
[Galaxy Note II Original Android Development] portalXHD:
I did calculated, I should increase the ABB? but if wont be stable...

MHz-TransistorGate-TransistorBody-Difference

200	812500	800000	12500

300	825000	900000	-75000

400	850000	900000	-50000

500	875000	900000	-25000

600	900000	900000	0

700	912500	900000	12500

800	925000	900000	25000

900	950000	950000	0

1000	975000	950000	25000

1100	987500	950000	37500

1200	1000000	950000	50000

1300	1025000	950000	75000

1400	1062500	950000	112500

1500	1100000	950000	150000

1600	1125000	950000	175000

1700	1175000	950000	225000

1800	1200000	950000	250000