[ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
No, I have not flashed the dtbs. And yes, I used voodik's defconfig and enabled the DS1307.
-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
I'll check my build environment (probably on monday) and report back.
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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:
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
- voodik
- Posts: 1996
- Joined: Sat Dec 07, 2013 2:36 am
- languages_spoken: armenian, english, russian
- Location: Armenia
- Has thanked: 47 times
- Been thanked: 327 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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.joerg wrote: ↑Sat Dec 19, 2020 7:37 pmYes @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
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

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
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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
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:
And I tried also the toolchain
Toolchains
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
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.-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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!)
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!)
- voodik
- Posts: 1996
- Joined: Sat Dec 07, 2013 2:36 am
- languages_spoken: armenian, english, russian
- Location: Armenia
- Has thanked: 47 times
- Been thanked: 327 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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
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

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
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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:
I think I am on the branch where the asterisk is.
Deleting the old branch, it's there because I have commited my changes.
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.
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
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
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.
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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
This is basically working, but not so optimal as inbuilt module.
I need to load the module from
First:
The module is loaded to late.
Then:
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
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:
It seems that
This line
/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
/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)
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
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
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}
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.-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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.
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.
- joerg
- Posts: 1306
- 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: 82 times
- Been thanked: 180 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
@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.
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.
-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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.
- voodik
- Posts: 1996
- Joined: Sat Dec 07, 2013 2:36 am
- languages_spoken: armenian, english, russian
- Location: Armenia
- Has thanked: 47 times
- Been thanked: 327 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
Update
New Camera HAL config file location
How to enable WIFI Direct/WFD/Miracast support
viewtopic.php?p=316848#p316848

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
Code: Select all
/odm/external_camera_config.xml
viewtopic.php?p=316848#p316848
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

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
-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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!
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!
- voodik
- Posts: 1996
- Joined: Sat Dec 07, 2013 2:36 am
- languages_spoken: armenian, english, russian
- Location: Armenia
- Has thanked: 47 times
- Been thanked: 327 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
Is your module directly connected to USB 3.0 port ?mad_ady wrote: ↑Tue Feb 09, 2021 5:10 amHey 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!
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

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
-
- Posts: 9250
- Joined: Wed Jul 15, 2015 5:00 pm
- languages_spoken: english
- ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
- Location: Bucharest, Romania
- Has thanked: 599 times
- Been thanked: 622 times
- Contact:
Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4
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,
-
- 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
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 pmUpdate![]()
New Camera HAL config file locationCode: 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
How to enable WIFI Direct/WFD/Miracast supportCode: Select all
/odm/external_camera_config.xml
viewtopic.php?p=316848#p316848
Who is online
Users browsing this forum: No registered users and 0 guests