http://www.sammobile.com/2013/04/19...9500-gt-i9505-sgh-i337m/#.UXFYHqYLuCk.twitter
This is great news! CM 10.1?
winwiz said:
http://www.sammobile.com/2013/04/19...9500-gt-i9505-sgh-i337m/#.UXFYHqYLuCk.twitter
This is great news! CM 10.1?
Click to expand...
Click to collapse
AOSP at the very least...
AWESOME!!!
I will be updating in this thread shortly about proper information about the last unknown things concerning the phones...
Edit: How big is this thing?!
Edit: 372mB, they included various new things in their platform sources, seems they released the source for the Samsung Browser which seems to be the bulk of the increased size.
The 5410 now has proper independent power-gating in its CPUIdle driver.
The CPUFreq driver is populated from 200MHz up until 1300MHz for the A7 cores and 2000MHz for the A15 cores in 100MHz steps.
The shipping CPU already is in its second revision REV_2_0.
The shipping frequencies are 500MHz to 1200MHz for the A7 cores, 800MHz to 1600MHz for the A15 cores.
EDIT: When the IKS is active, which means at all times, then the CPU is set up to run in "turbo"-like configurations, if 1 A15 is active, max frequency is 1800, 2 are active, it is 1700, if all >2 big CPUs are on, 1600MHz is the maximum frequency. I'm still reading through the max index they setup there so I can't confirm this behaviour yet, but it's there in the code.
EDIT: The above logic seems to be disabled any only valid once the CPU was actually set to 1800MHz as maximum, there is no turbo at max of 1600MHz. This probably explains the previous benchmarks and so on of it showing 1800, but never reaching those frequencies.
Hotplugging seems to be DEAD! Finally!
The GPU _is_ running at 532MHz. There is a define for to ommit the last frequency step in the driver and limit it to 480MHz, however, in the released source this is not used and the frequency is 532MHz.
Code:
#define DOWN_STEP_OLD 1100000
#define DOWN_STEP_NEW 600000
#define UP_STEP_OLD 550000
#define UP_STEP_NEW 600000
#define STEP_LEVEL_CA7_MAX 600000
#define STEP_LEVEL_CA15_MIN 800000
if (freqs[cur]->old <= UP_STEP_OLD && target_freq > UP_STEP_NEW)
target_freq = STEP_LEVEL_CA7_MAX;
if (freqs[cur]->old >= DOWN_STEP_OLD && target_freq < DOWN_STEP_NEW) {
if (strcmp(policy->governor->name, "ondemand") == 0)
target_freq = STEP_LEVEL_CA15_MIN;
else
target_freq = STEP_LEVEL_CA7_MAX;
}
if (cur == CA15 && target_freq < freq_min[CA15]) {
do_switch = 1; /* Switch to Little */
} else if (cur == CA7 && user_set_eagle_count > get_num_CA15()
&& target_freq > freq_max[CA7]) {
do_switch = 1; /* Switch from LITTLE to big */
if (count > 0 && count < 4 &&
target_freq > exynos_info[cur]->max_op_freqs[count + 1])
later = true;
}
This is basically the switching logic. The A7 cores are mapped to the A15 frequency at half speed, the frequency table as such means it's 1:1 A15 clocks up until 1200MHz.
There are two conditions to switching from A15's to A7's:
An A15 core will need to be above 1100MHz (real) for the previous sampling period, and the new (current target) virtual frequency to be below 600MHz (1200MHz A7) to trigger an override of the CPUFreq logic and initiate a jump from A15 to A7's, however it doesn't directly switch: Ondemand is the default governor, so what it seems to be doing is to have a stop-over at the minimum A15 frequency / 800MHz for a frequency period and let the next sample decide what to do.
An A7 core will need to be at 550 virtual (1100MHz A7) for its previous sampling period, and over 600 virtual (1200MHz A7) to switch to an A15 core, however again, this is not the actual switching, it's sitting again for another sample at 1200MHz real frequency before it lets the next sample decide.
The actual switching is simple: if frequency reaches 800MHz, we go to A7's, if it goes to 650 (1300 == freq_max[CA7]) it goes to A15.
The whole thing is a bit shenanigans in logic, but I suppose they do it so that the cores don't do too much fine-grained switching and the above logic flattens out the frequency jumps.
EDIT: There's plenty of evidence of a global LTE enabled 5410 device, the kernel even has the usual modem drivers for it and GPIO board definitions.
I think most of the more interesting stuff is already cleared up now.
Does this mean that i9500 owners will be able to clock up to 1.8 to keep up with those fancy Koreans?
AndreiLux said:
I will be updating in this thread shortly about proper information about the last unknown things concerning the phones...
Edit: How big is this thing?!
Edit: 372mB, they included various new things in their platform sources, seems they released the source for the Samsung Browser which seems to be the bulk of the increased size.
The 5410 now has proper independent power-gating in its CPUIdle driver.
The CPUFreq driver is populated from 200MHz up until 1300MHz for the A7 cores and 2000MHz for the A15 cores in 100MHz steps.
The shipping CPU already is in its second revision REV_2_0.
The shipping frequencies are 500MHz to 1300MHz for the A7 cores, 800MHz to 1600MHz for the A15 cores.
Click to expand...
Click to collapse
I'm trying to DL the 9505 sources atm, 28 KB/s on a 50+ Mb/s line, come on Samsung:crying: On the octa, is the voltage table populated for frequencies over 1600 MHz?, if so is there a big jump?
Turbotab said:
I'm trying to DL the 9505 sources atm, 28 KB/s on a 50+ Mb/s line, come on Samsung:crying: On the octa, is the voltage table populated for frequencies over 1600 MHz?, if so is there a big jump?
Click to expand...
Click to collapse
LOL i tried to download the 9500 source but the download speed ridiculously slow ( 20KB - 50KB ) WTF my download speed normally about 1.4MB
they seems only have 1MB LINE for the server :silly::silly::silly:
edit : Andrei how the voltage table, is it much lower than Exynos 4412 ( 32NM vs 28NM ) ? what 1.6GHz voltage ?
and can u check what the DAC model ? is it Wolfson 5102?
Turbotab said:
I'm trying to DL the 9505 sources atm, 28 KB/s on a 50+ Mb/s line, come on Samsung:crying: On the octa, is the voltage table populated for frequencies over 1600 MHz?, if so is there a big jump?
Click to expand...
Click to collapse
They're populated, but only with a dummy 1300mV max value.
I got both sources at 900kB/s so I guess I got lucky before everybody and their grandma started downloading them for kicks.
Lets go!!!!!
So is this better than with the S3 because everyone was complaining about missing kernels and incomplete source.
samsung seems to have stepped up. the 9500 should be OC'd in short order.
What about the freqcheck, how often is it sampling to change the frequency?
If this is good....yup.
I never have a Galaxy, so i dont know...lol
Did Samsung finally release proper sources with documentation?!?!?!?!
If so, I really hope they will do the same with the Note II and S3 quickly!!!!!!
AndreiLux said:
EDIT: There's plenty of evidence of a global LTE enabled 5410 device, the kernel even has the usual modem drivers for it and GPIO board definitions.
I think most of the more interesting stuff is already cleared up now.
Click to expand...
Click to collapse
Does it means that i9500 could be LTE capable?
Inviato dal mio GT-I9000 con Tapatalk 2
DubelBoom said:
Did Samsung finally release proper sources with documentation?!?!?!?!
If so, I really hope they will do the same with the Note II and S3 quickly!!!!!!
Click to expand...
Click to collapse
I think you should read more into the whole sources and documentation story, you obviously don't get it.
Long story short, these are kernel sources and not the sources the CM team needs.
Stevemeister said:
I think you should read more into the whole sources and documentation story, you obviously don't get it.
Long story short, these are kernel sources and not the sources the CM team needs.
Click to expand...
Click to collapse
I don't understand the technical info (English is not my mother language, and definitely not at tech things), but I did knew something was missing. Sadly, its not this
Thanks!
AndreiLux said:
I will be updating in this thread shortly about proper information about the last unknown things concerning the phones...
The GPU _is_ running at 532MHz. There is a define for to ommit the last frequency step in the driver and limit it to 480MHz, however, in the released source this is not used and the frequency is 532MHz.
Code:
#define DOWN_STEP_OLD 1100000
#define DOWN_STEP_NEW 600000
#define UP_STEP_OLD 550000
#define UP_STEP_NEW 600000
#define STEP_LEVEL_CA7_MAX 600000
#define STEP_LEVEL_CA15_MIN 800000
if (freqs[cur]->old <= UP_STEP_OLD && target_freq > UP_STEP_NEW)
target_freq = STEP_LEVEL_CA7_MAX;
if (freqs[cur]->old >= DOWN_STEP_OLD && target_freq < DOWN_STEP_NEW) {
if (strcmp(policy->governor->name, "ondemand") == 0)
target_freq = STEP_LEVEL_CA15_MIN;
else
target_freq = STEP_LEVEL_CA7_MAX;
}
if (cur == CA15 && target_freq < freq_min[CA15]) {
do_switch = 1; /* Switch to Little */
} else if (cur == CA7 && user_set_eagle_count > get_num_CA15()
&& target_freq > freq_max[CA7]) {
do_switch = 1; /* Switch from LITTLE to big */
if (count > 0 && count < 4 &&
target_freq > exynos_info[cur]->max_op_freqs[count + 1])
later = true;
}
Click to expand...
Click to collapse
Strcmp? An unbounded string compare Samsung? For Shame.
Cali3350 said:
Strcmp? An unbounded string compare Samsung? For Shame.
Click to expand...
Click to collapse
... so? The whole Linux kernel might have a word or two with you on the matter http://lxr.free-electrons.com/ident?i=strcmp
I did not download the source, but it clearly says "kernel"source. Isn't the issue that the drivers in the SGIII were not open sourced, yes, the Exynos non-support was an issue, but is there enough in this source release?
Cali3350 said:
Strcmp? An unbounded string compare Samsung? For Shame.
Click to expand...
Click to collapse
Why shame? It compares with literal bounded string. Not more dangerous than strncmp with wrong length.
Sent from my GT-I9300
Hats Off to AndreiLux :victory: to you man
Related
Right so I posted this in both the kernel thread and the overclock thread but nobody saw it so I'll just post it again:
While looking at the vogue forum, I found a thread about GPU overclocking : http://forum.xda-developers.com/showthread.php?t=697673 the changes made to the kernel to enable this are the following: http://git.linuxtogo.org/?p=groups/...ff;h=23ff83048726252bc785699fc749a3e364a3bdb0
Unfortunately I am no programmer and I do not see how to incorporate this code in to kernel sources for MSM7xxxA processors, though it should probably work because the gpus of A and non-A processors are pretty much the same (same basic specs such as number of triangles etc.), so if a kernel dev. could try to integrate this patch, that would be awesome.
this really looks like some awesome stuff! i hope someone can figure this out for the g1. thanks for supporting the g1 thread!
GPU overclocking
Holy crap, a dev should take a look at that source NOW
agreeeeed^
just saw this thread for the first time.
gona take a look
Even though its a good idea in theory..
Once you start over clocking the GOS you really gona kill not only battery life, but your phone will be able to cook eggs lol
Thanks kingklick, hopefully you'll figure it out so we can run newer 3D games better, as for overheating, dzo (who created this modification) says that he hasn't noticed anything differences in temperature after overclocking the GPU on the Vogue
It will be cool if someone can overclock the GPU , these days everybody is talking about overclocking the cpu , but what allot of people do when they are traveling is playing games, some games we cant play because they are a little bit to heavy for the GPU. Kingklick thanks for looking at this topic,
personally I have really much confidence in you!
For this to work.
Someone has to implement this for MSM72XX, which is completely different than what's in the TI phones.
I am not sure if that code is even in the kernel (GPU clock). I don't recall seeing it but I haven't really looked at the kernel all that much.
It's all in the board files if it's anywhere.
/arch/arm/mach-msm/
Are you sure it's safe to OC the GPU?
It's not like we're using a adreno or Power VR in these phones. Also doesn't android use the CPU for things like scrolling,animations,swiping,etc...
For this to work.
Someone has to implement this for MSM72XX, which is completely different than what's in the TI phones.
I am not sure if that code is even in the kernel (GPU clock). I don't recall seeing it but I haven't really looked at the kernel all that much.
It's all in the board files if it's anywhere.
/arch/arm/mach-msm/
Click to expand...
Click to collapse
Um, the HTC Vogue (or Touch CDMA) AFAIK uses the Qualcomm MSM7500 which pretty much has the same GPU, just clocked slower than in the MSM7XXXA series, so I think it's just a case of recoding the modifications made by dzo (android kernel developer for the Vogue) for other phones.
The GPU code for the MSM chips is in /drivers/video/msm/gpu/kgsl/
I haven't looked at any of the code much, but kgsl.h defines some structs for what I think are clock values and in kgsl.c it contains:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_enable(kgsl_driver.imem_clk);
clk_enable(kgsl_driver.grp_clk);
}
Which to me looks a lot like its setting the GPU clock at 128Mhz.
Just my $.02
Geniusdog254 said:
The GPU code for the MSM chips is in /drivers/video/msm/gpu/kgsl/
I haven't looked at any of the code much, but kgsl.h defines some structs for what I think are clock values and in kgsl.c it contains:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_enable(kgsl_driver.imem_clk);
clk_enable(kgsl_driver.grp_clk);
}
Which to me looks a lot like its setting the GPU clock at 128Mhz.
Just my $.02
Click to expand...
Click to collapse
I modified this on the Eris's kernel to 160000000 and ended up with slower benchmark scores in both Neocore and Quadrant. So... possibly not that.
ivanmmj said:
I modified this on the Eris's kernel to 160000000 and ended up with slower benchmark scores in both Neocore and Quadrant. So... possibly not that.
Click to expand...
Click to collapse
Can you try others like:
352x
480x
176x
245x
Ace42 said:
Can you try others like:
352x
480x
176x
245x
Click to expand...
Click to collapse
384 gave me close to normal speeds but still slower than 128... 160 was slower.
It doesn't make sense.
If overclocking the GPU is anything similar to the CPU, then shouldn't we be using multiples of 19.2? instead of 128, try 147.2 or 176.4 etc....
mejorguille said:
If overclocking the GPU is anything similar to the CPU, then shouldn't we be using multiples of 19.2? instead of 128, try 147.2 or 176.4 etc....
Click to expand...
Click to collapse
But the stock is set to 128, which is not a multiple of 19.2.
If messing with it caused the phone to go slower, then it must be possible to mess with it to make it go faster.
dzo, linked me to his commit and it doesn't correspond to anything in the eris source.
http://androidhtc.git.sourceforge.n...;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
Time to poke around...
Owning both a Kaiser and a G1, the Kaisers 3D is actually faster. A lot of apps render quicker and smoother. Games play better too.
Would be nice if someone could pick this up, and get some over clocking action going for the GPU. Even without the overclock, my Kaisers GPU seems so much faster, but yet it's a weaker GPU then what my G1 has.
I realize this may be pushing it but I was wondering where the MIPS or BogoMIPS value resides and if it can be altered? Clearly it defaults to a value just below the stock max core value. However if I am running an OC kernel, can MIPS be raised a little safely?
I think BogoMIPS (or Bogus Millions of Instructions Per Second) is simply a reported stat, rather than calculated on the fly.
However, it has a linear relationship to the CPU frequency, so you can calculate it yourself.
13.53/1512 = 0.0089484126984127 [This is the ratio of MIPS to MHz]
So, 0.00894841 * 1836 = 16.43 MIPS at 1.836GHz. That is per a core.
MIPS is sometimes jokingly referred to as "Meaningless Indication of Processor Speed" because it doesn't really tell you much.
ReedX50v said:
I think BogoMIPS (or Bogus Millions of Instructions Per Second) is simply a reported stat, rather than calculated on the fly.
However, it has a linear relationship to the CPU frequency, so you can calculate it yourself.
13.53/1512 = 0.0089484126984127 [This is the ratio of MIPS to MHz]
So, 0.00894841 * 1836 = 16.43 MIPS at 1.836GHz. That is per a core.
MIPS is sometimes jokingly referred to as "Meaningless Indication of Processor Speed" because it doesn't really tell you much.
Click to expand...
Click to collapse
Wow, I m so impressed with that answer...lol
But, unless I'm mistaken,, isn't that the value used as boot clocking? What process determines this?
Read.
Mips: http://en.m.wikipedia.org/wiki/Million_instructions_per_second
Bogomips: http://en.m.wikipedia.org/wiki/Bogomips
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Read.
Mips: http://en.m.wikipedia.org/wiki/Million_instructions_per_second
Bogomips: http://en.m.wikipedia.org/wiki/Bogomips
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
If you didn't know, I would have held off replying, really. If your saying look harder/elsewhere, I'd say that this was a convo w reed that I brought out of a diff thread because it strayed from relevance there. I assure you that this isn't one of those cases of a noob asking about a stupid/well established fact. It took me 3 months and only 8 posts to get reg status because I ask intelligent questions. Seeing as you had to try and direct me off site to a couple of by then useless links means it isn't over asked nor do you know or know where the answer is. Useless links because Reed had already condensed those wiki links already in his post. So You didn't read? lol
Bump
... retracted ... one of us can be nice
Good day everyone.
After extensive testing I found the best voltages for our nexus 7 cpu.
those tweaks have been made with the kernel m13
ive tested and compared different voltages behavior and found that in almost every kernel and or roms , the voltage is too high and thisis not for the benefits of performance nor stability.
So ive started to underclock and watch the behavior of the N7 and found the perfect settings.
PS : If someone have better settings to share please feel free. Ill not try to push my idea. but yet i found it was the most better settings.
Sent from my Nexus 7 using xda app-developers app
for me this is absolutely useless due to the fact cpus are not the same,never and never will be,and voltages optimal for someone can give bootloop to others...a more accurate thing could be do 3 set of voltages optimization related to the 3 variant known of tegra3 t30,variant 1 2 and 3.e known that differences between 3 variants are the power needed to operate withpour rebbot..when variant 3 support and run at high frequencies with predefined voltage,the same freq. on variant 1 need more millivolt to run..with these 3 division,you can list 3 mode of undervolts,i think it's more usefull that now,but you can trace only yours variants in this mode..let's see if the 3ad will grown and others users with other variant will write its best voltages.just my 2 cent mate!
hi!:good:
Just tested SIMILAR voltages (the frequency steps were not all the same, most 30 Mhz off) on Trinity 4.2 alpha0 and it works great so far, we will see if I get soft resets or bootloops, but I hasn't yet do I don't think it will.
With this kind of information, can you PLEASE include the Tegra variant information? Because not all of us are lucky enough to have a variant 3 (as I suspect you have, with that kind of undervolting)...
Take my nexus 32gb for example, it's a standard Variant 1, and 1090mv at 1600MHz would most definitely result in problems if I pushed it hard at that level. I can just barely get away with 1150-1200mv at 1600... I suggest you run the stress testing/burn in application to make sure your voltages are stable as well
APplication is called "Stability test" and it will push your CPU/GPU to the max. If it runs continuously without any issues at that voltage level, you're fine..
See, I can set 1090mv at 1600MHz no problem on my variant 1, but if I run Stability test, I'll get a lock-up after 2-3 passes or so. By the same token, I'll get a lockup running glow ball and other intensive games. Just because it runs stable during a benchmark / every day use, does NOT mean it's stable.
Here's a link ot stability test: https://play.google.com/store/apps/...=W251bGwsMSwxLDMsImNvbS5pbnRvLnN0YWJpbGl0eSJd
Those of us who do a lot of overclocking on the PC etc know how important it is to "burn in" test your overclocks to make sure they are absolutely stable. This usually means running a linpack or other such intensive burn-ins overnight.. and you don't consider it 'stable' until it runs a LONG time, with no errors.
how do u know which variant you have?
BurnOne77 said:
how do u know which variant you have?
Click to expand...
Click to collapse
You have to be using a kernel that exports this info... I know Faux's does FOR SURE, and I think a few others have actually merged that over into their own kernels.
It would be under /sys/kernel/debug/t3_variant, I believe. So, as root, you can cat /sys/kernel/debug/t3_variant or just browse via ES file explorer or root explorer or whatever root file explorer you choose. The variant is the cpu_process_id
Each variant more than likely is based on where on the wafer or whatever the chip came from, meaning higher quality.... what it boils down to is the higher the variant, the more likely you'll be able to run at a higher frequency with less power.
Here's the post on the One X forums about Tegra 3 variants, http://forum.xda-developers.com/showthread.php?t=1815466
Lots of good information there.
I'd really like to see the OP run multiple passes of Stability test going 1600MHz at 1090mv, though. If you can do that, you have one exceptional chip, and you're very lucky. Remember just because something is stable in everyday use, doesn't mean it's truly stable.. very little that you do will actually stress the GPU/CPU to the max at the same time, which is the only thing that will truly show if you have problems with undervolting. I'd make a habit of running stability test for at least 5-8 passes (I like to do many more than this) to make sure an undervolt is at least somewhat stable.
If you simply say "This is the BEST! Why isn't everyone doing this? Why do kernels set the voltage so high?!" and have everyone simply drop down to those levels, you're going to have a TON of people who will start having issues. There's a reason why they are set that way. If everyone could easily get away with undervolting this much, it would be a no brainer to make it the default...
Good evening everyone.
ill look for the variant asap and will also runs the stress test as suggested. Even if it did well so far ill post accurates testing results besides the performance quadrant test.
cheers mates
Sent from my Nexus 7 using xda app-developers app
stress test so far
at the end i was tired running it but for now no errors or crash
due to some heat generated after 10 minutes the CPU dropped to 1400mhz instead of 1600. I was on performance mode.
edit : ill try to find my cpu/gpu variant. and post it. i am not sure wich application could give me an accurate information but i am actively searching.
Cheers
ok so i found the tegra3 variant. i am posting the results
cpu_speedo_id => 7 soc_speedo_id => 1 cpu_process_id => 0 core_process_id => 0
Sent from my Nexus 7 using xda app-developers app
sert00 said:
for me this is absolutely useless due to the fact cpus are not the same,never and never will be,and voltages optimal for someone can give bootloop to others...a more accurate thing could be do 3 set of voltages optimization related to the 3 variant known of tegra3 t30,variant 1 2 and 3.e known that differences between 3 variants are the power needed to operate withpour rebbot..when variant 3 support and run at high frequencies with predefined voltage,the same freq. on variant 1 need more millivolt to run..with these 3 division,you can list 3 mode of undervolts,i think it's more usefull that now,but you can trace only yours variants in this mode..let's see if the 3ad will grown and others users with other variant will write its best voltages.just my 2 cent mate!
hi!:good:
Click to expand...
Click to collapse
No offence OP, but this.
All CPUs are created differently, they won't behave the same at the same voltages. What might be stable for someone may be unstable for someone else. Take clemsyn's kernels for example, they are undervolted to the extreme so they might be stable on one device but not even survive a minute on another device.
So what works for you might not work for someone else. So maybe take the values in the OP as a guide, not as the "best performance and batt life without sacrifices". That might be a bit vague for some.
Within a single variant there might be chips that withstand less voltage than others too
Anyway, as the great kernel dev faux123 said:
faux123 said:
Not All CHIPS ARE CREATED EQUAL
Click to expand...
Click to collapse
Peace!
Mark
jsmasterx said:
ok so i found the tegra3 variant. i am posting the results
cpu_speedo_id => 7 soc_speedo_id => 1 cpu_process_id => 0 core_process_id => 0
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! Have you switched kernels at all lately, or anyhthing like that? Because I believe you're suffering from the same bug that I am.
When I switched from Faux's kernel to M-Kernel, my variant also reports as "0" when it was very clearly a "1" before.
If you really do have a variant 0 chip that is hitting 1600MHz reliably at 1090mv then you're one of the luckiest people around! haha. But like others have said, no two chips are created equal, it appears you have a very very good one.
mine is 7 1 3 0 in that order... I guess I have a lucky 3 This is a clean device running smoothrom and only seen bricked kernel 0.55 so far.
I also cat /proc/cpuinfo
and it says cpu variant is 0x2, my friend has no t3_variant file to see cpu_procces_id but we both get cpu varient 0x2, I guess we both have a 3?
everyone else try cat /proc/cpuinfo
and report back pls.
ive cated cpu info and here are the results
as the previous op said hejad revision 0x2 and i have the same so maybe i have a variant 3. But I really need to be 100% sure.
Processor: ARMv7 Processor rev 9 (v7l) processor: 0 BogoMIPS: 1993.93 processor: 1 BogoMIPS: 1993.93 processor: 2 BogoMIPS: 1993.93 processor: 3 BogoMIPS: 1993.93 Features: swp half thumb fastmult vfp edsp neon vfpv3 tls CPU implementer: 0x41 CPU architecture: 7 CPU variant: 0x2 CPU part: 0xc09 CPU revision: 9 Hardware: grouper Revision: 0000 Serial : 0f410a0001440200
Sent from my Nexus 7 using xda app-developers app
Hello Mods please close this thread
O'll open a new thread wich will be more clear and more neutral than this one.
Galaxy S4 9500 onlyStandard Disclaimer: Im not responsible if something wrong happens to your device Read the guide as much as you want before proceeding with overclocking
Overclocking and undervolting is highly debatable, some say its good and some say its bad... so its upto you to decide and proceed further
First rule of overclocking.. Your Mileage May Vary
Most of the people here in xda do know about overclocking and stuffs but still there are many who are so eager to overclock their device . Hence this guide.
I have given some good info below about these stuffs as far as i can , you can always use google to get further details.
What is overclocking?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Advantage:
You can get more performance from your chipset, though s4 is already fast you can see the visible changes in application execution time and much more like instant response time.
Disadvantage:
* Overclocking is always risky if something is configured improperly and may also result in permanent damage to your hardware. As long as it is done safely you are good to go.
* You may see some increased power consumption.
* Extreme overclocking might kill your hardware.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
* Reduced heat from your device.
* Good battery life.
Disadvantage:
* Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Apart from the voltage table defined below for exynos the below mentioned data are common for 9500/9505
Overclocking in Exynos Octa:
Exynos 5410 is already one among the best performing chipset available, so overclocking this device is not going to give us any visible performance improvements except the benchmark scores. Underclocking is a different story on 9500, since the cpu temperature easily reaches upto 90C (90C is the throttle temperature defined for this device in the kernel, so its normal) undervolting the device will help in reducing the overall temperature of the device considerably. I highly recommend undervolting the device instead of overclocking it.
Exynos 5410 has 2 cpu clusters, stock voltages and available steppings are given below
Little Cores (A7) stock voltages
Code:
[B]STWEAKS[/B]
1200mhz : 1225mv
1100mhz : 1125mv
1000mhz : 1100mv
900mhz : 1037mv
800mhz : 987mv
700mhz : 950mv
600mhz : 950mv
500mhz : 950mv
400mhz : 950mv
300mhz : 950mv
200mhz : 950mv
Samsung divides the actual clock of a7 by 2 while displaying the steppings in order to accommodate the big little way of displaying values. Stweaks will show you every available steppings like above whereas most other cpu tuning apps show it like below, both are same though. stweaks @ 800mhz is equal to other tuning apps @ 400mhz
Code:
[B]OTHER CPU TUNING APPS[/B]
700mhz : 1225mv
550mhz : 1162mv
500mhz : 1100mv
450mhz : 1037mv
400mhz : 987mv
350mhz : 950mv
300mhz : 950mv
250mhz : 950mv
200mhz : 950mv
150mhz : 950mv
100mhz : 950mv
Big Cores (A15) stock voltages
Code:
2000mhz : 1250mv
1900mhz : 1250mv
1800mhz : 1250mv
1700mhz : 1200mv
1600mhz : 1162mv
1500mhz : 1137mv
1400mhz : 1100mv
1300mhz : 1062mv
1200mhz : 1025mv
1100mhz : 1000mv
1000mhz : 962mv
900mhz : 925mv
800mhz : 900mv
Though the cpu frequency table has steppings upto 2ghz the max stable clock i have seen so for on s4 is 1800mhz.
Requirements:
1. Kernel with overclocking/undervolting support.
2. stweaks or android tuner to change frequency/voltage.(you can use the app of your choice here).
3. set cpu and stability test to test the stability of CPU.
4. Some patience.
The below mentioned steps are common for 9500/9505
Step 1:
Set the current clock and voltage you want to test via android tuner/stweaks. (Select max frequency in cpu tab).
Example:
*If you want to test under volting for 1.4 ghz with 1050 mv (1100 is the default) then set 1.4 ghz as max clock and 1050mv as its voltage.
*If you want to test overclocking @ 1.7 ghz with 1150 mv (1200 is the default) then set 1.7 ghz as max clock and 1150 mv as its voltage.
Step 2:
Open set cpu's cpu stress test and run it for atleast 10 minutes. If you didnt get any errors or hang during the testing period and if the test completed successfully then the clock is ready for daily use
Step 3:
Now for undervolting use the same tools and reduce the voltage by -25mv.
Repeat step 2.
you can reduce the voltage further by -25 mv after every successful completion of stress test (Advanced users can try reducing -50mv )
Step 4:
Repeat step 1,2 and 3 for every possible cpu clock you see in android tuner/stweaks.
Note the stable cpu voltage for every clock, once you finish testing all your clock values save it as a profile and/or set it on boot.
Voila !!! now you have finished overclocking/ under voting your device.
Notes:
1. Never ever use set on boot option until you find the stable clock and voltage settings.
2. Not all chips are capable of running at higher speeds like 1800 mhz. Those speeds are highly experimental.
3. Recommended max overclocking is 1700 mhz.
4. If your device gets hotter allow the device to cool for few minutes before starting the test.
5. Either use stweaks or android tuner(or some other app), dont mix up.
6. Combining the overclocking and undervolting will give you the best of both the worlds
In case of emergency:
1. If your device becomes unstable and not responsive either press the power button until your device restarts or pull out your battery.
2. Android tuner has an option to create flashable zip for resetting the voltage table, use it if needed.
*********************Do note me if any information is incomplete or wrong ill change it.*******************************
Credits :
* wikipedia
* @AndreiLux and @wanam for their outstanding work on kernel development
Reserved for GPU
One more for some other if needed
I realize the thanks icon is there in order to prevent thanks spam.... however today I can not restrain myself.. thank you bala for this contribution
¡¡So say we all!! from Battlestar GT-I9500
well written and elaborate..thanks
thanks for the valuable input, but i differ on one thing. am using a 2Ghz overclock and is rock stable. using the GPU in the highest clock too....am attaching the STweaks values, battery and antutu score for the same. the device runs very cool too...hope this helps somone.
I do not know if am I doing it right or doing it wrong, but my phone runs without the (very occasional) hiccups and is as cool as it can be....and dat wat metters to me
thanks and regards,
Achyut.
P.S. - I resized the FHD screenshots to 25% for easy uploading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
achyut said:
thanks for the valuable input, but i differ on one thing. am using a 2Ghz overclock and is rock stable. using the GPU in the highest clock too....am attaching the STweaks values, battery and antutu score for the same. the device runs very cool too...hope this helps somone.
I do not know if am I doing it right or doing it wrong, but my phone runs without the (very occasional) hiccups and is as cool as it can be....and dat wat metters to me
thanks and regards,
Achyut.
P.S. - I resized the FHD screenshots to 25% for easy uploading.
Click to expand...
Click to collapse
Thank you very much!! Only wanted to ask about the 800mHz and 900mHz volts of the little cores since it's not shown in the screenshots. Thanks. :good:
noideaforusername said:
Thank you very much!! Only wanted to ask about the 800mHz and 900mHz volts of the little cores since it's not shown in the screenshots. Thanks. :good:
Click to expand...
Click to collapse
oops...sorry...here,
achyut said:
thanks for the valuable input, but i differ on one thing. am using a 2Ghz overclock and is rock stable. using the GPU in the highest clock too....am attaching the STweaks values, battery and antutu score for the same. the device runs very cool too...hope this helps somone.
I do not know if am I doing it right or doing it wrong, but my phone runs without the (very occasional) hiccups and is as cool as it can be....and dat wat metters to me
thanks and regards,
Achyut.
Click to expand...
Click to collapse
hmm, with 400Mhz more You have same results as stock? something is wrong, maybe settings do not apply or overheating is causing cpu throttling down so scores are so low.
Kriomag said:
hmm, with 400Mhz more You have same results as stock? something is wrong, maybe settings do not apply or overheating is causing cpu throttling down so scores are so low.
Click to expand...
Click to collapse
Every chips has different mileage, even if his chip runs at 2ghz, it will throttle down in very few seconds.
Sent from my GT-I9500 using Tapatalk 4 Beta
achyut said:
thanks for the valuable input, but i differ on one thing. am using a 2Ghz overclock and is rock stable. using the GPU in the highest clock too....am attaching the STweaks values, battery and antutu score for the same. the device runs very cool too...hope this helps somone.
I do not know if am I doing it right or doing it wrong, but my phone runs without the (very occasional) hiccups and is as cool as it can be....and dat wat metters to me
thanks and regards,
Achyut.
P.S. - I resized the FHD screenshots to 25% for easy uploading.
Click to expand...
Click to collapse
Which Kernel are u using??? I assume ure using Perseus 4... Ive heard and read on some forums that ver 4 has some problems with Camera/Sound etc issues???
Plz confirm.... Thanks
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
HassanM said:
Which Kernel are u using??? I assume ure using Perseus 4... Ive heard and read on some forums that ver 4 has some problems with Camera/Sound etc issues???
Plz confirm.... Thanks
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
Click to expand...
Click to collapse
absolutely Zero issues.....camera opens at the blink of an eye. Am on wanams MEA firmware, trimmed and themed by me according to my need.
hope this helps.
regards,
achyut
tried oc upto to 1.8 ghz today and yes, im impressed
quadrant gave something around 14,500 and geekbench scored 4k+
bala_gamer said:
tried oc upto to 1.8 ghz today and yes, im impressed
quadrant gave something around 14,500 and geekbench scored 4k+
Click to expand...
Click to collapse
I increased the voltages as advised by u but the quadrant results are around 13000 benchmark...
I'm currently using Omega 8/Perseus 3.4 along with the cross breeder....
My phones very snappy but just wondering about the quadrant result... Is there anything I'm missing???
Plz advise...
Thanks
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
HassanM said:
I increased the voltages as advised by u but the quadrant results are around 13000 benchmark...
I'm currently using Omega 8/Perseus 3.4 along with the cross breeder....
My phones very snappy but just wondering about the quadrant result... Is there anything I'm missing???
Plz advise...
Thanks
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
Click to expand...
Click to collapse
clock ur cpu at 1.8 ghz , u will get some similar scores
bala_gamer said:
clock ur cpu at 1.8 ghz , u will get some similar scores
Click to expand...
Click to collapse
Thanks for replying.....
Should I ser this value in STweaks or SetCpu or both?????
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
undervolting cpu
i dont get my phone pass all time stress cpu test but in my daily use he reboot all time!
anyone stable oc gpu? 640mhz or higher?
gpu overclock
jianlinooi said:
anyone stable oc gpu? 640mhz or higher?
Click to expand...
Click to collapse
mine is not so stabel something i manage to complete gfx berch and someting not on 700 on stock voltages!
jianlinooi said:
anyone stable oc gpu? 640mhz or higher?
Click to expand...
Click to collapse
yep....am on 700 mhz and is stable...check out my post in previous page, I shared the voltages for CPU & GPU.
regards,
Achyut
achyut said:
yep....am on 700 mhz and is stable...check out my post in previous page, I shared the voltages for CPU & GPU.
regards,
Achyut
Click to expand...
Click to collapse
looks like your chip is cooked well
It is still in beta phaze.
Use it your own Risk, I will not be held responsible if anything goes wrong with your phone
This kernel is only built for G900"H" Exynos Variant.
Features:
1. Made from SM-G900H_KK_Opensource_Update1 using Linaro Toolchain 4.7.
2. Permissive
3. Unlocked A7 Frequencies(200Mhz and 1500Mhz) -(*Credits: Andreilux)
4. Unlocked A15 Frequencies(2400Mhz) -(*Credits: Andreilux)
5. Wifi keeps forgetting password fix -(*Credits:Friedrich420)
Many more to come.
Please flash it using "Flashify" app until I find a proper way to make it CWM flashable.
Source: https://github.com/SandeepEmekar/Aqua-Kernel-OC
Special Thanks To:
@AndreiLux
Credits:
@AndreiLux
@friedrich420
If I forgot to mention some dev please pardon me.
Download Links:
V1.00
Reserved!
any way to unlock our cpu freq to normal?
the 2 quad cpu are downgrade 200mhz each other..
Airboner said:
any way to unlock our cpu freq to normal?
the 2 quad cpu are downgrade 200mhz each other..
Click to expand...
Click to collapse
It's weird.
I did not change anything in the kernel except Audio and SELinux.
It is 4AM here so I got to go to bed.
I will check it in morning.
Thanks for the report!
You are requesting for underclock?
I will look into it.
Airboner said:
any way to unlock our cpu freq to normal?
the 2 quad cpu are downgrade 200mhz each other..
Click to expand...
Click to collapse
Can you explain it further?
drakester09 said:
Can you explain it further?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52317603&postcount=141
Airboner said:
http://forum.xda-developers.com/showpost.php?p=52317603&postcount=141
Click to expand...
Click to collapse
The Samsung website shows the clocks as 1.3 and 1.9:
http://www.samsung.com/pk/consumer/mobile-devices/mobile-phones/smartphones/SM-G900HZKAPAK-spec
This is the frequency table for A15 cores:
See: https://github.com/AndreiLux/UNIVER...rivers/cpufreq/exynos5422-eagle-cpufreq.c#L57
Code:
static struct cpufreq_frequency_table exynos5422_freq_table_CA15[] = {
{L0, 2400 * 1000},
{L1, 2300 * 1000},
{L2, 2200 * 1000},
{L3, 2100 * 1000},
{L4, 2000 * 1000},
{L5, 1900 * 1000},
{L6, 1800 * 1000},
{L7, 1700 * 1000},
{L8, 1600 * 1000},
{L9, 1500 * 1000},
{L10, 1400 * 1000},
{L11, 1300 * 1000},
{L12, 1200 * 1000},
{L13, 1100 * 1000},
{L14, 1000 * 1000},
{L15, 900 * 1000},
{L16, 800 * 1000},
{L17, 700 * 1000},
{L18, 600 * 1000},
{L19, 500 * 1000},
{L20, 400 * 1000},
{L21, 300 * 1000},
{L22, 200 * 1000},
{0, CPUFREQ_TABLE_END},
};
From what I can understand from the source, if we have hotplug then the frequency can go all the way to 2.1
But since the Exynos 5422 in the G900H has global task scheduling that might be the reason for the lowered frequencies.
Having all the cores active at the same time raises the temperature and power consumption threshold.
See: https://github.com/AndreiLux/UNIVER...ivers/cpufreq/exynos5422-eagle-cpufreq.c#L556
Code:
#ifdef CONFIG_EXYNOS5_MAX_CPU_HOTPLUG
max_support_idx_CA15 = L3;
#else
#ifdef CONFIG_SOC_EXYNOS5422_REV_0
max_support_idx_CA15 = L5;
#else
max_support_idx_CA15 = L5;
#endif
#endif
The A7 is clocked at 1300 regardless of hotplugging enabled or not.
Thanks to Andrei for uploading the source dump to github.
drakester09 said:
The Samsung website shows the clocks as 1.3 and 1.9:
http://www.samsung.com/pk/consumer/mobile-devices/mobile-phones/smartphones/SM-G900HZKAPAK-spec
This is the frequency table for A15 cores:
See: https://github.com/AndreiLux/UNIVER...rivers/cpufreq/exynos5422-eagle-cpufreq.c#L57
Code:
static struct cpufreq_frequency_table exynos5422_freq_table_CA15[] = {
{L0, 2400 * 1000},
{L1, 2300 * 1000},
{L2, 2200 * 1000},
{L3, 2100 * 1000},
{L4, 2000 * 1000},
{L5, 1900 * 1000},
{L6, 1800 * 1000},
{L7, 1700 * 1000},
{L8, 1600 * 1000},
{L9, 1500 * 1000},
{L10, 1400 * 1000},
{L11, 1300 * 1000},
{L12, 1200 * 1000},
{L13, 1100 * 1000},
{L14, 1000 * 1000},
{L15, 900 * 1000},
{L16, 800 * 1000},
{L17, 700 * 1000},
{L18, 600 * 1000},
{L19, 500 * 1000},
{L20, 400 * 1000},
{L21, 300 * 1000},
{L22, 200 * 1000},
{0, CPUFREQ_TABLE_END},
};
From what I can understand from the source, if we have hotplug then the frequency can go all the way to 2.1
But since the Exynos 5422 in the G900H has global task scheduling that might be the reason for the lowered frequencies.
Having all the cores active at the same time raises the temperature and power consumption threshold.
See: https://github.com/AndreiLux/UNIVER...ivers/cpufreq/exynos5422-eagle-cpufreq.c#L556
Code:
#ifdef CONFIG_EXYNOS5_MAX_CPU_HOTPLUG
max_support_idx_CA15 = L3;
#else
#ifdef CONFIG_SOC_EXYNOS5422_REV_0
max_support_idx_CA15 = L5;
#else
max_support_idx_CA15 = L5;
#endif
#endif
The A7 is clocked at 1300 regardless of hotplugging enabled or not.
Thanks to Andrei for uploading the source dump to github.
Click to expand...
Click to collapse
the first link of samsung doesnt work...i will pot tommorow link which shows that sm-g900h cpu runs at 2.1 ghz and 1.5ghz thats why i am wondering.. but if you have time search on google. "cpu freq sm-g900h"
Στάλθηκε από το SM-G900H μου χρησιμοποιώντας Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 11:31 PM ----------
i found it check it
http://en.m.wikipedia.org/wiki/Exynos
it shows that exynos 5 (5422) runs on 2.1ghz and 1.5ghz and the last right list its about sm-900 h :/
Στάλθηκε από το SM-G900H μου χρησιμοποιώντας Tapatalk
You could set the frequencies that way it I think... just by changing the lines I have mentioned.
Expect higher temperatures and power consumption, of course.
It's nice to see someone finally doing something for the Exinos variant, keep up the good work.
drakester09 said:
You could set the frequencies that way it I think... just by changing the lines I have mentioned.
Expect higher temperatures and power consumption, of course.
Click to expand...
Click to collapse
the link final works..i see the freq on 1.3 and 1.9 as you said :/
btw my brand says that is universal 5422..
and i asked cauze on link that posted saw that runs on differents freq and
i was wondering if my cpu was lock..
anyway you are right so there is no reason to talk anymore about this
tnx btw for helping and for opening my eyes
SandeepEmekar said:
It is still in beta phaze.
Use it your own Risk, I will not be held responsible if anything goes wrong with your phone
This kernel is only built for G900"H" Exynos Variant.
Features:
1. Made from SM-G900H_KK_Opensource_Update1 using Linaro Toolchain 4.7.
2. Permissive
3. Wolfson Audio by Andreilux (Can be controlled from sys/class/misc/wolfson_control until I develop an app for it)
(Equalizer, Amplify Speaker,Earphone and Headphone)
Many more to come.
Please flash it using "Flashify" app until I find a proper way to make it CWM flashable.
Special Thanks To:
@AndreiLux
Credits:
@AndreiLux
@friedrich420
If I forgot to mention some dev please pardon me.
Click to expand...
Click to collapse
Why not posted your source code? XDA kernel GPL requires it! Please linking it!
halaszk88 said:
Why not posted your source code? XDA kernel GPL requires it! Please linking it!
Click to expand...
Click to collapse
Friend, I am new in development.
I still do not know github enough well.
There are few things I have planned to implement in my kernel.
As soon as I get over with it I will post it in Github.
Currently, I am busy building app to control "Wolfson Audio" which is included in my kernel.
Please have some patience.
SandeepEmekar said:
Friend, I am new in development.
I still do not know github enough well.
There are few things I have planned to implement in my kernel.
As soon as I get over with it I will post it in Github.
Currently, I am busy building app to control "Wolfson Audio" which is included in my kernel.
Please have some patience.
Click to expand...
Click to collapse
I tried to make one, I believe I had some success on it but I cannot remember.
I'll send you the source code by PM in case it's of any use... not posting it because it's not code I'm really proud of... :silly:
drakester09 said:
I tried to make one, I believe I had some success on it but I cannot remember.
I'll send you the source code by PM in case it's of any use... not posting it because it's not code I'm really proud of... :silly:
Click to expand...
Click to collapse
Please do send it.
That will ease my work.
Finally ! Kernel for Exynos version ! Looking forward to you, OP.:good::good::good:
Doble tap wake up?
Sent by my casiopeia E100
One request from me : Add more cpu governors please..
Sent from my GT-P6200 using Tapatalk