Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)

Search This thread
By:
Advanced…
P

pzoe

Member
Nov 19, 2016
20
3
Samsung Galaxy Note 4
Samsung Galaxy S6
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
 

Attachments

  • IMG_20220606_024846.jpg
    IMG_20220606_024846.jpg
    423.3 KB · Views: 25
edp17

edp17

Senior Member
Dec 9, 2019
169
84
pzoe said:
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
Click to expand...
Click to collapse
This is a problem with TWRP version. Are you using 2.8.7.0? (Newer versions have this problem.)
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
pzoe said:
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
Click to expand...
Click to collapse

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
 
Last edited:
  • Like
Reactions: Computershik
edp17

edp17

Senior Member
Dec 9, 2019
169
84
OTA from 4.4.0.58 to 4.4.0.64 is ready

Code: 
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:
Code: 
devel-su
zypper dup --details
cp /usr/bin/droid/wifi.conf.backup /usr/bin/droid/wifi.conf
reboot
 
Last edited:
edp17

edp17

Senior Member
Dec 9, 2019
169
84
OTA from 4.4.0.64 to 4.4.0.68 is ready

Code: 
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
 
karpura

karpura

New member
Mar 29, 2021
1
0
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 []]
 
Last edited:
edp17

edp17

Senior Member
Dec 9, 2019
169
84
karpura said:
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 []]
Click to expand...
Click to collapse
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?
 
  • Like
Reactions: karpura
C

Computershik

Member
Dec 26, 2016
11
0
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).
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
Computershik said:
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).
Click to expand...
Click to collapse
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?
 
C

Computershik

Member
Dec 26, 2016
11
0
edp17 said:
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.
Click to expand...
Click to collapse
The fact is that on Android, Samsung Galaxy Note 4 is capable of playing videos up to [email protected] in the official (and Vanced) app, and at least [email protected] 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.


edp17 said:
Therefore, AD support is only available on official devices.
Click to expand...
Click to collapse
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.
edp17 said:
What kernel requirements and services are you referring to?
Click to expand...
Click to collapse
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).
 
Last edited:
edp17

edp17

Senior Member
Dec 9, 2019
169
84
Computershik said:
The fact is that on Android, Samsung Galaxy Note 4 is capable of playing videos up to [email protected] in the official (and Vanced) app, and at least [email protected] 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.
Click to expand...
Click to collapse
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.

Computershik said:
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.
Click to expand...
Click to collapse
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)

Computershik said:
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.
Click to expand...
Click to collapse
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.
Computershik said:
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).
Click to expand...
Click to collapse
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.
 
Last edited:
  • Like
Reactions: Computershik
edp17

edp17

Senior Member
Dec 9, 2019
169
84
Computershik said:
Hi, sent it to your Telegram.
Click to expand...
Click to collapse
Hi,
Thanks.
I've checked that on my device. I could only select the resolution but not the frame per sec. When I selected 1080p, it was a few seconds waiting, then the device played the whole video to the end without any lag.
I've also checked resolution 720p which was not a problem either.
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
OTA from 4.4.0.68 to 4.4.0.72 is ready
Code: 
devel-su
mask the following:
systemctl-user mask voicecall-ui-prestart.service
systemctl-user mask mission-control-5.service
systemctl-user mask [email protected]
systemctl-user mask voicecall-manager.service
reboot
devel-su
cp /usr/bin/droid/wifi.conf /usr/bin/droid/wifi.conf.backup
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.72
ssu ar adaptation-common https://releases.jolla.com/releases/4.4.0.72/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.4.0.72/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.4.0.72/
ssu ur
zypper ref
zypper dup --details
vi /usr/lib/systemd/system/dsme.service
   set PrivateNetwork=true to PrivateNetwork=false
vi /usr/lib/systemd/system/systemd-hostnamed.service
   remove or comment out PrivateNetwork=true
cp /usr/bin/droid/wifi.conf.backup /usr/bin/droid/wifi.conf
unmask the following:
systemctl-user unmask voicecall-ui-prestart.service
systemctl-user unmask mission-control-5.service
systemctl-user unmask [email protected]
systemctl-user unmask voicecall-manager.service
reboot
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
If you OTA update to 4.4.0.72 on or after 07/12/2022, the following steps aren't necessary:
Code: 
vi /usr/lib/systemd/system/dsme.service
   set PrivateNetwork=true to PrivateNetwork=false
vi /usr/lib/systemd/system/systemd-hostnamed.service
   remove or comment out PrivateNetwork=true

