yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] DiamondJohn:
Marshmallow is getting old now. I build and test on my personal phones, the lowest of which is Oreo. I dont block people from using it on lower Android, its all up for the user to use at their own discretion/risk.

As for your errors. I would suggest to not change the filenames, and especially not remove the txt or log extensions. Files with no extensions can point to executables that may be a virus. And for some reason, all the carriage returns have been deleted?

Currently installed SQLite3 Location: /system/xbin/sqlite3

Currently installed SQLite3 Version: 3.41.0 2023-02-21 18:09:37

05941c2a04037fc3ed2ffae11f5d2260706f89431f463518740f72ada350866dp

That looks like a recent version, however, if you have used my magisk module creator, I would first start with "bin" as a location over xbin. I have seen issues in the days of non systemless installs of busybox failing with in the incorrect bin or xbn install location.

And the "mm" file, I have no idea what that is. Its not one of mine.

You also forgot to include the test results.

The following appears to maybe your point of failure:

Warning: 2023-05-18 01:57:37 ACT_SQLITE3_TEST_VERSION SQLite3 - TeMeFi - Location and Version WARNING: linker: /system/xbin/sqlite3: unsupported flags DT_FLAGS_1=0x8000001

I dont know this specific error, but, it may have something to do with the xbin location, but looks more like you may of hit a case where the latest sqlite calls methods only available in newer android versions. Its NOT a TeMeFI specific error, and if you search the web, you get links like:

WARNING: linker: su: unsupported flags DT_FLAGS_1=0x8000001 · Issue #5589 · topjohnwu/Magisk

Device: Xperia M4 (E2306) Android version: 6.0.1 (stock) Magisk version name: 2c092ff Magisk version code: 24301 Hi all, I get that WARNING: linker: su unsupported flags DT_FLAGS_1=0x8000001 after ...

github.com

Which mention:

Same with my 2013 Moto G on Nougat ROM. Seems like only happens on Nougat and below as I don't have such a problem on Oreo ROM.
=====================
The issue was introduced with the update of NDK d3d28f0
Here there is a workaround and I think it will be the unique solution.

Maybe running an older version of SQLite may side step the issue. however, I did remove the older compiles of sqlite from my build thread. Here is the oldest one I have for you to try.
[Android Apps and Games] KitsuneFoxy:
I will certainly try the other sql you have given to me. As for the mm file, that's my bad, tapping to fast made me click it. I'll upload the test.

I know Marshmallow is old now, i will probably upgrade the nexus4 with Oreo at some point.

I'm using systemless busybox in magisk, if that's causing errors.

I have no idea about carriage returns or coding android stuff, just the basics. Xbin i assumed is magisks copy thing.

-Edit-

Unfortunately the sql package did not solve the error.
[Android Apps and Games] DiamondJohn:
WARNING!​

I just had a Google Play Store Update on my Android 13 test device that wiped and reattached all my detachments.

However, my daily device running Android11 looks good. Maybe its because I just initialised my A13 device, and it was done with a previous version of the playstore which only now came through. while my A11 devices was always running. The thing against that theory is that the play store on the A13 phone looks sightly different. I'll be watching my A11 phone closely in case it undergoes the same update.

All I did was re-detach the selected apps.
[Android Apps and Games] diehard2013:
what are detachments?
[Android Apps and Games] alecxs:
what "installation sources" most your apps have?
[Android Apps and Games] DiamondJohn:
This is about "detaching" from the PlayStore, to block app updates of a selected app by the PlayStore. Most commonly used for YouTube (Vanced) or to stick to a specific older version of an app, or to hold onto a locally modified APK over the published APK.
[Android Apps and Games] DiamondJohn:
Huh? TeMeFI is a single app, so what do you mean by "most of my apps"?

From PM, That was directed at @diehard2013
[Android Apps and Games] diehard2013:
most from the play store, many from the galaxy app store and a select few from local sources (apk) such as file explorer, etc...
[Android Apps and Games] alecxs:
... and that info is stored somewhere (in packages.xml?) and you can view it yourself in app settings. if you "detach" the installation source from app, you made a "detachment" right? the installation source no longer won't care about maintaining the app.

exactly this is what google probably don't like, so google play behavior obviously has changed and decides to overtake the ownership back again - hence the warning.
[Android Apps and Games] Zoki88:
Hello, i deleted module from Magisk which was used for previous Detach method i was using till recently, rebooted device, cleared cache and storage from play store(someone said here in some post to do that), and everything seemed back to normal, apps appeared on list for updates in play store, so no other detaching methods should be interferring anymore. After that done, i tried to use 3rd method of this app to detach 1 of 3 apps i have for detaching, checked play store, and saw that it actually worked, even if i still got some error (look at attachment), is that error normal to appear even if it worked?

My 2nd question is that is there some rule when should i use which method of those 3 for detaching apps, or can i just use 3rd method for every app? I tried to find similar posts or answers here, but no luck, sorry if someone already asked these and thanks in advance.
[Android Apps and Games] DiamondJohn:
from memory the

/data/user/0/diamondjohndroid.utility.temefi/cache/temefi_runner.sh[641]: 3N: bad number '3N'
/data/user/0/diamondjohndroid.utility.temefi/cache/temefi_runner.sh[643]: 3N: bad number '3N'

Is what I have seen on bad shells, that do not support millisecond timing (ie the N time format, the 3 is for 3 digits, ie 0-999 ms)

What are your results from the detach test?

I dont think it would cause a failure, as its only used on log lines to shop when it was logged, for info purposes. The ms timing is not used on functional lines, just before & after, on info liens.

What ROM / firmware & version of Android are you using? I saw it waaaay back when I first started, many years ago.
[Android Apps and Games] Zoki88:
It works, it's not in play store for update, and i just checked in TeMeFI, it's on list of detached apps, only problem is that same error that appears, but as you explained that error is only about time format on log, then it's all good.

Android 8 on LG H930DS
[Android Apps and Games] DiamondJohn:
Thats NOT what I asked. Thee is a test / report showing if all the steps are working. EVERYTHING "works".... until it doesnt...

RE the 3N error, I remembered later there is actually a fix/workaround for this error built into TeMeFI, if you have Busybox installed.

You can "replace" your firmwares older default handler for "date" with the busybox version. its somewhere like

Magisk>Modules>Promote Busybox Method>Promote or Remove Method>Add One>DATE>Yes

REBOOT and check it works.
[Android Apps and Games] Zoki88:
I tried to find that test in app and here in thread, not sure what or where is it, do you mean CHECK: The Detach of a single package ?

I have Busybox for Android NDK module(1.36.1v) on Magisk. I just did these steps, and got (same) error (attachement), but i'll reboot now device and see if it worked.
[Android Apps and Games] DiamondJohn:
Are you seriously asking if something labeled "CHECK" and is just above where you detach, IS the check?

Always assume NOTHING in Magisk happens UNTIL after a reboot. I even stated so in CAPITAL letters
[Android Apps and Games] Zoki88:
No, i asked if "CHECK" is what you mean by test, because in my previous post i said that i checked the app in TeMeFI and it was indeed there on list of detached apps, but you said that is not what you asked me, so i'm confused what do you mean by test?

I'm sorry, but i seriously didn't see that anywhere. Also after reboot and after using "CHECK" , i didn't see any error appearing, so guessing that it worked?
[Android Apps and Games] DiamondJohn:
Not only is CHECK a synonym for TEST, if you read the first few post of the thread (XDA Rule), you will see that long pressing a menu item, pulls up info on the menu item. And now your asking me if it worked?

The TEST / CHECK is obviously a LOT more thorough than a simple list; which only lists the ones you attempted but may of failed or even broken by a Playstore update. With the 000's of menu items, I obviously would try not to duplicate things with no difference/benefit.
[Android Apps and Games] DiamondJohn:
Well, you got no arguments from me;)

When I first thought of the concept, I was really surprised I couldn't find something similar already:confused:

Ha! I wish there were no bugs. Some issues to note.

Switching to other apps while its processing an action can be "flakey"

Turning the screen portrait-landscape while its processing an action can be "flakey"

Some items are specific to the android version or the ROM you have flashed

SQL Lite is not installed by default on all ROMs. Ironically, I found the Pie version of my ROM (Havoc-OS) did not include SQL Lite :eek:; luckily I build my own ROMs so it wasn't hard to include it back in.:cool:

The issues we did have previously were commonly with root access, that seemed to be related to a beta version of Magisk.

This forum moves sooooo quickly, its off the first page within a day. I am also careful not to use gorilla marketing in in-appropriate threads. But you feel free to mention it when appropriate;)

Carefull, there is a LOT in there, it can become a time blackhole;)

But there currently is no advertising or limitations, so this IS the "pro version". I would see putting it up on the play store as a way to monetize it, but the complexity of what it does and support for the myriad of features/actions would far outweigh any possible monetary gain. Users here are probably a little more skilled than your general playstore user. I saw a review of an app called something like "don't shoot the messenger"and the first review is a kid complaining he didn't get to shoot the messenger :rolleyes:
[Android Apps and Games] DiamondJohn:
New Version!

New Version v1.0.49

Download: SEE OP!

New menu items:

Logcat>Logcats>Logcat Detailed - Old Toybox, No Root

Device Details>Kernel>Kernel CPU All Time in State - Tabulated

Current State>Settings>Generate Set All

Current State>Settings>All

Device Details>Kernel>Kernel CPU All Time in State

A couple of new items are pretty useful, at least for me!

RE "Generate Set All".

Most configurations for custom ROMs are accessible through the get/set settings commands. If you need to do a clean flash, running the generate before you clean the ROM, gives you a simple way to reset a LOT of your tedious manual configuration. For example, I have 3 pages of quick settings, with transparency on the panel, and different theme etc etc. I re-setup a phone to look the same simply by running selected lines from this output. It literally saves hours upon hours of remembering and setting up the phone through the interface.

RE Kernel CPU All Time in State

View attachment 4815399

This is a colourful graph displaying the time in state for each CPU. Its handy when comparing different CPU govs visually. I have seen how one gov favors the first CPU (generally considered more battery friendly) as opposed to another that spreads the load across multiple CPU's. Or how evenly spread the CPU goes between frequencies, or acts like a MIN-MAX function.

The first problem is I only have a single device (1 core, 4CPUs), so I am not sure how it is going to work with these multi core (2 or more cores with 8+ CPUs, etc etc) devices. Sorry.

The second problem is that when I first started and coded the feature, I used a file that contains all the cores timings in a single aggregated file. I have since found that this file is sometimes lacking details of a CPU, and it doesn't align with other reports. I have since found other files (individual for each CPU), but I had already done the work:mad:. Maybe a future release, but the existing one isn't bad.

NB: RED means it has sat at the frequency for the longest, GREEN means average time, and BLUE means the least.

Changes

fix some IFS and cut scripts

include the errors in the saved off output
[Android Apps and Games] DiamondJohn:
New Build!

New Version v1.0.50

Download: SEE OP!

New menu items:

TeMeFI Configuration>Difference Between two TeMeFi Logs

Changes:

added file compare (see above new menu item)

removed non-java media scan (it only works on old versions of android)

TeMeFI About logo

Re-Enabled "Ignore App Wakelock". I can not remember why I disabled it, but it looks right.

Added a few permissions to the set permissions methods
[Android Apps and Games] Fahrialubis:
Bro, this app should put with unoptimized battery? Then can i editing temefei doze? I mean like editing with profile? Or maybe if i can create my profie its looks better?
[Android Apps and Games] DiamondJohn:
Sorry, but I can not understand what you are asking:confused:. Below is some responses in an attempt to understand. If you haven't already, maybe write it in your own language, and then include a google translation or such.

I have no idea what you are asking here.:confused:

Firstly, its not TeMeFI that is doing doze, its your android OS. TeMeFI is only adjusting the parameters that doze uses to make a decision on when to switch states. In regard to editing, see my response below.

TeMeFI generates an example script which you can copy and save and then use any text editor to change the parameters. Creating a GUI to edit each individual parameter is well beyond the scope of this project and the interface of TeMeFI. Doze is only one of many many features, and what I think you are asking for would be a completely separate app in itself.
[Android Apps and Games] Fahrialubis:
Yeah i mean some app like greenify or naptime who need to be unoptimized, so this temefi its just script its means doesnt need any thing to keep running correctly right?
[Android Apps and Games] Fahrialubis:
What happened?
[Android Apps and Games] DiamondJohn:
To work that out, I will need a copy of:

