Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/22/2023 in all areas

  1. Definitely F(x)tec is NOT scamming us. They are just struggling with this project and things have not gone as they planned (SoC change etc). Sure, F(x)tec has done mistakes during the journey but I think that they are trying very hard with limited resources. I received my Pro1 after long wait and during this week I am supposed to receive Pro1-X. Let's see how it works compared to Pro1.
    7 points
  2. This is a bug in the stock OS, and happens because they modified Generic.kcm despite the comment at the top of the file instructing them not to. We have fixed this problem in LineageOS here: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver-19.1 Hopefully F(x)tec can include these changes in a future update.
    5 points
  3. Some of the modifier keys are mapped a little differently from stock, but the driver is still the same one as F(x)tec ships. The most important differences are the 'F logo' key is mapped to META, and the SYM key is mapped to AltGr (ralt). The old behavior of the 'F logo' key (KEY_HOMEPAGE) has consequently moved to 'F logo' + ENTER, but you can now use any of the other keyboard shortcuts built into Android. This list is contextual, and 'F logo' + '/' will bring up the list of shortcuts defined by the current app. FWIW, this is the same mapping as LineageOS uses on the Pro1. Among other mi
    4 points
  4. When you are worried about privacy, the single most important step is to get away from manufacturer-taintedbranded ROMs, Google Apps, and the Play Store. A publication demonstrating that by network analysis of phones' upstream traffic has actually been posted here before. Privacy-wise, you can essentially get on-par with all those self-proclaimed "privacy-first" OS's by simply installing LineageOS without Gapps and using F-Droid for your app needs. Sounds hard, and few do this, I know. On the other hand, If you think you can't live without Google services and Google apps, no amount o
    4 points
  5. Until we are using tdm's driver, there will be undesirable interactions between the F(x)tec's custom keymap and the keyboard language selection in Android. Have you selected a language and layout as directed by the persistent notification to "Configure physical keyboard"? Don't do that. 😜
    3 points
  6. I can attest that a Pi4 works flawlessly so far for flashing for me. Just had to do: sudo apt-get install -y android-tools-adb android-tools-fastboot to install the tools needed.
    3 points
  7. Believe it or not, this is how we used to create OS distributions back-in-the-day. Fattire even wrote a short poem about it: So Many Zeroes! A Children's Book By Dr. Seuss (a.k.a. fattire) Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review. "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?" And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor. "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!" So Blue packered his tracks with a /
    3 points
  8. As have others on Discord. Sean says it's "moderately stable" which is good enough for me. Probably not that different than the first unofficial test versions of Lineage 16 we got from TDM for the Pro1, and those were rock solid. As soon as I have a Pro1x, I'll be installing it.
    3 points
  9. Not a scam, just really unfortunate company. Chen who started to make dream come true is one of us: real linux and tech enthusiast and nerd/geek. Just a lot of bad luck. I am one waiting for my device still. From indiegogo crowfund.
    3 points
  10. @Noob : click sound, yes. I would say no mecanic problem here. I glue one touch with cyanocrylate a few months ago as he felt, and had no issue since. I test with three press on different touch like 'aaa eee ddd ccc sss ooo mmm....' and see what happens, then I found this : when pressing the bottom part of the keyboard the bug disappeard. As far as I understand @veRYANgry solve the problem with tightening the two bottom screws, wich could be related to my problem.
    2 points
  11. Me too! Hopefully sometime this year 🤣
    2 points
  12. (lineage-20.0-20230123-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)
    2 points
  13. BharOS seems like a student project that got wrapped into a political stunt. For example The Indian Express includes a link to the announcement that calls it a step towards "Atmanirbhar Bharat", a political slogan from Narendra Modi. But on a completely practical level, it won't work at all with Google apps, you can't download it for any device, and it may only support one or more Google Pixel phones when you can.
    2 points
  14. Thanks, but didn't help. Just dawned on me that I have a Pi4 sitting on my desk (running HomeAssistant and a Plex server). Works great from that! EDIT: Lineage 20 install worked perfectly! Thanks to everyone that helped.
    2 points
  15. FYI: https://forum.xda-developers.com/t/lineageos-20-for-pro1-x.4543997/
    2 points
  16. While all our work is public, we don't necessarily post a neon sign saying, "Break ur phone here!" 😉 The Pro1-X work is moderately stable now and has been moved to the official LineageOS org on GitHub: https://github.com/LineageOS/android_device_fxtec_pro1x https://github.com/LineageOS/android_kernel_fxtec_sm6115 You are welcome to use these for your own builds, but please be prepared debug any problems yourself. There are a few outstanding fixes on our gerrit, esp. this topic: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver Also, please remember that although we work
    2 points
  17. As already mentioned before, I use my Pro1x not only for data access (both regular mobile networks and Wifi), but also for calling (outgoing and incoming) and sending text messages using the traditional SMS (and also MMS if necessary). I disabled using VoLTE (voice over LTE) and also changed the priority for voice over Wifi to make it the last resort in case of Wifi being the only connectivity available (i.e. no mobile network coverage), because the call quality was rather bad with both VoLTE and voice over Wifi, but it works for me without any considerable issues apart from this (in addition
    2 points
  18. There is no need to root stock, just to install LineageOS. For that it would have been enough to just unlock the bootloader, no need for Magisk and boot.img patching ... On the other hand, if having root during use of the phone was your goal, you will find that in your newly flashed LineageOS, Magisk and su are now gone. You'll then have to re-install Magisk and re-do the boot.img-patching procedure (this time using the boot.img from payload.bin, contained in the lineage*.zip you used for sideloading).
    1 point
  19. Ahh, that's it, thank you! I ran fastboot right on the "START" screen and it worked. Even worked on my X270 without needing to boot up the Raspberry Pi.
    1 point
  20. I agree with @Hook. That screen in the first screenshot should be shown while you use fastboot to flash the boot.img. adb, on the other hand, does its job only from recovery, not from that bootloader screen. That said, just flashing the Magisk-patched boot.img (which I understand is what you are trying to achieve) does not require any action to be performed from recovery. You should not go there at all for this. The no-command-screen usually indicates that the recovery image fails to boot. It normally should not be shown at any step of a reflashing procedure, and probably indicates t
    1 point
  21. I'm a little confused by your descriptions. When you reboot to bootloader using adb, you should get the bootloader screen which is the same as your first screen shot way above except I think it says "START" in green at the top. I don't think it matters if you use the volume control to change what is at the top to "RECOVERY mode" because those are options you are scrolling through, but nothing changes unless you press power. That bootloader screen (with "START" or whatever at the top) is the bootloader. That is where fastboot is used. Going into recovery mode (by pressing the power button)
    1 point
  22. Mine would also not boot. Left it connected to the charger and used volume down + power. After a couple of minutes it tried booting. But the battery was completely dead. So after a couple of retries it finally was able to boot fully. Give it a try.
    1 point
  23. Thanks for testing the Pi4 in this respect. I do not have any of these and always worried its USB-3.0 parts might behave differently when compared to the older models' USB-2.0. Good to know this is not the case. I'm not sure which OS you use on your RPi, but since 'buster' the respective Debian packages are just called "adb" and "fastboot". I.e. in recent Raspberry Pi OS, one would rather do sudo apt install adb fastboot
    1 point
  24. I have always only used "B" models, which come with 4 USB ports and Ethernet in addition to WiFi. This of course doesn't mean that the A+ will not work for your purpose ...
    1 point
  25. I have an X250 and could never use fastboot from it (original Pro1, Linux also here). Probably ... There all kinds of tips and tricks (use external hubs, remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back.
    1 point
  26. fastboot is way more picky about the USB connection than adb. If @Casey's suggestions do not help: Various RaspberryPi's have been 100% reliable for me when it comes to flashing Pro1(X) -- I've never again used adb/fastboot from my PCs since I found that solution.
    1 point
  27. I also couldn't get it to work and gave up. Same timeout errors as you. I just rooted the phone with Magisk and used the following command to backup all the partitions to the sdcard: mkdir /sdcard/backup cd /dev/block/platform/soc/*/by-name for filename in *; do if [ "$filename" != "userdata" ]; then echo "dd if=$filename of=/sdcard/backup/$filename.dd"; fi; done This prints lines with the dd syntax to back up all partitions. It does not execute them for you. Please check if those lines fit your expectations first and then run one or all of them. I then got the backups off the
    1 point
  28. No idea. I am coming directly from lineage-16.0. But you are right, according to user reports on the net, 18.1 seems to have broken the built-in sshd. This has nothing to do with the Pro1-X.
    1 point
  29. sshd is present in /product/bin, with sshd_config in /product/etc/ssh. I don't use this myself, but adb root && adb shell /product/bin/sshd -dddDf /product/etc/ssh/sshd_config doesn't behave the way I would expect. Did this work in 19.1? A quick check of old versions suggests this doesn't work in 19.1 or 18.1 either, so it may have been broken for a couple of years 😞 Since this isn't specific to the beta test you might open a bug report, following the instructions here: https://wiki.lineageos.org/how-to/bugreport
    1 point
  30. Update: Just flashed the new ROM dated 20230124 via sideload smoothly. Level-3 keyboard modifier ("yellow arrow") keys now work correctly, with more keyboard options to come according to the XDA thread. Awesome! I also successfully rooted using Magisk. Yay! On the downside, I find that lineage-20.0 seems to no longer provide an OpenSSH-server . I think I will need that to re-implement the full functionality of my GNU/Linux-chroot setup on Pro1/lineage-16.0. I see there are Magisk modules providing sshd nowadays ... probably will have to get into that ...
    1 point
  31. Me too. Installation was smooth using the instructions linked above. Seems stable (i.e. no crashes)up to now, but I haven't played much with it yet (Pro1-X is not my daily). LTE/GSM connectivity is just as bad as in stock -- as was to be expected. On the positive side, WiFi scanning again works correctly after 2.1.5-GMSless had somehow broken that for me.
    1 point
  32. I tried to flash the newest builds today again using my notebook with debian linux. Everything went fine with both latest builds, Focal and Xenial. I failed with another computer with windows 10 from my parents when i visited them. Also it was possible to update the build to latest version. If you update you will get to the latest xenial (16.04) version, even if you are testing the focal (20.04) build. One problem with this device regarding the touch gestures of ubuntu touch is the curved screen. Gestures work great in landscape mode but in portrait mode it is a little bit difficult. I pe
    1 point
  33. https://forum.xda-developers.com/t/lineageos-20-for-pro1-x.4543997/ Scroll down :)
    1 point
  34. Donate link worked fine for me using Pay Pal. Where is it? 🙂
    1 point
  35. Donate link worked fine for me using Pay Pal.
    1 point
  36. And finally there's a donation button - the devs are real 😃 Not clicking it until someone tests it though, I would but still waiting...
    1 point
  37. I've installed the 20230120 image on my device, and so far everything is going nicely. No (new) problems to report. However, as anticipated, early indications are that this build does not improve the LTE situation, so I will continue to keep my device locked at 3G.
    1 point
  38. (lineage-20.0-20230116-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)
    1 point
  39. Yet another way how to backup persist (or any other) partition even without PC, with rooted phone and Magisk: Install Magisk module "backup" and reboot. After that using some terminal app in phone (I use Termux), first gain root access: su and then enter backup persist it will create file persist.img in folder /backup of your phone's internal storage. The path can be changed of course. I suppose same can be achieved with dd command, but the above is easier. Instead of terminal app in the phone you can of course use adb shell from a pc.
    1 point
  40. Alright, after toying with it for a few days I have cracked dual booting and decided to write up the steps myself. YOU WILL LOSE YOUR DATA DOING THIS. Credit to @order#10248 for proving the concept. First thing you will want to do is re-flash stock android on your phone. There isn't an official repo for this yet but @Waxberry has kindly provided one on this post. Download and extract the files from there and run the script fastboot_all.bat or you can download my modified linux version flash_all.sh. While that is flashing, download the latest version of Lineage here. Yo
    1 point
  41. You can try i don´t think you will get a refund. Im waiting since November... No phone and no refund...
    0 points
  42. funnily enough my tickets are also about payment
    0 points
  43. Also in the US on a T-Mobile SIM card. Microphone does not pick me up at all unless speaker phone is used.
    0 points
×
×
  • Create New...

Important Information

Terms