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

    Port Finishing Touches

    Scheduled Pinned Locked Moved Porting
    13 Posts 4 Posters 1.3k Views 3 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.
      • T Offline
        tigerpro
        last edited by tigerpro

        So my Galaxy Note 4 port has come a long way with help from other community members, I can confidently say it would be ready for a daily device if I didn't have these last little bits that, while aren't important to UT use, are annoyances that I know I've seen a solution for before but can no longer find. I have managed to get everything but the sensors and the stylus to work on my device, the sensors show up with "test_sensors" and the stylus works with libinput but mir or unity do not handle those events yet, I tried to look into the code for mir, but it goes over my head honestly as I am not a coder. I know Marius has briefly talked about sensorfw for sensors coming down the pipeline (which I'd love to test and give feedback) but for now, I accept that both those things are beyond my capabilities so I will just have to wait till I can get there or till the code gets there on its own. I have yet to get a working recovery with my source, and to be honest, I haven't really played with it in a while. Now for the annoyances I know I've seen a solution for (whether it was for ubports 5.1 or another version), the list overall I think is manageable, but here it goes:

        WiFi doesnt re-connect after a reboot

        BT sometimes crashes device

        Camera loads the viewfinder, sometimes takes a picture or two, and ultimately crashes the whole device

        On CDMA networks (Sprint and Verizon) I have to downgrade ofono to get a cellular signal (not UT's fault as most of the world has moved on from CDMA and EVdO)

        Charge indicator only works if device is plugged in to charger on boot

        Audio works for everything that isn't Youtube, or sound from a app that stores sounds locally (D-Bus error)

        I started this post in hopes of being able to have a centralized location for all the ports facing these issues, and possibly have a healthy discussion about things like D-Bus errors and how to fix them as there is not much info for D-Bus in regards to Ubuntu Touch. I know dbus-monitor works (how I found out I have a D-Bus error with localized audio vs audio from the web)

        I also welcome constructive criticism as long as it remains respectful and family friendly.

        I do apologize to mods if this is in wrong spot or anything of the like.

        I look forward to the healthy discussion and hopefully solutions to some of the lesser known issues

        Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.

        W dobeyD flohackF 4 Replies Last reply Reply Quote 2
        • W Offline
          wdehoog @tigerpro
          last edited by

          @tigerpro Great work. Some questions:

          • What events does libinput see but are ignored by Mir? Any logs from evtest?

          • Do you have any dbus logs while charging (in good and in bad charging state)?

          T 1 Reply Last reply Reply Quote 0
          • T Offline
            tigerpro @wdehoog
            last edited by tigerpro

            @wdehoog the events that arent being handled by unity/mir are all stylus/wacom related events (i.e. I pull stylus out, tap icon on the screen, put stylus back) dmesg will show the events for the given example, but nothing happens GUI side. I havent saved any full logs from dmesg yet but I will get some when I have a chance, did you have anything in particular you wanted me to get?

            Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.

            W 1 Reply Last reply Reply Quote 0
            • W Offline
              wdehoog @tigerpro
              last edited by

              @tigerpro lets start by logging all output from evtest on the device that responds to the stylus activity.

              and for dbus just start dbus-monitor and listen for everything. once on the system and once on the session bus.

              (use a pastebin like service)

              1 Reply Last reply Reply Quote 0
              • dobeyD Offline
                dobey @tigerpro
                last edited by

                @tigerpro said in Port Finishing Touches:

                I also welcome constructive criticism as long as it remains respectful and family friendly.

                Don't block getting the build showing up in the installer, on working stylus. It is not a trivial fix, and will require a lot of changes in multiple parts of the system to make work, because these aren't touch events, but drawing tablet events.

                T 1 Reply Last reply Reply Quote 0
                • T Offline
                  tigerpro @dobey
                  last edited by tigerpro

                  @dobey i understand that, and thats not a blocker, sorry if that wasnt clear, the recovery not working correctly is the major blocker atm, I tried adding the repos from Alfreds github, but it doesnt work for me, after that I have to find a scriptable way to install it (heimdall doesnt work for me and fastboot is not an option)

                  Edit:
                  I feel like this is focusing primarily on my port which is not what I was hoping to accomplish, I was hoping to have some solutions for the misc. Issues facing most of the near completed ports like in call audio not working or apps not working correctly (no sound/unable to queue files in music app)

                  Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.

                  dobeyD 1 Reply Last reply Reply Quote 0
                  • flohackF Offline
                    flohack @tigerpro
                    last edited by

                    @tigerpro Is the WiFi problem due to a module not being loaded, do you know whats missing? How do you get it working?

                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      tigerpro @flohack
                      last edited by tigerpro

                      @Flohack the wifi connects fine once the device is booted, and it reconnects when it scans and finds the wifi it was connected to before reboot, but as soon as I reboot, it doesnt reconnect. For my port I dont think I need any extra modules but I dont know if thats how other ports have gone. I honestly think a good chunk of my issues might be D-Bus related

                      Edit:
                      My port does have wpa_supplicant working and what not, if a device is having an issue with wifi connecting or enabling, I would think that be a good place to check

                      Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.

                      1 Reply Last reply Reply Quote 0
                      • dobeyD Offline
                        dobey @tigerpro
                        last edited by

                        @tigerpro said in Port Finishing Touches:

                        I was hoping to have some solutions for the misc. Issues facing most of the near completed ports like in call audio not working or apps not working correctly (no sound/unable to queue files in music app)

                        I suppose it would help if there were links to bug reports for these issues, specifically to comments on the issues where logs are attached that show these supposed D-Bus errors.

                        1 Reply Last reply Reply Quote 1
                        • flohackF Offline
                          flohack @tigerpro
                          last edited by

                          @tigerpro Music issues can also be caused through missing sound configs from Android. Can you check your device tree for mixer_paths.xml, acdbdata directories, and mediacodecs.xml?

                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                          T 1 Reply Last reply Reply Quote 0
                          • T Offline
                            tigerpro @flohack
                            last edited by

                            @Flohack my device has this:

                            https://github.com/tyg3rpro/android_device_samsung_trlte-common/blob/cm-14.1/audio/mixer_paths.xml

                            https://github.com/tyg3rpro/android_device_samsung_trlte-common/blob/cm-14.1/configs/media_codecs.xml

                            I dont seem to have acdbdata in my repo

                            Whether you think you can, or you can't, if you do not try, you will never truly know. So give it a Go.

                            flohackF 1 Reply Last reply Reply Quote 0
                            • flohackF Offline
                              flohack @tigerpro
                              last edited by

                              @tigerpro Ok try to copy both to /etc (UT container) for the time being and see if this changes things

                              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                              1 Reply Last reply Reply Quote 0
                              • flohackF Offline
                                flohack
                                last edited by

                                Also I started this document now: https://pad.ubports.com/p/PortChecklist - feel free to contribute!

                                BR

                                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

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