Jump to content

EskeRahn

Keymaster
  • Content Count

    5,756
  • Joined

  • Last visited

  • Days Won

    338

Everything posted by EskeRahn

  1. Sounds sad, but could be that they are merely saying that all that are in the pipeline for batches with shipping before that are allocated. But that could also be just my over-optimistic guess.
  2. (lineage-18.1-20220228-nightly-pro1-signed.zip on February 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)
  3. All this driver stuff should be in a different thread. Any suggestions of a good thread? Then I will move it. 🙂
  4. Would guess it is a bit tough to repair with home-stuff as it is supposed to be carrying significant currents, above 1A
  5. Never actually used them. It was mostly a proof of concept. The touch worked as such though obviously not at the side edges
  6. Update to February 23, with Februrary 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)
  7. Even the hugest players have problems getting components for their goods, so no big surprise that it goes for a tiny player too... If they are guilty of anything here, it is being over optimistic in these harsh times.
  8. The big difference (for some companies) is that that the stock version has been certified by Google.
  9. My GUESS would be that if a device support some (or even most), but not all of the bands the carrier offers, they will be reluctant to let it into their net. Simply because the bad experience of "poor coverage" most often fall back on the carrier, even if it actually is the phone that can not use the bands offered in the area in question. This dialogue is not uncommon: "I got a lousy signal here! - What carrier are you using? - XXX - Ahh, damned XXX" ...
  10. I understand your point of view, but I bet that the work it would require to persuade huge tele-companies to care about a tiny player like FxTec would far exceed any profit they could gain by additional sales. If they felt they could sell say 10K extra Pro1(X) it would obviously be a different story, and they could ask with a punch with a little weight. I think that the original idea of this thread with a user group is much more likely to have any leverage. It could potentially give bad press of the tele-giants not caring about customers, by stirring up commotion and thus will have muc
  11. The engraving was only available as a limited offer for Black Friday 2020, AFAIK
  12. (lineage-18.1-20220221-nightly-pro1-signed.zip on February 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)
  13. Totally agree with you. The benefits of IGG is the early perks - though they also comes at the higher risk. I will say that the risk at this late state is low though, but you still got better consumer rights with the classic web-shop order. IF you are interested in a spare battery and display-part, the $849 perk is a fairly interesting one though, compared to the $719 perk for the device alone. So IF you are going to order it on IGG, consider that option too... (They do not offer spare parts of the web-shop, at the least not currently AFAIK)
  14. I wonder if this text was written in the weekend, or today. It makes quite a difference, as "next week" today brings us into March... But I guess it would be rather optimistic to hope for "the end of the month" actually being February.
  15. Definitely more interesting than the Cosmo. We got a quite long thread on it already:
  16. Update to February 16, with January 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)
  17. I would suggest that you between your 1 and 2 install the stock Android, to get it as close to factory condition as possible, and IF the keyboard works there, install Lineage. If not it must be a hardware issue.
  18. (lineage-18.1-20220214-nightly-pro1-signed.zip on January 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)
  19. https://community.fxtec.com/topic/3509-faq-how-to-do-various-tasks/
  20. This is a post with links to threads on various tasks. Like installing and repairing. Suggest additions at will. If I find it relevant, I will add it, and plan to remove the suggestions to keep this thread (c)lean. ***Please be aware that guides for Pro1 and Pro1X are NOT interchangeable in general, though much goes for both*** Please: Help keep the forum clean and use the Report function whenever you see some spam or similar irrelevant content. Please: Enter your FxTec Device Information in your Member Title slot under "Edit Profile". See this (So other
  21. Good idea! I will suggest that someone make (and maintain) a FAQ post with relevant links in the "How to" section. I could then 'pin' it to the main-list, and it should contain links to the three currently 'pinned' on how to open up the display, how to setup qwertZ and how to flash. (and these three post could then be unpinned)
  22. If you got titanium backup, my approach before a wipe would be gradually> A backup One by one uninstall (or disable) any app. Start with those easy to reinstall, and/or recently installed, (and without any hard to restore data). Repeat this until it helps or all is gone. Wipe the phone by a factory reset Flash back to Stock Android (If your Lineage installation is somehow damaged) If you send it to service, they are most likely to start at step 4 anyway, unless it is a known bug to them.
×
×
  • Create New...

Important Information

Terms