Active Topics
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2016-10-05
, 10:01
|
|
Posts: 635 |
Thanked: 1,535 times |
Joined on Feb 2014
@ Germany
|
#142
|
Originally Posted by minimec
Sometimes restarting lipstick does not work, so i edited the command to first kill lipstick and then restart it.
Lipstick freeze workaround
Content of liprestart.sh
Code:#!/bin/bash systemctl --user restart lipstick
Code:
#!/bin/bash killall lipstick && systemctl --user restart lipstick
And by the way, does anyone know when 2.04 will be available for us Nexus users?
| The Following User Says Thank You to mautz For This Useful Post: | ||
|
|
2016-10-05
, 10:06
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#143
|
@mautz, it is enough just to do "killall lipstick", no need to restart it...
System will automatically restart it when killed.
System will automatically restart it when killed.
|
|
2016-10-05
, 10:13
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#144
|
Originally Posted by mautz
Good question. MER build targets is still on 2.0.2.48 level, and when that is updated; your guess is as good as mine
And by the way, does anyone know when 2.04 will be available for us Nexus users?
|
|
2016-10-05
, 10:34
|
|
Posts: 635 |
Thanked: 1,535 times |
Joined on Feb 2014
@ Germany
|
#145
|
Originally Posted by juiceme
I thought the same thing...my phone was in a weird state today, apps took ages to load or didn't even load and the restart lipstick script did not work. Restarting it from terminal did also not work, i then killed lipstick, but it did not restart itself, so i had to do a hard reset.
@mautz, it is enough just to do "killall lipstick", no need to restart it...
System will automatically restart it when killed.
Originally Posted by juiceme
Ok, i can wait a few days
Good question. MER build targets is still on 2.0.2.48 level, and when that is updated; your guess is as good as mine
| The Following User Says Thank You to mautz For This Useful Post: | ||
 |
|
2016-10-05
, 15:10
|
|
Posts: 411 |
Thanked: 1,105 times |
Joined on Jan 2010
@ Europe
|
#148
|
Originally Posted by mautz
You did the OTA coming from which sfos version? Are you using 12.1-20150901-SNAPSHOT
2.02.51 with CM12.1 and sfdroid. Updated via OTA.
-YOG4PAO237-hammerhead?
| The Following User Says Thank You to BluesLee For This Useful Post: | ||
|
|
2016-10-05
, 18:48
|
|
Posts: 635 |
Thanked: 1,535 times |
Joined on Feb 2014
@ Germany
|
#149
|
Yes, i'm using the same CM version. I updated from 2.0.0.10 to 2.0.2.4x and then to 2.0.2.51, because 2.0.2.51 wasn't released when i updated.
| The Following User Says Thank You to mautz For This Useful Post: | ||
|
|
2016-10-05
, 20:04
|
|
Posts: 635 |
Thanked: 1,535 times |
Joined on Feb 2014
@ Germany
|
#150
|
Just updated my test installation to 2.0.4.13. Took about half an hour and i only nedded to interrupt and reboot once. Sfdroid still works. Haven't used it much, only checked if my most needed patches are working, which wasn't the case. So i'm back to my normal install with 2.0.2.51, which will get updated if the patches are working.
 |
| Tags |
| hammerhead, nexus5, sailfishos, sfdroid |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 01:41.
(And I believe VOLTE is going to be the next problem-nest, when it gains more users...)