yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] defcondoc:
I'm very sorry to hear this happened to you. I have some experience with this. Most likely, you will need to hire an attorney who specializes in this to get your money back. If you haven't talked to NFCU corporate in VA. I would also recommend doing so. Keep logs of everything you do. Record pertinent conversations.

Best of luck you to you!
[General Questions and Answers] bdh1975:
Thank you very much for the reply! I planned to assemble my appeal and fire it off via the regular channels plus as you suggested send a copy of everything to NFCU corporate.

Have a great week!
[Google Pixel 7 Pro] S74V3N:
​

What can I Try to do?

I buy my Display on Ifixit.

My old fingerprint sensor is broken! So i have New Display with a New fingerprint sensor and the Fingerprint sensor needs calibration but Google repair software says my software version is newer than the repair tool.

some suggestions?

Unable to inspect

Your phone's current software version:TQ1A.230205.002 is newer than this repair tool has.

this shows up with

Google Pixel Update and Software​
[Google Pixel 7 Pro] schmeggy929:
So you bought a display to replace the broken one. First step would be to actually disassemble the phone, remove the display and install new one.

Fingerprint sensor is KO'd. How do you know it is a hardware instead of a software problem.

You need to add a few more details on what you trying to do?

What does using the repair tool have to do with replacing the screen.
[Google Pixel 7 Pro] S74V3N:
FIXED

Fingerprint sensor is working

used this link https://pixelrepair.withgoogle.com/udfps

used FASTBOOT mode not Rescue mode. And all works now :)

​
[Google Pixel 7 Pro] Sweeet1102:
I have the same issue, but can't really boot in FastBoot..

Rescue, Recovery, Barcode...
[Google Pixel 7 Pro] Hoetd:
You're not supposed to pick any of those. You are already in fastboot. Don't do anything except follow the given directions in your browser.
[Google Pixel 7 Pro] Sweeet1102:
Yeah it work that way 👍
[Google Pixel 7 Pro] Samuel Holland:
Would you mind me asking do you need to be all stock no root?
[Google Pixel 7 Pro] ysoof:
Pixel 7 fixed

make sure :

1. developer mode is on (not sure but I did it)

2. install the usb drive for debugging so it gets recognized in flash mode (Get the Google USB Driver)

Get the Google USB Driver | Android Studio | Android Developers

The Google USB Driver is required to perform adb debugging on Windows with Google devices.

developer.android.com

follow the steps in the link

Its the first page no need to go to rescue mode or recovery mode, (fastboot from recovery mode will not work)
[Google Pixel 7 Pro] Fracture7953:
Do you mind sharing your software version? Not sure if it will help at this point since I'm sure you've updated, but I'm wondering if rolling back my software to a previous version will get rid of my "Your phone's current software version:UQ1A.231205.015 is newer than this repair tool has." error
[Google Pixel 7 Pro] pixelguyfromca:
I had a lot of trouble getting this to work, these steps solved it for me. I had trouble with the udfps site, it was rejecting me because my phone OS was not supported because it was too new. after many attempts if finally worked.

thanks to everyone sharing here, it was a big help.

enabled usb debugging on the phone

Get your best usb c to usb c cable (I think this was a big part of my problem, I tried 3 or 4 cable options and ended up with it working while using my $79 quest 2 link cable.)

boot into fast boot, power + vol down. Do not go into rescue mode.

installed the google driver while connected in fast boot

went to https://pixelrepair.withgoogle.com/carrier_selection, scrolled down to the link to "Install fingerprint calibration software" (https://pixelrepair.withgoogle.com/udfps)

connecting the phone while in fast boot (Not rescue like it says on the repair wizard)

deploy the software

REBOOT

setup fingerprint

enjoy success
[Google Pixel 7 Pro] pennystrike:
Now This is what I call a true step by step success guide. thanks a bunch!
[Google Pixel 7 Pro] alexandruvlad:
Had my screen replaced, my fingerprint isn't working (not showing up at all in the options)

I can't seem to use the tool on https://pixelrepair.withgoogle.com/udfps

Getting the common errors everyone seems to be getting (used only the original USB-C to USB-C , not others)

Could the beta Android version cause the errors in the tool? Should i reset to factory / reinstall the latest Android version manually (not a beta version this time around!)

