.2072 new active frame behavior driving me nuts!

It's done that way according to an inside programmer so as to save on cash memory and prevent other apps from using most of your ram while running in the background, so I'm told. Does that make sense to any of you?

If the active frame is frozen when minimizing, it makes no sense to me that there would be any additional penalty vs using a previously cached image versus and taking a new one, since the the minimized app already has the updated frozen screenshot before it then decides to swap it out with an older one. It would seem the switching of the images would be a penalty. Even if there is a performance benefit to this behavior (which I doubt), I think user experience is more important. I doubt Android or iOS do this, and BB is supposed to be the better multitasker...

Not seeing this issue on mine with Z30STA100-3/10.3.1.2072 installed destructively a couple days after leaking, and a full restore. Apps that should change, such as pictures and BBM do, those that shouldn't such as browser and settings don't.

It's a leak, and even if it wasn't results will vary. Possibly reloading the OS would resolve it, or there's a setting I haven't found, or an app is creating a conflict. Either way it's a leak. Don't like it, try something else. Certainly not BlackBerry's fault you don't like it.

After severe Remote Access problems, I decided to wipe and set up from scratch. The method I posted earlier to reproduce the bug does not work anymore now. It now behaves correctly as Big Bad Wulf describes.

Hmm, I had upgraded via blitz, then security wiped, then downgraded via BlackBerry link then used an autoloader then formatted again.... I thought that was enough.
Besides my passport arrives tomorrow so I might stick to official for a little bit.

Hmm, I had upgraded via blitz, then security wiped, then downgraded via BlackBerry link then used an autoloader then formatted again.... I thought that was enough.
Besides my passport arrives tomorrow so I might stick to official for a little bit.

There are reasons, stuff to do with having to wait to go to work so I can access a windows machine to run an autoloader. I'll admit it's not my usual list of steps. I'd normally try a blitz and if it fails hit it with an autoloader and maybe a wipe to be sure (I've never had any problems that aren't inherent to the leak yet). I still don't get how this could have bodged it as technically the autoloader should supersede any prior steps... But then again, loading leaks is sometimes more like alchemy, sometimes it just doesn't work and there's no good reason.

It's done that way according to an inside programmer so as to save on cash memory and prevent other apps from using most of your ram while running in the background, so I'm told. Does that make sense to any of you?

Yep I can understand the idea but it goes against the BlackBerry flow we all love so much. I can't imagine a couple of thumbnails saving enough ram to make this worthwhile considering bb10 runs great even on the older z10 q10 hardware. Let's hope they revert this back to the old behaviour before they go live with anything official.

There are reasons, stuff to do with having to wait to go to work so I can access a windows machine to run an autoloader. I'll admit it's not my usual list of steps. I'd normally try a blitz and if it fails hit it with an autoloader and maybe a wipe to be sure (I've never had any problems that aren't inherent to the leak yet). I still don't get how this could have bodged it as technically the autoloader should supersede any prior steps... But then again, loading leaks is sometimes more like alchemy, sometimes it just doesn't work and there's no good reason.

Posted via CB10

My money is on the security wipe messing things up, and an autoloader doesn't wipe everything, every time. I'd do a cfp nuke if anything, but only if necessary, like after a security wipe.

Originally Posted by tomh235

Yep I can understand the idea but it goes against the BlackBerry flow we all love so much. I can't imagine a couple of thumbnails saving enough ram to make this worthwhile considering bb10 runs great even on the older z10 q10 hardware. Let's hope they revert this back to the old behaviour before they go live with anything official.

Posted via CB10

They don't need to fix anything. It works fine on my Z30. Honest to G_d.

It's done that way according to an inside programmer so as to save on cash memory and prevent other apps from using most of your ram while running in the background, so I'm told. Does that make sense to any of you?

I'm very happy to hear that, actually. It sounds like they may finally be addressing a fundamental flaw in the BB10 memory model that I've heard several people bring to their attention, including at the very first BB10 jam years ago now.

I look forward to seeing how they fix it. I'm glad to hear they are at least addressing it.

This is something the Palm team had to work out. The Android team had to figure it out. The WinCE and WP teams. The iPhone team had to figure it out.

Not seeing this issue on mine with Z30STA100-3/10.3.1.2072 installed destructively a couple days after leaking, and a full restore. Apps that should change, such as pictures and BBM do, those that shouldn't such as browser and settings don't.

It's a leak, and even if it wasn't results will vary. Possibly reloading the OS would resolve it, or there's a setting I haven't found, or an app is creating a conflict. Either way it's a leak. Don't like it, try something else. Certainly not BlackBerry's fault you don't like it.

I find it also varies with apps, having side loaded Google play store I found it slowed the device by a good 25%, but I'm not complaining multitasking background running apps causes faster battery drain,besides wouldn't you rather save cash and ram on things that are truly important like a word document email. Freezing a screenshot of the last thing you did before exiting is a reminder of where you left off. Now could be annoying for things like social media Twitter Facebook where live feed is important to you, so then stick with an Android device for the updating tabs. Just sayin...

Originally Posted by DaedalusIcarusHelios

If the active frame is frozen when minimizing, it makes no sense to me that there would be any additional penalty vs using a previously cached image versus and taking a new one, since the the minimized app already has the updated frozen screenshot before it then decides to swap it out with an older one. It would seem the switching of the images would be a penalty. Even if there is a performance benefit to this behavior (which I doubt), I think user experience is more important. I doubt Android or iOS do this, and BB is supposed to be the better multitasker...

Unfortunately I have encountered both behaviors. I just checked and at the moment I cannot duplicate it, but I have seen it before. I think the issue comes up more when running both BlackBerry and Android apps. That's usually when I see it the worst.

I'm going to resurrect this as Im getting the problem now on my passport after the official 10.2.1.2243 OTA. It doesn't start after a fresh reboot but it seems that it begins when you have a few applications running and once it has started it continues until you reboot. Seriously annoyed at this, I didn't want to have to wipe after the update but it seems you have twisted my arm bb.

What would you guys recommend, autoloader or reset through bb link? cpfnuke seems a bit overkill but I know some of you guys swear by it.

EDIT: looks like the problem is there on a fresh 10.3.1.2408 install so I actually think this is a change to the OS rather than a bug. doesn't happen all the time again so I believe its a memory management related change. Damn blackberry REVERT, REVERT, everything was working fine before. I've had not a single annoyance or instability but these 10.3.1 updates have messed these things up a wee bit. Hmmmm....

I have 10.3.1.2267 on my Z10 STL100-4 and just tried 9Gag, which doesn't define active frames, and the active frame bug exists there, where if I open it, I see an image, minimize it, and that is the active frame. I then reopen that app, scroll down to something else, minimize, and it'll show what I was looking at for a second, flash, and show the original active frame image.

Apps that are properly coded for an active frame (like Chive On), work as expected.