yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] incisivekeith:
As you are testing it out, as a data point, here is some info: I couldn't run the 3d tests and google earth didn't run for me, so I think the standard kernel wasn't playing well with 3d stuff on my Note. I have reverted back to my old kernel for now, but will keep an eye on this thread.

Criskelo ICS LQ3 v8, LPT Modem, GL_NOTECORE_v1 kernel, AT&T
[Galaxy Note GT-N7000 Android Development] g.lewarne:
most likely that your phone does not like the GPU running at 400mhz at 1000mv (kernel default which is actually an undervolt)

this is corrected in the next version for the "STADARD" kernel only which is gpu locked at 267 with default voltage
[Galaxy Note GT-N7000 Android Development] brolee93:
with my team rom CM9 full theme tweaks etc etc .

@thor oc gpu at 400 same g.lewarne

i have 8000 on antutu

and 5000 with quadrant :)

in 1.664MHz :) directly UV stress and OC in init.d script by me :)
[Galaxy Note GT-N7000 Android Development] fil--21:
Can i use this kernel on miui leaked rom?
[Galaxy Note GT-N7000 Android Development] nikz106:
See the title.. it states its for TW-touch wiz ROM only..

Swyped from Galaxy Note
[Galaxy Note GT-N7000 Android Development] shaolin95:
Like Nick Burns would say " If you want it NOT to work then yeah!" But if you want it to work then no..this is for Samsung Roms. :p
[Galaxy Note GT-N7000 Android Development] g.lewarne:
2nd core will hotplug in whenever its needed. having it always on would be a MASSIVE battery drain lol :silly:

if you want to try set your governot to "performance"

v9.2 cooking tonight :good:
[Galaxy Note GT-N7000 Android Development] shaolin95:
As far as I recall Performance governor has not being working in a long time...I get horrible performance for it, unless you have done some work on it. :)

That goes for all ICS kernels I have tried, not yours only btw :)
[Galaxy Note GT-N7000 Android Development] androiadicted:
Antutu 10000? Sgs3 eat my dust?
[Galaxy Note GT-N7000 Android Development] fil--21:
Tnx for quick replay ....too bad i thougt becouse miui rom its based on original samsung rom and not on cm9 tnx :good:
[Galaxy Note GT-N7000 Android Development] bttcp12:
+1
[Galaxy Note GT-N7000 Android Development] fjdogar:
I am on Criskelo v9, after flashing notecore 9 my battery is draining faster when playing games.

When i attach usb with the otg cable the mobile networks is gone and comes back after a few seconds.

The phone is not going in deep sleep. So more battery drain in standby (battery drain in gameplay has also increased as mentioned above)

I dint hav these problems on notecore 7 so im getting back to v7 and wait for further development.

Notecore v7 is the smoothest, most responsive, coldest and best battery kernel i ever flashed.

Thanks for your efforts.
[Galaxy Note GT-N7000 Android Development] Nazar78:
Hi Gavin,

I'm just curious. For both CPU and GPU, your voltage changes are on the ASV group B. And this doesn't reflect on Tegrak. But when I made the volt changes on the ASV group A, Tegrak showed the changes correctly for both CPU and GPU.

Is Tegrak module reliable?
[Galaxy Note GT-N7000 Android Development] elk2210:
For me it seems like noop is more deep-sleep friendly as sio. Am I the only one who's "feeling" this? Could just be an accident...

Gesendet von meinem GT-N7000 mit Tapatalk 2
[Galaxy Note GT-N7000 Android Development] g.lewarne:
well, im going to be completely honest with you here....

I have NO idea how the tegrak module works. When i initially worked out the correct PLL values to inject to generate any FOUT frequency i wanted i was altering the ASV group A tables. Tegrak didnt see those changes. But when i edited group B tegrak did see those voltages. So i left it at editing group B

If you have any idea how that god forsaken CPU table file works and have better ideas for implementation by all means let me know.

Just on basic deductive reasoning (ie- change, compile and check with tegrak)

this section of code seems to be the "allowed" voltages and dont directly affect what voltage is set

static const unsigned int asv_voltage_A[CPUFREQ_LEVEL_END][8] = {
/*
*	SS, A1, A2, B1, B2, C1, C2, D
* @Dummy:
* @1200 :
* @1000 :
* @800	:	ASV_VOLTAGE_TABLE
* @500 :
* @200 :
*/
{ 0, 0, 0, 0, 0, 0, 0, 0 },
{ 1350000, 1350000, 1300000, 1275000, 1250000, 1225000, 1200000, 1175000 },
{ 1350000, 1350000, 1300000, 1275000, 1250000, 1225000, 1200000, 1175000 },
{ 1300000, 1250000, 1200000, 1175000, 1150000, 1125000, 1100000, 1075000 },
{ 1200000, 1150000, 1100000, 1075000, 1050000, 1025000, 1000000, 975000 },
{ 1100000, 1050000, 1000000, 975000, 975000, 950000, 925000, 925000 },
{ 1050000, 1000000, 975000, 950000, 950000, 925000, 925000, 925000 },

while the third column of this function seems to adjust the actual CPU voltages at runtime

static const unsigned int asv_voltage_B[CPUFREQ_LEVEL_END][5] = {
/*
*	S, A, B, C, D
* @1600 :
* @1400 :
* @1200 :
* @1000 :
* @800	:	ASV_VOLTAGE_TABLE
* @500	:
* @200	:
*/
{ 1350000, 1350000, [B]1350000[/B], 1250000, 1225000 },
{ 1350000, 1350000,[B] 1275000,[/B] 1250000, 1225000 },
{ 1325000, 1275000, [B]1200000,[/B] 1175000, 1150000 },
{ 1225000, 1175000, [B]1100000,[/B] 1075000, 1050000 },
{ 1150000, 1100000, [B]1025000[/B], 1000000, 975000 },
{ 1050000, 1000000, [B]950000,[/B] 950000, 950000 },
{ 1025000, 975000, [B]925000,[/B] 950000, 950000 },

};

now the REALLY weird thing is that Padne, who compiles his own from my sources has to edit the second column of values in the above function to changes his detected voltages according to tegrak.
[Galaxy Note GT-N7000 Android Development] Nazar78:
Yeah Tegrak never released his source and disappeared last I know of.

"Just on basic deductive reasoning (ie- change, compile and check with tegrak)" <-- That's what I did for both CPU and GPU to see if the changes worked. Which I found out the 1st asv_voltage_A doesn't do anything, only asv_voltage_B is doing all the changes.

Frankly I didn't even noticed this in your codes not till I was looking in the ICS Opensource Update4 to find the default voltages (I'm using STD version now aiming to UV further). And if I can recall correctly since GB, Tegrak module has been reflecting the voltages in ASV group A which is the 2nd column next to the ones you BOLDed above. Can anyone else confirm?
[Galaxy Note GT-N7000 Android Development] g.lewarne:
thats werid as when i change a voltage in the third column its reflects in my tegrak, but changing the 2nd columns doesnt......strange eh?

thinking about it - is is possible that column 2/3 reflect different motherboard versions? if motherboard v1 detected use column 2, if motherboard v2 detected use column 3

this *could* i suppose be the random cases of "heat" that only very few users report compared with the majority
[Galaxy Note GT-N7000 Android Development] Nazar78:
Really??? Weird indeed. I'm on Tegrak 1.9.4 driver version 5.2 and column 2 reflects all the volt changes and crashes due to my over UV.

Think you could be right, different mobo revision using different asv group set.

Guys, it will help Gavin improve this wonderful kernel if you can download the Tegrak free version and post the voltages reported for each frequency after you've loaded the overclock module based on GL_NOTECORE V9.

Edited: Also useful if you can tell where in the world you get your note from haha.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
THAT WOULD BE VERY HELPFUL INDEED!

since I only have my own note I can only test on mine :p
[Galaxy Note GT-N7000 Android Development] g.lewarne:
For me its definately 3rd column

by the way this is based on notecore v9.2 voltages which arent out yet, but im using the voltage tables I posted above so you can see for me its definately 3rd cvolumn!)
[Galaxy Note GT-N7000 Android Development] Nazar78:
Yeah, you made volt changes in the v9 standard, 1250,1200,1100,1025,950,925. Users with the same batch as yours should reflect the same volt "1250,1200,1100,1025,950,925" accordingly. But mine (I just reflashed your v9 official release)...

GL_NOTECORE v9 standard:

1.4Ghz - 1350mv

1.2Ghz - 1275mv

1Ghz - 1175mv

800Mhz - 1100mv

500Mhz - 1000mv

200Mhz - 975mv

Bought: Asia/Singapore (No idea imported from where but it states Samsung Asia)

Serial: RHCBB84778K (Settings>About>Status or check label under battery)
[Galaxy Note GT-N7000 Android Development] DJ-Tumor:
This Error was really NOT kernel related. It really was ROM related.

Since switching from FusionRom to ClassicRom voodoo louder works with same kernel version v7 & v9 !!!
[Galaxy Note GT-N7000 Android Development] sniperbr0:
sorry for being the black-sheep here, but can we have the STD version without voltage changes? dead trigger and fpse freeze here on V9, and it is not even warm at all
[Galaxy Note GT-N7000 Android Development] Ushh:
GL_NOTECORE & Cleaning scripts

Anyone that could help me on how to clean for a new kernel?

I've been following the thread for some time and I don't have clear how to do it without risk of bricking, I know this kernel is considered safe, but, I think you can never be to safe!, haha.

The thing is, I am on speedmod, it has been the only non stock safe kernel I knew.

I´ve been following the thread and I'm really itchy of trying notecore. I feel my battery life is no good for me with speedmod since version k3-3. I feel 8 - 12 hrs is not good for standard performance, Stable indeed, but standard. I am not blaming the kernel, it can be my setup, but I need to try different.

So, to get to the real question.

Anyone that can tell me how to use the cleaning scripts? which one should I use? are they really needed?

Should I:

1.- Get into recovery, flash abyss

2.- Reboot to recovery

3.- Wipe Dalvik/cache

4.- Flash ????? cleaning script

5.- Flash new GL_NOTECORE! (suggestion if its my first? ex? standard?)

6.- Reboot and enjoy?

Thank you.
[Galaxy Note GT-N7000 Android Development] ardicli2000:
Frequency Voltage (CPU)

1400 1250

1200 1200

1000 1100

800 1025

500 950

200 925

Frequency Voltage (GPU)

267 1000 (Level 0)

267 950 (Level 1)

Serail: RUYBA10576Y

United Arab Emirates

TRA ID: 0016333/08

TA: 000000000/00

BTW, v9std is far best for me. So cool and so battery efficient as weel as it s very stable, fast and smooth :thumbup::
[Galaxy Note GT-N7000 Android Development] lilien98:
1. - READ 1ST POST...

2. - Reboot into recovery

3. - Flash cleaning script (will wipe cache/Dalvik cache. No need to do it twice...)

4. - Flash Notecore standard

5. - Reboot and enjoy...

Just a "Note" with Tapatalk.
[Galaxy Note GT-N7000 Android Development] Ushh:
Re-read first post, nothing about cleaning scripts.

I've read in the thread that a lot of people use them, people that have been following gl_notecore/gavin's work. But as I have read, there is no "the one" cleaning script, there are many, so I was hoping someone could recommend me one and stick with it.

Also, I was asking if anyone could be too safe, better flash abyss first, then clean, Or is it REALLY NOT POSIBLE that running a cleaning script in speedmod or notecore (don't have notecore yet) could brick my device by any means!

And the last question is that if we need to run the cleaning script each time we change notecore kernel version?
[Galaxy Note GT-N7000 Android Development] play_dead:
Mine is a bit different from the table above. Running v9ex and got my phone in Hong Kong.
[Galaxy Note GT-N7000 Android Development] jeriz:
Every flash can potentially kill your phone but it probably wont so just do a nandroid and flash away. And i dont think you need a cleaning script since im guessing that you havnt done alot of flashing yet
[Galaxy Note GT-N7000 Android Development] hereu:
I got this from earlier in the thread and never had any problems flashing this kernel which updates often.

As long as your happy that Speedmod is safe (I'm as sure as can be that it is) then follow this...

Boot into CWM then

1. Apply jbroid

2. Flash new kernel

3. Reboot recovery

4. Wipe cache, davik and battery stat

5. Reboot

And try turning on/off wifi then reboot again by turn the phone off and on before start using.

HTH
[Galaxy Note GT-N7000 Android Development] ardicli2000:
If you are on stock ICS and not rooted, it means you do not need cleaning script.

Go to Dr. Ketan's root guide.

Use temporaray CWM method.

After you are rooted install HC-kTool.

Download the kernel .tar file.

Extract zImage to /sdcard.

Flash it via HC-kTool.

If you are rooted follow the steps starting from "install HC-kTool" step.

If you are on AOSP or AOKP or any CM Rom.

Flash fresh GB Rom via Odin. It is not worth to lose your Note instead of your Data.

Then either upgrade it via Kies or Odin.

Then follow the steps above, starting from rooting your phone.

If your are on Rocket Rom etc (TW based Rom) you can flash it directly. I believe it is not needed to use cleaning script. If you want to use it so badly, there are many people in the thread using it. Just read last 50 pages. o_O (Yeah 50 pages. It is your Note. Do not come here again with a bricked phone. But still as you wish of course.)

Regards.

Edit: I flash tihs kernel since v3. I am on Stock ICS and never flashed cleaning script. I also do not take it necessary. I have very stable and fast phone with very very very reasonable battery life. Just flash it. Erase your init.d scripts and use default build.prop.
[Galaxy Note GT-N7000 Android Development] Ettepetje:
NoteCore v9-EX has been working fine on 2 Notes here. AnTuTu was giving me a problem on a previous version (yellow screen where there should be colored "fog"), but updating AnTuTu solved this.

Nearly 8000 on AnTuTu and 5120 on Quadrant, clean (no cpu profiles or anything), amazing!!! :cool:
[Galaxy Note GT-N7000 Android Development] Nazar78:
Thanks, yes different from my note batch, yours is volt table ASV group B and mine is volt table ASV group A.

For v9STD/EX (ASV group A), 1.4GHz = 1350mv

For v9STD/EX (ASV group B), 1.4GHz = 1250mv
[Galaxy Note GT-N7000 Android Development] Ushh:
Thank you, I'm actually rooted 4.0.4 just installed 2 days ago, stock, only with speedmod k3-11.

I've been following Dr. ketan's thread since Gingerbread his guide is great. So I have flashed like 6 different roms, all stock, updated versions. Just root and that's it but since ICS and the brick bug I am a little more cautious with the things I don't understand completely. Thats why I knew speedmod kernel.

I am only looking for a safe kernel and good battery life.

But I must say that everyone in the thread is so excited with Gavins work that I must try it!!!

Now I have to do it!!! and I am just trying to understand what I have to do having 4.0.4 LRI and coming from speedmod kernel.

Thanks for the time to write all this. Appreciate it.

---------- Post added at 04:55 PM ---------- Previous post was at 04:49 PM ----------

we can do nandroids in ICS?

I have just flashed like 6 stock roms and speedmod kernels, I guess I am not, by any means an Expert, maybe only advanced user, still learning.

but well now my question is....isn't it a recommendation not to do nandroids with ICS kernels? when is it possible without too much risk?

Yes I KNOW IT SOUNDS INCREDIBLY NOOB! but i know the problem is still there! and I have a 0x19 version!!

---------- Post added at 05:00 PM ---------- Previous post was at 04:55 PM ----------
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Ok this is great. i have a group B phone so we need someone to find stable undervolt settings on a group a phone....and then....maybe.....1600mhz for everyone
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
I bought my note from Saudi

CPU:

1400MHz ==> 1250mV

1200MHz ==> 1175mV

1000MHz ==> 1075mV

800 MHz ==> 1000mV

500 MHz ==> 950mV

200 MHz ==> 950mV

GPU:

267 MHz ==> 1000mV

267 MHz ==> 950mV

using normal V9
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Thanks thats another group b like mine:good:
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
can't imagine i am been thanked by you when it should be the other way around :)

Glad i am in the same group like you , feels more safe , hehehehee :silly:
[Galaxy Note GT-N7000 Android Development] ardicli2000:
Since you are rooted follow the instructions starting from installing HC-kTool.

Flashing a kernel will not wipe anything. The program just wirtes the kernel. That's all. It is safe. (Of course except regular risks)

As far as I know nandroid backup does not wipe anything. And I did it three times with NoteCore.

Even wiping cache and dalvik will not harm your phone. Just wiping data/factory reset is dangerous. and which is generally related with ROMs not kernels.

And I still see no reason to flash cleaning script in your case.

Just to be sure ask for nandroid backup in Speed-mod kernel thread.Moreover, there are some people here switvhing from spped-mod to notecore. You can ask them too.

Regards.

@Nazar

Is voltage values same for you for both of the kernels, ex and std???
[Galaxy Note GT-N7000 Android Development] cook:
Nandroid backup is always safe. Nandroid restore need take care to have safe kernel.
[Galaxy Note GT-N7000 Android Development] Ushh:
Gavin's Extra awesomeness!

Ohh my God! now I see that "extra awesomness" Gavin was talking about!!!

I just took the plunge with helpfull answers from this thread, and flashed v9 std over speedmod k3-11.

It seems to be ok and.......the extra awesomeness comes alive! When I did, only being curious, a CF Bench and Antutu, out of the box CF Bench 4237!!! was 3725 before.

And Antutu....was 6051..........now is 7225!!!!

AND THIS IS THE STANDARD KERNEL!!!

I DON'T KNOW WHAT CAN I EXPECT FROM EX VERSION!!!

Ok, now I am excited too!!!

need more!!

haha!!
[Galaxy Note GT-N7000 Android Development] Nazar78:
Yes I'm seeing the same values for both version. But I have no problem with it cos l'm compiling the kernel from Gavin's source.

Hmm so far most reported from group B, hoping see others with group A. Else my note is one of the rare breed haha...​
[Galaxy Note GT-N7000 Android Development] hchxoom:
CPU:

1400MHz ==> 1250mV

1200MHz ==> 1200mV

1000MHz ==> 1100mV

800 MHz ==> 1025mV

500 MHz ==> 950mV

200 MHz ==> 925mV

GPU:

267 MHz ==> 1000mV

267 MHz ==> 950mV

Serial RF1C217XN7K

Germany online retailer

Cleannote 4 with v9std kernel
[Galaxy Note GT-N7000 Android Development] k4syx:
V table

v9 EX voltage tables (tegrak overclock):

CPU

1600MHz -> 1325mV

1400 -> 1250

1200 -> 1200

1000 -> 1100

800 -> 1025

500 -> 950

200 -> 925

GPU

400MHz -> 1000mV

267MHz -> 950mV

Poland (Europe), official Samsung dealer network.

Group A, right? How can I help?
[Galaxy Note GT-N7000 Android Development] hereu:
Your group B same as me.

Germany Amazon.
[Galaxy Note GT-N7000 Android Development] drakal:
For me, i have some troubles with EX version, so i OC the normal version with Tegrak, it's the same? Right?

My voltage:

1600-1275

1400-1225

1000-1050

800-950

500-875

200-775

GPU

400-1000

267-850

I use this voltage with ALL kernel since i have my note (4month) stable as rock.
[Galaxy Note GT-N7000 Android Development] bttcp12:
Goob I'm B like g.lewarne :laugh:.
[Galaxy Note GT-N7000 Android Development] nmah75:
lol
[Galaxy Note GT-N7000 Android Development] bttcp12:
I've tried GPU 267-850 and got freeze in nenamark2, I use:

400-1000

160-875

0 freezes :confused:, little differences in hardware ;).
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Interesting stuff.

Right now im compiling a kernel with adjusted voltages for group A phones that shoul hopefully allow everyone to have a stable 1600mhz. Meaning i only need to compile 1 kernel.

Will release it as beta once tested :good:
[Galaxy Note GT-N7000 Android Development] shaolin95:
awesome...count me in :)
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Anything less than 925@160mhz on my phone leads to hard crashes doing anything gpu intensive
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Well thats weird that those voltages are stable for you on a tegrak overclocked standard kernel as those are lower voltages than set in EX

Me thinks tegrak doing some funky stuff
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Based on our previous discussions via PM on this very matter of voltages im gonna bet you have a group A

Am i right :p
[Galaxy Note GT-N7000 Android Development] shaolin95:
A=Addict? :silly: Not sure what that is but I am willing to try anything you build so it does not matter :D
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Beta v9.2 Universal

Changelog

- Bit more VM readahead to 768/16

- Increaased GPU voltage @400mhz to 1050 to resolve those random 3d gaming crashes (i had these on some games) - haven't noticed any more heat as its only 0.05 of a volt

- Adjusted voltages for Group "A" phones to *possibly* enable stable 1600mhz for everyone

Please full nandroid before install, and have your current version of v9 available for PC-ODIN flashing via download mode if you get bootloops

If the the findings by Nazar (thanks!:good:) are correct, your voltages should read as follows

[B]CPU[/B] [B]Group "A" mv[/B] [B]Group "B" mv[/B]
1600 1375 1325
1400 1350 1250
1200 1250 1200
1000 1125 1100
800 1050 1025
500 975 950
200 950 925

DOWNLOAD : http://www.hecubus.com/xda/kernel/test/GL_NOTECORE_V902_Uni.zip

EDIT dont post under this! (until i upload the kernel)

EDIT 2:

HAHAHAHahahahahaha my current "triangle" binary counter is 32 :P (shows how many times i **** up and have to ODIN)
[Galaxy Note GT-N7000 Android Development] g.lewarne:
feel free to post again

NEED FEEDBACK ON THE ABOVE BETA
[Galaxy Note GT-N7000 Android Development] jjamain:
Look for jbroid/sybr kernel script cleaning..

It has link here http://jjpda.blogspot.com/2012/07/fusionrom-v25-notecore-v61-jb-roboto.html?m=0
[Galaxy Note GT-N7000 Android Development] kopitalk:
Have not tried yet but you may consider Sherlock Holmes & dr. Watson@221b Baker St. :p
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Cool i havebstarted to run out of ideas
[Galaxy Note GT-N7000 Android Development] bttcp12:
I have tried it extensively, and no crashes, in fact i've run nenamark2 with 875@160mhz in both levels of gpu, and no freeze, yeah only 29.0 fps, but for testing it works.

Going to try 9.2 :good:.
[Galaxy Note GT-N7000 Android Development] g.lewarne:
Yeah nenamark2 is a very useful tool for me. its a crappy benchmark but just being able to complete 5 runs in a row is a pretty good indicator that i got the voltages right for both gpu and cpu
[Galaxy Note GT-N7000 Android Development] drakal:
Not unstable with EX, but remenber few post ago, i'm stuck at boot or bootloop with EX, not with standard. I don't know why :/

But everything works fine with standard :)
[Galaxy Note GT-N7000 Android Development] silverstream:
I've a Singapore Set, Group B. v9STD/EX (ASV group B), 1.4GHz = 1250mv

Was not able to use Extreme in the past, and now with 9.2, completed Quadrant and Antutu at 1.6 WITHOUT problem !

(Just flashed, benchmark results are crap)

Am going to try Nenamark2 to stress test it.
[Galaxy Note GT-N7000 Android Development] bttcp12:
All ok with 9.2, but I'm in group b, and the special interest it's in group a :cowboy:.
[Galaxy Note GT-N7000 Android Development] shaolin95:
Gosh I need some rest...I read that you were creating a kernel with adjustable voltages instead of adjusted and I was looking how to change them until I read it again! :D

As for voltages, I dont think that is what is affecting mine unless it really needs 1425 like that other kernel. I somehow doubt that it can work with a kernel at 1325 without crashing if it really needed 1425 though :)
[Galaxy Note GT-N7000 Android Development] ChrisHaze1:
Had worse benchmarks with the new one (not reliable, just flashed and already warmed up (Q: 4000 average instead of 4800 average, Antu 6200 average Instead of 7800), but i liked the v9 with the lower voltage for the GPU better i think (maybe just because of that, i had no Problems in any game ;))

I will go on testing it, but i am group B too, so, well....