5GHz WLAN #31
Comments
|
I don't, at present, have access to a phone new enough to support 5G WLAN. Would you be willing to work with me by installing special test builds and sending me logging information? It might be a rather slow process. . . |
|
@n76: Galaxy S2 is a very old phone but with LineageOS it can connect to 5Ghz WLANs also better than new phones. |
|
@ale5000-git Thanks! I've just placed a debug build at https://cloud.fitchfamily.org/index.php/s/4L23XRZ62PQwwBt all it does is add a Log.d just after the detection of 2.4 vs 5 GHz with the value and the data used to make the determination. You can watch for it with: |
|
@ale5000-git Can't really test it on my phone, but based on re-reading the WLAN ScanResult documentation, I've got a revised detection for 2.4 vs 5 GHz at: https://cloud.fitchfamily.org/index.php/s/eo7xtAw7mpfXFqc |
|
@n76: I don't get any entry with rfType. |
|
That looks like the normal start up set of logs. Have you used the backend before (i.e. has it built a database)? If not, then using an app like SatStat, OsmAnd, etc. with location set to high accuracy should start populating the database and generating those rfType messages. |
|
@n76: I had to reset it for the signature mismatch. Now I get it with SatStat: |
|
Looks like it detected a 5GHz access point, I see this one in the list twice:
So now I am confused: The released code should still have detected this. Are there 5GHz WLAN/WiFi signals being detected that are not give in the ScanResults because of some scan setting, etc.? So should the issue be closed or not? Interesting that centerFreq0 and frequency fields are both set. I was under the impression from the documentation that it might not be the case. Also interesting that you've got fields for distance and distanceSD. That would make the back end much more accurate if I could use those if values were defined but they aren't in the WiFi ScanResult documentation. I think I'd need to use the WifiRttManager but I haven't a phone that supports that to develop and test it. |
|
If you upload a file same of the release but with log messages I can test it also. About WifiRttManager, I can't help now but in the future I will look at updating Galaxy S2 to Pie and then I will see if it works. |
|
Here it explain how to calculate distance. |
@ale5000-git I've released v1.1.12 and it includes the 5G WLAN logging. You can download a signed release from https://github.com/n76/DejaVu/releases/tag/v1.1.12 However I haven't figured out how to do verified builds so the signature on it will not match with F-Droid's. If you are using the F-Droid version and want to retain your database then you may wish to wait for F-Droid to pick up this release. |
|
As i can see in output of logcat DejaVu Backend can detect 5Ghz APs perfectly but anyway it does not write them into database for some reason (and therefore does not use it) |
|
I have 4 entries of 5 GHz APs in the database, but they never change no matter what I try. Edit: I just tried older versions of DejaVu. |
|
Apparently (according to WifiAnalyzer) 6GHz is now the latest new hotness™. Though, I've not yet encountered any 6GHz 802.11 transmitters. |
|
I've faced this also. Then I found, that location is not saved because of this: if ((gpsLoc == null) || (gpsLoc.getAccuracy() > ourCharacteristics.reqdGpsAccuracy)) { gpsLocation has accuracy 25.538006 and ourCharacteristics.reqdGpsAccuracy is 10. So the question to @n76 is - is this correct? |
|
Yes, it will never be saved if the accuracy is worse than But even if the GPS accuracy is better, there's a catch: DejaVu uses a Kalman filter to determine location and accuracy for devices with bad GPS. On my device the accuracy returned by the Kalman filter almost never is better than 10 m. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
subj not collected by this backend: database lacks any wifi records other than "WLAN_24GHZ". also there is no traces from known 5GHz access points (no ssid nor bssid)
The text was updated successfully, but these errors were encountered: