UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Samsung S20 FE UT (Ubuntu Touch) | Android 13

    Scheduled Pinned Locked Moved Porting
    36 Posts 6 Posters 6.7k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • Sota4Ever_kS Offline
        Sota4Ever_k @Keneda
        last edited by Sota4Ever_k

        @Keneda Okay, but I'm going to put the logs that the camera gives me when I want to take a photo.
        Can I put the other topic?

        KenedaK 1 Reply Last reply Reply Quote 0
        • KenedaK Offline
          Keneda @Sota4Ever_k
          last edited by Keneda

          @Sota4Ever_k
          You can put it here as it is for your port debugging effort.

          Just use the code tag :

          Place text between 6 of those signs : `
          Three on top, three on bottom, 
          or use the editor button : </> then paste log in between
          

          2015-2023 : Meizu MX4 ☠️⚰️✝️
          2023-2024 : Nexus 5 ☠️⚰️✝️
          2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
          🇲🇫🇬🇧

          Sota4Ever_kS 1 Reply Last reply Reply Quote 0
          • Sota4Ever_kS Offline
            Sota4Ever_k @Keneda
            last edited by

            @Keneda It's going to be long, can I send it as a file?

            KenedaK 1 Reply Last reply Reply Quote 0
            • Sota4Ever_kS Offline
              Sota4Ever_k
              last edited by

              I will assume that those who read will not understand much of what I am going to say, about the process that the camera will do until the moment it gets stuck. But well...
              When I open the camera and when I take a photo it gets stuck, and assuming that I have to check in logcat or dmesg and there is this what happens to me:

              sudo lxc-attach -n android -- /system/bin/logcat  -c && sudo lxc-attach -n android -- /system/bin/logcat  > > stuck-camera-log.log
              

              It's very long, I'm going to put what NotKit mentioned to me:

              TheKit:
              from here, it seems like it did finish capturing the frame and even encoded it to JPEG:

              10-04 00:09:23.592   184  3217 I ExynosCameraSec: [CAM(0)][Back_0]-(m_captureStreamThreadFunc[25888]):[F61 T4]YUV capture done. entityID 227, FrameState(0) (227)
              10-04 00:09:23.592   184  3217 I ExynosCameraSec: [CAM(0)][Back_0]-(m_handleJpegFrame[25748]):Jpeg output done, jpeg size(2128085)
              10-04 00:09:23.592   184  3217 I ExynosCamera: [CAM(0)][Back_0]-(m_sendJpegStreamResult[3234]):Set JPEG result Done. streamId 3, frameCount 61
              10-04 00:09:23.592   184  3217 I ExynosCameraSec: [CAM(0)][Back_0]-(m_captureStreamThreadFunc[27795]):frame complete. framecount 61, frameType 4, pipeId(227)
              

              TheKit:
              and then

              10-04 00:09:23.643   184  3194 W ExynosCameraMCPipe: [CAM(0)][PIPE_ISP]-(m_getBuffer[2303]):HAL(54, 54, pbt(1) size(0)) requestFrameQ wait timeout,Duration(1),LogCnt(6) FrameQ_size(0, 0)
              10-04 00:09:23.702   184  3201 E ExynosCamera: [CAM(0)][Back_0]-(m_monitorThreadFunc[9685]):Sensor PIPE ID(6) ESD Detected. pipeCountRenew(16), lastMipiErr(0x0)
              

              Why wasn't it saved?

              Sota4Ever_kS 1 Reply Last reply Reply Quote 0
              • Sota4Ever_kS Offline
                Sota4Ever_k @Sota4Ever_k
                last edited by

                @Sota4Ever_k I would like to send the files to show more information, but it won't let me

                AppLeeA 1 Reply Last reply Reply Quote 0
                • KenedaK Offline
                  Keneda @Sota4Ever_k
                  last edited by

                  @Sota4Ever_k
                  If you use code tag, it'll be not, it is intended for that.

                  2015-2023 : Meizu MX4 ☠️⚰️✝️
                  2023-2024 : Nexus 5 ☠️⚰️✝️
                  2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
                  🇲🇫🇬🇧

                  1 Reply Last reply Reply Quote 0
                  • AppLeeA Offline
                    AppLee @Sota4Ever_k
                    last edited by

                    Hi @Sota4Ever_k

                    You can also give a link to a pad or pastebin with the full log file...

                    Sota4Ever_kS 2 Replies Last reply Reply Quote 1
                    • Sota4Ever_kS Offline
                      Sota4Ever_k @AppLee
                      last edited by

                      @AppLee https://gist.github.com/Sota4Ever/6a46c34800e5e0c9e35ecc38c91ab090
                      Here 🙂

                      Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                      • Sota4Ever_kS Offline
                        Sota4Ever_k @Sota4Ever_k
                        last edited by

                        @Sota4Ever_k And another thing, I was also able to take a photo, but I had to take the photo quickly when I entered the camera.
                        https://gist.github.com/Sota4Ever/6a46c34800e5e0c9e35ecc38c91ab090#file-quickly-camera-log-log

                        Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                        • Sota4Ever_kS Offline
                          Sota4Ever_k @Sota4Ever_k
                          last edited by

                          @Sota4Ever_k It is impossible for a human to read and understand everything I have written.

                          Sota4Ever_kS 2 Replies Last reply Reply Quote 0
                          • Sota4Ever_kS Offline
                            Sota4Ever_k @Sota4Ever_k
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • Sota4Ever_kS Offline
                              Sota4Ever_k @Sota4Ever_k
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • Sota4Ever_kS Offline
                                Sota4Ever_k @AppLee
                                last edited by

                                @AppLee Well I think I know why it can't take a photo, it's because it reached the buffer limits.

                                AppLeeA 1 Reply Last reply Reply Quote 0
                                • AppLeeA Offline
                                  AppLee @Sota4Ever_k
                                  last edited by

                                  Hi @Sota4Ever_k

                                  That's progress.
                                  But sadly I never ported Ubuntu Touch to a device, so I'm not able to help you with it.
                                  Have you tried to follow Keneda's suggestion and join the porting group on Telegram?

                                  arubislanderA 1 Reply Last reply Reply Quote 0
                                  • arubislanderA Offline
                                    arubislander @AppLee
                                    last edited by

                                    @AppLee I believe OP is already in the porter's group. They hit an obstacle with their port that has them stuck, but it seems very device specific, or else difficult to diagnose without having the port in front of you, so the suggestions of the other porters have not led to any breakthrough.

                                    🇦🇼 🇳🇱 🇺🇸 🇪🇸
                                    Happily running Ubuntu Touch
                                    Google Pixel 3a (20.04 DEV)
                                    JingPad (24.04 preview)
                                    Meizu Pro 5 (16.04 DEV)

                                    Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                                    • Sota4Ever_kS Offline
                                      Sota4Ever_k @arubislander
                                      last edited by

                                      @arubislander Yes, I'm stuck
                                      And I'm also still stuck that sometimes I can't connect to the internet when I restart the device

                                      ● NetworkManager.service - Network Manager
                                           Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
                                           Active: active (running) since Sun 2024-09-29 12:00:03 -05; 1min 55s ago
                                             Docs: man:NetworkManager(8)
                                         Main PID: 4342 (NetworkManager)
                                            Tasks: 3 (limit: 5560)
                                           Memory: 3.4M
                                           CGroup: /system.slice/NetworkManager.service
                                                   └─4342 /usr/sbin/NetworkManager --no-daemon
                                      
                                      sep 29 12:00:15 ubuntu-phablet NetworkManager[4342]: <info>  [1727629215.9285] device (p2p-dev-swlan0): supplicant management interface state: 4way_handshake -> disconnected
                                      sep 29 12:00:16 ubuntu-phablet NetworkManager[4342]: <info>  [1727629216.0273] device (swlan0): supplicant interface state: disconnected -> scanning
                                      sep 29 12:00:16 ubuntu-phablet NetworkManager[4342]: <info>  [1727629216.0274] device (p2p-dev-swlan0): supplicant management interface state: disconnected -> scanning
                                      sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <warn>  [1727629218.5755] device (swlan0): no secrets: No agents were available for this request.
                                      sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info>  [1727629218.5756] device (swlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
                                      sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info>  [1727629218.5759] manager: NetworkManager state is now DISCONNECTED
                                      sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <warn>  [1727629218.5761] device (swlan0): Activation: failed for connection '#########'
                                      sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info>  [1727629218.5765] device (swlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
                                      sep 29 12:00:19 ubuntu-phablet NetworkManager[4342]: <info>  [1727629219.6213] device (swlan0): supplicant interface state: scanning -> disconnected
                                      sep 29 12:00:19 ubuntu-phablet NetworkManager[4342]: <info>  [1727629219.6213] device (p2p-dev-swlan0): supplicant management interface state: scanning -> disconnected
                                      
                                      Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                                      • Sota4Ever_kS Offline
                                        Sota4Ever_k @Sota4Ever_k
                                        last edited by

                                        @Sota4Ever_k

                                        phablet@ubuntu-phablet:~/Downloads$ cat pe.log | grep wlan
                                        [    8.105718] wlan: Loading driver v5.2.022.3V-HS221230A
                                        [    8.106494] wlan_hdd_state wlan major(510) initialized
                                        [    8.108139] cnss: pinctrl_select_state wlan_en_sleep
                                        [    8.109147] cnss: pinctrl_select_state wlan_en_active
                                        [    8.389427] cnss: FW name added with prefix: qca6390/bdwlan.elf
                                        [    8.391856] cnss: Downloading BDF: qca6390/bdwlan.elf, size: 57836
                                        [    9.006058] cnss_pci 0000:01:00.0 wlp1s0: renamed from wlan0
                                        [    9.030189] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready
                                        [    9.030290] wlan: [4374:I:DP] 00000000: 10 76 12 29 c0 08 16 7a 99 6a a9 17 e1 e2 40 00
                                        [    9.030296] wlan: [4374:I:DP] 00000010: 39 c1 75 ef
                                        [    9.030299] wlan: [4374:I:DP] 00000000: 57 2c 2c b7 09 e3 09 18 0b 90 f7 e2 a8 40 d2 6f
                                        [    9.030302] wlan: [4374:I:DP] 00000010: 58 9d 29 73 5f c5 fe 3a 90 b2 c2 25 ed 9c d8 68
                                        [    9.030305] wlan: [4374:I:DP] 00000020: 1c f3 29 57 3b 17 90 cc 35 f6 7a 48
                                        [    9.084482] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready
                                        [    9.171887] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready
                                        [    9.270260] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready
                                        [    9.846611] init: processing action (vendor.wlan.ramdump_mode=2) from (/vendor/etc/init/wifi_qcom_ap_exynos.rc:46)
                                        
                                        Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                                        • Sota4Ever_kS Offline
                                          Sota4Ever_k @Sota4Ever_k
                                          last edited by

                                          @Sota4Ever_k hello?

                                          arubislanderA 1 Reply Last reply Reply Quote 0
                                          • arubislanderA Offline
                                            arubislander @Sota4Ever_k
                                            last edited by

                                            @Sota4Ever_k Are you DenPe on Telegram? If so. You are already in the best place to receive help there.
                                            The reason you are not getting more help is because your issues are appearantly very device specific, and dificult to diagnose for people not having the device in their hands.

                                            🇦🇼 🇳🇱 🇺🇸 🇪🇸
                                            Happily running Ubuntu Touch
                                            Google Pixel 3a (20.04 DEV)
                                            JingPad (24.04 preview)
                                            Meizu Pro 5 (16.04 DEV)

                                            Sota4Ever_kS 1 Reply Last reply Reply Quote 0
                                            • Sota4Ever_kS Offline
                                              Sota4Ever_k @arubislander
                                              last edited by

                                              @arubislander I noticed something about the wifi, it's that after a while the wifi works again.

                                              And in my repository I implemented several devices of the same processor and little by little it is working

                                              KenedaK 1 Reply Last reply Reply Quote 1
                                              • First post
                                                Last post