I've been playing about for a couple of days now with this graphics acceleration problem.
Yesterday i was trying out different DLL's and editing the registry, and i had put "libGLES_cm.dll" and "libGLES_cm.lib" into my windows folder. Today i was trying to install manila as many people have not been able to get it to work, it installed fine and then I clicked the "tap to start HTC home" on the homescreen and it asked me to allow "libGLES_cm.dll" and it is running.
However, it's a bit disproportioned and very very slow (0.75FPS).
I think it may be needing some more missing DLL's and the registry might need tweaking.
Also without libGLES_cm.dll (as the device is shipped) Manila fails to initialise. so HTC must have some sort of OGL drivers that they are using, but not supplying for Kaiser.
I used Vincent 3D libGLES: http://downloads.sourceforge.net/ogl-es/ogles-bin-1.0.0.zip?modtime=1144798031&big_mirror=0
and Heres a link for Manila: http://www.megaupload.com/?d=G5X13UZF
I'll try get a screenshot up in a minute but my kaiser's being a little slow now.
I'll try work on this more see what i get.
Any help would be appreciated
Thanks
Sorry, accidentally posted in the wrong section
Reposted in correct section, can a mod or admin delete this one please?
If you read the other Manilla thread you would know that Manilla is VGA. All of the icons need to be resized for QVGA. GLES is not enabled on the Kaiser so you can call for the dll all you want, but you still won't get any accleration or 3d out of it.
All of these possibilities have been investigated for acceleration &/or 3D.
As for Manilla, there is an effort & some progress being made in the other thread: http://forum.xda-developers.com/showthread.php?t=363500
I suggest that is probably the place to post your willingness to help/investigate in the effort to get it converted to QVGA & to spped it up.
As for acceleration & 3G I would look at some of the info Chainfire has posted as he has invested at least 100 hours into the effort.
I understand that but my point was that the libGLES_cm.dll is currently working on my device so there must be someway of getting acceleration, i was just posting so that others could look at this and possibly find a way to get gFx acceleration, screenshot on the thread i posted in the correct section http://forum.xda-developers.com/showthread.php?t=364459
dariushuntly said:
I understand that but my point was that the libGLES_cm.dll is currently working on my device so there must be someway of getting acceleration, i was just posting so that others could look at this and possibly find a way to get gFx acceleration, screenshot on the thread i posted in the correct section http://forum.xda-developers.com/showthread.php?t=364459
Click to expand...
Click to collapse
Isn't that just a software driver.
I can emulate DX10 feature in software, still doesn't give me any hardware acceleration... since it's software you know.
Yes it is software, it's the library containing the what is needed for OpenGLES to run, i could be wrong but seeing as it's needed by manila, it shows that HTC is planning to impliment a driver in the future.
Also i think it shows a possible sign for getting acceleration onto the kaiser
Just a thought, any chance someone has a LG KS20 dump?
Rom and registry?
i downloaded the dump off the FTP but it seemsto be corrupt as file sizes don't match up.
Thanks
LG has the same problem. Chainfire also pulled out the KS20 drivers & tried porting/rewritting to Kaiser with no luck.
As for th ogles, I think that manilla is looking for it & finding it yes. But obviously there is still no acceleration as evidenced by the FPS rate. The portion of the chip that would optimize/use the dll's is either not there or is deactivated. I tried calling for ogles in other proggies with some luck as to function, but performance has never changed or has always worsened. So yes, it's the library, but it has no effect on the hardware needed to support the ogles.
I really don't think you can look at this app as any proof that HTC plans to use any acceleration on the Kaiser because this was clearly not written for the Kaiser. It's VGA after all.
Believe me, there are few more than me that would like to see this pulled off, especially by a forum member, since HTC says it's way to hard of a process for them to pull off any time soon. But after many long months off following & conversing w/ chainfire, it's still nothing more than a dream & chainfire is the guy that has brought us some of the most amazing features for our WM6 devices not to mention the dynamic duo cmonex & olipro.
I hope you prove me wrong in spades, I'd like nothing better than to see "dariushuntly" hoisted up on our shoulders as the acceleration saviour.
manila youtube vid
http://msmobiles.com/news.php/7064.html
dariushuntly said:
Yes it is software, it's the library containing the what is needed for OpenGLES to run, i could be wrong but seeing as it's needed by manila, it shows that HTC is planning to impliment a driver in the future.
Also i think it shows a possible sign for getting acceleration onto the kaiser
Just a thought, any chance someone has a LG KS20 dump?
Rom and registry?
i downloaded the dump off the FTP but it seemsto be corrupt as file sizes don't match up.
Thanks
Click to expand...
Click to collapse
What makes you think this was ever meant for any MSM7X00-based devices?
I spoke with HTC PR in Sweden recently about an official upgrade to TouchFLO for the Kaiser. (Ie if the cube was destined for Kaiser devices) and the answer was no, no planned upgrades to touchflo functionality.
Ie no official cube, much less Manilla. In other words it pretty much has nothing to do with a future driver update.
Sorry if you think it's negative or that I'm rude, I just think it's better to be realistic about this issue and try to get it solved rather than to rely on a pipedream.
The only thing it really does confirm is that future HTC devices will have HW accelerated graphics and drivers.
undac said:
The only thing it really does confirm is that future HTC devices will have HW accelerated graphics and drivers.
Click to expand...
Click to collapse
01234567890
And VGA.
Related
Now that we have a working implementation of ArcSoft MMS for the Himalaya, is there any chance of bringing the camera application over from a Universal? I understand that the camera hardware is different, but I presume the application works through some sort of device driver, which we obviously already have on the Himalaya WM5.
Alternatively, has anyone managed to get the camera app from WM2003SE working under WM5?
Now the MMS issue has been solved, this is the only other major reason remaining for my not upgrading. I already upgraded once, but the lack of support from the major software I use and these other two issues meant that the upgrade effectively crippled my device. Now software support is starting to trickle through, it's just these core applications which need solving.
WARNING! DO NOT INSTALL THE 'Camera2K5.cab' FILE POSTED BELOW BY johnney ON HIMALAYA DEVICES. IT WILL LOCK UP YOUR DEVICE! THE POSTER OF THIS FILE MISUNDERSTOOD THE QUESTION!
well if it's not a general device driver then you cant use it
much like if you have a ati graphic card on your pc you cant use a nvidia driver
If you re-read my post, I wasn't suggesting the use of another driver for the camera, but rather the use of the one which is already there. I said the camera software probably interfaced with the camera through a device driver, so theoretically the software should be hardware independant.
grayhaze said:
If you re-read my post, I wasn't suggesting the use of another driver for the camera, but rather the use of the one which is already there. I said the camera software probably interfaced with the camera through a device driver, so theoretically the software should be hardware independant.
Click to expand...
Click to collapse
Thry this patch!
Can anyone confirm that this patch works on a Himalaya? I thought it was intended for a BlueAngel...?
WARNING............
DO NOT INSTALL THE CAMERA PATCH....
It just locked up my device completely....
had to hard reset it
I hate you sooooo much dude!!!!!!!
3 hours of my life wasted starting now
SICK SICK SICK!!!!
All my data lost, holy crap
:evil:
San
Johnney you are a savior! My BlueAngel's cam is working on WM5!!!!!
Excellent Job! Thanks m8
Can someone please remove that file from download before other Himalaya users mess up their devices? I was quite clear in my original post, and this guy obviously didn't test the file himself before urging others to use it. :x
This file works with Blue Angel! So let the file there for other BA users to get it! Just change the title to BA Camera Patch
As the original question related to a fix for the camera on Himalaya devices, I don't really see the point in changing the thread to a BlueAngel one, other than to further confuse people.
By all means start another thread with this information for BlueAngel owners, but in the meantime we're still looking for a fix for the Himalaya.
...???...
Few minutes ago I've tried this patch(I was ready for hard reset). This are my experiences:
-it DIDN'T lock my device!
-it disables the camera totally. That means no capturing interface,only album available.
...that means: It is for Himalaya with BuzzROM 1.60a unuseful.
Any ideas about camera in Himalaya yet?
Buzz can fix the camera issue, I assume he doesnt have time to do it at the moment
Himalaya Camera Patch
Hey guys, I used the following Patch and now my Himalaya under 1.60c.00WWE ROM has a better video camera.
It records great even at the awsome size of 240x180!!! :roll:
Here it is...
Best regards,
Rayan
Re: Himalaya Camera Patch
Rayan said:
Hey guys, I used the following Patch and now my Himalaya under 1.60c.00WWE ROM has a better video camera.
It records great even at the awsome size of 240x180!!! :roll:
Here it is...
Best regards,
Rayan
Click to expand...
Click to collapse
@ Rayan,
It's better quality, at least we know what object we were recording at, lol.. i mean it has clearer output now, but I notice when saving it seems slower. Btw, what did you change, did you increase or decrease some of the value. thanks
regards,
ferioz
@ferioz
First of all, let me say that this patch was not created by me, I found it over at Buzz_Lightyear's website (www.buzzdev.net ).
Yeah, the saving part of the process takes much longer to complete, but (correct me if I'm wrong) I think it's because now we are saving the clip to ROM, not RAM. That is, when recording it caches the video to RAM and then transfers it to ROM or SD which is also slower than normal RAM.
Conclussion, better this than nothing right? :wink:
Peace!
Rayan
So the Tilt and video drivers are hard enough on me already... and HTC is already pursuing me to upgrade my mobile so I can get TouchFLO 2.0...
Hopeing somebody can port this to kaiser when it comes out... Go Dutty
http://www.mobilemag.com/content/100/333/C14466/
Looks good finally something to raise an eyebrow at....
Err... Sorry about that... TouchFLO 2 is codenamed Manila... For more information, search for manila on xda...
Hmm...looks interesting....future studies on this should confirm any thoughts regarding this
[manilla] touchflo 2
i download it & install normal
but when i run it
there is a message for certificate
anyone can remove the certificate
sorry for my bad english
manila youtube vid
http://msmobiles.com/news.php/7064.html
I found the leak and installed it (10MB!!!) but it won't run. Oh well.
It does run... just not as well... For improving it to a sad FPS instead of a very sad FPS apply some scripts or tweaks found at http://forum.xda-developers.com/showthread.php?t=363500&page=8
It works on all phones not just HTC...
Hello everyone, I've been searching all these roms but it seems that there isn't one single ROM with manilla. Can I install this on Universal? Tks
Short answer? No.
Long answer? Manilla (aka TouchFlow 3D) requires far too much RAM and processing resources to run properly on our Uni's. The biggest problem is (seems to be?) the lack of decent hardware drivers, since HTC wrote custom ones for the TouchPro, etc.
Of course it's a few months since I even attempted using any of the ports, so things may have changed, though I somehow doubt it.
-PJC
pjc007 said:
Short answer? No.
Long answer? Manilla (aka TouchFlow 3D) requires far too much RAM and processing resources to run properly on our Uni's. The biggest problem is (seems to be?) the lack of decent hardware drivers, since HTC wrote custom ones for the TouchPro, etc.
Of course it's a few months since I even attempted using any of the ports, so things may have changed, though I somehow doubt it.
-PJC
Click to expand...
Click to collapse
But what about the 2D version?
I had one in my qtek 9090 (which is older than uni) and it ran just fine!
u can use this big-mem ROM by Cotulla: http://forum.xda-developers.com/showthread.php?t=468776 and install manila2d .. but if u have 64Mb uni, u will be memory low for something more with manila (i got 15-10Mb free with my 64Mb-Uni) .. its work very nice in portal mode.. and its so big, great for in-car use or similar
after install of manila, they will be small, not on full screen.. you must find VGA theme for manila2d .. search on forum
this is easy for install, ask if is problem find .. i think that on 128Mb uni it is will work very nice
//sorry for bad eng, big hello from Serbia
I would recommend to use ThrottleLauncher (just Google for it).
With the TF3D theme and with the Manila WeatherPanel installed it is great and fast (10-15 MB RAM, yes I know, but with a 128 MB Uni it's awesome ). But if you turn on the flash clock you will see, how many resources it needs, and it works only with 2-3 fps. But at least it is very customizable...
That's it,
DOMy
Hey Guys,
I know that this has been discussed a hundred times .
But let me at first explain:
This goes out to all you chefs which are cooking the roms (I'm not capable to cook one by myself)
So what I would like to have is a Kaiser ROM with a working Touchflo3d.
I've read and searched for hours and hours and found the rom from L26, but I think this had been an really early state. Now the drivers have changed and improved.
So is there anyone out there who is able to cook a rom (no matter if 6.1 or 6.5) with working TF3D and drivers?
I found out that there is a working version in this tread: http://forum.xda-developers.com/showthread.php?t=465507
But it was not working with my rom (M-Opal 1.0) due to cooked M2D.
So it would give hmm a bounty of 35€ (€ not dollars) if anyone would prepare a working, fast rom with TF3D.
And I am also sure that there will be a lot of other useres who would love it.
Best regards,
Matthias
Maeffjus said:
And I am also sure that there will be a lot of other useres who would love it.
Click to expand...
Click to collapse
Not me ...........................
That being said, here is the latest.
http://forum.xda-developers.com/showthread.php?t=458116
Maeffjus said:
Hey Guys,
I know that this has been discussed a hundred times .
But let me at first explain:
This goes out to all you chefs which are cooking the roms (I'm not capable to cook one by myself)
So what I would like to have is a Kaiser ROM with a working Touchflo3d.
I've read and searched for hours and hours and found the rom from L26, but I think this had been an really early state. Now the drivers have changed and improved.
So is there anyone out there who is able to cook a rom (no matter if 6.1 or 6.5) with working TF3D and drivers?
I found out that there is a working version in this tread: http://forum.xda-developers.com/showthread.php?t=465507
But it was not working with my rom (M-Opal 1.0) due to cooked M2D.
So it would give hmm a bounty of 35€ (€ not dollars) if anyone would prepare a working, fast rom with TF3D.
And I am also sure that there will be a lot of other useres who would love it.
Best regards,
Matthias
Click to expand...
Click to collapse
there are already tf3d roms and if your looking for one that will work flawlessly on our kaisers, not gonna happen.
Leo (L26) made a decent rom L26_KaiserTouch_V4_M3D that actually encompasses TF3d. I have not tried the others but I do love his rom even though it is not as smooth.
I wonder how it will work with 6.5 drivers. I'm going to take a shot at cooking it into josh's rom for you. We'll see how this goes.
Why should there be no interest in TF3D on a Kaiser? (@denco)
Because I've seen a lot of videos on Youtube where it is running smooth and it also seems nearly bugless.
Like this one: http://www.youtube.com/watch?v=wPf_gjMFBHs
or these one: http://www.youtube.com/watch?v=oDduRgWFweM&feature=related
What I want to fullfil my bounty should be:
1. Running TF3D
2. OpenGl-Drivers integrated in ROM (I think it is necessary to use TF3D)
3. The Standby bugfix should be integrated, which is located under the link in my first post.
4. Look and Feel like on the Videos (not any kind of "Tiger" or strange "Tribal" as system theme)
Optional but highly welcome: German Language
Or is it possible to install some kind of language pack? (I'm using WM since hmm 6 or 7 years but I've never seen such a thing)
I've tried the L26 ROM and it was not satifying to me because the speed was really low compared to the TF3D's on the youtube videos and it seemed very buggy.
If I'm not completely wrong, the version of TF3D from my first post is in an advanced state compared with the on from L26.
Thanks in Advance!
Would be nice to find some people who will help to increase the bounty!
Maeffjus said:
Why should there be no interest in TF3D on a Kaiser? (@denco)
Because I've seen a lot of videos on Youtube where it is running smooth and it also seems nearly bugless.
Like this one: http://www.youtube.com/watch?v=wPf_gjMFBHs
or these one: http://www.youtube.com/watch?v=oDduRgWFweM&feature=related
What I want to fullfil my bounty should be:
1. Running TF3D
2. OpenGl-Drivers integrated in ROM (I think it is necessary to use TF3D)
3. The Standby bugfix should be integrated, which is located under the link in my first post.
4. Look and Feel like on the Videos (not any kind of "Tiger" or strange "Tribal" as system theme)
Optional but highly welcome: German Language
Or is it possible to install some kind of language pack? (I'm using WM since hmm 6 or 7 years but I've never seen such a thing)
I've tried the L26 ROM and it was not satifying to me because the speed was really low compared to the TF3D's on the youtube videos and it seemed very buggy.
If I'm not completely wrong, the version of TF3D from my first post is in an advanced state compared with the on from L26.
Thanks in Advance!
Would be nice to find some people who will help to increase the bounty!
Click to expand...
Click to collapse
Yes it can run smoothely'ish the problem encountered is lack of driver to be able to sleep device in the correct manor.
But there is a patch to solve that kind of problem or am I wrong?
Q: Whenever I try and put the device into sleep mode, it powers off instead?
A: Try disabling the today time-out. Also, make sure you installed the standby CAB right.
Click to expand...
Click to collapse
Taken from the Linked TF3D thread...
Maeffjus said:
But there is a patch to solve that kind of problem or am I wrong?
Taken from the Linked TF3D thread...
Click to expand...
Click to collapse
No there are work arounds but no real fix
Im still TF3D fan, but after many bug and slow on my Kaiser, i have to move on.. if somebody create or develop ROM with it, i will give a try..
With that standby fix Touchflo3d is disabled automatically before sleep mode. Biggest problem for me was that when the device wakes up it needs to launch touchflo again and that process was kinda slow. Sometimes it just get stuck and needed softreset.
Still, I would be curious to see how smooth tf3d would be cooked in with newest builds and drivers...Also, if I remember right 3d drivers won't work if you have super ram hack in your rom.
Whatever ;-) ...
Also, if I remember right 3d drivers won't work if you have super ram hack in your rom.
Click to expand...
Click to collapse
I don't mind if there is a super-ram-hack or what else, in my opinion it should WORK
Also I think that all of you shall take a look in your money-bag if there is a possibility to make it a little more lucrative to work on such a rom.
As I also stated out that I will pay my full bounty only if it is able to run on latetest state of development - that means not that the chef has to develop touchflo3d once again but without bugs ;-) it means only that it should be able to run as good as possible at the moment.
But as I read yesterday evening, I saw that there are maybe two possibilities to get rid of the standby bug, but - forgive me - if did not looked detailed at these solutions - so I don't know how these work but maybe one of them is working better?
And when I'm right - all the roms with TF3D cooked in are with an earlier driver-version. The younger versions of the driver have improved, if I understood the development news made in the dev. and hack. section.
The TF3D-cooked-in-rom-threads are nearly all dated arround december '08 - and I read a lot of them
Maeffjus said:
Why should there be no interest in TF3D on a Kaiser? (@denco)
Click to expand...
Click to collapse
I am not saying that if you posted a working TF3d rom that no one would flash it, I would. But what is the effort /reward ?
What about it would make it better than my M2D rom ? Or anyone's 6.5 rom.
Enough great chefs put more than enough time into it, and could not get adequate drivers to make it smooth enough to keep as an everyday rom nor could they get by the stand by problem.
TF3D is M2D with some nice 3D touches that is all, am I missing something ? Is it head and shoulders above M2D or Neo Titanium, I don't think so. Which is why no one really cares to put in all the effort to make it work , nor is anyone really willing to spend any funds to make it work.
I am not being a contrarian or a nay sayer just for arguement sake, really With M$ coming out with cHome and Titanium, SPB out with MS 3, HTC coming out with Sense, there is a reason why people took porting TF3D as far as they could and then lost interest.
O.K. 0,5 Points for you
But I think that Sense is only for Andoid? Correct me if I'm doing wrong...
My problem is, that my Kaiser (and i think all others too) have not such a good touch screen accuracy... mine is terrible.
(yes, I cleaned out the frame and the edges...but on my bosses Kaiser the screen accuracy is also bad! - Compared to my - slow but accurate - P4350).
In my opinion the touchflo concept is one of the best solutions ever developed. But for me in person TF3D would be a nice looking (and little improved) upgrade. I'm already using M2D and I like it, but what I also like very much is for example the animated weather and the improved look and feel.
I have also tried 6.5 but with the terrible accuracy of my screen it is not so funny to use.. also it is not running such smooth as M2D and I in person think titanium is not everyones favourite choice. What i also do not like is the Honeycomb-Style... looks nice, but thats all.. O.k. the kinetic scrolling is good and thats one thing I like . But thats the only improvement I could see at WM6.5.
So whats your opinion: Is a rom with newest drivers and so on not for everydays use capable due to a lot of buggy functions? (I dont't know - I never used one ).
If I remember right, all the legendary cooks have tired TF3D and it doesnt work as it is supposed in Kaiser. Kaiser is just not made for TF3D. TF3D is more resource hungry, and our device just cant handle it.
I do believe there is a cab for TF3D available! Take a good lite 6.5 ROM with memory hack, and load it with TF3D, you will see if it will be able to handle it or not.
I had it working kinda decent with 6.5...just kept throwing drivers at it until i found a decent setup. But i was just wanting to see how it would be like you. When i get home i will look if i still have the file and send it to you. I cant even remember what all i had with it though lol. But like everyone has said its still slow with the newest drivers and such.
I cant find the file....but i will work on it this weekend.
Here is one that I had downloaded when the TF3D thread was alive. This does not have standby in it. So if you want to turn off your phone, then you need to find a stanby fix by somebody!
Hmm in my first post is another source for the TF3D, which has bigger files - there you'll find also the Audio Manager etc.
Has this thread died ?
Hello,
I am trying to find more information on Manila 3D or Touch Flo 3D and how it this is supposed to work on a phone.
I have installed at least two different types of .CABs and they are different and all all functions are available in both of them. My understanding is that these were ported by different people for their need I guess.
I am trying to do this on non-HTC phone with WVGA screen and I would like to start out with basics on how TF3D is suppose to work and list of requirements of both hardware and software.
I have searched every where and all I am not able to get to the big picture.
Any help is appreciated and many thanks in advance.
I dont know much about Touchflo and how it works, but I am pretty sure that it requires a special touch.dll that is only in newer HTC phones
cmstackar said:
I dont know much about Touchflo and how it works, but I am pretty sure that it requires a special touch.dll that is only in newer HTC phones
Click to expand...
Click to collapse
Thank you for the reply.
I have tested 2 different versions and both of them are working smoothly.
However, some of the functions work in one version and vise verse. Camera, Audio manager.....etc did not work in both versions!!!
That is why I was asking for some help on what TF3D is suppose to do since I never owned a HTC device that has TF3D.
I am hoping some one had it documented in some post. I just can not seem to find it!!!