[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 Hackborn about this quirky behaviour at IO12, she indicated it was unknown behaviour and should be reported as a bug: https://code.google.com/p/android/issues/detail?id=33971 -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
2012/2/4 David Ross grand...@vacuumpunk.com: 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 broadcasts -- Lookout's Plan B app registered for just about all of them IIRC. As a result, malware taking the same approach could automatically get control, albeit after some delay. Now, you can argue that they took a shotgun approach to the problem, wiping out app widgets along the way. IMHO, app widgets should still show up, despite this stopped status, and if the user elects to install an app widget, it should move the app out of the stopped state. I don't own a 3.x or 4.x device and the 3.x emulator sucks, I can't get it to run on my modest laptop, so I have trouble even testing on the later platforms. The 4.x WVGA emulator should run approximately as quickly as the Android 2.3 emulator. It's the tablet screen sizes that are the problem, much more so than the Android version. In fact, aside from that mention you linked to of an Application's state as stopped or started, there seems to be no real explanation of this behaviour at the Application level anywhere in the developer documentation. How are we supposed to know and understand this sort of undocumented behaviour? Ask questions, and let those of us who have crawled on the broken glass already help point out, Yo! There's broken glass down here! And, um, by the way, do you have any disinfectant, and maybe some bandages? -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 4.1 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 version past 2.2. I can't keep an ICE emulator running for more than a few minutes if I'm actually trying to do any work with it; pseudo-random reboots are the order of the day. I long since came to believe that nobody at Google actually uses the emulator; they have too much access to the latest hardware. If they had to dogfood it, I can't believe it'd be in the state it is. String -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 this by providing an activity that the user can launch from Launcher. This is not the same as the widget config activity. -- Kostya 4 февраля 2012 г. 5:30 пользователь David Ross grand...@vacuumpunk.comнаписал: 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 presto, it's there! No need to launch the App for it to be available as a Widget. The Android install process parses the manifest and places the new widget in the list of available Widgets without having to be launched first. And while you need to have the configuration Activity in the manifest and the widget config file, that Activity does not have to do anything at all really, you can just return RESULT_OKAY and handle the widget configuration in your WidgetProvider onEnabled() and onUpdate() when you get the APPWIDGET_xxx Intents. Has that changed in 3.0+? Am I missing something here? As I said before, this approach handles the bad use-cases that Android does not handle cleanly. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 in the release note you linked to. I don't own a 3.x or 4.x device and the 3.x emulator sucks, I can't get it to run on my modest laptop, so I have trouble even testing on the later platforms. I don't want my user to access functionality from the launcher at all, I want them to only access functionality from the Widget. All my Launcher Activity does is display a splash screen telling the user how to install the Widget. What was wrong with the old behaviour? Why not allow an installed application with a Widget be installed as Widget without Launching an Activity first? It makes no sense to me. In fact, aside from that mention you linked to of an Application's state as stopped or started, there seems to be no real explanation of this behaviour at the Application level anywhere in the developer documentation. How are we supposed to know and understand this sort of undocumented behaviour? Anyway, thanks for the info. On Feb 4, 7:40 pm, Kostya Vasilyev kmans...@gmail.com wrote: 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 this by providing an activity that the user can launch from Launcher. This is not the same as the widget config activity. -- Kostya 4 февраля 2012 г. 5:30 пользователь David Ross grand...@vacuumpunk.comнаписал: 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 presto, it's there! No need to launch the App for it to be available as a Widget. The Android install process parses the manifest and places the new widget in the list of available Widgets without having to be launched first. And while you need to have the configuration Activity in the manifest and the widget config file, that Activity does not have to do anything at all really, you can just return RESULT_OKAY and handle the widget configuration in your WidgetProvider onEnabled() and onUpdate() when you get the APPWIDGET_xxx Intents. Has that changed in 3.0+? Am I missing something here? As I said before, this approach handles the bad use-cases that Android does not handle cleanly. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
On Thu, Feb 2, 2012 at 8:53 PM, David Ross grand...@vacuumpunk.com 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/LAUNCHER activity. You are welcome to provide source code to a sample project that demonstrates this effect. I guess what you mean is that the system must first run the invisible do-nothing activity of .WidgetDummyInstall in order for the manifest contents to be registered with the system which then means the Widget will be entered into the list of available Widgets? No, I mean that the user must tap on your WidgetDummyConfiguration icon in the launcher so that the Widget will be entered into the list of available Widgets. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 presto, it's there! No need to launch the App for it to be available as a Widget. The Android install process parses the manifest and places the new widget in the list of available Widgets without having to be launched first. And while you need to have the configuration Activity in the manifest and the widget config file, that Activity does not have to do anything at all really, you can just return RESULT_OKAY and handle the widget configuration in your WidgetProvider onEnabled() and onUpdate() when you get the APPWIDGET_xxx Intents. Has that changed in 3.0+? Am I missing something here? As I said before, this approach handles the bad use-cases that Android does not handle cleanly. On Feb 3, 9:01 pm, Mark Murphy mmur...@commonsware.com wrote: On Thu, Feb 2, 2012 at 8:53 PM,DavidRossgrand...@vacuumpunk.com 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/LAUNCHER activity. You are welcome to provide source code to a sample project that demonstrates this effect. I guess what you mean is that the system must first run the invisible do-nothing activity of .WidgetDummyInstall in order for the manifest contents to be registered with the system which then means the Widget will be entered into the list of available Widgets? No, I mean that the user must tap on your WidgetDummyConfiguration icon in the launcher so that the Widget will be entered into the list of available Widgets. -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 after starting the download/install process, the Market posts a Notification where it will automatically launch the App if the user taps the Notification. That's what I meant by downloaded and run. But my point was that it only has to be installed for it to appear in the list of Widgets available from the home screen long- press dialogs. On Feb 3, 3:54 pm, phoku mboeh...@fh-muenster.de wrote: 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 Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
On Thu, Feb 2, 2012 at 6:01 PM, phoku mboeh...@fh-muenster.de 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 activity to present to the user. This is unavoidable, AFAICT, on Android 3.1+. You will need it at first install, and you will need it if the user elects to force-stop your application. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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(AppWidgetManager.EXTRA_APPWIDGET_ID, appWidgetId); setResult(RESULT_OK, resultValue); It does not even inflate a layout, after setting the result it does a finish(). It is an invisible configuration activity so that the user gets the effect of the Widget appearing instantly after selecting it for installation. Are you saying that does not work? On Feb 3, 7:06 am, Mark Murphy mmur...@commonsware.com wrote: On Thu, Feb 2, 2012 at 6:01 PM, phoku mboeh...@fh-muenster.de 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 activity to present to the user. This is unavoidable, AFAICT, on Android 3.1+. You will need it at first install, and you will need it if the user elects to force-stop your application. -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 (two types of ghost, one is where the OS thinks the widget is there but it is not, the other is where my App thinks the widget is there but is it not). These can be caused by things like not enough home screen space or unintented power down (eg battery fail) before the config activity returns the RESULT_OK. It took quite some time to nut out these rare use-cases. On Feb 3, 8:32 am, David Ross grand...@vacuumpunk.com wrote: 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(AppWidgetManager.EXTRA_APPWIDGET_ID, appWidgetId); setResult(RESULT_OK, resultValue); It does not even inflate a layout, after setting the result it does a finish(). It is an invisible configuration activity so that the user gets the effect of the Widget appearing instantly after selecting it for installation. Are you saying that does not work? On Feb 3, 7:06 am, Mark Murphy mmur...@commonsware.com wrote: On Thu, Feb 2, 2012 at 6:01 PM, phoku mboeh...@fh-muenster.de 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 activity to present to the user. This is unavoidable, AFAICT, on Android 3.1+. You will need it at first install, and you will need it if the user elects to force-stop your application. -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
On Thu, Feb 2, 2012 at 7:32 PM, David Ross grand...@vacuumpunk.com 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 your app out of the stopped state, such as launching an activity of yours from the launcher. It appears as though a reboot might also allow the app widget to show in the launcher, though I have not played with this scenario. A reboot definitely does not generally allow stopped apps to respond to broadcasts, though. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.4 Available! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
Not sure I understand that. My manifest has three activities:
activity
android:label=@string/app_name
android:name=.WidgetDummyConfiguration
intent-filter
action
android:name=android.intent.action.MAIN /
category
android:name=android.intent.category.LAUNCHER /
/intent-filter
/activity
activity
android:label=@string/app_name
android:name=.WidgetConfiguration
intent-filter
action android:name=android.intent.action.MAIN/
data android:scheme=com.vacuumpunk.CDTBD2012 /
category
android:name=android.intent.category.DEFAULT /
/intent-filter
/activity
activity
android:label=@string/app_name
android:name=.WidgetInstall
intent-filter
action
android:name=android.appwidget.action.APPWIDGET_CONFIGURE /
category
android:name=android.intent.category.DEFAULT /
/intent-filter
/activity
The Activity WidgetDummyConfiguration is called when the APK has been
downloaded from the market and run. It does nothing (literally) - the
onCreate() method has only two lines of code:
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
finish();
}
The .WidgetInstall Activity is referenced in the widget config file
pointed to in the Manifest:
appwidget-provider
xmlns:android=http://schemas.android.com/apk/res/android;
android:minWidth=294dp
android:minHeight=146dp
android:initialLayout=@layout/widget
android:configure= com.vacuumpunk.CDTBD2012.WidgetInstall
/
When the user installs the Widget on the home screen, the
Activity .WidgetInstall is used and again it is invisible, but it does
do some setting up of default preferences and then just calls
finish(). That's to handle the bad use-cases that Android doesn't
handle so well.
My AppWidgetProvider then registers a PendingIntent on the click
listener for the RemoteView which fires up the third activity
(.WidgetConfiguration) which is the business part of the UI behind the
widget.
I guess what you mean is that the system must first run the invisible
do-nothing activity of .WidgetDummyInstall in order for the manifest
contents to be registered with the system which then means the Widget
will be entered into the list of available Widgets?
In my production code I actually present a basic dialog when the App
is run that explains how to install the Widget and then exits. The
user can only access my App's functionality via a home screen Widget.
On Feb 3, 8:42 am, Mark Murphy mmur...@commonsware.com wrote:
On Thu, Feb 2, 2012 at 7:32 PM, David Ross grand...@vacuumpunk.com 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
your app out of the stopped state, such as launching an activity of
yours from the launcher.
It appears as though a reboot might also allow the app widget to show
in the launcher, though I have not played with this scenario. A reboot
definitely does not generally allow stopped apps to respond to
broadcasts, though.
--
Mark Murphy (a Commons
Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
_The Busy Coder's Guide to *Advanced* Android Development_ Version 2.4
Available!
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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? .. activity android:name=.InfoActivity android:label=@string/title_info intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / /intent-filter /activity .. Regards, Jaeyun On Nov 4, 9:25 pm, Mark Murphy mmur...@commonsware.com wrote: On Fri, Nov 4, 2011 at 2:32 AM,sincere6metal...@gmail.com wrote: I developed the widget app that runs on honeycomb OS. (Actually the hardware is Samsung Galaxy Tab.) When I installed the developed widget, it should be in the list of runnable widget list by pressing desktop screen for a few seconds. But it's not. Correct. Only the OS reboot solves the problem. Actually, I am surprised that solves the problem. Another solution is for the user to run an activity associated with your app, at least in my experience. BTW, when I installed the same widget into the mobile phone whose OS is froyo, it goes into the runnable widget list instantly. Any clue or hint on this problem? With Android 3.1+, applications are installed in a stopped state. Among other things, they will not receive broadcast Intents until they are moved out of this state. The only way I know of to do this is to launch an activity associated with the application. In particular, at least for ACTION_BOOT_COMPLETED, a reboot was insufficient. I was just experimenting with app widgets and 3.2/4.0 yesterday (XOOM and emulator, respectively). I encountered the same issue of not seeing the app widgets available for adding to the home screen. Once I launched an activity associated with the app, the app widgets appeared. -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Newly installed widgets are not runnable on Honeycomb
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 activity android:name=.InfoActivity * android:theme=@android:style/Theme.Holo.Light.Panel * android:label=@string/title_info intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / /intent-filter /activity 2. finish the activity as soon as it starts and you can see the widget in the list after the first installation. 2011/11/10 Jaeyun Noh metal...@gmail.com 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? .. activity android:name=.InfoActivity android:label=@string/title_info intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / /intent-filter /activity .. Regards, Jaeyun On Nov 4, 9:25 pm, Mark Murphy mmur...@commonsware.com wrote: On Fri, Nov 4, 2011 at 2:32 AM,sincere6metal...@gmail.com wrote: I developed the widget app that runs on honeycomb OS. (Actually the hardware is Samsung Galaxy Tab.) When I installed the developed widget, it should be in the list of runnable widget list by pressing desktop screen for a few seconds. But it's not. Correct. Only the OS reboot solves the problem. Actually, I am surprised that solves the problem. Another solution is for the user to run an activity associated with your app, at least in my experience. BTW, when I installed the same widget into the mobile phone whose OS is froyo, it goes into the runnable widget list instantly. Any clue or hint on this problem? With Android 3.1+, applications are installed in a stopped state. Among other things, they will not receive broadcast Intents until they are moved out of this state. The only way I know of to do this is to launch an activity associated with the application. In particular, at least for ACTION_BOOT_COMPLETED, a reboot was insufficient. I was just experimenting with app widgets and 3.2/4.0 yesterday (XOOM and emulator, respectively). I encountered the same issue of not seeing the app widgets available for adding to the home screen. Once I launched an activity associated with the app, the app widgets appeared. -- Mark Murphy (a Commons Guy)http://commonsware.com| http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
