divis1969
divis1969
На каком релизе-то это происходило? Вы не смотрели los-14.1 v0.4/v0.5 (см. также #109 )? На них то же самое?
Проверьте на v0.12, там были фиксы для блютус гарнитуры https://github.com/divis1969/android_hardware_libhardware/commit/87fd6bbc4bb83a611b81f050d7385d40bbcd11ae https://github.com/divis1969/android_packages_apps_Bluetooth/commit/b35117845d19cac1abd18889f96f1d348ef5f4f8 https://github.com/divis1969/android_external_bluetooth_bluedroid/commit/6b870b597c5687107f1684da0867b5fe389402bf
1. Почему она должна быть? На других циановских билдах встречалась? 2. Как выглядит? В каком сценарии должна быть?
If the issue appeared recently, it would be great to understand what change(s) caused this. I've also noticed some issue with AGPS (something wrong with SSL/TLS) in those logs. Actually,...
I'm not aware whether mtk_agps accesses /etc/gps.conf. I suppose no. Some observations from logs: `05-29 15:38:05.672 D/agps ( 247): [agps][SUPL] config supl_version=1 eCID=1 addr=[supl.nokia.com] port=7275 tls=1` Dont know yet where...
BTW: ping supl.nokia.com PING nokia.supl.svc.ovi.com.glb.as1248.net (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.008 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.020 ms 64 bytes...
It looks like DNS is reporting this IP. Nokia stopped to provide this service?
It looks the SUPL profiles are specified in /etc/agps_profiles_conf2.xml
That again raises a question: what had happened recently that causes the issue with GPS?
BTW, I've found a log from cm-12.1 v0.14 which is dated by March 1, 2017 and it had resolved supl.nokia.com to some IP > 03-01 21:44:06.800 262 2230 D agps...