Notices by Curtis Carter (codingcoyote@floss.social)

I joined the Android 16 Beta 1 and immediately found a bug that prevents Google Home from launching (reported and being worked on). Unfortunately this is the most I've needed to use Google Home in months and I can't open it. <sarcasm>Software bugs are fun</sarcasm>

There are many ways to solve any given problem and most of them are bad.

#softwareDevelopment

The biggest frustration as an EV owner isn't the range, or the running hum, it's the fact that it tries to evolve into a Jolteon every time I hook it up to electricity to charge it.

I'm fighting the global proxy settings in #aosp I'm not 100% certain the vendor or another dev didn't modify the something in the network stack, but it's unlikely. The #proxy works, but the exclusions list I set with it in the buildDirectProxy method isn't excluding any domains.

Any suggestions would be welcomed :androidalt:

It's come down to trying to debug the network stack... Except I'm not allowed to use #Linux and the tools don't support #Windows

Worse, the RDP connection to he machine with the source code is so slow that it's unusable. I'm using grep, find, sed, and winscp via ssh right now. Anyone with a better way to do this from the terminal would be a godsend.

To people who don't code, digging into the network stack to look for a bug is on the same level as changing the background color of the home app...

@alcinnz I feel like #bittorrent got some stigma due to its use with illegal file sharing, but if it facilitated p2p distribution so well, it's a shame not to utilize it more for legitimate file sharing (it's easily the best way to distribute Linux distro liveCD iso's)