Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Mine shows 702mb of user data after about 6 months of call history. However I don't find this very unreasonable for the feature set provided.
The app continues to function offline so I could imagine a cache of the information gets generated once the application is launched and permissions granted.
First off, it appears to source contact information, this appears to be standardized because access is backed by the Contacts permission scope. I imagine it caches this information, because it also builds an index of your contacts in order to drive the t9 dialer search.
The phone also offers integration for voicemail and visual voicemail transcriptions. These would either need to be stored in the app, or associated with the data if it rests outside of the apps directory.
Finally there is the call history. It looks like Android has a standard location for this because it has its own permisson scope.
This means, in order to maintain functionality when offline, the app would have to store associations to contacts, the call history, voice transcription text, and voicemail audio.
The look up of this information could be slow to do each time a tab is opened so it likely stores these associations in a local database for quicker access. That local database would need to be stored in the apps directory contributing to its size.
Almost all of that (excluding voicemail) is pure text data, isn't it? There's no way it should be taking up multiple hundreds of megabytes. I can't imagine voicemail audio is particularly high quality, but if you do have a load of messages then I can see it adding up.
My Phone app user data is 277MB.
Google Keep (lots of notes with offline mode) is 10.62MB.
Google Maps' offline maps for my entire local area is only 109MB.
All of the data you mentioned, voicemail audio included, would be about 10 megabytes.