**** BEGIN LOGGING AT Sat Jul 28 02:59:59 2018 Jul 28 05:47:52 Changing tack. Trying to flash a stock ROM to the A1. Maybe then the TWRP instructions will actually work. Jul 28 05:49:25 Windows's Edge has "helpfully" decompressed the tgz on download then 7zip turns out not to understand the tar file. Jul 28 05:50:46 So untarring and recompressing in linux so I can copy a zip file back to Windows so the flash tool can have a folder of files to work with. Jul 28 05:57:28 Good job I don't mind frittering yet another half an hour away! Jul 28 06:06:16 Is there a way to run Android apps inside of LuneOS? I remember there was something for sailfish.. 2 ways.. one worked well and only on jolla devices.. and some other method for porters Jul 28 06:06:58 "To start Android, enter your password"? This is supposed to be a stock ROM. Jul 28 06:24:08 Apparently, if I have set a password or lockscreen pattern, I should "just enter it" to unlock android. Jul 28 06:24:37 But what if I have not? (I have not.) Jul 28 06:25:32 Now I rememeber... https://wiki.merproject.org/wiki/Adaptations/libhybris/sfdroid Jul 28 06:48:51 Morning! Jul 28 06:49:06 Morning! Jul 28 06:49:26 elvispre: for recovery, I'm not using the treble-enabled version, just the simple version. fastboot boot twrp... has always worked for me, whatever the context. Jul 28 06:50:12 Tofe: That simply is not working for me :-( Jul 28 06:50:16 OrokuSaki: we're trying to have Anbox running on LuneOS, but so far no luck, there's always something that gets in the way Jul 28 06:50:53 Interesting stuff.. was just reading about that Jul 28 06:51:01 Morning Dude! Jul 28 06:51:43 elvispre: we're taklink about "recovery-3.2.1-2-oreo.img", right ? Jul 28 06:51:45 Morning! Jul 28 06:52:38 Tofe: I have read about but never seen any recovery-...img. I have been trying twrp-...img Jul 28 06:52:50 elvispre: from here https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472 Jul 28 06:58:17 Tofe: Progress! Thanks. Jul 28 07:10:42 Not much though. Now the only things that work are boot to fastboot or stock recovery. Jul 28 07:11:16 Booting to slot A or B just spins the androidone color bar at me Jul 28 07:12:42 elvispre: it's likely you'll have to reflash the whole android 7.1 image Jul 28 07:12:59 I thought that's what I already did. Jul 28 07:13:07 you're flashing from linux ? Jul 28 07:13:13 From Windows Jul 28 07:13:20 ah, never tried that Jul 28 07:13:27 :-) Jul 28 07:13:44 it requires an additional tool, if I understand correctly Jul 28 07:14:07 ah no, there's a "flash_all.bat" Jul 28 07:14:11 Well it seemed to work. It just ended up wanting to know the password that I did not set. Jul 28 07:14:30 ls Jul 28 07:14:32 oops Jul 28 07:14:41 you're also using tissot_images_7.12.19_7.1 ? Jul 28 07:14:55 it's the one I flashed Jul 28 07:15:13 PS: I didn't put any SIM card yet Jul 28 07:15:26 Now I have done "fastboot -w" which failed a bit and now things are even more broken. Jul 28 07:16:09 elvispre: ok, reflash, and then boot recovery and then install twrp.zip :) Jul 28 07:16:49 NB: I think you can avoid the hassle of reflashing everything Jul 28 07:17:08 One last attempt just now, then I'm going to go and buy a newspaper! Jul 28 07:17:41 tissot_images_7.12.19_7.1 yes Jul 28 07:17:47 you can: "fastboot flash boot_a boot.img", "fastboot flash boot_b boot.img", "fastboot flash userdata userdata.img", that should be enough Jul 28 07:18:38 Trying again with the MiFlash tool (Windows tool), but that stuff may be good to know. Jul 28 07:19:12 I do like the fastboot tool; it's small and efficient Jul 28 07:19:47 I liked it until "fastboot -w" did something weird to my device :-) Jul 28 07:21:47 Again, stuck on the androidone screen :-( Jul 28 07:22:32 meh Jul 28 07:24:29 ah, maybe you need to wipe cache; can you boot recovery and wipe it ? don't reformat data, just to a wipe Jul 28 07:29:23 I did your fastboot flash commands, used TWRP recovery to wipe cache (only) then rebooted, then the screen went black... and finally I have the Welcome screen again. Jul 28 07:29:48 Yay! Good suggestions Tofe :-) Jul 28 07:30:42 :) Jul 28 07:31:15 Good job I'm being all careful and conservative in my approach, eh? Jul 28 07:31:46 well I don't think you'll be able to brick that device so easily Jul 28 07:32:12 as long as you don't erase the bootloader partition, that should be fine :p Jul 28 07:32:34 Don't put it past me! Jul 28 07:38:32 Two and a half hours to break it and fix it again. It was a good learning experience, I suppose. Jul 28 07:40:29 well I did also half-break it the first day :) took a little while to realize it's very sensible to userdata being modified Jul 28 07:40:36 (android one, I mean) Jul 28 07:54:08 Is that the verity functionality? Jul 28 08:03:20 It is a little hard to pin down what is the fundamental difference between, say, recovery-3.1.1-1.img and twrp-3.2.2-0-tissot.img. Jul 28 08:04:48 They are both "TWRP" and they are very similar in size. Given the names, I would expect the 3.2.2 one to work, but only the 3.1.1 one does. Jul 28 08:07:41 I'm not sure, but it could be one of them is dedicated to oreo + treble Jul 28 09:57:08 Hmm. There was something about this might not work "if you haven't updated your firmware". Jul 28 11:36:42 hmm... just found an old external hdd Jul 28 11:36:44 i wonder if i can use this to compile lune os for my tablet Jul 28 11:36:54 how much space do i need? Jul 28 11:53:03 welcome back elvispre Jul 28 11:53:06 saidinesh5: You could get away with ~60 GB. 100 GB is more comfortable. 200 GB can be filled up but is pretty extravagant. Jul 28 11:53:09 Ahh Jul 28 11:53:28 * saidinesh5 checks Jul 28 11:54:52 elvispre|s: btw. how much difference does an SSD vs. HDD do for this? Jul 28 11:55:45 Huge difference. I had an old i5 (which I thought was alright) and HDD set-up and my build time was ~13 hours. Jul 28 11:56:19 I bought an i9 and the fastest SSD I could lay my hands on. Build time now ~ 2 hours. Jul 28 11:56:39 hmm... so I can manage to free up 100GB on this old SSD.. Oooooooooor can have that 200+ GB on an old HDD Jul 28 11:56:42 tough choice Jul 28 11:57:07 100 GB including chromium? Jul 28 11:57:14 or webengine etc.. ? Jul 28 11:57:41 100 GB is plenty. Less than that, you'll have to keep tidying up old builds all the time. Jul 28 11:57:51 the plan is to build myself a desktop PC with probably ryzen 7 or something .. but that seems to take time Jul 28 11:59:36 Lots of CPU cores also help to speed up the build. Just be careful to have an appropriate amount of memory to go with them. Jul 28 12:00:11 16GB ram isn't enough? Jul 28 12:01:39 I had 16 GB of RAM initially but I have 12 hyperthreaded cores so I was running out of memory with 24 simultaneous build jobs. I now have 48 GB RAM. Jul 28 12:02:18 2 GB RAM per core is a rule of thumb, I gather. Jul 28 12:02:23 Ahh Jul 28 12:02:38 wow. this looks like an expensive set up.. Jul 28 12:03:00 RAM prices still crazy Jul 28 12:03:59 Mine was very expensive, but I just turned 50 so it was a present to myself :-) Jul 28 12:04:07 hahah I see Jul 28 12:04:29 okay the PC can wait. nuking the partitions from the SSD Jul 28 12:04:57 Besides, I was fed up sitting about for 13 hours waiting for LuneOS build every other day. Jul 28 12:07:13 btw. Jul 28 12:07:18 what about rebuilds? Jul 28 12:07:32 i mean it is not like i will be building the whole thing always right? Jul 28 12:07:36 probably just the hw adaptation layers Jul 28 12:07:44 and the rest - hopefully leech off your CI caches? Jul 28 12:07:47 sstate or something Jul 28 12:08:15 They're pretty quick so long as you don't need to rebuild chromium / qtwebengine. Jul 28 12:08:43 and disk space requirements for that? Jul 28 12:08:54 Yes. So long as you have enough room to store sstate, rebuilds a pretty quick. Jul 28 12:09:02 That is what the 100 GB is for. Jul 28 12:09:07 oh Jul 28 12:09:10 that's less than i thought Jul 28 12:09:24 for me a sailfish build used to take up like 50-60GB Jul 28 12:09:29 and that's without any webkit whatsoever Jul 28 12:09:53 Sounds fairly similar then. Jul 28 12:11:06 and I can build this on any partition/path right? Jul 28 12:11:11 and on Arch linux? Jul 28 12:11:29 (sailfish needed ubuntu x chroot to build.. and the build scripts needed everything to be on ~) Jul 28 12:12:10 Any partition yes. Arch, I don't know, but I would think it *should* work. Jul 28 12:13:10 You need to be able to install the Yocto pre-requisites which are usually specified as an apt-get example command line. Jul 28 12:13:36 Ahh Jul 28 12:14:47 what's the yocto version? Jul 28 12:15:08 (Arch by default uses python 3 and says Yocto core 2.2+ will work with python3) Jul 28 12:17:21 Yocto pyro at the moment. I think that's 2.3 Jul 28 12:19:04 The OpenEmbedded build system should be able to run on any modern distribution that has the following versions for Git, tar, and Python. : Git 1.8.3.1 or greater tar 1.24 or greater Python 3.4.0 or greater. Jul 28 12:19:51 Yep. I don't predict a problem :-) Jul 28 12:21:27 We've tried using Ubuntu 18 and there were a few snags. Easi Jul 28 12:21:55 Easiest to use something popular so you're not on your own if there is a problem. Jul 28 12:26:27 hmm.. so le ubuntu chroot it is.. Jul 28 12:29:38 (and yeah bitbake fails to install on arch from AUR because of outdated dependencies) Jul 28 12:36:04 @elvispre|scould you point me to the build instructions? Jul 28 12:36:12 need to build an x86 build Jul 28 12:37:40 Follow one of our devices links from here http://webos-ports.org/wiki/Devices Jul 28 12:37:55 There are build instructions on each page. Jul 28 12:39:08 I'm not your x86 build expert, by the way, so you might need to speak to Herrie, for example. Jul 28 12:40:38 Ahh sure Jul 28 12:40:39 btw. Jul 28 12:40:46 is this up to date? curl -sL https://deb.nodesource.com/setup_4.x | sudo bash - Jul 28 12:40:55 4.x was outdated ages ago.. Jul 28 12:41:15 Pretty sure yes it is up to date for us. Jul 28 12:41:37 Ah Jul 28 12:42:43 Node is a pretty fast moving target I think. Jul 28 12:48:17 *very* Jul 28 12:49:13 a lot of the web - js ecosystem seems to be that way.. i started a project with gulp or grunt or whatever their make replacement was.. and it was outdated by the time i finished it in a month or two and had to spend 2 days updating scripts and their dependencies again Jul 28 12:50:27 :-) Jul 28 13:13:31 started the clone of envsetup.. for odd reason i am getting very bad speeds with my internet Jul 28 13:13:38 even speedtest is failing to load.. oh well Jul 28 13:16:03 I would expect envsetup to take ~1 minute, say. Jul 28 14:43:05 saidinesh5: FYI, I'm do builds using an i5 with 16GB of RAM and 200GB SSD. The later is oversize, but I'm also building for different targets, and I'm also building Halium, so in end, it's not that much :) Jul 28 14:43:18 I rarely use more than 6GB during the build though. Jul 28 14:43:47 elvispre: envsetup is still happening. something wrong with my internet today Jul 28 14:44:11 Tofe: out of curiosity, how long does your build take? Jul 28 14:44:39 decided to go with the HDD because the SSD has some of my older sailfish builds i needed to back up.. has a bunch of anbox patches etc.. Jul 28 14:46:23 saidinesh5: from scratch, without having to redownload everything, about 5 hours I'd say Jul 28 14:46:37 qtwebengine is the big piece here Jul 28 14:46:53 about 1h30-2h Jul 28 14:47:19 Ahh Jul 28 16:11:26 internet is back up! Jul 28 16:20:13 $ MACHINE=qemux86 bitbake -k luneos-dev-emulator-appliance Jul 28 16:20:13 ERROR: PRservice jenkins.nas-admin.org:8585 not available Jul 28 16:20:18 any ideas there? Jul 28 16:22:59 Tofe: ^? Jul 28 16:45:07 ah, that's probably pour online sstate which is ... offline Jul 28 16:45:57 saidinesh5: in conf/local.conf, comment out the line Jul 28 16:45:58 PRSERV_HOST = "jenkins.nas-admin.org:8585 Jul 28 16:47:04 and let the builds begin... Jul 28 17:59:18 132 pages in the TWRP recovery for A1 SDA forum thread (https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472/page132) Jul 28 18:01:49 Reading some of them, it is no wonder that I was floundering a bit this morning. Jul 28 18:07:09 s/SDA/XDA Jul 28 18:26:05 :) Jul 28 18:27:12 About 129 pages of wrong / misleading instructions and a handful of useful clarifications :) Jul 28 18:37:07 well, xda... :p Jul 28 18:47:32 Tofe: When you tell TWRP to install a zip, does it install it in the current slot or the other slot? Jul 28 18:47:58 (I haven't got this to succeed yet so it is hard to determine for myself so far.) Jul 28 19:30:43 Seems like the current slot is the one that gets trashed by my failed attempts to install LineageOS-14.1. Jul 28 19:46:45 But that does not explain how I ended up with no OS on either slot! Jul 28 19:47:04 Reflashing stock. Jul 28 20:00:24 Wow! Reflash stock. OK. Boot TWRP recovery. Switch active slot. Boot loop. Boot TWRP recovery. Switch active slot back. Still have a boot loop! Jul 28 20:00:36 Reflashing stock again. Jul 28 20:36:06 elvispre: it's the zip that tells what it wants to flash Jul 28 20:36:19 for instance, luneos installs itself in boot_a only Jul 28 20:36:28 twrp install in both boot_a and boot_b Jul 28 20:37:40 what it does is that it wraps the existing boot image with its own code, to be able to start recovery and normal boot. However, it doesn't seem to work with luneos's boot image, where it just breaks our boot_a image... Jul 28 20:39:37 so what I currently do is: 1. flash stock, 2. install recovery (so both boot_a and boot_b), 3. install luneos (so only boot_a), 4. set boot to B (to be able to go to recovery at reboot time), and 5. start luneos's boot image from fastboot each time. Jul 28 20:40:06 that way I've got a fairly easy way back and forth between recovery and luneos Jul 28 21:53:34 Tofe: OK. So the zip needs to be A/B aware then. I suppose since it is targeted at Mi A1 specifically anyway that is not so surprising. **** ENDING LOGGING AT Sun Jul 29 03:00:00 2018