@viper do you mean that you are trying to use the screencast option of magic-device-tool? I have not used it myself but it looks like you need to have set up a public key for ssh for it to work. Here's the explanation of how it works from Github "This tool will start ssh on your connected Ubuntu Touch device, forward a local port to the device, copy your ssh id down to the device (so you can log in without a password), and then ssh into the device through the locally forwarded port. This results in a very nice shell, which for example can display the output of 'top' at the correct terminal size, rather than being stuck at 80x25 like 'adb shell' Like ssh-copy-id, this script will push down the newest ssh key it can find in ~/.ssh/*.pub, so if you find the wrong key being pushed down, simply use 'touch' to make your desired key the newest one, and then this script will find it. The '--copy' option will make it copy your .bashrc down to the device, giving you the benefit of preserving your $PS1 (prompt) and any aliases and functions you may have defined on your host system. " Here's some documentation on setting up SSH/OpenSSH/Keys from Ubuntu. I hope that this helps.

Oh boy it was not a nice feeling, when after install on a new FP2, which ubports-installer claimed to be "done", the system ended up with blue screen and was stuck in a boot loop. Although, finding this thread and switching to rc channel helped. Few... Still https://ubports.com/page/ubuntu-fairphone-2 needs update for two reasons: Number one is mentioned above At least new camera module does not work, see relevant issue in a bug tracker.

Just noticed the sunrise sunset info has now gone from my m10 since the latest update. All other devices seem OK just this one its on the RC channel. This scope is really looking bare now Sorry please ignore me its just come up. Just took a little time thats all must be more patient in future.

