Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by marmistrz

  1. @Casey could you please shed some light on the current state of the production/delivery? The IGG updates have been silent for 4 months.
  2. In the end, what changes did you do? I remember doing gps.conf changes back in the day but they turned out to be placebo ;/
  3. I got an e-mail from them on Feb 19, I'm trying to get some replacement parts for my Pro1. So they're still alive.
  4. The ribbon cable looks intact and reattaching the top half of the device doesn't help, however, I have trouble opening the bottom half. I removed the five screws, but the bottom part won't even budge when I try to pry it open. It's not necessary to remove the keyboard with a heat gun to pry open the bottom part, is it?
  5. Casey, I think that even a "there's sadly no news" kind of update would still have been better than complete silence. I seriously thought F(x)tec had gone belly up. But it's good to hear that!
  6. Thanks. That's what I supposed. Given that opening the slider (with impact) seems to help, this feels like a ribbon cable issue. I'll open up the device and try to inspect the ribbon cable.
  7. Hi, My Pro1's screen suddenly started going crazy. In the morning it was kind of pale, and later suddenly started showing just stripes of green. See the video here. Do you have an idea what might've happened?
  8. My Pro1 worked perfectly with GenMobile (T-Mobile based MVNO). SimpleMobile and UltraMobile (also using T-Mobile's stations) claimed that the IMEI was incompatible due to "VoLTE being unsupported" and the cellular shop couldn't sell/activate the SIM.
  9. I still remember the times when someone from F(x)tec watched such threads and replied to frustrated customers...
  10. This is so sad, and I think we'll have to wait years and years for the next slider smartphone, if it ever happens. It's even sadder if you see the market these days, with vendors keeping removing features and flagships that are missing features such as the notification LED or the headphone jack.
  11. I also sent my Pro1 for a screen replacement and got it back last September or so.
  12. As in the title. The standard method is TWRP, but, as far as I know, TWRP for the Pro1 only supports SailfishOS and doesn't support LineageOS or /data decryption (aka device lock). In a nutshell, I want to try be able to clean flash a ROM and be able to revert to my current setup without hassle.
  13. I'm currently running LineageOS 18.1 on my Pro1 (19.1 has always had broken dual SIM support). Camera stopped working for me about a month ago. The flashlight applet is grayed out and says "Camera in use". The LineageOS camera only uses the front-facing camera. GCam crashes. There are some camera-related errors during boot: 05-01 06:29:44.568 0 0 I iommu : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb1 to group 14 05-01 06:29:44.569 0 0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 8, cb->name: :vfe sid [0] = 3072 05-01 06:29:44.569 0 0 E : ,
  14. What do you think about providing two variants of the print, one with the headphone jack covered and the other one uncovered? For me the availability of the headphone jack is quite important, even if it comes at the expense of the grip.' /edit: ah, I didn't realize that the new design isn't a a TPU-first design. This might change a lot. I really love the TPU case
  15. Thank you very much, it's awesome! I sent the ticket number by DM.
  16. Thank you very much for the reply! What would be the approximate cost of both options?
  17. I've happily used my Pro1 for over 2 years. I can't help dropping my devices, but the 3D-printed TPU case saved the screen from cracking throughout its life. However, a week ago, the screen suddenly stopped working, with no clear cause. A week earlier days ago I noticed a weird issue: the screen would turn off while it was being touched at one place (the place was around 50% vertically, 25% horizontally counted from the left). When I removed my finger, it would turn itself on again. I supposed some weird driver bug, so I rebooted and the problem went away. That day, it was a rainy da
  18. FWIW, the OnePlus 3 that I'm using for GPS is running LineageOS too, so it's not an issue with LineageOS (i.e. the common base) per se
  19. For me the "next fix" usually works. But sometimes it doesn't and getting a fix takes tens of minutes. This is why I carry my old OnePlus 3 whenever GPS is crucial... 😞 It's been that way ever since, I guess it's yet another bug that will never get resolved.
  20. I tried to upstream this "fix" for gps fixes and it turned out it never really worked for me.
  21. Magisk seemed to work fine, but I decided to downgrade (and reinstall) because dual-SIM was broken. See my previous post in this thread.
  22. I created an issue: https://gitlab.com/LineageOS/issues/android/-/issues/4841
  • Create New...

Important Information