lichess.org
Donate

What is your % Battery Status in Hexadecimal?

@Dukedog said in #10:
> I think he just wants you to convert a decimal number to hexadecimal.

Well, the easiest number to convert is 0. 0 = 0. There, I converted a number! (and played along).

However, something tells me, telling him the battery status of an uncharged, backup phone, I didn't look at, isn't exactly what he wants.

Where, even if it had a 'surface charge' or I charged it some, after looking at it, it might be a number less than 9%, but, even 9% is 9%.

It would be cool to be the first one to say, it had A% charge, which I could do. lol. a little silly, tho. :)
@Approximation said in #11:
> Well, the easiest number to convert is 0. 0 = 0. There, I converted a number! (and played along).

Just stop typing, I want your battery level out of 0x64.
<Comment deleted by user>
its base 16, computer scientists use it because its easier to read and remember than the longer binary (base-2). Hex is also used in colour codes for similar reasons
@keatanpatel said in #18:
> its base 16, computer scientists use it because its easier to read and remember than the longer binary (base-2). Hex is also used in colour codes for similar reasons

2^4 = 16, where that is the same as asking 4 (Yes/no) binary questions, for each storage unit, and the math can be added up, after taking the smallest amount of color contribution to it.

I wonder what the 4 binary based questions would be hypothetically, giving 16 possible answers, and then stretching that out to get the 4k resolution, or so. I could do this, in theory, with 16*16*16 = 4096 color possibilities of information = 1000 in hexidecimal.

I can imagine 3 color based yes/no, questions, as follows:
1. Add Red element? (Yes/no).
2. Add Green element? (Yes/no).
3. Add Blue element? (Yes/no).

That's where each combination of the 3 question answers, totals 8 possible answers, because 2^3 = 8.

That makes me wonder what the 4th question could be?

It could be: Make it Brighter? (Yes/no).

Idk, in reality how they do it - but, this way seems reasonable.

But, is this right? Just 16^3 data information for each pixel, per refresh rate?

This topic has been archived and can no longer be replied to.