[APP][TOOL] TeMeFI comprehensive system Administration

[DiamondJohn]

PS: It is obviously finding the library dB, as SQLite will create a new empty dB if the file is not found (but the path exists)

 

[Jbro129]

Sincerely, thank you. its my own private bug-bear.

Umm... to get the list of apps? I mean it IS the "library"

The library db file will let me hopefully duplicate the issue. A stack trace is more jibberish than I need to see. And, the error (if you click the bomb icon) would be more targeted to TeMeFI anyway. But, I dont think it will g9ie any more info than "its not valid"

I actually had some more ideas you could check/try so I came back here to post, and just noticed you already responded.

• Check the version of sqlite3 you are currently using
• switch to the TeMeFI internal sqlite binary Config>startup>Use Internal TeMeFI supplied SQLite
• Make a copy of the library db onto your sdcard, then use TeMeFI's dynamic query against it Dynamic DB Query>All Table Data>/storage/emulated/0>/storage/emulated/0/.../library.db>ownership

Actually, you look like you already had a look with another app? which app? and to be clear, its probably not a shell app and so would not be using the sqlite3 binary.

Just had another idea, maybe something else is locking the db all to itself. Its finding the dB, but says it cant open it (my previous assumption is that its corrupt or the sqlite3 is old) I kill the playstore to stop it from stopping me (as a bonus its fun to "stick it to the man" ). I would try a reboot and go into TeMeFI first thing and try again.

Thank you for the response.

As for your ideas:
I selected the 'Use Internal TeMeFI supplied SQLite' and tried again, but now the toast mentioned localappstate.db instead of library.db.
I copied both both databases and used the Dynamic DB Query on them. Inside of ownership in library.db I saw all the table keys and inside of localappstate.db I clicked appstate and found similar data.

I used this SQLite editor app as well as Root Explorers built in SQL viewer.

I tried force stopping the playstore and opening TeMeFI right after a reboot and the issue still occurred

 

[Jbro129]

PS: It is obviously finding the library dB, as SQLite will create a new empty dB if the file is not found (but the path exists)

The moment I first saw the error toast I checked to make sure the database files even existed on my device.

 

[DiamondJohn]

The moment I first saw the error toast I checked to make sure the database files even existed on my device.

Just to be clear, the toast is the old/original error system Its a cut down error message. Its just a "tap on the shoulder". Clicking the bomb icon should give MUCH more detailed info. Ill send you a cutdown script later, so you can actually check which line is causing the issue. (when you clarify where)

Also, as I said, if the db didn't exist, after you rub it once, sqlite3 automatically creates an empty file. Empty, but "a file" ie you will then find "a file"

It is on the first step? ie bringing up a list of packages?

Actually, now I am confused, the first step (by/when/after you click on DETACH: Select Package then Protection Level v6) does not reference the library db???? This is difficult unless you are specific about exactly at which step the error occurs.

 

[DiamondJohn]

...snip...

I used this SQLite editor app as well as Root Explorers built in SQL viewer.

...snip...

I previously had a pretty good on device SQL Editor, but it stopped working on newer android versions, and is no longer developed. Still searching for a replacement, I am guessing you are using MiX as your explorer. I do NOT want to develop my own, but there really seems to be a hole in the market. I have been using SQL 25+years, so have seen many interfaces/features across many platforms, and I dont see what the issue would be. I dont want to build another mouse trap, even though the current offerings seem poor. I think its just that I haven't come across it yet. Its not quantum mechanics; says the guy who hasn't built one... But I do have an app that queries its own internal dB, and that old app could be a good template/feature list...

 

[chaoscreater]

@DiamondJohn - does your Doze profile disable the MotionSensor as well, just like how ForceDoze does it?

https://xdaforums.com/t/app-forcedo...creen-off-disable-motion-sensors-etc.3377694/

 

[DiamondJohn]

@DiamondJohn - does your Doze profile disable the MotionSensor as well, just like how ForceDoze does it?

...snip...

No. It ONLY changes the parameters of the Doze settings that were available back in Oreo. The source code of exactly how/what it does is available for YOU to examine and compare with the other link. Also, I only created 1 of the profiles, all the rest were created by others, that I collected from github or such. I have not read your link, there is already too much to read. Motion sensors are not an issue for me, and reading the OP will explain why it is not therefore included.

If you search the thread, there are recent posts by another user, discussing this exact topic.

 

[chaoscreater]

I was able to fix the wakelocks AnyMotionDetector and DeviceidleController.sensing by fine tuning doze parameters.

Thank you for your support really appreciate it

@varunpilankar - using your Doze profile settings, I'm getting this wakelock "com.android.server.MountServiceIdler" running at over 10+ minutes. This used to be around 3~4 minutes. This is on Android 11, rooted MIUI ROM.

 

[varunpilankar]

Here is my current profile (Updated on 5th October 2022) - I would like to call it varunpilankar-NoMotionDoze:

inactive_to=2592000000,motion_inactive_to=2592000000,light_after_inactive_to=0,light_pre_idle_to=30000,light_max_idle_to=86400000,light_idle_to=43200000,light_idle_maintenance_max_budget=30000,light_idle_maintenance_min_budget=10000,min_time_to_alarm=60000,min_light_maintenance_time=10000,wait_for_unlock=true,quick_doze_delay_to=86400000

Feel free to add it to your app whenever possible. Once again, Thank you for your support! @DiamondJohn

I have just updated the profile, to the one I'm using currently.

Try it out

@chaoscreater

 

[chaoscreater]

I have just updated the profile, to the one I'm using currently.

Try it out

@chaoscreater

Thanks, I'll test it and see how it goes.

I noticed your code is very similar to the one from the section "limbo light doze" of this really awesome article:

Android Doze Tweaks

Do we need more power plants for mobile phones?

tsungi.medium.com

Except that you have this part at the end:

wait_for_unlock=true,quick_doze_delay_to=86400000

Could you briefly explain what that part does? I don't think I've seen this in any other doze profiles that others have provided.

 

[DiamondJohn]

Thanks, I'll test it and see how it goes.

I noticed your code is very similar to the one from the section "limbo light doze" of this really awesome article:

Android Doze Tweaks

Do we need more power plants for mobile phones?

tsungi.medium.com

Except that you have this part at the end:

min_light_maintenance_time=10000,wait_for_unlock=true,quick_doze_delay_to=86400000

Could you briefly explain what that part does? I don't think I've seen this in any other doze profiles that others have provided.

Yes you have. Its part of nearly every doze profile I have in TeMeFI. AND its even explained in the description of parameters that are included in TeMeFI.

 

[bzz11g]

Hi There!
where i can download previous versions of TeMeFi?
Version v1.1.19 not showing all app's in Detach menu

 

[DiamondJohn]

Hi There!
where i can download previous versions of TeMeFi?
Version v1.1.19 not showing all app's in Detach menu

The TeMeFI version has nothing to do with which apps are displayed. It uses code to bring up a list; the exact same code in both versions. If any app is not in the list, then its not attached. Search the thread (or at least read the last few pages)

If you are not seeing an app in the list, then its your playstore data that is lacking. This has all been discussed many times, including the last few pages. We actually had someone complain they didn't find youtube in the list, when i put it at the top of the list (if its attached).

In summary, v1.1.20 is showing all apps available to be detached. ie only apps that are attached. installed or even showing in the playstore, does not mean they are attached.

 

[DiamondJohn]

No, it's not.



This is YOUR doze profile. I've also tried out a bunch of other doze profiles as well. Please point out exactly where in the doze profiles is this part of the code being used:

ummm.. YES IT IS. And the code you have shown as mine is 1000% percent incorrect. That IS NOT my doze profile. I cant believe you are doubting the person who not only has access to the code (and on this method you have access to the script code also), but wrote the code. It is clear that you do not know how to use TeMeFI or what you are looking at. I not only checked to confirm before I made the statement, but I also have been running it for a few years now. I would of thought at least you would ask yourself, how the heck would two parameters have such a huge effect on the doze behaviors?

 

[rodken]

@DiamondJohn Is there a method within the app to disable or at least change the charging starting sound when plugging in device?

"adb shell settings put global charging_started_sound=/storage/emulated/0/Download/Silence.ogg" yields no results.

 

[DiamondJohn]

@DiamondJohn Is there a method within the app to disable or at least change the charging starting sound when plugging in device?

"adb shell settings put global charging_started_sound=/storage/emulated/0/Download/Silence.ogg" yields no results.

Not specifically in TeMeFI. HOWEVER, I actually had started a whole thread on how to do this exact same task. To check without having to ask me, you could also use the search icon in the flyout toolbar (magnifying glass) and searched for "sound"

