• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[APP][TOOL] TeMeFI comprehensive system Administration

Search This thread

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Hi, sorry if wrong but i got this log after detach Youtube and Youtube music with method 3, is it fine?
...snip...
Where to start...

Could you please please PLEASE edit your post and change the included screenshot to a thumbnail instead of the full image. Not only does it make your own post harder to read, but also everyone else's.

On a high level, a "segmentation fault" is a very low level error, and i would only expect to see that in the binaries (as untrapped errors) built into your ROM, not directly from script code executed by TeMeFI.

Do not post screenshots of errors. A screenshot is only part of the results, which are scroll-able! Its like you have shown me the tip of your finger, and are asking me to diagnose a brain hemorrhage.
SAVE the output using the little disk icon on the right of the fly-out menu. Then short click (a long click will delete the error log) the little bomb icon (which i thought would be pretty hard to miss) in the top right, and save off its output; we'll use these later, but there is still more reports to save off.

Next, If you looked at the menu, the item just above the detach is a "Check Detach". If you click on that and check the detach of youtube, save off those results also.

Your post is missing possible important info outside of TeMeFII. What device? what ROM and android version?

Another script I would like to see the output from, is the SQLite tests/info. Run the reports, and save off the results for Database>SQLite Location and Version + Database>SQLite3 Test And Help

So, from the above, you should have 4 saved off reports (if I counted correctly). Go into /sdcard/TeMeFI and zip up these 4 reports, and attach them to a post here, with the answer to my above questions regarding device and ROM.

out of interest, can you run the Battery History reports OK?
 

oldman20

Senior Member
Jan 18, 2014
917
67
Hà Nội
Samsung Galaxy Note 9
Where to start...

Could you please please PLEASE edit your post and change the included screenshot to a thumbnail instead of the full image. Not only does it make your own post harder to read, but also everyone else's.

On a high level, a "segmentation fault" is a very low level error, and i would only expect to see that in the binaries (as untrapped errors) built into your ROM, not directly from script code executed by TeMeFI.

Do not post screenshots of errors. A screenshot is only part of the results, which are scroll-able! Its like you have shown me the tip of your finger, and are asking me to diagnose a brain hemorrhage.
SAVE the output using the little disk icon on the right of the fly-out menu. Then short click (a long click will delete the error log) the little bomb icon (which i thought would be pretty hard to miss) in the top right, and save off its output; we'll use these later, but there is still more reports to save off.

Next, If you looked at the menu, the item just above the detach is a "Check Detach". If you click on that and check the detach of youtube, save off those results also.

Your post is missing possible important info outside of TeMeFII. What device? what ROM and android version?

Another script I would like to see the output from, is the SQLite tests/info. Run the reports, and save off the results for Database>SQLite Location and Version + Database>SQLite3 Test And Help

So, from the above, you should have 4 saved off reports (if I counted correctly). Go into /sdcard/TeMeFI and zip up these 4 reports, and attach them to a post here, with the answer to my above questions regarding device and ROM.

out of interest, can you run the Battery History reports OK?
Thank and so sorry, i edited my previous post! And below is logs i followed your instruction!
And last, I can't run Battery History reports! Thanks for your patience!
I'm using Samsung Galaxy Note 9 N960F/DS with SuperStable Rom OneUI 2.5 v18

 

Attachments

  • Logs.zip
    4.2 KB · Views: 4

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Thank and so sorry, i edited my previous post! And below is logs i followed your instruction!
And last, I can't run Battery History reports! Thanks for your patience!
I'm using Samsung Galaxy Note 9 N960F/DS with SuperStable Rom OneUI 2.5 v18

Thank-you for editing your post (y)

Now, the issue you appear to be having is that the SQLite binary that comes with your ROM is VERRRRRY old. And thus, unstable. The following is a comparison of different versions.

SOURCEVERSION
Yours3.7.6.3-Titanium
From an Oreo ROM I built from source a few YEARS back (NB: Oreo is before/older than Pie)3.19.4
The one from Magisk Repository3.27.2
Mine (built from latest source)3.35.5

Looking in comparison at the features supported:

YOURS v3.7.6.3-Titanium
MINE v3.35.5
Usage: /system/xbin/sqlite3 [OPTIONS] FILENAME [SQL]
FILENAME is the name of an SQLite database. A new database is created
if the file does not previously exist.
OPTIONS include:
-help show this message
-init filename read/process named file
-echo print commands before execution
-[no]header turn headers on or off
-bail stop after hitting an error
-interactive force interactive I/O
-batch force batch I/O
-column set output mode to 'column'
-csv set output mode to 'csv'
-html set output mode to HTML
-line set output mode to 'line'
-list set output mode to 'list'
-separator 'x' set output field separator (|)
-stats print memory stats before each finalize
-nullvalue 'text' set text string for NULL values
-version show SQLite version
-vfs NAME use NAME as the default VFS













Usage: /system/bin/sqlite3 [OPTIONS] FILENAME [SQL]
FILENAME is the name of an SQLite database. A new database is created
if the file does not previously exist.
OPTIONS include:
-append append the database to the end of the file
-ascii set output mode to 'ascii'
-bail stop after hitting an error
-batch force batch I/O
-box set output mode to 'box'
-column set output mode to 'column'
-cmd COMMAND run "COMMAND" before reading stdin
-csv set output mode to 'csv'
-echo print commands before execution
-init FILENAME read/process named file
-[no]header turn headers on or off
-help show this message
-html set output mode to HTML
-interactive force interactive I/O
-json set output mode to 'json'
-line set output mode to 'line'
-list set output mode to 'list'
-lookaside SIZE N use N entries of SZ bytes for lookaside memory
-markdown set output mode to 'markdown'
-memtrace trace all memory allocations and deallocations
-mmap N default mmap size set to N
-newline SEP set output row separator. Default: '\n'
-nofollow refuse to open symbolic links to database files
-nullvalue TEXT set text string for NULL values. Default ''
-pagecache SIZE N use N slots of SZ bytes each for page cache memory
-quote set output mode to 'quote'
-readonly open the database read-only
-separator SEP set output column separator. Default: '|'
-stats print memory stats before each finalize
-table set output mode to 'table'
-tabs set output mode to 'tabs'
-version show SQLite version
-vfs NAME use NAME as the default VFS

As you can see, it is also lacking a LOT of functionality, as well as being unstable.

Just because a ROM is stable when making calls and SMS does not mean it is really stable. For example, my grandmothers car is "stable" and may never break-down, but as soon as you drive around a corner at speeds greater than 5km/hr, it may flip on its roof. I call that car unstable, even though my car may break-down randomly more often.

Now, your options.

For all of this, it is your responsibility to make back-ups and only proceed if your comfortable. Its all on you, dont blame me for anything.;)

  • Contact your ROM dev and ask them to update their SQLite source. This may actually be the tip of the iceberg with other parts of their ROM (ie ToyBox) being old
  • Try installing the updated SQLite3 binary from/as the Magisk modules. The thing that I am unsure of is your location as /system/xbin where the magisk module (and my previous ROM) place it in /system/bin
  • NB I am assuming this is an ARM AMD i knew that sounded wrong when I was typing processor, not x86. To get really funky, I am guessing your system partition is R/W, you could (and make a Nandroid before) copy the sqlite3 file from /data/data/diamondjohndroid.utility.temefi/cached/sqlite3 to /system/xbin/sqlite3 And make sure the ownership & permissions (755) are correct
Ive attached my results for your own comparisons.
 

Attachments

  • 20210624104408_TeMeFI_Database_SQLite_3_Test_Help.log
    1.9 KB · Views: 2
  • 20210624104421_TeMeFI_Database_SQLite_Location_and_Version.log
    274 bytes · Views: 2
Last edited:

oldman20

Senior Member
Jan 18, 2014
917
67
Hà Nội
Samsung Galaxy Note 9
Thank-you for editing your post (y)

Now, the issue you appear to be having is that the SQLite binary that comes with your ROM is VERRRRRY old. And thus, unstable. The following is a comparison of different versions.

SOURCEVERSION
Yours3.7.6.3-Titanium
Mine (built from latest source)3.35.5
From an Oreo ROM I built from source a few YEARS back (NB: Oreo is before/older than Pie)3.19.4
The one from Magisk Repository3.27.2

Looking in comparison at the features supported:

YOURS v3.7.6.3-Titanium
MINE v3.35.5
Usage: /system/xbin/sqlite3 [OPTIONS] FILENAME [SQL]
FILENAME is the name of an SQLite database. A new database is created
if the file does not previously exist.
OPTIONS include:
-help show this message
-init filename read/process named file
-echo print commands before execution
-[no]header turn headers on or off
-bail stop after hitting an error
-interactive force interactive I/O
-batch force batch I/O
-column set output mode to 'column'
-csv set output mode to 'csv'
-html set output mode to HTML
-line set output mode to 'line'
-list set output mode to 'list'
-separator 'x' set output field separator (|)
-stats print memory stats before each finalize
-nullvalue 'text' set text string for NULL values
-version show SQLite version
-vfs NAME use NAME as the default VFS













Usage: /system/bin/sqlite3 [OPTIONS] FILENAME [SQL]
FILENAME is the name of an SQLite database. A new database is created
if the file does not previously exist.
OPTIONS include:
-append append the database to the end of the file
-ascii set output mode to 'ascii'
-bail stop after hitting an error
-batch force batch I/O
-box set output mode to 'box'
-column set output mode to 'column'
-cmd COMMAND run "COMMAND" before reading stdin
-csv set output mode to 'csv'
-echo print commands before execution
-init FILENAME read/process named file
-[no]header turn headers on or off
-help show this message
-html set output mode to HTML
-interactive force interactive I/O
-json set output mode to 'json'
-line set output mode to 'line'
-list set output mode to 'list'
-lookaside SIZE N use N entries of SZ bytes for lookaside memory
-markdown set output mode to 'markdown'
-memtrace trace all memory allocations and deallocations
-mmap N default mmap size set to N
-newline SEP set output row separator. Default: '\n'
-nofollow refuse to open symbolic links to database files
-nullvalue TEXT set text string for NULL values. Default ''
-pagecache SIZE N use N slots of SZ bytes each for page cache memory
-quote set output mode to 'quote'
-readonly open the database read-only
-separator SEP set output column separator. Default: '|'
-stats print memory stats before each finalize
-table set output mode to 'table'
-tabs set output mode to 'tabs'
-version show SQLite version
-vfs NAME use NAME as the default VFS

As you can see, it is also lacking a LOT of functionality, as well as being unstable.

Just because a ROM is stable when making calls and SMS does not mean it is really stable. For example, my grandmothers car is "stable" and may never break-down, but as soon as you drive around a corner at speeds greater than 5km/hr, it may flip on its roof. I call that car unstable, even though my car may break-down randomly more often.

Now, your options.

For all of this, it is your responsibility to make back-ups and only proceed if your comfortable. Its all on you, dont blame me for anything.;)

  • Contact your ROM dev and ask them to update their SQLite source. This may actually be the tip of the iceberg with other parts of their ROM (ie ToyBox) being old
  • Try installing the updated SQLite3 binary from/as the Magisk modules. The thing that I am unsure of is your location as /system/xbin where the magisk module (and my previous ROM) place it in /system/bin
  • NB I am assuming this is an amd processor, not x86. To get really funky, I am guessing your system partition is R/W, you could (and make a Nandroid before) copy the sqlite3 file from /data/data/diamondjohndroid.utility.temefi/cached/sqlite3 to /system/xbin/sqlite3 And make sure the ownership & permissions (755) are correct
Ive attached my results for your own comparisons.
Many thank sir, i followed the third way with replace sqlite3 and run detach an app without error, is it work properly? Here the logs, thank!
 

Attachments

  • Logsnew.zip
    11.6 KB · Views: 3

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Many thank sir, i followed the third way with replace sqlite3 and run detach an app without error, is it work properly? Here the logs, thank!
There is already a detach tester built into TeMeFI. ie. no need to ask me! its the item above DETACH item.

For the battery history, I wouldn't run anything less than SCREEN-WIDTHx1 I cant really remember why I even bothered to include them, except for mathematical checks, or maybe for people with really low res screens. Also, the 1hr (suggested) is normally what I find good. But I do use the tiny 5min window for things like "Active [ACTIVE].TEXT" to get a better of understanding of when they actually occurred more accurately. On a side, for "App Inactive [APP_INACTIVE].TEXT" I dont actually get any results.

As for the Bomb items. This is a "last error" thing, and therefore, once you get an error, it sticks all the way through multiple successful actions (inc possibly from the previous month), until a new error occurs. So, these errors may of been from the previous runs with the old SQLite binary. For example, the two you have included are the exact same error event! and have nothing to do with the reports that you did include in the zip. To clear this old error and be ready for the next real error, simply long press the bomb icon.

