* HELP * Can't connect HTC One M7 to external DAC

[Kouzelna]

Hi, thanks for your help.
 
I'm trying to use my HTC One M7 as a player, to send to my DX50 and then to my amp.  I have an OTG cable, but it's not seeming to work.  
 
1.  DX50 has the latest firmware as of today, and is set to DAC Mode (Windows)
 
2.  OTG is connected to the HTC, and then via cable to the DX50
 
3.  I did test the OTG independently with the HTC using a mouse, and it worked fine
 
I can see people have done this with other DACs, but for some reason this is not working for me.  Any ideas?  Regardless of what I do, when I play the music file it simply comes through the phone's speaker, instead of sending the signal to the DX50.
 

 

[cel4145]

I don't think the DX50 is designed to take input from Android phones. Research and ask questions in the DX50 thread: http://www.head-fi.org/t/679473/the-ibasso-dx50-thread-latest-firmware-1-9-4-january-24-2016

 

[Kouzelna]

Hey, thanks for the thread link!  I'll ask there.  I think you're right.  The crap part is that the options for USB are Storage - DAC (Windows) - DAC (Mac/Linux) - Charge Only.
 
When I choose "Mac/Linux" which I assume would cover Android... it won't let me choose it.  Brilliant.

 

[cel4145]

Android phones and connections to DACs is and has been problematic ever since USB OTG audio was developed. Some phones work with some DACs, some with others, and some DACs and phones not working at all with any. Some phones require a separate app to get it to work. And then it worked with some Android release versions on some phones, and not others, even dropping the capability with a newer version with some phones.

I don't believe that DX50 originally worked as a DAC with Windows and MAC when it first came out; they had to work on that in firmware releases. I would not have any expectation that they will/would be able develop the firmware to work with Android phones given all the problems with USB OTG audio and Android. I'd blame it on Android and the phone manufacturers who build the hardware and modify vanilla Android, not iBasso. In fact, given how problematic USB OTG audio has been, I'd be surprised if iBasso is working on that at all. Doesn't seem worth the effort given that phone manufacturer support has been so inconsistent.

 

[Kouzelna]

OK, all that makes sense.  Certainly my experience with other aspects of Android.  Overall, I like it better than iOS because it's more customizable.  But the updates for apps and especially the OS or interface break the functionality of the phone/app more often than not, and that's no fun.  Google chose to force update my Android, couldn't stop it, and the result was the dreaded HTC One purple camera.  That was 2 years ago, and guess what?  Never an update from either Google or HTC.  When I called they said it was a hardware issue, and now the camera read more "accurately".  Maybe, but it worked just fine before their software update, and a simple patch to bring it back to functionality would sure've been great.

 

[cel4145]

No further update is HTC's fault. Google can't make manufacturers refine and push forward an update for their phones.

Look into a custom ROM for your phone. The M7 is popular enough that most likely someone has developed on that solves your problem: http://www.xda-developers.com/

 

[Kouzelna]

I hear you.  Both of them dropped the ball.  HTC came out with a Sense update instead, that disabled the mic so you can't make calls anymore.  I learned my lesson the first time, and I looked that up to see if yeah, it fixed the camera problem, but no, it didn't and it also basically bricked your phone.

 

[cel4145]

I've had good luck with the Samsung Galaxy series. No major hiccups with any updates.

 

[Kouzelna]

I have a Galaxy tablet, and also, works perfectly.  The HTC One M7 worked perfectly too, and still does 3 years and many drops later... except the camera.  
 
HTC did offer to fix it, but since it was out of warranty they wanted $100.  I decided I could live without the camera.  I then called a year later, and they said they were now fixing that problem free of charge, and could also perform other improvements (change the battery for an extra charge, fix the power button, etc.)
 
I was packing the box to send it in when I just out of boredom read "the fine print."  Whadya know, the very last line was that they relocked the phone to the original carrier.  Well, mine's originally an AT&T phone, but I bought it unlocked because I use it overseas.  I called HTC and asked if they could forego relocking it.  The guy said "sure, no sweat" but I asked him to absolutely make sure.  I don't have an AT&T account, and could see them balking at unlocking it for me because of that.  Sure enough, he checked and they do, indeed, relock the phone.  That would basically give me a phone I can't use.
 
So, again, I have a camera that can't take photos at night or in low lighting.