yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] marctronixx:
the issue is the masses don't know any better and the codecs installed on the phone are just "good enough" for the masses. samsung sell to the masses , not the enthusiasts.

the folks on this forum are those "enthusiasts" and thus will notice subtle things like this.

once the masses complain about it, samsung would most likely add it back. just like how the masses complained about the cheap free buds not being in the box (where many of them didn't use them but nevertheless expected them out of principle) - samsung promptly provided them for free (and just tossed them haphazardly into a padded envelope to boot).
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
The Note series has always been an expensive niche product that targeted power users.

So during a economic depression what's Samsung do?

Raise prices, drop performance features and try to recast the Note as the pretty boy -everyone- wants.

Perfect. Inept marketing.

Samsung did it again this year and they are paying the price.

Between Samsung's screw ups and Q, no way I'll (and many others*) upgrade this year and at this rate not next year either.

Afterwhich Sammy better have gotten their lame rabid gerbil circus act together...

*all those glowing fold 2 reviews are bs, it's price is sinking faster than a concrete life preserver. Meanwhile the 10+ price is still remarkably high.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] speedyjay:
Its present for me...View attachment 5105227
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
AptX HD... is the one you wanted.

All those codecs are inferior to it:(
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] roryh86:
Really? Says who? Samsung Scalable Codec supports up to 512kbps, similar to Aptx HD 576kbps. A marginal difference that you and I will definitely not be able to hear. The fact that it scales is an added benefit to maintain connection, besides most of us will be listening close range so you will most likely always be in the high end 512 kbit range.

I don't know about you but most of us listen to Spotify or YouTube Music which have a maximum of 256-320kbps, so you're technically not even gonna use 512kbps.

Not to mention, that most of us who do a blind test cannot tell a difference above 320kbps audio. SSC also supports 24bit 96kHz audio, similar to Aptx HD.

I have never experienced any audio sync lag issues over Bluetooth while watching content on a Samsung device. I can't say the same for other devices I've used in the past.

Personally, I have tested my Sony WH-1000XM3s using Sony LDAC codec (which my Note 20 supports) at 990kbps and with SSC and cannot tell any difference whatsoever.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
LDAC is better than Samsung's Scalable codec but inferior to AptX-HD.

kbps not the only difference, things ain't quit that simple.

I learned long ago you -CAN- hear better codecs.

Not talking about 16 bit wav files; the scalable codec can't even fully reproduce that!

Let alone HDCDs that have up to 22 bit resolution not 16 bit.

&

With 24 bit masters being released every bit counts...

Dig up the analysis if your ears can't hear it... some people's can though.

Of course if you're listening to mp3's... never mind.

Try playing through bt speakers and the loss of spacial depth ie sound stage will be immediately noticeable using any of these bt codecs from an HDCD or 24 bit file. To electro-acousticly couple a sound stage you need at least 2 stereo speakers coupled by open air (not headphones).

The interaction of the acoustic waves create the stage stage and directly electro-acoustically couple you with where the recording was made.

O'Really... It can "support" it, but it grossly degrades it!

It has no where near even 22 bit resolution let alone 24 or higher bit resolution. I'm listening Sammy's Scalable codec right now and the highest HD audio setting allowed in Developer Options is Adaptive Bite Rate which is not even 909 kbps!
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] sr.bond:
to add insult to injury it does not allow me to change to any of the other codecs, it just stays at the factory selected codec.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] roryh86:
I've tested multiple high res songs from Tidal and Amazon Music against Spotify's Very High, on my Denon X4400H receiver using my upstand Q Acoustics 3050s through bluetooth on my Note 20 and brothers Oppo Find with aptx hd, with my myself and my brothers. At first we thought we heard the difference, then we had one of my bros not tell us which one is playing and switched that around. We all failed miserably.

They all sounded AMAZING.

