I want to stop charging my e-scooter at around 85% because this will increase the battery life. To avoid always having to pull the plug at the right level, I made a stop circuit that goes between charging brick and e-scooter.

There's no processor involved, just a CMOS 555 used as inverting Schmitt Trigger which controls a power mosfet. Also two status LEDs and a start switch. The poti adjusts the cut-off level. Worked on first try, with only manual voltage and tolerance calculations beforehand!

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.

*sees how Facebook kicked me out of my Bitlbee session again*
Me: "Motherf-..."

Still there's some friends of mine on Facebook who apparently got really hooked.. can't for the love of the holy Raven seem to get them away from that shithole.

"Alright then Facebook.. your win. I'll install Messenger and Pages Manager again to at least have your shit be semi-usable again 😑"

*installs said apps*

"Holy shit that battery is draining fast, and I'll have to go out in half an hour"

*plugs phone in fast charger*

*phone while charging keeps on dropping battery level*

FACECUNTS!!!!!! 😤

*powers off phone to conserve battery life and goes off to cook a meal*

*comes back to boot up the phone again and uninstalls those Face-crapps*

*phone immediately starts raising its battery level super fast*

Coincidence? I think not 🤔🤔🤔

I kind of feel like I invested 2.5 years of my life trying to run away from being a hamster, and here I am in my PhD back in the hamster spot.
The moment I finish compiling some not-os-compatible package, I get a new one to tame. A day after perfecting a sensor integration, another sensor is thrown at me. I am the one who calibrate and tunes the MoCap system, including manufacturing the markers and ordering part. I make sure the robot is functional, from software to battery replacement.
I need to crawl on floors to collect data, while the rest of the lab uses public datasets.
I optimize C++ code, and then get asked to write unit tests and use a CI, while the rest of the lab just writes some subpar Python.
They are doing research and I am doing Cinderella work.
I shouldn't be punished because I get shit done, whether it 3D modeling, CMake voodoo or low-level programming.
Instead of encouraging other lab mates to develop skills, everything is thrown at me. Fuck that shit.

My Sunday Morning until afternoon. FML. So I was experiencing nightly reboots of my home server for three days now. Always at 3:12am strange thing. Sunday morning (10am ca) I thought I'd investigate because the reboots affected my backups as well. All the logs and the security mails said was that some processes received signal 11. Strange. Checked the periodics tasks and executed every task manually. Nothing special. Strange. Checked smart status for all disks. Two disks where having CRC errors. Not many but a couple. Oh well. Changing sata cables again 🙄. But those CRC errors cannot be the reason for the reboots at precisely the same time each night. I noticed that all my zpools got scrubbed except my root-pool which hasn't been scrubbed since the error first occured. Well, let's do it by hand: zpool scrub zroot....Freeze. dafuq. Walked over to the server and resetted. Waited 10 minutes. System not up yet. Fuuu...that was when I first guessed that Sunday won't be that sunny after all. Connected monitor. Reset. Black screen?!?! Disconnected all disks aso. Reset. Black screen. Oh c'moooon! CMOS reset. Black screen. Sigh. CMOS reset with a 5 minute battery removal. And new sata cable just in cable. Yes, boots again. Mood lightened... Now the system segfaults when importing zroot. Good damnit. Pulled out the FreeBSD bootstick. zpool import -R /tmp zroot...segfault. reboot. Read-only zroot import. Manually triggering checksum test with the zdb command. "Invalid blckptr type". Deep breath now. Destroyed pool, recreated it. Zfs send/recv from backup. Some more config. Reboot. Boots yeah ... Doesn't find files??? Reboot. Other error? Undefined symbols???? Now I need another coffee. Maybe I did something wrong during recovery? Not very likely but let's do it again...recover-recover. different but same horrible errors. What in the name...? Pulled out a really old disk. Put it in, boots fine. So it must be the disks. Walked around the house and searched for some new disks for a new 2 disk zfs root mirror to replace the obviously broken disks. Found some new ones even. Recovery boot, minimal FreeBSD Install for bootloader aso. Deleted and recreated zroot, zfs send/recv from backup. Set bootfs attribute, reboot........
It works again. Fuckit, now it is 6pm, I still haven't showered. Put both disks through extensive tests and checked every single block. These disks aren't faulty. But for some reason they froze my system in a way so that I had to reset my BIOS and they had really low level data errors....? I Wonder if those disks have a firmware problem? So that was most of my Sunday. Nice, isn't it? But hey: calm sea won't make a good sailor, right?

I just LMFAO(ed..?) at myself so hard.....

