Hi again, I'm not able to enable GPRS in OVMS. I've tried some SIM cards with different operators and I think I've used properly APN settings (the same used in the phone) but it still having the 0x0041 error. In Italy (where I live) we have LTE, 3,5G 3G, 2.5G and 2G (not for every operator) but if I use the sim in a Phone and force 2G connections both SIM i've tried work (Vodafone and Telecom Italia). As lat information GSM works fine and I can communicate with OVMS by SMS. Any hint? Gianluca Il giorno 28/giu/2014, alle ore 06:00, ovmsdev-request@lists.teslaclub.hk ha scritto:
Send OvmsDev mailing list submissions to ovmsdev@lists.teslaclub.hk
To subscribe or unsubscribe via the World Wide Web, visit http://lists.teslaclub.hk/mailman/listinfo/ovmsdev or, via email, send a message with subject or body 'help' to ovmsdev-request@lists.teslaclub.hk
You can reach the person managing the list at ovmsdev-owner@lists.teslaclub.hk
When replying, please edit your Subject line so it is more specific than "Re: Contents of OvmsDev digest..."
Today's Topics:
1. Re: changing android app server IP (Christopher Cook) 2. Re: changing android app server IP (Lee Howard) 3. Re: changing android app server IP (Lee Howard)
----------------------------------------------------------------------
Message: 1 Date: Fri, 27 Jun 2014 12:44:52 +0800 From: Christopher Cook <christopher.cook@webprofusion.com> Subject: Re: [Ovmsdev] changing android app server IP To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Message-ID: <r7evp31xp6nup2wd3sya83eu.1403844292014@email.android.com> Content-Type: text/plain; charset=utf-8
Off topic but long term it would be prudent to investigate the cross platform options for the app, otherwise there's a lot of duplicate work.
I'd consider HTML/Cordova, Xamarin (and perhaps Xamarin Forms), Titanium Sdk, etc.
Not saying cross platform doesn't have its challenges but otherwise there's probably not enough dev resources to expect to develop a complete app for all platforms.
Chris
Tom Saxton <tom@idleloop.com> wrote:
On iOS, the App settings is buried in the System Settings app, a terrible UI design. Finally, with iOS 8, there will be a way for apps to send you straight to the app settings. But for now...
Open the Setting app, then scroll down to the bottom to find a list of apps that use the built-in settings mechanism. You'll find an item for "Open Vehicle". In there you'll find the configuration for your OVMS account, including the server IP address.
That's also where you can turn the Open Charge Map stuff on/off and where you can override the module's choice for distance and temperature units.
Arguably the server account should be per-vehicle but I'm guessing the thought was that anyone who has multiple OVMS vehicles will have them all on the same server and making that app-wide means you only have to enter username, password and server IP once.
Of course none of this is any help for figuring out how to do it on Android...
Tom
-----Original Message----- From: Lee Howard <lee.howard@mainpine.com> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Thursday, June 26, 2014 at 4:22 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] changing android app server IP
On 06/11/2014 05:23 PM, Mark Webb-Johnson wrote:
I think the 'tmc' server is hard-coded in the Android App.
The code on github is up-to-date, if anyone wants to take a stab at making it configurable.
I spent a few days getting acquainted with Android development and toying with the OVMS Android app code, loading it onto the Android emulator, etc.
I couldn't decide where was the best place was to put an "app settings" menu item, and so I caved and downloaded OVMS from the App Store onto my iPad...
The iOS App has it in the system settings tab.
I don't see it. Is this in unreleased/unpublished code?
There is the "OVMS Server IP" in the "Parameters" section of the "Control" menu for each configured car. However, I believe that refers to the server IP configured in the car module and not for the app. AND this same section and menu exist on the Android app (after waiting long-enough for it to populate... or getting lucky... I can't figure out which since it often doesn't populate at all).
Since for each car the app needs to talk to the same server as the car module it would be ideal for changes made to this "OVMS Server IP" in the "Parameters" section to apply to both the IP where the module communicates *AND* to where the app communicates for that car, but since this "Parameters" section doesn't even come up at all until the app can talk to the server and module, I don't think that's how it works, presently, and it would appear to need a lot of effort to get it working in that fashion.
It would be nice if I could have different car modules talking to different servers and for me to be able to use one app to rule them all. The app would merely talk to different servers for each car.
Anyway... since my initial interest is in doing server-side and car-module-side developments (and not so much the app-side of things) I'm inclined to just make a hard-coded change to the server IP address in my Android app and move on for the sake of being productive.
Thanks,
Lee.
-- *Lee Howard* *Mainpine, Inc. Chief Technology Officer* Tel: +1 866 363 6680 | Fax: +1 360 462 8160 lee.howard@mainpine.com | www.mainpine.com _______________________________________________ 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
------------------------------
Message: 2 Date: Fri, 27 Jun 2014 10:38:05 -0700 From: Lee Howard <lee.howard@mainpine.com> Subject: Re: [Ovmsdev] changing android app server IP To: ovmsdev@lists.teslaclub.hk Message-ID: <53ADABFD.4010407@mainpine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 06/26/2014 08:38 PM, Tom Saxton wrote:
On iOS, the App settings is buried in the System Settings app, a terrible UI design.
Oh, I see. Thank you. That was very helpful.
Yes, it is a terrible UI design by Apple on iOS.
I was going to try to do on Android similar to what had been done on iOS, but since this is so terrible, I'd rather not do it like that.
Arguably the server account should be per-vehicle but I'm guessing the thought was that anyone who has multiple OVMS vehicles will have them all on the same server and making that app-wide means you only have to enter username, password and server IP once.
Of course none of this is any help for figuring out how to do it on Android...
As I dug-into the Android code better to hard-code the address change I discovered - to my delight - that the app server address is stored in a per-car data object. Yay! So this is nice. I'm going to give this another shot.
Thanks,
Lee.
-- *Lee Howard* *Mainpine, Inc. Chief Technology Officer* Tel: +1 866 363 6680 | Fax: +1 360 462 8160 lee.howard@mainpine.com | www.mainpine.com
------------------------------
Message: 3 Date: Fri, 27 Jun 2014 12:44:16 -0700 From: Lee Howard <lee.howard@mainpine.com> Subject: Re: [Ovmsdev] changing android app server IP To: ovmsdev@lists.teslaclub.hk Message-ID: <53ADC990.5010708@mainpine.com> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
On 06/27/2014 10:38 AM, Lee Howard wrote:
On 06/26/2014 08:38 PM, Tom Saxton wrote:
Arguably the server account should be per-vehicle but I'm guessing the thought was that anyone who has multiple OVMS vehicles will have them all on the same server and making that app-wide means you only have to enter username, password and server IP once.
Of course none of this is any help for figuring out how to do it on Android...
As I dug-into the Android code better to hard-code the address change I discovered - to my delight - that the app server address is stored in a per-car data object. Yay! So this is nice. I'm going to give this another shot.
Here is the patch. Someone with privs can apply it and commit these changes to the repository if it meets with their approval.
It's a very small enhancement - basically permitting an interface to sel_server in the CarData object. The interface is right where it should be, IMO: right where you enter the vehicle info and passwords. The default is left to "tmc.openvehicles.com", but the user now has the capability to modify it (on a per-car basis, even).
I did not change the sel_server initialization value of "tmc.openvehicles.com". I could have changed this to "" as with the other CarData strings, but it probably makes little difference. Leaving it to initialize with "tmc.openvehicles.com" possibly it could be confusing to someone later who doesn't recognize that the initialized value is always overwritten by the configured value (as with the other CarData strings which are initialized to ""). If someone cares they can modify that at the top of CarData.java.
This patch also makes one obvious grammatical correction in a string appearing on the same page layout.
If there is any concern just look at the patch - it's a very, very benign set of changes. This e-mail is longer than the patch is.
Thanks,
Lee.
-- *Lee Howard* *Mainpine, Inc. Chief Technology Officer* Tel: +1 866 363 6680 | Fax: +1 360 462 8160 lee.howard@mainpine.com | www.mainpine.com