**** BEGIN LOGGING AT Tue May 07 02:59:57 2019
May 07 05:51:58 <ubptgbot> <Venji10> Is it possible to build Halium 7.1 with lineage Oreo trees?
May 07 06:19:29 <ubptgbot> <nanu_c> @Venji10 [Is it possible to build Halium 7.1 with lineage Oreo trees?], No, different Android API that breaks Halium 7.1
**** BEGIN LOGGING AT Tue May 07 17:21:37 2019
May 07 21:57:56 <za1b1tsu> Hello, so I don't understand something, this is not a linux distro made for the end-user? It's something that other distros to use?
May 07 22:02:03 <ubptgbot> <powderedtoastman9000> Yes, correct. Halium 7.1 is a platform to build a distro on top or, or port to use halium. It's meant to allow people to use linux systems on android(which is linux itself but modified) without custom work on hardware support. The idea is that there is a single platform for the kernel and boot system and hardware access, so t
May 07 22:02:03 <ubptgbot> hat distro's and projects don't need to each do the same work halium does for every project. It allows you to start from a better position than just a linux kernel and android tools
May 07 22:02:47 <ubptgbot> <powderedtoastman9000> Without halium, every linux alternate rom would have to do the work halium people do, for every linux rom platform/project
May 07 22:03:50 <ubptgbot> <powderedtoastman9000> It's a very useful project, UT and Plasma use it, and I think sailfish and postmarket are partially based on it(not sure about the second 2 I can't remember)
May 07 22:04:38 <ubptgbot> <powderedtoastman9000> Halium allows developers to start from a good starting point that doesn't involve writing drivers
May 07 22:06:42 <za1b1tsu> and for each devices there needs to be a custom Halium? Because I saw on the website that vendor kernel is used.
May 07 22:08:09 <ubptgbot> <ilyaishere> Yes, for devices that are not similar to each other you need separate Halium builds
May 07 22:08:46 <ubptgbot> <ilyaishere> This is not a problem of Halium, this is what Android forces us to have
May 07 22:09:19 <ubptgbot> <K31j0> Ideally you'd support them on one kernel, but it's kinda impossible
May 07 22:10:09 <ubptgbot> <K31j0> because even if you mainlined it all you'd still have to make device-specific builds and package them
May 07 22:10:23 <ubptgbot> <K31j0> unless you did something like microsoft for lumias, but it's impossible unless you're the vendor
May 07 22:11:22 <za1b1tsu> so what postmakertos tries to do is basically impossible?
May 07 22:11:25 <ubptgbot> <powderedtoastman9000> It's possible, and not hard, to make them all work with a single kernel tree, for each halium version that is - for different kernel versions you need different kernels, but part of my goal for 16.0 is to support every device version numbers by making abstraction layers to interface incompatible parts together in a working wa
May 07 22:11:25 <ubptgbot> y
May 07 22:12:04 <ubptgbot> <powderedtoastman9000> The problem becomes if you try to mix different kernel versions, but this is still possible if you modify the kernel source tree to have multiple versions of things and select them during kernel configuration
May 07 22:12:29 <ubptgbot> <K31j0> @za1b1tsu [so what postmakertos tries to do is basically impossible?], They have to package device-specific builds still
May 07 22:14:54 <za1b1tsu> is there a distro that uses halium?
May 07 22:15:31 <ubptgbot> <powderedtoastman9000> Ubuntu Touch and Plasma both use it
May 07 22:15:45 <ubptgbot> <K31j0> Microsoft supported all lumias from a single line with a single kernel having generic clock support and later dealing with rest of the peripherials using modules
May 07 22:15:51 <ubptgbot> <K31j0> also, UEFI
May 07 22:18:11 <za1b1tsu> wow I did not know that Plasma Mobile was a distro, I always thought it was just DE for touch devices...
May 07 22:19:43 <ubptgbot> <powderedtoastman9000> Yeah, and there is sailfish and postmarket and a few others
May 07 22:20:24 <ubptgbot> <powderedtoastman9000> There is at least a few projects to run non-anroid roms on Android
May 07 22:21:13 <ubptgbot> <powderedtoastman9000> personally I like UT a lot, which is why I'm here. I want to make halium support modern 9.0 android devices so I can port Ubuntu Touch to high end new devices instead of outdated ones
May 07 22:21:33 <ubptgbot> <K31j0> When I hear "ROM" when reffering to OSes I don't know what to say.
May 07 22:21:56 <ubptgbot> <powderedtoastman9000> Well, it's a ROM because the rootfs is mounted ro
May 07 22:22:09 <ubptgbot> <powderedtoastman9000> if the rootfs is mounted at rw, it's not a rom
May 07 22:23:13 <ubptgbot> <powderedtoastman9000> ROM just implies that the system is read only, or at least in part read only... Most "Custom ROMs" for android are zip files that extract to rw mounted partitons from a custom recovery, and to me they are less "ROM" than UT is with it's rootfs as ro
May 07 22:23:30 <ubptgbot> <powderedtoastman9000> Like, terminology gets so warped when you start merging things together
May 07 22:24:11 <ubptgbot> <K31j0> It's an inherently wrong term coined by Android community, which is a terrible platform in the first place. "ROM" used to mean Read-Only Memory as in physical chip limitation and it should stay that way.
May 07 22:25:20 <ubptgbot> <powderedtoastman9000> yeah, I know, but things change... ROM used to be single-use-flash devices that could only be written to once, but that was when I was a little kid, the term has changed a lot, and the Android/AOSP/XDA community is mostly idiots, so yeah they did repurpose the word incorrectly
May 07 22:25:57 <ubptgbot> <powderedtoastman9000> but their term ROM has become adopted enough that it's an actual definition now... Language evolves pretty damn fast in expanding new technology fields
May 07 22:26:37 <ubptgbot> <powderedtoastman9000> terminology based discussions are kinda annoying to me, because they usually have both people being right in a different way and arguing semantics
May 07 22:27:44 <ubptgbot> <K31j0> This discussion is pointless, but I think this is not "Android community" and it shouldn't replicate what others did wrong.
May 07 22:28:35 <ubptgbot> <powderedtoastman9000> @powderedtoastman9000 [terminology based discussions are kinda annoying to me, because they usually hav …], agreed that it's pointless, and agreed that the term should not be used this way, and I'll try and stop using it myself because you're right... but i think the main point you made that is most useful is this discussion
May 07 22:28:35 <ubptgbot> is pointless
May 07 23:14:45 <za1b1tsu> I wish I could find some libhybris device compatibility. I would like to buy a phone (big screen, oled) that I could try linux on (vendor kernel)
May 07 23:15:51 <ubptgbot> <powderedtoastman9000> @za1b1tsu [I wish I could find some libhybris device compatibility. I would like to buy a p …], Try getting a Nexus 5 or OnePlus One, both < $200, hard to find new, but used one is easy to find, then you can use Ubuntu Touch. Those 2 devices are the best supported for UT
May 07 23:16:00 <ubptgbot> <powderedtoastman9000> I use UT on Nexus 5, and it's great
May 07 23:17:25 <za1b1tsu> thanks for the recommendation, I am hoping for oled phone though
May 07 23:17:59 <ubptgbot> <powderedtoastman9000> Oh, well, in the next few months, I should have an alpha build of S7 phone for UT, but don't expect it to be stable and useful for daily driver
May 07 23:18:59 <za1b1tsu> I had an s7 gave it away, now I have a note 9
May 07 23:19:04 <ubptgbot> <powderedtoastman9000> Oh darn
May 07 23:19:18 <ubptgbot> <powderedtoastman9000> I wish you kept it so you could be one of my alpha testers
May 07 23:19:34 <ubptgbot> <powderedtoastman9000> In a few months I'll need people to do early stage testing
May 07 23:19:49 <za1b1tsu> the screen is so superb on the note 9, I need AMOLED screens in my life
May 07 23:19:52 <za1b1tsu> sorry :(, wish I knew
May 07 23:20:20 <ubptgbot> <powderedtoastman9000> I have almost all hardwarem support done, and I have most apps working... in 2-3 months I expect to only need to debug things and maintain. but that's a rough esitmate, I really can't exactly predict when it will be ready for alpha testing
May 07 23:21:01 <za1b1tsu> what is the hardest part when making a build for a phone?
May 07 23:25:04 <ubptgbot> Islander . was added by: Islander .
May 07 23:29:34 <za1b1tsu> goodnight, thank you for all the info
May 07 23:31:50 <ubptgbot> <powderedtoastman9000> @za1b1tsu [what is the hardest part when making a build for a phone?], The hardest part is learning the steps you need to do the work
May 07 23:34:59 <ubptgbot> <Islander .> enlightening, I'd better get some reading done before I come back here
May 07 23:35:31 <ubptgbot> <powderedtoastman9000> You can stay here, and learn from us(i'm a noob myself but many here can help you if i can't)
May 07 23:37:12 <ubptgbot> <Islander .> currently going through the Halium documentation and the UT stuff for a manual install - in an attempt to rescusitate a LG E430 circa 2013
May 07 23:38:08 <ubptgbot> <Islander .> I like the unit alot more than some of the recent gear
May 07 23:39:52 <ubptgbot> <ankaos> I ran it for ubports lge.
May 07 23:43:23 <ubptgbot> <Islander .> from Github..?
May 07 23:47:30 <ubptgbot> <Islander .> the device at least is being recognised after following the initial stages
May 07 23:47:36 <ubptgbot> <Islander .> mate19@mate19-Aspire-5735:~$ adb devices … List of devices attached … LGOTMS68678a40  device
May 07 23:48:37 <ubptgbot> <Islander .> something the UBPorts installer didn't get near (no criticism, just observation)
May 07 23:50:47 <ubptgbot> <ankaos> device models?
May 07 23:52:11 <ubptgbot> <powderedtoastman9000> I don't honestly know, but yeah the ubports team is kind of... Some of them I don't like beccause they are mean and rude to me, the others I like, but they are just normal programmers, they don't have amazing skills that I have respect for, I respect them because of the work they do, but I don't think they are as skilled as t
May 07 23:52:11 <ubptgbot> hey could be
May 07 23:52:41 <ubptgbot> <powderedtoastman9000> I love the team, and their work, but I think that the team needs people who are more hackers and less devs...
May 07 23:53:05 <ubptgbot> <powderedtoastman9000> like, that's just how I feel, they are good coders, I don't say they are bad, they just aren't hackers
May 07 23:53:41 <ubptgbot> <powderedtoastman9000> When I use the term hacking to describe a technique I make, they tell me to stop calling it hacking, they don't know the true meaning of hacking based on that comments
May 07 23:53:54 <ubptgbot> <ankaos> @Islander . [mate19@mate19-Aspire-5735:~$ adb devices … List of devices attached … LGOTMS68678a40 …], ı dont find :(
May 07 23:54:13 <ubptgbot> <powderedtoastman9000> I love the ones that aren't mean to me and have respect for them and their work, but the ones who aren't nice to me, I have no respect for
May 07 23:55:30 <ubptgbot> <powderedtoastman9000> I left all the channels related to UT except porting and stayed in this channel too, cause I don't want to deal with the people who are mean to me unless it's important for work we are doing on UT/hal
May 07 23:56:20 <ubptgbot> <Islander .> @ankaos [ı dont find :(], I'ts the OS I'm using on the laptop - Ubuntu Mate 18.04
May 07 23:56:50 <ubptgbot> <powderedtoastman9000> I use Kubuntu myself, love it
May 07 23:57:04 <ubptgbot> <Islander .> the text was taken from straight from the termonal
May 07 23:57:12 <ubptgbot> <powderedtoastman9000> i'm on 18.10
May 07 23:57:14 <ubptgbot> <ankaos> @Islander . [I'ts the OS I'm using on the laptop - Ubuntu Mate 18.04], phone device not found.
May 07 23:57:19 <ubptgbot> <ankaos> sorry
May 07 23:57:32 <ubptgbot> <ankaos> got it from the wrong place.
May 07 23:58:05 <ubptgbot> <Islander .> Kub, a bit too intergrated for me.
May 07 23:58:13 <ubptgbot> <powderedtoastman9000> I finished reading my udev rules book, and now my 3g and camera work on my S7
May 07 23:58:29 <ubptgbot> <Islander .> LGOTMS68678a40  device apparently thatś  the LG E430
May 07 23:58:56 <ubptgbot> <powderedtoastman9000> I only need to fix audio and then hardware support is done(but not debugged/tested)
May 08 00:00:04 <ubptgbot> <powderedtoastman9000> When I started this, I predicted it would take a year to get where i am now... it's been 5 weeks, so I'm damn happy with myself now. although I keep track of the time I code, and that 5 weeks has been 578 hours of time spent, and I bricked a phone from flashing it so many times with new builds to test
May 08 00:00:32 <ubptgbot> <ankaos> will
May 08 00:00:58 <ubptgbot> <Islander .> but the bootloader unlock and install can wait until the morrow. hasta mañana.
May 08 00:01:03 <ubptgbot> <ankaos> `https://docs.ubports.com/en/latest/porting/common-problems-install.html#ssh-hangs-when-trying-to-connect` Is there another solution?
May 08 00:02:31 <ubptgbot> <powderedtoastman9000> @ankaos boot into TWRP and use the repo halium-scripts which contains a halium-chroot script, and use that script while in TWRP, and it will give you a shell of the system. Use it to enable sshd via systemd, and enable network-manager, and disable UFW or allow ssh through UFW, and disable apparmor until you have all your hard
May 08 00:02:31 <ubptgbot> ware working
May 08 00:02:40 <ubptgbot> <ankaos> `debug1: connect to address 10.15.19.82 port 22: Connection timed out … ssh: connect to host 10.15.19.82 port 22: Connection timed out` say me
May 08 00:02:48 <ubptgbot> <ankaos> [Edit] ` debug1: connect to address 10.15.19.82 port 22: Connection timed out … ssh: connect to host 10.15.19.82 port 22: Connection timed out` say me
May 08 00:02:49 <ubptgbot> <powderedtoastman9000> halium-chroot allows you to get into the device ROM and edit it without the system properly running
May 08 00:02:53 <ubptgbot> <ankaos> [Edit] ` debug1: connect to address 10.15.19.82 port 22: Connection timed out … ssh: connect to host 10.15.19.82 port 22: Connection timed out ` say me
May 08 00:03:12 <ubptgbot> <powderedtoastman9000> Try pinging the device also
May 08 00:03:21 <ubptgbot> <powderedtoastman9000> that will tell you if the device is running a network connection at all
May 08 00:03:56 <ubptgbot> <ankaos> @powderedtoastman9000 [@ankaos boot into TWRP and use the repo halium-scripts which contains a halium-c …], connect to the system. should I enter?
May 08 00:05:37 <ubptgbot> <ankaos> how make ı?
May 08 00:05:38 <ubptgbot> <powderedtoastman9000> you enter twrp, then you use halium-chroot script to enter the system while it's not actually running, it gives you a shell in the rootfs with all partitions mounted and everything working, and you can try and fix your problems from chroot instead of blind debugging
May 08 00:05:43 <ubptgbot> <ankaos> ı dont understand
May 08 00:05:55 <ubptgbot> <powderedtoastman9000> hold on, let me get you a link to the script
May 08 00:06:09 <ubptgbot> <powderedtoastman9000> https://github.com/Halium/halium-scripts
May 08 00:06:51 <ubptgbot> <powderedtoastman9000> you enter TWRP, or whatever custom recovery you are using, and run the halium-chroot script, and it will enter you into the system in your terminal with everything mounted and working as if it was running the actual system
May 08 00:07:31 <ubptgbot> <powderedtoastman9000> UT rootfs uses upstart, which often doesn't start sshd properlty, but systemd is in the rootfs and I enable sshd with systemd that's how I fixed the no ssh problem, which I think is the same problem you are having
May 08 00:08:03 <ubptgbot> <powderedtoastman9000> So "systemctl enable sshd" and then reboot the device and try again... That is how I did it, but I don;'t know if it's the same issue I had or not
May 08 00:09:25 <ubptgbot> <ankaos> `bash: systemctl: command not found`
**** ENDING LOGGING AT Wed May 08 02:59:56 2019