testing run time now, Vine failed just normal install, doing debug convert method now
Printable View
testing run time now, Vine failed just normal install, doing debug convert method now
So it is running 4.2.2 then?
Posted via CB10
Yes it is.
Posted via CB10
Hey Kris will this be a full meal deal or a hybrid.
Posted from my Q10 on the addicting CB
Kris. _sys_android_rrr isn't available OTB in any of the android runtimes at the moment
All apps that require native will still require the debug workaround
That's what xsacha and I found at the very least
Snapchat - Works, but camera and sensors are way out of wack
Draw Something 2 - Works, some minor glitches guessing a word
Candy Crush - Same as before, Works
Simpsons - Boot screen than crashes
FlipBoard - Works with some UI glitches
Instagram - Works good, camera is messed up like snapchat
Vine - Allows log in, Crashes after
Well I may be using bad apk's than
Hmmm interesting, thanks for the update. I wonder why the camera for snapchat and instagram isn't working right?
Posted via CB10
No. What I'm trying to say is Vine obviously won't work without debug
However, it worked in the 341 android runtime with the permission enabled. It may be a different Vine version (I know FF android has this problem), but I obviously don't have the OS to test it ROFL
I'll give it a go once the OS is leaked, and let everyone know :)
Maybe the android player has been updated since the 341 dev, and it introduced some problems
Kris, instead of using what xsacha has in his test.mf
edit it so it includes
Entry-Point-User-Actions: access_internet,read_geolocation,access_shared,use _camera,play_audio,post_notification
Entry-Point-System-Actions: _sys_use_consumer_push,_sys_android_rrr
The first line may give it the correct permissions for the camera if it isn't doing so currently
Will try thanks
now it won't spit out a bar file :confused:
Read all thread in about 30 min amazing job
Posted via CB10
Thansk for the update, any info if the OS can be installed on SQN002 / 003 pls?
_sys_android_autostart_service??
:o
is it still called test.mf? That name can't change
Alternatively, you can use the command
apk2bar "????\UserInputPath%.apk" "???\sdk" -t "output folder" -a "CompanyName" -d "????\debug.bar" -os 10.0.9 -ma "???\test.MF"
You don't want that in your script
If that is there, then all your android apps will start on boot X_X!!!!!!!!!!!!!!!!!!!!!!!!!!!
The last posts are getting above my head lol
Posted via CB10
that is only if an Android app is opened to initiate the runtime... Or does the runtime start by itself on boot... I dont know how the change will come after support for headless.... will headless apps API support android apps...??
Headless android apps are already supported. What happens when you enable that permission is whenever you restart you device, once the android runtime begins (I believe it's actually initiated by apps with that permission), the app will autostart
These permissions are what allow the debug method to work
oh... ok.... yet to get hands on with 10.2.... So just to be clear, the Android runtime doesn't start unless an Android app is opened... That means a headless Android app will not provide headless functionality unless any Android is opened to initiate the runtime??
Question regarding Instagram:
Does it still suffers from these issues? (unable to see the "hidden" buttons as the editing area is too big)
http://forums.crackberry.com/attachm...-instagram.png
Dark theme on setting page?good
Posted via CB10
yup still called test.mf