@DJac said in reading voice mms in MESSAGES app:

yes, when i try from UT to UT, it work.
in my case, it come from android.
but the possibilty to download voice messages and use receive them from android could increase the app.
and this is why i post it in app devlopment.

some logs would be helpfull, probably a format issue.
Tested from an Android <> UT and it works too

@DJac said in reading voice mms in MESSAGES app:

hello,
i meet a difficulty to read a voice message in the sms app. I can read it but with simple way :

• no reading in the conversation
• not possible to download it directly
• so, i transfert it to myself and download the sending message. and read the file on the mp4 reading app....

is it a specific probleme with me ?

hmm it works here when recording from UT and send to self at least. Do you confirm ?
btw, why posting in App Development ?, this is more a "support" thing than app dev

The issue has been found. It will fix for new comers and those who upgrade to 24.04.
But unfortubatly it will not fix if user already hit it.

Thanks for your feedbacks

@vverve said in Battery saver on 24.04:

@lduboeuf said in Battery saver on 24.04:

hmm, have you installed 24.04.2 from existing 20.04 or a clean install ?
Because a user have reported that use case on a clean install: https://gitlab.com/lduboeuf/battery-saver/-/issues/8

Clean 24.04-2.x install,

Here too;
Creating ~/.config/systemd/user manually solved the issue.

Thanks for all your app & work on UT !!

Ah that is the issue, i should fix it, but i always postpone it since need to ask the OpenStore team for review each time before publishing it.

@vverve said in Battery saver on 24.04:

Salut @lduboeuf
Tag as solved , a different problem , but main topic on your app with noble,so posting it here .
On pixel 3a xl , 24.04-2.x ,app start , button on does nothing , on turn blue , says stopped .
Log , if it can help :
Failed to enable unit: Unit file batterysaver.service does not exist.
qml: start returned false
qml: init returned false

Just ask(with hints please)
how to get log you need to pinpoint the bug , would be glad to share those

hmm, have you installed 24.04.2 from existing 20.04 or a clean install ?
Because a user have reported that use case on a clean install: https://gitlab.com/lduboeuf/battery-saver/-/issues/8

For the logs, from LogViewer app is fine, or from Terminal with journalctl -b | grep batterysaver .

@wally said in Tip: call a contact with one hand (secret UT key !):

@lduboeuf Aha! I've gotten somewhere. In short, it relates to what language my system is set to.

I was suspecting some sort of regional dialing syntax issue. I tried changing my location in System Settings, to no effect. Then I tried changing my language to Français (France), and sure enough, up comes the cidrerie after dialing +33029, or also after dialing 029.
Attempting to dial Canadian numbers while set to Français (France) didn't yield any predictions regardless of syntax.

It only then occurred to me that my language is normally set to English (UK), not English (Canada). Setting it to English (Canada), I CAN get certain contacts to be predicted, but only if I start by dialing +1, and only then for contacts that happen to have the number saved starting with +1. My Contacts seem to have a wide variety of snytaxes, some starting in +1, others simply with 1, others without the regional code at all. Also some using parentheses, some not. Perhaps this relates to a Contact list that has been exported from one device to another and from 16.04 to 20.04, with different contacts being added at different times. The contact list has always been within UT.

I have never dialed a plus sign, living here. Using Google Maps, if I set my VPN to Canada, I see (555) 555-5555, where if set to, for example, France and searching a Canadian business I see +1 555-555-5555.
So in short, even with my language set to Canadian English, I wouldn't have stumbled across any predictions based on phone numbers. It only works for numbers stored with a +, and only if I type the + when dialing.

If it weren't too complicated a change, perhaps if the numeric prediction search dropped all special characters like + and (, it would work more internationally? But I have no idea how feasible this is.
The predictions based on contact name are probably useful to a lot more people anyway, and I don't want to create more work for you. Just trying to be helpful in the small ways that I can by testing and reporting.

Thanks for the feedback, will look at it one day. But i'm surprised prefixes change with language and not timezone

@wally said in Tip: call a contact with one hand (secret UT key !):

@lduboeuf Pardon my miscommunication! I only thought the predictions were bad when I didn't understand that the T9 element was happening, and they seemed to come out of nowhere and not relate to anything. A laugh solely at my own ignorance

But I don't get any predictions based on phone number, whether I use the region prefix or not. All predictions that I see are T9 based.
Once I have entered the full phone number of a contact in the dialer, it displays the contact name. But that's clearly a different feature, as the contact name does not appear in a box like it does with predictions.
I can type all but the final digit, with or without regional code, without seeing a prediction based on phone number.
I thought it might relate to parentheses in phone numbers as displayed in Contacts, which is a regional custom here, but I've found contacts without parentheses and these don't come up either.
I've also just tried adding a nice Ciderie de Bretagne as a contact, rebooting, and dialing the number, both with and without the 33 - still no prediction based on number.

