Hehe, yeah.
2013/1/17 b0b
>
>
> On Wednesday, 16 January 2013 10:43:37 UTC+1, Kostya Vasilyev wrote:
>>
>> Heh. Looks like it *is* intentional.
>>
>> https://android.googlesource.**com/platform/frameworks/base/+**
>> /refs/heads/master/services/**java/com/android/server/**
>> NotificationManager
On Wednesday, 16 January 2013 10:43:37 UTC+1, Kostya Vasilyev wrote:
>
> Heh. Looks like it *is* intentional.
>
>
> https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/services/java/com/android/server/NotificationManagerService.java
>
>
>
That change is really stupid.
So really all we have to do is rebuild our android OS with that flag set to
false and we're good to go? ;)
On Wed, Jan 16, 2013 at 4:56 AM, Tobias Lindberg <
tobias.e.lindb...@gmail.com> wrote:
> True, will do.
>
>
> 2013/1/16 Raghav Sood
>
>> @Tobias Now that you've found the problem, it'd be n
True, will do.
2013/1/16 Raghav Sood
> @Tobias Now that you've found the problem, it'd be nice if you could close
> your question on StackOveflow as well. I posted the answer for now, but it
> would probably be best if you posted it from your own account and accepted
> it.
>
> Raghav Sood
> http
@Tobias Now that you've found the problem, it'd be nice if you could close
your question on StackOveflow as well. I posted the answer for now, but it
would probably be best if you posted it from your own account and accepted
it.
Raghav Sood
http://www.appaholics.in/ - Founder
http://www.apress.com
That is really strange, if the user should have the option of disabling it
should not be bulked with push notifications.
2013/1/16 Kostya Vasilyev
> Heh. Looks like it *is* intentional.
>
>
> https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/services/java/com/android/
Heh. Looks like it *is* intentional.
https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/services/java/com/android/server/NotificationManagerService.java
Lines 693-707:
final boolean isSystemToast = ("android".equals(pkg));
if (ENABLE_BLOCKED_TOASTS &&
Definetly a bug, no one would be stupid enough to do that on purpose. Or at
least I hope so.
2013/1/15 Kevin Duffey
> Indeed that is important.. why would a toast notification be blocked by
> that setting? Obviously a bug.. I can't imagine they meant to do that.
>
>
> On Tue, Jan 15, 2013 at 2:0
Indeed that is important.. why would a toast notification be blocked by
that setting? Obviously a bug.. I can't imagine they meant to do that.
On Tue, Jan 15, 2013 at 2:09 PM, Mark Murphy wrote:
> Wow. That's an important find. Thanks for pointing this out!
>
> On Tue, Jan 15, 2013 at 4:31 PM, Ha
Wow. That's an important find. Thanks for pointing this out!
On Tue, Jan 15, 2013 at 4:31 PM, Harri Smått wrote:
> Hi,
>
> There's a bug filed on Android bug database;
>
> http://code.google.com/p/android/issues/detail?id=35013
>
> In other words, if you disable application notifications, Toasts
That must have been it, it started working today and by coincidence my boss
came and told me that there is some issues with push so I went and checked
there and it was not enabled and well yeah, enabled it and without
connecting it it started working again and now when u mention this it makes
total
Hi,
There's a bug filed on Android bug database;
http://code.google.com/p/android/issues/detail?id=35013
In other words, if you disable application notifications, Toasts also are
disabled for that particular application. Could this be the reason for
behaviour Tobias is facing?
--
H
On Jan 15
I have also tried this with the Galaxy S3 and 4.1.1, and the Toast shows
fine.
Here's the code I used:
public class MainActivity extends Activity {
@Override
protected void onResume() {
super.onResume();
Toast.makeText(MainActivity.this, "The message", Toast.LENGTH_LONG).show();
}
@Overri
Ok..I just tried and it worked for me. I have Android 4.1.1, checked for
updates nothing there.. so this seems to work for me. I am plugged in via
USB debugging.
On Tue, Jan 15, 2013 at 4:44 AM, Tobias Lindberg <
tobias.e.lindb...@gmail.com> wrote:
> Thx :)
>
> Try this in your onResume method o
If I can remember I'll try on my s3 sometime today. Any code snippet you
want me to try ?
On Jan 15, 2013 1:34 AM, "Tobias" wrote:
> My carrier is a Danish carrier called Tre (Three) but I dont have a
> carrier dependent phone, I ordered it over the internet.
>
> On Monday, January 14, 2013 5:38:
My carrier is a Danish carrier called Tre (Three) but I dont have a carrier
dependent phone, I ordered it over the internet.
On Monday, January 14, 2013 5:38:53 PM UTC+1, bob wrote:
>
> Who is your carrier?
>
> On Monday, January 14, 2013 7:06:36 AM UTC-6, Tobias wrote:
>>
>> I have a toast displ
My carrier is a Danish carrier called Tre (Three) but I dont have a carrier
dependent phone, I ordered it over the internet.
2013/1/14 bob
> Who is your carrier?
>
> On Monday, January 14, 2013 7:06:36 AM UTC-6, Tobias wrote:
>>
>> I have a toast displayed in the following way:
>>
>> Toast.makeT
Who is your carrier?
On Monday, January 14, 2013 7:06:36 AM UTC-6, Tobias wrote:
>
> I have a toast displayed in the following way:
>
> Toast.makeText(context, "The message", Toast.LENGTH_LONG).show();
>
>
> I am 100% I am displaying the toast from the UI thread and I can add that
> it worked
It's because you are creating a new toast object and canceling the new
object rather than the old object that's showing.
Maybe make the toast a member variable?
On Friday, December 21, 2012 1:04:09 AM UTC-6, sujit dubey wrote:
>
>
> I am trying to display a toast on incoming call an
Hi,
I am using a Toast inside an IntentService.
To fix the not disappearing toast issue I have used an handler:
private Handler handler = new Handler();
...
handler.post(new Runnable() {
@Override
public void run() {
Toast.makeText(getApplicationContext(), "Network problem",
Toast.LENGTH_SHORT)
for me the same is working on 4.0.3
On Wed, Feb 15, 2012 at 2:17 PM, giles ian wrote:
> FYI
>
> working on Galaxy S 2.2 but not on galaxy tab 10.1" 3.2 and Nexus S 4.0.3
>
>
> On Wed, Feb 15, 2012 at 2:13 PM, giles ian wrote:
>
>> Hi,
>>
>> The below piece of code is working fine on 2.2&2.3 but
FYI
working on Galaxy S 2.2 but not on galaxy tab 10.1" 3.2 and Nexus S 4.0.3
On Wed, Feb 15, 2012 at 2:13 PM, giles ian wrote:
> Hi,
>
> The below piece of code is working fine on 2.2&2.3 but not on 3.0 onwards.
>
> Toast.makeText(SomeActivity.this,
> getResources().getString(R.string.not_impl
My toast is extremely small on ICS, worked perfect on previous
releases. Also see
http://stackoverflow.com/questions/8658059/android-toast-notification-is-too-small-in-ice-cream-sandwich
Anyone?
On Dec 13, 3:43 pm, David Strickland wrote:
> > If you're modifying the source, try one of the grou
I was too experiencing this sticking Toast issue when calling finish()
in a LicenceChecker Callback
I fixed it by creating a toast message on the UI thread then posting
to the threads handler setting the toast text and showing it..
public class LicenseCheck extends Activity {
...
private
On Mar 1, 11:26 pm, Julius Spencer wrote:
> Hi,
>
> No unfortunately that didn't work.
>
Just for a try always put Log.d() or whatever.. if you see
constantly repeating output message you have while(1) problem and
it's easier to notice it.
--
You received this message because you
Well I could be wrong about the cause, but I have definitely seen them
stuck before. Killing the process fixed it. It wasn't in production
code so I never dug into it.
-Kevin
On Feb 28, 11:22 pm, Zsolt Vasvari wrote:
> On Mar 1, 1:01 pm, Kevin TeslaCoil Software
> wrote:
>
> > I think I've seen
On Mar 1, 1:01 pm, Kevin TeslaCoil Software
wrote:
> I think I've seen something like if you show a toast and then your
> activity is destroyed before the toast disappears it might get stuck.
> Easier to reproduce if you're calling finish(). Probably could avoid
> it if you save the toast refere
I think I've seen something like if you show a toast and then your
activity is destroyed before the toast disappears it might get stuck.
Easier to reproduce if you're calling finish(). Probably could avoid
it if you save the toast reference and do a .cancel() in onDestroy.
-Kevin
On Feb 28, 8:53
hi Flying Coder
Thanks for the suggestion.
In my case i don't want to make change to actual Service class because
in normal application run the Toast message is being displayed
properly.
But when i start the service from my test class, it give me such
problem.
On Aug 6, 5:07 am, Flying Coder wr
hi Flying Coder
Thanks for the suggestion.
In my case i don't want to make change to actual Service class because
in normal application run the Toast message is being displayed
properly.
But when i start the service from my test class, it give me such problem.
On Fri, Aug 6, 2010 at 5:37 AM, Fly
hi Flying Coder
Thanks for the suggestion.
In my case i don't want to make change to actual Service class because
in normal application run the Toast message is being displayed
properly.
But when i start the service from my test class, it give me such problem.
On Fri, Aug 6, 2010 at 5:37 AM, Fly
Hi Nikki,
Toast's need to happen on the main UI thread. Slightly different
situation, but you may find this thread useful:
http://groups.google.com/group/android-developers/browse_thread/thread/8fe7d6a776f5f2fb/a9ecf18a32891cab#a9ecf18a32891cab
Cheers,
Steve
On Aug 5, 8:48 am, nikki wrote
On Tue, Dec 1, 2009 at 10:25 AM, Lance Nanek wrote:
> Maybe you could just use a single Toast, but update the message with
> setText. A call to show each time would be needed as well to show it
> again if it has disappeared or to extend the time if it is still up
> and just getting its message cha
Maybe you could just use a single Toast, but update the message with
setText. A call to show each time would be needed as well to show it
again if it has disappeared or to extend the time if it is still up
and just getting its message changed.
On Dec 1, 10:28 am, Greg Donald wrote:
> On Mon, Nov
On Tue, Dec 1, 2009 at 2:51 AM, Guillaume Perrot
wrote:
> And you can try mToast.getView().setVisible(View.GONE) for the current
> one.
Thanks, but I tried this and it doesn't seem to help. The messages
still build up a queue. I need a way to manage the message queue
itself, I never want more t
On Tue, Dec 1, 2009 at 2:50 AM, Guillaume Perrot
wrote:
> There are only two possible durations, the integer parameter refers to
> the possible constants which are LENGTH_LONG and LENGTH_SHORT.
> According to me, cancel() just cancels pending toasts in queue, this
> may not work on the current one
And you can try mToast.getView().setVisible(View.GONE) for the current
one.
On 1 déc, 06:30, Suchand Ghosh wrote:
> what code base you r using? there should be function to hide toast. Hide
> generally post a msg to mHandler to hide the Toast.
>
> On Tue, Dec 1, 2009 at 10:50 AM, Greg Donald wrot
There are only two possible durations, the integer parameter refers to
the possible constants which are LENGTH_LONG and LENGTH_SHORT.
According to me, cancel() just cancels pending toasts in queue, this
may not work on the current one.
On 1 déc, 06:30, Suchand Ghosh wrote:
> what code base you r
I seem to remember something about this awhile ago. A Toast is a Toast and
once queue can't be canceled is what I remember.You might search this
group and I'll bet you'll find that answer.
On Mon, Nov 30, 2009 at 8:18 PM, Greg Donald wrote:
> On Fri, Nov 27, 2009 at 11:53 AM, Greg Donald
On Fri, Nov 27, 2009 at 11:53 AM, Greg Donald wrote:
> How can I keep Toast from building up a queue of messages?
>
> I'm working on a board game and I'm sending status messages back to
> the user with this wrapper function I created for Toast:
>
> private void toast( String s )
> {
Thats what I was thinking.I've had this happen on other apps before and
could never reproduce it. I really need to get taskkiller for myself some
day.[?]
On Tue, Nov 17, 2009 at 10:36 AM, niko20 wrote:
> I don't think the toast was your problem. It could be that something
> else in the pho
I don't think the toast was your problem. It could be that something
else in the phone hung up (I've even had my Droid do it) and thereby
the UI wouldn't respond as expected.
-niko
On Nov 17, 12:10 pm, Stephen Abrams wrote:
> No stuck toasts here. As documented, you generally don't have to
> can
Thank you! The got my app to display a message to the user! Yay!
And you are about to have a customer!
On Nov 4, 12:14 pm, Mark Murphy wrote:
> furby wrote:
> > Perhaps I am going about this the wrong way... it seems like a lot of
> > shifting of code around to get a simple message to display in
furby wrote:
> Perhaps I am going about this the wrong way... it seems like a lot of
> shifting of code around to get a simple message to display in google
> maps.
Not really.
> Let me rephrase the question : Is there a simple way to get the two
> String parameters to display (That are sent to th
Perhaps I am going about this the wrong way... it seems like a lot of
shifting of code around to get a simple message to display in google
maps.
Let me rephrase the question : Is there a simple way to get the two
String parameters to display (That are sent to the OverlayItem class)
when a point is
furby wrote:
> Hmmm Am I putting the onTap handler in the wrong place? I thought
> that it would go in the overlay handler
Your onTap() is in the correct place. However, HelloItemizedOverlay is
not a Context, and so it cannot be used as the first parameter to
makeText().
Either make Hello
Hmmm Am I putting the onTap handler in the wrong place? I thought
that it would go in the overlay handler
On Nov 4, 11:01 am, Mark Murphy wrote:
> furby wrote:
> > To be sure that you have some idea of what I am talking about, here is
> > the code for the entire class :
>
> > import java.
furby wrote:
> To be sure that you have some idea of what I am talking about, here is
> the code for the entire class :
>
> import java.util.ArrayList;
>
> import android.graphics.drawable.Drawable;
> import android.widget.Toast;
>
> import com.google.android.maps.ItemizedOverlay;
> import com.g
To be sure that you have some idea of what I am talking about, here is
the code for the entire class :
import java.util.ArrayList;
import android.graphics.drawable.Drawable;
import android.widget.Toast;
import com.google.android.maps.ItemizedOverlay;
import com.google.android.maps.OverlayItem;
It underlines the "makeText" word and when I ask it for suggestions
all it says is "Rename in file".
Which makes me wonder if, perhaps, "makeText' no longer exists in the
Toast object?
On Nov 4, 10:38 am, Mark Murphy wrote:
> furby wrote:
> > So I am slowly trying to figure out maps... I wan
Thanks for your answers.
Now I work with threads. But I dont use the AlertDialog - i make some
buttons visible and invisible.
Thats good enough for the first time. If someone has a better idea,
please let me know.
greets,
Stefan
--~--~-~--~~~---~--~~
You received
Hi,
On Sat, Aug 1, 2009 at 06:35, Stefan wrote:
> But can I include Buttons in a Toast??
AFAIK toasts don't receive any input as they never receive focus as
described at the top of the docs:
http://developer.android.com/reference/android/widget/Toast.html
I'd love to be proven wrong, though ;)
Hi,
On Aug 1, 1:42 am, CraigsRace wrote:
> You could create your own dialog class which started a thread that
> calls finish() (back on the EDT) after x seconds.
>
Do you mean, that i should do something like that:
alert = new AlertDialog.Builder(xxx.this).setTitle("Alert Example
1").setIcon(R
You could create your own dialog class which started a thread that
calls finish() (back on the EDT) after x seconds.
On Aug 1, 8:35 am, Stefan wrote:
> Hi,
>
> i need a alert dialog, which pop ups every time, when the location
> changed (after 100 meter for example).
> I want to have 2 Buttons i
Thanks Dianne Hackborn for the reply,
Will try this out and let you know..
Thanks
On Jul 15, 11:23 am, Dianne Hackborn wrote:
> Hi, this isn't really supported by toasts, which are designed to be shown
> completely independently of the current app. You can fairly easily
> accompli
Hi, this isn't really supported by toasts, which are designed to be shown
completely independently of the current app. You can fairly easily
accomplish this by just displaying a normal dialog, except making it not
have focus or receive touch events and giving it an animation style that
fades in an
hehe, well, I am trying to save some battery on the phone, so there is
no need to light it up in my case. Its not an alarm :)
On May 29, 2:04 pm, Sundog wrote:
> > Is there a way to show the Toast without turning on the light?
>
> I don't know, but that has to be my all-time favorite question h
> Is there a way to show the Toast without turning on the light?
I don't know, but that has to be my all-time favorite question here.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To po
58 matches
Mail list logo
