@dobey Thanks, I did not know that. It makes sense that there are binary compatibility issues if the D-pointer pattern is ignored Could you give me an example where the private API is used?

Is the current UT build for the VollaPhone using Halium 9? And if so, does the current UT build use the same vendor partition that is used by Volla's modified AOSP?

Updates being run should be back later.

@libremax Extra sorted, Sorry for half edit

@Thatoo No need to post the same thing in two places the answers will be the same and this Q&A thread is out of date as of yesterday really.

$ echo PATH = $ PATH: ~ / .local / bin >> ~ / .bashrc this line on the other hand has a few spaces too much

@trainailleur Thanks, but i don't want to mess with my file system. So i will ask again for this saturday ^^

Looks great! I didn't know the incoming call dialog changes its layout when there's a mouse present The port seems to always detect a mouse. Those bottom edge hints are always shown

Hi @nanu-c For your information, if you go forward in your work : @mateo_salta found an idea that maybe could useful for you also, to solve WebRTC leaks : see https://github.com/ubports/morph-browser/issues/257

@carrabelloy As has been mentioned to you before this forum is, for the benefit of all conducted in English. There are many different language speakers in this forum and providing translations to each is not possible. So that the vast majority can participate as fully as possible English has been decided upon. Please respect them and the Forum rules. At the very least you could provide a translation. I will add one this time but not again. In the future not doing so will result in the post being removed. Thanks for your understanding in this matter.