[APP][TOOL] TeMeFI comprehensive system Administration

[DiamondJohn]

Maybe, we are talking apples and oranges.
-- I was referring to the fact if Google Play Services [not Google Play Store] has a tendency to reset device_idle_constants after rebooting.

Because I have not had my Doze reset (except read below) on my phones daily, I don't think its a thing. Including on my Pixel 4a running stock ROMs for almost 2 years. That google phone should of been pretty close to ASOP and of course running the latest Play Services. If anything, I think google would of been over-reaching in their treatment of "their devices".

The exception to the above, is that a few months ago I switched to a heavily modified custom ROM (Bliss A11) which has MANY battery optimisation's. One of the things it appears to do in its optimisation's, is reset my doze settings, which blows away my custom doze. ie its not the play services but the ROM. The more I think of play services modding doze (beyond a wake-lock or whitelisting) on a device., the more it sounds like an overreach.

EDIT: PS its not just Vending that is whitelisted.

 

[KitsuneFoxy]

Anything I do i get this error. I m rooted and on marshmallow 6.0.1. with magisk. nothing is being actually denied to it writing or reading. But then it crashes. I can't upload any logs because it gives the same error.

 

[DiamondJohn]

Anything I do i get this error. I m rooted and on marshmallow 6.0.1. with magisk. nothing is being actually denied to it writing or reading. But then it crashes. I can't upload any logs because it gives the same error.

Connect to the phone via ADB (or you could do it in a rooted terminal on the device)

adb connect ?????
adb shell

run the following in the shell

su;
    
echo "1" > /sdcard/TeMeFI/.config/LOG_INF_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_WRN_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_TRC_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_DBG_ON;

logcat -c;
am start -n diamondjohndroid.utility.temefi/.main

From what you are saying, This should start temefi, and trigger the error
Go to the UI and click "NO"
In the adb shell, run the following

logcat -d > /sdcard/$(date +"%Y%m%d%H%M%S")_logcat.log; logcat -c;

rm /sdcard/TeMeFI/.config/LOG_INF_ON;
rm /sdcard/TeMeFI/.config/LOG_WRN_ON;
rm /sdcard/TeMeFI/.config/LOG_TRC_ON;
rm /sdcard/TeMeFI/.config/LOG_DBG_ON;

Copy and zip up the file /sdcard/202210DDMMHHSS_logcat.log and post it to me as an attachment in a PM to me.

It may also help to get the output from:
ls -l /data/user/0/diamondjohndroid.utility.temefi/cache/* > /sdcard/$(date +"%Y%m%d%H%M%S")_cachecontents.log

 

[DiamondJohn]

Is there a very to block sensor wakelock or change their wakeup settings?

Sir one help device dozing properly but motion sensor keeps on breaking deep idle mode very often anyway to disable significant motion detector! I believe thts the culprit. Iam on a12 custom rom aosp based

And anyone else interested in blocking sensors during doze, I just randomly came across the following, but have not tested it myself.

dumpsys sensorservice restrict <SENSOR_WHITELIST_PACKAGE>;
dumpsys sensorservice enable;

Seems a mismatch, that you disable by a single package, but then re-enable all.

Info on sernsor service from TeMeFI Current State>Dumpsys>sensorservice which I *think* calls dumpsys sensorservice;

also a little more left field (ie no doc / or didnt take any time to check)

dumpsys sensorservice data_injection <PACKAGE_ID>;

I Have NO IDEA what data_inject does, possibly as a guess, trigger the sensor via code/shell IDK.

 

[DiamondJohn]

Something I accidently came across recently further regarding "sensors". I am testing the next release by running as many methods as possible.

Under the Battery History Extras Graphs, it will actually plot "sensors". I am guessing its a flag showing something was triggered.

 

[ogmexicanfoo]

Hi, I installed the latest APK (as of 10/30/22). When the app was first installed I was able to find the menu to detach apps, as well as other options on the main menu. I detached Youtube and Youtube Music, restarted and it worked. Problem is that now when I launch the app I can't find nothing related to detaching, or any of the previous options shown on the main menu. After looking around XDA, Google and in the app itself I can't find why the options went away. The app doesn't even mention anything about it. I'm running Oxygen OS based off Android 12 on a One Plus 8 Pro with the latest Magisk (as of 10/30/22). Busybox and Toybox is installed via Magisk, LSposed running too but I believe it is unrelated. Thanks!

 

[DiamondJohn]

Hi, I installed the latest APK (as of 10/30/22). When the app was first installed I was able to find the menu to detach apps, as well as other options on the main menu. I detached Youtube and Youtube Music, restarted and it worked. Problem is that now when I launch the app I can't find nothing related to detaching, or any of the previous options shown on the main menu. After looking around XDA, Google and in the app itself I can't find why the options went away. The app doesn't even mention anything about it. I'm running Oxygen OS based off Android 12 on a One Plus 8 Pro with the latest Magisk (as of 10/30/22). Busybox and Toybox is installed via Magisk, LSposed running too but I believe it is unrelated. Thanks!

The only check I do to show or hide that menu item, is a root check. Check that the app still has root and its being logged as being granted root. You should see a toast telling you it was granted root.

 

[DiamondJohn]

...snip... latest Magisk (as of 10/30/22) ...snip...

the "latest magisk" is NOT stable Magisk,

 

[thunderteaser]

I am getting a similar crash whenever it tries to build a menu. This started happening after upgrading to Magisk v25 from v23. I have followed your instruction on collecting some logs, so I'm sending those to you if you don't mind having a look.

Connect to the phone via ADB (or you could do it in a rooted terminal on the device)

adb connect ?????
adb shell

run the following in the shell

su;
  
echo "1" > /sdcard/TeMeFI/.config/LOG_INF_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_WRN_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_TRC_ON;
echo "1" > /sdcard/TeMeFI/.config/LOG_DBG_ON;

logcat -c;
am start -n diamondjohndroid.utility.temefi/.main

From what you are saying, This should start temefi, and trigger the error
Go to the UI and click "NO"
In the adb shell, run the following

logcat -d > /sdcard/$(date +"%Y%m%d%H%M%S")_logcat.log; logcat -c;

rm /sdcard/TeMeFI/.config/LOG_INF_ON;
rm /sdcard/TeMeFI/.config/LOG_WRN_ON;
rm /sdcard/TeMeFI/.config/LOG_TRC_ON;
rm /sdcard/TeMeFI/.config/LOG_DBG_ON;

Copy and zip up the file /sdcard/202210DDMMHHSS_logcat.log and post it to me as an attachment in a PM to me.

It may also help to get the output from:
ls -l /data/user/0/diamondjohndroid.utility.temefi/cache/* > /sdcard/$(date +"%Y%m%d%H%M%S")_cachecontents.log

 

[DiamondJohn]

I am getting a similar crash whenever it tries to build a menu. This started happening after upgrading to Magisk v25 from v23. I have followed your instruction on collecting some logs, so I'm sending those to you if you don't mind having a look.

...snip...

I ONLY build & test against STABLE Magisk. As soon YOU install BETAS of anything, especially something as core as your root, YOU accept that you are running software that by definition has bugs, which could break other or even all your root apps.

A few years ago I had a similar issue with people wanting me to "fix" TeMeFI as it wasnt working against the latest Beta at that time. I gave the same response back then, and a few days later, a new Beta was released, that fixed the bug in Magisk.

Wait a sec, you "upgraded" from v25 to v23? isnt that a downgrade? I am running 25.2. To be honest, I haven't checked if that is still the latest stable for a while.

I also note the Bomb icon in the top right, of your screenshot. have you check what that error is? NO error should be reported without checking that first. And please, do not attach it as a screenshot. It may give a better idea of what has actually gone wrong.

PS: please use thumbnails when including screenshots in this thread. You can edit your post to switch it back.

 

[thunderteaser]

I ONLY build & test against STABLE Magisk. As soon YOU install BETAS of anything, especially something as core as your root, YOU accept that you are running software that by definition has bugs, which could break other or even all your root apps.

Yes, I'm running the latest stable Magisk release, which is v25.2.

Wait a sec, you "upgraded" from v25 to v23? isnt that a downgrade? I am running 25.2. To be honest, I haven't checked if that is still the latest stable for a while.

Nope, I said "to v25 from v23", it means it was working fine with v23, but as soon as I upgraded to v25.2 I had this weird exception.

I also note the Bomb icon in the top right, of your screenshot. have you check what that error is? NO error should be reported without checking that first.

That bomb icon just reloads the top navbar buttons. It appeared as I took that screenshot but can't seem to make it appear any longer. I just get the DataSourceFD exception

And please, do not attach it as a screenshot. It may give a better idea of what has actually gone wrong.

PS: please use thumbnails when including screenshots in this thread. You can edit your post to switch it back.

Sorry, I posted from my phone, fixed that.

By the way, I'm not expecting you to look into anything. I just politely asked if you minded having a look at my logs to tell me what's going on. If you don't have time or don't want to, I fully understand and thank you anyways for answering me back. I have this weird feeling that it's actually my phone itself telling me to please just let it die as it is behaving rather strangely from a month or so. It might not be TeMeFi nor Magisk at all, it's what i'm saying.

BTW it's a Redmi Note 7 (lavender) running on a stock ROM based on Android 9.

 

[DiamondJohn]

Yes, I'm running the latest stable Magisk release, which is v25.2.
...snip...
Nope, I said "to v25 from v23", it means it was working fine with v23, but as soon as I upgraded to v25.2 I had this weird exception.

Sorry, my bad, just saw the ver change on second reading, without seeing it was "from" and assumed X TO Y

That bomb icon just reloads the top navbar buttons.

No it should not, unless you have another issue as well. The bomb icon shows the details of the last error and or warnings encountered within a TeMeFI script (which includes filling the menu items). ie it may actually be the details to help to determine your specific issue. A click displays the error; which can be saved off and attached to this thread. ie not a screenshot. A long press clears the warning / error. as the error stays until. a new error/warning is encountered.

By the way, I'm not expecting you to look into anything. I just politely asked if you minded having a look at my logs to tell me what's going on. If you don't have time or don't want to, I fully understand and thank you anyways for answering me back. I have this weird feeling that it's actually my phone itself telling me to please just let it die as it is behaving rather strangely from a month or so. It might not be TeMeFi nor Magisk at all, it's what i'm saying.

BTW it's a Redmi Note 7 (lavender) running on a stock ROM based on Android 9.

I have TeMeFI running both A8 and A11. Its good to report errors/issues. It just would be easier with the correct logs to help both of us.


Without any further details, try running each of the following in a non-rooted terminal shell or over ADB.

su -c 'ls /data/data 2>/dev/null';

su -c busybox --list 2>/dev/null;

su -c 'ls /data/user_de/0/com.topjohnwu.magisk/databases/sulogs.db 2>/dev/null

PS: Thanks for switching the image

 

[thunderteaser]

No it should not, unless you have another issue as well. The bomb icon shows the details of the last error and or warnings encountered within a TeMeFI script (which includes filling the menu items). ie it may actually be the details to help to determine your specific issue. A click displays the error; which can be saved off and attached to this thread. ie not a screenshot. A long press clears the warning / error. as the error stays until. a new error/warning is encountered.

That's too bad I couldn't get any more info. Any animation basically triggers another error and I have to tap "Yes" all the time, so I can barely navigate the app. I can click on a menu and go down a level, but then it says "please wait until the menu finishes building" on anything I try to access.

Without any further details, try running each of the following in a non-rooted terminal shell or over ADB.

su -c 'ls /data/data 2>/dev/null';

su -c busybox --list 2>/dev/null;

I attached these logs to the post.

su -c 'ls /data/user_de/0/com.topjohnwu.magisk/databases/sulogs.db 2>/dev/null

This outputs 1.
EDIT: I just remembered I hid magisk app, so changed the path to reflect the hidden package name and it outputs the path to sulogs.db. Is this to be expected? If you meant to let me collect Magisk logs I could find another way

Oh, and thanks for helping, I do really appreciate it.

 

[DiamondJohn]

That's too bad I couldn't get any more info. Any animation basically triggers another error and I have to tap "Yes" all the time, so I can barely navigate the app. I can click on a menu and go down a level, but then it says "please wait until the menu finishes building" on anything I try to access.

A "backdoor" method, while the message is still displayed in TeMeFI and then again after clicking the OK button is to run the following in a rooted terminal shell:
cat /data/data/diamondjohndroid.utility.temefi/cache/TeMeFI_error.log" > /sdcard/$(date +"%Y%m%d%H%M%S")_temefierrorlog.log;
but probably best to clear it before running the above. ie: rm /data/data/diamondjohndroid.utility.temefi/cache/TeMeFI_error.log;

This will create a copy of the file in the root of your SDCard.

Also, in a rooted shell,
logcat -d > /sdcard/$(date +"%Y%m%d%H%M%S")_logcat.log;

Are you telling me you had NO output from the third command? On review, I should of excluded the "2>/dev/null"

 

[thunderteaser]

A "backdoor" method, while the message is still displayed in TeMeFI and then again after clicking the OK button is to run the following in a rooted terminal shell:
cat /data/data/diamondjohndroid.utility.temefi/cache/TeMeFI_error.log" > /sdcard/$(date +"%Y%m%d%H%M%S")_temefierrorlog.log;
but probably best to clear it before running the above. ie: rm /data/data/diamondjohndroid.utility.temefi/cache/TeMeFI_error.log;

This will create a copy of the file in the root of your SDCard.

Also, in a rooted shell,
logcat -d > /sdcard/$(date +"%Y%m%d%H%M%S")_logcat.log;

Are you telling me you had NO output from the third command? On review, I should of excluded the "2>/dev/null"

I had no relevant output from the third command, but I can browse that file with a SQLite browser and see a bunch of logs related to temefi which are basically the three commands you posted before. I am sending a magisk log and my logcat (which I also sent you via DM yesterday) hoping there's something useful in it. As for the temefi logs you just asked me to collect... I get a no such file or directory! It seems temefi can't write that file as it didn't have permissions? I'm just guessing.

Thank you so much for helping, but0Please don't try too hard on this as I am getting more and more certain my phone is just dying on me. Probably emmc or cpu

EDIT: I found what's going on!!! Along with Magisk, I also updated some modules. Among them was busybox 1.34.1. I reverted it back to the version I was using before upgrading, which is 1.31.1 and it works! Thanks for giving me an insight, please keep up the good work!!! Peace

 

[DiamondJohn]

...snip...
EDIT: I found what's going on!!! Along with Magisk, I also updated some modules. Among them was busybox 1.34.1. I reverted it back to the version I was using before upgrading, which is 1.31.1 and it works! Thanks for giving me an insight, please keep up the good work!!! Peace

So it works, right (stating the obvious...)

I too am using Busybox by @osm0sis v1.31.1
A few days ago, I downloaded what I think is a new stable build, but have yet to install it.

But, to be honest, that should not affect the third test, which is explicitly testing for Magisk Are you certain you are finding the dB in the exact location I specify?

 

[DiamondJohn]

almost forgot, with out the extra details you supplied, and solved for yourself, the following lines caught my interest in your logcast.

12-04 14:38:56.825 16518 16518 I WebViewFactory: Loading com.android.chrome version 107.0.5304.141 (code 530414123)
12-04 14:38:56.831 16518 16518 W linker  : Warning: "/data/app/com.android.chrome-dOT4y93ocKzjPsnTcpSAvg==/lib/arm64/libmonochrome.so" unused DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
12-04 14:38:56.884 16518 16518 I .utility.temef: Rejecting re-init on previously-failed class java.lang.Class<rh2>: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/webkit/PacProcessor;

The above implies that the issue is with your web-view. But obviously not. Which version are you runing?

 

[thunderteaser]

So it works, right (stating the obvious...)

I too am using Busybox by @osm0sis v1.31.1
A few days ago, I downloaded what I think is a new stable build, but have yet to install it.

But, to be honest, that should not affect the third test, which is explicitly testing for Magisk Are you certain you are finding the dB in the exact location I specify?

Yes, but I have to change package name as my app has been hidden. It just outputs the full path to sulogs.db. should ls-ing a db file output something else?
EDIT: probably this is intended as I'm using zygisk + shamiko.

almost forgot, with out the extra details you supplied, and solved for yourself, the following lines caught my interest in your logcast.

12-04 14:38:56.825 16518 16518 I WebViewFactory: Loading com.android.chrome version 107.0.5304.141 (code 530414123)
12-04 14:38:56.831 16518 16518 W linker  : Warning: "/data/app/com.android.chrome-dOT4y93ocKzjPsnTcpSAvg==/lib/arm64/libmonochrome.so" unused DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
12-04 14:38:56.884 16518 16518 I .utility.temef: Rejecting re-init on previously-failed class java.lang.Class<rh2>: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/webkit/PacProcessor;

The above implies that the issue is with your web-view. But obviously not. Which version are you runing?

It's using MiWebView, probably it's a very old version
EDIT: my bad, it's using Chrome v107.0.5304.141 and it seems consistent with the log. Those errors are probably another hint that my phone is dying. I might try switching to a custom ROM to see if anything runs smoother. I started getting a terribly freezy/laggy experience out of the blue some weeks ago (in safe mode as well).

 

[Atexor]

Hi, I've noticed conflict with YouTube Revanced. When I detach YT (vanilla) and then patch YT using ReVanced it's still detached successfully, however after phone reboot YouTube ReVanced often breaks (app crash on start and often changes package name to com.google.android.apps.youtube.app.YouTubeTikTokRoot_Application), sometimes it even rollbacks to older version but broken due to patches.

But, when first I patch YT with ReVanced, then I'm unable to detach it. TeMefi detects "com.google.android.youtube", but when wanting to detach I am getting error "Failed in preparation while looking for com.google.android.youtube. Do you have ANY apps detached"?

Except it I noticed that I've listed one bank app to detach... the problem is that I uninstalled that app weeks ago. And when I want to test detach it I am getting same issue but with "pl.creditagricole.nmobi" package.

Could you take a look on it?

 

[scoobyjenkins]

Hi, I've noticed conflict with YouTube Revanced. When I detach YT (vanilla) and then patch YT using ReVanced it's still detached successfully, however after phone reboot YouTube ReVanced often breaks (app crash on start and often changes package name to com.google.android.apps.youtube.app.YouTubeTikTokRoot_Application), sometimes it even rollbacks to older version but broken due to patches.

But, when first I patch YT with ReVanced, then I'm unable to detach it. TeMefi detects "com.google.android.youtube", but when wanting to detach I am getting error "Failed in preparation while looking for com.google.android.youtube. Do you have ANY apps detached"?

Except it I noticed that I've listed one bank app to detach... the problem is that I uninstalled that app weeks ago. And when I want to test detach it I am getting same issue but with "pl.creditagricole.nmobi" package.

Could you take a look on it?

I'm using the already patched magisk module from revanced.io and have no issues using TeMeFi to detach it. I don't already have YouTube installed as a system app as am on a custom android 11 ROM, I don't know if that makes a difference?