2026-10-24T20:29:50Z https://nostr.now GrapheneOS https://nostr.now/npub1kwarc5z9lwhen05uknd2nuwhhthd4ws0cku3t9j3rchm0fcd6luslse0nj https://grapheneos.social/system/accounts/avatars/109/415/078/265/909/169/original/c74b93c7870e37a0.png https://grapheneos.social/system/accounts/avatars/109/415/078/265/909/169/original/c74b93c7870e37a0.png https://nostr.now/nevent1qqs2dzr424ft7tealeavy4vv47cudk20kwwgm8tyk2080j484k9suvgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj9wpn7m In reply to <a href='/nevent1qqsd4wr3us920rtzc075lkdfuds04e4uukh6e8pd7287gtvatm5g4ssm38whv'>nevent1q…8whv</a><br/>_________________________<br/><br/>We&#39;re building new experimental OS releases now after resolving the Wi-Fi suspend issue. There&#39;s also likely a PCIe power saving regression to solve. There will be lots of other issues to solve but the end result of using the 6.18 GKI LTS and then getting rid of GKI ABI stability will be much nicer. 2026-10-28T04:51:20Z https://nostr.now/nevent1qqsd4wr3us920rtzc075lkdfuds04e4uukh6e8pd7287gtvatm5g4sszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljqhk6hx In reply to <a href='/nevent1qqsf6h253e6j9fgknmlmr034lm87nd6aumkragqu9ntmjadcvwxyzysz2fq5p'>nevent1q…fq5p</a><br/>_________________________<br/><br/>We&#39;ve resolved the lockup occurring during USB transfers which turned out to be caused by a pKVM bug in the common kernel tree. This is the third pKVM bug we&#39;ve fixed for 6.18 as part of the port. We also fixed an occasional early boot crash caused by a race. There&#39;s a Wi-Fi issue left to resolve. 2026-10-28T02:49:02Z https://nostr.now/nevent1qqsdvjepgshd7uvpl3pu79nxzg5jk9xjsggw4lr7dyqfms7m5wzm0jszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljxpzp2g Vanadium version 156.0.8078.73.0 released:<br/><br/><a href="https://github.com/GrapheneOS/Vanadium/releases/tag/156.0.8078.73.0">https://github.com/GrapheneOS/Vanadium/releases/tag/156.0.8078.73.0</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/43144-vanadium-version-15608078730-released">https://discuss.grapheneos.org/d/43144-vanadium-version-15608078730-released</a><br/><br/>#GrapheneOS #privacy #security #browser 2026-10-28T02:29:50Z https://nostr.now/nevent1qqsf6h253e6j9fgknmlmr034lm87nd6aumkragqu9ntmjadcvwxyzyszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljp304mv In reply to <a href='/nevent1qqsw2rq23glv0t0xtmqhwc2rr7exv2lznayf7az83am3wgtap6p3clczdc3ax'>nevent1q…c3ax</a><br/>_________________________<br/><br/>Our goal is get a port to 6.18 GKI LTS shipped within a couple months and a port to the upstream 6.18 LTS shipped within several more months. Once we&#39;ve achieved that, it will be much easier to ship each LTS release and we can move to the upcoming LTS release after it stabilizes for around 6 months. 2026-10-28T01:31:31Z https://nostr.now/nevent1qqsw2rq23glv0t0xtmqhwc2rr7exv2lznayf7az83am3wgtap6p3clczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj08ys6v In reply to <a href='/nevent1qqsdwjdwx94qnr9esd96584hvzjjt5vgcpmv9kl30505kjv9yt4739qgq9fgs'>nevent1q…9fgs</a><br/>_________________________<br/><br/>There are 2 main phases for our work on this. 1st phase is porting to the 6.18 GKI LTS branch and getting that into a production quality state. 2nd phase is porting from the GKI LTS branch to the upstream LTS branch with over a thousand extra backports and other downstream fixes kept intact. 2026-10-28T01:29:12Z https://nostr.now/nevent1qqsdwjdwx94qnr9esd96584hvzjjt5vgcpmv9kl30505kjv9yt4739qzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljffx6vm In reply to <a href='/nevent1qqs2l3pcuxd0cv4rmv43py7sy7era892rfzrnk3g4g3wt572jc0gvkcw9rk0v'>nevent1q…rk0v</a><br/>_________________________<br/><br/>We&#39;ve found a pKVM issue causing the device to lock up during large USB transfers. The initial releases have been removed and will be replaced with a new build in around 90 minutes at which point we&#39;ll put out another call for testing. This cycle will continue as issues are found and resolved. 2026-10-28T00:46:30Z https://nostr.now/nevent1qqs2l3pcuxd0cv4rmv43py7sy7era892rfzrnk3g4g3wt572jc0gvkczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj2xyr7h In reply to <a href='/nevent1qqsxynzxgl7cl4tsxkv7s8ftqu6mr2gnf3s550v4yr0xlcj34yn4wnsjc7ejp'>nevent1q…7ejp</a><br/>_________________________<br/><br/>Do not install the experimental releases unless you can tolerate regular freezes, kernel panics and broken hardware functionality. These are highly experimental and you should not expect the device to be very usable during the early testing. We&#39;ll make new releases with fixes for discovered issues. 2026-10-28T00:26:09Z https://nostr.now/nevent1qqsxynzxgl7cl4tsxkv7s8ftqu6mr2gnf3s550v4yr0xlcj34yn4wnszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljmpxddt In reply to <a href='/nevent1qqsxvzn03q5d88w48jvmnquyc03q8994t5lgn45xa0ajxftqdh040wqp3ed4k'>nevent1q…ed4k</a><br/>_________________________<br/><br/>These experimental releases have all of the changes from our current development branch and are security preview releases with the security preview patches from our previous release. We have 4 official build machines so we can build for all 4 devices in parallel and make new releases as people test. 2026-10-28T00:24:52Z https://nostr.now/nevent1qqsxvzn03q5d88w48jvmnquyc03q8994t5lgn45xa0ajxftqdh040wqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj5krc0a In reply to <a href='/nevent1qqs8ntka5pt8ssl52d97zhh6v2g3gl70ea8nprwaxhgxlpxwp0gmv8gcfd8sz'>nevent1q…d8sz</a><br/>_________________________<br/><br/>Users can update to these from our current releases and update from those to future experimental and regular releases. Hardware functionality should be the focus. Bluetooth / BLE, NFC, assorted Wi-Fi APs / standards, DisplayPort alt mode, USB peripherals, USB host modes, GNSS and NFC are examples. 2026-10-28T00:21:08Z https://nostr.now/nevent1qqs8ntka5pt8ssl52d97zhh6v2g3gl70ea8nprwaxhgxlpxwp0gmv8gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljnp3x6j In reply to <a href='/nevent1qqsxgd0h4rwfqepyfwna0ylw8754wx4a4rze72hug3z606n7ew9uytsqla4pd'>nevent1q…a4pd</a><br/>_________________________<br/><br/>If you&#39;re interested in helping with testing, please join either our #testing:grapheneos.org channel on Matrix or #testing on our Discord server. We&#39;ve posted links to over-the-air updates for each of the 4 releases in both channels. These are production builds signed with the official signing keys. 2026-10-28T00:17:26Z https://nostr.now/nevent1qqsxgd0h4rwfqepyfwna0ylw8754wx4a4rze72hug3z606n7ew9uytszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljermkev In reply to <a href='/nevent1qqs8ex5en6advdw4chkcdznkgpkmwj74njs9kqh92uqgx375gzasfds2admep'>nevent1q…dmep</a><br/>_________________________<br/><br/>People should only help with testing this if they&#39;re able to tolerate regular kernel panics and various hardware functionality not working. We&#39;ve done basic testing of Wi-Fi, Bluetooth, cellular, GNSS, Vulkan and virtual machines via the Terminal app and microdroid API but there&#39;s far more to test. 2026-10-28T00:13:43Z https://nostr.now/nevent1qqs8ex5en6advdw4chkcdznkgpkmwj74njs9kqh92uqgx375gzasfdszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljevr4eh Experimental releases of GrapheneOS with our initial port to the Linux 6.18 branch are now available for testing on the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold. We&#39;ve done initial testing but there will likely be at least a dozen more crashes and other issues to find and fix. 2026-10-28T00:11:30Z https://nostr.now/nevent1qqs973lfzj3278a2mw02h0xl8c8dhy2ntjmkea3m55ptsf4zmcswpyczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlje58vdd In reply to <a href='/nevent1qqs9pu6njdwqgmu2w4jyk3znset7tfrpar4k6qnqycdngt3pl8x65cgthm3v3'>nevent1q…m3v3</a><br/>_________________________<br/><br/>There are many published exploits on GitHub for vulnerabilities in the Linux kernel and other projects which are directly usable against most Android devices not keeping up with privacy and security updates. /e/ is particularly bad at keeping up with these updates. It&#39;s not fearmongering to point out that going years without shipping important privacy and security patches/protections is a disaster. It&#39;s increasingly bad in the age of AI models able to generate working exploits. 2026-10-27T16:39:36Z https://nostr.now/nevent1qqsw0hhng2qpmx7l3tjvajx640awygg5a7ppyvkvtv2hrn4wy90k3cczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj07x5pz In reply to <a href='/nevent1qqswkjdsum4fls6evjxy462j4qy3420tt9lcqydzgzgftus2adgksxsjpvn2c'>nevent1q…vn2c</a><br/>_________________________<br/><br/>Murena have spent years misleading people about GrapheneOS as part of falsely marketing phony privacy products. The same applies to dozens of other companies.<br/><br/>/e/ and their for-profit company Murena have repeatedly pushed anti-privacy talking points from authoritarians claiming devices with strong privacy and security are for criminals and pedophiles. Here are two of many examples:<br/><br/><a href="https://x.com/GrapheneOS/status/2040887784253141142">https://x.com/GrapheneOS/status/2040887784253141142</a><br/><br/><a href="https://clubic.com/actualite-604786-murena-e-os-interview.html">https://clubic.com/actualite-604786-murena-e-os-interview.html</a><br/><br/>We aren&#39;t on the same side and never were. 2026-10-27T15:04:55Z https://nostr.now/nevent1qqsfznafgd0d6qagqaq3lk08skncgl3s2ys5ue90zv2k6x78g5m4r8qzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljj5r9ng In reply to <a href='/nevent1qqs8e4vvzdzjztehwsqxdsu8k0w5l67g9c4vs0fs96pre3qzc4v2sscp0ezvv'>nevent1q…ezvv</a><br/>_________________________<br/><br/>Sandboxing requires a lot of work from the OS and application ecosystem to use it. /e/ doesn&#39;t keep the standard Android app sandbox and permission model fully intact. It lags far behind on privacy/security patches and updates to new releases addressing major issues with the sandbox and permission model. It opens up new holes with the changes it makes too. microG on /e/ doesn&#39;t run as a regular app but rather in a privileged domain and so does the Google Play code it downloads. 2026-10-27T15:03:06Z https://nostr.now/nevent1qqsvca2su2dzjg8ux3sla8r5wg7d52u08zzz8znc2s74xmee077t8yczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljkzylzm In reply to <a href='/nevent1qqs0ncd6ru3uwn6vje8tls77w98eqxe9y36rlt4nareg6hff9cfk6hqaknwx5'>nevent1q…nwx5</a><br/>_________________________<br/><br/>We care about people having privacy and they&#39;re not going to get that by buying phony privacy products from companies blatantly scamming people. iodéOS is not what it claims to be and does not provide what it claims. It can be evaluated objectively and many people have done so. A device that&#39;s consistently months to years behind on bare minimum standard updates is increasingly unsafe to use.<br/><br/>Privacy is not provided by branding and marketing products as private. 2026-10-27T15:00:33Z https://nostr.now/nevent1qqs956eh8emhve0fv4p8xfrak98paewsf898cel59nxweycgd0zpzjgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljkwdcpz In reply to <a href='/nevent1qqsqctlfnszjnt6ymqw6l2maxc67yju9tuhsdwvzyve6gx2r23u6qcquxfk2f'>nevent1q…fk2f</a><br/>_________________________<br/><br/>Those devices are nearly direct opposites of each other. Fairphone 5 has an end-of-life Linux kernel without security support and lags multiple months to a year behind on providing bare minimum patches to other components. There are a bunch of working exploits on GitHub.<br/><br/>CalyxOS greatly rolls back the privacy and security of AOSP rather than improving those as GrapheneOS does. It recently took multiple months to provide standard updates and previously went a whole year without any. 2026-10-27T14:56:12Z https://nostr.now/nevent1qqs2spf4ectd42953vv0pzmnu2e0kuzy6vtr5u5qrja7e3stx70hrpqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj3076d9 In reply to <a href='/nevent1qqs284z7mmdyfdnrhape4fr30nlj7a2neya0ep4nufe46pnjv4qv29cqpnlak'>nevent1q…nlak</a><br/>_________________________<br/><br/>/e/, iodéOS and CalyxOS do not keep up with the standard privacy and security patches or protections. They do not make similar enhancements to privacy and security. They go in the opposite direction by lagging many months and even years behind on updates.<br/><br/>Android Security Bulletins are incomplete backports of Android privacy/security patches to older releases. Those aren&#39;t the full patches and already come with a delay. Only shipping those with weeks of delay is increasingly bad. 2026-10-27T14:50:31Z https://nostr.now/nevent1qqs284z7mmdyfdnrhape4fr30nlj7a2neya0ep4nufe46pnjv4qv29czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljyeryrl In reply to <a href='/nevent1qqsgelqwg6s3kvrjjy3v2ccx9elzvq603h0sexxdqyel2lllljqmtag2dnynq'>nevent1q…nynq</a><br/>_________________________<br/><br/>GrapheneOS is a privacy project with major privacy enhancements including Contact Scopes, Storage Scopes, secure paste and much more. It doesn&#39;t connect to any third party services by default and has a very limited set of default connections which are documented and can be controlled by users.<br/><br/>GrapheneOS preserves the standard privacy/security of AOSP by keeping up with updates and enabling all of the protections. It also provides far better patches than AOSP and the Pixel OS. 2026-10-27T14:48:53Z https://nostr.now/nevent1qqspg84e579nxfe5xf9y7h33nr69jkwk2s0sx79rcrcejyqt0a46lmszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj3q0m6l In reply to <a href='/nevent1qqsgns2wk6tl84de5mdv3ma3pzhjzhuqf8vedfszl2zhzq2hdqcsqzqufvpzz'>nevent1q…vpzz</a><br/>_________________________<br/><br/>iodéOS greatly rolls back privacy and security compared to the Android Open Source Project. It lags far behind on privacy/security patches and protections. It isn&#39;t a reasonably safe option and doesn&#39;t provide what it&#39;s marketed as doing.<br/><br/>The badness enumeration approach you&#39;re talking about doesn&#39;t protect against the most privacy invasive behaviors by apps and services. It&#39;s easy to bypass and increasingly doesn&#39;t work. There are also better open source implementations for free. 2026-10-27T14:45:21Z https://nostr.now/nevent1qqsql2duup35643jtkxthgtpy3g5fccep68a7uhw48hwcnll4ymgq5czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj0x2z7x In reply to <a href='/nevent1qqs0ulfexg4xmjd0nhwpqe0zg7juv66g4xyqqeu6j88rexzmjvtuuscnd62pl'>nevent1q…62pl</a><br/>_________________________<br/><br/>Unlike /e/, GrapheneOS doesn&#39;t connect to Google services by default and doesn&#39;t provide privileged access to Google apps and services when those are installed. Google apps run in the standard sandbox if they&#39;re installed. microG doesn&#39;t run in the standard sandbox but rather as a privileged app similar to Google Play on the stock OS. On /e/, microG downloads and runs closed source Google Play code with the privileged access it has by default as part of providing compatibility. 2026-10-27T14:36:31Z https://nostr.now/nevent1qqszxjwqrsq5pq04swn2kvrl0wdtypkzl6xqvvt366vhdpv05qqywngzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljt6zvcv In reply to <a href='/nevent1qqspy7ypw23j2de87lu5j63f9vnay46kp2yadkdlh3c80atqx2yj6sgpuk2ay'>nevent1q…k2ay</a><br/>_________________________<br/><br/>No, /e/ always uses Google services without a way to disable it. It has highly privileged integration for Google services not present in the Android Open Source Project. It makes a large number of connections to Google by default and doesn&#39;t support disabling all of it. microG sits in between the Google libraries used by apps and Google services. It has highly privileged access. On /e/, it downloads and runs Google Play executable code with privileged access by default. 2026-10-27T14:35:10Z https://nostr.now/nevent1qqsya4fn9wpx9qsr9acyxd59vj9s79wv5uehg8gnfdad5p5vc0y2uvszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljh65duw In reply to <a href='/nevent1qqsq4jumqyqfw03erwnx2xxkcunc9whtpdaegyhvkt8qx2lh5fz7utg54gh0c'>nevent1q…gh0c</a><br/>_________________________<br/><br/>GrapheneOS is not a niche OS for people targeted by state actors as you&#39;re implying. It&#39;s a privacy project backing that up with serious privacy and security enhancements. Unlike Fairphone and /e/, GrapheneOS preserves the standard privacy and security patches/protections of the Android Open Source Project. It provides very important privacy and security patches missing elsewhere along with major privacy and security enhancements. These are important to everyone, not rare attacks. 2026-10-27T14:31:37Z https://nostr.now/nevent1qqsq4jumqyqfw03erwnx2xxkcunc9whtpdaegyhvkt8qx2lh5fz7utgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljvtwzqa In reply to <a href='/nevent1qqs89lxrhka542sh0wfx7gvhv6utvhvklez375jyhardwa4d6ym8hpca2tffv'>nevent1q…tffv</a><br/>_________________________<br/><br/>Fairphones do not last as long as an iPhone or Pixel due to starting out with past generation hardware and not providing proper updates for it. The newly launched devices have 1-2 months of delays for the incomplete Android Security Bulletin backports to older releases. There&#39;s a year or more of delay for the full updates requiring the new OS releases. Firmware and driver updates are shipped very late. Linux kernel patches are largely not provided and are cut off after 2-3 years. 2026-10-27T14:29:40Z https://nostr.now/nevent1qqs89lxrhka542sh0wfx7gvhv6utvhvklez375jyhardwa4d6ym8hpczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljhr2m3y In reply to <a href='/nevent1qqsq3wjzqrv7yw8sax3y32zjh4j70y60nze4h42w6zay3umak2hk2egqdn08v'>nevent1q…n08v</a><br/>_________________________<br/><br/>Fairphones are white labelled devices made by an ODM. The current ODM since the Fairphone 4 is T2Mobile. Fairphone doesn&#39;t publish actual information on the working conditions, pay and environment impact of the assembly, manufacturing and supply chain for the devices. On their site, they provide a transparency report with a list of companies involved in making the devices. The information provided on each company is limited to the city they&#39;re based in and a website if available. 2026-10-27T14:26:54Z https://nostr.now/nevent1qqsq3wjzqrv7yw8sax3y32zjh4j70y60nze4h42w6zay3umak2hk2egzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj7krzhw In reply to <a href='/nevent1qqs9s90rqc0upeqvw9vvvmkem4r06qfhnwqk9l60mlhnjcn5paqev5sv8qzvz'>nevent1q…qzvz</a><br/>_________________________<br/><br/>Fairphones are insecure devices unable to provide a reasonable level of privacy and security. They don&#39;t provide proper updates from day one and they get increasingly bad over the lifetime of the device. Fairphone 5 and earlier already have end-of-life kernels and it will happen for the Fairphone 6 too. They do not provide the kind of long term support the devices are marketed as having. The devices end up prematurely obsolete and need to be replaced early for privacy and security. 2026-10-27T14:24:48Z https://nostr.now/nevent1qqsq5xvgsxgkee6c4tcztln9y28uw7zwzyf5u65v4dyc2q3902jdgyczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljxm3ahs In reply to <a href='/nevent1qqs9s90rqc0upeqvw9vvvmkem4r06qfhnwqk9l60mlhnjcn5paqev5sv8qzvz'>nevent1q…qzvz</a><br/>_________________________<br/><br/>/e/ drastically reduces both privacy and security compared to the Android Open Source Project. If you care at all about those, stay far away from it. The standard Fairphone software doesn&#39;t receive good updates and everything older than the Fairphone 6 has an end-of-life kernel but it&#39;s still better than /e/. /e/ and Murena products are not what they&#39;re marketed as being.<br/><br/>More information:<br/><br/><a href="https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private">https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private</a><br/><br/><a href="https://eylenburg.github.io/android_comparison.htm">https://eylenburg.github.io/android_comparison.htm</a><br/><br/><a href="https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt">https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt</a><br/><br/>GrapheneOS logo 2026-10-27T14:20:20Z https://nostr.now/nevent1qqsxlygkq4xmgdk9v4ux07x3w6ukveqvgh0t3ddqx5u65zww8ducz3qzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljdkundh In reply to <a href='/nevent1qqsfwjttes2au0luuuuj2juml3kche3t472d8a03jfunflqvq44c3rqeurwys'>nevent1q…rwys</a><br/>_________________________<br/><br/>/e/ drastically reduces both privacy and security compared to the Android Open Source Project. If you care at all about those, stay far away from it. The standard Fairphone software doesn&#39;t receive good updates and everything older than the Fairphone 6 has an end-of-life kernel but it&#39;s still better than /e/. /e/ and Murena products are not what they&#39;re marketed as being.<br/><br/>More information:<br/><br/><a href="https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private">https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private</a><br/><br/><a href="https://eylenburg.github.io/android_comparison.htm">https://eylenburg.github.io/android_comparison.htm</a><br/><br/><a href="https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt">https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt</a> 2026-10-27T14:19:06Z https://nostr.now/nevent1qqsqg7apusrkzqdj8w5z2x6dwjwl9k24nx4hcattkfnqddge0r76s9szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlje6aq2t In reply to <a href='/nevent1qqsyya0gpumx60gwur4q658khcuxpu9unqq0t3nl58lzqds39u27s9qlzf3jj'>nevent1q…f3jj</a><br/>_________________________<br/><br/>Fairphone 5 is a highly insecure device without basic privacy and security updates. It has an end-of-life Linux kernel branch with no security support and doesn&#39;t receive other important privacy and security updates. It&#39;s increasingly easy to exploit to the point that there are many exploits being shared on GitHub which can be used against it. It&#39;s not a safe device and there&#39;s no safe operating system available for it. /e/ drastically reduces privacy and security compared to AOSP. 2026-10-27T12:17:34Z https://nostr.now/nevent1qqs0xazag2xnqxxs5jfl3n7puse5umt9f2f5523ktzyx2342ufarc9szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj9dq4hy In reply to <a href='/nevent1qqsq0qusds7sh6e63f9qj4e7sa6xjkjd0egr6u3dmqjjz32jus6jd0cmqrktd'>nevent1q…rktd</a><br/>_________________________<br/><br/>That&#39;s likely a standard Android message. GrapheneOS changes the OS name from Android to GrapheneOS. There have been recent tzdata updates and there are ongoing changes such as DST either being made permanent or dropped in some regions.<br/><br/>By default, timezone selection is automatic based on what the cellular network says since it doesn&#39;t have the same security impact as changing the actual time due to only being for displaying the local time to humans based on an offset. 2026-10-26T18:51:36Z https://nostr.now/nevent1qqsd7q0d56z966n4r0u6j3j5xvyd0e8sgda5fyut49z2elmwe66f5ggzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj3jeprh In reply to <a href='/nevent1qqswmvfju5pcekwty2ec44t89qtmrgczdg4z6lapzs2hxy79rea3spsky7mr5'>nevent1q…7mr5</a><br/>_________________________<br/><br/>One issue has been found but turned out to be an upstream Android Launcher bug which we&#39;ve fixed for the next OS release:<br/><br/><a href="https://github.com/GrapheneOS/platform_packages_apps_Launcher3/pull/87">https://github.com/GrapheneOS/platform_packages_apps_Launcher3/pull/87</a><br/><br/>We&#39;re ready to move our new major release of TalkBack to Stable once we get more testing feedback in #testing on Matrix or Discord. 2026-10-26T18:24:46Z https://nostr.now/nevent1qqswmvfju5pcekwty2ec44t89qtmrgczdg4z6lapzs2hxy79rea3spszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljtar9yw GrapheneOS TalkBack version 23 released:<br/><br/><a href="https://github.com/GrapheneOS/TalkBack/releases/tag/23">https://github.com/GrapheneOS/TalkBack/releases/tag/23</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/43100-grapheneos-talkback-version-23-released">https://discuss.grapheneos.org/d/43100-grapheneos-talkback-version-23-released</a><br/><br/>#GrapheneOS #privacy #security 2026-10-26T02:40:42Z https://nostr.now/nevent1qqsf280yg4dcrdvwja2yld0w0w5qs4ut84fyf699p26tu083mducc8czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljrq7gmn GrapheneOS Messaging version 17 released:<br/><br/><a href="https://github.com/GrapheneOS/Messaging/releases/tag/17">https://github.com/GrapheneOS/Messaging/releases/tag/17</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/43079-grapheneos-messaging-version-17-released">https://discuss.grapheneos.org/d/43079-grapheneos-messaging-version-17-released</a><br/><br/>#GrapheneOS #privacy #security #android 2026-10-24T22:31:56Z https://nostr.now/nevent1qqs9ttgtsujuvavw9zmfsrkf6xp02q37wym2xtquaq9e37gzzgls0wczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljr7k4dl In reply to <a href='/nevent1qqs95t5pq8pddgd2xqyr56th0w06x6jwts974ehmyfndl9qhn28dkucfe5wth'>nevent1q…5wth</a><br/>_________________________<br/><br/>RCS works with GrapheneOS but currently the only available implementation of RCS is Google Messages. Samsung has a legacy RCS app shipped on older devices but replaced it with Google Messages. There are only 2 modern implementations of RCS: Google Messages and iOS. We plan on making our own for our Messaging app forked from AOSP Messaging but the initial implementation is going to need to use sandboxed Google Play for setting up RCS due to the proprietary number verification system. 2026-10-24T20:50:38Z https://nostr.now/nevent1qqsdh253rm0ymyf8wkqfl5fk7pa7yxkyt0w2f067nvveh0ql9ye6j0szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljs9nxgd In reply to <a href='/nevent1qqsyeagqrh09pm95k578urtmtnh9grtgyg46pjyj7z943p69sgjhj2gn04hrh'>nevent1q…4hrh</a><br/>_________________________<br/><br/>Most of the people reporting RCS no longer working were able to resolve it by enabling the ICC authentication toggle. It&#39;s likely the requirement to have it enabled was rolled out to more carriers. The remaining reports may all be non-GrapheneOS-related.<br/><br/><a href="https://grapheneos.org/usage#rcs">https://grapheneos.org/usage#rcs</a> 2026-10-24T20:33:14Z https://nostr.now/nevent1qqsyvx54wma36wphe3fpp3pkgkhjy3un0qcpm5gcwxsx9adgnwn8hzszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj7cq38f In reply to <a href='/nevent1qqsv4et7vj8xewxelwzshnlffat2ezdpdpuayvgsuupf97k979gp0eg26aauz'>nevent1q…aauz</a><br/>_________________________<br/><br/>SailfishOS is already largely closed source for the code specific to it and would be a far worse starting point than hard forking AOSP even if it wasn&#39;t. There are a lot of stakeholders in open source AOSP and it would be able to continue without Google. The fact that they haven&#39;t closed it is why it hasn&#39;t been split away by a group of organizations working on it together. Multiple organizations have made hard forks with varying degrees of success but there wasn&#39;t much reason to do it. 2026-10-23T19:19:01Z https://nostr.now/nevent1qqsd7glzlvw8ekugnm7ueg5m5luepl3wpm9kvxpahfyn94wqu2c6zrczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj3rertj In reply to <a href='/nevent1qqsqpcue66056j6ksssejryhetqrdc8d0uhmugek7stgjznajvxdt5qhwl3j0'>nevent1q…l3j0</a><br/>_________________________<br/><br/>There&#39;s a flagship device from Motorola with official support for GrapheneOS coming soon if you don&#39;t want to buy another Pixel. It will be a higher end alternative to the Pixel 10 Pro XL. Pixels will remain the budget option for quite a while, especially since the &#39;a&#39; series devices have the same 7 years of updates and security features as the high end device. It will take more time before Motorola devices below an ultra high end flagship meet all of our security requirements. 2026-10-23T18:42:30Z https://nostr.now/nevent1qqsqpcue66056j6ksssejryhetqrdc8d0uhmugek7stgjznajvxdt5qzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj06nk7a In reply to <a href='/nevent1qqsxmhuumj9tx5vng3zu8z9709d6hnx4rf46qlg83sx0xs8avhdwngqh9k4cc'>nevent1q…k4cc</a><br/>_________________________<br/><br/>GrapheneOS and AOSP are Linux distributions too. Linux isn&#39;t glibc, systemd, Bash, coreutils and Wayland. Many Linux distributions use a different libc, init, shell, command-line utilities and graphics layer if they even have one at all. Android having massive adoption and high usability doesn&#39;t mean it isn&#39;t Linux. Linux dominates mobile already.<br/><br/>SailfishOS doesn&#39;t use a typical desktop Linux software stack anyway but rather their own largely closed source UI and application layer. 2026-10-23T18:39:13Z https://nostr.now/nevent1qqsxmhuumj9tx5vng3zu8z9709d6hnx4rf46qlg83sx0xs8avhdwngqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljdzm330 In reply to <a href='/nevent1qqs8yvzz57p99ajsxxs5t83ak3cg8e0w5e6n8vpe8nung9tsrwspg9gsgj70j'>nevent1q…j70j</a><br/>_________________________<br/><br/>SailfishOS is a massive downgrade for privacy and security from the Android Open Source Project even without the GrapheneOS improvements. It doesn&#39;t provide decent patches and combines the insecurity of both desktop operating systems with a low-end Android device without proper updates. It also has much worse usability, app compatibilitiy and battery life.<br/><br/>Unlike the Android Open Source Project which is open source, SailfishOS has largely closed source code for the high level OS code. 2026-10-23T18:28:12Z https://nostr.now/nevent1qqs23ymtpcxazjt4e5wdd64rzd7lw4fkwds9ypd683skhu2x4nza4ngzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljg95mf5 GmsCompatConfig version 178 released:<br/><br/><a href="https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-178">https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-178</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/43045-gmscompatconfig-version-178-released">https://discuss.grapheneos.org/d/43045-gmscompatconfig-version-178-released</a><br/><br/>#GrapheneOS #privacy #security #gmscompat 2026-10-23T17:52:29Z https://nostr.now/nevent1qqs0wh56qc7zpf8w2002uj4pkwn78c0mw5vxvdc5wlhymwtnu9t0azgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj0syw7f In reply to <a href='/nevent1qqsdwmmcw5wkm6hc33jv94q2k99rc4ahffwm75u3yyvp4glclhgzywsup43lr'>nevent1q…43lr</a><br/>_________________________<br/><br/>AOSP is open source. Hardware and firmware being closed source is unavoidable and there&#39;s no alternative available without it. The kernel drivers are entirely open source but the userspace code for the drivers is not which will be replaced in the future. It isn&#39;t currently a priority. The userspace code can already be easily reverse engineered since it isn&#39;t obfuscated and has debug symbols. We reverse engineer it to solve problems all the time. It has become drastically easier recently. 2026-10-23T15:45:37Z https://nostr.now/nevent1qqst9n5s8hc9s5nfksddrhr590pu7unzg9gx3l4q5ge7sjt2exf9cwqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj49qk0l In reply to <a href='/nevent1qqs87md89zachlhkms2y2p7nk0fw4u5wx7s5mu3qqvsvmsauyy7ytgcln4702'>nevent1q…4702</a><br/>_________________________<br/><br/>Shipping this requires a long term commitment to porting all the relevant Pixel and Motorola/Snapdragon kernel drivers to the latest upstream LTS code. We&#39;ve determined that&#39;s much easier than expected. The hard part is making the device independent LTS with all the backports. 2026-10-22T22:05:55Z https://nostr.now/nevent1qqs87md89zachlhkms2y2p7nk0fw4u5wx7s5mu3qqvsvmsauyy7ytgczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljd8m9y9 In reply to <a href='/nevent1qqsfuatz8y4pthhe982c2jcfk0zezu0s0s5kjx7t45kfse5gj2wmu2g643zda'>nevent1q…3zda</a><br/>_________________________<br/><br/>We&#39;ve successfully made an initial port to using the upstream LTS branch for Pixels. We need to do a huge amount of code review and fixing regressions. Once we have it shipped, it will become trivial to ship each upstream revision, although those do often introduce regressions. 2026-10-22T22:05:50Z https://nostr.now/nevent1qqsfuatz8y4pthhe982c2jcfk0zezu0s0s5kjx7t45kfse5gj2wmu2gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljmeqqyc In reply to <a href='/nevent1qqsyz4letyj440qshk4hkqzz367fyycqfaqlxn5u5q7pgf74d8jd80syuydzg'>nevent1q…ydzg</a><br/>_________________________<br/><br/>GKI makes it extremely hard to maintain the Linux kernel LTS branch for Android. It serves no real purpose and yet requires a massive amount of work to keep it going. It&#39;s adding months of delays to the stock Pixel OS kernel updates and doesn&#39;t help any Android OEM in practice. 2026-10-22T22:05:42Z https://nostr.now/nevent1qqsyz4letyj440qshk4hkqzz367fyycqfaqlxn5u5q7pgf74d8jd80szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljdkd7r2 In reply to <a href='/nevent1qqsfsjddfwyv2lz8mluc5yzzmxp4ny92hl8ctc2w524yemt3qsnydlsp8u5g7'>nevent1q…u5g7</a><br/>_________________________<br/><br/>Google wasted an enormous amount of resources to develop GKI. It was supposed to make it much easier to keep Android devices on an up-to-date kernel. It&#39;s a disastrous failure. It does not make it substantially easier because updating kernel drivers for LTS ABI changes is easy. 2026-10-22T22:04:53Z https://nostr.now/nevent1qqsfsjddfwyv2lz8mluc5yzzmxp4ny92hl8ctc2w524yemt3qsnydlszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljhtlnqc In reply to <a href='/nevent1qqsqxxxlkg8re8t7q56ancna0wrp7h7xr7645gyr0n94nf67nqe3l7g9pkmfq'>nevent1q…kmfq</a><br/>_________________________<br/><br/>All of the kernel drivers for any devices we&#39;ll support are open source. It would be an egregious violation of the GPL to ship driver code specific to Linux without providing all the source code. The drivers are updated alongside the kernel so there&#39;s no actual use case for GKI. 2026-10-22T22:04:48Z https://nostr.now/nevent1qqsqxxxlkg8re8t7q56ancna0wrp7h7xr7645gyr0n94nf67nqe3l7gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljerpk5z In reply to <a href='/nevent1qqspuhuapacwgq7tey8zl5dxktf96r8yq7sece6gukyshc9my7n0wncq4al2e'>nevent1q…al2e</a><br/>_________________________<br/><br/>The main purpose of the Android GKI branch is to implement a stable ABI for kernel drivers. The ABI is only stable within an LTS branch. It has no practical use case and a massive maintainability cost. This system collapsed under the massive increase in Linux kernel patches. 2026-10-22T22:04:43Z https://nostr.now/nevent1qqspuhuapacwgq7tey8zl5dxktf96r8yq7sece6gukyshc9my7n0wnczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj4a4gaf In reply to <a href='/nevent1qqs03ns5qp3wl7fr92gta0xc54vrp997wd0yfu9eawjfvj4pfndf0wgw4dxye'>nevent1q…dxye</a><br/>_________________________<br/><br/>The upstream Linux kernel LTS branches backport a enormous amount of bug fixes including a massive number of security fixes. Android backports much more because they want to ship many of the performance improvements, new features and additional fixes with older LTS branches. 2026-10-22T21:35:58Z https://nostr.now/nevent1qqs03ns5qp3wl7fr92gta0xc54vrp997wd0yfu9eawjfvj4pfndf0wgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljet5m2g In reply to <a href='/nevent1qqsxpws9vpa5up5jwtq7886jjrazxk888waxlj536lz2937j8y9fvys6scc9g'>nevent1q…cc9g</a><br/>_________________________<br/><br/>The changes required to move the Pixel drivers from 6.1, 6.6 and 6.12 to 6.18 are tiny. The changes needed to use the upstream 6.18 LTS ABI instead of the stable 6.18 GKI LTS ABI are larger but quite manageable. It&#39;s preserving all the extra improvements which is extremely hard. 2026-10-22T21:33:33Z https://nostr.now/nevent1qqsxpws9vpa5up5jwtq7886jjrazxk888waxlj536lz2937j8y9fvyszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljd6u90x In reply to <a href='/nevent1qqsyf8yfwdqnagy7s4p6gnr9p8xwuz29d8cam5mvh67vxaywspcwyfg8nlh8f'>nevent1q…lh8f</a><br/>_________________________<br/><br/>Porting from the 6.1, 6.6 and 6.12 GKI LTS branches to the 6.18 GKI LTS branch is relatively simple and doesn&#39;t require a large number of changes.<br/><br/>Porting from GKI LTS to the upstream LTS branch is much harder. Android has thousands of extra backported fixes and improvements. 2026-10-22T21:31:32Z https://nostr.now/nevent1qqsyf8yfwdqnagy7s4p6gnr9p8xwuz29d8cam5mvh67vxaywspcwyfgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljnexxs0 In reply to <a href='/nevent1qqs2p9qeaea62v6kprhktra4h5692df45drekrvskznendvhr9l6vtsweeaml'>nevent1q…eaml</a><br/>_________________________<br/><br/>We have a Pixel 7 working with the upstream Linux 6.18.58 release. We&#39;ll be getting all supported devices fully working with all hardware functionality. The upcoming Motorola flagship uses a fork of the 6.18 GKI LTS branch and we&#39;ll need to port it to the upstream kernel too. 2026-10-22T21:27:46Z https://nostr.now/nevent1qqs2p9qeaea62v6kprhktra4h5692df45drekrvskznendvhr9l6vtszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljtex8dc In reply to <a href='/nevent1qqsftvmyfdlkdd5300lcsgp2jqtxtkzce535gtxax8jszhkgac3pw6gp8774g'>nevent1q…774g</a><br/>_________________________<br/><br/>In the past several months, Android&#39;s official Generic Kernel Image (GKI) branches have fallen behind the upstream LTS revisions. We&#39;re resolving this by moving all of the devices we support to the latest LTS branch and making a GKI replacement for the latest upstream release. 2026-10-22T21:25:20Z https://nostr.now/nevent1qqsftvmyfdlkdd5300lcsgp2jqtxtkzce535gtxax8jszhkgac3pw6gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljmqerr0 Our latest OS release moved to using the Linux 6.18 LTS branch for both arm64 and x86_64 for the emulator, Cuttlefish and microdroid targets. We&#39;ve made a highly experimental port of the Pixel kernel drivers to 6.18 and are planning on moving to it across all supported devices. 2026-10-22T21:21:32Z https://nostr.now/nevent1qqsyeagqrh09pm95k578urtmtnh9grtgyg46pjyj7z943p69sgjhj2gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljf292v9 In reply to <a href='/nevent1qqs8zydw0wxrrtu0dj3c8yrxd8z8zmten0uhw60027ak2dzmqcc0gxcfartwa'>nevent1q…rtwa</a><br/>_________________________<br/><br/>Resolving this before it impacts a much larger number of users is one of our highest priorities. It&#39;s likely only going to be possible to resolve it with an OS update rather than a GmsCompatConfig release. We&#39;ve only just started working on it so we don&#39;t know the cause yet. 2026-10-22T21:19:12Z https://nostr.now/nevent1qqs8zydw0wxrrtu0dj3c8yrxd8z8zmten0uhw60027ak2dzmqcc0gxczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj2cw338 Google made a change to their RCS service breaking using it for a small number of users. It&#39;s likely in the process of being rolled out and is gradually causing issues for more users. We&#39;re already working on resolving it. It isn&#39;t caused by the OS update about to move to Stable. 2026-10-22T21:17:46Z https://nostr.now/nevent1qqsxhj0537etf8pxdg8h7zru3edf4kehn9wvel9yzmeeu9scjumdrjqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljl0htu0 In reply to <a href='/nevent1qqspsq35j4ktv9kac8462qrnuhdjwfmfkf3e5snhkw69zr3wamtrjzq4yumrv'>nevent1q…umrv</a><br/>_________________________<br/><br/>Bluetooth has a very low data transfer rate and isn&#39;t well suited to large transfers.<br/><br/>You can directly connect 2 Android phones with USB and transfer data between them with MTP. Not clear if you did it that way or used another computer but you don&#39;t need to use another computer for it.<br/><br/>Our recollection is that Signal&#39;s wireless data transfer preserves safety numbers but the offline backups do not. Signal could provide a better way of doing this such as a network-based transfer. 2026-10-22T16:28:57Z https://nostr.now/nevent1qqsg9qc5s35fyqyxkanxgt7975707akprl4wk580jt5xfumcy5d3mtgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljjjdx0j In reply to <a href='/nevent1qqsx92kpgf3wdgary20rlghz9pmly80vmxykyflnthg8hy52fm2jhacyj4w30'>nevent1q…4w30</a><br/>_________________________<br/><br/>Android can ship root store updates via an APEX component update. However, APEX component updates require a reboot after installation. Google Mobile Services Android ships the root store updates via Google Play system updates. It typically takes multiple days or even weeks for a Google Play system update to trigger once it&#39;s available and then it doesn&#39;t kick in until after people reboot. It doesn&#39;t offer much over shipping an OS update and the point is working around OEMs not updating. 2026-10-22T11:29:01Z https://nostr.now/nevent1qqsx92kpgf3wdgary20rlghz9pmly80vmxykyflnthg8hy52fm2jhaczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljk86kl8 In reply to <a href='/nevent1qqsq0fglhh50d8t29pw46et3rkp7kqm8qz22ezvptswzl8c7vzs2lac3d0y3z'>nevent1q…0y3z</a><br/>_________________________<br/><br/>Very few apps reduce the trusted root set. Many apps do pin keys but the vast majority don&#39;t do it. A lot of apps are targeting Android 17 so CT enforcement blocks new certificates issued with the root with the insecure intermediates. Most apps don&#39;t perform revocation checking but rather it&#39;s nearly entirely exclusive to browsers through distributing bundles of revocations. Android will likely start distributing the root store and bundles of revocations dynamically in the near future. 2026-10-22T11:27:25Z https://nostr.now/nevent1qqsq0fglhh50d8t29pw46et3rkp7kqm8qz22ezvptswzl8c7vzs2laczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljcpxk0g In reply to <a href='/nevent1qqs8z7qdw2wmutv0333s8upflt5e9dkcr7p67xm84ez9ksmym6zpujgg0dl8w'>nevent1q…dl8w</a><br/>_________________________<br/><br/>Android 17 has enforced Certificate Transparency (CT) enabled by default for apps targeting Android 17. Many apps are targeting Android 17 already but it&#39;s not mandatory for Play Store apps yet. Since the roots were untrusted by CT logs, it stopped being possible to make new certificates which would be trusted by Android&#39;s TLS implementation when CT is enforced.<br/><br/>Browsers ship revocations but operating systems currently don&#39;t do that for apps and leave it up to apps which rarely check. 2026-10-22T11:24:20Z https://nostr.now/nevent1qqs8z7qdw2wmutv0333s8upflt5e9dkcr7p67xm84ez9ksmym6zpujgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljwd0cs4 In reply to <a href='/nevent1qqs0u5jgcwvkksurul0uclflr7jhks9adtdnz2cd0944fusrfmqaqcsrg43g0'>nevent1q…43g0</a><br/>_________________________<br/><br/>Vanadium received the root store update via an out-of-band component update. That&#39;s the standard Chrome Root Store component distributed via our servers using a caching reverse proxy. We don&#39;t modify it right now.<br/><br/>Other Chromium-based browsers keeping component updates intact also would have received it this way.<br/><br/>Android has a configuration system for apps to limit the set of trusted roots or pin keys in the chain of trust. Our apps pin Let&#39;s Encrypt keys and backup leaf keys. 2026-10-22T11:18:04Z https://nostr.now/nevent1qqszm6kt7kx6dglmwrjgaw46epzfl42jyjkuq7l698gt7g47jf4l5wgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljew7a27 In reply to <a href='/nevent1qqs8ev8jc3hmx77gaejfnshzvv90he2glhw57auy7ug6x77v0x2eu7gukehlg'>nevent1q…ehlg</a><br/>_________________________<br/><br/>It&#39;s usually quickly available in the Alpha channel and then becomes available in the Beta channel within a few hours. It generally takes at least 16 hours for a release to reach the Stable channel after reaching Beta. It can be quicker when there are only a few changes and especially when it&#39;s a follow up release to one which didn&#39;t make it through public testing.<br/><br/>The vast majority of releases reach the Stable channel. The main exception are releases based on new major Android versions. 2026-10-22T11:04:15Z https://nostr.now/nevent1qqsgnzmlwffpu6nps5ynfcuervmdwn7jh2r0waqv5843lja2qs0kqhgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj95t686 GrapheneOS version 2026102100 released:<br/><br/><a href="https://grapheneos.org/releases#2026102100">https://grapheneos.org/releases#2026102100</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/43012-grapheneos-version-2026102100-released">https://discuss.grapheneos.org/d/43012-grapheneos-version-2026102100-released</a><br/><br/>#GrapheneOS #privacy #security 2026-10-22T10:14:16Z https://nostr.now/nevent1qqsylkrfx9u6a2drq7xq3e9sh077kc8yavjmak9t3cq2xkmm8t5xjcgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljvlzhcc In reply to <a href='/nevent1qqst8ep9znmh6cqjr9h2q6e38vy9m7hctzhmpd8dn4cy4uhqefkvx6szs7re7'>nevent1q…7re7</a><br/>_________________________<br/><br/>We want to remove their RSA root too but we might ship it as disabling it by default so people can still turn it back on if they need to use one of the many sites/services using it.<br/><br/>If Android and Chromium remove the active RSA root then we&#39;ll quickly remove it too. Our plan is to add code for disabling roots by default so we can avoid breaking compatibility with a bunch of sites and services used by apps while still getting rid of it for most users despite major platforms not doing it. 2026-10-22T00:58:43Z https://nostr.now/nevent1qqst8ep9znmh6cqjr9h2q6e38vy9m7hctzhmpd8dn4cy4uhqefkvx6szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljsju2zr In reply to <a href='/nevent1qqs2eq9wdrmwllyphnq4elkakzpsn5hwraxsyst6x8f7s47ek3qru3qg9jlvu'>nevent1q…jlvu</a><br/>_________________________<br/><br/>eMudhra has 2 active roots and 2 legacy roots. After our update, there will only be the active RSA root remaining. Browsers removed the active ECDSA root but not the other ones yet. We&#39;re considering whether we should also remove the active RSA root despite none of the major browsers or operating systems doing that yet. Their ECDSA root was conveniently only used for around 30k certificates as opposed to millions like their RSA root. They&#39;re moving the ECDSA root ones to the RSA root. 2026-10-22T00:55:11Z https://nostr.now/nevent1qqs2eq9wdrmwllyphnq4elkakzpsn5hwraxsyst6x8f7s47ek3qru3qzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj5pf8wq In reply to <a href='/nevent1qqsvecnu62ptmnwadz7yr884dy7g62uyj85hpm5uzeeey9u4cwsq02qphsvt3'>nevent1q…svt3</a><br/>_________________________<br/><br/>Vanadium receives out-of-band component updates for the root store so it didn&#39;t require an app update. Android doesn&#39;t yet have a way to rapidly update the OS root store. Chromium&#39;s root store also distributes revocations, unlike OS root stores.<br/><br/>We removed the relevant eMudhra ECDSA root. We also removed both their legacy roots. It&#39;s included in the OS update we&#39;re building right now. <br/><br/>Android supports out-of-band root store updates via APEX updates but those require reboots anyway. 2026-10-22T00:53:32Z https://nostr.now/nevent1qqsz2fkcw54d4vtfvkn6wqf97gdclpmw7sa8h544752jr99rw9mpgaqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljynllkj In reply to <a href='/nevent1qqsdqg933edeaw93g4aalwjc92pyz5f4x8p98aqjwrla46yxf79mxhgdclt2s'>nevent1q…lt2s</a><br/>_________________________<br/><br/>How can we replace it with something better without there being a high quality forum written in a better language? Ruby on Rails is easily worse than the modern PHP dialect used by Flarum via Laravel. Discourse is nearly certainly a lot less secure than Flarum. It has drastically more attack surface, complexity and resource requirements. It would be a lot more painful for us to host and manage. PHP not being a good language doesn&#39;t mean Ruby on Rails is better. Which alternative is there? 2026-10-21T16:03:56Z https://nostr.now/nevent1qqs0ug7sp6kv57xpvrqkaw6dz46xfhp3cajz4lrqj3qganw8xkucytqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljtqc60p In reply to <a href='/nevent1qqsyurssfd6yvtrt35fa6lj70n2gpc9axzy6kpnlq83l5nevqm76xtq2wd42x'>nevent1q…d42x</a><br/>_________________________<br/><br/>Our discussion forum is updated to PHP 8.5.12 and has been available again for over an hour:<br/><br/><a href="https://discuss.grapheneos.org/">https://discuss.grapheneos.org/</a> 2026-10-21T15:30:37Z https://nostr.now/nevent1qqst8lx4tz28yul99pf5pznkxq6he0gh3taj6vusdh02g3kvzsnpydgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljcdnxpu In reply to <a href='/nevent1qqsta4selu82wxpkday9a2zf3t7dw9usx8tplwkyla6wz5wvu2kytqs25wt3u'>nevent1q…wt3u</a><br/>_________________________<br/><br/>We haven&#39;t felt like patching Mastodon yet. We host a lot of services.<br/><br/>We&#39;re also constrained to a low character count regardless from cross-posting across platforms unless we write it as Bluesky sized paragraphs to paste into long posts.<br/><br/>If we&#39;re going to write real long form content, we want better formatting. Our forum has basic Markdown functionality along with the thread providing a way for people to reply and discuss it in a single place. We can post there and link to it. 2026-10-21T10:07:08Z https://nostr.now/nevent1qqsyurssfd6yvtrt35fa6lj70n2gpc9axzy6kpnlq83l5nevqm76xtqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljkv4nmf In reply to <a href='/nevent1qqs9cdfyxa6m39av0gpwylf9wzy5tzc8ef4zmrr3r2rcfqack3u5lcgcs3lv9'>nevent1q…3lv9</a><br/>_________________________<br/><br/>Details are public and exploits are being written. Too risky to keep the forum up. It&#39;s the 1st major downtime for it.<br/><br/>From a PHP core developer:<br/><br/><a href="https://phpc.social/@Girgias/117476477429221001">https://phpc.social/@Girgias/117476477429221001</a><br/><br/>&gt; The only thing I can say is that the only mitigation is patching / upgrading PHP. I sadly know too much. 2026-10-21T09:06:35Z https://nostr.now/nevent1qqs9cdfyxa6m39av0gpwylf9wzy5tzc8ef4zmrr3r2rcfqack3u5lcgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljz37pcc In reply to <a href='/nevent1qqsy89mgzjhhcyy8yy4usdfn4t765m5xwpapwenlxf9utkg2zde460c8prdjl'>nevent1q…rdjl</a><br/>_________________________<br/><br/>We deployed these mitigations but decided to turn it off anyway:<br/><br/>1) session.upload_progress.enabled = Off<br/>2) blocking requests with multipart/form-data in Content-Type (case insensitive)<br/>3) ZEND_MM_DEBUG=poison_free=0x00,poison_alloc=0x00,padding=16,check_freelists_on_shutdown=1 2026-10-21T08:55:06Z https://nostr.now/nevent1qqsy89mgzjhhcyy8yy4usdfn4t765m5xwpapwenlxf9utkg2zde460czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljnvv26x Our discussion forum is the only software we have using PHP. We&#39;ve taken it down temporarily while waiting for the patches for <a href="https://www.php.net/archive/2026.php#2026-10-20-1">https://www.php.net/archive/2026.php#2026-10-20-1</a> due to vulnerability details already being available and proof of concept exploits being developed. Don&#39;t want to take the risk. 2026-10-21T08:21:51Z https://nostr.now/nevent1qqswxz3rg57rdar26n8t39s43yfy0mdldmdfylx7zghq0c259jz59yqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj85fv2q Vanadium version 156.0.8078.47.0 released:<br/><br/><a href="https://github.com/GrapheneOS/Vanadium/releases/tag/156.0.8078.47.0">https://github.com/GrapheneOS/Vanadium/releases/tag/156.0.8078.47.0</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/42992-vanadium-version-15608078470-released">https://discuss.grapheneos.org/d/42992-vanadium-version-15608078470-released</a><br/><br/>#GrapheneOS #privacy #security #browser 2026-10-21T07:03:27Z https://nostr.now/nevent1qqswffpaugqfqd84ncx8uttzsxsa0a69ec5c9jkcdt3rqsw3jeh8r2szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljjuha23 In reply to <a href='/nevent1qqszp8t7ln4mdl9kw54wnkd2zc095mmray37vd6snmf0f4xtjvde3uqjmr3tl'>nevent1q…r3tl</a><br/>_________________________<br/><br/>They discontinued making traditional one-way pagers in 2001 and then phased out the rest due to mobile phones taking over. Those were the mass market devices preceding their mobile phones and that&#39;s what became Motorola Mobility, so it&#39;s definitely still a very historical part of the company. Motorola Mobility is what most people would recognize as being Motorola as a household name in the 1990s/2000s/2010s. It&#39;s a very old company with a long history prior to that though. 2026-10-20T21:53:27Z https://nostr.now/nevent1qqszp8t7ln4mdl9kw54wnkd2zc095mmray37vd6snmf0f4xtjvde3uqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj9lzwg2 In reply to <a href='/nevent1qqsvc69vrh7mh73dhw2es06fxg70euqpq89ywcsv6vrdz9rvu6hytvcevhyvp'>nevent1q…hyvp</a><br/>_________________________<br/><br/>Motorola Solutions keeping the original legal entity is only really a technical detail rather than it being the only actual continuation of the company.<br/><br/>Motorola Mobility is definitely also a continuation of the original Motorola.<br/><br/>Motorola Solutions has some of the older parts of the business including the radios but the mobile phones and the pagers before those which were discontinued long before the split are what most people recognized as being tied to the company. 2026-10-20T21:50:34Z https://nostr.now/nevent1qqsvc69vrh7mh73dhw2es06fxg70euqpq89ywcsv6vrdz9rvu6hytvczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljlhw9cy In reply to <a href='/nevent1qqsf0864lzs8f9el6r39750zdmwgdfqkxjpxvlsqzssrz0z4sf26ggs85adjd'>nevent1q…adjd</a><br/>_________________________<br/><br/>They didn&#39;t sell it but rather split it. Every Motorola shareholder received 1 share of Motorola Mobility for each 8 shares of Motorola. After spinning off Motorola Mobility, they did a reverse 1-for-7 reverse stock split for Motorola and renamed it to Motorola Solutions.<br/><br/>It was initially the same owners for both companies but immediately diverged due to both being publicly traded. Google acquiring Motorola Mobility ended the historical shared ownership of the companies. 2026-10-20T21:35:09Z https://nostr.now/nevent1qqsy2a5p4getq7fukz6az70w8959wntv40ywa4uh5a9sl26cx6nllhgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljz33x3u In reply to <a href='/nevent1qqsrvmv4ql6ar88vxr0a2r9m08gcckrc79r0zsnhumz2rd7uq54v7yc4gnwhg'>nevent1q…nwhg</a><br/>_________________________<br/><br/>Keeping the legal entity for Motorola Solutions was likely more about it being heavily based around government contracts in particular. It avoided a whole lot of hassle and potentially losing a lot of money. It was easier for Motorola Mobility to shift everything over than Motorola Solutions.<br/><br/>Google messed things up by acquiring it for the patents, not knowing what to do with the rest and gutting it to save money short term. They could have just spun it off immediately. 2026-10-20T21:31:55Z https://nostr.now/nevent1qqsrvmv4ql6ar88vxr0a2r9m08gcckrc79r0zsnhumz2rd7uq54v7yczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljk39v7k In reply to <a href='/nevent1qqsdyc2duusnzgs429zdufs8q56ua5qp6aeclqycthwr2awak3d9gfgtwgv2r'>nevent1q…gv2r</a><br/>_________________________<br/><br/>Motorola Mobility had a lot more revenue at the time of the split but wasn&#39;t as profitable and was considered to be far more risky. Mass market mobile devices are a much different business from mainly doing business based on long term government and enterprise contracts. That&#39;s why the companies were split in the first place. The trademark was more important to the larger mass market company and it was also probably seen as more likely to launch new classes of products. 2026-10-20T21:29:09Z https://nostr.now/nevent1qqsv27u03gkm9h80jje86n5fhexn3gjqe2zpj4ly2zze77qdrnnda5gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj7cx7ks <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1mmgm6jq8jkvh3p5mcx0y77pvgawl9thlm07tgkjzkjqqj3huy4ys4wk0pu" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>🎃Imogen🎃</span> (<span class="italic">npub1mmg…k0pu</span>)</a></span> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1tutdymj8yu06ashxmspjhh23rvyutzjvqkdmuvtqkdyvg547cjyske9v9r" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Ox1de</span> (<span class="italic">npub1tut…9v9r</span>)</a></span> This doesn&#39;t contradict anything. Motorola Trademark Holdings is a wholly owned subsidiary of Motorola Mobility, not Motorola Solutions. It&#39;s not Motorola Solutions which owns the trademarks but rather Motorola Mobility. Motorola Solutions has a limited license to use the trademarks in certain fields where they had existing products. Lenovo can freely use the trademarks for anything they want including fields where Motorola Solutions uses them. Read the linked SEC filing. 2026-10-20T21:15:03Z https://nostr.now/nevent1qqsp58hcawr337fsxsqz2jtdw8au5r682u028ux23jk58gvq3wn7k5czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljr3mfs0 In reply to <a href='/nevent1qqsfqvmwgh0w9qztwt2x4nh9tmj8n0add58qujzmwsmlctr4uwrcm5g5nnf8g'>nevent1q…nf8g</a><br/>_________________________<br/><br/>From the Motorola Solutions SEC filing linked above:<br/><br/>&gt; We no longer own certain logos and other trademarks, trade names and service marks, including MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M logo and all derivatives and formatives thereof (“Motorola Marks”) and we license the Motorola Marks from Motorola Trademark Holdings, LLC (“MTH”), which is currently owned by Motorola Mobility, a subsidiary of Lenovo. 2026-10-20T21:11:45Z https://nostr.now/nevent1qqsfqvmwgh0w9qztwt2x4nh9tmj8n0add58qujzmwsmlctr4uwrcm5gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj3h0p2r In reply to <a href='/nevent1qqspfzsud36pdu3yss3j2558e3vepkzehuhghy3439nqenej9pf038ghxsvh3'>nevent1q…svh3</a><br/>_________________________<br/><br/>No, Motorola Mobility owns the Motorola trademark via Motorola Trademark Holdings.<br/><br/>Motorola Solutions has a limited royalty-free license to use the trademark from Motorola Mobility. You can see this in the SEC filings for Motorola Solutions:<br/><br/><a href="https://www.motorolasolutions.com/content/dam/msi/investors/doc_financials/2025/q4/msi_2025_10-k.pdf">https://www.motorolasolutions.com/content/dam/msi/investors/doc_financials/2025/q4/msi_2025_10-k.pdf</a><br/><br/>Motorola Mobility was technically the company which was split out with Motorola Solutions keeping the original ticker, but Motorola Mobility owns the trademark and Motorola Solutions can&#39;t use it freely. 2026-10-20T21:09:39Z https://nostr.now/nevent1qqs0f8cq8pmep2p8mc06sqdr3v4q0swfxj24k6nqzsej0ammrz5tp4gzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljz0zghj In reply to <a href='/nevent1qqsq099ayl9rk8mdll6eqh96590u5fnslf4mufeflntu4dk2n4udvtg0snsaq'>nevent1q…nsaq</a><br/>_________________________<br/><br/>Motorola Mobility and Motorola Solutions are entirely different companies. GrapheneOS isn&#39;t partnered with Motorola Solutions and neither is Motorola Mobility.<br/><br/>The original Motorola was split into Motorola Mobility and Motorola Solutions back in 2011. Motorola Mobility was subsequently purchased by Google in 2012 and sold to Lenovo in 2014.<br/><br/>Motorola Mobility owns the Motorola trademark. Motorola Solutions is a different company using the trademark under a limited license from the split. 2026-10-20T19:24:20Z https://nostr.now/nevent1qqs8dq4s9s6kwmk0v5p3d5a3rlggyecqrjmt9sagphywd9cy7jl68zczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj43hhv5 GmsCompatConfig version 177 released:<br/><br/><a href="https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-177">https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-177</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/42964-gmscompatconfig-version-177-released">https://discuss.grapheneos.org/d/42964-gmscompatconfig-version-177-released</a><br/><br/>#GrapheneOS #privacy #security #gmscompat 2026-10-20T00:49:21Z https://nostr.now/nevent1qqsvkxhy3fmmhz6gc7zgrcvujcxyylsszaky9qkpv5egzwzhjqczwvqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljqt6qym In reply to <a href='/nevent1qqs0sutdnl444wn50njvpv6aqqvvfvgycc6ent67j66hvupzcdsr2zcxl9787'>nevent1q…9787</a><br/>_________________________<br/><br/>It was extended from the logo being held for 0.8s to 1.6s for the next release. We raised it to 2.0s earlier which is what&#39;s shown in the video above but then backed down to 1.6s since 2.0s seems a bit long to go without any visible animation. We could have some kind of animation around the logo but decided we want the logo itself unmodified for a period of time instead of having light move across it as we did in earlier concepts. 2026-10-19T07:31:03Z https://nostr.now/nevent1qqsx29h98c6sagrq3gtkk5rzl53w8dqze35yh56s2fw9plfxynjtpsczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljrgvm9x In reply to <a href='/nevent1qqsxtpwdy2h3amjua7pmrasg9r5pqjh6alespd30esa9wxvctnr7gvg07kqa4'>nevent1q…kqa4</a><br/>_________________________<br/><br/>The acceleration throughout the animation is currently done with smootherstep (quintic smoothstep) which is working nicely and likely going to be kept.<br/><br/><a href="https://en.wikipedia.org/wiki/Smoothstep">https://en.wikipedia.org/wiki/Smoothstep</a><br/><br/>The top speed for the loop could be reduced but we&#39;re getting mixed feedback about that aspect of it. 2026-10-19T06:25:34Z https://nostr.now/nevent1qqsxtpwdy2h3amjua7pmrasg9r5pqjh6alespd30esa9wxvctnr7gvgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljn9gjgd In reply to <a href='/nevent1qqswktmll63urrljw4hdsnew6yv6plzsmnx0zf6t0xr4ueydh5fk9agq3ucnf'>nevent1q…ucnf</a><br/>_________________________<br/><br/>The animation included in 2026101600 holds the logo for 0.8s rather than 2.0s in the video above since the new zips weren&#39;t committed to the OS yet. We&#39;ve reduced that to 1.6s though.<br/><br/>For the Pixel Tablet, we&#39;ve reduced the size of the logo to 30% of the screen height from 40%. 2026-10-19T06:11:33Z https://nostr.now/nevent1qqs892cc5d9et60vguzqyy53g30e4a8507f0d27p0pkngkz5tzjzquqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljg30d53 In reply to <a href='/nevent1qqsw8kgcvq5wpqzslnpa6ffe69jhtrn5uhs5sw728pfjfa3rfzxnptsmh725h'>nevent1q…725h</a><br/>_________________________<br/><br/>Android Auto works as well on GrapheneOS as the stock OS.<br/><br/>It sounds like you haven&#39;t enabled network-based location and are therefore losing ongoing location detection when GNSS loses reception. 2026-10-19T04:57:13Z https://nostr.now/nevent1qqs9zkwjuk9pmdcpav8v5n9xe2alfknq5lx05ptq5xgdjzvltyhk4pqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj8m23yf In reply to <a href='/nevent1qqsfjrxds6fxmqwcxm72svqnlqp7j24k4mhnd7tlllzdujlwzk365mc9s4unl'>nevent1q…4unl</a><br/>_________________________<br/><br/>The boot animation on the device is a series of PNG images in a zip with the ability to configure those for looping, controlling interrupting and using standard shaders including the option to make it follow the system theme similar to themed icons. It&#39;s pixel perfect with no compression artifacts and we&#39;re doing ours at 60 FPS similarly to the stock Pixel OS. It might be possible to use higher refresh rate on devices supporting it but we aren&#39;t sure and it isn&#39;t really needed. 2026-10-18T07:39:15Z https://nostr.now/nevent1qqs8w3zgs8aw65h4k4fn572mww9lt30084n3dakgyeepyzjyjn568ngzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljqcl27u In reply to <a href='/nevent1qqstq58ypxqc4wqwd2r48qe20hxz2q4wvyemk2vqgwufm5jvqralr4gxtg6ak'>nevent1q…g6ak</a><br/>_________________________<br/><br/>That sounds like a bug with DuckDuckGo&#39;s Open Search metadata. There will be a way to manually configure search engines soon so you could work around it but you should ask them to fix it. 2026-10-18T07:23:58Z https://nostr.now/nevent1qqswj82wassx2pjqzjsqjrulx3d5x7kfx5m5ruk9gex349t9w6ns6tgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljayz9c0 In reply to <a href='/nevent1qqsz5h4dvc36yadxh6wamws9wfzdme673v754nuczscputc6p7w06qg4ajvgj'>nevent1q…jvgj</a><br/>_________________________<br/><br/>It fixes the icon sizing, alignment, etc. and adds an extra horizontal row to each page. It also fixes widget alignment and more. 2026-10-18T07:23:21Z https://nostr.now/nevent1qqsr9jnska85na0es9qtzj52hlps87whpky6zwfxyclxn5jum7tq2yqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljy9ycrn In reply to <a href='/nevent1qqspl00y2cstd3l0x7fqc39pnggzx9k9mceeaaye4lamgg60e72vttsz9tn72'>nevent1q…tn72</a><br/>_________________________<br/><br/>The logo can&#39;t take more than around 3 seconds to form since it needs to hold for at least around 0.8s before it becomes interruptible to make sure the logo gets displayed. Boot time is already typically fast enough that there isn&#39;t enough time to run a full iteration of the loop for most boots.<br/><br/>The upcoming Motorola Signature 27 will be drastically faster than Pixels and we also have boot time optimizations planned. The boot can likely be completed before the 0.8s + 1.2s hold ends. 2026-10-17T22:36:25Z https://nostr.now/nevent1qqspl00y2cstd3l0x7fqc39pnggzx9k9mceeaaye4lamgg60e72vttszyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljgyhx7c In reply to <a href='/nevent1qqsdejvjgvvujgtz9cmxd9xujpp3a32exs7rj7c6mvtf8smqlchh9fs39gx4p'>nevent1q…gx4p</a><br/>_________________________<br/><br/>It can&#39;t be that way because the uninterruptible part of the animation needs to be under 4 seconds to avoid increasing boot time.<br/><br/>It looks nicer to have an uninterruptible loop with an outro but it would significantly increase boot time. The current loop is 4 seconds and adding a 3.5 second outro would mean extended boot time from between 3.5 to 7.5 seconds depending on how far it was into the loop.<br/><br/>We also don&#39;t want to freeze the animation for 10+ seconds when it has a lot to do. 2026-10-17T22:33:29Z https://nostr.now/nevent1qqs9fpnuxd4l67h4shsuj8pyyfpq87tl4sfc4pr0j0w95aetpns9wzgzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj8d24p8 In reply to <a href='/nevent1qqs9l59smul4l4ejlyreq24d3prcr4tq7qvhz7f96hwhq4mk60x2rsgkf6ktm'>nevent1q…6ktm</a><br/>_________________________<br/><br/>The launcher grid layout was fixed in the same release including the new boot animation.<br/><br/><a href="https://grapheneos.social/@GrapheneOS/117457467257349333">https://grapheneos.social/@GrapheneOS/117457467257349333</a><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note1yh8shtfw2vkxejhquy0xghj9vevw0mlyrdafyqgutzcm6dlkyj9sfzxwvs" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note1yh8…xwvs</a></span><br/> </div> GrapheneOS version 2026101600 released:<br/><br/><a href="https://grapheneos.org/releases#2026101600">https://grapheneos.org/releases#2026101600</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/42898-grapheneos-version-2026101600-released">https://discuss.grapheneos.org/d/42898-grapheneos-version-2026101600-released</a><br/><br/>#GrapheneOS #privacy #security </blockquote> 2026-10-17T21:19:09Z https://nostr.now/nevent1qqswq8z06uv6ecrszm4t528vcrh5rnp2dc8ue22mlrcgxvaatlhzkyqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljcymkhz In reply to <a href='/nevent1qqs8d8an3g7hzjmxhjylq3v4h07z0tuzwah40wpsz5h9q5hq28ph5xc3wur0n'>nevent1q…ur0n</a><br/>_________________________<br/><br/>We could reduce the motion by reducing the radius it expands to and extending the time for each loop but 4 seconds per rotation is already quite long. It already often doesn&#39;t have enough time to complete a single loop on current devices. Boot time will be getting significantly faster with our planned optimizations to secure spawning and also upcoming hardware. The upcoming Motorola flagship will be drastically faster than Pixels and may typically finish during the logo hold time. 2026-10-17T20:32:58Z https://nostr.now/nevent1qqstzs7yfhkcwgfk820wr2qquywu32wzp5wppk4hf6nqwcg9vnk32aqzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljgagfvx In reply to <a href='/nevent1qqsqj8tjcn75tnp3ha0xdft568eztrd95rdyylacaann3lq0m9sv3gqgldxet'>nevent1q…dxet</a><br/>_________________________<br/><br/>No, it was created with a Python script using the Pillow image library. It&#39;s only a few hundred lines of Python code. It may have made sense to use a framework suited to generated animations but the way we did it works well and is very straightforward.<br/><br/>We initially tried using Blender to make a 3D animation. We decided 2D is a better fit for the minimalist aesthetics used by GrapheneOS. 3D is drastically more complex and it&#39;s a lot harder to make it feel high enough quality. 2026-10-17T20:28:06Z https://nostr.now/nevent1qqswktmll63urrljw4hdsnew6yv6plzsmnx0zf6t0xr4ueydh5fk9agzyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj0kst86 In reply to <a href='/nevent1qqsyllm5prlfywjnuvrevqw9vhd8d5kpp87z6l4wm5h6gy4uz5hxw4sj2c9ke'>nevent1q…c9ke</a><br/>_________________________<br/><br/>Intro<br/>0.00-1.90: Atoms appear one-by-one and gather<br/>1.90-2.70: Bonds expand; name fades in from 2.20<br/>2.70-3.50: Hold<br/><br/>Transition<br/>0.00-1.20: Hold<br/>0.00-0.80: Outer and split inner bonds retract; name fades<br/>0.80-1.40: Ease into spin<br/><br/>Loop<br/>0.00-4.00: One rotation from initial offset 2026-10-17T19:13:00Z https://nostr.now/nevent1qqsyllm5prlfywjnuvrevqw9vhd8d5kpp87z6l4wm5h6gy4uz5hxw4szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljv0f4qe This is the new GrapheneOS boot animation. It&#39;s generated frame-by-frame using a script. It has a minimum 3.5s total runtime for the intro including a small pause. The rest of the animation gets interrupted once the device is booted to avoid any delay so there can&#39;t be an outro.<br/><video controls width="100%" class="max-h-[90vh] bg-neutral-300 dark:bg-zinc-700"><source src="https://grapheneos.social/system/media_attachments/files/117/457/828/132/802/187/original/c9dd1c4dabdf9335.mp4"></video><br/> 2026-10-17T19:10:29Z https://nostr.now/nevent1qqsztnct45h9xtrvetswz8nytezkvk88aljpk75jqyw93vdaxlmzfzczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljayg7wg GrapheneOS version 2026101600 released:<br/><br/><a href="https://grapheneos.org/releases#2026101600">https://grapheneos.org/releases#2026101600</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/42898-grapheneos-version-2026101600-released">https://discuss.grapheneos.org/d/42898-grapheneos-version-2026101600-released</a><br/><br/>#GrapheneOS #privacy #security 2026-10-17T17:38:36Z https://nostr.now/nevent1qqsqggygy52mpttpa7p7r9juyzkengj8ljzcxjeghzpuvpsvwhs8l9czyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtlj89rfel In reply to <a href='/nevent1qqsyms0hx0qzhlvh0rnxql6mgzx4l2ktcj2grjqadh34kaane3kyy2ccfjuak'>nevent1q…juak</a><br/>_________________________<br/><br/>Google apps and services can be installed on GrapheneOS as regular sandboxed apps. You can test both with and without Google Mobile Services on GrapheneOS.<br/><br/>Devices without Google Mobiles Services are increasingly popular and apps should fully work without it. Many popular mainstream apps do including even the Facebook app suite.<br/><br/>There are alternatives to Google services. For example, apps can default to FCM when present while offering UnifiedPush as an alternative. 2026-10-16T18:10:14Z https://nostr.now/nevent1qqswm4t7uspc3etm924l06l9n3dptm67vefr4fmj77c2my6wtez7k9szyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljuxvn8w In reply to <a href='/nevent1qqsp47wh073eak9gp0hn2cm465rddcxrehuzc6qrcugehzj4r5we2xgfxq43j'>nevent1q…q43j</a><br/>_________________________<br/><br/>It was a poor repair. They likely either forgot to reconnect it or broke it. 2026-10-16T17:08:36Z https://nostr.now/nevent1qqs9t2q7q97qnu0lgm82jxehyctvmslr95ssjpxzr0xjtsszprejswczyzem50zsgha6lxd7nj6d420367awak46plzmj9vk2y0zlda8phtljhr008n Vanadium version 155.0.8059.84.0 released:<br/><br/><a href="https://github.com/GrapheneOS/Vanadium/releases/tag/155.0.8059.84.0">https://github.com/GrapheneOS/Vanadium/releases/tag/155.0.8059.84.0</a><br/><br/>See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.<br/><br/>Forum discussion thread:<br/><br/><a href="https://discuss.grapheneos.org/d/42852-vanadium-version-15508059840-released">https://discuss.grapheneos.org/d/42852-vanadium-version-15508059840-released</a><br/><br/>#GrapheneOS #privacy #security #browser 2026-10-16T07:07:03Z