yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] DellKung:
first I flashed perseus via mobile Odin and it just hung at the mobile Odin screen. but when I use CWM, I have no problem. everything is fast and stable. no reboot yet.
[Galaxy Note II Original Android Development] AndreiLux:
Benchmarks like GLBenchmark are geometry heavy and the GPU is limited due to its single geometry processor, clocking the GPU higher won't scale linearly with frequency because it won't matter if the additional pixel processors are clocked higher as the bottleneck lies in the GP. This is the disadvantage of a non-unified architecture.

The resolution scores being the same are founded on the same problem, the PP's are plenty fast but they're never fully used as it's limited by the GP.
[Galaxy Note II Original Android Development] atonal:
New Version looks very good, stable and fast... But I got a permanently Problem with the stability of my Wlan connection. It reconnects all five Minutes, and then it lost connectivity for a part of a second.... I try different radios, but allways the same... Connection quality is very good... It looks like the problem at note 1,if you choose auto frequency (2,5/5ghz),this will reconnect also all five Minutes, that can be fixed by set it to a fix value (2,5ghz).but under JB, this option is not any more in wifi setup.....

I'm not sure, that it is a kernel problem... But maybe someone has the same problem...?

Another question is: Have anybody some recommended high end setups for STweaks, to push up the performance...? I got a lot of experience with cpu OC on Android and PC, but not on clocking Ram and internal Memory, so maybe, someone can give me some tips, to set the right values?

Thx and sry for my bad English... I'm from Germany, Munich...

By the way, someone from Germany test some radios, and know, what the best choice is for germany....?..

Thx and Greetz

Steff
[Galaxy Note II Original Android Development] _delice_doluca_:
Thank you for clearing the question marks on my head but now I have a new one. Since GLbenchmark is a good gaming simulation, there is no benefit of OCing the GPU?
[Galaxy Note II Original Android Development] AndreiLux:
Most games aren't as geometry heavy as GLBenchmark, anyway overclocking always will bring a boost, you don't lose anything, even power, as if the pixel processors are bottlenecked they'll just be idle for longer.
[Galaxy Note II Original Android Development] frankcilo:
After test for one day, great great kernel, great battery life!

No problem with light undervolt of mif and int:

#Customize the following 6 lines for mem_VOLT

echo "110110 147147 176176 293176 293220 440220" > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 110110 900000 > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 147147 900000 > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 176176 900000 > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 293176 950000 > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 293220 950000 > /sys/devices/system/cpu/busfreq/mif_volt_table

echo 440220 1050000 > /sys/devices/system/cpu/busfreq/mif_volt_table

#Customize the following 6 lines for int_VOLT

echo "110110 147147 176176 293176 293220 440220" > /sys/devices/system/cpu/busfreq/int_volt_table

echo 110110 875000 > /sys/devices/system/cpu/busfreq/int_volt_table

echo 147147 900000 > /sys/devices/system/cpu/busfreq/int_volt_table

echo 176176 925000 > /sys/devices/system/cpu/busfreq/int_volt_table

echo 293176 925000 > /sys/devices/system/cpu/busfreq/int_volt_table

echo 293220 1000000 > /sys/devices/system/cpu/busfreq/int_volt_table

echo 440220 1000000 > /sys/devices/system/cpu/busfreq/int_volt_table

Thanks Andreilux!
[Galaxy Note II Original Android Development] hkfriends:
N7105 has boot loop on verson 30.1 (Stock Rom LJ4)

please help...
[Galaxy Note II Original Android Development] betoNL:
How can we help you?

By giving you moral support perhaps?

Ok...Hang in there !

Btw, learn a thing or 2 before doing stuff on you phone...or at least...learn how to search...

.
[Galaxy Note II Original Android Development] DakiX:
CPU

MAX FREQUENCY, 1200MHz

MIN FREQUENCY, 200MHz

Undervolting:

200MHz, 837500

300MHz, 837500

400MHz, 850000

500MHz, 850000

600MHz, 850000

700MHz, 887500

800MHz, 912500

900MHz, 975000

1000MHz, 987500

1100MHz, 100000

1200MHz, 102500

CPU SCALING

Governor: pegasusq

SAMPLING RATE: 28000

UP THRESHOLD 81%

FREQUENCY FOR FAST DOWN, 1000MHz

CPU HOTPLUG

CPU UP RATE: 19 SAMPLES

HOTPLUG FREQ FROM 1 CORE TO ONLINE: 600MHz

HOTPLUG FREQ FROM 3 CORES TO OFFLINE: 400MHz

MEMORY/INTERNAL

INTERNAL VOLTAGE: 176MHz STEP, 950000

MEMORY VOLTAGE: 440MHz STEP, 1000000

GPU

UP THRESHOLD: 75%

DOWN DIFFERENTIAL: 17%

GPU VOLTAGE CONTROL:

160MHz, 925

266MHz, 925

350MHz, 975

440MHz, 1025

533MHz, 1125

I/O

INTERNAL STORAGE SCHEDULER: SIO

SD CARD SCHEDULER: CFQ

DYNAMIC FSYNC: ENABLE DYNAMIC FSync

AUDIO (who likes)

Speaker Tuning!

SPEAKER AMPLIFICATION OFFSET: 1

STEREO EXPANSION GAIN: 16

BAND1 GAIN, 4

BAND2 GAIN, 3

BAND3 GAIN, 2

BAND4 GAIN, 2

BAND5 GAIN, 3

OTHER SETTINGS: FLL TUNING, ENABLED

Better battery life without performance reduction. Guarantees on about 10h display-on :good: (What was not mentioned is standard)
[Galaxy Note II Original Android Development] Mad_Wolf:
When I plug the earphones music starts playing with the latest version ...

Anyone else has the problem
[Galaxy Note II Original Android Development] Nuvolaz:
Me too. But is not a kernel problem.
[Galaxy Note II Original Android Development] Mad_Wolf:
it is rom related ?
[Galaxy Note II Original Android Development] liqn7:
This is actually a feature/setting in the music player.

Poweramp for example you can turn this off/on.

Very useful when using your phone as a music source in a car with aux input.
[Galaxy Note II Original Android Development] snrbobo:
gonna give this a go! thank you sir!
[Galaxy Note II Original Android Development] _delice_doluca_:
Thanks again. Is there any way to OC the PP as well?
[Galaxy Note II Original Android Development] Mad_Wolf:
will also give it a try
[Galaxy Note II Original Android Development] b2rdetor:
not sure, but may be i got SOD on 30.1 - need more testing.

also hot reboot isnt works - it go to reboot and bootloop on bootanimation
[Galaxy Note II Original Android Development] kevin_diu:
Here's my settings.
[Galaxy Note II Original Android Development] Mad_Wolf:
System halted completely in menus
[Galaxy Note II Original Android Development] LittleH79:
Yeah me too :o
[Galaxy Note II Original Android Development] Mayday_XL:
Runs fine with stock settings.

Gesendet von meinem GT-N7100
[Galaxy Note II Original Android Development] twe90kid:
you need to remmeber that not all settings can be used on all phones. i would disable everything, set the settings... then enable it.
[Galaxy Note II Original Android Development] mrruin:
I left the voltage values untouched and changed the rest, working very well. Excellent smoothness. Thank you.
[Galaxy Note II Original Android Development] asderot5:
battery drain

for me a lot more battery drain with 30.1 compared to 29.1...
[Galaxy Note II Original Android Development] indigotheory:
A little bit more overnight yes
[Galaxy Note II Original Android Development] cobraboy85:
here are my thoughts on this post, as I see a lot of people merely adopting somebody else's settings without careful analysis. Not picking you apart dakiX, just clarifying so people understand. see my notes in the quoted post:

Also, if i may add this... I would recommend bumping the min frequency to something like 500MHz for the CPU. Reason being is simple - smaller tasks (maintenance, logging, etc) can be handled with ease without causing unnecessary CPU ramping. Meanwhile, setting your up_threshold value to something more aggressive like 70 or 65% will counteract tasks that actually DO require more speed by allowing the processors to scale before they are bogged down, effectively removing any latency in response time and throughput.

THIS is performance without battery life taking a hit - making your system AGGRESSIVE YET EFFICIENT, not hindering and crippling it to not do what it is programmed to do. Efficiency. "Less is more" as you see thrown around in the Linux world can also be thought of as more is less if you think in terms of more thought, tuning, and logic is less power consumed by your device.

