yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] SkoreK89:
It's my result after first day of instllation v13

View attachment 4049879

http://cloud.tapatalk.com/s/58acaa414c178/Screenshot_2017-02-21-21-52-10.jpg?

http://cloud.tapatalk.com/s/58acaa82eb7b5/Screenshot_2017-02-21-21-52-19.jpg?

http://cloud.tapatalk.com/s/58acaad0bb4f2/Screenshot_2017-02-21-21-54-00.jpg?

http://cloud.tapatalk.com/s/58acaac5e1e3e/Screenshot_2017-02-21-21-54-10.jpg?

http://cloud.tapatalk.com/s/58acab010d424/Screenshot_2017-02-21-21-54-27.jpg?

http://cloud.tapatalk.com/s/58acab43ed707/Screenshot_2017-02-21-21-54-36.jpg?
[Galaxy Note II Original Android Development] MCT_:
Thanks, but I can not see anything on your screenshots.

Well, I will share with you one little secret.

In fact, everything is simple.

In the screenshot you see two stripes, yellow and green ("Battery Monitor Widget").

Given my post above, you can see at what level is the monitoring.

The higher the scale of monitoring, is more powersave kernel.

In your case v13, monitoring is at the very bottom.

I slowly raise the bar upwards to the nearest SoD.

And he's almost in the middle.

Believe me, I know the power consumption when using the mod a bit big for you, even when using tools to suppress performance.

I will continue to work on this and as -10UV (in sleeping mode) for "Ondemand, Conservative..etc.." will receive SoD, it be new build v13a.

==========================================

- Optimization of kernel.

- Fixed SPEAK TUNING (support awake/sleeping mode | no stop process "AudioOutLock" | if stop process onrestart 0.9s "ie will not be jerks").

- Fixed FILE SYNC (support awake/sleeping mode).

- Fixed anti SoD (Now he forced to raise the voltage at the "/sys/* /wait_for_fb_wake == awake" and to read the directory of the script that would stop | send computing the number for system server and daemons).

- Circumvent the operation of the trigger (wakelock).

IMG_v4.5.5-FULL-MOD.R1_MODE_EPS.v13a_4.4.x_STOCK.zip
[Galaxy Note II Original Android Development] SkoreK89:
I will install this app and see how it's looks like. At this moment I never had SOT like this on Eclipse v9. No SOD problem. You are the best my friend :) You make fu***ng great job in my opinion :) I have this phone 4 years and 4 months and I'm not thinking about change it in nearest future :) Thanks to you and Eclipse v9.

Wysłane z mojego SM-N910C przy użyciu Tapatalka
[Galaxy Note II Original Android Development] MCT_:
Thanks, but I think, v14 build will be as a final, in this topic of discussion.

- Correction work of governors...

All that remains to do.

I also like it here, friendly people... fun and sociable )
[Galaxy Note II Original Android Development] MuradDA16:
Hi [MENTION=270886]mct[/MENTION], i am trying to understand why u set max frequency on sleeping mode is higher than awake mode. I would like to try ur mod kernel but i need to understand all ur mod added on agni's kernel.

Thanks for ur works Sir.
[Galaxy Note II Original Android Development] elsaedy:
i think to forced sod on deep sleep
[Galaxy Note II Original Android Development] MCT_:
Hi, [MENTION=4866859]MuradDA16[/MENTION].

Yes, until recently, the Mod has used the maximum frequency value.

These work only when you run the command.

In the long sleep mode, the value drops to a minimum.

You must watch the whole entire script... ie, it is a chain of execution commands which have a sequence number of the commands.

Below you will see how the maximum frequency gets the value you indicated.

Ie, the maximum work frequency like a shot

And the Use Of "Performance & Powersave" that would indicate the environment runtime.

It is sometimes impossible to switch governors when the device is in excessive suppression performance.

I'm doing the "Performance" before switching the governor.

===========================

v13b

- Optimization of kernel.

- Correction work of governors...(not fully).

- Pop-UPS for UV (Ondemand, Conservative, Powersave).

=================

IMG_v4.5.5-FULL-MOD.R1_MODE_EPS.v13b_4.4.x_STOCK.zip

After installation, reboot device.
[Galaxy Note II Original Android Development] squicky:
Hi [MENTION=3132251]MCT_[/MENTION]

