Keyguard currently relies on being in the system process to grab the
given user's widgets. When we split keyguard into a new process,
it will need to have access to user-specific info to instantiate a
specific user's widgets. In order to accomplish this, we add an
explicit userid to each binder call as well as new permission
check to allow keyguard access.
This also fixes a potential race condition of having an incorrect user id
due to an async call to change the user. Every binder call now has a specific
user id. The user id is either the calling process user's id or an explicit
one passed by applications like keyguard. It is created once when an
AppWidgetManager is instantiated and remains for the lifetime of the object.
Change-Id: Iec767fb399677b3cf2f9c0993e06b49951eb1f66
Fixes the flashes in name and icon in Battery usage screen when refreshing.
Bug: 8219466
Some earlier refactoring must have messed up the cache's scope. It will now
avoid reloading name and icon if already present in the cache.
Change-Id: I99c1f14dd53828dcb74cf12c02c47628e2e64d30
* commit 'ff5b96fb19e3a56a8803547a0c9cd11cfd97746c':
Use updated enterprise API
Fix EAP field display for a new network
Allow only valid EAP configs
Update enterprise API usage
We now hide certain EAP fields based on the type chosen. For a
new network, we should set a default and handle this the same
way
Change-Id: I9c8605694ba51bc588a49f711dcf31517ea3f6e4
We allow configuring all possible EAP fields today even though
some of the configs make no sense and will not result in a
successful connection.
Allow only support configs for various EAP methods
Change-Id: I2e3e8d4d6203acb2eac8cd645df39e1a9ca579ab
Also, remove the unnecessary keystore lock/unlock checks since these
are now controlled at lockscreen
Change-Id: If65c4029d4cf2b8377fbc3512c9f691572125995
- Add new labels for media ops.
- Fix crash due to missing boolean entry for access notifications op.
- Fix updating op category lists to remain stable (not jump
back to the top).
Change-Id: I505cfd91b1ff92587a627d33f3ac7a21145a9bbd
# By sunil duttu
# Via Android Git Automerger (1) and others
* commit '5c879e48eddfe617125733f2be46854a0266a23b':
P2PSetting:Avoid p2p_find on group removal event
# By sunil duttu
# Via Gerrit Code Review (1) and sunil duttu (1)
* commit '414d9e9c6928581d4f91b008c109a6a4630bfaae':
P2PSetting:Avoid p2p_find on group removal event
We now hide certain EAP fields based on the type chosen. For a
new network, we should set a default and handle this the same
way
Change-Id: I9c8605694ba51bc588a49f711dcf31517ea3f6e4
Immediately after group termination p2p_find is being issued
from settings and this causing issue whenever user sends
connection request immediately after group_removal_event.
Change-Id: I41e5f520f7d9475d0ec890d40eea172d9d66d06e
# By sunil duttu
# Via Android Git Automerger (1) and others
* commit '6639dee497304c359141caf9b0452699a6d64aa9':
wifiSettings: Updating the networkinfo on supplicant event
# By sunil duttu
# Via Gerrit Code Review (1) and sunil duttu (1)
* commit '203631b24cd3947bcba2ab24789e4cfec487eff7':
wifiSettings: Updating the networkinfo on supplicant event
In framework we update the networkId on supplicant state change
these changes in the network info should be reflected in settings.
there by updating the networkinfo.
The problem we are facing without this fix is when we have single
saved AP profile Switching off the AP when we are in connecting
tate resulting in a behavior Where UI keep showing connecting
to that AP instead of showing it as out of range.
Change-Id: I04073b9a4068f4b75216ebfd431adc126583f15c
