yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] willxh:
Official build working ok, thanks! (JBL speaker still not working but that was expected. Issue I had where needed to hard boot after charging when powered off seems fixed. Still no outgoing audio on Google Meets call- hopefully a fix can be made for that...more common use case for these old devices than people doing actual cellular network calls.) Thanks again, hard to believe we are getting Android 14 updates on these old devices.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gunnerz:
@ npjohnson ive flashed your latest build and its working great. thanks, there is just this one issue. ive got a feeling its something to do with this ims thing. i am not receiving any text messages and I can't send any when LTE is enabled, further more calls are coming up on screen as unknown and callers get disconnected on the other side after a few rings of they ring me. as soon as i change it to gsm/wcdma, i can send and receive messages as normal and calls are getting through to me with caller id as normal. its a weird one and i can leave it on gsm/wcdma when wifi is around but when out and about need lte. hopefully you will find a solution soon. cheers buddy

UPDATE - ROM works 100%, my issue all along was my network provider, tried a different provider and the error is gone.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Sunport:
I guess I'll wait for the next build with hot fixes and test it

ps: thank you for your work and time!🍻
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Sunport:
Just install today's build (07.10) and working like a charm.

LTE calls and received, sms send and revived, interface working fast and smooth!

Last security update and other many fresh fixes, respect and thanks for your hard working.

Want to send you some coins for beer, where?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] RobinKemen:
@npjohnson

First of all:

I am amazed, that you people managed bring back OTAs for this old phone. Seriously, great work!

But I was wondering:

Are the problems with LTE that gunnerz described related to the IMS issue, or where they more likely a random quirk?

Right now I am holding off on installing the latest OTAs, because I need my phone to be reliable and don't have the time to manually downgrade, if the latest updates mess with my cellular connection.

Greetings from Germany.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
It's ims. Most likely that he needs to disable RCS messaging.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] RobinKemen:
Okay, but if I didn't experience any of those issues so far, I shouldn't encounter them, if I update to the newest build, right?

Sorry for those basic questions, but I really don't know **** about how phones work, if that wasn't obvious by now.

From what I could grasp of the discussions on Discord, IMS has been broken/quirky for some time now, but like... not for everyone and not always? If so, I'm probably gonna try it and hope for the best.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Sunport:
As I know very varitable - depends what carrier and what county. You use VoLTE and VoWiFi now/before?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] RobinKemen:
I gave it a try today and don't have any issues thus far.

I'm pretty sure I have been using VolTE an VoWiFi before and did not have any problems, neither here in Germany, nor while travelling through Italy/Austria/Switzerland.

The only quirk I encountered last year was that every time I restarted my phone, I could not establish mobile Internet connection, until I connectected to WiFi for just a second.

It was almost like the phone needed to download some configuration first.

But anyways, this quirk has either been patched or sorted itself out a while ago.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gunnerz:
Update : The issue I was having had nothing to do with the ROM, infact it was my network. Testing the phone with a different sim has proved that the ROM works fine! I will be changing my network provider.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Grigori88:
XT1789-04

If there is information "Your device does not qualify for bootloader unlocking." on the website https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-b, I won't be able to install a custom ROM?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gunnerz:
ROM works fine. My issue was the network provider. A simple test of using a different network has helped me establish that.

Correct , bootloader can't be unlocked!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] willxh:
Assume the nash outgoing audio issue is same as this bug created for river device: https://gitlab.com/LineageOS/issues/android/-/issues/6895
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Sunport:
probably yes, as you see many devices affected, but no solution yet, I try vendor.audio.feature.dynamic_ecns.enable true but not successful 😕
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] RobinKemen:
That's cool.

I can also report, that everything is working perfectly.

It's so nice that official OTAs are back and working.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] RobinKemen:
@npjohnson

Man, this device must be hell to maintain, with all the mods!

I just ran into a minor bug with while using the Moto Power Pack Mod.

The Moto Mods Manager app notification is no longer showing the detailed status of the mod. It is not showing the remaining capacity of the mod, nor is it showing when the mod itself is being charged.

Also the battery symbol in the modification bar is no longer indicating, when the internal battery is being charged by the mod. The Mod still works fine. I am not sure, if this broke after the last update or the one before that, but it has got to be one of them.