First of all I would like to thank you for the time and effort you’ve put in to this kernel. For the last two days I was observing this topic. I was trying hard to understand exactly what settings are needed for properly working governors. Over the past year you’ve made quite a few changes in the MOD AGNi Control app. I’m really confused and really don’t know where to start.

I’m using Eclipse v9 ROM and normally I use PSN_AGNi_pureSTOCK-v4.5.5-N7100 kernel. This combination is working for me pretty good, but I wanted to test your mod.

1.	With original kernel v4.5.5 I don’t have issues with going into deep sleep state. When I use your kernel (tried v13a and v13b) phone doesn’t go into deep sleep, it’s always awake. I’ve tried a few governors (Intelliactive, Ondemand, Conservative, Powersave and others) and still couldn’t go into deep sleep. Any idea why? Or maybe it’s by design?

2.	I understand that you’ve made a loop to constantly apply some settings for governors. Pressing 4 times on power button to activate the loop often - but not always - gives me SOD/freeze on your default settings.

3.	Does you kernel mod is set with some safe/good default settings or is it just a work in progress and everybody must set it to their needs after it’s flashed?

4.	Why Android is optimizing apps on every restart after flashing your kernel mod? I think it should be done only once and only for the user apps right? Your kernel mod is activating Android optimizing to all - user and system apps - and on every restart also for user apps.

5.	If I choose Ondemand Control should I get some extra options in the MOD AGNi Control app?

6.	What exactly do first 2 options in MOD AGNi Control app? I won’t be able to use governors if I don’t select these 2 options?

7. I have flashed you kernel mod v13b. Then I waited for phone to boot and settle down. Then I did reboot and waited for phone to settle down again. Then I pressed home button and screen froze I guess SOD. Should I change governors or v13b is still not for daily use?

I have more questions, but for now I will be happy if you give me some answers to these ones :)
[Galaxy Note II Original Android Development] elsaedy:
iam eclipse v9 too..and i have same problems with SOD...v13..v13a..v13b i have sod with default setting and also with my setting...i told mct alot about sod but he tell me that iam wrong or i donnot use it with correct meathod......

and i use the version of bussy box that he tell to use...and alot of sod....i stop to say to him about sod ...he also angry from me

i think eclipse is the problem...mct use stock rom
[Galaxy Note II Original Android Development] squicky:
That may be true. On the other hand if Eclipse ROM is causing this SOD issues, then why is it working for me so good with original PSN_AGNi_pureSTOCK-v4.5.5-N7100? I've had some issues this kernel too, but it was my fault for too much undervolting. I didn't change anything in modded kernel and still got SOD almost instantly after boot.
[Galaxy Note II Original Android Development] MCT_:
~ Excessive suppression leads to high energy consumption.

The device tries to fight the excessive suppression.

And not falls into a deep sleep.

Yes, corrected the error...

zip..

You need to reinstall the settings.

To avoid the chaotic character device to buffering.

And to lock the volume of the heap integrity of the system.

"ondemand control"... Yes... in the process of developing.

Don't understand.

Corrected the error...zip...

=======================

IMG_v4.5.5-FULL-MOD.R1_MODE_EPS.v13c_4.4.x_STOCK.zip
[Galaxy Note II Original Android Development] squicky:
[MENTION=3132251]MCT_[/MENTION]

I'm really grateful for your answers, but machine translation from Russian is horrible. English is not my main language too, but if I can't understand your answers then I will have to give up on this subject. Language barrier in this case is really hard to overcome. It would be easier if you write in Russian language, so we could try to translate it individually, but mods probably wouldn't allow it. Maybe there is someone from your country who is following this discussion and would be willing to translate it for us?
[Galaxy Note II Original Android Development] MCT_:
There's no one here but me )

I understand you very well.

A few points I don't understand... everything else was good.

Don't understand.

Писать по-русски, было бы здорово, конечно.
Но это не понравится администрации сайта.
В крайнем случае.
Немного позже, напишу инструкцию.

Кратко:
Ну, в целом... всё уже существует в теме обсуждения ...
Т.е это установка busybox, (я использую v19), так же файл busybox интегрирован в систему /sbin.
Проверка работоспособности петли, скриншоты в теме обсуждения...
Всё как бы понятно.

Кнопку четыре раза нажимать не нужно.
Это исправлено уже давно.

Настройки...
Я установил Mod несколько минут назад, после поправок к рамдиску.
Необходимо немного времени, что бы говорить о настройках.
[Galaxy Note II Original Android Development] squicky:
OK :) I would like to tell you the same thing, that everything you wrote was clear to me, but it would be a big fat lie. ;)

