[android-developers] Sent SMS doesn't show up in the messaging app?
When using the conventional means to programatically send an SMS TXT message, does anyone understand why there is no history of the outbound message in the MESSAGING App? thanks, tob -- 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: Sent SMS doesn't show up in the messaging app?
I agree. Thanks.
*but* (you saw that coming right? ;)
It seems that for such an overbearing application such as a
MESSAGING app that (a) you can't delete and (b) you can even disable
(you know the green square boxy looking thing?) it seems that it would
have grabbed the outbound intent as well as any inbound.
{And please excuse me if there is some mysterious way to delete the
thing...}
On Jul 12, 3:15 pm, Mark Murphy mmur...@commonsware.com wrote:
On Tue, Jul 12, 2011 at 3:12 PM, tony obrien tobsourcecode...@gmail.com
wrote:
When using the conventional means to programatically send an SMS TXT
message, does anyone understand why there is no history of the
outbound message in the MESSAGING App?
First, there is no single MESSAGING App.
Second, since the MESSAGING App did not send the SMS, it should not
show up as an outbound message, any more than sending email through a
Yahoo Mail account should show up as an outbound message in Gmail.
--
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
[android-developers] Goo Market Frustration(s) -- a request to experienced app developers
HI,
I have several applications available for d/l. They involve
complicated use of the OS's facilities (GPS, SMS TXT, display
manipulations, etc.)
I have them tested on a Motorola DROID, and an LG ALLY, as well as a
few others through family and friends (otherwise known as beta
testers ;)
I was going to say, So if I can't test on EVERY device... but
perhaps that's my first question...
{a} Was I absent the day they told us in Android SDK class that any
actual DEVICE may react differently from some other? I understand that
if the device does not support somthing then, of course, it can't
comply to my app's request.
Example: I have 100's of downloads for an app... then I get a 1-STAR
with the comment: Does not work on HERO.
So I can imagine that he may be right OR he might be a twit and many
others with HEROs had no problem.
I find the communications facilities between the DEVELOPER and his
AUDIENCE via the GOO Market to be quite unsophisticated.
So...
{b} Is there some mechanism that I am not aware of that allows me to
'confront' my downloaders directly (i.e. an email address or
something?) so that I can help them or at least discover what the heck
someone means by It don't work ??
At the moment I am planning on adding an entire new layout to all of
my apps which would beg them to get in touch with me if they have
*any* problem at all ... is this my only means to accomplish this?
thanks,
tob
--
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: The Market App has a CACHE !
Doug, Greg... I've calmed quite a bit ;) As a (new android market) developer, I was making updates and expecting that the latest would always be the one coming down for me to verify. Now that I've 'institutionalized' my release process with scripts, etc. *and* understand what the heck was going on, I am feeling a lot better ! Between the manifest code version string(s), signing an unsigned APK (heck, just creating an unsigned APK in Netbeans -- don't get me started ; I was concerned that any number of steps could have been screwed up, and that was why I wasn't seeing my updates... But all is good now. Information is calming. Thanks -- c-ya 'round the water cooler. tob -- 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: The Market App has a CACHE !
For those thinking I meant a BROWSER's cache -- perhaps I was not clear... I meant that on the PHONE,the MARKET APPLICATION has a cache. (Settings = Applications = Manage Applications = Menu: Show ALL = Choose MARKET. You'll see a button to CLEAR CACHE. And my point is -- why would the designers of that APP use a cache? It doesn't 'minimize network traffic' since it always seems to go up to the net anyway to do a D/L but (perhaps maybe) its not REALLY going out to the net, since it will load from that cache instead; as both Zarah and I discovered. And having to either KILL the MARKET app on the device, or Clear its' cache still confounds me as to why it has one at all. If the thing is smart enough to know when an update is ready, why isn't it smart enough to know that its' cache is stale? tob -- 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: The Market App has a CACHE !
OK, I'll concede that the cache is useful for the WEB (or web-like)
aspects of the MARKET app -- but (it still) seems to me that if its
MAIN FUNCTION is to provide d/l of apps, then those app 'references'
should not be cached but should always be refreshed.
On Oct 4, 9:30 am, { Devdroid } webnet.andr...@gmail.com wrote:
On 4 October 2010 14:32, tony obrien tobsourcecode...@gmail.com wrote:
And my point is -- why would the designers of that APP use a cache?
It doesn't 'minimize network traffic' since it always seems to go up
to the net anyway to do a D/L
Cache in Market app does reduce network traffic.
And having to either KILL the MARKET app on the device, or Clear its'
cache still confounds me as to why it has one at all.
If the thing is smart enough to know when an update is ready, why
isn't it smart enough to know that its' cache is stale?
You do not have to do that. Sparringly Market may lag a bit
when you update anything, but it does not last too long.
--
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] The Market App has a CACHE !
Hi,
I just spent 2 hours in a minor panic because of this.
I had a small update to put out (and, yes, I AM new to this Market
stuff), so I update the Manifest to reflect the version upgrade, I
build the APK, and sign it, and do the 'upgrade' via the Console.
I then go to my phone, UNINSTALL my app ( this is, I'm guessing the
{mea culpa} mistake ) and fire up the Market app. Find my app, and d/l
and install -- its the OLD stuff. Huh?
I d/l again... no joy. What? ? ?
I go through the entire (build) process again --- with *exactly* the
same result; no updated app on my phone.
(So, those of you in the know, are probably either LOL-ing, or hmmph-
ing)
Then (as I carefully) review the Market's presentation of my app on
the device, I see that the version number HAS NOT CHANGED! So, now I
am *really* confused. Why is the MARKET App showing me an older
version?
I start to think that maybe perhaps its possible that they don't make
updates immediately available - or something. But I'm also thinking
that that make NO Sense to me; I gotta be doing something wrong.
I google around and discover that the MARKET app has a cache -- which,
IMHO, makes little sense.
Why do I think that? Because if the MARKET app ALWAYS appears to be
going out to the internet to D/L (i.e. fancy d/l graphics in the
notification area) whats the purpose of the cache? And why would
anyone ever think they they have to go clear it to ensure they get the
latest stuff in the d/l??
The idea of a cache in this instance seems to save no time (as its
purported to do for web PAGES), and does exactly the wrawng thingh.
Or is it just me?
--
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: (EDITED by author) My app gets killed ... but I think I know why now
(Good Morning)
Oh but you see, in fact, that's JUST WHAT THEY WANT... and is the
whole purpose of the application ;)
Its funny because as I've endeavored to bring my app to life; most of
what I need to do flies in the face of 'proper' etiquette; as you have
surmised. But it is just the ability to do these sorts of things
that originally brought me to Android. I looked into iPhone first and
there were 2 issues I had with that camp. {a} There was NO WAY to
accomplish most of what I needed to do since the SDK developers
decided to protect me from myself. and {b} I was amazed at how
hostile the developers group members were.
soapbox
I have been writing code for 30 years and I, too, get frustrated by
questions brought by developers that have obviously spent ZERO time
experimenting or trying stuff out... they want it all just handed to
them. But over in iPhone Developer Land --- they seem to prefer
battling why 'MY TECHNIQUE' is better than 'YOUR TECHNIQUE' and get
all medieval on the lowly guy just starting out trying to even
understand what techniques are available to him... and in my
particular case, the notion of my code's etiquette was just
S upsetting that they berated me instead of offering *any*
advice.
anyway ...
/soapbox
I found a code snip that illustrates how to start a new activity from
inside a BR -- and your point regarding specific naming of the
'context object' was used -- so, once again, I commend your expertise.
I think this is going to be the solution to all my problems (well,
except for that minor traffic altercation in Dubai ;)
Thanks a lot (and again) for all of your help...
On Sep 11, 5:36 pm, Kostya Vasilyev kmans...@gmail.com wrote:
Tony,
Your receiver is getting called - that's good. Can't comment on
notifications without seeing the code.
There should not be any reason why startActivity from within onReceive
wouldn't work (use the context object that's passed into onReceive to fix
the compile error you mentioned), but I don't think your users are going to
appreciate a window popping up like that.
--
Kostya Vasilyev --http://kmansoft.wordpress.com
12.09.2010 1:10 пользователь tony obrien tobsourcecode...@gmail.com
написал:
Actually I have LOGGING all over the place.
I was able to determine that the SMS Receiver is actually getting
called ... but it has trouble doing the NM.Notify(); (I'm still
trying to decode what *that* error is all about...)
And I have Thread.sleep(lots-o'seconds) and Thread.yeild() in the
runnable so I am being careful regarding your concerns.
What I would REALLY like to do is a startActivity() from inside the
Receiver... but I don't suppose that's possible? (In my first timid
attempts to do that awhile ago I could not get it to compile, I think
the extends BroadcastReceiever makes the compiler not understand
what startActivity() means.)
On Sep 11, 5:02 pm, Kostya Vasilyev kmans...@gmail.com wrote:
12.09.2010 0:37, tony obrien ...
--
You received this message because you are subscribed to the Google
Groups Android Developers g...
--
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] (EDITED by author) My app gets killed ... but I think I know why now
I think I have discovered the reason for my troubles. I also think
that the relationship to the media process was incidental.
What I really think is going on is related to the OS reclaiming
memory.
When I leave my app in the foreground (i.e. visible) it works (and It
Won't Die, Jim) -- if I use the BACK BUTTON to push it into the
background, it *may* die, and I am convinced it is at the hands of the
OS in its memory reclamation process… I assert this as my experiments
have shown that on a device with LOTS O' memory the app works
flawlessly… on a device with less memory it will almost certainly die
and I can guarantee to kill it if I start using the devices other
apps.
The rub here is that I NEED my app to reside in the background (or at
least my SMS BROADCAST RECEIVER class) .. I want the user to be able
to use his phone for other things while my app awaits a signaling
SMS. At that point I use a notification to get the user's attention.
I am hoping someone may respond and say … Well, all-you-gotta-do is
Blah_Blah… Is there a way to make the OS not clean me out of
memory? Is the answer to make the b-receiver a service? And is that
allowable in Android?
On Sep 6, 10:56 am, tony obrien tobsourcecode...@gmail.com wrote:
Hi,
I have seen one reference to this sort of problem where a MAIN app
dies because :::
because provider com.android.providers.media.MediaProvider is in
dying process android.process.media
In that reference the implication was that if you held a CURSOR too
long this could happen.
I am not using any explicit cursor, but maybe there is an implied one
somehere?
Hopefully these code snips will provide someone enough incite to offer
a solution.
I use a RINGTONE PICKER ==
String uri = null;
Intent intent = new
Intent( RingtoneManager.ACTION_RINGTONE_PICKER);
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_TYPE,
RingtoneManager.TYPE_NOTIFICATION);
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_TITLE, Select Tone);
if( uri != null)
{
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_EXISTING_URI,
Uri.parse( uri));
}
else
{
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_EXISTING_URI,
(Uri)null);
}
startActivityForResult( intent,
Set_Ringtone);
And catch the result
@Override
public void onActivityResult(int reqCode, int resultCode, Intent
data) {
super.onActivityResult(reqCode, resultCode, data);
if (resultCode == RESULT_OK) {
Uri uri =
data.getParcelableExtra(RingtoneManager.EXTRA_RINGTONE_PICKED_URI);
if (uri != null) {
MainActivity.ringTonePath = uri.toString();
}
}
}
At some time later, I call a sound class to play the selected
ringtone :::
Ringtone myr = RingtoneManager.getRingtone(context,
Uri.parse( MainActivity.ringTonePath));
if (MainActivity.doDebug) Log.d(FPH, clsSound:Play
RINGTONE);
myr.play();
return;
This is called repeatedly while a flag is TRUE (until the user sets it
FALSE)
At this point the App is sitting essentially idle --- and if the
android.process.media dies (say by force) then so do I. But I do not
understand why I should die.
Any ideas?
thanks,
tob
--
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: (EDITED by author) My app gets killed ... but I think I know why now
Thanks, but I already HAVE such a thing in my Manifest... I suppose that my BR intent *could be* lurking while my MAIN dies... but then why doesn't the MAIN get REStarted when the BR starts updating Main's (static) variables ? Main is *not* starting and so its just as if the SMS was never received... any ideas? On Sep 11, 3:02 pm, Kostya Vasilyev kmans...@gmail.com wrote: Well, all-you-gotta-do is: Register your receiver in the manifest, like so: receiver android:name=.YourSmsMessageReceiverClassName intent-filter action android:name=android.provider.Telephony.SMS_RECEIVED / /intent-filter /receiver ( Taken from:http://developer.android.com/resources/samples/ApiDemos/AndroidManife... ) Receivers declared in the manifest are active all the time, for as long as the application is installed (and not disabled in the manifest). You don't need to take any kind of special action for them to receive events. In the onReceive() method of your broadcast receiver, you are free to do whatever you like: such as starting a service to do some kind of processing (I actually recommend this). The application process will be started by Android as necessary. -- Kostya 11.09.2010 22:25, tony obrien пишет: I am hoping someone may respond and say … Well, all-you-gotta-do is Blah_Blah… Is there a way to make the OS not clean me out of memory? Is the answer to make the b-receiver a service? And is that allowable in Android? -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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: (EDITED by author) My app gets killed ... but I think I know why now
One more thing ... if I happen to be in the NetBeans IDE / Debugger I can be at a breakpoint and (all of a sudden) its been knocked out of debugging mode -- i.e. the App really has died On Sep 11, 3:37 pm, tony obrien tobsourcecode...@gmail.com wrote: Thanks, but I already HAVE such a thing in my Manifest... I suppose that my BR intent *could be* lurking while my MAIN dies... but then why doesn't the MAIN get REStarted when the BR starts updating Main's (static) variables ? Main is *not* starting and so its just as if the SMS was never received... any ideas? On Sep 11, 3:02 pm, Kostya Vasilyev kmans...@gmail.com wrote: Well, all-you-gotta-do is: Register your receiver in the manifest, like so: receiver android:name=.YourSmsMessageReceiverClassName intent-filter action android:name=android.provider.Telephony.SMS_RECEIVED / /intent-filter /receiver ( Taken from:http://developer.android.com/resources/samples/ApiDemos/AndroidManife... ) Receivers declared in the manifest are active all the time, for as long as the application is installed (and not disabled in the manifest). You don't need to take any kind of special action for them to receive events. In the onReceive() method of your broadcast receiver, you are free to do whatever you like: such as starting a service to do some kind of processing (I actually recommend this). The application process will be started by Android as necessary. -- Kostya 11.09.2010 22:25, tony obrien пишет: I am hoping someone may respond and say … Well, all-you-gotta-do is Blah_Blah… Is there a way to make the OS not clean me out of memory? Is the answer to make the b-receiver a service? And is that allowable in Android? -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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: (EDITED by author) My app gets killed ... but I think I know why now
Understood (and thanks for the in-depth response !) I had already run into (and repaired) the case where I was sitting around too long. And so now, I will try the NOTIFICATION route since I successfully use that elsewhere... Hopefully I can reawaken the MAIN activity and gather up the STATICs (and I made them static just for the reason you explain) and have my UI aspects offer the correct choices to my user. thanks, again. On Sep 11, 4:09 pm, Kostya Vasilyev kmans...@gmail.com wrote: Tony, Android apps are composed of individual components - activities, services, broadcast receivers, etc. Their lifetimes are managed by Android in response to events that are relevant for a particular type of component. http://developer.android.com/guide/topics/fundamentals.html#appcomp A broadcast receiver getting an event does not mean that some or other activity or a service should be started automatically, just because it's a component of the same application. After all, you wouldn't want all activities declared within your application to be invoked at once, right? Same with other component types. Each does its own thing, and they are glued together by the code you write. The issue with debugging a broadcast receiver is that Android limits the amount of time that an application can take in its callbacks (broadcast receiver's onReceive, activity lifecycle callbacks such as onStart, etc.) If you take too long in the debugger, Android kills the process thinking it's not responding. My suggestion is to add logging calls (using Android's built-in log class) to your receiver's onReceive, verify that does get called, and take it from there. http://developer.android.com/reference/android/util/Log.html If you would like to notify the user that an SMS has been received, you have two options: - Start an activity using Context.startActivity - which is what you seem to be trying to do, but which is considered in Android to be bad user experience. - Use a status bar notification, which would in turn launch the activity to show the message: http://developer.android.com/guide/topics/ui/notifiers/notifications Finally, as for statics - this is a Java thing. Static members are, by definition, independent of any particular instance of the class they are declared in. Hope this helps, -- Kostya 11.09.2010 23:40, tony obrien пишет: One more thing ... if I happen to be in the NetBeans IDE / Debugger I can be at a breakpoint and (all of a sudden) its been knocked out of debugging mode -- i.e. the App really has died On Sep 11, 3:37 pm, tony obrientobsourcecode...@gmail.com wrote: Thanks, but I already HAVE such a thing in my Manifest... I suppose that my BR intent *could be* lurking while my MAIN dies... but then why doesn't the MAIN get REStarted when the BR starts updating Main's (static) variables ? Main is *not* starting and so its just as if the SMS was never received... any ideas? On Sep 11, 3:02 pm, Kostya Vasilyevkmans...@gmail.com wrote: Well, all-you-gotta-do is: Register your receiver in the manifest, like so: receiver android:name=.YourSmsMessageReceiverClassName intent-filter action android:name=android.provider.Telephony.SMS_RECEIVED / /intent-filter /receiver ( Taken from:http://developer.android.com/resources/samples/ApiDemos/AndroidManife... ) Receivers declared in the manifest are active all the time, for as long as the application is installed (and not disabled in the manifest). You don't need to take any kind of special action for them to receive events. In the onReceive() method of your broadcast receiver, you are free to do whatever you like: such as starting a service to do some kind of processing (I actually recommend this). The application process will be started by Android as necessary. -- Kostya 11.09.2010 22:25, tony obrien пишет: I am hoping someone may respond and say … Well, all-you-gotta-do is Blah_Blah… Is there a way to make the OS not clean me out of memory? Is the answer to make the b-receiver a service? And is that allowable in Android? -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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: (EDITED by author) My app gets killed ... but I think I know why now
Well, that was a bust ...
I am pretty sure that *my* BR is not getting called... pls check my
work::
This is the Manifest = (assume the correct permissions in that I do
get the SMS when this is working in the foreground)
receiver android:name=.clsSMSRCV
intent-filter
action
android:name=android.provider.Telephony.SMS_RECEIVED /
/intent-filter
/receiver
My MAINACTIVITY declares the BR as so...
private clsSMSRCV myClsSMSRCV;
and then in the MainActivity.onCreate() ==
myClsSMSRCV = new clsSMSRCV();
This is the clsSMSRCV definition with the receive override:
public class clsSMSRCV extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
// I tear apart the SMS message(s) here... and alter Statics for
review outside this routine
}
}
One last thing, I can think of...
Main has a runnable which is essentially monitoring the Statics and so
can then act upon them changing in ClsSMSRCV.
In my last experiment I had the onReceive() try to express a
Notification nuttin happened.
On Sep 11, 4:21 pm, tony obrien tobsourcecode...@gmail.com wrote:
Understood (and thanks for the in-depth response !)
I had already run into (and repaired) the case where I was sitting
around too long.
And so now, I will try the NOTIFICATION route since I successfully use
that elsewhere...
Hopefully I can reawaken the MAIN activity and gather up the STATICs
(and I made them static just for the reason you explain) and have my
UI aspects offer the correct choices to my user.
thanks, again.
On Sep 11, 4:09 pm, Kostya Vasilyev kmans...@gmail.com wrote:
Tony,
Android apps are composed of individual components - activities,
services, broadcast receivers, etc. Their lifetimes are managed by
Android in response to events that are relevant for a particular type of
component.
http://developer.android.com/guide/topics/fundamentals.html#appcomp
A broadcast receiver getting an event does not mean that some or other
activity or a service should be started automatically, just because it's
a component of the same application.
After all, you wouldn't want all activities declared within your
application to be invoked at once, right? Same with other component
types. Each does its own thing, and they are glued together by the code
you write.
The issue with debugging a broadcast receiver is that Android limits the
amount of time that an application can take in its callbacks (broadcast
receiver's onReceive, activity lifecycle callbacks such as onStart,
etc.) If you take too long in the debugger, Android kills the process
thinking it's not responding.
My suggestion is to add logging calls (using Android's built-in log
class) to your receiver's onReceive, verify that does get called, and
take it from there.
http://developer.android.com/reference/android/util/Log.html
If you would like to notify the user that an SMS has been received, you
have two options:
- Start an activity using Context.startActivity - which is what you seem
to be trying to do, but which is considered in Android to be bad user
experience.
- Use a status bar notification, which would in turn launch the activity
to show the message:
http://developer.android.com/guide/topics/ui/notifiers/notifications
Finally, as for statics - this is a Java thing. Static members are, by
definition, independent of any particular instance of the class they are
declared in.
Hope this helps,
-- Kostya
11.09.2010 23:40, tony obrien пишет:
One more thing ... if I happen to be in the NetBeans IDE /
Debugger I can be at a breakpoint and (all of a sudden) its been
knocked out of debugging mode -- i.e. the App really has died
On Sep 11, 3:37 pm, tony obrientobsourcecode...@gmail.com wrote:
Thanks, but I already HAVE such a thing in my Manifest...
I suppose that my BR intent *could be* lurking while my MAIN dies...
but then why doesn't the MAIN get REStarted when the BR starts
updating Main's (static) variables ? Main is *not* starting and so
its just as if the SMS was never received...
any ideas?
On Sep 11, 3:02 pm, Kostya Vasilyevkmans...@gmail.com wrote:
Well, all-you-gotta-do is:
Register your receiver in the manifest, like so:
receiver android:name=.YourSmsMessageReceiverClassName
intent-filter
action android:name=android.provider.Telephony.SMS_RECEIVED /
/intent-filter
/receiver
( Taken
from:http://developer.android.com/resources/samples/ApiDemos/AndroidManife...
)
Receivers declared in the manifest are active all the time, for as long
as the application is installed (and not disabled in the manifest). You
don't need to take any kind of special action for them to receive
events.
In the onReceive() method of your broadcast receiver, you are free to do
whatever you like
[android-developers] Re: (EDITED by author) My app gets killed ... but I think I know why now
Actually I have LOGGING all over the place.
I was able to determine that the SMS Receiver is actually getting
called ... but it has trouble doing the NM.Notify(); (I'm still
trying to decode what *that* error is all about...)
And I have Thread.sleep(lots-o'seconds) and Thread.yeild() in the
runnable so I am being careful regarding your concerns.
What I would REALLY like to do is a startActivity() from inside the
Receiver... but I don't suppose that's possible? (In my first timid
attempts to do that awhile ago I could not get it to compile, I think
the extends BroadcastReceiever makes the compiler not understand
what startActivity() means.)
On Sep 11, 5:02 pm, Kostya Vasilyev kmans...@gmail.com wrote:
12.09.2010 0:37, tony obrien пишет: Well, that was a bust ...
I am pretty sure that*my* BR is not getting called... pls check my
work::
This is the Manifest = (assume the correct permissions in that I do
get the SMS when this is working in the foreground)
receiver android:name=.clsSMSRCV
intent-filter
action
android:name=android.provider.Telephony.SMS_RECEIVED /
/intent-filter
/receiver
Looks good. Assuming that your tags are nested correctly (receiver
should be inside application), and that you also have this at the end
of the manifest, inside manifest:
uses-permission android:name=android.permission.RECEIVE_SMS/ My
MAINACTIVITY declares the BR as so...
private clsSMSRCV myClsSMSRCV;
and then in the MainActivity.onCreate() ==
myClsSMSRCV = new clsSMSRCV();
No need to do this - Android will instantiate your receiver as
necessary, and call its onReceive(). This is the clsSMSRCV definition with
the receive override:
public class clsSMSRCV extends BroadcastReceiver {
�...@override
public void onReceive(Context context, Intent intent) {
// I tear apart the SMS message(s) here... and alter Statics for
review outside this routine
}
}
Have you tried logging this?
Just a simple
Log.i(clsSMSRCV, Inside onReceive)
would be immensely helpful.
One last thing, I can think of...
Main has a runnable which is essentially monitoring the Statics and so
can then act upon them changing in ClsSMSRCV.
In my last experiment I had the onReceive() try to express a
Notification nuttin happened.
Polling for events is bad - it ties the CPU, uses up the battery, and
doesn't work when the phone is asleep. You could broadcast an intent
with your own action string to notify other components of your application.
--
Kostya Vasilyev -- WiFi Manager + pretty widget
--http://kmansoft.wordpress.com
--
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] My app gets killed because of android.process.media getting killed by OS
Hi,
I have seen one reference to this sort of problem where a MAIN app
dies because :::
because provider com.android.providers.media.MediaProvider is in
dying process android.process.media
In that reference the implication was that if you held a CURSOR too
long this could happen.
I am not using any explicit cursor, but maybe there is an implied one
somehere?
Hopefully these code snips will provide someone enough incite to offer
a solution.
I use a RINGTONE PICKER ==
String uri = null;
Intent intent = new
Intent( RingtoneManager.ACTION_RINGTONE_PICKER);
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_TYPE,
RingtoneManager.TYPE_NOTIFICATION);
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_TITLE, Select Tone);
if( uri != null)
{
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_EXISTING_URI,
Uri.parse( uri));
}
else
{
intent.putExtra( RingtoneManager.EXTRA_RINGTONE_EXISTING_URI,
(Uri)null);
}
startActivityForResult( intent,
Set_Ringtone);
And catch the result
@Override
public void onActivityResult(int reqCode, int resultCode, Intent
data) {
super.onActivityResult(reqCode, resultCode, data);
if (resultCode == RESULT_OK) {
Uri uri =
data.getParcelableExtra(RingtoneManager.EXTRA_RINGTONE_PICKED_URI);
if (uri != null) {
MainActivity.ringTonePath = uri.toString();
}
}
}
At some time later, I call a sound class to play the selected
ringtone :::
Ringtone myr = RingtoneManager.getRingtone(context,
Uri.parse( MainActivity.ringTonePath));
if (MainActivity.doDebug) Log.d(FPH, clsSound:Play
RINGTONE);
myr.play();
return;
This is called repeatedly while a flag is TRUE (until the user sets it
FALSE)
At this point the App is sitting essentially idle --- and if the
android.process.media dies (say by force) then so do I. But I do not
understand why I should die.
Any ideas?
thanks,
tob
--
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] App inconsistencies
Hi, I have an app that uses Runnables, GPS, Sensors, the AudioManager, MapView, Shared Preference storage; in effect ---all manner of the phone's capabilities. When I run this app on my Motorola DROID, it functions consistently --- all activities operate as expected -- all dialog popups POPUP when they are supposed to, all sounds are delivered when they are supposed etc etc etc. When a beta tester I have (with a new LG Ally) downloads and runs the App -- the results are all over the map (PUN intended ;) Most times, it just seems to die BUT without any this application has terminated unexpectedly dialog. The App will stop at various places inside my activities. Again, without any indication it has done so. And even stranger, the app will not do the things it supposed to be doing even though it IS still running. And ***worse yet***, sometimes, it seems to work fine ... Until maybe the next time it is launched (in other words, it was NOT re-Installed or anything so severe.) I am loathe to start adding all kinds of log output turning this into a bloatware science experiment (but will if forced.) Has anyone else had this kind of experience? I am developing on NETBEANS, targeting Android 2.x -- and the LG Ally meets these requirements. -- 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: App inconsistencies
I am familiar with using LOGCAT via my local TERMINAL Session.. But you are suggesting that LOGCAT runs on the Device and can be accessed? Do I need to enable Logging in my app? Will the LOGCAT show *all* activities from everything that's running (i.e. not just MY app) ? On Aug 30, 9:33 am, Kostya Vasilyev kmans...@gmail.com wrote: 30.08.2010 16:48, tony obrien пишет: I am loathe to start adding all kinds of log output turning this into a bloatware science experiment (but will if forced.) Before you start doing that, I'd ask the user to download and install one of the many applications that can display logcat output, run it, and email the log to you. You might see something interesting that's worth fixing. -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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: App inconsistencies
So LOGCAT operate on the device as well?? Do I need to ENABLE anything in my app? Does the LOGCAT have all of the device's activities in it, including those NOT from my app? Does the device automagically wrap the logcat (it can't grow forever) ? On Aug 30, 9:33 am, Kostya Vasilyev kmans...@gmail.com wrote: 30.08.2010 16:48, tony obrien пишет: I am loathe to start adding all kinds of log output turning this into a bloatware science experiment (but will if forced.) Before you start doing that, I'd ask the user to download and install one of the many applications that can display logcat output, run it, and email the log to you. You might see something interesting that's worth fixing. -- Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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: MapActivity (MapView) Problem
Mr. Murphy --- excellent suggestion. TreKing -- you too were on the right TraK. Stare and compare revealed that I was missing the permission for ACCESS_COARSE_LOCATION in the manifest. How that translates into a Layout/PixelConverter problem is for another study ;) I would have expected to get a blank display -- not a crash. Thanks, again. On Aug 25, 5:16 pm, TreKing treking...@gmail.com wrote: On Wed, Aug 25, 2010 at 3:52 PM, tony obrien tobsourcecode...@gmail.comwrote: I have all the appropriate Manifest entries, the simplest OnCreate --- all it does is setContextView() to the xml with a mapview in it. Maybe post the layout file you're using? Maybe you have something goofy there. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- 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] MapActivity (MapView) Problem
I have a DROID using Android 2.2 I am attempting to get the simplest MapActivity to run on the device. (NetBeans latest and greatest using a Google Api build target.) I have all the appropriate Manifest entries, the simplest OnCreate --- all it does is setContextView() to the xml with a mapview in it. When it runs; the screen goes black for a few seconds then an error dialog saying it stopped. The problem seems to be WAY INSIDE map object. Any suggestions would be most welcome. The (poignant parts of the) log -- E/AndroidRuntime(24224): FATAL EXCEPTION: main E/AndroidRuntime(24224): java.lang.NullPointerException E/AndroidRuntime(24224):at com.google.android.maps.PixelConverter.toPixels(PixelConverter.java: 71) E/AndroidRuntime(24224):at com.google.android.maps.PixelConverter.toPixels(PixelConverter.java: 61) E/AndroidRuntime(24224):at com.google.android.maps.MapView.onLayout(MapView.java:681) E/AndroidRuntime(24224):at android.view.View.layout(View.java:7035) E/AndroidRuntime(24224):at android.widget.FrameLayout.onLayout(FrameLayout.java:333) E/AndroidRuntime(24224):at android.view.View.layout(View.java:7035) E/AndroidRuntime(24224):at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1249) E/AndroidRuntime(24224):at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1125) E/AndroidRuntime(24224):at android.widget.LinearLayout.onLayout(LinearLayout.java:1042) E/AndroidRuntime(24224):at android.view.View.layout(View.java:7035) E/AndroidRuntime(24224):at android.widget.FrameLayout.onLayout(FrameLayout.java:333) E/AndroidRuntime(24224):at android.view.View.layout(View.java:7035) E/AndroidRuntime(24224):at android.view.ViewRoot.performTraversals(ViewRoot.java:1045) E/AndroidRuntime(24224):at android.view.ViewRoot.handleMessage(ViewRoot.java:1727) E/AndroidRuntime(24224):at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime(24224):at android.os.Looper.loop(Looper.java:123) E/AndroidRuntime(24224):at android.app.ActivityThread.main(ActivityThread.java:4627) E/AndroidRuntime(24224):at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(24224):at java.lang.reflect.Method.invoke(Method.java:521) E/AndroidRuntime(24224):at com.android.internal.os.ZygoteInit $MethodAndArgsCaller.run(ZygoteInit.java:868) E/AndroidRuntime(24224):at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) E/AndroidRuntime(24224):at dalvik.system.NativeStart.main(Native Method) -- 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] SoundPool and LOADing from a resource
The code:
//this is all contained in my MainActivity.
private SoundPool soundPool;
private HashMapInteger, Integer soundPoolMap;
public static final int SOUND_CANNON = 1;
public static final int SOUND_HIT = 2;
public static final int SOUND_MISS = 3;
public static final int SOUND_WOUND = 4;
public static final int SOUND_TAUNT = 5;
private void initSounds() {
soundPool = new SoundPool(5, AudioManager.STREAM_MUSIC, 100);
soundPoolMap = new HashMapInteger, Integer();
try {
soundPoolMap.put(SOUND_CANNON, soundPool.load(this,
R.raw.cannon, 1) );
} catch(Exception e) {
String s = new String(e.getMessage());
}
soundPoolMap.put(SOUND_HIT, soundPool.load(this, R.raw.hit,
1));
soundPoolMap.put(SOUND_MISS, soundPool.load(this, R.raw.miss,
1));
soundPoolMap.put(SOUND_WOUND, soundPool.load(this,
R.raw.wound, 1));
soundPoolMap.put(SOUND_TAUNT, soundPool.load(this,
R.raw.taunt, 1));
}
The Problem:
soundPool.load fails indicating that the RESOURCE CANNOT BE FOUND.
The oog files cannon, hit, miss, wound, and taunt are in my res/raw
folder (I am using NetBeans with the Android 2.x Emulator, BTW)
As an experiment I have added a line to try to open the same resource
(i.e. via the R.raw.xxx ID) as an InputStream and that succeeds. So I
am stumped as to why won't load as a soundPool resource.
--
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] SoundPool.Load from a resource
The code:
//this is all contained in my MainActivity.
private SoundPool soundPool;
private HashMapInteger, Integer soundPoolMap;
public static final int SOUND_CANNON = 1;
private void initSounds() {
soundPool = new SoundPool(5, AudioManager.STREAM_MUSIC, 100);
soundPoolMap = new HashMapInteger, Integer();
try {
soundPoolMap.put(SOUND_CANNON, soundPool.load(this,
R.raw.cannon, 1) );
} catch(Exception e) {
// error HERE is 'Resource Not Found'
String s = new String(e.getMessage());
}
}
The Problem:
soundPool.load fails indicating that the RESOURCE CANNOT BE FOUND.
The ogg files cannon is in my res/raw folder (I am using NetBeans
with the Android 2.x Emulator, BTW)
I changed the APK extension to ZIP and unzipped it to find that the
res/raw folder and its sound files are all there.
--
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: How to change the normal behaviour of a listview
By extending the LISTVIEW and overriding the GetView() you can do whatever you want. On Apr 15, 5:35 am, androidDeveloper stepmas...@googlemail.com wrote: Hello Android Developers, does anyone know how to imitate the behaviour of the iPhone list used in the cineplexx iPhone app shown on this page: http://itunes.apple.com/de/app/cineplex-kinoprogramm/id361227953?mt=8 I refer to the left image, which shows a list with different locations to choose. Special about this list is, that everytime a location has been choosen, the list is adjusted automatically, so that the nearest location is centered in the blue border. The adjusting process is animated. Thanks in advance! -- 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 To unsubscribe, reply using remove me as the subject.
[android-developers] Re: Prevent Orientation change at runtime
Since you call the other overlay when the orientation changes, a cheap hack would be to have the BUTTON Click listener set a global variable that the ORIENTATION listener can see and decide whether or not to allow the orientation change. On Apr 15, 3:44 am, Kumar Bibek coomar@gmail.com wrote: Hi, Well, preventing an orientation change is easy. But what about doing it at run time. Say, I have an activity which supports orientation change in normal situations. It has say three Edit Texts. There's also a button, which when clicked would do some processing in a thread while showing a ProgressDialog which is not cancellable. Ok, so till the user hits the Button, I want the activity to be able to adapt the orientation changes. I have two layouts files for each orientation with different layout schemes. What I want is this. Once the user clicks on the button, and the ProgressDialog is showing, I don't want the activity now to be re- created again when the orientation changes. So, before showing the ProgressDialog, is there any way to tell the Activity not to handle Orientation change? Also, once the process is complete, and the ProgressDialog is removed, I want the Activity again to be able to handle orientation changes. :) I know, we can save the state of all the things, and retrieve them back. But, just curious if this can be done? Thanks and Regards, Kumar Bibek -- 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 To unsubscribe, reply using remove me as the subject.
[android-developers] Re: Hey Mr or Ms Moderator...
So , Yes, This One did appear in the group! Has anyone gotten a feel for when/how-many/etc posts before you no longer go thru the moderator? thanks, tob On Feb 12, 9:26 am, tony obrien tobsourcecode...@gmail.com wrote: Hi, I have been attempting to operate within the android-developers and android-beginners Groups. I understand that new members are moderated, and completely agree with the concept. But to date, NONE of my posts have appeared. Is this normal? I am a new developer (thus the groups I am trying to participate in) and would *really* like to get active. Anything you can do to hasten my acceptance would be greatly appreciated. thanks, tony obrien -- 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: Really simple android question
Hi, You're likely not waiting LONG ENOUGH it takes quite sometime for the emulator to wake up and your app to get transferred ... The process goes something liek this... A. Start Emulator B. See 'text-oriented' A N D R O I D with blinking cursor C. text turns to ANDROID Graphic with slide-across shining light D. Your app gets loaded. This process can take 10s of seconds! Afterwards you DO NOT have to kill the emulator to restart/rerun/Debug your app... it will automagically get re-loaded as necessary. If you watch the Console Tab in your IDE you'll see the progress. tob On Feb 10, 1:48 pm, Josh josh...@gmail.com wrote: Hello Android Dev's Short FYI: I am new to the Android development, I have the SDK (2.1) and I am running Eclipse. I tried writing the Hello Android basic application. I coped the same code the tutorial has but when I try running the application to see the final result, I am unable to get the Virtual Android to perform the same result as the tutorial. I have created the default AVD that the tutorial explains at the beginning of the tutorial; the problem is the AVD is for Android 1.5, and since I am working with 2.1; Eclipse does not appear to work. I went through the AVD Manager and created a 2.1 virtual device with default settings. The problem is, when I run, I get the emulator, however it just shows the default A N D R O I D screen. It does not show Hello Android like the tutorial explains. Does anyone know what I am missing in order for my basic application to show up? -- 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] Hey Mr or Ms Moderator...
Hi, I have been attempting to operate within the android-developers and android-beginners Groups. I understand that new members are moderated, and completely agree with the concept. But to date, NONE of my posts have appeared. Is this normal? I am a new developer (thus the groups I am trying to participate in) and would *really* like to get active. Anything you can do to hasten my acceptance would be greatly appreciated. thanks, tony obrien -- 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