If I am reading the bomb text right, its complaining that your SQLite does not understand the inbuilt function INSTR which is a really basic sql function. one I would of thought even your old sqlite would understand.
 
Last edited:

oldman20

Senior Member
Jan 18, 2014
917
67
Hà Nội
Samsung Galaxy Note 9
There is already a detach tester built into TeMeFI. ie. no need to ask me! its the item above DETACH item.

For the battery history, I wouldn't run anything less than SCREEN-WIDTHx1 I cant really remember why I even bothered to include them, except for mathematical checks, or maybe for people with really low res screens. Also, the 1hr (suggested) is normally what I find good. But I do use the tiny 5min window for things like "Active [ACTIVE].TEXT" to get a better of understanding of when they actually occurred more accurately. On a side, for "App Inactive [APP_INACTIVE].TEXT" I dont actually get any results.

As for the Bomb items. This is a "last error" thing, and therefore, once you get an error, it sticks all the way through multiple successful actions (inc possibly from the previous month), until a new error occurs. So, these errors may of been from the previous runs with the old SQLite binary. For example, the two you have included are the exact same error event! and have nothing to do with the reports that you did include in the zip. To clear this old error and be ready for the next real error, simply long press the bomb icon.

If I am reading the bomb text right, its complaining that your SQLite does not understand the inbuilt function INSTR which is a really basic sql function. one I would of thought even your old sqlite would understand.
Thank, last noob quest? When i replace sqlite3 in my rom with one from TeMeFi, i already set permission 755, but group permission can't, while original is "shell (2000), replaced file is "root (0). Any wrong if let it still there? Thank and sorry :(
 

Attachments

  • Screenshot_20210624-141120_X-plore.jpg
    Screenshot_20210624-141120_X-plore.jpg
    458.9 KB · Views: 31

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Thank, last noob quest? When i replace sqlite3 in my rom with one from TeMeFi, i already set permission 755, but group permission can't, while original is "shell (2000), replaced file is "root (0). Any wrong if let it still there? Thank and sorry :(
I would not feel comfortable with a single word answer on this question. This thread and myself are not an android source of whatever info/training you wish for, and I dont wish to head down that road. The last issue you had was not an issue with TeMeFI, but clearly a ROM issue, which I helped you fix. I could of just told you your issue, and set you on your own research path. There are many other threads on XDA where a question like this is on-topic, but its not here. This is the TeMeFI thread.

If anyone else wishes to answer your question, then they should feel free, but still, I would quote it and answer it in another thread, where many more people could be helped.

Although, your issue did make me think of a feature where instead of falling back to the inbuilt SQLite, I could add a feature where TeMeFI users could explicitly select the internal SQLite binary as the one to use when using TeMeFI. It would of avoided you touching your ROM to enable the features of TeMeFI; and ONLY TeMeFI, so you would still have a dud sqlite binary (only used by shell commands).
 

oldman20

Senior Member
Jan 18, 2014
917
67
Hà Nội
Samsung Galaxy Note 9
I would not feel comfortable with a single word answer on this question. This thread and myself are not an android source of whatever info/training you wish for, and I dont wish to head down that road. The last issue you had was not an issue with TeMeFI, but clearly a ROM issue, which I helped you fix. I could of just told you your issue, and set you on your own research path. There are many other threads on XDA where a question like this is on-topic, but its not here. This is the TeMeFI thread.

If anyone else wishes to answer your question, then they should feel free, but still, I would quote it and answer it in another thread, where many more people could be helped.

Although, your issue did make me think of a feature where instead of falling back to the inbuilt SQLite, I could add a feature where TeMeFI users could explicitly select the internal SQLite binary as the one to use when using TeMeFI. It would of avoided you touching your ROM to enable the features of TeMeFI; and ONLY TeMeFI, so you would still have a dud sqlite binary (only used by shell commands).
I understand and Sincerely sorry to bother you. Thats a great thing, many thank!😀
 
  • Like
Reactions: pocketrule

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
...snip...
Although, your issue did make me think of a feature where instead of falling back to the inbuilt SQLite, I could add a feature where TeMeFI users could explicitly select the internal SQLite binary as the one to use when using TeMeFI. It would of avoided you touching your ROM to enable the features of TeMeFI; and ONLY TeMeFI, so you would still have a dud sqlite binary (only used by shell commands).
Thumbs up on that possible feature.
FYI: I have this config option available for the next release. Some warnings though.

