I have a Samsung Galaxy Tab A 10.1" that I want to use as a second monitor with my PC. Spacedesk works great for my needs so long as I'm on a network with lots of bandwidth -- but more frequently I want to use second-monitor functionality in other environments, e.g. at a coffee shop, where the number of users bogs down network traffic and makes Spacedesk unacceptably slow.
Spacedesk doesn't natively support a wired connection, but for those who want one they suggest using USB tethering, presumably so both devices are on the same network. Problem is, my tablet is the Wifi-only version, so USB tethering isn't enabled. I rooted the device and used adb to run the commands enabling USB tethering as an option. It didn't take - the option never appeared under Settings / Connections. Then I installed ClockworkMod Tether as a 3rd party usb tether app. The PC tether software said it connected successfully to the tablet, but Spacedesk couldn't connect. Next I tried "gnirehtet", a reverse-tethering app. Got it working fine, but again Spacedesk on the tablet couldn't find the Spacedesk server on the PC.
How can I get both devices to be on the same network, without an intermediate connection (e.g. a router), in a way that preserves my PC's ability to connect to wifi, and that will allow Spacedesk to connect?
Turns out there's this thing called "Mobile Hotspot". Of course I couldn't use this on my tablet, as it had been disabled (thanks Samsung). But you can set it up on Windows easily -- in Windows 10 it's under Settings / Network & Internet / Mobile Hotspot. Connect your tablet to that hotspot and Spacedesk works like a charm.
Huge thanks to SpaceDesk customer support, who were extremely helpful in troubleshooting this apparently rather unusual situation. 5 stars both for the product, which I can now use anywhere, and the customer service.
Wifi tethering is possible with the tab A but only on android versions 6.x and below. it can be turned on via usb tethering enabling apps found in the app store that take you to the options in the settings of your device, these options appear to just be hidden in versions lower than 7 but removed in android 7 for whatever reason as the same apps just take you to an empty screen when used with 7.
If you have already upgraded to android 7.0 or above, and having spacedesk work with minimal lag is important to you, then I suggest you roll back youre tablet android version using Odin. This is what I've had to do after updating my tablet today (google it, there's plenty of guides out there)
TBH spacedesk is just poop over wifi. With USB you can watch video no problem
I tried the advice suggested here of using the mobile hotspot on my Windows 10 PC and used an old android tablet to create the extended screen to my PC using the suggested SpaceDesk app and it worked great! The download for Spacedesk for your Windows 10 PC is at https://spacedesk.net/ and the android app is in on the Google Playstore. Give it a try; it worked great for me.
I was connected to the internet over the LAN on my WIFI so I had difficulty in connecting the tablet (Samsung Galaxy Tab 3) over USB. My solution to this problem is disconnect your Laptop from the WIFI router from LAN cable as well as WIFI and use the tether option in tablet and connect it to the laptop and now it will work. Now for using the inter connect your Wi-Fi or LAN cable after this.
I tested the #Twiffy solution "Windows 10 hotspot" and worked for me. I disabled the tablet (Galaxy Tab A7) WiFi and the lag ended.
Related
I have a Samsung Galaxy S10 running Android version 10, and my USB connector does not work anymore. The Android docs state that I have to connect my phone to the host computer with a USB cable first before debugging via WiFi...
Are there any ways to work around this? I read one StackOverflow post that provided a solution (not sure if it works) for phones that are rooted, but I was hoping there was a simpler way.
Since your device is Android 10 you cannot init a Wireless connection without connecting it via USB first.
I don't know if the S10 is rooteable if you can root your device or it is already rooted you can follow the steps listed here:
How can I connect to Android with ADB over TCP?
You only need to prompt a few commands in your device to enable usb debugging via TCP.
Or you just need to wait for the Samsung S10 Android 11 update. Planned for this month.
I am developing an app with React Native. Thus far, Ive been testing on a iPhone, but naturally I want to test on an android device as well. I borrowed a OnePlus 6t, but I am having troubles connecting this device to my Macbook (pro 16" 2019). I've enabled developer mode and switched USB debugging on. Still my Mac does not recognize the device, even when I do adb devices. Any experience with this?
One sidenote is that the USB-C socket of the phone seems to be worn out, since my cable will not "click" into the device. The device is charging when sticking the cable in the phone though, so there seems to be some kind of connection.
Thanks for thinking along!
I asked for the original cable, and using that it worked. Seems that USB-C is not as universal as I thought.
My MacBook computer battery is broken and somehow it has not enough power to power device by usb-c adapter so I cannot connect anything and only have to use android emulator. But I need to debug on real device while testing some ocr sdk that obviously don't want to recognize anything in android emulator virtual scene. I asked other question about that but still I am puzzled by this inability to use WIFI for usb debugging because sdk runs fine on my phone but to debug using fabric and APK deployment is really horrible dev experience and productivity.
Is there some way I can setup WIFI debugging without cable at all... Maybe I need to root my device but again how to do it without cable, it seems impossible either way. I feel in like in dead and but still asking question here. I have computer and phone but cannot connect them for debugging by wifi.
Afraid I don't have an easy wireless solution. The closest thing I could find is that android wearables may have a debug over bluetooth feature, but it's built to route through another (wired) android device.
There is likely a feasible wired solution though- you can hook the device to a powered hub and the hub to the computer.
You could also use an adapter of sorts. They were built for printers and such before everything came with wifi and could get a proper wireless setup going without either side realizing they aren't directly connected over USB (OS still knows that some funky usb drivers are loaded and a separate application may need to run to connect), but again more hardware. A decent Wireless "USB Device Server" seems to run ~$100 while wired ones are cheaper, but not as cheap as a powered usb hub.
If you have another machine, you can use it to enable wireless debugging on your Android phone. See https://developer.android.com/studio/command-line/adb#wireless. Once wireless debugging is enabled, you can connect to it from your Mac without using USB. You still need USB for enabling wireless debugging though, but you can do it from a different machine. This should work on all Android phones, root is not required.
Update [2021]:
Things have developed since this question was asked. WiFi Debugging is a first class option now on newer devices. See https://developer.android.com/studio/run/device.html#wireless for details.
I can't seem to connect my Samsung Galaxy Note II (N7100) to my Windows 8 Machine (aiming to use the phone for debugging - but current can't even connect the device as mass storage). No USB notification is shown when connecting the mobile by cable.
Things I have checked thus far:
USB Cable (works on different machine and with HTC phone)
USB Ports (tried different ports, 2.0 and 3.0, all working)
PC USB Drivers
Phone (connects to my Win 7 machine)
Samsung Kies (and Samsung driver) and Google USB Driver both installed
PS. The reason Im asking this here is because I'm aiming to use the phone for development and I'm hoping to get some answers that aren't "have you double checked the cable?" like on every Google search I have performed so far. Hopefully another developer recognises this issue.
OK. so You've obviously done the basics and made sure all the cabling is functional.
it sounds like the Volume is not mounting in windows 8
if it's not detected in Windows Device Manager, and More importantly, if it's not visible in Disk Management, then the volume simply is not Mounting.
I would suggest
Try connecting to a Windows 7 Machine and see if it works, if it does, Then Most likely you need Windows 8 Drivers
I would be contacting Samsung Engineers for support on the Issue
What version of Kies are you using
i found this that might be useful for you
Ultimately, as you know the volume is not mounting due to Driver issues, and this needs to be resolved if you are to have a solution
You could always Try setting up XP Mode in Windows 8 and see if it recognizes that way.
Granted this is a bit of a workaround and a bit stuffy, but. Hey, it's another option.
let me know how you go
Go to dial pad & type *#0808#
It displays USB settings
Select MTP+ADB option
Press OK button
Connect to USB cable to PC
It shows Connected as a media device."
I am trying to develop an wifi peer to peer application in android(4.+).
The problem here is how to test it.
I tried to run that application in android emulator. there was no option to configure wifi in the settings menu, i also tired to enable wifi using the dev tools application form the emulator but it didn't work, And through all my googling over 3 days and i found that Android emulator is not supported the Wifi.
So i opted for androidx86 4.0eeepc using virtual box and tired to add devices both wifi and bluetooth (my app uses both bluetooth and wifi) but only bluetooth device got added and it did not work. But my virtual box detected the wifi and bluetooth devices. I just couldnt get them work with the virtual machine.
I tried everything like manually adding the addresses using terminal emulator app in androidx86 and used netcfg through the android commandline but neither of them worked.
Please suggest and guide me on the correct path to run these kind of applications that use wifi and bluetooth in android.
Thanks in advance.
First, be sure you enabled WiFi Direct in the Android settings for the two virtualbox instances:
Settings --> Wireless & Networks --> More... --> Wi-Fi direct
It has been stated as working once that hurdle was overcome, and I'm sure many have experienced the same...just be sure to enable wifi direct
I would have tried exactly what you've already tried by naturally moving from the emulator to the androidx86 project. Although unreliable, I'd recommend looking at and finagling this, if you haven't yet seen it: Android: Simulate WiFi in the emulator? and How to disable/enable network, switch to Wifi in Android emulator? most likely wouldn't have full out success but may be enough to let you know that it works or would work.
As far as testing WiFi-Direct/WiFiP2P without you yourself having a device/s, I would recommend:
Trying out some of the fiddling as mentioned above. And read through tons of logs.
You could always crowd source it to friends, or release an apk on a forum for a small group of testers.
Of course, both of those options are not ideal, seamless, or fast. So, I'd definitely hope you get VirtualBox VMs of AndroidX86 4.0 running as it should once you check that setting and pair up the WiFi APs :-)
A near future solution:
This might be something to look into in near future.
Real devices are hosted by Samsung and screens are streamed to your PC.
http://developer.samsung.com/remoteTestLab.do
According to an email responded by samsung, which I sent to them earlier.
They only have 2 devices (Galaxy Nexus) running on Android v4.0 at the moment.
Unfortunately they are not physically close to each other. (One in Korea, One in Poland)
But they are planning to upgrade existing Galaxy S2 to v4.0.
Because recently Samsung have released v4.0 upgrade for S2.
Once they done that, there will be plenty of v4.0 phones.
And you can ask them which 2 phones are physically close so you can test Wifi Direct.
--------------------------- EDIT ---------------------------------
There are plenty of ICS devices there now, which you can test P2P.
Check with them which 2 are physically near to each other.
Per the docs:
Each instance of the emulator runs behind a virtual router/firewall
service that isolates it from your development machine's network
interfaces and settings and from the internet.
You have to use Network Redirection, as described in the Developer Docs. In essence, you forward specific ports using ADB. Therefore you cannot test certain things like broadcast messages.
I have tried doing what you are trying to do, and-- while I won't say it is impossible (anything is possible in computing with enough time, money, and persistence)-- I wasted a lot of time on it. You cannot treat the Android emulator as a normal network peer-to-peer device. As far as I have been able to find, it is a fork of QEMU, and that is just how the QEMU emulator is implemented.
QEMU itself does support TUN/TAP bridging, but I was never able to get it working with the Android emulator. If you want to go that route, you may want to investigate running Android in the QEMU emulator, rather than in the SDK's emulator (I see you are already trying a similar approach with VirtualBox).
Unfortunately the best way to test a peer-to-peer networking program in Android is with physical devices at this time-- unless your app can suffice with the port forwarding method.
See Also: Issue 26:Emulated Androids should be able to communicate via TCP, and Google
(Repeating here my answer elsewhere.)
In theory, linux (the kernel underlying android) has mac80211_hwsim driver, which simulates WiFi. It can be used to set up several WiFi devices (an acces point, and another WiFi device, and so on), which would make up a WiFi network.
It's useful for testing WiFi programs under linux. Possibly, even under user-mode linux or other isolated virtual "boxes" with linux.
In theory, this driver could be used for tests in the android systems where you don't have a real WiFi device (or don't want to use it), and also in some kind of android emulators. Perhaps, one can manage to use this driver in android-x86, or--for testing--in android-x86 run in VirtualBox.