Recent content by timothyb89

I see that too. I've found that restarting the networkmanager service can help when SSIDs stop showing up: # /etc/rc.d/networkmanager restart It still has trouble connecting a lot, though I suspect half of that it the unstable wireless at my university. It gives me trouble even on stock or...

In theory you should be able to install a proper display manager without too many issues: # pacman -S lightdm lightdm-gtk-greeter # systemctl enable lightdm ...though when I tried this the DM would never actually be run. I was able to run it manually over SSH without issues (both lightdm and...

first decAobs I've been running the ArchLinux port for a few days now as my daily driver, more or less. It has some kinks yet but if you know what you're doing productivity is a ton higher. The Arch repos don't have libreoffice for whatever reason but google docs works fantastically...

I don't think sleep/suspend/hibernate is implemented at all quite yet. The backlight seems to turn off completely when the screen times out though so you can fake having a low power mode, though obviously true sleep would be nice. As for volume control, use pavucontrol. You may need to install...

Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc) The file runs the following by default: exec startxfce4 --with-ck-launch You can change everything after `exec` to the script for...

Blackbean is one choice. Though it's appears to be based on CM so it probably won't run on the Jellybean bootloader quite yet. A quick list of stock-based ROMs you could use arranged roughly in order of their popularity: Hydro (Jellybean) CleanROM - this is what I'm running right now...

That depends on how you use your tablet. For most uses the stock ROM is what you want. It generally offers a more stable experience, but some of the extra features of Cyanogen may make it worth it. One of the main reasons I use Cyanogen is to have a mostly AOSP system and remove manufacturer...

I was in roughly the same situation but needed to make a few minor adjustments: I couldn't transfer the file to /system/bin directly (adb complained about permissions). I also was on a completely stock rom with no backup of any root binaries - my device is unlocked and I flashed the...

I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well. The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.