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

[mad_ady]

Thanks!

[mad_ady]

Ok, I'm playing with alpha 0.2 on an N2+. I've install Magisk from within recovery (if you try to update it from Odroid Settings it fails, but if you do it from recovery it's fine). All seems fine except adb (over network) post Magisk. I used to be able to do adb connect x.x.x.x; adb shell, but now it complains:

Code: Select all

$ adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

If I try via microusb, I get the same:

Code: Select all

 adrianp  ~  Downloads  adb devices
List of devices attached
001e0642505d	unauthorized

 adrianp  ~  Downloads  adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
 adrianp  ~  Downloads  1  

Most likely my adb has changed from Magisk. Any ideas what I could do? I plan on using scrcpy to do a remote setup/testing.

@voodik - regarding Magisk - I have a question. I plan on compiling my own kernel to add support for onewire (not sure if the stock kernel has it) and also for docker-related modules. If I have time I'd like to try to run docker from Android or from within Linux Deploy. I've played a bit with it and it has potential, but I ran out of time because of the pandemic. I doubt I'll have more time, but I need to keep my mind busy with something. Anyway, the steps are roughly described here: https://magazine.odroid.com/article/run ... r-android/.

My question is - if I start flashing my own kernel/dtbs, what impact does that have on Magisk? Do I need to reinstall Magisk after a kernel flash? Not sure how it changes kernel/dtbs, or if it doesn't (though it reports it's packing/unpacking them)...
Thanks!

[odroid]

Hey Voodik,

Can you check the HW RTC functionality with a Lithium coin battery installation on your N2+ board?
One user has reported an issue with RTC. That project looks quite attractive.
viewtopic.php?p=306902#p306902

[voodik]

Ok, I'm playing with alpha 0.2 on an N2+. I've install Magisk from within recovery (if you try to update it from Odroid Settings it fails, but if you do it from recovery it's fine). All seems fine except adb (over network) post Magisk. I used to be able to do adb connect x.x.x.x; adb shell, but now it complains:

Code: Select all

$ adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

If I try via microusb, I get the same:

Code: Select all

 adrianp  ~  Downloads  adb devices
List of devices attached
001e0642505d	unauthorized

 adrianp  ~  Downloads  adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
 adrianp  ~  Downloads  1  

Most likely my adb has changed from Magisk. Any ideas what I could do? I plan on using scrcpy to do a remote setup/testing.

@voodik - regarding Magisk - I have a question. I plan on compiling my own kernel to add support for onewire (not sure if the stock kernel has it) and also for docker-related modules. If I have time I'd like to try to run docker from Android or from within Linux Deploy. I've played a bit with it and it has potential, but I ran out of time because of the pandemic. I doubt I'll have more time, but I need to keep my mind busy with something. Anyway, the steps are roughly described here: https://magazine.odroid.com/article/run ... r-android/.

My question is - if I start flashing my own kernel/dtbs, what impact does that have on Magisk? Do I need to reinstall Magisk after a kernel flash? Not sure how it changes kernel/dtbs, or if it doesn't (though it reports it's packing/unpacking them)...
Thanks!

You need reinstall magisk if you flash new dtbs.

[voodik]

Hey Voodik,

Can you check the HW RTC functionality with a Lithium coin battery installation on your N2+ board?
One user has reported an issue with RTC. That project looks quite attractive.
viewtopic.php?p=306902#p306902

Sure, i will check it today.

[mad_ady]

