**** BEGIN LOGGING AT Wed Nov 13 02:59:58 2019 Nov 13 03:09:31 The project is alive as ever if look at the activity in the telegram group @halium current efforts are focussed on getting android 8+ devices supported Nov 13 03:10:13 There's also docs.halium.org regarding architecture Nov 13 03:28:21 hmm. of course theres more chat on telegram heh I’m of course american and we dont use that app much. ive been reading around for hours over the past several days. The halium docs aren’t _bad_ just not always 100% thorough. I get the whole idea. It builds a base system based on your phone, mainly just the kernel and HAL, then helps you install libhybris on top. im more curious about the inner workings - the flags its using for builds, what modules, the Nov 13 03:28:22 configs, etc. my friend has done custom AOSP installs before so it isnt all foreign or anything. either way, @rudi9719 and i will be around in the coming days occasionally asking questions possibly. well be taking notes, so if we think the documentation is lacking somewhere, we will happily make pull requests and the like. Nov 13 03:28:41 my apologies for being so long winded by the way. I just tend to be that way heh Nov 13 03:42:16 Anthony Olmstead was added by: Anthony Olmstead Nov 13 03:43:40 I made a telegram specifically for this, as IRC is a little clunky. So, messages from me will now be from this acc Nov 13 04:35:10 Ah no problem and welcome Nov 13 07:36:46 Peter Schelchshorn was added by: Peter Schelchshorn Nov 13 08:18:53 Hi guy's, … I try to make a port for the GT-N8000, I'm using the same kernel source (smdk4412 Linux 3.0.101) which I use for LinageOS 14.1. … But, the device is just rebooting because of a Kernel panic. … https://pastebin.com/9JHJBk4P … What do you think, do I have a driver problem what cause's the Kernel panic? Nov 13 12:31:42 Hello to the Hallium team! Been having this error here: https://pastebin.com/1zF4W5zc . Not much of information of why it failed, but maybe someone has any idea whatsoever? Nov 13 12:43:35 @rixchy [Hello to the Hallium team! Been having this error here: https://pastebin.com/1zF …], error: /home/rixchy/halium/out/target/product/chagalllte/boot.img too large (8749072 > [8650752 - 88704]) Nov 13 12:43:44 You need to slim down your kernel Nov 13 12:43:50 change compression to LZMA for example Nov 13 12:44:51 @rixchy [], Hm, I have. Nov 13 12:45:49 @rixchy [Hm, I have.], Then its still too large ;) - It is what it is, so you need to disable kernel options to remove code. For me it helped for example to turn off support for md devices and remove the joystick support 😆 Nov 13 12:46:23 use lz4 Nov 13 12:48:47 @Flohack [Then its still too large ;) - It is what it is, so you need to disable kernel op …], I even set some configs to =m, but as I understand, then the joystick support, is like the controllers and all like that? Nov 13 12:51:23 @rixchy [I even set some configs to =m, but as I understand, then the joystick support, i …], set them to n, you need to remove the feature to get maximum savings Nov 13 12:51:58 @Flohack [set them to n, you need to remove the feature to get maximum savings], Ok, but what abut the joystick support. Those are D-Pads, controllers, yeah? Nov 13 12:55:30 @rixchy [Ok, but what abut the joystick support. Those are D-Pads, controllers, yeah?], Kind of all joysticks ever made for PCs. For details plz google ^^ Nov 13 12:55:57 @Flohack [Kind of all joysticks ever made for PCs. For details plz google ^^], Hm, okay. :) Nov 13 12:55:58 Your kernel probably has a ton of stuff thats unneeded. Also you can disable file systems Nov 13 12:56:03 they are also quite large in size Nov 13 12:56:35 YOu need 89kB less ^^ Nov 13 12:56:38 Thats not that much Nov 13 12:57:01 Hm, actually you just helped me out a little futher. My halium-boot was 4 MB larger than the boot partition so I have to make it smaller. I will scroll through the defconfig a little and remove the things I don't need. :) Nov 13 13:19:58 Is it okay if EXT2 is set like this "CONFIG_EXT2_FS=n"? Since EXT2 isn't used? Nov 13 13:20:20 @rixchy [Is it okay if EXT2 is set like this "CONFIG_EXT2_FS=n"? Since EXT2 isn't used?], Yes probably, what else is enabled? Nov 13 13:20:40 See also here: https://elinux.org/Kernel_Size_Tuning_Guide Nov 13 13:21:33 (Photo, 284x657) https://irc.ubports.com/ee5N1T0T.png Here's the FS in defconig, will check out your link now. Nov 13 13:22:01 Yeah and then after disabling a bit, just rebuild and see Nov 13 13:22:07 this is try & error for some time ^^ Nov 13 13:22:12 Mhm. :) Nov 13 13:22:32 F2FS can prob be removed as well since we dont support that Nov 13 13:23:21 @Flohack [See also here: https://elinux.org/Kernel_Size_Tuning_Guide], Just checking in, I need to disable the CONFIGs which are in the "Kernel Configuration Options" part, right? Nov 13 13:23:27 @Shakendo [F2FS can prob be removed as well since we dont support that], Mhm, okay! Nov 13 13:30:33 Right, (i.e. CONFIG_F2FS=n) Nov 13 13:30:59 [Edit] Right, (i.e. CONFIG_F2FS_FS=n) Nov 13 13:32:06 @rixchy [Just checking in, I need to disable the CONFIGs which are in the "Kernel Configu …], Yes but be careful, not all will be ok ^^ Nov 13 13:32:26 @Flohack [Yes but be careful, not all will be ok ^^], Okay. Nov 13 13:44:16 Does Halium use NTFS? Nov 13 13:44:47 Heh, no Nov 13 13:44:58 Okay. :) Nov 13 13:45:06 Just wanted to know if I can disable this (CONFIG_NTFS_FS=y) Nov 13 13:47:44 yes please do it. Those kernels were never properly cleaned Nov 13 13:47:56 Yep, I did! Nov 13 13:48:06 Well only reason could be if you want to use an SD card with NTFS ^^ Nov 13 13:48:14 And it went even further after disabling NTFS. Nov 13 13:48:47 @Flohack [Well only reason could be if you want to use an SD card with NTFS ^^], I doubt that, since I don't have a SD card in my tablet, and I feel like I never will, since all of my documents are in Dropbox or etc. Nov 13 13:54:06 @rixchy [And it went even further after disabling NTFS.], Did you check size and try to compile? Nov 13 14:14:06 @Flohack [Did you check size and try to compile?], It went further, but it failed at recovery making with the same error. "error: /home/rixchy/halium/out/target/product/chagalllte/recovery.img too large (10864656 > [10813440 - 109824])" Nov 13 14:14:14 And it just finished now. Nov 13 14:16:49 the way you could fit initramfs could be by using minimal ramdisk to unpack halium-boot ramdisk from physical partition, but that needs some bash scripting and trial-and-error debugging Nov 13 14:24:45 Is it okay to disable this CONFIG_MSDOS_PARTITION? Nov 13 14:26:10 it seems like you're getting into the area of disabling reasonable functionality now Nov 13 14:26:25 Oh, so I shouldn't disable it? Nov 13 14:31:36 i don't know if vfat requires it or not Nov 13 14:54:07 The Samsung people here: "ERROR: Failed to confirm end of file transfer sequence! … ERROR: BOOT upload failed!" This means that the image's too big, right? Nov 13 15:29:10 @rixchy [The Samsung people here: "ERROR: Failed to confirm end of file transfer sequence …], you are using Heimdall? Nov 13 15:29:35 Yup. Nov 13 15:30:34 Not sure if its size sorry. Did not have this case I believe with my Samsung S3. Nov 13 15:30:40 Whats your cmdline for flashing Nov 13 15:30:57 @Flohack [Whats your cmdline for flashing], heimdall flash —BOOT halium-boot.img Nov 13 15:31:05 But the image itself is too big indeed. Nov 13 15:31:57 As looking into the BoardConfig.mk, I have 8388608 bytes available which are approx. 8 MB. But halium-boot is 10 MB. Nov 13 15:42:52 @rixchy [As looking into the BoardConfig.mk, I have 8388608 bytes available which are app …], ouch! Nov 13 15:42:59 Yep. Nov 13 15:43:19 And now, I modified the defconfig, and it won't even compile now. That means I BROKE SOMETHING. Nov 13 15:43:28 good luck ^^ Nov 13 15:43:42 Thanks. Nov 13 16:32:40 Joginder Singh Saini was added by: Joginder Singh Saini Nov 13 16:32:49 Hello. Nov 13 16:34:06 Hi! Nov 13 16:37:22 I have a redmi2 device, can I port it to Ubuntu touch using halium. Nov 13 16:37:57 Depends, does your device has kernel published on GitHub? Nov 13 16:38:26 @Joginder Singh Saini [I have a redmi2 device, can I port it to Ubuntu touch using halium.], Follow docs: http://docs.halium.org/en/latest/porting/first-steps.html Nov 13 16:38:32 Yes but it has only 8 Gb internal storage. Nov 13 16:38:48 @Joginder Singh Saini [Yes but it has only 8 Gb internal storage.], Oh. Hm. It might be enough...? Nov 13 16:39:06 Thank you. Nov 13 16:39:11 Mhm! Nov 13 16:43:11 I will post again if I need more help. Nov 13 16:45:55 Okat. Nov 13 16:46:02 [Edit] Okay. Nov 13 16:48:31 Thanks Richard Lucin Nov 13 16:54:01 No problem again! Nov 13 17:10:27 Joginder Singh there is halium port for redmi2 already Nov 13 17:12:44 https://github.com/abhishek9650 Nov 13 17:13:34 Oops, I apologize for not including this. Nov 13 17:37:07 @rixchy have you tried repartitioning? Nov 13 17:56:32 Richard Nov 13 17:57:10 Yep? Nov 13 17:57:20 whats your nand name under /dev/? Nov 13 17:57:37 How to check that? 😆 Nov 13 17:57:42 ls /dev/ Nov 13 17:58:01 you can try repartitioning with fdisk Nov 13 17:58:44 @Akatsu . [ls /dev/], abd shell? Nov 13 17:58:51 @Akatsu . [ls /dev/], [Edit] adb shell? Nov 13 17:59:15 yup Nov 13 17:59:18 under twrp Nov 13 18:00:14 (Photo, 587x639) https://irc.ubports.com/5yANwu3F.png Nov 13 18:00:27 Here you go. Nov 13 18:00:33 cd block? Nov 13 18:00:36 and then ls Nov 13 18:01:26 Same. Nov 13 18:02:14 nothing like that? Nov 13 18:02:15 (Photo, 720x1280) https://irc.ubports.com/KmfwJXRy.png Nov 13 18:02:27 Hm, wait. Nov 13 18:02:58 Ah-ha! Got it. Nov 13 18:03:56 do you have mmcblk there? Nov 13 18:04:00 (Photo, 687x323) https://irc.ubports.com/GIIG1X5M.png Sorry, just didn't understand you correctly. Anyways, here you go. Nov 13 18:04:15 fdisk -l mmcblk0 Nov 13 18:04:18 from that dir Nov 13 18:04:31 From the /dev/block, right? Nov 13 18:04:34 ye Nov 13 18:05:17 (Photo, 679x409) https://irc.ubports.com/MWSrd0YX.png Here! Nov 13 18:05:28 (I have heard that the HIDDEN partition isn't needed. Nov 13 18:05:34 [Edit] (I have heard that the HIDDEN partition isn't needed.) Nov 13 18:05:46 yup Nov 13 18:05:56 Okay! Nov 13 18:06:05 but getting rid of hidden will leave you with tons of resizing Nov 13 18:06:36 PARAM and recovery might be interesting Nov 13 18:06:56 ? Nov 13 18:07:05 Is there any more info you need? Nov 13 18:07:13 not really Nov 13 18:07:18 Alright. Nov 13 18:07:26 you have tried some resizing with pit files rite? Nov 13 18:07:32 Yeah. Nov 13 18:07:42 does it repartition entire lfash? Nov 13 18:07:54 I guess so. Nov 13 18:08:03 well OTA looks juicy Nov 13 18:08:07 i wonder what sits there Nov 13 18:08:13 @Akatsu . [well OTA looks juicy], I LMAO'd. Nov 13 18:08:26 get ota out resize recovery and move some MB from it to BOOT Nov 13 18:08:45 Yeah, I need atleast 5 MB to BOOT. Nov 13 18:08:48 10MB OTA is plenty Nov 13 18:09:27 you should ask some devs for what OTA is Nov 13 18:09:39 @Akatsu . [get ota out resize recovery and move some MB from it to BOOT], Ok, I understand you. Could you guide me, because I have absolutely no idea how to use fdisk. Nov 13 18:10:03 @Akatsu . [you should ask some devs for what OTA is], I think it is either where the OTA's are downloaded using stock rom and then it is installed into system or smth like that. Nov 13 18:10:10 for now i don;t really know if we could take ota out, maybe some devs will know but i dont really know any Nov 13 18:10:21 10MB is bit too low for ota Nov 13 18:10:36 i remember back in time sony had FOTA where we placed recoveries Nov 13 18:10:41 @Akatsu . [10MB is bit too low for ota], Now that you said it, then I agree. Let me gOoGlE. Nov 13 18:11:41 https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565 Nov 13 18:11:50 it might be something usefull Nov 13 18:12:17 @Akatsu . [https://forum.xda-developers.com/android/general/info-android-device-partitions- …], i actually just visited this website. Nov 13 18:13:01 @Akatsu . [https://forum.xda-developers.com/android/general/info-android-device-partitions- …], Maybe it is a vendor partition? Nov 13 18:13:28 "VENDOR … This partition is replaced with a shortcut (symbolic link in fact) to /system/vendor directory. It contains system applications and libraries that do not have source code available on AOSP but added by vendors (OEM's). During normal operation, this partition is mounted read-only; its contents change only during an OTA update." Nov 13 18:13:44 vendor partition doesnt exist mostly before 8.1 Nov 13 18:13:50 Hm, ok. Nov 13 18:14:07 after Treble vendors started to create them Nov 13 18:14:56 "OTA, FOTA - OTA updates" Nov 13 18:15:11 Then why is it only 10 MB....? Nov 13 18:15:28 `MISC - also FOTA on older devices` Nov 13 18:15:32 look at this point Nov 13 18:15:39 its not for storing ota Nov 13 18:15:53 just for preparing phone to apply OTA Nov 13 18:15:53 But I don't have MISC. Nov 13 18:16:01 "also FOTA" Nov 13 18:16:04 @Akatsu . [MISC - also FOTA on older devices], I read that, but I assumed that it's not a case. Nov 13 18:16:07 OTA is on older Nov 13 18:16:10 FOTA on newer Nov 13 18:16:17 OTA, FOTA - OTA updates Nov 13 18:16:25 "It's a tiny partition used by recovery to communicate with bootloader store away some information about what it's doing in case the device is restarted while the OTA package is being applied. " Nov 13 18:16:34 Hm, "it's a TINY." Nov 13 18:16:38 It is 10 MB. Nov 13 18:16:43 Maybe it is FOTA indeed. Nov 13 18:16:49 so i see potential space Nov 13 18:17:07 do you have some kind of factory image which will contain all partitons? Nov 13 18:17:18 or you are able to dump all of them? Nov 13 18:17:37 @Akatsu . [do you have some kind of factory image which will contain all partitons?], I am not sure. Nov 13 18:17:46 @Akatsu . [or you are able to dump all of them?], I could try to dump them to a .pit file. Nov 13 18:17:56 thats what will we need to be 100% sure we are safe Nov 13 18:18:05 Ok, dump to .pit? Nov 13 18:18:13 if you can go ahead and dump Nov 13 18:18:18 Okay. Nov 13 18:18:27 you can ignore system and userdata tho Nov 13 18:18:43 these are big and can be flashed with normal zips from LOS Nov 13 18:18:56 Yeah, IK. Nov 13 18:19:05 one guy on Leeco telegram lost entire userdata by messing with treble repartition zip Nov 13 18:21:31 For some reason the partitions didn't dump to the .pit file but it spitted it on the terminal. Nov 13 18:21:56 (Document) https://irc.ubports.com/b81ypLz8.txt Nov 13 18:22:35 hmm Nov 13 18:22:48 isnt pit file only one which describe structure? Nov 13 18:22:58 I think so. Nov 13 18:23:13 maybe do it simple Nov 13 18:23:25 and use dd Nov 13 18:24:11 Then, could you guide me? Because I have no experience with these terminal-android tools. Nov 13 18:24:29 i have idea xD Nov 13 18:25:12 ? :) Nov 13 18:25:50 dd if=/dev/block/mmcblk0p10 of=/userdata/recovery.img Nov 13 18:25:58 dd if=/dev/block/mmcblk0p11 of=/userdata/ota.img Nov 13 18:26:21 and then copy these files from userdata to oc Nov 13 18:26:28 [Edit] and then copy these files from userdata to pc Nov 13 18:26:36 Yah, give me a moment. Nov 13 18:27:50 @Akatsu . [dd if=/dev/block/mmcblk0p10 of=/userdata/recovery.img], dd: can't open '/userdata/recovery.img': No such file or directory Nov 13 18:28:05 @Akatsu . [dd if=/dev/block/mmcblk0p11 of=/userdata/ota.img], dd: can't open '/userdata/ota.img': No such file or directory Nov 13 18:28:17 hmm Nov 13 18:28:20 wait Nov 13 18:28:24 maybe i messed Nov 13 18:28:38 is /userdata mounted? Nov 13 18:29:05 Yeah. Nov 13 18:29:09 or can you mount system in twrp and do of=/system instead? Nov 13 18:29:17 wait a bit pls Nov 13 18:29:22 Sure. Nov 13 18:30:35 dd if=/dev/block/mmcblk0p10 of=/system/recovery.img Nov 13 18:31:27 @Akatsu . [dd if=/dev/block/mmcblk0p10 of=/system/recovery.img], "~ # dd if=/dev/block/mmcblk0p10 of=/system/recovery.img … 20480+0 records in … 20480+0 records out … 10485760 bytes (10.0MB) copied, 0.149508 seconds, 66.9MB/s" Nov 13 18:31:35 perfecto Nov 13 18:31:37 Oh, yeah. Copy to my PC. Nov 13 18:31:39 we get dump Nov 13 18:31:47 well recovery is just twrp image Nov 13 18:31:53 Mhm! Nov 13 18:32:02 but better backup these most important Nov 13 18:32:07 Okay. Nov 13 18:32:18 you know how are these named rite? Nov 13 18:32:25 Ofc. Nov 13 18:33:46 it wont help with? Nov 13 18:33:57 if you going to resize then we want to have backup Nov 13 18:34:02 (Photo, 586x411) https://irc.ubports.com/IBQjYZ9J.png Nov 13 18:34:12 Well, okay. Nevermind, sorry. Nov 13 18:34:20 backup OTA partition too Nov 13 18:34:33 its mmcblk0p11 as you noticed Nov 13 18:35:06 dd if=/dev/block/mmcblk0p11 of=/system/ota.img Nov 13 18:35:07 ? Nov 13 18:35:14 y Nov 13 18:35:17 Okay. Nov 13 18:35:38 Okay, backup complete! Nov 13 18:37:13 https://linux.die.net/man/8/resize2fs Nov 13 18:37:21 this shoudl be there in twrp Nov 13 18:37:42 It is! Nov 13 18:37:45 So, now... Nov 13 18:37:48 I... Nov 13 18:37:58 Uhm, I. Nov 13 18:39:50 I shrink it with "resize2fs -M mmcblk0p11"? Nov 13 18:40:35 tbh im not realy aware how it works Nov 13 18:40:48 and have no idea how much free space is on OTA Nov 13 18:41:06 we could just format OTA and progress with it Nov 13 18:41:16 Ok, I will format OTA now. Nov 13 18:41:37 How do you format the OTA since it isn't in the wipe window? Nov 13 18:41:41 we have copy at the end Nov 13 18:42:01 by hand probably Nov 13 18:42:24 @Akatsu . [by hand probably], Well, obviously. 😆 But what commands/tools would be used? Nov 13 18:42:42 https://www.howtogeek.com/106873/how-to-use-fdisk-to-manage-partitions-on-linux/ Nov 13 18:43:41 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/s2-disk-storage-parted-resize-part Nov 13 18:45:51 tbh i feel lost now, i dont really have exp with this Nov 13 18:46:05 Okay, trying to follow the tutorial. Nov 13 18:46:42 "Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel … Building a new DOS disklabel. Changes will remain in memory only, … until you decide to write them. After that the previous content … won't be recoverable." Nov 13 18:46:56 That's "fdisk /dev/block/mmcblk0p11" Nov 13 18:47:13 you are fdisking on partition Nov 13 18:47:19 mmcblk0 instead Nov 13 18:47:26 p stands for partition Nov 13 18:48:22 ah maybe for now abandon it Nov 13 18:48:30 Wait. Nov 13 18:48:35 I think I got it, Nov 13 18:48:37 Wait. Nov 13 18:48:44 tomorrow i will look into your sources and try build image myself Nov 13 18:48:54 so maybe i will get it to lower size Nov 13 18:49:23 we have to get it to 8MB from what i see Nov 13 18:49:45 Yea. Nov 13 18:50:10 gianluparri03 was added by: gianluparri03 Nov 13 18:50:17 Hi guys! Nov 13 18:50:40 i'd like to install ubuntu touch in my lg magna, is it possible? Nov 13 18:52:10 Depends, does your device has kernel published on GitHub? Nov 13 18:52:17 MT6582 uh Nov 13 18:52:21 pretty hard Nov 13 18:53:17 @gianluparri03 also, there are docs :) http://docs.halium.org/en/latest/porting/first-steps.html Nov 13 18:53:31 @rudi9719 [@gianluparri03 also, there are docs :) http://docs.halium.org/en/latest/porting …], thanks Nov 13 18:54:51 PrinceRAMBHAKT was added by: PrinceRAMBHAKT Nov 13 18:55:00 @gianluparri03 [thanks], just a question. when you say "This will probably take a while as it downloads several GBs:", how many gb of data should i download? Nov 13 18:55:58 @gianluparri03 [just a question. when you say "This will probably take a while as it downloads s …], (http://docs.halium.org/en/latest/porting/get-sources.html#initialize-and-download-source-tree) Nov 13 19:01:41 At least 20GB iirc Nov 13 19:17:57 ok, i can't do it with ubuntu live so Nov 13 19:18:28 Are you joking, every developer needs a Linux distro installed on their SSD/HDD not a Live USB. Nov 13 19:18:39 Didn't mean to be rude or offensive. Nov 13 19:22:27 @rixchy especially developing for Linux, you should be running a Linux Distro or at the very least a VM Nov 13 19:22:29 could be done under windows/mac too i guess Nov 13 19:22:53 @dohbee [could be done under windows/mac too i guess], On Windows it is possible, but is a lot harder if you use Cygwin for example. Nov 13 19:23:17 but yes, you're not likely to be doing a successful android device port from an ubuntu live iso Nov 13 19:23:36 @rudi9719 [@rixchy especially developing for Linux, you should be running a Linux Distro or …], VM would be great, if you have alot of RAM. I have only 4 GB, and the build would lag alot on a VM, but on the installed system it is pretty fast. Nov 13 19:23:43 @dohbee [but yes, you're not likely to be doing a successful android device port from an …], I agree. Nov 13 19:23:59 @rixchy [On Windows it is possible, but is a lot harder if you use Cygwin for example.], you can use WSL but android has its own compiler and stuff anyway Nov 13 19:24:18 @rudi9719 [Depends, does your device has kernel published on GitHub?], Ok , can I use Android 8 kernel for build newer version of halium Nov 13 19:24:27 @dohbee [could be done under windows/mac too i guess], And about Macs, I think Macs have alot of different commands from Linux, so it would be harder because the commands from docs and commands in macs would differentiate. Nov 13 19:24:32 @dohbee [you can use WSL but android has its own compiler and stuff anyway], Yeah. Nov 13 19:24:53 @rixchy You can compile a lot of GNU tools that Linux uses (or brew them if you don't want to compile) on macOS Nov 13 19:24:58 @rixchy [And about Macs, I think Macs have alot of different commands from Linux, so it w …], i mean, android development is supported on all three, so it's not a huge problem if one wants to use them instead of linux Nov 13 19:25:01 @PrinceRAMBHAKT [Ok , can I use Android 8 kernel for build newer version of halium], Halium-8.1 isn't stable, so it isn't recommeded. Nov 13 19:26:02 @dohbee [i mean, android development is supported on all three, so it's not a huge proble …], Well, yeah. But it's just.. harder on other platforms, since docs are based off Linux commands. Nov 13 19:26:10 sure Nov 13 19:26:28 App development is supported across all 3, but is kernel dev supported across all 3? Nov 13 19:26:36 but we can improve our docs to make it easier Nov 13 19:27:07 @dohbee [but we can improve our docs to make it easier], Well, yeah. But it would take alot of time. Nov 13 19:27:26 @rudi9719 [App development is supported across all 3, but is kernel dev supported across al …], I think so, just different commands, I guess. Nov 13 19:27:46 mostly the same commands, except for installing specific needed software Nov 13 19:29:16 Also that, indeed. Nov 13 19:32:55 Halium sources are like 4GB Nov 13 19:33:09 device tree+kernel+vendor sumarize at max 1GB Nov 13 19:54:48 Hi , I'm trying to port to samsung note 3 with a kernel 3.4 in the docs it says "halium currently requires a device with kernel >=3.10" but then it says ubuntu touch uses older kernel 3.4 what i wanna know is can i port with kernel 3.4 ? Nov 13 19:56:16 for UBPorts it is still possible, but will require more kernel patches Nov 13 19:57:53 I see , i have the halium sources ready can i build the required images and boot the rootfs or will i need to patch directly to the krenel sources ? Nov 13 20:27:23 you will most llikely encounter errors during kernel build Nov 13 20:41:28 @x [Hi , I'm trying to port to samsung note 3 with a kernel 3.4 in the docs it says …], DW. I have kernel 3.4, tho I haven't heard of this error message before... Nov 13 20:41:40 @x [Hi , I'm trying to port to samsung note 3 with a kernel 3.4 in the docs it says …], [Edit] I have kernel 3.4, tho I haven't heard of this error message before... Nov 13 21:55:21 If I wanted to update my 3.0.101 kernel source to 3.1+, would I only need to cherry pick the changes from torvalds linux? Or is there something more involved required? Nov 13 21:57:37 @Qiangong2 [If I wanted to update my 3.0.101 kernel source to 3.1+, would I only need to che …], if you are required to use binary blob drivers for hardware that are built against 3.0.101, it's probable they would break when using a newer kernel. if you're not using binary blobs, then it'd probably be better to use 5.3 or 5.4 kernel if pos Nov 13 21:57:37 sible Nov 13 21:58:04 but you're trying to do something on tizen i guess? Nov 13 21:59:00 @dohbee [but you're trying to do something on tizen i guess?], Yeah, eventually. Either my tizen devices or an older android. The tizen devices are on 3.10.65, and the older android on 3.0.101 Nov 13 21:59:40 @Qiangong2 [Yeah, eventually. Either my tizen devices or an older android. The tizen devices …], that's a pretty big difference. what is it using for drivers? Nov 13 22:00:51 They aren't the same device if you're asking. The Z2, Z4, and galaxy star pro are the three I want to work on Nov 13 22:01:26 All three are spreadtrum, but I believe the Z2 and Z4 uses video drivers from the tizen source tree Nov 13 22:02:33 The Z2 source we've gotten up to 3.11.1 already Nov 13 22:02:40 you could try using a newer android kernel for the android device i guess, but if it has binary blobs for drivers, it'll probably break Nov 13 22:03:05 if tizen devices are using all open source drivers, you can probably get latest upstream working on it Nov 13 22:03:18 Mali blobs for GPU for sure Nov 13 22:03:28 though it could probably work with Lima now Nov 13 22:04:04 right, especially if it's older mali Nov 13 22:04:26 I'd really just like to upgrade the Z2 to 3.18 or higher if possible Nov 13 22:04:58 The Z4 uses pretty much the exact same source too, just different camera and digitizer drivers Nov 14 00:06:37 nachodorito was added by: nachodorito Nov 14 00:07:10 Question, it is required to use specifically LOS 12.1/14.1? Nov 14 00:16:34 Uh if those are equivalent to andriod 5.1_and 7.1 yes it is afaik Nov 14 00:16:45 [Edit] Uh if those are equivalent to andriod 5.1 and 7.1 yes it is afaik Nov 14 02:08:02 Christina was added by: Christina **** ENDING LOGGING AT Thu Nov 14 02:59:58 2019