Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by EskeRahn

  1. (lineage-19.1-20220530-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313)
  2. I'm amazed by their perseverance too. The small group take a lot of beating from angry users, and way too little praise, IMHO I really hope they will continue to both produce PKB phones and support them. If there will not be a successor I hope they will consider crowdfunding extended phone-support as long as possible for the chipset and security update. . I have no idea what a year of support / minor development would cost, but they could come up with a number and see if we are enough that are willing to chip in. As a stretch goal they could offer those that chipped in some special rate
  3. I think they more or less will process the orders, in the same order they were made. If the produced layout batches allow it. I have no idea if they can save some shipping or custom handling fees in 'bundling' orders with close by destinations, if so that could potentially affect the order slightly. But this is all guessing as is the time it will take to produce all needed to fulfil pending orders, as we know neither the size of the backlog nor the production rate.
  4. There is likely to be quite a backlog before any device ordered today can be delivered, so not unexpected really. But good that it has been updated from the old estimate that was there before.
  5. I agree with you, I was surprised that it did not require a factory reset. And for my case I think the mess I had was due to changing from OpenGapps to MindTheGapps simultaneously. Had I reflashed latest 18.1 with MindTheGapps before the upgrade to 19, it might have worked smoothly. (OpenGapps is not yet available for Android 12 / hence I was forced to do the swap. I Prefer OpenGapps, as they have lesser packages than MindTheGapps, as I mapped out extending the OpenGapps compare schema last year)
  6. I did too, practically immediately, as described earlier in the thread, so that might be a general good advice? (...at the least people should be prepared that they might need a factory reset)
  7. I have not tried Android 12, but my guess would be that the UI changes stem from Google not LineageOs as such.
  8. Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220525.zip on May 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload Known keyboard bug still there (see lineage thread) Note that the signature when downloaded as a zip is not accepted, so the loader on the phone asks you "...install anyway?".
  9. (lineage-19.1-20220523-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313)
  10. PS A hint on this. As the service used uses several severs, a simply retry of requesting a recovery is likely to be answered from another IP, that might not be blacklisted.
  11. Now that is good logic for ordering more than one ... 😁
  12. Exactly. And for the first one rebooting the phone resting on the desktop, without touching the plug fixes it so it clearly is NOT related to the physical connection. It is some 'state' it enters, from which the only (known?) exit is a reboot. And we have ONLY had reports on this from those on LineageOS & AICP, not Stock Android, so almost certainly a matter of the kernels handling the hardware differently. It MIGHT be that we would see the same if Stock was offered as 11 or 12. (If i recall correctly this was NOT reported for LineageOS 16 and 17, hence Android 10 most likely OK)
  13. Though I perked for a Pro1X, I doubt that it will be much of an improvement for daily usage, except the more stanardised QWERTY. But I think there is a good chance for more (security) updates on the Pro1X, so that might prolong its life time. As I expect it might be many years before we see a new alternative. On the Cosmo, you should rather have a look at their successor the Astro, it seems an overall improvement. The sliding (like most previous sliders except the Nokias) will require a balanced push to open, but should not posse a serious problem. The larger keys might making typing
  14. This seems even cheaper: https://aliexpress.com/item/1005002314744127.html I have no idea of the quality of the offerings, but I would suggest to start buying say two from each and test....
  15. Sounds like a good idea to me.. But as the correct glueing seems not to be super easy to do correctly, you might extend this servce to have people send in the top part - or the whole device. I think that is the reason why FxTec do not offer the display in it self but the whole top as a spare part, as this is easier to replace for the less tech experienced user.
  16. Indeed, data will be lost by this manoeuvre - on the other and a fix might never come, only time will tell if someone find a fix.
  17. Also note that you can not upgrade to 19 OTA. But most likely the upgrade will work putting it on a SD-card. And for me I had problems requiring a reset, that I belive was caused by switching from OpenGapps to MindTheGapps. (OpenGaps not available for 12 yet)
  18. Though you have to flash to stock to fix, you are not stuck at stock! You must boot once into stock, to the language selection, but it will still work after flashing to e.g. Lineage.
  19. You only need to flash stock and boot (important) once. Then you can flash your preferred OS. Tedious - I know, but no known workarounds...
  20. We have that debate in a display thread, but no known fix less flashing currently.
  21. Not much left *LOL*, I doubt the keys are standard parts, but could be wrong obviously. Maybe contacting FxTec is the most realistic option to get spare parts. But we still have no idea of a new screen/camera will work. worst case getting them as spare parts, they will break when attached. On the other hand displays are not expensive on AliExpress...
  22. If someone does not get a mail, and it is not a simple spam-filter issue, a very common issue is if the SPF (spoof) record is not setup correctly on the senders domain. A properly set up mail server checks for spoofing, though not all mailservers do so - that could explain why some get mails and others do not. The whole point of the spoof control is so the sender can not send claiming to be sending from some other domain. The recipients mail-server can ask the claimed domain if this mail sent from elsewhere is allowed to be sent on behalf of the claimed domain. This is useful i
  23. The tap sensitive margins have to be programmed correctly. If you ask WHY the screens comes with some other default - I have no idea....
  • Create New...

Important Information