Jump to content

Rob. S.

Members
  • Content Count

    1,053
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Rob. S.

  1. You're right, they're two different things. Then again it might still be a specific problem of your phone; I've tested calls to both mobile and landline connections, calling as well as being called from the other phone, and no such issues came up in any way...
  2. Just to be sure, I suppose this is exactly what should NOT have happened with the fingerprint sensor ribbon cable of my old Pro¹? I replaced the defective USB module today, and I wanted to see if I might be able to get the fingerprint sensor working again, too, which had stopped working months ago, but I guess I can forget about that now. Except if Fxtec might be able to sell a back cover including buttons and fingerprint sensor as a replacement part, perhaps?
  3. The question has also turned up on XDA today, with links to the necessary boot.img file, which indeed seems to relate to the file @Casey Cheung linked to here. The rest I'd suppose should be the same as for the Pro¹... (Personally, I guess I'll wait with root until LineageOS becomes available. Unrooted stock Android on the Pro¹ X so far is a much better experience than I expected.)
  4. That would be true if Android phones would be obliged to come with a light sensor designed and specified to report correct Lux values, but that is not the case. The app is taking readings from a sensor that never was designed for the purpose, just guessing what Lux value those readings might correspond to. If nothing reliable comes out of that, it's not the fault of the phone.
  5. It's Gorilla glass, and I doubt there's any phone on the market where it's easier to swap screens, provided you get the official replacement unit (which practically is the whole top part of the phone, replacement involves just five screws and a ribbon cable). As a cheaper option there also is the actual display available from sources like Aliexpress which is also not too difficult to replace, but involves gluing which carries the danger of a less than perfect result. Right, but there are other issues which may arise with protectors, and physically breaking isn't what you need to protec
  6. Anyone else observing this? Once paired and connected, I cannot make the phone 'forget' a Bluetooth device. At least not with audio devices which actively try to reinstate a connection with a controlling unit that knows it, like a phone or a laptop. Tried this with a 'Willnorn Soundplus' Bluetooth speaker and a 'Logitech' BT audio adapter for stereo systems. If I tap 'forget' while the device is connected and active, nothing at all happens. If I tap 'disconnect' and then 'forget', the device moves to 'previously connected devices' for a second, then immediately reconnects and
  7. Except for the shutter release button not having two steps (which is no problem for my as camera apps seem to start with continuous autofocus anyway), I have not seen any complaints yet with regard to the camera, or were there some? I've only found a small one so far; my preferred camera app ('Manual Camera') does offer RAW mode, but, when activated, either freezes or crashes when I try to shoot. The default 'Snapdragon Camera' app doesn't offer RAW mode to begin with. Neither does 'Open Camera', although it ought to, as long as the camera itself supports it. Might be a b
  8. Import VAT (129.16 € including administration fees) was 22.4% of the perk's original price for me, $679 which did equal 576 € in Oct 2020. Excluding administration fees (111.31 €), it's 19.3%, close enough to Germany's import VAT rate of 19%. I think I missed the 'super early bird' offer only by a few days back then 😉 but I found and find $679 to still have been an excellent price for what it is. By the way, without root, for the time being, and therefore without the ability to use the 'Advanced Charging Controller' daemon and app (ACC/AccA), I've reactivated my 'Chargie' devices to
  9. Here's mine, finally got it yesterday! Yay! 🙂 (QWERTZ 8/256 GB IGG order from Oct 2020, with the QWERTY 8/256 GB website order from Sept 2019 hopefully arriving soon too, though no tracking confirmation yet.) Coming from a (shifted) QWERTY, 8/128 GB Pro¹ with LineageOS 18.1 (didn't bother to upgrade to 19.1 yet with the Pro¹ X now actually within reach), I thought going back to stock Android would be a significant change for the worse, but so far I don't feel it is. Except for the right/lower speaker dropout problem, I haven't found any issues yet, which of course doesn't
  10. Doesn't sound like a contact issue for me, either. If it were, the dropout phenomenon wouldn't reliably go away with the volume dialed up, which it seems to do for the people who've been reporting this. Also, a contact problem would produce some kind of noise between loud and silent phases, which doesn't happen here at all. The cuts are absolutely clean. Is there even anyone who doesn't have this issue? I'm no low-level systems programmer, but intuitively I would locate the reason at the bottom of the driver stack, like in the speakers driver, if there is such a thing. Headphones-o
  11. I get wildly flashing triangle/circle/square icons when I tap and hold the square icon which is strange, but I get split screen mode by a short tap on the square icon, a short tap on the size-reduced app's icon, and then there's the split screen option. (I keep forgetting how this works as well, with so many changes in past Android versions...)
  12. Problem is, the Pro¹X they wanted to build actually was a Pro¹ — just with more flash storage (optionally), a blue casing and some of the already existing alternative ROMs preloaded, possibly after helping to make them more stable in case of Sailfish and Ubuntu Touch. But then they didn't get the SoCs anymore, even though, as I understand, the SoCs were paid for and promised. And as that SoC was already out of production at that point, they couldn't get it anywhere else, either. So they made a complete redesign for a current SoC. Which, unfortunately, loses compatibility with existing RO
  13. Another shipping update on Indiegogo: So we now know that there is a – albeit smaller – third batch coming, too.
  14. Today's delivery attempt failed because the delivery person wanted to collect import VAT (130 €). Next attempt tomorrow. (FedEx did not announce the fact, let alone give me the option to pay online beforehand, as UPS did last time I received something through them... )
  15. (OpenCamera supports it too, but obciously this is Pro1 and not Pro1X) On the Pro1, so does 'Manual Camera'.
  16. Just for the record, my Pro1 has a clearly felt two-step behaviour in the shutter release button. When I press it until there is a substantial resistance, the camera focuses, and then I need to apply more pressure to take the shot.
  17. I've become wary of screen protectors! I've told the story already, but some time ago, I applied one such thing right after I had self-installed a new display panel from Aliexpress, lest I would break it again. Next thing I did was trying to wipe some dirt off the screen, and with the swipe I catapulted the phone from the table onto the stone floor, because the protector had a slightly sticky surface whereas we know the phone's bottom to be dangerously slick. Needless to say the display broke again in the process! Also, my impression is that a screen protector might save a display from mi
  18. When I get my 2019 order which is supposed to come as a blue QWERTY 8/256 GB Pro¹X (no tracking confirmation yet; the 2020 order which *is* scheduled to arrive on Thursday is QWERTZ), I might be willing to swap, given it actually does come in blue.
  19. Right, and that includes hope for a longer support with security updates.
  20. That would be good if the user could decide for each app which keyboard mode it should use, but that's not how it is. In a browser, for example, I rarely find myself wanting the autorepeat feature, whereas I often need accented characters, and by tendency I find browsers using autorepeat mode instead of giving me the character selector. That said, with the Pro1 + LOS 18.1 I'm not missing the char selector box anymore, as I get all accented/umlaut characters I need with fairly easy-to-type Sym+Char combinations, but I'm sometimes annoyed when I would like to do autorepeat but get the chara
  21. If you still haven't received one when all of batch #1 has shipped, you will have a reason to complain, and rest assured I will complain in case the phone I ordered in Sept 2019 won't come in batch #1, too. If you cannot contain yourself for the few more days that will take, all the more so after you have been waiting for more than two years now, your fuse it too short. And then tell us which other tiny, but "thriving" and "efficient" company has been denied an already promised supply of SoCs, making scrap out of their mainboard, in place of which they then had to create a completely new
  22. You can email fxtec.(info@fxtec.com) I'm pretty sure they have some. Right, that's how I got mine (together with a USB-C module that eventually has become available as a replacement part, too, just on time before my current phone would completely lose its recharging ability) 🙂
×
×
  • Create New...

Important Information

Terms