Detect recycle called twice always (and when DEBUG_RECYCLE is on, we
detect recycle called twice or called zero times, and we show a stack).
Bug: 231799394
Test: manual (calling recycle twice)
Change-Id: I1dd9f392ee916edd9c598085a1c19dbdd3ce957f
Merged-In: I1dd9f392ee916edd9c598085a1c19dbdd3ce957f
The output of derivePassword() is a key (byte array, not hex encoded),
not a password. Therefore, rename it to deriveSubkey().
No change in behavior; this is just a cleanup.
Test: atest SyntheticPasswordTests
Change-Id: Ie3d74a579963bcbe63fc93c1b4c436c2aba8c342
Now, when the condition doesn't meet, smart idle maintenance service
doesn't update write amount record. Fixed it, since it should be updated
every period.
Test: check smart idle maint log of StorageManagerService
Signed-off-by: Daeho Jeong <daehojeong@google.com>
Change-Id: I339109fcaa821620a3b9b4b8c49e25fd18d03cf3
Add clarification that this flag can only be applied by privileged apps, and will be ignored otherwise.
Bug: 236932598
Change-Id: I78db484b9d479abed67689c827707b6f141b2c00
Test: N/A
This application can be installed as a signature app. It displays
all available rollbacks, and will manually trigger the rollback of
all selected rollback IDs. This application will not trigger a
reboot in the case of staged rollbacks.
Test: m SampleRollbackApp, adb install. Manually install a train
with rollback enabled and reboot. Verify that the available
rollback is displayed, and that the rollback can be committed.
Bug: 220204580
Change-Id: Id2e5afac9e25532d8c24ea2b803c07dcfdb84d85
This is going to be disted instead of the monolithic one being
used currently.
Bug: 235140934
Test: m sdk-annotations{,-system}.zip and diff; manual spot checking
Test: m sdk dist && diff out/dist/system-data/annotations.zip with this
Change-Id: I9874f88e933a8b804a73638e6bac7a9d312c7c9f
It's clearer to define the module in Android.bp, and keep
our custom Go code to the minimal. The only thing the go
code really needs to do is create a "all module annotations"
module. This matches the pattern of the other modules here (the
pattern was invented after sdk-annotations.zip was first
migrated).
Bug: 235140934
Test: m sdk-annotations.zip before/after (no diffs)
Change-Id: Iae246081bcf4e5177d1da98c2e01c702fb349a22
what is the mean of SYNC_DISABLED_MODE_NONE?
form code, it may should be "sync is not disable"
Signed-off-by: zhangjincheng <zhangjincheng@xiaomi.com>
Change-Id: I0017001966a9bee524e92803a1bc48a436f68129
The "adb_temp_keys.xml" file is used to keep track of each ADB key and
when it was previously connected. It also keeps track of authorized WiFi
networks. It is written correctly, however, the parser currently is
unable to read the file that it wrote, meaning that:
1. ADB keys never properly expire
2. WiFi APs are never properly restored
Furthermore, because of complex interactions with restoring the adb_keys
file in Test Harness Mode, duplicate keys get appended repteatedly to
the adb_keys file if they're not in the key map.
This cleans up the file, making it more testable, adds tests for the
previously broken functionality, and just performs some simple
restructuring of bits of the code that were error-prone.
Now, the adb_keys file is nothing but a view of the temp keys file. When
keys are added to the temp keys file, we completely rewrite the adb_keys
file with the set of keys present in the temp keys file, meaning that
duplicates cannot be added.
This also introduces a method for other system services (primarily for
TestHarnessModeService) to notify the AdbDebuggingManager that the key
files were modified, and it should reload the state.
Bug: 236299256
Test: atest AdbDebuggingManagerTest
Change-Id: Iae955aca17e873288d58b16f184bd4d325d50d86
Android's Trace class seems to have a 127 char limit to section names (which is
not enforced running locally), which should no longer be hit when this
change goes through.
Bug: 236230898
Test: atest ByteBufferBulkPerfTest
Change-Id: I0ff3f13bc0d22bc412dfedad2772fc8c341f8f0c
