[Paid Software Announcement and Discussion] Chainfire:
Back from vacation :)

If your device has a standard microUSB connector this isn't possible due to USB OTG design. Even "powered" host cables actually provide power to the client (camera), not the host (Android).

This is something specific with Nexus devices firmware (seems to be the kernels). This problem does not occur on various other devices.

There are two parts to this.

(1) Most EOS models have a "live view silent mode" setting that is enabled by default. Flash is not triggered if this feature is enabled.

(2) Even if that setting is disabled, there have been various reports that various non-Canon-branded flashes do not work, but the Canon ones do.

After bug-fixes, this is actually the number one priority feature for DSLR Controller at the moment. However, this is much more complicated and there are many technical problems that have to be solved for this. More in the area of how Android works (and how Android actively works against DSLR Controller) than any hardware issue. It would take me hours to explain, but rest assured, this is unfortunately a very complicated feature to implement.

(1) I'm not sure what the problem is with your liveview, but it's not specific to the 50D. I have a 50D myself that works without issue.

(2) No, because all the (current) functionality is dependent on having a camera connected.

(3) Unfortunately, the image decoding will not become much faster. If you are using JPG/L or CR2 this is pretty much as optimized as it's going to get. After taking a picture, the camera waits for the image to be written to the card fully (not just in buffer, but actual written to card) before it tells the Android device the picture is ready. Then the Android device needs to download the image over USB (which isn't that fast on most devices), and then it needs to decode the image. The decoding part can take a second or two on it's own, and is already fully hardware accelerated. The speed of that will only improve with the next generation mobile GPUs.

(4) This is one these things that are very tricky to make. (See my reply above this one). DSLR Controller takes up pretty much as much CPU and RAM as your device can throw at it, and Android will allow. As a result, Android constantly wants to close DSLR Controller. As long as DSLR Controller remains the "focussed" app, it usually succeeds in staying alive - but as soon as you want to share (using the three-point standard Android share button) the app becomes a background app - an invitation to trouble. This doesn't mean it's not possible to build something for this (after image download mode is finished), but it does mean I might have to build all the code from scratch myself, instead of being able to leverage existing components and code provided and maintained by Android developers and/or Dropbox etc.

Interesting, will check this out.

Beginner mode/expert mode, not coming any time soon.

Night mode: been on my to-do list for ages. Still looking for a good way to actually implement this.

Yes.

Also on the to-do list !

This is all on the list, but with no solid date for release. I understand the need but all this is very complicated to do right and keep the app working.

As for continuous shooting mode, its configurable if the button is touch once to start shooting, again to stop, or keep shooting while held.

See my response to ryusen above.

See my response to ryusen above.

Sorry, it seems your hardware is ok for DSLR Controller, but the software (probably kernel) isn't right :(

Good to know! :)

Yeah see all my responses above ;)