Patches by nephros

Applications
#47

As a matter of a fact that was the first thing I did. I already have two patches working, both were downloaded and installed through Patchmanager, and I have been trying to get Fuzzy Time as well, but when I click the activation button on the left of the “Installed Patches” page, activation fails.

Thank you! I did not know this and it is good to know; unfortunately I just tried this way too, and it did not work.
So far I have:
1 - Downloaded and installed the patch from within Patchmanager: patch is there, activation failed;
2a- Downloaded Fuzzy Time 1.0.4.rpm from Openrepos, installed from File Manager (click on .rpm file, and on “install” window afterwards): patch is there, activation failed;
2b- Same as above, but after editing the .patch file in the rpm, replacing usr/lib entries with usr/lib64: activation failed;
3 - Downloaded Fuzzy Time 1.1.0.tar.gz from Webcatalog, edited the .patch file replacing usr/lib entries with usr/lib64, copied the .patch file in usr/share/patchmanager/patches/patch-fuzzy-time: patch is there, activation failed.

I mean, it is surely my fault (my phone’s, at this point) somewhere, but I have no idea what may be wrong.

#48

You could take a look at the patch log, after the activation fails. Have you tried disabling the other patches and only test fuzty time? Maybe there is a conflict…

#49

Hi, I tried to use the Patch Glass Popups, but it isn’t compatible to 4.5.0.19.

#50

It is not explicitely compatible, but for me it does work if I activate developer mode in the patch manager settings

1 Like
#51

It’s not developer mode any more, it’s now called Version Check. And it has the bug mentioned above ATM.

3 Likes
#52

No. It was me.

I turned the phone off (for other issues) and first thing after restart I tried to activate the patch and it worked!

Thank you for the help, though. I learned something.

And thank you @nephros for the help and for these amazing “toys”, the useful ones, and the joyful ones.

1 Like
Bluetooth search: show always device MAC address
#53

Just pushed a new one to Web Catalog: Bluetooth Car Mode

Three effects:

  • Shows BT devices as a large button grid instead of a list
  • Makes the bluetooth toggle in the top menu launch Bluetooth Settings when it is activated
  • Allows to set a favorite device. This will be connected to automatically.

Intended for car use and other situations where fiddling with the device is inappropriate. Drive safely!

Currently only tested in 4.4, but likely works on other releases.

9 Likes
#54

That we already have. Long press on any top menu toggle always open settings. :wink:
Thanks for the other effects though.

#55

Reminds me of an in-car functionality I had on :ahem: other OSes: when detecting a bluetooth device (car) turn on the hotspot. You know, for cars that don’t always call home…
Or maybe Situations could do that hmm.

#56

Screenshot attached to announcement post would be cool. 1000 words etc

#57

There are now screenshots added to the web catalog entry.

https://coderus.openrepos.net/pm2/project/patch-bt-carmode

5 Likes
#58

Droidian on that galaxy S9 next please:)

#59

Hmm needs updating for 4.5.0.x…

#60

Ah, sometimes buttons are the answer!

#61

You’re saying it doesn’t apply on 4.5?

#62

Nonono, they’re not Buttons! No. They are… square things. Slates. That you can tap. So TappySquares or InteractiveSlates.

Not Buttons, can’t be, that would be Like, and We are Unlike.

3 Likes
#63

well, if you phrase it that way…
Actually also a tappable List of entries could be interpreted as lengthy buttons.
Your arrangement however looks pretty nice. I consider to install the patch although I don’t use cars.

#64

Or InteractionSlate? Yes, of course. Not buttons. Bad UI mojo. Bad. (I gotta get rid of some buttons!)

1 Like
#65

It would seem so

----------------------------------
Dry running patch file
----------------------------------

checking file usr/lib64/qt5/qml/Sailfish/Bluetooth/BluetoothDeviceColumnView.qml
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 27 with fuzz 1 (offset 9 lines).
Hunk #3 succeeded at 70 (offset 12 lines).
Hunk #4 succeeded at 127 (offset 12 lines).
Hunk #5 succeeded at 162 (offset 12 lines).
Hunk #6 succeeded at 179 (offset 12 lines).
Hunk #7 succeeded at 194 (offset 12 lines).
1 out of 7 hunks FAILED
checking file usr/share/jolla-settings/pages/bluetooth/EnableSwitch.qml

*** FAILED ***
1 Like
#66

Thanks, I shall look into that.

1 Like