Related
Good day...
Im wanting to connect a USB camera to my ViewSonic G Tablet... I have 3 different USB models. When I plug them in (individually,) I get the /dev/video0 device but I don't seem to be able to use the device...
Why a second camera? I'm thinking I can use my G Tab in my car with a USB camera connected for a Baby Cam (since the baby faces the other way so I can't see and most of my traveling is at night so the normal mirror won't work unless I blind the poor child...) -- In theory, it could be used as a backup camera as well. (Same effect)
The internal camera works, but I don't need to see myself, I'd rather see something behind me.
Ideas?
I've scoured the Forums in more detail... Several ask the questions and someone made it work on the Nook, but it looked Nook specific. =/
Is there a more appropriate place to ask? This would affect all Android Devices that have a USB Host Port...
Now, the G Tablet, VEGAn mod at least... has the UVC Driver for WebCams. When I plug a camera in I get the /dev/video0 device (which doesn't exist until I plug in a camera.) - could it be permissions or is the driver not fully implemented?
The mplayer app that was released sets the root path to /sdcard so I can't point it at /dev/video0... I've tried to use the stream part, but it just exits the video - no error that I can see...
adamsoutherland said:
Now, the G Tablet, VEGAn mod at least... has the UVC Driver for WebCams. When I plug a camera in I get the /dev/video0 device (which doesn't exist until I plug in a camera.) - could it be permissions or is the driver not fully implemented?
Click to expand...
Click to collapse
The device appearing is a good first sign. Can you get me a dmesg output after you've plugged the webcam in? Run a Terminal Emulator app, then type in the window:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
The mplayer app that was released sets the root path to /sdcard so I can't point it at /dev/video0... I've tried to use the stream part, but it just exits the video - no error that I can see...
Click to expand...
Click to collapse
Is this app an Android port of the standard mplayer for Linux? If yes, then it will use the V4L (Video 4 Linux) API to grab video frames, and if you can start it on the command line (or supply an input file name), then you can try "tv://" as the input file name.
Run this command first, though, to give everybody read-write access to /dev/video0:
Code:
$ [B]su[/B]
# [B]chmod 666 /dev/video0[/B]
I'm attaching a dmesg prior to plugging in the camera, and one after... I'm also inserting the text of the "diff" in the post...
Code:
[ 189.574313] usb 1-1.1: new high speed USB device using tegra-ehci and address 3
[ 189.657223] usb 1-1.1: New USB device found, idVendor=18ec, idProduct=3299
[ 189.664506] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 189.671944] usb 1-1.1: Product: USB2.0 PC CAMERA
[ 189.677125] usb 1-1.1: Manufacturer: ARKMICRO
[ 189.685907] usb 1-1.1: configuration #1 chosen from 1 choice
[ 189.695760] uvcvideo: Found UVC 1.00 device USB2.0 PC CAMERA (18ec:3299)
[ 189.708989] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
[ 189.732392] input: USB2.0 PC CAMERA as /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1/1-1.1:1.0/input/input7
[ 190.318832] SO340010: gpio_val=0xc0a50000, button_val = 0xdbaf0002
[ 190.445387] SO340010: gpio_val=0xc0a50000, button_val = 0xdbaf0000
and this:
Code:
/data/data/berserker.android.apps.sshdroid/home # ls -lh /dev/vid*
crw-rw---- 1 0 1006 81, 0 Sep 2 18:22 /dev/video0
I've also done this:
Code:
/data/data/berserker.android.apps.sshdroid/home # chmod 666 /dev/video0
/data/data/berserker.android.apps.sshdroid/home # cat /dev/video0 /mnt/sdcard/test.mpg
cat: read error: No such device
/data/data/berserker.android.apps.sshdroid/home # ls -lh /dev/vid*
crw-rw-rw- 1 0 1006 81, 0 Sep 2 18:22 /dev/video0
/data/data/berserker.android.apps.sshdroid/home #
The mplayer was an APK from someone on the forums... I've opened it up only to find a "mplayer.so" as I thought it might contain the mplayer binary... (I don't have a machine (with sufficient space) to load the Android SDK at the moment...) (It's on my todo list.)
Am I right to try "cat /dev/video0" before I find the proper mplayer or event ffmpeg binary? (It generally works in linux when I do it...)
PS - I have 3 WebCams, I can give you a dmesg of each one if you need it... They all appear to do the same thing (they are by different manufacturers... iMicro, Sabrent and Agama.) -- also note that these 3 web cams work in Linux (each slightly different, but they work.)
adamsoutherland said:
The mplayer was an APK from someone on the forums... I've opened it up only to find a "mplayer.so" as I thought it might contain the mplayer binary... (I don't have a machine (with sufficient space) to load the Android SDK at the moment...) (It's on my todo list.)
Click to expand...
Click to collapse
Attach the APK so I can have a look at it.
Am I right to try "cat /dev/video0" before I find the proper mplayer or event ffmpeg binary? (It generally works in linux when I do it...)
Click to expand...
Click to collapse
I'm surprised that that works even on standard Linux! You have to setup the frame capture parameters first using ioctl()s before you can start reading data from /dev/video0. Even after that, you get raw frame data, and not mpeg video from the device.
PS - I have 3 WebCams, I can give you a dmesg of each one if you need it... They all appear to do the same thing (they are by different manufacturers... iMicro, Sabrent and Agama.) -- also note that these 3 web cams work in Linux (each slightly different, but they work.)
Click to expand...
Click to collapse
Attach all the 3 webcams to your desktop machine, check that each one works and get me a dmesg and a lsmod command output for each one. I want to see what drivers are loaded for each one. We'll have to load the same drivers on the gTablet too after compiling them.
Code:
[I]Attach Camera1 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg1.txt[/B]
desktop$ [B]lsmod > lsmod1.txt[/B]
[I]Attach Camera2 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg2.txt[/B]
desktop$ [B]lsmod > lsmod2.txt[/B]
[I]Attach Camera3 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg3.txt[/B]
desktop$ [B]lsmod > lsmod3.txt[/B]
Caveats: Even if we get all the drivers to load on the gTablet (the V4L drivers, the main camera driver, and, possibly, its support drivers), we still have the problem of displaying the video stream on Android. While I'm happy to write whatever systems code is required, writing the Java UI code for the Android app is beyond my ken. We'll have to ask someone else (try in the main Android development forums on XDA, or, ask user herbert1 here who's helped out before with custom Java apps) once we've checked that we can read data from the V4L device (I'll send you a test prog which'll output .jpg files once every second once we have the drivers sorted out).
It would be great if someone has already ported mplayer for Android.
I'm attaching the APK I found...
Side note:
After looking deeper at 'cat /dev/video0'; it does not work with these webcams... I think this works on my TV Cards that natively displayed mpeg2 video (it's been a while).
See the attached dmesg-*.txt and lsmod-*.txt. Each is named after the company logo on the camera. (I can get the model numbers if the dmesg isn't enough.) Between each dmesg I rebooted the linux box for clarity. (They can all work at once, but I get confused on what is doing what.)
The command I used to test:
Code:
ffmpeg -f alsa -i hw:0,0 -f video4linux2 -s 320x240 -i /dev/video0 test-agama.mpg
(Each of these cameras has audio - The audio is not important for what I am attempting to do...)
About the UI... I've been avoiding this but it maybe time to start work on this =P -- I just realized that the box I'm testing the cameras on has space... I may have to reload linux for 64bit but then I can install the Android SDK and get to UI Development.
All three webcams seem to depend on only 3 kernel modules: uvcvideo, videodev and v4l1_compat.
If all 3 drivers are loaded on the gTablet too, then we should be able to get the video frames from /dev/video0 (or whatever the device).
I'll send you a test program this evening. In the mean time...:
That .apk file contains the application too--the classes.dex file contains the Dalvik executable bytecode. Just install the .apk, then run the app and provide a file name as input. Try "tv://" as the file name once all 3 drivers have been loaded. Do the "chmod 666 /dev/video0" before running the app.
Try the webcam test program in the attachment. The program reads from a user-specified V4L device and outputs JPEG images until you stop it with CTRL-C. Run as:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]mkdir /mnt/sdcard/tmp[/B] [I]Make a tmp dir. for storing imgs[/I]
# [B]./webcam -o /mnt/sdcard/tmp[/B] [I]Capture webcam images until stopped with CTRL-C[/I]
Get usage instructions with "./webcam --help".
EDIT: I actually didn't test the program out because I couldn't locate my webcam. Report if you encounter any bugs.
Quick Update:
I will be trying this tonight... I've been busy trying to get things done. (Little one is going to be born tomorrow!)
Sorry I haven't been able to respond sooner...
rajeevvp said:
Try the webcam test program in the attachment. The program reads from a user-specified V4L device and outputs JPEG images until you stop it with CTRL-C. Run as:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]mkdir /mnt/sdcard/tmp[/B] [I]Make a tmp dir. for storing imgs[/I]
# [B]./webcam -o /mnt/sdcard/tmp[/B] [I]Capture webcam images until stopped with CTRL-C[/I]
Get usage instructions with "./webcam --help".
EDIT: I actually didn't test the program out because I couldn't locate my webcam. Report if you encounter any bugs.
Click to expand...
Click to collapse
I copied it to /mnt/asec (because I can execute things there without remount)
When I run it, i get:
Code:
/mnt/asec # ./webcam -o /mnt/asec/tmp -d /dev/video0
./webcam: error getting video channel info. Invalid argument
I tried without the -d /dev/video0 and got the same result.
(Sorry for the LOOONG delay... Turns out a newborn takes more time and energy than I expected. I'm just now figuring that out... =P It's worth it though.)
Try this simple USB Webcam test app in the attachment which works on VEGAn-Tab 7.1 and GtabComb* (which have the pershoot kernel).
1. Plug the USB webcam in.
Assuming the kernel you're running has the correct USB webcam drivers compiled in--and, most of them do seem to have the V4L subsystem and the UVC camera drivers (which supports a lot of the common USB webcams) built into the kernel--you should see a new /dev/video0 device file pop up.
2. Run these commands to set correct permissions and owners on the device file (some ROMs--eg. GtabCombOver--don't need it):
Code:
$ [B]su[/B]
# [B]chown system.camera /dev/video0[/B]
# [B]chmod 660 /dev/video0[/B]
(Note that if you unplug and replug the webcam, you'll have to re-run the commands on ROMs which don't set the correct permissions and owners.)
3. Now install and run the SimpleWebCam app.
If, for some reason, no /dev/video0 device is created, then your webcam may need different device drivers, which have not been compiled in (or not been written!), in which case you'll have to compile a new kernel with the correct drivers either built-in or as loadable modules. Nothing else described in this post will need change.
adamsoutherland said:
When I run it, i get:
Code:
/mnt/asec # ./webcam -o /mnt/asec/tmp -d /dev/video0
./webcam: error getting video channel info. Invalid argument
I tried without the -d /dev/video0 and got the same result.
Click to expand...
Click to collapse
Looks like I'll have to update the code to make the program use the V4L2 API instead.
Nexus 7
Just tested this on my Google Nexus 7 tablet and it worked fine, I didn't have to modify the permissions either,
PS, it is rooted, of sure if that makes much difference, will test it on my friends stock nexus 7 tomorrow
USB Camera App
I was able to get the app working on my rooted Nexus 7 4.2 and an unrooted Galaxy SIII . How hard would it be to add a video record function to the app?
droidoso said:
How hard would it be to add a video record function to the app?
Click to expand...
Click to collapse
If you want to do that, then it's better to compile a custom native camera-interface library which makes the USB webcam appear as a standard camera (--the rear one, usually). Then, you can use the standard apps to record videos.
See this thread for a precompiled binary and for the source.
Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!
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
Dear all,
I installed Unbuntu Touch on my Nexus 4 yesterday (18.09.2013, with the build 20130917.1). It is working more or less, as expected :silly:
One of the problem I am facing is that the ssh server is not working. I could install (and --reinstall) it without problem (apt-get install openssh-server ssh), but if I check with "ps -ef|grep ssh") I only see the ssh-agent and the connection from another computer is not working.
Any idea?
Best regards,
Pierre
[email protected]:/# apt-get install --reinstall openssh-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/231 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 38659 files and directories currently installed.)
Preparing to replace openssh-server 1:6.2p2-6 (using .../openssh-server_1%3a6.2p2-6_armhf.deb) ...
Unpacking replacement openssh-server ...
Processing triggers for ureadahead ...
Processing triggers for ufw ...
WARN: / is world writable!
WARN: / is group writable!
Setting up openssh-server (1:6.2p2-6) ...
[email protected]:/#
[email protected]:~$ ssh [email protected]
ssh: connect to host 192.168.1.69 port 22: No route to host
[email protected]:/home/phablet/Downloads# ps -ef | grep ssh
phablet 739 711 0 09:11 ? 00:00:00 ssh-agent
I just noticed that I have the same problem...
If I had time I would look at it, too, but right now I have other things to do...
To98 said:
I just noticed that I have the same problem...
If I had time I would look at it, too, but right now I have other things to do...
Click to expand...
Click to collapse
Same problem here. ssh to another device is possible, but no acces to phablet.
Same In GNex
try
sudo service ssh start
(if you are root or not you must use sudo)
but it does not automatically start when reboot
Still not wokring
[email protected]:/# service ssh start
ssh start/running, process 5890
[email protected]:~$ ssh [email protected]
ssh: connect to host 192.168.1.69 port 22: No route to host
[email protected]:~$ ps -ef|grep 5890
vmalep 12613 12544 0 13:00 pts/4 00:00:00 grep --color=auto 5890
chaoskernel said:
try
sudo service ssh start
(if you are root or not you must use sudo)
but it does not automatically start when reboot
Click to expand...
Click to collapse
thank you! installed version 57 and used
sudo service ssh start
work fine!