@Josele13 The design is locked down now as prototypes are being made; we made the decision to only have one sim slot early on in the design process (basically, the intent is to keep things simple) and this will not change. Regarding the adapter - I simply do not know, but will try to find out for you (I'll edit this post). @Eryk-Michalak Witaj, the PinePhone will ship world-wide (with some exceptions, but Poland is not one of them). As for when it will be available; early adopter batches will ship in Q4 this year.

Found this topic again after a while, since screen of my bq 4.5 is not responding to touches anymore. Tried to do backup as explained by @Flohack in Migrate data from device to device. Below are my observations and notes. Sequence adb reboot recovery followed by adb pull /data/system-data have not copied anything, because it errored out: $ adb pull /data/system-data adb: error: failed to copy '/data/system-data/lib/ufw/user6.rules' to './system-data/lib/ufw/user6.rules': remote Permission denied Added adb root to the mix to handle "Permission denied", and after a bit of copying I've got to the next error: $ adb pull /data/system-data adb: error: failed to copy '/data/system-data/var/log/installer/media-info' to './system-data/var/log/installer/media-info': remote No such file or directory Looks like permission errors can be resolved. Why files are missing? After digging a bit (cross-referencing results of broken symlinks in recovery and normal environments, looking into mounted filesystems and layout) I think it is because of "dangling" links pointing to nowhere for the following reasons: Parts of the file system are not available in the recovery environment, because not mounted, like many click packages There are broken links in the systems (links that are broken also in normal boot) accumulated through its lifetime due to bad behaviors of install/uninstall/upgrade tools and SW in general All the above leads me to the following: Looks like adb pull should be run at least in rooted recovery (maybe it should also use -a switch to preserve permissions?) adb pull cannot handle "dangling" links So in my experience adb pull is not a good tool to make a backup. I would really appreciate, if someone could comment on the above and tip better and working ways to backup data so that it can be restored on the other device. Currently I am looking into the option of creating backup on external sdcard using tar + gzip.

Sorry to hear of Marius' grandfather passing away. I would not expect him to be present tonight, but I pray he and others are comforted in their loss. Regarding Pinephone I wonder if there is any update on how it is performing / what (if any) blockers for full usability (camera / power consumption / mobile network / etc.) there are or how it is looking?

@arubislander @dobey ,mmm ok, i belive understand, it is a problem in the frontend and backend?, example: in the best of case: i could use kotlin/kotlin native, but the result is a console app? or, in a develop of three lenguages in the case kotlin,c++ and qml. in the ultimate case, its clear, this is more work, in other words it possible, but in this moment not..?

How does it look if the badge is removed altogether? Somehow I think that the mascot can stand on its own without the roundel, especially if you're concerned about trademark disputes.

@Stefano I agree: fragmentation of the marketplace ought to be good for UT: an imperative being that we need to get it on hardware at point of sale. (I have been half expecting an announcement from Micro$oft too, suggesting they might have another go.)

Unfortunately, no, there is no current way to ship a console app and have it run inside the system terminal app. You would need to ship your own version of the terminal in your app's package, and run your app inside it.

@dobey you were correct, the location call was just being ignored. Adding the necessary lines enabled access for the webapp. Thanks for the direction. I copied this from the Morph browser code: onFeaturePermissionRequested: { switch(feature) { case WebEngineView.Geolocation: grantFeaturePermission(securityOrigin, feature, true); break; } } there is of course cases for other feature requests in the code I copied, and this just grants permission passing responsibility for approving the call to the OS. This does work around the issue where Morph asks permission each and everytime location is called, without the trouble of approving different sites as there is only one.

@tubaclarinet Thank you. I'll add that to the description

For french people, it is sometimes possible to find a compatible UT phone here : https://www.leboncoin.fr/recherche/?category=17&text=Nexus5

@matteo I can picture Yumi as an Avenger Vigilante