Oneplus Nord N10, 20.04 OTA 11, Canada.

In any case, i love this T9 feature. Thank you!!

ok, i will need to look at it then, because it works for me by either using a prefix '+33' or start with 06 or 07

@wally said in Tip: call a contact with one hand (secret UT key !):

As somebody who still often "dials" a phone number, I always just figured those contact names that appeared as I started dialing were predictions based on the phone number.. but pretty bad predictions
Finally I understand! That seems like a really useful feature!
(also, I think T9 WAS the one where you only had to press each number a single time.)

As i did the T9 feature few years ago, i'm interested in what you mean by "pretty bad predictions" when typing numbers. Works well on my side when starting to dial for a number and/or for the letters. But may have some issue if e.g number is stored with a region prefix or not.

@gpatel-fr
oh funny!.
But seems buggy, it shows the contact profile even in edit mode on click, instead of filling the number

Could anyone that has that kind of issue remember the steps done ?

e.g from 20.04 stable to 24.04.x daily, then back to 24.04.1 stable, then....
If there were remote calendars, etc...

@dR0W said in Calendar and Alarms issue:

@lduboeuf I've removed the mentioned lines and executed the script again and got the same error. The three lines deleted, are restored once script finished.

I've restarted the phone after deleting evolution sources folder, and I have to say you that now both apps work as expected.

I didn't manipulate evolution data server before.

THANKS A LOT for your help!!!!!

i don't like that work around, but if it is fine for you, glad it works
Now we need to know what has happened

Also, i wonder where does that lower case entries come from, i've checked even a Xenial device, and there are not in lower case too. Did you manipulate evolution data server before ?

Well it seems there also others entries that are duplicated:

The easiest way to fix it if you don't care about cleaning all alarms and calendars is to remove the
/home/phablet/.config/evolution/sources folder then restart,

@dR0W said in Calendar and Alarms issue:

[Data Source]
displayname=Personal
displayname[ar]=شخصي
displayname[as]=ব্যক্তিগত
displayname[ast]=Personal
displayname[be]=Асабістыя
displayname[bg]=Лични
displayname[bn]=ব্যক্তিগত
displayname[bn_in]=ব্যক্তিগত
displayname[bs]=Lično
displayname[ca]=Personal
displayname[ca@valencia]=Personal
displayname[cs]=Osobní
displayname[cy]=Personol
displayname[da]=Personligt
displayname[de]=Persönlich
displayname[dz]=རང་དོན།
displayname[el]=Προσωπικά
displayname[en@shaw]=𐑐𐑻𐑕𐑩𐑯𐑩𐑤
displayname[en_ca]=Personal
displayname[en_gb]=Personal
displayname[eo]=Persone
displayname[es]=Personal
displayname[et]=Isiklik
displayname[eu]=Pertsonala
displayname[fa]=شخصی
displayname[fi]=Henkilökohtainen
displayname[fr]=Personnel
displayname[ga]=Pearsanta
displayname[gl]=Persoal
displayname[gu]=ખાનગી
displayname[he]=אישי
displayname[hi]=व्यक्तिगत
displayname[hr]=Osobno
displayname[hu]=Személyes
displayname[id]=Pribadi
displayname[is]=Einka
displayname[it]=Personale
displayname[ja]=個人
displayname[kk]=Жеке
displayname[km]=ផ្ទាល់​ខ្លួន
displayname[kn]=ವೈಯಕ್ತಿಕ
displayname[ko]=개인
displayname[lt]=Asmeniniai
displayname[lv]=Personisks
displayname[mai]=व्यक्तिगत
displayname[mk]=Лично
displayname[ml]=വ്യക്തിപരം
displayname[mr]=खाजगी
displayname[nb]=Personlig
displayname[ne]=व्यक्तिगत
displayname[nl]=Persoonlijk
displayname[nn]=Personleg
displayname[oc]=Personal
displayname[or]=ବ୍ଯକ୍ତିଗତ
displayname[pa]=ਨਿੱਜੀ
displayname[pl]=Osobiste
displayname[pt]=Pessoal
displayname[pt_br]=Pessoal
displayname[ro]=Personal
displayname[ru]=Личное
displayname[rw]=Bwite
displayname[sk]=Osobné
displayname[sl]=Osebno
displayname[sq]=Personale
displayname[sr]=Лично
displayname[sr@latin]=Lično
displayname[sv]=Personligt
displayname[ta]=தனிப்பட்ட
displayname[te]=వ్యక్తిగత
displayname[tg]=Шахсӣ
displayname[th]=ส่วนบุคคล
displayname[tr]=Kişisel
displayname[ug]=شەخسىي
displayname[uk]=Особисте
displayname[vi]=Cá nhân
displayname[xh]=Ezakho Buqu
displayname[zh_cn]=个人
displayname[zh_hk]=個人
displayname[zh_tw]=個人
enabled=true
parent=local-stub
DisplayName=Sin nombre
Enabled=true
Parent=

