Skip to main content
  1. Home
  2. Phones
  3. Business
  4. Mobile
  5. News

Qualcomm faces a potential $900 million fine in South Korea over unfair market practices

Add as a preferred source on Google

Qualcomm is in hot legal trouble yet again, as the California-based processor manufacturer finds itself on the wrong side of a potential $900 million fine that South Korea’s Fair Trade Commission looks to dole out, reports The Korea Times.

According to the government agency, which concluded a 17-month investigation into the matter, Qualcomm breached fair trade rules by abusing its position in the mobile processor market. The conclusion was that Qualcomm charged phone manufacturers excessively high licensing fees by basing its calculations on a phone’s wholesale price rather than its processors.

Recommended Videos

“Qualcomm has been collecting royalty fees from mobile phone manufacturers based on certain fixed rates from the suggested price of a mobile device,” said an FTC official. “Qualcomm should have sought royalty fees based on each chipset.”

The Korean newspaper reports that Qualcomm collects $1.27 billion annually in royalty fees from South Korean phone manufacturers like Samsung and LG, with the South Korean market accounting for 16 percent of Qualcomm’s sales last year. For its part, Qualcomm said that it significantly helped these phone makers become some of the top dogs in the phone market.

Whether or not there’s truth to that statement, the FTC may fine Qualcomm close to a billion dollars for its transgressions, with the government agency set to close the case by year’s end. If the number sticks, it will be the highest monetary penalty the FTC has ever issued toward a company.

As alluded to earlier, Qualcomm was fined $975 million by China’s National Development and Reform Commission (NDRC) in 2015 for abusing its position as market leader with high licensing costs and royalties. As a result of the anti-trust case, Qualcomm changed its licensing practices, with the company creating revised patent agreements after the case.

More recently, Qualcomm filed a complaint against Meizu, accusing the Chinese phone manufacturer of using its technologies without the correct licenses. The case is currently ongoing.

Williams Pelegrin
Williams is an avid New York Yankees fan, speaks Spanish, resides in Colorado, and has an affinity for Frosted Flakes. Send…
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more