XPost: alt.comp.os.windows-10, comp.mobile.android   
   From: mickeydavis078XX@ptd.net   
      
   On Mon, 29 Jan 2024 11:43:18 +0000, Java Jive wrote:   
      
   >     CMD: adb install com.keuwl.wifi.apk   
   >   
   > Tx, copied all of this to a another folder in case useful for future   
   > reference.   
      
   The best way to manage Android is from Windows, generally over Wi-Fi, but   
   if you keep the phone close to the PC, then USB also works almost as well.   
      
   Given Android never removes the original APK installer, you can always copy   
   it to Windows, but there are easier ways than adb to collect all of them.   
   https://play.google.com/store/search?q=apk%20exttractor&c=apps   
      
   >> The best way to manage an Android phone is always going to be from Windows.   
   >   
   > Not entirely sure I agree, but will leave it.   
      
   I didn't say "adb" was the best way to manage Android; I said Windows was.   
   APK sucks because it's a command-line tool - but APK enables GUI tools.   
      
   For example, you can mirror Android onto Windows and just slide the APK   
   over from your Windows screen onto your Android screen & that installs it.   
      
   You can mount Android as a drive letter onto Windows so you can use the   
   Windows File Explorer to manage every installer APK that you've extracted.   
      
   But where are you going to get all the hundreds of installed APKs from?   
   Easy. There are so many good (& bad) APK extractors, I'll suggest this.   
   https://f-droid.org/packages/com.apk.editor/   
      
   But if folks are stuck on the Google Play Store, then I'll suggest this   
   application inspector & extractor which does all that abd did, and more.   
   https://play.google.com/store/apps/details?id=com.ubqsoft.sec01   
      
   Note that they're called "APK extractors" but all they do is copy/rename   
   the "base.apk" which Android always stores for every app installed on it.   
      
   >> Can helpful people let me know what you think of that spectrum analysis?   
   >   
   > I can't, but maybe others can.   
      
   I googled around a bit and I think I'm supposed to just look for unexpected   
   frames of energy in areas either between channels or spanning channels.   
      
   There's so much energy out there that I'm not good at finding where it is.   
      
   It seems the lower Wi-Fi channels have higher energies so the only real   
   conclusion I could come up with is to assign APs to the higher channels.   
      
   I'm going to run a 5GHz spectrum analysis separately but since the Netgear   
   WNR834v2 is only a 2.4GHz bridge client repeater, it will just more data.   
      
   > I don't consider myself to be an expert at this sort of thing, but to   
   > explain further, it's not the fact that the Tx & Rx were, & are still,   
   > different that made me think "Hardware problem?", because I would guess   
   > that irregular differences of small numbers of errors might randomly   
   > occur in normal conditions & most probably not be significant, it's the   
   > consistent one-sidedness with significant numbers of errors that makes   
   > me suspect some sort of underlying systemic fault.   
      
   Agreed. Why would transmit be different than receive. Of course that   
   happens all the time when there is a nearby source of in-band local   
   interference because the weaker receive signal is greatly affected by local   
   interference but the stronger transmit signal would be less affected.   
      
   But in my situation, it was the transmitted signal that wasn't received 86%   
   of the time, so that points to a problem on the other end (ie on the AP).   
      
   I don't think for a moment that simply updating the AP's firmware is what   
   solved it, but I do say that it's the only thing that I overtly did.   
      
   Right now, the problem seems to be better (where I'm only losing 3% of the   
   TX & 0% of the RX) which is still lopsided, but at least not 14% to 86%.   
      
   > An off-the-wall idea:  I suspect from parts of your posts that you have   
   > some sort of mesh system, and am now wondering if the errors occur   
   > because the DD-WRT device gets confused as to which device in the mesh   
   > it's supposed to be communicating with, and perhaps if you could find a   
   > way of linking it to a particular device rather than to the system as a   
   > whole, they would go away?  Of course, if I'm mistaken and you haven't   
   > got a mesh system, the idea goes out-of-the-window rather than   
   > off-the-wall :-)   
      
   It's not a mesh system so much as access points that have to cover a few   
   football fields' worth of area - which may play a role in the noise level.   
      
   I repurpose a lot of wireless equipment that I get at the local thrift   
   shops and from a friend in the business so I have a lot of radio gear.   
      
   However, that shouldn't matter because a lot of people live in close   
   proximity to a lot of other people who have a lot of diverse radio gear.   
      
   What should only matter is the what is immediately on both sides of the   
   wireless bridge repeater, which is just this connection to the Internet:   
    PC <===> wireless client bridge <===> AP <===> main router <===> modem   
      
   > At any rate, at least things have improved, but I suspect I can't help   
   > much further now, because I'm already at the edge of my knowledge.   
      
   Me too! I've actually fallen off the cliff going well beyond my knowledge.   
   That's why I had asked here - to find the people who know this stuff.   
      
   I figured the people who know the most are gonna be on a.e.w & Windows.   
      
   >> But I'm not the only one who can't find the latest DD-WRT firmware.   
   >> https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=289360&sid=5c   
   3d9b0e602c12f2c7a8414a4a6a837   
   >   
   > Yes, it's confusing enough that I bricked one of my Cisco WRT320Ns by   
   > putting the wrong image on it, but fortunately managed to revive it to   
   > put the correct image on it, and it worked ever after.   
      
   Understood. Agreed. I gave up looking for a DD-WRT update for the Netgear   
   WNR834Bv2 because of that reason (plus I already have its 2023 firmware).   
      
   Funny story, a friend bricked his Netgear R7000P similarly so he gave it to   
   me to keep or throw away - which - forever reason - wouldn't factory reset.   
      
   A few google's later & quite a few tftp's later, I had a "new" router.   
      
   Why do I need the "latest & greatest" router for a simple household   
   when last years' latest & greatest router is being thrown away every year?   
      
   >  (I used to have   
   > two of them, but cabled one of the connections they covered, so that one   
   > became a spare, useful for odd situations, but it died quite recently.)   
      
   It started in the days of RS232 cables but I used to have "a box" for spare   
   wall warts & routers and the like but now it's an entire section of boxes.   
      
   The beauty of a router is it can be many things (like an AP or switch).   
   The beauty of Android & Windows is they run many free debugging tools.   
      
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)