Ok, so there has been plenty to say about the lack of the Download Booster feature from within Verizon, Sprint and ATT Galaxy S5 models. T-mobile is the only carrier who seemingly decided to allow the use of the feature on their network, which is certainly a disappointment to some. The interesting thing is, that the Verizon and ATT variants of the Galaxy S5 actually have Download Booster still. The feature was discovered by a friendly member over at XDA, who are the folks you would definitely expect to come across this type of discovery. As one would have it, all you would have to do to find the feature would be to first install a home launcher application like Nova or Apex launcher, both which have the option to create system shortcuts to place on the homescreen, after the which the feature could be found and turned on.
While the feature actually does exist on the devices, finding it and toggling the feature on does nothing at this point in time, which means there is probably something else on the carrier side that is preventing it from operating correctly. There will eventually be some way of getting around this as the development community is a pretty crafty bunch and it most likely won’t be long before someone has a fix to turn the feature into a usable one. That will probably require root access though, and a tad bit of patience as we wait for the devs to work their magic in this area.
This wouldn’t be the first time that a blocked feature has required some finagling to jumpstart it into a usable status. As of now there a good number of possible scenarios on the table that could see Download Booster as a usable feature to consumers in the future. The carriers who have chosen to block or remove the feature initially could end up updating the devices down the line which would officially make the feature available to users, or we could end up getting it through an unofficial means which is basically with some tweaks to the device which as stated above, would most likely require root access from the user. Now that we know the feature actually exists on those devices, users just have to play the waiting game.