[APP][TOOL] TeMeFI comprehensive system Administration

Search This thread

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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".:poop:

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.
 
Last edited:
  • Like
Reactions: rodken

KitsuneFoxy

Senior Member
Dec 14, 2014
159
15
Leicester
Google Nexus 4
HTC Desire C
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.
 

Attachments

  • Screenshot_20221025-053719.png
    Screenshot_20221025-053719.png
    68.5 KB · Views: 46

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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)
Code:
adb connect ?????
adb shell

run the following in the shell
Code:
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

Code:
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

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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.
Code:
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)
Code:
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.
 
  • Like
Reactions: curiousrom

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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

Member
Dec 14, 2021
5
2
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

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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.
 

thunderteaser

Senior Member
Jul 22, 2010
829
293
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.

Screenshot_2022-12-04-14-42-38-614_diamondjohndroid.utility.temefi.png

Connect to the phone via ADB (or you could do it in a rooted terminal on the device)
Code:
adb connect ?????
adb shell

run the following in the shell
Code:
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

Code:
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
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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

Senior Member
Jul 22, 2010
829
293
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.
 
Last edited:
  • Like
Reactions: pocketrule

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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 :whistle:

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.

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

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

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

PS: Thanks for switching the image (y)
 
  • Like
Reactions: pocketrule

thunderteaser

Senior Member
Jul 22, 2010
829
293
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.

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

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

I attached these logs to the post.

Code:
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. :)
 

Attachments

  • adb_logs.zip
    4 KB · Views: 7
Last edited:
  • Like
Reactions: pocketrule

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
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

Senior Member
Jul 22, 2010
829
293
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
 

Attachments

  • magisk_log_2022-12-05T04.13.19.log
    63.4 KB · Views: 3
  • temefi_logs.zip
    37.9 KB · Views: 4
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
...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 o_O 👀 Are you certain you are finding the dB in the exact location I specify?
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,513
6,493
Sydney
almost forgot, with out the extra details you supplied, and solved for yourself, the following lines caught my interest in your logcast.
Code:
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

Senior Member
Jul 22, 2010
829
293
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 o_O 👀 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.
Code:
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).
 
Last edited:
  • Like
Reactions: pocketrule

Atexor

Senior Member
Jun 28, 2014
410
156
Poland
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

Senior Member
Jul 8, 2012
3,716
4,861
Leeds
OnePlus 5
Lenovo Yoga Tab 3 Plus
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?
 
  • Like
Reactions: pocketrule

