yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] g.lewarne:
all memory management / performance management in a rom should be left entirely up to 2 things - the core Android OS and the Kernel

The kernel has *highly tuned* settings specific to our note, that i have perfected over countless builds. In the kernel These settings pertain to

- readahead

- VM memory

- LMK (low memory killer)

- Minfree

Android OS iteself should be left alone to work with the settings provided by the kernel for optimum efficiency. Having init.d scripts that "tweak" these values reduces efficiency. Efficiency is the key to two things - battery life and performance

Eg - my kernel sets most of the OOM LMK values to 14366kb. Most tweak scripts, eg supercharger, loopy smoothness etc set this to a lower value. Setting a SD card readahead in a script is a very bad idea and only hurts performance and wastes cpu cyctles (and hence battery). The more readahead is set - the lower the actual efficiency of the system and higher the battery drain.

In my ROM (cleanote) there are NO scripts at all. Everything is left to android and the kernel. There are many posts in this thread from people who have deleted all the tweak scripts and noticed a significant performance gain and better battery life. Some people even flash my ROMs build.prop for even better performance.

Lets go back to sd card readahead for example........

Android need to access a file in storage. If readahead is set only by kernel (in notecore case to 384kb) then this happens

file = 100k

android requests file, reads the 100k file and the next 284k in adjacent blocks. Since the file is 100k large, 284k is "flushed" by the kernel.

in the case of silly large readaheads set by scripts (lets say 4096 as that is common)...

file - 100k

android reads the file, and the next 3094k in adjacent blocks. reading that extra 3094k takes time (cpu + battery) and the same amount of time (cpu and battery) for it to be "flushed" by the kernel as it is not required.

this is in its most simple terms - in some cases there is a slight advantage to having larger readaheads, but for general day-to-day use 384k is more efficient as most android system files are quite small.

hope this helps
[Galaxy Note GT-N7000 Android Development] g.lewarne:
patience...... :good:

i am but one person.....i am tired! i work countless hours for free here on XDA....let me chill for a week or two :)
[Galaxy Note GT-N7000 Android Development] MikeFRG:
Why? If u realy want to "see" how a Kernel works it takes 2-3 days! So better to release once a week!

And iam not in the beta club, what ever i dont care.
[Galaxy Note GT-N7000 Android Development] androiadicted:
This should be pm to every rom cooker that use your kernel like rocket. His rom hase 13!!! init.d tweaks. V9 that is. V10 i do not know.
[Galaxy Note GT-N7000 Android Development] jaskiratsingh:
Gavin,

When rest of use can enjoy version 12.1?
[Galaxy Note GT-N7000 Android Development] g.lewarne:
nah, let the ROM guys do their thing.....eventually they might catch on.

But in terms of scripts - "supercharger" is by far the worst! and if it isnt edited by the rom chef before inclusion you get crazy low OOM and LMK valuus which totally screw with the system and cause LAG
[Galaxy Note GT-N7000 Android Development] MikeFRG:
NEVER ask on XDA for eta!!!
[Galaxy Note GT-N7000 Android Development] nickshertzer:
Now I feel smarter!

Such a well stated, lucid, explanation. :victory:
[Galaxy Note GT-N7000 Android Development] jaskiratsingh:
Not along for eta. Version 12.1 had been beta tested and good reports have came out.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Im not doing daily "public" releases any more.

v12 is an excellent kernel, perhaps about as fast as it can get without losing stability and eating battery like no tomorrow.

From now on it is about "tuning" it to give the best possible responsiveness...this takes time for users to test, hence why beta releases to a closed group. When I am happy after a few days, another public release will be made.

Its not like im going away or your losing out, and in fact 12.1 does have a couple of issues which were noticed and I have been working on.

Im also working on global undervolting for all voltage groups - again this takes time for stability testing. Something I cannot do on my own.

12.4 beta will be an interesting release for them to test;)
[Galaxy Note GT-N7000 Android Development] g.lewarne:
@ ALL BETA TESTERS

12.4 available. You know where to find it, changes in OP :good:
[Galaxy Note GT-N7000 Android Development] Formhault:
Again, Pixel Salad... CN v4 w/ NC 12.1. Oh well, perhaps it's the theme...

Will flash 12.4 and report back in the morning ;)

:great: Gavin!

