I got a shiny new bluetooth keyboard for use with my Android phone.
The right shift button actually launches the browser instead of acting like a shift button, which is very inconvenient, so I edited /system/usr/keylayout/Generic.kl and /system/usr/keylayout/qwerty.kl to change the mapping. But now it doesn't work at all (it still connects fine, and sends key stroke messages/events, but nothing shows up on screen). I must have wrecked something, but I can't find any problems with those files.
I have a little app that simply displays the information from keystrokes, and it now reports that the keyCode is KEYCODE_UNKNOWN for every key I press, but the scanCode appears to be correct.
Anybody have any ideas? Do you think I could find an error in the system log?
Thanks in advance.
p.s. Samsung Infuse 4G (SGH-I997). CyanogenMod. Android 4.1.2. No carrier. Keyboard is this: www dot ebay dot ca (then add this: /itm/170931572392)
Output from system log
This is the captured output from logcat:
D/SizeAdaptiveLayout( 446): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/SizeAdaptiveLayout( 446): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/BluetoothEventLoop( 335): Device property changed: 20:12:03:16:15:26 property: Connected value: true
I/HeadsetService(21316): Headset=false; Bluetooth=false
I/BluetoothEventLoop.cpp( 335): agent_event_filter: Received method org.bluez.Agent:Authorize
I/BluetoothEventLoop( 335): First check pass for incoming HID connection from 20:12:03:16:15:26
I/BluetoothDeviceProfileState( 335): handleIncomingConnection:6:true
D/BluetoothEventLoop( 335): onAgentAuthorize(/org/bluez/434/hci0/dev_20_12_03_16_15_26, 00001124-0000-1000-8000-00805f9b34fb) = true
D/BluetoothService( 335): allowIncomingProfileConnect: 20:12:03:16:15:26 : true : 707126680
D/BluetoothEventLoop( 335): Input Device : Name of Property is: Connected
D/CachedBluetoothDevice(20624): onProfileStateChanged: profile HID newProfileState 2
D/BluetoothInputProfileHandler( 335): InputDevice state : device: 20:12:03:16:15:26 State:0->2
D/BluetoothService( 335): CONNECTION_STATE_CHANGE: 20:12:03:16:15:26: 0 -> 2
I/BluetoothDeviceProfileState( 335): Entering ACL Connected state with: 102
D/EventHub( 335): No input device configuration file found for device 'Bluetooth Keyboard'.
E/Keyboard( 335): Could not determine key map for device 'Bluetooth Keyboard' and no default key maps were found!
I/EventHub( 335): New device: id=12, fd=54, path='/dev/input/event7', name='Bluetooth Keyboard', classes=0x80000001, configuration='', keyLayout='', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
I/InputReader( 335): Device added: id=12, name='Bluetooth Keyboard', sources=0x00000101
D/dalvikvm( 335): GC_EXPLICIT freed 1511K, 39% free 15740K/25603K, paused 5ms+13ms, total 121ms
D/SizeAdaptiveLayout( 446): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/SizeAdaptiveLayout( 446): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
I noticed a "No input device configuration file found for device". But why not?
Maybe I'll check file permissions or something...
And why is it looking for /system/usr/keychars/Generic.kcm when I'm editing /system/usr/keylayout/Generic.kl ???
magmatic said:
Maybe I'll check file permissions or something...
Click to expand...
Click to collapse
Yup, turns out the file permissions got set to 600 instead of the preferred 644. Once I fixed that everything works now.
Thanks for all your help.
Related
I'm having trouble getting the sonicwall netextender app to work on my G2.
I have tested this app on the dell streak and samsung vibrant without issues.
The log file that is generated by the app shows this:
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
11-22 11:02:54.300 D/sysHelper( 3941): Check Root Permission: Exit-Value ==> 0
11-22 11:02:54.390 I/NetExtender.nxservice( 2651): new connection accepted. socket = 12
11-22 11:02:54.390 I/NetExtender.nxservice( 2651): client try to query profiles
11-22 11:02:54.390 I/NetExtender.nxclient( 3941): start to listen the service status update.
11-22 11:03:05.819 D/NetExtender.nxclient( 3941): action button clicked
11-22 11:03:05.847 I/NetExtender.nxservice( 2651): connection thread starts
11-22 11:03:05.847 I/NetExtender.nxservice( 2651): nxcore connect triggered
11-22 11:03:05.847 I/NetExtender.nxservice( 2651): start connecting
11-22 11:03:05.929 I/NetExtender.nxservice( 2651): setStatus 1, 0
11-22 11:03:06.037 I/NetExtender.nxservice( 2651): setStatus 1, 10000
11-22 11:03:06.203 I/NetExtender.nxservice( 2651): httpsClient - getResponseHeaderStr(X-NE-message: not found
11-22 11:03:06.203 I/NetExtender.nxservice( 2651): httpsClient - getResponseHeaderStr(X-NE-rsastate: not found
11-22 11:03:06.203 I/NetExtender.nxservice( 2651): httpsClient - getResponseHeaderStr(X-NE-tfresult: not found
11-22 11:03:06.203 I/NetExtender.nxservice( 2651): httpsClient - getResponseHeaderStr(X-NE-pwdexpdays: not found
11-22 11:03:06.203 I/NetExtender.nxservice( 2651): httpsClient - getResponseHeaderStr(X-NE-maychangepwd: not found
11-22 11:03:06.257 I/NetExtender.nxservice( 2651): setStatus 1, 40000
11-22 11:03:06.297 I/NetExtender.nxservice( 2651): login success, switch to next state
11-22 11:03:06.297 I/NetExtender.nxservice( 2651): setStatus 2, 0
11-22 11:03:06.297 I/NetExtender.nxservice( 2651): Couldn't set master to hdlc discipline
11-22 11:03:06.297 I/NetExtender.nxservice( 2651): setStatus 2, 10000
11-22 11:03:06.347 I/NetExtender.nxservice( 2651): setStatus 3, 0
11-22 11:03:06.347 I/NetExtender.nxservice( 2651): setStatus 3, 10000
11-22 11:03:06.347 I/NetExtender.nxservice( 2651): setStatus 3, 20000
11-22 11:03:06.347 I/NetExtender.nxservice( 2651): detect pppd initialization
11-22 11:03:06.347 I/NetExtender.ppp( 2650): Nxhelper: start pppd main routine
11-22 11:03:06.347 E/NetExtender.ppp( 2650): Couldn't set tty to PPP discipline: Invalid argument, ppp_disc: 3
11-22 11:03:06.347 E/NetExtender.ppp( 2650): Couldn't get channel number: Invalid argument
11-22 11:03:06.347 I/NetExtender.ppp( 2650): Nxhelper: pppd hung up, notify the service
11-22 11:03:06.347 I/NetExtender.nxservice( 2651): Unable to read from the pty, error: I/O error
any help?
TIA
I am having a similar issue. The only different is i get the erro 'pppd is unable to open /dev/ppp device after the Nxhelper: start pppd main routine log entry. Is there any other resources that can provide help on thisapp?
EDIT
apparently the following command needs to be run as root (according to the log file)
mknod /dev/ppp c 108 0
but mknod is not an android command as far as i can tell
I emailed the developer ... he's working on getting a g2 for testing.
my friend just got the mytouch 4g and has the same issue ... just waiting for the developer to update now ...
nexus s
Having the exact same I/O error on my Nexus S.
Any resolution?
In quick sucession, i went through a droid-x and an HTC droid eris and both worked, so im not sure what causes the problem.
Does everyone get the same I/o error? Maybe we can compare log files from different devices to try and nail down the issue.
Strange thing is the app completes authentication and i can see my login active on the sonicwall log files, just doesnt complete the login on the device itself :/
@wroashan - it's definitely an htc issue but i guess it's extending to samsung / nexus.
@sangamc - I got an email from the developer yesterday ...
"Hi Trent,
I just wanted to give you a quick update on the NetExtender issue. I've done some testing with the G2, and at this point it looks like HTC's version of the Linux kernel may in fact not support PPP properly. I'm going to keep researching the issue. I'll let you know if and when I discover anything new.
Thanks
Mike"
That's it for my updates ... I'll post back if I hear anything
I discussed with Trent today that it may be a kernel module that is not properly built into the HTC kernel. Now, however, it is reported on the Nexus S. Very frustrating. This worked on my Dell Streak and my HTC Aria (both on AT&T). Could it be a Tmo issue?
http://www.experts-exchange.com/Sof...19.html?sfQueryTermInfo=1+"global+vpn+client"
In trying different VPN solutions, I received an error message from the OpenVPN app - "No Netfilter". OpenVPN describes the "No Netfilter" error as such:
This means that the Linux kernel on your device does not have the features (CONFIG_NETFILTER, CONFIG_IP_NF_IPTABLES and CONFIG_NETFILTER_XT_MATCH_MAC) required for tethering.
Out of curiosity, I enabled tethering on my device and attempted to use OpenVPN again; alas I was unsuccessful. The search continues...
Did anyone ever get this resolved? I'm having the same issue on a NookColor running both Froyo & CM7.
Wondering also if anyone has found a fix for this? I have run into the same issue on a HTC Thunderbolt. Works perfectly on my Droid X.
Same With HTC EVO 3D (Rogers)
I know this topic has been floating around for a while but I am getting the same I/O Error message when I try connecting with my Evo 3D. I could post a dump of the log file if needs be.
Just an update for anyone who might stumble across this thread looking for answers. Sonicwall has released a new client similar to the iOS one for Android. The catch is, it only works with ICS and will also require the firewall to be running OS 5.8 or above. Good luck.
Sent from my HTC EVO 3D X515m using XDA
Sonicwall mobile connect - works on android 4.0.4 and does not require a root.
Hey all,
I just rooted my galaxy tab 2 10.1 GT-P5110 following the steps that are explained in the [How To] ROOT- Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110] thread on this forum. But i noticed that sometimes the sound of the tab not work.
This happens sometimes and i don't know why or how this can happen, when i reboot my device the sound does not come back, but when i use the Bootloader functionallity in the Quickboot app, my sounds will come back after rebooting.
Anyone had the same problem or know a solution to this problem?
Wesley
No Problem on 5113
I rooted my 5113 and left it with the stock TouchWiz ROM for a few weeks and had no audio problems at all. Watched the entire second season of BlackAdder off of Netflix on it.
I have since gone to the CM9 image, and I have yet to have an issue with audio. I can't imagine activating root would cause such a problem, but you never know.
C'pn
no sound...
The strangest is when i does have audio, it will work correctly, the sound is as it suposed to be, but it looks like when my tablet is idle for a bit longer time ( minute of 5 or 10 maybe 15 ), this problem will occur. Is theire a posibillity that a docking station with keyboad has something to do with it?
strange got the exact same problem! also on 4.0.3 and rooted. And i have the keyboard from samsung as well. please tell me if you found a fix!
still not resolved the problem
No i did not found the solution aldready, and i also have the official samsung tab 2 keyboard docking station, i noticed that this problem will only occur when i have my tab in the dockig and its idle for a minute of 10 maybe 15.
Today i did not use my docking for testing, and all day long i just have my sound, so the problem is with the docking station.
Unfortionally i still not have a solution, but i keep looking and if i find one i will post it here..
Tomorrow i will lay my device onto the eclipse debugger, and see where the stacktrace goes if i reproduce this problem.. results i will post here..
Thnx for the tip gonne try that today i also got the original keybpoard im about to contact samsung monday
problem also before root?
i'm just hooked my device up to logcat in eclipse, but now i don't have the problem so just waiting for getting the problem.
yeah i was also doubting of contacting samsung, but i don't know if the problem also was theire before rooting my tab. in my opinion i did not have any trouble before root, but i don't know for sure..
Exact same over here but dont wanne unroot
logcat results
Today i reproduced the problem and logged it with the ecplise tool logcat and here are the results:
The moment i pushed my volume button to increase by 1 to recognize the point in logcat, and then i put it on lock, so you will hear the lock sound ( i did not hear the lock sound) , this where the results:
07-08 23:02:40.378: I/AudioHardwareTinyALSA(98): mMusicVolumeIndex=6
07-08 23:02:40.378: I/AudioHardwareTinyALSA(98): mMusicVolume=0.044668
07-08 23:02:41.480: D/dalvikvm(1125): GC_CONCURRENT freed 399K, 8% free 6722K/7239K, paused 4ms+1ms
07-08 23:02:43.378: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:44.370: W/PowerManagerService(190): Timer 0x0->0x0|0x0
07-08 23:02:44.378: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:44.948: E/Watchdog(190): [email protected] 764
07-08 23:02:45.378: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:46.386: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:47.386: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:48.386: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:49.394: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:50.394: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:51.394: W/AudioTrack(190): obtainBuffer timed out (is the CPU pegged?) 0xe9c150 user=00001400, server=00000400
07-08 23:02:52.378: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot write stream data: I/O error
07-08 23:02:52.378: W/AudioFlinger(98): write blocked for 9998 msecs, 55 delayed writes, thread 0x63f750
07-08 23:02:52.378: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:02:52.378: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:02:52.378: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:02:52.386: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
--- Here over 100 times the following ---
07-08 23:02:52.386: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
--- And then after that ---
07-08 23:02:55.370: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:02:55.386: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:02:55.402: D/AudioHardwareTinyALSA(98): Entering AudioStreamOutALSA standby mode
07-08 23:02:55.402: I/AudioHardwareTinyALSA(98): Close mHandle:6badf0
07-08 23:02:59.995: E/AlarmManagerService(190): android_server_AlarmManagerService_set to type=3, 73549.975000000
07-08 23:03:00.003: D/KeyguardUpdateMonitor(190): received broadcast android.intent.action.TIME_TICK
07-08 23:03:00.003: D/KeyguardUpdateMonitor(190): handleTimeUpdate
07-08 23:03:00.003: V/AlarmManager(190): ClockReceiver onReceive() ACTION_TIME_TICK
07-08 23:03:00.042: D/ClockWidget(190): Current time: 23:03
When playing a video also the video is lagging, and this is the result of playing the video:
07-08 23:12:44.214: V/AwesomePlayer(98): we're late by 374519 us (0.37 secs)
07-08 23:12:44.214: V/AwesomePlayer(98): we're late by 374519 us (0.37 secs) dropping one after 0 frames
07-08 23:12:44.230: V/AwesomePlayer(98): we're late by 346116 us (0.35 secs)
07-08 23:12:44.230: V/AwesomePlayer(98): we're late by 346116 us (0.35 secs) dropping one after 0 frames
07-08 23:12:44.245: V/AwesomePlayer(98): we're late by 316309 us (0.32 secs)
07-08 23:12:44.245: V/AwesomePlayer(98): we're late by 316309 us (0.32 secs) dropping one after 0 frames
07-08 23:12:44.253: V/AwesomePlayer(98): we're late by 285923 us (0.29 secs)
07-08 23:12:44.253: V/AwesomePlayer(98): we're late by 285923 us (0.29 secs) dropping one after 0 frames
07-08 23:12:44.261: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:12:44.261: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:12:44.269: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:12:44.269: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
07-08 23:12:44.269: E/AudioHardwareTinyALSA(98): TinyAudioStreamOut::write() failed: cannot prepare channel: Device or resource busy
Hope someone can see the problem or knows a solution...
My nexus 5 has a broken wifi. I just upgraded to Lollipop and it appears that whenever the phone goes into sleep, it'll try to initilize the wifi and run into some error. This causes the phone to reboot and the same error repeat itself during the next sleep cycle. The catlog as follows:
I/PowerManagerService(23996): Going to sleep due to power button (uid 1000)...
E/Sensors ( 186): sns_acm_mr.c(432):Transport error -45
I/PowerManagerService(23996): Sleeping (uid 1000)...
I/Adreno-EGL(23996): <qeglDrvAPI_eglInitialize:410>: QUALCOMM Build: 10/24/14, 167c270, I68fa98814b
I/WifiNative-HAL(23996): startHal
E/wifi (23996): getStaticLongField sWifiHalHandle 0x9d7fb86c
I/WifiHAL (23996): Initializing wifi
I/WifiHAL (23996): Creating socket
I/WifiHAL (23996): Initialized Wifi HAL Successfully; vendor cmd = 103
D/wifi (23996): Did set static halHandle = 0xb3e33040
D/wifi (23996): halHandle = 0xb3e33040, mVM = 0xb4f5c280, mCls = 0x40162a
E/wifi (23996): getStaticLongField sWifiHalHandle 0x9d7fb81c
D/wifi (23996): array field set
D/PhoneStatusBar(24166): disable: < expand ICONS alerts SYSTEM_INFO back HOME RECENT clock SEARCH >
F/libc (23996): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x5000001 in tid 24123 (WifiStateMachin)
I/libc (23996): Suppressing debuggerd output because prctl(PR_GET_DUMPABLE)==0
I/ServiceManager( 164): service 'country_detector' died
Is there a way to totally disable or remove the wifi device? I know I should get the device RMA but due to some constrain, I am unable to do it now. Any help appreciated.
I'm investigating the same problem. Currently no progress.
I have discussed this issue in thread: http://forum.xda-developers.com/google-nexus-5/help/android-5-0-rebooting-screen-shut-off-t2938805
Hello.
I activated the Bluetooth HCI snoop log on my Nokia 7 plus.
I restarted the phone, and connected it to different bluetooth devices.
But i can't find the logfile. Where should i find it?
adb pull /sdcard/Android/data/btsnoop_hci.log
adb pull /sdcard/data/btsnoop_hci.log
adb pull /sdcard/btsnoop_hci.log
adb pull /btsnoop_hci.log
returns always "remote object ... does not exist"
This is what /etc/bluetooth/bt_stack.conf looks like:
# Enable trace level reconfiguration function
# Must be present before any TRC_ trace level settings
TraceConf=true
# Trace level configuration
# BT_TRACE_LEVEL_NONE 0 ( No trace messages to be generated )
# BT_TRACE_LEVEL_ERROR 1 ( Error condition trace messages )
# BT_TRACE_LEVEL_WARNING 2 ( Warning condition trace messages )
# BT_TRACE_LEVEL_API 3 ( API traces )
# BT_TRACE_LEVEL_EVENT 4 ( Debug messages for events )
# BT_TRACE_LEVEL_DEBUG 5 ( Full debug messages )
# BT_TRACE_LEVEL_VERBOSE 6 ( Verbose messages ) - Currently supported for TRC_BTAPP only.
TRC_BTM=2
TRC_HCI=2
TRC_L2CAP=2
TRC_RFCOMM=2
TRC_OBEX=2
TRC_AVCT=2
TRC_AVDT=2
TRC_AVRC=2
TRC_AVDT_SCB=2
TRC_AVDT_CCB=2
TRC_A2D=2
TRC_SDP=2
TRC_SMP=2
TRC_BTAPP=2
TRC_BTIF=2
TRC_BNEP=2
TRC_PAN=2
TRC_HID_HOST=2
TRC_HID_DEV=2
# This is Log configuration for new C++ code using LOG() macros.
# See libchrome/base/logging.h for description on how to configure your logs.
# sample configuration:
#LoggingV=--v=0
#LoggingVModule=--vmodule=*/btm/*=1,btm_ble_multi*=2,btif_*=1
# PTS testing helpers
# Secure connections only mode.
# PTS_SecurePairOnly=true
# Disable LE Connection updates
#PTS_DisableConnUpdates=true
# Disable BR/EDR discovery after LE pairing to avoid cross key derivation errors
#PTS_DisableSDPOnLEPair=true
# SMP Pair options (formatted as hex bytes) auth, io, ikey, rkey, ksize
#PTS_SmpOptions=0xD,0x4,0xf,0xf,0x10
# SMP Certification Failure Cases
# Set any of the following SMP error values (from smp_api_types.h)
# to induce pairing failues for various PTS SMP test cases.
# Setting PTS_SmpFailureCase to 0 means normal operation.
# Failure modes:
#
# SMP_PASSKEY_ENTRY_FAIL = 1
# SMP_PAIR_AUTH_FAIL = 3
# SMP_CONFIRM_VALUE_ERR = 4
# SMP_PAIR_NOT_SUPPORT = 5
# SMP_PAIR_FAIL_UNKNOWN = 8
# SMP_REPEATED_ATTEMPTS = 9
# SMP_NUMERIC_COMPAR_FAIL = 12
#PTS_SmpFailureCase=0
Click to expand...
Click to collapse
After Nougat I had to take a bug report instead
You may not still be looking this info, but for the sake of anyone else who may be... It may depend on your Android version. From my own experience it was always right there in the main directory, but as soon as my Nokia 5 upgraded past Android 6 Marshmallow, the HCI snoop log is no longer generated, and now if I want Bluetooth logs I take a bug report, send it to myself, and pull Bluetooth logs out of it. It's a bit more fiddly, but it works.
schorsch81 said:
Hello.
I activated the Bluetooth HCI snoop log on my Nokia 7 plus.
I restarted the phone, and connected it to different bluetooth devices.
But i can't find the logfile. Where should i find it?
adb pull /sdcard/Android/data/btsnoop_hci.log
adb pull /sdcard/data/btsnoop_hci.log
adb pull /sdcard/btsnoop_hci.log
adb pull /btsnoop_hci.log
returns always "remote object ... does not exist"
This is what /etc/bluetooth/bt_stack.conf looks like:
Click to expand...
Click to collapse
I'm on Android 10 with my Pixel3 and in the last few days it gets randomly hot. Battery is wasted as a consequence.
I leave it on the table for like 40 minutes when I pull it up I feel it's hot in some specific area.
Tipically it's hot in the central area just at bottom of the fingerprint sensor.
I noticed a high battery consumption caused by "carrier services".
I opened logcat and found it's flooded by carrier services logs errors (see attachment).
There are so many errors.
Code:
[09-20 17:32:42.617 2853:4185 E/CarrierServices]
[199] bvc.a: (RCS): : The SIP message can't be sent: Socket is closed: java.net.SocketException: Socket is closed
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.waitForHandshake(ConscryptFileDescriptorSocket.java:491)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.getOutputStream(ConscryptFileDescriptorSocket.java:463)
at bws.c(SourceFile:23)
at bvc.a(SourceFile:38)
at dre.a(SourceFile:195)
at drd.b(Unknown Source:4)
at drh.b(SourceFile:9)
at drh.a(SourceFile:5)
at cnt.b(SourceFile:17)
at drh.b(SourceFile:9)
at drh.a(SourceFile:5)
at cpl.b(SourceFile:3)
at drh.b(SourceFile:9)
at drh.a(SourceFile:5)
at cpf.b(SourceFile:9)
at drh.b(SourceFile:9)
at drh.a(SourceFile:5)
at bit.b(SourceFile:26)
at drh.b(SourceFile:9)
at dre.b(SourceFile:185)
at dre.a(SourceFile:179)
at dre.a(SourceFile:150)
at bup.a(SourceFile:206)
at bup.f(SourceFile:141)
at bup.b(SourceFile:84)
at btv.a(SourceFile:73)
at buv.run(SourceFile:40)
at bij.handleMessage(SourceFile:44)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
[09-20 17:32:42.617 2853:30612 E/CarrierServices]
[133099] bvh.run: (RCS): : Error while receiving message: SSL handshake aborted: ssl=0x736da92388: I/O error during system call, Connection reset by peer: javax.net.ssl.SSLHandshakeException: SSL handshake aborted: ssl=0x736da92388: I/O error during system call, Connection reset by peer
at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
at com.android.org.conscrypt.NativeSsl.doHandshake(NativeSsl.java:387)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.startHandshake(ConscryptFileDescriptorSocket.java:226)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.waitForHandshake(ConscryptFileDescriptorSocket.java:476)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket.getInputStream(ConscryptFileDescriptorSocket.java:439)
at bws.b(SourceFile:20)
at bvh.run(SourceFile:9)
[09-20 17:32:42.618 2853:30612 I/CarrierServices]
[133099] bsa.z: Using RCS compliant config URL
[09-20 17:32:42.618 2853:4185 I/CarrierServices]
[199] bsa.z: Using RCS compliant config URL
[09-20 17:32:42.624 2853:4185 I/CarrierServices]
[199] bws.a: Closing socket
[09-20 17:32:42.626 2853:4185 I/CarrierServices]
[199] bsa.z: Using RCS compliant config URL
[09-20 17:32:42.632 2853:4185 E/CarrierServices]
[199] btv.a: (RCS): : Transport error while receiving a message: (RCS): : Can't send message: Socket is closed
[09-20 17:32:42.633 2853:4185 I/CarrierServices]
[199] auh.b: (RCS): : Restarting the IMS connection manager, reason: NETWORK_ERROR
[09-20 17:32:42.633 2853:4185 I/CarrierServices]
[199] auh.d: (RCS): : Schedule to stop IMS connection, reason: NETWORK_ERROR
Are you experiencing the same?
Way to fix this?
i see my phone too gets hot often but i dont see carrier services that is causing it. All the apps for me are the regular ones that i use.
This is something that i experienced in the beta builds too but mostly when i was using the camera. Hoping between (HDR+/ & night sight). Gladly the warning message of phone overheating always flashed so that i could turn it off in time.