Battery charge tests - running a battery to 0 frequently - checking re-charge times

I listed the manufacturer in the my posting. However, I didn't include the model number because it is not the latest:

I have a CBA-II. The current version is a CBA-V for $190. However, these are only good up to 200 watts. Higher power versions are available, but you won't like the price. There's also a problem with higher power batteries. The designers decided to save a few dollars and NOT provide a four terminal Kelvin bridge voltage sense system: The result is that any voltage drop in the cables between the discharge tester and the battery is substracted from the battery voltage. This creates accuracy problems at high power levels. I've been told that this was fixed in later units, but until I see a photo with 4 power wires (two heavy gauge, two smaller) I don't believe it.

Most of what I've done with the CBA-II was characterize LiIon 18650 cells, match cells, and test various small battery packs for 2way radios. Also, I did some rapid charge tests on NiCd and NiMH cells. The dicharge tester doesn't have a battery charger feature, but was useful for determining if my rapid charge method was decreasing capacity and/or cycle life.

Some more random test results. The NiMH tests were to demonstrate that a brand new NiMH cell will need to be charge cycled before it can attain a full rated charge.

I have more test results, but can't seem to find them.

You'll probably find a better review in the various flashlight forums:

Today I wrote a tutorial which shows an _easy_ way to install even hundreds of apps from Windows to Android over Wi-Fi using the command line.

Tutorial: *Working examples using Android/Windows adb over Wi-Fi* The documentation below is designed to be as cut-&-paste as possible.

This tutorial assumes you already installed adb & enabled USB debugging.

Note this was tested WITHOUT the Android SDK; it just needs "adb.exe".

Android 11 and up allows adb connections purely over Wi-Fi (with no initial or continued need for USB cables) which allows mirroring over Wi-Fi using any of a variety of free & FOSS tools such as: a. Vysor b. Scrcpy c. Microsoft Phone Link plus Microsoft/Samsung Link to Windows

Those local/remote mirror tools are described in gory detail here: *What free software do you use to locally mirror Android over Windows*

*What free software do you use to remotely control Android over Windows*

While screen mirroring is fantastic, what this tutorial focuses on is using the Android Debug Bridge (adb) commands over Wi-Fi from Windows.

Prior to Android 11, if the user wished to use adb with Android over Wi-Fi, the adb connection had to be initially _established_ over a USB cable.

There is much information about that problem set, only summarized below.

1. C:\> adb kill-server (optional, but it helps for a starting point)
2. Connect the Android phone to USB (mandatory on Android 10 & below).
3. Connect to the Android phone over USB. C:\> adb connect Or C:\> adb reconnect You should see an output of something like: * daemon not running; starting now at tcp:5037 * daemon started successfully reconnecting ABCDEFGHIJK [device]
4. C:\> adb tcpip 5555 You want one of these two show up: restarting in TCP mode port: 5555 Or... * daemon not running; starting now at tcp:5037 * daemon started successfully restarting in TCP mode port: 5555 Not this: * daemon not running; starting now at tcp:5037 * daemon started successfully error: no devices/emulators found But you might get this if you started from scratch * daemon not running; starting now at tcp:5037 * daemon started successfully error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device. If you do, just press "Allow" & "Remember" on the phone when it asks.
5. At this point you can disconnect the USB cable (or leave it connected).
6. To connect over Wi-Fi, this always works at this stage in the process. C:\> adb connect 192.168.0.2 Or, if you're a stickler for details, specifying the port works too. C:\> adb connect 192.168.0.2:5555 In either case, you want to see this: connected to 192.168.0.2:5555
7. At this point you are completely connected: C:\> adb devices That should output either this (if you left the USB connected). List of devices attached ABCDEFGHIJ device 192.168.0.2:5555 device Or this (if you disconnected the USB already). List of devices attached 192.168.0.2:5555 device

However, as of Android 11 and up, it's now possible to pair your Android phone to your over Wi-Fi Windows computer without ever needing a USB cable.

That instantly negates the need for the workaround above, detailed below. *Android Studio wireless ADB error (10061)*

That 5-year old wireless/usb workaround was updated on Oct 4, 2021.

Here's a description of the new adb Wi-Fi capabilities in Android 11+

