Skip to content

GitLab

Switch branch/tag
  1. 22 Apr, 2015 2 commits
    • Robert Greenwalt's avatar
      Merge "Telephony: Fix call forward info logging." · e9b0fcbc
      Robert Greenwalt authored
      e9b0fcbc
    • Gao Rong's avatar
      Telephony: Fix call forward info logging. · e2015471
      Gao Rong authored 
      Currently, QUERY_CALL_FORWARD_STATUS would use array to store call info
response, from BP side. So RILJ would just show the array hash code
instead of each field in the array, it would like this:
< QUERY_CALL_FORWARD_STATUS [Lcom.android.internal.telephony.CallForwardInfo;@41573f30]

This code change would parse the array field one-by-one, and show
each field in RILJ, like this:
< QUERY_CALL_FORWARD_STATUS { [not active reason:0 serviceClass:255 'null' 0seconds] }

This is very helpful for developer tracking call forward related issues.

Change-Id: I5485578c70f5344c75294d56583896a2d87d5d29
      e2015471
  3. 11 Mar, 2015 2 commits
  5. 14 Feb, 2015 2 commits
  7. 13 Feb, 2015 1 commit
  9. 12 Feb, 2015 3 commits
    • Robert Greenwalt's avatar
      am e5c8dd51: am 40dc7774: Treat a SIM power cycle as first boot. · 3ebb983f
      Robert Greenwalt authored 
      * commit 'e5c8dd51':
  Treat a SIM power cycle as first boot.
      3ebb983f
    • Robert Greenwalt's avatar
      am 40dc7774: Treat a SIM power cycle as first boot. · e5c8dd51
      Robert Greenwalt authored 
      * commit '40dc7774':
  Treat a SIM power cycle as first boot.
      e5c8dd51
    • Robert Greenwalt's avatar
      Treat a SIM power cycle as first boot. · 40dc7774
      Robert Greenwalt authored 
      TL;DR - forget the previous subId used only for optimization
purposes if we get a SIM_READY notification.

We moved some code that poked the modem from a SIM_READY handler
to a onSubscriptionChanged handler and also protected it
with logic to only fire if the subId changed.  This caused
us to not poke the modem on SIM power cycle.  Some modems
do a SIM power cycle on airplane mode.  The result was
on these modems we weren't causing the modem to register with
the network after airplane mode.

This was often masked because if we were setup to try a
data call these devices were configured to try the data call
regardless of data registration and the act of trying a data call
would cause the modem to register with the network.

If during airplane mode you had turned on wifi, telephony would
stop trying to setup a data call (so we don't poke the network
all the time when on a better wifi connection) and the restoration of
that data request has been blocked until data-registration in the
new multisim code.

bug:19194287
Change-Id: I21b76b7c62a6161d8422b11a831c3747591c56f3
      40dc7774
  11. 10 Feb, 2015 3 commits
  13. 06 Feb, 2015 4 commits
  15. 05 Feb, 2015 6 commits
  17. 04 Feb, 2015 5 commits
  19. 03 Feb, 2015 3 commits
  21. 02 Feb, 2015 3 commits
  23. 30 Jan, 2015 6 commits