search

Halium / projectmanagement

141 stars 32 forks source link

[device-port] [espresso3g/espressowifi] Samsung Galaxy Tab 2 #238

Open MightyM17 opened 3 years ago

MightyM17 commented 3 years ago

Tree: halium-7.1

=== Sensor 1 == Name: MS-3E (YAS530) Magnetic Sensor Vendor: Yamaha Corporation Version: 0x1 Handle: 0x2 Type: 2 maxRange: 800.0 resolution: 0.300000 power: 4.0 mA minDelay: 10000

=== Sensor 2 == Name: MS-x Orientation Sensor Vendor: Yamaha Corporation Version: 0x1 Handle: 0x3 Type: 3 maxRange: 360.0 resolution: 0.100000 power: 0.0 mA minDelay: 10000

=== Sensor 3 == Name: GP2AP002 Light Sensor Vendor: Sharp Version: 0x1 Handle: 0x4 Type: 5 maxRange: 0.0 resolution: 0.0 power: 0.0 mA minDelay: 0

=== Sensor 4 == Name: GP2AP002 Proximity Sensor Vendor: Sharp Version: 0x1 Handle: 0x5 Type: 8 maxRange: 5.0 resolution: 0.0 power: 0.0 mA minDelay: 0

  * [ ] test_audio

phablet@ubuntu-phablet:~$ test_audio Audio device API version 0200 doesn't match platform current 3004.test_audio: test_audio.c:71: main: Assertion `audiohw->common.version == AUDIO_DEVICE_API_VERSION_CURRENT' failed. Aborted

  * [ ] test_camera

phablet@ubuntu-phablet:~$ test_camera Problem connecting to camera

  * [x] test_input

phablet@ubuntu-phablet:~$ test_input fatal error opening "/sys/power/wake_lock": Permission denied fatal error opening "/sys/android_power/acquire_partial_wake_lock": No such file or directory

  * [ ] test_recorder

^Cphablet@ubuntu-phablet:~$ test_recorder Test application for video recording using the camera Recording start with volume up button. And stops with volume down. The result is stored to /root/test_video.avi



<!-- 
Other information goes below this comment. Possible topics of comment may 
include special flashing or building instructions, such as manual effort to
change vendor files.
-->
MightyM17 commented 2 years ago

Great! Now u can do whatever mka/make commands were there

yxles-dev commented 2 years ago

Great! Now u can do whatever mka/make commands were there

Thx, didn't know that you dont need to execute breakfast after doing that but executing mka mkbootimg I have 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/deniel/halium/out/build-aosp_espresso3g.ninja] Error 1
make: Leaving directory '/home/deniel/halium'

#### make failed to build some targets (33 seconds) ####
MightyM17 commented 2 years ago

Did repo sync finish successfully? Never faced missing external/gpg/Android.mk file https://github.com/Halium/projectmanagement/issues/296 have a look here

yxles-dev commented 2 years ago

Did repo sync finish successfully? Never faced missing external/gpg/Android.mk file #296 have a look here

Yes, I actually did it twice and its still errors out but looking at #296 I found this

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/rhino/halium-7.1/out/build-lineage_chagallwifi.ninja] Error 1 make: Leaving directory '/home/rhino/halium-7.1'

add line to samsung_chagallwifi.xnl my fix No such file external/gpg/Android.mk

./halium/devices/setup chagallwifi

But I'm confused if they're talking about the manifest on samsung_chagallwifi.xnl (xml) and if so where am I gonna add it there.

MightyM17 commented 2 years ago

Sorry for the late replies, never faced this issue, does the file external/gpg/Android.mk exists for you?

MightyM17 commented 2 years ago

https://github.com/Halium/android/blob/halium-5.1/default.xml#L70 and https://github.com/Halium/android/pull/49/files are some leads I could find

yxles-dev commented 2 years ago

@MightyM17

Where does it say that removing device/sample is gonna fix it?

the line

device/sample/frameworks/PlatformLibrary/Android.mk:37: build/core/java_library.mk: No such file or directory

When it tries to build the device/sample, it looks for that file but since it doesn't exist for me it just errors out and stop the building so I just deleted it (temporarily) to see if it fix it and it did build without errors but I'm guessing that if I build it without the sample I may have problems later if not now

MightyM17 commented 2 years ago

Nah as stated before device/sample is only needed for the APN list, you can work without it causing major troubles

yxles-dev commented 2 years ago

what about here?

ok now mka mkbootimg completed successfully as well as export USE_HOST_LEX=yes mka halium-boot but without the device/sample but now when executing mka systemimage I got this 

Running kati to generate build-aosp_espresso3g.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/yxles/halium/out/target/product/espresso3g/obj/SHARED_LIBRARIES/libdl_intermediates/export_includes', needed by '/home/yxles/halium/out/target/product/espresso3g/obj/EXECUTABLES/applypatch_intermediates/import_includes', missing and no known rule to make it
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/yxles/halium'

I'm guessing this error was caused by me removing bionic/libdl but when I dont remove that it will error out this

hey its you, thx for helping me with this but there's another problem. So I downloaded the master branch of gpg here https://github.com/ubports/android_external_gpg and paste it on the external folder. Now when I execute mka mkbootimg I got this error

build/core/base_rules.mk:183: *** external/gpg: MODULE.TARGET.STATIC_LIBRARIES.libdl already defined by bionic/libdl.
make: *** [build/core/ninja.mk:167: /home/yxles/halium/out/build-aosp_espresso3g.ninja] Error 1
make: Leaving directory '/home/yxles/halium'
yxles-dev commented 2 years ago 
build/core/base_rules.mk:183: *** external/gpg: MODULE.TARGET.STATIC_LIBRARIES.libdl already defined by bionic/libdl.
make: *** [build/core/ninja.mk:167: /home/yxles/halium/out/build-aosp_espresso3g.ninja] Error 1
make: Leaving directory '/home/yxles/halium'

If you encounter this, use the halium-9.0 branch of gpg [https://github.com/ubports/android_external_gpg] not the master so that way you dont need to mess with bionic/libdl

yxles-dev commented 2 years ago

Ok so another problem out of infinite, executing export USE_HOST_LEX=yes mka halium-boot with a patched config (using the command ./halium/halium-boot/check-kernel-config /home/yxles/halium/kernel/ti/omap4/arch/arm/configs/espresso_defconfig -w will result to this error:

  CC      arch/arm/mach-omap2/omap5_ion.o
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap4_ion.c: In function 'omap4_ion_init':
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap4_ion.c:84:36: warning: comparison between 'enum ion_heap_type' and 'enum <anonymous>' [-Wenum-compare]
       omap4_ion_data.heaps[i].type == OMAP_ION_HEAP_TILER) {
                                    ^
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap5_ion.c: In function 'omap5_ion_init':
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap5_ion.c:84:36: warning: comparison between 'enum ion_heap_type' and 'enum <anonymous>' [-Wenum-compare]
       omap5_ion_data.heaps[i].type == OMAP_ION_HEAP_TILER) {
                                    ^
  CC      arch/arm/mach-omap2/omap_ram_console.o
  CC      arch/arm/mach-omap2/omap_gcxxx.o
  LD      arch/arm/mach-omap2/mailbox_mach.o
  LD      arch/arm/mach-omap2/built-in.o
make: *** [Makefile:130: sub-make] Error 2
make: Leaving directory '/home/yxles/halium/kernel/ti/omap4'
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/yxles/halium'

#### make failed to build some targets (23 seconds) ####

@MightyM17

yxles-dev commented 2 years ago

@MightyM17

Where does it say that removing device/sample is gonna fix it?

the line

device/sample/frameworks/PlatformLibrary/Android.mk:37: build/core/java_library.mk: No such file or directory

When it tries to build the device/sample, it looks for that file but since it doesn't exist for me it just errors out and stop the building so I just deleted it (temporarily) to see if it fix it and it did build without errors but I'm guessing that if I build it without the sample I may have problems later if not now

My fix for this was to just remove everything BESIDE the etc folder since as stated before, APN was the only thing needed there

MightyM17 commented 2 years ago

Ok so another problem out of infinite, executing export USE_HOST_LEX=yes mka halium-boot with a patched config (using the command ./halium/halium-boot/check-kernel-config /home/yxles/halium/kernel/ti/omap4/arch/arm/configs/espresso_defconfig -w will result to this error:

  CC      arch/arm/mach-omap2/omap5_ion.o
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap4_ion.c: In function 'omap4_ion_init':
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap4_ion.c:84:36: warning: comparison between 'enum ion_heap_type' and 'enum <anonymous>' [-Wenum-compare]
       omap4_ion_data.heaps[i].type == OMAP_ION_HEAP_TILER) {
                                    ^
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap5_ion.c: In function 'omap5_ion_init':
/home/yxles/halium/kernel/ti/omap4/arch/arm/mach-omap2/omap5_ion.c:84:36: warning: comparison between 'enum ion_heap_type' and 'enum <anonymous>' [-Wenum-compare]
       omap5_ion_data.heaps[i].type == OMAP_ION_HEAP_TILER) {
                                    ^
  CC      arch/arm/mach-omap2/omap_ram_console.o
  CC      arch/arm/mach-omap2/omap_gcxxx.o
  LD      arch/arm/mach-omap2/mailbox_mach.o
  LD      arch/arm/mach-omap2/built-in.o
make: *** [Makefile:130: sub-make] Error 2
make: Leaving directory '/home/yxles/halium/kernel/ti/omap4'
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/yxles/halium'

#### make failed to build some targets (23 seconds) ####

@MightyM17

The error is not in here, check above in the logs

MightyM17 commented 2 years ago

Also I already have the config patched, why do you need to do it again?

yxles-dev commented 2 years ago

Also you need to change the defconfig, add these to espresso_defconfig

CONFIG_KERNEL_GZIP=n
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_KERNEL_XZ=y

(Also do the normal ubports/halium changes)

I'll try again without patching it

yxles-dev commented 2 years ago

Ey I got to 36% at mka systemimage then it errors out this

2 warnings generated.
[ 36% 5498/15058] Generated: (/home/yx...t/product/espresso3g/android-info.txt)
FAILED: /home/yxles/halium/out/target/product/espresso3g/android-info.txt 
/bin/bash -c "(build/tools/check_radio_versions.py ) && (echo \"board=piranha\" > /home/yxles/halium/out/target/product/espresso3g/android-info.txt )"
  File "/home/yxles/halium/build/tools/check_radio_versions.py", line 56
    print "*** Error opening \"%s.sha1\"; can't verify %s" % (fn, key)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
[ 36% 5498/15058] host C: checkpolicy ...al/selinux/checkpolicy/policy_define.c
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/yxles/halium'

#### make failed to build some targets (12:04 (mm:ss)) ####
MightyM17 commented 1 year ago

Did you manage to fix it?

massimo1980 commented 1 year ago

Hi there, i'm trying to build an image for my old P5100 following the official halium doc and your commets i've managed to complete the build the boot image: mka mkbootimg mka halium-boot ( this log was pretty long ..so i snipped the middle part. Anyway i've got the log file if you need it )

But once i try to make the system image it returns this error:

max@NEWMILLENNIUM:~/halium$ mka systemimage
make: Entering directory '/home/max/halium'
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20221118-UNOFFICIAL-espresso3g
TARGET_PRODUCT=lineage_espresso3g
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.15.74.2-microsoft-standard-WSL2-x86_64-with-glibc2.10
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NOF27B
OUT_DIR=/home/max/halium/out
============================================
Running kati to generate build-lineage_espresso3g.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'libsrv_init', needed by '/home/max/halium/out/target/product/espresso3g/obj/EXECUTABLES/pvrsrvinit_intermediates/pvrsrvinit.o', missing and no known rule to make it
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/max/halium'

#### make failed to build some targets  ####

(base) max@NEWMILLENNIUM:~/halium$

I've tried to install the boot image on my tablet anyway using TWRP recovery mode i get this error: Size of image is larger than target device

Any advice?

Thank you in advance for you support

MightyM17 commented 1 year ago

Hey there! Well I suppose you did use my trees as that makes the boot.img fit into out partition. But it looks like the systemimage is not built at all due to ninja: error: 'libsrv_init' Please use proper sources for hardware/ti

massimo1980 commented 1 year ago

Hi Mighty and tnx for you quick reply. Actually i've not used your xml config file. I have tried this one:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <project path="device/samsung/p5100" name="android_device_samsung_p5100" remote="los" revision="cm-10.1" />
        <project path="device/samsung/omap4-common" name="android_device_samsung_omap4-common" remote="los" revision="cm-10.1" />
        <project path="kernel/samsung/espresso10" name="android_kernel_samsung_espresso10" remote="los" revision="cm-10.1" />
        <project path="packages/apps/SamsungServiceMode" name="android_packages_apps_SamsungServiceMode" remote="los" revision="cm-10.1" />
        <project path="device/samsung/espresso3g" name="android_device_samsung_espresso3g" remote="los" revision="cm-11.0" />
        <project path="device/samsung/espressowifi" name="android_device_samsung_espressowifi" remote="los" revision="cm-11.0" />
        <project path="device/samsung/espresso-common" name="android_device_samsung_espresso-common" remote="los" revision="cm-10.2" />
        <project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="los" revision="cm-11.0" />
        <project path="kernel/ti/omap4" name="android_kernel_ti_omap4" remote="los" revision="cm-11.0" />
</manifest>

sorry for the dumb question: what do you mean for "use proper sources for hardware/ti" ?

Thanks again

MightyM17 commented 1 year ago

Hi Mighty and tnx for you quick reply. Actually i've not used your xml config file. I have tried this one:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <project path="device/samsung/p5100" name="android_device_samsung_p5100" remote="los" revision="cm-10.1" />
        <project path="device/samsung/omap4-common" name="android_device_samsung_omap4-common" remote="los" revision="cm-10.1" />
        <project path="kernel/samsung/espresso10" name="android_kernel_samsung_espresso10" remote="los" revision="cm-10.1" />
        <project path="packages/apps/SamsungServiceMode" name="android_packages_apps_SamsungServiceMode" remote="los" revision="cm-10.1" />
        <project path="device/samsung/espresso3g" name="android_device_samsung_espresso3g" remote="los" revision="cm-11.0" />
        <project path="device/samsung/espressowifi" name="android_device_samsung_espressowifi" remote="los" revision="cm-11.0" />
        <project path="device/samsung/espresso-common" name="android_device_samsung_espresso-common" remote="los" revision="cm-10.2" />
        <project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="los" revision="cm-11.0" />
        <project path="kernel/ti/omap4" name="android_kernel_ti_omap4" remote="los" revision="cm-11.0" />
</manifest>

sorry for the dumb question: what do you mean for "use proper sources for hardware/ti" ?

Thanks again

I dont know if this would work or not. I tried lots of combinations and finally the one i used worked hence the suggestion. There have been quite some changes in the android_hardware_ti_omap4 hence sticking to AOSP/Unlegacy Android. P.S. Why are you using so many different branches, cm11, cm10,2, cm10.1 (they are ancient) Plus we are building android 7.1.1 while cm10.1 is like 4.x

massimo1980 commented 1 year ago

i have used cm-10.1 cause, reading the docs, i've understood to use the same version of LineageOS installed on the tablet. so, where there wasn't that version, i choose the next one i will try to update to current version... let's see what happens. can you please share your xml config file, so i can try with yours ?

Thank you very much for your patience!

MightyM17 commented 1 year ago

I'll put the repo links here device/samsung/espresso - https://github.com/Unlegacy-Android/android_device_samsung_espresso device/samsung/espresso3g - https://github.com/Unlegacy-Android/android_device_samsung_espresso3g device/sample - https://android.googlesource.com/device/sample (only needed for espresso3g because of

# Get the long list of APNs
PRODUCT_COPY_FILES += \
    device/sample/etc/apns-full-conf.xml:system/etc/apns-conf.xml

can remove this line kernel/ti/omap4 - https://github.com/MightyM17/android_kernel_ti_omap4/tree/halium hardware/ti/omap4 - https://github.com/Unlegacy-Android/android_hardware_ti_omap4 vendor/ti - https://github.com/Unlegacy-Android/proprietary_vendor_ti vendor/samsung - https://github.com/Unlegacy-Android/proprietary_vendor_samsung

Please refer to this, I do not have a config file on my machine currently sorry

massimo1980 commented 1 year ago

Ok ...so ...i've used your repo indication and restart everything from scratch:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <remote  name="espresso" fetch="https://github.com/Unlegacy-Android/" revision="aosp-7.1" />
        <remote  name="device-sample" fetch="https://android.googlesource.com/" revision="nougat-release" />

        <project path="device/samsung/espresso" name="android_device_samsung_espresso" remote="espresso" />
        <project path="device/samsung/espresso3g" name="android_device_samsung_espresso3g" remote="espresso" />

        <!-- Project Depedencies -->
        <project path="device/sample" name="device/sample" remote="device-sample" revision="nougat-release" />
        <project path="kernel/ti/omap4" name="android_kernel_ti_omap4" remote="espresso" revision="3.4/espresso" />
        <project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="espresso" revision="stable" />
        <project path="vendor/ti" name="proprietary_vendor_ti" remote="espresso" revision="aosp-7.0" />
        <project path="vendor/samsung" name="proprietary_vendor_samsung" remote="espresso" revision="aosp-7.1" />
</manifest>

after resynced, "breakfast" command didn't work anymore:

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_espresso3g".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_espresso3g".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_espresso3g".  Stop.
Device espresso3g not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_samsung_espresso3g
Traceback (most recent call last):
  File "vendor/cm/build/tools/roomservice.py", line 263, in <module>
    default_revision = get_default_revision()
  File "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_espresso3g".  Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_espresso3g".  Stop.

** Don't have a product spec for: 'lineage_espresso3g'
** Do you have the right repo manifest?

so....using "lunch" command i choosed "aosp_espresso3g-userdebug" after using the "check-kernel-config" script: ./halium/halium-boot/check-kernel-config ./kernel/ti/omap4/arch/arm/configs/espresso_defconfig -w i runned "mka mkbootimg" without error

for the "hybris-boot" i have encountered a fir issue with "dtc-lexer.lex.c" file: vi out/target/product/espresso3g/obj/KERNEL_OBJ/scripts/dtc/dtc-lexer.lex.c changing "YYLTYPE yylloc;" to "extern YYLTYPE yylloc;"

but now i'm stuck on this errors:

/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c: In function 'mpihelp_mod_1':
/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:68:3: error: too many arguments to function 'count_leading_zeros'
   count_leading_zeros(normalization_steps, divisor_limb);
/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:145:4: error: too many arguments to function 'count_leading_zeros'
    count_leading_zeros(normalization_steps, divisor_limb);
    ^
In file included from /home/max/halium/kernel/ti/omap4/lib/mpi/longlong.h:22:0,
                 from /home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:31:
/home/max/halium/kernel/ti/omap4/include/asm-generic/bitops/count_zeros.h:27:19: note: declared here
 static inline int count_leading_zeros(unsigned long x)
                   ^
  CC      net/key/af_key.o
/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c: In function 'mpihelp_divmod_1':
/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:424:3: error: too many arguments to function 'count_leading_zeros'
   count_leading_zeros(normalization_steps, divisor_limb);
   ^
In file included from /home/max/halium/kernel/ti/omap4/lib/mpi/longlong.h:22:0,
                 from /home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:31:
/home/max/halium/kernel/ti/omap4/include/asm-generic/bitops/count_zeros.h:27:19: note: declared here
 static inline int count_leading_zeros(unsigned long x)
                   ^
/home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:499:4: error: too many arguments to function 'count_leading_zeros'
    count_leading_zeros(normalization_steps, divisor_limb);
    ^
In file included from /home/max/halium/kernel/ti/omap4/lib/mpi/longlong.h:22:0,
                 from /home/max/halium/kernel/ti/omap4/lib/mpi/mpih-div.c:31:
/home/max/halium/kernel/ti/omap4/include/asm-generic/bitops/count_zeros.h:27:19: note: declared here
 static inline int count_leading_zeros(unsigned long x)
                   ^
make[3]: *** [/home/max/halium/kernel/ti/omap4/scripts/Makefile.build:307: lib/mpi/mpih-div.o] Error 1
make[2]: *** [/home/max/halium/kernel/ti/omap4/scripts/Makefile.build:454: lib/mpi] Error 2
make[1]: *** [/home/max/halium/kernel/ti/omap4/Makefile:958: lib] Error 2
make[1]: *** Waiting for unfinished jobs....

i'm actually loosing faith on this ....

MightyM17 commented 1 year ago

You still are using the wrong sources :(

massimo1980 commented 1 year ago

can you please point me which line is wrong in my repo file? i can't understand what do you mean for wrong sources.....do you mean the branch?

MightyM17 commented 1 year ago 

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <remote  name="espresso" fetch="https://github.com/Unlegacy-Android/" revision="aosp-7.1" />
        <remote  name="device-sample" fetch="https://android.googlesource.com/" revision="nougat-release" />
        <remote  name="mighty" fetch="https://github.com/MightyM17/" revision="halium" />

        <project path="device/samsung/espresso" name="android_device_samsung_espresso" remote="espresso" />
        <project path="device/samsung/espresso3g" name="android_device_samsung_espresso3g" remote="espresso" />

        <!-- Project Depedencies -->
        <project path="device/sample" name="device/sample" remote="device-sample" revision="nougat-release" />
        <project path="kernel/ti/omap4" name="android_kernel_ti_omap4" remote="mighty" revision="halium" />
        <project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="espresso" revision="stable" />
        <project path="vendor/ti" name="proprietary_vendor_ti" remote="espresso" revision="aosp-7.0" />
        <project path="vendor/samsung" name="proprietary_vendor_samsung" remote="espresso" revision="aosp-7.1" />
</manifest>
massimo1980 commented 1 year ago

@MightyM17 you're the best!!! seems that now i can build both "mkbootimg" and "hybris-boot" but when i run "mka systemimage" i get this error now:

Running kati to generate build-aosp_espresso3g.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'vendor/samsung/espresso3g/system/lib/libsec-ril.so', needed by '/home/max/halium/out/target/product/espresso3g/system/lib/libsec-ril.so', missing and no known rule to make it
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/max/halium'

#### make failed to build some targets  ####

working on it... EDIT: nevermind ....i've managed to resolve the errors and now i'm at:

[ 23% 3111/13018] target thumb C++: recovery <= bootable/recovery/recovery.cpp

massimo1980 commented 1 year ago 
FAILED: /bin/bash -c "(/home/max/halium/out/host/linux-x86/bin/aprotoc --proto_path=.  --nanopb_out=/home/max/halium/out/target/product/espresso3g/gen/STATIC_LIBRARIES/librilutils_static_intermediates/proto --plugin=external/nanopb-c/generator/protoc-gen-nanopb hardware/ril/librilutils/proto/sap-api.proto )"

         *************************************************************
         *** Could not import the Google protobuf Python libraries ***
         *** Try installing package 'python-protobuf' or similar.  ***
         *************************************************************

Traceback (most recent call last):
  File "external/nanopb-c/generator/nanopb_generator.py", line 17, in <module>
    import google.protobuf.text_format as text_format
  File "/home/max/halium/external/nanopb-c/generator/google/protobuf/text_format.py", line 406
    except ValueError, e:
                     ^
SyntaxError: invalid syntax

....and then ....probably wrong python version :joy: is there a working image of linux for P5100 that i can download?! :joy:

RealTheHexagon commented 1 year ago

Install Python2 and use a python2 venv. ArchWiki has good info about it

On Sun, 20 Nov 2022, 7:06 am Maxxam, @.***> wrote:

FAILED: /bin/bash -c "(/home/max/halium/out/host/linux-x86/bin/aprotoc --proto_path=. --nanopb_out=/home/max/halium/out/target/product/espresso3g/gen/STATIC_LIBRARIES/librilutils_static_intermediates/proto --plugin=external/nanopb-c/generator/protoc-gen-nanopb hardware/ril/librilutils/proto/sap-api.proto )"

     *************************************************************

     *** Could not import the Google protobuf Python libraries ***

     *** Try installing package 'python-protobuf' or similar.  ***

     *************************************************************

Traceback (most recent call last):

File "external/nanopb-c/generator/nanopb_generator.py", line 17, in 

import google.protobuf.text_format as text_format

File "/home/max/halium/external/nanopb-c/generator/google/protobuf/text_format.py", line 406

except ValueError, e:

                 ^

SyntaxError: invalid syntax

....and then ....probably wrong python version 😂 is there a working image of linux for P5100 that i can download?! 😂

— Reply to this email directly, view it on GitHub https://github.com/Halium/projectmanagement/issues/238#issuecomment-1320936969, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKWMSWK532ZCMX4TSUPMRDWJEJMFANCNFSM4WFDSUSA . You are receiving this because you commented.Message ID: @.***>

massimo1980 commented 1 year ago

fortunately i was just working on an anaconda environment...so i just switched python version now seems that is missing something:

make: Leaving directory '/home/max/halium/hardware/ti/omap4/pvr-source/eurasiacon/build/linux2/omap_android'
[ 99% 3408/3420] Target boot image for Ubuntu Touch: /home/max/halium/out/target/product/espresso3g/boot.img
/home/max/halium/out/target/product/espresso3g/boot.img maxsize=8562048 blocksize=4224 total=5332992 reserve=88704
[ 99% 3409/3420] ----- Making recovery ramdisk ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat '/home/max/halium/out/target/product/espresso3g/root/init.recovery.*.rc': No such file or directory
----- Making uncompressed recovery ramdisk ------
[ 99% 3411/3420] ----- Making recovery image ------
FAILED: /bin/bash -c "(/home/max/halium/out/host/linux-x86/bin/mkbootimg  --kernel /home/max/halium/out/target/product/espresso3g/kernel  --ramdisk /home/max/halium/out/target/product/espresso3g/ramdisk-recovery.img --cmdline \"androidboot.hardware=espresso buildvariant=userdebug\" --base 0x40000000 --pagesize 2048 --os_version 7.1.1 --os_patch_level 2017-03-05  --output  /home/max/halium/out/target/product/espresso3g/recovery.img --id > /home/max/halium/out/target/product/espresso3g/recovery.id ) && (size=\$(for i in  /home/max/halium/out/target/product/espresso3g/recovery.img; do stat --format \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \" /home/max/halium/out/target/product/espresso3g/recovery.img\" | tr \" \" +); img_blocksize=4224; twoblocks=\$((img_blocksize * 2)); onepct=\$(((((8650752 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=\$((twoblocks > onepct ? twoblocks : onepct)); maxsize=\$((8650752 - reserve)); echo \"\$printname maxsize=\$maxsize blocksize=\$img_blocksize total=\$total reserve=\$reserve\"; if [ \"\$total\" -gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > [8650752 - \$reserve])\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (echo ----- Made recovery image:  /home/max/halium/out/target/product/espresso3g/recovery.img -------- )"
+/home/max/halium/out/target/product/espresso3g/recovery.img maxsize=8562048 blocksize=4224 total=9267200 reserve=88704
error: +/home/max/halium/out/target/product/espresso3g/recovery.img too large (9267200 > [8650752 - 88704])
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/max/halium'

#### make failed to build some targets (01:19 (mm:ss)) ####

EDIT: i've copied the file init.recovery.espresso.rc directly from the los repo a little step forward...and now:

[ 82% 53/64] ----- Making recovery ramdisk ------
Copying baseline ramdisk...
Modifying ramdisk contents...
----- Making uncompressed recovery ramdisk ------
[ 85% 55/64] ----- Making recovery image ------
FAILED: /bin/bash -c "(/home/max/halium/out/host/linux-x86/bin/mkbootimg  --kernel /home/max/halium/out/target/product/espresso3g/kernel  --ramdisk /home/max/halium/out/target/product/espresso3g/ramdisk-recovery.img --cmdline \"androidboot.hardware=espresso buildvariant=userdebug\" --base 0x40000000 --pagesize 2048 --os_version 7.1.1 --os_patch_level 2017-03-05  --output  /home/max/halium/out/target/product/espresso3g/recovery.img --id > /home/max/halium/out/target/product/espresso3g/recovery.id ) && (size=\$(for i in  /home/max/halium/out/target/product/espresso3g/recovery.img; do stat --format \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \" /home/max/halium/out/target/product/espresso3g/recovery.img\" | tr \" \" +); img_blocksize=4224; twoblocks=\$((img_blocksize * 2)); onepct=\$(((((8650752 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=\$((twoblocks > onepct ? twoblocks : onepct)); maxsize=\$((8650752 - reserve)); echo \"\$printname maxsize=\$maxsize blocksize=\$img_blocksize total=\$total reserve=\$reserve\"; if [ \"\$total\" -gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > [8650752 - \$reserve])\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (echo ----- Made recovery image:  /home/max/halium/out/target/product/espresso3g/recovery.img -------- )"
+/home/max/halium/out/target/product/espresso3g/recovery.img maxsize=8562048 blocksize=4224 total=8824832 reserve=88704
error: +/home/max/halium/out/target/product/espresso3g/recovery.img too large (8824832 > [8650752 - 88704])
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
make: Leaving directory '/home/max/halium'

#### make failed to build some targets (49 seconds) ####
massimo1980 commented 1 year ago

i didn't find a way to resolve the issue about the recovery image size... playin around i found the file: device/samsung/espresso/BoardConfigCommon.mk I changed the value of BOARD_RECOVERYIMAGE_PARTITION_SIZE from 8388608 to 8824832 ( that was my last build size ) ( i made the change cause i was thinking to left the recovery partition of my tablet with TWRP installed ... don't know if it is a good idea ) so in the end the build runned successfully.....and the step was to test it I've used "halium-installer" as the docs says, downloaded the last rootfs tar.gz file ( ..and for those who are struggling ....DON'T USE WSL2. i made it run only on native linux ) and put the tablet in recovery mode: on halium docs says to use "-p halium" but gives me a lot of errors like "No space left on device" on ubport docs says to use "-p ut" ...and this one seems to works:

massimo@MILLENNIUM:~/halium-install$ sudo ./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img -v
D: Chosen rootfs is ubports-touch.rootfs-xenial-armhf.tar.gz
D: Chosen android image is system.img
D: Chosen release is ut
D: Compress images before pushing: false

I: Writing rootfs into mountable image
I: Writing android image into mountable image
I: Running post installation tasks
enabling SSH ... [done]
Please enter a new password for the user 'phablet':
Inserire nuova password UNIX:
Reinserire la nuova password UNIX:
passwd: password updated successfully
I: Shrinking images
e2fsck 1.46.5 (30-Dec-2021)
resize2fs 1.46.5 (30-Dec-2021)
Resizing the filesystem on .halium-install-imgs.ZDIkr/system.img to 28387 (4k) blocks.
Inizio del passo 2 (max = 221)
Riallocazione dei blocchi     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Inizio del passo 3 (max = 8)
Scansione della tavola degli inodeXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on .halium-install-imgs.ZDIkr/system.img is now 28387 (4k) blocks long.

I: Unmounting images
I: Pushing rootfs and android image to /data via ADB
I:    Pushing rootfs to /data via ADB
.halium-install-imgs.ZDIkr/rootfs.img: 1 file pushed. 3.0 MB/s (3221225472 bytes in 1017.088s)
I:    Pushing android image to /data via ADB
.halium-install-imgs.ZDIkr/system.img: 1 file pushed. 3.2 MB/s (116273152 bytes in 35.056s)

real    17m32,166s
user    0m1,125s
sys     0m4,891s
I: Cleaning up
umount: .halium-install-rootfs.jexQz: not mounted.
(base) massimo@MILLENNIUM:~/halium-install$

but the tablet seems to be stucked looping on reboot

i have no more ideas ....

MightyM17 commented 1 year ago

Can you telnet/ssh into the device and check the logs? https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html

massimo1980 commented 1 year ago

Can't... It keeps rebooting Samsung logo....black screen...and back again Windows can't even load the driver ( i mean the Classic sound you ear when you plug a USB device )

MightyM17 commented 1 year ago

Can't... It keeps rebooting Samsung logo....black screen...and back again Windows can't even load the driver ( i mean the Classic sound you ear when you plug a USB device )

Well then do you have something like last_kmsg in /proc folder? I am unsure of what is broken as it did boot for me, you'd get more help about debugging in the halium/ubports channels

massimo1980 commented 1 year ago

I have to try reboot in TWRP recovery and see on terminal... I'll give a try in the afternoon Anyway i want to thank you again for all your support and patience!

massimo1980 commented 1 year ago

( Sorry for the late reply ...here in italy today there was the apocalypse=really bad weather ) as you said, i checked for the log in /proc ( both /proc and /data/ubuntu/proc ) but there wasn't any last_kmsg ...only kmsg.log but was 0 byte there was an interesting line in /data/ubuntu/var/log/kern.log:

Nov 22 19:33:32 localhost kernel: [  148.517883] C1 [    kworker/1:1] battery_manager battery_manager: vcell = 3999000 soc = 84  current = -154 avg_current = -155 status = 2 health = 1 temp = 247 discharge status = 0, limit time : 0, bootmode : 0
Nov 22 19:33:36 localhost kernel: [  152.976593] C0 [         powerd] backlight panel: [1] brightness=0, bl=0
Nov 22 19:33:36 localhost kernel: [  152.977569] C0 [        mmcqd/0] mmc0 LDO enable
Nov 22 19:33:37 localhost kernel: [  153.240020] C0 [           init] init: Connection from private client
Nov 22 19:33:37 localhost kernel: [  153.252929] C0 [           init] init: Handling runlevel event
Nov 22 19:33:37 localhost kernel: [  153.254455] C0 [           init] init: rc goal changed from stop to start
Nov 22 19:33:37 localhost kernel: [  153.257415] C0 [           init] init: rc state changed from waiting to starting
Nov 22 19:33:37 localhost kernel: [  153.258605] C0 [           init] init: rsyslog goal changed from start to stop
Nov 22 19:33:37 localhost kernel: [  153.259521] C0 [           init] init: rsyslog state changed from running to pre-stop
Nov 22 19:33:37 localhost kernel: [  153.262878] C0 [           init] init: rsyslog state changed from pre-stop to stopping
Nov 22 19:33:37 localhost kernel: [  153.265014] C0 [           init] init: hwclock-save goal changed from stop to start
Nov 22 19:33:37 localhost kernel: [  153.265930] C0 [           init] init: hwclock-save state changed from waiting to starting
Nov 22 19:33:37 localhost kernel: [  153.267120] C0 [           init] init: resolvconf goal changed from start to stop
Nov 22 19:33:37 localhost kernel: [  153.269958] C0 [           init] init: resolvconf state changed from running to stopping
Nov 22 19:33:37 localhost kernel: [  153.272064] C0 [           init] init: alsa-store goal changed from stop to start
Nov 22 19:33:37 localhost kernel: [  153.272979] C0 [           init] init: alsa-store state changed from waiting to starting
Nov 22 19:33:37 localhost kernel: [  153.274108] C0 [           init] init: cron goal changed from start to stop
Nov 22 19:33:37 localhost kernel: [  153.275024] C0 [           init] init: cron state changed from running to pre-stop
Nov 22 19:33:37 localhost kernel: [  153.278320] C0 [           init] init: cron state changed from pre-stop to stopping
Nov 22 19:33:37 localhost kernel: [  153.280731] C0 [           init] init: plymouth-upstart-bridge goal changed from stop to start
Nov 22 19:33:37 localhost kernel: [  153.281646] C0 [           init] init: plymouth-upstart-bridge state changed from waiting to starting
Nov 22 19:33:37 localhost kernel: [  153.282806] C0 [           init] init: Handling starting event
Nov 22 19:33:37 localhost kernel: [  153.285491] C0 [           init] init: rc state changed from starting to pre-start
Nov 22 19:33:37 localhost kernel: [  153.286468] C0 [           init] init: rc state changed from pre-start to spawned
**Nov 22 19:33:37 localhost kernel: [  153.290893] C1 [           init] init: Failed to open system console: No such device**
Nov 22 19:33:37 localhost kernel: [  153.293212] C0 [           init] init: rc main process (586)
Nov 22 19:33:37 localhost kernel: [  153.293609] C0 [           init] init: rc state changed from spawned to post-start
Nov 22 19:33:37 localhost kernel: [  153.294982] C0 [           init] init: rc state changed from post-start to running
Nov 22 19:33:37 localhost kernel: [  153.296295] C0 [           init] init: Handling stopping event
Nov 22 19:33:37 localhost kernel: [  153.297973] C0 [           init] init: rsyslog state changed from stopping to killed
Nov 22 19:33:37 localhost kernel: Kernel logging (proc) stopped.

in the ubports docs says to use this lines for samsung's devices

CONFIG_CMDLINE="console=tty0"
CONFIG_CMDLINE_EXTEND=y

i'll try with: BOARD_KERNEL_CMDLINE += console=tty0 i'm attaching the log file if interested.. kern.log

MightyM17 commented 1 year ago

The logs you sent seem to be of the twrp or smth? Linux version 3.0.31-CM-g9ca9e30-dirty (starcarr@tauron) hence I cannot find any issues. The kernel we built is 3.0.101

massimo1980 commented 1 year ago

i'm really sorry....my fault. i think that i have to take a break from this ...

after using halium-install, using both rootfs image from the docs:

i found that on tablet there was only the directory: /data/ubuntu/dev nothing else....so i have tryied other way to make it works The log i sent yesterday was from another file: cm_p5110-ota-eng.starcarr.zip ( i managed to modify some scripts inside this file to adapt for my 5100 ) using this one and the preinstalled file: quantal-preinstalled-phablet-armhf.zip it seems to boot well in ubuntu touch ( well...there are other issues like: it connects well to my wifi but it doesn't take the dns resolve server...remain 0.0.0.0 )

with the files i built in halium ...there was no way to populate the rootfs

i'm going to buy a TFT monitor for my raspberry and throw away this p5100 :joy:

MightyM17 commented 1 year ago

Why do you want halium on the tab though? It's a very unfinished port xD

massimo1980 commented 1 year ago

well....Halium....or whatever....i only need a linux dist on my tablet :joy: actually i have developed a nodejs service and a dedicated webpage to talk with my photovoltaic system to have a real time image of what my house is producing/consuming. The app that the system come with is pretty crappy...and it update the measures every 10 minutes so my idea was to use the P5100 as a dashboard for my software.....but as you see...with no luck :joy:

MightyM17 commented 1 year ago

Maybe try out postmarketos since that is in a better state currently and runs mainline Linux :P And sorry about the issues you've been facing, haven't really touched halium in a while so I'm unsure of what's breaking things on your end. Again asking for support on halium/ubports channels would help you :D

massimo1980 commented 1 year ago

well... i have installed PostmarketOS pretty quickly on the tablet ( the procedure it's pratically full-automated ) but damn!! it's really slow!! :joy: i can't even write the password of my wifi :joy: i've read only after that there's no hardware acceleration :joy: anyway....i continue to thank you for all your support ❤️

MightyM17 commented 1 year ago

Ah right you need to get video/image, sooo either 1) Work on and try to fix halium 2) Try pvrports (postmarketos with hardware acceleration, just gotta wait sometime once 10" support is released) 3) Try SailfishOS (no idea about the software there)

massimo1980 commented 1 year ago

yep...i'm going to retry on the halium build actually i've managed to configure the device in this way:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <remote  name="donkey" fetch="https://github.com/DonkeyCoyote/" />
        <remote  name="espresso" fetch="https://github.com/Unlegacy-Android/" revision="aosp-7.1" />
        <project path="device/samsung/p5100" name="android_device_samsung_p5100" remote="los" revision="cm-13.0" />
        <project path="kernel/samsung/espresso10" name="android_kernel_samsung_espresso10" remote="los" revision="cm-14.1" />
        <project path="packages/apps/SamsungServiceMode" name="android_packages_apps_SamsungServiceMode" remote="los" revision="cm-14.1" />
        <project path="device/samsung/espresso-common" name="android_device_samsung_espresso-common" remote="los" revision="cm-14.1" />
        <project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="los" revision="cm-14.1" />
        <project path="device/samsung/omap4-common" name="android_device_samsung_omap4-common" remote="los" revision="cm-14.1" />
        <project path="vendor/samsung" name="proprietary_vendor_samsung" remote="them" revision="cm-14.1" />
        <project path="vendor/ti" name="proprietary_vendor_ti" remote="espresso" revision="aosp-7.0" />
</manifest>

breakfast seems to works well:

max@NEWMILLENNIUM:~/halium$ source build/envsetup.sh && breakfast p5100
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
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20221124-UNOFFICIAL-p5100
TARGET_PRODUCT=lineage_p5100
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.15.74.2-microsoft-standard-WSL2-x86_64-with-debian-bookworm-sid
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NOF27B
OUT_DIR=/home/max/halium/out
============================================

mka mkbootimg and mka hybris-boot runs flawlessly ( if i remember correctly the only issue was with the file kernel/samsung/espresso10/security/commoncap.c ...but easy fix )

the problems starts with mka systemimage. A lot of this errors :

device/samsung/espresso-common/audio/audio_hw.c:545:9: error: use of undeclared identifier 'adev'
    if (adev->outputs[OUTPUT_LOW_LATENCY] != NULL &&
        ^
device/samsung/espresso-common/audio/audio_hw.c:546:14: error: use of undeclared identifier 'adev'
            !adev->outputs[OUTPUT_LOW_LATENCY]->standby) {
             ^
device/samsung/espresso-common/audio/audio_hw.c:547:15: error: use of undeclared identifier 'adev'
        out = adev->outputs[OUTPUT_LOW_LATENCY];
              ^
device/samsung/espresso-common/audio/audio_hw.c:553:9: error: use of undeclared identifier 'adev'
    if (adev->active_input) {
        ^
device/samsung/espresso-common/audio/audio_hw.c:554:14: error: use of undeclared identifier 'adev'
        in = adev->active_input;

i have still to understand if it's possible to remove the -Werror on audio_hw build or something else...

MightyM17 commented 1 year ago

Yeah the issue is halium needs 3.4 kernel while lineage/cm uses 3.0 kernel hence I'm not sure if it will even work after booting, hence the reason i chose Unlegacy-Android as the source. Mixing various sources i.e. Lineage and Unlegacy is a bad idea, they are two different roms.

massimo1980 commented 1 year ago

Hi there! after a little break from headaches, i retried everything from scratch! with this new images seems to boot without entering in the "reboot loop" but the screen remains black. This time i was able to pull the "syslog" file from TWRP, but still can't find any hint on the issue

BTW i want to wish you merry Christmas and all the Holiday Greetings!

p5100-boot.log

MightyM17 commented 1 year ago 
Dec 16 10:09:55 ubuntu-phablet kernel: [   21.045318] PVR_K:(Error): GetHandleStructure: Handle index out of range (4294967295 >= 256)
Dec 16 10:09:55 ubuntu-phablet kernel: [   21.045349] PVR_K:(Error): PVRSRVLookupHandle: Error looking up handle (149)
Dec 16 10:09:55 ubuntu-phablet kernel: [   21.045349] PVR_K:(Error): PVRSRV_BridgeDispatchKM: Invalid kernel services handle (149)
Dec 16 10:09:55 ubuntu-phablet URfkill[779]: Modem found: '/ril_0'
Dec 16 10:09:55 ubuntu-phablet accounts-daemon[1548]: started daemon version 0.6.40
Dec 16 10:09:55 ubuntu-phablet dbus[775]: [system] Successfully activated service 'org.freedesktop.Accounts'
Dec 16 10:09:55 ubuntu-phablet ofonod[1535]: get_property_value: ERROR reply to Get
Dec 16 10:09:56 ubuntu-phablet kernel: [   21.560089] PVR_K:(Error): GetHandleStructure: Handle index out of range (4294967295 >= 256)
Dec 16 10:09:56 ubuntu-phablet kernel: [   21.560119] PVR_K:(Error): PVRSRVLookupHandle: Error looking up handle (149)
Dec 16 10:09:56 ubuntu-phablet kernel: [   21.560119] PVR_K:(Error): PVRSRV_BridgeDispatchKM: Invalid kernel services handle (149)
Dec 16 10:09:56 ubuntu-phablet kernel: [   21.930389] init: lightdm main process (1528) terminated with status 1
Dec 16 10:09:56 ubuntu-phablet kernel: [   21.930450] init: lightdm main process ended, respawning
Dec 16 10:09:56 ubuntu-phablet kernel: [   22.083435] PVR_K:(Error): GetHandleStructure: Handle index out of range (4294967295 >= 256)
Dec 16 10:09:56 ubuntu-phablet kernel: [   22.083435] PVR_K:(Error): PVRSRVLookupHandle: Error looking up handle (149)
Dec 16 10:09:56 ubuntu-phablet kernel: [   22.083465] PVR_K:(Error): PVRSRV_BridgeDispatchKM: Invalid kernel services handle (149)
Dec 16 10:09:57 ubuntu-phablet kernel: [   22.583831] PVR_K:(Error): GetHandleStructure: Handle index out of range (4294967295 >= 256)
Dec 16 10:09:57 ubuntu-phablet kernel: [   22.583862] PVR_K:(Error): PVRSRVLookupHandle: Error looking up handle (149)
Dec 16 10:09:57 ubuntu-phablet kernel: [   22.583892] PVR_K:(Error): PVRSRV_BridgeDispatchKM: Invalid kernel services handle (149)
Dec 16 10:09:57 ubuntu-phablet kernel: [   23.134246] PVR_K:(Error): GetHandleStructure: Handle index out of range (4294967295 >= 256)
Dec 16 10:09:57 ubuntu-phablet kernel: [   23.134277] PVR_K:(Error): PVRSRVLookupHandle: Error looking up handle (149)
Dec 16 10:09:57 ubuntu-phablet kernel: [   23.134277] PVR_K:(Error): PVRSRV_BridgeDispatchKM: Invalid kernel services handle (149)

From the log you attached, looks like the tablet is booting fine but PowerVR, the GPU is failing to load in the kernel, hence there is no UI (or just a blank screen)

MightyM17 commented 1 year ago

After a quick search seems to be that some module isnt being loaded :/ https://forum.xda-developers.com/t/q-build-kernel-mt6577-cant-boot-after-build.2159580/post-51778665 Can you show the output of lsmod?

massimo1980 commented 1 year ago

Hi Mighty i found that thread but no clue on how resolve Unfortunately, when booted, it is not recognized by ADB so i can't log in I've tried to configure manually NetworkManager with my SSID ( i've created the config file in the "system-connections" dir ) but i see this error message in the logs:

ubuntu-phablet NetworkManager[1275]: <info> [1671629094.5036] audit: op="connection-activate" uuid="7d9d5594-7ce3-4fd2-aba1-9a82f8449f7a" name="MyRouter" result="fail" reason="No suitable device found for this connection."

i've no idea how to log in in that state....