I have a problem with a USB hosting program I have written for the Galaxy Tab 10.1. I am trying to communicate with a PIC microcontroller via USB and had the program working a month or so back. Attachment to the PIC was by using an intent in the manifest, as per the standard method. However, I then upgraded via Kies to Android 4.0.4 and since then have not been able to use the program.
There have been a few issues - at first I had no luck in even seeing the PIC but once I told the PIC to pretend it was a mass storage device that problem cleared up (the original version was configured as an HID). It seems that in 4.0.4 Samsung have reintroduced the "whitelist" - can anyone confirm this?.
Now I have the issue that I can trigger my program on plugging in the PIC (which proves that the permission is working on attaching) but within the program the only intent that is seen is the MAIN one.
I don't want to go away from a stock device, and I don't want to have to downgrade back to 4.0.3 which I had when the system was working, and would appreciate any ideas.
There have been a few issues - at first I had no luck in even seeing the PIC but once I told the PIC to pretend it was a mass storage device that problem cleared up (the original version was configured as an HID). It seems that in 4.0.4 Samsung have reintroduced the "whitelist" - can anyone confirm this?.
Now I have the issue that I can trigger my program on plugging in the PIC (which proves that the permission is working on attaching) but within the program the only intent that is seen is the MAIN one.
I don't want to go away from a stock device, and I don't want to have to downgrade back to 4.0.3 which I had when the system was working, and would appreciate any ideas.
