yashsingh1/xdaforums huggingface dataset:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] rddxda:
All good apart from camera. If I try to use the camera I get a message camera not supported.

Lineage 21 10 july 2024 Mind the gapps 14.

Moto G7 Play channel. Sorry camera now sorted, old icon removed and new one added
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kind of android newbie:
I currently have a Moto G7 River on the 7/6 Lineage OS 21 Nightly. I've tried downloading / using the built in updater to install the 7/14 Nightly. The installation completes fine, but when rebooting for the first time when prompted, the phone will just hang on a black screen -- it does not complete the boot process.

Force powering off / powering up the phone just brings the system back the the 7/6 build. Its unclear to me if this is an issue with the updater, or an issue with the 7/14 Nightly.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Mister-XY:
I have the same error here. I installed it twice and had the same error both times.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] mobmad:
Here as well.

No difference if I use the updater or download manually.

Tried to create a gitlab issue for this: https://gitlab.com/LineageOS/issues/android/-/issues/7416
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
Fixed in the builds that will post tomorrow for river and ocean, weds for channel
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Cronoss:
Haven't tried a LOS21 build in a long time.

Has the Discord , Whatsapp and Telegram voice notes issue been fixed?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
No
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Skippy12359:
If you're referring to VoIP bug where the microphone doesn't work on apps like google meet or telegram and others during video calls its still unresolved. That's what it says on the telegram site for G7p as of a few days ago. It affects LOS and other LOS based a14 ROM's as well.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
Whatever telegram site you refer to is unofficial and has no more idea than any other user.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ReyLoBacca:
21-20240716-NIGHTLY-river Device will now connect to Wifi. Thank you very much.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] makaholic:
I noticed after installing lineage-21.0-20240707-nightly-ocean through installer. The notification light will not work until I manually turn off/on under settings. Every time I power up the device I need to repeat this process in order to get the notification light working again.

I also installed the most recent build lineage-21.0-20240716-nightly-ocean and still getting the same issue.

Everything else is working fine, is anyone having the this issue?

Thanks
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
File a bug ticket with logs per the wiki.

I don't have ocean.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] MRC01:
Same here. The notification light does not work at all. No amount of turning it off, back on, rebooting, etc. makes it work.

Motorola G7 Power, Lineage OS, currently the build dated 20240716, but this issue has been happening long enough, it may have stopped working when I upgraded from 20 to 21.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] MRC01:
Today I installed the build dated 20240722 and the notification light is working for the first time in I don't remember how long. (y)
[Motorola Edge 20 Pro] npjohnson:
moto edge 20 pro

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the moto edge 20 pro .

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

pstar - Official builds​

pstar - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.​

Find any? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sm8250
[Motorola Edge 20 Pro] Maxi693:
Great job

Does magisk work on this rom?
[Motorola Edge 20 Pro] Maxi693:
Or is there the error like in lineage OS 20
[Motorola Edge 20 Pro] npjohnson:
Probably doesn't work, but try it.
[Motorola Edge 20 Pro] zpunout:
Thanks for making LOS21 for the pstar.

I've been trying to figure out why my particular device will not register with VoLTE on my carrier (as is my issue with official LOS20 as well. link) . In the attached logcat, I recorded about 10 seconds from just before disabling Aeroplane mode.

Of note is the stock firmware is retapac android 13

I don't know if I have some unusual variant of pstar if there is such a thing (bootloader reports as being XT2153-1 12GB RAM)

If I can find a SIM for a different carrier, I'll test the phone with that next. [edit:update: same result]

