Mine is fully charged at 64%
Same here.
100%
<Comment deleted by user>
First we need to know the register size, or bit-count, to derive the hex value.
Just sayin ...
Just sayin ...
Does percentage make sense in hexadecimal? Maybe it does.
But isn't 64% = 64/100. I.e., not full? 100/100 could be hexadecimal. 256/256 in decimal.
Calling on mathematicians.
But isn't 64% = 64/100. I.e., not full? 100/100 could be hexadecimal. 256/256 in decimal.
Calling on mathematicians.
45%
OK, you got me ... I think in terms of 'register size' out of habit, but strictly speaking, one can express any value in terms of its 'hex' representation ... thank you for making me think again ...
For the non-specialist, 'fractional binary values' are often handled in high speed controllers by a method called 'scaled binary values' ... so the value is actually a fraction of whatever desired scale, 'appropriately scaled' to reside within a given architecture's register size as an integer ... anyways, it gets somewhat challenging when balancing silicon budget with tolerable truncation error ...
For the non-specialist, 'fractional binary values' are often handled in high speed controllers by a method called 'scaled binary values' ... so the value is actually a fraction of whatever desired scale, 'appropriately scaled' to reside within a given architecture's register size as an integer ... anyways, it gets somewhat challenging when balancing silicon budget with tolerable truncation error ...
@Frogster64 said in #6:
> Does percentage make sense in hexadecimal? Maybe it does.
>
> But isn't 64% = 64/100. I.e., not full? 100/100 could be hexadecimal. 256/256 in decimal.
>
> Calling on mathematicians.
I interpret % to mean, parts per hundred units.
How many (parts per hundred units) exist in a fully charged battery life, measured in hexadecimal for a phone?
What is the upper limit of fully charged? How should we do the conversion?
Either, there are:
1. There might be 16^2 parts total, representing fully charged = 256 parts in decimal terms, or 100 in hexidecimal.
2. There might be 16*6+4 parts total in decimal, which written in hexidecimal is 64 units, representing fully charged.
Given, percent is normally written in decimal terms. I'd give more probable weight to the 2nd, and less to the first, even though the parts per 100 could be in written in hexidecimal, meaning that it is actually out of a possible 256 decimal units.
Because, I don't fully understand the question, it's hard for me to say, based on the meaning of %. (parts per hundred units).
> Does percentage make sense in hexadecimal? Maybe it does.
>
> But isn't 64% = 64/100. I.e., not full? 100/100 could be hexadecimal. 256/256 in decimal.
>
> Calling on mathematicians.
I interpret % to mean, parts per hundred units.
How many (parts per hundred units) exist in a fully charged battery life, measured in hexadecimal for a phone?
What is the upper limit of fully charged? How should we do the conversion?
Either, there are:
1. There might be 16^2 parts total, representing fully charged = 256 parts in decimal terms, or 100 in hexidecimal.
2. There might be 16*6+4 parts total in decimal, which written in hexidecimal is 64 units, representing fully charged.
Given, percent is normally written in decimal terms. I'd give more probable weight to the 2nd, and less to the first, even though the parts per 100 could be in written in hexidecimal, meaning that it is actually out of a possible 256 decimal units.
Because, I don't fully understand the question, it's hard for me to say, based on the meaning of %. (parts per hundred units).
I think he just wants you to convert a decimal number to hexadecimal.
This topic has been archived and can no longer be replied to.