Ok, I'm playing with alpha 0.2 on an N2+. I've install Magisk from within recovery (if you try to update it from Odroid Settings it fails, but if you do it from recovery it's fine). All seems fine except adb (over network) post Magisk. I used to be able to do adb connect x.x.x.x; adb shell, but now it complains:

Code: Select all

$ adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

If I try via microusb, I get the same:

Code: Select all

 adrianp  ~  Downloads  adb devices
List of devices attached
001e0642505d	unauthorized

 adrianp  ~  Downloads  adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
 adrianp  ~  Downloads  1  

Most likely my adb has changed from Magisk. Any ideas what I could do? I plan on using scrcpy to do a remote setup/testing.

@voodik - regarding Magisk - I have a question. I plan on compiling my own kernel to add support for onewire (not sure if the stock kernel has it) and also for docker-related modules. If I have time I'd like to try to run docker from Android or from within Linux Deploy. I've played a bit with it and it has potential, but I ran out of time because of the pandemic. I doubt I'll have more time, but I need to keep my mind busy with something. Anyway, the steps are roughly described here: https://magazine.odroid.com/article/run ... r-android/.

My question is - if I start flashing my own kernel/dtbs, what impact does that have on Magisk? Do I need to reinstall Magisk after a kernel flash? Not sure how it changes kernel/dtbs, or if it doesn't (though it reports it's packing/unpacking them)...
Thanks!

Well, I'm still struggling with the ADB unauthorized error after installing Magisk. I've tried disabling ADB from developer options and re-enabling it, but it didn't do anything. Also deleted my adb key, restarted everything multiple times, etc. Any other ideas I could try?
One more curious thing - I have a USB UART and I can get bootloader/boot messages. However, I never get a shell after the system has booted. Is this normal? How can I enable a shell via serial?

[Kaos7313]

I have a silly question as I've never used android on anything other than a tablet of Phone.
How do you close background apps that you open. like everytime I open something I can go back to the main OS screen but when you click the square on the bottom NAV bar all the shit you opened is there and it uses a lot of resources and slows everthing down...

For the life of me I can figure out how to close all the shit with just hard resetting the N2.....

[mad_ady]

There are two ways:
1. from the recent apps view you swipe those apps off-screen and they get closed
2. In developer options you can tell it to kill background apps

[mad_ady]

Me again, with my broken adb...
I've flashed alpha 0.2 image to a new emmc and booted it. Installed Magisk 21 this time. Rebooted and tested adb - all is fine. I upgraded to Magisk 21 on my original image (with broken adb), and sadly, adb does not magically recover...
So I'm throwing in the towel and reinstalling... Oh well...

[voodik]

Me again, with my broken adb...
I've flashed alpha 0.2 image to a new emmc and booted it. Installed Magisk 21 this time. Rebooted and tested adb - all is fine. I upgraded to Magisk 21 on my original image (with broken adb), and sadly, adb does not magically recover...
So I'm throwing in the towel and reinstalling... Oh well...

Only custom Magisk which created by me is supported now, don't update it.
I will take a look is it possible create custom Magisk 21.

[mad_ady]

Stock Magisk 21 worked just fine...

[voodik]

n2_11_1.png (84.41 KiB) Viewed 1348 times

[trycatch]

cant believe it, android 11 for N2!!!!

thanks voodik

[mad_ady]

n2_11_1.png

Will it be upgradeable from 10? I ask so that I know of I will invest more time in android 10, or better yet wait for 11...

[voodik]

n2_11_1.png

Will it be upgradeable from 10? I ask so that I know of I will invest more time in android 10, or better yet wait for 11...

It's too early to talk about it, Lineage Team just started working on it, lot of features is missing for now and some bugs occurred.
So i think first nightly version available in 1-2 month.

Stock Magisk 21 worked just fine...

Yes, just tested, Magisk 21 is working out from the box.
So people now can use it instead of my patched versions.

https://github.com/topjohnwu/Magisk/releases

[voodik]

Update

Code: Select all

20201013 Alpha-v0.3
* Fixed some RTC issues
* Removed/Cleanup some unused things
* Merge with last BSP changes
* Lineage merge with upstream

[thering1975]

Hi

In my quest to find the perfect Android experience just tested this rom, all was great, but i have one question. Is Kiosk Mode meant to remove the status and nav bars? If so unfortunately i cannot get it to work on this rom. With a diff launcher the status bar goes but the Navbar is permanently displayed.

Just FYI

[voodik]

Hi

In my quest to find the perfect Android experience just tested this rom, all was great, but i have one question. Is Kiosk Mode meant to remove the status and nav bars? If so unfortunately i cannot get it to work on this rom. With a diff launcher the status bar goes but the Navbar is permanently displayed.

Just FYI

I will check this feature.

[voodik]

Hi