My point is, at least for my consumer grade £1500 equipment, I and several others could not tell the difference in a blind test. At the end of the day, the phone isn't meant for £50,000 professional grade audio equipment or a studio, and if you happen to have that, you're not going to be using your Note 20 Ultra to stream audio to it via Bluetooth. Most Artists carry around iPhones with AAC/SBC, I don't hear them complaining that their songs sound inferior. SSC is even better than that, and I just think it's ridiculous that someone wouldn't buy a phone due to something they most likely will not hear. It's like wanting 4K resolution on a 6" screen.

Truth is, it's diminishing results after 320kbps for 99.99% of us. Yes you can probably pick up the difference in audio software using a benchmark, but that doesn't translate to reality. If you're okay buying into the 24bit marketing or can actually hear the subtlest of subtle detail, then you're in a very very small minority.

I would recommend completing the custom audio profile setup in your Samsung phone in the "adapt sound" setting. You should at the very least have a perfect score if that's the case.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
In Developer Options it should allow you to switch it to any codec that the devices support.

It then however degrades it by forcing the Adaptive Bit Rate. With the Buds it can't be successfully toggled to a higher bit rate protocol.

Maybe that's needed for the voodoo scalable codec but anything less than 909 kbps is unexceptable not that 909 kbps is that great to begin with.

Maybe Google/Samsung fixed this in Q... I'm running Pie; screw scope storage.

If your bt peripheral supports AptX-HD though you're completely boned because of the legacy bt chipset Samsung forced down our Notes:(
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Slypnslyde:
Until some famous or big Youtuber calls them out about things that Samsung does with their phones like taking away codes and locking bootloaders. They simply will keep doing it. It's not a big deal for them too change anything until then. Flossy Carter always mentions them taking out the IR blaster but they still haven't put it back.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
Well I've ordered the Buds+, red for $99, strangely that was the cheapest color. Whatever.

That's as good it gets for the 10+ and 20U on bt.

The dongle is a complete pain in the arse... no.

The Samsung Proprietary Codec slams out a fairly large amount of data in optimum transmission conditions.

How good is it?

I have the Buds but it's drivers aren't the best; the Buds+ dual drivers are better. Heavily tweak with Poweramp the Buds don't sound too bad after many recent firmware patches and updates. Range is excellent.

The Buds+ will need the same as they are lighter on the bass end than I probably want, like the Buds.

The plus version is also reportedly much better for phone conversations although the first version was acceptable.

I'm not liking the Live Buds; I want that seal, the long play time and the fact the Buds -never- fall out.

For the Buds to work though a completely air tight seal is mandatory. This seems doable for most.

The Buds are light and comfortable to wear once dailed in.

A very little bit of coconut oil applied to the ear canal every 2-3 days helps prevent swimmer's ear and makes them easier to use. They are easy to clean and durable.

The cases are reportedly intercompatible too.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] bluefish196:
When I got my Note 9, I got in a fight with samsung Support, they were rude and ignorant like many in this thread defending Samsung.

The funny part, Samsung introduced me into audiophile music, yes, back in the S6, you could play FLAC and DSD64 over Bluetooth.

The line of Level Headphones were like Sony, using AptXHD.

Later got a nice amp dac for my desktop and if you hear LDAC and AptXHD, you can not hear the difference after 48Khz and 24 bits.

Now, the shocker.

During the S8, Oreo, AptXHD was SUPPORTED but they suddenly removed COMPLETELY IN ANDROID PIE.

No AptX. No warning, nada. Then they said in a Press release we will put it on the Note9.

Got the Note9 and it had it.

Then they removed to AptX.

Literally they don't care.

My advice, buy a FIIO dedicated player that can stream Tidal or DSD, supports AptXHD and LDAC and no sputtering.

Just use the Hotspot for streaming.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
SK Samsung can't handle criticism. They go to pieces, it's an Asian thing. Sort of funny.

Get the best set of monitor speakers you can afford and receiver etc to drive them.

Only in open air listening will you hear the full potential of electro-acoustic coupling.

You need a minimum of 2 channels to recreate the sound stage of were the recording was made.

If your room acoustics, equipment, set up, etc are done correctly it will be as if you are standing in the same room where the music was recorded.

The phenomenon of two different frequency audio waves colliding to produce a 3rd one make this possible. Example: 35khz + 36khz = 1khz

