Maxi 11x 💉<p>Zu "Google erschwert Entwicklung alternativer Android-Varianten für <a href="https://chaos.social/tags/Pixel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pixel</span></a>-Smartphones" (durch Nichtherausgeben einiger Treiber und HW-Infos)</p><p><a href="https://chaos.social/@suka_hiroaki/114687074255867211" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">chaos.social/@suka_hiroaki/114</span><span class="invisible">687074255867211</span></a></p><p>»This is what <a href="https://chaos.social/tags/JBQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JBQ</span></a> quit over. Just for people following along. </p><p>He quit because they were blocking this at the silicon level. And he said that was unethical. And he made the operating system. </p><p>Now Google may be doing it themselves.«</p><p><a href="https://x.com/chrisprice/status/1933049413666300091" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">x.com/chrisprice/status/193304</span><span class="invisible">9413666300091</span></a></p><p>2013: JBQ leaves <a href="https://chaos.social/tags/AOSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AOSP</span></a>, Qualcomm to blame</p><p><a href="https://www.osnews.com/story/27250/jbq-leaves-aosp-qualcomm-to-blame/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">osnews.com/story/27250/jbq-lea</span><span class="invisible">ves-aosp-qualcomm-to-blame/</span></a></p>