"If you're on Android 11 (with SDK platform tool version 30 or greater) and above, you can use wireless debugging to pair your device with the computer. This Wi-Fi pairing method uses a new adb command called 'pair' which works similar to how Bluetooth pairing works."

The _new_ command sequence to pair Windows adb to Android over Wi-Fi is: A. Optionally, start at a known default starting point on Windows. C:\> adb kill-server B. Optionally, start at a known default starting point on Android. Settings > Developer options > Revoke USB debugging authorizations C. Make sure these Android 11+ settings are turned on. Settings > Developer options > USB debugging = On Settings > Developer options > Wireless debugging = On Optionally: Settings > Developer options > Disable adb authorization timeout = On

Then, to connect Windows adb to your Android 11+ phone over Wi-Fi:

1. Long press on Android "Developer options > Wireless debugging" settings.

1. Press the "Pair device with pairing code" option item. This will report something like the following information: Pair with device: Wi-Fi six-digit pairing code: 123456 IP address & Port: 192.168.0.2:54321
2. C:\> adb pair 192.168.0.2:54321 123456 You should see something like this on the phone: Successfully paired to 192.168.0.2:54321 [guid=adb-{serial number}]
3. C:\> adb connect 192.168.0.2:54321

Now you can issue adb commands from Windows over Wi-Fi to an Android phone. C:\> adb devices That should report the devices that adb is connected to, for example: List of devices attached 192.168.0.2:54321 device

C:\> adb shell netstat That should list the phone's TCP/IP connectivity tables.

C:\> adb shell service list That should list all the running services on the phone.

C:\> adb shell ps That should list all the running processes on the phone.

C:\> adb shell ifconfig That should provide your Android network interface information.

C:\> adb shell "cd /sdcard/Download && ls" That should list files in your internal storage Download folder.

C:\> adb shell "cd /sdcard && mkdir temp" That should create a "temp" directory in your internal storage sdcard on your Android phone.

C:\> adb shell screencap -p /sdcard/temp/screenshot.png That should snap a screenshot of your android phone & store it in the newly created temp folder on the Android phone.

C:\> adb shell screenrecord /sdcard/temp/screenrecord.mp4 Do whatever on the Android phone & then press Ctrl+C to end. That should create an MP4 recording of your Android screen.

C:\> adb install "C:\path-to\filename.apk" That should install the APK from Windows over Wi-Fi onto Android. (Note this is useful when you have hundreds of apps like I do!)

Windows APK archive

C:\> adb push "C:\path-to\filename.apk" /sdcard/Download That should copy the named file from Windows to Android & (in this case) put it in your internal storage "Download" folder.

Note that each phone OEM "can" use a different filespec for internal & external sdcards (e.g., /storage/emulated/0/Download).

C:\> adb push C:\path\apk_archive\ /sdcard/Download/apks That should create a folder named "apks" in the Android phone's internal storage "Download" folder and then copy all the files from the Windows "apk_archive" folder into that new "apks" folder.

C:\> adb shell $ /storage/emulated/0/DCIM $ ls $ exit That should allow you to interactively manage the Android filesystem from Windows over Wi-Fi. Note these are common: /mnt/sdcard/DCIM /sdcard0/DCIM etc.

C:\> adb logcat Use this if you're a glutton for punishment as it will forever spit out a log of what's going on your phone (until you Ctrl+C).

C:\> adb logcat *:E The values are: V: Verbose (lowest priority) D: Debug I: Info W: Warning E: Error F: Fatal S: Silent (highest priority. Nothing is printed) Note logcat has multiple options, e.g., adb logcat Tag1:I *:S That will list output log messages with the tag "Tag1" and priority level Info or higher. The *:S at the end will exclude the log from other tags with any priority.

C:\> adb shell getprop | FindStr /i "ro.build.version" Get properties off the phone & grep for the given keyword.

C:\> adb shell getprop ro.build.version.security_patch This will report the property of the security patch level.

C:\> adb shell getprop ro.build.fingerprint This will report basic hardware information about your phone.

C:\> adb shell input swipe 500 1000 500 100 This will instantly swipe from center to the top of the screen.

You can add a time period, e.g., take 3 seconds to swipe that. C:\> adb shell input swipe 500 1000 500 100 3000

