Archive for the ‘Windows Phone 7’ Category

Microsoft Advertising pubCenter dashboard down

Saturday, March 12th, 2011

Only for maintenance, hopefully it shouldn’t take too long for the service to be restored according to the message:

We’re building a better Microsoft Advertising pubCenter!
We are currently performing site maintenance. All ad units will continue to serve ads normally during this process, but you will not be able to log in.
Service should be restored by Saturday, March 12, 2011 6:00:00 PM. We apologize for the inconvenience and appreciate your patience.
For more information contact us.

Just In: Windows Phone 7 will power the Nokia phones

Friday, February 11th, 2011

Microsoft just announced they partnered with Nokia to be their preferred OS.

Symbian is dead!

Here’s the press release:

LONDON – Feb. 11, 2011 – Nokia and Microsoft today announced plans to form a broad strategic partnership that would use their complementary strengths and expertise to create a new global mobile ecosystem.

Nokia and Microsoft intend to jointly create market-leading mobile products and services designed to offer consumers, operators and developers unrivalled choice and opportunity. As each company would focus on its core competencies, the partnership would create the opportunity for rapid time to market execution. Additionally, Nokia and Microsoft plan to work together to integrate key assets and create completely new service offerings, while extending established products and services to new markets.

Under the proposed partnership:


Nokia would adopt Windows Phone as its principal smartphone strategy, innovating on top of the platform in areas such as imaging, where Nokia is a market leader.

Nokia would help drive the future of Windows Phone. Nokia would contribute its expertise on hardware design, language support, and help bring Windows Phone to a larger range of price points, market segments and geographies.

Nokia and Microsoft would closely collaborate on joint marketing initiatives and a shared development roadmap to align on the future evolution of mobile products.

Bing would power Nokia’s search services across Nokia devices and services, giving customers access to Bing’s next generation search capabilities. Microsoft adCenter would provide search advertising services on Nokia’s line of devices and services.

Nokia Maps would be a core part of Microsoft’s mapping services. For example, Maps would be integrated with Microsoft’s Bing search engine and adCenter advertising platform to form a unique local search and advertising experience

Nokia’s extensive operator billing agreements would make it easier for consumers to purchase Nokia Windows Phone services in countries where credit-card use is low.

Microsoft development tools would be used to create applications to run on Nokia Windows Phones, allowing developers to easily leverage the ecosystem’s global reach.

Nokia’s content and application store would be integrated with Microsoft Marketplace for a more compelling consumer experience.
“Today, developers, operators and consumers want compelling mobile products, which include not only the device, but the software, services, applications and customer support that make a great experience,” Stephen Elop, Nokia President and CEO, said at a joint news conference in London. “Nokia and Microsoft will combine our strengths to deliver an ecosystem with unrivalled global reach and scale. It’s now a three-horse race.”

“I am excited about this partnership with Nokia,” said Steven A. Ballmer, Microsoft CEO. “Ecosystems thrive when fueled by speed, innovation and scale.The partnership announced today provides incredible scale, vast expertise in hardware and software innovation and a proven ability to execute.”

——————————————————————

Update 03/28/2011:
Nokia confirmed Symbian is Dead: no more Symbian phones after 2012.
It also raises some questions about the future of Qt since Nokia acquired Trolltech in 2008.

Upgrade to the latest Microsoft Advertising SDK for Windows Phone 7 to avoid application crashes

Thursday, February 10th, 2011

Microsoft provides an ad control to integrate in Windows Phone applications.

The first version of the SDK, namely 2.1.9130.1 released on Sept.29 2010, has a critical bug that crashes your whole application when the ads are set to auto rotation.

You know you’re affected if your application unexpectedly crashes with an “Element is already the child of another element.” error message:

