Database Info

[Q] Headset issue with Sebastian Kernel's ROM

Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?

Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse

[Q] Google Music app sometimes can't play radio

Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.

vaindil said:
Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.
Click to expand...
Click to collapse
Did you ever end up finding a solution to this problem. I've been experiencing it for a couple months now. I emailed Google Play app support but have not gotten a response from them even after numerous attempts.

I keep having this issue too and its so annoying...if anyone has a fix please share.

vaindil said:
Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.
Click to expand...
Click to collapse
PartimusPrime said:
I keep having this issue too and its so annoying...if anyone has a fix please share.
Click to expand...
Click to collapse
Found a solution that worked for me I grabbed the old APK from APK mirror and installed that version instead ( grab oct 21 2014 release) install this version and play a few of the contextual radios they all seemed to work on that version. After playing the ones that weren't working I installed the newest version again and they continued to work.
http://www.apkmirror.com/apk/google-inc/google-play-music/google-play-music-5-7-1717q-1530520-apk/ this is the version that I used to get it working again.

Here's what worked for me... I completely uninstalled the app. It was installed by default as a system app. Then installed again through the Google Play store. Haven't had any issues so far ??

PartimusPrime said:
Here's what worked for me... I completely uninstalled the app. It was installed by default as a system app. Then installed again through the Google Play store. Haven't had any issues so far
Click to expand...
Click to collapse
Thanks for this. I started getting the same error so I followed your instructions. I'm not rooted so I couldn't completely remove the app. But I uninstalled as much as i could and cleared everything I could and the radio stations are working again.

Hey guys
I know I'm late to the party but I found a fix to this issue and I wanted to see if it works for other people. I did this on a galaxy S7 running Android 7.0 and running the latest version of Google play music. Here's what I did:
1. Tap the 3 dot menu on the playlist in question and select "create new playlist"
2. Name the playlist something different from the original
3. Remove one song from the playlist (I don't think it matters which but I removed the first song)
4. Put the song back in the playlist.
5. Check to see if the radio function works for the new playlist
6. Delete the old playlist and rename the new on to what the old playlist was called.
7. Now you should have a playlist that is identical to the original and the radio function should work for it.
Hope this helps.

Bluetooth Metadata & Connectivity Issues

I'm running my OnePlus One and I've had this issue since the first CM12 update to Lollipop, but with the recent OTA claiming to have fixed "Bluetooth" issues and this still isn't fixed I'd really like to know if theres a solution.
Basically I have an aftermarket Pioneer headunit. When I start the car and it attempts to connect to the phone, the phone takes almost a full minute before it connects. Prior to lollipop it would connect in 2-3 seconds.
I stream music from my phone using Spotify and Google Play Music, using either has tons of stuttering over Bluetooth. Atleast once every minute or so, it will stutter for a second or two.
And finally, the radio only ever sees the song information for the first track that plays from when the phone connects. Skipping songs, restarting the app won't change the song data that's being sent out. The only thing I can do to update is to restart the phone and it will get stuck again. This is by far my biggest gripe because it worked fine on KitKat and JellyBean for me on CM11.
I really like Lollipop but neither CM12 or OxygenOS has solved this issue for me. Right now all I can think of is just flashing an older CM11 rom but I'd like to know of any alternatives, whether that be a different ROM or whatever. I've also read up that someone just flashed an older CM11 radio/modem onto CM12, but I don't know if that was a solution, there was no follow up post.
It does this with nearly every aftermarket radio I've paired my phone with (friend's cars etc.)
Details:
OnePlus One
CM12 YNG1TAS2I3
TWRP Recovery / Rooted.

My voice is apparently horribly disformed when I make phone calls

Hi!
My OPO has the latest CM13 nightly (from https://download.cyanogenmod.org/). For some time now, whenever I make a call, people tell me it's impossible to understand me.
Everything else works fine. Is this fixable? Am I the only one?
I would guess that flashing the latest radio would maybe help. Where can I get the latest radio, etc.?
Cheers!

As I noted there are only two possible causes (most of the times):
1. AudioFX causing this (Turn that OFF)/V4A/Other Audio MOD
2. Google Now Voice Turned On (Turn that OFF)

Microphone not working...

My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??

i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse

LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.

since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.

I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.

toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...

I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.

Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem

LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?

I installed lineageos 16 without gapps and is working good for hours until installed gapps.

ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??