All the more reason to give yourself a bigger domain (101 elements instead of 5). You don't need to map into the percentage domain directly from signal strength; you could easily define a function of data/voice connectivity as throughput to a percent scale.
"But data and voice have different quality of service criteria and blah blah blah!" So make up a function that accounts for this. Or add another indicator for data exclusively and keep the bars for voice.
you could -EASILY- define a function of data/voice connectivity
as throughput to a percent scale.
"But data and voice have different quality of service criteria
and blah blah blah!" So make up a function that accounts for this.
Translation: insert magical code here?
You remind me of people who say "Your videogame is so slow, why don't you use multiple cores? Just use threads, you could easily do it."
And yet this problem has not only been solved but been subsequently broken by marketers. Some things that seem easy are actually hard. I'm sure defining the appropriate function isn't all roses but a semi-competent software/radio engineer could figure out something with the right properties. With Apple's budget, they couldeasily do this.
"But data and voice have different quality of service criteria and blah blah blah!" So make up a function that accounts for this. Or add another indicator for data exclusively and keep the bars for voice.