yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
it depends on what you want to do with it.i find its a smooth rom optimized for performance and battery optimization.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
but you can install and report the findings . the only way things get improve is by trying an reporting issues and matters to developers for their attention.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Maxi693:
Thank you I will install it
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
sorry i forgot to include new revenge ui, i will release new update today
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
its ok. dont worry about it. It give me a new chance ot try out something new.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
so do you have your latest update upload to take rom fora a test drive
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Maxi693:
The rom is great all very fluid
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
do agree. at least its an official android 11 while we se what others do. I still have not seen other android 11 roms.so this is the rom I use on my moto g7 power device at the moment .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Maxi693:
Styles and wallpaper stops working when placing an animated wallpaper
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
I already fixed, just redownload and it will have revengeui
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
thank you for your report, ill investigate
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
good to know.when i have some tiem .i will reflash as thisis not my primary device any more its pixel 4 a . dont know why with the device my device 1955-2 always encrypts after any rom install. i have not bothered to root to se if that will fix it or not. but its one strange thing about this model of the moto g7 power 1955-2 .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] BadWolf2705:
I already downloaded the RevengeOS 4.0 ROM for G7 Ocean and Nikgapps Stock, just do the flash by TWRP normally installing ROM first and then Nikgapps ??
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
sure
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] BadWolf2705:
[QUOTE = "Electimon, postagem: 84190159, membro: 7198594"]

certo

[/CITAR]

Tudo bem se os arquivos ZIP (ROM e Nikgapps) estiverem no cartão SD? Tentei criar o backup antes de fazer o flash mas está dando erro. Estou com "medo" de fazer o flash e não funcionar !? Meu G7 Ocean já está com o bootloader desbloqueado e o TWRP instalado ... Basta fazer o wipe primeiro e adicionar a ROM e Nikgapps ao TWRP e instalar? A ROM funciona tudo? Incluindo impressão digital?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] BadWolf2705:
I installed the ROM. It is very fluid and good, but the Radio App does not work and every time I try to share my internet through the access point it is disconnecting and dropping the wi-fi. Will the ROM be updated via OTA or only manual via TWRP?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
are you talking about the FM Radio. if ahts what your talking about, that has been broken in custom roms that i have tried from paranoid, to pixel to evolution to revenge.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
thank for developing.saw on telegram that there is a new build out with jan 2021 patchs and fixes. will give it a spin as soon as I have some free time.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
looks like updates will be done manually through twrp instead of an OTA function. unlestaht is planned down the road for the rom.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
Please redownload and update

2021-01-25:

Fixed Hotspot

January Patch
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
It works on my device, try the new update
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
Hi, these were fixed in the latest update, thanks.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
Spoiler content hidden.

Ok, got that figured out.

I'm assuming the need for Magisk on page 2 is no longer needed. And my main issue was I was coming from an encrypted/pin rom previously. So I had to erase everything except the external SD card, and then "Format Data" in TWRP. Once I did that I was able to install Revenge 4.0, reboot back to bootloader, boot TWRP, install TWRP (3.5.0_9-0) via sideloading the installer zip, reboot back, install NikGapps Core, NikGapp addon for Pixel Launcher and Adaway, then Magisk-R-A11.zip from page 2. And it was up and running in a few minutes.

I set up a PIN and verified that I could reboot back into TWRP and decrypt the user data.

As it turns out, I could upgrade to the latest Magisk 21.4, and still able to use TWRP without breaking it.

Though it would fail SaftetyNet, so did the following steps:

First attempt was to install the MagiskHide Prop Config, but that only passed the Basic Integrity step

Then I tried the new Universal SafetyNet Fix module, same result

Then I installed Busybox for Android NDK module

Installed Termux

Typed 'su' in it to gain root access

then 'props', followed the step to change edit device fingerprint, then chose "Pick a Certified Fingerprint"

From there picked 16 for Motorola, 16 for Motorola G7 Power (9/10), then selected Android 10 (9 and 10 being the only two options)

