yashsingh1/xdaforums huggingface dataset:
[HTC Butterfly S] tsokh:
I don't hear any high pitched squeaks, but there is an audible hiss only with max volume when I scroll pages with music playing in background or with no music at all - I don't pay attention to it. In my opinion, there always be a hiss in smartphones due to touchscreens being so close to DAC, amplifiers and other hardware - you can't neglect physics, so I really don't bother about it. I know only one exception - IBasso DX100, but that's completely other functional device. If you want really good sound, get a music player but not an all-in-one solution.
[HTC Butterfly S] FYL21:
I think this whole crackling issue has to do with impedance. My Panasonic HTX7 which has 40 ohms of impedance has almost no crackling at maximum volume with 320kbps mp3s. The other headphones I tested were 16 ohms which is relatively common. They also tend to hiss more while the HTX7 does a good job masking light hiss. However, I am not sure what the impedance of the RC E160 is but it might actually be higher than 32 as many stock earbuds are. (mine that came with the phone are not E160 they are the same in-ear pair that come with the HTC One)

The other problem is the hiss is continuous as long as the headphone is plugged in. In my One X+, the hiss is only present during and slightly before and after music or just a simple sound is played. I think in the Butterfly S the headphone amplifier is causing this hiss.

Also if you use the camera and take a picture while playing music the music will obviously pause but it sometimes resumes at a slightly lower volume although the volume level actually remains the same - you must unplug your phone and then replug it in. It's as if taking a picture turns off the amplifier. Sometimes Beats Audio is rather inconsistent as well it seems to sometimes apply the EQ but not increase volume.
[HTC Butterfly S] tsokh:
HTC RC E160 has around 40-50 Ohm impedance, Sennheiser HD25-SP 60 Ohm. Hiss only noticeable on volume after 12. The problem with volume might be caused by Beats enhancement, as I didn't have such issues with my phone.
[HTC Butterfly S] FYL21:
Well I think IEMs and earbuds regardless of impedance are more suspect to hiss. I find 12/15 to be the optimal listening volume for my IEMs but there's already the bass distortion. :( 14/15 sounds fine with my HTX7s. Because the highs are much better on the Butterfly s than the HOX+ I'm somewhat paranoid of audio clicking (not crackling) perhaps I'm too used to One X+'s sound signature which is a bit low on the highs.

Overall while I'm impressed by the audio quality but the distortion disappoints me as I hoped the headphone amp would give a higher volume for most headphones.

I had contacted HTC regarding this issue but have yet to recieve a more detailed reply. So far I only received news that they forwarded the issue to the "relate department" to confirm it. It's already been a few days though... =S
[HTC Butterfly S] FYL21:
also with PowerAMP i notice some occasional audio popping (not distortion) even at some lower volumes. Maybe it's because I'm switching between stock player and PowerAMP without closing one of them, but I have not had this issue with my One X+ (the only real issue with the One X+ is audio skip and sometimes a crash, which usually only happens if you turn on the screen).

At 12/15 it seems bass distortion doesn't always happen especially if you play the whole song instead of skipping to that section where it's supposed to happen.

I've tried PowerAMP and Neutron, the bass distortion happens on both.
[HTC Butterfly S] tsokh:
I don't have audio popping, however, I don't use multiple music players. I didn't install stock music player, playing everything with PowerAmp.
[HTC Butterfly S] FYL21:
I contacted HTC Canada because I was having some problems getting the message to HTC Taiwan (they can accept messages in English but there is a bit of a language barrier and the responses are often partially fixed). An HTC North America representative then told me this was now a known issue with the Butterfly s. They told me to run the diagnostics program and to close third-party apps which may interfere with the music, but the problem is still there.

The current solution is only using high-impedance over-ear headphones, but the maximum volume still has a little distortion.

I would like to know if anyone with Bluetooth is having the same issue. If that's the case then it's not the headphone amplifier it's the DAC.

Another thing I would like to point out is if you power on the phone it doesn't remember the headphone volume level you had before you turned off your phone the previous time.
[HTC Butterfly S] FYL21:
The representative then suggested there may be a malfunction with the headphone amplifier of my phone and asked me to phone the HTC RMA Center, which I think is a bit of a hassle... I might as well wait until I get back to Taiwan in a few months and take it to an HTC service center to ask about the problem.

Considering tsokh had a similar problem I think it might not be a malfunction...
[HTC Butterfly S] FYL21:
unfortunately the problem is still there in the latest software update...
[HTC Butterfly S] daorderdillon:
What's your cid
[HTC Butterfly S] FYL21:
HTC_621

Perhaps I do have a defective headphone amp or something's wrong with the DAC :( I haven't checked Bluetooth though...

My phone is a 901e purchased from an HTC store Taiwan.

[MENTION=5393121]tsokh[/MENTION] what is yours?
[HTC Butterfly S] daorderdillon:
HTC_622 and I'm not having no problems
[HTC Butterfly S] FYL21:
which headphones are you using and what volume level?

With my over-ear headphones (Panasonic HTX7) only the absolute maximum volume level distorts. 14/15 sounds fine, indeed it sounds amazing, the headphone amp drives them very well. I struggled getting decent volume on my HOX+ (Beats gains well, but adds some artifacts, preamp causes similar bass distortion what I'm having here, but not as bad).
[HTC Butterfly S] daorderdillon:
The headphones that came with it at max volume
[HTC Butterfly S] FYL21:
It only happens on songs like this: https://app.box.com/s/71ernfnfrucms6iggetk
[HTC Butterfly S] daorderdillon:
Lol nah no crackle playing that
[HTC Butterfly S] FYL21:
interesting... perhaps something is wrong with the headphone amp on mine :(

Are you using 901e or 901s?

I wonder what tsokh's CID is because he had the same problem I had but fixed it with a mod.
[HTC Butterfly S] daorderdillon:
I'm 901s
[HTC Butterfly S] FYL21:
hmm maybe 901e are affected??? Unfortunately I don't think anyone else listens to music this loud, so HTC says nobody's reporting the problem but they have taken my report into account for development...

unfortunately I'll have to wait until I go back to Taiwan, don't know if I should just send it to RMA, because who knows, maybe if the amp is replaced it still has problems...

I did notice at first with some headphones there is a similar crackling noise when you spin the headphone plug around the jack, but it goes away after some days. My iPad 2 has a tiny bit of this whenever I plug in a headphone, must give it a twirl. However, when I turn the volume up and down I also hear a crackle as it changes volume levels, so I believe the issue may be software-related...
[HTC Butterfly S] daorderdillon:
U have any idea when we are getting the sane update u got
[HTC Butterfly S] FYL21:
nope, I got mine yesterday but I would guess the others will get it in the next few days or following week, Taiwan (901e) usually gets updates first, but they won't be too fast with updates at other places... :S
[HTC Butterfly S] tsokh:
Mine is 901s from Taiwan.
[HTC Butterfly S] FYL21:
hmm 901s isn't found in Taiwan we only have 901e as we don't have LTE in the first place. What's your CID? 901s is found in Hong Kong, Singapore etc.
[HTC Butterfly S] daorderdillon:
HTC_622
[HTC Butterfly S] FYL21:
I was asking Tsokh but I guess he would have the same as yours.

Interesting so I guess it's a few unlucky units :( gonna be a pain to RMA though... When I get back to Taiwan I definitely won't be able to ask for a new replacement... About a week after I bought it after traveling about, I did ask the store ppl (semi-official seller) they said it was probably a software problem and would contact HTC about it.

I think it's how the software is increasing the volume levels and low-frequency clipped peaks OR it's a defective headphone amp, which is why I would like to try out Bluetooth before ruling that out (but I have to buy another headset then -_-).
[HTC Butterfly S] tsokh:
have the same CID HTC_622. tried bluetooth, didn't hear any clipping.
[HTC Butterfly S] FYL21:
then it probably is the amp :(
[HTC Butterfly S] FYL21:
The latest update to 4.3 seems to make it a lot better though there is still a TINY bit of crackling above 11/15 for an in-ear headphone... strangely i hear a tiny crackle at 12/15 but i don't hear it at levels above, but the volume is just very loud beyond that. it sounds more like the sound card is clipping the signal of low frequencies.

Also the speaker-headphone volume glitch still occurs. If you leave a game running in the background or plug in headphones while music is playing with the speakers, the volume will be louder than it usually is - "overblown" and you might here a bit of crackling. You need to replug your headphones to lower the volume.
[HTC Butterfly S] edorner:
Test results

Continued from: issues/improvements of update 4.3

Hey,

My opinion is that this issue is simply a design flaw which affects all/most Butterfly S devices. Fortunately, it seems to be limited to a certain level of volume and a specific type of music (as you have already observed). So my theory is that this is a widespread problem which very few people notice.

I listen to music on my 901s quite often, but still, I had to deliberately look for this issue in order to confirm it:

I normally listen to music at about 7-10/15 volume. With in-ear headphones, above volume 12 it is so loud for me it almost hurts :D Nonetheless, out of curiosity, I tried volume 13 with some of my bass-heavy tracks yesterday, but I could not hear any distortion / artifacts, etc. Then I downloaded your test-track, and listened to it at the same volume. It indeed produced the phenomenon you described.

Test environment :) :

Butterfly S 901s (CID: 622), Stock Android 4.2.2 (1.23.708.3), AudioTechnica ATH-CKM500 (16 Ohm), JVC HA-FX66 (16 Ohm), stock HTC music player app, with BoomSound enabled and disabled.

Genres: Rap/Jazz/Trance/Pop
[HTC Butterfly S] FYL21:
Thanks for the reply.

I had previously contacted HTC about this and they suggested I do a factory reset but seeing that you did that already and the problem persists, I don't think that is the problem.

After the 4.3 update it's more subtle "pop" or "click" that occurs at the exact same part of the song each time and usually only the left audio channel, noticeable on most of my IEMs at 12/15. In the test-track, it occurs when the piano is being played and only on the left side; at higher volumes it also occurs at another point in the song near the end (the bass kicking in before the ending chorus) but on both channels. On my phone the left channel does give a bit of high-pitched noise in addition to the typical IEM hiss, noticeable when switching tracks... Also, BoomSound speakers do hiss when audio is supposed to be played and give out a "pop" at the end of an audio signal, even if the phone is muted. It's only noticeable in dead silence.

When I'm outside I tend to listen to music at lower volumes but when I'm at home I'm used to listening at higher volumes.

I had a CKM500iS before (I just lost it recently) and on the 4.3 it sounded fine up to and including volume 12/15; the same goes for my other Audio-Technica IEM (CK323M also 16 ohms) as well as the stock HTC IEM (impedance unknown but probably higher). Strangely, my backup CKM500 (without the mic box) and JVC Marshmallow crackle a bit at 12/15.

PowerAMP - using IEMs there is no audio popping until 13/15 because volume is slightly lower and limiter turned on. But as I said before, on third party players there is a different type of audio clicking that occurs regardless of volume. It can occur at the same part of a song but it does not always happen if you go back to that same section, like audio skipping on older Android phones, but it's now just a click. In PowerAMP I've tried changing the settings around but it still occurs.
[HTC Butterfly S] edorner:
Yep, this is exactly my experience, too.

And it also seems to be a common problem, which is not even limited to the Butterfly S. I remember reading an article about the common issues of the HTC One and their possible solutions/walkarounds, and the speaker pop was among the main items there...
[HTC Butterfly S] fluidz:
I get the exact same popping in the left channel sound on my HTC One M7 on 4.3. Affects both Phonak pfe232 iem's and Sennheiser HD215 headphones. You had any luck in finding a fix?
[HTC Butterfly S] FYL21:
I'm not sure if it's universal but it seems several other users of the Butterfly s have the problem. On mine it happens on both channels but is more noticeable on the left. You could try using PowerAMP with the limiter turned on, it should prevent the popping at least one volume level higher. However, on my unit at least, I get occasional audio clicking (not distortion, it doesn't always happen and does not necessarily happen when there is bass) playing music with a third-party music player (and sometimes even the HTC player after the Sense 6 update).

I've noticed it's improved slightly in the past few updates, but even after having my headphone jack repaired (it got damaged due repeatedly yanking out the headphone plug causing it to buzz unless positioned properly), the problem is still there. On IEMs it distorts a little at 13/15 volume level. On over-ear headphones with higher impedance, it only starts distorting around 14/15 volume level with long bassy notes (not many songs where it occurs but I noticed it first in the breakdown of Touch by Daft Punk). Normally I listen to music around 10-11/15 volume with IEMs and 12-13/15 with larger headphones.

On the Butterfly s there also seems to be something wrong with the DSP, because sometimes if you unplug the headphones and quickly plug it back and play music, it sounds louder and more bassy, other times it sounds quieter and less bassy. It's as if Beats Audio was turned on by mistake.

Although I consider the audio quality to be great overall at the lower volumes (up to 12/15), there's still a considerable amount of hiss and I can hear some CPU noises on the left channel when no music is playing. The problem is only obvious with IEMs. It might just be my unit but I've seen reports of these on M7s as well.
[HTC Butterfly S] FYL21:
I suspect it is a problem with how the DAC is handling clipped signals. I just heard "O" by Coldplay, which normally has a constant rumbling distortion of of the piano and bass throughout the song, but there are pops and crackles that shouldn't be there when I have the volume cranked up to 13/15 using my Audio-Technica ATH-M50x.
[Samsung Galaxy Mega] mse_uk:
Hi Tech,

I'll match your $25.
[Samsung Galaxy Mega] Gotroot:
If this is for the I527 I will throw 25 np
[Samsung Galaxy Mega] Techngro:
To be honest with you, I didn't consider the different versions. The international versions (i9200 and i905) have been out for a few weeks, so that is the one that most of us have been dealing with, but I know that the AT&T version (i527) was just announced and will be in stores soon (if not already).

I am pretty sure that the internals of all of the versions are the same, so it may be that one ROM will be good for all phones (except for the radios/modems). But we'll need a dev to actually confirm that.

I'll leave your pledge off until we can figure that out. Thanks for showing interest anyway.
[Samsung Galaxy Mega] dparrothead1:
The i527 is locked tighter than ****'s hat band!
[Samsung Galaxy Mega] mse_uk:
How about this....

I'll offer a Galaxy Note 2 GT-N7100X store demonstrator, fully functional except it can't be used to make calls. But I'd want access to the source to be able to carry on building.

Would this be of interest to any experienced dev's?

Sent from some dark corner of my imagination from my Mega (or) Note.
[Samsung Galaxy Mega] Techngro:
[MENTION=4746062]mse_uk[/MENTION]: Thanks for making this available for the bounty, i'm sure it will peak a few dev's interest.

[MENTION=1007992]everyone[/MENTION] else: I wonder if there's a way to advertise our bounty on XDA. Dev's probably won't know about it until they come to this forum, which they probably won't do if they don't have a Mega or aren't thinking about getting one.

Maybe i'll tweet at XDA about the bounty with a link to this thread.
[Samsung Galaxy Mega] n1tro:
I think this bounty is unrealistic and the responses or lack of from developers will tell. The bounty is asking for a fully functional 10.2 rom with everything working. Right now, 10.2 is still in beta for the Note 2 and even when it gets out of beta and becomes a daily driver rom, there will still be some stuff that needs to be ironed out (Bluetooth, camera, low in call volume, etc...) if the past rom development is any indication.

Basically what I'm saying is I highly doubt any dev would take on the above requirements which is not realistic to complete and all for $75 and a phone that can't make calls.

You may want to revise the bounty for whoever can get CM to boot on the Mega 6.3 first. Then we should be able to get roms ported over. Then god willing, with the Megas going to the US, more devs get interested and develop for this phone.
[Samsung Galaxy Mega] mse_uk:
At present only three people have pledged to a bounty, next week we could still have three, similarly we could have twenty which would be more appealing to somebody with the skills. I'm contributing towards a bounty because I just don't have the skills to do it myself even though i am giving it my best shot.

My latest failure after starting from scratch (again):

error: /home/mark/cm10.2/out/target/product/meliuslte/system.img+ too large (298913472 > [283041792 - 2838528])
make: *** [/home/mark/cm10.2/out/target/product/meliuslte/system.img] Error 1
make: *** Deleting file `/home/mark/cm10.2/out/target/product/meliuslte/system.img'
[Samsung Galaxy Mega] jpeps:
Please root
[Samsung Galaxy Mega] Techngro:
The Mega is still a fairly new device, and a niche device at that. But I don't see any problem with having a bounty for CM 10.2, even if all you say is true. The same time/effort that would be dedicated to any other device could be dedicated to this device as well. And the sooner we get someone working on the latest version, the less time we have to wait to get a stable version. I would rather have the effort put towards the latest version with slow progress, than someone quickly porting CM 9.

But perhaps your suggestion of having bounties for different stages does make sense. we could have a small bounty for getting 10.2 to boot, and then a larger bounty for a test version and a stable version. If people think that is a good idea, I can set it up that way.

As for the current level of the bounty, yeah it's small, but as I said, the Mega is still a fairly new device, and is just hitting US carriers now. It might take a few weeks, but as more people get their devices and seek to expand its capabilities, they will come here and hopefully pledge something towards the bounty. I think everyone who is participating knows that this won't be an overnight effort.

Edit: btw, did you come here because you have a Mega and were just browsing the forum, or did you see my tweet about this bounty? :)
[Samsung Galaxy Mega] n1tro:
I have a mega and note 2 so I switch back and forth. Unfortunately time is not on our side. The note 3 will be coming out next month and devs will be moving on the the latest and greatest. What we need is for devs to have a vested interest in developing for the mega even though it isn't popular. I personally love slimbean ROMs. They are well programmed *and* they support older devices as they continue to do great things for new devices.

What I'm trying to say is that for the mega to have a chance of getting custom roms , one of the devs would have to have the phone to maintain it.

So instead of waiting until a dev does all the work getting a working ROM and collecting the bounty, we should contact one of them eg. Slimbean lead dev asking if he could include the mega among supported devices and send him enough money to buy one himself.
[Samsung Galaxy Mega] jpeps:
All we need to unlock the boot loader hopefully soon
[Samsung Galaxy Mega] dparrothead1:
We have a dev that has the device and he is working hard at rooting. Keep in mind, the Note III will also be locked.....at least from ATT.
[Samsung Galaxy Mega] jpeps:
Thanks for the update
[Samsung Galaxy Mega] Warnahly:
I just found this thread for unlocking the bootloader maybe maybe and I hope it helps you on the way

http://xdaforums.com/showthread.php?t=2396819
[Samsung Galaxy Mega] jpeps:
Does not work with samsung :(
[Samsung Galaxy Mega] rakesh_4utoo:
15 days back i sent a PM to Indie but no response from him. Missing Omega , Criskelo and Android Revolution Badly... Only these developers with NEAK or perseus Kernel could remove little Touchwiz and other Lag .
[Samsung Galaxy Mega] Krijs:
Would be nice to see some love for this phone.

Pledging $25 as well.
[Samsung Galaxy Mega] ponglenis:
I would happily toss in 15$ for a cm 10.1 or cm 10.2 that boots!!

Many a mickle makes a muckle, right? ;)
[Samsung Galaxy Mega] Warnahly:
Since CM10.2 is having bugs ATM I would prefer CM10.1 honestly

I wont give 20$ to CM10.2 if buggy
[Samsung Galaxy Mega] Lifeisrandom:
Sounds like an interesting project. I'll give it a go.
[Samsung Galaxy Mega] mse_uk:
I'd say buggy depends on your perspective. I'm using home built CM10.2 on my note for daily use and having no problems whatsoever.

Sent from some dark corner of my imagination from my Mega (or) Note.
[Samsung Galaxy Mega] jpeps:
There a dev working on is ?? One post that he is working on this root ?
[Samsung Galaxy Mega] Frogimus:
I'll happily chuck 25 bucks to someone who gets a decent rom on this :good:
[Samsung Galaxy Mega] Techngro:
Thanks, i'll add your pledge to the total.

Every little bit helps, gracias.

Does that mean you'd like to add to the bounty? If so, let me know how much you'd like to contribute.

Alright, now we're talking. :)
[Samsung Galaxy Mega] ga88352006:
If this can be confirmed for I527 I'd throw in $25
[Samsung Galaxy Mega] marcdunn82:
I have yet to get the phone but I am sure this is what I'm buying, so throw me in for $25 bucks as well.
[Samsung Galaxy Mega] Techngro:
Well, as we said before, the specs are the same, it's just a problem with AT&T locking down their device tighter than a clam. If they can unlock the bootloader, then I don't see why any ROM for the other versions shouldn't be able to run on the AT&T version.

Ok, you're officially in the club. I'll send you the secret handshake later. lol
[Samsung Galaxy Mega] Techngro:
This is an interesting idea. Anyone else think this would work?
[Samsung Galaxy Mega] Techngro:
I'm sorry, I think I misunderstood your post. Were you talking about trying to develop a ROM or contributing to the bounty? Either would be great of course. :)
[Samsung Galaxy Mega] jpeps:
It sound good here hopefully and root this
[Samsung Galaxy Mega] i04055:
I think that is a better idea.... the main reason why the dev won't work for this device is because they don't have the device itself and won't spend their money to buy this device.... so why don't we give them enough (or at least most) money to buy it...

NB:

FYI, galaxy s4 mini already got its official CM 10.1 nighlies, maybe we can contact the dev arco68.....
[Samsung Galaxy Mega] Techngro:
The only problem is, unless it's a

very

well recognized developer, how do we know that once we buy the device and send it, that they will actually do the work and provide a stable ROM? I know it sounds jaded, but sending off a $450+ device without any assurance that we'll actually get a working ROM makes me unsure about trying this.