Active Topics
-
[ANNOUNCE] MeeShop - new app store (8)
to Applications by Maemish - 3 hrs, 54 mins ago -
HTTP-401 Sfos-Builder when using /etc/ssu credentials (0)
to SailfishOS by insanelysexy - 8 hrs, 24 mins ago -
Longtime users: What device(s) are you using today? (54)
to General by ryu1 - 2 days, 13 hrs ago -
Registering (1)
to General by Halftux - 5 days, 6 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 6 days, 8 hrs ago - more...
| The Following 3 Users Say Thank You to MikeHG For This Useful Post: | ||
|
2016-08-05
, 12:54
|
|
Posts: 189 |
Thanked: 143 times |
Joined on Nov 2009
|
#512
|
The update to the latest version just made rockpool useless for some reason. All notifications are just empty.
https://github.com/abranson/rockpool/issues/44
//Edit: Fixed
Last edited by MaemoUser; 2016-08-05 at 13:08.
https://github.com/abranson/rockpool/issues/44
//Edit: Fixed
Last edited by MaemoUser; 2016-08-05 at 13:08.
| The Following User Says Thank You to MaemoUser For This Useful Post: | ||
|
|
2016-08-05
, 14:16
|
|
Posts: 189 |
Thanked: 143 times |
Joined on Nov 2009
|
#514
|
After the upgrade, I only got empty notifications and changes for the Timeline interface did not get set.
After a second manual restart of the rockpool daemon it worked. But I had to redo all settings.
After a second manual restart of the rockpool daemon it worked. But I had to redo all settings.
|
|
2016-08-09
, 17:51
|
|
Posts: 959 |
Thanked: 3,427 times |
Joined on Apr 2012
|
#515
|
Another issue on Nexus 5 (not sure whether this is something you can fix): the Pebble connection stops working after the phone goes to sleep and wake up again. The Pebble thinks it is connected, and Rockpool shows it as connected, but it no longer receives notifications, is no longer able to control media, and things like watch faces can no longer be uploaded.
If this happens while something is uploading to the watch, the upload hangs for half a minute and then it says "Failed" (on the watch).
If this happens while something is uploading to the watch, the upload hangs for half a minute and then it says "Failed" (on the watch).
__________________
Saera: A Siri clone for the N900, N9(50) and Jolla
Follow me on Twitter: twitter.com/taixzo
Saera: A Siri clone for the N900, N9(50) and Jolla
Follow me on Twitter: twitter.com/taixzo
| The Following User Says Thank You to taixzo For This Useful Post: | ||
 |
|
2016-08-09
, 17:54
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#516
|
If I remember correctly, Nexus 5 had severe BT problems when I tested it. That was CM11 though. Are you on the newest port?
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
| The Following 3 Users Say Thank You to Bundyo For This Useful Post: | ||
|
|
2016-08-09
, 18:41
|
|
Posts: 959 |
Thanked: 3,427 times |
Joined on Apr 2012
|
#517
|
I installed using CM11, and SFOS 1.1.9 - is there a newer one?
__________________
Saera: A Siri clone for the N900, N9(50) and Jolla
Follow me on Twitter: twitter.com/taixzo
Saera: A Siri clone for the N900, N9(50) and Jolla
Follow me on Twitter: twitter.com/taixzo
|
|
2016-08-10
, 04:58
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#518
|
Yeah, though it has other tradeoffs.
http://talk.maemo.org/showthread.php?t=96932
http://talk.maemo.org/showthread.php?t=96932
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2016-08-11
, 08:03
|
|
Posts: 207 |
Thanked: 482 times |
Joined on Mar 2016
|
#519
|
Originally Posted by Upp15
I think I spotted it this morning - although on a different occasion.
But the bluetooth connectivity issue is still there: I tend to turn bluetooth off from the phone for night time. In the morning I turn it on again, and the phone and the watch find each other perfectly every time, but Rockpoold does not notice the connection until I restart it.
Tonight I left my phone at 15% bat - so it was whining all the night with low battery beeps. This morning I put it on a charger with 5% but noticed that pebble is disconnected. On the way to the office I've turned on my BT headset and realized it cannot connect to the phone. I've checked BT - it was on, however showing only devices which were on nearby - pebble, headset and my BT speaker. In fact I have smth like 10 devices paired - they just disappeared from BT settings screen (I've seen such behaviour before though).
Any attempt to connect the phone from headset failed. When I initiated connection from the phone - it connected.
Attempting to reset BT (off/on) does nothing - pebble is still disconnected, headset still cannot initiate connection.
Looking into syslog I see kernel reporting l2cap_sock_connect: failed -115 and followed by standard rockpool's QBluetoothSocket::UnknownSocketError.
So it seems there's still a problem in the BT stack implementation on jolla, where when BT adapter goes into deep sleep - it cannot be recovered back into proper state.
|
|
2016-08-12
, 05:57
|
|
Posts: 21 |
Thanked: 28 times |
Joined on Mar 2016
@ Finland
|
#520
|
Not sure if that is the same case. I turn BT explicitely off from the phone in the evening, and on again in the morning. The devices get connected quickly (Pebble vibrates and BT marker disappears), only Rockpoold does not notice the connection. So, the connection is fine just by restarting the Rockpoold, no further actions to BT needed. And the phone connects e.g. to my car's hands-free every time.
| The Following 2 Users Say Thank You to Upp15 For This Useful Post: | ||
journalctl -fl
then cause the crash.
Congratulations, and thanks for the 1.0 (even if disputed