|
|
LinkBack | Thread Tools | Display Modes |
|
||||
GfxBoost 0.7 and 1.1 Service version - Out now! (updated 5-1-09)
[HTC-MSM7K][01.05.2009] GfxBoost v1.1 - Service - Next attempt
For HTC-built MSM7K-based devices only! All MSM7K are technically capable, but only HTC's may have the correct drivers. Will probably not work on stock ROMs. I suspect the CDMA versions of the older MSM7K devices - pre-diamond - do not have the necessary drivers either. As far as I know, the first device that came with these drivers is the Kaiser, but IIRC they are also included in various Polaris ROMs. About Short and simple, GfxBoost activates "QTV" mode for specific surfaces. This makes for example DirectDraw display smoother and: a bit slower or significantly faster, depending on how you look at it. It also seems to have a small effect on Direct3D/OpenGL. Err, what? Right, this is a bit tricky! If you will benchmark it the result will be lower FPS. However, it will actually appear faster. This is because normally, not all frames are actually drawn on-screen, and the timing of the drawing can be so it appears nothing is being actually drawn at all. This does not happen when using GfxBoost - more is actually drawn to the screen, and smoother. So, from the application's point of view, it can do less per second, but from what you actually see on-screen, more happens! If you don't understand what I mean, just take it from me: it definitely looks better Some good effects
Alright, it took a bit of research, a lot of trial and error, quite a bit of hairpulling, a few hours of IDA, and an entire crate of beer to get this working on the few of my devices I actually bothered to test it on (Kaiser and Touch Pro). I think everything is now properly hooked up with HTC's own software so things like Camera and WMP also still work. If you run into anything, strange, well, first RTFM below, then see if you want to post it here. TFM (The F*ing Manual, read it!) Requirements An HTC-built MSM7K-based device, sporting QTV and some similar nonsense. In general, I would say this this is the entire range between the Vogue and the Touch Pro, though I've only tested it on Kaiser and Touch Pro, and both are GSM. Installation - Install the CAB on your device - Soft-reset (does not seem to be needed on all devices) - Start GfxBoost and click Enable Uninstallation - Start GfxBoost (if not running) and click Disable - Uninstall CAB as usual Upgrading - Install new CAB - Soft-reset "What's this Enabled (Inactive) status? It means another application is running that needs this chipset feature. For example, Windows Media Player, YouTube, Camera, etc. As soon as you exit all of those, GfxBoost should re-activate itself. "I see no difference Q_Q" If there's a visible difference depends completely on the application you are running and what you are doing with it (aside from it possibly just not working for you). The more graphical an application is, the more chance you have this makes a difference. I've seen no differences with normal "GDI" style applications (normal apps), but for example on my Kaiser the difference in Manila 2D is enormous. "What about this video-running-in-the-background-thing I keep reading about?" If done properly, that has the same effect as GfxBoost. Just not as easy and it doesn't think about other applications that need this chipset feature. bla bla Coreplayer bla bla Exactly! Changelog 1.1 - 01.05.2009 - Some patches to service code and handling - Added registry fixes for common issues - WM6.5 icon adjusted again 1.0 - 29.04.2009 - Fixed service version, hopefully this one works 0.8 - 29.04.2009 - Service version 0.7 - 28.04.2009 - Changed loader mechanism 0.6 - 28.04.2009 - Loading of dependencies is dynamic - with error messages - All files are now signed - Added program icons [Thanks to 12aon] Original thread with more info and feedback:http://forum.xda-developers.com/showthread.php?t=509704 Created by Chainfire over @ XDA
__________________
Last edited by santod; 05-01-2009 at 08:47 PM. |
This post has been thanked 12 times. |
|
||||
Re: GfxBoost v0.5 - Out now!
Is this the only thread about this? Does it play nicely if we have used the driver from another device? has anyones device required a hard reset from this or is it relatively safe to try?
Sounds like a winner, will try it soon! edit: chainfires thread @ xda... http://forum.xda-developers.com/showthread.php?t=509704 . Last edited by nuguy; 04-30-2009 at 09:38 AM. |
|
||||
Re: GfxBoost v0.5 - Out now!
Quote:
EDIT .. Found Version 0.7 .. tested ! WORK EDIT New Service version .. testing .. Last edited by Hammerz; 04-29-2009 at 03:07 PM. |
This post has been thanked 1 times. |
|
||||
Re: GfxBoost v0.7 and .8 service version - Out now!
Thanks, original post updated with latest version .7 and .8 service version which has the settings panel under Settings -> System, not under Programs!
|
|
||||
Re: GfxBoost v0.7 and .8 service version - Out now!
Service version .08 doesnt seem to be working It show enabled but inactive. Guess chainfire is working on a solution now.
dschoenike |
|
||||
Re: GfxBoost v0.7 and .8 service version - Out now!
Installed 0.7 on my Sprint Touch Pro w/ stock ROM. No errors, enables fine. But appears to do absolutely nothing. Hmm.
|
|
||||
Re: GfxBoost v0.7 - Out now!
Installed it on my Diamond w/ Calkulin's 6.5 rom. Runs fine. Not sure if it does much although my phone is pretty bare from a new flash so I'm limited on apps to test. Titanium may be a bit smoother on the zooming animations when you switch panels. Opera doesn't seem any faster/smoother. Will probably try pointui, xtrakt and igo8 once I get them back on my device. I'd like to hear other people's experience with this.
|
|
||||
Re: GfxBoost v0.7 - Out now!
This is a mortscript code for automatic start versione 0.7
Sleep(5000) Run( "\Windows\GfxBoost.exe" ) WaitFor( "GfxBoost","30" ) MouseClick( "GfxBoost","117","86" ) Sleep(1500) Minimize( "GfxBoost" ) Exit Updated .. Last edited by Hammerz; 04-29-2009 at 02:19 PM. |
This post has been thanked 1 times. |
|
|
|