Today I learned that if you install the opengapps package for Android 9 (Pie), it'll bootloop to recovery instead of loading up. Apparently same goes for the S4 too. They just don't like the recent opengapps packages. Use MindTheGapps, they work fine.
Edit: Turns out there was a bug in opengapps when I tried to install. Figures... works fine now.
09 October 2019
01 October 2019
DD-WRT allowing setting of initial username and password then locking out, and unable to TFTP new firmware
Seems it's the day for discovering things. I upgraded to the latest Brainslayer DD-WRT release on an R7000 at work. So far, so good, fairly standard stuff. I'd wiped it beforehand, set my PC IP to 192.168.1.2, got to the web interface, set the username and password as previous, clicked on setup, waited, and then watched myself repeatedly get a "connection reset" message. I figured it was a bad flash. Tried to TFTP a new copy of the image in, it wouldn't take - turns out it works better if you use the .CHK format for that. Got out a USB-TTL interface and flashed it manually, wiped it, rebooted.
Same problem.
After much head scratching, it turned out the problem was in fact a combination of my browser and saved credentials (in this case, provided by Kee and KeePass). Because I had previously saved HTTP credentials for 192.168.1.1 on an unrelated router, it tried to repeatedly automatically submit them to the HTTP auth request, and it looks like I triggered anti-lockout rules.
Whoops!
Suffice to say opening the router was unnecessary, but at least I had the kit handy and ready.
Same problem.
After much head scratching, it turned out the problem was in fact a combination of my browser and saved credentials (in this case, provided by Kee and KeePass). Because I had previously saved HTTP credentials for 192.168.1.1 on an unrelated router, it tried to repeatedly automatically submit them to the HTTP auth request, and it looks like I triggered anti-lockout rules.
Whoops!
Suffice to say opening the router was unnecessary, but at least I had the kit handy and ready.
Microsoft Remote Desktop breaks with error 0x800706be every time you try to make an outgoing connection
I was getting the above "An authentication error has occurred (Code: 0x800706be)." every time I tried to remote out of my work PC. Couldn't figure it at all, and thought it was the machine I was trying to remote into. Turns out that the CSR Harmony Bluetooth stack (it's old, but the only way to easily get APT-X on a reasonably cheap bluetooth dongle for my Sony headphones) breaks the authentication. Wtf.
Renaming C:\Program Files\CSR\CSR Harmony Wireless Software Stack\BLEtokenCredentialProvider.dll to something else (I went with .disabled, but whatever works) instantly solves the problem, and doesn't seem to affect the bluetooth setup at all.
Mostly keeping this here for my own benefit, but hopefully it'll help those searching for an answer.
(Originally spotted via https://community.spiceworks.com/topic/1778270-rdp-from-windows-10-to-anywhere - took me ages to find the answer, over several months!)
Edit: New versions of Windows 10 don't play nice with the CSR Harmony Bluetooth stack. It should be removed. But be aware, I've seen it break the Bluetooth audio stack when doing so - to the point Skype crashes when attempting to initialise the Bluetooth microphone. Haven't found a fix yet.
Renaming C:\Program Files\CSR\CSR Harmony Wireless Software Stack\BLEtokenCredentialProvider.dll to something else (I went with .disabled, but whatever works) instantly solves the problem, and doesn't seem to affect the bluetooth setup at all.
Mostly keeping this here for my own benefit, but hopefully it'll help those searching for an answer.
(Originally spotted via https://community.spiceworks.com/topic/1778270-rdp-from-windows-10-to-anywhere - took me ages to find the answer, over several months!)
Edit: New versions of Windows 10 don't play nice with the CSR Harmony Bluetooth stack. It should be removed. But be aware, I've seen it break the Bluetooth audio stack when doing so - to the point Skype crashes when attempting to initialise the Bluetooth microphone. Haven't found a fix yet.
Edit 2: Apparently Solarwinds RMM also causes the same problem. Guessing other third party authentication systems can cause similar problems.
Subscribe to:
Posts (Atom)