[ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

I'll check my build environment (probably on monday) and report back.

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Yes @mad_ady, normally it is not needed to replace the modules if the kernel version stays the same.
As I installed some weeks ago Alpha-v0.4, this branch test5 should be the correct one. I will make some more tests, but to replace the kernel modules I have to totally dismount my C4 to get the emmc :( .

[edit]
I have compared the logs and this is the first bad message with my kernel:

Code: Select all

[    2.524706@0] Unable to handle kernel paging request at virtual address 0002001a
[    2.526460@0] pgd = ffffffc03b68b000
[    2.530138@0] [0002001a] *pgd=0000000000000000, *pud=0000000000000000
[    2.536426@0] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[    2.542144@0] Modules linked in: mali_kbase(O+)
[    2.546650@0] CPU: 0 PID: 2251 Comm: init Tainted: G           O    4.9.113 #2
 

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

joerg wrote:
Sat Dec 19, 2020 7:37 pm
Yes @mad_ady, normally it is not needed to replace the modules if the kernel version stays the same.
As I installed some weeks ago Alpha-v0.4, this branch test5 should be the correct one. I will make some more tests, but to replace the kernel modules I have to totally dismount my C4 to get the emmc :( .

[edit]
I have compared the logs and this is the first bad message with my kernel:

Code: Select all

[    2.524706@0] Unable to handle kernel paging request at virtual address 0002001a
[    2.526460@0] pgd = ffffffc03b68b000
[    2.530138@0] [0002001a] *pgd=0000000000000000, *pud=0000000000000000
[    2.536426@0] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[    2.542144@0] Modules linked in: mali_kbase(O+)
[    2.546650@0] CPU: 0 PID: 2251 Comm: init Tainted: G           O    4.9.113 #2
 
Yes. Lot of modules, like mali, media omx and also wifi drivers not included in kernel tree. This modules building separate in Android build process.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

OK, but what is the solution then? This modules that are built in Android build process should also be compatible to the kernel I am building. As I see in Kernel-Version, your version is 4.9.113 #2 Thu Nov 12 18:57:54 WITA 2020.
As I was wondering before, if I use different toolchain, or if I compile the kernel out of Android tree, can this be the thing why it is not working?
This is how I compiled:

Code: Select all

export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
export PATH=/home/joerg/Development/odroid_n2/toolchain/gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu/bin/:$PATH
make odroidc4_android_defconfig
make -j12
And I tried also the toolchain gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu
Toolchains gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux and lineage/prebuilts/clang/host/linux-x86/clang-r383902b are failing.

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

I think my last kernel compile (about a month and a half ago) was done with this toolchain: gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu.
The dtb flashing steps here are no longer correct: https://magazine.odroid.com/article/run ... r-android/, but otherwise the steps are about the same. I used voodik's fork, with this branch: lineage-16.0_odroidg12_64_test4 (BUT NOTE - this was for an N2, not C4!)

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

Code: Select all

root@ubuntu:/1data/N2/Q/5Q-64# prebuilts/gcc/linux-x86/aarch64/aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc -v
Using built-in specs.
...........
Target: aarch64-linux-gnu
...........
Thread model: posix
gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)

Code: Select all

#n2/c4
export PATH=$PATH:/opt/toolchains/gcc-linaro-aarch64-none-elf-4.9-2014.09_linux/bin
export PATH=$PATH:/opt/toolchains/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/bin
export PATH=$PATH:/opt/toolchains/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin
BTW.
Did you change config ? or dtbs only ?
if you enable some drivers in config yes kernel should be flashed, if only dtb modification you can flash only dtbs partition.
Maybe I can help you and build kernel for you? I can provide you boot.img and /vendor/lib/modules folder. just replace modules flash kernel and after do any modifications with dtb and flash dtb only...
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I have replaced the kernel compiled with this toolchain when it was Alpha-v0.1. It was working.
I check if I am on the right branch:

Code: Select all

git branch
  lineage-16.0_odroidg12_64
* lineage-16.0_odroidg12_64_test5
I think I am on the branch where the asterisk is.
Deleting the old branch, it's there because I have commited my changes.

Code: Select all

 git branch -D lineage-16.0_odroidg12_64
Branch lineage-16.0_odroidg12_64 entfernt (war 7e2e405e027d).
git branch
* lineage-16.0_odroidg12_64_test5
git pull
Bereits aktuell.
git status
Aktualisiere Index: 100% (58508/58508), Fertig.
Auf Branch lineage-16.0_odroidg12_64_test5
Ihr Branch ist auf demselben Stand wie 'origin/lineage-16.0_odroidg12_64_test5'.
git diff
diff --git a/arch/arm64/configs/odroidc4_android_defconfig b/arch/arm64/configs/odroidc4_android_defconfig
index 067aba71b554..032bc90b8343 100644
--- a/arch/arm64/configs/odroidc4_android_defconfig
+++ b/arch/arm64/configs/odroidc4_android_defconfig
@@ -4461,7 +4461,7 @@ CONFIG_RTC_INTF_DEV=y
 #
 # CONFIG_RTC_DRV_ABB5ZES3 is not set
 # CONFIG_RTC_DRV_ABX80X is not set
-# CONFIG_RTC_DRV_DS1307 is not set
+CONFIG_RTC_DRV_DS1307=y
 # CONFIG_RTC_DRV_DS1374 is not set
 # CONFIG_RTC_DRV_DS1672 is not set
 # CONFIG_RTC_DRV_HYM8563 is not set
Cleaning the kernel source and compiling again. The same.
If it results that we cannot replace the kernel, it would be meaning that we need to ask @voodik if he provides a new update. But it is not what I want, to charge others with my whishes.

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

As I need my C4 now in the car and no one seems to trying out, if the kernel can be replaced, I have now compiled ds1307 as loadable kernel module and placed it in /vendor/lib/modules.
This is basically working, but not so optimal as inbuilt module.

Code: Select all

[    1.476908] hctosys: unable to open rtc device (rtc0)
[    5.885400] rtc_ds1307: disagrees about version of symbol dev_warn
[    5.885422] rtc_ds1307: disagrees about version of symbol _dev_info
[    5.885440] rtc_ds1307: disagrees about version of symbol dev_err
[    5.893072] rtc-ds1307 0-0068: rtc core: registered ds3231 as rtc0
[   12.702665] type=1400 audit(12.640:163): avc: denied { open } for comm="system_server" path="/sys/devices/platform/soc/ffd00000.cbus/ffd1d000.i2c/i2c-0/0-0068/rtc/rtc0/hctosys" dev="sysfs" ino=23148 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[   12.954612] type=1400 audit(12.640:163): avc: denied { open } for comm="system_server" path="/sys/devices/platform/soc/ffd00000.cbus/ffd1d000.i2c/i2c-0/0-0068/rtc/rtc0/hctosys" dev="sysfs" ino=23148 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
I need to load the module from /vendor/etc/init/hw/init.odroidc4.rc with insmod /vendor/lib/modules/rtc-ds1307.ko in trigger section on boot.

First:

Code: Select all

[    1.476908] hctosys: unable to open rtc device (rtc0)
The module is loaded to late.

Then:

Code: Select all

[    5.885400] rtc_ds1307: disagrees about version of symbol dev_warn
[    5.885422] rtc_ds1307: disagrees about version of symbol _dev_info
[    5.885440] rtc_ds1307: disagrees about version of symbol dev_err
The kernel modules need to be compiled against Module.symvers. But it's only a warning, the module loads.
Obviously the reason why Android don't boot with the custom kernel?
Need to learn how to compile correct.

Next:
Made a custom dtb overlay for DS3231, modified the makefile and compiled it.
But to unpack the dtbs partition and repack with the additional dtbo does not work.
The dtbs.img created with mkfs.cramfs is about 50% shrinked, means compressed.

Code: Select all

mkfs.cramfs dtbs newdtbs.img -v
  ads7846.dtbo
  can0.dtbo
  ds3231.dtbo
  esp8089.dtbo
  fanspeed-full.dtbo
  gpio_shortcut.dtbo
  hktft32.dtbo
  hktft35.dtbo
  i2c0.dtbo
  i2c1.dtbo
  meson64_odroidc4_android.dtb
  meson64_odroidhc4_android.dtb
  onewire.dtbo
  pcf8563.dtbo
  pwm_a-pwmfan.dtbo
  pwm_ab.dtbo
  pwm_b-backlight.dtbo
  pwm_cd.dtbo
  pwm_ef.dtbo
  sdio.dtbo
  spi0.dtbo
  sx865x-i2c1.dtbo
  uart0.dtbo
  uart1.dtbo
  uart2.dtbo
  wifi_bt_combo.dtbo
Verzeichnisdaten: 780 Bytes
-52,29% (-434 Bytes)	ads7846.dtbo
-47,89% (-261 Bytes)	can0.dtbo
-46,61% (-220 Bytes)	ds3231.dtbo
-42,33% (-185 Bytes)	esp8089.dtbo
-39,75% (-95 Bytes)	fanspeed-full.dtbo
-62,93% (-618 Bytes)	gpio_shortcut.dtbo
-58,32% (-722 Bytes)	hktft32.dtbo
-68,03% (-1277 Bytes)	hktft35.dtbo
-39,01% (-87 Bytes)	i2c0.dtbo
-39,01% (-87 Bytes)	i2c1.dtbo
-70,14% (-48652 Bytes)	meson64_odroidc4_android.dtb
-70,00% (-49725 Bytes)	meson64_odroidhc4_android.dtb
-45,32% (-189 Bytes)	onewire.dtbo
-46,27% (-217 Bytes)	pcf8563.dtbo
-69,14% (-1407 Bytes)	pwm_a-pwmfan.dtbo
-48,54% (-200 Bytes)	pwm_ab.dtbo
-54,32% (-509 Bytes)	pwm_b-backlight.dtbo
-48,67% (-201 Bytes)	pwm_cd.dtbo
-48,54% (-200 Bytes)	pwm_ef.dtbo
-36,84% (-84 Bytes)	sdio.dtbo
-48,06% (-248 Bytes)	spi0.dtbo
-55,73% (-428 Bytes)	sx865x-i2c1.dtbo
-48,42% (-184 Bytes)	uart0.dtbo
-37,78% (-85 Bytes)	uart1.dtbo
-37,78% (-85 Bytes)	uart2.dtbo
-64,23% (-984 Bytes)	wifi_bt_combo.dtbo
Alles: 52 Kilobytes
Superblock: 76 Bytes
CRC: 7c7a4eaf
mkfs.cramfs: Warnung: GIDs abgeschnitten auf 8 Bits. (Dies könnte ein Sicherheitsrisiko sein.)

Code: Select all

-rwxr----- 1 joerg joerg 131072 Dez 24 11:48 dtbs.img
-rw-rw-r-- 1 joerg joerg  53248 Dez 24 15:28 newdtbs.img
It seems that it is not compatible, obviously when u-boot tries to load it.
Android build system has other method to compile it.

Finally:
I added the necessary part into boot.ini:

Code: Select all

fdt addr ${dtb_mem_addr}
fdt mknode i2c0 rtc@68
fdt set i2c0/rtc@68 compatible "maxim,ds3231"
fdt set i2c0/rtc@68 reg "<0x68>"
fdt set i2c0/rtc@68 status "okay"
fdt set /rtc status "disable"
booti ${loadaddr} - ${dtb_mem_addr}
It seems that fdt addr ${dtb_mem_addr} must be given again after dtbo reading.
This line fdt set /rtc status "disable" is to disable the virtual rtc module.

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

The difference in dtb size is that the original dtbo partition is 128k in size and you read it with dd. There's some free space after it.
You can try zeroing kernel and dtbo before flashing them, though that wasn't necessary for me on the n2.
And run file on the kernel/dtb and compare output with the originals.

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

@mad_ady: Merry Christmas and also to all other.
Then it is interesting why it does not boot when I flash it. I do nothing else as unpack it and add a small dtbo and pack it with mkfs.cramfs again. I flashed it by dd to dtbs partition. To try it with fastboot I have to disassemble the C4 again. I will see if I do, or if the solution I found works so far.

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Try to mount cramfs without unpacking it. I don't remember, but the fuse driver might be smart enough to repack the cramfs for you.

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

Update :!:

Code: Select all

20210126 Alpha-v0.5
* Added new External Camera HAL(to use old one setprop persist.camera.legacy_hal true)
* Added WIFI Direct feature (disabled by default)
* Added Miracast(WFD) sink/source support
* Added mouse right click option to Odroid Settings
* Added Enable/Disable CEC globally to Odroid Settings
* Added pinch zoom by mouse wheel
* Added setting rotate display after reboot
* Added several Joystick keylayout configs (fixed broken ones) 
* Added Google Search app (Google Assistant is working, check device system language from Settings> System > Languages and input)
* Kernel enable CONFIG_HID_SMARTJOYPLUS
* Kernel added Realtek 8814au 8192eu 8188fu WIFI drivers
* Kernel added Mediatek mt7601u WIFI driver
* Kernel enabled P2P support on supported Realtek WIFI drivers
* Sync wifi_id_list with drivers (add missing vid/pid)
* Fixed Recovery HDMI output with custom resolution
* Fixed i2s1 output on J7
* Fixed USB Microphone input (Fixes Ok Google)
* Disabled DEXPREOPT for some targets (free up space on system partition)
* Removed ro.sf.defaultrotation property (use native ro.surface_flinger.primary_display_orientation)
* Minor cleanup/fixes
* Lineage merge with upstream
* Merge latest BSP changes
New Camera HAL config file location

Code: Select all

/odm/external_camera_config.xml
How to enable WIFI Direct/WFD/Miracast support
viewtopic.php?p=316848#p316848
These users thanked the author voodik for the post (total 2):
mad_ady (Wed Jan 27, 2021 12:20 am) • odroid (Wed Jan 27, 2021 9:37 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Hey everyone!
I'm using this OS on a C4 I've given my inlaws that live in a different town.
It has an Odroid Wifi 5 module attached (not 5A).
I've installed one of the original releases and updated it twice (not the last update yet though), but I have two problems that weren't present before the updates.
1. WIFI doesn't automatically reconnect on boot. Once wifi disconnects, it doesn't automatically reconnect again. The AP isn't hidden and can connect manually. Not sure how to force it to scan or connect automatically.
2. I'm using Openvpn for Android to connect automatically when there is a network connection back home (for troubleshooting). It used to connect, but no longer connects automatically after the updates, although it's set to do it. It connects manually, though.

Any suggestions on what to try to troubleshoot next time I'm there? Should I try to wipe cache from recovery? Collect some logs?
Can't do much remotely, my inlaws haven't managed to turn on wifi themselves :)
Thanks!

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

mad_ady wrote:
Tue Feb 09, 2021 5:10 am
Hey everyone!
I'm using this OS on a C4 I've given my inlaws that live in a different town.
It has an Odroid Wifi 5 module attached (not 5A).
I've installed one of the original releases and updated it twice (not the last update yet though), but I have two problems that weren't present before the updates.
1. WIFI doesn't automatically reconnect on boot. Once wifi disconnects, it doesn't automatically reconnect again. The AP isn't hidden and can connect manually. Not sure how to force it to scan or connect automatically.
2. I'm using Openvpn for Android to connect automatically when there is a network connection back home (for troubleshooting). It used to connect, but no longer connects automatically after the updates, although it's set to do it. It connects manually, though.

Any suggestions on what to try to troubleshoot next time I'm there? Should I try to wipe cache from recovery? Collect some logs?
Can't do much remotely, my inlaws haven't managed to turn on wifi themselves :)
Thanks!
Is your module directly connected to USB 3.0 port ?
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

No, it's through a 1m usb extender and it's connected to the usb-otg port in order not to interfere with the usb hdd that is connected to a usb3 port. Also, it's about 1m away, for better reception. I'll try to move it closer and switch ports if you think it will make any difference,

suchit1989
Posts: 1
Joined: Sat Feb 27, 2021 10:39 pm
languages_spoken: english
ODROIDs: Odroid C4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by suchit1989 »

How Can I download this Alpha v0.5 android source code? I need to build and flash. Could you pls provide me steps how to download ?
voodik wrote:
Tue Jan 26, 2021 8:08 pm
Update :!:

Code: Select all

20210126 Alpha-v0.5
* Added new External Camera HAL(to use old one setprop persist.camera.legacy_hal true)
* Added WIFI Direct feature (disabled by default)
* Added Miracast(WFD) sink/source support
* Added mouse right click option to Odroid Settings
* Added Enable/Disable CEC globally to Odroid Settings
* Added pinch zoom by mouse wheel
* Added setting rotate display after reboot
* Added several Joystick keylayout configs (fixed broken ones) 
* Added Google Search app (Google Assistant is working, check device system language from Settings> System > Languages and input)
* Kernel enable CONFIG_HID_SMARTJOYPLUS
* Kernel added Realtek 8814au 8192eu 8188fu WIFI drivers
* Kernel added Mediatek mt7601u WIFI driver
* Kernel enabled P2P support on supported Realtek WIFI drivers
* Sync wifi_id_list with drivers (add missing vid/pid)
* Fixed Recovery HDMI output with custom resolution
* Fixed i2s1 output on J7
* Fixed USB Microphone input (Fixes Ok Google)
* Disabled DEXPREOPT for some targets (free up space on system partition)
* Removed ro.sf.defaultrotation property (use native ro.surface_flinger.primary_display_orientation)
* Minor cleanup/fixes
* Lineage merge with upstream
* Merge latest BSP changes
New Camera HAL config file location

Code: Select all

/odm/external_camera_config.xml
How to enable WIFI Direct/WFD/Miracast support
viewtopic.php?p=316848#p316848

barthoxx
Posts: 3
Joined: Tue Dec 17, 2019 4:22 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by barthoxx »

Hi, I really enjoy this rom, it just feels fluid and nice, thanks for your work. I got one small, but rather annoying problem. My C4 is connected to my TV via HDMI and when I turn the TV off, wait some minutes and then turn it back on, there is no signal anymore. The C4 is not going to sleep, the leds stay on, i can still ping it and adb logcat (over network) is still giving output. Whatever I try, I have to cut power / reboot the C4 to have a signal on hdmi again. I deactivated all the HDMI CEC options, my TV doesn't support CEC anyways.

Here the logcat output from the time I powered on the TV again. (I hope I got everything):

Code: Select all

03-14 14:35:59.810  3050  3068 I SystemControl: aLatency:  Invalid/Unknown
03-14 14:35:59.810  3050  3068 I SystemControl: i_vLatency:  Invalid/Unknown
03-14 14:35:59.810  3050  3068 I SystemControl: i_aLatency:  Invalid/Unknown
03-14 14:35:59.810  3050  3068 I SystemControl: SCDC: 0
03-14 14:35:59.810  3050  3068 I SystemControl: RR_Cap: 0
03-14 14:35:59.810  3050  3068 I SystemControl: LTE_340M_Scramble: 0
03-14 14:35:59.810  3050  3068 I SystemControl:   DeepColor
03-14 14:35:59.810  3050  3068 I SystemControl: checkvalue: 0x1c760000
03-14 14:35:59.810  3050  3068 I SystemControl: Deep color
03-14 14:35:59.810  3050  3068 I SystemControl: 444,12bit
03-14 14:35:59.810  3050  3068 I SystemControl: 444,10bit
03-14 14:35:59.810  3050  3068 I SystemControl: 444,8bit
03-14 14:35:59.810  3050  3068 I SystemControl: 422,12bit
03-14 14:35:59.810  3050  3068 I SystemControl: 422,10bit
03-14 14:35:59.810  3050  3068 I SystemControl: 422,8bit
03-14 14:35:59.810  3050  3068 I SystemControl: rgb,12bit
03-14 14:35:59.810  3050  3068 I SystemControl: rgb,10bit
03-14 14:35:59.810  3050  3068 I SystemControl: rgb,8bit
03-14 14:35:59.810  3047  3175 I SystemControlClient: notifyCallback event type:3
03-14 14:35:59.810  3050  3068 I SystemControl: HDR
03-14 14:35:59.810  3050  3068 I SystemControl: HDR10Plus Supported: 0
03-14 14:35:59.810  3050  3068 I SystemControl: HDR Static Metadata:
03-14 14:35:59.810  3050  3068 I SystemControl:     Supported EOTF:
03-14 14:35:59.810  3050  3068 I SystemControl:         Traditional SDR: 0
03-14 14:35:59.810  3050  3068 I SystemControl:         Traditional HDR: 0
03-14 14:35:59.810  3050  3068 I SystemControl:         SMPTE ST 2084: 0
03-14 14:35:59.810  3050  3068 I SystemControl:         Hybrif Log-Gamma: 0
03-14 14:35:59.810  3050  3068 I SystemControl:     Supported SMD type1: 0
03-14 14:35:59.810  3050  3068 I SystemControl:     Luminance Data
03-14 14:35:59.810  3050  3068 I SystemControl:         Max: 0
03-14 14:35:59.810  3050  3068 I SystemControl:         Avg: 0
03-14 14:35:59.810  3050  3068 I SystemControl:         Min: 0
03-14 14:35:59.810  3050  3068 I SystemControl:
03-14 14:35:59.810  3050  3068 I SystemControl: HDR Dynamic Metadata:
03-14 14:35:59.810  3050  3068 I SystemControl:
03-14 14:35:59.810  3050  3068 I SystemControl: colorimetry_data: 0
03-14 14:35:59.810  3050  3068 I SystemControl: Preferred mode: 1080i50hz
03-14 14:35:59.810  3485  4390 I SystemControlClient: notifyCallback event type:3
03-14 14:35:59.810  3485  4390 D systemcontrol-jni: eventcallback notify event = 3
03-14 14:35:59.810  3050  3068 I SystemControl: Sink type: sink
03-14 14:35:59.810  3050  3068 I SystemControl: Audio caps
03-14 14:35:59.810  3050  3068 I SystemControl: CodingType MaxChannels SamplingFreq SampleSize
03-14 14:35:59.810  3050  3068 I SystemControl: PCM, 2 ch, 32/44.1/48 kHz,
03-14 14:35:59.810  3050  3068 I SystemControl: Raw EDID
03-14 14:35:59.810  3050  3068 I SystemControl: 00ffffffffffff004c2d300b000000002c17010380693b780aee91a3544c99260f5054bdef80714f81c0810081809500a9c0b3000101023a801871382d40582c450075f23100001e662156aa51001e30468f330075f23100001e000000fd00184b0f5117000a202020202020000000fc0053414d53554e470a2020202020011c020325f14d901f04130514031220212207162309070783010000e2000f67030c001000b82d011d80d0721c1620102c258075f23100009e011d8018711c1620582c250075f23100009e011d00bc52d01e20b828554075f23100001e011d007251d01e206e28550075f23100001e8c0ad090204031200c40550075f23100001e76
03-14 14:35:59.810  3050  3068 I SystemControl: write /sys/class/video/disable_video, val:1 end
03-14 14:35:59.810  3485  4390 I SystemControlEvent: system control callback event: 3
03-14 14:35:59.811  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.hdmimode value:custombuilt
03-14 14:35:59.811  3050  3068 I SystemControl: the resolveResolution mode [1080p30hz] is not valid
03-14 14:35:59.811  3050  3068 I SystemControl: the resolveResolution mode [1080p25hz] is not valid
03-14 14:35:59.811  3050  3068 I SystemControl: set HDMI to highest edid mode: 1080p60hz
03-14 14:35:59.811  3050  3068 I SystemControl: write /sys/module/amvdec_h265/parameters/double_write_mode, val:0 end
03-14 14:35:59.811  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.cvbscable value:(null)
03-14 14:35:59.811  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.cvbsmode value:(null)
03-14 14:35:59.811  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.hdmimode value:custombuilt
03-14 14:35:59.811  3050  3068 I SystemControl: getBootEnv(ubootenv.var.hdmimode, custombuilt)
03-14 14:35:59.812  3066  3117 E MesonHwc: ConnectorHdmi::update to 1
03-14 14:35:59.812  3066  3117 E MesonHwc: FixedDisplayPipe::getConnetorCfg 0
03-14 14:35:59.811  3050  3068 I SystemControl: display sink type:1 [0:none, 1:sink, 2:repeater], old outputmode:custombuilt, new outputmode:custombuilt
03-14 14:35:59.812  3050  5170 I SystemControl: HDCPTx Auth status is: 0
03-14 14:35:59.812  3050  3068 I SystemControl: write /sys/devices/virtual/amhdmitx/amhdmitx0/avmute, val:1 end
03-14 14:35:59.812  3050  3068 I SystemControl: hdcp_tx 2.2 & 1.4 stop hdcp pwr
03-14 14:35:59.812  3050  3068 I SystemControl: write /sys/class/amhdmitx/amhdmitx0/hdcp_pwr, val:1 end
03-14 14:35:59.812  3066  3117 E MesonHwc: ConnectorHdmi::update to 1
03-14 14:35:59.813  3050  5170 I SystemControl: getBootEnv key:ubootenv.var.hdmimode value:custombuilt
03-14 14:35:59.814  3050  5170 I SystemControl: HDCPTx Auth status is: 0
03-14 14:35:59.814  3066  3117 E MesonHwc: ConnectorHdmi::update to 1
03-14 14:35:59.811  3485  4390 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1045 android.content.ContextWrapper.sendBroadcast:448 android.content.ContextWrapper.sendBroadcast:448 com.droidlogic.app.SystemControlEvent.HdmiHotPlugEvent:77 com.droidlogic.app.SystemControlManager.notifyCallback:3322
03-14 14:35:59.815  3319  3412 W ExtconUEventObserver: No match found for DEVPATH of {SUBSYSTEM=extcon, SEQNUM=2828, ACTION=change, DEVTYPE=hdmi_audio, STATE=HDMI=1, DEVPATH=/devices/virtual/amhdmitx/amhdmitx0/hdmi_audio, NAME=hdmitx_extcon_audio} in {/devices/virtual/amhdmitx/amhdmitx0/hdmi=com.android.server.ExtconUEventObserver$ExtconInfo@ffaaa9e}
03-14 14:35:59.816  3319  3412 I WiredAccessoryManager: MSG_NEW_DEVICE_STATE
03-14 14:35:59.819  3052  3860 D audio_hw_primary: adev_set_parameters(0xf175c340, connect=1024)
03-14 14:35:59.819  3052  3860 I audio_hw_primary: adev_set_parameters(kv: connect=1024)
03-14 14:35:59.819  3052  3860 I audio_hw_primary: adev_set_parameters,bHDMIConnected: 1024
03-14 14:35:59.820  3082  3082 I AudioFlinger: openOutput() this 0x7b24314c00, module 10 Device 0x400, SamplingRate 32000, Format 0x000001, Channels 0x3, flags 0x41
03-14 14:35:59.820  3052  3860 D audio_hw_primary: adev_open_output_stream_new: enter
03-14 14:35:59.820  3052  3860 D audio_hw_primary: adev_open_output_stream: enter: devices(0x400) channel_mask(0x3) rate(32000) format(0x1) flags(0x41)
03-14 14:35:59.820  3052  3860 I audio_hw_hwsync: aml_audio_hwsync_init open tsync fd 11
03-14 14:35:59.820  3052  3860 I audio_hw_hwsync: aml_audio_hwsync_init done
03-14 14:35:59.820  3052  3860 D audio_hw_primary: adev_open_output_stream format=1 rate=32000
03-14 14:35:59.820  3052  3860 I audio_hw_primary: init resampler from 32000 to 48000!
03-14 14:35:59.820  3052  3860 D aml_audio_resampler: resampler_init, Init Resampler: input_sr = 32000, output_sr = 48000
03-14 14:35:59.820  3052  3860 D audio_hw_primary: adev_open_output_stream: exit
03-14 14:35:59.820  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.820  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.820  3052  3860 D audio_hw_profile: query hdmi format...
03-14 14:35:59.821  3052  3860 I audio_hw_primary: get_sink_capability mbox+dvb case sink_capability =  1
03-14 14:35:59.821  3052  3860 I audio_hw_primary: !!!get_sink_format() Sink devices 0 Source format 0x1 digital_format(hdmi_format) 0 Sink Capability 0x1
03-14 14:35:59.821  3052  3860 I audio_hw_primary: get_sink_format() HDMI ARC case
03-14 14:35:59.821  3052  3860 I audio_hw_primary: get_sink_format sink_format 0x1 optical_format 0x1, stream device 0
03-14 14:35:59.821  3052  3860 I audio_hw_subMixingFactory: ++initSubMixingInput()
03-14 14:35:59.821  3052  3860 I audio_hw_subMixingFactory: ++initSubMixingInputPcm(), out 0xf179e300, flags 0x41, hwsync lpcm 1, out format 0x1
03-14 14:35:59.821  3052  3860 I audio_hw_subMixingFactory: initSubMixingInputPcm(), lpcm case
03-14 14:35:59.821  3052  3860 D audio_hw_primary: -adev_open_output_stream_new: out 0xf179e300: usecase = STREAM_PCM_HWSYNC card = 0 devices = 0
03-14 14:35:59.822  3052  3860 I audio_hw_primary: out_get_buffer_size(out->config.rate=32000, format 1,stream format 1)
03-14 14:35:59.822  3082  3082 I AudioFlinger: HAL output buffer size 1024 frames, normal sink buffer size 1024 frames
03-14 14:35:59.822  3082  6419 I AudioFlinger: AudioFlinger's thread 0x7b24404000 tid=6419 ready to run
03-14 14:35:59.824  3052  3860 D audio_hw_subMixingFactory: out_standby_subMixingPCM: out_stream(0xf179e300) usecase: STREAM_PCM_HWSYNC
03-14 14:35:59.831  3082  3082 I AudioFlinger: openOutput() this 0x7b24314c00, module 10 Device 0x400, SamplingRate 0, Format 00000000, Channels 0, flags 0x41
03-14 14:35:59.831  3052  3860 D audio_hw_primary: adev_open_output_stream_new: enter
03-14 14:35:59.831  3052  3860 D audio_hw_primary: adev_open_output_stream: enter: devices(0x400) channel_mask(0) rate(0) format(0) flags(0x41)
03-14 14:35:59.831  3052  3860 I audio_hw_primary: adev_open_output_stream: for raw audio output,force alsa stereo output
03-14 14:35:59.831  3052  3860 I audio_hw_hwsync: aml_audio_hwsync_init open tsync fd 12
03-14 14:35:59.831  3052  3860 I audio_hw_hwsync: aml_audio_hwsync_init done
03-14 14:35:59.831  3052  3860 D audio_hw_primary: adev_open_output_stream format=150994944 rate=48000
03-14 14:35:59.831  3052  3860 D audio_hw_primary: adev_open_output_stream: exit
03-14 14:35:59.831  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.831  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.831  3052  3860 D audio_hw_profile: query hdmi format...
03-14 14:35:59.831  3052  3860 I audio_hw_primary: get_sink_capability mbox+dvb case sink_capability =  1
03-14 14:35:59.832  3052  3860 I audio_hw_primary: !!!get_sink_format() Sink devices 0 Source format 0x9000000 digital_format(hdmi_format) 0 Sink Capability 0x1
03-14 14:35:59.832  3052  3860 I audio_hw_primary: get_sink_format() HDMI ARC case
03-14 14:35:59.832  3052  3860 I audio_hw_primary: get_sink_format sink_format 0x1 optical_format 0x1, stream device 0
03-14 14:35:59.832  3052  3860 I audio_hw_primary: adev_open_output_stream_new(), direct usecase: STREAM_RAW_HWSYNC
03-14 14:35:59.832  3052  3860 D audio_hw_primary: -adev_open_output_stream_new: out 0xf179e600: usecase = STREAM_RAW_HWSYNC card = 0 devices = 0
03-14 14:35:59.834  3052  3860 I audio_hw_primary: out_get_buffer_size(out->config.rate=48000, format 9000000,stream format 9000000)
03-14 14:35:59.834  3082  3082 I AudioFlinger: HAL output buffer size 512 frames, normal sink buffer size 512 frames
03-14 14:35:59.835  3082  6420 I AudioFlinger: AudioFlinger's thread 0x7b24406800 tid=6420 ready to run
03-14 14:35:59.835  3052  3860 I audio_hw_primary: out_get_parameters sup_formats,out 0xf179e600
03-14 14:35:59.835  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.835  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.835  3052  3860 D audio_hw_profile: query hdmi format...
03-14 14:35:59.835  3052  3860 I audio_hw_primary: sup_formats=AUDIO_FORMAT_PCM_16_BIT
03-14 14:35:59.836  3082  3082 D APM_AudioPolicyManager: modifySurroundFormats: forced use = 0
03-14 14:35:59.836  3052  3860 I audio_hw_primary: out_get_parameters format=1;sup_sampling_rates,out 0xf179e600
03-14 14:35:59.836  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.836  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.836  3052  3860 D audio_hw_profile: query hdmi sample_rate...
03-14 14:35:59.836  3052  3860 I audio_hw_primary: sup_sampling_rates=32000|44100|48000
03-14 14:35:59.837  3052  3860 I audio_hw_primary: out_standby_direct(0xf179e600),out 0xf179e600
03-14 14:35:59.838  3052  3860 I audio_hw_primary: out_get_parameters format=1;sup_channels,out 0xf179e600
03-14 14:35:59.838  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.838  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.838  3052  3860 D audio_hw_profile: query hdmi channels...
03-14 14:35:59.838  3052  3860 I audio_hw_primary: sup_channels=AUDIO_CHANNEL_OUT_STEREO
03-14 14:35:59.839  3052  3860 I audio_hw_primary: out_get_parameters format=150994944;sup_sampling_rates,out 0xf179e600
03-14 14:35:59.839  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.839  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.839  3052  3860 D audio_hw_profile: query hdmi sample_rate...
03-14 14:35:59.839  3052  3860 I audio_hw_primary: sup_sampling_rates=32000|44100|48000
03-14 14:35:59.839  3052  3860 I audio_hw_primary: out_get_parameters format=150994944;sup_channels,out 0xf179e600
03-14 14:35:59.839  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.839  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.839  3052  3860 D audio_hw_profile: query hdmi channels...
03-14 14:35:59.840  3052  3860 I audio_hw_primary: sup_channels=AUDIO_CHANNEL_OUT_STEREO
03-14 14:35:59.840  3052  3860 I audio_hw_primary: out_get_parameters format=218103808;sup_sampling_rates,out 0xf179e600
03-14 14:35:59.840  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.840  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.840  3052  3860 D audio_hw_profile: query hdmi sample_rate...
03-14 14:35:59.840  3052  3860 I audio_hw_primary: sup_sampling_rates=32000|44100|48000|128000|176400|192000
03-14 14:35:59.841  3052  3860 I audio_hw_primary: out_get_parameters format=218103808;sup_channels,out 0xf179e600
03-14 14:35:59.841  3052  3860 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.841  3052  3860 D audio_hw_profile: read from aud_cap
03-14 14:35:59.841  3052  3860 D audio_hw_profile: query hdmi channels...
03-14 14:35:59.841  3052  3860 I audio_hw_primary: sup_channels=AUDIO_CHANNEL_OUT_STEREO|AUDIO_CHANNEL_OUT_5POINT1|AUDIO_CHANNEL_OUT_7POINT1
03-14 14:35:59.842  3052  3860 D audio_hw_primary: out_set_parameters(kvpairs(closing=true), out_device=0x2)
03-14 14:35:59.842  3052  3860 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.843  3052  3860 D audio_hw_primary: out_dump(0xf179e600, 14)
03-14 14:35:59.844  3052  3860 D audio_hw_primary: out_set_parameters(kvpairs(exiting=1), out_device=0x2)
03-14 14:35:59.844  3052  3860 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.844  3052  3860 D audio_hw_primary: adev_close_output_stream_new: enter usecase = STREAM_RAW_HWSYNC
03-14 14:35:59.844  3052  3860 D audio_hw_primary: adev_close_output_stream: enter: dev(0xf175c340) stream(0xf179e600)
03-14 14:35:59.844  3052  3860 D audio_hw_primary: out_standby_new: enter
03-14 14:35:59.844  3052  3860 I audio_hw_primary: do_output_standby_l(0xf179e600), stream usecase: STREAM_RAW_HWSYNC continuous_audio_mode 0,status 0
03-14 14:35:59.844  3052  3860 I audio_hw_primary: ++usecase_change_validate_l(), dev usecase masks = 0, is_standby = 1, out usecase STREAM_RAW_HWSYNC
03-14 14:35:59.844  3052  3860 I audio_hw_primary: enable rawtopcm_flag !!!
03-14 14:35:59.844  3052  3860 I audio_hw_primary: --usecase_change_validate_l(), dev usecase masks = 0, is_standby = 1, out usecase STREAM_RAW_HWSYNC
03-14 14:35:59.844  3052  3860 I audio_hw_primary: do_output_standby_l current usecase_masks 0
03-14 14:35:59.844  3052  3860 D audio_hw_primary: out_standby_new: exit
03-14 14:35:59.844  3082  3082 I AudioFlinger: openOutput() this 0x7b24314c00, module 10 Device 0x400, SamplingRate 32000, Format 0x9000000, Channels 0x3, flags 0x41
03-14 14:35:59.844  3052  3860 I audio_hw_hwsync: aml_audio_hwsync_release done
03-14 14:35:59.844  3052  3052 D audio_hw_primary: adev_open_output_stream_new: enter
03-14 14:35:59.844  3052  3052 D audio_hw_primary: adev_open_output_stream: enter: devices(0x400) channel_mask(0x3) rate(32000) format(0x9000000) flags(0x41)
03-14 14:35:59.844  3052  3052 I audio_hw_primary: adev_open_output_stream: for raw audio output,force alsa stereo output
03-14 14:35:59.845  3052  3860 D audio_hw_primary: adev_close_output_stream: exit
03-14 14:35:59.845  3052  3860 D audio_hw_primary: adev_close_output_stream_new: exit
03-14 14:35:59.845  3052  3052 I audio_hw_hwsync: aml_audio_hwsync_init open tsync fd 12
03-14 14:35:59.845  3052  3052 I audio_hw_hwsync: aml_audio_hwsync_init done
03-14 14:35:59.845  3052  3052 D audio_hw_primary: adev_open_output_stream format=150994944 rate=32000
03-14 14:35:59.845  3052  3052 D audio_hw_primary: adev_open_output_stream: exit
03-14 14:35:59.845  3052  3052 D audio_hw_profile: get_hdmi_sink_cap is running...
03-14 14:35:59.845  3052  3052 D audio_hw_profile: read from aud_cap
03-14 14:35:59.845  3052  3052 D audio_hw_profile: query hdmi format...
03-14 14:35:59.845  3052  3052 I audio_hw_primary: get_sink_capability mbox+dvb case sink_capability =  1
03-14 14:35:59.845  3052  3052 I audio_hw_primary: !!!get_sink_format() Sink devices 0 Source format 0x9000000 digital_format(hdmi_format) 0 Sink Capability 0x1
03-14 14:35:59.845  3052  3052 I audio_hw_primary: get_sink_format() HDMI ARC case
03-14 14:35:59.845  3052  3052 I audio_hw_primary: get_sink_format sink_format 0x1 optical_format 0x1, stream device 0
03-14 14:35:59.845  3052  3052 I audio_hw_primary: adev_open_output_stream_new(), direct usecase: STREAM_RAW_HWSYNC
03-14 14:35:59.845  3052  3052 D audio_hw_primary: -adev_open_output_stream_new: out 0xf179e900: usecase = STREAM_RAW_HWSYNC card = 0 devices = 0
03-14 14:35:59.847  3052  3052 I audio_hw_primary: out_get_buffer_size(out->config.rate=32000, format 9000000,stream format 9000000)
03-14 14:35:59.847  3082  3082 I AudioFlinger: HAL output buffer size 512 frames, normal sink buffer size 512 frames
03-14 14:35:59.848  3082  6423 I AudioFlinger: AudioFlinger's thread 0x7b24406800 tid=6423 ready to run
03-14 14:35:59.849  3052  3052 I audio_hw_primary: out_standby_direct(0xf179e900),out 0xf179e900
03-14 14:35:59.853  3050  3068 I SystemControl: write /sys/class/amhdmitx/amhdmitx0/hdcp_ctrl, val:stop14 end
03-14 14:35:59.854  3050  3068 I SystemControl: write /sys/class/amhdmitx/amhdmitx0/hdcp_ctrl, val:stop22 end
03-14 14:35:59.856  3050  3068 I SystemControl: hdcp_tx pthread exit id = 519720406352, (null)  done
03-14 14:35:59.856  3050  3068 I SystemControl: Only modify deep color mode, get colorAttr from ubootenv.var.colorattribute
03-14 14:35:59.856  3050  3068 E SystemControl: [ubootenv] value - 444,8bit
03-14 14:35:59.856  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.colorattribute value:444,8bit
03-14 14:35:59.856  3050  3068 I SystemControl: get hdmi color attribute : [444,8bit], outputmode is: [custombuilt] , and support color list is: [444,12bit444,10bit444,8bit422,12bit422,10bit422,8bitrgb,12bitrgb,10bitrgb,8bit]
03-14 14:35:59.856  3050  3068 I SystemControl: cur deepcolor attr value is equals to colorAttribute, Do not need set it
03-14 14:35:59.857  3050  3068 I SystemControl: setMboxOutputMode colorAttribute = 444,8bit
03-14 14:35:59.857  3050  3068 I SystemControl: [ubootenv] update value [ubootenv.var.custombuilt_deepcolor : 444,8bit]
03-14 14:35:59.857  3050  3068 I SystemControl: [ubootenv] update value [ubootenv.var.colorattribute : 444,8bit]
03-14 14:35:59.857  3050  3068 E SystemControl: [ubootenv] value - 444,8bit
03-14 14:35:59.857  3050  3068 I SystemControl: curMode = custombuilt outputmode = custombuilt
03-14 14:35:59.857  3050  3068 I SystemControl: cur display mode is equals to outputmode, Do not need set it
03-14 14:35:59.857  3050  3068 I SystemControl: set display-size:1920x1080
03-14 14:35:59.857  3050  3068 I SystemControl: setHdrMode state: 2
03-14 14:35:59.857  3050  3068 I SystemControl: write /sys/module/am_vecm/parameters/hdr_mode, val:2 end
03-14 14:35:59.862  3050  3068 I SystemControl: setSdrMode state: 2
03-14 14:35:59.862  3050  3068 I SystemControl: write /sys/module/am_vecm/parameters/sdr_mode, val:2 end
03-14 14:35:59.863  3052  3052 D audio_hw_primary: out_set_parameters(kvpairs(closing=true), out_device=0x2)
03-14 14:35:59.863  3052  3052 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.864  3052  3052 D audio_hw_primary: out_dump(0xf179e300, 14)
03-14 14:35:59.865  3052  3052 D audio_hw_primary: out_set_parameters(kvpairs(exiting=1), out_device=0x2)
03-14 14:35:59.865  3052  3052 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.866  3052  3052 D audio_hw_primary: adev_close_output_stream_new: enter usecase = STREAM_PCM_HWSYNC
03-14 14:35:59.866  3052  3052 I audio_hw_subMixingFactory: ++deleteSubMixingInput()
03-14 14:35:59.866  3052  3052 I audio_hw_subMixingFactory: deleteSubMixingInputPcm(), cnt_stream_using_mixer 0
03-14 14:35:59.866  3052  3052 I audio_hw_subMixingFactory: deleteSubMixingInputPcm(), lpcm case
03-14 14:35:59.866  3052  3052 D audio_hw_primary: adev_close_output_stream: enter: dev(0xf175c340) stream(0xf179e300)
03-14 14:35:59.866  3052  3052 D audio_hw_subMixingFactory: out_standby_subMixingPCM: out_stream(0xf179e300) usecase: STREAM_PCM_HWSYNC
03-14 14:35:59.866  3052  3052 I audio_hw_hwsync: aml_audio_hwsync_release done
03-14 14:35:59.866  3052  3052 D audio_hw_primary: adev_close_output_stream: exit
03-14 14:35:59.866  3052  3052 D audio_hw_primary: adev_close_output_stream_new: exit
03-14 14:35:59.867  3050  3068 I SystemControl: [ubootenv] update value [ubootenv.var.sdr2hdr : 2]
03-14 14:35:59.867  3050  3068 I SystemControl: setMboxOutputMode cvbsMode = 0
03-14 14:35:59.867  3050  3068 E SystemControl: writeSysFs, open /sys/class/amhdmitx/amhdmitx0/aud_mute fail.
03-14 14:35:59.867  3050  3068 I SystemControl: write /sys/class/amhdmitx/amhdmitx0/aud_mute, val:1 end
03-14 14:35:59.867  3050  3068 E SystemControl: writeSysFs, open /sys/class/amhdmitx/amhdmitx0/aud_mute fail.
03-14 14:35:59.867  3050  3068 I SystemControl: write /sys/class/amhdmitx/amhdmitx0/aud_mute, val:0 end
03-14 14:35:59.867  3050  3068 I SystemControl: write /sys/devices/virtual/amhdmitx/amhdmitx0/avmute, val:-1 end
03-14 14:35:59.868  3052  6422 D audio_hw_primary: out_set_parameters(kvpairs(closing=true), out_device=0x2)
03-14 14:35:59.868  3052  6422 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.869  3052  6422 D audio_hw_primary: out_dump(0xf179e900, 11)
03-14 14:35:59.869  3050  6425 I SystemControl: hdcp_tx thread loop entry
03-14 14:35:59.869  3050  3068 I SystemControl: hdcp_tx, create hdcp thread id = 519720406352 done
03-14 14:35:59.870  3050  3068 I SystemControl: write /sys/class/video/disable_video, val:0 end
03-14 14:35:59.870  3050  3068 I SystemControl: getBootEnv key:ubootenv.var.digitaudiooutput value:(null)
03-14 14:35:59.870  3050  3068 I SystemControl: [ubootenv] update value [ubootenv.var.outputmode : custombuilt]
03-14 14:35:59.870  3050  3068 I SystemControl: set output mode:custombuilt done
03-14 14:35:59.870  3050  3068 I SystemControl: Matched uevent message with pattern: DEVPATH=/devices/virtual/amhdmitx/amhdmitx0/hdmi_audio
03-14 14:35:59.870  3050  3068 I SystemControl: HDCP TX switch_name: hdmi_audio ,switch_state: 1
03-14 14:35:59.870  3050  3068 I SystemControl: onTxEvent switchName:hdmi_audio hpdstate:1 state: 1
03-14 14:35:59.870  3050  6425 I SystemControl: hdcp_tx key:00
03-14 14:35:59.871  3050  6425 I SystemControl: write /sys/class/video/disable_video, val:0 end
03-14 14:35:59.871  3047  3175 I SystemControlClient: notifyCallback event type:0
03-14 14:35:59.871  3047  3175 I SystemControlClient: notifyCallback event type:5
03-14 14:35:59.871  3485  4390 I SystemControlClient: notifyCallback event type:0
03-14 14:35:59.871  3485  4390 D systemcontrol-jni: eventcallback notify event = 0
03-14 14:35:59.871  3485  4390 I SystemControlEvent: system control callback event: 0
03-14 14:35:59.871  3485  4390 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1045 android.content.ContextWrapper.sendBroadcast:448 android.content.ContextWrapper.sendBroadcast:448 com.droidlogic.app.SystemControlEvent.HdmiHotPlugEvent:77 com.droidlogic.app.SystemControlManager.notifyCallback:3322
03-14 14:35:59.872  3485  4390 I SystemControlClient: notifyCallback event type:5
03-14 14:35:59.872  3485  4390 D systemcontrol-jni: eventcallback notify event = 5
03-14 14:35:59.873  3485  4390 I SystemControlEvent: system control callback event: 5
03-14 14:35:59.873  3485  4390 D SystemControlEvent: setWireDeviceConnectionState public void android.media.AudioManager.setWiredDeviceConnectionState(int,int,java.lang.String,java.lang.String)
03-14 14:35:59.873  3052  6422 D audio_hw_primary: out_set_parameters(kvpairs(exiting=1), out_device=0x2)
03-14 14:35:59.873  3052  6422 E audio_hw_primary: Amlogic_HAL - out_set_parameters: parameter is NULL, change ret value to 0 in order to pass VTS test.
03-14 14:35:59.874  3052  6422 D audio_hw_primary: adev_close_output_stream_new: enter usecase = STREAM_RAW_HWSYNC
03-14 14:35:59.874  3052  6422 D audio_hw_primary: adev_close_output_stream: enter: dev(0xf175c340) stream(0xf179e900)
03-14 14:35:59.874  3052  6422 D audio_hw_primary: out_standby_new: enter
03-14 14:35:59.874  3052  6422 I audio_hw_primary: do_output_standby_l(0xf179e900), stream usecase: STREAM_RAW_HWSYNC continuous_audio_mode 0,status 0
03-14 14:35:59.874  3052  6422 I audio_hw_primary: ++usecase_change_validate_l(), dev usecase masks = 0, is_standby = 1, out usecase STREAM_RAW_HWSYNC
03-14 14:35:59.874  3052  6422 I audio_hw_primary: enable rawtopcm_flag !!!
03-14 14:35:59.874  3052  6422 I audio_hw_primary: --usecase_change_validate_l(), dev usecase masks = 0, is_standby = 1, out usecase STREAM_RAW_HWSYNC
03-14 14:35:59.874  3052  6422 I audio_hw_primary: do_output_standby_l current usecase_masks 0
03-14 14:35:59.874  3052  6422 D audio_hw_primary: out_standby_new: exit
03-14 14:35:59.874  3052  6422 I audio_hw_hwsync: aml_audio_hwsync_release done
03-14 14:35:59.874  3052  6422 D audio_hw_primary: adev_close_output_stream: exit
03-14 14:35:59.874  3052  6422 D audio_hw_primary: adev_close_output_stream_new: exit
03-14 14:35:59.877  3319  3319 I Telecom : WiredHeadsetManager: ACTION_HEADSET_PLUG event, plugged in: false, : WHC.oADA@ABA
03-14 14:35:59.877  4223  5207 D AudioFx-AudioOutputChangeListener: onAudioOutputChanged id: 10 type: 9 name: hdmitx_extcon_audio address:  [android.media.AudioDeviceInfo@29]
03-14 14:35:59.878  3319  3319 V MediaRouter: Audio routes updated: AudioRoutesInfo{ type=HDMI }, a2dp=false
03-14 14:35:59.878  3466  3466 V MediaRouter: Audio routes updated: AudioRoutesInfo{ type=HDMI }, a2dp=false
03-14 14:35:59.878  3319  3319 V MediaRouter: Selecting route: RouteInfo{ name=ÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÅÔÇÄÔÇÄHDMIÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄ, description=null, status=null, category=RouteCategory{ name=ÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÅÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄSystemÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄ types=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO  groupable=false }, supportedTypes=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO , presentationDisplay=null }
03-14 14:35:59.878  3466  3466 V MediaRouter: Selecting route: RouteInfo{ name=ÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÅÔÇÄÔÇÄHDMIÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄ, description=null, status=null, category=RouteCategory{ name=ÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄÔÇÅÔÇÄÔÇÅÔÇÄÔÇÅÔÇÅÔÇÄÔÇÄÔÇÄÔÇÅÔÇÄÔÇÄÔÇÄÔÇÄÔÇÄÔÇÅÔÇÅÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÅÔÇÄSystemÔÇÄÔÇÅÔÇÄÔÇÄÔÇÅÔÇÄ types=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO  groupable=false }, supportedTypes=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO , presentationDisplay=null }
03-14 14:35:59.878  3319  3440 W AS.AudioDeviceInventory: handleDeviceConnection() failed, deviceKey=0x400:, deviceSpec=[DeviceInfo: type:0x400 name:hdmitx_extcon_audio addr: codec: 0], connect=true
03-14 14:35:59.884  3466  3805 I vol.Events: writeEvent level_changed STREAM_MUSIC 20
03-14 14:36:00.003  3466  3466 D KeyguardClockSwitch: Updating clock: 14:36
Is it a bug or do I have any wrong setting? TV is a Samsung UE48H5090, Power supply of the C4 is extra, not via USB from TV

[edit]: It seems this is the same problem (not a specific problem for your build) as talked about here: viewtopic.php?f=204&t=42060 - For anyone else encountering this problem, see that thread for the solution - it's just setting some values.

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

Update :!:

Code: Select all

20210813 Alpha-v0.6
* Fixed Realtek 8821CU WIFI/Bluetooth support
* Fixed Miracast with Samsung Smart View
* Minor cleanup/fixes
* Lineage merge with upstream
* Merge latest BSP changes
These users thanked the author voodik for the post (total 2):
odroid (Tue Aug 17, 2021 9:17 am) • barthoxx (Thu Aug 26, 2021 1:44 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jholbrook514
Posts: 41
Joined: Wed Mar 06, 2019 10:00 am
languages_spoken: english
ODROIDs: Odroid C1, C2, XU4, C4, N2, N2+, Odroid Go, OGA, OGU
Has thanked: 4 times
Been thanked: 4 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by jholbrook514 »

Does this image work with the Odroid VU7 Screen on the C4 ???

I am making a "Carputer" to run YT Music Vanced, and YT Vanced along with a few other media apps. Plus Torque for live OBDII diagnostics

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

jholbrook514 wrote:
Thu Aug 26, 2021 1:06 am
Does this image work with the Odroid VU7 Screen on the C4 ???

I am making a "Carputer" to run YT Music Vanced, and YT Vanced along with a few other media apps. Plus Torque for live OBDII diagnostics
Yes, it should be work
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

Furiouss
Posts: 1
Joined: Wed Sep 08, 2021 2:06 am
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by Furiouss »

Hi,
I installed the last image with gapps one a brand new odroid c4 i'm setuping ofr my dad, and I keep having the uncertified warning from google services, so I installed device_id, registered the ID on google.com/android/uncertified and still after a reboot its not working.
Before that I tried the android version on the wiki (https://wiki.odroid.com/odroid-c4/os_im ... id/android) and it was the same.
Any Ideas ? :(

User avatar
theronmad
Posts: 4
Joined: Sat Sep 25, 2021 1:38 am
languages_spoken: english
ODROIDs: ODROID-C1
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by theronmad »

suchit1989 wrote:
Sat Feb 27, 2021 10:42 pm
How Can I download this Alpha v0.5 android source code? I need to build and flash. Could you pls provide me steps how to download ?
voodik wrote:
Tue Jan 26, 2021 8:08 pm
Update :!:

Code: Select all

20210126 Alpha-v0.5
* Added new External Camera HAL(to use old one setprop persist.camera.legacy_hal true)
* Added WIFI Direct feature (disabled by default)
* Added Miracast(WFD) sink/source support
* Added mouse right click option to Odroid Settings
* Added Enable/Disable CEC globally to Odroid Settings
* Added pinch zoom by mouse wheel
* Added setting rotate display after reboot
* Added several Joystick keylayout configs (fixed broken ones) 
* Added Google Search app (Google Assistant is working, check device system language from Settings> System > Languages and input)
* Kernel enable CONFIG_HID_SMARTJOYPLUS
* Kernel added Realtek 8814au 8192eu 8188fu WIFI drivers
* Kernel added Mediatek mt7601u WIFI driver
* Kernel enabled P2P support on supported Realtek WIFI drivers
* Sync wifi_id_list with drivers (add missing vid/pid)
* Fixed Recovery HDMI output with custom resolution
* Fixed i2s1 output on J7
* Fixed USB Microphone input (Fixes Ok Google)
* Disabled DEXPREOPT for some targets (free up space on system partition)
* Removed ro.sf.defaultrotation property (use native ro.surface_flinger.primary_display_orientation)
* Minor cleanup/fixes
* Lineage merge with upstream
* Merge latest BSP changes
New Camera HAL config file location

Code: Select all

/odm/external_camera_config.xml
How to enable WIFI Direct/WFD/Miracast support
viewtopic.php?p=316848#p316848
also can't find this

User avatar
odroid
Site Admin
Posts: 42480
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3708 times
Been thanked: 2079 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by odroid »

Install 0.4 image and update it to 0.6 via Ethernet if your WiFi doesn't work.

rdowell
Posts: 12
Joined: Tue Mar 23, 2021 7:31 am
languages_spoken: english
ODROIDs: C2, C4
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by rdowell »

Is there a way to setup persistent GPIO exports using this image? With the default hardkernel image I was able to create a gpio.rc script with my exports and place it in /odm/etc/init/ but that doesn't seem to work here.

Code: Select all

on late-init
    write /sys/class/gpio/export 490
    write /sys/class/gpio/gpio490/direction in
    write /sys/class/gpio/gpio490/edge both
    ...
I tried moving the script to /etc/init or /vendor/etc/init instead but still no effect

jholbrook514
Posts: 41
Joined: Wed Mar 06, 2019 10:00 am
languages_spoken: english
ODROIDs: Odroid C1, C2, XU4, C4, N2, N2+, Odroid Go, OGA, OGU
Has thanked: 4 times
Been thanked: 4 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by jholbrook514 »

Does this work with the VU7A+ ?? I have the VU7A+ in my car with my C4 running stock android, id like to switch to LineageOS

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

Hi guys, great ROM, I have been able to use usb_modeswitch to switch from ethernet to 4G huawei dongle to provide internet connection.
After adding magisk root, fiddling around with changing the boot logo and bootanimation (succesfull) I installed my app that has settings to allow auto-start after device boots up.
Unfortunately, when the device boots, it stays at the desktop and nothing changes.
Where should I look for clues ?

edit: i have doublechecked with a "clear" selfinstall-odroidc4-lineage-17.1_alpha-0.4_20201113.ng.img - my app also doesn't auto-start even if the auto-start option is set in its settings.

edit2: stock android, downloaded from https://de.eu.odroid.in/?directory=.%2F ... ie%2F64%2F - the newest one, when started, allows my app to auto-start... so there must be a difference somewhere between "stock" android and this lineage rom. The reason im using lineage is also usb_modeswitch, so it's important.

Please help!

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

joerg wrote:Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.
Sorry, im not the author of app so dont have that. Maybe apk will help - https://central.stacks.pl/ds-loader.apk in Ds settings its set to autostart so Ds loader should start and show Mac address of computer


Wysłane z iPhone za pomocą Tapatalk

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

OK, so I can't help much. It depends on the app code if it supports all the Android versions. The stock version is 9, @voodik LOS versions are 10 and 11.

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

qlex wrote:
Wed Feb 16, 2022 11:44 pm
joerg wrote:Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.
Sorry, im not the author of app so dont have that. Maybe apk will help - https://central.stacks.pl/ds-loader.apk in Ds settings its set to autostart so Ds loader should start and show Mac address of computer


Wysłane z iPhone za pomocą Tapatalk
I will check this app
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

voodik wrote:
qlex wrote:
Wed Feb 16, 2022 11:44 pm
joerg wrote:Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.
Sorry, im not the author of app so dont have that. Maybe apk will help - https://central.stacks.pl/ds-loader.apk in Ds settings its set to autostart so Ds loader should start and show Mac address of computer


Wysłane z iPhone za pomocą Tapatalk
I will check this app
Thanks [mention]voodik [/mention] I could also use your Android 9 or 11 if that helps. I only need to be able to use Huawei e3372 as alternative (or simply Ethernet) and replace boot logos, so if any Android supports autostart of that app that I’m using, it’s ok


Wysłane z iPhone za pomocą Tapatalk

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

In the meantime I got this from app manufacturer - do you think it’s the best option?

Code: Select all

  DS Loader will attempt to auto start the digital signage software when the device is first booted. However, this fails on some devices, particularly those running Android 10 and up.

There are a couple of solutions.

First, ensure the option Auto start and keep running is enabled in DS Settings. This is enabled by default but may have been disabled accidentally.

Assuming this option is enabled. Try the following:

Android Settings
Apps
Special App Access
Display over other apps
DS Loader
Allow.
Finally, if the above still fails to auto start DS Loader, you can run it as a screen saver instead:

Android Settings
Device Preferences
Screen saver
DS Loader
5 mins inactivity  

edit: confirming this works - allowing ds-loader to display over other apps solves the problem.

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

qlex wrote:
Thu Feb 17, 2022 6:12 am
voodik wrote:
qlex wrote:
Wed Feb 16, 2022 11:44 pm
joerg wrote:Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.
Sorry, im not the author of app so dont have that. Maybe apk will help - https://central.stacks.pl/ds-loader.apk in Ds settings its set to autostart so Ds loader should start and show Mac address of computer


Wysłane z iPhone za pomocą Tapatalk
I will check this app
Thanks [mention]voodik [/mention] I could also use your Android 9 or 11 if that helps. I only need to be able to use Huawei e3372 as alternative (or simply Ethernet) and replace boot logos, so if any Android supports autostart of that app that I’m using, it’s ok


Wysłane z iPhone za pomocą Tapatalk
So let's try find solution for you.

First install latest Lineage-18.1 version from here
https://oph.mdrjr.net/voodik/S905X3/ODR ... lfinstall/
or without gapps version if you don't need google services
https://oph.mdrjr.net/voodik/S905X3/ODR ... lfinstall/

Then ignore ds-loader auto-start option and check is your app working normally when you start it manually.
also check usb-modeprobe and everything you need for your project.
in this version you can put your bootanimation.zip to /odm/media folder and it will persist across updates.

In general I make Lineage-18.1 more customizable and use /odm partition (this partition not rewrite across updates) for keeping custom configs.

About auto start your application after boot.
I can't debug why this app cannot start after boot because does not have sources.
But if Lineage-18.1 is ok for you i will suggest method how to start ds-loader after boot via init.rc script.

P.S.
Check /odm/etc/modprobe.d/default.conf you can find there usb-modeswitch example.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

Burette
Posts: 86
Joined: Sat Feb 05, 2022 8:14 am
languages_spoken: english, français
ODROIDs: C4
Location: Montréal, Canada
Has thanked: 16 times
Been thanked: 2 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by Burette »

I once had Lineage on my Nexus5 phone.

I have read the first pages of this topic and did not find an anwer to my question.

What are the benefits of this ROM vs HK original Android 9 ROM ?

Thanks

User avatar
rooted
Posts: 10627
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 822 times
Been thanked: 736 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by rooted »

Burette wrote:I once had Lineage on my Nexus5 phone.

I have read the first pages of this topic and did not find an anwer to my question.

What are the benefits of this ROM vs HK original Android 9 ROM ?

Thanks
All the features of LineageOS

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

voodik wrote:
qlex wrote:
Thu Feb 17, 2022 6:12 am
voodik wrote:
qlex wrote:
Wed Feb 16, 2022 11:44 pm
joerg wrote:Can you please show the manifest and the part of java/kotlin code that manages the autostart. I can compare it with my apps that do autostart.
Sorry, im not the author of app so dont have that. Maybe apk will help - https://central.stacks.pl/ds-loader.apk in Ds settings its set to autostart so Ds loader should start and show Mac address of computer


Wysłane z iPhone za pomocą Tapatalk
I will check this app
Thanks [mention]voodik [/mention] I could also use your Android 9 or 11 if that helps. I only need to be able to use Huawei e3372 as alternative (or simply Ethernet) and replace boot logos, so if any Android supports autostart of that app that I’m using, it’s ok


Wysłane z iPhone za pomocą Tapatalk
So let's try find solution for you.

First install latest Lineage-18.1 version from here
https://oph.mdrjr.net/voodik/S905X3/ODR ... lfinstall/
or without gapps version if you don't need google services
https://oph.mdrjr.net/voodik/S905X3/ODR ... lfinstall/

Then ignore ds-loader auto-start option and check is your app working normally when you start it manually.
also check usb-modeprobe and everything you need for your project.
in this version you can put your bootanimation.zip to /odm/media folder and it will persist across updates.

In general I make Lineage-18.1 more customizable and use /odm partition (this partition not rewrite across updates) for keeping custom configs.

About auto start your application after boot.
I can't debug why this app cannot start after boot because does not have sources.
But if Lineage-18.1 is ok for you i will suggest method how to start ds-loader after boot via init.rc script.

P.S.
Check /odm/etc/modprobe.d/default.conf you can find there usb-modeswitch example.
[mention]voodik [/mention] thanks for helping out. I managed to get the app auto start using that option suggested by app creator (described above in edited post). Will use your software and hopefully it will be stable - using it as digital signage in public transport.

Was wondering if there’s an option to have custom errors for WebKit browser if internet connection is temporarily not available so instead of “website not found” error (that appears when digital signage software tries to open a website with no internet connection) we could show a custom made website - in times of Android 5/6 we replaced noload.html and other html file with own one.


Wysłane z iPhone za pomocą Tapatalk

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

I'm still using this great ROM on my in-law's C4, as a media player mostly. I've just upgraded to the latest release (from mid 2021), and I was wondering if this should work: viewtopic.php?p=336902&sid=d45090421bc8 ... d6#p336902

I put a startup script in /odm/etc/init/startup.rc, made it executable, and inside it's something like:

Code: Select all

#!/bin/sh
sleep 50
input tap 746 827

which should turn on a widget on the desktop for automatic VPN connection. It works when called manually, but not on boot. As a workaround, I'm calling the script from inside /vendor/bin/makebootini for now...

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

mad_ady wrote:
Mon Dec 26, 2022 2:23 am
I'm still using this great ROM on my in-law's C4, as a media player mostly. I've just upgraded to the latest release (from mid 2021), and I was wondering if this should work: viewtopic.php?p=336902&sid=d45090421bc8 ... d6#p336902

I put a startup script in /odm/etc/init/startup.rc, made it executable, and inside it's something like:

Code: Select all

#!/bin/sh
sleep 50
input tap 746 827

which should turn on a widget on the desktop for automatic VPN connection. It works when called manually, but not on boot. As a workaround, I'm calling the script from inside /vendor/bin/makebootini for now...
Nope, android init have a it's own syntax for rc files.
e.g.

Code: Select all

service myservice /system/bin/input tap 746 827
    class core
    user shell
    group shell
    seclabel u:r:shell:s0
    disabled
    oneshot

on property:sys.boot_completed=1
    start myservice
So if you need run script first post your script to /data partition, odm is FAT fs so you can set any flags.
/data/myscript.sh
and create rc script like

Code: Select all

service myscript /data/myscript.sh
    class core
    seclabel u:r:shell:s0
    user root
    group root
    disabled
    oneshot

on property:sys.boot_completed=1
    start myscript
EDIT:
This not work on old Lineage versions, you should use 18.1 and up
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
mad_ady
Posts: 12034
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 663 times
Been thanked: 1298 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Thanks for the extra details, voodik! Enjoy your holidays!

phatlewt
Posts: 2
Joined: Mon Nov 28, 2022 6:54 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by phatlewt »

Is the Vu7C touchscreen supported? After editing env.ini the screen can be displayed, but not sure how to enable touch.

User avatar
voodik
Posts: 2666
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 115 times
Been thanked: 805 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

phatlewt wrote:
Tue Jan 10, 2023 12:23 pm
Is the Vu7C touchscreen supported? After editing env.ini the screen can be displayed, but not sure how to enable touch.
Use upper version.
viewtopic.php?f=204&t=44808
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

Hey guys!
Need to revive this thread a little. Got >100 odroids c4 running in remote locations (eMMC) and periodically have this message on the screen. What could be the cause - eMMC failure or something else? What can be done - access to those devices is quite limited and complicated....
recovery-screenshot.jpg
recovery-screenshot.jpg (80.5 KiB) Viewed 127 times
Thanks for any pointers..

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

Bumping my problem with recovery screen. Nobody watches this forum anymore? I know i should upgrade to newer version of lineageos - is it possible to do it OTA somehow? Access to odroid or emmc is limited, but we could work on using mouse+keyboard attached to usb.

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Was there a sudden power outage that has corrupted the emmc? Or can you reboot and it works again?
As far as I know, there is no way to upgrade with OTA.

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

Yes there are frequent power outages but it didn’t influence other odroids. I think each restart ends with this message now.


Wysłane z iPhone za pomocą Tapatalk

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I think a power outage can corrupt the emmc storage, but not always. How often? Who knows. But with your >100 installations, you probably see it now and then. Android was built for battery powered devices, these devices normally do not have power outages. It's the reason why I have created my app ShutdownService, especially for car use, to have an ordered battery buffered shutdown and not a sudden power outage when the car is switched off.
Can you tell more about the installation of your Odroids?

qlex
Posts: 104
Joined: Tue Jul 29, 2014 6:21 pm
languages_spoken: english, polish
ODROIDs: C1, C1+, C2, U3 (a lot of them!)
Has thanked: 3 times
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by qlex »

@joerg thanks for info. We have taken out that Odroid and it turnes out that emmc is still ok (we managed to write a new image on it) but Odroid stopped working. No blue pulse led but only solid red.


Wysłane z iPhone za pomocą Tapatalk

User avatar
joerg
Posts: 2085
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 214 times
Been thanked: 482 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

@qplex, to know if this C4 is dead please us an uart adapter. There must be some scanning messages from u-boot. If there are no messages, then I guess the C4 is broken. Another thing is to measure voltage at pin1 3.3V and 5V at pin 2. Can you try the emmc with another C4, to check if the emmc card makes the problem? Because also if there are messages from u-boot, it can be that only the mmc ports are not working anymore.

Post Reply

Return to “Android”

Who is online

Users browsing this forum: No registered users and 4 guests