Hello, I have run the clock calibration routine.
The issue persists. The issue seems to be related to this notice showing up in the logs: Aug 28 00:34:41 sysmobts-v2 osmo-bts-sysmo[1022]: DMEAS NOTICE (bts=0,trx=0,ts=1,ss=0) 1886430/1422/00/42/14 no space for uplink measurement, num_ul_meas=104, fn_mod=78 (measurement.c:338) I am sorry but I am too much of a newbie to understand if this actually can be related. Thank you for help! Christoph Am 26. August 2025 16:14:52 UTC schrieb Joachim Steiger <jstei...@sysmocom.de>: >Hi, > >you may want to check your clock calibration. >either against a neighbor cell or if installed as option the gps clock source. > >clock calibration is a value stored on the device and can be overridden in >config in case it drifted too far over time. >this is not uncommon since the crystals age with use and time. >a recalibration every few years should be enough in most cases. > >the behavior of the phone sounds a lot like what happens if the phone gets >confusing clock-references from the networks it can receive and at some point >decides which one is 'right' and ignores whats not fitting that raster. > >regards > > >-- >- Joachim Steiger <jstei...@sysmocom.de> http://www.sysmocom.de/ >======================================================================= >* sysmocom - systems for mobile communications GmbH >* Siemensstr. 26a >* 10551 Berlin, Germany >* Sitz / Registered office: Berlin, HRB 134158 B >* Geschaeftsfuehrer / Managing Director: Harald Welte
