Related
Is there a way to manually enable Auto-Rotate (via Terminal Emulator, etc). For some reason Droidsans isn't working right now. It gives me "Operation Failed" whenever I try to enable it, before and after a reboot.
I had to re-root my phone after I semi-bricked it yesterday.
|Spike|
AGx-07_162 said:
Is there a way to manually enable Auto-Rotate (via Terminal Emulator, etc). For some reason Droidsans isn't working right now. It gives me "Operation Failed" whenever I try to enable it, before and after a reboot.
I had to re-root my phone after I semi-bricked it yesterday.
|Spike|
Click to expand...
Click to collapse
Did you make sure you hit the Mount Read/Write button first?
1 - Mount Read/Write
2 - Disable auto-rotate
3 - restart g1
4 - Mount Read/Write
5 - enable auto-rotate
Trying that now.....
Edit: No good. Still gives me the operation failed..
|Spike|
i encountered that problem the when i first installed DroidSans
i disabled auto rotate on browser then tried to reboot then enable autorotate on DroidSans.
AGx-07_162 said:
Trying that now.....
Edit: No good. Still gives me the operation failed..
|Spike|
Click to expand...
Click to collapse
Everytime I enable auto-rotate it fails the first time I hit enable, but if u hit enable a second time then it should work then hit reboot. hope that helps.
Same thing happened to me. What works for me is to hit disable (even if it's disabled), then hit enable and reboot, works like a charm every time for me!
That usually happens to me, and that reminded me to turn Auto-Rotate back on. So, let's go about how I do it:
1) I open up DroidSans.
2) I check Auto-Rotate status. Current: Disabled.
3) I press "Enable Auto Rotate." Operation Failed
4) Okay, let's try "Disable Auto Rotate." Operation Completed; Please reboot your phone WTF?
5) Now let's try to enable it again. Operation Completed; Please reboot your phone Again, WTF?
6) Now I reboot just to see if it works. SUCCESS!
To disable Auto Rotation, just swap around "Enable" and "Disable" in the above tutorial.
Bah that's not working either. I know I'm rooted. I have themes, I use tether wifi, I can even use driodsans reboot feature. I don't get it. Does anyone know a command I can use to enable it?
|Spike|
blackknightavalon said:
That usually happens to me, and that reminded me to turn Auto-Rotate back on. So, let's go about how I do it:
1) I open up DroidSans.
2) I check Auto-Rotate status. Current: Disabled.
3) I press "Enable Auto Rotate." Operation Failed
4) Okay, let's try "Disable Auto Rotate." Operation Completed; Please reboot your phone WTF?
5) Now let's try to enable it again. Operation Completed; Please reboot your phone Again, WTF?
6) Now I reboot just to see if it works. SUCCESS!
To disable Auto Rotation, just swap around "Enable" and "Disable" in the above tutorial.
Click to expand...
Click to collapse
What I was trying to say is that you need to keep hitting Enable Auto-rotate till it says enabled... It takes me 2 times. DON"T HIT DISABLE unless auto rotate is on and u want it off and DON'T REBOOT till it says enabled.
Oh Yeah! I just remembered that There used to b two dif. copies of Driodsans on the market so if they still have two copies up try the other with the same steps. If that don't help. Then try re rooting your G1 maybe.
umm
the gallery application does not autorotate, does it?
Disable Operation Failed
On JF1.41 Rooted..
Having the opposite problem. I had used this to enable auto-rotate but it's annoying me by being too sensitive and switching back and forth when I don't want it to. I've tried to disable and it fails. I mounted R/W first, and still no success. But if I click Enable AR it works. I've tried rebooting, even got so annoyed with the Force Close error during phone calls, that I just did a wipe. I was surprised that did not kill the auto-rotate. So I re-downloaded Droid Sans 0.87 and it still won't allow me to disable the feature! Anyone have any ideas?
Thanks!
Just a simple thought. I had the same problem when I accidentally installed jf adp1 instead of jf33. There are two different versions of droidsans last I checked for the different versions. Might check to make sure you've got the right one.
The two different versions of Droid Sans are: Droid Sans Tweak Tools, which is for root users and includes remount r/w, autorotate, and reboot functions...the other is Droid Sans Tweak Tools LITE and it is for users WITHOUT root, no autorotate included...
I have an SGS3 with cm 10.2 and the secure settings has updated and uses the new system+ but I can't remove the helper. It gives me invalid configuration in the screen to install the system+. When I browse to the system/app folder I can't delete because of wrong permissions. When I try to change permissions on the folder it already has fuel permission for owner but I can't add write for the other options. I do have root access.
Anyone have any ideas?
Sent from my SCH-I535
I've got the exact same problem on my Nexus 4 with CM 10.2.
Edit: I just played around a bit and had the new version of System+ uninstalled.
I deactivated Secure Settings Helper in Android Settings -> Apps -> All. Tried to remove the securesettings.apk under system/app via terminal and adb without success. I deleted everything relating to secure settings using Titanium Backup. When I was unsuccessful, I opend up Tasker and unsurprisingly got a couple of Plugin Error messages.
Then I thought I might as well reactivate Secure Settings Helper again, so I did and also installed the new System+ Secure Settings app. For some reason via this app, I could now remove the helper granting root permissions again in the process and enable System+.
tl;dr: Try deactivating and reactivating Secure Settings Helper in Android Settings -> Apps -> All and then remove it via the new System+ Secure Settings app.
I have the same problem, also on a Nexus 4 but with stock KitKat. I have root, but I can't uninstall Secure Settings Helper either through the app or manually.
Mepsipax said:
I've got the exact same problem on my Nexus 4 with CM 10.2.
tl;dr: Try deactivating and reactivating Secure Settings Helper in Android Settings -> Apps -> All and then remove it via the new System+ Secure Settings app.
Click to expand...
Click to collapse
I'm not sure how this worked for you, because the System+ module supposedly can't be installed unless the Helper is gone. I did try uninstalling with TiBu, and it said it was successful, but I think that only removes updates to the Helper, and not the original apk.
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
floepie said:
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
Click to expand...
Click to collapse
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
clcdev said:
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
Click to expand...
Click to collapse
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
floepie said:
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
Click to expand...
Click to collapse
When I click that checkbox, I got the confirmation on the bottom that says Adaway was granted Superuser rights, but the box doesn't actually check, and nothing changes. Am I missing something stupid?
Go to setting in magisk and enable this module, restart, and then adaway should work.
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
wbgenetic said:
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
Click to expand...
Click to collapse
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Mother_Teresa said:
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Click to expand...
Click to collapse
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
airmark said:
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
Click to expand...
Click to collapse
Are you using the latest AdAway? Maybe you need to update the app itself.
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
hunfatal said:
Are you using the latest AdAway? Maybe you need to update the app itself.
Click to expand...
Click to collapse
Version 4.2.9. F-droid says it's the latest
wbgenetic said:
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
Click to expand...
Click to collapse
Yes, checks settings
So most ads get blocked but not all?
adaway forum to get latest version and gossip.
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
I stopped using adaway in favor of DNS66 for about two years now. Might be worth a shot if you're still having issues with Adaway
https://f-droid.org/en/packages/org.jak_linux.dns66/
HypromanGT said:
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
Click to expand...
Click to collapse
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
driss.sadok said:
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
Click to expand...
Click to collapse
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
smile20 said:
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
Click to expand...
Click to collapse
have you enabled systemless hosts in magisk?
gvsukids said:
have you enabled systemless hosts in magisk?
Click to expand...
Click to collapse
Yes, in magisk manager, restarted system, then installed adaway, gave permission to storage before first turn on, then checked systemless host setting in Adaway menu, but it was already on, downloaded sources, restarted system and now it supposed to wotk, but it doesn....There was just one reason i've rooted system, and it doesnt work...
Try enabling the hosts before installing adaway. Are you using the fdroid version?
gvsukids said:
Try enabling the hosts before installing adaway. Are you using the fdroid version?
Click to expand...
Click to collapse
This is how i've done . First enabled in magisk manager, then installed Adaway. I've downloaded direct Adaway apk from frdroid site.
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
LGZACRO said:
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
Click to expand...
Click to collapse
Just a issue that had developed while you was building your daily driver
Sent from my moto g(7) play using Tapatalk
PoochyX said:
Just a issue that had developed while you was building your daily driver
Click to expand...
Click to collapse
Any idea what might caused it? P.S., previously I have flashed the complete rom except userdata partition, and the issie was still there. Even if I disable all magic modules and xposed as well, the issue remain.
Has anyone faced something like that? Personally, I think some file is being overwritten after reboot and it might cause this issue. That's the only logical explanation I can figure out.
Hi!
Recently, I have been unable to open the Dreame Home App. My device has been rooted. When opening the application, an error message appears (presumably in Chinese) which says
"检测到该应用在root环境中运行".
All I can read is... "root"
With Magisk, I have ensured that the app no longer sees that the device is rooted. The app now opens initially without an error message. However, it closes automatically after a few seconds, without an error message.
Does anyone here have an idea what the cause might be and how I can get a handle on this problem?
[Mods: I have deleted my other post, please leave this here.]
The error message you mentioned, "检测到该应用在root环境中运行," translates to "Detected that the app is running in a root environment" in English. The Dreame Home App might be using advanced root detection methods that can bypass standard root-hiding techniques. It's possible that the app has implemented additional checks beyond just looking for the presence of root files or system modifications.
If possible, try disabling root access temporarily or unrooting your device entirely. This will help determine if the app's behavior is directly related to the root status. Also, you can try other root-hiding modules.
matthewJ32 said:
Also, you can try other root-hiding modules.
Click to expand...
Click to collapse
Thanks for your tips and ideas. Which other root hiding modules are you referring to?
niko26 said:
Thanks for your tips and ideas. Which other root hiding modules are you referring to?
Click to expand...
Click to collapse
I also used Magisk, but I know that there are modules like "Hide My Root" and "RootCloak". I can't guarantee success, but you can try.