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.
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
I thought that well.
Our shift uses an internal cellphone kind of thing... that uses a Quallcom 400Mhz processor... could it be possible, that a rom for TyTN II for example, be cooked and make our shifts hidden parts work ?
The parts used for the gps antenna etc etc... in which other device are they used ?
Or perhaps the bluetooth chip...
anyone knows ...?
vulcan_gr said:
I thought that well.
Our shift uses an internal cellphone kind of thing... that uses a Quallcom 400Mhz processor... could it be possible, that a rom for TyTN II for example, be cooked and make our shifts hidden parts work ?
The parts used for the gps antenna etc etc... in which other device are they used ?
Or perhaps the bluetooth chip...
anyone knows ...?
Click to expand...
Click to collapse
Well, it is possible in theory, but the issue is BT, WiFi, Voice (WaveDev) etc. are locked by Vista side of the world. On the other hand Vista uses WinMo as a modem to connect to internet and fetch GPS. I may be wrong too.
thanks
Ram
This doesnt fall into any category of phone, but I think with some tweaking, we can really utilize this deck to its full potential. The Pioneer AVIC series Navigation/DVD/Car Radios are Windows CE Based, and there has been a mod to boot it directly into windows CE. The potential is AMAZING to combine the units with our smartphones. PM me if you are interested, and or have the knowledge to take this to the next level. Go to AVIC411.com to see what has been done so far. Really, not much besides some minor mods, but I could see this unit becoming a complete smartphone interphase, etc... I currently have a touch pro, and have ordered the AV adapter. I am working on a launcher to keep it in the shell, and give it the ability to use the phone as a modem, to then have dash board internet, and outlook. the possibilities are limitless!
I have the same setup, surprised no one has really taken this any further yet. I agree with you the potential here could be pretty sweet!
Was wondering if you had anyluck with teathering your touch pro to the pioneer avic headunit?
Avic...
No, I have not, but I did get the video adapter on ebay, so I am pumping video thru the AV1 source...
I really have not had a ton of time to do alot, but there is a bunch of stuff on AVIC411.com...
Let me know if you find or are able to do anything cool. (like getting the bt to work consistantly!!!)
CHARLIE
Interested
I'm definately interested. Just got a avic-900bt and would love to code some bolt on functions & camera input mods & maybe even get some extra devices interfaces working better.
I'm guessing we'd never be so lucky as to get source for the 2.0 update. Do you know if there is an avic emulator available? Where to start?
Details on setting up AVIC emulator here: http://avic411.com/forum/viewtopic.php?t=18137&postdays=0&postorder=asc&start=8
Has anyone done research, mods or other to get internet and/or full phone screen output to show up on the AVIC's???
I have two avic900bt's & a Sprint TP2...
I'd love to have weather, current location radar and everything else to display while driving.
The ultimate "coolness" would be able to control the phone through the AVIC's display!
Off to do some more dreamin'...
Raymond
Avic
I too have a sprint tp2 and an avic f90bt with the 3.0 firmware upgrade. I do know that it is Windows CE, and there is a lot that could be done, I just dont know exactly how to do it
I have purchased a video out from ebay for the tp2, and am able to use the video 1 input on the avic, but it is not near what it could be. There are so many other things like interactive mapping, weather etc...
Can you activesync with it?
If you just want to remotely display the screen of another Windows CE device (the Pocket PC) on another one (the Avic) just use a program like NetOp (http://www.netop.com/) installed on each device. You can probably create a PAN connection between the 2 devices using bluetooth to get a network connection. And you probably won't need Activesync if you just download the cab versions and install them.
maybe have someone intresse to help me with the radar detector system modify on a pioneer AVIC-HD1bt
see
on this forum off-topic > [Q] radar update for Pioneer AVIC-HD1bt almost there
Hey everyone,
I had a question oncerning the Kaiser's video drivers. I know there are numerous drivers floating around that have been working great. I was curious if PDA phone operate like computers when it comes to having differennt drivers for the monitor and the video card or are they basicaly all wrapped into one driver. I was curious if any portion of these drivers controls the refresh rates of the screen for the kaiser device. Hopefully this question makes sense.
Thread moved. Not related to ROM development.
Thanks
Dave
Hey Guys
First of all: I realize that this is a rather long text, so I appreciate the effort of everyone who is going to read it!
Also, I asked a questions about 2 weeks ago, which was related to this topic, but was very specific about android wear (which I gave up on since then!).
So, actual post:
I want to build, or already am building an informational system for my motorcycle.
As the result of my work, I imagine a display (about 7 inches) in the dash of my motorcycle. It shall display information from my Smartphone (for example notifications about incoming calls etc.) as well as giving me the possibility to control the music on the smartphone (Android 5.1).
Also, I want to display further information, like speed, average speed, altitude etc. (hope you got the idea, basically just an advanced trip computer).
I started developing something, but ran into issues. I will explain my two concepts or ideas I had so far and explain, what the issues were I ran into. I then hope, that somebody here has a solution for my problem (which includes recommending hard- and software).
Firstly about my skills: I am experienced in programming "low level hardware", like Atmel's AVR Series (in plain old C) and developing the associated hardware for it. Also making custom pcb's at home isn't a problem for me, as long it doesn't come to some fancy BGA or SMD packages
On the programming side I am experienced the most in Java (and Android, which is basically Java of course). I know also C# and the .NET framework.
But I am willing to learn something new
The two ideas I had so far differed on the way how I wanted to let the raspberry pi (which I wanted to place in the cockpit) communicate with the smartphone.
In both concepts, I planned to have a raspberry pi with attached display in the cockpit on which I wanted to run a JavaFX application (already started programing). This application would then communicate with the smartphone over:
Idea 1: Java serialization:
I wanted to communicate over command objects. So for example I'd have an object for asking the altitude from the smartphone.
I'd then serialize this command object on the pi's side and deserialize on the smartphone. This isn't a problem, because there's java on either side (already got that piece working).
The smartphone would, after receiving and deserializing the object, get the actual altitude from the GPS sensor, pack the result in an answer-object, serialize it and send it back to the pi.
The issues I ran into were the following:
-Java Bluetooth library: I wasn't able to find a good, up-to-date, java library for communicate over Bluetooth in java. I then stuck to RXTX Library which did the job, but I always had the feeling of doing something "not so good". In particular I didn't want to just write on a COM-Port (which is emulated from the Bluetooth-module), because I had the feeling that COM-Ports may change after reboots if the OS feels like it, and I didn't want to build something which needed constant "tinkering". Also, writing to COM-Ports in 2015 just feels wrong, but this may be my personal problem
Idea 2: HTTP and Web Sockets
The basic idea was to have a webserver running on the smartphone and offering a REST-like API which I could access from the pi.
I also got this concept working, like so:
By using the NanoHTTPD library (from github) I was able to start a webserver on the android device. When then someone issued a POST-request on, for example, <IP>:<port>/api/music/next, the WebServer would receive this request and switch to the next song.
Actualizing data on the pi which changes often, for example the altitude, would have been achieved by using a WebSocket connection between the Java-App on the pi and the android webserver (which I also got to work).
I figured out that it would be a power consumption problem to let the smartphone offer a wifi hotspot (I don't want to have to connect the smartphone to cables on the motorcycle), so I decided to let the pi start a wifi access point (which isn't a power problem, because the pi is connected to on-board-power of the motorcycle).
However I then realized that the smartphone won't connect to an access point which doesn't offer internet access but only LAN-access.
And even if there was a way to force the smartphone to let it connect anyways, it isn't guaranteed that this will work too on future devices. And: The whole notification-stuff would have been needless, because as long as the smartphone is connected to a "dead-end wifi", it wouldn't receive emails or whatsapp-messages.
Idea 3: Using Bluetooth low energy:
It seems like the new, modern way, to let devices communicate over Bluetooth is to use Bluetooth low energy (BLE). (But I never worked with it before!).
However, there seems to be little to no support on raspberry pi for it, and it seems to be impossible to find a library for java which helps in using BLE. (If anyone knows one, please let me know).
I then thought about replacing the raspberry pi with an android board, because android has support for BLE. But I wasn't able to find a board which is supported from android 5.1+ and offers support for BLE. Even the Odroid-boards don't seem to support android >4.4 and BLE.
Summary:
In general I liked the second and third option much better. It seemed to be the the more versatile, modern way. The first way felt a bit like a hack.
However I found those problems I presented above, and until now, I couldn't think of a way around it.
If anyone here:
1) Solved this problem already
2) Knows a really good, NON-HACKY, community supported, Java (BLE) Bluetooth library
3) Knows a language or framework which would be well suited to solve the problem
4) Has another good idea how to solve it
Please let me know!
I just want to build something sophisticated, (which I could maybe make an open source project out of it) which isn't hacky.
I mean, the problem has to be solvable, look at the Pebble smartwatch. They also solved it without android wear.
I really want to emphasise that this is an open question. I am not limited / fixed on Java, Raspberry pi or anything.
I those have two requirements.
1) I don't want to connect the smartphone to a cable, either for data or for power
2) The solution needs to be something power saving, so no hotspot on the android device
3) Non-hacky, sophisticated solution
Best regards
Me =)
PS: As English isn't my native language, I maybe put some sentences wrong or wasn't able to express something clearly and unambiguous.
Please feel free to ask, I'd be pleased to clear any questions!
Any updates?
Hi!
I know this is an old thread, but I'm struggling with a similar issue - except I want to use it for roadcycling. Did you have any luck with your project?
All the best
Marius