/srv/irclogs.ubuntu.com/2016/10/10/#ubuntu-touch.txt

WoCAnyone managed to install on SGH-I957 ? (Replacing Android)00:05
OerHeksWoC, there is no port (yet) for that galaxy tab 8.9 https://wiki.ubuntu.com/Touch/Devices00:15
WoCJust checking, ty. I'm aware though... Not too sure about the boot loader and boot up standard, otherwise i would try to make one myself00:25
WoCAppreciated deshack00:25
WoCerr DerHeks00:26
OerHeksplease feel free to start a port?00:26
WoCI would be happy to, but the boot up on arm is a puzzle to me00:28
WoCnot to mention the 30+ partitions from Android00:28
WoCI'm thinking i would have the tab as a x-display and run the apps on one of the 3 servers i have on my lan00:30
WoCwhich would also enable using nfs and softlinks for additional storage...00:32
OerHeksi wish i could help you with that :-(00:32
WoC(soft mounts)00:32
WoCWell, i might figure something out... would be great having grub and ubuntu-touch on it, given that native programs gets about 200+% performance compared to Android (not incluing floatpoint math)00:36
bumbleheadthe app store on ubuntu touch is slow and does not show the page for any app that I click on...00:40
bumbleheaddoes anyone know how to get around this problem?00:40
bumbleheadI'm using a nexus 400:41
WoCif you you which app, you might want to use apt directly in a terminal00:45
WoCerr, if you know*00:45
WoCapt-cache search is handy too00:46
bumbleheadthis app https://uappexplorer.com/app/uradio.rubenxparra00:46
WoCStill trying to open that one, iḿ on a super slow connection at the moment... like 57 kbit/s00:51
WoCSo... don't hold your breath...00:52
bumbleheadit seems that the app store is generally very slow00:52
bumbleheadand my intuition is that... after a certain amount of time passes the app store app simply stops00:53
WoCsomething similar to; gnuradio - GNU Radio Software Radio Toolkit00:55
WoC?00:55
=== JanC is now known as Guest54043
=== JanC_ is now known as JanC
=== JanC is now known as Guest26650
=== JanC_ is now known as JanC
=== _salem is now known as salem_
=== salem_ is now known as _salem
tsdgeosMirv: ping?08:01
tsdgeosMirv: i was wondering, did you also rebuild unity8 on that silo for arm64 or only qt?08:02
tsdgeosdoctors appointment! bbl!08:03
=== Wellark is now known as Wellark|lunch
=== Wellark|lunch is now known as Wellark
Mirvonly qt08:48
=== LarreaMikel1 is now known as LarreaMikel
=== zenvoid_ is now known as zenvoid
=== mr_rcollins_ is now known as mr_rcollins
=== ejat_ is now known as ejat
Mirvtsdgeos: so only Qt, now there is unity8 too. so you think https://codereview.qt-project.org/#/c/169892 would require a rebuild of unity8, why? or in other words, how can we know what needs a rebuild if that change would be landed..10:04
tsdgeosMirv: so with that silo, unity8 arm64 actually passed without an unity8 rebuild?10:05
tsdgeosthat would mean a rebuild is not needed10:05
tsdgeosMirv: thing is that change touches some private headers of qtdeclarative and unity8 uses some qtdeclarative private headers10:06
tsdgeosso it would not be so far fetched that it needs an unity8 rebuild10:06
Mirvtsdgeos: I thought you were asking because of my https://bugreports.qt.io/browse/QTBUG-54822 comment where I stated i386 and armhf started segfaulting10:06
tsdgeosMirv: yes, i am10:06
tsdgeosMirv: the question is, i386 and armhf started segfaulting untiy8, but what about arm64, all was fine?10:07
Mirvtsdgeos: the autopkgtests are not run on arm6410:07
tsdgeosi see10:07
Mirvso I don't know. but amd64 was fine.10:07
tsdgeosso what was failing before?10:08
Mirvtsdgeos: and, qtdeclarative built and ran its own tests on arm64, which wasn't the case without he patch.10:08
tsdgeosok the tests10:08
Mirvtsdgeos: everything on arm64 that executes any qml, like qmlplugindump10:08
tsdgeosi'm getting a chroot with that qt on10:08
tsdgeossee if i can pin point what would be the problem10:08
Mirvtsdgeos: ok. on armhf?10:08
tsdgeoson i38610:09
Mirvoh, right10:09
tsdgeoswell amd64 hardware but a i386 chroot10:09
Mirvtsdgeos: yeah, great, I was hoping to ask you to do something like that :)10:09
tsdgeoslet's see if that still has it crashing10:09
Mirvtsdgeos: autopkgtests are now rerunning with unity8 rebuilt, but there is some worry as even ubuntu-system-settings-online-accounts on i386 (not armhf) shows segfaults: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2055-excuses/2016-10-10_08:15:02/2055_yakkety_excuses.html10:09
Mirvso that's why I was asked about the needs to rebuild, since u-s-s-o-a does not use private headers10:10
tsdgeosyeah then no10:10
=== om26er is now known as om26er_tst
=== om26er_tst is now known as om26er
dr_gogeta86hi guys10:39
faenilondra: dr_gogeta86 is looking for help on HW adaptation, can you assist him or find someone who can? ^10:55
dr_gogeta86tnx faenil10:56
tsdgeosMirv: can you add the uitk to the silo and rebuild too?11:06
tsdgeosMirv: at least unity8 gdb trace says http://paste.ubuntu.com/23302609/11:06
tsdgeosso worth rebuilding the uitk11:06
Mirvtsdgeos: ok11:12
Mirvtsdgeos: I'm fine if it'd be limited to our private header users..11:12
Mirvlet's see11:12
tsdgeosi'm also rebuilding it here, may be faster than the silo11:12
tsdgeosor not D:11:12
tsdgeosMirv: yeah rebuild of the uitk helped locally11:22
tsdgeosMirv: basically i'd say we need to rebuild everything that uses qtdeclarative-private11:23
Mirvtsdgeos: hmm..11:58
Mirvtsdgeos: then there's also the problem of vivid, I tried to apply the patch on top of 5.4 qtdeclarative and it did not only fail here or there, but pretty spectacularly11:59
Mirvtsdgeos: anyway, rebuilding qtdeclarative-abi using packages is doable, although for yakkety a bit of problem because it's being released12:00
tsdgeosMirv: do we really care for arm64+vivid+overlay?12:20
Mirvtsdgeos: well, no, true, just bileto will shout but otherwise meaningless12:23
Mirvtsdgeos: doh, ui-toolkit fails two tests on arm64 in that silo12:26
tsdgeoswell at least it doesn't crash? :D12:26
Mirvwell, I'm suspicious that it fails the tests in test file tst_textinput_touch.SEGFAULT.11.qml :D12:26
tsdgeoshmmm12:26
tsdgeosyeah :D12:26
tsdgeosMirv: and without the patch it was good? or?12:28
Mirvtsdgeos: well it's the same source that landed last Friday and was built a week ago, but I can see in another silo if something else changed meanwhile to cause that12:43
Mirvit's useful that silos are "free" now12:43
tsdgeosMirv: sure but was that with the "bad" kernel?12:43
Mirvtsdgeos: oh right I can't test it in a clean silo since because of the new kernel it will fail even more if the qtdeclarative is not there12:45
Mirvtsdgeos: yes the successful build was with the earlier kernel12:45
tsdgeosit's sad Qt upstream doesn't have arm64 CI12:46
tsdgeosso we're the ones suffering from this12:46
tsdgeosMirv: so it aws arm64 the only one failing on the new silo with qtdeclarative, toolkit and unity8, right? no other arch12:46
Mirvtsdgeos: yes: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2055/+packages12:47
tsdgeoswhich means there's no way for me to help12:47
Mirvtsdgeos: buy a frieza :)12:48
tsdgeosdo we actually run the M10 on arm64? i thought we didn't12:48
Mirvtsdgeos: well not "really really" but there's something experimental that boots ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu --device=frieza_arm6412:50
tsdgeosand with that i'd get "the bad kernel" ?12:50
Mirvtsdgeos: oh, right, no. stupid me. but if it's something else (the UITK test failure), it could be seen there. but frieza always uses 3.10 kernel so we have no way to access hardware with that.12:51
Mirv..that 4.4 kernel that causes these problems12:52
tsdgeosmeh12:53
tsdgeosso what is actually running the bad kernel?12:55
Mirvwe could land this silo to z + xenial-overlay anyway by disabling those two subtests in UITK, if no other problems12:55
tsdgeossome magic hardware?12:55
Mirvtsdgeos: the Launchpad builders12:55
tsdgeosis it qemu'ed? or there's actual hardware in there?12:56
Mirvactual arm64 hardware that was upgraded from 4.2 kernel to 4.413:00
Mirvand 4.4 kernel has CONFIG_ARM64_VA_BITS=48 enabled13:00
tsdgeosok13:03
Mirvon #ubuntu-kernel I'm trying to ask if there is any chance of tweaking that option... I'd guess they have their reasons13:06
Mirvmeanwhile I pushed qtmir* qtubuntu* to the same silo13:06
yang_is BQ Aquaris M10 the only tablet with Ubuntu touch OS ? Is there any new device to be made soon ?13:13
=== yang_ is now known as yang
=== dandrader is now known as dandrader|afk
=== Guest84871 is now known as IdleOne
=== dandrader|afk is now known as dandrader
kaisozhi!14:22
=== ABrownBear is now known as Donald_Trump
=== Donald_Trump is now known as The_Donald
=== dandrader is now known as dandrader|afk
=== nuclearbob is now known as nuclearbob_semi_
=== nuclearbob is now known as nuclearbob_holid
=== pleia2_ is now known as pleia2
abeatojdstrand, hi, the ofono PR is ready again for review15:30
=== dandrader|afk is now known as dandrader
=== LjL is now known as puuq
=== puuq is now known as LjLjL
=== LjLjL is now known as LjL
oSoMoNogra_, hey, do you happen to remember why that was needed? https://bazaar.launchpad.net/~phablet-team/ubuntu-touch-session/trunk/revision/10617:12
ogra_oSoMoN, autopilot tests17:15
ogra_and to run apps from adb shell17:15
ogra_(or ssh login)17:15
oSoMoNogra_, ok, thanks17:16
=== dandrader is now known as dandrader|afk
=== Stskeepz is now known as Stskeeps
=== dandrader|afk is now known as dandrader
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
ledufakademyhello20:14
=== mcphail_ is now known as mcphail
=== dandrader is now known as dandrader|afk
=== salem_ is now known as _salem
=== dandrader|afk is now known as dandrader

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!