yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] pzoe:
I unlinked previously made symlinks and then tried waydroid init but still the error persists.

Here are the libs on my setup and my sailfish os version is 4.1 which you have given in your recent posts.

I followed exact procedure given in your posts to get to that version. I came from 3.4 to 4.1 using your info in posts.

[root@GalaxyNote4 lib]# locate libssl

/home/.lxc/sid/usr/lib/arm-linux-gnueabihf/libssl.so.1.1

/home/.lxc/sid/usr/lib/arm-linux-gnueabihf/libssl3.so

/home/.lxc/sid/usr/share/doc/libssl1.1

/home/.lxc/sid/usr/share/doc/libssl1.1/NEWS.Debian.gz

/home/.lxc/sid/usr/share/doc/libssl1.1/changelog.Debian.gz

/home/.lxc/sid/usr/share/doc/libssl1.1/changelog.gz

/home/.lxc/sid/usr/share/doc/libssl1.1/copyright

/home/.lxc/sid/usr/share/perl-openssl-defaults/get-libssl-abi

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.list

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.md5sums

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.postinst

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.postrm

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.shlibs

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.symbols

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.templates

/home/.lxc/sid/var/lib/dpkg/info/libssl1.1:armhf.triggers

/system/lib/libssl.so

/usr/lib/libssl.so.1.0.2o+git5

/usr/lib/libssl.so.1.1

/usr/lib/libssl.so.1.1.1h+git1

/usr/lib/libssl.so.10

/usr/lib/libssl3.so

/usr/libexec/droid-hybris/system/lib/libssl.so

[root@GalaxyNote4 lib]# waydroid init

python3: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
[Galaxy Note 4 General] pzoe:
I went over some searching in repo urls and I see this.

Does this mean 4.2 and 4.3 versions are also available?
[Galaxy Note 4 General] edp17:
In short, No.

A bit longer explanation:

To correctly build all OTA packages on OBS I need to re-build some packages locally and upload them to OBS. I've done this for 3.4, 4.0 and 4.1.

Then using the old packages, that were uploaded for 4.1, I've let OBS build all OTA packages for 4.2 and 4.3. One of the builds (4.2) has been completed successfully while the other one (4.3) has ended up with one unresolvable package (pulseaudio-modules-droid-hidl).

When I locally built a 4.2 image, the device didn't boot, therefore I didn't want to use those local packages on OBS either. That's why I tried to use the older packages and I got surprised when the builds have completed.

In theory, OTA to 4.2 can work but I've not tried it yet.

If you dare enough you can try. :) However, do a full backup first!!
[Galaxy Note 4 General] serifpersia:
@edp17 Is there a way to make this work on n910k variant?(same Exynos 5433)

The only twrp is 3.3.1-0( https://xdaforums.com/t/recovery-all-variants-twrp-3-3-1-0-touch-recovery.3836759/ ) and the only LineageOS is 17.1 ( https://xdaforums.com/t/exynos-unofficial-lineageos-17-1-06-30-2021.3937956/ ) (I just want to use scrcpy in linux via usb cable (OTG cable) to remote into another android and control it with touch.

I'm willing to learn how to make it work. Just let me know how do actually build kernal and can it work with new twrp and this version of LineageOS 17.1. I have a little experience with linux but I can learn new things if I have clear instructions and I can try to troubleshoot on my own. EDIT: I installed the 3.3 version. I removed assert line from script from lineage 14.1 and added in assert trelteskt in sailfish zip. And it works lol. Now I want debian or ubuntu and scrcpy running over usb

Thanks!
[Galaxy Note 4 General] edp17:
Hi,

What would you like to make work? Instaling SFOS or WayDroid or both or using scrcpy on your device?

For SFOS: you can try to install this port (install the Los14.1 image from the first post and try to boot). If that works fine, you're lucky. Otherwise, you need to port SFOS to that device. (That probably will not be so difficult as you can re-use much stuff from this device's repos.) I'll help you if you choose to port SFOS to your device.

However, if you'd only like to use scrcpy with this device, you'll need to install an Android on your device and scrcpy on your PC (Linux), then follow the instruction on scrcpy's github page. (I've been using scrcpy with my Galaxy S2-i9100 for a while now.)
[Galaxy Note 4 General] serifpersia:
I want to use scrcpy on linux on my note 4 to remote into another device that can be adb connected i can use pc no problem but I want to do it using my phone not pc.

