It's a simple fix/recompile for a batterylog by Lucas Fraser to fix reporting energy readings broken in the app on sailfish 4+
original git: https://github.com/zeburon/sailfish-batterylog
my fork with fixes: https://github.com/mankysee/sailfish-batterylog/tree/release
Attachment | Size | Date |
---|---|---|
harbour-batterylog-1.3.3-1.aarch64.rpm | 125.4 KB | 11/12/2023 - 03:31 |
harbour-batterylog-1.3.3-1.armv7hl.rpm | 123.66 KB | 11/12/2023 - 03:31 |
harbour-batterylog-1.3.3-2.aarch64.rpm | 125.45 KB | 16/12/2023 - 15:28 |
harbour-batterylog-1.3.3-2.armv7hl.rpm | 123.69 KB | 16/12/2023 - 15:28 |
1.3.3
Comments
shults
Fri, 2023/12/29 - 21:23
Permalink
On Xperia 10iii it does not start.
mksfrank
Sun, 2023/12/31 - 03:11
Permalink
Have you tried both versions, -1 and -2? It can be down to some permissions misconfigure. Though I have no arm64 device to check the app anyway so without some debug information I don't think I can help in any way sadly.
Markkyboy
Tue, 2023/12/12 - 14:50
Permalink
Pretty simple to remedy (I believe), have a look here; https://github.com/sailfishos/sailjail-permissions there is an example of how a desktop file should look.
mksfrank
Tue, 2023/12/12 - 14:52
Permalink
thanks! I'll look into it!
ninepine
Tue, 2023/12/12 - 11:54
Permalink
I'm not clear why this App needs such extensive access permissions to run:
Access Microphone, Bluetooth, Camera, Internet, Location, Media Index, NFC, Play and record audio, Removable media, User directories, Web content.
Are these actually necessary please?
mksfrank
Tue, 2023/12/12 - 14:09
Permalink
tldr: I don't know :(
As far as my understanding goes this is because of permision system that was introduced in sailfish 4 but wasn't in place when the app was developed(it's last release was back in 2016) and therefore the app don't even know about permissions at all.
I don't have any expirience with sailfish development to be honest and all I've done is changed one file that was responsible for power readings and recompile the program using official guide. So in essence no, almost all of the permissions the program is asking are not required at all.
I can look into the whole permission thing and maybe it's something that I can address but no promises because of my lack of knowledge and to be frankly time :)
I will make sources available this week though so anyone can check the code and see for himself is it secure enough(and maybe I even got some luck and my fixes will be merged into the main program itself).