Viper4Android + Nougat - Nexus 6P Q&A, Help & Troubleshooting

Since the last dev preview up to the final release, I've been having some major issues getting Viper4Android to work properly with Spotify and Google Play Music. For whatever reason, it works for a few minutes after the initial Nougat setup, then stops working whenever I'm steaming music. When I look at the driver status, it says "processing: no."
However, on Pocket Casts things are running normally - which is less than ideal since I turn it off when listening to podcasts.
I've forced permissive mode at boot, removed MusicFX, the audio effects file in the root folder, yet I still can't get it to work properly. I've even flashed various "fixes" and versions of Viper4Android, still, nothing changes.
This is exactly what kept me from staying on the dev previews, and I'm bummed to see nothing has changed since the final release.
I'm on the verge of pulling my hair out! Has anyone successfully gotten Viper4Android to work properly on Nougat, and if so, how?

It is entirely possible that viper needs to be updated due to changes in the coding. This would be something you may want to ask about over at the actual viper forum

Related

[Q] Bugs and Questions for OMNIROM 4.4 Nightly

Hi,
I recently flashed my Samsung s3 i9300 and installed the Omnirom-4.4-20131112-i9300-NIGHTLY build.
I came across the following bugs. Some are already listed over the web , but thought still to list them together to see if they hav been fixed, or are in the process :-
1) Sometimes music doesnt play with headset. Have to remove the headset, play it once on speakers (duration doesnt matter, a milisecond would do too ), and then plug headsets back in, and it works.
2) When i lock or unlock a phone while music is playing, there is a sound (something like a thread or something got stuck for half a second and the music note got repeated).
3) com.android.(something).systemui crashes sometimes.
4) I couldn't find a default File Manager. I don't know if stock android has something like that or not. Just thought to bring it to Notice .
5) Cell Broadcasts with garbled messages.
6) My Cell (not battery. I removed the battery to see if it was hot, and it wasn't. Though, the lower part of the cell, where the Exynos Processor has started overheating a bit. Tasks performed while doing this :-
a) Downloads
b) Music Pkayback + Surfing
c) Games.
7) I want to know if the builds include an OTA update system or i need to flash my mobile again to install the latest nightly. Because nightlies have been released till December, but my mobile shows "Your system is up-to-date) in Settings -> About Phone -> System Updates
I checked and found that the latest nightly for 4th December has been released, has any( or all) of the bugs been fixed ?
I'll give out more bugs, as and when i get them
Thank you in advance!
PS : Great work people. First time i flashed my phone, and i really liked it
8) In Video Playback, i don't get any video. It's just audio. Also tried on custom app MX Player.

Having strange issues? 6.0.X or 7.0 bring strange bugs? If you haven't already, try..

Flashing the very first 6.0.0 (MDA89D).
In my ventures this last week or so, after dealing with the Battery issue (15-30% power off range) and having my speakerphone mysteriously stop working (It was as if I hit mute to the person on the other end) I have been doing all the research and tinkering I could think of to see if these were indeed hardware or software issues with our 6P.
So in my venture, It may be that 7.1.1 fixed the battery issue for me, as after 3 full rundowns over the past few days, I was able to run down to 3% and then 1% 2 times before shutdown which is immensely better than shutdown anywhere from at best 13% to ~25-30% at worst when you're trying to use your phone through the day.
This was done by running the Mountain app to put a load on the device while I do other things. Once I see it hit 15% I allow it to turn on Battery Saver and watch as it ticks down to 1-0% and goes into Shutdown.
Not sure how truly comprehensive this test is, but so far, it is pretty incredible to have such an improvement over what many of us have been experiencing with our battery life being a cointoss through the day.
I only had 7.1.1 flashed as a fresh image straight from google, TWRP 3.0.2-3 and SuperSU 2.78 SR5 for Root for this test. No Google Account connected or anything else syncing or updated that would touch the battery or run in the background.
Now for my Speakerphone issue. I cannot recall exactly when the issue happened, but since I have been running PN since literally the day I got my Nexus, somewhere in that time, with a lot of dirty flashing from one MM update to the next, messing with Kernels, and overall going quite a while between clean flashes until I finally did one for the move to 7.0, I lost my Speakerphone Mic and only the sound for speakerphone was coming out of the bottom speaker. After testing my Refurb replacement and now my "fixed" original 6P, sound for the speakerphone is supposed to use both Speakers when everything is working normally.
The test for this was easy to do with the Skype Test Call. Just call it and turning on Speakerphone would either work, it records my voice and plays it back, or when it wasn't working, it would just end quickly telling me it doesn't hear anything (and the audio only comes through the bottom speaker).
So TL/DR and plainly, my recommendation if you haven't already done so, and you are having similar interesting and semi baffling issues such as these, try flashing the oldest Image available for our 6P as I did (Directly from google, I just did the Flash-all.bat file as it was included with the minimal ADP terminal on Windows 8.1) and let it do its thing. Once I was in the original MM build, I just skipped my way to my homescreen, downloaded Skype from apkmirror, and logged into that to do the test. Boom! After the test was a success, I downloaded the 7.1.1 image, flash-all.bad'ed that and did the same skip to test.... And Boom! Speakerphone Continues to work normally.
Now to test the battery side by side with both devices to see how bad my old one has degraded if it indeed has done so... or if 7.1.1 has indeed fixed that as well.

