B&O Hi-fi Plus on H830 - T-Mobile LG G5 Questions & Answers

I'm on the fence about getting the V20, and I currently have a T-Mobile G5. The only real reason I see myself wanting the V20 is the quad dac, everything else is basically the same as the G5 (minus the second screen).
If the Hi-fi Plus was able to work with the H830, I don't think I'd get the V20. I've looked around for an answer but it seems no one has discussed this yet. So my question is, has anyone looked into what causes the incompatibility between the H830 and the DAC module? Is it a simple software thing, such as the build.prop or mixer paths? Or is it some sort of hardware check that prevents it from being used?
If anyone has the means to test this, that would be great!
If there is a simple software mod that could be done, then the DAC could be usable on the H830.

anyone using HiFi Dac module on their H830?

I do believe it is a hardware issue. But, that being said, you can use a C to C cable, and from my understanding it does work that way.

Related

[Q] USB OTG DAC / headphone amp w/ One XL

Hey, I had a good search and found a lot of general info on this but I couldn't find anything specific to our device, so here goes:
Has anyone had any luck using a USB headphones amp / DAC with their One XL via USB OTG? I'm looking specifically at the FiiO range but would love to hear of any others that have been confirmed to work. I'm hoping for a very confident "it'll probably work" before I spend $++
I'm running the latest AOKP 4.2.2 release preview (Rohan). I have got various USB peripherals working via a $5 OTG cable, including a keyboard & mouse and memory stick [StickMount didn't work but I was able to access the contents under /mnt/usbdisk just fine with ES File Explorer].
I'm happy flashing different kernels but don't really have experience manually editing linux system files.
I've read / skimmed most of this monster thread on head-fi, and the consensus seems to be that YMMV depending on the two devices, USB DAC and phone, used: http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1320
I also have a Nexus 7 that I would be far less concerned about breaking in the name of research, and I also happen to own the Logitech G930 gaming headset that some people have reported success with with Android, so I might have a crack getting that to work before I buy anything else.
Cheers!
TrancerSte said:
Hey, I had a good search and found a lot of general info on this but I couldn't find anything specific to our device, so here goes:
Has anyone had any luck using a USB headphones amp / DAC with their One XL via USB OTG? I'm looking specifically at the FiiO range but would love to hear of any others that have been confirmed to work. I'm hoping for a very confident "it'll probably work" before I spend $++
I'm running the latest AOKP 4.2.2 release preview (Rohan). I have got various USB peripherals working via a $5 OTG cable, including a keyboard & mouse and memory stick [StickMount didn't work but I was able to access the contents under /mnt/usbdisk just fine with ES File Explorer].
I'm happy flashing different kernels but don't really have experience manually editing linux system files.
I've read / skimmed most of this monster thread on head-fi, and the consensus seems to be that YMMV depending on the two devices, USB DAC and phone, used: http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1320
I also have a Nexus 7 that I would be far less concerned about breaking in the name of research, and I also happen to own the Logitech G930 gaming headset that some people have reported success with with Android, so I might have a crack getting that to work before I buy anything else.
Cheers!
Click to expand...
Click to collapse
After you skimmed some one posted a master update:
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1785#post_9215106
I want to believe that most of the diy dacs will work because 90% use a PCM2707 to talk to the usb. Then either they use the pcm2707 internal decoder, or feed the is2 signal from the pcm2707 to a higher quality dac

Any experience with a MTCD unit on a 2013 Mazda CX-9 GT (premium audio)?

