Develop Bugs

[Q] DAC or sound chip/card in Samsung Galaxy S II UK version

First thread here,
I wanted to know the DAC or sound chip/card in the UK version of the Samsung Galaxy S II. Is it the wolfson on yamaha dac? I'm currently on o2 and i'm due for an upgrade. The iphone 4 32GB is just too expensive and the 16GB is too small for my music collection with no option to expand the memory (just so stupid).
Does the version of the GSII vary with network as well?

The GS2 is the same on every network with maybe a few software tweaks. O2 and Vodafone have just changed the bootscreen and added some wallpapers (I hate to see what Orange are going to do). You can easily flash a stock ROM via Odin though.
Check out this thread for answers to your audio questions http://forum.xda-developers.com/showthread.php?t=1053978

steve228uk said:
The GS2 is the same on every network with maybe a few software tweaks. O2 and Vodafone have just changed the bootscreen and added some wallpapers (I hate to see what Orange are going to do). You can easily flash a stock ROM via Odin though.
Check out this thread for answers to your audio questions http://forum.xda-developers.com/showthread.php?t=1053978
Click to expand...
Click to collapse
thanks a lot

Coming from an i8000 like you I have found the sound quality to be just as good..... but the amplifier is definitely not as powerful which is a little disappointing. It can be increased somewhat with software preamp in programs like poweramp but it starts distorting because the levels are preamped too much.
So if you have sensitive headphones its not such a problem or you are using an external amplifier.
I much prefer this phone in just about every way except for two areas, one being the sound output for headphones and the other is I'm only getting one day out of the battery instead of a couple with the i8000 but I do tend to play round a lot more because there is more to play with

[Q] Sound distortion issues with certain headphone types in T-mobile Galaxy S4!

