Whenever I use Poweramp to play music data seems to stop working. Mobile and wifi doesn't work until I reboot. This is a weird issue that i never had with any previous device, and I've been using poweramp for years with numerous devices. That's why i think the phone is the issue, not the app itself. Is this happening to anybody else?
I also use Poweramp and don't have any connectivity issue when playing music. I'm on Havoc OS.
Are you on OxygenOS or an AOSP based custom ROM? which kernel? Does it also happen after a factory reset?
Toutatis_ said:
I also use Poweramp and don't have any connectivity issue when playing music. I'm on Havoc OS.
Are you on OxygenOS or an AOSP based custom ROM? which kernel? Does it also happen after a factory reset?
Click to expand...
Click to collapse
I am on stock Oxygen OS 9.5.9 the issue was present in 9.5.8 also. Coming from T-Mobile ROM
Just tested on my TMO phone. No issues with wifi or data.
roaduardo said:
Just tested on my TMO phone. No issues with wifi or data.
Click to expand...
Click to collapse
It's so weird. I don't get it. If i play music for longer than a couple of minutes, no data until i reboot. I might have to perform a hard reset
I've started using Player Pro instead and the issue is resolved. Therefore the issue is with Poweramp.
Related
It happens fairly often, any ideas?
DX 2.3.3
In retrospect it may have been equalizer app from market. Currently running cm7 with dsp manager, no reboot issues.
marculous said:
It happens fairly often, any ideas?
DX 2.3.3
Click to expand...
Click to collapse
DX+CM7
Mine doesn't reboot, but Music crashes every time I try to stream over 3g. Works great on wifi. Hope they get the bugs out, because I like the program.
Sent from my DROIDX using Tapatalk
TurboD said:
Mine doesn't reboot, but Music crashes every time I try to stream over 3g. Works great on wifi. Hope they get the bugs out, because I like the program.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
I was having some issues at first. It was either gingerbread or equalizer. Works fine now with cyanogenmod.
DX+CM7
I used to have that issue, but it disappeared after a few factory resets (not because of google music, other reasons). It happened only when I started playing music then locked the device, but not every time it rebooted. I did have that music Fx equalizer however.
Because one signature isn't enough.
I hate doing resets, although I'm using Titanium now, so it should be an easy restore. Maybe I'll try that this weekend. Was kind of hoping for a app update that would fix it.
TurboD said:
I hate doing resets, although I'm using Titanium now, so it should be an easy restore. Maybe I'll try that this weekend. Was kind of hoping for a app update that would fix it.
Click to expand...
Click to collapse
I don't think a factory reset if necessary, just remove the equalizer app if you have it, but if it's not the problem try everything before factory reset even if you have titanium, a single app isn't worth it because if you just restore everything back it's likely the problem will still be there.
Because one signature isn't enough.
Factory resets didn't fix my issue, even tried only downloading that app to make sure it wasn't interference from another one. But somehow I managed to get it to work when I unchecked cache music and wifi only from on to off and vice versa. Now it streams on both wifi and 3g like it's suppose to. Must have been a glitch in there.
G music is a data hog. I'm twenty days into my billing cycle and I've used over seven gigs of data on 3g. That's the only thing I've used differently. Luckily I have unlimited data, truly unlimited according to a Verizon Rep.
DX+CM7
Hey
Since I have my s8+ this app keeps freezing on me. Sometimes it works, but that's not often. I open the app and it is just staying on A and the arrow is not transparent as it should while tuning. It's also not a setting because non of the buttons are working.
I've tried clearing data and cashe and I've just flashed renovate ice 3.0 so it's not a rom issue as it occurred on both stock and custom.
I've had a s7 edge and it was working fine there (also nougat)
Also it's the official app from play store.
Anyone an idea how to fix this?
Thanks in advance!
I use cleartune all the time, I haven't had any issues. Have you tried uninstalling/reinstalling? I have a tmobile so I don't know about custom ROMs as we have no custom ROMs.
sanjsrik said:
I use cleartune all the time, I haven't had any issues. Have you tried uninstalling/reinstalling? I have a tmobile so I don't know about custom ROMs as we have no custom ROMs.
Click to expand...
Click to collapse
Yes I've reinstalled it but that doesn't do the job
When i run discord it blocks the mic in clear tune from working. You proably have some app blocking it cause it taking over the mic.
The problem for me is im runnign into issue with this being in stable in andriod 9 stock tmobile. I dont think they have updated the app in a while. Drag cause this is the best tuner app on the market for sure
Hey all,
Its been a while when I couldn't make any phone calls using any bluetooth devices, non work; car, headphones, loudspeakers with mics even with the phone toggle on in bluetooth settings. This started before the first beta of P, sometime after purchasing the device.
I know that there are some bluetooth problems with some people on the pixel and Android Oreo and Pie but couldnt find any information if these problems are solvable or not.
I installed the official Pie update today and the issue has not been fixed, does anyone know if there is a solution to this or should I wipe the device clean and start over?
Of123 said:
Hey all,
Its been a while when I couldn't make any phone calls using any bluetooth devices, non work; car, headphones, loudspeakers with mics even with the phone toggle on in bluetooth settings. This started before the first beta of P, sometime after purchasing the device.
I know that there are some bluetooth problems with some people on the pixel and Android Oreo and Pie but couldnt find any information if these problems are solvable or not.
I installed the official Pie update today and the issue has not been fixed, does anyone know if there is a solution to this or should I wipe the device clean and start over?
Click to expand...
Click to collapse
I have no issues. I'm using the pixel 2 straight from Google, on verizon. Make sure to do a clean wipe when upgrading to Android P, not a dirty flash.
I downloaded the factory images (not OTA), flashed the update script in Windows which wipes everything by default. I then rooted using Magisk 16.7.
I just took a phone call using phone speaker with no issue. I then used my sennheiser momentum wireless bluetooth headset to call my voicemail. No issues, and sound quality is great.
So yeah, make sure to do a clean wipe on the update. I recommend the latest factory images and not the OTA. Perhaps maybe your radio and/or vendor images are mismatched? The latest factory image will make sure everything is in sync.
davidisflash said:
I have no issues. I'm using the pixel 2 straight from Google, on verizon. Make sure to do a clean wipe when upgrading to Android P, not a dirty flash.
I downloaded the factory images (not OTA), flashed the update script in Windows which wipes everything by default. I then rooted using Magisk 16.7.
I just took a phone call using phone speaker with no issue. I then used my sennheiser momentum wireless bluetooth headset to call my voicemail. No issues, and sound quality is great.
So yeah, make sure to do a clean wipe on the update. I recommend the latest factory images and not the OTA. Perhaps maybe your radio and/or vendor images are mismatched? The latest factory image will make sure everything is in sync.
Click to expand...
Click to collapse
Thanks! any idea how to do it without unlocking the bootloader?
Of123 said:
Thanks! any idea how to do it without unlocking the bootloader?
Click to expand...
Click to collapse
Search for it.
Any fixes? It keeps crashing and reboot doesn't fix it.
Open "Beta" build. Expect bugs. Also there's a reason this build is pulled back by OnePlus. Downgrade to OB11. Everything seems fine to me on OB11.
No issues here on OB12
silvercat said:
No issues here on OB12
Click to expand...
Click to collapse
Click pair new device. I'm getting crashes on 9.0. 3 official.
Batfink33 said:
Click pair new device. I'm getting crashes on 9.0. 3 official.
Click to expand...
Click to collapse
Same problem for me. It happens every time I update the ROM, beta or not, I have to do a clean install each time ...
Anyone has fix this Bluetooth issue in ob12?
So it's still not fixed in ob14
Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far
Hello,
I had the same crash with stable 9.04 approx one week after upgrading from 9.0.3.
Suddenly, entering bluetooth made settings app force close.
I couldn't find any solution and ended up to factory reset the phone...
elmarian756 said:
Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far
Click to expand...
Click to collapse
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.
sylvn said:
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.
Click to expand...
Click to collapse
Sorry but i use none of these. In my case the rom starts to collapse itself after a few updates dirty flashed. Some system apps not showing on ocasional boots, some sudden soft reboots and then lockscreen not showing at all, theming bugs, and Bluetooth crash. I take backup using oneplus switch and titanium and fresh install open beta, restoring all doesnt take more than 20 minutes.
My bluetooth setting crash, i couldn't connect any new devices. so i searched for solution in this forum. im on OOS 9.0.4. just before i take the plunge wipe data clean install rom, i tried the following.
I first cleared Setting App cache and data, didn't work.
then i gone into recovery and cleared Dalvik cache, didn't work.
then i used Clean Master and cleared system cache, 3gb worth, and bluetooth setting worked again!
hope this helps someone in the future.
Hello guys, i just noticed that bluetooth settings crashing ,everything was working fine for me (as long as i remember), but yesterday i was trying to pair a BT controller and it happened. So let me explain, turning on and off bt affects nothing, but when it's on and you try to go to the settings by long tap on quick settings or by the settings it crashes. when it's off you can go to the settings but once you try to pair a new device it crashes, old paired devices pair when you turn on the BT so it happens only when you try to pair a new device.
I tried to go to the 9.0.6 but it was crashing there too, so i rolled back to OB19.
I'm rooted, magisk 19.2 and twrp and with stock or smurf kernel it crashes , so i ended up pairing the controller with a third party app.
I'm sure it was working before because i paired alot of devices. I tried some "fixes" like freezing the bttestmode or clearing the cache and data of the bluetooth but none of those fixed the issue. So did anyone find a solution.
Thank you
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You just came out of nowhere, thank you it worked when i found that there was no device name in the About Section, changed it and now it works.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
True hero right there. Thanks man !
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You are freaking Jesus Christ sir, whole day searching around and I was about to give up and clean flash.
Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
Many Thanx
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??