From 214406a8e95348bfea8a65d981e508f35bf5cf21 Mon Sep 17 00:00:00 2001
From: Jim Miller
If you want a SIM-unlocked phone, then you might consider either an Android Dev Phone or the -Google Nexus S. These are SIM-unlocked so that you can use them on any GSM network using a SIM -card. The Android Dev Phones also feature an unlocked bootloader so you can install custom system -images (great for developing and installing custom versions of the Android platform). To find a -a place you can purchase the Nexus S, visit google.com/phone. To purchase an Android -Dev Phone, see the Android Market site -(requires a developer account).
+If you want a SIM-unlocked phone, then you might consider the Google Nexus S. To find a place +to purchase the Nexus S and other Android-powered devices, visit google.com/phone.
Note: When developing on a device, keep in mind that you should
still use the
Date: Mon, 24 Oct 2011 11:10:36 -0700
Subject: [PATCH 03/15] Add getAvailableNetworks.
To allow a operator test to pass we need to manually select
a network. Therefore getAvailableNetworks needs to be implemented
on CDMALTEPhone so that RIL_REQUEST_QUERY_AVAILABLE_NETWORKS is
sent to the RIL/radio.
Bug: 5420630
Change-Id: I8e138b211d42755399a9e30f3e45dde2f579401e
---
.../com/android/internal/telephony/cdma/CDMALTEPhone.java | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/telephony/java/com/android/internal/telephony/cdma/CDMALTEPhone.java b/telephony/java/com/android/internal/telephony/cdma/CDMALTEPhone.java
index 4f50d2483f267..8534810d56c7a 100644
--- a/telephony/java/com/android/internal/telephony/cdma/CDMALTEPhone.java
+++ b/telephony/java/com/android/internal/telephony/cdma/CDMALTEPhone.java
@@ -245,6 +245,11 @@ public class CDMALTEPhone extends CDMAPhone {
return mIccRecords.getMsisdnNumber();
}
+ @Override
+ public void getAvailableNetworks(Message response) {
+ mCM.getAvailableNetworks(response);
+ }
+
@Override
public void requestIsimAuthentication(String nonce, Message result) {
mCM.requestIsimAuthentication(nonce, result);
From 084369fb5e738e4db6ae94b4e24e777bdd9d9c2c Mon Sep 17 00:00:00 2001
From: Scott Main
If this attribute is not set, the activity inherits the theme set for the
-application as a whole — see the
+application as a whole — from the
Must be one of the following values. For more information about the action bar, see the Action Bar developer guide. This attribute was added in API level 14. Must be one of the following values. For more information about the action bar, see the Action Bar developer guide. This attribute was added in API level 14. G|-J&4&`Jx1GIvXF@`
zXtL!_&yjcB#5U|F-NB5BF>{n}1fpwCu0e;59JC>U12=uBvEH%@zH8oAlrHmRSQ)Oz
z$h1#mFB<&ZqrGz|LA+Ex<2Yjl?RmlMv#4GJG>49Ga1*U?B=4b&%i~luj6}=AT*t3A
z<`5d=&XI#|LAz1HJ5Mq?d*(%BS=p5O@5e{CQuBvnm^yizIEUX^O>?w&T>c3&bYw)y
zK0>ri%zbysLfPyFarjB+NVmJP9BM+K3+m#=I<application>
element's
theme
-attribute. If that attribute is also not set, the default system theme is used.
+attribute. If that attribute is also not set, the default system theme is used. For more
+information, see the Styles and Themes developer guide.
+
+
+ Value Description
+ {@code "none"} No extra UI options. This is the default.
+ {@code "splitActionBarWhenNarrow"} Add a bar at
+the bottom of the screen to display action items in the {@link android.app.ActionBar}, when
+constrained for horizontal space (such as when in portrait mode on a handset). Instead of a small
+number of action items appearing in the action bar at the top of the screen, the action bar is
+split into the top navigation section and the bottom bar for action items. This ensures a reasonable
+amount of space is made available not only for the action items, but also for navigation and title
+elements at the top. Menu items are not split across the two bars; they always appear
+together. theme
-attributes; see that attribute for more information.
+
+
+ Value Description
+ {@code "none"} No extra UI options. This is the default.
+ {@code "splitActionBarWhenNarrow"} Add a bar at
+the bottom of the screen to display action items in the {@link android.app.ActionBar}, when
+constrained for horizontal space (such as when in portrait mode on a handset). Instead of a small
+number of action items appearing in the action bar at the top of the screen, the action bar is
+split into the top navigation section and the bottom bar for action items. This ensures a reasonable
+amount of space is made available not only for the action items, but also for navigation and title
+elements at the top. Menu items are not split across the two bars; they always appear
+together.