Start with the app widget sample in API demos. If this isn't working, your
customized platform is broken.
On Wed, Aug 31, 2011 at 6:03 PM, eagle eagle.l...@gmail.com wrote:
Sorry for my English... What i mean is that, when i switch to
customized platform and are not using the private
On Wed, Aug 31, 2011 at 12:17 AM, eagle eagle.l...@gmail.com wrote:
But the problem is that, even I didn't use these private functions, it
didn't work.
I think you need to clarify your issue, because originally you said: But
when i switched to the standard platform, it worked
perfectly.
On Tue, Aug 30, 2011 at 10:17 PM, eagle eagle.l...@gmail.com wrote:
But the problem is that, even I didn't use these private functions,
it didn't work.
The article you linked is purely and solely about using internal functions.
If you are not using it and still having your problem, why did
Sorry for my English... What i mean is that, when i switch to
customized platform and are not using the private functions, the
program doesn't work (Even a Hello app widget program doesn't work).
The app widget with a configuration activity won't be added, while the
app widget without
But the problem is that, even I didn't use these private functions,
it didn't work.
On Aug 31, 10:27 am, Dianne Hackborn hack...@android.com wrote:
Your problem lies
here:http://devmaze.wordpress.com/2011/01/18/using-com-android-internal-pa...
Using private functions means you will randomly
Yeah thanks for your reply..and now my widget is no longer unavailable
after reboot the phone..thanks
On Aug 6, 4:11 am, Kevin TeslaCoil Software ke...@teslacoilsw.com
wrote:
Make sure you have:
android:installLocation=internalOnly
In your AndroidManifest.xml, Widgets don't work when
Make sure you have:
android:installLocation=internalOnly
In your AndroidManifest.xml, Widgets don't work when installed to the
sdcard.
Full example:
manifest xmlns:android=http://schemas.android.com/apk/res/android;
package=com.teslacoilsw.widgetlocker
android:versionCode=25001
I'm not sure if I made a mistake when I posted this, but it's currently only
receiving .BATTERY_CHANGED events despite being registered for these events:
-
action android:name=android.appwidget.action.APPWIDGET_UPDATE /
action android:name=android.bluetooth.adapter.action.STATE_CHANGED /
action
I have found the problem. The onEnabled event gets triggered at the start
when the first widget is added. The onDisabled event gets triggered when the
last widget is removed, but the onEnabled event does not get triggered when
you try to add another first widget.
I had code that was similar
I plan to show this message when the app detects it has been moved to the SD
card (i.e. the first time it runs after the event):
Android automatically disables homescreen widgets for apps that have been
moved to the SD card. If you would like to use widgets, then please move
this app back to
You could also consider separating widget from main app. having two apks you
could allow sd card for main user and keep widget plugin app on main memory.
depending on what your widget shows it may be the way to go
On Jun 16, 2011 9:33 AM, Mark Carter mjc1...@googlemail.com wrote:
I plan to show
Yes, I have considered that and may well end up taking that route. It's
messy though, whether it's a separate app in the Market or an APK downloaded
from my server (or even bundled as an asset in the main app).
Also the separation means you have to handle the scenario where the widget
app is an
Here's mine, being used in several apps now:
[app name]'s widgets are currently disabled because it has been installed to
SD card. To re-enable widgets, click App settings Move to phone, then
restart [app name].
Similar to yours, but I wanted to give (novice) users more explicit
instructions
I wanted to make clear this was an Android limitation rather than something
specific to the app.
I'm guessing most users would have manually moved the app to SD so they know
where to go. But maybe that's not right if the installLocation is auto?
Maybe it's enough to include a button (in the
Having been forced to enable install-to-SD for a couple of apps which
feature widgets, this is a bit of a sore spot with me. I say forced
because the average user doesn't understand the issues involved, only
understands that you (the dev) haven't enabled install-to-SD, so they
downrate you for
Thanks for the feedback.
On 31 May 2011 16:58, String sterling.ud...@googlemail.com wrote:
As a workaround, I'm currently in the process of implementing a warning of
my own in the app's main activity. It'll check to see if it's been installed
to SD, and if it has, issue a warning of its own.
On Tuesday, May 31, 2011 10:08:19 AM UTC+1, Mark Carter wrote:
What is the best way to check the app has been moved to SD?
http://developer.android.com/reference/android/content/pm/ApplicationInfo.html#FLAG_EXTERNAL_STORAGE
Thanks.
I wonder if it's possible to listen for a Move to SD event (is there a
broadcast intent?). If it were, then the app could at that moment raise a
notification warning the user that widgets would no longer be available.
On 31 May 2011 17:28, String sterling.ud...@googlemail.com wrote:
On
On Tuesday, May 31, 2011 10:51:30 AM UTC+1, Mark Carter wrote:
I wonder if it's possible to listen for a Move to SD event (is there a
broadcast intent?).
If there is, it's undocumented (or well hidden). The most likely looking
Intent in the docs is android.intent.action.PACKAGE_CHANGED, and
No commment on this topic?
Tom
On May 23, 9:16 pm, Tomáš Hubálek tom.huba...@gmail.com wrote:
Hello,
I followed widget definition guidelines described
athttp://developer.android.com/guide/topics/appwidgets/index.html#MetaData
and I suspect that formula for calculation of widget size
Where did you put those values of dimension?
it have to be on value folder, widget appwidget-provider xml
at what scale? dp ?
it works in other device?
maybe you have correctly created but the size of your widget Layout
not using the entire area...
On 23 maio, 16:16, Tomáš Hubálek
Thanks for your answer. Units are dip (not dp, I'll try to change dip to
dp).
According my observation this formula works well when widget's size is
bellow 5 icons.
The same behavior in emulator and on Acer Iconia Tab.
Tom
On Tue, May 24, 2011 at 9:30 PM, KlausSK8 klausmagalh...@gmail.com
I am looking for a technical answer, with a pointer to an API.
On Feb 17, 12:37 pm, TreKing treking...@gmail.com wrote:
On Thu, Feb 17, 2011 at 11:42 AM, Cheryl Sedota cherylsed...@gmail.comwrote:
I got an email from my Google partner advocate contact stating that basic
animations are
Actually, after playing with it a bit, I have determined that the
problem lies with installing the app on the SD card. Apparently the
card is not mounted in time during a reboot. I presume that it is
simply a bad idea to have a Widget that runs from the SC card, because
the user can unmount it
On Sat, Jan 15, 2011 at 8:30 PM, John Gaby jg...@gabysoft.com wrote:
Actually, after playing with it a bit, I have determined that the
problem lies with installing the app on the SD card.
http://developer.android.com/guide/appendix/install-location.html#ShouldNot
I presume that it is
simply
So, it's a
bit of a pain for all involved, but it would allow you to have the
main APK installable to the SD card.
You have to admit, that's not a reasonable expectation for the user
having to download a seperate app. It's an invitation to 1-stars (and
understandably so) if the user cannot
You have to admit, that's not a reasonable expectation for the user
having to download a seperate app. It's an invitation to 1-stars (and
understandably so) if the user cannot find the widget.
Yes, that is what I was thinking as well (I was asking if there was an
automatic way to install a
AppWidgetManager manager = AppWidgetManager.getInstance(Context);
Hope this solve your problem.
On Jan 11, 10:14 am, John Gaby jg...@gabysoft.com wrote:
I am trying to create an App Widget for the Home screen which displays
a line of text. When the user clicks on the Widget, I want the text to
AppWidgetManager manager = AppWidgetManager.getInstance(context);
That is exactly what I needed, thanks much!
On Jan 11, 12:21 am, Kostya Vasilyev kmans...@gmail.com wrote:
11.01.2011 5:14, John Gaby пишет:
I tried adding a class
member variable, 'm_appWidgetManager', which I set during
Broadcast receivers are only guaranteed to stay around long enough for
their onReceive to complete. They can be destroyed after that, and a new
instance will be created if needed later.
Given that it creates a new instance of my AppWidgeProvider class for
each call, is there a way to have
11.01.2011 23:10, John Gaby пишет:
Broadcast receivers are only guaranteed to stay around long enough for
their onReceive to complete. They can be destroyed after that, and a new
instance will be created if needed later.
Given that it creates a new instance of my AppWidgeProvider class for
Yes... that was it. I was comming on to update for the group because I
fixed it and saw your suggestion.
The main activity didn't have a finish() anywhere. I added an exit
button that called it and everything was good.
Thanks
On Jan 10, 11:51 pm, deeMurthy darshana.mur...@wipro.com wrote:
Hi
Hi Mike
You can call finish() at the end of your onCreate() method and check.
Otherwise, see what intent filters are given for your main activity in
the manifest file..it could be the culprit
Post your code around MikeIt will be easier for us to help!
Cheers!
On Jan 11, 2:24 am, BiiG
not sure I follow you here --
T-Mobile G1/G2 has the following specs -
320px x 480px (pixels)
1.77 x 2.65 (inches)
which gives about 181 dpi.
according to this --
http://developer.android.com/guide/practices/ui_guidelines/widget_design.html
4x1 widgets on T-Mobile G1 and G2 should be
Please read on screen density:
http://developer.android.com/guide/practices/screens_support.html
http://developer.android.com/guide/practices/screens_support.htmlJust
scale your coordinates based on the screen density. You can't assume some
specific size for some screen -- consider the
It seems that screen density alone is not sufficient to know what the
dimension should be; at some point aspect ratio has to come into
play. For example, I could have a screen that is the same screen
density as a T-Mobile G1, but twice has tall (physical screen size;
and 2x as many pixels in that
Did you read my second paragraph?
On Sun, Nov 1, 2009 at 10:57 AM, sdphil phil.pellouch...@gmail.com wrote:
It seems that screen density alone is not sufficient to know what the
dimension should be; at some point aspect ratio has to come into
play. For example, I could have a screen that is
yeah i did, but it wasn't much help, perhaps I didn't understand what
you were saying --
Just scale your coordinates based on the screen density.
That is what I was commenting on. Screen density does not seem
sufficient to me.
You can't assume some specific size for some screen -- consider the
That makes sense for portrait (480 / 320 = 1.5) but for fwvga in
landscape, 854 / 480 = 1.78.
On Oct 31, 10:55 am, Dianne Hackborn hack...@android.com wrote:
Multiply by 1.5.
On Sat, Oct 31, 2009 at 8:23 AM, sdphil phil.pellouch...@gmail.com wrote:
what are the 4x1 app widget sizes for WVGA
It's not the number of pixels, it's the density.
On Sat, Oct 31, 2009 at 12:10 PM, sdphil phil.pellouch...@gmail.com wrote:
That makes sense for portrait (480 / 320 = 1.5) but for fwvga in
landscape, 854 / 480 = 1.78.
On Oct 31, 10:55 am, Dianne Hackborn hack...@android.com wrote:
Multiply
Hi Lee,
Thanks for the information.
As my widget has progressed, I now have full caching for JPEG files as
I'm no longer reading from a local source and it's working fine. I'm
also loading a Bitmap rather than setting a Uri to them. Perhaps
there's some issue with using the resource ID in a
On my G1 it's not possible.
The standard G1's home screen rotates when you slide out the keyboard.
Right, thanks.
lilbyrdie, I can confirm that my caching solution also works when
the screen is rotated.
Lee
--~--~-~--~~~---~--~~
You received this message
Just a quick update: instead of using the application icon returned
from the PackageManager with views.setImageViewBitmap, I saved the
bitmap to a file and set it with views.setImageURI( /data/data/etc.../
z.png ).
That seems to have fixed my problem with icon disappearing after a few
minutes.
Hello, problem solved here, though not elegantly.
In case it helps, I discovered that at boot time the size of the
bitmap file was only 104 bytes
(and therefore probably other times it disappears). However, at widget
creation time the file
is always perfect. So I cache the file at
Also, I don't think this is related to the configuration issue
reported (and confirmed) here:
http://groups.google.com/group/android-developers/browse_thread/thread/869afdb312fc1e76/cb49f5e728430e75
But, if it is, that would be nice to know.
On Sep 1, 2:07 pm, Lee lee.wil...@googlemail.com
I'm using setImageViewResource.
I find it odd that it persists when an Alarm is set, but not when an
Alarm isn't set.
Are you saying that for your widget your aren't configuring an update
at all (e.g. just a static widget) via the widget configuration or
manually?
On Sep 1, 2:07 pm, Lee
On Sep 2, 3:19 pm, lilbyrdie kf6...@gmail.com wrote:
I'm using setImageViewResource.
Curses, I was hoping the Bitmap call that was the common culprit.
Guess I'll try storing the bitmap somewhere and using one of the other
calls anyway, will report back.
Are you saying that for your widget
Hello,
After an orientation change when the home screen redraws, the
ImageView doesn't always draw. The rest of the RemoteView does draw
just as it was set during the most recent Update.
I've just submitted a similar thread (hope it appears soon). As
with you, my ImageView is
AutoCompleteTextView cannot be used in widgets.
On Sat, May 2, 2009 at 10:07 AM, davidyu yule...@gmail.com wrote:
public class SearchWidget extends AppWidgetProvider {
@Override
public void onUpdate(Context context, AppWidgetManager
appWidgetManager,
int[]
49 matches
Mail list logo
