Leaderboard

Sure, its their choice. And I fully understand that Lineage is not in the position to lead Android development and force Google to adapt. Still, I feel like this is the end of the road for me. (Edit: And I am very thankful for the work everyone has done with LineageOS! Lineage is clearly the better Android, and they rescued countless devices from an early obsolescence.) (Warning: Old-man-rant approaching!) Google's choice to develop Android the way they did made sense, back in the olden days. But they quickly gained marked shares, followed by absolute power. Despite that, they contin

As you know, I feel the same. But in all fairness, let's say that Lineage is not actively going that way. It simply maintains compatibility with the respective Android release, which does make sense, right?

Google and Lineage are going the wrong way, making things too "secure" and "fool proof". Root and SD-cards are a good example of the things the future won't hold. I feel that power-users have to bend over backwards to use their devices the way they want. So that's what I did. I bent over backwards ... and gave birth to an old-timer 🤰👴 😁

Build took 01:49:55 on Intel Core i7-11700K with 64GB of RAM though I don't think RAM usage got much over 20GB anyway. I used 100 GB ccache but it only contains 26GB after the build. Huge speed increase then, which was to be expected when compared to Windows hosted solutions.

Beloved community, here it is: Another up-to-date outdated ROM to satisfy your custom ROM fetish. LineageOS 17.1 JeBB "A noble spirit embiggens the smallest man!" is (so far) a slightly modified build that will be updated in irregular intervals. Future builds may contain additional fixes, or I may attempt to fix things with a Magisk module ... "may" is the important word here 😉 This build can be installed from scratch like any LineageOS build (LineageOS Wiki). Dirty-flashing from the last official LineageOS 17.1 is possible, but the official signature keys have to be exch

Just for the record, after I decided to install LOS 18.1 with Magisk when I moved to 18.1 after had been using a non-rooted LOS 16.1, the first thing I tried was to just install the next OTA and see what comes out of it, and both GApps and Magisk were still there and working after the reboot. Has been that way for me ever since.

You can, with fastboot. fastboot --set-active=a

Seems like they indeed fixed it and somehow without reverting those changes. I wish someone could explain that to us. My latest build is real smooth.

I have an option in recovery to reboot to recovery anyway.

Changelog 20211025: New build with Android security patch level 05.10.2021. No other changes.

About 6h30mn on Windows using Virtual Box, about the same using WSL. On Ubuntu I'll let you know once it's done. Looks like those random crashes are gone for good.

I checked the updater and the OTA package is slightly larger (749 MB) than the sideloaded one (707 MB), whatever that means. Maybe just the sideload plus the install executable?

Right, that may cause problems even if it does not reveal in a usual workflow. Anyway, does memtest86 run on the machine for a longer period (like a day) without issues? Otherwise, if you will experience problems again, you may also try to run it using another kernel, in very rare cases it may also cause problems on a specific hardware. Anyway, how long does it take for you to compile? ...and I am curious to see if it was different on these OSes.

I believe OTA is a different package than the sideload.

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

Yeah, the semantics is off. What is switched is what recovery indicates is the running slot. I chose to make it a step that I always ended the install with a reboot to recovery so I wouldn't forget where I was. 😄

I don't know since I always just went ahead and reflahed Gapps and Magisk when I was sideloading because it was easy. But tdm indicated that you shouldn't need to in his instructions for LOS 16 (though he noted some said it didn't work). And why does both Gapps and Magisk persist after OTAs? Just asking questions because I'd like to learn.

They have good intentions and a great product (hardware-wise), however: They SERIOUSLY need to work on their public relations. It really needs a STRONG improvement. @Erik! That guy is at a mess and He desperately NEEDS YOUR HELP!

Interesting. I have compiled it on a chrooted Ubuntu environment earlier and now I have checked relevant packages were not upgraded since then. I have not tried yet to compile the very latest version of Pro1-related codes anyway. Maybe - are you sure you have enough free space on the partition where this compile runs?

I believe the last remark is not quite accurate. It is the flashing&install of the main image that also changes the active slot. Reboot to Recovery just boots to that. If you do not want gapps/magisk/... a reboot from the main menu will also boot into slot B

These two changes have been merged, and are in the 20210906 build for Pro1. If you have any trouble using a custom keymap, please open a new bug report following the instructions here: https://wiki.lineageos.org/how-to/bugreport

@Slion I understand this was missing in the original patch. Could that explain what you observe?

Hmm, it can be a vaild reason,, thanks. 🙂

I have changed the behavior of DeviceSettings here: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/315310 The built-in keymap mods are still toggled off and disabled when a custom keymap is active to avoid interference, but you can now use the built-in keymap mods when a custom keymap is present but not installed.

I tend to think that things like batteries could be changed without having to recertify the device as it has nothing whatever to do with the radios, as stated. We could always take the approach I used on my old VHS movie camera. I removed the sealed lead battery from its battery pack and turned it into an adapter that went via speaker wire to a lawnmower battery I wore in a backpack while filming. I ran it for days and never EVER ran out of juice while filming. :)

Ok, so way back when I said "I'll keep you guys posted" about my adventures trying to get my screen replaced. 7 months later, here's an update: Tl;dr: I still have not been able to get an official replacement screen from F(x)tec. 7 months of having effectively abandoned my Pro1 for practical reasons, and not being involved with the community at all. Trying to talk myself out of demanding a refund for the replacement screen I ordered, but I can't say that's going well. So the first thing I did was check eBay in case anyone was selling Pro1 parts, or just a dead Pro1 for parts. I was i