Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by SCΛRECROW

  1. Phone is now sold. Used Original F(x)tec Pro¹ (SD835) for sale with spare parts, includes: Pro1 Phone running LineageOS 20 (Android 13) with original pouch Replacement screen + repair tools Replacement display backing plate Replacement USB-C board Fully functional, just no longer needed. Some scratches and scuffs on rear of phone. Small black screen bleed blob in lower right corner of screen. Bonus Core i7 sticker to confuse people. 😋 Full disclosure: screen has been replaced due to fault, but there is some lifting at edges where adhesive isn't sticking p
  2. Think this one might be dead in the water for SD835. Would have been fun to try, but no audio, wifi or cellular kills it for me: https://wiki.renegade-project.cn/en/state As an aside, W10 22H2 going forward has dropped support for ARMv8 as well.
  3. I'll give it a shot since my Pro1 is no longer my daily driver, no promises to when I'll get around to it though.
  4. Was about to say I haven't noticed it since Aug 18, but the issue reoccurred today...
  5. Follow up: it happened again, this time after using dumb chargers only, also LOS18.1. Battery was below 50%. I'll start recording battery % and uptime before each charge to see if there's a pattern.
  6. Managed to find some time to re-glue the screen with B-7000, which works nicely. Left the phone under a stack of books overnight and just rubbed the overflowed glue residue off with my fingers. Also, I forgot who had the idea of adding a diffuser to the notification LED window, but thank you. I added a bit of magic tape to it and it's a much better look now.
  7. Can say that the same thing happened to me twice in the past week. Only happened after I used a USB-C PD charger, hasn't happened again when using "dumb" chargers in the past 3 days. Kind of tempted to say it's a software issue. 🤷‍♂️ Will keep an eye on it.
  8. That might be a loose flex connector, provided that the USB cable isn't damaged. For the record, my device didn't have any issues charging with the cable at different angles.
  9. Yes, indeed, removed the old strip and cleaned the frame with isopropyl alcohol before applying the new adhesive tape, which was also cut to size. Thanks for the tip, I'll give the B-7000 glue a shot.
  10. I'm having the same problem, used the 3M tape, left it under a couple of heavy books for 2 days but one corner is still popping up.
  11. Got aliexpress replacement display and replaced the faulty one successfully. Can confirm, no more ghost touches. Such a relief to get the keyboard back.
  12. I see a lot of damaged devices at work and I've never come across a digitiser fault without the display or glass substrate being damaged. But as they say, there's a first time for everything. I'd be interested in knowing the frequency of this type of damage in phones with curved screens vs flat screens vs the Pro1.
  13. Thanks @Hook and @vvv So I contacted support, who are saying that they've investigated this type of failure and they've determined it's caused by some sort of impact that has damaged the touch layer, but not the OLED layer. As such, it's not covered under warranty...I'm not going to argue the point because I can't prove what caused the malfunction either way. Annoying, but that's life I guess. I've migrated to using my spare phone because the random touch inputs are making my Pro1 unusable. ☹️ In any case, I've ordered 2 replacement displays from aliexpress, which are cheaper t
  14. Another one to add to the list. Mine started doing the same thing today, exact same symptoms. @vvv How's your aliexpress replacement screen doing?
  15. Should have stayed on LOS17....Storage Access Framework/Scoped Storage is a pain Edit: Everything else works as expected though, so there's that I guess.
  16. The researchers specifically mention MSM8998 which is the Snapdragon 835. https://research.checkpoint.com/2021/security-probe-of-qualcomm-msm/
  17. Yeah, no way to OEM unlock these phones. IIRC there was temp root at one point, but it got patched out pretty quickly. Haven't looked into development for these phones in a long time.
  18. https://www.catphones.com/en-au/cat-s60-smartphone/ I had a CAT S60 few years ago, a fairly typical ruggedised phone with mid-range spec, but with a FLIR thermal "Predator vision" camera and hardware navigation bar buttons! It was a colossal brick of a phone. but the thermal camera was very useful for work and around the house....considering getting an addon FLIR camera for my Pro1. Would probably be rocking an S62 Pro if the Pro1 didn't exist.
  19. A late update with my device suffering this issue...I fixed it after tightening a loose screw. I dissembled my phone looking for any loose connectors, specifically the flex cable to the USB sub board, but the screw circled in red was loose with maybe 1mm of movement between the screwhead and PCB. (thanks to @gelraen.ua for the photo, I forgot to take photos haha) The FCC teardown photo below shows some contacts on the underside of this PCB. So my theory - without knowledge of the schematics or circuit diagrams - is that a lack of contact against the metal midframe caused the Hal
  20. My apologies, I think that functionality existed in Nova running on Android 9 (LOS 16) but something messed it up in Android 10 (LOS 17). No spontaneous reboots here and I did not wipe my phone either. It's been up for over 42 hours since the last (user initiated) reboot.
  21. You can get the app drawer button back in Nova, I certainly have it. You'll need to add the button back as a widget: Long press an empty spot on the home screen Tap on widgets Tap and drag the Nova action shortcut (should be the first one) into the dock or where ever you want it Then tap on App drawer in the Nova Action menu
  22. I installed Magisk through the Custom Recovery method for root, find instructions here: https://topjohnwu.github.io/Magisk/install.html
  • Create New...

Important Information