Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 11/17/2025 in Posts

  1. F(x)tec never had all the driver sources. And even if they did, they would not have been allowed to publish them. A prominent exception is the keyboard, which is the one hardware component they developed themselves. The rest of the hard- and software came from a Chinese OEM. The idea that f(x)tec ever wanted to make the Pro1/Pro1X "open" phones is a misconception introduced by some media and bloggers. F(x)tec never publicly corrected that misunderstanding, presumably as they hoped to profit from all that "Linux-phone" hype. In reality, the Pro1 was designed as a pretty standard, proprieta
    3 points
  2. Lineage-23.0-20251215-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.
    2 points
  3. Lineage-23.0-20251208-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.
    2 points
  4. Lineage-23.0-20251201-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.
    2 points
  5. The base kernel source is of course available as per the GPL2. Also, e.g., the keyboard-driver source is available as part of LineageOS. However, much of the device drivers that make up basic mobile-phone functionality are not. The project of mainlining the Pro1 got stuck on such profane things like the touchscreen driver requiring some non-disclosed firmware magic to be usable in the first place. Device drivers not being open-sourced is pretty standard in the Android world, though. Nothing specific to the Pro1 here. 👎
    2 points
  6. I think that for an OS like Lineage, which is supposed to be just Android-without-the-Google-bits, upgrading the major Kernel version will be next to impossible. The proprietary vendor blobs compiled for 4.4. will not load with 4.14 or later. That's just not how Linux works. Yes, there may be some other ms8998 devices out there using later Android kernels. So it may boot somehow. But what's the good of that if your LTE-modem, camera, and touchscreen no longer work?
    2 points
  7. Hello all, As @elvissteinjr correctly stated, Pro1 needs a kernel patch to be supported in LOS 23. in the concrete case that the ebpf backport will not be available for the kernel 4.4, I googled for msm8998 devices and there are one or two shipped or updated with kernel 4.14. maybe trying to update the kernel to that version is the way to. Also thinking that some hardware is shared with pro1x that is shipped with 4.19 will make easier the compilation. Do we have the kernel sources for pro1?
    2 points
  8. Lineage-23.0-20251124-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.
    2 points
  9. If you are updating the same major version via OTA, you should not have to reflash magisk, I never do for OTA. Now, I only use Magisk for SU, so maybe it is different if you use different modules. I only ever flash Magisk if I am doing a non-OTA major version upgrade.
    1 point
  10. Yes, after every update per OTA you have to reinstall magisk to the inactive slot before restart!
    1 point
  11. Oh - nono...it will be too much work for me 🙂 Maybe more simple way will be downgrade AA to latest working 14.x.x version.
    1 point
  12. My first idea was to start with pro1x kernel 4.19, maybe the compiled proprietary blobs are the same or mostly the same as pro1. But I never found a 4.19 kernel built for msm8998... Maybe one of the guru of the company can help us with the driver sources? unless @EskeRahn is correct and the sources were part of the swindle, though.
    1 point
  13. (Still no 23.0 for Pro1, so likely not going to happen, and as 22.2 is borked use 22.1 or earlier)
    1 point
  14. Lineage-23.0-20251117-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Lol. Maybe I should just have one post and keep adding to the list, 😉
    1 point
  15. Sorry for the late reply but I do have a copy if your still interested. This is the qfpkg_linux.zip, not sure if there were any others. qfpkg_linux.zip
    1 point
  16. I have a black semicircular blob on the bottom corner of my Pro1 X screen due to drop damage. Fortunately, it doesn't block any important parts of the screen just yet, but it's slowly getting bigger over time. Yesterday I ordered what is apparently a replacement screen and digitizer for the Elephone U Pro from this Amazon link. Once it arrives, I'll test it with the Pro1 X directly, though I assume it'll need to be reflashed like all the others. Is anyone still offering this service? I live in the US, which might make things tough, but I'm willing to cover any shipping and import fee
    0 points
  17. 0 points
  18. Hi all 🙂 I have problem on my pro1 with Android auto and i want to know , if is it problem only with my device or on all. Display on car stereo is like pulsing and blurring. It was tested on 3 (vw and toyota)cars and on all is it same. I am now on latest LOS and android auto version 15.8.15404. Tested on wireless and cable connection.
    0 points
×
×
  • Create New...

Important Information

Terms