**** BEGIN LOGGING AT Fri Apr 05 02:59:57 2019
Apr 05 07:47:55 <ubptgbot> Hangman228 was added by: Hangman228
Apr 05 07:49:37 <ubptgbot> me_gossen was added by: me_gossen
Apr 05 09:42:41 <ubptgbot> LedBass was added by: LedBass
Apr 05 10:37:36 <ubptgbot> Stebomurkn420 was added by: Stebomurkn420
Apr 05 10:44:19 <ubptgbot> <powderedtoastman9000> Do I need the driver blobs from a ROM in my system partition, or does TheMuppets vendor repos have drivers covered? And what do I do with the Android replace script, like do I use it with the system.img to replace the original ROM partition or do I use a stock ROM so it has blobs and other stuff needed? I am confused by lack
Apr 05 10:44:19 <ubptgbot> of details in the docs
Apr 05 10:53:09 <ubptgbot> <fredldotme> It really depends on your device. TheMuppets probably has their repos set up by device codename, you should be able to find out whether they have the blobs already or not.
Apr 05 10:58:58 <ubptgbot> <powderedtoastman9000> The Muppets has my device, but I don't know if that's all I need or if both are required. I have on my own project just used blobs with a HAL in kernel space, so I wasn't sure if I still needed blobs or if them vendor tree would work, provided it has my device in the tree which it does
Apr 05 10:59:20 <ubptgbot> <powderedtoastman9000> So is the only blob I actually need the radio binary?
Apr 05 10:59:52 <ubptgbot> <powderedtoastman9000> I have not gotten to the point where I can test hardware I'm just thinking ahead
Apr 05 11:02:42 <ubptgbot> <powderedtoastman9000> Looks like TheMuppets has some blobs included now that I'm looking, so I have the blobs in my vendor tree... I didn't think they would actually publish blobs they ripped from ROMs
Apr 05 11:04:19 <ubptgbot> <powderedtoastman9000> So that answers the first question, next what do I do with the Android replace system.img script. I have not seen it mentioned in the docs, and I am a not sure if I should use it at all, or if wiping system partition and using halium-install to push them to userdata partition is all I need.
Apr 05 12:37:43 <ubptgbot> dcshendu was added by: dcshendu
Apr 05 16:39:20 <ubptgbot> <powderedtoastman9000> Has anyone run success enlightenment de on Halium?
Apr 05 17:00:05 <ubptgbot> <NotKit> it needs code for hwcomposer at the very least
Apr 05 17:12:15 <ubptgbot> <powderedtoastman9000> Well, I'm totally up getting everything possible working by the time I do all this stuff I plan, not just the minimum to work stable and nice
Apr 05 17:13:34 <ubptgbot> <powderedtoastman9000> I will invest time in gl accelerarion and other stuff like that but only if it will be accepted and used... But before enlightenment I need a proper UT port system, then I can goof off with other stuff
Apr 05 17:15:05 <ubptgbot> <powderedtoastman9000> I want to make Hal 7.1 and UT working ROMs, before I try making custom versions that won't get as adopted
Apr 05 17:16:28 <ubptgbot> <powderedtoastman9000> But I can do hardware drawing accel and I have done drm on one phone a couple years ago, but that stuff comes after getting more prepared systems running as they were meant to
Apr 05 17:51:28 <ubptgbot> <LedBass> Hi everybody … I've followed every steps to create a Halium-boot.img to install in a Samsung GalaxyNote 10.1 2014 … It turns out that the the halium-boot.img image got bigger tha
Apr 05 17:53:06 <ubptgbot> <LedBass> Hi everybody … I've followed every steps to create a Halium-boot.img to install in a Samsung GalaxyNote 10.1 2014 … It turns out that the the halium-boot.img image got bigger than the partition in PIT file (and yes, all patitions were listed in the fixup-mountpoints file
Apr 05 17:53:45 <ubptgbot> <LedBass> does anybody tyring port to samsung devices? if yes, did you guys managed to overcome this?
Apr 05 17:53:58 <ubptgbot> <LedBass> is Anybody*
Apr 05 17:55:22 <ubptgbot> <Flohack> @LedBass [does anybody tyring port to samsung devices? if yes, did you guys managed to ove …], you need to try to reduce kernel size. Look at lzma compression, dont use lzo
Apr 05 17:55:41 <ubptgbot> <LedBass> Ok, thanks
Apr 05 17:56:22 <ubptgbot> <LedBass> Do you know that work as well for system and rootfs images?
Apr 05 17:57:51 <ubptgbot> <Flohack> @LedBass [Do you know that work as well for system and rootfs images?], You will have a rather hard time reducing their size I am afraid. But the critical one is usuall only boot partition
Apr 05 17:58:11 <ubptgbot> <Flohack> Note that Odin and Heimdall normally dont tell you if the flash was unsuccessful, it will just boot previous image or bootloop
Apr 05 18:01:26 <ubptgbot> <LedBass> @Flohack [Note that Odin and Heimdall normally dont tell you if the flash was unsuccessful …], It actually show some erros, but is something like "ERROR: Failed to confirm end of file transfer sequence!"
Apr 05 18:01:41 <ubptgbot> <Flohack> ok
Apr 05 18:01:52 <ubptgbot> <Flohack> that might depend a bit on the device. Mine just ate it ^^
Apr 05 18:04:35 <ubptgbot> <LedBass> Yeah, but even that isn't that helpfull, I had to go and search for possibilities, and the size of the partition crossed my mind, when I went to check that and bang! the size were smaller than the image I was trying to flash
Apr 05 18:05:16 <ubptgbot> <LedBass> well, let's try lzma
Apr 05 18:05:21 <ubptgbot> <LedBass> Thanks Florian
Apr 05 18:05:53 <Danct12[m]> On my LG P698, the kernel partition is too small that I have to use XZ compression, had to backport that in
Apr 05 18:06:23 <Danct12[m]> Sadly that phone never got a Halium port as it's kernel too old
Apr 05 18:07:29 <ubptgbot> <powderedtoastman9000> Remove kernel components you don't need, select optimize kernel for size, and disable compiling of modules that won't be loaded in the menu menuconfig of kernel, and debugging features take up space in the kernel so only enable the ones you need for your next test build
Apr 05 18:07:49 <ubptgbot> <powderedtoastman9000> If your kernel won't fit the answer is to make it smaller
Apr 05 18:09:25 <ubptgbot> <powderedtoastman9000> You can also set compiler flags in CFLAGS env variables to optimize for size as well as kernel config option. It's very likely that your kernel has tons of stuff enabled that you don't need, unless you've already tried all those steps and it still doesn't fit
Apr 05 18:09:45 <ubptgbot> <powderedtoastman9000> I forget the CGLAGS option of optimize for size
Apr 05 18:10:07 <ubptgbot> <LedBass> @powderedtoastman9000 [Remove kernel components you don't need, select optimize kernel for size, and di …], How do I know what components the device doesn't need to work properly?
Apr 05 18:11:19 <ubptgbot> <NotKit> @LedBass [does anybody tyring port to samsung devices? if yes, did you guys managed to ove …], you would need a hack basically to boot initramfs from another device
Apr 05 18:11:21 <ubptgbot> <powderedtoastman9000> Well, you probably don't need support for every language to display and keep locale info on, you're probably never going to use any file systems except fat, ext2 ext4 ntfs and hfs+...
Apr 05 18:11:31 <ubptgbot> <NotKit> kernel components disabling won't help much
Apr 05 18:11:47 <ubptgbot> <powderedtoastman9000> Its It's worth trying
Apr 05 18:11:55 <ubptgbot> <powderedtoastman9000> Every byte matters
Apr 05 18:11:57 <ubptgbot> <LedBass> @powderedtoastman9000 [Well, you probably don't need support for every language to display and keep loc …], Ok, know I got it … Thanks
Apr 05 18:12:19 <ubptgbot> <NotKit> how much larget resulting boot.img is compared to partition size?
Apr 05 18:12:23 <ubptgbot> <powderedtoastman9000> It might not help enough, but the alternative is to give up
Apr 05 18:12:25 <ubptgbot> <NotKit> [Edit] how much larger resulting boot.img is compared to partition size?
Apr 05 18:12:47 <ubptgbot> <LedBass> the image is 1.6 MB larger then the partition size
Apr 05 18:14:32 <ubptgbot> <powderedtoastman9000> You MIGHT be able to cut it down by 1.6mb, also have you tried using a different compression type for kernel image and dtb and initramfs
Apr 05 18:15:09 <ubptgbot> <powderedtoastman9000> Default is gzip which is much less effective than xz or lz4
Apr 05 18:15:22 <ubptgbot> <LedBass> Not yet, will try next time othr options
Apr 05 18:15:27 <ubptgbot> <NotKit> you can't have different compression for kernel and dtb, as that is handled by bootloader
Apr 05 18:15:37 <ubptgbot> <NotKit> but using xz for ramdisk could give you 1.4 mb
Apr 05 18:15:55 <ubptgbot> <powderedtoastman9000> You can on Samsung device like they have.
Apr 05 18:16:17 <ubptgbot> <NotKit> don't you get zImage as result?
Apr 05 18:16:53 <ubptgbot> <LedBass> I got just an img file, if it's a zimage i can't say for sure
Apr 05 18:18:47 <ubptgbot> <powderedtoastman9000> I have tried xz and lz4 on my s7, and they worked
Apr 05 18:19:03 <ubptgbot> <LedBass> Hmmm, woth a try
Apr 05 18:19:07 <ubptgbot> <powderedtoastman9000> Can't say for sure that their device is the same but its possible
Apr 05 18:19:41 <ubptgbot> <LedBass> Probably is diferent (it's from 2013/2014) but it's a try
Apr 05 18:19:57 <ubptgbot> <powderedtoastman9000> Also halium-boot is way smaller than hybris-boot
Apr 05 18:20:08 <ubptgbot> <powderedtoastman9000> Incase you are in hybris
Apr 05 18:21:25 <ubptgbot> <LedBass> Well, that's the point
Apr 05 18:21:27 <ubptgbot> <powderedtoastman9000> I couldn't get hybris-boot to branch into the kernel code so I have no way to debug it, and halium-boot works great for me
Apr 05 18:21:46 <ubptgbot> * powderedtoastman9000 shrugs
Apr 05 18:21:58 <ubptgbot> <LedBass> The Hybris-boot actually fits and flashes with no problem, but halium-boot doesn't
Apr 05 18:22:26 <ubptgbot> <LedBass> and hybris, in my case with this device, endded up smaller than halium
Apr 05 18:22:41 <ubptgbot> <powderedtoastman9000> Oh, that's... strange to me. I would investigate why that is the case, because it compiles and includes much less code
Apr 05 18:23:02 <ubptgbot> <powderedtoastman9000> I mean, maybe there is a factor I'm missing but it seems strange based on my limited knowledge
Apr 05 18:24:14 <ubptgbot> <LedBass> Well, my knowledge is quiet limited too … I just started the porting for this device 2 days ago and stucked in the flashing part of the porting
Apr 05 18:26:27 <ubptgbot> <LedBass> hybris does flash and Heimdall restarts the device (that's very frustrating and irritating), the screen shows the samsung logo with a waring that the kernel isn't compatible with selinux and the screen goes black … Strangelly the partitions of the device got listed in my laptop (it's running KDE Neon)
Apr 05 18:26:54 <ubptgbot> <LedBass> sorry for some miss typos in my messages
Apr 05 18:30:42 <ubptgbot> <powderedtoastman9000> You can pass --no-reboot to heimdall. Then every command after the first requires  --resume
Apr 05 18:33:10 <ubptgbot> <LedBass> I did that and it just doesn't work well … However, the images were bigger too, when I manage to shrink them I will try again
Apr 05 18:33:23 <ubptgbot> <LedBass> offcourse I will update you guys here
Apr 05 18:39:36 <ubptgbot> <powderedtoastman9000> Good luck
Apr 05 18:43:23 <ubptgbot> <LedBass> Thanks, will need it
Apr 05 19:07:38 <houkime_> Why exactly it is said that halium ports need 16 gb storage? Linux distros are usually way smaller than that.
Apr 05 19:08:55 <ubptgbot> <UniversalSuperBox> Because Android partitioning means that you normally don't have the contiguous space you need with an 8GB eMMC
Apr 05 19:09:19 <ubptgbot> <UniversalSuperBox> The space you need being about 2.5GB
Apr 05 19:13:32 <houkime_> Is there a way to overwrite partitioning (and maybe use other bootmanager to accomodate for that?)
Apr 05 19:15:17 <ubptgbot> <UniversalSuperBox> Repartitioning an Android phone is not guaranteed to be successful
Apr 05 19:15:47 <ubptgbot> <UniversalSuperBox> And it's a pain for your users, so you limit your userbase something awful
Apr 05 19:15:57 <ubptgbot> <UniversalSuperBox> The devices just aren't worth your time
Apr 05 19:20:18 <houkime_> ok thanks.
Apr 05 20:11:32 <ubptgbot> <NotKit> houkime_, you can SD if supported
Apr 05 20:11:47 <ubptgbot> <NotKit> but device with 8 GB eMMC is probably very old and has little RAM as well
Apr 05 20:19:21 <houkime_> well, yep 512 mb is a bit on the small side though for minimalistic linux and almost text-mode web-browsing might be enough. Don't know about ubuntu touch though, it might not be economical enough.
Apr 05 20:23:25 <ubptgbot> <powderedtoastman9000> I don't think UT on a half gig of ram is useful for anything other than SMS and making calls,  and even that may oom it
Apr 05 20:24:55 <ubptgbot> <powderedtoastman9000> Like my nexus 5 uses 500+ mb when I'm not using any apps
Apr 05 20:25:09 <ubptgbot> <powderedtoastman9000> 500 is a minimal usage,800 is more common
Apr 05 20:25:47 <ubptgbot> <powderedtoastman9000> Oh sorry I though this was the IT channel .. no clue how much halium needs
Apr 05 20:26:29 <houkime_> hmm. 500 idle feels a bit over the top and unoptimized maybe. It is in range of full-blown desktop KDE.
Apr 05 20:27:14 <houkime_> maybe i can make or find myself sth smaller than UT and all will be fine.
Apr 05 20:30:11 <ubptgbot> <powderedtoastman9000> If you make it, you can strip out functionality and features you don't want to decrease memory and CPU loads
Apr 05 20:30:42 <ubptgbot> <powderedtoastman9000> But then its only really useful to you and no one else
Apr 05 20:33:24 <houkime_> well, these phones have native software which fits and useful. So at least it is possible to pack enough functionality in that. Also there's an extremely small but cool enough Puppy Linux.
Apr 05 20:56:24 <ubptgbot> * alfred_hedgehog
Apr 05 21:56:28 <ubptgbot> rockerdiaz was added by: rockerdiaz
Apr 05 21:58:16 <ubptgbot> <NotKit> houkime_, those specs are more in Maemo Leste range, but they aim for mainline support, so probably no luck here either
Apr 06 01:35:22 <ubptgbot> <ankaos> hi
Apr 06 01:35:31 <ubptgbot> <ankaos> d802 make ubport
Apr 06 01:35:37 <ubptgbot> <ankaos> thanks grup
Apr 06 01:36:00 <ubptgbot> <ankaos> (Photo, 720x1280) https://irc.ubports.com/wIvMSPQr.png
Apr 06 01:36:13 <ubptgbot> <ankaos> but not test
**** ENDING LOGGING AT Sat Apr 06 02:59:57 2019