Edit:

The mod also charges the internal battery regardless of the setting (On/Off/efficiency/normal). I will check if the mod battery still charges normally later.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] alikila:
I got the "download verification failed" error when updated the phone.

Tried many times but got the error again.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
as I said long ago in this very thread, you need to do this once to get onto the July builds which are signed with a new key.
[Touch Viva, MDA Basic ROM Development] xiaomouse:
hello, i just bought a htc viva

i only can change the theme but the skin of manila still same (brown colour)

anyone can teach me that how to change the skin?
[Touch Viva, MDA Basic ROM Development] marSoul:
http://xdaforums.com/showthread.php?t=427392
[Touch Viva, MDA Basic ROM Development] tropical cactus:
Open colour scheme folder on main computer. Choose either red or green folder. Open and move dat files to your device program files: spb mobile shell directory. soft reset and colour will change. Took me a while to figure it out, but working now.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Razer Phone

- 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 Razer Phone.

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.

cheryl - Official builds​

cheryl - 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:

Known bugs (won't fix):

- Can't switch FPS to 60 (can only switch between 90 and 120)

- Can't switch screen resolution (defaults to 2560x1440)

Find any more? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps. - GApps are included in my unofficial builds​

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_razer_msm8998
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] kh.v:
Hi man,

i do have difficulty in flashing boot img in the razer phone 1, hope you can help

Hi i'm new in this Razer phone 1,

Currently, it run android 9.0.1, global. I tried to unlock bootloader and it seem unlocked (unlock bl + critical)

However, i have a intruction of changing slot boot. However, the command on cmd, seem not working well. It showed "Too many link". Also it seem not working with flashing boot or twrp

Any clear help, much appriciate! or you can DM me your chating platform that i can give you the access to my pc and razer phone 1 to hlep me flashing and setup LineageOS

Again, thanks for any helps
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Stop doing everything you're doing and just follow the instructions written out on the wiki, they're well tested and work fine.

You have some combination of outdated fast boot and broken drivers.

If you just follow the installation guide you'll do fine.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] kh.v:
for the wiki said : fastboot oem unlock

i got error with this command , it gives command error

but on the last time i tried, i do the unlock bootloader on the fastboot menu selection to unlock . Then it can unlock, however, it still got stuck in flashing boot img.

That why i have struggle :(
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Yeah the wiki said to do that long after it talks about how to install drivers and fastboot, something is wrong there, go back and follow that part again
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] kh.v:
Thx so much for the rom. Finally i can make the rom working on my razer phone 1

I switch to MAC to have the adb driver working for flashing files !!!

Again, thanks so much for the ROM, and hope can get the OFFICIAL ROM soon :)
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Thanks for updating the rom again! Ur a legend
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
just wanted to let you know while using mobile data, it still appears off even while on. So in the status bar and quick setting menu for the mobile data constantly has a ' ! '
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
We're working on it.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Deleted member 11329269:
After restarting the phone, the time is always reset. Surfboard doesn't work, but v2rayNG works fine. Douyin (the Chinese version of Tik Tok) has the floating window permission turned on but the floating window does not work.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Deleted member 11329269:
There is a problem with screen-recorded video playback, and the screen will freeze.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Cellular ! fixed, builds will roll within a week officially!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] unsponsoredgeek:
This is cool. I just updated my RP2 today.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Nice.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Sick, just waiting for official build to be put out an then I'll update it, I was having some trouble with using root on unofficial lineage 21
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 晚..:
When my phone reboots the time returns to build time.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Is it just me or there is no download for 21(official build) anymore, I sware it was there a few days ago. Or am I tripping?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Build was pulled due to an issue with AOD. New one in a few days.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Since Los 21 came out iv been having problems connecting my watch to my phone, I thought the 2 new updates might fix it but didn't help. This an issue for anyone else?

Should I try to reflash the ROM or is this a know issue?

worked totally fine in Los 20
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Sadly, this device utilizes android.hardware.radio@1.3 (or below).

This means that the March security bulletin - known as QPR2 - fully killed this device.

We (LineageOS) are trying to write a wrapper to make older radio HAL versions compatible with newer radio HAL versions.

With that said, we may or may not be successful and we're entirely unsure how long it would take.

