I am trying to have a serial port opened between my linux mint PC and my gnex (on cyanogen mod) so I can have a gps working with my PC.
The problem is that I only have A2DP and network access point avaliable on blueman.
Typing the command "sdptool records bc:85:1f:a6:d4:62" gives me this, if it can help:
Code:
Service Name: BlueNMEA
Service RecHandle: 0x10009
Service Class ID List:
UUID 128: 00001101-0000-1000-8000-00805f9b34fb
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
Related
Hi there
My IP adress keeps on changing on my Android (Cyanogen 6.1.1) Desire and so I keep on hopping between different IP addresses. The IP adress of the only other system on my network has not changed.
I would prefer not to use a static address but to understand and fix the cause of this. I have a laptop which does'nt hop around so frequently so
I think it must be related to a phone/Android setting but so far i've been unable to find out where this is configured.
My link speed is 54 Mbps so I have a good connection to my wireless router.
How can I fix this ? Perhaps I just need to install an extra application.
Elixir displays the lease in binary for some reason, 10101000110000000 (86400 base 10). 86400 seconds is a lease time of 1 day.
And this is confirmed on the OS itself.
Code:
# getprop dhcp.eth0.leasetime
86400
# dhcpcd --version
dhcpcd 4.0.15
Copyright (c) 2006-2008 Roy Marples
# pgrep -lf dhcpcd
1486 /system/bin/dhcpcd -ABKL -h android_dddddddddddddddd eth0
dhcpdcd options if they are the same on Android : http://roy.marples.name/cgi-bin/man-cgi?dhcpcd
-A, --noarp
Don't request or claim the address by ARP. This also disables
IPv4LL.
-B, --nobackground
Don't run in the background when we acquire a lease. This is
mainly useful for running under the control of another process,
such as a debugger or a network manager.
-K, --nolink
Don't receive link messages for carrier status. You should only
have to use this with buggy device drivers or running dhcpcd
through a network manager.
-L, --noipv4ll
Don't use IPv4LL (aka APIPA, aka Bonjour, aka ZeroConf).
I was having problems getting adb to recognize my Galaxy Nexus LTE when it was connected to OS X. It worked fine from Linux w/ the correct udev rules. I eventually tracked it down by comparing the vendor IDs I was using in Linux w/ the vendor ID I was seeing in OS X. The vendor ID in OS X was showing up as 0x15eb instead of 0x04e8. The only difference between the two was that in Linux it was directly connected to the computer through the internal hub. In OS X it was connected via a powered external hub. So I removed the hub and connected the device directly. Is this configuration is shows up with the correct vendor ID and adb works fine. I know different IDs are used at different points, eg fastboot/recovery vs. fully booted.
My question is - why am I seeing different vendor IDs when it is connected via an internal hub vs. an external hub?
That Device ID is the USB hub's id.
ADB won't work if you connect your phone to some USB hubs.
Thanks. But it doesn't look like the ID is the hubs product or vendor ID. It seems like the phone is presenting itself as a different gadget. The vendor ID when plugged into the external hub seems to match that of a modem or serial connection.
Below is the info when connected to the external hub:
USB 2.0 Hub:
Product ID: 0x0101
Vendor ID: 0x1a40 (TERMINUS TECHNOLOGY INC.)
Version: 1.11
Speed: Up to 480 Mb/sec
Location ID: 0xfd120000 / 5
Current Available (mA): 500
Current Required (mA): 100
CDS7:
Product ID: 0x0001
Vendor ID: 0x15eb
Version: 0.00
Speed: Up to 12 Mb/sec
Manufacturer: VIA Telecom
Location ID: 0xfd124000 / 7
Current Available (mA): 500
Current Required (mA): 0
=====
Here is the same info with no external hub:
Hub:
Product ID: 0x2513
Vendor ID: 0x0424 (SMSC)
Version: b.b3
Speed: Up to 480 Mb/sec
Location ID: 0xfd100000 / 2
Current Available (mA): 500
Current Required (mA): 2
Full:
Product ID: 0x6860
Vendor ID: 0x04e8 (Samsung Electronics Co., Ltd.)
Version: 2.16
Serial Number: 0149A4481500400A
Speed: Up to 480 Mb/sec
Manufacturer: unknown
Location ID: 0xfd120000 / 5
Current Available (mA): 500
Current Required (mA): 500
I'm guessing that the USB hub have a separate chip because your computer is not reading your phone.
Btw phones often will not get recognized by the computer if you plug it into a USB hub.
Hello
I am working directly with AT commands on my phone. For example: AT$GSM?\r for the GSM page of the FieldTest application.
I wrote a little app which call the command "AT$GSM?\r". The app is running nicely on a HTC Magic 32 B (CM 7) and a Nexus One (CM 9). Now I installed it on the CM10 on my HTC One X. But I only get the response +CME ERROR: 100.
The detailed "logcat -b radio" output is:
AT$GSM?\r
(t=1357078390)>> AT$GSM?\r
D/HTC_RIL ( 161): TX::> AT$GSM?\r
}/RILJ ( 698): [3691]< OEM_HOOK_STRINGS {UNIAT, +CME ERROR: 100
When I call the RIL through the byte commands I get the error:
< OEM_HOOK_RAW error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
At the moment I use CM9 with baseband-version: 2.1204.119.17
In FASTBOOT is the information:
RADIO-1.1204.105.14
MODEM PATH: OFF
Does anybody has an idea how to solve it?
Felix
Hi Felix,
FelixGroup said:
OEM_HOOK_STRINGS {UNIAT, +CME ERROR: 100
Click to expand...
Click to collapse
Did you ever resolve this?
CME ERROR: 100 is labelled as "unknown" in the 3GPP 27.007 docs, so it means that your script is working but perhaps that AT command/device is not enabled on that device. Usually ATCoP on Qualcomm MSM8960 can be easily customized by OEM. Since HTC love to customize everything, perhaps its a RIL thing. Many RILs can be made to "interpret" AT commands, and thus they either don't reach CP at all, and is faked by RIL in AP, or reformatted or blocked. Basically anything can happen. Did you try some other AT commands and see if something changes.
Hey boys, new OnePlus 3 user here.
Is there anyone that has any idea why I can't see the processes running on the phone via Monitor on Windows? And why I can't get Pixel Perfect to work?
I keep getting this following error:
Code:
[2016-08-11 10:55:04 - hierarchyviewer]Unable to get view server version from device 2ed6457b
[2016-08-11 10:55:04 - hierarchyviewer]Unable to get view server protocol version from device 2ed6457b
[2016-08-11 10:55:04 - ViewServerDevice]Unable to debug device: oneplus-oneplus_a3000-2ed6457b
[2016-08-11 10:55:04 - hierarchyviewer]Missing forwarded port for 2ed6457b
[2016-08-11 10:55:04 - hierarchyviewer]Unable to get the focused window from device 2ed6457b
[2016-08-11 10:55:09 - hierarchyviewer]Missing forwarded port for 2ed6457b
[2016-08-11 10:55:09 - hierarchyviewer]Unable to load window data for window <Focused Window> on device 2ed6457b
[2016-08-11 10:55:09 - hierarchyviewer]null
Any ideas?
Hello,
I'm using the Capsule app to establish a VPN connection into my employers's network, the authentication is done via certificates.
My environment:
Device: Fairphone 2
Recovery: TWRP
OS: LineageOS 14.1 (Android 7.1.2)
LineageOS-Version:
14.1-20180213-NIGHTLY-FP2 --> last version VPN connection works14.1-20180220-NIGHTLY-FP2 --> first version VPN connection does not works anymore
Since 14.1-20180220-NIGHTLY-FP2, the VPN client throws this error message:
'failed to retrieve certificate from device store'
below you can find more details copied out of the app's logfile.
The error is reproducable:
I always did TWRP backups before installing a newer lineage version. When restoring a version older than 20.02.2018, then VPN connection works. I can install update after update, till 14.1-20180220-NIGHTLY-FP2 all works fine.
Could someone give some advice how this can be solved?
Thanks in advance.
App's log file:
03-03 23:04:38.132 11264 259 E NEMO.In Service Main:
android.security.KeyChainException: java.security.UnrecoverableKeyException: Failed to obtain information about private key
at android.security.KeyChain.getPrivateKey(KeyChain.java:390)
at com.checkpoint.VPN.Service.b(SourceFile:1156)
at com.checkpoint.VPN.Service.b(SourceFile:67)
at com.checkpoint.VPN.Service$CCCDoer.handleMessage(SourceFile:706)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.security.UnrecoverableKeyException: Failed to obtain information about private key
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePublicKeyFromKeystore(AndroidKeyStoreProvider.java:223)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStoreKeyPairFromKeystore(AndroidKeyStoreProvider.java:259)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePrivateKeyFromKeystore(AndroidKeyStoreProvider.java:269)
at android.security.KeyChain.getPrivateKey(KeyChain.java:382)
... 6 more
Caused by: android.security.KeyStoreException: Key not found
at android.security.KeyStore.getKeyStoreException(KeyStore.java:659)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePublicKeyFromKeystore(AndroidKeyStoreProvider.java:224)
... 9 more
03-03 23:04:38.137 11264 1 D NEMO.SyncController::handleMessage: got msg from service: type = CONNECT
03-03 23:04:38.138 11264 1 D NEMO.service says: CONNECT Failure: error_msg: 'failed to retrieve certificate from device store', error_code: '-1'
03-03 23:04:38.138 11264 1 D NEMO.In Connecting task activity:nCCCError(): failed to retrieve certificate from device store