Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 3 hrs, 17 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 7 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 20 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 19 hrs ago - more...
 |
jellyroll |
2023-06-23
, 18:25
|
|
Posts: 435 |
Thanked: 684 times |
Joined on Apr 2012
@ Netherlands 020
|
#71
|
Does mobile data works in Waydroid?
|
|
2023-06-25
, 10:41
|
|
Posts: 435 |
Thanked: 684 times |
Joined on Apr 2012
@ Netherlands 020
|
#72
|
I had to change the perferred network type into 3G to get mobile data on Waydroid.
This device is an Xperia 5 (bahamut) updated to SailfishOS 4.5.0.19 Struven ketju.
The battery life is good.
Last edited by jellyroll; 2023-07-02 at 21:49.
This device is an Xperia 5 (bahamut) updated to SailfishOS 4.5.0.19 Struven ketju.
The battery life is good.
Last edited by jellyroll; 2023-07-02 at 21:49.
 |
|
2023-06-29
, 15:29
|
|
Posts: 600 |
Thanked: 711 times |
Joined on Jul 2019
@ UK
|
#73
|
Originally Posted by jellyroll
As far as I know neither wifi nor mobile data works in waydroid. However, it uses the hosts internet connection whatever is switched on. It means, you cannot turn on/off wifi or mobile data in waydroid but it has internet connection if wifi or mobile data is turned on on the host.
I had to change the perferred network type into 3G to get mobile data on Waydroid.
This device is an Xperia 5 (bahamut) updated to SailfishOS 4.5.0.19 Struven ketju.
The battery life is good.
I hope it does make sense.
On the other hand this topic is about the Sailfish Os community port for the Galaxy Note 4 (SM-N910C), so I am not sure how your Xperia 5 is in the scope here.
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
| The Following User Says Thank You to edp17 For This Useful Post: | ||
|
|
2023-08-31
, 18:57
|
|
Posts: 600 |
Thanked: 711 times |
Joined on Jul 2019
@ UK
|
#74
|
OTA from 4.5.0.19 to 4.5.0.21 is ready
Here are the steps I followed and the commands I executed
Here are the steps I followed and the commands I executed
Code:
devel-su mask the following: (just in case any of these triggers a reboot in the middle of OTA update) systemctl-user mask voicecall-ui-prestart.service systemctl-user mask mission-control-5.service systemctl-user mask booster-silica-media@.service systemctl-user mask voicecall-manager.service reboot devel-su if installed, unapply and remove all patches if installed, uninstall patchmanager if used, ssu dr mousetracker if used, ssu dr chum if used, ssu dr sailfishos-chum ssu release 4.5.0.21 double check whether these three repos are pointing to the 4.5.0.21 version: ssu lr adaptation-common should be: https://releases.jolla.com/releases/4.5.0.21/jolla-hw/adaptation-common/armv7hl/ adaptation-community-common should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.21/ adaptation-community-treltexx should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.21/ ssu ur zypper ref zypper dup --details unmask the following: systemctl-user unmask voicecall-ui-prestart.service systemctl-user unmask mission-control-5.service systemctl-user unmask booster-silica-media@.service systemctl-user unmask voicecall-manager.service reboot
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
|
|
2023-09-28
, 10:31
|
|
Posts: 600 |
Thanked: 711 times |
Joined on Jul 2019
@ UK
|
#75
|
I couldn't fix the LXC problem on recent releases, so, I've decided to go back to SFOS4.2.
Some fixes (wifi, netlistener flod, etc.) were included in newer releases, therefore, I've included them into the hybris-hal for 4.2. So, if you'd like to go back to 4.2 but you want wifi fixed, please flash this hybris-boot image into /boot partition. (hybris-boot-sfos42-08-wd-fixes_usbmoded-wifi-netlistener.img)
Edit (2024-09-25):
I've found the root cause of the issue with lxc and managed to fix it.
When testing sfos4.6 on the device I did play with lxc a bit more and found out that sfos upgrades also install newer version of lxc packages (more precisely: lxc-libs, lxc-templates & lxc).
On sfos 4.2 and 4.3 the lxc version 3.0.1 were installed. However, sfos 4.4 upgrade did install lxc version 4.0.10. This was the point when the lxc-attach started crashing.
It seems my kernel has got some missing elements therefore the newer than 3.0.1 version of lxc-attach has stopped working. It aborts with the error posted here.
There were two ways to solve this issue.
1. backport all necessary kernel/device changes for supporting that memfd
2. install older version of lxc packages and try how they work on the newer sfos version
The first option would the best and comprehensive as it will ensure compatibility with newer lxc versions. However, it can be challenging and time consuming. Therefore I've chosen the second option.
I downloaded those lxc packages from older sfos version of jolla repositories and tested them.
The latest 3.0.1 version (3.0.1+git4-1.4.3) from this repo works well even on sfos 4.6.:
Last edited by edp17; 2024-09-25 at 12:10.
Some fixes (wifi, netlistener flod, etc.) were included in newer releases, therefore, I've included them into the hybris-hal for 4.2. So, if you'd like to go back to 4.2 but you want wifi fixed, please flash this hybris-boot image into /boot partition. (hybris-boot-sfos42-08-wd-fixes_usbmoded-wifi-netlistener.img)
Edit (2024-09-25):
I've found the root cause of the issue with lxc and managed to fix it.
When testing sfos4.6 on the device I did play with lxc a bit more and found out that sfos upgrades also install newer version of lxc packages (more precisely: lxc-libs, lxc-templates & lxc).
On sfos 4.2 and 4.3 the lxc version 3.0.1 were installed. However, sfos 4.4 upgrade did install lxc version 4.0.10. This was the point when the lxc-attach started crashing.
It seems my kernel has got some missing elements therefore the newer than 3.0.1 version of lxc-attach has stopped working. It aborts with the error posted here.
There were two ways to solve this issue.
1. backport all necessary kernel/device changes for supporting that memfd
2. install older version of lxc packages and try how they work on the newer sfos version
The first option would the best and comprehensive as it will ensure compatibility with newer lxc versions. However, it can be challenging and time consuming. Therefore I've chosen the second option.
I downloaded those lxc packages from older sfos version of jolla repositories and tested them.
The latest 3.0.1 version (3.0.1+git4-1.4.3) from this repo works well even on sfos 4.6.:
Code:
https://releases.jolla.com/releases/4.3.0.15/jolla/armv7hl/
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
Last edited by edp17; 2024-09-25 at 12:10.
|
|
2024-09-25
, 12:15
|
|
Posts: 600 |
Thanked: 711 times |
Joined on Jul 2019
@ UK
|
#76
|
OTA from 4.5.0.21 to 4.6.0.13 is ready
Here are the steps I followed and the commands I executed
Here are the steps I followed and the commands I executed
Code:
devel-su mask the following: (just in case any of these triggers a reboot in the middle of OTA update) systemctl-user mask voicecall-ui-prestart.service systemctl-user mask mission-control-5.service systemctl-user mask booster-silica-media@.service systemctl-user mask voicecall-manager.service reboot devel-su if installed, unapply and remove all patches if installed, uninstall patchmanager if used, ssu dr mousetracker if used, ssu dr chum if used, ssu dr sailfishos-chum ssu release 4.6.0.13 double check whether these three repos are pointing to the 4.6.0.13 version: ssu lr adaptation-common should be: https://releases.jolla.com/releases/4.6.0.13/jolla-hw/adaptation-common/armv7hl/ adaptation-community-common should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.6.0.13/ adaptation-community-treltexx should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.6.0.13/ ssu ur zypper ref zypper dup --details unmask the following: systemctl-user unmask voicecall-ui-prestart.service systemctl-user unmask mission-control-5.service systemctl-user unmask booster-silica-media@.service systemctl-user unmask voicecall-manager.service reboot
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
| The Following User Says Thank You to edp17 For This Useful Post: | ||
|
|
2024-10-02
, 11:28
|
|
Posts: 600 |
Thanked: 711 times |
Joined on Jul 2019
@ UK
|
#77
|
OTA from 4.6.0.13 to 4.6.0.15 is ready
Here are the steps I followed and the commands I executed
Here are the steps I followed and the commands I executed
Code:
devel-su mask the following: (just in case any of these triggers a reboot in the middle of OTA update) systemctl-user mask voicecall-ui-prestart.service systemctl-user mask mission-control-5.service systemctl-user mask booster-silica-media@.service systemctl-user mask voicecall-manager.service reboot devel-su if installed, unapply and remove all patches if installed, uninstall patchmanager if used, ssu dr mousetracker if used, ssu dr chum if used, ssu dr sailfishos-chum ssu release 4.6.0.15 double check whether these three repos are pointing to the 4.6.0.15 version: ssu lr adaptation-common should be: https://releases.jolla.com/releases/4.6.0.15/jolla-hw/adaptation-common/armv7hl/ adaptation-community-common should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.6.0.15/ adaptation-community-treltexx should be: https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.6.0.15/ ssu ur zypper ref zypper dup --details unmask the following: systemctl-user unmask voicecall-ui-prestart.service systemctl-user unmask mission-control-5.service systemctl-user unmask booster-silica-media@.service systemctl-user unmask voicecall-manager.service reboot
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
