Bluetooth Problems with Galaxy S4

If you deleted the phone from the Prius and deleted the Prius from the phone by doing the factory reset, then there isn't much else except if you haven't tried pulling the battery out of the S4. Not sure if your Prius head unit has the setting to perform a wipe all personal data and settings on the Prius, but if it does, you might try that.

I have an S4 on Sprint and just the Lollipop 5.0.1 update on Friday and it worked fine on Saturday on a short trip around town so I haven't been in my Prius that much since the update. But I have the premium nav head unit in my Prius.

 

Sounds like a hassle. Maybe you could try the Media Button Router app to intercept the bluetooth auto-play signal from the Prius so the phone doesn't try to start playing anything automatically. Maybe some media capable app on the phone locking up the bluetooth media audio and maybe this app could intercept it show something at that two minute mark. This app appears to still work on lollipop as some of the user comments are from S5 owners.

Media Button Router - Android Apps on Google Play

Reference:
Samsung Galaxy S4 | Page 2 | PriusChat

As for me, my lollipop S4 still works the same with bluetooth as before with the Prius Premium radio as I'm using Tasker to start the Beyondpod podcast app playing automatically every time the phone connects to the Prius.

 

I have a similar problem. There is obviously an issue. For me. when the phone is connected via Bluetooth, the car Bluetooth goes off one or two minutes after start up. Hence no internet-based features. I am in the process of making an appointment with the local Toyota dealer to see if there is any fix on that end. Perhaps it is a problem with the s4 and lollipop. I have Verizon.

Update 5/25/15: I called Verizon customer service. We did a factory reset on my s4 (save all your data/apps via an app that does that). I also relinked the phone to the car from scratch. After everything sitting overnight, the Bluetooth stayed on during a 20 mile trip and back. I hope that works for you.

 

Hi Mike. I am having the same problem exactly. I've contacted Verizon, Samsung and Toyota. Toyota customer service has been surprisingly great and has been in contact with me through this whole ordeal. This is a known issue for them with the upgrade to lollipop and they are collecting data to provide a patch in the very near future. Verizon too is collecting data and said that a patch is in the works for Verizon version of the S4. (3 weeks was the technician's estimate) There is really nothing else that we can do other than wait. Hooking up the phone up the old fashioned through an audio cable is an option to get by, but not a great one. I was actually thinking of downgrading my phone back to kitkat to get it to work. (factory reset will not work for very long, the problem continues)

 

So the problem of the s4 with Lollipop shutting down the Bluetooth on my Prius recurred. I called Verizon Customer Service and they told me that if I went to my local Best Buy and talked to the Samsung Experience folks in the cell phone area of the store, they would install a patch that fixes the problem. I went there. They installed it. I drove home and the Bluetooth stayed on in my Prius. That seems to be a solution. The Verizon person told me that they are also working on a Lollipop update that should fix it. They expect to have it ready in a few weeks.

I hope this is helpful to anyone who has the same problem.

 

I took my phone to the Samsung counter at Best Buy as suggested by leegart. They were able to fix the problem with my phone by re- updating the lollipop from their computer. The Samsung guy there told me that when updating over the air, there are often problems encountered. They were able to update directly from Samsung through a wired connection. The phone now works as before. Thanks for the suggestion!

 

Hi George. I'm glad there was a solution. Too bad it had to happen in the first place. I was afraid I was going to be stuck with no Entunes (Pandora) and no traffic info until I upgraded from the s4. The Samsung people at my local Best Buy were very willing to help and knew about the issue immediately. It makes one think about being loyal to Samsung and getting the s6 when my contact is up.

 

Well, I'm very sad to say that Best Buy solution worked for about 2 days. It has now stopped working. When it did work, it worked for the several hours of our trip and consistently for a 2 day period. At this point I guess I need to wait for Verizon to issue the patch and for Toyota to update their software. Thank you for the Best Buy suggestion. It did work for a bit.

 

Sorry!!! I don't think you have anything to lose by going back to Best Buy and having them install it one more time. The prior installation could have had a glitch. Anyway, you'd be no worse off than you are now. Mine is still working fine.

 

I have the same exact issues as you with my S4 and tried the same things. Just checking on if the S6 is still working for you without issues and/or if anyone else can confirm there's a fix that persists for the S4.

 

My S4 is with AT&T and I got the OTA Lollipop update about 2 weeks ago. All seemed fine until 6/19/15 when all of a sudden my USB wouldn't play and it is continually "Loading". Then I tried playing my MP3's from my phone through BlueTooth and the same thing, it's continually "Loading". The only thing that connects is the call/ receive function.
The dealer is supposed to take a look at it next week and they ordered a new USB connector for the car but I think it is wayyyy more than that.

 

I got a firmware fix today for my problems with my AT&T S4 w/ Lollipop at the Dealership.
for details see post # 10 at Nav system wonky in 2012 Prius | PriusChat
I didn't need a new USB connector, it was all firmware related.

 

The problem of the s4 shutting of the bluetooth has recurred. Sometimes unpairing and re-pairing the device helps for a few days but it keeps coming back.

 

Have you asked your dealer about T-SB-0051-13. It's a firmware update for the Display/Audio from 2.2.0 to 3.2.0.
It cured the problems I was having that were similar to yours.

 

Thanks. I will do that.

 

Your welcome, Hope it works for you as it did for me. I haven't had anymore problems after the update.