yashsingh1/xdaforums huggingface dataset:
[HD2 General] sunking101:
I have never used predictive text and I'm not going to start now as a workaround due to poor hardware/software. I am old-school, I type every letter and I type FAST. The HD2 doesn't allow me to do this and I'm not going to adjust my style to fit this cruddy keyboard. If someone knows of a better keyboard then I'm all ears. I tried the RESCO keyboard and it's very good but there are no arrow keys to navigate around the text and no support for landscape mode. Therefore I uninstalled it but that's the kind of half-decent keyboard I'm looking for.
[HD2 General] kuzibri:
Try Fingerkeyboard 2.1. It's adjustable and supports also landscape. And with the addition of this:http://xdaforums.com/show...94#post5052394

it should be possible to type well.
[HD2 General] omneity:
Time to kill this thread off?

I think it's time the mods stepped in a deleted this thread, it's served no purpose and I think was only ever started as flamebait.
[HD2 General] kuzibri:
I would like to ask the mods to close this thread.
[HD2 General] sunking101:
Deary me. If anyone brings up any negative aspects of the handset they are trolling or flaming? The stock keyboard software IS awful, I haven't met anyone in the flesh who thinks my HD2 is anything but terrible to type on. This is a discussion about what can be done, I have asked for recommendations about other keyboards but all the fanboys just start getting abusive and childish. Then they throw their toys out of the pram and ask for the thread to be closed. :rolleyes:
[HD2 General] omneity:
Hardly seems like like an opener to practical discusion.

This thread was never good and it's now descended to the level of a kiddy flamewar.
[HD2 General] kuzibri:
Might it be that when you were a bit less sarcastic and cynical and not always in the role of the "only victim of this bloody HD2 keyboard", that people are more willing to help you? A lot of people are happy with their device and that should also be respected.
[HD2 General] kuzibri:
totally agree with you, but what I find amazing is that no one mentions the tone he is raising in his comments.
[HD2 General] sunking101:
You swore! I never have. 'Tone' is very, very had to grasp from text. I have never been aggressive towards members on here, only the HD2 device itself. My only sarcasm towards members has been in retaliation to theirs (towards me).
[G1 Q&A, Help & Troubleshooting] G1gurl:
How do I un-root my G1 if I have Haykuro's spl?
[G1 Q&A, Help & Troubleshooting] jonzina:
The first thing you must to do is downgrade the SPL . (This is very important you must to do this step first, DOWNGRADE THE SPL)

download the original stock SPL - http://www.megaupload.com/?d=6JMCDJJH

Rename the Original SPL to Update.zip and place it (now named update.zip) on the SD card (not in any folder)

Turn off the phone

Turn on the phone holding Home and End key till the recovery screen pops up.

Hit Alt W to wipe the phone, then hit Alt S to load the update.zip

After the update is complete, press Home and Back to reboot.

next

you must to load the factory DREAMIMG.nbh

1. Download the Original DreaIMG.nbh file: http://www.megaupload.com/?d=XXSQ0T7W

2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card (root SD card not in any folder)

3. 3. Turn the phone off if it is on.

4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.

5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.

6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29. You must do the next section to get back to cupcake.

Back to cupcake

Download the cupcake update from here - http://code.google.com/p/android-ro...=signed-kila-ota-148830.de6a94ca.zip&can=2&q= , then put it on your SD card, rename it to update.zip Turn off your phone and turn it back on by holding down Home and Power to get to recovery mode. In recovery mode (the ! screen) hit Alt L to see text, then hit Alt S to Apply the update.
[G1 Q&A, Help & Troubleshooting] supremeteam256:
Or just flash the RC29 image cause it has the stock spl with it. It will downgrade everything at once.
[G1 Q&A, Help & Troubleshooting] GoliathTheRipper:
^^^^ G1gurl have a Haykuro SPL he must to downgrade the SPL before downgrade to RC29. G1gurl if you downgrade to RC29 without downgrade the SPL you go to have a BRICK. downgrade the SPL first and the next step is downgrade to RC29
[G1 Q&A, Help & Troubleshooting] Ace42:
But why lose such acess? Are you returning it?
[G1 Q&A, Help & Troubleshooting] G1gurl:
Yes I'm having problems with it, I hate having to do everything all over again but when I touch it touches something else. Is there a way I can fix that or try to repair it?:confused:
[G1 Q&A, Help & Troubleshooting] jackslim:
Being able to calibrate the screen is one of the thing's I've always thought the G1 lacked, especially because I got fat fingers.

Have you tried wiping your data and reflashing your rom yet, to see if it's a software bug?
[G1 Q&A, Help & Troubleshooting] G1gurl:
Yes I've tried that too, but it goes away and then it starts again, but I''m trying out mlign hero rom and it's seems to be ok now. :)
[Windows Mobile Software Development] Chainfire:
Apps, games, benchmarks

Apps and games

This patch has been tested (at least somewhat) with the following apps and games:

- glBenchmark

- helios.dev "Test OpenGL"

- helios.dev "Test OpenGL 2"

- A few of my own OpenGL test tools

- Sense

- SPB Mobile Shell 3.5 (HW accel)

- Opera Mobile (GL mode, see this post by Tung_meister)

- Cubespace

- NFS Undercover [v0.1.5 doesn't seem to work nice, but v17 does?]

- Electopia Demo

- Boom Blox *

- Tower Defense **

- Flight Commander *

- Monopoly World *

- Xtrakt

- Experiment 13

- PowerVR demos *

* Reported to work best in "slow / anti-stutter" mode

** Reports differ on whether to use "slow / anti-stutter" mode or not

Note that if your phone is busy doing other things it will still make your phone slow! This patch only tries to fix

driver-related

stutter.

Please report your games/apps, whether they work better or not and in which mode they work right!

glBenchmark

Attached are some glBenchmark results of the various patch revisions. Some awesome improvements in the HD and Pro tests, as well as kTriangles/s. Though glBenchmark is nice, these figures do need to be taken with a grain of salt - it's not all that is important, smoothness and compatibility are also important.

Here's a grab out of the results.

Stock HD2 vs Patch 1.1

GLBenchmark HD ES 1.1: 487% ~ 1598 Frames up from 328

GLBenchmark HD ES 1.1 no GPU Skinning: 502% ~ 1647 Frames up from 328

GLBenchmark PRO ES 1.1: 107% ~ 229 Frames up from 215

GLBenchmark Pro ES 1.1 no GPU Skinning: 157% ~ 625 Frames up from 397

Swapbuffer speed: 496% ~ 556 up from 112

Averages: Lights: 116% ~ 1550 kTriangles/s up from 1350

Averages: Texture Filter: 159% ~ 2150 kTriangles/s up from 1350

Averages: Texture Size: 158% ~ 2150 kTriangles/s up from 1350

Averages: Triangles: 161% ~ 2150 kTriangles/s up from 1350

Test Suite

Well, it's not really a test suite, but here's 35mb of OpenGL ES v1 and v2 apps, games and demos I use for testing: http://rapidshare.com/files/408102039/Turbo3D-TestSuite.rar.html

Note that all of the included files are freely available from XDA, the authors' site, or a freeware app site.
[Windows Mobile Software Development] Chainfire:
Chefs and Developers

For Chefs

I am putting down some ground rules for using my driver in your ROMs:

The rules apply only to the Chainfire-Turbo3D-X.X package (you can do whatever you want with the TG01-D3DM package).

Cooking the driver patch is allowed

if-and-only-if

all of these conditions are met:

- The main release and support thread of your ROM is located on XDA-Developers.com

- The download of the ROM is "free for all" (with an exception for closed beta ROMs)

- The release and support threads note that this driver is used, "Chainfire" is credited for it, and includes a link to this thread ( http://xdaforums.com/showthread.php?t=592663 )

- Turbo3D configuration tool must be included, working, and be available through the start menu (or a subfolder thereof)

- All files must end up in \Windows

- You must test it before releasing (NOTE: Turbo3D uses a service! Make sure it is working!)

If you do cook it into your ROM, I request you let me know either by sending me a PM or posting in this thread (thank you). I feel these conditions are fair. If you can't meet all of them, feel free to PM me.

All DLL and EXE files in my CAB are signed with a dummy certificate, you might want to remove those signatures before cooking in.

For developers

This patch blocks 4 bits-per-subpixel modes, but these can still be used by setting EGL_CONFIG_ID in your GL configuration attributes. Attached is a CSV with a listing of all (original) configurations, including their various attributes (including EGL_CONFIG_ID).
[Windows Mobile Software Development] Chainfire:
Changelogs

v3.0 *FINAL*, 26.07.2010

- Final tweaks

- Marketplace release (EN-US)

- Ready for cooking

- Works on all GL-capable devices, though aside from Snapdragon I doubt you'll see any difference.

v2.60 BETA, 21.07.2010

- Complete rebranding to "Turbo3D"

- CL libraries have been removed, as they don't work and nobody uses them anyways

- Added "help" tab

- Fixed an issue that caused "unknown" apps always to run in "fast" mode, instead of the configured default GL mode

- Fixed an issue related to .NET based OpenGL ES v2 apps

- Frametime is back to 18 ms

- Added "Test Suite" link to first post

v2.50 BETA, 08.07.2010

- Added ordinals to proxied functions, improves compatibility for some OEM-built apps (for example on LG Expo)

- Completely reworked the loading and initialization of the driver, so no ROM files have to be overwritten anymore. This negates the need for a seperate patch for each different device model, and improves compatibility with custom ROMs and newer stock ROMs.

v2.0, 20.04.2010

- Adapted the driver to decide performance factors based on registry instead of hard-coded

- Added CF3DConf, the configuration UI for the driver

v1.1, 01.12.2009

- Added glModeSwitch app to switch between normal (fast) and anti-stutter (slow) modes

- Fixed nasty timing error
[Windows Mobile Software Development] VanKurt:
Hi Chainfire!

Thanks for the effort. I've just installed your patch. Sadly it doesn't change anything :(
[Windows Mobile Software Development] Chainfire:
- Did you soft-reset your device after installation?

- Which exact program/game are you having a problem with and what exactly is that problem.

Again, please note that if your device is busy with other things it will still slow down your game/app. Giving the phone a few minutes after boot-up of 'alone time' usually helps if that is the problem.
[Windows Mobile Software Development] rovex:
Experiment 13 seems to work ok for me, perhaps a little smoother if anything.
[Windows Mobile Software Development] naTpuoTXDA:
Chainfire Hi! First of all thank You for Your work both Leo and O2! Install your patch and electopia running much better than it was before. No lags! testing...
[Windows Mobile Software Development] VanKurt:
Yes, I resetted the device and closed every running app.

For testing I used a little test-app I just wrote. It displays 16 textured quads and runs only at 5/6 FPS (with or without patch).

(Screenshot and binaries attached)
[Windows Mobile Software Development] naTpuoTXDA:
Me too 5-6 fps
[Windows Mobile Software Development] Chainfire:
How sure are you that that is a driver issue and not a code issue? It didn't even run on any of my other phones I tried it on.
[Windows Mobile Software Development] RacerII:
Bloomblox is allot better after the patch!

I tried running test opengl , it scores allot lower after the patch however it runs pretty smooth.

So it looks very promising :)
[Windows Mobile Software Development] Chainfire:
Which Test OpenGL? helios.dev?

Numbers aren't everything. I've had it score in the 200k range but it didn't look very nice :P
[Windows Mobile Software Development] RacerII:
Yes that one , and yes thats why i posted the "however" ;)

Thanks so far Chainfire!
[Windows Mobile Software Development] zeus34:
Thaks Opengl work beter but Sense work me very slow
[Windows Mobile Software Development] VanKurt:
Hm, not 100% ;)

