[Tama][XZ3] SDM845 PostmarketOS on mailine kernel #799
Comments
|
cc @rinigus Our tama sodp Sailfish OS maintainer |
|
For SFOS, we use Sony kernel sources with Jolla's patches and Tama config. Kernel and config are available at https://github.com/sailfishos-sony-tama/android_kernel_sony_msm . That one boots from storage just fine. But, as you can see, kernel version is 4.14.xxx |
|
@rinigus thanks, but yes this issue "solely" concerns with PmOS on a mainline kernel. (@phodina can you update the title with that? Afaik PmOS is also totally designed for and capable of running on older kernels) Maybe SfOS can utilize that some day when we resolve more issues and missing features upstream. |
phodina
changed the title
|
Btw is this the commit that fixes the UFS? (on the downstream kernel) sailfishos-sony-tama/android_kernel_sony_msm@cfd1489 |
|
mainline 😉 That is the commit, and there should be a port to mainline somewhere but no-one dared to sacrifice their device to test it yet. |
|
Sorry, yeah meant mainline. Okay, let's leave it as the last thing to do in case it bricks the device ;-) |
|
0001-arm64-dts-qcom-sdm845-tama-Set-serial-indices-and-st.zip (unzip and then |
|
Thanks @konradybcio for the patch. So the debug output has to be enabled in the patch in the kernel. The bootloader has no such functionality and the logs before the kernel boots are therefore not accessible. |
|
Another question regarding the UFS.
|
Yes, always. And this is mostly where you want to look as we've already gone through the work to make these kernels boot fully: if anything is up (and you get no USB for example), it'll be in the kernel logs.
Seems so, unfortunately. I was able to see them on Loire but that's a different (older) platform, YMMV on newer ones. |
Since the patch just enables the UART how are the pins managed? The Debug UART is on the SD card pins and I can see on the scope the CLK signal from the SD card controller to attempt to talk to the card. Is there some mux that is also need to be enabled? The modified micro SD card adapter I have has the micro SD card form factor and it triggers the Card Detect pin, that tells the kernel, there's a card inserted. |
|
The LineageOS wiki entry lists 3 models. Do we know the differences?
|
I've applied the patch but didn't get any output. Probed the pins and the pads on the uSD inserted close the circuit if I connect my multimeter to the other side of the flex cable. |
|
Typically dualsim and singlesim, and of that list H9436 has 6GB RAM whereas the others have 4. |
hmm.. I wonder if the tray detection kills off uart and kicks in sdcard.. do you think you could jerry rig pushing the sdcard adapter in without the tray? |
That's my concern #799 (comment). I have dremel so I can remove part of the pcb. Do we have some photo of something Sony or somebody else used in order to get the UART working? Or can't we just revert the CD pin? Insertion disables the uSD card interface. |
|
Good news. The issue was in loading the firmware. It was in incorrect path so using a framebuffer I could get to the logs and then modify accordingly the path. |
|
@MarijnS95 In order to get the device supported in the PostmarketOS we'll have to pick the patches and apply it to the Is my assumption correct that what's missing in the mainline is the display panel, display stream controller support and touch controller? |
|
There are few things in the log that stand out:
|
|
Also I noticed the touchscreen has input issues on the edges, same can be said if LineageOS runs on the device. Is that due to missing configuration or support in the driver? Sony has the |
|
@phodina Thank you very much for your work |
|
@MartinX3 I can definitely add those. Will there be volunteers to test the images on their devices? Can you point out the panels? I'll have to port them later as well. |
|
@phodina Since I own only a single device I couldn't test it, but I could setup a build server and provide images on xda for volunteers like I already do for SODP AOSP on tama. About the panel:
PRs: |
|
Sharing prebuild images through Github Actions (or also instructions) on XDA is a great idea. Thanks for the Issues and PRs. I'll add the Apollo and Akari and ping once done. |
|
@MartinX3 Oki, so the device is now renamed to |
|
@MarijnS95 regarding the touch screen. Do you know if there's some special way how to handle the touch screen on the curved edges as it's not responsive there. I recall Sony had some special feature called |
The DRM/MSM maintainer is already on it, trying to piece together the missing part of the DSC puzzle while wondering why our Sony SDM845 setup is working which is very similar. Which is funny since DSC was originally "brought up on" that device, but it seems to have never been tested / made it to completion No clue if you can easily turn off "side sense" and treat it as normal touches. I haven't checked the limits on mine, but without a case you'd rather reject the sides as it's very easy to activate accidental touches while merely holding the phone. |
|
@phodina in order to get a UART output, you need to put the microsd card holder tray into the slot not completely (see the photo under the spoiler), so as not to trigger the cd-gpio. And another important moment, first you have to press the power button and then connect the Rx pin to the already prepared USB-UART adapter, then you will get the UART fancy output Photo |
|
PS. in order to avoid these connection order tricks, you can try to use a pull-down ~4.7k resistor |
Thank you very much for the detailed photo and additional information. I'll test that once I'll have the uSD adapter with me and add description to the pmOS about this. |
|
Also there are incremental improvements. @MarijnS95 I was able to get the battery fuel gauge working as well as the haptics sensor on the akatsuki. I'm attempting to get also the WiFi working but that depends on the modem firmware running and atm it's crashing without any additional information. So I'll have to learn more about the https://gitlab.com/sdm845-mainline/linux/-/merge_requests/73 |
you're welcome. ping me if you need anything, I'll try to help if it's in my power |
|
@bartcubbins I tried the UART adapter. Unfortunately no UART signal, just if I plug it to far I get the SD card interface CLK signal. Regarding the pull-down. So your suggestion is to put it to the Rx line right? Also how does your adapter look like? Did the continuity test with the multimeter and the signals go for each end to the other and they are not short circuit with any other. |
|
I suspect you didn't do the connection order trick. Then my recommendation is to find a resistor. Yes, between GND and Rx, any resistor in the range of about 1-10k will work (I have tried 7.5k (purple-green-red-gold) and 2.2k (red-red-red-gold) resistors). This is a SD card in which the tracks between the card itself and the contact pads are physically broken (cut), two 0.125mm (36 AWG) wires are soldered directly to the pads and polished to prevent damage to the contacts in the device, then a 7.5k resistor is soldered between them and everything is connected to CH340G |
|
@bartcubbins So I added the pull-down resistor - 3.9k between the Rx and GND. Measured for short circuit and also checked the resistance between the GND and Rx. However, I still don't see any UART signal on the osciloscope. I tried several positions for insertion and either I get the CLK for the uSD card if inserted to much or nothing at all just GND. Is there some fastboot command to enable the UART? E.g. Pixel line of devices have them. Even without the USB UART converter there's no signal on the osciloscope as you mentioned the trick. Is it possible the UART from bootloader has UART disabled in firmware? |
|
note you'll also need to copy your modemst* and something else partitions from the ufs, store them on the sdcard in a directory and point rmtfs to them |
|
Thanks @konradybcio. I somehow forgot that we run from the uSD and some data is on the UFS internal storage. Here's the list of the partitions: I've dumped with dd the Also are these A/B partitions since they have Do you konw how to point the Also the Linux kernel is responsible for loading them, right, since it's in charge of UFS (at least on Android) and it get's some RPC from other remote processor to access the specified partition? |
|
@konradybcio Also I have an I bought it with the intention to run the test on that phone. |
|
I've found the |
No, UART is enabled by default and you should see the bootloader logs even on a locked bootloader. This is valid for all devices from Tama to Sagami platforms. |
|
If UART is correctly installed there are initial messages from bootloader. |
|
@konradybcio The dumped Still no celluar connectivity but I'll look into the other repo you suggested and modem manager/qrtr to find what's the cause. Also I've dumped the sensors from the device so I'll check them with the https://gitlab.com/sdm845-mainline/sensors-porting/-/merge_requests/2 |
|
The modem is not even listed in the Here's comparison for The remote processors are enabled by this commit, so could it be due to some regulators not being turn on? https://gitlab.com/phodina/linux/-/commit/9c5b955432ad74e6d40641e594a4605b889e4ce4 |
|
Also what's the purpose of the ~240MiB partition |
Okay, in that case it's probably the design of the adapter that triggers either the Card/Tray detect or is not inserted enough to capture the bootloader logs. I acknowledge that the kernel will not output anything unless configured correctly. |
|
sorry for the off topic. i know its the issue for tama. but i cant find any better place to ask. where can i know the mainline progress of yoshino? especially the display part. is it been abandoned? by using kernel from SoMainline/linux@4f0d15d , i can only get a working back light and usb gadget for ssh. is display still be worked on? |
|
@rhjdvsgsgks no problem hopefully someone will be able to give you more details, however if you look at the main page of the bug_tacker the |
|
@phodina deprecated by SODP which uses qualcom OEM binaries. |
|
@rhjdvsgsgks I recently got hold of Maple (while already owning Poplar) and hope to make sure they run correctly on the latest mainline fork at Some Point In Time™. Note that the commit you linked is from my personal development branch where I mainly work on SM8xxx- and SM6xxx-based devices; that commit is just to fix a compiler error, MSM8996 (which isn't even Yoshino, that's Tone) hasn't been ran on that branch. @phodina just curious why you're pointing to deprecation status in SODP's |
|
@MarijnS95 you're right the question was about the mainline and not the SODP, so my comment was not relevant ... sorry for that confusion |
glad to hear tha
i saw that branch have some new commit about nt35950 . so i think the state maybe have some changes. but obviously failed, as you said they are just some fix about compiler error |
|
thanks for the hard work of MarijnS95 and konradybcio . maple finally have a working display now (on branch https://github.com/SoMainline/linux/tree/topic/maple_wip). gpu also works, just need to enable it in dt (and add |
Platform: Tama
Device: XZ3
Kernel version: 6.4.0
Android version: None
Software binaries version: edge
Hi,
this is continuation of ticket to get PostmarketOS working on Tama XZ3. Currently it boots but do to the missing UFS drivers, that won't wipe the UFS storage the device needs workaround to boot off the SDcard.
sonyxperiadev/kernel#2558
@MarijnS95 @jerpelea @konradybcio @Thaodan
The text was updated successfully, but these errors were encountered: