Android ADB 7.4 plugin: Installation instructions??

[algol]

Really no comments by Android-experts on the apparent differences of handling the file transfer/access to the external SD-card between Lollipop 5.0.1 and 5.1.1? Did anyone notice the change in directory structure?

The "sdcard" subfolder of the root, where under 5.0.1 the entire internal data-storage of the phone could be found, now seems empty (or somehow "protected") whereas the internal data-storage now seems to be located under:

Code: Select all

\\\ADB\<device-ID >\storage\emulated\0\..

greetings
algol

[iana]

Well I'm still using kitkat although for it's age and price my phone is quite powerful x8 cores@ 1.7GHz, 2GiB of RAM and 16GiB of internal storage and all I can tell you is I don't really use this plugin any more, instead I use TC for android
http://www.ghisler.com/android.htm
https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander&hl=en
with the LAN plugin for Total Commander
https://play.google.com/store/apps/details?id=com.ghisler.tcplugins.LAN&hl=en

with it I have direct access to my PC from the android device, if your windows account does not have a password you'll need to add one or you can use the build in administrator account (which will also need a password)

[algol]

I don't really use this plugin any more, instead I use TC for android

Well, who doesn't? Use TC_Android, that is.

with it I have direct access to my PC from the android device

Having that said, the LAN plugin - in a manner of speaking - provides me with kind of "the wrong perspective" and has - at least from my point of view - a number of security-related disadvantages.

This starts with me having to turn on "administrative shares" on my Windows PC if I want to conveniently access my PC-data-drives - and not only some auxiliary-type common folder for copying. Definitely a measure not highly recommended by security experts.

Second, I need to turn WLAN on, a totally un-necessary security risk for the purpose of perhaps transferring my most confidential personal data when that can be easily done via trusted USB-cable while at the same time charging the phone as opposed to drawing power for the transfer.

But first & foremost, I'd certainly prefer to control my phone as the "little brother-companion" of my PC with a (comparatively) tiny 5.7"-screen and very limited data-comparison and multitasking capabilities from my primary workstation console with a large hi-res screen with all tools and a performance-mouse/keyboard interface at hand than having to fiddle it the other way round.

From that perspective any comments on changed behavior of data-transfer on modern Android systems via the ADB-interface/-plugin - or even a possibly necessary adaption thereof - would still be highly appreciated.

greetings
algol

[iana]

about android security you can always install a firewall and let only a few apps access your network, a good open source firewall is AFWall+
you can get it from F-Droid (the open source android repository)
https://f-droid.org/repository/browse/?fdid=dev.ukanth.ufirewall
or google play
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en

I have no experience with lollipop but on most androids the internal sd drive always has a hardlink in the root filesystem in
/sdcard
actually my kitkat has 3 hardlinks for the same internal memory in
/sdcard and
/mnt/sdcard and
/storage/sdcard0
so check those folders

[algol]

on most androids the internal sd drive always has a hardlink in the root filesystem in
/sdcard
actually my kitkat has 3 hardlinks for the same internal memory in
/sdcard and
/mnt/sdcard and
/storage/sdcard0
so check those folders

As already mentioned the "/sdcard" folder is still there and up until "5.0.1" 'was filled' with internal-memory-filesystem. Since "5.1.1"-update it is shown empty.

The internal content seems now only to be found at

"..\storage\emulated\0"

What consequences, if any, does this change bear?

greetings
algol

[ghisler(Author)]

/sdcard has been just a link to the real location for a long time. There is an Android function to get the real location, which usually returns /storage/emulated/0

[algol]

Hello Christian,

thanks for the comment. A little research has shown the internal memory content under Andr.5.1.1 (Samsung GNote4) listed under:

Code: Select all

[\\\ADB\**Dev_serial**\data\media\0\]
[\\\ADB\**Dev_serial**\mnt\shell\emulated\0\]
[\\\ADB\**Dev_serial**\storage\emulated\0\]

Would you mind telling us the Android function to inquire for the true location of the data and is it 100% irrelevant which way you choose to access them?

greetings
algol

[ghisler(Author)]

The function to use is:
Environment.getExternalStorageDirectory().getAbsolutePath();

This will usually return \storage\emulated\0\

The other paths MAY work too, but not offer all the user rights, e.g. for writing.