Hello,
I have a problem related to album,when i try to open faces the app force close,i know the problem is related to SomcPhotoAnalyzer so i tried to clear data for both album and somcphotoanalyzer but still not working,i attached the log if anyone could help.thanks.
I'm having the same issue since a long time already. I have searched all around and tried a lot of things (clear data of all related apps, installing different versions of the apps in different locations) but nothing seems to solve it.
There are several people throughout the forums that have the same problem.
I do let it crash regularly and send crash reports in the hopes Sony fixes it...
Same here, searching for fix...
Maybe someone with more knowledge can help us, here is the log from the bug (I made it crash twice)
Code:
(logcat)
======================
Process Photo Analyzer(com.sonymobile.photoanalyzer)
E/22:46:31.573 at android.os.Binder.execTransact(Binder.java:453)
E/22:46:31.573 at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/22:46:31.573 at android.content.ContentProvider$Transport.query(ContentProvider.java:238)
E/22:46:31.573 at android.content.ContentProvider.query(ContentProvider.java:1017)
E/22:46:31.573 at com.sonymobile.photoanalyzer.provider.face.FaceRecognitionProvider.query(FaceRecognitionProvider.java:520)
E/22:46:31.573 java.lang.SecurityException: caller is not grant
E/22:46:31.573 Writing exception to parcel
W/22:46:31.573 certificate is not match: 6339375AC295CB0CD22811B97ACCD40104BD4A0185D4DD2289B81860C15D623C
W/22:46:31.449 [MessageHandlerThread]processFaceRecognition() please check permission:caller is not grant
W/22:46:31.449 certificate is not match: BC01A8CD9E5D87854F6DC4C84AED49EDC34AC196C00B89623CEA6CCBBDEA627B
W/22:43:59.615 [MessageHandlerThread]processFaceRecognition() please check permission:caller is not grant
E/22:43:59.612 at android.os.Binder.execTransact(Binder.java:453)
E/22:43:59.612 at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/22:43:59.612 at android.content.ContentProvider$Transport.query(ContentProvider.java:238)
E/22:43:59.612 at android.content.ContentProvider.query(ContentProvider.java:1017)
E/22:43:59.612 at com.sonymobile.photoanalyzer.provider.face.FaceRecognitionProvider.query(FaceRecognitionProvider.java:520)
E/22:43:59.612 java.lang.SecurityException: caller is not grant
E/22:43:59.612 Writing exception to parcel
W/22:43:59.611 certificate is not match: 6339375AC295CB0CD22811B97ACCD40104BD4A0185D4DD2289B81860C15D623C
W/22:43:59.605 certificate is not match: BC01A8CD9E5D87854F6DC4C84AED49EDC34AC196C00B89623CEA6CCBBDEA627B
I/22:43:59.221 Connecting to camera service
Thanx in advance
Edit:
Already tried remove app data
Already tried fix permissions
Related
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
EDIT: maybe it was related to Maps since I installed maps 7.x I don't see that process anymore!
moly82 said:
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
Click to expand...
Click to collapse
Maybe you have some program/app installed which uses the download manager? Some app trying to download an update outside of the regular mechanism? I don't see DownloadService running on my phone unless I instructed it to download something. Do you notice anything downloadmanager/media related in logcat? If in doubt, attach the phone to a PC, run the following commands and attach the resulting file ('attach_me.txt') here:
Code:
adb shell 'ps; echo -----------;logcat -v time -b main -b system -b events -d;echo -----------;dumpsys;' > attach_me.txt
Use the full path to adb if you need to.
This shows the currently running processes (ps), the contents of the main, system and event logs (logcat) and a snapshot of the current state of your phone (dumpsys). If there is anything there you don't want to show to the whole world edit the resulting file before attaching it here.
thanks a lot for the reply my friend
tonight at home I think I will be able to run the adb command you suggested me (in my home computer I have sdk installed)
so far I checked logcat in terminal ("logcat |grep edia" and "logcat |grep ownload") and this is what I got:
$ su
# logcat |grep edia
D/Vold ( 1197): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1197): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageParser( 1626): No actions in intent filter at /data/app/org.wikipedia-1.apk Binary XML file line #39
I/ActivityManager( 1626): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=1765 uid=10011 gids={50011, 1015, 1023, 1024, 1028, 2001, 3003, 3007}
V/ActivityThread( 1765): android.process.media white listed for hwui
D/SystemUIService( 1701): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 1701): running: [email protected]
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothHeadset.:273 android.bluetooth.BluetoothAdapter.getProfileProxy:1155 android.media.AudioService.getBluetoothHeadset:2198 android.media.AudioService.access$2800:104
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothA2dp.:160 android.bluetooth.BluetoothAdapter.getProfileProxy:1158 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4087 android.app.LoadedApk$ReceiverDispatcher$Args.run:758
$ su
# logcat|grep ownload
I/ActivityManager( 1624): Start proc com.google.android.youtube for broadcast com.google.android.youtube/.core.transfer.DownloadService$BootReceiver: pid=2305 uid=10050 gids={50050, 3003, 1015, 1006, 1028}
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
I'm attaching also screenshots of the process I'm talking about
EDIT: I reinstalled everyting from scratch as a new build by quarx came out.. it seems that installing only cm build + minimal gapps, that process doesn't show up. Later after I installed back all my apps (via app2zip flashable zip) the process showed up again.. so probably you are right and there is a certain app using that process.. but how can I understand which one has relation with that service? maybe YouTube as i see it mentioned in logcat?
delete
i could generate the logs you asked without using the pc but using the phone terminal and multiple commands.. i'm uploading them to my dropbox links are below thanks in advance..
http://db.tt/gJLBYeT7
http://db.tt/OahQ8Zf7
http://db.tt/KPUTy4et
YAFU what happened to you?
it seems to me after I installed latest maps 7.x the media > download process is not appearing anymore in running processes.. maybe it was related to sh*tty maps??? :fingers-crossed:
Hello together,
I recently made an update of LineageOS for my LG G5 (LineageOS 14.1) as well as my Samsung Galaxy S5 (LineageOS 15.1). They both seem to have serious issues afterwards and I don't know what happened. I assume something has changed within the last month or so and my problem appears with both devices.
It appears as if the permissions for all GApps have changed (or the uids perhaps). All other apps work perfectly fine so far. I also downloaded the latest GApps and installed them via TWRP but that doesn't seem to solve any problem. However I'm not sure that overwrites the old applications or only installs currently not installed ones.
So when ever I use one of these apps (Gmail, Playstore, Maps, some of the system processes), it always crashes and I see the log messages looking like this:
Code:
com.google.android.gms.persistent, PID: 13071
java.lang.RuntimeException: Unable to create application
com.google.android.gms.common.app.GmsApplication:
java.lang.SecurityException: addOnPermissionsChangeListener:
Neither user 10039 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5451)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1564)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
or
Code:
java.lang.SecurityException: Permission Denial: opening provider
com.google.android.gsf.gservices.GservicesProvider from
ProcessRecord{22a7d3b 23968:com.google.android.youtube/u0a108}
(pid=23968, uid=10108) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
at android.os.Parcel.readException(Parcel.java:1684)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4199)
or
Code:
java.lang.SecurityException: tname=Sensors - Permission Denial: opening provider com.google.android.gsf.gservices.GservicesProvider from ProcessRecord{3745b29 6048:com.google.android.apps.maps/u0a179} (pid=6048, uid=10179) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
They all have in common that they tell me that "Neither user [???] nor current process has android.permission.[???] "
It seems to work uninstalling the specific app and reinstalling it. However this is a lot of work and isn't really easy for some apps that are closer to the system.
So what can I do? What exactly is the problem here? Did the UIDs change? Any suggestions please!
A developer reported that an app downloaded from AppGallery could not be installed.
After checking the message to find out more details about the error, I discovered that the error message was actually "Conflicting provider (Error code: -13)", indicating that ContentProvider of the downloaded app conflicted with that of an existing app. The system also provided a description of the error and recommended a solution.
Generally, if a provider conflict occurs when you install an app, it is probably because an existing app has the same ContentProvider. ContentProvider is one of the four Android elements, although it very rarely used. The ContentProvider feature interacts and shares data between processes, which determines that it must be globally unique. Once an app has registered a ContentProvider on the phone, the app installed later cannot use the same ContentProvider. Otherwise, installation will fail.
As expected, installation failed when we found the same ContentProvider settings in the AndroidManifest.xml file after checking the two conflicting apps.
In this case, you can modify the ContentProvider information and install the app again to resolve the problem.
You may have encountered app installation failures during app development. Lets take a look at some of the most often reported errors on Huawei devices, what they mean and how you as a developer can fix them!
The app package is invalid, incomplete, or incompatible with the operating system (result code: -2).
Cause analysis: An invalid package is uploaded for a third-party app.
Solution: Upload a valid app package.
Insufficient storage space (result code: -4).
Cause analysis: The storage space is insufficient for installing an app.
Solution: Open Optimizer and tap Cleanup to free up some storage space on your phone.
An app with the same package name has already been installed on the device (result code: -5).
Cause analysis: The app cannot be installed as the package name already exists.
Solution: Change the package name to a new one.
Incompatible update (result code: -7).
Cause analysis: The package name of the later version is the same as that of the earlier version currently installed, but their signatures are different.
Solution: Change the signature of the later version to that of the earlier one.
Incompatible app that supports ShareUid (result code: -8).
Cause analysis: The installation failed because the signature of the to-be-installed app that supports ShareUid is different from that of the installed app that supports ShareUid.
Solution: Ensure that the signature is the same as that of the installed app that supports ShareUid.
The shared library is lost (result code: -9).
Cause analysis: The Google Maps library that the app depends on does not exist. As a result, the app installation failed.
Solution: It is recommended that you integrate HMS Core into your app to avoid such dependency issues.
An element name of the to-be-installed app is the same as that of an installed app (result code: -13).
Cause analysis: The ContentProvider defined in the app is the same as that of an installed app.
Perform the following steps to find the conflict:
View logs and check the installation failure callback information.
Run the adb command to obtain all ContentProvider definitions on the device, and find the app that caused the conflict. adb shell dumpsys package providers >d:/temp/provider.txt Solution:Uninstall the conflicting app or resolve the conflict.
The app is incompatible with the CPU of the device (result code: -113 or -16).
Cause analysis: Adaptations for specific CPU versions were not performed when the app was packaged.
Solution: Adapt the app for the CPU version of the device in question.
App verification timed out (result code: -21), and app verification failed (result code: -22).
Cause analysis: When the app was being automatically verified by Google Play, the network connection timed out. Usually, the preceding process is not triggered unless Google Play has been updated by the user or by a downloaded app, which leads to verification timeout.
Solution: On the device, go to Settings > Apps > Google Play Services and tap DISABLE on the App info page, or go to Settings > Apps > Google Play Services Updater and tap Uninstall updates in the upper right corner. Then click FORCE STOP (if available) to deactivate the app if it is still displayed in the app list.
On the device, ensure that Google Play Protect is disabled.
The app package failed to be installed because a later version has been installed (result code: -25).
Cause analysis: Android devices allow for the creation of multiple user accounts. A non-owner account may have downloaded and installed a later version of the app in PrivateSpace for testing purposes. If so, the installation will fail.
Solution: Check whether a later version of the app is installed in PrivateSpace by a non-owner account. If so, uninstall the app and install it again.
Parsing failed (result code: -102).
Cause analysis: An error occurred when generating the package, causing parsing to fail.
Solution: Contact the technical support of the corresponding channel to check logs to locate the download path, download the APK again using a browser, and then install the APK in ADB mode to check whether the error occurs again.
The app package does not contain any certificates (result code: -103).
Cause analysis: The app package is for Early Access targeting specific users and does not contain any certificates.
Solution: Add a certificate to the app package.
Unknown error (result code: -111).
Cause analysis: The device is a TD Tech dual-system policing terminal and is customized to limit app installation.
Solution: Instruct users to contact TD Tech for assistance.
If anyone knows descriptions to miuiop please share, I'm curious what they do.
What App Ops does is allow a user to revoke an individual permission for an app. When the app then starts and tries to make an Android system call to access something that the user has now forbidden then Android will return an error and won’t grant access to that data or functionality.
As you can see there are several numbers starting with 100xx. These are the app IDs (UID = user IDs) the system is dealing with. Every app has a corresponding UID which is needed for file permission rights. Example: If only a certain app (UID 10666) has the permission to open a certain folder, the folder will be restricted to u0_a666 (=user 0, that's you, + app UID 10666)
Usually the first UID slots 10001, 10002, ... are system apps since they get started first upon an initial boot of your device. I assume that MIUIOP belongs to the MIUI optimization, but not sure about that. But you can figure it out with the help of the UIDs:
Apk Analyzer - Apps on Google Play
Detailed reports of the applications on your device. 📱
play.google.com
Selecting an app shows you its UID. Unfortunately it doesn't show you the UID in the app's list directly.
So the uid number could be different across different miui versions… unlike standard appops which are the same regardless of device?
Posting a list of the apps just because:
10008 com.miui.core.internal.editor.services
10017 - com.miui.systemui.overlay.devices.android
10020 - com.android.theme.font.notoserifsource (Noto Serif / Source Sans Pro)
10026 - com.android.internal.systemui.onehanded.gestural (One Handed Mode)
10033 - com.android.overlay.gmstelephony
10036 - com.android.systemui.gesture.line.overlay
10037 - com.miui.systemui.carriers.overlay
The app UIDs are assigned ongoing by your system on first boot (for system apps) or after installation (for user apps). Example: The first app you install on your device gets the UID 10201 then the second one gets 10202 and so on. It doesn't depend on your MIUI version or sth like this.