yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] rester555:
I really hope this doesn't necessitate a wipe after every monthly update since there is a new boot image every single month. That would really suck!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Agreed. And since we don't know exactly what the issue is, it's impossible to say.
[Google Pixel 5 Guides, News, & Discussion] rester555:
I am bumping this reply... Wouldn't this guide apply to someone unrooted on A12 as well?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Potentially, but your mileage may vary.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
@HumorBaby I'd like to point out that this method only flashes the active slot, and you can't flash both slots from fastboot. You can switch slots in bootloader but that seems to break the whole deal. I'm not completely sure when the phone would switch slots anyway, most likely after an automatic OTA, so while this should work going forward, we'll have to ensure everyone knows to avoid the automatic OTA.

This is what I tried:

-Sideloaded OTA

-Entered fastboot, flashed /vbmeta and /boot

-Rebooted, confirmed I still had root

-Rebooted to bootloader, switched slots, rebooted to recovery, re entered fastboot

-Flashed /vbmeta and /boot again

-Rebooted, got dumped in recovery with the Corrupted Data message

I'm going to have to try everything all over again when I get home today. I'm using the same patched image with the same version of Magisk that worked before, but I don't have root for some odd reason.

I think what I'll do is start in fastboot, then reflash both a and b sides of everything with stock images - I wish we could do this via Android Flash Tool but force flash all partitions requires a data wipe.

Then, switch to slot A, reboot to recovery, apply OTA, enter fastboot, flash vbmeta with disable flags, flash patched boot, confirm successful boot and root.

Then, switch to slot B, and try to do the same thing.
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Any chance you (or anyone else) tried this for the Nov patch (sp1a.211105)

I tried it this AM and ended up having to wipe.

But I think this was because in my hurry I forgot to patch the boot image on my phone first, and didn't remember until I had sideloaded OTA and dropped to fastbootd. Then, I had to use my Magisk 23001 (same version I am currently running on Pixel 5) on my Pixel 2XL to patch the 5's boot image.

After flashing vbmeta and patched boot (using Magisk on Pixel 2XL), a reboot took me to a system that didn't have root. I am hoping this is because the boot image was patched on a Pixel 2XL and not a 5, and not because the OTA/slot-issues have once again required a wipe even for simple monthly updates 😿

I have just finished restoring and don't want to go through a series of wipe/install/tests if I don't have to .
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Related to this (and my previous post), in order to try to salvage my failed root, I did exactly this: reboot to bootloader, switch slots, flash vbmeta and patched boot (patched on Pixel 5 this time). I had the same result: Corruped Data.

My point is: I have a feeling that switching slots is going to reset your "successful boot with disable-verity and disable-verification", which will once again force a wipe… i'm curious to see what you find, as if you do end up having to wipe, this would support my understanding/guess as to what the new bootloader that came with 12b5 (and onwarrds) is doing in regards to storing boot state (based on what I parsed from this section about AVB onward)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Turns out we should flash vbmeta in bootloader, not fastbootd.

The CRITICAL issue is to not allow the device to boot into system until vbmeta has been disabled. If this happens, a wipe will be required when it is disabled again.

I successfully updated to the November patch exactly like this:

- Sideloaded the OTA in recovery, immediately rebooted to bootloader

- Flashed vbmeta:

fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img

I flashed to both slots because the OTA is typically an out of band update, and I wanted to be safe.

- Booted the patched boot image; got stuck on Google logo with loading bar, so forced reboot and allowed device to boot

- Rebooted to bootloader, booted patched image, confirmed root was working, performed Direct Install, rebooted again, root was retained.

Then, for the sake of proof, I dirty flashed the factory image through Android Flash Tool with verity and verification disabled, and let the device reboot into unrooted system. Rebooted to bootloader, flashed patched boot image, rebooted into rooted system.

As for losing root, it's possibly because you patched Magisk with a different device, as Magisk does leave a signature on the patch.

Try re-patching the stock boot image on the Pixel 5, then boot it and see if it works.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That method failed for me too.

What I believe we have to do, as pointed out by @Anonshe , is that we have to reflash vbmeta in bootloader, not fastbootd - and we must not allow the kernel to boot until that is done. Meaning, directly following OTA sideload, immediately reboot into bootloader and reflash vbmeta to both slots with disable flags.

Alternatively, you can dirty flash the system image with the disable flags.

This seems to be the trick. Once vbmeta has been disabled, it must be kept disabled, and if it gets reflashed without the disable flags for any reason, the device must not leave bootloader until it is disabled again, otherwise a wipe is required.

This is why the automatic OTA requires a wipe to re-root - because it writes /vbmeta without the disable flags, then reboots.

I don't see why switching slots would do it.
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Yep, I realized that this may be the main culprit, since as you noted, OTA works by updating the non-current slot, then switches after a reboot.

Thinking back and looking at the old ouput from my commands showed that OTA much has updated _a for me, but since I was in _b, fastboot flash vbmeta/patched-boot was put in _b. Then, reboot changed to _a, and a successful boot reset the verity flag and forced a wipe upon any subsequent actions.

My gut was telling me that I needed to be more aware/thoughtful of the slots as I was doing it, but I ignored it. Lesson learned.

I did try this once I realized I didn't have root, but at this point it was already too late since slot_a already booted without a disabled verity/verification.

Nope, just was floundering. Was hoping since I flashed vbmeta/patched boot into _b, a switch would get me root and bootloader would respect the disabled-verity during flash. However, knowing now that verity status is stored in userdata, it makes sense that it wouldn't work.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well..."A smart man learns from his own mistakes; a wise man learns from other's mistakes." I am by no means wise, so I don't blame you!
[Nokia 6 ROMs, Kernels, Recoveries, & Other Develop] Atharv Negi:
View attachment 5438957

Skyhawk Recovery Project For Nokia6 (PLE)

Features

- Themes

- Status bar customization

- New rounded icons added on dashboard

- Notch mode with toggle to disable

- Dark mode or pure white, it's on you

- Navigation bar customization

- Settings + Advanced Settings

- Flash Magisk

- Clear fingerprints

- Recovery Locking , Pin or Pattern lock

- Hal3 / CameraAPI2 enabling/disabling

- Oreo+ Reboot menu style

- Redesigned lock screen interface

- Flashlight

- Magisk manager - Enable, disable or delete magisk modules right from SHRP

- Text Editor

- Custom Themes

- Theme, Lock, Addon survival

- Some OTA functionalities

- SHRP Injection (A/B)

- Magisk injection

- Auto decrypt

- and many more, flash right now to find out

Flashing Process

Flash With TWRP or Orangefox

Download

Zip : https://we.tl/t-PCNHGtdc2m

Addons : https://we.tl/t-qIPMFixdxi

Bugs

Tell in telegram or reply this thread if it boots

Credits

EpicX

DNI9

Giovix92

TeamWin

osmOsis

VR25

Topjohnwu

Mauronofrio

DarthJabba9

steadfasterX

oddlyspaced

Corsicanu

Contributors

Atharv,EpicX

Source Code: https://github.com/SKYHAWK-Recovery-Project

Device Source Code

GitHub - atharv2951/android_device_fih_D1C

Contribute to atharv2951/android_device_fih_D1C development by creating an account on GitHub.

github.com

For More help Join Us on Telegram

Telegram: Contact @nokia6_community

t.me

Thanks

Hit Like On Xda
[Nokia 6 ROMs, Kernels, Recoveries, & Other Develop] cbkings:
Nope, didnt boot into recovery. I flashed it using twrp 3.3.1. No errors during the flashing. but it didnt boot into recovery.

Im on stock pie PLE
[Nokia 6 ROMs, Kernels, Recoveries, & Other Develop] Atharv Negi:
Yes thanks for reply let me check my trees btw try out orangefox
[General Topics] PPCBANDIT:
I like HTC Task Manager's feature, that enables the Quick Menu when pressing the X-button. But I would like to acces the Quick Menu with a hardkey. Does anybody know how that can be done?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Alysson0321:
I'm thinking about porting the CorvusOS 9.0 from g5 to g4+
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] chuy19312:
Sadly i don't know but you could try, something curious is some of the Moto G4 Pie roms i checked, were detected on some apps as Moto G5 or Moto G5 Plus.
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
View attachment 5438979​

This series of roms is focused to gain more performance and add some other features to the rom, all of them are based in latest firrmware for each

How To install:

1) install TWRP for your device

2) enter in advance wipe and wipe dalvik, system,data,internal storage and cache

3) format data partition

4) flash the rom

5) enjoy!!

Devices suppoted by now:

A10

A11

A20

A30

A30s

A50

A70

more devices soon

Spoiler content hidden.

​

Spoiler content hidden.

Stockless 2.3 A50F/G: A50F/G

Stockless 2.3.1 changelog:

fixed some critical issue of droping performace

fixed ram manager

others fixes and improvements

Download: Stockless 2.3.1 folder

Spoiler content hidden.

Stockless 2.4 changelog:

updated to latest firmware version for G variant (A505GUBS9CVC6)

fixed ram management

fixed gpu management

some oneui4 apps

general improvements

Stockless 2.4 folder

ROM OS Version: 11

ROM Kernel: Stock

ROM Firmware Required: Stock Android 11

Status: Stable

Created 27-08-2021

Last Updated 15-05-2022

Kernel source: Stock from samsung

Telegram support Group
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] JULiO.7:
provide screenshots
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
is stock based, why you need screenshots ?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] redymedan:
Good Job @tutibreaker for new rom for A50.

Overview, review, how to install and rooting. Make it more slim.. some bloatware still over there
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
got it, i dont own the device so debloating is delicate due some system apps may crash the whole system but i will try
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] redymedan:
use this tool https://xdaforums.com/t/tool-adb-appcontrol-1-7-ultimate-app-manager-debloat-tool-tweaks.4147837/ to remove bloatware and it will help you to know which apps that safe or not to be removed. I have done it to stock rom. It worked on A505F, according to me you don't need release new version for A505F, generally everything works on A505F. I like your jobs, if you can increase free RAM, I think it will be good for gaming
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] ashishgawali:
Nice rom thank you 🤩🤩🤩🤩
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] phvtai:
Thank you
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] lord damz:
Hi, I like the rom can I download any other kernel for my SM-A505G ?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
Updated for G variant others variant will be updated soon
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tugrul_27:
Where is link A505F variant
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] avitswai:
last time i tried this rom my root partition was around 3Gb+ instead of 5.03Gb is this issue fixed in the latest update
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
Updated rom for F/G and FN models
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] GabrielGuerreroHND:
How is the SM-A505G doing for games with your version of Rom friend?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
try and tell :)
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] asms5583:
great work
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Chinito_H18:
dude im really amazed with this rom both for gaming or normal use you are a genius follow if i love you
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] GabrielGuerreroHND:
ESPAÑOL:

Soy usario de: SM-A505G.

Saludos desde Honduras amigos, he probado la última actualización, y la verdad anda bien. Lo único es el consumo ligero de la bateria, pero creo que se debe al mayor rendimiento del equipo. Todavia hay mucha Bootloader que puedes eliminar pero anda bien.

PARA GAMING:

Solamente juego: Call Of Duty: Móbile, y anda super bien, con un Game Booster para jugar bien sin Lag. Y eso que CODM es un juego que ocupa mucho rendimiento para jugar a Gráficos Bajos, y FPS Medio (Ojo los fps en Máximo se pone con mucho Lag, por eso los fps los puse en Medio).

PARA USO DIARIO:

Lo he probado y anda bien, no he tenido problemas en ninguna aplicación entre cambiar de una a otra. Así que ahí anda bien.

CÁMARA:

Super bien! todo funcionando a la perfección. Todo anda bien.

Y pues! te felicito, anda muy bien compita. Estaremos al pendiente de una próxima actualización el parche de Enero (Cuando salga).
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] GabrielGuerreroHND:
ENGLISH:

I am a user of: SM-A505G.

Greetings from Honduras friends, I have tried the latest update, and the truth is that it works well. The only thing is the light consumption of the battery, but I think it is due to the higher performance of the equipment. There is still a lot of Bootloader that you can remove but it works fine.

FOR GAMING:

I only play: Call Of Duty: Mobile, and it works great, with a Game Booster to play well without Lag. And that CODM is a game that takes up a lot of performance to play at Low Graphics, and Medium FPS (Beware the fps at Maximum is very laggy, that's why I put the fps at Medium).

FOR DAILY USE:

I have tried it and it works fine, I have not had problems in any application between switching from one to another. So it's fine there.

CAMERA:

Super good! everything working perfectly. Everything is fine.

And so! I congratulate you, you are doing very well, compete. We will be on the lookout for an upcoming update on the January patch (when it comes out).
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
Stockeless 2.3 Soon
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
updated to version 2.3.1 with some fixes and improvements for F/G and FN variants
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Thatbruhmoment:
failed to stat "/tmp/config": No such file or directory when i try to flash it via twrp
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
device?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Thatbruhmoment:
Samsung Galaxy SM-A505FN
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
ok, gonna check and reupload when fix the installer
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Chinito_H18:
friend you can remove the GOS, to have a good performance in games and applications thanks.
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
no
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
rom reupload and fixed some issues and the installer
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
Updated to version 2.4 for G variant, others variants in progress
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] gnpaone:
Nice, are u sure there is volte and fingerprint support in a505f? Should I download a505g or a50fn rom for my a505f?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
dude, you have the 505f download the 505f rom ._.
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] hunk33:
A505G in the download why a505f no download link
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
cuz is not updated to v 2.4 yet, use 2.3
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] hunk33:
2.3 only g version I uploaded error my phone is a505f
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
F n G are compatible
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] q1pa:
Is this a preroot rom?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] rezabahramnezhad:
Thank you
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] lucifer:
so i lost my widevine l1 a year or so ago but today i flashed dostos custom rom and suddenly i got my l1 back anyone know how that is possibleView attachment 5438993View attachment 5438995View attachment 5439001
[Tilt, TyTN II, MDA Vario III General] jafar16:
Bonjour,

je viens d'acheter un TYTN II. Sur mon ancien TYTN, j'avais mis la rom 4.31 de shap's (en français) et je l'aimais bien.

Voici ma question : puis-je mettre la rom de shap's prévue initialement pour un TYTN sur un TYTN II ? Le gps fonctionnera t-il toujours ?

Merci.

Hello,

I just bought a TYTN II. On my old TYTN, I put the Rom 4.31 Shape's (French) and I loved her well.

My question is: can I put Rom Shap's planned originally for a TYTN on a TYTN II? The GPS work there forever?

Thank you.
[Tilt, TyTN II, MDA Vario III General] slovoflud:
:D you've made my day! :)

here's the link you need :)

http://xdaforums.com/showthread.php?t=356119&highlight=schap

good luck!
[Tilt, TyTN II, MDA Vario III General] Dust2Dust:
No you cannot put a hermes (tytn) rom on a kaiser (tytn 2).

Eventualy you can.... but you will ruin your kaiser....so don't do it.
[Tilt, TyTN II, MDA Vario III General] jafar16:
merci beaucoup pour la rom et pour vos conseils.

Thank you for your advices and for the rom.
[Tilt, TyTN II, MDA Vario III General] telegraph0000:
Exact thought...those Frenchies sure have a way for wooing zee women. Though I've never seen a ROM being wooed...

"J'ai...un...Tour D'eiffel...dans mis....panatalons..."---Ahhh Scrubs is a great show...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Aaditya ZeO:
View attachment 5438975

" #DroidOnTime "

ROM Version: 5.2

Device: PAYTON

Maintainer: AADITYAZEO

Build Status: OFFICIAL

View attachment 5438991​

"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."

View attachment 5438997

dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....

View attachment 5438999

CLEAN FLASH/First Time Installation :

01. Download the ROM, Firmware and GApps from the links above.

02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.

03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"

04. Create backup. i.e. EFS

## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##

05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"

06. Flash the ROM and TWRP installer.

07. Choose Reboot -> Recovery

08. Install GApps & Magisk.

09. Reboot -> Bootloader

10. fastboot -w

11. Reboot and Enjoy.

*Note-1: Slots, ROMS install to opposite (inactive) slot

If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"

*Note-2: Firmware's

* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)

DIRTY FLASH :

1.Download the latest build.

2.Reboot to recovery.

3.Flash the latest build along with the twrp.

4.reboot to recovery. (very Important)*

5.flash optional packages like gapps and magisk.

6.Wipe Cache.

7.Reboot.

Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.

Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.

View attachment 5439003

CLICK ME

View attachment 5439005

COMPLETE CHANGELOG : https://changelogs.droidontime.com/

View attachment 5439007

AOSP

Lineage OS

Pixel Experience

Dirty Unicorns

Project Lighthouse

And all other open-source Devs/Teams.

View attachment 5439009

Mohan CM - Founder/Core Developer

Iacob Ionut - UI, UX Developer/ Core Developer

Sipun Kumar - Developer/Maintainer

Special thanks:

Manish Bajpai - Web Developer

Important Links

If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM

Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd

dot OS source

dotOS-Device Sources

Telegram Group

Telegram Channel

Website

Downloads page

REPORTING BUGS !

As soon as the problem occurs, take a LOGCAT!

for more READ THIS

and do not forget to send it to us 😜

View attachment 5439011

Contributors:

AadityaZeo

Source Code: https://github.com/DotOS

GitHub : - https://github.com/aadityazeo

ROM OS Version: 11.x Android R

Version Information

Status: STABLE

Current Stable Version: v5.2

Stable Release Date: 16-10-2021​
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] noogi:
Finally :). Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Aaditya ZeO:
Pro tip :- Enable blur option in developer settings, QS will look much more elegant.

Enjoy 👍
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Black-Zero410:
I'm so in love with this phone, thanks for your work, I'm going to test the rom today :D
[Nova Launcher] MrIc3c0ld:
Hi folks,

I'm a big fan of Nova. Since a few weeks I'm getting a purple-ish background on some parts of the launcher. E. g. when I hold the home screen for reaching the widgets. I added a picture. Is there anyway to change this?

Thanks in advance.

Regards

FlipView attachment 5439015
[Nova Launcher] MrIc3c0ld:
No-one? :(
[Nova Launcher] 0justin8:
I've got the same problem except it's worse
[Nova Launcher] MrIc3c0ld:
Mod edit: @MrIc3c0ld Thread closed as duplicate of

https://xdaforums.com/t/nova-launcher-purple-ish-in-some-situation.4350853/

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

If you want to add more information, just edit the already existing thread.

Regards

Oswald Boelcke

Senior Moderator

Hi folks,

I'm a big fan of Nova. Since a few weeks I'm getting a purple-ish background on some parts of the launcher. E. g. when I hold the home screen for reaching the widgets. I added a picture. Is there anyway to change this?

Thanks in advance.

Regards

FlipView attachment 5439015
[ASUS ROG Phone II Questions & Answers] Anmol@70:
I try all methods of fastboot.ode but don't get into fastboot mode it open into normal reboot mode
[OPPO Find X3 Pro] Gtenkas:
Hello there to everyone.

I have a disconnecting issue with my watch and would like some help if anybody knows a solution.

I have bought the Find X3 Pro and paired it with my Huawei Watch GT through Huawei Health App. Everything ok till then.

The problem is that the Phone closes the Health App in the background whatever I do.

I gave it the permissions to run in background and auto start and even locked it in the recent tag but still no luck.

It keeps always disconnecting.

The Phone is great but my Watch is useless.

Thanks in advance for your replies.
[OPPO Find X3 Pro] colossus_r:
See if you have the last option enabled.

I have a gt2 pro and it works just fine.

View attachment 5441445
[OPPO Find X3 Pro] Gtenkas:
I can't find the last option on my phone.
[OPPO Find X3 Pro] grisusu:
I have Huawei watch GT and it works fine