Hey folks,
Anyone tried using Vysor with the S7 Edge and got it to work successfully here?
I can't seem to get it to work. I have USB debugging mode on and tried both MTP and PTP but I keep getting the error:
'An error occurred while connecting to the Android device. Restarting the Vysor app, or disconnecting and reconnecting the Android may resolve this issue.'
I've had this working on my Moto X and N5 before.
Or does anyone know of a good alternative app? I was trying out Teamviewer Quicksupport but it looks like it keeps the phones display on all the time.
Thanks.
Had to restart my computer after installing the Samsung drivers! All good.
Had it working on Note II before. When I have connected S7 edge it just continued to work on the same computer.
For those who are struggling:
This error usually happens if something else is using adb.exe
Probably your phone sync software or any other software that can communicate via adb. Close the application (not only with exit, use task manager and force close) and it will be ok.
daninet said:
This error usually happens if something else is using adb.exe
Click to expand...
Click to collapse
For a month I was also getting adb connection issues until I figured out what the problem was, and it turned out it's due to adb being sensitive to the changes that happen on the phone in Android 11 and Android 12.
It took me a while but about two months ago I got Vysor (and scrcpy) to work (almost) flawlessly on Android 11 (with USB setting up the initial adb connection and then switching to Wi-Fi thereafter)....
In early May I updated from Android 11 to Android 12 and I found out that Android 12 has a fantastic new Developer option "Wireless debugging" feature where you can set up the adb connection to the PC completely over Wi-Fi (no need for the initial USB connection!).
I just wanted people to know new information related to using Vysor completely over Wi-Fi (no USB connection is ever needed again!).
This always on Wi-Fi Vysor capability is new in Android 12 because Android 12 has a new Developer option for "Wireless debugging".
However, Android 12 also has a new Developer option for "Enhanced MAC Randomization" which randomizes the MAC address on every Wi-Fi connection, so with that added desired Wi-Fi simplicity in Android 12 comes also the added desired privacy of MAC randomization on every connection (the difference being Android 11 only randomized the MAC per SSID, as far as I understand it).
All this new Android 12 functionality has implications for your Vysor (and scrcpy) setup, based on my tests over the past couple of months.
Of course, if your router is using the MAC address to hand out the IP address you might need address reservation since the router can no longer expect a consistent MAC address if you set that new Android 12 Developer option but you can set the Android phone to request a "Static" IP address (if you want the adb connect commands to be consistent in the IP address in day to day usage).
I have found that rebooting the PC causes me to need to reconnect via an adb command on the PC before Vysor will work, and, for unknown reasons yet, often the Android 12 "Wireless debugging" switch gets turned off (mysteriously) - which affects the Vysor (and scrcpy) connections from one day to another.
It's no big deal once you figure out the commands and switches though, where the screenshots below show the settings I currently have on my unrooted Android 12 Samsung Galaxy A32-5G phone from T-Mobile (many of which are for privacy and functionality reasons).
Related
What about AdHoc wifi support in MDJ Android builds (or others)? I am using 'MDJ FroYo Sense Clean v. 2.3 [kernel: mdeejay #15]' and in no way i can enable adhox wifi...
I looked around a lot, and i found nothing that works:
*) There is this thread that fixes the problem by patching the wpa_supplicant binary, and provides a compiled one to put on your android, but the mentioned file doesn't even exist on Sense Clean, can this be integrated? or how does it work?
*) This blog entry explains how to enable ad hoc on Samsung Galaxy, but it uses wpa_cli, which is also not present on this android build
*) few threads and blogs explain about how to enable this by directly modifying the wpa_supplicant.conf (/data/misc/wifi/wpa_supplicant.conf) and tiwlan0.conf (/system/etc/wifi/tiwlan.ini) files, but seems that in latest builds this doesn't even work, and anyway, the tiwlan is not found in the mentioned location.
update to point 3:
as expected, ap_scan is removed from the conf file, and what i get is only that android tried to connect (Connecting to ssid, Authenticating to ssid) but then disconnects.
does anybody have a working solution?
If I am understanding your post rightly, you are looking for connecting your HD2 with the Internet connection of your computer, either WLAN or LAN fixed.
I have been looking around as well, as I am travelling a lot and in some parts of the world there is only plugged LAN connection available in hotels, so one cannot use an Android fone unless you want to push your roaming costs skywards!
However, I managed to connect the HD2 to the internet via my laptop with a free little program called Connectify and it is working flawlessly.
Works only under Windows 7 though.
Maybe this helps.
WinMo Goatrip 6.0
Android MDJ 1.3 Matted
MDJ S3 Kernel and very happy with it
SO, this Connectify will make you laptop wifi appear as if it is an Access Point and not AdHoc network, making any device connect to it?
Ok, but unfortunately it doesn't support my laptops intel wifi module (3945), that's the reason i've never checked what connectify really do. But i'll try with a usb wifi that i have.
Thanks for the tip...
Update:
Thanks !!! it worked !!!!!!
With an external usb wifi adapter that is supported by Connectify i was able to connect Android to the computers Wifi network, more than enough.
NO ROOT required!! - I am using MyTouch 4g with android 2.2.1
This is for anyone using Android who wanted to use Ad Hoc network to connect to internet (Android device connects to PC/laptop which is connected to internet) and couldn't because android doesn't support it ( Not rooted ). Here is a solution that DOESN'T require rooting the phone. I am running Android 2.2.1 and have no knowledge on compatibility despite my 2 days of research and eventual success.
Things you need: Windows 7, Android device and Connecitfy software ( link below... free version works just fine )
1. Update drivers for Ethernet and WiFi adapters in device settings... windows virtual WiFi miniport adapter should show up in the device list
2. Now startup Connectify: Create hotspot and choose password (uses WPA) and then start hotspot.
3. Now on your android device this network name should show up because its not Ad Hoc anymore. Its like a virtual router or hotspot.
4. NOTE: If google services fail on the android device. Go to account and settings and then sync now for your google login. Once synced, try opening android market and if it says authentication failed, try opening market two or three times more and it should eventually accept. If it doesn't... go find a solution and add to this post or create a blog.
5. Enjoy...hey hey wheres my treat!!
Links that helped me:
www(.)connectify(.)me --- The software -- I AM NEW SO IT DOESN'T LET ME INSERT LINK!!
erratasec(.)blogspot.com/2009/11/windows-7-includes-soft-ap(.)html -- Main source for solution (Remove dots)
Hello. First of all I want to apologize for my bad English... I'm still learning it. Second of all, this problem is appearing on any device I try to connect to my PC's Wifi Hotspot, but to be specific:
- Huawei Ascend Y511
- Samsung Galaxy Y (GT5360, not really sure for that one, I don't have access to check the exact model)
- Vonino Sirius QS (Tablet)
- Prestigio Quantum Multipad 4 (9.7" / Tablet)
- Samsung Galaxy Tab3 8.0
- Samsung Galaxy S4 / S5
- LG G Flex
(I have a hobby to collect different phones and tablets, yeah... it's crazy I know )
Recently I installed Windows 7 on my laptop because the old windows XP was bugged completely... The only working components were the browser and the Bluetooth (Which is not working currently). First of all I tried to start a wifi hotspot from the networking and sharing center that comes with Windows 7, but I couldn't manage to do so. So I went to another option - softwares that enable the Wifi Hotspot on your laptop. The best result I got was Connectify, but I don't have the funds to buy it, so I used it temporarly (a week or so), and then it stopped working (Ethernet Sharing problems). Since then all the softwares I tried are starting the Wifi Hotspot, but when I try to connect every device gets stuck at "Obtaining IP Adress...". I tried looking for solutions, but I couldn't find anything that helps. I tried setting the IP adress to automatically obtain IP adress (The one in the change adapter settings tab in Control Panel), but then the network itself does not want to work. I ran out of ideas on how I can fix this...
Just some additional info: The local area connection is shared and the wifi is allowed, also the WLAN Autoconfig service is working properly.
Refresh IP
MoltenX said:
Hello. First of all I want to apologize for my bad English... I'm still learning it. Second of all, this problem is appearing on any device I try to connect to my PC's Wifi Hotspot, but to be specific:
- Huawei Ascend Y511
- Samsung Galaxy Y (GT5360, not really sure for that one, I don't have access to check the exact model)
- Vonino Sirius QS (Tablet)
- Prestigio Quantum Multipad 4 (9.7" / Tablet)
- Samsung Galaxy Tab3 8.0
- Samsung Galaxy S4 / S5
- LG G Flex
(I have a hobby to collect different phones and tablets, yeah... it's crazy I know )
Recently I installed Windows 7 on my laptop because the old windows XP was bugged completely... The only working components were the browser and the Bluetooth (Which is not working currently). First of all I tried to start a wifi hotspot from the networking and sharing center that comes with Windows 7, but I couldn't manage to do so. So I went to another option - softwares that enable the Wifi Hotspot on your laptop. The best result I got was Connectify, but I don't have the funds to buy it, so I used it temporarly (a week or so), and then it stopped working (Ethernet Sharing problems). Since then all the softwares I tried are starting the Wifi Hotspot, but when I try to connect every device gets stuck at "Obtaining IP Adress...". I tried looking for solutions, but I couldn't find anything that helps. I tried setting the IP adress to automatically obtain IP adress (The one in the change adapter settings tab in Control Panel), but then the network itself does not want to work. I ran out of ideas on how I can fix this...
Just some additional info: The local area connection is shared and the wifi is allowed, also the WLAN Autoconfig service is working properly.
Click to expand...
Click to collapse
Try checking your IP Configuration and refresh the IP In the Windows Internet and Sharing Center.
JBmorris said:
Try checking your IP Configuration and refresh the IP In the Windows Internet and Sharing Center.
Click to expand...
Click to collapse
Did that many times, but didn't work. I just hate Windows 7... it's the worst windows for network adapters -.-
I have been using vysor since i had my Samsung galaxy S4A and it has been working flawlessly which is why i bought it. Ever since I changed phones from s7 to s10+ I've noticed that after a bout 3-5 minutes of playing I get a blue lock on the screen and it makes me pull to the side to unlock it. What i don't understand is why this started happening when i have had two phones (S4A and S7A) both worked perfectly without getting this annoying blue lock screen and now i cant even play/macro a game without the screen locking. Anyone else use this software getting the same thing? Any suggestions would be appreciated.
Battousai21 said:
after a bout 3-5 minutes of playing I get a blue lock on the screen and it makes me pull to the side to unlock it.
Click to expand...
Click to collapse
Can you just right click with your PC mouse and sweep upward on the mirrored phone to unlock it?
I just found this thread long after I got Vysor (and scrcpy) to work (almost) flawlessly on Android 11 (with USB setting up the initial adb connection and then switching to Wi-Fi thereafter)....
In early May I updated from Android 11 to Android 12 and I found out that Android 12 has a fantastic new Developer option "Wireless debugging" feature where you can set up the adb connection to the PC completely over Wi-Fi (no need for the initial USB connection!).
I just wanted people to know new information related to using Vysor completely over Wi-Fi (no USB connection is ever needed again!).
This always on Wi-Fi Vysor capability is new in Android 12 because Android 12 has a new Developer option for "Wireless debugging".
However, Android 12 also has a new Developer option for "Enhanced MAC Randomization" which randomizes the MAC address on every Wi-Fi connection, so with that added desired Wi-Fi simplicity in Android 12 comes also the added desired privacy of MAC randomization on every connection (the difference being Android 11 only randomized the MAC per SSID, as far as I understand it).
All this new Android 12 functionality has implications for your Vysor (and scrcpy) setup, based on my tests over the past couple of months.
Of course, if your router is using the MAC address to hand out the IP address you might need address reservation since the router can no longer expect a consistent MAC address if you set that new Android 12 Developer option but you can set the Android phone to request a "Static" IP address (if you want the adb connect commands to be consistent in the IP address in day to day usage).
I have found that rebooting the PC causes me to need to reconnect via an adb command on the PC before Vysor will work, and, for unknown reasons yet, often the Android 12 "Wireless debugging" switch gets turned off (mysteriously) - which affects the Vysor (and scrcpy) connections from one day to another.
It's no big deal once you figure out the commands and switches though, where the screenshots below show the settings I currently have on my unrooted Android 12 Samsung Galaxy A32-5G phone from T-Mobile (many of which are for privacy and functionality reasons).
Hello!
I have a bit of a weird situation here.
I have a WiFi router in a remote location that needs configuring (Linksys EA2750) as it lost its settings after a power outage. The person that could help me is technically challenged, but at least there is an Android phone there that I can access remotely. The phone is an un-rooted Nokia 5.1 Plus (still) running Android 9. This phone is connected both to the router via WiFi and to mobile data. I can remotely operate it via Team Viewer.
I have tried to use the router's official Android app, but it is unable to configure the router's WAN/Internet settings. I have tried to connect to the router's web admin page, but it is inaccesibile via the browsers (tried Chrome and Firefox). I have tried using a firewall app (Mobiwol and NoRoot Firewall) to limit the browsers to WiFi only without any luck.
The only thing that I think will work is to somehow force the browser to use the WiFi interface no matter what. I've already spent hours trying to find out how to do that, but I am kind of losing hope here. I am guessing that I might need root access to accomplish that, but I am hoping it will not come to that.
I would appreciate any help in making my friend's phone stay connected to Team Viewer's servers via mobile data and access the WiFi router's admin page simultaneously.
Thank you in advance!
This has actually been bugging me for years but now I finally open this question to forums: So I have at my home several wifi-devices. And my wifi comes from my phone that creates the hotspot. Apps for controlling these wifi-devices always require wifi-connection to the same wifi-network they are themselves. So i need to have a second phone to control them because my "main phone" cannot be both hotspot provider and connect to the same hotspot itself. Is there any workaround to this ? Using android 10 with Zenfone 7. I would love to get rid of that 2-phone system at home. And i' not looking for solutions that require more devices