Use version 2.0.1 for now...
To add if using the 3.5mm adapter some require TRRS cables where some use TRS. The officisl Google one expects TRRS.
Also something to keep in mind that I haven't mentioned which may play a part in this, there's only digital USB-C audio on Pixels, no analog so your mic and/or DAC/Amp needs to be digital. Also when you do get it to work, volume can be low. Using an amp that can provide -10dB is advised also if you encounter it.
The 3.5mm to USB C is that the official Google one?
Yes the extensions are now available in Android 14, however due to currently requiring 'Pixel Camera Service' and Native Code Debugging = On, it will be a little time before they're implemented into GOS.
Please be patient as we make the transition to 14 proper (Stable Release) at which point other considerations can be given appropriate attention and prioritisation.
Is the mic actually USB C or are you using a 3.5mm to USB C adapter?
Is this a case of not working in all apps or any in particular such as the GOS Camera app?
I'm trying to get external USB microphones to work with Graphene OS, but none of them are recognized and the camera / call app uses the internal mic.
Any tips?
nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c
Are you plugging them in before unlocking? If so unplug, unlock then plug back in.
USB Peripherals FAQ:
Not having one on hand I can't confirm but if the 6th and 7th Gen are anything to go by any in camera feature will work.
Features requiring Google Photos integration and usage however will depend on sandboxed Play Services.
No we implement a cross profile notification system info is here:
https://grapheneos.org/features#notification-forwarding
As for Open EUCC, the team is already investigating an open-source implementation for eSIM activation, however, what currently exists out there doesn't support the latest standards, so it isn't a complete replacement or ready for implementatiin into a production ready OS.
For broad use across the OS or just for input from a keyboard?
A suggestion for the latter is Sayboard:
https://github.com/ElishaAz/Sayboard
For the former I am unaware of any robust solution.
GrapheneOS is now based on Android 14. Most of our changes have been ported already but we still have a lot more porting work to do. It's all going to need to be tested before we can get it all merged, and then we can start making public experimental releases based on 14.
It should happen in under 2 weeks and we'll try to get it out as soon as possible. Don't forget to expect after internal testing to go through experimental releases, followed by an alpha then beta channel release being mindful we only had very limited access to the sources before October 4th.
Don't use TTS myself however RHVoice has a Github Discussions and I found this which may help?
just find GCam in aurora store and its saying no trackers and no permissions, is that really true? how is that possible that google create such app? So I assume, as nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c is saying too, using GCam in base profile { not work profile either another user } is OK and safe.
Yes, the only downside is EXIF data will be present in GCam where it isn't by default in our Secure Camera.
Ahh yes loved having the Swagger Mode toggle 😆 great pic!
Short Answer: No
Long Answer:
Pixels are currently the only phones meeting basic security requirements while also providing proper alternate OS support. There are other phones doing one or the other but not both. We want to support other devices but we aren't going to accommodate a massive security downgrade.
In most casrs those devices don't meet basic security requirements which is why we don't support them due to the purpose of GrapheneOS being providing a highly private and secure mobile device.
Hey man me too, did my fair share of rooting/tinkering back in the day. Using Cyanogen, LeeDrOiD, AOKP, AICP, Dirty Unicorns, PAC ROM, Viper, Android Revolution et al
What OS are you running, it may need a TTS (Text to Speech) engine?
They haven't tended to however we believe they may decide to match major OS updates and security updates as they've committed to for Pixel 8. That said who knows, these are minimum time commitments at the end of the day.
Fantastic comparison between common alternate OS recommended in the #security and #privacy spheres for #Android devices.
CONFIRMED
Pixel 8 and Pixel 8 Pro are confirmed to have at least 7 years of full support:
support.google.com/nexus/answer...
We expect 6th and 7th generation Pixels will also receive major OS updates until the end of their security support period. Bear in mind these are a minimum, not when it ends.
If Google isn't an issue: Google Speech Services
If Googlr is an issue: RH Voice
The above are the two most recommended by our community.
Checked stock and it's the same as GOS. It's an app issue.
Android 14 will likely be released on October 4th and Android 13 will no longer have monthly or quarterly stable releases. Android 13 will only have the monthly release of the Android Security Bulletin (ASB) patch backports to 11, 12, 13 and soon 14. Those aren't all the patches.
The full set of patches is provided by the monthly, quarterly and yearly releases of Android. Their policy is for every Critical/High severity AOSP patch to be backported. Most Moderate/Low severity patches aren't backported. However, severity levels are often very arbitrary.
Pixels will only be supported by Android 14 going forward so the many patches for firmware, drivers and other hardware-related code will only be available via Android 14. This is why GrapheneOS has focused so much on porting to Android 14 in order to quickly migrate over to it.
Will have access to a stock Pixel device later will check that for you too.
Just tried on my device, Tor is indeed available within the app after wallet creation but there is no UI for it before hand.
If someone can confirm and show it being available on stock then we can troubelshoot it from a GOS perspective. Otherwise it lies with the app itself.
We'll be releasing an early October security update today since there hasn't been an official Android Open Source Project and stock Pixel OS release yet. They'll likely release it with Android 14 and we'll be fully focused on quickly porting to Android 14 once it's available.
With Android 14 on the horizon, the #GrapheneOS dev team have their noses to the grindstone hard at work to ensure a smooth expeditious and secure transition for users across all supported devices.
Cheer them on...
grapheneos.org/donate
Yeah wouldn't use without one, changed case to a fashion one for an evening out and before I left dropped it 30cm to the ground and ended up replacing the screen. Spigen/Cyrill cases my go to never off and fit well with screen protectors.
Ahh I felt the same the LaForge isn't for everyone but when the design language results in Pixels being identifiable in the wild like the iPhone cluster it works.
Did you use the web installer? Also the Keyboard is just the stock AOSP keyboard. Don't feel the need to stick with it, Google left it languishing when they forked it and advanced it with GBoard.
Florisboard is great for swype/swipe.
Anysoft is another oft recommended Open Source KB as well as Openboard and Simple Keyboard (SimpleMobileTools has a suite of AOSP replacement apps)
You could also just choose to use GBoard with permissions like network revoked.
On the OS choice some information to consider:
