That's because before the last rule before setting to silent the profile was beep, so that's what is restored.
ok so I need a gap between rules (not possible rule one has an idle equivalent rule 2 which brakes the idea of having a gap in between) and default to have PSM auto20% (that is not in profilematic yet)
ok so I need a gap between rules (not possible rule one has an idle equivalent rule 2 which brakes the idea of having a gap in between) and default to have PSM auto20% (that is not in profilematic yet)
From my testing, and correct me if I'm wrong, but changing PSM mode with profilematic does not change the Auto percentage setting. So if you force PSM on with ProfileMatic, and then put it back to off, the real setting will be Auto 20%.
If I've understood correctly, you can just put to default rule PSM Off, and in Idle condition PSM on. Then when Idling PSM will be on, and otherwise it would be Auto 20%.
Thanks, that's valuable. So it's something in evaluating the condition. Have you installed FasterN9?
...it could be informative to see the logs between 5:57 - 6:20 when that problem happens.
I haven't FasterN9 installed.
Problem hasn't occured for couple of days now. I uninstalled and reinstalled ProfileMatic, so maybe something had gone wrong during previous installation.
I'll keep getting log for some time anyway, just in case the problem shows up again.
Problem hasn't occured for couple of days now. I uninstalled and reinstalled ProfileMatic, so maybe something had gone wrong during previous installation.
I'll keep getting log for some time anyway, just in case the problem shows up again.
I very much doubt it has anything to do with install going wrong. The background process either works or doesn't.
So if it used to misbehave 2-3 times a week, but works ok when running from terminal - that's a hint also to what could be the cause of the problem.
I have couple of possible causes in mind, but this needs test results, so thanks for trying it out.
I have submitted a fixed version to Nokia Store. Thanks for the bug report Diggler!
The fixed version is now finally available in store. This was the hardest update to get through QA, with many an e-mail passed between me and QA. Ironic, as this is also probably the smallest update ever.
The fixed version is now finally available in store. This was the hardest update to get through QA, with many an e-mail passed between me and QA. Ironic, as this is also probably the smallest update ever.
And the least downloadable update ever... I've been having random issues with it not applying any rules, which is sad since I barely got it to do exactly what I wanted it to do. So then I see an update that was supposed to fix issues, but unfortunately I can't download it. Which is odd, since there were 5 other updates at the same time, and they all downloaded fine.
I even removed ProfileMatic, hoping I could then install the newer version, but that didn't work.
I've been having random issues with it not applying any rules, which is sad since I barely got it to do exactly what I wanted it to do. So then I see an update that was supposed to fix issues
Unfortunately this update probably has nothing to do with what you're struggling with. This update only fixes restoring of previous ringing volume level, nothing more.
So what kind of problems you're having? Something similar than "kkarioja" above outlines or something completely different?
Originally Posted by
I even removed ProfileMatic, hoping I could then install the newer version, but that didn't work.
Anyone else having this issue?
I've had that issue with several different applications. Basically Nokia store is just unreliable. It has always eventually worked, but it's a frustrating problem for sure.
Odd. Well this sort of happened to me before, so I sat down and worked on it.
Basically something screwy or conflicting was in my apt repositories. It's happened once before, but doesn't make much logical sense that your program specifically wouldn't install. As I said, I updated 5 other packages, including mieru, firefox, meecast, etc. They all installed fine. I think what did it was mieru. It either wasn't installed fully, even though the "Applications" tab said it was. I also apparently installed the one from appsformeego-testing, since I now have a newer version than what appsformeego has available.
But once I fixed that (I also removed snowshoe-mobile, since it also decided to start pulling in qt5 beta packages) and now I have profilematic again.
Beauty is, I didn't have to recreate my profile, it automatically applied it. So if I have the issue again, I'll let you know so we can work together to see what the problem was, but it may have been something completely unrelated.