Mission accomplished:
When going through the initial account setup process, my USB WiFi adapter (which came included with the Nano) wouldn’t work so I was forced to run a line of Ethernet cable from my router into my living room where the Nano was located in order to proceed. However, after that was all done, when perusing through the WiFi settings, the USB WiFi adapter was able find all the available networks nearby, but was unable to connect to any one of them. Why is that?
That usb wifi card worked the last time I tried. I’ll have to pull my 2gb unit back out and try a recent build to see if anything changed. One thing I would note: android doesn’t like hotswap wifi card. So it has to be plugged in on boot and left plugged in. Other than that, it was working when I shipped 18.1.
Ok, fair enough. Thanks
I tested wireless on my nano 2gb today and it was working as expected. The scan list showed during the setup wizard and it connected to my local wifi just fine.
Once you explained earlier that the Nano doesn’t like hotswapping the USB WiFi adapter since it wasn’t plugged in before I started the AndroidTV setup process, I didn’t dispute your explanation.
For the life of me, I can’t figure out how to update recovery. Being that “lineage-18.1-20221104-recovery-porg” is an .img file, wouldn’t you need fastboot in order to flash the recovery file? However, there is no bootloader on the Nano 2GB so how does that work? I even tried booting into recovery using command “adb reboot sideload” and tried using “adb sideload” to flash it out of curiosity, but it failed like I knew it would. On a Windows PC, I confirmed “adb devices” detected my device was connected, but there are no instructions in the wiki that goes over the process regarding how to flash recovery and I rather it not be on outdated version “20220516” if I can help it.
Also, one more last thing: not sure why, but the apps I try to use on the Nano which are mainly retro console emulators don’t have file access as in when I attempt to navigate to the file path, the folders turn out empty even though files are there; I tried granting those apps permissions, but I still can’t see any files nor are they accessible from those apps. Is this a common issue? Because when I use the same emulator apps on a different native AndroidTV device, they are capable of accessing those same files that come up missing on the Nano. Any further help or guidance would be greatly appreciated.
Fastboot isn’t there because this isn’t an android bootloader. Complain to nvidia about that one. The android builds of cboot (the main stage bootloader) do not support the nano, mainly because qspi support is disabled. So… yeah, we get to play cards with the hand we’re dealt. I try to make it as seamless as I can, but there are some things I can’t control. This is one of them.
That said, you can go into the updater app settings and enable updating recovery with ota’s. Then the next time you update, recovery should update with it. But also, recovery really doesn’t have to be the latest and greatest. It doesn’t change much.
The file storage stuff is related to the android version. Apps targeting Android 11 or newer are required to use the newer storage framework, which severely limits what apps can access. That’s outside the scope of device support here, though.
Ok, fair enough. Now I do understand that you vehemently oppose resorting to Magisk as an option to root the Nano device according to your comment “here” so what other alternative would you suggest someone use to root it? Or would it even be viable to put any effort into enabling root access on the device at all?
It depends on what use case as person has for root. Lineage supports adb root, which can be enabled in dev settings. Su and root apps are not supported, but few if any useful apps that need that exist anymore.
Yeah, that’s the thing. I’m only familiar w/ root app options which is how I’ve went a/b performing root on my devices (phones) in the past (e.g., SuperSu, CF-Auto-Root, Magisk, etc.). My use case for the need to root is pertaining to my previously mentioned issue where I had explained that I’m unable to access any files w/in emulator apps I use on the Nano so in response I wanted to use “LSPosed” to enable modules that would affect System Framework in order to force accessiblity to those paths/directories that those apps are restricting.
So how would I be able to perform root if I went a/b it by it being “enabled in dev settings” as you suggested? Would that be “Settings → System → Developer Options, then enable ‘Rooted Debugging’”?
That’s to enable root for adb. So when you run adb you can access things as root. It doesn’t affect apps.
I dunno what to tell you about emulators being unable to access folders. The only things I’ve tested are retroarch and dolphin. I know they’re both able to access /sdcard/Roms and an external sd on various shield devices on Lineage 18.1. Beyond that, you’d have to talk to the app maker. This is something that would affect the shield devices on the latest os version as well, it’s not unique to this device or Lineage.
Based on your experience using LineageOS 18.1, could you do me a favor: download SNES9x from the Google Play store and if you could try to load a compatible rom using the emulator app and tell me whether or not you are capable of being able to access the rom files within the path/directory where they are located. Also, what nightly build version of LineageOS are you using? I am currently on the latest version, 20221104.
Supporting specific apps is out of scope for this thread. I do not have time to check every single app. If it doesn’t work for something I expect to work, like retroarch, then it would warrant more investigation.
Before I do this, is it possible to safely downgrade from LineageOS 18.1 to 17.1 w/o losing data by way of “adb sideload …porg.zip” in recovery?
No, you cannot downgrade without wiping data.
You would have to start by flashing the 17.1 flash package as well. This is discussed earlier in the thread.
Based on the ‘access restriction’ issues I’ve run into since using LineageOS 18.1, I’m considering performing a fresh install of LineageOS 17.1 instead. Could you perhaps provide me w/ a link w/ images of LineageOS 17.1 (porg) that are being hosted.
Never mind, I found 2 sites hosting images, one of them being the Internet Archive.
So I attempted to use the 17.1 flash package found here in order to sideload “lineage-17.1-20220214-nightly-porg-signed” build, but the problem I keep running into is when I attempt to run command “sudo ./flash.sh” I get the following errors in Ubuntu:
./flash.sh: 24: source: not found
./flash.sh: 26: Syntax error: "(" unexpected
Do you happen to know what exactly would be causing this error to occur or if the flash package being utilized works for 17.1. I’d greatly appreciate it.
Sounds like you’re using a distro that doesn’t have bash as the default shell. Try sudo bash flash.sh.
Ok, thanks for that tip. I’ll try that some time later today when I get a break at work.
Just to provide you w/ a status update I can confirm that your workaround method freaking worked. Thank you tremendously. How did you become so very knowledgeable a/b Linux?