yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Techguy777:
Congrats to whoever started this project. Yes jamesdsp will cause it to fail. Im on tab s8 plus samsung One UI 5 and its working.Im just missing 2 options I use the playback gain control and headphone surround sound. Im super pumped to see viper4android working at all in 64bit devices.

I don't know how hard its been but I think I speak for everyone when I say awesome job!

do you guys plan on getting all the features to work eventually?
[Google Pixel 7 Pro] Draco1876:
Lets goooo! Thank you so much, ill try it out later. Really appreciate your hard work regardless.

Edit: It works great! Make sure to also remove audio modification library and audio complatability patch along with JamesDSP. I do not know if you need to remove both but I did that and it works just fine after. Hope headphone surround gets added soon. Great work!
[Google Pixel 7 Pro] schmeggy929:
I think some of you are yanking our chain. I have been trying for 2 days to get this work on my Pixel 7 Pro. No audio mods installed, tried 3 different music players and still driver is unknown, Enabled NO, Audio format Unsupported, Processing NO with obviously no sample rate. lol

EDIT: Don't mind me, only took me 2 days to realize I had LDAC selected in bluetooth.
[Google Pixel 7 Pro] Namorbrowneyes:
Is Bluetooth effects working for anyone ? Mine got all raspy and bad when connected to my car and playing music.
[Google Pixel 7 Pro] Nick_Gl:
Second this. I gave up on v4a years ago after I found this. Simple/effective. Works with android auto too.
[Google Pixel 7 Pro] Lughnasadh:
FYI: AML was just updated to v. 4.2 and now supports V4A RE.
[Google Pixel 7 Pro] Lughnasadh:
With the new AML (v. 4.2), JamesDSP (4.6) is now working with the new V4A RE on my Pixel 7 Pro, for those interested.
[Google Pixel 7 Pro] Schroeder09:
Aren't James DSP and v4a two separate apps that do the same things? I'm probably misunderstanding something, but your post makes it look like you're using them all. What's "v4a RE"? Do you have a GitHub link?
[Google Pixel 7 Pro] Fentadroid:
Just installed AML 4.2

This is what i got on my Pixel 7 Pro if I install V4A RE....

https://github.com/programminghoch10/ViPER4AndroidRepackaged

Maybe you mean this version...?

https://github.com/AndroidAudioMods/ViPER4AndroidApp/releases/tag/v0.1.0
[Google Pixel 7 Pro] Lughnasadh:
Yes and no. They are both sound processing apps/mods and have some similar features but also have unique features as well. I personally like some features of JamesDSP over V4A, and vice versa, so when I can I use both and pick and choose what features I use from each mod.

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Schroeder09:
Thanks.

I've asked some questions on the jamesdsp thread about convolvers and equalizers. V4a used to have these files for download. You put them in a specific file path, and then they're selectable from the app. The convolvers change the way audio sounds for different situations and genres. I understood them as pre-configured equalizers. Do those still exist? Is that what you've linked to and what this thread is about? Where do I store them for jamesdsp?
[Google Pixel 7 Pro] Lughnasadh:
Yes convolvers/irs files still exist. For JamesDSP, put the .irs files in the "Convolver" folder that is placed on your internal storage when you install JamesDSP.

I linked you to the new V4A-RE github, not a thread.
[Google Pixel 7 Pro] Schroeder09:
Where are convolvers to be found for download? Are v4a convolvers compatible with jamesdsp?

Can you explain which portions of v4anand jamesdsp are different and why you're using both? It may be applicable in my decision to use bother or only one. Thanks.
[Google Pixel 7 Pro] sharkie405:
This is working great on my Pixel 6 pro running Android 13 December update RiceDroid. I've only used it while playing music from the phone speakers and from my car speakers via Bluetooth, but in both instances it's working great.

Thanks for this!
[Google Pixel 7 Pro] Lughnasadh:
Go to the V4A and JamesDSP Telegram groups and see if they have links or posted any files.

Yes

You should just go to the respective threads and read the descriptions, or even better, just try each one yourself.
[Google Pixel 7 Pro] schmeggy929:
I use both V4Android and JamesDSP. Since Convolvers and VIPER-DDC do not work in V4A I use JamesDSP for those as well as the JamesDSP Equalizer.
[Google Pixel 7 Pro] dd805bb:
Wavelet is where it's at. Viper was good. Dev is the same and show some love for him. Wavelet is his so is viper. Wavelet for me works just the same for what I use. Great app. Can't say enough. Adb a command & blammo whole app works.
[Google Pixel 7 Pro] Schroeder09:
When you adb the command you mean it becomes a system-wide audio app? As I understood it wavelet did everything v4a did BUT there were a few apps like Spotify that it couldn't apply its changes too. You're saying with the ADB commands this a thing or the past and wavelet=v4a. Why not jamesdsp?
[Google Pixel 7 Pro] vibrantliker:
are all the files (presets, etc) now working in the newest V4A that was made to work on A13 with the latest Pixels (6-7's)
[Google Pixel 7 Pro] dd805bb:
I never used JamesDSP. I used Viper before. I like the simplicity of it. I use the bass filter and vocal booster. Along with output gain to max out phone speakers and connected Bluetooth speakers. Whenever anything is playing you can change just what is playing and it will recognize that preset whenever that app is playing music. I use YouTube music and not Spotify either so I don't if that works or not. For what I used Viper, wavelet is a great replacement IMO.

Also equalizer presets with some new ones I didn't see in viper. Headphone preset for a ton of earbuds. Pixel Buds are on there too.
[Google Pixel 7 Pro] Schroeder09:
Aren't the convolvers these presets you speak of? Sounds like your usage is the exact same as mine. I wanted max possible volume but also clarity. I want to boost the vocals too. I listen to a lot of podcasts and radio programs. I don't care to or want bass boost. I prefer clarity for people talking in these long form interviews and shows.
[Google Pixel 7 Pro] dd805bb:
Yes. Definitely help with clarity on vocal booster. I listen to podcasts and it gets some that twang high pitch static out you hear from microphones. Clearer if that makes sense. Free version works great too. I only got the paid version for bass with my bluetooth speaker. And it is loud again.
[Google Pixel 7 Pro] schmeggy929:
The latest update is unusable, even disabled AML and JamesDSP. Toggled Legacy Mode and audio drops and cannot activate V4A again until reboot. The multiple ways to activate V4A do not work. It fails every time. Downgraded to 0.1.0 and everything is fine again.
[Google Pixel 7 Pro] Lughnasadh:
I only had problems with bluetooth but speakers and wired earbuds still working for me on 0.2.0. Of course, bluetooth not working is a deal breaker for many. I think the dev is aware of the bluetooth problems on this version.
[Google Pixel 7 Pro] vibrantliker:
Bluetooth working on 0.1.0? Also, are all viper files working ok, like presets, profiles, etc?
[Google Pixel 7 Pro] Lughnasadh:
I never tried bluetooth on 0.1.0. Not all options are available it's an Alpha release so options are being added as time goes on.
[Google Pixel 7 Pro] vibrantliker:
Maybe you wouldn't mind chiming in : Bluetooth working on 0.1.0? Also, are all viper files working ok, like presets, profiles, etc?
[Google Pixel 7 Pro] schmeggy929:
Yes Bluetooth does work on 0.1.0. However Presets and profiles do not work yet. There are only a few settings that are able to be toggled on at the moment.
[Google Pixel 7 Pro] vibrantliker:
Got it. Will wait to upgrade to A13 until it's more stable.
[Google Pixel 7 Pro] marinovedder:
One question, to all of you V4A users. I was reading a bit in the telegram group for v4a about the "limitations" of the app regarding sampling rate. It is known that v4a is limited to 24/48khz. So anything over that is down sampled I am assuming. I'm not very savvy in this particular subject. So, let's say, my particular music usage is always listening to flac files copied directly to the phone.

Those flac files can go from 16/44 to 24/192. Almost every time I listen to music is through PowerAmp (with the hi-res 24/192+ options for usb dacs available), a usbc dac (either a NextDrive Spectra 32/384 or a Razer THX usbc to 3.5 dongle which I don't know the sampling info, and Sony MDRXB55AP ìn-ear headphones). I rarely listen to those files via bluetooth, but can happen at some point. I never use spotify or streaming music apps.

So, to all of you knowledgeable of this, what is the benefit of using V4A for my listening experience? Is it beneficial for my Pixel 7 Pro?
[Google Pixel 7 Pro] Falcon_X:
Where to get and where to put preset files in Viper?
[Google Pixel 7 Pro] schmeggy929:
They are going to be placed on the SDcard in VIPER4Android folder. You make to make the presets. Only a few settings currently work.
[Google Pixel 7 Pro] yash_ghar:
If you have files above 48kHz and you are using USB DAC, you should use UAPP or Fiio Music as it will pass the audio bit perfect and avoid any resampling. I have used Fiio Music and it asks for exclusive access to the USB DAC and passes the audio to DAC without any resampling.
[Google Pixel 7 Pro] Falcon_X:
Thanks, I will try.

I am using version 4.1 from here https://t.me/WSTprojects

with V4A_Magisk_Module_0.2.0.zip

I haven't tested all settings, but I think all settings are there and I guess they are working.
[Google Pixel 7 Pro] schmeggy929:
Never even knew of this telegram project. This works on the Pixel 7 Pro?
[Google Pixel 7 Pro] Falcon_X:
Sorry, I can't tell as I don't have an Pixel 7 Pro. I've justed posted here, because the other Viper4Android threads are abandoned.

It works for me on an Xiaomi phone, with Legacy mode turned on, together with Dolby Digital Audio Mod.
[Google Pixel 7 Pro] schmeggy929:
Gotcha, There is a thread for V4A here. Viper_FX RE being worked on for Pixel series with 64 bit.
[Google Pixel 7 Pro] Riseaknight:
Installed ViPER4Android-RE v0.2.0 on my pixel 7 pro. It works! Thank you.
[Google Pixel 7 Pro] Neuken6969:
How? Where did you download this?
[Google Pixel 7 Pro] Riseaknight:
Release ViPER4Android-RE v0.2.0 · AndroidAudioMods/ViPER4Android

WARNING: THIS VERSION OF THE DRIVER WILL CRASH ON SOME DEVICES! IF YOU EXPERIENCE CRASHES, USE THE 0.1.0 DRIVER (MAGISK MODULE) INSTEAD. How to update: Download and install BOTH files (App + Magisk...

github.com
[Google Pixel 7 Pro] Techguy777:
dont get to excited it only has bass and clarity working, I have it on my Tab S8 plus and it needs headphone surround sound and gain. At the very least headphones surround sound.
[Google Pixel 7 Pro] Neuken6969:
Ahhh damn ... Anyway ty I found it. I have 0 presets. Since I deleted all my files since I thought viper was dead for the pixel7pro
[Google Pixel 7 Pro] Techguy777:
lol Im confused to because its so close but still not working. I hope for updates but I don't see any progress and I have no idea how possible it is. EvoX rom plays viper for pixel 7 pro. Theres always that
[Google Pixel 7 Pro] Neuken6969:
Evox rom? Never heard of it. Any good? Must be if it's got viper4android just for that I'd test it
[Google Pixel 7 Pro] Techguy777:
https://xdaforums.com/t/rom-13-0_r30-official-evolution-x-7-6-2-03-07-2023.4546503/
[Google Pixel 7 Pro] Neuken6969:
F me I hate doing the reset and deleting everything. I have so many "web pages" open and I lose them everytime I reset
[Google Pixel 7 Pro] Techguy777:
Everyone feels like that. Why are so many open? Because you have lost interest and moved on and thought it was important and youll go back lol. Choices
[Google Pixel 7 Pro] Neuken6969:
P0rn pages lol, and exo doesn't have viper4android baked in. I asked on their page
[Google Pixel 7 Pro] Techguy777:
Are you new? Its not usually baked in you flash the zip in magsik
[Google Pixel 7 Pro] Techguy777:
I don't own the phone I read in the evox thread viper is working. So you know youll probably have to flash a couple of zips. JamesDsp, viper4android, and audio modification library all in magisk manager. Youll also need busybox magisk module. Fox manager apk is a good place to find modules. Its not hard it takes a few flashed zips and a reboot and viper is the best thing about root. But it has to have the surround sound otherwise it doesn't sound as good.
[Google Pixel 7 Pro] Sasaiber:
Too bad the bluetooth doesn't work.
[Google Pixel 7 Pro] Riseaknight:
So it works on speaker but when I try to play through my buds pro then it won't process.
[Google Pixel 7 Pro] Lughnasadh:
Try disabling LDAC.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] jean marc:
Hello,

I broke my touch screen and I change it with new from ebay, but after install it the rotate screen doesn't work, it was working fine with the other screen.

Can it be from the screen who don't have this function? Maybe I must upgrade the Universal again with the Rom to recognize the new screen?

Can some one help me?

Many thanks.

Jean Marc.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] pdc4:
Hi,

What do you mean by "rotate screen" not working?

You are unable to "rotate", or change the orientation of the screen by yourself, when you press the relevant system setting option?

Or instead you are speaking about the auto-rotate screen function that is trigerred when you put (turn) the display facing the keyboard or facing you?

The answers will be different...

Regards,

P
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ATLDON:
If I remember correctly, there is a tiny magnet that is clipped on the edge of the screen housing that controls the orientation of the screen. Make sure that magnet didn't pop out while installing the new screen. Look in the Universal Service Manual to get details.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] jean marc:
Hello,

I speak about auto-rotate screen function when I turn the screen, I didn't saw any tiny magnet clipped on the edge of the screen housing, I will chek on manual.

Thanks.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MikeChannon:
Have a look at the following thread. I know it's for the Hermes, but it shows pics of the kind of magnet you are looking for:

http://xdaforums.com/showpost.php?p=1449001&postcount=6

You will also be able to work out where it should be, by locating the magnet operated switch - again there are pics of what to look for.

Mike
[JASJAR, XDA Exec, MDA Pro Software Upgrading] neutrino:
I had the same problem

Hello Jean Marc

I also had this problem, you just forgot the little magnet mounted near the screen, it's used to tell uni if it's landscape or portrait ...

Good luck
[JASJAR, XDA Exec, MDA Pro Software Upgrading] jean marc:
Eureka

thanks a lot for this info, good it was that I didn't trow the frame, and I found back the small magnet that I'd put in his place. now it work fine.

Thanks again, jean-Marc.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] trzcina:
Hello. I have got the same problem with my Wizard. Could someone tell me where the magnes should be locatated ?
[Google Pixel 7 Pro] v12xke:
Got my P7P today from the Store and unlocked the BL, flashed 13.0.0 (TD1A.220804.031, Oct 2022). Fired right up and configured everything. Used cable to transfer from my DD P4XL. All was well until I started looking at my Wi-Fi speeds. I've got a P4XL and P3XL connecting to my router at max speed, but the P7P will only connect at 54 Mbps. On the P7P, under the AP settings, it says my network type is "Legacy" vs the other Pixel phones saying "Wifi 5". I have rebooted several times and reset network settings twice. I have forgotten and reset the AP many times. What I am seeing is it first connects at 866 Mbps, but immediately drops to 54 Mbps. I don't think it is a router setting because the other Pixels are working fine, as are other wifi devices in the house. Any ideas before I factory reset the phone after spending a couple hours setting it up?
[Google Pixel 7 Pro] ze7zez:
Did you check the speed before unlocking the bootloader?
[Google Pixel 7 Pro] Noe367:
Any news ?
[Google Pixel 7 Pro] v12xke:
Sorry for the delayed response. The problem was not with the phone but with the router. My Netgear R8000 router received a firmware update on the morning before I received the phone. What I did not know was that the update DISABLED WMM, a setting under QOS. Normally a firmware update does not change settings. My search was centered around the phone, so it took a while to come down on the router. Once I toggled WMM on for all 3 bands, the problem went away and my phone now links at 1083 Mbps up/down. All is good.
[Motorola One Fusion Questions & Answers] FrenzyyXX:
Hey Guys

I'm new here and i don't know if this is the right place to post, if so, pls let me know

My Motorola One Fusion (XT2073-2) is bricked, i can only access the fastboot mode and i've tested all the roms i could, but it didn't work ( it shows preflash validation error ) and i couldn't find one for my bootloader "MBM-3.0-astro_retail-d88b69237fd-220323", can anyone help me find what region is that bootloader ?

It will make me very happy, i am searching for it for months 😔
[Google Pixel 7 Pro] badabing2003:
View attachment 5734057

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.

For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 7 Pro] badabing2003:
Placeholder
[Google Pixel 7 Pro] i5lee8bit:
Got Pixel 7 and Pixel 7 Pro (wife and me) on launch day. Both of us coming from 4 and 4 XL. Crazy how far things have come and continue to go. Love this community, and I'm sure I'm gonna love this tool too. Thanks OP!!
[Google Pixel 7 Pro] galaxys:
Great to see GUI Tool! Kudos 📱
[Google Pixel 7 Pro] banshee28:
As soon as BB has my P7P in stock, I will then be taking this for a spin!! Thanks for making it compatible with P7P!!
[Google Pixel 7 Pro] ScottIsMyName:
Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.
[Google Pixel 7 Pro] badabing2003:
Thanks for the feedback, no need for files considering that it worked fine.

