Login
You're viewing the front-end.social public feed.

Replies

  • Oct 4, 2026, 8:04 AM

    @Tutanota @GrapheneOS Wenn ich eine email aus Apps versenden muss wird immer nur Gmail angezeigt. Andere Email Anbieter muss ich extra eingeben. Beim Smartphone aber auch bei GoogleTV oder Amazon ( letzteres kennt wenigstens noch T-Online ).

    Selbst wenn mann alle Google Apps nicht mehr nutzen will drängeln diese sich immer rein.

    Auch bei Terminen z.B. für 7er Rugby World Series Übertragung nur Google Kalender zur Auswahl.

    Normales Android für Normalnutzer.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • Konradretrocomputing@mastodon.social
    Oct 4, 2026, 8:15 AM

    @Tutanota @GrapheneOS the only problem is that as of now GrapheneOS is only compatible with Pixel phones.
    From next year it will be compatible also with some select Motorola phones, not clear for now when and which ones.
    Short-term solution will be moving to some other Android-ish flavor (HyperOS, ColorOS, ...).
    Switching to iOS won't fix anything, as it's already where Google is going
    We definitely need a 3td alternative, soon.

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 2
  • Konradretrocomputing@mastodon.social
    Oct 4, 2026, 8:34 AM

    @Goodlucksil @Tutanota @GrapheneOS My understanding is that GrapheneOS' compatibility limits are set by the hardware, or lack thereof, not by some policies or intent.
    Can you name a phone OS alternative that can be used right now for your everyday phone?

    💬 0🔄 0⭐ 4
  • 💬 0🔄 0⭐ 5
  • 💬 1🔄 0⭐ 1
  • Oct 4, 2026, 2:29 PM

    @retrocomputing @marcellinusme @Goodlucksil @Tutanota /e/ is highly unsafe due to lack of important standard privacy/security updates and features. Murena is also heavily pushing anti-privacy propaganda including repeatedly claiming highly private and secure devices are mainly beneficial to criminals and pedophiles. It's not a legitimate privacy OS on either a technical level or the fact they're siding with highly anti-privacy policies. Don't be fooled into using it. It isn't what it claims.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 2:40 PM

    @retrocomputing @marcellinusme @Goodlucksil @Tutanota /e/ is a poorly maintained fork of LineageOS reducing privacy and security patches/protections far more than LineageOS compared to AOSP. It takes years to ship full patches despite misleading users. It also adds many privacy invasive services.

    More information:

    eylenburg.github.io/android_co

    codeberg.org/divested-mobile/d

    discuss.grapheneos.org/d/24134

    Two examples of Murena pushing anti-privacy propaganda:

    x.com/GrapheneOS/status/204088

    clubic.com/actualite-604786-mu

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:01 PM

    @retrocomputing @marcellinusme @Goodlucksil @Tutanota Android's standard privacy/security patches and protections are increasingly inadequate, but they're far behind those.

    Android 17 was released in June 2026 and is required for full privacy/security patches as not all are backported. New protections aren't backported at all. Android 17 QPR2 is the next major release coming out in December 2026 with a lot more.

    There are also kernel, driver and firmware updates largely not being shipped.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 4, 2026, 3:36 PM

    @marcellinusme @retrocomputing @Goodlucksil @Tutanota No, it's you who is spreading misinformation to promote highly insecure and non-private products from Murena.

    /e/ and Murena devices have years of delays for privacy and security updates along with not having anything close to current standard privacy and security protections.

    GrapheneOS has an OEM partnership with Motorola and they have upcoming devices with official support for it which will have greatly improved updates and security.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:44 PM

    @marcellinusme @retrocomputing @Goodlucksil @Tutanota Android OEMs have months of early access to Android Security Bulletin patches and are allowed to ship those patches early. We're the only platform shipping all of these patches early. We strongly disagree with this system and are advocating against it but we massively benefit from it. We get to ship the Android Security Bulletin patches months before they're publicly available. We're far ahead of the Pixel OS on those patches, not behind it.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:46 PM

    @marcellinusme @retrocomputing @Goodlucksil @Tutanota We only use devices with reasonable updates and security features where users can be properly protected against widespread real world attacks. Until recently, Pixels were the only devices with alternate OS support providing important standard updates and security features. That's changing with the upcoming Motorola devices starting with a high end flagship launching very soon and then trickling down to lower end devices from there over time.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 11:49 AM

    @retrocomputing @Tutanota @GrapheneOS ColorOS and HyperOS are proprietary, and one of them is the product of a massive corporation.

    Those are odd suggestions, especially since their hardware compatibility doesn't seem to be any better than LineageOS, /e/, Calyx, or other less… let's say "encumbered" options.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 2:56 PM

    @cocaine_owlbear @retrocomputing @Tutanota

    CalyxOS, LineageOS and especially /e/ don't provide current standard privacy and security patches/protections which is increasingly important. Exploiting privacy and security vulnerabilities/weaknesses is getting far easier and more widespread.

    Android isn't nearly good enough at protecting users itself and each of those operating systems is drastically worse. They lag months to years behind inadequate standard patches and protections.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:21 PM

    @GrapheneOS @retrocomputing @Tutanota I agree with all of that. Obviously GrapheneOS is the best Android replacement, but since it's locked to Pixels until next year, and even then will only work on one new Motorola phone model, we need options people can put on their phones *now*.

    I'm not trying to slander your project, buddy, but it's not a realistic option for literally *most* android users right now.

    I would absolutely welcome your suggestions or advice.

    💬 2🔄 0⭐ 0
  • Oct 4, 2026, 3:27 PM

    @cocaine_owlbear @retrocomputing @Tutanota The approach of pretending everything is fine and misleading users into believing exploits are only used in advanced targeted attacks is rapidly collapsing. AI accelerated vulnerability discovery and exploit development has made exploits very accessible to non-experts.

    Android's standard privacy and security patches/protections aren't at all adequate. Those alternative operating systems have drastically worse patches and protections rather than better.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:32 PM

    @cocaine_owlbear @retrocomputing @Tutanota Encouraging people to use devices increasingly unable to protect them against severe known privacy and security vulnerabilities isn't going to work out well for them.

    It's important for people to buy devices where reasonable updates and security protections are possible to provide. People should buy used devices with many years of updates and decent security protections rather than bottom of the barrel new Android devices without those.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 7:00 PM

    @cocaine_owlbear @GrapheneOS @retrocomputing @Tutanota the vast majority of android users have locked bootloaders from their service provider anyways, so for them, a new device is necessary if they want to install any alternative OS. I got a brand new unlocked pixel 9a from best buy for $350, the last google device I'll ever buy, and it was well worth it to switch to GrapheneOS.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 5, 2026, 1:06 AM

    @cocaine_owlbear @nahmgood @retrocomputing @Tutanota Most devices sold as locked by carriers don't ever get the ability to unlock the bootloader. It can also take a long time before they allow people to do it which means using it with the stock OS for a long time.

    Budget 'a' series Pixels are extremely high value compared to the higher end devices due to having the same SoC, updates and security features. The cheap option are used 'a' series Pixels. Pixel 8a is still a recommended device.

    💬 1🔄 0⭐ 0
  • Oct 5, 2026, 1:09 AM

    @cocaine_owlbear @nahmgood @retrocomputing @Tutanota Pixel 8a still meets all of our current generation security standards. It has 3 more years of updates than the Pixel 7a due to that being raised from 5 years to 7 for the Pixel 8 and later. It still has around 4 years and 8 months left before the guaranteed updates run out.

    It doesn't make sense to buy a bottom of the barrel new Android device rather than a used Pixel.

    Most people do not use a smartphone where another OS can be installed.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 4, 2026, 8:34 AM

    @Tutanota @GrapheneOS Once fraphine becomes accessible with Talkback out of the box, I'll most certainly support it. Has any progress been made finding a tts engine that complies with licensing restrictions and can be bundled?

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 8:34 AM

    @Tutanota @jolla

    Quizá sea mejor acercarse a alternativas como Jolla.
    Open y Graphene no creo que quepan en la misma frase

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 4, 2026, 11:24 AM

    @fasnix @GrapheneOS we are talking about a 4+year old phone which was a flagship one when it came out. What about modern phones that aren't flagships and are < €300? (Example: Motorola G 56, Samsung A1x/2x series or similar)

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 4, 2026, 9:09 AM

    @Tutanota A shame Google went through with this... Yet not surprising coming from them. The openness of Android served them in the early days of Android to attract people, against big bad "Apple's locked down Iphone". Now it's in their way.
    I used to recommend Fdroid to friends and family. Happy #murena_eos user myself (never had a graphene compatible device to try it), but I can't imagine recommending flashing a ROM to just anyone, not everyone is ready to take that big a step.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 4, 2026, 10:40 AM

    @Tutanota @GrapheneOS

    Problem with Graphene OS, it is only installable on selected google Pixel Phones.

    The cooperation with Motorola is a positive sign but unlikely to be affordable as it will be high end devices only.

    For real acceptance we need devices with a reasonable level of performance for around 300 to 400 Euro.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 2:44 PM

    @Kerplunk @Tutanota

    > The cooperation with Motorola is a positive sign but unlikely to be affordable as it will be high end devices only.

    That's not the case. It's starting with high end devices because those will be the first ones providing reasonable updates and security features.

    > 300 to 400 Euro

    GrapheneOS supports devices in that range and lower via older devices including budget 'a' series Pixels. Pixel 8a meets all of our latest security requirements and has plenty of support left.

    💬 1🔄 0⭐ 0
  • Oct 5, 2026, 3:49 PM

    @GrapheneOS @Tutanota

    Not a criticism of Graphene OS, just we all need it yesterday and many of us can not afford another expensive purchase.

    Apart from the environmental aspect of having to dump good phones, in many cases due boot loader lock.

    Btw.
    Pixel 8a is hovering around 400 Euro in Germany.

    Purchasing one supports google.

    I would prefer not to have to do so.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 10:43 AM

    @Tutanota @GrapheneOS

    #Android is supposed to be open, & your phone should be yours → NOT GOOGLES.

    YES, BUT we need legislation to force release of Bootloader unlock codes for all phones.

    Until we can controll a phone and its software it is not fully our property.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 10:47 AM

    @Tutanota @GrapheneOS This all stem from a duopoly where the other player has a closed ecosystem and profits greatly from that, Google played the useful mirage as the open option for far longer than they needed to and now with no other option left on the table, are giving the middle finger. Maybe regardless how loyal to a slogan or fruit brand, don't let a duopoly take hold, let competition foster, duopoly is worse than a monopoly as people believe that illusion of choice is all that is needed.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 11:35 AM

    @Tutanota @GrapheneOS
    @ccc

    Samsung m8 es den Nutzenden ebenfalls schwer.
    Nach jedem #AndroidUpdate sind individuelle Funktionen gestrichen worden.
    Obwohl bspw. das Samsung A55 mehr kann,
    wird Behauptet, dass gwünschte Funktionen nicht (mehr) möglich seien.
    Mich stört es, dass sog. #Fest_Installierte_Apps nicht vom Gerät entfernt werden können!
    Auch der Zugriff auf SpeicherungsEinstellungen wird angeblich aus SicherheitsGründen arg eingeschränkt. Der SpeicherMisbrauch ist sehr hoch.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 11:43 AM

    @Tutanota @GrapheneOS
    @Bundesverband

    Anführen möchte ich dazu auch,
    ein Kauf von Apps ist ebenfalls nicht (mehr)
    außerhalb von #AsiStore von Google / Samsung
    möglich.
    Dazu noch #PlayServiceNutzungsZwang
    ist ja wohl an Frechheit kaum zu überbieten!
    Wenn das nicht #Wettbewerbverzerrung ist, dass weiß ich auch nicht . . .
    #GooglePlayGuthabenKartenCode funktioniert nicht, trotz Kauf und vorhandenem Guthaben.
    Immer wieder scheitert die Aufladung. 😤

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 11:49 AM

    @Tutanota @GrapheneOS I'm faily positive a "phone" has NEVER been our. Google and others have made sure it it just an extension of their advertising and data collection departments from day one. As are most commercial software products and most appliances, autos and everything else we "purchase".

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 11:54 AM

    @Tutanota @GrapheneOS I couldn't agree more! While I notice that, in the absence of MicroG and Google Play Services, Tuta’s notifications don’t work—unlike other apps (e.g., Signal, Proton, etc.).

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 4, 2026, 12:33 PM

    @Tutanota @GrapheneOS

    Noo nooooo, that cannot be an actual issue!!!!!

    I told everyone 10-15 years ago (i.d. when it wasn't too late) that exactly these things are going to happen.

    All all the smart people around me agreed:

    I'm a stupid idiot. I follow conspiracy theories. I'm a tinfoil hat guy. All these things are FINE and there is DEFINITELY NO PROBLEM AT ALL, everyone agreed.

    So, calm down!!!!

    Everything is FINE!!! ;) ;) ;)

    💬 0🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 4, 2026, 2:57 PM

    @jeroensky @pino @Tutanota That's completely untrue. /e/ adds a bunch of Google services to the OS with privileged access compared to the Android Open Source Project (AOSP). It also adds other privacy invasive services including their own.

    Their supposed tracking protection is a small list of filtered domains for DNS lookups. It can't block the vast majority of the privacy invasive behavior by apps and services due to dual purpose domains. Apps can also trivially evade DNS filtering regardless.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:00 PM

    @GrapheneOS @jeroensky @Tutanota

    @GrapheneOS @jeroensky @Tutanota

    Yeah, sorry for these inaccuracies. I am an /e/OS user (before that, I was a cyanogenmod user (before that was only the HTC Dream)).

    These are some nice additions.

    But the OS itself is still completely a Google product, right? Once AOSP disappears, there's no way these custom ROMs could still make sense, right?

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:05 PM

    @pino @jeroensky @Tutanota /e/ drastically reduces privacy and security compared to the Android Open Source Project. It isn't at all a safe option, especially on end-of-life devices lacking kernel, driver, HAL and firmware updates, but it's far behind everywhere.

    /e/ lags years behind on updates to new major releases with the full set of privacy and security patches. A large portion of privacy and security patches are not backported. New privacy/security protections aren't backported at all.

    💬 2🔄 0⭐ 0
  • Oct 4, 2026, 3:08 PM

    @pino @jeroensky @Tutanota Android Open Source Project (AOSP) is an open source OS and alternative operating systems based on it are forks of it similarly to each Android fork made by an OEM for their devices. The terminology custom ROM is inaccurate on a technical level and propagates many misconceptions about these. These are not modifications of the stock OS on devices but rather a fork of AOSP which runs on the hardware too with firmware and typically also userspace driver code from the OEM.

    💬 1🔄 0⭐ 2
  • Oct 4, 2026, 3:09 PM

    @pino @jeroensky @Tutanota AOSP can be forked and developed further without Google, but currently Google are the ones doing most of the development. It would be a massive amount of work to take over developing the whole OS.

    It would be far better for Android to be split away from Google into an independent company by regulators due to Google's anti-competitive and fraudulent behavior in many areas. They use their monopolies for coercive control over Android OEMs and go back on commitments.

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 3:09 PM

    @GrapheneOS @jeroensky @Tutanota

    Ahh, sry, now I read it slowly enough... You are saying that /e/ is not even that good.

    Well, yeah, might absolutely be true. Personally, I will not spend lots of efforts into migrating to another Google-based OS, though. I WOULD spend money and effort for a system that is ACTUALLY free and not depending on Google at all.

    All these custom ROMs - the good ones and the worse ones - are just a cat and mouse game.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:11 PM

    @pino @jeroensky @Tutanota AOSP is an actual open source OS and be developed without continued releases from Google. That would be an enormous amount of work and very difficult to do but it's entirely possible. It's certainly easier than starting over or trying to turn the desktop Linux software stack into a viable mobile OS with similar usability, compatibility and especially privacy/security. Desktop operating systems are extremely far behind on privacy and security, especially outside macOS.

    💬 3🔄 0⭐ 0
  • Oct 4, 2026, 3:21 PM

    @GrapheneOS @jeroensky @Tutanota

    That will only work for some time, up to the point you've largely lost compatibility to actual recent Android versions.

    But, yeah, fine for me. As soon as this fictitious OS is actually there, I'd take a look.

    But I want to see that new mode of procedure actually working before I'd invest much effort. I don't believe in it at all.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 3:49 PM

    @pino @jeroensky @Tutanota You're using an OS without standard privacy/security patches and protections. Even the standard Android patches and protections are far from adequate to keep users safe, especially with AI models accelerating exploit development.

    Currently, your data is up for grabs by any app which wants to abuse known privacy and security vulnerabilities along with remote attacks. It isn't a theoretical problem. There are public exploits on GitHub which you don't have patched.

    💬 1🔄 0⭐ 0
  • Oct 4, 2026, 4:12 PM

    @GrapheneOS @jeroensky @Tutanota

    Thank you for your hint. Yes, there's probably some risk. I'm not saying it's ideal. But, I think, the actual danger is manageable for me. I would absolutely take action, as soon as anything fundamentally better is available. And spend money. But any other AOSP fork isn't what I'm waiting for. It's still the "Google OS" (unless you manage to split it away from them). Even if you cleverly sell it as "operating system with Android app compatibility".

    💬 0🔄 0⭐ 0
  • Oct 4, 2026, 6:24 PM

    @GrapheneOS @pino @Tutanota
    Why should mac OS be safer then Linux?
    Read only OS does not mean it is safer then Linux (read/write), assuming they both uptodate. I think Open source (Linux distro) is more secure then proprietary (OSX, Windows), because with open source their are way more people who can check for and fix security issues.

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0