I have a question regarding using adb. I have the SDK on my computer but whenever I try to open adb, a command prompt pops up, scrolls some text really quickly and then closes itself immediately.
Is this normal or something I have done wrong.
well, it's normal if you run it wrong.
adb is a command line app, not a gui. So what you need to do is open a command prompt and then type "adb devices". If you added the tools folder to your path environment variable correctly then it should give you output.
Look here
http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/
that's a common thing in all cmd programs. if you dont run it straight from a cmd window, the window will just shut down when it's done. you should run ADB from a cmd window instead of just double clicking the ADB launcher icon. Somebody needs to make a frontend for those monstrous google tools.
anyway, just go Start>Run, and type cmd and then hit enter, navigate your way to your ADB directory, and run it from there (using ADB and then passing whatever parameters)
jubeh said:
Somebody needs to make a frontend for those monstrous google tools.
Click to expand...
Click to collapse
But ADB is a shell program, a "shell" front end is text/cli?
And ddms has a front end. Besides, you don't want to make it too easy for folks to screw up their phones.
smasraum said:
But ADB is a shell program, a "shell" front end is text/cli?
And ddms has a front end. Besides, you don't want to make it too easy for folks to screw up their phones.
Click to expand...
Click to collapse
i wholeheartedly agree. tools that can do damage need to be run in terminal because most people are either too lazy to learn the terminal/cmd or they are afraid of messing up the phone. if we were to build a front end where a user basically tells the program what they wanna do then they will more than likely decide to try new things and screw up the phone. new users might not search but if they are spoonfed they are less likely to stray from the instructions.
btw OP i do not believe you are a noob or anything else, just throwing what i think out there. i know you have been around for a while and you are a good member.
Does the terminal work with a VK?
yes it does. Although it may have some issues if its same as mytouch (like the number keys not registering)
i use android terminal emulator by jack palevich it works flawlessly even in landscape.
This might be a little odd, i'm on my vaication and i'm trying to learn a bit of linux! it's a very long vaication though
The thing is, i don't have internet where i am (accept 2g on my x10) and i don't have a computer (again, accept my x10)
So i'm reading this book "Linux Fundamentals" and i noticed some of the commands are not supported in android, i'm using better terminal and i'm rooted to r2 023.
The commands that are missing for eg. are ls -i so i can't see the inodes, cal for calendar, man for manual etc...
Is there some other way to access those commands or do they just don't exist on android?
The most problems i've been having is with the grep command. It seems to work because it gives me an explination of how to use it but when i try something loke this:
grep "this" demo_file - i get nothing and i should be getting:
this line is the 1st lower case line in this file Two lines above this line is empty
Am i doing something wrong or i just won't work whatever i try?
Sorry for being such a noob, i'm trying tho thanks
come on, no one?
EDIT: Can a mod please move this to the dev pages? Thanks
You might have more luck re posting this in the development pages..
Sent from my x10 using XDA and swype.
First off let me say thanks to the many members that posted pieces of this fix for various Samsung phones.
The sole purpose of this post is to condense the info I found spread out across multiple threads when trying to resolve this issue myself. Hopefully making it easier for future users that may have the same problem I did. Which is why I have the various sensor names in the subject.
If your phone is having problems auto-rotating, or does not rotate at all in any app (like mine did). These steps should get you working again. This will be overkill in some cases but I like to cover all my bases when something is not working to begin with.
Note: This assumes you are running Android 2.2 (if you are not, you will not be able to perform the last step, but your phone should still work properly without it). Your phone will need to be rooted with busybox and you will need a terminal emulator app installed. I have attached the "Android Terminal Emulator" apk just in case you don't have or know what that is.
open your terminal type su press enter
type cd /data/system press enter
type rm ms3c_yamaha.cfg press enter
type cd /system/bin press enter
type ./sensorcalibutil_yamaha press enter
secure your phone on a flat level surface and gently press the enter key on your keyboard
type exit press enter
type exit press enter
Close your terminal and go to menu -> Display -> Horizantal calibration
turn your phone upside down with the bottom edge over hanging the table you used as a flat surface so that you can just barely see the calibration button when you are looking under the phone. Gently press the calibration button.
All done, you should be in working order!
Nice post! But the Epic does not require all of these steps that other phones might.(assuming your using Terminal Emulator)
Once within terminal, type
"su"
then you only need to type
"sensorcalibutil_yamaha" and press enter. Then follow the steps on the screen.
As far as hanging the bottom edge over the table goes, it's not necessary. The Epic is level on both ends because the camera protrudes at the other.
A couple of weeks ago, i had the problem where sensorcalibutil... in terminal emulator (and adb etc) was failing when trying to execute. Deleting the file above did fix this. So, maybe update the op to only try that if it fails. Thx for putting this together juise
Sent from my SPH-D700 using Tapatalk
decalex said:
A couple of weeks ago, i had the problem where sensorcalibutil... in terminal emulator (and adb etc) was failing when trying to execute. Deleting the file above did fix this. So, maybe update the op to only try that if it fails. Thx for putting this together juise
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Good point. I've never run into that issue myself, and I'm not sure what would cause it, but deleting that file would fix it.
Auto rotation.
Thanks for posting this. I was having this problem on my phone and now it's fixed!
Ahhh! This has finally fixed my auto-rotation issues! My phone has been unable to auto-rotate for months and now it works again. Thanks much!
mattallica76 said:
Nice post! But the Epic does not require all of these steps that other phones might.(assuming your using Terminal Emulator)
Once within terminal, type
"su"
then you only need to type
"sensorcalibutil_yamaha" and press enter. Then follow the steps on the screen.
As far as hanging the bottom edge over the table goes, it's not necessary. The Epic is level on both ends because the camera protrudes at the other.
Click to expand...
Click to collapse
Actually I needed to delete the cfg file with my Epic, so the need is there depending on the problem. This why I say in some cases this may be overkill, but it if you follow the instructions as posted no harm can come of completing all the steps I chose to list. As long as you don't have faulty hardware you should be back in business after completing them.
If my years with BSD/Linux have taught me anything, it's assume nothing! If you know *nix you'll notice that my commands assume nothing about the user environment. To me that is the safest way to provide instructions like these to users that may not be familiar with the OS.
Thank you for this consolidation... for noobies like me, searching all the forums can be a lil intimidating... this may be "overkill" like you said, but it sped up my auto-rotate like nobody's business. You get TWO thumbs up...
juise said:
Actually I needed to delete the cfg file with my Epic, so the need is there depending on the problem. This why I say in some cases this may be overkill, but it if you follow the instructions as posted no harm can come of completing all the steps I chose to list. As long as you don't have faulty hardware you should be back in business after completing them.
If my years with BSD/Linux have taught me anything, it's assume nothing! If you know *nix you'll notice that my commands assume nothing about the user environment. To me that is the safest way to provide instructions like these to users that may not be familiar with the OS.
Click to expand...
Click to collapse
Good philosophy. I'm just currious as to why that file would get corrupted in the first place. Unless folks are trying to restore data from a froyo Rom onto an eclair rom, this should not be happening. The file resides on the data partition which would have been wiped durring the install process, assuming it was done correctly. Ha, there I go assuming again.
Sent from my SPH-D700 using Tapatalk
meh i guess it works. didnt really do anything though.
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.