If the RIL_REQUEST_OPERATOR response[2], the numeric for the operator,
is bad use the system property ro.cdma.home.operator.numeric.
bug: 3383515
Change-Id: I090e5ba0cb7e3a7f1dc08d24996e78e489b9cd41
Bug 3422121
Cherry-picked from master's 95472.
With ellipsize, lines starting with a very long word that does not
fit inside the width were simply ignored. Cut the long word instead.
start - widthStart index offset shift in BiDi.
The original ellipsize-end patch that added '...' after the last
word on end-ellipsized lines has been punted in favor of a true
ellipsize support in I.
I believe the StaticLayout calculateEllipsise is a no-op since textwidth <= avail
by construction: fitWidth and okwidth are < outerWidth. The only exception is the
paraEnd != here case in generate (when not a single character fits in width).
This case is exercised by StaticLayoutTest in cts (width of 8 pixels) and revealed
an offset error in widstart.
All in all, it looks like this code was probably never really tested. I tried some
typical text configuration to make sure these changes improved the situation.
Change-Id: I6c2cb26436a21f0f89078c275a89e891f0f23b92
AIOOB exception fix in TabWidget
Bug http://code.google.com/p/android/issues/detail?id=15005
The problem was not specific to the legacy theme. The code that first
measure the tab's width with no contraint was incorrectly using the
mImposedTabsWidth array which could not have the right size if a
child was added.
The first measure after a child is added should indeed crash. Could
be investigated. This fix is sure anyway.
Change-Id: If5015aaa2d5574939fd5d6c6362ed6db94d35d4a
Listen for connectivity changes. If WIFI is connected, check if
we have recently checked for NTP time. If we haven't yet checked the
time or it has been long enough (a day), then connect to the NTP server
and get the latest time. Update the time if it is significantly out of sync.
This doesn't poll the NTP server every time there is connectivity, only
if it hasn't been checked since boot or has been a day.
This fixes the problem that during SetupWizard, we try to contact the NTP
server before there is connectivity and fail. Now, as soon as the user
chooses a WiFi network to connect to, it will update the time before
getting to the Date/Time step. Then as soon as the user corrects the TZ,
the date/time should be correct.
Bug: 3491920
Change-Id: I62664156616510b67ecd6a1c24dd838b98d5204f
The airplane icon is used as a fallback when no
other radios are available *and* the AIRPLANE_MODE_ON system
setting is set to 1. (NetworkController now tracks changes to
the setting via ACTION_AIRPLANE_MODE_CHANGED broadcasts.)
This fixes wifi-only devices, for which the previous logic
did not correctly and consistently detect airplane mode.
Bug: 3489820
Change-Id: I226bb0e977f6a5fd3f2d829ba51ca54c5c910ef3
If PNO is set after the device is disconnected, the scan
alarm should be cleared to prevent both PNO and alarm
being active at the same time
Bug: 3495698
Change-Id: Id48c87fef68a34a05799e6b82de4088e0573009f
Also, start using the 0-bars WiFi icon when necessary;
previously, one bar was the lowest the WiFi icon could show.
Bug: 3488403
Change-Id: I3018685db3cf302d10c5e525a7d2c90f3c664f10
Squashed commit of the following:
commit b1732e9b8bfea4c99bd07907c9aac9fcf1e8b264
Author: Andreas Huber <andih@google.com>
Date: Thu Feb 24 12:05:40 2011 -0800
DO NOT MERGE: Alternate patch for late video issue: seek only the video ahead to the next
syncframe after the current audio media position, leave audio untouched.
Change-Id: I4f6eb4e577147bc12ed2e998bea299f4bcfaf936
related-to-bug: 3375737
commit 5e7282cf0b5c7a613da5e65fd6c8cb33a1058f8e
Author: Andreas Huber <andih@google.com>
Date: Fri Feb 11 13:09:36 2011 -0800
DO NOT MERGE: Start playing (and decoding) audio only after the first video frame has been decoded.
if there's both audio and video content. This gives the video decoder an opportunity
to fill its internal buffer queue at the start of playback.
Change-Id: If17c4243546b1c27c8e5ee43941654d0e36f5ee5
related-to-bug: 3431702
Change-Id: Ic3a6be467ff7ad09da04b1d2bb1a692ee38002b4
By not starting RILReceiver we don't waste any cycles
trying to communicate with a vendor ril which may
not exist. This allows a wifi-only device to operate
as expected and the system to gracefully handle the
missing radio as ril requests will report RADIO_NOT_AVAILABLE.
Change-Id: I6c6f60830486c5f0447b3b9eb44c8b1f2d70c517
