Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/05/2021 in all areas

  1. Agreed, after upgrading from AICP Q to Lineage R it seems to just work - the safetynet test in Magisk fails with API error, but testing with a separate Safetynet test app works, and Google Pay works. It doesn't seem to affect Google Pay, but one problem I have is that MagiskHide does not survive a reboot. Have to manually disable and re-enable it after rebooting...but even then it does not affect Google pay, but some other apps warn that the device is rooted, if MagiskHide is not running.
    2 points
  2. Thanks. Not to be sarcastic, but I do wonder what they mean by "support" when it has been almost nine months without bugfixes, and the security updates are over a year behind... But I guess I'm just impatient.
    2 points
  3. I asked. They answered. "The existing Pro1 will not lose it's support from us for Android or the LineageOS, Linux communities anytime soon. Although the Pro1 X has a slight advantage - it's still updated by the SoC maker Qualcomm."
    2 points
  4. I'm in the same boat. Given up hope for an update, and will be pleasantly surprised if it arrives after all.
    2 points
  5. This didn't quite work for me. I've had my Pro 1 on the stock firmware up until today, where I installed LineageOS 18.1 20210401. I followed this guide, did the magisk hideprops config, and cleared the google play settings, but afterwards the safetynet would still not pass (even in magisk's own check). I googled a bit, and installed https://github.com/kdrag0n/safetynet-fix (downloaded + installed via magisk), then hid magisk and did the clear data/cache/reboot dance again, and afterwards safetynet passes. I also installed Google Pay and was able to set up NFC and everything seem
    2 points
  6. I'm baa-aaack. (After a stay in hospital (AGAIN.))🥵 So I've finally gone and cracked my screen 😢. Despite the phone being in a case when I dropped it the darn thing bounced out of the case when it hit the floor and the top left corner hit the concrete. The crack is a small star crack that just covers the none viewable black border. I've put some clear nail varnish over it for now (to stop any splinters breaking out) and I've got 2 screen protectors on order that should help stop it from getting bigger. I've looked on Ali Express but the screens are no longer available (bummer 😢)
    1 point
  7. Nice of you to ask them but uhhh..press x to doubt. I am sure they could finish 10 because that is 100% supported afaik but anything beyond that I wouldn't count. So far everything seems to indicate us 835ers are SOL unless we dedicate a full day to moving to Lineage or some other variant.
    1 point
  8. Bit of an update - I changed the Preferred network type to GSM/WCDMA preferred and I have had 4 phone calls in that time without the severe distortion. 4G call and WiFi calls are currently disabled. With just these disabled I still had muffled calls. I'm tempted to turn WiFi calling back on to see how that goes. I've a feeling that it may be related to the preferred network setting only.
    1 point
  9. Oh indeed. What we do not know is how much the swindle affected their plans for the original Pro1. Optimistically it could merely be a matter of prioritising getting the Pro1X ready and out on the streets first.
    1 point
  10. We do know they had plans for an Android 10 upgrade before the SoC changed. My guess would that they just won't have the resources to do that now, but you never know, the very existence of our Pro1 proves FxTec is very resourceful indeed.
    1 point
  11. 🙂 Good idea, though after their ticket form already said "we are currently swamped with work, so it may take up to a week or two", I didn't bother. The package is on its way; maybe I'll still try to call them tomorrow to give them the phone's unlock code, as applying the touch area patch is part of the service 👍 and I didn't mention it in my order...
    1 point
  12. Same for me. I have decided to go for Lineage OS instead of resetting stock one when I have time and mood for doing that...
    1 point
  13. At this point I've given up hope we will see anything beyond P. I saw a theory around here given the 1X is switching SoC, they won't push anything for us 835ers and focus just on that.
    1 point
  14. 1 point
  15. Are you connected through a VPN at all? I'm using Blokada v5 and was having similar issues, which meant I had to disable Blokada to check for updates. After some poking about I found out that Blokada was blocking the Adups service, once I whitelisted this in Blokada I can now check for updates without switching off the VPN.
    1 point
  16. If you never got an auto-responder message, I would question they received it. I have always gotten an auto-response to a new email to [email protected] that was a new request (responses formatted with ticket number and "type above this line" don't get auto-responses). I have always only used the [email protected] address and have always gotten a real response from them within 2 weeks (it varies-- I've had responses within 48 hours... 2 weeks is the max). @Erik Any idea what's going on in these two cases?
    1 point
×
×
  • Create New...

Important Information

Terms