Engadget posted a link to a video tour of Windows 6.5. (The video was moved to here).
In the video (about 6 and a half minutes in), they basically say that WiMo 7 is WiMo 6.5 with multi-touch support. The reason we dont have multi-touch now is that all screens are different due to the loose hardware standards resulting in each device needing its own coding. Later with WiMo7, they intend to tighten up the standards to simplify the coding in the OS.
Is it possible that the TP2's hardware already meets those standards? In the AT&T spec leak of the Fortress and Warhawk (and yes, I know none of this can be taken as fact and the dates are obviously WAY off, but why disregard all of it?), they say the Touch Diamond 2 would require a hardware upgrade, but the Touch Pro 2 is upgradable to WiMo7.
Could it be??
yes, just test the guitar-hero game that somebody made.
Very informative...but I am pretty sure that Windows Mobile 7 isn't going to be Windows Mobile 6.5 with multitouch...
If it's not going to have large menus and large buttons like Android, iPhone, Symbian, or Pre, than it's for sure not Windows Mobile 7. And if they **** this up I might switch to android or pre.
poetryrocksalot said:
And if they **** this up I might switch to android or pre.
Click to expand...
Click to collapse
I agree. this may be the last WinMo handset I buy. unless they can pick it up and make it more finger friendly and eye-appealing.
I mean cmon, Microsoft can see that HTC and Samsung are making UI's that practically erase any evidence of WinMo, and they don't take the hint. once I get the TP2 I'm switching over to Android until Microsoft catches on.
Maybe they figure it's better to make a crappy UI that everyone knows how to program for, then let each maker do their own overlay for it.
Let's face it, HTC are obviously much better than MS at making mobile device UIs...
poppinpengawen said:
I agree. this may be the last WinMo handset I buy. unless they can pick it up and make it more finger friendly and eye-appealing.
Click to expand...
Click to collapse
This may be the last winmo handset I buy because I fear they'll soon leave behind some of their strengths chasing the capacitative/consumery bandwagon. Fortunately, I expect the TP2 to last a while.
It is a perfect OS, but the reason they can't make the buttons any bigger is because Windows Mobile is also designed for phones with small screens that are less than 2.8 inches. Because of this if they increase the standard in size, well than Windows Mobile (Big Buttons Version) would not be a logical operating system for phones with small screens.
But seriously, Microsoft needs to reassess and make a minimum 3 inch screen limit so they can create a finger friendly standard. And the stylus is still a very welcome accessory with the bigger menus and options.
If Microsoft were smart or had hired smarter people than we would have not have these stupid constraints.
Does anyone know what the required hardware specs are for a pocketpc to support WM7? And does the TP2 satisfy these specs?
sakshaug007 said:
Does anyone know what the required hardware specs are for a pocketpc to support WM7? And does the TP2 satisfy these specs?
Click to expand...
Click to collapse
http://wmpoweruser.com/?p=4332
here are 2 interesting ones
1. Multi touch (which basically denotes a capacitive screen)
2. Compass capability
poppinpengawen said:
http://wmpoweruser.com/?p=4332
here are 2 interesting ones
1. Multi touch (which basically denotes a capacitive screen)
2. Compass capability
Click to expand...
Click to collapse
Styli are helpful for many Asian languages (winmo is courting Chinese markets as we speak), and capacitative styli are humongous. Perhaps the capacitative preference for winmo7 explains why winmo6.5 will coexist with it--so resistive screens can hang around and help capture Asian markets.
However, your link prefaces the list with "WM7 Chassis 1 Spec" (note the 3.5" minimum screen size), something that indicates there could be a "Chassis 2" etc.
poppinpengawen said:
here are 2 interesting ones
1. Multi touch (which basically denotes a capacitive screen)
2. Compass capability
Click to expand...
Click to collapse
As far as I know resistive touchscreens can support multi-touch and I hope WM7 does not require a capacitive touchscreen. Resistive is so much more functional (stylus handwriting recognition, less battery consumption, cheaper, etc.) And it saddens me that they are getting phased out due to all the iphone lovers out there.
sakshaug007 said:
As far as I know resistive touchscreens can support multi-touch and I hope WM7 does not require a capacitive touchscreen. Resistive is so much more functional (stylus handwriting recognition, less battery consumption, cheaper, etc.) And it saddens me that they are getting phased out due to all the iphone lovers out there.
Click to expand...
Click to collapse
link indicating the screen technology used in the Touch pro 2 can do multitouch?
crazy talk said:
link indicating the screen technology used in the Touch pro 2 can do multitouch?
Click to expand...
Click to collapse
stantums-mind-blowing-multitouch-interface-on-video/
As far as products actually on the market, multitouch does mean capacitative. But for the future, it doesn't have to stay that way.
fortunz said:
Styli are helpful for many Asian languages (winmo is courting Chinese markets as we speak), and capacitative styli are humongous. Perhaps the capacitative preference for winmo7 explains why winmo6.5 will coexist with it--so resistive screens can hang around and help capture Asian markets.
However, your link prefaces the list with "WM7 Chassis 1 Spec" (note the 3.5" minimum screen size), something that indicates there could be a "Chassis 2" etc.
Click to expand...
Click to collapse
oh yea, I completely agree with you. I don't see why it isn't possible to just fuse the features of a resistive screen and a capacitive screen together. there's a video (can't remember where I found it...it was somewhere on xda-developers) that shows a resistive screen with multi-touch capability. so that alone shows that it IS possible to have a multi-touch resistive screen. (now that I think about it, it sorta makes sense why the document says "multi-touch" and not simply "capacitive" )
and I have no doubt that there will be a chassis 2. from what I hear, the chassis 1 is being considered Microsoft's "Pink" smartphone. so there's no doubt that the upcoming devices running WM7 will have bigger screens and more hardware, etc.
That video is in linked in the post above yours.
The techs are different, and there will likely always be some tradeoffs. There will never be a complete melding of the two, but some of the biggest concerns can be addressed.
fortunz said:
stantums-mind-blowing-multitouch-interface-on-video/
As far as products actually on the market, multitouch does mean capacitative. But for the future, it doesn't have to stay that way.
Click to expand...
Click to collapse
i knew about that.
what i was trying to say was proof the exact screen in the Tp2 can support multi touch. because that was what the person i was replying to was implying.
crazy talk said:
i knew about that.
what i was trying to say was proof the exact screen in the Tp2 can support multi touch. because that was what the person i was replying to was implying.
Click to expand...
Click to collapse
sakshaug007 said:
As far as I know resistive touchscreens can support multi-touch and I hope WM7 does not require a capacitive touchscreen.
Click to expand...
Click to collapse
He said resistive touchscreen can support multitouch. They can. I guess we all agree with each other. Big hugs, all around.
But we don't have the answer yet
Does the Touch Pro 2 have a resistive screen that can handle multitouch or not ...
The video using resistive screen for multitouch uses special hardware chips to handle that.
TP2 does not, AFAIK.
Here's a detailed breakdown on what exactly was learned from the video that Hamburg's referring to.
Seems to me that, technically, WM7 won't be available for the TP2, but we all know there'll be some builds cooked up here that'll work at some point in the future
Technically capable or not I don't think there will be an official upgrade available. In an interview with someone with HTC they said that the upgrade to 6.5 was being done because Microsoft had said they would provide the rights for the free upgrade. I doubt Microsoft would provide two free upgrade rights for the same phone,, and I doubt HTC would shell out the cash necessary to provide a second update either. So in the end, it'd require a cooked ROM. Good thing though is the fact that in one of the many articles around it said the processor would need to be ARMv6, which the Pro2's is.
Related
N900 seems superior to the TP2 in every way except the keyboard, is anyone else thinking about getting an n900? 5 megapixel camera with dual led flash, decent keyboard, fast processor, great multimedia capabilities, upnp, 32gb built in with sd expansion... what does the touch pro 2 have over it?
RTbar said:
... what does the touch pro 2 have over it?
Click to expand...
Click to collapse
The N900 seems like a nice phone, but I prefer the stylus, hand writing recognition, windows mobile, and XDA support that the TP2 has to offer.
I got a TP2, waiting to get N900 when it's release. Do what I do, then you wont have to decide between 2 phones lol.
Agree with sakshaug007
Strange...
Coming to an HTC specialized forum like XDA to say that n900 is better?
Don't really think so...it has symbian on it...
TP2 with WM is just great!
orb3000 said:
Agree with sakshaug007
Strange...
Coming to an HTC specialized forum like XDA to say that n900 is better?
Don't really think so...it has symbian on it...
TP2 with WM is just great!
Click to expand...
Click to collapse
no symbian... maemo... and my father has a TP2 which I've been customizing for him and playing with and I agree it's an awesome phone. I wouldn't mind having either one, but the N900 clearly has superior hardware except for keyboard
ok maemo whatever, is not WM...
And hardware keyboard is more than enough to go for it!
Sorry, I got to say that these "this versus that" topics are useless. Don't let a couple of forum users sway your opinion. There are numerous text/video reviews of the TP2. And when the N900 releases, it will receive the same treatment from reviewers. Make your own decision based on your needs and preferences.
And forget specs. Just check out that monstrosity that Toshiba made (TG01).
For me TP2 is a better choice than Nokia. The large touchscreen, qwerty keyboard. And I got diamond 2. I like it very much. So if I have to choose one, I'd get HTC. I even don't know how to change message tones on n900.
The deciding fact is people themselves not the phones.
I will definitely get the N900 once it's released in the US and after the initial price drop. The TP2 will be my back up phone.
Maemo (true Linux OS) + faster processor (OMAP3) + more RAM (256MB & 768MB virtual) + more space (32GB) + better camera
i prefer tp2
tp2 is my choice
I had a N800, and I think the major problems with it were lack of developers and the high price tag for the N810. Maybe the N900 will spur new Maemo growth with subsidized prices, but the MSRP needs to go down a lot. It's fun to be able to run Debian on a mobile device, just not all that useful at the end of the day (for me, at least).
Other than that, I think we can all agree that the TP2 needs a better camera and flash.
True, the TP2 is lacking, but the N900 won't have 3G in the States, I believe, not that there's a lot out available anyways...
whatledog said:
True, the TP2 is lacking, but the N900 won't have 3G in the States, I believe, not that there's a lot out available anyways...
Click to expand...
Click to collapse
It has T-mobile 3g bands
RTbar said:
It has T-mobile 3g bands
Click to expand...
Click to collapse
Yeap and it's just perfect for me
I think both are great "phones", so everyone needs to decide for themselves. That having siad: it has been stated on a website (fprgot the URTL) that the N900 only has landscape view and no portrait. If that is true, then the N900 is not a real replacement/competito to the TP2
kuzibri said:
I think both are great "phones", so everyone needs to decide for themselves. That having siad: it has been stated on a website (fprgot the URTL) that the N900 only has landscape view and no portrait. If that is true, then the N900 is not a real replacement/competito to the TP2
Click to expand...
Click to collapse
I haven't heard that, but even the N800/N810 could do rotation through a switching app (through a kernel hack). And I thought the N900 was supposed to have an accelerometer. It worked quite well on the N8x even without one...
I think a lot of features for the n900 are forthcoming, they just wanted to release it asap... as far as rotation they said that devs are free to include it into their apps, weather it is integrated on the ui level remains to be seen.
Two things concern me though, the lack of buttons which the tp2 has, and the lack of XDA support... I don't know how talented the maemo developers are but I don't imagine they are as good as some of the guys here... time will tell
the standard view of the N900 is landscape, so you need (extra) software to rotate it to portrait, which is IMHO cumbersome.
For the rest I agree with RTbar
orb3000 said:
ok maemo whatever, is not WM...
And hardware keyboard is more than enough to go for it!
Click to expand...
Click to collapse
orb3000 said:
Agree with sakshaug007
Strange...
Coming to an HTC specialized forum like XDA to say that n900 is better?
Don't really think so...it has symbian on it...
TP2 with WM is just great!
Click to expand...
Click to collapse
You are assuming that everyone is as much a wm fanboy as yourself. We get that your pro wm but to say that he cant come into an htc forum and tell hem what he can and cant say....Thats just being thick and limited on your part. What do you think of Android on HTC phones!? Go to the Hero section and say that too then.
ohyeahar said:
Sorry, I got to say that these "this versus that" topics are useless. Don't let a couple of forum users sway your opinion. There are numerous text/video reviews of the TP2. And when the N900 releases, it will receive the same treatment from reviewers. Make your own decision based on your needs and preferences.
And forget specs. Just check out that monstrosity that Toshiba made (TG01).
Click to expand...
Click to collapse
Why would these topics be useless. He is a asking a legitamate question. He is torn between phones and asking knowledgeable community what they think. Many others may be on the fence about which phone to get.
Also I see that when asked about specs on the tp2 (which are ****) the common tp2 enthusiasts defensive is to compare a device loaded with specs but **** on gui like the TG01. Come on, like that is the only device that is has better specs as yet. Check out the B7610 omnia pro.
@ ORB Stop being so limited, Its competition. You want other phones to be better to increase competition, hence HTC will keep pumping out phones that are better and better. IE nvidia v. ATI. SEE QUOTE not directed at PILOT
-PiLoT- said:
okay
A, orb3000, we all know this is a htc forum, but we still like to be kept abreast of the latest technology, we want people like newforce to post this type of news as it gives us an idea of what hardware other manufacterers are putting in the devices
so when u write "Not of much interest here as we dedicate to HTC devices only", this just isnt true as we want this type of info to keep us clued in.
just because this is a htc devices forum doesnt mean we dont want people to contirbute news on other hardware.
B, NewForce, this is and always has been a htc device thread and its not changing anytime soon
but like i said above posts can be made on other hardware models unless its a post asking for a forum
Click to expand...
Click to collapse
Well, looking at all the current mobile OS's,
looks like i will stay with good old WM6.x for a long time.
- I want to listen to music and do something else - 1GH CPU for 1 single task? *gggg*
- I give a **** on multitouch - It's just a hype and makes handling worse...
I want to use my device with one hand!
Scrolling through a list with 20 pages? I praise the scrollbar!!
- I need simple and just working tethering
- I want to take and sync notes
- Capacitive screen? Forget it!
Come on, i've tried it an its a lot more inaccurate, then any resistive screen i know.
Same hype as multitouch...
- etc,etc,etc
I'm really wondering where the development goes - more and more eyecandy...
just my 2cents
ReflexNPG said:
Well, looking at all the current mobile OS's,
looks like i will stay with good old WM6.x for a long time.
- I want to listen to music and do something else - 1GH CPU for 1 single task? *gggg*
- I give a **** on multitouch - It's just a hype and makes handling worse...
I want to use my device with one hand!
Scrolling through a list with 20 pages? I praise the scrollbar!!
- I need simple and just working tethering
- I want to take and sync notes
- Capacitive screen? Forget it!
Come on, i've tried it an its a lot more inaccurate, then any resistive screen i know.
Same hype as multitouch...
- etc,etc,etc
I'm really wondering where the development goes - more and more eyecandy...
just my 2cents
Click to expand...
Click to collapse
i think you're wrong about most of what you typed. WM does have multitasking just not the way you're used to...hell if you check some of my other posts...you'll see it. scroll bars are useless with kinetic scrolling. Capacitive screens allow for more accurate sure presses. You gotta get past the simple and embrace something new. It might be something better but you won't know unless you try...but by all means stick it out with 6.5.3 its awesome in its own right. You just shouldn't bash till you see a finished copy..I could be wrong
~style~
Check this article. Straight from the designer. We really have to wait for MIX to see for sure, but it all depends on the implementation.
ReflexNPG said:
- I give a **** on multitouch - It's just a hype and makes handling worse...
I want to use my device with one hand!
Scrolling through a list with 20 pages? I praise the scrollbar!!
Click to expand...
Click to collapse
Multitouch doesn't impress me either.
I use real paper and paint for fingerpainting.
Don't panic and stay calm!
http://forum.xda-developers.com/showthread.php?t=633571
From this you can see, that it's based on WinCE 7.0. So it's multi-task-able.
If there would not be "multi-taks" by default, i bet xda-gurus will bring a path to make it available
Another thing, that MS is a customer-oriented company. They make things that ppl buy, if ppl don't buy, they improve it
If they get feature request like "multi-tasking", they will implement it
style1 said:
i think you're wrong about most of what you typed. WM does have multitasking just not the way you're used to...hell if you check some of my other posts...you'll see it. scroll bars are useless with kinetic scrolling. Capacitive screens allow for more accurate sure presses. You gotta get past the simple and embrace something new. It might be something better but you won't know unless you try...but by all means stick it out with 6.5.3 its awesome in its own right. You just shouldn't bash till you see a finished copy..I could be wrong
~style~
Click to expand...
Click to collapse
capacitive screens allow for more accurate presses?
ur an idiot...
style1 said:
i think you're wrong about most of what you typed. .
Click to expand...
Click to collapse
maybe, but thats my opinion & experience - i type with my nail (impossible on cs) and now please tell me which cs device is more accurate?
All implementations of kinetic "eye candy" scrolling i know, are bad in some way. They are inaccurate, laggy or both There is no indication where in the list i am located -> See all the guys rubbing their fingers 2 or 3 times on the screen, just to understand "oh i'm at the end"?
Ok, it will have some kind of multitasking - but i will depend on the folks of xda to make mortscript or autohotkey to work
Maybe you should rethink about your position: Not every new thing is good for the customer...
For example: Compact disc, DVB-x (T,S,C), flat screens, audio downloads with DRM ...
The core operating system is a modern multitasking operating system. If you play music for example, the music will play back as you navigate around the experience...if you're using email, we have great support for push email and that happens in the background.
For third party applications—we'll get into a lot more detail on this in MIX—but we have a few ways we're going to make sure that third parties can bring their value to the user even when the app is not running. Live tiles are an example. Data feeds in the hubs are another example for some apps.
http://pocketnow.com/software-1/mwc-can-windows-phone-7-series-multitask
Click to expand...
Click to collapse
What i think about is a bit more complicated. The OS Does support Multitasking i guess but we will not need to keep the apps running in the background. if the application needs to wait for something to work, it will notify the OS what to look for and once it happens the OS will start the required app.
Makes sense doesn't it? this will give more than just multi tasking capability to the devices without the need of wasting RAM for background processes or apps that wait for something to happen.
jug6ernaut said:
ur an idiot...
Click to expand...
Click to collapse
It will be some "iPhone style" of multitasking, but it's crappy in my opinion - http://pockethacks.com/what-about-multitasking-in-windows-phone-7-series/
micro$oft really took HUGE steps back with this. no multitasking, no flash, no copy/paste, no customizing. yeah im not digging this at all. ill stick with my hero.
jug6ernaut said:
capacitive screens allow for more accurate presses?
ur an idiot...
Click to expand...
Click to collapse
Hardly even called for, one would figure with your post count you would understand basic forum rules about flaming but I guess thats non sequitur. Either way I guess I should just go off spouting at the fingers without qualifying or justifying what I'm really trying to say. 'Accurate presses' meaning I don't have to continuously tap the screen 2-3 times just to get a simple press as I have to do currently with my Acer and have had to do with my previous HTC. Miss types are bound to happen and thats true but there are many cases when I'll tap the screen and wont get a response because the resistive touch screen uses pressure to sense where you press, more accurate presses stems from the technology of capacitive screens themselves being that you don't actually require pressure to operate the screen leading to less miss types. I'm not trying to offend you or anyone else, I'm really just making debate as this is the biggest thing to happen to Windows mobile since its creation. I'll fade back to the shadows...you guys carry on, I'll lurk..lol
~style~
EDIT"no multitasking, no flash, no copy/paste, no customizing..." please be prepared to offer some sort of proof to this... The Reps were saying that copy and paste had not be optimized yet...meaning it had not be implemented into the build at that stage. Multitasking is in fact part of the OS, Flash has been announced as not being included at launch but will be added...and customizing....really??? So do people honestly believe that Samsung, HTC, ASUS, Acer, Toshiba, Garmin, etc all plan on just releasing the EXACT SAME PHONE WITH NO DIFFERENCES? of course there will be customizing or else M$ could have just released the phone themselves and made all the profit similar to apple
I think the push notification system is god awful. Lets take irc for example. I want to keep that running in the background but it REQUIRES a persistent connection and the app to reply to pings and ctcp's etc. So i sell my irc app for x dollars to the customer. In order to give them a good experience i have to either 1: Supply them with a list of free bnc servers, 2 add a subscription so i can host a server to keep the app supplied with info when it wakes up, or 3. incur a cost greater than what i sell the app for in order for people o not be pissed.
Microsoft definitely listened to the people when they made this. Just the wrong people. People that don't use winmo. All the hate that wino got has been rectified and now the people who were enthusiastic about winmo aren't very happy.
My next phone provided microsoft dosen't get its act together will be a Meizu m8, a china ohone running a skinned version of wince, a Bada phone, android or symbian. EVEN SYMBIAN DIDNT DECIDE TO SCREW AROUND WITH ITS EXISTING FANBASE. Iphone is not an option, I just personaly hate them more than google.
ok my last post...I promise...its a long look at windows phone 7 enjoy
~style~
style1 said:
Hardly even called for, one would figure with your post count you would understand basic forum rules about flaming but I guess thats non sequitur. Either way I guess I should just go off spouting at the fingers without qualifying or justifying what I'm really trying to say. 'Accurate presses' meaning I don't have to continuously tap the screen 2-3 times just to get a simple press as I have to do currently with my Acer and have had to do with my previous HTC. Miss types are bound to happen and thats true but there are many cases when I'll tap the screen and wont get a response because the resistive touch screen uses pressure to sense where you press, more accurate presses stems from the technology of capacitive screens themselves being that you don't actually require pressure to operate the screen leading to less miss types. I'm not trying to offend you or anyone else, I'm really just making debate as this is the biggest thing to happen to Windows mobile since its creation. I'll fade back to the shadows...you guys carry on, I'll lurk..lol
~style~
EDIT"no multitasking, no flash, no copy/paste, no customizing..." please be prepared to offer some sort of proof to this... The Reps were saying that copy and paste had not be optimized yet...meaning it had not be implemented into the build at that stage. Multitasking is in fact part of the OS, Flash has been announced as not being included at launch but will be added...and customizing....really??? So do people honestly believe that Samsung, HTC, ASUS, Acer, Toshiba, Garmin, etc all plan on just releasing the EXACT SAME PHONE WITH NO DIFFERENCES? of course there will be customizing or else M$ could have just released the phone themselves and made all the profit similar to apple
Click to expand...
Click to collapse
well no offence to u also but u are 100% wrong.
resistive is easilly more accurate honestly u cant even compare them. what ur referring to is the software which is made for capacitive screens...made for the less accurate screens....
while i understand ur opinion around capacitive screens u have a very bad understanding of how capacitive/resistive screens and the relative software works and how its differinciated.
style1 said:
'Accurate presses' meaning I don't have to continuously tap the screen 2-3 times just to get a simple press as I have to do currently with my Acer and have had to do with my previous HTC.
Click to expand...
Click to collapse
sorry, but this is simply not true: all my phones never missed a touch (Blackstone, Trinity, Magician). Maybe its cause you are not using your nail?
Now just watch the windows 7 video:http://channel9.msdn.com/posts/LauraFoy/First-Look-Windows-Phone-7-Series-Hands-on-Demo/
1. scene (3. min) the guy tries to scroll down - ups does not work - again. And this is what i hate about capacitive "swish swish UI's".
Its a waste of time - every second.
I'm happy with Pocket Plus and Pocket Breeze on my today screen!
lol.. I have no idea how I keep getting drawn back into this..but I guess I shouldn't waste time trying to clarify I'll just redefine since we obviously sit at on different sides of the fence here...Let me just try again. Capacitive screens are more RESPONSIVE to the touch than are resistive touch screens. I guess that would be the better way to put it. There really is no arguing this point, when I said accurate earlier i mean it as they screen registering what is being done to it and reacting accordingly. And yes, the video walk through with Laura Foy had its UI hickups but its unoptimized software running on a prototype unit (ASUS) its not like they are walking around touting it as a finished product read to ship...They are projecting to ship by the "holiday's" so we have 7-9 months before they will be shipping. I don't know what else to say.
Also in clarification, as to mistouches on resistive touch screens, I don't type with a nail or stylus I use my finger to press the key and I expect that the phone itself will understand what is happening and respond accordingly. I have epic, and I mean EPIC fails on my resistive touch screen. Why? not because I got fat fingers (which I don't) but because the screen isn't sensitive enough.
Since jug6ernaut believes I'm borderline retarded...I guess I'll drop some knowledge. Resistive touch screen works by using 2 or more electrically charged layers with a gap between them. When you press the screen down the first layer fills the gap and touches the second layer thereby causing and electrically event registered as a press. Yes it is more accurate in the sense that you can touch it with a stylus and it will press exactly where you point, but if you press the screen and the two layers don't touch its isn't registered as a press, thereby creating missed presses on the screen. This isn't just some crap that affects only windows its ALL RESISTIVE screens...so if you've never ever mistyped then you are in a very small minority. It has nothing to do with software...its all HARDWARE.
Capacitive screens on the otherhand when they fail it can be attributed to software because unlike Resistive screens, capacitive is just glass coated with an invisible conductor...since we also conduct electricity anytime we touch the screen it distorts the level of capacitance (its a word) thereby registering as a touch. The electricity however has to run through software created by developers to read and understand how that touch related to the UI and software.
But what do I know....Hell I only do this for a living...lol. Anyway I'm not trying to pick a fight with any of you. Just trying to separate fact and fiction.
~style~
Capacitive screens are more RESPONSIVE to the touch than are resistive touch screens. I guess that would be the better way to put it.
Click to expand...
Click to collapse
Yep. Because they are definitely less accurate. More responsive but less accurate.
I'm looking forward to the WP7 approach. The big pain in using WM and it's predecessors for the past 15+ years is that it's slow and hangs a lot. I'll trade all those years of waiting for a WM device to respond for a fast, responsive interface. All I really need is smooth app switching...not multi-tasking.
I like the new approach. Finally, speed comes first.
I've used resistive screens for most of my life - had Sharp Zauruses, Sony Clies, Kaiser, Pro2, Xperia. The Pro2 has the best resistive screen that I've used.
Around a week ago I got an HD2, and honestly, the capacitive screen is a fantastic improvement!
The vast majority of people would agree that capacitive is far superior in terms of feel. It may be less accurate in some ways, but as long as the software is designed well, this shouldn't be a big problem, and there are many benefits to it (light touch, multi touch, flat screen which you can use as a mirror, nice look & feel of glass).
Multi touch can be implemented as a gimmick, but can also be very useful and add a new dynamic to controlling software via a touch screen (e.g. google earth on Ipod/Iphone).
Anyhow, I'm looking forward to seeing how Windows Phone 7 turns out - I'm reserving my judgements until I can try it, and see how easy it is for people to customise it.
http://pocketnow.com/rumor/windows-phone-7-series-for-htc-hd2-more-proof
"Can Adobe clarify the roadmap for Android and Windows Mobile? Based on what was announced in February and June I was expecting some alpha release during MAX and had planned for that. The announcement at MAX there was to be some preview release in December together with the Open Screen Project partners was unfortunate, but no big problem.. Unfortunately that preview release did not materialize and 2009 has passed. Mobile Flash is different from the regular Flash in that I can not get my developers to just install it on the hardware they have, I need to get funding for new phones, acquire them etc. Budgets do not come overnight, so the sooner Adobe can provide us with a clear roadmap the better.
What I need to know is:
- what will be the first Android phone for which a Flash Player 10.1 alpha/preview will be released?
- what will be the first Windows Mobile phone for which a Flash Player 10.1 alpha/preview will be released?
- When?
To that, the Adobe rep replies:
We're waiting for OS updates from Google and Microsoft before we can distribute a Flash Player Beta. We expect this to happen early this year. Thank you for your patience!
The first Android devices that will support Flash Player are the Droid and Nexus One. The first WinMo device will be the HTC HD2.
And in another reply, the Adobe rep mentions:
You can expect the final release for Android to be available mid-year. All Android devices that meet our minimum s/w and h/w requirements will be supported. Unfortunately, I cannot say a lot more publicly about our port to the Android platform at this time.
As for WinMo, we have made the tough decision to defer support for that platform until WinMo7. This is due to the fact that WinMo6.5 does not support some of the critical APIs that we need.
So wait a sec - if Adobe isn't adding flash to Windows Phone until version 7, and the HD2 will be the first device to have it, doesn't this mean that the HD2 will run Windows Phone 7 Series? Connecting the dots, this seems to be the case."
So what do you guys think????
UPDATE
http://wmpoweruser.com/?p=13719
Whilst Microsoft may have previously said there were no current devices that were WP7 capable, they may well just have reversed that.
It’s early days yet, and that’s really for our hardware partners to think about.
I cannot think any reason why HD2 cannot use Windows Phone 7 Series.
All minimum requirements are met, except HD2 has 5 buttons while the requirement is only 3 buttons.
That would be OK, there will be 2 buttons unused or even better they can be mapped to certain functionality.
But then it depends on HTC to make it happen .... or XDA gurus here
I also think this will be answered next month during MIX10.
All minimum requirements are met, except HD2 has 5 buttons while the requirement is only 3 buttons.
Click to expand...
Click to collapse
lol... it's minimum three buttons of course.
I remain skeptical for several reasons regarding the Win Phone 7 minimum specs;
1. The phone must have back, search and home keys, and the HD2 lacks the search key, as well as the other two having incorrect legend (it might be possible to use the Windows key as the search key though)
2. The phone must have camera and power keys, one of which the HD2 lacks
3. The screen has to be able to register four simultaneous finger-presses, which the HD2 cannot do
4. The phone must have a forward-facing camera, which the HD2 does not have
5. There are not supposed to be any other keys, but the HD2 has two phone keys and volume keys
Aside from any possible key mapping, which I suspect Microsoft wouldn't be happy with, the other points lead to a deal-breaking condition.
I can't see how the HD2 would cope with the lack of four-point fingerpress recognition, although I'm not too sure when that would be used other than during two-handed typing using two fingers from each hand?
EDIT: If Microsoft do allow key mapping, then I guess the right-hand phone key could be POWER, and the left-hand one might be the CAMERA button.
Jim Coleman said:
I remain skeptical for several reasons regarding the Win Phone 7 minimum specs;
1. The phone must have back, search and home keys, and the HD2 lacks the search key, as well as the other two having incorrect legend (it might be possible to use the Windows key as the search key though)
2. The phone must have camera and power keys, one of which the HD2 lacks
3. The screen has to be able to register four simultaneous finger-presses, which the HD2 cannot do
4. The phone must have a forward-facing camera, which the HD2 does not have
5. There are not supposed to be any other keys, but the HD2 has two phone keys and volume keys
Aside from any possible key mapping, which I suspect Microsoft wouldn't be happy with, the other points lead to a deal-breaking condition.
I can't see how the HD2 would cope with the lack of four-point fingerpress recognition, although I'm not too sure when that would be used other than during two-handed typing using two fingers from each hand?
EDIT: If Microsoft do allow key mapping, then I guess the right-hand phone key could be POWER, and the left-hand one might be the CAMERA button.
Click to expand...
Click to collapse
I doubt what's on the keys is going to be a deal-breaker. I mean, MS want people to use this new OS, and HD2 users aren't going to go and buy a new phone for it (in 98% of cases). So I can't see what harm it would do (to either MS or HTC) to bend these stupid marketing rules for existing WM7-capable phones.
Yupe 5 is more than 3, are you happy?
I want to buy HD2 to replace my HTC Kaiser, but I would wait something new from HTC (HD3? *yummy*).
In the meantime, I am playing with Android on HTC Kaiser.
freyberry said:
lol... it's minimum three buttons of course.
Click to expand...
Click to collapse
guys you seriously missing the point adobe have stated that hd2 is going to have windows mobile 7 and all you can do discuss the 5 button problem lol. ive seen a demo of hd2 with flash working on 6.5 so maybe theyve delayed it for 7 because windows 7 utilises the hardware better?
yustheman said:
http://pocketnow.com/rumor/windows-phone-7-series-for-htc-hd2-more-proof
[cut]
To that, the Adobe rep replies:
We're waiting for OS updates from Google and Microsoft before we can distribute a Flash Player Beta. We expect this to happen early this year. Thank you for your patience!
The first Android devices that will support Flash Player are the Droid and Nexus One. The first WinMo device will be the HTC HD2.
And in another reply, the Adobe rep mentions:
You can expect the final release for Android to be available mid-year. All Android devices that meet our minimum s/w and h/w requirements will be supported. Unfortunately, I cannot say a lot more publicly about our port to the Android platform at this time.
As for WinMo, we have made the tough decision to defer support for that platform until WinMo7. This is due to the fact that WinMo6.5 does not support some of the critical APIs that we need.
Click to expand...
Click to collapse
This is why I hate Internet rumours; people never bother to think.
The two posts being referred to in the Adobe forum are more than a month apart. It's obvious that the decision not to issue a version of FlashPlayer for WM6 was taken during that one month gap.
When the guy posted back in early January, they were still intending to release a version for WM6.5; at that point the plan was that the HD2 would be the first WM6.5 phone able to run it.
By early February they had changed their plans; having discovered that WM6.5 lacks certain crucial API's they decided to cancel the release of FlashPlayer for Windows Mobile altogether, and not release anything for a Microsoft platform until WP7 is available.
There is no logical connection between the HD2 and WP7 there; the two things feature in entirely different plans.
What Shasarak said.
THINK if you have read correctly what i have written than you would understand ive seen a demo of HD2 running flash infact heres a video http://www.adobe.com/devnet/flashplayer/articles/mobile_demos_fp10.1/popup13.html
the video clearly shows hd2 with 6.5 working with flash so the api bulls*** is rubbish. Even if it was the case that there was some API missing Adobe could have included in the software?????
yustheman said:
THINK
Click to expand...
Click to collapse
My anger wasn't directed at you, it was directed at the idiots at pocketnow who lack basic comprehension skills.
yustheman said:
if you have read correctly what i have written than you would understand ive seen a demo of HD2 running flash infact heres a video http://www.adobe.com/devnet/flashplayer/articles/mobile_demos_fp10.1/popup13.html
the video clearly shows hd2 with 6.5 working with flash so the api bulls*** is rubbish. Even if it was the case that there was some API missing Adobe could have included in the software?????
Click to expand...
Click to collapse
Well, there are two possibilities, there. One is that the so-called Adobe rep quoted at pocketnow doesn't what know what the f*ck he's talking about, in which case speculating about WP7 appearing on the HD2 on the basis of what he says is clearly entirely pointless; the other is that the rep does know what he is talking about, and that what you saw was an alpha version with support for only a subset of Flash functions, and that there will now never be a finished version because some of the missing features require api's that WM6.5 doesn't have.
Shasarak said:
My anger wasn't directed at you, it was directed at the idiots at pocketnow who lack basic comprehension skills.
Well, there are two possibilities, there. One is that the so-called Adobe rep quoted at pocketnow doesn't what know what the f*ck he's talking about, in which case speculating about WP7 appearing on the HD2 on the basis of what he says is clearly entirely pointless; the other is that the rep does know what he is talking about, and that what you saw was an alpha version with support for only a subset of Flash functions, and that there will now never be a finished version because some of the missing features require api's that WM6.5 doesn't have.
Click to expand...
Click to collapse
My apologies........
Jim Coleman said:
3. The screen has to be able to register four simultaneous finger-presses, which the HD2 cannot do
4. The phone must have a forward-facing camera, which the HD2 does not have
Click to expand...
Click to collapse
#3 is a software adjustment. The hardware itself is capable.
I haven't seen #4 listed as a requirement anywhere. Reference? They didn't sound like they were pushing video-calling at all. I don't even think their reference model had a forward-facing camera.
#4 is not a reqiurement
#5 is wrong as well, of course there may be other keys (like send & end)
The search and camera keys are required for new devices, but not a reason not to provide an upgrade.
What I can say is, an official upgrade is possible and seemed very likely from what I've heard some time ago (I can't reveal more, you have to trust me) but the last I've heard was that it's getting increasingly unlikely (lots of politics there...). I expect an official announcement of their decision when it launches in the US.
Right now, it's a waiting game and we can only hope...
And please, don't ask me, that's all I can say.
Seems like the majority of the blogs/sites don't think before posting (or just do it to generate traffic). At least MTW questioned the "realness" of the stuff: http://www.mobiletechworld.com/2010...-1-support-for-windows-mobile-6-5-wait-a-sec/
And how the **** did Pocketnow see any hint/connection with a WP7 update for the HD2 is beyond me.
MasterTP said:
At least MTW questioned the "realness" of the stuff: http://www.mobiletechworld.com/2010...-1-support-for-windows-mobile-6-5-wait-a-sec/
Click to expand...
Click to collapse
My working hypothesis today is that Adobe has indeed cancelled any plans to release Flashplayer for WM6.x, but that they are lying about their reasons for doing so. Happy to be corrected on any point if there is conflicting evidence, naturally.
We've seen Flash 10.1 running on WM6.5, so their statement about missing APIs is clearly a lie.
freyberry said:
We've seen Flash 10.1 running on WM6.5, so their statement about missing APIs is clearly a lie.
Click to expand...
Click to collapse
Well, we don't know that every feature of Flash was supported, and we certainly don't know that every feature was supported at an acceptable level of performance.
Seriously, do you think they would have developed it for months if they could have known from the beginning that it would not work?
It was almost ready. They've shown it on video. At that state, you normally know about the APIs you need. Plus, WP7 will offer even less APIs.
Their answer is nonsense. I'm sure they're lying.
Flash is dead.
HTML5 is the new way.
EOS().
http://apcmag.com/microsoft-no-windows-phone-7-upgrade-for-windows-mobile-6x-devices.htm
Owners of HTC’s highly-praised HD2 touchscreen smartphone will be unable to upgrade the device to Microsoft’s new Windows Phone 7 software when the OS is released towards the end of the year.
Despite the HD2 meeting many of the criteria laid down in Microsoft’s ‘Chassis 1’ spec – including a 1GHz Qualcomm processor, high-res capacitive touch display, 5 megapixel camera and 3.5mm headphone jack – the phone will be ruled out for the simple reason that it has five buttons instead of the three mandated for all Windows Phone 7 devices.
That’s the official line from Microsoft, at any rate. Natasha Kwan, General Manager for Microsoft’s Mobile Communications Business in the Asia-Pacific region, told APC that the HD2 “doesn’t qualify because it doesn’t have the three buttons”.
At least officially, but un-officially I would bet that some gurus from XDA-dev will make it happen ... when the WP7S is available end of this year. They should be able to get the ROM and port it to HD2. That's my feeling.
And there is still hope this will be negated on the next MIX10 .... Microsoft will say "That's not true, HD2 is upgradeable to WP7S and here is the beta ROM you can put and test"
This .. its just... don't have words 4 this..
Now its all up to the devs..
That well and truly Sux ....
But i have very little to worry about
We're at XDA's !!!!!!!!
gogol said:
At least officially, but un-officially I would bet that some gurus from XDA-dev will make it happen ... when the WP7S is available end of this year. They should be able to get the ROM and port it to HD2. That's my feeling.
Click to expand...
Click to collapse
Well, as has been pointed out in many other threads, producing a cooked ROM based on a new CE kernel is a completely different proposition from porting between different versions of WM5 and 6. Whether we see a cooked HD2 ROM based on WP7 is pretty much entirely dependent on three things:
1) There needs to be a beta WP7 ROM for the HD2 produced by Microsoft and/or HTC. (Evidence that this exists is strong, but not absolutely conclusive).
2) The beta version has to be recent enough that there is no change to the driver architecture between it and the released version.
3) The beta has to be leaked.
IMO, the last of those is not by any means guaranteed this time round.
I hardly think that because the HD2 has 2 extra buttons this would prevent WP7S from running on it! Seriously, who are they trying to kid?
Hmm, there's some more stuff in the linked article that the original poster doesn't quote:
There could be more to this than just the sin of having two buttons too many, however: Tony Wilkinson, Business Operations Director for Microsoft Australia, told APC that “there are some hardware components that the HD doesn’t have”.
We’re not sure what those are because Microsoft has not revealed its complete recipe for Windows Phone 7 devices – that’s due to take place at this month’s MIX developer conference in Las Vegas – but we’ve heard that a pixel-pushing graphics chip might be on the checklist.
Click to expand...
Click to collapse
Assuming that it's not just a matter of buttons, I'd say that makes even an unofficial HD2 port a bit less likely, but we'll see.
Completely understood.
We could wait that ROM anyway, whether leaked or come from official WP7S phone later this year or God knows where.
There are many amazing things which were unthinkable done by XDA devs here. They just too many to mention here ... HTC Kaiser missing drivers, WM6.5 on <insert HTC devices>, Android on WM, etc.
Even if it could not be done, but having HOPE is not a bad thing ...
However, certainly, this could potentially put a halt on HD2 sales.
Shasarak said:
Well, as has been pointed out in many other threads, producing a cooked ROM based on a new CE kernel is a completely different proposition from porting between different versions of WM5 and 6. Whether we see a cooked HD2 ROM based on WP7 is pretty much entirely dependent on three things:
1) There needs to be a beta WP7 ROM for the HD2 produced by Microsoft and/or HTC. (Evidence that this exists is strong, but not absolutely conclusive).
2) The beta version has to be recent enough that there is no change to the driver architecture between it and the released version.
3) The beta has to be leaked.
IMO, the last of those is not by any means guaranteed this time round.
Click to expand...
Click to collapse
Ruudfood said:
I hardly think that because the HD2 has 2 extra buttons this would prevent WP7S from running on it! Seriously, who are they trying to kid?
Click to expand...
Click to collapse
It could certainly be enough to prevent an official WP7 upgrade for the HD2, and we now have word from an actual Microsoft representative which suggeststhat this is indeed the case.
That reminds me, where's Freyberry? He owes a number of people a grovelling apology for insulting them when they suggested that the buttons on the HD2 might have an impact on WP7 availability....
gogol said:
Even if it could not be done, but having HOPE is not a bad thing ...
Click to expand...
Click to collapse
Having hope is a bad thing if anyone buys an HD2 because of that hope, only to have it proven unrealistic.
gogol said:
We could wait that ROM anyway, whether leaked or come from official WP7S phone later this year or God knows where.
Click to expand...
Click to collapse
A ROM from an official WP7S phone almost certainly wouldn't be adequate. Unless every single hardware component in it is identical to the HD2, you would still have no way of getting hold of the necessary drivers. So if, say, the camera in this phone wasn't the same as the one in the HD2, then it would be impossible to make a cooked WP7 HD2 ROM from it in which the camera works. The only way you could do it is if there is a group of official WP7S phones which between them contain every single component in the HD2 - not just the chipset but the camera, proximity sensor, touchscreen, everything.
I bet the "5 buttons" reason is a bad excuse to not having to reveal more info prior to MIX.
My guess that this reason is BS because of the announcement of LG's first WP7 phone, this is taken from the article about it on neowin:
The device sports a QWERTY slide-out keyboard as well as a touch screen and the three standard Windows Phone 7 prescribed buttons: back, home and search. Other buttons include power, camera and volume controls.
Click to expand...
Click to collapse
source:
http://www.neowin.net/news/microsoft-reveals-first-windows-phone-7-series-handset-from-lg
Obviously this phone has more buttons than the HD2 and will be running WP7.
Shasarak said:
It could certainly be enough to prevent an official WP7 upgrade for the HD2, and we now have word from an actual Microsoft representative which suggeststhat this is indeed the case.
That reminds me, where's Freyberry? He owes a number of people a grovelling apology for insulting them when they suggested that the buttons on the HD2 might have an impact on WP7 availability....
Click to expand...
Click to collapse
No comment on this he he he
Shasarak said:
Having hope is a bad thing if anyone buys an HD2 because of that hope, only to have it proven unrealistic.
Click to expand...
Click to collapse
You are correct, but I also said:
However, certainly, this could potentially put a halt on HD2 sales.
What I mean with hope is for "current owner" of HD2
Shasarak said:
A ROM from an official WP7S phone almost certainly wouldn't be adequate. Unless every single hardware component in it is identical to the HD2, you would still have no way of getting hold of the necessary drivers. So if, say, the camera in this phone wasn't the same as the one in the HD2, then it would be impossible to make a cooked WP7 HD2 ROM from it in which the camera works. The only way you could do it is if there is a group of official WP7S phones which between them contain every single component in the HD2 - not just the chipset but the camera, proximity sensor, touchscreen, everything.
Click to expand...
Click to collapse
Fully understand. But do you think all the hardware components would be exactly different?
Learning from past experience, most if not all past devices still have the same hardware components. That's why XDA can still port WM6.5 to some of old devices.
Why would suddenly the hardware is now totally differents?
Even if it is new hardware component, I would think it will be backward compatible with the old hardware.
Well, it could be that the new OS requires to use "new drivers format" for that "old hardware" (HD2) ...
That is quite obvious.
So, either the new WP7S devices are still using most the same hardware components, which means the WP7S drivers will be somehow backward compatible with old hardware.
Or, some super clever XDA dev will create new drivers for HD2 using new device driver format of WP7S. This sounds impossible, but .... who knows?
I won't believe any article until MIX. Especially an article which doesn't mention the HD2 in the quote
I see the words "current phones" and "HD", but no HD2 in there. But hey, I'm clutching at straws now really!
gogol said:
Or, some super clever XDA dev will create new drivers for HD2 using new device driver format of WP7S. This sounds impossible, but .... who knows?
Click to expand...
Click to collapse
New kernel, relatively new architecture will mean that it will be effectively like porting HD2 to Android...only with zero documentation.
reverse-engineering drivers? just look at the problems present in android-development... ^^ the problem is you need exact (!) specifications of the hardware to start with - and that's closed-source. even after that it's not easy.
but even IF some magician would pull this off, i have learned one thing with the x1: not having an official firmware adapted to the OS you want to use deprives you of a stable base, it will always be patchwork at best. (and i'm talking 6.1 -> 6.5 here, where the difference isn't that big)
I was going to buy a touch hd2 for 425 off craigslist with the complete idea that this phone would be wp7s. Seeing that it won't has left me stay with my reliable tp2...
its a shame actually I wanted the hd2 to be wp7s for obvious reasons
If this is true I will sell my hd2 soon!
I mean the buttons... its nothing but a lie, its not the true reason!
They could have told more early that the HD2 wont get an upgrade they just didnt because they want to sell it!
Then the "russian twitter" thing was only marketing to sell a phone with dead OS..
But I still don't realy believe this.. windows [email protected] told that "there 'may' be information next month".. well it is " next month" but the hd2 wasnt mentioned directly as far as I can see..
Cheers
If the buttons are the culprit, I bet the problem isn't the extra buttons, but lack of the Search button. Sure the Home one could be remapped, but what about consistency, ease of use for consumers etc.?
Blade0rz said:
I won't believe any article until MIX. Especially an article which doesn't mention the HD2 in the quote
I see the words "current phones" and "HD", but no HD2 in there. But hey, I'm clutching at straws now really!
New kernel, relatively new architecture will mean that it will be effectively like porting HD2 to Android...only with zero documentation.
Click to expand...
Click to collapse
Agreed, it looks like nothing is set in stone yet:
http://www.mobiletechworld.com/2010...-because-of-hardware-buttons-dont-be-so-sure/
chris5932 said:
I mean the buttons... its nothing but a lie, its not the true reason!
They could have told more early that the HD2 wont get an upgrade they just didnt because they want to sell it!
Click to expand...
Click to collapse
That would be a good reason for HTC not to offer the upgrade, but I don't see how Microsoft sells more WP7 licences by not allowing the HD2 to be upgraded. From Microsoft's perspective what matters is getting an absolutely consistent look-and-feel across all WP7 phones. So I find it plausible that Microsoft might refuse to sell HTC any licences to install WP7 on HD2's, given the lack of a search button.
I'm not giving up hope yet though. They've already announced the button requirement. If the HD2 was going to be disqualified for this reason why not say so? I don't think this is over. She's all the way on the other side of the planet from Redmond and most likely less 'in the know' just for this reason. Just this Saturday a much more knowledgeable MS rep said 'Wait for MIX' in regards to the HD2 getting an upgrade.
The statement leads me to believe that the MS rep in a far flung region is just interpreting the 3 button requirement to automatically mean that MS won't allow any current devices to get the upgrade and not them having actual info that the HD2 will specifically not get the upgrade. That and MS will need to get some sort of hardware in devs hands before official availability. An emulator is nice and all but real hardware is key. The HD2 is supposedly launching here in the States right after MIX. Coincidence? Maybe I'm just grasping at straws but fingers crossed nonetheless.
Shasarak said:
Well, as has been pointed out in many other threads, producing a cooked ROM based on a new CE kernel is a completely different proposition from porting between different versions of WM5 and 6. Whether we see a cooked HD2 ROM based on WP7 is pretty much entirely dependent on three things:
1) There needs to be a beta WP7 ROM for the HD2 produced by Microsoft and/or HTC. (Evidence that this exists is strong, but not absolutely conclusive).
2) The beta version has to be recent enough that there is no change to the driver architecture between it and the released version.
3) The beta has to be leaked.
IMO, the last of those is not by any means guaranteed this time round.
Click to expand...
Click to collapse
I think you're making some assumptions that aren't fair to make at this point in time. If the hardware is nearly identical to the HD2 (which it will be) why would it need an entirely new bootloader as compared to other WP7 devices? #2 (and therefore 3 as well) doesn't even make sense as they're developing this on CE. It's not like they're going to change CE versions mid-dev. The driver architecture won't change. MS has stated that they're doing all the driver dev, not the OEMs. As long as the HD2 matches the chassis specs, there's no reason it will need different drivers. The only thing that concerns me is the bootloader as it's my understanding that it's unique per device and likely a WM6 bootloader won't be able to boot WP7.
Shasarak said:
That would be a good reason for HTC not to offer the upgrade, but I don't see how Microsoft sells more WP7 licences by not allowing the HD2 to be upgraded. From Microsoft's perspective what matters is getting an absolutely consistent look-and-feel across all WP7 phones. So I find it plausible that Microsoft might refuse to sell HTC any licences to install WP7 on HD2's, given the lack of a search button.
Click to expand...
Click to collapse
Well I agree with most ppl here.. lets just wait til MIX..
There are severall things said that fight each other!
MS:"info for hd2 may next month","no upgrade for WinM 6.X phones"
HTC:"HD2 is able to run WP7's",
HTC twitter:"HD2 will get an upgrade" ..
I think the chances are still as before the article but make ur own guess.
Cheers
I wonder if microsoft is using some sort of qualcomm system on chip like there new MSM7x30 soc. As microsoft is only letting snapdragon devices, im sure they have a certain gpu that they have to use so the performance is the same on all handsets. so a SOC would make sense and that might be why the hd2 does not meet the specs.
Also i dont think the hd2 has 4 point multi touch.
Also i think microsoft wont let them upgrade as they wont 3 buttons only on the front so to let the hd2 have a upgrade on to wm7 makes a mockery of wm7 requirements.
Welcome all, just wanting to discuss some future plans after Apollo. As we know Apollo will definitely bring us up to speed with our competitors.
After Apollo is where MS must prevail bringing new intuitive hardware and software to Windows Phone. MS is going to have to be trend setters in the future to pursue the competition. It will be no more keeping up with the competition but exceeding the competition.
In what ways can MS push Windows Phone past the competition with intuitive hardware and software?
I will compile a list of everbodys ideas in this first post
My ideas
*Kinect gestures and speech as what they are bringing to the laptops.
*Wireless charging (beleivie Nokia is already working on this)
*Solar charging
Nicksti:
#1 More handset choices. For example, rumours are the SGS3 and the iPhone will be waterproof. Fujitsu makes a waterproof WP but it is not available globally. More choices like FFC, keyboards, bigger storage capacities, colours.
#2 More apps especially games.
#3 Improved notifications. Just throwing something out there, but maybe in style of the Windows Phone "get in get out" they should build a notification center which operates on the lock screen? I find it a little tedious to unlock my phone in order to interact with the notification center.
Sent from my Venue Pro using XDA Windows Phone 7 App
*a feature that will attract hot Latinas with the press of a button or tile*
prohibido_por_la_ley said:
*a feature that will attract hot Latinas with the press of a button or tile*
Click to expand...
Click to collapse
My ball and chain would kill me if I voted for this
#1 More handset choices. For example, rumours are the SGS3 and the iPhone will be waterproof. Fujitsu makes a waterproof WP but it is not available globally. More choices like FFC, keyboards, bigger storage capacities, colours.
#2 More apps especially games.
#3 Improved notifications. Just throwing something out there, but maybe in style of the Windows Phone "get in get out" they should build a notification center which operates on the lock screen? I find it a little tedious to unlock my phone in order to interact with the notification center.
some of the stuff you state I beleive will be coming, but what would be groundbreaking hardware/software that will catapult WP to the head of the game? Anroid made FFC and multi core a popular thing and peple look for that. What can WP implement to do the same?
937dytboi said:
some of the stuff you state I beleive will be coming, but what would be groundbreaking hardware/software that will catapult WP to the head of the game? Anroid made FFC and multi core a popular thing and peple look for that. What can WP implement to do the same?
Click to expand...
Click to collapse
Ecosystem and Integration is WP's thing. Speed, reliability and 'it just works' - on the side.
i wish a docking screen for my windows phone.
as we know, windows 8 will have tiles, and a desktop (win7 like) app.
so i have my mobile phone with wp8, dual core and 1gb ram. at home i connect my smartphone on a dockingstation/multimediastation, which turns my phone into a laptop or desktop pc.
similar like the motorola atrix:
http://techfokus.de/blog/wp-content/uploads/2011/09/motorola-atrix-2-lapdock-100.jpg
in short:
* docking my smartphone to a fully windows laptop*
Surprized no one mentioned Landscape startscreen when phone is turned.
nicksti said:
My ball and chain would kill me if I voted for this
#1 More handset choices. For example, rumours are the SGS3 and the iPhone will be waterproof. Fujitsu makes a waterproof WP but it is not available globally. More choices like FFC, keyboards, bigger storage capacities, colours.
#2 More apps especially games.
#3 Improved notifications. Just throwing something out there, but maybe in style of the Windows Phone "get in get out" they should build a notification center which operates on the lock screen? I find it a little tedious to unlock my phone in order to interact with the notification center.
Click to expand...
Click to collapse
Aside from #3, all of those things have/are being done and as far as hardware is concerned are beyond the controll of MS aside from them making their own handsets. I find it funny that while it is rumored that an iPhone is gonna be doing XXX, MS/Partners are already quietly doing it, and when feature XXX releases on an iPhone the reaction will be 'OMG is so NEW and REVOLUTIONARY!"
ROCOAFZ said:
Surprized no one mentioned Landscape startscreen when phone is turned.
Click to expand...
Click to collapse
this will be supported in Apollo. Should have been implemented from jump
Sent from my Venue Pro using XDA Windows Phone 7 App
voluptuary said:
Aside from #3, all of those things have/are being done and as far as hardware is concerned are beyond the controll of MS aside from them making their own handsets. I find it funny that while it is rumored that an iPhone is gonna be doing XXX, MS/Partners are already quietly doing it, and when feature XXX releases on an iPhone the reaction will be 'OMG is so NEW and REVOLUTIONARY!"
Click to expand...
Click to collapse
Trust me, I laugh about that constantly. Or in the iCamp it can take a worse turn. A feature seems unnecessary until the iPhone gets it. Adobe Flash is not necessary, neither is removeable memory, or a radio. Megapixels did not matter until the iPhone got with it. Neither did a FFC.
937dytboi said:
this will be supported in Apollo. Should have been implemented from jump
Sent from my Venue Pro using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Where did you see an article for this? just interested as i didn't see this in any lists and would like to read it.
ROCOAFZ said:
Where did you see an article for this? just interested as i didn't see this in any lists and would like to read it.
Click to expand...
Click to collapse
Actually saw the support for start screen landscape in the leaked video of wp8 Apollo. Not sure if the video is still up. I haven't seen it in any articles, just the video.
Sent from my Venue Pro using XDA Windows Phone 7 App