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

UBPORTS Stats

Scheduled Pinned Locked Moved Off topic
20 Posts 9 Posters 4.9k 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.
    • G Offline
      GIEMME
      last edited by 28 Jul 2017, 08:18

      Following the link on Ubports statistics, I could see that the number of devices that went to ubports has grown steadily. But what is the current target limit? What should the theoretical number of the UBPORTS phone be? Starting with R.Padovani's earlier remarks in this post https://rpadovani.com/how-many-ubuntu-phone and adding non-official devices to the FP2 project (but removing those who were abandoned and / or Back to Android), the "about" 8,000 devices that have the ubports image are so many? They are few?
      To what extent could we target whether all Canonical Ubuntu Touch devices migrated to Ubports?
      Nothing "scientific" .... just a summer vacation reflection! 😉

      BQ Aquaris E4.5 since 2015

      A 1 Reply Last reply 29 Jul 2017, 18:37 Reply Quote 0
      • A Offline
        advocatux @GIEMME
        last edited by 29 Jul 2017, 18:37

        @GIEMME as I see it the mere fact UBports exists is a "miracle" by it self, so it really doesn't matter if that number of phones running UBP is high or low now.

        And I say "now" because most of all Ubuntu Touch phones are legacy and going the way of the dodo.

        The future number of devices running 16.04, that will be the interesting number to me.

        1 Reply Last reply Reply Quote 1
        • O Offline
          Osndok
          last edited by 10 Aug 2017, 15:15

          This trend seems to good to be true, and the fact that there is no negative movement (only flats) makes me think it might be accumulating rather than measuring.

          e.g. if the stats per month is "where time<=month", rather than "where month(time)=month", or if there is a missing "stats.reset()"... I have no idea how/where this is implemented, but I would be interested in seeing the actual counting code.

          Also, the way it is spec'd makes me think that my one device, whenever it gets a new address (leaving home wifi, rejoining the cell tower network, and maybe even rebooting or roaming to a new super-cell) will count as a new device.

          I might notice how frequently my phone's ip changes, for this sake, but I assume that in the common case (which I assume is wifi+cell) the actual numbers are at least (and almost automatically) half what is reported.

          U 1 Reply Last reply 11 Aug 2017, 00:52 Reply Quote 1
          • U Offline
            UniSuperBox @Osndok
            last edited by 11 Aug 2017, 00:52

            @Osndok

            That's exactly what the page does. Since we don't track any devices (really! We have no idea which phone is yours!), adding another tick for each IP that hits the server is about all we can do.

            D 1 Reply Last reply 11 Aug 2017, 06:33 Reply Quote 0
            • D Offline
              doniks @UniSuperBox
              last edited by 11 Aug 2017, 06:33

              @UniSuperBox said in UBPORTS Stats:

              @Osndok

              That's exactly what the page does.

              Can you be more specific what "That" is precisely. Can someone maybe point to the code.

              Since we don't track any devices (really! We have no idea which phone is yours!),

              That is very much appreciated. Really!

              adding another tick for each IP that hits the server is about all we can do.

              Well, there should still be some confidence that the number largely represents how many people use it / how many devices are alive / something like that. Otherwise, it's a bit ... pointless.

              There was also this recent thread
              https://forums.ubports.com/topic/470/wrong-ubports-statistic/2
              Where something was supposedly reset recently ...

              Looking at https://stats.ubports.com/ now it looks like in the last 11 days the number of ubports installations grew from zero to 1300. I kinda doubt that!

              Counting hits TOGETHER with the right frequency of discarding old numbers might do the trick of representing alive devices reasonably.

              F 1 Reply Last reply 12 Aug 2017, 12:27 Reply Quote 0
              • F Offline
                flohack @doniks
                last edited by 12 Aug 2017, 12:27

                @doniks This is the reason why I suggested already to at least hash lets say some serial number plus MAC id. It is still no real tracking, since there is no user info inside, but we would immediately see precise stats...

                So either: Unique device id tracking or useless stats (but then we can switch off the stats page also ;))

                My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                1 Reply Last reply Reply Quote 0
                • U Offline
                  UniSuperBox
                  last edited by 13 Aug 2017, 00:01

                  It'd also be possible to generate a random UUID at install-time and use that to communicate with the server. Problem is that I don't think anyone wants to take on putting that code into the system image AND system image server.

                  1 Reply Last reply Reply Quote 2
                  • ? Offline
                    A Former User
                    last edited by 13 Aug 2017, 15:17

                    A mi se me ha ocurrido una idea para llevar un recuento más exacto. Si bien ahora el servidor registra la solicitud del dispositivo de buscar actualizaciones junto a la información del modelo del dispositivo, versión y canal, se podría hacer que dicha solicitud caduque al tiempo si no se vuelve a recibir otra solicitud desde el mismo móvil, pero con la diferencia de usar un ID aleatorio para cada dispositivo, o en caso contrario que se actualice la solicitud en el servidor en base al ID para no duplicar dispositivos. Espero haberme explicado bien y haber sido de ayuda 😉

                    I have an idea to take more accurate stats. Now, the server registers device’s model, version and channel that uses, that request could be made to expire at the time if another request is not received again from the same device, but with the difference of use a random ID for each device, or otherwise to update the request on the server based on the device’s ID to not duplicate. I hope I have explained well and been of help 😉
                    PD: Sorry for my bad English

                    B 1 Reply Last reply 7 Jan 2018, 22:45 Reply Quote 1
                    • D Offline
                      doniks
                      last edited by 31 Dec 2017, 10:41

                      In the meantime it shows 30K "Total Devices", which is also being picked up by other websites:

                      https://ikhaya.ubuntuusers.de/2017/12/30/ubuntu-touch-lebt-und-stellt-android-apps-in-aussicht/

                      wird die aktuelle Zahl aktiver Nutzer auf über 30.000 geschätzt.

                      Shouldn't we do something? At least change the page title to something else like "Update server access".

                      U 1 Reply Last reply 31 Dec 2017, 14:58 Reply Quote 0
                      • U Offline
                        UniSuperBox @doniks
                        last edited by 31 Dec 2017, 14:58

                        @doniks

                        Good point. I'll bring some people to this thread, maybe we need to remove the device counter for now.

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          Aury88
                          last edited by 7 Jan 2018, 08:31

                          could be based on the push notification service?...the push notification service to work shoud already know how many (unique) devices use it.

                          B 1 Reply Last reply 7 Jan 2018, 22:50 Reply Quote 1
                          • B Offline
                            Bastos @Guest
                            last edited by 7 Jan 2018, 22:45

                            @ds2000x said in UBPORTS Stats:

                            if another request is not received again from the same device

                            But this seems to be axactly the problem. we don't (want to!) to know if it is the same device or not because we don't want to track it.
                            The problem to be solved is how to identify the device without the device to be idetified...

                            F 1 Reply Last reply 9 Jan 2018, 10:40 Reply Quote 0
                            • B Offline
                              Bastos @Aury88
                              last edited by 7 Jan 2018, 22:50

                              @aury88 said in UBPORTS Stats:

                              could be based on the push notification service?...the push notification service to work shoud already know how many (unique) devices use it.

                              Maybe you are right. The moment UBpots decided to run this notification service, devices are identified anyway.

                              By realizing this, I am not sure if this central notification service is such a good idea never the less I appreciate a notification service very much.

                              Off Topic here: Afaik @DanChapman realized a local but not battery consuming notification service for dekko2 which runs like charm on my device.

                              1 Reply Last reply Reply Quote 0
                              • F Offline
                                flohack @Bastos
                                last edited by 9 Jan 2018, 10:40

                                @bastos I think we should stop being over-sensitive with the tracking problem. There is a fundamental difference between knowing how much unique devices of which hardware and which image channel we got, as opposed to tracking activity.

                                By taking a unique device id at the moment of installation and telling a server that it has been installed means just that "someone anonymous has installed ubports on a new hardware". Apps wont have access to this ID for real activity tracking. So we should allow this fingerprinting because it greatly helps us to determine the needs of the community.

                                How can I plan for server resources if I do not know the exact amount of devices? Be it 1.000 or 10.000 ? Its important to see a trend also, to just in time bring in new hardware etc.

                                The push server does not show any device that is not using a push service and therefore has never signed in to U1 account, so its also not reliable.

                                And there is a rationale for having those registrations, if we would open up the push service to the world, soon somebody will come and use it as a zombie virus/worm control dispatcher etc. The days of free access to Internet resources is over, as we trust no one. You have to identify yourself as a legit UT user to use our push server. And the easiest way is be requesting a U1 token for that.

                                A mobile device will only be as good as it has integration with some central services, and thats impossible without a minimum exchange of information. So you can choose to not use our OTA and push services, but that makes a lot things harder or impossible.

                                The local notification once more: This works because Dekko can easily check POP3 and IMAP accounts for new messages. This is far more complex with Telegram: You need to establish a full blown session to the server, do some crypto talk and then load the list of chats, find out which are muted, then from the remaining ones find those with new messages, and then find out which type of message has been sent there. Plus there are notifications that arent messages at all, which you would never get. There is a reason for implementing all this code on Telegram side, and let them send this to us. Dont think local notification is in any way a trivial, not battery-consuming process.

                                BR

                                My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                A 1 Reply Last reply 10 Jan 2018, 18:31 Reply Quote 1
                                • B Offline
                                  Bastos
                                  last edited by 10 Jan 2018, 08:19

                                  I agree, @Flohack
                                  Again thank you and your collegues for beeing privacy sensible. But you are right. There is a limit to hystery

                                  1 Reply Last reply Reply Quote 0
                                  • A Offline
                                    Aury88 @flohack
                                    last edited by 10 Jan 2018, 18:31

                                    @flohack do you think there are many upborts device without push services?
                                    however how does the id system work?

                                    F 1 Reply Last reply 10 Jan 2018, 18:34 Reply Quote 0
                                    • F Offline
                                      flohack @Aury88
                                      last edited by 10 Jan 2018, 18:34

                                      @aury88 Well we dont know 🙂 - I dont think there are many, but in theory it could be a few 100.

                                      The Id system will generate a hash value from the device MAC address plus some other installation-dependent id. Then we split the hash in half to make it double-proof and send this as unique id to the server when asking for updates.

                                      This way the server can safely count unique id´s and there is no backtrace to the user. It´s even more secure than using the IP addies since they could be linked to actual users.

                                      BR

                                      My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                      A 1 Reply Last reply 10 Jan 2018, 18:37 Reply Quote 1
                                      • A Offline
                                        Aury88 @flohack
                                        last edited by 10 Jan 2018, 18:37

                                        @flohack but when is the id sent? any random time? only at first ubport device start? on server request?

                                        F 1 Reply Last reply 10 Jan 2018, 18:38 Reply Quote 0
                                        • F Offline
                                          flohack @Aury88
                                          last edited by 10 Jan 2018, 18:38

                                          @aury88 At every time you are asking for updates, specifically OTA image updates.

                                          My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                          A 1 Reply Last reply 10 Jan 2018, 18:42 Reply Quote 1
                                          • A Offline
                                            Aury88 @flohack
                                            last edited by 10 Jan 2018, 18:42

                                            @flohack, that is a very interesting solution! thank you!

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