Sent from my GT-N7000
[Galaxy Note GT-N7000 Android Development] g.lewarne:
tius weird i havent had a pixel salaed for ooooh about 4 weeks or so !
[Galaxy Note GT-N7000 Android Development] azzledazzle:
I get them rarely, But so do many others on different ROMs and Kernels so i dont think its related to them.

Its a little scary and weird, But it hasnt affected anything and it goes away after a simple lock / unlock.
[Galaxy Note GT-N7000 Android Development] jaskiratsingh:
Sounds good :)
[Galaxy Note GT-N7000 Android Development] Formhault:
Could be because of themes...

Will you ever include 15 toggles in CleaNote?

Sent from my GT-N7000

---------- Post added at 10:28 PM ---------- Previous post was at 10:27 PM ----------

Nope. Have to force reboot...

Sent from my GT-N7000

---------- Post added at 10:28 PM ---------- Previous post was at 10:28 PM ----------

Wtf, posts merging is now a feature of Tapatalk? Finally!

Sent from my GT-N7000
[Galaxy Note GT-N7000 Android Development] robert1968:
no oc works. wrong note?

What is the problem with my note?

My board is in voltage A group, and none of the oc versions ever worked.

V12oc started at least but frozen within seconds.

Standard versions are always OK.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
very, very few people with Group "A" phones are able to run the OC kernels.....group "A" needs quite a bit more voltage than B/C and for me to make it stable it would need crazy voltage at which point people would then be complaining about heat and battery, so i dont
[Galaxy Note GT-N7000 Android Development] robert1968:
Thank you very much for explanation!

Better to know I'm not alone :)

Thanks Gavin.

Robert
[Galaxy Note GT-N7000 Android Development] milsabords:
+1

See what happened to the Stunner thread.
[Galaxy Note GT-N7000 Android Development] cook:
Hello,

Could you advises us which file we can / should delete in init.d on main ROMs ?

I believe some scripts are needed and are not customisation tweaks.

Should I delete S95_sdcardspeedfix from Criskelo ROM for example ?

#!/system/bin/sh

#

# by Slaid480

READ_AHEAD_KB="3072"