Hello,
I am the new owner of a 2013 Mazda CS-9 GT with premium (Bose) audio. I had a MTCD unit on my old vehicle and I would love to do the same for this one. Custom units do exist for my vehicle, but I am wondering about the integration of the unit with the rest of the system, more so knowing that Bose likes proprietary things which tend to be incompatible with everything else. (At least this is how it used to be some 10+ years ago: one of my old cars had a Bose system and it was a royal pain to modify anything, including but definitely not limited to low-impedance, non-standard speakers and DC component on the audio line to power on the amp.)
Anyway, I was wondering whether anybody has any previous experience with such systems, either good or bad. I am basically wondering whether an MTCD head unit will play nicely with the rest of the audio system.
In somehow unrelated matter, does anybody have any experience (good or bad) with using the factory installed backup camera with such a unit.
Last but not least, this would be my first vehicle with the CAN bus exposed to the head unit. Are there any pitfalls I should be aware of regarding the CAN bus integration?
Information and advice are much appreciated. Many thanks in advance!
If they make a CANBus adapter for your configuration, it's pretty much plug and play.
Sent from my SM-G935F using Tapatalk
sbruda said:
Hello,
I am the new owner of a 2013 Mazda CS-9 GT with premium (Bose) audio. I had a MTCD unit on my old vehicle and I would love to do the same for this one. Custom units do exist for my vehicle, but I am wondering about the integration of the unit with the rest of the system, more so knowing that Bose likes proprietary things which tend to be incompatible with everything else. (At least this is how it used to be some 10+ years ago: one of my old cars had a Bose system and it was a royal pain to modify anything, including but definitely not limited to low-impedance, non-standard speakers and DC component on the audio line to power on the amp.)
Anyway, I was wondering whether anybody has any previous experience with such systems, either good or bad. I am basically wondering whether an MTCD head unit will play nicely with the rest of the audio system.
In somehow unrelated matter, does anybody have any experience (good or bad) with using the factory installed backup camera with such a unit.
Last but not least, this would be my first vehicle with the CAN bus exposed to the head unit. Are there any pitfalls I should be aware of regarding the CAN bus integration?
Information and advice are much appreciated. Many thanks in advance!
Click to expand...
Click to collapse
As I remember .... my cx5 can-bus was not prepared for bose.
Anyway why don't you ask to the seller?
Because....if exist any bose support is by means of any can-bus decoder.
Enviado desde mi D6603 mediante Tapatalk
verkion said:
If they make a CANBus adapter for your configuration, it's pretty much plug and play.
Click to expand...
Click to collapse
ikerg said:
As I remember .... my cx5 can-bus was not prepared for bose.
Anyway why don't you ask to the seller?
Because....if exist any bose support is by means of any can-bus decoder.
Click to expand...
Click to collapse
It is great to know that proper support for the CAN bus is all that is needed; things have changed quite a bit since I last dealt with premium audio. Thank you very much guys. I will make sure that the CAN bus adapter is properly programmed for my setup.
I have dealt in the past with the seller I have in mind and they are pretty responsive and knowledgeable (as opposed to most on Aliexpress/eBay/etc.) and I did ask them. I was looking here for personal experience, so thanks again for that!
Hello,
I have received the unit with CAN bus adapter and everything, and advertised as working with my vehicle (though also see below).
Unfortunately I am having trouble convincing the unit to properly turn on the amp. No matter what I do the amp refuses to produce audio; I can hear instead really loud beeps at approximately two a piece per second (theft-deterrent feature maybe?). Any idea whether this is a matter of CAN bus options or goes deeper than this?
For what it is worth, my vehicle is wired for factory navigation (though I do not have the navigation module installed). Could this make a difference?
I am hoping that somebody encountered this problem already and I could use any advice on the matter. In essence I would like to figure out whether the problem is solvable in software/settings or I should simply return the unit. Advice is much appreciated.

USB C to Headphone Adapter is Spotty

My headphone adapter from Google does not consistently work. What's the deal?
I plug it in and usually gives me the notification for different USB options: charge, supply power, transfer files, transfer photos, MIDI
But sound just plays through my speakers or calls come through the ear of the phone.
Any ideas? Is there some secret to it that I'm not getting?
Is this the included adaptor or one that you acquired elsewhere?
It is the adapter that came with the phone from Google.
Sounds like a defective cable. What I'm unsure of is USB-C was suppose to be a new "standard" but Google changed pins or something preventing other adapters from working. Really piss poor. Just sent back my second after market adapter that did advertise pixel2 compliant. Nope.
MLT2004 said:
What I'm unsure of is USB-C was suppose to be a new "standard" but Google changed pins or something preventing other adapters from working. Really piss poor. Just sent back my second after market adapter that did advertise pixel2 compliant. Nope.
Click to expand...
Click to collapse
You don't say which after market adapter you got.
Google is using the standard but requires DAC which meets the standard. If you get a cheap adapter, the chances are they don't have the necessary DAC chip in them or a cheap version which doesn't work.
One of many articles about it.
https://www.androidauthority.com/3-5mm-audio-usb-type-c-701507/
Google will have them back in stock shortly for $9 w/free shipping.
https://store.google.com/us/product/usb_c_headphone_adapter
Another solution would be to get a BT to 3mm device which allows you to use BT on your phone to any 3.5mm plug devices. I have been using a several of these for a couple years to hook up my TV and other devices which use the 3.5mm jack to use with my really good BT headphones.
Yes, I can confirm that the HTC adapter works with the Pixel 2. However, aftermarket adapters designed for Motorola phones won't because Moto aren't following the USB-C digital standard there (and they key is "digital", which is why, as the post above says, the adapter needs a DAC in it).
I have the same problem and apparently I am not the only one.
I heard that people got 2 or 3 replacements and the problem persists. It is probably software related.
I will see if with the Moshi splitter I have the same problem.
Has anyone fixed this? I'm on my second pixel 2xl and have 3 Google adaptors that work intermittently
Spotty is too kind
The designed in difficulty Google lovingly put into the Pixel 2 surrounding that oh so special USB-C socket, that lonely and inadequate solitary physical output port, to get music to output through there is ridiculously difficult to next to impossible. To Google's credit they have _tried_ to help when I've called - repeatedly - in the past 6 months but it's just simply not designed to send music out that sole output socket. Which is stupefying trying to grasp how those brilliant Mtn. Viewers could have thought such a design a 'good idea.' All previous versions of android allowed me to 'choose' output to fill-in-the-blank - device speaker, b-t, or the cable/port. With the design push err shove toward b-t headphones or devices that then send your signal to your sound system/speakers they evidently just decided no one would want to send music through the cable. That fact is, as I have indicated, perplexing not to mention maddening. It's also a glaring design flaw. The short of it is it will only work if it's plugged into some device that I guess is factory designed to work with Oreo. Then and only then will the Pixel 'see' that resource as an option to play the signal - and it works automatically. Physically choosing to send your music out that USB-C port & out your cable is not an option, according to Google tech support who I finally called after months of frustration and finally giving up on finding resolution online on my own.
Maybe there's something I'm not understanding, but it's certainly not true that music output only works "if it is plugged into some device that is factory designed to work with Oreo". Mine plays music fine through a HTC adapter that predates Oreo by about a year, or a Dragonfly Red portable USB DAC/amp that predates Oreo by a couple of years and isn't even USB-C. And conversely the Google adapter, which I infer you are having problems with, surely was designed for Oreo since it was released with phones that have never had any earlier version of Android.
Now if you are saying that the OS doesn't allow you to send sound out through the socket when it doesn't identify a device capable of handling it as connected, well OK. But would a previous version of Android allow you to route audio through the USB socket if there was nothing connected to it (or nothing more than an OTG connector)? I never tried that (for obvious reasons) so don't know. But I do know it also didn't allow you to route audio out of the headphone jack unless there was something in that making the correct electrical connections. So it seems to me that the main difference is that this is purely digital audio out, so a digital handshake replaces the electrical connection. But as I say, maybe I'm missing something you are trying to say?
I seriously got fed up with the USB-C to 3.5mm jack playing music out loud in my office is no bueno. I decided to buy a FiiO BTR1, it works while charging so ill just leave it plugged in at work.
Update to 2020 January 7. I just bought a new headphone for my Pixel 2 and it won't recognise it with the dongle I got with the phone. I read it was a problem known by Google in 2017 and a fix would happen on a software update. I've also heard masses saying the cheap dongle won't work and Google saying they would replace it. I've also tried a high quality Apple dongle and it didn't work. I'm on Android 10.

