I was able to get my old G1 talking just fine by tweaking the udev rules, so it's not like I am totally unfamiliar with how it's supposed to work.
The facts so far, as far as I can verify:
1. udev rule in place, like with working G1 entry only with new strings (g1 commented out here for testing):
Code:
#G1 stanza
#SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="[I]username[/I]"
# Optimus T stanza
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1004", ATTRS{idProduct}=="618e", MODE="0666", OWNER="[I]username[/I]"
I've tried many, many udev rule combinations (sysfs v. ATTR v. ATTRS) followed by udev restarts and some reboots when I really wanted to be sure. You would think that the stanza that works right now with the G1 would work with the OptT. Grrr.
2. USB debugging turned on at handset. Handset shows USB Debugging On when plugged into usb cable.
3. Mass Storage Only option turned off in Settings
4. device shows up in lsusb, sdcard is mountable over USB, no problems there
Code:
Bus 001 Device 011: ID 1004:618e LG Electronics, Inc.
5. tried several different USB ports, front and back
6. xubuntu 10.10
Code:
Linux [I]redacted[/I] 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:48 UTC 2011 i686 GNU/Linux
7. Rooted OptT, 2.2. It exhibited the same lack of cooperation before rooting, too. Rooted mainly to run Ti Backup to remove some of the bloatware.
Is there something squirrely about the T that I am missing here? I will assume the problem is with my udev rather than anything else.
Possibly solved.
I pulled down the latest sdk and downloaded a newer adb as described in the tools/adb-has-moved.txt file:
Code:
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
[B]launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
[/B]
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.
Was running adb 1.0.20; after update it's 1.0.26 and it immediately connected to the phone with zero changes to anything other than adb itself.
I hope this helps someone else. I was starting to doubt my sanity.
If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
I am currently running the same setup. I will try soon and report back. Thank you!
Sent from my PG86100 using XDA Premium App
MiSfit211 said:
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
That will work. It's exactly what I had to do about 5 days ago to get ADB to work with my 3D. Prior to doing that, i would just get "List of Devices attatched : ??????????? NO permissions". I did a bit of googling and found the steps you just posted. Definitely would've saved me some searching if this was up last week This should help out anyone with the same problem, because it definitely works. Nice write up.
working perfect, thank you very much for the guide.
The only thing I had to do in addition was restart the adb server (since it was already running)
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT16MHX28070 device
(Also, the chmod to executable won't hurt anything but isn't necessary)
Thanks for the post!
thanks buddy. this couldnt have been any more helpful. it worked like a charm. this was very easy to follow. I am new to linux and appreciate the effort that you put in to explain getting this to work.
I used this thread and it works perfectly.
XDA/showthread.php?p=11823740#post11823740
MiSfit211 said:
If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
Click to expand...
Click to collapse
great post.just a heads up, you shouldn't have to do this on 11.10 though. after a fresh install of 11.10 and android-sdk all seems to be working without doing this.
This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) OpenSuse, Fedora AND Gentoo. If there's any missing for major distro's let me know, or add them to a separate post and i'll put them up here
***Debian based distros**
Code:
sudo apt-get install mtpfs
sudo mkdir /media/onex
sudo chmod 775 /media/onex
sudo mtpfs -o allow_other /media/onex
gedit /etc/udev/rules.d/51-android.rules
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then:
sudo service udev restart
***Arch Linux***
Code:
pacman -S libmtp
After installation, you have several mtp tools available. Upon connecting your MTP device, you use:
mtp-detect
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then reload udev rules:
udevadm control --reload
Arch Linux guide is from the ArchLinux wiki
**Redhat\Fedora16**
First of all, I using my computer with other people, who can come over the network, so the 0666 mode bits not a right choice for me. I make it all on a fedora 16, but the distro is really not important.
So the steps:
- add a user to the "disk" group (or whatever You want)
- make a mount point (the media doesn't work for me, across the init removes the content)
- add this mount point to the fstab, with some parameter
- create udevd rules
- restart udevd
- install fuse-mtpfs
- (re)login user
- try it
My common experience is that, the mtpfs is very very very very slow. Really slow, so I can use it only with CLI, any GUI has been coming back with time out
And the "code":
Code:
usermod -a -G disk $LOGINUSER
Code:
sudo mkdir /mnt/sgs2 ; sudo chgrp disk /mnt/sgs2; sudo chmod 0770 /mnt/sgs2
Code:
sudo echo "mtpfs /mnt/sgs2 fuse users,noauto 0 0" >> /etc/fstab
Code:
cat > /etc/udev/rules.d/51-android.rules <<EOF
SUBSYSTEM!="usb_device", GOTO="label_end"
ACTION!="add", GOTO="label_end"
# ATRRS{idVendor}== ertekei:
#Acer 0502
SUBSYSTEM=="usb",ATTRS{idVendor}=="0502",MODE="0660",GROUP="disk"
#ASUS 0b05
SUBSYSTEM=="usb",ATTRS{idVendor}=="0b05",MODE="0660",GROUP="disk"
#Dell 413c
SUBSYSTEM=="usb",ATTRS{idVendor}=="413c",MODE="0660",GROUP="disk"
#Foxconn 0489
SUBSYSTEM=="usb",ATTRS{idVendor}=="0489",MODE="0660",GROUP="disk"
#Fujitsu 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Fujitsu Toshiba 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Garmin-Asus 091e
SUBSYSTEM=="usb",ATTRS{idVendor}=="091e",MODE="0660",GROUP="disk"
#Google 18d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="18d1",ATTRS{idProduct}=="4ee1",MODE="0660",GROUP="disk"
#Hisense 109b
SUBSYSTEM=="usb",ATTRS{idVendor}=="109b",MODE="0660",GROUP="disk"
#HTC 0bb4
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",MODE="0660",GROUP="disk"
#Huawei 12d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="12d1",MODE="0660",GROUP="disk"
#K-Touch 24e3
SUBSYSTEM=="usb",ATTRS{idVendor}=="24e3",MODE="0660",GROUP="disk"
#KT Tech 2116
SUBSYSTEM=="usb",ATTRS{idVendor}=="2116",MODE="0660",GROUP="disk"
#Kyocera 0482
SUBSYSTEM=="usb",ATTRS{idVendor}=="0482",MODE="0660",GROUP="disk"
#Lenovo 17ef
SUBSYSTEM=="usb",ATTRS{idVendor}=="17ef",MODE="0660",GROUP="disk"
#LG 1004
SUBSYSTEM=="usb",ATTRS{idVendor}=="1004",MODE="0660",GROUP="disk"
#Motorola 22b8
SUBSYSTEM=="usb",ATTRS{idVendor}=="22b8",MODE="0660",GROUP="disk"
#NEC 0409
SUBSYSTEM=="usb",ATTRS{idVendor}=="0409",MODE="0660",GROUP="disk"
#Nook 2080
SUBSYSTEM=="usb",ATTRS{idVendor}=="2080",MODE="0660",GROUP="disk"
#Nvidia 0955
SUBSYSTEM=="usb",ATTRS{idVendor}=="0955",MODE="0660",GROUP="disk"
#OTGV 2257
SUBSYSTEM=="usb",ATTRS{idVendor}=="2257",MODE="0660",GROUP="disk"
#Pantech 10a9
SUBSYSTEM=="usb",ATTRS{idVendor}=="10a9",MODE="0660",GROUP="disk"
#Pegatron 1d4d
SUBSYSTEM=="usb",ATTRS{idVendor}=="1d4d",MODE="0660",GROUP="disk"
#Philips 0471
SUBSYSTEM=="usb",ATTRS{idVendor}=="0471",MODE="0660",GROUP="disk"
#PMC-Sierra 04da
SUBSYSTEM=="usb",ATTRS{idVendor}=="04da",MODE="0660",GROUP="disk"
#Qualcomm 05c6
SUBSYSTEM=="usb",ATTRS{idVendor}=="05c6",MODE="0660",GROUP="disk"
#SK Telesys 1f53
SUBSYSTEM=="usb",ATTRS{idVendor}=="1f53",MODE="0660",GROUP="disk"
#Samsung 04e8
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="6860",MODE="0660",GROUP="disk"
#Sharp 04dd
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",MODE="0660",GROUP="disk"
#Sony 054c
SUBSYSTEM=="usb",ATTRS{idVendor}=="054c",MODE="0660",GROUP="disk"
#Sony Ericsson 0fce
SUBSYSTEM=="usb",ATTRS{idVendor}=="0fce",MODE="0660",GROUP="disk"
#Teleepoch 2340
SUBSYSTEM=="usb",ATTRS{idVendor}=="2340",MODE="0660",GROUP="disk"
#Toshiba 0930
SUBSYSTEM=="usb",ATTRS{idVendor}=="0930",MODE="0660",GROUP="disk"
#ZTE 19d2
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",MODE="0660",GROUP="disk"
LABEL="label_end"
Code:
udevadm control --reload-rules
Code:
yum/apt-get/pacman/etc install mtpfs
Logout-login, for get in to the disk group, connect the device via usb, and try
Code:
mptfs
without any parameter, and it must write out some information:
Code:
[email protected]:~$ mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 4
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)
fuse: missing mountpoint parameter
And finally mount /it must be working now with user account/:
[CODE]mount /mnt/sgs2
or dismount:
Code:
umount /mnt/sgs2
**OpenSuse 12.2**
this method will work for music and photos access only,
Code:
sudo zypper addrepo -f http://packman.inode.at/suse/12.2/ packman
sudo zypper ref (type a to always accept the packman repo)
sudo zypper in mtpfs
sudo vim /lib/udev/rules.d/69-libmtp.rules and add the following line (replace vim with gedit if you want a gui editor)
# HTC One X+
ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dfc", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
sudo cp /lib/udev/rules.d/69-libmtp.rules /etc/udev/rules.d/.
reboot
When you plug in the phone you will see android phone icon on the desktop click on it to browse your files.
*note
disable any media players from trying to read the device...
** Gentoo **
Code:
Prerequisites
If your device is not recognized by libmtp, try upgrading to latest (or even git) version.
User needs to be in group plugdev to mount device.
MTPFS
You need to add option: user_allow_other in /etc/fuse.conf
$ mkdir ~/AndroidDevice
$ mtpfs -o allow_other ~/AndroidDevice
NOTE: this can take really long time, up to several minutes. As an indication of successful mount the mtpfs will go to background.
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
If mtpfs doesn't work for you try updating to latest version first.
Go-MTPFS
Seems to be more stable
$ emerge -a go
$ mkdir ~/go
$ export GOPATH=/home/$USER/go
$ go get github.com/hanwen/go-mtpfs
To mount:
$ ~/go/bin/go-mtpfs ~/AndroidDevice
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
Troubleshooting
Sometimes (e.g. on HTC One X) USB debugging automatically turns on when device is connected to PC. You need to turn debugging off, otherwise libmtp can't recognise device.
Make sure your Android device is not going to sleep and the screen is not getting locked. Set screen timeout to very long values, or enable in Development section flag "Do not turn off the screen".
Thanks to ihavoc and Fonya1 for the opensuse and redhat\fedora tutorials
thank you a lot for your help.
when i try to acces to the /media/onex direcory i have this :
ls: cannot access onex: Transport endpoint is not connected
After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium
somemadcaaant said:
After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
excuse me to ask many question but i am really noob. when all this done what would i see in /media/onex ? actualy after mounting the folder is empty
the only thing i need to do is copy files from/to my HOX+
Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?
It still dont work, i have tryed so many things these days to mount my HTC Ox+ as a USB Mass Storage and everything failed.
I tried tou manualy mount a MTP folder on my Ubuntu like Lloir explained here.
I tried to flash a TeamWorkRecovery and a ClockWorkRecovery to access the "Mount USB" option in the menu
my Device is seen by ubuntu but i am unable to read or write anything, for example if I copy a music album, the copy operation starts, takes a very long time an then end whith an error lik "error unable to copy xxxx.mp3 file does not exist"
actualy i am almost convicted that using an MTP device as an usb mass storage under Ubuntu is purely and simply IMPOSSIBLE !
HQRaja said:
Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?
Click to expand...
Click to collapse
works for ALL MTP devices
Thanks a bunch. This should come pretty handy. =)
Lloir said:
works for ALL MTP devices
Click to expand...
Click to collapse
does it works for you ?
how do you copy your files from/to your phone ?
Waiting for Ubuntu instructions (maybe)?
followed instructions to the letter and still cant mount my htc one xL running jellybean on ubuntu
Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.
spdrosin said:
Waiting for Ubuntu instructions (maybe)?
Click to expand...
Click to collapse
The instructions for Ubuntu are the first ones (Debian based distros), Lloir mentioned it at the start of the OP:
Lloir said:
This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) And Archlinux i will add others soon.
Click to expand...
Click to collapse
Linux really needs to add native support for MTP already. They also should add native support for adb as well while they are at it. Its annoying to have to add entrees to udev to even to be able to access the device.
One suggestion for anyone wanting to do this with a device other than an HTC:
You'll need to change the line you add to /etc/udev/rules.d/51-android.rules based on the vendor of your phone.
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Change the code to one of the following USB vendor ids:
Code:
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Fujitsu 04c5
Fujitsu Toshiba 04c5
Garmin-Asus 091e
Google 18d1
Hisense 109b
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenovo 17ef
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10a9
Pegatron 1d4d
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony 054c
Sony Ericsson 0fce
Teleepoch 2340
Toshiba 0930
ZTE 19d2
Most up-to-date list is here: http://developer.android.com/tools/device.html
You can also have multiple vendor lines in your /etc/udev/rules.d/51-android.rules file, just put one on each line. As someone who's testing on a bunch of different devices, I simply put a line in for all of the above
If your vendor code isn't listed, enter the command "lsusb" in a terminal, and you'll see something like this:
Code:
Bus 001 Device 119: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Bus 001 Device 112: ID 18d1:4e42 Google Inc.
The first four hex values of the id is the vendor ID, e.g., for the Samsung it's 04e8.
cloverz7 said:
Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.
Click to expand...
Click to collapse
same here with GNex and ubuntu 12.04
Use Airdroid
Using Airdroid and wifi from Tethering hotspot, you can simply access your Android without USB Cable and you can use anything OS. Search on Google Play with keyword "Airdroid"
Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.
Nschneider7 said:
Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.
Click to expand...
Click to collapse
That "SUBSYSTEM..." line needs to be appended to the file opened in the text editor. It shouldn't be entered on the command line.
And add "sudo" to in front of that gedit line...i.e., "sudo gedit /etc/udev/rules.d/51-android.rules"
Good luck!
I prefer to use adb. If you want a GUI you can use QtADB:
http://qtadb.wordpress.com/
Hello everyone,
I started to port Tizen on Nexus 7.
Porting state:
- wifi working
- touchscreen working (doesn't yet support multitouch)
- media (pictures, music and videos) doesn't work
- no graphics acceleration (Xorg doesn't use Tegra module)
- USB doesn't work
- GPS / Bluetooth not tested
- Audio not tested
Installation:
To install it, you will need an unlocked Nexus 7 and MultiROMv7. MultiROMv7 is a way to have multi boot on Nexus 7. Once Recovery and MultiROMv7 are installed, you must reboot into recovery. Send image on your Nexus 7:
adb push /path/to/image/Nexus_7_Tizen.zip /sdcard/
After click on install button and select Nexus_7_Tizen.zip. It will install Tizen on your Nexus 7. Now you can reboot. In list of ROM, you will see Tizen_Testing. Select it and enjoy.
Download:
MultiROMv7: http://forum.xda-developers.com/showthread.php?t=2011403
Tizen ROM: http://easymt.org/files/Nexus_7_Tizen.zip
In days, I will publish instruction to build the ROM.
If you get this on par with the factory OS then you're a hair away from every nexus device using this if they want. Thank you for the work.
Sent from awesomeness?
Tizen 2.0?
Sent from my One S using xda app-developers app
Wonderful to see people just using MultiROM to create ports like this, good job
A big thank you for your work!
When USB will be avaible,
we can take screenshot from the Tizen SDK
(sdb_1.0.24_ubuntu-64)
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
it reminds me of something, but I do not know what
ikslawlok said:
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
Click to expand...
Click to collapse
LOL. adb knockoff.
johnwazhere said:
Tizen 2.0?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Actually, it is Tizen 2.0 alpha. I'm porting 2.0.
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used? (even though it's for their development tablet from what I've read the socs are identical)
https://developer.nvidia.com/linux-tegra
Sent from my Nexus 7 using Tapatalk HD
Culex316 said:
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used?
Click to expand...
Click to collapse
Yes it can be used. The driver work but it enable mice pointer.
Edit:
In fact I can't use it because xorg server and driver abi missmatch.
I probaly need to buimd another version of xorg than provided.
Thanks for your effort in this, very interested in this project. It's amazing to see the amount of operating systems being ported to Nexus 7.
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Sent from my GT-P6800 using xda app-developers app
You're right man.
Anyone believed in him.
I do not know why all this lies telling about his work.
He got several downloads through internet about his work. And no respect at all.
---------- Post added at 06:42 PM ---------- Previous post was at 06:32 PM ----------
I'm going to quit from here xda.
This was a bad experience.
I've released code.google.com/p/tizen-kernel-s8500
a github.com/vic3t3chn0
a twitter.com/vicetechno
for my it works.
now, i'm going to quit for the bad experience at telling me i'm a liar.
but I had downloads at code.google.com if i'm a liar.
thank you for all.
long6688 said:
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Click to expand...
Click to collapse
I don't know who exactly do you mean, but if it is the author of "Tizen [PORT] Attempt almost" thread then you might have not read that thread (or do not know bada/tizen forums) well enough to know that he claimed that he has so many things up and running without bothering to actually try to run it.
When we wanted to know the details it came out that he used many components developed by badadroid team without proper credit and claiming to have functionality that never existed (like working RIL or even stupid lie that he changed a bootlogo in the component that was not responsible for displaying it - to cover this lie he changed one line and provided only the non-working binary violating GPL, but the component was pure assembly we wrote so seeking truth was not difficult) in these components and were known not to be working with Tizen (kernel init not aligned with Tizen).
Looking at the repositories he pointed to, there is no source code he developed or even modified by himself - everything is public and part of other projects.
You are free to elaborate on my mental capacity, but from where I stand his complicated work appears to be limited to the ability to follow compilation instructions.
I don't claim he wanted that to be a scam from the very beginning - he might have had a will to do something and learn along the way (which would be an adequate way), but he chose to cheat where stuff got unmanageable.
While I still encourage everybody to take up the challenge to see how fun it is, but when such a "dev" is leaving XDA we couldn't be worried less. Bon voyage!
Does it take lot of time to boot up? Its showing [ 915.19111] CP L2->L0 and the process is being continued... Cant use power button.
So where does this stand? This is the one OS I want to use more than any other. I dont know jack about compiling code and such. But if someone has this for a N4 I would be all over it like ants on a peach.
This looks cool, I hope this thread doesn't die, I would really like to try Tizen on my nexus
Ubuntu touch is still unusable, but a tizen port could be quite stable, once properly ported
What is the progress of this project?
SuperBoUDS said:
What is the progress of this project?
Click to expand...
Click to collapse
Looks pretty dead. I keep coming back to check if I can get tizen on my s3
Sent from my GT-I9300 using xda app-developers app
...I keep coming back to check if I can get tizen on my s3
Click to expand...
Click to collapse
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
adfree said:
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I have asked in s3 thread. My post got deleted after a few comments... I was hoping a port for s3 would be easy and quick but there's no development on this whatsoever
Sent from my GT-I9300 using xda app-developers app