FJ Software

Hi,

Recently Android V1.0.17 was released and I updated it through the market.

What I have noticed is that sometimes, the clent does not automatically starts when it detect connection to a WiFi access point or connection to a paied bluetooth device.

I am running Gingerbread V2.3.6 on a Samsung Galaxy S2.

Has anyone seen this issue?


Regards

John

There were no changes in autostart functionality (also no technical changes). Please try it the next days with 1.0.17 and then go back to 1.0.16 and try again some days to identify clearly if the problem has to do with the update. You can get 1.0.16 here: www.fjsoft.at/files/mpeclient_1.0.16.apk

FJ,

I upgraded my Galaxy S2 to ICS (Android V4.0.3) and the client (V1.0.17) seems to start correctly most of the time when it detects he selected WiFi APs.

However, MPE was not able to connect and producing an error stating it could not find the the Phone IP Address. This was also happening when the phone had Gingerbread (V2.3.6). This only started happening in the last week or so and as late as this morning, I could not connect using WiFi.

An upgrade to the MPE client appeared in the Android market this afternoon -- V1.0.18 - and I installed it. Now WiFi connectivity works. This may be a coincidence.

I will keep an eye on it and if I can reproduce the issue, I will let you know.


Regards

FJ,

I can confirm that the android client starts every time.

However, I have a discovered another issue with WiFi and Bluetooth connectivity.

Every so often, the PC application will fail to connect to the android client. When trying to use WiFi, it says it cannot find the phone's IP address, yet the andoid client reports it is connected to WiFi. You can ping the phone.

The way to fix if is to shutdown the andoid client and restart it.

Similar issue with Bluetooth. The desktop application reports it cannot find the phone.

What is interesting is you may be connected to the phone and for example perform a sync, then after a while, if you try to sync againn, you get the above mentioned errors. Its as if the android client goes to sleep and doesn't wake up.

I can send you a copy of the debug file if that helps.


Regards

JP

Does the client-setting "Avoid standby" help ?