In my quest to find the perfect Android experience just tested this rom, all was great, but i have one question. Is Kiosk Mode meant to remove the status and nav bars? If so unfortunately i cannot get it to work on this rom. With a diff launcher the status bar goes but the Navbar is permanently displayed.

Just FYI

Test version with fixed kiosk mode.
set persist.kiosk_mode true/false
https://drive.google.com/open?id=1UUvxu ... N8eG75vel0

[atwar]

"persist.disable_bluetooth true|false default:true"

Where I may apply this settings to switch on BT?

[voodik]

"persist.disable_bluetooth true|false default:true"

Where I may apply this settings to switch on BT?

Uncheck
Odroid Settings> Misc> Disable bluetooth service

[JosSch]

I'm trying to use the 'com.google.android.things' sample from this forum. (viewtopic.php?t=37101)
But my program crashes when started on the N2+, using image version 20201013.
So i suppose the 'android.things' runtime libraries are not included in this image ?
If not, is there any change they will be included in a next version ?

By the way, the code compiled and runs just fine on an older N2+ android image, i think it was a version 9 of android (but that one was having bluetoothLE issues).

[voodik]

I'm trying to use the 'com.google.android.things' sample from this forum. (viewtopic.php?t=37101)
But my program crashes when started on the N2+, using image version 20201013.
So i suppose the 'android.things' runtime libraries are not included in this image ?
If not, is there any change they will be included in a next version ?

By the way, the code compiled and runs just fine on an older N2+ android image, i think it was a version 9 of android (but that one was having bluetoothLE issues).

I will check this.

[wireshark]

I'm trying to use gapps nano to use Google Assistant.
But it displays error code 70.

Selfinstall Images without preinstalled Gapps
What kind of variant is this?

[voodik]

I'm trying to use gapps nano to use Google Assistant.
But it displays error code 70.

Selfinstall Images without preinstalled Gapps
What kind of variant is this?

Use this
https://oph.mdrjr.net/voodik/S922X/ODRO ... lfinstall/
It allready gapps nano included.

EDIT
I removed Google Search from this build.
So install it from Play Store
https://play.google.com/store/apps/deta ... ksearchbox

[wireshark]

I'm trying to use gapps nano to use Google Assistant.
But it displays error code 70.

Selfinstall Images without preinstalled Gapps
What kind of variant is this?

Use this
https://oph.mdrjr.net/voodik/S922X/ODRO ... lfinstall/
It allready gapps nano included.

Thanks i installed it.
But can't access Google Assistant Voice Match.

After hours of searching on Google,
I knew I had to use at least Gapps micro.

I've tried installing Gapps through the instructions below.
https://wiki.odroid.com/odroid-n2/getti ... stallation

But I failed to install.
Error code 70

[voodik]

Update

Code: Select all

20201103 Alpha-v0.4
* Fixed Odroid Things 
* Fixed Auto Framerate
* Fixed Kiosk mode
* Fixed touch rotation when screen rotated by ro.sf.defaultrotation prop
* Fixed rtl8812au minor issues
* Fixed minor Wifi and BT issues 
* Added Realtek WIFI 8188eus driver
* Added persist.wifi_arg property to set WIFI module loading arguments.
* tvheadend updated to latest version
* Merge with last BSP changes
* Lineage merge with upstream

[voodik]

Oops, forgot to add in changelog

Code: Select all

* Added Bluetooth command line tools (bccmd, hciconfig, hcitool, hcidump)

Maybe someone want to manage BT from console

[wireshark]

Thanks for replying.

There is no problem with install of Google and Google Assistant.
But still like the image below


This is the function the assistant works, speaking "hey, google"
voice match is disabled. (There is no response when I press the button.)

I installed the OS from the link below and tried the same way.
https://wiki.odroid.com/odroid-n2/os_im ... id/android

Still voice match is disabled.
However, installing nano or micro Gapps solves the problem.

Maybe you need to install other packages besides google, google assistant.
(It seems to be included in gapps.)

I'd like to install Gapps in lineageos, but strangely I get Error code :70 during the flashing process.

You said google has been removed from its own install image (nano) with Gapps 64 bit.

