Yeah, Alsamixer hangs because there's a process run by systemd at boot time that tries to restore the state (sound levels) of each channel to the value they had before shutting off. The problem is that the process fails and it hangs the whole audio system.I've found pulseaudio hanging as well, but I can't seem to remove it because it's integrated with GNome. As far as mixer apps, none of them seem to work. If I run alsamixer from the console I can't change anything because it uses Fkeys for changing values which are not mapped on the TF300T. I was able to find the F6 key but I can't select the file1 [tegracodec ]: tegra-codec - tegra-codec.
Any help would be greatly appreciated.
Edit: Also tried alsamixer -c1 and it hangs
Even the Nexus 7 with Ubuntu? OMG we suck hard!! how can Canonical with their hundreds of developers (many of them under a salary) beat us??Does anybody know what is missing to get suspend to work? It's the only thing that stops me from taking the device with me every day... even the Nexus 7 with Ubuntu is able to suspend.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Whats your problem, Mr. Facepalm? Any problem with non-native speakers? Or just trolling around? What I meant wasn't to complain, this was just a normal question to me. Have been searching for a hack to get suspend to work for some days now...Even the Nexus 7 with Ubuntu? OMG we suck hard!! how can Canonical with their hundreds of developers (many of them under a salary) beat us??
(Couldn't find :facepalm: emoticon)
Arch for the Transformer Pad is being ported by one dev only (cb22) so if you ask me, what we need is more people who are willing to try to make things work, contribute to this thread with whatever they did to make their Arch better and last but not least, don't complain or give anything for granted.
Cheers
Thanks for the leading me in this direction. Sadly though after creating the symbolic links using ln -s for both alsa-restore and alsa-store, alsamixer -c1still hangs on me and gives me no way to setup the sound card. One thing that does work for me now is the Shutdown and Restart.Yeah, Alsamixer hangs because there's a process run by systemd at boot time that tries to restore the state (sound levels) of each channel to the value they had before shutting off. The problem is that the process fails and it hangs the whole audio system.
What I did was disable the store and restore of those values, by "masking" alsa store and alsa restore in systemd. Google for "mask systemd service". What you actually do is create a symlink pointing to null for those services, so when they get called no code is actually executed.
Look for more info on systemd on internet while checking out /etc/systemd and /lib/systemd.
I wouldn't know how to help you with pulse as I'm using xfce without it.
If You ask for TF700 ubuntu on TF300* lock http://forum.xda-developers.com/showpost.php?p=34655444&postcount=1What tutorial did you use? What is your current configuration?
Suspend is an issue due to wakelocks at the moment. Since we are running an Android kernel, they still exist, and are a pain in the behind. Ubuntu's kernel doesn't have them compiled in (to the best of my knowledge, I could be wrong...) And I was playing around with a little hack to disable them via a proc interface.Whats your problem, Mr. Facepalm? Any problem with non-native speakers? Or just trolling around? What I meant wasn't to complain, this was just a normal question to me. Have been searching for a hack to get suspend to work for some days now...
And with "even the nexus 7" I meant that even the nexus 7 is no native Linux device, so this should be doable.
And if you don't know how facepalm, you can take this for the meantime: m(
Pretty much the same for me, pm-suspend does suspend, however power button attempts to wake (screen flashes) but fails.Suspend is an issue due to wakelocks at the moment. Since we are running an Android kernel, they still exist, and are a pain in the behind. Ubuntu's kernel doesn't have them compiled in (to the best of my knowledge, I could be wrong...) And I was playing around with a little hack to disable them via a proc interface.
Someone mentioned they had suspend and resume working fine over at the bug report - https://bitbucket.org/cb22/archlinuxarm-tf300/issue/3/no-suspend-support
However, for me it results in a "suspend loop". There's an easy way to test this - simply su to root, make sure you've saved everything and ran sync a few times, then run pm-suspend. If the tablet suspends, and pressing the power button turns it on, great - let me know.
Ubuntu for tablets (developer preview) is about to be made available for Nexus 7 http://www.webupd8.org/2013/02/canonical-unveils-new-ubuntu-tablet.htmlI heave installed TF700 Ubuntu on TF300T
working ... need testing fixing ....
Definitely, Arch is by far the ****tiest OS I have ever used. Way too unstable and their packages, at least the ARM V7 applications anyway, most are returning 404 errors. Not hating on cb22 though, this is still better than nothing. Ubuntu would be amazing!Ubuntu for tablets (developer preview) is about to be made available for Nexus 7 http://www.webupd8.org/2013/02/canonical-unveils-new-ubuntu-tablet.html
Hope someone can port it to our TF300.
Sorry for the OT
Hmm. A good start would be disabling wakelock support in the kernel (this will break Android) and seeing if that allows us to get suspend / resume. After that, we could look at maybe having a parameter that enables / disables checking of wakelocks based on a setting in /sys / /proc or wherever.The device is getting in suspended loop, it seems that the Android and Linux suspend are in conflict, I have made some video and photos of kernel messages when running pm-suspend:
https://dl.dropbox.com/u/1664131/VID_20130219_215442.m4v
https://dl.dropbox.com/u/1664131/IMG_20130219_215610.jpg
https://dl.dropbox.com/u/1664131/IMG_20130219_215626.jpg
https://dl.dropbox.com/u/1664131/IMG_20130219_215635.jpg
Maybe this can help, cb22 do you know with module/part of kernel code can cause this problem? I think making in it an bool, give if before this code, and exporting this bool as module parameter can help us, I already did this many times, but I need to know with part of code can made this problem.
Sorry, but I have no interest in porting Ubuntu. The "ground work" is mostly done, if someone is interested in getting Ubuntu running, it really wouldn't be that much effort. However, that person is not going to be me.Definitely, Arch is by far the ****tiest OS I have ever used. Way too unstable and their packages, at least the ARM V7 applications anyway, most are returning 404 errors. Not hating on cb22 though, this is still better than nothing. Ubuntu would be amazing!
Before you go around bashing a specific OS, might want to make sure first that it's the OS's fault, and that the alternative won't/doesn't experience a similar thing.Definitely, Arch is by far the ****tiest OS I have ever used. Way too unstable and their packages, at least the ARM V7 applications anyway, most are returning 404 errors. Not hating on cb22 though, this is still better than nothing. Ubuntu would be amazing!
Long live Arch!Sorry, but I have no interest in porting Ubuntu. The "ground work" is mostly done, if someone is interested in getting Ubuntu running, it really wouldn't be that much effort. However, that person is not going to be me.
Also, quite a few of the crashes / instabilities (such as X dying) are due to interactions between the Tegra userspace and kernel drivers. Moving to Ubuntu won't help with that.
I actually just tried this, and it works! A bit more digging will be needed to get this working with a dualboot solution - but it should definitely be doable.Hmm. A good start would be disabling wakelock support in the kernel (this will break Android) and seeing if that allows us to get suspend / resume. After that, we could look at maybe having a parameter that enables / disables checking of wakelocks based on a setting in /sys / /proc or wherever.