Porting to Samsung Galaxy Note 4 SM-N910P
-
So I have been trying to get my ofono stack working, as of now it seems like the android stuff can't access its own stuff in the /proc folder.
The list of what isn't working as of this writing is:Cellular (Ofono sees the cellular modem but can't access its own folder in /proc)
Bluetooth (completely untested)
Rotation (sensors are found but no values generated)
GPS (test_gps segfaults in halium-boot but not in hybris-boot)
Audio (untested)
S-Pen (kernel sees it as a input device but disables it for some reason)
If anyone reading this has a note 4 and wants to take on any of these tests let me know your findings and I will update the list as issues are resolved. I also welcome any advice anyone may have if they read this and are not in telegram but have an idea of what's going on.
-
So I have an update for anyone following this that isn't on telegram or IRC, there are now a couple people working with me on the Note 4 port, the devices are the Sprint, the T-Mobile, and the Trltexx. We have managed to get audio somewhat working, all the hardware as far as we can tell is seen by the kernel, and we are now just trying to get everything working on the GUI side. I have switched to telegram as the primary communication method so dont expect many updates on here, if you have a galaxy note 4 and would like to contribute, you can find me on telegram in the UBPorts group, the UBPorts porting group, and the halium group.
-
Dear @tigerpro,
Which exactly Note 4 version should I buy to support you?
Is "SM-N910P" the only that you support ?
I can see that there are different models called N4: SM-N910S, SM-N910C, SM-N910H, SM-N910L, SM-N910K.Kind regards and good luck, Piotr.
-
@pe3noATo2DOTpl i currently own a 910P and a 910V, they both have a CDMA modem in them, theres also a 910T port which is GSM and a 910F, in theory any of the variants should be able to boot the port, but without all the variants to test I cant confirm, whichever you get, let me know on telegram and I will add you into the note 4 ubports chat and we can see if we get more features working
-
@tigerpro Congrats, 3 Samsung Galaxy Note 4 models are now in UBports installer.
Can you precise what is functioning and what is not on those devices ?
-
@libremax at the time of this writing,
what works:
Audio
GPS
Status LED
Video Accelerationwhat works with quirks:
BT (if disabled requires reboot to enable again)
SMS/MMS (seems to work overall, but sometimes there is no notifications for recieved SMS/MMS, Sometimes won't send SMS/MMS either)
Auto-Brightness (Sometimes has to be toggled off then on after a reboot)
Camera (GStreamer camera is needed for Camera to not crash the device, otherwise view finder shows then device crashes after a few seconds)what doesn't work:
In Call Audio (Logs show it is working but it does not actually work, mic nor sound work)
S-Pen (detected by kernel, mir/unity does not handle styli input currently)
Sensors (they are detected, but no values are added)
Fingerprint Sensor (halium needs a repo for biometry services)I think that's everything, if I missed anything I'm sure someone will chime in and ask, I also welcome anyone who'd like to try and help, to please do so.
Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.
-
@tigerpro Thanks for your answer
What about hotspot functionality ? -
@libremax I only tried it once for a couple minutes, it turned the hotspot on, then off, and the device I connected was able to get to google, but I had the Samsung Quirks from Florian installed, and I didnt have it on for more than a couple minutes, so I would say it seems to work, but its not fully tested
-
@tigerpro
Hi!
Congratulation for this port, I read all the work you have done to finish that it was very intresting.
I have this device but it have a hardware, stuck in boot loop if it's not plug to power supply. Anyway it still works so I want to install UT.
The devices is now on unofficial Lineage 16.0 (android 9), i used odin to install it and I have the TWRP recovery. Samsung drivers, ADB minimal and fastboot are installed on the PC Win10.
Do I have to go back to a stock to a stock rom to install it through the UBports Installer? I guees yes, which one is better?Thanks.
-
@tchan if you already have twrp and a custom ROM installed, then your safe to install with the launcher, you dont need to revert software or anything. I will caution to make sure its a snapdragon variant as my port will not work on the exynos variant. I can say from experience, the bootloop issue your experiencing is a bad battery, I have 2 devices that had this issue till I replaced the battery. I would like to ask that you report back what happened if you do go ahead and try to install my port.
-
@tigerpro
Thanks for reply, I will retry, it didn't work yesterday.
When it reboot in fastboot mode after the first step, I saw "odin mode" on the first line code, is it a problème? Nothing after. Also I have to select the phone manually i the installer. Maybe I should remove the other phone driver before. I will check again if ADB reconize the phone. Cable is a USB 2.0
The phone is N910F it's a snapdragon normally. I thaught it was a battery problem but I change it 1 year ago...
If I manage to install UT I will check the battery.
Thanks!Edit: after retry same problem, the phone reboot in fastboot through the installer but after I have this error : Error: heimdall:flash: Error: {"error":{"code":3221225781,"cmd":"C:\Users\<user name>\AppData\Local\Temp\1lbGW63w4cPeKpcts4AvNGVgPjG\resources\app.asar.unpacked\node_modules\android-tools-bin\dist\win32\x86\heimdall.exe flash --BOOT C:\Users<username>\AppData\Roaming\ubports\trlte\firmware\halium-unlocked-recovery_trlte.img --RECOVERY C:\Users\fanny\AppData\Roaming\ubports\trlte\firmware\halium-unlocked-recovery_trlte.img"}}
If it's not the right place to talk about this I'am on Teleport @tchan74.
I reported the issues on the Github UBports installer to. -
@tchan that is an issue that I have not been able to resolve, I believe it may just be a limitation of the installer, when that error comes up click ignore if it is available and it should proceed as usual
-
@tigerpro
It's ok now ! ( my girlfriend have now a dual boot with ubuntu on her computeur and it was easier )
I write this from the phone you ported ! I hope you will find a solution to fix the audio call bug. I will check others fonctions.
It's very sad that you can't use your galaxy note 4 anymore cause the network support in US.
Thanks for this port. -
This post is deleted! -
so I found myself with about an hour of free time over the past couple days and decided to check into the wifi not re-connecting properly after a reboot, I suspect it is related to efs, I was able to verify it is mounted, but I have a suspicion its not mounted in the correct location, so that leads me to this question, is there a better way to force the correct location rather than putting a bind mount in init? Im not sure what else this will fix, or even if it will fix anything, but its a start since android mounts efs to /efs, and UT is mounting it to /android/efs, I suspect the stuff that is working is not fully working due to that.
Thanks for for your time.
-
-
@doniks thats actually what made me think to check it, the difference is for my device efs is mounted and I can access it, but its mounted at /android/efs rather than /efs hence me asking if anyone knows if that matters, or how to fix it
-
@tigerpro The mounts in /android are made deliberately to not "collide" with the root file system. So you cannot change that. But the container should actually "see" those mounts at / ... if this is not the case, efs might need some treatment in the lxc container setup.
-
@flohack so if Im understanding correctly, the android side sees /android as /? if that is the case then how would I massage the lxc container to get the blobs to see the efs partition?
