incremental OTA update issue - Xiaomi Mi A1 Questions & Answers

Hi everyone,
I'm getting following errors while installing incremental ota update.
Code:
11-08 10:13:56.990 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(1060)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
11-08 10:13:56.990 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(1065)] Expected: sha256|hex = 5627E3F89DD3B57B81CE17F4FFD6D4A97DDFB0616DD4BB519215478BCD529738
11-08 10:13:56.990 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(1068)] Calculated: sha256|hex = 1AEAD84DACE6C6306D2132BC17587BE8C5019027B215CCCFB00310AC9FA52121
11-08 10:13:56.991 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(1077)] Operation source (offset:size) in blocks: 79022:2
11-08 10:13:56.991 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(1142)] ValidateSourceHash(source_hasher.raw_hash(), operation, error) failed.
11-08 10:13:56.991 2201 2201 E update_engine: [1108/101356:ERROR:delta_performer.cc(283)] Failed to perform SOURCE_COPY operation 636, which is the operation 620 in partition "system"
11-08 10:13:56.991 2201 2201 E update_engine: [1108/101356:ERROR:download_action.cc(273)] Error 20 in DeltaPerformer's Write method when processing the received payload -- Terminating processing
11-08 10:13:57.278 2201 2201 I update_engine: [1108/101357:INFO:multi_range_http_fetcher.cc(171)] Received transfer terminated.
11-08 10:13:57.278 2201 2201 I update_engine: [1108/101357:INFO:multi_range_http_fetcher.cc(123)] TransferEnded w/ code 200
11-08 10:13:57.278 2201 2201 I update_engine: [1108/101357:INFO:multi_range_http_fetcher.cc(125)] Terminating.
I had modified the build.prop file for enabling camera api2. is it because of that? any idea how to fix this and install the latest update?

I also can't install incremental ota with unlocked bootloader,stock recovery and unmodified system.Only due to unlocked bootloader ota installation failed ,which shouldn't happen.

Related

Gapps authentication?

