←back to thread

1424 points moonleay | 6 comments | | HN request time: 0.001s | source | bottom
Show context
isoprophlex ◴[] No.45943174[source]
From a bit further down the page

> Bluetooth DID (Device Identification) Hook > Turns out, if you change the manufacturerid to that of Apple, you get access to several special features!

I hope Apple gets slammed hard by some regulatory body. Apparently there's absolutely zero magic reasons why their airpods are unable to connect to non-Apple devices; pretend you're an iPhone and you're in.

EDIT: read "unable to connect" => "unable to expose advanced functionality", ofc they connect just fine

replies(15): >>45943218 #>>45943230 #>>45943299 #>>45943335 #>>45943389 #>>45943452 #>>45943491 #>>45943620 #>>45943639 #>>45943933 #>>45944000 #>>45945287 #>>45945990 #>>45946884 #>>45950063 #
exitb ◴[] No.45943230[source]
AirPods can connect to any device and perform on par with other Bluetooth headphones. This is about availability of special features which require a dedicated driver non-Apple devices are not expected to have.
replies(6): >>45943697 #>>45944080 #>>45944871 #>>45946495 #>>45947945 #>>45952870 #
kakacik ◴[] No.45943697[source]
This is patently incorrect. Wife switched from iphone 13 mini to samsung s24, and airpods pro 2nd gen immediately started behaving extremely annoyingly to the point of becoming completely useless for any serious use and she just gave them away to her sister which still is on apple, although she loved them before.

Literally all other earpieces work flawlessly with that phone including dirt cheap chinese stuff, apart from apple.

Now somebody could come and claim multi trillion company couldnt just nail that pesky bluetooth protocol well, but everybody else can do it better than them, including 15 bucks products. Its all by design. They clearly dont need hardware revenue to have products who can compete on open market, they need their closed ecosystem revenue, hence these dirty practices. There is hopefully a billion or ten lawsuit in the making by courts with balls, ie EU.

All the downvotes in the world won't change above.

replies(7): >>45943711 #>>45943798 #>>45943858 #>>45943953 #>>45945416 #>>45945540 #>>45945944 #
talkingtab ◴[] No.45945416[source]
Just take apple to small claims court. If everyone who is scammed by Apple takes them to small claims they will have an incentive to change. Without this they have -0.00000000000 incentive to do anything. Even a class action suit won't help. The fundamental question is whether Apple should be able to sell products with lock in. Since there is lockin on all Apple products it is not accidental. In my humble opinion only. You, dear reader, work out your own thoughts.
replies(2): >>45945859 #>>45946712 #
1. thewebguyd ◴[] No.45946712[source]
> The fundamental question is whether Apple should be able to sell products with lock in.

Unpopular opinion in these parts, but I think yes, they should be able to (continue) to sell products with lock in.

Where Apple should get in trouble is specifically locking others out, rather than locking their own stuff in. If Apple wants to make a smartwatch that only works with iPhones, fine. What they shouldn't be able to do is block (either intentionally or via undocumented/private APIs and TOS violations) third parties from making a smartwatch for iPhone that can compete on the same playing field as the Apple Watch, with access to all of the same features.

Same goes for all tech companies. If you want to lock-in your own first party products, fine, but you absolutely should not be allowed to lock-out others.

replies(2): >>45947528 #>>45947540 #
2. Wowfunhappy ◴[] No.45947528[source]
I'm not entirely sure if the distinction you're making exists.

Let's say I'm Samsung and I want to make a phone that works with the Apple Watch. Isn't the Apple Watch locking me out? Apple is preventing third party devices from working with the Apple Watch.

replies(2): >>45947689 #>>45962106 #
3. gdwatson ◴[] No.45947540[source]
Could you explain your reasoning? I don’t see any moral difference between deliberately limiting compatibility from the peripheral side and doing so from the “computer” side (i.e., iPhone, iPad, Macintosh). One type of device may produce more inadvertent incompatibilities than the other, but that’s different.

Besides, I think this will create surprise and confusion for less technical users. In my experience, many will blame the incompatibility on whichever device is new, without understanding who is gating out whom. And even for technical users, consider CarPlay and Android Auto: From the phone’s perspective, the car is a peripheral, and that makes sense; but lots of people will still consider the car the “core device.”

4. thewebguyd ◴[] No.45947689[source]
I’m saying it’s fine for Apple to make first party tech that only works either their other tech.

Samsung not being able to make a phone to work with Apples first party accessory isn’t the problem.

The problem is Samsung can’t make a watch that functions on par with the Apple Watch on iPhones.

Having first party, integrated accessories is fine. Locking out third party accessories is the issue.

Whatever Apple makes first party for the iPhone , third parties should also be able to make for the iPhone with the same level of access and functionality.

replies(1): >>45947750 #
5. Wowfunhappy ◴[] No.45947750{3}[source]
I think the line between accessory and non-accessory is really slippery. When the iPhone was released, I think it would have been correct to call it an accessory for your computer. When did that change, exactly?

Heck, I don't really think of my Apple Watch as an accessory. Mine has its own LTE connection; it does need to be connected to an iPhone during initial setup, but after that I don't think there's anything stopping me from giving my phone away and using the watch by itself. Many of the children I teach have an Apple Watch but don't own a phone yet.

6. gblargg ◴[] No.45962106[source]
If a company figures out how to make Apple products work with theirs, the line is between whether Apple modifies the firmware or future devices specifically to prevent this from working.