The two colliding frequencies are beyond the human hearing range, the product however isn't.

These interactions are the biggest factor in recreating the sound stage ie stage presence.

The high frequencies must be present and allowed to interact in open air (not headphones).
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Compusmurf:
It's simple. Qualcomm charges a license fee for the advanced codecs and to optimize profits, Samsung doesn't want to pay the additional fee.

US as consumers get the screwover while Samsung rakes in the $
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] 13MeePwn13:
This. The aptX various codecs are properiatry as well, it is not Samsung's fault. They are just trying to use their own Samsung scalable codec which should perform as well the Apt-X adaptive in theory. and Samsung saves money by not paying Qualcomm for having to activate apt-x codecs on those BT chips they are using, which contrary to what a user posted here...are not downgraded chips.

i doubt consumers get screwed over if they are using samsung earbuds, they have been doing same with Apple products so the criticism seems unwarranted.

The pitfalls of having an ecosystem similar to Apple is that now samsung is using own proprietary codec and if you have a Samsung phone, tablet and earbuds, everything will work well together but we get locked into using products of one company only.

I wish Bluetooth Audio get standardized somewhat. a combination of LDAC, any adaptive codec and TWS+ type codec should see more adoption.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
SSC is likely inferior to AptX-HD, as the latter is 24 bit.

Both use compression.

Finding any 3rd party technical reviews for SSC seems impossible.

LDAC may be the best codec available.

If you're going with the high end Sony bt listening products (the head phones)* it probably is.

The headphones have bigger, better drivers and should sound better codecs being equal.

I haven't sampled any so...

That said with a good equalizer like in Poweramp dailing them in, the Buds+ sound pretty good and are fun to use.

Perfect for calls... and they never fall out.

Without SSC the Buds+ are duds; SBC, AAC and AptX don't cut it.

For a Samsung phone though they are a no brainer for around $100.

Haven't tried the Buds Pro and because Samsung changed the physical design they may not work as well. A crap shoot.

In this day and age I want 24 bit throughput not wimpy excuses🤬

*https://www.soundguys.com/samsung-galaxy-buds-pro-review-46564/

Vs

Sony WF-1000XM3 vs Samsung Galaxy Buds Pro

Can the Sony WF-1000XM3 noise canceling true wireless earbuds keep up with the shiny and new Samsung Galaxy Buds Pro earphones?

www.soundguys.com

I would take the Buds+ over the Sony ones at this point. I can verify the Buds+ can reproduce as low as 27 hz and definitely have usable bass in the 30-35+ hz range.

100 hz don't cut it and the low end bass roll off looks a lot worse for the Sony. LDAC may or may not give them better resolution than the Buds+ SSC on a Samsung device... not sure.

The price point, the lack of low end bass on Sony's wf-1000xm3 and the Buds+ superb battery life put the Buds+ on the top of my preferred bud of choice.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] imucarmen:
I have the Bud+, Buds Live, and the Pro's, and imo the Buds+ sound like junk. This is on a Note 20 Ultra with the same settings. The Buds+ have such a high pitch and shallow sound imo. The Lives and Pros are both much better sounding.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
Sounds like a poor seal on the Buds+

It will trash the sound.

There are foam earpieces available which can give a better seal.

The seal is critical. You need to use the right earpiece/wing combo. It's possible none will give you the needed fit. When you walk you should be able to hear your footfalls (bone conduction) if the seal is tight.

A little coconut oil* in the ear canal helps. I put them partially in, let them warm up for 30 seconds or so then screw them home. I found this works best for me.

I use Poweramp's graphic equalizer to boast the bass; the Buds+ are fully capable of it. I listen to a lot of rock, heavy metal and jazz. Below is one of my EQ profiles.

*helps protect the delicate ear canal and helps to prevent swimmer's ear. Apply as needed. Once every few days is all I need... a very little bit is all that's needed. Coconut oil has natural anti- bacterial/fungal/viral properties.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Sprov:
It has been like this for years. If I have to guess, Samsung does so in order to push its wireless earbuds making the other TWS earbuds sound worst than the Buds+, Buds Live and Buds Pro on their devices. The Samsung Scalable Codec is anyway a very valid codec, it's just a pity that is compatible only with Samsung products. No problem for me because I always used the Buds, but...
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] 13MeePwn13:
What is scalable codec? | Samsung Support India

