This one is simple,
- CM10: FiiO E7 doesn't work
- Stock: FiiO E7 works perfect
Just a heads up for those of us who currently have and use external usb dac's (sound cards) with our SGS3s.
Thats weird. I work for a company that sells fiio products. I also offer tech support. Why doesnt it work?
Sent from my SCH-I535 using xda app-developers app
No idea why but after plugging in the DAC there was absolutely zero activity. Not even the usual "usb device connected" message. It's as if the CM10 didn't have the drivers built in to handle the USB DACs. I wonder if there are any other devices running CM that could run the E7. As far as I know a stock SGS3 is the first android phone that actually supported the FiiO E7 right out of the box, which could mean that Samsung personally included the necessary drivers/libraries for that support.
Oh, ok so it's a CM issue. I misunderstood your first post. I personally like using the fiio E11 (Even though its not a usb DAC). It is my favorite amongst all the models I have. Mainly because i find it easier/quicker to use and adjust settings.. It helped a lot with my old HTC dinc because the volume on the audio out jack on that phone was horrible. Max volume on the phone and it wasn't loud at all! It was like having my ipod volume on the middle setting. The fiio amps changed that tremendously. I love the Fiio amps, they make music sound so amazing even with lower-end headphones. Whats your opinion the E7?
Do you have it directly connected to the SG3 via usb cable?
To be honest, i didnt realize such devices existed until recently, when I started working for a distributor.
Sent from my SCH-I535 using xda app-developers app
I got myself an E7 mainly because of it's amazing DAC. The volume isn't an issue for me since my headphones are quite sensitive but quality, noise-free audio on the other hand is the biggest reason. I would have gone for the E17 which seems to provide a bit more cleaner output but apparently only E7 works with the SGS3. I've had many android-based phones and none of them come even close to the E7. E7 produces the best virtual noise-free quality audio. Even at the lowest volumes there are absolutely no artifacts (SGS3's internal DAC goes haywire with artifacts & glitches at the lowest volumes).
It's connected directly through an OTG usb cable. No power adapters, nothing. FiiO E7 has it's own battery but can charge from the phone if it's running low. Personally I disable charging over USB to isolate the DAC from the phone as possible in order to avoid any potential noise generated by the phone itself.
Overall, I'm very satisfied with E7. The best $71 I've ever spent. It's quite unfortunate that it doesn't work with CyanogenMod based ROMs just yet.
Have you reported the issue to the CM developers? It most likely may have something to do with the kernel. I havent actually tried to use the E7 via usb directly to the phone. I will try tonight, if i can find the right cables at my house.
Sent from my SCH-I535 using xda app-developers app
I have an E7 also, and I REALLY wish it worked on CM10. I have scoured the web, but I'm still clueless on why it doesn't work, or how it even works on stock in the first place. The weird thing is that it seems like CM10 recognizes the E7 as a DAC, but doesn't do anything with it. When I run dmesg in BOTH stock and CM10, I get this:
<6>[ 8.753456] usb 1-1: new full speed USB device number 2 using msm_hsusb_host
<6>[ 8.834060] light_enable_store,new_value=1
<6>[ 8.909476] usb 1-1: New USB device found, idVendor=08bb, idProduct=2706
<6>[ 8.909507] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 8.909568] usb 1-1: Product: USB Audio DAC
<6>[ 8.909598] usb 1-1: Manufacturer: Burr-Brown from TI
<6>[ 8.932824] input: Burr-Brown from TI USB Audio DAC as /devices/platform/msm_hsusb_host/usb1/1-1/1-1:1.2/input/input14
yet it works in stock but not CM10
This is what it says on the fiio website:
<i>Ask: Can FiiO E7 or FiiO E17 work with Samsung Galaxy S3 via the USB interface? If yes , then how?
Answer: E7 can ,E17 can’t ,you can connect your Samsung Galaxy S3 through the micro USB interface and then connect to E7’ mini USB port ,and you need a OTG cable (mini usb to micro usb)to connect them together, finally E7 works. Taking about E17 connect with Samsung Galaxy S3 , the E17 shows lock at 16bit 48kHz, but there is no sound output with USB charge "on" or "off" ,as its working power is different from E7, we are sorry we now haven’t figured out a way to make them connect together become possible. Maybe you can pay attention to our following products, maybe E18 can, I’m sure someday you will find a product which can meet your needs, thanks.</i>
Lol
Sent from my SCH-I535 using xda app-developers app
I seem to be having exact same problem. On stock OS my Galaxy S3 can handle Fiio E7 perfectly but after I flashed latest CM10 nightly it does not recognize the DAC at all...
It looks like a missing kernel module or driver or something like that, as far as I can see... was anybody able to find any solution? I have international version of Galaxy S3, not the Verizon one. I'm not sure what the difference is, in regards to this particular issue.
whtvr said:
I seem to be having exact same problem. On stock OS my Galaxy S3 can handle Fiio E7 perfectly but after I flashed latest CM10 nightly it does not recognize the DAC at all...
It looks like a missing kernel module or driver or something like that, as far as I can see... was anybody able to find any solution? I have international version of Galaxy S3, not the Verizon one. I'm not sure what the difference is, in regards to this particular issue.
Click to expand...
Click to collapse
Same problem with AT&T Galaxy S3 for me.
Samsung based ROM's work.
AOSP based ROM's don't work.
I already found out, that the Moto G supports USB OTG, but would it support USB DAC's (digital-analog audio converter) ? If any Moto G owner owns a USB Dac or atleast something compareable like a USB headset or USB headphones, I'd be really thankfull if you could try it out.
The dac/headset needs to be plugged into the phone using a USB OTG cable.
Thanks!
Sent from my GT-I8160 using xda app-developers app
Works!! BUT:
I hooked an USB-OTG to Moto G, in there a Creative USB Soundcard with analog/digital output. Analog didn't work (must be the soundcard), but digital. I connected the digital out with a light cable to my RME environment and I could hear the music but with wrong frequency and crackled - but it works
Moto G has enough power to let the soundcard work.
[edit]
Hooked another soundcard in, this time analog works but wrong sample frequency and oversaturated, no option to control the volume.
Wow! This phone seems to be even more incredible value than I ever thought.
The problems that you mention sound pretty weird, though. The first thing that I'd suspect is the lack of special drivers for the soundcards on the Moto g. Maybe a simple DAC that doesn't need any special drivers would work better.
In fact, stock androids rarely work with any USB audio devices. But there's a app that includes special drivers and makes most USB-OTG enabled droids work with USB audio devices. You can the trial version (link in the description of the app) of it if you like:
https://play.google.com/store/apps/...=organic&utm_term=usb+audio+recorder+pro+demo
Be aware that the trial only works for 15 minutes and it doesn't play the usual audio formats. ( .flac works) If you try it, you should put a flac on the phone before installing the app.
Oh, and who knows how well this might work when CM and KitKat arrive!
Thanks a lot for your help.
Sent from my GT-I8160 using xda app-developers app
With the app it works, without stuttering and you can control the output volume, although there was an error warning at startup regarding main volume
I tried to record something, but hadn't enough time. First try was unsuccessful unfortunately.
shaftenberg said:
With the app it works, without stuttering and you can control the output volume, although there was an error warning at startup regarding main volume
I tried to record something, but hadn't enough time. First try was unsuccessful unfortunately.
Click to expand...
Click to collapse
Well, that's nice to hear. Maybe some Custom ROMs (Cyanogenmod in particular) will have better support for this without the app.
Anyway, I think I'm going to get this phone (Christmas is coming ). Usb audio support (atleast with the app) is crucial for me, so thanks for reporting that it works.:good:
One last thing though, what make and model were the two soundcards that you used for testing?
UnknownAX said:
One last thing though, what make and model were the two soundcards that you used for testing?
Click to expand...
Click to collapse
First a cheap Creative USB Soundcard, second a DJ-Audio-Player from EKS (www.eks.fi) which has its own soundcard per player.
Could you test this on the faux kernel that your running atm, Shaftenberg?
Most people who have tried it on the stock ROM have experienced the same glitches that you mentioned in your first post. On the other hand, there's also one report of it working fine, with the Google music player. The DAC is probably the biggest factor.
Anyway, I'm just waiting for the 16gb version to be available....
I tried 2 DACs. One was a CEntrance DACport LX flashed with the iPad firmware, and the other was a cheap off-brand thing (ELE EL-D01 on eBay). Both of them "worked", but I encountered the same issue with each: I tested both by playing a Youtube video, and the audio was not playing back at the proper sampling rate. The audio was slightly slowed down... as a result, pitches were slightly lower, and the audio lagged behind the video pretty significantly. If I had to guess, the audio was 48kHz, and Android was trying to play it back at 44.1kHz without resampling it first.
Why it was doing this, I have no idea: on a Nexus 4 running stock Jellybean with jacknorris' patch (which, AFAIK, doesn't pay attention to sampling rates but just assumes Android will handle that properly elsewhere), this works perfectly. However, it was fascinating/encouraging to see this work at all on the Moto G: it means that with stock firmware, not only does OTG/USB host mode work, and not only does the kernel have the stock Linux USB DAC driver compiled in, but the Android framework itself attempts to use the DAC, which is *definitely* not true with plain-jane AOSP.
One thing I was sad to see (which also seems to be true of a LOT of other Android phones that support OTG out-of-the-box) is that if I injected 5V from an external source into the USB power lines, the phone would NOT charge as long as OTG mode was engaged. Which means that, at least with the stock Moto G firmware, you can't both be in USB host most *and* be charging the battery at the same time. (Interestingly, the very first time you plug the power in, the phone says "charging", but it's quickly obvious it isn't. If you unplug and re-plug the power in after that, it will not show the lightning symbol on the battery any longer until you reboot the phone. Normal USB chargers continue to work without the OTG cable without requiring a reboot.)
-- Nathan
nlra said:
If I had to guess, the audio was 48kHz, and Android was trying to play it back at 44.1kHz without resampling it first.
Click to expand...
Click to collapse
That makes sense to me. But what would happen if we played a 44.1kHz track? It wouldn't have to resample then, would it?
Maybe that's why there is a report of it working with google music player...maybe he just happened to try it with a 44.1kHz track?
I'm pretty sure this will/can be fixed with a ROM / Kernel. Like USB OTG charging, it's just a matter of time (I hope). Both things have already been successfully enabled on many different devices.
Thanks for the info, luckily I'm not the only one showing interest in this.
It most definitely works with my Moto G and my FiiO E17 (connected via a generic OTG cable)
Trouble is, although it ALMOST worked, I got sporadic but impossible to listen to skipping/stuttering when using Poweramp or the native Google player app.
I finally found an app made by the same people who do the USB Audio Recorder Pro as mentioned by the poster, called USB Audio Player Pro (can't post the link, being a new poster, but a quick search for "USB audio player" gets to it)
...it costs over 5 pounds, and to be frank it is not the world's prettiest or richly featured player, but it certainly works and the output sound is great.
Anyway, just posting to let you know that it works, at least with my Fiio E17.
So here's some good news: after applying the official KitKat 4.4.2 OTA, OTG still works, USB DAC support still exists, and now it even works properly, at least for me! No more strange audio sampling issues: I could attach either one of my DACs and play the same Youtube clip without any difficulty! Audio was perfectly in-sync with the video.
-- Nathan
Did anyone manage to get USB audio to work with the Moto G play edition?
Has anybody found a way to enable OTG and charging at the same time? I genuinely enjoy listening to Moto G + FiiO E17 but it leaves me with low battery on the way home which is rather frustrating and makes me to swap charger/DAC during the day.
I don't mind putting unofficial ROM in as long as it doesn't require hardware mods.
jjacks said:
Has anybody found a way to enable OTG and charging at the same time? I genuinely enjoy listening to Moto G + FiiO E17 but it leaves me with low battery on the way home which is rather frustrating and makes me to swap charger/DAC during the day.
I don't mind putting unofficial ROM in as long as it doesn't require hardware mods.
Click to expand...
Click to collapse
I have taken ziddey's USB OTG kernel patch for the Nexus 4, which allows both for charging as well as USB OTG mode without an actual OTG cable, and I have compiled a new kernel for the stock Moto G 4.4.2 ROM, and it works great! The only thing is that you have to use a non-OTG cable...if it detects the OTG cable it will shut off the charging. So you will need a USB Y cable to inject a 5V power source to both your DAC and phone, and plug the phone into the Y cable using a standard micro-USB cable instead of an OTG cable.
If people are interested in this kernel, I can post it. You will need to unlock your bootloader to flash it.
-- Nathan
That is interesting. I would be happy to flash it. Is it safe operation? I flashed multiple windows mobile / windows phone devices but no experience with Android mods yet. Any downsides of custom kernel?
jjacks said:
That is interesting. I would be happy to flash it. Is it safe operation? I flashed multiple windows mobile / windows phone devices but no experience with Android mods yet. Any downsides of custom kernel?
Click to expand...
Click to collapse
You should read some of the other threads on how to unlock your Moto G bootloader and how to flash stock ROMs back, at the very least, before applying mine. I can't educate you on these matters here and there are other threads more appropriate for those discussions. Then take that knowledge and apply it to this. In this case, as long as you are using a stock Motorola ROM already (and not a GPE ROM!), you only need to flash one component: the kernel.
This kernel is completely identical to the stock Motorola kernel in every way except that it has ziddey's patch applied. So the only downsides would be:
1) because you have to unlock the bootloader, if you live in the U.S. at least, Motorola can legally void your hardware warranty, even if you have a hardware failure that cannot be linked to your unlocking of the bootloader. (Other countries' laws are different and Motorola may not be legally allowed to void warranties for bootloader unlocks where you are at.)
2) If an OTA update is pushed to your phone, I believe the kernel will be replaced with a stock one again, and this will stop working. Either that, or because you are running a custom kernel or an unlocked bootloader, perhaps OTAs won't be pushed to your phone, or if they are, they might not install. I have not tested this or read up on this myself as I generally detest OTA updates outside of my control, and prefer to flash my devices myself on my terms when I'm ready to do so.
You can read about ziddey's USB OTG patches that he developed (with the help/inspiration of CaptainMuon) here: http://forum.xda-developers.com/nexus-4/orig-development/usb-otg-externally-powered-usb-otg-t2181820
The only real difference between how this works on the Nexus 4 and how this works on the Moto G is that, as I explained previously, on the Moto G, there is something in hardware that prevents the phone from accepting a charge if it detects that you are using an OTG micro-USB cable, whereas the Nexus 4 doesn't care if you use an OTG cable or not because pin 5 on the Nexus 4 is not actually wired to anything internally. On the Moto G, there is even a slight cosmetic quirk: if you try to inject 5V power to the phone through an OTG cable, the first time that you plug it in after a fresh reboot, it will say that it is charging after you plug the cable in, but it actually isn't (battery will continue to deplete). And if you unplug the cable and plug it back in, it will no longer show the "charging" symbol, until you reboot the phone again. If you plug in a regular micro-USB cable, though, it will both show charging as well as actually take a charge.
Another thing to be aware of is that there are two different releases of KitKat 4.4.2 that Motorola has released for the G (they released an updated 4.4.2 ROM that fixed a couple of bugs after its initial release), but as far as I can tell, they have so far only released the kernel sources for the original 4.4.2 ROM and not the updated one. So I have only managed to build a kernel for the original 4.4.2 update for the Moto G. I have not tested this, but it's *possible* that this kernel will work just fine with the later 4.4.2 ROM. You are welcome to try it; you won't harm your phone by doing so and can always flash the factory kernel back if it doesn't work or has problems. This kernel likely won't work with any 3rd-party ROMs or with the Google Play Edition ROM (which doesn't support USB DACs anyway, sooo no point in using that one, at least if you care about USB audio which you obviously do). Motorola has not released any kernel sources for 4.4.3 or 4.4.4 yet either, so you should stick with 4.4.2 for now. If this kernel does not work with the later 4.4.2 release, then you should be able to downgrade your system image to the older 4.4.2 ROM and use this kernel with that.
The two 4.4.2 releases on the Moto G (excluding the GPE ROM) are marked by their kernel versions. The first 4.4.2 kernel is versioned as KXB20.9-1.8-1.4, and corresponds to the U.S. retail 172.44.4 ROM version, among others internationally. The second 4.4.2 kernel is versioned as KXB20.9-1.10-1.24-1.1, and corresponds to the U.S. retail 174.44.1 ROM version, among others internationally. It is the source for the first kernel that I have access to.
You may download my kernel from here: http://www.nconx.com/~nathan/motog/boot_motog_KXB20.9-1.8-1.4_OTG_charge.img
After you have unlocked the bootloader via Motorola's site and mfastboot, enter Fastboot mode on your phone again, and then flash the kernel to the phone with mfastboot (the Motorola version of fastboot) the same way that you would flash a stock Motorola kernel (see this post, step 3b: http://forum.xda-developers.com/showthread.php?t=2542219), but substituting in the file name of my kernel instead:
Code:
mfastboot flash boot boot_motog_KXB20.9-1.8-1.4_OTG_charge.img
Reboot your phone, plug it into your DAC + 5V power source (again, using a normal micro-USB cable), and enjoy battery charging while simultaneously connected up to your external DAC.
Good luck,
-- Nathan
Great. Thanks a lot. I will give it a try when I find some spare time
My Moto G works with Creative X-FI DAC
My Moto G runs Kitkat.
OTG cable is connected between Creative X-FI Dac and Moto G. Then Creative device's optical output is fed to the Logitech speaker with optical input. Sound with this setup is much better and awesome.
My Moto G Works w/ Fiio E07K
Running Android 4.4.4
Moto G (LTE) > USB OTG cable > Fiio E07K USB Cable > Fiio E07K > headphones
:victory:
nlra said:
I have taken ziddey's USB OTG kernel patch for the Nexus 4, which allows both for charging as well as USB OTG mode without an actual OTG cable, and I have compiled a new kernel for the stock Moto G 4.4.2 ROM, and it works great! The only thing is that you have to use a non-OTG cable...if it detects the OTG cable it will shut off the charging. So you will need a USB Y cable to inject a 5V power source to both your DAC and phone, and plug the phone into the Y cable using a standard micro-USB cable instead of an OTG cable.
If people are interested in this kernel, I can post it. You will need to unlock your bootloader to flash it.
-- Nathan
Click to expand...
Click to collapse
Would you be interested in building a compatible kernel for 4.4.4? Is the source available? My Moto G is brand new pre-installed with 4.4.4. so no option to use your 4.4.2 kernel. I would really appreciate the help - I have a project that requires me to be able to charge and host simultaneously.
Also, I'm fine with flashing an alternate ROM with source available, such as CyanogenMod -- anything to get OTG + Charging working. Any advice is appreciated.
Thanks,
samwathegreat
Is there anyone who have tried fiio dac with your Lenovo P2? I have a fiio k1 dac and it doesnt work with my phone but works well with my old samsung j7(2015).Does changing my stock rom help me with this problem?
For me i have managed to get it to work a few times. Reconnecting multiple times and it would work 1 out of every 15-20 times. Very unreliable and I'm afraid i'm damaging the phone in the process.
I just use allcast to stream music to my laptop which then outputs to the dac as a workaround.
Ecto5 said:
For me i have managed to get it to work a few times. Reconnecting multiple times and it would work 1 out of every 15-20 times. Very unreliable and I'm afraid i'm damaging the phone in the process.
I just use allcast to stream music to my laptop which then outputs to the dac as a workaround.
Click to expand...
Click to collapse
Thanks a lot for your reply.I thought this problem was only with my P2. I have tried as you said.Reconnected multiple times and usb audio player pro plays the music at a very loud volume enough to damage the headphone and then all of a sudden the app crashes.Same case with Neutron music player.Poweramp detects the dac and plays song but no sound is heard.I think any custom rom can help me with this problem
P2A42 (hardware p2c72) here same problem only charging Fiio X3 first generation, used to work on OnePlus one and Moto G third generation
Sent from my Lenovo P2a42 using Tapatalk
Reporting again.
Just flashed validus oreo and fiio X3 first generation works like a charm
Sent from my Lenovo P2 using Tapatalk
I'm using Lenovo P2 unrooted with Stock.
My Fiio E07K didn't work but I could try some others and the Audioquest Dragonfly as well as the Cyrrus Soundkey work like a charm. The Oppo PM-1 didn't work either.
I'm very happy with my new Soundkey...
I'm also using unrooted Lenovo P2 with Stock (P2a42_S224_170725_ROW) .
I confirm that my Fiio Q1 works like a charm...
i havent faced any problem till now regarding the connection...
Stock ROM, FiiO E18 KUNLUN fully works.
Hello everyone, I have a very very annoying issue with the headphones + amp / DAC connected with the mobile phone ( fold z 4 )
I have little hopes to find a fix, but it's worth trying.
So, let's explain what is about.
I'm using the headphones Denon D9200 ( wired ) + the Signature amp / DAC connected to the mobile phone.
micro iDSD Signature by iFi audio - Supercharged desktop and transportable USB DAC and headphone amp
Our iDSD Signature Dish Supercharged desktop and transportable USB DAC and headphone amp that will take your tunes to the moon and back.
ifi-audio.com
https://www.denon.com/en-us/product/over-ear-headphones/ah-d9200
After listening some time on YouTube, the signal from the Signature is gone and the mobile phone speakers are active, not the headphones
I tested on different mobile devices. Here are the results.
Samsung Galaxy Tab S8 ultra : after less than 5 minutes, same issue.
Android 13, One UI 5.0
Samsung Galaxy Z fold 4, same issue.
Android 13, One UI 5.1
Google Pixel 2 XL, no issues
Android 8.1, rooted phone, but the sound quality is far far away behind , from everything else I used as mobile device.
Low volume, no matter I do, and it sounds like I'm using some cheap amp / DAC device
IPad Pro 12.9 ( tested on 3 different devices, 2018, 2020 and 2021 )
No issues at all. The sound quality and the loudness level is the best I've ever heard with the Signature + Denon d9200
That's a mistery for me. I thought, the Signature is doing the job, not the mobile device or the OS
USB C is on all devices ( iPad pro, Android phones, Android tablet )
PC Windows 10, no issues at all
Laptop Windows 10, no issues at all
Samsung Galaxy note 10 and Note 9 ( didn't check the Android and One Ui version )
Same issue
It's hard to say but it might be Android ( latest versions ) the culprit.
Google Pixel 2 xl is using Android as well but some older ( 2018 ) version and with custom ROM + custom kernel
Hopefully, someone here who read this post, with the Signature and some newer Android devices, could give me some advices
Thank you
LE : from the Signature to the mobile devices, it's a cable USB A with an OTG adapter to USB C
That's the only way I can connect it with the USB C mobile devices.
Just did another test, for about one hour with Samsung Galaxy Note 10 plus
Android 12, OneUI 4.0
Not a single issue.
Android 13 is the culprit. Not the cables, not iFi Signature.
With Android 13, they added the headphones icon when headphones are connected and the volum button is used
Android 12, classic, without the headphones icon
I wonder what exactly could be done about this
There must be a way to fix it
Any advices, guys??