yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] egoist6:
i have been using vjtoggletoday as well for hiding the buttom-bar and the top-bar separator line. but from time to time the buttom-bar and the top-bar were re-appearing - so i was hoping to find a more stable solution. i am using now dcinobar which only hides the buttom bar
[Windows Mobile Development and Hacking General] pmorganii:
did you ever find a resolution? I found this site...have not tried, but you may want to take a look. (http://www.codeproject.com/KB/mobile/PPCColorConfig.aspx)
[Xiaomi Mi 11] GUARDIANBD:
Hi Team

Anyone noticed that the main camera has a lot focus issues on faces?

Background is on focus while the faces aren't.

Any way to upgrade Camera firmware only?
[Xiaomi Mi 11] PandaKiller:
I notice focus issues on the main came that star a few days ago. To fix them, I need to shake or give some kicks to the phone in other to solve the issue...

This may be caused by some drop, however, I always use the TPU case.
[Xiaomi Mi 11] GUARDIANBD:
Same here my phone is well protected..
[Xiaomi Mi 11] Pho3nX:
What is your ROM / Region ? 12.X.X.XX / Global-EEA-CH-IN ?
[Xiaomi Mi 11] GUARDIANBD:
12.5.1 RKBEUXM
[Xiaomi Mi 11] Sage:
Got the same issue here. Apparently there is a fix on 12.5.4
[Xiaomi Mi 11] GUARDIANBD:
No update yet...
[Xiaomi Mi 11] Pho3nX:
How i can test for help you ? I'm on MiuiMix 26.6.23 (MIUI 12.6)
[Xiaomi Mi 11] PandaKiller:
This seams a hardware problem, I have concerns if they can compensate it by software.

The issue semana to me that the focus mechanism is get stuck, maybe by the lac of power, and only some kicks help do put the lens in the right position...

Can anyone confirm about the fix for 12.5.4.
[Xiaomi Mi 11] Sage:
Don't think it's a hardware issue as I don't get the problem with other camera apps.. though not sure they use all the lenses
[Xiaomi Mi 11] Pho3nX:
Take the Google Cam from BSG MGC_8.1.101_A9_GV1j_snap.apk (org.codeaurora.snapcam)

+1 Google Cam is more stable for pictures and produce better quality. Not an Hardware problem
[Xiaomi Mi 11] Asnamus:
Hello . I started having main camera focusing issue.

When it zoom close subjects its fine and than when it zooms distant subject it becomes blurry .

So when I shake the phone or make a tap it removes blur and catch the picture good.

Should I replace camera lens , sensor .. or it might be hardware ?
[Xiaomi Mi 11] friscoboi:
I just got the phone. Focus on people is always bad. No recognition. I have to switch to Portrait mode manually to get good shots of people.

Main camera also has focussing problems with flowers.

I expected more than this...

My Huawei used to always regognize people.
[Xiaomi Mi 11] blazion56:
I'm honestly in the same boat. After buying a flagship xiaomi phone and having to slap or shake the camera for it to work properly is very disappointing definetly my last xiaomi phone.
[Xiaomi Mi 11] obertscloud:
You must send feedback send the feedback Id number to https://t.me/joinchat/3Sgh-WWgxRg3ZWM1

Plus screenshot of your about phone they will help everyone fix it
[Samsung Galaxy A50 Questions & Answers] MordenStudios:
At the moment I'm trying to port Halium 9.0 to the Samsung A50

It worked well until I entered 'make halium-boot'.

There I have the Error: Unrecognized Property "Vintf_Fragments" to get

Log: click here

Repo List and device specific things: click here

( all repos are for the porting required )

All patches of Halium 9.0 have not yet

transferred (but were patched before the compilation)

I'm posting this on XDA because in the Ubports Forum no one answers me

( I used a Android 10 device tree because i didnt found anything others. If thats the Problem Plesse tell me )

( Sorry for the bad English )
[Samsung Galaxy A50 Questions & Answers] sadatdaniel:
Hello, did you progress further?
[Samsung Galaxy A50 Questions & Answers] MordenStudios:
Yeah im i found out that there is Halium 10

Im now working on it :)

