yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] thehelios:
That's news. About a year and a half ago, some Russian or European guy released WM drivers for USB host and he had it working with a mouse, keyboard, external cd drive, etc. I got the Usb mini male to USB female adapter but the drivers didn't work.

If it was only a driver problem, I'd be super happy. But there was someone reputable who kept saying that the Vogue had no USB host support so that's where I got it from.
[Touch CDMA Android Development] fstluxe:
Dear dzo,

Is this tweak also possible on the newer snapdragon phones like nexus etc?
[Touch CDMA Android Development] Shidell:
lol, Dzo you're incredible. Nice work.

This makes me wonder--how much more might performance improve, given the OC to the CPU and the GPU, when you're running Froyo with the JIT instead of Eclair?

Have you tried even using a SDK-rip build to see if it might affect performance?

Makes me wonder if you could crack 40 FPS. LOL. (If you do, I expect you to wire-up and write some sort of USB->HDMI adapter and put us new Evo owners to shame. ;))
[Touch CDMA Android Development] xport:
Id love to try this, can anyone tell me how?

running Myn’s Warm Donut - [RLS 5 - 04/24/2010] and voguimg-240x320-29-05-10.nbh
[Touch CDMA Android Development] thoughtlesskyle:
haha if were over 30fps after the OC were already doing better than the EVO
[Touch CDMA Android Development] *M*:
What fps does a stock vogue get?
[Touch CDMA Android Development] masalma:
I just tested mine and came up at 18.5 fps
[Touch CDMA Android Development] *M*:
Daaaam, practically double
[Touch CDMA Android Development] dzo:
I just put a new kernel and NBHs on my site that allows you to change the GPU clock. Flash (or boot) it and the open a terminal (or use adb) and type:

su

cd /sys/module/clock_7x00/parameters/

echo 0xa99 > gpu

to go back to the default, use:

echo 0x4a80 > gpu

There are some other changes in this kernel, in particular it powers down the sd card on suspend which should save some power and works fine for me but may cause problems (especially if not running from nand). Let me know if you have trouble.

p.s. I also did some tests and didn't notice any difference in power consumption using an overclocked GPU.

If you want to play with other values, bits 0..2 are the pll number, 0 is 19.2MHz, 1 is 800MHz and 4 is 200MHz, bits 3..6 are a divider for the clock, 0 means divide by 1, 1 means divide by 2 etc.. so 0xa99 is 800MHz/4, i.e. 200MHz.
[Touch CDMA Android Development] rps13:
Would it be possible to apply this patch to the MSM 7xxxA processors as well?
[Touch CDMA Android Development] *M*:
Possible to apply this from default.txt?
[Touch CDMA Android Development] dzo:
Yes, clock_7x00.gpu=0xa99 in cmdline should work.
[Touch CDMA Android Development] SuperJMN:
How could I apply this to Myn's Warm Donut for Polaris on NAND? I looked for this path in the filesystem, but I don't have idea of what I have to change to make it work :(

* Sorry for my noob question. I'm using your latest .NBH (Vogue today's converted to Polaris)
[Touch CDMA Android Development] xport:
How do you get Better Keyboard to type an underscore in Better Terminal Emulator?

Or paste without a "Ball"

Thanks dzo for the new option, thanks in advance for the _ help.
[Touch CDMA Android Development] brunes:
I can't even stay stable with the CPU at 400 so I don't have high hopes for tihs :(
[Touch CDMA Android Development] *M*:
Seems to work, although cancles out CPU oc in default.txt, I get ~520 in caffiene mark with a 528 OC.

When I do the GPU OC I get 25 fps in neo, but caffiene mark goes back down to ~320.

When I try to set the GPU through terminal I get the error cannot create gpu: director nonexistent which is why I'm trying the default.txt method
[Touch CDMA Android Development] SuperJMN:
Sorry! I didn't see this message. I'm going to try it. Thanks!
[Touch CDMA Android Development] demandarin:
I would love to know this also. I have a tilt 2 running the AOSP 2.1 Launcherpro XdAndroid overclocked to 787MHz. So would that gpu overclock work on rhodium devices or with 7xxxA processesors? Putting that edit it will knock out the cpu overclock? Anyway to have them both overclocked at once?

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] c-pimp:
Just curious what the cmdline for cpu overclock is that you have set in your default.txt

