yashsingh1/xdaforums huggingface dataset:
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] valentinc22:
Yes, I mentioned that in post #132.

Aurora Store apps are identical with those downloaded from Google Play and DO contain those Gapps components, as Aurora is just a proxy for Google Play, it's not a store in and of itself.

I use Aurora Store myself, but only for apps that don't require GPS (which work fine). For those that do,

which in my case are just 2 (Waze and OSMand), I download them from other sources and don't

bother that much updating them (as updates are not critical on these).

OSMand apk is available for download on their website and for Waze I downloaded an apk from Aptoide

and use that version (did not keep Aptoide itself).

Also be careful not to update these apps in Aurora, as updating will render them non-functional.

I mention this because they will obviously appear in the update menu when you update other apps.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
Hello VoltageOS users, i hope you are are having a great weekend, quick status on current scenario. My server has just got over. So until we get a new server to keep this project continued i am sorry to address the project is currently on hold.

To help us overcome this issue, you can help us with donating a Google Cloud Platform (gcp) free trail.

this wont cost you anything, basically it refunds your Rs.1 after it verifies.

Gcp are very important for us to keep building as we don't have powerful pc to keep up with it.

Those who are interested to donate a gcp free trail can follow this procedure

Gcp free trail guide

if you are successful in getting a gcp free trail you can contact me on telegram

https://t.me/PptOo7

Thanks to everyone, i repeat we don't want any type of crowd funding or donation, we wont ask for your hard earned money, this is free trail will take just Rs.1 for verification and that too will be refunded basically free of cost.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] danielfreund:
thank you so much
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cris2d2:
Can someone tell me if this ROM has the following features?

- AOD Schedule;

- Long (or scrolling) screenshot.

I always keep my storage decrypted by flashing DFE after every ROM flash. If I want to use Voltage, can I flash it from official TWRP? I see that it's decrypted by default so flashing DFE is not required if I want to keep everything decrypted.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] danielfreund:
is it safe to include wipe metadata when having a clean flash of a custom rom?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
Special thanks to @ BrorDavid (Telegram ID) for donating me gcp server, VOS lives again
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] danielfreund:
does this custom rom support f2fs?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] swapyworld:
Can anyone update dirty flash instructions, in case Rom is flashed followed by EFE to encrypt the storage.

How to make next dirty flash to update the rom, as custom rom is not encrypted by default, will it cause issues flashing on encrypted storage?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
Do you guys want some Tiramisu ?

Hope you will have a taste of it soon until i make it daily drivable

Till then enjoy the screenies
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cudi90:
Can anyone tell me how to change the view back? All of a sudden it looked like this. Have not adjusted anything.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Krullendhaar:
Is it possible to hide the gesture pill at the bottom?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cantonak:
Gesture Settings > Fullscreen gestures
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Alexintheecho:
In Voltage Launcher settings (long press in a empty space in the home screen), miscellaneous, turn off grid style recent apps
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cantonak:
I just want to report my observation with this rom(v 1.7) after two weeks of use. I clean flashed rom according to flash instruction with encryption enabled. I really like the rom but I found couple problems.

Phone heating up when GPS tracking app is running in background, battery drains quickly. Can Google Play services be the cause? In GSam Google Play services are always on top by quite margin. I found out that my log is spammed with these messages all the time. Around thousand lines every second.

2022-08-21 18:32:51.353 20140-20236/? I/SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.01 seconds.
2022-08-21 18:32:51.355 20140-20236/? I/SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
2022-08-21 18:32:51.358 20140-20236/? W/SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
java.lang.IllegalStateException
at xba.k(:com.google.android.gms@222615044@22.26.15 (190400-461192076):0)
at bmnq.f(:com.google.android.gms@222615044@22.26.15 (190400-461192076):0)
at bmmj.a(:com.google.android.gms@222615044@22.26.15 (190400-461192076):10)
at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:com.google.android.gms@222615044@22.26.15 (190400-461192076):12)
at com.google.android.chimera.IntentOperation.onHandleIntent(:com.google.android.gms@222615044@22.26.15 (190400-461192076):2)
at uzr.onHandleIntent(:com.google.android.gms@222615044@22.26.15 (190400-461192076):4)
at ffi.run(:com.google.android.gms@222615044@22.26.15 (190400-461192076):3)
at ffh.run(:com.google.android.gms@222615044@22.26.15 (190400-461192076):11)
at cfvf.run(:com.google.android.gms@222615044@22.26.15 (190400-461192076):2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)

Anyone else has the same problem or it's just me?

It also seems that mobile data restriction per app is not working at all. If i disable mobile data for certain app, it can still access internet.

I have "Night light" enabled permanently, to reduce eye strain when reading feeds. Before screen automatically turns off, it lower brightness for couple seconds, when I touch screen to light up the screen "Night light" is disabled. I have to lock/unlock the phone to enable it again. Adaptive brightness also disabling Night light.

Thanks to the team for great work I hope some of these issues could be fixed in newer version in case these problems are not related only to me.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] jimladen:
Hi everyone. I can't make visualisation work.

Can anyone help me?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cudi90:
I have the same problems. Hope of a fix
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] jimladen:
Battery drain is crazy. What i have done wrong?How can i fix this?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cudi90:
@jimladen

It's because of Google Services. There is a bug there.

But beware: if you have entered the command under Termux, Gpay no longer works.

I hope that this will be fixed soon by the developer...

su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] jimladen:
Thanks for the response. But i really need gpay .
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] zamc:
you have to be root for that command to work?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] cudi90:
Yes, and after that I removed Root again.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] zamc:
thanks

is there a link or something to describe the procedure? i really wouldn't like to reinstall rom from start!!
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
Guys please try to understand you drain is due to gapps.

And we here at VoltageOS are vanilla rom.

We dont ship GooLag bloat in our rom.

So its none of my concern or my team concern to fix your gapps issues.

Let me make it clear we are VoltageOS devs and not Gapps devs.

We wont care to fix a problem that we dont even ship with rom in first place.

Hope you all understand and stop asking us for GooLag fixes.

Anyway LineageOS has merged Aug-Sept Cves on their gerrit

https://review.lineageos.org/q/topic:S_asb_2022-09

We have picked them and after proper testing we will release Vos 1.8 in this week itself if all goes proper, Get ready guys for final A12.1 | L build.

1.8 will be final release and no support will be provided for a12L builds in near future.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] zamc:
So after last 1.8 version..we are waiting for Android 13? 🙂
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
Finally the wait is over and here we are at EOL (End of life) update for VoltageOS 1.8, the last update for A12.1 | L .

It comes with CVE's merged for August and September but it will still show Security patch as july for passing SafetyNet and various other bugs like netflix dosent show in playstore.

Also EFE users here is an important thing for you as i will move to A13 i have decided to use same fstab on final 1.8 and future a13 builds so you will need to flash A13 EFE from HERE

Build Date : 09/09/2022

Changelog :

Device Side :

- Kang IMS system blobs from Redmi/alioth/alioth:12/RKQ1.200826.002/V13.0.3.0.SKHCNXM:user/release-keys

- Fixed native carrier video calling works only on google dialer

- Xiaomi Parts : Added back Dirac

- Xiaomi Parts : Dirac fixes, Handle more error for dirac

- Xiaomi Parts : Introduce haptic feedback level adjustment

- Xiaomi Parts : Vibrate when changing haptic feedback level

- Xiaomi Parts : Don't explicitly set android:theme for activities

- Audio config misc improvements

- Enable Volte support for few Indo carriers

- Allow rmt_storage to acquire wakelocks correctly

- Fix ctl.interface_start logspam by dropping vendor.qti.hardware.cacert hal from manifest

- Add missing entries for vendor.qti.data.factory in manifest

- Add missing entry for com.dsi.ant in manifest and import ant blob from Miui 12.5.6.0

- Improve haptic feedback for calls and message by configuring vibrator kernel nodes for QTI vibrator HAL

- Fixed audio in chrome with soundcloud

- Disable redir_party_num

- Unpin updatable media and launcher from memory

- Build nxpnfclegacy hal & address its sepolicy

Source Side :

• Merged August and September Android Security Bulletin (ASB) commits.

• Introducing VoltageOS SetupWizard.

• Added SeedVault.

• GMSCompat changes.

• Added SleepMode.

• Fixes on reTicker.

• Added Force Background Freezer.

• Implemented support for Strict Standby Policy.

• Changed Background for inactive rows in Volume Dialogue.

• Added Statusbar Notification Ticker.

• Fixed inconsistent Navigation Bar color in certain apps.

• Fixed Hidden Clock Mode.

• Fixed Statusbar padding on the left side on LockScreen.

• Added Fingerprint wake unlock mode list preference.

• Rearranged Device information page.

• Added preference to Battery Optimisation Page.

• GameSpace changes :

> Reworked Lock Gesture.

> Added "Do Not Change" option to Ringer mode.

> Added Memory Information in Game Overlay.

> Exposed icon in Launcher.

> Added in-game Danmaku.

> Added reTicker.

> Properly filtered duplicate notifications.

> Implemented Auto Answer/Reject calls.

> Added notification for incoming call number when receiving/rejecting call.

> Added toggle to turn Overlay menu off.

> Fixed crash when "Device & App notifications" access is enabled.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] zamc:
hi, if we are on 1.7, can we do a dirty install for 1.8? and is there a guide for dirty install?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] danielfreund:
hi, the rom is awesome. thank you very much
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] zamc:
Any news when we have voltage os android 13?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
The gcp free trail period has come to an end, if you wish to see the project continue with Vos 2.0 a13 consider donating a gcp free trail, its free of cost & i will never force anyone to donate money for AOSP unlike others.