Do you have a simple demo app that runs smoothly using the drivers? I'd be interested to take a look at the code, just to see if I did something wrong...
[Windows Mobile Software Development] tnyynt:
Stuck!

Thread stuck!
[Windows Mobile Software Development] fards:
so far everything seems good to me..

never really had lagging, but all the things ive tested appear smoother.

sense is working fine (on the 148 rom)

thrown you 10 euro mate, at least you can buy a pint or two.

the shepherd neame christmas ale is highly recommended.
[Windows Mobile Software Development] zeus34:
i use test v1.48 sense (2.5.19211619) work very slow must be test hardreset my hd2
[Windows Mobile Software Development] Chainfire:
Sense is fine here, but I'm on 1.43... Can't test until I have 1.48, obviously.
[Windows Mobile Software Development] Cupra TDI:
Is it nessesary to disable sense before installing these drivers? Neos driverpack for the HD1 recommended that. How is it with yours?
[Windows Mobile Software Development] DialecticThought:
Opera has crashed 3 times in a half hour while having GL mode enabled, forcing me to perform a soft reset just to get the phone starting again. Though I loved the graphic enhancements this mode provided, it was unusable. Opera has yet to crash once with it disabled. Anyone else experiencing this?
[Windows Mobile Software Development] danielherrero:
same here....
[Windows Mobile Software Development] naTpuoTXDA:
No one crash in opera in both modes:-)
[Windows Mobile Software Development] adell_:
Hmph, Chainfire, what is your opinion about this?
[Windows Mobile Software Development] :
i noticed something on my acer s200 with your driver. all applications that are choppy run in landscape mode
[Windows Mobile Software Development] Chainfire:
Sorry for the absense, busy week. I hope to be able to update this thing some time next week - if not I'm afraid it'll have to wait 'til after new year.

