UPDATE: WhenWillApple thinks they know what’s going on with the 3.1 fix.
Looks like the tempest has run out of room in the teapot, as that bug we linked to earlier, about iPhone 3.0 Spotlight showing email messages that should be well and truly deleted, seems to have indeed been crushed in iPhone 3.1.
Matt Janssen has discovered what looks like a bug in iPhone 3.0 Spotlight, whereby the search feature keeps emails in the index/cache even after they’ve been deleted from the inbox and purged from the trash (and even obliterated from the host server). Janssen claims in the video above he’s found emails he deleted several months ago using this method.
Email is likely cached to speed up searches. Initially tapping on a deleted email in a search result will launch Mobile Mail, which will promptly crash, but searching and tapping a second time will actually show the email, albeit in a buggy manner.
Engadget (via CultofMac) has heard this bug might be fixed in iPhone 3.1, now on Beta 3, and perhaps to be released as soon as Apple’s next iPod/iTunes event rumored for the week of September 7.
No doubt about it, issues with battery life remain a hot topic for iPhone 3.0 and iPhone 3GS users.
Now, if your battery drain is caused simply by use — you never put the iPhone (or iPod touch) down and are always playing games, pushing IMs, watching movies, etc. your only choice is to get a few more charging cables or battery extenders. If, however, you’re doing roughly the same things you’ve always done and getting substantially less battery life for your troubles, there’s a chance a few troubleshooting steps might just help get your power problems back under control.
148apps posted up a PR from a developer in the Czech Republic that states:
“When the Push based application such as NotifyMe requests an ID from APNS, the server responds within a second and identifies the device with the unique token. From that point, the connection between APNS and user’s device is successfully established,” said Pavel Serbajlo, PoweryBase’s lead developer. “However, on a unofficially activated device, APNS keeps the application wait forever and does not provide any respond at all, keeping user wait infinitely or time out the connection, if the target application is capable of timing out.”
So that makes us wonder, is Push Notification really not working? And if it’s not, is Apple really blocking it, or is it just not set up to recognize some Jailbroken iPhones that weren’t activated in the usual way via iTunes?
Apple has updated a knowledge base article for those “Unable to use Wi-Fi or Bluetooth with iPhone or iPod touch because there’s no address listed for the device”, which is something we’ve heard quite a bit about lately. The four-pronged approach:
Settings > General > Reset > Reset Network Settings
Settings > General > Reset > Erase All Content and Settings.
Restore the device via iTunes
Take your iPhone or iPod touch in for repairs.
Apple finishes off with some extra advice:
If the device shows an address in the Wi-Fi Address field and you are still having issues using Wi-Fi, refer to article 305715 for additional Wi-Fi troubleshooting tips. If the device shows an address in the Bluetooth field and you are still having issues using Bluetooth, refer to articles HT1843 and HT1664 for additional Bluetooth troubleshooting tips.
If any of that works for you, let us know in the comments. If it doesn’t, let us know as well…
Back when iPhone 3.0 launched, we heard Wi-Fi was giving problems to some — primarily iPod touch — users. Various network resets or OS restores seem to have quieted that down, but now TUAW is reporting that the newly launched iPhone 3GS might be suffering Wi-Fi troubles as well:
Users note that signal strength can fluctuate between one and full bars even when standing right next to the router or when a computer nearby shows a constant signal. This goes along with a commensurate reduction in speed.
Neither Jeremy nor I have been experiencing this, but if you have, let us know in the comments, along with what type of router you’re running, and what kind of speed/connection quality you’re getting (or not getting, more precisely).
(Wether this is, in fact, a widespread problem and one corrected by iPhone 3.1 we don’t yet).
Since the iPhone 3.0 Jailbreak has become available, and now with both purplera1n and redsn0w coming on line with iPhone 3GS Jailbreak solutions, we’ve heard rumblings about problems with Push Notifications not working, or not working properly.
we have some remaining 3.0 jailbreak issues to investigate, including push notification
danmowchan in our forums notes this again today with regards to Prowl. Potential battery drain issues aside, if you’ve Jailbroken, are you having trouble getting your Push on? If not, has problems with Push made you put your Jailbreak on hold?
Back when Apple re-introduced Push Notification at the iPhone 3.0 Sneak Preview Event, Scott Forstall claimed that, unlike background multitasking that could cause an 80% drop in battery life, Push Notification would only cause a 20% drop. While some debated the truth (or truthiness) of his claims, it did set the expectation that users running Push Notification-enabled apps would see lower battery life, and gave an indicator of just how much less.
So, while it too a while, now that we finally have Push Notification, and some of the more popular messengers and games are implemented it, how’s your battery life doing?
Are you seeing a hit compared to your pre-Push Notification days, and if so, is it in the 20% range? Let us know which iPhone you have, how often you’re getting Push Notifications, and how your battery is holding up!