Marcos,

my last test build can be downloaded and installed from here:

http://dexters-web.de/f/tw/oVMS-release.apk

...but I haven't found the solution to the version compatibility issue yet, according to another tester it will only show OCM markers correctly on Android 5.x.

Regards,
Michael


Am 24.01.2015 um 13:34 schrieb Marcos Mezo:
Would you consider adding the aplications to an alternative market? I was thinking of f-droid since it is specially for open-source software.
I have a mostly google free phone without any account and would greatly apreciate it.

Thank you,
Marcos

Michael,

I've added you to the maintainers list for the Android repository.

Regards, Mark.

On 17 Jan, 2015, at 10:38 pm, Michael Balzer <dexter@expeedo.de> wrote:

Hi again,

the directory structure changes are not that complex, it's just another root directory and the sources subdirectory is named "java" instead of "src".

So here are my changes so far:
https://github.com/dexterbg/Open-Vehicle-Android/commit/56445e31a3de48dfde97956ce70b1153f6729922

 Version 3.2.3:
- OCM API update: fixes missing stations, missing detail data
  and station address encoding issues
- USSD code dialog is now text field allowing "*" and "#",
  default "*100#" (account balance query in most networks)
- 12V battery state display (car info)
- Renault Twizy: "Homelink" gets "Profile" and extended by "Default"

Mark, you need to pull this or add me, I cannot push into the project repository.

Haven't begun on the range switch, I'm stuck building for my Android 2.3.5 phone -- everything works except the OCM markers, and the log contains lots of resolver errors (see below). Tried different build settings and also replacing the google-play-services.jar, but nothing helps so far.

It must be some build config, as it runs perfectly on my 5.0.2 tablet. If anyone's got an idea on this, let me know.

Regards,
Michael

Resolver errors on Android 2.3.5:

01-17 13:31:56.788    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to find class referenced in signature (Landroid/app/Fragment;)
01-17 13:31:56.788    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 90: Landroid/app/Activity;.getFragmentManager ()Landroid/app/FragmentManager;
01-17 13:31:56.948    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 6780: Lcom/actionbarsherlock/internal/nineoldandroids/widget/NineFrameLayout;.onHoverEvent (Landroid/view/MotionEvent;)Z
01-17 13:31:56.958    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5406: Landroid/widget/FrameLayout;.getAlpha ()F
01-17 13:31:56.958    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5408: Landroid/widget/FrameLayout;.getTranslationY ()F
01-17 13:31:56.958    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5412: Landroid/widget/FrameLayout;.setAlpha (F)V
01-17 13:31:56.958    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5420: Landroid/widget/FrameLayout;.setTranslationY (F)V
01-17 13:31:56.968    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5100: Landroid/view/ViewGroup;.getAlpha ()F
01-17 13:31:56.968    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5111: Landroid/view/ViewGroup;.getTranslationX ()F
01-17 13:31:56.978    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5112: Landroid/view/ViewGroup;.getTranslationY ()F
01-17 13:31:56.978    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5134: Landroid/view/ViewGroup;.setAlpha (F)V
01-17 13:31:56.978    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5139: Landroid/view/ViewGroup;.setTranslationX (F)V
01-17 13:31:56.978    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5140: Landroid/view/ViewGroup;.setTranslationY (F)V
01-17 13:31:57.008    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 7644: Lcom/actionbarsherlock/internal/widget/ActionBarView$HomeView;.onHoverEvent (Landroid/view/MotionEvent;)Z
01-17 13:31:57.008    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5410: Landroid/widget/FrameLayout;.onPopulateAccessibilityEvent (Landroid/view/accessibility/AccessibilityEvent;)V
01-17 13:31:57.049    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 4995: Landroid/view/View;.jumpDrawablesToCurrentState ()V
01-17 13:31:57.049    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5003: Landroid/view/View;.onInitializeAccessibilityEvent (Landroid/view/accessibility/AccessibilityEvent;)V
01-17 13:31:57.049    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve static method 5027: Landroid/view/View;.resolveSizeAndState (III)I
01-17 13:31:57.079    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve static method 7853: Lcom/actionbarsherlock/internal/widget/IcsAbsSpinner;.resolveSizeAndState (III)I
01-17 13:31:57.089    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5117: Landroid/view/ViewGroup;.onInitializeAccessibilityEvent (Landroid/view/accessibility/AccessibilityEvent;)V
01-17 13:31:57.089    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to find class referenced in signature (Landroid/view/accessibility/AccessibilityNodeInfo;)
01-17 13:31:57.089    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5118: Landroid/view/ViewGroup;.onInitializeAccessibilityNodeInfo (Landroid/view/accessibility/AccessibilityNodeInfo;)V
01-17 13:31:57.089    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5122: Landroid/view/ViewGroup;.onRequestSendAccessibilityEvent (Landroid/view/View;Landroid/view/accessibility/AccessibilityEvent;)Z
01-17 13:31:57.099    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve direct method 5551: Landroid/widget/PopupWindow;.<init> (Landroid/content/Context;Landroid/util/AttributeSet;II)V
01-17 13:31:57.109    7099-7099/com.openvehicles.OVMS E/ResourceType﹕ Style contains key with bad entry: 0x01000000
01-17 13:31:57.109    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5473: Landroid/widget/LinearLayout;.getAlpha ()F
01-17 13:31:57.109    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5476: Landroid/widget/LinearLayout;.getTranslationX ()F
01-17 13:31:57.109    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5488: Landroid/widget/LinearLayout;.setAlpha (F)V
01-17 13:31:57.109    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 5498: Landroid/widget/LinearLayout;.setTranslationX (F)V
01-17 13:31:57.249    7099-7100/com.openvehicles.OVMS E/Database﹕ close() was never explicitly called on database '/data/data/com.openvehicles.OVMS/databases/sampledatabase'
    android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here
            at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1960)
            at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:906)
            at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:940)
            at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:933)
            at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:614)
            at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
            at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:118)
            at com.openvehicles.OVMS.ui.utils.Database.get_ConnectionTypes_Main(Database.java:222)
            at com.openvehicles.OVMS.utils.ConnectionList.<init>(ConnectionList.java:46)
            at com.openvehicles.OVMS.ui.MainActivity.onCreate(MainActivity.java:59)
            at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1072)
            at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1836)
            at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1893)
            at android.app.ActivityThread.access$1500(ActivityThread.java:135)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1054)
            at android.os.Handler.dispatchMessage(Handler.java:99)
            at android.os.Looper.loop(Looper.java:150)
            at android.app.ActivityThread.main(ActivityThread.java:4385)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:507)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:849)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:607)
            at dalvik.system.NativeStart.main(Native Method)
01-17 13:31:57.879    7099-7099/com.openvehicles.OVMS W/dalvikvm﹕ VFY: unable to resolve virtual method 4995: Landroid/view/View;.jumpDrawablesToCurrentState ()V





Am 15.01.2015 um 00:38 schrieb Michael Balzer:
Mark,

I managed to import the App code into Android Studio and build the App, currently running successfully on Android 5.0.2 on my tablet -- not yet tested on my 2.3 phone.

I have fixed the OCM integration and the USSD code entry, also added a homelink reset menu option and extended the "D" message parsing to include 12V reference and charging info, which is then displayed on the car info sheet.

I'll fix the OCM range switch tomorrow (if I find the time).

I'd like to push my changes back into github, but it seems the change to Android Studio / Gradle modified a lot of files, even directory layout. It seems I'll have to create a new repository, breaking the version history. I'll see if I can do something about that and work in my own github account first.

Regards,
Michael


Am 13.01.2015 um 07:03 schrieb Mark Webb-Johnson:
This seems to be a one-liner in res/layout/dlg_pin.xml:

        <EditText android:id="@+id/etxt_input_value"
                android:layout_width="match_parent"
                android:layout_height="wrap_content"
                android:digits="0123456789"
                android:password="true"
                android:inputType="numberSigned" />

It seems that the re-use of the showPinDialog in so many places in the Android code is a bit restrictive.

We could try changing this to andoid:inputType textPassword.

Regards, Mark.

On 12 Jan, 2015, at 1:57 am, Michael Balzer <dexter@expeedo.de> wrote:

Hi Pierre,

that's a known bug of the App. You currently need to use the perl client to send USSD codes.

Command code for this is 41, so for your USSD code it's...

./cmd.pl 41 "*131#"

Regards,
Michael


Am 11.01.2015 um 17:33 schrieb Pierre Uhl:
 
Hi everybody,
 
I am trying to use USSD Codes. But the App (Android 3.2.2) does not accept * and # but only numbers. How can I input *131# to recharge the Prepaid SIM-Card?
 
Pierre Uhl


-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev



_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev


-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26



_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev


-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev



_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev




_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev


-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26