Can someone help me with this error?
Overlay permission is already checked...
Code:
04-23 21:34:41.328 9075 9075 W GH.PermissionChecker: Overlay permission denied: android.view.WindowManager$BadTokenException: Unable to add window [email protected] -- permission denied for window type 2010
04-23 21:34:41.432 9075 9075 W GH.PermissionChecker: Overlay permission denied: android.view.WindowManager$BadTokenException: Unable to add window [email protected] -- permission denied for window type 2010
04-23 21:34:41.537 9075 9075 W GH.PermissionChecker: Overlay permission denied: android.view.WindowManager$BadTokenException: Unable to add window [email protected] -- permission denied for window type 2010
I'm encountering this problem too, on a Redmi Note 2. The Android Auto check won't see that I ticked the Overlay permission.
I know this thread is quite old, but I figured out that the issue is in the current Android Auto app.
AA tries the wrong method to request overlay permission.
That's because it checks the Android version in the ROM signature (ro.build.fingerprint).
Most of custom ROMs keep the original phone signature to preserve Android CTS although they upgrade the Android OS version.
As an example, for Redmi4X, the latest lineageos version available is 16.0 (Android 9), but the ROM signature inside is still "santoni-user 7.1.2 N2G47H V9.2.1.0.NAMCNEK release-keys".
AA catches "7.1.2" and believes it is on Android Nougat whereas the system is Pie.
Overlay permission request is different between Nougat and Pie, AA calls the wrong methods, leading to this "permission denied".
Workarounds are:
- change your /system/build.prop, changing ro.build.fingerprint to avoid the pattern "7.1.2", but you will loose CTS
- Use Magisk SafetyPatch v3 as proposed here (this modifies the fingerprint+security patch to a newer version, in order to keep CTS)
- spoof build fingerprint like done here , but for "com.google.android.projection.gearhead" (package name for AA).
Related
I've recently returned to work on an app I developed while ago (targeted then to 4.4). at the time I had a galaxy s2 for debugging and now I have s4 (i9500).
I tried to run the app while my phone connected and got installation failed. So I installed Android studio and imported (converted) and changed target to 5.0.1 (my phone's version).
When I hit run (or debug) I get this message:
HTML:
nstalling myapp.leff.app
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/myapp.leff.app"
Aborted
Launching application: myapp.leff.app/myapp.leff.app.myappAppActivity.
DEVICE SHELL COMMAND: am start -n "myapp.leff.app/myapp.leff.app.myappAppActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Aborted
filltering the log-cat (Android) i've noticed this lines:
HTML:
06-24 02:20:34.641 3269-3685/? D/SettingsProvider﹕ name = verifier_verify_adb_installs
06-24 02:21:30.331 3576-3576/? W/Settings﹕ Setting install_non_market_apps has moved from android.provider.Settings.Global to android.provider.Settings.Secure, returning read-only value.
06-24 02:21:30.426 3576-3576/? W/Settings﹕ Setting install_non_market_apps has moved from android.provider.Settings.Global to android.provider.Settings.Secure, returning read-only value.
06-24 02:21:46.231 9094-9094/? I/MultiDex﹕ install
06-24 02:21:46.261 9094-9094/? I/ProviderInstaller﹕ Insert disabled by gate 'gms:security:enable_conscrypt_in_gms_application'
06-24 02:21:49.656 3576-3576/? W/Settings﹕ Setting install_non_market_apps has moved from android.provider.Settings.Global to android.provider.Settings.Secure, returning read-only value.
06-24 02:21:49.716 3576-3576/? W/Settings﹕ Setting install_non_market_apps has moved from android.provider.Settings.Global to android.provider.Settings.Secure, returning read-only value.
06-24 02:22:00.016 3269-3269/? I/ActivityManager﹕ Killing 4849:com.samsung.android.app.filterinstaller/1000 (adj 15): empty for 1806s
I've re-installed new version of my custom rom - result is the same
I took another phone (samsung s5) and install was success. connected my s4 again. same error.
And ideas on how to resolve this?
note: usb-debugging is active
Hello,
Your project before conversion was built with Eclipse, if I understood it correctly? If so,
in Android Studio, the API targeting is not being read from the Android Manifest, but from the Gradle files.
In Android Studio, open (on your Project tree on the left), under the Gradle Scripts the build.gradle (Module: app) and check if inside the defaultConfig the targetSdkVersion has the correct API level. Then, press Build->Clean project from the menu bar on the top
If your application works with this String: INSTALL_NON_MARKET_APPS from the Settings.Global class , it is deprecated in API level 21, so use INSTALL_NON_MARKET_APPS from the Settings.Secure class instead. Check here.
I think it has to do with this class, the getString method with the above String that has been deprecated. I could help you further if I knew how is your app accessing this class or any code related to that
The S5 you tested has custom rom? Can you post the full logcat with the S4?
If you still need help, let me know
Hello again!
Tried launching supolicy --live as root in init context, it failed with code -13.
What gives? If I want to run supolicy --live very early in init, which context should I use ? Should I assume Zygote's context via seclabel ?
Hey, I hope I will not be comitting a gross transgression if I tag @Chainfire into this to hopefully draw attention.
Basically, what I'm trying to do is to patch Selinux policies and temporarily set Selinux to Permissive rather early during init sequence (after /system is available but before /data is properly available)
Supolicy --live says
supolicy v2.45 (ndk:arm64-v8a) - Copyright (C) 2014-2015 - Chainfire
Patching policy ...
- Failure! 13
Click to expand...
Click to collapse
What has gone wrong and how would I go about making it right ?
P.S.:
Do note that when the boot completes Supersu runs fine and Selinux can be switched to Permissive without issue (but it's too late at that point )
Android is Lollipop 5.0 and sources are not available for this specific ROM
Hello,
I tried on
supolicy v2.64 (ndk:armeabi-v7a)
same problem. Did you find a way to fix this issue ?
Error 13 is access denied. supolicy probably doesn't have the rights to read/write the sepolicy.
I have installed the latest Android Studio onto a new machine, and have installed Flutter plugin into the new installation. I then created a Flutter project, taking all the default settings.
After creating the project, I set up an emulator and tried to compile and run the flutter app. Unfortunately I get the following error:
Code:
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\Users\rbrown3\AndroidStudioProjects\flutter_app\android\build.gradle' line: 26
* What went wrong:
A problem occurred evaluating root project 'android'.
> A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
> Uninitialized object exists on backward branch 142
Exception Details:
Location:
com/android/build/gradle/internal/pipeline/VariantInfoImpl.<init>(Lcom/android/build/gradle/internal/scope/VariantScope;)V @200: goto
Reason:
Error exists in the bytecode
Bytecode:
...bytecode listing omitted for brevity...
Note that I also took a look at the build.gradle file that contained the offending line . Line 26 just contains:
Code:
project.evaluationDependsOn(':app')
I did not edit that line at all. In fact, I did not change anything, not even in the main.dart file.
Have I found a bug in the Flutter plugin? Or is it an Android Studio bug? Why does a pristine installation of Android Studio fail to compile default code due to a flaw in a gradle build file??? More importantly, what is the flaw causig these compilation failures and how do I fix it?
Installed BeyondROM a few days ago with the help of:
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
Click to expand...
Click to collapse
no boot issues, Magisk safety check cleared, TWRP working perfectly with no issues. but when i try to systemize a file trough adb shell or Terminux i run into this issue
C:\Users\Name\AppData\Local\Android\Sdk\platform-tools>adb shell
beyond1:/ $ su
beyond1:/ # systemize
==============================================
App Systemizer (Terminal Emulator) v17.3.1(70)
by veez21
==============================================
BusyBox v1.33.1-osm0sis
/system/bin/busybox
==============================================
Enter logs to upload logs
==============================================
Set SELinux Enabled: false
SELinux Status: Enforcing
==============================================
1 - Systemize Installed Apps (Listed)
2 - Systemize Installed Apps (Enter label)
3 - Systemize given APK
s - Set SELinux
0 - Exit
[CHOICE]: 1
Loading Apps [-]
==============================================
Installed Apps ===============================
==============================================
To systemize multiple apps, enter multiple number. Example: "1 0 0"
x - Back to Menu
r - Refresh list
0 - Exit
[CHOICE]:
Click to expand...
Click to collapse
Trying to move a app from standard install into app-priv, but with no success so far. i have tried to copy or move manually with TWRP file management but that just removes the app(files are there, but phone removes the install)
Tried option 2 with label but systemize cant find the Folder or the APK in the folder.
any help appreciated.
Hi,
I recently got a vivo x80 pro and managed to unlocked the BL, flash the boot.img using Magisk 25.2 and achieve some level of root.
but after failing to install LSposed, I looked at the complete logs and it shows that root has issues
Tried reinstalling and issues persist
this is a part of the log:
[ 5.690269][ T1] selinux: SELinux: Could not set context for /data/adb/modules: Permission denied
[ 5.691500][ T1] selinux: SELinux: Could not set context for /data/adb/modules/hosts: Permission denied
[ 5.691953][ T1] selinux: SELinux: Could not set context for /data/adb/modules/hosts/system: Permission denied
[ 5.692393][ T1] selinux: SELinux: Could not set context for /data/adb/modules/hosts/system/etc: Permission denied
[ 5.692606][ T1] selinux: SELinux: Could not set context for /data/adb/modules/hosts/system/etc/hosts: Permission denied
[ 5.692693][ T1] selinux: SELinux: Could not set context for /data/adb/modules/hosts/module.prop: Permission denied
[ 5.693002][ T1] selinux: SELinux: Could not set context for /data/adb/modules/safetynet-fix: Permission denied
[ 5.693395][ T1] selinux: SELinux: Could not set context for /data/adb/modules/safetynet-fix/system.prop: Permission denied
[ 5.693483][ T1] selinux: SELinux: Could not set context for /data/adb/modules/safetynet-fix/service.sh: Permission denied
I'm running Android 12 (OriginOS Ocean v12.0.13.5)
I also created this thread on the LSposed github: https://github.com/LSPosed/LSPosed/discussions/2089
thanks
even using the SElinux permissive module didn't fix the issue
modules like LSposed, JamesDSP are not working because of this
Any suggestions on how to debug / fix this?
Thanks
also tried the most recent canary 25.203 and same results
What boot.img did you use? I just unlocked my bootloader I have the global funtouch from Malaysia.
Also if I update to the beta will I lose bl unlock?
Hey,
I used the most recent boot.img for my w10
If you find the bookt.img for your beta version, then you can patch it
can you manually set context on these folders?
no
even the selinux module didn't help
still having a half rooted phone
I can explore / using total commander
some magisk modules work (safetynet fix, props config...)
but other won't work like LSposed
Washo4evr said:
no
even the selinux module didn't help
still having a half rooted phone
I can explore / using total commander
some magisk modules work (safetynet fix, props config...)
but other won't work like LSposed
Click to expand...
Click to collapse
edit build.prop
ro.debuggable=1