[ROM][LineageOS 19.1][Android 12.1][voodik] for the ODROID-N2

[zyssai]

From env.ini.template

Code: Select all

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Enable backlight_pwm
; example)
; overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight"

So try

Code: Select all

overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight display_vu7c"

Unfortunately vu7c brightness not work with last update, I tried different configurations, but no reaction from screen.

[voodik]

@voodik - Thanks for your hard work !
I enjoy Alpha-v0.3 but I've been waiting for this fix - " Android: Media: fix some Videos not playing in Webview."

Is there OTA file available to upgrade from 0.3 to 0.4 ?

Odroid Settings > Update > Online

[voodik]

From env.ini.template

Code: Select all

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Enable backlight_pwm
; example)
; overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight"

So try

Code: Select all

overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight display_vu7c"

Unfortunately vu7c brightness not work with last update, I tried different configurations, but no reaction from screen.

Oh, found, permission issue

Put at end of /odm/etc/ueventd.rc

Code: Select all

/sys/class/backlight/backlight brightness     0666 system system

Overlay can be default for vu7c

Code: Select all

overlays="i2c0 i2c1 spi0 pwm_cd pwm_ef display_vu7c"

[zyssai]

From env.ini.template

Code: Select all

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Enable backlight_pwm
; example)
; overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight"

So try

Code: Select all

overlays="i2c0 i2c1 spi0 uart0 pwm_cd pwm_ef pwm_backlight display_vu7c"

Unfortunately vu7c brightness not work with last update, I tried different configurations, but no reaction from screen.

Oh, found, permission issue

Put at end of /odm/etc/ueventd.rc

Code: Select all

/sys/class/backlight/backlight brightness     0666 system system

Overlay can be default for vu7c

Code: Select all

overlays="i2c0 i2c1 spi0 pwm_cd pwm_ef display_vu7c"

It works!
Thanks voodik

[jupiter95]

Is there any way to redirect audio to Bluetooth audio output device instead of HDMI? Unlike in Odroid origin Android In this Android version various Bluetooth dongles are well detected and working.

[voodik]

Is there any way to redirect audio to Bluetooth audio output device instead of HDMI? Unlike in Odroid origin Android In this Android version various Bluetooth dongles are well detected and working.

If you connect to Bluetooth A2DP Sink device (Speaker, Headphone) audio automatically routed to Bluetooth device.

p.s.
Handsfree not supported.
p.s.p.s
Bluetooth Sink profile from Odroid Settings> Misc page should be disabled when you use Odroid as A2DP Source.

[jupiter95]

Unfortunately this feature "If you connect to Bluetooth A2DP Sink device (Speaker, Headphone) audio automatically routed to Bluetooth device." - does not work in my OndroidN2

I am using ver 0.4
Audio headset connected and visible in Connected Devices, In Odroid Settings> Misc page: Disable Bluetooth service - OFF, Enable Bluetooth Sink profile- ON

Is there anything I can check on my end? Can anyone verify if audio automatically routed to Bluetooth device?

[voodik]

Unfortunately this feature "If you connect to Bluetooth A2DP Sink device (Speaker, Headphone) audio automatically routed to Bluetooth device." - does not work in my OndroidN2

I am using ver 0.4
Audio headset connected and visible in Connected Devices, In Odroid Settings> Misc page: Disable Bluetooth service - OFF, Enable Bluetooth Sink profile- ON

Is there anything I can check on my end? Can anyone verify if audio automatically routed to Bluetooth device?

I don't understand how you want to use your Odroid as Audio Sink or Audio Source device. You want to stream music from Odroid or to Odroid ?
Just remember voice call audio is not A2DP it's Handsfree Bluetooth profile which not supported, and cannot be supported.

[jupiter95]

I just want to listen to Audio through Bluetooth headphones instead of wired headphones connected to Monitor (connected to Odroid with HDMI). Am I connecting something wrong?

[voodik]

I just want to listen to Audio through Bluetooth headphones instead of wired headphones connected to Monitor (connected to Odroid with HDMI). Am I connecting something wrong?

Set -> Enable Bluetooth Sink profile OFF
Then reboot, unpair your headphones and pair them again

[jupiter95]

@voodik - thanks a lot works fine now

[fleck]

Hi, thanks for this. I just installed the ATV version on an N2+ EMMC and have some problems straight off the bat. In the settings menu, I can't access Privacy, Display & Sound, Apps, System or Remotes & accessories; every time I click on those options it goes straight to Network & Internet. So I can't pair a remote or look at any of the other options. 18.1 works fine though.

[zench1k]

hello, is it possible to enable samba on this image for sharing content?

[philippe456]

hello, How to connect in SSH , for sending the adb commands ....

adb root
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'


thanks for help

[odrooz]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

[voodik]

hello, How to connect in SSH , for sending the adb commands ....

adb root
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'


thanks for help

https://www.xda-developers.com/install- ... cos-linux/

[philippe456]

thank you @voodik
allright, i will manage that.

And is it possible to connect via SSH ? what is login & password ?

thanks for help

[mad_ady]

Android doesn't come with a ssh server. You can install one from the playstore if you want.

[Burette]

Call for alpha test : LineageOS-19.1 Android 12 for Odroid-N2

I am trying to update my friend's N2 which is running on HK Pie9.
The install goes well but the device keeps freezing at boot at the Lineage Logo.

Is is a known behavior?
Should I regress to you LOS 18 or upgrade to 20 or do you believe the box is faulty ?

After a few reboot, I update Petitboot to the last version from the shell.

Thanks

[voodik]

Call for alpha test : LineageOS-19.1 Android 12 for Odroid-N2

I am trying to update my friend's N2 which is running on HK Pie9.
The install goes well but the device keeps freezing at boot at the Lineage Logo.

Is is a known behavior?
Should I regress to you LOS 18 or upgrade to 20 or do you believe the box is faulty ?

After a few reboot, I update Petitboot to the last version from the shell.

Thanks

You installing via Selfinstall images or update ?

[voodik]

thank you @voodik
allright, i will manage that.

And is it possible to connect via SSH ? what is login & password ?

thanks for help

You can use adb over network and modified putty with adb support.
Edit /odm/etc/build.prop and set

Code: Select all

service.adb.tcp.port=5555

Here is custom putty with adb support
https://drive.google.com/open?id=12dVPe ... p=drive_fs

Example session config:

putty.jpg (62.29 KiB) Viewed 681 times

[istanbulls]

merry christmas @voodik, christmas was yesterday but i remember you today.

[Burette]

You installing via Selfinstall images or update ?

Selfinstall of course.

I verified the MD5, it matched
I extracted the zip and used Rufus to flash the image. It booted, I took care of the Android GSF, it never rebooted.

Then I flashed the zip directly with Balena. It booted, I took care of the Android GSF, it never rebooted.

Then, even if the MD5 was ok, I redownloaded the zip, flashed with Etcher...

Then, as a last resort, I flashed over USB OTG. same result.

I had no problem on my own C4 so that's why I am curious for the N2.

[voodik]

You installing via Selfinstall images or update ?

Selfinstall of course.

I verified the MD5, it matched
I extracted the zip and used Rufus to flash the image. It booted, I took care of the Android GSF, it never rebooted.

Then I flashed the zip directly with Balena. It booted, I took care of the Android GSF, it never rebooted.

Then, even if the MD5 was ok, I redownloaded the zip, flashed with Etcher...

Then, as a last resort, I flashed over USB OTG. same result.

I had no problem on my own C4 so that's why I am curious for the N2.

Setup adb and dump logs

Code: Select all

adb shell
setprop persist.logd.size 8388608
reboot
adb shell
logcat -d > /data/logcat.txt
dmesg > /data/dmesg.txt
exit
adb pull /data/logcat.txt
adb pull /data/dmesg.txt

[odrooz]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

[voodik]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

There was a lot of issues in google about Bluetooth connectivity of this controller. Is it work via USB connection ?
Are you try pair it in windows with same USB Bluetooth dongle then connect to Odroid ?

[voodik]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

BTW, after some research.

This controllers can work via Bluetooth only with custom kernel module called xpadneo
https://atar-axis.github.io/xpadneo

Here is a Lineage-19.1 ATV build with xpadneo driver backport
https://drive.google.com/file/d/1Krx9Yt ... share_link

How to update from downloaded package
https://youtu.be/QwJNYuDVat4

Also read the troubleshooting of this driver (Gamepad Does not Connect at All, Runs A Reconnect Loop, or Immediately Disconnects)
https://atar-axis.github.io/xpadneo/#troubleshooting

To disable ERTM edit /odm/env.ini and change extra_boot_args line as

Code: Select all

extra_boot_args="bluetooth.disable_ertm"

[odrooz]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

BTW, after some research.

This controllers can work via Bluetooth only with custom kernel module called xpadneo
https://atar-axis.github.io/xpadneo

Here is a Lineage-19.1 ATV build with xpadneo driver backport
https://drive.google.com/file/d/1Krx9Yt ... share_link

How to update from downloaded package
https://youtu.be/QwJNYuDVat4

Also read the troubleshooting of this driver (Gamepad Does not Connect at All, Runs A Reconnect Loop, or Immediately Disconnects)
https://atar-axis.github.io/xpadneo/#troubleshooting

To disable ERTM edit /odm/env.ini and change extra_boot_args line as

Code: Select all

extra_boot_args="bluetooth.disable_ertm"

Thank you for the invaluable information on that sir, I don't think I would have been able to find the connection between the two modules but disabling ERTM alone fixed the issue and I'm able to pair / unpair successfully the Xbox controller. If you are wondering, I didn't have to rebuild the kernel or include xpadneo in anything because the kernel apparently is using a different module that supports the controller natively.

I'll definitely be "buying you a beer" once I have a minute to do so.

In regards to the ATV remote, allow me to explain what controller I'm attempting to connect since disabling ERTM didn't seem to correct the issue with this one. The remote I'm attempting to connect is the Fios TV remote (https://www.verizon.com/support/residen ... ice-remote). The controller itself is able to pair with my Android handset running DrKeatons ROM on a Galaxy Note10+, I also have several Linux laptops in my home that I use the same Bluetooth adapter on that is able to pair successfully with. I'm attempting to use this remote as a standard ATV remote (hoping for the voice feature, but not real sure it will even work). None the less, it should still be able to pair and aside from the possibility of the voice feature working, all the buttons when paired with my Android handset work just fine.

When using my Fedora Linux laptop, dmesg shows the below information upon successfully pairing the remote

Code: Select all

[478028.208822] Bluetooth: hci1: Bootloader revision 0.4 build 0 week 30 2018
[478028.209826] Bluetooth: hci1: Device revision is 2
[478028.209829] Bluetooth: hci1: Secure boot is enabled
[478028.209830] Bluetooth: hci1: OTP lock is enabled
[478028.209831] Bluetooth: hci1: API lock is enabled
[478028.209831] Bluetooth: hci1: Debug lock is disabled
[478028.209832] Bluetooth: hci1: Minimum firmware build 1 week 10 2014
[478028.253737] Bluetooth: hci1: Found device firmware: intel/ibt-19-0-4.sfi
[478028.253849] Bluetooth: hci1: Boot Address: 0x24800
[478028.253852] Bluetooth: hci1: Firmware Version: 106-39.22
[478030.081092] Bluetooth: hci1: Waiting for firmware download to complete
[478030.081800] Bluetooth: hci1: Firmware loaded in 1785213 usecs
[478030.081863] Bluetooth: hci1: Waiting for device to boot
[478030.096862] Bluetooth: hci1: Device booted in 14675 usecs
[478030.096866] Bluetooth: hci1: Malformed MSFT vendor event: 0x02
[478030.097252] Bluetooth: hci1: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[478030.098806] Bluetooth: hci1: Applying Intel DDC parameters completed
[478030.099822] Bluetooth: hci1: Firmware revision 0.4 build 106 week 39 2022
[478030.165052] Bluetooth: MGMT ver 1.22
[478070.253909] Bluetooth: hci0: unexpected SMP command 0x0b from 30:f9:xx:a5:xx:7b
[478072.731707] input: VRC4100 Keyboard as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input52
[478072.731885] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input53
[478072.731996] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input54
[478072.732080] hid-generic 0005:06E7:8096.001D: input,hidraw10: BLUETOOTH HID v1.10 Keyboard [VRC4100]

Is there any information you'd be able to digest from the pairing attempt I made with Linux that can be used to get the LineageOS pair to work? If there's somewhere I can get more detail on the LineageOS attempt you'll have to let me know, dmesg basically shows nothing on that attempt, the UI only displays "Couldn't pair". Am I possibility missing the firmware? I don't think the voice feature is going to work with this remote, however my fear is that I might be running into the same issue in my quest to try other voice remotes..

Thanks again

[voodik]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

BTW, after some research.

This controllers can work via Bluetooth only with custom kernel module called xpadneo
https://atar-axis.github.io/xpadneo

Here is a Lineage-19.1 ATV build with xpadneo driver backport
https://drive.google.com/file/d/1Krx9Yt ... share_link

