Most of what you use is built by "code monkeys" and is on the way to being vibe coded.
294 karma · joined February 7, 2023
>binutils gcc gdb libffi perl xorriso
Good luck replacing those ...
We get it. Your behavior makes reading the posts hard for no reason.
This is not Facebook, people take time to read here.
Google can kill them in an instant, they need the AOSP source to survive.
Every Google Pixel model per generation ends up supported.
DO NOT UNDERESTIMATE TSA.
Social hardening is a real problem.
Someone high up got tired to pull over every pixel user at the border.
With the new Motorola, TSA line are going to move faster that ever!
If you care about privacy, stay away for the moto release and stick with pixel.
The only source of truth is hosted by bluesky
https://github.com/bluesky-social/atproto/discussions/1892 https://github.com/bluesky-social/atproto/discussions/2821
This is very useful on OEM ROMs with a bunch of scrapware, no one expects a custom ROM to have this issue.
If 1% of iPhone users are criminals and 5% of GrapheneOS users are criminals, border search agents are going to be interested in your GrapheneOS mobile.
I am pretty sure criminals are more likely to use a super safe and secure phone that is easy to obtain.
Did you know that before reinventing the wheel, you can ask LLM your requirements, and they can find the most suited already existing tool ?
A true AOPS image is missing most core Apps.
And OSS projet based on the SFOS core exist : https://nemomobile.net/, https://github.com/nemomobile-ux
https://forum.sailfishos.org/t/open-sourcing-proceeding/2468...
https://github.com/sailfishos/sailfish-weather/
https://github.com/sailfishos/jolla-camera
It's still more open than AOSP
I can't find recent demos of the phone, everything is a few years old on YouTube now, and I know the device is still in development.
How usable the browser and camera are ?
Can you get a full day of battery ?
What else use main line kernel without blob ?
Don't buy if this is your main goal.
It's running a custom Wayland compositor and UI.
Still use all the Linux stack you expect (GCC, Wayland, SystemD, Pulseaudio, RPMs, Dbus ...)
Yes they do ship phones !
Everyone is stuck on the 2015 tablet failure.
Let us clarify here as it is very different indeed.
The Jolla C2 Community Phone is done in collaboration with Reeder, who is the HW vendor. This means Reeder sources the components, plans the production and does the manufacturing in Turkey. Jolla provides the complete software stack (Sailfish OS) which is installed by Reeder in the manufacturing.
In the new Jolla Phone everything is different. Jolla is the vendor, has designed the product itself, done the component sourcing and pays directly to the component vendors. We control the pipeline. Further, we have secured our position for the initial memory batch with advance purchase.
Also, to be clear: Reeder has no involvement in the new Jolla Phone.
Thank you for asking, very good points to clarify!
Cameras:
The primary back camera will feature Sony IMX766 AF 50MP sensor module, known for its quality and performance within the price range
The secondary back camera will be a 13MP ultrawide AF Sony IMX214
Front camera is set to be a 32MP wide lens FF Sony IMX616
For some user, /e/ is more approachable (Friendly and colorful UI)
I could not get my mother to use GrapheneOS, /e/ is a lot simpler.
Still miles better than to use a Default ROM from most OEM.
Far has I know, pebble user have spent the last 10 years searching for another pebble without luck.
Used since the 60s lol