[DEVS needed](Camera / Multitouch / Sound).. getting closer to native WP7 experience - HD2 Windows Phone 7 Development

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!

Related

Working Bluetooth ROM hybrid!

I've been working with a great group of developers over at PPC-geeks.com on the Titan bluetooth problems, and I'm proud to say that our efforts have been fruitful!
The History:
In case you didn't know, the Titan has had horrible official Bluetooth support, and even the custom roms only get it "partway" there.
HTC's latest CDMA device, the Touch, uses roughly the same hardware under the hood as the Titan, however their bluetooth worked flawlessly. So, clearly the hardware is capable, its a matter of running the proper software!
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
The Solution:
Update the OS, but keep the drivers from an earlier build that had less new "issues" with BT. The 2.09 rom from sprint had stable bluetooth, however it had poor quality over the headset/handsfree profile. This was apparently NOT an issue with the drivers as much as it was an issue with how the OS handles them!
Replacing the OS with a ported AKU .7 from a Universal, and basing the rest of the rom on 2.09, we have what appears to be a release with stable, decent quality bluetooth that works as it should have out of the box!
More testing is needed, but it seems like the best build so far, and should be a strong candidate as a base rom for future customs.
What this fixes:
-No more poor BT quality
-No more random BT shutoffs
-No more system freezes when coming out of standby due to BT stack left on and disconnected
-No more D-pad lock issues
-Generally stable Bluetooth performance that works AS EXPECTED.
Known issues:
-Alarm Bug, which was and still is a part of 2.09
However, we're working on a fix for this.
Find it here:
ftp://ppcgeeks:[email protected]/Titan/Users/sfaure03/ithinkwegotsit.rar
(as of this writing, the ppcgeeks ftp and webserver have been hit pretty hard, and are timing out an awful lot, so if it doesn't work, try again later. Perhaps someone would like to mirror it somewhere?)
Special thanks to all who contributed to this effort, particularly PPC-geeks users Sfaure03, DogGuy, no2chem, jtrag, and all the others who tested, theorized, and gave sage advice.
Personal thanks to ImCoKeMaN, for explaining how things work and having the patience to answer bizzare questions from the rest of the group.
edit: whoops nevermind
I'm not expereinced enough in using this type of file - can you please tell me what is the procedure to install a .rar file into the phone.
its an .nbh file, rar is the compression method. Its like .zip, only you need winrar (or something compatible) to uncompress it.
there's a tutorial on ppc-geeks (which I should really post here as well) about how to unlock and flash custom firmwares on the titan.
you guys rock!
So installed this ROM a couple hours ago. So far the phone's working fine. Tested BT in my RAV4. Wife says it's much improved -- previously if I called from the carphone she'd known instantly and ask me to switch it off. Now she's says it's fine. (High praise indeed. )
So bottom line: quality issues appear much improved. Major kudos!
Update: maybe I was slightly hasty. So the phone sits in my pocket for a few hours. I press the power button to bring it out of sleep. Password screen takes 15 seconds to come up. Enter the password, Today screen takes 30 seconds. Click on the Voicemail link, get a message that the phone cannot make the call. (low RAM?) Nothing else (afaik) except SPB Mobile Shell running at the time.
Boom, soft reset. Is it the phone? Is it the ROM? Is it me?
Mirror at: http://rapidshare.com/files/71094429/ithinkwegotsit.rar.html
The ROM finally makes my BT usable, but is still quite choppy and compressed. Unfortunately not a true fix for my device.
But, kudos to the developers for getting it to be usable! Thanks!!! You clearly beat Sprint/HTC!
However, my RAZR2 and Touch still have much better BT, so will keep using them at least for awhile.
Will see if the 'official' Sprint ROM (1) actually happens, (2) truly fixes the problem. If not, then I'll use my Touch until the Treo 800w or Titan 2.0 come out and likely swap my Titan at that point.
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
wsparvis said:
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
Click to expand...
Click to collapse
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
I have to agree here - the Cingular 8525 runs quite well with only 64MB of RAM (Other at work run it). My Titan runs quite well with only 64MB of RAM - HTC Home from the touch on the other hand makes it run like a three legged dog. Without the 3rd party plugins it zooms along quite well even with several apps running.
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
OK - fair enough, my memory comment WAS off topic! BTW you introduced the word "major"; I never said it was major - just unfixable. And, yes, you're right - if you want to manually do the OS's job for it, there is an acceptable workaround.
Interesting, though, that you responded only to that one sentence out of five in my post, not the other four which stated that BT quality is poor/mediocre on my device (which is an improvement from the prior unlistenable state).
Anyway - what kind of success rate are you seeing from various forums with this ROM? I still suspect the problem is partially HW, and that BT on some devices (mine probably one of them) may be unfixable.
Dishe said:
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
Click to expand...
Click to collapse
Why call out another developer? I fail to see how it was necessary. I'm assuming you have no life, and make roms for a living? I'll download whatever works; but because of your approach to criticize other people who try (which is EXACTLY what you do) to make something work, makes me not want to download your rom.
dishe is an such arrogant SOB, who think he's all that because he's creating ROM...well props to you that you do create rom...but its just people opinion/wish about having more ram (which is UNFIXABLE! on mogul)...you don't have to bash them for it...would u preferred an old style laptop/computer from the 2000's or newer/faster in 07's. However, you might be able to upgrade their RAM through hardware...but does HTC have such RAM upgrade for mogul!? anyways...i'm not hating on your work at all...but i just get disgusted when you go and ranted on someone post (n it was a valid post.)
ps. If you want to brag, make something that's useful w/o any glitches. Success at that then brag all you want, but at this moment you still using the public to test whatever ya doing. So stop tripping home boy.
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
hey DISHE
bro u dont even owe these guys an explanation, they contribute nothing and take everything. they dont understand whats involved and quick to criticize anything they dont agree with.
it appears to me that they think they are all that and a bag of chips/ but if the DEVs of these fixes decided not to share, i bet they would keep there mouth shut real quick/
bottom line bro, dont bother posting any more responses to these idiots / look at the end of the "
Hard-SPL - or how to not brick your PDA ever again" post and u will see what these guys are like on this forum, calling each other names and etc just like they r doing now.
i c u at ppcgeeks
Dishe said:
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
Click to expand...
Click to collapse
Where was I supposedly contacted?
dishe don't even trip! The folks *****ing are the ones using the Roms also. Take their comments with a grain of salt....F**K EM!!!! Don't waste your time on these idiots. Others apperciate the work you do to make our Moguls useful.
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
lazee said:
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
Click to expand...
Click to collapse
LMAO...such childish folks here....I'm gonna just LMAO!! at u...so sad
Lazee,
its not about kissing ass. Its about appreciation for what these guys do (AND FOR FREE they do it!!!!) they rarely ask anything of the rest of us, if anything at all. Because of the fact that they do give up alot of free time, which they could be doing something else, to help out alot people they dont even know, i have a certain amount of respect for that alone, regardless if they might seem arrogant. the truth is that they really do care about people or they wouldnt even share what they do! theres no law that says that they have to share anything with us/ sometimes its easy for us to forget this and take it all for granit/ lets just call a truce and stop with the name callin and etc and try to maintain a respectible forum ok.
PEACE!!! come on guys we are all in this together
Oh and by the way Custel, u rock bro, do what it is u do and dont stop!! dishe luvs ya nothing personal, i dont want to speak for him but i get the feeling that things might have came out wrong when he was responding to the "lazee's post and was just a lil fluddered.

Windows 7 mobile on hero?

Is it possible to get the new Windows 7 mobile on the hero? If so, how? If not, can someone make it possible?
nicolajreck said:
Is it possible to get the new Windows 7 mobile on the hero? If so, how? If not, can someone make it possible?
Click to expand...
Click to collapse
No. Wrong chipset, not powerful enough, wrong screen size. Many reasons.
Wrong chipset is enough though.
Its windows ..... thats enough of a reason XD
btdag said:
Its windows ..... thats enough of a reason XD
Click to expand...
Click to collapse
Well, android can run on a iPhone, so, it's not a stupid question
Android should run on the iPhone - its the only way they'll get a good OS on their phone! but why would you want to run the iphone os or windows on an android phone?
I'm being antagonistic for the sake of it FYI. And the question was never "stupid" - your words not mine
I would love to see this happen - just to say they we can run any of the OS's. BUT IMHO Android is by far the best and I would never replace it completely on my phone. I think most of the devs on here probably feel the same which is why you're unlikely to see anyone working on doing this.
AND IMHO - there is no technical reason that either of the above mentioned OS's wouldn't run on an Android phone. Drivers/Code can be created for chipsets and screen size & resolution is easy to fix (in comparison). It may not be simple but its dooable. The tricky part would be getting access to the code - as those os's aren't open source or copyleft. So you'll have to "illegally" break the code to gain access in order to create the drivers to support other chipsets etc. This creates a nightmare time for places like XDA from a legal standpoint as they will be liable if people distribute this code through their website.
So in terms of this topic actually going somewhere and this technology actually coming to fruition - don't hold your breath!
I hope this helps a little more than previous answers
btdag said:
Android should run on the iPhone - its the only way they'll get a good OS on their phone! but why would you want to run the iphone os or windows on an android phone?
I'm being antagonistic for the sake of it FYI. And the question was never "stupid" - your words not mine
I would love to see this happen - just to say they we can run any of the OS's. BUT IMHO Android is by far the best and I would never replace it completely on my phone. I think most of the devs on here probably feel the same which is why you're unlikely to see anyone working on doing this.
AND IMHO - there is no technical reason that either of the above mentioned OS's wouldn't run on an Android phone. Drivers/Code can be created for chipsets and screen size & resolution is easy to fix (in comparison). It may not be simple but its dooable. The tricky part would be getting access to the code - as those os's aren't open source or copyleft. So you'll have to "illegally" break the code to gain access in order to create the drivers to support other chipsets etc. This creates a nightmare time for places like XDA from a legal standpoint as they will be liable if people distribute this code through their website.
So in terms of this topic actually going somewhere and this technology actually coming to fruition - don't hold your breath!
I hope this helps a little more than previous answers
Click to expand...
Click to collapse
Thanks for the detailed answer, that explained a lot more.

Windows Phone 7 on Topaz... COME ON DEVS!

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...

Tapping into the knowledge question

Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
xriderx66 said:
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
Click to expand...
Click to collapse
Thanks for your response. I do understand that "cutting & pasting" is a no go. But what got me curious is that the hardware is the same. So speaking from a PC Geek's view a series of GPU's if you will can be produced by different third party vender's. However the Drivers would be the same even if the third party vender changes the BIOS they could still be flashed to another card ex. flashing ASUS bios to a similar card like a MSI GPU. Some vender's may slightly change the user interaction ex. software suites for "tweaking" settings ie over-clocking. So I guess this is why I'm asking what is so different regarding these two phones that prevents a "clean" port. If the hardware was a completely different generation I totally could understand. This unless I am wrong (which I probably am) is what is bending my logic.
Edit: I stand corrected the Nexus is different
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
vs.
http://www.ubmtechinsights.com/repo...stigative-analysis/samsung-galaxy-s/teardown/
amwilliams9 said:
Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
Click to expand...
Click to collapse
difgerent radio, difgerent storage inand on ns, basically two different phones
And most importantly the lack of vibrant source code
Sent from my Nero powered Vibrant

[WIP] Finding professional developers to fix WP7 bugs on HD2

Hi all, we all know the main Windows Phone 7 bugs on our HTC HD2.
There were lots of threads and everytime we stated that the fixing process would need a professional developer (and he has to be a good one).
Professional developers work for money, so i had this idea:
We can propose a job for a developer on www.getacoder.com and pay him with our money, together.
I'm not asking for money, i'd just like to know how much will you pay for this.
I'll take the total amount as payment, so please be honest as, if you say you'll give to this project 10$, your 10$ are needed by the project itself!
I also thought about splitting the work (fixing one bug at time), this will make it easyer to find developers to work on it succesfully.
So, how much are you going to pay to get a fully working Windows Phone 7?
If you think this is a good idea, thank me and share it with your friends Higher we get, faster we will get bugs fixed
15 euro ...
Ahother funny thread .....
Why? Don't you think anybody will be able to do that?
I hope this doesn't turn into a crazy high bounty thread.. haha
dual boot mango and AmericanDroid?
I would love a stable build WP7 mango and dual boot American Droid 2. 3. 4, I would donate up to 50$
has anyone done this successfuly?
trav_44 said:
I would love a stable build WP7 mango and dual boot American Droid 2. 3. 4, I would donate up to 50$
has anyone done this successfuly?
Click to expand...
Click to collapse
Not yet as far as i know, that's why we are here
e334 said:
I hope this doesn't turn into a crazy high bounty thread.. haha
Click to expand...
Click to collapse
In fact, let's hope so Higher "bounties" means more money to pay developers
Professional or not I will donate 30$ to 50$ (depending on the success) to put everything working, specially camera,multitouch and Bluetooth drain in standby..
Sent from my HD2 using XDA App
Developer is last thing you will need. The first most important - get documentation from HTC fully describing HD2 hardware(ports adresses, interrupts and other hardware parameters) in details. And tools as well. This has to be hardware device driver programming. It takes a lot of time and effort even with documentation, but imposible without. It is not web or graphics or kind of this programming.
So first collect money to pay HTC for docs. Or better idea - collect money to pay HTC to develop perfect drivers.
That is why this and other threads like this will lead to nowhere without documentation.
zcdg said:
Developer is last thing you will need. The first most important - get documentation from HTC fully describing HD2 hardware(ports adresses, interrupts and other hardware parameters) in details. And tools as well. This has to be hardware device driver programming. It takes a lot of time and effort even with documentation, but imposible without. It is not web or graphics or kind of this programming.
So first collect money to pay HTC for docs. Or better idea - collect money to pay HTC to develop perfect drivers.
That is why this and other threads like this will lead to nowhere without documentation.
Click to expand...
Click to collapse
I know, electronic is my field, but if someone who knows how to do it, decompiles drivers, he can get the needed informations. I know ASM is not easy and it's hard to understand what the code does, that's why, this time, we need a professional developer payed to do so instead of the (maybe) community developers which can work on this only in the spare time.
Your theory sounds good, but ...
Did you ever try to disassemble any hardware driver for such a complex device? Without anything...
Even if someone will get some information back from reverse engineering existing drivers it won't be complete enough to modify/make drivers perfectly working. It is all guessing without proper information - results are unknown. Who will pay for unknown results?
Possibility is only find contacts with HTC to get docs. DTF probably has such contacts(i don't know how deep are contacts)
All others ways i think(based on my experience in reverse engineering) just dreams and waste of time....
zcdg said:
Your theory sounds good, but ...
Did you ever try to disassemble any hardware driver for such a complex device? Without anything...
Even if someone will get some information back from reverse engineering existing drivers it won't be complete enough to modify/make drivers perfectly working. It is all guessing without proper information - results are unknown. Who will pay for unknown results?
Possibility is only find contacts with HTC to get docs. DTF probably has such contacts(i don't know how deep are contacts)
All others ways i think(based on my experience in reverse engineering) just dreams and waste of time....
Click to expand...
Click to collapse
Why? If he manage to understand how the hardware works, he can do that. As I said it's an hard way, but i don't think HTC is going to give us their private specs.
Because world made this way....
You can't get good from bad drivers- simple if like this way....
zcdg said:
Because world made this way....
You can't get good from bad drivers- simple if like this way....
Click to expand...
Click to collapse
If DFT has made those semi-working drivers and, as you think, they have contacts with HTC, maybe they are still working on them?
DFT didn't do any drivers for HD2. Drivers were made by HTC for internal testing purpose only. that is why they are so buggy - not finished. DFT found the way how to get that test ROM and drivers from HTC. And surely they have contacts with HTC - official/unofficial i don't know.
P.S. i don't think anyone working on drivers - for this long period of time(from first test ROM to Mango) we don't see any kind of progress.
Looks like all serious developers forgot about HD2(exept Xboxmod). Sad, but it is life.... A lots of new devices with good drivers around(they are not so unique as HD2, but devs don't care)
RE: Already Stable
trav_44 said:
I would love a stable build WP7 mango and dual boot American Droid 2. 3. 4, I would donate up to 50$
has anyone done this successfuly?
Click to expand...
Click to collapse
I don't know about the others but Yuki and Xboxmod's back to the future rom does wonders...I am currently dual booting back to the future rom with SD American Android 2.3.5. I have no bugs to report with the back to the future mango rom while dual booting back and forth with american android. I currently just adjusted the notification sounds by researching and reading threads found here...all of which was given for free...J
i think Cotulla is able to write drivers, he done it for android/linux kernel, he knows hw and sw very well, and i think that donations to DFT team are better than find a new dev.
DFT is very experienced, and they done a lot for us, from linux kernel contribution, magldr, firsts android and wp7 ROMs, and they are in contacts with HTC.
They done a lot for us for free, they spent a lot time working to improve our hd2, it's time to say thanks to DFT
i will donate 20€ for fully fixed HD2 drivers:
1)multitouch
2)battery meter
3)green tint camera
4)high drain on standby
Cotulla contact is https://twitter.com/CotullaCode
or http://forum.xda-developers.com/member.php?u=600525
It's last twit is: Yes. In our future plans for LEO: DFT Hornet, DFT Legacynd, DFT Ultrafruit and DFT MAGLDR200. Then maybe DFT Legasto...
Donations to Cotulla is the best choise for me
What are those projects?
Cero92 said:
What are those projects?
Click to expand...
Click to collapse
i think a new Desire based Android ROM
a new WP7.5 Mango ROM
a new MAGLDR 2.0
and new tools for WP?
pirlano said:
i think a new Desire based Android ROM
a new WP7.5 Mango ROM
a new MAGLDR 2.0
and new tools for WP?
Click to expand...
Click to collapse
Let's hope so

Categories

Resources