Audio Of Streamed Music Increases When Passive Jammer Active about pilfershushjammer

[kaputnikGo]

hmm, i think that this may have something to do with the EQ checking routine that is run when testing for device abilities.

Thanks for the bug report :) I will look into this.

[puppykickr]

Yes, I think so too.
Also, today, I turned on an enhancer called Equalizer FX, and it is working just fine with PilferShush.

[kaputnikGo]

ok, have update the app and released to google play and here (which fdroid should pick up on in some days...).
the EQ checking function still checks for the existence of an EQ and any band divisions but doesnt really do anything at all. i left it in for when (if ever) the active jammer gets updated to a native version. it would seem that changing the eq is NOT application specific but instead operates across the whole device - which probably makes sense. This would explain some of the volume differences as some freq bands were boosted, others squashed.

But the other thing that may be occurring is the output audio check routine instantiates an audio track object to test device capabilities and sets a volume level as part of this. Then it destroys the audioTrack object but it would appear the volume level stays set. So now the output audio check is only run if and when the Active Jammer is engaged. App init and passive jammer run will check the record audio capabilities only. The bumping of any audio apps that are already running is more than likely to be caused by the Jammer's audio focus request, so this is now only done when active jammer is started.

hopefully this fixes those problems,
and thanks again for the bug report!!

[puppykickr]

Cool. Always glad to be of any help for such a useful app. Grant Ryan Swan (puppykicker)

…

On Mon, Aug 26, 2019, 23:33 kaputnikGo ***@***.*** wrote: ok, have update the app and released to google play and here (which fdroid should pick up on in some days...). the EQ checking function still checks for the existence of an EQ and any band divisions but doesnt really do anything at all. i left it in for when (if ever) the active jammer gets updated to a native version. it would seem that changing the eq is NOT application specific but instead operates across the whole device - which probably makes sense. This would explain some of the volume differences as some freq bands were boosted, others squashed. But the other thing that may be occurring is the output audio check routine instantiates an audio track object to test device capabilities and sets a volume level as part of this. Then it destroys the audioTrack object but it would appear the volume level stays set. So now the output audio check is only run if and when the Active Jammer is engaged. App init and passive jammer run will check the record audio capabilities only. The bumping of any audio apps that are already running is more than likely to be caused by the Jammer's audio focus request, so this is now only done when active jammer is started. hopefully this fixes those problems, and thanks again for the bug report!! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=AKWIG727D3DO33Y4Z6G6VRDQGSVANA5CNFSM4IPLWMPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5GOH6A#issuecomment-525132792>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKWIG7ZTTW3LEOAGJNZV4LLQGSVANANCNFSM4IPLWMPA> .