Have you ever deleted anything other than google?

[jd637]

Ok, I'm playing with alpha 0.2 on an N2+. I've install Magisk from within recovery (if you try to update it from Odroid Settings it fails, but if you do it from recovery it's fine). All seems fine except adb (over network) post Magisk. I used to be able to do adb connect x.x.x.x; adb shell, but now it complains:

Code: Select all

$ adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

If I try via microusb, I get the same:

Code: Select all

 adrianp  ~  Downloads  adb devices
List of devices attached
001e0642505d	unauthorized

 adrianp  ~  Downloads  adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
 adrianp  ~  Downloads  1  

... Any ideas what I could do? ...

I ran into the same "unauthorized...$ADB_VENDOR_KEYS" issue after installing a Magisk module. To fix it, I had to locate the adbkey.pub file on my Mac (located at ~/.android), copy that to my N2, move it to /data/misc/adb/ and rename it from "adbkey.pub" to "adb_keys" (no extension). After that everything worked fine for me. Here's the resource that helped me figure it out: https://forum.xda-developers.com/androi ... t-t3693961

FYI, the adb_keys file did not exist on my N2, but (from my understanding) if that file already exists for you, you would just copy the contents of adbkey.pub, open (or nano) the existing adb_keys file, enter a line break, and paste in the contents of adbkey.pub. I think adb_keys is an array of public keys separated by line breaks.

[mad_ady]

Thanks, I didn't know about that file!

[mad_ady]

Me again and my Android problems. I've recompiled the Android kernel (steps here: https://magazine.odroid.com/article/run ... r-android/) and enabled onewire support. More specifficaly, this:

Code: Select all

adrianp@bellatrix-n2:~$ zcat /proc/config.gz | grep W1 | grep "=y"
CONFIG_W1=y
CONFIG_W1_CON=y
CONFIG_W1_MASTER_GPIO=y
CONFIG_W1_SLAVE_THERM=y

Flashed kernel and it boots fine, but I need to enable onewire in the dtb (or use the new overlay system - which to be frank I don't understand). This is what I was modifying before:

Code: Select all

fdtput -t s ~/development/linux/arch/arm64/boot/dts/amlogic/meson64_odroidn2_android.dtb /onewire status okay

I tried flashing the modified dtb to dtbs, but it resulted in a boot-loop, because apparently the format of this partition changed since last winter when I played with it.
It currently is:

Code: Select all

adrianp@c4:~$ file dtbs-orig.img 
dtbs-orig.img: Linux Compressed ROM File System data, little endian size 32768 version #2 sorted_dirs CRC 0xa5c0e7fd, edition 0, 41 blocks, 25 files

And I have:

Code: Select all

adrianp@c4:~$ file meson64_odroidn2_android.dtb 
meson64_odroidn2_android.dtb: Device Tree Blob version 17, size=74368, boot CPU=0, string block size=7632, DT structure block size=66680

The dtbs partition seems to contain various other dtbo files:

Code: Select all

adrianp@c4:~$ sudo mount -o loop dtbs-orig.img /media/usb1
adrianp@c4:~$ cd /media/usb1/
adrianp@c4:/media/usb1$ ls -l 
total 93
-rw-r--r-- 1 nobody 254   830 Jan  1  1970 ads7846.dtbo
-rw-r--r-- 1 nobody 254   545 Jan  1  1970 can0.dtbo
-rw-r--r-- 1 nobody 254   241 Jan  1  1970 fanspeed-full.dtbo
-rw-r--r-- 1 nobody 254   982 Jan  1  1970 gpio_shortcut.dtbo
-rw-r--r-- 1 nobody 254   247 Jan  1  1970 gpio_spdif.dtbo
-rw-r--r-- 1 nobody 254  1228 Jan  1  1970 hktft32.dtbo
-rw-r--r-- 1 nobody 254  1876 Jan  1  1970 hktft35.dtbo
-rw-r--r-- 1 nobody 254   223 Jan  1  1970 i2c0.dtbo
-rw-r--r-- 1 nobody 254   223 Jan  1  1970 i2c1.dtbo
-rw-r--r-- 1 nobody 254   228 Jan  1  1970 irblaster.dtbo
-rw-r--r-- 1 nobody 254 72985 Jan  1  1970 meson64_odroidn2_android.dtb
-rw-r--r-- 1 nobody 254  1634 Jan  1  1970 odroidn2-opp.dtbo
-rw-r--r-- 1 nobody 254  1859 Jan  1  1970 odroidn2_plus-opp.dtbo
-rw-r--r-- 1 nobody 254   417 Jan  1  1970 onewire.dtbo
-rw-r--r-- 1 nobody 254  2036 Jan  1  1970 pwm_c-pwmfan.dtbo
-rw-r--r-- 1 nobody 254   413 Jan  1  1970 pwm_cd.dtbo
-rw-r--r-- 1 nobody 254   938 Jan  1  1970 pwm_d-backlight.dtbo
-rw-r--r-- 1 nobody 254   412 Jan  1  1970 pwm_ef.dtbo
-rw-r--r-- 1 nobody 254   225 Jan  1  1970 saradc.dtbo
-rw-r--r-- 1 nobody 254   228 Jan  1  1970 sdio.dtbo
-rw-r--r-- 1 nobody 254   516 Jan  1  1970 spi0.dtbo
-rw-r--r-- 1 nobody 254   768 Jan  1  1970 sx865x-i2c1.dtbo
-rw-r--r-- 1 nobody 254   225 Jan  1  1970 uart0.dtbo
-rw-r--r-- 1 nobody 254   225 Jan  1  1970 uart1.dtbo

What is the elegant way of enabling onewire? I added "onewire" to the list of dtb items in Odroid Config App...
Now, I still can't see my temperature sensor after adding onewire to the list. How can I troubleshoot further? It seems to be enabled:

Code: Select all

adrianp@bellatrix-n2:~$ cat /proc/device-tree/onewire/status
okay

How would one add custom parameters to the dtb with the overlay feature (in Android)?

[voodik]

@mad_ady
/odm/meson64_odroidn2_android.dtb not need anymore, you can safely delete it.
If you want permanent changes. you need re-create dtbs.img.
Copy all files from mounted image to some folder. Make changes in your dtb file.
Then create new dtbs.img

Code: Select all

mkfs.cramfs <dir> <outfile.img>

then flash it to /dev/block/dtbs.

You can also add fdt commands in boot.ini
Read example at the end of second post
viewtopic.php?p=269305#p269305

BTW i don't know which dtb modification you need to make onewire work.

P.S.
https://wiki.odroid.com/odroid-n2/appli ... gpio/1wire

[mad_ady]

Thanks for that! I'll give it a try tomorrrow. If it doesn't work, I'll try booting ubuntu to check the hardware connection

[mad_ady]

Ok, it seems I still get a bootloop when I try to repack the dtbs (by running mkfs.cramfs), after replacing the meson64_odroidn2_android.dtb inside:
Here is the original:

Code: Select all

$ ls -l dtbs-orig.img
-rw-r--r-- 1 adrianp adrianp 131072 Nov 11 10:00 dtbs-orig.img
$ file dtbs-orig.img 
dtbs-orig.img: Linux Compressed ROM File System data, little endian size 32768 version #2 sorted_dirs CRC 0xa5c0e7fd, edition 0, 41 blocks, 25 files

This is the modified file:

Code: Select all

$ ls -l dtbs-onewire.img 
-rw-r--r-- 1 root root 32768 Nov 11 10:06 dtbs-onewire.img
$ file dtbs-onewire.img 
dtbs-onewire.img: Linux Compressed ROM File System data, little endian size 32768 version #2 sorted_dirs CRC 0x6b6619e4, edition 0, 42 blocks, 25 files

I suspect the difference in size is due to the dtbs partition being larger than the actual cramfs archive, so I'm not worried. But it fails to start once I flash it, so I'm puzzled.

@voodik - can you confirm that the kernel source you're building from is this?

https://github.com/hardkernel/linux.git -b odroidn2-4.9.y-android

After compiling (and running git pull to make sure I'm up to date), I get kernel 4.9.113. Maybe it's too old and doesn't support dtb overlay?
I'll validate my hardware sensor via linux, just to make sure it's still working...

[joerg]

Hello new mod , how did you flash? Maybe you have the same issue as had on the C4 earlier this year?
viewtopic.php?p=294144#p294144
If not yet tried with fastboot, you can check if this method works on the N2 with this LOS version. You can interrupt the u-boot with the debug console and start the fastboot from there.
If not working, can you share the onewire patch? When I am back from work I can try it on my N2+.

And: @voodik uses his own kernel repository, but it should almost be the same as the one from Hardkernel. So it should work also with this kernel.

[voodik]

Ok, it seems I still get a bootloop when I try to repack the dtbs (by running mkfs.cramfs), after replacing the meson64_odroidn2_android.dtb inside:
Here is the original:

Code: Select all

$ ls -l dtbs-orig.img
-rw-r--r-- 1 adrianp adrianp 131072 Nov 11 10:00 dtbs-orig.img
$ file dtbs-orig.img 
dtbs-orig.img: Linux Compressed ROM File System data, little endian size 32768 version #2 sorted_dirs CRC 0xa5c0e7fd, edition 0, 41 blocks, 25 files

This is the modified file:

Code: Select all

$ ls -l dtbs-onewire.img 
-rw-r--r-- 1 root root 32768 Nov 11 10:06 dtbs-onewire.img
$ file dtbs-onewire.img 
dtbs-onewire.img: Linux Compressed ROM File System data, little endian size 32768 version #2 sorted_dirs CRC 0x6b6619e4, edition 0, 42 blocks, 25 files

I suspect the difference in size is due to the dtbs partition being larger than the actual cramfs archive, so I'm not worried. But it fails to start once I flash it, so I'm puzzled.

@voodik - can you confirm that the kernel source you're building from is this?

https://github.com/hardkernel/linux.git -b odroidn2-4.9.y-android

After compiling (and running git pull to make sure I'm up to date), I get kernel 4.9.113. Maybe it's too old and doesn't support dtb overlay?
I'll validate my hardware sensor via linux, just to make sure it's still working...

No, you should use this kernel
https://github.com/voodik/android_kerne ... _odroidg12 -b lineage-16.0_odroidg12_64_test4
Please always check which branch have latest commits and use this branch.

[voodik]

Hello new mod , how did you flash? Maybe you have the same issue as had on the C4 earlier this year?
viewtopic.php?p=294144#p294144
If not yet tried with fastboot, you can check if this method works on the N2 with this LOS version. You can interrupt the u-boot with the debug console and start the fastboot from there.
If not working, can you share the onewire patch? When I am back from work I can try it on my N2+.

And: @voodik uses his own kernel repository, but it should almost be the same as the one from Hardkernel. So it should work also with this kernel.

There are lot of backports from mainstream kernel in my kernel branch, and also some config differences.
So I recommend use with my builds use my kernel.

BTW
If you want use hardkernel kernel branch to avoid bootloop at least this commit required.
https://github.com/voodik/android_kerne ... 5360a1d828

[joerg]

Yes, I forgot about. You are right.

[mad_ady]

No, you should use this kernel
https://github.com/voodik/android_kerne ... _odroidg12 -b lineage-16.0_odroidg12_64_test4
Please always check which branch have latest commits and use this branch.

Thanks! I'll keep that in mind when I build my next kernel.
I worked out what was wrong with onewire - turns out it doesn't work under linux as well. During my experiments of flashing kernels I ripped a wire from the temperature sensor. I'll need to do some more robust soldering...

[lifeform]

hello,
how i can emulated pinch with mouse and keyboard?
i trying to use ctrl in keyboard and mouse it did not work.
any help?

[harald_knoll]

Hi,

I am on alpha 4 of this build running on the N2+. Great work. Thanks! I have a couple of questions and comments:

1.) Some applications in Google Play are marked as “incompatible” e.g. Arts and Culture. Due to what? Missing CAM, GPS.
2.) Google Earth is not working probably, looks like an GPU issue. No move possible, no zoom, no details. It seems textures cannot be loaded. As i can see on the Internet this seems to be an old problem and by now i can´t find a solution.
3.) Do you support touch screens with HID e.g. Samsung QM43R-T?
4.) Installed Retrorach. Input control for JoyPads is Android. By nature the only driver. No way to get the XBOX 360 controller funcaton corrertly. Any idea?