Thank you for your inputs
[Google Pixel 7 Pro] coolsid8:
Your Display isn't genuine most likely. Had the same experience with a third party vendor. Had to change the display again.
[Google Pixel 7 Pro] alexandruvlad:
I've thought of that, to be honest, but it looks gorgeous (as i remember it) and works on 120Hz as well without any hiccups. How can i tell for sure it ain't genuine?

Any chance it could be something else?
[Google Pixel 7 Pro] coolsid8:
Hey I thought the same as well. I think they dont do cheap copies anymore or atleast the panels are the same but the surrounding parts arent. The pixel service centre guy told me that they were almost 95% similar but they were subtle differences.

Also, I think in most cases as some of these displays work automatically with the original fingerprint sensor from your broken display. But I dont think there is anything anyone can do here.
[Google Pixel 7 Pro] SchmidtK:
Great, thank you very, very much - Worked like a charm with my Pixel 7 after getting a new display including fingerprintsensor.

Addition to the description: @pixelguyfromca already wrote it in upper cased letters, but I want to repeat it here: REBOOT after the phone booted the first time after successfully deploying the software (The first time after deploying the software I still got the error, but after rebooting it was gone).

Thank you (y)
[Zenfone 5 Q&A, Help & Troubleshooting] Llorenzaccio:
My Asus Zenfone 5 is beginning to have some malfunctions :

No more sound, which means :

I can't make calls (the phone freezes to black and I can only start it up again by holding the power button)

I can't receive calls (callers go directly to voicemail)

I can't open the camera to take pictures or videos

Alarms don't ring, they just vibrate

I can't listen to music

I can't watch videos (videos taken with my phone, on youtube, on any social media app...) : video just won't start.

I got this bug report from NewPipe, a youtube client :

Exception​

User Action: play stream

Request: Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing

Content Country: GB

Content Language: en-

App Language: fr_FR

Service: YouTube

Version: 0.25.0

OS: Linux Android 9 - 28

Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100]), format_supported=YES

at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:198)

at android.os.HandlerThread.run(HandlerThread.java:65)

Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)

at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2110)

at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1070)

at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1049)

at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:846)

at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)

at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:703)

at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1894)

at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:792)

at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)

at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)

... 3 more

Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)

... 13 more

I don't know if it's related, but I've also noticed that in the play store, when I check the the compatibility of any app with my device, it is identified as Asus UNKNOWN_PRJ_ID, instead of X00QD.

I don't know how to proceed from there, is my phone fixable ?

The last time it happened, I was able to fix the issue by shutting down and restarting the phone a dozen times, but this time it's not working.
[Zenfone 5 Q&A, Help & Troubleshooting] defcondoc:
Stating the obvious, it could be hardware related. Has the phone been dropped ever or been contact by liquid, water, etc?

Are you running stock ASUS ROM?

You could back up and try factory reset.
[General Questions and Answers] Llorenzaccio:
My Asus Zenfone 5 is beginning to have some malfunctions :

No more sound, which means :

I can't make calls (the phone freezes to black and I can only start it up again by holding the power button)

I can't receive calls (callers go directly to voicemail)

I can't open the camera to take pictures or videos

Alarms don't ring, they just vibrate

I can't listen to music

I can't watch videos (videos taken with my phone, on youtube, on any social media app...) : video just won't start.

I got this bug report from NewPipe, a youtube client :

Exception​

User Action: play stream

Request: Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing

Content Country: GB

Content Language: en-

App Language: fr_FR

Service: YouTube

Version: 0.25.0

OS: Linux Android 9 - 28

Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100]), format_supported=YES

at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:198)

at android.os.HandlerThread.run(HandlerThread.java:65)

Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)

at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2110)

at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1070)

at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1049)

at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:846)

at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)

at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:703)

at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1894)

at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:792)

at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)

at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)

... 3 more

Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)

... 13 more

I don't know if it's related, but I've also noticed that in the play store, when I check the the compatibility of any app with my device, it is identified as Asus UNKNOWN_PRJ_ID, instead of X00QD.

I don't know how to proceed from there, is my phone fixable ?

The last time it happened, I was able to fix the issue by shutting down and restarting the phone a dozen times, but this time it's not working.
[General Questions and Answers] defcondoc:
Could be hardware related. Has the phone been dropped ever or been contact by liquid, water, etc?

Are you running stock ASUS ROM?

You could back up and try factory reset.
[General Questions and Answers] Llorenzaccio:
Yes, I am running stock Asus ROM, the phone is not rooted, it has taken some hits over the years, but it's always been in a protective case and screen protector. Also the last time it happened was some time ago, so the causation is not obvious.

