maemo.org - Talk
Page 8 of 8 « First 67 8
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)
-   -   Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (https://talk.maemo.org/showthread.php?t=101104)

jellyroll 2023-06-23 18:25
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
Does mobile data works in Waydroid?

jellyroll 2023-06-25 10:41
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
1 Attachment(s)
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.

edp17 2023-06-29 15:29
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
Quote:
Originally Posted by jellyroll (Post 1575346)
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.
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 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.

edp17 2023-08-31 18:57
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
OTA from 4.5.0.19 to 4.5.0.21 is ready
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

edp17 2023-09-28 10:31
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
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.:
Code:
https://releases.jolla.com/releases/4.3.0.15/jolla/armv7hl/

edp17 2024-09-25 12:15
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
OTA from 4.5.0.21 to 4.6.0.13 is ready
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

edp17 2024-10-02 11:28
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
OTA from 4.6.0.13 to 4.6.0.15 is ready
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

edp17 2025-01-18 15:46
Re: Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)
 
This post will be about installing Waydroid on Galaxy Note 4.

I've realized the original instruction is outdated because waydroid has evolved since I wrote that guide a few years ago.
Also, in the meantime, waydroid and related packages have been added into Chum repo and all of these are always getting updated to keep up with main line development.

Unfortunately, newer waydroid and configs are not working on the Note 4 because on it the waydroid is working with a non-existent halium version. (The Galaxy Note 4 is the only device where waydroid works with Lineage Os 14.1 because the "official" waydroid support starts from Lineage Os 16 - Halium 9)

All in all, we cannot use waydroid packages from Chum and we have to stick on waydroid version 1.2. Plus, only the older (Los 17.1) waydroid system & vendor images must be used.
For the Note 4 both, vendor and system images has to be amended, so the ones you download from sourceforge won't work. (Device specific drivers have been added into vendor.img and the ld.config.vndk_lite file also had to be amended in system.img). As these changes have been added to the latest waydroid 17.1 images, it should be a problem as there won't be new 17.1 build anymore.

So, to support those who'd like to use it on the Note 4, I've built Note 4 specific packages. (So, Chum won't flag an update for those if waydroid packages updated there.)

Here is the new installation guide (I've tested in on my device, so it should work):
  1. Remove all waydroid related packages:
    Code:
    devel-su zypper rm dnsmasq python3-gbinder-python python3-gbinder waydroid-sensors waydroid waydroid-runner waydroid-gbinder-config-hybris waydroid-gbinder-config-mainline waydroid-settings waydroid-treltexx
  2. Refresh the repo:
    Code:
    devel-su ssu ur
    devel-su zypper ref
    Install packages
    Code:
    devel-su zypper in dnsmasq
    devel-su systemctl mask dnsmasq
    devel-su zypper in python3-gbinder
    devel-su zypper in waydroid-sensors
    devel-su zypper in waydroid-gbinder-config-hybris-treltexx
    devel-su zypper in waydroid-1.2-treltexx
    devel-su zypper in waydroid-vendor17.1-treltexx
    devel-su zypper in waydroid-settings-treltexx
  3. Download waydroid 17.1 system image VANILLA or GAPPS
    Then, install the required one with
    Code:
    devel-su zypper in waydroid-system17.1-{vanilla or gapps}-treltexx-1.0.0-1.armv7hl.rpm
    Note: Both will install a system.img file into /home/waydroid/images/ folder!
  4. Start waydroid container
    Code:
    devel-su systemctl start waydroid-container
  5. Start waydroid session. There are two ways: 1.) Go to Settings/Waydroid and click on 'Start daemon' button or 2.) Add the Waydroid toggle to the top menu and start/stop from there (Settings/Top Menu/Waydroid)

You may need to mask dnsmask service:
Code:
devel-su systemctl mask dnsmasq
Start Waydroid (full UI):
- Once waydroid-container and waydroid-session are running, tap on the Waydroid icon on your desktop (In case it doesn't start, open Fingerterm and type in
Code:
waydroid show-full-ui
and press enter.)


Any issues, please let me know.


All times are GMT. The time now is 16:33.
Page 8 of 8 « First 67 8
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8