Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 09/18/2021 in all areas

  1. This is now official. Builds are weekly, currently scheduled for Wednesdays. Install instructions are exactly as LineageOS 18.1. Download site: https://dwnld.aicp-rom.com/ Enjoy!
    10 points
  2. Hello, In case of someone would be interested, I try archlinux container in termux with Xfce and it works perfectly for the pro1 with Xserver-XSDL apk. It also works with VNC but without sound. I can now listen music, use Libreoffice and firefox and play with my programming tools. Pro1's keyboard works prefectly (qwerty version here) Very nice discovering a new linux distro. It's not so hard and the documentation is very complete. Source installing archlinux : https://github.com/SDRausty/termux-archlinux When you have done this, $ startarch (in Termux) and you wil
    8 points
  3. Currently working on a new low profile bookcase, I reckon I still have like 12 hours of stitching to go through. I had to remove the stitches to be able to incorporate the smartcase magnet, move the closure magnet to accommodate for the Pro1 thickness and customize the back panel to enable kickstand feature.
    6 points
  4. To eleminate clicking/popping sound: switch off NFC. I have also experienced that annoying clicking noise, until today when I accidentaly enter into factorytest by tapping build number, and go through all of the tests. And there was an NFC test, but I had no nfc device to connect, so I switched it off. And then the clicking sound dissappeared. I tried again to switch on NFC and the clicking sound came back, and with switching off, it disappeared. 🙂
    6 points
  5. Maybe you can try this... I just uploaded it and will merge to 18.1 in a few days after I clean it up a bit. https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/316402
    6 points
  6. I like those news in particular ... 😺
    6 points
  7. Yes, they did... looks good for now! For the sake of completeness: 😉
    6 points
  8. Uploaded my LOS 16.0 build dated 20211017. AOSP patchlevel of October 2021. Contains a version of @Slion's experimental "Fn-Tab-as-Alt-Tab" mod as discussed above.
    5 points
  9. Done with stitching. I love the leather quality, really soft, one of the best I've seen. I need to finish the cutouts on the bumper case and glue it to the leather. Will hopefully get around it tomorrow. The case is 75g that's 25g lighter than the one I've been using so far. Moreover I reckon its lower profile will be more confortable to use, notably when the keyboard is open. The closing latch is on the front panel which is a rarely seen design. As a result when closed it won't lay flat on it's back which should make the phone easier to pick up, not that this was ever a problem considering th
    5 points
  10. Try to be optimistic. Money is not everything. I paid my Pro1 (without the "X") also more than a year before I finally got it. Now that I have a real keyboard phone, I congratulate myself for the decision to preorder every day.
    5 points
  11. You may also want look at the latest update of their IGG campaign sent out almost an hour ago. It seems they have some working units (potentially good for development even if its mainboard has an earlier version), a potential last iteration of V3 main board, then an ongoing CE/FCC certification (it should be done using the final mainboard iteration) and mass production then. They currently estimate shipping in November which is potentially the end of the month and that will mean if they are right, they will serve their pending orders first near the beginning of December. So I would
    5 points
  12. (lineage-18.1-20211004-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.
    4 points
  13. Had it reprinted in TPU and it fits fine. Thanks for the help everyone and ubuntuscofield for the design and 3dpeople for printing it.
    4 points
  14. As usual, the OTA update installed smoothly here, too (with previously sideloaded MindTheGApps and Magisk installations unharmed)...
    4 points
  15. They just posted an update on their indiegogo page. Looks like production will start October
    4 points
  16. Thanks @tdm, links added here 😁
    4 points
  17. Right now you will need to use 'adb' to install the custom keymap, and there isn't any app to help you create the map 😕 @Slion made this nifty QWERTY keyboard image with each key labelled with the 'key number' in yellow: The manual process is to choose which key you want to remap, and to look up the keycode you want it to generate in this list: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h You will need to convert the keycodes from decimal to hexadecimal if they don't begin with '0x'. The custom keymap is a file with lines contain
    4 points
  18. ...and going back to my BlackBerry Priv. It's been an interesting year and a bit with the Pro 1, but I don't think it's working out. Software is just... I don't know, unfinished. It's more than a year, some glaring bugs are still there, apt-X, taking two tries for the launcher to minimize properly, inability to press Shift + Num for the corresponding symbol, you name it. My Priv is still on Android 6, but at least BlackBerry had the decency to keep it updated (close to) monthly and most bugs were ironed out before they pulled the plug. I know inevitably someone will tell me install Linea
    3 points
  19. I haven't tried AICP yet because LOS 18.1 has been working nicely, including OTA updates wich leave both GApps and Magisk intact. Also, according to the settings page, my phone is encrypyted, too.
    3 points
  20. I feel similar to Hook. The lineage is a cleaned up Android, where you can infest it with the Gapps you need or none at all to your liking. The Aicp is (in my layman terms) like a Lineage with added options to tweak as you please. I like the AICP better, as it somehow feels cleaner. But I must admit that I barely use all the options, as none of the OS's are on my daily driver (a normal retail unit) that runs plain Android. I have a suspicion (though I have not yet tested!) that some of my apps will not work if I upgrade from stock Android to AICP. One app that I find crucial with a fli
    3 points
  21. I have tried both. AICP offers more tweaks that I like. Lineage seems very vanilla to me-- I used to use Dirty Unicorns. I don't think there is much of a difference in their core functionality. Now that AICP has become official, it is updated weekly with a reliable OTA updater. I have not had problems with either Lineage or AICP's updater. I do use Magisk, but only for SU, I am encrypted according to settings (I only use swipe access).
    3 points
  22. That is pure hindsight bias. It is useless to look behind. Of course you would have made money if you knew back then what courses are today. If you would have bought XTZBEAR Coins for that money you would have like 0.02 $ right now...
    3 points
  23. Turns out, they indeed had answered within a week and my mail provider had apparently decided, that I don't want to recieve some emails already before my inbox limit was fully reached. I sent them an inquiry recently and they answered within nine days. So I guess if anyone doesn't get an answer for more than two weeks, they should just try again. Also my phone was already repaired in July, so they were almost right with their initial projection of how long the repair process would take. Only took one month longer, which is kinda good for their standards :D
    3 points
  24. I am ready to help, but I would first need to know what you are failing at ... Please have a look at this post, and try to understand it, following the links I provided. The first step is to prepare an SD-card with a partition containing the GNU/Linux distribution. This is best done from an existing (x86) Linux-PC using qemu as described in the first link of my post. As most modern Linux distros are based on systemd (which cannot run in an Android chroot), I suggest Devuan which uses traditional System-V init. It is possible to change the init system also in vanilla Debian, but that
    3 points
  25. Termux is a nice project and has some interesting features. But as an in-app solution, I guess it will always be somewhat limited. That is why I decided to install everything from scratch by myself. Note that, in the beginning, I also knew nothing about chrooting Linux distros on phones: the Pro1 is my first Android device. Do not give up! The reward for all the work and learning is that I have now a GNU/Linux distro running really in parallel to LineageOS, which allows me to use the Pro1 like an actual PC, while neither disturbing the Android environment nor depending on it in any way (e
    3 points
  26. Maybe start a topic and try to involve some LOS folks. It could be the drivers and/or hardware are just bad, or it could be something else is amiss. It would be awesome if the community could somehow investigate audio recording issues on one hand and call quality on the other.
    3 points
  27. I surely agree. That said, at least after Fxtec eventually decided to turn to Indiegogo again* for funding the Pro1X, a real danger of maybe never seeing either one's device or one's money again has always been the elephant in the room. Which still is no excuse for their bad (or complete lack of) communication, of course. _____ * after the founders (as a company named Livermorium Ltd. back then) had been using Indiegogo already to fund the Moto Z Keyboard Mod, which failed to reach general availability due to no fault of their own, with everyone being offered a refund, and
    3 points
  28. No I've been off doing other things. Maybe one day...
    3 points
  29. @tdm This is from the AICP-Q thread, but I'm wondering if any progress has been made on this?
    3 points
  30. Build 20210922 is available. It includes the September 5 AOSP security fixes. As of this release, the build includes a backported patch, originally made by @Slion for LOS 18.1, which allows one to use "Fn-Tab" and "Alt-Tab" equivalently for switching Apps (see this thread). I find that feature really useful when holding the Pro1 by the keyboard. I have used that modified keyboard driver for weeks without issues. Still, be warned that this code has not been merged into any official LOS branch yet, and should thus be considered experimental. Edit: I think I should clarify:
    3 points
  31. Updated to the 22 SEP weekly via OTA. All went smoothly and root was maintained, Basically, looks like the same updater Lineage uses and has the same result.
    3 points
  32. Just a final note. Have most everything set up again and I am loving being back on AICP-- my favorite tweak being that it uses Slim Recents. Still tweaking, but everything is running smoothly.
    3 points
  33. I seem to have successfully flashed AICP 16, but I'll update once I have the phone fully set up again which will take me a while with other things I have to do. It booted up and is running very smoothly. I used the Lineage 18 recovery and started by wiping data/factory resetting, assuming a dirty flash wasn't a good idea. I did adb sideload and then, as always, rebooted to recovery. When I did that, I got a few mounting errors (which I didn't write down, sorry) which I chose to ignore. Lol. I flashed Magisk and open gapps nano and booted the system. Usual longer bootup for first time. E
    3 points
  34. @tliebeckWelcome on the forums. I think the displayed layouts on the IGG page are still what they were when first published. The community has already heavily criticized them in multiple places on those forums. My take on this, is that it should look like that: See also: The last thing we want is removing modifiers, also having printable characters on the bottom row of keys is not a good idea IMHO.
    3 points
  35. You should be able to use pretty much any recovery to install it.
    3 points
  36. On Lineage OS 18.1 I keep getting in situations where the fingerprint sensor won't work until I unlock to phone with PIN. That was somewhat of an issue before but since I changed my case it's annoying to the point where the fingerprint sensor is almost useless. I'm assuming most those issues are related to the fact that the fingerprint sensor gets temporary locked after 5 failed attempts and permanently locked after 20 failed attempts. Though on stock it would show a message on the lock screen telling you your fingerprint sensor is disabled, on LOS I don't get such message. My new case en
    2 points
  37. Actually I really enjoy that kind of manual activity, it is such pleasant change from software engineering.
    2 points
  38. I just sent the following email to FxTec:
    2 points
  39. Ah! I had to purposely look there to see them. I have a hard time finding things when there's low contrast 😝
    2 points
  40. Nice job! Always good to see I am not the only one using the Pro1 as an actual computer ... 😎 By using XRDP as a wrapper around VNC, you can forward sound from the VNC session to an RDP client (I recommend MS Remote Desktop 8 as it seems to work best with the Pro1's keyboard). This way you do not need a separate XServer on Android, and the Linux session can run in the background when disconnected. I gave an overview about such a setup in another thread. I do not use termux, but I guess it cannot install XRDP and the required PulseAudio drivers for you. You'll have to do that yourself f
    2 points
  41. > And then we don't see how many people have had success in their dealings with support, they don't come here to report. It's only the failures we get to see here. Sure, but when we're getting to the point where I'm considering I may never see my device or my money again, and fxtec is plainly just not responding to old or new tickets, it's pretty scary. I just want a "sorry, we're missing some parts, we're on it" so that I know that there's life on the other side. At this point, one needs to start considering that buying a Fxtec device is a bit like buying second hand. You get what
    2 points
  42. Confirmed on LOS 16.0: With NFC switched-off, no clicking when recording from the 3.5-mm-jack. Thanks for sharing!
    2 points
  43. Updated to the 29 SEP weekly via OTA. All went smoothly and root was maintained, September security patch.
    2 points
  44. Download and flash worked smoothly too.
    2 points
  45. ADD: A really low priority bug. When attepmting unlocking with the fingerprint scanner from display-off it quite often does not work.. If I then press Power and tries again (from the lock screen) it (AFAIK) always works, including the haptic feedback. I THINK it is could be related with how deep it sleeps, that is if after a while in lock it might work if by some chance I touch it while a wake lock has woken the system, e.g. to check mails. But that is pure guesswork. This is absolutely a low priority issue, but just to the list to remember if more important things fails to do as ex
    2 points
  46. (lineage-18.1-20210920-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.
    2 points
  47. To configure Night Light you need to edit that config.xml resource overlay: https://github.com/LineageOS/android_device_fxtec_pro1/blob/lineage-18.1/overlay/frameworks/base/core/res/res/values/config.xml It is in fact overriding values from the platform config.xml in which you can find all defaults: https://github.com/LineageOS/android_frameworks_base/blob/lineage-18.1/core/res/res/values/config.xml From the two quadratic equations defined in our config, Pro1 uses the native one, at least in the configuration I tested: config_nightDisplayColorTemperatureCoefficientsNative Red co
    2 points
  48. On my proposal the left AltGr should really be labelled Sym and then everyone can map it to whatever they want, Del for instance. The right AltGr is really needed, not least for Alt+Tab.
    2 points
  49. I like Slions version, except I would swap the backslash and back- apostrophe keys. to more usual placements, and especially in light of other qwerty-based languages where the accents are usually on the right side
    2 points
×
×
  • Create New...

Important Information

Terms