**** BEGIN LOGGING AT Sun May 05 03:00:37 2019 May 05 05:26:05 Binance TestNet Bot was added by: Binance TestNet Bot May 05 06:03:00 This should be close to the ubuntu based reference rootfs, but is also available for arm64: https://archive.kaidan.im/debian-pm/images/halium/minimal/ May 05 09:57:40 how is CAF handled in it? May 05 10:00:35 Fully in a hook of the halium install script, which saves me a lot of build time and space on the server. May 05 10:02:18 You basically use the generic rootfs with halium-install -p debian-pm-caf, and it will then enable the additional repository component and install the caf packages. The ci appends caf1 to the version numbers of the caf packages so they are always newer and replace the generic ones. May 05 10:09:24 that's pretty nice solution **** BEGIN LOGGING AT Sun May 05 11:42:03 2019 May 05 13:40:41 where do I put the udev rules file on the ubporta? May 05 14:06:23 @JBBgameich [This should be close to the ubuntu based reference rootfs, but is also available …], Thanks, I'll look at it once I give up on Hal 16.0 for the day May 05 14:07:52 you generate the udev rules using a command line string which is in the docs but they are not reliable. I've been reading an entire 80 page book on udev rules cause I don't know anything about them which as a UT porting guy is very bad May 05 14:08:53 You need to use the command to have your device boot but you can't trust the rules to all be right, after like 2 years someone fixed camera on Nexus 5 with a simple udev rule change May 05 14:13:57 @NotKit [that's pretty nice solution], Do you know what you're doing with udev rules? They seem simple but in reality pack a lot of complexity hence me buying the book on udev May 05 14:14:28 You seem like me, skilled in theory but no clue what you're actually doing May 05 14:15:18 what we need udev rules for basically is to set proper permissions on /dev nodes May 05 14:16:10 Yeah, but I meant as far as making and modding them, I am 25 pages into the ebook I got on udev out of 80.. then I should know how to use them properly and effectively May 05 14:17:43 I think Nexus 5 bug was from the fact UBPorts accesses v4l nodes as phablet user and some services are not run, so it was not in original ueventd rules in Android May 05 14:18:39 I have know udev bugs in my s7 s7+ and A7 tab that I need to fix but don't know how yet May 05 14:19:04 Like the rule generation isn't perfect under Hal 7.1 or possibly just in general May 05 15:37:12 well, it just converts Android ueventd rules, which is generally enough, but you may want to adjust that if you see permission denied in strace and that device is supposed to be accessible by the process May 05 16:14:20 Yeah, I see those permission denied errors which is how I know that the rules are bugged but I haven't read enough of the book to write the proper rules to replace them May 05 16:15:19 Also, any idea why LTE would work but not 3G or lower spec modem protocol? I have LTE but when I'm in bad service area instead of 3g I get no connection May 05 17:10:46 That could be APN, I had to futz with that to get my CDMA network to sorta work May 05 21:38:06 hello. May 05 21:38:21 ı use http://docs.halium.org/en/latest/porting/debug-build/logging-in.html May 05 21:38:30 but not open ssh May 05 21:38:58 what else can I do? May 05 21:56:23 @ankaos did you use the version of halium-install from JBB? It enabled ssh and lightdm/Mir when pushing.rootfs and system img to the device May 05 21:57:17 If you used the wrong halium-install version it won't set user credentials or enable mir and ssh which may be your problem May 05 21:58:31 ı use ubports. ubports xenial versiyon install. halium-7.1 use my code May 05 21:59:36 how do I find out about the Halium-install version? May 05 21:59:45 You can boot into TWRP, and use it to mount the rootfs with hslium-chroot and then enable the stuff manually, but the branch/repo I use has ability to.configure the images May 05 21:59:45 @powderedtoastman9000 May 05 22:00:03 @ankaos let me find it for you May 05 22:00:20 okey. May 05 22:02:02 @ankaos [okey.], https://github.com/JBBgameich/halium-install/ branch master May 05 22:02:37 That one is the only one that does.everything set post-flash to be useful May 05 22:06:03 okey. now test May 05 22:08:36 You need to reflash the device using halium-install from halium-scripts which I posted. It's the only fork or branch that works properly without needing to modify the ROM after flashing May 05 22:32:42 @powderedtoastman9000 [You need to reflash the device using halium-install from halium-scripts which I …], not open. May 05 22:34:56 What do you mean not open? May 05 22:38:56 ı use `ssh phablet@10.15.19.82` May 05 22:39:03 but not open ssh May 05 22:39:25 `https://docs.ubports.com/en/latest/porting/common-problems-install.html#ssh-hangs-when-trying-to-connect` use? May 05 22:39:44 Did you apply the hack in the porting docs to create then configure a virtual network adapter? May 05 22:40:04 no May 05 22:40:27 Try both those options and let us know how it works May 05 22:45:24 https://docs.ubports.com/en/latest/porting/common-problems-install.html#ssh-hangs-when-trying-to-connect not work May 05 22:48:22 @ankaos boot into TWRP, and use halium-scripts/halium-chroot to enter the device with root shell and enable sshd and lightdm, then try rebooting May 05 22:54:33 please code send me? May 05 22:55:57 in recovery. chroot ubports. start lightdm. it read me `start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused` May 05 22:56:53 It's a git repo from GitHub halium and you can use it when device is installed system and rootfs imgs to enter chroot based shell on the device May 05 22:57:21 You may need to do some debugging in lightdm May 05 22:57:50 Lucky, I never get to write any original code I just apply patches and follow docs May 05 22:58:11 I have only put 40 lines of code into my kernel in 5 weeks May 05 22:58:12 ı use docs. May 05 22:59:48 but not open ssh. May 05 22:59:52 interesting May 05 23:21:33 You should use TWRP to read your logs and look for bugs that may have error messaged suggestions to how to fix it and where the error is and what type of error May 05 23:22:15 Stupid question: … Am I "required" to get a source from LineageOS Github repository list? May 05 23:23:04 ? May 05 23:24:22 https://pastebin.com/10J4cFUY May 05 23:24:53 No, you can get it from anywhere but linesgeos official kernels are very good quality and will be more likely to work with less trouble or time May 05 23:25:21 The linesgeos official git repos are the best ones if you care about trusted sources May 05 23:25:55 I guess it's the [breakfast [codename]] command that i'm having trouble with. I think it's can't see Dashes(-) May 05 23:26:21 (Relevant link: http://docs.halium.org/en/latest/porting/build-sources.html#for-halium-7-1) May 05 23:28:33 Summary: I wrote a manifest similar to existing Motorola manifests for the Moto-C-Plus (Panelli). It wasn't a clean sync, but no errors after "—force-sync" was used. Now, next step is breakfast. May 05 23:28:51 (Which reminds me, I haven't made yet.) May 05 23:31:58 can someone give me a sample for that "breakfast [codename]" thing … I write "moto_c-plus" since it's the name of the repo, and it ignores the "plus" May 05 23:32:06 [Edit] can someone give me a sample for that "breakfast [codename]" thing … I write "moto_c-plus" since it's the name of the repo, and it ignores the "plus" May 05 23:32:11 breakfast herolte May 05 23:32:19 Breakfast hammerhead May 05 23:32:20 [Edit] can someone give me a sample for that "breakfast [codename]" thing? … I write "moto_c-plus" since it's the name of the repo, and it ignores the "plus" May 05 23:32:56 I should try making it again with one word, I guess... … Thank you May 05 23:33:16 Is your manifest named differently? May 06 00:20:16 I'm sad I got through all this, I can't get it made because there's a dash in my phone's name TTwTT May 06 00:20:41 I found a vendorsetup.sh thing, and still nothing May 06 00:21:13 What is the name for your manifest? May 06 00:21:30 Or device rather May 06 00:22:58 It'a a Motorola C-Plus "Panelli". (Or at least this is the closes with the screen size, chipset, Android version, RAM, and features) May 06 00:23:58 Hmm so whats the actual error? May 06 00:24:16 I tried many other names, but my manifest is currently named moto_cplus. … It has been sync'd and source'd under these names May 06 00:24:45 Pastebin: https://pastebin.com/10J4cFUY May 06 00:25:09 This was under the many names I tried, but all had the same error May 06 00:25:20 Try naming it "moto_c_plus" May 06 00:25:51 retrying (I recall doing that. Won't hurt to try again) May 06 00:26:22 If you get the same error again let me know May 06 00:26:49 Will do May 06 00:34:26 https://pastebin.com/TVYJuh6T May 06 00:36:57 Can I just make an empty manifest for my device? Like I don't want to sync it via repo.or using repo sync May 06 00:37:28 You don't need a manifest, but you also can't distribute your work as easily that way. There's really no point in doing it another way. May 06 00:40:00 I'm just experimenting with different device/vendor/kernel trees to pick one to work with for initial code writing... This is not meant to be product shipping or even stable/worth keeping May 06 00:40:36 Yeah, go for it May 06 00:41:35 Thanks Dalton, yeah I'm just experimenting right now and will 200% be replacing this work with better or different stuff May 06 00:42:02 It's only day 2 of the project so no need to make things distribution worthy May 06 00:45:29 @Aaron Lim [https://pastebin.com/TVYJuh6T], According to the error it looks like your missing something in your manifest, can I see your manifest? May 06 00:47:13 @powderedtoastman9000 [It's only day 2 of the project so no need to make things distribution worthy], Everything must be distro worthy hahaha jk May 06 00:47:38 Lol May 06 00:48:23 I would love to help but as I said earlier, Im not gonna try porting .y DD device, my note 4 has an oreo port, I dont think theres a pie port though May 06 00:50:10 One of my goals from 16.0 is to have a Hal for each kernel version to interact with blobs from older devices with a new sexy kernel, but that is something to do much later not when I'm tinkering on day 2 May 06 00:50:49 Yeah, when you get to that point Ill gladly test my note 4 with it and report back May 06 00:51:07 I could also test my N5 May 06 00:55:53 https://pastebin.com/WFwYyPS8 May 06 00:56:32 I want to see old and new devices all supported not just a few outdated devices and some legacy building but priority 1 is that it works with 9.0 blobs and code May 06 00:58:19 The additional version support would be a task for later in the project... I requested Samsung to sponsor the project by supply devices with 9.0 ROM May 06 00:58:48 So hopefully I'll have some phones to give to others devs do they can help with the task May 06 01:02:35 @Aaron Lim [https://pastebin.com/WFwYyPS8], Have you tried it with that lenovo kernel added as well? May 06 01:06:03 @Tygerpro [According to the error it looks like your missing something in your manifest, ca …], Replying May 06 01:06:03 https://pastebin.com/WFwYyPS8 May 06 01:07:06 Thats the same manifest i just looked at May 06 01:09:55 Yeah, Sorry. I thought it wasn't seen, because I didn't say anything after XD … Looking for a Lenevo Kernel May 06 01:23:50 Still in progress at 99% but looks promising … Pastebin: https://pastebin.com/T53cmvya May 06 01:24:59 Still in progress at 99% but looks promising … Pastebin: https://pastebin.com/T53cmvya May 06 01:30:04 Scared because it's still at 99% … Retrying May 06 01:30:51 Well if you hit ctrl+C it should give you an error message May 06 01:31:06 error: Cannot fetch kernel_lenovo_msm8916 from https://github.com/DhirajSurvase/kernel_lenovo_msm8916 … aborted by user May 06 01:31:24 Is this a cause for worry? May 06 01:31:42 Hmm ... it isnt good, thats for sure, give me a moment May 06 01:31:56 no worries. Waiting May 06 01:32:49 Have you tried this repo? … https://github.com/MayurSat19 May 06 01:35:04 Trying soon … Waiting for the retry to finish May 06 01:35:17 Making a manifest for it now May 06 01:59:43 https://pastebin.com/WK5PyNtb … Some fatal errors were seen May 06 02:15:02 https://pastebin.com/FTLgSBnq May 06 02:15:27 So far, it just reaced 99%, and I'm hoping this finishes May 06 02:25:26 Fetching projects: 99% (215/216)^Cerror: Cannot fetch android_device_Moto-Cplus from https://github.com/MayurSat19/android_device_Moto-Cplus … aborted by user … »»User is sad May 06 02:25:36 [Edit] Fetching projects: 99% (215/216)^Cerror: Cannot fetch android_device_Moto-Cplus from https://github.com/MayurSat19/android_device_Moto-Cplus … aborted by user May 06 02:25:41 User is sad May 06 02:27:03 because the repo is 404 May 06 02:27:11 or renamed to https://github.com/MayurSat19/android_device_moto_C_plus-XT1721 May 06 02:27:53 TTwTT … Trying now May 06 02:28:53 Porting halium is like doing your hair in the shower. Mod code, compile, flash, test, debug, repeat May 06 02:29:50 Right now I'm still in the store looking for the perfect shampoo for my hair XD May 06 02:30:14 Fetching projects: 94% (204/216)fatal: Not a git repository: '/home/bigaisdgood1/BUILDDIR/.repo/projects/device/moto/C_plus-XT1721.git' May 06 02:36:04 I dont know whats going on, Im not at my desk for a couple days so I am trying to do this on the fly, whats your current manifest look like? May 06 02:37:55 Theres one above. I'm trying this one now: … https://pastebin.com/XSCvgase May 06 02:39:54 I've been trying out different ways to read the path="device/[manufacturer]/[device]" … https://pastebin.com/ADSWaM0e May 06 02:42:43 You prob wont need the GCC entry, but leave it for now, Im looking through the last one you posted May 06 02:46:45 Your probably having your issue with android_device_moto-cplus, it should prob be android_device_moto_c_plus-xt1721 May 06 02:47:09 THe name, right? Will try that May 06 02:47:34 Yes, iirc its saying it cant fetch that repo right? May 06 02:55:35 https://pastebin.com/CU7bLCJG … Profound Sadness May 06 02:56:35 https://pastebin.com/eBbTRnr6 May 06 02:56:36 Do "repo sync --force-sync" May 06 02:58:06 It's updating my BUILDDIR now May 06 02:59:09 Well were trying to get the repo synced with your builddir so lets just wait and see **** ENDING LOGGING AT Mon May 06 02:59:57 2019