7 ms·

I knew it would be their higher end devices but I really wish they would have put it on their lower end as well. I have a Moto G running LineageOS and it's my

I knew it would be their higher end devices but I really wish they would have put it on their lower end as well. I have a Moto G running LineageOS and it's my favorite phone ever. The ability to have my 800GB of music synced to a sdcard is something I'm loath to give up.

BoldColdHold 1mo ago
Lower end devices simply don't have the hardware required.
- cosmic_cheese 1mo ago
  I would bet that what Motorola can change without trouble on the lower end is more restricted, too. Generally low end models use more parts that are old, off the shelf, and/or shared with several other models to keep costs low, and so major changes can quickly balloon costs.
  - LelouBil 1mo ago
    From the linked url > Lower end devices will take more time to meet our requirements since the updates and security features aren't as good. It's mostly due to how Qualcomm handles it. The latest Snapdragon flagships have the best security features. We'll also need Motorola to start paying them for longer updates below flagships
    - freedomben 1mo ago
      GP is likely right still, the longer updates is an also according to the post.
- grapheneos 1mo ago
  We need the devices to meet our requirements so that's the main limitation. The current generation Snapdragon 8 Elite Gen 5 is the only one providing hardware memory tagging (MTE). Even the slightly lower end Snapdragon 8 Gen 5 doesn't support MTE. The next generation flagship SoC has improvements needed to meet our requirements. There's still going to be a lot of porting and integration work. We'll be the first ones using MTE for the whole kernel and OS as we are on Pixels so there's going to be a lot to deal with for it. For Pixels, Google did do testing for MTE across the OS internally but even on Pixels it isn't perfectly supported and we have to fix a lot of memory corruption bugs it finds in both the kernel and userspace.
AndrewKemendo 1mo ago
What is your music workflow? I got stuck in Spotify for new music but that obviously doesn’t work long term
- paweladamczuk 1mo ago
  Not him but I can as well throw in my setup. For playback, I mainly use Navidrome. For autotagging and importing (moving files), Beets. For tagging edge cases, MusicBrainz Picard as the GUI and the Python tagging lib underneath it (mutagen iirc) with an LLM inside the pi cli agent for automation. For format conversion and copying to portable devices, ffmpeg in custom bash scripts managed by an LLM.
- dietr1ch 1mo ago
  Bandcamp or buying CDs and ripping them, it doesn't take that long and each CD is a fire-and-forget task. I'm using syncthing to avoid the chore of having to copy them into my SD card
  - freedomben 1mo ago
    I really wish more artists would put their music on band camp. I have even noticed that some artists who used to put their albums up there no longer are. It's a real shame
- LarryDarrell 28d ago
  For discovering new music, I listen to my old college radio station. About once a month they play something good that makes me do a deep dive. I use Pianobar while I work, and creating a station based on a new (to me) artist tends to give me more to explore. I also use music-map.com from time to time. As for acquiring music, I use Bandcamp. If they aren't on there, I'm not above finding it via file sharing. I have a bunch of python scripts that help me rename all my files once I get their tags sorted out. For that I mostly use AudioRanger because it's so simple and I only process one album at a time. From there, I use Syncthing. But I'm thinking about replacing it with rsync and just kick it off manually when I want to update everything about once a month.
colordrops 1mo ago
[flagged]
embedding-shape 1mo ago
I had Motorola Moto Gs all from the first generation to the fifth or sixth, cheap and worked great, had everything one could wish for in a daily smartphone. But eventually they too started growing in size, and so I got an iPhone 12 Mini instead, that I still use to this day. I'm currently hoping I'll find something released in 2025+ that is the same size as the Mini or the old Moto Gs, but they are nowhere to be found... I think I'll buy one of those new Motorolas with GrapheneOS just to hopefully vote with my wallet a bit, and make them port it/use it for more phones in the future, which just maybe might eventually be a "normal" sized phone again.
- SoftTalker 1mo ago
  Pretty much the same story. I am hoping my iPhone 12 lasts until I retire and I won't need to carry a smartphone anymore.