How to update from downloaded package
https://youtu.be/QwJNYuDVat4

Also read the troubleshooting of this driver (Gamepad Does not Connect at All, Runs A Reconnect Loop, or Immediately Disconnects)
https://atar-axis.github.io/xpadneo/#troubleshooting

To disable ERTM edit /odm/env.ini and change extra_boot_args line as

Code: Select all

extra_boot_args="bluetooth.disable_ertm"

Thank you for the invaluable information on that sir, I don't think I would have been able to find the connection between the two modules but disabling ERTM alone fixed the issue and I'm able to pair / unpair successfully the Xbox controller. If you are wondering, I didn't have to rebuild the kernel or include xpadneo in anything because the kernel apparently is using a different module that supports the controller natively.

I'll definitely be "buying you a beer" once I have a minute to do so.

In regards to the ATV remote, allow me to explain what controller I'm attempting to connect since disabling ERTM didn't seem to correct the issue with this one. The remote I'm attempting to connect is the Fios TV remote (https://www.verizon.com/support/residen ... ice-remote). The controller itself is able to pair with my Android handset running DrKeatons ROM on a Galaxy Note10+, I also have several Linux laptops in my home that I use the same Bluetooth adapter on that is able to pair successfully with. I'm attempting to use this remote as a standard ATV remote (hoping for the voice feature, but not real sure it will even work). None the less, it should still be able to pair and aside from the possibility of the voice feature working, all the buttons when paired with my Android handset work just fine.

When using my Fedora Linux laptop, dmesg shows the below information upon successfully pairing the remote

Code: Select all

[478028.208822] Bluetooth: hci1: Bootloader revision 0.4 build 0 week 30 2018
[478028.209826] Bluetooth: hci1: Device revision is 2
[478028.209829] Bluetooth: hci1: Secure boot is enabled
[478028.209830] Bluetooth: hci1: OTP lock is enabled
[478028.209831] Bluetooth: hci1: API lock is enabled
[478028.209831] Bluetooth: hci1: Debug lock is disabled
[478028.209832] Bluetooth: hci1: Minimum firmware build 1 week 10 2014
[478028.253737] Bluetooth: hci1: Found device firmware: intel/ibt-19-0-4.sfi
[478028.253849] Bluetooth: hci1: Boot Address: 0x24800
[478028.253852] Bluetooth: hci1: Firmware Version: 106-39.22
[478030.081092] Bluetooth: hci1: Waiting for firmware download to complete
[478030.081800] Bluetooth: hci1: Firmware loaded in 1785213 usecs
[478030.081863] Bluetooth: hci1: Waiting for device to boot
[478030.096862] Bluetooth: hci1: Device booted in 14675 usecs
[478030.096866] Bluetooth: hci1: Malformed MSFT vendor event: 0x02
[478030.097252] Bluetooth: hci1: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[478030.098806] Bluetooth: hci1: Applying Intel DDC parameters completed
[478030.099822] Bluetooth: hci1: Firmware revision 0.4 build 106 week 39 2022
[478030.165052] Bluetooth: MGMT ver 1.22
[478070.253909] Bluetooth: hci0: unexpected SMP command 0x0b from 30:f9:xx:a5:xx:7b
[478072.731707] input: VRC4100 Keyboard as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input52
[478072.731885] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input53
[478072.731996] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input54
[478072.732080] hid-generic 0005:06E7:8096.001D: input,hidraw10: BLUETOOTH HID v1.10 Keyboard [VRC4100]

Is there any information you'd be able to digest from the pairing attempt I made with Linux that can be used to get the LineageOS pair to work? If there's somewhere I can get more detail on the LineageOS attempt you'll have to let me know, dmesg basically shows nothing on that attempt, the UI only displays "Couldn't pair". Am I possibility missing the firmware? I don't think the voice feature is going to work with this remote, however my fear is that I might be running into the same issue in my quest to try other voice remotes..

Thanks again

Voice over Bluetooth is not working with USB Bluetooth dongles and Android Bluetooth stack.
Bluetooth Handsfree Protocol is not supported at all. So don't spend your time and resources.
In case why input device couldn't pair dump logs maybe i can find something there.

Code: Select all

adb shell
setprop persist.logd.size 8388608
reboot
adb shell
logcat -d > /data/logcat.txt
dmesg > /data/dmesg.txt
exit
adb pull /data/logcat.txt
adb pull /data/dmesg.txt

Also enable Bluetooth HCI snoop logging and dump it after pairing attempt.

Code: Select all

adb pull /data/misc/bluetooth/logs/btsnoop_hci.log

[odrooz]

@voodik

hi, using the latest ATV release of 12 I've been having issues pairing a couple of Bluetooth devices that I have, one being a Android TV remote and another a Xbox series X controller.

Code: Select all

[323191.450268] 323191.450268@3] Bluetooth: hci0: BCM: chip id 73
[323191.467268] 323191.467268@2] Bluetooth: hci0: BCM20702B
[323191.468242] 323191.468242@2] Bluetooth: hci0: BCM20702B0 (002.001.014) build 0000

I experienced the same thing running Lineageos on the Nintendo switch so I expected maybe it being a universal issue because I'm able to get the devices properly paired on other computers I own. When I go through the process of trying to pair the devices, the UI simply indicates "Couldn't pair" and no matter what combination or code I use doesn't work. Any advice you can provide?

Thanks

Hi @voodik any other information I can provide to troubleshoot the above issue?

Thanks in advance

BTW, after some research.

This controllers can work via Bluetooth only with custom kernel module called xpadneo
https://atar-axis.github.io/xpadneo

Here is a Lineage-19.1 ATV build with xpadneo driver backport
https://drive.google.com/file/d/1Krx9Yt ... share_link

How to update from downloaded package
https://youtu.be/QwJNYuDVat4

Also read the troubleshooting of this driver (Gamepad Does not Connect at All, Runs A Reconnect Loop, or Immediately Disconnects)
https://atar-axis.github.io/xpadneo/#troubleshooting

To disable ERTM edit /odm/env.ini and change extra_boot_args line as

Code: Select all

extra_boot_args="bluetooth.disable_ertm"

Thank you for the invaluable information on that sir, I don't think I would have been able to find the connection between the two modules but disabling ERTM alone fixed the issue and I'm able to pair / unpair successfully the Xbox controller. If you are wondering, I didn't have to rebuild the kernel or include xpadneo in anything because the kernel apparently is using a different module that supports the controller natively.

I'll definitely be "buying you a beer" once I have a minute to do so.

In regards to the ATV remote, allow me to explain what controller I'm attempting to connect since disabling ERTM didn't seem to correct the issue with this one. The remote I'm attempting to connect is the Fios TV remote (https://www.verizon.com/support/residen ... ice-remote). The controller itself is able to pair with my Android handset running DrKeatons ROM on a Galaxy Note10+, I also have several Linux laptops in my home that I use the same Bluetooth adapter on that is able to pair successfully with. I'm attempting to use this remote as a standard ATV remote (hoping for the voice feature, but not real sure it will even work). None the less, it should still be able to pair and aside from the possibility of the voice feature working, all the buttons when paired with my Android handset work just fine.

When using my Fedora Linux laptop, dmesg shows the below information upon successfully pairing the remote

Code: Select all

[478028.208822] Bluetooth: hci1: Bootloader revision 0.4 build 0 week 30 2018
[478028.209826] Bluetooth: hci1: Device revision is 2
[478028.209829] Bluetooth: hci1: Secure boot is enabled
[478028.209830] Bluetooth: hci1: OTP lock is enabled
[478028.209831] Bluetooth: hci1: API lock is enabled
[478028.209831] Bluetooth: hci1: Debug lock is disabled
[478028.209832] Bluetooth: hci1: Minimum firmware build 1 week 10 2014
[478028.253737] Bluetooth: hci1: Found device firmware: intel/ibt-19-0-4.sfi
[478028.253849] Bluetooth: hci1: Boot Address: 0x24800
[478028.253852] Bluetooth: hci1: Firmware Version: 106-39.22
[478030.081092] Bluetooth: hci1: Waiting for firmware download to complete
[478030.081800] Bluetooth: hci1: Firmware loaded in 1785213 usecs
[478030.081863] Bluetooth: hci1: Waiting for device to boot
[478030.096862] Bluetooth: hci1: Device booted in 14675 usecs
[478030.096866] Bluetooth: hci1: Malformed MSFT vendor event: 0x02
[478030.097252] Bluetooth: hci1: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[478030.098806] Bluetooth: hci1: Applying Intel DDC parameters completed
[478030.099822] Bluetooth: hci1: Firmware revision 0.4 build 106 week 39 2022
[478030.165052] Bluetooth: MGMT ver 1.22
[478070.253909] Bluetooth: hci0: unexpected SMP command 0x0b from 30:f9:xx:a5:xx:7b
[478072.731707] input: VRC4100 Keyboard as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input52
[478072.731885] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input53
[478072.731996] input: VRC4100 as /devices/virtual/misc/uhid/0005:06E7:8096.001D/input/input54
[478072.732080] hid-generic 0005:06E7:8096.001D: input,hidraw10: BLUETOOTH HID v1.10 Keyboard [VRC4100]

