Hi @rubencarneiro I'm not sure about your comment, as there was already a related bug on Launchpad... I believe the dedicated N5 page is newer so not every bug in "global" has been reported in?
Also, could you please explain the origin of the problem? I'm curious about it (no information found on launchpad tickets) 
Anyway, thank you for your answer, and all the work you do for this porting project !!
Hi everyone,
A few months ago I installed UB on my Nexus 5, and for that I want to thank again all the people behind that huge work
But since the beginning (I'm on devel_rc) there is no improvement on GPS issue (not working at all), so I wanted to ask here if there were any information about a bugfix? Stable channel seems to have it working (?), should I move to it?
Thx for your answer
By the way, I was thinking... Could it be interesting to improve hammerhead device page, on the website, to describe progresses for all the channels, including stable and devel_rc? Or maybe just adding some topic gathering release comments... ? Just in case it could help, both users and developers
Hi, and thx for your feedback. Indeed, with the r292 wifi issue seems fixed on devel_rc, as the problem with phone sleep/wakeup on power button press. I don't have the mobile data problem, but so far... I think even if there are still some bugs, the development continues quite fast!
So a great thank you to all the team!
Hi,
I've installed few days ago the devel_rc build on my Nexus 5. With my little experience, here it is:
Also, but this is not really an issue: I couldn't find a way to backup and restore my SMS from previous Android phone. My eBook reader, Beru, doesn't access to the whole SD card, due to 'AppArmor restrictions'... Not so important maybe, but I found it a little annoying. This also can be fixed following these tips : http://rschroll.github.io/beru/confinement.html
For the rest, everything works fine, even if I am not sure, for now, that the ported Ubuntu phone can be used as main and only one... But wait and see, developments are going forward quite fast!
Hi,
Yes, and also, having some candles to light, before any USB plug... 
Again, I really want to thank you for your time. I finally can enjoy the UT experience, and maybe try to participate to it
Hi everyone,
So, here's the thing: I finally succeed!
I installed TWRP on my Nexus 5, and then unlocked it before following the Ubuntu official recipe to reinstall Android on a phone. Don't think the TWRP step has been really useful, but anyway... After reinstalling Android, I tried to install Ubuntu Touch, the same way I used on my first try. And it worked!!!
I used the channel devel_rc, as I saw it was highly suggested on this forum... I am also not sure but I guess the USB issue may have been related to hardware and software, as the first try failed interrupting the install with hard unplug (thx to my cat...). I may have resolved this part reinstalling Android, luckily, but I guess I'll have to replace the USB port from the N5, sooner or later.
Anyway, I am sooo happy to finally discover UT on my Nexus 5, and for now, it seems just great, even if I noticed two issues on wifi and battery display. Next step will be a small report after a week, and working with launchpad to help reporting bugs.
Many thanks to all of you who helped me, and long live to UB Ports !!
@doniks My mistake, I did a bad copy/paste in my results... So here are the new ones (with he lsusb and adb devices on fastboot mode):
4. tail -f /var/log/syslog (with the N5 booted)
Mar 2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Mar 2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Mar 2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Mar 2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Mar 2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 2 19:28:01 localhost dbus[811]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 2 19:28:01 localhost systemd[1]: Starting Hostname Service...
Mar 2 19:28:01 localhost org.freedesktop.FileManager1[1864]: (nautilus:2391): Gtk-WARNING **: Refusing to add non-unique action 'TerminalNautilus:OpenFolderLocal' to action group 'ExtensionsMenuGroup'
Mar 2 19:28:01 localhost dbus[811]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 2 19:28:01 localhost systemd[1]: Started Hostname Service.
5. tail -f /var/log/syslog (with device into recovery mode)
Mar 2 19:19:06 localhost systemd[1]: Started Hostname Service.
Mar 2 19:19:30 localhost org.freedesktop.FileManager1[1864]: App load time: 428ms
Mar 2 19:20:03 localhost dbus[811]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 2 19:20:03 localhost systemd[1]: Starting Hostname Service...
Mar 2 19:20:03 localhost dbus[811]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 2 19:20:03 localhost systemd[1]: Started Hostname Service.
Mar 2 19:24:54 localhost systemd[1]: Starting Cleanup of Temporary Directories...
Mar 2 19:24:54 localhost systemd-tmpfiles[6612]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar 2 19:24:54 localhost systemd[1]: Started Cleanup of Temporary Directories.
Mar 2 19:25:01 localhost CRON[6625]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 2 19:26:39 localhost org.freedesktop.Notifications[1864]: ** (notify-osd:2326): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong
6. lsusb (with device on fastboot mode)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 014: ID 18d1:4ee0 Google Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
7. adb devices (with device on fastboot mode)
List of devices attached
About the possible hardware issue... I can't say: I bought the N5 in second hand, and if it seemed ok, I noticed that my cables didn't fit perfectly with the USB port 
Anyway, if those new results tell you something you're welcome. Meanwhile I'll be looking for TWRP (the one I know best) for N5, if it can help...
The problem for me actually is also to be sure about the origin of my problem : hardware/software original state of this second hand device, caused by the "first try accident", ... And at the end, installing this damn' UT on this N5 ! 
@allaoua What wouldn't work? As I said just before, for some reason the problem seems in my case related to the USB connection (for some hardware or software reason)... But when I got it, the N5 is well recognized.
@doniks Here are the results from what you asked. As I was trying, I noticed that the N5 finally mounted on my laptop! But for some reason, sometimes it still loses the connection... So is it bricked, or is the USB connector which is to replace (from the N5, maybe, as I tried several cables) ?
Anyway, here are the results, with a great thank you also for your time and your kindness:
1. lsusb (without anything plugged in)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
2. lsusb (with the N5 booted)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 030: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
3. lsusb (with device into recovery mode)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
4. tail -f /var/log/syslog (with device into recovery mode)
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb 28 23:24:54 localhost dbus[814]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 28 23:24:54 localhost systemd[1]: Starting Hostname Service...
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:2394): Gtk-WARNING **: Refusing to add non-unique action 'TerminalNautilus:OpenFolderLocal' to action group 'ExtensionsMenuGroup'
Feb 28 23:24:54 localhost dbus[814]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 28 23:24:54 localhost systemd[1]: Started Hostname Service.
Feb 28 23:25:01 localhost CRON[20942]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
5. tail -f /var/log/syslog (with device into recovery mode)
Feb 28 23:19:08 localhost kernel: [35096.841602] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 28 23:19:08 localhost kernel: [35096.841607] usb 1-1: Product: Android
Feb 28 23:19:08 localhost kernel: [35096.841611] usb 1-1: Manufacturer: Google
Feb 28 23:19:08 localhost kernel: [35096.841614] usb 1-1: SerialNumber: 02e845da21307082
Feb 28 23:19:08 localhost mtp-probe: checking bus 1, device 38: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 28 23:19:08 localhost mtp-probe: bus: 1, device: 38 was not an MTP device
Feb 28 23:19:30 localhost smartd[926]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 68 to 59
Feb 28 23:20:49 localhost kernel: [35198.190092] usb 1-1: USB disconnect, device number 38
Feb 28 23:20:51 localhost kernel: [35200.286754] usb 1-1: new full-speed USB device number 39 using xhci_hcd
Feb 28 23:20:51 localhost kernel: [35200.398788] usb 1-1: device descriptor read/64, error -71
Hello,
Sorry if my initial message was not clear enough... So:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=hammerhead --bootstrapI also tried lsusb and adb devices, but without success: the first one gives me only a list with no device, and the second returns me an empty result. I don't have any particular recovery, just the Android one.
I am not an expert, but I guess it is bricked, no? Is there a way I can fix this in order to give a second try to my UT install?
Thx again for your help, hoping there will be a happy ending!
Hi everyone,
I finally bought an old (second hand) Nexus 5, in order to install UT on it. So two days ago I give it my first try and... unfortunately the USB cable has been accidentally unplugged while it was working...
Now, the N5 seems fine but it doesn't mount on my Ubuntu laptop or on my Windows desktop. adb devices and lsusb gives nothing and I am quite lost, as I can't figure out how to restore the phone, in order to try the UT install again...
Anyone having the same issue? If so, or if anyone has an idea that could help to restore the phone... It would be really great!
Thx in advance for your help!
Hi,
With new OP3t, announcing also the death of OP3, what will be the future of the OP3 porting project? Can actual work be still useful for an OP3t porting project?
What can we expect in the net months?
Thx in advance
Hello everyone, as this topic has ben writen before the OP3 category was created, could it be possible to move it in the right place?
Sure, this is just a detail... Thx
@ChloeWolfieGirl Ok... That's sad but it is fully understandable. I'll be waiting for news, also, wishing good luck to the team(s)!
Maybe there is something I would be able to do to help? I'll see if my small skills allow me to participate to porting projects... if not please do not hesitate to tell me if there is something I can do (I already participate with monthly donations, but it is not so big).
Thx a lot for your answer, and thx to everyone (developers...) here who help on those porting projects, which are, in my humble opinion, the first way for Ubuntu to meet success on phones and mobile devices.
Hello everyone,
As I am impatient to have an Ubuntu phone, but ported on the OnePlus device, I was wondering if there were already any news of the OP3 porting project, any details, ... ? I see the gauge still at the same point, for some time now... I hope not to be too much impatient?
Thanks a lot in advance for your answers, and for all the job already done here, and sorry again for being (too?) impatient!