CPM Plugins don't have permission to write external storage?

by RaviY » Wed, 02 Jun 2010 08:32:02 GMT


Sponsored Links
 I believe it is by design to not provide right permissions on the
sdcard to the mediaserver. If needed, you need to figure out a way to
pass an open file handle to your CPM component, and then use that to
do the writing.

-Ravi




-- 



Other Threads

1. PhoneStateListener not called until Phone Activity completes...

Hi -

I'm having a problem with my PhoneStateListener not being called until
after the Phone Activity is finished.  Here is what I am doing:

step 1:  Install a PhoneStateListener.  The listener is supposed to
call notify() (synchronized on the lock object) when it detects a
change in the phone state (specifically OFF_HOOK).

step 2:  Place a call with the ACTION_CALL intent.

step 3:  Call wait(timeout) (in a synchronized loop), waiting for the
listener to wake us up.

(I realize  wait/notify can be tricky but am confident the
implementation is  correct...)

Step 3 is always appearing to time out even though I am seeing the
call go through properly on the emulator screen.  No matter what
timeout value I use, it always times out even though
telephonyManager.getCallState() returns the correct value (OFF_HOOK).

I tried placing step 2 and step 3 in their own, separate (ordinary
Java) threads.  Same behavior.

When I tried placing step 1 in its own (ordinary Java) thread, Android
throws:

11-17 12:12:01.451: ERROR/AndroidRuntime(2004): Uncaught handler:
thread Thread-9 exiting due to uncaught exception
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):
java.lang.RuntimeException: Can't create handler inside thread that
has not called Looper.prepare()
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
android.os.Handler.<init>(Handler.java:111)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
android.telephony.PhoneStateListener$2.<init>(PhoneStateListener.java:
235)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
android.telephony.PhoneStateListener.<init>(PhoneStateListener.java:
234)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
test.phone.PhoneTestService$MyPhoneStateListener.<init>
(PhoneTestService.java:529)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
test.phone.PhoneTestService$MyPhoneStateListener.<init>
(PhoneTestService.java:529)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
test.phone.PhoneTestService.listenToCallState(PhoneTestService.java:
640)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
test.phone.PhoneTestService.access$2(PhoneTestService.java:618)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
test.phone.PhoneTestService$1.run(PhoneTestService.java:704)
11-17 12:12:01.451: ERROR/AndroidRuntime(2004):     at
java.lang.Thread.run(Thread.java:935)

Working on figuring out the right way to launch the listener in a
Handler thread - however, there's nothing in the PhoneStateListener
write-up about having to launch in a separate execution context.  This
doesn't seem to follow Java orthodoxy either - e.g., in Swing,
callbacks are invoked seamlessly - no separate execution context
required.

...Unless - I've overlooked something ...

Can anyone shed any light on this?

Thanks much.

-dreamer


--~--~---------~--~----~------------~-------~--~----~

2. rtc_alarm_interface should not do device specific thing

When driver register rtc_alarm_interface by class_interface_register
(),it wil call below code:
====
if (class_intf->add_dev) {
                list_for_each_entry(dev, &parent->devices, node)
                        class_intf->add_dev(dev, class_intf);
        }
====
Then rtc_alarm_add_device() will add at least one device to the
interface.But in rtc_alarm_add_device() driver do device specific
thing such as misc_register().

Though alarm_rtc_dev has value when exit the function the first time,
the latter call will just return -EBUSY ,i think this is not a good
design.
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 

3. Compressed Camera Images

4. Provide Web Access (non-Mobile) to Android Market!

5. Set an EditText view editable or not

6. how to use TouchDelegate

7. porting on ZOOM MDK