I have read all your comments and am taking stuff into consideration. Thanks to those who have provided useful comments and information.

10 points for randomly combining all the graphics-related words you know without paying attention.

The 4-bits-per-subpixel modes are 16 bit color modes with 4 bits red, green, blue and alpha each. (The most common 16 bit color mode is 5 bits red, 6 bits green, 5 bits blue - though another often used mode is 5 bits red, green and blue each, and 1 bit alpha). For some reason these 4 bits modes are very slow - apart from looking crappy, of course.

It has completely nothing at all to do with either multisampling or antialiasing. If the application requests MS/AA it will still get it with this driver, simple as that.

And no, glBenchmark does NOT use 4xMSAA by default. It does have a 4xMS test if 4xMS is available, but most tests are run in plain whatever mode the GL drivers offers first.
[Windows Mobile Software Development] steveman29:
Hi, i would like to thank you chainfire for this driver, almost all of my games is faster and smoother. The only problem i am having is with galaxyhopper. This game makes my HD2 crash after only minutes of playing with this driver installed.
[Windows Mobile Software Development] Sc4Freak:
So presumably, by disabling the 16-bit colour modes, you've forced the applications to use 32-bit framebuffers instead.

How can this work in the general case? If an application wants to perform software blitting for some reason, or reads the buffers back into CPU, forcing different colour modes isn't going to play nice.
[Windows Mobile Software Development] Chainfire:
Who says 16 bit modes are disabled? 4444 modes are disabled? Read! 565 mode is now in fact the standard mose - as on virtually every other device. This in fact makes it more compatible, not less.
[Windows Mobile Software Development] naTpuoTXDA:
Chainfire, any news about FPUenable driver?:-)
[Windows Mobile Software Development] timma5:
Does it work @ HD1:confused:
[Windows Mobile Software Development] erdoke:
Does the HD have the same hardware so that it can utilize the same driver?
[Windows Mobile Software Development] Henry_Lee:
Yes, Opera crashed several times when GL mode was enabled. :(

And I think, new driver has affected on the power comsumption. When driver installed I lost power energy for 1 day. Without driver phone worked 1-2 days. :(

.
[Windows Mobile Software Development] christonabike:
I've found power consumption identical with or without the driver installed. Now running on the 1.61 rom with no problems (the stock 1.61 opengl drivers are the same in terms of performance as 1.43/1.48.. and similarly broken!)
[Windows Mobile Software Development] fards:
I've found a massive hike in Glbenchmark scores using the driver and 1.61 rom.

150% increase over the 1.48 rom.

http://xdaforums.com/showpost.php?p=5146655&postcount=185

without the 1.12 driver I'm getting better than the 1.48 roms without the driver but obviously nowhere near as good as with the driver on fast (and it looks awful).

1.61 rom sans driver

GLBenchmark PRO ES 1.1 :	214 Frames
GLBenchmark HD ES 1.1 :	289 Frames
Fill Rate: Multi-Textured 1.1 :	127795 kTexels/s
Triangles: Flat Shaded + Color 1.1 :	1324 kTriangles/s
GLBenchmark HD ES 1.1 no GPU Skinning :	295 Frames
Texture Filter: LINEAR_MIPMAP_LINEAR 1.1 :	1324 kTriangles/s
Lights: Parallel x 2 1.1 :	1259 kTriangles/s
Texture Size: 64x64 1.1 :	1324 kTriangles/s
Swapbuffer speed :	100
Texture Size: 128x128 1.1 :	1324 kTriangles/s
GLBenchmark Pro ES 1.1 no GPU Skinning :	388 Frames
Triangles: Textured 1.1 :	1324 kTriangles/s
Texture Filter: NEAREST 1.1 :	1324 kTriangles/s
Texture Filter: NEAREST_MIPMAP_LINEAR 1.1 :	1324 kTriangles/s
Texture Size: 256x256 1.1 :	1324 kTriangles/s
Lights: Omni x 1Lights: Omni x 1 1.1 :	1046 kTriangles/s
Triangles: Textured + Color 1.1 :	1324 kTriangles/s
3D Rendering Quality: Perspective Correction :	100% (Success)
Texture Size: 1024x1024 1.1 :	1275 kTriangles/s
Texture Filter: LINEAR 1.1 :	1324 kTriangles/s
3D Rendering Quality: Z-buffer Precision :	98.7% (Success)
Lights: Ambient x 1 1.1 :	1259 kTriangles/s
Lights: Parallel x 4 1.1 :	1259 kTriangles/s
Lights: Spot x 1 1.1 :	964 kTriangles/s
CPU Performance: Integer :	20120
Lights: Parallel x 8 1.1 :	1030 kTriangles/s
Texture Filter: NEAREST_MIPMAP_NEAREST 1.1 :	1324 kTriangles/s
CPU Performance: Float :	1964
Triangles: Smooth Shaded + Color 1.1 :	1324 kTriangles/s
Texture Filter: LINEAR_MIPMAP_NEAREST 1.1 :	1324 kTriangles/s
Texture Size: 512x512 1.1 :	1324 kTriangles/s
Lights: Parallel x 1 1.1 :	1259 kTriangles/s
Fill Rate: Single-textured 1.1 :	89702 kTexels/s
3D Rendering Quality: Sub Pixel Precision :	100% (Success)
3D Rendering Quality: Bilinear Filter :	100% (Success)
3D Rendering Quality: Trilinear Filter :	100% (Success)
[Windows Mobile Software Development] Toss3:
GLBenchmark Pro 1.1 Result Details
Texture Filter: NEAREST_MIPMAP_LINEAR 1.1 :	2141 kTriangles/s
Triangles: Textured 1.1 :	2174 kTriangles/s
Texture Size: 512x512 1.1 :	2109 kTriangles/s
Texture Filter: LINEAR_MIPMAP_NEAREST 1.1 :	2174 kTriangles/s
CPU Performance: Float :	1531
Lights: Omni x 1Lights: Omni x 1 1.1 :	1030 kTriangles/s
3D Rendering Quality: Z-buffer Precision :	98.7% (Success)
Texture Filter: NEAREST_MIPMAP_NEAREST 1.1 :	2174 kTriangles/s
Texture Filter: NEAREST 1.1 :	2158 kTriangles/s
Texture Size: 128x128 1.1 :	2190 kTriangles/s
GLBenchmark Pro ES 1.1 no GPU Skinning :	636 Frames
Lights: Parallel x 4 1.1 :	1455 kTriangles/s
Lights: Parallel x 8 1.1 :	1030 kTriangles/s
3D Rendering Quality: Sub Pixel Precision :	100% (Success)
CPU Performance: Integer :	22271
3D Rendering Quality: Bilinear Filter :	100% (Success)
Fill Rate: Single-textured 1.1 :	122880 kTexels/s
Texture Filter: LINEAR 1.1 :	2158 kTriangles/s
Texture Size: 64x64 1.1 :	2190 kTriangles/s
Lights: Ambient x 1 1.1 :	1716 kTriangles/s
Lights: Spot x 1 1.1 :	964 kTriangles/s
GLBenchmark HD ES 1.1 :	1629 Frames
Triangles: Textured + Color 1.1 :	2060 kTriangles/s
3D Rendering Quality: Trilinear Filter :	100% (Success)
Triangles: Flat Shaded + Color 1.1 :	2223 kTriangles/s
Texture Size: 1024x1024 1.1 :	2043 kTriangles/s
Lights: Parallel x 2 1.1 :	1684 kTriangles/s
Fill Rate: Multi-Textured 1.1 :	130253 kTexels/s
GLBenchmark HD ES 1.1 no GPU Skinning :	1660 Frames
Triangles: Smooth Shaded + Color 1.1 :	2207 kTriangles/s
GLBenchmark PRO ES 1.1 :	229 Frames
3D Rendering Quality: Perspective Correction :	100% (Success)
Texture Filter: LINEAR_MIPMAP_LINEAR 1.1 :	2141 kTriangles/s
Texture Size: 256x256 1.1 :	2158 kTriangles/s
Swapbuffer speed :	555
Lights: Parallel x 1 1.1 :	1716 kTriangles/s

This is with the 1.61 stock rom and chainfire's drivers.
[Windows Mobile Software Development] denis.ovod:
problem with MD3D

after reseting texture for some sampler (eg device->SetTexture(index, NULL);), there is no way to set it back.

can be observer in Hologram app for exmaple or on any MD3D WM6 SDK app.

returning to original drivers - fix the problem in cost of render speed.
[Windows Mobile Software Development] DomSim:
well, installed and didnt brick my sprint touch pro2. i cannot give details about improvments as glbenchmark will not run correctly on my device for some reason.
[Windows Mobile Software Development] vgeorg:
Video performance

Can anyone confirm whether the patch removes that annoying stuttering and missing frames when playing h.264 encoded video, either CorePlayer or HTC Album? Not much into games but I'd love to see such a powerful processor delivering a decent playback on video files...
[Windows Mobile Software Development] HeavyX:
driver patch 1.1

Hi there,

i am quite new to the forum. I've just installed the patch on my HTC Leo with ROM 1.48 and everything is working fine. I had a little scepticism on the reported results, but even look and feel of HTC Sence has improved.

Really nice work.

Thank you very much, Chainfire!

greets,

HeavyX
[Windows Mobile Software Development] ThoroSOE:
I found one very obvious improvement. After flashing my ROM to 1.48 (on 1.43 I have had applied the drivers so 1.48 was the chance to test) I watched a .gif file without Chainfire's driver - and it was played in slow motion. Then I installed the driver - and just after that it runs just fine and as fast as it should.

(.gif was the one with the turning dancer figurine's silhouette that is supposed to be linked to right end left brain usage; 300x400 px)
[Windows Mobile Software Development] gottiz:
is de patch voor hd2 nou goed of niet
[Windows Mobile Software Development] zakariae:
hi, I can confirm some improvements on my HD (Blackstone) with LEO rom Sense2.5 :D

thanks very much for the patch :D:D:D
[Windows Mobile Software Development] DMAND:
^ You do know that this is for the HD2 (Leo) right and not blackstone for which there's another driver pack