[Galaxy S III Android Development] css2020:
Update on this: the Lineage 14.1 glgps behaves the same way, in the meantime I managed to get a few more logs out of this thing, and it seems it runs into date inconsistencies due to the GPS week rollover and exits:

06-04 20:48:43.303 21598 21598 I slog : $737015I GlChovyCtrl::MeasureRefTime()
06-04 20:48:43.303 21598 21598 I slog : $737015I GL100 Tim [ 2000-Oct-19 18:48:44.211087, +/- 0.012015 sec ]
...
06-04 20:48:44.220 21598 21598 D slog : --GlPeTimeManager::Gross difference between initial time and Satellite time (619315194.990 > 100 sec)
06-04 20:48:44.220 21598 21598 D slog : --GlPeTimeManager:: At Lms:103941.000000 UncorrectedTimeMgr Time=[1084 413270.083000000 1000000(unc us)] Satellite Time=[2108 413265.073000000 12000(unc us)] Delta:619315194.990000010 sec
06-04 20:48:44.220 21598 21598 D slog : --GlPeTimeManager::Error is in initial time. Reset required!
...
06-04 20:48:44.338 21598 21598 D slog : $738058C ReloadComponents() PSF={DERATE_TIME 0x0 RECOVER_JOBS 0x0} Need={Reset 1 Restart 1} Abort 0
06-04 20:48:44.338 21598 21598 D slog : $738058C Abnormal GlEngine stop. Initial time estimate was bad
...
06-04 20:48:44.351 21598 21598 D slog : BrcmGpsHalGpio::Standby
06-04 20:48:44.352 21598 21598 D slog : WriteSysfs pin [1] value[0] successful
06-04 20:48:44.352 21598 21599 D slog : GPSIS.OUT.gps_release_wakelock_cb();
06-04 20:48:44.352 21598 21598 D slog : GpsHalPlatfCloseLogFile
06-04 20:48:44.358 3095 3353 D gpslogd : IPC Connection closed by peer (GpsInterface)

After that it needs quite a few attempts to restart properly again, the logs then always show the same assert (probably that the GPS chip is in an unexpected state):

06-04 20:48:47.554 25442 25442 D slog : UpdateGpsStatus(SESSION_BEGIN(1))
06-04 20:48:47.554 25442 25443 D slog : GPSIS.OUT.gps_status_cb(GPS_STATUS_SESSION_BEGIN[1]);
06-04 20:48:47.554 25442 25442 D slog : GpsInterfaceStateRunningRequest: OnStart
06-04 20:48:47.554 25442 25442 E slog : ASSERT in /tmp/12075037/customers/Asustek/Tabletandroid/../../../proprietary/deliverables/android/gps_interface/../gpsd/common/GpsInterfaceStateRunningRequest.cpp:39: ASSERT(0)
06-04 20:48:47.554 25442 25442 D slog : BrcmGpsHalGpio::Standby
06-04 20:48:47.555 25442 25442 D slog : WriteSysfs pin [1] value[0] successful
06-04 20:48:47.555 25442 25443 D slog : GPSIS.OUT.gps_release_wakelock_cb();
06-04 20:48:47.555 25442 25442 D slog : GpsHalPlatfCloseLogFile
06-04 20:48:47.560 3095 3353 D gpslogd : IPC Connection closed by peer (GpsInterface)

I think the GPS never worked 100% flawlessly on earlier versions either - I remember especially these sudden dropouts of a couple of minutes, probably these would show up in the logs in a similar way. But I guess resetting the GPS chip was working better.

---------- Post added at 05:18 PM ---------- Previous post was at 04:56 PM ----------

Have a look at post #232, I switched to zzmove and have the feeling the battery life is better. With the default pegasusq governor, I experienced some unusual drain, though infrequent, but especially overnight without any activity - e.g. CPU monitor showed all CPUs on at 1.4 GHz. With zzmove I haven't seen this. But still, battery life is not as good as Lineage 14.1, but still reasonable.

The charging LED has to be enabled (see changelog for the last build), but this unfortunately only works after startup. The charging itself does work, however. But you're right there, there's something wrong with the charging animation: I often have the problem that I can't start the phone after I plug it in and the animation shows. Only after disconnecting, waiting a bit and then holding the power button again, it will boot (and then I connect it again to charge). In this case, the charging LED also won't light up even after the system is up, only after disconnecting and connecting again.

And concerning performance: give it a try - for me, it feels a lot better than Lineage 14.1, almost like a new device :) otherwise I wouldn't bother debugging the broken GPS and just flash back the latest 14.1 build...