Github: https://github.com/AnaxMorden/Halium-10-Samsung-a50
[Samsung Galaxy A50 Questions & Answers] sadatdaniel:
I know it's not an easy job to do. But mate, if you really succeed it'll be amazing! Is there any estimation about when you might be able to release it?
[Samsung Galaxy A50 Questions & Answers] MordenStudios:
Just Not I'm having a hard time estimating my time right now but I hope to get it done as soon as possible.
[Miscellaneous Android Development] DiamondJohn:
I built the latest stable SQLite3 binary for ARM devices. I built it as I have an app that I requires it, and distribute it with my app TeMeFI , as a lot of people asked to not have to install it as a separate step. TeMeFI app does a LOOOOOT of SQL,

To use this on your device (RO devices), I *think* the easiest way is to install the SQLite3 module from the magisk module repository, and simply unzip the contents in the attached file, and replace the binary that is in /data/adb/modules/sqlite3/system/bin/sqlite3, set the owner & group to ROOT and permissions to 755

Alternatively, you could use my app TeMeFI, which also includes a menu item to create a Magisk module on the fly.;

Please feel free to use and distribute any of these binaries, without any attribution, or feeling you need to get my explicit permission; Spoiler content hidden.

OR you could build it yourself using the simple instructions I followed at:

GitHub - stockrt/sqlite3-android: SQLite CLI and Library build scripts for Android

SQLite CLI and Library build scripts for Android. Contribute to stockrt/sqlite3-android development by creating an account on GitHub.

github.com

I used the latest stable NDK

The MD5 of the zip file (not the binary) for v3.45.02 is MD5: 4DB77068958955DA2F3C3AAF9A7EDD65

Architectures included are:

arm64-v8a

armeabi-v7a

x86

x86_64

But I only test the ARM64 based binary.