i have this problem with 4.4.2 omnirom on the Nexus 5. G+ and hangouts are not signing in. i revoked access to my phone to see if it would regrant access (google > security > account permission) , it did and the only thing not signing in is the G+ and hangouts!
any help on this issue, please?. happy holidays.
Also Google Keep keeps re-asking me for authentication.
Happy holidays
yuukimoonstar said:
i have this problem with 4.4.2 omnirom on the Nexus 5. G+ and hangouts are not signing in. i revoked access to my phone to see if it would regrant access (google > security > account permission) , it did and the only thing not signing in is the G+ and hangouts!
any help on this issue, please?. happy holidays.
Also Google Keep keeps re-asking me for authentication.
Happy holidays
Click to expand...
Click to collapse
It seems like your Gapps package is broken. G+ and Keep are fine here.
yuukimoonstar said:
i have this problem with 4.4.2 omnirom on the Nexus 5. G+ and hangouts are not signing in. i revoked access to my phone to see if it would regrant access (google > security > account permission) , it did and the only thing not signing in is the G+ and hangouts!
any help on this issue, please?. happy holidays.
Also Google Keep keeps re-asking me for authentication.
Happy holidays
Click to expand...
Click to collapse
don't use Banks's gapps, leads to
Code:
12-31 08:34:49.219 1397 3382 W GLSActivity: [aia] Status from wire: INVALID_SCOPE status: INVALID_SCOPE
12-31 08:34:49.229 6761 6781 E HttpTransaction: HttpOperation failed [email protected]
12-31 08:34:49.229 6761 6781 E HttpTransaction: java.lang.RuntimeException: Cannot obtain authentication token
12-31 08:34:49.229 6761 6781 E HttpTransaction: at drh.a(PG:64)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at dry.a(PG:194)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at dry.<init>(PG:243)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at dro.a(PG:298)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at dro.a(PG:264)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at dro.r(PG:245)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.apps.plus.service.EsSyncAdapterService.h(PG:528)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.apps.plus.service.EsSyncAdapterService.e(PG:466)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.apps.plus.service.EsSyncAdapterService.b(PG:73)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at ege.onPerformSync(PG:224)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259)
12-31 08:34:49.229 6761 6781 E HttpTransaction: Caused by: android.accounts.AuthenticatorException: Cannot get Oath2 token from GMS
12-31 08:34:49.229 6761 6781 E HttpTransaction: at buq.d(PG:138)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at buq.a(PG:88)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at drh.a(PG:61)
12-31 08:34:49.229 6761 6781 E HttpTransaction: ... 10 more
12-31 08:34:49.229 6761 6781 E HttpTransaction: Caused by: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.gms.auth.GoogleAuthUtil.getToken(Unknown Source)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.gms.auth.GoogleAuthUtil.a(Unknown Source)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source)
12-31 08:34:49.229 6761 6781 E HttpTransaction: at buq.d(PG:135)
12-31 08:34:49.229 6761 6781 E HttpTransaction: ... 12 more
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: [bwm] failed due to exception: java.lang.RuntimeException: Cannot obtain authentication token
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: java.lang.RuntimeException: Cannot obtain authentication token
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at drh.a(PG:64)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at dry.a(PG:194)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at dry.<init>(PG:243)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at dro.a(PG:298)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at dro.a(PG:264)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at dro.r(PG:245)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.apps.plus.service.EsSyncAdapterService.h(PG:528)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.apps.plus.service.EsSyncAdapterService.e(PG:466)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.apps.plus.service.EsSyncAdapterService.b(PG:73)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at ege.onPerformSync(PG:224)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: Caused by: android.accounts.AuthenticatorException: Cannot get Oath2 token from GMS
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at buq.d(PG:138)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at buq.a(PG:88)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at drh.a(PG:61)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: ... 10 more
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: Caused by: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.gms.auth.GoogleAuthUtil.getToken(Unknown Source)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.gms.auth.GoogleAuthUtil.a(Unknown Source)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: at buq.d(PG:135)
12-31 08:34:49.239 6761 6781 E EsSyncAdapterService: ... 12 more
12-31 08:34:49.249 4383 4403 D AccountTypeManager: Registering 1 extension packages
12-31 08:34:49.259 4383 4403 E ExternalAccountType: Unsupported attribute readOnly
12-31 08:34:49.259 4383 4403 D AccountTypeManager: Registering extension package account type=com.google, dataSet=plus, packageName=com.google.android.apps.plus
12-31 08:34:49.269 4383 4403 I AccountTypeManager: Loaded meta-data for 3 account types, 2 accounts in 14ms(wall) 5ms(cpu)
12-31 08:34:49.269 895 1283 I ActivityManager: Killing 4075:com.android.provision/u0a57 (adj 15): empty #17

lots of linux_qmi_qmux_io_wake_lock/linux_qmi_qmux_io_wake_unlock

looking at my logcat I see lots of the following on Android 8.0
09-06 17:57:33.313 631 946 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1 : Operation not permitted]
09-06 17:57:33.313 631 946 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
09-06 17:57:35.873 631 946 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
09-06 17:57:35.874 631 946 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
09-06 17:57:37.153 631 946 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
09-06 17:57:37.154 631 946 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
(slightly edited because this text editor screws with it)
surfing around a bit I found this commit for Nexus 5X
https://android.googlesource.com/device/lge/bullhead/+/95aa2b4e2d6c26ee1b37241bc22ec32a6382d3fb%5E%21/
which launches qmux as root instead of radio
maybe /init.angler.rc also needs this change ... any thoughts?
I have the same logs in my 6P. I have update today to last 8.0 update, October OPR5.170623.007 and those errors keep appearing...
Rooting with Supersu 2.82-SR5
have this problem too
8.1.0
The error still occurs with the november factory image. Version OPR5.170623.011
I have opened an issue report about this problem in Google Issue Tracker, please starred it
https://issuetracker.google.com/issues/67438793
In the new 8.1 version is not fixed the issue
Android 8.1.0 - OPM1.171019.011
Code:
8.1 is not fixed the issue :(
Android 8.1.0 - OPM1.171019.011
12-07 20:15:25.783 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.783 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.784 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.784 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.787 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.787 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.789 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.789 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1 Operation not permitted]
12-07 20:15:25.792 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.792 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1 Operation not permitted]
12-07 20:15:25.796 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.796 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.797 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.797 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.800 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_lock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]
12-07 20:15:25.800 694 1105 E QC-QMI : linux_qmi_qmux_io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: Operation not permitted]

Whatsapp can't record voice notes

EDIT: FIXED! Turns out I had the magisk module "Oneplus 6 stereo speaker mod" installed (not sure why I didn't have the 6t version, maybe that's part of the reason), after uninstalling that everything started working again.
Hey everyone,
so after updating to OOS10 I can't record voice messages in whatsapp anymore. Every other app works fine, even whatsapp calls work, just voice notes are broken.
I know there are a few similar threads but the only proposed solution there is to use WhatsApp Business, which I don't want to.
I've looked at the logcat while trying to record a message and there's a few error messages thrown by various audio drivers
Code:
01-04 20:34:42.610 824 29193 E soundtrigger: audio_extn_sound_trigger_update_stream_status: invalid input device 0x0, for event 3
01-04 20:34:42.612 824 29193 E ACDB-LOADER: Error: ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE Returned = -19
01-04 20:34:42.612 824 29193 E ACDB-LOADER: Error: ACDB AFE returned = -19
01-04 20:34:42.699 824 29193 E msm8974_platform: platform_set_channel_map: Could not set ctl, error:-22 ch_count:2
01-04 20:34:42.793 961 1026 E SurfaceFlinger: screenshot by : /system/bin/surfaceflinger
01-04 20:34:43.024 961 1026 E SurfaceFlinger: screenshot by : /system/bin/surfaceflinger
01-04 20:34:43.134 824 11979 E audio_route: unable to find path 'speaker-dmic-endfire-whatsapp'
01-04 20:34:43.137 824 11979 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
01-04 20:34:43.137 824 11979 E ACDB-LOADER: Error: ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE Returned = -19
01-04 20:34:43.137 824 11979 E ACDB-LOADER: Error: ACDB AFE returned = -19
01-04 20:34:43.140 961 1026 E SurfaceFlinger: screenshot by : /system/bin/surfaceflinger
01-04 20:34:43.146 824 11979 E audio_hw_primary: start_input_stream: cannot set hw params: Invalid argument
01-04 20:34:43.148 824 11979 E audio_route: unable to find path 'speaker-dmic-endfire-whatsapp'
01-04 20:34:43.222 824 11979 E audio_route: unable to find path 'speaker-dmic-endfire-whatsapp'
01-04 20:34:43.225 824 11979 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
01-04 20:34:43.226 824 11979 E ACDB-LOADER: Error: ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE Returned = -19
01-04 20:34:43.226 824 11979 E ACDB-LOADER: Error: ACDB AFE returned = -19
01-04 20:34:43.233 824 11979 E audio_hw_primary: start_input_stream: cannot set hw params: Invalid argument
01-04 20:34:43.236 824 11979 E audio_route: unable to find path 'speaker-dmic-endfire-whatsapp'
01-04 20:34:43.242 961 1026 E SurfaceFlinger: screenshot by : /system/bin/surfaceflinger
01-04 20:34:43.311 824 11979 E audio_route: unable to find path 'speaker-dmic-endfire-whatsapp'
01-04 20:34:43.313 824 11979 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
These messages keep looping while trying to record the message, showing the the code just tries to connect to the mic in the background indefinitely but always fails.
Anyone have any idea what to do here? I've reinstalled Whatsapp already to no avail, rebooting didn't help either.

FireTV 4K and WiFi FDS Channels

