[Galaxy S III Android Development] leleobhz:
Indeed, something is wrong here.

m0:/ # busybox microcom -s 115200 /dev/ttySAC1 | xxd - | tee -a /sdcard/gps.dump
00000000: a593 0400 1400 0100 0000 0100 0000 0000 ................
00000010: 0000 0000 0000 1a00 a568 a593 0800 4800 .........h....H.
00000020: 0200 0100 0100 4000 0100 0200 0000 0100 ......@.........
00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000040: 0a0c da07 4252 4f41 4443 4f4d 0000 0000 ....BROADCOM....
00000050: fe00 fd40 0000 f1f1 1620 9dfc fe00 fd3f ...@..... .....?
00000060: fe00 0200 0000 30fc fe00 fd3f 1f01 d559 ......0....?...Y
00000070: 0100 58fc fe00 fd3f fb02 1100 0000 64fc ..X....?......d.
00000080: a593 0400 1400 0100 0000 0100 0000 0000 ................
00000090: 0000 0000 0000 1a00 a568 a593 0800 4800 .........h....H.
000000a0: 0200 0100 0100 4000 0100 0200 0000 0100 ......@.........
000000b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000c0: a593 0000 0600 0501 0c00 a568 a593 0400 ...........h....
000000d0: 1400 0100 0000 0100 0000 0000 0000 0000 ................
000000e0: 0000 1a00 a568 a593 .....h..

This was collected in GPS application start. I've also installed (For testing reasons) the magisk module Global Optimized GPS File Replacer. Just for a test if something changes, but not and indeed made it worst. Removing module leads to:

m0:/ # busybox microcom -s 115200 /dev/ttySAC1 | xxd - | tee -a /sdcard/gps.dump
00000000: a593 0000 0600 0401 0b00 a568 a593 0400 ...........h....
00000010: 1400 0100 0000 0100 0000 0000 0000 0000 ................
00000020: 0000 1a00 a568 a593 0800 4800 0200 0100 .....h....H.....
00000030: 0100 4000 0100 0200 0000 0100 0000 0000 ..@.............
00000040: 0000 0000 0000 0000 0000 0000 0a0c da07 ................
00000050: 4252 4f41 4443 4f4d 0000 0000 0000 0000 BROADCOM........
00000060: 3437 3531 3141 3000 0000 0000 0000 0000 47511A0.........
00000070: 4905 a568 a593 0100 0800 0300 0300 0f00 I..h............
00000080: a568 a593 0100 0800 0400 0300 1000 a568 .h.............h
00000090: a593 0100 0800 0500 0300 1100 a568 0100 .............h..
000000a0: 0200 0000 0100 0000 0000 0000 0000 0000 ................
000000b0: 0000 0000 0000 0a0c da07 4252 4f41 4443 ..........BROADC
000000c0: 4f4d 0000 0000 0000 0000 3437 3531 3141 OM........47511A
000000d0: 3000 0000 0000 0000 0000 4905 a568 a593 0.........I..h..
000000e0: 0100 0800 0300 0300 0f00 a568 a593 0400 ...........h....
000000f0: 1400 0100 0000 0100 0000 0000 0000 0000 ................
00000100: 0000 1a00 a568 a593 0800 4800 0200 0100 .....h....H.....
00000110: 0100 4000 0100 0200 0000 0100 0000 0000 ..@.............
00000120: 0000 0000 0000 0000 0000 0000 0a0c da07 ................
00000130: 4252 4f41 4443 4f4d 0000 0000 a593 0100 BROADCOM........
00000140: 0800 0400 0300 1000 a568 .........h
m0:/ #

I cant differ what is chip anwsering or getting asked for, but I think some part of handshake is missing here. I'm thinking here in a way to reverse it: If I understood well, /system/vendor/bin/gps_daemon.sh is the responsable to launch proper GPSd. I can try switch to Stock blob and see what is missing in handshake with block device. I'll try, but since there is a issue about TEXTREL, i think it will not work, right?

---------- Post added at 01:26 PM ---------- Previous post was at 01:17 PM ----------

I prefer the current behavour. As I posted in Page 15, using Magisk to turn it on a Android GO device was more efficient than try to overclock/zram/whatever behaviour. RAM in this device is a issue and the changes made by the magisk module are indeed good. I'm also using Google *Go apps, Uber Go, Skype Lite, etc. And I see no issue at all with every app Ive installed here.

I see a considerable lag when device is awaking. The lag is worst if there is notifications on screen - unlock may take 5 seconds to be done with PIN. But no not warms me.

Battery is indeed a champion here: Last LOS I've installed drained battery in about 2h or less and phone only woked well if its in performance profile.

Performance profile is set in my battery config too and even this way, battery can take more than a day in standby or about 1h of use. Since my battery is very very old, I think its a perfect combination.

About changes in PowerHAL, i just think if a burstable time of high cpu requests isnt a good idea and set a game-mode (I dont know if its possible to be set on battery config) allowing much CPU as requested.