,

www.samsung.com

this link mentions that SSC has 24-bit and 96Khz support. I have never used any samsung Buds so i don't know how good is SSC. but i felt that samsung bashing in this thread is a bit unwarranted considering Apt-x is also proprietary codec.

LDAC is great for music although for videos occasionally the lag between Audi-video can be noticable.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] arsenal74:
My thoughts on this.........

How good SSC is maybe is irrelevant as it is only available on Samsung headphones.

I would prefer APTX-HD over LDAC as with LDAC you will almost certainly end up with lower quality than APTX or APTX-HD unless you force the higher quality option in dev settings and good luck getting those to work or stick on a Samsung device! There is actually a good chance that LDAC will sound worse than SBC on some devices.

How much better APTX-D is vs standard APTX in real world use is open to question, as a Tidal HiFi customer yes it would keep more of the quality but more and more these days I find myself questioning the value of HiFi as the the headphones I own (B&W PX7, Sony M3s) are good but still consumer and honestly I am not sure I can tell the difference. For example Tidal high @ 320 kbps AAC sounds very good and the lower quality of say Spotify is I think more down to the masters they use than any codec difference. Apple Music @ 256kbps sounds pretty good on an iPhone over 250 kbps AAC too.

YMMV
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Spider102:
LDAC Can be an alternative, it streams at a maximum of 990 kbps and supports Hi-res. Unfortunately, not all phones transmit at 900 kbps by default. so you may have to set the speed manually. on development settings
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Spider102:
But they have already fixed the sound with the equalizer in the record studio. so if you have the correct speakers, you do not need an equalizer
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
What is the correct speaker?

What about the correct listening area?

The users own hearing anomalies?

Beyond that most will be using Buds+ etc. not a bt studio monitor* so the EQ needs to be alter for the used drivers or listener's deficiencies.

*A bt driver monitor would highly degraded because of the lost higher frequencies, poorer noise floor and added distortion above 20khz for open air stereo listening. Loss or degrading of those inaudible higher frequencies severely degrades the sound stage which is highly dependent on them to form a complete stereo (or above) image which forms the sound stage.

It electroacoustically couples the recording stage to the listening area.

24+ bit 96khz music data>precision DACs>amp or preamp> monitor speakers... with no bluetooth in the pathway to degrade the image.

