Jump to content

EskeRahn

Keymaster
 View Profile  See their activity

  • Content Count

    5,798

  • Joined

  • Last visited

  • Days Won

    348

 Content Type 

Everything posted by EskeRahn

  1. EskeRahn
    I had various issues when I got a new PC, and I posted them in here, but I forgot where, and also what driver I used, but i did 'something', it did not work out of the box as I recall it....
  2. EskeRahn
    BTW I do not use the -d option - I have no clue if that makes a difference
  3. EskeRahn
    "could not read ok from ADB server" That could be communication issues. Try a slower port. Have your PC got a USB2.0 port? If not try a hub. An ancient very primitive hub supporting USB 1.0 only, worked for me - quite slow, but it worked. Just to be sure that it not the issue. Could be driver also of course.
  4. EskeRahn
    I mean that the flashing is likely to fail on some connections. What is the error message you get from adb? After you have flashed the recovery image with fastboot you need to boot into recovery mode, bootloader mode on the phone does not understand adb-commands directly Here is the batch-file I use on windows for flashing: @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause echo * sending %~n1 fastboot --set-active=a fastboot flash boot %1 TimeOut 5 /nobreak>nul shift REM fastboot reboot r
  5. EskeRahn
    Also remember that both ports and cables can be problematic with fastboot on newer PC's For me going through a hub helped connecting (It is still USB3.0, but something is different from when connecting directly), I guest that even a Thunderbolt hub, adds a tiny extra delay in the communication, and that helps getting fastboot working.
  6. EskeRahn
    The point with this step is to assure that everything hardware wise is working in your specimen, not to waste time on troubleshooting on Lineage, if it is a faulty specimen, that slipped through their QC. Or a connector managed to pop out during transportation, perhaps before you even got it. But it is not a MUST, seen in the sense that things wont work if you did not do it. It is just a fairly simple step, that might ease debugging any trouble.
  7. EskeRahn
    Most likely. You could try without, but I would certainly be sure to back up stuff first, since I think the risk of having to wipe is high. (My point was more to download and save the file, and if the issue is not fixed shortly, you have a return path)
  8. EskeRahn
    As the other thread said, it can be REALLY picky on some tags. I have some where moving it a single mm in the wrong direction prevent it from reading. Please try to light trough the card (or what ever got the tag) to be sure what type of nfc tag you are trying to read, And I even for some have better results WITH a case than without, so picky on the distance too.... In short it is bit of a nightmare to get it to read some tags..
  9. EskeRahn
    Yes connected, but as he describes not charging continuously, but a few seconds per boot. Amazing that it worked. I really hope others can reproduce it, fixing their issues.
  10. EskeRahn
    Just to chime in here, the camera seems to still work fine with both the build in Camera app and the Open Camera app with the older build in lineage-21.0-20240615-nightly-pro1-signed.zip So I would recommend to make sure to get a copy from here of that version until the bug (hopefully) gets fixed. As not all bugs got high priority, the working build might disappear by age, as only the last five builds are available for download. (On the priority, e.g. the keyboard is still almost useless for bilingual usage and has been so in all the 21.0 releases this far, so I am considering reverting
  11. EskeRahn
    Awakening an old thread. A user reported a way to fix the issue on IGG:
  12. EskeRahn
    To those that got a Pro1X not charging, try the fix found by Thomas Bonde Pedersen on IGG. Made a thread here:
  13. EskeRahn
    Thomas Bonde Pedersen has at IGG posted a fix for the not charging Pro1! ADD: This has been confirmed to work by other users! Please try it, before disassembly (or send in for service)
  14. EskeRahn
    I tried both a Pro1 and a Pro1X as delivered, as well as a Pro1 with Lineage 21 - all show the same: Basic is green,
  15. EskeRahn
    I believe it would require wiping your phone back to factory defaults. So make sure to have all data backed up.
  16. EskeRahn
    I think they are fairly seldom visitors in here these days.
  17. EskeRahn
    It is a tough one. It would seem fair to do as they wrote. But the IGG policy clearly says that backers should be served before any other. Logically the money you paid for the original Pro1 should be seen as some sort of a backing, but as buyers have other legal rights than backers, it most likely is not the case seen from IGG point of view. How FxTec choose to handle the conflicting interests I do not know.
  18. EskeRahn
    (lineage-21.0-20240615-nightly-pro1-signed.zip on May 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-14.0.0-arm64-20231025_234300) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
  19. EskeRahn
    They seems to finally be sending out the form-request for IGG. Got this
  20. EskeRahn
    Labels are there in both landscape and portrait with the default QuickStep launcher on Pro1. But not so on the (different) QuickStep on the Pro1X.
  21. EskeRahn
    (lineage-21.0-20240518-nightly-pro1-signed.zip on May 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-14.0.0-arm64-20231025_234300) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
  22. EskeRahn
    I hope you are right, but if so a bit odd they did not provide a link on the new front page. Time will tell if it will be added later... could also be that they just archived it for now,, until they decide what to do.
  23. EskeRahn
    Ah! so they sort of moved www.fxtec.com to www.fxtec.com/smartphones So anything with relative links works there
  24. EskeRahn
    yes, e.g. https://web.archive.org/web/20240317094412/https://www.fxtec.com/ https://web.archive.org/web/20240317094415/https://www.fxtec.com/pro1x
  25. EskeRahn
    It seems that currently all fxtec.com pages except the comunity is reroutetd to a common page. Anyone that knows how to access the other pages, if they still exists that is? Obviosly there is always the webarchive, but.... ADD: @sequestris reported that stuff seems to still be available, now under a subpage: www.fxtec.com/smartphones (Not all links/buttons are working though)
×
×
  • Create New...

Important Information

Terms

  I accept