[yohannyphm]

Why

Posted via CB10

It's like unplugging your computer while performing a task or loading, can damage software and cause it to go on an endless rebooting cycle or cause OS trouble. It's being warned all around the forums. By using the volume rockers you do a save reboot and a system check that fixes OS pitfalls.

Posted from the best mobile device Z10 10.2.0.1767 from Singapore!! Thanks to Sashesi

[drinka4yearz]

OK thanks didn't know that.

Posted via CB10

[hamode 192]

Will this work on the official update??


Posted via CB10

[shabbs]

Will this work on the official update??

It certainly should. I'll be re-sideloading my runtime after the update.

[GTiLeo]

is this the most resent unlocked runtime or is there really only one version of it? i havent followed the unlocked runtime so i'm lost with it as i have no need for android apps right now until i setup my new aquarium controller and need to control it from my phone

[shabbs]

is this the most resent unlocked runtime or is there really only one version of it? i havent followed the unlocked runtime so i'm lost with it as i have no need for android apps right now until i setup my new aquarium controller and need to control it from my phone

The most recent unlocked runtime is from 10.2.1.641. Search the forums and you shall find it...

[GTiLeo]

The most recent unlocked runtime is from 10.2.1.641. Search the forums and you shall find it...

thanks sir and that works on the official release correct

[bradfordjohnson]

The most recent unlocked runtime is from 10.2.1.641. Search the forums and you shall find it...

Any way we can just get a quick link to the BARs? And do they work with 1791?

[hamode 192]

It certainly should. I'll be re-sideloading my runtime after the update.

Thanks :-*

Posted via CB10

[nemasus]

I have sideloaded the unlocked Android runtime over the one that came with OS 10.2.0.1791, all good except now I am back being stuck with the navigiation bar at the bottom of the screen whereas I was able to hide it on the stock Android runtime by swiping from the top and select hide.

Is there a way of getting the hide bar option back or I have to revert back to the stock Android runtime?

If that's the only way to get it back, how can I revert to the stock Android please or is there an unlocked version of it I could sideload?

Thanks Crackberry peeps.

[tayl0rd]

There's another unlocked runtime that came with 10.2.1.545. It allows you to hide the bar. Seek that one out.

Posted via CB10

[shabbs]

There's another unlocked runtime that came with 10.2.1.545. It allows you to hide the bar. Seek that one out.

Seek out the 10.2.1.641 one.

[nemasus]

Thank you both, seeking....

[tayl0rd]

Seek out the 10.2.1.641 one.

What he said.

Posted via CB10

[nemasus]

Seek out the 10.2.1.641 one.

Found the runtime, thanks, I can hide the bar now but have another problem, apps that require signing on can not connect to network, Flipboard & Seeking Alfa for example return error "Network not Available" when I try to login while, to my surprise, Skype and WhatsApp worked OK.

There obviously are differences in how these apps connect to the Internet, I think Skype bypasses Android and connects directly to the BlackBerry native network drivers while Flipboard is totally contained within the Android runtime.

Oh well, back to the hunt for another unlocked Android runtime, I think I need to find and pull one of a leaked OS 10.2.0.x

I <3 BBM

[zoozzooz123]

The locked runtime is working good for me

Z10STL100-1/10.2.0.1791, buying Z30 this year

[midknightz]

Found the runtime, thanks, I can hide the bar now but have another problem, apps that require signing on can not connect to network, Flipboard & Seeking Alfa for example return error "Network not Available" when I try to login while, to my surprise, Skype and WhatsApp worked OK.

There obviously are differences in how these apps connect to the Internet, I think Skype bypasses Android and connects directly to the BlackBerry native network drivers while Flipboard is totally contained within the Android runtime.

Oh well, back to the hunt for another unlocked Android runtime, I think I need to find and pull one of a leaked OS 10.2.0.x

I <3 BBM

does this happen for you with wifi on and off? im going back to this runtime as the newer ones from 10.2.1 dont play nice when im in wifi coverage. apps dont connect similar to what you are describing. when i disable wifi and go to 3g or 4g they connect fine though.

[nemasus]

does this happen for you with wifi on and off? im going back to this runtime as the newer ones from 10.2.1 dont play nice when im in wifi coverage. apps dont connect similar to what you are describing. when i disable wifi and go to 3g or 4g they connect fine though.

Thanks, that was spot on, some of the Android apps are not able to connect over WiFi with the unlocked runtime pulled out of 10.2.1.641, but work as expected over a 3G data connection.

I possibly need to have the latest unlocked Android runtime from OS 10.2.0.x,

This thread is like a maze, any one know where I can easily locate the above version?

[nemasus]

Update to above post...

I found the connectivity issue with latest Android runtime comes up only when you try to go through the initial sign-on when running an app for the first time while on WiFi.

A simple workaround I found is to run the app first time and login while connected over 3G then exit it to save the settings. From then on apps such as Flipboard & Bloom.FM that require network access will work over WiFi too.

I am on Z10STL100-2/10.2.0.1791

I <3 BBM

[Icarus3000]

Do they just "work" or are they truly connecting over wifi?

Posted via CB10

[sanjk1]

BerryLeaks help please!! So many problems. So I upgraded ota official 10.2.0.1791 and obviously my previous sideloads stopped working. So I opted for the unlocked runtime bar. Have tried several times and several different runtimes but still the same thing happens. Blue bar loads and app shuts down. Ports from bb world also!! I did a device reload a day ago so I could start fresh. Today I tried again using what everyone says is the most stable unlocked runtime for that os. Sideloaded both files via chrome. Rebooted with rocker keys until blue loading thing came up. Opened up a port and sideload to hopefully give it a boost but not only did the sideload close down, the port from bb world close down also. This truly sucks balls. Cant do the debug method as Java only provides an RE for 64bit. I have 32bit lol. Unless you know how I can work around that. Please help. Thanks

[leejayh]

A suggestion, after rebooting, leave the phone alone for 10 minutes before launching an android app.

It actually takes a few more minutes for the bb10 to load up the runtime.

After the 5-10 minutes, it will take 5 minutes to load the first Android app

Do this all once

In the future, the apps will load very quickly. You still need to wait the 5 min after a reboot, but after that everything load quickly.


Posted via CB10

[Labba Labbala]

Please PO or moderator,
update the first post of this thread with needed info that people are asking in this thread over and over again...

Will work with 10.0.x : No
Will work with 10.1 : No
Will work with 10.1 MR : No
Will work with official update 10.2.0.x : Yes
Will work with 10.2.1.x : Yes
Have permanent bar below: Yes
permanent bar can be configure to be visible or not: No
Android Runtime versions :
- sys.android.shell-10.2.1.9.bar
- sys.android-10.2.1.9.bar

* After installing reboot device
* After rebooting, leave the phone alone for 10 minutes before launching an android app

I think i covered all the basics ... feel free to add what ever you want.

[bounce007]

If I want to revert to the android runtime on 10.2.0.1791 do I just sideload the android bar file that comes with it, or do I have to reload the entire OS?

[nappp]

If I want to revert to the android runtime on 10.2.0.1791 do I just sideload the android bar file that comes with it, or do I have to reload the entire OS?

just sideload the runtime you want and restart your phone before you install any new bar files

Sent from an ATM
No trees were harmed during the making of this message