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

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

mad_ady wrote:
Thu Nov 05, 2020 10:50 pm
You may need to remount /vendor as rw
I did try that, but it said something about being unmountable. I probably did it wrong though lol. I'll look into it more, try again, and report back.

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

Okay, now I'm unable to login to Google for some reason. After fixing the SafetyNet issue and registering my GSF ID (registered almost a week ago), Netflix was still not showing up in the Google Play store, so I thought I should try logging out and logging back into my google account. That was a mistake! When I click the "Sign in" button, the spinning circle loading animation comes up for a couple seconds then just disappears without showing the login form. I tried through Settings-->Accounts&Sign-in as well as through the Google Play store, but get the same behavior. Anyone know how to fix this? I tried rebooting the system a couple times. Also, FYI, in Google Play settings it does say "Device is Certified" under Play Protection Certification.

Edit: I rolled back my fix for the SafetyNet failures hoping that would do the trick, but no luck. :( The rollback entailed reseting my the device fingerprint back to default value via the MagiskHide Props Config module terminal command, then uninstalling the module from Magisk, and rebooting.

Edit #2: Okay, I fixed it. I had to go into Settings-->Apps, and delete Cache and Data for Google Play Services. Still no Netflix in the Play store. Oh well. At least I can get into it again.

Here's a 25 second gif/video of what was happening...
Image
These users thanked the author jd637 for the post:
odroid (Fri Nov 06, 2020 9:29 am)

Peto
Posts: 5
Joined: Mon Jan 27, 2020 5:24 am
languages_spoken: French
ODROIDs: Odroid N2
Has thanked: 0
Been thanked: 0
Contact:

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

Post by Peto »

Is it possible to install Netflix, Disney + and Amazon Prime Video on this version of Android?

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

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

Post by voodik »

Peto wrote:
Sun Nov 08, 2020 8:59 pm
Is it possible to install Netflix, Disney + and Amazon Prime Video on this version of Android?
No, ATV version of this apps requires Widevine DRM. Which isn't available on SBC's.
Last edited by voodik on Sun Nov 08, 2020 9:25 pm, edited 1 time in total.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

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

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

Post by voodik »

jd637 wrote:
Thu Nov 05, 2020 11:06 pm
Okay, now I'm unable to login to Google for some reason. After fixing the SafetyNet issue and registering my GSF ID (registered almost a week ago), Netflix was still not showing up in the Google Play store, so I thought I should try logging out and logging back into my google account. That was a mistake! When I click the "Sign in" button, the spinning circle loading animation comes up for a couple seconds then just disappears without showing the login form. I tried through Settings-->Accounts&Sign-in as well as through the Google Play store, but get the same behavior. Anyone know how to fix this? I tried rebooting the system a couple times. Also, FYI, in Google Play settings it does say "Device is Certified" under Play Protection Certification.

Edit: I rolled back my fix for the SafetyNet failures hoping that would do the trick, but no luck. :( The rollback entailed reseting my the device fingerprint back to default value via the MagiskHide Props Config module terminal command, then uninstalling the module from Magisk, and rebooting.

Edit #2: Okay, I fixed it. I had to go into Settings-->Apps, and delete Cache and Data for Google Play Services. Still no Netflix in the Play store. Oh well. At least I can get into it again.

Here's a 25 second gif/video of what was happening...
Image
ATV version of Netflix requires Widevine DRM. Which isn't available on SBC's.
These users thanked the author voodik for the post:
jd637 (Tue Nov 10, 2020 6:51 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

Peto
Posts: 5
Joined: Mon Jan 27, 2020 5:24 am
languages_spoken: French
ODROIDs: Odroid N2
Has thanked: 0
Been thanked: 0
Contact:

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

Post by Peto »

what's the point of installing android tv then...

Peto
Posts: 5
Joined: Mon Jan 27, 2020 5:24 am
languages_spoken: French
ODROIDs: Odroid N2
Has thanked: 0
Been thanked: 0
Contact:

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

Post by Peto »

Widevine DRM works on Coreelec/Kodi on the same SBC's

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Sun Nov 08, 2020 9:21 pm
ATV version of Netflix requires Widevine DRM. Which isn't available on SBC's.
Oh, okay. Thanks for the heads up! Glad to know it's not me. :D

Peto wrote:
Sun Nov 08, 2020 10:18 pm
what's the point of installing android tv then...
For me personally, GeForce NOW.
These users thanked the author jd637 for the post:
istanbulls (Wed Nov 11, 2020 2:06 am)

User avatar
istanbulls
Posts: 446
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID; N2, C4, XU4, N2+, CH4
Location: Istanbul-Turkey
Has thanked: 278 times
Been thanked: 65 times
Contact:

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

Post by istanbulls »

jd637 wrote:
Tue Nov 10, 2020 6:51 pm
voodik wrote:
Sun Nov 08, 2020 9:21 pm
ATV version of Netflix requires Widevine DRM. Which isn't available on SBC's.
Oh, okay. Thanks for the heads up! Glad to know it's not me. :D

Peto wrote:
Sun Nov 08, 2020 10:18 pm
what's the point of installing android tv then...
For me personally, GeForce NOW.
How is GeForce NOW performance?
Could you make a video about GeForce NOW. :)

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

istanbulls wrote:
Wed Nov 11, 2020 2:06 am
How is GeForce NOW performance?
Could you make a video about GeForce NOW. :)
I'm not much of a content creator, nor am I very experienced with cloud gaming, so I probably wouldn't be the best choice to make a video about it. :) But I can tell you that I have been very happy with the performance of GFN on the N2+ w/ LineageOS so far. I haven't notice any difference versus running GFN on my MacBook Pro 2017 (2.9 GHz Quad-Core Intel Core i7, Radeon Pro 560). I do have pretty good internet (80 Mbps), which I understand is the most important factor for cloud gaming. But yeah, the N2+ seems to handle GFN just fine. I like to play games while sitting on my couch, and didn't like having to hook up my work laptop to my TV via HDMI every time I wanted to play a game, so it's great to have a quiet little low-power SBC that can run GFN always hooked up and ready to play.

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

Has anyone had luck getting an XBOX 360 controller with the wireless USB adapter working? It works partially, but the right-stick input is all over the place. If I'm in a first-person-shooter game, the camera just spins all around. The mapping of other buttons are off as well. I've confirmed that the controller and adapter work fine in multiple other devices/computers. I believe it's related to this issue posted on XDA: https://forum.xda-developers.com/showpo ... stcount=12

The person recommended this fix:
Firstly you need to run dmesg and look for the line:
<6>[ 1489.104652] usb 2-1: New USB device found, idVendor=045e, idProduct=0291

Taken from http://forum.xda-developers.com/show....php?t=1418263:

Open up a terminal emulator and run the following (building the new filename from the idVendor and idProduct)

su
cd /system/usr/keylayout/
mount -o remount,rw /system
cp Vendor_045e_Product_028e.kl Vendor_045e_Product_0291.kl

Reboot for the change to take into effect and both gta3 and shadowgun worked brilliantly. I had to assign some controls from within the shadowgun game to my preference and I can't be happier. I am running teamEOS ics ROM but this should work for honeycomb.
I do see some "Vendor_045e_..." files in /system/usr/keylayout:

Code: Select all

...
-rw-r--r-- 1 root root 1543 2009-01-01 00:00 Vendor_045e_Product_028e.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02d1.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02dd.kl
-rw-r--r-- 1 root root 1402 2009-01-01 00:00 Vendor_045e_Product_02e0.kl
-rw-r--r-- 1 root root 1341 2009-01-01 00:00 Vendor_045e_Product_02e3.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02ea.kl
-rw-r--r-- 1 root root 1772 2009-01-01 00:00 Vendor_045e_Product_02fd.kl
-rw-r--r-- 1 root root 1543 2009-01-01 00:00 Vendor_045e_Product_0719.kl
...
But I can't tell through dmesg which one is the proper one. If I remove the USB adapter, plug it back in, and run dmesg I get the output below (only the last few lines provided here). I copied and pasted the entire dmesg output into VSCode and searched for "New USB device found" and "045e" but got zero results.

Code: Select all

...
[203529.745306] usb 1-1.4: new full-speed USB device number 10 using xhci-hcd
[203529.882383] usb 1-1.4: Unsupported device
[203529.882644] usb 1-1.4: Unsupported device
[203529.888664] usb 1-1.4: Unsupported device
[203529.891773] usb 1-1.4: Unsupported device
And that's the extent of how far I'm able to understand and troubleshoot what's going on. 🤷🏻‍♂️ Any help would be greatly appreciated. Perhaps I could try the Magisk module "OneController"? But I'd prefer to get it working without relying on another 3rd-party module.

Thanks.

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

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

Post by voodik »

jd637 wrote:
Mon Nov 23, 2020 11:22 pm
Has anyone had luck getting an XBOX 360 controller with the wireless USB adapter working? It works partially, but the right-stick input is all over the place. If I'm in a first-person-shooter game, the camera just spins all around. The mapping of other buttons are off as well. I've confirmed that the controller and adapter work fine in multiple other devices/computers. I believe it's related to this issue posted on XDA: https://forum.xda-developers.com/showpo ... stcount=12

The person recommended this fix:
Firstly you need to run dmesg and look for the line:
<6>[ 1489.104652] usb 2-1: New USB device found, idVendor=045e, idProduct=0291

Taken from http://forum.xda-developers.com/show....php?t=1418263:

Open up a terminal emulator and run the following (building the new filename from the idVendor and idProduct)

su
cd /system/usr/keylayout/
mount -o remount,rw /system
cp Vendor_045e_Product_028e.kl Vendor_045e_Product_0291.kl

Reboot for the change to take into effect and both gta3 and shadowgun worked brilliantly. I had to assign some controls from within the shadowgun game to my preference and I can't be happier. I am running teamEOS ics ROM but this should work for honeycomb.
I do see some "Vendor_045e_..." files in /system/usr/keylayout:

Code: Select all

...
-rw-r--r-- 1 root root 1543 2009-01-01 00:00 Vendor_045e_Product_028e.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02d1.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02dd.kl
-rw-r--r-- 1 root root 1402 2009-01-01 00:00 Vendor_045e_Product_02e0.kl
-rw-r--r-- 1 root root 1341 2009-01-01 00:00 Vendor_045e_Product_02e3.kl
-rw-r--r-- 1 root root 1568 2009-01-01 00:00 Vendor_045e_Product_02ea.kl
-rw-r--r-- 1 root root 1772 2009-01-01 00:00 Vendor_045e_Product_02fd.kl
-rw-r--r-- 1 root root 1543 2009-01-01 00:00 Vendor_045e_Product_0719.kl
...
But I can't tell through dmesg which one is the proper one. If I remove the USB adapter, plug it back in, and run dmesg I get the output below (only the last few lines provided here). I copied and pasted the entire dmesg output into VSCode and searched for "New USB device found" and "045e" but got zero results.

Code: Select all

...
[203529.745306] usb 1-1.4: new full-speed USB device number 10 using xhci-hcd
[203529.882383] usb 1-1.4: Unsupported device
[203529.882644] usb 1-1.4: Unsupported device
[203529.888664] usb 1-1.4: Unsupported device
[203529.891773] usb 1-1.4: Unsupported device
And that's the extent of how far I'm able to understand and troubleshoot what's going on. 🤷🏻‍♂️ Any help would be greatly appreciated. Perhaps I could try the Magisk module "OneController"? But I'd prefer to get it working without relying on another 3rd-party module.