(is it safe to use on kaiser or only on vogue? do you know?)
[Touch CDMA Android Development] demandarin:
Well I entered ur edit in my startup txt on tilt2 Aosp 2.1 launcherpro android. For starters it didn't throw up an error. My android booted up fine. Plus it didn't knock out my overclock, I'm still at 787MHz. I can't really tell any difference yet. Was already running great with the overclock. What did u use to test the new edit. Or what benchmarking apps are good for GPU edit testing? Ill post bck if I notice anything but it did wrk in my startup txt on rhodium. Now I just have to test and see if it actually makes an improvement.

-------------------------------------

Sent from my AOSP on XDANDROID MSM

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] DmK75:
Neocore is GPU benchmark. But, how you enabled hw3d on Rhodium?

Because, if i added "hw3d.force=1" on my Topaz, i see only black screen in 3D apps.
[Touch CDMA Android Development] demandarin:
Hardware 3d not completely wrkn on the rhodium build, yet. In the startup utility, there is a box to check off for hrdware 3d. I always leave it unchecked. Ill check it off to see if it makes a differnence.I just entered in this gpu overclock edit in mines for tilt2 android , to see if any improvements. Ill get that neocore u mentioned. Ill post bck with more info or any improvements
[Touch CDMA Android Development] demandarin:
Well I got that Neocore and tested. :( lmao. That app looks like some cool videogame. I never seen graphics like that and that good on my tilt 2. Mind u I'm booted into Android 2.1 using the Neocore. Everything looked great but my results sucked. Lol. Only 2.0 frames per second. Lmfao. I figured that because the hardware 3d on this build isn't wrkn yet completely. Everything software rendered or somethin. So even with my cpu overclock and this new gpu overclock, I only pulled that number. Still have to test more. I'm sure once the hardware 3d is finally enabled in its entirety, that Neocore will produce decent numbers. I have to test that without the gpu overclock to see if it made a difference. Still cool find though.

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] DmK75:
I get same bad results.

Usual results there with hw3d is 23-26 and more FPS.
[Touch CDMA Android Development] rps13:
Also just to comment, according to Qualcomm's data sheet for the MSM7200A (and I suppose for any other MSM7xxxA processor) the graphics core is clocked at 256MHz so you should set the clock to something higher because for non A processors the clock is 100MHz
[Touch CDMA Android Development] demandarin:
Can u give me an example¿ or what does the OP edit clock the gpu to? Which numbers should I increase since I hve the tilt 2?

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] rps13:
The op sets it to 200 MHz using 0x1a99 (he didn't write the 1 because it's not needed) but I have no idea how he divides the pll (1=pll for 800mhz) by 4 using the rest of the bits (a99) try 0xa80 which I think should be 800/2

-------------------------------------

Sent via the XDA Tapatalk App
[Touch CDMA Android Development] demandarin:
I did the Caffeine benchmark. Ran it twice. First time overall score was 820 or somethin. Second time, I got 775. Are those decent scores? I did just increase my cpu overclock. I'm now officially at 806MHz. :P. I don't know how to play with those gpu numbers yet. Don't know which ones to mess with or increase.

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] *M*:
~800 is great, My spare vogue at 590 got ~600

Do you run android using our vogue kernel? Might be possible to oc you'll have to wait for dzo to answer on that.

clock-7x00.ahb_div=4 clock-7x00.a11=528

Should work. If you get lockups or strange behavior try dropping to 500.

For gpu I add clock-7x00.gpu=0xa99, which works but cancles out the cpu oc, ill try using rogue tools to set my cpu from within android.