:good:
[Galaxy Note II Original Android Development] retrorom:
kernel cleaning script?

Just out of curiosity, I've tried a few kernels so far, now sticking with Perseus though ...but is there any kernel cleaning script available for the note2? I didn't find anything yet, and also would like to know if it is even needed, when there will be one available.
[Galaxy Note II Original Android Development] DakiX:
Each CPU is different and of course it does not work every time, with a jerky it with this setting when there are other reboots so completely different on the same device, galaxy note II

At any rate: Good work AndreiLux !

FYI: With the app Android tuner you can still make a lot of tweaks in sysctl ;)
[Galaxy Note II Original Android Development] retrorom:
I turn off wifi and data connection over night and I lose 2% (+-8 hours) and this is on 30.1

That, to me is good :)
[Galaxy Note II Original Android Development] agentdark45:
Sorry to sound like a noob, but which settings are you advocating changing? I'm having a bit of a hard time following your post. Thanks man.
[Galaxy Note II Original Android Development] cobraboy85:
For the most part the ones mentioned in my post.
[Galaxy Note II Original Android Development] agentdark45:
You don't say...

My confusion lies here:

"Also, if i may add this... I would recommend bumping the min frequency to something like 500MHz for the CPU. Reason being is simple - smaller tasks (maintenance, logging, etc) can be handled with ease without causing unnecessary CPU ramping. Meanwhile, setting your up_threshold value to something more aggressive like 70 or 65% will counteract tasks that actually DO require more speed by allowing the processors to scale before they are bogged down, effectively removing any latency in response time and throughput."

Does "meanwhile" mean instead of, or in addition? And which "Min frequency" are you referring to?

So:

1. Set min freq to 500mhz AND up_threshold to 65%, or

2. Set min freq to 500mhz, leave up_threshold alone, or

3. Just increase up_threshold
[Galaxy Note II Original Android Development] honki24:
Okay so I increased freq for responsiveness to 600 on 30.1 and I'm still seeing the stuttering of playback from Google play. I was seeing hot reboots (my phone never comes out of hot reboot. Just blank screen after boot ani. For some reason that's never worked) with extended SNote usage but haven't used SNote today. I was surfing chrome a little while ago and it hot booted out of nowhere. I figured out how to get a dmesg. DB link: http://db.tt/NDx8wAqn

Note: totally stock settings on everything in stweaks.
[Galaxy Note II Original Android Development] fredli888:
I have a great battery life on 30.1 on default setting for n7105
[Galaxy Note II Original Android Development] AndreiLux:
The efficient part of your post is pretty much nonsense, those settings are aggressive and battery hungry. Setting min frequency that high screws with the cpupower scheduler settings, if anything stay below 500MHz as that's an internal threshold for biasing tasks on core 0.

You're recommending those settings for all the wrong reasons.

The runqueue depths never "switch" from one sample to another in such a fine granularity such that they would create some constant cycling. They're also averaged over a 134ms period per sample when requested from the scheduler and we store samples every 30ms so there's a trailing window taken into account for each runqueue depth. There's no real reason to have asychronous runqueue thresholds actually, it's just how Samsung originally delivered Pegasusq.

Anyway, don't worry, everything works as it should.
[Galaxy Note II Original Android Development] honki24:
Just got another reboot. Link: http://db.tt/bNjbRQbE
[Galaxy Note II Original Android Development] cobraboy85:
Well, I would respectfully disagree with you based on performance seen by setting parameters as mentioned and watching games stop stuttering and video playback smoothen out. It is still logic either way, a more aggressive CPU will increase responsiveness to work ques and execute tasks in a more timely manner.
[Galaxy Note II Original Android Development] AndreiLux:
Disagree with me on what?

I said those settings are battery unfriendly, I didn't argue they wouldn't be smooth. You can also use the performance governor and have extreme smoothness, but it's not optimal.
[Galaxy Note II Original Android Development] Bushido76:
Hey Andrei,

thanks for the i9300 emergency fix from last night. Do you know wether the N7100 could get effected by the emmc bug too? The N7100 seems to use the same chips/firmwares like the S3. In my case: VTU00M/0xF1.

Bushido
[Galaxy Note II Original Android Development] cobraboy85:
What is the use of having your processor run at max clock 24/7? That governor is useless and not anything to do with the point here.

