It appears progress has been made on the Kaiser (MSM7200) to have a D3D driver available.
What are the chances this will work on the Titan (MSM7500)?
http://htcclassaction.org/driverprogress.php#update_20080717_1
Looks pretty good so far.
Hell to the yeah, I'm buying that dude a fruit basket. Keep up the good work whoever you are.
i thought the msm7500 referred to the cpu, and not the graphic accelerator? or is it built onto the cpu
The msm7500 is the chipset. Everything is on the chip.
Besides the fact that one is GSM and the other CDMA, I would assume the architecture and hardware is almost identical. I think it should work but hey, I'm not an expert.
what's the more advance chipset of the two? and what are the difference?
OpenGL ES please!!!
Im very interested in getting an OpenGL ES driver for my xv6800. Im no device driver expert but I am familiar with graphics programming using OpenGL and OpenGL ES. Im willing to help in whatever way I can if anyone is working on this for the Titan. I can write OpenGL ES test apps and can use my beloved xv6800 as a alpha/beta test platform, whatever... hell I will wash your car if I have to!
Don't bother trying to install the driver... it will lock up at the carrier screen.
now to figure out how to uninstall it...
Rawr,
I had to hard reset, but I expected that
Thank god for auto installers
MrTek said:
Rawr,
I had to hard reset, but I expected that
Thank god for auto installers
Click to expand...
Click to collapse
Yeah i figured i'd have to do that too... good thing i only cooked this setup the other day
The problem that we're going to have is that the power user base for the Mogul and Touch combined is still less than that of the Kaiser, since the Kaiser isn't just the Tilt in the US but is sold in other countries as well.
I don't really think that no2chem wants to start another project right now, he's busy trying to get nueROM 2.2 out the door.
Eth,
I agree..... CDMA phones are still in the minority on this board.
Ahh...When Verizon goes LTE I'll be a happy boy. Of course that will be 2012 - 2015.
By that time my phone will be holographic, 5TB of data storage, and a mind implant instead of a touch screen
But We'll still have to hack it just to do the things we want!
MrTek said:
Eth,
...By that time my phone will be holographic, 5TB of data storage, and a mind implant instead of a touch screen
But We'll still have to hack it just to do the things we want!
Click to expand...
Click to collapse
5TB? For a holographic phone? That's the same mentality that designed the Titan with 64M of memory. =P
We need 1.21 Jigabytes!!! (yeah I quoted Dr Emmet Brown)
I can totally see us jacking in ala Circuitry Man!
If you are curious at the paltry D3D performance of your Titan, here is the D3D Demo app from the Treo 800w.
I get 4fps
ddi.dll
A little updated info on MSM7x00 driver support from htcclassaction. Basically they say to check for a couple of dependencies in ddi.dll.
http://www.htcclassaction.org/driverprogress.php#update_20080722_1
I was going to download/install the windows mobile SDK tonight and see if I can see the dependencies but thought I would check to see if someone has done it already first .
mrfurby2u said:
A little updated info on MSM7x00 driver support from htcclassaction. Basically they say to check for a couple of dependencies in ddi.dll.
http://www.htcclassaction.org/driverprogress.php#update_20080722_1
I was going to download/install the windows mobile SDK tonight and see if I can see the dependencies but thought I would check to see if someone has done it already first .
Click to expand...
Click to collapse
our ddi.dll has no ties to disptools.dll. i think we would need a ddi.dll from another device - im not even trying.
Dcd,
And I am sure this is too obvious to be possible, but couldn't we get the ddi.dll from the Kaiser?
or is the ddi.dll needed specific to the device or the MSM7500 chipset?
MrTek said:
Dcd,
And I am sure this is too obvious to be possible, but couldn't we get the ddi.dll from the Kaiser?
or is the ddi.dll needed specific to the device or the MSM7500 chipset?
Click to expand...
Click to collapse
there are people more capable than myself who could maybe do it, but kaiser's ddi.dll does not work for me.
DCD,
From reading the information on the MSDN link
http://msdn.microsoft.com/en-us/library/aa447495.aspx
It looks like DDI.DLL is the video driver itself?
could we possibly look to the Vogue/Touch for this driver?
Related
Does any one know if any one in the Titan threads (xda or ppcgeeks) will be creating a New Rom based on the leaked Diamond ROM
http://forum.xda-developers.com/showthread.php?t=394985
The Kaiser community has managed to create one already.
dcd has been talking in the Diamond ROM threads so I would imagine that he will be doing one.
Has any one extracted the components from the ROM?
I was thinking of doing a Diamond Theme, but I would rather save some time if some one already extracted the components.
[email protected]$ said:
Has any one extracted the components from the ROM?
I was thinking of doing a Diamond Theme, but I would rather save some time if some one already extracted the components.
Click to expand...
Click to collapse
VetVito over at PPCGeeks has ported over a Diamond ROM and is testing some OEMs now according to his latest post.
would the titan be able to run that well though? I doubt it would be worth it.
Its not the the actuall full rom...just the updated build and such...not the 3d interface...we have no drivers
there are some cool OEM apps in the diamond
it also has aku 1.1 SYS
its very buggy. my standard ROM will not be getting this OS.
I will be updating parts of OEM from it.
since its a test build and clearly buggy, i am not going to mess with bringing over any drivers.
dcd1182 said:
there are some cool OEM apps in the diamond
it also has aku 1.1 SYS
its very buggy. my standard ROM will not be getting this OS.
I will be updating parts of OEM from it.
since its a test build and clearly buggy, i am not going to mess with bringing over any drivers.
Click to expand...
Click to collapse
yes, but i wanted to ask, since i checked out the OEM ROM Pack from the diamond i was able to find out it did contain alot of updated drivers for some of the same hardware the titan had, specifically the WIFI module, i was going to update it myself, but didn't think it would be worth it if ur going to do it on a later build of your own rom MR. DCD. And hey there were even tons of hardware accelerator drivers that may actually work for the titan. wonder if you were able to port em over? probably not since a lot of these drivers are also created for what they were intended for, and that clearly isent the titan.
Regardless i cant wait to see what you have in stock for us with a Diamond based ROM for our titans, for the time being befor i get myself the HTC Raphael.
Its to bad the xperia is only GSM and not CDMA, That really looks like a nice phone, but the Raphael well be nicer maybe...
i already tried making my own cabs for alot of what the diamond offers to put on my titan, but alot of them require massive changes because of QVGA... so nothing really kicked off. and im not talking just picture re-sizing, there was alot of XML changing and .dll modifying (which im not capable of) so i don't even think well be seeing a fully fledged diamond clone rom for our titans any time soon, ESPECIALLY SINCE WERE STILL WAITING FOR THOES DAMN HARDWARE ACCELERATION DRIVERS... UGH... Did they think since its QVGA, that its just not even worth it? well they better be coming with em soon, cause I'm getting ridiculously impatient.
ranmasaotome510 said:
yes, but i wanted to ask, since i checked out the OEM ROM Pack from the diamond i was able to find out it did contain alot of updated drivers for some of the same hardware the titan had, specifically the WIFI module, i was going to update it myself, but didn't think it would be worth it if ur going to do it on a later build of your own rom MR. DCD. And hey there were even tons of hardware accelerator drivers that may actually work for the titan. wonder if you were able to port em over? probably not since a lot of these drivers are also created for what they were intended for, and that clearly isent the titan.
Regardless i cant wait to see what you have in stock for us with a Diamond based ROM for our titans, for the time being befor i get myself the HTC Raphael.
Its to bad the xperia is only GSM and not CDMA, That really looks like a nice phone, but the Raphael well be nicer maybe...
i already tried making my own cabs for alot of what the diamond offers to put on my titan, but alot of them require massive changes because of QVGA... so nothing really kicked off. and im not talking just picture re-sizing, there was alot of XML changing and .dll modifying (which im not capable of) so i don't even think well be seeing a fully fledged diamond clone rom for our titans any time soon, ESPECIALLY SINCE WERE STILL WAITING FOR THOES DAMN HARDWARE ACCELERATION DRIVERS... UGH... Did they think since its QVGA, that its just not even worth it? well they better be coming with em soon, cause I'm getting ridiculously impatient.
Click to expand...
Click to collapse
i didnt look at the wifi driver really..
i played a little bit with drivers last night (i have the cdma diamond rom, not sure if its leaked anywhere yet?) but it seemed that anything of interest has a dependency down the chain that is incompatible. i may give it another try but when i found that, i scrapped that project for other things.
right now i am trying to package/play with the OEM stuff. some of it will make it over.
Cool, but I don't mean to crush hopes, just thought you should know:
The Diamond has 192MB or RAM or 3 times what the titan has and 1.5x what were begging for (128...) we're going to run into big problems. Though the idea of OEM would be cool.
Also on the subject of ROMs the P6500 now has a forum and it's got a rom from it. The 6500 is rumored to have good drivers so that could be cool.
Unfortunately the Raphael will be GSM if the recent engadget news is correct which pus the thing on T-Mobile.
Cycomachead said:
Unfortunately the Raphael will be GSM if the recent engadget news is correct which pus the thing on T-Mobile.
Click to expand...
Click to collapse
the Raphael will also be CDMA... Sprint will have it and hopefully Telus will too...
rawr said:
the Raphael will also be CDMA... Sprint will have it and hopefully Telus will too...
Click to expand...
Click to collapse
really, that's cool! 5 rows of a hardware keyboard. Hopefully VzW will open up by then.
===================================================
Developing a graphics driver for Windows Mobile Wiki
===================================================
Now, the goal of this thread is to unite the different driver threads on different device forums. I've seen alot of good stuff going on but the info is too spreaded.
So, here's a list of threads discussing / devving a driver or performance:
====================================================
Kaiser / Polaris / Nike
Polaris 3D Driver Development Project (P3D)
Blackstone
Nike
Diamond
Xperia X1
KaiserGL Development
====================================================
Testing Team
Let's get these MSM devices performing the way they should! What we need is people who know about OpenGL ES and the Windows Mobile OS, and willing to contribute in development. We're currently testing the Twin's Libgles_cm.dll combined with OpenVG and Ati drivers. With that, there's also Windows Mobile 7 coming, with probably updated drivers and core. All these factors need to be taken in account, and that's what we're currently researching.
====================================================
OpenVG
This new 2D hardware driver development started by Khronos for mobile devices in 2008. Currently, we've managed to get a few files from the Quartz which seem to enable the openVG capabilities in the Xperia, and the Diamond seems affected by it. It seems heavily dependable on DDI so it may or may not work with your device.
UPDATED 24-09-09 - NeoS2007 Driver pack 3:
Installation: Disable Manila or Titanium before installing the cabfile. It's to make sure there are no files in use when copying the files. If you have an older version of the driverpack installed, best thing to do is a hard-reset. I know, it sucks. But believe me, it's best for your device.
Reported working devices so far: HTC Touch Diamond, Touch Pro, Touch HD, Touch Pro 2, Touch Diamond 2 and Sony Ericsson X1.
Test OpenGL (now with different resolutions!): http://forum.xda-developers.com/showthread.php?t=511363
Changelog & F.A.Q.
http://forum.xda-developers.com/showpost.php?p=2868656&postcount=2
The driverpack on the net
Newspost on Windowsmobilejunkies.blogspot.com
Newspost on Pockethacks.com (Good to see the poster adds his "donation link")
Newspost on vip-chicks.de (german)
great!
i was hoping they would bring these projects back. Maybe someday my kaiser can enjoy true TouchFLO 3D
thanks and good luck to the team
mbarvian said:
great!
i was hoping they would bring these projects back. Maybe someday my kaiser can enjoy true TouchFLO 3D
thanks and good luck to the team
Click to expand...
Click to collapse
There is no team... Yet. This thread is also a cry for help. I can't do this myself and i'm no programmer. I did however read up on alot of info about OpenGL ES and the Windows Mobile drivers. AFAIK, the current drivers lack calls, and the hacked driver from htcclassaction.org has a bug which keeps the screen on when 3D is used. (It's a dirty hack to keep the screen alive, because in the Polaris 3D project, the screen wouldn't come back on when the device went into sleep)
If that bug can be resolved, at least the Kaiser and Polaris users can run Manila3D.
It's great to see that the development of the MSM720X devices hasn't been abandoned!
I wish you (and other developers) the best of luck!
HRQ.SLV said:
It's great to see that the development of the MSM720X devices hasn't been abandoned!
I wish you (and other developers) the best of luck!
Click to expand...
Click to collapse
It nearly is abandoned, that's why I started this thread. I'm hoping more people will aid me in this quest to get a decent driver for our MSM720X devices.
By the way, the new ROM by Laurentius26 for HD gives nice results in GLbenchmark. If you have an HD, give it a try.
The 1-mar-09 topaz drivers give some very good results on the X1
Can you post a benchmark result?
ah, this thread was lost too
Neo, could you please post the OpenVG files and registry again and I can repost a .cab
ummm... ok, but can You tell us what this cab exactly does and is there any real gain in any speed/ functionality from it? sorry to sound silly, but I couldn't spot much info about it.
thanks
bro
bronx said:
ummm... ok, but can You tell us what this cab exactly does and is there any real gain in any speed/ functionality from it? sorry to sound silly, but I couldn't spot much info about it.
thanks
bro
Click to expand...
Click to collapse
that's because this thread was restored from yesterday's backup after the site crashed, and a lot of posts were lost
mbarvian said:
ah, this thread was lost too
Neo, could you please post the OpenVG files and registry again and I can repost a .cab
Click to expand...
Click to collapse
Here you go
"HKLM\software\HTC\VelocityEngine\3D\enable=1"
also: are you using this http://forum.xda-developers.com/showthread.php?t=495145 ?
NeoS2007 said:
Here you go
"HKLM\software\HTC\VelocityEngine\3D\enable=1"
also: are you using this http://forum.xda-developers.com/showthread.php?t=495145 ?
Click to expand...
Click to collapse
I did at first, but when I tried to add the registry entry the signature blew up on me, obv
but, on an emulator, I had no problem installing normally, so attached it the normal version
btw, could you change the title of this thread again?
thanks man
Thank you mbarvian. I've edited the threadtitle and added your file to the first post.
Projects like this one is what makes XDA-Developers worth visiting AND STAYING.
mbarvian said:
I did at first, but when I tried to add the registry entry the signature blew up on me, obv
but, on an emulator, I had no problem installing normally, so attached it the normal version
btw, could you change the title of this thread again?
thanks man
Click to expand...
Click to collapse
What is VG for?
http://www.khronos.org/openvg/
and
http://en.wikipedia.org/wiki/OpenVG
Enjoy reading
is there a noticeable difference between these and the samsung omnia d3d driver?
LG ks20 driver?
any driver for LG ks20?
Hey, you probably heard that WP7 has been ported on HD2.
Well, that's a great start. But I think we can try it out... Even it would be a lot buggy or slow or anything else... I think if we contact DFT (Dark Forces Team) they might help us out... I know it's near impossible (because of our ARMv6 CPU. == WP7 needs an ARMv7 CPU which HD2 has it.) But it's not impossible completely... Let's do something about it... What do you say devs?
I'm just waiting for the hackers team is to discuss about this. Because I am only new person in the world PHONE.
im will suporter to u all
Come on ,it will be great to run wp7 on topaz
Oh golly, because you demanding it will sure make them motivated.
When you say "Lets do something" you must mean, "I cant do it, can you do it for me?". Why not learn reverse engineering, and then doing something yourself? Because realy, if you want dev's to do all the work for you, you obviously should stick to the Windows-GUI manipulation level, doubt being spoof-feed will help you.
Desert Storm said:
Oh golly, because you demanding it will sure make them motivated.
When you say "Lets do something" you must mean, "I cant do it, can you do it for me?". Why not learn reverse engineering, and then doing something yourself? Because realy, if you want dev's to do all the work for you, you obviously should stick to the Windows-GUI manipulation level, doubt being spoof-feed will help you.
Click to expand...
Click to collapse
First of all, I don't see any reason to answer you directly. In second, I'm a developer but can't do it alone. I'm asking for help. So just keep learning things. You may someday understand what I was asking for.
Personally, I wouldn't mind seeing a port for the Topaz, and I'd probly try it out... But I'm looking forward to the cracking of WP7 on WP7 phones so that I can upgrade to a new phone and not be stuck with that horrible start screen
Black.Heart said:
First of all, I don't see any reason to answer you directly. In second, I'm a developer but can't do it alone. I'm asking for help. So just keep learning things. You may someday understand what I was asking for.
Click to expand...
Click to collapse
I know you have some developing skills, although I dont know if it goes beyond changing the registry and gui-manipulation, but the system-level developers are unlikely to port the Windows 7 to the Topaz, mainly because its a old device now, outdated and slow.
(And I know that you've got some knowledge because I used eclipse for few days, good ROM)
Desert Storm said:
I know you have some developing skills, although I dont know if it goes beyond changing the registry and gui-manipulation, but the system-level developers are unlikely to port the Windows 7 to the Topaz, mainly because its a old device now, outdated and slow.
(And I know that you've got some knowledge because I used eclipse for few days, good ROM)
Click to expand...
Click to collapse
I appreciate that... But as I mentioned above, it's near impossible... Not completely. Your'e right... Topaz has ARMv6 processor... WP7 requires ARMv7. But i'm talking about experiencing it on Topaz... By the way, I agree with oldness of Topaz... I'm gonna buy a Desire HD
It's wishfull thinking and never going to happen. The best us topaz owners can expect to get for our outdated phones is a 100% working Android.
hoosbude said:
The best us topaz owners can expect to get for our outdated phones is a 100% working Android.
Click to expand...
Click to collapse
And wouldn't that be great!!!!
That ain't true I find that the ui from wp7 is lite and simple. This can easily be ported to our devices with a little magic. But The part of windows live games or xbox live is the part that our devices cant handle. Our devices aren't old they where made cheap by htc and att to cover some sectors of the market. But our devices could have been easily been made with the same stuff as hd2, as few months passed since each launched.
The ui is simpler than ours and faster I think it could be done......just that I need to finish studying by then to make this. And I don't think of waiting is another great idea. As we are shadowed by what could have been if we had a twin processor to hd2's. But, we bought this and I find it great!
And please respect each other!!!!!
I think it's NOT possible because of hardware requirements.
mahra said:
I think it's NOT possible because of hardware requirements.
Click to expand...
Click to collapse
our device was made of tinking on this.. As I read before it was tought to be ported in form of an upgrade. But it was left in the clouds. And our device have the custom buttons on a new device like android and wp7. Ram can't be a prob. If the UI was made for speed and simplicity. Just the xbox live games won't run properly.
joefrank said:
our device was made of tinking on this.. As I read before it was tought to be ported in form of an upgrade. But it was left in the clouds. And our device have the custom buttons on a new device like android and wp7. Ram can't be a prob. If the UI was made for speed and simplicity. Just the xbox live games won't run properly.
Click to expand...
Click to collapse
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Black.Heart said:
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Click to expand...
Click to collapse
AH man! I've been focussing on another site. WWW.htc-pure.com, which I am a moderator. And for years I've been here quietly. but I think I will try to move here to help. Lets see what I can do.
wp7 requires ARMv7 instruction set on cpu. but topaz is just ARMv6 i think. that's why I think it's not possible
Moreover, why would you want WP7? The only thing it has going for it is that it runs smoothly and doesn't crash, which it would NOT do if someone did manage to port it. Better off building skins over 6.5.x; that way you could at least retain functionality...
joefrank said:
AH man! I've been focussing on another site. WWW.htc-pure.com, which I am a moderator. And for years I've been here quietly. but I think I will try to move here to help. Lets see what I can do.
Click to expand...
Click to collapse
I am waiting, good luck man
Black.Heart said:
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Click to expand...
Click to collapse
actually, hd2 had devices that only need to be (partially) reverse-engeneered. hell some libs etc worked directly from Desire, cotulla took half of its radio SW to get rmnet data working and ...HD7...well it's hd2 without hardware buttons!...
magldr is child's play and development was over in 2 months but they kept it testing for that time to see how phone will respond to tottaly diffrent os.
now find something like that for Touch(something).
htc was lazy with hardware at the time and hackers took advantage of that.
but these devices nature is so much different that every piece of system would have to be homebrew-and devs struggle with android for a long time with sources and inch from their nose. imagine rewriting even basic parts of kernel to support armv6 without any proper source. i truly can't imagine wp7 being done...
even with few developers, reasonable timeframe would be over year or two!
i own 3 htc phones and one td2 just for fun of it, to see evolution of htc's over the years.. go buy yourself hd2 if you really wish to hack the hell out of your phone. they go really cheap - around $200 - and save yourself time
stirkac said:
actually, hd2 had devices that only need to be (partially) reverse-engeneered. hell some libs etc worked directly from Desire, cotulla took half of its radio SW to get rmnet data working and ...HD7...well it's hd2 without hardware buttons!...
magldr is child's play and development was over in 2 months but they kept it testing for that time to see how phone will respond to tottaly diffrent os.
now find something like that for Touch(something).
htc was lazy with hardware at the time and hackers took advantage of that.
but these devices nature is so much different that every piece of system would have to be homebrew-and devs struggle with android for a long time with sources and inch from their nose. imagine rewriting even basic parts of kernel to support armv6 without any proper source. i truly can't imagine wp7 being done...
even with few developers, reasonable timeframe would be over year or two!
i own 3 htc phones and one td2 just for fun of it, to see evolution of htc's over the years.. go buy yourself hd2 if you really wish to hack the hell out of your phone. they go really cheap - around $200 - and save yourself time
Click to expand...
Click to collapse
I agree. I'm moving to iPhone 4 or Sensation or EVO 3D...
Hey guys,
Wondering if anyone can help me with this opengl thing. I am simply curious to where in a ROM is it? Also wondering what it is/does. Can anyone point me in the right direction please?
Thanks in advance.
I believe it's in the kernel information. There are discussions regarding it for the HC rom, but supposedly, the kernels we've been using are .32 or something, and the one that contains the video files we need are on a .36 version, that's a bit more difficult ot work with.
Basically, openGL, as I recall, is part of a video driver that handles 3D rendering, and/or acceleration. Our Gtablets are capable of it, and the froyo builds support it, since we have openGL for them. It's proven more difficult to be able to reverse engineer them for gingerbread or honeycomb roms. Nvidea hasn't provided the drivers for these operating systems (yet) so it's up to developers to attempt to build them from scratch, using existing drivers...
What is chainfire 3d? I read that it can run opengl apps?.. is that true?
So reverse engineering is out of the question. Snap! Lol. Ok thank you fam.
not completely out of hte question, just more difficult than expected, I think. the only thing to work from are devices running on the ventana hardware...so REing it to run on harmony board is a whole different story.
As soon as any of the harmony devices get it, then reverse engineering will, as far a sI know, be feasable.
TJEvans said:
not completely out of hte question, just more difficult than expected, I think. the only thing to work from are devices running on the ventana hardware...so REing it to run on harmony board is a whole different story.
As soon as any of the harmony devices get it, then reverse engineering will, as far a sI know, be feasable.
Click to expand...
Click to collapse
I wish I could help a bit more but I'm sucking right now! I finally broke down and want to give back to Andriod community but the whole Dev thing is kicking my ass lol. Thanks though TJ
Guys (and girls ... if any are reading .. )
After some tinkering about (for days now) with Mango build 7720 (Thanks again YUKI + XBOXMOD!) I can confirm that the many of the issues present in Mango Beta are now gone ... Ok granted the MicroSD gets encrypted but its not meant to be removed on an original WP7! You can refer to Yuki's thread on how to unlock your MicroSD card if you don't fancy the likes Microsofts OS and want to revert back to Android .....
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way. Have been using it some years now on a daily basis. I am willing to provide my help. I hope that anyone could help along maybe we create yet another open source bootloader which does the trick.
Hoping to hear from you so we get something going ...
Regards
Al
I would really like to hear from some devs I am more than sure that the community would be very grateful.
Secondly (courtesy of warriorvibhu)
I suggest that you all Sign this Petition.. Kindly inform all fellow HD2 owners to sign it ... especially if they were impressed by WP7 on HD2.
Alcatrazx said:
Guys (and girls ... if any are reading .. )
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
No there are some issues in camera and sound with android but is related to incomplete kernel. They are not related to each other for example no multi touch issues on android. All those issues are related to not perfect drivers hd7 is using another touchscreen panel I guess and maybe different speakers and camera. Anyway those drivers are complexed to write because we dont get source from microsoft on how to write them.
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Theoritically yes but CLK is designed to load an linux kernel. So if we want that we need to write a complete new bootloader.
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
Yes but you need to go backt to Windows 6.5 and read out the current drivers and port them to windows phone 7 properly. But you will need a JTAG for it and you must be very skilled.
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way.
Hoping to hear from you so we get something going ...
Regards
Al
Question
Click to expand...
Click to collapse
Hope this make some stuff clear.
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
We need an asm developer for try to fix multitouch problem... or the source code of driver...
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Just hope that's will come soon, I cant wait it !
However, I also hope the Mango will worked with flash and include more apps in the marketplace.
Fisher_9511 said:
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Click to expand...
Click to collapse
Its not working in any of multitouch Games.
Nice thread,curious to See the answers, definitely camera is a big issue for me, hope it get fixed soon.
Sent from my HTC HD2 using XDA App
Dont forget the need to use the "batterytrick"
good thread by the way
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Try to think positive man... Have you ever seen the arm listed file? We need to find a timer between the two finger... would not be so so so hard... but only hard...XD
TonyCubed said:
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Click to expand...
Click to collapse
Hi and thanks for the feedback. With a negative attitude the thread will lead to nowhere yes. That was what people said a year ago when they said that WP7 will never run on the HD2 but the devs ultimately got there. Thanks for answering the question re the Android drivers though.
You are RIGHT that the drivers in WP7 are closed source drivers ... so is MAGLDR. Rewriting another bootloader (if needed) which does not have all the frills of MAGLDR but which is open source could be a possibility.
I am not interested in getting into the WP7 ROM and modifying the drivers built in ... We have to use a technique similar to what they use when creating emulators by reverse engineering ... The most die hard emulators out there such as some of the Playstation emus out there were all closed source but it did not stop the devs from doing a proper emulation of the console.
I'd really appreciate if you could be more specific when you said that we are using the stuff which was leaked from the original "LEO" ROM ... as far as I know, is it not the Schubert which was leaked? Correct me if I'm wrong ... We got too far to give up just now...
Multitouch games do not work .. with the current Multitouch driver .. mainly due to the finger position bug .... This is explained in detail on youtube.
Sound is distorted because the input gain is too high ...
Let's not speak about the camera for now ... I think those are the two major issues which need to be remedied for now. Hopefully this thread will get us somewhere.
Regards
Al
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
backlashsid said:
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
Click to expand...
Click to collapse
Nicely said and many thanks
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
Click to expand...
Click to collapse
That is not exactly fixing the issue... It just modifies the maxima and minima ... The sound (input gain) is too high making it sound distorted from the HD2. The fix does remedy this a bit but its ... erm not really fixing the problem.
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
dazza9075 said:
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
Click to expand...
Click to collapse
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
backlashsid said:
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
Click to expand...
Click to collapse
I'd say... let's do this! If we get enough people, and those will send emails like everyday, then why not? There's nothing to lose
IF, and its a big IF, we are going to get it working better its going to need ideas like the comment from backlashsid to get unofficial support from these companies
In my humble opinion there is little chance of getting anything else working better without the support of people in the loop, essentially that means HTC and Qualcomm, but remember that by getting the HD2 running WP7 we are costing them money in lost sales, so there is little incentive for them to support us in an official capacity, what we're looking for is an insider!
it doesnt hurt hunting for new devices with the same hardware but its unlikely anyone would use old gear.
This would be nice so then we (as the community of XDA) can show off our HD2's as the beast-mode phone and bestest phone ever!