Welcome to the Android community on Lemmy. 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:
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:
I see a framerate/refresh rate bug that occasionally locks the framerate at a low value upon unlock. Fixing it requires a lock/unlock cycle.
my reporting process generates about 170'000 csv files, totalling 4.5GB. it takes about 10min to write them; which 9min 58 secondes longer than I need to compute them. Any suggestions ?
Assuming that this is happening not because the destination write media is simply too slow, but because the process is unnecessarily fsync()ing writes to disk mid-process, maybe try:
$ sudo apt install eatmydata
$ eatmydata <reporting-command> && sync
Are you gonna play the 'That's fair' game? Meaning the first bad thing to happen to the phone you say that's fair and leave it where it is forever just to buy a new phone to start over?