**** BEGIN LOGGING AT Mon Nov 09 03:02:03 2020 Nov 09 06:43:18 <@_telegram_565620682:hacklab.fi> @NotKit: just tried your latest CI build of UBPorts Nov 09 06:43:20 <@_telegram_565620682:hacklab.fi> stellar work man Nov 09 06:43:26 <@_telegram_565620682:hacklab.fi> keyboard working perfectly Nov 09 06:43:36 <@_telegram_565620682:hacklab.fi> wifi works, getting ready to put my main sim back in for a bit Nov 09 06:43:59 <@_telegram_565620682:hacklab.fi> can you add the binder and ashmem modules to the kernel Nov 09 06:56:14 <@_telegram_101151514:hacklab.fi> > can you add the binder and ashmem modules to the kernel Nov 09 06:56:14 ? they are always in kernel since Android needs them Nov 09 06:56:57 <@_telegram_565620682:hacklab.fi> hmm Nov 09 06:57:20 <@_telegram_565620682:hacklab.fi> i thought those were the two modules anbox needed Nov 09 06:57:33 <@_telegram_565620682:hacklab.fi> im not seeing the device files Nov 09 06:59:18 <@_telegram_565620682:hacklab.fi> is there another dependency for anbox Nov 09 06:59:43 <@_telegram_565620682:hacklab.fi> im wrong i do see the files now, *groan* Nov 09 07:00:00 <@_telegram_565620682:hacklab.fi> not sure what im missing, will need to dig furtherin documentation Nov 09 07:18:59 <@_telegram_101151514:hacklab.fi> UBPorts' Anbox needs /dev/anbox-binder device Nov 09 07:19:04 <@_telegram_101151514:hacklab.fi> will add that Nov 09 07:19:18 <@_telegram_101151514:hacklab.fi> * I will add that Nov 09 07:28:06 <@_telegram_565620682:hacklab.fi> sweet Nov 09 07:28:34 <@_telegram_565620682:hacklab.fi> also just noticed the build from 4 days ago has no sound Nov 09 07:28:51 <@_telegram_565620682:hacklab.fi> but its otherwise running smooth as heck Nov 09 07:29:15 <@_telegram_565620682:hacklab.fi> buttery smooth, working keyboard makes a massive difference in useability Nov 09 07:29:46 <@_telegram_565620682:hacklab.fi> thismight tide me over until the pro1x ships ☺ Nov 09 07:58:55 <@_telegram_21747166:hacklab.fi> > wifi works, getting ready to put my main sim back in for a bit Nov 09 07:58:55 Did you get bluetooth to connect to something? It shows bluetooth devices but no connect. Nov 09 08:00:07 <@_telegram_565620682:hacklab.fi> nope, bluetooth isnt working for me Nov 09 08:00:22 <@_telegram_565620682:hacklab.fi> its on in the ui but no devices detected Nov 09 08:00:33 <@_telegram_565620682:hacklab.fi> so probably not actually on or working Nov 09 08:52:11 <@_telegram_1110327683:hacklab.fi> Delighted to hear that the UBports is going so well. I need to give it a try. Out of curiosity, would a signal private messenger client run on it, or will it be like Sailfish, too old a kernel? (I think I've remembered that rightly as being the problem ...) Nov 09 08:52:11 I take it there are some instructions on oesf that I can follow? Nov 09 08:54:00 <@_telegram_1110327683:hacklab.fi> I guess we've still not had the CoDi-communicating linux update that was promised a month or two ago? Or have I just missed it's arrival? Nov 09 08:58:41 <@_telegram_991509486:hacklab.fi> > Delighted to hear that the UBports is going so well. I need to give it a try. Out of curiosity, would a signal private messenger client run on it, or will it be like Sailfish, too old a kernel? (I think I've remembered that rightly as being the problem ...) Nov 09 08:58:42 > I take it there are some instructions on oesf that I can follow? Nov 09 08:58:42 which signal messenger doesn't run on sfos? you can probably run older version (from around FebApril when NotKit built the kernel last time if you're getting libc errors) Nov 09 08:59:45 <@_telegram_991509486:hacklab.fi> or it should be rebuildable with 3.2.1 target in the SDK to latest version running Nov 09 09:01:46 <@_telegram_991509486:hacklab.fi> then again the kernel rebuild with the few defconfigs needed for 3.4 should get all openrepos app running, so not sure if worth spending time on rebuilding Nov 09 10:29:48 <@_telegram_1110327683:hacklab.fi> Thanks for your reply. I thought the whisper fish in the open repos has been abandoned. (Thinking about it, that was to do with changes in Signal's API rather than the kernel; the kernel issue was the thing preventing running of Android apk's which seemed to be what other SfOS users were doing to access Signal.) Is there another SfOS native Signal client I've missed? Nov 09 10:30:46 <@_telegram_991509486:hacklab.fi> afaik whisperfish 0.5 was abandoned due to rewrite in C Nov 09 10:30:52 <@_telegram_991509486:hacklab.fi> but it should still work Nov 09 10:31:18 <@_telegram_1110327683:hacklab.fi> OK. I'll have a look. Thanks for your help. Nov 09 10:31:46 <@_telegram_991509486:hacklab.fi> 0.6 alpha might need rebuilding under 3.2.1 target as openrepo version will probably require 3.4 (but hopefully with kernel update we might get 3.4 on cosmo soon) Nov 09 10:32:37 <@_telegram_1110327683:hacklab.fi> That would be great. And in the meantime I can still have a look at what is being done with Ubports. Nov 09 10:34:34 <@_telegram_991509486:hacklab.fi> there's 3 defconfigs which should allow 3.4 with flatpak support and maybe BT on sfos, not sure about the Fn key support as couldn't see the file that NotKit changed for gemini in cosmo kernel Nov 09 10:50:07 <@_telegram_701506086:hacklab.fi> > Did you get bluetooth to connect to something? It shows bluetooth devices but no connect. Nov 09 10:50:07 Mine shows the devices are connected (In this case my Pebble watch) but then Rockwork won't let me actually do anything with it.. so wasnt sure if its a rockwork issue or bluetooth one Nov 09 10:53:24 <@_telegram_701506086:hacklab.fi> havent tried any other bluetooth devices yet Nov 09 10:54:51 <@_telegram_792211460:hacklab.fi> > Mine shows the devices are connected (In this case my Pebble watch) but then Rockwork won't let me actually do anything with it.. so wasnt sure if its a rockwork issue or bluetooth one Nov 09 10:54:51 are you talking about Gemian or UBPorts? Nov 09 10:55:20 <@_telegram_701506086:hacklab.fi> UBPorts Nov 09 10:55:40 <@_telegram_792211460:hacklab.fi> grate. so Bluetooth is there finaly Nov 09 10:55:54 <@_telegram_701506086:hacklab.fi> well Nov 09 10:55:59 <@_telegram_701506086:hacklab.fi> looks like others are having issues, so maybe not Nov 09 14:20:37 <@_telegram_565620682:hacklab.fi> @PiecerEdd: what build are you on? Nov 09 14:20:49 <@_telegram_565620682:hacklab.fi> i flashed the lastest available in the CI last night, which i was from 4 days ago iirc Nov 09 14:20:54 <@_telegram_565620682:hacklab.fi> but i have no bluetooth devices showing up Nov 09 14:20:58 <@_telegram_565620682:hacklab.fi> nor do i have sound Nov 09 14:21:18 <@_telegram_565620682:hacklab.fi> im about to boot into android to just make sure it really is just UT Nov 09 14:23:59 <@_telegram_565620682:hacklab.fi> ok, thats at least confirmed Nov 09 14:24:26 <@_telegram_565620682:hacklab.fi> i was starting to worry that somehow whatever internal stress caused my codi screen to again spontaneously crack migh have had a side effect Nov 09 14:25:22 <@_telegram_565620682:hacklab.fi> with the keyboard working properly, the cosmo has been made great again with Ubuntu Touch :-D Nov 09 14:25:34 <@_telegram_565620682:hacklab.fi> only a few small issues seem to remain Nov 09 14:25:40 <@_telegram_565620682:hacklab.fi> camera UX needs to be rotated Nov 09 14:25:46 <@_telegram_565620682:hacklab.fi> bluetooth needs a fix Nov 09 14:26:07 <@_telegram_565620682:hacklab.fi> getting anbox kernel support fully configured will significantly diminish the app gap Nov 09 14:26:50 <@_telegram_565620682:hacklab.fi> and if calls still work as well as they did in the first release (hjaven't tested, no sound) then i could safely say this is more than daily driver material Nov 09 14:27:07 <@_telegram_565620682:hacklab.fi> once sound gets figured out, its daily capable for me now Nov 09 14:27:37 <@_telegram_565620682:hacklab.fi> but id really like to get anbox working so i can stop carrying an android phone for monitoring my kids at daycare and checking them in and out for pickup/dropoff Nov 09 14:27:38 <@TauPan:matrix.org> ("make cosmo great again"... scnr :-D ) Nov 09 14:33:29 <@_telegram_565620682:hacklab.fi> I've seen anbox running on the nexus 5 and its aging CPU handles apps pretty well Nov 09 14:33:45 <@_telegram_565620682:hacklab.fi> they run at midrange spec with good touch response Nov 09 14:33:53 <@_telegram_565620682:hacklab.fi> more than good enough for non gaming type apps Nov 09 14:34:03 <@_telegram_565620682:hacklab.fi> the cosmo significnatly outpaces that device Nov 09 14:34:20 <@_telegram_565620682:hacklab.fi> also, even on the pinephone in arch, anbox is useable, though the camera is inaccessible Nov 09 14:34:57 <@_telegram_565620682:hacklab.fi> i may have lofty expectations, but i think outside of compatibility issues, the cosmo in UT should probably give a near native if not native experience in anbox Nov 09 14:35:36 <@_telegram_565620682:hacklab.fi> @NotKit also fixed the app swiping issue from teh first build, UT feels freaking fantastic on the cosmo now Nov 09 14:36:27 <@_telegram_565620682:hacklab.fi> all i had time to try last night for the sound was alsamixer which doesnt work Nov 09 14:36:45 <@_telegram_565620682:hacklab.fi> not sure if the alsa cli interface can adjust levels, it may be somethign as trivial as that Nov 09 22:44:54 <@_telegram_701506086:hacklab.fi> > @PiecerEdd: what build are you on? Nov 09 22:44:54 im on the one where the commit says: Nov 09 22:44:54 overlay: mount-android.sh: mount tmpfs over /mnt Nov 09 22:53:20 <@_telegram_701506086:hacklab.fi> so what isnt working about sound? just 'everything' or a specific thing? Nov 10 00:18:00 <@_telegram_565620682:hacklab.fi> everything Nov 10 00:18:04 <@_telegram_565620682:hacklab.fi> it doesn't make a peep Nov 10 00:18:27 <@_telegram_565620682:hacklab.fi> no vibration and no audio of any kind when booted into UT Nov 10 00:19:57 <@_telegram_565620682:hacklab.fi> fairly certain im on the same build as you Nov 10 00:20:26 <@_telegram_565620682:hacklab.fi> did you rename the image to ubuntu.img and copy it to the root, then flash boot? Nov 10 00:20:43 <@_telegram_565620682:hacklab.fi> or did you upgrade from an existing installation that had the old android.img Nov 10 00:21:26 <@_telegram_565620682:hacklab.fi> i wonder if im missing something that you have then, my install is completely fresh, i wiped everything, repartitioned and started from complete scratch when i did my install Nov 10 00:40:46 <@_telegram_565620682:hacklab.fi> plugging in headphones and unplugging them result in detection in the UI Nov 10 00:41:17 <@_telegram_565620682:hacklab.fi> and looking at the audio properties with pactl i can see the droid device and the available outputs, speaker is set and unset as active as i plug and unplug Nov 10 00:41:20 <@_telegram_565620682:hacklab.fi> ¯\_(ツ)_/¯ **** ENDING LOGGING AT Tue Nov 10 00:42:46 2020 **** BEGIN LOGGING AT Tue Nov 10 00:50:58 2020 Nov 10 00:54:48 <@_telegram_701506086:hacklab.fi> i nuked system + user files and re-copied the image/re-flashed the boot/removed android img Nov 10 00:55:04 <@_telegram_701506086:hacklab.fi> i had lots of issues until i did those things Nov 10 02:40:49 <@_telegram_1492348329:hacklab.fi> Forwarded from 窦玮焦: Nov 10 02:40:50 > 币圈电报微信群炸群、电报群指定群私聊、Twitter/Facebook点赞加粉等 **** ENDING LOGGING AT Tue Nov 10 02:59:56 2020