People would then learn that at x% they are getting decent data speed, and at x% things become unusably slow, at x% voice service drops off, etc..
"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.
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."
Practical problems are rarely easily solved.