PixelExperience / android-issues

Issue tracker
95 stars 41 forks source link

Mobile Internet is losing connection. #5915

Closed Vit2024 closed 8 months ago

Vit2024 commented 10 months ago

Build Date

PixelExperience_kunlun2-13.0-20240103-1436-OFFICIAL.zip

Device

kunlun2

Version

thirteen

Describe the Bug

When downloading a large file, the Internet works fine. 1.5 gigabytes in 5 minutes. When scrolling through the Internet, the connection disappears. At the same time, there is a network signal in the status bar. The same thing happens when scrolling through Telegram, the Internet disappears. The SDM-710 does not support 5G, the cellular network operator does not support 5G, but the logcat is full of NR messages. NR = 5G I believe this is the reason for the connection loss. The APN settings correspond to the operator's requirements. In the menu ##4636## is set for both GSM/WCDMA/LTE(PRL) SIMs. Only GSM can be manually selected.

Steps to Reproduce

logcat -b radio |grep -i "Reset timers" See by the time of messages how often Pixel Experience tries to turn on 5G.

01-08 23:31:29.357 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:33:49.792 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:34:57.735 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:34:57.736 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:35:01.177 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:35:01.652 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:35:01.653 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:35:05.794 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:36:14.298 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:11.191 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:11.191 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:12.960 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:37:13.297 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:37:13.358 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:37:13.361 17754 17754 D NetworkTypeController: [1] Reset timers since NR is not allowed. 01-08 23:37:13.490 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:17.062 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:17.062 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:19.074 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:19.075 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:19.232 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:19.232 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:21.241 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:21.241 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:21.406 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:21.407 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:23.415 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:23.415 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:23.529 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:23.529 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:25.543 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:25.543 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:25.970 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:25.970 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:37:45.293 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:38:44.790 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-08 23:38:44.790 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. If you enable only GSM, then Pixel Experience also includes Reset timers.

01-09 00:03:07.726 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:09.381 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:10.987 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:11.036 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:11.044 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:11.044 17754 17754 D NetworkTypeController: [0] Reset timers since 2G and 3G don't need NR timers. 01-09 00:03:11.064 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed.
logcat -b radio |grep -A2 -B2 "Reset timers since 2G and 3G" The Edge network also contains 5G errors. 01-09 00:03:04.635 17754 17754 D NetworkTypeController: [0] LegacyState: process EVENT_DATA_RAT_CHANGED 01-09 00:03:04.635 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:04.635 17754 17754 D NetworkTypeController: [0] Reset timers since 2G and 3G don't need NR timers. 01-09 00:03:04.636 17754 17754 D Phone : [0] SubId1,get allowed network types user: value = GPRS|EDGE|GSM 01-09 00:03:04.636 17754 17754 D PhoneFactory: calculatePreferredNetworkType: phoneId = 0 networkType = 32771

01-09 00:03:11.044 17754 17754 D NetworkTypeController: [0] LegacyState: process EVENT_DATA_RAT_CHANGED 01-09 00:03:11.044 17754 17754 D NetworkTypeController: [0] Reset timers since NR is not allowed. 01-09 00:03:11.044 17754 17754 D NetworkTypeController: [0] Reset timers since 2G and 3G don't need NR timers. 01-09 00:03:11.045 17754 17754 D Phone : [0] SubId1,get allowed network types user: value = GPRS|EDGE|GSM 01-09 00:03:11.045 17754 17754 D PhoneFactory: calculatePreferredNetworkType: phoneId = 0 networkType = 32771

Expected Behavior

I wish Pixel Experience didn’t try to make the SDM 710 5G work. I have to turn on airplane mode and turn on mobile data again. I wish the internet worked.

Possible Solution

No response

pixelexperiencebot commented 10 months ago

Issue created! You can close at any time by commenting /close

Vit2024 commented 10 months ago

Perhaps this will help in finding a solution to the bug. find /{system,vendor}/ -type f -name '*.jar' | xargs grep -i "Reset timers since NR is not allowed" /system/framework/telephony-common.jar

Vit2024 commented 9 months ago

logcat_radio.txt I take the pid from the error messages in the log and use the pstree utility to find out information about the process.

kunlun2:/ # logcat -db radio *:E |grep 1199 01-13 23:24:29.761 1199 1247 E RILQ : (1/1199): RIL[1][(1199,1247)] get_ecc_property_name: ecc list name : ril.ecclist1.

kunlun2:/ # /data/data/com.termux/files/usr/bin/pstree -tsp 1247 /system/bin/init(1)───/vendor/bin/hw/qcrild(1199)───{DispatcherModul}(1247)

kunlun2:/ # logcat -db radio *:E |grep 1172 01-13 23:24:29.740 1172 1246 E RILQ : (0/1172): RIL[0][(1172,1246)] get_ecc_property_name: ecc list name : ril.ecclist.

kunlun2:/ # /data/data/com.termux/files/usr/bin/pstree -tsp 1246 /system/bin/init(1)───/vendor/bin/hw/qcrild(1172)───{DispatcherModul}(1246)

kunlun2:/ # logcat -db radio *:E |nl 1 --------- beginning of radio 2 01-13 23:24:29.778 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 44 3 01-13 23:24:29.778 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 0 4 01-13 23:24:29.779 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 0 5 01-13 23:24:29.779 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 0 6 01-13 23:24:29.779 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 44 7 01-13 23:24:29.780 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 44 8 01-13 23:24:29.780 17754 17857 E RILJ : processResponse: Unexpected response! serial: 80560 ,error: 44 kunlun2:/ # /data/data/com.termux/files/usr/bin/pstree -tsp 17857 /system/bin/init(1)───zygote64(17052)───com.android.phone(17754)───{HwBinder:17754_}(17857)

Vit2024 commented 9 months ago

The file /vendor/bin/hw/qcrild does not correspond to the file vendor_11.5.117_v3/vendor/bin/hw/qcrild. These are different files.

Vit2024 commented 9 months ago

I installed vendor_11.5.117_v3/vendor/bin/hw/qcrild but nothing changed. Earlier, in December, I installed this file apns-conf.zip https://dumps.tadiphone.dev/dumps/redmi/manet/-/blob/missi_phone_cn_only64-user-14-UKQ1.230804.001-V816.0.8.0.UNMCNXM-release-keys/system/system/etc/apns-conf.xml?ref_type=heads But then nothing changed, the Internet also lost connection. Yesterday I downloaded this file from the same site: spn-conf.zip I think these two files are complementary. I have a SIM MVNO "Rostelecom". Perhaps the apns-conf.xml file has regional settings, it is very large! Therefore, I reduced both files, leaving only operators from Russia. They are here: E.zip I copied files from E.zip to /system/etc. I have been entering exactly the same APN settings manually for two months now and the Internet is losing connection. But with these two files the Internet started working!!! But there are still a lot of errors in the logcat.

Jorg3Lucas commented 8 months ago

Hello, I hope you are well, thanks for your feedback/report, we have ended support for Android 13. We hope you will be with us in the future to make the Android 14 experience as stable as possible.

Jorg3Lucas commented 8 months ago

Hello, I hope you are well, thanks for your feedback/report, we have ended support for Android 13. We hope you will be with us in the future to make the Android 14 experience as stable as possible.