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

    Porting to the Samsung Galaxy A10

    Scheduled Pinned Locked Moved Porting
    porting
    6 Posts 4 Posters 3.0k Views 2 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.
      • A Offline
        actuday6418
        last edited by

        Hey I've been trying to port Ubuntu touch to the A10 following the official guide located here. I've found the device repository for the a10 here, and vendor blobs here. So the XML manifest file I ended up with is this:

        <?xml version="1.0" encoding="UTF-8"?>
        <manifest>
                <remote name="a10_remote" fetch = "https://github.com/geckyn" revision="lineage-16.0"/>
                <project path="device/samsung/a10" name="android_device_samsung_a10" remote="a10_remote"/>
                <project path="kernel/samsung/a10" name="android_kernel_samsung_exynos7885" remote="a10_remote"/>
                <project path = "vendor/samsung/a10" name="proprietary_vendor_samsung_a10" remote="a10_remote"/>
        </manifest>
        

        The ./halium/devices/setup a10 command exits with no errors. But then when I run breakfast a10, I get the following output:

        build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10".  Stop.
        build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_a10".  Stop.
        build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
        Device a10 not found. Attempting to retrieve device repository from LineageOS Github http://github.com/LineageOS.
        Repository for a10 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your lo
        cal_manifests/roomservice.xml.
        build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
        build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
        
        ** Don't have a product spec for: 'lineage_a10'
        ** Do you have the right repo manifest?
        

        The A10 doesn't have an official Lineage OS port, in my knowledge, so I understand that there would be no reference to it on Lineage's GitHub. And I don't mention this repository in my manifest. Why do I get this error then?

        These errors above were generated when using Halium 7.1 with unofficial Lineage OS 16.0 sources, because the A10 shipped with Android 9. I tried to use this command:

        repo init -u https://github.com/Halium/android -b halium-9.0 --depth=1
        

        instead to match the Hallium version with the Lineage OS version. However, I can't find the Halium directory mentioned in the docs when executing the command with this version of Halium. How can I find a work around for this issue?

        The A10 is a project Treble enabled device, so would the GSI be the only way to get Ubuntu touch working?

        A supervisorS T 3 Replies Last reply Reply Quote 0
        • A Offline
          actuday6418 @actuday6418
          last edited by

          I was made aware of the Halium 9 porting guide on GitHub, so I'm trying to follow that right now.

          1 Reply Last reply Reply Quote 1
          • supervisorS Offline
            supervisor @actuday6418
            last edited by

            @actuday6418 soooo what happened?

            I LOVE COOKED ORANGES

            1 Reply Last reply Reply Quote 0
            • L Offline
              L-01074
              last edited by

              This post is deleted!
              T 1 Reply Last reply Reply Quote 0
              • T Offline
                TheVancedGamer @L-01074
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • T Offline
                  TheVancedGamer @actuday6418
                  last edited by

                  @actuday6418 You're supposed to use the standalone kernel method for porting all devices from Android 9 and up that ship with Treble. https://pad.ubports.com/p/treble-device-adaptation may help you

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