Unison / UnisonSync for Android - the file synchronisation tool - has been updated for latest Android!
Finally got around to recompile Unison and OpenSSH for the latest Android versions. You can find the binaries in the Unison app: https://play.google.com/store/apps/details?id=net.danielroggen.unison
That's a command line only app - so a bit cumbersome to use.
UnisonSync is a more convenient app to use Unison with a graphical interface:
https://play.google.com/store/apps/details?id=net.danielroggen.unisonsync
UnisonSync uses Unison as a client: you need your own server somewhere accessible over SSH which will run the server-side Unison counterpart.
This is allows you to use unison even if the Android device and your server are on different subnets, or even if your Android device is behind a firewall.
(The other Android Unison app on the play store makes your device acts as a server - which may or may not be what you need to access a device across networks or over GSM).
Related
Hey there!
So I switched my server from linux over to windows (hdmi audio driver issues with ion2, don't ask) and can no longer use Rsync to sync files (unless of course you know of a way to do this in windows)
I am looking for a tool that allows for LAN syncing of files on my Windows desktop to my android device. I know there are tons (box.net, Mozy, SugarSync, etc) that do this however they push files to the cloud. I do not want this. I want a simple LAN sync tool, any personal faves are welcomed!
Thanks in advance!
I'm using freeFTPd as my daemon on the windows box and andFTP as my client on the device. This is the closest I can get to rsync and I think it's the best possible solution right now.
I like rsync for android:
https://market.android.com/details?id=eu.kowalczuk.rsync4android&feature=search_result
It would require opensshd on your windows box. You can get that at:
http://sshwindows.sourceforge.net/
There's a thread on it here:
http://forum.xda-developers.com/showthread.php?t=871307&highlight=rsync
rsync over ssh does not require the rsync daemon, so you should be good to go there, though cygwin does provide rsync if you just had to have it on the windows side.
Also, linux to windows? eww.
On a non rooted Samsung Galaxy tab 2 7.0" I have the app GNUroot Debian installed. This is a chroot (actually it is called PRoot, see below for a description) Linux distribution - currently Debian 'Jessie' - with a terminal. I have installed the android-tools-adb package from the Debian Jessie repository. This means the chroot environment has access to the tablet's network hardware.
Now I would like to control another device (I have a non rooted Huawei Ascend Y300) from the tablet using adb inside the chroot terminal. I managed to do this through WiFi by first connecting the phone to a pc and run the terminal command 'adb tcpip 5555'. Then, on the tablet in the GNUroot Debian app terminal running the command 'adb connect xxx.xxx.x.x' gives adb control from the tablet over the phone through the local wifi network. Nice!
It would be even better to manage the adb control between two android devices from a chroot / PRoot environment without the pc, for example using an On The Go cable. Assuming non rooted devices. The tablet in question (Samsung Galaxy tab 2 7.0") has usb host capabilities. So in theory it could be done with a usb On The Go cable connecting the two Android devices.
Questions:
Is it possible to use adb within the described chroot / PRroot environment to run commands to controle another Android device, when both Android devices are connected through a USB On The Go cable?
Does a chroot / PRoot environment give access to the usb port as host?
Information:
The reason for this question is the development of an app on my tablet, using the Android IDE app, which must be tested on other (non rooted) Android devices. Preferably from the tablet, preferably without a pc.
Description of PRoot from 'proot-me' repository at github.com:
==
PRoot is a user-space implementation of ``chroot``, ``mount --bind``,
and ``binfmt_misc``. This means that users don't need any privileges
or setup to do things like using an arbitrary directory as the new
root filesystem, making files accessible somewhere else in the
filesystem hierarchy, or executing programs built for another CPU
architecture transparently through QEMU user-mode. Also, developers
can use PRoot as a generic Linux process instrumentation engine thanks
to its extension mechanism, see CARE_ for an example. Technically
PRoot relies on ``ptrace``, an unprivileged system-call available in
every Linux kernel.
The new root file-system, a.k.a *guest rootfs*, typically contains a
Linux distribution. By default PRoot confines the execution of
programs to the guest rootfs only, however users can use the built-in
*mount/bind* mechanism to access files and directories from the actual
root file-system, a.k.a *host rootfs*, just as if they were part of
the guest rootfs.
When the guest Linux distribution is made for a CPU architecture
incompatible with the host one, PRoot uses the CPU emulator QEMU
user-mode to execute transparently guest programs. It's a convenient
way to develop, to build, and to validate any guest Linux packages
seamlessly on users' computer, just as if they were in a *native*
guest environment. That way all of the cross-compilation issues are
avoided.
PRoot can also *mix* the execution of host programs and the execution
of guest programs emulated by QEMU user-mode. This is useful to use
host equivalents of programs that are missing from the guest rootfs
and to speed up build-time by using cross-compilation tools or
CPU-independent programs, like interpreters.
It is worth noting that the guest kernel is never involved, regardless
of whether QEMU user-mode is used or not. Technically, when guest
programs perform access to system resources, PRoot translates their
requests before sending them to the host kernel. This means that
guest programs can use host resources (devices, network, ...) just as
if they were "normal" host programs.
==
Unison / UnisonSync for Android - the file synchronisation tool - has been updated for latest Android!
Finally got around to recompile Unison and OpenSSH for the latest Android versions. You can find the binaries in the Unison app: https://play.google.com/store/apps/details?id=net.danielroggen.unison
That's a command line only app - so a bit cumbersome to use.
UnisonSync is a more convenient app to use Unison with a graphical interface:
https://play.google.com/store/apps/details?id=net.danielroggen.unisonsync
UnisonSync uses Unison as a client: you need your own server somewhere accessible over SSH which will run the server-side Unison counterpart.
This is allows you to use unison even if the Android device and your server are on different subnets, or even if your Android device is behind a firewall.
(The other Android Unison app on the play store makes your device acts as a server - which may or may not be what you need to access a device across networks or over GSM).
XDA:DevDB Information
UnisonSync, App for all devices (see above for details)
Contributors
droggen, droggen
Version Information
Status: Stable
Current Stable Version: 1.15
Stable Release Date: 2018-10-08
Created 2018-10-27
Last Updated 2018-10-27
NextCloudPi is a Nextcloud instance that is preinstalled and preconfigured, and includes a management interface with all the tools you need to self host your private data in a single package.
Import the 100MB image linked below into Linux Deploy and wait a few minutes for NextCloudPi to build from install.sh.
ncd12.tgz
Lightly-forked edition of NextCloudPi to account for network detection and SysV Init scripts
When the Linux container is created NextCloudPi automatically provisions via install.sh
Speedrun of the deployment: YouTube Link
I sent a PR to investigate if it's viable to accomodate this deployment method out-of-the-box. Not many changes needed, mostly just code for network detecton. If accepted, a fork won't be necessary and NCP could install (and update) on Android just like it does currently in Docker or on bare-metal.
Enjoy!
If you are frustrated since #L2TP/PPTP is gone after MIUI 13 Update, or after your phone's / tablet's / device's Android Version update, then this full guide tutorial is for you. If your phone, tablet, or mobile device's Android version is above 11 and you can't find the #PPTP VPN protocol to connect your private #VPN, then don't worry. Because I am explaining the easiest way to set up our VPN to connect from your device in this tutorial guide.
Point-to-Point Tunneling Protocol (PPTP) was so easy to set up on Windows Server and you were able to connect your private VPN easily through your phone. But this is not possible anymore since PPTP is removed from the majority of phones and mobile devices.
So instead of setting up our private VPN through features of Windows Server, we are going to use open source #SoftEther VPN Project.
In this video I will show you thoroughly from scratch:
1: Generate a new virtual server on Hyper-V and install Windows Server 2019 evaluation version.
2: Install SoftEther VPN Project on Windows Server 2019.
3: Make the necessary configuration of SoftEther.
4: Generate and export the #OpenVPN configuration file.
5: Modify the OpenVPN configuration file which ends with the .ovpn extension.
6: Install the OpenVPN app through Google Play Market and import the .ovpn configuration.
7: Connect to your VPN from your phone. I demonstrate this with my Xiaomi Poco X3 Pro - Android 12
8: With this methodology, we don't have to deal with complex and very hard-to-set-up IKEv2 / #IPSec #MSCHAPv2, #IKEv2 / IPSec #PSK, and IKEv2 / IPSec #RSA VPN protocols. These are the only available protocols on my mobile device.
0:00 Introduction
1:17 New Virtual Machine
3:28 Setting up Windows Server 2019
7:20 SoftEther Download & Installation
11:56 How to Setup OpenVPN on the Phone and Use VPN
click bait! there is no IKEv2 configuration, only OPENVPN. shame on you!
sandreanops said:
click bait! there is no IKEv2 configuration, only OPENVPN. shame on you!
Click to expand...
Click to collapse
let me explain again. how else I could describe this video title ? why did I made this video?
Because I wanted to setup my vpn. However all existing tutorials not anymore working because phones are now only supporting IKEv2 . So I did search for IKEv2 word
And what a surprise there isn't any good tutorial and easy way to setup IKEv2
Instead I did a lot of research and found a way to connect IKEv2 supporting phones
an easy one
How is this now click bait?
You are fooling people. Those who enter this post or see the title of your video on YouTube are waiting for a guide to configure an IKEv2 MSCHAPv2 server and be able to connect from Android 12+ with the integrated VPN client. Instead, what you show has nothing to do with IKEv2, it is an OpenVPN server for which it is necessary to use a third-party app on Android.
Also SoftEther does not support IKEv2, only IKEv1 (ISAKMP)/L2TP.