My point is the settings I outlined specific to CPU adjustments - battery unfriendly, yes. Noticeably unfriendly, no. Which is my point. Not trying to argue with you here over semantics of what was implied. You understand my point. And I'm not trying to be disrespectful towards anybody in any way, just so we are clear. I was merely commenting on a post full of misinformation and bad advice. An aggressive UV, underclocked CPU, and IO schedulers that are not applied properly followed by "this will not degrade performance" lol...

Anyways, take it as you wish. I'm not trying to argue, just trying to enlighten.
[Galaxy Note II Original Android Development] SandeepEmekar:
After disconnecting phone call auto brightness doesn't work and it sets brightness to full.
[Galaxy Note II Original Android Development] dlt0rre:
two days with 30.1 on N7100 and no reboot and good battery life! Thanks!
[Galaxy Note II Original Android Development] baileyjr:
Same here, no random reboots on the new version so far :good:
[Galaxy Note II Original Android Development] shchiam1978:
Did you tweak anything or you just use the default values?
[Galaxy Note II Original Android Development] dlt0rre:
Default! :good:

I just change values when I notice lag or battery drain, but this time everything works great!
[Galaxy Note II Original Android Development] EdgaBimbam:
Hmm changed equalizer, made 300mhz as lowest cpu stage and no music stutter. Overall 30.1 so good release, no problems here with stock dll7
[Galaxy Note II Original Android Development] wl3gan:
I am interested to know the answer as well.
[Galaxy Note II Original Android Development] CitizenLee:
3.5 days with light-moderate use and no reboots to report. Samsung should ship this as stock kernel :)

Nothing changed in STweaks other than Audio stuff.
[Galaxy Note II Original Android Development] bervin:
Wow! your so smart and well versed in linux/android and the making things efficient why don't you do the note 2 community a huge favor and develop a kernel that is efficient by your standards for us, in my eyes andreilux in a very talented dev and i'm sure he knows what he's doing and if we were to take a look at credentials he has much more of that (on XDA at the very least) than you. So what i'm trying to say is he knows more than you.

I'll be looking forward to testing out your highly efficient kernel though once you've posted it on the original development forum! please make me eat my own words.:angel:
[Galaxy Note II Original Android Development] ilovemeow:
how long does it last from 100 to 20 or less? thanks :)
[Galaxy Note II Original Android Development] dlt0rre:
My use time is depends on the day, but I would say something like this:

2 days (about 3 hours of screen)

One day (5-6 hours)
[Galaxy Note II Original Android Development] ilovemeow:
1day is like 24 hr? coz mine only can hold for 10hr from 100 to 20 as 6hr screen on :( with -100uv
[Galaxy Note II Original Android Development] kastafela:
The best kernel ever :thumbup::thumbup::thumbup:
[Galaxy Note II Original Android Development] nyarnon:
Well andreilux is talented as far as the kernel goes. No one better IMHO he knows his stuff. That's why I accept him being acid. But if that's going to be the common tone here I out a here.

Verstuurd van mijn GT-N7100 met Tapatalk
[Galaxy Note II Original Android Development] Myriam77:
Is data on ? Anyway it seems ok with 6hours screen on at 20% ,you could reach 7hours for full cycle which is good I think .

I saw some people posting 8 to 10 hours screen on but I don't know how they do.
[Galaxy Note II Original Android Development] yahyoh:
Andrei do u think note2 is affected with SDS ? i have 0xf1 VTU00M eMMC :(

and do u think Sammy include the fix in XXDLL7 ( i really hope Sammy will release LL7 source soon :silly: )
[Galaxy Note II Original Android Development] shchiam1978:
Thanks

I am using default as well. Will see how it goes.
[Galaxy Note II Original Android Development] shrooms90:
I get up to 9 hours display time, only thing i do to save some juice is keeping my screen brightness as low as possible. But it depends on so many factors. If u live in a low signal area for example, u will never get those 9 hours.

Gesendet von meinem GT-N7100 mit Tapatalk 2
[Galaxy Note II Original Android Development] EdgaBimbam:
with surfing the net with wifi/3g you wont reach 8-10 hours of screen time, especially with 3g. For me mostly is 1.5day, 6:20 screen time,~ 5 hours music, 5:30 hours surfing the net and for me it is more than enough.
[Galaxy Note II Original Android Development] dajumper:
i want to know this also? before it is to late
[Galaxy Note II Original Android Development] SirCanealot:
For people having music stuttering problems:

Try not using the stock player app. I use clean music from the play store and it's a fantastic, bare bones solution that is all you need on such a fantastic audio chip. (it also directly reads the file structure rather than relying on the media scanner which randomly stopped seeing some of my folders...)

I used to get some stuttering with the stock player, but the stock player also used to take 4 hours to open a folder from my micro sd, so I stopped using it. It works, but it's bloated and crap...

Btw, I'm getting simply ridiculous battery life with 30.1. Performance is more or less perfect too. I was thinking about trying some of these tweaks for more responsiveness, but then I've decided Andrei is awesome and I'm also going to start stalking and dressing like him. Thanks. (translation: I cba when the defaults are almost a perfect balance already :p)
[Galaxy Note II Original Android Development] betoNL:
What you mean exactly? If a developer is super talented and delivers, other users cannot have different points-of-view and post them?

What is a discussion thread for?

If you have been following cobraboy58 was inicially reacting to another post and warning users here, about those potentially very unstable UV settings, and was thanked for it :

http://xdaforums.com/showpost.php?p=36459511&postcount=1705

In the other hand I tend to agree with AndreiLux regarding the total efficiency picture (balance between performance and energy efficiency or something like that) regarding "setting the min frequency to something like 500MHz for the CPU" suggested by cobraboy58

When I was using the Note1 running harcore's kernel, I set the minimum frequency to 500MHz without any negative impact on battery performance and I kept it like that. The total efficiency thing was great.

But the Note 2 is a whole different ball game, so I will be doing my own testings regardless the differents points-of-view and how interesting and impressive they sound

Remember that not every Samsung device is the same and afaik OP doesn't even own a Note2, so every feedback/discussion is useful

Even if you are no Linux/Android expert , no developer or no super-advanced user, you can learn a lot based on a trial-and-error basis.

And the discussion between Andrei and cobraboy was at least interesting.

Now , comments like "he-is-a-talented -recognized-developer-and-he-knows-always-better or he-"knows-more- than-you " is pure fanboy behavior which adds nothing to any discussion thread...

What I mean is how interesting the different points-of-view are and how recognized a developer is......

(whole post: http://xdaforums.com/showpost.php?p=21889564&postcount=88 )

...always keep an open mind , do your own testings, because, as I said before not every device is the same and every usage/need is different .....

And remember that developers are no gods :laugh:

.
[Galaxy Note II Original Android Development] moraize:
People:

I´m using Now Omega Rom V 10

on Stock kernell, on camera 4.2.1, after taking a Picture, I drag the finger on the screen from right to left and I go Straight to the picture taken. Drag from left to right returns to the camera.

After installing Perseus 29 it DOES NOT functions any longer !!!

Anyone could test it on new V10 (or any rom that install camera 4.1.2, the one that take 360º pictures) and perseus 30 ??

Thanks...
[Galaxy Note II Original Android Development] duowing:
So far so good with this kernel, haven't had any problems with reboots yet, but I also was only seeing reboots maybe once a week. Anyway, it's probably more a coincidence rather than the kernel, but it seems like I'm consuming a little bit more battery overnight than when I was on 29. The best I've ever seen was leaving my phone with data turned on over night, set my custom reference, and go to sleep. I managed .3% loss per hour. I seemed to pretty consistently get .6% or less battery loss. Day before on 30.1 best I've gotten so far, and this is only with mobile data on is .5%, then this morning I woke up to .8% loss. I haven't changed anything, I'm seeing less cpu sleep time than normal, but I really am not sure if the kernel has anything to do with it. Anyway my actual battery drain when actively using the device seems to be better so I'm really happy with this kernel so far. Seems very smooth, games seem to load quicker, no problems with music, and as mentioned no reboots so far.

Also Andrei I'm sure you've seen it, but as a few others have asked do you have any opinion on the emmc brickbug for the Note II seeing as the Internal memory and revision match that of the 16gb S3? If anything it could just maybe be a way those i9300 memory chips were initially flashed or firmware differences? Maybe even they were manufactured slightly different?