Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19
Like Tree1Likes

Thread: Lexus IS250 Android integration using iVIC and ODROID U3

  1. #11
    Newbie focused's Avatar
    Join Date
    May 2014
    Location
    Canada
    Posts
    19
    Quote Originally Posted by kevinkga View Post

    You were right Focussed, delivery is rather quick! However, our customs had a surprise for me too. Seems like customs charged me an additional GBP28 for it. Bummer! Hopefully I'll have it by tonight when I get home
    Sounds about right. I had to pay some brokerage as well from Hardkernel. For my project the brokerage and shipping accounted for $149.60CAD, 24.6% of the project. Probably a useful thing to know for people who are pricing things out. Very exciting though, the Odroid is a lot of fun!

  2. #12
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    So I finally received the ODROID and here are some unboxing pics:
    Attached Images Attached Images      

  3. #13
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    I was very curious about the hardware and chipsets available on this device, so I installed the dual booting image for linux and android. Here's what I did (on linux):

    #download the zipped image file
    wget http://www.odroid.in/mirror/dn.odroi...140315.img.zip
    #unzip the file to reveal the image
    unzip xubuntu-13.10-desktop-armhf_android_odroidu_20140315.img.zip
    #do a raw write to the chip using the linux dd command and specifying 4M block size
    sudo dd if=xubuntu-13.10-desktop-armhf_android_odroidu_20140315.img of=/dev/sdb bs=4M
    sudo sync

    NOTE: that /dev/sdb is the Usb Card Reader to which I attached my eMMC module to. This might vary on different systems and should be used with extreme care otherwise you risk overwriting data such as your OS!

    Hardkernel provided an eMMC to MicroSD adaptor with the purchase of the eMMC module. You basically take off the eMMC module from the ODROID, press it onto the MicroSD adaptor, put the MicroSD adaptor into a (USB) MicroSD reader/writer and stick that MicroSD reader/writer into your PC's USB port. It turned out to be very handy for updating images. Once the image was written, I just took the eMMC chip and placed it under the ODROID U3 in its socket. Voila! New OS!

    Power on the device and it boots into an ncurses a config mode, where you can set the HDMI output modes, SSH-on-boot etc. Very easy and convenient stuff. Once done, it boots straight into Xubuntu.

    This video shows how to perform the actual dual boot afterwards: https://www.youtube.com/watch?v=4FTQgpalAqY
    In short (btw the root password is 'odroid'):
    odroid@odroid:/media/boot$ sudo su
    [sudo] password for odroid:
    root@odroid:/media/boot# cd /media/boot/
    root@odroid:/media/boot# mv boot.ini.android boot.ini
    root@odroid:/media/boot# mv boot.scr boot.scr.ubuntu
    root@odroid:/media/boot# sync
    root@odroid:/media/boot# reboot
    Attached Images Attached Images    
    Last edited by kevinkga; 07-12-2014 at 09:52 AM.

  4. #14
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    So here are some commands that I ran to get more info about the unit

    odroid@odroid:~$ uname -a
    Linux odroid 3.8.13.16 #1 SMP PREEMPT Tue Feb 11 10:47:21 BRST 2014 armv7l armv7l armv7l GNU/Linux
    odroid@odroid:~$ lspci
    pcilib: Cannot open /proc/bus/pci
    lspci: Cannot find any working access method.
    odroid@odroid:~$ lsusb
    Bus 001 Device 006: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
    Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 003: ID 0424:3503 Standard Microsystems Corp.
    Bus 001 Device 002: ID 0424:9730 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    odroid@odroid:~$ lsmod
    Module Size Used by
    fuse 65473 2
    ipt_MASQUERADE 1693 1
    iptable_nat 2485 1
    nf_conntrack_ipv4 13029 1
    nf_defrag_ipv4 1231 1 nf_conntrack_ipv4
    nf_nat_ipv4 3444 1 iptable_nat
    nf_nat 14753 3 ipt_MASQUERADE,nf_nat_ipv4,iptable_nat
    nf_conntrack 65240 5 ipt_MASQUERADE,nf_nat,nf_nat_ipv4,iptable_nat,nf_c onntrack_ipv4
    ip_tables 11486 1 iptable_nat
    x_tables 15172 2 ip_tables,ipt_MASQUERADE
    bridge 81191 0
    stp 1882 1 bridge
    llc 4842 2 stp,bridge
    rfcomm 31784 16
    btusb 12824 0
    bnep 10808 2
    bluetooth 197870 22 bnep,btusb,rfcomm
    mousedev 10060 0
    ipv6 269175 55 bridge
    joydev 8724 0
    smsc95xx 19090 0
    usbnet 19464 1 smsc95xx
    hid_logitech_dj 10725 0
    rtl8192cu 522755 0
    gpio_keys 7062 0
    vfat 9124 1
    fat 49103 1 vfat

    Note that the USB logitech receiver is just my keyboard/mouse receiver.

    Name:  wifi32.jpg
Views: 230
Size:  53.2 KB
    The wifi adaptor uses the RTL8188CUS chip and rtl8192cu kernel module:
    Bus 001 Device 006: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x0bda Realtek Semiconductor Corp.
    idProduct 0x8176 RTL8188CUS 802.11n WLAN Adapter
    bcdDevice 2.00
    iManufacturer 1
    iProduct 2
    iSerial 3
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 46
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
    (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 4
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 255 Vendor Specific Subclass
    bInterfaceProtocol 255 Vendor Specific Protocol
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x84 EP 4 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 1

    Name:  201206301836543944.jpg
Views: 230
Size:  46.6 KB
    Here is some more info about the USB Bluetooth adapter:
    Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 224 Wireless
    bDeviceSubClass 1 Radio Frequency
    bDeviceProtocol 1 Bluetooth
    bMaxPacketSize0 64
    idVendor 0x0a12 Cambridge Silicon Radio, Ltd
    idProduct 0x0001 Bluetooth Dongle (HCI mode)
    bcdDevice 19.58
    iManufacturer 0
    iProduct 0
    iSerial 0
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 177
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 3
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0010 1x 16 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x82 EP 2 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0000 1x 0 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0000 1x 0 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 1
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0009 1x 9 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0009 1x 9 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 2
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0011 1x 17 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0011 1x 17 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 3
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0019 1x 25 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0019 1x 25 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 4
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0021 1x 33 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0021 1x 33 bytes
    bInterval 1
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 5
    bNumEndpoints 2
    bInterfaceClass 224 Wireless
    bInterfaceSubClass 1 Radio Frequency
    bInterfaceProtocol 1 Bluetooth
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x03 EP 3 OUT
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0031 1x 49 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 1
    Transfer Type Isochronous
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0031 1x 49 bytes
    bInterval 1
    Last edited by kevinkga; 07-12-2014 at 09:23 AM.

  5. #15
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    I also received the GPS board today. It's a Sure Electronics Bluetooth, USB and Serial GPS device (mine is GP-GS009V430)
    Name:  IMAG0190.jpg
Views: 231
Size:  279.5 KB
    Happy to find out that it's actually recognized as a COM port as I had originally suspected.
    Opening /dev/ttyUSB0 showed me some GPS data, which is great news!
    odroid@odroid:~$ cat /dev/ttyUSB0

    It seems to be handled by these modules:
    Module Size Used by
    cp210x 8163 0
    usbserial 23409 1 cp210x

    Bus 001 Device 007: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x10c4 Cygnal Integrated Products, Inc.
    idProduct 0xea60 CP210x UART Bridge / myAVR mySmartUSB light
    bcdDevice 1.00
    iManufacturer 1
    iProduct 2
    iSerial 3
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
    (Bus Powered)
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 0
    bInterfaceProtocol 0
    iInterface 2
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x01 EP 1 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 0
    Last edited by kevinkga; 08-02-2014 at 08:07 AM.

  6. #16
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    So after the reporting on the hardware and drivers in linux, I was happy to reboot the system into Android mode.

    The next step was to install GAPPS (Google Apps e.g. Google play etc). To do this I opened this APK from the android browser: http://dn.odroid.com/GAPPS/GAppsInstaller_jellybean.apk

  7. #17
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    Some of the apps that I use (Sygic Fleet) more specifically cannot work through the Android Mock Location APIs, which is what Bluetooth GPS uses. Therefore, a more native wired solution seemed a good idea. Here's how I figured it out:

    1. So as I mentioned before, my GPS board supports both BT and USB. BT seemed out of the question due to the way it uses mock locations and how that caused Sygic to simply crash.
    2. I went ahead and connected my GPS board to the ODROID U3, running HardKernel Stock 4.1.2 and noticed that it was handled by the cp21x module (good so far) and that it created the device node /dev/ttyUSB0 (great).
    root@android:/ # ls -l /dev/ttyUSB0
    crw-rw-rw- gps gps 188, 0 2000-01-01 01:16 ttyUSB0
    3. I was feeling even more confident when I realised that the system had even recognised that it was a GPS device, having assigned permissions to user "gps:gps" (even better!).
    4. Then I did a cat on /dev/ttyUSB0 and .... NOTHING!
    5. ..until the moment where a light went on in my mind and I realised that serial ports could be quirky and needed to be initialized properly. So I did this:
    root@android:/ # stty -F /dev/ttyUSB0
    speed 115200 baud; line = 0;
    intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
    eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
    werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
    -brkint igncr -icrnl ixoff -imaxbel
    -onlcr
    -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke
    6. Problem solved in one command. The solution was to set the baud rate to 9600, as specified by the device. However, depending on the driver module or config, this can often be set to something else as was the case. The fix was as simple as:
    stty -F /dev/ttyUSB0 9600
    and voila! Issue solved!

    Now cat /dev/ttyUSB0 is giving me valid nmea data:
    root@android:/ # cat /dev/ttyUSB0
    $GPGGA,221020.000,5122.4293,N,00006.8644,W,2,9,0.8 9,13.4,M,47.0,M,0000,0000*73
    $GPGLL,5122.4293,N,00006.8644,W,221020.000,A,D*4D
    $GPGSA,A,3,01,20,04,32,31,12,11,13,06,,,,1.54,0.89 ,1.25*06
    $GPGSV,4,1,14,20,73,078,33,04,73,272,23,23,61,169, 21,17,43,248,*72
    $GPGSV,4,2,14,01,37,136,19,13,36,191,26,32,30,076, 38,06,29,303,18*75
    $GPGSV,4,3,14,31,22,052,37,11,12,148,15,40,12,118, 28,12,06,334,20*76
    $GPGSV,4,4,14,10,06,262,,25,02,007,26*7B
    $GPRMC,221020.000,A,5122.4293,N,00006.8644,W,0.00, 306.77,310714,,,D*7F
    $GPVTG,306.77,T,,M,0.00,N,0.00,K,D*3D
    $GPGGA,221021.000,5122.4293,N,00006.8644,W,2,10,0. 89,13.4,M,47.0,M,0000,0000*4A
    $GPGLL,5122.4293,N,00006.8644,W,221021.000,A,D*4C
    $GPGSA,A,3,01,20,04,32,31,12,23,11,13,06,,,1.48,0. 89,1.19*05
    $GPGSV,4,1,14,20,73,078,33,04,73,272,23,23,61,169, 21,17,43,248,*72

    and the cherry on the cake for tonight is that Sygic fleet works flawlessly with the new USB GPS device enabled. I just need to figure out how to make sure the baud rate doesn't change, but that's fairly trivial.

    Bottom-line is that the 4.1.2 image does indeed support USB GPS!

  8. #18
    Newbie
    Join Date
    Sep 2009
    Location
    London
    Posts
    32
    I realised that the ODROID wifi dongle was a bit too bulky for my needs. However, my other WIFI dongles were not recognised by the system when I tried them. Looking at the previous lsusb data it seemed like the ODROID WIFI dongle uses a RTL8188CUS. Therefore, in theory, any other dongle with the same chip should work. Some google revealed this as a potential replacement candidate: http://www.amazon.co.uk/Edimax-EW-78.../dp/B003MTTJOY.

    Just got it today and it works flawlessly (so far). Good thing I got two of them.

  9. #19
    Mo' Programming Mo' Problems
    Auto Apps:loading...
    Sonicxtacy02's Avatar
    Join Date
    Sep 2004
    Location
    Woodbridge, VA
    Posts
    8,168
    Blog Entries
    51
    following your work. Love to see the ODROIDs here on the forum

    btw, moving this to the worklog section. Show off is for completed projects
    kevinkga likes this.
    mp3Car.com Senior Tech Blogger (Want a product reviewed? Contact me.)
    Find my plugins on the MP3Car App Store!
    Follow Me on Twitter or Facebook
    Live mp3Car Facebook Chat

Page 2 of 2 FirstFirst 12

Similar Threads

  1. 2004 Ford Focus ZTS and Odroid U3
    By focused in forum Worklogs
    Replies: 14
    Last Post: 08-16-2014, 07:28 AM
  2. ACUI: Android Integration into your car!!
    By ACUI in forum Software & Software Development
    Replies: 4
    Last Post: 07-25-2014, 06:52 PM
  3. What are my options for running raspberrypi/odroid 24/7?
    By Vadim Osovski in forum Power Supplies
    Replies: 0
    Last Post: 12-14-2013, 11:06 PM
  4. Replies: 14
    Last Post: 07-28-2012, 01:20 PM
  5. Lenovo S10-3t in my IS250
    By n3w813 in forum Show off your project
    Replies: 9
    Last Post: 12-15-2010, 03:09 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •