To all KITKAT ROM USERS having problems in installing apps from play store:
If you have tried to install an app and got an error message: COULDN'T INSTALL IN USB STORAGE OR SD CARD,
1. DOWNLOAD and INSTALL SELINUX MODE CHANGER from play store. (Make sure that you have supersu installed and your phone rooted obviously). Grant permission access to SELinux mode changer when supersu prompts you.
2. OPEN SELINUX MODE CHANGER AND CHANGE SELINUX permission to PERMISSIVE.
3. INSTALL THE APP which you wanted for your phone.
Enjoy.
N.B. You can change the permission to ENFORCING after installing the app you wanted.
Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD
This is also how to get Cydia Substrate working on 4.4
Sent from my GT-I9100G using Tapatalk 4
ottomatteseo said:
Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Hi ottomatteseo. Did it work?
Omni rom don't have selinux
so how i install the app?
Fighting Dreamer said:
Omni rom don't have selinux
so how i install the app?
Click to expand...
Click to collapse
HI Fighting Dreamer. Omnirom has SELinux. But its mode in Android 4.4 is set to ENFORCING by default. I suspect that this is one of the reasons why we get the error message upon installing some apps which worked for previous android versions and rom.
Anyway, just download SELinux mode changer from playstore and follow the above instructions then install the app which gave you the error message. Update me if it worked for you. Good luck
rarjonillo said:
Hi ottomatteseo. Did it work?
Click to expand...
Click to collapse
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD
ottomatteseo said:
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Glad it worked for you.:good:
worked
thanks
alkasser011 said:
worked
thanks
Click to expand...
Click to collapse
Great.
This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.
Mll4eveR. said:
This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.
Click to expand...
Click to collapse
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.
rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I just flashed 4.4 and set SE Linux mode in "permissive" and updated to 4.4.1. The mode appeared to be "permissive" indeed in 4.4.1 but somehow the "couldn't install app in usb and sd card" error persisted.
I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18
Mll4eveR. said:
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.
Click to expand...
Click to collapse
colorprint said:
I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18
Click to expand...
Click to collapse
I think it's high time to report this to ryuinferno and jiangyi (developers of the CM11 and omni roms respectively).It may be caused by either the rom or still the specific app since there are some which are still not working with the 4.4 structure http://forums.androidcentral.com/google-nexus-5/331321-apps-do-not-work-currently-n5-4-4-a.html.
I'll report this. Thanks!
This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...
colorprint said:
This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...
Click to expand...
Click to collapse
Please see this. https://www.xda-developers.com/android/android-4-4-kitkats-art-and-app-compatibility/. Thanks.
Related
Hi,
Anyone here noticed if the StickMount is stopped working after the update to JB 4.2? I have tried other mount apps but they all seems to be not working.
They mount the drive alright but the folder is empty. Anything to do with folder structure changed in JB 4.2?
Thanks
http://forum.xda-developers.com/showpost.php?p=34054744&postcount=182
Seems your not the only one.
PS - Did you update OTA or manually? THanks
Same here, Stickmount is not working, it will monut the mass storage but will only show an empty folder in any file explorer. Nexus Media Importer from the Play Store is working well.
dnsp said:
Same here, Stickmount is not working, it will monut the mass storage but will only show an empty folder in any file explorer. Nexus Media Importer from the Play Store is working well.
Click to expand...
Click to collapse
I can't test it right now, but can you verify you still have root after the upgrade? I just found out I lost mine and had to re-root. That could be the reason why it doesn't work.
Chainfire owns a Nexus 7 too. He will fix it soon, I would say.
Im leaning towards the fact its probably the root permissions you described.
As this happened to me when going to 4.1.2
So try to re-root and report back !
rtiangha said:
I can't test it right now, but can you verify you still have root after the upgrade? I just found out I lost mine and had to re-root. That could be the reason why it doesn't work.
Click to expand...
Click to collapse
Yes, rooted with superSU prompt kicking. I also had to re-root after the update.
i Have Root.But StickMount stopped Working.Lets wait..Chainfire will fix it soon hopefully.
Not working here too, did clean install and flashed everything again.
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
I don't think so. I believe it's related to the multiuser feature and the new mount points for /sdcard.
Sent from my Nexus 7 using xda app-developers app
That's my take as well. The new virtual directory structure is mucking things up.
drx69 said:
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
Click to expand...
Click to collapse
You are wrong
Other Chainfire app says everything has full support.
https://www.dropbox.com/s/zp55xc94gngzz8q/2012-11-13 20.45.58.png
drx69 said:
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
Click to expand...
Click to collapse
Unfortunately you would be incorrect. I've been using StickMount for USB-OTG on 100% stock rooted 4.1.2 for a while. Sucks it's broke in 4.2 currently but it just came out and I know chainfire will fix it up soon.
yaderly DKC
It's probably due to the new multiuser feature.
I manually mounted an usb flash drive to /mnt/shell/emulated/0/usbdrive.
Now "ls /mnt/shell/emulated/0/usbstick" shows it's content but not for the associated /storage/emulated/0/usbdrive.
So the new multiuser stuff makes the files "invisible" even if the usb flash drive is correctly mounted and can be accessed by root.
any udizes
Wilks3y said:
http://forum.xda-developers.com/showpost.php?p=34054744&postcount=182
Seems your not the only one.
PS - Did you update OTA or manually? THanks
Click to expand...
Click to collapse
Thanks. I updated manually.
StickMount
Updated manually, rooted and SuperSU installed, both Stickmount and USB OTG Helper display display empty folders.
Nexus Media Importer works fine, looks like I'll have to use this until Chainfire gets around to fixing up Stickmount.
i see chainfire has updated SuperSU i was wondering if anyone with 4.2 has any idea if this has helped Stickmount?
Herkfrog said:
i see chainfire has updated SuperSU i was wondering if anyone with 4.2 has any idea if this has helped Stickmount?
Click to expand...
Click to collapse
No the update just delt with apps that require root on the multi user profiles.
Sent from my Nexus 7 using xda app-developers app
pknall said:
Updated manually, rooted and SuperSU installed, both Stickmount and USB OTG Helper display display empty folders.
Nexus Media Importer works fine, looks like I'll have to use this until Chainfire gets around to fixing up Stickmount.
Click to expand...
Click to collapse
I am the "developer" of USB OTG Helper. Please could you be kind enough to try this version and confirm if this works -> http://www.mediafire.com/?wlt084peiksjb1l
The drive(s) are not mounted on sdcard but on /USB-OTG-Drives root folder.
The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
What this app does? How did you find it?
and after put in system/bin what to do next? how to run it?
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
I use SManager , give to scrfix su and boot privs it will work?
I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.
There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.
I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.
Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.
amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.
amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs
I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.
I'm just creating this so that it'll be easy for everyone to post about the functionality of the awesome viper4android
I used it with SELinux mode changer and it worked. But is there like a more simple way to install and make the app work.
Any suggestions and workarounds?
Sent from my E6533 using XDA-Developers mobile app
from my side, am using androkernel v31, i had a problem when installing drivers for viper, it says installed but when phone is restarted, it asks to instal driver again.
fix: setting>app>viper4android, allow storage in permission
zemetal said:
from my side, am using androkernel v31, i had a problem when installing drivers for viper, it says installed but when phone is restarted, it asks to instal driver again.
fix: setting>app>viper4android, allow storage in permission
Click to expand...
Click to collapse
Hmmm, I had the same problem but soon as I set SELinux to permissive it worked.
njaya95 said:
Hmmm, I had the same problem but soon as I set SELinux to permissive it worked.
Click to expand...
Click to collapse
on mine, SELinux was already on permissive.
I'm on magisk 15.1. Almost modules that have been downloaded from repo can't be installed.
Check attached log for sure.
@topjohnwu
exodius48 said:
I'm on magisk 15.1. Almost modules that have been downloaded from repo can't be installed.
Check attached log for sure.
@topjohnwu
Click to expand...
Click to collapse
Since the DNS module has a different error than the others in the install log, could you post recovery logs for the other modules as well?
Edit: I forgot: your Magisk log as well, please.
Didgeridoohan said:
,..could you post recovery logs for the other modules as well?
Click to expand...
Click to collapse
Its ok if i install from recovery
Didgeridoohan said:
Edit: I forgot: your Magisk log as well, please.
Click to expand...
Click to collapse
I already attached magisk log from installed module above
exodius48 said:
Its ok if i install from recovery
Click to expand...
Click to collapse
Thank you, that confirms a suspicion...
I already attached magisk log from installed module above
Click to expand...
Click to collapse
No, you didn't. Those are the install logs. I asked for the Magisk log (or if you're using the beta release of v15.1 the magisk_debug.log would be even better).
Didgeridoohan said:
No, you didn't. Those are the install logs. I asked for the Magisk log (or if you're using the beta release of v15.1 the magisk_debug.log would be even better).
Click to expand...
Click to collapse
Check attached file. I'm using 15.1 stable.
Yesterday i used magisk on android 7.1.2 , now updated to 8.1.0 and i get same error.
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
chazarss said:
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
Click to expand...
Click to collapse
That's interesting. What device do you have? I do not have a installation permission on any of my devices...
chazarss said:
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
Click to expand...
Click to collapse
Did you mean storage permission? It already granted on my device.
exodius48 said:
Did you mean storage permission? It already granted on my device.
Click to expand...
Click to collapse
Had same issue .... uninstall magisk from recovery, then install magisk 14 and install any module (Viper4Android for e.g.) it should install properly and then update to 15.1 . all modules will work from then on.
andromodgod said:
Had same issue .... uninstall magisk from recovery, then install magisk 14 and install any module (Viper4Android for e.g.) it should install properly and then update to 15.1 . all modules will work from then on.
Click to expand...
Click to collapse
If so, the issue is from magisk 15.1 i think
exodius48 said:
If so, the issue is from magisk 15.1 i think
Click to expand...
Click to collapse
not really. i mean my device is qmobile Noir E2 (Chinese Phone Rebrand) and its operating system is from the Panasonic Eluga A3, which i modified to not encrypt internal storage and such. so it might be a problem with generic devices and not with magisk.
Didgeridoohan said:
That's interesting. What device do you have? I do not have a installation permission on any of my devices...
Click to expand...
Click to collapse
@exodius48
I have OnePlus 5 - On android Oreo it asks spesific permission for apps to install mods or apks
Use these kw to search on settings`Install unknown apps`
chazarss said:
@exodius48
I have OnePlus 5 - On android Oreo it asks spesific permission for apps to install mods or apks
Use these kw to search on settings`Install unknown apps`
Click to expand...
Click to collapse
Ah... Then I understand. That has nothing to do with the Managers ability to install modules only with it's built-in update feature. And there's no need to manually enable it. If an app needs that permission, you'll get a message that it needs to be activated.
Didgeridoohan said:
Ah... Then I understand. That has nothing to do with the Managers ability to install modules only with it's built-in update feature. And there's no need to manually enable it. If an app needs that permission, you'll get a message that it needs to be activated.
Click to expand...
Click to collapse
No it doesn`t show message, i just found it by mistaken then enabled and all problem solved, till then i have searched so much on internet
chazarss said:
No it doesn`t show message, i just found it by mistaken then enabled and all problem solved, till then i have searched so much on internet
Click to expand...
Click to collapse
Hm... It's not supposed to show a message when installing modules though, only when updating the Manager or otherwise installing an apk manually.
I find it interesting that installing modules wouldn't work unless you enable that option... Could you record a logcat when install a module with the setting off and then when it's on?
Didgeridoohan said:
Hm... It's not supposed to show a message when installing modules though, only when updating the Manager or otherwise installing an apk manually.
I find it interesting that installing modules wouldn't work unless you enable that option... Could you record a logcat when install a module with the setting off and then when it's on?
Click to expand...
Click to collapse
sorry it was like nightmare so i just dont want to risk it and break anything again. but i remember that everytime i tried to install any mod, magisk fails and says "Unable to extract zip", it is kinda phone doesnt let it to use storage and make installation, but after gave the permission everything solved.
Edit. Ss attached from my setting