[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-07-01 Thread Bill Filler
** No longer affects: touch-preview-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206941 Title: [ofono][rild] Retries property does not not work To manage notifications about this bug go

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-05-07 Thread Launchpad Bug Tracker
This bug was fixed in the package ofono - 1.12.bzr6858+14.10.20140501-0ubuntu1 --- ofono (1.12.bzr6858+14.10.20140501-0ubuntu1) utopic; urgency=low [ Tony Espy ] * [ Tony Espy ] build, gril, rilmodem, plugins/ril, test: call- forwarding support. [ Alfonso Sanchez-Beato ]

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-04-29 Thread Tony Espy
** 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/1206941 Title: [ofono][rild] Retries property does not not work To manage

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-04-29 Thread Tony Espy
** Changed in: ofono (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/1206941 Title: [ofono][rild] Retries property

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-04-25 Thread Alfonso Sanchez-Beato
Pull request https://github.com/rilmodem/ofono/pull/79 fixes this partially. The number of available retries for a password will be shown in the Retries property of org.ofono.SimManager when the password has been incorrectly entered, but there is no guarantee that the property will hold any

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2014-04-25 Thread Alfonso Sanchez-Beato
Note: the previous fix works just for mako, not for maguro. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206941 Title: [ofono][rild] Retries property does not not work To manage notifications

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-12-04 Thread Tony Espy
** Changed in: touch-preview-images Assignee: Tony Espy (awe) = (unassigned) ** Changed in: ofono (Ubuntu) Assignee: Tony Espy (awe) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-10-29 Thread Alfonso Sanchez-Beato
We recently discovered that the number of retries returned when entering the PIN/PUK is unreliable in the current RIL implementation of Google devices (Galaxy Nexus and Nexus 4 return always 0 and 1 respectively in ENTER_SIM_PIN/PUK). So, for these devices we will never be able to display the

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-10-17 Thread Michael Zanetti
Tony, any update on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206941 Title: [ofono][rild] Retries property does not not work To manage notifications about this bug go to:

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-10-14 Thread Alfonso Sanchez-Beato
I have tested the SIM/PUK behaviour in Galaxy Nexus with Android 4.3, and it never displays the retry counter of either the PIN or the PUK, not even when you have entered any of those wrongly at least once. Interestingly, an old Huwaei phone I have with Android 2.2 prints always the retry counter.

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-20 Thread MichaƂ Sawicz
The only thing I can think of about improving this situation would be to cache/store the number of remaining tries (per-SIM), but obviously that's unreliable if the SIM is taken out and used in another phone... I'm not sure on the internals of RIL, but I assume if we'd like to fix it, we'd need

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-20 Thread Tony Espy
Unfortunately, rild is a binary blob. We're also constrained by the generic RIL API which doesn't offer any messages which allow us to query the PIN/PUK retry counts independent of an action. In theory, this is something that could be fixed for a specific OEM by means of a custom RIL

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-20 Thread Michael Zanetti
In this case that's probably the best we can do, yes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206941 Title: [ofono][rild] Retries property does not not work To manage notifications about

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-19 Thread Tony Espy
So is this is a pretty obvious, function-didn't get implemented type of bug. The rilmodem's sim modules doesn't define a function for ofono_sim_driver.(*query_pin_retries). On the RIL side, there's no RIL message that can be used to query the various PIN retry counts. Instead, the RIL PIN

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-19 Thread Michael Zanetti
The UI in the design shows a label with the text: x attempts remaining To show that I would need to get the value somehow. I couldn't find anything else in the ofono API that would give me this values. Note that rebooting the phone does not reset the remaining attempts in the SIM card. So your

[Bug 1206941] Re: [ofono][rild] Retries property does not not work

2013-08-19 Thread Tony Espy
Yea, forgot about the power down case ( which is rare, but could happen ). I re-reviewed the RIL API, and there really is no other way to get the counts. So, I guess the best we could do is only initialize 'Retries' after the first attempt to enter a PIN via EnterPin was invoked, and also the