-
Notifications
You must be signed in to change notification settings - Fork 103
Problem with Android Oreo version #20
Comments
Please add a logcat trace of the app running on your device. |
Here is the logcat trace pixel.txt |
I don't see the application starting from this logcat.
|
It seems that the XML file parsed by the crawler ins't complete (missing the intent-filters). |
I might want to use a third party library to crawl AndroidManifest files such as APKParser. |
But the problem is with only Pixel devices running on Oreo, other devices which are running on Oreo display the list of codes available but on clicking them throws an error as |
Yeah, but I don't know why the parsing is no longer working. The issue with secret codes that are not working from the app (what you describe on your last coment) is already known but can't be fixed. Some OS are blocking such broadcasts to be sent:
|
((TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE)) |
I don't think this will work since this API call requires to have carrier privileges or to be the default dialer app. |
Dear SimonMarquis, 2019-03-15 18:17:24.415 1702-1797/system_process W/BroadcastQueue: Background execution not allowed: receiving Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://4636 flg=0x10 } to com.android.settings/.TestingSettingsBroadcastReceiver |
Uh oh!
There was an error while loading. Please reload this page.
I'm running the app on Pixel which is running on Android Oreo, App doesn't list any secret codes but some codes like ##225## is run on dialer app the codes run fine. Is there an issue with the app which runs on Oreo devices??
The text was updated successfully, but these errors were encountered: