yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Not sure that I got what you need, but I'll attach the file. It seems like I had to start the adb logcat command before causing the problem in order to see it in the log. There are some interesting lines in the log, but it's possible you need me to filter it better or have a bigger buffer.

I'll see about flashing official soon. Maybe you will see something pertinent in the log before I do that. Thanks.

EDIT: It doesn't show that I've attached the file, even though it shows it once I select it from my computer. It is called log.txt. Something wrong with that file type?

EDIT2: Googled and it says that it's most likely something in the text that makes it not actually attach. I could put it in-line here, but it's fairly big. Let me know if you know the right way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Try zipping it
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Good idea about zipping, @temporarium. But I haven't done that yet. I have learned some things...some strange things.

1. I did install official Lineage 20, replacing your rom. I can connect to the Tmobile Home Internet (let's call it THI). But in the list of visible SSID's under Internet, it shows there after a few others, but it does not show that it is connected (it doesn't show that any are connected, but THI actually is). If I pulldown from the status bar, Internet DOES show it as the connected SSID. It will NOT show it in Saved Networks, so if I switch to another SSID and then want to connect to THI again, I have to reenter the SSID. It never stores it in Save Networks.

2. I have stock Android 10 (Q) on another Essential phone. It is a little better but still strange. After connecting to THI, it correctly shows at the top of the list of SSID's as connected. It also shows in Saved Networks. But! If I click it there, it shows that it is not in range, and forget, connect, and share are the options. What?! If I click connect there, it does do it, but it takes maybe 15 seconds.

3. I have official Android 11 Lineage 18 on a Leeco device. I think Android 11 may be the latest stable release for that device. Everything is perfect there...it connects fine, it is in both the list of SSID's and in Saved Networks. Nothing unusual at all. (If Lineage 18 or 19 official exists for Essential, I could try it..but maybe that's unnecessary).

4. I have more Android devices, ranging from Android 7! to 12, and they all connect fine to the THI.

I haven't put your optimized rom back on yet. It's possible that it works the same as what I described in 1 for official Lineage 20. I could have been misled when THI did not show as connected under Wifi SSID's. But I really think that it did not connect at all. I'll have to install it again to see, but I figured I would say all of this before doing that.

I'll keep going by reinstalling your rom "soon". And try to get a good logcat and attach it after zipping.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
UPDATE: Now I believe that official Lineage 20 and your optimized 20 are both working the same way, i.e. as in 1 above. Sometimes I think either rom won't connect to THI at all, but I haven't seen that in the latest testing.

EDIT: Sorry to keep changing things. It does appear that your version may connect once, but never again. Otherwise, it is like official in that other SSID's work and get saved. SSID for THI did not get saved and cannot connect again.

So official is doing some strange things, as described in 1. But it does connect again and again. Yours does not after the first time during init.

EDIT2: Attaching a zip of a .txt file from earlier today. You many need a "better one", but maybe this is a start. The SSID for THI is "bebetmo" and you'll see it 3? times in the .txt file. But ENETDOWN happens before that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It all sounds very strange, anyway, you should perform some additional steps and capture another log for it to be more helpful. First, enable ADB root access in Developer Options. Second, run adb root, then adb shell setprop log.tag DEBUG, then adb shell setprop persist.log.tag DEBUG, then finally adb logcat -b all -c (this will clear the log buffer). Now start capturing the log with adb logcat -b all > log.txt and reproduce the error. Thanks.

P.S.: once you're done, disable ADB root access in Developer Options.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks for the detailed instructions for logging. I have used a catlog/logcat app in the past, but I think most of them require root.

Speaking of root, that is one of the complications in this mess! When I was going back and forth on whether the connection attempt to THI would always fail, I have learned that occurs only if I have installed Magisk! I believe the behavior of all of this is the same on the official and yours.

I should give a little more background here. I have multiple devices because it is a hobby for me to play with them, install roms, learn. So I don't have a good reason to have everything work on every device. For the two Essential devices that I have, it is not essential (ha) that you fix this. But I wanted to report it, just because it is strange and not consistent with all my other devices.

The main issue I would love to see fixed occurs before Magisk is installed. That's when the THI SSID is not saved in the Saved networks, for both official and yours. Android Q stock has a minor peculiarity on Essential, but it does save the SSID properly and it has no problem reconnecting to that Saved network after Magisk is installed.

So I guess I should get you the logs for the "not saving" problem before installing Magisk. Then if you are interested, we could move on to where the THI does not connect at all after Magisk is installed.

I'll try to get you an interesting log soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Extremely weird. So, if I have understood things correctly, both my and official builds connect but don't save the network if Magisk is NOT installed, while they do not connect at all if Magisk is installed.

Are you 100% sure Magisk is what causes this change in behavior? It really doesn't make any sense. Magisk is just a modification for the boot partition, which is only read on boot to load the kernel, literally never again...

EDIT: anyway, we'll see what insights the log will offer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Yes, you understood correctly.

Well, I don't think I could say I'm 100% sure! All I know is that I was trying multiple devices/roms, got different results, so I got a little more focused. If I didn't install Magisk with either Lineage 20 rom, I was just having the Save networks problem. I was not thinking Magisk was the cause of the problem, but most of the time, I do install Magisk. So I did, and there it was. I have done it several times, so I am fairly sure. But I don't think I can put a percentage on it!

I know there were some issues about going from Magisk 25.x to 26.x. so maybe trying the older version is something to try once we learn more about the Save problem.

One more tidbit about that. Even if I uninstall Magisk, it still has the "never connect" problem. So some damage has been done. Sorry, I know that's vague! I end up doing a reset/erase all data, just so that I can start from scratch again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I won't keep posting until I have a good log. But since I've learned a little more and want to confirm what you said about Magisk, I'll post it now. Magisk is NOT the culprit, so your instincts are correct. Sorry for detours...I'll get there.

If I'm connected successfully to THI, then restart (which I certainly did when installing Magisk, making me think it was the bad variable...wrong!). When booted back up, the status bar pulldown still shows THI as the connected SSID...just for a few minutes. I haven't timed it yet. But it disconnects so that the pulldown shows Networks available. (EDIT: I supposed it disconnected when I restarted, but it just takes time for that to show up). I cannot reconnect to the THI SSID again after that. I can connect to another SSID.

But at least I realized that instead of erasing data, I can just reset wifi, mobile, and bluetooth. That's quicker and gets me back up and testing more quickly!

I'll get the log for when I first connect to THI successfully, and maybe that will show why it doesn't get saved. But I'm not sure about getting a good log after restarting. I may not have time to do those adb logcat steps again before the connection goes away. I will certainly be able to get a log with the subsequent failed attempts to reconnect. I think that log will look like the zipped one I gave you last night.

EDIT: If I connect to another SSID, then try to reconnect to THI, it fails continually. I don't have to restart to see the problem where it won't reconnect. That means I should be able to get logs. Okay, I'll quit writing for a while.

EDIT: That last EDIT was incorrect. If I have restarted the device (or turned off wifi or gone into airplane mode), it is true that I can't reconnect, regardless of other SSID's. But if I'm connected to THI, connect to another SSID, I am able to switch back and forth between them successfully. Of course, I have to reenter the password for THI each time. I'm not sure how to get good logs when I restart the device (but I should be able to after turning off wifi or turning on airplane mode). But I'l worry about that after I get the first one that shows connecting but not saving.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I had a hard time! Log only contained about 1 second worth, so I changed the Log buffer sizes value in Developer Options from 256k to 1M. Then I got plenty.

Also, I had trouble getting the 2nd and 3rd parts. 2nd is where I turn wifi off and back on...this will cause the subsequent connection problem. 3rd is where I try to connect again. So for now, I'll just give the 1st part which possibly has info about why it's not saving the SSID. I say possibly because it's sure not obvious to me.

Here are the ranges of what to look at.

SSID bebetmo interesting info: starts at 17:31:04:207 ends at 17:31:09:205

Its MAC address begins with ac:df: starts at 17:31:05:990 ends at 17:31:06:642
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It's not clear to me what kind of problems you are having grabbing the logs. Anyway, changing the log buffer size is not needed at all. If you run the sequence of commands I gave you, the resulting file will contain all messages printed between the moment you ran the "clear buffers" command and the moment you interrupt the log capturing command.

Also, I strongly suggest that when you perform my steps again to grab more logs, when you're done, just before disabling ADB root, you run adb shell setprop persist.log.tag WARNING.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I can't explain why I need to change the buffer size. I executed your exact commands with the buffer size set back to 256k, and the log was small and had no interesting events. I changed back to 1M. Sorry that I can't get this to work as you expect.

I'm going to give you 2 logs which are stripped down. It may not be what you want, but these are easier to read since they are smaller and have "pertinent info" about the issue.

The 1st is when it connects properly. The 2nd is when it fails. I am not giving the part in between where I turn wifi off and back on. That should be interesting because without that, I can keep connecting back and forth between another SSID and the SSID for THI with no problems. So I have to turn wifi off/on to cause the THI connection attempt to fail. I had thought I could reboot, but that complicates restarting the log, etc. (I know you're not understanding why).

Look for bebetmo for interesting info.

EDIT: Even though the 1st connects "properly", the SSID is not saved.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I am starting to understand what the anomaly is. What is the security type of the network? Do you only have a single access point, or are there any repeaters/mesh points?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Good that you are making progress.

WPA version allows three choices. WPA2/WPA3 default, WPA/WPA3, and WPA2. It is set to the default, but I'm pretty sure I tried all three.

WPA encryption mode only allows AES when that default choice is selected. 2nd choice only allows TKIP and AES (not separate), 3rd allows only AES.

Frequency band is set to automatic which allows both 2.4 and 5.0. Or the band can be set to either of those individually.

Single access point.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hac0demon:
Could we please get updated MinMicroG package from February version to late July one? February one failing on latest ROM during account registration. Default MinMicroG also doesn't work well
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I don't recommend MinMicroG anymore. Use this installer instead: https://github.com/nift4/microg_installer_revived/releases

I'll update the second post, thanks for making me notice I have to. Sorry for the inconvenience!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, a new build is available. It brings September's Platform security patches, which are one part of the full set of patches released monthly by Google. The other part is called Pixel security patches and, despite their name, they are usually not Pixel-specific. This month, for some reason Google hasn't released the Pixel patches publicly yet. So I've manually picked the Platform ones only. The security version string in this new build reports "September 1st, 2023" (and not Sept. 5th) for this reason.

Also, some kernel bug fixes are present in this build too, and the whole build has been compiled with an updated toolchain.
[Essential Phone ROMs, Kernels, Recoveries, & Other] just4me12:
Thank you! Updated without problems so far 🙂
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Were you able to fix the possible security problem that we discussed a few weeks ago (post 352 and prior)? The problem was that I could not connect to a T-Mobile home internet 5G gateway.

Unfortunately, I did not keep that gateway. I did like it, but I'm wanting to get rid of my TV service as well as the internet. And I wasn't ready to do that yet, so I stayed with my existing internet service in the meantime. So I can't test it for you! If you did include a fix, maybe someone else who has that T-Mobile gateway can try it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Nope, I haven't had the time to inject my debugging code in the right places to fully debug the problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Under About phone - Android version - Build number:

lineage_mata-userdebug 13 TQ3A.230805.001

eng.nobody.20230915.195921

Is that correct?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
If you are wondering whether TQ3A.230805.001 is correct, yes it is :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Yes, that's the part I wondered about. But after I put that line, I thought I'd make it clear by adding the whole thing that is under Build number. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I am having a problem with FX file explorer app. I have Magisk 26.3 installed. I checked the setting in FX file explorer for Developer/Root access.

If I click System(Root) (vs. just System) folders, Magisk asks for permission, I grant it, and it "normally" will show all the files in root. But now after granting, it displays " the operation could not be completed". This is with your 0812 or 0915 releases. Your 0720 has the correct behavior.

I tried the official nightly lineage version 0918, and it works properly.

Strangely, Total Commander app never has a problem when clicking File system root folder for any of the ROMs mentioned above.

I have reproduced this several times, so I think I am reporting it accurately.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Unfortunately, I have noticed the same behavior. Thanks for letting me know which is the first affected build. This will likely be helpful in debugging this. Expect this to be fixed soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I've found a workaround for this problem. It'll be included in the next build, coming most likely tomorrow.

The problem seems to be that FX File manager, despite being quite good (at least apparently, I've been using it for years and it's my favorite), is not actually very solid under the hood. It does not read the file system via Linux system calls, but it has a prebuilt native binary it uses to launch a shell, then runs the ls command in that shell, and finally it parses the output produced by ls. This is not considered a good practice, because this approach suffers from a variety of weaknesses you can read more about in Material Files' Github repo.

In fact, Material Files and most others/any other root file explorer work fine on my ROM.

Apparently, some change I have recently implemented in my ROM triggers a warning in the 32-bit C standard library built into Android. This warning is printed to the standard error buffer when FX runs ls using its internal shell (apparently FX uses 32-bit native code). FX then has some code (I know because I've decompiled the app) that throws an exception if any warnings are printed while the app executes its commands. Strangely, the C standard library code that prints this warning is also present in official LineageOS 20 (it's actually been present in any Android version released in the last 9 years), but for some reason it looks like it is not being triggered there. My workaround is to simply suppress that warning. It is no big deal because the warning alone does not prevent bad things from happening, when an app triggers it. It is really just a warning. As far as I've been able to understand, that warning does indeed indicate that an app uses a shared library coded in a poor/unsafe way. But as long as it works, we're happy, and this workaround gives me some time to take a look at all the patches I've implemented in between July's and August's builds, to see if I can spot anything related, without keeping the app broken on my builds. Authoritative GNU devs also think that this warning can be ignored: https://lists.gnu.org/r/grep-devel/2019-12/msg00022.html
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks for the great analysis and explanation.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
New build available with all of September's security patches, a different Bluetooth audio component (shouldn't really matter to you as end users) and the FX file manager fix. @sga999
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
The last one I see there is from September 15?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
hi, there is a bug in the Updater... i expect Tomoms will sort it out in the morning.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Okay, but I don't use the updater, I get the ROM from GitHub. A new one is not there yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
h

hmmm... i'm seeing "lineage-20.0-20230926-UNOFFICIAL-Tom-mata-signed.zip"
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Weird! I clicked on 'here on GitHub' in the 1st post, and I do not see that. We must be going to different links somehow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Tags · Tomoms/mata_releases

Contribute to Tomoms/mata_releases development by creating an account on GitHub.

github.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks! I have never looked at tags before, only releases. That's because clicking on 'here on github' always got me to the latest release before this one. So something has changed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
UPDATE: FX File Explorer app now works for root. Thank you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Well, a strange occurrence with Total Commander app. I click on "Internal shared storage", and it displays a warning about allowing full access on the next dialog box. But 3 choices display, and none of them can be selected, i.e. clicking on any of them does nothing.

I have not gone back to see when this occurred with your releases. But with official nightly 0918 Lineage, those 3 choices (which could not be selected) do not display. Instead, "All files access" screen displays. I can turn on a button to Allow access to manage all files.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I can correctly see yesterday's build under Releases too. Weird. Maybe it was an issue on Github's side. The command I use to publish a new release on Github hasn't changed.

I could not reproduce this on my other device (not a PH-1, but still running my "unofficial, optimized LineageOS", so an environment identical to the PH-1's, device-specific bits aside). Total Commander works fine. Will check on my PH-1 later today.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Crazy! I don't understand why I would not be seeing the latest release when you and others are. I am merely clicking on "here on GitHub" under Downloads in your first post. This is what I have always done. I also can long press that, copy the link, and paste it into the browser. It does the same thing. I will attach a screenshot. Oh well, as long as I know I can see it in tags, I will do it that way.

EDIT: This occurs on browsers on both Android devices and laptop. Oh, is everyone using the app instead of a browser?

By the way, I am not signed in to Github and never have been, as far as I know I am signed in on XDA. Maybe I will sign into GitHub later and see what happens.

About the Total Commander problem, I do not see it on any other Android device. I do have another ph-1 with the nightly version that I mentioned. I could go back and see if this occurred on older releases of yours. That's a bit of work. I do not use Total Commander very often, so it's certainly not urgent. I had just been using it to compare when I was having the FX file explorer problem. So I tried it again with this new release and had the issue.

EDIT: Signing in to Github did not help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I'm using a browser too. Maybe you should clear Github's cookies and the browser's cache? Just speculating, this doesn't really make any sense...

About Total Commander: I forgot to check it on my PH-1. I'll do it tomorrow. For the moment, don't bother rolling back to older builds of mine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Clearing cookies and cache did not help. I was using Edge browser, but it did the same thing with Chrome. Really strange... on that releases screen, I can "Find a release" for 09-15, no problem. But the one from the 26th says "there are no releases containing 09-26".

Okay, I'll try to keep learning about the Total Commander problem without going to older builds. It did work one time after I had rebooted. But nothing since then, even when I reboot again. Crazy problems.