I will try the factory reset
[General Questions and Answers] defcondoc:
Ahh ok. Yes, please try a factory reset. Let me know if that fixes. Thank you.
[General Questions and Answers] Llorenzaccio:
Well it didn't work, I still have no sound. And the accelerometer is gone too...

I think it's time to look for a new phone
[General Questions and Answers] defcondoc:
That's unfortunate. As I expected it might be hardware related. At least it lasted a good 4 years or so...
[General Topics] muffinman123987:
sry i dont know where to put this and since you guys here are like beasts with phones i was wondering if you could help me out.

My friend wants to buy my dads old blackberry 8820 since my dad got the new bold now. Thing is the 8820 won't turn on. The only thing that ever happens is the little red light in the top right will sometimes blink on.

Can someone here help me turn it on?
[General Topics] TheChampJT:
Did you ask your father what he did to it?
[General Topics] muffinman123987:
he aint here. he's in some other country right now for work.
[Realme GT 2] Luigi2201:
Hi anyone have found how to unlock the rmx331, idk maybe changing to the indian version, trying to modify the "deep test" app?
[Realme GT 2] lucy1983:
Changing to the Indian version (RMX3312) is very easy. The problem is that, by doing that, you lose your IMEI numbers and Baseband. And the deep test APK made for RMX3312, the only one who's bootloader can be unlocked, doesn't work since there is no valid IMEI and Baseband.
[Samsung Galaxy Watch 5] Locoman_:
The last one I tried left a small border on the outside of the circle.
[Android Head-Units] Burak71:
I can't do the agama car Launcher home screen, it returns to its old state when it presses back, is there anyone who will help me, I'm bored, there is no one who understands this business i
[Android Head-Units] Burak71:
Up
[Xiaomi Redmi Note 4 Questions & Answers] zagzaggr:
I installed Lineageos 20 on my device, and I keep hearing my own voice and other mic sounds through my headset, both in calls and after calls while the headset is connected. Other people say they hear echoes of their own voice. I don't know if the two are related.

Additionally, after a messenger call, both headset and builtin microphones sometimes stop working everywhere, but come back after another call, I can't seem to find a more exact pattern to replicate this.

I tried so far installing a microphone-fix magisk module, but I think it was only for microphone volume, and also editing build.prop to include :

ro.vendor.audio.sdk.fluencetype=fluence
persist.vendor.audio.fluence.speaker=true
persist.vendor.audio.fluence.voicecall=true
persist.vendor.audio.fluence.voicerec=true

though I'm not sure if these are the correct lines, I've found conflicting information about fluencetype on build.prop, or even if it's relevant at all...

Any information that could help to fix the issues?
[General Topics] TVDinner:
Is there some general T9 help sections.

Also, I would like to add something to the dictionary of things to do like when I type "i" on the keyboard (I have a htc Fuze) it automatically changes to "I".

Any T9 help would be greatly appreciated. Thanks!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
LG V20

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

Introduction:

This is the Official Lineage OS 19.1 thread for the LG V20.

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.

Official Builds:

h910

h918

h990

ls997

us996

us996d

vs995

Unofficial - built once a month by me, includes GApps and Pixel goodies:

h910

h918

h990

ls997

us996

us996d

vs995

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

Known Bugs:

IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.

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.

This uses a port of Linux kernel version 4.4.

Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Builds will roll within a week!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] itt533:
as this is based on android 12, and this device is about 6 years old, isn't it slow?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Runs fine enough here - no worse than A11.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ROMSG:
better than 11 in my experience
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] loyukfai:
Have anyoned tried dirty flashing from LOS18?

Cheers.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ROMSG:
Builds aren't out yet
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] d2xTaimen:
Thanks for bringing 12 to the v20! Not complaining or arguing at all but why didn't you just skip 12 and move to 13 all together?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
I planned to but Bluetooth is horridly broken on 13 for one reason or another - figured I wouldn't hold release back for it.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] dextructor:
I'm new to the V20 and picked my used device last Thursday (990DS variant), already unlocked thanks to this forum and played with some ROM's and Kernels for a while.

