Yes, I thought that was where I looked and didn’t find the switch - it just showed the feature without a choice to turn it off. Then after your comment I made sure to look in the actual right place and sure enough, there it was. I am not feeling very intelligent right now.
no worries
sometimes one gets lost in the settings like in a maze
Out of curiousity reproduced similar behaviour as described above:
Forcing stop and cleaning storage is undone after system reboot, even though it is turned off in input settings…
Does App info give a package name if you scroll down to the end of the page?
(To use it with Uninstall default apps - #29 by AnotherElk … or alternatively, perhaps Shizuku and Canta might provide a way without a computer and the command line.)
I haven’t updated my phone running /e/os to 3.01 yet, but if I have heartburn with Murena VTT, I’ll just disable it from the command line. No big deal. Through as a matter of principle, “disabled” should not be greyed out in the Apps settings.
Why do so many apps do that for seemingly no reason? Every bundled app likes to think it’s critical to the system. I mean some are, especially if you list system apps, but few are in the regular apps list.
Hello!
I’m on holliday since a week and using mobile data only. My Murena VTT is switched off and the microphone and messages are granted to MVTT by default. In my mobile data consumption per app there is no MVTT listed, so I believe there is no connection to OpenAI. And I also believe that no voice data is surreptitiously sent to OpenAI, otherwise my 500MB mobile volume would not last as long as it does. The consumption is coherent!
Personally I installed FUTO some months before MVTT came and I was really surprised how good it workes. For long Texts it is much faster than typing on this tiny screen keyboard! But it is as Gaël said: mixing different languages is a problem.
So I can understand the decission of Murena and I appreciate a solution for raising the privacy level. I personally will go on using FUTO, because it saves (mobile) data.
This is not surprising at all. When you deny the permissions for the microphone and notifications, this will be stored in your cache/user data. If you then clear this, the original permissions will be restored.
I believe on my S7 the name is foundation.e.stt
I tried with the ADB commands
adb root
adb shell pm uninstall --user 0 foundation.e.stt
And it seemed to be removed, this is a test phone so not sure what effects are on other apps or if the OpenAI api is removed.
It is.
You can follow-up the command for uninstall by:
pm clear foundation.e.stt
… to remove the remaining linked userdata of the now-removed application.
Then everything should be gone regarding STT.
Since the -k option to keep the data was not used with the uninstall command … user data is still left to clear?
Not sure if individual settings of integrated applications are removed without the -k parameter or if there could be something left due to it being integrated into the image itself, snippets which might be stored in different places.
The (repeated) removal won’t do damage if there’s no data left due to uninstall without -k.
Hey @Manoj can you keep us updated regarding the documentation ? Is it coming out soon ? Thanks
I’m very late to this conversation, but since this thread is about to be closed in 4 days (why are useful user conversations artificially truncated in this way?) I would like to add my comments.
Whilst enormously grateful for the incredible efforts of dreaming and creating /e/OS, this type of imposition of software that is contrary to the desires and interests of much of the userbase is upsetting.
Stating that ‘No data is sent to OpenAI’ when anonymised biometrically identifying recordings are sent to them is sadly, not answering questions openly and transparently. I could only think, will Murena next send video of me to CorporateAI and then tell me that it’s okay, they changed the username. Recordings are biometric data as has been stated repeatedly above. That data is our data.
If there is a conflict of interests between simplicity of installation and feature modernity with privacy and security, then surely that could be handled with a ‘Default or Custom Install’ option at the outset (ensuring unwanted components are never on the device), plus the ability to subsequently permanently remove perceived dangers such as Maps app, VtT etc.
This seems like it would provide the clarity and transparency, safety and usability, feature richness or sparcity, customisation or vanillaness that everyone is asking for.
Clearly, the dream is that your Grandma can be at ease and happy with an /e/ device… but also clear is that the project is the driven by the dream of getting away from the dangers of corporate tech.
I wish I didn’t feel like Gael was warning us that his canary was dead.
I’ve been a user for many years now. Let’s keep the project true to its original purpose AND growing. Also, thanks to everyone who has kept the tone as civil and impersonal as possible around these big topics.
@Manoj … can this topic stay open longer?
I would like to add that all the negativity towards the decisions in regards to OpenAI VtT is overshadowing some brilliant ideas here, like the implementation of “find my device” via a secret code that can be sent to the device via SMS that is then handled on-device.
It just surprises me how they apparently didn’t anticipate any of the backlash integrating OpenAI services inevitably caused.
I would have expected it to be obvious that the vegetarians they assembled do not take well to discovering bacon in their food, even if it is anonymised bacon.
This topic has been open in different posts with different words and the same message. On our side responses from Gaël have also been published. The team understands that not all users are happy with some of the new features but we also need to balance with our corporate users and non technical users. Users have requested for this feature and some do use it. The implementation was also explained and the source code is also available publicly. For those who do not want to use these features the simple option is to not enable it. The point that information about new features needs to be shared before they are implemented has been conveyed.
I’m glad to hear that things will hopefully be bettercommunicated in the future.
What about the other main concern of biometric data being sent to OpenAI? It’s not stated clearly in the documentation, but there is a line about it in the privacy policy. I get that some people will want to use this feature anyways, but users should be clearly warned.
The insistence about privacy in the documentation seems disingenuous without a clear warning about the sharing of biometric data. It’s insisting on more privacy than was actually there that made me lose all trust in big tech. This feels like the same thing to me.
For all the malcontents: patch notes aren’t for dogs.
For the rest, maybe the foundation should have a big communication on the forum when new specific services are added to /e/OS in order to channel user reactions and allow the foundation to explain certain choices made (and also allow community members to reply to each other) without it creating multiple posts.
Thanks to the /e/ foundation for all the work they’ve done since the start.
This topic was automatically closed after 30 days. New replies are no longer allowed.