These are fixed in packages, so no longer need to do the change manually.
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
OTA from 4.4.0.xx to 4.5.0.18 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 [email protected]
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.18
ssu ar adaptation-common https://releases.jolla.com/releases/4.5.0.18/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.18/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.18/
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 [email protected]
systemctl-user unmask voicecall-manager.service
reboot
 
Last edited:
edp17

edp17

Senior Member
Dec 9, 2019
169
84
I've also updated the zip file int the first post if someone want to install fresh.
 
edp17

edp17

Senior Member
Dec 9, 2019
169
84
OTA from 4.5.0.18 to 4.5.0.19 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 [email protected]
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.19
double check whether these three repos are pointing to the 4.5.0.19 version:
ssu lr
  adaptation-common should be https://releases.jolla.com/releases/4.5.0.19/jolla-hw/adaptation-common/armv7hl/
  adaptation-community-common should be https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.19/
  adaptation-community-treltexx should be https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.19/
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 [email protected]
systemctl-user unmask voicecall-manager.service
reboot
 
  • Like
Reactions: anjarys
You must log in or register to reply here.

Similar threads

NoteboyTech
Samsung Galaxy Note 4 indian users
Replies
4K
Views
833K
K
kirubhamadhu
JHColt
Note 4 N910C [09 OCT] Sammobile Firmware - MEGA Mirrors
Replies
2K
Views
787K
A
alrase
S
Note 4 Battery Thread!!
Replies
3K
Views
758K
L
louisJJ
S
Note 4 - Canadian Thread
Replies
4K
Views
741K
D
dave678
K
[Discussion] Android Marshmallow for Note 4
Replies
2K
Views
575K
I
imeem

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    edp17
    edp17
    Code: 
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!            Everything you do,               !!
!!      you do at your own peril and risk.     !!
!!                                             !!
!!      I do not bear any responsibility       !!
!!          for your faulty devices.           !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!                                             !!
!!   THIS ROM IS ONLY FOR THE EXYNOS VERSION   !!
!!                                             !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    First I would like to thank NoKit, monich, elros34 and all the Sailfish OS porter guys who helped me to make this port.
    Thank you very much guys!

    News 05/03/2023: OTA to SFOS 4.5.0.18

    26/10/2022: OTA to SFOS 4.4.0.72
    14/07/2022: OTA to SFOS 4.4.0.68
    08/06/2022: OTA to SFOS 4.4.0.64
    30/05/2022: OTA to SFOS 4.3 & 4.4
    22/02/2022: OTA to SFOS 4.2
    16/10/2021: Waydroid on Galaxy Note4 (SFOS 4.1)
    03/09/2021: OTA to SFOS 4.1
    23/03/2021: OTA to SFOS 4.0

    Requirements:
    Before you start to download anything, please read all this through carefully.
    The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.

    Installation instructions:
    1. Download all files, LOS14.1 zip, Sailfish OS zip and twrp2.8.7.img to the external SD card on the phone
    2. Reboot into TWRP (Hold buttons: Power on + Home + Volume up)

    At this point you should install TWRP 2.8.7 as the installation work the best with this recovery.​

    Once you flashed TWRP 2.8.7, please reboot into recovery and continue the process.​

    ​
    3. Do a factory reset
    4. Still in recovery, flash the LOS14.1 image
    5. Still in recovery, flash Sailfish Os image
    8. Reboot
    9. Enjoy the latest (3.3.0.16) Sailfish OS on your Note 4 (treltexx). :)
    You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.

    This Sailfish OS Android HAL based on LOS 14.1.


    Downloads:

    Problems/Solutions:
    1. Problem: LXC container doesn't start on any of these two builds.
      Solution: In TWRP install the kernel for lxc support. (This will be included into a later build.)
    2. Problem: Incoming calls are not displaying the number only the 'Private call' text.
      Solution: Install the fix for 'Private number' calls rpm. (This will be included into a later build.)


    Some useful patches:

    Apps from Openrepos
    Apart from the Jolla store there are plenty of other, community made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman

    Debug/login/troubleshooting:
    In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].


    Notes:
    • On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.

    How to make a backup/restore with TWRP:
    You can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.

    Battery life
    In my experience this build gives a very good battery life (I've tested with a new battery and it drops beteen 5% - 10% overnight with wifi on)

    Changelog:

    10.10.2020
    =========
    • Custom (Sailfish OS) boot logo


    09.10.2020
    =========
    • Sound fix is included, it works out of the box
    • GPS fixed!
    • S-Pen works as a mouse! :DTo make the cursor visible (thanks for elros34!) you need to install:
      1. Patchmanager 3 from openrepos
      2. mousetracker
      3. amend '/var/lib/environment/compositor/droid-hal-device.conf' file, add the -plugin evdevmouse:abs:/dev/input/event3 to the end of LIPSTICK_OPTIONS. (That line should look like this:
        Code: 
        LIPSTICK_OPTIONS=-plugin evdevtouch -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap -plugin evdevmouse:abs:/dev/input/event3
      4. as final step apply the moustracker patch in Settings/Patchmanager, then restart the services (pulley menu in Patchmanager) or reboot, then pull out the S-Pen and use it as a stylus/mouse.
        (Note: As patchmanager doesn't yet work when the default user is defaultuser, the instruction above works only on sfos 3.3.0.16 or the OTA updated 4.0.1.48. On fresh sfos 4.0.1.48 install you need to install mousetracker and manually apply the patch from it.)

    28.09.2020
    =========
    Work:
    • Screen
    • Touch
    • IMEI number is detected
    • Sensors (Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
    • GPS (The permanent solution will be included in a future build. Now, the workaround is (do it only once): as root delete the folder /data/system/gps and then reboot. GPS should start working)
    • Notification LEDs (white, green, blue, red)
    • Wifi
    • MTP
    • Bluetooth
    • Calls incoming/outgoing
    • Messages incoming/outgoing
    • Mobile data
    • External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is the name of the sd card when it was formatted like 4B93-785B)
    • Home button and the Back soft button
    • Vibra
    • Pixel ratio and icons set to 2.00
    • Audio is routed to headphone if that presents
    • Camera front/rear
    • Video recording (only on the rear camera)
    • Jolla store (please skip the account creating/adding in the initial setup)
    • findutils is installed by default (updatedb and locate commands work out of the box)
    • Torch
    • can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
    • Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
    • Sound - Please download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download, then give it executable permission and run as root or do the following:
      1. Download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download
      2. goto Settings/Developer tools, enter a Password and save it
      3. start the Fingerterm app and within, issue the following commands
      4. devel-su (press enter, then enter the password you set)
      5. chmod +x /home/nemo/Download/soundfix-treltexx.sh
      6. /home/nemo/Download/./soundfix-treltexx.sh

    Do not work:
    • USB mode selection from Settings (workaround: as root run 'systemctl restart usb-moded' command)
    • Video recording on the front camera
    • Video playback in Gallery app (You can use Kodi for playing videos)
    • Internal SD card is not mounted to /android
    • S-Pen WIP

    Extra 1: Change boot logo, Download warning image, Charring image and Download image for Sailfish OS like. :D
    Simply download the Note4-Boot-Logo-Updater_by_edp17.zip from the download section and flash it with TWRP.
    Important!: Once the zip is flashed, boot into recovery again, then you can boot into Sailfish OS.

    To revert these images back to original:
    Download the original param.bin and flash it with heimdal:
    Code: 
    heimdall flash --PARAM param.bin
    Inspired by this post

    Extra 2: Desktop Linux distro install/run on the Note 4!
    1. First flash the kernel from the Downloads section (in a later build this kernel will be included)
    2. Install all the following packages:

    3. Once the packages are installed, fire up the LXC and install a distro into it (e.g. Debian SID)
    On the Note 4 the harbour-containers GUI doesn't work properly. Fortunately the desktop distro installation can be done from a command line. Here are the steps:
    • sudo lxc-create -t sfos-download -n mycontainer
      follow the instruction and set the distribution (e.g. debian) then the version (e.g. sid) then the architecture (armhf)
      example command: sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid
    • sudo lxc-start -n mycontainer
    • sudo lxc-attach -n mycontainer
    • then within the container:
    • /mnt/guest/setup_desktop.sh
    • /mnt/guest/setups/debian.sh

    4. Once the Desktop distro is installed you can start:
    I recommend to use one of these scripts as they save a little time. (Note: You need sudo installed and configured for these scripts!)

    5. Enjoy. :)

    6. More info about the Full linux distros on Sailfish OS.

    Pictures:

    treltexx-apps.jpg


    treltexx-settings.jpg


    treltexx-top-menu.jpg




    Custom boot logo and other pictures:

    logo450x800.jpg


    warning450x800.jpg


    lpm450x800.jpg


    download450x800.jpg
    View
    2
    edp17
    edp17
    Running Windows XP (with Qemu 4.2.0) on Desktop Debian (Sid) distro within an LXC container on the Galaxy Note 4 (SFOS4.0).
    (The Qemu 4.2.0 is compiled on the device within the Desktop Linux.)

    Galaxy-Note4-Debian-Sid-in-LXC-running-Windows-XP-in-QEMU1.png


    Galaxy-Note4-Debian-Sid-in-LXC-running-Windows-XP-in-QEMU2.png
    View
    2
    edp17
    edp17
    The first OTA update is ready. (Well, sort of :) as it requires some additional manual work.)
    Because sfos 3.4 is a stop release, the device must be OTA updated to 3.4 first.
    As I have not built a sfos 3.4 image for this device, the OTA update to version 3.4 is meant to be only an interim step.
    The manual additional work is needed because, for unknown reasons, some packages and the kernel is not deployed to the device during the update.

    The benefit of upgrading this way, rather than installing the sfos 4.0 image from scratch:
    • nemo user is kept as the default user
    • all scripts that hardcoded to use user nemo, should work without any change
    • all your data, files and apps will remain and should work as before
    • if you installed and configured a desktop Linux in an lxc container, that also should work (don't need to reinstall/reconfigure again)
    • patchmanager and installed patches like Mouse cursor, More folder icons and Notes app cover will remain working

    Here is the instruction what to do:

    Step 1 - OTA 3.3 to 3.4
    1. Boot into sfos, enable developer mode and set a password
    2. Connect the phone to a wifi network (for downloading packages)
      From this point, we will work on the PC, leave the phone connected.
    3. Connect the phone to a PC, open a console and on the PC run (enter the password when you prompted):
      Code: 
      ssh [email protected]
    4. Switch user to root (enter the password when you prompted):
      Code: 
      devel-su
    5. Check repos:
      Code: 
      ssu lr
    6. Disable all repos, except: apps, hotfixes, jolla:
      Code: 
      ssu dr <repo_name>
    7. Add/modify adaptation-community-common repo:
      Code: 
      ssu ar adaptation-community-common http://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_3.4.0.24/
    8. Add/modify adaptation-community-treltexx repo:
      Code: 
      ssu ar adaptation-community-treltexx http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/treltexx/sailfishos_3.4.0.24/
    9. In case you have the mousetracker repo
      Code: 
      ssu ar mousetracker http://repo.merproject.org/obs/home:/elros34:/sailfishapps/sailfishos_3.4.0.24/
    10. Put the device in release mode:
      Code: 
      ssu release 3.4.0.24
    11. Refresh packages:
      Code: 
      pkcon refresh
    12. Upgrade the system:
      Code: 
      version --dup
    13. Then reboot:
      Code: 
      reboot

    Step 2 - OTA 3.4 to 4.0
    1. Boot into sfos, enable developer mode and set a password
    2. Connect the phone to a wifi network (for downloading packages)
      From this point, we will work on the PC, leave the phone connected.
    3. Connect the phone to a PC, open a console and on the PC run (enter the password when you prompted):
      Code: 
      ssh [email protected]
    4. Switch user to root (enter the password when you prompted):
      Code: 
      devel-su
    5. Check repos:
      Code: 
      ssu lr
    6. Disable all repos, except: apps, hotfixes, jolla:
      Code: 
      ssu dr <repo_name>
    7. Add/modify adaptation-community-common repo:
      Code: 
      ssu ar adaptation-community-common http://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.0.1.48/
    8. Add/modify adaptation-community-treltexx repo:
      Code: 
      ssu ar adaptation-community-treltexx http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/treltexx/sailfishos_4.0.1.48/
    9. In case you have the mousetracker repo
      Code: 
      ssu ar mousetracker http://repo.merproject.org/obs/home:/elros34:/sailfishapps/sailfishos_4.0.1.48/
    10. Put the device in release mode:
      Code: 
      ssu release 4.0.1.48
    11. Refresh packages:
      Code: 
      pkcon refresh
    12. Upgrade the system:
      Code: 
      version --dup
    13. Then reboot:
      Code: 
      reboot

    Once the device is updated to 4.0 boot into TWRP and flash this kernel: 02-hybris-boot-firejail-enhanced.img
    Then boot into SFOS and install these two packages:
    Reboot again and after this, all apps and Bluetooth should work as before.

    If you have any issues, give me a shout. :)
    Good luck!
    View
    1
    edp17
    edp17
    tigerpro357 said:
    Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant
    Click to expand...
    Click to collapse

    Yes, all sources are available on github: here
    Please let me know when the UT is available for this device! I'd like to try it. :D
    View
    1
    edp17
    edp17
    OTA from 4.5.0.18 to 4.5.0.19 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 [email protected]
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.19
double check whether these three repos are pointing to the 4.5.0.19 version:
ssu lr
  adaptation-common should be https://releases.jolla.com/releases/4.5.0.19/jolla-hw/adaptation-common/armv7hl/
  adaptation-community-common should be https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.19/
  adaptation-community-treltexx should be https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.19/
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 [email protected]
systemctl-user unmask voicecall-manager.service
reboot
    View

New posts