[edit2: I Managed to get VoLTE working by installing Magisk and using the Magisk module voenabler published by @edgd1er . Would it be possible to build the functionality of voenabler into LOS21 ? ]
[Motorola Edge 20 Pro] ShayNeeo:
I have problem with NFC function, when I want to enable it, the button flicker, please fix it. It will be a big help for me. (I'm using 01/14 version)
[Motorola Edge 20 Pro] mikib1:
Hi, I used LoS20 but last few updates crash with Magisk rooted boot (which you clearly mention it is not supported...), and now trying your build of LoS 21. But there is any advise from you how to get root access, please? Also safety net CTS problem occure.
[Motorola Edge 20 Pro] npjohnson:
Magisk should work fine now.
[Motorola Edge 20 Pro] mikib1:
I write here to not make confusion with OS builds. In LoS 21 (as you know) are the same problems. Do not answer, just keep in mind to fix this build before it gous officiall please. Phone can't be used to work, fortunatli I have second one with stock ROM... wich I do not like.
[Motorola Edge 20 Pro] zpunout:
The link to download the builds has been offline for a day. Just letting you know in case you're not aware of this.
[Motorola Edge 20 Pro] npjohnson:
I am, I had to clear the GitHub releases, and have been reuploading all 75~ build for the last 24 hours lololol. It is still running.View attachment 6059532
[Motorola Edge 20 Pro] zpunout:
I've been testing build 20240123. By default, VoLTE won't work on my particular carrier (Vodafone Australia - Felix MVNO). I can make it work however by editing the build.prop file by adding the following code:

# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1

# Data Options
persist.data.iwlan.enable=true
persist.data.iwlan=1
persist.data.iwlan.ipsec.ap=1

# Radio Options
persist.radio.volte.dan_support=true
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.radio.VT_ENABLE=1

# Other Options
persist.sys.cust.lte_config=true
persist.rcs.supported=1

I found the code from voenabler on GitHub

Is it appropriate to configure build.prop like this in your builds to just make VoLTE work with certain carriers? Or is it messy? Are you willing to add this?
[Motorola Edge 20 Pro] npjohnson:
Half of those properties do nothing

Narrow down which one enables it for you and I can probably add it.

My bet is these two

persist.dbg.ims_volte_enable=1

persist.dbg.volte_avail_ovr=1
[Motorola Edge 20 Pro] zpunout:
Adding just those two lines wasn't enough to get VoLTE calls to work. Do you have a suggestion of which other lines to add to minimally modify build.prop ?

Alternatively, I could start experimenting to see for myself after the weekend and let you know next week.
[Motorola Edge 20 Pro] npjohnson:
unsure, try and lmk
[Motorola Edge 20 Pro] mikib1:
Last reuploaded build from LoS 21-20240123 do not fixed known issues (bsod, freezes). During black screen phone it self looks like working normally for some time (just do not backinglight screen) it is rebooting when som process freezes and stuck with no response. Or just rebooting it self rundomly.
[Motorola Edge 20 Pro] zpunout:
Turns out your bet is correct. My attempt at testing only those two lines failed that day due to a mobile coverage outage early that Friday morning. What are the odds of that happening?

Anyway, after much testing, it turns out that just persist.dbg.volte_avail_ovr=1 is enough to be able to make calls on VoLTE.

I've confirmed it [edit: "it" meaning that by adding that one line in build.prop ] works after a clean flash of build 20240123

Could you please add this to build.prop ? [edit: also for LOS20 please ?]

On a side note, I discovered that after a factory reset, system/build.prop resets back to it's original state. I thought system remains the same after a factory reset? Not important, but could you please explain why that is so, just to satisfy my curiosity?
[Motorola Edge 20 Pro] mikib1:
Yeah... I did the same, complete wipe and clean install, now testing, hope that is it to fix all this issues. Will see. Thanks a lot for all of people involved of LoS21
[Motorola Edge 20 Pro] zpunout:
I seem to have fixed the black screen of death thing on my Moto Edge 20 Pro by reducing the maximum screen refresh rate to 90Hz in the display settings. (I fixed the same issue that way also on my Razer Phone 2)
[Motorola Edge 20 Pro] npjohnson:
merged on 20 and 21
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
F(x)tec Pro^1 X

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the F(x)tex Pro^1 X.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

pro1x - Official build​

pro1x - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.​

Find any? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​

Kernel Source: https://github.com/LineageOS/android_kernel_fxtec_sm6115
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vitu42:
After the upgrade from LOS20 to LOS21, I encountered the keyboard layout issue detailed here https://xdaforums.com/t/official-lineageos-20-for-pro1-x.4543997/post-88065145 from another user's LOS20 experience. It appears that the layout was defaulted to English(US).

Resolution:

Settings > System > Keyboard > Physical keyboard > Builtin Keyboard:

- Change layout to F(x)tec QWERTY (or one of the other F(x)tec options to match the physical keyboard on your device)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Yes, I think that the preference isn't persisting on upgrade for some reason, but it's an easy fix from the user side.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Solana Saga] npjohnson:
Solana Saga

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the Solana Saga.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

ingot - Official build - Maybe soon^TM​

ingot - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

AGPS is broken/touchy.​

SELinux is permissive.​

Find any? Report them according to this guide.​

Notes:

This is still pending fork to LineageOS organization.​

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​

Credits:

* mikeioannina

* npjohnson

Kernel Source: https://github.com/mikeNG/android_kernel_qcom_sm8450/tree/ingot
[Solana Saga] newuser11100:
Hi thank you for this rom of this rare phone I have the evaluation version with Android 12 and it is impossible to update to 13. Can I make this version that you post?
[Solana Saga] npjohnson:
What do you mean it's impossible to update to Android 13?
[Solana Saga] newuser11100:
Yes I have a phone version for evaluation released before the official release of the phone with Android 12 preinstalled and solana saga does not give me the possibility to update to 13
[Solana Saga] newuser11100:
View attachment 6057872
[Solana Saga] npjohnson:
You should be fine to flash this?

