[06:32] <duflu> Whee, a phone with Mir 0.18
[08:06] <dholbach> good morning
[08:36]  * donkey_12 I Love Monday!
[09:25] <JamesTait> Good morning all; happy Monday, happy New Year, and happy World Braille Day! 😃
[09:25] <lotuspsychje> ;:..:::;...::::
[10:34] <popey> Is it still the case that a device (e.g. OPO) (ping mariogrip) needs to be on Android 4.x before we flash Ubuntu on it?
[10:34] <popey> or can I have an OPO with 5.1 on it and flash ubuntu directly as per https://wiki.ubports.com/w/OnePlus_One
[11:37] <mariogrip> popey: android version should not effect Ubuntu at all, so you can flash it directly with 5.1
[11:37] <popey> oh hey :)
[11:38] <popey> I get "2016/01/04 10:57:19 Expecting the device to be in the bootloader... waiting"
[11:38] <popey> it just sits there, when I have the phone in TWRP
[11:39] <mariogrip> What does "fastboot devices" say?
[11:39] <popey> nothing mariogrip
[11:40] <mariogrip> Sudo?
[11:40] <popey> same
[11:40] <mariogrip> Is your device in fastboot mode? (adb reboot bootloader)
[11:40] <popey> no, recovery
[11:41] <mariogrip> Oh, you need to be in fastboot mode
[11:41] <popey> ok, rebooted into fastboot
[11:41] <popey> and now it shows up in fastboot devices
[11:41] <mariogrip> Then it should work
[11:41] <popey> well, it does with sudo
[11:41] <popey> just says "waiting..."
[11:42] <mariogrip> Did you start the script again?
[11:42] <popey> yes
[11:42] <popey> interestingly if I try ubuntu-device-flash with sudo, it reports the device name
[11:42] <popey> ahh, i see the issue (maybe)
[11:43] <popey> the -- in my terminal are broken because I copy pasted from your page
[11:43] <popey>  — vs --
[11:43] <popey> yeah, it's flashing now!
[11:43] <mariogrip> Oh
[11:43] <mariogrip> Cool :)
[11:43] <popey> thanks dude :)
[11:43] <popey> 2016/01/04 11:43:21 Flashing version 8 from ubuntu-touch/stable channel and server http://system-image.ubports.com to device bacon
[11:43] <popey> :D
[11:43] <popey> \o/ bacon
[11:44] <mariogrip> :D
[12:02] <popey> mariogrip, "recovery image not found, cannot continue with bootstrap" :(
[12:53] <mariogrip> popey: sorry for late answer, but I'm not home atm
[12:54] <mariogrip> But, try without bootstrap from twrp
[13:12] <popey> mariogrip, okay, thanks for the help! :D
[13:15] <popey> mariogrip, it fails in the same way unfortunately. "recovery image not found, cannot continue with bootstrap"
[13:16] <popey> gets further if I don't use --bootstrap
[13:20] <popey> mariogrip, seems to do the flash but then reboots back into twrp but doesn't install
[13:31] <mariogrip> Ah, you need to flash boot.img
[13:33] <popey> mariogrip, I purchased this OPO second-hand from someone else, and I am going through the instructions as if I'm completely new to this :)
[13:33] <popey> (which I am)
[13:34] <popey> mariogrip, so it sounds like the docs need updating
[14:22] <beuno> jdstrand_, happy new years!
[14:23] <beuno> found binaries for architecture 'all': share/locale/de/LC_MESSAGES/checkers.costa.mo, share/locale/it/LC_MESSAGES/checkers.costa.mo lint_control_architecture_valid_contents
[14:23] <beuno> those errors, are they valid for .mo's?
[14:23] <beuno> I see those more and more often
[14:36] <n1cky> is a lack of 4.2.2 sources still a preventing factor in porting devices launched with 5.0+?
[14:36] <n1cky> I've got some free time and am looking to work on a Nexus 6 port
[14:36] <n1cky> s/4.2.2/4.4.2/
[14:54] <dobey> n1cky: the nexus6 is armv8, so unless you can run an armv7 build on it, 64-bit hardware is going to require a lot more work than just building on the android 5.x kernel source
[14:55] <dobey> beuno: that seems like a bug to me.
[15:00] <n1cky> dobey: are you sure about that? My googling says that it's a Snapdragon 805, i don't think it is armv8
[15:00] <n1cky> I'm talking about Shamu not the 6P.
[15:02] <dobey> oh, ok. i thought the 6 was v8 as well
[15:02] <dobey> i guess it should be plausible then, as long as you can get the necessary features enabled in the kernel
[15:03] <dobey> there has been some work to enable ubuntu based on android 5.x, but i don't know how far along that work is
[15:11] <n1cky> cool, thank you
[16:05] <mariogrip> popey: Yeah, I'm working on a new wiki. (Sorry for not answer as so fast, i have been away all day)
[16:06] <mariogrip> popey: did you get it working btw?
[16:06] <popey> mariogrip, no problem :) - appreciate the help
[16:06] <popey> mariogrip, no, I didn't know where to get boot.img from
[16:08] <mariogrip> https://cdimage.ubports.com/ubuntu-touch/bacon/device/device_bacon.tar.xz
[16:09] <mariogrip> then it should be in the "partition" folder inside the tar ball
[16:10] <mariogrip> btw, I'm cooking up a new version based on 5.1
[16:11] <mariogrip> where mostly everything seem to work correctly
[16:12] <mariogrip> popey: ^
[16:12]  * popey looks
[16:32] <popey> mariogrip, not sure what I'm doing wrong. i used fastboot to flash boot.img, and when I try and ubuntu-device-flash it pushes all the files then reboots into twrp. Am I supposed to do something else to make it actually do the flashing?
[17:01] <mariogrip> can you check if system.img is created (in recovery in /data folder)
[17:02] <mariogrip> and sorry for the delay, i had to wrap my head around some ikea furnitures...
[17:02] <mariogrip> popey: ^
[17:02] <popey> heh
[17:03] <popey> there is no /data/recovery folder
[17:03] <mariogrip> no, look for the /data/system.img
[17:03] <popey> oh, you mean /data/system.img when in recovery mode?
[17:03] <popey> no, not there
[17:04] <mariogrip> any output when you flash?
[17:04] <popey> mariogrip, http://paste.ubuntu.com/14401350/
[17:05] <mariogrip> oh, wait twrp does not use the recovery mode adb....
[17:05] <mariogrip> okey then, reboot to bootloader
[17:05] <popey> ok
[17:05] <popey> ok, done
[17:05] <mariogrip> find the recovery.img from the tarball you downloaded
[17:06] <mariogrip> then sudo fastboot boot recovery.img
[17:06] <mariogrip> then start the flash script
[17:06] <popey> did you mean "sudo fastboot recovery recovery.img"?
[17:07] <popey> or did you really mean "sudo fastboot boot recovery.img" ?
[17:07] <mariogrip> yeah, boot
[17:07] <popey> ok
[17:07] <mariogrip> so you can keep twrp
[17:07] <popey> gotcha
[17:08] <popey> should it have done something after the sudo fastboot boot recovery.img
[17:08] <popey> it did the "downloading boot.img" thing
[17:08] <mariogrip> no, it just says on the opo logo
[17:08] <mariogrip> try adb devices
[17:08] <popey> ok
[17:08] <popey> i see it in recovery
[17:08] <mariogrip> then start the script
[17:09] <popey> so now... sudo ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[17:09] <mariogrip> no bootstarp
[17:09] <popey> ok
[17:11] <popey> mariogrip, ok. it's rebooted into twrp again
[17:11] <mariogrip> oh? log?
[17:11] <popey> same http://paste.ubuntu.com/14401431/
[17:12] <mariogrip> okey, okey, don't stop the script and do the same thing with fastboot boot recovery
[17:13] <popey> eh?
[17:14] <popey> I don't know what you mean by "don't stop the script"
[17:14] <mariogrip> wait, do you use the "ubp" twrp?
[17:15] <mariogrip> ubports twrp version
[17:15] <popey> uh, dunno. I'm just following your guide
[17:15] <popey> I have done nothing but what the steps you've said since I got this device
[17:16] <mariogrip> I see, i really need to update to the new wiki asap, sorry for the confusion
[17:16] <popey> np
[17:17] <popey> I just expected to run ubuntu-device-flash and it work :)
[17:17] <mariogrip> yeah, it should do that
[17:19] <mariogrip> okey, let's try again, reboot to bootloader can copy this ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[17:19] <davmor2> Saviq: ahayzen points out in bug 1528668 that the launcher is requiring a double tap to close it now it still is with the silo installed so I guess it isn't related to that do you need a new bug for it?
[17:19] <ubot5`> bug 1528668 in qtubuntu (Ubuntu) "[regression] Qt.application.active not working correctly" [Critical,In progress] https://launchpad.net/bugs/1528668
[17:20] <popey> mariogrip, ok, doing that
[17:21] <popey> mariogrip, "recovery image not found, cannot continue with bootstrap"
[17:23] <mariogrip> try to add --recovery-image=[recovery.img that you downloaded]
[17:23] <popey> ok
[17:23] <mariogrip> and, I need to test this for my self, that should not happen
[17:26] <popey> mariogrip, just rebooted into recovery again (twrp v2.8.6.0)
[17:26] <mariogrip> log?
[17:27] <popey> http://paste.ubuntu.com/14401561/
[17:27] <mariogrip> oh, you forgot --bootstrap
[17:27] <popey> oh
[17:27] <popey> sorry
[17:28] <mariogrip> np
[17:30] <popey> mariogrip, just sits there after:-
[17:30] <popey> 2016/01/04 17:28:11 Device is |bacon|
[17:30] <popey> 2016/01/04 17:28:11 Flashing version 8 from ubuntu-touch/stable channel and server http://system-image.ubports.com to device bacon
[17:31] <mariogrip> try to restart it, and are you in bootloader?
[17:33] <popey> mariogrip, yeah, restarting it...
[17:33] <popey> hah, now it's moving :)
[17:34] <mariogrip> :)
[17:36] <popey> mariogrip, rebooted and now at 1+ screen.
[17:36] <popey> will get a cup of tea and leave it alone ;)
[17:36] <mariogrip> :D
[17:37] <mariogrip> it now flashes, this takes a little while
[17:39] <popey> thanks for your help mariogrip! I really appreciate it!
[17:39] <mariogrip> np, im glad to help :D
[17:41] <mariogrip> to check the progress, you can use adb shell "cat /data/.last_update"
[17:41] <mariogrip> if it says true, just do adb reboot
[17:43] <Saviq> davmor2, ahayzen, doubt it's the same issue, can you please file a bug?
[17:44] <popey> nice
[17:44] <davmor2> ahayzen: do you want to do the honours?
[17:46] <mariogrip> popey: still processing?
[17:47] <mariogrip> oh, it was if the file exist then it's done.
[17:48] <mariogrip> the recovery sometimes dosent want to reboot after it's done.
[17:51] <ahayzen> davmor2, yeah no problem, Saviq which project should it be against ?
[17:52] <davmor2> ahayzen: unity8 for now Saviq can blame someone else after :D
[17:52] <ahayzen> hehe ok :-)
[17:53] <Saviq> davmor2, ahayzen, unlikely to blame someone else I'm afraid :P
[17:55] <ahayzen> davmor2, Saviq, bug 1530940
[17:55] <ubot5`> bug 1530940 in unity8 (Ubuntu) "Dismissing the launcher in the dimmed/shadow portion requires two taps" [Undecided,New] https://launchpad.net/bugs/1530940
[17:55] <Saviq> ahayzen, tx
[17:55] <ahayzen> no problem :-)
[17:58] <davmor2> ahayzen: thanks dude :)
[18:03] <kaie> hello. Is there a key-press combination to reboot a phone that is in "fastboot mode"?
[18:03] <greyback_> kaie: usually long press on power key will end that
[18:04] <kaie> my aquaris e5 was off, and I must have accidentally pressed keys that caused it to boot into fastboot mode. now it's stuck and doesn't react to anything.
[18:04] <kaie> Hmm. Yeah, I have tried long power. Let me try again
[18:05] <kaie> 20 seconds and it's still on
[18:06] <kaie> I'm on the "release candidate" channel. I installed a new OTA update today. I didn't pay attention if it ever came up again since installed. But I think it was fine, and I think I had turned it off, because I wanted to remove a sim card, but then got distracted.
[18:08] <kaie> ok, connected cable, ran "fastboot reboot", and it did.
[18:08] <kaie> Now I'm just worried this could happen me again while I'm not close to a computer.
[18:08] <greyback_> kaie: heh good, I was 90% through writing that suggestion
[18:21] <popey> mariogrip, still going and that file exists, so time to reboot?
[18:21] <mariogrip> jup
[18:21]  * popey crosses fingers
[18:23] <popey> mariogrip, sitting at the 1+ screen
[18:24] <mariogrip> adb devices
[18:24] <popey> not there
[18:26] <mariogrip> oh, did you flash boot.img?
[18:26] <mariogrip> oh, wait you used bootstrap
[18:28] <mariogrip> popey: give me a minute so i can test this, i dunno why it's not working as expected...
[18:28] <popey> sure
[18:39] <mariogrip> popey: OH! dangit,  i upgraded the system-server the other day and it does not make device part images.......!
[18:39] <popey> heh, oops
[18:40] <mariogrip> I'm so sorry about that! my head sometimes cannot keep up with everything xP
[18:43] <popey> heh
[18:59] <mariogrip> popey: now you can try XP
[19:00] <popey> sure!
[19:00] <mariogrip> now you can remove --recovery
[19:00] <mariogrip> --recovery-image=
[19:01] <popey> hmm
[19:02] <popey> power + volup ?
[19:02] <mariogrip> for bootloader yes
[19:03] <popey> not working
[19:03] <popey> wont power on
[19:03] <popey> oh, now it does
[19:03] <popey> silly phone
[19:04] <mariogrip> xP
[19:05] <mariogrip> should flash v9 now
[19:05] <mariogrip> sudo ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[19:09] <popey> yup, 9 installing
[19:09] <mariogrip> :)
[19:10] <mariogrip> and if it doesn't reboot after booting into recovery for flash, just reboot it after 10 mins
[19:11] <mariogrip> that should be plenty
[19:16] <popey> okay, i think it's done
[19:17] <popey> \o/ ubuntu logo
[19:17] <popey> welcome screen!
[19:17] <popey> Nice one mariogrip
[19:19] <popey> Ubuntu is nice and quick on this!
[19:22] <mariogrip> Yeeey :D \o/
[19:36] <mterry> morphis, hello!  I'm told you are the guy to talk to when making aosp changes?  I've got a gerrit checkout of android_bootable_recovery, but are there instructions for building?  I'm not used to Android.mk
[19:39] <morphis> mterry: I am one, yes :-)
[19:41] <morphis> mterry: its a matter of:
[19:41] <morphis> repo init ...
[19:41] <morphis> repo sync -j<n>
[19:41] <morphis> . build/envsetup.sh
[19:41] <morphis> lunch <select machine>
[19:41] <morphis> make -j4
[19:41] <morphis> should build you everything
[19:41] <mterry> morphis, I need everything?
[19:41] <morphis> there is a short cut to build just the recovery
[19:42] <morphis> ondra knows it
[19:42] <mterry> morphis, I tried the repo init route, but couldn't figure out how to pass the port to use.  I tried "repo init --repo-url=mterry@code-review.phablet.ubuntu.com:29418" but it timed out on port 22 anyway
[19:42] <mterry> So I went to just straight git
[19:42] <morphis> yeah
[19:43] <morphis> using simply https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git here
[19:43] <morphis> and pushing against ssh://morphis@code-review.phablet.ubuntu.com:29418/aosp/platform/manifest
[19:43] <morphis> mterry: https://wiki.cyanogenmod.org/w/Doc:_Building_Basics is also helpful
[19:45] <mterry> OK, repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git worked.
[19:45] <mterry> I'll add that to the wiki...
[19:48] <mterry> morphis, thanks!  This seems to be working.  I'll poke you again when I have something to review  :)  -- I'm working on a redesign of the flashing-new-image recovery animation (from design team specs)
[19:51] <morphis> mterry: great!
[19:59] <mterry> morphis, hrm.  repo sync -j4 fails due to missing git repos
[20:01] <popey> mariogrip, do you know why I have to run "sudo fastboot devices" and not just "fastboot devices"?
[20:01] <popey> mariogrip, on your pc do you have an entry in an adb.ini file somewhere for this device?
[20:02] <mariogrip> due to udev
[20:02] <popey> ah yeah
[20:02]  * popey will add a udev rule
[20:02] <popey> ta
[20:02] <genii> popey: This seems to be the same with *buntu fastboot no matter what the device attached
[20:27] <popey> hmm
[20:27] <popey> added to 70-android.rules, but it still needs sudo for fastboot, which is annoying
[20:31] <taiebot> Hi All Happy new year. Has anyone reported that on nexus 4 app cannot go fullscreen anymore on rc-proposed? It is a regression or a new feature?
[20:32] <dobey> taiebot: eh?
[20:33] <mariogrip> https://github.com/M0Rf30/android-udev-rules/blob/master/51-android.rules popey
[20:33] <taiebot> dobey app like camera used to go fullscreen (without the top bar) and now the top bar is always there. my webapp https://uappexplorer.com/app/runeaudio.taiebot65 is now always displaying the top bar
[20:34] <dobey> taiebot: ah, probably a regression in mir perhaps
[20:35] <taiebot> dobey: Ok i thought there was a design decision to not allow apps to go fullscreen anymore
[20:35] <dobey> i don't know, but i don't think so
[20:36] <dobey> there have been updates to mir and qt recently though, so maybe those caused something to break?
[20:36] <taiebot> dobey ok i create a bug report
[20:36] <dobey> yes, please do
[20:40] <taiebot> dobey: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530977
[20:40] <ubot5`> Launchpad bug 1530977 in Canonical System Image "Regression apps cannot go fullscreen" [Undecided,New]
[20:41] <dobey> kgunn: ^^ do you know if maybe mir or qtubuntu is the cause of that?
[20:42] <kgunn> dobey: not completely sure...but i think i did hear something like this morning in a unity meeting
[20:42] <kgunn> dobey: lemme ping in #ubuntu-unity
[20:43] <dobey> sure, thanks
[20:45] <kgunn> dobey: and fix is in midst of migrating
[20:45] <kgunn> aiui
[20:45] <dobey> cool
[20:46] <dobey> "already fixed and moving through the system" is my favorite type of bug reports
[21:14] <Guest66299> hi, Im trying to install ubuntu touch on a brand new nexus 7 and keep getting directory access issues. the only item I can find referencing this suggests the newest nexus devices have a different mmc card. Is there any documented solution to this?
[21:16] <popey> Guest66299, which model of nexus 7?
[21:16] <popey> 2012 or 2013?
[21:16] <Guest66299> sorry, 2013, just bought it
[21:17] <Guest66299> manufactured july 2015
[21:19] <popey> not seen that issue, sorry
[21:20] <Guest66299> Flashing the device fails with the message that the image didn't copy to /cache/recovery/ because it "Is a directory"
[21:20] <Guest66299> just found the specific error
[21:23] <Guest66299> http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to details the only info I can find
[21:24] <Guest66299> does anyone have any idea on an alternate solution?
[21:25] <dobey> Guest66299: if you can flash android 4.4 to the device, i would suggest doing that, booting to the android welcome screen, then rebooting to the bootloader and trying ubuntu-device-flash again. if android 4.4 is not instalalble on the latest nexus 7 devices, then it may require waiting until we have builds that are based on android 5.x
[21:25] <Guest66299> OK cool, I shall try that thanks
[21:26] <Guest66299> signing out now, if it works I shall post my result tomorrow.
[22:10] <taiebot> Hi all can someone else on rc-proposed confirm this bug. https://bugs.launchpad.net/unav/+bug/1530222 Thanks
[22:10] <ubot5`> Launchpad bug 1530222 in uNav "Taping on the back arrow in the main screen leads to a blank screen" [Undecided,Confirmed]
[23:02] <a10b87a10feea58e> Guest66299, dobey, popey: https://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to
[23:22] <Guest57618> Hi, spoke about an hour ago on problems installing Ubuntu on new Nexus 7, july 2015 manufacture. There appears to be an issue with the latest devices using a new MMC card which renders the stock install useless on these machines. Suggestion was to downghrade Android to 4.4. Tried this but it did not work, no version 4.x would install. re-installed version 5.1 image which worked fine. Back to starting point now, new Nexus 7 w