We always switched to combined view when we tapped "Starred" in a
mailbox list. This was confusing since tapping to show the mailbox list
will take you to the mailbox list for the combined view, even if there's
only one account on the device! Other confusing things happened like
showing coloured account chips, even if there's only one account.
This fixes it so that we pass the account ID when building the
selection. Lots of wiring to make it happen, but very little change
overall.
Bug: 5388326
Change-Id: I1fe52f211cceca0c1b26581e200f3c7adcd0734a
This only applies for the main EmailActivity. The compose window still
uses the user-visible setting for "Default account" as the default
account when handling intents like "mailto:" links.
In the future, we should probably just remove that setting, now that we
remember the last account in the reading-email case.
Bug: 4460450
Change-Id: I4b3e7c9e13b7e89320891346383780cd670492ae
When the socketfactory init code was moved, I forgot to re-add in the check
to skip hostname verification. This made "Trust all SSL certificates"
checkbox useless.
Bug: 5450563
Change-Id: Ie4cba749aaf8c0fd9f9c43f09ebf354c6600d4f0
We were never clearing the error state when typing in a field that
needed to be non-empty.
Bug: 5422268
Change-Id: Iabe8c6f6c348b4210695c3eeff98e79e60f83d08
- make subject text have the proper text flags
- remove unneeded v13 overlay, and fix the main style to not have
DarkActionBar (which is wrong)
Bug: 5430026
Change-Id: I44d72f89118f03be89ed3ea1a5516321798d9fa1
Also do some cleanup - we were creating a background task for opening a
message, when in the common case we don't need to hit disk for any
reason. This was also an issue since the async opening of the message
caused the list item to go into an "active" state, changing its colour
(this problem still exists in starred view now, though)
Bug: 5222509
Change-Id: Ie94109df42406fd6eec1e1255bb0827626ba0628
note that this applies for the account name.
the actual user name has inputType=textPersonName, which I guess the
framework folks have decided should be spellchecked, so I'm leaving that
as is
Bug: 5418912
Change-Id: Ie39aa64e59940415b4d8d9a275af07c902937234
Bugs: 5383037, 5165745, 5163232, 5162668, 5162667, 5162328
Changes include making text friendlier, more consistent
use of wording, capitalization, punctuation, simplification
of dialogs. Changed spelling of Wi-Fi to WiFi.
Change-Id: I6d1656416d1844fc361bbedc1d7e98cb5cc8af6e
Revision based on review feedback from Ben.
Makes text vertically and horizontally centered
Also makes it more robust to text size changes
Bug: 5406487
Bug: 5360657
Change-Id: I5183c988163381237cf3aa38121075b7281df695
* I don't know how the timestamp can be zero for a message, but we
shouldn't crash, and it's late for adding new localizable text
Bug: 5410814
Change-Id: Idf1c8b0d4c0b7e0e2b2466643ea52e5244d1bb5f
In cases where the account gets removed, we accidentally hold a stale
cursor. This leaves a ticking bomb, which generally explodes when the
list tries to save state.
Bug: 5367199
Change-Id: Ibcd0c281c9668778f7d1d2abba472ffff8b22879
* We were using the deprecated ConnectivityManager for this; we should now be
using the setting in ContentResolver
* Also, remove broadcast receiver code that is no longer relevant
Bug: 5405352
Change-Id: I985a95071aea92d235a2708925f775b817ba2328
The data is usually really quick, but it's enough to cause it to flicker
if we set it with an empty adapter first.
Bug: 5087874
Change-Id: I2fc37751edcaa8ffeee144b85417b48e94b4ba4f
