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

    Could use help porting to n8000

    Scheduled Pinned Locked Moved
    Porting
    5
    13
    909
    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.
    • K
      KingProNoob2 @domubpkm
      last edited by

      @domubpkm Yes, that's it.

      K 1 Reply Last reply Reply Quote 0
      • K
        KingProNoob2 @KingProNoob2
        last edited by

        @kingpronoob2 This is the output of breakfast n8000.

        including vendor/cm/vendorsetup.sh
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_n8000".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_n8000".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_n8000".  Stop.
Device n8000 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_samsung_n8000
Traceback (most recent call last):
  File "/home/erik/halium/vendor/cm/build/tools/roomservice.py", line 263, in <module>
    default_revision = get_default_revision()
  File "/home/erik/halium/vendor/cm/build/tools/roomservice.py", line 115, in get_default_revision
    d = m.findall('default')[0]
IndexError: list index out of range
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_n8000".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_n8000".  Stop.

** Don't have a product spec for: 'lineage_n8000'
** Do you have the right repo manifest?
        KenedaK 1 Reply Last reply Reply Quote 0
        • KenedaK
          Keneda @KingProNoob2
          last edited by Keneda

          @kingpronoob2
          Shouldn't you use the exact codename wich seems to be like @domubpkm said GT-N8000 ?

          Edit : also, i don't see your device here https://wiki.lineageos.org/devices/#samsung
          Neither there https://download.lineageos.org/

          2015-2023 : Meizu MX4 now in legacy drawer by lack of pristine battery 😫
          2023-***** : Nexus 5 (16.04 OTA 25) for daily use, slowly dying πŸ€•
          2024-***** : Fairphone 5 waiting UT for freedom πŸ˜‰
          πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

          K 1 Reply Last reply Reply Quote 0
          • K
            KingProNoob2 @Keneda
            last edited by KingProNoob2

            @keneda The codename on the lineage os github is n8000. And i dont know why it is not on the official website, but it is on their github https://github.com/LineageOS/android_device_samsung_n8000 EDIT: I did manage to build lineage 14.1 stock, but not halium.

            K 1 Reply Last reply Reply Quote 0
            • K
              KingProNoob2 @KingProNoob2
              last edited by

              @Keneda Ok, i did manage to fix this, but after running mka mkbootimg, i got this error:

              Checking build tools versions...
build/core/executable.mk:87: external/gpg/Android.mk: No such file or directory
make: *** [build/core/ninja.mk:167: /home/erik/halium/out/build-cm_n8000.ninja] Error 1
make: Leaving directory '/home/erik/halium'

#### make failed to build some targets (9 seconds) ####
              M 1 Reply Last reply Reply Quote 0
              • K
                KingProNoob2
                last edited by

                @Keneda OK, got past that, but i have another error (this can happen only to me).

                including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:268: *** No matches for product "lineage_n8000".  Stop.
** Warning: 'n8000' is using CM-based makefiles. This will be deprecated in the next major release.
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20220805-UNOFFICIAL-n8000
TARGET_PRODUCT=cm_n8000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.18.15-200.fc36.x86_64-x86_64-with-glibc2.35
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NOF27B
OUT_DIR=/home/erik/halium/out
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20220805-UNOFFICIAL-n8000
TARGET_PRODUCT=cm_n8000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.18.15-200.fc36.x86_64-x86_64-with-glibc2.35
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NOF27B
OUT_DIR=/home/erik/halium/out
============================================
Running kati to generate build-cm_n8000.ninja...
/home/erik/halium/out/build-cm_n8000.ninja is missing, regenerating...
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20220805-UNOFFICIAL-n8000
TARGET_PRODUCT=cm_n8000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.18.15-200.fc36.x86_64-x86_64-with-glibc2.35
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NOF27B
OUT_DIR=/home/erik/halium/out
============================================
halium/hybris-boot/Android.mk:69: ********************* /boot appears to live on /dev/block/mmcblk0p5
halium/hybris-boot/Android.mk:70: ********************* /data appears to live on /dev/block/mmcblk0p12
PRODUCT_COPY_FILES device/samsung/smdk4412-common/configs/audio_effects.conf:system/etc/audio_effects.conf ignored.
PRODUCT_COPY_FILES device/samsung/n80xx-common/ueventd.smdk4x12.rc:root/ueventd.smdk4x12.rc ignored.
PRODUCT_COPY_FILES device/samsung/n80xx-common/ueventd.smdk4x12.rc:recovery/root/ueventd.smdk4x12.rc ignored.
PRODUCT_COPY_FILES device/samsung/n80xx-common/configs/audio_policy.conf:system/etc/audio_policy.conf ignored.
build/core/Makefile:54: Duplicate header copy: /home/erik/halium/out/target/product/n8000/obj/include/libsecmm/mfc_errno.h
build/core/Makefile:54: Defined in: hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk
build/core/Makefile:54: Duplicate header copy: /home/erik/halium/out/target/product/n8000/obj/include/libsecmm/mfc_interface.h
build/core/Makefile:54: Defined in: hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk
build/core/Makefile:54: Duplicate header copy: /home/erik/halium/out/target/product/n8000/obj/include/libsecmm/SsbSipMfcApi.h
build/core/Makefile:54: Defined in: hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk hardware/samsung/exynos/multimedia/codecs/video/exynos4/mfc/Android.mk
No private recovery resources for TARGET_DEVICE n8000
vendor/cm/build/tasks/kernel.mk:159: ***************************************************************
vendor/cm/build/tasks/kernel.mk:160: * Using prebuilt kernel binary instead of source              *
vendor/cm/build/tasks/kernel.mk:161: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED                *
vendor/cm/build/tasks/kernel.mk:162: * Please configure your device to download the kernel         *
vendor/cm/build/tasks/kernel.mk:163: * source repository to kernel/samsung/smdk4412
vendor/cm/build/tasks/kernel.mk:164: * for more information                                        *
vendor/cm/build/tasks/kernel.mk:165: ***************************************************************
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/erik/halium/out/target/product/n8000/kernel', needed by '/home/erik/halium/out/target/product/n8000/obj/ROOT/halium-boot_intermediates/halium-boot.img', missing and no known rule to make it
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1

#### make failed to build some targets (12 seconds) ####
                K 1 Reply Last reply Reply Quote 0
                • K
                  KingProNoob2 @KingProNoob2
                  last edited by

                  @Keneda God, so many errors this day... https://paste.ubuntu.com/p/75MvCc7DSx/

                  KenedaK 1 Reply Last reply Reply Quote 0
                  • KenedaK
                    Keneda @KingProNoob2
                    last edited by Keneda

                    @kingpronoob2
                    Just to be clear, i'm not a porter and have no porting (or dev) skills πŸ˜…
                    I asked you about device and pointed lineage device page to be sure there was no issue there ^^

                    2015-2023 : Meizu MX4 now in legacy drawer by lack of pristine battery 😫
                    2023-***** : Nexus 5 (16.04 OTA 25) for daily use, slowly dying πŸ€•
                    2024-***** : Fairphone 5 waiting UT for freedom πŸ˜‰
                    πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

                    1 Reply Last reply Reply Quote 0
                    • M
                      Marsh_Jiang @KingProNoob2
                      last edited by

                      @kingpronoob2 I have the same problem when porting, how did you solve this problem？

                      1 Reply Last reply Reply Quote 0
                      • P
                        pe3noATo2DOTpl
                        last edited by

                        Hello Dear @KingProNoob2, @Marsh_Jiang and other UBports Firends πŸ™‚

                        13.1). Did you get any progress and/or do you continue your efforts?

                        13.2). I found the quite fresh LineageOs 19.1 for N80xx here:
                        https://xdaforums.com/t/lineageos-19-1-android-12l-for-gt-n8000-gt-n8005-gt-n8010-gt-n8013-gt-n8020-beta.4363603/

                        13.3). I would be happy to get involved to help somehow to someone who could try to port this device to Ubuntu Touch 20.04 πŸ™‚

                        Thank you and kind regards~~ Piotrek~~pe3no.

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