Top Liked Posts

  • 4
    FYI: This project is not dead. I have simply been away from my PC since about Dec 11 2022, and now it will probably be a while till I get back into the swing of things. I had a major release I was testing in late dec
    1
    I'd like to accomplish something unusual and idiosyncratic on my Pixel 5 running Android 11, and I'm wondering whether TeMeFI might offer one or more facilities which could help me.

    First, some background ...

    Google monitors our phones and keeps track of whether screen locking is enabled. 3rd parties (such as banks) can query this screen-locking status, and it turns out that some (all?) banks remove their debit cards from our Google-Pay wallets if they detect that screen locking is turned off in our devices.

    As part of my own, personal, idiosyncratic nature, I hate having to use screen locking, while at the same time, I'm gladly willing to take on the risk of carrying an unlocked device with usable debit cards that are available for Google Pay.

    This finally brings me to my question: is there anything I can set up via TeMeFI which can cause my device to fool Google into "thinking" that either Pin Locking, Pattern Locking, Fingerprint Locking, or Password Locking is enabled on my device, when actually, I'm only using Swipe Locking?

    Thank you in advance for any thoughts and suggestions.
    Never had this issue to deal with myself, so wouldn't know how to side-step it. Sorry.

    This sounds like something that Magisk users may of had to deal with previously, as they have done a lot of work regarding hiding root from the banking apps, and this sounds like an extension of those action. Ie maybe ask on the MAgisk thread, it really sounds like something others have had to deal with previously. I too only have used a lock pattern / fingerprint in the past two years ie when I got my Pixel 4A withy a fingerprint reader. but no banking until very recently.

    FYI: I am rooted (obviously) and my bank (one of the big ones in Australia) lets me run and use their banking app on my phone, without any messing about with the device (eg through magisk modules) to hide root.:cool:

    Im not sure if I should be grateful (y) or concerned their security is not up to scratch:eek: so far, its worked in my favour. ie I can do banking on my device and even my old 2013 device, both rooted.
  • 4
    FYI: This project is not dead. I have simply been away from my PC since about Dec 11 2022, and now it will probably be a while till I get back into the swing of things. I had a major release I was testing in late dec
    1
    I'd like to accomplish something unusual and idiosyncratic on my Pixel 5 running Android 11, and I'm wondering whether TeMeFI might offer one or more facilities which could help me.

    First, some background ...

    Google monitors our phones and keeps track of whether screen locking is enabled. 3rd parties (such as banks) can query this screen-locking status, and it turns out that some (all?) banks remove their debit cards from our Google-Pay wallets if they detect that screen locking is turned off in our devices.

    As part of my own, personal, idiosyncratic nature, I hate having to use screen locking, while at the same time, I'm gladly willing to take on the risk of carrying an unlocked device with usable debit cards that are available for Google Pay.

    This finally brings me to my question: is there anything I can set up via TeMeFI which can cause my device to fool Google into "thinking" that either Pin Locking, Pattern Locking, Fingerprint Locking, or Password Locking is enabled on my device, when actually, I'm only using Swipe Locking?

    Thank you in advance for any thoughts and suggestions.
    1
    I'd like to accomplish something unusual and idiosyncratic on my Pixel 5 running Android 11, and I'm wondering whether TeMeFI might offer one or more facilities which could help me.

    First, some background ...

    Google monitors our phones and keeps track of whether screen locking is enabled. 3rd parties (such as banks) can query this screen-locking status, and it turns out that some (all?) banks remove their debit cards from our Google-Pay wallets if they detect that screen locking is turned off in our devices.

    As part of my own, personal, idiosyncratic nature, I hate having to use screen locking, while at the same time, I'm gladly willing to take on the risk of carrying an unlocked device with usable debit cards that are available for Google Pay.

    This finally brings me to my question: is there anything I can set up via TeMeFI which can cause my device to fool Google into "thinking" that either Pin Locking, Pattern Locking, Fingerprint Locking, or Password Locking is enabled on my device, when actually, I'm only using Swipe Locking?

    Thank you in advance for any thoughts and suggestions.
    Never had this issue to deal with myself, so wouldn't know how to side-step it. Sorry.

    This sounds like something that Magisk users may of had to deal with previously, as they have done a lot of work regarding hiding root from the banking apps, and this sounds like an extension of those action. Ie maybe ask on the MAgisk thread, it really sounds like something others have had to deal with previously. I too only have used a lock pattern / fingerprint in the past two years ie when I got my Pixel 4A withy a fingerprint reader. but no banking until very recently.

    FYI: I am rooted (obviously) and my bank (one of the big ones in Australia) lets me run and use their banking app on my phone, without any messing about with the device (eg through magisk modules) to hide root.:cool:

    Im not sure if I should be grateful (y) or concerned their security is not up to scratch:eek: so far, its worked in my favour. ie I can do banking on my device and even my old 2013 device, both rooted.
  • 133
    TeMeFI

    icon_source3.png

    This app provides/returns a bucket load of information regarding your device and the currently running ROM, and much, much more. And hence the name "TeMeFI"; as its Too Much F????? Information. The F stands for whatever your comfortable with.;)


    Download: TeMeFI v1.1.19
    MD5: E643DD1ECC3243473A0EAEBF69CD4209

    Simply download the APK and install as normal, and allow root when asked, and grant storage permissions. I *think* the very first time you run it, there possibly may be an issue with the menu. Simply stop and restart the app.

    You can use it without root, but you will be HEAVILY limited in what you can do. Also, installing busybox opens another menu for you, and so does Magisk (17.*+). SQLite3 is also a HUGE feature adder (ie if you have it, it enables many many methods). Can be installed via Magisk if your ROM does not have it by default.

    If you are unrooted, have a read of the following post, regarding a recently added feature for non-root users

    The "search" function is very useful for finding what you need, but it does not search inside dynamic menu's. Its the magnifying glass in the slide out toolbar/menu

    The current menu can be viewed within the app at TeMeFI Configuration>Show Whole Menu or a historic example at:
    CURRENT MENU [as at 2021-11-19]

    XDA:DevDB Information

    Contributors

    DiamondJohn

    Version Information
    Status:
    Stable
    Current Stable Version: 1.1.19
    Stable Release Date / Last Updated: 3 Sug 2022
    Current Beta Version:
    1.0.3
    Beta Release Date: 2018-06-21

    Created 2018-06-19

    I will fill in this page as I get around to it.
    20
    Fly-out Toolbar items and their Actions

    The fly out toolbar has had its buttons and their corresponding actions change over time. However of recent, they have been pretty stable, and as they have changed over time, and I probably said what / how their function changed, its probably all over the thread. So, I thought it might be best to have a single location / doco of what the current buttons actually do.

    Firstly, to display the toolbar, simply click on the menu. If it isn't already showing.
    MenuButton.png

    EVERY button, has both a "short-press" and "long-press" action.

    The icons kind-of relate to their short press action.

    NB The following are from v1.0..19 The main difference are a long press on the [<] arrow goes back to the previous results, and a long press of the [HOME} icon reloads the current menu (useful if you filtered the menu items), and a long press on the pencil icon saves off the action as a favourite. Also, the long press on the exit icon [X] acts to filter a menu list that was generated by code. eg any list of installed apps
    For Short-press actions:
    Shortpress menu actions.png

    For Long press actions
    Longpress menu actions.png

    If you get an error, a toast will be shown which is HEAVILY CUT DOWN, so please no screen shots! :mad: Also, in a recent release a Bomb Icon will appear on the screen after an error. Short press to display then FULL error, or long press the bomb to clear the error. It will not clear by itself.

    And again, NOT a screen shot of the results. Save off the results using the save button (ie the pencil icon explained above), then get the log text file from /sdcard/TeMeFI, and attach it to a post.

    please stop with the screenshots of a cut down error message :cry::cry::cry:
    16
    New Build!

    New Version v1.0.77

    Download: SEE OP!

    Notable changes are:
    v2 of detach apps from playstore NB: If you are already using it, simply reapply the method. Method 3 is recommended for YouTube, but all 3 have been upgraded
    Added touchable hot-spots to the mem info graph
    Added Timezone view and setting
    corrected the loading of the previous results when displaying the covid pages

    Updated Items. within the menu at "TeMeFI Configuration>Latest Updated Menu Items"
    Application Info / Manage>Detach Package from Playstore>Select Package then Protection Level v2
    Application Info / Manage>Detach Package from Playstore>List all configured detached apps
    Currently Running>Memory>Meminfo Usage Graph by Category
    Currently Running>Memory>Meminfo Usage Graph by Process
    Currently Running>Memory>Meminfo Usage Graph by OOM
    Various Ungrouped Extras>COVID-19 Status Update
    Various Ungrouped Extras>COVID-19 Status Update>COVID-19 Status Update Desktop

    New Items. within the menu at "TeMeFI Configuration>Latest Added Menu Items"
    Current State>Timezone>Set Current Timestamp (ROOT)
    Current State>Timezone>Set Current Timezone
    Current State>Timezone>Get Current Timezone
    Current State>Timezone
    Current State>Timezone>Get Current Timezone (ROOT)

    It is recommended that you delete ALL your existing favorites and re-create them, as they will run the old code/version.

    Enjoy and stay safe.
    14
    New Build!

    New Version v1.0.66

    This release is a major update.:eek:

    Download: SEE OP!

    • Added a new type of battery history graph. Type 4. This new one plots the battery drain % per hour (user selectable max range) with the colour of the block as the battery level %.
    • corrected spelling of "Manage Permission" to "Manage Permissions"
    • Removed duplicate battery reset, changed it to a short cut
    • Moved a bunch of battery stuff into a new menu of "Currently Running>Battery" INCLUDING the battery history graph
    • moved running processes into a sub menu
    • moved a bunch of dumpsys commands from various location to mostly be under the single menu item "Current State>Dumpsys"
    • Added LMK details
    • Added Setting of LMK min memory values
    • Added Setting of LMK min memory break OOM levels and their mod
    • On the new battery history graph, the horizontal ruler count depends on the % (4-4 lines, 25=5 lines, 50=5 lines 100=4 lines and 200 = 10 lines)
    • added a colour map/legend to battery history graphs that use it
    • Added a few other menu items/actions
    • Improved handling of device rotation/orientation and switching to another app and back again

    As you can see below, there have been a lot of changes to the internal code that run reports, and perform the actions.

    However, the BIG new feature is the "Currently Running>Battery>Battery History Graph", I have now added a new way to look at your battery history.
    "4. Discharge Rate as vertical height and Battery Level as the Gradient Colour (Green=100%, Red=0%)"​

    THIS NEW GRAPH IS THE BIG ADDITION! It is truly my latest obsession. It displays your battery discharge rate / hour as the vertical height (so the lower the better), and the colour of the graph shows your battery level (it should basically fade from green to red, left to right) And logically, the higher the graph, the faster the change in colours. NB: My phone has a removable battery, so you can see jumps where I changed battery, instead of charging the one in the device. Another interesting fact that comes out in the graph, is the jump in discharge (ie the height) during a boot and shutdown, which makes totally logical sense.:good:

    This graph is an early build, so should be considered a WIP:p. 90% of the time, it appears OK:victory:, but I have seen some questionable results (minor) if the device is rebooted and switched between charging often. I thought it was good enough for a first release :highfive:

    It takes some time in getting a firm grasp of exactly what you are looking at, but once you do, its like you can see the "Matrix" :cool:

    NB: This graph is in addition to the previously provided graphs.

    You can view the new graph at 4%/hour (with each horizontal line at 0.5% intervals), 25%/hour (with each horizontal line at 5% intervals), 50%/hour (with each horizontal line at 10% intervals), 100% (with each horizontal line at 25% intervals) and 200% (with each horizontal line at 10% intervals). (and a few others I added at the last minute:rolleyes:)

    An important concept to understand, is the 100% / hour would mean your battery would be dead in an hour, IIIFFFF the graph showed that it was running at full tilt for the full hour.

    There is also a colour chart/grid below the graph to help translate the colours to actual battery levels. But again, if you transfer the file to a pc, the mouse hover should give you the details (I didn't test it, but I did not change it either)

    When its charging, it may appear to flip up and down. This is due to the source data being in whole numbers (ie integers, eg 1 instead of 1.5), so it it charges at 3% per 2 minutes, it will report 1 minute at 1% and then the next minute at 2%, and then back again, and hence the flip/jumping up and down.

    Its good to use the 4% to check your idle drain (mine goes below .5%! which would mean theoretically 200hrs if it stayed like that; but I normally get about 25hrs due to actually using the phone). I switch to one of the higher (ie 25-200%) graphs to see just how high the peaks go for a very short time.

    The other BIG thing is the Low Memory Killer (ie LMK) items.


    Also, its been there a while, but wake-locks are under the new battery menu as well.

    Totally New Items. within the menu at "TeMeFI Configuration>Latest Added Menu Items"
    Code:
    These first two are simply shortcuts to the original items found in a different location within the menu. Just saves navigating back and forth when investigating/correcting the MediaDB
    	Database>MediaDB SQL>Extend Shortcut: Media Scan File(s) [Java] - Date Range
    	Database>MediaDB SQL>Extend Shortcut: Media Scan File(s) [Java] - Start Character
    
    General info regarding the internal action items. I mainly use this for info and as an integrity check of the menu system before I do a release, in case of a typo.
    For example, The first one is a listing of where I have used shortcuts, which in a way are a duplicate, but only as an entry point. There is only a single version of the code.
    	TeMeFI Configuration>TeMeFI Internal Database Information>Menu / Action Shortcuts
    	TeMeFI Configuration>TeMeFI Internal Database Information>Action Type Breakdown
    	TeMeFI Configuration>TeMeFI Internal Database Information>Count of Child Menu Items
    	TeMeFI Configuration>TeMeFI Internal Database Information>Duplicate Sort Order
    	TeMeFI Configuration>TeMeFI Internal Database Information>Missing Parent Menu Item
    	TeMeFI Configuration>TeMeFI Internal Database Information>Missing Expand Prefix
    	TeMeFI Configuration>TeMeFI Internal Database Information>Menu with No Children
    	TeMeFI Configuration>TeMeFI Internal Database Information>Missing Action Command
    	TeMeFI Configuration>TeMeFI Internal Database Information
    
    These allow you to view AND modify your LMK. NB: The third item in the list actually has ALL the config detils (mem va;lsand OOM val's) while the first has a bit of textural background explaining LMK values somewhat.
    	Currently Running>Memory Info>Low Memory Killer (LMK)>Current OOM to LMK Min Memory
    	Currently Running>Memory Info>Low Memory Killer (LMK)>Current LMK Min Memory Free Values
    	Currently Running>Memory Info>Low Memory Killer (LMK)>Set OOM to LMK Min Memory Free Break Points
    	Currently Running>Memory Info>Low Memory Killer (LMK)>Set LMK Min Memory Free Values
    	Currently Running>Memory Info>Low Memory Killer (LMK)
    
    	Currently Running>Battery>Battery Files /sys/class/power_supply/battery
    	
    	Currently Running>Broadcasted Activity Intents
    	Currently Running>Battery>Battery Properties & Health
    	Currently Running>Battery>Battery Reset
    	Device Details>Kernel>CPU Scheduler Features
    	Dynamic Lists>Files>Data System
    
    	Currently Running>Running Processes
    	Currently Running>Battery

    You will see some "New Items" in this list, as I had major upgrade/fixes after my initial cut of code.
    Modified Menu Items within the menu at "TeMeFI Configuration>Updated Menu Items"
    Code:
    TeMeFI Configuration>TeMeFI Internal Database Information>Count of Child Menu Items
    TeMeFI Configuration>Get default Blob Config      
    Currently Running>Memory Info>Low Memory Killer (LMK)>Current OOM to LMK Min Memory
    Currently Running>Memory Info>Low Memory Killer (LMK)>Set OOM to LMK Min Memory Fre
    Database>Dynamic DB Queries>Two Field Table Filter
    Database>Dynamic DB Queries>Filtered Delete Table Data
    Database>Admin Actions>Individual PRAGMA statements against a Table
    Database>Dynamic DB Queries>Complex Filtered Table Data
    Database>Dynamic DB Queries>Filtered Delete Table Data
    Database>Dynamic DB Queries>Filtered & Grouped Table Data
    Database>Dynamic DB Queries>Filtered Table Data   
    Database>Dynamic DB Queries>Grouped Table Data    
    Database>Dynamic DB Queries>Two Field Table Filter
    Database>Dynamic DB Queries>All Table data        
    TeMeFI Configuration>TeMeFI Internal Database Information>Action Type Breakdown
    TeMeFI Configuration>TeMeFI Internal Database Information>Duplicate Sort Order
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Action Command
    TeMeFI Configuration>TeMeFI Internal Database Information>Menu with No Children
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Expand Prefix
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Parent Menu Item
    TeMeFI Configuration>TeMeFI Internal Database Information>Count of Child Menu Items
    TeMeFI Configuration>TeMeFI Internal Database Information>Menu / Action Shortcuts
    Database>Dynamic DB Queries>All Table data        
    Database>Dynamic DB Queries>Grouped Table Data    
    Database>Dynamic DB Queries>Filtered Table Data   
    Database>Dynamic DB Queries>Filtered & Grouped Table Data
    Database>Dynamic DB Queries>Complex Filtered Table Data
    Device Details>Display Size                       
    Currently Running>Memory Info>Low Memory Killer (LMK)>Current OOM to LMK Min Memory
    Database>Admin Actions>Run ALL PRAGMA statements for a Database
    Database>Admin Actions>Individual PRAGMA statements against a Table
    Database>Dynamic DB Queries>Complex Filtered Table Data
    Database>Dynamic DB Queries>Filtered Delete Table Data
    Database>Dynamic DB Queries>Filtered & Grouped Table Data
    Database>Dynamic DB Queries>Filtered Table Data   
    Database>Dynamic DB Queries>Grouped Table Data    
    Database>Dynamic DB Queries>Two Field Table Filter
    Database>Dynamic DB Queries>All Table data        
    TeMeFI Configuration>TeMeFI Internal Database Information>Action Type Breakdown
    TeMeFI Configuration>TeMeFI Internal Database Information>Duplicate Sort Order
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Action Command
    TeMeFI Configuration>TeMeFI Internal Database Information>Menu with No Children
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Expand Prefix
    TeMeFI Configuration>TeMeFI Internal Database Information>Missing Parent Menu Item
    TeMeFI Configuration>TeMeFI Internal Database Information>Count of Child Menu Items
    TeMeFI Configuration>TeMeFI Internal Database Information>Menu / Action Shortcuts
    Currently Running>Battery>Battery History Graph   
    Device Details>Kernel>SYS Kernel File join        
    Currently Running>Battery>Battery Simulate>Battery Reset

    Enjoy!
    14
    New Build!

    New Version v1.0.82

    Download: SEE OP!

    Notable changes:
    NB: the changes made to the detach methods, are only spelling and extra info. There are no structural/technical changes to the detach methods.
    The battery history changes are covering two aspects.
    1. The formatting is now more in-line with the doze graph (black on white table text for headers/labels)
    2. The Auto-Height has been corrected. I think it currently runs off of a % of items by count, not by time at that discharge rate. Previously it rounded the max up so much, it basically included nearly everything every time.

    Updated Items. within the menu at "TeMeFI Configuration>Latest Updated Menu Items"
    Currently Running>Battery>Battery History Graph
    Application Info / Manage>Detach Package from Playstore>ENABLE ATT: One App for re-attachment
    Application Info / Manage>Detach Package from Playstore>List all configured detached apps

    New Items. within the menu at "TeMeFI Configuration>Latest Added Menu Items"
    Currently Running>Doze>Doze Parameter Description

    Enjoy and stay safe.