Just today I noticed how Android Oreo (8.1) on my Nexus 6P can actually see my Bluetooth headset's remaining battery capacity. I didn't even know that my headset could send out this information! Windows never presented this information to me, and neither did my tablet which runs Nougat 7.0. Apparently there's multiple implementations of that battery level reporting too.. so lack of support in Microsoft's driver makes sense. Especially given that the Bluetooth standard already counts several thousands of pages. Compare that to Wi-Fi which is far more complex (with - some of - its 7 OSI layers, 2.4GHz and 5GHz frequencies, MIMO etc) which counts only 400-ish pages. I'm surprised that Google actually supports this Bluetooth battery reporting at all.. implementing all the standards must've been quite the chore.

TL; DR: Bluetooth is an overengineered piece of shit, and is in dire need of refactoring.

I don't know if this is a problem only in Belgium or also in other countries but while I love Bluetooth for audio playback (headsets, speakers and everything) despite being extremely convoluted as a protocol.. FUCK Bluetooth keyboards.

Several of them I've tried. Several of them, from various brands. Pairing, setting the Belgian keyboard layout (which on that shitty Android 7.0 tablet that I want to use the fucking things with apparently has to be done *every fucking time you connect*, because reasons) all well. Except half the keys don't fucking map properly. A keymap, it doesn't get easier than that! How hard is it to make buttons map to the right keys!? They're literally fucking push buttons on a matrix! Seeing which points in the circuit make contact and sending that off to wherever it needs to go!

And to put the icing on the cake? USB keyboards with the same fucking layout settings work without any problems. So it's extremely likely that it's something in those shitty keyboards' controllers or Bluetooth going full rart on all of them.

Of course, Bluetooth being as convoluted as it is, manufacturers just copy each others' implementations of it if they can.. so there's that.

Can really nobody make a product halfway decent anymore before putting it on the market!?

Another one bites the dust.. JUNK!!! Every single goddamn one of them!

Thank you, Slack

Learn More is just a bunch of unsolicited instructions

The worst part about owning a non Nexus Android phone is the long wait for the next version of Android. I want 7.0 but I'm not even sure if my s7 edge on Sprint will get it before the year is over

My teacher gave me his phone during class and told my to give him Android 7.0 (HTC m7) and now I am plowing through Verizon's bullshit to unlock the bootloader

Fuck motherfucking android 8 fucking sideways. And Huawei for that matter too.
My battery drains like 30% faster since the update from 7.0, with even more app limiting than in 7. I've already ranted about UI stuff, but that is negligible compared to this bullshit.
Also, auto brightness is broken and it keeps blinding me fora few seconds in the dark, and choosing way too much brightness.
I've loved my otherworldly battery life, now I feel like an apple user with 4k mah.
I used to get one and a half day battery, now I barely get through the day.

When Nougat came out a month ago and you still don't have it on your S7. Nougat= Android 7.0. My background pic is me..

Which do you like Android
4.0 Kitkat
5.0 Lollipop
6.0 Marshmallow
7.0 Nougat

Bug report

Using a physical keyboard seems to prevent me from being able to complete a post. I can open both a comment and new rant, type the contents but am not able to post. The button doesn't do anything.

Switching off the keyboard seems to cause strange behaviour (deleted this rant the first time I was trying)

My setup:
Moto z play android 7.0
SwiftKey keyboard app
Logitec K810 Bluetooth keyboard

Another android update. More media server issues even on 7.0.

I thought 7.0 was supposed to sort this stuff out?

An eventful day:
Because of my recent amateur thermopaste application onto a heatpipe that connects a laptop CPU and a discrete GPU and *ingenious* HP ProBook engineering my Radeon graphics have fried yesterday.

On the bright side, got the Nougat update for my Samsung S6, with bright hopes that it will help restore the state of an unresponsive fingerprint scanner... nope, that is still broken.

Summer is near, exams finished, time for some DIY on used and abused tech! :D

Genuine rant 😫
Volley library the heck.
The request that is added to the request queue is being executed on Android 7.0 and above but is not executed in any API level below that.
Try and help me please.