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.
Related
hey guys,
I saw winmo devs OCing this same Magic's CPU up to 800Mhz with great performance boost.
any one could reach same with android OS so far?
URL: http://wmpoweruser.com/?p=7461
thnx!
first off, the touch pro 2 isn't a magic. at all.
second of all, this is completely wrong forum. please read rules.
third, it probably never will happen. someone did it a while back and there was a huge debate about whether it worked or not and it was finally confirmed that it didn't work.
I can't find the word magic anywhere in there!!! Damnitt!!
so it leads to this question,
How did you come to the assumption that you could OC the magic when nothing about the magic is there?
The cpu is the same on the magic...
Deviser said:
The cpu is the same on the magic...
Click to expand...
Click to collapse
yup thats why I've asked...thanks!
Code:
http://forum.xda-developers.com/showthread.php?t=630450
Rugga said:
Code:
http://forum.xda-developers.com/showthread.php?t=630450
Click to expand...
Click to collapse
It's a shame that project died. I really believe that it's possible if the right person would try cause it already worked on a lot of phones. I used to clock my Omnia at 800Mhz which gave it a great boost and there was no real battery drain. They've also managed to clock the N900 cpu at 1Ghz:
http://talk.maemo.org/showthread.php?t=39753
renegadEEE said:
It's a shame that project died. I really believe that it's possible if the right person would try cause it already worked on a lot of phones. I used to clock my Omnia at 800Mhz which gave it a great boost and there was no real battery drain. They've also managed to clock the N900 cpu at 1Ghz:
http://talk.maemo.org/showthread.php?t=39753
Click to expand...
Click to collapse
indeed sad :/ could give us nexus cpu power on magic if some one could work this out....
rommark said:
indeed sad :/ could give us nexus cpu power on magic if some one could work this out....
Click to expand...
Click to collapse
No, it wouldn't. You're buying into the megahertz myth. The magic has a ARM11 (ARMv6) chip, whereas the N1 has a Cortex (ARMv7). It's more like a P3 against a P4 - the clockspeeds may match, but the performance is still going to be off. Not to mentium ARMv7 has a bunch of new instructions (NEON), that are not present on the v6. And the GPU still wouldn't support OpenGL ES 2.0. It may speed things up sure, but it wouldn't really matter.
sadly it's not the cpu preventing me from overclocking it! it's the software in the phone, the pll's are defined in the spl and it would take i SIGNIFICANT skill of hexing and backporting to do something about them! and by the way it would almost certainly brick the phone! i'm sorry guys the only thing i ever was able to play a litlle with was some parameters giving a little better gpu performance, but it's unstable
I already posted this in the Nexus dev forum, and I hate to clutter the boards, but I know that there are a bunch of talented devs here that may not see it on those forums. If we can bust the 30fps cap for good, and get the GPU overclocked, then we could see some serious gaming performance out of our Snapdragon devices.
I'm sure we all heard about being able to overclock the GPU on some of the old MSM devices, but the Snapdragon handles the graphics chip in a different way. The goal of this thread is to try and overclock the GPU on Snapdragon devices as well.
There is nothing GPU related in acpuclock-scorpion.c (the Snapdragon cpu clock settings) at least for setting gpu clock speed as far as I can tell.
In board-mahimahi.c (Nexus board file) and board-supersonic.c (Evo board file) there is some kgsl init code, but so far as I can tell it isn't setting the clock there, instead it seems to be pointing to PWR_RAIL_GRP_CLK to set the clock in both devices. It defines the variable in each of those files but I'm not sure where that variable is set, since it doesn't seem to be in any of the other board files as far as I can tell. I could be completely off here too though.
In drivers/video/msm/gpu/kgsl/kgsl.c there is a method called kgsl_clk_enable that seems to be called whenever the GPU is enabled. It looks like this:
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_set_rate(kgsl_driver.ebi1_clk, 245000000); // Looks like it sets the GPU clock, right? Wrong.
clk_enable(kgsl_driver.imem_clk); // Enable the clock
clk_enable(kgsl_driver.grp_clk); // Enable another clock, but why?
}
The line that's been commented out is the original value, I replaced it with my value on the line below it in a failed attempt to overclock it. Probably a stupid effort on my part, I doubt it's that simple, but it was worth a shot. The comments at the end of the line are also my additions.
According to the clk.h files in the standard linux kernel, clk_set_rate is obviously a method to set the clock rate. The first variable is a struct that tells it which clock to set, and the second variable is a long value that is the rate you want it set at. Is it setting the right clock there for Snapdragon chips? Or is it only the clock for older chips?
I'm in way over my head with this source, I'm but a lowly Java dev, but I really wanna solve this. Can anyone with a little more experience than me throw in a little more info? Sorry if it doesn't make much sense, if it isn't clear just ask me & I'll try to explain a little more.
Regards,
Jesse C.
EDIT: Okay I did a little more digging and those kgsl settings should work for QSD8x50 chips. In the config file, under Drivers, Graphics Support, it allows you to enable 3D accelleration for QSD8x50 & MSM7x27 chips. The tag for that is CONFIG_MSM_KGSL_MMU. If you check in kgsl.c it checks to see if that is enabled in the config, and if it is then it compiles and uses kgsl.c & all of the kgsl code. That tells me that the clock is either not being set, or the wrong clock is being set. I'm adding some debug code right now so I can see in dmesg what code is actually being run.
Dude I have no idea how to do this but bump and best of luck
Sent from my PC36100 using XDA App
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
fstluxe said:
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
Click to expand...
Click to collapse
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Geniusdog254 said:
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Click to expand...
Click to collapse
okey, But as far as I know that code is not standard... Becouse the Vugue msm7500 device is originally WM device.. so the Smart dzo managed this custom code.
I wil follow the nexus form .. This is Damn interesting !
i wish you guys the best of luck..wish i could help..i love xda..lol
I'm going to bump this, would be nice if more people were working on this.
Man... I absolutely love my phone. It really sux that this even needs to be asked. This device is so much more capable and I cannot understand why HTC would cripple it so badly. Look at the Samsung galaxy s or the Droid x. Or even a more similar phone like the nexus or incredible. They all stomp this phone when it comes to anything graphics wise even if it is just swiping home screens. It makes me sad. Lol
I love how it makes you sad, but you still lol. Lol (correctly placed)
This is big but first let's get a true cap fix!
Sent from my Evo 4G
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
psych2l said:
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
Click to expand...
Click to collapse
I don't know, yet I am in deep havoc lol. I activated my phone on the 20th. I have till 13th of July to pay my bill, so don't know.
I mean the locked bootloader of the Droid X is kind of lame. Also on the Evo, I have a 10$ discount because of the IO conference... unlimited texts too, and I bought two batteries for it with a charger(for 10$ lol, and they actually last a long time 1500ma, I put the 2 extras in my wallet)
Also I think I can upgrade my phone right away already if I read things right, so if Sprint gets an awesome phone I can upgrade to that whenever.
Verizon is more expensive, but I like how they let me do a 1 year contract. The Droid X is also nicer, I mean it has a better camera, and the mic quality when taking videos isn't piss, hopefully someone fixes that. It also has a real graphics card.
So yeah, it's hard to decide. A better phone, vs saving me some money. Though I plan to attend the IO conference once again. I'm still porting my distrubuted prime client onto Android, hopefully it will be high performance. So it's not like I just go there for a phone ^^. Hell I didn't even know about the phones till they said "Where do you want the Droid delivered" I lol'd. Though my time is limited, summer classes at UC Berkeley are tough : /
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
some of the source for the OpenGL ES GPU core was announced as being released today
Qualcomm releases open-source 3D Snapdragon driver
http://www.androidcentral.com/qualcomm-releases-open-source-3d-snapdragon-driver
havent looked at it yet, but im sure in the very least this should at least help shed some more light on overclocking the GPU and add another piece to the puzzle!
git location -
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
topdnbass said:
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
Click to expand...
Click to collapse
There isn't really a fps cap with the novatek kernel hack. It made the display much smoother for me and I am using it on EvolutionX. So beast.
Good news about the drivers, maybe we can actually see some overclocking now.
I want this to happen!
Nova runs pretty well on the Evo. Gameloft updated it recently.
I would just like for iphone ports to run well.
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
patelkedar91 said:
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
Click to expand...
Click to collapse
The Pixi doesn't have the same GPU, it has one of the low/mid-range MSM7227 (I think thats the model?) chips. It's similar as it's one of Qualcomms latest gen chips, but it is NOT a Snapdragon so it's different.
Also, the Snapdragon GPU's on HTC devices are clocked as follows:
GRP_CLK: The actual graphics clock, 256mhz
IMEM_CLK: The gpu memory clock, 256mhz
EBI1_CLK: As best I can tell, the bus that the GPU is on is EBI1, this is the clock for it, 128mhz
If you want more info, look here: http://forum.xda-developers.com/showthread.php?t=710850 since that thread is a lot more active, but please don't clutter it, there's actual devving going on there
Thanks for the info. I just wonder how they're going to get 3d games to work on the Pixi then... weird.
It was announced that the Pixi would get 3d gaming with the 1.4.5 update.
Much better (Y)
http://forum.xda-developers.com/and...ck-overclocking-tuning-snapdragon-s1-t2883708
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.
Dear XDA people,
Im currently working with Max's V4 RC2 kernel in combination with Cromi-X 4.6.9 (still need to update to the latest), which gives me a pretty smooth working tablet.
Now, im running the cpu at 1900mhz, 1225mV (still testing if i can go lower), and I can adjust speed and voltage nicely with Trickster Mod.
But, I would wan't to crank up the gpu speed (which is currently 666mhz I think?) and have the same "options/settings" available to do so. For example, a rom limitation of 750/800mhz on the gpu, with a variation of voltages to choose from. This way I can get as much gpu power as possible, since i find gaming on the tf700 pretty disappointing in terms of performance (of course a lot of games are not optimized for tegra).
Do you guys know what would be the best possible solution to overclock/adjust the gpu speed+voltage?
Thanks!
Sent from my GT-I9505 using xda app-developers app
tijsva said:
Dear XDA people,
Im currently working with Max's V4 RC2 kernel in combination with Cromi-X 4.6.9 (still need to update to the latest), which gives me a pretty smooth working tablet.
Now, im running the cpu at 1900mhz, 1225mV (still testing if i can go lower), and I can adjust speed and voltage nicely with Trickster Mod.
But, I would wan't to crank up the gpu speed (which is currently 666mhz I think?) and have the same "options/settings" available to do so. For example, a rom limitation of 750/800mhz on the gpu, with a variation of voltages to choose from. This way I can get as much gpu power as possible, since i find gaming on the tf700 pretty disappointing in terms of performance (of course a lot of games are not optimized for tegra).
Do you guys know what would be the best possible solution to overclock/adjust the gpu speed+voltage?
Thanks!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I think 666mhz GPU setting is probably reserved for Satans minions. At the moment the only way to control GPU speed is by adjusting the voltage. This is easiest using hunds kernel (3.1 if you have problems with 3.2) and his app. Together, you can crank the GPU all the way up to 775MHz and fry some eggs on the back of your TF700 and waiting for it to go into nuclear meltdown.
I know the gpu runs hot, thats why I want to see what speeds can be achieved with limited voltage. So you‘re saying the only way to change gpu speed is by setting a higher voltage for it? Why is that exactly?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
You've posted this in the wrong forum, so it will be deleted, in the mean time there is really no reason to use 1900mhz even less so while gaming. 1700mhz at max (it can go higher but you wont see much change/ if at all in benchmarks/ games but u'll see the difference in battery life)
As for gpu i run 750 mhz but again the difference between 650 - 750 mhz is hardly noticeable, gaming performance isn't great on the tf700, the tf300t doesn't look as good but its noticeably smoother with 3d
Moral of the story the tegra 3 gpu isn't powerful enough for 1920x1200 the tegra 4 wont be much better, the tegra 5 is the interesting one
tijsva said:
So you‘re saying the only way to change gpu speed is by setting a higher voltage for it?
Click to expand...
Click to collapse
Yes, that's what I'm saying. Unless you want to learn to create kernels and do all the magical voodoo these wizards do to bring us OC kernels!
tijsva said:
Why is that exactly?
Click to expand...
Click to collapse
I have no idea, been wondering that myself. I even posted the question somewhere about a week ago, but no one enlightened me. I really reccomend using hunds kernel and app though. There is a "gaming" option in his app that works very well, good speed without the ominous red glow of molten metal on your TF700's back panel.
TitanUranus said:
Yes, that's what I'm saying. Unless you want to learn to create kernels and do all the magical voodoo these wizards do to bring us OC kernels!
I have no idea, been wondering that myself. I even posted the question somewhere about a week ago, but no one enlightened me. I really recommend using hunds kernel and app though. There is a "gaming" option in his app that works very well, good speed without the ominous red glow of molten metal on your TF700's back panel.
Click to expand...
Click to collapse
Are you saying increasing gpu voltage will subsequently increase gpu frequency? (i have no idea how it works, ive never bothered to look into it but now im interested) _that or Hunds will know but im guessing if thats the case freq and voltage must be linked in a voltage table but i would have thought freq could be changed independently to voltage
JoinTheRealms said:
You've posted this in the wrong forum, so it will be deleted, in the mean time there is really no reason to use 1900mhz even less so while gaming. 1700mhz at max (it can go higher but you wont see much change/ if at all in benchmarks/ games but u'll see the difference in battery life)
As for gpu i run 750 mhz but again the difference between 650 - 750 mhz is hardly noticeable, gaming performance isn't great on the tf700, the tf300t doesn't look as good but its noticeably smoother with 3d
Moral of the story the tegra 3 gpu isn't powerful enough for 1920x1200 the tegra 4 wont be much better, the tegra 5 is the interesting one
Click to expand...
Click to collapse
I know the tf700 isnt much of a gaming tablet unfortunately, but then again, why not setting it up so that it runs games as smooth as the hardware will allow ? Every small improvement is an improvement if you ask me.
For 750mhz gpu, what kernel are you using?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I'm using hundsbuahs latest kernel, the problem with tegra CPUs is thermal throttling, it starts around 72c on a lot of devices (not sure about the tf700) at 1900 you could find worse gaming performance than a lower cpu / GPU clock speed. Its completely up to you, hundsbuahs kernels give users a lot of flexibility as they can push the devices to the limit, I like _that's kernels personally they suited to my usage (what ever that means)
I feel like this should have been easier to find, and I feel like I should have known this now after using this phone for 18+ months but I can't seem to find a definitive answer anywhere... What's the stock 3D/2D clock for the GPU on this phone? I believe 3D is 400, correct? Just wondering, because I can't figure it out. I feel like a noob again
RollTribe said:
I feel like this should have been easier to find, and I feel like I should have known this now after using this phone for 18+ months but I can't seem to find a definitive answer anywhere... What's the stock 3D/2D clock for the GPU on this phone? I believe 3D is 400, correct? Just wondering, because I can't figure it out. I feel like a noob again
Click to expand...
Click to collapse
i founded this:
http://www.anandtech.com/show/5559/qualcomm-snapdragon-s4-krait-performance-preview-msm8960-adreno-225-benchmarks/3
this post says that adreno 225 can run at up to 400mhz.
i think it is a variable clock speed...it only runs at 400mhz when needed.and the rest of time runs at lower speeds to save battery life.