XPost: alt.comp.os.windows-10, comp.mobile.android   
   From: mickeydavis078XX@ptd.net   
      
   On Sun, 28 Jan 2024 15:50:53 +0000, Java Jive wrote:   
      
   >> That WiViz survey is hard to read. What's all that bouncing around?   
   >   
   > Yes, it's a bit manic, but you can alter that in the options.   
      
   Thanks for that hint. I froze that geospacial WiViz with screenshots   
   but I see now that you mentioned it that it can be made to be static.   
      
   I'm guessing this image is trying to geospacially locate (so to speak) the   
   Wi-Fi access points, relative to the location of the WNR834Bv2 bridge.   
      
   >> I like the Ubiquiti Wi-Fi Man debugger, but is this the one you use?   
   >> https://play.google.com/store/apps/details?id=com.vrem.wifianalyzer   
   >>   
   >> Or is it this WiFi Analyzer?   
   >> https://play.google.com/store/apps/details?id=com.manageengine.wifimonitor   
   >   
   > It's neither of those.  In fact, I've just searched for it and can't   
   > find it in the App Store any more, I don't know why not but perhaps the   
   > original developer lost interest in updating it.   
      
   I've noticed a lot of the more powerful apps are being slowly removed from   
   the Google Play Store. I attribute it to them mostly being FOSS where they   
   don't always have the time & energy to keep up with Google's new split-APK   
   rules (which seem to require them to build APKs a different way lately).   
      
   > The only 'versions' of   
   > it around now seem to be from unreliable sites which I wouldn't wish to   
   > recommend because at least some of those 'versions' seem to be flagged   
   > as potential malware.   
      
   You don't need to recommend an iffy APK because, luckily there are many out   
   there that do both Wi-Fi and network analysis on the Android phone today.   
      
   What everyone needs in their Wi-Fi debugging folder is 3 types of tools.   
   A. Wi-Fi debuggers (these work for Wi-Fi channels but not interference)   
      https://play.google.com/store/apps/details?id=ru.andr7e.wifimonitor   
   B. Cellular debuggers (these only work for one carrier's SIM at a time)   
      https://play.google.com/store/apps/details?id=com.qtrun.QuickTest   
   C. Network debuggers (these are similar to those on the Windows PC)   
      
   There are other tools that I'm not sure of such as heat-map monitors   
   (which I think are used to map out floor-plan coverage for Wi-Fi).   
   https://play.google.com/store/apps/details?id=com.etwok.netspotapp   
      
   And tools to tell you if you're using the latest patches & router firmware.   
   https://play.google.com/store/apps/details?id=com.stoutner.privacycell   
      
   There are even tin-foil-hat tools to find if insecure protocols are used   
   https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch   
      
   And for the tin-foil-hat user, tools to find stingrays (IMSI catchers).   
   https://play.google.com/store/apps/details?id=com.skibapps.cellspycatcher   
   WARNING: No app from me will have ads unless I say so; this one does.   
      
   > I bought my first android smartphone in 2012 and   
   > a year or two later found WiFi Analyzer (the one we're discussing, by   
   > Kevin Yuan) in the App Store and installed it on that phone; AFAICR   
   > without actually checking, my current phablet is about 5 or 6 years old,   
   > and the app was still in the App Store when I was setting up that   
   > tablet, or perhaps I just copied it from the phone; in neither of these   
   > cases were there any problems from malware using the original app from   
   > the App Store.  I suppose what has happened since is that malware   
   > writers have hijacked a clean original version from when it was widely   
   > available and adulterated it.   
      
   You might not know this but, unlike Windows, Android never deletes the   
   original APK installer - it just changes the name to "base.apk" for   
   every app you've ever installed. So you can copy it direct to Windows.   
      
   This will give you the unique package name (if "wifi" is in the name).   
    CMD: adb shell pm list packages | findstr /i "wifi"   
         package:com.vrem.wifianalyzer   
         package:com.samsung.android.wifi.softap.resources   
         package:com.google.android.apps.carrier.carrierwifi   
         package:com.samsung.android.wifi.h2e.resources   
         package:com.samsung.android.server.wifi.mobilewips   
         package:com.samsung.android.wifi.p2paware.resources   
         package:com.samsung.android.wifi.softapwpathree.resources   
         package:com.keuwl.wifi   
         package:com.android.wifi.resources   
         package:com.samsung.android.wifi.resources   
         package:com.manageengine.wifimonitor   
         package:com.samsung.android.net.wifi.wifiguider   
         package:com.android.wifi.dialog   
         package:ru.andr7e.wifimonitor   
      
   Then you can find the path on Android to any of those packages it finds.   
    CMD: adb shell pm path com.keuwl.wifi   
      package:/data/app/~~17JnPS2TxnX4dB1JH1wezQ==/com.keuwl.wifi-z   
   co0PcHZ1Z0cImyNCvrMQ==/base.apk   
      
   Then you can pull that original installer from Android onto Windows.   
    CMD: adb pull /data/app/(see scrambled eggs above)/base.apk   
    CMD: rename base.apk com.keuwl.wifi.apk   
      
   Using this method you can archive every original installer on your   
   Android phone onto the same directory you store Windows archives.   
      
   What that means is you never need to download an app twice.   
   1. You install the app once off the Google Play Store (or from wherever).   
   2. You save the APK (just like I did above) into your Windows archives.   
   3. When you get a new phone, you repopulate that phone with the apks   
      CMD: adb install com.keuwl.wifi.apk   
      
   The best way to manage an Android phone is always going to be from Windows.   
      
   > So if the one you are using is working satisfactorily, I wouldn't bother   
   > about trying to find another.   
      
   Don't worry. I have plenty of radio and wi-fi debugging apps on my phone.   
      
   Take a look as I just ran those commands for you so that I would be   
   absolutely positive that I was providing you the proper correct syntax.   
   https://i.postimg.cc/jSBfSgRC/baseapk.jpg   
      
   >> The only thing I did was burn the latest firmware for every access point   
   >> including the Ubiquiti access point that the WNR834Bv2 wireless client   
   >> repeater bridge was WNR834Bv2 connected to.   
   >   
   > That at least is a significant improvement, but it's still not   
   > symmetric, although it now may well be liveable with, only you can   
   > decide that.  Also it does suggest that I was on the right track to   
   > suggest a problem with the system rather than extraneous noise.   
      
   I think you are correct that it's may not be noise as I ran the free   
   spectrum analysis (which will find EVERYTHING in the band, not just   
   inside of Wi-Fi channels) and, while I'm not sure how to interpret   
   what it found, I don't see any smoking gun (but maybe I'm missing it).   
   https://i.postimg.cc/8krQvmf8/longtime.jpg   
      
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)