For this concrete bug I find it interesting that the file on the SIM
does exist and that its content is 112 911 (otherwise we would have
had the default ofono list, which does include 110 and 119).
@Wenfang, could you please attach the output of the getprop command?
Some properties are related to
I have checked that in my Android phones I can try to call non-emergency
numbers with locked or no SIM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444883
Title:
Emergency numbers for China
Public bug reported:
nuntium exits when call to ofono DBus method
org.ofono.PushNotification.RegisterAgent fails. Log is:
2015/05/14 02:13:50 Received GetServices()
2015/05/14 02:13:51 Initializing modem /ril_0
2015/05/14 02:13:53 Modem online: true
2015/05/14 02:13:55 Identity added
** Branch linked: lp:~alfonsosanchezbeato/nuntium/upstart-respawn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456097
Title:
nuntium does not re-start
To manage notifications about this bug go
Public bug reported:
nuntium does not re-start when it exits, or when SIGTERM/SIGKILL signals
are sent to the process.
** Affects: nuntium (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: nuntium (Ubuntu)
Status: New = Confirmed
--
You received this bug
The attached upstart configuration file solves the issue.
** Attachment added: nuntium.conf
https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1456097/+attachment/4399359/+files/nuntium.conf
** Changed in: nuntium (Ubuntu)
Assignee: (unassigned) = Alfonso Sanchez-Beato
The same error (ContentNotFoundError) can be also seen when *receiving*
an MMS, when *uploading* the confirmation of MMS received to the server.
The MMS is never shown as received. Changing the description.
** Summary changed:
- MMS wrongly reported as sent
+ MMS wrongly reported as sent or not
Changes for nuntium in
https://github.com/ubuntu-phonedations/nuntium/pull/18
** Changed in: nuntium (Ubuntu)
Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Changed in: nuntium (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454625
Title:
Cannot send MMS messages with combined contexts with WiFi
The regression is due to NM setting DEVICE_IFACE to ril_0 in version
0.9.10.0 instead of /ril_0 as in 0.9.8.8.
There has been a change in nm-modem-ofono.c:nm_modem_ofono_new that
explains this (MODEM_UID is skipping the slash in the latest version).
The patch that creates nm_modem_ofono_new is
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
- enabled, for some operators. Combined contexts are able to handle
+ connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$
Public bug reported:
Cannot send MMS messages with combined contexts in case the WiFi is
enabled, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
** Summary changed:
- Cannot send MMS messages with combined contexts with WiFi enabled
+ Cannot send MMS messages with combined contexts with WiFi connected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@cm-t, kind of agree on the usability comment. Note however that most of
the confusion comes from the operator providing the data that you fill
in Android phones, and much of that is not really needed. We are also
trying to improve our DB to minimize the chance of having to use the APN
editor.
--
This is a regression: in the same situation MMS are being sent in RTM.
$ system-image-cli -i
current build number: 276
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-05-13 16:13:32
version version: 276
version ubuntu: 20150508
version device:
@cm-t, taking a look at comment #1 you are not filling properly the
form. MCC/MNC are not necessary (they are stored in your SIM), neither
the type (it is implied as you are filling the MMS APN). Please try
again filling APN MMS and MMSC and leave the other fields empty, as
they are not specified
** Changed in: ofono (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338758
Title:
Re-provisioning GPRS/MMS contexts requires re-starting ofono
To
Implementation in
https://github.com/rilmodem/ofono/pull/180
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338758
Title:
Re-provisioning GPRS/MMS contexts requires re-starting ofono
To manage
** Also affects: ubuntu-download-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-download-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Evan, the issue you describe is different and is reported in bug
#1447748
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417445
Title:
SIM is not reported as locked after re-starting ofono
To
** Changed in: telepathy-ofono (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306693
Title:
ofono modem Online property is not set when restarting ofono
To
Adding
policy user=phablet
allow send_destination=fi.w1.wpa_supplicant1
send_interface=org.freedesktop.DBus.Introspectable
send_member=Introspect
send_type=method_call
When you are registered in a network with different MCC/MNC codes to the
ones in your SIM, you are roaming unless the MCC/MNC of the network you
are registered to is in a list that is stored in a file on the SIM.
In this case two operators with different codes have recently merged, so
it is
Examining output of dbus-monitor --system shows that URfkill is
actually emitting signals that can be used by push-client to track the
status of the radio devices, for instance:
signal sender=:1.3 - dest=(null destination) serial=85
path=/org/freedesktop/URfkill/WLAN;
@carharttguy, probably not. Which is your operator? As a first step I
would use the APN editor and add an APN with your operator's setting.
Also output from scripts:
/usr/share/ofono/scripts/list-modems
/usr/share/ofono/scripts/list-contexts
would be useful.
--
You received this bug
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug (which leds to screenshot in comment #3) has been produced with
a modified ofono that was fixing bug #1436820. This modified ofono shows
the number of retries on boot and when the SIM gets toasted after
introducing 10 times a wrong PUK (both things were not happening
before).
Package
In fact I would not expect neither of the screenshots in comments #2 or
#3, but something saying that the SIM is unrecoverable AND a way to
dismiss that warning and enter the phone.
The SIM is unrecoverable when following ofono properties have values:
org.ofono.SimManager.PinRequired = puk
While testing the ofono landing that drops the call, I have seen many
problems with dialler/telephony service after calling/setting
FM/unsetting FM. If I do not re-start the dialler app, audio is not
working when pressing buttons. I can dial, but I cannot drop the call
(from the app, the ofono
@Tony
Yes, I checked in both krillin and arale.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436820
Title:
Blocked SIM card keeps on asking for PUK
To manage notifications about this bug go to:
@Tony
No, I cannot reproduce anymore easily. That SIM has now credit, and even
when it did not have the sequence in #26 was not happening any more
after a couple of days.
What I interpret from syslog in #26 is:
1. Apr 14 07:48:54 ubuntu-phablet nm-dispatcher: Dispatching action 'down' for
Silo 6 solves the issue on boot, we should land it.
However, as said in comment #6 nuntium is not able to recover from an
ofono re-start (this is not deterministic, in some cases it is actually
able to recover, but not always), so we can keep the bug open until that
gets sorted out.
--
You
@Sergio
No, it does not. Unless there are a lot of re-spawns in a short amount
of time, as pointed out in comment #8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441135
Title:
Cannot send MMS
@Tony
Just got it once, and I have not been able to reproduce. I was testing
the fix for the empty data call list iirc, but I do not know if ofono
was patched at that moment or not. I think that the only thing we can do
for the moment is to keep an eye on this so we can get more traces if it
@Tony, ok, probably after applying the ofono patch it is difficult to
have this happening in RTM so it is not worth the effort. But I think we
should fix this in vivid / NM 0.9.10, if the routing logic is still the
same.
--
You received this bug notification because you are a member of Ubuntu
This PR fixes the issue on the ofono side:
https://github.com/rilmodem/ofono/pull/177
However, there is still some problem in telepathy/dialler even with the
patched ofono. Doing:
1. Start call from dialler
2. Set flight mode (call is dropped)
3. Unset flight mode
4. Start a second call from
)
Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445580
Title:
Impossible to end a call after switching to airplane mode
To manage
** Description changed:
Cellular data is not activated in ~50% of the cases in arale after
setting then unsetting flight mode.
I obtained the attached log this way:
1. Disabled wifi (to have less noise) and removed syslog (to make smaller the
attached one)
2. Reboot
3. See
Ok, for some unknown reason I downloaded
nuntium_0.1+14.10.20141013-0ubuntu1 instead of the last version. Weird,
because I did it in arale so it is vivid. apt-get source nuntium gives
me now 1.4-0ubuntu6. I did apt-get build-dep nuntium and used the
installed go, which seems to be gogcc.
Anyway,
Public bug reported:
It is not possible to send an MMS in case cellular data is disabled.
This might look as an invalid bug because MMS needs cellular data to
work, but it is not that obvious. For instance, in Android you can
send/receive an MMS even when you have set cellular data to off.
The
** Changed in: nuntium (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/1441135
Title:
Cannot send MMS when nuntium started before ofono
To manage
Public bug reported:
I tried to send an MMS. It took a bit longer than usual (~1 minute).
While doing it I was checking the list of open contexts with list-
context ofono script. The MMS IP context was opened at a point, but then
it was closed, and messaging app still reported it was sending the
/home/phablet/.cache/* and /var/log/syslog
** Attachment added: mms-not-sent.tar.gz
https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1444840/+attachment/4376888/+files/mms-not-sent.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Probably this change fixed this
http://bazaar.launchpad.net/~go-dbus/go-dbus/v1/revision/131
(2014-11-13)
Current nuntium is from 2014-10-13
(side thought: we need shared libraries for GO ASAP... fortunately
people is already working on this :-)
--
You received this bug notification because
... so we must land a new nuntium package to solve this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441135
Title:
Cannot send MMS when nuntium started before ofono
To manage notifications
I have discovered that if I dowload and build latest nuntium and its
dependencies:
https://github.com/ubuntu-phonedations/nuntium
lp:go-dbus/v1
lp:go-xdg/v0
lp:udm
, using that binary the error does not happen anymore (nuntium can
handle the case of ofono starting after it).
My guess is that
Public bug reported:
Cellular data is not activated in ~50% of the cases in arale after
setting then unsetting flight mode.
I obtained the attached log this way:
1. Disabled wifi (to have less noise) and removed syslog (to make smaller the
attached one)
2. Reboot
3. See cellular data is on:
Side note: I have created bug #1444314 to address a weird thing I have
seen in the files attached in comments #7 and #8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435328
Title:
Leaving Wifi
. However, adding a default route with
ip route add default dev ccnmi0
makes the network reachable. This means that Attached should be TRUE for
sure.
Seen on krillin/vivid.
** Affects: ofono (Ubuntu)
Importance: Undecided
Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato)
Status
Reproduced. syslog attached. Steps:
1. Start the phone
2. Check that you have network connectivity
3. Disable WiFi
4. Check that you cannot connect to network although cellular data is ON.
The mobile context was up, cnmi0 was up, phone was attached, but ip
route showed nothing.
Adding a default
@Tony, great catch! I have tested your changes and reproduced the bug.
Now list-contexts does not show any active context when ccmni0 is down.
However, NM is not able to recover from this situation. It tries to add
routes before we get the UNSOL_DATA_CALL_LIST_CHANGED event in ofono.
After that
Some more traces when reproducing the bug:
/system/bin/logcat -v threadtime -b main -b radio
...
04-14 09:31:21.057 1844 1861 D use-Rlog/RLOG-AT: +CGEV: NW DEACT IP,
100.125.255.239, 1
...
04-14 09:31:21.058 1844 1861 D use-Rlog/RLOG-RIL: configureNetworkInterface:
Down E
04-14
My comment #23 is probably a red herring, as it looks like in the end
all DNS servers are registered in dnsmasq, and it sends queries to all
available servers. So I am hiding it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Jonas, yes, it can be used for MMS too. There is in fact no restriction
on how this flag is used on the ofono side. Whatever needs to be
enforced is something between system-settings and NetworkManager. For
ofono, it is just a property that can be read and written from outside,
and it is not used
Operator added in change https://code-review.phablet.ubuntu.com/#/c/363/
** Changed in: android (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439272
Title:
Public bug reported:
Cannot send MMS in vivid image #163, arale.
$ system-image-cli -i
current build number: 163
device name: m75
channel: ubuntu-touch/vivid-proposed
last update: 2015-04-06 12:29:08
version version: 163
The reason might be that nuntium is being started before ofono:
Marked as won't fix, as we are not using MBPI any more.
** Changed in: mobile-broadband-provider-info (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253586
** Changed in: android (Ubuntu)
Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439272
Title:
[APN] Add settings for MVNO
The bug might be related to a problem with DNS configuration. The
default route is wlan0:
default via 10.0.1.1 dev wlan0 proto static
However, the last line of grep dnsmasq syslog is
Mar 30 15:26:35 ubuntu-phablet dnsmasq[3855]: using nameserver
172.26.38.2#53
which is the DNS provided by
This brach
https://github.com/rilmodem/ofono/pull/173
implements a per-context Preferred property that can be used freely by
the ofono clients to express preference on context activation.
** Changed in: ofono (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug
** Changed in: urfkill (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379807
Title:
urfkill does not wait for modem to be powered to online it
To
** Changed in: urfkill (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392397
Title:
Crash when ofono is respawning fast
To manage notifications
Maybe this trace is the key here:
Mar 24 10:27:01 ubuntu-phablet NetworkManager[1377]: info (ril_0):
device state change: prepare - failed (reason 'no-secrets') [40 120
I have seen this error in some cases where I was unable to start a
cellular data connection. Rebooting solved the issue, and
/scripts/list-modems
** Attachment added: ofonod.gz
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1436820/+attachment/4360734/+files/ofonod.gz
** Changed in: ofono (Ubuntu)
Assignee: Tony Espy (awe) = Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Changed in: ofono
Seems that the APN entry in comment #7 is fine, from joc's log:
Provisioning for MCC 234, MNC 10, SPN 'giffgaff',...
and he was able to start a data connection:
[ /ril_0/context1 ]
Active = 1
Name = giffgaff
Type = internet
MessageProxy = 82.132.254.1:8080
I think the right APN should be:
apn carrier=giffgaff
mcc=234
mnc=10
apn=giffgaff.com
authtype=1
user=giffgaff
password=
mmsc=http://mmsc.mediamessaging.co.uk:8002;
mmsproxy=82.132.254.1
mmsport=8080
Finally, there is a
preloaded=true
line in the giffgaff entry that I have no idea what is for. I have not
seen any reference to it in the AOSP code. Qualcomm specific maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mzanetti, would it be possible to get the output of the list-modems
script? To do that:
1. Insert the blocked SIM
2. Make sure you can adb the device even with a locked screen:
sudo touch /userdata/.adb_onlock
3. Reboot
4. Insert a wrong PUK once
5. Execute:
/usr/share/ofono/scripts/list-modems
Public bug reported:
In case there there is no type field for an entry in the Android APN
DB, we should provision all possible types for that entry. In those
cases, the type is set to PhoneConstants.APN_TYPE_ALL in the Android
code. See:
Change submitted to gerrit with the APN checked by joc:
https://code-review.phablet.ubuntu.com/#/c/362/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434605
Title:
[APN] giffgaff APNs don't have
This PR fixes the bug:
https://github.com/rilmodem/ofono/pull/172
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437200
Title:
In case there is no type field in APN, we should provision for all
@mzanetti, definitely looks like an ofono bug. The PR pointed out by
Tony should help, but anyway I'd like to gather more traces. Could you
modify /etc/init/ofono.override, changing the exec line with the
following 3 lines:
...
env OFONO_RIL_TRACE=
env OFONO_RIL_HEX_TRACE=
exec ofonod -d -P
** Description changed:
- There are several conditions that prevent the APN Editor from being
- available, these include:
-
- 1. Carrier selection is set to manual ( see below for steps )
- 2. Cellular data is disabled for the SIM
- 3. The phone is not registered to a carrier's network
+ APN
I have edited the description and just left the case of APN editor
disabled when cellular data is off.
The other two cases were wrong, I was not able to reproduce them having
data enabled at the same time, so they were red herrings. Also, I was
confused initially and thought that
I think it is perfectly fine to add operators that use the same MCC/MNC
code even if we cannot discriminate with the mvno_* fields. The list of
APN choices will grow, but NetworkManager is supposed to handle that
properly and eventually will get to the right one.
About the position in the file,
Another comment: it will be difficult to get somebody in an operator
that can answer the question about how to detect if it is the owner of
the SIM, unless the phone is sold directly by them.
One thing that should be pretty safe for MVNOs is to check the content
of EF_SPN SIM file and set:
With this fix Christina was able to open a cellular data context:
https://github.com/rilmodem/ofono/pull/170
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435784
Title:
SMS and calls working, but
Public bug reported:
You cannot specify currently the authentication method that should be
used when opening a data context.
Note that upstream ofono currently supports this via the
AuthenticationMethod property in interface
org.ofono.ConnectionContext. This was introduced in release 1.15.
**
Radio logs show error:
+CME ERROR: 149
Taking a look at 3gpp 27.007, section 9.2.2.2:
149 PDP authentication failure
which points in the direction suggested by Tony.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
In order to support devices with LTE modems, a new APN type IA needs
to be supported by the APN Editor.
This APN is sent to the modem using a RIL_REQUEST_INITIAL_ATTACH and is
sent much earlier than a normal the request to setup a data connection.
ofono
It is not required by ofono either. Removing it did not apparently break
anything from the telephony side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240250
Title:
phablet user part of the
I've started my mako and found this problem: no network indicator is
shown.
syslog attached. No indicator-network.log in ~/.cache/upstart (just
gzipped files from previous runs).
indicator-network-service was running and there was no crash file for
it. Restarting indicator-network made the
** Description changed:
Flight mode fails to be set if we have the 3G capabilities set for the
second slot and we have just one SIM, which is inserted in the that
slot.
To reproduce using scripts:
cd /usr/share/ofono/scripts
./set-3g-slot /ril_1
* Reboot the phone (set 3G is
@Tony, sorry, the description was wrong, the error happens for vivid-
proposed, not for RTM (it is a regression introduced by the arale
changes). I was using RTM + ofonod compiled with latest main.
I have changed the description with steps to reproduce it from the GUI
and changing version to
@Tony, answering your questions
1. Setting the second slot as 3G under the conditions commented in the
bug description gets stalled. No direct error shown in the log. The
error is that we are waiting for a change in radio state that does never
happen (second slot reports SIM_LOCKED_OR_ABSENT
The reason for the failure is that the radio state reported for the
first slot is always SIM_LOCKED_OR_ABSENT: radio OFF state is only
reported for the main (=3G) slot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This PR fixes the issue:
https://github.com/rilmodem/ofono/pull/168
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430700
Title:
Cannot set flight mode if the second slot is 3G and we have just
@Ratchanan, thanks for the log. This implies that we should not really
use the index if set to -1 for your modem, but send the request for
selecting an application before. Great to know that you are already able
to register, maybe getting ofonod to work will just need a couple of
minor
ubuntu: 20150310
version device: 20150225-b67e0b6
version custom: 20150216-561-29-186
** Affects: ofono (Ubuntu)
Importance: Undecided
Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato)
Status: New
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) = Alfonso Sanchez-Beato
More combinations are possible...
krillin:
test-ss *31# - Number shown in called phone. Shown status is disabled.
test-ss #31# - Number not shown in called phone. Shown status is enabled.
arale:
test-ss *31# - Number shown in called phone. Shown status is disabled.
test-ss #31# - Number not
More testing reveals that depends more on the operator than on the
phone:
Pepephone operator, krillin, arale and mako:
test-ss *31# - Number shown in called phone. Shown status is disabled.
test-ss #31# - Number not shown in called phone. Shown status is disabled.
Vodafone operator, krillin and
@Patrick, would you mind attaching /var/log/syslog , and possible
urfkill crash files in /var/crash ? Also, could you please describe what
were you doing when this happened?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at the definition of the reply to RIL_REQUEST_GET_SIM_STATUS in
http://androidxref.com/4.4.2_r1/xref/hardware/ril/include/telephony/ril.h
I see that if RIL_CardStatus_v6::gsm_umts_subscription_app_index value
in the parcel is -1, it *should* mean that there is no GSM/UMTS
application in
The only device where this is a real issue is in arale: after switching
on, then off flight mode:
1. The SIM atom is re-created, as in krillin, but not as in mako.
2. The radio is switched off and then on, but differently from krillin the SIM
is not reset.
In mako using flight mode does not
** Changed in: ofono (Ubuntu RTM)
Status: Confirmed = Fix Released
** Changed in: ofono (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422401
The bug happens in fact when we accept the incoming call very fast, when
it has just appeared.
PR for ofono in:
https://github.com/rilmodem/ofono/pull/164
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-system-settings (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/1415833
Title:
Wrong tech set in Cellular screen
To manage notifications
Finally got a Tuenti SIM, and was able to activate mobile data. It took
me two days to buy the SIM, because first time at the shop I was told
that Tuenti systems were down. Next day I called and they said their
system was still down, and finally today I was able to buy it.
@costales told me that
Public bug reported:
The second slot is not detected some times on reboot in krillin after
latest ofono update. It appears as Disconnected in the network
indicator.
Detected in vivid-proposed image #94
** Affects: ofono (Ubuntu)
Importance: Undecided
Assignee: Alfonso Sanchez-Beato
501 - 600 of 808 matches
Mail list logo
