Slion

Still building... RAM usage went up to almost 20GB. All cores at 100%, temperatures still below 70C.

I believe OTA is a different package than the sideload.

Definitely enough free space, it's an almost empty 2TB SSD. I think this is a hardware issue, some kind of memory corruption since I can't reproduce the crash. It always crashes differently even froze the PC once. I've reset the BIOS notably RAM clock from 3600 Mhz to the default 2133 Mhz. Those sticks were rated as 3600 Mhz but that's still overclocking so I guess I better try the system's default. Sure enough my build is still running but I'm pretty it never went that far so it looks like RAM speed was the issue.

Very good point, I'm just like you, trying to understand and learn.

I'm pretty sure that's not the case. You need to reapply GApps even if it was installed on that slot before, same for Magisk. I'm guessing both sideloads overwrite files from the ROM.

I'm having a hard time getting the build to work on a native Ubuntu 20.04 installation. See: https://github.com/android/ndk/issues/1578 Right now I'm stuck, the build crashes and I have no idea what to try next. Turns out it was a lot easier on Windows using WSL or Virtual Box, who knew…

Unlikely LATER: Actually you were right @claude0001see comment from @npjohnson below.

It looks like it's still in there though somehow it was remerged? No sure what's going on TBH. Maybe they fixed it some other way too...

I did not checked that they actually reverted and somehow I doubt it... 😁

Looks like it's fixed. I'll test it some more but I already advised the guys at Lineage to revert it.

I'm investigating that lag issue. As explained above I further reduced the list of potential culprit. I switched back to my broken build and sure enough not long after boot I could reproduce the issue fairly easily. I'm currently attempting a build reverting that change to see if that fixes it.

I never tried do any audio recording and very few video recording TBH. However my understanding is that people have had some issues with that as you discovered from searching the forums. Be happy FxTec support tried to help you. At least they took your harware and tried to fix it somehow. Unfortunately it didn't work so well in the end and I understand your frustration. You may have to live with this issue I'm afraid.

You want to buy a screen for the Elephone U Pro. Phone call quality is known to be bad sadely.

Those are the changes that occurred between the 25th and the 30st of August. There is obviously one Pro1 change that could be the culprit. repo forall -c 'git log --since "AUG 25 2021" --until "AUG 30 2021" --pretty=format:"===============================%n%Cred$(git config --get remote.github.projectname)%n%Creset%H%n%an%n%ad%n%B%n"' =============================== LineageOS/android_device_fxtec_pro1 15b9323d740da90ba3c00a86002a6b995c42d211 Luca Stefani Wed Aug 18 22:07:34 2021 +0200 pro1: Adjust powerhint for QOS interface Currently all writes to the dev interface are done by WriteStrin

I reverted back to a custom build from the 27th of August and I don't have that issue at all. Actually I believe my code checkout was front the 25th so at some point between the 25th and the 30st someone introduced that regression. Now go figure what it is exactly.

I think I have a similar issue. Looks like I'm getting lags or freeze from time to time. Definitely a regression in the latest release. Even though I'm not actually using the release but my own build from around the same time. It happened like 5 times while I was typing this message. That's 6 now.

I've put together a guide from knowledge I gathered over the last couple of weeks as I eventually got around trying Lineage OS on my F(x)tec Pro¹: https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/ It takes you through the installation process from Windows setup to Magisk root and SafetyNet validation to working around prominent issues. It will also take you through the build process from Windows environment setup to development and code contribution. Also taking this opportunity to mention how awesome it is to be able to update, use and customize almost every aspect o

Not sideloading magisk after sideloading a new ROM does not break it's functionality it seems but the app won't be fully loaded. It will look like Magisk is not installed as far as the app is concerned. Therefore when loading a new ROM the process goes: Sideload ROM Sideload GApps Sideload Magisk Reboot

As posted on GitLab there is a Magisk extension call "Fullscreen/Immersive Gestures (Q-S)" to workaround this issue. It's designed to hide the "hide keyboard" tool bar displayed below your onscreen keyboard. Use the volume +/- buttons to set it up. I used the following options: Vol+ Fullscreen (not sure though what's the difference with immersive) Vol+ Low sensitivity gesture (apparently also fixing the Task Switcher gesture being overly sensitive in landscape) Vol- Don't disable back gesture It's also worth noting that this is so annoying that manufacturers like Samsung

I noticed GMail won't start anymore. I'm not sure if that was caused by the re-sideloading of GApps somehow.

You will be able to remap every modifiers. My understand is that he is simply planning to add them to our keymap.

@VaZso That's my understanding too. What Sean is suggesting is definitely an extension of your work taking things even further by making it more generic. Great team work guys.

So you want to extend our keymap to support them too? Sounds good to me.

It's actually seven, you forgot Sym.

Maximal flexibility sounds good to me but sensible defaults is also important as most people will just use that. Also keep in mind that you can already remap your modifiers from KCM. However being able to remap them from our keyboard advanced settings sounds a lot more practical to use assuming this is what you have in mind.