[-] AlmightySnoo@lemmy.world 1 points 1 hour ago

they obviously have upscalers in their brains

[-] AlmightySnoo@lemmy.world 3 points 2 hours ago

Reminds me of when it was smelly as hell in our house a few years ago and when we checked just by chance the roller shutter of one of the windows, we found a dead bird in there which probably got stuck there and was crushed to death.

[-] AlmightySnoo@lemmy.world 2 points 2 hours ago

according to https://nitter.net/onbeeper/status/1733385534545052129 it's only Beeper Cloud they're talking about in the update, they're saying "work continues on Beeper Mini" meaning it's likely not operational yet and users in that thread seem to confirm it

[-] AlmightySnoo@lemmy.world 2 points 3 hours ago* (last edited 3 hours ago)

Biased opinion here as I haven't used GNOME since they made the switch to version 3 and I dislike it a lot: the animations are so slow that they demand a good GPU with high vRAM speed to hide that and thus they need to borrow techniques from game/GPU programming to make GNOME more fluid for users with less beefy cards.

[-] AlmightySnoo@lemmy.world 5 points 15 hours ago

You just need more EXP to unlock the Appraisal skill

[-] AlmightySnoo@lemmy.world 9 points 16 hours ago

It's as if you are in an isekai

[-] AlmightySnoo@lemmy.world 70 points 20 hours ago* (last edited 19 hours ago)

Double and triple buffering are techniques in GPU rendering (also used in computing, up to double buffering only though as triple buffering is pointless when headless).

Without them, if you want to do some number crunching on your GPU and have your data on the host ("CPU") memory, then you'd basically transfer a chunk of that data from the host to a buffer on the device (GPU) memory and then run your GPU algorithm on it. There's one big issue here: during the memory transfer, your GPU is idle because you're waiting for the copy to finish, so you're wasting precious GPU compute.

So GPU programmers came up with a trick to try to reduce or even hide that latency: double buffering. As the name suggests, the idea is to have not just one but two buffers of the same size allocated on your GPU. Let's call them buffer_0 and buffer_1. The idea is that if your algorithm is iterative, and you have a bunch of chunks on your host memory on which you want to apply that same GPU code, then you could for example at the first iteration take a chunk from host memory and send it to buffer_0, then run your GPU code asynchronously on that buffer. While it's running, your CPU has the control back and it can do something else. Here you prepare immediately for the next iteration, you pick another chunk and send it asynchronously to buffer_1. When the previous asynchronous kernel run is finished, you rerun the same kernel but this time on buffer_1, again asynchronously. Then you copy, asynchronously again, another chunk from the host to buffer_0 this time and you keep swapping the buffers like this for the rest of your loop.

Now some GPU programmers don't want to just compute stuff, they also might want to render stuff on the screen. So what happens when they try to copy from one of those buffers to the screen? It depends, if they copy in a synchronous way, we get the initial latency problem back. If they copy asynchronously, the host->GPU copy and/or the GPU kernel will keep overwriting buffers before they finish rendering on the screen, which will cause tearing.

So those programmers pushed the double buffering idea a bit further: just add an additional buffer to hide the latency from sending stuff to the screen, and that gives us triple buffering. You can guess how this one will work because it's exactly the same principle.

[-] AlmightySnoo@lemmy.world 3 points 1 day ago* (last edited 1 day ago)

it's possible that you have the IzzyOnDroid repo on your app and the latter automatically picks up the IzzyOnDroid entry once it extracts the "com.akylas.documentscanner" name from the URL

[-] AlmightySnoo@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

“these bots”: Yeah, you are being an asshole

I'm pretty sure he didn't mean his colleagues and is rather talking about the UiPath bots, it's an IT automation tool... 🤖

[-] AlmightySnoo@lemmy.world 3 points 1 day ago

If he's a contractor it's unlikely he'll stay there for too long. I'd bring up the improvements and potential gains (faster processing, ideally no more UiPath license costs) directly with your boss. If they're still not open to that then yeah I'd look elsewhere, because even as an IT automation job it just screams laziness.

[-] AlmightySnoo@lemmy.world 4 points 1 day ago

but some of these processes involve going through Excel files which can take these bots 10s of minutes, which can be done instantly in any scripting language

The key is being proactive. Have you tried suggesting that to them? Do a small POC with say a Python script and show them the difference on one of the Excel files, they're likely to like your alternative. They're likely to have poor data warehousing too and it could be an opportunity for you to shine and at the same time get to learn to do that for them from scratch.

[-] AlmightySnoo@lemmy.world 3 points 1 day ago* (last edited 1 day ago)

You're maybe referring to this app: https://apt.izzysoft.de/fdroid/index/apk/com.akylas.documentscanner

It's not on the main F-Droid repo (hence the 404), but it's on the IzzyOnDroid repo.


The thread link points to the fixes and enhancements brought by the December update. At the same time there's also a feature drop for Pixel devices, a summary of which you can see below:

For now, Video Boost seems to be exclusive to the Pixel 8 Pro despite it being done on the cloud.


tl;dr: they basically decompiled the latest APK of Google Photos and found these strings which give a few hints about how the "Video Boost" feature of the Pixel 8 Pro would work:

“To boost your videos, turn on backup in settings, or back up this individual video”

To use Video Boost, you need to back up this video, which requires signing in with your Google Account

“Waiting to back up video”

“Backing up for Video Boost. This may take some time. A notification will be sent when your video is ready.”