Thanks.
run lsusb command with and without controller connected. Check difference to find out your vid/pid
These users thanked the author voodik for the post:
jd637 (Tue Nov 24, 2020 1:12 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Mon Nov 23, 2020 11:55 pm
run lsusb command with and without controller connected. Check difference to find out your vid/pid
Got it. Thanks! Almost there. I get an error when trying to remount. I'm guessing this mount command is a bit different for Lineage?

Code: Select all

# cp Vendor_045e_Product_028e.kl Vendor_045e_Product_0719.kl
cp: Vendor_045e_Product_0719.kl: Read-only file system

# mount -o remount,rw /system 
mount: '/system' not in /proc/mounts

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 12:09 am
voodik wrote:
Mon Nov 23, 2020 11:55 pm
run lsusb command with and without controller connected. Check difference to find out your vid/pid
Got it. Thanks! Almost there. I get an error when trying to remount. I'm guessing this mount command is a bit different for Lineage?

Code: Select all

# cp Vendor_045e_Product_028e.kl Vendor_045e_Product_0719.kl
cp: Vendor_045e_Product_0719.kl: Read-only file system

# mount -o remount,rw /system 
mount: '/system' not in /proc/mounts
just run

Code: Select all

remount
And please confirm if that help I add this to next build.
These users thanked the author voodik for the post:
jd637 (Tue Nov 24, 2020 1:12 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Tue Nov 24, 2020 12:25 am
just run

Code: Select all

remount
And please confirm if that help I add this to next build.
I don't think that worked, but I'm probably doing it incorrectly.

Code: Select all

:# remount
E only functions on userdebug or eng builds
I also tried:

Code: Select all

# remount,rw /system
/system/bin/sh: remount,rw: inaccessible or not found

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 12:32 am
voodik wrote:
Tue Nov 24, 2020 12:25 am
just run

Code: Select all

remount
And please confirm if that help I add this to next build.
I don't think that worked, but I'm probably doing it incorrectly.

Code: Select all

:# remount
E only functions on userdebug or eng builds
I also tried:

Code: Select all

# remount,rw /system
/system/bin/sh: remount,rw: inaccessible or not found
Where you run commands ? Terminal app or adb ?
Are you sure you write right forum ? Are you running Android 10 ATV on N2 ?
Is Magisk installed ?
In this build you get root shell when connect to it via USB adb shell command (if no Magisk installed)
These users thanked the author voodik for the post:
jd637 (Tue Nov 24, 2020 1:12 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Tue Nov 24, 2020 12:39 am
Where you run commands ? Terminal app or adb ?
Are you sure you write right forum ? Are you running Android 10 ATV on N2 ?
Is Magisk installed ?
In this build you get root shell when connect to it via USB adb shell command (if no Magisk installed)
Definitely 10 ATV. See below for contents of /system/build.prop.

Magisk is installed. I tried via Terminal app, Termux app, SSH through SimpleSSHD app, and adb shell (typed SU and then saw the prompt that Shell was granted superuser rights).

Thanks again for your help.

Image

Code: Select all

# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Sat Oct 31 17:59:17 WITA 2020
ro.system.build.date.utc=1604138357
ro.system.build.fingerprint=hk/lineage_odroidn2/odroidn2:10/QQ3A.200805.001/root10311759:userdebug/test-keys
ro.system.build.id=QQ3A.200805.001
ro.system.build.tags=test-keys
ro.system.build.type=userdebug
ro.system.build.version.incremental=eng.root.20201031.175916
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=hk
ro.product.system.device=odroidn2
ro.product.system.manufacturer=hardkernel
ro.product.system.model=ODROID-N2-ATV
ro.product.system.name=odroidn2
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ3A.200805.001
ro.build.display.id=lineage_odroidn2-userdebug 10 QQ3A.200805.001 eng.root.20201031.175916 test-keys
ro.build.version.incremental=eng.root.20201031.175916
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2020-10-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Sat Oct 31 17:59:17 WITA 2020
ro.build.date.utc=1604138357
ro.build.type=userdebug
ro.build.user=root
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=lineage_odroidn2-userdebug
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=11
# ro.build.product is obsolete; use ro.product.device
ro.build.product=odroidn2
# Do not try to parse description or thumbprint
ro.build.description=lineage_odroidn2-userdebug 10 QQ3A.200805.001 eng.root.20201031.175916 test-keys
ro.lineage.device=odroidn2
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
ro.lineage.version=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineage.releasetype=UNOFFICIAL
ro.lineage.build.version=17.1
ro.modversion=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineagelegal.url=https://lineageos.org/legal
ro.lineage.display.version=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineage.build.version.plat.sdk=9
ro.lineage.build.version.plat.rev=0

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 12:53 am
voodik wrote:
Tue Nov 24, 2020 12:39 am
Where you run commands ? Terminal app or adb ?
Are you sure you write right forum ? Are you running Android 10 ATV on N2 ?
Is Magisk installed ?
In this build you get root shell when connect to it via USB adb shell command (if no Magisk installed)
Definitely 10 ATV. See below for contents of /system/build.prop.

Magisk is installed. I tried via Terminal app, Termux app, SSH through SimpleSSHD app, and adb shell (typed SU and then saw the prompt that Shell was granted superuser rights).

Thanks again for your help.

Image

Code: Select all

# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Sat Oct 31 17:59:17 WITA 2020
ro.system.build.date.utc=1604138357
ro.system.build.fingerprint=hk/lineage_odroidn2/odroidn2:10/QQ3A.200805.001/root10311759:userdebug/test-keys
ro.system.build.id=QQ3A.200805.001
ro.system.build.tags=test-keys
ro.system.build.type=userdebug
ro.system.build.version.incremental=eng.root.20201031.175916
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=hk
ro.product.system.device=odroidn2
ro.product.system.manufacturer=hardkernel
ro.product.system.model=ODROID-N2-ATV
ro.product.system.name=odroidn2
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ3A.200805.001
ro.build.display.id=lineage_odroidn2-userdebug 10 QQ3A.200805.001 eng.root.20201031.175916 test-keys
ro.build.version.incremental=eng.root.20201031.175916
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2020-10-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Sat Oct 31 17:59:17 WITA 2020
ro.build.date.utc=1604138357
ro.build.type=userdebug
ro.build.user=root
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=lineage_odroidn2-userdebug
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=11
# ro.build.product is obsolete; use ro.product.device
ro.build.product=odroidn2
# Do not try to parse description or thumbprint
ro.build.description=lineage_odroidn2-userdebug 10 QQ3A.200805.001 eng.root.20201031.175916 test-keys
ro.lineage.device=odroidn2
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
ro.lineage.version=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineage.releasetype=UNOFFICIAL
ro.lineage.build.version=17.1
ro.modversion=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineagelegal.url=https://lineageos.org/legal
ro.lineage.display.version=17.1-20201031-UNOFFICIAL-VooDiK-odroidn2
ro.lineage.build.version.plat.sdk=9
ro.lineage.build.version.plat.rev=0
Try

Code: Select all

su
bash
remount
If no i will try reproduce in this version tomorrow with installed magisk.
These users thanked the author voodik for the post:
jd637 (Tue Nov 24, 2020 1:11 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Tue Nov 24, 2020 1:03 am
Try

Code: Select all

su
bash
remount
If no i will try reproduce in this version tomorrow with installed magisk.
Same result, unfortunately. Thanks for your help today and for looking into it tomorrow.

Image

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 1:11 am
voodik wrote:
Tue Nov 24, 2020 1:03 am
Try

Code: Select all

su
bash
remount
If no i will try reproduce in this version tomorrow with installed magisk.
Same result, unfortunately. Thanks for your help today and for looking into it tomorrow.


I don't know which modules you installed with Magisk but I think Magisk and some modules cause this problem.
Just on fresh ATV Android installed Magisk, open Local terminal from Developer settings and everything works.
magisk.png
magisk.png (33.14 KiB) Viewed 841 times
remount.png
remount.png (43.5 KiB) Viewed 841 times
So please uninstall Magisk, and or Reinstall system and do your manipulations. When everything ok bring Magisk back.
Regards.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Tue Nov 24, 2020 9:48 am
So please uninstall Magisk, and or Reinstall system and do your manipulations. When everything ok bring Magisk back.
Regards.
That worked. I reinstalled the system and was able to remount over adb shell. I was able to copy the kl file, but unfortunately that did not fix my controller input issue. Oh well. At least now I'm able to manipulate these button mapping files, so I can continue to try and figure it out. Thank you again for your help. I'll be sure to report back here if I have any luck fixing the controller input issue.

Edit: Is there an equivalent program on Android to Linux's jstest for testing joystick inputs?

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 4:54 pm
voodik wrote:
Tue Nov 24, 2020 9:48 am
So please uninstall Magisk, and or Reinstall system and do your manipulations. When everything ok bring Magisk back.
Regards.
That worked. I reinstalled the system and was able to remount over adb shell. I was able to copy the kl file, but unfortunately that did not fix my controller input issue. Oh well. At least now I'm able to manipulate these button mapping files, so I can continue to try and figure it out. Thank you again for your help. I'll be sure to report back here if I have any luck fixing the controller input issue.

Edit: Is there an equivalent program on Android to Linux's jstest for testing joystick inputs?
I don't know such programs, but getevent command might help you.
e.g.

Code: Select all

getevent -l
You can see if any input events occurs, remap if they wrong
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

I got it working by installing the 1Controller Magisk module. From my understanding, the module just puts the correct kl files in /system/usr/keylayout/. After installing the module and successfully testing the controller input, I compared the contents of the new Vendor_045e_Product_0719.kl with the previous one I was using per that other fix I found online. Most of it was the same, but there was indeed a difference...

The correct mappings from the new kl file:

Code: Select all

key 316   HOME
...
# Hat.
# (D-pad is reported as digital. Each direction has a scan code.)
key 0x2c0 DPAD_LEFT
key 0x2c1 DPAD_RIGHT
key 0x2c2 DPAD_UP
key 0x2c3 DPAD_DOWN
The differing incorrect mappings from my old kl file:

Code: Select all

key 316   BUTTON_MODE
...
# Hat.
axis 0x10 HAT_X
axis 0x11 HAT_Y
Below are the the full contents of the working Vendor_045e_Product_0719.kl file that the Magisk module installed, in case anyone needs it.

Thank you again, Voodik, for your help.

Code: Select all

# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# XBox 360 USB Wireless Controller
# Reports itself as "Xbox 360 Wireless Receiver" and
# "Microsoft Corp. Xbox 360 Wireless Adapter"
# Similar in behavior to XBox 360 USB Controller except for the d-pad,
# which is digital (scan codes instead of axes) on the wireless version.

key 304   BUTTON_A
key 305   BUTTON_B
key 307   BUTTON_X
key 308   BUTTON_Y
key 310   BUTTON_L1
key 311   BUTTON_R1
key 314   BUTTON_SELECT
key 315   BUTTON_START
key 316   HOME
key 317   BUTTON_THUMBL
key 318   BUTTON_THUMBR

# Left and right stick.
# The reported value for flat is 128 out of a range from -32767 to 32768, which is absurd.
# This confuses applications that rely on the flat value because the joystick actually
# settles in a flat range of +/- 4096 or so.
axis 0x00 X flat 4096
axis 0x01 Y flat 4096
axis 0x03 Z flat 4096
axis 0x04 RZ flat 4096

# Triggers.
axis 0x02 LTRIGGER
axis 0x05 RTRIGGER

# Hat.
# (D-pad is reported as digital. Each direction has a scan code.)
key 0x2c0 DPAD_LEFT
key 0x2c1 DPAD_RIGHT
key 0x2c2 DPAD_UP
key 0x2c3 DPAD_DOWN
These users thanked the author jd637 for the post:
voodik (Tue Nov 24, 2020 7:42 pm)

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

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

Post by voodik »

jd637 wrote:
Tue Nov 24, 2020 7:21 pm
I got it working by installing the 1Controller Magisk module. From my understanding, the module just puts the correct kl files in /system/usr/keylayout/. After installing the module and successfully testing the controller input, I compared the contents of the new Vendor_045e_Product_0719.kl with the previous one I was using per that other fix I found online. Most of it was the same, but there was indeed a difference...

The correct mappings from the new kl file:

Code: Select all

key 316   HOME
...
# Hat.
# (D-pad is reported as digital. Each direction has a scan code.)
key 0x2c0 DPAD_LEFT
key 0x2c1 DPAD_RIGHT
key 0x2c2 DPAD_UP
key 0x2c3 DPAD_DOWN
The differing incorrect mappings from my old kl file:

Code: Select all

key 316   BUTTON_MODE
...
# Hat.
axis 0x10 HAT_X
axis 0x11 HAT_Y
Below are the the full contents of the working Vendor_045e_Product_0719.kl file that the Magisk module installed, in case anyone needs it.

Thank you again, Voodik, for your help.

Code: Select all

# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# XBox 360 USB Wireless Controller
# Reports itself as "Xbox 360 Wireless Receiver" and
# "Microsoft Corp. Xbox 360 Wireless Adapter"
# Similar in behavior to XBox 360 USB Controller except for the d-pad,
# which is digital (scan codes instead of axes) on the wireless version.

key 304   BUTTON_A
key 305   BUTTON_B
key 307   BUTTON_X
key 308   BUTTON_Y
key 310   BUTTON_L1
key 311   BUTTON_R1
key 314   BUTTON_SELECT
key 315   BUTTON_START
key 316   HOME
key 317   BUTTON_THUMBL
key 318   BUTTON_THUMBR

# Left and right stick.
# The reported value for flat is 128 out of a range from -32767 to 32768, which is absurd.
# This confuses applications that rely on the flat value because the joystick actually
# settles in a flat range of +/- 4096 or so.
axis 0x00 X flat 4096
axis 0x01 Y flat 4096
axis 0x03 Z flat 4096
axis 0x04 RZ flat 4096

# Triggers.
axis 0x02 LTRIGGER
axis 0x05 RTRIGGER

# Hat.
# (D-pad is reported as digital. Each direction has a scan code.)
key 0x2c0 DPAD_LEFT
key 0x2c1 DPAD_RIGHT
key 0x2c2 DPAD_UP
key 0x2c3 DPAD_DOWN
As I understand this mapping should work without Magisk ? So I can add it to next builds?
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

jd637
Posts: 22
Joined: Sun Nov 01, 2020 2:21 am
languages_spoken: english
ODROIDs: N2+
Has thanked: 9 times
Been thanked: 4 times
Contact:

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

Post by jd637 »

voodik wrote:
Tue Nov 24, 2020 7:42 pm
As I understand this mapping should work without Magisk ? So I can add it to next builds?
That's my understanding too, but here is the module's GitHub repo in case you want to look into it more. You would understand what's happening better than I do. :) There are a few more kl files for other game controllers that you might want to add as well.

Edit: Here's the XDA forums thread discussing the module. https://forum.xda-developers.com/apps/m ... t-t3865889
These users thanked the author jd637 for the post:
voodik (Tue Nov 24, 2020 8:00 pm)

Sav
Posts: 244
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 73 times
Been thanked: 26 times
Contact:

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

Post by Sav »

Hi,
did someone try latest dolphin emulator? The app starts, but when I try to launch a game it crashes and returns to the main app page.
No issues on Voodik's ATV 16 version.

boudour1
Posts: 19
Joined: Mon Nov 23, 2020 5:54 pm
languages_spoken: english
ODROIDs: odroidn2
Location: Paris
Has thanked: 6 times
Been thanked: 1 time
Contact:

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

Post by boudour1 »

voodik wrote:
Thu Jun 25, 2020 11:05 pm
Call for beta test : LineageOS-17.1 based Android TV for Odroid-N2


atv_n2_q.png



How-to install.
For first time you need prepare your emmc/sd with spercial selfinstall image.
You can find latest version here

Code: Select all

https://oph.mdrjr.net/voodik/S922X/ODROID-N2/Android/LineageOTA-17.1-ATV/builds/selfinstall/
Image flashing guide.
https://wiki.odroid.com/troubleshooting ... hing_tools

For Google apps please read this.
https://www.google.com/android/uncertified/
Also after you register your Android framework ID, please wait some time (30-60 minutes) then reboot Odroid and try to add Google Account.


Extra:
  • tvheadend
  • aptX aptXHD ldac Bluetooth codecs
Changelog:

Code: Select all

20201031 64 bit Alpha-0.2
* Fixed inactive Play Store menu
* Added Realtek WIFI 8188eus driver
* Added persist.wifi_arg property to set WIFI module loading arguments.
* Fixed rtl8812au minor issues
* Fixed minor WIFI and BT issues 
* Removed/Cleanup some unused things
* tvheadend updated to latest version
* Merge with last BSP changes
* Lineage merge with upstream
20200625 Alpha-v0.1
* first alpha release
Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks

boudour1
Posts: 19
Joined: Mon Nov 23, 2020 5:54 pm
languages_spoken: english
ODROIDs: odroidn2
Location: Paris
Has thanked: 6 times
Been thanked: 1 time
Contact:

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

Post by boudour1 »

Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks

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

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

Post by voodik »

boudour1 wrote:
Mon Dec 14, 2020 6:47 pm
Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks
Yes, USB modem support stripped down from this build. I don't think someone need it on ATV version.

BTW.
If you really need it I can add it to next update.
These users thanked the author voodik for the post:
boudour1 (Mon Dec 14, 2020 10:31 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

boudour1
Posts: 19
Joined: Mon Nov 23, 2020 5:54 pm
languages_spoken: english
ODROIDs: odroidn2
Location: Paris
Has thanked: 6 times
Been thanked: 1 time
Contact:

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

Post by boudour1 »

voodik wrote:
Mon Dec 14, 2020 7:40 pm
boudour1 wrote:
Mon Dec 14, 2020 6:47 pm
Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks
Yes, USB modem support stripped down from this build. I don't think someone need it on ATV version.

BTW.
If you really need it I can add it to next update.
okay thanks for your response, if i will copy the usb_modeswitch to the /system/bin it will work or not ?
because honestly i had test it in AOSP of the odroid and it doesnt work it needs other lib to add like libusb

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

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

Post by voodik »

boudour1 wrote:
Mon Dec 14, 2020 10:31 pm
voodik wrote:
Mon Dec 14, 2020 7:40 pm
boudour1 wrote:
Mon Dec 14, 2020 6:47 pm
Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks
Yes, USB modem support stripped down from this build. I don't think someone need it on ATV version.

BTW.
If you really need it I can add it to next update.
okay thanks for your response, if i will copy the usb_modeswitch to the /system/bin it will work or not ?
because honestly i had test it in AOSP of the odroid and it doesnt work it needs other lib to add like libusb

Code: Select all

/vendor/bin/usb_modeswitch
/vendor/lib64/libusb.so
/vendor/etc/init/usb_modeswitch.rc
/odm/usb_modeswitch.conf
These users thanked the author voodik for the post:
boudour1 (Tue Dec 15, 2020 6:21 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

boudour1
Posts: 19
Joined: Mon Nov 23, 2020 5:54 pm
languages_spoken: english
ODROIDs: odroidn2
Location: Paris
Has thanked: 6 times
Been thanked: 1 time
Contact:

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

Post by boudour1 »

voodik wrote:
Mon Dec 14, 2020 11:34 pm
boudour1 wrote:
Mon Dec 14, 2020 10:31 pm
voodik wrote:
Mon Dec 14, 2020 7:40 pm
boudour1 wrote:
Mon Dec 14, 2020 6:47 pm
Good morning Voodik thanks alot fro the great work you have done, well i have some questions about integrating USB 3G/4G modem to ATV solution of the lineage OS, I have tested it in Mobile version and it works good but when i did the same for atv it doesn't work. i wanna know if this depends on the version of mobile and atv or you didnt integrated yet ?
thanks
Yes, USB modem support stripped down from this build. I don't think someone need it on ATV version.

BTW.
If you really need it I can add it to next update.
okay thanks for your response, if i will copy the usb_modeswitch to the /system/bin it will work or not ?
because honestly i had test it in AOSP of the odroid and it doesnt work it needs other lib to add like libusb

Code: Select all

/vendor/bin/usb_modeswitch
/vendor/lib64/libusb.so
/vendor/etc/init/usb_modeswitch.rc
/odm/usb_modeswitch.conf
thanks alot it works

taimed
Posts: 26
Joined: Tue Dec 08, 2020 4:09 pm
languages_spoken: english
Has thanked: 3 times
Been thanked: 0
Contact:

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

Post by taimed »

jd637 wrote:
Thu Nov 05, 2020 10:45 pm
thering1975 wrote:
Thu Nov 05, 2020 9:32 pm
jd637 wrote:
Wed Nov 04, 2020 10:08 pm
Anyone else having trouble getting the app switcher ("Recent Apps") function to work. I've tried two mini keyboards and a couple of button mapper apps, but no luck. The Button Mapper app registers the keboard input but after mapping the button to it to Recent Apps action it doesn't do anything. Same for "Last App" action. I just want to confirm with you guys that these functions are working for you and it's not a LineageOS ATV issue before I continue troubleshooting my setup.
On ATV the recent apps function is not as relevant as it is on standard Android. I have never invoked it on purpose albeit it has popped up once when i was randomnly mashing keys lol. Atv is more designed to go back to home screen and quickly select app

However i understand some do like that feature so im not much help there, i know i only used it before when CLOSE ALL was an option (this was on a gt king pro), and i replaced that with a kill all app and a widget on home screen.
Yeah, after some research I basically came to the conclusion that the Recent Apps feature isn't available on Android TV, which is fine. As you mentioned, it's not that big of a deal. I just thought there was something wrong with my remote or my install of LineageOS. I ended up achieving the functionality I wanted with a couple of apps -- Dashboard (easy to switch between the last few used apps), and Background Apps & Processes List (easy to see what's open and close stuff). Along with the Button Mapper app, everything is working great. I even figured out how to fix the SafetyNet issues (here's the YouTube video that helped me, if anyone's interested).

There's really only one more thing I'm stuck on and that's setting up a custom IR remote configuration. The remote.conf file is not in /system/etc/ as described in the Ordoid Wiki. I ended up finding a remote.cfg in /vendor/etc/, but I can't figure out how to edit it. I've granted Sudo permissions to Terminal and Shell, tried through adb root, but it always shows "File is Unwritable" in nano. Any idea how I can modify this file?
any updates regarding this ?

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

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

Post by voodik »

taimed wrote:
Mon Dec 28, 2020 9:06 pm
jd637 wrote:
Thu Nov 05, 2020 10:45 pm
thering1975 wrote:
Thu Nov 05, 2020 9:32 pm
jd637 wrote:
Wed Nov 04, 2020 10:08 pm
Anyone else having trouble getting the app switcher ("Recent Apps") function to work. I've tried two mini keyboards and a couple of button mapper apps, but no luck. The Button Mapper app registers the keboard input but after mapping the button to it to Recent Apps action it doesn't do anything. Same for "Last App" action. I just want to confirm with you guys that these functions are working for you and it's not a LineageOS ATV issue before I continue troubleshooting my setup.
On ATV the recent apps function is not as relevant as it is on standard Android. I have never invoked it on purpose albeit it has popped up once when i was randomnly mashing keys lol. Atv is more designed to go back to home screen and quickly select app

However i understand some do like that feature so im not much help there, i know i only used it before when CLOSE ALL was an option (this was on a gt king pro), and i replaced that with a kill all app and a widget on home screen.
Yeah, after some research I basically came to the conclusion that the Recent Apps feature isn't available on Android TV, which is fine. As you mentioned, it's not that big of a deal. I just thought there was something wrong with my remote or my install of LineageOS. I ended up achieving the functionality I wanted with a couple of apps -- Dashboard (easy to switch between the last few used apps), and Background Apps & Processes List (easy to see what's open and close stuff). Along with the Button Mapper app, everything is working great. I even figured out how to fix the SafetyNet issues (here's the YouTube video that helped me, if anyone's interested).

There's really only one more thing I'm stuck on and that's setting up a custom IR remote configuration. The remote.conf file is not in /system/etc/ as described in the Ordoid Wiki. I ended up finding a remote.cfg in /vendor/etc/, but I can't figure out how to edit it. I've granted Sudo permissions to Terminal and Shell, tried through adb root, but it always shows "File is Unwritable" in nano. Any idea how I can modify this file?
any updates regarding this ?
In lineage /odm/remote.tab4 file is used.
You can connect yor sd/emmc to Window/Linux/Mac and found this file on fat partition.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

taimed
Posts: 26
Joined: Tue Dec 08, 2020 4:09 pm
languages_spoken: english
Has thanked: 3 times
Been thanked: 0
Contact:

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

Post by taimed »

voodik wrote:
Mon Dec 28, 2020 9:20 pm
taimed wrote:
Mon Dec 28, 2020 9:06 pm
jd637 wrote:
Thu Nov 05, 2020 10:45 pm
thering1975 wrote:
Thu Nov 05, 2020 9:32 pm
jd637 wrote:
Wed Nov 04, 2020 10:08 pm
Anyone else having trouble getting the app switcher ("Recent Apps") function to work. I've tried two mini keyboards and a couple of button mapper apps, but no luck. The Button Mapper app registers the keboard input but after mapping the button to it to Recent Apps action it doesn't do anything. Same for "Last App" action. I just want to confirm with you guys that these functions are working for you and it's not a LineageOS ATV issue before I continue troubleshooting my setup.
On ATV the recent apps function is not as relevant as it is on standard Android. I have never invoked it on purpose albeit it has popped up once when i was randomnly mashing keys lol. Atv is more designed to go back to home screen and quickly select app

However i understand some do like that feature so im not much help there, i know i only used it before when CLOSE ALL was an option (this was on a gt king pro), and i replaced that with a kill all app and a widget on home screen.
Yeah, after some research I basically came to the conclusion that the Recent Apps feature isn't available on Android TV, which is fine. As you mentioned, it's not that big of a deal. I just thought there was something wrong with my remote or my install of LineageOS. I ended up achieving the functionality I wanted with a couple of apps -- Dashboard (easy to switch between the last few used apps), and Background Apps & Processes List (easy to see what's open and close stuff). Along with the Button Mapper app, everything is working great. I even figured out how to fix the SafetyNet issues (here's the YouTube video that helped me, if anyone's interested).

There's really only one more thing I'm stuck on and that's setting up a custom IR remote configuration. The remote.conf file is not in /system/etc/ as described in the Ordoid Wiki. I ended up finding a remote.cfg in /vendor/etc/, but I can't figure out how to edit it. I've granted Sudo permissions to Terminal and Shell, tried through adb root, but it always shows "File is Unwritable" in nano. Any idea how I can modify this file?
any updates regarding this ?
In lineage /odm/remote.tab4 file is used.
You can connect yor sd/emmc to Window/Linux/Mac and found this file on fat partition.
I want to use my own remote control, but I can't find the file to modify

maple121
Posts: 14
Joined: Tue Mar 27, 2018 3:27 pm
languages_spoken: English, Korean
ODROIDs: Odroid-C2
Odroid-XU4
Odroid-N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

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

Post by maple121 »

I want to report an error on my system.

When watching Youtube contents, and selecting one to see, then my monitor is going to sleep mode. I think it looks like "Monitor Off" command is coming out from N2 through HDMI cable when selecting one contents on Youtube. Did anybody experience like me?

Even though I turned off HDMI-CEC mode from Android TV Setup, the problem is still happening.

mad_ady
Posts: 9067
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 596 times
Been thanked: 578 times
Contact:

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

Post by mad_ady »

Try playing youtube from a browser to see if it works
These users thanked the author mad_ady for the post:
maple121 (Mon Jan 04, 2021 12:53 pm)

maple121
Posts: 14
Joined: Tue Mar 27, 2018 3:27 pm
languages_spoken: English, Korean
ODROIDs: Odroid-C2
Odroid-XU4
Odroid-N2
Has thanked: 4 times
Been thanked: 1 time
Contact:

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

Post by maple121 »

mad_ady wrote:
Sun Jan 03, 2021 5:05 pm
Try playing youtube from a browser to see if it works
Thank you for the comment.
I tested it from a browser and there was no problem.

I'm using 21:9 monitor with 3440x1440 resolution.
The problem only happens with 3440x1440 & 2160x1080 resolution, not with 1080p when running Youtube App.

I tested it with ASOP Android 9.0 PIE (ATV version) in below, and there was no problem.

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

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

Post by voodik »

Update!

Code: Select all

20210115 Alpha-v0.3
* Added WIFI Direct feature (disabled by default)
* Added Miracast(WFD) sink/source support
* Added mouse right click option to Odroid Settings
* Added Enable/Disable CEC globally to Odroid Settings
* Kernel enabled P2P support on supported Realtek WIFI drivers
* Added pinch zoom by mouse wheel
* Added several Joystick keylayout configs (fixed broken ones) 
* Kernel enable CONFIG_HID_SMARTJOYPLUS
* Kernel added Realtek 8814au WIFI driver
* Sync wifi_id_list with drivers (add missing vid/pid)
* Fixed Recovery HDMI output with custom resolution
* Fixed USB Microphone input (Fixes Ok Google)
* Fixed few NPE's
* Lineage merge with upstream
How to enable WIFI Direct/WFD/Miracast support
viewtopic.php?p=316848#p316848
These users thanked the author voodik for the post (total 2):
Sav (Fri Jan 15, 2021 11:32 pm) • odroid (Mon Jan 18, 2021 9:31 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

Post Reply

Return to “Android”

Who is online

Users browsing this forum: No registered users and 0 guests