Newstand can't be placed in a folder. At least on my 3GS I'm not able to do it. This must be a bug.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Begins Seeding of iOS 5.1 Beta, Xcode 4.3 to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Newstand can't be placed in a folder. At least on my 3GS I'm not able to do it. This must be a bug.
Yes it can. It's not supposed to be but there is a glitch where you can.
http://www.youtube.com/watch?v=ujTDVgReBUQ
Why wouldn't you be able to restore to earlier versions of iOS after upgrading? An earlier restore always seems possible. 
Your previous post, to which I was responding, was, itself, a response to a post about a video driver bug. You included the following quote
MY main point is that the video driver bug refrenced in this quote (given the other link associated with this issue) sounds like a very strong candidate for many of the battery problems experienced on BOTH iPhones (4 and 4s). Let's hope it is and that it's addressed in the new release. It was a very good find with some clever research done by an italian iPhone developer.
Pete
Last edited:
A video driver bug would affect all phones. There are tons of units out there that have normal battery life (mine is one).
Why would it have to? Like any bug, what if it only manifests itself with a certain set of obscure circumstances? There are plenty of examples of bugs in video drivers that only manifest themselves to certain customers.
It's not the device :
It's some kind of software configuration on some devices. Notice I have bluetooth on, I have Siri "Raise to speak" enabled, and that usage is mostly Music listening and playing Infinity Blade.
Zero visible improvements. Unable to put Newsstand in a folder trick as Apple considered it a bug.
I understand the point you are making, and that could very well be behind it all or part of it all. In my original response I was mainly pointing out that the comments, which seemed to imply that things were limited to the 4S, wouldn't quite be accurate given how many 4 phones are experiencing the same kind of battery issues after upgrading to iOS 5.
Absolutely wrong.
As a successful software developer, I can tell you without question, that bugs in ANY one piece of software can exist such that they appear to any conceivable percentage of users.
The developer who found this bug proposed the theory that only certain apps are triggering the video driver bugs. There is NOTHING inherent in video driver software to preclude this. The bug might require a call to certain video functions; calls to specific functions with specific parameters; calls made in a specific sequence; certain values existing in uninitialized memory; and on and on.
I love when people state something as absolute fact, while, at the same time, demonstrating zero knowledge of the subject. There's nothing wrong with having an uninformed opinion, but you'd be far less subject to ridicule (and be far less abrasive), if you'd label it as such. A few words such as "I would think" go a long way
Pete
Last edited:
Any fixes for iTune Match bugs:
-Play count not syncing
-Last Played not updating
-Smart Playlists not obeying criteria (limits especially)
-No Genius Playlists
-Album Artwork not downloading
??????????????????????????????
-Play count not syncing
-Last Played not updating
-Smart Playlists not obeying criteria (limits especially)
-No Genius Playlists
-Album Artwork not downloading
??????????????????????????????
As also a trained software developer, I can tell you you're forgetting one big piece of information we have : Stand-by time. Ie, we're all basically running the same code as far as video drivers go : the lock screen (with the screen turned off mostly I'd bet).
Apps by that point are suspended or doing their background tasks only (since we're talking overnight here, not just locked for a few minutes in which the foreground app remains in the foreground), which does not include using the frame buffer or graphical rendering :
http://developer.apple.com/library/...w.html#//apple_ref/doc/uid/TP40007072-CH4-SW3
Next time you want to bully, pick your victim a little more wisely.
While I don't question the qualifications of that Italian guy, I do question his conclusion and to state his opinion as fact is quite wrong. There's more than 1 model type affected and not all units are even though they are all running the same code (these are not jailbroken units as far as the 4S is concerned). Let Apple sort it out, we're not going to be the ones to figure it out and fix it (not having access to the full source code and having no way to do actual on device debugging at the lower levels of the OS).
But again, I don't know about you, but my iOS devices wake up every few minutes or so to display one notification or another. So it's still possible that within that "standby" time for some of us, the Phones aren't constantly "standing by" if you know what I mean. (Of course, I haven't tested completely turning off all notifications and things, because I like them more than low battery life has affected me on my 4S). And even if not, who knows if the bug isn't also related to background tasks
Not saying the graphics driver is a definite conclusion- just saying it can't necessarily be ruled out.
But again, I don't know about you, but my iOS devices wake up every few minutes or so to display one notification or another. So it's still possible that within that "standby" time for some of us, the Phones aren't constantly "standing by" if you know what I mean. (Of course, I haven't tested completely turning off all notifications and things, because I like them more than low battery life has affected me on my 4S). And even if not, who knows if the bug isn't also related to background tasks
Again, by that point, we're all running the same code as far as graphic sub-systems go. The notification graphics system is not different on my 4S' lock screen than it is on yours. Sure notification spam will affect stand-by time (that could be an issue, but then again, I think someone having battery issues would notice the hundreds of notifications and probably look into it
) and same for background tasks, none of them include actually drawing out anything. So yes, I'd say the graphics driver bit is quite on shaky grounds based on this information. To say I'm "absolutely wrong" when pointing out it doesn't really make sense in the context of stand-by time is quite a bold statement to make, especially then backing it up with credentials and just plain forgetting the meat of the issue.
And again, "ruled out" is quite useless at our level. All we can do is try to play with options and close open apps. iOS is not the paragon of customization here. Let Apple debug this thing. Obviously, it's not affecting every unit (and since it's affecting units outside of the 4S like the 3GS and 4 running iOS 5, I'd dare say it doesn't seem to be something that would be caused by a model specific system like a graphics driver).
Well, I didn't say you were "absolutely wrong". Just that based on the information, you weren't necessarily "absolutely right"
And I'm sure a lot of the things we talk about here are "useless"- doesn't mean they aren't worth discussing and considering the possibilities. It's not as if the "graphics driver hypothesis" is so out of line with reality that it's not worth even a second thought.In the end I'm sure Apple will list the fix again as "Fixes Bugs Affecting Battery Life"" without pointing to the exact cause
I wasn't referring to you either. I was referring to the post to which I initially replied by PeteLP.
Battery Life currently is:
Usage: 2 Hours, 23 Minutes.
Standby: 22 Hours, 12 Minutes.
65% still left. I say my battery got improved.
Usage: 2 Hours, 23 Minutes.
Standby: 22 Hours, 12 Minutes.
65% still left. I say my battery got improved.
Note: Here's a good thing, if you want to downgrade from 5.1 to 5.0.1, it's possible. Just DFU and restore.