03-12-2012 10:02 AM
Im trying to use the Playbook for presentations...but NOT using HDMI output.
I understand the reasons BlackBerry gives for batter life etc...but it doesn't help
me AT ALL. I'm trying to speak from an outline created in Docs To Go. The
Docs To Go app goes dark after 5 minutes and I lose my place. The new OS2.0
update helps a little with the highlight color choices, but it sure would be nice
if I didn't have to swipe the screen every 5 minutes!!!
I've gotten frustrated a few times and gone back to paper...but the Playbook
is suppose to help me go digital. Why cant I have the option to choose more
than 5 minutes????? If I kill my battery, isn't that my choice? As you may be
able to tell...I'm a little frustrated.
03-12-2012 01:30 PM
I tried Battery guru's keep awake feature, it will keep itself awake but even in showcase mode, will NOT keep browser or stopwatch awake. Useless sort of stopwatch!
03-12-2012 01:34 PM
03-12-2012 04:34 PM
OK I thought Showcase allowed the battery guru app to be active but in the background. Fortunately 5 minutes is long enough to soft-boil my eggs.....
03-12-2012 05:07 PM
04-04-2012 07:31 PM
im not being funny but i just want it to stay on, i dont want to run apps in the background. why dont they just fix it. if i'd have known about this b4 i bought 1 id prob not bothered id have gone 4 something else. i think a lot of ppl have heard about this now thats why sales have decreased.
it goes off while im playing on my betting site and more importantly it goes off when im watching videos (of the adult kind lol) (no one else would say it) i dont want to be touching the screen every 5 mins IM BUSY.
this customer support is prob why everyone i know with a bb phone is waiting until they can upgrade to get rid. leaving a sinking ship.
rim in administration by the end of the year????????????
by the way i love my playbook otherwise.....
10-19-2012 11:47 AM
I appreciate that the forced-standby thing bothers many people, and in fact it bugs me at least when I have the unit plugged in.
With respect to timer-based applications which fail to keep proper track of time while inactive, those apps are simply defective. The developer of such an app has implemented an incorrect design, or implemented a good design incorrectly.
I have a simple time tracking app that I wrote myself. Still crude, unreleased. It works perfectly well whether it's active, inactive, the tablet is on standby, shutdown and left overnight, or battery drained completely. Showcase, Default, or Paused mode, no difference. Every time you go back to it or restart it, it accurately shows the elapsed time since you started the timer, and the live display is perfectly on track.
There is no excuse for timer apps which can't do this, other than lazy or bad programming. This isn't a difficult thing to do either, but it is something that rookie programmers may not have learned or figured out on their own how to do.
Said with respect to those programmers who are still learning... but please don't blame the PlayBook for problems that are the fault of bad apps.
(Note: a count-down timer app that is supposed to actually make a sound, for example, when the timer expires, would have to take advantage of the special QNXSystemPowerMode settings or the setAlarm() feature related to that, or it wouldn't alert the user when the device was in standby. My above comments related solely to the "not tracking time in realtime" part of things. There are several ways to code timers, and the wrong ways don't notice the passage of time when the app isn't active, while the right ways mean the app's timer is right back where it should be as soon as it becomes active again. The setAlarm() function merely gives it a moment of "activeness" to sound the alarm, but does not by itself do anything to fix the basic bug of missing the passage of time while inactive.)
Said with all due respect to you sir, this is stupid. You say your developing an app and that the apps devopled that do not take into consideration the timeout feature of the playbook is their problem but you are wrong. Teh timeout feature is a setting that should have an option to not be used, a dev would not take this into consideration as it is something that should be a basic feature already working correctly.
RIM dropped the ball here without giving the user the option to keep his device on full time, this is a basic feature and one that is a must for a decent device. I am reviewing the playbook and this is a major con to the device that I just discovered. This would be a major downcheck in features and ratings as many of the devices apps would be affected by this sort of basic functionality.
10-19-2012 12:06 PM
10-19-2012 12:21 PM
Peter's right - but this is all a bit of a red herring! - the point is that regardless of whether an app is well-written or not, it should be possible to make the **bleep** screen remain ON.
Even when the thing is plugged into mains power, you still can't select to have it on all the time. It's absolutely ridiculous and I defy RIm to come up with a justification - if they ever read any of this stuff, which I doubt.
I really hoped that this would be fixed in the latest 2.1 release, but no. RIM seem to have absolutely no idea how to make a tablet that people want to actually use. I'm giving up and getting an iPad.