OTA updates are never found - Google Pixel 3a Questions & Answers

My phone is rooted via Magisk, and bootloader unlocked. For the past year OTA updates have never shown up for me, so I've had to sideload them each time they are released. According to @pbanj's rooting guides (and others I've looked at) I should expect the OTAs to show up even though I'm rooted and my bootloader unlocked. When I first discovered this, I was 4 months behind on security updates, and manually checking for updates continued to say my phone was up to date. I recently upgraded to Android 11, which did actually show up via the system update GUI, so I figured once I updated, the security OTAs would start showing up. Apparently I was wrong as I see that the October update was released, but my phone continues to say it's up to date.
Has anyone else had this issue?

Resolved
I seem to have figured out why this is happening. I used logcat to pull the log while SystemUpdate was checking for updates.
Here is what I found:
10-07 17:27:51.314 18025 1536 I SystemUpdate: [Execution,UpdateEngineDelegate] verifyPayloadMetadata()
10-07 17:27:51.319 1156 1156 I update_engine: [INFO:binder_service_android.cc(179)] Received a request of verifying payload metadata in /data/ota_package/payload_metadata.bin.
10-07 17:27:51.327 1156 1156 I update_engine: [INFOayload_verifier.cc(102)] signature blob size = 267
10-07 17:27:51.332 1156 1156 I update_engine: [INFOayload_verifier.cc(118)] Truncating the signature to its unpadded size: 256.
10-07 17:27:51.334 1156 1156 I update_engine: [INFOayload_verifier.cc(129)] Verified correct signature 1 out of 1 signatures.
10-07 17:27:51.336 1156 1156 I update_engine: [INFOayload_metadata.cc(224)] Metadata hash signature matches value in Omaha response.
10-07 17:27:51.372 1156 1156 I update_engine: [INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot A in /dev/block/bootdevice/by-name/system_a
10-07 17:27:51.374 1156 1156 I update_engine: [INFO:dynamic_partition_control_android.cc(957)] vendor_a is mapped on device mapper: /dev/block/dm-1
10-07 17:27:55.082 1156 1156 I update_engine: [INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot A in /dev/block/bootdevice/by-name/system_a
10-07 17:27:55.084 1156 1156 I update_engine: [INFO:dynamic_partition_control_android.cc(938)] boot_a is not in super partition metadata.
10-07 17:27:55.086 1156 1156 I update_engine: [INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot A in /dev/block/bootdevice/by-name/system_a
10-07 17:27:55.092 1156 1156 E update_engine: [ERROR:delta_performer.cc(1158)] 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.
10-07 17:27:55.094 1156 1156 E update_engine: [ERROR:delta_performer.cc(1163)] Expected: sha256|hex = A9CA8642B1E38A6D8707C31B9C146CB04CFE390A79853CF8AB0FFA9091CDC6CC
10-07 17:27:55.096 1156 1156 E update_engine: [ERROR:delta_performer.cc(1166)] Calculated: sha256|hex = 5BE55D2089653B1A9A244BDDF60582ACAFC0444B7F62A8546E0D030337C00331
10-07 17:27:55.097 1156 1156 E update_engine: [ERROR:delta_performer.cc(1177)] Operation source (offset:size) in blocks: 0:1,8172:1
10-07 17:27:55.117 18025 1536 E SystemUpdate: [Execution,PreDownloadValidateAction] UpdateEngine.verifyPayloadMetadata() failed.
10-07 17:27:55.686 18025 1536 E SystemUpdate: [Execution,PreDownloadValidateAction] Failed to download.
10-07 17:27:55.686 18025 1536 E SystemUpdate: awhr: Unexpected status code: 403.
10-07 17:27:55.686 18025 1536 E SystemUpdate: at awhv.run[email protected]@20.36.15 (150400-333172415):7)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at qzo.b[email protected]@20.36.15 (150400-333172415):12)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at qzo.run[email protected]@20.36.15 (150400-333172415):7)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at rfo.run[email protected]@20.36.15 (150400-333172415):0)
10-07 17:27:55.686 18025 1536 E SystemUpdate: at java.lang.Thread.run(Thread.java:923)
10-07 17:27:55.686 18025 1536 E SystemUpdate: [Execution,PreDownloadValidateAction] Failed to validate package, with resolution=REJECT.
So it looks like it was seeing a difference in the expected boot image hash vs my magisk patched boot image. I used magisk to restore images and re-ran the SystemUpdate. At that point it indicated that there was an OTA to install. I thought in the past it would at least indicate that there was an OTA to download, at which point I could go through the magisk restore images process. Oh well.
TL;DR: I needed to restore the boot image in magisk prior to checking for updates in order for the OTA to show up.

