haarp
haarp
fyi, I've also collected some (preliminary) information on RBv3 [over here](https://github.com/kevinlekiller/cvt_modeline_calculator_12/issues/6) :)
This is unfortunate. I was looking forward to running this addon. Do you have an .xpi file for it? Also, Mozilla should really use a different approach. Instead of "disappearing"...
Ah, just after creating this issue I managed to make it work. Disabling and re-enabling the app worked. Maybe there's a bug preventing some sort of initialization the first time...
Honestly, there's no way you're getting more than a few hundred m accuracy just with GSM. You must be using GPS.
Version 0.0.1.4: I'm also noticing moderate battery usage. After 2 days on battery, GSMLocationBackend has accumulated over 20 minutes of CPU time!
Seems to indeed be cell polling. In App ops, I can see that GSMLocationBackend has used "cell scan" around 7 and a half million (!) times. In the two months...
> i think there is not that much to do. Maybe I am missing something, but what about only showing the overlay when the rotate button is to be displayed?...
> But the second overlay is basically an empty and invisible view.. this one is requesting the system to have a certain orientation. Therefore it needs to be active all...
It actually isn't an off-by-one error, I just used 99 and 100 as an example. This issue also presents itself when toggling between e.g. 60 and 100.
Cheers, those notes sounds familiar. Looks like DDC is hell of a mess of poorly implemented specs. Manual tests with ddcutil seem to work fine, unlike doing the same with...