This will bring you to Android 13 firmware. You could also just flash the newest OTA zip first from Solana.
[Solana Saga] IronRoo:
Well this is a surprise! I was't expecting a custom ROM for this phone, especially from you! Awesome! Does the seed vault work with Lineage? Thanks again.
[Solana Saga] npjohnson:
I'm assuming you mean the crypto seed vault?

If so, haven't tried at all, that would be on you to try.
[Solana Saga] tlxxxsracer:
Is dapp store included or able to be installed?
[Solana Saga] npjohnson:
not sure what that is, if it's from stock, no it is not installed.

Is that the fdroid alternative? If so, you can probably just install it afterwards, idk.
[Solana Saga] tlxxxsracer:
No it's the web3 app store from Solana. It's in addition to play store
[Solana Saga] npjohnson:
install it and lmk if it works.
[Solana Saga] IronRoo:
the dApp store comes built in, I don't believe it's available from an official source eg Play store. I guess it may have to be "extracted" from stock, if possible, but it is essential for downloading the web 3 apps
[Solana Saga] npjohnson:
Yeah, you would have to extract and install it. I won't be including it.
[Solana Saga] Triskite:
the main purpose of this phone is 1. to act as a yubikey (hardware encrypted ed25519 private keystore) 2. provide an unrestricted app store natively, like fdroid, but with greater curation (performed by the solana mobile team).

many of the apps on the native (system app, you can't extract it easily) dapp store are custom made for the saga

just for context
[Solana Saga] npjohnson:
1. Yeah, on an unlocked bootloader I'm not sure you'd even want that to work. And it probably won't.

2. Again, from a licensing perspective, as well from a LineageOS UX perspective, I will not be including it. You can make a flashable zip for it if you want to utilize it, just like GApps have.
[Solana Saga] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Samsung Galaxy Tab E  Questions & Answers] tle2099:
i have an older Galaxy Tab E T377T that is stuck in the download mode.

when trying to flash it with the original firmware, i get

<ID:0/008> File analysis..

<ID:0/008> Total Binary size: 2498 M

<ID:0/008> SetupConnection..

<ID:0/008> Initialzation..

<ID:0/008> Get PIT for mapping..

<ID:0/008>

<ID:0/008> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

all posts point to opening the tar file and getting the pit file from it but there are only the 6 files in it.

boot.img

cache.img

modem.bin

recovery.img

sboot.bin

system.img

which file is the pit file?

please note it is an older firmware so it is only 1 file so there is no csc file. just the T377TUVU1BQI5_T377TTMB1BQI5_T377TUVU1BQI5_HOME.tar.md5
[Samsung Galaxy A54 5G] Earth-Chan:
Has anyone tried this module?

https://github.com/HuskyDG/magic_overlayfs.

It is a module to make system partitions become rw. But I don't know if it will work on this device specifically on Android 14

Since there is still no twrp on this phone, the operations are more complicated and for example if the module gave a bootloop, it could not be removed with twrp and you would have to flash everything back with odin.
[Samsung Galaxy A54 5G] khusika:
Hi @Earth-Chan

Welcome to XDA!

First of all, I don't use A54 or use Magisk on my device. But based on this issues, it seems like those module does not support partitions in Android 14.
[Poco F5 Pro / Redmi K60 (China)] Techguy777:
I don't own the device but you laid out a beautiful tutorial on rooting the Poco f5 pro. It doesn't seem like anyone can get viper4android working on the Poco f5 pro from what I have gathered online. Otherwise I would be hot to buy one. Usually a custom rom is easy to get viper4android working. The best way is to install James dsp, BusyBox, viper repackaged and audio modification library and set selinux to permissive.

I have ran permissive for 7 years and have never got malware on any of my devices. Everybody's so damn scared to turn on permissive drives me nots. They got to have the latest security patch which does absolutely nothing next month. They'll say oh that one was hacked.
[Poco F5 Pro / Redmi K60 (China)] bayad:
Thank you dev for this great tutorial.

Just one question : can I use Disable Force Encryption NEO file in any rom or is it specific to Pixel Experience Plus ?
[Poco F5 Pro / Redmi K60 (China)] NOSS8:
Missing important information for unlocking the bootloader:

Enable OEM unlocking and USB debugging.
[Poco F5 Pro / Redmi K60 (China)] urbanman2004:
If you notice, I mentioned "enabl[ing] USB debugging" twice in my guide:

And I never needed to "enable OEM unlocking" to unlock the bootloader so why would I need to include unnecessary instruction in the guide?
[Poco F5 Pro / Redmi K60 (China)] urbanman2004:
My use of Disable Force Encryption NEO is specific to this ROM. You would need to do your research to find out if it's compatible with another ROM. That's why I asked @flakeforever this question.
[Poco F5 Pro / Redmi K60 (China)] NOSS8:
2 times but not for unlocking