I have the 3.3 build, I flashed the kernel for lxc support in twrp. I installed the packages from EXTRA 2 except the mouse rpm file it says it the terminal that is not a valid rpm file(I saved the link clicking on it gives me error page Not Found....)

I tried sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid

but it gives me error Couldn't find a matching image Error creating container my container

Seems like even if I could get it to work it would be choppy and no 3d acceleration.

It would be nice if there is scrcpy app for sailfish but probably not.... I guess I will have to get a windows tablet and just get scrcpy running like that but I would really like to use my note 4 as that but if its not possible its not.... Its my fault that I damaged display flex cable on my new phone lol(Samsung galaxy M31S).
[Galaxy Note 4 General] edp17:
Afaik, scrcpy uses adb which is an android thingy. This doesn't exist on SFOS. Can you use scrcpy with Note4? Sure, if you install an Android on it. With SFOS? I don't think so.

True, the full Debian distro in an LXC container has got some limitations. (Like: cannot access the camera, no 3D acceleration, when is running the sound on the host stops as the Debian takes it over, etc...) However, with all of these limitations, it is very cool and useful to be able to run a desktop distro.

It seems that URL you mentioned doesn't work anymore, I'll check the new one and will update the post. (Thanks for highlighting this.)

What is the error you are getting when running that 'sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid' command?
[Galaxy Note 4 General] edp17:
I've updated the qxcompositor link in the main post.
[Galaxy Note 4 General] serifpersia:
When I installed all the hyperlinked packages I tried to run this command

sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid

but it gives me error : Couldn't find a matching image Error creating container my container

Did I write it wrong in the terminal? If I try to run without specifying what distro to get I'm asked what distro and architecture and after I enter Debian sid armhf I get the same error: Couldn't find a matching image Error creating container my container