So, sadly, for now, this device has 21 builds disabled - I have deployed one final February ASB unofficial build people can use in the intermediary (or you can use the final official build).

I will announce here if/when the device is re-added to the roster.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
is it possible to get older lineageOs image? i want to downgrade to LOS 20, cuz somethings are not working as it is intended because of root. Iv been looking around and can only find LOS 21.

Ty and hope everything works out!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
not sure how lineageos 20 will help you, but google timschumi lineageos archive.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Iv reset / reflashed lineageos 21 like 3 times trying to connect my watch with my phone but hasn't worked, even with older lineageos 21 versions. But in lineageos 20, it works completely fine.

And thanks for the archive I got it downgraded to lineageos 20 and working 😀
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
The radio issue has been fixed and official builds will roll again in the next week
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] unsponsoredgeek:
Yes...HaHaHa...YES!

N.B. I did change my RP1 to e/OS but will keep an eye on this one, too.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Yeah Baby! That’s what I’ve been waiting for !!!,​

ill try out 21 again but im not sure if the annoying watch linking issue would also be fixed
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
It is fixed.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] SonyGG:
I have installed Official builds but nfc and BT are not working
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
same here, i first tried to upgrade from official 20 to 21 but that kept crashing and taking me to bootloader, after i wiped and installed just lineage os 21, the Bluetooth crashes frame one of setup, and nfc does not work(checked a nfc checker app and the app says "not supported")
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
anyone test the new build that came out may 28? i dont wanna upgrade if it still got bugs cuz this my daily driver xD
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
It still has the same issues as the last build.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
I was going through some old reports, I came across this one titled "Unlock screen does not work anymore via fingerprint" by @itsmeans18. I think I noticed this as well but this for me happens when I installed your unofficial version of lineageOs not the official, just thought I would throw this out there
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
The unofficial hasn't had the patch deployed yet.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Wait, wrong device, no clue what you're talking about.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
yea this is like awhile back, i noticed this in LineageOs 19 or 20 a while back
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
any fixes in the june 4 update regarding the bluetooth and nfc
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
I can't recreate this - it works fine for me on June 4.

No one can get me BT logs.

My phone pairs to Cheryl and my headphones pair and work.

NFC is a WIP.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 9903286:
I also have the issue with bluetooth not working. Which logs do you need?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Follow the wiki guide to report a bug. It details it.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 9903286:
There's already an issue for this opened with the required logcat log though, here: https://gitlab.com/LineageOS/issues/android/-/issues/7183

From what i can see the provided logcat does show problems with the bluetooth at around line 22395 and i'm fairly certain my logcat would not provide any data not already in this one, so i assume i shouldn't post another issue?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
fixed in todays build
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 9903286:
Confirmed, bluetooth and NFC both now working! Thank you very much!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
lets goo i can now upgrade to lineage os 21!!! TY for fixing, and still supporting this old device 😂
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] csharpfaze:
Confirmed for the official build?

I still have the same error even with lineage-21.0-20240618-nightly-cheryl-signed.zip.

https://wiki.oddsolutions.us/devices/cheryl/ just gives me a 502 :/
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 9903286:
Yeah, I'm on 21-20240618-NIGHTLY-cheryl and they're both working for me as of this update.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] csharpfaze:
Thanks, its working now for me too. 👍

I disabled wifi and restarted (again), after giving the phone the time to boot up completely, I finally could use bluetooth again.

(maybe the setting was relevant, maybe there's still a timing issue, idk 🙈 )
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
unofficial server is fixed as well, upgraded to 24.04, it broke things lol
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
Is the unofficial not updated? It shows 2024-05-08 as latest in unofficial while it's 2024-06-18 for the official.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
June builds will come soon.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
for unofficial, there is also "vendor.img", what would that be used for? i dont see anything referring to it in the installation instructions
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] npjohnson:
Its for people who need it. (Aka messed up their system)

