Back

@droidian I wish it could be possible to get F(x)tec that easy Such a cool device.

@Shatur it really is!

@danialbehzadi which device? Do you have some other updates pending in the Software app?

@droidian
On miatoll. No. It's completely updated. And ringtones are reverted to the default one and doesn't change too.

@danialbehzadi some metapackage has been removed perhaps? Could you try installing the droidian-phosh-full package if you have it missing?

@droidian
Thanks. It fixes the dark mode and color accent in apps; but the phosh and osk are still using the default blue and ringtones are stuck to default.

P.S: I found out that the vibration is completely gone too.

@danialbehzadi are you using a custom GTK+ theme? Accent colours are enabled only on Adwaita (and adw-gtk3 in Droidian) to avoid messing up 3rd party themes.

Will investigate on ringtones tomorrow. Vibration stuff has not been touched in 100, so it's curious. Does the device vibrate if you run fbcli from a terminal?

@droidian
By auto setting the high constraint mode and revert it, phosh and osk now adopt the accent color, but still no vibration and custom ringtones. I checked with fbcli and there are no vibration there too.

@danialbehzadi if you dist-upgrade now, is the custom ringtone issue fixed? Just pushed an update

@droidian
Is there a package for this? Cause I got the list update, but no packages needs an upgrade

@danialbehzadi sorry, there was a mishap in the update server, it should show up since this (European) afternoon, packages are `droidian-phosh-minimal` and `sound-theme-phosh`

@droidian
So Thanks. The sound is now fixed.
Now only the vibration is missing…

@danialbehzadi if you run this python snippet (you should install python3-gbinder first), is the vibration working? https://gist.github.com/g7/6a4db04561447ee98e48f2736a4e5f50

@droidian

```
Traceback (most recent call last):
File "/home/droidian/virba.py", line 8, in <module>
assert remote != None
^^^^^^^^^^^^^^
AssertionError
```

@danialbehzadi hah, interesting... anything if you do

```
binder-list -d /dev/hwbinder | grep vibra
```

and

```
binder-list -d /dev/binder | grep vibra
```

if nothing appears, most likely there is something gone awry in the underlying Android HAL (checking/pastebining `sudo logcat` might help finding some clues)

@droidian
Nothing…
Here is the catlog:
https://paste.ubuntu-ir.org/ucxk

@danialbehzadi ctrl+f vibra doesn't bring anything :(

Is there something interesting in dmesg? If the Android init attempted to start the vibra service there should be a trail there

@droidian
a quick `sudo dmesg | grep -i vib`:
https://paste.ubuntu-ir.org/fhvu

@danialbehzadi I suppose if you look at the current processes with `ps aux` you don't find anything regarding `vendor.qti.hardware.vibrator` ?

Does the hal launch manually if you do something like

```
sudo lxc-attach -n android /vendor/bin/hw/vendor.qti.hardware.vibrator@1.2-service
```

?

@droidian
https://paste.ubuntu-ir.org/feem

@danialbehzadi thanks and sorry for the late reply. Could you try running `fbcli` with `G_MESSAGES_DEBUG=all` ?

Also, could you try running the same gist I pasted before (https://gist.github.com/g7/6a4db04561447ee98e48f2736a4e5f50) replacing `android.hardware.vibrator@1.0::IVibrator` with `android.hardware.vibrator@1.2::IVibrator` ?

in the lxc-attach shell, could you run

strace -s 1000 /vendor/bin/hw/vendor.qti.hardware.vibrator@1.2-service

?

Thanks! :)

@Idcrafter you might want to try to port :) https://github.com/droidian/porting-guide/

We have some experimental images for 5.10-android12 GKI kernel, not sure which Pixel devices use that (6, 6a I think)

@droidian My Pixel 6 Pro currently uses Kernel 5.10.209 on CalyxOS Android 15 which would seem like a obstacle with it due to the bootloader preventing from downgrading to any thing under Android 13 and this being Android 12 but thanks i'll look into it when there is one for Android 13.