Hi Taylor,

Yes, mine is A501. Unfortunately I'm trying to experiment with my A501 in
India and the 3.1 update is not yet available here. Looks like I've to wait
for a long time before being able to check the USB Host APIs on A501.

Thanks a lot Taylor and I sincerely appreciate your great enthusiasm and
willingness to share the knowledge. Have great time!!!

Warm Regards,
Anil

On Tue, Sep 27, 2011 at 12:17 PM, Taylor Alexander <[email protected]>wrote:

> Hey Anil,
> I connected my tablet to wifi and it immediately said there was an update.
>
> You have an A501 though? Mine is an A500. Perhaps the A501 does not have an
> update yet? I'm not familiar with that model. Mine is wifi only. Since you
> mention verizon I assume the A501 is the verizon model. It may have
> different updates due to the cell module.
>
> -Taylor
>
>
>
> On Mon, Sep 26, 2011 at 11:19 PM, Anil Sasidharan <[email protected]>wrote:
>
>> Hi Taylor,
>>
>> Thank you so much. Where do we get the 3.1 update that was applied on your
>> tablet. Is it OTA (from Verizon??) or Is this available as a firmware
>> download somewhere in the Internet? I would really appreciate if you could
>> help us get this update for my Acer Tab A501.
>>
>> Thanks once again for the great support so far...
>>
>> Warm Regards,
>> Anil
>>
>> On Tue, Sep 27, 2011 at 4:15 AM, Taylor Alexander 
>> <[email protected]>wrote:
>>
>>> Yes, the tablet shipped with 3.0 but I immediately applied the 3.1
>>> update. And then another small update wanted to be applied, but I think USB
>>> worked after the first one. I didn't try it before that.
>>>
>>> Under "About Tablet" in settings I have:
>>>
>>> Model: A500
>>> Android Version: 3.1
>>> Kernel Version: 3.6.36.3
>>> Build Number: Acer_A500_4.0.10.13_COM_GEN2
>>>
>>> Let me know if you have any other questions!
>>>
>>>
>>>
>>> On Sat, Sep 24, 2011 at 8:20 PM, Anil Sasidharan <[email protected]>wrote:
>>>
>>>> Hi Taylor,
>>>>
>>>> Thanks a lot. Based on what have experienced, I guess the Samsung Tab
>>>> 10.1 with Android-3.1 firmware does not yet support USB Host APIs whereas
>>>> Acer's Iconia A500 supports the same. Would you please let me know the 
>>>> exact
>>>> version of the Android firmware on A500 that worked for you. I've come
>>>> across an Acer Tab A501 with Android-3.0.1 version, however I'm not sure if
>>>> it supports USB Host API because Google says it is supported only from 3.1
>>>> (sdk-version 12 and above) onwards (even though there is an back port of 
>>>> USB
>>>> Host library for Gingerbread out there).
>>>>
>>>> I would greatly appreciate your comments/suggestions on this.
>>>>
>>>> Warm Regards,
>>>> Anil
>>>>
>>>> On Sat, Sep 24, 2011 at 12:31 AM, Taylor Alexander <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Anil,
>>>>>
>>>>> Yes, I did get it working with the Acer. I had replied off list to Will
>>>>> because my original reply to the list was taking too long to get approved
>>>>> (it was my first post to this list).
>>>>>
>>>>> Here is my first off-list message, where I gave some details:
>>>>>
>>>>> On Thu, Sep 22, 2011 at 1:43 AM, Taylor <[email protected]> wrote:
>>>>>
>>>>>> Hey,
>>>>>> I replied to the group, but I'm not seeing the message, so I don't
>>>>>> know if it failed to post, or if its in limbo since I'm a new user.
>>>>>> Anyway, I wanted to reply directly to you. I was having the EXACT same
>>>>>> problem as you. I had a USB device that I had compiled a kernel module
>>>>>> for. I loaded the module onto the tablet, and lsmod showed it running.
>>>>>> However, I couldn't get the device to work, and dmesg showed the same
>>>>>> problem - device not supported, over and over, even though the VID and
>>>>>> PID matched the source code for the driver. I was going crazy, but I
>>>>>> thought it was my kernel modules, so I tried a different approach at
>>>>>> someone's suggestion.
>>>>>>
>>>>>> I tried some of google's example code for USB, and when it runs
>>>>>> getDeviceList() I had it print how many USB devices were connected. It
>>>>>> always reads zero, even when a functioning USB mouse is connected!
>>>>>> This was frustrating, so I googled for how to enumerate devices on a
>>>>>> galaxy tab, and found your post.
>>>>>>
>>>>>> After seeing your post, I realized this may be an issue with Samsung.
>>>>>> I bought an Acer Iconia Tab A500 today, as some users had reported
>>>>>> success with it - it works! The same code run on the galaxy tab still
>>>>>> fails.
>>>>>>
>>>>>> Both are running 3.1.
>>>>>>
>>>>>> So I'm inclined to believe this is an issue with Samsung. Did you ever
>>>>>> get this working?
>>>>>
>>>>>
>>>>>
>>>>> I have had continued success with the Acer, and none with the Samsung.
>>>>>
>>>>> Will - replying to your off-list message. I just checked again. The
>>>>> Acer enumerates a webcam and thumbdrive I've tried, but not a mouse or
>>>>> keyboard.
>>>>>
>>>>> This is with the following code, which logs values to logcat:
>>>>>
>>>>> UsbManager usbman = (UsbManager) getSystemService(USB_SERVICE);
>>>>>  HashMap<String, UsbDevice> devlist = usbman.getDeviceList();
>>>>> Iterator<UsbDevice> deviter = devlist.values().iterator();
>>>>>  PendingIntent pi = PendingIntent.getBroadcast(this, 0, new Intent(
>>>>> ACTION_USB_PERMISSION), 0);
>>>>>
>>>>> while (deviter.hasNext()) {
>>>>> UsbDevice d = deviter.next();
>>>>>  l("Found device: "
>>>>> + String.format("%04X:%04X", d.getVendorId(),
>>>>>  d.getProductId())); }
>>>>>
>>>>> where l is a function that logs stuff to the debug window.
>>>>>
>>>>> That is a snippet from the source code found here:
>>>>>  http://android.serverbox.ch/?p=370
>>>>>
>>>>> There is that USB missile launcher that the google demo supports. I
>>>>> have been considering getting one of those to do some more testing with 
>>>>> the
>>>>> Samsung.
>>>>>
>>>>> -Taylor
>>>>>
>>>>>
>>>>>  On Fri, Sep 23, 2011 at 7:34 AM, Anil Sasidharan 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>>  Hi,
>>>>>>
>>>>>> I'm curious to know if you were able to get this fixed using "Acer
>>>>>> Iconia A500". Are you able to use the android application to enumerate
>>>>>> devices using USB Host API?
>>>>>>
>>>>>> Warm Regards,
>>>>>> Anil
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 22, 2011 at 1:05 AM, Taylor <[email protected]>wrote:
>>>>>>
>>>>>>> Hey!
>>>>>>>
>>>>>>> I've actually had the EXACT same problems and it was driving me nuts!
>>>>>>> I'm running a 16GB Wifi Galaxy tab with the 3.1 touchwiz update.
>>>>>>>
>>>>>>> I can connect a USB mouse and keyboard and hub all just fine, they
>>>>>>> work great. However, when I try to enumerate the devices, I get
>>>>>>> nothing.
>>>>>>>
>>>>>>> To compound the confusion, I was trying to build custom kernel
>>>>>>> drivers
>>>>>>> for an unsupported device (FTDI chips) and it was driving me crazy
>>>>>>> because I could install the module and verify it was running, but I
>>>>>>> had the same problem - the device is not supported message. I thought
>>>>>>> it was me!
>>>>>>>
>>>>>>> Specifically, I was trying to do this:
>>>>>>> http://android.serverbox.ch/?p=285
>>>>>>>
>>>>>>> Then I tried this:
>>>>>>> http://android.serverbox.ch/?p=370
>>>>>>>
>>>>>>> and couldn't get it to indicate that ANY devices were enumerated,
>>>>>>> even
>>>>>>> when it was just a USB mouse that was working!
>>>>>>>
>>>>>>> So then I tried BOTH of google's example apps, modifying the code to
>>>>>>> print all enumerated devices. Nothing. It printed the count value for
>>>>>>> the number of devices enumerated. Zero. Again, this was with a
>>>>>>> functioning device plugged in (In this case a keyboard).
>>>>>>>
>>>>>>> Annoyingly, I couldn't even TRY the ADB example the way its intended,
>>>>>>> because my phone is apparently a "high power device" and the tablet
>>>>>>> straight up tells you it refuses to mount it. Grrr.
>>>>>>>
>>>>>>> But aside from the high power device issue, which is annoying but
>>>>>>> seems to be by design, I am starting to feel like there is some
>>>>>>> problem with the USB implementation on the Galaxy Tab 10.1, and I am
>>>>>>> going to go out and buy an Acer Iconia A500 since people have
>>>>>>> reported
>>>>>>> success with that, and I am doing this for work.
>>>>>>>
>>>>>>> I will let you know how that goes.
>>>>>>>
>>>>>>> -Taylor
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Aug 5, 6:58 am, wl <[email protected]> wrote:
>>>>>>> > Hi,
>>>>>>> >
>>>>>>> > I'm trying to interface to a USB device from my googleIO galaxy tab
>>>>>>> 10.1.
>>>>>>> >  I've been through the documentation on developer.android.com and
>>>>>>> stack
>>>>>>> > overflow and I can't find anything on this.  Here's the problem:
>>>>>>> >
>>>>>>> > I connect the USB device:
>>>>>>> >
>>>>>>> > I've set up device filters as per the docs, and nothing happens.
>>>>>>> > If I look in logcat when I connect the device, nothing happens.
>>>>>>> > If getDeviceList() says there are 0 devices connected.
>>>>>>> >
>>>>>>> > But if I connect to my galaxy tab 10.1 using "adb shell" then run
>>>>>>> dmesg, I
>>>>>>> > discover the device is being detected after all:
>>>>>>> > <6>[ 1685.332067] usb 1-1: new low speed USB device using
>>>>>>> tegra-ehci and
>>>>>>> > address 45
>>>>>>> > <3>[ 1685.370073] usb 1-1: device v1267 p0000 is not supported
>>>>>>> > <6>[ 1685.392656] host_notify: ndev name=tegra-ehci.0: from state=5
>>>>>>> -> to
>>>>>>> > state=5
>>>>>>> > <3>[ 1685.392726] hub 1-0:1.0: unable to enumerate USB device on
>>>>>>> port 1
>>>>>>> > <6>[ 1685.551797] usb 1-1: new low speed USB device using
>>>>>>> tegra-ehci and
>>>>>>> > address 46
>>>>>>> > <3>[ 1685.881732] usb 1-1: device v1267 p0000 is not supported
>>>>>>> > <6>[ 1685.903018] host_notify: ndev name=tegra-ehci.0: from state=5
>>>>>>> -> to
>>>>>>> > state=5
>>>>>>> > <3>[ 1685.903089] hub 1-0:1.0: unable to enumerate USB device on
>>>>>>> port 1
>>>>>>> >
>>>>>>> > Not only is it being detected, but it seems to be repeatedly:
>>>>>>> > - detecing the device
>>>>>>> > - reading the vid and pid
>>>>>>> > - declaring that they are not supported
>>>>>>> > - giving up on enumerating the device
>>>>>>> >
>>>>>>> > and then starting all over again, about 5 times a second.  I tried
>>>>>>> this with
>>>>>>> > a different USB device (different VID/PID), and saw the same
>>>>>>> pattern. My
>>>>>>> > questions are:
>>>>>>> >
>>>>>>> > - Could this be because I've managed to cock up setting up the
>>>>>>> intent
>>>>>>> > filters, or is there some lower level problem stopping the device
>>>>>>> even
>>>>>>> > getting that far?
>>>>>>> > - What constraints are there on which usb devices are supported on
>>>>>>> android
>>>>>>> > (e.g. are there limits to which protocols are supported? Or which
>>>>>>> VIDs/PIDs
>>>>>>> > are supported? Or some other constraints?)
>>>>>>> > - Is there any detailed documentation on USB on android (besides
>>>>>>> the
>>>>>>> > hardware.usb. api reference)?
>>>>>>> > - Has anyone else had this problem?  Have they found a solution?
>>>>>>> >
>>>>>>> > Any help would be much appreciated
>>>>>>> >
>>>>>>> > W
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Android Developers" group.
>>>>>>> To post to this group, send email to
>>>>>>> [email protected]
>>>>>>> To unsubscribe from this group, send email to
>>>>>>> [email protected]
>>>>>>> For more options, visit this group at
>>>>>>> http://groups.google.com/group/android-developers?hl=en
>>>>>>>
>>>>>>
>>>>>>  --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Android Developers" group.
>>>>>> To post to this group, send email to
>>>>>> [email protected]
>>>>>> To unsubscribe from this group, send email to
>>>>>> [email protected]
>>>>>> For more options, visit this group at
>>>>>> http://groups.google.com/group/android-developers?hl=en
>>>>>>
>>>>>
>>>>>  --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Android Developers" group.
>>>>> To post to this group, send email to
>>>>> [email protected]
>>>>> To unsubscribe from this group, send email to
>>>>> [email protected]
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/android-developers?hl=en
>>>>>
>>>>
>>>>  --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Android Developers" group.
>>>> To post to this group, send email to
>>>> [email protected]
>>>> To unsubscribe from this group, send email to
>>>> [email protected]
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/android-developers?hl=en
>>>>
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Developers" group.
>>> To post to this group, send email to [email protected]
>>> To unsubscribe from this group, send email to
>>> [email protected]
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-developers?hl=en
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google
>> Groups "Android Developers" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>>
>
>  --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to