We already have a ROOT, so maybe think about the new video drivers for WF? current drivers cause errors in texture and are terribly slow.
I tried to move the drivers from other devices, but they caused the system to stop the HTC logo. Unfortunately, Android is not my forte.
Devices with the same processor at the WM, cope better with 3d graphics.It seems that this is only the problem of 3D drivers.
Related
I have been scouring through the different Kaiser,Polaris and Diamond threads that concern driver issues that we would all want solved. What i have found is that all 3 of these phones use similar driver .dlls and if HTC drops a driver for one of those 3 phones....will somebody be able to render the drivers to work for the other 2 phones that the driver didnt come out for? Like if the diamonds drivers are droped, will Polaris and Kaiser individuals be able to use the same driver to help there video playback? Seems highly unlikely for HTC to drop individual drivers for all 3 top level HTC phones but maybe a universal QUalcomm MS7200 chipset driver for these phones would come out. If not, would somebody be able to make a Polaris driver work for the Diamond or Kaiser? the phones may have different .dlls or D3D or Open GL registrys if its a MS7500 or even similar MS7200 chipset. If you guys havent seen this postt check it out plz
http://forum.xda-developers.com/show...postcount=1004
Hi,
check this site, seems Diamond had the same video issues with previous model of HTC.
http://www.wmexperts.com/articles/video_driver_issues_still_htc.html
thats because there are no hardware drivers. everyone was fooled because opengl es and d3dm were running, but what they dont realize is that the opengl is only a software renderer using the CPU. why do you think d3dm is just a wrapper around opengl? if there were real hardware drivers then directdraw would have been pretty fast at drawing,and d3dm wouldnt have needed a wrapper.
check out my post from a few days ago
http://forum.xda-developers.com/showthread.php?t=452983
As far as I know, the attempts at making OpenGL ES drivers for the TyTN II have been discontinued. But why did the developers decide to abandon the project?
Did the developers of the drivers ever release the source of their work for any other developers to pick up and continue where the first developers left off?
Has it ever been confirmed that the hardware actually does/doesn't exist and is/isn't wired in such a way that a driver can be used to add OpenGL ES support? I mean, even if the chip exists and is accessible by the OS, it doesn't have to mean that the chip is connected to the display of the device in such a way that you can utilize its features.
If so, it's be pretty much like having a computer with a powerful video card, but without the monitor connected to the card.. Instead the monitor is connected to a poor performance card in the same computer, making it possible to use the powerful card to generate "screenshots" which are then simply displayed through the poor performance card, but still without achieving the same performance as you would if the monitor had been connected directly to the powerful video card.
Can someone update me a bit on the progress, or perhaps direct me to the right place to read more? I used to closely watch the htcclassaction.org website, but now that website seems to be dead, without any info about why the development just stopped.
I know that this device is getting old and pretty much belongs to the history books now, but now that android is being ported for the TyTN II, the device may have a new chance of seeing daylight again. Perhaps someone is willing to take a look at the driver issue again and make some TyTN II video driver for android? I certainly hope that the development didn't stop because it was simply impossible to make a driver. After all, you cannot write a driver for hardware that doesn't exist.
Thanks.
yeah, up for this, and is there any driver that will install on the default wm 6.1? thanks for the upcoming reply people
I don't think it's a matter of history yet. The newer devices that have physical keyboards have the same chipset and, therefore, same performance issues they TyTN II has. That extra 124mhz the Touch Pro/2 have aren't doing much to remedy the problem.
Excuse me, what's the currently true problem ?
Some OpenGL ES applications don't runs ? ( an example ? ) or they runs too slowly ? ( an example ? ).
In my "beta" configuration everything seems to work decently.
Regards,
Stefano G.
I think some people were working on it most recently under the development and hacking thread...search Neos2007 open vg drivers...They managed to get some accelleration in much newer msm7201A devices with the ati d3d drivers but when I tried it on my tilt it had a device exception error when I ran some d3d samples...What worked for me for now was:
1. Disable manila/chome
then
2. intall Gfxboost 1.1 by chainfire
then
3. install neos2007 driverpack 2A
then
4. install HTC-CA drivers
By following the procedure above I was able to actually run the program GL benchmark and most of the d3d samples (except text) but somehow some d3d samples break the drivers too...
I have tried some Kaiser " SuperRam - 101/102 MB " roms,
nobody was completely compatible with HTC-CA drivers.
With my rom ( no SuperRAm ) I obtain the best result replacing
the DLL "ahi2dati.dll" with a renamed copy of "ahi2dati_dm.dll".
Regards.
I have bought a sony vaio vgn-fw11m laptop, and there is windows vista home premium x32 installed. Iwanted to install vista ultimate x64 on it but couldnt find some of the drivers for it. does anyone know where i can find them. cause im realy tired of x32 system, it works very slow and it doesnt fully use the sytem of the laptop for example i have 4gb ram but the x32 OS
can operate only 3gb... any ideas where i can find x 64 drivers?
now that would very much depend on what the drivers where for
Mazahaka999 said:
I have bought a sony vaio vgn-fw11m laptop, and there is windows vista home premium x32 installed. Iwanted to install vista ultimate x64 on it but couldnt find some of the drivers for it. does anyone know where i can find them. cause im realy tired of x32 system, it works very slow and it doesnt fully use the sytem of the laptop for example i have 4gb ram but the x32 OS
can operate only 3gb... any ideas where i can find x 64 drivers?
Click to expand...
Click to collapse
I have the Sony VGN-CR240E, and I installed Windows 7 RC1 x64, since I wanted to see if I should buy that instead, and I can safely say that most things work flawlessly. The downloads page for your model should have all the drivers, and most other software like Webcam and specific control panel settings.
One thing to keep in mind is that some stuff takes more work to get working right, and sometimes it won't work at all. For example, even though I'm running the Windows recommended driver for my built Texas Instruments card reader, it still doesn't work, and I can't find any OEM x64 drivers. And there is a row of buttons such as Volume up/down/mute, webcam, and dim display, but Windows uses its own driver for that, so only volume controls completely work as intended.
So, rather than deleting one version of Vista and installing the other right away, I'd shrink the existing vista partition using Disk Mangement from the Management Console, then create a new partition on which to install Vista x64, then install on that, and make sure most stuff works. That way, you don't have to stick with the x64 version.a
Now, once you install x64, download all the drivers for your computer from the Sony support site for your compter, but only download it for hardware that isn't working fully, even though Windows recogizes it (such as the webcam and mic in my case). Then, use a tool like Universal Extractor or 7zip to extract the .exe files you downloaded into the same folder, and call that folder Drivers or something similar. Then, from Device Manager, you can install drivers for that piece of unrecognized or non-functional hardware by choosing a specific location on your computer to search, and include the folder you made earlier called Drivers, and if there is a 64 bit driver in the original installer that is compatible, it should install and work as normal, though sometimes using the original .exe file is the only way to install it correctly (as in the case of my webcam), and sometimes, it won't work at all, as in the case of my card reader. Hope that helps you.
Ive already tried visiting sony support6 and vaio support, there were only the originally installed drivers an utilities, and when i tried tried to install the card reader driver itworked, but the webcam and the WMP control panel werent working. also while installin one of the drivers the blue screen appeared. after some time imjust used the recovery to roll back to x32 home premium. any other ideas?
Hello all!
So I've been using Mac for the last years and really enjoying it, but now wanted to use Linux (more specifically Fedora) as my main OS, rather than MacOS.
The machine for doing so it's a late 2013 15" MacbookPro with NVIDIA graphics.
For getting everything setup it took a while as a lot of drivers are proprietary, but manage to get most things working (expect for sleep, that for an unknown reason is broken and the Mac takes more than 5 min to wake from sleep, and FaceTime camera not working).
The problem however is that the machine is using the NVIDIA GPU, which causes it to get very toasty and drain battery faster.
I would like to enable the iGPU, but keep the NVIDIA GPU available as sometimes I connect an external monitor using the HDMI port.
I am newbie to Linux and have little knowledge but want to try everything possible to make Fedora work as best as possible on my computer. The procedures I tried were:
-Install rEFIND and try to use an set_apple.efi thing but probably did it wrong and did not work,
-Try to modify NVRAM variables to make the mac use the iGPU by default, but when booting to Fedora still only show up the NVIDIA GPU
Any help is welcome, bur please don't say for me to stay on MacOS or that is impossible as I read from people who manage to succored.
Thanks in advance!