Most active commenters

    ←back to thread

    AirPods libreated from Apple's ecosystem

    (github.com)
    1424 points moonleay | 11 comments | 16 Nov 25 00:01 UTC | HN request time: 0.521s | source | bottom
    Show context
    moonleay ◴[16 Nov 25 00:02 UTC] No.45941605[source]▶
    A cool project, when you want to use AirPods outside of Apples ecosystem. Sadly, you have to use a rooted android device with a small patch due to a bug in the Android Bluetooth implementation. https://issuetracker.google.com/issues/371713238
    replies(6): >>45942063 #>>45942373 #>>45942451 #>>45943437 #>>45943943 #>>45944340 #
    1. cbsks ◴[16 Nov 25 01:52 UTC] No.45942063[source]▶
    That is such a typical bug report to a large company. A user who spent a lot of time debugging and finding the root cause of an issue, and a few faceless peons at the large company spending a few minutes on it, realizing it’s not a priority, and abandoning it.
    replies(3): >>45942089 #>>45942124 #>>45942183 #
    2. fragmede ◴[16 Nov 25 01:55 UTC] No.45942089[source]▶
    And not a small bug either. This large an interoperability issue and it takes a nerd not in the employ of Google to fix their shit? This is why Apple's vertical integration makes it one of richest companies in the world. Google's only up there because of their success in that one business of theirs.
    replies(1): >>45942113 #
    3. mhluongo ◴[16 Nov 25 02:01 UTC] No.45942113[source]▶
    Funny, I was under the impression that Apple's stuff is closed source, so no one outside their employ even could fix a similar issue?
    replies(3): >>45942132 #>>45942384 #>>45942562 #
    4. fragmede ◴[16 Nov 25 02:05 UTC] No.45942132{3}[source]▶
    What does Apple being Apple have to do with Google not paying somebody to work on getting Airpods, which presumably should conform to some Bluetooth spec, in order to get Airpods to work on Android?
    replies(1): >>45942395 #
    5. netsharc ◴[16 Nov 25 02:15 UTC] No.45942183[source]▶
    Ah, when "open source" means begging an advertisement company to bless your code changes...
    replies(2): >>45942386 #>>45943040 #
    6. butvacuum ◴[16 Nov 25 02:56 UTC] No.45942384{3}[source]▶
    Apparently, android isn't fixing it either.
    7. charcircuit ◴[16 Nov 25 02:56 UTC] No.45942386[source]▶
    It was a hack. An actual code change would be submitted via the gerrit and not buganizer.

    https://android-review.googlesource.com/q/status:open+-is:wi...

    replies(1): >>45943569 #
    8. catlikesshrimp ◴[16 Nov 25 02:57 UTC] No.45942395{4}[source]▶
    >>...due to a bug in the Android Bluetooth implementation.

    The issue can be resolved because an android bug can be debugged by a contributor. A similar issue can't even be analyzed from the apple side by anyone but an apple employee.

    We are assuming there are bugs in iOS, but their closed sourceness can mislead people to believe there aren't. Then, yes, their vertical integration makes them rich, which in this case is bad for users, in the guise of being good.

    9. justinclift ◴[16 Nov 25 03:39 UTC] No.45942562{3}[source]▶
    Bearing in mind that Apple does Open Source some stuff: https://opensource.apple.com/projects

    They also Open Source the base OS layer pieces for macOS too:

    * https://github.com/apple-oss-distributions/

    * https://opensource.apple.com/releases/

    I don't keep any kind of close eye on this stuff though.

    10. Aurornis ◴[16 Nov 25 05:39 UTC] No.45943040[source]▶
    Not really. There wasn’t a true patch attempt submitted, as far as I can see. There was some helpful info about how commenting out a couple lines could work around the issue, but doing a real engineering evaluation to check spec compliance and make sure it’s all covered in the Bluetooth testing infrastructure is a much bigger task.
    11. IshKebab ◴[16 Nov 25 08:20 UTC] No.45943569{3}[source]▶
    Yeah except nobody is going to put the effort in to do that because they know it will be ignored.

    I tried back in the day.