I'm about to buy a WP device, and of course it's my first WP device so I was doing some research on it.
We know that Lumia devices to WP are like Nexus device to Android, which means first gets update to new system.
And recently there a lot of wallet-friendly WP phones comes out like Prestigio, Yezz, Blu... etc, and as I have wait for 2 months that Lumia 630 dual sim is still not available in my country so I'm thinking about prestigio multiphone 8500.
Only thing I'm worrying about is system update. I take no doubt it's not gonna be as fast as Lumia devices get.
And I read an article about an app "windows preview for developers", and appears it can run on Lumia, Huawei and Samsung.
So I was wondering how does WP work?
I mean, for example the Android , each device has its own driver so need manufacturer to do the update.
And WP doesn't work that way? just like we saw on PC, one system contains almost all driver?
Each OEM device contains the Windows Phone OS + OEM/Carrier specific firmwares that do include drivers that will add and tweak things for the specific version of WP.
The Preview for Developers program allows a user to update his or her phone to the latest version of the Windows Phone OS ONLY, keeping the current firmware that you had installed BEFORE you updated the OS via the preview for developers. Before updating, Microsoft informs you that if something goes wrong with your phone, that it CAN void your warranty (unless you can get back to a previous version of the OS to match the version that is in production for your carrier).
The carriers will release the OEM/Carrier updates when they are approved.
qtwrk said:
I'm about to buy a WP device, and of course it's my first WP device so I was doing some research on it.
We know that Lumia devices to WP are like Nexus device to Android, which means first gets update to new system.
And recently there a lot of wallet-friendly WP phones comes out like Prestigio, Yezz, Blu... etc, and as I have wait for 2 months that Lumia 630 dual sim is still not available in my country so I'm thinking about prestigio multiphone 8500.
Only thing I'm worrying about is system update. I take no doubt it's not gonna be as fast as Lumia devices get.
And I read an article about an app "windows preview for developers", and appears it can run on Lumia, Huawei and Samsung.
So I was wondering how does WP work?
I mean, for example the Android , each device has its own driver so need manufacturer to do the update.
And WP doesn't work that way? just like we saw on PC, one system contains almost all driver?
Click to expand...
Click to collapse
Hi,
Firstly, although now Nokia's mobile division belongs to Microsoft, I do not think as long as it is a kind of exclusivity for updates. It's just that there are only a duo (or rather all in one) Microsoft/Nokia that move your ass, the rest of the manufacturers do almost nothing, and royally fu** Windows Phone (Huawei, HTC, Samsung, etc). It is therefore felt in the updates:
- Nokia first in almost all the time
- Huawei, HTC, Samsung, etc. last
All this because some OEMs do not want to bet (big) on Windows Phone. This is unfortunate.
In addition, the updates via the Developers Preview for all models of Windows Phone 8 uild OS updates have the same time. Namely, since the GDR3 Preview, the Preview status updates become official once the release for everyone (almost no change the build version between of Preview/official).
On Windows Phone, the packages the OS portion and the firmware part *are separated*, which means that one can go without the other.
Some example (Nokia):
- Preview GDR3 WP8.0 on Lumia Amber (Lumia Amber is fully compatible under GDR2 WP8.0).
- Preview WP8.1 on Lumia Black (Lumia Black is fully compatible under GDR2 WP8.0).
- Preview GDR1 WP8.1 on Lumia Cyan (Lumia Cyan is fully compatible in WP8.1).
- Etc. (along with other OEM).
Of course, for each GDR (at minimum), OEMs need to update their firmware to make it fully compatible at this level (software-hardware).
anaheiim said:
Hi,
Firstly, although now Nokia's mobile division belongs to Microsoft, I do not think as long as it is a kind of exclusivity for updates. It's just that there are only a duo (or rather all in one) Microsoft/Nokia that move your ass, the rest of the manufacturers do almost nothing, and royally fu** Windows Phone (Huawei, HTC, Samsung, etc). It is therefore felt in the updates:
- Nokia first in almost all the time
- Huawei, HTC, Samsung, etc. last
All this because some OEMs do not want to bet (big) on Windows Phone. This is unfortunate.
In addition, the updates via the Developers Preview for all models of Windows Phone 8 uild OS updates have the same time. Namely, since the GDR3 Preview, the Preview status updates become official once the release for everyone (almost no change the build version between of Preview/official).
On Windows Phone, the packages the OS portion and the firmware part *are separated*, which means that one can go without the other.
Some example (Nokia):
- Preview GDR3 WP8.0 on Lumia Amber (Lumia Amber is fully compatible under GDR2 WP8.0).
- Preview WP8.1 on Lumia Black (Lumia Black is fully compatible under GDR2 WP8.0).
- Preview GDR1 WP8.1 on Lumia Cyan (Lumia Cyan is fully compatible in WP8.1).
- Etc. (along with other OEM).
Of course, for each GDR (at minimum), OEMs need to update their firmware to make it fully compatible at this level (software-hardware).
Click to expand...
Click to collapse
thanks for your reply.
please forgive my stupidity and poor english, about GDR, can I take it like a big update on Windows , like Service Pack ? at least that's how I felt about this thing ...
what do you mean "Amber", "Black" and "Cyan" ? I assume it's like system name ? like TouchWiz , SenseUI and something ?
so I assume i bought a Prestigio Multiphone 8500 duo (WP8.1) , is it possible i get WP8.1 GDR1 myself ? (even somehow it's problematic and not fully compatible) or I must wait for OEM to do it ?
qtwrk said:
thanks for your reply.
please forgive my stupidity and poor english, about GDR, can I take it like a big update on Windows , like Service Pack ? at least that's how I felt about this thing ...
what do you mean "Amber", "Black" and "Cyan" ? I assume it's like system name ? like TouchWiz , SenseUI and something ?
so I assume i bought a Prestigio Multiphone 8500 duo (WP8.1) , is it possible i get WP8.1 GDR1 myself ? (even somehow it's problematic and not fully compatible) or I must wait for OEM to do it ?
Click to expand...
Click to collapse
GDR means "General Distribution Release". GDRs provide bug fixes, modifications of any kind, add features, etc.
If Windows Phone 8 would "equal" (excuse the term) at Windows 7 (not Windows 8, because there are more Service Pack on this version), then yes a GDR would be about equal to a Service Pack.
Lumia Amber, Lumia Black and Lumia Cyan are firmware developed by Nokia. They contain all sorts of things, such as drivers, features, assembly (dll/exe), etc.
Basically, it is the firmware that makes the link between the hardware and the software. All other manufacturers are developing the firmwares for their Windows Phone, only they do not give of name at of their firmware. Nokia does.
All Windows Phone 8 will get the GDR1 of WP8.1, even your device (either by voice Preview, or by the official voice).
anaheiim said:
GDR means "General Distribution Release". GDRs provide bug fixes, modifications of any kind, add features, etc.
If Windows Phone 8 would "equal" (excuse the term) at Windows 7 (not Windows 8, because there are more Service Pack on this version), then yes a GDR would be about equal to a Service Pack.
Lumia Amber, Lumia Black and Lumia Cyan are firmware developed by Nokia. They contain all sorts of things, such as drivers, features, assembly (dll/exe), etc.
Basically, it is the firmware that makes the link between the hardware and the software. All other manufacturers are developing the firmwares for their Windows Phone, only they do not give of name at of their firmware. Nokia does.
All Windows Phone 8 will get the GDR1 of WP8.1, even your device (either by voice Preview, or by the official voice).
Click to expand...
Click to collapse
if I may , i'd like to know something more about WP.
as we can see in Android , the eco-system is full of fragment , and Google couldn't push OEMs to update their devices, does Microsoft have more control over this matter ?
I mean , how could Microsoft to be so sure about all WP8 devices will get GDR1 ? for Lumia series I can understand , but what about devices of Huawei , Samsung and other OEMs ? how could Microsoft guarantee the update on NO-Lumia devices ?
qtwrk said:
if I may , i'd like to know something more about WP.
as we can see in Android , the eco-system is full of fragment , and Google couldn't push OEMs to update their devices, does Microsoft have more control over this matter ?
I mean , how could Microsoft to be so sure about all WP8 devices will get GDR1 ? for Lumia series I can understand , but what about devices of Huawei , Samsung and other OEMs ? how could Microsoft guarantee the update on NO-Lumia devices ?
Click to expand...
Click to collapse
All Windows Phone 8 device has support in terms of updates. Support for Windows Phone 8 will normally end at the latest in 2016 (for some device).
On this point, you do not have to inquitez, not before long (and in hope that Microsoft to learn from their mistake with WP7).
anaheiim said:
All Windows Phone 8 device has support in terms of updates. Support for Windows Phone 8 will normally end at the latest in 2016 (for some device).
On this point, you do not have to inquitez, not before long (and in hope that Microsoft to learn from their mistake with WP7).
Click to expand...
Click to collapse
with all due respect sir , i think you misunderstood me ...
my main question is , how could Microsoft possibly to oversee the update over all other OEMs ? for Lumia , there is no doubts about that ...
like they've made a contract , agreement , or such thing ?
we see how the looser Google is, in the control, special the update part of Android ...:crying:
Microsoft controls the phone update servers. If an OEM doesn't want to release an update for their phone, MS could (in theory) just push the OS update to all users of that phone anyhow. This would be functionally equivalent to using the Preview For Developers option, except doing it for everybody instead of just those who opted into it.
PFD allows you to update any WP8 device from any OEM and on any carrier as though it were an Android Nexus device: you get the updates as soon as Microsoft publishes them, without waiting on OEM/MO customizations and without the OEM or MO having any opportunity to block or delay the update unless it breaks on their firmware (in which case MS will stop pushing the update until it's fixed).
Related
is possible win mobile on htc tattoo?
tanks
see here:
http://forum.xda-developers.com/showthread.php?t=583920
Still trying to find a method to root the device, then WM is pretty much further (and uninteresting sincerely). Buying a Tattoo for WM is a really bad idea, I don't even know if the processor can support WM
Windows Mobile is closed source, so no, it possibly couldn't be done.
Windows Mobile is lame anyway, it's actually a dummified version of Windows 2000 running some pretty GUI. Win Mobile is also a GUI on top of Windows CE, I believe the latest version is WinCE 6.5.
WinCE afaik needs to be compiled for specific CPU and such... It's not a one-size-fits-all setup. Sorry to pop your bubble.
Coburn64 said:
Windows Mobile is closed source, so no, it possibly couldn't be done.
Windows Mobile is lame anyway, it's actually a dummified version of Windows 2000 running some pretty GUI. Win Mobile is also a GUI on top of Windows CE, I believe the latest version is WinCE 6.5.
WinCE afaik needs to be compiled for specific CPU and such... It's not a one-size-fits-all setup. Sorry to pop your bubble.
Click to expand...
Click to collapse
A little history from wiki..
Released in 16 November 1996 Codename "Alder".
Devices named "handheld PC" (HPC).
2.0 Released in September 1997 Codename "Birch".
Devices named "Palm-sized PC".
Real-time deterministic task scheduling.
Architectures: ARM, MIPS, PowerPC, StrongARM, SuperH and x86.
32-bit color screens.
SSL 2.0 and SSL 3.0.
3.0Released in June 2000 [MSCE3].Codename "Cedar".
Major recode that made CE hard real time down to the microsecond level.
Base for the Pocket PC 2000, Pocket PC 2002 and Smartphone 2002.
Priority levels was increased from 8 to 256.
Object store was increased from 65 536 to 4,19 million allowed objects.
Restricted access to critical APIs or restricting write access to parts of the registry.
4.x Released in January 2002 [MSCE4].Codename "Talisker/Jameson/McKendric".
Driver structure changed greatly, new features added.
Base for "Pocket PC 2003".
Bluetooth support.
TLS (SSL 3.1), IPsec L2TP VPN, or Kerberos.
5.0 Released in August 2004.Adds lots of features. Codename "Macallan".
Automatic report of bugs to the manufacturer.
Direct3D Mobile, a COM-based version of Windows XP's DirectX multimedia API.
DirectDraw for 2D graphics and DirectShow for camera and video digitisation support.
Remote Desktop Protocol (RDP) support.
6.x Released in September 2006. Codename "Yamazaki".
Process address space is increased from 32 MB to 1 GB.
Number of processes has been increased from 32 to 32 768.
User mode and kernel mode device drivers are possible.
512MB physically managed memory
Device.exe, filesys.exe, GWES.exe has been moved to Kernel mode.
SetKMode and set process permissions not possible.
System call performance improved.
Theres no doubt Windows can do more than Android can in certain areas that really make a device useful. Windows Mobile= Mini PC w/phone capabilities, and Android= Modern Smart phone/w PC like functionality. It's all up to what you want in a phone..but if you gave me a Mini PC Phone..all in one word..that will be winner.
Cant understand WHY anyone wants WM ??? Its **** compare to Android in my world
OK, Could be nice with update for android to 2.x but windows mobile = hell no....
WM Shouldn't be a priority - Let's root and update
I have owned several WM devices, and Android is way superior than WM. Why would you buy a tattoo and then convert it? You should have bought a WM device if you want WM. Anyway, we should first be able to root the device, and update to 2.1.
Let us get our priorities right people!
besides being free source and visually more appealing i fail to see where exactly does android out do windows mobile???? Functionality ways according to me nothing beats windows mobile. I upgraded to the hero just to try something different, just to see what android is like..and in no way is it better than windows mobile....if ur talking about sense ui, facebook integration, and all the million other widgets that make your experience a great one.....that isn't the android OS per se...theyre just add ons. any way SPB mobile 3.5 is still better than the sense ui that we get on our phones.
things i didn't like about android:
-No bluetooth file transfer(at least in the version im running on the hero now)
-No bluetooth tethering option(i used to use this a lot on my windows phone)
-no option of installing programs on sd card( i had to root and install apps to sd, that too cache still remains on the phone memory)
-lacks basic programs when it comes from the factory, being a smart phone one would expect it to ship with basic programs like a file explorer and an office suite. but no...this phone overly depends on the market for everything.
conclusion
Although android is developing fast and seems to have a promising future, it is yet to become as good as windows mobile let alone out doing it. if i had the money i would surely buy an HD2.
We all know Android looks nicer but how does that make it superior? Wouldn't the operation system with the most features be ahead? Windows mobile will get flash 10.1 support first..windows CE usually powers all the intese 3D U.I's you see in embedded devices. Even nvidia has said they prefer the windows kernel over linux for doing 3D applications. I'm just saying the next windows mobile is obviously going be like holding a Mini Gaming PC from 2005-2006 in your pocket. Android will have to impress me with just good looks, and open source goodness..if theres an alternative that can actually do more. Dont get me wrong though, once i've booted Android on my device I never looked backed at windows again.
Whoopeedoo, a smartphone with a 3D UI. Big deal. Windows Mobile is horrible on Battery Life, I had a Windows Mobile PDA and it was in standby after a full charge, and it just drained like crazy yet it was idle.
Android is open source. It can be extended, edited and used for any task - It powers some eBook readers. Windows Mobile is crap, it's based on Windows NT Kernel (yes, that's correct) and you can't develop apps for WM unless you learn all the .NET garbage.
FACT: Android supports Bluetooth File Transfer via custom APK.
Go get a HTC Hero or HTC Dream with Quickoffice if you want some office app on your phone. Who would want to type a school assignment on their phone anyway?
I'll be a linux and android supporter, I'm not going to be corrupted with Windows Mobile. I use Windows CE + Linux on my Jornada HPC, so I'll have a shot at porting Android over to it.
@above
whatever suits you dude. For me, yes i can live with android(till i can afford the HD2) but the experience is not as pleasing as it was on the win mobile platform. As far as battery life goes, i have never had any issue with win mob, its pretty much the same as android...... well at least for my usage.
NO the android 1.5 that i currently run on the HERO does not support bluetooth file transfer or tethering even via a custom apk, although the much acclaimed 2.0 and newer versions do. But sadly there hasn't yet been any official release from HTC and the leaked roms though good (thanks to the efforts of the devs) aren't stable enough for my daily usage. In the end it all boils down to personal preference and your needs, whats superior and whats not doesn't matter really.
Coburn64 said:
Whoopeedoo, a smartphone with a 3D UI. Big deal. Windows Mobile is horrible on Battery Life, I had a Windows Mobile PDA and it was in standby after a full charge, and it just drained like crazy yet it was idle.
Android is open source. It can be extended, edited and used for any task - It powers some eBook readers. Windows Mobile is crap, it's based on Windows NT Kernel (yes, that's correct) and you can't develop apps for WM unless you learn all the .NET garbage.
FACT: Android supports Bluetooth File Transfer via custom APK.
Go get a HTC Hero or HTC Dream with Quickoffice if you want some office app on your phone. Who would want to type a school assignment on their phone anyway?
I'll be a linux and android supporter, I'm not going to be corrupted with Windows Mobile. I use Windows CE + Linux on my Jornada HPC, so I'll have a shot at porting Android over to it.
Click to expand...
Click to collapse
Yeah, I'm just saying the next high end windows phones will bring mobile smartphones into the next level. It will support higher res 1200x600 screens ,multiple screen support, being able to output movies, and UI to your TV..making it a true portable media device. You'll basically have a xbox 360/Zune/PC in your pocket.
hers what to do
send me your tatoo
ill send you my htc touch mk 1
fair swap
you get windows
i get anotheR lovely android device !!
(( no but seriously the apps you want i can sort of agree with, file managers on android are a whole new thing when your used to win-mob, maybe try linda file manager or astro its just a getting used to process... or we can swap ! ))
=====PEACE=====
eldrid said:
@above
whatever suits you dude. For me, yes i can live with android(till i can afford the HD2) but the experience is not as pleasing as it was on the win mobile platform. As far as battery life goes, i have never had any issue with win mob, its pretty much the same as android...... well at least for my usage.
NO the android 1.5 that i currently run on the HERO does not support bluetooth file transfer or tethering even via a custom apk, although the much acclaimed 2.0 and newer versions do. But sadly there hasn't yet been any official release from HTC and the leaked roms though good (thanks to the efforts of the devs) aren't stable enough for my daily usage. In the end it all boils down to personal preference and your needs, whats superior and whats not doesn't matter really.
Click to expand...
Click to collapse
Noted, I guess I misread your post as "OMG Android ****, WM pwns". Sorry if I offended you.
I'm sure if people wanted to, they could make a Win Mobile UI for android... but in my opinion, Android has a better feature set and can be hacked more than Windows Mobile can.
Hey i wasn't offended. Any way i agree the win mob UI is ****ty, its just the way the platform works that makes me like it, its very much like the windows pc that we use and are so overly familiar with. May be i will eventually get used to android.
As far as hacking goes....well no one has been able to root the tattoo or the droid eris yet...but almost all win mob devices at least have a soft spl out there.
Again a phone is meant to satisfy an almost unique set of needs of each individual, so yes its all personal preference.
I love the market on the android though..tons of free applications and in future if i had to buy a phone i would always choose a win mob or android phone...had a bad experience with symbian and i simply don't like the i-phone.
True. The iPhone UI is too simple, Windows Mobile had me going around in circles wondering how to send files to another device, and Android is just a "little slice of heaven". Again, that's my two cents, but yes, if any hardcore WM hacker wants a challenge, try porting WM to the HTC Click.
normally such porting is very hard if not impossible as drivers for the tattoo are made to be used with android 1.6, writing drivers from scratch for windows is going to be a royal pain in the @$$ for most developers.
How can we move forward by continuing what we were used to do with WM6.5 on WP7 & HD7
I have just purchased HD7 and was expecting to move easily from WM6.5 on my previous diamond to WP7.
One of my reasons why I am buing a windows phone device is that all my history of work for more than 10 years was stored on windows mobile... It is true that I find some difficulties when upgrading, but there is always a way to upgrade and take with you your old staff...
Here is a surprise ...
This was a chat that i made on microsoft official Website...
________________________
TOPIC:
________________________
-How can we move forward by continuing what we were used to do with WP6.5 and work with WP7?
________________________
DESCRIPTION:
________________________
-Ok it seems that i will regret buying my new HTC HD7 that operates Windows phone 7.
-I have my own software that i purchased for windows phone 6.5 and i have no idea if I am able to install these softwares on windows phone 7.
-I use these software in my work and the backup softwares that i was used to for getting back all my contacts and SMS's... If anyone have a solution for this please reply and help the windows phone users.
-I beleive I am not the only one suffering from the same problem.
-Is Microsoft asking us to go and buy again the same softwares just for the reason of being windows phone 7?
-Ok, let us think forward, I will buy the new windows phone 7 apps but I want to be sure that these apps can also work on windows phone 6.5 so that i can continue building up by taking my old personal files and continue.
-I don't think it is a good idea to restart from scratch again...!
________________________
REPLY: from Joel Ivory Johnson
________________________
Cutting straight to the conclusion, Windows Phone isn't a form of Windows Mobile and has no compatibility with it. You can't use your Windows Mobile software on it.
If you want to see the full reasons behing the break away from Windows Mobile for a consumer solution you will want to watch the 15 February 2010 announcement from the Mobile World Congress for what was then called "Windows Phone 7 Series" (by Joe Belfiore and Steve Ballmer). The best way I can summarize it is that Microsoft couldn't provide the user experience they aimed for while retaining backwards compatibility. With the shrinking marketshare of Windows Mobile among consumers it would appear that the lost of past investments was already a shrinking concern (after all as users moved to Android and iPhone they were separating themselves from the past software investments. So no matter what it is bound to happen).
So Microsoft designed a new operating system for consumers and Windows Mobile (now called Windows Embedded Handheld) is still around as an enterprise solution and evolving in it's own direction.
________________________
In reply to Joel Ivory Johnson post on March 12, 2011
________________________
WoW... it was really shocking ... Now microsoft is asking me again to forget about my work in the last years...
I am ordered to push the button and restart or else i will be outdated...
does anyone have a suggestion ?
Now, I will not only think of changing my operating system, I'll think of changing my whole life and go to any other company that would respect people efforts over the years... And i have nothing to sacrifice this time, by anyways I will lose my previous work...
Thanks Microsoft for wasting 10 years of my life... (I started to work on windows mobile since this old i-mate 2020, anyone remember?)
________________________
NOW:
-What do you think? -Any suggestion? -Any work arround? -Should we go back?
Move on, adapt to changes. I think Microsoft did a good thing starting from scratch. I mean.. if there was no Windows Phone 7 you would have either moved to Android, iOS, Blackberry or Symbian(Which is as good as dead by now). Then you would have had to start all over again with everything unless you wanted to use an archaic phone with an even more archaic OS.
As a good rule of thumb, it's always beneficial to do some research on what you are purchasing before you go ahead with the purchase.
As you have found out, Windows Mobile 6.5 is nothing like or even related to Windows Phone 7 (aside from the similarities in the name). Applications from Windows Mobile are not compatible with Windows Phone, and the same is true the other way around.
If you like Windows Mobile 6.5, you should stick with it. You'll be safe in knowing you will always have the latest version of Windows Mobile and won't ever have to upgrade your software again.
If you switch to Windows Phone 7, you switch to a brand new (version 1.0) platform. Kinda like switching from a PC to a Mac. So you'll be buying and building new apps for your new platform and will have to find ways to work with the new platform. You'll find that both Windows Mobile 6.5 and Windows Phone 7 have their positives and negatives, and you just need to figure out what works best for you and stick with it.
You remember moving from 3.11 -> Win 95, Win 98 -> XP, and XP -> Vista... Win CE -> WM5
Now it is WM6.5 -> WP7...
Microsoft always do the same...
Don't you remember some good staff you had on your Win98 that you miss now?
I am an Engineer, I was used to use multiple engineering softwares that creat special file formats. Also some general softwares like GPS Tracking software, Graphic Calculators, and more...
Now Microsoft dicovered that it is out of the competition due to Android OS, and Iphone. So instead of holding its previous clients who where Using there PPC for real business applications and paying lots on cash for doing this, Microsoft decides to go with the easy trend. Some funny games, some animation, BUT WHERE IS THE CORE?
Now Windows Phone 7 looks to me like any simbian device with "MS office" (thanks god, they did not throw it away)
Where is the origen of "Windows =(multi-tasking)"?
does anyone believe that a windows os doesn't have multi-tasking? doesn't have file explorer?
sooo weired ...
I was a fan of Microsoft I always say those competitors are far away from what a PPC was made for...
Now I am shocked, even Microsoft is taking the easy way...
AmgAdly said:
You remember moving from 3.11 -> Win 95, Win 98 -> XP, and XP -> Vista... Win CE -> WM5
Now it is WM6.5 -> WP7...
Click to expand...
Click to collapse
And this is where you misunderstand. Your progress chart is kinda off.
Win 1.x -> Win 2.x -> Win 3.x -> Win 95 -> Win 98 -> Win ME (end)
Win NT 3.x -> WinNT 4 -> Win 2000 (end)
Then the Windows consumer kernel and the Windows NT kernel were combined to create Windows XP.
Win XP -> Win Vista -> Win 7
The above are three separate lines of products but they happen to share the same brand name. Windows ME was the last of its product line. Upgrading from the Windows ME line to XP was a rather turbulent experience as it broke support for many hardware devices and offered little support for older software (though of course, there were always ways to make it work).
As for the Windows Mobile and Windows Phone lines.
... -> WM 6.0 -> WM 6.1 -> WM 6.5
WP7
Windows Mobile 6.5 and below are not part of the Windows Phone 7 line of software. They are two separate software product lines. Though they share similar names, which is a marketing tactic (a failed one I might add), but that's where the similarities end.
A sentiment shared by most people in the industry (and most consumers), Windows Mobile was (is) a dead platform and could not succeed any longer in its current form in this modern market. So its development has ended, and a new product was created called Windows Phone 7. WP7 is built from scratch, and because of that, it does not have all the features that the 10+ year old Windows Mobile product has. Given time, Windows Phone 7 will become an even better mobile platform than it currently is, but until then, if you are not happy with the kinds of things Windows Phone 7 brings to the table, then by all means switch to something else that does, or stick with Windows Mobile.
You bring up points that countless others have brought up before, and your complaints will yield no results, so its rather useless to complain. Not to mention, it is rather unfair to compare a product less than a year old to a product that has more than 10 years of development time. Of course Windows Mobile has got more features. That's just common sense.
What kind of a business tactic involves supporting a 10 year old product that doesn't cut it anymore? In this modern day of smartphones, the game has changed, so Microsoft needed to change with it.
So you are right, PPC is made for a different type of person, and Windows Phone 7 is not PPC, not even close.
You're a little off on your chart as well.
Win2000 is NT5.0. XP is NT5.1. They should be listed on the same line.
Just sayin'.
Thank you all for your reply...
As you mentioned, we should move forward... There was a nice PIM backup software that we used to backup our SMS's and contacts...
Is there any news about a new version to work on WP7 and use the Backup files we created on WM6.5 to be restored on WP7?
or any fix to run PIM backup software (in compatiblity view) (run as WM6.5 app) on WP7...?
We need to go forward and at least keep some backup of our SMS's ... right?
Thank you!
prjkthack said:
And this is where you misunderstand. Your progress chart is kinda off.
Win 1.x -> Win 2.x -> Win 3.x -> Win 95 -> Win 98 -> Win ME (end)
Win NT 3.x -> WinNT 4 -> Win 2000 (end)
Then the Windows consumer kernel and the Windows NT kernel were combined to create Windows XP.
Win XP -> Win Vista -> Win 7
The above are three separate lines of products but they happen to share the same brand name. Windows ME was the last of its product line. Upgrading from the Windows ME line to XP was a rather turbulent experience as it broke support for many hardware devices and offered little support for older software (though of course, there were always ways to make it work).
As for the Windows Mobile and Windows Phone lines.
... -> WM 6.0 -> WM 6.1 -> WM 6.5
WP7
Windows Mobile 6.5 and below are not part of the Windows Phone 7 line of software. They are two separate software product lines. Though they share similar names, which is a marketing tactic (a failed one I might add), but that's where the similarities end.
A sentiment shared by most people in the industry (and most consumers), Windows Mobile was (is) a dead platform and could not succeed any longer in its current form in this modern market. So its development has ended, and a new product was created called Windows Phone 7. WP7 is built from scratch, and because of that, it does not have all the features that the 10+ year old Windows Mobile product has. Given time, Windows Phone 7 will become an even better mobile platform than it currently is, but until then, if you are not happy with the kinds of things Windows Phone 7 brings to the table, then by all means switch to something else that does, or stick with Windows Mobile.
You bring up points that countless others have brought up before, and your complaints will yield no results, so its rather useless to complain. Not to mention, it is rather unfair to compare a product less than a year old to a product that has more than 10 years of development time. Of course Windows Mobile has got more features. That's just common sense.
What kind of a business tactic involves supporting a 10 year old product that doesn't cut it anymore? In this modern day of smartphones, the game has changed, so Microsoft needed to change with it.
So you are right, PPC is made for a different type of person, and Windows Phone 7 is not PPC, not even close.
Click to expand...
Click to collapse
I'm quoting this because this is just about the best explanation I have seen so far. Honestly, this should be at the top of every WP7 related page on this forum. This is very well thought out, and articulated version of what I keep screaming everytime I read/see the same stuff.
"Quit cryin!" Get over it or move to Android (which IMO is Windows MOBILE 7+)
You're not going to cry MS into reverting back to WM6.'whatever'. So you can roll with it or move and roll in another direction.
You can keep backups of your SMS messages by utilizing Microsoft MyPhone (WinMo 6.5), which syncs your texts to your live account.
Unfortunately, no way to get those texts to your WP7. But you can always look at them.
http://myphone.microsoft.com
jimbonics said:
You're a little off on your chart as well.
Win2000 is NT5.0. XP is NT5.1. They should be listed on the same line.
Just sayin'.
Click to expand...
Click to collapse
I separated Windows 2000 from XP because it is considered that Windows 2000 was the end of the whole "business-only" Windows platform (at the time 2000 was released, ME was also not far behind, so it was still billed as the separate "consumer" and "business" platforms), even though it was technically the first hybrid kernel Windows platform. It was only when XP was released that it was considered the first of the consumer/business hybrid platform. So therefore I think that warrants it to be part of a separate line on its own since its all been based on XP's whole hybrid mantra since then.
So yes, on either line, technically, it'd be correct. Haha.
The best indicator of whether something is good and valuable is the equipment price. At the beginning of the HD7 was very expensive and no one knew what it is WP7. After several months, it appears that it is better to give the phone to be utilized than to sell it on ebay. Nice phone on which you can do a little.
Hey, i would know if it is possible on WP8 to change the OEM market to nokias as there were wp7 apps for that.
would be great if there will be something to do this, as i think that nokia will wait a long time to release the normal Nokia Drive for all Windows Phones
how I can insall app design for wp8 at wp7
what about update wp7 to wp8 (I have hd7 wp7.8)
md80410 said:
how I can insall app design for wp8 at wp7
what about update wp7 to wp8 (I have hd7 wp7.8)
Click to expand...
Click to collapse
Firstly this is Windows 8 not windows phone 8.
But in answer to your question. There is no way to update a windows phone 7 device to windows phone 8. Windows phone 8 apps physically cannot run on windows phone 7 as it lacks the APIs to do so. Most developers right now still make apps for windows phone 7 because they can run on both 7 and 8.
If you want windows phone 8 and windows phone 8 apps, get a windows phone 8 handset.
As for upgrading WP7 device to WP8, it's technically not impossible - the hardware can run it (though poorly) - but the WP8 OS was designed to require hardware features not present on WP7 handsets. Consequently, there are no WP7 devices which receive an official update to WP8.
GoodDayToDie said:
As for upgrading WP7 device to WP8, it's technically not impossible - the hardware can run it (though poorly) - but the WP8 OS was designed to require hardware features not present on WP7 handsets. Consequently, there are no WP7 devices which receive an official update to WP8.
Click to expand...
Click to collapse
The biggest limitation for an update is a complete kernel swap. WP7 used the windows CE kernel. WP8 uses the windows NT kernel. For all intents and purposes this makes them entirely different operating systems and the technical difficulty of issuing an update for WP7 to 8 would be like releasing an update to the iPhone that installs android or an update to windows 8 which installs OSX.
Its only because WP7 apps are in .NET and it was possible to port .NET to WP8 that WP7 apps do run on WP8. Other than that the only relationships between the 2 platforms are name, general design style and the fact that they are made by the same company.
But otherwise. WP8 could feasibly run on WP7 handsets. Its just it wouldn't be possible to do the same way as regular software updates. Plus most WP7 devices are actually pretty low spec, they were all single core hitting clock speeds of 1.4ghz max, half gb of ram usually. Not beasts of handsets at all.
What do you mean by "regular updates"? Each Windows Phone update required the phone switching to a special "Update OS" boot mode where the "ROM" of the main OS could be modified, and at that point switching out the kernel (and associated userspace libraries) is no harder than, for example, switching out IE7 for IE9 (which the Mango update to WP7 did). Yeah, it's not really the same OS afterward, but so what? The data is still there.
Admittedly, WP7 makes substantial use of Windows Embedded Database and CE Database files, which are accessed through APIs that are CE-specific extensions to the standard Win32 API. Those would either need to be ported to the Win32/NT API, or the data in them would need to be converted to another format during the update... or the phone's configuration would need to be wiped and set up with defaults again, which would kind of suck but still be better than "no WP8 for you; go buy new hardware!"
Anyhow, this whole thread is in the wrong forum. Could somebody do something about that?
hi
is it possible to install windows 8.1 on nokia lumia 1520? hardware is good enough and display size is big enough to have windows
I request to find way to do that!
motibala said:
hi
is it possible to install windows 8.1 on nokia lumia 1520? hardware is good enough and display size is big enough to have windows
I request to find way to do that!
Click to expand...
Click to collapse
Yes.
You have two possibility:
- Install Windows Phone 8.1 via the Preview for Developers (PFD) program.
- Wait for the official deployment.
I do not give you more information on the PFD, because the official deploy Windows Phone 8.1 (and Lumia Cyan) for Nokia Lumia 1520 should soon began. Also, Microsoft currently stopped for the moment (for a indefinitely period) deploying Windows Phone 8.1/Lumia Cyan on phones equipped with PFD.
anaheiim said:
Yes.
You have two possibility:
- Install Windows Phone 8.1 via the Preview for Developers (PFD) program.
- Wait for the official deployment.
I do not give you more information on the PFD, because the official deploy Windows Phone 8.1 (and Lumia Cyan) for Nokia Lumia 1520 should soon began. Also, Microsoft currently stopped for the moment (for a indefinitely period) deploying Windows Phone 8.1/Lumia Cyan on phones equipped with PFD.
Click to expand...
Click to collapse
thanks for your quick reply, I meant hack for windows 8.1 as a computer!
motibala said:
thanks for your quick reply, I meant hack for windows 8.1 as a computer!
Click to expand...
Click to collapse
may be Windows RT which is the versión of Windows OS for ARM. Instead of that, think about something, since this is not open source is not possible to Port Windows RT, may be is possible using a virtual machine but that is a lot of work and i dont think anyone will do it for free. Just my two cents ?.
Yeah, the hardware is absolutely not "good enough" for normal Windows 8.1, because that only runs on x86 or x64 CPUs, not on ARM. Windows RT 8.1 is a locked-down version of Windows 8.1 which does run on ARM, but it's not "installable" in the usual sense so you'd need to hack it on there, and its performance on the 1520 would be OK but not tremendous.
The Lumia 2520 tablet is an example of an RT device.
No any way.. Can't do it. Lack of hardware requirements.
Thanks ALL