Dear community
I have an issue with my front camera on my Zuk Z2 Pro. I cannot switch to front camera only back camera works. There is no symbol for switching to the front camera beside the "shot" button in the camera app.
I tried to check the camera settings, but the as soon I try to navigate into the "Front camera photo" or "Front camera video" I just get a white screen with the title "camera" and nothing else.
I also installed other camera apps, but also no front camera access...
I have this issue since ever but I thought I'd better wait for Android 7 Nougat update, before asking you guys.
So this morning I updated phone from Stock ZUI 2.3.044 ST via OTA to ZUI v 2.5.335 - unfortunately the issues persists
Below you will also find crash log (I guess). Hope someone can help me out and has some idea how to solve this.
Thank you very much in advance for your help.
LOG:
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@78c38f3
versionCode=21
BOARD=QC_Reference_Phone
BOOTLOADER=unknown
TYPE=user
ID=NRD90M
TIME=1484568612000
BRAND=ZUK
TAG=Build
HARDWARE=qcom
SERIAL=XXX removed
SUPPORTED_ABIS=[Ljava.lang.String;@f0079b0
CPU_ABI=arm64-v8a
IS_DEBUGGABLE=false
RADIO=unknown
MANUFACTURER=ZUK
IS_EMULATOR=false
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@ac2f62
TAGS=release-keys
CPU_ABI2=
UNKNOWN=unknown
PERMISSIONS_REVIEW_REQUIRED=false
USER=buildslave
FINGERPRINT=ZUK/z2_row/z2_row:7.0/NRD90M/2.5.335_170116:user/release-keys
HOST=byws6
versionName=0.9.0.0
PRODUCT=z2_row
DISPLAY=NRD90M dev-keys
MODEL=ZUK Z2121
DEVICE=z2_row
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.zui.cameragallery/com.zui.cameragallery.camera.settings.SettingsPreferenceActivity}: java.lang.NullPointerException: Attempt to get length of null array
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2695)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2768)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1481)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6153)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)
Caused by: java.lang.NullPointerException: Attempt to get length of null array
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.getSavedSltPos(SettingsPreferenceActivity.java:296)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.refreshListView(SettingsPreferenceActivity.java:256)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.initView(SettingsPreferenceActivity.java:212)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.onCreate(SettingsPreferenceActivity.java:128)
at android.app.Activity.performCreate(Activity.java:6705)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2648)
... 9 more
java.lang.NullPointerException: Attempt to get length of null array
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.getSavedSltPos(SettingsPreferenceActivity.java:296)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.refreshListView(SettingsPreferenceActivity.java:256)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.initView(SettingsPreferenceActivity.java:212)
at com.zui.cameragallery.camera.settings.SettingsPreferenceActivity.onCreate(SettingsPreferenceActivity.java:128)
at android.app.Activity.performCreate(Activity.java:6705)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2648)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2768)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1481)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6153)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)
Did you find any fix for this?
Hi everyone, my camera app is crashing after 3-5 seconds of black screen, I have already cleaned data and cache, also tried other apps, no luck, even a factory reset didnt change anything.
Here is the log written by the app:
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@419cd4a
versionCode=21
BOARD=QC_Reference_Phone
BOOTLOADER=unknown
TYPE=user
ID=NRD90M
TIME=1484568612000
BRAND=ZUK
TAG=Build
HARDWARE=qcom
SERIAL=24d72879
SUPPORTED_ABIS=[Ljava.lang.String;@cc524bb
CPU_ABI=arm64-v8a
IS_DEBUGGABLE=false
RADIO=unknown
MANUFACTURER=ZUK
IS_EMULATOR=false
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@9292b5
TAGS=release-keys
CPU_ABI2=
UNKNOWN=unknown
PERMISSIONS_REVIEW_REQUIRED=false
USER=buildslave
FINGERPRINT=ZUK/z2_row/z2_row:7.0/NRD90M/2.5.335_170116:user/release-keys
HOST=byws6
versionName=0.9.0.0
PRODUCT=z2_row
DISPLAY=NRD90M dev-keys
MODEL=ZUK Z2121
DEVICE=z2_row
java.lang.RuntimeException: Media server died.
at com.zui.cameragallery.camera.CameraErrorCallback.onError(CameraErrorCallback.java:33)
at com.zui.cameragallery.ex.camera.portability.AndroidCameraAgentImpl$ErrorCallbackForward$1.run(AndroidCameraAgentImpl.java:1210)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6153)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)
Thanx in advance.
Camera module replaced, still not working
I bought a replacement in Ali express, and after replace the module, same error, now running in Oreo.
any ideas?
Hey I could really appreciate some help with that problem and please excuse all style problems it's my first post.
Information:
OnePlus 5T
OxygenOS 5.1.3
Magisk V 16.0
So here's the Problem:
Everytime I try to deactivate or delete a module named Adaptive icons Round Mask my device gets into a bootloop. I tried to uninstall it with the manager app and in recovery. Also i uninstalled magisk but it got still into the bootloop. I think that there's still a modifaction left that tries to load the module which i have to delete but i have no plan where it could be. I also found an error in the android_boot.log:
Code:
06-23 12:43:11.553 3144 3144 W ziparchive: Unable to open '/vendor/overlay/RoundMaskOverlay.apk': No such file or directory
06-23 12:43:11.553 3144 3144 W zipro : Error opening archive /vendor/overlay/RoundMaskOverlay.apk: I/O error
06-23 12:43:11.553 3144 3144 D asset : failed to open Zip archive '/vendor/overlay/RoundMaskOverlay.apk'
06-23 12:43:11.553 3144 3144 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 3144 (main), pid 3144 (main)
06-23 12:43:11.584 3178 3178 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
06-23 12:43:11.584 1048 1048 I /system/bin/tombstoned: received crash request for pid 3144
06-23 12:43:11.587 3178 3178 I crash_dump64: performing dump of process 3144 (target tid = 3144)
Thanks for any help.
Same issue...
I can only restore my nandroid backup now.
Edit:
As the repo is already deleted, I find this in Google cache:
https://webcache.googleusercontent....Icons-Round-Mask/issues/4+&cd=1&hl=en&ct=clnk
But anyway, it's not a permanent solution. Can anyone advise how to remove this module completely? Thanks!
PS. The module is here: https://forum.xda-developers.com/showpost.php?p=76861990&postcount=794
edison0354 said:
Edit:
As the repo is already deleted, I find this in Google cache:
Click to expand...
Click to collapse
I'm using the same temporary solution as mentioned in that google link.
Finally, find a solution...
Tested on Nexus 5 & Nexus 7 2013, both on LineageOS 14.1, but, do it on your own risk, better do a nandroid backup before.
1. Disable this module in Magisk manager;
2. Install Substratum https://play.google.com/store/apps/details?id=projekt.substratum&hl=en ;
3. Open Substratum using legacy root mode, in manager page, you will see a null module, select and delete it;
4. Reboot, everything should be fine.
In your case, I think you only need to delete the module using substratum manager.
How do i use legacy root mode?
Edit:
Ok i think i found the magisk module but it says it can't be installed on Oreo and above.
And in my manager page aren't any modules.
RDM.NSA said:
How do i use legacy root mode?
Edit:
Ok i think i found the magisk module but it says it can't be installed on Oreo and above.
And in my manager page aren't any modules.
Click to expand...
Click to collapse
I'm on 7.1.2, so by default it goes to legacy mode because Nougat doesn't support the newer mode...
Please check if there's any trigger in setting or somewhere else to switch to legacy mode, my Oreo device doesn't have this magisk module install so I can't help you, sorry...
Hi guys, this is my first thread I write on xda and I'm italian so, please, forgive me if I don't write so good. Today I flashed on my nexus 6 the last twrp recovery and then the lineage 16 rom released yesterday. Before rebooting I flashed the open gapps zip Platform arm, android 9, variant stock that includes the pixel launcher. Unluckly, when I boot the system, the pixel launcher keeps interrupting automatically so I'm forced to select the trebuchet as default launcher. I wanna say that I faced this issue even with lineage 15 so I guess the problem isn't given by the rom. Some tips on how I can solve this issue?
I also installed the stock variant of Gapps. Pixel Launcher keeps crashing for me too. Also the Android Setup wizard keeps crashing and will not complete. Did you also experience this? Other than that, Lineage 16 seems to be working fine for me.
nhasian said:
I also installed the stock variant of Gapps. Pixel Launcher keeps crashing for me too. Also the Android Setup wizard keeps crashing and will not complete. Did you also experience this? Other than that, Lineage 16 seems to be working fine for me.
Click to expand...
Click to collapse
No, I completed the setup wizard without any problem.
I am seeing this issue as well. Are any of you rooted with Magisk?
mattewthep said:
Hi guys, this is my first thread I write on xda and I'm italian so, please, forgive me if I don't write so good. Today I flashed on my nexus 6 the last twrp recovery and then the lineage 16 rom released yesterday. Before rebooting I flashed the open gapps zip Platform arm, android 9, variant stock that includes the pixel launcher. Unluckly, when I boot the system, the pixel launcher keeps interrupting automatically so I'm forced to select the trebuchet as default launcher. I wanna say that I faced this issue even with lineage 15 so I guess the problem isn't given by the rom. Some tips on how I can solve this issue?
Click to expand...
Click to collapse
A log would be handy. Otherwise no one will look into this bug.
log
Elektroschmock said:
A log would be handy. Otherwise no one will look into this bug.
Click to expand...
Click to collapse
I'm far from being pro, but looks like something with permission.
"03-05 12:36:57.572 W/ActivityManager(748): Permission Denial: setShelfHeight() from pid=9545, uid=10012 requires android.permission.STATUS_BAR
03-05 12:36:57.573 D/AndroidRuntime(9545): Shutting down VM
03-05 12:36:57.575 E/AndroidRuntime(9545): FATAL EXCEPTION: main
03-05 12:36:57.575 E/AndroidRuntime(9545): Process: com.google.android.apps.nexuslauncher, PID: 9545
03-05 12:36:57.575 E/AndroidRuntime(9545): java.lang.RuntimeException: Unable to resume activity {com.google.android.apps.nexuslauncher/com.google.android.apps.nexuslauncher.NexusLauncherActivity}: java.lang.SecurityException: Permission Denial: setShelfHeight() from pid=9545, uid=10012 requires android.permission.STATUS_BAR"
nhasian said:
I also installed the stock variant of Gapps. Pixel Launcher keeps crashing for me too. Also the Android Setup wizard keeps crashing and will not complete. Did you also experience this? Other than that, Lineage 16 seems to be working fine for me.
Click to expand...
Click to collapse
I solved the issue giving to the launcher all permissions, try this way
mattewthep said:
I solved the issue giving to the launcher all permissions, try this way
Click to expand...
Click to collapse
I tried this approach when I first installed the update but it did not work. When I get a chance, I will try again with updated builds.
Any of you guys with the Pixel launcher error have ADB fired up and willing to check this out as a workaround?:
https://developer.android.com/reference/android/Manifest.permission.html#STATUS_BAR
https://github.com/TilesOrganization/support/wiki/How-to-use-ADB-to-grant-permissions
tldr;
STATUS_BAR:
Allows an application to open, close, or disable the status bar and its icons.
Not for use by third-party applications.
Constant Value: "android.permission.STATUS_BAR"
adb shell pm [grant|revoke] com.google.android.apps.nexuslauncher android.permission.STATUS_BAR
adb shell dumpsys com.google.android.apps.nexuslauncher
Raksi said:
Any of you guys with the Pixel launcher error have ADB fired up and willing to check this out as a workaround?:
https://developer.android.com/reference/android/Manifest.permission.html#STATUS_BAR
https://github.com/TilesOrganization/support/wiki/How-to-use-ADB-to-grant-permissions
tldr;
STATUS_BAR:
Allows an application to open, close, or disable the status bar and its icons.
Not for use by third-party applications.
Constant Value: "android.permission.STATUS_BAR"
adb shell pm [grant|revoke] com.google.android.apps.nexuslauncher android.permission.STATUS_BAR
adb shell dumpsys com.google.android.apps.nexuslauncher
Click to expand...
Click to collapse
No. I have not seen this anywhere. I will try it later in the week when time permits.
zzenyoo said:
I'm far from being pro, but looks like something with permission.
"03-05 12:36:57.572 W/ActivityManager(748): Permission Denial: setShelfHeight() from pid=9545, uid=10012 requires android.permission.STATUS_BAR
03-05 12:36:57.573 D/AndroidRuntime(9545): Shutting down VM
03-05 12:36:57.575 E/AndroidRuntime(9545): FATAL EXCEPTION: main
03-05 12:36:57.575 E/AndroidRuntime(9545): Process: com.google.android.apps.nexuslauncher, PID: 9545
03-05 12:36:57.575 E/AndroidRuntime(9545): java.lang.RuntimeException: Unable to resume activity {com.google.android.apps.nexuslauncher/com.google.android.apps.nexuslauncher.NexusLauncherActivity}: java.lang.SecurityException: Permission Denial: setShelfHeight() from pid=9545, uid=10012 requires android.permission.STATUS_BAR"
Click to expand...
Click to collapse
I wonder why the app name isn't com.google.android.apps.pixellauncher
No luck.
Seems like despite the launcher/something_else needs it, the manifest file does not request it.
Code:
[[email protected] platform-tools]# ./adb shell pm
...
grant [--user USER_ID] PACKAGE PERMISSION
revoke [--user USER_ID] PACKAGE PERMISSION
These commands either grant or revoke permissions to apps. [COLOR="Red"]The permissions
must be declared as used in the app's manifest[/COLOR], be runtime permissions
(protection level dangerous), and the app targeting SDK greater than Lollipop MR1.
...
Code:
[[email protected] platform-tools]# ./adb shell pm grant com.google.android.apps.nexuslauncher android.permission.STATUS_BAR
Security exception: Package com.google.android.apps.nexuslauncher has not requested permission android.permission.STATUS_BAR
java.lang.SecurityException: Package com.google.android.apps.nexuslauncher has not requested permission android.permission.STATUS_BAR
at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:379)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5475)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21418)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2821)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3920)
at android.os.Binder.execTransact(Binder.java:731)
Code:
[[email protected] platform-tools]# ./adb shell pm grant com.google.android.apps.nexuslauncher android.permission.STATUS_BAR_SERVICE
Security exception: Package com.google.android.apps.nexuslauncher has not requested permission android.permission.STATUS_BAR_SERVICE
java.lang.SecurityException: Package com.google.android.apps.nexuslauncher has not requested permission android.permission.STATUS_BAR_SERVICE
at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:379)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5475)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21418)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2821)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3920)
at android.os.Binder.execTransact(Binder.java:731)
Packing error? Wonder if I'm able to edit the manifest on the device.
Raksi said:
Packing error? Wonder if I'm able to edit the manifest on the device.
Click to expand...
Click to collapse
I do not think you can edit the manifest without decompiling.
Look, someone opened an issue with OpenGapps:
https://github.com/opengapps/opengapps/issues/727
Code:
eth481642 commented 7 hours ago •
After installing Lineage OS 16.0 with latest opengapps(stock variant) on Nexus 6, pixel launcher crashes. It looks like there is some kind of permission problem
All hail hypnotoa... i mean eth481642!
For those of you that use Magisk, installing this module fixed the problem for me. It breaks Trebuchet, but after you switch to the Pixel launcher, everything works as expected.
https://forum.xda-developers.com/showpost.php?p=78029447&postcount=483
David B. said:
For those of you that use Magisk, installing this module fixed the problem for me. It breaks Trebuchet, but after you switch to the Pixel launcher, everything works as expected.
https://forum.xda-developers.com/showpost.php?p=78029447&postcount=483
Click to expand...
Click to collapse
Ha! It works! :highfive:
zzenyoo said:
Ha! It works! :highfive:
Click to expand...
Click to collapse
Yup! I can't figure out what it does, but it does indeed work. Unfortunately this is merely a band-aid for the problem, but at least it's a start.
So, apparently the kind devs at opengapps did solve it a few weeks ago:
Adding STATUS_BAR and MANAGE_ACTIVITY_STACKS indeed solves the problem.
Click to expand...
Click to collapse
I was a bit late but can confirm the new 2020.01.24 stock opengapps has a working Pixel Launcher!
Did a dirty update over my current rom as I already had the same package.
The Pixel Launcher forces close because he's not the recents provider, i fix this issue using Quickswitch magisk module
Got into a bootloop with the newest LOS16 nightly "Feb 1". and the previously mentioned OpenGapps Jan24.
After a few combinations of LOS nightly only factory reset solved it for me. As soon as I installed the Jan24 opengapps... bootloop.
Now LOS Jan30 nightly with OpenGapps Jan 31 stock booted up. Setting back everything. Donno what happened.
I recently downgraded my rog phone 3 from android 12 to android 11 while rooting it with twrp and magisk. After I did this, everything worked fine on my system (besides mms for a moment), once it is flashed, the first reboot afterwards completely stops bluetooth from functioning. No startup, nothing. The drivers are just nonfunctional I guess. Anyone else have this issue/ know how to solve? Not very fluent in this and just looking to fix this asap.
Also here is a logcat error that shows itself when I try to enable bluetooth.
FATAL EXCEPTION: BluetoothDatabaseManager
Process: com.android.bluetooth, PID: 2430
android.database.sqlite.SQLiteCantOpenDatabaseException: Cannot open database '/data/user_de/0/com.android.bluetooth/databases/bluetooth_db': Directory /data/user_de/0/com.android.bluetooth/databases doesn't exist
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:252)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:205)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:918)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:898)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:762)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:751)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:373)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:316)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:145)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:106)
at androidx.room.RoomDatabase.inTransaction(RoomDatabase.java:476)
at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.java:281)
at com.android.bluetooth.btservice.storage.MetadataDao_Impl.load(MetadataDao_Impl.java:258)
at com.android.bluetooth.btservice.storage.MetadataDatabase.load(MetadataDatabase.java:95)
at com.android.bluetooth.btservice.storage.DatabaseManager$DatabaseHandler.handleMessage(DatabaseManager.java:124)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:248)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:224)
... 20 more
I really need help with this if anyone could spare the time.
I have dumped the same stock rom I installed and I have noticed it is missing the bluetooth APEX file. Is it even possible to install an APEX file without reinstalling an entire system? I know the format is similar to APK and i have read/write access to my system partition, so is it possible to do?
Try setting selinux to permissive (from a root command line, run "setenforce 0"). I have a similar issue (messed up permissions when downgrading and I'm trying to debug it now. I'm trying to figure out how to fix those permissions without disabling selinux entirely, as disabling it is a massive security hole.