Jump to content

Rob. S.

Members
  • Content Count

    1,053
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Rob. S.

  1. Of course I don't know how you use KDE Connect, but, while wondering what makes the Android app developers think they should tamper with the keyboard functionality, perhaps Warpinator might do the job for you, if it's mostly about file transfer? It's what I use for connecting my phone with my Linux desktop. (Which, for me as a Linux Mint user, is of course as straightforward as your using KDE Connect if you're a KDE user.)
  2. Getting upset helps noone, least of all yourself. All we can do in such a case, after two years of complaints publicly and directly to Fxtec's support, is actively trying to help them by pinging Erik. Your prime mistake here is to somewhat naïvely think Fxtec wouldn't know that their support sucks, and how it sucks, and that therefore they could simply improve things by "learning" something. As I said earlier, at this point we can call ourselves lucky that they even still exist. The main consideration of all of us who still are waiting for a device (or, like me, two) should be that
  3. For completeness 🙂 : So there we go – January at the earliest, more probably February.
  4. It says "once a month". What is there to misunderstand? It means Nov 30th would be sufficient even if the last update would have been Oct 1st.
  5. Quite well, actually. Earlier this year, to be a bit more safe, I applied a display protection foil after the phone had come back from a screen replacement. Next thing I did was trying to swipe some dirt from the display, which resulted in swiping the phone from the table, as the screen protector was much more sticky than the screen alone—making the next display replacement necessary... Then I thought, why not put something like that foil on the back of the phone instead of the front? I experimented with commercially available back cover protector foils for some other phones, but they did
  6. Are you on stock Android? Don't know about that, but on LineageOS 18.1, in "Settings" -> "System", the last item is "Touchscreen", which lets you set (in three steps) how wide a margin should be insensitive to the touch. Personally, I'm mostly ok now after setting it to 32. Oh, and I've reduced my drop rate (which used to be very similar to yours) to practically zero by covering the whole back cover surface (minus camera) with transparent packaging tape!
  7. @Val I'm not forgetting anything, and I'm not confusing "secured" with "bought and received", either. Also, while I agree that "they should have" done that in a perfect world, and I add that they should have done a lot more and should be doing a lot more in general, and also a lot of the things they're actually doing could and should be done better, this world isn't perfect, and with even just a remote idea of how the smartphone business works no one would have had any right to assume that they were even still alive after the Pro1 production had hit all those obstacles, let alone have substant
  8. Successfully installed OTA update 18.1-20211122-NIGHTLY-pro1 yesterday, but had that hiccup from October again.
  9. You obviously didn't quite understand what he was saying. He said, in addition to the general problem of reliably getting fully-functional copies of the display panel itself (for which the sellers on Aliexpress do not qualify), there could also be a shortage in some of the additional parts that make the screen assembly Fxtec are offering as a replacement, which is substantially more than just the panel. The assembly also includes the casing plus several other components like front camera and speaker. You do have noticed that there have been supply problems worldwide for quite some time wi
  10. If you go to the project's Indiegogo site, there's a menu bar "STORY – FAQ – UPDATES – COMMENTS", and when you select UPDATES, you'll see that there have been frequent (monthly) updates, with the last one being from 28th October. You don't need an Indiegogo account to read them. Also, I've tried to copy those updates as they appear (which I also receive per mail as a backer) here in the forum into this thread: Just for the record, my personal state in this affair is that I'm waiting for two phones, one Pro1 ordered per website in September 2019, and one Pro1X ordered through Indiegogo in
  11. By the way, to me it seems some (if not most or even all) of the cheap screens which come through Aliexpress have a minor flaw in that the lower (seen in portrait orientation) two corners of the screen are not fully active, a small outermost part is blackened. While some of us might not even notice let alone care (only some sellers even mention this), it's something the manufacturer might not want to accept. And screens without such small faults might indeed be difficult to get for anyone at this point, not just FxTec.
  12. Even though Fxtec runs the website, this is just a user forum; Fxtec does not publish official statements here. Still, they do publish monthly updates about how the preparations for production are going for the Pro1X on Indiegogo, which have been copied into this thread here, too: Indiegogo backers also get that information by email. It just seems that the people who ordered straight from the website instead of using Indiegogo don't get as much love...
  13. Spoken too soon; in the morning (now on 18.1-20211115-NIGHTLY-pro1), while connected, the battery was down to 20%, there was no flash symbol in the status bar and AccA again reported "not charging".
  14. Ok, "as it won't build on OSS builds" indeed doesn't sound very promising...
  15. I just tried it with an USB C hub that includes an HDMI socket which works well with my netbook/laptop (a cheap Teclast F5), but instead of sending an image to the TV, it provoked a cold shutdown (switchoff) of the phone when I connected the HDMI cable...
  16. It's still a capable phone, though, and it's also still one of a kind with regard to its specific design with that physical keyboard. That's why people want it, and that's why those who use it also mostly love it, despite quirks, issues and the company seeming to be overburdened with the support. It is definitely not a device for people who would want to boast with the latest and greatest specs (which they might not even need anyway), today obviously less so than when the Pro1 originally was introduced...
  17. Now that you're reporting this, I've had a few (very few) situations over the last few weeks which were slightly similar, but not as severe. Screen going black while in use, needing a press of the power button to come on again, or screen becoming touch-insensitive until switched off and on again with the power button, and there might have been one occasion or so in which such a situation needed a reboot, too. I'm on LineageOS 18.1, and for me this somehow rather felt more like software rather than hardware, but that's just an impression.
  18. Following up to my last post: since the 18.1-20211108-NIGHTLY-pro1 OTA update on Monday I haven't observed any charging interruptions so far.
  19. ... of which the latest is: However that goes, I guess it would be sensible to consider that the shipping backlog goes back to 2019 for some of the original Pro1 orders which never were shipped and then were changed into Pro1X orders (this includes my own first order). So even if shipping would start at the end of this month, someone who ordered their device just recently will probably not be served with that first batch.
  20. Thanks, this is really good to hear! 🙂
  21. Just for the record, yesterday I had another occasion of the phone not charging, with the state remaining "discharging", although the cable was connected and live and the charge level was below the discharge limit. After reboot, charging restarted. The most obvious difference to the earlier behaviour, by the way, is also a slight improvement: While earlier a failure to charge (along with entering the "not charging" mode) still showed a battery plus flash symbol in the status area as if it was charging, now the flash doesn't even appear, so I can at least see that it doesn't charge without
  22. If I remember correctly, I had it replaced twice and replaced it myself one more time (always just the bare screen like they sell it on Aliexpress). I don't think there's any sticky grid or rubber cover left now in my phone. To make up for that somewhat, though, I did leave the camera window protection film on the inside of the new screen, now giving me a nice soft focus effect...! Other than that, everything works well, and I don't miss the proximity sensor's function that much, so I'll leave it like it is for the time being. But is seems like I should try to get one of Fxtec's complete
  23. Does anyone know what this is about the camera and the proximity sensors? I didn't do anything to the camera and it was still there after the last of several screen replacements (this time doing it myself), but now, thinking about it, the proximity sensor has long since stopped to function on my device?
  24. Did anyone else notice a slightly different behaviour with charging after the latest update? While I cannot say yet whether something changed with the intermittent failures to charge although being connected (the ominous "not charging" state instead of either "charging" or "discharging"), it seems to me that it takes a bit longer now until charging starts after connecting the cable; also, I've had several occasions in which charging wouldn't start after connecting, with the state still "discharging"? I cannot totally exclude the possibility that in some of those cases AccA was keeping th
  25. Nor had I, but it is indeed good to know—if just because the few times I experienced something like that now were probably not caused by worn-out hardware, which I'd otherwise would have expected...
×
×
  • Create New...

Important Information

Terms