What's wrong with 184.108.40.2068
So, RIM recently pulled the update, and a lot of people on the forums have been expressing hate towards 220.127.116.118. I don't understand though, everything works fine for me, what are the problems you guys are facing?
Why has RIM pulled the update?
Should I also restore back to 18.104.22.1688?
(BTW I do have the 22.214.171.1248 debrick image that I can CFP at anytime).
I also noticed that the build date for .668 was June 12, which means they must have had plenty of time to test it on the WiFi PlayBook right? Might someone had accidentally released .668?
- 08-04-12, 08:27 PM #8
It's been good for me also. Fixed my duplicate folders in email. Battery life is about the same, took it off the charger at 2:30 and have been using it quite a bit, went out to dinner and have been using it steady since I got back home. It is now 8:26 and I have 44% left. I took my Acase off to see if it felt hot, nope.
Edit: almost constant use it is now 10:33 and 21% left. This is better than I got before .668.
Last edited by kbz1960; 08-04-12 at 10:34 PM.
- 08-05-12, 03:08 AM #9
There's several reports about abnormally rapid power drain resulting in a PB that becomes very hot to the touch. Whatever the cause, to pull the update after 1 day shows it wasn't seen as a minor issue.
Last edited by JeepBB; 08-05-12 at 03:11 AM.
- 08-05-12, 05:29 AM #10
Mine is running fine with 668 but i am going back just in case. I cant have this starting to have problems when i am on the road as i will be away for a few days.
What were they thinking when they released this.
- 08-05-12, 06:06 AM #11
So this time I turn off my playbook instead of standby. That fix the battery drainage. Still a pain to start the tablet. But I am staying with this update. A minor thing happened when I turn off my tablet. It turn back on by itself a few minutes later. So I have to turn it off again.
- 08-05-12, 06:41 AM #12
It's OK tho', I notice it's apparently not newsworthy enough to warrant an update to the CrackBerry front-page puff-piece announcing the availability of 668.
To be fair to RIM, whilst I'm sure they tested it thoroughly, any device as configurable as the Playbook will undoubtedly present corner-cases in individual setup that cause bad things to happen for some PB users. Though it has to be said that any issue serious enough to cause the update to be pulled within the day doesn't inspire confidence in the depth of the testing that was performed.
Nice fish by the way...
Last edited by JeepBB; 08-05-12 at 06:47 AM.
- CrackBerry Abuser
08-05-12, 07:42 AM #14
- 176 Posts
- the tail on the donkey
Calendar issues with this build
Has anyone had issues with adding appointments with attendees to the calendar since the maintenance update? I have issues with syncing to Google calendar and when i try to delete the appointment from the playbook, it refuses to delete. I have hard reset, deleted information out of the fields etc, all to no avail.
- 08-05-12, 08:57 AM #16
668 Kobo issue
For me the .668 update fails because, since installing it, my playbook will only load a book from my Kobo library when connected to the internet. Which makes it pretty much useless as an e-reader at the moment. Unless I decide what I want to read before I leave the house.
Does anyone know how to revert to the previous OS (bearing in mind that my desktop machine is a mac)?
- 08-05-12, 11:03 AM #19
Speculation why RIM pulled the update:
All the ******** and whining on Crackberry.com about RIM not releasing OS 2.1 pissed them off. (Picture Soup Nazi: No OS updates for you!)
668 was only supposed to fix the security vulnerability in Flash. And everything we are experiencing is a placebo. Engineers at RIM are scratching their heads...they are trying to reverse engineer the placebo effect for stronger wireless signal and fix app lag issues. Then they can implement same placebo magic into Blackberry 10.
- 08-06-12, 04:38 AM #21
668 kobo problem ongoing
Certainly it's possible to get the DM to offer a 'restore to original' (I've forgotten the exact phrase) facility, but that wipes all the data/media/settings. Although it should be possible to restore most of that using the synch facility my natural pessimism makes me want to avoid that unless it becomes the only option!
- 08-06-12, 06:13 AM #23
kobo problem part-resolution
Since my earlier posting I've been trying different things with the Kobo app itself and found a workround that is a bit tedious but does the job. I will include it here in case others may find it useful.
The sequence is as follows:
1 Start the Kobo app. Normally it should open at whatever page one was last reading. Under .668 the bookmark shows but instead of text there is a continually spinning wheel. None of the options in the top bar are operational.
2. Swipe down to get rid of the menu.
3. Swipe down to reveal menu. This time the options work, but the book still doesn't load to the screen automatically.
4. Choose library and select the book you want. It will open at the bookmarked page.
5. Marvel at the perversity of inanimate objects.
It would be good to think that Kobo would provide an update to match the most recent iteration of the OS. Or that BB would patch the OS to match the Kobo app. Perhaps they could talk to one another?