Categories

• General
  

  The Meta category: Organizational or general discussion.

  91
  Topics
  793
  Posts

  D

  There is an effort under way to move the ubports documentation from the wiki to readthedocs https://forums.ubports.com/topic/467/i-need-help-reorganizing-the-wiki. Can you explain the motivation for the move and for the choice of technologies? It seems to me that contributing to the documentation will be technically a bit more complicated. Are we not scaring away contributors? Are other technologies still under evaluation?

• Support
  

  Discuss and solve problems with other users

  108
  Topics
  742
  Posts

  S

  @mlinodasilva How interesting. I have an Android version and had no problems to flash either Canonical or Ubports version on it.
  Had acctually another one Androis version and also no problem to install.

  Make sure when flashing to clear recovery folder as if there is no rooom, the flash will fail.

  Device/cache/recovery and delete all inside of that folder.

• Porting
  

  Porting Ubuntu Touch to new devices

  143
  Topics
  829
  Posts

  T

  @doniks looking through the lineage repo, it doesnt look like my device is an official device, the repo from what I can tell only goes to cm13, but I do understand what your suggesting. Make sure DirtyRect is enabled everywhere, try make again, if I give up or just cant get code ro compile try a different repo and see if that works. I think Ill have to just try building cm/lineage for my device and to from there, I have a suspicion that will compile fine cause the errors Im seeing according to the default.xml file are from the ubports repo of android_hardware_qcom_display-caf and the note 4 uses the apq8084 as a display chip so ... yea ... kinda need to figure out whats going on to move forward with ubports. If I het cm to compile then I may have to switch to the cm display-caf to get moving again. A whole OS is definately harder to port than to compile, thats for sure.

• OS
  

  Discussions on development of Ubuntu Touch

  48
  Topics
  388
  Posts

  

  @Vehi_MV said in "The" Bluetooth Thread:

  @advocatux
  I think Bastos got autocorrected, it should be Pebble time round.

  Exactly. Sorry. This comes from quickly firing some thoughts...

• App Development
  

  Creating Ubuntu Touch apps

  43
  Topics
  415
  Posts

  

  @Flohack that looks fantastic! Kudos.

• Yunit
  

  Yunit discussion and development

  3
  Topics
  26
  Posts

  A

  Hi guys! about this topic I didn't read any news about the collaboration between ubport and yunit team and I'm curious to know if it is already reality or a work in progress.
  For what I understand yunit has successfully ported unity code on debian stable and is backporting to 16.04. will this migration to 16.04 be useful for ubport too?
  is it still possible to merge all the fixes and update both projects had done on their branch?

  Also I would like to know if there is some sort of collaboration between ubport (and yunit) with the canonical mir team

  about the mir support by canonical this is the actual situation
  Also mate team seems interested in a mir-based wayland compositor/client. is the collaboration between all those project on this common objective possible and already started?
  I hope in some news in the next Community Update ;-)

  bye guys and thank you!

• Translations
  

  Discussion on translating Ubuntu Touch and its core apps

  4
  Topics
  42
  Posts

  

  Do you want to help translating but don't know how to start?

  @UniSuperBox and @advocatux have joined their skills to prepare a handy guide for you:

  https://wiki.ubports.com/wiki/Getting-Started-with-Translations

• Off topic
  

  For things that just don't fit in the other categories.

  51
  Topics
  237
  Posts

  D

  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