Author Topic: Android  (Read 68835 times)

DanDare

Re: Android
« Reply #105 on: November 01, 2015, 06:00:16 pm »
I am running mine now, with no dvbt plugged in, lets see if I see the same issue.
How long does it take before you cannot connect to 192.168.1.1 ?

about 20-30 mins IIRC.

I've just added the baro board so will be doing some more tests this evening and over night.

Admin

Re: Android
« Reply #106 on: November 01, 2015, 06:05:07 pm »
I found the error message you referred to, this us produced when it cannot open the file you requested, eg index.html

I have a suspicion the system is running out of file descriptors, but cannot see hiw at the moment.

Are you running a web-client permanently looking at 192.168.1.1 ?
Or do you interrogate only when it seems to have gone bad ?

Thx
Lee

DanDare

Re: Android
« Reply #107 on: November 01, 2015, 06:21:41 pm »
Quote
I found the error message you referred to, this us produced when it cannot open the file you requested, eg index.html
awesome :)

I have left the web client (chrome) open on the tablet but I am not sure if chrome is active and loading or not when skydemon is running, the multi-tasking on droid might be putting it into hibernation.

once the connection times out I have a look at the web server page. although last time I did check the web server page to notice the connection has gone wonky as skydemon was still quite happy.

Skydemon does seem to take quite a while to time out and report and error when it loses the GPS connection to PAW.

DanDare

Re: Android
« Reply #108 on: November 01, 2015, 06:33:17 pm »
I have a suspicion the system is running out of file descriptors, but cannot see hiw at the moment.

do you suspect a file descriptor leak?

I'm trying to SSH into the PAW box so I can have a look to see how many descriptors are in use with user: pi pw: raspberry but I can't connect. Have the credentials been changed with the PAW o/s?

DanDare

Re: Android
« Reply #109 on: November 01, 2015, 07:02:28 pm »
latest test using the tablet timed out at approx: 60 mins

first thing I noticed was an error in the web browser "Error prohibited CGI execution"

upon reload the message is:

ERR_CONNECTION_REFUSED


DanDare

Re: Android
« Reply #110 on: November 01, 2015, 08:30:39 pm »
tested using the laptop:
got the exact same results as with the tablet, connection to GPS and web server dies after about 1 hour but WiFi connection remains.

so it looks to be related to the PAW box or one of the connected devices.
 

Admin

Re: Android
« Reply #111 on: November 02, 2015, 09:15:30 am »
I have reproduced this error, now to isolate.
it must be one of two things

1. Not having DVB-T connected
2. Constantly running Web Interface

Can I just confirm in your case, you have a web client permanently connected to the PAW index page (which auto refreshes)

DanDare

Re: Android
« Reply #112 on: November 02, 2015, 09:43:36 am »
yes I can confirm I have been running the web interface alongside SkyDemon to keep an eye on things.

As I'm still waiting for the DVB-T dongle I'll try another test today without the web interface connected and report back.

Gyronaut

  • Guest
Re: Android
« Reply #113 on: November 02, 2015, 09:54:12 am »
Hi,
I’m experiencing connectivity issues with my Google Nexus 7 (Android 5.1.1) and SkyDemon (version 3.4.2.20312). I'm not able to get as far as connecting SkyDemon to the PAW. I believe my problem stems from the PAW not recognising the auto generated licence as logging continually states “License Fail for wlan 001D430100F4”.

The Wi-Fi dongle is blinking away quite merrily and is the type recommended in the known good hardware list, so I presume that this is not the cause of the problem?

Has anyone had this type of difficulty before and if so, do they know of a neat way to cure it?



Admin

Re: Android
« Reply #114 on: November 02, 2015, 10:05:30 am »
Hi,
I’m experiencing connectivity issues with my Google Nexus 7 (Android 5.1.1) and SkyDemon (version 3.4.2.20312). I'm not able to get as far as connecting SkyDemon to the PAW. I believe my problem stems from the PAW not recognising the auto generated licence as logging continually states “License Fail for wlan 001D430100F4”.

The Wi-Fi dongle is blinking away quite merrily and is the type recommended in the known good hardware list, so I presume that this is not the cause of the problem?

Has anyone had this type of difficulty before and if so, do they know of a neat way to cure it?

Hi Paul

I have seen 2 license request from your email address
001E8C70F761
3085a95c604f

None of these match the WLAN reported above for 001D430100F4
Thx
Lee

Admin

Re: Android
« Reply #115 on: November 02, 2015, 11:20:59 am »
yes I can confirm I have been running the web interface alongside SkyDemon to keep an eye on things.

As I'm still waiting for the DVB-T dongle I'll try another test today without the web interface connected and report back.

Good Catch!
The problem is related to not having a DVB-T dongle inserted.
it tries to open a connection which fails, but leaves a file descriptor without closing, so over a period of time the process runs out of file descriptors.
Now fixed internally, and you will not see this issue if you insert a DVB-T, which I think you mentioned is on its way

Ian Melville

Re: Android
« Reply #116 on: November 02, 2015, 12:34:26 pm »
Will you be changing the code to allow it to run without a DVB-T dongle?

Admin

Re: Android
« Reply #117 on: November 02, 2015, 12:51:48 pm »
Will you be changing the code to allow it to run without a DVB-T dongle?
It runs now, well for an hour. This is simply a bug and will be fixed in the next release.
Not really sure of the value of a PAW without a DVB-T  ::)

Gyronaut

  • Guest
Re: Android
« Reply #118 on: November 02, 2015, 01:17:17 pm »
Hi Paul

I have seen 2 license request from your email address
001E8C70F761
3085a95c604f

None of these match the WLAN reported above for 001D430100F4
Thx
Lee
[/quote]

Hi Lee,

The first MAC address was for my PC (001E8C70F761) which is no longer required.
The second MAC address is for my Nexus 7 (3085a95c604f) which I'm trying to use.

If neither of these licence requests work with the current WLAN which is reporting 001D430100F4, what do you suggest I do to try and cure this problem?

Rgds,

Paul.

Admin

Re: Android
« Reply #119 on: November 02, 2015, 01:38:02 pm »
The first MAC address was for my PC (001E8C70F761) which is no longer required.
The second MAC address is for my Nexus 7 (3085a95c604f) which I'm trying to use.

If neither of these licence requests work with the current WLAN which is reporting 001D430100F4, what do you suggest I do to try and cure this problem?

Hi Paul,
The license request is based upon the MAC address reported by PilotAware. So I am guessing the hotspot you are seeing is :-
Code: [Select]
PilotAware-001D430100F4So you need to request a license for
Code: [Select]
001D430100F4
« Last Edit: November 02, 2015, 01:40:22 pm by Admin »