The scripts that use SQLite that are generated with this option on, would be dependent on TeMeFI being installed.

I normally update the version of scripts when I update them, and this part is actually an include which crosses ALL SQLite scripts, which are a LOT. Once a script is flagged as updated,, any saved Favourites become invalidated and wont run. Because of this flow-on effect of updating the version of the include, I have NOT updated the version number. It bugs me, but I too have a lot of favourites that depend on this include.
 

oldman20

Senior Member
Jan 18, 2014
917
67
Hà Nội
Samsung Galaxy Note 9
FYI: I have this config option available for the next release. Some warnings though.

The scripts that use SQLite that are generated with this option on, would be dependent on TeMeFI being installed.

I normally update the version of scripts when I update them, and this part is actually an include which crosses ALL SQLite scripts, which are a LOT. Once a script is flagged as updated,, any saved Favourites become invalidated and wont run. Because of this flow-on effect of updating the version of the include, I have NOT updated the version number. It bugs me, but I too have a lot of favourites that depend on this include.
Oh, Speaking of saved favorites by the way, I tried to find how to add an item to favorites menu but couldn't find it. please just let me know!
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Oh, Speaking of saved favorites by the way, I tried to find how to add an item to favorites menu but couldn't find it. please just let me know!
Its in the second post

My bad in that I have not updated the images, but if you actually read the text, it says (after I correct the spelling on one word....)
...snip...
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.
...snip...

You can edit the menu name and sort order under: TeMeFI Configuration>Manage Favourites>*
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
New Version v1.1.10

The following items are of special interest
  • Compile / update SQLite binary to 3.36.0
  • Option to force use the internal SQLite over the ROM default. TeMeFI Configuration>Default Startup Config>Use Internal TeMeFI supplied SQLite
  • Memory Summary Currently Running>Memory>Memory Summary
  • Improvemets to swap file enable (removed swappiness as its for ALL swaps & broadened priority values)
  • Broadened set swappiness, including enabling a swappiness of 100
  • Hide keyboard better after search. I think newer android re-shows the keyboard once i hid it. ie it worked in earlier Android
  • Banana gets "stronger" the longer he is allowed to dance while waiting for results...

Download: SEE OP!

New Items. within the menu at "TeMeFI Configuration>New Menu Items"

Updated Items. within the menu at "TeMeFI Configuration>Latest Updated Menu Items"
All should be the ones mentioned above.

New "Memory Summary" report
This report pulls together and visually displays a summary of multiple Memory / Swap textural reports.

Some examples:
1. Only Zram
live only zram.PNG
Probably the most common case out there

2. My live with ZRam and a single swap
my live with 2 swaps.PNG
I found that the Zram file on my Pixell 4a, was always 100% full. So I have added a swap file. This was the driver for this report.

3. A test case with 3 swap files and ZRam.
many multiple swaps.PNG

And as usual, clicking on a block in the graph pops up extra info

Enjoy and stay safe.
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
Is there a way to make the doze settings persists through reboots, I have to enter the app and change the settings every time I reboot.
For starters, on my last Oreo phone and my Current A11 Pixel 4a phone, the doze settings do stick after a reboot. You may like to check if your phone/ROM is actually explicitly resetting the doze settings on each boot.

The source for the doze settings change is available, and not only that, the results actually explicitly provides you an example boot script to re-instate the setting on reboot.

How to run a boot script is well beyond the scope of TeMeFI. Search elsewhere on how to create/run boot-scripts, such as Magisk.
 

mario0318

Senior Member
I have a question, and it may be silly or totally just due to my custom rom and system mods configuration... But, given my frequent use of directly downloading apk files through XDA, why is it the TeMeFi apk always struggles launching directly be it from the notification upon download completion, or even just Chrome's Downloads page? It seems to have an issue finding the package manager even thru my systems default file manager. It just simply refuses to recognize Androids Package Manager entirely. I have to resort to using Solid Explorer or other third party file managers for me to be able to select Package Manager as the execution app.

I've noticed with intent Interceptor that TeMeFi seems to send a different type of intent to system than another apk i randomly selected downloaded in the same way thru XDA.