You don't.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
I'm still having this annoying issue with my smartwatch app where it attempts to connect with my watch but fails and after 2 trys it says "Bluetooth has stopped working" (something like this not exact), it can't be the app cuz it works fine with lineage is 20, just lineage is 21 is causing this problem for some reason. I'll try to look more into it tomorrow if I can't then I'll try to provide logs. I guess for now I'll stick with lineage os 20 ;(
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] TenseRaptor:
i cant figure out what the problem could be, after i authorize my watch to pair i think bluetooth just carshes, i see in the quick settings that BT just turns off and comes back on after a few seconds
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 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!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] flopticalcube:
Thank you for your unofficial build, npjohnson. My Cheryl lives again as I lost mobile data last month when my provider dropped support for Pie. Adaptive backlight is still broken (never worked in stock Pie). I'll have to look into rooting to get Wallet back but that was always flakey anyhow.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] flopticalcube:
Notifications don't appear to be respecting the volume setting. Only in Do Not Disturb are you able to make them quiet.

EDIT: Sorry, it is not that notifications are ignored but that volume is still present even when levels are set to zero.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] flopticalcube:
Just FYI, with the July 18th build, Magisk 27.0 and Play Integrity Fix 16.7 pass both Device and Basic integrity, allowing Google Wallet to work for payments again.
[Google TV General] shi1as:
Hello and thank you for your work :)

I'm trying to run this build on ODROID C4 unsuccessfully. I have successfully flashed aml_install_package.img and booted into recovery. Then successfully sideloaded the image of your build without errors, but if i try to reboot, it boots to recovery again (Bootloop to recovery). I haven't loaded any extra addons, just your build.

What I can check to help me debug this problem?
[Google TV General] AusX10:
Tested Banana Pi M5, USB is still broken.

I was able to pair the Google TV app though. It works to adjust volume and turn off the TV but can't get past the remote pairing animation. Pressing 🔙 resets the animation but won't clear it.

Otherwise seems to work fine.
[Google TV General] npjohnson:
We have a proper way to disable the pairing animation now. Going to do it for devkits.
[Google TV General] BTK19:
Hdmi cec is still broken on Wade and Dopiner
[Google TV General] npjohnson:
We are working on it. Just hard to test all cases.
[Google TV General] hp420:
I think I bricked my dopinder. I flashed lineage 21 recovery, tried to boot into it, and I'm hung on an ONN boot screen with no ABD or fastboot connections.
[Google TV General] npjohnson:
just reboot and hold the button, you're back in update mode and can flash whatever via amlogic's update tool.

Almost impossible to brick.
[Google TV General] shi1as:
Does anyone know how to run it on odroid c4? Still in a bootloop to recovery.
[Google TV General] hp420:
lol well somehow I did. sucker won't even power on anymore. I have no idea how I managed that, but When I held down the button and plugged it in it flashed, turned off, and shat the bed. Been modding androids, game consoles, etc. for 20 years now and I've never hard bricked anything until now. At least it was a super cheap one and I already replaced it with the 2023 model.
[Google TV General] npjohnson:
I forget what device you were on but if this is dopinder, we have seen a bunch of people who just had spontaneous blue smoke right out and it died lol

And those people were just on stock
[Google TV General] hp420:
Whoa, yeah I was. Glad it just shut off then. Couldn't have gotten any luckier I guess. I gave it a sniff test right away and no weird smells. Not sure what happened there.
[Google TV General] npjohnson:
Oh, blue smoke is a colloquialism for spontaneous hardware death, doesn't actually mean blue smoke shot out.
[Google TV General] hp420:
Ah ok gotcha. I actually just popped the board out because I was wondering and everything looks pristine. No dead chips, fried leads or anything. I wonder if the failures are why they released the hardware revision.

Guess I'll have to find a new flashable ATV to play with.
[Google TV General] Functioner:
Did you install v21 to the m5 as a fresh install starting by flashing the amlogic format image aml_install_package.img, and then booting that to LineageOS recovery and sideloading the v21 .zip? If not, how did you install v21? Did you use any of the workarounds discussed in the v20 thread?
[Google TV General] AusX10:
Just by flashing the aml_upgrade_package. I never got the aml cli stuff working to fix usb.
[Google TV General] Functioner:
To your m5 device that had 20 already installed?
[Google TV General] AusX10:
Yep
[Google TV General] npjohnson:
Awesome update:

Changes are all merged up, and after tonights builds (I requested m5/radxa0/odroidc4{,_tab}) be rebuilt tonight) and the wiki instruction updates, all should be perfect.

All the issue are ironed out.