if [ -e /sys/devices/virtual/bdi/0:18/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/0:18/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:0/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:0/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:0/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:1/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:1/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:2/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:2/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:3/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:3/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:4/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:4/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:5/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:5/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:6/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:6/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/7:7/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:7/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

if [ -e /sys/devices/virtual/bdi/default/read_ahead_kb ]; then

echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/default/read_ahead_kb

echo "SD card read ahead kb SET to $READ_AHEAD_KB"

fi

Thanks
[Galaxy Note GT-N7000 Android Development] monomer888:
With the magic of the Google Cache and Chasmodo's kernel repository thread, you can reconstruct a fair portion of the old NoteCore changelogs back to V7. It might look even something like this:

https://dl.dropbox.com/u/60702179/NoteCoreChangelogOld.txt
[Galaxy Note GT-N7000 Android Development] g.lewarne:
WOW...just WOW

so because i decide to do a *little* less FREE work for XDA, and not release possibly very broken beta quality kernels to the public after making what everyone is in agreement a very solid v12 you think what? im going somewhere? this is turning into some kind of exclusive club?

oh, the attitude of some users :rolleyes:
[Galaxy Note GT-N7000 Android Development] cook:
Hello,

Note stable since 1 week with this undervoltage applied to your last OC kernel (version vary from one day to another) via tegrak :

My wife's note : (Group A)

CPU

1600 : (not used as I'm looking for best battery life)

1400 : 1.250V

1200 : 1.150V

1000 : 1.075V

800 : 1.000V

500 : 0.950V

200 : 0.850V

GPU

267 : 0.900V

160 : 0.800V

My note : (Group B)

CPU

1600 : (not used as I'm looking for best battery life)

1400 : 1.200V

1200 : 1.100V

1000 : 1.025V

800 : 0.950V

500 : 0.900V

200 : 0.800V

GPU

267 : 0.900V

160 : 0.750V

So my wife note, group A, is stable with a serious undervolting. She got one time a pixel salad on wake up on phone call but as I understood this have nothing to do with undervolting.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
simple answer - yes!
[Galaxy Note GT-N7000 Android Development] :
bitte

Spoiler content hidden.

original http://www.goa-roms.de/index.php?page=Thread&postID=14972#post14972
[Galaxy Note GT-N7000 Android Development] androiadicted:
Never saw a very broken beta. We all no the riks when it goes wrong. Never did go wrong here so wy sudden beta testers? I love your work. And after 15 kernels updated i think we past beta kernels.
[Galaxy Note GT-N7000 Android Development] milsabords:
Hi Gavin,

:) did not want to be rude, sorry if you feel so.

I've been a happy user of Stunner, very disappointed when Neo decided to go private on FB. Many users - me included - left board, because we were motivated by being in the game.

Plymouth ... nice place, went over there a few times when we had a major networking unit out there.

Cheers.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Its because this time im making some dramatic alterations to things....especially voktages. i dobnt wabt to release broken kernels.

Why am i even explaining this? :rolleyes:
[Galaxy Note GT-N7000 Android Development] g.lewarne:
No problem
[Galaxy Note GT-N7000 Android Development] bttcp12:
I love your work Gavin, but love more that you release betas to the public so anyone could choose to use them our not, it isn't going to change that yours it's the best kernel for our notes.

Keep up the good work, and re-think your beta policy.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Good lord! why is this even being questioned so much?

Im trying to do better by you all by getting reliable, non noobish feedback from a quite large group of people on some significant changes that i cannot possibly test completely myself.

Do you want to lose data?

Geez....one more post like this and i wont post anything public for quite some time.

GET OVER IT THIS IS MY PROJECT I CAN DO WHAT I WANT AND IF YOU CANT BEAR THE THIUGHT OF NOT HAVING A BROKEN OR UNSTABLE KERNEL IN YOUR PHONE GO ELSEWHERE.

You can see for yourself the changes im making (bottom of op)....you are not missing out on anything at all
[Galaxy Note GT-N7000 Android Development] Supersaiyan.IV:
Instead of tweaking voltages, are there any plans for DEEP IDLE?

Also, I'm getting dejavu over this thread. Revise beta policy flamewar? Have a flamewar over getting your warranty voided instead. He can even lock his kernel to be compatible with only 1 ROM had he wished to, so stop being justice-dickwagglers.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
If you mean a 100mhz frequency that wont operate properly on any voltage less than 875 (playing with this@200) and will just add to frequency ramp up latency...no
[Galaxy Note GT-N7000 Android Development] Supersaiyan.IV:
Unfortunately DEEP IDLE has nothing to do with undervolting. It's the state that toggles between TOP-ON and TOP-OFF from which the CPU may only be awoken through an external interrupt. Meaning that it's in near-complete sleep.

When this is implemented it's actually more favorable to have a higher clock speed (so you can get the job done fast and go to sleep again).

So the 100Mhz you mentioned, yeah it's a bad idea, 200Mhz likewise. It should operate at the least 800Mhz, or the highest possible where the chip still supports low power mode.

Apart from that, I really have no idea what you're talking about.

EDIT: Interactive governor fixes ramp up problem by the way (ramps up to MAX on screen touch), in case you had a completely unrelated problem with that.
[Galaxy Note GT-N7000 Android Development] bttcp12:
It's ok, calm down Gavin, I'm ok with it, only I liked more the previous method ;).

P.D.: I been using 400 mhz / 1000 mv // 200 mhz / 900 mv, without any freezes for a long time, the random freezes could been because of cpu undervolt.

My CPU table of group B:

1600 mhz / 1300 mv

1400 mhz / 1225 mv

1200 mhz / 1150 mv

1000 mhz / 1075 mv

800 mhz / 1000 mv

500 mhz / 900 mv

200 mhz / 800 mv
[Galaxy Note GT-N7000 Android Development] hchxoom:
Just ignore them, Gavin. I suspect most long-term users, like me, have watched you develop this great kernel long enough to know you'll keep putting out great stuff when its ready for distribution.

V12, by the way, is running great. Smooth, and battery life quite good. At my usage pattern, no issue getting well beyond 24 hours (I'm not a gamer), though I almost always have access to an outlet much more frequently than that. Frankly, I think I'm going to appreciate a little time between releases to let your work really settle in.

To the gent with the gps battery issue, in addition to Gavin's recommendation, I'd suggest investing in Tasker and learning to program your note to turn GPS on and off when its needed. GPS is a real hog, and Tasker has saved me lots of juice from forgetting to turn off GPS.
[Galaxy Note GT-N7000 Android Development] monomer888:
I think Gavin means having an extra frequency step would cause extra latency in having to switch through that step in response to load. He can probably explain that better than me though.

As to Deep Idle, from what I read from the SGS2 kernels, the exynos chipset prevents either core going into Deep Idle states when the second core is on, so sadly some of the fancy stuff about balancing workload asymmetrically between cores by having one core going into a powersave state won't work if both cores are online.

Some interesting reading from Entropy512 here:

http://xdaforums.com/showpost.php?p=23193259&postcount=100

http://xdaforums.com/showpost.php?p=23194932&postcount=105

I get the impression that proper implementation of Deep Idle states is therefore limited to when the CPU is using a single core, and multi-core powersaving will depend more on hotplugging logic.
[Galaxy Note GT-N7000 Android Development] hotelier1984:
No need to wait 2-3 days for his kernel. You get that instant snappy feel from his Kernel within minutes after installation. It's not placebo effect too. Usually within an hour after flashing his new versions, your Quandrant scores could achieve at least 4000. Wait for a day and 5000 is doable, depending on your phone settings and other things. That's why i told my friends some miracle happen in the Note lately, and that's his Kernel. It's unbelievable fast, smooth, and low battery drain.

I am actually not sure whether these awesome user experiences are due entirely to the kernel or could be credited to my Kingdroid rom as well, but i do believe this kernel and Kingdroid have some kind of synergy when work together.
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
I think I will be talking on behalf of the majority when I say please do whatever you want as long as it will keep you motivated and continue to share your awesome effort with us here

Don't re- think anything
[Galaxy Note GT-N7000 Android Development] linuques:
Anyone else having problems with wifi reconnecting after sleep?
[Galaxy Note GT-N7000 Android Development] biliskner:
Just posting to say I support your beta method. Like others have said, ignore the ignoramasus who will post anything just to whinge. I find it funny you say "you can see for yourself in the OP re changes". Well, that's the problem, ignoramasus can't read, ESPECIALLY if it's in the OP. :)

Sent from my GT-N7000
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Intereating that entropy came to the same conclusion as me regarding the arm topology patch...but from different methods. i will look into the idle states available. would you like a link to the exynos 4 s.o.c manual its quite interesting if yoh havent seen it
[Galaxy Note GT-N7000 Android Development] musashiro:
is it possible that the kernel affects some widgets? like for example lock screen widget? i tried the widget on m brother's S3 and the widget works fine... way back on GB, the widget is ok but now that im on 4.0.4 + note core, tapping the widget locks the phone then it wakes up after locking. my phone doesn't wake up if i use the hardware button to lock..

another thing, digital clock disappears after some time..
[Galaxy Note GT-N7000 Android Development] birdfish:
+1, I use V12oc without any issues. I think it is very good for daily use for average users. Let the experts to test the beta for us and it saves me from flash addict.
[Galaxy Note GT-N7000 Android Development] dannycanrock:
Same here
[Galaxy Note GT-N7000 Android Development] birdfish:
Not the kernel. I think you are NOT using the stock TWlauncher. Some wigets are only working with the stock TWlauncher.
[Galaxy Note GT-N7000 Android Development] musashiro:
yeah, i removed the s3 launcher and the disappearing digital clock is solved. my only concern now is the lock screen widget, it wakes up after locking the screen.. weird...
[Galaxy Note GT-N7000 Android Development] atonal:
Hi Gavin,

Re Flashing yesterday my whole System new. Updating FW to LRK and switch to chracks Rom v11, but injecting the cleanote build prop. Kernel OFCOURSE Note core V12........

After flashing the Rom, I clear the init.d folder, except the scripts for zipalign.

Is this okay? Or did this also have negative influence to the kernel?

All sd read ahead scripts are cleared already....

And what's about fugutweaks..... (that's a script to get more sensibility on the touch screen, it's taken from the S3)

But my Device now with LRK Base and Note core Kernel runs like hell......

Got the OC Version and Voltage Table B. Got No Props with wifi or anything (not on any version, and I tried it ALL), for battery life its too short to make a report......

It's amazing........

Sorry, not using cleanote whole Rom, but last time I try, and have a boot loop two times and have to re flash complete. So this time I go the save way.... :) and I need a german csc code...

Greetz and thank you so much for this kernel.... From our german forum pocket.ch I can report also no bugs, just happiness :)