- grapheneos 1mo ago
  We want to support cheaper devices too but flagships will be the first ones meeting all of our update and security features requirements. Providing hardware memory tagging (MTE) and a good enough secure element with the modern AOSP APIs are the main requirements for hardware security features. Snapdragon 8 Elite Gen 5 is the only current Snapdragon SoC with hardware memory tagging since even the slightly lower end Snapdragon 8 Gen 5 didn't provide it due to being developed a bit earlier despite being launched later. They tried to provide it for both but didn't get it fully working in time. The next generation makes major secure element improvements. We potentially could have supported a Snapdragon 8 Elite Gen 5 with a secure element from another company but there wasn't enough time and the next generation is a lot better in multiple ways. There's still a large amount of porting and integration work remaining to do.
- deleted 1mo ago
  [deleted]
username135 1mo ago
This! Expandable storage is priceless to me and the main reason I opt for this product.
grapheneos 1mo ago
Motorola's flagships are going to be their first devices providing the updates and hardware-based security features required by GrapheneOS. It will come to lower end devices but it will take longer. Snapdragon 8 Elite Gen 5 is the first Qualcomm SoC with hardware memory tagging (MTE). MTE isn't even available on the slightly lower end Snapdragon 8 Gen 5. A lot of the SoC security features are segmented based on price and only the flagship SoC platform has everything we need. Snapdragon's upcoming next generation SoC is the first truly providing everything we need. There's still a lot of work to do since providing the features on paper is different from having those fully integrated to match what we have on Pixels.
- wishfish 29d ago
  Replying to you here in hopes you see this question. I'm one of those people who is affected by PWM on OLED screens. I tried a Pixel 9 Pro XL and it didn't work for me. Have a Razr 2024 which mostly works and that's thanks to some custom PWM settings from Motorola. Will Graphene OS have these custom PWM mitigation settings on 2027 Motorolas?
  - wishfish 27d ago
    If anyone runs across this comment in the future, the answer is: YES. On Mastodon, they told me they will have full support for Motorola's custom PWM settings.
deleted 29d ago
[deleted]

BoldColdHold 1mo ago

Lower end devices simply don't have the hardware required.

cosmic_cheese 1mo ago
I would bet that what Motorola can change without trouble on the lower end is more restricted, too. Generally low end models use more parts that are old, off the shelf, and/or shared with several other models to keep costs low, and so major changes can quickly balloon costs.
- LelouBil 1mo ago
  From the linked url > Lower end devices will take more time to meet our requirements since the updates and security features aren't as good. It's mostly due to how Qualcomm handles it. The latest Snapdragon flagships have the best security features. We'll also need Motorola to start paying them for longer updates below flagships
  - freedomben 1mo ago
    GP is likely right still, the longer updates is an also according to the post.
grapheneos 1mo ago
We need the devices to meet our requirements so that's the main limitation. The current generation Snapdragon 8 Elite Gen 5 is the only one providing hardware memory tagging (MTE). Even the slightly lower end Snapdragon 8 Gen 5 doesn't support MTE. The next generation flagship SoC has improvements needed to meet our requirements. There's still going to be a lot of porting and integration work. We'll be the first ones using MTE for the whole kernel and OS as we are on Pixels so there's going to be a lot to deal with for it. For Pixels, Google did do testing for MTE across the OS internally but even on Pixels it isn't perfectly supported and we have to fix a lot of memory corruption bugs it finds in both the kernel and userspace.

AndrewKemendo 1mo ago

What is your music workflow? I got stuck in Spotify for new music but that obviously doesn’t work long term

