UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Fray_Tormenta
    F
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 10
    • Groups 0

    Fray_Tormenta

    @Fray_Tormenta

    3
    Reputation
    3
    Profile views
    10
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    Fray_Tormenta Unfollow Follow

    Best posts made by Fray_Tormenta

    • RE: Need Help for Redmi Note 12 pro plus 5g (22101316UP)

      Sure, just post what step are u done!

      posted in Porting
      F
      Fray_Tormenta

    Latest posts made by Fray_Tormenta

    • RE: Need Help for Redmi Note 12 pro plus 5g (22101316UP)

      Sure, just post what step are u done!

      posted in Porting
      F
      Fray_Tormenta
    • RE: I'm collecting halium for samsung m31

      follow the error guide from halium build.
      https://docs.halium.org/en/latest/porting/common-system-build-errors.html#common-system-build-errors

      Under title: signapk.jar missing

      This error is because some parts of code have missing dependency with some android/Java packages, so wich devices files need specifically modifications

      posted in Porting
      F
      Fray_Tormenta
    • RE: halium 10 on samsung M31

      try with this manifest file.

      <?xml version="1.0" encoding="UTF-8"?>
      <manifest>

      <project path="device/samsung/m31" remote="github" revision="lineage-17.1" />
      <project path="device/samsung/universal9610-common" name="android_device_samsung_universal9610-common" remote="github" revision="lineage-17.1" />
      <project path="device/samsung/m31" name="android_device_samsung_m31" remote="github" revision="lineage-17.1" />
      <project path="kernel/samsung/m31" name="android_kernel_samsung_universal9610" remote="github" revision="lineage-17.1" />
      <project path="vendor/samsung" name="proprietary_vendor_samsung" remote="github" revision="lineage-17.1" />
      

      </manifest>

      posted in Porting
      F
      Fray_Tormenta
    • RE: Can not locate config makefile for product

      it's by bad repo manifest. See the paths maybe it's wrong formed

      posted in Porting
      F
      Fray_Tormenta
    • RE: Support for galaxy tab S2

      Hello!

      @nishanthkvasan may be i can help you. But the process it's incomplete, i got a error while compile. The rest of steps like to manifest file, it's done.

      about the error i find that is about the kernel threads of some UUID.

      Manifest file
      https://forums.ubports.com/topic/6088/trouble-porting-halium-to-new-device-gts210vewifi?_=1710091107817

      Error
      https://forums.ubports.com/topic/9446/error-while-building-halium-boot-samsung-device?_=1710091107826

      posted in Porting
      F
      Fray_Tormenta
    • RE: Trouble porting halium to new device gts210vewifi

      @Fray_Tormenta
      Correct manifest file

      <?xml version="1.0" encoding="UTF-8"?>
      <manifest>
        <project name="dantecpu/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.1" />
        <project name="dantecpu/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-17.1" />
        <project name="dantecpu/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-17.1" />
        <project name="dantecpu/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-17.1" />
        <project name="dantecpu/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-17.1" />
        <project name="dantecpu/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-17.1" />
      </manifest>
      
      posted in Porting
      F
      Fray_Tormenta
    • error while building halium-boot Samsung device

      Hello community!

      I try porting the device Samsung Tab S2 (gts210vewifi).
      HOST MACHINE:
      Ubuntu 20.04.6 LTS
      Kernel: 20.04.6 LTS

      Target device:
      Samsung S2 9" (gts210vewifi)
      Lineage OS 16

      Build
      halium9
      Ubuntu Touch OS 16

      In the Build step when run "mka halium-boot" got the above error.

      ============================================
      PLATFORM_VERSION_CODENAME=REL
      PLATFORM_VERSION=9
      LINEAGE_VERSION=16.0-20231014-UNOFFICIAL-gts210vewifi
      TARGET_PRODUCT=lineage_gts210vewifi
      TARGET_BUILD_VARIANT=userdebug
      TARGET_BUILD_TYPE=release
      TARGET_ARCH=arm64
      TARGET_ARCH_VARIANT=armv8-a
      TARGET_CPU_VARIANT=generic
      TARGET_2ND_ARCH=arm
      TARGET_2ND_ARCH_VARIANT=armv8-a
      TARGET_2ND_CPU_VARIANT=generic
      HOST_ARCH=x86_64
      HOST_2ND_ARCH=x86
      HOST_OS=linux
      HOST_OS_EXTRA=Linux-5.15.0-86-generic-x86_64-Ubuntu-20.04.6-LTS
      HOST_CROSS_OS=windows
      HOST_CROSS_ARCH=x86
      HOST_CROSS_2ND_ARCH=x86_64
      HOST_BUILD_TYPE=release
      BUILD_ID=PQ3A.190801.002
      OUT_DIR=/home/ubuntu/halium9/out
      PRODUCT_SOONG_NAMESPACES=device/samsung/msm8976-common hardware/qcom/audio-caf/msm8952 hardware/qcom/display-caf/msm8952 hardware/qcom/media-caf/msm8952
      ============================================
      ninja: no work to do.
      ninja: no work to do.
      No need to regenerate ninja file
      No need to regenerate ninja file
      [ 25% 2/8] Building Kernel Config
      make: se entra en el directorio '/home/ubuntu/halium9/kernel/samsung/msm8976'
      
      In file included from /home/ubuntu/halium9/kernel/samsung/msm8976/include/linux/sched.h:52:0,
                       from /home/ubuntu/halium9/kernel/samsung/msm8976/arch/arm64/include/asm/compat.h:25,
                       from /home/ubuntu/halium9/kernel/samsung/msm8976/arch/arm64/include/asm/stat.h:23,
                       from /home/ubuntu/halium9/kernel/samsung/msm8976/include/linux/stat.h:5,
                       from /home/ubuntu/halium9/kernel/samsung/msm8976/include/linux/fs.h:10,
                       from /home/ubuntu/halium9/kernel/samsung/msm8976/fs/ext4/namei.c:27:
      /home/ubuntu/halium9/kernel/samsung/msm8976/fs/ext4/namei.c: In function 'ext4_unlink':
      /home/ubuntu/halium9/kernel/samsung/msm8976/include/linux/cred.h:341:24: error: used struct type value where scalar is required
       #define current_uid()  (current_cred_xxx(uid))
                              ^
      /home/ubuntu/halium9/kernel/samsung/msm8976/fs/ext4/namei.c:2818:5: note: in expansion of macro 'current_uid'
        if(current_uid()) {
           ^
      /home/ubuntu/halium9/kernel/samsung/msm8976/fs/ext4/namei.c:2819:3: error: aggregate value used where an integer was expected
         inode->i_version |= (u64)current_uid() << 32;
         ^
      make[3]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/scripts/Makefile.build:308: fs/ext4/namei.o] Error 1
      make[2]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/scripts/Makefile.build:455: fs/ext4] Error 2
      make[1]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/Makefile:836: fs] Error 2
      make[1]: *** Se espera a que terminen otras tareas....
        ...
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cgroup.c: In function 'subsys_cgroup_allow_attach':
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cgroup.c:2138:37: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
         if (current != task && cred->euid != tcred->uid &&
                                           ^
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cgroup.c:2139:18: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
             cred->euid != tcred->suid)
                        ^
      make[2]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/scripts/Makefile.build:308: kernel/cgroup.o] Error 1
      make[2]: *** Se espera a que terminen otras tareas....
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cpuset.c: In function 'cpuset_allow_attach':
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cpuset.c:1433:18: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
             cred->euid != tcred->uid && cred->euid != tcred->suid)
                        ^
      /home/ubuntu/halium9/kernel/samsung/msm8976/kernel/cpuset.c:1433:46: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
             cred->euid != tcred->uid && cred->euid != tcred->suid)
                                                    ^
      make[2]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/scripts/Makefile.build:308: kernel/cpuset.o] Error 1
      make[1]: *** [/home/ubuntu/halium9/kernel/samsung/msm8976/Makefile:836: kernel] Error 2
      make: *** [Makefile:130: sub-make] Error 2
      make: se sale del directorio '/home/ubuntu/halium9/kernel/samsung/msm8976'
      ninja: build stopped: subcommand failed.
      22:07:50 ninja failed with: exit status 1
      
      #### failed to build some targets (02:01 (mm:ss)) ####
      
      
      

      In this line have the first error

      /home/ubuntu/halium9/kernel/samsung/msm8976/include/linux/cred.h:341:24: error: used struct type value where scalar is required
       #define current_uid()  (current_cred_xxx(uid))
      

      And well when run the cat command at these file "cred.h" got this.
      I applied a grep filter for the "uid"

      cat kernel/samsung/msm8976/include/linux/cred.h | grep -n "uid"
      20:#include <linux/uidgid.h>
      113:	kuid_t		uid;		/* real UID of the task */
      115:	kuid_t		suid;		/* saved UID of the task */
      117:	kuid_t		euid;		/* effective UID of the task */
      119:	kuid_t		fsuid;		/* UID for VFS ops */
      140:	struct group_info *group_info;	/* supplementary groups for euid/fsgid */
      305:	__u = get_uid(__cred->user);			\
      333:#define task_uid(task)		(task_cred_xxx((task), uid))
      334:#define task_euid(task)		(task_cred_xxx((task), euid))
      341:#define current_uid()		(current_cred_xxx(uid))
      343:#define current_euid()		(current_cred_xxx(euid))
      345:#define current_suid()		(current_cred_xxx(suid))
      347:#define current_fsuid() 	(current_cred_xxx(fsuid))
      364:#define current_uid_gid(_uid, _gid)		\
      368:	*(_uid) = __cred->uid;			\
      372:#define current_euid_egid(_euid, _egid)		\
      376:	*(_euid) = __cred->euid;		\
      380:#define current_fsuid_fsgid(_fsuid, _fsgid)	\
      384:	*(_fsuid) = __cred->fsuid;		\
      

      I can more or less understand the syntax but I can't recognize how to resolve the errors.
      This guy have the similar error: https://forums.ubports.com/topic/8701/error-in-mka-halium-boot

      I hope your help, thanks in advance.

      posted in Porting
      F
      Fray_Tormenta
    • Trouble porting halium to new device gts210vewifi

      Hello.

      I followed the instructions for port halium to a new device. Exactly in the step for create the manifest, I have trouble.

      This is my manifest file.

      <?xml version="1.0" encoding="UTF-8"?> 
      <manifest> 
      <remote name="mictlan" fetch="https://github.com/mictlantecuhtli420"/>
      
      <project path="kernel/samsung/msm8976" name="android_kernel_samsung_msm8976" remote="los" revision="lineage-16.0" />
      <project path="hardware/samsung" name="android_hardware_samsung" remote="los" revision="lineage-16.0" />
      <project path="hardware/sony/timekeep" name="android_hardware_sony_timekeep" remote="los" revision="lineage-16.0" />
      <project path="device/samsung/msm8976-common" name="android_device_samsung_msm8976-common" remote="los" revision="lineage-16.0" />
      
      <project path="gts210vewifi" name="proprietary_vendor_samsung" remote="mictlan" />
      <project path="msm8976-common" name="proprietary_vendor_samsung" remote="mictlan"/>
      </manifest>
      

      Manifest.png

      When I run the Sync command, "./halium/devices/setup gts210vewifi.xml" I got the follow response.

      setup.png

      I don´t understand, why not found the device? Maybe for the name? Do i need pull my manifest in the Lineage repos?

      Manifest.png

      In the "../.repo/manifest.xml I have this

      manifestDefault.png

      in the instructions not say about need edit this file.

      when trying use the "source build/envsetup.sh" and " breakfast" command I have the same response,
      "** Don't have a product spec for: 'lineage_gts210vewifi'
      ** Do you have the right repo manifest?"

      And well I hope u can help me, in special with the manifest for my device, maybe the structure is wrong (I think is this the origin of the trouble), I have the vendor blobs in github and the "physical files" in my PC.

      Thanks for advance

      posted in Porting
      F
      Fray_Tormenta