Stan Brown <
the_sta...@fastmail.fm> wrote
>> Here are my relevant settings (as far as I know what to look for anyway).
>> <
https://i.postimg.cc/P5Kb99jy/wificall01.jpg> Roaming & Network Settings
>
> My Android 13 Samsung A54 5G doesn't have "Allow 5G" or "Allow 2G"
> under Mobile Networks, and neither one came up in a search of
> Settings.
Hi Stan Brown,
I know you from the Windows newsgroup and you are well respected there.
Thank you for looking at the annotated images as sometimes I wonder if it's
worth the effort to do all that work if nobody benefits from me doing that.
I would _love_ for you or Andy Burns or anyone else to explain to me _why_
the phone has those switches as they don't seem to make sense to me either.
Q: Why have "Allow 2G" and not "Allow 3G" or "Allow 4G/LTE" for example?
I agree that this is likely one of the most important switches as we're
constantly moving about when we're on a Wi-Fi call, such that we often go
down the driveway while still on the call - and then - it drops on us!
Why?
Probably because it didn't switch over to Wi-Fi data quickly enough, right?
Which is why those extra settings in Developer options might be important.
"Settings > Developer options > Mobile data always active = On
Always keep mobile data active even when Wi-Fi is active
(for fast network switching)"
That's one of my questions I'm asking of others in this group, where I saw
that most people don't even know about these settings in Developer options.
But for those who do know about them, what are _your_ settings set up as?
Every Android phone has Developer options, just like every Windows PC has
regedit. You just have to know the secret way to make it available, which
Andy Burns covered in another post so I won't belabor the issue here.
There is a ton of good stuff that Developer options enabled, where I'll
just show you a few illustrative screenshots for remote Android control.
<
https://i.postimg.cc/9M0Tqzm6/adb01.jpg> Wireless debugging option
<
https://i.postimg.cc/hPVtkTXK/adb02.jpg> Boot turns W/L debug off
<
https://i.postimg.cc/Dyy7rWYd/adb03.jpg> Activity requires permission
<
https://i.postimg.cc/wTfg06CK/adb04.jpg> WiFi Calling on/off Activity
<
https://i.postimg.cc/Gm4rfWR4/adb05.jpg> Some Activities fail to run
<
https://i.postimg.cc/3xz7Qtrn/adb06.jpg> Run Activity from Termux
<
https://i.postimg.cc/W3vvhtkZ/adb07.jpg> Activity = Bad Component Name
<
https://i.postimg.cc/9X1hQmF4/adb08.jpg> Starting Intent with -n
<
https://i.postimg.cc/zB5sqMsS/adb09.jpg> Same Intent different name
<
https://i.postimg.cc/rwb9Mrr8/adb10.jpg> WiFi settings overview
<
https://i.postimg.cc/xTqWjL47/adb11.jpg> WiFi control history
<
https://i.postimg.cc/R0x8TyZ5/adb12.jpg> Using an Activity Inspector
<
https://i.postimg.cc/7hhQ6ym7/adb13.jpg> Adb using -a for wifi Intents
<
https://i.postimg.cc/sxn4F1WS/adb14.jpg> Wi-Fi Calling Activity
<
https://i.postimg.cc/ZK9B82gP/adb15.jpg> adb pair [IP][Port] [code]
<
https://i.postimg.cc/SRRXtvKh/adb16.jpg> Android 12 Wireless Pairing
<
https://i.postimg.cc/CLWZmJT3/adb17.jpg> Allow wireless debugging
<
https://i.postimg.cc/rmBHmvtV/adb18.jpg> Windows adb vysor & scrcpy
<
https://i.postimg.cc/CLyK8z9v/adb20.jpg> Both vysor & scrcpy use adb
<
https://i.postimg.cc/qRhkhTwV/adb21.jpg> Android Wireless-debugging tile
<
https://i.postimg.cc/zfLp8b2v/adb22.jpg> Windows Ctrl-Z,bg workaround
<
https://i.postimg.cc/85FwbwfX/adb23.jpg> USB needed before Android 11
<
https://i.postimg.cc/SRBWNrJ3/adb24.jpg> Android 12 needs no USB
<
https://i.postimg.cc/6p90PBGv/adb25.jpg> C:\> set ANDROID_ADB_SERVER_PORT
<
https://i.postimg.cc/YjBWwCPw/adb26.jpg> setprop service.adb.tcp.port #
<
https://i.postimg.cc/L4bDbk6z/adb27.jpg> scrcpy --tcpip=[IP]:[PORT]
<
https://i.postimg.cc/zDCTY9NS/adb28.jpg> multiple adb connections
<
https://i.postimg.cc/R0BXTMCy/adb29.jpg> multiple pairing connections
<
https://i.postimg.cc/DZV4tcYM/adb30.jpg> Windows pairing debuggers
<
https://i.postimg.cc/436FCYFX/adb31.jpg> Local adb runs on Android
<
https://i.postimg.cc/7YLhtcZL/adb32.jpg> ladb eliminates the PC
<
https://i.postimg.cc/9MSg3sjj/adb33.jpg> Long and short serial formats
> Alas! "Wi-fi safe mode / prioritize Wi-fi stability over
> performance" sounds like it might help, because I do get dropouts in
> Wifi calling. Switching to "Roaming network preference / Wifi
> preferred" a couple of weeks ago has seemed to help.
Ah. Good. I'm happy that you _looked_ at the images as I'm always wondering
if it's worth the effort to help others with images if they never look
(which is something you see a lot on the child-like Apple newsgroups).
I'm glad you _looked_ at those settings, not only because most people just
go with the defaults but also because this is a hidden Wi-Fi option
(well, it's not hidden so much as harder-to-find if you don't know how).
You and I are always trying to get better Wi-Fi and both of us can use that
"Wi-fi safe mode / prioritize Wi-fi stability over performance" option".
If you turn it on, and if you (or anyone) can find out more about what it
actually does, I would _love_ to hear back from you as I'm clueless.
I'm never afraid to admit when I'm ignorant - where all I did was set that
switch long ago - but I don't really know what it's actually doing.
In summary, I do NOT know what "Wi-Fi Safe Mode" really does nor do I know
why there are settings to "Allow 2G" but not "Allow 3G" or "Allow 4G/LTE".
Nor am I sure which collection of Wi-Fi settings makes Wi-Fi calling more
stable where the situation for most of us is probably similar in that
a. We're likely using Wi-Fi calling (connected to the router) at home
b. But we also have our cellular data probably turned on at the same time
c. And we often drive down our driveway while on a call initiated at home
I'm trying mostly to find the best Wi-Fi calling setup such that when I
drive down my driveway, I don't lose the call - because it should switch
over to the cellular data network when it loses the router Wi-Fi AP signal.
--
On Usenet, each time you faithfully try to help someone else, you learn.