Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Help building Halium for International Galaxy S4 (jfltexx)

    Porting
    7
    11
    1335
    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.
    • YamiYukiSenpai
      YamiYukiSenpai last edited by

      So I'm running into issues building Halium for jfltexx.

      When I ran mka mkbootimg, here's what I got:

      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
      

      Here are the list of commands I ran (pretty much followed the steps), and their output. Hope you can help me.

      D 1 Reply Last reply Reply Quote 0
      • D
        doniks @YamiYukiSenpai last edited by

        @yamiyukisenpai said in Help building Halium for International Galaxy S4 (jfltexx):

        /block/platform/msm_sdcc.1/by-name/boot

        I think the actual error is the line right after what you quoted and I think that means you miss something in your manifest. Did you use this one: https://github.com/Halium/projectmanagement/issues/59 if not, why not and share it/the difference to #59

        1 Reply Last reply Reply Quote 0
        • T
          tigerpro last edited by

          Try "touch frameworks/base/packages/SettingsLib/common.mk" it says that file is missing

          1 Reply Last reply Reply Quote 1
          • C
            curioussav last edited by

            HI, I'm trying to find out the status of device ports right now. I have a spreadsheet I started with the following categories.
            bootable, wifi, bluetooth, speaker, cellular, data, camera which of those are true/working on the device so far?

            advocatux 1 Reply Last reply Reply Quote 0
            • advocatux
              advocatux @curioussav last edited by

              @curioussav probably this is the best place to follow https://github.com/Halium/projectmanagement/issues

              1 Reply Last reply Reply Quote 0
              • YamiYukiSenpai
                YamiYukiSenpai last edited by

                So I got it to build, but now I'm wondering about changing userdata or data to ext4. In fstab.qcom, there are 2 /data mountpoints, one with f2fs and the other with ext4. Do I just delete the f2fs entry?

                /dev/block/platform/msm_sdcc.1/by-name/userdata  /data          f2fs    nosuid,nodev,noatime,rw,inline_xattr                                                          wait,check,formattable,encryptable=footer
                /dev/block/platform/msm_sdcc.1/by-name/userdata  /data          ext4    nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic                        wait,check,formattable,encryptable=footer
                
                advocatux 1 Reply Last reply Reply Quote 0
                • advocatux
                  advocatux @YamiYukiSenpai last edited by

                  @yamiyukisenpai hi, for such a specific question maybe you can get help in any of the Halium channels:

                  • Telegram: https://t.me/halium
                  • Matrix: #halium:disroot.org
                  • IRC: #halium@freenode
                  YamiYukiSenpai 1 Reply Last reply Reply Quote 0
                  • BlueKenny
                    BlueKenny last edited by

                    Commend the first one and leave the ext4 one

                    1 Reply Last reply Reply Quote 1
                    • S
                      suoko last edited by suoko

                      I bet you saw this post https://github.com/Halium/projectmanagement/issues/62#issuecomment-391226918

                      I got one question though: following the guide on https://wiki.ubuntu.com/Touch/Devices/i9505 you find a link to a rom that includes the boot.img only and it doesn't work, obviously.
                      Do you know of any old but working ubuntu touch rom for the s4?

                      Edit:
                      If you're writing down what you're doing I can try do the same to speed up the porting.

                      1 Reply Last reply Reply Quote 0
                      • YamiYukiSenpai
                        YamiYukiSenpai @advocatux last edited by

                        @advocatux The Matrix room doesn't exist

                        I just finished school, so now I have time to tackle this again.

                        I'm now getting this error after I ran mka mkbootimg

                        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 /dev/mmcblk0p20
                        halium/hybris-boot/Android.mk:70: ********************* /data appears to live on /dev/block/platform/msm_sdcc.1/by-name/userdata /dev/mmcblk0p29
                        halium/hybris-boot/Android.mk:73: *** There should be a one and only one device entry for HYBRIS_BOOT_PART and HYBRIS_DATA_PART.  Stop.
                        

                        @suoko nope sorry

                        advocatux 1 Reply Last reply Reply Quote 0
                        • advocatux
                          advocatux @YamiYukiSenpai last edited by

                          @YamiYukiSenpai that room is still listed in Halium official documentation (http://docs.halium.org/en/latest/porting/first-steps.html?highlight=%23halium%3Adisroot.org) but maybe they've a problem with federation and that's why you can't access it from your instance?

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post