Reports are coming in that iPad 3G users who have upgraded their tablets to the new iOS 4.2.1 platform have been noticing slow or broken 3G connection since the update. While some users seem to have problems with connecting to their 3G SIM card, others users complain about their tablet frequently switching to the slower Edge network. The issue appears to be coming from several countries and is not restricted to any particular geography.
“I am in the US and after update 4.2.1 my ipad cannot connect with valid 3g sim card that i have been using for 4 months on ipad. i took the sim card out of the ipad and tested it on my iphone 4 and it works fine. the ipad is telling me that my cellular data plan usage has expired. i am using my sim that is unlimited.”
“After upgrade to the new OS 4.2.1 last night, I lost the 3G connection with the iPad. only Edge Connection.”
“My iPad 3G signal at work has gone down the pan since the 4.2.1 update. Instead of 3-5 bars depending on where I am in the office it has dropped to 1 or 2 bars in the best locations and if I move around too much I lose the the signal completely.”
Yet another bug with the new iOS, people. If you are an iPhone 3G user who has officially unlocked your handset to migrate to another carrier that Apple has not partnered with, you may be better off holding back on your iOS 4.2.1 update. This is because a number of users, primarily from Europe, who have made the upgrade have noticed that the update has caused the Internet tethering options on their phone to disappear!
This could be annoying because many of these users pay for the tethering option. Apparently, the bug is because the new iOS does not carry forward the carrier settings when making the update. If you are on a carrier that is contracted with Apple, this should happen seamlessly and you may not be affected. However, iPhone users on other carriers lose the tethering options on their handset completely. The issue does not seem to have affected iPhone 3GS and iPhone 4 users.
Apple has not acknowledged the issue so far and the only fix right now appears to be downgrading your iPhone to the older iOS 4.1 firmware. In case that is not a process you are comfortable with, you do not have an option but to wait for an official fix to come your way.
Every new iOS update seems to be causing some issue or the other with respect to establishing connection with car stereos. Several iPhone users had reported having problems with pairing up their device with a car stereo after upgrading to iOS 4.0 earlier this year. While this was apparently resolved with iOS 4.1, that update brought another issue with many users observing intermittent crackling noises.
With the release of iOS 4.2 (actually iOS 4.2.1 ), problems seem to have cropped up once again. Several users have been complaining that they are having trouble connecting their iPhone to a car stereo over USB. Connecting a device displays a “Device not supported” or “Unreadable” message instead.
At the moment, Apple has not offered an official acknowledgement of the issue. However, there are some reactions from users who have been able to get some details about the issue.
“I have spoken to my local Volvo dealership and they are aware of the issue, and claim that Volvo have raised the issue with Apple and are awaiting a response. Not sure whether that will have much effect – but at least they are aware. Volvo are expecting an Apple patch to solve the issue rather than a car based fix – so we may have to wait for the next iOS update.”
Unless you slept through the whole of yesterday, you may have definitely heard that the new iOS 4.2 update for Apple devices is already available for download over iTunes. The update introduces users to a number of new features. But as several users have been noticing, this update seems to be causing all music on your iPod app to vanish. Users launching the iPod app on their iPhone or iPod Touch may find that their music library no longer exists.
Apparently, this is a bug and it doesn’t actually deletes your music library. Instead, it only stops from showing them. To fix this, carry out these following steps
Step 1 : Connect your iPhone to the computer and launch iTunes
Step 2 : The iPhone will now be listed on the iTunes sidebar. Click on the arrow besides it and select Music. Playing a song on iPhone via iTunes should play the music on your computer.
Step 3 : Now, sync the phone again
You are done. Disconnecting iPhone and relaunching the iPod app should bring back all the lost music. Did it work?
We now hear that the recently released OS X update may have finally brought a patch to the flickering display bug. A new support document that has been released by Apple has noted that the new Mac OS X 10.6.5 released last week would fixed the display issue.
If you are a user who has been suffering from this issue, do update your computer to this latest update and let us know if it resolves the problem.
Yet another security flaw on the iOS 4.1 has been discovered. And this time it will let users bypass the mandatory input of passcode to let users access private details like contacts list, recent calls, voicemails,etc. The security bug will also let users send emails and MMS messages without having to know the passcode. How […]
Yet another security flaw on the iOS 4.1 has been discovered. And this time it will let users bypass the mandatory input of passcode to let users access private details like contacts list, recent calls, voicemails,etc. The security bug will also let users send emails and MMS messages without having to know the passcode.
How do you do this? Simple. Users simply have to tap on the ‘Emergency call‘ option in the Passcode window and once here, dial a non-emergency number like #### followed by a tap on ‘Send‘ and quickly followed by pressing the iPhone lock key. This will force the user on to the iPhone’s phone application from where all these private details can be accessed.
Check out a video demonstration of the bug.
Do not expect an immediate resolution of this bug though. Apple is expected to release the new iOS 4.2 early next month and it is possible that the bug is attended to only in this update. Or probably later.