明少Oline
明少Oline
> > 与该问题为同一个问题 #8 解决方案 #6 > > 行不通，需要官方修改是最好的办法。 回调的页面 改成你自己的地址就行了
官方不改是因为那个oath2页面是有地址白名单的 而白名单就只有homeassistant.local
> > 这几天更新的很勤。 现在31版本勾选追加默认dns， 内核会报错 default nameserver should be pure IP" > > 看看配置文件default nameserver加了什么内容进去 33版本 勾选追加上游也会出现default nameserver should be pure IP提示 检查发现default nameserver这里好像少个空格  @vernesong 如果有需要的话 我去建一个新的issuse
> That's interesting - I didn't think a time interval for passive logging actually made sense. I'd be interested in seeing what it did. This PR adds a passive locations...
The passive location interval was a performance fix, so I tagged it as such. Technically we could move the timestamp closer to passive data and add context notes – but...
Since my OEM device upgraded to Android 15. The OOM issue persisted for two months despite multiple attempted fixes. The owner couldn't reproduce it due to more lenient WorkManager restrictions...
不行了 电网那边会判断账号是否频繁读取接口 多了就会限制api请求
The [v134](https://github.com/mendhak/gpslogger/releases/tag/v134) release (based on PR #1213) has already implemented similar functionality.
> [@LOVE2CMOL](https://github.com/LOVE2CMOL) Actually on reviewing the code, I'm not sure if this would help the situation described in this issue. The problem isn't too frequent passive logs between other passive...
> > with a 5s interval: record first data point > > This is irrespective of where it came from (eg GPS vs network vs passive)? If so that's exactly...