Phone not waking from sleep correctly on Samsung Moment device about android-smspopup

[GoogleCodeExporter]

From user:
-------------------------------------------------------------------------
Sysinfo - Samsung/SPH-M900/SPH-M900/SPH-M900:1.5/CUPCAKE/CJ05:user/ota-rel-
keys,release-keys
Model: SPH-M900

SMS Popup v1.0.1 config -
enabled: true
timeout: 30
privacy: false
dimscreen: true
markread: true
showonkeyguard: true
showbuttons: true
button1: 1
button2: 2
button3: 4
blur: true
popup: true
notification: false
notifsound: content://settings/system/notification_sound
vibrate: true
vibrate_pattern: 0,1200
vibrate_pattern_custom: null
flashled: true
flashled_color: Yellow
notif_repeat: false
notif_repeat_num: 2
notif_repeat_interval: 5
locale: English (United States)
-------------------------------------------------------------------------

Original comment by [email protected] on 6 Nov 2009 at 5:02

[GoogleCodeExporter]

Have the same issue on an ADP1 running Cyanogenmod -- currently 4.2.4, but this 
has
been happening since 4.1.x.

Original comment by [email protected] on 13 Nov 2009 at 5:57

[GoogleCodeExporter]

In the Samsung Moment this is caused by the "Dim Screen" option being set (the 
device 
doesn't seem to support the SDK call to set the screen to dim).  Can you see if 
you 
have that setting on?

Original comment by [email protected] on 13 Nov 2009 at 9:32

[GoogleCodeExporter]

"Dim Popup Screen" in SMS Popup's Additional Settings section is *not* checked.

Original comment by [email protected] on 13 Nov 2009 at 10:12

[GoogleCodeExporter]

Does this happen 100% of the time or only sometimes?  Do you have any special 
lock 
screen apps or other messaging apps installed?

Original comment by [email protected] on 14 Nov 2009 at 4:12

[GoogleCodeExporter]

It does not happen 100% of the time.

I'm not sure of the pattern, but it seems like the most frequent occasion when 
it
occurs is first thing in the morning, when I unlock the phone.  It is as though 
the
longer the phone remains idle with the screen asleep, the more likely this is 
to occur.

I do have WifiLock, and usually leave it set so that the wifi is prohibited from
sleeping.

I use Cyanogenmod's built-in menu-button-to-unlock capability.  I don't have any
other locking apps, nor do I have any lock-screen customizations.

The only other messaging app I can think of is the default Cyanogenmod 
Messaging app.
 Notifications are disabled in that app.

Original comment by [email protected] on 14 Nov 2009 at 4:42

[GoogleCodeExporter]

I don't think its WifiLock causing issues.  The only problem that seems to 
occur with 
the Cyanogenmod rom is that its always running low on memory (as it loads some 
fancier things in memory) - the way Android behaves in these conditions is it 
starts 
to kill off background processes, if it happens to knock off a piece of SMS 
Popup 
this behavior could occur.

One more question: when you wake up the phone and see this, is SMS Popup just 
waiting 
there behind the unlock screen or does it take a second or two to load before 
poppping up and making the sound?

Original comment by [email protected] on 17 Nov 2009 at 1:42

[GoogleCodeExporter]

Yeah, changing WifiLock doesn't seem to have made much difference.

It seems plausible that it could be low-memory killoff.

When I unlock, the popups and beeps rapidly tumble out.  They don't take a 
second or
two, but there is definitely a fraction of a second before they appear/sound 
out.

Original comment by [email protected] on 17 Nov 2009 at 3:01

[GoogleCodeExporter]

Yep it sounds like the background process that holds the "WakeLock" (which 
prevents the 
device from sleeping while work is being done) is getting killed off.  These 
memory 
issues normally happen on custom roms as they tend to load more stuff 
permanently in 
memory.  One thing you can try is disabling "Keep Home in memory" (i think its 
called 
that) under Spare Parts in CyanogenMod, this uses up a lot of memory without 
allowing 
any app to use it (of course the upside is Home always loads fast..)

Original comment by [email protected] on 20 Nov 2009 at 2:31

[GoogleCodeExporter]

Well, disabling "Keep Home in Memory" definitely helped.  It also helps to kill 
off
some of the apps android inexplicably launches for no apparent reason.

Is there no way to exclude SMSPopup from being killed?

Also, is it just me, or is SMSPopup's RAM footprint rather large?  It's 
currently
using about 14 MB on my G1. 

Original comment by [email protected] on 26 Nov 2009 at 9:49

[GoogleCodeExporter]

I also found another bug that may have been causing the system messaging app to 
hang
(which could have caused incoming messages not to store correctly).  This fix 
is in
SMS Popup 1.0.6 so try that out and see if it helps.

14MB sounds like a lot, which tool did you use to see this?

Original comment by [email protected] on 11 Dec 2009 at 4:12

[GoogleCodeExporter]

This might also be caused by another bug which should now be fixed in the 
latest 
version (not yet in market but soon):
http://code.google.com/p/android-smspopup/issues/detail?id=79

Original comment by [email protected] on 24 Jan 2010 at 10:45

• Changed state: Fixed