maemo.org - Talk
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   2.2.0 EA / Mouhijoki (https://talk.maemo.org/showthread.php?t=100344)

peterleinchen 2018-07-10 20:38
Re: 2.2.0 EA / Mouhijoki
 
No problem with e-mail notifications on my Jolla C.

Saturn 2018-07-10 20:59
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by peterleinchen (Post 1546135)
No problem with e-mail notifications on my Jolla C.

Thanks, that is useful.

Just to clarify, mine is MfE against Exchange server 14.1

Is yours or someone else similar?

peterleinchen 2018-07-10 21:18
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by Saturn (Post 1546137)
Thanks, that is useful.

Just to clarify, mine is MfE against Exchange server 14.1

Is yours ... similar?
Nope, I have only standard (manually configured) IMAP accounts.

olf 2018-07-10 22:23
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by Kabouik (Post 1546052)
[...]
I have run "version --verify", several packages are not in the right version:

Code:
[nemo@Sailfish ~]$ version --verify
[...]
One ore more packages are not at the expected version for Sailfish OS 2.2.0.29 (Mouhijoki)
(+ = expected version, - = installed version)
I have tried reinstalling them, [...]
IMHO the "+" / "-" output of version --verify is a bit irritating, but you seem to have these packages installed in newer versions than available in Jolla's repositories for SFOS 2.2.0.29!
So your subsequent results are IMO somewhat expected.

As no packages seem to be missing and everything is running fine, I wouldn't put much effort into investigating why.

pichlo 2018-07-11 05:03
Re: 2.2.0 EA / Mouhijoki
 
@Saturn, no problem with email notifications on my Jolla 1 either. Including Exchange emails. Sorry, no idea what Exchange server but I seriously doubt that matters anyway.

There is one annoying thing with email notifications though, but I believe it is "as designed". Just one of many bad design ddecisions. Say you are half between automatic email checks (or in an off-peak period for Exchange emails) and you have new emails waiting that the phone does not know about yet. You select an account (i.e. not in the global view with all the accounts, where such a thing might be forgiven) and do a manual update. The new emails appear on the list (good) and you get a notification (bad). Why on earth do I need a notification? Audible notifications are for telling me that something has happened, check the screen. But here, I am looking right the at it. Annoying.

peterleinchen 2018-07-11 06:10
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by olf (Post 1546141)
IMHO the + / - output of version --verify is a bit irritating, but you seem to have these packages installed in newer versions than available in Jolla's repositories for SFOS 2.2.0.29!
So your subsequent results are IMO somewhat expected.

As no packages seem to be missing and everything is running fine, I wouldn't put much effort into investigating why.
Right.
Probably some other (mer?) repo active during upgrade???

I would try:
pkcon refresh
pkcon install --allow-reinstall --allow-downgrade sailfish-content-*


--side note
as already asked: does anyone know what these droid-vibrator packages are? at least I am not the only one ;)

taixzo 2018-07-11 16:40
Re: 2.2.0 EA / Mouhijoki
 
Just updated, and enabled fingerprint unlock. I noticed an inconsistency: if you have it set to lock after a timeout (I set mine to 10 minutes), before that timeout fingerprint unlock doesn't work, while after that, swipe unlock doesn't work, so you have to guess at how long it's had the screen locked to know which way to try unlocking it. It would be nice if fingerprint worked to unlock even if the pin code hasn't kicked in yet.

Kabouik 2018-07-12 23:27
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by peterleinchen (Post 1546150)
Right.
Probably some other (mer?) repo active during upgrade???

I would try:
pkcon refresh
pkcon install --allow-reinstall --allow-downgrade sailfish-content-*


--side note
as already asked: does anyone know what these droid-vibrator packages are? at least I am not the only one ;)
Thanks. I tried the command you recommended but it returns the following:

Code:
nemo@Sailfish ~]$ pkcon install --allow-reinstall --allow-downgrade sailfish-content-*
Resolving                                      [                      ] (0%)  Package not found: sailfish-content-*
Command failed: This tool could not find any available package: No packages were found
This is weird because "pkcon search sailfish-content" does fin packages. I have tried with removing the "*" in the command, but same issue. Does pkcon install need exact package names one by one?

As a side note, "pkcon refresh" needed to be run as root, which kind of surprised me. I always thought pkcon didn't need root permissions in the past, did it change? Same thing happens with "ssu ur":

