Hi all,
So I recently received a replacement S6 (because of a camera vibrating issue). Thankfully that issue is fixed, but what I've come to realize is that whenever I listen to podcasts, my phone would randomly rewind or fast-forward what I am currently listening to on its own. It took me a day to realize I wasn't crazy.
For example:
While listening to a podcast using Podcast Addict or PodBean, audio would randomly repeat the last 5 seconds, or skip forwards 5 seconds. I tried multiple stations, apps, and even kept the screen on to watch for it to happen. I thought it could possibly be my phone inputting commands on its own, so I watched and noticed Podbean only has a R/FF option for 30 seconds, yet it still does it in shorter increments.
Questions:
1. Has anyone experienced this before?
2. Is there any way to for the device to trigger a toast when a command is issued?
3. Would a keylogger work to find out what's happening? (I don't know..)
4. Should I get another device? Maybe this is why my current device was returned?
Currently on:
Galaxy S6 Replacement Device
Stock S6 MM 6.0.1
Having same issue.
I am having the same issue I started to notice it right after I updated to Marshmallow 6.0.1. Im using Pocket Casts as my podcast app. I have not found any fixes, I thought I was the only one with this kind of issue
Related
Anyone else having issues with Google Music lately??
I've noticed songs pause themselves, and upon pressing play they rewind some.
Specifically, I've found Pearl Jam's free album "Toronto Live" the 1st song, "Long Road" @ 5:27s it pauses itself everytime I've played it. And upon hitting play it rewinds to about the 5min mark and pauses again @5:27.
This may be very specific to this track, but I've noticed all sorts of weirdness that last month or so, with tracks not playing at all, shuffle not working properly (ie: not progressing to the next song), and even songs skipping mid-track.
I'd like to think this is an isolated incident, but it also has been happening on my Atrix, and I've even tried reverting back to prior and as of last night, the new versions, with the same issues popping up. I've been using the beta version since release and its only been the last month or so, and I've noticed it on a variety of Roms (however I have not tried full stock on either device)
Perhaps this is due to being in "Beta" and maybe the surge of new users, but just throwing it out there to see if anyone else has had issues similar to these.
I have a Note 4 and have zero problems with BT disconnects but this damned watch seems to disconnect every 10 minutes then won't reconnect. What a pain.
Not sure what firmware you have on your note 4 but I had this on my note 3 when I had my phone running lollipop leak firmware
Since going back to kit kat on the phone it hasn't lost connection once
I think therefore there are issues with lollipop currently
I have this constantly on my Verizon Galaxy note 3 with Eclipse 2.2 ROM. With watchmaker, I'm constantly feeling 2 vibrating pulses (disconnection), immediately followed by a single vibrating pulse (reconnect).
Frustrating as all hell. I've searched forums and online but nobody else seems to have this same problem.
Cheers,
B.D.
EDIT: I just froze Google "Hangouts" app on my phone based on another post that said sometimes certain programs (hangouts, Skype, and a few others were mentioned) and suddenly no more disconnections in the past 30 minutes.... I will monitor it for a few hours/days to see if the disconnections return, but this may be what has been causing my phone to disconnect/reconnect every couple of minutes....
Yes, it`s Lollipop 5.0 bluetooth issue. Works fine with Teamsek 5.0.2 CM12, Resurrection 5.4.0 and of course KitKat 4.4.2 roms.
Ok, after too much frustration I flashed a mostly unmodified ROM onto my phone, and my issues disappeared. My battery life is much better, and I do not get constant disconnections/re-connections anymore.
My thoughts are that some of the pseudo-drivers used on ROMs may not be completely compatible with some of the Bluetooth Low Energy (BLE) devices, or specialty devices, such as Android Wear watches.
Cheers,
B.D.
BostonDan said:
I have this constantly on my Verizon Galaxy note 3 with Eclipse 2.2 ROM. With watchmaker, I'm constantly feeling 2 vibrating pulses (disconnection), immediately followed by a single vibrating pulse (reconnect).
Frustrating as all hell. I've searched forums and online but nobody else seems to have this same problem.
Cheers,
B.D.
EDIT: I just froze Google "Hangouts" app on my phone based on another post that said sometimes certain programs (hangouts, Skype, and a few others were mentioned) and suddenly no more disconnections in the past 30 minutes.... I will monitor it for a few hours/days to see if the disconnections return, but this may be what has been causing my phone to disconnect/reconnect every couple of minutes....
Click to expand...
Click to collapse
I have the same problems with my Note 3 on Lollipop 5.0.1. Very bad.
Update: now I am back on 4.2.2 and everything works fine. Maybe there is a way to handle this problem?
Hello good people,
I hope someone finds time to read this and help me to find a solution.
I was using "throw" function on the default Music player app to play on my Denon AVR since my Z3c was on KitKat, later it upgraded to Lollipop (I think then it became "cast" instead of "throw") and later it upgraded to Marshmallow - all was good, one touch and I had music playing through my audio system. I recently replaced my phone with another Z3c and was happy until tried to cast my music - it plays intermittently (2 seconds of sound followed by 2 seconds of silence and this repeats non stop). I've tried installing 3rd party apps (AirAudio) but the issue remains. Today I had a chance to hold my old Z3c and to my big surprise - it also developed the same intermittent play issue when casting! The only thing which changed on my old Z3c since I owned it was that it was reset to factory default settings.
Any ideas would be very welcome, second day googling and still no music
Thank you!
Tadas GPS said:
Hello good people,
I hope someone finds time to read this and help me to find a solution.
I was using "throw" function on the default Music player app to play on my Denon AVR since my Z3c was on KitKat, later it upgraded to Lollipop (I think then it became "cast" instead of "throw") and later it upgraded to Marshmallow - all was good, one touch and I had music playing through my audio system. I recently replaced my phone with another Z3c and was happy until tried to cast my music - it plays intermittently (2 seconds of sound followed by 2 seconds of silence and this repeats non stop). I've tried installing 3rd party apps (AirAudio) but the issue remains. Today I had a chance to hold my old Z3c and to my big surprise - it also developed the same intermittent play issue when casting! The only thing which changed on my old Z3c since I owned it was that it was reset to factory default settings.
Any ideas would be very welcome, second day googling and still no music
Thank you!
Click to expand...
Click to collapse
Hi,
was the version of firmware on your replacement phone the same as your old phone?
The early versions of Marshmallow had a problem with Bluetooth, specifically throw and stuttering audio.
Have you tried to update your phone with PC Companion.
How far are you willing to go to fix your problem?
I am using the latest version of MM from a developer called Wajik that has no Bletooth issues. But obviously you'd need to root your phone and add recovery to get there. I know it sonds complicated, but there are several great guides and lots of friendly folk here to help you if you get stuck.
Edit: There is a music player called Poweramp, that has the ability to change the priority of the player, it also has a buffer that you can change yourself. With both of these features tuened up you might be able to defeat the stuttering without any major regime change. It also comes as a trial as well.
Hi,
I had been using Android Auto with a Huawei P8 lite. It never crashed, but only the response times where a bit sluggish.
I got a brand new Samsung 5 Neo, and after setting up the phone, there was immediately an update to Marshmallow.
When I started using Android Auto, I was pleased to see that the overall experience was faster and better than my Huawei.
But for some reason, during (longer) drives, my Spotify (and Google Music), would crash in the middle of a song. (first a stutter, it could happen after two songs, five songs, there is no logic in it). After it crashes, Google Maps becomes unresponsive. The only thing that helps is disconnecting the cable.
After reading the web, I learned that it could have been because of the marshmallow update.
So after trying all the usual fixes (rebooting phone before using Android Auto, keep data always alive, etc), I decided to downgrade to Android 5.0.
At first sight, I thought everything was solved, but after a few days, the exact same problem started to appear
I will now try to clear the app cache, and reboot the phone each time, but I'm a bit dissapointed that it doens't work as it's supposed to work.
Any tips, remarks are welcome.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.