App does not scan QR code, no other option to connect

[droth-dreynor]

Edit: Maybe I am also misunderstanding the feature - is the QR code for WIFI only? Because the app just starts in it despite being connected to USB and the app-install via USB has been working before as well.

Otherewise the original report:

After giving the app the camera permission it does not ask for itself and getting the camera image to show up in the app it does not scan the QR code on the computer screen. It's a 4K screen and it's perfect conditions for it to recognize it so I am very sure that that is not the issue.
Personally I also think the QR code is not a good idea, since I have to unmount my phone from its stand to point it at the screen and then remount it - I think a simple 5 digit code or so you have to type in would have been easier and less error-prone.

And this should probably be a separate issue but the .bat for installing the APK fails silently if you just run it and closes the CMD window, unless you started it from within an existing CMD window.

[darusc]

Yes the QR code is just for the WIFI connection.

If it is plugged in it will directly connect through USB over the Android Debug Bridge but in order for this to work you must follow the steps specified in the README: first plug the phone in, start the windows app and then start the android app.

A 5 digit code won't work as you need the computer's IP address and that is definately more inconvenient to type.

Also regarding the BAT file, I tested it and it works even when started by clicking on it. Does it still fail if run with admin mode?

[VagrantOldFox]

Yes the QR code is just for the WIFI connection.

If it is plugged in it will directly connect through USB over the Android Debug Bridge but in order for this to work you must follow the steps specified in the README: first plug the phone in, start the windows app and then start the android app.

A 5 digit code won't work as you need the computer's IP address and that is definately more inconvenient to type.

Also regarding the BAT file, I tested it and it works even when started by clicking on it. Does it still fail if run with admin mode?

No, following that exact order it still won't connect via USB, nor will it scan the QR code. It just doesn't work, dude.

[DLC86]

Same here, I just can't connect in any way, QR code isn't detected by the app and the phone isn't recognized by the windows app when connected via usb

[darusc]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).

If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

[VagrantOldFox]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).

If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.

This is not a Windows firewall issue.
This is not an ADB issue.

The issue is, you built an app that does not function the way you advertise it to.

[darusc]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).
If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.

This is not a Windows firewall issue. This is not an ADB issue.

The issue is, you built an app that does not function the way you advertise it to.

Look, I've built this app for myself, not as a comercial app. It does its job for what I need, it works for me and for others.

I also don't understand people like you that expect any app on github to work flawlessly and have the support of a comercial app.

I told you the fixes that worked for me, thats it.

You are free to test and contribute to this project.

[VagrantOldFox]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).
If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.
This is not a Windows firewall issue. This is not an ADB issue.
The issue is, you built an app that does not function the way you advertise it to.

Look, I've built this app for myself, not as a comercial app. It does its job for what I need, it works for me and for others.

I also don't understand people like you that expect any app on github to work flawlessly and have the support of a comercial app.

I told you the fixes that worked for me, thats it.

You are free to test and contribute to this project.

And you're free to go fuck yourself. Prick and a hack.

[darusc]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).
If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.
This is not a Windows firewall issue. This is not an ADB issue.
The issue is, you built an app that does not function the way you advertise it to.

Look, I've built this app for myself, not as a comercial app. It does its job for what I need, it works for me and for others.
I also don't understand people like you that expect any app on github to work flawlessly and have the support of a comercial app.
I told you the fixes that worked for me, thats it.
You are free to test and contribute to this project.

And you're free to go fuck yourself. Prick and a hack.

Lol :)) keep it like this, you're doing great

[DLC86]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).

If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

Thank you, will try these suggestions and let you know if they work.

[VagrantOldFox]

USB connection is over ADB so that should start properly in order for app to work. Check app.log to see if adb actually started. (There might still be an adb process alive, end it in task manager and restart).
If the connection with QR code doesn't work make sure you allowed VCamdroid.exe in firewall when prompted (Go to firewall inbound rules, deleted everything related to vcamdroid and click allow when prompted next time). If it still doesn't work try pinging the server adb shell ping x.x.x.x and see if it is reachable.

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.
This is not a Windows firewall issue. This is not an ADB issue.
The issue is, you built an app that does not function the way you advertise it to.

Look, I've built this app for myself, not as a comercial app. It does its job for what I need, it works for me and for others.
I also don't understand people like you that expect any app on github to work flawlessly and have the support of a comercial app.
I told you the fixes that worked for me, thats it.
You are free to test and contribute to this project.

And you're free to go fuck yourself. Prick and a hack.

Lol :)) keep it like this, you're doing great

Moron.

[droth-dreynor]

Since I got an email notifcation about the comments just now:

I will be honest, I tried for about 1-2 hours to get the app working, couldn't get it to work for me, wrote this bug report and then went with a commercial product (Camo) because I needed to record a very long video just once.

I think since a lot of people run into issues, maybe you can try it out on a laptop or some secondary device(?) Or maybe make the app spit out more debug information easily or give the option to manually enter the IP address as a backup(?)

As for the rest of the comments:

I'll never understand devs like you, who refuse to simply admit something is not working the way it's supposed to, and instead expect end users to jump through a million hoops to get your bad software to function.

This is a free, non-commercial app built by someone for themselves and that someone was kind enough to upload it and write instructions for it because they thought maybe other people could use it as well. And while I understand that it's frustrating when the things you find online don't work, nobody owns you shit, especially not people who put their work online free to use and continue developing for other people. You didn't pay for a service. You didn't watch ads for this. This is like somebody deciding to help you out and clean your house and you come into the room after they worked for two days straight, slap them in the face and tell them they forgot to clean the bathroom mirror, so they are a "moron and a hack". When they did all those things for free. Get a fucking grip, understand and appreciate free and open-source projects especially coming from a single person or pay for a commercial product.