It helps to get the confirmation as I don't have a Pixel 7 / 7P device.
[Google Pixel 7 Pro] losticloud:
I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this

Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)

fastboot: error: Command failed

rebooting to bootloader ...

Rebooting into bootloader FAILED (remote: 'Couldn't download data')

fastboot: error: Command failed

After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.

Resizing 'vendor_a' OKAY [ 0.003s]

archive does not contain 'boot_other.img'

archive does not contain 'odm.img'

archive does not contain 'odm_dlkm.img'

extracting product.img (2811 MB) to disk... took 24.746s

archive does not contain 'product.sig'

Resizing 'product_b' OKAY [ 0.007s]

Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]

Writing 'product_b' OKAY [ 0.354s]

Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]

Writing 'product_b' OKAY [ 0.371s]

Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]

Writing 'product_b' OKAY [ 0.358s]

Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]

Writing 'product_b' OKAY [ 0.405s]

Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]

Writing 'product_b' OKAY [ 0.365s]

Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]

Writing 'product_b' OKAY [ 0.403s]

Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]

Writing 'product_b' OKAY [ 0.359s]

Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]

Writing 'product_b' OKAY [ 0.398s]

Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]

Writing 'product_b' OKAY [ 0.362s]

Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]

Writing 'product_b' OKAY [ 0.385s]

Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)

fastboot: error: Command failed

rebooting to bootloader ...

Rebooting into bootloader FAILED (remote: 'Couldn't download data')

fastboot: error: Command failed

Sleeping 5-10 seconds ...
[Google Pixel 7 Pro] badabing2003:
This sounds like a flaky communication problem.

1- Support.zip file from PF's help menu greatly helps

2- Make sure you are only using SDK 33.0.3 anything older will not work

3- Make sure your connection to the PC is solid, and the fatsboot drivers are good

4- USB 2 connections are more reliable

When you scan for devices in PF, does it detect the phone? in any mode?

if yes, what mode is that?

I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.
[Google Pixel 7 Pro] losticloud:
1. do you want me to post it here or PM to you?

2. I downloaded 33.0.3 before starting

3. drivers are good

4. I tried usb 2 connection but doesn't do anything. If i use the usb c cable that it came with it shows up as port com3

I tried scanning with PF and it doesn't detect the device at, I used both usb c and usb 2 cable.

If you can help great, if not I can always do RMA since i just got device. Thank you in advance

If you can help great, if not I can start RMA process. Thank you
[Google Pixel 7 Pro] K1nsey6:
Is this method keeping L1 and Safetynet?
[Google Pixel 7 Pro] losticloud:
Yes, the pixel no longer shows up. it also stopped booting, it's just dark.

Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.
[Google Pixel 7 Pro] K1nsey6:
Holding down Power/Vol Up for 20 seconds isnt rebooting?
[Google Pixel 7 Pro] losticloud:
Nope, doesn't even vibrate.
[Google Pixel 7 Pro] simplepinoi177:
God is that still a thing?!?!?!

LOL, I remember when I first started rooting on my Pixel 2 XL, SOOOO many people were having issues using the USB-C connection, but once they used the legacy USB-A, things would suddenly work!

USB-C connections on a computer/laptop were still rather new-ish, so I figured that was the reason. I can't believe how many years later that this advice would still be relevant! 😅