crash

It looks like some users who have Gmail on their Windows Phone 8 devices are experiencing syncing issues that eventually cause the email app to crash. The problem seems independent of hardware (so 8X and 920 users are affected) and is tied to Gmail specifically.

The problem occurs with the People Hub and linked contacts constantly syncing. Likewise, when people head to their Gmail inbox, it too is stuck on a constant sync and may even crash when one attempts to scroll the message list. Over in our forums, user moc426 made the above video of the phenomenon occurring, a test which site WinSource has also validated as happening on their HTC 8X.

More →
12
loading...
0
loading...
0
loading...
0
loading...

Rage against the Galaxy

To close out this exciting, Windows Phone 8-filled week, The Nokia Blog managed to get their hands on a few more pics of the Finns crashing Samsung’s party this week at IFA in Berlin.

Previously we had what seemed like a single person with a sign but as it turns out, it was a small crowd of at least 6 people with placards and smiles. What’s more, you can tell Samsung’s security was not to impressed with the brazen display, pulling the signs from the Astroturfers.

While silly jesting, it still pales when compared to what RIM tried to pull off with Apple back in April but clearly Nokia has a bone to pick with Samsung.

See more photos at the Nokia Blog.

More →
2
loading...
0
loading...
0
loading...
0
loading...

Browsing Bild.de can be hazardous to Tango's health

With Windows Phone Tango rolling out it is perhaps not a surprise that some isolated bugs may be discovered along the way. So far, not too many have cropped up but there is one that is interesting though seemingly rare.

Users have found that navigating to the German news site Bild.de on their phone, with “Desktop” enabled can result in the browser locking up the device. The site Bild.de does default to a mobile WAP version and there is a Windows Phone app too but users are free to use their IE9 in desktop mode to view the site “as is”.

We’ve tested the scenario on our Tango phone (Focus 2) and sure enough, upon loading the page the second time it does lock up the device. Since Internet Explorer is a native app, native apps can crash the OS whereas third-party apps should not be able to do so.

The theory seems to revolve around the idea that Bild.de is very graphic intensive with a lot of photos being pushed to the browser. Combined with Tango's low-overhead for 256MB devices and it seems to zap all of the available memory on the phone (of course we can’t rule out javascript errors or something else, either). You can replicate the crash yourself by following these directions:

  • Turn “Desktop” mode on in the browser
  • Navigate to Bild.de, it may load just fine
  • Navigate to another site then go back to Bild.de
  • Browser should crash when loading

The resulting crash means you would have to pull the battery (or hold the power button for 10 seconds) to reboot the phone. We tried this on a Windows Phone Mango device (HTC Titan) and could not replicate the crash. We also had no issues with a Galaxy Nexus with Android 4.1 meaning this most certainly seems correlated with Windows Phone “Tango”.

Is it a dire bug? Certainly not but it could be used as a browser-exploit by some nefarious people out there, even though that seems remote to us. Still, hopefully Microsoft will see this and patch it up for their next OS build.

Update: To make things even more confusing, it's not all devices. Our Lumia 900 with Tango is okay, but reports at XDA of the Radar, Omnia 7, Lumia 800 and our Focus 2 do have the crash.

Source: XDA; Thanks DerAusgewanderte, for the tip

More →
0
loading...
0
loading...
0
loading...
0
loading...

Over at the XDA Developers forum, member z33dev33l has created a thread where he explains that a Nokia Lumia 800 (our review) survived an accidental drop test carried out by his one year old offspring. Before you ask, yes the one year old is a Windows Phone owner. Staying at a hotel (two stories up), the child dropped his Lumia 800 from the balcony where the handset hit the concrete floor below, just inches from the pool edge.

The device itself took the fall graciously with its polycarbonate casing. The only issue is a loose power button, which is still functional. z33dev33l has stated that he can't locate any scratches or marks and the loose button is the only outcome of the two story fall and concrete landing. See the photo above for a blurry look at the loose button, note it's difficult to see as it's flush with the body. Should this test be real then it's an achievement for the Lumia 800 and it's strong encasing. Remember that when purchasing the handset, included in the box is a protective cover too - just in case you happen to hand it to a one year old.

Source: XDA Developers forum, via: MonWindowsPhone

More →
3
loading...
0
loading...
0
loading...
0
loading...

There appears to be an issue with the Facebook app for Windows Phone, with a number of readers reporting the same problem over on our forums. Should you install the Facebook app from the Marketplace and attempt to login you will be greeted by; "Sorry, there was an error." The app generally experiences problems when alterations are made on Facebook's end. A community moderator at Microsoft Answers has been made aware of the issue, but let's hope the team addresses this soon. In the mean time, the Facebook integration still works flawlessly.

Are you having these issues? Head on over to our forum to join the discussion.

More →
0
loading...
0
loading...
0
loading...
0
loading...

The official Facebook application, brought to you by Microsoft, is experiencing some odd crashing issues with some users. Checking the Marketplace for the application and reading some reviews featured on the app summary page displays a clear indication as to the scale of the problem.

We have attempted to reproduce the issue ourselves, and were only able to report one instance (Samsung Focus - another Focus worked however) that experienced crashes when running the Facebook app. It appears (at this early stage) to be randomly tripped with no apparent cause(s) being identified.

Reading the reviews back to the beginning of March, it seems as though it suddenly sprung on unsuspecting users, who are now understandably frustrated. Much like the Youtube offering from Microsoft being a complete flop, this is a serious concern that must be addressed soon to prevent further negativity clouding the WP7 experience and continuing the painful reminder of the pre-NoDo update.

Are you familiar with these recent issues? There is a temporary workaround for posting statuses and commenting on friends updates via the built-in integration the Windows Phone 7 platform sports. At least we have some way of spying on people we dislike while the official gateway to social goodness is unreliable or simply not working.

Thanks mk for the tip!

More →
0
loading...
0
loading...
0
loading...
0
loading...
1

What goes on when an app crashes

Ever wonder where that Windows Mobile error report screen comes from, and what information you're actually sending back to Microsoft if you still have the thing turned on? OK, us, either. But it's nice to learn that the reports actually do go somewhere and are read by someone, as the Windows Mobile blog details:

What you might not know is that this window is generated by Watson, which is a component of Windows Error Reporting (WER). Specifically, Watson is the client-side executable that is activated when an unhandled exception occurs on your phone. Watson is responsible for preparing an error report (stack details, system information, variable information, etc), notifying the user about the error (happy window), and with the users consent sending the file to Microsoft (via data or ActiveSync). Assuming the user chooses to send the report, these encrypted files are then added to a WER database where they can be reviewed by Microsoft technical support personnel and Microsoft developers.

There's plenty more developer mumbo jumbo to be had in the full post, but it is an interesting look behind the curtain.

More →
0
loading...
0
loading...
0
loading...
0
loading...