| r0kk3rz | liux: push your stuff to github, its a lot easier for us to help you if we can see exactly what you're doing | 01:44 |
|---|---|---|
| r0kk3rz | its also useful to have a public record of what fixes you've done | 01:45 |
| T42 | <austenite> udev_contexts | 03:00 |
| asriel[m] | ah, forgot to register a freenode account, by the way. | 04:03 |
| asriel[m] | can anyone tell me about 4.1 from the HADK? I only followed 4.2 | 04:03 |
| * asriel[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/dNfganDUTJikDcTbfbqtURMy > | 04:14 | |
| liux | r0kk3rz, ok, i'll do that later | 04:18 |
| asriel[m] | Weird, adaptation0 repo URL is password-protected. Not sure why that is. | 04:21 |
| liux | Regarding camera issue, i want to apply the patch: https://github.com/mer-hybris/android_system_core/commit/3456e019173b426927baf606d7b817d6ffdb7fdd, but how to build libstagefright_omx.so in hadk and install it to /usr/libexec/droid-hybris/system/lib? | 04:24 |
| Nokius | asriel[m]: then your repo is wrong | 06:51 |
| Nokius | liux: did you check the logs channel logs? | 06:52 |
| Nokius | sledges: Hope your summer is bad ass ;) could we get targets for dont be evel aka pinephone please? Thanks in advance <3 | 06:53 |
| asriel[m] | Nokius: Huh, that's weird, it's a fresh installation of HADK, The guide I used to install the SDK was from the wiki: https://sailfishos.org/wiki/Platform_SDK_Installation | 06:57 |
| deathmist | morning :) SFOS 3.1 brings support for fingerprint authentication to the Xperia XA2 https://together.jolla.com/question/208530/release-notes-310-seitseminen/ how possible would this be to implement for other community ported devices w/ FP sensors? | 06:59 |
| T42 | <elros34> asriel[m]: ignore adaptation0 error | 06:59 |
| r0kk3rz | deathmist: not sure if all the parts are open for that | 08:23 |
| deathmist | r.i.p, I hope they open it up at some point then, well see tho :) when should we expect build targets to drop for 3.1? | 08:26 |
| r0kk3rz | week or so | 08:26 |
| deathmist | awesome! can't wait for the update already | 08:43 |
| T42 | <Harsh18262> Guys I have made hybirs hal boot and recovery and all errors and most of the warnings fixed but then to the device is not booting it just keep bootlooping | 08:52 |
| T42 | <Harsh18262> I have already added audit=n in defconfig | 08:52 |
| T42 | <Harsh18262> And is there any difference androidboot.selinux=permissive and selinux=0 | 08:53 |
| vknecht | if you miss selinux=0 and the bootparam CONFIG setting, that's probably it. don't mod audit unless you really have to | 08:55 |
| T42 | <Harsh18262> Ok and I am using androidboot.selinux=permissive can that make a difference from using selinux=0 | 08:56 |
| T42 | <Harsh18262> In cmdline | 08:56 |
| vknecht | sfos doesn't care about permissive/enforce once you've set selinux=0 | 08:57 |
| T42 | <Harsh18262> @vknecht [sfos doesn't care about permissive/enforce onc …], Ok | 08:57 |
| T42 | <elros34> @Harsh18262 I thought you already understand that config_vt cause bootloop for your kernel so why did you enable it again? | 09:04 |
| T42 | <Harsh18262> The device kept bootlooping even after disabling config_vt | 09:05 |
| r0kk3rz | i think config_vt is needed anyway | 09:05 |
| T42 | <Harsh18262> So from now should a keep it enabled or disabled I am going to try to turn audit back on and enable bootparam in defconfig and add selinux=0 in cmdline instead of androidboot.selinux=0 | 09:07 |
| * asriel[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/JBPKyrcPOnzvJFifdTEpLoav > | 09:09 | |
| asriel[m] | Do I have to uh, set a keyserver and recv it? | 09:09 |
| T42 | <elros34> @Harsh18262 so how did you fix bootloop earlier? | 09:09 |
| r0kk3rz | what device? | 09:11 |
| T42 | <Harsh18262> To the same stage I am right | 09:11 |
| T42 | <Harsh18262> Right now my device keep bootlooping and can only get to telnet when I flash a custom kernel after flashing hybris-boot that to on port 23 | 09:12 |
| vknecht | asriel[m], try with --no-repo-verify | 09:14 |
| T42 | <elros34> so stick to working kernel, telnet to it and grab /init.log | 09:16 |
| T42 | <Harsh18262> Ok | 09:24 |
| foobar2018 | hi | 09:25 |
| foobar2018 | I would like to help porting sailfish to other devices | 09:26 |
| foobar2018 | but I dont know how to do it. What should I start learning? Please I need your expertise. | 09:26 |
| r0kk3rz | you want to help, or you would like help? | 09:26 |
| r0kk3rz | do you have a device to port to? | 09:27 |
| foobar2018 | r0kk3rz: I would like to help | 09:27 |
| foobar2018 | I have some here but I don't know if they're useful. | 09:27 |
| foobar2018 | To learn at least. | 09:28 |
| r0kk3rz | pick one | 09:28 |
| foobar2018 | r0kk3rz: what's next | 09:28 |
| r0kk3rz | well.. what is it? | 09:29 |
| foobar2018 | Here I have an Lenovo A1000L tablet and a Nook Simple Touch | 09:29 |
| asriel[m] | According to HADK, as long if it uses CM 10.1 -> Lineage 15.1 then it's good to do the port on. :P | 09:30 |
| r0kk3rz | the lenovo is probably a better target to start with | 09:31 |
| r0kk3rz | then you need to follow the HADK | 09:32 |
| T42 | <MarcoDS_bit> Hi, trying (again) to port sailfish, hybris-15.1. compiled and installed succesfully but it just freeze while booting: https://paste.ubuntu.com/p/DQrFybRKqX/ | 09:33 |
| foobar2018 | r0kk3rz: Ok, Ill go with this lenovo tablet | 09:34 |
| T42 | <MarcoDS_bit> Thought about audit but last time it at least booted without ui with the same audit config | 09:34 |
| T42 | <elros34> @MarcoDS_bit you did not disable selinux, also you are missing autofs in defconfig | 09:37 |
| foobar2018 | asriel[m]: what happens if it's not supported by that? | 09:38 |
| r0kk3rz | then it becomes harder, what is it supported by? is there a thirdparty rom for it? | 09:38 |
| asriel[m] | Then make sure check for third party roms, there are unofficial LineageOS for devices like that as far I know of | 09:40 |
| asriel[m] | I don't know if kernel version is a requirement, but Halium needs at least kernel >= 3.13 | 09:40 |
| foobar2018 | r0kk3rz: How do I figure out that? | 09:41 |
| r0kk3rz | well, you find a rom for it | 09:41 |
| foobar2018 | r0kk3rz: I found one | 09:43 |
| r0kk3rz | what is it? | 09:44 |
| T42 | <MarcoDS_bit> @elros34 actually selinux is set to 0 in BOARD_KERNEL_CMDLINE | 09:44 |
| foobar2018 | r0kk3rz: it seems it comes from a russian lenovo forum, it's called " | 09:46 |
| foobar2018 | A1000F_AllegroROM_v0.3_11102013 | 09:46 |
| foobar2018 | " | 09:46 |
| T42 | <elros34> @MarcoDS_bit not really, look at command line in your logs | 09:47 |
| T42 | <MarcoDS_bit> Just was it ouch, thank you @elros34 | 09:50 |
| *** foobar2019 is now known as foobar201919 | 09:53 | |
| foobar201919 | hi again, i got disconnecte | 09:53 |
| foobar201919 | d | 09:53 |
| foobar201919 | r0kk3rz: I found a custom rom, but i dunno if it's enough | 09:54 |
| r0kk3rz | does it work? is all the source available? | 09:54 |
| foobar201919 | r0kk3rz: It's called "AllegroRom" but I cant find any sources | 09:56 |
| r0kk3rz | then its no good | 09:57 |
| foobar201919 | I see | 10:00 |
| foobar201919 | So I should first learn how to port CM/LineageOS to this device? | 10:01 |
| r0kk3rz | sure | 10:01 |
| foobar201919 | thank you | 10:09 |
| T42 | <adampigg> Anyone done an inline update to 3.1 without rebuilding? | 11:40 |
| deathmist | adampigg: I tried via cmdline w/ ssu release & version --dup, ended up with a broken mess and no telnet (which I expected :p) | 11:44 |
| T42 | <adampigg> Oh dear, i wont try it on my 5hr train journey then ! | 11:46 |
| T42 | <adampigg> I hear there is ui changes, whats it like? | 11:46 |
| deathmist | https://youtu.be/pr4UJXCjMyk should showcase some of it :) I already like it a lot | 11:47 |
| T42 | <Harsh18262> a new update on device now after turning of vt and enabling bootparam the device get stuck on asus logo and turns telnet just for 2-5 secs | 11:54 |
| T42 | <Harsh18262> i also wanted to know that what to do to all warnings related to systemd should i enable it or not | 11:55 |
| deathmist | @Harsh18262 I enabled practially everything (you can research options to make educated decisions) | 12:01 |
| T42 | <Harsh18262> @deathmist did enabling everything worked? | 12:01 |
| deathmist | I never booted without everything already set :p read the descriptions, I remember one of them saying it's required for libhybris even tho it's optional | 12:03 |
| deathmist | then mka hybris-boot, flash new image and check | 12:03 |
| T42 | <Harsh18262> i enabled that | 12:03 |
| T42 | <Harsh18262> ok will try after enabling everything | 12:04 |
| deathmist | which telnet also, port 23 or 2323? if 23 then try to cat /init.log quick so you could see what's possibly wrong | 12:06 |
| liux | Nokius, yes. but I just want to know what is proper way to built out libstagefright_omx.so and libmedia.so and install them to device | 12:08 |
| electro575 | hi all | 12:31 |
| electro575 | can you help me with this different name ? | 12:48 |
| electro575 | https://dpaste.de/TfYF | 12:48 |
| electro575 | @DEVICE : hammerhead | 12:48 |
| electro575 | @VENDOR : lge | 12:48 |
| electro575 | @DEVICE_PRETTY : Nexus 5 | 12:48 |
| electro575 | @VENDOR_PRETTY : LG | 12:49 |
| electro575 | me i have | 12:49 |
| electro575 | @DEVICE : t0lte | 12:49 |
| electro575 | @VENDOR : samsung | 12:49 |
| electro575 | @DEVICE_PRETTY : ? | 12:49 |
| electro575 | @VENDOR_PRETTY : ? | 12:49 |
| T42 | <austenite> pretty is how you want it to look in device info in settings | 12:50 |
| deathmist | electro575: https://wiki.lineageos.org/devices/t0lte indicates vendor: Samsung device: Galaxy Note 2 (LTE) | 12:50 |
| electro575 | why @VENDOR_PRETTY ? | 12:50 |
| deathmist | those are the pretty entries for vendor & device you should use that I just listed | 12:51 |
| electro575 | ok thk | 12:52 |
| electro575 | git push jo master | 13:10 |
| electro575 | fatal: 'jo' does not appear to be a git repository | 13:10 |
| deathmist | is "jo" your github user? you have to create an empty repo for the droid hal stuff you push to manually | 13:11 |
| deathmist | https://github.com/new you'll have to do that 3 times too: repo for "droid-hal-t0lte", "droid-config-t0lte" & "droid-hal-version-t0lte" | 13:13 |
| T42 | <austenite> do i need to port ff memless haptiics for vibration feedback with onscreen keyboard ? | 13:20 |
| T42 | <austenite> native vibrator feedback is very low | 13:20 |
| deathmist | austenite: it's low for on-screen keyboard key presses? it shouldn't be strong at all, just enough to know it activated. I think you can tweak it, I don't have the knowledge myself tho | 13:21 |
| electro575 | no, it's not my account | 13:26 |
| deathmist | electro575: then you are doing it wrong, it should be "git push [YourGitHubUsername] master", you'll have to re-add the remote again too with the proper username | 13:27 |
| T42 | <austenite> deathmist on-screen keyboard is absent ;p, only long press and periodic theme effects are working | 13:30 |
| electro575 | it's a lot of command to arrived at the end with a sailfishOS :) | 13:45 |
| T42 | <Harsh18262> @deathmist i enable everything but now telnet is also not available | 13:48 |
| deathmist | Harsh18262: well obviously don't literally enable everything, some of them need to be unset for stuff to work (had to figure out a few random options myself to get telnet working at all), you can probably undo the changes. you still didn't check init log when you could telnet in to see what was wrong? | 13:50 |
| superprower | Hi! It may be a bit off-topic, but I'm currently working with sensorfw and trying to verify that my device config is correct. Is there any command line utility that could talk to sensorfwd and query it about, for example, luminosity sensor? | 13:52 |
| T42 | <Harsh18262> @deathmist \last time when the device was going to telnet for 2-5 secs at that the telnet server was not able to establish and before that to start telnet i had to install a custom kernel which would edit a boot img so will that log be genuine or useful? | 13:53 |
| deathmist | superprower: check systemctl status sensorfwd, it should list errors and more in journalctl, if all looks good and you have Jolla Store available, check them with AIDA64. display auto-brightness setting should also be available when ALS (ambient light sensor) works for example | 13:55 |
| deathmist | Harsh18262: so you never got telnet on hybris-boot kernel? | 13:56 |
| T42 | <Harsh18262> nope | 13:56 |
| superprower | deathmist: display and such is currently WIP, that's why I'm looking into command-line utilities or at least something with open source code so that I could replicate it in similar application | 14:00 |
| deathmist | superprower: in that case I'd worry about sensors a bit later ;) test_sensors should list some stuff. also are you booted using hybris-boot image? I made the mistake of booting w/ hybris-recovery and after switching I got UI :p | 14:05 |
| electro575 | can you helpl me with github ? | 14:05 |
| electro575 | https://dpaste.de/aRR0 | 14:05 |
| electro575 | i have enter my correct name | 14:06 |
| deathmist | electro575: you still haven't made the 3 empty repositories on GitHub on that account like I told you to do before | 14:06 |
| electro575 | i must create a new repositorie in my account github to git push | 14:06 |
| electro575 | no, ok i do | 14:07 |
| electro575 | i have created 3 empty repositories | 14:10 |
| electro575 | but don't arrive to push | 14:10 |
| superprower | deathmist: It's complicated, so please don't bother with the details. What package contains test_sensors? | 14:10 |
| electro575 | it's ok for me | 14:12 |
| deathmist | superprower: I'd say "pattern:sailfish-porter-tools" under jolla-configuration-*.yaml under your dcd patterns, but I honestly have no clue, mal? | 14:12 |
| T42 | <elros34> electro575: libhybris-tests | 14:13 |
| T42 | <elros34> sorry I mean superpower | 14:15 |
| superprower | Thanks | 14:16 |
| mal | superprower: related to sensors, did you add the configuration file as described in faq? | 14:19 |
| mal | superprower: which device and android base? | 14:22 |
| superprower | mal: don't bother, it's outside of regular adaptation process. | 14:25 |
| mal | what do you mean? | 14:28 |
| T42 | <adampigg> Mal, any way to ping lbt other than here? (for patternizing) | 14:31 |
| electro575 | i have do mistake | 14:31 |
| electro575 | forget replace myname with git command | 14:32 |
| electro575 | now : fatal: repository 'https://github.com/myname/droid-hal-version-hammerhead.git/' not found | 14:32 |
| mal | superprower: you do know that different android bases need different changes so knowing which android version is used as base is quite important if you expect someone to help you | 14:34 |
| electro575 | it's okey | 14:35 |
| superprower | mal: I'm not doing regular adaptation process for an android-based device, that's why I said that it could be an off-topic. | 14:39 |
| mal | superprower: I don't understand what that mean in this context, test_sensors is useful only on normal android base ports | 14:41 |
| mal | there are only two options for porting, android based and native linux porting | 14:42 |
| superprower | mal: yes, I understand that (now). | 14:42 |
| electro575 | can i help me for this sentence ? | 14:55 |
| electro575 | Once all these 3 repositories get upstreamed under https://github.com/mer-hybris create PR into an appropriate | 14:55 |
| electro575 | branch of the file .repo/local_manifests/hammerhead.xml to the https://github.com/mer-hybris/local_manifests repository. | 14:55 |
| mal | most people haven't moved their repos to mer-hybris | 14:56 |
| electro575 | ok | 14:56 |
| electro5751 | error when i launch this cmd : rpm/dhd/helpers/build_packages.sh | 15:12 |
| electro5751 | https://dpaste.de/fDAs#L1 | 15:12 |
| electro5751 | warning need to be fix ? | 15:14 |
| electro5751 | mal ? deathmist ? An idea | 15:14 |
| electro5751 | error must be fix as | 15:15 |
| electro5751 | vi ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 15:15 |
| T42 | <Harsh18262> check the log | 15:16 |
| mal | electro5751: you DO NOT edit out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 15:17 |
| mal | that is the file generated by build, not the one used in build | 15:18 |
| mal | electro5751: also show full log that is mentioned at the end of that paste you gave | 15:18 |
| electro5751 | https://dpaste.de/yuFb | 15:19 |
| electro5751 | ok | 15:19 |
| deathmist | electro5751: YOU need to use mer_config_checker and set the values as it says, you seem to have done nothing so far (check your defconfig e.g. lineage_t0lte_defconfig) | 15:20 |
| electro5751 | hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/t0lte/obj/KERNEL_OBJ/.config | 15:21 |
| electro5751 | ? | 15:21 |
| mal | electro5751: edit the lineage_t0lte_defconfig based on the errors you see in the log you just gave | 15:21 |
| electro5751 | ok thk | 15:22 |
| mal | the errors are the critical ones, also set CONFIG_SECURITY_SELINUX_BOOTPARAM=y and keep CONFIG_AUDIT=y | 15:22 |
| liux | I'm blocked by camera freezes when pressing to recod video, on cm-12.1. I've patched frameworks/av just as i've done on cm-11.0, but it seems more errors on cm-12.1. The logcat log was pasted here: https://paste.ubuntu.com/p/t696RYCyn3/ | 15:23 |
| electro5751 | i launch find cmd for lineage_t0lte_defconfig | 15:23 |
| electro5751 | nothing file have this name | 15:23 |
| mal | that is in kernel repo | 15:23 |
| mal | somewhere under $ANDROID_ROOT/kernel/ | 15:24 |
| deathmist | I checked logs, it seems to be at kernel/samsung/smdk4412/arch/arm/configs/lineageos_t0lte_defconfig | 15:24 |
| mal | that one | 15:24 |
| electro5751 | thk | 15:24 |
| liux | abranson, please help when you have time | 15:25 |
| mal | are you sure you reverted the things correctly? | 15:27 |
| deathmist | electro5751: you'll most likely have to do this https://git.io/fjMka to device/samsung/t0lte/BoardCommonConfig.mk (build a new hybris-boot image afterwards) | 15:34 |
| electro5751 | sorry, no same lines as my file | 15:40 |
| electro5751 | https://dpaste.de/mJaQ | 15:40 |
| electro5751 | no line, BOARD_KERNEL_CMDLINE | 15:40 |
| electro5751 | i'm here : 7.2.1 Building the droid-hal-device packages | 15:43 |
| electro5751 | in the guidline | 15:43 |
| electro5751 | guide sorry | 15:43 |
| mal | electro5751: did you rebuild kernel after the defconfig changes? | 15:46 |
| electro5751 | humm, no i suppose | 15:46 |
| electro5751 | humm, yes sorry | 15:46 |
| electro5751 | but i have same error | 15:46 |
| electro5751 | that i pasted | 15:47 |
| mal | of course the kernel defconfig changes are only used if you run make hybris-hal or make hybris-boot in HABUILD_SDK | 15:48 |
| electro5751 | o Okey | 15:48 |
| electro5751 | so, go | 15:48 |
| electro5751 | make hybris-hal ? i have never do that | 15:51 |
| electro5751 | but make hybris-recovery | 15:51 |
| electro5751 | and make hybris-boot | 15:52 |
| mal | electro5751: yes you did in chapter 5.4 | 15:52 |
| electro5751 | ok | 15:54 |
| T42 | <austenite> mal, is ff memless haptics is required for controlling vibrator intensity? keyboard haptic feedback is not working | 15:54 |
| mal | @austenite no, keyboard haptics work fine without memless, sometimes keyboard feedback needs some configuration to make it observable | 15:59 |
| mal | like this https://github.com/mer-hybris/droid-config-sony-nile/commit/6c2a331b8778a76cfe1f86d26f0f36565c0a83c2 | 15:59 |
| mal | most devices don't support controlling the intensity, only duration like is done in that config | 16:00 |
| T42 | <austenite> thanks mal | 16:08 |
| electro5751 | i don't have this file | 16:12 |
| electro5751 | DEFCONFIG=arch/arm/configs/cyanogenmod_hammerhead_defconfig | 16:12 |
| electro5751 | with this | 16:13 |
| electro5751 | HABUILD_SDK [t0lte] sailfish-dev@jopcportable:~/hadk/kernel/samsung/smdk4412 | 16:13 |
| mal | electro5751: come on, use your brain, your file is lineageos_t0lte_defconfig | 16:14 |
| mal | anything with hammerhead in hadk pdf is an example | 16:15 |
| electro5751 | o No, i have done this cmd so no file | 16:15 |
| electro5751 | yes | 16:15 |
| mal | what command? | 16:15 |
| electro5751 | make -j$(nproc --all) hybris-hal | 16:15 |
| electro5751 | i have erase all file ? | 16:15 |
| mal | NOOOOOOOO | 16:15 |
| mal | you just run the commands in chapter 5.4 | 16:16 |
| mal | assuming you have fixed the defconfig alreafdy | 16:16 |
| electro5751 | i have launched make hybris-boot && make hybris-recovery | 16:17 |
| mal | electro5751: why? | 16:18 |
| mal | are you sure you at some point ran make hybris-hal? | 16:18 |
| electro5751 | of course the kernel defconfig changes are only used if you run make hybris-hal or make hybris-boot in HABUILD_SDK | 16:19 |
| electro5751 | beucause of that | 16:19 |
| electro5751 | i have done this cmd | 16:19 |
| electro5751 | source build/envsetup.sh | 16:19 |
| electro5751 | export USE_CCACHE=1 | 16:19 |
| electro5751 | breakfast $DEVICE | 16:19 |
| electro5751 | make -j$(nproc --all) hybris-hal | 16:19 |
| electro5751 | cd $ANDROID_ROOT | 16:19 |
| electro5751 | hybris/mer-kernel-check/mer_verify_kernel_config \ | 16:19 |
| electro5751 | ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:19 |
| electro5751 | make hybris-boot | 16:19 |
| electro5751 | make hybris-recovery | 16:19 |
| electro5751 | that's all | 16:19 |
| electro5751 | and i do that chapter | 16:20 |
| electro5751 | Contribute your mods back | 16:20 |
| electro5751 | because i don't have tape this | 16:20 |
| mal | do not paste so many lines | 16:20 |
| electro5751 | sorry | 16:20 |
| mal | make hybris-hal includes both make hybris-boot and make hybris-recovery | 16:21 |
| mal | did you edit the defconfig file to fix the errors? | 16:21 |
| electro5751 | yes | 16:22 |
| electro5751 | so, just do this cmd | 16:22 |
| electro5751 | make -j$(nproc --all) hybris-hal | 16:22 |
| electro5751 | but error appear again | 16:23 |
| mal | are you sure you fixed correct defconfig | 16:24 |
| mal | show what you did, go to kernel/samsung/smdk4412 and show output of "git diff" | 16:24 |
| piggz | mal: whats this, not seen it before? https://github.com/mer-hybris/droid-config-sony-nile/blob/master/patterns/jolla-hw-adaptation-pioneer.yaml#L36 | 16:25 |
| mal | piggz: that is some ancient fix from 4 years ago | 16:26 |
| piggz | ok | 16:26 |
| mal | https://github.com/mer-hybris/droid-hal-configs/commit/d8272589ccf5a10d5210a5e299e30356e2818373 | 16:26 |
| electro5751 | mal, https://dpaste.de/9sVy | 16:28 |
| mal | electro5751: what is that supposed to be? | 16:28 |
| electro5751 | once i launched make -j$(nproc --all) hybris-hal then i check with this cmd ? | 16:28 |
| electro5751 | hybris/mer-kernel-check/mer_verify_kernel_config \ ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:28 |
| mal | go to kernel/samsung/smdk4412 and show output of "git diff" | 16:28 |
| electro5751 | ok | 16:29 |
| electro5751 | https://dpaste.de/eCPp | 16:30 |
| mal | electro5751: so what error are you talking about | 16:31 |
| electro5751 | and after verifying -> https://dpaste.de/NzAU | 16:31 |
| electro5751 | during make hybrid-hal -> error with defconfig i suppose, no ? https://dpaste.de/9sVy | 16:32 |
| mal | electro5751: was the make hybris-hal or hybris-boot build successful, you only show a small part of the log | 16:33 |
| electro5751 | yes, but after modifying the file ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:33 |
| electro5751 | before do make hybrid-boot | 16:33 |
| electro5751 | and make hybrid-recovery | 16:34 |
| mal | electro5751: what? you edited out/target/product/$DEVICE/obj/KERNEL_OBJ/.config ?????? | 16:34 |
| electro5751 | what command is necessary : make -j$(nproc --all) hybris-hal , make hybrid-boot or make hybrid-recovery | 16:34 |
| electro5751 | yes, ... | 16:34 |
| mal | 18:17 < mal> electro5751: you DO NOT edit out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:34 |
| electro5751 | but erase after make | 16:35 |
| electro5751 | okey | 16:35 |
| electro5751 | but now | 16:35 |
| electro5751 | after make hybris-hal | 16:35 |
| electro5751 | i do this command | 16:35 |
| mal | you are still not showing complete build log | 16:35 |
| electro5751 | hybris/mer-kernel-check/mer_verify_kernel_config \ ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:35 |
| electro5751 | complete build log | 16:35 |
| mal | SHOW THE DAMN FULL BUILD LOG or I will not help you anymore | 16:35 |
| electro5751 | for make hybris-hal ? | 16:36 |
| mal | yes | 16:36 |
| electro5751 | i give it to you | 16:36 |
| electro5751 | sorry, ... | 16:36 |
| mal | I have told so many times on this channel to not try to guess where to relevant part of the log is but instead always give full logs | 16:36 |
| electro5751 | https://dpaste.de/XCDv | 16:39 |
| electro5751 | full log for you, thanks | 16:39 |
| mal | now show output of hybris/mer-kernel-check/mer_verify_kernel_config \ ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:41 |
| mal | remove that \ from the command just in case | 16:41 |
| mal | so hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:41 |
| mal | electro5751: wait, where in the defconfig did you add your changes? those should be added to the end of the file | 16:42 |
| electro5751 | where, i don't know exactly | 16:43 |
| electro5751 | i'm looking | 16:43 |
| mal | the diff you gave suggests you added the changes to quite near the beginning of the defconfig file | 16:44 |
| electro5751 | humm, after the first | 16:44 |
| mal | move the changes you did to the end of the file and then run make hybris-hal again | 16:45 |
| electro5751 | yes, after CONFIG_IRQ_WORK | 16:45 |
| electro5751 | ok | 16:45 |
| mal | electro5751: the file is processed in order, so if you add something to the beginning it might be overridden later in the file | 16:45 |
| electro5751 | exactly | 16:46 |
| electro5751 | it's done | 16:47 |
| electro5751 | make working | 16:47 |
| electro5751 | i must install : module-init-tools | 16:48 |
| electro5751 | how ? | 16:48 |
| mal | ? | 16:48 |
| mal | what are you talking about | 16:49 |
| electro5751 | DEPMOD 3.0.101-lineage-gb7ffe7f2aea-dirty | 16:49 |
| electro5751 | Warning: you may need to install module-init-tools | 16:49 |
| electro5751 | i pasted you the full log after | 16:49 |
| mal | I think that is fine | 16:49 |
| electro5751 | the make hybris-all is more longer | 16:51 |
| electro5751 | i'm waiting for finish | 16:51 |
| electro5751 | it's necessary after make hybris-hal to do make hybris-boot and make hybris-recovery ? | 16:55 |
| mal | no | 16:55 |
| mal | I said already earlier that hybris-hal includes hybris-boot and hybris-recovery | 16:56 |
| electro5751 | yes | 16:56 |
| electro5751 | https://dpaste.de/01zW | 16:56 |
| electro5751 | it's my full log | 16:56 |
| electro5751 | with terminal, but not the FULL | 16:57 |
| electro5751 | more object have compiled | 16:57 |
| electro5751 | it's more good i suppose | 16:57 |
| T42 | <elros34> does this device use 3.0.101 kernel? | 16:57 |
| mal | of course more things were build since now the kernel config changes were different | 16:57 |
| electro5751 | ok | 16:58 |
| electro5751 | i can continue now ? | 16:58 |
| mal | check the hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 16:59 |
| mal | if no errors then probably ok | 16:59 |
| electro5751 | https://dpaste.de/dCNm | 16:59 |
| electro5751 | some error appear | 16:59 |
| mal | one error | 16:59 |
| electro5751 | modify defconfig ? | 16:59 |
| mal | add CONFIG_IKCONFIG=y before CONFIG_IKCONFIG_PROC=y | 17:00 |
| electro5751 | ok | 17:01 |
| electro5751 | done | 17:01 |
| electro5751 | i remake | 17:01 |
| mal | just to be sure, both should be on their own lines | 17:03 |
| electro5751 | https://dpaste.de/VKdB | 17:03 |
| electro5751 | yes | 17:03 |
| mal | looks reasonable | 17:03 |
| electro5751 | just warning so | 17:03 |
| electro5751 | can i continue ? | 17:03 |
| electro5751 | i re-edit my guide file .odt | 17:04 |
| mal | yes, some warnings are always left | 17:04 |
| electro5751 | do you think it's important ? | 17:05 |
| mal | like I just said, some warning are always seen, not all kernel support all configs | 17:07 |
| electro5751 | ok | 17:07 |
| electro5751 | thanks for your help | 17:07 |
| electro5751 | mal, i must create | 17:19 |
| electro5751 | <project path="kernel/lge/hammerhead" | 17:19 |
| electro5751 | name="CyanogenMod/android_kernel_lge_hammerhead" | 17:19 |
| electro5751 | revision="stable/cm-11.0-XNG3C" /> | 17:19 |
| electro5751 | but mine | 17:19 |
| electro5751 | it's possible ? | 17:20 |
| electro5751 | but actually, i have this manifest | 17:20 |
| electro5751 | https://dpaste.de/zhy8 | 17:20 |
| mal | electro5751: what are you talking about, you already did local manifest | 17:22 |
| T42 | <austenite> hammerhead is an example | 17:22 |
| mal | forget about the part about pushing those to github for now | 17:22 |
| electro5751 | wtf, my computer crash | 17:23 |
| electro5751 | i'm talking about : Contribute your mods back | 17:24 |
| electro5751 | it's ok | 17:26 |
| electro5751 | rpm/dhd/helpers/build_packages.sh -> GOOD | 17:26 |
| electro5751 | errors :/ https://dpaste.de/4tK0 | 17:27 |
| electro5751 | error dependencies at the end | 17:27 |
| electro5751 | mal, Package 'ssu-kickstart-configuration' not found. | 17:28 |
| T42 | <austenite> electro5751 its in hadk pdf | 17:29 |
| T42 | <austenite> section 8.3 | 17:29 |
| electro5751 | why it's after section 7 ? | 17:30 |
| electro5751 | what is really necessary in 8.2 | 17:31 |
| electro5751 | jolla-xt9 (predictive text input) : ye | 17:31 |
| electro5751 | yes | 17:31 |
| electro5751 | sailfish-eas (Microsoft Exchange support) : no for me i suppose ! | 17:31 |
| electro5751 | aliendalvik (AndroidTM Apps Support) : if you use android app | 17:31 |
| electro5751 | sailfish-maps : yes | 17:31 |
| T42 | <austenite> skip 8.2 is what you cannot build along with sailfish image | 17:32 |
| T42 | <austenite> its rules | 17:32 |
| electro5751 | yes | 17:32 |
| mal | electro5751: read in faq | 17:33 |
| mal | @austenite different issue | 17:33 |
| mal | this is an issue in droid-config repo, a known thing | 17:33 |
| electro5751 | i'm going to finish compilation | 17:35 |
| electro5751 | what i must do again ^^ | 17:36 |
| mal | just do what faq tells, line 692-> | 17:36 |
| electro5751 | https://dpaste.de/Na2x | 17:37 |
| electro5751 | thk | 17:37 |
| electro5751 | all build is ok | 17:41 |
| electro5751 | https://dpaste.de/S7mr | 17:53 |
| electro5751 | last line : Error <creator>[07/19 17:52:00] : URLGrabber error: https://releases.jolla.com/jolla-apps//armv7hl/repodata/repomd.xml | 17:53 |
| deathmist | electro5751: you didn't set RELEASE. please do e.g. "RELEASE=3.0.3.10" | 17:53 |
| electro5751 | yes sorry | 17:54 |
| electro5751 | sailfishOS version depend on the sailfish SDK ? | 17:56 |
| deathmist | when using latest SDK you can always build latest public release from https://en.wikipedia.org/wiki/Sailfish_OS#Version_history | 17:57 |
| electro5751 | v3.1.0.11 | 17:58 |
| electro5751 | or v3.0.0.8 | 17:58 |
| deathmist | I said "latest public release", so neither. latest public release is v3.0.3.10 | 17:58 |
| deathmist | ignore early access | 17:59 |
| electro5751 | EXTRA_NAME=. | 18:00 |
| electro5751 | i suppose | 18:00 |
| deathmist | just don't set it | 18:00 |
| electro5751 | o sorry | 18:00 |
| electro5751 | ok | 18:00 |
| electro5751 | why this -> C_CREATEREPOLIB: Warning: Record with type "patterns" already exists in repomd.xml | 18:00 |
| electro5751 | have again this error | 18:01 |
| electro5751 | Error <creator>[07/19 17:52:00] : URLGrabber error: https://releases.jolla.com/jolla-apps//armv7hl/repodata/repomd.xml - e.errno: 14 | 18:01 |
| deathmist | ignore all warnings, if you get a ZIP at the end you are good to go | 18:01 |
| electro5751 | o no | 18:01 |
| electro5751 | it's good | 18:01 |
| deathmist | you still didn't set release? | 18:01 |
| electro5751 | it's good | 18:01 |
| electro5751 | Error <repo>[07/19 18:01:35] : found 1 resolver problem, abort! | 18:01 |
| electro5751 | Warning[07/19 18:01:34] : repo problem: nothing provides libhybris-tests needed by pattern:sailfish-porter-tools-1-1.noarch, | 18:01 |
| electro5751 | Warning[07/19 18:01:14] : Can't get version info of /usr/bin/qemu-arm-static, please make sure it's higher than 0.13.0 | 18:02 |
| mal | did all build in build_packages.sh work without errors | 18:07 |
| electro5751 | ok | 18:07 |
| electro5751 | it's working | 18:08 |
| electro5751 | sorry but | 18:10 |
| electro5751 | Build libhybris? [Y/n/all] | 18:10 |
| mal | all | 18:10 |
| electro5751 | https://dpaste.de/96S3 | 18:11 |
| electro5751 | always all ? after seeing paste | 18:12 |
| mal | well all means it will build all | 18:14 |
| electro5751 | ok | 18:15 |
| mal | you need to build all at least once | 18:16 |
| T42 | <austenite> mal, on 15.1 port , system and vendor are not mounted https://pastebin.com/YFvq7quE | 18:16 |
| mal | maybe you have the usual issue that fstab and ueventd*.rc is not copied to out/.../root/ | 18:18 |
| T42 | <austenite> and there is no property_contexts file after hybris_hal so i copied the plat_property_contexts as property_contexts and propert_set errors are gone , but there is no /system | 18:19 |
| mal | check that I just told | 18:19 |
| mal | *what | 18:19 |
| T42 | <austenite> ok | 18:19 |
| electro5751 | DONE! Now proceed on creating the rootfs | 18:28 |
| electro5751 | mal, Error <creator>[07/19 18:30:47] : Unable to find pattern: Jolla Configuration t0lte | 18:31 |
| electro5751 | after this cmd : sudo mic create | 18:32 |
| electro5751 | p24 | 18:32 |
| deathmist | electro5751: run "hybris/droid-configs/droid-configs-device/helpers/process_patterns.sh" again? | 18:34 |
| mal | did you run all the commands told in there | 18:34 |
| electro5751 | forget one cmd | 18:35 |
| electro5751 | always : Warning[07/19 18:35:31] : Can't get version info of /usr/bin/qemu-arm-static, please make sure it's higher than 0.13.0 | 18:35 |
| mal | ignore that | 18:36 |
| electro5751 | ok, after the zip il created | 18:36 |
| electro5751 | can i use my twrp recovery ? | 18:36 |
| electro5751 | to flash the zip | 18:36 |
| electro5751 | for you, what is the main advantage of choose sailfishOS rather than AOSP and LineageOS ? | 18:40 |
| deathmist | @birdzhang or someone else knowledgeable on the topic: is there info about Anbox on 4.4 kernel? lxc-checkconfig returns https://pastebin.com/YkCeYCZN I've only done minor kernel tweaks https://git.io/fjMqZ, so adding these patches https://git.io/fjMqn should be next? (the contents are quite a bit different on some of the files) | 18:44 |
| electro5751 | it's ok -> sailfishos-t0lte-release-3.0.3.10.zip | 18:44 |
| electro5751 | it's possible to flash .zip with twrp recovery ? | 18:45 |
| deathmist | electro5751: congrats! now you need a cm-14.1 zip to flash BEFORE flashing that one (preferably official) while making sure /system and /cache are formatted as ext4 in TWRP | 18:45 |
| electro5751 | ok thk | 18:45 |
| electro5751 | how to be sure ? | 18:46 |
| deathmist | if you haven't made full backups, do so now. Wipe > Advanced Wipe > Click partition to check > Repair or Change File System should show it (formatting doesn't hurts either :p) | 18:48 |
| electro5751 | i suppose it's in ext4 because i have resurrexion remix | 18:50 |
| electro5751 | and before lineageOS | 18:50 |
| electro5751 | just flash cm-14.1 so | 18:50 |
| deathmist | prob should factory reset wipe from TWRP too before beginning for the first time | 18:51 |
| electro5751 | just have CM13 | 18:51 |
| electro5751 | https://www.cyanogenmodroms.com/2014/04/cyanogenmod-rom-samsung-galaxy-note-2-t0lte.html | 18:51 |
| deathmist | your base was on cm-14.1 right? https://mirrorbits.lineageos.org/full/t0lte/20190126/lineage-14.1-20190126-nightly-t0lte-signed.zip | 18:53 |
| electro5751 | humm, now resurrexion remix but | 18:54 |
| electro5751 | lineageOS | 18:54 |
| electro5751 | never CM | 18:54 |
| deathmist | CM = LineageOS | 18:54 |
| electro5751 | this link is dead | 18:54 |
| electro5751 | https://mirrorbits.lineageos.org/full/t0lte/20190126/lineage-14.1-20190126-nightly-t0lte-signed.zip | 18:54 |
| electro5751 | ok, so i flash lineageOS ? | 18:54 |
| deathmist | oh I didn't even check, oops | 18:54 |
| electro5751 | RR-N-v5.8.5-20181218-t0lte-Unofficial | 18:56 |
| deathmist | https://androidfilehost.com/?fid=1395089523397906488 there, found a mirrored one ;) | 18:57 |
| electro5751 | lineage-14.1-20180729-nightly-t0lte-signed | 18:57 |
| electro5751 | it's good too ? | 18:57 |
| electro5751 | ok i download this | 18:58 |
| electro5751 | 2019 | 18:58 |
| electro5751 | after deathmist, i wipe system, install lineageOS | 18:59 |
| electro5751 | and after wipe system and install zip sailfish OS ? | 18:59 |
| electro5751 | what are step ? | 18:59 |
| deathmist | factory reset wipe from TWRP should be enough, then LineageOS => SFOS zip | 18:59 |
| electro5751 | install LineageOS and install SailFishOS ? | 19:01 |
| electro5751 | SailFishOS.zip proceed to wipe system before install it ? | 19:01 |
| deathmist | ? sailfish doesn't touch your system partition, lineageos will and you'll flash that first | 19:02 |
| electro5751 | ok | 19:02 |
| electro5751 | so need lineageOS ^^, it's strange for an independant OS ^^ | 19:03 |
| electro5751 | sailfish | 19:03 |
| deathmist | it uses LineageOS as a base to get the hardware, display, LEDs, buttons etc working fully under Sailfish OS software, no need to reinvent the wheel ;) | 19:04 |
| electro5751 | exactly | 19:04 |
| electro5751 | but, with sailfishOS, no google and no microsoft | 19:05 |
| electro5751 | it's possible ? | 19:05 |
| deathmist | what's possible? install Sailfish without LineageOS zip? I've thought about this too but one would have to go into great lengths (and imho waste time) to make that even partially working | 19:07 |
| electro5751 | sorry but i don't understand all | 19:07 |
| electro5751 | i must reboot and start LineageOS before install zip SailFishOS ? | 19:08 |
| deathmist | nope, just flash lineage zip then sailfish | 19:09 |
| electro5751 | ok | 19:09 |
| electro5751 | sailfish is installing | 19:13 |
| electro5751 | i just want to know if package google or microsoft are in sailfishOS | 19:13 |
| electro5751 | and if it's possible to add android app in the phone | 19:14 |
| electro5751 | installation of sailfishOS error : updater processus error 7 | 19:17 |
| deathmist | electro5751: about android apps, basically no. alien-dalvik (the Android app layer) is a commercial piece of software that Jolla doesn't allow community ports to have. maybe you could get a license for around $25, but I have no clue. even then it would probably be strictly for personal use. Anbox is a thing but it's not in a pretty state right now | 19:18 |
| deathmist | at all. | 19:18 |
| electro5751 | ok | 19:18 |
| electro5751 | thanks for you answer | 19:18 |
| deathmist | that's kinda expected, what happened there is the extraction binary "tar" is broken on your TWRP, using an older TWRP version could fix this, but I just use the one SFOS generates w/ busybox | 19:18 |
| T42 | <Harsh18262> try using format data that fixes error 7 for me | 19:19 |
| electro5751 | format DATA | 19:19 |
| T42 | <Harsh18262> after selecting wipe in twrp there are two options advanced option and format data | 19:20 |
| electro5751 | for me, failed to mount /dev/block/platform/dw_mmc/by-name/USERDATA at /data | 19:20 |
| deathmist | that's ok, it's already mounted before you entered the setup (kind of a pointless check, I made a custom solution that JUST checks if everything is in the right format i.e. ext4) | 19:20 |
| deathmist | if you format data please reboot back to TWRP recovery, then flash lineageos and sailfish again (after copying them over to the phone again) | 19:22 |
| electro5751 | ok | 19:23 |
| T42 | <Harsh18262> use adb sideload or a ext sd card that would reduce the hasle of copying a new test version on device | 19:23 |
| electro5751 | erf | 19:29 |
| electro5751 | failed to mount | 19:29 |
| electro5751 | USER-DATA | 19:29 |
| electro5751 | USERDATA | 19:29 |
| T42 | <Harsh18262> did u reboot? | 19:29 |
| electro5751 | device or resource busy | 19:29 |
| electro5751 | yes | 19:29 |
| T42 | <Harsh18262> this warning while installing zip | 19:30 |
| T42 | <Harsh18262> meaning is the zip continuing to install or stopped? | 19:30 |
| electro5751 | continuing | 19:31 |
| T42 | <Harsh18262> thats not a error as deathmist said it gives that error because the partition is already mounted | 19:31 |
| electro5751 | yes | 19:32 |
| electro5751 | already mounted yes but i don't know why /data is mounted | 19:33 |
| electro5751 | i have disable MTP service | 19:33 |
| electro5751 | but same notice | 19:33 |
| T42 | <Harsh18262> it gets mounted at the start of twrp | 19:33 |
| electro5751 | ok, so | 19:33 |
| electro5751 | Hum, place my .zip in sd card | 19:34 |
| electro5751 | it's for that i suppose | 19:34 |
| T42 | <Harsh18262> i didnt understand | 19:34 |
| electro5751 | maybe because i launch the zip under my internal storage | 19:34 |
| T42 | <Harsh18262> no that does not matter | 19:34 |
| electro5751 | maybe it's because i have install LineageOS ? | 19:35 |
| electro5751 | i must restart recovery ? | 19:35 |
| T42 | <Harsh18262> if u want that warning to go then go to mount section of twrp unmount data and internal then flash the warning will not appear | 19:35 |
| T42 | <Harsh18262> for what? | 19:36 |
| electro5751 | error installation | 19:36 |
| electro5751 | so what i must do ? | 19:36 |
| T42 | <Harsh18262> the installation stopped | 19:36 |
| T42 | <Harsh18262> ? | 19:36 |
| electro5751 | yes | 19:36 |
| electro5751 | error 7 | 19:37 |
| T42 | <Harsh18262> last line before stoping | 19:37 |
| electro5751 | i try to use SD card | 19:38 |
| electro5751 | to install SailFishOS | 19:38 |
| T42 | <Harsh18262> ok try | 19:39 |
| electro5751 | it's ok | 19:41 |
| electro5751 | just mount sdcard | 19:41 |
| electro5751 | before launch the .zip | 19:42 |
| deathmist | that won't help you, most likely tar is eating up all your available ram and then gets killed by OOM => results in error 7, which you could also verify in recovery log located in /cache | 19:42 |
| deathmist | sorry, log path is /tmp/recovery.log | 19:44 |
| deathmist | if tar is getting killed due to using all ram, you have 3 choices: downgrade TWRP, use tar from sailfish busybox or create a swapfile | 19:46 |
| deathmist | TWRP downgrade may or may not work (didn't for me) | 19:46 |
| electro5751 | my phone restart | 19:48 |
| electro5751 | the installation is okey but | 19:48 |
| electro5751 | always restart at startup | 19:48 |
| deathmist | how long until a restart? | 19:48 |
| electro5751 | just display samsung Galaxy note II | 19:48 |
| electro5751 | and restart until 6s | 19:48 |
| T42 | <Harsh18262> same for me | 19:49 |
| electro5751 | all 6s | 19:49 |
| electro5751 | :/ | 19:49 |
| T42 | <Harsh18262> 6s means 6 seconds ? | 19:49 |
| electro5751 | yes | 19:49 |
| T42 | <Harsh18262> ok | 19:49 |
| electro5751 | 15 seconds | 19:50 |
| deathmist | that is to be expected, try to use "telnet 192.168.2.15 23" from host quickly when the phone is booting and also do "cat /init.log" if possible to get details about init process | 19:50 |
| electro5751 | local adress is 192.168.2.15 23 ? | 19:51 |
| deathmist | that is your phone when it's plugged in via USB, it will always have the 192.168.2.15 IP for development and debugging purposes | 19:52 |
| deathmist | or it should anyways, another way to tell if it's doing anything is running "dmesg -w" on the host, plug the phone in and start booting to SFOS, "Mer boat loader" should show up there etc | 19:53 |
| T42 | <Harsh18262> @deathmist at what stage is your device booting in sfos or telnet only? | 19:53 |
| electro5751 | telnet not work | 19:54 |
| deathmist | if you don't spam the telnet command when trying to connect (e.g. CTRL + C if it doesn't connect instantly, UP arrow then ENTER) it'll just hang, see host dmesg like I told you above | 19:55 |
| deathmist | Harsh18262: in very early init you get telnet 23, that is before it even boots Sailfish. if you can't get that it's likely a SELinux, device fstab, ueventd*.rc etc problem | 19:56 |
| electro5751 | i don't arrived to do anything | 19:56 |
| electro5751 | just display Samsung Galaxy Note II GT-N7105 | 19:58 |
| electro5751 | and reboot at each 15 seconds | 19:59 |
| electro5751 | not telnet possible | 19:59 |
| electro5751 | can i flash SailfishOS with adb ? | 20:00 |
| electro5751 | what version of twrp is better ? | 20:00 |
| deathmist | if flashing succeeded that is not the issue, your issue would currently be hybris-boot | 20:00 |
| deathmist | could you show your fixup-mountpoints? | 20:01 |
| electro5751 | yes | 20:01 |
| electro5751 | https://dpaste.de/4hAs | 20:03 |
| electro5751 | i have TWRP version 3.1.1-0 | 20:04 |
| deathmist | that should be ok, how about your kernel/samsung/smdk4412/arch/arm/configs/lineageos_t0lte_defconfig ? | 20:06 |
| electro5751 | you want all file ? | 20:07 |
| electro5751 | it's difficult to give it to you | 20:07 |
| deathmist | dpaste? | 20:08 |
| electro5751 | yes | 20:08 |
| electro5751 | https://dpaste.de/YqjE | 20:10 |
| electro5751 | i have fix warning but how to really know what they do ! :/ | 20:14 |
| electro5751 | add the end of the def_config | 20:16 |
| deathmist | just to make sure, give contents of device/samsung/t0lte/BoardCommonConfig.mk | 20:18 |
| electro5751 | ok | 20:19 |
| deathmist | oh actually run "grep -rnw device/ -e BOARD_KERNEL_CMDLINE" | 20:19 |
| deathmist | seems you didn't modify that yet | 20:19 |
| electro5751 | device/samsung/smdk4412-common/BoardCommonConfig.mk:54:BOARD_KERNEL_CMDLINE := console=ttySAC2,115200 | 20:20 |
| electro5751 | https://dpaste.de/JkLA | 20:20 |
| electro5751 | i can use odin to flash my samsung device | 20:22 |
| deathmist | the file you linked doesn't have BOARD_KERNEL_CMDLINE even though it's clearly found above? | 20:22 |
| electro5751 | O, no, | 20:23 |
| deathmist | find the proper file first of all, then append " audit=0 selinux=0" at the end of BOARD_KERNEL_CMDLINE line in the PROPER BoardCommonConfig.mk | 20:23 |
| electro5751 | device/samsung/t0tle/BoardCommonConfig.mk not have BOARD_KERNEL_CMDLINE | 20:25 |
| T42 | <Harsh18262> @deathmist audit=0 is also neccesary i dont have that in my bc.mk | 20:25 |
| deathmist | https://git.io/fjMY9 the line 100% is there, you pasted the wrong file | 20:25 |
| deathmist | you are looking at the wrong file... are you even looking what find returned? it clearly says "device/samsung/smdk4412-common/BoardCommonConfig.mk" | 20:25 |
| electro5751 | i don't know what modify | 20:26 |
| electro5751 | yes | 20:26 |
| electro5751 | but, what i must to do | 20:26 |
| deathmist | append " audit=0 selinux=0" at the end of BOARD_KERNEL_CMDLINE line like so https://git.io/fjMka | 20:27 |
| electro5751 | for this file ? | 20:27 |
| electro5751 | device/samsung/smdk4412-common/BoardCommonConfig.mk | 20:27 |
| deathmist | maybe | 20:29 |
| electro5751 | but i don't have the same text on the line | 20:29 |
| deathmist | yes you do https://git.io/fjMY9 stop looking at the wrong file | 20:31 |
| electro5751 | what is the wrong file for you | 20:32 |
| electro5751 | # Kernel | 20:32 |
| electro5751 | BOARD_KERNEL_CMDLINE := console=ttySAC2,115200 | 20:32 |
| electro5751 | BOARD_KERNEL_BASE := 0x40000000 | 20:32 |
| electro5751 | BOARD_KERNEL_PAGESIZE := 2048 | 20:32 |
| electro5751 | KERNEL_TOOLCHAIN := $(ANDROID_BUILD_TOP)/prebuilts/gcc/$(HOST_OS)-x86/arm/arm-eabi-4.8/bin | 20:32 |
| electro5751 | TARGET_KERNEL_CROSS_COMPILE_PREFIX := arm-eabi- | 20:32 |
| deathmist | there it is, "BOARD_KERNEL_CMDLINE", it's in device/samsung/smdk4412-common/BoardCommonConfig.mk like I've already said | 20:33 |
| electro5751 | yes ok | 20:33 |
| electro5751 | so after, i must recompile all ? | 20:33 |
| electro5751 | make -j$(nproc --all) hybris-hal | 20:34 |
| electro5751 | hybris/mer-kernel-check/mer_verify_kernel_config \ | 20:34 |
| electro5751 | ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 20:34 |
| deathmist | run "mka hybris-boot", then give that .config file | 20:34 |
| electro5751 | run with SDK environment ? | 20:35 |
| electro5751 | sfossdk | 20:35 |
| deathmist | nope, HABUILD like always before when working with Android parts such as HAL or kernel | 20:35 |
| electro5751 | ok | 20:35 |
| electro5751 | what i must do after running this cmd ? | 20:37 |
| deathmist | give me your ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config | 20:37 |
| electro5751 | https://dpaste.de/i0Fp | 20:38 |
| deathmist | don't think you ran all the needed commands: ". build/envsetup.sh && breakfast $DEVICE && export USE_CCACHE=1" | 20:40 |
| deathmist | also "cd $ANDROID_ROOT" | 20:40 |
| electro5751 | ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config : https://dpaste.de/bH4w | 20:40 |
| electro5751 | i run make hybris-boot | 20:43 |
| electro5751 | log of | 20:44 |
| electro5751 | make hybris-boot | 20:44 |
| electro5751 | https://dpaste.de/eMiO | 20:44 |
| deathmist | alright good, now go to TWRP and flash hybris-boot.img to your boot partition, reobot and see if this changes anything (it should) | 20:45 |
| electro5751 | a lot of warning at the beginning | 20:45 |
| electro5751 | warning: override: reassigning to symbol BTRFS_FS | 20:45 |
| electro5751 | ok thk | 20:45 |
| electro5751 | it's write image for boot | 20:50 |
| electro5751 | i suppose | 20:50 |
| electro5751 | it's not that deathmist | 20:50 |
| deathmist | what do you mean? grab the fresh hybris-boot.img from out/ and write it to the boot partition using TWRP (need to tap Install Image) | 20:51 |
| electro5751 | yes, it's done | 20:51 |
| electro5751 | my phone reboot | 20:51 |
| deathmist | still same 15s? | 20:51 |
| electro5751 | yes | 20:52 |
| electro5751 | mal, an idea ? | 20:54 |
| T42 | <elros34> do you have something in host dmesg? | 20:54 |
| electro5751 | i don't know if i have more message | 20:55 |
| electro5751 | be appear no | 20:55 |
| electro5751 | https://dpaste.de/dSRi | 20:55 |
| electro5751 | nothing more | 20:56 |
| electro5751 | try flashing with odin ? | 20:56 |
| T42 | <elros34> sure I see no reason to use twrp to flash kernel but that shoudn't be issue | 20:58 |
| electro5751 | flash only the zip with odin ? | 20:59 |
| deathmist | electro5751: there are the rest of your options for kernel defconfig https://pastebin.com/uVdBpij0 probably won't make a difference, but won't hurt to try | 20:59 |
| deathmist | what zip? you are working with hybris-boot image, did you format something or wipe data? | 20:59 |
| electro5751 | nono | 21:00 |
| electro5751 | ok, after append this text | 21:01 |
| T42 | <elros34> try to hold recovery button when it reboots so it reboot straight to twrp | 21:01 |
| electro5751 | what i do | 21:01 |
| T42 | <elros34> there is no point for adding more config changes, there is a chance one of them cause issue | 21:02 |
| T42 | <elros34> I asked earlier, do you use kernel 3.0 ? | 21:03 |
| electro5751 | make -j$(nproc --all) hybris-hal | 21:03 |
| electro5751 | ? | 21:03 |
| deathmist | yes he does, 3.0.101 | 21:03 |
| electro5751 | https://dpaste.de/CeYQ | 21:04 |
| T42 | <elros34> so you need patched glibc after you fix kernel issue | 21:04 |
| electro5751 | just to check | 21:04 |
| electro5751 | what i must to do ? now | 21:05 |
| electro5751 | recompile ? | 21:05 |
| electro5751 | make -j$(nproc --all) hybris-hal | 21:05 |
| deathmist | elros34: ah, I didn't know, I have a 4.4 device myself | 21:05 |
| T42 | <elros34> have you tried what I said about rebooting to twrp? | 21:05 |
| electro5751 | rebooting yes | 21:05 |
| electro5751 | it's ok | 21:05 |
| electro5751 | to twrp | 21:05 |
| T42 | <elros34> so you should have now /proc/last_kmsg | 21:06 |
| electro5751 | with adb ? | 21:06 |
| T42 | <elros34> yes | 21:06 |
| electro5751 | ok | 21:06 |
| electro5751 | no devices :/ | 21:07 |
| electro5751 | i reboot my device | 21:08 |
| electro5751 | ok | 21:10 |
| electro5751 | i go | 21:10 |
| electro5751 | elros34 : https://dpaste.de/nGfd | 21:11 |
| electro5751 | how get a file ? | 21:13 |
| electro5751 | adb push or adb pull | 21:13 |
| electro5751 | it's a binary | 21:16 |
| electro5751 | i'm sorry i have no more | 21:16 |
| electro5751 | elros34 ? are you here ? | 21:17 |
| electro5751 | vknecht ? | 21:18 |
| electro5751 | i must go to sleep | 21:20 |
| electro5751 | nobody ? | 21:20 |
| T42 | <Harsh18262> ADB pull to get a file | 21:24 |
| T42 | <Harsh18262> ADB pull {path of file to be pull} {path where to save the pulled file} | 21:25 |
| T42 | <elros34> electro5751: for me looks like it crash very early thus only "Starting kernel at*" in log, you can try with minimal defconfig changes. On 3.0 kernel I had issues with: CONFIG_VT/_DEVTMPFS/_CGROUP_MEM_RES_CTLR so you can try to disable them first | 21:40 |
| T42 | <elros34> or you just grab log wrong way | 21:53 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!