• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Need help in porting Halium/Ubports to Galaxy S4 jfltexx

Scheduled Pinned Locked Moved Porting
15 Posts 7 Posters 2.8k Views 4 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      suoko
      last edited by suoko 2 Dec 2019, 17:00 11 Feb 2019, 16:55

      I'm trying compile with this error:

      BUILD_ID=NOF27B
      OUT_DIR=/home/admin/halium/out
      ============================================
      frameworks/av/camera/cameraserver/Android.mk:18: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
      halium/hybris-boot/Android.mk:69: ********************* /boot appears to live on /dev/block/platform/msm_sdcc.1/by-name/boot
      halium/hybris-boot/Android.mk:70: ********************* /data appears to live on /dev/block/platform/msm_sdcc.1/by-name/userdata
      hardware/samsung/AdvancedDisplay/Android.mk:34: frameworks/base/packages/SettingsLib/common.mk: No such file or directory
      make: *** [build/core/ninja.mk:167: /home/admin/halium/out/build-lineage_jfltexx.ninja] Error 1
      make: Leaving directory '/home/admin/halium'
      

      using this manifest:

      <?xml version="1.0" encoding="UTF-8"?>
      <manifest>
          <project path="device/samsung/jfltexx" name="android_device_samsung_jfltexx" remote="los" revision="cm-14.1" />
          <project path="device/samsung/jf-common" name="android_device_samsung_jf-common" remote="los" revision="cm-14.1" />
          <project path="device/samsung/qcom-common" name="android_device_samsung_qcom-common" remote="los" revision="cm-14.1" />
          <project path="hardware/samsung" name="android_hardware_samsung" remote="los" revision="cm-14.1" />
          <project path="packages/resources/devicesettings" name="android_packages_resources_devicesettings" remote="los" revision="cm-14.1" />
          <project path="vendor/samsung" name="proprietary_vendor_samsung" remote="them" revision="cm-14.1" />
          <project path="kernel/samsung/jf" name="android_kernel_samsung_jf" remote="los" revision="cm-14.1" />
      </manifest>
      
      1 Reply Last reply Reply Quote 0
      • S Offline
        suoko
        last edited by Lakotaubp 2 Dec 2019, 21:14 12 Feb 2019, 16:59

        CHK     include/generated/utsrelease.h
        make[2]: 'include/generated/mach-types.h' is up to date.
        CALL    /home/admin/halium/kernel/samsung/jf/scripts/checksyscalls.sh
        CHK     include/generated/compile.h
        GZIP    kernel/config_data.gz
        CHK     kernel/config_data.h
        Kernel: arch/arm/boot/Image is ready
        LD      arch/arm/boot/compressed/vmlinux
        OBJCOPY arch/arm/boot/zImage
        Kernel: arch/arm/boot/zImage is ready
        make: Leaving directory '/home/admin/halium/kernel/samsung/jf'
        [ 98% 808/819] Target boot image: /home/admin/halium/out/target/product/jfltexx/boot.img
        /home/admin/halium/out/target/product/jfltexx/boot.img maxsize=10543104 blocksize=135168 total=6729744 reserve=270336
        Made boot image: /home/admin/halium/out/target/product/jfltexx/boot.img
        [ 98% 809/819] ----- Making recovery ramdisk ------
        Copying baseline ramdisk...
        Modifying ramdisk contents...
        ----- Making uncompressed recovery ramdisk ------
        [ 99% 811/819] ----- Making recovery image ------
        /home/admin/halium/out/target/product/jfltexx/recovery.img maxsize=10543104 blocksize=135168 total=9086992 reserve=270336
        Made recovery image: /home/admin/halium/out/target/product/jfltexx/recovery.img
        [ 99% 814/819] Construct recovery from boot
        FAILED: /bin/bash -c "(mkdir -p /home/admin/halium/out/target/product/jfltexx/obj/PACKAGING/recovery_patch_intermediates/ ) && (PATH=/home/admin/halium/out/host/linux-x86/bin:\$PATH /home/admin/halium/out/host/linux-x86/bin/bsdiff /home/admin/halium/out/target/product/jfltexx/boot.img /home/admin/halium/out/target/product/jfltexx/recovery.img /home/admin/halium/out/target/product/jfltexx/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p )"
        /bin/bash: /home/admin/halium/out/host/linux-x86/bin/bsdiff: No such file or directory
        [ 99% 814/819] build /home/admin/halium/out/target/product/jfltexx/obj/NOTICE.html
        Combining NOTICE files into HTML
        Combining NOTICE files into text
        ninja: build stopped: subcommand failed.
        make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
        make: Leaving directory '/home/admin/halium'
        
        #### make failed to build some targets (26 seconds) ####
        
        A L 2 Replies Last reply 12 Feb 2019, 18:42 Reply Quote 0
        • A Offline
          advocatux @suoko
          last edited by 12 Feb 2019, 18:42

          @suoko you can select all your text and click on that </> icon to make it more readable, or you can add 3 backticks (```) at the beginning and the at end of your text πŸ™‚

          1 Reply Last reply Reply Quote 0
          • L Offline
            Lakotaubp @suoko
            last edited by 12 Feb 2019, 21:14

            @suoko Edited your post as @advocatux recommended. Hope you don't mind.

            1 Reply Last reply Reply Quote 0
            • F Offline
              flohack
              last edited by 12 Feb 2019, 21:54

              @suoko said in Need help in porting Halium/Ubports to Galaxy S4 jfltexx:

              hardware/samsung/AdvancedDisplay/Android.mk:34: frameworks/base/packages/SettingsLib/common.mk: No such file or directory

              This seems to be a Java application, try to get rid of AdvancedDisplay fully.

              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

              S 1 Reply Last reply 13 Feb 2019, 20:15 Reply Quote 0
              • S Offline
                suoko @flohack
                last edited by 13 Feb 2019, 20:15

                @Flohack i did it, i flashed it but now it boot loops.
                No signs of ubuntu touch, it just reboots after a minute of black screen and no way to ssh into it

                F 1 Reply Last reply 13 Feb 2019, 20:26 Reply Quote 0
                • F Offline
                  flohack @suoko
                  last edited by 13 Feb 2019, 20:26

                  @suoko Did you start using the reference rootfs?

                  let it bootloop once, go into recovery, look for cat /proc/last_kmsg - that will give you kernel dmesg

                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                  S 1 Reply Last reply 14 Feb 2019, 14:21 Reply Quote 0
                  • S Offline
                    suoko @flohack
                    last edited by 14 Feb 2019, 14:21

                    @Flohack

                    ~ # cat /proc/last_kmsg 
                    [    0.000000] Truncating memory at 0xc0000000 to fit in 32-bit physical address space
                    [    0.000000] sec_tsp_mode: LCD_ID = 0x408047, val: 0X408047, ret1: 0x8
                    [    0.036590] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
                    [    0.059722] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059753] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059783] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059783] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059814] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059844] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059844] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.059875] msm_rpm_get_status(): Status id 433 not defined for target
                    [    0.209259] sensor_power_on_vdd: done
                    [    0.263061] i2c i2c-4: Failed to register i2c client imx135 at 0x10 (-16)
                    [    0.263305] i2c i2c-4: Can't create device at 0x10
                    [    0.263763] i2c i2c-4: Failed to register i2c client s5k3l1yx at 0x34 (-16)
                    [    0.264007] i2c i2c-4: Can't create device at 0x34
                    [    0.298034] ion_heap_create: Invalid heap type 3
                    [    0.303222] msm_slim_ctrl msm_slim_ctrl.1: Slim-dev:3 report inf element:0x0
                    [    0.303436] msm_slim_ctrl msm_slim_ctrl.1: offset:0x0:bit mask:8
                    [    0.304138] msm_slim_ctrl msm_slim_ctrl.1: Slim-dev:4 report inf element:0x400
                    [    0.304473] msm_slim_ctrl msm_slim_ctrl.1: offset:0x0:bit mask:8
                    [    0.385742] Error-Bad Function Input
                    [    0.386718] Error-Bad Function Input
                    [    0.705566] smd_channel_probe_worker: allocation table not initialized
                    [    0.721649] dma_test_init, minor number 37
                    [    0.729095] mdm_modem_probe: registered mdm id 0
                    [    0.729248] mdm_do_first_power_on:id 0: Powering on modem for the first time
                    [    0.990509] cont_splash_clk_ctrl: dsi_esc_clk - clk_set_rate failed
                    
                    
                    1 Reply Last reply Reply Quote 1
                    • S Offline
                      suoko
                      last edited by 14 Feb 2019, 14:26

                      Had to truncate due to false spam-detection

                      [    0.999847] [mdnie lite] start!
                      [    1.000061] [mdnie lite] end!
                      [    1.001800] hdmi_msm hdmi_msm.1: external_common_state_create: sysfs group df038608
                      [    1.002227] Inside writeback_driver_init
                      [    1.002471] Inside writeback_probe
                      [    1.006286] Unknown PM state 0
                      [    1.006378] Unknown PM state 3
                      [    1.192382] wcd9xxx_slim_probe: failed to get slimbus tabla-slim logical address: -6
                      [    1.261932] msm_otg msm_otg: failed to get phy_clk
                      [    1.431884] couldn't get usb power supply
                      [    1.454223] [jc_spi_init:336] Entered
                      [    1.454315] [jc_spi_probe:301] Entered
                      [    1.454498] [jc_spi_probe:311] jc_spi successfully probed
                      [    1.454589] jc_config_isp_irq~~~~~~~~~~
                      [    1.454803] msm_eeprom_probe probe_fail
                      [    1.459228] msm_sensor_i2c_probe s5k6b2yx probe succeeded
                      [    1.459320] msm_eeprom_probe probe_fail
                      [    1.494873] mmc0: No card detect facilities available
                      [    1.620819] power_supply sec-fuelgauge: driver failed to report `status' property: 4294967274
                      [    1.621063] power_supply sec-fuelgauge: driver failed to report `status' property: 4294967274
                      [    1.639068] max77693_get_health_state: Fail to get psy (battery)
                      [    1.641784] power_supply sec-charger: driver failed to report `power_now' property: 4294967274
                      [    1.643585] max77693_get_health_state: Fail to get psy (battery)
                      [    1.646301] power_supply sec-charger: driver failed to report `power_now' property: 4294967274
                      
                      
                      1 Reply Last reply Reply Quote 1
                      • S Offline
                        suoko
                        last edited by 14 Feb 2019, 14:48

                        dbbb7e68-5fe2-4e45-807c-e302dddde79b-image.png g

                        F 1 Reply Last reply 14 Feb 2019, 22:27 Reply Quote 1
                        • F Offline
                          flohack @suoko
                          last edited by 14 Feb 2019, 22:27

                          @suoko it would be better you join @Halium group on Telegram. We dont want to overload the forum. And copy all such things into a pastebin plz...
                          Your log is very short. nothing that could help us. Please try to build Lineage with this manifest to verify if the kernel is at all working.

                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                          1 Reply Last reply Reply Quote 0
                          • F Offline
                            flohack
                            last edited by 14 Feb 2019, 22:45

                            Or maybe not. You might want to do telnet debugging with the break=bottom kernel cmdline parameter.

                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                            1 Reply Last reply Reply Quote 0
                            13 out of 15
                            • First post
                              13/15
                              Last post