Blackberry 10 report

Issue #75 wontfix
Evanova Android repo owner created an issue

From user and helper T.

I've tested the latest Evanova 1.2.4 (from the Google Play beta program) on a simulator (version 10.2.0.1521) at 720x720 and 720x1280, and my phone (version 10.2.0.1725) at 768x1280.

The long and short of what I've found:

768x1280 (and 720x1280) display perfectly. 720x720 still doesn't display properly. api_keys.txt and manual import work. QR code import calls upon an Android app (not sure how to get this working for BB10). Once the data has been updated, just about every screen displays as it should. Setting an image as device wallpaper causes a force close. Setting an image as app wallpaper doesn't. Importing EVEMon .xml files works. Bringing up the keyboard causes the wallpaper to resize (nothing major, really) Ship description pages have HTML tags showing.

720x720 support is the biggest issue, as the other 2 real issues (device wallpaper and QR code) can be bypassed. I uploaded screenshots of the app on my phone and the simulator here: http://imgur.com/a/K8kcK

Comments (3)

  1. Evanova Android reporter

    From super-powered BB tester T.

    Yesterday, the public got its hands on the first major leak of BlackBerry OS 10.2.1. Being a member of the public, I installed the software on my phone and tried to see of Evanova worked. Long story short, it works marvelously.

    Firstly, I installed the app as an apk directly from my phone. No fancy conversions needed. ‎Then, when I opened it, I checked the import functions. The BlackBerry browser now recognizes the URN, so importing from the EVE API website works. QR code mode asks for com.google.zxing.client.android, but I got the apk for that and installed. Now, QR code mode seamlessly shifts into the scanner. Text file and manual entry still work. The force close upon wallpaper selection is gone, screenshot attached.

    ‎While there is no simulator to test 720x720, everything else looks great.

    Keep on coding in the free world,

  2. Evanova Android reporter

    And more guidance from T.

    They've also updated their tools, so the command line converter and Eclipse plug-in have replaced the Web converter.‎ The warning file upon converting with the command line converter (which has a GUI now, too) says that the app contains a widget, but according to BlackBerry's developer guidelines, as long as the widget is secondary to the function of the app, it's supported. It also says that the minimum API level should be either 10 (OS 10.1 and prior) or 17 (10.2 and following) , so not 18. That was all that the warning file said, which is good.

    ‎The BlackBerry World Vendor Portal is slower on the verification process than Google Play, from what I've heard, but the prospects are good. All that the apk needs is to be converted to a signed bar file with the tools (after the computer has been configured for signing, which is pretty simple). Once the signed bar is made, then it can be uploaded to BlackBerry World, verified and released. A minimum OS of 10.2.1 and support only for the two full touch devices (Z10 and Z30) should avoid the bugs with 10.2.0 and 720x720 that popped up before.

    Here are some relevant links.

    Porting guidelines: http://developer.blackberry.com/android/documentation/port_android_app_to_bb_device.html

    BlackBerry Tools for Android 2.0 Beta (can convert and sign in one step with GUI if signing set up): http://developer.blackberry.com/android/documentation/blackberry_android_development_tools_2.0_beta.html

    Signing configuration (do this first): ‎http://developer.blackberry.com/android/documentation/configure_app_signing_2007101_11.html

    Getting Started with BlackBerry World: ‎http://developer.blackberry.com/devzone/blackberryworld/getting_started_preparing_your_app_for_blackberry_world.html

  3. Log in to comment