Xiaomi Community

new.c.mi.com
[Poco F5 Pro / Redmi K60 (China)] urbanman2004:
Did you actually read and follow the instructions in the guide or are you just making an impulsive response b/c it sounds like the latter. You must be trolling b/c the unlock method you're trying to impose has nothing to do w/ my guide. There's a saying that folks in the southern part of America go by which is: "there's more than one way to skin a cat." 🙄🤷🏽‍♂
[Poco F5 Pro / Redmi K60 (China)] NOSS8:
Well, the posted link is the official method from an official Xiaomi website.

Your tutorial is not false but incomplete, including for the installation of the Pixel Experience plus, as a recognized troll on XDA (Green Team), I must point this out to you.

Users didn't wait for your thread to unlock the bootloader and flash the ROM.

He who learns from his mistakes proves for himself that he is a wise man.

Cheers.🍻
[Poco F5 Pro / Redmi K60 (China)] urbanman2004:
If you feel that strongly a/b that so called "official" method then by all means, go make your own tutorial instead of spamming my thread as if you're some gatekeeper. I don't remember anybody asking for your useless input. By the way, how many tutorials have you posted on XDA? I'll wait...
[Poco F5 Pro / Redmi K60 (China)] bayad:
@NOSS8 is well known in the XDA community and is always available to help other members...
[Poco F5 Pro / Redmi K60 (China)] fadeko:
so i followed all these instructions but my camera wasn't working and i realized it was bc of the firmware part. Could you please link a guide on how to flash firmware
[Poco F5 Pro / Redmi K60 (China)] urbanman2004:
The default camera that comes included w/ the ROM (which was imported from MIUI) should actually work out of the box after successfully installing the ROM by following the instructions. The camera works on my device w/o issue so I would suggest researching your issue online.
[Poco F5 Pro / Redmi K60 (China)] bayad:
If you have K60, this is the recommended firmware :

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[Poco F5 Pro / Redmi K60 (China)] China_zz:
From my understanding, the k60 has an independent recovery partition and can be directly flashed to the recovery partition. Doesn’t the F5 pro have an independent recovery partition? Has the non-China version been specially processed?
[Poco F5 Pro / Redmi K60 (China)] fadeko:
okay thanks but what is this firmware thing is it like an operating system?
[Poco F5 Pro / Redmi K60 (China)] bayad:
I cannot explain it technically but you must flash it to fix camera issue in

PE rom...
[Poco F5 Pro / Redmi K60 (China)] fadeko:
okay thank you could you tell me how to do it tho
[Poco F5 Pro / Redmi K60 (China)] bayad:
Flash it by twrp and don't forget to tick option to reflash twrp after flashing firmware because firmware replace twrp by it's own default recovery...
[Poco F5 Pro / Redmi K60 (China)] djp2k18:
Unfortunately I won't be rooting my F5 Pro just yet as I just Google wallet on my phone & with all the issues trying to use it with Google banning/blocking fingerprints, I think I'll wait until a decent viable solution is released.
[Poco F5 Pro / Redmi K60 (China)] vinocastro:
Hello I desperately need help. I cannot boot into recovery after `fastboot flash recovery_ab twrp.img`. The `fastboot reboot recovery` command does not work. It just prints out all the fastboot commands. The `fastboot set_active a` and `fastboot set_active b` commands do not work as well.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
hmm weird, perhaps you should check your platform-tools?
[Poco F5 Pro / Redmi K60 (China)] vinocastro:
I just randomly left the phone idle and when I tried to power + volume up, it booted to recovery. I was able to flash PE plus now. I'm not yet done setting it up back to its original state as I am still busy at work.
[Poco F5 Pro / Redmi K60 (China)] vinocastro:
Hello @flakeforever , I am done setting up my phone back to its pre-soft-brick state. This new version is really smooth with the fingerprint.
[Poco F5 Pro / Redmi K60 (China)] canteo:
Hi, i don't know why i can 't add my account, i receive a message wich say to ask authorization at mi community, how can i do that? at the app i can see that i got it

d. Your Mi Account must be added to your Mi Settings

Sign into your Mi Account on the device.

Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.

Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.

Agree, then "Add account and device".

Edit: solved
[Poco F5 Pro / Redmi K60 (China)] nutcracker510:
How did you solve it?

I got the same issue

It asked me to apply in mi community for authorization
[Poco F5 Pro / Redmi K60 (China)] canteo:
I did another miui account and with that when opened the mi community there was a new option for request the unlock, so i tried again with my old account and the option was there, It IS strange but that option appeared with the new account...that was my problem i did not had the option at the beggining at the miui community apk
[Poco F5 Pro / Redmi K60 (China)] gt20v:
Is there any guide to do a dirty flash??

Flash rom>fw>dfe neo?

I dont need to care about the slot??thanks