-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[device-port] [halium-9.0] [dreamlte] Samsung Galaxy S8 #262
Comments
Hello, I'm working on Galaxy S8+ with halium-9.0 |
where did you got ? i'm interested in working with you |
I have too few linux knowledge and I decided to give up. Nothing I compile actually ran on the device. Sorry to tell you this |
Consider updating https://docs.halium.org/en/latest/supplementary/devices/dream2lte.html while you're on it. (psst https://github.com/Halium/docs/blob/master/supplementary/devices/dream2lte.rst) or maybe you should create a new file called dreamlte (regular S8) and go from there. IIRC dream2lte and dreamlte shared a common kernel/device tree, so those devices should be (theoretically) interchangeable. I myself worked on an S8+ |
Hello @pklampros , I've managed to build halium-boot and system.img for this device with halium 10 (I'll raise an issue later) for the dreamlte (S8). I've deployed these on my device but like you, nothing appears in the dmesg nor telnet, nor ssh. I want to know if you have had some ideas to work about this problem. (And maybe if you want us to work together ?) |
Last thing : When I was booting the phone, the screen stuck on the "samsung galaxy s8" splashcreen for a while without doing anything (no ssh, no telnet as I said). After a couple of minutes, the phone automatically restart. However, if I go into the twrp recovery, there is no file in /sys/fs/pstore, maybe the kernel started successfully and just the usb networking failed ? |
@Jo-Blade the reboot is most likely due to the fact that the kernel booted indeed, and the process of starting an LXC container started. The LXC container failed to boot and forced a reboot of the phone. You can check that by chrooting into rootfs.img and disabling the LXC image service. if it stops rebooting after these steps, then the kernel does boot successfully, and LXC is at fault ssh/telnet is indeed broken in the kernel itself - it's a known fact since my first initial attempt at porting the device to halium-7. to check whether it booted or not, check if there are any new files/folders generated in |
@vanyasem Sorry to not gave any news, but thanks to @abkro on the Telegram porting room, I've successfully built a halium-9 port for the device and booted in the UI. Furthermore, the usb is working, thanks to another guy who explains me I need to add the "usb-tethering" binary in /usr/bin of the rootfs. I would probably open a new issue with my manifest.xml and explanation of the fixes soon. |
@Jo-Blade wow, that's great news! would you mind sharing some photos? I am really interested in looking at your trees, please commit them anywhere you like I will close this issue once you open a new one. I appreciate the work you've done |
Tree:
usb: Manufacturer: GNU/Linux Device
appears indmesg
on host.Doesn't boot yet.
Using this unofficial LineageOS build/source/device tree
Remove multiple definitions of YYLTYPE yylloc (kernel/samsung/universal8895/scripts/dtc/dtc-lexer.l and kernel/samsung/universal8895/scripts/dtc/dtc-lexer.lex.c_shipped)
Remove
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
and add$(call inherit-product, $(SRC_TARGET_DIR)/product/halium.mk)
in device/samsung/dreamlte/lineage_dreamlte.mkThe text was updated successfully, but these errors were encountered: