[ROM][LineageOS 20.0][Android 13][voodik] for the ODROID-N2/N2L

[zyssai]

I see, I have tried this app also now. It seems the the developer has forced portrait mode and it has no landscape layout.

Thanks for give it a try.
As I said, it does not really matter. I use default text size and I just seen this behavior in a friend car while I installed my project and he wanted a bigger text size.
But he will not have to use this app, at least, not as much as me

[mad_ady]

There's always the option of contacting the developer, explaining the problem and use case and hoping for the best...

[zyssai]

There's always the option of contacting the developer, explaining the problem and use case and hoping for the best...

That's a good idea, as this is an app with a lot of development settings, I think they can work on it.
I will write to the team

[zyssai]

I just faced this, and don't know if it's a normal behavior.

When leaving a USB key while shutting down, the next power on status will not recognize USB key. We need to remove and reinsert USB key to be recognized again.

[ubair]

Hello I am running LineageOS 20.0][Android 13][voodik] for the Odroid N2L . I am Facing Problem of Using Any Application as It shows This device isn't Play Protected certified . what should i do

[zyssai]

Hello I am running LineageOS 20.0][Android 13][voodik] for the Odroid N2L . I am Facing Problem of Using Any Application as It shows This device isn't Play Protected certified . what should i do

https://www.google.com/android/uncertified/

You can find your ID in the Odroid Settings app.
Need to wait some time before it takes effect.

[ast260ast]

https://www.techradar.com/news/android- ... -efficient

[voodik]

Something new on the way

Latest BSP and ATV version ready.

Lineage-20.0-ATV-r21p0.png (72.44 KiB) Viewed 3076 times

Mali driver updated to r21p0

Mali-r21p0.png (180.6 KiB) Viewed 3076 times

1.1.117 Vulkan API (hwui can rendered via Vulkan)

Vulkan-r21p0-1.1.117.png (82.29 KiB) Viewed 3076 times

Compare Vulkan API
https://vulkan.gpuinfo.org/compare.php? ... 2630,22339

And the most important is new HIDL Gralloc v3.0 is ported and fixed to work on our Hardware!
So our Hardware OMX Decoders/Encoders is working !

I continue stability tests, if no major issues found i will release it soon as test version.

[zyssai]

Wonderful work, you're amazing

[voodik]

Uh, finally found and fixed 4k60fps hdr video issues. So image will released soon. BTW I open separate thread for it. If no major issues found i move all my projects to new drivers and drop old ones. The space for each new project is about 350gb )))

[voodik]

Progress update
Hardware encoders doesn't work in most cases. New gralloc have a new private buffer sucture and mali blob depends on it. Video encoder is hardcoded on old private buffer structure.
So i disable hw enconders for android Mediacodec/Recorder. BTW our hw encoders can maximum do 1080p, Software encoders also can do it with medium cpu usage.
We are lucky that DECODERS don't depend on gralloc private structure and working with any supported format !!

Now i have a question. When i started Android 13 development i facing low space on system partition. So Android 13 was released with 1GB more bigger system partition by reducing data partition size.
Now after framework cleanups and more optimizing i facing 1.3GB free space on system partition. If I release new image with smaller system partition you cannot update from old version but have 1GB more space on data(internal storage).
So please vote to understand what to do )))

[zyssai]

In my case it's not a big deal, will install from scratch with pleasure, always happy to test new releases, thanks for this

[loznic89]

Progress update
Hardware encoders doesn't work in most cases. New gralloc have a new private buffer sucture and mali blob depends on it. Video encoder is hardcoded on old private buffer structure.
So i disable hw enconders for android Mediacodec/Recorder. BTW our hw encoders can maximum do 1080p, Software encoders also can do it with medium cpu usage.
We are lucky that DECODERS don't depend on gralloc private structure and working with any supported format !!

Now i have a question. When i started Android 13 development i facing low space on system partition. So Android 13 was released with 1GB more bigger system partition by reducing data partition size.
Now after framework cleanups and more optimizing i facing 1.3GB free space on system partition. If I release new image with smaller system partition you cannot update from old version but have 1GB more space on data(internal storage).
So please vote to understand what to do )))

what you see better voodik. In my case I don't mind doing a clean install.

[Nortonko]

in my case it doesn't matter. i'll do a clean install. anyway great work thank you

[eruo1]

New install works for me too. Thanks Voodik!

[voodik]

Okay, thanks guys. I will release new image with reduced system partition size. Just waiting for Hardkernel specs answer about recovery issue i found.
Btw, today i backed up and recover data partition via Linux machine and rsync. Rsync can preserve Selinux contexts which need Android. I will post commands how to mound emmc raw partition and rsync files to pc and after fresh install back. Maybe someone want to preserve user data.

[wireshark]

thank you!
This makes me very happy.
How do I get the fan to work?

[voodik]

thank you!
This makes me very happy.
How do I get the fan to work?

I think if you search on forum you found solution. Btw you can enable separate thread to get solution. I don’t have n2 fan and can’t do some tests.

[wireshark]

thank you!
This makes me very happy.
How do I get the fan to work?

I think if you search on forum you found solution. Btw you can enable separate thread to get solution. I don’t have n2 fan and can’t do some tests.

I did the following modifications in boot.ini and it solved.

Code: Select all

###################
#dtboconfigs
###################

setenv overlays "uart0" fanspeed-full
setenv overlays_resize 16384

Thank you always.
I'm feeling good

[voodik]

I couldn't imagine but don't stopping my attempts.
And finally by extending new gralloc by part of old gralloc. And apply old gralloc private structure on HW_ENCODER usage buffers the HARDWARE encoders are WORKING now!!!))

[mad_ady]

I don't know what you did there, but it sounds like a massive hack! Congratulations!

[voodik]

I don't know what you did there, but it sounds like a massive hack! Congratulations!

Yeah, it’s like fixing Tesla with Mercedes C124 parts))))

[voodik]

Ready
viewtopic.php?f=178&t=47125

Just one known issue at this moment, recovery UI only work with 1080p resolution.
This comes with new BSP, @codewalker already know about this issue and will fix it when have a some free time.

[mike0odroid]

Coming from the Android 12 version this has been nice and stable for me. I do have one issue though, I'm just not sure if it's related to the build or to hardware. In between flashing this newer version my old touchscreen monitor died and I got an ASUS VT229H. It looks good and mostly works fine but there seems to be 0 "fling" velocity for lack of a better term. I don't know if there's a way I can modify that myself or if it's just something I have to live with but I'd appreciate any suggestions. Thanks.

[vices]

Hi All,
I'm new here, may I know where can I get the Android 13 source code for Odroid-N2 so I can try compiling it? And the recommended kernel for it.
Appreciate your reply. Thanks.

[roterdrachen]

Hi I have Lineage 20-20221212 installed with Magisk with a few Apps installed. Can I upgrade to latest version? And if, how? Or is it better to do a clean install?
I must admit I don´t want to install all new. Michael

[voodik]

Hi I have Lineage 20-20221212 installed with Magisk with a few Apps installed. Can I upgrade to latest version? And if, how? Or is it better to do a clean install?
I must admit I don´t want to install all new. Michael

20221212 is latest version for this build.
I released other Lineage-20 with latest Mali GPU drivers and lot of other improvements.
viewtopic.php?f=178&t=47125

But you can't update to it because of new partition scheme. You should install it from scratch.

[mike0odroid]

Adding some more info from my earlier post in case anyone sees this. The ASUS VT229H I'm having problems with is listed as

Code: Select all

Device 005: ID 2575:0401 Weida Hi-Tech Co., Ltd. CoolTouchR System

in lsusb, and does seem to work fine on the official android 9 image from Odroid. I'm trying to figure out if it's a driver issue or what. the best way I know how to describe the problem is that when you're swiping vertical or horizontal on a window that should let you fling and scroll for a while it just stops rapidly. it's more than a minor annoyance because it can be difficult to flip homescreen pages. Wondering if it's possible for me to copy something from the Odroid image over this Android 13 (or the updated mali version) image?

[tb2668]

Hi Voodik,

first of all, thank you for your great work.
Everything is working really well.

However, I have an issue which I hope you can help me with.
I am building a car head unit which uses a CanBus serial device connected via USB.
The device mounts to /dev/ttyACM0.
This causes a conflict with the GPS dongle, which usually also mounts to /dev/ttyACM0.

How can I make the GPS dongle mount to /dev/ttyACM1 instead?

I found some suggestions in other threads, but nothings is working so far (system ui crash, gps not recognized, ...)

Hope you can help.
Cheers.

EDIT:
Is the something like udev rules in the ROM, so a solution like this could be used?

EDIT2:
The issue seems to be similar to this.
Is it possible to have a similar patch?

[voodik]

Hi Voodik,

first of all, thank you for your great work.
Everything is working really well.

However, I have an issue which I hope you can help me with.
I am building a car head unit which uses a CanBus serial device connected via USB.
The device mounts to /dev/ttyACM0.
This causes a conflict with the GPS dongle, which usually also mounts to /dev/ttyACM0.

How can I make the GPS dongle mount to /dev/ttyACM1 instead?

I found some suggestions in other threads, but nothings is working so far (system ui crash, gps not recognized, ...)

Hope you can help.
Cheers.

EDIT:
Is the something like udev rules in the ROM, so a solution like this could be used?

EDIT2:
The issue seems to be similar to this.
Is it possible to have a similar patch?

When both devices is connected one should be ttyACM0 second ttyACM1.
If you want swap ACM number you can just swap USB ports.
if you want force GPS configuration to ttyACM1 edit /odm/etc/build.prop and set

Code: Select all

ro.kernel.android.gps=ttyACM1

[tb2668]

When both devices is connected one should be ttyACM0 second ttyACM1.
If you want swap ACM number you can just swap USB ports.
if you want force GPS configuration to ttyACM1 edit /odm/etc/build.prop and set

Code: Select all

ro.kernel.android.gps=ttyACM1

Thank you for the quick reply.
The system ui still crashing (screen keeps reloading and not recognizing any input).
Also sometimes after reboot the Wifi Stick is not recognized when the GPS stick is plugged in.

This is the last piece missing for my head unit to be done.

[voodik]

When both devices is connected one should be ttyACM0 second ttyACM1.
If you want swap ACM number you can just swap USB ports.
if you want force GPS configuration to ttyACM1 edit /odm/etc/build.prop and set

Code: Select all

ro.kernel.android.gps=ttyACM1

Thank you for the quick reply.
The system ui still crashing (screen keeps reloading and not recognizing any input).
Also sometimes after reboot the Wifi Stick is not recognized when the GPS stick is plugged in.

This is the last piece missing for my head unit to be done.

Setup adb access, and dump logs. logcat, lsusb, dmesg

[tb2668]

Setup adb access, and dump logs. logcat, lsusb, dmesg

Thanks.
Here you go: log dumps

Cheers

[voodik]

Setup adb access, and dump logs. logcat, lsusb, dmesg

Thanks.
Here you go: log dumps

Cheers

1. Your microsd card have problems. Test without it.

Code: Select all

[   30.592888] sd: req failed (CMD18): -110, retrying...
[   30.592921] meson-mmc: sd: resp_timeout,vstat:0xe1f08800,virqc:3fff
[   30.599278] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.605530] meson-mmc: Command retried failed line:664, cmd:18
[   30.611580] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.618116] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.624330] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.630827] meson-mmc: meson_mmc_irq_thread_v3() 642: set 1st retry!
[   30.637354] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.643488] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.649936] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.656139] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.662696] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.668791] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.675299] meson-mmc: Command retried failed line:664, cmd:13
[   30.681137] mmcblk1: error -110 sending status command, retrying

2. You are using Ralink chip based WIFI. As I remember this modules have issues with Encrypted networks. So i can't recommend it.

Code: Select all

[   42.902280] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   51.862608] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   63.895353] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[  299.193094] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193102] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193106] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  303.936789] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 7 in queue 2
[  303.957092] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 12 in queue 2
[  303.998392] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 14 in queue 2

I don't see any crashes in your log dump. BTW check your power source, you need stable DC converter in your project.

[tb2668]

1. Your microsd card have problems. Test without it.

Code: Select all

[   30.592888] sd: req failed (CMD18): -110, retrying...
[   30.592921] meson-mmc: sd: resp_timeout,vstat:0xe1f08800,virqc:3fff
[   30.599278] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.605530] meson-mmc: Command retried failed line:664, cmd:18
[   30.611580] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.618116] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.624330] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.630827] meson-mmc: meson_mmc_irq_thread_v3() 642: set 1st retry!
[   30.637354] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.643488] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.649936] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.656139] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.662696] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.668791] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.675299] meson-mmc: Command retried failed line:664, cmd:13
[   30.681137] mmcblk1: error -110 sending status command, retrying

2. You are using Ralink chip based WIFI. As I remember this modules have issues with Encrypted networks. So i can't recommend it.

Code: Select all

[   42.902280] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   51.862608] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   63.895353] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[  299.193094] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193102] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193106] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  303.936789] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 7 in queue 2
[  303.957092] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 12 in queue 2
[  303.998392] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 14 in queue 2

I don't see any crashes in your log dump. BTW check your power source, you need stable DC converter in your project.

I removed the SD card and the Wifi stick, but it did not make a difference.
As for the power supply, I am using GPIO'4'Cars from zyssai.

I also pulled new dumps and added videos of a boot with and without GPS stick (U Blox 7).
You can see that without the GPS stick it boots properly.
With the GPS stick everything is freezing and the screen turns black sometimes (not seen on video).
GDrive

[voodik]

1. Your microsd card have problems. Test without it.

Code: Select all

[   30.592888] sd: req failed (CMD18): -110, retrying...
[   30.592921] meson-mmc: sd: resp_timeout,vstat:0xe1f08800,virqc:3fff
[   30.599278] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.605530] meson-mmc: Command retried failed line:664, cmd:18
[   30.611580] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.618116] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.624330] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.630827] meson-mmc: meson_mmc_irq_thread_v3() 642: set 1st retry!
[   30.637354] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.643488] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.649936] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.656139] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.662696] meson-mmc: sd: resp_timeout,vstat:0xa1f0a800,virqc:3fff
[   30.668791] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[   30.675299] meson-mmc: Command retried failed line:664, cmd:13
[   30.681137] mmcblk1: error -110 sending status command, retrying

2. You are using Ralink chip based WIFI. As I remember this modules have issues with Encrypted networks. So i can't recommend it.

Code: Select all

[   42.902280] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   51.862608] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[   63.895353] ieee80211 phy0: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[  299.193094] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193102] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  299.193106] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 8 in queue 2
[  303.936789] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 7 in queue 2
[  303.957092] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 12 in queue 2
[  303.998392] ieee80211 phy0: rt2800usb_txdone: Warning - Data pending for entry 14 in queue 2

I don't see any crashes in your log dump. BTW check your power source, you need stable DC converter in your project.

I removed the SD card and the Wifi stick, but it did not make a difference.
As for the power supply, I am using GPIO'4'Cars from zyssai.

I also pulled new dumps and added videos of a boot with and without GPS stick (U Blox 7).
You can see that without the GPS stick it boots properly.
With the GPS stick everything is freezing and the screen turns black sometimes (not seen on video).
GDrive

I will try to reproduce this issue with GPS modules connected.

[voodik]

@tb2668

Please remove ro.kernel.android.gps=ttyACM1 prop, and immediately after fresh boot run

Code: Select all

logcat | grep UsbDevReceiver

and

Code: Select all

logcat | grep gps_serial

[tb2668]

@tb2668

Please remove ro.kernel.android.gps=ttyACM1 prop, and immediately after fresh boot run

Code: Select all

logcat | grep UsbDevReceiver

and

Code: Select all

logcat | grep gps_serial

I uploaded the logs you asked for and commented ro.kernel.android.gps=ttyACM1 in /odm/etc/build.prop.
GDrive

But I also got this output:

Code: Select all

# getprop|grep gps
[sys.kernel.android.gps]: [ttyACM1]

Not sure if that is set in another build.prop-file.
I did check /vendor/build.prop and /system/build.prop and was commented out.

EDIT
"logcat | grep UsbDevReceiver" did not give any output

[voodik]

@tb2668

Please remove ro.kernel.android.gps=ttyACM1 prop, and immediately after fresh boot run

Code: Select all

logcat | grep UsbDevReceiver

and

Code: Select all

logcat | grep gps_serial

I uploaded the logs you asked for and commented ro.kernel.android.gps=ttyACM1 in /odm/etc/build.prop.
GDrive

But I also got this output:

Code: Select all

# getprop|grep gps
[sys.kernel.android.gps]: [ttyACM1]

Not sure if that is set in another build.prop-file.
I did check /vendor/build.prop and /system/build.prop and was commented out.

EDIT
"logcat | grep UsbDevReceiver" did not give any output

to get logcat | grep UsbDevReceiver you should run it while device booting.

sys.kernel.android.gps is set automatically by framework, when U Blox device is detected.

Is your GPS dongle working when your CanBus serial device is not connected ?

[tb2668]

to get logcat | grep UsbDevReceiver you should run it while device booting.

sys.kernel.android.gps is set automatically by framework, when U Blox device is detected.

Is your GPS dongle working when your CanBus serial device is not connected ?

Ok, I got a dump now.
With CAN Bus dongle connected:

Code: Select all

odroidn2:/ # logcat | grep UsbDevReceiver
12-12 13:32:03.976  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.977  3753  3753 I UsbDevReceiver: MNG finding tty node with vid 0x1546 pid 0x0
12-12 13:32:03.979  3753  3753 I UsbDevReceiver: MNG attached: ttyACM1
12-12 13:32:03.982  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.987  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.988  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED

With CAN Bus dongle disconnected:

Code: Select all

odroidn2:/ # logcat | grep UsbDevReceiver
11-21 23:05:12.436  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
11-21 23:05:12.438  3735  3735 I UsbDevReceiver: MNG finding tty node with vid 0x1546 pid 0x0
11-21 23:05:12.440  3735  3735 I UsbDevReceiver: MNG attached: ttyACM0
11-21 23:05:12.444  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
11-21 23:05:12.445  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED

SystemUI still seems to freeze / miss behave when GPS stick is connected and the CAN Bus dongle is disconnected.

[voodik]

to get logcat | grep UsbDevReceiver you should run it while device booting.

sys.kernel.android.gps is set automatically by framework, when U Blox device is detected.

Is your GPS dongle working when your CanBus serial device is not connected ?

Ok, I got a dump now.
With CAN Bus dongle connected:

Code: Select all

odroidn2:/ # logcat | grep UsbDevReceiver
12-12 13:32:03.976  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.977  3753  3753 I UsbDevReceiver: MNG finding tty node with vid 0x1546 pid 0x0
12-12 13:32:03.979  3753  3753 I UsbDevReceiver: MNG attached: ttyACM1
12-12 13:32:03.982  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.987  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
12-12 13:32:03.988  3753  3753 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED

With CAN Bus dongle disconnected:

Code: Select all

odroidn2:/ # logcat | grep UsbDevReceiver
11-21 23:05:12.436  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
11-21 23:05:12.438  3735  3735 I UsbDevReceiver: MNG finding tty node with vid 0x1546 pid 0x0
11-21 23:05:12.440  3735  3735 I UsbDevReceiver: MNG attached: ttyACM0
11-21 23:05:12.444  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED
11-21 23:05:12.445  3735  3735 I UsbDevReceiver: action: android.hardware.usb.action.USB_DEVICE_ATTACHED

SystemUI still seems to freeze / miss behave when GPS stick is connected and the CAN Bus dongle is disconnected.

Did you get readable output when ?

Code: Select all

cat /dev/ttyACM0

[tb2668]

Did you get readable output when ?

Code: Select all

cat /dev/ttyACM0

I do get a readable output in both cases.
Only GPS Stick:

Code: Select all

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /dev/ttyACM0
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,11,,,27*7D
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,12,,,20*79
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64

GPS Stick and CAN Bus dongle plugged in:

Code: Select all

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /dev/ttyACM1
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,18,,,28*7B
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,19,,,28*7A
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64

[voodik]

Did you get readable output when ?

Code: Select all

cat /dev/ttyACM0

I do get a readable output in both cases.
Only GPS Stick:

Code: Select all

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /dev/ttyACM0
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,11,,,27*7D
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,12,,,20*79
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64

GPS Stick and CAN Bus dongle plugged in:

Code: Select all

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /dev/ttyACM1
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,18,,,28*7B
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,01,19,,,28*7A
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64
$GPRMC,,V,,,,,,,,,,N*53
$GPVTG,,,,,,,,,N*30
$GPGGA,,,,,,0,00,99.99,,,,,,*48
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGLL,,,,,,V,N*64

I can't find my Ublox 7 module so i made tests with Ublox 8. Btw can you find some working microsd card, install Android from scratch.
I recommend this version viewtopic.php?f=178&t=47125
Then just enable GPS from Odroid Settings > Misc page, reboot and test. Maybe something other makes troubles.

[voodik]

docker2.png (51.27 KiB) Viewed 337 times

docker1.png (67.86 KiB) Viewed 337 times

I was able to backport the 4.14 Kernel Cgroup2 features to N2 kernel.
Now docker working without much hacks.
I managed to set up SONOFF Zigbee 3.0 USB Dongle Plus V2 for HA and pair simple ZigBee button))

[mad_ady]

Awesome work!

[zyssai]

Great work as always, voodik

I have some weird display with some apps (here Spotify).
Is there something to do with dpi density to improve this behavior?
I use VU7C.

[voodik]

Great work as always, voodik

I have some weird display with some apps (here Spotify).
Is there something to do with dpi density to improve this behavior?
I use VU7C.

try to set smaller ones e.g.

Code: Select all

wm density 120

[tb2668]

I can't find my Ublox 7 module so i made tests with Ublox 8. Btw can you find some working microsd card, install Android from scratch.
I recommend this version viewtopic.php?f=178&t=47125
Then just enable GPS from Odroid Settings > Misc page, reboot and test. Maybe something other makes troubles.

The Vulkan version of the ROM didn't boot for me so I went back to Lineage 19.1 and so far everything is working.
I only added ro.kernel.android.gps=ttyACM1 to /odm/etc/env.ini.