EDIT: setting gpu in default.txt and cpu with rougue tools works, I got 31fps with 528/200
[Touch CDMA Android Development] demandarin:
I'm using the Rhodium Aosp 2.1 LauncherPro Xdandroid. I have a tilt 2. I was hoping this gpu overclock might help with the rhodium build. Hardware3d not wrkn compltely on it. Which numbers on gpu overclock do I change or increase? Since I hve a tilt 2 overclocked(cpu) to 787MHz when booted in Android. Cuz I hvent noticed any improvement, as far as neocore goes.

-------------------------------------

Sent from my AOSP on XDANDROID MSM
[Touch CDMA Android Development] Millence:
Need help for gpu overclock!

I'm trying to overclock gpu on kaiser unsuccessfully. Usually I don't ask for help but this one is real pain in the ass.

Tried NAND, haret on donuts and eclairs and nothing!

Result from Neocore on my kaiser with CPU on 512Mhz is 25fps with sound and 28fps without sound(on donut builds, with eclair builds it's little less). If I overclock GPU scores must

be higher(expecting 36.5).

I noticed that is new 'file' on /sys/module/clock_7x00/parameters/ in new kernel but it's not GPU it's GRP! So when I try to 'echo 0xa99 > gpu' from adb or command line I got

'cannot create gpu: directory nonexistent'. Putting 'echo 0xa99 > gpu' in default.txt does not help.

Then I decided to play with GPR parameter. Value 0xa99 (echo 0xa99 > grp) dont change Neocore score (still 28fps). With value 0xa80 Neocore scores 15fps. This make me think that gpr

parameter have something to do with GPU. Tried several other values with different results (from 2-22fps and soft reset).

If anyone can help me please? Dzo?
[Touch CDMA Android Development] dzo:
Oops, sorry my fault, Qualcomm calls it a grp (graphics processor) rather than a gpu so that's what I named it. I tried 0xa99 on a polaris and it crashed, the next step down from 0xa99 is 0xaa1 (800/5), try that instead. It could also be that the pll vlaues are different on kaiser.
[Touch CDMA Android Development] *M*:
Sweet I got 35 fps with that now, + the GDE cube effect is buttery smooth.

Anything higher than 0xa99?, Don't mind sacrificing my spare vogue to the test.

Also is it possible to put this in a script that executes at every boot?
[Touch CDMA Android Development] 360discgolf:
am I doing something wrong?

So I'm over clocking the CPU at 499 and I used the echo 0ax99 setting, but I'm only gettings 23 fps. Is there something specific to make sure the grp setting "sticks?" I did a soft reset after I applied the grp change in the terminal emulator so I'm wondering if it would revert?
[Touch CDMA Android Development] xport:
Finally got some testing done.

I finally got to test this out, running running Myn’s Warm Donut - [RLS 5 - 04/24/2010] and voguimg-240x320-12-06-10.nbh (NAND), overclocked cpu via roguetools to 501 MHz, density 110, stock theme.

Neocore (no sound) before change: after change (no sound):

31.3 32.8

32.0 34.6

32.3 34.0

32.1 34.7

35.7 33.9

32.5 33.9

32.3 34.1

32.0 34.5

32.6 33.7

33.0 34.1
[Touch CDMA Android Development] drewden123:
How'd you get those numbers? I tried applying the fix in better terminal and i got nothing higher than 26 w/o sound and 19.1 with sound. I can't seem to get it to work (warm donut rls 5, voguimg-12-06-10)
[Touch CDMA Android Development] DmK75:
Overclocked to 551, without changes gpu/grp.

Unfortunately, i cannot testing grp because my Polaris get "waiting for notbusy" errors with 12.06 zImage.
[Touch CDMA Android Development] xport:
nothing special other than what i posted in my test header, honestly.

Myn’s Warm Donut - [RLS 5 - 04/24/2010] and voguimg-240x320-12-06-10.nbh (NAND), overclocked cpu via roguetools to 501 MHz, density 110, stock theme.
[Touch CDMA Android Development] fstluxe:
Dear dzo,

Could you take a look to this topic ?

Thank you
[Touch CDMA Android Development] c-pimp:
Not seeing any results with nand with kaiser runing k_k's latest lite eclair and dzo's latest nbh... will do some more tests from sd install.

Anyone with a tilt got any results?

-------------------------------------

Sent via the XDA Tapatalk App
[Touch CDMA Android Development] ebautista:
cannot enable in kaiser

Hi Dzo, can you help me how to make it in my kaiser? I cannot find even grp or gpu file. I used your kaisimg-panel1-320-24-05-10.nbh but cannot seems to find it. I am using Warm Donut RL5.
[Touch CDMA Android Development] tsrich:
Rogue Tools

Has this been added to any version of Rogue Tools? I'd be willing to give it a try.
[Touch CDMA Android Development] cbaty08:
Yeah, I would like to try this too!!!
[Touch CDMA Android Development] dzo:
That device has a Snapdragon SOC with a very different GPU so it's very unlikely the clocks will be the same.
[Touch CDMA Android Development] demandarin:
To the OP, DZO, do u know if ur gpu overclock will wrk on Rhodium? I had made a few posts in this thread but got no response. I've already tried it out in my startup txt but it made no difference. I'm figuring since the rhoduim is more powerful than the vogue, I need to increase those values that u have. I have my tilt 2 cpu overclocked to 787MHz running Android. AOSP 2.1 LauncherPro version. I had downloaded Neocore and ran the test. That edit u had made no difference on my device. I'm figuring because it needs to be increased but I don't know which one in that edit to do it to. My processor is the MSM7201A. I don't know what my gpu is clocked at. I would really appreciate any insight into this, DZO . I know my device isn't a vogue, but it is htc though, cuz..lol.

-------------------------------------

Sent from 787MHz Tilt 2 :P
[Touch CDMA Android Development] dzo:
The GPU in the 7x00A is very similar to the one in the 7x00 so it should be possible but you will need to talk to your kernel devs to add this functionality.
[Touch CDMA Android Development] ebautista:
Help

Okay. I managed to do it now. I have downloaded the latest nbh from Dzo's site I used NBH editor because it was meant panel 2, mine is panel 1. Then I flash my kaiser and applied those settings. Overclocked at 501 using Rogue tool i can only get 18-21 fps using Neocore. I cannot get the expected result as posted in post#1. Anything need to be done aside from those steps mentioned by Dzo in post #39.

Disregard: Still wanna try in my kaiser but nobody replying on how to do it. No grp or even gpu in the said directory in android. Please help?
[Touch CDMA Android Development] Millence:
After two days, spending every minute of my free time testing, I can report NOTHING!

Ok almost nothing.

If I understood correctly about bits in 0xa99 my testing gave me strange results.

Let me explain:

a99=10101 0011 001 that is 800MHz divided by 4

aa1=10101 0100 001 that is 800MHz divided by 5

so 001 is bit 1 and pll value should be 800MHz

0011 and 0100 are divisors 4 and 5

10101 are bits that I did not change in my testing

And one more thing. If 4a80 is back to default then

100 10101 0000 000

And 100 is more bits to play with. I use 000 in tests because if bit 4 is 1 (100) then changing clock is disabled ( i think).

Only pll value that respond to divisor like it should is 0 (000) . But when pll is (000) and divisor 1 (0000) (0xa80) Neocore scores 14.5fps! If I raise divisor to 4 (0011) Neocore scores 5.5fps.

Bit 4 in pll is interesting (100). With that value in pll divisor is acting like subtrahend. You can review the results in attachment but I am guessing that the formula is

(24Mhz – divisor)*8 or something like that.

With pll set to 1 (001) things get strange

10101 0000 001 – 0xa81 - NO GPU. Neocore starts but it runs like there is no GPU support! Same like hd3d.version=1 is set on donut builds. Smoke and textures are different.

10101 0001 001 – 0xa89 – NO GPU

10101 0010 001 – 0xa91 – Neocore don't start when i hit run and FC after a while.

From 10101 0011 001 to 10101 1111 001 divisor is acting like subtrahend.

I hope this will help finding solution how to overclock Kaiser GPU. That's all from me for now I need to rest a little bit of bits and bytes.

All results are in attachment
[Touch CDMA Android Development] iseeka:
i´m trying to do it from terminal on my polaris

when entering echo 0xa99 > gpu

i get: cannot create gpu: directory nonexistent

any clue?
[Touch CDMA Android Development] dzo:
should be grp rather than gpu, i'm not sure it works on 7200 devices though.
[Touch CDMA Android Development] Millence:
Don't work for Kaiser. I only manage to downclock GPU. Dzo can you look the results of my testing? Maybe it will help you figuring out how to overclock Kaiser GPU.
[Touch CDMA Android Development] Twit:
Are there any dangers of overclocking CPUs through Rogue tools? Im thinking of doing it but dont wanna fry my phone!
[Touch CDMA Android Development] incubus26jc:
yeah it will be ok, I wouldnt go to far over 500mhz though. Anymore than 510 for most vogues causes problems. Probably a faster battery drain as well. But a good speed boost.
[Touch CDMA Android Development] thoughtlesskyle:
im running a 528mhz, the other key is moving slowly up to your desired setting
[Touch CDMA Android Development] iseeka:
Doesnt seem to work either on polaris (as expected)

from polaris: on terminal:

all test made with eclair 17-06 nbh running @512

Initial results 0xa99

neocore=20.2fps,20.0fps, 20.3fps, 20.4fps

caffeine mark

sieve=498,602,596,567

loop=512,715,717,696

logic=536,511,512,511

string=536,497,511,523

float=360,421,433,431

method =478,531,523,522

overall=519,506,538,541,536

with 0x4a80

neocore=19.6fps,20.3fps, 19.9fps, 20.1fps

caffeine mark

sieve=331,598,603,603

loop=403,712,685,717

logic=413,502,427,491

string=400,497,461,480

float=416,433,448,447

method=526,526,536,537

overall=526,537,518,538
[Touch CDMA Android Development] Millence:
iseeka can you please test this values if you have time.

0xa8c

0xabc

0xadc

0xaf4

If FPS drops with every value then I assume that formula is

(24Mhz – divisor)*8 or close to that

If we manage to do (24Mhz+divisor)*8 we can overclock GPU. For that we need Dzo's help of course.
[Touch CDMA Android Development] cbaty08:
I hear every proc has it's unique limit.. I have been running at 520 for over a month and not an issue.... yet!
[Touch CDMA Android Development] ptcfast2:
I've pushed as high as 550. I tend to stay right at 529 though as 550 seems to be a bit flaky.
[Touch CDMA Android Development] Dominik06:
whoa. o:

nearly 27fps..

n1, thanks. ;D
[Touch CDMA Android Development] ivanmmj:
I can't find the code changes anywhere. Can you post a diff? Or if you have a working git, can you point me to the commit?

Thank you!
[Touch CDMA Android Development] dzo:
This is the original commit but the code has changed a bit since then.

http://androidhtc.git.sourceforge.n...it;h=23ff83048726252bc785699fc749a3e364a3bdb0
[Touch CDMA Android Development] thoughtlesskyle:
is there anyway myn can build this into rogue tools?
[Touch CDMA Android Development] ivanmmj:
Thank you, Sir.
[Touch CDMA Android Development] mrkite38:
he has stated he would earlier in this thread. don't know when, though. :confused:
[Touch CDMA Android Development] indianneel:
help../

hey can anyone give me step by step instructions on how to do this!? i understand editing the commands in the default.txt file, but where is it on the Sd card after doing a nand install? ive used the latest nbhs from dzos website, and am running myns warm donut rls5.

if someone could jus post some steps on how to do this that would be awesome
[Touch CDMA Android Development] dzo:
Start "Term" in dev tools and then type:

su

echo 0xa99 > /sys/module/clock_7x00/parameters/grp
[Touch CDMA Android Development] indianneel:
ok i did su then enter

then typed in that thing, is anything supposed to happen, like confirmation wise? if not then it went thru i guess lol, thanks for the help! i was using an older command line in this thread and kept errors
[Touch CDMA Android Development] mnjm9b:
Is this working for kaiser?
[Touch CDMA Android Development] fstluxe:
i Get 35.5 FPS.. with cpu @ 550 @ my kaiser 130
[Touch CDMA Android Development] SuperJMN:
How did you get it? With my Polaris it's about 24 FPS!
[Touch CDMA Android Development] fstluxe:
I used this rom http://xdaforums.com/showthread.php?t=700669

and OC to 550 mhz + the 0xa99 line..
[Touch CDMA Android Development] gedster314:
Just when I thought it was save to ditch my Vogue.:eek: At this rate you guys will develop on board Cold Fusion in time for Christmas.

Thanks a lot guys.
[Touch CDMA Android Development] SuperJMN:
Does it work for Polaris? I tried it in the past and I didn't get any result. By the way, now I'm using Froyo.
[Touch CDMA Android Development] vinny13:
What kind of results am I supposed to see in Fresh Froyo?

I did:

su
cd /sys/module/clock_7x00/parameters/
echo 0xa99 > grp

And in Neocore I barely see 25-27 FPS with CPU overclocked to 512mHz.. Is that an improvement? I forgot to run it before I did the line lol :P
[Touch CDMA Android Development] vinny13:
Do you get that result with sound disabled?
[Touch CDMA Android Development] fstluxe:
I get 35.9 +- with sound off
[Touch CDMA Android Development] clemsyn:
I get 34.9 with sound disabled on my Donut build. This is without the 0xa99. With 0xa99 I only get 29 fps with sound disabled. BTW, my Kaiser is OC'd at 542.
[Touch CDMA Android Development] tsrich:
Works with Incubus26Jc's Super FroYo ??

Can I use this with the kernel that comes with super froyo?
[Touch CDMA Android Development] hexto:
DZO you are amazing. I upgrade to the Incredible and it gets 25.8fps on Neocore. I since have regretted upgrading to this phone. Mainly because the Snapdragon chip is disappointing when it comes to 3D acceleration. Games constantly slow down or crash. This is truly impressive. Great job!!
[Touch CDMA Android Development] hussmanne:
My score on Froyo. Donut faster?

Running Super Froyo RLS 12 Sprint Touch/Vogue @529mhz w/ 0xa99 entered in terminal & sound disabled. Score: 26.1 FPS.
[Touch CDMA Android Development] SuperJMN:
I think that only Kaiser can take advantage of this tweak. With models like Polaris I didn't have luck :(
[Touch CDMA Android Development] dertester123:
On Incubus super Froyo RLS12 i can confirm that this does not work.

I only get ~7 Frames with and without the tweak.

But i think it has something to do with the gpr generally, because some of the live wallpapers like these waveform/waterwaves etc dont work or some parts are white(the live wallpaper where leaves fall on water, the water is white) for me...

Maby its the little difference between msm7200 und msm7500 :(

Would be cool if there were more people interested in the old devices.
[Touch CDMA Android Development] dzo:
If you only get 7fps then you are using the wrong kernel, get the latest froyo kernel for your device from here:

http://cs-alb-pc3/vogue/files/?C=M;O=D
[Touch CDMA Android Development] dertester123:
Its not better now, i installed the polaimg from 26/7

running incubus Rls12 or freshfroyo "system-froyo-26-07-10_16.tgz"

I have a pola200 aka orbit 2...

Also i get a other result, the fps is in the down left and a small syle not mittle big white bold like i saw on youtube videos

---------

doing 0xa99 > ////grp doesnt help

Its neocore 1.9.22