TeMeFi intent:
intent://com.android.chrome.FileProvider/downloads/TeMeFI-v1.1.10.apk#Intent;scheme=content;type=application/binary;launchFlags=0x13000003;end
------------
Action android.intent.action.VIEW
Data content://com.android.chrome.FileProvider/downloads/TeMeFI-v1.1.10.apk
MIME type application/binary
URI intent://com.android.chrome.FileProvider/downloads/TeMeFI-v1.1.10.apk#Intent;scheme=content;type=application/binary;launchFlags=0x13000003;end

Xposed APK intent:
intent:#Intent;action=android.intent.action.SEND;type=application/vnd.android.package-archive;launchFlags=0x1b080001;S.android.intent.extra.SUBJECT=XposedInstaller_3.1.5.apk;end
------------
Action android.intent.action.SEND
MIME type application/vnd.android.package-archive
URI intent:#Intent;action=android.intent.action.SEND;type=application/vnd.android.package-archive;launchFlags=0x1b080001;S.android.intent.extra.SUBJECT=XposedInstaller_3.1.5.apk;end
Apologies for the formatting.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
I have a question, and it may be silly or totally just due to my custom rom and system mods configuration... But, given my frequent use of directly downloading apk files through XDA, why is it the TeMeFi apk always struggles launching directly be it from the notification upon download completion, or even just Chrome's Downloads page? It seems to have an issue finding the package manager even thru my systems default file manager. It just simply refuses to recognize Androids Package Manager entirely. I have to resort to using Solid Explorer or other third party file managers for me to be able to select Package Manager as the execution app.

I've noticed with intent Interceptor that TeMeFi seems to send a different type of intent to system than another apk i randomly selected downloaded in the same way thru XDA.
...snip...
When you download an APK from XDA, it is NOT the same for every APK. Each APK you download can use a different hosting source. The way Android / Your ROM / Browser handles a downloaded APK could possibly vary dependiong on the hosting source. There is nothing I do specifically within the APK (i know of) that would make it behave differently to any other APK. Note, the Intent is sent by your browser, as it is sent before my APK is even installed!

To test this concept a little further, I will TEMPORARILY attach the latest APK to this post directly. Give it a go, and tell me if it behaves differently. I will delete it within 12hrs if you do nnot get back to me sooner to let me know I can delete it.
 
Last edited:

mario0318

Senior Member
It most certainly behaves differently. I had no idea such a thing was the situation all having to do with XDA, links and browser handling being such major factors. Your temporary apk link does indeed launch with the correct intent without a hitch.

You're due both my apologies and a huge thanks for clarifying the crux of what has been a stickler pest on my end with certain apks exhibiting this.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,381
5,073
Sydney
It most certainly behaves differently. I had no idea such a thing was the situation all having to do with XDA, links and browser handling being such major factors. Your temporary apk link does indeed launch with the correct intent without a hitch.

You're due both my apologies and a huge thanks for clarifying the crux of what has been a stickler pest on my end with certain apks exhibiting this.
I actually realised after I posted the above, the download LINK I provide in the OP, actually has two little things that make it possibly a little different to other links you may of encountered before. Including the one I provided above, that worked how you expected.
  1. I upload into dropbox, and instead of using the default link that takes you to a download page (an extra step), I "skip"over that page and download directly from the link (with a manually modified URL). Which may then be handled differently by your browser.
  2. I go through a link short-ner / share provider. How they handle the link or how your browser then handles the redirect, is beyond my control or knowledge of what the heck they do. And again, how your browser handles it.

...snip...
crux of what has been a stickler pest on my end with certain apks exhibiting this.
...snip...
WHAT!?!?! You implied this behavior was TeMeFI specific. This little tid-bit that it was other APK's as well, might of been useful... at least to confirm in my mind it wasn't something my APK was doing differently/wrong.
 
  • Like
Reactions: pocketrule

Top Liked Posts

  • 4
    <SNIP>
    Btw, detach module works for you?
    I tried to detach three apps, one of them it never found and two other reappeared in Google play after just a few hours
    <SNIP>
    The detach module doesn't seem to really work I still end up with YouTube in my play store. The only thing that gets it is titanium backup but then it doesn't last. At least it doesn't update the YouTube but I still don't enable auto update anyway in case it tries.
    <SNIP>
    Hi. :)

    I figured I would reply over here in the TeMeFI thread instead of the Magisk thread.

    The detach scripts in TeMeFI are excellent. :sneaky:

    DiamondJohn gives an example (happens to be YouTube) back in post # 291 on detaching an app from PlayStore.
    Post # 291 - Link

    You can also search this thread for detach and YouTube there is quite a bit about it in this thread.

    DiamondJohn is always updating and improving TeMeFI.

    Cheers. :cowboy:
    3
    Hi. :)

    I figured I would reply over here in the TeMeFI thread instead of the Magisk thread.

    The detach scripts in TeMeFI are excellent. :sneaky:

    DiamondJohn gives an example (happens to be YouTube) back in post # 291 on detaching an app from PlayStore.
    Post # 291 - Link

    You can also search this thread for detach and YouTube there is quite a bit about it in this thread.

    DiamondJohn is always updating and improving TeMeFI.

    Cheers. :cowboy:
    ummm... are you expecting cash or bitcoin ;)

    I have been happily having about 26 apps detached. Mostly Method 2, but of course youtube and youtube music are Method 3. Your mention made me think that maybe its about time to check on these. I haven't had any unruly updates, but I have seen that google do vending updates very VERY often; a feature is in TeMeFI is to see the history of updates, including Vending, which google do not report on in their own history.

    Anyway, I was a little shocked to see that my detachments had multiple fails/warning, but still continued to work. I also found that I couldn't get to re-detach some apps (this is added to my to-do). So, I did re-detach YouTube, and now it also passes all the tests again and does not crash the test page.

    A little concerning was that the test page also had an error in it, before I re-detatched, so thats on the to-do as well.

    And regarding the quotes you have above about others who find the detach fails. For clarity, for others, they are specifically talking about another detaach method, not TeMeFI. Which (ie the other method) is known to be very vending store update sensitive.
    2
    In fact, there was a slightly different convo in Magisk thread where some Magisk modules were mentioned, Detach being one of them

    Anyway, I know for the TeMeFI app. Personally I'm not a fan of detaching (simple disabling Auto Update per apps is good for me) but once again I tested TeMeFI-v1.1.10 and yes, I can successfully detach four apps. It finds YT under the strange name YouTube Language app, but the package name is correct and YT is detached
    Yeah, I got "YouTube Language App" on one of my phones, but that's what is stored in the Vending dB, its not me. More common is just blanks. I thought of breaking out to AAPT, but I didn't want to add any dependencies. The AAPT methods always return the correct name from the APK.

    Its strange that you can get away with simply turning off updates. That is a veeeeeery small part of TeMeFI detach, but alone, it failed for me, and for many others. You dont have anything else weird going on? running the latest Vendor/playstore I assume?

    Looking at your detach list, FYI, I tested using Method 2 (significantly gentler than Method 3) and only youtube and youtube music failed. So All mine are method 2, except those two. To give you some context, when I had all at Method 3, I have had situations where I was using the playstore, and it just disappeared on me. Method 3 triggers an internal crash if the playstore even starts to try and attach any detached apps, which the playstore does not handle or trap, at all. Bad Google ;)
    1
    Hi. :)

    I figured I would reply over here in the TeMeFI thread instead of the Magisk thread.

    The detach scripts in TeMeFI are excellent. :sneaky:

    DiamondJohn gives an example (happens to be YouTube) back in post # 291 on detaching an app from PlayStore.
    Post # 291 - Link

    You can also search this thread for detach and YouTube there is quite a bit about it in this thread.

    DiamondJohn is always updating and improving TeMeFI.

    Cheers. :cowboy:
    In fact, there was a slightly different convo in Magisk thread where some Magisk modules were mentioned, Detach being one of them

    Anyway, I know for the TeMeFI app. Personally I'm not a fan of detaching (simple disabling Auto Update per apps is good for me) but once again I tested TeMeFI-v1.1.10 and yes, I can successfully detach four apps. It finds YT under the strange name YouTube Language app, but the package name is correct and YT is detached
  • 9
    New Version v1.1.10

    The following items are of special interest
    • Compile / update SQLite binary to 3.36.0
    • Option to force use the internal SQLite over the ROM default. TeMeFI Configuration>Default Startup Config>Use Internal TeMeFI supplied SQLite
    • Memory Summary Currently Running>Memory>Memory Summary
    • Improvemets to swap file enable (removed swappiness as its for ALL swaps & broadened priority values)
    • Broadened set swappiness, including enabling a swappiness of 100
    • Hide keyboard better after search. I think newer android re-shows the keyboard once i hid it. ie it worked in earlier Android
    • Banana gets "stronger" the longer he is allowed to dance while waiting for results...

    Download: SEE OP!

    New Items. within the menu at "TeMeFI Configuration>New Menu Items"

    Updated Items. within the menu at "TeMeFI Configuration>Latest Updated Menu Items"
    All should be the ones mentioned above.

    New "Memory Summary" report
    This report pulls together and visually displays a summary of multiple Memory / Swap textural reports.

    Some examples:
    1. Only Zram
    live only zram.PNG
    Probably the most common case out there

    2. My live with ZRam and a single swap
    my live with 2 swaps.PNG
    I found that the Zram file on my Pixell 4a, was always 100% full. So I have added a swap file. This was the driver for this report.

    3. A test case with 3 swap files and ZRam.
    many multiple swaps.PNG

    And as usual, clicking on a block in the graph pops up extra info

    Enjoy and stay safe.
    4
    <SNIP>
    Btw, detach module works for you?
    I tried to detach three apps, one of them it never found and two other reappeared in Google play after just a few hours
    <SNIP>
    The detach module doesn't seem to really work I still end up with YouTube in my play store. The only thing that gets it is titanium backup but then it doesn't last. At least it doesn't update the YouTube but I still don't enable auto update anyway in case it tries.
    <SNIP>
    Hi. :)

    I figured I would reply over here in the TeMeFI thread instead of the Magisk thread.

    The detach scripts in TeMeFI are excellent. :sneaky:

    DiamondJohn gives an example (happens to be YouTube) back in post # 291 on detaching an app from PlayStore.
    Post # 291 - Link

    You can also search this thread for detach and YouTube there is quite a bit about it in this thread.

    DiamondJohn is always updating and improving TeMeFI.

    Cheers. :cowboy:
    4
    ...snip...
    I have to resort to using Solid Explorer or other third party file managers for me to be able to select Package Manager as the execution app.
    ...snip...
    oooo... almost forgot, for file managers, look into MiX by @HootanParsa

    3
    I have a question, and it may be silly or totally just due to my custom rom and system mods configuration... But, given my frequent use of directly downloading apk files through XDA, why is it the TeMeFi apk always struggles launching directly be it from the notification upon download completion, or even just Chrome's Downloads page? It seems to have an issue finding the package manager even thru my systems default file manager. It just simply refuses to recognize Androids Package Manager entirely. I have to resort to using Solid Explorer or other third party file managers for me to be able to select Package Manager as the execution app.

    I've noticed with intent Interceptor that TeMeFi seems to send a different type of intent to system than another apk i randomly selected downloaded in the same way thru XDA.
    ...snip...
    When you download an APK from XDA, it is NOT the same for every APK. Each APK you download can use a different hosting source. The way Android / Your ROM / Browser handles a downloaded APK could possibly vary dependiong on the hosting source. There is nothing I do specifically within the APK (i know of) that would make it behave differently to any other APK. Note, the Intent is sent by your browser, as it is sent before my APK is even installed!

    To test this concept a little further, I will TEMPORARILY attach the latest APK to this post directly. Give it a go, and tell me if it behaves differently. I will delete it within 12hrs if you do nnot get back to me sooner to let me know I can delete it.
    3
    I've tried to download the apk from the OP for about a dozen times. Unfortunately the download keeps getting interrupted if it starts at all. I have no idea what could be the reason but maybe others have this problem too?

    FWIW I've been able to download from the OP of this thread on Android from the XDA app to Naked Browser Pro (and probably other Androidcbrowsers although I did not test all), and also on a Windows computer running Firefox.
  • 95
    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.;)

    TeMeFI v1.1.10
    MD5: ffcfc3386b5a2d18f715bd29cc3b44ea

    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-04-07]

    XDA:DevDB Information
    [APP][TOOL] TeMeFI comprehensive system documentation & action, App for all devices (see above for details)

    Contributors
    DiamondJohn

    Version Information
    Status:
    Stable
    Current Stable Version: 1.1.10
    Stable Release Date / Last Updated: 4 Jul 2021
    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.
    16
    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.