Have a good day!

[mad_ady]

Sadly I have to confirm the Google Earth issues. I can use the interface (but not rotate, zoom), but if I use the search bar to go some place, it doesn't load textures... I was planning on doing virtual trips with my kids during the long winter and explore the world... Hopefully it can be fixed

[voodik]

Update

Code: Select all

20201116 Alpha-v0.5
* Fixed USB Microphone input (Fixes Ok Google)
* Added Google Search app (Google Assistant is working, check device system language from Settings> System > Languages and input)
* Disabled DEXPREOPT for some targets (free up space on system partition)
* Minor cleanup/fixes

If you don't have a USB microphone attached, please Disable microphone permission for all apps.

[harald_knoll]

Hi,

will update to .5. BTW: The Android 9 (latest) from Hardkernel has the same issue with the Google Earth etc textures. Was this ever fixed? viewtopic.php?t=2552? Would be great! Have a good day!

OK, loaded. Well, GPU texture problem same as since Android 9 or earlier. Still no chance to get der XBOX S Controller to work with Retroarch. But this seems a general issue with Retroarch for Android or with the Android input driver. Controller is detected on USB, buts thats is. Overall the image looks good on the first shot, but without a proper GPU driver the N2 / N2+ is not useable for me. Keep me updated i will try every version you plan to release!

