Brand new Galaxy S4 MK2; Hyperdrive Bluetooth issues

Search This thread

xaero252

Member
Oct 30, 2009
40
5
I had an unlocked S4, which took an unfortunate dive and ended up non-functioning. I used my phone insurance to acquire a new (unfortuantely) updated phone running the full MK2 suite. First order of business was a root & install of SafeStrap, followed by installation of Hyperdrive to Rom Slot 1. I use my phone with my 2013 Subaru XV Crosstrek's bluetooth handsfree for both calling and media playback, and I use this feature EVERY SINGLE DAY. Unfortunately, not any more. I cannot get more than 15 seconds of connected time over bluetooth with the phone. I've tried multiple wipes. I'm fairly certain the issue doesn't exist on stock rom; so I may end up just customizing a stock rom in slot 1 by removing absolutely everything and building it from the ground up, since I don't have to use the (apparently buggy) mk2 modules.

Edit:
I'm seriously considering selling this phone and getting something more friendly to modding, this is a repeat of the Droid Bionic at this point.
 

decaturbob

Senior Member
Mar 30, 2011
2,492
842
Decatur
Is there a question here? Did the stock rom blue tooth work ok?

Sent from my SCH-I545 using XDA Premium 4 mobile app
 

xaero252

Member
Oct 30, 2009
40
5
And this is why I shouldn't hastily write a post.

Yes there should be a question:

What can I try to fix the issue of frequent (alarmingly) bluetooth disconnects?
What kind of logging can I do to try and help provide developers with the information to fix this?
Anybody else have this problem? Any experience fixing it?

If I can't get this fixed, I have no choice but to move to another phone. Preferably at Verizon's expense.


Even more irritating: The phone is listed as compatible with the Crosstrek. I'm going to test that it works fine using the stock rom and bluetooth, and factory resetting my head unit.
 
Last edited:

xaero252

Member
Oct 30, 2009
40
5
Did you install the MK2 modules after installing Hyperdrive?

Yes. Originally when I installed it WiFi and Bluetooth didn't work at all. I realized quickly my error was the lack of installing the MK2 modules. I wiped and installed again, this time ensuring the MK2 modules followed the rom install. I got everything set up the way I like to, and began day to day use of the phone. Since then I have had the bluetooth connectivity problems I described above.
 

xaero252

Member
Oct 30, 2009
40
5
Bluetooth is rock solid on stock. I'd really rather not have to play this game where I can install stock or.... basically stock... and now that I'm locked kernel and radio wise if I have issues further with OTAs I'm just as stuck with a near useless phone as I was with my Bionic
 

s.whiplash

Member
Dec 7, 2007
49
8
I'm afraid that I don't have anything else for you, except try a different ROM. Bonestock or Eclipse? Bluetooth works pretty good for me with multiple headsets and vehicles. My only issue with Bluetooth is not all the apps will pass metadata to my truck. This happens with all 3 of these ROMs and I think it is a TW 4.3 limitation.

Are you doing anything to boost the Bluetooth volume? With my previous phone I boosted the Bluetooth volume via some hacks and my truck would not like it.

I know what you mean about having a locked down phone. I came to the S4 via a warranty replacement from an unlocked S3 running SlimBean and SlimKat.The problem is that most of the new phone that are coming out all have bootloader hurdles.
 

myb120

Member
Jan 21, 2014
15
4
I'm having the same issue with my SGH-M919 (T-Mobile) running rooted stock TW. I've documented my issues and a few LogCats here. Have you figured out a solution?