Greetz

Steff from Germany, Munich (Oktoberfest Capitol)
[Galaxy Note GT-N7000 Android Development] Akilesh:
Using v12 std now. Deep sleep battery stats is good. But drains when connected to wifi. Any fixes?

Sent from my GT-N7000
[Galaxy Note GT-N7000 Android Development] jamir5:
had the same issue.

go to security, screenlock choose none. :)

im just using jblockscreen. works fine.

try it :)
[Galaxy Note GT-N7000 Android Development] dipe7987:
Can I reset the binary counter with triangleAWAY app (http://xdaforums.com/showpost.php?p=22462960&postcount=1) with this v12 OC kernel + Stock 4.0.4 singapore ROM ???

does it safe or risky ???
[Galaxy Note GT-N7000 Android Development] and.traini:
Hello Gavin. Thanks for your hard work. I'm ignorant and I not have computer skills, but I hope that sooner or later you will have time to reject your experience of this kernel in a kernel for CM9 AOKP. If I come back from AOKP to stock and derived is only for the quality of your work!

Excuse my English! :thumbup:

Criskelo 11.2 - Notecore v12 - XXLRK
[Galaxy Note GT-N7000 Android Development] chasmodo:
It is safe. I've yet to hear of a single user having problems using TA.
[Galaxy Note GT-N7000 Android Development] ronfsp:
Mr Gavin,

Just as much as i wanna get my hands on the latest release of ur great kernel & try it out 1st hand, but having beta testing is also not a bad idea too. But have ur horsemen report to u thru PMs or other means rather than posting their testings here would be more approppriate as some ppl would feel left out, only having to read how good the beta versions r & not having a chance to test it out themselves.

& u can't deny the fact dat after all beta testings done & releasing it to the public, there will still be ppl posting i have this problem with V.XX, batt drain in V.XX etc... like u said b4, different phones running differrent ROMS, apps, tweaks would perform differently all together.

Juz a suggestion on ur criteria to be ur beta testers. To have ppl running on different ROMs. Imagine IF ur beta testers mostly running on ur ClearNote ROM or Kingdroid ROM. 1 guy came posting having problem after running ur kernel of a diferernt ROM. Then u'll be thinking after all beta testing no such problem, could it be ROM issue? Hope u know wat i mean Mr Gavin:) Cheers & continue ur good work!
[Galaxy Note GT-N7000 Android Development] dipe7987:
thx for the answer mate...so I dont need to buy the USB jig

answer from the pro :D
[Galaxy Note GT-N7000 Android Development] Berlino:
+1 :good:
[Galaxy Note GT-N7000 Android Development] Ottschke:
Always it's mentioned that it is the better choice to use a jig. At eBay it is only 2-5€. I tried it with a jig and it worked well.

Greetings from Germany
[Galaxy Note GT-N7000 Android Development] Lightysnake:
I've buy TA yesterday from Play Store and i've used with RRv9+NoteCore v11 the triangle is now gone without problems ;)
[Galaxy Note GT-N7000 Android Development] mustafaakk:
How do we play with voltage settings with these kernels ?
[Galaxy Note GT-N7000 Android Development] ardicli2000:
Tegrak, SetCPU whatever you like.

However, it is recommended not to do so...

Let the kernel do its job. Don't intervene.
[Galaxy Note GT-N7000 Android Development] sotmax:
agree...i d never used outside controllers..i m feeling like killing the battery and sometimes performance.
[Galaxy Note GT-N7000 Android Development] Ztrindberg:
Same here but maybe its Rom and not kernel?

Skickat från min GT-N7000

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

Yes me too

Skickat från min GT-N7000
[Galaxy Note GT-N7000 Android Development] mustafaakk:
There is no voltages tab in setcpu.

I played a lot with voltages on GB Rom.
[Galaxy Note GT-N7000 Android Development] pikaone:
Dude, your last cleanote and kernel done an orgasm to my gnote, incredibly smooth whaouh!!!
[Galaxy Note GT-N7000 Android Development] chasmodo:
Care to elaborate why "it is the better choice to use a jig"? And who is it that "always mentions it"? I'm genuinely curious.