[ROM][LineageOS 20.0][Android 13.0][Mali r44p0][Vulkan 1.3.231][ODROID-N2/N2L]

[Nortonko]

Hi,
i am try to get state detection via Android Debug Bridge integration for Home Assitant - https://www.home-assistant.io/integrati ... -detection.
I found that there is some missing info on response.
Response from odroid n2+ with [ROM][LineageOS 20.0][Android 13.0][Mali r44p0][Vulkan 1.3.231][ODROID-N2/N2L]:

Code: Select all

adb_response: >-
  {'screen_on': True, 'awake': True, 'audio_state': 'idle', 'wake_lock_size': 2,
  'current_app': None, 'media_session_state': None, 'audio_output_device':
  'hdmi', 'is_volume_muted': False, 'volume': 24, 'running_apps':
  ['com.android.systemui', 'android.ext.services',
  'com.google.android.tv.remote.service', 'com.google.android.gms.persistent',
  'com.google.android.gms', 'com.teamsmart.videomanager.tv',
  'com.google.process.gservices', 'com.google.android.katniss:interactor',
  'com.android.providers.media.module', 'com.android.inputmethod.leanback',
  'com.google.android.tvrecommendations', 'com.google.android.tvlauncher',
  'com.android.providers.tv', 'com.google.android.tts', 'com.viki.android',
  'com.android.vending', 'com.google.android.katniss:search',
  'com.android.vending:background', 'com.android.tv',
  'com.google.android.gms.unstable', 'org.xbmc.kodi',
  'de.cyberdream.dreamepg.tvh.tv.player', 'com.android.vending:quick_launch',
  'cz.ceskatelevize.ivysilani.tvapp', 'com.android.webview:webview_service',
  'com.android.webview:webview_apk', 'com.google.process.gapps'], 'hdmi_input':
  None}
hdmi_input: null
device_class: tv
entity_picture: >-
  /api/media_player_proxy/media_player.android_tv_172_23_23_31?token=a24e294ef871a02fe6907723c20b4d1d126588dca355f18a3babd55485c582de&cache=0d56520e40f0ce72
friendly_name: Android TV 172.23.23.31
supported_features: 23997
volume_level: 0.96
is_volume_muted: false

compare to response from another device (vontar X4 with slimboxTV ROM):

Code: Select all

adb_response: >-
  {'screen_on': True, 'awake': False, 'audio_state': None, 'wake_lock_size': 3,
  'current_app': None, 'media_session_state': None, 'audio_output_device': None,
  'is_volume_muted': None, 'volume': None, 'running_apps': None, 'hdmi_input':
  None}
hdmi_input: null
device_class: tv
friendly_name: Android TV 172.23.23.16
supported_features: 23997
source_list:
  - com.android.systemui
  - com.android.launcher3
  - com.google.android.ext.services
  - com.google.android.tv.remote.service
  - com.google.android.gms.persistent
  - com.android.providers.media.module
  - com.google.android.katniss:interactor
  - com.dolby
  - Android TV Launcher
  - com.google.process.gservices
  - com.google.android.tvrecommendations
  - com.google.android.katniss:search
  - com.android.providers.tv
  - com.google.process.gapps
  - android.process.acore
  - Play Store
  - org.liskovsoft.androidtv.rukeyboard
  - com.android.permissioncontroller
  - com.android.providers.calendar
  - com.android.vending:background
  - com.google.android.gms.unstable
  - DreamPlayer TVHeadend
  - com.android.gallery3d
  - com.android.packageinstaller
  - com.google.android.leanbacklauncher.partnercustomizer
  - cz.ceskatelevize.ivysilani.tvapp
  - com.android.webview:webview_service
  - com.android.webview:webview_apk
  - com.android.vending:quick_launch
volume_level: 0.9538461538461539
is_volume_muted: false
app_id: cz.ceskatelevize.ivysilani.tvapp
app_name: cz.ceskatelevize.ivysilani.tvapp
source: cz.ceskatelevize.ivysilani.tvapp
entity_picture: >-
  /api/media_player_proxy/media_player.android_tv_172_23_23_16?token=40aa38efae3a6060370d8f3a17986c4acbf31913f0f02695aff1242a90250393&cache=73563fe1bf91bb34

as you can see from second device there is some more info from response. Most important for me is the tags:

Code: Select all

app_id: xxxxxxxx
app_name: xxxxxxxxxxxx
source: xxxxxxxxxxxx

these are important to get the currently running application.
To get status of running app there is tag "wake_lock_size" - this is on your ROM from response OK.
I think these responses are hardcoded in the ROM, or am i wrong?
thanks for the reply/help.
sorry for my english

[voodik]

Hi,
i am try to get state detection via Android Debug Bridge integration for Home Assitant - https://www.home-assistant.io/integrati ... -detection.
I found that there is some missing info on response.
Response from odroid n2+ with [ROM][LineageOS 20.0][Android 13.0][Mali r44p0][Vulkan 1.3.231][ODROID-N2/N2L]:

Code: Select all

adb_response: >-
  {'screen_on': True, 'awake': True, 'audio_state': 'idle', 'wake_lock_size': 2,
  'current_app': None, 'media_session_state': None, 'audio_output_device':
  'hdmi', 'is_volume_muted': False, 'volume': 24, 'running_apps':
  ['com.android.systemui', 'android.ext.services',
  'com.google.android.tv.remote.service', 'com.google.android.gms.persistent',
  'com.google.android.gms', 'com.teamsmart.videomanager.tv',
  'com.google.process.gservices', 'com.google.android.katniss:interactor',
  'com.android.providers.media.module', 'com.android.inputmethod.leanback',
  'com.google.android.tvrecommendations', 'com.google.android.tvlauncher',
  'com.android.providers.tv', 'com.google.android.tts', 'com.viki.android',
  'com.android.vending', 'com.google.android.katniss:search',
  'com.android.vending:background', 'com.android.tv',
  'com.google.android.gms.unstable', 'org.xbmc.kodi',
  'de.cyberdream.dreamepg.tvh.tv.player', 'com.android.vending:quick_launch',
  'cz.ceskatelevize.ivysilani.tvapp', 'com.android.webview:webview_service',
  'com.android.webview:webview_apk', 'com.google.process.gapps'], 'hdmi_input':
  None}
hdmi_input: null
device_class: tv
entity_picture: >-
  /api/media_player_proxy/media_player.android_tv_172_23_23_31?token=a24e294ef871a02fe6907723c20b4d1d126588dca355f18a3babd55485c582de&cache=0d56520e40f0ce72
friendly_name: Android TV 172.23.23.31
supported_features: 23997
volume_level: 0.96
is_volume_muted: false

compare to response from another device (vontar X4 with slimboxTV ROM):

Code: Select all

adb_response: >-
  {'screen_on': True, 'awake': False, 'audio_state': None, 'wake_lock_size': 3,
  'current_app': None, 'media_session_state': None, 'audio_output_device': None,
  'is_volume_muted': None, 'volume': None, 'running_apps': None, 'hdmi_input':
  None}
hdmi_input: null
device_class: tv
friendly_name: Android TV 172.23.23.16
supported_features: 23997
source_list:
  - com.android.systemui
  - com.android.launcher3
  - com.google.android.ext.services
  - com.google.android.tv.remote.service
  - com.google.android.gms.persistent
  - com.android.providers.media.module
  - com.google.android.katniss:interactor
  - com.dolby
  - Android TV Launcher
  - com.google.process.gservices
  - com.google.android.tvrecommendations
  - com.google.android.katniss:search
  - com.android.providers.tv
  - com.google.process.gapps
  - android.process.acore
  - Play Store
  - org.liskovsoft.androidtv.rukeyboard
  - com.android.permissioncontroller
  - com.android.providers.calendar
  - com.android.vending:background
  - com.google.android.gms.unstable
  - DreamPlayer TVHeadend
  - com.android.gallery3d
  - com.android.packageinstaller
  - com.google.android.leanbacklauncher.partnercustomizer
  - cz.ceskatelevize.ivysilani.tvapp
  - com.android.webview:webview_service
  - com.android.webview:webview_apk
  - com.android.vending:quick_launch
volume_level: 0.9538461538461539
is_volume_muted: false
app_id: cz.ceskatelevize.ivysilani.tvapp
app_name: cz.ceskatelevize.ivysilani.tvapp
source: cz.ceskatelevize.ivysilani.tvapp
entity_picture: >-
  /api/media_player_proxy/media_player.android_tv_172_23_23_16?token=40aa38efae3a6060370d8f3a17986c4acbf31913f0f02695aff1242a90250393&cache=73563fe1bf91bb34

as you can see from second device there is some more info from response. Most important for me is the tags:

Code: Select all

app_id: xxxxxxxx
app_name: xxxxxxxxxxxx
source: xxxxxxxxxxxx

these are important to get the currently running application.
To get status of running app there is tag "wake_lock_size" - this is on your ROM from response OK.
I think these responses are hardcoded in the ROM, or am i wrong?
thanks for the reply/help.
sorry for my english

Maybe because different Android versions ? Is the Android 13 supported by this integration ?
Please ask it first on Home Assitant support.

[rooted]

Tested vulkan backend on retroarch and am able to do 4x scaling on PSX with several other heavy features enabled, quite impressive.

But something about the Bluetooth built into WiFi Module 5BK doesn't like the PS4 controller much, the range is like 1.5m and this is with WiFi disabled.

I have an old long range CSR dongle but it doesn't work on this ROM.

[voodik]

Tested vulkan backend on retroarch and am able to do 4x scaling on PSX with several other heavy features enabled, quite impressive.

But something about the Bluetooth built into WiFi Module 5BK doesn't like the PS4 controller much, the range is like 1.5m and this is with WiFi disabled.

I have an old long range CSR dongle but it doesn't work on this ROM.

Did you enable Realtek/Csr Bluetooth module fixes from Odroid Settings ?
Don't enable both. Csr for Csr, Realtek for Realtek. Reboot required.

[rooted]

I'll try it again but I'm relatively sure I tried the fix.

[voodik]

I'll try it again but I'm relatively sure I tried the fix.

And don't forget about this
https://www.bluetoothandusb3.com/the-explanation

[rooted]

I'll try it again but I'm relatively sure I tried the fix.

And don't forget about this
https://www.bluetoothandusb3.com/the-explanation

Yeah I think the range issue is potentially USB3 interference. The CSR dongle won't work regardless of what I do but that's okay.

I may have an OTG for micro USB but if I do I'm not sure where

[voodik]

I'll try it again but I'm relatively sure I tried the fix.

And don't forget about this
https://www.bluetoothandusb3.com/the-explanation

Yeah I think the range issue is potentially USB3 interference. The CSR dongle won't work regardless of what I do but that's okay.

I may have an OTG for micro USB but if I do I'm not sure where

if CSR is oldest one, Without BLE support it does not work.

But this one with CSR8510 should work (China clones also doesn't work)
https://www.hardkernel.com/shop/bluetooth-module-2/

[오그라든다]

Where is the power off menu?

[voodik]

Where is the power off menu?

Here))

poweroff.png (90.25 KiB) Viewed 2392 times

[rooted]

I'll try it again but I'm relatively sure I tried the fix.

And don't forget about this
https://www.bluetoothandusb3.com/the-explanation

Yeah I think the range issue is potentially USB3 interference. The CSR dongle won't work regardless of what I do but that's okay.

I may have an OTG for micro USB but if I do I'm not sure where

if CSR is oldest one, Without BLE support it does not work.

But this one with CSR8510 should work (China clones also doesn't work)
https://www.hardkernel.com/shop/bluetooth-module-2/

Oh it's like 10 years old probably, definitely no BLE

[loznic89]

Where is the power off menu?

Here))
poweroff.png

hi @voodik in ATV version doesnt appear poweroff menu with longpress power button. its possible add this? thanks

[rooted]

I've tried everything and I can't get a PS4 controller to reconnect after rebooting, I have to re-pair it every time.

After pairing it works fine and I can turn it off and back on and it reconnects fine but after rebooting it won't.

[voodik]

Where is the power off menu?

Here))
poweroff.png

hi @voodik in ATV version doesnt appear poweroff menu with longpress power button. its possible add this? thanks

This menu not designed for Remote/Dpad usage, and unusable.
So for shutdown/reboot use Setiings>System menu.

[rooted]

Is there a log I can provide or anything to help debug the issue @voodik ?

[voodik]

Is there a log I can provide or anything to help debug the issue @voodik ?

I have a PS4 controller, i will look into this issue.

[rooted]

Is there a log I can provide or anything to help debug the issue @voodik ?

I have a PS4 controller, i will look into this issue.

Awesome

[voodik]

Is there a log I can provide or anything to help debug the issue @voodik ?

I have a PS4 controller, i will look into this issue.

Awesome

There is a Bluetooth firmware issue. The one which used in this build making this issue.
The latest firmware does not have this issue but unfortunately have issues with Android BLE stack.
Trying to understand BLE issues.

[rooted]

If you can get it worked out that would be great, if not I can deal with pairing.

I certainly appreciate you looking into it.

[voodik]

If you can get it worked out that would be great, if not I can deal with pairing.

I certainly appreciate you looking into it.

Can you test ?
https://drive.google.com/file/d/1ZGwT6A ... sp=sharing

[rooted]

If you can get it worked out that would be great, if not I can deal with pairing.

I certainly appreciate you looking into it.

Can you test ?
https://drive.google.com/file/d/1ZGwT6A ... sp=sharing

You fixed it, I don't know how you do it but I'm thankful we have you around.

Thank you.

[voodik]

If you can get it worked out that would be great, if not I can deal with pairing.

I certainly appreciate you looking into it.

Can you test ?
https://drive.google.com/file/d/1ZGwT6A ... sp=sharing

You fixed it, I don't know how you do it but I'm thankful we have you around.

Thank you.

Just firmware issue. Updated to latest one, create Bluetooth service fixes for new firmware behavior.
I wrote above about BLE issues with new firmware but it not firmware related issue.
Almost all USB Bluetooth devices have limitation. Some of BLE features can't work simultaneously.
e.g. BLE advertising with BLE direct connection. In case with ATV we have always active BLE advertising (Android TV remote service).
This service for Android remote app. So if someone want to connect other BLE device (e.g. Mouse) he first need to disable Android TV remote service.

[rooted]

It wouldn't have taken me so long to test but I'm out of room after copying all my game ROMs.

Is the partition layout in such a way I can image this 16GB eMMC, flash to 32GB, then resize? I'm guessing yes since it gets resized automatically after flashing.

[voodik]

It wouldn't have taken me so long to test but I'm out of room after copying all my game ROMs.

Is the partition layout in such a way I can image this 16GB eMMC, flash to 32GB, then resize? I'm guessing yes since it gets resized automatically after flashing.

Not automatically, but i provide you special update.zip which do it.

[rooted]

I meant manually but a update ZIP would be great.

[오그라든다]

Where is it?You can't find it on my monitor

[voodik]

Where is it?You can't find it on my monitor

https://drive.google.com/file/d/1kZEOyR ... sp=sharing

[오그라든다]

Why can't I see it?

[voodik]

Why can't I see it?

Your screenshot is from Settings. My video is Status Bar/Notification panel. Swipe from status bar down.

[오그라든다]

I monitored it in the same setting environment Is this ATV Lineageos?

[오그라든다]

I monitored it in the same setting environment Is this ATV Lineageos?

[voodik]

I monitored it in the same setting environment Is this ATV Lineageos?

Sorry, i don't understand what you mean. Just wait for tomorrow Hardkernel team translate and show you where is the Power menu.

[오그라든다]

There's an error when booting up Android 20 for the first time, so I have to disable display activation after execution to get it working normally, is there any other way?

[오그라든다]

N2+ does not connect to Bluetooth Is there a way to connect?

[voodik]

N2+ does not connect to Bluetooth Is there a way to connect?

Deselect Odroid Settings > Misc Settings > Disable Bluetooth Services

[오그라든다]

It's set up I can't find the Bluetooth device

[voodik]

It's set up I can't find the Bluetooth device

What USB Bluetooth module you use ?

[voodik]

Update

Code: Select all

20230922 Alpha-v0.3
* Android: fixed video playback in Webview.
* Android: fixed Wifi priority high option
* Android: fixed Odroid Settings set GPU governor
* Android: Bluetooth: update RTL8821 Bluetooth firmware
* Android: fix ATV Settings text color issues.
* Android: ATV: map Home key long press to launch assistant
* Android: ATV: change default density to 320
* Android: Audio: Implement multi device support per Strategy/Source
* Lineage merge with upstream(Security patch 2023-09-05)
* minor cleanup/fixes

[rooted]

So far so good on the latest build.

WiFi/LAN working (still no WPA3 but we discussed this already), PS4 controller reconnecting after rebooting, WoL working, Vulkan performing nicely.

[voodik]

So for now I treat this build as almost stable. So I changing my vector to other boards (M1/XU3).
You can continue report bugs but i will return to them after release new builds for other boards.

[rooted]

Sounds good, I may be able to do some M1 testing as well.

[zyssai]

Do you plan to fix petitboot issue or is it petitboot related?

it fixed since
viewtopic.php?p=374147#p374147

Hi voodik.

Unfortunately even with alpha 0.3 I cannot flash using petitboot. Stuck with HK logo.

[voodik]

Do you plan to fix petitboot issue or is it petitboot related?

it fixed since
viewtopic.php?p=374147#p374147

Hi voodik.

Unfortunately even with alpha 0.3 I cannot flash using petitboot. Stuck with HK logo.

Flash ? do you mean selfinstall process ? Can you try it without petitboot?

[zyssai]

Do you plan to fix petitboot issue or is it petitboot related?

it fixed since
viewtopic.php?p=374147#p374147

Hi voodik.

Unfortunately even with alpha 0.3 I cannot flash using petitboot. Stuck with HK logo.

Flash ? do you mean selfinstall process ? Can you try it without petitboot?

Yes selfinstall, I have no EMMC reader so my only way to flash is with petitboot using command ums /dev/mmcblk0 and connect with micro-usb to computer.

[voodik]

Do you plan to fix petitboot issue or is it petitboot related?

it fixed since
viewtopic.php?p=374147#p374147

Hi voodik.

Unfortunately even with alpha 0.3 I cannot flash using petitboot. Stuck with HK logo.

Flash ? do you mean selfinstall process ? Can you try it without petitboot?

Yes selfinstall, I have no EMMC reader so my only way to flash is with petitboot using command ums /dev/mmcblk0 and connect with micro-usb to computer.

I will try this method.
BTW did you try this ?
viewtopic.php?p=374263#p374263

[zyssai]

Yes selfinstall, I have no EMMC reader so my only way to flash is with petitboot using command ums /dev/mmcblk0 and connect with micro-usb to computer.

I will try this method.
BTW did you try this ?
viewtopic.php?p=374263#p374263

Will do it in the worst case. Thanks voodik

[zyssai]

BTW did you try this ?
viewtopic.php?p=374263#p374263

I'd just give a try, ubuntu to SD card, started with petitboot, downloaded alpha 0.3, and uploaded to EMMC with dd as you suggested, and I have same behavior, stuck to HK logo with blue light kept on.

[rooted]

There is still one outstanding bug I forgot about, I can't turn off my TV.

When I have the N2+ as the current device input on the TV and turn off the TV CEC on the N2+ keeps turning it back on. I have to switch inputs then turn the TV off.

TV is Samsung.

[loznic89]

There is still one outstanding bug I forgot about, I can't turn off my TV.

When I have the N2+ as the current device input on the TV and turn off the TV CEC on the N2+ keeps turning it back on. I have to switch inputs then turn the TV off.

TV is Samsung.

viewtopic.php?p=374720#p374720

[오그라든다]

I'm using the Wi-Fi of the hard kernel

Bluetooth settings don't seem to be a problem, but I can't connect