Its open source project and should be free for everyone.

for this to be alive i will need servers and without them its not possible to build roms

read the quoted post for further info on how to donate a gcp free trial

Thankyou for your support, have a good day ahead.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] arjunraina7:
Hi,

Can anyone help me with the ringtones from this rom, I have been trying to extract some ringtones from this rom but unfortunately I can't and the guides online aren't helping either.

Thank You
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Pranav Temkar:
I hope mods are having a great day, sorry to disturb you all and take a bit of time, i would like to close this thread as the rom is now EOL (End of life)

Thank you
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Sib64:
INFO MODERATION

Following the OP's request, the thread is permanently closed.
[Google Pixel 3 XL Guides, News, & Discussion] Bradypodion:
Hello!

I am new to Pixel phones. I own a Pixel 3 and wanted to root it without flashing TWRP. It's been years since I last rooted a phone and this Magisk app is really nice.

I used it to "systemlessly" root my Pixel 3 XL and now I read that to relock I would need to flash the stock boot.img.

What if I just keep the one I patched with magisk? Has anyone tried it? If I do and it ends up bricking my phone, will I be able to unbrick it?

Thank you
[Google Pixel 3 XL Guides, News, & Discussion] mgp53:
Do not do it.. you will permanently brick it.
[Google Pixel 3 XL Guides, News, & Discussion] CosmicDan:
Not possible. At the moment.

The Pixel series does support loading the device with custom keys, so you can use a custom-signed boot image and lock the bootloader - technically - but Magisk won't work with this.

The closest thing k can find to such a feature is this open discussion: https://github.com/topjohnwu/Magisk/issues/2323

....but Pixel 3 has AVB 2.0 iirc, so *shrug*.
[Motorola Edge + (2020) Guides, News, & Discussion] bjf189:
i ran into trouble with this. the firmware you have and lineage your using is now outdated but i tried with both your version and the updated ones and 18.x version of lineage does seem to detect my sim card and the new one lineage 19 detects it but i get the error from verizon that my phone cant be authenticated for calls but everything else works. i notice when im running updated stock, the sim card reads fine and service works normally but before when i had it running older stock firmware (android 10) i got the same thing. everything would work but calls. then when i updated the stock firmware, everything worked. so im not sure what im missing here when trying to follow your direction for getting this installed but maybe you know whats going on since your a verizon user using the global variant. please write me back when you get this. thanks a bunch
[Motorola Edge + (2020) Guides, News, & Discussion] Knuxyl:
Well I only had the phone as a test for getting mmWave 5G on the global variant, which isn't possible due to a proprietary solder pattern on the board, but I no longer use this phone.

What I would recommend for you is to flash the NON-HLOS.bin from the stock firmware that worked for you without a problem. It's the modem firmware and it could cause problems like that. I didn't have any issue with my sim card, calls worked fine over CDMA and I could get text messages and LTE data worked.

I have never even seen the error that says the phone can't be authenticated for calls. Is it coming from a verizon app or is it an android error? I would also suggest to make sure the correct APN is being used, should be VZWINTERNET. I had an issue with an older motorola where it would for some reason randomly switch to some other VZW APN that was wrong.

I didn't do thorough testing of this, I just wanted to get the baseline for getting custom roms running, but I didn't encounter anything like what you're going through. Considering you had this problem on a certain stock firmware version, my best guess is the modem firmware. I did flash the VZW firmware on the phone and that worked as well, maybe you should try flashing that modem firmware? I didn't have issues, but I can't 100% recommend it because VZW expects the QTM 5G modules to be present, which it isn't. I don't know if this could cause hardware issues. Other than that, the phones are 100% identical.

