ADC II Package Rename & Content Providers

by Michael Elsd枚rfer » Tue, 01 Sep 2009 01:47:28 GMT

Sponsored Links
 This is slightly confusing me right now. If I have a content provider, 
should it's authority be renamed also? I would have thought it makes 
sense, allowing both versions to run next to each other cleanly.

But then I seem to be experiencing strange errors if both versions do 
run hat the same time, with the non-ADC version of the app trying to use 
the ADC-Provider...or something. I can not exclude a bug in my own code, 
but I don't see where the problem is right now - both the Authority 
defined as well as the URI used to access seem to be correct and 
different in each case.

Any obvious problems I might be missing? Is using two different URIs 
generally the way to go?



Other Threads

1. Google should clearly express their marketing strategy regarding Android Market


I know that this is often discussed topic but I think that it is very
important for strategy decisions.

What I would like to hear from Google is what is their short and mid
term strategy regarding Android Market. Whether the will prefer Ads
based model or whether they will open android market for more

I think that this information is very important for decisions about
investing to development of Android apps. Business model is IMHO
important before you invest any money and current situation (when they
have more than one year on the web that more countries come soon, and
nothing changes it is not trustworthy for me) is IMHO bad for

Ads based mobile apps needs to be designed differently than paid apps
and uncertainty may cause worse quality of the apps on the market from
long term point of view because to base Android Market apps supply on
free apps from hobbyists is IMHO bad idea.

I already developed quite successful apps to test demand (4 or 4,5
stars, more than 1000 installation (not downloads) daily) but because
of uncertainty I'm seriously considering to leave Android (which I
love from technical perspective but hate from business perspective)
and focus on Bada (which seems more much flexible from marketing point
of view) or iPhone.

There are many features suggested by users that would made my apps
almost perfect but I can't eat rating stars.

Another problem that can't be successfully solved without investments
of real money is Android fragmentation. There is huge amount of
Android versions, screen resolutions and customized ROMs (HTC Sense,
Motoblur, ...) that can't be tested in emulator that every developer
that wants deliver real quality needs to buy more than phone.

I'm frustrated from current situation and I guess I'm not alone


2. IllegalArgumentException when trying to run an OpenGL ES 2.0 application

The emulator doesn't support OpenGL ES 2.0 at this time.

>> > 

3. Any Tree (Swing/JTree-like) widget for Android?

4. <AbsoluteLayout>

5. Fast screen update

6. pesky problems with AVD at wits end what the hell am I doing wrong?

7. Media.insertImage locked to heavy compression