=== salem_ is now known as _salem | ||
atlaspaine | hell | 08:37 |
---|---|---|
atlaspaine | hello | 08:37 |
atlaspaine | my device is not supported, a moto x play, | 08:37 |
atlaspaine | i want to try out ubuntu touch, what would you recommend? | 08:37 |
atlaspaine | any guidance is appreciated :) | 08:37 |
atlaspaine | hello? | 08:40 |
swalladge | atlaspaine: you'll have to look at the wiki guidelines for porting to new devices (unless there's already an unofficial build) | 09:01 |
swalladge | anyone know how to get the acquaris m10 into fastboot mode? | 09:04 |
swalladge | ^ nvm managed to find it - 'reboot to bootloader' does it | 09:16 |
swalladge | how do you use fastboot to flash the ubuntu image for a particular device? ubuntu-device-flash wants the device available via adb interface (which it isn't - only fastboot can see it) | 09:22 |
swalladge | --bootstrap works :) | 09:38 |
mariogrip | ogra_: do you know if there is device specific pulse/alsa settings, if yes where? | 10:49 |
swalladge | can i flash ubuntu-touch from a recovery (like twrp)? asking because i just get 'unauthorized' with adb, and i can't boot into the ubuntu system to authorize it | 11:23 |
ogra_ | mariogrip, i forgot where, but there is surely some default setup shipped in the device tarballs, just pick one from an existing device and dig for pulse | 12:02 |
mariogrip | ogra_: what i found out that i need to set alsa ucm | 12:03 |
ogra_ | right | 12:03 |
mariogrip | ogra_: but do you know if there is a config where i need to enable my new ucm card? or is that automatic | 12:04 |
ogra_ | mariogrip, you need to configure alsa on the android side, pulse then talks to it through the pulseaudio-android module, thats all i know | 12:11 |
mariogrip | ogra_: do you know if there is some docs on how to do that? | 12:16 |
ogra_ | nope ... you have to ask one of the android specialists ... i would just grab an existing tarball and look for all "audio*" or "*alsa*" files in there | 12:17 |
ogra_ | ... and then adjust mine | 12:18 |
mariogrip | maybe morphis can help ^ | 12:18 |
dobey | swalladge: in fastboot you have to use --bootstrap option for u-d-f, and it will wipe all the user data on the device (if ubuntu is already running on it, i mean) | 12:46 |
dobey | swalladge: if your m10 is an android version, you will have to repartition first i think, using the tools from bq | 12:47 |
mariogrip | is it module-jackdbus that does the jack detection on ubuntu touch too? (when headphones plugged example) | 12:53 |
mariogrip | nevermind, it's here it's detects switch, http://bazaar.launchpad.net/~binli/ubuntu/vivid/pulseaudio/support-android-60/view/head:/src/modules/droid/droid-extcon.c | 13:05 |
=== mhall119_ is now known as mhall119 | ||
Asad2005 | My ubuntu 16.04 adb version was 1.0.32 and i have downloaded adb 1.0.36 platform tools as a zip then moved adb and fastboot to /usr/bin/adb to replace old version now the adb version is 1.0.36 would this creat problem in terms of related libraries | 14:43 |
matv1 | side-staged apps are being switched to main-stage after a screen rotation. (leaving an empty side-stage). is this a known bug? or is this perhaps by design? | 14:47 |
matv1 | doesnt reall | 14:47 |
matv1 | -really feel right | 14:47 |
dobey | mariogrip: jackdbus is for detecting when jackd is being used, and stopping pulseaudio to jackd can take over the alsa device. not something that should be on phones/tablets (at least not until we can get rid of android i guess) | 15:06 |
dobey | Asad2005: yes. it means the binaries changed from what were provided in the package. you shouldn't do that. also, #ubuntu is the channel for general ubuntu support. | 15:07 |
mariogrip | dobey: yeah, i see that now. I found out where android does it "switch javk" signal | 15:07 |
mariogrip | jack* / input/output | 15:07 |
Acou_Bass | quick query, is aethercast going to be supported on other devices than the pro 5? if so, is there anywhere i can check progress of this? | 19:13 |
nhaines | Acou_Bass: maybe, and no! | 22:29 |
nhaines | The kernel APIs for aethercast are different between Android 4 and Android 5, so basically the 5 API has be be backported. They're focusing on making it stable and robust on the Android 5 API first before worrying about anything else. Patches welcome, I believe. | 22:30 |
Acou_Bass | ahh | 22:39 |
Keziolio | https://wiki.ubports.com/index.php/OnePlus_One ..? | 22:50 |
ogra_ | Keziolio, https://devices.ubports.com/#/bacon | 22:55 |
Keziolio | yes ogra_ in that page there's a link to the broken page for multirom | 22:55 |
ogra_ | ah, let mariogrip know then | 22:56 |
ogra_ | (i wasnt aware that mutirom still works with *any* device) | 22:57 |
mariogrip | Keziolio: that's the old wiki url, but the Multirom manager that you find from google play should have ubuntu touch support | 22:57 |
Keziolio | uh, I don't have google play | 22:57 |
Keziolio | i'll find an updated mirror | 22:57 |
Keziolio | thanks | 22:58 |
mariogrip | ogra_: only opo has multirom support, but i don't maintain it anymore | 22:58 |
ogra_ | yeah, i know it is a pain | 22:58 |
ogra_ | (which is why i'm surprised there is stll a device) | 22:58 |
mariogrip | yeah | 22:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!