Now the answers I don't really understand.

1. "Excessive suppression leads to high energy consumption." - I have not changed default settings that came with your modified kernel so what is causing this "excessive suppression". I have to get rid off undervolting for sleeping mode? Should I change it from -10 to 0 or +10?

2. "Yes, corrected the error...zip.." You've made changes to v13b and I should download the file again or you are going to upload a new file?

3. What do you mean by "reinstall settings"? Should I clean init.d folder and reset all settings in Mod Agni Control app? I did that and still got SOD and no Deep Sleep.

4. "To avoid the chaotic character device to buffering. And to lock the volume of the heap integrity of the system." - This one is a black magic to me :D Please write this in Russian like you did before :)

5.""ondemand control"... Yes... in the process of developing." So if choose this option then new settings for ondemand should show in your app?

6. The first two options in Mod Agni Control app I was referring to are these:

Do they have to be enabled for governors to work in some special way or what? I simply don't understand what are these packages for and why should I enable them? Should I enable one of them or both (only "all governors" or only "original governors' or both of them)?

7. I Don't know how to interpret this scale picture. You mean that on the left is v13c and on the right v13b???

Now I will download v13c and will see if it will improve things to me. Once again thanks:good:
[Galaxy Note II Original Android Development] MCT_:
Post #6343 zip file.

Ondemand Control:
[Galaxy Note II Original Android Development] squicky:
I don't know if it's because Eclipse v9 has different Busybox or something else is to blame, but my Mod Agni Control app doesn't look like yours when I choose "Ondemand Control" and I still ended with SOD. Even requesting for ROOT takes 2-3 times longer than with original Agni Control app. Using original v4.5.5 kernel I have no issues. I don't know what else to try.

---------- Post added 26th February 2017 at 12:02 AM ---------- Previous post was 25th February 2017 at 11:09 PM ----------

I've had SOD again and again with modded agni kernel so I thought I will try this kyubi you were talking about. I don't know if it's better or worse than agni kernel, but I've managed to flash it on the first try without any issues. That's what I did:

1. From AGNi Control app: Clean init.d then Reset All Settings

2. Uninstall AGNi Control app using for example Titanium Backup.

3. Flash AGNi Cleaner.

4. Flash Kyubi kernel.

5. Uninstall Synapse or not, that's up to you.

6. Flash Update-SuperSU

7. Install SuperSU from Play Store if needed.

Kyubi's got potential. When you've got a lot things going on in the background interface might got a bit choppy, but at least it wasn't making my music choppy. With nadia's script it's actually quite good. But I think that UI is still more fluid on agni 4.5.5 with default zzmove zanez optimised governor. AGNi has a number of configuration options for different things than governors also.

Kyubi might be more immune to SOD and more battery friendly though. Either way it's good to have some alternative to AGNi :) I wonder how Kyubi reacts to undervolting...
[Galaxy Note II Original Android Development] elsaedy:
agni is the best kernel...v12 and v12a were work good without sod....but deep sleep was not good...iam sure [MENTION=270886]mct[/MENTION] will find good way to make it the best

do you know that there are boeflla kernel for s3 i9300...that mean it can port for our n7100
[Galaxy Note II Original Android Development] MCT_:
Hm, what you showed me and writing, it's just awful and I understand your feelings.

Actually, all not so bad... little patience.

1)

You show a screenshot with no script.

Here you will find the number of the evaluator total package.

/ <= 460 / MEDIUM

Ie, all the packages have their own calculations.

/ <= 369 / LITE

/ <= 515 / FULL ...etc.

Display is correct in that case, if the sum of the package is correct.

Sometimes, after flashing the kernel, many things just do not apply.

Most often, stability of the work occurs only after reboot and even after the next reboot.

It's nobody's fault, it's the principle work of the system (system prescribed new code = adaptation...).

Sometimes, I flashing kernel two times, that would be my changes was of applied.

I can see it very well, because I am programming a script for the kernel and flashing of kernel in a day ten times.

But you immediately go to write a bug report.

You with 2012 registered, flashing kernel and various firmware.

Because you are not new on XDA.

You don't know anything about it ?

Of course, the original AGNi has no such problems, because of its simple script.

If you think that downl of packages takes a lot of time, unplug Autoreset.

And of course, after flashing the kernel you want to try all of the tweak and make it fast.

But the principle of operation of the program requires full monitoring script.