[mad_ady]

Ok, me again. I finally figured out why onewire wasn't working. It was a combination of factors:
1. I accidentally swapped GND and signal wires on the sensor (oops!)
2. It seems the newer kernel moved onewire to pin 15, not pin 7 as it was before. I found this out by looking at what gpio the w1 driver was loaded:

Code: Select all

root@odroidn2:/ # cat /sys/kernel/debug/gpio | grep w1
 gpio-483 (                    |w1                  ) in  hi

Now I can read temperatures once more! Yay!

Code: Select all

root@localhost:~# cat /sys/bus/w1/devices/28-0516866e14ff/w1_slave 
90 01 4b 46 7f ff 0c 10 33 : crc=33 YES
90 01 4b 46 7f ff 0c 10 33 t=25000

Now, I only need to find out a reliable way of launching some apps on boot (e.g. kodi, MPD, etc).

[adamforeman]

I have a spare Edimax EW-7833UAC USB 3.0 Wi-Fi adapter and I want to use it on another N2 with Android as its OS. Currently this ROM doesn't recognise the hardware/device.

https://www.edimax.com/edimax/download/ ... ew-7833uac

Is it possible to use the Linux drivers or if there are other WiFi adapters that use the same chipset that drivers can be added?

Many thanks in advance

[zohar]

Hi,
I just replaced my old TV screen with a new Samsung 4K running tizen.
I'm trying to set up the connection to the N2 in a way that the TV remote will control the android.
I manages to get it to work once, but I just cannot make it work again.

in the N2 all the options under HDMI CEC are grayed out.
In the TV there are settings for "Anynet+(HDMI-CEC)" and "input signal plus" I change them both but still the CEC is gray.
Any idea on this?

[adamforeman]

Hi,
I just replaced my old TV screen with a new Samsung 4K running tizen.
I'm trying to set up the connection to the N2 in a way that the TV remote will control the android.
I manages to get it to work once, but I just cannot make it work again.

in the N2 all the options under HDMI CEC are grayed out.
In the TV there are settings for "Anynet+(HDMI-CEC)" and "input signal plus" I change them both but still the CEC is gray.
Any idea on this?

What Version of HDMI cable are you using? The N2 has a HDMI 2.0 video output.

[zohar]

I have no idea which cable version I have...
I found 4 cables in the house, used the one that looked the most expensive and the CEC just started to work!

Some more question on this CEC:
1) Can the TV turn the N2 on/off together with itself?
2) I moved my wireless USB keyboard to the TV, can the CEC transfer the keyboard to the N2?