Hardly have time to write new and original content this days. Some of the emails correspondence makes pretty good blogging material. So I always have a desire to dedicate a special section for this. Just never find the time to do so. Until now. Hopefully this will be a good way to add some content to this blog. Here’s the first, and hopefully many to come.
From Marc (31st Mar 2019 4:43 PM):
on atom absed? i got a black screen on atom n2800 BENCH OF RETARDS
From Marc (31st Mar 2019 10:26 PM):
hi after waitng few minutes ON A NONSENSE black screen installation began after waitng loooong to let the setup finish scanned my Library took a hear test i installed latest firmware AND ALL MY TIME got to trash!!!!!!!!!! i’m using Windows 2012 core optimized for free that sounds a WAYYYYYYYYY better than your crap system DO YOU REALLY THINK I WILL PAY A CENT FOR THIS SHIT fuck you retard and put your stupid system in your big asshole
I’ve been wanting to get one for a while since I first tried the Bose Quiet Comfort 35 II. The Bose is my first positive experience of ANC, and the Bose is THE phone to buy if you want the best ANC.
Here in Australia, we see QC25 and QC35 for sale/demo in the shops; and we see people wearing them like a fashion statement out in the streets.
The Bose has the best ANC, but not any more.
There is a new kid in town. All hail the market leader in ANC - the Sony WH-1000X M3.
Like Bose, this came from the left field. And like like Bose, it asserted it’s authority immediately on arrival. And now the Sony sits atop the mantle as the best ANC headphones available in the market today. If you need any proof the Bose has been toppled, just look at the street price for a pair of QC35II now. Stores has no choice to cut the price to compete with the Sony.
Actually, this Sony has been available for sale for a while (The M3 is released probably around ~ Aug 2018 if not earlier). It just took me this long to snag one at a good price - just under AUD$300.
This trend is getting really tedious to be honest, and it really shows the immaturity of the developers of not thinking things through. Honestly I never liked the concept of agile development. Developing at such a rapid pace with no time to think through good/solid design concepts may well be this project’s downfall.
They seriously need to have a stable branch for backwards compatibility, and only introduce breaking changes when they are finally ready to make it release 1.0.0. But who am I to complain? I’m not involved in the development at all. So really need to suck it up, and do all the necessary changes to make Google Assistant work again.
Note this walk-through is aimed for Home Assistant 0.80 and above.
Bits are bits - and your computer playback will always be perfect. Right?
Do not answer that - the above is a rhetorical question.
No matter how good your computers are - once in a while you may find your computer is running fine one minute but suddenly crash in the next.
The rarer this phenomenon occurs, the harder it is to troubleshoot the cause.
There are many reasons why a system may crash this way. More often than not, the main cause is simply badly written software. The less usual suspects are leaky motherboard capacitors, poor quality ‘Yumcha’ power supply and issues like over heating.
However, there is one component that is often overlooked, and this component can cause unpredictable system or software failure. This component is the main focus of this article, and you you probably already know what that is: