(Applications resident on SD complicate this a bit, but that's the
basic problem in a nutshell, and is the reason for the explicit policy
that you're seeing in action.)
For your test suite, you might consider using a two-process
architecture in which the system-process test code communicates via
the Binder or other IPC mechanism with another process whose job is
mostly to handle the file I/O.
--
chris tate
android framework engineer
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.
>
Can it be done, say, by making the system process call a C library
that opens & writes files ?
--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
tells me that if I am using APi level 7 or below I can use this path
"/Android/data/<package_name>/files/" ...
what does this mean?
Does it mean what I write hear will be reflected on the external
storage root path? /sdcard/ ?
So example I have my bluetooth C program saving an incoming file, I save it to
/data/com.android.bluetooth_ftp/bluetooth and will be reflected in
/sdcard/bluetooth ?
regards,
Pavan
--
--Pavan Savoy