paweladamczuk 1mo ago
Not him but I can as well throw in my setup. For playback, I mainly use Navidrome. For autotagging and importing (moving files), Beets. For tagging edge cases, MusicBrainz Picard as the GUI and the Python tagging lib underneath it (mutagen iirc) with an LLM inside the pi cli agent for automation. For format conversion and copying to portable devices, ffmpeg in custom bash scripts managed by an LLM.
dietr1ch 1mo ago
Bandcamp or buying CDs and ripping them, it doesn't take that long and each CD is a fire-and-forget task. I'm using syncthing to avoid the chore of having to copy them into my SD card
- freedomben 1mo ago
  I really wish more artists would put their music on band camp. I have even noticed that some artists who used to put their albums up there no longer are. It's a real shame
LarryDarrell 28d ago
For discovering new music, I listen to my old college radio station. About once a month they play something good that makes me do a deep dive. I use Pianobar while I work, and creating a station based on a new (to me) artist tends to give me more to explore. I also use music-map.com from time to time. As for acquiring music, I use Bandcamp. If they aren't on there, I'm not above finding it via file sharing. I have a bunch of python scripts that help me rename all my files once I get their tags sorted out. For that I mostly use AudioRanger because it's so simple and I only process one album at a time. From there, I use Syncthing. But I'm thinking about replacing it with rsync and just kick it off manually when I want to update everything about once a month.

colordrops 1mo ago

[flagged]

embedding-shape 1mo ago

I had Motorola Moto Gs all from the first generation to the fifth or sixth, cheap and worked great, had everything one could wish for in a daily smartphone. But eventually they too started growing in size, and so I got an iPhone 12 Mini instead, that I still use to this day. I'm currently hoping I'll find something released in 2025+ that is the same size as the Mini or the old Moto Gs, but they are nowhere to be found... I think I'll buy one of those new Motorolas with GrapheneOS just to hopefully vote with my wallet a bit, and make them port it/use it for more phones in the future, which just maybe might eventually be a "normal" sized phone again.

SoftTalker 1mo ago
Pretty much the same story. I am hoping my iPhone 12 lasts until I retire and I won't need to carry a smartphone anymore.
grapheneos 1mo ago
We want to support cheaper devices too but flagships will be the first ones meeting all of our update and security features requirements. Providing hardware memory tagging (MTE) and a good enough secure element with the modern AOSP APIs are the main requirements for hardware security features. Snapdragon 8 Elite Gen 5 is the only current Snapdragon SoC with hardware memory tagging since even the slightly lower end Snapdragon 8 Gen 5 didn't provide it due to being developed a bit earlier despite being launched later. They tried to provide it for both but didn't get it fully working in time. The next generation makes major secure element improvements. We potentially could have supported a Snapdragon 8 Elite Gen 5 with a secure element from another company but there wasn't enough time and the next generation is a lot better in multiple ways. There's still a large amount of porting and integration work remaining to do.
deleted 1mo ago
[deleted]

username135 1mo ago

This! Expandable storage is priceless to me and the main reason I opt for this product.

grapheneos 1mo ago

Motorola's flagships are going to be their first devices providing the updates and hardware-based security features required by GrapheneOS. It will come to lower end devices but it will take longer. Snapdragon 8 Elite Gen 5 is the first Qualcomm SoC with hardware memory tagging (MTE). MTE isn't even available on the slightly lower end Snapdragon 8 Gen 5. A lot of the SoC security features are segmented based on price and only the flagship SoC platform has everything we need. Snapdragon's upcoming next generation SoC is the first truly providing everything we need. There's still a lot of work to do since providing the features on paper is different from having those fully integrated to match what we have on Pixels.

wishfish 29d ago
Replying to you here in hopes you see this question. I'm one of those people who is affected by PWM on OLED screens. I tried a Pixel 9 Pro XL and it didn't work for me. Have a Razr 2024 which mostly works and that's thanks to some custom PWM settings from Motorola. Will Graphene OS have these custom PWM mitigation settings on 2027 Motorolas?
- wishfish 27d ago
  If anyone runs across this comment in the future, the answer is: YES. On Mastodon, they told me they will have full support for Motorola's custom PWM settings.

deleted 29d ago

[deleted]