Code:
[nemo@Sailfish ~]$ ssu ur
WARNING: ssu.ini does not seem to be writable. Setting values might not work.

taixzo 2018-07-13 02:15
Re: 2.2.0 EA / Mouhijoki
 
Ok, just noticed a huge problem with this release on Xperia X: bluetooth speakers no longer work. They connect, however audio still comes out of the phone speakers for Sailfish apps, and doesn't come out at all for Android apps.

karlos devel 2018-07-13 03:47
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by taixzo (Post 1546207)
Ok, just noticed a huge problem with this release on Xperia X: bluetooth speakers no longer work. They connect, however audio still comes out of the phone speakers for Sailfish apps, and doesn't come out at all for Android apps.
to fix the bluetooth issue temporally ,go to bluetooth settings then disconnect/connect the device that you try use it

colin.stephane 2018-07-13 08:18
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by peterleinchen (Post 1546150)
Right.
Probably some other (mer?) repo active during upgrade???

I would try:
pkcon refresh
pkcon install --allow-reinstall --allow-downgrade sailfish-content-*


--side note
as already asked: does anyone know what these droid-vibrator packages are? at least I am not the only one ;)
Hi peterleinchen,

Could it be related to : URL ???

A++

taixzo 2018-07-13 16:19
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by karlos devel (Post 1546208)
to fix the bluetooth issue temporally ,go to bluetooth settings then disconnect/connect the device that you try use it
This causes audio to stop coming out of my phone speakers, but it does not come out of the bluetooth speaker.

Fellfrosch 2018-07-13 16:25
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by taixzo (Post 1546207)
Ok, just noticed a huge problem with this release on Xperia X: bluetooth speakers no longer work. They connect, however audio still comes out of the phone speakers for Sailfish apps, and doesn't come out at all for Android apps.
Bluetooth on XperiaX with Sailfish is a mess! I have these problems all the time, especially with my car systems. I had never any problems with my Jolla1 and still don't have.

Kabouik 2018-07-13 16:49
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by taixzo (Post 1546207)
Ok, just noticed a huge problem with this release on Xperia X: bluetooth speakers no longer work. They connect, however audio still comes out of the phone speakers for Sailfish apps, and doesn't come out at all for Android apps.
I am surprised that it just started to happen with this version on Sailfish X: it's a long standing issue on my Jolla C since more than three or four updates. I would say it mostly happens with old Bluetooth devices, like cars. It's hard to reproduce. Sometimes it works and will work flawlessly multiple times in a row, sometimes it just stops working, and in that case unpairing and pairing again is what worked the best for me (but not always necessary, and not always working).

karlos devel 2018-07-13 17:36
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by taixzo (Post 1546225)
This causes audio to stop coming out of my phone speakers, but it does not come out of the bluetooth speaker.
well with that trick helped me to connect(get stream pass) to bluetooth slaves, first connect ur xperia x with ur bluetooth speaker, when both are connected but audio not come out on the speaker ,go to bluetooth setting and tap twice the bluetooth-speaker-name to disconnect y connect, then the stream going pass :)

olf 2018-07-13 20:36
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by Kabouik (Post 1546205)
[...]Does pkcon install need exact package names one by one?
IIRC, yes, wildcards do not work in pkcon.
But you can address multiple packages in a single line / command.

Quote:
Originally Posted by Kabouik (Post 1546205)
As a side note, "pkcon refresh" needed to be run as root, which kind of surprised me. I always thought pkcon didn't need root permissions in the past, did it change?
IIRC, that was the case, when Warehouse (a OpenRepos client) was installed.
You probably changed that lately.

Quote:
Originally Posted by Kabouik (Post 1546205)
Same thing happens with "ssu ur".
As always and as it should.

Quote:
Originally Posted by colin.stephane (Post 1546214)
Yes, that seems to host the source code of one of the packages @Kabouik has installed, but the source of the RPMs proper is somewhere else (probably the MER-OBS).

juiceme 2018-09-06 09:55
Re: 2.2.0 EA / Mouhijoki
 
Quote:
Originally Posted by juiceme (Post 1544947)
Noticed that ping no longer worked for nemo user.
I fixed that by adding nemo to net_raw group, however cannot recall if it was so before and the group was dropped or has busybox behaviour changed?

If somebody has not yet updated their device, could you please do "groups" as nemo and check if net_raw is there?
Lo and behold; when I updated to 2.2.1.18 the net_raw capability was dropped from nemo... :mad:


All times are GMT. The time now is 15:42.
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8