Open GoogleCodeExporter opened 9 years ago
In the past it was usually GoSMS that has eaten the intents. But your reasoning
sounds correct. At the moment there is no way to configure the SMS received
intent priority as it's defined the manifest. And it configured to a very
reasonable value. I see this more as a bug of the default stock SMS app of the
HTC One.
Anyway, we first have to verify that it is *in fact* a problem related to the
intent receiver priority. Are you able to compile GTalkSMS yourself with a
higher receiver priority or do we need to release a 'patch' release for you
(which may take some time)?
Original comment by fschm...@gmail.com
on 18 Dec 2012 at 12:09
I agree it seems to be a problem with the stock SMS app on the one x+. I
have managed to recompile the code with an increased filter priority but I
get an error when installing. I'll figure that out and get back to you
here. (I will get back to you here if I can't figure it out too.)
Do you know, is the "person x is calling" report part of the SMS intent?
Sent from my phone. Please excuse brevity.
Original comment by patrick....@bsdfirst.com
on 18 Dec 2012 at 12:15
Just wanted to give an update as to my testing:
I compiled with the maximum receiver priority. GtalkSMS then provided "SMS
Received" and "<x> is calling" notifications; however, "SMS was sent"
notifications were never output.
I have since removed my custom compile and re-installed the current GtalkSMS
from the Play store. I now continue to receive "SMS Received" and "<x> is
calling" notifications and event receive "SMS was sent" notification albeit
very intermittently.
To be honest, I am now completely at a loss as to what is happening, but the
functionality that I desire is working for me. If you see any value, I'm happy
to provide whatever help I can to run this down. (Not sure if this will become
more apparent with other newer HTC devices.) But otherwise, I guess you can
feel free to close the ticket.
Appreciate your feedback. Apologies if I've wasted your time at all.
Original comment by patrick....@bsdfirst.com
on 28 Dec 2012 at 1:05
No need to apologize, you did a great research job and all the work. :)
I don't have a explanation yet about what is going either. I'll leave this open
as new for a while. Maybe we'll figure it out.
Original comment by fschm...@gmail.com
on 28 Dec 2012 at 9:42
It might be an issue during the first installation and the receivers (call, and
sms) were not corretly registered.
Original comment by Florent....@gmail.com
on 30 Jan 2013 at 12:58
I have the same problem on my Galaxy S4 GT-I9505 JDQ39.XXUAME2 stock. No SMS
apps installed other than the Samsung stock one.
Original comment by paal.nil...@gmail.com
on 13 Jun 2013 at 12:48
Original issue reported on code.google.com by
patrick....@bsdfirst.com
on 18 Dec 2012 at 6:12