Jump to content

Leaderboard

Popular Content

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

  1. 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
  2. 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
  3. 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
  4. 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
  5. I like those news in particular ... ๐Ÿ˜บ
    6 points
  6. Yes, they did... looks good for now! For the sake of completeness: ๐Ÿ˜‰
    6 points
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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...
    4 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. When I still had an official LineageOS, I was applying every weekly OTA and "su" would be preserved reliably. I never disabled encryption. Those were the days of AddonSU though, which was officially supported by LOS. Always remember that Magisk is a third-party tool before blaming the OS for it to stop working for some reason. Today I run my own builds which I install via sideload. This requires "su" to be reinstalled at every update ... one gets used to it. At this point, I would not prefer one ROM over another just for its ability to maintain root across updates. Let's face it: us roote
    3 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. 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
  23. 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
  24. 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
  25. 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
  26. 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
  27. No I've been off doing other things. Maybe one day...
    3 points
  28. @tdm This is from the AICP-Q thread, but I'm wondering if any progress has been made on this?
    3 points
  29. 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
  30. 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
  31. I agree that Fxtec's keyboard design is better for most purposes, even though some people complain about it being too wide for comfortable thumb typing. I cannot confirm this; I have rather small hands and I got used to its dimensions very quickly. That Pinephone slider keyboard prototype looks a lot like what the Fxtec people (then named Livermorium) tried to do for the Moto Z series of Motorola phones with their Keyboard Mod!
    2 points
  32. Here is an image of the keyboard prototype for the pinephone. Appears very similar to planet computers keyboard design. I still feel fxtec pro1 keyboard geared toward thumb typing and a full 60% keyboard layout is vastly preferable for linux users to this type of layout. Hopefully, pinephone will make a slider keyboard with a layout similar to pro1's one day. Actually, it sounds like they're already working on one: https://liliputing.com/2020/07/pinephone-linux-smartphone-could-get-a-slide-out-keyboard-acessory.html
    2 points
  33. ,,,Or you could make a case where the flap goes the other way. Just 12h stiching... *LOL*
    2 points
  34. Guys ... you do need to clean your gear from time to time! ๐Ÿ˜„ Ever heard of this (famously quoted in Kubrick's "Full Metal Jacket")? Different device, same approach. ๐Ÿ˜‰
    2 points
  35. You are right. But @Dyna Smart do not provide much details in their report: Replaced themselves or by FxTec? Source of the replacement screen? Installed OS? My experience is that, in lack of more information, you never know what people understand by "not working at all", especially when they are at a certain level of frustration. Hell: I myself have sometimes said my Pro1's camera was "not f**ing working at all!", although this is objectively far from true ... ๐Ÿ˜‰
    2 points
  36. Did you or Fxtec do the repair? If you did the repair, was it Fxtec's replacement kit or the naked display from another, probably Chinese source? Anyway, I fear that sounds like either the replacement screen is somehow defective, or maybe something went wrong during the replacement, like a connector not properly connected or maybe even a wire damaged...
    2 points
  37. Ah! I had to purposely look there to see them. I have a hard time finding things when there's low contrast ๐Ÿ˜
    2 points
  38. The numbers are edited into the pictures on the bottom right. The order is: 1, 1, 1, 2, 2, 3 Eske didn't message me so I guess @brunoais has reserved the first one. The other two are still available then.
    2 points
  39. Oh, I did read that. As I did read all the other announcements since 2019. I guess, for those who have followed FxTec's path for so long, there are only to possible outcomes: you become either a pessimist or a believer. ๐Ÿ˜‰
    2 points
  40. @AngledLuffa and @saygi, You may want to look in the following thread: ...or most likely in this thread: I think the latter (Factory Restore Tool) would be interesting for you, but I have a feeling it will not help. My friend had a similar problem of his Pro1 maybe a year ago (or more) which has started the same way and ended up with a factory replacement device. Flash tool could reach the device, but it has failed reaching its internal flash storage, most likely UFS flash IC became dead in his case. (So, it was either a soldering problem or IC fault but the result
    2 points
  41. Download and flash worked smoothly too.
    2 points
  42. Yeah, not in my spam box. I'll chalk it up for now to some blip in the internet, like dryers eating socks. ๐Ÿ˜‰
    2 points
  43. OK bit the bullet & tried contacting them via the webform instead of my email lets see if they respond to that If the warranty runs out before they respond to me & they start playing silly buggers, they're going to end up paying my lawyers legal fees too -- EDIT -- Ah a request received email, thank you automated reply system
    2 points
  44. 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
  45. (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
  46. An odd bug with 1.1.3, on AICP-R: It very often auto-opens when lid closed, after some seconds. (with the "....screen lock aborted") It MIGHT be related to the motion detector, as it seems easier to have it stay off when on a table. But there are no full correlation, at the best a tendency, but could be multiple factors, that effect when it triggers and when not. A not too slow 'close-open-close' on a table seems to work quite often.
    2 points
  47. As you mentioned - it's all about the scancodes. This means manufacturers can make all keyboards the same and just put different labels on the keycaps to make mass production cheaper then rely on customers to chose the matching language setting in their operating system. The ISO physical layout (tall enter, split left shift) has many language variants, ISO-US keeps \| near where it is on an ANSI (wide enter, big left shift) board while ISO-UK one puts \| next to left shift and ISO-FR (French AZERTY) and ISO-DE (German QWERTZ) don't have a \| key at all. From what I've read I find it ver
    2 points
  48. I think @tliebeck's question (which is also the thread title) is quite easily answered: because we need at least two keys which standard keyboards usually have on a sixth row above our five rows, Esc and Del, and unfortunately there doesn't seem to be a standard for five-row keyboards which include those two keys. Plus, there's at least one special key for Android which has no analogy on PC keyboards. That said, Fxtec could perhaps have found some existing keyboard on one of the many existing laptops/notebooks/netbooks than would have made a better model for our keyboard than what we have
    2 points
  49. (Just downloaded, will flash within minutes ๐Ÿ˜) It did not install with the previous AICP-q boot.img, but it did install with the latest LineageOS 18.1 .img open_gapps-arm64-11.0-pico-20210712.zip installed as well. So now i'm back on AICP after being 'unfaithfu'l using LineageOS 18.1 for some weeks on the 'final sample' too. Lovely. ๐Ÿ˜ Battery saver "Battery may run out soon ....blah blah .... 40%" I would say that kicks in a little early.... But it was when it still installed apps in the background, so the projected remaining time was low as could be expected. I usually turn
    2 points
×
×
  • Create New...

Important Information

Terms