*** This bug is a duplicate of bug 1617961 ***
https://bugs.launchpad.net/bugs/1617961
** This bug has been marked a duplicate of bug 1617961
Need to detect use of UCS-2 encoding and reflect in message count
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Here's the bug report for that:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1484664
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to SMS being sent mul
Ok, forget about this! I just found something out. Using some special
characters (including some accents included in the name of the messages'
recipient) lowers the character count per message to 70!!!
With that in mind, the length of each message perfectly translates to its
costs. Sorry for all
Ok, it looks like I need to correct something here. The messages
actually had to be splitted into multiple smaller ones. However, the
number of messages being sent according to the provider is still too
high.
The one from August 10 had 356 chars, the one from August 11 had 334
ones, so with 160 ch
Oh, and I decided to send you the syslog via email as it is simply to
long to go through looking for information to censor. While it doesn't
contain the part from August 10, it contains the part when the issue
appeared yesterday.
--
You received this bug notification because you are a member of U
@Alfonso, here you go. :)
I x-ed out all phone numbers and all personal identifiers.
** Attachment added: "upload.tar"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443509/+files/upload.tar
--
You received this bug notification because you are a member
@Alfonso Thanks. :)
I just built the tar file and will x out any personal information when I come
home and then upload them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs
@Niklas, application-failed.log*, application-legacy-dialer-app-.log*,
dbus.log*, ofono-setup.log*, telephony-service-indicator.log* are of
interest. Maybe you could send the logs to me via private e-mail if you
do not feel comfortable posting them here.
--
You received this bug notification beca
@Alfonso, It's not that I can't but that I don't want to upload all of
my application logs. So which ones do you need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to
@Niklas, just do a tarball with it all and attach to the bug ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to SMS being sent multiple times
To manage notifications
@Alfonso, I'll do that later today. Thank you for your reply. :)
What logs from ~/.cache/upstart/ do you need? There are so many in there...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title
@Niklas, the radio log for mako is not very useful, could you attach
/var/log/syslog and ~/.cache/upstart/* ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to SMS being
Yes, that's true. Instead, there is an "assertion failed" block less
than 5 secons after each SMS that shows up in the web interface.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
Hig
in the attached log file of Cooment #16 is nothing about AT cmds or SMS,
please check;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to SMS being sent multiple times
T
And it just happened again. I think I'll stop using my phone for SMS
now!
** Attachment added: "again.png"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443024/+files/again.png
--
You received this bug notification because you are a member of Ubuntu
Bu
Here's the log. (I x-ed out what I thought were some personal
identifiers.)
** Attachment added: "radio.out"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443013/+files/radio.out
--
You received this bug notification because you are a member of Ubuntu
(Btw, I'm using a SIM card from the German provider "Aldi Talk".)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
Title:
High costs due to SMS being sent multiple times
To manage notification
Here's the new screenshot from my provider.
** Attachment added: "provider.png"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443015/+files/provider.png
** Description changed:
- When sending text messages, Ubuntu displays the loading spinner forever.
This happened again yesterday. With GOOD network connection!!! But this
time I was able to fetch the log file using the command Matthias posted.
** Description changed:
+ When sending text messages, Ubuntu displays the loading spinner forever.
+ In the provider's monthly reports, I can see that t
this is how the SMS could be monitored on sending to the modem, but only
"online" or short after the sending:
root@ubuntu-phablet:/home/phablet# /system/bin/logcat -b radio | tee
/tmp/radio.out
(btw: one should better use: /system/bin/logcat -b radio -v time
to get as well the timestamps)
...
@Alfonso: Thank you very much for your response. I really hope that this
will be fixed soon because I agree with your comment from the mailing
list that this is "worrying".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
the AT chats can be monitored online from the ring buffers with:
$ sudo /system/bin/logcat -b radio
but this does not help to analyze weeks later what was going on :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
what we need here is the log file of the AT cmds chated with the modem;
if there is rumor that it might go wrong (in bad network conditions)
Canonical should clarify how to get them and how to make sure that they
are not purged in short time;
--
You received this bug notification because you are
What brings my attention here is that apparently the receiver is seeing
only one message (comment #7). It is possible that the receiver phone
detects receiving 2 messages that are exactly the same and shows only
one, but I would say that is not usual.
I would like to know if in some case the recei
Yes, after converting it to the right time zone (UTC+2) it becomes
21:31:58.664 21:32:05 ... 21:32:45
13:31:17.015 13:31:21 ... 13:31:32.
As I remember seeing the phone trying to send it for a relatively long
time on July 12th, it really seems as if there is some issue with
queueing the messa
comparing the database timestamps and the provider times (from the
screenshots) we see:
databaseprovider
19:31:58.664 21:32:05 ... 21:32:45
11:31:17.015 13:31:21 ... 13:31:32
i.e. (ignoring the 2 hour diff due to TZ) it seems that the database
timestamp is made when the SMS is "qu
a) I sent one SMS every time.
b) Those were short enough to be sent as one SMS by the provider.
c) The receivers' phones are displaying only one SMS.
d) The MySQL database has only one entry both times.
For the first screenshot its timestamp is 2015-07-12T19:31:58.664
for the second one it sa
Thank you for your reply, Matthias!
There is only one line in the database per message. Both rows have a
messageStatus of 4 which seems to be correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/148
What I do not fully understand is: AFAIK SMS is sent upstream to the
provider with AT cmds, like this example:
AT+CMGF=1
OK
AT+CMGS="+49170xx"
This is the text message.
+CMGS: 4711
OK
(+CMGF=1 is text mode, =1 PDU mode).
The response from the provider could be OK or ERROR. Have you looke
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: telephony-service (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480554
T
Another one.
** Attachment added: "SMS2.png"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437380/+files/SMS2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
The worst one.
** Attachment added: "SMS.png"
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437379/+files/SMS.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
32 matches
Mail list logo