Switching between packages is time consuming.

If you are in a hurry, use something else.

I do not impose anything and do not sell anything here.

2)

No SoD, ondemand, conservative, powersave.. )

< or curr 440220

In addition, ondemand, conservative, powersave "ORIGINAL GOVERNORS", is disable from the loop.

The script of the governors for loop is empty, no SoD... and will be even better.

Also, Deep Sleep work.

3)

If you clean the directory /init.d

You should return a value of "default for UV sleeping mode.

The button can be highlighted, but the script is no in the directory.

Accordingly, he gets -20UV from script to awake mode and SoD.

In addition, to take into account the directories loop.

I don't know what can be discussed, if you even can't correctly flash the kernel.
[Galaxy Note II Original Android Development] squicky:
[MENTION=3132251]MCT_[/MENTION]

I didn't want to upset you. I simply and truly can't understand how your MOD work. Yes I registered to xda in 2012 but I'm no dev, I only go here time to time to find something interesting to my old N7100. I've flashed your kernel mod at least 15 times over the last two days, so my conclusions wasn't based on a one time flash as you write.

Still got SOD no matter what governor I choose. I think it's time for me to give up. I'm convinced that it's not compatible with Eclipse ROM, but of course I may be wrong, I'm not dev. Thanks again for your work.
[Galaxy Note II Original Android Development] MCT_:
[MENTION=4539857]squicky[/MENTION]

I'm not upset.

Even for the reason that I have everything working.

But you must understand what you are doing.

You see before you the instruments that suppress the voltage, change CPU frequency, governors etc...

Excessive voltage suppression leads to increased consumption mA.

And governors such as "Ondemand, Conservative" not can control deep sleep not even have the intermediate frequency.

Only ping the system to execute commands cyclic shift can hold your device in a state of live.

(A lot of information you can read about it, no secret brand).

Tell me that ~ swappiness does not work and I will look for the cause of the error.

But we're spinning our wheels with the problem of installing and excessive suppression performance.
[Galaxy Note II Original Android Development] elsaedy:
why we cannot control ondemand...alot of kernel use it ...shift kernel and boeffla and kyubbi use ondemand and itis stabble and control deep sleep
[Galaxy Note II Original Android Development] squicky:
I told you already that I didn't play with UV or OC on your MOD that's why I was so confused that I had SOD all the time.

I've decided to try some old stock ROM 4.4.2 from wesam.othman. I've restored it from backup. Then I've installed your MOD. COMPLETELY DIFFERENT THING!!!

I didn't have to do anything else. MOD works very good there, no SOD after minute or two like it was happening to me on Eclipse v9. And it works smooth on stock ROM. On Eclipse it was choppy.

1. On stock rom menu in MOD AGNi Control app looks exactly like yours on your screenshots. On Eclipse it was a mess - no matter if I chosed "package all governors" or "package original governors" it still displayed every governor of both groups and that's why I didn't know why and what these 2 options do.

2. On stock rom there are two checker files in the dev/cpuset/mod-mct-monitor and they are not empty. On Eclipse there was only one and it was empty.

3. On stock rom I don't have "optimizing apps" on each and every reboot. On Eclipse I had it and it was making me mad.

4. On stock rom I don't have any issue with Deep Sleep - works without any tinkering or changing settings. On Eclipse never worked.

I will try clean flashing Eclipse v9 and then your MOD to see if it will make any difference. For now I'm convinced that it's not compatible with Eclipse v9 because on stock ROM your MOD works very good on the first try.

UPDATE: I've now flashed clean Eclipse v9 and still menu in MOD AGNi Control app is messed up like before, still have one empty checker file dev/cpuset/mod-mct-monitor.

What's change is that I didn't have SOD for now and Deep Sleep is working, but it's clean flashed ROM so not much apps working in background and overall it's lighter than usual.

For my understanding MOD kernel is not compatible with either Eclipse v9 ROM or busybox in this ROM... I don't know. What I know is that it doesn't work like it worked in the stock rom I've tested earlier.
[Galaxy Note II Original Android Development] MCT_:
[MENTION=4539857]squicky[/MENTION]

a) SoD, just daemon is not running, the script in background mode stops the system with mistake.

Fixed for the next build.

b) Install busybox.

In the search subject, is a lot of information about it.

By the way, [MENTION=6296907]elsaedy[/MENTION] tested it on Eclipse v9 )

