pairing Dock with Computer - Nexus One Accessories

Any idea how the dock closes itself for non-nexus ones?
mac address filter? secret handshake?
anyone managed to scan it yet?
*edit*
just ocurred to me that the dock might enter Visible mode only during pairing. so i removed the pairing on the phone. put it into the dock, and voila. the dock is visible for a short while. i could get this info:
$ hcitool scan --class --info
Scanning ...
BD Address: 00:17:53:16:3X:XX [mode 1, clkoffset 0x5d50]
Device name: Nexus One Desk Dock
Device class: Audio/Video, Hands-free (0x240408)
BD Address: 00:23:76:E5:0X:XX [mode 1, clkoffset 0x40f6]
Device name: gcb-n1 [cached]
Device class: Phone, Smart phone (0x58020c)
Maybe now i can start to simulate the nexus one on the computer ...if it's just a case of simple mac address filtering. If it's secret handshake than i'm screwed.

Any luck with this?
I'm trying to figure out how to initiate pairing from Mac OS X.

update
looking at the source code, the dock pairs with it using the onewire talk via the 3rd metal connector.
damn idiotic 'solutions' for problems that doesn't exist!

Related

Bluetooth serial port? OBD2 device on android

Hi,
Since a few days im a proud owner of a HTC desire.
On this device i am trying to connect my bluetooth OBD2 car diagnose device.
Unfortunatly i cannot get it working.
What i did was search for the device in bluetooth settings, pair it with the phone (The bluetooth device says paired, but disconnected), and change the settings in the obd2 app to make sure it uses the device ( i tried torque and obd2 reader). This will result in the following bluetooth error :
1270932653682 **** OBD Comms thread starting ****
1270932653682 **** Connecting to OBD via bluetooth ****
1270932653686 **** Connecting to OBD via bluetooth (1) ****
1270932654262 *** EXCEPTION:Service discovery failed ***
Service discovery failed android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:377)_ android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:201)_ org.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:305)_
The previous phone i had was a touch pro 2 running Windows mobile. I managed to use the diagnose device on this phone for a while without any issues.
What i am thinking is that i maybe miss out on a step on the android phone to get it working. This is because on my windows mobile phone i had to setup a serial port first. Could this be different in android, or am i doing something wrong?
Any help is welcome!
Anyone with ideas ?
Thanks alot!
do you need the software on the phone to run the obd2 connector? do they have that software available or is it just for data logging? the connection is there but there is no software calling for the data connection.
good luck. hopefully. the manufacturer developes or ports their software to Android
Yes you need to software to communicate with the obd2 bluetooth connector. You pair it with the phone, and then need to software to get the info.
There are currently 2 apps available, but they both fail to work. I thought it could maybe be a bug in android, but i can't seem to find any info about it.
I also expected i could have made a mistake while pairing the device to the phone, since i am only using android for a few weeks
it should be working, the only thing is that further down the debug the bluetooth stack blows up inside a native method
>>>> 1270932756398 *** EXCEPTION:Unknown error: 0 ***
>>>> Unknown error: 0 >>>> android.bluetooth.BluetoothSocket.initSocketNative(Native Method)_ >>>> android.bluetooth.BluetoothSocket.<init>(BluetoothSocket.java:142)_ android.bluetooth.BluetoothDevice.createRfcommSocketToServiceRecord(BluetoothDevice.java:715)_ g.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:303)_
I'm itching to see what the UUIDs your bluetooth device advertises
Hey ! we have spoken through email
Im trying to see how i can get the UUID of the device. I tried it with my ubuntu laptop, but couldnt find it yet.
Im using the same bluetooth device as listed on the torque website, the one with the blue sticker on the side
I have bonded the adapter with my laptop. Then setup Serial port.
I did not manage to get the UUID yet, is the info below helpfull?
[email protected]:~$ sdptool search SP
Inquiring ...
Searching for SP on 00:0D:18:B0:04:78 ...
Service Name: Dev B
Service RecHandle: 0x10002
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Yes we did talk on email, thats how I found the thread here
Yep thats fine on the bluetooth info, this is looking like a bug in androids handling of bluetooth, and it's a weird one at that.
Is your firmware a completley stock ROM for the phone? You haven't put a modified ROM onto it?
Well good to hear you at least know what is wrong.
My rom is a stock rom. This is the info from settings, software information :
Firmwareversion :
2.1-update1
Smallbandversion :
32.30.00.28U_4.05.00.11
Kernelversion :
2.6.29-97da29ed
[email protected] # 1
Build number :
1.14.405.4 CL144070 release keys
Software number :
1.15.405.4
Browserversion :
WebKit 3.1
The phone's model number is HTC Desire A8181
Do you know what the bug consists of?
Thanks again !
Sorry, I haven't replied earlier, been busy for a few days.
It's looking very much like a bluetooth stack issue on the HTC Desire. Googling a reveals a couple more grumblings with the desires bluetooth stack but nothing concrete. Unfortunately I haven't got one of the devices directly to play with to verify my assumption, so fixing it is probably not going to happen (if I am able to work around the bug at all!).
Unfortunately I'll have to say you're out of luck /for the moment/, if one of my friends aquires one (or I can reproduce it on my Nexus one if/whenever Google/Brightpoint decide to deliver it!) then I will try to reproduce the fault and to get it to work for you (from my point of view I want this to work with as many devices/vehicles as possible!!)
Ian
Is there anything i can help you with? as i also really like to use this app.
If you provide me with things to check, gather or investigate i would be happy to do so!
Hi to all
I have the same bluetooth OBD2 car diagnose device.
I am trying to pair it with wm 6.5 HTC HD but it ask always for secure password for bluetooth.
Does anybody know whitch is the passcode?
Thanks
blueeyedme said:
Hi,
Since a few days im a proud owner of a HTC desire.
On this device i am trying to connect my bluetooth OBD2 car diagnose device.
Unfortunatly i cannot get it working.
What i did was search for the device in bluetooth settings, pair it with the phone (The bluetooth device says paired, but disconnected), and change the settings in the obd2 app to make sure it uses the device ( i tried torque and obd2 reader). This will result in the following bluetooth error :
1270932653682 **** OBD Comms thread starting ****
1270932653682 **** Connecting to OBD via bluetooth ****
1270932653686 **** Connecting to OBD via bluetooth (1) ****
1270932654262 *** EXCEPTION:Service discovery failed ***
Service discovery failed android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:377)_ android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:201)_ org.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:305)_
The previous phone i had was a touch pro 2 running Windows mobile. I managed to use the diagnose device on this phone for a while without any issues.
What i am thinking is that i maybe miss out on a step on the android phone to get it working. This is because on my windows mobile phone i had to setup a serial port first. Could this be different in android, or am i doing something wrong?
Any help is welcome!
Click to expand...
Click to collapse
evagelos said:
Hi to all
I have the same bluetooth OBD2 car diagnose device.
I am trying to pair it with wm 6.5 HTC HD but it ask always for secure password for bluetooth.
Does anybody know whitch is the passcode?
Thanks
Click to expand...
Click to collapse
the passcode is 1234
I have the same problem - same obd2 elm bt reader - with samsung moment (with unreleased 2.1) - the phone and CBT pair but torque keeps oin saying adapter not found .. retrying etc ...
Hi
Just to let you know I managed to sort a workaround out for torque with regards to the bluetooth problems and it is now connecting fine
dandruff1 said:
the passcode is 1234
I have the same problem - same obd2 elm bt reader - with samsung moment (with unreleased 2.1) - the phone and CBT pair but torque keeps oin saying adapter not found .. retrying etc ...
Click to expand...
Click to collapse
Thanks
The code was 1,2,3,4
I've been a android user since Sept '09 (G1/Dream) and now I recently got my X10.
I've had a Nokia 770,800, and now N810. I used a application called 'Carman' which would read a OBD2 Bluetooth unit which was connected in my car. I would simply plug it into the port under my steering wheel and it would show up easily on my Nokia. The software worked great.
There is code available, and the website for carman is: http://openbossa.indt.org/carman/
The bluetooth unit I got was this one: http://www.dealextreme.com/details.dx/sku.16921 (although mine is orange, got mine back in Dec '08)
It would be great to see this being ported over to Android. Hopefully this is helpful!
how many cm is the Height of this bt?
evagelos said:
how many cm is the Height of this bt?
Click to expand...
Click to collapse
Hmm not including the connector its about 2.5cm
Hello!
Are there any known issues with Android and bt devices? I can't seem to get my desire and a bt obd reader to pair, the phone doesn't even see it.
piemmmm said:
Hi
Just to let you know I managed to sort a workaround out for torque with regards to the bluetooth problems and it is now connecting fine
Click to expand...
Click to collapse
what did you do to get it working?
drdino said:
Hello!
Are there any known issues with Android and bt devices? I can't seem to get my desire and a bt obd reader to pair, the phone doesn't even see it.
Click to expand...
Click to collapse
yeah i've been searching for awhile and apparently HTC broke the stock bluetooth stack with some kind of proprietary settings that makes most advanced functions not work (HID, SPP, etc) it appears if you use a rom thats not sense based (like cyanogenmod) then the profiles work

Anyone know how to get Freedompop to work?

I have a galaxy tab 2 7.0 wifi version with CM 10.1 on it. I have the ubee freedom stick from freedompop. I brought the otg usb dongle but the 4g stick is not working. It turns on and the middle blue light flash and then it turns off. Anyone got it to work?
joe.stay said:
I have a galaxy tab 2 7.0 wifi version with CM 10.1 on it. I have the ubee freedom stick from freedompop. I brought the otg usb dongle but the 4g stick is not working. It turns on and the middle blue light flash and then it turns off. Anyone got it to work?
Click to expand...
Click to collapse
Okay. Update. I got it to turn on and stay on with signal bars but internet doesn't work.
Yea i need help with this too. I want to get it working on my Galaxy S4.
BTW try this: http://forum.xda-developers.com/showthread.php?t=1921928
didnt work for me terminal said no such port or somthing
I tried that link but its a no go there.
Reply to your request for help
sharpknight said:
Yea i need help with this too. I want to get it working on my Galaxy S4.
BTW try this: http://forum.xda-developers.com/showthread.php?t=1921928
didnt work for me terminal said no such port or somthing
Click to expand...
Click to collapse
Hello Sharpknight,
Although I am not a developer maybe I can help. I'll share some of my learning's with you. The Freedompop dongle I have has a feature called "Diskless Install" It initially acts like a USB Memory Stick and downloads the drivers then it is supposed to switch automatically into the 3G/4G mode and then connects to the web. Every other time it is installed it is supposed to switch back into the Memory stick mode. In case you plug it into another computer.
By the way If you try something and it doesn't work you may wish to unplug and replug the dongle as it may be in the wrong mode? You may even want to try rebooting. That may change the mode on the dongle.
First I did not see if you had rooted your S4. You must root your device before my instructions will work. If it is rooted, plug in your dongle and wait for it to lock onto the signal. You should have two or more bars that indicate the signal is being recv'd by the dongle.
Next launch the terminal mode and enter super user mode by typing "su".
At the next prompt type netcfg (note the port eth0 maybe?)
It will list all of the Mac addresses, ports and the IP addresses connected. If you can match the mac address of your dongle with what is shown in the table it is seeing the dongle.
I am not sure it conflicts but I turn off the WIFI radio also. I read somewhere that it would display the dongle connection in the system WIFI control panel although my Acer never has.
If you can see the dongle in the netcfg listing the next thing you have to do is assign the IP addr. by following these steps:
type: Ifconfig eth0 192.168.1.12 ( Can be any IP address you choose (You can type: netcfg again to confirm the Dongle is seen by the Tablet)
type: dhcpcd eth0 ( Wait for lease to complete and next prompt.)
type: setprop net.dns1 8.8.8.8 (use any dns server - I used Google's free dns server or 8.8.4.4 also Google)
Launch your favorite browser and input 192.168.14.1 (for the FreedomPop PXU1964) for the URL or what ever URL is required by your device.
The FreedomPop setup screen should appear. Click on Network about center screen and it should show how many bytes transferred.
Click on the Advanced Link and insure it's set to NAT Mode.
I hope this helps - I will be out of internet range until Monday if you send me a note when I get back I'll reply if I see another post from you.
By the way I tried to reply to your post and it says you have turned off the reply via email in your profile.
Regards,
- Phil
PBates123 said:
Hello Sharpknight,
Although I am not a developer maybe I can help. I'll share some of my learning's with you. The Freedompop dongle I have has a feature called "Diskless Install" It initially acts like a USB Memory Stick and downloads the drivers then it is supposed to switch automatically into the 3G/4G mode and then connects to the web. Every other time it is installed it is supposed to switch back into the Memory stick mode. In case you plug it into another computer.
By the way If you try something and it doesn't work you may wish to unplug and replug the dongle as it may be in the wrong mode? You may even want to try rebooting. That may change the mode on the dongle.
First I did not see if you had rooted your S4. You must root your device before my instructions will work. If it is rooted, plug in your dongle and wait for it to lock onto the signal. You should have two or more bars that indicate the signal is being recv'd by the dongle.
Next launch the terminal mode and enter super user mode by typing "su".
At the next prompt type netcfg (note the port eth0 maybe?)
It will list all of the Mac addresses, ports and the IP addresses connected. If you can match the mac address of your dongle with what is shown in the table it is seeing the dongle.
I am not sure it conflicts but I turn off the WIFI radio also. I read somewhere that it would display the dongle connection in the system WIFI control panel although my Acer never has.
If you can see the dongle in the netcfg listing the next thing you have to do is assign the IP addr. by following these steps:
type: Ifconfig eth0 192.168.1.12 ( Can be any IP address you choose (You can type: netcfg again to confirm the Dongle is seen by the Tablet)
type: dhcpcd eth0 ( Wait for lease to complete and next prompt.)
type: setprop net.dns1 8.8.8.8 (use any dns server - I used Google's free dns server or 8.8.4.4 also Google)
Launch your favorite browser and input 192.168.14.1 (for the FreedomPop PXU1964) for the URL or what ever URL is required by your device.
The FreedomPop setup screen should appear. Click on Network about center screen and it should show how many bytes transferred.
Click on the Advanced Link and insure it's set to NAT Mode.
I hope this helps - I will be out of internet range until Monday if you send me a note when I get back I'll reply if I see another post from you.
By the way I tried to reply to your post and it says you have turned off the reply via email in your profile.
Regards,
- Phil
Click to expand...
Click to collapse
Those ^ directions work. Only thing you might have to do differently is set the USB stick to NAT mode via your PC. Log in to 192.168.14.1 via your PC browser and put it into NAT mode. Then use those instructions. Worked for me on the Galaxy S4. Thanks Phil.
Awesome - Glad it worked!!
sharpknight said:
Those ^ directions work. Only thing you might have to do differently is set the USB stick to NAT mode via your PC. Log in to 192.168.14.1 via your PC browser and put it into NAT mode. Then use those instructions. Worked for me on the Galaxy S4. Thanks Phil.
Click to expand...
Click to collapse
:good:
Not working with CM10 on Nook HD+
PBates123 said:
If you can see the dongle in the netcfg listing the next thing you have to do is assign the IP addr. by following these steps:
type: Ifconfig eth0 192.168.1.12 ( Can be any IP address you choose (You can type: netcfg again to confirm the Dongle is seen by the Tablet)
type: dhcpcd eth0 ( Wait for lease to complete and next prompt.)
type: setprop net.dns1 8.8.8.8 (use any dns server - I used Google's free dns server or 8.8.4.4 also Google)
Click to expand...
Click to collapse
So, what kernel module / driver is missing if I can light up the stick and see the bare USB device, but netcfg never sees an eth0 device?
I am running CyanogenMod 10.2 on a B&N Nook HD+ (but I tried CM10.1 with exactly the same results).
Thanks in advance...
FreedomPop Dongle w/ CyanogenMod on B&N NookHD+
wanderso said:
So, what kernel module / driver is missing if I can light up the stick and see the bare USB device, but netcfg never sees an eth0 device?
I am running CyanogenMod 10.2 on a B&N Nook HD+ (but I tried CM10.1 with exactly the same results).
Thanks in advance...
Click to expand...
Click to collapse
Hello Wanderso,
I was in Dripping Springs & Austin a week ago - for the week.....
Here is a couple of things. CyanogenMod 10.1 or 10.2 should have everything you need.
1. Plug your FreedomPop dongle into a PC or laptop first and follow the instructions with the unit to put it into NAT mode. Open a browser window and type 192.168.14.1 (if my memory is correct) and go from there.
By the way FreedomPop has a couple of dongles. I have never tried this procedure with the newer dongles. But there is no reason I know of that would stop this from working on those.
2. Next in my instructions I used eth0 (thats eth zero, but could be any available port eth1, eth2, or usb0 or usb1, ect)
Also remember that every other time the Dongle is plugged in it acts like a jump drive with a start-up program on it. So if it doesn't respond when you run your script or type it in, unplug it and re-plug it and try the script again. The second time it is installed it acts like the Radio dongle and not like a jump drive. Let me know if that helps.
Good luck! - Phil
Also for a little more history and maybe a few tips check out this thread toward the bottom I documented the steps I took to get my Acer A500 working it might also help.
http://forum.xda-developers.com/showthread.php?t=1921928
PBates123 said:
I was in Dripping Springs & Austin a week ago - for the week.....
Click to expand...
Click to collapse
Phil:
Hope you enjoyed your visit to Central Texas, but you missed the great weather we are having now, and ACL :good: but come back anytime...
I've tried your entire procedure, but the issue (I believe) is a issue in the CDC and/or RNDIS drivers on the Nook HD+ (Ovation). I need some diagnostic procedures to understand what the kernel is thinking when I plug in the stick. No "eth0" or "usb0" device shows up when i plug it in, even though it is connecting to the WiMax network (as indicated by the external lights on the stick). I have set the stick to NAT mode on a PC, and have tried to plug / unplug to get it to cycle through its boot modes.
Wanderso
FreedomPop Dongle w/ CyanogenMod on B&N NookHD+
wanderso said:
Phil:
Hope you enjoyed your visit to Central Texas, but you missed the great weather we are having now, and ACL :good: but come back anytime...
I've tried your entire procedure, but the issue (I believe) is a issue in the CDC and/or RNDIS drivers on the Nook HD+ (Ovation). I need some diagnostic procedures to understand what the kernel is thinking when I plug in the stick. No "eth0" or "usb0" device shows up when i plug it in, even though it is connecting to the WiMax network (as indicated by the external lights on the stick). I have set the stick to NAT mode on a PC, and have tried to plug / unplug to get it to cycle through its boot modes.
Wanderso
Click to expand...
Click to collapse
Thanx Wanderso not sure when the next time I'll be there is.
As I am not a developer I had to spend a lot of time researching to come up with the procedure I used. I did a quick google search and found this link among others that seemed to fit the issue your having. What puzzles me with this issue is that the device should be recognized as a USB Drive initially by your Nook HD+, and it doesn't seem to do so. OH! Just had a brain flash! One of the problems many tablets have is that these Dongles draw a lot of power, sometimes more than the ports on the tablets can supply due to the radio. Can you try a powered USB port extension to see if that helps?
Here is the link I ran across in the google search: http://stackoverflow.com/questions/12974114/detection-of-plugged-in-usb-device
Could you keep me in the loop as you have me intrigued and I like to see how to solve the problem. I'll keep looking and let you know if I find anything that may help you solve the problem.. We can solve this I'm sure! :good:
Regards,
- Phil
PS. I ran across a thread with what is suspiciously like the problem I refered to the USB ports draw down the voltage and caused connection problems. check it out:
http://bookclubs.barnesandnoble.com...ce-not-recognized-resolved/td-p/813686/page/2

[Q] Non-branded Android car device - 3g modem problem

It is my first post here, so forgive me any mistakes. I'm a newbie to Android.
I've been drifting throughout the Internet and XDA-developers forum to find a solution to my problem, but I can't find it. You are my only hope. Even original support can't help. I bought a non-branded Android device for my car in April 2014, specifically this one: (happyshoppinglife[.com] / honda-civic-android-autoradio-dvd-navigation-with-dtv-wifi-3g-p-1168[.html]). Since then I can't connect to the Internet using 3G modem.
It seems to have some tailor-made Android version, since normal tablets don't have a DVD or FM radio or wheel-buttons.
Recently the manufacturer/developer upgraded the Android to a version 4.4.2 (chinabatemon [.com] / cargpss / android-update-442.rar)
Precisely it is:
Model SNT-210
Android 4.4.2-0140516-sntb-HOMEMADE
Kernel 3.0101-gdaab9de-dirty
[email protected] #9
Build omnisntb-eng 4.4.2 KOT49H eng.QDroid.20140516.133512 test-keys
iGo 9.6.7.235654-Thin1.1
Manual: autoradiodvdgpstv [.com] / user-manual / car-dvd / android-car-dvd-player-cp1.pdf
Currently I have 3g modems: Huawei E220 (VID 12d1:1003, PID 12d1:1003), Huawei K3770 (VID 12d1:14d1, PID 12d1:14c9), ZTE MF626 (VID 19d2:2000, PID 19d2:0031), Huawei E230 (VID 12d1:1003, PID 12d1:1003)
Wifi works fine, but I need 3g..
[EDIT]
I have no root access:
1|[email protected]: / $
after doing "su":
[email protected]: / $
I'm probably unable to root the device because I cannot connect to it (I got a cable: USB type A - USB type A, but it didn't work: no response from Android device nor from my laptop). After clicking "Build number" once (in the "About CarDVD" menu) it shows "No need, you are already a developer", but there are no "developer options" in the Settings menu.
There is the app "3g reconnect" already installed in the system, but after I connect a modem (E230, E220 or K3770) with working SIM (no PIN) in "Plus" (MCC 260 MNC 01) its LED is blinking green, and then blue after a while (one blink per 3-5 sec) but the system remains unchanged. The support (the Chinese via chat, not very nice experience talking: an hour waiting for response) said I .
I tried PPP Widget to help me, as well as Android Terminal and Slick USB 2 Serial Terminal.
I set PPP widget to start manually, set APN to "internet", left number to dial unchanged, no user, no password. After booting without 3g modem, PPP Widget starts and I connect the modem to a USB port. I click on the PPP icon, choose my E230 modem (12d1:1001) and I click connect. PPP Widget searches for the port and tries to connect.
When I turn on logging, portcheck.log says:
== START LOG ==
PPP Widget version 1.3.3
USB_ModeSwitch log from {date}
Raw args from udev: 1-1.1/portcheck
using top device dir /sys/bus/usb/device
SymLinkCheck called with /sys/bus/usb/ttyUSB0
My name is ttyUSB0
Checking my endpoints ...
in /sys/bus/usb/devices/1-1.1/1-1.1:1
checking ep_81 ...
ep_81 has interrupt transfer type
--> I am an interrupt port
--> No interrupt interface below me
{something was here}
== END LOG ==
When I check the Android Settings (Mobile status) there is:
Network: unknown
Signal strength: 2147483647 dBm 255 asu
Mobile network type: Unknown
Service state: Out of service
IMEI: {my SIM's IMEI}
IMEI SV: Unknown
IP address: Unavailable
WiFi MAC address: {some MAC address}
When I turn Android Terminal it goes:
lsusb:
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 05e3:0608
Bus 001 Device 003: ID 0bda:8176
Bus 001 Device 007: ID 12d1:1003
Bus 001 Device 005: ID 04e8:6860
Sometimes There is Bus 001 Device 005 instead of 007 by 12d1:1003
When I try to use Slick USB 2 Serial Terminal it connects to the modem and answers all the AT commands:
ATI
Huawei
E230
Rev. 11.104.20.00.00
IMEI...
+GCAP: +CGSM +DS +ES
AT+CSQ
15.99
AT^SYSINFO
2,3,0,5,1,,4
AT+COPS=?
(1,"Plus","PLUS","26001",0), (2,"Plus","PLUS","26001",2) ... {and other}
AT+COPS?
0,2,"26001",2
I can swich the modem's mode:
AT^U2DIAG=0
the default was AT^U2DIAG=257
After switching to AT^U2DIAG=0 the modem seems to be recognised by lsusb as 12d1:1001
I tried to connect manually:
AT+CGDCONT=1,"IP","internet"
ATD *99***1#
.. and it returned CONNECTED
but when I went back to the home screen and tried to check if there is Internet access (I turned on Chrome), there was no Internet access, but I have to revise this once more.
hi i'm italian and my english is bad, i've buy your same model but i have some problems because i've a short manual only for radio,bt,cd parts.
i want a complete manual to understand the several application infact i don't know which is the app for 3g, if is it possible to use logo of car, why when connect my phone (samsung s5) with bt when download the contacts remain in working without finish.
if i can help me, it is wonderful
thank you in advance
by
alfonso
3g problem => APN list & rooting problem
alfo79 said:
hi i'm italian and my english is bad, i've buy your same model but i have some problems because i've a short manual only for radio,bt,cd parts.
i want a complete manual to understand the several application infact i don't know which is the app for 3g, if is it possible to use logo of car, why when connect my phone (samsung s5) with bt when download the contacts remain in working without finish.
if i can help me, it is wonderful
thank you in advance
by
alfonso
Click to expand...
Click to collapse
HI, alfonso.
Answering to your questions:
1) I've had many problems, which I had to solve mysfel or using chat-support (It was not a pleasant experience, each talk lasted forever..)
2) There is no "a complete manual" for SNT-210. I can only share the one I got from Happyshoppinglife => Manual
3) Changing logo: there should be an application to do that, but in my case the user should enter a password, which was "121212" and could choose the logo for your car
4) I had the issue with downloading the contacts from my phone via BT either. I didn't resolve it, I just quit doing that (downloading contacts). The problem was probably too much records in the phonebook. But synchronising the Android's phonebook with Google Account might be a solution. But.. there is a 3g / wifi connection required, which I still don't have.
Sholud you have any more questions, don't hesitate to write.
Regarding the 3g connection problem:
I am still struggling with the 3g modem case. I found out (thanks to arnoldziq) that my 3g modem is ok (there are modem drivers in Android 4.4.2, Android finds the modem and the usb port the modem is attached to). All the problems may result from a wrong APN list in \system\etc\apns-conf.xml. In my case there is
Code:
<apn carrier="PlusGSM" mcc="260" mnc="01" apn="internet" type="default,supl" />
but it should be
Code:
<apn carrier="Plus" mcc="260" mnc="01" apn="internet" type="default,supl" />
But the next problem is - it is not editable (the device is not rooted). And I tried to root the device using a shor tutorial by an XDA user KID52 for a similar device. I connected both: the device and my laptop to a router so that both devices see each other (ping confirms that). I installed ADB ("15 seconds ADB v1.3.exe" from here) on my laptop. Then I tried to connect. In my cmd (laptop) I run:
Code:
C:\Users\Grreg>adb connect 192.168.170.3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.170.3:5555
C:\Users\Grreg>adb devices -l
List of devices attached
C:\Users\Grreg>adb tcpip 5555
error: device not found
I tried to install adbWireless.apk in the CarDVD device and run the commands again. Without chnage. I read that in order to use adb via Wifi / TCPIP you have to be connected with an USB cable. But I tried, and I can't do it - neither device noticed the connection with USB type A plug - USB type A plug cable.
A question to XDA users: is there an alternative way to root the device? Or am I doing something wrong?
Hi, thank for your assistance
now I'm having another problem, the car is connected to an external display, if I insert a USB stick containing a movie in automatic start a program to read music only, if I use an app for Android naturally from the external screen is impossible see anything ... is there a way to watch movies from usb directly with some programs of the car without using the app of android?
In fact there is a program for dvd....a program for aux in....a program for usb and a program for sd card (this last I have not used yet, infact I don't know is a program for music or movies ...I hope the second!!)
You know something about?
Scuse me for my bad english
thank you
alfo79 said:
Hi, thank for your assistance
now I'm having another problem, the car is connected to an external display, if I insert a USB stick containing a movie in automatic start a program to read music only, if I use an app for Android naturally from the external screen is impossible see anything ... is there a way to watch movies from usb directly with some programs of the car without using the app of android?
In fact there is a program for dvd....a program for aux in....a program for usb and a program for sd card (this last I have not used yet, infact I don't know is a program for music or movies ...I hope the second!!)
Click to expand...
Click to collapse
Hi,
what do you mean by "external display"? my device (youtube.com/watch?v=sEJMvUQhTJA) does not provide an option to connect an external screen - no DVI/HDMI output (maybe some AUX out, but I did not check that) - what would you need one for?
After iserting an SD card (or connecting a USB plug with SD reader or USB Flash memory) Android autimatically turns on a music app, but if you want to watch a movie, just close it and browse to the sdcard / flash using for instance "ES File Explorer File Manager" (I had it preinstalled), then when you see your file, click on it and choose an app you want to opent the file with, MX Player is one of the most popular (I had it preinstalled). is that what you needed?
i have your same software but the car device is different, i can connect an external display for person behind for example, but if i use an app of android to red movies on usb the external display doesen't receive nothing; infact if i use dvd ,or tv connet on aux ,i riceive them on external display.
Is strange that automatically device usa a program only for music fo usb or sd card....is not possible to instal a program (no app android) for use them to see movies?
I found a Russian forum where they've been discussing about this device, there is a lot of information and they are way ahead of us, the URL is
4pda dot ru/forum/index.php?showtopic=578873
you can find the latest firmwares for this device here
pan.baidu dot com/share/link?uk=1529874287&shareid=2934645460#dir/path=%2FCUSP%2FCSDVI-4.4.2[/url] ,
the Malay version always seems to be released first, and instructions on how to update can be found here
cusptech dot com/index.php?c=service

Bluetooth on Intel

This is mostly for the new Joying INTEL units.
*********************************************
OLD STUFF: aka "BlueBalls.apk"
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
**************************************************
NEW STUFF!!!!
Ok, so the thing is, even with blueballs installed, the process of tethering is somewhat... MANUAL. On both sides of the connection -- data source, typically your phone, and head unit. Wouldn't it be nice to AUTOMATE things a little bit?
While there are some guides and hackish programs that suggest that they can get this done, for instance http://forum.xda-developers.com/showthread.php?t=2574310 -- the reality is that NONE of these solutions will actually WORK, nor are they simple to configure, nor are they reliable. They are a BIG UGLY MESS.
So I decided to do it myself, in a nice, clean, self-contained Android application.
The result is the BluetoothTethering.apk attached below.
Here is description of this program;
Start up the program, and you are presented with a screen with some buttons, switches, and spinners.
FOR THE CAR RADIO SIDE:
At the top of the screen is a spinner containing a list of all paired bluetooth devices. If you select one of those devices, and hit the "CONNECT PAN" button, it will try to connect to that device as a bluetooth tethering client. If you enable the switch "Auto Connect PAN", then whenever it connects to that device (the one currently showing in the spinner), it will AUTOMATICALLY try to connect PAN. The application does NOT need to be running for this to occur, since there is a receiver registered in the application's manifest.
The next button down, "Launch Bluetooth Settings", just launches the standard Android Settings --> Bluetooth activity. This is the same as what BlueBalls does, so you don't need to install both.
FOR THE PHONE SIDE:
At the bottom, there is a button "START SERVICE", hit that button on your phone, and it should start up bluetooth tethering service.
And the switch "Auto Bluetooth Tethering", means that every time the bluetooth device turns ON, it will automatically enable bluetooth tethering. Again, it receives an intent and does the work in the background, so the application need not be open.
CAVEATS!!!
Ok, this is where the fun begins! Starting with Android version 3.1, newly installed applications are given a default state of "stopped", in which they are unable to receive any broadcast intents. In order to get the application out of the stopped state such that it can receive broadcast intents, it needs to be manually run first. A second part of this feature, is that if an application is force stopped, it is RETURNED to the "stopped" state. This becomes a problem on at least some Chinese Android car radios. In particular, it is a problem on at LEAST Joying units (possibly also others). In these units, when the car ignition is turned off, after a few minutes they go to SLEEP mode so that they don't drain the car's battery. The problem is that just before going to sleep, everything running is FORCE STOPPED, sending everything, INCLUDING BluetoothTethering.apk, into a "stopped" state, thus disabling the application's ability to receive the broadcast intent necessary in order to activate PAN!
Workaround: NOW TESTED AND VERIFIED FUNCTIONAL... provisioning the application with enhanced privileges, by installing it into /system/priv-app/, will allow it to avoid the "stopped" state, or at least allow it to receive broadcast intents regardless of that state. After all, there are many system receivers that fire as expected, even if you don't manually open the applicable application manually!
If you are going to do this (which you MUST on Joying Intel car radios, and possibly other MTCD Intel car radios), the steps are as follows;
Connect it and a laptop (with adb installed) to a common wifi network. This CAN be a hotspot running on the head unit or laptop, or even your PHONE. Just as long as they are all on the same network! Find the IP address of the head unit. If the head unit is connected to a different AP rather than hosting a hotspot, you can look in wifi --> 3dots menu --> advanced. If the head unit IS the hotspot, then look at your laptop (terminal --> ifconfig) and find ITS IP address (for example, 192.168.30.123) and change the last byte to a "1" to find the head unit's IP address, in this case, it would be 192.168.30.1.
In a terminal on the computer, run following;
Code:
adb connect <ip address of head unit>
adb push BluetoothTethering.apk /sdcard/
adb shell
$ su
# mount -o remount,rw /system
# mkdir /system/priv-app/BluetoothTethering
# cp /sdcard/BluetoothTethering.apk /system/priv-app/BluetoothTethering/
# chmod 755 /system/priv-app/BluetoothTethering
# chmod 644 /system/priv-app/BluetoothTethering/BluetoothTethering.apk
# sync
# reboot
Now the application is installed with extra privileges, so it will respond properly to the broadcasts when the unit powers back on after sleeping.
Note: This application will not currently work with a typical Android TABLET. The reason is that despite being "paired" to your phone for tethering, the two devices do not automatically establish a connection when they are in proximity. A car radio and phone DO automatically establish a connection when in proximity in order that your phone calls will be directed over bluetooth. I will be looking into whether or not there is some battery efficient mechanism for accomplishing this, but I am not hopeful.
I am also aware that the auto-tethering setting is currently limited to a selection of ONE bluetooth device. If two people share a car, this may be inadequate. My intention is to create a LIST of devices that it can try connecting to. CANNOT just try ALL devices, since obviously it would be silly to try to establish a PAN connection with your OBD dongle.
There is also a potential weakness where if the bluetooth connection is established BEFORE the PHONE has bluetooth tethering enabled, the head unit will just try once to connect PAN, fail, and give up. I intend to have it periodically retry if the connection is established to an enabled device, but PAN failed.
Going to test it this afternoon. I think it will work.....
By the way: many other settings are hidden (accounts, sync, ...). They even have a second "settings.apk" (only 1 MB)....wtf.....? A lot of overlays too (we should get rid of them)
Interesting.
I'll have to rip a few of those apart and see what is up with them.
Hopefully, I'll have my 128N2's by next week.
FYI: Brainless "Candy" at Joying is really giving me the runaround when asking her about getting into recovery. Told her even to ask their technical people for the answer.... her solution? Just wait an extra hour before responding to the email with the same nonsense "do not worry, it will not fail to boot into Android, this is our latest very much more stable"
I *really* hate dealing with chinese manufacturers.
Wonder how she's going to respond to my request for kernel source code? Probably give me a link to kernel.org....
The blueballs.apk is working.
lol anyone wanna try this on a RK3188 unit
thanks doitright..
My UL128N2 from joying in in transit. hopefully receiving it in a week. I will try this in my unit and post you the feedback:good::good:.
May be this simple app can make UL128N2 to connect to 'any brand' BT OBD2 adapter.
doitright said:
This is mostly for the new Joying INTEL units.
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
Note: It works perfectly on my Nexus 6, but I don't have a Joying INTEL head unit yet (two UL128N2's on order). It *should* be fine, unless they did something REALLY weird, in which case I have another way to issue the intent that may work.
Click to expand...
Click to collapse
masri1987 said:
lol anyone wanna try this on a RK3188 unit
Click to expand...
Click to collapse
Not even remotely the same thing.
leonkernan said:
Not even remotely the same thing.
Click to expand...
Click to collapse
I know, just don't understand why the CPU makes the native ROM different for
masri1987 said:
I know, just don't understand why the CPU makes the native ROM different for
Click to expand...
Click to collapse
The Bluetooth was a separate module on the RK boards, it's on the processor board on the Sofias.
They have completely different driver software requirements.
leonkernan said:
The Bluetooth was a separate module on the RK boards, it's on the processor board on the Sofias.
They have completely different driver software requirements.
Click to expand...
Click to collapse
Well, you know something... just because the bluetooth module is on a separate board does not mean that it is necessarily "wrong". Consider the fact that you can plug a bluetooth USB dongle into ANY normal laptop/desktop/server and have it work correctly! The thing is, there ARE a bunch of high speed ties between the SoC through to the MCU board, and we know from the fact that things like torque CAN work on the rockchip/arm/mtcX units that BT SPP profile is definitely able to make it through to the bluetooth device itself. Also the fact that WIFI works on those units supports the idea that they aren't completely broken (wifi and bluetooth are on the same physical RF chip, since they use the same spectrum and need to coordinate with each other in order to operate correctly).
What this really boils down to, is that very likely, those older arm boards *actually could* be programmed to have correctly working bluetooth.
However, there IS a difference in the software. While on the RK/arm boards, they have MODIFIED the settings/bluetooth screen to be horribly broken, on the INTEL boards, they have simply deleted the link to the settings/bluetooth activity from the main settings activity, and otherwise left it fully intact. So really, there are TWO possibilities here in just how they butchered it; (1) They added a new settings/bluetooth screen and changed the link to point to it, which could mean that the original one is actually still there UNBROKEN, or (2) They actually butchered the settings/bluetooth activity.
If they used approach (1), then this apk ***COULD ACTUALLY WORK*** on them. However, if they used approach (2), then it would definitely be necessary to build a new settings/bluetooth screen with the appropriate permissions to change bluetooth settings, and installed in the system partition (i.e., root needed).
Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
doitright said:
This is mostly for the new Joying INTEL units.
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
Note: It works perfectly on my Nexus 6, but I don't have a Joying INTEL head unit yet (two UL128N2's on order). It *should* be fine, unless they did something REALLY weird, in which case I have another way to issue the intent that may work.
Click to expand...
Click to collapse
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
hi, doitright,
error screenshot attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
aneesp said:
Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
Click to expand...
Click to collapse
@aneesp --> Use the built-in BT app to connected (first time) with your OBD device. Maybe you have to change the PIN to 0000 or 1234 to get a paired connection (use the built-in BT app to change the PIN!!!)
aneesp said:
Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
hi, doitright,
error screenshot attached.
Click to expand...
Click to collapse
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.
ok..
I will do that way and give you feed back..
doitright said:
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.
Click to expand...
Click to collapse
@doitright and @MMTK84,
you saved my day and night. It worked. I entered my BT OBD2 PIN "6789" in the Chinese "Bluetooth" application (stock) and then used blueballs.apk to pair CHX. it paired smoothly. Torque could successfully establish connection and I am very happy about this unit JY-UL135N2. BT in the unit is fully functional. simultaneous playback of BT music and OBD2 is possible. Bluetooth hardware which is on on the SOC is perfect and only chinese software interface is making the issue. Any way we got the work around for this.
Please note that I didnt go for any firmware update from JOYING to make this happen. Yesterday I received the unit shipped with factory firmware MCU Version 2016-10-31 14:30:43 JY_(NOR)_90_C9_7706_5009_CAN(GX)_Newlap.
:highfive::good::good::good::good:
doitright said:
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.
Click to expand...
Click to collapse
aneesp said:
@doitright and @MMTK84,
you saved my day and night. It worked. I entered my BT OBD2 PIN "6789" in the Chinese "Bluetooth" application (stock) and then used blueballs.apk to pair CHX. it paired smoothly. Torque could successfully establish connection and I am very happy about this unit JY-UL135N2. BT in the unit is fully functional. simultaneous playback of BT music and OBD2 is possible. Bluetooth hardware which is on on the SOC is perfect and only chinese software interface is making the issue. Any way we got the work around for this.
Please note that I didnt go for any firmware update from JOYING to make this happen. Yesterday I received the unit shipped with factory firmware MCU Version 2016-10-31 14:30:43 JY_(NOR)_90_C9_7706_5009_CAN(GX)_Newlap.
:highfive::good::good::good::good:
Click to expand...
Click to collapse
Glad to hear it!
Once I get my head units delivered (can you believe that I'm writing software to fix problems on these things before even owning one? LOL), I will look into it a bit more deeply. There is probably an intent being fired to prompt for the BT pin, but the receiver (or its registration) has probably been deleted by china.
wow... many thanks for your great support. :highfive::victory::victory:
Do you have an idea how to boot in to stock recovery of this unit. I just wanna to take a nandroid backup of the unit. I t seems I have to root the unit before doing it.
doitright said:
Glad to hear it!
Once I get my head units delivered (can you believe that I'm writing software to fix problems on these things before even owning one? LOL), I will look into it a bit more deeply. There is probably an intent being fired to prompt for the BT pin, but the receiver (or its registration) has probably been deleted by china.
Click to expand...
Click to collapse
aneesp said:
wow... many thanks for your great support. :highfive::victory::victory:
Do you have an idea how to boot in to stock recovery of this unit. I just wanna to take a nandroid backup of the unit. I t seems I have to root the unit before doing it.
Click to expand...
Click to collapse
I actually just started a thread to compile all the known methods of booting into recovery. Nothing firm on that front, however, obviously you CAN "reboot" to recovery.
Good news for you about root though! Joying Intel devices ship WITH ROOT. The only thing you need to know about it, is that it is restricted to access through ADB. So turn on adb over wifi, adb connect to the ip address of the head unit on your LAN, adb root, and adb shell. You can then issue your "reboot recovery" command.
ADB over USB should also work, but you'll need to find the place in their menus where you can control the USB mode switch, and of course, you'll need a USB-A-male to USB-A-male cable.
Hi doitright,
I followed your steps for reboot to recovery using adb over wifi. I could issue the command "reboot recovery" and unit rebooted. After few seconds showing the boot logo, the android logo screen appeared with "No command" after two seconds, No command changed to "Error!". From earlier threads, I got an idea to press power button when we get this error screen. |I did so, but nothing happened. I was little bit afraid if the device is soft bricked. But, upon pressing reset button, unit booted normally.
Any clue?
doitright said:
I actually just started a thread to compile all the known methods of booting into recovery. Nothing firm on that front, however, obviously you CAN "reboot" to recovery.
Good news for you about root though! Joying Intel devices ship WITH ROOT. The only thing you need to know about it, is that it is restricted to access through ADB. So turn on adb over wifi, adb connect to the ip address of the head unit on your LAN, adb root, and adb shell. You can then issue your "reboot recovery" command.
ADB over USB should also work, but you'll need to find the place in their menus where you can control the USB mode switch, and of course, you'll need a USB-A-male to USB-A-male cable.
Click to expand...
Click to collapse
aneesp said:
Hi doitright,
I followed your steps for reboot to recovery using adb over wifi. I could issue the command "reboot recovery" and unit rebooted. After few seconds showing the boot logo, the android logo screen appeared with "No command" after two seconds, No command changed to "Error!". From earlier threads, I got an idea to press power button when we get this error screen. |I did so, but nothing happened. I was little bit afraid if the device is soft bricked. But, upon pressing reset button, unit booted normally.
Any clue?
Click to expand...
Click to collapse
Congrats. You successfully made it into recovery. Not sure what to tell you at this point, since factory recovery is what factory recovery is.
Going from there to the regular recovery menu on MOST devices (remember that I don't have one of these yet, so I haven't been able to play with it yet) involves more than just the power button. Typically it is hold power + something like volume up. You could also try mashing on a USB keyboard and see if anything happens.

Remotely Wake-up Keyboard Dock

Hi folks,
I have a rooted TF101 that I've assigned a very important role - to act as a WiFi connected serial console to my Linux server (idea being that, if my server has no IP connectivity, I can still remotely access it by connecting through my TF101).
The set up is pretty simple:
- Rooted TF101 (KatKiss 5.1.1_030c) with keyboard dock
- Dropbear SSH daemon running (clean and tight bot of software!)
- Busybody (provides 'microcom' terminal emulation amongst other things)
- USB to RS232 Serial cable connecting to the serial port on my server
The TF101 is docked, and the USB->RS232 Serial cable is via the USB port in the keyboard dock.
It all works rather well - boot messages are streamed to the serial terminal as well as the standard Linux virtual one, and the boot process finishes with a login prompt on the serial terminal. Great!
The problem is this:
If the TF101 is *not* connected to the power supply, the keyboard Dock eventually goes to sleep, and the serial port is not available. The only way to wake it up, is to physically open the 'lid' and everything is available once again. Not exactly conducive to remote access!
This is not an issue if the TF101 is connected to the power supply, but I want to be able to switch the power supply on or off as needed in order to not ruin the batteries by having them constantly connected to the charger long-term (the easy method will be via a standard mains timer, but I'm also considering getting the TF101 to control the power supply and charge itself when the batteries drop below a set threshold)...
So, the question is: is there a method to wake the keyboard dock remotely (i.e. from the command line)?
I expect that there is, I just haven't been able to find out how...
[Additional: For some reason, there is no option to keep the keyboard dock awake under "Settings->Dock->Dock Power Mode - WakeUp tablet with key press" - The 'Dock Power Mode' section is simply not there - no idea why. Also no idea if this would resolve the issue or not...]
Looking forward to some handy solutions!

Categories

Resources