UBports Robot Logo UBports Forum
    • 版面
    • 最新
    • 標籤
    • 熱門
    • 使用者
    • 群組
    • 搜尋
    • 註冊
    • 登入

    Cosmo Communicator

    已排程 已置頂 已鎖定 已移動 Off topic
    62 貼文 17 Posters 31.2k 瀏覽 6 Watching
    正在載入更多貼文
    • 從舊到新
    • 從新到舊
    • 最多點贊
      回覆
      • 在新貼文中回覆
      登入後回覆
      此主題已被刪除。只有擁有主題管理權限的使用者可以查看。
      • ? 離線
        舊使用者 @Mou du GNU
        最後由 舊使用者 編輯

        @mou-du-gnu

        What's the problem with the 'm' key and the 'Fn' key?
        Is it a physical problem where they are a bit sticky or dozy and need to loosen up and 'bed in', or is it a software keyboard mapping type problem where they just don't register what they are supposed to on your French Azerty layout? I'm on UK Qwerty and pretty much everything but the keyboard backlight adjustment worked out of the box.

        Mou du GNUM 1 條回覆 最後回覆 回覆 引用 0
        • Mou du GNUM 離線
          Mou du GNU @訪客
          最後由 編輯

          @moncon For me the layout is good for all the keys but the "m" one (output is "ù") and Fn key doesn't work. I think it is surely a keyboard mapping problem. I don't have it with the linux boot.

          KenedaK S 2 條回覆 最後回覆 回覆 引用 0
          • KenedaK 離線
            Keneda @Mou du GNU
            最後由 編輯

            @mou-du-gnu
            Forgive my off topic, but i love your nick lol

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

            1 條回覆 最後回覆 回覆 引用 0
            • S 離線
              sven @Mou du GNU
              最後由 編輯

              @mou-du-gnu There have been keyboard mapping problems (Russian, Dvorak, ...) that have been resolved quite quickly via an issue in gitlab. Please open a good one at https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/issues

              VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-9), Pocophone F1 (pmOS, edge), FLX1 (Debian)

              ? 1 條回覆 最後回覆 回覆 引用 0
              • ? 離線
                舊使用者 @sven
                最後由 舊使用者 編輯

                @sven @mou-du-gnu

                @sven said in Cosmo Communicator:

                @mou-du-gnu There have been keyboard mapping problems (Russian, Dvorak, ...) that have been resolved quite quickly via an issue in gitlab. Please open a good one at https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/issues

                Yes, let us know how you get on, keep us in the loop, hopefully this will be resolved soon.

                I'll see if I can reproduce the same behaviour on my unit by selecting AZERTY keyboard and French language if need be when I get a chance.

                S 1 條回覆 最後回覆 回覆 引用 0
                • S 離線
                  sven @訪客
                  最後由 編輯

                  @Mou-du-GNU The relevant section is labelled "French" in https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/blob/master/overlay/system/usr/share/X11/xkb/symbols/planet_vndr/cosmo
                  AE... is the top row of keys, AD the second etc. Compare to your physical keyboard.

                  VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-9), Pocophone F1 (pmOS, edge), FLX1 (Debian)

                  Mou du GNUM 1 條回覆 最後回覆 回覆 引用 0
                  • Mou du GNUM 離線
                    Mou du GNU @sven
                    最後由 Mou du GNU 編輯

                    @sven
                    The solution was to declare the existing french cosmo layout in the evdev.xml file. I added :

                    <variant>
                       <configItem>
                         <name>fr</name>
                         <shortDescription>fr</shortDescription>
                         <description>French (Cosmo Communicator)</description>
                         <languageList>
                           <iso639Id>fr</iso639Id>
                         </languageList>
                       </configItem>
                     </variant>
                    
                    

                    in the "planet" section as explained here : https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/issues/3

                    Then the Cosmo communicator layout appears in the variants of French in the physical keyboard menu of UT. Didn't touch to the layout file at all.

                    Thanks both of you for the tips. Works perfectly now.

                    Mou du GNUM 1 條回覆 最後回覆 回覆 引用 2
                    • Mou du GNUM 離線
                      Mou du GNU @Mou du GNU
                      最後由 編輯

                      @mou-du-gnu I pushed my exploration of UT on Cosmo with a french keyboard further.
                      The keyboard layout works perfectly on UT and apps.
                      I tried to install a couple linux apps in a Libertine container and suddenly I'm back to sort of a qwerty layout. The keyboard layout indicator in UT switches to "En" (English Cosmo communicator, UK) wich explains the issue. I haven't found a way to revert to a French layout.
                      As soon as I go back to an app in UT, the layout is correct again.

                      1 條回覆 最後回覆 回覆 引用 0
                      • PrometheusP 離線
                        Prometheus @訪客
                        最後由 編輯

                        @moncon - Very nice instructions, thank you. Can you tell us more about the full functionality of Ubuntu Touch on Cosmo Communicator (i.e. What works and what doesn't work)?

                        S ? 3 條回覆 最後回覆 回覆 引用 0
                        • S 離線
                          sven @Prometheus
                          最後由 編輯

                          @prometheus I am running UBports on Cosmo Communicators for a year. The coverage is not complete, but it might fit your needs, see https://devices.ubuntu-touch.io/device/cosmo-communicator/

                          VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-9), Pocophone F1 (pmOS, edge), FLX1 (Debian)

                          PrometheusP 1 條回覆 最後回覆 回覆 引用 0
                          • PrometheusP 離線
                            Prometheus @sven
                            最後由 編輯

                            @sven - Thanks sven! Just was wondering if 4G calling, text, email, data and wifi along with respective notifications were working reliably since "Port Progress" shows "Inactive".

                            KenedaK S 2 條回覆 最後回覆 回覆 引用 0
                            • KenedaK 離線
                              Keneda @Prometheus
                              最後由 編輯

                              @prometheus
                              4G calling, a.k.a. VoLTE is not handled by uTouch, no matter what phone you'll try, for now.

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

                              PrometheusP 1 條回覆 最後回覆 回覆 引用 0
                              • S 離線
                                sven @Prometheus
                                最後由 編輯

                                @prometheus Wifi works reliably (except the hotspot, but this is broken on many UBports devices). I have no SIM card, so I cannot report about mobile data.

                                VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-9), Pocophone F1 (pmOS, edge), FLX1 (Debian)

                                PrometheusP 1 條回覆 最後回覆 回覆 引用 0
                                • PrometheusP 離線
                                  Prometheus @Keneda
                                  最後由 編輯

                                  @keneda - Thanks for the 4G/VoLTE issue heads up. Do you know if at least 3G voice, text, and data along with notifications are working reliably on Cosmo/UBports?

                                  KenedaK 1 條回覆 最後回覆 回覆 引用 0
                                  • PrometheusP 離線
                                    Prometheus @sven
                                    最後由 編輯

                                    @sven - Thanks again sven!

                                    1 條回覆 最後回覆 回覆 引用 0
                                    • KenedaK 離線
                                      Keneda @Prometheus
                                      最後由 Keneda 編輯

                                      @prometheus
                                      Can't tell you as i don't have Cosmo.
                                      But it works perfectly well on my MX4.

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

                                      TotalSonicT 1 條回覆 最後回覆 回覆 引用 0
                                      • TotalSonicT 離線
                                        TotalSonic @Keneda
                                        最後由 編輯

                                        Curious - does the outside screen on the Communicator just always stay blank with UT, or does it display something?

                                        Best regards,
                                        Steve Berson

                                        S 1 條回覆 最後回覆 回覆 引用 0
                                        • S 離線
                                          sven @TotalSonic
                                          最後由 sven 編輯

                                          @totalsonic It is on per default, but does not show anything useful and battery will drain even if the cosmo is turned off. So, better turn the CoDi off. (How? I can provide a link to a relevant topic, if needed.)

                                          VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-9), Pocophone F1 (pmOS, edge), FLX1 (Debian)

                                          1 條回覆 最後回覆 回覆 引用 0
                                          • ? 離線
                                            舊使用者 @Prometheus
                                            最後由 編輯

                                            @prometheus I've been running Ubuntu Touch on Cosmo since November, and as my only device (pda, phone, laptop, shopping list, torch) since April until the network connection recently went bad. I don't think it's a Ubuntu Touch issue, I've reflashed and tried Debian and even Ugly Android and the problem remains. It's still my constant companion as a UT-PDA, but now my PinePhone is my phone, which is entertaining at times but that's another thread.
                                            Looking at https://devices.ubuntu-touch.io/device/cosmo-communicator/ I think the 'What works' section is about right, but I think the summary under 'Automated Usability' is a bit harsh. Until I lost the network connection mine worked very well as a phone (and everything else).
                                            By the way @TotalSonic @Sven, I was getting notifications on my CoDi for incoming calls and LED for SMS (I think there was a limitation from day one on any OS where it would only show the callers name for the first couple of hundred contacts and after that just the numbers) but I've also disabled it for battery since the network connection disappeared. If I got the network back tomorrow I'd probably leave it powered down and try a PineTime instead. In essence a Gemini with a backlit keyboard and a remote CoDi.
                                            As for the 'Status (Inactive)', I think it's still getting attention by NotKit and others, and I still get regular updates on Development channel, but perhaps the 'inactive' status reflects that the CC doesn't have the UBports installer tool and needs a more manual approach to install. I don't know.
                                            In summary, I've been more than happy running Ubuntu Touch on my Cosmo, but that's my use case and expectations, YMMV. If you happen to have a Cosmo I would recommend giving UT a whirl, if not maybe wait and see what happens with the Astro Slide or the Pro1-X.

                                            1 條回覆 最後回覆 回覆 引用 1
                                            • ? 離線
                                              舊使用者 @Prometheus
                                              最後由 編輯

                                              p.s.
                                              @prometheus
                                              Apologies for the delay in replying, been a bit busy.

                                              PrometheusP 1 條回覆 最後回覆 回覆 引用 0
                                              • 第一個貼文
                                                最後的貼文