C:\> adb shell input text "K-9\ Mail" This will enter into the phone's search GUI a search for that app.

C:\> adb shell pm list packages That should list all the packages installed on your Android phone.

C:\> adb shell pm list packages | findStr /i "facebook" That should list all the packages with that string in their name.

C:\> adb shell pm path com.facebook.appmanager That should list the path to the named package, e.g., package:/system/app/FBAppManager_NS/FBAppManager_NS.apk

C:\> adb pull /system/app/FBAppManager_NS/FBAppManager_NS.apk That should copy the APK from Android over to Windows.

C:\> adb shell dumpsys package com.facebook.appmanager This should list an app's components, activities & services, etc.

C:\> adb shell pm list permissions | FindStr facebook This should list all permissions granted for that particular app. C:\> adb shell pm revoke com.facebook.appmanager android.permission.READ_EXTERNAL_STORAGE This should revoke the stated permissions from that app.

C:\> adb shell pm grant com.facebook.appmanager android.permission.READ_EXTERNAL_STORAGE This should grant the stated permissions to that app.

C:\> adb shell pm clear com.facebook.appmanager This should clear all the application data in that package.

C:\> adb shell pm uninstall -k --user 0 com.facebook.appmanager That should uninstall the named package for the current user. (You don't need root to uninstall system apps for the current user.)

Note this app will provide, by default, a list of all apps you've installed, in the reverse order that you installed them. *App Inspector* by UBQSoft Free, ad free, gsf free, rated 4.3, 100K+ installs

C:\> adb shell pm install-existing com.facebook.appmanager That should re-install that package that you had just uninstalled. (This works because it was only uninstalled for the current user.)

C:\> adb shell pm disable-user --user 0 com.facebook.appmanager That should disable the named package.

C:\> adb shell pm list packages -d | findStr /i "facebook" That should find the disabled apps & then grep for "facebook".

C:\> adb shell pm enable com.facebook.appmanager That should enable the named package.

C:\> adb shell pm uninstall com.facebook.appmanager If you omit the "-k --user 0" part, it uninstalls for all users.

C:\> adb bugreport That should create a zip file of your current bug-report data.

C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity That should pop up an Android "Reset Advertising ID" settings page.

C:\> adb shell input tap 500 400 If run after the command above, that will tap the button to asking to "Opt out of Ads Personalization" in that Activity if that button is like mine, at the X=500 & Y=400 location.

On my phone, this is the "Reset advertising ID" button location: adb shell input tap 500 200 On my phone, this is the "OK" button on that GUI above. adb shell input tap 700 1000

C:\> adb shell am force-stop com.google.android.gms If run after bringing up the advertising-id reset Activity, it will close the activity without doing anything else.

C:\> adb shell input keyevent KEYCODE_HOME That should press the "Home" button. C:\> adb shell input keyevent KEYCODE_CAMERA That should press the "Camera" button. C:\> adb shell input keyevent KEYCODE_BACK That should press the "Back" button. C:\> adb shell input keyevent KEYCODE_HEADSETHOOK That should press the "Headset" button. A list of hardcoded buttons is located in Android documentation:

C:\> adb pull /system/etc/hosts .\hosts.txt [That should copy the hosts file over even if you're unrooted.]

C:\> adb shell dumpsys battery set level 4 That will _simulate_ (aka "spoof") a 4% battery level, which may instantly cause a cascade of actions on your phone as "if" your battery level really were low.

C:\> adb shell dumpsys battery set ac 1 That will _simulate_ (aka "spoof") that you just connected an AC power adapter to your phone, so, for example, the phone should show an icon and speak that you connected to AC power if you've set this app to do that for you. *Charging Indicator* by Jason A. Maderski Free, ad free, gsf free, rated 4.2, 50K+ installs

Note that with adding notifications, I use text-to-speech to clarify what the notification is telling me, instead of sounds.

Two text-to-speech free apps I use for notifications are: *Tell Me - Text To Speech* by Simply Complex Apps Free, ad free, +inapp $, rated 4.1, 100K+ installs

*NTM* Convert Text To Audio File by MEPROWORLD Free, ad free, not rated, 10K+ installs

In the case of the battery indicators, I set notifications such as: "Your battery just reached 100% charging" "Your USB cable just disconnected" etc.

C:\> adb shell dumpsys battery reset This will turn off the battery-level simulation (aka spoofing).

C:\> adb shell dumpsys battery set ac 0 That will _simulate_ (aka "spoof") that you just dis-connected an AC power adapter from your phone.

C:\> adb shell dumpsys battery set usb 1 That will _simulate_ (aka "spoof") that you just connected a USB cable to your phone. . C:\> adb shell dumpsys battery set usb 0 That will _simulate_ (aka "spoof") that you just dis-connected a USB cable to your phone.

C:\> adb shell pm list packages That should list all installed packages. C:\> adb shell pm list packages -s (list system packages only) C:\> adb shell pm list packages -3 (list 3rd-party package names) C:\> adb shell pm list packages -u (list uninstalled packages) C:\> adb shell dumpsys package packages (list package information) C:\> adb shell pm dump com.facebook.appmanager (info on one package) C:\> adb shell pm path com.facebook.appmanager (package apk filespec)

C:\> adb shell pm list packages google | find /c /v "" That should tell you the number of packages you have on Android which have "google" in the package name.

C:\> adb shell am start -n com.android.settings/.Settings\$PowerUsageSummaryActivity That should bring up a moving graph of your current battery usage.

C:\> adb shell am start -n com.google.android.gms/.location.settings.LocationAccuracyActivity That should tell you if you have Google location spyware running.

C:\> adb shell am start -n com.google.android.gms/co.g.Space That should allow you to clear your Google Play services storage.

C:\> adb shell am start -n com.google.android.gms/.update.SystemUpdateActivity That should allow you to check for Android updates. C:\> adb shell am start -n com.google.android.gms/.nearby.exposurenotification.settings.SettingsActivity That will let you know your Covid exposure notification status.

C:\> adb shell am start -n com.google.android.gms/.app.settings.GoogleSettingsLink That should bring up most of the Google privacy settings on Android.

C:\> adb shell am start -n com.android.settings/.Settings\$NotificationAppListActivity That should bring up _all_ your extant notifications.

C:\> adb shell am start -n com.android.settings/.Settings\$AppMemoryUsageActivity That should show you how much memory each app is using.

C:\> adb shell am start -n com.android.settings/.network.telephony.MobileNetworkActivity That should tell you how much mobile data you've used up.

C:\> adb shell am start -n com.android.settings/.applications.ManageApplications That should bring up the form to set your default Android apps.

C:\> adb shell am start -n com.google.android.gms/.gcm.GcmDiagnostics That should scare the crap out of you when you see what it says! mtalk.google.com is obtaining your private location information?

C:\> adb backup -all Supposedly this will back up your entire device & app data to an encrypted "backup.adb" file in your current Windows directory.

C:\> adb restore "C:\path-to\backup.adb" Supposedly this will restore your backed up device & app data.

Please note that I tested the commands above so that cut-&-paste works. Note, of course, that many (but not all!) of those commands can likely be found on the net scattered about (however, some don't exist to my knowledge on the net though, as they were found by trial and error).

However _basic_ information on adb commands abound on the net, e.g., *Android Debug Bridge (adb) cheat sheet*

In addition, below are untested possibilities... for future tutorials.

Note the debilitating problem that, while you can install an SMB _server_ on non-rooted Android, it's impossible (so far) to use an SMB _client_ on non-rooted Android to connect to a typical Windows SMB share over Wi-Fi.

Non-rooted Android SMB client apps can't connect to Windows SMB shares simply because Windows SMB requires port 445 but non-root Android SMB clients, much to my chagrin, can't ever access ports lower than 1024.

However, an enterprising experimenter "may" be able to work around this intractable problem perhaps by the use of "port forwarding"? C:\> adb forward tcp:local_port tcp:device_port C:\> adb reverse tcp:device_port tcp:local_port

And be advised that adb can temporarily elevate permissions for a user where this example below is run completely on the Android device itself. Termux % adb pair localhost:54321 <add the 6-digit wi-fi pairing code>

Termux % adb connect localhost:54321 Termux % adb shell Termux # run-as com.termux Termux $ {permissions are now elevated while inside this prompt}

It has been said you can run privileged commands, like look at the default protected contacts sqlite database on Android phones.

Termux $ adb -s emulator-5554 shell Termux $ sqlite3 /data/data/com.android.providers.contacts/databases/contacts2.db SQLite version 3.3.12 Enter ".help" for instructions sqlite> select * from data; sqlite> delete from data; sqlite> delete from contacts; sqlite> delete from raw_contacts;

If you have additional useful adb commands, please share so we all learn.

I found the docs to the load tester the my mechanic uses. It's a Sun VAT-40:

Besides the battery, it also tests the alternator, starter, regulator, gauges, and parts of the electrical system. The battery load is an adjustable carbon pile.

Yep. That's what the more modern shop use. An active load is much better than a carbon pile.

I don't have much experience with automotive ESR testers. The few times I tried one, I found that a discharge curve test was much better.

<snip>

Testing the resistance and conductance can tell you if the battery is bad. But that can't tell you what the reserve capacity is.

that's the point.

some do, however, it's a parameter that is not particularly important for cars. it's also not something that's measured by carbon pile load testers.

For the record, for anyone attempting to reset the Android Advertising ID from Windows, Android 11 and below would reset the id to a GUID, or globally unique ID, (similar to what Windows 95 CoCreateGUID created, according to Mayayana's kind advice on the Android newsgroup today).\

Doubletap to Reset AD ID Set doubletap to any Activity Calling an Intent with a URI Calling an Intent with a GUI

However, notice in Android 12 the GUID at times is set to all zeroes.

Check Advertising ID

We surmised that's because there are two new commands in Android Settings > {Privacy,Google} > Ads > Reset advertising ID Settings > {Privacy,Google} > Ads > Delete advertising ID <== new! Settings > {Privacy,Google} > Ads > Get new advertising ID <== new!

Delete Advertising ID

Apparently "delete" isn't so much a delete as a "zero out" such that the GUID is of the form (8-4-4-4-12) of 00000000-0000-0000-0000-000000000000.

This program is the only known program in all of Google Play that is known to report that Advertising ID outside of the Android Settings GUI. *Device Identifiers* by Umang Chamaria Free, ad free, Google free, GSF free, rated 3.8, 5K+ installs

But it's a crappy program otherwise as that's its only real job (still, it's the _only_ one anyone knows about that does that).

These are better for reporting most of the identification IDs on Android. *DevCheck Hardware and System Info* by flar2 Free + inapp, ad free, Google free, gsf free, rated 4.8, 1M+ installs

*Device ID* by Evozi Free, ad free, Google free, GSF free, rated 4.5, 1M+ installs *Inware* by evowizz Free, ad free, Google free, gsf free, rated 4.4, 100K+ installs *Device Info HW* by Andrey Efremov Free, ad free, Google free, gsf free, rated 4.7, 1M+ installs *Device ID* by BINHDRM26 Free, ad free, Google free, gsf free, unrated, 10K+ installs *Device Identifiers* by Umang Chamaria (this gets the advertising ID) Free, ad free, Google free, GSF free, rated 3.8, 5K+ installs

Unfortunately, I haven't found one app which gives you everything you need.

If you can find an app that does all that we need, that would be great, as it would be nice, for example, to have all the critical versions spit out by a single app. Android Security Patch Level version Google Play Services version Google Play Store version Google Play System update version Android Device ID Google Services Framework ID Google Advertising ID Java VM Android Runtime version Media DRM Widevine CDM Device Unique ID Hardware Serial Number Device Build Fingerprint etc.

Has anyone here used WebDav to mount Android onto Windows as a drive over Wi-Fi? If so, can _you_ see your Android external sdcard from Windows over Wi-Fi?

I can't. I can see _everything_ else (including the root filesystem!) but not the sd card. (Note I'm not rooted but that shouldn't matter to see the sd card, should it?)

I attempted these permission-addition commands because the Windows Wi-Fi mount of the Android file system as a drive doesn't access the external sdcard yet. C:\> net use Z: \\192.168.0.2@8080\DavWWWRoot

I also tried adding a login/password of (foo/bar) but that didn't matter. C:\> net use Z: \\192.168.0.2@8080\DavWWWRoot /USER:foo bar

And I tried specifying the root directory: C:\> net use Z: \\192.168.0.2@8080\storage\emulated\0 /USER:foo bar C:\> net use Z: \\192.168.0.2@8080\storage\0000-0001 /USER:foo bar

At least not when using this free WebDav server on Android to mount Android as a drive letter onto Windows over Wi-Fi using that Windows "net use" command. *WebDAV Server* by The Olive Tree

The problem I'm having with Android 12 connecting to Windows is that I can set the WebDav server root to anything I want to in the WebDav server GUI:

Mount Android over Wi-Fi

But from Windows I can see everything on Android (including the root file system) except what is on the external sdcard (even though, on Android, I can easily see what's on the external sdcard).

Using this adb tutorial to check if permissions are the problem, I run: C:\> adb shell pm list packages | findstr "webdav" package:com.zq.webdav.app_free <== this is ad free but more complex package:com.theolivetree.webdavserver <== this is the one I'm using To list its permissions I can run this but it didn't find any permissions. C:\> adb shell pm list permissions | FindStr "com.theolivetree.webdavserver"

This "might" grant it permission to read external storage: C:\> adb shell pm grant com.theolivetree.webdavserver android.permission.READ_EXTERNAL_STORAGE

But, unfortunately, even though I can see the Android root file system from Windows (with Android being a drive letter), I can't see the external sdcard for some reason.

What's odd is I can see literally everything _except_ the external sdcard from Windows with Android mounted as a drive letter over Wi-Fi.

Has anyone here used WebDav to mount Android onto Windows as a drive over Wi-Fi? If so, can _you_ see your Android external sdcard from Windows over Wi-Fi?

In summary, the situation is thus for mounting Android to Windows over Wi-Fi: a. I'm not rooted (and yet I can see the root file system) as a drive letter. b. The WebDav server _says_ it will mount Android over Wi-Fi as a drive letter. c. But _only_ the external sdcard will not show up in that Windows mount.

Why? What's the solution?

Big Al wrote:

SOLVED!

Thank you for that purposefully helpful kind & astute suggestion!

Both sdcards mounted

Following up on your excellent advice, I mounted the entire internal sdcard over Wi-Fi as Windows drive letter Y: using one Android webdav server set up to use port 8080...

While simultaneously mounting the external sdcard over Wi-Fi as Windows drive letter Z: using another Android webdav server over port 8081...

A USB cable is fine, and, in fact, works great for file transfer. but it doesn't act like a Windows drive letter, nor an Android mirror.

a. This mounts the internal sdcard as a drive over wifi on Windows: C:\> net use Z: \\192.168.0.2@8080\DavWWWRoot /user:foobar snafu

b. This mounts the external sdcard as a drive over wifi on Windows: C:\> net use Z: \\192.168.0.2@8081\DavWWWRoot /user:foobar snafu

c. This pairs Android to Windows over wifi for mirroring & control: C:\> adb pair 192.168.0.2:54321 123456

Here is the result, where I don't know if it gets any better than this!

Both sdcards mounted

Again you bring up a GREAT question, of whether a WebDav server is the same thing or if it's completely different from an HTTP server.

I don't know. Does anyone here know how a WebDAV server differs from a plain old HTTP server? Are they one and the same?

If they're the same thing, all you need to do to make your Android phone (or iOS phone for that matter) a drive letter over Wi-Fi is run those "NET USE" commands listed above.

What I see is the entire Android phone from Windows over Wi-Fi, at least as far as I know, but I only have write permission to the sections of the phone that you'd expect to write to.

As far as I know, you can't get much more power than I have now.

Thanks. I hope others benefit from the knowledge and I very much appreciate that you helped me solve the problem of _simultaneous_ access to both the internal and external sdcard, thanks to you!

Here are some of the screenshots for those interested in this power! (They're in reverse order as that's where the success is in the end!)

WebDav:

Both sdcards mounted Permissions are the same My Files has permission File Manager has permission X-plore has no permission WebDav has no sd permission

Vysor:

Removing Apple iTunes crap Nuking Apple shitware 1 by 1 The bloatware is everywhere iTunes crapware won't install Best iOS drivers installed Apple Device working properly iPad is connected to Win10 Apple Win10 iOS drivers suck Apple iPad on Win10 over USB Classic Apple error 2502 Classic Apple error 2503 Apple Mobile Device Support Install Apple AMDS engine Classic Apple Error Code 2503 Apple Mobile Device Support Connect over the Internet Vysor Camera virtual webcam Vysor easily finds Android Vysor searches for Android/iOS Vysor Windows Virtual Camera Classic Apple Error code 2503 Apple Mobile Device Support iOS requires Apple AMDS kluge Remote mirror over the net Vysor Internet mirroring Vysor ADB USB setup switches Vysor remote sharing Vysor console operation Vysor Android/iOS PC mirroring

Note: Android always works whereas iOS always sucks by way of comparison.

Scrcpy:

Android SMS/MMS on Windows Vysor IP address option Windows Drive: === Android Start /b as a CMD works! :) Start /b TARGET fails :( Free Automation APKs AutoIT & IFFT & Automate powershell hide-console trick Trick to pin batch shortcut AppPath & shortcut TARGET No scrcpy console window! REG test of showwin.lnk Shortcut test of showwin.lnk The console came up :( REG test of showwin.bat CMD test of showwin.bat Android mnt as drive letter Press two hardware buttons Drag APK from Windows Extraneous cmd window (&) The efficient setup explained An efficient program setup Mirror Android on any PC

Can interfacing a smartphone to Windows get any better than this?

Today I solved _all_ the problems I had run into, thanks to the advice from other helpful intelligent people such as Andy Burns, Herbert Kleebauer, Big Al, et. al, all of whom are who make Usenet a valuable adult conversation where ideas are exchanged so we all benefit from the result.

1. Over Wi-fi
2. Using only widely available free tools
3. I can now easily mount the _entire_ Android device
4. both the internal sdcard (including the root partitions!)
5. and the external sdcard, simultaneously,
6. each as their own Windows drive letter
7. while at the same time being able to mirror the Android phone
8. and control the Android phone using the mouse & keyboard
9. while simultaneously sharing the two clipboards between them
10. And being able to slide files back and forth at will

My question to the group at large simply is whether there is anything else that we could possibly want in terms of complete Android/Windows sharing?

Note all of this is done a. WITHOUT any login to anything! b. WITHOUT any connection to the Internet! c. WITHOUT paying a penny for tools

Does it get any better than that?

WebDav:

Both sdcards mounted Permissions are the same My Files has permission File Manager has permission X-plore has no permission WebDav has no sd permission

Vysor:

Removing Apple iTunes crap Nuking Apple shitware 1 by 1 The bloatware is everywhere iTunes crapware won't install Best iOS drivers installed Apple Device working properly iPad is connected to Win10 Apple Win10 iOS drivers suck Apple iPad on Win10 over USB Classic Apple error 2502 Classic Apple error 2503 Apple Mobile Device Support Install Apple AMDS engine Classic Apple Error Code 2503 Apple Mobile Device Support Connect over the Internet Vysor Camera virtual webcam Vysor easily finds Android Vysor searches for Android/iOS Vysor Windows Virtual Camera Classic Apple Error code 2503 Apple Mobile Device Support iOS requires Apple AMDS kluge Remote mirror over the net Vysor Internet mirroring Vysor ADB USB setup switches Vysor remote sharing Vysor console operation Vysor Android/iOS PC mirroring

Scrcpy:

Android SMS/MMS on Windows Vysor IP address option Windows Drive: === Android Start /b as a CMD works! :) Start /b TARGET fails :( Free Automation APKs AutoIT & IFFT & Automate powershell hide-console trick Trick to pin batch shortcut AppPath & shortcut TARGET No scrcpy console window! REG test of showwin.lnk Shortcut test of showwin.lnk The console came up :( REG test of showwin.bat CMD test of showwin.bat Android mnt as drive letter Press two hardware buttons Drag APK from Windows Extraneous cmd window (&) The efficient setup explained An efficient program setup Mirror Android on any PC

133 posts, so far, for no discernably new, useful or effective information other than uninspired navel gazing. Not quite a record given all this originated with Jimmy Neutron.

The lesson remains: Please do not feed the trolls.

Peter Wieck Melrose Park, PA