[Nexus 7 General] Mgruben:
Just Made an Arch-Nexus :D

Let me start by saying that you've done excellent work, ylixir, on this forum and on the google doc :good:

Some observations:

the arch*.mrom, oddly, downloads on the nexus as a .zip file. If you can access a root terminal on the device (or through adb), simply rename .zip to .mrom and carry on with the guide.

# mv /sdcard/Download/arch_20130626.{zip,mrom}

I found that when I started connectbt.service (which launches connect_bt.sh), and when my bluetooth keyboard is off, a hidd --connect [address] command made my wifi disconnect, every time (whether NetworkManager or the Static IP / WPAsupplicant script from the ArchWiki: https://wiki.archlinux.org/index.php/Wireless_network_configuration#Systemd_with_wpa_supplicant_and_static_IP)

My solution to this was to install acpid and edit /etc/acpi/handler.sh so that a single (short!) power button executes sh /usr/bin/connect_bt1.sh, which only defines the pre-determined bluetooth keyboard's address variable and issues the hidd --connect [address] command once.​

The alsa-utils package, through the use of the ncurses alsamixer, was able to get my sound working on LXDE

The monitorix package works wonderfully for allowing you to see how the Nexus is behaving over time, if you're planning on setting and forgetting the tablet somewhere.

I also wondered a few things:

If anyone has been able to turn the screen completely off. I am able to change brightness by editing /sys/class/backlight/pwm-backlight/brightness as root, but even setting the value in that file to 0 doesn't turn off the Nexus' backlight (as it does for the corresponding brightness file on the Arch laptop I'm writing this post from).

Update: setterm -blank 1 -powersave powerdown -powerdown 2 did not successfully turn the screen off, although there was a noticeable screen blip 2 minutes after the terminal blanked.​

If there is a package similar to acpi that allows me to see the battery status of the Nexus (acpi -b itself always reports battery at 0%, and I don't know of another way to check if the Nexus is about to die)

It looks like /sys/class/power_supply/battery/uevent contains a lot of great info, but that the charge_full and charge_full_design attributes are missing, which I would guess is preventing acpi -b from calculating or displaying a charged percentage

Update: as if on queue, my ArchNexus died this morning while plugged into the wall, and the charging signals I'm getting seem to indicate that the battery needs to charge before I can turn it back on again. Well that or I totally bricked it, but I'm going to optimistically assume the former until I prove that hypothesis wrong. After leaving the off Nexus plugged into the wall for an hour, I successfully turned it on and booted into Kali Nethunter, which indicated that the device was at 14% battery. Either some setting I changed in Arch made the power drain too great (or stopped charging), or the ArchNexus actually hasn't been charging for a few days while running, which seem too impressive to me to be the case.

Although it didn't indicate much, acpi -b did tell me that the battery was "charging" when I checked a day before battery failure.

Update 2: I let the Nexus charge to 100% on Kali Nethunter while I went to the MetroPCS store to acquire a (hopefully stock) wall outlet charger for it (was using the iPad brick with the Asus microUSB cable, which the internet tells me is a no-no). Currently, acpi -V indicates that the battery is "Full," although I don't know how acpi knows what full is.

I've also set up a batterypeek service and timer to cat charge_now to a log file every 15 minutes, so I'll know in the morning if there's much of a fluctuation in the charge​

If there is a package similar to lm_sensors that allows me to see temperature info of the Nexus (note: don't let lm_sensors probe your nexus 7 2012! It will spit out a bunch of text and cause your system to reboot)

(probably outside the scope of this thread) If Arch linux allows for the use of a powered y-OTG cable for charging the Nexus while connecting it to, say, an external USB hard drive, or if I'm misunderstanding the 'kernel' references on websites describing how powered y-OTG cables work.