Interesting. I just received the OTA for Oct---first one I've received since January (sometimes I don't wait, but other times I've gone into mid-month before dealing with updates). I'm always running magisk patched. I wonder if a specific kernel build has that effect. I will try this method next month.

How do you patch the boot image after OTA on device since "Install to inactive slot" is now gone?

koichirose said:
How do you patch the boot image after OTA on device since "Install to inactive slot" is now gone?
Click to expand...
Click to collapse
I ended up just booting with the stock boot.img (losing root), then patching the boot.img from the October full image and flashing via fastboot. There may be an easier method though.

Related

Help with CM13 boot loop - logcat included

Hi,
my oneplus one with CM13 (14_06 build) is stuck in a bootloop and I don't know how to solve.
Here's what I have tried to do:
Wipe cache
Flash a previous build
Delete the last apps I have installed via adb (pm uninstall APPNAME)
The last thing I have done before rebooting is installing the GMSCore from MicroG project (Yes, I don't have gapps).
http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
Then I have successfully removed the gsmcore via adb but the bootloop continued.
The phone reboots when "Prearing contacts storage" appears....
Here's my logcat (*:E)
Code:
06-14 14:46:46.384 3660 3660 E Minikin : addFont failed to create font /system/fonts/DroidSansFallback.ttf
06-14 14:46:46.384 3660 3660 E Minikin : addFont failed to create font /system/fonts/MTLmr3m.ttf
06-14 14:46:48.623 3654 3654 E installd: eof
06-14 14:46:48.623 3654 3654 E installd: failed to read size
06-14 14:46:49.304 4935 4935 E QCOM PowerHAL: Unable to open prefetcher: dlopen failed: library "libqti-iop-client.so" not found
06-14 14:46:49.304 4935 4935 E QCOM PowerHAL: Failed to get prefetcher handle.
06-14 14:46:49.305 4935 4935 E QCOM PowerHAL: Invalid hint ID.
06-14 14:46:49.894 4935 4935 E art : DexFile_getDexOptNeeded file '/system/framework/org.apache.http.legacy.jar' does not exist
06-14 14:46:51.356 3653 3653 E msm8974_platform: hw_util_open Opening device /dev/snd/hwC0D1000
06-14 14:46:51.356 3653 3653 E msm8974_platform: hw_util_open success
06-14 14:46:51.356 3653 3653 E msm8974_platform: send_codec_cal cal sent for anc_cal
06-14 14:46:51.356 3653 3653 E ACDB-LOADER: ACDB -> send_codec_cal
06-14 14:46:51.356 3653 3653 E msm8974_platform: send_codec_cal cal sent for mad_cal
06-14 14:46:51.357 3653 3653 E msm8974_platform: send_codec_cal cal sent for mbhc_cal
06-14 14:46:51.358 3653 3653 E audio_hw_primary: Amplifier initialization failed
06-14 14:46:51.358 3653 3653 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
06-14 14:46:51.358 3653 3653 E ACDB-LOADER: Error: ACDB AFE returned = -19
06-14 14:46:51.377 3653 3653 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
06-14 14:46:51.377 3653 3653 E ACDB-LOADER: Error: ACDB AFE returned = -19
06-14 14:46:51.386 3653 3653 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
06-14 14:46:51.397 3653 3653 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
06-14 14:46:51.430 3653 3653 E MonoPipe: Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
06-14 14:46:51.435 3653 5160 E AudioFlinger: no wake lock to update!
06-14 14:46:51.437 3653 5161 E AudioFlinger: no wake lock to update!
06-14 14:46:51.443 3653 5163 E AudioFlinger: no wake lock to update!
06-14 14:46:51.455 3653 3653 E SoundTriggerHwService: couldn't load sound trigger module sound_trigger.primary (No such file or directory)
06-14 14:46:51.460 3653 3653 E RadioService: couldn't load radio module radio.primary (No such file or directory)
06-14 14:46:52.409 3649 3649 E Netd : netlink response contains error (File exists)
06-14 14:46:52.409 3649 3649 E Netd : Can't add IPv4 default route to dummy0: File exists
06-14 14:46:53.221 3657 5266 E QC-QMI : qmi_client [3657] 16: failed to locate client data
06-14 14:46:53.222 3656 3656 E QC-QMI : qmuxd: RX on fd=27 returned error=0 errno[11:Try again]
06-14 14:46:53.222 3656 3656 E QC-QMI : QMUX qmux_client_id=16 not found in qmux client list, unable to remove
06-14 14:46:53.228 3657 5272 E QC-QMI : qmi_client [3657] 17: failed to locate client data
06-14 14:46:53.229 3656 3656 E QC-QMI : qmuxd: RX on fd=27 returned error=0 errno[11:Try again]
06-14 14:46:53.229 3656 3656 E QC-QMI : QMUX qmux_client_id=17 not found in qmux client list, unable to remove
06-14 14:46:53.328 3656 3718 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:53.562 3656 3729 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:53.848 3656 3735 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:54.073 3656 3745 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:54.252 3656 3749 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:54.538 3656 3756 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:54.800 3656 3760 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:46:55.083 3656 3776 E QC-QMI : qmi_ctl_handle_set_data_format_rsp, skipping unknown type = 18
06-14 14:47:22.040 4935 4935 E PackageManager: updateAllSharedLibrariesLPw failed: Package com.android.dialer requires unavailable shared library com.qualcomm.qti.smartsearch; failing!
06-14 14:47:22.042 3654 3654 E installd: invalid apk path '/system/framework/org.cyanogenmod.platform-res.apk' (bad prefix)
06-14 14:47:22.225 4935 5987 E qti_sensors_hal: SensorsContext: Hal opened lib /system/lib/hw/sensors.oem.so failed!
06-14 14:47:22.268 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.268 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.268 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.269 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle is -1 or error is true or mSensors[handle] is NULL!
06-14 14:47:22.269 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.269 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.269 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.269 4935 5990 E qti_sensors_hal: processSingleSensorInfoResp: either handle_wakeup is -1 or error is true or mSensors[handle_wakeup] is NULL!
06-14 14:47:22.269 4935 5987 E qti_sensors_hal: OEMAddSensors : The OEM_module is NULL!
06-14 14:47:22.350 4935 4935 E ConsumerIrService: Can't open consumer IR HW Module, error: -2
06-14 14:47:22.504 4935 6037 E EventHub: could not get driver version for /dev/input/mice, Not a typewriter
06-14 14:47:22.550 4935 6037 E filemap : mmap(0,4096) failed: No such device

[APP] [NO-ROOT] themeDIY for Samsung Galaxy S8/S7/S6/J/C ✺ 6.x/7.x

Original Thread
https://forum.xda-developers.com/android/apps-games/app-themediy-samsung-galaxy-s8-s7-s6-j-t3685010
Idk if im right here. but someone told me i should post my problem here. I have a ported S8 Nougat Samsung Music on Android 6.0.1 Marshmallow an i get an fatal error which makes the app crash after few minutes of using:
Code:
10-07 01:23:10.812 449 449 F DEBUG : pid: 4054, tid: 4383, name: RenderThread >>> com.sec.android.app.music:service <<<
10-07 01:23:12.972 923 2455 I ActivityManager: Process com.sec.android.app.music:service (pid 4054)(adj 1) has died(153,322)
10-07 01:23:12.972 923 2455 W ActivityManager: Scheduling restart of crashed service com.sec.android.app.music/com.samsung.android.app.music.service.PlayerService2 in 1000ms
10-07 01:23:13.172 426 426 I SurfaceFlinger: id=261 createSurf (13x13),1 flag=4, Application Error: com.sec.android.app.music
10-07 01:23:13.832 426 1473 I SurfaceFlinger: id=189 Removed com.sec.android.app.music/com.samsung.android.app.music.common.activity.PlayerActivity (6/10)
10-07 01:23:13.842 426 445 I SurfaceFlinger: id=189 Removed com.sec.android.app.music/com.samsung.android.app.music.common.activity.PlayerActivity (-2/10)
10-07 01:23:14.812 426 2050 I SurfaceFlinger: id=261 Removed Application Error: com.sec.android.app.music (8/9)
10-07 01:23:14.812 426 448 I SurfaceFlinger: id=261 Removed Application Error: com.sec.android.app.music (-2/9)
---- 07.10.2017 01:23:32 ----
Can anyone tell me how to understand a log to solve the problem? bc i understand nothing..
thx
Looks like some system files were deleted. Did you remove anything or was it given to you like that.

Android 7.1.2 no video image only sound

I have a nokia 5, after the upgrade of android version to 7.1.2 some apps stops to show video image , I just can hear the sound.
I found this on logcat
Code:
10-31 13:35:58.874 513 513 E SurfaceFlinger: CaptureScreen: layer name = pt.nowo.nowotv/androme.be.nebula.ui.boot.SplashScreen
10-31 13:35:58.913 2840 2840 E PBSessionCacheImpl: sessionId[12491961548232875] not persisted.
10-31 13:36:01.791 1506 1883 E WifiHAL : Received fatal event, sending alert
10-31 13:36:01.792 1506 1837 E WifiHAL : wifi_get_ring_data: Error -22 happened.
10-31 13:36:01.793 1506 1837 E WifiHAL : wifi_get_ring_data: Error -22 happened.
10-31 13:36:01.793 1506 1837 E WifiHAL : wifi_get_ring_data: Error -22 happened.
10-31 13:36:01.794 1506 1837 E WifiHAL : wifi_get_ring_data: Error -22 happened.
10-31 13:36:01.794 1506 1837 E WifiHAL : wifi_get_ring_data: Error -22 happened.
10-31 13:36:09.324 703 941 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware/widevine.mdt errno = 2
10-31 13:36:09.324 703 941 E QSEECOMAPI: Error::Loading image failed with ret = -1
10-31 13:36:09.356 703 941 E DrmWidevineDash: sion_buffer g_wv_fhandle->ion_sbuffer 0x0xe8579000
10-31 13:36:09.366 564 566 E rpmb_emmc: ----------------------------rpmb_emmc_read-----------------------------
10-31 13:36:09.372 564 572 E QC-time-services: Receive Passed == base = 13, unit = 1, operation = 2, result = 0
10-31 13:36:09.372 686 734 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
10-31 13:36:09.373 686 734 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
10-31 13:36:09.400 703 703 E DrmWidevineDash: tz api security patch level = 0
10-31 13:36:09.782 702 702 E : Service not available yet
10-31 13:36:09.797 431 2516 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 13:36:09.952 702 943 E OMX-VDEC-1080P: Extension: OMX.google.android.index.storeANWBufferInMetadata not implemented
10-31 13:36:09.959 702 943 E OMX-VDEC-1080P: Extension: OMX.google.android.index.storeANWBufferInMetadata not implemented
10-31 13:36:09.959 702 943 E OMX-VDEC-1080P: Extension: OMX.google.android.index.configureVideoTunnelMode not implemented
10-31 13:36:09.959 702 943 E OMX-VDEC-1080P: Extension: OMX.google.android.index.useAndroidNativeBuffer is supported
10-31 13:36:09.963 702 943 E OMX-VDEC-1080P: Does not handle dataspace request
10-31 13:36:09.963 702 943 E OMXNodeInstance: getConfig(2be0037:qcom.decoder.avc.secure, ??(0x7f000062)) ERROR: UnsupportedSetting(0x80001019)
10-31 13:36:10.396 702 702 E OMX-VDEC-1080P: Does not handle dataspace request
10-31 13:36:10.396 702 702 E OMXNodeInstance: getConfig(2be0037:qcom.decoder.avc.secure, ??(0x7f000062)) ERROR: UnsupportedSetting(0x80001019)
10-31 13:36:10.494 702 2051 E OMX-VDEC-1080P: Does not handle dataspace request
10-31 13:36:10.494 702 2051 E OMXNodeInstance: getConfig(2be0037:qcom.decoder.avc.secure, ??(0x7f000062)) ERROR: UnsupportedSetting(0x80001019)
10-31 13:36:10.634 697 7482 E msm8916_platform: platform_check_backends_match: Invalid snd_device2 =
10-31 13:36:10.651 697 7482 E audio_hw_dolby: audio_extn_dolby_ds2_set_endpoint: Dolby set endpint :0x2
10-31 13:36:13.647 513 513 E SurfaceFlinger: CaptureScreen: layer name = pt.nowo.nowotv/androme.be.nebula.ui.MainActivity
Also, on this android version I need to turn on/off the mobile data manually every time that I send / receive a MMS, is there any way to turn on mobile data automatically any time that I send / receive a MMS like other Android versions do?
Any one can help me to understand the issue and hopefully help me to fix it. Best regards
Even I face the same issue on android 7.1.2 but on a custom rom by Mokee, it happened when I entered wrong WiFi password for a certain network and the phone switched off itself and just vibrated for 4-5 seconds...

Need to remove unknown MDM agent from LG Aristo Tmobile Version bug report included

Hello,
I have an issue with my personal phone, the Tmobile LG Aristo, being enrolled and supervised by an unknown MDM management agent (I don't know which one or who put it there). I will post the instances in the bugreport that show up when I search for "MDM" below and please let me know if there's more information I can provide. Here are some questions and observations:
Wiping the phone doesn't fix the problem and there's nothing stated anywhere that the phone is being managed so no obvious certificate to delete nor an app.
Also, do the trust certificates have anything to do with this and if I disabled the correct one(s) it would then remove the software?
I know Apple has Apple Configurator to do enroll/unenroll management software from iOS devices. Does Android have a tool like Apple Configurator that I need to use?
Thanks very much and I know very little about this problem so sorry if I left out anything important.
Places in the bug report where "MDM" shows up:
u:r:system_server:s0 system 1683 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMUIApplicat
u:r:system_server:s0 system 1768 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMPostRunnab
u:r:system_server:s0 system 1769 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMDevicePoli
u:r:system_server:s0 system 1770 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMDevicePoli
u:r:system_server:s0 system 1772 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMExternalMe
u:r:system_server:s0 system 1774 1349 1365492 114324 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMPermission
u:r:system_server:s0 system 3277 1349 1365492 114332 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMUIApplicat
u:rlatform_app:s0 u0_a91 2220 1842 1327444 95752 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMUILockScre
u:rlatform_app:s0 u0_a91 2745 1842 1327444 95752 20 0 0 0 fg SyS_epoll_ 00000000 S LGMDMUIApplicat
1683 LGMDMUIApplicat SyS_epoll_wait
1768 LGMDMPostRunnab SyS_epoll_wait
1769 LGMDMDevicePoli SyS_epoll_wait
1770 LGMDMDevicePoli SyS_epoll_wait
1772 LGMDMExternalMe SyS_epoll_wait
1774 LGMDMPermission SyS_epoll_wait
3277 LGMDMUIApplicat SyS_epoll_wait
2220 LGMDMUILockScre SyS_epoll_wait
2745 LGMDMUIApplicat SyS_epoll_wait
11-26 21:45:32.925 1349 1349 W PackageManager: Unknown permission com.sec.enterprise.knox.MDM_CONTENT_PROVIDER in package com.android.chrome
11-26 21:45:34.785 1349 1695 W PackageManager: Unknown permission com.sec.enterprise.knox.MDM_CONTENT_PROVIDER in package com.android.chrome
11-26 21:45:35.148 1349 1349 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.mdm.controller.LGMDMVpnController.bindLGVpnService:486 com.lge.mdm.controller.LGMDMVpnController.isAuthentecVpn:463 com.lge.mdm.controller.LGMDMVpnController.<init>:68 com.lge.mdm.controller.LGMDMVpnController.getInstance:77
11-26 21:45:35.148 1349 1349 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.mdm.controller.LGMDMVpnController.bindLGVpnService:486 com.lge.mdm.controller.LGMDMVpnController.isAuthentecVpn:463 com.lge.mdm.controller.LGMDMVpnController.<init>:68 com.lge.mdm.controller.LGMDMVpnController.getInstance:77
11-26 21:45:35.148 1349 1349 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.mdm.controller.LGMDMVpnController.bindLGVpnService:486 com.lge.mdm.controller.LGMDMVpnController.isAuthentecVpn:463 com.lge.mdm.controller.LGMDMVpnController.<init>:68 com.lge.mdm.controller.LGMDMVpnController.getInstance:77
11-26 21:45:35.148 1349 1349 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.mdm.controller.LGMDMVpnController.bindLGVpnService:486 com.lge.mdm.controller.LGMDMVpnController.isAuthentecVpn:463 com.lge.mdm.controller.LGMDMVpnController.<init>:68 com.lge.mdm.controller.LGMDMVpnController.getInstance:77
11-26 21:45:36.061 1349 1349 D AudioSystem: muteMicrophone [MDM policy:false], [state:false]
11-26 21:45:37.518 1349 1695 I MountService: MDM Ignoring mount emulated due to policy
11-26 21:45:37.572 1349 1695 I MountService: MDM Ignoring mount public:179,65 due to policy
11-26 21:45:39.408 1842 2179 V LGMDMManager: Create singleton instance
11-26 21:45:39.442 1842 2179 V LGMDMManagerInternal: Create singleton instance
11-26 21:45:39.563 1349 1404 W PackageManager: Unknown permission com.sec.enterprise.knox.MDM_CONTENT_PROVIDER in package com.android.chrome
11-26 21:45:40.460 2198 2210 V LGMDMManager: Create singleton instance
11-26 21:45:42.568 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:42.575 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:42.627 1904 1904 D wpa_supplicant: wlan0: [MDM] get_mdm_autoconn_policy : 0
11-26 21:45:42.627 1904 1904 D wpa_supplicant: wlan0: [MDM] reassociate : 1
11-26 21:45:42.627 1904 1904 D wpa_supplicant: wlan0: [MDM] lg mdm allow/disallow auto connect is not set!
11-26 21:45:42.629 1904 1904 D wpa_supplicant: wlan0: [MDM] get_mdm_autoconn_policy : 0
11-26 21:45:42.629 1904 1904 D wpa_supplicant: wlan0: [MDM] reassociate : 1
11-26 21:45:42.629 1904 1904 D wpa_supplicant: wlan0: [MDM] lg mdm allow/disallow auto connect is not set!
11-26 21:45:43.342 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDeviceWipeController.connectATService:36 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:231
11-26 21:45:43.342 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDeviceWipeController.connectATService:36 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:231
11-26 21:45:43.342 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDeviceWipeController.connectATService:36 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:231
11-26 21:45:43.379 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDownloadModeController.connectATService:35 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:232
11-26 21:45:43.379 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDownloadModeController.connectATService:35 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:232
11-26 21:45:43.379 1349 1769 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1426 com.lge.android.atservice.client.LGATCMDClient.bindService:105 com.lge.mdm.controller.LGMDMATClientConnector.connectATService:42 com.lge.mdm.controller.LGMDMDownloadModeController.connectATService:35 com.lge.mdm.controller.LGMDMDevicePolicyManagerService$1.onReceive:232
11-26 21:45:43.688 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:43.698 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.430 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.432 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.432 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.439 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.440 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.455 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.455 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:44.493 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:46.025 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:46.100 1842 1842 D EmergencyButton: MDM updateEmergencyCallButton() - isLockoutMode: false
11-26 21:45:47.030 2836 2836 I MDM__DMClient: Process started
11-26 21:45:47.394 1904 1904 D wpa_supplicant: wlan0: [MDM] get_mdm_autoconn_policy : 0
11-26 21:45:47.394 1904 1904 D wpa_supplicant: wlan0: [MDM] reassociate : 1
11-26 21:45:47.394 1904 1904 D wpa_supplicant: wlan0: [MDM] lg mdm allow/disallow auto connect is not set!
11-26 21:45:47.395 1904 1904 D wpa_supplicant: wlan0: [MDM] get_mdm_autoconn_policy : 0
11-26 21:45:47.395 1904 1904 D wpa_supplicant: wlan0: [MDM] reassociate : 1
11-26 21:45:47.395 1904 1904 D wpa_supplicant: wlan0: [MDM] lg mdm allow/disallow auto connect is not set!
11-26 21:45:55.577 2766 2766 V LGMDMManagerInternal: Create singleton instance
11-26 21:45:57.338 1904 1904 D wpa_supplicant: wlan0: [MDM] get_mdm_autoconn_policy : 0
11-26 21:45:57.338 1904 1904 D wpa_supplicant: wlan0: [MDM] reassociate : 1
11-26 21:45:57.338 1904 1904 D wpa_supplicant: wlan0: [MDM] lg mdm allow/disallow auto connect is not set!
11-26 21:46:00.545 3373 3373 V LGMDMManager: Create singleton instance
11-26 21:46:11.163 3373 3373 V LGMDMManagerInternal: Create singleton instance
11-26 21:46:22.862 3373 3373 I LGMDMSettings: UserHandle is : 0
11-26 21:46:22.866 3373 3373 I LGMDMSettings: isDpmMaximunTimeToLock`s value is : 0
11-26 21:46:45.966 2899 5207 E MDM : [329] xet.run: Couldn't connect to Google API client: krr{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-26 21:46:55.238 5429 5441 V LGMDMManagerInternal: Create singleton instance
11-26 21:47:00.282 6023 6023 V LGMDMManager: Create singleton instance
11-26 21:47:09.268 6455 6455 I MDM__DMClient: Process started
11-26 21:47:09.998 6472 6472 I MDM__DMClient: Process started
"LGMDMUIApplicationAdapter" prio=5 tid=35 Native
"LGMDMPostRunnable" prio=5 tid=32 Native
"LGMDMDevicePolicyManagerServiceReceiver" prio=5 tid=40 Native
"LGMDMDevicePolicyManagerService" prio=5 tid=41 Native
"LGMDMExternalMemorySlotContoller" prio=5 tid=43 Native
"LGMDMPermissionController" prio=5 tid=45 Native
"LGMDMUIApplicationAdapter" prio=5 tid=113 Native
"LGMDMUILockScreenAdapter" prio=5 tid=44 Native
"LGMDMUIApplicationAdapter" prio=5 tid=60 Native
Action: "com.lge.mdm.intent.action.LGMDM_LOCK_OUT"
com.lge.mdm.intent.action.LGMDM_LOCK_OUT:
Current LGMDM Device Policy Manager state:
com.google.android.gms.mdm.MDM_SETTINGS_ACTIVITY:
com.google.android.gms.mdm.MDM_LOCKSCREEN_ACTIVITY:
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
5d7199e com.android.settings/.lgmdm.LGMDMBroadcastReceiver
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
3LM_MDM_ACTIVATED:
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
3LM_MDM_DEACTIVATED:
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
8332180 com.lge.email/.policy.mdm.MDMConfigReceiver
Permission [com.lge.email.permission.MDM_EMAIL_ACCOUNT] (133a7a9):
perm=Permission{5ca112e com.lge.email.permission.MDM_EMAIL_ACCOUNT}
com.lge.email.permission.MDM_EMAIL_ACCOUNT: prot=signature|privileged, INSTALLED
com.lge.email.permission.MDM_EMAIL_ACCOUNT: granted=true

Android 6's "Optimizing app 1 of 1" bug is ruining my life

So I have an LG K8 (2017) with this apparently well documented issue in Marshmallow where Android keeps trying to optimize one or more apps at boot, and takes forever to do so, often rebooting and then trying again, sometimes for hours on end. I'm not a firstworlder who can just get a new phone and be done with it, so I'd genuinely appreciate any guidance on how to fix this.
I enabled USB debugging and logged the phone while it boots, and the affected package seems to be 'googlequicksearchbox'. I'm not sure what this is, but it sounds like a part of Android, not something I can uninstall easily. Here are the relevant logs:
Code:
06-26 16:46:06.546 1840 1840 E installd: DexInv: --- END '/data/app/com.google.android.googlequicksearchbox-2/base.apk' --- status=0x000b, process failed
06-26 16:46:06.547 2443 2443 D PackageManager.DexOptimizer: dexopt package: /data/app/com.google.android.googlequicksearchbox-2/base.apk pkg=com.google.android.googlequicksearchbox - cost time = 273851 ms.
06-26 16:46:06.594 2443 2443 I PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/com.google.android.googlequicksearchbox-2/base.apk pkg=com.google.android.googlequicksearchbox isa=arm64 vmSafeMode=false debuggable=false oatDir = /data/app/com.google.android.googlequicksearchbox-2/oat
06-26 16:46:06.590 2587 2587 W dex2oat : type=1400 audit(0.0:89): avc: denied { module_request } for kmod="personality-8" scontext=u:r:dex2oat:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
06-26 16:46:06.666 2587 2587 I dex2oat : Starting dex2oat.
06-26 16:46:06.765 288 1797 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.12 dur=1014.48 max=19.62 min=13.25
06-26 16:46:07.083 288 288 I SurfaceFlinger: [Built-in Screen (type:0)] fps:61.139503,dur:1014.07,max:18.02,min:14.76
06-26 16:46:07.285 1651 1662 I PerfService: PerfServiceNative_getPackName
06-26 16:46:07.780 288 1089 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.10 dur=1014.78 max=17.28 min=15.82
06-26 16:46:08.097 288 288 I SurfaceFlinger: [Built-in Screen (type:0)] fps:61.121483,dur:1014.37,max:16.57,min:16.12
06-26 16:46:08.286 1651 1662 I PerfService: PerfServiceNative_getPackName
06-26 16:46:08.794 288 396 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.11 dur=1014.63 max=16.87 min=15.91
06-26 16:46:09.112 288 288 I SurfaceFlinger: [Built-in Screen (type:0)] fps:61.114136,dur:1014.50,max:16.53,min:16.20
06-26 16:46:09.286 1651 1662 I PerfService: PerfServiceNative_getPackName
06-26 16:46:09.808 288 1089 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.14 dur=1014.02 max=16.75 min=15.89
06-26 16:46:10.126 288 288 I SurfaceFlinger: [Built-in Screen (type:0)] fps:61.119678,dur:1014.40,max:16.93,min:15.81
06-26 16:46:10.287 1651 1662 I PerfService: PerfServiceNative_getPackName
06-26 16:46:10.421 1867 1867 I sn : Retry 32
06-26 16:46:10.422 1867 1867 I sn : Fail to access err=2
06-26 16:46:10.422 1867 1867 I sn : Fail to access err=2
06-26 16:46:10.422 1867 1867 I sn : Fail to access err=2
06-26 16:46:10.422 1867 1867 I sn : Check all possible paths
06-26 16:46:10.553 1854 1854 I thermal_repeater: oh, queryMdThermalInfo (0)No such file or directory
06-26 16:46:10.558 1854 1854 I thermal_repeater: [recvMdThermalInfo] ret=5, strLen=127, ERROR
06-26 16:46:10.823 288 1089 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.08 dur=1014.99 max=17.03 min=16.01
06-26 16:46:11.141 288 288 I SurfaceFlinger: [Built-in Screen (type:0)] fps:61.103127,dur:1014.68,max:16.61,min:16.21
06-26 16:46:11.287 1651 1662 I PerfService: PerfServiceNative_getPackName
06-26 16:46:11.838 288 1797 I BufferQueueProducer: [Android se está iniciando...](this:0x7fa1dd2780,id:14,api:1,p:2443,c:288) queueBuffer: fps=61.13 dur=1014.28 max=16.99 min=15.90
06-26 16:46:11.911 288 524 W hwcomposer: [JOB] (0) Timed out waiting for vsync...
At this point hwcomposer begins to repeat this error message until the phone eventually reboots:
Code:
06-26 16:46:35.821 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1483/val=1)
06-26 16:46:35.853 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1485/val=1)
06-26 16:46:35.886 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1487/val=1)
06-26 16:46:35.918 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1489/val=1)
06-26 16:46:35.950 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1491/val=1)
06-26 16:46:35.982 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1493/val=1)
06-26 16:46:36.014 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1495/val=1)
06-26 16:46:36.047 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1497/val=1)
06-26 16:46:36.079 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1499/val=1)
06-26 16:46:36.111 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1501/val=1)
06-26 16:46:36.143 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1503/val=1)
06-26 16:46:36.176 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1505/val=1)
06-26 16:46:36.208 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1507/val=1)
06-26 16:46:36.240 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1509/val=1)
06-26 16:46:36.272 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1511/val=1)
06-26 16:46:36.304 288 524 W hwcomposer: [WKR] Timed out waiting for UICompThread_0 (cnt=1513/val=1)
After it tries again it may either boot successfully or fail again with the same error messages. Any ideas?
Enviado desde mi LG-X240 mediante Tapatalk
Same error here...
If you look at
play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
you will see it's a part of "Google" application.
Just uninstall upgrades of "Google" and you're done !

Categories

Resources