Well. Have to say, the WP8 ecosystem/devices aren't really ones I could recommend currently. Here's the latest issue: had an update to Nokia Maps appear today, but failed to download. It gets 50% complete then errors out with a "8103010d" code and fails to finish. Ok, no big deal except that WP8 disables the app you are attempting to update. So now I have no maps. Great.
I was a hearty supporter of WP7 after Mango. Rock-solid, good design, great ecosystem of services. Now the opposite is true - the devices have stability issues, battery problems, build quality concerns; the ecosystem lost a decent number of features: wireless sync, Zune/XBox Video playback, custom podcast support, a decent desktop app; and no one at MS seems to care or get this. Whichever intern at MS screwed up during the WP8 design process needs to be fired.
Back to the original point of this post- anyone had the 8103010d error and got around it?
I was a hearty supporter of WP7 after Mango. Rock-solid, good design, great ecosystem of services. Now the opposite is true - the devices have stability issues, battery problems, build quality concerns; the ecosystem lost a decent number of features: wireless sync, Zune/XBox Video playback, custom podcast support, a decent desktop app; and no one at MS seems to care or get this. Whichever intern at MS screwed up during the WP8 design process needs to be fired.
Back to the original point of this post- anyone had the 8103010d error and got around it?