[Fire TV General] harlekinwashere:
I am sorry to inform you - but even if they JUST have hidden the adb toggle in a hidden "service menu" - the question is why.

Of course product bloggers won't ask it openly, because despite catering to users interest, they have 5 other Alexa *blub , bleep - use voice search - its so eazy* articles to pump out every day.

If you are hiding away the adb toggle it puts up another barrier of entry there - behaviorally, for the normal user. Amazon playing their freaking "take their rights one pinprick at a time" game is just as despicable as it was on day one -

and the only reason they are still doing it, is that everyone lets them get away with it, no questions asked.

(

- Why are you adding a blacklist to an open source operating system you borrowed from the linux community?

- Why are you banning launchers, whose functionality you stole from community developers, add a banner ad to yours, and then roll it out (depreciated, because - the Echo audience, never needs to force close or quickly uninstall their apps, or to sort them, or to hide some apps that arent accessed daily) as the new default?

- Why are you banning Kodi - but allow in Kodi Clones as soon as they have stripped out the python interface that enables streaming webenabled content (Isn't that anti competitive to the highest extent?)

- Why are you modifying adb - so some features like parsing logs become impossible?

- Why are you hiding away the development features behind a hidden key combination, so normal users loose the feature - until they are told how to find it again?

- Why have you bloggers that champion you for your interface decisions and who make podcasts about every new menu you add running this scene - but then don't mention it, if your redesign is basically "stealing all the design lessons you could take away from Kodi (which you just kicked out of distribution" and Microsofts Xbox OS? )

- When they took our launchers - the bloggersphere chanted "finally its become eazier".

- When they kicked Kodi (the "browser" of the set top box age), the bloggersphere filled you with all kinds of BS articles about how great it would be to use one of the mangled forks, that had to vow, never to inclue a scriptable python backend - because using the internet as informed users - is something Amazon gets very uncomfertable with. With them its all simple voice button prompts to get stuck in their echosystem with and waging war against EVERY AND ALL open standards, apis, the OS itself...

- When they started blacklisting apps - the bloggerspehere wrote them the excuses for why its ok, and they'd never cross the red line that is blacklisting Kodi. WHO CARES? Blacklisting launchers was enough to mangle the homebrew ecosystem once and for all -- no developer writes code for your benefit, when its clear as day - that amazon stealing it and banning the initial app not only is commonplace in the Fire TV ecosystem - its cheared on by bloggers.

Take your eazy voice commands - and get straight out of this community. If your intention is to whitewash every move Amazon implements to make "running your own code" on the FireTV "just a little harder", but instead would like to promote Amazons paid services - while they introduce blacklists to Android and hide away the developer bridge behind presumably a remote key combination - you have become complacent.

Amazon has made it very clear - that the only way for you to get access to the android ecosystem openly - is to block their updates - hiding away the adb toggle is just another stabwound.

If you wan't to exchange "Echo" and "i watch show - by saying "houswives" and it plays" for access to an unfiltered internet, different sources that don't have to pay Amazon the required obolus, or apps that are actually usable (Amazon App Store apps are often slow to the point they become unusable, or get pulled shortly after release, because they crash all the time - of course, bloggers don't make that their focus - ) - be my guest --

but don't play the "oh - its nothing" - they do all of this to benefit the user game, like some others in here. I get irritated by that. Immensely.

Also - don't abuse this forum for requests on "Echo" and "I hit button and cloud does the work" stuff - because it is specifically out of our reach. As tinkerers, as hackers, as consumer advocates. If you wan't that stuff - you sign away your rights and pay a subscription fee. With that comes paid support and a cookie cutter community that finds "having bought the right trinket" is all the tribalism they'd ever need.

Don't try to bait people with Echo - in exchange for loosing yet another accessibility feature - because its suddenly hidden.

Don't become the blogger that scrambles on his way to contact the company to give a denial as soon as an issue pops up - turn on your brains instead, and don't just neglect the steps Amazon sets to shut out their audience from the outside world a little more.

Everytime they put up another wall - people scramble to explain it away and offer you a little more "Echo" inside your walled garden.