Is it true that Samsung removed USB OTG Host capability from latest firmwares?
"DSLRcontroller" requires USB host and developer is suggesting that Samsung removed the feature.
http://dslrcontroller.com/devices.php
https://market.android.com/details?id=eu.chainfire.dslrcontroller
Could anyone try or disagree?
Galaid said:
Is it true that Samsung removed USB OTG Host capability from latest firmwares?
Click to expand...
Click to collapse
Why would you doubt Chainfire?
http://www.chainfire.eu/articles/103/_SGS2_KI_Samsung_removes_USB_host_support_patches_bootloaders/
http://forum.xda-developers.com/showthread.php?t=1202082
Any official response from Samsung about WHY did they remove the feature that existed on previous 2.3 ROMS?
Is this true ???
Sent from my GT-I9100 using Tapatalk
Someone correct me if I'm wrong, but the way I understood it was this:
USB OTG still works (technically) for "identified devices"; those devices being flash drives (and by extensions also usb card readers which appear as flash drives), mouse and keyboard. "Unidentified Devices" ie your DSLR will not activate in the newer firmwares. If Samsung didn't specifically add the device's USB id to their "whitelist" of approved devices, it will not activate. My guess is certain unsupported devices may have been causing issues with the phone?? Not quite sure, but this is the cause of this app not working on the newer firmwares. Before now, any usb otg would work in the sense that the phone would connect and form a link with it, even if it didn't necessarily know what to do with it (be it a webcam, dslr, etc) which is again what we need for this dslr program to work.
Maybe an answer could be to locate and modify the whitelist? My guess is that might be the easiest solution (speaking as a non-developer...)
compuw22c said:
Someone correct me if I'm wrong, but the way I understood it was this:
USB OTG still works (technically) for "identified devices"; those devices being flash drives (and by extensions also usb card readers which appear as flash drives), mouse and keyboard. "Unidentified Devices" ie your DSLR will not activate in the newer firmwares. If Samsung didn't specifically add the device's USB id to their "whitelist" of approved devices, it will not activate. My guess is certain unsupported devices may have been causing issues with the phone?? Not quite sure, but this is the cause of this app not working on the newer firmwares. Before now, any usb otg would work in the sense that the phone would connect and form a link with it, even if it didn't necessarily know what to do with it (be it a webcam, dslr, etc) which is again what we need for this dslr program to work.
Maybe an answer could be to locate and modify the whitelist? My guess is that might be the easiest solution (speaking as a non-developer...)
Click to expand...
Click to collapse
Hey,
I am not an expert on this, but I belive that your statement is just partially true.
I just encounterd the same problem, i.e. usb-devices such as mouse, usb-stick, etc are properly supported BUT my own application would not run on my SGS2 (running KI1/KI1/KI1).
The application doesn't try to establish a connection to any unsupported device whatsoever (i.e. it just queries the number of connected usb-devices). Hence there is no special requirement for this application except the presence of the USB Host API, but this application crashes just like any other application which requires USB HOST (e.g. DSLRController).
Best
Related
I have a Canon EOS 350D which needs a driver on windows. Canon could solve this with a new firmware but this will not happen. If I have the usb adapter for the SGT is there a solution to copy photo's from the EOS? Or will I have to take the pcmcia card out to copy photo's?(and use a seperate reader).
Is this a strange Q? Or is it simple: If there doesn't exist an android driver for a external usb device you can't connect it?
It annoys me big time, I will own a nice piece of equipment like the tab, but have to carry a usb adapter, a usb cable and a cardreader with me, to transfer photo's from my camera when I'm on the road.(and the hassling with removing cards etc.)
I don't think there will ever be native support for proprietary drivers in Android. I'm no developer so I can't say if you could add support for that camera driver through an app but I don't think you'll get around the sd card reader + USB adapter combo for now.
If you can find Linux/Ubuntu support for it, you MIGHT be able to hack it in with an alternate kernel - but depending on the nature of the support method, the user interface may be suboptimal. (using shell commands to mount, etc.)
Edit: Check Themes and Apps section, new news. There's apparently now a "DSLR Controller" app, not sure how well this will work for you. I shoot Pentax so I can't test it.
Entropy512 said:
If you can find Linux/Ubuntu support for it, you MIGHT be able to hack it in with an alternate kernel - but depending on the nature of the support method, the user interface may be suboptimal. (using shell commands to mount, etc.)
Edit: Check Themes and Apps section, new news. There's apparently now a "DSLR Controller" app, not sure how well this will work for you. I shoot Pentax so I can't test it.
Click to expand...
Click to collapse
If I can also copy photo's with it, it will be great. Thanks, I will check it out.
Since the Xperia Tipo doesn't seem to support USB OTG although several sources on the Internet claim that it does I'm now thinking about getting an Xperia U for a college project where we need a relatively low-priced USB host capable Android smartphone.
But before actually getting the device I have two questions which I would be really glad if you could answer:
-the "USB Host Diagnotic" database here (http://usbhost.chainfire.eu/) says that several ROMs for the Xperia U are USB host capable stating
OS Support: Yes
3rd party apps: rooted
Does this mean that once the device is rooted the entire Android USB API (like described here: http://developer.android.com/guide/topics/connectivity/usb/host.html) or does it just mean that some Apps can utilize the USB host features using some non-standard API?
-I read that there is some limit for the maximum current an attached USB device can draw from the Xperia but unfortunately I never could find the exact value for the maximum current that is supported - not even in Sony's official datasheet and manual
Thanks
Regards,
karlmueller
The Z2 supports OTG apparently. My question is, can I move files directly from my current Android phone to my Z2 using OTG? Or Do I still have to use my PC as the middleman between the two?
sacredsoul said:
The Z2 supports OTG apparently. My question is, can I move files directly from my current Android phone to my Z2 using OTG? Or Do I still have to use my PC as the middleman between the two?
Click to expand...
Click to collapse
You cannot directly connect two phones with a cable and transfer files. The reason is that the phone never exposes its filesystem directly, but uses an MTP client to make files available on a PC. Since the Z2 is not an MTP host, it cannot see the files on the "old" phone.
There could be an exception if your "old" phone is really old. Originally, Android phones used a FAT filesystem for the "SD card", and then often exposed that directly to PC's, and then they ought to work also with an OTG phone as host. I cannot confirm what phones from what manufacturers would work in that manner, however.
Another way to transfer files, if your old phone supports OTG, is to use a USB memory stick as intermediate storage. A PC might still be more convenient, however, compared to using a clunky file manager on yotr phones.
Hi Devs!
I imagine this should be already discussed and explained somewhere, but I just can't find it as the word "android driver" is ambiguos and directs me to different topics.
Here we go with the question: nowadays many Android devices come with otgusb, so you can connect usb sticks, and all sorts of compatible devices. But: how to make a device compatible?
Since Android is linux, I assume loading a driver cannot be loaded just by installing an app, so do you need to call google and say "hey I got this new device, can you load the driver in your next kernel?" (sarcasm!!) or ...well...in short:
what the heck should one do if he wants to make a device compatible with android phones/tablets, even assuming he is able to write the driver by himself?
the question may be applicable to a variety of devices... a new remote one bought, a new BT wristband one wants to launch into the market, a usb sensor of some kind, etc etc etc.
thank you!
Ok, so I see there's apparently something called USB Host API, I read a little bit how it works, but I still have questions:
1. Does this mean basically that Android phone/tablet will provide RAW access via the USB Host API to any usb data stream received, and all I need is to write an app to decode that data?
2. If so, what makes a device compatible/incompatible?
3. If all of the above assumptions are wrong, please help
4. this still doesn't answer the bluetooth part, sorry for being so slow
Hi all, sorry if this thread is in the wrong place, but not sure where I'd actually put it, so feel free to move it to the correct forum if needed.
Basically I've got an android head unit in my car which claims to be running android 10 (the unit is a PX5 I think), and have multipe USB connections which allow me to plug in a memory stick to transfer MP3's onto the inbuilt storage, plug in a USB DAB radio receiver, or an OBD adapter, TPMS, etc. Problem is these devices are to be left plugged in permanently, and whenever I start the car I get a pop up notification asking if a device should be the default adapter for a specific app, etc. I've attached a photo to show the type of pop up I mean. There's an option to make it the default, which it doesn't want to be otherwise none of the adapters work with their respective apps, but there is no option to say no and never ask again? So it asks every single time I start the car. Is there a simple way I can stop this pop up from appearing? If I cancel the prompt, all works fine with each adapter and app, but I'm sick of having to cancel it every single time. No idea if the stereo is already rooted or not, haven't checked, but not sure if that would hinder me or not.
Does anyone have any ideas? Thanks.
StuartTheFish said:
Does anyone have any ideas?
Click to expand...
Click to collapse
None good or simple. This is a really annoying part of Android.
If you have an AndroidManifest.xml with meta-data in it (see: https://developer.android.com/guide/topics/connectivity/usb/host) then it will always pop up.
If you don't you won't be able to get permission to use the device.
What you and I want is to be able to say, "This app gets permanent and exclusive access to VID/PID 1234/5678, but never do an automatic app startup. Wait until the app is invoked normally."
System HID devices (like keyboard, mice) go in quietly, but belong to the system.
But to clarify things, is in this case your FTDI UART showing as a Linux /dev/ttySomething or just being handled in Java?
Could you do this:
Code:
$ zcat /proc/config.gz | grep CONFIG_USB_SERIAL
If yes, do you see it in /dev?
Hi, I've no idea how it's handled I'm afraid. All I know is it's a USB OBD adapter to do real time monitoring and data logging of my car's ECU. Normally it's used with a Windows laptop, but works with the android version of the software if I tell the app the VID and PID info. I also don't know why the TPMS app is the one always making the request to use this device when it has it's own one which it never asks for, it just works.
So, I guess that "TPMS" is "Tire Pressure Measuring System"?
So both your OBD and your TPMS use undifferentiated FTDI UARTs?
That's a separate problem.
Could you post the two apps to me privately?
Renate said:
So, I guess that "TPMS" is "Tire Pressure Measuring System"?
So both your OBD and your TPMS use undifferentiated FTDI UARTs?
That's a separate problem.
Could you post the two apps to me privately?
Click to expand...
Click to collapse
The two apps are NDS1 (Nissan Datascan), and the TPMS app is by Deelife, both are just apps I got directly off the play store. The NDS1 app needs to be configured with the VID and PID to work, which I found out via the serial USB terminal app, also from the play store. The TPMS adapter however doesn't show up in this, but the Deelife TPMS app just works regardless, albeit with it autodetecting and wrongly asking to use the UART one each time I start the car.
Nah, too much bother.