I've done that on every Android device I owned as well as shutting all the transitions and other BS off, stands to reason it would work somewhat on the Android runtime as well, though doubt it works 'as much'.

Force GPU Rendering:
The early life of Android suffers from buggy implementation of GPU driver and API calls, which means that at the time using GPU is like using Blood Magic to increase your performance with a pretty big chance of dying instantly.

Modern Android apps are expected to make good use of GPU calls for drawing but sometimes developers simply don't, which means pretty much all drawing is done via CPU, which is not the processor you want to do complex drawing in. Enabling this option will activate the aforementioned Blood Magic in all apps, which as Android implementation get better has reduced chance of dying.

Depending on BlackBerry's implementation, enabling this option can be the difference between using GPU and not at all on certain apps

Don't keep Activities:
This one is something I generally don't want to mess with, but yblmv. The "activity" being mentioned there is the Android term that amounts to a page in an app. Most simple applications will make use of multiple pages to display stuff, and as memory gets low pages that you're not in will be discarded and if that happens when you are going back to that page the app will have to restart it.

Depending on what each page needs to do, restarting the page may cause unfavorable outcome. Ideally each page should be able to reconstruct itself everytime it dies, because the danger of getting flushed is totally real; the pro is of course aggressive RAM clearing, the con would be potentially wasted CPU cycles restarting pages all the time

Activating these two may very well improve performance; generally there's a reason they're called "Dev Tools" and that they're not enabled by default, but the allure of Android is customization, so yeah.

The Overlay being referred to is the process of laying out the UI, which as you may have noticed is composed of multiple layers of stuff overlapping each other. The process of doing this is generally done by a dedicated hardware to do that, hence the HardWare Overlay; disabling this Hardware Overlay will offload the work to either CPU or GPU instead, which is less efficient at doing that. If BlackBerry instead simply simulates an overlay hardware, offloading the work to CPU or GPU may indeed be faster

I have done a cursory check on my android apps (11 of them in total) and I am NOT noticing any great differences in time to open. I have timed them with and without the settings enabled and have no improvement in that regard. My one MAJOR app is Show Box and it is actually shutting down when I switch from "updates" to "my library" . I have noticed (preliminary!) some improvement in speed WITHIN 3 or 4 of my other android apps though.

Definitely notice a performance increase. Is it night and day? No. More like going from a cloudy day with a chance of rain to clear skies but still a little muggy. (if that makes sense to you guys). The performance is in animation and responsiveness. Not load time.

Turned off animations and turned on force gpu render and wow it runs much better now had 2 android apps going and they ran so smooth and slick I was like wow this is smoother than most android phones haha

Did as suggested and immediately noticed a huge difference in playing PBA (bowling). The app used to crash when first opening and when finally opened there was bad lag in getting the game going. That seems to have now been solved.

Try not to combine these tweaks and enable both "Show Touches" and "Pointer Overlay" at the same time. My Android runtime crashed multiple times, the setting having persisted, and I had to do various tricks to get to the developer option and turn them off.

Specifically, it looks like that "Don't keep activities" and "pointer overlay" don't play nice together, somehow, for some reason, I don't know why. At any rate, don't.

The symptom is that I can't scroll in my Android apps, it'll crash the Android runtime, crashing all other Android apps, even subsequent attempts at starting one. I can touch and drag around for a bit but then suddenly it crashes. I can touch and hold and tap on stuff to get to the Developer Option itself, but scrolling down to the options themselves is hard

I had to flick hard and quickly to get the developer option screen to scroll all the way down to Don't keep activities, which I disable, then I try a series of flicks until I managed to get to the Pointer Overlay option, which I disable and my runtime is stable again.

Edit: I also disabled all animations, specifically the window animation, transition animation, and animator duration scales are all set to off. I don't know if it has anything to do with the problem, but after I disable don't keep activities the runtime gets more stable
Z10 STL100-1/10.2.1.3247