*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, Myself, NikMel or any of the posters of software, or links to software on this thread take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
-----------------------------------------------------------------------------------------------------------------------------------------------
Project Name: Polaris Project P3D
CAB Name: HTC-CA-Polaris-Drivers
Development and Testing Team: Bally3, NikMel, Neos2007, NuShrike, Rogro82
Bally3 - Development, testing and updates
NikMel - Development, ROM updates and testing
Neos2007 - Development, CAB updates, videos and testing
NuShrike - Development and code optimisation
Rogro82 - Development, code optimisation and testing
JesseW - Design & testng
11/10 - With the release of the 2D driver and also a rom dump of the long-awaited Toshiba G810 rom - We are temporarily suspending further development and discussion of the 3D driver whilst we pursue our other ambition of bringng better 2D capabilities to our devices.
Please see the Poilaris 2D Driver development thread here:
http://forum.xda-developers.com/showthread.php?t=435190
Thank you - we will continue the 3D driver improvement discussions shortly.
-----------------------------------------------------------------------------------------------------------------------------------------------
8/10 - Today, The P3D team are proud to announce the release of the P3D Polaris 3D driver in an installable (and uninstallable!) cab form through its partnership with the htcclassaction.org website. Our thanks to Chainfire and the Kaiser team for the creation and distribution of the cab file via its website and enabling the p3D team to concentrate on further development and improvement to the driver.
We wish them all the best
The link to the cab can be found on this page: http://www.htcclassaction.org/driverprogress.php#update_20081009_1
-----------------------------------------------------------------------------------------------------------------------------------------------
2/10 - Distributed new set of drivers that are compatible with the Polaris ddi to all rom chefs to test and integrate into their roms.
-----------------------------------------------------------------------------------------------------------------------------------------------
30/9 - Initial feedback from Itje's rom is encouraging - users express faster speeds with a few exceptions. NuShrike has success making the original Polaris ddi,dll work with the 3D driver - tested and confirmed working with improved results.
-----------------------------------------------------------------------------------------------------------------------------------------------
28/9 - Asked rom chefs to assist with testing with their own roms with the drivers cooked in - ije released a new version with 3D drivers.
-----------------------------------------------------------------------------------------------------------------------------------------------
27/9 - Testing continues with some impressive benchmarks from NikMels rom which has the files cooked in.
-----------------------------------------------------------------------------------------------------------------------------------------------
26/9 - Group set up for development team: http://forum.xda-developers.com/group.php?groupid=18
-----------------------------------------------------------------------------------------------------------------------------------------------
25/9 - NuShrike and Rogro82, our developers on this project had a breakthorough to fix the scrolling. Neos2007 created a cab which will be posted out to all testers on this project.
An updated video from Neos2007 of the non scrolling 3D acceleration can be seen here: http://www.youtube.com/watch?v=58PFxhIVeE0
A Cab file has been generated by Neos2007 for testing FOR the team - we will release a Public Beta after some testing.
PLEASE DO NOT POST REQUESTS FOR THE CAB!
------------------------------------------------------------------------------------------------------------------------------------------------
23/9 - After trying every angle to fix the scrolling we are now looking at help from NuShrike, a veteran from the CA Kaiser driver who has agreed to help us in porting the CA driver to the Polaris.
-------------------------------------------------------------------------------------------------------------------------------------------------
UPDATE: After much research and some interesting development work, NikMel has posted a rom which shows hardware acceleration working in concept! - you can see a few youtube videos here:
Neos2007: http://nl.youtube.com/watch?v=69_6zgIZLaU
SuperJMN: http://www.youtube.com/watch?v=0RMYnI23JB4
What you ask IS what we all want to know. Why the Kaiser, but not Polaris?
Is it capable to do it? It is not? Is is a matter of time?
Putting my thoughts to graphical paper here. it might help someone or it might not.
So when I enquired about whether the 3D driver for the Kaiser from htcClassAction.org would work on the Polaris, the answer was a resounding NO!..
Apparently the Polaris was missing a potential ddi.dll file that was rumoured to be included in WM 6.1.
UDK's Syrius R0 looked promising but the bugs forced me to look elsewhere so I flashed swtos new rom which claims to include the ddi.dll and have "3D Support", though swtos also mentions that there is NO hardware accelerated driver available for the Polaris.
Swtos' Rom included the 3D tests which show the D3DM demo cube actually moving at about average 3.2 fps but the lights program still shows HARDWARE RASTERIZATION: false and "Using system memory".
Athough there are clear speed differences from my UDK R8 rom, video playback is slightly smoother, overall rom speed after installing all programs faster its clear that apart from some tweaking and the ddi.dll file (or tweaking BY the ddi.dll file) this is only software acceleration.
So the question is:
IS THE POLARIS CAPABLE OF HARDWARE ACCELERATED 3D?
From my limited understanding of this, the only way to verify that the Polaris is running on hardware accelerated 3D mode is that the lights test should say "Using Video Memory".
I tried installing the kaiser 3D driver in the hope that now I have the ddi.dll file this may work. no such luck - exception errors etc..
So started looking at the dll files mentioned in the lights program and googled the file named on the first screen which was d3dmref.dll. I found this interesting article at Microsoft:
Failed on Direct3D mobile Test in Test Tools
Apparently d3dmref is a Microsoft D3D reference driver (not hardware accelerated)
(Continued)
------------------------------------------------------------------------------------------------------------------------------------------
Some questions then:
drdmref.dll is a referenced driver. So what is ddi.dll and what does it do specifically?
The ddi.dll performs better than the Samsung Omnio driver which in itself proved to show much improvement than before - why?
If we now have the required ddi.dll, what else needs to be done to make the HtcClassAction Kaiser 3D drivers work with the Polaris?
What other files are we missing?
Time for a break.. and hopefully someone might be kind enough to provide some answers.
SuperJMN said:
What you ask IS what we all want to know. Why the Kaiser, but not Polaris?
Is it capable to do it? It is not? Is is a matter of time?
Click to expand...
Click to collapse
Sure it is.. and here's hoping somehow we get an answer from someone.
Swtos, UDK, these guys must know a little though the actual 3D bit seems to be a carrot dangled to get everyone excited over individuals forthcoming roms.
udk does not directly answer the 3D question, swtos in his defense, has been blunt about the fact that HARDWARE acceleration doesnt exist in his rom which is fairplay.
bally3 said:
.....
So the question is:
IS THE POLARIS CAPABLE OF HARDWARE ACCELERATED 3D?
...
Click to expand...
Click to collapse
the think is, if the chipset have hardware alleleration, so the polaris have hardware acceleration. we just need the software to unlock it. a time ago i read something about the qualcomm chip and there where standing that the chip have hardware acceleration. i dont think that htc has made a new chip for the polaris so it dont have hardware acceleration. they just used the chip how it was.
Which would mean it should be capable and we should try to ascertain which, if any files are missing from the Polaris as opposed to the almost identically specced Kaiser which has now seen true hardware acceleration.
Of course it might be some simple tweaking to the registry or the dll files to make the classaction drivers working.
I Found this thread in these forums. Look at the last post:
Can anyone run the D3d Mobile samples?
"i,ve had kinda the same problem trying to get some of the samples to run on my trinity, try changing d3dmpp.AutoDepthStencilFormat = D3DMFMT_D24S8;
Dont know if its the same problem but it helped me out."
Anyone care to venture a thought?
This is an interesting article:
microsoft.public.win32.programmer.directx.graphics
might be old news, might be new but this Don Crouch guy seems to know his stuff. Of interest is this line:
"Any device manufacturer should be spanked for shipping this driver as it was only designed for generating golden images to test drivers against. MS prohibits it from being shipped on any device."
This is in reference to the d3dmref.dll which IS present in the Polaris!
Been reading the Kaiser thread to see if I could better understand the issue:
D3D or OpenGL ES hardware acceleration for Qualcomm MSM7200
Reading the last posts we now also have to consider another question if there is a heat issue and HTC were aware of it:
SHOULD we try to hardware accelerate the Polaris???
bally3 said:
Been reading the Kaiser thread to see if I could better understand the issue:
D3D or OpenGL ES hardware acceleration for Qualcomm MSM7200
Reading the last posts we now also have to consider another question if there is a heat issue and HTC were aware of it:
SHOULD we try to hardware accelerate the Polaris???
Click to expand...
Click to collapse
good point. i mean, does anyone have real problems because he dont have the drivers? tomtom could be a little more faster but it works. last time i drove over 350miles and was using tomtom all the time and the device got really hot. so if its true i dont think i will use the drivers....
another question....does the kaiser really have 3d drivers ? i dont read the hole story.
OK, putting the "should we" question aside I've been doing some more delving into why the HtcClassAction.org kaiser driver doesnt work out of the box (mainly cos we all would still like to see the Polaris doing hardware accelerated 3D - and who could blame us?
So heres what I've found out so far:
1. Kaiser driver is compatible with roms which include a ddi.dll file version 3.28 and up - someone mentioned 3.55(my file version in the swtos rom shows 3.13.0.0?)
2. We might be missing some required dll's (anyone fancy doing some digging here plz?)
... I'll investigate further!
thanks bally3 for those news...
ouioui01 said:
thanks bally3 for those news...
Click to expand...
Click to collapse
You're right welcome!
It seems this is the missing link, the wm6.1 that htc officially releases must have a ddi.dll file of 3.28 or above built into it, but I dont know what tweaks are meant to be involved to make a difference.
I'm currently looking for a ddi.dll ver 3.28 as mine is in the Windows directory so I'm assuming its not going to blow up if I try it! (might mean yet another HARD RESET - but it would only be my 10-11th reset since udk's R0 release! - and I always have my current swtos rom on my card ready to flash back if it doesnt boot).
Anyone find this file might want to post it - or brave enough to try it?
Reading this thread in the Kaiser forum, whilst looking for the illusive dll and its dependencies, I came across this thread which contains a ddi.dll file that I do have as a cab on my ppc and was wondering what it would do:
Tutorial - FIX The ClearType in Landscape
It mentions that any ddi.dll file under 3,28 must be a wm6.0 ddi file.
Seeing that mine happens to be 3.1 in swtos new rom which does seem to show some hardware improvements, am I looking in the wrong place or was the 6.1 rom built with a 6.0 dll simply with some jigger-pokery (sorry my technical expression!) to make it work better?
Will the OFFICIAL WM 6.1 come with the required ddi.dll file?
I think I'll quit my hunt for the dll file for the time being and look for more info on the official WM6.1, which is rumoured for release some time in the very near future...
I just want to share my tests
This test is made by Spb Benchmark
I don't think that there is a test like this high.
Who did these tests? and were they done on the current 6.0 release?
These are my test on my polaris wm 6.1 with the latest drivers from o2.
I can share this rom but there is a BIG problem camer is not working and video call too.
I made this rom.
if you've installed the rom can you tell us what version the ddi.dll is then please?
..and thank you for contributing to this thread
NikMel said:
These are my test on my polaris wm 6.1 with the latest drivers from o2.
I can share this rom but there is a BIG problem camer is not working and video call too.
I made this rom.
Click to expand...
Click to collapse
It doesn't really matter!! All we wanna do is TESTING! Please, share that ROM to see if it has some clues for us to carry out research on possible improvements
SuperJMN said:
It doesn't really matter!! All we wanna do is TESTING! Please, share that ROM to see if it has some clues for us to carry out research on possible improvements
Click to expand...
Click to collapse
hmm.. maybe you're right but the ultimate question about hardware acceleration like the kaiser lies with the version of the ddi.dll. But yes, if the benchmarks are that good its worth testing it so please do share the rom with us, who knows, with different radios the video calling and problems may get fixed and will only help to improve the rom.
I made this test after installation of keiser video fix from htc....org
Uploading.....
Related
Hello,
I have just bought new coreplayer ver 1.1.0 and it is splendid and especially no artifact with my trinity with harware accelation and ati Driver keep on.
wouahhh !!!
Huge speed improvements...
http://www.corecodec.com/forums/index.php?topic=227.msg1175#msg1175
Where can i download the new version?
A link
Can you provide a RS link because I still have the old version and my only option would be to buy it again
TCPM 0.72 the best player i had !
Please remove that file, you are not allowed to redistribute it.
cosinusx said:
Try this...
Click to expand...
Click to collapse
If people post warez on this site - it risks being closed down.
I'm sure you'll agree that is not what we want.
This is a great bit of software - for $19.99 but it - if you use your Trinity for Video it's worth it. If you don't use your Trinity for video much - use TCPMP earlier version - very satisfactory.
So please, remove the file.
Not a warez, only download without cracks and serials. This is only installation form. If you have purchased previous version, you can install this one as upgrade, otherwise you must buy licence.
Sorry, this is still not allowed. CoreCodec let users get the file through Mobihand so if the user is asking for a copy, he must be using a pirated copy and you are helping him.
?
Not quite true
Cant find Ati settings
Solution: I uninstalled program and installed from scratch. I now have the ATI options. Thanks.
OLD question:
I just updated to 1.1.1 build 1600.
I have no Ati option under Preferences/Video. I only have Direct Draw/Raw/Disabled etc.
Where do I set Ati Imgeon to ON?
Hi guys,
I saw some forum topics about running succesfully running google's android on the kaiser and the vogue!
http://forum.xda-developers.com/showthread.php?t=383695 (Kaiser)
and
http://forum.xda-developers.com/showthread.php?t=382265 (Vogue)
The source for all those things is this page,
http://it029000.massey.ac.nz/vogue/
see here for an video on the kaiser...
http://echofloripa.blogspot.com/2008/04/android-in-kaiser-t-mobile-mda-vario.html
Do you think some linux experts are capable of running it on the hermes(tytn)?
I am not an expert on this, but i tried the Kaiser files on the hermes, but it didtn load the kernel right..
You dont have to flash your hermes for this, only running an exe on the hermes....!
TripleQ said:
I am not an expert on this, but i tried the Kaiser files on the hermes, but it didtn load the kernel right..
Click to expand...
Click to collapse
If you will compile the kernel for Hermes, you can probably start the android runtime.
this will be cool....
keep us informed
cr2 said:
If you will compile the kernel for Hermes, you can probably start the android runtime.
Click to expand...
Click to collapse
i'm a newbie in linux but i'll try to search about it. i think that in POF's web are a hermes linux kernel...
Yeah the idea off running android on the Hermes is very cool!
I dont have the knowledge to get this working...but the guys from the kaiser and the voguage(touch) forums where capable enough let it work..
Is anybody here smart enough for this?
ilion said:
i'm a newbie in linux but i'll try to search about it. i think that in POF's web are a hermes linux kernel...
Click to expand...
Click to collapse
Interesting...here's POF's Linux thread started in 2006 and still active!
http://forum.xda-developers.com/showthread.php?t=273579
Any news?
I have seen compiled versions of the kernel for the Kaiser and the Vogue, but if anyone has a compiled kernel for the Hermes I willl test it out (I have three at home )
And the wait continues . Now with the Android developer challange closing Im despirate to get Android on my Hermes before it finally dies after being dropped for the 200th time.
The major boos tint his will be when the memcard drivers are written - the Hermes is low on RAM as far as I understand, and thus has problems. Once everything can be run from the card, it will be pretty trivial for someone who know what they are doing to recompile the kernel.
Doesn't seem to be much recent progress though!
Seemingly I can't spell.
It doesn't look like it is going to be easy getting this working as the controller for the mem card on the Hermes is apparently causing some trouble!
Hi there,
nikc0069 said:
It doesn't look like it is going to be easy getting this working as the controller for the mem card on the Hermes is apparently causing some trouble!
Click to expand...
Click to collapse
That's not all!
There are some information that all the android stuff is compiled for ARMV5.
So no chance to drive the hermes with the packages provided.
HTC Kaiser also uses some newer instruction set.
If you got enough spare time, try to compile some of the android packages for ARMV4. That's what hermes is running.
Anyway, there's a lot work to get a suitable linux on hermes.
There had been some breaktrough on universal. Check that out!
Full debian EABI running on this platform!
It was console based first, but there had been a lot of development in the last few month and it has grown to a very useable linux
Hopefully there would be some usable linux on hermes platform too!
There's so much information so far...
...and it is similar to the openmoko stuff.
Maybe we should not waste the time to focus on android.
Regards,
scholbert
Any news?
I want Android for my Hermes
hmm
what?? hmm ... drools
I had just been browsing the web and thought I better keep an eye out for this ... looks awesome.
Looks like a lot of guys have been working to get Android on the TyTN II and just yesterday they were able to make/recieve calls. Im sure once a lot of the bugs are worked out, it can be ported over to the Hermes.
......mmm
Hi,
AdamNimrod said:
Looks like a lot of guys have been working to get Android on the TyTN II and just yesterday they were able to make/recieve calls. Im sure once a lot of the bugs are worked out, it can be ported over to the Hermes.
Click to expand...
Click to collapse
that's the theory so far.
TYTN II is equipped with a newer ARM11 with a V5 instruction set (MSM7500) for system OS. Android has been designed to run on these new processors.
Fantastic work had been done by those guys to make it run!!!
TyTN uses older instruction set... i wrote this before.
Anyway, if there'll be some mods in the source code it perhaps will do some day.
Another complex part is all that GUI stuff. There's nothing to be found about the ATI 2282, the hermes is using for graphics.
Due to this fact there's only a very simple framebuffer in the current linux port for hermes, no ATI specific code for the GUI.
Maybe some of the masterminds out there will solve this issue some day .
At least i'm very interested in some source code for the ATI Imageon 2282 !
Anyone???
scholbert
scholbert said:
Another complex part is all that GUI stuff. There's nothing to be found about the ATI 2282, the hermes is using for graphics.
Due to this fact there's only a very simple framebuffer in the current linux port for hermes, no ATI specific code for the GUI.
Maybe some of the masterminds out there will solve this issue some day .
At least i'm very interested in some source code for the ATI Imageon 2282 !
Anyone???
scholbert
Click to expand...
Click to collapse
http://www.umpcportal.com/products/product.php?id=55
if that is correct info athena has this same ati chip. And when I looked at the Athena/Android project, someone has allready made something with graphics. Look at this post:
http://forum.xda-developers.com/showthread.php?t=393389
it says graphics done!
Hope this helps in any way.
Hi sniveri,
thanks for the links.
...if that is correct info athena has this same ati chip. And when I looked at the Athena/Android project, someone has allready made something with graphics. Look at this post:
http://forum.xda-developers.com/showthread.php?t=393389
it says graphics done!
Click to expand...
Click to collapse
HTC Athena uses ATI W2284. Maybe this part is very similar to W2282 on hermes.
Anyway, if you have a look in the patch, they also use vsfb (very simple framebuffer) driver for graphics.
This is the same like hermes, maybe it's O.K. for testing.
There's not much ATI specific code inside.
Still would enjoy to have a look on some ATI imageon driver code
Regards,
scholbert
I have unpacked two initrd-images and tried to found out what those contains. First one that works on hermes has init-file that is straigth link to /bin/busybox. After starting busybox it continues to inittab script to set environment settings or so I think.
Second initrd-image, that is made for kaiser or vogue, has someway compiled init file or something that I can not edit with any program..? It would be nice to know what scripts or commands this file contains.
Wow，it is cool.
I hope some expert can make Android run on our phone.
[size=+1]Introduction:[/size]
I am proud to introduce "AndroidAthenaProject1.0" on behalf of the Athena Project Team! We have successfully ported Android to the Athena (More info about the Athena). This will be the official thread for optimizing and working out bugs related to Android on the Athena.
YouTube Demo
[size=+1]News:[/size]
05/28/2008 - New update available: (Athena-Android "All-n-1" Release) (More Info and even more info). This update adds touch screen support and screen rotation applet. Video driver still needs a lot of work. Screen updates are slow. Coding decent video drivers will be my next priority and if anyone is willing to give a hand, please let me know. Thanks!
[size=+1]Athena/Android Resources:[/size]
Download Android for the Athena (x7500/x7501/Ameo/etc...): Latest Release or Here (Click here for instructions)
Git: https://github.com/mistadman/android-athena/. This should be easier for us to manage changes. Enjoy!!
Diff and .Config (05282008): Download
[size=+1]Project Status:[/size]
Keyboard (not started) (A USB keyboard can be used for testing while we wait for drivers. See this post)
Touch screen (done):
More info
Testing/Bug fixes
Phone (not started)
Video(in progress):
Correctly implement pan_display() function (double buffering)
Speed improvements
Sound (in progress)
Wifi (not started)
Bluetooth (not started)
GPS (not started)
Camera (not started)
Sub-display (not started)
Accelerometer (not started)
Android Application Functionality(in progress):
RotateView Applet added: (More info)
This applet lets you rotate the screen. Unfortunately, due to incomplete video driver, video performance takes a serious hit during rotation.
[size=+1]Contribute:[/size]
If you would like to test or can contribute to one of the outstanding issues above, please let us know. Also, marthynovak has posted quick and dirty guide to testing our releases. See this post for more information.
-----
_--Reserved--_
This post has been reserved!
_--Reserved--_
This post has been reserved...
Here is small how to to start android on Athena.By mistadman
Download Android for Athena here(last build): http://rapidshare.com/files/118229739/Android-Athena-05282008.exe.html
free method(please use only when you cant you rapidshare) http://gymjs.net/~m.novak/Android-Athena-05282008.exe
Once downloaded, unzip and copy the unzipped files to a SD Card. The root of your SD Card should have these files:
haret.exe
default.txt
zImage
initrd-android
Once you have verified the files listed, insert the SD Card in to your Athena. From there just load up Windows Mobile and browse to your "Storage Card" in "File Explorer". Click on the file called "haret.exe", and once the program has loaded; click run.
Just remember that this is work in progress!
more info:
its only the system,the keybord is not working,screen isnt working.Just remember that this is work in progress!
Here is some plan what must we do(by mistadman):
1.) Add some Ati specific 3D acceleration (Double Buffering, Rotation).
2.) Optimize Power Saving...
3.) Add/repair touch screen driver.
4.) Add/create keyboard driver.
5.) Add sound
6.) Add phone driver support (be able to make a call).
7.) Add Wifi Driver.
8.) Get the camera working maybe?!?!
more also here:http://forum.xda-developers.com/showpost.php?p=2242471&postcount=19
_-Reserved-_
__-Reserved-__
--reserved--
__reserved__
-= Reserved =-
Keyboard?
As you can see on the post located here, they've written a simple onscreen keyboard. Maybe he'll give you the source for it and it wouldn't be hard to implement it into this kernel for future releases...
Let's pull all of our resources together and make this happen. Whoever can contribute let's post here and let's try to get a 1.0 final out ASAP.
Thanks in advance to everyone for helping where you can.
Areas of interest for developing the project:
- Graphics
- Sounds
- Drivers (highest priority of course)
- Apps
- Functionality (highest priority of course)
If you can provide a driver or something that fits in the categories above, please post a description...a how-to....and a link to a RapidShare download. Thank you all in advance.
Now we are talk'n! LOL!
- Graphics
- Sounds
- Drivers (highest priority of course)
- Apps
- Functionality (highest priority of course)
Click to expand...
Click to collapse
Just remember though, we do not want to duplicate Google's efforts... What I mean is that Google OS/Middleware (Android) will be in direct competition with the iPhone, Symbian, Window Mobile, etc. That means we can expect things like onscreen keyboards, SMS apps, Office Apps (probably complements of Google Docs/Google Gears), mapping/GPS software (Google Maps), a camera app, etc... (See: http://reviews.cnet.com/4520-9239_7-6546759-1.html for more info) And that’s not to mention some of the great work already being done by Third-Party Vendors (Android Developer Challenge: see: http://phandroid.com/2008/05/10/adc-round-1-winners for more info). Heck, look at what was done on the iPhone... And it was/is "closed source"!
I believe the IMPORTANT thing is that we provide a stable kernel for Google's "Middleware". I envision that most of the kernel work will revolve around driver development (in order of priority): (Here is a pictorial representation of the software stack:http://i.i.com.com/cnwk.1d/i/bto/20080521/android_stack_540x387.jpg, as you can see the kernel is the base to which all other software depends on.)
Keyboard
Touch screen
Phone
Video
Sound
And of course:
Wifi
Bluetooth
GPS
Camera
Long term objectives:
Sub-display
Accelerometer
Of course there will need to be work done on Android itself... Maybe we will need to develop applications custom to the Athena Hardware. At the very least, we will have to provide Android with a way to talk to hardware via kernel icotls (e.g. Camera Settings, Video Settings, etc…). So having some with inside knowledge of Android will help. Not sure though, because I haven’t hacked on Android (yet ;-) )...
Once the kernel/drivers are stable I believe Android will be a better fit for the Athena than WM6 could have ever be.
What do you guys think?
FYI: Looks like Google is already improving Android: http://www.talkandroid.com/99-adc-finalists-receive-android-sdk-snapshot-access/
i will have new develop version of Android soon.i hope so.so maybe it could be better for this project.i will let you know!
marthynovak said:
i will have new develop version of Android soon.i hope so.so maybe it could be better for this project.i will let you know!
Click to expand...
Click to collapse
Check your PM.
we should look here,there are plany of informations about android.its for vogue,but i think that something we can use.they said that touchscreen is working now
http://forum.xda-developers.com/showthread.php?t=382265
also see this.its on screen keybord included in the zimage.i cant try it right now,im away and my athena is not with me.
http://forum.xda-developers.com/showpost.php?p=2213637&postcount=303
also see this updates
http://it029000.massey.ac.nz/vogue/
http://forum.xda-developers.com/showpost.php?p=2191014&postcount=344
Update...
Just to let you guys know, I have been working on the touch screen driver. I pretty much have it working perfectly, expect for the fact that the touch screen works in the horizontal position even though Android boots vertically. I am pretty sure I will not be much longer before I release an update.
Also, if anyone is working on any particular issue related to porting Android to the Athena, please let us know. The more the merrier!
The main thing is that we wouldn't want to duplicated efforts or if someone is working on an issue we could match you up with someone doing the same thing. This would speed development a great deal. Two heads or better than one! On the main page I will post updates as to where we are with each issue.
And thanks to everyone who is either showing interest or encouragement!
Maybe you should give to each update a date.So they can know what is new and what is old.I tried to do someting with video driver,but no luck at all.ï can do more when i will be back home.
edit:we have(with mistadman) decided something about marking releases.he will tell everything to you.thx
All in one executable...
Hello everyone,
I am trying something new... Even though there has been some progress with this project, I am re-releasing the original Android release as an All-in-one executable for testing. If all goes well, we will be releasing further updates in this fashion. If you are testing, please post feedback on this thread.
This will help make testing easier, because there will be less files to mess with, and anyone new to testing will not be easily confused. Also the "All-n-1" release will be dated, which should also minimize confusion.
If anyone has any suggestions, or any better ideas, let us know. Thanks!
Here is a the link to the "All-n-1" re-release: http://rapidshare.com/files/117520672/Android-Athena-05172008.exe.html
***NOTE*** There is nothing new with this release, other than the fact its all merged in to one file for easier testing.
New Update...
Hello everyone... I'm back with a new update! I finally got the touch screen working! Still have a lot of work left of course.
If you want to play with it, you can get it here: http://rapidshare.com/files/118229739/Android-Athena-05282008.exe.html. This is an "All-n-1 Release". Just copy the exe to your sd card and run. After clicking, it could take up to 20 seconds to boot. Be patent!
As always, this is work in progress... Thanks for testing!
Here is the patch and .config:
thanks very much it's working fine and waiting for keyborad and wifi
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, Team P3D or any of the posters of software, or links to software on this thread take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Project Name: Polaris 2D Driver Project
Driver Name: P3D 2D Driver (Working title)
Development and Testing Team: SEE Post #2
---------------------------------------------------------------------------------------------------------------------------------------------------------------
ANNOUNCEMENT:
The P3D team would like to extend an OPEN INVITATION to all developers and programmers from all forums of EVERY device to come forward and help us create the 2D driver which, as it is being developed from scratch will require much development work with many dll files created from scratch.
If you are interested in helping, please post your interest in this forum and we will add your name to the developers list. If you would like to help but own a different device to which the 3D driver is yet to be ported to, we would also like to hear from you and hopefully assist you with the knowledge we have gained in return for your efforts here. (actually we'll help you anyway but.. we do want your help! )
---------------------------------------------------------------------------------------------------------------------------------------------------------------
11/10 - BigKVak successfully dumped the G810 rom and work has started in analyzing its content
---------------------------------------------------------------------------------------------------------------------------------------------------------------
P3D 2D Driver Development Team:
Administration/Testing:
Support and Testing:
Bally3
NikMel
Neos2007
BigKvak
Imfloflo
Developers: (TBC)
Rogro82
NuShrike
Chainfire
Monkeyass
maqui01
It started with a few simple questions:
"Can the Polaris be hardware accelerated?"
"Why doesnt the CA Kaiser 3D driver work on the Polaris?"
That was a month ago..since then, thanks to the help and support of NikMel, NeoS2007, Rogro82 and NuShrike to name a few, we now have a working 3D driver which is currently in a version 1 state and with the release of the cab version through CA last night, we can now concentrate on improving speed and compatibility to make better use of the graphic chips capabilities.
My intention then was never to start a 2D driver or work on a 2D driver until I was satisfied no more could be done to improve it and a "final" release was in the cards, but through my own testing and various posts and conversations, I now find myself wondering whether the improvements with 3D is linked to the 2D driver?
From day 1, before we released the 3d driver and after, users have expressed faster speeds in 2d as well as 3d - though many have explained it to be a "placebo" effect, we naturally attributed this to the gpu sharing the workload with the cpu which makes sense in a common sense way - itje posted a humorous answer on his thread explaining this very thing as worth a read just to put a smile on your face, but on a serious note a question has to be asked - Does improvement on 3D really effect 2D and if that is the case, would a 2D driver help improve the 3D drivers perfornance?
So why start a 2D thread when the 3D driver still needs refining?
Well, apart from the question above, the overwhelming requests for 2D support on both Polaris and Kaiser forums (it should work on both in theory), we now have a dump of the long awaited Toshiba G810 rom to get us started- A BIG THANK YOU TO BIGKVAK - welcome to the team!
Originally Posted by BigKvak
I have dumped ROM from Toshiba, here the link http://rapidshare.com/files/152085600/dump.rar.html
Click to expand...
Click to collapse
It is inevitable then that work needs to start on this project. We also need to preserve the 3D thread for future 3D driver developments and defer 2D driver related posts from it, for these reasons, this new thread has been opened for all to start working with the P3D team in bringing 2D greatness to our devices.
Lets share our knowledge and have fun doing it like we did with the 3D driver!
PS: Although I have named the project Polaris 3D driver project, I would like to extend an invitation to users of all devices that could benefit from the 2D drivers creation, after all through CA Kaiser development, we have now ported the 3D driver to the Polaris AND the NIKE and hopefully to many more devices
Let our devices not make us divisive - whats is the point?
It is common knowledge that files from newer devices are used to help create the drivers we need for our devices - so why should we gloat and mock other less supported devices, should we not help them and share our knowledge and in the words of a good friend here "Pay it Forward?"
This is not the spirit of XDA Developers and it is certainly not the ethos of Team P3D - We have and pledge tol share all knowledge with users of all devices.
Besides, its so much more fun when we all work together!
It appears that HTC-CA were already in the process of
Reserved for p3d 4
Reserved for p3d 5
Reserved for p3d 6
Reserved for p3d 7
Reserved for p3d 8
Reserved for p3d 9
Reserved for p3d 10
I found this link on microsoft MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1214862&SiteID=1
It's a guy asking for a 2d driver library. Maybe we can look into that?
I have dumped ROM from Toshiba, here the link http://rapidshare.com/files/152085600/dump.rar.html
Click to expand...
Click to collapse
To move the discussion of 2d in here..
Windows Mobile 2D and 3D explained on MSDN
I believe this: http://msdn.microsoft.com/en-us/library/aa911096.aspx will be out first place to look. It's mostly there: 2D AND 3D info.
Here's what functions there are:
AlphaBlend API
Provides information about adding support for the AlphaBlend function to your OS design.
Direct3D Mobile
Provide information about adding 3-D graphics support to your OS design and creating applications that use the API.
DirectDraw
Provide information about adding 2-D graphics support to your OS design and creating applications that use the API.
Gradient Fill Support
Provides information about adding support for the GradientFill function to your OS design.
Imaging
Provide information about adding support for compressed still images to your OS design and reference information for the API.
Multiple Screens
Provide information about adding support for multiple displays to your OS design and creating applications to support them.
NeoS2007 said:
I believe this: http://msdn.microsoft.com/en-us/library/aa911096.aspx will be out first place to look. It's mostly there: 2D AND 3D info.
Click to expand...
Click to collapse
reading it now.. some of it we know.. let see what we can learn..
http://msdn.microsoft.com/en-us/library/aa925824.aspx
Here we go:
"Applications direct output to a specified device by creating a device context for the device. The device context is a GDI-managed structure containing information about the device. An application creates a device context by calling device context functions. GDI returns a device context handle used to identify the device.
Applications can direct output to a physical device, such as a display or printer, or to a logical device, such as a memory device.
A device context also contains attributes that determine how GDI functions interact with a device. These attributes eliminate the need to specify every piece of information Windows Embedded CE requires to display an object on a device. If you want to change an attribute, you can use attribute functions to change current device settings and operating modes. Operating modes include text and background colors and the mixing mode that specifies how colors in a pen or brush combine with colors already on a display surface."
GDI is the source of 2D on our devices. Maybe we need to look out for GDI tweaks in the registry?
BPP (Bits Per Pixel) explained
I also found this blog about the colors used on a mobile device. It's said that if you have a colordepth of 18 instead of the usual 8, 16, 32 bits, it's more cpu intensive. Isn't there a registry key for colordepth?
http://blogs.msdn.com/windowsmobile/archive/2005/09/07/462187.aspx
"The next thing to understand is how the bits turn into colors on the screen. Say you've got a typical PocketPC with a resolution of 240x320 and 65536 colors. That means you've got 320 rows of 240 pixels (dots), each of which has 16 bits of data representing its color. All of that information is stored in a chunk of memory known as the "Frame Buffer." The LCD hardware takes whatever is in the Frame Buffer and converts it directly to what's on the screen. Want to change what's on the screen? Change what's in the Frame Buffer and the screen will update.
Okay, so we need 16 bits for every pixel, and we've got 240 times 320 dots. 16 bits is two bytes, so that's a total of 153600 bytes, or 150K of RAM used to hold what's on the screen."
Maybe a good thing to mention: we're hoping that the Toshiba g810 Portege has the files we need to develop a 2D driver. We're currently trying to extract a dump we got. Anyone have experience in extracting Toshiba's .Bin files?
Direct Draw explained
On MSDN:
"The DirectDraw® API provides support for hardware-accelerated 2-D graphics. It offers fast access to display hardware while retaining compatibility with the Windows graphics device interface (GDI). DirectDraw is a specialized memory manager for both system and display device memory and uses hardware acceleration where available. With DirectDraw, you can allocate and manipulate both system and graphics memory, including transfers between the two.
DirectDraw for Windows Embedded CE is adapted from DirectDraw for Windows-based desktop operating systems. Some capabilities from the desktop version have been extended and others have been curtailed to better suit embedded devices.
DirectDraw supports the following effects:
Bit-block transfers (blits)
Page flipping and multiple back buffers
Overlays, which is placing one image surface over another on the video display
Alpha source over destination blending, which is blending two surfaces using the source alpha image component
Video YUV pixel formats and color conversion
Direct video access to the frame buffer
What if we compare our HKLM\system\DDRAW\ keys in the registry with other devices? I see the values in ALL keys there are empty.
Yes.. I've noticed that and played around with them.. no difference.
I've tried the LG KS520, Diamond and HD ddraw.dll files.. none work out of the box. Maybe the G810 one might make a difference?
We need to find out what calls are made and to what other dll files. If you remember the problem we had with the 3.13 ddi? it could be similar situation in that theirs a dependencies issue.
DirectMobile is a DirectX based Managed UI Framework for Windows Mobile. Aim of the framework is to provide an elegant UI for Windows Mobile devices which is simple to develop against.
Target Platform:
WM6.0+
.NET CF 3.5
Current Implementation:
All graphics rendered in Direct3D. Each DM Application gets access to the rendering device and has one host window. The host window renders one frame at a time. Each frame can hold other elements such as buttons, labels or lists.
Design Considerations:
Sharing of GPU by multiple applications [High Priority]: Ideally a DirectMobile Rendering service must be implemented and applications request rendering via named pipes. This will reduce GPU and CPU utilization.
Remove dependencies on System.Windows.Forms [Low Priority]: To reduce developer confusion, references to Windows Forms need to be removed. This can be implemented via native calls to AGL lib.
Tested Against:
Blackstone: WM 6.5 + Neo Driver Pack r3
Touch Cruise: WM 6.5
WM 6.5 Device Emulator
WM 6.1 Device Emulator
WM 6.0 Device Emulator
Sample Code:
public static void Main()
{
//Start DirectMobile Application
DMApplication.Run();
//Render a new Frame
DMApplication.Current.ShowFrame(new Controls.Frame{ BackgroundColor=Color.Black, ForeGroundColor=Color.White, Title="My First Frame"});
}
DirectMobile on Codeplex
put me down for pre-alpha, alpha, beta, rc tester.
Nice initiative. It is rumoured that MS will let go of Direct3D with the onset of WM7. Is OpenGLES not the way forward?
On a side note, I wouldn't mind beta testing, heh.
Thanks in advance.
Count me in for graphics and ideas (if needed).
nuke1 said:
Nice initiative. It is rumoured that MS will let go of Direct3D with the onset of WM7. Is OpenGLES not the way forward?
On a side note, I wouldn't mind beta testing, heh.
Thanks in advance.
Click to expand...
Click to collapse
I did a quick lookup and i dont see any references on OpenGLES been used with WM7. If you find something let us know but please lets not discuss this here
Am always willing to test for constructive purposes. Let me know if you need a tester for the HTC Fuze / Touch Pro
i am also willing for some alpha and beta testing!!!! using a diamond
twolf said:
Count me in for graphics and ideas (if needed).
Click to expand...
Click to collapse
me too, graphics and usability issues.
wondering if XDA Flame will support this in HW Accelerated mode.
Most of the drivers on Flame are reference BS, slapped from the MS emulator onto the device. Fingers crossed for this one.
Count me in to test it (VGA device, HTC Universal).
I'm in as a developer. I have a decent amount of c# experience.
will to beta test for usabilty and bugs - diamond user.
Count me in. Sprint touch pro
I'm also want to be a tester. Also, can help in development, if free time will be exists.
I'm not try use managed DirectX, only OpenGL small apps for PC.
HTC Blackstone.
I thought about writing something like this a while back - don't have a ton of cycles, but can contribute on the dev side and testing.
I can help with testing this time around. Maybe I can help with developing later on. I'm using an HTC Touch VOGU100
tester
just got a touch pro and can consider as intermediate user .....well i can help out as tester ... do giv me a pm ..... hopefully i can help out n also gain some exp ..... thanks
I will be happy to help with graphics and design. I have helped with the manila - framework.
BTW: my other account it call UknownDev
also I am have some nice TF3D Themes.
So.. I'll be more than happy to help.
nice!
I'm in for testing and graphics!
I own an ASUS P550 (greek WM6.1pro) and will probably switch to an Omnia variant soom.
This seems to me like a great idea!
I'm experienced with C# and would like to help in this project (the development part). I don't have much spare time because of my current job, but whenever I can find some, I'd love to help.
-- edit:
I've got a Codeplex Id: w0lf