Hi! I am new to xda forums and require some advanced help for my T-mobile Galaxy S4. I am sure this must have been brought up previously as there is a completely other thread for this issue regarding sound distortion when using non-Samsung headphones. (See: http://forum.xda-developers.com/showthread.php?t=2258831
The issue is affecting almost all variants of the Galaxy S4 where there is some sort of problem with lower impedance headphones. At higher volumes, crackling and distortion of sound and bass become almost unbearable. However, this issue does NOT affect the regular in-box Samsung headphones, as well as other lower quality headphones. The higher-end, audiophile headphones are usually the ones affected. I have a pair of Klipsch S4a headphones designed specifically for android phones, and it is impossible to listen to music with them. When I use the regular headphones in the S4 box, they work fine without any problem. Interestingly enough, my Klipsch headphones work perfectly in my old Galaxy S3, as well as my HTC phones. So this is obviously a problem with Galaxy S4 only. I even plugged in my headphones into several working models at T-mobile store/Costco and all had the same problem. But my headphones sounded perfectly fine in other devices.
Now if you have clicked the above link that talks about the issue, it seems that international S4's and GT-I9505/GH-I337 phones got the fix several weeks ago via an update from Samsung that changed their kernel versions. AT&T also received an OTA android update that fixed the audio headphones issue earlier this month (http://www.christianpost.com/news/galaxy-s4-android-4-2-2-software-update-corrects-earphone-distortion-issue-101838/ . Now the problem is, is that both T-mobile and Samsung refuse to acknowledge this issue. I have tried contacting tech support for both several time, with T-mobile saying they are unaware of the issue and no update is to be released for it, and Samsung simply saying "we recommend using your Samsung headphones that came with the device". Unbelievable considering there are official fixes for this that have gone to International users and North American AT&T users. I don't know what to do. I am guessing 99% of T-mobile users just use the headphones in the box so T-mobile/Samsung don't really care to address this issue. I am a part-time music producer and can't use my my high-end headphones on my S4 and it is really disappointing that it can't handle such a basic task. I don't want to have to root my phone because I use Wi-Fi calling and NFC very frequently and usually they are disabled in rooted versions. If anyone has a fix for this it would be much appreciated. I am a noob here at these forums so please explain any solutions step-wise for better understanding - thanks.

Bad phone call quality

I am on latest LOS with my XT1676 (3GB Ram) and noticed bad audio quality during calls (at least receiving audio but I also heard that my voice sounds bad). Anyone else with this problem?

Yes, I also noticed there is a noise during the call, like the person I was calling with was outside. And also when I turn on loudspeaker and I am little further from microphone the other side cannot hear me well, as I used it to do on Moto G2. I am on latest Lineage 14.1. Do you think it could be causing these problems?
Thanks

Me too, I'm using pixel experience (oreo). It's sounds like the person is talking in handsfree. Maybe an bug from custom ROM?

I'm having the same issue: Poly OS , android 7.1.2

Since I started the thread I could not find a fix. It seems that stock ROM does not have this problem which suggests it has something to do with drivers(?).

Same issue
I also noticed this Issue
When I called my mum who has the same phone and model ( XT1675 )she sounded quite blurry, in a way muffled, I thought she has changed a setting on her phone then my best mate wanted me to ring her, same issue, she sounded muffled and I apparently did
Got home, called my phone from my mum's phone and listened to the quality on both sides, I sounded really clear on my mum's phone but really muffled on my phone
I wanted to go back to stock firmware but Moto G5 XT15675 firmware isn't available, only XT1670 and XT1677

V30 Quad DAC Root Bybass fix

Ive been playing about with this phone now and making a rom and in my expericance so far and from somthing @ChazzMatt said that I realized something was not quite right and it happened after i flashed a new 10c kdz and did the normal thing twrp + Magisk + Viper that i found the Quad DAC to not be switching on. Volume at 50 is nowhere near what i should be with it on compared to off. Ive found something in the build prop but im not sure if its just a coincence or this is actually doing something but 2 things might be the cause of the DAC not switching on.
1. Persist.audio.dmb_hifidac = true
2.Persist.audio.hifi_dac = off
Ive found that playing with these options and rebooting causes the DAC to switch on again. Maybe someone else can confirm exactly which of these keeps it working.

In custom CM/LOS ROMs with the 2016 ZTE Axon 7, which also has a quad DAC, devs could not use the quad DAC for audio processing. They had to use the Qualcomm Snapdragon audio processor -- as ZTE would not release proprietary source code for their award-winning quad DAC.
I believe stock based custom ROMs still had access -- as those were just debloated, tweaked ZTE firmware.
(Last time I checked was a few months ago, so if devs overcame that hurdle, then good for them. I only know the situation last time I looked.)
I do not know about the LG V20 custom ROMs, either stock-based or CM/LOS. LG V20 of course also has quad DAC. I've not researched. Maybe someone coming from V20 can tell us, either a dev or a user?
It's just the quad DAC on this phone is one of the main selling points, so you want to make sure it's being used if possible... Your ROM is stock based, but LG does have limits in place. For instance, it checks for impedance. And there's things you don't want to break.
Sent from my carrier unlocked LG V30+ US998

Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON

donky kong 017 said:
Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON
Click to expand...
Click to collapse
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.

Whiskeyomega said:
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.
Click to expand...
Click to collapse
Yeah it's strange. Everything worked last time with old magisk (I had to go back to stock and reflash twrp after updating to magisk 15 got me a bootloop)
It seems odd that rooting changes such things in build.prop

I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.

Whiskeyomega said:
I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.
Click to expand...
Click to collapse
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk

donky kong 017 said:
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.

Whiskeyomega said:
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.
Click to expand...
Click to collapse
Atm im on vacation. I will look into it when I have the time. FYI I have ath m50x and teufel move inear
Sent from my SM-G935F using Tapatalk

so i've looked into it. my HP have 32 and 16 Ohm impedance.
they trigger the dac on when i connect them (after i changed the build.prop. it never stopped working for me again)
judging from this thread connecting higher impedance HP will trigger higher power output modes, but the dac is always on in the same way

If somebody was thinking battery test on youtube video streaming, i did that and got 8h 2min sot. Full brightness and volume.

can someone help me? have the feeling that my dac does not run since I use viper4android

with me the dac does not run with viper4android

Sony92 said:
with me the dac does not run with viper4android
Click to expand...
Click to collapse
Don't use that then. Instead use this:
Whiskeyomega's V30 Sound Mods
https://forum.xda-developers.com/lg-v30/themes/whiskeyomegas-v30-sound-mods-t3757115
What LG has done as made a bad job of the mixer_paths_tavil.xml which includes references a ES9018 which was never put in the phone or any phone AFAIK.
But what I have just noticed is if you are using a set of low impedance headphones, It goes through to the low power sound device chip but keeps the HIFI DAC switch working so the EQ can still work. Unless you make it think you are running a different type of headset which it calls "Advanced" which is high impedance then it runs to the decent DAC and there are no problems.
I have also noticed in all the mixer_paths_tavil.xml from around the world markets that there are differences in settings which should be the same. Which is what could account for some people saying Low Impedance still runs through the same decent DAC and some people saying it doesnt. Either way mixer_paths_tavil.xml is a maze of old and incorrect information.
So with that in mind. I'd Like to share the results of my work with more always coming.
Click to expand...
Click to collapse
Besides these standalone mods, some of this is implemented in at least two stock-based ROMs.

I do not want to use only the DAC, but also viper4android

Sony92 said:
I do not want to use only the DAC, but also viper4android
Click to expand...
Click to collapse
Those mods improve the DAC so you don't need viper4android.

Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper

Sony92 said:
Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper
Click to expand...
Click to collapse
You will have to ask them.
Sent via open market LG US998 V30/V30+

can it be because I installed a Costum Rom because the DAC is not running?

have the deep_buffer file restored. Now the DAC is running with Viper4Arise. I did not have to change any settings in Build.prop.

Bluetooth

Is it me or does Samsung always have Bluetooth connectivity issues? One of my biggest complaints is that It's always a hassle to connect via Bluetooth. I also own an iPhone and that sucker connects to Bluetooth seamlessly. Especially when connecting to my car.

LuRock said:
Is it me or does Samsung always have Bluetooth connectivity issues? One of my biggest complaints is that It's always a hassle to connect via Bluetooth. I also own an iPhone and that sucker connects to Bluetooth seamlessly. Especially when connecting to my car.
Click to expand...
Click to collapse
I've owned the S3, Note 3, Note 5, Note 8, S9, and, now, the Note 10+, and I'd say I only remember some BT issues with one of the early Galaxy phones on that list. I can't remember which one, but they went away as I experimented with different ROMs. Eventually, I was happy enough with the OOTB OS and Samsung overlays that I just stopped flashing ROMs. I've certainly had no BT issues with the Note 8 or the Note 10+. (I didn't use the S9 long enough to have a strong opinion)
In my life, I have, off the top of my head, the following BT devices:
- several portable BT speakers
- 3 family cars
- 2 August Smart Locks
- 2 garage door openers
- a JBL Link 20
- an LG sound bar with BT
- thermostat
- refrigerator
- Nespresso
- several smart lights, switches, and dimmers
- a weird string of lights in my daughter's room
Many of those things only use BT momentarily, while setting up a WiFi connection, but they seemed to work perfectly with my Samsung phones, nonetheless. (I'll get back to you on whether I'm frying my brain and sterilizing my kids with all the wireless tech in my home)
Sent from my SM-N975U using Tapatalk

I have used bluetooth devices since my sony ericsson days, the k700i, back in 2005, since there, I have had a lot of various bt gadgets, and, the most common issue is the difference in bt versions, and the implementation, commonly the phone has a higher version, and the gadget has a lower one, and there is where I have found some troubles, not always, but sometimes, at first, say, 2006, 2007, I always thought as you that the phone was somewhat the culprit, but as I have had more and more phones and gadgets, the pattern became evident

winol said:
I have used bluetooth devices since my sony ericsson days, the k700i, back in 2005, since there, I have had a lot of various bt gadgets, and, the most common issue is the difference in bt versions, and the implementation, commonly the phone has a higher version, and the gadget has a lower one, and there is where I have found some troubles, not always, but sometimes, at first, say, 2006, 2007, I always thought as you that the phone was somewhat the culprit, but as I have had more and more phones and gadgets, the pattern became evident
Click to expand...
Click to collapse
Sorry just seen your sig
Just had to mention my old units - Sony P800, Sony P910, Nokia C7, and Nokia 701 ahhh Symbian!

LuRock said:
Is it me or does Samsung always have Bluetooth connectivity issues? One of my biggest complaints is that It's always a hassle to connect via Bluetooth. I also own an iPhone and that sucker connects to Bluetooth seamlessly. Especially when connecting to my car.
Click to expand...
Click to collapse
Hey there. I had the same issue amongst a few other things. My audio for phone calls wasn't working about 90% of the time. Took it in to a Sprint Service Center and not just one of their kiosk stores. They said it might have just been a bad load from the factory and wiped the phone and reloaded the factory software they had up to date and everything seems to be working flawlessly. Apparently this happened to a few of the handsets. So try to have it reloaded with the original software and not just a factory reset.

skryte said:
Hey there. I had the same issue amongst a few other things. My audio for phone calls wasn't working about 90% of the time. Took it in to a Sprint Service Center and not just one of their kiosk stores. They said it might have just been a bad load from the factory and wiped the phone and reloaded the factory software they had up to date and everything seems to be working flawlessly. Apparently this happened to a few of the handsets. So try to have it reloaded with the original software and not just a factory reset.
Click to expand...
Click to collapse
Hi, I don't think that's my case. This has been my history with the Note 8 & 9 and now with 10. I always have to manually connect and it takes me 3-6 tries before it connects. Sometimes it doesn't connect at all.

Not any connection issues whatsoever here with mine either..