Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/29/2023 in all areas

  1. This is a placeholder for info that I will put about DivestOS which is based on LineageOS. The goal of the OS: DivestOS takes LineageOS and hardens security and throws away a lot of propriatary stuff & blobs to enhance both security and privacy. IMPORTANT: Please read what is dropped by design before choosing to use this OS: faq functionality_tables To ask questions and get help see community (mainly XMPP chat, also available via Matrix bridge) To file problem reports see bug_reporting Current status for pro1: Unknown: Build ex
    2 points
  2. Hi all! As you might experienced, there are so many different issues with comments and reports spread across so many forums and chats, that community members decided to gather them in one place. This is an attempt to create such a list, first we try using Github. <PATIENCE PLEASE UNTIL THE WEEKEND, THIS IS UNDER CONSTRUCTION, THANK YOU FOR UNDERSTANDING> The updated status tracking page is located on this GitHub wiki: https://github.com/ColdCamel/fxtec-pro1x-status/wiki Procedure for reporting updated status: If you wish to let us know that some feature or a problem s
    1 point
  3. Just a note. Even if there is not a lot of activity, the beta thread on Telegram is Official, as per the link you provided.
    1 point
  4. I tested this 2.1.7 and the connectivity problems seem to be the same, I am going back to testing LineageOS for now and later I will be also testing DivestOS I know the radios are weak but I just experienced that LineageOS definitely has less calling&audio problems than stock Android
    1 point
  5. I've uploaded another build of LineageOS 16.0 at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 which includes backported ASB fixes up to "5 June 2023". Go for the ROM dated 20230628. Based on @raymo's feedback above, I have removed @Slion's "fn-tab = alt-tab" patch from the keyboard driver for now. It was the only mod that -- while significantly modifying the driver code -- was never included in any later official LOS trees. Based on my own testing, I still do not think it introduces any problems with regard to keyboard response, but I want to give it a shot. I
    1 point
  6. @raymo: So I installed a test build of my ROM with all my keyboard-related modifications disabled. I.e. the driver is the same than in (official) LOS 16.0 and 17.1. My sometimes unresponsive keys ("N" is the most problematic one for me) are definitely still there. As I remembered, I get a lot more unwanted doubles ("douubless") this way, as the respective patch introduced in LOS 18.1 is now missing.
    1 point
  7. Pro 1. Now on a Pixel 7. I like the phones that start with a P and end with a number.
    1 point
  8. The frame is not metal, it is plastic. Mine has a small bit missing at one of the corners since it was <1 year old.
    1 point
  9. This is a post with links to threads on various tasks. Like installing and repairing. Suggest additions at will. If I find it relevant, I will add it, and plan to remove the suggestions to keep this thread (c)lean. ***Please be aware that guides for Pro1 and Pro1X are NOT interchangeable in general, though much goes for both*** Please: Help keep the forum clean and use the Report function whenever you see some spam or similar irrelevant content. Please: Enter your FxTec Device Information in your Member Title slot under "Edit Profile". See this (So other
    1 point
×
×
  • Create New...

Important Information

Terms