For me, it worked great.
[Galaxy Note II Original Android Development] elsaedy:
yes v12 was work good without sod and with the version of bussybox that you told...only deep sleep was not good..i wait new version...i need to make ondemand on awake and also ondemand on sleep if it can posible
[Galaxy Note II Original Android Development] MCT_:
v12 is already a dinosaur.

v13.., In the section "ORIGINAL GOVERNORS", he even disconnected from the loop.
[Galaxy Note II Original Android Development] elsaedy:
i have 2 busy box version on my phone...should i unustall the pro version and use the version you told or itis ok if boath installed
[Galaxy Note II Original Android Development] squicky:
Yes, now after all day of searching and testing I found out that Busybox was the main culprit and your MOD works fine on Eclipse v9. It was a wrong version of Busybox to be exact. I wasn't here throughout the year when you were developing this MOD so I was a bit lost in all this conversation ;) Now I feel a bit more confident because I tried different things which didn't work and some that did work, so let's say I have a starting point.

For now I have one question. First you were recommending Busybox 1.19.3 and now it's suppose to be 1.24.1 right? Could you make the final version of your MOD compatible with the newest version 1.26.2 or maybe this would be to much of work?

Playing with this MOD is on the next level for me. Earlier I simply was using ready scripts where I edited values for OC, UV and other stuff. This MOD is really complicated for me to understand and requires quite some time to gather all information about how each governor works, what values can be changed, what are the limits and so on. That's a lot :) But actually it's very interesting stuff.
[Galaxy Note II Original Android Development] MCT_:
You can use multiple, if they do not conflict.

For dir /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

Well :: )

I use v1.23.0.git working not very good.

1.19.3 better with this type of script but also has disadvantages.

Ie it cannot be used to install the kernel /sbin but for the script, works well.
[Galaxy Note II Original Android Development] elsaedy:
so after you try and search..which version of bussybox you recommended to use...for working without sod
[Galaxy Note II Original Android Development] MCT_:
MOD v13d

- Anti SoD (Fixed start-stop-daemon script running in sleeping mode --background).

- Fixed start-stop-daemon script running stop in awake mode.

- *To send the value of the min-max frequency directly to system & daemon.

------------------------------------------------------------------------------------------------------------------------------------------------------------

*Possible conflict with such governors as:

smartassV2 zzmoove lulzactiveq yankasusq pegasusqplus pegasusqpluso hotplug adaptive pegasusq

Will be fixed upon receipt of the error.

Until I noticed errors with them (the priority of the script is a little higher).

IMG_v4.5.5-FULL-MOD.R1_MODE_EPS.v13d_4.4.x_STOCK.zip

==================================================
[Galaxy Note II Original Android Development] elsaedy:
can i use ondemand on wake and sleep governor
[Galaxy Note II Original Android Development] MCT_:
Yes, no problem.

-/+ UV in sleep mode, regulate deep sleep.

Use any program, to see how it happens.

And I adjust the -/+ UV script that would find the optimal value for deep sleep.
[Galaxy Note II Original Android Development] squicky:
I can't tell you exactly what is100% working, but I can describe you the steps I did, so you could try it on your phone.

Looks like Eclipse v9 is forcing busybox 1.23.0git on every restart of the phone. So even though I installed busybox free (stericson) (it was suppose to be 1.24.1 but until restart it was showing as 1.22.1) from the link given by MCT_ sometime earlier, I ended up still having 1.23.0git.

But without installing this busybox the menu in MOD Agni Control app looked funky and I'm pretty sure things didn't work as they should. So if you want, you can try this procedure:

1. Install busybox https://mega.nz/#!i5xCVIYI!UH_CG9D9-AjBrUHyy0w1Q4nE3uygm1uPwtlFTjz7v6s from MCT_.

2. In MOD Agni Control app activate INIT.D (CLEAN COMPLETELY)

3. In MOD Agni Control app activate APP:RESET ALL SETTINGS

4. Restart your phone.

5. In MOD Agni Control app set your governor (I simply set it for Ondemand for now).

6. You can do another restart to make sure your settings are properly applied.

Doing this steps in Eclipse 9 helped me with SOD and for now looks like I don't have problems with Deep Sleep. Catlog doesn't show any errors about busybox.

All of his was done on MOD v13c as I've not tried v13d yet.
[Galaxy Note II Original Android Development] elsaedy:
i already use this version of bussybox..i follow mct mod long time ago..i only was yse mct mod long time..alot of test