[00:26] Project daily-hammerhead build #345: SUCCESS in 12 min: http://ci.ubports.com/job/daily-hammerhead/345/ [00:28] Project ota-push build #1135: SUCCESS in 2 min 15 sec: http://ci.ubports.com/job/ota-push/1135/ [00:34] Wnl/ [00:35] who's idea was it to drop the old recovery and go with CMW? [00:35] because it's... horrible [00:35] and it's not even complete, could have waited till it was ready before replacing the old one [00:38] What old recovery? [00:39] The one that comes with vivid [00:39] On... [00:39] I'm working on getting xenial to boot on mako [00:40] I'm assuming I'm not an idiot and the only one who can't get it to boot [00:40] Well, no. No one has. No one has tried. [00:40] Except you [00:40] ahh [00:40] I see [00:40] well the kernel is fine [00:42] and but the system reboots half way through loading according to , the progress bar, and then won't do anything till I wipe cache and factory reset [00:43] and adb works, but adb logcat doesn't [00:43] No, it might not. The binaries aren't in the expected place. [00:43] Try `/system/bin/logcat` [00:45] nothing in /system/bin at all [00:45] not a single binary [00:45] wat [00:46] Is there anything in /systm [00:46] but there's recovery logs in /tmp [00:46] cd /system [00:46] oops [00:46] just the empty bin folderr [00:46] Is anything showing on screen at this point? [00:47] yeah, the boot screen loads if i do a factory reset, but then half way through the progress bar it crashes [00:47] I almost wonder if Android nuked itself [00:47] I think it could be, that I forget about the initfamfs [00:47] I remeber I need one, but can't find it [00:48] I could try to ping @mariogrip but I think he's asleep. [00:48] Well, I've still got a lot of things to try [00:50] I'm gonna make a folder where i extract the system image and ensure everything is there, in which case the partitions aren't being mounted, which means the old recovery was far superior [00:51] But lacking in the source department. [00:51] And the recovery isn't responsible for mounting partitions once you're to System [00:52] yeah, but it's responsible for mounting them when I'm in recovery [00:52] I'm gonna make my own recovery, that should solve this [00:52] Alternatively, it's possible that everything is getting pushed but Android is deleting itself once you get to the system [00:53] Or rather, the container crashes and systemd tries to start it for a second time on a single boot, deleting it. [00:54] To fix it, do the following from root in recovery: … ```mount /data/rootfs.img /mnt … chroot /mnt /bin/bash … . /etc/environment … systemctl disable lxc@android``` [00:54] That way you can adb in, (in theory) and start the container at your own leisure to see what's going on [00:55] no like, seriously, I'm not okay with the downgrade in recovery [00:55] I have always looked down on CWM, and this is CWM missing most of the features which is even worse] [00:56] TWRP is widely accepted as a better recovery with way more features [00:56] and the vivid recovery is TWRP based and worked great [00:56] it just didn't have the look of ubuntu/unity [00:57] https://code-review.phablet.ubuntu.com/#/admin/projects/?filter=recovery [00:57] If that's the case, it's Canonical's build and there's no source [00:57] Well, I'll make one [00:57] gonna try the recovery that's not device specific, see if it's any better [00:58] but we need a better recovery than this [00:58] Why? [00:59] Because it's featureless and useless [00:59] the old one was useful in more than a few ways [00:59] amrhelmy2004 was added by: amrhelmy2004 [01:00] remeber when I mentioned that my goals had to be similar to what the project leaders want... well, I really hope this isn't something we argue over [01:01] nope, no luck with the generic recovery, just a blank screen with a backlight [01:02] liek this one has less features than the stock recovery [01:02] I consider that a bad thing [01:03] Anch4 was added by: Anch4 [01:03] i just flashes lineageos recovery [01:03] 14.1 which I synced from the repo earlier today [01:04] yeah, the recovery is failing to process the fstab [01:04] that's what I see in the logs, which I couldn't see with the ubuntu official recovery [01:06] well, there was no fstab, only a recovery fstab [01:06] so that could be the problem, that it didn't have a file system to work with [01:06] Interesting. [01:07] Yeah, they might have meant to make a better recovery, but they haven't done it yet [01:08] Well, Canonical might have. We took more of a 'It updates Ubuntu and we can debug, it only needs to look pretty during updating' approach. [01:09] well, I am taking a 'it must be as functional and relevant to the os it's meant to serve as I can make it' [01:09] approach [01:09] Sure. [01:09] which the old one was [01:09] it didn't look like it was part of unity, but it had lots of functionality that I thought was good [01:10] I liked the vivid recovery [01:10] Wait... when did the recovery change? [01:11] @UniversalSuperBox, when I switched to vivid, it was a featureless CWM fork instead of a really relevant set of features in a highly modded TWRP [01:11] *switched fROM vivid [01:11] to xenial [01:12] the recovery in the rc/devel/stable channels is good [01:12] this one is not anywhere near what that one was [01:12] It changed? [01:12] uh [01:12] it's like they took out all the features and put in a nice UI and just shipped it [01:12] yes [01:12] it changed to something useless [01:12] or nearly useless [01:12] Where's the build from? [01:13] flips through pages of system-image server [01:13] Ubuntu Website [01:13] http://cdimage.ubuntu.com/ubuntu-touch/xenial/daily-preinstalled/pending/ [01:13] Oh, good. That's not our fault. [01:13] yeah, I didn't think you guys would purposely cripple your os [01:14] that's why I've been complaining, because we need to do something about this [01:14] Newest build of Xenial on our side is unfortunately still from July and only runs on the Nexus 5 ootb. [01:14] well, we can fix that fairly easily [01:15] wait [01:15] I'm tired [01:15] They're actually on the build artifacts at http://ci.ubports.com/ [01:15] Wait [01:15] I'm tired [01:16] There is no artifact for armhf rootfs [01:16] what does that mean? [01:18] xorpad, in a perfect world there'd be a rootfs ready and waiting on Jenkins for you to download [01:18] Actually, in a perfect world it'd be on cdimage.ubports.com [01:18] No in a perfect world it will be easy for me to make a better recovery than anything you've seen [01:18] but in a not so perfect world it will take time [01:21] the tarballs of the touch system are complete, i extracted the two i tried [01:22] so I'm not exactly sure the issue [01:22] Did you have adb during the boot? [01:22] what I need, is logcat from the moment the kernel boots [01:22] no [01:22] i need that [01:22] damn the thing [01:23] it's literally the worst recovery ive seen... When you click the backup/restore option, the text makes a joke about how they tricked you and it's not gonna back anything up [01:23] like, that's beyond ridiculous [01:24] whoa [01:24] yeah [01:24] I'm not complaining over little stylistic changes here [01:25] and i'm not trying to place blame either [01:25] I just want to replace this with something awesome asap [01:26] Have you put Xenial on your Nexus 5 yet? [01:26] Or, y'know, one of them? [01:26] no [01:27] Would recommend. See which recovery is going on there. [01:27] because there is no prebuilt images for it [01:27] I have to create them myself [01:27] https://wiki.ubports.com/wiki/How-to-install-Ubuntu-Touch-16.04 [01:27] this was just intended as a practice run to learn how the roms are built [01:27] figured i should know how to do that [01:28] (Photo, 720x1280) https://irc.ubports.com/N4uCNWBl/file_1038.jpg [01:28] This horribly blurry picture is what you should expect from the recovery. [01:29] yeah, it's n nothing like that [01:29] we'll have something better than that soon, i promise you [01:29] just a question of how long it takes me [01:29] I know that Canonical's Xenial image didn't run on the nexus 4, so you'll have bigger problems than the recovery [01:29] Well, that's fine [01:29] Should be able to just flash the old recovery.img and not deal with it. [01:29] I'll make it work [01:30] But that doesn't solve the problem [01:34] try flashing that recovery if you have a device that can boot it [01:34] or i'll take a picture for you [01:34] actually i think the font is too small for a picture ro show you anyting [01:43] well, this is a new experience, I never make a custom recovery before [01:48] I was able to get the ramdisk image [01:48] with make bootimage [01:54] sengloong was added by: sengloong [02:41] man... i'm gonna lose it on canonical [02:42] like I'm gonna get in my friends plane, fly to them, show up at their offices, and flip out [02:42] and by flip out i mean get violent [02:43] I just got told off for complaining that this was done, and was told it was the act of an automated build systen that was left running... i don't think an automated build system would replace a product with one that makes a joke and tells you it won't work when you press a button that's considered basic functionality [02:44] it's completely illogical, and the person kept saying I was wrong, and then saying he doesn't know what I'm talking about, back and fourth each statement contracting the one before it [02:45] and apparently it's my fault for using ubuntu [02:45] So I just won't anymore [02:45] I'll make my own distro [02:46] and I don't mean instead of this project, but they don't want to be associated at all with this project and I think their name should be taken off of it [02:46] I mean, they officially said that no one cares and the project should die [02:48] i've never heard of open source developers who care so little about the projects they work on or they are associated with [02:48] it's insane [02:49] Like i'm so upset right now [02:49] Because of their response to this nonsense and immediate rush to blame me and unports for everything [02:50] I think ubports should stay the name after that conversation i just had [02:50] but it's not my call [02:59] https://puri.sm/shop/librem-5/ [03:00] security based phone reliant on proprietary closed source driver blobs [03:00] that's a joke [03:00] any hacker would tell you that's a stupid idea [03:01] i will buy that Phone [03:03] I won't, I can put linux on a rapsberry pi with a gsm module, throw a case on it that has a space for the standard rpi touch screes, why do i need to pay someone to make me a secure phone? [03:03] like lots of people make linux based phones from raspberry pi's now [03:04] there's nice cases to put them in so they look professional [03:09] Purism Librem 5 , you should buy it too [03:11] I could but I'd rather work on this project [05:27] Welcome @Snaprack and @sengloong [05:29] Hey @Xorpad . Hopefully you have realized, that this community is different and there is a lot of support to each other. [05:29] @bastos777 that's why I'm still in this channel, but have compromised like half their network [05:29] lulz [05:29] they try to fuck us over, so I'm fucking them over [05:30] And what I read, all the core devs are appreciating that you are on board. [05:30] I'm gonna talk to someone at cannonical management before I do anything though [05:31] if they don't figure out who purposely messed up the android compatible builds and reprimand them, well I'll mess with them hard [05:32] Like, someone purposely sabotaged the code we need to make 16.04 viable on all devices [05:32] and they will pay [05:32] do you realize that Ubuntu touch is marked as out of support by canonical? [05:33] Hopefully management takes my side, and this is between me and them, I will make it clear i'm acting alone [05:33] bshah, yeah but they purposely made it a lot harder to get 16.04 working [05:33] xorpad: for instance? [05:34] someone went to the effort of making the released recoveries for the next builds 1) not work at all and 2) make jokes about how the recovery is refusing to do what we tell it to [05:34] Canonical out of my opinion has tried it best but failed. This can happen. Why to blame them about there failure? [05:34] the text output when you click backup/restore in the new recovery they replaced the old one with, just say Haha, we're not gonna back anything up, and then do nothing [05:35] and they removed files from their build tree like the fstab so that we can't boot the packages they are releasing [05:35] and the mount command [05:35] they made it impossible to mount the partitons [05:35] xorpad: can you point me to change? [05:36] http://cdimage.ubuntu.com/ubuntu-touch/xenial/daily-preinstalled/current/ [05:36] ? [05:36] all those images are designed to not work [05:36] xorpad: how? [05:37] Please fucking stop making allegations without any proof that someone made them not working intentionally [05:37] the recovery can't mount filesystem to fix it, and the fstab is gone so the kernel can't either, and the recovery doesn't do anyting [05:37] My proof is that there is no reason other than making this stuff not work on android devices for swapping out the custom recovery with one that does nothing [05:38] the mount binary and fstab are missing, so the thing boots and the crashes when it can't mount any paritions [05:38] and then it just starts bootlooping [05:38] We had the ability to fork and furthermore there are some former canonical devs with us. On top there is also Alan pope and simon quingly AFAIK current cannonical devs with us. I think together with all the great people around - including you- there is a good chance to succeed without the need to blame canonical. [05:39] And the recovery does nothing, all the stuff it used to do is gone, it used to be TWRP with features added, now it's CWM with features removed [05:40] I don't accept their explaination that an automated build system for something they don't support all of a sudden replaced the recovery with a non-functioning one not at all related to the one that was there [05:41] Someone did it out of spite [05:41] dude [05:41] you need to fucking stop [05:41] they did this so we can't use their code anymore [05:42] they said the project should just die when i asked them about it [05:42] xorpad that's enough now. Your entitled to your opinions but this isn't the place for this discussion. [05:42] Okay, sure [05:42] Ill stop talking about it [05:42] I just wish you guys believed me [05:44] i'm done talking and i'm too upset to code so i'm gonna go for a walk [05:45] It is not a question of believing. This is what we have and we should accept it as it is. All the power we have should go in support not in complaints... [05:47] I am not even sure wht the hell this fuss is about [05:47] I just checked the prebuilt recovery [05:47] and there is a mount [05:47] % ls -la sbin/mount [05:47] lrwxrwxrwx 1 bshah users 7 Oct 9 11:14 sbin/mount -> busybox [05:47] like seriousl? [05:48] I'm done talking, you told me to shut up so i'm not saying any more about it [05:48] I am pointing you to facts [05:48] but yeah, let's stop talking [05:49] cool it guys [06:24] https://puri.sm/shop/librem-5/ [06:24] looks like their almost there [07:01] Project click-import build #19: SUCCESS in 4.7 sec: http://ci.ubports.com/job/click-import/19/ [07:01] Project vivid-rootfs-armhf build #154: SUCCESS in 12 sec: http://ci.ubports.com/job/vivid-rootfs-armhf/154/ [07:01] Project ota-push build #1136: SUCCESS in 2.1 sec: http://ci.ubports.com/job/ota-push/1136/ [07:48] @wayneoutthere I enjoy your audiocasts :) [07:52] @xorpad, I agree .. The recovery has never worked and not useful .. Why can't we adopt twrp? [08:11] @andreasimonetti, Because twrp does not know how to install our OTA [08:13] Plus it makes no sense starting to work on all corners at the same time. Recovery is not on our urgent list at the moment. It may come there one day of course. [08:24] Project daily-fp2 build #363: SUCCESS in 14 min: http://ci.ubports.com/job/daily-fp2/363/ [08:25] Project ota-push build #1137: SUCCESS in 1 min 15 sec: http://ci.ubports.com/job/ota-push/1137/ [08:32] @Flohack How many developers are currently working with UBports? [08:33] @samitormanen, Hard to say. There is a bunch of 5-10 core and regular developers, and then a lot of people doing occasional contributions. [08:35] Ok. Thanks! [08:36] Remember that there were about 100 Canonicals workinf nearly all fulltime on this [08:52] Bebehero was added by: Bebehero [08:52] @popescu_sorin, I got one of those. It is fine [08:59] 😊 [10:00] Interesting conversation [10:19] @Flohack, If it needs to be held together with string to make it work at the moment, that is fine. If beautifully crafted vanadium brackets replace the string at a later date, that is also fine [11:19] Is there any way to download the Ubuntu SDK? [11:19] you can add the PPA and then install the SDK [11:20] Ya even with the PPA it doesn't seem to be available anymore [11:20] Oh, the package changed names [11:20] I should test it [11:20] I have a virtual machine with the SDK configured [11:20] do you want the link? [11:20] Is canonical still going to be updating it or did they drop it alongside ubuntu touch? [11:21] I think I've got it :) [11:21] https://drive.google.com/open?id=0B9PnbdpLgp86LWNYQ0JOcnNiTVE [11:21] it has the SDK updated on september [11:21] SDK + Images [11:21] danke :) [11:22] Going to try to compile tdesktop for ubuntu touch [11:22] user: ubucon, password: ubucon [11:22] the client that ships with ubuntu touch is too old [11:22] all the info => https://forums.ubports.com/post/4334 [11:23] @samzn, wut? triggered [11:23] tdesktop works surprisingly well on phones [11:24] it's very responsive [11:33] did you use a prebuilt? [11:34] they are all x86 [11:34] I did previously compile it when I had a nvidia housefire tablet [12:12] @Xorpad I'm not a developer, and you might even find that Nickels of Cannon purposely sabotaged the code, and that they failed us on purpose and that they are in bed with Microsoft, etc, etc. However, it's my opinion that you should take all that energy and dedicate it to focusing laser-sharp on making the code clean, open, free, and better for guys like me who don't care what Canonical does and wants a project that will be here for my daughter [12:12] as many devices as possible. So, instead of spending time and money and energy flying to give Shuttleworth the middle finger or your opinion (he won't care anyway probably since his decision is made) just help us here. We need your help. You have skills. Let's rock. Let's roll. [12:14] @wayneoutthere, And this is not about UBports :P [12:15] It is. Completely agree @wayneoutthere ! [12:16] @Lorxu, that's true again! I should be in the OT group but... actually I will defend myself here and say that it is 'on topic' but not focused enoguh perhaps. Opinion rants maybe not best here... [12:19] I think this is very much on topic. Encouraging ourselfes to support ubports even if Cannonicle has moved out is important and on topic. [12:19] @Christopher, Another fan...props to Wayne and Joe [12:21] For me it is good to know, that even if someone leaves the community do not reduce emphasis. So @wayneoutthere is encouraging me personally to further support UBports... [12:22] @bastos777, +1 [12:35] So I think the Audiocast and Youtube Live update is super important to the health and longevity of the UBports project. In my opinion Canonical had just as much a PR problem as anything else. I saw years of bad history and vocal critics in the launchpad bugs area (Network Manager and VPN) that brough down the entire feel of the project and I believe led to its demise. I was super upset with Mark for not standing up and showing off the devices at [12:35] final (mobile?) conference. So my N5 is working now, its awesome and I'm super excited. I think positivity and open communication while managing expectations is paramount. [12:36] @wayneoutthere, Summary please [12:42] @Crash_Burn, thanks :) [12:43] Ubuntu Touch changing channels and boot on Fairphone 2 [12:43] https://www.youtube.com/watch?v=6IO4nQxxbcs [12:43] changed fro stable to release candidate [12:44] 7-8 min in total, download, install, boot. quite smooth [12:44]