Hi
I am using Lineageos 15.1 on my good old nexus 6. Working well but Titanium Backup is crashing on start .... I tried uninstall, then reinstall but nothing.
I tried one
Code:
adb logcat
in order to get some clue , here is one extract of the file :
08-04 18:38:37.718 2562 2574 I ActivityManager: Start proc 6602:com.keramidas.TitaniumBackup/u0a233 for activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:37.802 14937 5573 I DeviceStateChecker: DeviceStateChecker cancelled
08-04 18:38:37.802 14937 14937 I MicroDetector: Keeping mic open: false
08-04 18:38:37.811 14937 5898 I AudioController: internalShutdown
08-04 18:38:37.813 14937 6308 I MicroRecognitionRunner: Stopping hotword detection.
08-04 18:38:37.818 6602 6602 I o.კ : onCreate()
08-04 18:38:37.842 6602 6602 I o.კ : Detected CPU architecture: ARM
08-04 18:38:37.845 6602 6602 W Settings: Setting android_id has moved from android.provider.Settings.System to android.provider.Settings.Secure, returning read-only value.
08-04 18:38:37.851 6602 6602 D o.dJ : Debug features are disabled.
08-04 18:38:37.855 6602 6602 I o.dx : restoreMySettings_ifNeeded()
08-04 18:38:37.863 6602 6602 I o.dx : Internal settings found => No need to restore.
08-04 18:38:37.865 2235 6523 D audio_hw_primary: disable_audio_route: usecase(9) reset and update mixer path: audio-record
08-04 18:38:37.866 2235 6523 D audio_hw_primary: disable_snd_device: snd_device(75: voice-rec-mic)
08-04 18:38:37.879 14937 5898 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
08-04 18:38:37.879 14937 5417 I MicroRecognitionRunner: Detection finished
08-04 18:38:37.949 6602 6602 I com.keramidas.TitaniumBackup.MainActivity: Main Activity is being created for the first time => scheduling next wake-up ...
08-04 18:38:37.950 6602 6602 I o.dg : scheduleNextWakeup(): Invoked with idToExcludeForToday=null
08-04 18:38:37.974 6602 6602 I o.dg : scheduleNextWakeup(): No next wakeup scheduled.
08-04 18:38:37.975 6602 6621 I o.ỵ : Thread started.
08-04 18:38:37.989 6602 6602 I ToolbarWidgetWrapper: Progress display unsupported
08-04 18:38:38.024 6602 6623 D OpenGLRenderer: HWUI GL Pipeline
08-04 18:38:38.031 6602 6622 I o.ep : Detected 0 mount point(s) in addition to Android "external" storage.
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] No cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Cache valid? = false
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Deleting non-valid cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.035 6602 6622 I o.cj : [Licensing] Performing query: attempt 1/4
08-04 18:38:38.040 11256 11256 I com.keramidas.TitaniumBackupPro.LicenseQueryService: onCreate()
08-04 18:38:38.078 6602 6623 I Adreno : QUALCOMM build : a5b4970, If5818605d9
08-04 18:38:38.078 6602 6623 I Adreno : Build Date : 10/12/16
08-04 18:38:38.078 6602 6623 I Adreno : OpenGL ES Shader Compiler Version: XE031.09.00.04
08-04 18:38:38.078 6602 6623 I Adreno : Local Branch : N24D
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Reconstruct Branch :
08-04 18:38:38.087 6602 6623 I zygote : android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
08-04 18:38:38.106 6602 6623 I OpenGLRenderer: Initialized EGL, version 1.4
08-04 18:38:38.106 6602 6623 D OpenGLRenderer: Swap behavior 1
08-04 18:38:38.138 2562 3863 W ActivityManager: Permission Denial: Accessing service ComponentInfo{com.android.vending/com.google.android.finsky.services.LicensingService} from pid=11256, uid=10143 requires com.android.vending.CHECK_LICENSE
08-04 18:38:38.140 6602 6624 E AndroidRuntime: FATAL EXCEPTION: Thread-4
08-04 18:38:38.140 6602 6624 E AndroidRuntime: Process: com.keramidas.TitaniumBackup, PID: 6602
08-04 18:38:38.140 6602 6624 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.vending.licensing.ILicensingService pkg=com.android.vending }
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2005)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1951)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at com.keramidas.TitaniumBackupPro.LicenseQueryServiceRemoteInterface$if$if.ˊ(Source:133)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at o.cl.run(Source:75)
08-04 18:38:38.148 2562 3275 W ActivityManager: Force finishing activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:38.165 6602 6624 I Process : Sending signal. PID: 6602 SIG: 9
08-04 18:38:38.201 2562 3290 I ActivityManager: Process com.keramidas.TitaniumBackup (pid 6602) has died: vis +99TOP
Click to expand...
Click to collapse
It seems to be a permission issue but any help will be welcome ... How to solve ?
Thanks
mahashakti89
I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
Yes, I already tried clearing cache, uninstall, reinstall but it won't work.
Thanks
I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
I did a clean install this morning. Wiped system , cache, dalvik but I did'nt format data. I used TWRP. How do you format data and NOT user data ?
What do you mean by clearing play store app's data and cache ?
Thanks
No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
If your problem with TiBu began as part of a clean install, it may be due to a bad flash, wrong gapps, bad download (always use checksums like MD5) or a hiccup during setup.
In this case then, I would remove TiBu, clear the play store data and cache then reinstall TiBu if it doesn't improve, them double check the quality of the downloaded files you installed, make site you've got the correct gapps and wipe, then flash again.
Sent from my Nexus 6 using XDA-Developers Legacy app
ktmom said:
No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
That's exactly what I did. Formatted all partitions except /data and Internal storage.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
Already done. I asked because I was not sure if I mean the same as you mean
I will perhaps a full wipe tomorrow or wit till a new version of LineageOS.
Regards
Click to expand...
Click to collapse
I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app
ktmom said:
I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks
mahashakti89 said:
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks
Click to expand...
Click to collapse
I did'nt wait .... Wiped data. It works now ....
Thanks for helping
Hitting the "thanks" button on posts is always appreciated.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Related
Hi, here's the AOSP Marshmallow ROM that I would like to share with the community.
https://androidfilehost.com/?w=files&flid=57323
Thanks for the ground work they had laid out for P880 and Nexus 7 (2012).
@dmitrygr
@alfsamsung
@streambinder
@Demetris
...and...
XDA developers community
Changelog
20170307
- Android-6.0.1_r79 (MOB31T)
Complete changelog
https://androidfilehost.com/?w=files&flid=57323
Issue
- MHL/HDMI does not work (by @juantech)
Repo patches made available in 2nd POST for
- lge-kernel-p880 from CyanogenMod
- platform_device_lge_p880 from MoltenMotherBoard
SELinux for Marshmallow
Release 20160626 is SELinux clean. Google Marshmallow android_external_sepolicy and android_external_selinux source git repo remain pristine without downgrading the rules and policies to Lollipop/Kitkat level. Only the sepolicies of device tree are updated.
To enable SELinux Enforcing, do this from recovery
Code:
$ adb shell mount /data
$ adb shell touch /data/.selinux
$ adb shell umount /data
Recommened GApps is modular GApps from @Deltadroid, or OpenGapps stock. google-webview is a *REQUIRED* component. The minimum required GApps to be installed (which is how I test my setup)
- gapps-base
- gapps-exchange
- gapps-chrome
- gapps-gmail
- gapps-maps
- gapps-search
- gapps-tts
- gapps-webview
- gapps-youtube
This is based on Grouper blobs, so as usual barcode/QR scanning will not work and will not consider this as bug. However, Grouper blobs works with Screen Cast, which for me, is more useful than barcode/QR code scanning.
Let the testing begin!!!:fingers-crossed::fingers-crossed::fingers-crossed:
Kernel source
https://github.com/CyanogenMod/lge-kernel-p880/tree/cm-12.1
Code:
commit 413b3fc527c086450f28acbe92893c71e73ad5b6
Author: demetris <[email protected]>
Date: Wed Nov 4 00:39:13 2015 +0200
Check AOSP Nougat 7.0 thread for updated unified kernel
http://forum.xda-developers.com/showpost.php?p=68614155&postcount=2
Device Tree
https://github.com/MoltenMotherBoard/platform_device_lge_p880/tree/aosp-lp
Complete device tree is attached - device_lge_p880-mm-20160602.tar.gz
Misc. framework patch
Code:
[frameworks/base] Fake SMD sensor with WAKE_GESTURE
diff --git a/core/java/android/hardware/SensorManager.java b/core/java/android/hardware/SensorManager.java
index 5d405f9..278bbc2 100644
--- a/core/java/android/hardware/SensorManager.java
+++ b/core/java/android/hardware/SensorManager.java
@@ -445,6 +445,8 @@ public abstract class SensorManager {
* @see Sensor
*/
public Sensor getDefaultSensor(int type) {
+ if (type == Sensor.TYPE_SIGNIFICANT_MOTION)
+ type = Sensor.TYPE_WAKE_GESTURE;
// TODO: need to be smarter, for now, just return the 1st sensor
List<Sensor> l = getSensorList(type);
boolean wakeUpSensor = false;
Reserved #2
csk1jw said:
p880-ota-eng.mob30jz.zip
Click to expand...
Click to collapse
Perhaps I will finally be tempted into a custom ROM
So far, P880 serves me as an alarm clock, unfortunately.
csk1jw said:
Hi, here's the AOSP Marshmallow ROM that I would like to share with the community.
https://www.androidfilehost.com/?fid=24533100289590699
Thanks for the ground work they had laid out for P880 and Nexus 7 (2012).
@dmitrygr
@alfsamsung
@streambinder
@Demetris
...and...
XDA developers community
Changelog
- Android-6.0.1_r43 (MOB30J)
- 1st Release
Please update your own WiFi MAC address
- Update /system/etc/bcmdhd.cal to inject your own unique MAC address.
Repo patches will be made available shortly for
- lge-kernel-p880 from CyanogenMod
- platform_device_lge_p880 from MoltenMotherBoard
Recommened GApps is modular GApps from @Deltadroid. The minimum required GApps to be installed (which is how I test my setup)
- gapps-base
- gapps-exchange
- gapps-chrome
- gapps-gmail
- gapps-maps
- gapps-search
- gapps-tts
- gapps-webview
- gapps-youtube
This is based on Grouper blobs, so as usual barcode/QR scanning will not work and will not consider this as bug. However, Grouper blobs works with Screen Cast, which for me, is more useful than barcode/QR code scanning.
Let the testing begin!!!:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hey, mate! Good work!
But why "MoltenMotherBoard"? Just to know.
Good work downloading
Edit: I installed and it was running fine until install deltadroid gapps. I found the error. How can i solve this ?
Code:
Process: com.google.android.gms.persistent, PID: 2038
05-10 11:07:17.270 2038 2268 E AndroidRuntime: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1620)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1573)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:606)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:880)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:496)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.util.ae.a(:com.google.android.gms:65)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.util.af.a(:com.google.android.gms:45)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.a.o.a(:com.google.android.gms:40)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.a.p.g(:com.google.android.gms:56)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.a.p.am_(:com.google.android.gms:37)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.ay.a(:com.google.android.gms:318)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.k.a(:com.google.android.gms:207)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.f.a(:com.google.android.gms:164)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.f.a(:com.google.android.gms:73)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.bj.a(:com.google.android.gms:170)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.dh.a(:com.google.android.gms:151)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.cm.a(:com.google.android.gms:60)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.co.a(:com.google.android.gms:126)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.fused.dl.handleMessage(:com.google.android.gms:94)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at com.google.android.location.util.au.dispatchMessage(:com.google.android.gms:50)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
05-10 11:07:17.270 2038 2268 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
05-10 11:07:17.280 2038 2268 I Process : Sending signal. PID: 2038 SIG: 9
Edit2: I found the solution. Install rom, boot and open developer settings(If you are using OpenGapps download and install Android System WebView too). Then install gapps. Boot again rom you will see "setup has been stopped" error. Connect your phone to pc. Open an adb window and type this 3 lines
Code:
adb shell pm grant "com.google.android.setupwizard" android.permission.READ_PHONE_STATE
adb shell pm grant "com.google.android.gms" android.permission.ACCESS_FINE_LOCATION
adb shell pm grant "com.google.android.gms" android.permission.ACCESS_COARSE_LOCATION
Sent from my LG-P880 using XDA-Developers mobile app
Impossible to start the installation process, after you set the wifi, I jump the notice google play services has stopped. Impossible to move forward. I tried to do it several times, but no way.
Imposible, al empezar el proceso de instalación, despues de configura el wifi, me salta el aviso que los servicios de google play se ha detenido. Imposible seguir adelante. He intentado hacerlo varias veces, pero no hay forma.
@CrazyWinner: I don't get any of those permission warnings. You should install GApps right after flashing the ROM zip file without booting the ROM, all in recovery. You should also wipe data//cache/dalvik-cache to start at clean state. The apps will ask for the permission when they are 1st invoked after 1st boot.
Here's my logcat I just capture from reboot to SIM PIN entry, none of the error showed up.
Code:
$ adb logcat | grep "AndroidRuntime"
05-10 08:20:31.650 228 228 D AndroidRuntime: >>>>>> START com.android.internal.os.ZygoteInit uid 0 <<<<<<
05-10 08:20:31.822 228 228 D AndroidRuntime: CheckJNI is OFF
05-10 08:21:23.260 1262 1262 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
@jrcquinito: Did you get the minimum GApps list installed in recovery? Check my reply above. I have been able to gone through Setup Wizard twice, with or without setting up Google account.
Apparently. this is AOSP. It got to work with some GApps before the 1st initial booting. I am only testing deltadroid modular GApps, unfortunately.
csk1jw said:
@CrazyWinner: I don't get any of those permission warnings. You should install GApps right after flashing the ROM zip file without booting the ROM, all in recovery. You should also wipe data//cache/dalvik-cache to start at clean state. The apps will ask for the permission when they are 1st invoked after 1st boot.
@jrcquinito: Did you get the minimum GApps list installed in recovery? Check my reply above. I have been able to gone through Setup Wizard twice, with or without setting up Google account.
Apparently. this is AOSP. It got to work with some GApps before the 1st initial booting. I am only testing deltadroid modular GApps, unfortunately.
Click to expand...
Click to collapse
I tried. But TWRP gives "set metadata recursive some changes failed bad=4" error if rom is not booted. I tried a lot of things , it finally booted and working fine. Thank you for your hard work
PS: Sorry for my bad english
I use the CWM recovery. It is from the official CWM for P880 with updated kernel. I got no errors on install ROM zip or Deltadroid modular GApps zip file.
I still prefer CWM traditional non-touch interface to TWRP or the touch-based CWM.
After install rom go to reboot meny and select reboot bootloader, after reboot install gapps and after reboot in rom. It's for twrp
Отправлено с моего Optimus 4X HD через Tapatalk
how to install
csk1jw said:
I use the CWM recovery. It is from the official CWM for P880 with updated kernel. I got no errors on install ROM zip or Deltadroid modular GApps zip file.
I still prefer CWM traditional non-touch interface to TWRP or the touch-based CWM.
Click to expand...
Click to collapse
To avoid unnecessary problems, you should expressly written in the first post on how to install.
CWM or TWRP does not matter if the installation script is properly prepared.
Hey @csk1jw, I did a clean install of this rom last night via cwm with delta gapps and everything seems to work fine. The only problem I have is the sdcard which is not recognized by the phone or when I plug the phone to my pc. The sdcard is perfectly working otherwise, I checked it with a sdcard adapter.
Mentah said:
Hey @csk1jw, I did a clean install of this rom last night via cwm with delta gapps and everything seems to work fine. The only problem I have is the sdcard which is not recognized by the phone or when I plug the phone to my pc. The sdcard is perfectly working otherwise, I checked it with a sdcard adapter.
Click to expand...
Click to collapse
Did the phone offer to format the SD card? If it did, please backup the data on SD card to allow the phone to format the SD card. I haven't checked out SD card functionality myself yet. Did Android M even offer the option for standalone or adoptable on using SD card?
csk1jw said:
Did the phone offer to format the SD card? If it did, please backup the data on SD card to allow the phone to format the SD card. I haven't checked out SD card functionality myself yet. Did Android M even offer the option for standalone or adoptable on using SD card?
Click to expand...
Click to collapse
There was nothing related to the sd card when I installed the rom. Everything went fine and the sd card is still recognised in cwm. I can tell you that on alfasamsung's cm 13 I always had sd card functionality.
Mentah said:
There was nothing related to the sd card when I installed the rom. Everything went fine and the sd card is still recognised in cwm. I can tell you that on alfasamsung's cm 13 I always had sd card functionality.
Click to expand...
Click to collapse
Alright, I will check it out. Could be something with init or fstab.
@Mentah: Thanks for reporting the issue with SD card. It is fixed now with the updated rootfs. You can apply the fix I attached. I had verified it myself that Android will prompt for SD card notification. It should be simple and does not require going through the initial setup. You just need to flash it from LG fastboot.
Code:
$ and reboot oem-unlock
$ sudo fastboot flash boot boot.img
$ sudo fastboot reboot
csk1jw said:
@Mentah: Thanks for reporting the issue with SD card. It is fixed now with the updated rootfs. You can apply the fix I attached. I had verified it myself that Android will prompt for SD card notification. It should be simple and does not require going through the initial setup. You just need to flash it from LG fastboot.
Code:
$ and reboot oem-unlock
$ sudo fastboot flash boot boot.img
$ sudo fastboot reboot
Click to expand...
Click to collapse
@csk1jw Thank you for looking into it, I will try the fix tomorrow and report back.
Uploaded new build for SD card fix.
No way, I'm back down the rom, rom and install only after the gapps, reboot several times ... the notice has stopped google service installation fails.
No hay manera, he vuelto a bjar la rom, instalar solo la rom y despues la Gapps, reiniciar varias veces... del aviso que se ha parado el servicio de google no pasa la instalación.
My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!
Did a factory reset, which did not solve it. Still no network operators found.
Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?
Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.
yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?
VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.
Opening Security app:
java.lang.ExceptionInInitializerError
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHolder.getAdvertisingId(Unknown Source:0)
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHelper.getGAId(Unknown Source:57)
at com.miui.securityscan.cards.j.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference
at com.xiaomi.ad.mediationconfig.internal.utils.SharedPreferencesWrapper.<init>(Unknown Source:19)
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHolder.<clinit>(Unknown Source:4)
... 6 more
I see this also here: https://xiaomi.eu/community/threads/8-12-20.48265/post-463391
Is it fixable?
Hi!
I have exact same Problem on my Xiaomi Note 5!
Have you tried to Wipe Data = Factory Reset?
It has been fixed in Global Dev 8.12.27
Hey Guys,
I'm on the EEA 10.2.28 Rom and I can't open the Play Store App. I deleted the Play Store App Cache, the Data and all updates but nothing fix the problem. I also deleted the Cache, the Data and all updates from Google play service, but still nothing happens i can't open the play store app.
I also got a crash log:
com.google.android.flib.log.WhatATerribleException: FutureCallback failed
at jkh.a(SourceFile:2)
at aiud.run(SourceFile:3)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6815)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: android.database.sqlite.SQLiteException: not an error (code 0 SQLITE_OK): Could not open the database in read/write mode.
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:211)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:195)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:880)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:865)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:739)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:729)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:355)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:298)
at nqs.a(SourceFile:3)
at nqs.iterator(Unknown Source:1)
at npj.a(SourceFile:5)
at npm.call(Unknown Source:6)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at aivb.run(Unknown Source:2)
at aive.run(SourceFile:16)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at jju.run(Unknown Source:5)
at java.lang.Thread.run(Thread.java:764)
Do you have any ideas to fix the problem [emoji24] [emoji24] [emoji24] [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app
I rooted my Pixel 5a using Magisk and it no longer successfully backs up to Google cloud/Google One.
To be specific:, when I run "Back up Now" from Settings, it runs for a bit and then returns "Pixel 5a: No data backed up" (or if I run backup from the Google One app itself "Pixel 5a: some data not backed up")
Under backup details it says:
Apps No data backed up
Photos & videos: Synced with Google Photos
SMS & MMS messages: No data backed up (though it does seem to backup messages if I run backup from Google One app itself)
Call history: No data backed up
Device settings: No data backed up
Google account data: Synced with Contacts, Calendar, and more
So it seems like the phone is still syncing photos/video and my account data as normal but nothing is being backed up unique to the device.
Note that:
Backup worked properly before rooting and everything else works fine after rooting
I am short but not out of storage on Google cloud (>1GB left)
Under Magisk, I pass the full SafetyNet
I tried clearing backups and re-installing Google One -- all to no avail.
Any thoughts on how to fix or troubleshoot?
Dude! Sorry, I meant to reply yesterday when I got home after I saw this post on the train after work. You can fix this. You can force a backup with adb. After you force the backup it should do it automatically after.
In adb enter:
adb shell
bmgr run
bmgr backupnow --all
Sometimes you'll get an error/fail. If this happens enter:
bmgr backupnow appdata
It won't actually backup anything and is over in one or two seconds. When it's done, enter again:
bmgr backupnow --all
And all of your stuff should start backing up. Like I said earlier, once you do this auto backups should start working again.
Good luck!
I tried the above and it returned 'Success', however I still have the same problem.
Specifically,
The Backup detail screen under settings is unchanged
Apps No data backed up
Photos & videos: Synced with Google Photos
SMS & MMS messages: No data backed up (though it does seem to backup messages if I run backup from Google One app itself)
Call history: No data backed up
Device settings: No data backed up
Google account data: Synced with Contacts, Calendar, and more
Google drive backups still shows that only MMS was backed up
So that whatever was backed up manually via 'adb' doesn't seem to be showing up in Google drive as a backup
Not sure this is relevant, but when running 'bmgr backuppnow --all', I got a lot of messages of form:
Package xxx.xxx.xxx. with result: Transport rejected package because it wasn't able to process it at the time
Indeed this occurred for almost all the packages
(By comparison, I tried the same 'bmgr' commands on my old Samsung S8+ and I got very few packages with transport errors and lots of 'successes'. The backup also took much longer and the progress seemed to indicate significant amounts of data being backed up...)
But bottom line is that I can't seemingly manually or automatically backup the phone
I've never had problems like this. Backup all always works except for apps not gotten from the Play Store. The only thing is I have to sign into every app again. SMS, call history, device settings and Google account Data are always restored
The logcat shows the following errors corresponding to the transport, for example:
09-22 21:22:20.539 1557 11541 I PFTBT : Initiating full-data transport backup of com.android.theme.icon_pack.rounded.themepicker token: 2040284044
09-22 21:22:20.554 1557 11541 I PFTBT : Transport rejected backup of com.android.theme.icon_pack.rounded.themepicker, skipping
09-22 21:22:20.554 1557 11541 I PFTBT : Unbinding agent in com.android.theme.icon_pack.rounded.themepicker
09-22 21:22:20.554 1557 11541 W ActivityManager: Unbinding backup agent with no active backup
puterboy said:
The logcat shows the following errors corresponding to the transport, for example:
09-22 21:22:20.539 1557 11541 I PFTBT : Initiating full-data transport backup of com.android.theme.icon_pack.rounded.themepicker token: 2040284044
09-22 21:22:20.554 1557 11541 I PFTBT : Transport rejected backup of com.android.theme.icon_pack.rounded.themepicker, skipping
09-22 21:22:20.554 1557 11541 I PFTBT : Unbinding agent in com.android.theme.icon_pack.rounded.themepicker
09-22 21:22:20.554 1557 11541 W ActivityManager: Unbinding backup agent with no active backup
Click to expand...
Click to collapse
That doesn't matter. There's several things that have that output, but it makes no difference. What gets backed up successfully is everything that an automatic backup would do. The only difference is now you're seeing the output, but when is was auto before you didn't.
Don't worry, the commands I suggested you use will backup everything that a regular G backup would do.
It's often more comprehensive.
When I'm flashing something that could possibly go wrong (including system updates ~ sometimes something happens and I have to wipe afterwards) I KNOW that using that command will backup everything that it can. Some days sms won't backup on automatic backup, sometimes call logs..,.etc
OK I *partially* solved the problem.
The clue for me was the logging line (found elsewhere in the log):
not performing kv backup "Encryption key has not synced"
Then in the following xda post (https://forum.xda-developers.com/t/guide-google-backup-waiting-to-backup.3895101/post-81931589), I saw the following:
""Starting in Android Pie, devices can take advantage of a new capability where backed-up application data can only be decrypted by a key that is randomly generated at the client. This decryption key is encrypted using the user's lockscreen PIN/pattern/passcode, which isn’t known by Google. Then, this passcode-protected key material is encrypted to a Titan security chip on our datacenter floor. The Titan chip is configured to only release the backup decryption key when presented with a correct claim derived from the user's passcode."
And elsewhere in the thread, people suggested turning off password encryption...
So I removed the login/lock screen password and backups proceeded successfully (both from 'adb/bmgr' and after reboot from 'Settings->Backup' on the phone itself)
UNFORTUNATELY, restoring the login/lock screen password caused the backups to fail again with the same errors as before...
So it appears the problem seems to be with the encryption key not being synced when I have a security password enabled.
Even more annoying, turning login/lock screen password back on seems to delete the previous backup done without protection, leaving me with no Google cloud backup at all.
puterboy said:
Even more annoying, turning login/lock screen password back on seems to delete the previous backup done without protection, leaving me with no Google cloud backup at all.
Click to expand...
Click to collapse
Did you check in Google Drive > backups? It should be still listed there. Changing someone on your phone shouldn't affect what stored on the cloud. If you wipe, during setup you should still get the option to restore your latest backup
xunholyx said:
Did you check in Google Drive > backups? It should be still listed there. Changing someone on your phone shouldn't affect what stored on the cloud. If you wipe, during setup you should still get the option to restore your latest backup
Click to expand...
Click to collapse
After adding back security, it does seem to get completely wiped from Google Drive. Indeed, under backup, it says "Your Device is not backed up" -- though backups from my other devices are there untouched.
So adding back security seems to reset/wipe any old backup created without security...
Not sure this is helpful, but found this in the 'logcat' when doing a "Backup Now" operation from the phone:
09-23 21:20:59.303 3191 14292 E Backup : [BackUpNowOperation] Waiting for key to sync timed out09-23 21:20:59.303 3191 14292 E Backup : java.util.concurrent.TimeoutException: Waited 45000 milliseconds (plus 156618 nanoseconds delay) for [email protected][status=PENDING]09-23 21:20:59.303 3191 14292 E Backup : at ccrq.get[email protected]@21.33.14 (150400-395723304):38)09-23 21:20:59.303 3191 14292 E Backup : at qhc.d[email protected]@21.33.14 (150400-395723304):1)09-23 21:20:59.303 3191 14292 E Backup : at qhc.f[email protected]@21.33.14 (150400-395723304):6)09-23 21:20:59.303 3191 14292 E Backup : at adhi.run[email protected]@21.33.14 (150400-395723304):17)09-23 21:20:59.303 3191 14292 E Backup : at bxdu.run[email protected]@21.33.14 (150400-395723304):2)09-23 21:20:59.303 3191 14292 E Backup : at uwo.c[email protected]@21.33.14 (150400-395723304):6)09-23 21:20:59.303 3191 14292 E Backup : at uwo.run[email protected]@21.33.14 (150400-395723304):7)09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)09-23 21:20:59.303 3191 14292 E Backup : at vcm.run[email protected]@21.33.14 (150400-395723304):0)09-23 21:20:59.303 3191 14292 E Backup : at java.lang.Thread.run(Thread.java:923)09-23 21:20:59.325 3191 14292 I Backup : [BackUpNowOperation] Backup done for all packages, result code: 29011Again, suggesting that there is some issue with syncing the encryption key corresponding to the security passcode.
puterboy said:
Not sure this is helpful, but found this in the 'logcat' when doing a "Backup Now" operation from the phone:
09-23 21:20:59.303 3191 14292 E Backup : [BackUpNowOperation] Waiting for key to sync timed out
09-23 21:20:59.303 3191 14292 E Backup : java.util.concurrent.TimeoutException: Waited 45000 milliseconds (plus 156618 nanoseconds delay) for [email protected][status=PENDING]09-23 21:20:59.303 3191 14292 E Backup : at ccrq.get[email protected]@21.33.14 (150400-395723304):38)09-23 21:20:59.303 3191 14292 E Backup : at qhc.d[email protected]@21.33.14 (150400-395723304):1)09-23 21:20:59.303 3191 14292 E Backup : at qhc.f[email protected]@21.33.14 (150400-395723304):6)09-23 21:20:59.303 3191 14292 E Backup : at adhi.run[email protected]@21.33.14 (150400-395723304):17)09-23 21:20:59.303 3191 14292 E Backup : at bxdu.run[email protected]@21.33.14 (150400-395723304):2)09-23 21:20:59.303 3191 14292 E Backup : at uwo.c[email protected]@21.33.14 (150400-395723304):6)09-23 21:20:59.303 3191 14292 E Backup : at uwo.run[email protected]@21.33.14 (150400-395723304):7)09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)09-23 21:20:59.303 3191 14292 E Backup : at vcm.run[email protected]@21.33.14 (150400-395723304):0)09-23 21:20:59.303 3191 14292 E Backup : at java.lang.Thread.run(Thread.java:923)09-23 21:20:59.325 3191 14292 I Backup : [BackUpNowOperation] Backup done for all packages, result code: 29011
Again, suggesting that there is some issue with syncing the encryption key corresponding to the security passcode.
Click to expand...
Click to collapse
I'm really not sure. I use this to force backups even when I have a recent one on my Pixel 5 and 2xl. I've had to use it in the past on both when backups didn't start automatically. I actually used this for beta 12/5 when I was visiting my dad for his birthday.
(I had problems with getting fastboot to work on his PC and ended having to wipe when I got home a couple of days later to re-root)
I ended up just 'factory resetting' my phone and starting from scratch -- first rooting, then restoring apps, then adjusting settings, then using the Magisk SafetyNet-fix.... each step-by-step, testing backup after each change...
And to my relief, it works and continued to work at each step...
Somehow, something must have gotten "wacked" in my previous setup and was not able to be reset (despite clearing caches and data stores on Google Play Services, Google Play Store, Google One, Google Pay, etc). But a full factory reset did solve it.
Unfortunately, while Swiftbackup restored my apps and most of their settings, I had to manually redo all the Android settings since there was (obvoiusly) no Android backup that I could use to restore them... this took hours...
But in any case, it works and perhaps this thread will be useful to others should they encounter this problem...
I have the same issue. Still has no clue on solving it except temporary disabling the lockscreen passcode.