New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to grant access to USB port through AndroidManifest #84
Comments
Maybe..but not for the feeble minded. @Calsign: I wanted/needed to activate largeHeap, and ended up hacking APDE using
My sketch.properties for this app, is below btw...but that may be relicts from unsuccessful attempts.
|
So APDE used to allow you to customize the manifest directly. I changed that behavior in v0.4.0 (the introduction of multiple build targets) because each target requires a different manifest and it was unclear how to support manifest customizations. Instead the manifest is re-generated from the @uheinema Yes technically you can achieve what you want by modifying the manifest template, but this isn't really a solution for most users because it means that every sketch built with the modified version of APDE will have the I've thought a bit about this and I am planning to implement the following solution:
Any suggestions or improvements to this plan are welcome, otherwise I will probably make it happen in the next week or so and try to include in the the v0.5.2 release. |
Grrr. the BackButtan ate my text... So short: Brilliant.But isn't this a lot of work on your side for relatively little effect? How about (optionaly, see 'Build on internal/external') putting the templates (all! And why not the whole assets folder...makes 'Reimport Android.jar' etc. superflous, and would allow access to the whole android XMLism, MainActivity, etc....I hate the stuff, but it is needed sometimes) on external storage? Templates could then be searched (in order of precedence)
And I think they could/should remain templates. Keep it up! |
The execution of arduino-Firmata samples, slightly modifies to adapt to android-serial lib constraints (use of Serial.list(this) instead of Arduino.list()), leads to a crash and the closure of the activity if an Arduino with standardfirmata is connected to the USB
if nothing is connected you get a warning asking to check
This seems to be possible to correct through the insertion, in the Manifest, of the "use-feature" tag mentioned above and pointing at USB.HOST port. Unfortunately, this is not possible with APDE since the manifest is re-generated from the sketch properties at build time
Tested (KO) on
Is there a known workaround?
The text was updated successfully, but these errors were encountered: