Shouldn't do, all supported devices can use GCam out of the box without Play Services.
To use features dependent on Google Photos you'll need to install sandboxed Play Services.
Our default Secure Camera is capsble of many if not all functions however we rely upon the CameraX API and each individual vendor providing the extensions to enable them.
Google haven't as of yet for the Pixels (Samsung is the only OEM so far) however these should come with Android 14 for existing Pixels and/or the Pixel 8. However, it may initially require sandboxed Google Play. We will have to see. When they do our camera app will be able to function to it's potential.
I use the above, Aves Gallery is also another one I've seen used by community members.
Yeah I get you, made me nope out too. Until I brought myself to tentatively scroll slowly to one of their least offensive/dangerous posts and block/report them.
Should be able to when curated properly using blocks, and in cases like this block and reporting for seriously egregious content. Otherwise it harms discoverablity. I believe in a centralised censorship resistant platform but personal curation is important to retain engagement.
Some accounts also share a lot of content with a 50/50 split interest wise that I wouldn't want the other 50 spoiling my Follow feed with.
Having blocked and reported a certain account "LoveAI" I believe, for some seriously questionable content not even marked NSFW, is there anyway on Amethyst nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z for the Global image feed from showing my avatar and the fact I have them blocked on every one of their uploads? Scrolling through numerous of these to find content is making the Global feed unusably monotonous.
This one...
Having blocked and reported a certain account "LoveAI" I believe, for some seriously questionable content not even marked NSFW, is there anyway on Amethyst nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z for the Global image feed from showing my avatar and the fact I have them blocked on every one of their uploads? Scrolling through numerous of these to find content is making the Global feed unusably monotonous.
It's in the pipeline. ETA unknown while Android 14 is the primary focus.
Thankyou for your continued support. 👍
GrapheneOS Foundation Transition Clarification Update:
We're continuing to make progress towards moving stewardship of GrapheneOS to the non-profit GrapheneOS Foundation. We'll be replacing our previous announcement with more detailed info on our website. We removed the thread here since it was being misunderstood and misrepresented.
There has been a significant effort to spread fabrications and spin targeting our project members with the clear aim of directing harassment towards them. Our founder stepped down as lead developer due to extreme level of harassment including multiple extreme swatting attacks.
We explained in detail how we were moving forward by transferring responsibilities to the GrapheneOS Foundation and the new lead developer. We explained it would be a long process. We don't understand how what we posted was so widely misinterpreted as someone leaving the project.
We have a team of 6 full time developers that's growing along with people working on the non-profit organization. Nearly all have been involved for many years. We've avoided other project members being targeted with significant harassment by minimizing their public exposure.
Due to the extreme attacks on GrapheneOS, most of our project members aren't comfortable with a public facing role. It's why there are so few interviews with our team, and part of why it's so difficult for us to build up the non-profit since people don't want to become targets.
We have a substantial amount of funding available to the non-profit that's not yet being used because of the difficulty in expanding the team under these adverse conditions. We could have 12 full time developers or more, but we don't because of these attacks on the project.
The way we've protected our team led to increasingly more targeted harassment towards the only person who had a public-facing role. The attacks shifted from technical misinformation to bullying/harassment based on misrepresentations/fabrications referencing the past harassment.
Top 4 or 5 reactions with a ... button to expand. Feed would get really cluttered otherwise.
ANDROID 14 SITUATIONAL UPDATE:
Stable release of Android 14 is expected to be released in early October. We've spent months preparing for it and we've completed a lot of porting in advance. This has been much more difficult than it should be since we have to rely on unofficial access to pre-launch sources.
Stable releases of Android are open source. Pixel stock OS source tree matches the AOSP source tree with additional private repositories added for the Google/Pixel components/overlays. Beta releases and the development branches are mostly internal. Most isn't done in AOSP main.
The Android security team wanted to collaborate with us and gave us security partner access. We hoped this would lead to us getting full partner access so that we could port to new major releases much earlier with the ability to build and test nearly all of the port in advance.
The engineering side appreciates our work and multiple prominent people have tried to get full partner access for the GrapheneOS Foundation. Android's business side had our security partner access revoked and blocked progress. We've decided to stop making upstream contributions.
Many of the privacy and security features we're built could be included in Android. It was always difficult to contribute without partner access, but we put in significant effort and achieved some positive results. We also reported a lot of firmware and software vulnerabilities.
Not having partner access makes quickly porting to major releases into an ordeal, but we still have to do it for security reasons. We only managed to have it done within around a week of launch of Android 13 and past releases via superhuman amounts of work hours and productivity.
Our policy for upstream Android vulnerabilities we discover has become fixing them downstream ASAP with a clear explanation in our release notes for the release including them. Filing a report upstream hasn't been part of our process for a while due to their related decisions.
We've deferred shipping most of our newly developed features until after Android 14 including duress PIN/password and several new per-app toggles for enabling additional security features we already had implemented but couldn't enable globally due to some apps being incompatible.
GrapheneOS. Better be vigilant.
https://discuss.grapheneos.org/d/7712-tweet-and-the-graphene-forum-announcements-deleted
Vigilant to what and why?
With the length of support being provided it makes perfect sense as an investment.
nostr:npub1zs3zftl4jjr0r3dzrrdfcj7f4cdq944cgrvpw35l2q3hxj3jpe9sfrhlqa no like i said extended support is only for the newest EOL devices
Correct, our extended support releases provide all the AOSP and GrapheneOS changes. It's unclear if extended support will continue for the Pixel 4, Pixel 4 XL and Pixel 4a after the release of Android 14 but we'd like to continue it. However, firmware and most drivers won't get updates. To temper expectations we generally make clear ESR will continue 12 months after the last major OS an EOL device receives. Anything more is a bonus, however it could be less dependent on regressions.
Ideally you should be moving to a 7th generation Pixel from the 4th Gen. There are only a couple days to a couple weeks remaining before the Pixel 4a is behind on security patches regardless of your OS choice. Our extended support releases are only harm reduction, not a solution.
Receiving patches for all known serious vulnerabilities is part of the basics. You won't have that on an end-of-life device. Continuing to provide all the AOSP and GrapheneOS changes for end-of-life devices via extended support releases fundamentally can't provide this.
The past 2 generations of devices have 5 years of proper support from launch. Only the Pixel 5a and earlier had 3 years of proper support from launch. It stopped making much sense to buy them once the Pixel 6 was released if you want to use devices for a long period of time.
If budgets are a concern then the Pixel 6a should be a target. It would make little long term sense to buy anything below this.
nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c How long does it take to support new Pixel models?
We offer no ETA or timescales however for an approximate idea the last two major OS were ported to within a month.
Agree, very much has religious or cult like undertones encouraging people to volunteer to be sheep/cattle to wedded to personalities.
Exceptionally well, but I might be biased 😜
Our Matrix chat rooms are once again being severely impacted by major flaws in the protocol and the main implementations of it. It appears to have been caused by temporarily making rooms invite-only in response to raids targeting our project members and community with harassment.
Matrix's federation design makes it extremely vulnerable to abuse and it has very weak anti-abuse tools. One of the few tools available to us is making the rooms invite-only temporarily, but unfortunately the broken protocol and implementation leads to that bricking our rooms.
This has happened to us multiple times before. Each time, it disrupts our rooms and we lose a significant portion of our community on Matrix. Matrix has never fixed these issues and only option has been replacing the room via a room upgrade and inviting everyone to the new one.
Room upgrades don't work well and the notice isn't received by the many users no longer able to sync with bricked rooms. Extracting a list of users in the room and inviting them will miss the users who got dropped by the state reset and many people have invites notices disabled.
There's no good option available to use unless [Matrix] investigates the issue, determines the cause and helps us fix our rooms. They could surely figure out why it's breaking and implement a fix including recovering our rooms without us going through all this again.
The question wasn't related to rooted devices. If individuals wish to root their devices and remove system components, break functionality, power to them. Your device is your device.
Doing so breaks the security model and is not an avenue I can spend time discussing as it can't be supported by us.
You cannot alter permissions of system components.
https://discuss.grapheneos.org/d/3038-comgoogleandroidiwlan/2
I completely appreciate that position. Just in the same way I can see and understand why people make their own choices for their own reasons.
It is often something many people misjudge when our team discuss technical or objective differences etc. on what can be an emotive topic.
However the information through such discourse isn't just for those in the thread but those who might read it and have the privilege of being able to make a different choice. Provided for accuracy and posterity.
Taking the best measures available to you is always commendable.
While I understand people taking a position they believe strongly about, which is admirable, something to consider is that while GrapheneOS might require the one time purchase of a Google product, not doing ensures that data points between you and Google persist.
LineageOS always use multiple Google services while giving them privileged access even if users don't use microG. It would be wrong to imply they don't use Google services. microG is of course an implementation of Google services at the system level.
To clarify further they always use Google services for the following:
°Connectivity checks
°Network time
°Attestation key provisioning
°SUPL
°DNS fallback
°PSDS
°eSIM activation
°and more
ALL enabled by default.
This includes any other OS based on it too.
GrapheneOS doesn't use or provide privileged Google services by default.
GM #Nostritches
#GM #GoodMorning #GIF #Nostrland #Amethyst #Android #GrapheneOS
|￣￣￣￣￣￣￣￣￣￣￣￣|
| We 🖤 GrapheneOS |
|＿＿＿＿＿＿＿＿＿＿＿＿|
\ (•◡•) /
\ /
——
| |
|_ |_
Yeah Osmand is the reverse Obtainium is showing a lesser version as latest even though latest I have is the one on F-Droid. 🤷♂️
Seemingly an issue with Obtainium as I've got the same on Osmand+ try disabling:
As far as revealing specifics that's outside my purview and would come from the main project/foundation accounts.
From what is already in the public domain though we were in discussions and thought we had found an OEM interested in working with us but they got sidetracked by a different focus (crypto). We think they would have have had a much more successful project if they'd heavily collaborated us and focused on making a highly private/secure device. We're still open to this, however as it stands has stalled.
We're currently in talks with another, major OEM, about early collaboration which we hope will eventually lead to them producing devices which we can support. This is going to take longer than expected since things didn't work out with the previous OEM we were in talks with, mentioned above.