Hey
Is anybody of you able to use the MagineTV App on your Fire TV?
I was able to install the .apk with adbFire and lunching it also works without any problem.
But then its necessary to enter your email and password to enter MagineTV.
This is were I fail , because selecting the windows were the password/email has to be entered can't be done with the remote control.
Greets
mrmaks said:
Hey
Is anybody of you able to use the MagineTV App on your Fire TV?
I was able to install the .apk with adbFire and lunching it also works without any problem.
But then its necessary to enter your email and password to enter MagineTV.
This is were I fail , because selecting the windows were the password/email has to be entered can't be done with the remote control.
Greets
Click to expand...
Click to collapse
use a keyboard and mouse
Magine TV with Fire
mrmaks said:
Hey
Is anybody of you able to use the MagineTV App on your Fire TV?
I was able to install the .apk with adbFire and lunching it also works without any problem.
But then its necessary to enter your email and password to enter MagineTV.
This is were I fail , because selecting the windows were the password/email has to be entered can't be done with the remote control.
Greets
Click to expand...
Click to collapse
I haven't tried it yet, but I don't see why it wouldn't work? Although some apps are more Fire friendly than others, there's usually a way around everything However, the solution may not always be as easy or convenient as we'd prefer. And in this case, you may have to go the "old-fashioned" way by hooking up a keyboard in order to be able to enter the info that is required, or if you insist on remaining wireless you can now get a Smart Keyboard for a pretty fair price!
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
abacus0101 said:
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
Click to expand...
Click to collapse
Need to go into Settings (from Original AFTV launcher) and System, then Developers Option and turn on Install from Unknown Sources.
If you have an earlier version of AFTV, then you need to do the SQLite method, do a search for it.
abacus0101 said:
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53451988 ORIGINAL THREAD
I had this same problem today...I coudlen't get the ADB commands to work...But I found out it's done via SQLITE editing ...so I did another solution
*buy* (or find) SQLIte Editor...(or an app that can edit SQL database files) and sideload it.
Download LanMote Lite from the play store(you need mouse support) and Sideload it. Once done RUN LanMote Lite and start the server (Free version is limited to 30 minutes so act quickly) On your HTML 5 device (preferrably a smartphone or tablet) [PC works but mouse is slow and wonky] connect to the same wifi as the FTV (if you didnt do it already) and open your web browser and put in the address LANMOTE will show on the FTV (example http://xx.xx.xx:9999) also enable different cursor.
Go to FTV home and go to settings>>APPLICATIONS >> your SQLITE editing program.
(in SQLITE Editor) Allow SU permisions and use your amazon remote (it works for simple navigation for now) to go to FILES TAB and go to
DATA>>>DATA>>>com.android.providers.settings >>SETTINGS.DB
go to the GLOBAL folder. You should see a list with different settings (BE CAREFUL)
(now this is where you need a mouse)
on your HTML 5 device (smartphone) go the MOUSE Tab and use the mouse pad to mouse near the entry that says INSTALL_NON_MARKET_APPS you will notice that default for this option is 0 (which means off/ disabled) Mouse over the 0 and tap the "click" button on your HTML device. you will notice the entire row becomes gray.
Use your Amazon Remote and click EDIT RECORD. cursor down to the 0 and change it to a 1
use your remote and scroll below it should give a CANCEL and SAVE button. Click save with the remote.
go back to home and enjoy sideloading unknown sources.
stanleyopar2000 said:
http://forum.xda-developers.com/showthread.php?p=53451988 ORIGINAL THREAD
I had this same problem today...I coudlen't get the ADB commands to work...But I found out it's done via SQLITE editing ...so I did another solution
*buy* (or find) SQLIte Editor...(or an app that can edit SQL database files) and sideload it.
Download LanMote Lite from the play store(you need mouse support) and Sideload it. Once done RUN LanMote Lite and start the server (Free version is limited to 30 minutes so act quickly) On your HTML 5 device (preferrably a smartphone or tablet) [PC works but mouse is slow and wonky] connect to the same wifi as the FTV (if you didnt do it already) and open your web browser and put in the address LANMOTE will show on the FTV (example http://xx.xx.xx:9999) also enable different cursor.
Go to FTV home and go to settings>>APPLICATIONS >> your SQLITE editing program.
(in SQLITE Editor) Allow SU permisions and use your amazon remote (it works for simple navigation for now) to go to FILES TAB and go to
DATA>>>DATA>>>com.android.providers.settings >>SETTINGS.DB
go to the GLOBAL folder. You should see a list with different settings (BE CAREFUL)
(now this is where you need a mouse)
on your HTML 5 device (smartphone) go the MOUSE Tab and use the mouse pad to mouse near the entry that says INSTALL_NON_MARKET_APPS you will notice that default for this option is 0 (which means off/ disabled) Mouse over the 0 and tap the "click" button on your HTML device. you will notice the entire row becomes gray.
Use your Amazon Remote and click EDIT RECORD. cursor down to the 0 and change it to a 1
use your remote and scroll below it should give a CANCEL and SAVE button. Click save with the remote.
go back to home and enjoy sideloading unknown sources.
Click to expand...
Click to collapse
I'll try your method...phew, got tired just listening to all that has to be done...thanks
I am a new Fire TV owner and have downloaded the ES file manager app, then I installed Firestarter, then I installed Kodi and had Wookie running on that, then I tried to put Mobdro onto Kodi using kodisrael repo. It crashed. I powered off and left for a while powered back on and it loads up AFTV screen then Firestarter then Freezes remote not making a click sound doing nothing ? Help how do I fix ?
Did you do anything else? Root, hiding packages, etc.?
Try to connect an USB keyboard and navigate through the firestarter settings. There are several autostart settings in the app, also disable the ADB-mode.
Edit:
Can you still connect via ADB?
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
JedSpink said:
Hi all
Sorry if this is a repeat but hope not.
My AFTV updated to 5.0.5. Claims an installed date of 21 Jan 16, but only recently have I noticed a number of issues, so not sure why they took so long to show up, unless 21 Jan is actually the 5.0.5 build date, rather than install. So here's what I've found (on Fire TV and stick - got both).
1. First Llama stopped working - I used LLama events with Condition/Action setup to start Kodi whenever I started Ikono (and switched logos). Testing the condition appeared to work, i.e. Kodi fired up but the difference was that in the test BEFORE you used to see Ikono fire up for a few seconds then switch to Kodi. After the 5.0.5 the test just fired up Kodi. And then when you start Ikono in the normal way, Kodi does not fire. Same for all my other "shortcuts".
2. Wukong: would not work for a while, the mouse pointer showed up by clicks did not fire off any action on AFTV side. A few reboots and messing around solved it but even now a bit flakey, compared to solid before.
3. Side-loading: cannot side-load apps now! Can connect via ADB, but running "adb install xxxxxx.apk" results in a:
error: device not found
- waiting for device -
4. Apps that update themselves, e.g. ShowBox, are failing (probably for the same reason as 3)
So is this common? I'm assuming Amazon have put in a range of changes to lock-down the device? Are there any workarounds / fixes?
Jed
Click to expand...
Click to collapse
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
bula1ca said:
1) Lama does not work under OS5
2) Sometimes I have to reboot as well
3) go in settings/ Developer Options/and turn off and on ADB debugging a three times ....
Click to expand...
Click to collapse
Thanks for confirming 1), I tried AutomateIt too and it seems to have the same problem, so I suppose it's some sort of OS-level blocking of the kind of hooks that Llama and others used in the past? Guess they could argue it was a security improvement as allowing one app to start another could be abused...
Re: Wukong and side-loading being blocked.... I played a bit more and similar results to you.... I don't think the OS is deliberately blocking / preventing but there may be a bug or issue. For example if I do a reboot of the box then, say, Wukong, will work fine but then tried:
adb kill-server
adb start-server
adb connect xx.xx..x.xx
and then quick test with: adb shell
and get the error: device not ready.
Do a reboot, don't connect Wukong and try the above commands and adb shell works (quick test) and then any commands like adb push / install work too. But then Wukong seems blocked, e.g. may connect as mouse pointer but using the click function does nothing, or may not connect at all.
I'll try your fix of the ADB debug off/on instead of reboot; and see how that goes.
Fun times!
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
El_Nino9 said:
did you carry on using your device as is with the same data from the old version?i.e. no factory reset after the update?
i ask because things often break after an OTA.
i factory reset my fire stick after the update and then again after kingroot(do not push super su on it yet if you want root-wait for a pre-rooted image if you want super su).
so after re-logging in, i enabled adb, sent kodi to the device and i can launch it from Apps on the left hand side, no need to go into settings anymore or even use llama. it's there. it won't be in the recent apps, i don't know why, but at least it shows up in apps.
i don't use wukong, but i have set up my rooted phone to be a bluetooth mouse, just encase or even use my ps4 touchpad.
Click to expand...
Click to collapse
Lama is broken in OS5. Are you sure about it?
bula1ca said:
Lama is broken in OS5. Are you sure about it?
Click to expand...
Click to collapse
i never said llama works under OS5.
all i said it's not needed anymore due to kodi being available to launch from the apps menu on the left hand side.
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
My remote mouse for fire tv works fine on OS5 prerooted rom
Zenroid said:
Wukong seems working fine for me but the remote mouse for fire t.v. unable to click
Click to expand...
Click to collapse
Hi that's what I get sometimes, shows mouse pointer but click does not work. I find a reboot of the fire box fixes... what i've noticed it that once you have got say Wukong working then adb will not do adb - install or push: gets the device not ready error. Again a reboot will fix but then, say, Wukong won't work properly.
So it seems like something is blocking the other process - hence why I was wondering if a bug.
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
JedSpink said:
Take on the point about doing a factory reset from @El_Nino9 but then I'll have to reinstall and setup Kodi and my other side-loaded apps from scratch?
Jed
Click to expand...
Click to collapse
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
El_Nino9 said:
as with all factory resets, you have to redo the setup. there are tools available to back up your setups and its easy enough to adb install apps. plus you might be able to push all the latest versions of the apps back on the fire if you haven't done so already.
it depends what you want to achieve and what you want to eliminate. it all involves doing some sort of work, however i understand the more little work you have to do the better it is. no need.
Click to expand...
Click to collapse
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
JedSpink said:
You are right of course. Just being a bit lazy. It's mainly Kodi I worry about as I have a lots of add-ons and takes time to setup correctly. I know you can backup your Kodi configuration but never done a backup / restore of Kodi. Will take a look into it and if I can preserve my add-ons then will do factory reset and adb -install them again.
Click to expand...
Click to collapse
i rooted my device and would use titanium back up. however kodi within itself has various tools.
they have an addon called back up and they also have other features.
however, on the stick, you can use storage easily unless you know how to adb well.
for simple use i would recommend titanium back up and then back up to a cloud service such as gdrive.
each user has different preferences.
if you aren't rooted just use the addon back up too or there is a 3rd party app that also does similar stuff which i've never used so can't help.
if you do decide to root, do not use supersume app after kingroot. stick to king root su until a rooted system image is released for the device. i used kingroot 4.1 from xda thread and despite it saying failed i had root.
if you're not comfortable don't do it
You can use Tasker instead of llama
How can I get OpenVPN working with Kodi & Do I need to root my Amazon Fire TV Stick?
Hi,
Currently I've done a really weird hacky way of getting my VPN working...
1. Installed NordVPN via Apps2Fire
2. Installed KodiOnBoot via Apps2Fire
3. Setup NordVPN to Boot on Launch
4. Setup KodiOnBoot to Launch Kodi after 120 Seconds of Screen Timeout (Alternatively I can just press Home & Load Kodi manually)
NordVPN was a nussiance to get it to where I've managed to get it to so far because you can't scroll down in the settings correctly. Likewise the same problem with OpenVPN's application, I can't scroll down so I can't even get that app to boot...
However in Kodi there is an OpenVPN app you can download via https://brianhornsby.com/kodi_addons/openvpn however when trying to setup that it just tells me to Check the Log because it failed to connect to the .opvn file yet I can't find the log and I have a feeling its to do with root/su.
Any ideas what I should do to get around this?
Thanks