Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Same here. Without thist, my mountscripts won't work. Is there a way to add the Android Device in the Whitelist?
[Deleted User] <[Deleted User]>
Yes, any mount script is broken because it must execute the mount command under "adb shell"
Android 4.2 made mounting miserable due to he multiuser changes
Android 4.2.2 makes it 4x more miserable...
Android 4.2 made mounting miserable due to he multiuser changes
Android 4.2.2 makes it 4x more miserable...
yb...@google.com
Yes, the problem is real. Is there any alternate method? I really miss my server's shares.
as...@gmail.com
This is a very unfortunate regression. I find myself constantly reaching for my Galaxy Note 1 over my Nexus 10 now because I can mount my cifs shares on it (4.1.2). Please restore the abd loopback functionality or better yet implement a mount point where shares public to all installed android apps can be mounted.
ch...@gmail.com
This is a retrograde step. Localhost connections to adb should not pose any external security threat and should not be subject to RSA security. Is it possible to generate an RSA key for localhost ? and if one existed would a localhost connection to adb then be allowd ?
ch...@gmail.com
After digging the (confusing) adb/adbd source code:
- adbd reads available keys in /data/misc/adb/adb_keys. These are base64 encoded string and I'm not sure at this point what they are
- the first time adb is executed on device, it will generate a private key and public key in /data/.android, named adbkey and adbkey.pub. This this the same than on a PC but not at the same location (uses $HOME/.android and on a device $HOME value is /data)
The device is offline due to adb <-> adbd authentification failing, I think because the entry corresponding to localhost is missing in /data/misc/adb/adb_keys.
adbd only reads /data/misc/adb/adb_keys. So the question is what process adds entries to it. My guess is that it is the activity displaying the "the computer's RSA key fingerprint is: <fingerprint>" popup that is displayed the first time an USB host connects.
So I think if the correct entry is added to adb_keys either manually or with a small standalone executable (needs root but since the purpose to fix this is to mount which also requires root, this is not a problem), it would work.
The other option is to recompile adbd so the gloabal variable auth_enabled is forced to 0 in adbd.c, to disable the auth negociation.
Btw a side effect of this issue is that if you want to do ADB through WiFi you must still authorize it first plugging an USB cable.
- adbd reads available keys in /data/misc/adb/adb_keys. These are base64 encoded string and I'm not sure at this point what they are
- the first time adb is executed on device, it will generate a private key and public key in /data/.android, named adbkey and adbkey.pub. This this the same than on a PC but not at the same location (uses $HOME/.android and on a device $HOME value is /data)
The device is offline due to adb <-> adbd authentification failing, I think because the entry corresponding to localhost is missing in /data/misc/adb/adb_keys.
adbd only reads /data/misc/adb/adb_keys. So the question is what process adds entries to it. My guess is that it is the activity displaying the "the computer's RSA key fingerprint is: <fingerprint>" popup that is displayed the first time an USB host connects.
So I think if the correct entry is added to adb_keys either manually or with a small standalone executable (needs root but since the purpose to fix this is to mount which also requires root, this is not a problem), it would work.
The other option is to recompile adbd so the gloabal variable auth_enabled is forced to 0 in adbd.c, to disable the auth negociation.
Btw a side effect of this issue is that if you want to do ADB through WiFi you must still authorize it first plugging an USB cable.
Description
– Display a scrollable list below translucent system bars.
– Content should underlap the system bars.
– The scroll indicator and overscroll edge effects should be inset to not underlap the system bars.
Approach:
– Use a TranslucentDecor theme.
– Use a RecyclerView with setClipToPadding(false) and setPadding(0, paddingTop, 0, paddingBottom).
Steps to reproduce:
1. Run the attached Android Studio project (see MainActivity.java for details).
2. Slowly scroll the content and observe the [de]materialization of views underlapping the status bar and navigation bar.
Expected: views do not disappear until they are no longer visible.
Actual: views disappear once they are fully within the padding of the RecyclerView.
Note:
This culling behavior looks fine if |clipToPadding| is true, however it seems that setting |clipToPadding| to false is the only way to elegantly underlap translucent system bars. Let me know if there is a better way!
Versions:
– Android L Emulator (google_sdk_x86-eng L LPV81B 1242878 test-keys)
– recyclerview-v7 (21.0.0-rc1)