I think what that phrase is actually trying to convey is something different. Of course, htneb didnāt use that wording to stir up drama or to demand that every single feature theyāve added should immediately be implemented by Jolla. I think the point of saying āJolla, did you forget?ā was more about getting these features noticed and considered. Because when you really look at it, some of these features genuinely should be included by default. Even people here have acknowledged that certain features are actually necessary. And thatās exactly why I think Jolla should take an interest in this and give it some attention.
A lot of pretty basic stuff are missing yes. You donāt need to agree with all of the items, but things like sharing more than 1 picture at the same time in the gallery is not possible.
Simple things like cropping pictures; not possible.
When I receive a phone call; no overlay popup possible, instead I am being bothered with a full screen window forcing me to loose my focus on what I was doing, like answering a message.
There are definitely some things that some people would not use, of course.
But having a catchy slogan to the app, is one way to get the attention
(Which seems to be working )
Patchmanager is not really end-user friendly in my opinion, so Iāve made my own catalog browser instead, which became SaneFish
You can still use Patchmanager, sure.
For people who do not like to see SaneFish, you can also hide it.
SaneFish > About > Pulley > Hide SaneFish
@Dequei itās an apk bundled in the rpm, you can grab it out of it if you want.
I was thinking to release it as a separate download, but itās a bit less end-user friendly yet.
(Which is why Wireless Android Auto is hidden in the pulley menu)
Patchmanager itself doesnāt care where a patch comes from, all it needs is two files being in the right location.
The two ways that is usually done is either uploading things to web catalog, which brings some validation and things like screenshots.
It is also likely the variant whith the best user visibility as itās probably where most go looking for a patch.
Or, distributing rpm packages, and this is the recommended variant, if there are some additional requirements the patch has, such as depending on other packages, or indeed a specific OS version or architecture. Web Catalog cannot do those.
And of course rpms can include additional files which may be unsuitable for a web catalog patch (e.g. larger files, binaries or images etc).
Choosing the method is up to the developer of the patches.
just a small question: I saw in the description of the patchmanager that the patches are loaded into RAM instead of modifying the actual system files. Does this apply to patches from external sources (like openrepos) as well? This is my main concern, since, if I am to use these many patches that may not be properly vetted, I do fear some stability issues afterward.
@petrescatraian Yes, Patchmanager is exactly working like that. If a patch behaves bad, you can simply turn it off, or a restart of a phone will make it disable it
It does not modify any patched system files persistently, that is true.
However that doesnāt keep patches from doing what they want.
Note that if a patch happens to create something to upload your passwords to some malicious site and then brick your device, it can and will. Patchmanager can not prevent that.
If you suspect any patches being wonky in some way, make sure the āapply patches on bootā option is OFF so you have a chance of booting and disabling patchmanager or the suspect patch.