Get it via Google Play Store.

 [:]

Main changes:

• Video and Audio stream support
• Several bugfixes
• Alternative video renderer option
• Layout optimization
• Notifications

Get it![:]

If you use Windows roaming user profiles with folder redirection (which should be the default setting in a company), huge folders like .gradle or .AndroidStudio2.2 are always copied between server and local disk on Windows logon or logoff. You might have to wait 15 – 20 minutes to get your Windows profile fully loaded.

Meanwhile, at least some of the folders went to better locations. E.g. the Android SDK is now under %LOCALAPPDATA% (c:\users\me\appdata\local), which means it will be ignored by the user profile service and not be copied. If you explicitely want it to be copied, move it e.g. to your %APPDATA% folder (could be \\server\profiles\me\appdata). In your project settings file “local.properties” you can modify the SDK directory.

Unfortunately, two huge folders still reside in under %USERPROFILE% by default: .gradle and .AndroidStudioX.X

I recommend to also move these folders to %LOCALAPPDATA%. Then recreate a junction point (mklink) for them:

move %USERPROFILE%\.gradle %LOCALAPPDATA%
move %USERPROFILE%\.AndroidStudio3.4 %LOCALAPPDATA%
move %USERPROFILE%\.android %LOCALAPPDATA%

mklink /j %USERPROFILE%\.gradle %LOCALAPPDATA%\.gradle
mklink /j %USERPROFILE%\.AndroidStudio3.4 %LOCALAPPDATA%\.AndroidStudio3.4
mklink /j %USERPROFILE%\.android %LOCALAPPDATA%\.android

So your huge directories are moved to a non-synced place and Android Studio can still find it in the default location.[:]

Use DHCP reservation feature of your server and maybe give it a DNS A hostname so you are able to access (at least ping) your mobile phone via a constant name/IP in your local network.

But starting with CM12 and Android 5.x, your phone gets a new MAC address or DHCP ID on every reboot, or even every time you reconnect to your WLAN.

A MAC address is definitely not wanted to be changed ever. So this results e.g. in many useless IP lease entries in your DHCP server, and your mapped DNS names may not work any more.

Cyanogenmod developers seem to ignore this problem as seen on these threads:

https://jira.cyanogenmod.org/browse/NIGHTLIES-729

https://jira.cyanogenmod.org/browse/NIGHTLIES-786

The first thread is closed because of “too old” with the suggestion of creating a new thread, the second one is closed because of “duplicate” – which is quite contradictory.

For me the only workaround at this moment was to set a static IP address for the WLAN connection on my phone.

You are using an IP intercom like 2N Helios IP or a Mobotix product.

You have an electronic door lock like G-U Secury Automatic which is connected to any home automation system like KNX, and you use a server system like Gira Homeserver, Loxone Miniserver, Wiregate or a custom EIBd system.

So you might be looking for an app for your mobile phone (or maybe in-wall tablet) to use it as a doorbell, camery display and remote door lock control.

Some Android apps already exist from the hardware manufacturers, e.g. 2N Helios IP Mobile. But they are quite expensive and error-prone. E.g. it does not work over VPN, does not save the chosen intercom and seems to be buggy when using WLAN connection.

Solution

Because I could not find an existing app which works stable and covers all these features, I wrote one.

You can download it for free via Android Play Store: DXSdata IP Intercom Doorbell

With this app, you can:

• Display any camera image from an HTTP source, e.g. 2N Helios: http://[intercom-ip]/enu/camera640x480.jpg
• Push an app button to open the door (e.g. your KNX server gets the HTTP command and closes a relay which opens the lock)
• Get a popup on your phone or tablet if someone is at your door and pushes the doorbell button (e.g. call your mobile phone’s local IP or DNS name like “http://[your-ip]:8787/?action=bringDoorbellAppToFrontAndRing”)
• Some Android devices which have Ethernet ports (e.g. HP Slate 21 Pro) do not have an option to keep the LAN connection awake. This can be a problem because your doorbell cannot find the device in the network, e.g. to bring the app to front if someone is at the door. So there is an option in the IP Intercom Doorbell app to keep LAN alive.

Physical Android devices can be used for debugging with Android Studio easily, if they are included in the Google USB driver. The HP Slate 21 (and Pro) is not, but it can be added.

Solution

Download Google USB driver.

Unzip the file and open android_winusb.inf e.g. with Windows Notepad.

Add the lines below to the sections [Google.NTx86] and [Google.NTamd64]:

;slate21

%SingleAdbInterface%        = USB_Install, USB\VID_0955&PID_7100

%CompositeAdbInterface%     = USB_Install, USB\VID_0955&PID_7100&MI_01

Install the driver via Device Manager (manually).

If you are using Windows 7 or 8 upwards, you might have to disable driver signature verification.

Source