1. the file explicitly named in the error message, directly after the error has occurred. i.e. /data/user/0/diamondjohndroid.utility.temefi/cache/temefi_runner.sh. You can also easily access this script either by long pressing the middle section where the text is in the menu/icon bar, or clicking the menu and selecting the second last icon (on the right)

2. The results from

dumpsys deviceidle;

Which can also be retrieved from TeMeFI itself, under the menu "Dynamic Lists>Dumpsys Service Calls>SVC: deviceidle"

TeMeFI builds the scripts (ie temefi_runner.sh) on the fly depending on which menu item you have selected, some of which are further confounded as they are also built dynamically based on your device and/or configuration. However, the menu item you have selected I think should generate a consistent script between devices, I think. I did look at the script generated on my device, and although it looked "ok" (especially at line 85), I did see room for improvement in that area, which may possibly alleviate the issue you have experienced.
[Android Apps and Games] DiamondJohn:
You are correct that TeMeFi does not need to be running in the background, so any adjustments made will stick, even if you kill it or even if you uninstall the app. The only exception here is that some adjustments made by TeMeFI are reset by the device on a reboot. For example, when I tested the doze setting adjustments, these were reset by my LOS ROM on a reboot, back to the original settings. I even found that the doze settings are reset in a delayed fashion so that they would need to be set a few minutes after the reboot actually occurred (and this is reflected in the script it generates for your).
[Android Apps and Games] DiamondJohn:
I brought these from another thread as they were OT for the other threads.

See the above post to help me decipher why your doze graph is screwed. https://xdaforums.com/showpost.php?p=80506875&postcount=128

I am running Oreo Havoc-OS and it is working correctly. I am pretty sure I have also run a Pie version of Havoc-OS and it worked fine for me. The above source files will help. And to be clear, modifying your doze settings should be done with Havoc-OS's built in feature not using TeMeFI.

Yes, they are the same. But I suggested you to ask in a Magisk thread, as that is the correct place to ask and seek help on service.d It is very off topic for the thread you posted the question in.
[Android Apps and Games] DiamondJohn:
New Build!

New Version v1.0.51

Download: SEE OP!

New menu items:

Currently Running>Battery History Graph

Changes

Very small adjustment to the code for doze graph

The new battery history graphs have 4 variations

0. Single block colour

View attachment 4862791

1. four block colours. red (low), orange, blue and green for high

View attachment 4862793

2. Blended coloured

View attachment 4862797

3. A blended colour based on the discharge rate. ie the faster it discharges it will be red, orange, blue and green if it is flat or charging up.

View attachment 4862795

It also handles a reboot.

You can also write out the file, and view it on your PC. If you view it on the pc (this also goes for the Doze and the memory graphs), when you hover your cursor over a point it will show you the value and the time that it occurred at. Or if you click on a part of the graph, it will show it as a pop-up.
[Android Apps and Games] TiTiB:
Thanks again...kinda. ? Every time I open this app it sends me down a rabbit hole of discovery and further investigation that usually ends up with me saying, "Whaa? it's that time *already*?!"

I have a question about the app's orientation (I use my tablet 'upside down'), and why it sometimes flips to my correct (upside down) orientation, and sometimes not. It seems to *not* flip while it's performing operations.

I wouldn't normally ask, but I'm preparing an email template that I intend to send to devs whose apps won't flip 180° without using 3C's 'Sensor Orientation' setting applied to them, and having some insight will make me better prepared.
[Android Apps and Games] DiamondJohn:
Your not the first.https://stackoverflow.com/questions...-the-screen-is-not-counted-as-a-config-change

Answer 3 (including the update) may help understand or even solve the problem, I haven't tested it.

As for "sometimes", I will take a guess that if you flip to landscape slow enough, and then to reverse portrait slowly again, the step in between will allow it to trigger a re-orientation event, between the two portrait modes. But that's just a guess. If you flip between one landscape to the revers landscape, the activity quickly flashes into existence, ie it does not get killed re-created.

For me, I have to admit, rotation/re-orientation is always an after-thought when I build apps. Often I don't even allow it :p:. Its problematic to program, as instead of a simple "resize" event, the activity is basically closed and re-started.
[Android Apps and Games] DiamondJohn:
I just had a "play" and I could not get it to respect reverse portrait (and stick). Reverse landscape was a no-brainer (ie it does it now). So I checked a sensor app, and I found that even it did not respect reverse portrait. It then occurred to me to check the settings app within the ROM. It does not support reverse portrait. So, to me, the OS does not support it.

Does your OS's settings respect reverse portrait by default?
[Android Apps and Games] TiTiB:
Yes. I don't recall using an OS that doesn't, and it's just a few apps that irritate me; Dictionary.com's, for instance. It opens in its normal 0° orientation then switches to 180°, tap the search box and goes back to 0° then 180°, type in a word and hit enter, 0° then 180° again. It switches around on every user input, and it's annoying as hell. BTW, it will go 180° without third-party app intervention, but also doesn't change its behavior with such intervention.

---------- Post added at 08:00 PM ---------- Previous post was at 07:18 PM ----------

So, removed "From a programming viewpoint it is easy to do." from my email.

Thanks for the link. I don't understand all of it, but enough to improve my 'complaint email' and add some correct terminology.

I tried rotation/re-orientation with the irritating Dictionary.com app and nothing changed, but I'll keep it in mind when I encounter this 'problem' in the future. I put *problem* in quotes because it's a key part of my e-mail below. BTW, the 'physical disability' part is a lie, the truth is that I have a preferred way of using my tablets (power plug on top, case cover-flap easy to grip) and actually have a 'mental inability' to see why anyone would hold their tablet in any other way.

I realize that the chances of an email of this sort having any effect is slim to none, but it will make me feel better.

"Accessibility Issue — Screen Rotation

Please have your programmers add 'screenOrientation="fullSensor"' this should allow all screen rotations/follow device rotation. From a user viewpoint it is a limition that, either due to poor design principles, or simply oversight makes your app impossible to use without a third-party app to correct.

Because of a physical disability I have to use my tablet 'upside down', which requires an app to rotate 180° for it to be usable. Unfortunately, there is not yet an accessibility setting for Android to override an app's inability to rotate all four ways, so it is up to app developers to correct this oversight.

Thank you"

...and, Thank *You*
[Android Apps and Games] DiamondJohn:
I have added the fullSensor line to TeMeFI, but i cant test it, as my ROM/device does not support reverse-portrait (I have 3 devices which are all exactly the same:silly:). I'll upload a test build and PM you a link so that you can test it.
[Android Apps and Games] TiTiB:
Tested and PM'd you.
[Android Apps and Games] DiamondJohn:
AAAAArrrrrggggggghhhhhhh:mad:

My ROM does support reverse landscape, HOWEVER it is turned off by default!

I turned it "on", and TeMeFI (kind-of) supports it already. Problem is I currently have some code that "breaks" it while it is building a menu (it forces normal portrait if its any kind of portrait) , and a few other places.

Have you checked what is in your settings? An app can dummy it up based on the gravity/accelerometer sensors (which is what I was trying to do), which may explain why it only works for you in some apps.

Have you checked that you have allowed ALL rotations? For me its under "Settings/Display/Rotation Settings"
[Android Apps and Games] DB126:
FWIW - absolutely no rotational issues as described above on four devices I grabbed at random:

- stock Moto G7 (unrooted Android 9)

- stock Onn 8 (unrooted Android 9)

- stock Samsung S7 (unrooted Android 8.1)

- 3rd gen HDX (unlocked w/Lineage 14.1; Xposed module stabilizes rotation)

I have other rooted devices running a variety of ROMs ranging from Android 5 to 7.1. I'll tinker with those as they come to hand. On the surface this appears to be device/ROM/setting/tweek related and, *perhaps*, less of an issue with contemporary Android builds (which I rarely root) as all of the sampled stock devices/roms from different vendors performed flawlessly.
[Android Apps and Games] DiamondJohn:
Thanks, but I actually found that after I turned on reverse portrait on in my ROM settings, I had code that would explicitly (and incorrectly:o) force the rotation to standard portrait while an action is running (and possibly while its building a menu, I say possibly as I am now running a fixed version and can't remember all my fixes). So it would flip back and forth.

The fact you did not notice issues, confirms a little stronger that it was (mostly) a ROM/config issue. So thanks.

I am running a new build with the issue I described, fixed. And will release it soon.:good: So don't bother tinkering, I think it is/should be sorted.
[Android Apps and Games] oldman20:
Seem long time to update! 😌