System.InvalidOperationException was unhandled
  Message=Element is already the child of another element.
  StackTrace:
       at MS.Internal.XcpImports.CheckHResult(UInt32 hr)
       at MS.Internal.XcpImports.Collection_AddValue[T](PresentationFrameworkCollection`1 collection, CValue value)
       at MS.Internal.XcpImports.Collection_AddDependencyObject[T](PresentationFrameworkCollection`1 collection, DependencyObject value)
       at System.Windows.PresentationFrameworkCollection`1.AddDependencyObject(DependencyObject value)
       at System.Windows.Controls.UIElementCollection.AddInternal(UIElement value)
       at System.Windows.PresentationFrameworkCollection`1.Add(UIElement value)
       at Microsoft.Advertising.Mobile.UI.AdFrameManager.CreateNewFrame(FrameworkElement[] controls)
       at Microsoft.Advertising.Mobile.UI.AdFrameManager.DisplayNextFrame(Boolean newAd)
       at Microsoft.Advertising.Mobile.UI.AdFrameManager.ResumeFrameRotation()
       at Microsoft.Advertising.Mobile.UI.AdControl.ActivateAdControl()
       at Microsoft.Advertising.Mobile.UI.AdControl.OnParentSelectionChanged(Object sender, SelectionChangedEventArgs e)

The workaround so far was to disable auto rotation:

xmlns:ad="clr-namespace:Microsoft.Advertising.Mobile.UI;assembly=Microsoft.Advertising.Mobile.UI"

<ad:AdControl AdModel="Contextual" AdUnitId="123" ApplicationId="123456" RotationEnabled="False" />

On December 8th 2010, Microsoft released an update to the SDK, version 2.1.11120.1

This update seems to have fixed the problem and can be downloaded here.

If you’re running ads in your apps on WP7, please do upgrade to the latest version as you may not even be aware of this bug.

Microsoft showed a lack of communication about this update:

1/ The blog post announcing the update doesn’t describe what the update consists of, and which bugs it fixes

2/ The download page does not have any changelog of overview describing what bug fixes and features are included in the update

In contrast, the Windows Phone Developer Tools January 2011 Update download page does have an Overview section summarizing the important changes.

3/ No email or communication was sent to the PubCenter users.

As a PubCenter member I receive updates on how great PubCenter is, that it represents 33.8% of U.S search queries with the partnership with Yahoo! and other communications explaining how to use PubCenter.

4/ No message in the “What’s New” section of the PubCenter advertises the update.

The last message I have from this section dates back to September.

How come, with at least 4 different communication channels listed above, I’m not alerted when something really important happens, like an update to a buggy SDK?

Did I completely miss it?
Or was it an intentional silent update to avoid admitting an embarrassing bug?

A search on “Element is already the child of another element” in the PubCenter forums yields nothing.

The same search on the Windows Phone 7 developer forums returns 2 main threads:

One with a user (Momenta aka Matt Dotson) posting a workaround on December 18th, 10 days after the release of the SDK update, so obviously he was not aware of the update either.

Another thread started on November 16th with user as far as Jan. 23rd posting they encounter the problem before a Microsoft employee (Mark Chamberlain) suggests using the latest Advertising SDK:

Are you folks using the latest Advertising SDK?

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b0f00afc-9709-4cc2-ba2c-57728db6cbd6

I found an internal email thread suggesting that it is the cure for the issue (Element is already the child of another element)

Hope this helps,
Mark

Obviously I was not the only one not knowing about the update.

To the Microsoft Advertising SDK team, could you please be more communicative about your updates and bug fixes?

Developers would greatly appreciate.

——————————————————————

Update 02/11/2011:
MSFT responded favorably to our request for more communication.
Thanks guys for being proactive and listening to your developer community.
MSFT is doing a great job following and supporting their dev community for Windows Phone 7, we’re impressed.

Update 03/24/2011:
Well we’re not impressed anymore: on 02/11 Douglas Robb from Microsoft acknowledged the problem this way:

Thanks for the suggestion. We hear you. Those above me also hear you. When I say ‘those above me’ that means pretty much everybody, so have no fear, the word is out.

And we falsely assumed the next release would be… advertised (pun intended).
It was not: a new version was released on 03/04.
Thanks again to Mark Chamberlain to let the WP7 devs know about it.

We urged them again to correct this situation and hopefully next time have the new release properly advertised.
In the meantime, the only way to tell a new release is out is too… refresh the download page everyday.
Oh so lame in 2011 when they could have used one of those (modern?) communication channels:
- a special email sent just for the release
- the “weekly blog recap” email blast
- “Messages” section of the dashboard
- the pubCenter blog

Even more confusing: Only the XNA version of the SDK was updated, not the Silverlight:

Before installing the latest version (and using the Dec. 08 2010 version):
Microsoft.Advertising.Mobile.UI.dll is at version 2.1.11120.1, filesize 89,912 bytes
Microsoft.Advertising.Mobile.Xna.dll is at version 5.1.0.148, filesize 214,400 bytes

After installing
Microsoft.Advertising.Mobile.UI.dll is at version 2.1.11120.1, filesize 89,912 bytes (NO CHANGE)
Microsoft.Advertising.Mobile.Xna.dll is at version 5.1.0.166, filesize 216,472 bytes

It can be extremely confusing because the download page is now using the version of the XNA DLL and shows 5.1.0.166 as the version number, which is correct for the XNA library only.
Previously this same download page was using the version of the Silverlight DLL (2.1.11120.1) to show the version.

Dear PubCenter, obviously you cannot switch between using the Silverlight version of the DLL and the XNA version.
Either provide 2 different downloads links with their respective version tied to the DLL version and separate the DLLs, or come up with a compounded version number.
Next time you update the Silverlight SDK, your download link will have a version starting in 2.X, don’t you think that will confuse everyone using the latest 5.1.0.166?

Update 03/30/2011:
Microsoft now advertising updates and the changelog.
These are for the Silverlight update of December 8th 2010 and the XNA update of March 4th 2011 (about time to get the changelogs…).
Hopefully next release will be advertised the proper way through different communication channels (blog, emails, newsletter, twitter) along with a much needed changelog.

Update 04/05/2011:
Troy Wood, Portfolio Manager for Windows Phone 7 App Publishers writes:
“Starting with 5.2, both, Silverlight and XNA will use same 5.2.xxxx.y version number.”
Seems the revision problem is fixed for next release.

A user experience of switching from iPhone to Windows Phone 7

Thursday, February 3rd, 2011

Being an iPhone customer since 2008 with the 3G version, I switched to the new Microsoft Windows Phone 7 (WP7) last year.

Here are a few comparison points to make up your mind if you want to switch.

With the new Windows Phone update due anytime now, the shortcomings of the WP7 may be solved soon, or at least we hope.

Overall WP7 is a great product but still behind the competition, and we hope that MSFT, by throwing its whole weight in the battle, will bridge the gap soon.

Features like copy paste are supposed to be introduced in this latest update.
Although not a killer feature (I must have used it only a couple of times within a year on the iPhone), it’s a powerful marketing weapon Apple bigots will throw at any platform that doesn’t support it (“what? your phone doesn’t even have copy-paste? you’re so lame”).
It’s not something you really need, but it’s something that will make your phone retarded if you don’t have it.

The iPhone is still a superior product, but Apple itself made me switch as soon as I upgraded the poor 3G to iOS 4.0.
The whole thing was unusable.
The 3G was already not a speed daemon, but after the upgrade it was slow as hell (pun intended).
I literally had to wait 20 to 30 seconds for the settings page to show.
An eternity in the computer-science-user-patience scale.

How could a big manufacturer like Apple release an update that:
1/ made all the old devices so slow they were rendered unusable?
2/ does not warn the customers beforehand it will render older hardware slow?
3/ prevents you from downgrading to revert to a usable device?

(I guess we all know the answer: the goal was to sell newer versions of the device.)

Anyway, here are the pros and cons of Windows Phone.

1/ WP7: The Good

  • Boots fast: nothing compared to sluggish iPhone 3G
  • Syncs fast: synchronization is faster than the iPhone on iTunes to the point I always wonder if the sync did really happen
  • the screen is bigger (4 inches on the Samsung Focus vs 3.5 inches) than an iPhone 3G or even an iPhone 4
  • Lighter: the difference is very noticeable when both held in hands with the iPhone 4 much heavier (4.8oz) feeling like a brick while the Samsung Focus is only 4oz.
  • You can take picture with the phone locked
    No need to enter your password, press the picture button and you can take a picture. No need to waste time entering your password and missing the picture you wanted to take.
    Although for this feature to be totally useful it should be consistent and popup the camera all the time.
    There’s a bug where sometimes you can keep your finger pressed on the camera button for minutes and the camera doesn’t show up…

  • Applications can offer a trial mode, so you can test an app before buying it.
    This would be great if you could actually update the Trial apps! (see “The Bad” below)

  • Integration of all your contacts pulled from your different email addresses (gmail, yahoo, hotmail) and facebook and in one single address book. This is very powerful.
  • You can hear people on the other end of the line! Pretty amazing for a telephone no?
    But the iPhone speakers are so low you cannot have a normal conversation in a place a little noisy like on the street, in a restaurant,…
    I always wonder how construction workers can have an iPhone as you can’t hear anything.

  • Black is black.
    The black parts of the screen are actually real black and not backlit grey.
    The iPhone 4 is probably much better than the 3G in this area and more comparable to the WP7.

    1/ WP7: The Bad

    1.1 Major features missing

  • NO visual voicemail!
    On the iPhone your voicemails are downloaded and you can see them visually like email.
    At one glance you can tell how many messages you have, which ones you haven’t listened to, who left them, and you can replay a particular one easily without having to go sequentially through all of them.
    With WP7 your back to the old ages: you only know you have a voicemail waiting. You still need to dial a number that will walk you sequentially through all the voicemail and type the appropriate key to skip/delete/archive,…
    Worse: when buying the WP7, the AT&T representative didn’t warn us of that, so they even forgot to switch their backend from visual voicemail to regular voicemail, resulting in a voicemail outage I wasn’t aware of for several days.

  • Copy Paste
    To MSFT’s defence the upcoming update will come with copy pasting.

  • No support for reading MPEG videos
    Trying to read a simple MPEG video in Internet Explorer yields this error message:
    “Can’t download file! Windows Phone doesn’t support .MPG files.”

  • No support for Adobe Flash
    So it’s a draw with the iPhone4

  • No support for reading Silverlight
    This is much more amazing: Silverlight is Microsoft’s equivalent of Adobe Flash.
    Yet they don’t support it on their own phone so you can’t browse a website written in Silverlight. Go figure.

    1.2 Major bugs, Microsoft style

  • the Marketplace (the Microsoft equivalent of the App Store) is awfully unstable, to the point that it crashes, and it crashes big time.
    Meaning once it has crashed, you cannot bring it back up again anymore: your only option is to reboot the phone!

  • the Trial applications cannot be updated!
    There is a major bug on the platform where people who bought a Trial application cannot update it (cf this forum thread).
    Worse: if the user tries to uninstall the current version he has in the hope of getting the latest one, the update will not get downloaded so the user is left with nothing, not even the old version of the app!

  • the Ads crash the applications: provided by Microsoft themselves with PubCenter you would expect something stable, yet there’s a serious bug that crashes your app when the ads are automatically rotating.

    Here is a stack trace of the “Element is already the child of another element.” crash caused by the ads:

    System.InvalidOperationException was unhandled
      Message=Element is already the child of another element.
      StackTrace:
           at MS.Internal.XcpImports.CheckHResult(UInt32 hr)
           at MS.Internal.XcpImports.Collection_AddValue[T](PresentationFrameworkCollection`1 collection, CValue value)
           at MS.Internal.XcpImports.Collection_AddDependencyObject[T](PresentationFrameworkCollection`1 collection, DependencyObject value)
           at System.Windows.PresentationFrameworkCollection`1.AddDependencyObject(DependencyObject value)
           at System.Windows.Controls.UIElementCollection.AddInternal(UIElement value)
           at System.Windows.PresentationFrameworkCollection`1.Add(UIElement value)
           at Microsoft.Advertising.Mobile.UI.AdFrameManager.CreateNewFrame(FrameworkElement[] controls)
           at Microsoft.Advertising.Mobile.UI.AdFrameManager.DisplayNextFrame(Boolean newAd)
           at Microsoft.Advertising.Mobile.UI.AdFrameManager.ResumeFrameRotation()
           at Microsoft.Advertising.Mobile.UI.AdControl.ActivateAdControl()
           at Microsoft.Advertising.Mobile.UI.AdControl.OnParentSelectionChanged(Object sender, SelectionChangedEventArgs e)
    
  • The Internet Explorer Browser is a joke.

    First, it can’t handle big files (big being only 130k). When browsing a simple html text file, some parts will be completely missing and not rendered!
    Tilting the phone from Portrait to Landscape will make the missing text appear.
    What an annoying bug when reading news and long text article or eBooks.

    Second, you cannot go back if you get out of IE. The history is not persistent so you can lose it easily.
    For instance you’re checking out where you will be dining tonight from a site that points to different places.
    You select one, get out of IE to check your Google Bing map, go back to IE and bam! you cannot go back to the original list of restaurants (so you better like your first pick)

    1.3 Annoying things

  • the Marketplace is slow (the caching mechanism seems inexistent or inefficient)
    That’s a serious problem that MSFT discarded as marginal when I contacted them. Probably by now they realized how widespread it is and the upcoming release will fix it?

  • the phone call list in one giant list with outgoing, incoming and missed calls.
    You cannot easily filter to show only the missed calls or outgoing calls for instance.

  • the camera does not remember your settings.
    Set your settings the way you want on the camera:
    - AF mode (Normal, Macro)
    - White balance (Automatic, Incandescent, Fluorescent, Daylight, Cloudy)
    - Image effect (Negative, Sepia, Antique, Green, Blue)
    - Contrast (Minimum, Low, Medium, High, Maximum)
    - Saturation (Minimum, Low, Medium, High, Maximum)
    - Sharpness (Minimum, Low, Medium, High, Maximum)
    - EV (-2, -1, 0, +1, +2)
    - ISO (Auto, 50, 100, 200, 400, 800)
    - Metering (Matrix, Center Weighted, Spot)
    - Photo Quality (Low, Medium, High)
    - Wide Dynamic Range (Off, On)
    - Photo Resolution (VGA 640×480, 2M 1600×1200, 3M 2048×1536, 5M 2560×1920)
    - Anti-Shaking (Off, On)
    That’s a lot of settings right?
    Well, you will lose those settings if you close the camera application. Ouch!
    I wonder why they even bothered adding a “Restore to default” button at the bottom then.
    The Windows Phone camera doesn’t remember your settings, plain awful.

  • the keypad is mute, not making any noise when dialing the numbers. It feels weird when you’re not used to the sound feedback and there’s no option to turn it on.
  • same for the headsets: they are not ringing for incoming calls, so you can easily miss calls if you’re driving.
  • the alarm cannot be stopped easily if you don’t catch it right away before the screen blanks again within 10 seconds.
    If you miss this spot (probably frequent when waking up in the morning), you’re punished by having to first hit the power button to get out of screen saving mode then find the “dismiss” button (by that time you really need to have your eyes open and able to focus).
    Why not being able to stop the alarm by pressing any button like on the iPhone? That’s enough of a proof you’re awake.
    The alarm also doesn’t vibrate when in vibrate mode, strange.

    1.4 Device specific problems: the Samsung Focus SGH-i917

  • Opposed physical buttons:
    The power button and the volume button are on opposite sides of the phone, at the exact same place.
    This means when you press the power button, you most likely change the volume at the same time
    And worse, the opposite: changing the volume might well lock your phone (or reboot it it you click too long!)
    Looking at other phone designs I don’t see many putting button opposite of each other like this.
    This is not Samsung’s first phone, what were they thinking?

  • The touch screen doesn’t work when the phone is on a table.
    Put your Samsung on the table and just use your finger to play with the touch screen. Sometimes it will work, but most of the time it doesn’t.
    Could that be a hand detection feature that forces you to hold the phone? Or maybe the phone thinks you’re holding it at the ear.
    Either way, that’s a very bad user experience.
    The proof it’s a bug? Leave the phone as it is, just reboot it, and the touch screen will work fine… for a few minutes until the bug appears again.

  • The 3 soft buttons at the bottom of the screen (Back, Home and Search) are too sensitive. You can easily activate them with a normal phone grip.
    If the fatty/muscular part of your hand between the thumb and the palm is too big, you’re in trouble. Luckily I have thin hands, but the problem annoys me already!

  • The keyboard is not as precise as the iPhone. Apple still has superior finger detection and is more precise when typing.

    3/ The Ugly

    Switching from a 2-year old iPhone 3G to a brand new Samsung 3G phone, I expected the signal quality to be better, hoping the advance in technology would make the 3G chipsets better.

    It turns out there was absolutely no improvement.

    Wherever I had bad signals and calls dropping with the iPhone were exactly at the same places as with the new WP7.

    Conclusion: it’s definitely not the device, it’s the network. Hear that AT&T?