If you go to settings and filter the results for "sound" you can get a list of the different sounds, including ones not in your settings UI.

And when you say "no results" are you saying that a get shows no change? I also run under root & have the files in a more permanent location.

You may also (but not for charging sounds) be being hindered by another operating behavior of Android. That feature is that, some sounds use a file URI while other sounds use a media content link to the file from the Media DB. I hit this a few years ago, so I use the attached file as one of my many boot script to correct or reinstate when I flash an update or new ROM. I use to build from source, so I tested/flashed ROM after ROM. Its specific to me, and the includes that you care about, probably set up the SQLite location and the MediaDB filename/location. But for the charging sounds, I cover two settings in the script (wireless and wired) and also in the above thread.

I guess I could reuse a lot of the code from the sqlite Magisk module method and my boot script, but, right now (and the past few months I am bogged down in a new feature of TeMeFI, where it records a history of everything you run (user configurable), with the actual results that were returned at the time, so one would have a searchable history, of everything they run AND the results at the time. But I digress, cause Im getting close to finalising it. Also, i would have to know when to use a content link and when to use a file URI and in all ROMs and what sound events are supported, between Android versions, use the same settings tag etc etc etc. To many moving parts. And I already have a solution (boot script) to my personal issue, and this app is all about me

 

[rodken]

Not specifically in TeMeFI. HOWEVER, I actually had started a whole thread on how to do this exact same task. To check without having to ask me, you could also use the search icon in the flyout toolbar (magnifying glass) and searched for "sound"

If you go to settings and filter the results for "sound" you can get a list of the different sounds, including ones not in your settings UI.

And when you say "no results" are you saying that a get shows no change? I also run under root & have the files in a more permanent location.

You may also (but not for charging sounds) be being hindered by another operating behavior of Android. That feature is that, some sounds use a file URI while other sounds use a media content link to the file from the Media DB. I hit this a few years ago, so I use the attached file as one of my many boot script to correct or reinstate when I flash an update or new ROM. I use to build from source, so I tested/flashed ROM after ROM. Its specific to me, and the includes that you care about, probably set up the SQLite location and the MediaDB filename/location. But for the charging sounds, I cover two settings in the script (wireless and wired) and also in the above thread.

I mentioned 'no results' in my previous post as a less draconian way of expressing my displeasure of not hitting paydirt. I would agree that it could be a hindrance within Android and or OOS considering that I am on a OnePlus device.

Coincidentally, I visited your aforementioned thread which brought me back to the magic question.

 

[DiamondJohn]

I mentioned 'no results' in my previous post as a less draconian way of expressing my displeasure of not hitting paydirt. I would agree that it could be a hindrance within Android and or OOS considering that I am on a OnePlus device.

Coincidentally, I visited your aforementioned thread which brought me back to the magic question.

Did you try my suggestions? ie root & covering both settings? This method has worked for me across multiple ROMs, android versions and devices. But I have never had a OnePlus. And, on that other thread, it appears to have worked for others.

Did you explicitly check the setting is being saved, using a get? to see if it was being ignored? That can be done explicitly from within TeMeFI. If it is still failing ie the setting is saved, but it is ignored, maybe check your logcat for any clues when you try and set it.

I do love hearing the road runner every time I plug in my charger. And he has greeted me for a number of years now

 

[LuckyStrike1695]

Hi,

Quick question about using TeMeFi on multi-user env.
I used TeMeFi from the owner's account to detach an app. It worked as expected.
But when using a secondary user account, the app is still listed in the Play Store "available updates" section (making the owner's detach useless since any secondary user can update the app for the whole system).
When I tried to detach it from the secondary user account, it seems to not be working as it still appears in Play Store updates list.

So, how should I proceed to detach an app for *every* users ?
Thanks.

 

[rodken]

ummm.. YES IT IS. And the code you have shown as mine is 1000% percent incorrect. That IS NOT my doze profile. I cant believe you are doubting the person who not only has access to the code (and on this method you have access to the script code also), but wrote the code. It is clear that you do not know how to use TeMeFI or what you are looking at. I not only checked to confirm before I made the statement, but I also have been running it for a few years now. I would of thought at least you would ask yourself, how the heck would two parameters have such a huge effect on the doze behaviors?

Which of the doze profiles listed within the app actually disables doze globally?