Jump to content

PokeParadox

Members
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by PokeParadox

  1. Just an update to maybe help anyone having the same problem: I had forgotten to delete my old "hidden" Magisk installation and this confusing/preventing Magisk 26.x from realising it was installed in recovery. As soon as I uninstalled the hidden Magisk application, running the latest installed Magisk prompted me to complete the installation finally!
  2. EDIT: Doh I missed the above messages... I guess I'll try again. Are you flashing the latest version of Magisk? Could I get some help installing magisk on 20.0 from someone please? Lineage is installed but can't seem to get Magisk working - I patched the boot.img and flashed it but the Magisk app doesn't change...
  3. Which version of Lineage are you running, I don't appear to have that file? There's one similarly named (IIRC "/system/vendor/etc/mixer_paths_skul.xml" ).
  4. I've not got around to trying again, do you have a more recent set of steps I could follow? I don't seem to have much luck getting this set up.
  5. I'm most irritated that some emulators (Citra, RetroArch) I can no longer find my roms... RetroArch was solved by using DIG frontend - but I simply can't use Citra at the moment.
  6. Yep - Had this same problem, even down to looking at it as it faded to black! They replaced it fairly quickly (covid considering), but it was long enough that I had to get an intermediary phone... sigh.
  7. I apologise for spamming the thread, but I do think it's important to point out that with GSM/WCDMA preferred + WiFi calling enabled on Lineage 18.1 I've had a further 7 calls without quality taking a hit. I'll stop posting for now. :)
  8. Yeah - I feel very much like this - I still have some emulators that I can't use: DraStic - I can only use DIG to launch roms, but can't select the rom directory natively. Citra - I can't get it to work at all. RetroArch only running via DIG I was hoping Lineage would have an "advanced mode" workaround for the scoped storage as it's really limiting...
  9. Another update. I've got the setting to GSM/WCDMA preferred as mentioned before, but I've also re-enabled the WiFi-calling. I have unfortunately only had 1 call so far in this setup, but it was clear without interference in sound.
  10. Yes, sorry I should have been clearer. I'm using the hide list, but Halifax banking app is somehow still detecting root - other root-sensitive apps aren't. I'm not sure how.
  11. Magisk has been updated (23.0), so the internal SafetyNet check should work again!
  12. I've now had about 8 calls in the setup above. I've not enabled WiFi calls again yet. Only one of those has had some "buzzing" - so it seems to made an overall improvement to call quality. In the call that was buzzing moving around a little improved the quality. (I suspect - signal strength may be related too) Obvious downsides to this is you lose 4G - which is not really a problem for me for what I use mobile data for usually - plus currently I'm still housebound with WiFi. Also this is only my experience, obviously. I'd be very interested if others have tried this and get similar result
  13. I can also confirm I proceeded to downloaded a separate safety check app, which passed and then logged into my root sensitive apps mostly without a problem. I setup my GooglePay without a hitch without having to follow the GooglePay specific part of the OP post. One of my banking apps is still detecting root, however.
  14. Thanks for that... I've been sat twiddling my thumbs waiting for the Magisk fix - didn't think about checking with a separate app. I can continue setting up the rest of my phone apps now! :P
  15. 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.
  16. Yes I have very bad call quality... it's very muffled. I'm currently on LOS 18.1 If AICP performs better I may move to that :(
  17. Still have distorted calls - very muffled. I'm on Lineage 18.1 and turning of the 4G calls and WiFi calls seems to have reduced the frequency of the muffling... maybe but it's still happening. :(
  18. I'm currently running 18.1 unofficial. Can I move over to this without wiping my data/apps and having to setup Magisk again?
  19. OMG! That's beautiful! :) I look forward to your tutorial in setting this up! I had a big break in all of this since my original Pro1 died... :( But it's definitely something I want to try again! :)
  20. Yeah I've disabled WiFi calls too. I'll see if this makes things better on the next call...
  21. I disabled the 4G call option and received a call this morning which was "buzzy" I do have WiFi calls enabled though... It would be nice to find a concrete workaround!
  22. Hello all! First the good news, my Pro1 has been repaired and sent back! Unfortunately it needed a new board so I basically lost a few photos which I saved to the internal memory instead of SD.. :( Anyway I have some quirks - I am now on stock Android but I'm not sure if I'm on the latest version. There's a few things that don't seem right: Battery seems to be draining a lot quicker than I remember. I keep getting a "Wireless Update" notification popup fairly frequently and disappear. I'm not able to perform an OTA update even if I go to the menu - it's like it's
  23. Just an update - Tech Support worked through several things to try but it didn't want to respond to anything and it looks like I have to send it back for repair...
  24. Indeed - I was already using Lineage without issue for a good while - long after any flashing took place. I was browsing Twitter and the screen faded to off. Now I'm stuck in this state. :(
×
×
  • Create New...

Important Information

Terms