PS: if you're an advocate for equal rights and opportunity for AppWidgets,
please star this issue too:
https://code.google.com/p/android/issues/detail?id=33973
--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send
A reboot is not necessary (well, it's overkill) as all that is needed is a
restart of the Launcher app. So force close the launcher app and the widget
will show up. The problem is the Launcher app does not update the list of
AppWidgets as often as it updates the list of Apps.
I asked Dianne Hac
On Sunday, February 5, 2012 1:17:54 PM UTC+1, Mark Murphy (a Commons Guy)
wrote:
The 4.x WVGA emulator should run approximately as quickly as the
> Android 2.3 emulator.
>
It does run about as fast, but - in my experience - emulator stability has
taken a progressive hit with every platform versi
2012/2/4 David Ross :
> Why change working behaviour?
In this case, to help stop drive-by malware. Android has long had a
"nothing runs until the user runs it" approach, which is why there is
no on-install code you can have run. Developers were getting past that
by registering for system broadcast
Thank you.
Sigh, this sort of change is so very, very irritating.
Who makes these decisions? Why change working behaviour? This is the
sort of code bomb drop nonsense that is making it so very hard for
Android developers to make robust software. No cogent explanation as
the 'why' of this decision
Yes, this changed starting with 3.1:
http://developer.android.com/sdk/android-3.1.html#launchcontrols
The end result is:
App widget can't be added to the home screen immediately after the
installation.
The application's package needs to be moved from stopped to started state
first.
You can do
I guess I was not clear. Downloaded from the Market and then "run by
the user". Yes, the download and install process does not run the APK
automatically, but after it has been downloaded the Market App gives
the user the the options to "Open" or to "Uninstall". Even if the user
exits the Market App
But that's not how it works in 2.3.x.
Install the "App (Widget)", say from market. Don't run it when given
the "Open" option in the market after download completes. Don't launch
it from the Launcher either. Just navigate back to the Home Screen.
Long press on home screen and select Widgets. Hey p
On Thu, Feb 2, 2012 at 8:53 PM, David Ross wrote:
> The Activity WidgetDummyConfiguration is called when the APK has been
> downloaded from the market and run.
I sure hope not. Nothing is supposed to run in an APK file when it
"has been downloaded from the market and run". Certainly not the
MAIN/
I do not really believe that your WidgetDummyConfiguration is called after
installation of the app. Usually apps are not started via their main
launcher after installation, or am I getting something wrong here?
--
You received this message because you are subscribed to the Google
Groups "Androi
Not sure I understand that. My manifest has three activities:
On Thu, Feb 2, 2012 at 7:32 PM, David Ross wrote:
> Are you saying that does not work?
It should not work, because the user can't add the app widget to bring
up the configuration activity in the first place. The app widget does
not appear in the launcher until the user has done something to bring
By the way, I went the "invisible instant Activity" path for the
Widget configuration because there are a number of horrible use-cases
with the Widget installation process that Android does not handle
properly and spending any time in the config activity can result in
bad things like ghost widgets
In my Widget I have a "dummy" configuration App that does as the
earlier poster said, it just runs, does some internal housekeeping
like setting up default preferences and returns the provided
AppWidgetId and RESULT_OK:
Intent resultValue = new Intent();
resultValue.putExtra(AppWid
On Thu, Feb 2, 2012 at 6:01 PM, phoku wrote:
> Is there anything new about this bug?
It is not a bug.
> I am developing a "widget-only" app,
You can no longer do that.
> i.e. I do not have any activity to present to the user. How can I allow him
> to add my widget without rebooting?
Put in an
Is there anything new about this bug? I am developing a "widget-only" app,
i.e. I do not have any activity to present to the user. How can I allow him
to add my widget without rebooting?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To
hi,
i solved this issue recently.
if you don't want to start with activity, you can hide an initial activity
with the source below.
1. add an android theme to hide
2. finish the activity as soon as it starts
and you can see the w
Thanks a lot. It helps much!
Adding an activity in Androidmanifest.xml like the following can solve
the problem?
Then does it mean that starting this widget incurs new InfoActivity
run at an initial start?
..
.
18 matches
Mail list logo