Sorry I didn't get back to you sooner, XDA's "stay logged in" checkbox does not seem to work correctly and this website is a hassle to navigate.
[Motorola Edge + (2020) Guides, News, & Discussion] bjf189:
I'll try flashing the Verizon modem when I can. Recently, my service randomly died and I turned on airplane mode to restore service but the unable to authenticate for calls happened again when it worked fine before. I had to restart the phone to get calls working again. No idea what it was about. As for the apn, I was going to transfer the apn over from my s21 plus but it seems the verizon sim already sets the apn automatically to where it's not able to be changed. It's all greyed out. I noticed that I also got the unable to authenticate for calls before I updated the firmware. I bought the phone used and it was behind in updates. When I updated to the second most recent update, I noticed calls started to work. I haven't updated to latest since installing magisk with root broke the Ota update. I could update with a pc easy but I haven't since the things listed here are now out of date so trying to stay with the firmwares listed here. Lastly for 5G, i checked the bands the phone supports before buying it and I believe it matched one or two bands with 5G and I do get 5G in few areas. It also supports most LTE bands that Verizon gives. I didn't see any cdma support, only GSM but from my understanding GSM and CDMA is an older thing when it came to 2g or 3g. What I've gathered is if voice can be done through LTE then calls would work. So just a tip on the testing and things I've come across so far
[Motorola Edge + (2020) Guides, News, & Discussion] bjf189:
I just noticed in the thread that voice over LTE doesnt work. I wonder if that's my issue? However I see CDMA voice is working so says the thread here. It's confusing at this point
[Motorola Edge + (2020) Guides, News, & Discussion] Knuxyl:
Ok I remember now when I was trying to enable VoLTE the calls just wouldn't work. I didn't get an error though. You have to turn off VoLTE for it to work again. This is in Settings/Network & Internet/Mobile Network/Advanced Calling.

The developer of the lineageos gsi was aware of this issue and tried to fix it but I guess it only applies to whatever phone he was testing with.

As long as the APN says VZWINTERNET you should be fine. Trying to flash over another APN isn't worth the effort and can cause more problems than it could fix, the values are correct as long as the right APN is being selected.

CDMA is Verizons standard calling radio technology, was also used by Sprint. CDMA is being phased out though to be replaced by LTE entirely. I don't know when this will happen. If you check the GSMArena link in the first post you will see all the bands listed on this phone, and it does support CDMA, which is why calling works without VoLTE.

Considering you were having problems on the stock firmware, it seems like your issue is more than just VoLTE not working, because what you explained is not a typical issue, and no matter what stock firmware you were on, VoLTE and CDMA calling both should've worked out of the box. I would test to make sure your Verizon account even has VoLTE support first because that seems to be the only reason for error messages popping up like you had. Although this doesn't really matter though because this method does not support VoLTE from what I tested.
[Motorola Edge + (2020) Guides, News, & Discussion] bjf189:
Well I will do more testing here shortly. I noticed that on lineage 18.x (Android 11) I get a missing Sim card error when a Sim card is present. Then with latest lineage 19, I get no sim error except the calling authentication error. I have Verizon firmware with the modem now so I'll try testing lineage again with the Verizon modem to see how it plays out.

UPDATE: i tried both lineage 18.x and 19 that have android 11 and 12 in them. still have the same result of phone not able to be authenticated even after flashing verizon modem. ive even tried other gsi roms and ether ended in a bootloop or an error saying petition was too small. it seems that the apn for verizon becomes greyed out and changes the apn settings itself from the sim card. ive even tried using the latest stock update with the gsi and same results. (had to pay a site for the firmware since the newest update is exclusive?) at this point, ive decided using a gsi on this phone with verizon service a bust. so ive decided to stick with stock with root and magisk.

on a side note, i noticed the newer updates have provisioning apps installed on the stock firmware for carriers. not sure if that makes much of a difference but im done messing with it.
[Motorola Edge + (2020) Guides, News, & Discussion] ifritknight:
First of all thanks Knuxyl for your guide, it helped me to install a GSI ROM n my Edge+, I found really good images but in the end all the images I tried had the same issue... "bluetooth devices connects but transfer no audio", I dont think this is a ROM issue, because I tested 6 android 10 custom ROMS and 3 android 11 with the same result, so I wonder if you dont have this same issue or you manage to solve it.

Im using crdroid v313+211013 and BT wont connect to anything unless I disable A2DP hardware offload inside developer options, with this option enable, the phone pairs with devices but transfer no sound also most of audio codecs are not selctable, they are disabled (grau color), if I enable gabeldorsche stack, the phone is unable to pair with devices. Please if anyone have this issue or suggestion let me know. Have a great day.
[Motorola Edge + (2020) Guides, News, & Discussion] Disillusionedsal:
@Knuxyl - Thanks for putting this guide together.

@ifritknight - Indeed, I also couldn't get bluetooth to work. I got bootloop with Havoc and LOS 19. LOS 18 worked well.
[Motorola Edge + (2020) Guides, News, & Discussion] atarum0r0:
hi , thank you , there are upgrade?
[Motorola Edge + (2020) Guides, News, & Discussion] Knuxyl:
Well this platform isn't widely supported. I wrote the guide just to get us a foot in the door. The problems with VoLTE, sim, and Bluetooth are more than likely an improper implementation of the new oem partition stuff Google started enforcing, which started with Project Treble.

I did request the source for the kernel for global retail and verizon variants like a year ago. They finally released them within the past month on their github, so maybe a lineage developer could take a peek and possibly officially support this phone. This phone is too good to not support, but the display over usb c would take some effort.

Here are the links

Verizon

GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2

Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2

github.com

Retail

GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11

Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11

github.com