[I was originally going to ask here if you had a UBports image or the original Canonical images installed, but after re-reading, I noticed that you had Canonical's image installed (since UBports is at OTA-3 now). So feel free to disregard this post, I'm not discarding it simply because it could be of use to other people further on.] If you were using a UBports image, you shouldn't have needed to reinstall the libertine and xmir components, as they appear to come installed by default. Libertine itself also has very little in the way of dependencies. [Like above, this was before I re-read the OP] @ctyler1984 Also, you should remove the libertine-scope package and install it from the Ubuntu Store. I'm not entirely sure if the scopes are the same version, but using the click is safer since it can receive upgrades. If you receive any OTAs from UBports or Canonical (I know, this one isn't happening), the OTA will overwrite dpkg's info files and cause the system to believe the libertine-scope package isn't actually installed, even though it is, which can cause issues when attempting to reinstall, remove or even upgrade it. (This isn't theoretical, it does actually happen, I've run into it multiple times while Canonical was still the development team since I use a modified kernel for the Nexus 7 so I can run QEMU-x86/WINE on the tablet.) Also for future reference, you can remount without making the whole image fully writable by using sudo mount -o remount,rw / from the normal terminal. I know this is all a moot point now since you've solved your own issue, but hopefully it will help someone else in the future. The TL;DR: For new users to Ubuntu Touch: If you have installed from the UBports branch, libertine and it's components come installed and ready to use by default (except for the scope, you need to find that in the Ubuntu Store, or install libertine-scope using APT [Not recommended due to possible package management issues later on] You shouldn't install packages if you're expecting to be able to OTA update, it WILL cause issues with dpkg after an OTA, they might not be visible immediately, but it will definitely show up if you attempt to upgrade, reinstall or remove packages installed before the OTA that aren't a part of the default system. I'm not telling you not to do it (that would be major hypocrisy on my part), I'm just genuinely recommending that you don't. You don't need to permanently make the system writable (yes, it can be reversed by removing the .writable-image file under /userdata but that's more work than it needs to be, you can easily mount the rootfs read/write (and do it without rebooting, saving some time) by performing sudo mount -o remount,rw / from the terminal. I know the post is long, that's why I did a TL;DR, sorry for the wall of text.

@vadrian89 Not to worry. Thanks for taking the time to look and reply...and for keeping the thread alive. Maybe someone out there who knows GO will be willing to have a look. Textsecure is a great messaging app and it would be an asset to have it available and working for the Ubuntu phone.

@Shea83 said in Installation issue with Ubports installer on a Nexus 5 using a Windows 10 OS powered PC: Ubports failed to complete the installation even on my nexus 5, to make installation I always used cpt that worked wonderfully. Thank you! I tried on friday with cpt, but i was in a rush and the antivirus was not helping at all. Tried again yesterday right after your message, and it worked fine! Now i am back with Ubuntu Touch (i was a former Meizu MX4 owner).

Hi darkeye, Thank you very much! That was what was missing. After installing the Bluetooth file transfer app from the openstore, I was able to transfer files to my other device. Thank you very much again!.

@Stefano @doniks Sorry, your summons got lost in the ether for a while. [REDACTED, SEE EDIT] I don't think much has changed between the kernel used on the Flo image now and the canonical one. I think it's just the rootfs that's been updated. ################# Edit: I did some cleanup on my kernel tree. It's now buildable, the reason it wasn't prior was because of a driver the elementalX stuff pulled in (which is broken right now, not sure why yet) and I hadn't mrproper'd before commiting (what a moron I was). Kernel Tree: http://github.com/ShadowEO/TonoKrnl The kernel has the standard Android CPU governors available, however Vivid's init seems to set it to ondemand, as well as binfmt_misc (It is possible to run WINE with some sorcery under recovery to enlarge the system image, and then install the components to the system image, WINE will not run under Libertine because of proot, which it uses to set up a unprivileged chroot) Anyway, the kernel is indeed buildable, I'm running it on my 15.04 N7 right now. Perhaps I should make a thread for the kernel on here now that it's buildable, might be able to get some help with it (cleanup, optimization, etc), not sure how well received it will be though, what do you think @doniks? (Btw, was playing around with the Mainline kernel, postmarketOS, and a couple other distributions [using a modified ramdisk to boot from a directory on /data], the mainline kernel is pretty cool, but I couldn't get USB working and postmarket has no onscreen keyboard functionality.)

You're welcome

@roger said in Help install from WinXP: Roger that, got 32-bit Ubuntu running on desktop. Thank you ubuntu-16.04.3-desktop-i386.iso Is there a 32-bit version of ubports-installer to flash 1+1 phone? Not sure. https://github.com/ubports/ubports-installer/releases/tag/0.1.7-beta ubports-installer_0.1.7-beta_amd64.deb -- crashes 32-bit Ubuntu desktop ubports-installer-0.1.7-beta.dmg ? -- is this 32-bit Ubuntu desktop Nah, dmg is Apple. ubports-installer.0.1.7-beta.exe ? -- is this 64-bit Windows desktop Don't know. Have you tried it? Now that you have a 32 bit linux running, I'd try the magic device tool, pulled from git, or using ubuntu-device-flash directly, installed via apt My 1+1 phone came with Android - Can I flash UBports directly from the phone? not sure, maaaayyybe. Somewhere in this forum someone managed to manufacture an Android-zip installer for their phone .... I'd try mdt/udf first as mentioned above Edit: mdt link: https://github.com/MariusQuabeck/magic-device-tool

And by radio, I don't mean streaming internet radio...I mean an app that will use a phone's built in fm chip. Something like this http://nextradioapp.com/

There are currently a few issues with Dekko 2, but it is stating to show promise. This issue was reported a month ago, but if I am reading this gorrect it is closed now as the fix is in Milestone 0.1.4. However, there is no timeline for this fix to be rolled out. May be worth adding another comment to this to try and move things along a bit.

Thank you @Flohack for your reply. I think that is not a problem of Ubuntu Touch. Unfortunately it is related to the touch screen of my Nexus 4. I installed a paint app on UB Ports and check my touch screen and found out the down part of the screen where the Call button is located does not work properly. To do a more investigation, I also installed the Official Rom 4.2.2 and did the same check and the problem exists. Thank you.

@slannish Yes, the the system will be updated once new OTA is out, but you need to check fir update manually. Then it will download and install just like on Canonical image. There is Open Store app installed and also old Ubuntu store is present to get the apps from.

@altr0n Looking at this: https://github.com/ubports/android_kernel_lge_hammerhead/blob/ubp-5.1/arch/arm/configs/cyanogenmod_hammerhead_defconfig#L1491 bcmdhd is being built as a module. Can you confirm that it is being built? Maybe it's just not being installed. How exactly did you "craft" the boot image?

Excellent, glad you got it working! Have fun!