A number of Windows Phone 7 users in the past month had reported about a mysterious bug on their handsets that caused unrequested consumption of massive levels of data. The complaints, nicknamed the Phantom data issue, prompted Redmond to have an immediate look into the issue.
The company has now issued a statement noting that they have managed to round upon the potential cause to a common “third party solution” that was seen to be consuming larger than expected levels of data. Microsoft is noted to be working with its partner to rectify the issue. No details were made available regarding the third party in question.
Microsoft has also additionally pointed out that the number of customers affected was not significantly high noting that a “low single-digit” percentage of Windows Phone customers were affected. We will update you when the aforementioned fix is released.
A new bug on the Android operating system seems to be affecting a number of Google Nexus S users. According to complaints posted on the Google support forum, the bug on Nexus S causes the phone to reboot randomly while making a phone call. Some users have been experiencing this every other time while others have been facing the issue only once in a while.
Fortunately though, unlike the Android random SMS recipient bug, Google seems to have rounded upon the possible root-causes early enough and have reported that they are now trying to reproduce the bug and consequently find a fix for the same. Samsung is noted to be working with Google on this issue.
We will let you know when a fix is released. Have you experienced similar issues on your Nexus S? Tell us in the comments.
For more than a year now, Android users have been reporting a bizarre bug on their handsets that sends text messages to a wrong contact from the address book. Several long-running threads on the Google Support forum are littered with complaints from users who have been affected by the problem.
Finally, it looks like Google may have succeeded in rounding upon the actual source of the bug. According to a new report on BBC, the company has developed a fix that it shall be rolling out to Android handsets shortly. Speaking to the BBC, Android security team engineer Nik Kralevich said,
“It took us some time to reproduce this issue, as it appears that it’s only occurring very rarely. Even so, we’ve now managed to both reproduce it and develop a fix that we will deploy.”
Kralevich did not however elaborate on an estimated time for the rollout.
A lot of iPhone users had a rude awakening this new year when their alarm failed to go off. Apple soon acknowledged the problem with the following statement,
“We’re aware of an issue related to non repeating alarms set for January 1 or 2. Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3″
January 3 (or 4 depending on where you are located) is already here but it looks like the issue is still noticed by a number of users. If you are one of those being affected by the issue, you can set a recurring alarm instead of the non-recurring one that you have set currently. This will prevent the issue from recurring, at least in the short term.
Meanwhile, the iPhone alarm bug seems to have affected a number of travelers and office-goers. Here are a couple of comments from our earlier post about the issue.
“Im a cabin crew, I set my alarm for my 5:45am sign on after new year’s eve. I almost miss my flight and might miss my job for this! Thankgoodness the crewing phoned and woke me up and just went straight away at the aircraft without our usual crew briefing.”
“I missed my 8am flight on Jan 2 due to this alarm malfunction and it cost me $469 to get a new ticket that would get me to Miami in time for the Orange Bowl. Wonder if Apple will reimburse me? Ha! That is the LAST time I’ll rely on my iPhone alarm without backup. C’mon Apple where’s the QC??”
“2 hours late for work after the 2 non-recurring alarms I set failed. The extra sleep was nice though”
Yet another bug with the iPhone alarm. A number of iPhone users seem to have overslept on New Year’s day thanks to a bug in the alarm app that has caused non-recurring one-off alarms to malfunction. Users have complained that their alarms failed to ring in at the scheduled time since moving into the new year. There is a workaround for the time being – set the alarm in recurring mode which however means you will have to disable it after you wake up in order to stop the alarm from ringing again the next day.
For what it’s worth, reports note that the bug only works if the phone clock actually ticks over from 11:59 PM on December 31 to 00:00 on January 1. Also, the bug seems to autocorrect itself after January 3. This means it is just a minor hassle for those of you looking to set alarms for January 1.
Did you notice this iPhone bug? Tell us in the comments.
Over the past couple of months, a number of Apple TV users have been complaining that downloading HD movies over iTunes seem to be taking an inordinately high amount of time. We had initially diagnosed the problem as one with the internet connection. However many users who were on high speed internet plans noted that this could not have been the case.
Apple had released a software update last week that was apparently aimed at fixing this issue. The update fixed this along with other bugs on Apple TV including flickering displays and improper HD rendering.
It has now been noted that there could be yet another issue plaguing Apple TV users – one with the DNS set up on their connections. Reports suggest that users who have set up their DNS over centralized systems like Google DNS and OpenDNS could be the ones to be suffering from the long download times. These reports suggest that users who download content via Apple’s servers, the Akamai Content Delivery network do not seem to be facing these issues.
There is not much clarity on why this is the case. In any case, if you are someone who is still affected, why not try out an alternate DNS configuration to see how the downloading works? Don’t forget to tell us how it works in the comments below.
As we had reported earlier in the day, Apple has released an update to their iTunes media organization software that is aimed at fixing a number of bugs in the earlier version. Ironically though, the installation process itself seems to have been affected by another bug.
A number of users have taken to the Apple support forums complaining that installation the new version via a software update seems to be crashing the application. Users have noted that launching iTunes subsequently shows them an error message that reads, “iTunes cannot be opened because of a problem“.
Here is an excerpt of the problem faced by some users
“I had the same problem as all of you mentioned. I let automatic updates install the new version of iTunes 10.1.1 and iTunes would not open afterward.”
“I had this problem on one of my two machines. One of them installed and updated fine from Software Update – I think that on the machine where it worked, I hadn’t run iTunes between turning it on and running Software Update. On the machine where it failed, I had run iTunes.
The crash report indicated that it was looking for a shared library named:
which should be present in /Applications/iTunes.app/Contents/MacOS, but wasn’t there after the update. The shared library (and some others) were present in my Time Machine backup, but restoring the pre-update versions didn’t fix the problem – iTunes would now launch without flying a crash reporter panel immediately, but reports that it’s corrupt and wants to be reinstalled.”
So do we have a fix here? Users note that reinstalling iTunes directly from the website seems to be fixing the issue.
“I installed this via Software Update, and iTunes immediately crashed after launching. The error detail indicated that some dynamic library could not be found.
After a reboot didn’t fix it, I downloaded the standalone installer from here:
Ran it, all’s well now.”
So if you are one who is affected by the issue, try downloading the new iTunes version directly from the Apple website here and let us know how it works in the comments section.
It was only recently that we had written about a bug on the iOS 4.2 platform that resulted in a number of mobileme users noticing a “password error” message while trying to access mobileme. You can check out the possible resolution methods for the bug by clicking here.
Now we are hearing about yet another login related trouble with mobileme. Apparently, this time the problem is not with iOS 4.2, but a new password policy from Apple that targets users with short and easy passwords. According to the new policy, mobileme accounts should now have passwords that are at least 8 characters long and need to contain at least one number and letter.
Users who have short passwords not fulfilling the criteria are thus seeing a message from Apple prompting them to change passwords. However, a section of users are also complaining that the change is invisible and simply displays login failure messages to users whose passwords do not meet the criteria.
If you are one of those users seeing such errors, simply reset your password to fulfil the new criteria and that should do.
Bugs on Apple’s latest iOS seem to be cropping up one after another. We have earlier written about a number of issues users have been facing since they upgraded to the latest iOS 4.2. For instance, some found their music libraries go missing, others complained about their iDevice not being able to connect to their car stereo or to the 3G network.
Now adding up to Apple’s woes is a new issue with the iPad Wi-Fi network. A number of users have been complaining that their tablet is noticing an extremely slow Wi-Fi connection since updating to the latest iOS. A thread on the Apple support forums, spanning close to 700 posts has a lot of users posting about the issues they have been facing.
“My wifi is incredibly slow after I upgraded two of the three iPads in my home to iOS 4.2. The other iPad that has not been upgraded works fine. In a side by side test loading the same web page, the iOS 4.2 iPad takes 5x as long. Any ideas on why this would happen?”
“After iOS 4.2 installation the wifi connection is very slow. Unusable. Other mac and pc work fine on the same wifi lan. There are other posts on this subject, I believe this is a true bug.”
The issue is not with all iPads and the problem appears to be rather selective. In any case, if you have been affected, you may try out these solutions. Seems to have worked for some.
“I had the same problem with Ipad appearing to have a connection but IP is 169.xxx.xxx.xxx, Here is what I did that so far worked,been connected for 3 days straight now.
- Reset/forget the network on iPad.
- Change security on your router to just wpa2-aes only .( might have to retype your password again)save and restart router.
- I’m not sure if I did a reboot on my ipad but wouldn’t hurt..find your netwrok and connect…that’s it.”
“I changed the passwords for my Main network and my Guest Network. After doing that, the utility instructed me to disconnect my modem’s power cord for a couple seconds and reconnect. I should say that I had already performed the disconnect of my modem’s power supply before. That accomplished nothing. The difference here was that I had changed the passwords of my two networks first.
If you read my last post, you know that I quoted terrible video performance for two specific apps…AppAdvice and MLB at Bat 2010. So, after doing the above I tried playing videos on both apps. FLAWLESS PERFORMANCE. OMG!”
Did these tips work? Tell us in the comments.
Apple introduced a dongle named the Camera connection kit along with the iPad back in April this year. This is a nifty accessory that lets users to connect their digital camera to the iPad in order to quickly import or browse images from a digital camera on the iPad.
As users who purchased the dongle have noted since then, the camera connection kit was also capable to connecting to other USB devices like the keyboards, microphones, etc. No longer. Users who have updated their iPad to the latest iOS 4.2 platform are reporting that the dongle is no longer capable of connecting the iPads to devices that consume more than 20mAh.
This limitation does not restrict the accessory’s original function that is to help users connect the iPad to a digital camera. But for those who were thinking of alternate use-cases, the dongle no longer seems to be a useful device.