**** BEGIN LOGGING AT Wed Jan 31 03:00:03 2018 Jan 31 03:07:26 @vanyasem, Nice working Jan 31 05:05:42 I could try to do a video in my spare time Jan 31 05:05:51 im afraid it would take 4 months for me Jan 31 05:11:06 how about a shitty livestream? Jan 31 05:11:10 I can easily make those Jan 31 05:47:35 @vanyasem, Why does it matter if the folder is called local manifests or just manifests? Jan 31 05:50:11 I think it's largely an organization thing Jan 31 05:52:04 yep.. manifests is core halium projects and local_manifests are local user environment specific manifests Jan 31 05:58:22 @Ellenjott, just manifests weren't read for me yesterday Jan 31 05:58:32 I had to move it to local manifests for it to work Jan 31 05:58:43 plz don't change things without good reason Jan 31 06:03:03 @vanyasem, Why needed you to move something to a local_manifests folder in halium-devices? Jan 31 06:04:39 @vanyasem, I didnt changed the folder name? It only in .repo local_manifests and in halium devices there is only one type of manifests, so I called the folder just manifests Jan 31 06:06:01 @Ellenjott, please revert the change you've made with folder names there Jan 31 06:06:14 I don't have time to explain that, but it's wrong Jan 31 06:06:22 I could.do that myself, but please Jan 31 06:07:10 I didnt changed the folder from local_manifests to manifests. Before it was a totally different and more complicated file structure Jan 31 06:10:09 @vanyasem, I see absolutely no problem with the current way, if you want that I change this, you'll have to explain it to me. I wont do things which I dont see a necessary for. Jan 31 06:10:40 @Ellenjott, you have to put your manifest under local manifests or otherwise repo ignores it Jan 31 06:10:51 tested that myself 2 times yesterday Jan 31 06:11:02 please don't change things without good reason or proper testing Jan 31 06:11:27 But the manifests WILL be linked to local_manifests! Jan 31 06:11:53 Don't fix if it ain't broken Jan 31 06:11:56 🙃 Jan 31 06:12:05 halium-devices != repo Jan 31 06:12:42 @Ellenjott, no, they weren't Jan 31 06:12:57 It works absolutely well for me and jbb and everybody else who tested it so (e.g. jonnius) Jan 31 06:13:35 @vanyasem, Then have a look at the setup script, please. Its all written there Jan 31 06:16:40 @vanyasem that change works for me as well, can you recheck what's wrong on your end please? Jan 31 06:17:48 @bhushanshah, sure I will. a bit later Jan 31 06:22:45 Did you even run the setup script? Jan 31 06:46:46 @NotKit, after … repo init -u https://github.com/Halium/android -b halium-5.1 … I run 'repo sync' instead of "repo sync -c". => 8.9GB downloaded. Is it ok? Jan 31 07:18:07 @vanyasem, yep my mistake Jan 31 07:18:27 I forgot to run the script after syncing due to docs issue yesterday Jan 31 07:18:28 sorry Jan 31 07:35:35 @JBBgameich , so, it is necessary to run … ../halium/halium/devices/setup … before "Adding your device-specific source" … ? Jan 31 08:16:47 ? Jan 31 08:43:07 @Progromizd, after Jan 31 08:59:41 @Progromizd, First add your manifest to halium/devices/manifests/ and then run ./halium/devices/setup DEVICENAME Jan 31 09:03:32 leinir was added by: leinir Jan 31 09:03:58 Welcome! ;) Jan 31 09:04:11 Hi Jan 31 09:05:24 i'm /sure/ i was in here at some point in the past... but hi! :) Jan 31 09:06:04 Just gonna blame telegram being a strange system ;) Jan 31 09:27:38 https://github.com/Halium/lxc-android/blob/master/usr/lib/lxc-android/mount-android - can you think of any way of adding exception like " ([ "$2" = "/system" ] || [ "$2" = "/data" ]) && continue" without editing the script? Jan 31 09:28:06 I don't understand? Jan 31 09:28:12 What you want to achieve? Jan 31 09:28:43 I have /nvram and /nvcfg partitions, which need to be mounted by mount_all in container, otherwise NVRAM daemon refuses to initialize Jan 31 09:30:56 I had something like that in bullhead.. not sure what was that but it was quite easy to workaround in android side Jan 31 09:31:15 do you have exact error message? Jan 31 09:32:58 no errors about that, but service.nvram_init property stays Pre-Ready Jan 31 09:33:15 and lots of other service are waiting for it to become Ready Jan 31 09:33:42 that nvram daemon that sets the property is closed blob, so no idea what kind of event does it wait exactly for Jan 31 09:34:23 I'll check irc logs of this channel... I had exactly similar issue with other services.. Jan 31 10:04:48 @NotKit … is this line correct in my case: … … ? Jan 31 10:05:03 no Jan 31 10:05:12 it's kernel, not device tree Jan 31 10:07:56 I guess Jan 31 10:11:15 thanks, for device tree: … … correct? Jan 31 10:13:25 no, you need LOS14.1 device tree Jan 31 10:13:31 his device tree is for MTK AOSP Jan 31 10:26:16 @NotKit , maybe this one? … … from: … https://github.com/SeriniTY320/android_device_doogee_x5pro Jan 31 10:27:22 you can try Jan 31 10:27:49 no idea if it works or not though, last commit is 4 months ago Jan 31 10:35:07 @NotKit on github there are only 2 result matching that criteria: … https://github.com/search?utf8=%E2%9C%93&q=doogee_x5pro++LOS14.1&type=Repositories … - device tree and vendor tree Jan 31 10:35:55 i'll try Jan 31 10:35:59 https://vk.com/smart_rom - I guess you can ask them if that device tree is working Jan 31 10:36:32 I don't see their builds for it, so I guess it might be not Jan 31 10:36:42 you linked another LOS14.1 device tree yesterday Jan 31 10:37:06 https://github.com/nE0sIghT/android_device_doogee_x5pro/ Jan 31 10:44:13 @NotKit , yes this one looks better. My xml conf currently contains 2 items: … … … Perhaps, I need a vendor tree and something for dependencies (comparing with other configs), right? Jan 31 10:44:37 vendor tree and maybe somethine else, right Jan 31 13:02:34 @NotKit how to resolve … "The given device is not supported. :(" while executing: … ./halium/devices/setup doogee … ? Jan 31 13:03:57 You need to have a manifest in halium/devices/manifests/$vendor_$codename.xml Jan 31 13:07:50 I guess argument should be doogee x5pro? Jan 31 13:10:08 or doogee_x5pro, not sure Jan 31 13:31:00 @NotKit , yes, you right. Now: … fatal: remote github not defined in /media/user/D500/halium/.repo/manifest.xml Jan 31 13:39:53 yeah, you should use the los or hal remote in Halium 7.1 Jan 31 13:40:15 los for cm-14.1 branches and hal for halium-7.1 branches Jan 31 13:47:17 @Ellenjott, Wow, it actually was a problem with the docs! Time to go screw up on something else. Jan 31 13:53:32 @sudanisayfree, Fat books of docs make the world go 'round. Jan 31 14:00:48 @sudanisayfree, Why don't you use Google translate for translation to Arabic? 🤔 Jan 31 14:03:51 @JBBgameich let's clarify. If my "device.xml" contains 3 items(for kernel, device and vendor), than .repo/manifest.xml must contain 3 items too, MATCHING repo names, yes? Jan 31 14:05:57 @NotKit, Where is that script? (Mount_all)? Jan 31 14:06:12 @shenoy13, Because it's largely trash. Jan 31 14:06:46 It's no secret. Jan 31 14:07:02 @zoomer296, But it does the job what it is supposed to Jan 31 14:07:18 Don't know how good does it translate to arabi Jan 31 14:07:43 But other languages like Chinese, Japanese, it's very good. Jan 31 14:09:45 @Progromizd, .repo/manifest.xml contains the Halium base. Your three device specific repositories need to be downloaded additionally. The additional repositories per device are stored in manifests in halium/devices/manifests. They need to be called vendor_device.xml (for example sony_yuga.xml). To set up the tree for a specific device, run ./halium/devices/setup $device Jan 31 14:14:08 @shenoy13, Even in those languages, it'd probably fail miserably at this. … Google Translate is not suitable for documentation. Jan 31 14:18:24 (Photo, 1207x730) https://irc.ubports.com/UPFyjbi5/file_3961.jpg Jan 31 14:19:16 @JBBgameich if i left .repo/manifest.xml in its default state I've got this Jan 31 14:20:02 There is still some other manifest which wants to use a remote "github" I guess Jan 31 14:20:41 github is mentioned 3 times in my dooge_x5pro.xml Jan 31 14:20:55 Change it to "los" or "hal" Jan 31 14:21:26 or add your own `` Jan 31 14:22:31 (Photo, 1187x664) https://irc.ubports.com/1jJTLCkM/file_3963.jpg Jan 31 14:22:52 @JBBgameich tried, but process was stuck on it Jan 31 14:22:58 do what it wants? Jan 31 14:23:07 Just read the console output Jan 31 14:23:28 You are using an outdated repo version it seems Jan 31 14:36:48 @Progromizd, censor Jan 31 14:36:54 @Progromizd, no censor Jan 31 14:36:57 wtf? xD Jan 31 15:39:38 Anyone happens to know what's the equivalent of the firmware partition on OnePlus devices? Jan 31 15:41:44 @Herrie, You can take a look on internet, on android running adb shell mount or watching fixupmountpoint Jan 31 16:56:12 Mattia990: well I have the layout, just don't know which name they might use ;) Jan 31 17:07:18 @Mattia990, in init.${soc}.rc Jan 31 17:07:22 inside Android ramdisk Jan 31 17:47:27 @NotKit repo status returns … nothing to commit (working directory clean) … but … ./halium/devices/setup x5pro … -> error: Cannot remove project "halium/devices": uncommitted changes are present … commit changes, then run sync again … how to solve it? Jan 31 18:19:42 @NotKit, Thanks! Jan 31 21:37:01 adomas was added by: adomas Jan 31 22:34:10 I've just updated https://github.com/Halium/projectmanagement/issues/40 Jan 31 22:34:50 It now includes a new debian-based initrd rather than the Ubuntu-based one. Compatible with both Halium (with the listed changes) and Ubuntu Touch. Jan 31 22:35:33 I should try booting 16.04 on shamu again Jan 31 22:43:54 @JBBgameich just tested your script with UT param Jan 31 22:44:01 it failed to create appropriate symlinks Jan 31 22:44:52 It doesn't link rootfs.img to ubuntu.img, no Jan 31 22:45:02 Er... wait. ubports-boot. It's system.img Jan 31 22:45:13 manual linking didn't help Jan 31 22:45:18 still initrd debug Jan 31 22:45:22 Can you mount the image? Jan 31 22:45:37 oh it failed to mount /data Jan 31 22:45:49 nope, nvm Jan 31 22:49:32 okay so it booted Jan 31 22:49:35 and it doesn't bootloop Jan 31 22:49:40 and i can see it's interface Jan 31 22:49:48 but i can't ssh and i blame jbbs script for that Jan 31 22:49:51 will investigate that Jan 31 22:50:09 Set your interface IP Jan 31 22:50:16 And ssh to phablet@ Jan 31 22:50:32 Also it might decide to reboot on the first boot Jan 31 22:51:09 @UniversalSuperBox, i know how to do that dalton :P Jan 31 22:51:18 it just hangs on "connecting using ssh" Jan 31 22:51:42 seems like sed magic was not done by jbb's correctly Jan 31 22:51:50 ssh seems disabled Jan 31 22:51:59 i don't use rootstock but i really should Jan 31 22:54:28 I get a lot of stuff like "systemd-udevd[1207]: specified group 'log' unknown" now. Do I need to fix up the device specific udev rules? Jan 31 22:57:11 or should I create the groups instead? Jan 31 22:57:31 Sounds like udev is wrong, but I'm not an expert on that subject Jan 31 23:00:06 Yes, the messages probably come from the rules generated for the device. It has groups in there like "adb", "graphics", etc which do not exist on the reference rootfs Jan 31 23:01:05 Now the question is, do I change the group to match the system groups or do I create the groups, or should I just ignore them Jan 31 23:03:30 also, the lxc container seams to reboot my phone :-) Jan 31 23:06:35 And I have a really strange systemd problem, as in if the system.img is there, then it gets stuck during boot and the ssh server never starts. If I rename it, then system.mount fails and the ssh starts. Jan 31 23:06:57 Probably something after system.mount, then Jan 31 23:08:14 yes, now that it boots I will probably be able to finally get a dependency graph, something which seams to be impossible with systemd from a chroot Jan 31 23:09:25 i am in sir @UniversalSuperBox Jan 31 23:09:30 yeye Jan 31 23:09:52 ssh freezes Jan 31 23:09:56 oh Jan 31 23:10:00 phone totally freezes Jan 31 23:10:11 nm being helpful Jan 31 23:10:21 it does not bootloop, but it seems to crash after 30 seconds Jan 31 23:10:30 No Jan 31 23:10:31 @UniversalSuperBox, i disabled that Jan 31 23:10:38 hm Jan 31 23:10:39 i can't reconnect Jan 31 23:10:56 so it's the phone that got frozen Jan 31 23:11:12 ssh was enabled though, i inspected the entire configuration Jan 31 23:11:42 so @JBBgameich you script works fine except for the part with symlinks. it just pushes rootfs.img and doesn't rename/link it Jan 31 23:12:02 Which should be remedied if halium-boot is accepted Jan 31 23:12:10 Then he can remove the "stuffing system.img" too Jan 31 23:12:19 yeah Jan 31 23:12:37 how do i deal with my phone freezing now? Jan 31 23:12:52 disable LXC? Jan 31 23:12:58 the ususal break-through route? Jan 31 23:13:26 I suppose Jan 31 23:13:45 dam Jan 31 23:14:39 and so it doesn't use systemd. Jan 31 23:14:40 rught? Jan 31 23:14:57 Right Jan 31 23:15:03 how do i disable services with upstart? Jan 31 23:15:08 So create lxc-android-config.override with the content `manual` Jan 31 23:15:09 which one should i set to manual? Jan 31 23:15:24 `lxc-android-config`, right. thanks Jan 31 23:16:55 mope.. Jan 31 23:17:11 something is still stale Jan 31 23:17:15 which is weird Jan 31 23:17:26 either the override is not working or something else is the issue Jan 31 23:17:38 Hmm. Seriously, does your network icon show the "Connecting" symbol? Jan 31 23:17:45 no Jan 31 23:17:50 i disabled network manager Jan 31 23:17:58 i am on arch, i can do whatever i want Jan 31 23:18:00 Anything fun in `dmesg` on host? Jan 31 23:18:20 nope Jan 31 23:18:42 it just worked with plasma. but it's freezing with ubports after i enter my password Jan 31 23:18:53 i get prompted for phabled password, i enter it and ssh hangs Jan 31 23:19:00 Hmm Jan 31 23:19:05 I gotta find a way to free up my 5X Jan 31 23:19:06 if i kill it, it doesn't respong to connection requests after that Jan 31 23:19:28 Are system-data and user-data created? Jan 31 23:19:35 You can see the fancy logs in there Jan 31 23:19:54 @UniversalSuperBox, jep Jan 31 23:20:06 Logs are in system-data/var/log Jan 31 23:20:12 syslog and the ssh log will be interesting Jan 31 23:21:13 ```lxc-wait: monitor.c: lxc_monitor_open: 237 Failed to connect to monitor socket. Retrying in 100 ms: Connection refused … lxc-start: tools/lxc_start.c: main: 366 The container failed to start``` Jan 31 23:21:18 lxc log Jan 31 23:21:41 can't find ssh logs Jan 31 23:21:51 Should be in the upstart folder Jan 31 23:22:07 @UniversalSuperBox, https://paste.ubuntu.com/26497767/ Jan 31 23:22:19 Anything fun in syslog? Jan 31 23:23:09 don't have that. only `lastlog` and `faillog`. both empty Jan 31 23:23:27 flashbacks Jan 31 23:23:39 I feel like I've been here before Jan 31 23:23:53 Over a year ago at this point, sheesh. Jan 31 23:24:11 Never actually fixed it... Jan 31 23:24:22 Well. With your kernel config changes, can you still boot PM? Jan 31 23:24:34 can't test that Jan 31 23:24:59 bhushan has local changes to kernel/device trees that are mandatory for new plasma builds to boot Jan 31 23:25:03 and i don't have them Jan 31 23:25:04 Oh dear. Jan 31 23:25:19 he told me that this should not affect ubports. camera/audio fixes Jan 31 23:25:24 I don't have a solution for you right now. But I do have dinner waiting. be right back Jan 31 23:26:06 enjoy your meal Feb 01 00:00:11 @UniversalSuperBox i assume there's something wrong with the image Feb 01 00:00:23 i have just installed it on HTC 10 and it's having the same issue Feb 01 00:00:28 oh wait it bootlooped Feb 01 00:03:02 okay so i installed ubports to htc 10 and it bootloops @UniversalSuperBox Feb 01 00:03:59 ```$ service lxc-android-config status … lxc-android-config stop/post-start, (post-start) process 1057``` Feb 01 00:04:17 That means the container is running Feb 01 00:04:30 that's due to ofono i assume Feb 01 00:04:38 will remove that now :P Feb 01 00:05:08 see, HTC 10 works. 5x doesn't. not an issue with NM on my machine Feb 01 00:05:27 there's something more compicated with the 5x Feb 01 00:31:50 @vanyasem, ```Broadcast message from root@ubuntu-phablet … (unknown) at 14:26 ... … The system is going down for reboot NOW!``` Feb 01 00:32:07 the container refuses to start now Feb 01 00:32:38 i wonder why Feb 01 00:35:03 (Photo, 872x118) https://irc.ubports.com/X9SCsxh4/file_3965.jpg observation: it starts, but then crashes (fails) Feb 01 00:35:25 i also get this in df `/dev/loop0 1965760 1930924 0 100% /` Feb 01 00:35:26 If lightdm failes to start 5 times, the system reboots Feb 01 00:35:34 Wait... how is that possible Feb 01 00:35:55 loop0 is read only darn it! Feb 01 00:36:08 what is loop0 anyways Feb 01 00:36:43 It should be ubuntu.img Feb 01 00:36:52 loop1 is Android system.img Feb 01 00:37:03 i have just resized it Feb 01 00:37:04 I'm broken Feb 01 00:37:31 @vanyasem, or is it Feb 01 00:37:33 ehh Feb 01 00:39:29 @UniversalSuperBox, you were right. don't listen to me,i'm stupid Feb 01 00:39:40 It still shouldn't be full Feb 01 00:39:43 resized it Feb 01 00:39:47 nothing changed Feb 01 00:39:58 ideas? Feb 01 01:24:35 Here's the proposal for halium-boot: https://github.com/Halium/projectmanagement/issues/55 Feb 01 01:30:13 last time I've tried ut 16.04 on HTC 10 I got the boot logo Feb 01 01:30:26 I cant remember how I got past bootloops Feb 01 01:30:43 the only thing I remember is that Marius helped me with that Feb 01 01:30:54 documentation cringe Feb 01 01:31:07 I left sidenotes on a projectmanagement issue Feb 01 01:31:12 they don't seem to work Feb 01 01:31:29 has something changed significantly? Feb 01 01:31:42 There are always changes Feb 01 01:31:49 But nothing significant to my knowledge Feb 01 01:32:00 At least not in the boot process Feb 01 01:33:14 I commented out stuff in the out directory Feb 01 01:33:19 as we used to back in the day Feb 01 01:33:30 and not in the init.rc by itself Feb 01 01:33:35 is that an issue? Feb 01 01:33:57 No, as long as you rebuilt and reflashed Feb 01 01:35:24 done that, still bootlooped Feb 01 01:36:49 I assume I missed something important Feb 01 01:37:21 I should maybe try old rootfs tarball Feb 01 01:37:36 eh its 4am Feb 01 01:41:26 when I tried 16.04 on the nexus 6 the unity 8 compositor just kept crashing Feb 01 02:21:32 @vanyasem you still have udev? Feb 01 02:21:37 make that ssh Feb 01 02:21:52 i'm in Feb 01 02:22:24 btw the issue was that jbb's script only allocates 2 gigs of memory to rootfs.img and that was not enough for ubports @JBBgameich Feb 01 02:22:31 that's why it was 100% Feb 01 02:22:49 @UniversalSuperBox, ? Feb 01 02:22:58 that'll be fixed by halium-boot Feb 01 02:23:08 Anyway, you've ssh Feb 01 02:23:18 @vanyasem, oop I ran into that wth the n6 as well, that was annoying Feb 01 02:23:31 So let's see the log in `~/.cache/upstart/unity-system-compositor` Feb 01 02:24:00 i don't have a ~/.cache folder Feb 01 02:24:07 oops wrong user Feb 01 02:24:16 whot Feb 01 02:24:25 i was logged in as root Feb 01 02:24:29 oh Feb 01 02:24:34 @UniversalSuperBox, i don't have that file anyways Feb 01 02:24:52 https://paste.ubuntu.com/26498405/ Feb 01 02:25:28 unity8.log? Feb 01 02:25:41 @UniversalSuperBox, https://paste.ubuntu.com/26498409/ Feb 01 02:25:46 Oh right. The system compositor and lightdm logs are in /var/log/upstart Feb 01 02:26:05 ls /android Feb 01 02:26:13 @UniversalSuperBox, `boot cache carrier data dsp firmware misc none persist persistent recovery system` Feb 01 02:26:32 Okay this is officially weird Feb 01 02:26:41 @UniversalSuperBox, https://paste.ubuntu.com/26498412/ Feb 01 02:26:43 `sudo stop apport` so it shuts up Feb 01 02:27:00 @UniversalSuperBox, stopped apport Feb 01 02:27:26 nothing happened Feb 01 02:27:49 That's okay Feb 01 02:28:19 Let's see Feb 01 02:29:01 Can you run `unity-system-compositor` Feb 01 02:29:07 And then check logcat when it crashes Feb 01 02:30:16 no i can't Feb 01 02:30:21 but Feb 01 02:30:23 the rootfs is 32 bit Feb 01 02:30:30 and my phone is aarch64 Feb 01 02:30:32 logcat won't run Feb 01 02:30:43 we've discussed that back in the day with Marius Feb 01 02:30:48 Is there anything in /android/firmware? Feb 01 02:30:49 he told that it's ok Feb 01 02:31:00 @UniversalSuperBox, `adsp radio slpi venus` Feb 01 02:31:03 stuff that has to be there Feb 01 02:31:12 as per fstab Feb 01 02:31:27 well Feb 01 02:32:50 @vanyasem, https://github.com/JBBgameich/halium-install/issues/15 Feb 01 02:33:06 @UniversalSuperBox, i mean what could get wrong? everything seems fine Feb 01 02:33:38 Well there's probably a clue in adreno's log Feb 01 02:33:40 But we can't get it Feb 01 02:34:11 sad. so should i leave it for now? Feb 01 02:34:37 sure. :/ Feb 01 02:43:21 why is date set to 1971 @UniversalSuperBox Feb 01 02:43:31 is it even ok Feb 01 02:43:42 Wait, really? Feb 01 02:43:46 yes Feb 01 02:44:00 (Photo, 800x88) https://irc.ubports.com/VeUvwq0r/file_3967.jpg Feb 01 02:44:02 Android RTC's store the time as seconds since they were powered up Feb 01 02:44:16 And then the OS stores the offset between the RTC and now Feb 01 02:44:32 can that be an issue? Feb 01 02:44:35 no Feb 01 02:44:36 do i need to change my date? Feb 01 02:44:37 ok Feb 01 02:44:38 ty Feb 01 02:44:39 no Feb 01 02:45:23 by the way new rootfs seems to be broken Feb 01 02:45:33 i got the unity logo with the old one Feb 01 02:45:39 that was working for me before Feb 01 02:46:21 No... Feb 01 02:46:26 what? Feb 01 02:46:37 these are my results, that's what i got Feb 01 02:46:44 i flashed each image ~4 times Feb 01 02:46:53 Something working worse than it did before on a broken port doesn't really mean the image is at fault Feb 01 02:53:14 oh i know de wei now Feb 01 02:53:17 it booted Feb 01 02:53:30 i am shaking Feb 01 02:53:38 (Photo, 960x1280) https://irc.ubports.com/kg90sQCv/file_3969.jpg Feb 01 02:55:01 Nice! Feb 01 02:55:30 (Photo, 960x1280) https://irc.ubports.com/nXbYhA7m/file_3971.jpg Feb 01 02:55:37 whats wrong with scopes Feb 01 02:55:50 uh I think it's in windowed mode Feb 01 02:56:11 It tried to guess it it's on a phone Feb 01 02:56:13 should have a toggle for it somewhere Feb 01 02:56:15 And guessed wrong Feb 01 02:56:51 That's actually something that Rodney might know tbh... Feb 01 02:56:54 @UniversalSuperBox, 2k displays ftw lol **** ENDING LOGGING AT Thu Feb 01 03:00:03 2018