No driver found

Question

No driver found

Closed this issue 2 years ago · 7 comments

DJohnston79 commented 2 years ago

Using P7 latest a13 and module v 1.0
Followed install directions: no driver found
Go to GitHub prompt

Module 2.0
Same as above

Anyone had success on P7?

Answer 1 · 2023-01-26T19:44:50.000Z

try the latest v0.2.0 instead 0.1.0

Answer 2 · 2023-01-27T07:25:24.000Z

Thanks . I did but it doesn't kick on when using Bluetooth. I hear it switch on but either don't notice a difference or switching on various options doesn't do anything :-/ regards, Dennis Johnston

…

On Thu, Jan 26, 2023, 8:45 PM SWHSmash ***@***.***> wrote: try the latest v0.2.0 instead 0.1.0 — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOW3HK7LQLSVVZNRMQIRSLWULH3ZANCNFSM6AAAAAAUEXAE3E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 3 · 2023-02-03T12:14:18.000Z

Try enabling the Legacy mode in app settings and restart the app. You can verify the processing status within the app itself.
To confirm it actually works, try increasing or decreasing the master volume gain within Viper app.

Answer 4 · 2023-02-24T12:20:43.000Z

I too have a Pixel 7. It's the pro version. I tried the 0.1.0 version and the 0.2.0 version. Neither worked. I get the driver not installed. Error prompt. I have James DSP on my phone. If it matters. It stopped working after the Google February security patch update. Idk what else to do. P7p, February security patch, magisk 25.2, and lsposed 1.8.6 (if it matters).

Answer 5 · 2023-03-10T23:48:11.000Z

Hi! Try it with v0.3.0 and the latest version of Audio Modification Library. Reopen the issue if it still doesn't work.

Answer 6 · 2023-03-10T23:51:46.000Z

Why was this closed?

…

On Fri, Mar 10, 2023, 6:48 PM Iscle ***@***.***> wrote: Closed #17 <#17> as completed. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIG3ZW46646JJSSAH64R7T3W3O4UPANCNFSM6AAAAAAUEXAE3E> . You are receiving this because you commented.Message ID: ***@***.*** com>

Answer 7 · 2023-03-10T23:52:49.000Z

Why was this closed?
…
On Fri, Mar 10, 2023, 6:48 PM Iscle @.> wrote: Closed #17 <#17> as completed. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIG3ZW46646JJSSAH64R7T3W3O4UPANCNFSM6AAAAAAUEXAE3E . You are receiving this because you commented.Message ID: @. com>

There was an update which fixed this issue.