Hi everyone!
I've noticed a strange issue on my OP5. It seems to loose root privilege for certain apps:
- AdAway stops block ads after a while.
- Better Battery Stats is not able to load reference anymore while it was just working fine.
However other rooted apps like Kernel managers or Titanium Backup work just as expected. I'm using Magisk 13.3 and the manager shows that I'm still rooted. I'm running OOS 4.5.6 (but had the same issue on previous versions as well) by the way.
I do not have this issue on my N6P, might be OOS that blocks apps to interfere at system level?
Thanks!
This isn't an issue with root.
- Adaway: ads are blocked when on Wi-Fi but not on data so I checked my APN settings and removed my carrier proxy. Solved.
- Better Battery Stats: not 100% sure but I think it's blocked by doze.
Related
Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?
Delete OTACERTS.zip in system/etc/security. You must enable r/w and have root.
When I did It, it downloaded the update in front of me but didn't update. Then I deleted the update. Now i'm still on 6.2.1 and Loving It.
Molinari said:
Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?
Click to expand...
Click to collapse
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.
mark_a_l said:
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.
Click to expand...
Click to collapse
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.
iroctheworld said:
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.
Click to expand...
Click to collapse
What were you blocking? I've only got about 6 things on my white list (not blocked). Half are market related. In any case even if it doesn't work for OTA updates, I find some apps to be a bit too 'chatty' (looking at the logs). So it does work at blocking 'unnecessary' wifi traffic.
Thanks for the rename tip!
I am still avoiding the 6.2.2 update (only time can tell, last time mine was updated about 1 week after the first posting about forced updates ...)
I am running the rooted version of 6.2.1. I flashed this after losing root from the 6.2.1 forced update.
This time I only did two "mods" for protection -
(1) un-register from Amazon (actually I never register during ROM installation)
(2) use Droidwall
I dunno which one will make me survive the forced update, but I suspect it may / will be #(1).
I only allow a few things to go through Droidwall, most of them are 3rd party apps' names. The only two additional processes necessary for normal functions are:
(1) downloads, media storage, DRM protected content storage, download manager (needed for Market downloads)
(2) search (for Google search)
The one I always worry about in Droidwall is obviously #(1). I certainly do not let things like Amazon device client platform (ADCP) to go through!
This is just my Droidwall setup. People using other apps may need to allow other Android processes through therefore I cannot guarantee Amazon update won't sneak through that way.
I only know about the otacerts.zip when I revisited the forum yesterday afte reading elsewhere about the new OTA update. This time I won't modify this file on purpose.
(fingers crossed for me, I am not out of the woods yet)
P.S. Feb 2nd and I am still clean, looks like I dodged it!
I created a Moto Mod Battery Service App that Implements the Efficiency Mode and Moto Mod battery status. It is also opensource.
This is much more efficient than the Automate way of doing this. Automate had to loop and keep waking up the device.
This service only does stuff if the battery tells it something has changed and if a charger has been plugged in or unplugged.
Release Info:
Moto Mod Battery service for LineageOS 15.1
Version 1.0.1
Fixed charge bug, where charging would not stop after charging over night
Change High Trigger wording
Version 1.0
Features:
Status Notification:
Displays Moto Mod battery capacity in %
Displays Moto Mod battery status
Icon: Shows capacity and short form of status
Efficiency Mode:
The ability to turn on and off efficiency mode
The ability to set when efficiency mode will trigger
The ability to set when to stop charging once the efficiency mode has been trigger
Self Start:
If running and package is reinstalled restart self
If Moto Mod battery has been ran once then on boot start up service
https://github.com/devilsclaw/MotoModBattery/releases/
Updated to Version 1.0.1
Thanks a lot. I've been using your APP with LineageOS for a few days and it seems to work pretty good. Great job. :good:
Can i ask you a few questions?
First of all. Why isn't this great APP integrated into the Lineage OS ROM?
Does the APP need root access all the time or just to change the settings? Each time the APP requests root access, an icon (#) is shown in the "status bar". Sometimes this happens about 50 times in a row. The symbol (#) then flickers constantly. Is that normal? Is it perhaps better to install the APP as a system APP?
One thing, but that has nothing to do with your APP. Every time I reboot the Moto Z with the Power Pack installed, the phone thinks the external battery is the internal battery. Do you understand what I mean? No internal battery. Only a reboot without Power Pack fixes the problem. Is it maybe possible to fix this with your APP or more a LineageOS problem?
Sorry for my bad English. I am not a native speaker. Just school englisch.
I for one do not know why a similar app is not built into the stock linage rom.
After a certain version of android apps started requiring root access for certain battery status info. also to make any modifications to the power pack settings require root. I personally turned off the root icon indicator for the reason you mentioned above.
I custom built my ROM and added a toggle switch for the SU root indicator and turned it off. there is a file that can be manually edited that can turn it off also, but I forget what file that is.
This works only in lineage os? Or works in any other rom?
If other ROMs have support to the moto mods and have the same directory paths as linage for accessing there settings then it should work.
It should also work with newer versions of linage. unknown about older versions.
chuletaz024 said:
This works only in lineage os? Or works in any other rom?
Click to expand...
Click to collapse
I forgot to mention i use LineageOS 16.
Thank you for your reply. I don't know if I want to deactivate the icon. I like to see if an App uses root but I think about it.
Yesterday I made a test and put your App in the system/app/ directory. In this case it turns into a System App. Right? I thought System Apps don't need root access because they are System Apps and system Apps have root anyway. I was wrong. My knowledge is to little .
But I have discovered some strange behavior. After changing your App into a System-App I could choose the "efficiency mode" in the original MotoMod App and I think there was more. I didn't tested it and now I'm a little bit annoyed about me, because the only thing i wanted yesterday was no root Icon and that didn't worked out. The rest I didn't care .
As a System App I had then problems to remove it. After deleting the directory in the system/app/ folder the Moto Z didn't recognized the PowerPack any more. I had to make a factory reset. My fault :crying:.
Is there a way to install it as a System App without the App asking for root? I want to integrate it in the LineageOS System.
Sorry for my ignorance/inexperience.
A system app can access certain information without root, but the app has to read and write to the /sys/kernel/debug sub system, the battery section does not need root but the moto mod section does, because the developers for the moto mod driver set the permission as such to require it. I made the app so that it would not need a custom linage build of the ROM with the permissions fixed.
I did make the program open source so you or anyone could modify it to not require root. I might have time to do it my self if it is possible as a system app to do.
Not sure if it's just me but the moto mod battery is charging phone no matter what setting... It's weird since even I turned off charge phone option in the original moto mod app in the lingeaos. It's still charging the phone ... It could be the system issue. I don't know. Any help is appreciated. Thanks!
Works really well for Moto Z Los 16. Thanks for the app.
No working
Not working efficiency mode in moto z2 force with lineageos 17.1 any solution?
I have been using this service installed on
lineage-15.1-20200211-UNOFFICIAL-albus.zip
lineage-17.1-20210224-UNOFFICIAL-albus.zip
with Magisk. The service runs fine on my on both ROMs.
However, since I used Magisk to give root access to the service, I now get a pop-up "Modo Mod Battery was granted Superused rights" every 60 second (I counted the interval) on the screen which is a bit annoying. I guess the service is called every 60 sec or so, and thus the root access is given every time?
Since the pop-up is from Magisk granting the Battery Mod Service the root access, I have just turned of all the notifications from the Magisk App, which works fine but maybe not the optimal way.
Any take on this?
Hi,
Since I updated my device to Pie, I have problems with some apps (for example the game HearthStone or my Home Camera Application)
It looks like these apps does'nt work when they need background data update.
Does anyone had the same problem ?
Of course the Data Saver is disabled and I tried to enable it but disable just for these applications : no change.
All Google applications are NOT concerned by this problem.
Thanks for reply.
Move to custom ROM . Stock pie ROM is buggy.
I am on my second V20, H990DS this time and I am running Superv20 which I have been using the past few days and is a dream, bar these issues I have run into which seem to be related to each other.
I have been unable to get youtube vanced to install on this V20, and it returns with
'Installation failed for unkown reasons'
then in advanced
'java.io.FileNotFoundException: No such file or directory'
I was also restoring a backup with Titanium Backup from my other phone to get around snapchats root detection as magisk hide did not work. On restoring the app+data I am hit with a generic 'App not installed.' message, and then titanium hangs on the screen indefinitely until rebooting the phone (did manage to restore just Data after installing stock snapchat).
Then I remembered the first few times I attempted to setup the phone and update magisk and magisk manager. After updating magisk, the next time the phone was booted I got a simple grey background and small white writing filling half the screen with the first line stating something similar to
'Crash on the LK!' (might not be exact, didn't have my other phone to take a photo) and I had to reinstall the rom. I did this twice to test just in case it was a random issue.
My assumption is that it is related to storage somehow and I did manage to find one thread with a similar issue so I checked if internal was not the default install location, but pm get-install-location returns with
1[internal]
but also I have tried setting the storage to auto and external and neither worked (for vanced at least)
Unsure what to try next as my troubleshooting and searching for similar issues has run dry.
Help much appreciated and thanks in advance <3
-A9
Hello.
I just updated my rooted S10+ to One UI 4. Of course, everything is not working as it should, as Samsung limits feature access to rooted devices. I have installed latest Magisk (24.1), bluetooth library patch (2.4.0 by 3arthur6, whit additional steps) and universal safetynet fix (2.2.1), that passes. As I was testing all my apps, as always, I have issues whit shealth. When I open app it opens and shows my stats, but if I try to enter any menu or tab app closes whit error as in picture below. It there a way to get shealt to work?
And what else I am missing from fixes?