Will this phone have OIS? will it support normal hdmi out?

Something that was sorely missing from the OnePlus 5 was OIS.
Can anyone confirm if its got it.
Edit: yes it does
Second question I think I know the answer to but thought I'd ask.
I think no for both, but wait for launch day, who knows?
EDIT: OIS is most likely confirmed. (German Amazon leaked specs) But no HDMi sadly.
_MartyMan_ said:
I think no for both, but wait for launch day, who knows?
EDIT: OIS is most likely confirmed. (German Amazon leaked specs) But no HDMi sadly.
Click to expand...
Click to collapse
Good news about OIS, the HDMI out of a killer, but displaylink will still work.
Are you sure about no HDMI out? Isn't that something that Android supports by default and since 1+6 will jave usb c I see no reason why it should not support?
Sent from my SM-G950F using Tapatalk
doctor78SI said:
Are you sure about no HDMI out? Isn't that something that Android supports by default and since 1+6 will jave usb c I see no reason why it should not support?
Click to expand...
Click to collapse
No I'm afraid not, the last device to be able to use HDMI directly from usb-c was the HTC 10 to my recollection, since googles pixel doesn't use direct usb-c to HDMI, all devices are now the same.
Display link technology is a dock with its own chipset, meaning it can render for the device.
I have a thread in the one plus 5 forum because there simply was no way to use a wired solution, I've had the one plus since midnight on its launch day, the general idea was that HDMI out was not possible, I tested the display link devices I've got and it works.
You need an app but it works well.
Hopefully on the next batch of phones we can use HDMI directly, but I'd assume not.

Oneplus Nord wired video output, firmware blocked?

Hi all,
At present it seems impossible to output video with a cable on the Oneplus Nord (OOS11). In my research I found out:
_MHL does not work
_Slimport does not work
_USB 2.0 protocol instead of 3.1 ; it seems this choice was made to favour warp charging.
_Force desktop mode works well with keyboard and mouse on device screen.
So my understanding is that the hardware is there to make this work but firmware has MHL and slimport locked. I suppose the limitation is to push advance use towards more expensive models.
Q: Is it possible to unlock MHL or Slimport via a Magisk module or other tweak?
Thanks
Freesoup said:
Hi all,
At present it seems impossible to output video with a cable on the Oneplus Nord (OOS11). In my research I found out:
_MHL does not work
_Slimport does not work
_USB 2.0 protocol instead of 3.1 ; it seems this choice was made to favour warp charging.
_Force desktop mode works well with keyboard and mouse on device screen.
So my understanding is that the hardware is there to make this work but firmware has MHL and slimport locked. I suppose the limitation is to push advance use towards more expensive models.
Q: Is it possible to unlock MHL or Slimport via a Magisk module or other tweak?
Thanks
Click to expand...
Click to collapse
I was able to dig this thread on XDA that touched on this already https://forum.xda-developers.com/t/dev-wip-enabling-mhl-in-kernel.2262682/
It's a bit old though (latest post was 2013).
Since that time it looks like it got simpler. The chip can do it so it's probably an On-off command somewhere.
Anybody familiar with this?

Categories

Resources