Anyone going to create a Manila Touchflo for the BA?
i think that is not so easy (impossible ?)
manila is just for vga (640x480) screen.
so it can´t be displayed on a blueangel´s qvga (320x240) screen.
manila need much graphic power.
the diamond use a special 3d graphic chip to render it.
i think manila required biotouch, too.
the blueangel display driver is not compatible with biotouch
wmvfan said:
i think that is not so easy (impossible ?)
manila is just for vga (640x480) screen.
so it can´t be displayed on a blueangel´s qvga (320x240) screen.
manila need much graphic power.
the diamond use a special 3d graphic chip to render it.
i think manila required biotouch, too.
the blueangel display driver is not compatible with biotouch
Click to expand...
Click to collapse
We have the regular TouchFlo interface working for virtually every device (haven't tried it in my Wallaby ), which also uses BioTouch (afaik), so I don't think that would be a problem. As far as the qvga thing, look at this (from the Kaiser forums)
http://forum.xda-developers.com/showthread.php?t=395337&page=8
Apparently, there are a few guys in there that might be able to pull this one out.
The only thing that I will agree with you is the fact that we have a huge disadvantage hardware-wise (3D acceleration to be more precise), even when compared with the Kaiser... but don't let your hope down. Someone will come up with something. For instance, ThrottleLauncher 0.9.1 has it pretty close.
I still think that my BA has one more upgrade to go through before I can no longer upgrade(WM7, here I go)
wmvfan said:
i think that is not so easy (impossible ?)
manila is just for vga (640x480) screen.
so it can´t be displayed on a blueangel´s qvga (320x240) screen.
manila need much graphic power.
the diamond use a special 3d graphic chip to render it.
i think manila required biotouch, too.
the blueangel display driver is not compatible with biotouch
Click to expand...
Click to collapse
I was totaly wrong.
watch this great work:
http://forum.xda-developers.com/showthread.php?t=398173&page=2
Great link! Anyone have it working on the BA yet?
If not I will test this a little later and post my feedback here or there in the manila link
it works on my blueangel.
i get more than 3.5 frames.
controls doesn´t work yet.
just the home screen is usable.
Related
Hi,
I don't know if it's due to the trueVGA resolution but many aplication doesn't work properly (especially games) on my Athena. I wonder if there isn't any QVGA simulator, I mean an application with which the QVGA application would work and would just be stretched on the VGA screen.
I hope that a such program exists !! (Or an another solution)
Thanks for any answer in advance.
disable true vga and you will get what you want
Is thear any way to get the LG ks 20 Home plugin work on VGA device ???
What device are you talking about?
i know thear is a lg home plugin for not lg device. you got it at xda dev´s by sing the search funktion.
http://forum.xda-developers.com/showthread.php?t=342866&page=27
it work on lots of qvga pda´s with windows mobile 6.
but when i install it on my vga pda, thear is an error.
i need a new dll or something like that, what let the programm work on vga shreens
I want too, a vga version of the above plugin.
I own a qtek9000 (wm6).
Thanks in advance
http://forum.xda-developers.com/attachment.php?attachmentid=62200&d=1197935655
See if that one works... if it does, let me finish patching it
i can install it, but it looks so:
Ok, that means that my patch for it to work on WM5, makes it work on VGA devices too.
When I have the time, I'll increase the size of the graphics so that you can use it on VGA resolution. BTW: what's the standard VGA resolutions?
VGA = 640x480
My question is simple...
I have been using QVGA screen devices for a long time and I have invested a good ammount on softwares that display well on QVGA screens.
Now I'm thinking of doing an upgrade and I have pinpointed the HD as my next device, but since I have invested a lot money on softwares, I don't want to upgrade to a new phone and find all these softwares unusable on a WVGA screen.
Will the programs designed for QVGA display properly on a WVGA screen?
My common sense tells me that no, it won't but I have read that it will display without problems.
Any thoughts anyone?
where did you read that it will display with no problems?
Very few apps are made for WVGA and I cannot image that HTC lets this be a show stopper, since it will take years and years before WVGA is as standard as QVGA is.
The same goes for VGA though, which is also just catching on in mainstream, yet my VGA Diamond has no problems running anything whatsoever. Some QVGA apps just get blown up to fit the screen and run just like on a QVGA screen, yet I wonder how this would work when the aspect ratio is no longer 4:3 (as with QVGA, HVGA and VGA) but instead 16:9 (WVGA). Stretching is ugly so with apps that need to maintain the aspect ratio (anything other than apps that can resize infinitely like Operah, Windows Mobile etc) we would likely see black boxes on top of and below the app.
Copy pasted one of my own old posts from another topic, which had the same question but for VGA on the Raphael.
WM has a so-called compatibility mode. If an app is not specifically compiled to tell WM it knows about resolution and DPI settings, WM presents your device to the program as 240x320 QVGA. This way, most QVGA apps simply run on VGA. (And I can verify that at least on the Diamond, most apps just work). WM then simply scales the application to fill the screen. (One way to notice if this is happening with an app is that you can see the text is smooth and looks high-res, except on the menu bar at the bottom)
Actually that was quite a nice move of MS. However, there is a bug with compatibility mode and 320x320 devices (like the Treo800w) that prevents some apps from running. Luckily, the Raphael is not one of those devices.
However, of course, some apps do tell WM they know about resolution and DPI, but aren't made to support 480x640 devices like the Axim v51, Diamond and Raphael, those apps may look weird (though they don't seem to be numerous), but generally still work.
Click to expand...
Click to collapse
If I recall correctly, however, non-resolution/dpi-aware applications ran on odd resolutions like WVGA for the Touch HD are still represented as 320x240, and will be stretched to use the entire screen (in other words: fugly). I know this is the case for 320x320, and I think it would be a safe bet to assume the same for 480x800.
For applications that are resolution/dpi-aware, it all depends on how the developers did it. Black border at the bottom and top, correctly scaled, etc, it's all possible and completely up to how the developer handled this in their code.
Chainfire
Thanks for the answer.
That was very well explained.
What I read that it won't have problems was perhaps with the fact that WM will stretch the program to fit the screen, but it wasn't as well explained as your post.
So now I know that it's possible that half of my programs will be stretched on the screen and it will look crappy, the other half will have black borders around...
WVGA Themes
I just wonder if all the (beautiful) themes created for Diamond will be correctly displayed with the Touch HD ?
As I'm creating my own (for Diamond) and first one, I hope I can use it with the HD WVGA screen.
Thanx for informations.
WVGA has the same aspect ratio of the WQVGA
WVGA 480x800 (Touch HD, Sony XPERIA)
WQVGA 240x400 (Samsung Omnia)
Being an owner of a Samsung Omnia I found out that there are very few software that wont run on non a standard QVGA resolution.
Good thing about it is that most important and recently updated software do take into consideration the modern variable display sizes and aspect ratios.
This is a promising trend, software companies tend to release fixes/upgrades for their software for these new resolutions
So I wouldnt worry so much!
ydg said:
I just wonder if all the (beautiful) themes created for Diamond will be correctly displayed with the Touch HD ?
As I'm creating my own (for Diamond) and first one, I hope I can use it with the HD WVGA screen.
Thanx for informations.
Click to expand...
Click to collapse
I recently installed Manilla2d on the omnia, the themes have to be modified for the omnias resolution 240x400 images, backgrounds, icon possitions etc, therefore no theme for diamond will be directly usable with the touch hd, there will have to be modifications on them to work
mkMoSs said:
I recently installed Manilla2d on the omnia, the themes have to be modified for the omnias resolution 240x400 images, backgrounds, icon possitions etc, therefore no theme for diamond will be directly usable with the touch hd, there will have to be modifications on them to work
Click to expand...
Click to collapse
With this Forum and community and the other WVGA topphone Xperia, these forums will be soon filled with people working on these modifications....
I am not worried at all about this
You can try Force high resolution. You can find it at pocketpcfreeware.com.
Tried the latest cab from here:
Update 11: Direct from Chainfire:
=========================
TF3D QVGA - Release #2
http://forum.xda-developers.com/showthread.php?t=430718
Prior to installing the cab, I unzipped the OpenGL ES software drivers from here...
http://forum.xda-developers.com/attachment.php?attachmentid=121298&d=1223892257
...to the \WINDOWS directory.
The results: TF3D-QVGA installed in probably 10 minutes. Very slow progress at the beginning, but when the bar hit the 50% mark, installation was completed just after one or two more minutes. Startup time of TF3D is quite good, too. Takes about a minute to fire up. The drawbacks: The software 3D driver seems broken on the BA. No textures, but all white surfaces. One can see, though, that the shapes are rendered correctly. The clock on the Home tab flips correctly, messages on the Mail tabs fly in and out like they should etc. Unfortunately rendering is a tad slow, too. Not very smooth, yet no stills either. One can see the animations, but even if the textures were okay, it would be too slow to really enjoy.
Does anyone have an idea where to find suitable OpenGL ES software drivers for the BA?
Cheers.
which rom are you using ?
on my rom installing takes 30min and startup after soft resett takes 30 min, too.
i also get the white textures.
The "old" Helmi WM6 with German language files, which is really a fantastic ROM (always came back to it). Btw, when I tried TF3D, I already had loaded all kinds of stuff on my device (only about 15MB of internal memory free), so I'm really not talking about a virgin install, either.
BA was never designed for 3D graphic the first place, if you guys really like Manilla interface, I strongly suggest try out the Manilla 2D. just an idea.
imatrix said:
BA was never designed for 3D graphic the first place, if you guys really like Manilla interface, I strongly suggest try out the Manilla 2D. just an idea.
Click to expand...
Click to collapse
I know, I know. M2D is great, but I miss the opportunity to view multiple appointments on the home tab.
Is it possible to put a TouchFLO 3D on a Jade?
Yes? >> Where can i download it?
No >> Why not?
No, the Touch 3g has no 3D hardware.
one of the reasons why jade has much better standby time than diamond i guess, besides the battery...
3D on Jade
I do not understand the statement that Jade does not have 3D hardware. I use TomTom and see a 3D screen at all times, also SPB Traveller, software in which a tab with a turn capable 3D earth globe is available. Both programs, they even used to run on my very old Qtek S200 too. I do not understand what does mean having a 3D capable graphical interface versus not having it when it is the software which makes the difference. In other words, Open GL or Direct X are used to run with or without 3D hardware acceleration on desktop PC's. What is the real difference when it comes to PPC? I ignore that and I just want to understand it before I give up the idea of choosing between Manila 2D (shipped) or Touch 3D (wished) Regards
Missing 3D hardware probably isn't a problem. But touchflo 3d has been designed for VGA, not QVGA. And _if_ Touchflo 3D required 3d hardware accelation, then porting will be even more difficult.