[01:22] <NwS> OMG that bezels on the Ubuntu tablet -.-"
[01:22] <NwS> those*
[01:22] <NwS> or that bezel w.e
[01:23] <NwS> Why can't BQ create something prettier? fml
[08:40] <yellabs-r2> hello and , goodmorming
[08:41] <yellabs-r2> yesterday we talked about the video stutter on Bq E5 ubuntu edition with ubuntu OTA-9
[08:42] <yellabs-r2> i tried some other sites with video , and on some its the same issue ( stutter )
[08:42] <yellabs-r2> now as i was thinking about it, could it be that maybe its stuttering on buffering ?
[08:43] <yellabs-r2> and when it would buffer ( or read ahead ) a bit more , it would be solved ?
[08:43] <yellabs-r2> what do you think ?
[08:58]  * yellabs-r2 background
[10:12] <vs__> hello everybody. i have a question. can connect ubuntu phone to linux mint cinnamon 17.3?
[16:38] <CheeryLee> J
[16:39] <CheeryLee> Is anybody here?
[16:49] <CheeryLee> Can you help me with porting?
[16:57] <peat-psuwit> CheeryLee: What's your problem? Ask your question right away.
[16:59] <CheeryLee>  I built the image for my tablet, but I don't know how to flash it
[17:01] <CheeryLee> Rootstock-ng doesn't work for me.
[17:02] <peat-psuwit> CheeryLee: What's wrong?
[17:04] <CheeryLee> It copies the files of the image in /cache. But after rebooting these files disappear.
[17:06] <CheeryLee> I did everything as written in porting article (besides AppArmor).
[17:21] <peat-psuwit> CheeryLee: What does you mean "disappear"? Did you flash boot and recovery partition?
[17:28] <CheeryLee> Sure. Before flashing system.img and Ubuntu tarball I flashed boot.img and recovery.img
[17:28] <CheeryLee> Recovery works fine.
[17:31] <peat-psuwit> CheeryLee: What do you mean "disappear", anyway? Like, how do you know that they disappear?
[17:33] <CheeryLee_> Oh, disconnect
[17:34] <peat-psuwit> CheeryLee_: What do you mean "disappear", anyway? Like, how do you know that they disappear?
[17:34] <CheeryLee_> So, when rootstock-ng finishes it's operations, I reboot the tablet. After it I got cycle reboot.
[17:35] <CheeryLee_> Through TWRP I can view the root folder
[17:36] <peat-psuwit> CheeryLee_: Hey hey hey, you shouldn't have TWRP. Flash "Ubuntu" recovery.
[17:36] <CheeryLee_> I was convinced that android folder doesn't create in root.
[17:37] <CheeryLee_> No, I use TWRP for file management
[17:38] <peat-psuwit> CheeryLee_: I think there's no problem with rootstock-touch-ng
[17:38] <CheeryLee_> Even if I use ubuntu recovery, the situation will not change
[17:39] <CheeryLee_> I have no /android folder in root.
[17:39] <peat-psuwit> CheeryLee_: Anyway, when you get a bootloop (that's the word), do you get Ubuntu word with 5 dots on the purple background?
[17:40] <CheeryLee_> No. I get Samsung logo. Nothing else.
[17:41] <CheeryLee_> It seems that the kernel does not see the ramdisk.
[17:42] <peat-psuwit> CheeryLee_: Create bootloop, go to recovery (Don't let phone power off), then run "cat /proc/last_kmsg" in recovery (any recovery will do).
[17:42] <CheeryLee_> Hmm. How can I turn to recovery without rebooting?
[17:43] <CheeryLee_> ADB doesn't work
[17:43] <peat-psuwit> CheeryLee_: Press recovery combo keys when the phone reboots.
[17:46] <CheeryLee_> I I have done it many times, but last_kmsg is absent
[17:46] <CheeryLee_> I have no it
[17:47] <CheeryLee_> Maybe my kernel doesn't want to be flashed? :D
[17:47] <peat-psuwit> CheeryLee_: I don't think so. Let me think....
[17:49] <mariogrip> is the wiki down or is it just me?
[17:50] <CheeryLee> No. It works fine
[17:51] <mariogrip> humm, that's weird. it works with firefox...
[17:51] <mariogrip> not in chrome
[17:53] <CheeryLee> Hmm. I just tried the wiki in my Chrome and it works. Try to clean your cache.
[17:54] <peat-psuwit> CheeryLee: What does your bootloop look like? Samsung logo appears, briefly disappear, then re-appear, all without your intervention. Is that right?
[17:54] <CheeryLee> Yes, it is
[17:55] <peat-psuwit> CheeryLee: BTW, what's your tablet's model?
[17:56] <CheeryLee> Galaxy Note 10.1 N8000
[17:59] <peat-psuwit> CheeryLee: When bootloop happen, try pressing only volume up and not pressing power button.
[18:00] <CheeryLee> OK, i'm going to try now. Don't go leave please
[18:13] <peat-psuwit> CheeryLee: Does it works?
[18:13] <CheeryLee> Rootstock-ng now. Still waiting
[18:18] <CheeryLee> I completely forgot! When rootstock comes to 'adding android system image to installation' recovery blinking in second.
[18:19] <CheeryLee> And process doesn't finish.
[18:20] <peat-psuwit> CheeryLee: That's strange. Could you try again?
[18:21] <peat-psuwit> CheeryLee: What's on the terminal when it fails?
[18:21] <CheeryLee> 'adding android system image to installation'
[18:21] <peat-psuwit> CheeryLee: And it goes to prompt?
[18:22] <CheeryLee> Now I get that: 'Invalid sparse file format at header magi. Failed to read sparse file'
[18:23] <peat-psuwit> CheeryLee: run "file $OUT/system.img" and give me the result.
[18:24] <CheeryLee> Linux rev 1.0 ext4 filesystem data, UUID=7737b09a-291e-a752-a883-f5e38364b952, volume name "SYSTEM" (extents) (large files)
[18:29] <peat-psuwit> CheeryLee: I see now why rootstock-touch-install doesn't work. Finding the way to solve.
[18:39] <peat-psuwit> CheeryLee: Run "sed -i.bak 's#simg2img \$SYSIMG \$WORKDIR/system.img.raw#\0 || cp $SYSIMG $WORKDIR/system.img.raw#' rootstock-touch-install" in project-rootstock-ng directory
[18:40] <peat-psuwit> CheeryLee: Then try running rootstock-touch-install again
[18:48] <CheeryLee> Still this error
[18:49] <peat-psuwit> CheeryLee: Does the flashing continue?
[18:49] <CheeryLee> The flashing process ended but I got bootloop
[18:50] <peat-psuwit> CheeryLee: Then press volume up when bootloop happens
[18:50] <CheeryLee> Nothing happens when pressing
[18:50] <peat-psuwit> CheeryLee: Did you hold it?
[18:50] <CheeryLee> Sure
[18:56] <CheeryLee> Now I check /system folder. It's empty.
[18:56] <peat-psuwit> CheeryLee: That's correct. System files sits in /data/ubuntu.img
[18:57] <CheeryLee> Hmm... I have only /data/media.
[18:58] <peat-psuwit> CheeryLee: The partition is probably not mounted.
[18:58] <peat-psuwit> CheeryLee: Let's do some experiment. Run 'ls /dev/block/platform'
[18:59] <CheeryLee> I get dw_mmc and s3c-sdhci.2
[18:59] <CheeryLee> My partitions stores in /dev/block/platform/dw_mmc/by-name/
[19:00] <peat-psuwit> CheeryLee: OK, now 'ls /dev/block/platform/dw_mmc/by-name/boot'
[19:01] <CheeryLee> /dev/block/platform/dw_mmc/by-name/BOOT
[19:01] <CheeryLee> Thats what I get
[19:01] <peat-psuwit> 'dd if=/dev/zero of=/dev/block/platform/dw_mmc/by-name/BOOT bs=16 count=1'
[19:02] <CheeryLee> And?
[19:02] <peat-psuwit> CheeryLee: reboot, wishing to get fastboot mode
[19:03] <CheeryLee> My device doesn't support fastboot. Only Heimdall and Odin.
[19:03] <peat-psuwit> CheeryLee: Oh, how can I forget that?
[19:04] <CheeryLee> So, I need to reflash the kernel?
[19:05] <peat-psuwit> CheeryLee: I'm sorry. Re-flash boot.img
[19:05] <CheeryLee> Ok. It's done.
[19:07] <peat-psuwit> CheeryLee: I'm out of idea to help solving your problem. Sorry.
[19:09] <CheeryLee> It's sad. I had high hopes. :c
[19:10] <peat-psuwit> CheeryLee: BTW, do you have console=tty0 in your kernel cmdline?
[19:10] <CheeryLee> Yep.
[19:11] <CheeryLee> And when compilation finishes I get the kernel which has a many 0 bites files.
[19:21] <peat-psuwit> CheeryLee: What files?
[19:23] <CheeryLee> In initramfs.cpio.gz. In folder bin and sbin
[19:26] <peat-psuwit> CheeryLee: where?
[19:29] <CheeryLee> boot.img contaims initramfs.cpio.gz and zImage, right?
[19:29] <CheeryLee> contains*
[19:29] <peat-psuwit> CheeryLee: Right.
[19:30] <CheeryLee> So, in initramfs.cpio.gz. In folder bin and sbin
[19:31] <peat-psuwit> CheeryLee: Ok. Ther're probably symlinks to Busybox multi-call binary.
[19:32] <CheeryLee> Oh, sure. I did not take it into account
[19:34] <CheeryLee> How can I make sure that boot.img was flashed on my device?
[19:35] <CheeryLee> I think it doesn't want to flash.
[19:36] <peat-psuwit> CheeryLee: How do you flash it, BTW? In recovery?
[19:36] <CheeryLee> Through Heimdall
[19:37] <peat-psuwit> CheeryLee: Try 'md5sum /dev/block/platform/dw_mmc/by-name/BOOT' in recovery, and 'md5sum boot.img' on your computer.
[19:38] <CheeryLee> It's different
[19:39] <peat-psuwit> CheeryLee: Then try flashing in recovery
[19:40] <CheeryLee> Hmm, but i have IMG, not ZIP
[19:40] <CheeryLee> I need to create it myself?
[19:40] <peat-psuwit> CheeryLee: 'dd if=boot.img of=/dev/block/platform/dw_mmc/by-name/BOOT'
[19:41] <CheeryLee> Run on computer or adb shell?
[19:41] <peat-psuwit> CheeryLee: adb shell, in recovery
[19:43] <CheeryLee> No space left on device
[19:44] <CheeryLee> Thats what i wrote
[19:45] <CheeryLee> Kernel contains the files that take up space
[19:45] <peat-psuwit> CheeryLee: that's strange.
[19:46] <peat-psuwit> CheeryLee: I think boot partition maybe really have not enough space to hold boot image.
[19:47] <CheeryLee> How can I extend it?
[19:47] <peat-psuwit> CheeryLee: Maybe hiemdal can help. But I really don't know.
[19:52] <CheeryLee> That's strange. I just extracted initramfs.cpio.gz and got 7.2 MBytes.
[19:54] <CheeryLee> So, when i delete symlinks, the size decreases.
[19:59] <peat-psuwit> CheeryLee: I have to go now. See you again next time.
[20:00] <CheeryLee> Thanks for your reply! I will try to extend my boot partition.
[20:37] <taiebot> Eh eh looks like the Mx5 pro will be a reality \o/ look what as landed 3 days ago online https://github.com/meizuosc/m576
[20:57] <matv1> taiebot well spotted!
[21:05] <tathhu> :o
[21:05] <tathhu> damn