Hi Guys, I live in an apartment building and the non-dfs channels are pretty congested. I have been using DFS channels for a long time (64 or 100). Lately, my fireTV4K has started to behave weird. It connects to the wifi, but, after some minutes, it drops the wifi, and crashes. Only way to get it back is pulling power.
From logcat, i can see that it is related to DFS and P2P wifi. I am running the lastest version of ForeOS. I have also tried to root and debloat all amazon apps, but the issue is still happening.
Here is the logcat when it crashes:
Code:
08-24 23:08:48.411 605 658 D AmazonWifiP2pServiceImpl: CREATE_GROUP
08-24 23:08:48.411 605 658 I AmazonWifiP2pServiceImpl: found saved GO, netId=0
08-24 23:08:48.412 605 658 I AmazonWifiP2pServiceImpl: ethernetConnected = false
08-24 23:08:48.412 605 658 I AmazonWifiP2pServiceImpl: Create GO group use the saved p2p property = 5320
08-24 23:08:48.413 878 878 I wpa_supplicant: P2P: The forced channel for GO (5320 MHz) is not supported for P2P uses
08-24 23:08:48.414 605 658 I AmazonWifiP2pServiceImpl: Create GO group use the default chnl =5180
08-24 23:08:48.416 878 878 I wpa_supplicant: P2P: init GO, use existing freq 5500
08-24 23:08:48.416 878 878 E wpa_supplicant: Failed to create interface p2p-p2p0-12: -12 (Out of memory)
08-24 23:08:48.416 878 878 E wpa_supplicant: P2P: Failed to create new group interface: err=1 (Operation not permitted)
08-24 23:08:48.416 878 878 E wpa_supplicant: P2P: Failed to add group interface
08-24 23:08:48.417 605 658 E WifiP2pService: InactiveStateCREATE_GROUP failed
08-24 23:08:48.417 605 658 I WifiP2pService: InactiveState CREATE_GROUP failed cnt=11
08-24 23:08:48.417 605 658 I WifiP2pService: InactiveState Sending DRIVER_HUNG_EVENT to WifiStateMachine
08-24 23:08:48.419 605 660 I WifiStateMachine: WifiMonitor.DRIVER_HUNG_EVENT
08-24 23:08:48.422 605 660 D WifiNative-HAL: stopRssiMonitoring, cmdId 0
08-24 23:08:48.423 605 661 D DhcpClient: doQuit
Anyone has any clue?

OTA Update for Feb security update is failing on OnePlus 8 Pro

It seems like despite restoring the partitions in Magisk uninstall, its detecting some sort of hash mismatch. Anybody else run into this one?
This is what is in logcat:
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553075:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553332:ERROR:delta_performer.cc(551)] Unable to open ECC source partition a
bl on slot A, file /dev/block/bootdevice/by-name/abl_a: Invalid argument (22)
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553404:ERROR:delta_performer.cc(1283)] The hash of the source data on disk
for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or
that the source partition was modified after it was installed, for example, by mounting a filesystem.
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553451:ERROR:delta_performer.cc(1288)] Expected: sha256|hex = C1ED0BAD947
9566E02A8C4F9D2A2ACC149427202832F5A54B71F4ED05687F322
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553495:ERROR:delta_performer.cc(1291)] Calculated: sha256|hex = F30FAC54ED1
A719EDBF2F001BF45A9074A3F0B569B50AEAC7F911B02D04E084C
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553540:ERROR:delta_performer.cc(1302)] Operation source (offset:size) in bl
ocks: 0:528
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553615:ERROR:delta_performer.cc(1623)] source_fd != nullptr failed.
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553676:ERROR:delta_performer.cc(307)] Failed to perform BROTLI_BSDIFF opera
tion 1, which is the operation 1 in partition "abl"
02-27 10:17:25.553 1543 1543 E update_engine: [0227/101725.553727:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitia
lizationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
02-27 10:17:25.556 1543 1543 I update_engine: [0227/101725.556148:INFO:delta_performer.cc(324)] Discarding 1727306 unused downloaded b
ytes
02-27 10:17:25.556 1543 1543 I update_engine: [0227/101725.556239:INFO:libcurl_http_fetcher.cc(548)] Requesting libcurl to terminate t
ransfer.
02-27 10:17:25.556 2549 32032 I chatty : uid=1000(system) com.android.settings expire 2 lines
02-27 10:17:25.559 1543 1543 I update_engine: [0227/101725.559492:INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
02-27 10:17:25.559 1543 1543 I update_engine: [0227/101725.559562:INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 206
02-27 10:17:25.559 1543 1543 I update_engine: [0227/101725.559606:INFO:multi_range_http_fetcher.cc(131)] Terminating.
02-27 10:17:25.620 1543 1543 I update_engine: [0227/101725.620530:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAct
ion with code ErrorCode::kDownloadStateInitializationError
Click to expand...
Click to collapse

Categories

Resources