i’m “still” on 3.0 and recognize a really bad GPS behaviour. every app requesting gps gets only very flaky a gps lock. sometimes it gets a lock/fix out of the box. but most of the time is never gets a fix. doesnt matter if i kill every other app using gps, nor rebooting helps. does anyone else having this error?
i dont use gps on regular basis but i think it was much better in older releases, eg. 2.6 or 2.9?!?
In fact, it is explicitly stated on OrangeFox recovery’s website that the zip must not be unzipped but flashed as is. I guess some features do not work by flashing the uncompressed recovery.img. But it was sufficient to use the .img to flash ROM or the zip of the recovery itself from SD card.
Merci pour le retour. Effectivement, c’était bien abordé. Par contre, je ne trouve pas comment installer orangefox en img
Thanks for the feedback. Indeed, it was well addressed. On the other hand, I can’t find how to install orangefox in img
Je vous remercie pour votre retour. Par contre, j’ai toujours le même message d’erreur. Comment fait on pour la méthode d’installation que vous suggérer plus haut?
Good evening MaximusDecimus
Thank you for your feedback. However, I still get the same error message. How do we go about the installation method that you suggested above?
For anyone wanting to use Revolut on e/os with this device theres a simple solution granted the bootloader must be unlocked via unofficial method, then you need to root and edit build.prop simply remove the e_ from the build id and change dev-keys to keys userdebug to user also change lineage_levender_userdebug to levender_user, then open up magisk and select uninstall then complete uninstall
This is device specific to the redmi note 7 and if its bootloader is unlocked via unofficial “ubl” method, theres a youtube video about it, if done this way the unlock is not detectable by apps
Anyone with officially unlocked lavender can try and share their results, but if bootloader unlocked status is detectable it wont work.
I got mine from electronics recycling and it was mi account locked, used this method and saw that bootloader status wasnt visible and revolut works after the build.prop tweak
Hi,
I recently performed a dirty flash of the ROM, upgrading from the official version 2.3. Everything appears to be working well, except for the following issue:
"Profiles Trust Provider keeps stopping."
To resolve this, I added the following file:
in the following path:
/system/system_ext/etc/permissions
it’s been two days now without any errors.
The profile switching works perfectly when a Bluetooth device is connected or disconnected.