“Boosting video quality. This may take some time. A notification will be sent when your video is ready.”

“This may take some time depending on video length, internet speed, and battery status. A notification will be sent when your video is ready.”

“Boosting your video won’t affect your phone’s battery life or performance, but it may take some time. A notification will be sent when your video is ready.”

The boosted video could also be exported as a AVC or HEVC file according to the same decompilation.

submitted 1 week ago* (last edited 1 week ago) by AlmightySnoo@lemmy.world to c/googlepixel@lemmy.world

Any Pixel 8/8 Pro owners using the new "Read aloud" feature? What is your impression of it?


He uses C++ and the SFML library throughout the course. He just uploaded the last lecture 3 days ago.


Also from the official announcement (https://blog.mozilla.org/addons/2023/11/28/open-extensions-on-firefox-for-android-debut-december-14-but-you-can-get-a-sneak-peek-today/ ):

Starting December 14, 2023, extensions marked as Android compatible on addons.mozilla.org (AMO) will be openly available to Firefox for Android users.

“We’ve been so impressed with developer enthusiasm and preparation,” said Giorgio Natili, Firefox Director of Engineering. “Just a few weeks ago it looked like we might have a couple hundred Android extensions for launch, but now we can safely say AMO will have 400+ new Firefox for Android extensions available on December 14. We couldn’t be more thankful to our developer community for embracing this exciting moment.”


A thread by @Reddit_refugee7834@lemmy.today (cross-posted from: https://lemmy.today/post/3507919 )

This is a guide to a longer lasting Android device, from choosing one to how to preserve the life of the one that you have.

Choosing a long-lasting and repair friendly phone:

To get the best shot at longevity, start with a high quality device from a manufacture with a history of long term device support, and one that regularly releases there modifications to the kernel source code. A device that has an unlockable bootloader (XDA developers Forums is a good place to see about ROM support), and is user repairable (See iFixit's Smartphone Repairability Scores) will allow you to keep the software & hardware going the longest. Both the Google Pixels, and Fairphone's line are a good place to start.

Before you use your phone

  • Use a good sturdy case like an Otterbox
  • Apply a liquid “screen protector” then a screen protector on top, Sapphire being the best (but very expensive).


Lithium-ion (LI-on) battery's wear out faster when near the upper and lower charge levels (read why here: Battery University, so avoid charging or discarding the battery fully, aiming for around 20~80% is a good target.


  • Avoid fast & wireless charging. (to reduce the heat the battery endures)
  • Use a magnetic charging cable to reduce the wear on the plug (Like Volta), you need a bulky case to have it flush to not make the phone uncomfortable to hold though. 
  • When/If you use a regular charging cable don't move the phone when it's plugged in, movement wears the plug much sooner.
Use a charge limiting feature. (Listed in order of recommendation.)
  1. If your phone has a built Smart battery charge management feature, use that.
  2. If you have Root use ACCA(a GUI for ACC) (recommended, automatic)
  3. Buy a cut off switch, like a Chargie by Lighty Electronics that's has an app to auto cut off power based on power draw or charge level. Note that in The newest Android versions restricts the APP from auto enabling Bluetooth, making this a bit of a meh solution. Using an Automation APP like Tasker to turn off a Home Assistant-controlled smart plug when the battery exceeds a reprogramming threshold might be a more reliable method. 
  4. Download an APP that alerts you at charge levels, (AccuBattery, Battery Guru: Monitor & Health, etc.

Waking & Locking the screen

Try to avoid using the power button, as it's a common fail point

To wake 

 1. Use the features "Lift to check phone/events" and "Double-Tap to check phone"

 2. Use the fingerprint reader to wake and unlock.   

To lock/turn off the screen  

 1. Use a launcher that support double tapping the home screen to lock it (Nova launcher, Smart launcher, etc.)

 2. Use Googles Quick Tap feature if you have a Pixel or the APP Tap, Tap for any Android to lock the screen. (Note: battery life might suffer)  

 3. Use a short Screen Time out.

  • Get a new case to get a fresh look and feel when your tired of the one you have
submitted 1 week ago* (last edited 1 week ago) by AlmightySnoo@lemmy.world to c/googlepixel@lemmy.world

In the latest release of GrapheneOS, you can now enable hardware memory tagging for all user installed apps on the Pixel 8 and Pixel 8 Pro to make them substantially harder to exploit. This is particularly useful for apps like Signal and WhatsApp.

More info in this thread: https://grapheneos.social/@GrapheneOS/111479293301664182

A bit of a technical update, but in a nutshell this improves memory safety, and for those familiar with pointers, you can watch this nice video explaining it: https://www.youtube.com/watch?v=UwMt0e_dC_Q

submitted 1 week ago* (last edited 1 week ago) by AlmightySnoo@lemmy.world to c/android@lemmy.world

I also compiled the update schedule into a table for those who prefer it this way:

The "(?)" are for when the precise day isn't known yet.


Apparently the update is for the Pixel 8 Pro only, and someone in the comments is claiming that Magic Eraser got faster with it.


Google now not only acknowledges the bumps that some users noticed but also tries to reassure them that those bumps are nothing to worry about:

Pixel 8 phones have a new display. When the screen is turned off, not in use and in specific lighting conditions, some users may see impressions from components in the device that look like small bumps. There is no functional impact to Pixel 8 performance or durability.

For instance, here's one photo from Google's official Pixel forums:

view more: next ›


16824 post score
8526 comment score
joined 5 months ago