SMS problem

[Guest ntanghe]

Hi,

I use the last FLB on my 2.1 pulse.

I use ADW (because too many reload with launcher pro) and It works very good.

Unfortunately, I don't receive sms sometimes (but most of time is ok)

Is the problem with too small memory ?

Is there a solution ?

Thanks !

[Guest Ellia]

Probably it's caused by a lack of free ram because the sms service is killed.

Well, use AutoKiller and try to get free ram. But there is no real solution.

[Guest ntanghe]

Is possible to use autokiller and put the "sms service" in a no killed app list ?

[Guest sNaiL94]

The auto killer can't kill the sms service! It's a system service (hidden)

But if not, put it on the ignore list

[Guest Rumcájsz]

Is the problem with too small memory ?

Is there a solution ?

Yes. Unfortunetly, No.

This is a general Android Bug, but Google no answer: http://code.google.com/p/android/issues/detail?id=4991

Keep your RAM over 10MB.

[Guest -Wii-]

Yes. Unfortunetly, No.

This is a general Android Bug, but Google no answer: http://code.google.com/p/android/issues/detail?id=4991

Keep your RAM over 10MB.

Don't get this confused with the problem we have, it's different, it may be related but it's different.

Reason been on other devices they may get a notification saying they can't get a message and therfore it's not received.

With out phone the phone is defiantly accepting the SMS and taking it off the messaging server but then never showing it to the user, in affect it's getting lost in the RAM or something.

It's a separate issue.

[Guest de_shepherd]

May not just be SMS that get missed ... after increading numbers of force close requests etc (n.b. I'm still on an old FLB ROM and more recent ones are meant to be better in this respect) I decided to clear the dalvik cache as had read that that helped. When phone rebooted I noticed I now had a missed call warning (which I'm sure wasn't there before) and when I looked at it saw that the call was "missed" on the previous day (n.b. at time phone was recharging at home while I was out so no idea if it actually rang or not).

So, now wondering if its also possible for calls to be "missed" as well as SMS messages

[Guest meinnit]

May not just be SMS that get missed ... after increading numbers of force close requests etc (n.b. I'm still on an old FLB ROM and more recent ones are meant to be better in this respect) I decided to clear the dalvik cache as had read that that helped. When phone rebooted I noticed I now had a missed call warning (which I'm sure wasn't there before) and when I looked at it saw that the call was "missed" on the previous day (n.b. at time phone was recharging at home while I was out so no idea if it actually rang or not).

So, now wondering if its also possible for calls to be "missed" as well as SMS messages

I dont think this is an issue...this normally happens under the following circumstances:

- You receive a call that you have missed

- You go to notifications and simply press clear

- Do not go into call log

- Reboot phone

Notification appears again although I think it appears at the current time rather than the time of the actual missed call.

[Guest Rumcájsz]

Don't get this confused with the problem we have, it's different, it may be related but it's different.

Reason been on other devices they may get a notification saying they can't get a message and therfore it's not received.

With out phone the phone is defiantly accepting the SMS and taking it off the messaging server but then never showing it to the user, in affect it's getting lost in the RAM or something.

It's a separate issue.

You're right, but I think in both cases, this (low memory) causes the problem

[Guest Rumcájsz]

If you get this problem, please add comments and STAR this issue:

http://code.google.com/p/android/issues/detail?id=11045

[Guest Rumcájsz]

If you get this problem, please add comments and STAR this issue:

http://code.google.com/p/android/issues/detail?id=11045

Google solved the SMS error, and will fix it in next Android release:

"Comment 29 by lennart, Sep 17 (2 days ago)

I am happy to pass on that according to my source at Google, this bug has now been fixed and will be available in the next release of Android. Thank you for helping to bringing it to their attention."

Edited September 20, 2010 by Rumcájsz

[Guest Daz555]

I am happy to pass on that according to my source at Google, this bug has now been fixed and will be available in the next release of Android. Thank you for helping to bringing it to their attention."

...which I doubt we will ever see on the Pulse (officially at least). Over to TomG et al.

Also, has adding swap to the kernel currently used in 2.1 effectively worked around the issue anyway?

[Guest meinnit]

In an attempt to reduce this problem, I have disabled Messaging app from triggering when receiving a text. It seems that both Handcent AND Messaging app are trigger each time you receive a message. Obviously with 2 apps running for each message received you are more likely to run out of RAM.

Has anyone tried this? I did a quick test and I'm still receiving SMS messages. If anyone wants to try this you need a paid app from the Market called Autostarts and simply disable Message on SMS Received trigger.

[Guest meinnit]

Update...disabling Messaging on SMS Received trigger doesn't seem to have caused any nasty side effects and I don't seem to have missed any texts yet :lol: Don't know if it's had any affect on MMS though.

[Guest Daz555]

I have so far been unable to recreate the SMS bug running FLB-mob 1.6b with 64MB swap enabled. This is excellent news.

[Guest Azurren]

I have so far been unable to recreate the SMS bug running FLB-mob 1.6b with 64MB swap enabled. This is excellent news.

I got an SmS late (When power using browser / music) when using SWAP

I deem this a success :lol:

[Guest GlasWolf]

I have so far been unable to recreate the SMS bug running FLB-mob 1.6b with 64MB swap enabled. This is excellent news.

Could you reproduce it on previous versions? Was it frequent for you?