I have an issue, I got a tv stick, tried 3 different apps, I can connect fine but nothing sideloads, adbfire just sits with a progress bar, and once it gets to the end it starts again FTV utility connects fine again but also does nothing when I try to side load, Any ideas?
Sometimes having a space in a folder name or file name in the path of the file you want to sideload causes problems
Embedded spaces aren't an issue with adbFire, spaces are accounted for with sideloads. If the activity bar is endlessly cycling you have an adb issue. Check the log and see if you can spot the error or use adbFire's console mode and try adb install filename.apk and see what errors are produced.
Related
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
http://www.xbmchub.com/forums/showthread.php?t=21380
Sent from my Nexus 7²
Vidikron said:
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
screwyluie said:
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
Click to expand...
Click to collapse
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Vidikron said:
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Click to expand...
Click to collapse
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
DeVSS said:
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
Click to expand...
Click to collapse
Interesting.. It just says "waiting for device" when I try.
Vidikron said:
Interesting.. It just says "waiting for device" when I try.
Click to expand...
Click to collapse
Just double checking, but you did turn adb on on your fire tv right?
DeVSS said:
Just double checking, but you did turn adb on on your fire tv right?
Click to expand...
Click to collapse
Yes. I've been installing APKs via the command prompt on my PC and that works fine. But when doing that I have to use the connect command to connect to a specific IP. I guess I'm unclear on how adb is actually supposed to find my device without telling it where to look.
[edit] Well, I've sort of gotten around the issue. I just made a second shell command to connect. So now I right-click connect and then right-click install. Not as pretty as a single command, but much faster than what I was doing before. But if anyone knows how to merge the two into a single command please let me know.
So I went through the process of rooting, installing xbmc, installing llama only to find out that I am unable to play any videos in XBMC or install any add ons. I installed the official Gotham 13.0 release from the XBMC Firetv wiki. When I try to select a video, it makes the noise you get when selecting but nothing happens. When I try to install an add-on, it starts downloading at 0% and then stops downloading immediately. I was trying to look for a log file in /sdcard/Android/data/org.xbmc.xbmc/files/ but it's empty. I don't see any settings/files in there.
I performed a factory reset and this time only installed XBMC but am still getting the same behavior. Could this be a permissions problem? It also doesn't generate thumbnails for everything, only some. Any suggestions?
Edit: It appears to be able to play local files just fine but when trying to access a samba share it fails. The log file appears like this:
NFO: FileSmb->Open: Unable to open file : 'smb://192.168.1.3/MediaUSB3/tv/Archer%20(2009)/Season%2004/Archer.2009.S04E07.sample.mkv'
unix_err:'26' error : 'Function not implemented'
Edit 2: The plugin links truly were broken which was that issue and there was a problem with accessing my samba share. I switched it to using Apple's network sharing and it's fine.
A couple hours ago, the AFTV wouldn't play any Prime video and would just hang on the Netflix screen with the loading icon. Fairly certain it was on 51.1.1.0_user_511070220. Definitely 51.1.1.0. This was rooted with updates turned off using the adbFire app and a few Amazon URLs blocked in my router's access restrictions. After rebooting the AFTV a couple times, I read that a lot of solutions online were to delete the Prime/Netflix apps' data/cache. That didn't fix it. So then I followed the next common step and deauthorized the account. This is where the AFTV starting going crazy. After putting the user/pass back in, it started very quickly flashing between the "Authorizing Your Device" screen and the "Could not connect screen." A lot of button mashing broke the loop but every time I entered the user/pass, the loop would begin again. Hard and soft rebooting had no effect. Turning off the router (running AdvancedTomato) access restriction didn't help. I even used adbFire to very temporarily re-enable updates. Still no access.
I figured that this was a sign I should protect my root better. It may have been a mistake, but I decided to try and install Clockwork recovery. I left the "pm disable com.amazon.dcp" from adbFire enabled. So Amazon updates were still blocked. I downgraded to 51.1.0.2_user_510058520 kinda not realizing that this would kill my root and maybe also not realizing that Clockwork would need root to install.
I now have the same exact problem as before. I am stuck on the registration page and cannot sign in. It either says that the "sign in failed" or that the "connection was lost." At least on this earlier firmware, it doesn't seem to get stuck on the flashing loop between those two screens. There is some new weirdness where it seems to be pressing buttons on its own somehow. The text entry menu will disappear as if I closed it. And then when I select it again, it's in a broken format with all the keyboard buttons there, but the input field names missing.
I have verified that the current firmware is 51.1.0.2_user_510058520 with "grep fingerprint /system/build.prop".
I am 99% sure that nothing else from amazon is blocked besides "pm disable com.amazon.dcp", which I'm now unable to turn on again as I don't have root. adbFire says that "Amazon updates are off". I thought that this was reset by a downgrade? I can't think of anything else to check. I used to use dnsmasq to block three Amazon URLs before I found AdvancedTomato's Access Restriction but dnsmasq is empty and the rule in Access Restriction is deleted.
I am 99% sure I never edited my AFTV's hosts file. I just did "adb pull /system/etc/hosts" and all it has in it is "127.0.0.1 localhost".
Is there anything else I should check?
Just tried it again this morning. After every "sign in failed," if I let it sit on the failed screen with the keyboard where it wants me to enter user/pass again and touch nothing for 5-10 seconds, it will suddenly close that keyboard pop up and then immediately reopen it -- except it will be broken in that it's missing all the labels for fields like "Enter email here".
?
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
{ParanoiA} said:
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
Click to expand...
Click to collapse
I don't know where the router block could be. The rule in Access Restrictions is deleted and the Dnsmasq field is empty. I'm going to try using a cell phone hot spot to register it. Probably won't change anything but I can at least rule out the router as a problem.
So like the Google Play Store, if you install Happy Chick on the stock Ouya Rom it won't show up in the Apps or Software menu. Anyone know a work around, possibly be able to just rename it within the apk to get around it?
The same for me. Any solution?
Hi, don't know if anyone will read this, but here it is:
I suppose installing a custom ROM would also do the trick, but if you want to keep the Ouya ROM (keep in mind that this is not a pretty solution, and that it requires a PC running on the same network as the Ouya):
- Download the ADB tools and install them on your desktop PC
- Activate network ADB on the Ouya (development menu)
- On your PC, go to the ADB folder and type "adb shell am start -n com.xiaoji.emulator/.Entry"
If this does not work, try "adb connect <IP>" with the IP shown on your TV, and then the shell command.
You can create a .BAT file to launch it, which is a cheap hack but works.
Hello, today one of my rooted fire tv's became stuck on black screen and basically none of the important stuff can be accessed. This has happened to me a few times in the past and I am usually able to get the settings menu launched by playing around with the remote and the voice functions or if all else fails usually disconnecting my network will prompt the network connections menu which then will jog the main settings again and from there I can force quit and get it back up and running. But today I have gone through pretty much every method I know of and still no luck just a black screen. I run xposed on my fire tv so it is set to use spmc as the homescreen launcher. Any other methods out there that I have not tried? I wanted to avoid having to do a factory restore and reinstall everything if I can.
Nobody? LOl
danknasty said:
Hello, today one of my rooted fire tv's became stuck on black screen and basically none of the important stuff can be accessed. This has happened to me a few times in the past and I am usually able to get the settings menu launched by playing around with the remote and the voice functions or if all else fails usually disconnecting my network will prompt the network connections menu which then will jog the main settings again and from there I can force quit and get it back up and running. But today I have gone through pretty much every method I know of and still no luck just a black screen. I run xposed on my fire tv so it is set to use spmc as the homescreen launcher. Any other methods out there that I have not tried? I wanted to avoid having to do a factory restore and reinstall everything if I can.
Click to expand...
Click to collapse
If you just need to get into the settings menu, then connect to the Fire TV via ADB and run the following command to load up the settings menu:
Code:
adb shell am start -n com.amazon.tv.launcher/.ui.SettingsActivity
AFTVnews.com said:
If you just need to get into the settings menu, then connect to the Fire TV via ADB and run the following command to load up the settings menu:
Code:
adb shell am start -n com.amazon.tv.launcher/.ui.SettingsActivity
Click to expand...
Click to collapse
Is there anyway to access settings without abd. I know I can change resolution and restart from the remote is that all?
danknasty said:
Is there anyway to access settings without abd. I know I can change resolution and restart from the remote is that all?
Click to expand...
Click to collapse
The only other way is to hold the home button until the popup menu appears with the settings option. You have to be on one of the newer software version for that to work since it was recently added.