Recently, my Bluetooth audio quality has become very. There's a high pitched crackling sound. Anyone else have the same issue?
I have the same version but unlocked not encountered any odd sounds via my Audi A3, my only complaint is that the option to keep all music tracks as same volume only affects the louder ones.
Yah, at first I thought it was limited to my car, but I experience similar sound quality issues with other bluetooth headphones
Plugging in directly to my car's AUX jack, the audio quality is fine.
Same issue
jamesm113 said:
Recently, my Bluetooth audio quality has become very. There's a high pitched crackling sound. Anyone else have the same issue?
Click to expand...
Click to collapse
I'm absolutely having the same issue. Sounds like static and distortion in the higher frequencies, almost like a low bitrate mp3 file.
I first noticed it when I upgraded from the G6 which sounded completely fine over bluetooth. I have several bluetooth devices in my house and car and all exhibited the same issue. As a sanity check, I connected my laptop to all of those devices and was getting absolutely no distortion. So clearly it's an issue with the phone.
Upon further inspection, I discovered it has something to do with the G8's SBC codec implementation. I have a pair of bluetooth headphones that support both AAC and AptX and the G8 sounded completely normal over those codecs, but when switching back to SBC, I got the same distortion.
My guess is that a bug is forcing the bitrate to the lowest level regardless of signal quality.
Someone had reported something similar happening on the G6 a couple years ago, but I didn't notice it on my particular G6. Perhaps the issue is limited to certain variants. I have the US T-Mobile version.
I'm surprised that no one else thus far has noticed the issue. Drives me absolutely bananas.
I sent mine in because of this issue. They replaced the bluetooth module and the audio quality is much improved.
They also messed up the camera in the process, so I had to send my phone in again, which wasn't fun.
jamesm113 said:
I sent mine in because of this issue. They replaced the bluetooth module and the audio quality is much improved.
They also messed up the camera in the process, so I had to send my phone in again, which wasn't fun.
Click to expand...
Click to collapse
Thanks for the update. Sounds like a terrible experience. Perhaps not worth the risk.
They did send me the attached troubleshooting steps before granting my warranty repair request.
The first two steps did nothing, but the factory reset resolved it for a few days. Once the issue came back, I reported it to LG, and they sent me a label to send my phone in. I explored doing a warranty exchange through T-Mobile, but they charge a fee, and send you a refurbished phone. At least with LG, I got my original phone back.
Today, the audio quality is fine, for the most part. In my car, if I have it cranked, the cymbals can be a little distorted, but nowhere near as bad as it was before. My car has an old JVC receiver that uses bluetooth 2.1, so it's not like I expect great audio quality out of it anyway.
jamesm113 said:
They did send me the attached troubleshooting steps before granting my warranty repair request.
The first two steps did nothing, but the factory reset resolved it for a few days. Once the issue came back, I reported it to LG, and they sent me a label to send my phone in. I explored doing a warranty exchange through T-Mobile, but they charge a fee, and send you a refurbished phone. At least with LG, I got my original phone back.
Today, the audio quality is fine, for the most part. In my car, if I have it cranked, the cymbals can be a little distorted, but nowhere near as bad as it was before. My car has an old JVC receiver that uses bluetooth 2.1, so it's not like I expect great audio quality out of it anyway.
Click to expand...
Click to collapse
Thanks. Seems like the factory reset also worked here, though as you mentioned, I fully expect it to go back to the way it was in a few days.
I have the T-Mobile G8. I don`t know if it s the same issue but You should give it a try.
When I connected to my bluetooth headphones, the volume was very low. I made a research and found out that when you change the bluetooth device name to ABS-DO-ENABLE it increases the volume to normal level. I changed the device name and it worked.
@tonisama - I think the issue must have jumped from your phone to mine! The sound quality issue is back.
@salihss - No luck, still sounds like crap
back for me as well
jamesm113 said:
@tonisama - I think the issue must have jumped from your phone to mine! The sound quality issue is back.
@salihss - No luck, still sounds like crap
Click to expand...
Click to collapse
Same here. The bluetooth audio worked great for a couple of weeks after the factory reset, but eventually, the distortion resurfaced.
Note that bluetooth audio over the AAC and AptX codecs does not exhibit this issue. If you don't want to dump your phone, you could try using devices that support those codecs rather than the default SBC.
Any idea on how we could get visibility to what bit-rate SBC is using? I've tried a handful of apps from the play store last time, but didn't have much success.
I've also noticed my set of bluetooth 5.0 headphones sound fine.
Started a new thread in the more general forum: https://forum.xda-developers.com/an...hooting-bluetooth-audio-t4039667#post81583193
jamesm113 said:
Any idea on how we could get visibility to what bit-rate SBC is using? I've tried a handful of apps from the play store last time, but didn't have much success.
I've also noticed my set of bluetooth 5.0 headphones sound fine.
Click to expand...
Click to collapse
Apparently, there's a setting in the Developer options "Enable Bluetooth HCI snoop log" which will record the handshake with the negotiated bit rate. The log is stored in the /sdcard/ directory which is not accessible from the phone itself. I believe you need ABD installed on a PC with the phone connected to pull the log.
Yeah, I think they changed it with android 9, so you have to do a full bug report, which is kind of a pain.
My process is this:
Turn off bluetooth
enable bluetooth snoop log
turn on bluetooth and connect device
play audio sample
turn off bluetooth
disable bluetooth snoop log
send full debug report to my own email
review large log file
Anyway, I found something interesting.
A few nights ago, I pulled the bugreport log (couldn't find the snoog log), when audio quality sounded decent, and found it was 328 kbps:
Code:
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: sample_rate=44100 bits_per_sample=16 channel_count=2 min_bitpool=2 max_bitpool=35
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate rate = 345
01-24 22:42:14.809 1002 2931 3024 W a2dp_sbc_encoder: initial bitrate = 345
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 56 (345 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (56)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 55 (340 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (55)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 54 (335 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (54)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 53 (330 kbps)
01-24 22:42:14.809 1002 2931 3024 E a2dp_sbc_encoder: offload_bitrate for sbc = 330
01-24 22:42:14.809 1002 2931 3024 W a2dp_sbc_encoder: [BTUI] final offload_bitrate for sbc = 328
Today, it sounds like garbage and is 229 kbps:
Code:
01-27 09:47:22.126 1002 25240 25283 E a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate is peer edr = 1
01-27 09:47:22.126 1002 25240 25283 D a2dp_codec: A2DP_GetCodecType:
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: sample_rate=44100 bits_per_sample=16 channel_count=2 min_bitpool=2 max_bitpool=35
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate rate = 345
01-27 09:47:22.127 1002 25240 25283 W a2dp_sbc_encoder: initial bitrate = 345
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 56 (345 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (56)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 55 (340 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (55)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 54 (335 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (54)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 53 (330 kbps)
01-27 09:47:22.127 1002 25240 25283 E a2dp_sbc_encoder: offload_bitrate for sbc = 330
01-27 09:47:22.127 1002 25240 25283 W a2dp_sbc_encoder: [BTUI] final offload_bitrate for sbc = 229
Then, while the audio was playing, I fiddled around with some of the debugging settings related to bluetooth. I heard the audio switch cutout very briefly each time I changed a setting and now it sounds a little better. Something worth trying @tonisama
jamesm113 said:
Yeah, I think they changed it with android 9, so you have to do a full bug report, which is kind of a pain.
My process is this:
Turn off bluetooth
enable bluetooth snoop log
turn on bluetooth and connect device
play audio sample
turn off bluetooth
disable bluetooth snoop log
send full debug report to my own email
review large log file
Anyway, I found something interesting.
A few nights ago, I pulled the bugreport log (couldn't find the snoog log), when audio quality sounded decent, and found it was 328 kbps:
Code:
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: sample_rate=44100 bits_per_sample=16 channel_count=2 min_bitpool=2 max_bitpool=35
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate rate = 345
01-24 22:42:14.809 1002 2931 3024 W a2dp_sbc_encoder: initial bitrate = 345
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 56 (345 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (56)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 55 (340 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (55)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 54 (335 kbps)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (54)
01-24 22:42:14.809 1002 2931 3024 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 53 (330 kbps)
01-24 22:42:14.809 1002 2931 3024 E a2dp_sbc_encoder: offload_bitrate for sbc = 330
01-24 22:42:14.809 1002 2931 3024 W a2dp_sbc_encoder: [BTUI] final offload_bitrate for sbc = 328
Today, it sounds like garbage and is 229 kbps:
Code:
01-27 09:47:22.126 1002 25240 25283 E a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate is peer edr = 1
01-27 09:47:22.126 1002 25240 25283 D a2dp_codec: A2DP_GetCodecType:
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: sample_rate=44100 bits_per_sample=16 channel_count=2 min_bitpool=2 max_bitpool=35
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_offload_source_rate rate = 345
01-27 09:47:22.127 1002 25240 25283 W a2dp_sbc_encoder: initial bitrate = 345
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 56 (345 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (56)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 55 (340 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (55)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 54 (335 kbps)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: computed bitpool too large (54)
01-27 09:47:22.127 1002 25240 25283 D a2dp_sbc_encoder: a2dp_sbc_calulate_offload_bitrate: bitpool candidate: 53 (330 kbps)
01-27 09:47:22.127 1002 25240 25283 E a2dp_sbc_encoder: offload_bitrate for sbc = 330
01-27 09:47:22.127 1002 25240 25283 W a2dp_sbc_encoder: [BTUI] final offload_bitrate for sbc = 229
Then, while the audio was playing, I fiddled around with some of the debugging settings related to bluetooth. I heard the audio switch cutout very briefly each time I changed a setting and now it sounds a little better. Something worth trying @tonisama
Click to expand...
Click to collapse
Very interesting indeed. Thanks for looking into this. I guess the question is how to prevent the bitrate from dropping from the max. No reason why this should happen when the device is right next to the source.
If only I had LineageOS' bluetooth stack to enable dual channel SBC mode (up to 551kbps) https://www.lineageos.org/engineering/Bluetooth-SBC-XQ/
Wish LG would unlock the bootloader.
Yeah, I was reading about that. The author of those changes is a member here. Apparently he tried submitting them to stock android, but no one's even looked at his pull request.
https://forum.xda-developers.com/android/software-hacking/improve-bluetooth-audio-quality-t3832615
I found the issue on google's issue tracker in case you want to star it @tonisama https://issuetracker.google.com/issues/144517406
I doubt it'll help us with the G8, but maybe in a few years, it will help all android users
Ugh, with Android 10, the issue is back, and my workaround (changing bluetooth related settings in Developer Settings) doesn't help.
Related
We got root on the one xL. So, my question is How about this over clocking going on here? So I finally rooted, got a ROM, flashed a kernel.. Then bought SETCPU and turned it up to 1.9ghz. This seemed to work right well, but then I discovered a tool from chainfire and found that it wasn't sticking. So I was told about and edited this thermald.conf file.
But I wanna know, what temp was it that caused this to occur, and what I have just changed?
I've overclocked 3 phones now (8125/fuze/inspire) but none were this nice (dual core for example.) and this one gets warm. But I cannot tell how warm? And now I've even changed something and don't even know what. And it was related to warm.
Tl;dr how hard is are you Pushin yer phone?
The change:
sampling 5000
[pa_therm0]
sampling 5000
thresholds 70 80 90
thresholds_clr 65 75 85
actions none none none
action_info 0 0 0
[tsens_tz_sensor0]
sampling 1000
thresholds 50 65 75 80 99 102 105
thresholds_clr 40 62 72 77 96 99 102
actions cpu cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1809000 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor1]
sampling 1000
thresholds 75
thresholds_clr 72
actions none
action_info 0
[tsens_tz_sensor2]
sampling 1000
thresholds 100
thresholds_clr 80
actions none
action_info 0
[tsens_tz_sensor3]
sampling 1000
thresholds 75 78 81 84 87 90
thresholds_clr 72 75 78 81 84 87
actions cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor4]
sampling 1000
thresholds 50 65 80 86
thresholds_clr 40 62 77 84
actions gpu gpu gpu gpu
action_info 400000000 300000000 200000000 27000000
Please!
Move on to the One XL forum, please.
This is the forum for the One X with quadcore Tegra 3 CPU so we can't tell you which temperatures are ok for the dualcore S4 CPU in your device
Sent from my HTC One X using xda app-developers app
New Pokemon Emerald Code For GameBoid Emulator On Android Phones
Here is a list of EACH code and what it
corresponds too:
Make sure you put a 0 before all double
digits and 00 before single digits.
Replace the Three X's with your variable
choice.
Use this code, 82005274 0xxx
They are about 4000
It replaces the top item at any mart.
1-9 is different poke balls
10 is defrost
11 is awakens
12 is heal paralyzation
13 is full restore
14 is max potion
15 is hyper potion
16 is super potion
17 is full heal
18 is revive
19 is max revive
20 is heal powder
21 is revival herb
22 is ether
23 is max ether
24 is elixir
25 is max elixir
26 is Lava cookie
27 is blue flute
28 is yellow flute
29 is red flute
30 is red shard
31 is blue shard
32 is yellow shard
33 is green shard
34-39 are nothing. Displayed as ???????.
Can be used as a hold item, good to use
with a Pokemon who knows Trick
40 is protein
41 is iron
42 is carbos
43 is calcium
44 is RARE CANDY!!
45 is raise max pp
46 is zinc
47 pp max
48 is nothing displayed as ???????
49 is guard spec.
50 is a poke doll
51 is a fluffy tail
52 is nothing
53 is super repel
54 is max repel
55 is escape rope
56 is repel
57 is nothing
58 is nothing
59 is nothing
60 is thunderstone
61 is Water stone
62 is leaf stone
63-66 is nothing
67 is tiny mushroom
68 is big mushroom
69-78 are nothing
79 is orange mail
80 is shadow mail
81 is tropic mail
82 is dream mail
83 is fab mail
84 is retro mail
85 is Cheri berry
86 is chesto berry
87 is pecha berry
88 is rawst berry
89 is aspear berry
90 is wiki berry
91 is mago berry
92 is aguav berry
93 is ipapa berry
94 is razz berry
95 is bulk berry
96 is nanab berry
97 is wepear berry
98 is pinap berry
99 is pomeg berry
100 is pink scarf
101 is green scarf
102 is yellow scarf
103 is Mach bike
104 is coin case
105 is item finder
106 is old rod
107 is good rod
108 is super rod
109 is s.s. ticket
110 is acro bike
111 is poke block case
112 is letter
113 is eon ticket
114 is red orb
115 is blue orb
116 is scanner
117 is go goggles
118 is meteorite
119 is rm. 1 key
120 is devon scope
121 is TM01
122 is TM02
123 is TM03
124 is TM04
125 is TM05
126 is TM06
127 is TM07
128 is TM08
129 is TM09
130 is TM10
131 is TM11
132 is TM12
133 is TM13
134 is TM14
135 is TM15
136 is TM16
137 is TM17
138 is TM18
139 is TM19
140 is TM20
141 is TM21
142 is TM22
143 is TM23
144 is TM24
145 is TM25
146 is TM26
147 is TM27
148 is TM28
149 is TM29
150 is TM30
151 is TM31
152 is TM50
153 is HM01
154 is HM02
155 is HM03
156 is HM04
157 is HM05
158 is HM06
159 is HM07
160 is voucher
161 is gold teeth
162 is old amber
163 is card key
164 is lift key
165 is helix fossil
166 is dome fossil
167 is silph scope
168 is bicycle
169 is town map
170 is rainbow pass
171 is tea
172 is mystic ticket
173 is aurora ticket
174 is powder jar
175 is ruby
176 is sapphire
177 is magma emblem
178 is old sea map.
PS: If you have any problem PM me or comment here , another code i will added later . Sorry if i post in wrong section
I try to use Peel Smart Remote app to remote control my TV, but it's not working. And I used another camera to look at my M9 top part, there is also no purple IR light. So is my M9 IR blaster broken?
Here is the log after I press the button in Peel Smart Remote:
Code:
10-16 14:02:50.965: W/CIRControl(23151): Control(L&S): UUID=ae61f479-d57e-41d2-8d2e-595360817bfb
10-16 14:02:50.965: W/CIRControl(23151): transmitIRCmd: drop=true {1 and 38000 and 72}
10-16 14:02:50.965: W/CIRControl(23151): sendMessageToService: 4
10-16 14:02:50.967: W/CIRControlServiceClient(23230): sendMessageToService
10-16 14:02:50.967: W/CIRControlServiceClient(23230): sendMessageToService , thread :main
10-16 14:02:50.967: W/CIRControlService(23230): IncomingHandler: 4
10-16 14:02:50.967: W/CIR-HtcAccessory(23230): IncomingHandler: mCirExist: true, mAccessoryExist: false, mAccessorySupportCIR: false
10-16 14:02:50.969: W/CIRControlService(23230): Send drop-cmd dispatched
10-16 14:02:50.970: E/CIRControlService(23230): CommandHandler: request 4 drop: 0 RID=ae61f479-d57e-41d2-8d2e-595360817bfb
10-16 14:02:50.970: E/CIRControlService(23230): CommandHandler: poll 1 drop:true id=ae61f479-d57e-41d2-8d2e-595360817bfb
10-16 14:02:50.970: W/CIRControlService(23230): Transmit IR +++ 0
10-16 14:02:50.970: W/CIRControlService(23230): frameTime=0
10-16 14:02:50.971: W/htcircontrol(23230): loadAndSendIR: repeatCount=1 cmd[4]=0x1
10-16 14:02:50.971: W/htcircontrol(23230): loadAndSendIR: freq=38000 cmd[6]=0x70 cmd[5]=0x94
10-16 14:02:50.971: W/htcircontrol(23230): loadAndSendIR: 343 170 22 62 22 20 22 20 22 20 22 20 22 20 22 20 22 20 22 20 22 62 22 62 22 62 22 62 22 62 22 62 22 62 22 20 22 20 22 62 22 62 22 20 22 20 22 20 22 20 22 62 22 62 22 20 22 20 22 62 22 62 22 62 22 62 22 1530 343 84 22 3812 (223)
10-16 14:02:50.975: W/OpenGLRenderer(23151): Fail to change FontRenderer cache size, it already initialized
10-16 14:02:50.978: W/htcircontrol(23230): loadAndSendIR: retry: 6 write end: tnum=85
10-16 14:02:50.990: E/htcircontrol(23230): loadAndSendIR: exit 0x0
10-16 14:02:50.990: W/CIRControlService(23230): reply S/LS IR msg when client exists
10-16 14:02:50.990: W/CIRControlService(23230): sendMessageToControl: 2 and 0 and 0
10-16 14:02:50.996: W/CIRControlService(23230): Transmit IR --- aCount: 0 cmdQ.size=0
10-16 14:02:50.996: W/CIRControlService(23230): period: 219 value: 284 wakeup: false
10-16 14:02:51.021: W/CIRControl(23151): Got <MSG_RET_TRANSMIT_IR>
10-16 14:02:51.021: W/CIRControl(23151): sendMessageToUI: 2 and 0 and 0
10-16 14:02:51.281: W/CIRControlService(23230): End of sleeping
10-16 14:02:51.281: W/CIRControlService(23230): Transmit IR final aCount: 0
Have you successfully programmed peel remote to any tv?
Beamed in by telepathy.
Hello everyone,
recently im having serious battery problems (random reboots with battery logo, 20-30% battery decrement).
Can someone attach a log made with CurrentWidget of a normal usage (normally 1 charge cycle from 100 to 20 for example)?
Basically i'm noticing that when the phone is absorbing significant amounts of current is becomes unstable
Example of a shutdown situation (need to charge in order to boot properly, green text)
Code:
Date Time mA % volt temp
08/11/2016 07:44:00 -63 78 3,588 23,7
[COLOR="Red"]08/11/2016 07:45:37 -1154 78 3,588 23,7[/COLOR]
08/11/2016 07:46:37 -43 78 3,588 23,7
[COLOR="Orange"]08/11/2016 07:47:39 -204 78 3,588 23,7[/COLOR]
08/11/2016 07:49:22 -166 78 3,588 23,7
08/11/2016 07:50:22 -172 78 3,588 23,7
0[COLOR="Red"]8/11/2016 07:51:55 -654 77 3,709 20,5[/COLOR]
[COLOR="SeaGreen"]08/11/2016 08:12:04 140 63 4,084 26,5[/COLOR]
08/11/2016 08:13:29 480 66 4,357 25,5
08/11/2016 08:14:29 444 67 4,355 25
Unusual drop in voltages (i'm assuming this happens since i waked up my phone after waking up myself)
Code:
Date Time mA % volt temp
08/11/2016 07:07:27 -51 83 4,062 16
[COLOR="red"]08/11/2016 07:08:28 -47 83 4,062 16
08/11/2016 07:09:28 -54 82 3,696 19[/COLOR]
08/11/2016 07:10:28 -47 82 3,696 19
Moreover when in TWRP 3.0.2 i can't see the battery value on top right corner! Can someone confirm he can?
Hi
I have been working on google pixel 2xl in my research and I wanna understand the contents of the thermal-engine.conf file (I mean what each subroutine written there is doing)
many phones start throttling when the temperature of the cores exceeds some threshold, although in google pixel 2xl and according to what I understood from thermal-engine.conf file
it is rather based on a sensor called bd_therm2 as shown in the first subroutine in the thermal-engine.conf file
"[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0"
but this is not the only subroutine there and there are others and I do not understand what each subroutine is doing
although based on my experiments when bd_therm2 sensor exceeds 38 throttling starts
I appreciate if somebody directs me to some reference that explains these contents
The file contents are as follows (sorry my first time on that forum and I did not know how to attach it)
[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0
[SKIN-MID-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 40000
set_point_clr 39000
device_max_limit 1497600
time_constant 0
[SKIN-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 45000
set_point_clr 44000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL2]
algo_type virtual
trip_sensor bd_therm2
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN2]
algo_type ss
sensor HOT-SKIN-VIRTUAL2
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 48000 50000 52000
thresholds_clr 47000 49000 51000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[BATTERY-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 50000
thresholds_clr 48000
actions battery
action_info 3
[SKIN-SHUTDOWN2]
algo_type monitor
sampling 1000
sensor bd_therm2
thresholds 54000
thresholds_clr 53000
actions shutdown
action_info 1
[SKIN-MID-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 49000
set_point_clr 48000
device_max_limit 1804800
time_constant 0
[SKIN-LOW-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 51000
set_point_clr 50000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL]
algo_type virtual
trip_sensor bd_therm
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN]
algo_type ss
sensor HOT-SKIN-VIRTUAL
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR]
algo_type monitor
sampling 2000
sensor bd_therm
thresholds 58000 60000 64000
thresholds_clr 57000 59000 63000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[SKIN-SHUTDOWN]
algo_type monitor
sampling 1000
sensor bd_therm
thresholds 66000
thresholds_clr 65000
actions shutdown
action_info 1