Audio "crash" on multiple ROMs (including stock)

And boi it's annoying. For Alarms and and Calls the system simply stops all audio.
To put the long story short; an error happens at a moment be it double disable audio or simply unable to use the driver or similar. It doesn't happen at any exact moment, it can happen at random. And it's really annoying. Like I said, music players stop working, alarms don't work (vibration does tho), you can make nor answer calls.
I honestly thought this was done via Amplify or Greenify or something, then moving to other roms, it kept happening and thus I decided to post it here. I have logcats if needed.
In my case; last few occurrences went off with a lag, trying to navigate and seemingly freezing for about 2-3 minutes and then the audio crash. sadly didnt log that one.
bump?
lordsolrac2 said:
bump?
Click to expand...
Click to collapse
This won't be of much help but I haven't experienced any audio issues with any ROM yet.
Do you have any utilities such as V4A or AFX installed? Do you have a custom kernel with sound control installed? Also, if you're on Vegito audio may crash while the phone is off as Vegito will unplug all cores but one when idle.
There was a featured XDA thread about enabling high-perf mode for Qualcomm DACs too... it simply sets it to maximum power at all times to the DAC, reducing audio startup delay. Worked fine on my G4 with Magisk, but ymmv.
I do not have any mods installed. And have the ROM kenrel (In this case AOSIP)
I have some catlogs if needed @[email protected] However, mind letting me know of this featured thread? sorry for the ridiculously late reply, I thought I had replied the same day.

Light + Stable ROM for a work phone?

