A simplest Application access "Content Provider"

by Dianne Hackborn » Thu, 06 May 2010 05:40:43 GMT

Sponsored Links
 Please don't spam questions across every android group in the world.

> website: 

A simplest Application access "Content Provider"

by linlone9 » Thu, 06 May 2010 10:51:57 GMT


I've corrected it.
If you have any idea about this issue, please help check it.


2010/5/5 Mateusz Kozak <mateuszkozak...@gmail.com>


Sponsored Links

A simplest Application access "Content Provider"

by grace » Thu, 06 May 2010 13:51:05 GMT


getcontentResolver() is the method of Context class which is the super
class of activity,

so any non activity class cannot get access to the content resolver
one work around(even though its not good practice to do..)pass the
content resolver object as parameter to the function you want to use
it from another class which is a activity,
but in your case i don't think you have that option of passing content
resolver object from another class as you have only one class that is
calling main in your program.

On May 6, 7:51am, linlo...@gmail.com wrote:

Other Threads

1. Can I add Linux Driver on the Gphone when I bought it?

You'll need a rooted phone I think. See here for details:

2009/3/23 Handy_Zhou <qdzhouhanq...@gmail.com>:

echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc
This will help you for 99.9% of your problems ...


2. Surfaceflinger in cupcake

I am currently upgrading the old base to cupcake base. I meet 2 issues with
video playback and surface flinger.

   1. In my old code base, the YUV data is put onto overlay directly after a
   few seconds operations with postBuffer through base layer. This is mainly
   because android did not have framework for overlay previously. This worked
   fine until I move the same code onto cupcake recently.  Right now I find
   even if I don't go through postBuffer any more, as long as the buffer list
   is not unregistered from the surface handler, surface flinger seems to keep
   pushing the last 1 or 2 frames onto base layer by itself. This costs a lot
   of CPU cycles when I actually only need overlay. My question: is this a new
   feature introduced into surface flinger? If so, is it reasonable for me to
   unregister this buffer list to save performance? And is there an interface
   in application level to control the behavior of surface flinger like
   disabling pushing the last frames?
   2. Even if I unregister the buffer list of surface handler, there are
   still 2%-3% CPU Mhz (600MHz in total) consumed by "system_server". I did not
   observe this issue in older code base. It seems a bit weird as I dont know
   where it comes from.

I'd appreciate if any hints are provided!



3. How to show my ProgressBar

4. How to test camera on android

5. Multiplayer game

6. Anyone interested in joining an Android Developers Group on Linkedin?

7. MediaPlayer fails with LocalSocket