PilotAware
British Forum => Technical Support => Topic started by: Deker on May 12, 2023, 05:39:23 pm
-
I've been using my trusty Samsung Tab4 SM-T230 running Android 4.4.2 which worked with my PAW faultlessly for several years.
Now I've "upgraded" to a Samsung A7 lite SM-T225 Android 13, I keep getting the "waiting for device message" in Sky Demon, normally after about 20 to 30 mins from start up.
Usually need to turn the tablet wifi off and back on, but once the problem starts, it repeats at random intervals. It's been like this for the past 6-9 months and not changed behaviour even with several recentish PAW firmware updates.
I'm pretty sure its a tablet issue as I've been in P2 seat with P1 running his Apple table, my Samsung flags the message but the Apple functions properly. I've also repeated the test with my phone and tablet connected, tablet flashed the message but phone continues to work fine.
As far as i can tell, bth tablets are configured the same.
Any suggestions?
ATB
Deker
-
Is there an issue if the tablet is connected to a Wifi network with no Internet access? Newer versions of Android can rear up about this.
Does the tablet have a problem with connecting to open networks?
Both things to Google for with your particular model.
You can remove the open networks theory by setting a password for the PAW Wifi, then if it makes no difference, clearing it again.
Do you have Internet access/iGrid?
Tablet firmware/Android fully up to date?
-
I've been using my trusty Samsung Tab4 SM-T230 running Android 4.4.2 which worked with my PAW faultlessly for several years.
Now I've "upgraded" to a Samsung A7 lite SM-T225 Android 13, I keep getting the "waiting for device message" in Sky Demon, normally after about 20 to 30 mins from start up.
Usually need to turn the tablet wifi off and back on, but once the problem starts, it repeats at random intervals. It's been like this for the past 6-9 months and not changed behaviour even with several recentish PAW firmware updates.
I'm pretty sure its a tablet issue as I've been in P2 seat with P1 running his Apple table, my Samsung flags the message but the Apple functions properly. I've also repeated the test with my phone and tablet connected, tablet flashed the message but phone continues to work fine.
As far as i can tell, bth tablets are configured the same.
Any suggestions?
ATB
Deker
Hi Derek,
Definitely sounds like a WiFi connectivity issue to me, but of course not easy to determine exactly what.
Remind me - are we talking Rosetta or PAW Classic?
When you go to 'turn the tablet WiFi off and back on' do you notice whether it has connected to something else in the plane - such as another phone? If so, it might just be a question of adjusting the PAW WiFi strength / channel from the default settings. I have just dealt with a similar issue for a mate running an 'upgraded' Classic on a Pi3 board (so not simply a faulty WiFi dongle) into an full size iPad in his Emeraude - which we seem to have resolved by reducing the PAW WiFi power from 50mW to 20mW. Take a note of the defaults before you make any changes and just change one field at a time and test fly before changing anything else - and remember to try both reducing the WiFi strength and increasing it. I can't remember, but you may also have to reboot your PAW each time for the changes to take effect.
Let us know if that helps.
Best Regards
Peter
-
Thanks for the reply Steve and Expo.
My PAW classic has a password, so not an open network problem.
Samsung update the tablet more often than I use it :-)
I have been using i-grid intermittently, I haven't seen a correlation but will monitor that.
When I ON-OFF-ON the wifi it always connects to PAW, I don't see any other hotspots and have intentionally turned all other devices off which may have been more attractive to my tables wifi
Often it will connect automatically after random times from a few seconds upwards.
Maybe a "forget network" and re-enter the PAW login credentials is worth a try?
Strange thing is it always occurs after about 20 mins or more after take off.
ATB
Deker
-
Android has a habit of doing this when any power/battery saving options are enabled
Try disabling
-
Android has a habit of doing this when any power/battery saving options are enabled
Try disabling
Ditto data saving or compression...
-
I updated the PAW firmware to 20230512
Had a quick pootle about this afternoon, got the message after about 15mins, reconnected automatically and was Ok for rest of the flight.
I've just checked, and power saving is off.
Running android 13
PAW is set to UDP.
Phone worked as second screen without wifi dropout.
Will check the wifi power next time.
ATB
Deker
-
I had the same problem today a couple of times - a warning that connection had been lost, but no discernible problem in Skydemon. The logs were intact as a single log, and it seemed to recover immediately. I wonder if this is a very minor timeout issue, that was hidden from us before Tim introduced the audio alert to loss of connection in SD recently?
Dave
-
Flight on 27th/5/23 after clearing all the wifi settings (forget networks) on my tablet resulted in no change.
Connection was OK for about 15mins, then multiple "waiting for device banner" warnings but connected automatically in 1-2 seconds.
Then after about 8 disconnections, it stubbornly refused to auto connect so had to toggle wifi on/off/on.
Phone operating perfectly throughout.
Might check the PAW wifi power next time.
-
I encountered this problem yesterday with my new Samsung Galaxy Tab A7 Lite (SM-T220 model, Android 13) and my PAWClassic with the latest PAW software.
When I connected the tablet to the PAW wifi it detected that there wasn't an internet connection and asked if I still wanted to connect which I told it to do. As soon as I told Skydemon to use pilotware it connected then proceeded to loose the connection and re-connect every couple of minutes. I'd disabled power saving on the tablet and any other settings that I thought may affect it. I tried changing the wifi power settings on the PAW but it made no difference
As the PAW wifi connection was unusable I then tried connecting it to my Skyecho and had no disconnects at all (during a one hour flight) which makes me think that it maybe something in the PAWwifi setup.
I've done some digging today and had a look at the wifi settings on the Skyecho and its got the wifi channel set to auto (and was using channel 11). I tried setting the PAW to channel 11 and the connection in Skydemon stayed up for about 10 minutes before I got the connection lost message so some improvement. I'm going to try setting the wifi channel to auto and see what happens.
I'd like to try changing the mode setting but as I don't know what it does I'm concerned that I may lock myself out of the PAW.
One other thing I noticed was that the tablet seems to run some sort of check on the wifi connection every minute or so
My old Google Nexus 7 (Android 6) had no issues at all so I was able to use that.
Brooklands
-
I encountered this problem yesterday with my new Samsung Galaxy Tab A7 Lite (SM-T220 model, Android 13) and my PAWClassic with the latest PAW software.
When I connected the tablet to the PAW wifi it detected that there wasn't an internet connection and asked if I still wanted to connect which I told it to do. As soon as I told Skydemon to use pilotware it connected then proceeded to loose the connection and re-connect every couple of minutes. I'd disabled power saving on the tablet and any other settings that I thought may affect it. I tried changing the wifi power settings on the PAW but it made no difference
As the PAW wifi connection was unusable I then tried connecting it to my Skyecho and had no disconnects at all (during a one hour flight) which makes me think that it maybe something in the PAWwifi setup.
I've done some digging today and had a look at the wifi settings on the Skyecho and its got the wifi channel set to auto (and was using channel 11). I tried setting the PAW to channel 11 and the connection in Skydemon stayed up for about 10 minutes before I got the connection lost message so some improvement. I'm going to try setting the wifi channel to auto and see what happens.
I'd like to try changing the mode setting but as I don't know what it does I'm concerned that I may lock myself out of the PAW.
One other thing I noticed was that the tablet seems to run some sort of check on the wifi connection every minute or so
My old Google Nexus 7 (Android 6) had no issues at all so I was able to use that.
Brooklands
This is a useful bit of information. The important bits are as follows
1. The SkyEcho stayed connected
2. The tablet seems to run some sort of check on the wifi connection every minute or so
3. My old Google Nexus 7 (Android 6) had no issues at all so I was able to use that.
OK, why is this interesting - well its as follows.
When PilotAware accepts a connection it advertises itself as not having a router capability, ie it tells your device you "cannot connect to the internet through me", this allows a cellular device the opportunity to connect to the internet through its 3g/4g connection rather than attempting to use the WiFi (PAW) connection
My understanding is that SkyEcho does not have this setting, and therefore any WiFi client thinks it can access the internet - even though it cannot
The fact that your older device does not make this check, sounds like the clincher.
My Android device does not seem to care either
Do you have iGrid ?
If so can you enable the router option when connected to iGrid and see if that satisfies the tablet that it can see the internet, and does not therefore attempt to go looking for another connection
some additional searching
https://android.stackexchange.com/questions/130265/stay-connected-to-specific-wifi-which-has-no-internet
also this post
https://android.stackexchange.com/questions/110471/disable-internet-access-detection-of-wifi-networks
says to disable 'Avoid poor connections'
-
Short trip to Leicester today, got the usual "waiting for connection" message after about 20 mins.
Returning after a chance meeting and chat with Brooklands at Leic' I set as the "GSM" hotspot and no drop out.
PAW has always been set to "Router mode".
Will repeat the test on next trip to check if this wasn't a fluke.
If this works, can PAW spoof a GSM connection even when a real GSM is not available?
ATB
Deker.
-
Not directly related to PAW, but a similar issue.
This week I had to record a presentation and planned to connect my laptop to my camera. Create a WiFi hotspot on the laptop and connect the camera to it. Tested it at home and all worked well and I was able to monitor the recording and adjust it as needed. At the venue there is no Wifi, and I do not have GSM in the laptop. When I tried to activate the hotspot previously created, the laptop reported that it cannot see the internet, so failed the Hotspot >:(
Under Windows you can configure this from the command line or install a Microsoft app called 'Hotspot lite' to resolve this issue. I suspect there are other fixes for various OS. Not tried either yet
-
An update.
I haven't been able to reproduce the problem where the new tablet kept dropping the connection to the PAW as soon as I told SD to use it.
On the trip to Leicester yesterday I had my old (Android 6) tablet connected to the PAW and my new tablet (Android 13) connected to the Skyecho. Neither lost the connection.
On the way back I set up the PAW with iGrid, but missed enabling the router setting and the new tablet lost the connection after about 20 minutes but reconnected immediately.
I've done some more tests today at home with the PAW set up with iGrid via my broadband connection but SD is still loosing the connection. Its ok for about 15 - 20 minutes the I get the connection lost audio message but the table reconnects almost immediately it then goes another 10 -1 15 minutes before dropping again and reconnecting before going into a phase where it constantly drops and re-connects, sometimes immediately and sometimes after a few seconds. I also re-ran the test with the Skyecho and the connection stayed up until I stopped the test after 40 minutes.
I've had a look at the two links but I don't have the "Avoid poor connections" option in the Advanced settings and I'd rather not root the device which the others suggestions seem to need.
Brooklands
-
Will repeat the test on next trip to check if this wasn't a fluke.
If this works, can PAW spoof a GSM connection even when a real GSM is not available?
ATB
Deker.
Same test but today I got the "waiting for device message" even with GSM connection.
This is becoming a real pain.
-
Did you ever check the PAW Wifi output power and try cranking it up a notch?
-
Same test but today I got the "waiting for device message" even with GSM connection.
This is becoming a real pain.
Hi Deker,
this is odd isn't it.
let me have a think about what we can do
BTW, what software version are you running - I know you have access to the Beta
was your flight using igrid ?
if so I should be able to access some log information if I can get your MAC Address of your PAW
Thx
Lee
-
Hi Lee,
I have one of the betas from a couple of weeks ago, I'll check the version, think its 20230512.
the flight should have been using igrid as my phone was set to hotspot but didn't check the PAW page as had Skydemon running.
MAC is B827EB7BC28D.
There were 2 or 3 quick disconnects after about 10 mins and automatically reconnected each time, then a disconnect and after about 15 secs I turned wifi on off on and it was mainly ok for rest of the flight.
The pattern is reasonably repeatable. OK for 10 to 15 mins, then get disconnects which eventually requires a wifi on off on.
Only a problem with my new tablet running android 13. Phone also on Android 13 is faultless for whole flight.
One difference is phone has active SIM where tablet has GSM capability but I don't have a SIM fitted.
ATB
Deker.
-
I get similar behavior with Pi3b and newest software. using Skydemon I get 'waiting for device' and find that the WiFi hotspot is gone. WiFi drops out seemingly randomly. Seems to be most often in the early part of a flight though. Sometimes the wifi hotspot of the paw re-appears, sometimes it doesn't and I have to 'reboot' the paw. Then in flight it kind of stabilizes and often the whole flight is ok. Same thing happened several times on Samsung S22+ and Sony Tablet Compact, Android. Same thing happened with a Pi2b and wifi dongle, rather than Pi3b/builtin wifi. Didn't have these problems in the past with Pi2b but now any configuration of hardware seems to result in the same problem. If anyone had similar issues and solved them, please share what you did because it's a mystery for some of us.
-
Same problem yesterday, multiple "waiting for device" this is making my PAW effectively useless combo with my Samsung tablet.
Has there been any updates to fix this issue?
TA
Deker
-
Has anyone worked through Peter's instructions about Wifi power on the previous page?
-
I have had similar issues with WiFi disappearing - it's not low wifi power, it completely goes until I reboot the Rosetta. The GPS output to my Trig transponder continues to work and it stays connected to my phones hotspot.
I have now bought a new RPi3b to see if this fixes the problem but can't test it as I'm having trouble getting an activation code from support. Emailed with old and new mac addresses on Thursday but no reply and nobody answers the support phone.
Help! Please!
-
Hi Ray I have sent yu a private message for your details
Thanks
Keith
-
After several longish flights I think I can confirm that replacing the Rasberry Pi has fixed my intermittent loss of WiFi connection and all is right again.
Thanks for the updated activation code.
-
Couple of flights yesterday.
Wifi was set on 100mw, set this to 50mw
Running Skydemon on my 'bad' tablet and good phone.
Lots of disconnections on the tablet after 10 to 15 mins, but the phone was rock solid.
I think this more of an Android issue than a hardware problem.
I'll try putting a sim in the tablet to see if its is a network problem? (clutching straws)
ATB
Deker
-
Running Skydemon on my 'bad' tablet and good phone.
Lots of disconnections on the tablet after 10 to 15 mins, but the phone was rock solid.
I think this more of an Android issue than a hardware problem.
I'll try putting a sim in the tablet to see if its is a network problem? (clutching straws)
The SIM may confuse the issue, as if the table connects to the Internet directly over CGNAT it may not see any of the PAW LAN. It might still connect via Wifi though...
I'd suggest that you load the same Wifi analytics app on both phone and tablet. As an example, VREM Software Wifi Analyzer.
Compare them side by side looking at the same Wifi networks. Any noticeable difference in receive power would point to problems in the RF amp or internal antenna damage?
-
App details separate. Attachment limits are very small and difficult to comply with...
-
Following this with interest. Much comment about Android and with/without SIM. I use iPad Mini 4 (with a SIM) and also experience intermittent dropouts reported by SkyDemon so perhaps this rules out Android/SIM. I also have hardwire to a Dynon Skyview which continues to show traffic. I'm making the link here that, if traffic continues to be shown on Skyview, then PAW must have a GPS signal but, for some reason, is not broadcasting it to the iPad. Maybe this helps?
-
I'm leaning in the same direction. I have had a couple of 'Waiting For Device' messages but they did not last very long and auto-connected again. The most recent was after only about 15 minutes. I have a serial connection to my Skyview HDX and traffic remained on the Dynon screen. To add to the confusion, my PAW is served GPS from the HDX and the GPS remained on the HDX, so I do not think it is GPS related.
-
If anyone is concerned about the PAW receiving GPS, they can download the tracklog for the particular flight from the device and upload it to playback.
When scrolling through the tracklog, the number of satellites received at any time will be show IIRC.
-
Distilling all above, looks like GPS ok and culprit is intermittent WiFi dropouts. Does PAW log this and, if so, how to find?
-
I'm leaning in the same direction. I have had a couple of 'Waiting For Device' messages but they did not last very long and auto-connected again. The most recent was after only about 15 minutes. I have a serial connection to my Skyview HDX and traffic remained on the Dynon screen. To add to the confusion, my PAW is served GPS from the HDX and the GPS remained on the HDX, so I do not think it is GPS related.
I'm almost certain it's not GPS related.
With phone and (new) tablet running simultaneous, only the tablet has the problem. Phone is rock solid every flight.
Also, when I use my other (older) tablet in place of the new tablet (same location in the plane) , this also runs without the dropouts.
I think it is an Android version issue (or my tablet is knackered - don't think so as it works fine on my home wifi).
I've tried all the recommendations I can find on internet for wifi dropping but has had no affect, which sort of make me think it is a PAW / android version incompatibility.
-
I'll just muddy those waters by saying I have an iPad Mini 4 and not an Android in sight ???
-
I'll just muddy those waters by saying I have an iPad Mini 4 and not an Android in sight ???
But you can still look at received RF power for the Wifi network...
-
I realise that but I was responding to Deker's suspicion:
I think it is an Android version issue (or my tablet is knackered - don't think so as it works fine on my home wifi).
I flew yesterday and no snags at all.
-
I think this issue is unrelated to power
The fact that Deker has a solid client on the apple device, but not on the Android
Points to an issue with the android device I think
Thx Lee
-
I think this issue is unrelated to power
The fact that Deker has a solid client on the apple device, but not on the Android
Points to an issue with the android device I think
Thx Lee
To add, flying buddy flew one leg and his iOS (and PAW) functioned perfectly also my phone running SD radar page concurrently.
It appears only to be my new Android tablet that has the issue. My old tablet and current phone, also both android are OK.
ATB
Deker.
-
My experience is similar to Deker's - its fine on my old Nexus 7 running Android 6. The problem only occurs on my Samsung Galaxy Tab 7 running Android 13.
The Samsung tablet used to be OK with my Skyecho 2, but last time out I had issues with it losing the connection to the SE2 as well.
I managed to borrow a a Google Pixel running Android 13 off a colleague for a test on the ground and didn't see any warnings on the screen with that over about an hour, but was also expecting audio warning and only found out afterwards the volume had been turned down.
I think its an issue with Android 13,or perhaps just Samsungs implementation of it.
Brooklands
I
-
I'm running a Samsung Galaxy Tab A7 Lite (SM-T220) on Android 13, and although I was having problems earlier in the year with "waiting for device" messages, I haven't had any in the last couple of months. I've reduced the power output of the PAW, as I keep getting the "throttled" message (different problem).
Not sure if this helps. Happy to check other device settings if people want me to.
Dave
-
I think I have found a kludge/work around for the problem (I hesitate to call it a fix).
I was doing some tests on the ground to try and find out what was happening to the WiFi connection between my Samsung Galaxy Tab A7 Lite (SM-T220)and the PAW. I downloaded an app called PingMon (https://play.google.com/store/apps/details?id=com.mishuto.pingtest&hl=en&gl=US) to monitor the WiFi connection to see if I could see it dropping. With Pingmon running and Skydemon connected to the PAW in go flying mode I didn't get any dropouts over the hour I ran the test for.
It also worked fine on my flights to and from Fenland on Saturday.
I need to do some more testing to find the optimum settings. You need to increase the time Pingmon runs before it stops itself (the default is one hour) but you can set it to not stop until you close the app.
Brooklands
-
Hi All, I came on this forum looking for a solution to my "waiting for device" issue and found this topic almost instantly.
This has been happening to me since I updated to Android 13 a few months ago and adding iGrid at the same time so I'm not 100% which is the main cause but I think they are both connected.
It certainly seems that it's related to the tablet looking elsewhere for a wifi connection that can provide internet instead of PAW. The other day it happened on the ground before takeoff and would not reconnect to PAW at all, it couldn't even see it or scan it. I found that it had actually switched to using an open wifi connection on a SkyEcho device on an adjacent aircraft and seemed to have tagged PAW as unusable. I hadn't ask it to look for that, it just moved on it's own accord. I also have the issue regularly in the air and I think it is trying to connect to the mobile phone hotspot that I have setup for iGrid. I've made sure it doesn't have the connection or password for the hotspot saved but I think it still drops the PAW wifi link in order to try it. Sometimes it comes back to PAW after 5 secs or so and sometimes it drops it completely and I need to reboot PAW.
I need to find a way to stop it from dropping the PAW wifi and making it stay with it. I have tried various settings and nothing works so far. Is there a way to make PAW say it provides (spoof) Internet so it doesn't drop?
or is there any other way to sort it out. This is becoming very distracting and quite dangerous in my opinion and always seems to happen to me at just the wrong time. e.g. threading my way through a narrow gap between airspace etc.
I think it will start to affect more and more people in the near future as they get newer android devices or upgrade versions on existing and I think this issue will grow rapidly.
I noticed there is also another "Wifi disappears" topic below so is becoming more prevalent.
-
Paw does not advertise itself as a router, unless you explicitly select it to on the network page
Skyecho DOES advertise itself as a router, so as you say devices prefer it in order to gain access to the internet, which is totally bogus, as it is not a router
You could enable the router feature AND add passwords to restrict access
-
Fairly sure I tried that already, but I'll try enabling the router setting again to be 100%. I think the new Android versions check for internet traffic as well as basic connection and if no joy sending/receiving data they move on to try another wifi gateway, so would still drop PAW.
-
Paw does not advertise itself as a router, unless you explicitly select it to on the network page
Skyecho DOES advertise itself as a router, so as you say devices prefer it in order to gain access to the internet, which is totally bogus, as it is not a router
You could enable the router feature AND add passwords to restrict access
I have router enabled and passworded, I still get "waiting for device".
-
I think I have found a kludge/work around for the problem (I hesitate to call it a fix).
PingMon (https://play.google.com/store/apps/details?id=com.mishuto.pingtest&hl=en&gl=US)
Brooklands
Hi Brooklands,
I tested with Pingmon running and no "waiting for device" during my 1:15min flight today, hallelujah!! ;D
This does does give further evidence it's a Android 13 'thing', not PAW or hardware issue.
Wonder if PAW can "reverse ping" the tablet to generate the same effect?
ATB
Deker.
-
Deker,
Glad to hear that its worked for you as well, I had no isses yesterday on my trip to/from Halfpenny Green with pingmon running. I'm not sure that the reverse ping would work though: my suspicion is that by forcing the tablet to constantly ping the PAW it stops the connection dropping some how.
@Colled - what make of tablet are you using? I'm trying to work out if this is purely a Samsung issue or a more general Android issue. I'm not running iGrid so that's not causing the problem. Try installing and running pingmon as this seems tohave 'fixed' the issue for Deker and myself.
I don't think its the lack of internet connection as my Nexus 7 (running Android 6) doesn't drop the connection to the PAW even though it recognises that it doesn't have an internet connection.
Brooklands
-
I am using a Lenovo M9 so different hardware to you, so does sound Android 13 specific.
I'll try using pingmon, does it affect battery life having that running?
If a ping from that app is enough to keep the connection open, I would have thought the data that PAW sends across the connection to Skydemon would also be enough to keep the connection open!?
-
Its a strange one
One thing you could try is connecting as flarm rather than pilotaware
The flarm setting uses TCP, rather than UDP
Thx
Lee
-
Colled,
I don't know how pingmon affects battery life on the tablet for certain, but I don't think it has a significant effect - I haven't noticed anything on the flights I've done since I started using it. I can only guess why it keeps the connection up whereas incoming data doesn't.
@Lee - I've done a test on the ground were I tried setting the PAW to TCP/Flarm and connecting SD using that but I still get dropouts, although they are not as bad as setting the PAW to "All"
Brooklands
-
Putting this out there as it's maybe worth a try and easy to do..
I was plagued with this issue on my previous tablet, a Lenovo device which I eventually permanently solved with an 'off the wall' so to speak solution.
This was to create another user on the machine such as Guest (which you never have to use BTW) This can be done on the Samsung device from Settings / Accounts and Backup /Users / Add guest
How and why it worked I haven't a clue, but worked it certainly did!
The original post is here http://forum.pilotaware.com/index.php/topic,1091.msg16603.html#msg16603
My current device, a Samsung Tab A7 Lite SM-T220 (not a SM225 like the OPs) has never had the issue even without the Guest account and IGrid
-
I've now tried flying with Pingmon firing a ping every second to 192.168.1.1 and it made no difference for me, I still got multiple PAW disconnections :(
It always seems to happen at just the wrong time as well, when I most need to know where I am in confined airspace and is very distracting, bordering dangerous.
I can't justify buying a new tablet until I find one that works with PAW so I think I will need to find an alternative to PAW that will work.
-
Last flight I forgot to run pingmon and after about 10mins I got the dreaded "waiting for device".
Quickly started pingmon and was all OK for the rest of the flight and the return.
i've set up a guest account on my android 13 device and will test to see if this is an alternative fix to pingmon.
ATB
Deker.
-
I've now tried flying with Pingmon firing a ping every second to 192.168.1.1 and it made no difference for me, I still got multiple PAW disconnections :(
It always seems to happen at just the wrong time as well, when I most need to know where I am in confined airspace and is very distracting, bordering dangerous.
I can't justify buying a new tablet until I find one that works with PAW so I think I will need to find an alternative to PAW that will work.
Connect the audio out from the PAW to the audio input of your radio or intercom, and get audio alerts for traffic.
Run the tablet using its own location services. Then it will not lose its location when you are transiting airspace. There will be no on screen traffic, but then you have audio alerts.
-
If I connect PAW to the comms audio instead of the tablet I won't then get the airspace and other warnings from Skydemon through the headset which I find quite useful. And if I use the tablet location service instead of PAW on Skydemon then I also don't see the traffic on screen. So I lose both traffic and airspace awareness which is no good.
-
I am using a Lenovo M9 so different hardware to you, so does sound Android 13 specific.
If it's Android specific you know the answer.
-
If I connect PAW to the comms audio instead of the tablet I won't then get the airspace and other warnings from Skydemon through the headset which I find quite useful. And if I use the tablet location service instead of PAW on Skydemon then I also don't see the traffic on screen. So I lose both traffic and airspace awareness which is no good.
In which case, as Paul has posted, you either need to to do some fault finding with a different Android device or try the same with iOS.
-
If it's Android specific you know the answer.
I could look for an older 2nd hand android tablet or switch to Apple, but in the meantime PAW is no longer compatible with new Android tablets, which seems less than ideal.
-
If it's Android specific you know the answer.
I could look for an older 2nd hand android tablet or switch to Apple, but in the meantime PAW is no longer compatible with new Android tablets, which seems less than ideal.
I think you're looking at a miniscule sample of the Android user base.
Where the aircraft is flying with some form of internet access for the PAW, the Android device will be more likely to stay connected because there is Internet access.
One solution is to get a simple mobile broadband router or MiFi and to connect the PAW to that wirelessly via the iGrid dongle.
Then any device connected to the PAW with the PAW router function enabled sees the Internet and has no reason to move or drop the connection.
Have you thought of trying this?
It is my own set up and comes with other benefits, like the licence auto updating without retyping the new key, supplementary traffic and rainfall radar, and so on.
-
If only it was that easy, I already have this setup with iGrid on to a hotspot and get all the additional traffic and weather etc. but it doesn't help with my disconnections unfortunately.
-
If only it was that easy, I already have this setup with iGrid on to a hotspot and get all the additional traffic and weather etc. but it doesn't help with my disconnections unfortunately.
As an engineer working in the field we often fix or diagnose problems by substitution. Given that most of us have iGRid working on other Android phones/tablets with no problems, it would be a good fault finding technique to swap out the tablet. If the fault goes, you are happy. If the fault remains, we can look at other areas for a more complicated fault, secure in the knowledge that the tablet has been exonerated.
Does the tablet get used for anything else and have you used a Wifi diagnostic tool to check RF levels? With a Wifi tool on a known working phone and the tablet in question difference of received RF levels might be a clue. Also, you could see how well the tablet receives the PAW Wifi.
-
Well I wish I had read this thread before buying a “Samsung Galaxy A7 Lite” to replace my old iPad. (Skydemon are no longer supporting anything older than IOS10, so my trusty 11 year old ipad used only for SD, has become redundant as its stuck with iOS9)
anyway, as previously described by others, the Samsung tablet is totally unusable with PilotAware Classic, waiting for device pops up in flight at random times when navigating with SD. Most frustrating and totally unusable.
-
Well I wish I had read this thread before buying a “Samsung Galaxy A7 Lite” to replace my old iPad. (Skydemon are no longer supporting anything older than IOS10, so my trusty 11 year old ipad used only for SD, has become redundant as its stuck with iOS9)
I'm led to believe that what Skydemon can support with newer releases is controlled by Apple. It may be an Apple Store restriction that new releases can't go on for versions of iOS unsupported by Apple?
Some manufacturers of Android devices mess about way too much with stock Android, adding their own skins, bloatware and other unwanted crud to the devices.
It's best to stick with something close to vanilla Android, as it will get more use/snagging out in the field that the more exotic, down a rabbit hole rework of the OS used by likes of Oppo.
You may also be able to flash the tablet with something else when it's out of guarantee...
-
the Samsung tablet is totally unusable with PilotAware Classic, waiting for device pops up in flight at random times when navigating with SD. Most frustrating and totally unusable.
I agree, it is distracting to the point of being dangerous.
Pingmon worked for me, but it is one more thing to remember to set running before take-orff.
Prior to my last flight I had set up a guest account on my Samsung Android tablet, suggested earlier up the thread.
It was a short flight of 30 min but I didn't get a "waiting for device warning" (ping mon not running) where I'd normally get the message within 10 mins.
I need to uninstall Pingmon and test with again over a few more flights. I'll report back once done.
Deker
-
Ive binned* the Samsung Galaxy A7 Lite because of the disconnects, bought a new iPad Mini, hopefully I can get a good few years out of this one, rather like the last one.
*I've actually given it away
;)
-
40min flight on Sunday:
Ping mon not running.
Guest account on my Samsung Tablet.
Rock solid connection without a single "waiting for device".
Will uninstall pingmon and do further tests, after plane comes out of annual, but this looks like a fix.
ATB
Derek.
-
It appears that Vic has found the simplest solution to this problem, although I haven't tried it myself yet. I haven't had any issues when running Pingmon*.
I'm adding this as a postscipt for completeness.
I managed to borrow a Google Pixel phone from a collegue running 'stock' Android 13 and ran it alongside my Samsung Galaxy A7 lite (without Pingmon running) for about 45 minutes. The Samsung was dropping the connection at random intervals whilst the Google Pixel was rock solid. So it seems that the issue is the customisation(s) that Samsung (and possible other manufacturers) make to the basic Android OS rather than Android itself.
As far as the Samsung goes I suspect it may be the Knox security software as I know from colleagues it causes other issues when used with work systems
*except the time I hadn't increased the "stop after" interval to 2 hours (I probably ought to set it to never) and the connection dropped as I was nearing my destination
Brooklands
-
Now after a good number of flights, I'm confident that the "waiting for device" issue is fixed.
I added guest account to my Android tablet.
Uninstalled Pingmon.
Not had a single connection drop out since adding the guest account and I don't have to remember to set pingmon running.
ATB
Deker