Related
I always try on not to be a party p**per but also would like to make this debate as civilized as possible so no need to bash me if you found my doubts in a negative way.
But after spending all this time with the Nexus Player of Google, I found myself with the conclusion, why is worthy my time for any root for the device.
At least I have a goal on showing my step-dad that paying DirecTV (Nothing against DirecTV BTW, just want to save money) is not 24/7 cost-effective versus Google Play Service and popular streaming services.
Heck, I didn't even felt left out in terms that versus Apple TV, the Nexus Player is still short without service like WWE, Amazon, NFL, etc. I was happy with the service available as of the writing of this.
To tell you the truth, the exact moment when I read all the possibility for free TV and streaming needs with Kodi (XBMC), I realized that was exactly why I bought the Google Nexus Player on the first place, beside having an alternate set-top box instead of my lovely Playstation 3 and except for improvement on hardware level for Android TV (reboot capacity WILL BE so WELCOMED!) I don't see how rooting the device can be compared as rooting a Smartphone.
Also some needs that we find regularly on Android Smartphone can be requested to Google either by AOSP or direct feedback (I realize that Google might just ignore anyways) and I am pretty sure that future Android 5.0.x or 5.x version will be synonymous of improvements.
No, this is not ignorance and definitely not naive-ness, perhaps I need another point of view to better understand or see more benefits for rooting the device.
Again, please I created this thread as a informative and debatable spot for this topic, do not flame me and not flame each other if you don't agree with an specific opinion.
TheGeeZus said:
I always try on not to be a party p**per but also would like to make this debate as civilized as possible so no need to bash me if you found my doubts in a negative way.
But after spending all this time with the Nexus Player of Google, I found myself with the conclusion, why is worthy my time for any root for the device.
At least I have a goal on showing my step-dad that paying DirecTV (Nothing against DirecTV BTW, just want to save money) is not 24/7 cost-effective versus Google Play Service and popular streaming services.
Heck, I didn't even felt left out in terms that versus Apple TV, the Nexus Player is still short without service like WWE, Amazon, NFL, etc. I was happy with the service available as of the writing of this.
To tell you the truth, the exact moment when I read all the possibility for free TV and streaming needs with Kodi (XBMC), I realized that was exactly why I bought the Google Nexus Player on the first place, beside having an alternate set-top box instead of my lovely Playstation 3 and except for improvement on hardware level for Android TV (reboot capacity WILL BE so WELCOMED!) I don't see how rooting the device can be compared as rooting a Smartphone.
Also some needs that we find regularly on Android Smartphone can be requested to Google either by AOSP or direct feedback (I realize that Google might just ignore anyways) and I am pretty sure that future Android 5.0.x or 5.x version will be synonymous of improvements.
No, this is not ignorance and definitely not naive-ness, perhaps I need another point of view to better understand or see more benefits for rooting the device.
Again, please I created this thread as a informative and debatable spot for this topic, do not flame me and not flame each other if you don't agree with an specific opinion.
Click to expand...
Click to collapse
I dunno, i rooted mine because i really needed to have expandable storage. So i rooted for chainfires stickmount. So i could have all my movies on my external hard drive run through xbmc natively.
↑This!↑
I have not rooted mine but if i do it will be for the ex-storage as well.. i am at the point of not storing a lot of movies because they are almost all online for a fee or free if you go that way.. We watch a movie once or twice and that is the end of it.. So to add to your debate i don't at this point see why you would root this device.
Would like a reboot function..
Im sure someone will come up with some nice ways to use root.. give them a week or so lol..
The main current use for rooting in my home is support for PS3 & 4 controllers wirelessly, using stick mount & folder mount to store game data and kodi data on an external drive and the ability to modify xml to re-arrange the order of programs in the NP's leanback interface (kodi gets top billing). My daughters now have immediate access to over twenty very large installed games so far thanks to folder mount. I also store all my kodi fanart, cover art, cd art, etc on the external as it takes up so much space internally for my large media collection that kodi accesses from my nas.
There will be future uses for root as well, of course (there always is), but these were my immediate needs.
Elrondolio said:
The main current use for rooting in my home is support for PS3 & 4 controllers wirelessly, using stick mount & folder mount to store game data and kodi data on an external drive and the ability to modify xml to re-arrange the order of programs in the NP's leanback interface (kodi gets top billing).
Click to expand...
Click to collapse
I recently rooted my NP, and I'm completely new to android and rooting. My main desire is to be able to get all of my sideloaded apps into the leanback interface, and to be able to rearrange the order and hide app icons I don't use. I've noticed by default Kodi RC2 appears in the leanback interface.
Do you have any tips for modifying the leanback interface in the way I've described?
kaess said:
I recently rooted my NP, and I'm completely new to android and rooting. My main desire is to be able to get all of my sideloaded apps into the leanback interface, and to be able to rearrange the order and hide app icons I don't use. I've noticed by default Kodi RC2 appears in the leanback interface.
Do you have any tips for modifying the leanback interface in the way I've described?
Click to expand...
Click to collapse
Since things are so new with the leanback launcher there hasn't been much time for any semi-automated tools/apps to be coded to accomplish what you want. Manually, however, is very doable depending on your desired time investment.
You can modify select sideloaded apps to make them show up on the leanback interface by uncompressing its apk, editing its manifest then re-compressing and re-sideloading. See this post: How to sideload XBMC/Kodi on Nexus Player. See also this helpful post from @zlexy : [Q] Launching Netflix From Within Kodi.
You can re-arrange the order of apps listed in the leanback interface by editing leanback launcher's database. See this post by @ariful : [Q] Rearranging Apps on Android TV Nexus Player.
Again, these methods are a bit labour intensive... it'll have to be that way until more devs start/finish coding for this brand new interface/device and/or for Google to release more customizable updates. Good luck.
Elrondolio said:
Since things are so new with the leanback launcher there hasn't been much time for any semi-automated tools/apps to be coded to accomplish what you want. Manually, however, is very doable depending on your desired time investment.
You can modify select sideloaded apps to make them show up on the leanback interface by uncompressing its apk, editing its manifest then re-compressing and re-sideloading. See this post: How to sideload XBMC/Kodi on Nexus Player. See also this helpful post from @zlexy : [Q] Launching Netflix From Within Kodi.
You can re-arrange the order of apps listed in the leanback interface by editing leanback launcher's database. See this post by @ariful : [Q] Rearranging Apps on Android TV Nexus Player.
Again, these methods are a bit labour intensive... it'll have to be that way until more devs start/finish coding for this brand new interface/device and/or for Google to release more customizable updates. Good luck.
Click to expand...
Click to collapse
The last thing you said is exactly why I am resisting the temptation.
I am being fair with the fact that this is the first face of Android Tv and there is yet more to see and I am faithful that most feature that needs root for now, Google might have something on their sleeves, but they are waiting to see how many Nexus Player gets sold, specially after the holidays.
My mom and my step-dad were impressed with the Nexus Player so great, that my step-dad sold me the Google Chromecast as he wanted to have an experience on his own and he really didn't find the Cast environment hard but he liked the more controlled environment of the Nexus Player, so we are buying a second one for me and I will let him take the first one after the second arrives.
I think that is another example that rooting (again, my exception is that a proven restart method gets developed) for now is not needed in base of a normal usage and still haven't got the problem of storage (yet, I know the day will come).
or even better in designated folders.. as far as I understand, this can be done after rooting right? but I'd rather not go down that route (at least atm) as I haven't a clue what I'm doing & the methods I've seen for the Shield TV are a little complicated for me (is there an automated method?)
Advice would be appreciated.
If you want to use the LeanBack (default) launcher you have to download SideLoad Launcher from the play store, otherwise you can flash Zulu99's ROM that gives you the default Android experience.
Agreed. I want to root my Android TV, but every thread I read is a little different, and since I don't have much experience doing it, I don't even know where to start. I'd rather wait until I've understood the process better before taking a chance at bricking my console.
Root is dead simple on this device. It's literally not requiring exploits and roots like a nexus device. You unlock the bootloader with very easy instructions, and can even leave the stock recovery if you are worried about things like that. I'm also pretty sure, though don't quote me, that unless you do something massively strange and unlikely, like changing partition sizes, that going back to stock, and relocking is always possible. At least it is on almost every single factory unlockable device on the market. No risk, I recommend it. That being said, you don't need root to sideload as stated abbove. Just get the launcher they recommended by chainfire, nistall it, then grab something like es file explorer, both in the play store, then install apk files from es file explorer, and launch from teh other launcher. The stock launcher launches the other one as the stock launcher can only display android TV supported apps, but the other launcher can display any android app, hence having a launcher inside a launcher.
Hope this helps.
I'd like to flash Steele01's Cyanogenmod 12.1 and use the twrp multi-rom, but from what I've seen, he's still working out a lot of kinks with the console since it's different from the Shield tablet.
If it wasn't for ES Explorer, I'd really be limited. At least I've been able to install Amazon Prime Instant Video and some other apps using their apk files. As far as the launcher inside of a launcher, are you referring to the crappy Sideload Launcher that's available through Leanback Launcher's play store? I saw the full Android mod for the Android TV, and it looks awesome. It looks exactly like you would expect any Android product to look. This whole Leanback Launcher is very disappointing. I feel like someone enabled Kid's mode on their tablet or something. I guess I'm thinking too much into this, and I should just go ahead and do it. Like you said, I could always go back to stock recovery, which from what I understand will need to be done anyway to receive any further updates.
Rolldog said:
I'd like to flash Steele01's Cyanogenmod 12.1 and use the twrp multi-rom, but from what I've seen, he's still working out a lot of kinks with the console since it's different from the Shield tablet.
If it wasn't for ES Explorer, I'd really be limited. At least I've been able to install Amazon Prime Instant Video and some other apps using their apk files. As far as the launcher inside of a launcher, are you referring to the crappy Sideload Launcher that's available through Leanback Launcher's play store? I saw the full Android mod for the Android TV, and it looks awesome. It looks exactly like you would expect any Android product to look. This whole Leanback Launcher is very disappointing. I feel like someone enabled Kid's mode on their tablet or something. I guess I'm thinking too much into this, and I should just go ahead and do it. Like you said, I could always go back to stock recovery, which from what I understand will need to be done anyway to receive any further updates.
Click to expand...
Click to collapse
I recommend trying it out with a cestom rom, as long as you are willing to unlock. I have since gone back to stock after trying both as I needed/wanted 2 features. The streaming button (there is a paid alternative) and the headphones on the controller. Keep in mind you also give up wireless controller, hence the headphones, by going to other roms. I use a monitor, and without a USB DAC I don't have sound if I give up wireless. I have simply settled for running 2 sidebar launchers, and it's working great for me. Also, Market Helper is good as it'll tell the play store (web version) that you are using a Nexus 7, ect, and can install most apps that way easily without having to sidelead everything. It'll also handle auto-updates ironicly ,ith stock play store app. Hopefully that'll help you decide. Please let us know what you did and why as we as a community like to know users needs. If you get stuck at any part of the process, please PM me or ask on the forums. We'd be glad to help with anything!
I don't have any problems with unlocking it, I, like you, just want to be sure I don't lose any features of the Shield. Losing game streaming and the wireless controller sound like a deal breaker. I'm sure it's just a matter of time before someone fixes these issues in a custom ROM. The wireless controller is configured using WiFi Direct. Even on Nvidia's website, they're all for people rooting their device and customizing it the way people want. One guy, who works for Nvidia was saying that they're definitely not against people rooting it because once someone buys it, they're willing to do whatever they want with it. So hopefully, we'll see Nvidia release more info to help people develop custom ROMs without losing any of the functionality of the device. Aren't there custom ROMs you can flash onto the Shield Tablet and still be able to use the wireless controller?
Is Market Helper an apk to install on the console? And what sidebar launchers are you using? There are times when I try using Shield Hub to connect to my local PC and it not work, and then I try with Moonlight, and it works everytime. I also like using the remote desktop feature. If you add the remote desktop app manually into the GeForce Experience software on your PC, then using the Shield, you can connect to your desktop using either Moonlight or Shield Hub and your TV mirrors your monitor.
kdb424 said:
Root is dead simple on this device. It's literally not requiring exploits and roots like a nexus device. You unlock the bootloader with very easy instructions, and can even leave the stock recovery if you are worried about things like that. I'm also pretty sure, though don't quote me, that unless you do something massively strange and unlikely, like changing partition sizes, that going back to stock, and relocking is always possible. At least it is on almost every single factory unlockable device on the market. No risk, I recommend it. That being said, you don't need root to sideload as stated abbove. Just get the launcher they recommended by chainfire, nistall it, then grab something like es file explorer, both in the play store, then install apk files from es file explorer, and launch from teh other launcher. The stock launcher launches the other one as the stock launcher can only display android TV supported apps, but the other launcher can display any android app, hence having a launcher inside a launcher.
Hope this helps.
Click to expand...
Click to collapse
Not to forget Es file explores send by land feature which is great for sending apks from other devices to your shield
With my AFTV2 currently broken down about one day after I set it up - I mentally went through some of the steps I'm likely to repeat very soon and - also seeing that some people in here still are struggling with some aspects of it, that I already learned long ago how to cope with - I thought I share some of my reflections.
This is by the way not meant to be a usability review - or tips guide of Amazons own interface - which I find abysmal for the most part. Let them struggle on their own - and also, for some reason there already are in depth "reviews" of it on aftvnews (which I came to slowly accept and even somewhat like.. ) - which mostly highlight aspects of it deemed positive. Bravo and lull Amazon into false confidence I say...
So here we go.
1. Best launcher (rooted or not) still is Firestarter. Basically because of its deep integration to app settings - which allows you to stop apps, delete their data or uninstall them in the fastest way possible. You'll need it more often than you think and its great that its there.
Change icon PPI to 144 and for your own sake - change the background to something more uplifting and also enable the text background bubbles so you get a higher text contrast, regardless of the BG image you chose.
2. Fire OS v5 and its limitation to one adb connection only isnt the enormous setback I thought it would be. Firestarter literally changes its default automatically within the first 3 seconds of it not being able to access adb - and the one click>double click combo to launch it from anywhere is good enough. Also in OS 5 there are no screen transitions, so switching to Firestarter feels more "instant".
Not having Firestarter use adb frees up you using adb from different devices. Once you are connected via adb from a PC f.e. you can also open different shells, or transfer a file and simultaneously perform another action in the shell - so thats a non issue. Also I rewrote all the scripts I use to cleanly exit adb with adb disconnect - and ultimately that works fine.
Through the two days of setting the Fire TV up and testing use cases I got a "cant connect via adb" error (because there already was another process using it) only twice - which in return can be promptly fixed by toggling adb on and off - and again - Firestarter provides a shortcut to that menu as well - so its fast, and if you use adb disconnect as intended, you dont need it very often.
3. Drop adbFire or equivalent "Helper Tools" as fast as possible - because they prevent you from learning even the simplest command line instruction, that will speed up your life in the long term. Seriously - just do it.
Also, explore the file structure of Kodi and the Fire TV (as in "look at it", try to make sense of it - not as in "I wander what happens if I delete this..."), so you can actually learn how they work. This again brings me back to the do not use adbFire or other "prepackaged" (and poorly laid out and documented) tools.
4. If you transfer single files - and most of them you usually want to drop to /sdcard/ first, you use the adb push command, because it simply turns out to be the fastest way to move stuff - at least if your OS allows you to drop a file onto the command line window to autopopulate the filepath.
If you want to transfer files and folders not directly located in /sdcard/ - either use something more GUI orientated - like AAFM ( https://github.com/sole/aafm ) (Windows cant use it to its fullest extent in its current state (on Windows you can use Total Commander (Windows Version - this time it will cost you something ) - which also has an adb plugin available) and or - zip the folder you want to transfer locally, then push it to /sdcard/ and then use Total Commander to unzip it into its desired location on the Fire TV.
Transferring .zip files wirelessly ultimately almost always turns out to be faster than transferring the individual files themselves. That also goes for zipping files on the AFTV using Total Commander, and then backing them up to a PC.
5. Use Total Commander. No seriously, download it from the Amazon App Store today. I know how popular ES File Explorer became from being the only free filemanager left, that was popular back in the day - but its approach to be iconographic to a fault and hiding away features in sub menus hurts its usability on any device where you try to perform actions with a remote. TC is simply better suited for the usecase.
TC also can write to the sdcard1 partition in Android 5 - either using root, or using a scripted workaround - so you generally dont have the "its not writable" issue. Also adb shell with su can write to it as well - so also use that if you need to.
You can also install Total Commanders LAN plugin ( http://www.ghisler.com/androidplugins/ ) and thereby access network shares.
6. There even is a usecase for the Amazon Voice button - because from Kodi - you can use it to launch Total Commander with just three button presses (say: "Total Commander") - which is faster than it was before - and you can also exit back to Kodi with only a few presses of the back button. Other than for this, the voice button of course is entirely useless - as we generally arent especially interested in how bad the Amazon Store is stocked (at least over here in europe... ).
7. Dont use the RC3 of Kodi 16 (Jarvis) right now. With Kodi 14.2 and 15.2 you can pause a video, drop back to Amazons launcher, then into Firestarter - then launch another app, then leave it and return to Kodi - with the video (usually - if you have enough free memory) still being in the paused state. In RC3 for Kodi 16, the video auto stops as soon as you switch away from Kodi - which in the long run causes much frustration and the need for additional button presses. Just remember to manually stop a video if you dont plan on returning to it anytime soon so Kodis bookmark your current position feature triggers.
8. If you want to install a Kodi repo - its much faster to download it as a .zip file and then adb push it to /sdcard/ where Kodi can find and install it - than to "start typing" anything in Kodi itself.
At some point - create a shell script for your pc that allows adb to connect to your Fire TVs IP address by just typing adb.sh (for example) - so you dont have to type in your Fire TVs ip address each time you want to connect to it.
9. If you dont already have a NAS -get an old router with an USB port that runs dd-wrt and has NTFS support (= all newer firmwares with at least 16mb package size should have it integrated - if you use ddwrt, even some with a 8mb package size). You get a very low power NAS that also can mirror as an FTP server (faster file transfers), and can become a torrent box in case you use that stuff. The negative only is - that with 4.5-6MB/s transferspeeds tops (WLAN, but actually limited by the individual routers CPU - they are low powered, remember) compressed 1080p is the most you can wish for - out of a 10-30 USD device. Preferably run it as a stand alone and not as your main router (reboots can be performed without bringing down your whole network, processor load, ...).
edit:
10. Kodi runs a little faster on the AFTV2 than on the Fire TV Sticks - which turns out to cut out just the right amounts of seconds on Kodi plugins with an "lets aggregate everything" approach.
You failed to mention what is "broken down" lol
You did quite abit of modding there so what "broke" it.
Playing a GPU intensive 3D game and then watching a video.
No, really.
The part you describe as "modding" went perfectly well - and what I describe above is mostly normal Android use for anyone not depending on "prefab click button to do thingy" stuff. Thats actually what I want this community to explore more - because at some point it literally becomes pointless - watching another in depth video analysis of Amazon taking out a row of items from their spreadsheet inspired Smart TV interface..
Amazon should have done more chip testing before they let their devices out of their factories. Or they should have done more testing regarding the 5.0.5 update. Slowly rolling out firmware updates in case you missed something important - is no substitute for proper testing...
All banter aside - the rooting process doesnt modify the kernel of the device, and on mine the GPU seems to have run into problems. From "working perfectly fine" to "full brick" (slightly different colors of black screens flashing, then settling on a full black screen) after playing a game and then watching a video.
AFTV - quality you can trust in.
Also - somehow its curious - when you buy a laptop these days - where you have root rights from the start, most complaining centers around stuff the manufacturer has messed up in producing the device and the software. But if you - as a manufacturer - take away the actual rights (permissions) from people - the discussion suddenly shifts to "OMG what have you done to the device".
But people usually dont get suddenly less educated or less cautious, once you take certain rights away from them - so the only explanation I have come up with is, that actually taking away permissions and property rights from people for some reason surfaces more voices that now very publicly campaign for this being a much more desirable state in the first place.
On a related note - If I had bricked my device during the rooting process, or while the TWRP custom recovery was installed - or by modifying system files (which now that TWRP runs on the Fire TV is easier to fix then ever), my first action would have been to give a full report of what happened (which I have actually done in a separate thread, in this case as well), so potential flaws or stumbling blocks in the rooting method could have been sussed out.
Mine has had 0 issues.. then again i rooted mine and have twrp, xposed, adaway, v4a, play store, firestarter, busybox, kodi, plex leanback youtube, debloated (removed most Amazecrap) etc.
Does more than I expected and then some.. even better than Nexus Player imo
Good - then we only agree that it isnt the rooting process.
And with TWRP you now have the means to entirely wipe and factory reset the device - so even if you for some reason had messed up the entire system partition (system files) - you still have a fallback, in fact a much better one than on a stock Fire TV, to "start over".
But that sadly doesnt fix hardware issues. Believe me, I tried. And documented it along the way. Look for it in another thread.
edit: Also this isnt me taking a jab at the device itself. I dont agree with Amazons product policies (= politics), but I was perfectly happy with my AFTV 2 as well. For as long as it worked..
In fact my fall back was to go back to the Fire TV Stick I had still laying around and I had the same functionality back (including all this "modding" you see in the OP ) within around 15 seconds (I missed the power socket in the wall twice... ).
harlekinrains said:
Good - then we only agree that it isnt the rooting process.
And with TWRP you now have the means to entirely wipe and factory reset the device - so even if you for some reason had messed up the entire system partition (system files) - you still have a fallback, in fact a much better one than on a stock Fire TV, to "start over".
But that sadly doesnt fix hardware issues. Believe me, I tried. And documented it along the way. Look for it in another thread.
Click to expand...
Click to collapse
Yea.. no device is perfect lol.. but the fact it has a gpu processor (when it works) is great! probably one of the cheaper 4k capable boxes available..
For the price, its a great option with root/recovery for what it does do and to achieve what its capable of.. theres bound to be a few bad devices and surely pushed to the max it can die
Sure.
Love the device. Dont love Amazons policies and product politics. Will use any chance to heckle them, that comes my way.
Thats me in a nutshell.
If you like the product, but dont like the company, their Store UI, their Store, the way they managed their store (app removals) in the past, the content thats in their store, their "underground" store program (that puts price pressure on devs)... thats not only possible - but also valid.
I dont think of Amazon as "a package deal".
When I criticize certain aspects of their infrastructure, I dont say that others are bad.
And I also dont proclaim that there is a high failure rate with Fire TV 2s on the 5.0.5 firmware. For me its just a nuisance and another chance to throw some banter..
But look - there is also something good, that came from it - I wrote an entire post about usability and how to best interact with the Fire TV on 5.0.5.
Because people just demanding updates (and root) - isnt enough..
yea.. i can write a banter on any device lol..
chromecast is great but cant say i like it..
the stick is worse..
nexus player is decent but also limited and if you install a full rom its essentially no longer a nexus player etc.
Deleted
Just one little additional tidbit -
Amazon still prevents the Fire TV 2 from using SD Cards formated with exFat. They literally write it out of their firmwares. Their Fire tablets of course support it - because, well its fun to play with your customer, and prevent usecases you see unfit for your current business model.
If you by any chance have purchased a 64GB Micro SD - Windows doesnt allow you to format it in Fat 32 - but this can be circumvented, by following this tutorial:
https://www.raspberrypi.org/documentation/installation/sdxc_formatting.md
Of course the 4GB filesize limit still holds up.
edit: Also tested Kodi 15.2 by now - which shows the same pause state/app switching behavior as 14.2. I've edited the OP to reflect that.
harlekinrains said:
Just one little additional tidbit -
Amazon still prevents the Fire TV 2 from using SD Cards formated with exFat. They literally write it out of their firmwares. Their Fire tablets of course support it - because, well its fun to play with your customer, and prevent usecases you see unfit for your current business model.
If you by any chance have purchased a 64GB Micro SD - Windows doesnt allow you to format it in Fat 32 - but this can be circumvented, by following this tutorial:
https://www.raspberrypi.org/documentation/installation/sdxc_formatting.md
Of course the 4GB filesize limit still holds up.
edit: Also tested Kodi 15.2 by now - which shows the same pause state/app switching behavior as 14.2. I've edited the OP to reflect that.
Click to expand...
Click to collapse
kodi installs repos fine for me on 15.2.. of course i dont use the remote I use the fire tv app and then the keyboard so it doesnt take forever
It does on all versions.
Installing repos by downloading their .zip files first, then pushing them to /sdcard/ using -
adb push /path/to/zipfile.zip /sdcard/
is just faster - because you dont have to type something you see on one screen, letter by letter - into an app on another screen. You download the file, you open a command line window, type adb push , then drag/drop the downloaded file onto the command line window to get its filepath into it - then finish typing /sdcard/ and press enter. In Kodi you then just use the "install from zip file" option.
You dont switch devices, you dont switch keyboards, you dont have to look at two screens, you dont have to copy a url. But using a BT keyboard probably in the end isnt that much slower...
Its just good practice to not see the Fire TV (stick) as a device that has to be managed on its own. It is a always on, connected Android device. You can look at its contents, you can move files from and to it, you can give it instructions...
adb and adb shell
make it open enough.
Two more usability tips.
1. If you are rooted, sideload WiFi ADB ( https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb ) - its just a quicker way of disabling and reenabling ADB - when you cant connect (since 5.0.5 the Fire TV only allows one ADB connection at a time) from your PC.
I also tried to replace adbd (the adb daemon file on the FIre TV) - but so far have only found one from API level 21 (and Fire TV 5.0.5 needs 22 (as it is based on Android 5.1)) - that one didnt work at all. Even if replacing it with the exact API 22 version would work, this doesnt necessarily mean that the "one adb connection limit" is gone - but it is something I though would be worth giving a try.
2. If you have WiFi connection issues on a Fire TV 2 - especially with the Fire TV repeatedly failing to connect, It turns out that Amazons Wifi Implementation REALLY, REALLY wants you to have WMM enabled on your router. If you don't the connection tends to drop every day and the Fire TV then has problems to reconnect. With WMM enabled I now run three days without the slightest issue - and I also have changed WiFi networks within seconds, and not as previously - it taking about 10 minutes until thats successful. Before I came by this little quirk of the FIre TV , switching bands - even temporarily on 2.4 GHz would kickstart the Fire TV reconnecting to the same AP, just fyi.
Also when you are on the 5 GHz band, the Fire TV has a "drop off" if you are on any band higher than the first few (five or six), the Fire TV has problems even "seeing" the network. Also the last channel it still "sees" it has problems connecting to - so drop even one below that if you want it running on 5 GHz.
This quirk is more widely reported than the first one, but just as annoying.
Also just a big "really?!" into Amazons direction for messing up the Wifi implementation on the device this badly. I'm sure MediaTeks proprietary drivers play a part in this, as might the Fire TV 2 always running its own ad hoc WiFi network in the background - but still Amazon is selling that stuff.
I could test it with two different routers - on largely uncongested bands in both the 2.4 and 5 GHz space - and I have half a dozen other devices that never displayed any problems with the way I had my network set up in the past - but for the Fire TV 2 I had to reconfigure my routers just so it would stop dropping out - or start finding the respective network in the first place.
Has anyone been able to successfully install and use either GameSome or Hyperspin on the Nvidia Shield TV on Marshmalloe? I followed directions for Gamesome to the T, using the new beta version but every time I load the app it says merging data, and my storage/0/gamesome folder disappears every single time. I don't think I'm doing something right and I messed with it for hourd last night. I'm not gonna put anymore time into it, until I verify that either one can be run on the new MM update. These frontends are awesome, if I could get them to work. Has anyone had better luck than I?
Sent from my Sammy S6 using Revolution 1.0
Same happens here, soon as app loss it migrates that folder to some place. Not sure if it's a beta issue or what. I can't get it to run on marshmallow.
I've had no success with Gamesome, even switching to the 2.0 beta he is working on. I do know the dev has bought a SHIELD TV so in time things will improve we hope. I've heard people are using "Arc Browser" instead which is similar to Gamesome.
I do have an extensive Hyperspin setup (68 systems iirc) on my HTPC. I'm playing with the android version for my SHIELD TV, with a 500GB USB HDD connected as adopted storage. I have several of what I call the classic consoles (Nes,Snes,MD,32X etc.) working. They have artwork, videos playing and they launch the game almost instantly with Retroarch.
My advice would be to ensure you can play the games on the emulator first then worry about Hyperspin. The .ini files I downloaded from the guide on their website DID need editing. The ROM path proved to be the biggest hic-cup, it was very fussy over how it was set. I'll provide a few lines from my snes setup as an example to help you out. Obviously you'll need to adapt it for different systems...
rompath=/storage/emulated/0/Hyperspin/Emulators/Super Nintendo Entertainment System/roms/
userompath=true
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
romextension=sfc,zip
parameters=cores/bsnes_mercury_performance_libretro_android.so
honosuseri said:
I've had no success with Gamesome, even switching to the 2.0 beta he is working on. I do know the dev has bought a SHIELD TV so in time things will improve we hope. I've heard people are using "Arc Browser" instead which is similar to Gamesome.
I do have an extensive Hyperspin setup (68 systems iirc) on my HTPC. I'm playing with the android version for my SHIELD TV, with a 500GB USB HDD connected as adopted storage. I have several of what I call the classic consoles (Nes,Snes,MD,32X etc.) working. They have artwork, videos playing and they launch the game almost instantly with Retroarch.
My advice would be to ensure you can play the games on the emulator first then worry about Hyperspin. The .ini files I downloaded from the guide on their website DID need editing. The ROM path proved to be the biggest hic-cup, it was very fussy over how it was set. I'll provide a few lines from my snes setup as an example to help you out. Obviously you'll need to adapt it for different systems...
rompath=/storage/emulated/0/Hyperspin/Emulators/Super Nintendo Entertainment System/roms/
userompath=true
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
romextension=sfc,zip
parameters=cores/bsnes_mercury_performance_libretro_android.so
Click to expand...
Click to collapse
Nice to see this. I'm have a very extensive hyperspin/rlauncher setup. Very helpful to those (like myself) looking to setup hs on Android. ?
Hi all,
first of all I am pretty much beginner level for Android rooting.
Actually what I want to do is play around a bit with the system files and see if I can find some way to turn off HDMI CEC. There is some post here where someone did this by modifying a file on the Amazon FireTV.
But for starters I am even failing to access the file system via my PC
I have rooted following the tutorials, I have installed ES File Explorer , I have granted root to ES Explorer when the SuperSU popup appeared (and it also shows as being granted in the SuperSU app).
Also I enabled Root Explorer in ES File Explorer.
Then when activating Remote Manager when /sdcard is set as FTP root directory I can access the file system (below /sdcard) via FTP from my PC and do see the files - so FTP access basically works and I am pretty sure there is no issue on the PC side.
However when I set / as FTP root directory and then connect from my PC via FTP (using Total Commander, FileZilla.... the client makes no difference) then I can't see anything at all, it lists an empty directory (or not even that as on an empty directory I'd have the ".." entry and I don't even have that.
Also when I try setting anything else except /sdcard as FTP root directory in Remote Manager in ES File Explorer it's the same thing.
It seems when accessing the file system via FTP I just don't have the necessary privileges to browse the root file system.
Within ES File Explorer itself on the other hand it's no problem to browse everything, there I do seem to have the necessary privileges.
Can anyone help me please, either this is an issue with rooting on the Shield or with ES File Explorer on the Shield or I am making some dummy mistake.
I have searched on Google for hours looking for a solution to this but I hardly even find people having this problem.
So now I am a bit puzzled.
How is one supposed to gain access to the root file system via the PC?
Also how do I get SSH access with root privileges?
tbh this all seems a bit strange to me, I am rooted, but it seems almost impossible to gain access to the root file system from the PC!?
I am also amazed because something like this can be achieved on any jailbroken iOS device by any beginner within 5 minutes without any issues, and I always thought for the much more open Android environment there would be 100s of entry paths and 1000s of tutorials but I seem to find hardly anything at all and after hours and hours of trying and research I still fail even accessing the damn root file system from my PC
FireAustria said:
Hi all,
first of all I am pretty much beginner level for Android rooting.
Actually what I want to do is play around a bit with the system files and see if I can find some way to turn off HDMI CEC. There is some post here where someone did this by modifying a file on the Amazon FireTV.
But for starters I am even failing to access the file system via my PC
I have rooted following the tutorials, I have installed ES File Explorer , I have granted root to ES Explorer when the SuperSU popup appeared (and it also shows as being granted in the SuperSU app).
Also I enabled Root Explorer in ES File Explorer.
Then when activating Remote Manager when /sdcard is set as FTP root directory I can access the file system (below /sdcard) via FTP from my PC and do see the files - so FTP access basically works and I am pretty sure there is no issue on the PC side.
However when I set / as FTP root directory and then connect from my PC via FTP (using Total Commander, FileZilla.... the client makes no difference) then I can't see anything at all, it lists an empty directory (or not even that as on an empty directory I'd have the ".." entry and I don't even have that.
Also when I try setting anything else except /sdcard as FTP root directory in Remote Manager in ES File Explorer it's the same thing.
It seems when accessing the file system via FTP I just don't have the necessary privileges to browse the root file system.
Within ES File Explorer itself on the other hand it's no problem to browse everything, there I do seem to have the necessary privileges.
Can anyone help me please, either this is an issue with rooting on the Shield or with ES File Explorer on the Shield or I am making some dummy mistake.
I have searched on Google for hours looking for a solution to this but I hardly even find people having this problem.
So now I am a bit puzzled.
How is one supposed to gain access to the root file system via the PC?
Also how do I get SSH access with root privileges?
tbh this all seems a bit strange to me, I am rooted, but it seems almost impossible to gain access to the root file system from the PC!?
I am also amazed because something like this can be achieved on any jailbroken iOS device by any beginner within 5 minutes without any issues, and I always thought for the much more open Android environment there would be 100s of entry paths and 1000s of tutorials but I seem to find hardly anything at all and after hours and hours of trying and research I still fail even accessing the damn root file system from my PC
Click to expand...
Click to collapse
Are you doing this to just turn off HDMI CEC? You can do that without root on stock in the settings>HDMI
I haven't rooted my Shield TV pro. I prefer it stock with the lean back launcher so I can't help accessing the root file system.
Sent from my Nexus 6P using Tapatalk
Acid0057 said:
Are you doing this to just turn off HDMI CEC? You can do that without root on stock in the settings>HDMI
I haven't rooted my Shield TV pro. I prefer it stock with the lean back launcher so I can't help accessing the root file system.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well basically yes I am doing this only for the HDMI CEC. It is kind of a big deal in actual usage of my Shield actually.
Apparently there is a bug in the Shield firmware related to HDMI CEC, that for me (and many others) results in this behavior when the Shield TV is connected to an AV receiver.
In my case the Shield is connected to an Onkyo TX-RZ3100 and then from there to a Samsung TV.
HDMI CEC is enabled on both because if it wasn't then the ARC audio return channel wouldn't work (but this is needed, otherwise I won't have audio when watching terrestrial TV which is being received by the Samsung TV).
Now what happens is that whenever I turn on the TV, then the AV receiver also switches on via HDMI CEC (in this case this is wanted and normal behavior).
However when the Shield is connected to the AV receiver (which it normally is), then the Shield will *also* turn itself on and switch the AV receiver to the input of the Shield.
So e.g. if I want to turn on the TV to play with the PS4, then I end up with the Onkyo turning on, showing me the PS4 screen as the AV receiver is switched to the input of the PS4. But then 20s later suddenly the Shield turns itself on and switches the Onkyo to its input.
So the end result is this: whenever I turn on the TV to do anything else (PS4, satellite receiver, HTPC, cable box....) then 20s later the Shield will switch to its input and force me to manually switch back to what what I actually intended to watch.
It looks like the issue was introduced with the 5.x firmware as it didn't happen before.
Now you say I should switch off HDMI CEC via settings - however there are no settings to switch it off unfortunately.
There is no Settings/HDMI (in 5.x) .
What's there is Settings / Display & Sound / Power Control, and there you can switch "CEC TV on" and "CEC TV off", however this only controls whether the Shield will turn on (or off) the TV when switching it on/off - and I have these settings set to disabled. But this doesn't help.
Unless I am missing some other settings there seems to be no way to completely switch off HDMI CEC via the UI.
Ah so turning off CEC TV in the normal settings doesn't solve it. Yes that's the options I did mean. In Display and Sound. Sorry I can't be more help. Maybe try the app Settings Editor in the play store on the shield. It might have the settings to completely disable CEC
Sent from my Nexus 6P using Tapatalk