Enjoy!
[Miscellaneous Android Development] rodken:
@DiamondJohn What would be the easiest or best method to keeping Sqlite3 updated after flashing the Magisk module, unzipping the contents in the attached file, and replacing the binary that is in /data/adb/*?
[Miscellaneous Android Development] DiamondJohn:
I do not think I understand exactly what you are asking me?

Do you mean?

Update for this release? Which I described above, and you a have re-iterated... so it cant be that?

Updated for the next stable release available?

Get a new stable build as soon as the new source version goes stable? kind-a the same as item 2...

As you can see by the above questions, I am really unsure of what you are asking.

My best guess is you are asking how you could get the next release, when it is released (i.e. item 3). And my answers for that are

"Keep an eye out" on the web in places like XDA, in case someone does a build and release it publicly like I did here.

Check https://www.sqlite.org/download.html for when they release a new stable build. Spoiler content hidden.

Follow the steps (like I did) in the links of the OP and build your own. You still need to watch out for when a stable version is released of the source.

Hope that someone in a project that you are following or have an interest in (I see that you saw my TeMeFI post ;) ), is doing the above and makes a post like I did above.

Hassle...err..I mean contact/request the current builder of the SQLite Magisk module to do an update, when the update is available.

As you can see in my post in the TeMeFI thread, people are including really old releases on ROMs they label as "stable", even though their SQLite self-destructs. More ROMs these days do not even include an SQLite binary, for example my stock Pixel 4a! Remember, this binary is NOT the android internal SQLite driver as used by java, but is only used by the shell. Carrying this idea further, updating this binary, will not upgrade your ROMs SQLite, only the shell.

While writing the above, for item 2, I checked myself, and they have released a new stable build! v3.36.0 On their page, they have a link for a "pre-built" android binary, but I couldn't find a simple binary file (like in the zip of the OP) ready to drop onto a device (thats what I would call "pre-built") But as you can see in the table of my TeMeFI post, people are running (including me on my Oreo device) older builds without issues; other than the guy running the "stable" pie ROM;) Although, I choose to keep my Oreo device with the older SQLite as a test harness when building TeMeFI so I don't take advantage of an SQLite command only available with a bleeding edge SQLite release.
[Miscellaneous Android Development] rodken:
@DiamondJohn Are you keeping the attachment in the OP updated or would I have to heed your advice and watch out for when a stable version is released of the source even though my current SQlite3 is at 3.33.0 as of 08/14/2020?

Disregard, it turns out that after flashing the module and replacing the binary with the file attached from the zip in the OP, the changes do not survive reboots. The device reverts back to the original binary file. Nevertheless, I am good-to-go until further notice.
[Miscellaneous Android Development] DiamondJohn:
I do not plan to actively maintain a build, you have to take your chances with freeware. I do know that @hinxnz also built his own SQLite binary from source (and also supports x86) for one of his projects maybe drop a hint of an SQLite update on his thread, and kang it from him ;)

Something strange is going on, because it makes no sense to me, and is not acting the same way for me on two devices. The issue is beyond the scope of this thread, so you would be best to take it to a Magisk specific thread. As it should work, and should not be overwritten on boot. I mean, where is it keeping a copy of the old file?!?!

On a side, why are you so concerned with SQLite3 for the shell? Do you use a lot of boot scripts? I personally have MANY MANY boot and maintenance scripts that rely on SQLite, in addition to my TeMeFI project that uses SQLite in the shell heavily.
[Miscellaneous Android Development] DiamondJohn:
PS: the change log is at

SQLite Release 3.36.0 On 2021-06-18

The other thing to remember, we are running a cut-down version of SQLite (these change logs are for full Unix/Linux/Windows builds) So, some of the changes would have nothing to do with an Android build.
[Miscellaneous Android Development] DiamondJohn:
PPS: I found the history of releases at: https://sqlite.org/chronology.html

They appear to do stable releases every month! Yeah, Im not keeping up with that!
[Miscellaneous Android Development] rodken:
I maintain quite a bit of boot scripts that use shell independently. Therefore, I was relying on SQLite for experimental purposes and not solely for anything else.

I would have to agree that my concern/issue is possibly a Magisk and/or ROM issue.
[Miscellaneous Android Development] DiamondJohn:
FYI It built successfully, and seems to run... it will be in the next TeMeFI release ;) if it continues to work.

PS: In all my boot script I use an include with an explicit path to SQLite3. By doing so, I can change all my boot scripts SQLite version, simply by changing the path in one place. Maybe a workaround for you since Magisk/ROM is playing up.
[Miscellaneous Android Development] DiamondJohn:
I have compiled a new 3.36.0 binary, but have yet to update the OP, if you want a copy and cant wait, ive included it in the latest release of my App TeMeFI

https://xdaforums.com/t/app-tool-temefi-comprehensive-system-administration.3806260/post-85278641
[Miscellaneous Android Development] DiamondJohn:
Updated to v3.36.0
[Miscellaneous Android Development] DiamondJohn:
oops... the attached files failed. Corrected now.
[Miscellaneous Android Development] rodken:
I suppose that there is no further use for the SQLite Magisk Module after using the updated version of TeMeFi?
[Miscellaneous Android Development] DiamondJohn:
If ALL your shell scripts using SQlite are done using TeMeFI, then even the previous versions did not need to use / have the Magisk version installed. Ever since I first started shipping SQLite with TeMeFI it was coded to fall-back to the internal SQLite, if it wasnt fond in the ROM (or through Magisk)

However, the one case where a few people will need the Magisk module explicitly, is for x86 architecture. The one I build and ship with TeMeFI is only for ARM devices. Oh, and the one in this thread is also only ARM devices.

The latest release of TeMeFI has the new option whereby you can explicitly choose to use the SQLite shipped with TeMeFI over the ROM or the Magisk installed one, which is probably older/lower version.
[Miscellaneous Android Development] edgarf28:
Are your releases compiled for armeabi-v7a or arm64-v8a?
[Miscellaneous Android Development] DiamondJohn:
I run them on both a 64b Pixel 4A running A11, and also a 32b Samsung S4 GT-I9506 (2013) running Oreo.

test method is to install the TeMeFI app I built and distribute here, and set the use internal sqlite feature, to force it to use this compiled one, and then run one of the many sqlite based scripts. Its only x86 that I think it would fail on, but its easy to test, You could also simply copy it to your device and explicitly test it in a temp folder.
[Miscellaneous Android Development] DiamondJohn:
oooo.... the next release is "pending".... https://sqlite.org/chronology.html
[Miscellaneous Android Development] DiamondJohn:
They did two releases in quick succession. I built the first one, and was suprised when the resultant binary jumped from about 500k to 2500k???? I tested it and could not find a flaw. They then did a release soon after, and when I built that i was expecting it to go back down, but it did not...

Anyway, I have updated the OP to include the new latest build. v3.37.2

enjoy.
[Miscellaneous Android Development] DiamondJohn:
ooo almost forgot, I also updated the NDK (ie compiler) to the latest stable for this new build.

And to be clear, even using the previous NDK resulted in a larger binary.
[Miscellaneous Android Development] DiamondJohn:
Had another look into why the file size had increased, and found I could simply change one line of code, and it would generate an SQLite for ALL architectures.

MD5 of the ZIP is : 09C3E996A635FF0ED63D65755D62F117

It includes SQLite3 binaries for:

arm64-v8a (64bit arm device, like mine)

x96_64 (Intel 64bit)

x86 (Intel 32bit)

armeabi-v7a (32bit arm, like most now older phones)

Use the technique in the OP to install/replace to the default SQLite magisk module, and take the appropriate binary from the zip, and set the owner & permissions as below.

View attachment 5505323
[Miscellaneous Android Development] Noob9496:
@DiamondJohn can you update to version 3.38.5?
[Miscellaneous Android Development] rodken:
Have you tried to install/update on your own via Termux?

pkg update sqlite
[Miscellaneous Android Development] DiamondJohn:
Hey, did you read that I had a new compile from the TeMeFI thread? Out of interest, which one are you interested in? I have kinda held back as I now have builds for

arm64-v8a

armeabi-v7a

x86

x86_64

Not everyone runs Termux. I for one do not run Termux. And I will be surprised if it does have a build of the latest code. But thats just purely a guess. Have you checked which version it downloads?
[Miscellaneous Android Development] rodken:
3.38.5
[Miscellaneous Android Development] DiamondJohn:
can you also get a curl binary from Termux?
[Miscellaneous Android Development] DiamondJohn:
Updated the OP with 3.38.5
[Miscellaneous Android Development] Noob9496:
i want to flash systemless using magisk module
[Miscellaneous Android Development] rodken:
Quite possibly, since one can install the curl package via Termux.
[Miscellaneous Android Development] DiamondJohn:
Actually, thats another question. When you download using Termux, where/how does it install it? And to be clear, my download zip also still requires the pre-built/installed magisk module. I dont wanna be supporting an SQLite Magisk module as well. Magisk has too many builds put up for canary, which many people run; I am still on stable.
[Miscellaneous Android Development] DiamondJohn:
I have another script thread for downloading and combining Hosts files (HUGE files). I currently suggest using another magisk module to get curl. However, I personally have kanged it from the now defuncted Vanced installer APK, and run that on my device. Havent requested permissions yet, so for politeness sake, I havent released an update of that script with the kanged binary.
[Miscellaneous Android Development] Noob9496:
Thank you 😀
[Miscellaneous Android Development] Noob9496:
Unfortunately don't work. I add arm64 version to magisk module but don't work.
[Miscellaneous Android Development] Noob9496:
Version 3.37.2 work.
[Miscellaneous Android Development] Noob9496:
I'm so sorry. My bad. Work.
[Miscellaneous Android Development] DiamondJohn:
New build is up v3.39.00 Which is the latest available, that just came online in the last 24hrs or so.

I also remembered to change the thread title to match the SQLite version.

It says there is about a 1.5% speed improvement (in addition to functional improvements). I did a quick ONE off test between the one build before and this one, once. And it went from taking 5.242 seconds down to 4.901. That's a 6.5% improvement, and also includes a heap of shell code, which wouldn't of changed. But dont forget, it was simply a one-off test.
[Miscellaneous Android Development] Noob9496:
Can I make magisk module with this sqlite3 and share it? After flashing this sqlite3 version, the phone sped up considerably. I don't know if it's a placebo or if it really works.
[Miscellaneous Android Development] DiamondJohn:
from the OP

Thats a yes! Were you being super cautious / polite? or should I somehow re-word the OP to make it even clearer?

I dont expect attribution or wish to restrict any use of the binary, as it is 100% simply a mechanical build for me, following the instructions that I linked to. It takes a little time, but not enough to claim any attribution for me. No brain, just a little time.

As for speed. it should logically only make a difference for shell scripts that use SQLite. NB: Many apps could use shell scripts instead of Java. SQL Accessed through java should be the same. However, if it feels faster, that is in some ways better than measurable benefits. If it was the other way around? ;) Also, note the excessive use of the word "should".

Apart from speed, there is also a LOT of new functionality in the last few releases, and the existing Magisk module (last time I looked) was VERY old. And with the different architectures, there is room to target the install for all devices, not just ARM (like i think the current one is).
[Miscellaneous Android Development] rodken:
Is it safe to say that most, if not all modules should be set at the same configuration?

-- I've noticed that most of my other modules are set at different permissions, e.g., '750', '777', etc.

-- In light of the fact that '644' is commonly used, I suppose that '755' would be somewhat of the new norm?

-- In general, users should never use 777 or 776 on any file or directory without explicit need to?

-- There are cases where chmod 777 actually breaks functionality.
[Miscellaneous Android Development] DiamondJohn:
755 is explicit to executables. If its simply a data file, it does not require executable permissions, so 644 may be what that is needed. its a file-by-file basis. To wrap my head around the numbers, I use the file explorer MiX, and not just for this, I think its brilliant.
[Miscellaneous Android Development] rodken:
+1
[Miscellaneous Android Development] DiamondJohn:
New build is up v3.39.1 Which is the latest available. Came online 2022-07-13​

Note: its changes are items 9+ in the linked change-log below. The ones below (ie 8 and below) are from the previous build.

SQLite Release 3.39.1 On 2022-07-13

sqlite.org
[Miscellaneous Android Development] DiamondJohn:
whoops... I forgot and have now updated the MD5 of the new version zip file in the OP. I also found that I had the wrong version number, even for the previous release. 🤢
[Miscellaneous Android Development] DiamondJohn:
Just an FYI. I am in-process of adding a method in the next TeMeFI release, to create an SQLite magisk module, on the fly, based either off the download from the OP of this thread or a user supplied specific sqlite build. That way as new builds are made, it will be simple to refresh/update to the new build.
[Miscellaneous Android Development] Noob9496:
Downloads for : -Android- Utilities | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

I made a module with sqlite3 compiled by you. I added thanks and information that you compiled it in the Readme.md file
[Miscellaneous Android Development] DiamondJohn:
Well, you actually made 6!

I know that one can run an install script in a magisk install zip, and thereby have a single install zip, that will install the correct binary for each of the different architectures. Such a single magisk ZIP may be a even better solution. And an option for those that do not install and run TeMeFI .

My TeMeFI script will depend on the ZIP name (only the version number changing) and structure, so you could even get your install zip to download the latest version. From your own upload, I dont think XDA is built as an easy repository. I was thinking of having the option to download the latest, but I didn't want to do the whole upload to another repository. Also, if someone else takes over, it would be a smoother transition.
[Miscellaneous Android Development] DiamondJohn:
New build is up v3.39.2 Which is the latest available. Came online 2022-07-21​

Note: its changes are items 16+ in the linked change-log below. The ones below (ie 8 and below) are from the previous build.

https://sqlite.org/releaselog/3_39_2.html
[Miscellaneous Android Development] J.Michael:
I run 3.39.2 arm64-v8a in a terminal (jackpal), get a "sqlite>" prompt, and I can't see what I type -- as I press each key, it is not echoed.

Am I missing a command option?
[Miscellaneous Android Development] DiamondJohn:
Not much info to respond to. t the VERY MINIMAL, I would expect to see the commands entered, and how you know/proof you are running v3.39.2. ie your insta,lation. If you are getting no response, how did you check the version?

What it sound like, is more of a terminal UI interface than an SQLite3 issue (if it is not a user error) or a user issue. Well beyond the scope of this thread; this is NOT an SQLite use & support thread. NB: I didnt code SQLite3, I only compile it, and use it. seriously use it.

Secondly, I never use the interactive mode personaly, so no experience there, except by accident. I normally issue complete commands in a single line. Have you tested using on a single line? Also have you tried my TeMeFI app?
[Miscellaneous Android Development] DiamondJohn:
OK, I couldn't resist testing, or avoiding doing what I should be doing...

Below are the checks what I would see as an absolute bare minimum "shake down". I am running A11 Bliss Official Custom ROM on a Pixel 4A, I have created / installed SQLite3 as a Magisk Module, which is a feature/function in the yet to be released, next TeMeFI release. In the screen-shot, I have coloured my input in blue to make it clear what I typed in as opposed to what it returned. I used TermONEPlus