Confirmed and rebooted

Then SafetyNet finally passed completely.

I then made sure to clear cache/storage for Google Play Store, upon doing that, apps that were hidden from search (ie: Netflix, Hulu, etc) showed up again and was able to install while rooted.

So in a nutshell, as of Jan 30th 2021 I can confirm that this rom

Works with TWRP 3.5.0_9-0 installed AND Works with Magisk 21.4 and Magisk Manager 8.0.7 (and can reboot back into TWRP, and decrypt user data, after having installed Magisk 21.4)

PS: Revenge Launcher seems to crash if you try to switch to it with PixelLauncher installed.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
Testing Streaming apps with the current Revenge 4.0 (and Magisk 24.1 with a successful SafteyNet Pass),

Working = opens, logs in, plays content

Netflix - Working

Hulu - Working

Disney+ - Working

Plex - Working

Tubi - Not Fully Working, "DRM Error" when attempting to play some content, some will play, others will not

Prime Video - Not working, tries to show login page, then goes to "Sign in Failure", If I reboot, I'll see the login page for a few seconds, but the moment I put the cursor into the username box, it pops the same "Sign In Failure" dialog box.

Likewise none of the Amazon apps (Music, Photo, Shopping, Kindle) will work either, some will open but the moment you try to sign in, it quits. Music for example just says "Update Chrome" (which is already updated) and won't continue. Basically all the apps if there is a message say something like "No Internet Connection".
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] JosFlix7:
ok this is probably a stupid question but if i already have RevengeOS installed how do i update without losing my data?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
Some would call that a dirty flash.

Basically have ready the rom on the external card (or PC if you're doing a sideload), as well as any addons (NikGapps, Magisk of the same or later version than you installed), since the rom flash will erase any addons.

Boot into recovery (if you have an intact recovery), flash the rom, reboot back into recovery since it'll likely switch up the A/B on that install, flash the Gapps you use of the latest version, flash addons, and flash magisk if you had it before, wipe Dalvik-cache, And boot up.

The rom and addon installs should not touch the userdata area, but good to have a backup just in case, be it a TWRP backup or dragging files to computer. But if you run into problems you might have to flash clean.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
To follow-up, on a hunch I disabled/paused the Adaway addon from the NikGapp, which was being applied by root (as opposed to VPN). It would appear that AdAway is what was breaking all the Amazon apps.

Also, while Tubi shows a DRM error on most videos, you can still cast it to chromecast without a problem. Fine for me because I don't watch on my phone I just use it to launch shows to my TV.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
I can't update QKSMS.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
Found another thing that doesn't work. When you go into

Settings -> About Phone -> Emergency Information

Fill it out, but it's nowhere to be found on the lockscreen, and tapping the "Emergency Call" button when you swipe up does nothing.

Probably one of the more important 'base' feature that should be working.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] bosko1333:
Is there any option to turn front LED off when charging? Mine is always on.

I do not want to use Magisk and LED Control [ROOT] app (which works). Is there any other way to change the code?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
There was a setting in both LineageOS and Ressurection Remix, but they're both Android 10.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Electimon:
"

RevengeOS for ocean support will be dropped, thank you for your support.

As you probably know my ocean has some damages, mainly the USB TYPE-C port. It is damaged, I can't reliably debug or dev for it without it disconnecting midway through a sideload...

Thank you again for your support thus far.

"
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kbeezie:
Unfortunate considering how young it's been.

Hopefully there are other 11.0 ongoing in the meantime I'm going to keep using this rom til I can't any longer. It's been good to me thus far.

Thanks for the work.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
totally understand.thanks for building the rom for the time being. will move on to a bunch of other android 11 roms that are on telegram , like havik 4.1, evolution x 5.4, pixel experience plus android 11, lineage 18.1 unofficial, and a bbunch of others.these all can be found on the telegram moto g 7 power build telegram group.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Chriskinda96:
Thanks for this. Im passing both now. However, it seems that all my apps that previously used biometrics are no longer showing it as an option. I've googled everything I can think of, apparently I'm the only one with this problem. Any ideas? Thanks
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
there is another official android 11 rom a few post above that you can try for android 11 does have gapps built in.
[Touch Diamond, MDA Compact IV General] mpovolo:
Want the vibrate to turn on when I am at work.

thanks
[Touch Diamond, MDA Compact IV General] RockaleW:
Don't mean to bring up an old post. I noticed it when I created an new thread. No one has an recommendations for an app?
[Samsung Galaxy S7 Questions and Answers] Stymix:
Hello,

I have actually a problem with my Samsung G7.

He is in ODIN MODE.

I tried to use the "POWER + VOL -" combinaison, but it was blocked in "Samsung Galaxy S7 powered by ANDROID"

I know I can use an another ROM and Firmware and ODIN but I want to keep my photos stored

Someone can Help me please ?

Best Regards,

Stymix
[Samsung Galaxy S7 Questions and Answers] Stymix:
Any news please
[Samsung Galaxy S7 Questions and Answers] djibe89:
Hi, what do you mean by Odin mode ?

You may try my tutorial from step 3 and tell us what happens.

One in TWRP, you can explore phone's memory.
[Samsung Galaxy S7 Questions and Answers] riojosepha:
Hi there, is the phone OEM Unlocked? If so, you can flash TWRP via Odin or Heimdall.

Try doing Power Button + Volume Down + Home Button again multiple times until you get into odin/download mode.
[Redmi 9 / Poco M2 Questions & Answers] mhark.moby:
please delete this thread.

someone opened this topic.

thanks moderator
[Galaxy S 5 Q&A, Help & Troubleshooting] liquidraver:
Hi all!

I've run into the problem in the title and solved it, so I thought I'll share my experiences.

1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:

Samsung Accessory service:

https://play.google.com/store/apps/details?id=com.samsung.accessory

Galaxy Watch plugin:

https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin

Galaxy Wearable:

https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager

The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)

2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one :)

To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.

To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:

/system/build.prop

/system/vendor/build.prop

/system/vendor/odm/etc/build.prop

You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.

You can now "download" and "upload" build.props. Between adb pull and adb push, you need to edit the downloaded build.prop like I wrote above.

adb pull /system/build.prop
adb push build.prop /system

adb pull /system/vendor/build.prop
adb push build.prop /system/vendor

adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc

EDIT: on lineageos 18 you need to edit two more files:

adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop

adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop

Restart into system after this.

The 3(5) build.prop edit will do the work and Galaxy Wearables will start and you can connect your watch.

Important info again after every OTA or manual LineageOS update, you need to edit build.props to continue using your watch (watch won't connect after OS update at all, without build.prop edits)
[Galaxy S 5 Q&A, Help & Troubleshooting] kierownikk:
Fantastic. I just installed LineageOS 18.1 on my Tab A6 and I Galaxy Wearable app didn't want to work but thanks to your post I managed to get it fixed. Great work. Thanks
[Galaxy S 5 Q&A, Help & Troubleshooting] WhipWhip:
Thx, works perfectly on a Galaxy S5 (klte) with LineageOS/eOS based on Android 11 with Magisk-Root.
[Galaxy S 5 Q&A, Help & Troubleshooting] Bernd1712:
gilt das auch für 19.1
[Galaxy S 5 Q&A, Help & Troubleshooting] Bernd1712:
this also applies to
[Galaxy S 5 Q&A, Help & Troubleshooting] desklamp:
Hi, everytime when i wanted to push the changed build.prop file to system/vendor/odm/etc adb says :

adb: error: stat failed when trying to push to /system/vendor/odm/etc: Not a directory

But the build.props from the other directories work. Can someone help me? And sorry for my english...

Thanks

Edit: I'm using an S5 klte with official Lineage 18.1
[Galaxy S 5 Q&A, Help & Troubleshooting] j007!:
probably a bit late, but for anyone having the same problem.

I had followed the installation method for installing lineage 18.1 on my s4 and therefore used the recovery image linked on the instruction website of the official lineage os team. But this recovery image

1.doesnt support root access to the /system file sys,

2. only mounts it read only

and therefore even when mounting it, you can only read some stuff, but other things like the vendor directory in this case not.

(As far as i understood it, and confirmed via the adb shell :-)

The solution for me was to just download the TWRP recovery image onto the phone (no need to reinstall lineage os therefore), which enables mounting with root access and r/w permissions.

Hope this helps!
[Galaxy S 5 Q&A, Help & Troubleshooting] htc_softbank:
I know this is a old thread, but having the same problem. I rooted my Note 10+ with lineageos 20 and wondering if there's a magisk module to replicate my original OS, etc fingerprint and fool these stupid OS modification restrictions that way?
[Galaxy S 5 Q&A, Help & Troubleshooting] htc_softbank:
I followed this and I was able to get samsung wearables app to work. Apparently it's a Samsung phone issue only with root/custom os.

Unfortunately I can't get past the agreement screen for Samsung watch 4. I guess it's incompatible with lineageos 20 with microg.

Galaxy Wearable App on Rooted Phone Help

Hello, I am trying to install the new Wearable app on my galaxy s9 that is running a custom rom / rooted. The app says it is not compatible due to the phone being modified in an unauthorized way. I know people got the previous wear app to work on...

xdaforums.com
[Galaxy S 5 Q&A, Help & Troubleshooting] rmajid2:
Hi,

I've flashed LOS21 on my mi a3. my galaxy watch 6 can be paired with my phone successfully however, it can't be connected again once it is disconnected.

any working solution to this problem ?

I've installed all three necessary apps which are mentioned above.
[Galaxy S 5 Q&A, Help & Troubleshooting] JedidroidX:
I have the same problem on my oneplus 8T with lineage 21. The wearable app says google mobile services is being updated and cannot connect to watch. Take note that no issues when using stock Oxygen Os from oneplus and is a lineage Os issue

Screen shot below, hopefully this can help in a resolve.View attachment 6096943
[Galaxy S 5 Q&A, Help & Troubleshooting] rmajid2:
I have exactly the same issue on my mi a3 running lineage os 21. I can provide logcat, too.

I just flashed back stock android because I couldn't use my watch with LOS21. Hope there is work around and a solution to this problem by some experts.
[Galaxy S 5 Q&A, Help & Troubleshooting] Borland04:
Same for my OnePlus 9R (Nameless AOSP) + Galaxy Watch 5. It worked fine at first, but next morning I got the same error message - "Google Mobile Services is being updated". After a few days of my attempts to restore connection, I don't get this error anymore - app is just trying to connect a few minutes and then fails without any reason.
[Galaxy S 5 Q&A, Help & Troubleshooting] mallika the satanist:
Have you tried not using microG and instead using Google Play Services?
[Galaxy S 5 Q&A, Help & Troubleshooting] Borland04:
Ok, so my watch started to work recently without any reason (they've been discharged, and after I charged and turn it on, it just connected to my phone). Try to update watch OS if you didn't do that yet.
[Android Q&A, Help & Troubleshooting] tekerjerbs:
tablet model RCT6213W23H1

android stock 7.1

one day after being off for a while with the battery drained, it would just sit on the Maven Pro boot logo for hours after charging/turning it on and not load the OS. i've left it plugged in overnight to boot and it will sit there forever. i've let the battery fully drain and charged it again but still won't boot all the way

lots of guides about doing a wipe and reset from recovery which i've done multiple times but still the same issue

USB debugging was not previously enabled (not that it matters since it's been wiped so many times now)

i've connected it to my PC using both USB ports (USB mini charger port and USB A port) and device manager does not show a proper device description and it will not accept any driver i throw at it from this thread and this thread

it's not being picked up by fastboot/adb at all

i can't find the stock rom for it

doesn't have twrp but my goal is to at least get twrp on it and see where i can go from there as it will have more troubleshooting options

i have some options from the recovery menu, the only realistic one being to load something from the external SD card but without the stock ROM to try reflashing it, i'm not sure what else i can try via SD

just looking for some recovery options here to force it to boot. i've opened it up so i can access the board if needed. thx
[Touch Diamond, MDA Compact IV General] veil:
HI :confused:

I am going to buy an O2 diamond . Can i change its language to English and ..........What will be the procedure (if anyone can provide links). Thanxx
[Touch Diamond, MDA Compact IV General] xep624:
re

Hi,

changing the language won't be possible if you don't want to loose the guarantee.

But: I recommend to update the newest Original HTC ROM, beause it's d*mn faster - and if you do this, you can choose the english ROM.

(I have an german XDA Diamond and did that too. Now it's way better than ever!)
[Touch Diamond, MDA Compact IV General] veil:
Thanx for the info but can u link me to the rom u flashed
[Touch Diamond, MDA Compact IV General] veil:
Plz can anyone provide me the links for flashing rom on Xda diamond
[Touch Diamond, MDA Compact IV General] xep624:
http://xdaforums.com/showthread.php?t=400402

http://xdaforums.com/showthread.php?t=400411
[Touch Diamond, MDA Compact IV General] greebear:
I flashed the german version, because i was not sure if the WWE ROM has Umlaute (äöü etc)?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] shivatejapeddi:
AospExtended 8.0 (Android 11) Build 6 for POCO F1:

Vannila build : https://sourceforge.net/projects/shivatejapeddi/files/A11/AospExtended-v8.0-beryllium-UNOFFICIAL-20201118-1828.zip/download

Gapps build : https://sourceforge.net/projects/shivatejapeddi/files/A11-GAPPS/AospExtended-v8.0-beryllium-UNOFFICIAL-20201119-0348.zip/download

Device Side Changes:

- Switched to CAF LMKD

- Fixed Ram management issues

- Fixed issues related to bubbles

- All status bar and navigation issues fixed

- Added Back Stock display Modes and and KCAL

- Added supported for Enhanced Display Mod (Check Notes)

- Battery stats issues have been fixed

- Added New Balanced 2 profile

* People facing touch issues flash NoName kernel 1.0 (Check Notes)

AospExtended 8.0 (Android 11) initial Release :

Download : https://sourceforge.net/projects/shivatejapeddi/files/A11/AospExtended-v8.0-beryllium-20201029-UNOFFICIAL.zip/download

Device Side Changes:

- Switched to A11 hals for Display,Media,Audio

- Updated Perf Stack to Android 11

- Updated Media Stack to Android 11

- Updated DPM to Android 11

- Updated DRM stack to Android 11

- Switched to Display Config 2.0

- Updated Graphics and display Stack to Android 11

- Fixed Screen record lags

- Swicthed to QTI bluetooth

- Switched to Thermal hal 2.0

- Swicthed to To 2.1 Health hal

- surfaceflinger tweaks for better smoothness

- Rebased Kernel based on Android Tag

- Fixed DIRAC Settings

Telegram Support Group : https://t.me/aexpocof1
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] callmebutcher101:
Selinux and safetynet status ?

Some screenshots ?

Thanks for the rom. Would really love to see the development on caf extended project.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] shivatejapeddi:
Selinux is permissive, will be enforcing in coming builds,

Safety net requires magisk to be flashed
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Demetris:
Hi, great work on this.

Any doorstoppers this cant go official?

I ask because ota updates are more convenient vs checking this thread if and when there is an update.

Keep up the great work nevertheless :D

p.s.

I also noticed you are using a slightly old kernel any reason to keep a 6 months old kernel still kicking?

Check https://android.googlesource.com/kernel/common/+/refs/heads/android-4.9-p/Makefile
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] shivatejapeddi:
we will be official, as still aex hasnt announced official releases, so iam holding it,

anyway yeah kernel will be updated
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Ravindrasan:
Does this rom has option for circular battery icon or % inside the icon, i couldn't find one though.