[Galaxy S III Original Android Development] curiousrom:
LineageOS Network Traffic Monitor - Incoming Call Lag

I was looking at LineageOS Downloads > Changes for i9300 > to check if the 2018-06-07 update is worth the trouble and noticed the commit SystemUI: Network Traffic [1/3] (Add cmsdk internal NetworkTraffic to the statusbar) so in my currently running Official Lineage 14.1 on the S3 i9300 2018-05-31 I checked in Settings > Status bar > and Network traffic monitor was already included in the 2018-05-31 build.

It's really well done with several options like show the data for upload only, download only or both, Trafic measurements units (Mb/s, MB/s, etc) & show units or not. I included screenshots w/ both + units enabled while running Speedtest by Ookla¹ and the Network traffic monitor panel with only download & units disabled which is my preferred choice when using the monitor for a cleaner status bar.

¹ - If you are a Speedtest user or install it, to save power & privacy: Settings > Privacy > Privacy Guard > Speedtest > disable Run in background and Speedtest > Settings > disable Network signal scanning and > Analytics. That's why they want to run in the background: to collect your data. :eek:

***

Incoming Call Screen On Lag

Any ideas why this happens?" - It happens because the S3 is old. ;) This has been discussed for the S3 in XDA since 2013. Testing on my S3 it varies form 2.2 (2 calls in quick succession) to 5 seconds depending on sleep state & if you have a bunch of apps that have running in the background enabled & are woken up and trying to do stuff in the middle of the incoming call process.

The sequence as seen in Logcat is roughly > incoming call > CallerInfoLookupHelper > Play ringtone > draw Full Screen in call UI > Repeat ringtone > Blocking screen on until initial contents have been drawn > turn on screen.

See these 2 posts made with using MatLog (a logcat reader) to capture the incoming call > screen on process with precise time stamps: In Call Wake Up Time and also S3 i9300 In Call Wake Up Time #3 - Logcat.

"...I also had this on my stock 4.3 version"- It's been so long since I have used 4.3 that I don't remember. If somebody running stock Samsung 4.3 could post a logcat captured as described in the linked post it would awesome to compare it with Lineage 14.1.

"The physical button will answer the call even though the screen is black" - Thanks :good: for the suggestion but it does not work on my S3 setup. Checking in logcat I see (selected lines - in bold the keywords if you search in logcat opened in Wordpad for example):

06-07 04:55:20.598 I/Telecom (23474): : Adding new incoming call with phoneAccountHandle

06-07 04:55:21.407 I/Telecom (23474): AsyncRingtonePlayer: Play ringtone.

06-07 04:55:23.067 I/ScreenEventHandler(30932): Received Broadcast ACTION_USER_PRESENT <<<< Home button press

06-07 04:55:23.131 I/DisplayPowerController(23474): Blocking screen on until initial contents have been drawn.

06-07 04:55:23.666 I/DisplayManagerService(23474): Display device changed state: "Built-in Screen", ON

Time it took: 23.666 - 20.598 = 3.062 seconds. Only after the screen is turned on do I have the option to answer or dismiss the call.

***

S3 Battery Temperature

Yes it makes sense what you say but since all the kernel managers I used on stock S3 including EX Kernel Manager which I will add to the post above don't report the battery temperature for the S3 LOS stock it may be something enabled in the Boeffla-Kernel.

Anyway this is all academic has my fingers on the back of the phone are excellent temperature reporting devices & they are connected directly to my brain which concludes in a nano second that's it's better to kill some apps & turn off the phone to let it cool off a bit or wait for cool down before charging it because charging a hot battery is really bad for it's life expectancy.

Thanks :good: for doing it. Too bad you used a split screen w/ your stress test (again: name of the test?) as now I can't see the device's name & other info shown in Boeffla-Config. :crying:

Thanks :good: for posting your Boeffla-Config screenshot. I see in it that you are running a custom Android 4.4.4. Did you try Official LineageOS 14.1 based on Nougat 7.1.2 w/ or w/o Boeffla-Kernel? Check this post it includes download links as well as know 14.1 issues & battery optimization links: S3 i9300 LineageOS Super Clean Install & Samsung Firmware

***

S3 Modem Board?

If you are talking about the hardware model name & # of the S3's Modem Board I don't know of any app that reports that info because it's not reported by the device I guess.

I used the powerful & dangerous Z3X Samsung Tool > Backup & under Modem Board it is blank (screenshot) just like in the Phone Info Samsung app and using Terminal Emulator by Jack Palevich (because I can email the content of the screen to myself with it) > getprop | grep modem.board > returns: [ril.modem.board]: [ ] instead of [ril.model_id]: [I9300] for example.

I searched a complete getprop dump with "modem" and that's the only instance. Note that all this can be done with adb shell.

If you are talking about the modem firmware (baseband) various versions are included in the stock Samsung firmwares but not in LineageOS.

***

Thanks :good: for reporting back how you fixed your intermittent network connection problem. It's probable that a clean install of LineageOS would have worked too.

Next time you could use SysLog for example to capture full logs including Modem for troubleshooting.

***