Hi guys,
My LG V20 is my main, and also my work phone. My goal is to have the lightest ROM available while still having a stable feature set (speaker, bluetooth, wifi, etc all working normally)
After a bit of trouble, I finally got 14.1 Lineage OS loaded up and it's definitely lighter but I've been running into issues. People do not hear me well on speaker, bluetooth music play "skips", and now the bluetooth is no longer connecting to devices I've connected it to before.
I'd love to have something that removes all bloatware, but still has the stability of stock. Any recommendations?
I have a H910 AT&T Variant,
My job requires my phone. I mainly use my phone for Skype, WhatsApp, Email, Google Maps + Navigation, Playing FLAC music using High Impedance headphones and Car 3.5mm input, FM Radio, RockRadio.com app/Galaxie Radio(RadioKing) app and 4G LTE data.
I tried AOKP, RR, LOS, Alpha and Super...both ver. 7(Nougat) and 8(Oreo).
This took me a very long time to decide, I also tried older stuff like WETA, etc...
Alpharom Oreo works best for me, everything I listed works fine.
I use the mk2000 kernel, great battery life, with heavy use you need to fast charge sometime in the day.
The only problem I have, the wifi seems to go off when phone is inactive because whatsapp on pc keep saying not connected until you unlock/wake up phone.
But it is so awesome, I love it...
AOSP based roms have problems with audio and dac, it works but not loud and clean, I tried playing with mixer file but no luck.
They are much faster and LOS15 based roms have the second screen working with custom kernel...
Don't worry, it is work in progress...
This is just my opinion, and it suits my lifestyle, you need to try some different ones and see for yourself.
It's funny you mentioned Alpha being the one you like most. I was going through the roms yesterday, and couldn't install some of the Oreo based roms (I'd get an error that the kernel wasn't the correct one, I guess since I was coming from 14.1)
After looking through some, I ended up installing the alpha omega oreo rom with mk2 kernel and it is working great so far (I just haven't tested bluetooth yet).
I've lost all the sluggishness I saw before, especially when using "Ok, Google" to add calendar appointments, etc.
I have the second screen which is also a nice little bonus. Battery life seems to be as good as it's been, as well.
One question : I tried using Magisik to check all the bloatware I wanna hide, but it doesn't seem to do anything? Is there a way I can remove LG and ATT bloatware completely?
i am still using wetarom with weta kernel... since it was well developed and a stock base rom, i found no problem whatsoever while using it... even tho is outdated, no one has successfully hacked my phone yet lol
The alpha install lets you choose what bloatware you want to remove...
Flash the magisk zip right after before reboot, thats what I do...
You can disable whatever apps remain like uber, etc....
I just keep LG Smartworld for themes, LG Health, FM Radio and LG Music app.
I've been trying to get the LG AirDrive to work, it worked some time with older alpha build but it now keeps crashing.
---------- Post added at 07:42 PM ---------- Previous post was at 07:11 PM ----------
WETA was/is a great rom but something about running the latest android appeals to me. Great performance/battery life and audio stuff.
So far alpha rom has been working well (still trying to find a safe list of bloatware that I can remove via ADB, or some other way.)
Only issue I'm having, which I also had before, is that bluetooth play (especially in the car, but no exclusively), will sometimes stutter like it's a 90's cd player. Not sure if it could be related to the case I have on the phone at all? I'll have to test it both ways and see what happens
Just run BluReset app included with the ROM (I think you have to select it) it helps but need to do it ever so often, I just use Bluetooth for calls in the car and 3.5mm for audio.

Viper4Android sometimes not working

Hey Guys ,
I tried a search here in the forum but I can't find anything related to my problem.
I'm using a OnePlus 6T with OOS 9.0.11, rooted with Magisk and I'm using the Viper4Android Materialized module from Magisk manager.
After a time not using viper/not listening to music, the service stops working. I force closed viper, cleared cache and reopen it doesn't help. Viper itself says that the drivers are in supported state. But I can play around in the app and nothing changes.
After a reboot viper works again but I don't know how long. And rebooting the phone Everytime I want to listen to music is a bit annoying.
So I'm asking here if someone experiences the same issue and/or maybe have a solution for this.
Thanks in advance
Calvin
I have the same problem. You may try "Lock Effect Mode" in Viper4Android Settings. This works for my for Bluetooth headphones.
Try enabling the persistent notification in viper settings
Maybe you have to update to the latest version (2.6.0.5): https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Magisk Modul is not allways up to date.
I'm on Version 2.6.0.6. (from the telegram group) and Viper4Android work with spotify most of the time. When I play around with the V4A settings I loose sometimes the V4A. Then I have to stop and play the music again and everything is fine.
I don't have that problem whatsoever.... UNTIL i use my work profile, because at the moment of installation, i chose "system" and thus it's "installed" in both profiles and they conflict, but when i remember I'll change it to data partition... and hopefully it'll solve it.
I usually get it back by closing my work profile and if isn't enough, a force close and/or "disable selinux" from within viper, i haven't checked to see if my kernel actually allows it or not or whatnot for that matter, but it seems to trigger a refresh for the app and starts working again, and/or try toggling the main switch off/on again.
I tell you many different scenarios because i don't know your firmware nor kernel, viper setup and other audio configurations, neither do i have any info of other settings, such as the battery's background restrictions for the app along with the optimization status, etc.
Play with it and you'll be fine!
I'm on beta two, clean slate kernel, viper and dolby along with the modification and compatibility modules, all installing choices set to "1", and like i said, viper as system.

Categories

Resources