I already downloaded and flashed the unofficial version and I really don't like the design language/choices that Google made, but it's working very well. The only thing that's not working (and I didn't notice on other ROM's) it's the FM Radio (I don't use, but tested with the stock before unlocking).

Since I try not using the physical buttons unless it's really necessary I use in Lineage 18 the volume panel to change it (the same panel it's not available in this release), and Simple Reboot for other tasks that requires the power button menu. But I discovered that the double tap to wake don't work after 5 seconds when you lock your device (If you try to use between 1 and 3 seconds it works), but after that you need to use the power button or the fingerprint. But If I wanna check notifications or the time without unlocking my device DT2W it's useful.

I personally use LineageOS for microG and when it's available there (or even a regular Lineage without gapps for testing) I will use this V20 as a daily driver since my OnePlus3 it's out of service because of my mistake with the LCD.

My sincere congratulations for the 4.4 Kernel porting, it's really impressive the work of the community here.

Off-topic: Since my last device was an OP3 I was really used to off screen gestures (flashlight, music playback etc). There's something similar that could be used in this device? Thanks!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] 0ldsoul:
Hi, thanks for your hard work OP and everyone who contributed to keep this old device of ours running up to date. We really appreciate it! It's my first time flashing a custom rom since the phone was released. Phone broke on me after a year of using (stock no root, ig something inside got damaged because of excessive heat) and on it's fourth year of hibernating I picked it up again and it miraculously somehow fixed itself. I'm in LOS 18.1 right now and so far IR isn't working. Where can I download the 19.1 and I see it's not in known bugs anymore, does IR work?

BTW, is it really not possible to use twrp instead of lineage recovery? Does migrate work on lineage recovery?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] 0ldsoul:
It's impossible to bake this in custom rom. Your best bet is to use apps that remap the button. There's plenty in play store.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
You can use another recovery if you really want to, although los recovery streamlines everything. And i believe the ota updates may rely on having los recovery, npj will need to comment on that.

Overall, no, you don't NEED to use los recovery, but i'd recomend using it.

Also, no, ir still does not work.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Lineage Recovery is needed for OTA yes.

And, really? IR is still broken?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Yes, it still is broken on 4.4 unfortunately (and there's no sign of what the issue could be since 3.18), although we intend to patch it up once we're done with USB as a whole.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] 0ldsoul:
I see. I don't really use OTA. I always manually update roms thru recovery.

I guess the only way to get LOS 19.1 is thru OTA? I went to LOS website and there's only 18.1 available.

If 19.1 becomes available and I'm in 18.1 rn do I have to factory reset first before flashing 19.1?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
Just follow the wiki guide, everything will work fineJust follow the wiki guide, everything will work fine
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
('h830', 'Wednesday, 2023-03-29')

('h850', 'Sunday, 2023-04-02')

('h910', 'Thursday, 2023-03-30')

('h918', 'Thursday, 2023-03-30')

('h990', 'Sunday, 2023-04-02')

('ls997', 'Sunday, 2023-04-02')

('rs988', 'Sunday, 2023-04-02')

('us996', 'Thursday, 2023-03-30')

('vs995', 'Tuesday, 2023-03-28')

Here is the build schedule for 19.1
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] 0ldsoul:
Sorry if this is not allowed here. I just want to ask my v20 is still suffering from thermal throttling. Is my phone bad or does v20 really act like this? I'm in Los 18.1. I only do browsing and watching videos. I know this phone broke on me before due to excessive heating it even reached 50°C+. Currently the highest I had is 47.2°C while using. Are there any mods for Android 11? I saw one for Nougat. I don't think it will work on newer versions.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] d2xTaimen:
I don't have much to say for you software wise but you can try to replace the thermal pads and see if it yields better results for you.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ROMSG:
Only use the included kernel, 3.18 based kernels will NOT work in any way. As for the heating issues, you likely need to replace the thermal paste inside the phone. Could you grab a logcat to help diagnos BT?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] shahroooz.n:
Thanks for your quick reply 🙏

I not sure which kernel i use right now. The last one i flash after using dirtysanta and...

Is 3.18 or 3.20

And after that i just flash rom with lineage os recovery without rooting.

Sorry if i'm not understanding some of your advance guidance 🙏

I see a video for changing thermal paste and i'm looking for doing this after i buy thermal paste.

I search developer menu for grabing log for bluetooth but nothing found yet!!!

I searched it and i find bluetooth hci snoop log and save logs off bluetooth and then create a system bug report with adb and extract it with adb to use it in Wireshark.

If i say it right.

Please tell me to do this
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] npjohnson:
When you flashed lineage you flashed our kernel - stop using custom kernels - they won't work with this ROM as this ROM requires 4.4.