Jump to content

Rob. S.

Members
  • Content Count

    1,042
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by Rob. S.

  1. Sorry, forgot the irony tags. I was commenting on the "postponed" aspect there...
  2. Because shit happens. Just because it didn't until now, it doesn't mean it won't or couldn't. Also, people make mistakes, which, I guess, includes you, too... I completely agree, like others already did, too. Still, I'm afraid there's not much we can do to make Lineage change their policies, and getting our knickers in a twist about it doesn't help us, either. As all of this is an open source thing, I suppose it means taking things in our own hands, and finding a maintainer for continued LOS 16 and 17 updates like the one @Hook mentioned for that Samsung phone. Perhaps there are more p
  3. @claude0001 I guess I have an – if only faint – idea of what you're doing there... And, sure, if that were what I'd need in a phone to be able to use it productively for what I do, I might even try something like it myself. I just wouldn't get my expectations up as to its working in a stable way for a longer period of time. Neither would I rely on such a massively tweaked system as my single phone... Incidentally, after three to four years in productive use, right now I have to upgrade two Linux servers the OS versions of which stop being maintained. Even though it's a fairly normal thing
  4. @lawliett No, that's definitely not glass, it's a flexible plastic, just like the one I ordered earlier – the delivery of which has been been postponed, with the new estimated period already nearly over, too. (If it was specifically designed for the Pro1 instead of the Elephone, one might suspect that might be to better fit the specific device.)
  5. Does 18.1 (using US or US Intl layout) let you select special characters on the screen on long-press of a character, like à á ä etc. when long-pressing 'a', like 17.1 used to? That never seemed to worked on web pages, but it would be better than nothing. Did you have to somehow remove OpenGapps or something before flashing MindTheGapps?
  6. No idea why the postponement... Perhaps they want to reserve themselves the option to make small changes to the screen should the redesign of the Pro1X require them. (Whether or not that might introduce incompatibilities to existing devices – which would be, of course, bad for those who wanted the screens for existing devices...) On 16 March I asked info@fxtec.com whether they could send me a spare screen for my Pro1, but I have yet to get an answer (or even an acknowledgement of receipt, like the ones I used to get for earlier mails on other topics). That's why, in the meantime, I o
  7. I'm not sure I understand this, could you elaborate a bit further? (I don't have much experience with root and Magisk; the only device I have had Magisk on so far didn't get any system updates anymore anyway – and with the latest Magisk app update Magisk itself has stopped working there, too, but that's something else again...). Do you mean whenever there was a LOS update you needed to flash Magisk to the inactive slot?
  8. That's something I would be interested in, too. LOS 17.1 was painless for me so far with OTA updates – but then again it was non-rooted, no Magisk, just LOS + Gapps. Now that today one of my mandatory banking apps (mandatory even for entering internet banking on the PC) has stopped working, complaining about a modified software/firmware, I'll need root plus the stuff that hides both root and the fact that it's an alternative ROM rather sooner than later. I guess changing the update procedure to sideloading the updates like @Hook has been doing would be ok for me, although I'd be even
  9. Just on a side note, I have rather small hands and I still like the size of the Pro1... The screen can't be big enough for putting it to good use, and it didn't really take long for me to become comfortable with typing with my thumbs.
  10. That would explain @ivoanjo's experience with 18.1. I'll be staying on 17.1 for a bit longer, then, I suppose.
  11. Surely looks like a defective camera to me. There's no way a phone camera with its huge depth of field could render one corner halfway sharp (bottom right) while blurring the rest of the image if there wasn't something bent out of shape in it.
  12. I did. Nothing seemed to change. None of the built-in layouts seem to do anything. With LineageOS 17.1 and physical keyboard set to US Intl., I can use Sym + ' and then e to get é. Or Sym + " and then a to get ä. No root here.
  13. Did you try LineageOS with its US Intl. setting for the physical keyboard?
  14. Oh, I see! Interesting! It could be then, of course, that Fxtec would already sell their replacements "pre-flashed"... But still I don't think they'd intentionally try to make things difficult for those of us who want to replace only the panel itself. It would go against their self-repairability promises with which they started out. Also, it seems they're out of display replacements themselves, as on IndieGogo these are not expected to become available before August...
  15. If I understood all the past information correctly, Fxtec is in fact supportive of repairs with those cheap parts. Also, I believe their own screen replacements (the added value of which is the easier replacement as they include the screen casing with all that's inside) needed the changed driver, too, from some point in time onwards, and someone who's using LineageOS, which Fxtec also officially supports, would need the driver package, too, even if they got the screen replacement from Fxtec...
  16. From what I've heard in the meantime, there must have been some confidentiality restriction on those files, whatever the reason for that may be. Perhaps EvilDragon has become aware of that, too, and maybe that's why he doesn't react on further requests here, either. If communicating with Fxtec would work as we would like it to work, we could get into a discussion with them about it, but as it doesn't, I wouldn't get my hopes up. Still it wouldn't hurt to try...
  17. I'm in not quite the same but remotely similar kind of a situation, with a device I got second-hand that had already been flashed with LineageOS, but without root, and sooner or later I'm going to want Magisk and hide-root and Xposed to pass SafetyNet and enable Google Pay and the security token app for my employer's VPN. From what I've read, I'd say we need forget about TWRP for the time being, though, because there's no official version yet that would handle decryption, so it's no use for backups. Also, I don't know whether someone is working on getting such a fully-functional TWRP for
  18. Thanks @all for the tips regarding protection. I've already ordered screen protectors. I already do have two flip cases which basically fit, but I'm hesitant to use one because of the need to customize the holes and also they significantly add bulk, much more than the flipcase I used to have for the Moto Z3 Play which fit like a (surgeon's) glove... But I guess I'll give one of them a try, after all. (I've also been playing with the thought of buying a 3D printer just to print my own Pro1 protectors 😉 )
  19. I did so, but @EvilDragon currently doesn't seem to be reachable through forum messaging (or maybe I'm too impatient)... Is there perhaps someone else with the file(s) (and the description)? I dropped the phone again today and now the display has a slightly splintered corner... I'll definitely need to get some protection for the phone, going forward... And I wouldn't want to replace the screen before making sure I can still use all of my apps...
  20. Would it perhaps make sense for @tdm to include that in LineageOS and AICP, too? If it doesn't break something with older displays, that is...
  21. For anyone who might be interested in a Pro1 but finding @Devion's offer too cheap, there's one of three Pro1s left someone from Japan is selling on ebay for $1,450 / EUR 1,232 ... 😉
  22. Just on a side note, it may or may not have anything to do with this – I have experienced anomalous behaviour with my Moto Z3 Play a few times which seemed to relate to either SIM card or SD card not being properly (physically) connected. Removing and reinserting the card tray and rebooting usually returned things to normal. This came to my mind now as I remembered the Pro1's card tray to be quite flimsy (not that other phones' card trays would always be more sturdy).
×
×
  • Create New...

Important Information

Terms