Related
I have got a 32b magic and number keys are not working on the keyboard, will getting "better terminal" fix it? I cant get numbers working on free terminal apps, eveything else is working properly on my phone.
It's running latest cyanogen
Try typing ?123 in terminal
The question mark is working, not the numbers, when i press the numbers on the keyboard it appearsa big number in a white box over it, but nothing in the terminal
Same problem
It would type for me, both letters and numbers, but when i tried to execute it by pressing enter, I could never get it to work for some reason.
So I just used ADB instead of terminal.
Well what I usually do is renaming the files I need to use in the terminal using roman numbers . But i would really like to find a real fix
Moved to Beta
Stepping Closer to Perfection
Ello,
Been messing with this for a bit now and think I have a decent set of instructions organized for getting a vnc server (with resumable sessions) of your webtop in a pinch for those times you say "where the hell is a hdmi/dock/etc when I need one" its a little repetitive but simple as hell hopefully someone who knows more can set up the x server config to include this set up as a just in case.
Pre-recs
Of course Root!!
Full Native Ubuntu Webtop (Sogarths webtop2sd here)
Terminal Emulator (I recommend this one)
And vnc viewer something like really shouldn't matter.
And you'll need to fix your dependencies using this regardless of which mod so you wont have to worry about not being able to use apt to install things.
Any form of a custom dock not stock version e.g. xfce-panel, debain panel or genome otherwise you'll have no dock at all (I am working on getting a way around this for DebainMOD/stock dock users)
More Pre-recs DO THIS BEFORE ANYTHING!! WHY? because I rather that than I told you so XP
BACK YOUR SH%^T UP I recommend using the more expanded CWM Due to its backing up sd-ext and osh
Fun stuff:
Open Terminal Emulator
and enter the following minus (anything in)
su
(get root for term)
/usr/bin/sudo - u adas bash
(get into the webtop enviornment, can be used alot XD)
sudo bash
(gotta love root)
({or just} /usr/bin/sudo -u root bash {for easy way to root shell})
apt-get install tightvncserver
apt-get install lxde
or just
apt-get install tightvncserver lxde
(install a vnc server and a desk environment)
tightvncserver
(run before the config worked best for me it'll ask you to set up a password then ask if you would like to set up a view only password which I liked with this I used getvncstate for that one jic I wanted to see if it was running up to you really)
(now config the vnc display, this way was the least fubar'ed x display I managed to get working and repeated)
export USER=adas
vncserver -geometry 1024X800
(if you ran this before the previous set thats fine after you might see a localhost:2(ect) don't worry if you did this before first use you'll be asked to enter a password. once set enter the next line by line)
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
(then hit ctrl-d twice then enter should get you out, that is pretty much where you select what you want to have started in your root environment in vnc if you don't want stock dock or the webtop panel remove them lxsession starts xfce if you used that you can also add gnome -session or panel which ever)
(now to fix known keyboard mapping issue for 9.04 from root terminal in webtop run)
apt-get install nano
nano /root/.vnc/xstartup
(add the line {export XKL_XMODMAP_DISABLE=1} before /etc/X11/Xsession or gnome-session or if you have another way of adding this that'll do)
(use gedit to do this on one of my atrix's webtops was sooo much easier XO)
(now hit the home key and open up your vnc viewer on your phone)
The drop down should be newconnection
Nickname: adas (or whatever I use root)
Password: (the password you set up if you dont remember then...try below steps for reconnect)
Address:localhost
port: 5901 (5902 worked too x.x idkw)
(the press the connect button XD Always exit your vnc connection before leaving it!!!!)
(This should not fubar your x display for hdmi/dock/etc but did notice that on the first run re plugging the hdmi loaded the moto screen with a black screen though rebooted it went fine though the vnc server needed to be reset so...
Get to webtop root through the terminal emulator and run...)
tightvncserver
(you'll be promoted to set up another password, once done you can go back and use the vnc view settings you had before and get back in do what you need and exit and you will beable to plug in too hdmi/doc/etc without loading up a completely grey screen with the nice useless x courser XP)
Now the really fun part kicking myself that I didnt realize this shortly after setting this up, but you got this vnc server running on your webtop but you really arn't big on messing with the tiny screen while your on a wifi and you have access to a computer or even your pluged into a computer and have moto phone portal open on it.... well haha just download a vnc viewer get your IP address (from network or the phone portal ip) on the network and plug
(the x's are your IP numbers being that every network might be different you get the diffrent)
XXX.XXX.XXX.XXX:5901
as the target address and you be asked to enter a password that you set up and note that the 01 in the port suffix is indeed the display number.
And bamn easy access to your webtop on your Atrix while your chilling and using your TV for what every you watch XP
Any suggestions changes or better how to's post your stuff and Ill add it with quotes this will not work in any of the Debian mods Images/Including Blacktrack 5 (v.v) due to not being able to load the linux app from the command line Tho will work on the DebainMOD/ w apt sources fixed. I'm looking into getting into chroot after I finish up my tweaks from a fresh test run.
Known Half Way Marks: Use Seamonkey Browser to replace firefox while using vnc sessions. The sessions are in root user which is fine for the pinch use, but if you wanna resume what you were using on the webtop from vnc veiwer in hdmi and vica versa I need some one to look at the commands and see where it is I marked up above where I think it is the grey part x.x will update this part think I'm closing in on a solution to this, and it would reflect what you see on the hdmi and be shared XD
Known pita: Screen time out..... kills the tightvncserver display as well >,>
For now the most recommended use guide can be found here you don't necessarily have to plug into the HDMI of the initial launch if you follow the steps above, although not the intended direction mostly the safest if you follow these steps being that currently without X or Xvnc being configured you may very well mess with your HDMI at display at DISPLAY=:1 being that the vnc method at this point exports the root environment only the method below is safe and would do XP
See this for the direction of vnc without use of a dual boot within chroot still needs messing with as mentioned above back your Sh%^t up X3
fernandoavc said:
I've finally made it work the way I wanted but it probably not the best or easiest way to do it...
1-)First I plugged in my HDMI cable over my phone and my tv and got Webtop V1 running.
2-)From lxterm I issued the command 'sudo bash backtop' (this is very well explainned over this thread)
3-)Once I got the terminal from BT running then I issued the 'ui' command that is a vncserver built-in into backtrack5 ARM distro and with the default password of 123456789 (you can change it by issuing 'vncpasswd' command if you want..)
4-) Now you can unplug the HDMI cable if you want.
5-) And you are ready to connect at the gnome version of Backtrack from your cell phone using any of the vnc clients available on the Market with no need of the HDMI anymore...
Concerns:
1-)How about battery life after that? will it be drained since bt is running "in the background" ?
I didn't tested yet... and have no idea atm... will let it running here to see if it get warmer than normal or the battery last shorter (of course it will not last longer...)
2-) Is there a way to run this commands without the HDMI cable plugged-in?
If anyone interested (or even you Djazin) want to see some directions/hints there is a thread written by an X10 owner that have some scripts to be used at the phone terminal, the X10 doesnt have the webtop (duh)... not sure how useful it is for us but maybe the scripts he wrote can be used....
As we were discussing before in this thread if I try to run the command " sudo bash backtop" it gives a lot of errors from mount points unreacheable to DISPLAY problems... I will post the errors here just in case any one reading have some good ideas to contribute:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See the screenshot of my phone running smootly the BT5 distro:
And here is the script from the thread mentioned on the step 2 - I just renamed it to .txt but it's a bash script:
backtop.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This looks really interesting. I'm not able to test right now, but I wonder how come this one didn't get more views/replies until now.
Anyway, thanks OP for sharing, I'll test it ASAP.
Thanks for the guide!
Just wondering something... what if we have a way to run the webtop without a dock/lapdock then put some kind of vnc server and through the phone itself (with a vnc client for android) to access it as a remote computer..... Am I tripping?
fernandoavc said:
Just wondering something... what if we have a way to run the webtop without a dock/lapdock then put some kind of vnc server and through the phone itself (with a vnc client for android) to access it as a remote computer..... Am I tripping?
Click to expand...
Click to collapse
The Webtop runs alongside the phone as it is you can get to its shell through a terminal emulator (I installed all of this through terminal emulator on the android side) and run tightvncserver after setting this up and access webtop through a vnc client on the phone screen.... now if you mean to access the webtop's vnc server from a local remote computer work/home over the network then... heh that would take alot of config within tightvncserver probably with a parallel program like xauthority configured to run the vnc server with a lan address 192.168.x.x and so forth how to do that Im not sure I thought about it earlier this morning but atm Im trying to get backtop working x.x
as for tightvncserver options run
toghtvncserver -h
Though atm there is no vnc server working on the atrix android side
Djazin said:
The Webtop runs alongside the phone as it is you can get to its shell through a terminal emulator (I installed all of this through terminal emulator on the android side) and run tightvncserver after setting this up and access webtop through a vnc client on the phone screen.... now if you mean to access the webtop's vnc server from a local remote computer work/home over the network then... heh that would take alot of config within tightvncserver probably with a parallel program like xauthority configured to run the vnc server with a lan address 192.168.x.x and so forth how to do that Im not sure I thought about it earlier this morning but atm Im trying to get backtop working x.x
as for tightvncserver options run
toghtvncserver -h
Though atm there is no vnc server working on the atrix android side
Click to expand...
Click to collapse
Oh I will try that... but I am not sure how to run webtob without plug anything on it (such HDMI over tv or lapdock) ... may I just issue the startx command over a terminal? do the xterm works if I issue it through a connectbot or something? Do you suggest something else?
I actually want it because of the Backtop (my backtop is working fine but I need to run it with sudo bash backtop command thats why I want to vncview it ...) may I help you somehow?
can you clarify what does this actually do...does this mean i can vnc from my actual phone to the webtop on my phone screen?
or can i use this to access webtop from my vnc client say on a laptop on the same wifi network...
humzat said:
can you clarify what does this actually do...does this mean i can vnc from my actual phone to the webtop on my phone screen?
or can i use this to access webtop from my vnc client say on a laptop on the same wifi network...
Click to expand...
Click to collapse
first one, yes you can!!! using this guide XD
Second needs tweaking but in theory I don't see why it wouldn't I'm working on getting backtop without any form of the Debian mod then Ill get back to that.
fernandoavc said:
Oh I will try that... but I am not sure how to run webtob without plug anything on it (such HDMI over tv or lapdock) ... may I just issue the startx command over a terminal? do the xterm works if I issue it through a connectbot or something? Do you suggest something else?
I actually want it because of the Backtop (my backtop is working fine but I need to run it with sudo bash backtop command thats why I want to vncview it ...) may I help you somehow?
Click to expand...
Click to collapse
its easy from terminal emulator run the following without (anything in)
su
(get root)
(then run)
/usr/bin/sudo -u adas bash
(or just)
/usr/bin/sudo -u root bash
(Thats all)
and your in webtop with no hdmi/gui from here you can infact install vncserver using the steps above or just run commands without accessing the gui now xterm needs a gui exported display of "any" kind because it is mostly like a vm there was a way once you got up up and running you can access from command line only but I'ma have to dig for that within the Debain Mod posts I used to get it done when I was using them, but I cant for the life of me recall.
If you can post how you were able to get Backtop to work in that thread for it it might help I got the same output that one user posted in page 3 of that thread.
Djazin said:
first one, yes you can!!! using this guide XD
Second needs tweaking but in theory I don't see why it wouldn't I'm working on getting backtop without any form of the Debian mod then Ill get back to that.
Click to expand...
Click to collapse
How? I can see through 'ps' command that xinit is running .... but how to issue a vncserver command or something?
My backtop runs through that webtopmod from Joe version one and the bt img on the /sdcard/bt folder including the scripts backtop and stopbacktop .... Are you planning something different from that?
Sorry all the dumb questions I did... just read the OP and saw everything I need.. now I am researching about to change the 10.77.32.150 address from sources.list that I actually have on my /osh/etc/apt folder... to be able to install the tightvncserver... Will post my results .. ty for the post Djazin
fernandoavc said:
How? I can see through 'ps' command that xinit is running .... but how to issue a vncserver command or something?
My backtop runs through that webtopmod from Joe version one and the bt img on the /sdcard/bt folder including the scripts backtop and stopbacktop .... Are you planning something different from that?
Sorry all the dumb questions I did... just read the OP and saw everything I need.. now I am researching about to change the 10.77.32.150 address from sources.list that I actually have on my /osh/etc/apt folder... to be able to install the tightvncserver... Will post my results .. ty for the post Djazin
Click to expand...
Click to collapse
The webtopscripts run well with most webtop mods they are here should allow you to install tightvncserver without problems
Adding to OP as a pre-rec
Djazin said:
The webtopscripts run well with most webtop mods they are here should allow you to install tightvncserver without problems
Adding to OP as a pre-rec
Click to expand...
Click to collapse
Nice hint man I finally did the apt-get to work and installed the tightvncserver! Now I just need to make it works openning a valid xwindow ( actually it is openning the xwindow with nothing but the crosshair)
But so far thank you for all your help!!!
Sent from my MB860 using XDA App
fernandoavc said:
Nice hint man I finally did the apt-get to work and installed the tightvncserver! Now I just need to make it works openning a valid xwindow ( actually it is openning the xwindow with nothing but the crosshair)
But so far thank you for all your help!!!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
is the x window grey or is it showing a the webtop background with no dock, if its the first you need to run the cat > /root/.vnc/xstartup command and add the text below it from the op or you will cause the vncserver to export the x server settings bare which at this point is a pita to set up for the adas user environment though root exports fine atm I updated the code group under the cat command try them from root in which ever webtop terminal you prefer to use, I'm actually doing this from a stock webtop again to check it out that and I wanted my Debian mods back so I can try to set up vncserver for them as well.
Last night I was messing with the webtop's x server and found a more native vnc server built into the very x server that supports hdmi we possibly might be able to get vnc server to export the hdmi display as soon as I figure out where to put the shar display commands for vnc access but for now this seems to work fine in the root environment and its safer than what I was trying last night hehe I switched the hdmi cable display with the root environment that was accessed through vnc but no key pad so it was interesting to see, thought it didn't survive my tinkering.
fernandoavc said:
Nice hint man I finally did the apt-get to work and installed the tightvncserver! Now I just need to make it works openning a valid xwindow ( actually it is openning the xwindow with nothing but the crosshair)
But so far thank you for all your help!!!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Recreated that problem you were having go to /root/.vnc and delete your current xstartup file then from terminal run
tightvncserver -kill :1
tightvncserver
and you should be set
Sent from my MB860 using XDA Premium App
Djazin said:
Recreated that problem you were having go to /root/.vnc and delete your current xstartup file then from terminal run
tightvncserver -kill :1
tightvncserver
and you should be set
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Hey sorry the delay in response but I did the cat step and also the kill but still getting the grey screen with no xterm just the crosshair ...
Sent from my MB860 using XDA App
fernandoavc said:
Hey sorry the delay in response but I did the cat step and also the kill but still getting the grey screen with no xterm just the crosshair ...
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
run the kill command then in root explorer kill xstartup in /root/.vncserver then run tightvncserver and it should load the mouse and a grey screen and then it'll load the root desktop just after that (give it a few seconds). if not reboot and try it all again.
UPDATED OP check out the bottom section
Djazin said:
run the kill command then in root explorer kill xstartup in /root/.vncserver then run tightvncserver and it should load the mouse and a grey screen and then it'll load the root desktop just after that (give it a few seconds). if not reboot and try it all again.
UPDATED OP check out the bottom section
Click to expand...
Click to collapse
Even doing the commands
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
I am still getting the grey screen with nothing but a crosshair mouse pointer.... instead of lxsession can I use something else?
Edit: figured it out
fernandoavc said:
Even doing the commands
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
I am still getting the grey screen with nothing but a crosshair mouse pointer.... instead of lxsession can I use something else?
Click to expand...
Click to collapse
Post your config your version of webtopmods's active what your osh-wrt-1 and 2 sh files are set with and What dock are you using as well as the settings your using in the vnc viewer, I'ma try to recreate your set up on another Atrix I have and see if I can crack what your problem with the root environment is.
Note if your just using the AWN dock try something else, though even with no dock it should at least load the stock wallpaper with the mouse cruiser. And you did delete the xstartup file found in /root/.vnc and not try to recreate one?
Djazin said:
Post your config your version of webtopmods's active what your osh-wrt-1 and 2 sh files are set with and What dock are you using as well as the settings your using in the vnc viewer, I'ma try to recreate your set up on another Atrix I have and see if I can crack what your problem with the root environment is.
Note if your just using the AWN dock try something else, though even with no dock it should at least load the stock wallpaper with the mouse cruiser. And you did delete the xstartup file found in /root/.vnc and not try to recreate one?
Click to expand...
Click to collapse
Well my webtopmod is Joe Ferreira v1 and I've installed the webtop2sd from Sorgarth... about the wrt-osh 1 and 2 I'm gonna need to know how to get them to you... I 've some linux knowledge so just tell me where they are... My vnc I am connecting at the port the server is telling me (i.e: localhost:1 - 5901).
I'm not using Any dock at all... nothing connected through the hdmi port....
I'd deleted the xstartup and when I run the tightvncserver it was recreated with different values from what u suggested ... it recreate the following content:
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
#x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#x-window-manager &
/etc/X11/Xsession
By my knowledge in linux and vnc I am suspecting that it's not being able to load the icewm xwindow...
Sent from my MB860 using XDA App
There hasnt been much talk about the terminal emulator and how much power it has if any so guys i was thinking is there ,anyway to send messages over the terminal emulator on android ive tried notify-send but doesnt work :-\ also looking for any other useful or cool tricks that can be done over the android terminal emulator :cool
Im using terminal ide by the way can anyone get pinging websites to work i might be doing it through the wrong port im using port 80
I bought a Favi FE02BT-BL mini bluetooth remote and no matter what I did, I couldn't get it to connect through the settings.apk even thou people with the FireTV Stick are able to connect.
This took me to the command line to try a few things so this is as far as I could get.
Fist lets connect to the FTV and enter su
adb connect x.x.x.x
adb shell
$ su
Next we're going to remount the system as rw and download some files to the system
# mount -o remount,rw /system
# cd /system/xbin
# wget http://androidobex.googlecode.com/files/hciconfig
# wget http://androidobex.googlecode.com/files/hcitool
# wget http://androidobex.googlecode.com/files/hidd
# chmod 777 hciconfig
# chmod 777 hcitool
# chmod 777 hidd
# cd /
# mount -o remount,ro /system
Now we can run some commands
# hciconfig
hci0: Type: UART
BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 1021:8 SCO
UP RUNNING PSCAN INQUIRY
RX bytes:41121 acl:373 sco:0 events:1628 errors:0
TX bytes:14569 acl:401 sco:0 commands:666 errors:0
# hcitool dev
Devices:
hci0 xx:xx:xx:xx:xx:xx
On the FireTV go to the settings.apk and go to the bluetooth menu and hit scan
Set your remote to discoverable
# hcitool scan
Scanning
11:11:11:11:11:11 Bluetooth FAVI
#hidd --connect 11:11:11:11:11:11
The light in your keyboard should stop blinking and the keyboard should be connected
THE BAD:
- Mouse pad doesn't work
- Connection is lost when keyboard enters sleep
- Does not reconnect automatically
Any one with better knowledge of Android can probably get this to work 100% so any help would be appreciated.
I was also searching for a way to use my iPazzport Bluetooth keyboard with my Fire TV box, and after several dead ends I finally figured out a working solution! Unfortunately this requires root, but both the keyboard and integrated touchpad seem to function perfectly, and so far it has had no problems reconnecting after waking from sleep. This may also be useful for other Bluetooth devices that will accept a PIN of "0000".
For reference, my Fire TV box is running rbox's pre-rooted 51.1.4.0 ROM and I'm using an iPazzport KP-810-10BTT keyboard.
The first step is to sideload the Settings APK mentioned in several other threads on this forum. Open the app and go to the Bluetooth section. Put your keyboard into pairing mode, press "Scan for Devices" and ensure that it shows up in the list of available devices. Select your keyboard from the list to begin pairing and then press cancel when you see the prompt to enter a PIN.
Connect to your Fire TV using adb, open a shell and run this command:
Code:
logcat -d | grep BTConnectionReceiver
You should see several lines that include "BluetoothDevice: address=<XX:XX:XX:XX:XX:XX>, alias=null, name=<keyboard name>". The XX:XX:XX:XX:XX:XX part is the Bluetooth address of your keyboard. Make note of the first half of this address, you will need it for the next step. For example, the first half of my keyboard's address is 54:46:6B.
Next, in your adb shell, type:
Code:
su
echo FixedPinZerosKeyboardBlacklist=XX:XX:XX > /data/misc/bluetooth/dynamic_auto_pairing.conf
Replace XX:XX:XX with the first half of your device's Bluetooth address. Make sure to use uppercase letters if the address contains any. You can use multiple addresses by separating them with a comma, like this: XX:XX:XX,XX:XX:XX
Now reboot your Fire TV, go back into the sideloaded Settings app and select Bluetooth. Make sure your keyboard is in pairing mode and press "Scan for Devices". Select your keyboard from the list and when you see "Pairing..." under its name, quickly type four zeros (0000) on your Bluetooth keyboard and press "enter". It should now successfully pair and begin working right away. Enjoy!
If the settings app gives you a PIN to type on your keyboard instead, then something went wrong and you should make sure that you followed all the directions carefully and used the right Bluetooth address, using all uppercase letters.
essdee said:
Code:
su
echo FixedPinZerosKeyboardBlacklist=XX:XX:XX > /data/misc/bluetooth/dynamic_auto_pairing.conf
Click to expand...
Click to collapse
Thank you, that worked perfectly with the exception that "logcat" wasn't returning any values so I had to use the "hcitool scan" command from my post.
Weird, I got a bunch of messages in logcat when I tried it on my box, but only after I tried pairing at least once. I also have busybox installed, so that might make a difference too. Glad someone else found the info useful though.
essdee said:
Weird, I got a bunch of messages in logcat when I tried it on my box, but only after I tried pairing at least once. I also have busybox installed, so that might make a difference too. Glad someone else found the info useful though.
Click to expand...
Click to collapse
I have busybox installed as well and I think the reason I don't get anything back is maybe the process name after grep is incorrect.
If I type
Code:
logcat -d | grep Bluetooth
I get a bunch of messages but not with BTConnectionReceiver
essdee said:
The first step is to sideload the Settings APK mentioned in several other threads on this forum.
Click to expand...
Click to collapse
Where can we get this Settings.APK?
Neo3D said:
Where can we get this Settings.APK?
Click to expand...
Click to collapse
Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=2714494
Hi All,
This seems to be exactly what I need, but I just purchased my AFT and have not been successful in root it. Is there another way of getting this to work (other than obviously purchasing another mini keyboard)?
Thanks,
Jose
josep01972 said:
Hi All,
This seems to be exactly what I need, but I just purchased my AFT and have not been successful in root it. Is there another way of getting this to work (other than obviously purchasing another mini keyboard)?
Thanks,
Jose
Click to expand...
Click to collapse
I don't know of anyway to do it without root.
Why are you unable to root? Did you update the box?
Try to return it and get a new one but this time go to http://www.aftvnews.com/start/ before you plug in the box.
lightning413 said:
I don't know of anyway to do it without root.
Why are you unable to root? Did you update the box?
Try to return it and get a new one but this time go to ... before you plug in the box.
Click to expand...
Click to collapse
It is my understanding that firmare versions past 1/1/15 can no longer be rooted. At least not yet. I looked at the version I have and it does not show up as one of the "rootable" versions.
josep01972 said:
It is my understanding that firmare versions past 1/1/15 can no longer be rooted. At least not yet. I looked at the version I have and it does not show up as one of the "rootable" versions.
Click to expand...
Click to collapse
I bought one a couple of weeks a from Staples and it was rootable.
lightning413 said:
I bought one a couple of weeks a from Staples and it was rootable.
Click to expand...
Click to collapse
I guess no such luck with me... Any other ideas?
lightning413 said:
I bought one a couple of weeks a from Staples and it was rootable.
Click to expand...
Click to collapse
No such luck for me. Any other ideas?
Thanks,
Jose
josep01972 said:
No such luck for me. Any other ideas?
Thanks,
Jose
Click to expand...
Click to collapse
The only one I can think of is to get a FireTV Stick instead of the FireTV.
Eventhou the Stick can't be rooted, they can connect the bluetooth keyboards through the settings.apk app without any issues.
lightning413 said:
The only one I can think of is to get a FireTV Stick instead of the FireTV.
Eventhou the Stick can't be rooted, they can connect the bluetooth keyboards through the settings.apk app without any issues.
Click to expand...
Click to collapse
Thanks for your answer. Has anyone figured out why that is? Is Settings.apk at fault, or does it call some faulty routine that takes over?
Regards,
Jose
I have a bluetooth accessorie kb for my old galaxy 7510 tab. Wonder if I can use for my fire tv?
josep01972 said:
Thanks for your answer. Has anyone figured out why that is? Is Settings.apk at fault, or does it call some faulty routine that takes over?
Regards,
Jose
Click to expand...
Click to collapse
I've spent some time digging around in the Bluetooth configuration files for both the box and the stick, and here's my theory. Although the box and stick run mostly the same software, due to major hardware differences they each use a different Bluetooth stack.
For whatever reason Amazon thought it would be easier/better to use BlueZ with the Fire TV box version even though by default Android 4.2+ comes with BlueDroid(which is what the stick appears to use). It looks like Amazon made BlueZ work well enough for their accessories, but since none of them use a PIN, that part of Bluetooth pairing never got fixed.
essdee said:
The first step is to sideload the Settings APK mentioned in several other threads on this forum. Open the app and go to the Bluetooth section. Put your keyboard into pairing mode, press "Scan for Devices" and ensure that it shows up in the list of available devices. Select your keyboard from the list to begin pairing and then press cancel when you see the prompt to enter a PIN.
Connect to your Fire TV using adb, open a shell and run this command:
Code:
su
echo FixedPinZerosKeyboardBlacklist=54:46:6B > /data/misc/bluetooth/dynamic_auto_pairing.conf
Now reboot your Fire TV, go back into the sideloaded Settings app and select Bluetooth. Make sure your keyboard is in pairing mode and press "Scan for Devices". Select your keyboard from the list and when you see "Pairing..." under its name, quickly type four zeros (0000) on your Bluetooth keyboard and press "enter". It should now successfully pair and begin working right away. Enjoy!
Click to expand...
Click to collapse
This just worked perfectly for me and the FAVI FE02BT-BL. I used the FireTV-Bluetooth-Settings.apk from here http://forum.xda-developers.com/showpost.php?p=58092814&postcount=54
Using this just saved me from returning this device to Amazon! Even the touchpad works. I was just about to return this for the RF version, but now this frees up the USB port for other uses.
post #2 worked perfect for me. I was able to get the bluetooth address off the back of my keyboard and didn't have to run the logcat commands etc. Took literally <1 minute to install the settings.apk and run command, a reboot and <1 minute to pair the keyboard.
Touchpad and keyboard work for me.
Using the Logitech PlayStation 3 Cordless MediaBoard Pro.
This is a tutorial on how to get an official Sony brand Dualshock 3+Sixaxis Controller (AKA PS3 controller) working on your Fire TV over USB.
This has been tested on confirmed working on the Fire TV 2 (Sloane) but will presumably work on all generations and versions of Fire TV as long as it is rooted.
WHAT YOU WILL NEED:
-Root Access (required for joy to touch feature, with apparently must be activated to use the feature that emulates other controllers)
-A Terminal Emulator app or ADB
-SELinux set to "Permissive" (I use the app SELinux Mode Changer)
-The following apps installed:
*USB/BT Joystick Center
*Sixaxis Enabler
-Mouse (any USB or Bluetooth mouse should be fine. I use a logitech K400+ Keyboard With Touchpad)
OR
-Mouse Toggle app
-Powered USB Hub (Only if your mouse is USB)
OPTIONAL: My supplied keymaping file
This is a pretty straightforward process, in all reality. Here are the steps.
1. Install USB/BT Joystick Center. I have included the APK for an older free version of the app, but I would suggest obtaining the latest "Gold" version, which is for sale on Google Play.
2. Open your ADB connection or Terminal Emulator of choice, enter a root shell with "su" and enter the following commands:
Code:
ime enable com.poke64738.usbjoygold/.USBJoyIME
ime set com.poke64738.usbjoygold/.USBJoyIME
OR
Code:
ime enable com.free.usbjoyfree/.USBJoyFreeIME
ime set com.free.usbjoyfree/.USBJoyFreeIME
Depending on if you are using the paid 2019 Gold version, or the free 2018 version, respectively.
Then you may close your ADB or terminal. Honestly I'm not entirely sure this is even needed, since we are going to be using gamepad emulation, but I would say to do it just in case.
3. Install Sixaxis Enabler, open it, and follow the instructions on screen. Allow the app to access the USB Device when prompted
NOTE: Sixaxis Enabler may tell you that your firmware does not support Sixaxis and that the service is stopped. In that case Keep disconnecting the controller and reconnecting it and pressing the PS Button. "Eventually it will say Sixaxis ENABLED Please Try buttons and sticks"
This is NOT a free app and is available for purchase on Google Play.
When you get "Sixaxis ENABLED" the four LEDs will stop blinking and just LED 1 will blink. If you keep getting the not supported message, and your LED 1 blinks, continue because you might still be able to get it to work.
4. Exit Sixaxis Enabler and open USB/BT Joystick Center. For this you will need some sort of mouse functionality.
Check in the upper left of the screen and make sure that the IME switch is orange and says "ON" (this should be the case, as we have already enabled and set the IME in ADB/Terminal)
With your mouse, click the IME switch and it should bring up a little menu. Click on USBJoyIME and the menu will close. This was just to be absolutely sure that the IME was FOR SURE selected.
5.Below the IME switch, there is a oval shaped cluster of buttons that will say "Search, Auto, Norm, HID"
Click "Norm" and then click allow on the prompts to access the USB Device. (if you have multiple devices connected over USB, it will ask for each device. You do NOT need to allow them all if you do not wish, a black notification at the top of the screen will tell you what device it found so you know what the app is requesting access to. I just click allow on all because it doesn't hurt anything)
After it gets trough all the USB devices, it will start a check for bluetooth devices, and will show a prompt with your paired devices on it, you can just click back on your Fire Remote or keyboard.
After a few seconds, a gray square will appear on the screen that says "PS3 USB Controller and LED 1 on your PS3 controller should now be solid. With your mouse, click on the square. A little black text box will say something about loading a keymap file. If you click some buttons on your controller, you should see the little boxes underneath the big gray box blinking orange and white when you press them. CONGRATS! You now have your PS3 controller working on your Fire TV.
Don't be content yet, WE ARENT DONE.
While this is a somewhat functional way to control your Fire TV, I don't find the default settings to be optimal. It seems like I can't rapidly press buttons. I can enter in two or three button presses before it stops accepting input for a moment. Also, despite all the controller buttons working on the test in USB/BT Joystick center, the default keymap is NOT properly configured for the Fire TV, and I was only able to get the D-pad to work outside of Joystick Center.
Instead of fussing around trying to get everything working with the default IME setting, I decided to use the app's built in controller emulation feature to simulate an Xbox 360 controller. (There is also a setting to emulate a PS3 controller, but I figured it would be better to make the system think I'm using a 360 controller, which is officially supported, then a controller that I had to install off of this stuff just to use) So onto Step...
6. With your mouse, go to the upper right and click the switch "J>T"
If you do not Already have SELinux set to Permissive, it will give you a message saying that this must be done. Do so however you want, but as mentioned above, I use the app "SELinux Mode Changer" to achieve this. The app can be found on F-Droid
With SELinux set to Permissive, give USB/BT Joystick Center Superuser rights when prompted, and the switch will turn ON.
Once "J>T" is on, to the left of that you will see the Green "JOY>" switch and a small box next to it that says "IME NAT 360 PS3"
Just click the box until "360" is selected
From here you can use the little boxes underneath the "PS3 USB Controller" box, or just load my keymap file, in order to configure the buttons and sticks properly. If you use my keymap file, down load "PS3to360_JoyPrefsFile_1356_616_0.xml" from the attachments and paste it into the folder for USBJoy in the root of your Fire's internal memory (for me it is called "USBJoyGoldData") then use the little load button and it should appear as "PS3 to 360"
With that out of the way, you are finally DONE! Your Dualshock 3 controller is connected and configured to act as an Xbox 360 controller on your Fire TV and you may now proceed to use it on your games, Emulators, or whatever you want to do with it!
When you are done, just make sure to disable "J>T" with Joystick center before you disconnect the Dualshock, otherwise things will bug out, and if you arent using an alternate launcher with mouse support, you wont be able to re-enter the app to disable it, and will have to reboot the Fire TV.
I would also suggest disabling USBJoyIME when you are not using your controller, as I have noticed that typing with my K400+ keyboard acts strange on some apps, such as Puffin Browser, when it is still enabled.
Code:
ime disable com.poke64738.usbjoygold/.USBJoyIME
OR
Code:
ime disable com.free.usbjoyfree/.USBJoyFreeIME
Feel free to play around with the different gamepad emulation modes, and if you find a better configuration, please do share it on here!