[OnePlus 3 & 3T Cross Device Development] [GER]Roxxor:
So does anybody else have issues with GPS? Like said in my post before, there is simply no satellites shown. Changing the NTP Server to Europe in the GPS config fixed it for a day. Now it doesnt work again. I also tested Oxygen OS to exclude an hardware flaw, I have no issues getting a fix in OOS.

I now set set the logging level to verbose, an thats what is repeatedly shown:

04-21 08:18:17.370 581 1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
04-21 08:18:17.370 581 1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 69
04-21 08:18:17.371 581 1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
04-21 08:18:17.371 581 1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
04-21 08:18:18.372 581 1512 V LocSvc_api_v02: locClientIndCb:949]: Indication: msg_id=36 buf_len=18 pCallbackData = 0x7aa9aaa350
04-21 08:18:18.373 581 1512 V LocSvc_api_v02: locClientGetSizeByEventIndId:2382]: event ind Id 36 size = 488
04-21 08:18:18.373 581 1512 V LocSvc_api_v02: locClientGetSizeAndTypeByIndId:730]: indId 36 is an event size = 488
04-21 08:18:18.373 581 1512 I LocSvc_ApiV02: <--- globalEventCb line 115 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
04-21 08:18:18.373 581 1512 V LocSvc_ApiV02: globalEventCb:120] client = 0x7aa9aaa350, event id = 36, client cookie ptr = 0x7b39aaa110
04-21 08:18:18.373 581 1512 V LocSvc_LBSApiV02: eventCb:61] client = 0x7aa9aaa350, event id = 36, event name = QMI_LOC_EVENT_POSITION_REPORT_IND_V02 payload = 0x79e4f0ea30
04-21 08:18:18.373 581 1512 D LocSvc_ApiV02: eventCb:3954]: event id = 36
04-21 08:18:18.373 581 1512 D LocSvc_ApiV02: Reporting position from V2 Adapter
04-21 08:18:18.373 581 1512 D LocSvc_ApiV02: reportPosition:2264 QMI_PosPacketTime 1779 (sec) 137992285 (nsec)
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: flags: 0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: source: 0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: latitude: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: longitude: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: altitude: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: speed: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: bearing: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: accuracy: 0.000000
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: timestamp: 0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: rawDataSize: 0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: rawData: 0x0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: Session status: 2
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: Technology mask: 0
04-21 08:18:18.374 581 1512 D LocSvc_LocApiBase: SV used in fix (gps/glo/bds/gal/qzss) : (0/0/0/0/0)
04-21 08:18:18.374 581 1512 D LocSvc_IzatAdapterBase: reportPositionEvent: default implementation invoked
04-21 08:18:18.374 581 1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
04-21 08:18:18.374 581 1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 70
04-21 08:18:18.374 581 1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
04-21 08:18:18.375 581 1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0