not waking phone to notify/show popup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Let the phone go to sleep for 5-10 min
2. If any sms messages are received, the phone will not alert/show any popup 
until the 
phone is woken up/unlocked.

What is the expected output? What do you see instead?
It is supposed to wake the phone with a popup message containing the message 
received. 
Instead it does nothing until the phone is unlocked, then you get bombarded 
with all 
messages received since the last time the phone went to sleep.

What version of the product are you using? On what operating system?
1.0.6
Android 2.0.1

Please provide any additional information below.

Original issue reported on code.google.com by StiKe...@gmail.com on 6 Jan 2010 at 7:30

[GoogleCodeExporter]

I looked into another problem similar to this mentioned before, in which the 
phone
had very low memory and was possibly shutting things down in the background.. 
but I
have very little apps installed, and the Droid comes with plenty of memory 
anyway.

I had a different Droid before this one, in which SMS Popup worked perfectly 
on. It
only started doing this on my new replacement Droid. I find it hard to believe 
that
the phone hardware would be the problem.. I mean imagine trying to explain to 
Verizon
that this app doesn't work and it's the phone's fault. They would blame the app 
and
call me crazy.

Original comment by StiKe...@gmail.com on 7 Jan 2010 at 9:19

[GoogleCodeExporter]

I am having the same issue as StiKemUp.  When the phone goes to sleep for a 
little 
while, and I don't know how to time the exact duration, SMS notifications go 
unannounced until after the phone is unlocked.

I'm using a Motorola Droid, OS 2.0.1, SMS Popup v1.0.6

Original comment by eolanow on 11 Jan 2010 at 4:16

[GoogleCodeExporter]

Good to see I'm not the only one =\

Been doing everything I can to narrow this issue down for the past couple of 
days.
All notifications work perfect without SMS Popup installed. If I install SMS 
Popup
and have the popup 'disabled' everything works fine as well. It's only when I
'enable' the popup notification that this problem occurs.

It's really hard to make changes and test, since there's no specific time I can
predict this will happen. Just happens after so long with the phone being 
locked.