I might learn about how to port ubuntu touch on my n910k I found halium 9.0(lineageos 16.0) manifest file and I can extract vendor blobs from lineage 16.0 zip for my device and then follow the steps for building hybris boot image and ubuntu. After It boots have to follow next steps adding desktop ui wifi etc. It will be hard because I'm complete novice but could be fun.
[Galaxy Note 4 General] Computershik:
after I shutted down SFOS and pulled out the battery, it keeps rebooting. How to fix?
[Galaxy Note 4 General] edp17:
Put a little piece of paper where the batter connects to the device. (This helps you to save battery if you don't use the device for a long time.)

What kernel is installed on the device?
[Galaxy Note 4 General] Computershik:
Please add fingerprint support and it does not see my sim-card. SM-N910C.
[Galaxy Note 4 General] anjarys:
ssh defaultuser@192.168.2.15

ssh: connect to host 192.168.2.15 port 22: Connection timed out

help please cant ssh to phone

fresh install 4.1 from zip
[Galaxy Note 4 General] edp17:
This was on my to-do list but now as I've looked into it, I realized the Los14.1 android base under the Sailfish Os port does not have fingerprint support. Sorry. :(

Which version doesn't see your SIM card?
[Galaxy Note 4 General] edp17:
Before you installed the zip file, did you do a factory reset in TWRP? What I spotted was, that sometimes factory reset was not enough and some garbage remained in the data partition.

The only solution I found was in TWRP got to 'Wipe' menu, then select 'Advanced Wipe' and select everything except the 'Micro SDcard' and 'Swipe to Wipe' (Important!! DO NOT SELECT 'Micro SDcard' because you'll lose all data on your external sd card.

You are not finished yet. Go back to the 'Wipe' menu and tap on 'Format Data' and type 'yes' then press enter. This will reformat the internal sd card (data partition) and remove all residue from previous installs.

Of course, if you have important stuff on your internal storage do save them before you do what I suggested, otherwise you'll lose them forever.

Then, you can reboot into TWRP and flash the los14.1 zip and sfos zip again.

If you are stuck on the boot logo again (you shouldn't as I tested the 4.1 image) try the following: before you boot the phone, connect it to the PC. If there is still no ssh, try to use: telnet 192.168.2.15 2323 or telnet 192.168.2.15 23
[Galaxy Note 4 General] anjarys:
I did the advanced wipe. One thing i missed is to go back to wipe and format data. Thanks for that.

One question, how to buy/install the android certificate on this rom?
[Galaxy Note 4 General] edp17:
In my experience, when doing a fresh install, ALWAYS format data to avoid residues of previous installs that potentially mess up the new install as well. (I've been chasing weird issues for days until figured out data must be formatted prior to the installation. Once I've done that, all weird issues were gone. :))

Regarding the android support.

The bad news, none of the community Sailfish Os devices has android support.

The good news, I've managed to make WayDroid (Android10) work on my builds. Not everything works (e.g. no GPS), but (just name a few) I use Signal, Aurora store and Vanced (YouTube replacement) without any issues.

Plus, I wrote a little script that allows me to switch between a vanilla android10 and another one where I registered the device with google and therefore I have google play and all google stuff available. In there, banking apps that require the google framework just do work fine. ;)
[Galaxy Note 4 General] anjarys:
Hi, tried to format data and still cannot ssh via usb. Alternatively, ssh via wifi using defaultuser username was successful. Thanks for the guidance.

To be honest this is my first time hearing waydroid. Sounds interesting. Will dig it up.
[Galaxy Note 4 General] edp17:
Interesting what you are saying about ssh over wifi is working but isn't via USB. To work with wifi all the following are required:

- device booted into the gui AND

- manually connected to a wifi network AND

- developer mode is activated and a password is set.

To ssh in via USB doesn't need GUI and wifi at all. It only requires a password for the defaultuser and an IP address. This means if you cannot ssh in via USB, there is a problem with either the cable or USB port on the host or device.

Anyway, I am glad finally you were able to ssh in.

About the waydroid stuff, you can find how to install it on the first page.
[Galaxy Note 4 General] Notfunction:
what is the best and stable os for samsung note 4 sm-n910c treltexx exynos
[Galaxy Note 4 General] edp17:
Well, there is no simple answer to this question.

What's the best depends on what you would like to use it for.

Probably what's best for me is not necessarily the best for anybody else.

Example.

If you need all the official camera functions and blobs, then the best rom is the latest official android.

If you don't bother about the camera, but you need MHL (connect the device to a TV), the best bet is one of the latest official Lineage Os (or could be unofficial ones but you need to test HML on those)

If you need google play store and framework, again, use the latest android or a lineage with gapps.

If you need a Linux system on it, sfos 4.2 is stable enough for daily use but don't expect too many native apps and there is no android app support.

My current setup on the note4 (sfos 4.2 + waydroid + desktop Debian sid in an LXC container) is stable enough for me for all the tasks I need on the phone. It is not my main phone but I use it daily. I don't use it for navigation and don't want to connect it to the TV. Although this is one of my backup phones, I mainly use it for developments/experiments and as a Bluetooth music player. Occasionally, I play Sid Meier's Civilization with DOSBox installed on the Debian Sid and VNCd into it from my pc. I know, I can use DOSBox directly on my PC but running it all on a phone is more fun. :cowboy: I even compiled qemu from its source on the device and launched Windows XP on it. :cool: (The Winows 7 was too much for its hardware, it was unbearable slow but XP ran surprisingly well.)
[Galaxy Note 4 General] pzoe:
I have a problem updating

Previously when I'm on 4.0 koli I updated to 4.1, 4.2 and that went fine and at that time I'm trying to use LXC containers and waydroid too so I installed other packages as well.

Now I'm using a different Note 4 and trying to get to latest OS by upgrading from 3.3 to 4.4 (only OS related stuff) and then on latest version try LXC and waydroid stuff. While going with this method I'm facing issues like I cannot upgrade from 4.0 koli to 4.1. Update went fine but when I do reboot then the display is stuck on Sailfish OS logo and from there it wont go any further. I waited for more than an hour and it happened more than enough times to understand that there is an issue.

To solve this issue I flashed 02-hybris-boot-firejail-enhanced.img as mentioned in tutorial (4.0 koli update) but still no success. I did wiped cache partition but still the error persists.

Is there any way to install directly the latest version without going from 3.3 to 4.4. It's taking me a whole day to do this and then I'm stuck with 4.1 not booting.

Does TWRP play any role in all of these. I have the latest 3.3.1 version on my phone.
[Galaxy Note 4 General] edp17:
Hi, it looks like sfos is booted but for a reason, it couldn't start the UI (Lipstick). I can help you find out what's wrong and how to fix it, but via this channel (xda), it is a bit difficult. Plus, as you mentioned that you need the latest version to experiment with, so I've uploaded the 4.4.0.58 version for you here Sailfish OS 4.4.0.58 for Galaxy Note 4 (treltexx). Just flash this image right after the Los 14.1 zip. (Please wipe all partitions except the external sd card and do a Format data in TWRP. Otherwise, some residue of the previous installation can remain that interfere with this new build.) It should work out of the box.

Regarding waydroid. Once you flashed all packages, please disable waydroid-sensor and dnsmasq services.

devel-su systemctl disable waydroid-sensors.service

devel-su systemctl disable dnsmasq.service

(Sensors will be started, when the waydroid UI starts, so it doesn't need to be running as a service. I'll fix this in a later package. Dnsmasq is required for installation but waydroid doesn't use it later. If we keep dnsmasq service running, it is clashing with the Sailfish Browser and the browser doesn't work. Therefore, it is better to disable dnsmasq service.)

Good luck and let me know the result.
[Galaxy Note 4 General] pzoe:
I tried 4.4 update from twrp. Lineage installs good but sailfish no. Previously I could able to install lineage 17.1 on this and use it extensively. Lately with Sailfish Im getting this error. Even with sailfish 3.3 I get the same error but after reboot sailfish boots but with sailfish 4.4 it boots directly into lineage 14.1

It looks like sailfish doesnt want to install on my device easily. You better tell me the hard way of fixing stuck on sailfish os logo. I have sailfish 4.0 twrp backup. I can update from there and fix the bug if you can help me. Please dm me for instructions.

My current error is
[Galaxy Note 4 General] edp17:
This is a problem with TWRP version. Are you using 2.8.7.0? (Newer versions have this problem.)
[Galaxy Note 4 General] edp17:
Hi, I've tested the 4.4 image and the waydroid installation on it for you. It works. I have updated the instruction here. Please read that as it requires installing packages in a specific order.

On the other hand, I've spotted a bug in that 4.4 build that I gave you. (Because of that bug, after the initial setup, the device keeps rebooting.) I have fixed it, you can download the fixed version from here: sailfishos-treltexx-release-4.4.0.58-CM141-20220521_fixed.zip

Please flash it with TWRP 2.8.7.0. If you still get the Error: 7, I'll remove the device check from the zip and then you'll be able to install it.

Edit: I've created another image for you. On this, there is no device verification, so if you get Error 7 on the other image, you should be able to install this one: sailfishos-treltexx-release-4.4.0.58-CM141-20220521_fixed-noverif.zip
[Galaxy Note 4 General] edp17:
OTA from 4.4.0.58 to 4.4.0.64 is ready

devel-su
cp /usr/bin/droid/wifi.conf /usr/bin/droid/wifi.conf.backup
ssu release 4.4.0.64
ssu ar adaptation-common https://releases.jolla.com/releases/4.4.0.64/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.4.0.64/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.4.0.64/
ssu ur
zypper ref
zypper dup --details

The device will will reboot when installing: "voicecall-ui-jolla-1.14.38.1-1.6.1.jolla.armv7hl"

just leave it connected and wait until it boots up, then ssh in and continue the update:

devel-su
zypper dup --details
cp /usr/bin/droid/wifi.conf.backup /usr/bin/droid/wifi.conf
reboot
[Galaxy Note 4 General] edp17:
OTA from 4.4.0.64 to 4.4.0.68 is ready

devel-su
cp /usr/bin/droid/wifi.conf /usr/bin/droid/wifi.conf.backup
disable all openrepos
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.4.0.68
ssu ar adaptation-common https://releases.jolla.com/releases/4.4.0.68/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.4.0.68/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.4.0.68/
ssu ur
zypper ref
zypper dup --details
double-check dsme and systemd-hostname services:
in '/usr/lib/systemd/system/dsme.service' the 'PrivateNetwork' must be set to 'false'
in ;/usr/lib/systemd/system/systemd-hostnamed.service' the 'PrivateNetwork=true' must be commented out or deleted
cp /usr/bin/droid/wifi.conf.backup /usr/bin/droid/wifi.conf
reboot
[Galaxy Note 4 General] karpura:
Hello, I had a question. I install the operating system, but it gets stuck on Lego, what should I do?

I receive this message

Done! E:unknown command []]
[Galaxy Note 4 General] edp17:
Hi,

What's your device type? (This port is for the SM-N910C and I am not sure this works on any other type.)

Please let me know all steps how you installed it and what files you flashed.

Where did you get that 'E: unknown command' message?
[Galaxy Note 4 General] Computershik:
Hello! Thanks one more time for supporting this device! It is great, that you fixed modem that was broken in 4.2 (via OTA) and 4.1 (if flashing)

Now I ask you to fix hardware acceleration in the web browser, YouTube videos lag with quality >=720p.

And please add entire firmware 4.4 link into the first post.

Is there any chance of aliendalvik support? I have packages... but the service did not start due to some missing kernel features (I tried on 4.0, 4.1 and 4.2).
[Galaxy Note 4 General] edp17:
Hi,

I am not sure how you mean hw acceleration in the web browser. The built-in web browser is Jolla's own and it should work as is.

I've uploaded the 4.4 zip and added to the fist post.

Because AD is designed for a device, even is you have the .rpm packages, it won't work on another one unless that device has a VERY similar hw architecture. Therefore, AD support is only available on official devices.

On community ports like this only Waydroid is the option to run android apps. Waydroid is only available on halium-based (halium >= 9) devices, but you are lucky because I've managed to make it work on this port. Waydroid is available on this port since sfos 4.1. (All instructions are on the channel, so I recommend reading it through.)