All bt codecs lack the needed bandwidth to reproduce a high res audio image faithfully.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] FYL21:
This is late but actually there is a hardware reason in part - Samsung uses Murata Bluetooth modules/modem on nearly all their devices, even in their phones with Snapdragon processors (this is why S21 series does not have BT5.2 despite Snapdragon 888 being capable of such (the S21 Ultra does have BT5.2, but uses a Samsung Bluetooth module). Samsung EU forum a developer claimed there were issues with stability adding AptX HD onto the Note 9/S9 and that they were looking into adding only AptX Adaptive, but they never bothered with it either. It's certainly possible to add it via software, but it's unlikely Samsung sees any incentive to do so (Huawei had AptX HD on their non-Qualcomm P2 series, but it may be that Qualcomm provided drivers as they were clearly listed on their website).

Anyways, I didn't have much problem with scalable codec until recently, but now it sounds bad on my Note 9 especially when Wifi is turned on. Not sure what happened but recently I started noticing the sound distorting whenever I have wifi turned on using my Galaxy Buds+ and Buds 2.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackhawk:
Going back about 2 months ago Wearables updated and completely screwed up the sound on my Buds+

After blocking the updater with Karma Firewall I uninstalled Wearables and the Buds apks, then used my backup of the previously working known good version.

If you don't firewall block Wearables update (I see it as UID103339) and Apps (UID 1000) Wearables will refuse to load unless updated or update and ruin the fix. I have no idea if Samsung has corrected this issue, but these versions I uploaded work.

Try a network reset and clearing the system cache before you embark using this solution.

Try a forced Wearables update too.

Also see my Buds+ thread for more details.

Hopefully the easy way will work, if not...
[ASUS ROG Phone II Guides, News, & Discussion] reg66:
CAUTION: This update may have major bugs (see link below) with overheating, constant max cpu and therfore, battery drain.

I've updated via the full zip already and will give updates for the next couple of days. I did experience heating whilst driving, I was streaming via Bluetooth to my car and uploading this latest full zip to mega at the same time. Initially I just put it down to these factors but reading some of the link from [MENTION=2585240]MelquiXDA[/MENTION], it may be a full issue with the rom. Once I cancelled the upload and finished my journey the phone returned to normal temps. Everything still stable now too. I've not changed any settings to counter the issues. Time will tell, will keep people posted

https://zentalk.asus.com/en/discussion/36275/high-temperature-cpu-usage-battery-drain-on-2009-47/p1

UPDATE: LINKS REMOVED, TOO MANY BAD EXPERIENCES

UPDATE : it seems its a Google issue causing the cpu spikes to max. This would tie up with my device not having max cpu possibly because I'm running the Google beta services

Asus has released a new update for our device

Changelog;

Android security patch update to 2020-09

Added support for ROG Connect in Armoury Crate

Support TwinView Dock 3 FW update

Fix issue where Pokemon Go could cause high CPU usage

Fix Application names being cut off in Recents view for Hebrew localization

Fix AirTriggers mistouch issue and optimize AirTriggers stability

Incremental (WW);

Alternative link;

Will update when there's links released for full zip

Full zip update;

For those of you that are rooted: Download the full zip, move to root of internal storage and reboot. System will detect and prompt to update, click update. Wait until it finishes but DON'T click 'restart', instead, click 'restart later'. Go to Magisk manager. Click 'install' for Magisk. Click the last option 'install to inactive slot after OTA'. Click confirm force flash. Reboot when prompted. Done - root kept intact. One thing I did find which may have been a one off, but it changed my default launcher from Nova back to Asus. Not a big deal, I just changed it back under 'default apps' in settings.

Will post mega mirror soon.

Note: incremental update won't work with rooted devices
[ASUS ROG Phone II Guides, News, & Discussion] atir usman butt:
Update faild 92%
[ASUS ROG Phone II Guides, News, & Discussion] atir usman butt:
92% reached updating suddenly update failed

92% reached updating suddenly update failed
[ASUS ROG Phone II Guides, News, & Discussion] reg66:
There's 2 links on telegram, just uploaded the other version in case the first link I posted is corrupt. See first post for new link
[ASUS ROG Phone II Guides, News, & Discussion] reg66:
[MENTION=3068510]panzerpig[/MENTION] I see you gave thanks to first post, was the first link OK for you? Did the update work? I'm wondering if the file is corrupt...
[ASUS ROG Phone II Guides, News, & Discussion] dennis96411:
I'm assuming they didn't bother enabling VoLTE for T-Mobile/AT&T like they did for ROG Phone 3?
[ASUS ROG Phone II Guides, News, & Discussion] 2nd4last:
failed 9% ?
[ASUS ROG Phone II Guides, News, & Discussion] panzerpig:
Havent installed it yet, but it downloaded ok. (need to fix my fingerprint from china to WW..
[ASUS ROG Phone II Guides, News, & Discussion] atir usman butt:
My update successfully
[ASUS ROG Phone II Guides, News, & Discussion] atifx:
Can someone verify the battery life for this update? Last update ruined it for me
[ASUS ROG Phone II Guides, News, & Discussion] MelquiXDA:
Please don't update. This update has a serious bug (OMG Asus)

https://zentalk.asus.com/en/discussion/36275/high-temperature-cpu-usage-battery-drain-on-2009-47/p1
[ASUS ROG Phone II Guides, News, & Discussion] reg66:
Will add to OP. Cheers.
[ASUS ROG Phone II Guides, News, & Discussion] reg66:
See screenshot, it seems its a Google issue causing the cpu spikes to max. This would tie up with my device not having max cpu possibly because I'm running the Google beta services