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! ;-)
@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.
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.
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.
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
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.
@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 ;))
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.
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