I think this app is far better than Handicent, due to it's basic and simplistic
look/feel. It's just what I wanted for notifications on my Moto Droid. Hope we 
can
get this figured out =(

Original comment by StiKe...@gmail.com on 11 Jan 2010 at 8:20

[GoogleCodeExporter]

I've been tweaking some settings here and there, and I may have come across a 
config 
that solves our issue.  I am going to verify it during charging overnight (when 
I 
know that I can replicate the notification issue) but so far, even after 
leaving it 
for 10 mins, 60 mins, and 90 mins time periods, I have been getting text 
notifications.

What I did is to turn OFF the popup notifications when I am actively using the 
phone.  
Now, popups only happen when the screen has gone into sleep mode.  It's not 
ideal, 
but when I'm using the phone, I still get the customized notification vibration 
and 
LED so glass half full, right?

The adjustment can be made under: ADDITIONAL SETTINGS > RESTRICT POPUP checkbox 
IS 
checked.  Incidentally, I also have PRIVACY MODE enabled (checked).

I'll come back if this resolution really works for the duration and perhaps it 
will 
allow Adam to track down the issue more deliberately.

Original comment by eolanow on 11 Jan 2010 at 8:51

[GoogleCodeExporter]

Lol, yeah I've been trying a lot of those settings here and there. Something 
will
seem to work great, and then the next day while at work it happens again. Very
diminishing.

So I was thinking maybe something was wrong with the OS on the phone recently. 
Last
night I loaded a new ROM for a modified version of 2.0.1. That way it would 
replace
the entire OS, just in case there may have been a bad batch of phones flashed 
from
Motorola.

Today the popups 'were' working great... until I let one sit without picking up 
my
phone to check it. After testing by texting myself from another phone, I was 
able to
duplicate the issue. If I get a message, the screen lights up and I can see the
popup. Then if I don't touch it and let the screen timeout, anything that comes 
in
after that will not alert/notify in any way until the screen is unlocked again. 
Once
unlocked, all those messages hanging will come tumbling out.

So ya, I'm back to the drawing board AGAIN.

Original comment by StiKe...@gmail.com on 12 Jan 2010 at 4:24

[GoogleCodeExporter]

Hey guys,

Thanks for all the testing you've been doing.  Several other people have 
reported 
this issue as well so its definitely a bug of sorts.  However for some reason I 
am 
unable to reproduce on my phone (perhaps I'm not receiving enough messages).  
All 
your feedback above should hopefully help me pinpoint the issue.  In particular 
I'm 
interested in knowing if the "restrict popup" feature fixes or helps the 
problem 
substantially (seems so on initial testing).

FYI, the SDK uses something called a WakeLock to wake the CPU and perform 
actions 
when the phone is sleeping.  The problem is likely due to the WakeLock not 
being 
acquired correctly (perhaps due to the previous WakeLock not being released 
correctly) which has the effect of nothing processing till the phone is 
awakened 
next.

Original comment by adam.eve...@gmail.com on 12 Jan 2010 at 4:18

• Changed state: Accepted

[GoogleCodeExporter]

Hey there.  First off, and again, GREAT PRODUCT. I really love it.  Google 
should 
acquire you immediately and incorporate you into their Android OS 2.2 SDK!

So far, and I'm keeping my fingers crossed, the "restrict popup" fix has 
ameliorated 
my problem.  I'm going to continue to monitor texts over the next couple days 
and 
I'll report back if it it's still working or if I'm getting notification issues 
again.

However, I'm also going to try StiKemUp's approach of sending a text to my 
phone, NOT 
touching the phone, letting it go back to sleep for a while, and then texting 
it 
again to see if I receive a notification.  I'll report back after that 
iteration 
also.

Thanks for keeping track of these issues.

Original comment by eolanow on 12 Jan 2010 at 4:25

[GoogleCodeExporter]

If there's anything you need as far as info from my phone etc, let me know I'd 
be
happy to help in any way I can. If so shoot me an email, StiKemUp@gmail.com.

Original comment by StiKe...@gmail.com on 12 Jan 2010 at 4:36

[GoogleCodeExporter]

StiKemUp: you will be excited (and probably relieved) to know that I was able 
to 
duplicate your issue exactly.  As you mentioned, I sent a text message to my 
phone and 
did not touch anything on the phone after I received that first text message 
(which 
did result in waking up the phone and making a popup).  After waiting for the 
phone to 
go back to sleep and an additional 10 minutes to pass, I sent a second text 
message to 
my phone which did NOT wake the phone nor result in a popup message.  I think 
we are 
honing in on the root of the problem here.

Original comment by eolanow on 12 Jan 2010 at 4:48

[GoogleCodeExporter]

I did one more test whereby I disabled the popup feature of SMSPopup but kept 
the 
vibration, notifier and LED settings of SMSPopup.  So basically, it's just 
handling 
SMS notification duties (same as the default Android app) but allows for me to 
control the LED and the vibration pattern.  I let the phone sleep for 5-10 
minutes, 
then sent a message to myself.  The phone's screen did not turn on (as 
configured) 
but the LED turned yellow, the notification tone sounded, and the custom 
vibration 
worked.

Then immediately thereafter (say 1 min), I sent myself another text.  Again, it 
worked as above (notifier tone, LED and custom vibration all worked).  So far 
so 
good.

Next, I waited for the phone to sleep (mine is set at 1min) and then waited an 
additional 10 minutes.  At this time, I sent myself a third text message.  Lo 
and 
behold, this time, I DID receive the text message alert.

Accordingly, it would appear that the popup is creating the problem.  Perhaps 
it is 
because it sits unanswered in sleep mode.  I have read where some users noticed 
problems with multiple popups and not hearing notifications.  This seems to be 
tied 
to it.  The solution may be as simple as allowing multiple popups to pile up 
and for 
each one to be able to indicate a 'new' message.

Original comment by eolanow on 12 Jan 2010 at 5:09

[GoogleCodeExporter]

I can reproduce this problem on my phone every time which is good news - stay 
tuned, 
should have a fix soon hopefully.

Original comment by adam.eve...@gmail.com on 20 Jan 2010 at 11:49

[GoogleCodeExporter]

Can you both try this beta version of SMS Popup to see if it helps the issue:
http://android-smspopup.googlecode.com/files/SMSPopup-1.0.7-beta2.apk

It fixes the problem on my phone (Nexus One), but I don't have other phones to 
test 
with (with pre-Android 2.1).

This also may make the popup feel a bit slower to show on older phones as it 
will 
turn the screen on before it does some of the work (whereas before it turns the 
screen on once most of the work has been completed).

Original comment by adam.eve...@gmail.com on 22 Jan 2010 at 5:10

[GoogleCodeExporter]

Installing now and will test tonight and tomorrow. 
Thanks for working with us on this one :)

Original comment by StiKe...@gmail.com on 22 Jan 2010 at 5:33

[GoogleCodeExporter]

Seems to be working like a champ =)
Sent myself 20+ messages last night and it didn't skip a beat. Had many 
messages back
and fourth with multiple people this morning and still running strong.

Original comment by StiKe...@gmail.com on 22 Jan 2010 at 6:50

[GoogleCodeExporter]

Awesome news.  Haven't had a chance to install it yet for testing but I'm 
betting this 
solved the problem.  Can't wait to get the popups back (which I disabled in 
SMSpopup 
in order to resolve the problem)...it's one of my favorite features.

Original comment by eolanow on 22 Jan 2010 at 7:23

[GoogleCodeExporter]

Marking this as fixed for now.  Please report back and update the issue tracker 
if you 
still have problems.

v1.0.7 is now in Market so if you installed the beta you should uninstall and 
reinstall 
from Market.

Original comment by adam.eve...@gmail.com on 25 Jan 2010 at 4:44

• Changed state: Fixed

[GoogleCodeExporter]

Hey. 
Any possibility to know what caused this problem? I am developing an sms popup 
myself, and i have the same problem. When i receive a message, the screen is 
turned on, the keyguard is unlocked and the popup is shown. I wait until the 
phone goes to sleep, it doesn't count how long it's sleeping, 1 second, 1 hour, 
whatever, it does not turn on the screen or give out a popup when a new message 
is received, until the phone is woken up. If it's not configured to turn on the 
screen, but only give out a notify, the notify is given every time. No matter 
what.

How did you solve this?

Original comment by runel...@gmail.com on 12 Sep 2010 at 9:55