Is there any information you'd be able to digest from the pairing attempt I made with Linux that can be used to get the LineageOS pair to work? If there's somewhere I can get more detail on the LineageOS attempt you'll have to let me know, dmesg basically shows nothing on that attempt, the UI only displays "Couldn't pair". Am I possibility missing the firmware? I don't think the voice feature is going to work with this remote, however my fear is that I might be running into the same issue in my quest to try other voice remotes..

Thanks again

Voice over Bluetooth is not working with USB Bluetooth dongles and Android Bluetooth stack.
Bluetooth Handsfree Protocol is not supported at all. So don't spend your time and resources.
In case why input device couldn't pair dump logs maybe i can find something there.

Code: Select all

adb shell
setprop persist.logd.size 8388608
reboot
adb shell
logcat -d > /data/logcat.txt
dmesg > /data/dmesg.txt
exit
adb pull /data/logcat.txt
adb pull /data/dmesg.txt

Also enable Bluetooth HCI snoop logging and dump it after pairing attempt.

Code: Select all

adb pull /data/misc/bluetooth/logs/btsnoop_hci.log

Thanks for that, I'll try to get some more details.

That's a bummer about the USB bluetooth stack, is that something beyond our control being able to fix in a ROM? That's sort of been a dream of mine ever since I got the ODroid with a custom ROM on it..

[voodik]

Update

Code: Select all

20230112 Alpha-v0.5
* Android: Input: implement mouse wheel pinch to zoom
* Android: Bluetooth: add option to enable fixes for CSR dongles
* Android: UI: add option to disable "Tablet is starting" message on boot
* Kernel: port HID-XPADNEO driver (Advanced Linux Driver for Xbox One Wireless Controller)
* Kernel: backport HID-PLAYSTATION (HID driver for Sony DualSense/DS4  controller)
* Kernel: update RTLBT driver (supports more Realtek Bluetooth dongles)
* Kernel: add dispay_vu7c_no_dai overlay (remove DAI for display)
* Android: Recovery: fixed Magisk install error
* Merge latest BSP changes
* Lineage merge with upstream

[odrooz]

Update

Code: Select all

20230112 Alpha-v0.5
* Android: Input: implement mouse wheel pinch to zoom
* Android: Bluetooth: add option to enable fixes for CSR dongles
* Android: UI: add option to disable "Tablet is starting" message on boot
* Kernel: port HID-XPADNEO driver (Advanced Linux Driver for Xbox One Wireless Controller)
* Kernel: backport HID-PLAYSTATION (HID driver for Sony DualSense/DS4  controller)
* Kernel: update RTLBT driver (supports more Realtek Bluetooth dongles)
* Kernel: add dispay_vu7c_no_dai overlay (remove DAI for display)
* Android: Recovery: fixed Magisk install error
* Merge latest BSP changes
* Lineage merge with upstream

@voodik thanks. I can confirm that the Xbox controllers I have work perfect after the update. I haven't gotten around to getting the info for the ATV remote yet, I'm thinking of trying a different one for reasons outside the scope of any of this.

I recently just purchased a new Bluetooth dongle in hopes to improve the connectivity of some of my devices, turns out that Lineageos doesn't appear to have either the driver or firmware included in the image. I found that the chipset is a Realtek RTL8761bu


Is there anyway I can load the driver for this on the Odroid or is there something I'm missing?

[voodik]

Update

Code: Select all

20230112 Alpha-v0.5
* Android: Input: implement mouse wheel pinch to zoom
* Android: Bluetooth: add option to enable fixes for CSR dongles
* Android: UI: add option to disable "Tablet is starting" message on boot
* Kernel: port HID-XPADNEO driver (Advanced Linux Driver for Xbox One Wireless Controller)
* Kernel: backport HID-PLAYSTATION (HID driver for Sony DualSense/DS4  controller)
* Kernel: update RTLBT driver (supports more Realtek Bluetooth dongles)
* Kernel: add dispay_vu7c_no_dai overlay (remove DAI for display)
* Android: Recovery: fixed Magisk install error
* Merge latest BSP changes
* Lineage merge with upstream

@voodik thanks. I can confirm that the Xbox controllers I have work perfect after the update. I haven't gotten around to getting the info for the ATV remote yet, I'm thinking of trying a different one for reasons outside the scope of any of this.

I recently just purchased a new Bluetooth dongle in hopes to improve the connectivity of some of my devices, turns out that Lineageos doesn't appear to have either the driver or firmware included in the image. I found that the chipset is a Realtek RTL8761bu


Is there anyway I can load the driver for this on the Odroid or is there something I'm missing?

You need put rtl8761bu_fw.bin and rtl8761bu_config.bin to /odm/etc/firmware/rtl_bt folder.

[odrooz]

Update

Code: Select all

20230112 Alpha-v0.5
* Android: Input: implement mouse wheel pinch to zoom
* Android: Bluetooth: add option to enable fixes for CSR dongles
* Android: UI: add option to disable "Tablet is starting" message on boot
* Kernel: port HID-XPADNEO driver (Advanced Linux Driver for Xbox One Wireless Controller)
* Kernel: backport HID-PLAYSTATION (HID driver for Sony DualSense/DS4  controller)
* Kernel: update RTLBT driver (supports more Realtek Bluetooth dongles)
* Kernel: add dispay_vu7c_no_dai overlay (remove DAI for display)
* Android: Recovery: fixed Magisk install error
* Merge latest BSP changes
* Lineage merge with upstream

@voodik thanks. I can confirm that the Xbox controllers I have work perfect after the update. I haven't gotten around to getting the info for the ATV remote yet, I'm thinking of trying a different one for reasons outside the scope of any of this.

I recently just purchased a new Bluetooth dongle in hopes to improve the connectivity of some of my devices, turns out that Lineageos doesn't appear to have either the driver or firmware included in the image. I found that the chipset is a Realtek RTL8761bu


Is there anyway I can load the driver for this on the Odroid or is there something I'm missing?

You need put rtl8761bu_fw.bin and rtl8761bu_config.bin to /odm/etc/firmware/rtl_bt folder.

Yeah I figured that, and tried it but it didn't seem to make any difference in getting it working. Is there anything else aside from that?

Code: Select all

$ ll /odm/etc/firmware/rtl_bt/
total 42
-rwxrwxrwx 1 root root     6 Jan 18 07:48 rtl8761bu_config.bin
-rwxrwxrwx 1 root root 42088 Jan 18 07:48 rtl8761bu_fw.bin

In the UI nothing shows up when trying to scan, when unplugging and plugging back in dmesg shows:

Code: Select all

[  646.279460]  646.279460@4] usb 1-1.3: Device not responding to setup address.
[  646.340452]  646.340452@5] binder: undelivered death notification, 0000006f1d14ace0
[  646.487413]  646.487413@4] usb 1-1.3: Device not responding to setup address.
[  646.695370]  646.695370@4] usb 1-1.3: device not accepting address 6, error -71
[  652.535384]  652.535384@4] usb 1-1.4: new full-speed USB device number 8 using xhci-hcd

[voodik]

Update

Code: Select all

20230112 Alpha-v0.5
* Android: Input: implement mouse wheel pinch to zoom
* Android: Bluetooth: add option to enable fixes for CSR dongles
* Android: UI: add option to disable "Tablet is starting" message on boot
* Kernel: port HID-XPADNEO driver (Advanced Linux Driver for Xbox One Wireless Controller)
* Kernel: backport HID-PLAYSTATION (HID driver for Sony DualSense/DS4  controller)
* Kernel: update RTLBT driver (supports more Realtek Bluetooth dongles)
* Kernel: add dispay_vu7c_no_dai overlay (remove DAI for display)
* Android: Recovery: fixed Magisk install error
* Merge latest BSP changes
* Lineage merge with upstream

@voodik thanks. I can confirm that the Xbox controllers I have work perfect after the update. I haven't gotten around to getting the info for the ATV remote yet, I'm thinking of trying a different one for reasons outside the scope of any of this.

I recently just purchased a new Bluetooth dongle in hopes to improve the connectivity of some of my devices, turns out that Lineageos doesn't appear to have either the driver or firmware included in the image. I found that the chipset is a Realtek RTL8761bu


Is there anyway I can load the driver for this on the Odroid or is there something I'm missing?
Are you on latest version ?
What USB vid/pid have it ?

You need put rtl8761bu_fw.bin and rtl8761bu_config.bin to /odm/etc/firmware/rtl_bt folder.

Yeah I figured that, and tried it but it didn't seem to make any difference in getting it working. Is there anything else aside from that?

Code: Select all

$ ll /odm/etc/firmware/rtl_bt/
total 42
-rwxrwxrwx 1 root root     6 Jan 18 07:48 rtl8761bu_config.bin
-rwxrwxrwx 1 root root 42088 Jan 18 07:48 rtl8761bu_fw.bin

In the UI nothing shows up when trying to scan, when unplugging and plugging back in dmesg shows:

Code: Select all

[  646.279460]  646.279460@4] usb 1-1.3: Device not responding to setup address.
[  646.340452]  646.340452@5] binder: undelivered death notification, 0000006f1d14ace0
[  646.487413]  646.487413@4] usb 1-1.3: Device not responding to setup address.
[  646.695370]  646.695370@4] usb 1-1.3: device not accepting address 6, error -71
[  652.535384]  652.535384@4] usb 1-1.4: new full-speed USB device number 8 using xhci-hcd

[odrooz]

@voodik

VID/PID = 2550:8761

I'm using the latest firmware package provided in the Linux kernel tree

https://git.kernel.org/pub/scm/linux/ke ... ree/rtl_bt

[voodik]

@voodik

VID/PID = 2550:8761

I'm using the latest firmware package provided in the Linux kernel tree

https://git.kernel.org/pub/scm/linux/ke ... ree/rtl_bt

I don't know.
This guy confirms after latest patches rtl8761bu working on 19.1
https://github.com/voodik/android_kerne ... 1363864712

You don't see this kind logs in dmesg ?

Code: Select all

[  828.135115] Bluetooth: RealTek module detected
[  828.137062] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  828.138041] Bluetooth: hci0: RTL: rom_version status=0 version=1
[  828.138051] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  828.138367] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[  828.138541] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[  828.278035] Bluetooth: hci0: RTL: fw version 0x09a98a6b

[odrooz]

@voodik

VID/PID = 2550:8761

I'm using the latest firmware package provided in the Linux kernel tree

https://git.kernel.org/pub/scm/linux/ke ... ree/rtl_bt

I don't know.
This guy confirms after latest patches rtl8761bu working on 19.1
https://github.com/voodik/android_kerne ... 1363864712

You don't see this kind logs in dmesg ?

Code: Select all

[  828.135115] Bluetooth: RealTek module detected
[  828.137062] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  828.138041] Bluetooth: hci0: RTL: rom_version status=0 version=1
[  828.138051] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  828.138367] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[  828.138541] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[  828.278035] Bluetooth: hci0: RTL: fw version 0x09a98a6b

I don't, there's nothing like that. I uploaded my dmesg here in case you want to take a look, the bluetooth stack doesn't seem to be loading the driver to me. At the very end of the dmesg you can see where I disconnect and reconnect.

See attached.

[odrooz]

@voodik so maybe I should have read the bug report you sent a bit more clearly.. according to the reporter the chipset isn't supported until the 5.x kernel, the ATV image I'm using is only 4.9. Are there any plans on building a new kernel for 19.1? I saw you built one that added the driver in maybe, is it okay to install this image over the latest update and will this include the driver?

Code: Select all

$ uname -a
Linux localhost 4.9.113 #18 SMP PREEMPT Thu Jan 12 13:48:56 +08 2023 aarch64 Android

[voodik]

@voodik so maybe I should have read the bug report you sent a bit more clearly.. according to the reporter the chipset isn't supported until the 5.x kernel, the ATV image I'm using is only 4.9. Are there any plans on building a new kernel for 19.1? I saw you built one that added the driver in maybe, is it okay to install this image over the latest update and will this include the driver?

Code: Select all

$ uname -a
Linux localhost 4.9.113 #18 SMP PREEMPT Thu Jan 12 13:48:56 +08 2023 aarch64 Android

EDIT:

Sure, it does not work because it have different than original 8761BU vid/pid.
https://patchwork.kernel.org/project/bl ... /#24704798

I wil add this VID/PID in next build.

[voodik]

Here is test ATV version
https://drive.google.com/file/d/1_6Ky7k ... share_link

[odrooz]

Here is test ATV version
https://drive.google.com/file/d/1_6Ky7k ... share_link

@voodik

Was just about to post with some new info but looks like you figured it out. Flashed the test image and tried again, everything working now. Thanks for the assistance on that sir. Tested and confirmed.