**** BEGIN LOGGING AT Mon May 21 03:00:04 2018 May 21 06:43:25 Morning! May 21 07:36:18 Morning! May 21 07:37:39 morning May 21 07:58:35 Herrie: do you see something in /var/lib/anbox/data/tombstones ? May 21 08:37:11 Tofe: Will have a look later May 21 08:37:31 On my way out with kids in a minute May 21 08:38:07 I built another image with some additional defconfig changes May 21 08:38:25 Will charge mido and test that and report back May 21 19:02:59 Tofe: I'm getting a "[ 2018-05-14 20:08:46] [launch.cpp:220@operator()] Android hasn't fully booted yet. Waiting a bit .." on my latest mido image May 21 19:28:06 Tofe: (Or Herrie) Where does anbox fit on your architecture diagram? Inside the Halium box, I suppose. But if anbox is for running Android apps, that seems less likely. May 21 19:41:55 elvispre: It's a separate LXC container basically May 21 19:42:08 With a different Android instance v.s. Halium May 21 19:44:55 Herrie: So we have / we're going to have two Android instances? Why? (Just curious, you understand.) May 21 19:46:20 that's kind of right elvispre May 21 19:49:44 Well Halium = minimal Android basically just to access hardware May 21 19:49:53 Other one is full Android via emulator in lxc May 21 19:52:54 elvispre: I.e. Halium can be 5.1 based Android but Anbox 7.1 or 8 for example May 21 19:54:22 Herrie|TP: OK. But what do we need full Android for? Loads and loads of apps for free? May 21 19:58:13 elvispre: Yup May 21 19:58:32 :) May 21 19:59:09 Anything that runs on Android app wise could theoretically also run on LuneOS and other distro's. Similar to OpenMobile on TP and AlienDalvik etc May 21 19:59:20 Just for free instead :-) May 21 20:42:49 But it's true it's a bit of a stress from a RAM point of view: there's LuneOS, Halium and now Anbox May 21 20:51:35 I thought this must have something to do with the rebase onto webOS OSE, but I guess not. May 21 20:55:06 ah no, it's totally uncoupled May 21 20:55:12 unrelated I mean :) **** ENDING LOGGING AT Tue May 22 03:00:04 2018