[Calendar]
backendname=local
color=#77216f
selected=true

[Ubuntu]
accountid=0
applicationid=
autoremove=true
writable=true
metadata=
AccountId=0
ApplicationId=
AutoRemove=true
Writable=true
Metadata=

[Lomiri]
accountid=0
applicationid=
autoremove=true
writable=true
metadata=
AccountId=0
ApplicationId=
AutoRemove=true
Writable=true
Metadata=

ok, just remove this 3 lines in the [Data Source] section:

DisplayName=Sin nombre
Enabled=true
Parent=

and try to run again the script, if it fails again, see which file fails.
Try then to open calendar-app/clock-app ( not sure but maybe a reboot is needed)

@dR0W said in Calendar and Alarms issue:

@lduboeuf Yes, I did it.

could you show the output of
cat /home/phablet/.config/evolution/sources/system-calendar.source

@dR0W said in Calendar and Alarms issue:

@lduboeuf This is what I get:

phablet@ubuntu-phablet:~$ /usr/share/session-migration/scripts/eds-lomiri-ext-migration.py
Migrating EDS sources using Ubuntu extension to Lomiri extension
be8033a4c49ef662e4ecf98a72a5f0d2146fcdc0.source: already has 'Lomiri' section, don't migrate.
Traceback (most recent call last):
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 50, in <module>
    main()
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 40, in main
    if migrate_single_source(source_path):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 10, in migrate_single_source
    source.read(source_path)
  File "/usr/lib/python3.12/configparser.py", line 684, in read
    self._read(fp, filename)
  File "/usr/lib/python3.12/configparser.py", line 1075, in _read
    raise DuplicateOptionError(sectname, optname,
configparser.DuplicateOptionError: While reading from PosixPath('/home/phablet/.config/evolution/sources/system-calendar.source') [line 83]: option 'displayname' in section 'Data Source' already exists
phablet@ubuntu-phablet:~$

interesting, some configs are corrupted. Did you have once installed a 24.04.2.x version then back to 24.04.1 or 20.04 before ?

@dR0W said in Calendar and Alarms issue:

@lduboeuf This is the log for Calendar and Clock apps:

Calendar log: https://dpaste.com/54LDR8SMF
Clock log: https://dpaste.com/5MRHK6WB2

Apparently, the problem is the same as yesterday

hmm, i don't see why it failed.
could you manually run and share to us the output:
/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py

@dR0W said in Calendar and Alarms issue:

@lduboeuf said in Calendar and Alarms issue:

grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch

This what I get now:

phablet@ubuntu-phablet:~$ grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch
migrated=lomiri-system-settings-datahome-migration.sh;lomiri-gsettings-schema-name-change.sh;lal-cache-migration.sh;lomiri-schemas-gsettings.sh;lomiri-thumbnailer-gsettings-schema-name-change.sh;lomiri-keyboard-gsettings-schema-name-change.sh;luitk-config-migration.sh;eds-lomiri-ext-migration.py;ubuntu-system-settings-keyboard-accountsservice-to-gsettings.py;lomiri-accountsservice-schema-name-change.py;lomiri-system-settings-greeter-data-rename.sh;lomiri-schemas-accountsservice.py;dark-theme-migration.sh;lomiri-schemas-launcher-system-app-rename.py;lomiri-wizard-has-run-migration.sh;03_run-account-polld-hook;lomiri-telephony-service-greeter-data-migration.sh;ldm-db-migration.sh;ubuntu-system-settings-sound-gsettings-to-accountsservice.py;lomiri-system-settings-gsettings-schema-name-change.sh;messaging-app-name-change.sh;lomiri-cache-migration.sh;content-hub-gsettings-schema-name-change.sh;dialer-app-name-change.sh;morph-browser-name-change.sh;03_migrate_signon;lomiri-push-service-rename-migration.sh;lomiri-push-service-migrate-settings.py;libusermetrics-rename-gsettings.sh;address-book-app-name-change.sh;lomiri-thumbnailer-cache-migration.sh;
phablet@ubuntu-phablet:~$

Ok so the migration has run. What is your logs now on calendar and clock app ?

@Ernst-Jan15
Maybe a reinstall with 24.04.1 stable via the installer

@dR0W could you try :
grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch

if it finds something then the migration has run. But something else needs to be done.
Could you just reboot just in case ?