What kernel requirements and services are you referring to?
[Galaxy Note 4 General] Computershik:
The fact is that on Android, Samsung Galaxy Note 4 is capable of playing videos up to 1080p@60fps in the official (and Vanced) app, and at least 1080p@30fps in the browser.

Other SFOS devices like Sony Xperia 10 do not lag playing YT videos in Jolla's web browser on the same SFOS version (and even earlier). They use GPU, and some programmers from @sailfishos TG chat told me that it is the problem of the port. Maybe, it tries to use only CPU for drawing (at least in the browser), Idk.

It is very strange that even 720p videos lag here. I hope you will solve this problem.

Packages from Sony Xperia X should suite. Me and my friend tested it on other similar devices, but I am not sure if it is legal to speak anymore about it on the forum.

puddlejumper,vndpuddlejumper should be in /dev/

You should add puddlejumper,vndpuddlejumper to CONFIG_ANDROID_BINDER_DEVICES

If you are really able to compile the kernel compatible with android 9 base (or whatever it is called) and add puddlejumper,vndpuddlejumper - dalvik packages will work.

Btw, I saw android kernel with fingerprint support on androidfilehost (Pixel Experience rom based on Android 9). Isn't it your firmware? Maybe, it can be useful. There are also LineAge OS and RR OS based on Android 10. Maybe, they have kernel sources somewhere.

P.S. Fingerprint support on SFOS will be excellent (if possible).

P.P.S (sorry for offtop) I also have Samsung S7, and waiting for a newer SFOS for it (instead of 2.x).
[Galaxy Note 4 General] edp17:
Okay, I'll see whether I can fix this. As never used the browser for watching YT videos (I use microtube), I didn't see this issue.

No, it is not legal to speak here. If you'd like to discuss it further, you can pm or find me on TG (@edp_17)

As I never got the chance to experiment with AD on this device, I only set binder devices for Waydroid. I'll add these into the kernel. However, the AD support for the Xperia X is an Android 4.4.4 version which is VERY old now. This means even if you can install the AD on this device, many apps won't install/update because of the outdated android layer.

Plus afaik the AD stopped working on the hammerhead (Nexus 5) since sfos 4.1, so don't hold your breath it will work on sfos 4.4 on this device.

I also tried to find a rom where the fingerprint was supported but haven't found any. I don't think only a kernel would be enough if there are missing parts elsewhere. It might be worth a try, though.

However, this port is based on Android 7.1 (Los14.1) rather than 9. This means a kernel from a newer android might not work properly without the matching device tree. This means using a newer android layer needs rebasing.

Rebasing requires to re-do the whole port. I've done it already with a Los 17.1 base but nothing got better than this port so I scrapped that project and returned to this one.

I did work on an S7 port a few years ago when I had a device. Then I replaced that phone with an XA2 and purchased an official sfos licence for it. I also sent my notes to somebody who was interested in porting sfos for the S7 but that guy then just disappeared and the port didn't show up either.

I still have the zip that I built for the S7 (sfos 3.2) but it doesn't work properly.
[Galaxy Note 4 General] edp17:
Hi,

I've just tested this on my Note 4 (SFOS 4.4.0.68) and I didn't experience any lags with even 1080p videos on youtube. Please give me a link where you got that problem.
[Galaxy Note 4 General] Computershik:
Hi, sent it to your Telegram.