Messing around with all the option in the Android Emulator's "Extended Controls" window, and I was playing with the battery level slider.. got a little carried away, and suddenly my emulator just shut down.. by itself!

🤔

It took me way longer than it should've to realise what happened. But yeah, that's what Android does when your fucking battery reports 0%.

🤣🤣🤣🤦

I think I must stop working now, this day is done with me.

Gdpr thing aside...

Does anybody read the new policy...

I just did for 2 apps (intel driver software and 9ga.. You know it)...

On the things that they collected on the side without you knowing include:
9ga:
Device memory, language, battery level, timezone, unique device identifiers, compass, accelorometer and microphone... Even service provider and signal strength

Intel:
Website you visit, how you use your computer(vague too vague) and computing environment.

Did anybody knew for sure before this that their apps are listening to them? That they just made a profile of you with all the data?

With all this they dont even need your ip they already know who you are and what you do on a daily basis...

There are 20 more but it will be waaay too much to write about. These 2 are way worse since 9ga doesnt use microphone for anything... And why a driver reads what websites i am going to?

How modern smartphone OSs (Android) deal with battery charge.

// handler for when the battery level changes
public void onLevelChange (BatteryInfo info) {
if(info.batteryLevel() < 99) Device.getBattery().drainAllCharge()
}

Got the iphone mini cuz I was ecstatic to have a small phone that I could use on one hand on the IOS ecosystem.
Found out that apple might discontinue the line for the next iteration due to "poor sales".

It really doesn't matter to me what operating system I am using for the phone, I wanted to give the IOS ecosystem a go with the release of this model. But man it kinda hurts that everyone is hell beant on large screens. Even the standard pixel phone feels too big. I do not want a "tiny" phone, even if one of my favorite Android devices was my Sony Ericsson XPERIA. To me the size of the iphone 5s was perfect. I just want companies to go to that again man. And I do know that there are models for Android that are capable of reaching similar sizes, its just that finding a premium level experience on a phone that size from the Android size gets hard to adjust to carriers etc.

I am liking this little fucker though, very speedy, nifty, decent battery time, camera etc.

I now have further proof that Android 9's fancy Battery Management is shit:
The compass on my new (flagship) smartphone uses the air pressure sensor and the air pressure at sea level to display your current elevation. The air pressure at sea level is fetched from the weather app. And of course, the weather app has its battery policies set to auto-managed.
Can you guess what happened? "Weather app could not be found" and an elevation of -17m
Because no one thought the battery manager could decide that the weather app should not be launched by other apps. Has no one thought this through? Good thing I figured out what was happening pretty quickly.

!rant

Accomplishments of today:

- Wrote a small battery level script for my polybar config to print "AC" as battery level if the battery is removed, rather than having it continue to display the level the battery was at when I removed it (how the polybar module does by default)

- Small bluetooth detector script (checks if bluetooth is on or off, and if it's connected to anything)

- Wrote another script to turn my screen's backlight off when the lid closes and back on when it opens again (literally just finished this one maybe 5 minutes ago)

- Finally fixed an issue with the volume level module on my polybar config, where it increments in levels of 5%, but it would always be on like 94 or 89, rather than 95 and 90 (weird to explain)

Pretty accomplished with myself, they were all minor differences that most people wouldn't really think about, but I'm happy about them.

Look at the battery level!! 🤩🤩🤩🤩

I am using Dell Insipiron 7567.
I have dual booted my rig with Ubuntu 18.04 and Windows 10.

Right from the start itself I couldn't get to the screen of trying or installing with default settings. I had to use 'nomodeset' with 'quiet splash'.

Even after installing I had problems. After some hours of searching I found out that installing Nvidia 390 driver would remove the bug. It did. But my rig heats like shit. And throttles very much. Where as I am not using anything other than
1.chrome
2.vscode
3.terminal

Which i think is very normal?
And looor of battery drain.

I used to get around 3-5 hrs of battery life in Ubuntu Gnome 16.04 but now its like max 2 hrs.
Which is bad I guess.

I switched back to "X.Org X server" driver with "nomodeset" (without nomoseset it will load upto login page. Once i hit enter it gets stuck) it boots up but can't change the level of brighness or can't do anything related to display setting. Temperature has reduced but sacrificing on display settings.

Is there any way to remove this bug?

And additional infos

Graphics in about shows something like "llvmpipe (LMVM 6.0, 256bits)"

Guys do respond please?

Anyone have any decent Android apps for showing bluetooth headset's battery level info on status bar? (It can be a non-closeable notif)

FYI, an iPhone can detect this knock-off headphone's battery level. My phone doesn't have a viewing option as a stock widget/app.