Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/25/2022 in Posts

  1. FTW.. to get into Fastboot Mode via buttons is really difficult. But after several trys with different timings it worked like described: "Then pick your clacky Pro1x, power it down, hold down [Volume -] and [Power] until it boots. It will show a dead droid logo. From there, hold [Power] and without releasing it, hit [Volume +] briefly with another finger. From the menu that just appeared, select Bootloader. The phone will reboot into bootloader mode, where you can use fastboot commands" I'm back with DROIDIAN. 🤓
    5 points
  2. Hi, Eugenio from Droidian here: Did you happen to run a dist-upgrade via the command line before doing that? Unfortunately there is an ongoing GNOME migration in Debian testing that required rebuilding of some packages (both in the Droidian side and Mobian side). It might have happened that a dist-upgrade would have asked you to remove some packages such as phosh/phoc. The Droidian-side packages have already been rebuilt, for the rest we should wait Debian/Mobian. It will sort itself out in a few days. To aid that, I've pushed an hotfix that will help in keeping the installed
    5 points
  3. I tried out Adam's latest kernel tonight, and I'm glad to report that although I still can't get the more recent UT kernels to boot, Adam's does boot, and also I've got Waydroid up and running just fine. Whether or not it's in a usable state is a different question of course. 🙂
    2 points
  4. For what it's worth, another update of Netflix (to version "8.35.0 build 19 50257") just came in via Aurora. Runs just fine on rooted, GAPPs-free LOS 16.0. Seems like it is indeed just a matter of circumventing the Google Play store ...
    2 points
  5. A new build of good-old LineageOS 16.0 for our good-old Pro1 (835) is available at http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 2022-08-23. It contains backported AOSP security fixes up to patchlevel "1 August 2022". I bumped the Android security string to reflect that. Seemingly, people are slowly losing interest in Pie. While the AOSP patches since May have been backported and have undergone basic testing (by me and on other devices), they have not been merged into the official LOS 16.0 tree yet, due to pending code review. While I a
    2 points
  6. I think my Pro1X just did this a few minutes ago. Suddenly appeared powered-off and unresponsive, had to try holding the power button a couple times before it woke back up. I checked dmesg and saw a huge number of these lines: [ 2836.383934] mas_ioctl: cmd=0x80044d22 [ 2836.383941] mas_ioctl: end. [ 2836.394128] mas_ioctl: cmd=0x80044d22 [ 2836.394137] mas_ioctl: end. [ 2836.404314] mas_ioctl: cmd=0x80044d22 [ 2836.404323] mas_ioctl: end. [ 2836.414717] mas_ioctl: cmd=0x80044d22 [ 2836.414726] mas_ioctl: end. I have no idea what this is referring to.
    1 point
  7. Glad that you managed to reflash! You should be able to reliably reach fastboot mode directly by powering down the device and then holding down [Vol-], while plugging in an USB cable.
    1 point
  8. Ha, I was about to reply, but I recognize this excerpt above. 👀
    1 point
  9. Would be nice to disable fingerprint reader while it is not required for unlock or authenticate... I'm having trouble when holding the phone with right hand and typing on the keyboard... My palm seems to trigger fingerprint reads all the time which causes flickering and strange behavior. I know it's the perfect place for landscape mode, but come on... It's a mobile after all... I would really like to not use the physical keyboard, just to say hi to someone or type short answers like Yes, No... Also I don't see any good reason for keeping active this sensor all the time while it'
    1 point
  10. I ran into this the bit I used it. I found the location great in both landscape and portrait. Though I noticed that I had to tap the power button before I could finger print unlock...was it just me?
    1 point
  11. Oh well, I feared that at sort of thing when I'd read about China's absolute lockdown policy on covid diagnoses. I suppose I'll just have to sit tight a bit longer.
    1 point
  12. Pro1X takes better photos than Pro1 using stock camera application but Pro1 takes better photos than Pro1X if I compare Pro1X stock application to Pro1 using Google Camera (GCAM mod of Pocophone F1). It would be good to compare an optimized Camera software on both devices anyway. I don't know if @DieBruine has tried GCAM mod but it really worth a try.
    1 point
  13. The Pro1X i got my hands on is not retail, but would be interesting if some that got retail version of both, could post some sample images.
    1 point
  14. It's not just FxTec. I think 40% from China and Hong Kong is delayed. I am waiting for a couple of Indiegogo perks, my Fiido X v2 and my engraved Pro1x also. Mind you, they posted the engraved back cover months ago. Yet none of those are shipped yet. On the other hand, I personally can live with first come first serve. If you ordered a "regular" Pro1 and never received one, you should be first in line. Just my 2 cents on the matter. I for one can't wait for my Pro1x. The Pro1 camera was unsufficient for my taste.
    1 point
  15. this time i wil be positive and say i think we wil receive our devices starting of december i was expecting problem with creating/manufacturing batch 2 ( mainly financial ) but it seems shipping wil hold up the delivery if anything we cannot or ever blame any manufacturer / seller to controll shipping shipping isues wil happen regardless of shipping company
    1 point
  16. …To those that are blaming FxTec for the shipping delays, see e.g. Astroglide https://www.indiegogo.com/projects/astro-slide-5g-transformer/x/16576339#/updates/73 “There are still limitations on courier shipping from the warehouse in Hong Kong.”
    1 point
  17. After Playing a little bit around on SFOS, the virtual touch keyboard isn't shown anymore when I focus on text inputs. Just the numeric keyboard to enter the security pin is still shown. The hardware keyboard still does work. Has anybody an idea how to get it working again? Changing layouts, installing the dolphin keyboard and such things don't have any effect. I tried to kill the maliit-server on the shell and restart it manually, I get some error messages: WARNING: bool MIMPluginManagerPrivate::loadPlugin(const QDir&, const QString&) Error loading plugin from "/u
    1 point
  18. @bryan could your random shutoffs be related to this? Not actually a dead battery, but a problem returning from sleep? Doze? I don't quite understand it but it's something to try.
    1 point
  19. I was experiencing the 100% battery issue, but never had any sudden power-offs, and I'm using the phone nearly all day at this point. The full-for-too-long issue seems to have vanished since I've flashed the current beta ROM, but I am not certain it would address your primary fault.
    1 point
  20. I'm not a Windows or Mac user, but I'm pretty happy that we have two tools at hand, including one that's multiplatform, fully open source and based on an open source language. The alternatives to that would either be (i) nothing or (ii) proprietary software, which I would view as a much higher "infection" risk. I mean, at some point we'll have to install something on our machines to perform operations to reflash our Pro1(x), there's no other way, and them being flashable easily was one of their selling points. Python also is a language that can easily be containerized in a virtual enviro
    1 point
  21. Yes, i missed something. With adb reboot bootloader I had to switch to the bootloader and run there the flash script. Now I have droidian on my pro1-x 😎
    1 point
  22. @matf-kabouik i confirmed it is the pro1x image thanks @tschakram. I thought that would work but I get the same result. Droidian logo appears, pulses briefly then dims slightly and disappears. I'm running these commands. ╭╴╴╴liquidvx@UX482:~/Downloads/droidian/droidian-OFFICIAL-phosh-phone-fxtec_pro1x-api30-arm64-24_20220804 ╰╴$ fastboot format:ext4 userdata Warning: userdata type is raw, but ext4 was requested for formatting. mke2fs 1.46.2 (28-Feb-2021) Creating filesystem with 59072979 4k blocks and 14770176 inodes Filesystem UUID: 102e9c78-666e-4084-8ba7-6ed2902f2a66 Superbloc
    1 point
  23. I've had my Pro1X since Aug 1, and noticed today that the fingerprint scanner had separated from the case. It still works; the electrical connection is on the other end of it. I've taped it down with a bit of electrical tape for now. What's the best way to stick it down permanently? Should I disable it until it's been fixed? I don't use it anyway.
    0 points
  24. I dunno... I'm pretty darn frustrated....🙃
    0 points
  25. Expansys/FedEx have not even sent out the Batch 1 they got from FxTec yet.... Really annoying, but not much FxTec can do I guess. I'm in the first dozen on IGG, yet I still have not got a shipping mail, despite FxTec told me that Expansys has processed it a fortnight ago... They are as frustrated as we are on the situation.
    0 points
×
×
  • Create New...

Important Information

Terms