=== claydoh_ is now known as claydoh [01:53] hello, i am just look for some help [01:53] i am currently trying the ubuntu 13.10. But it seems i ma missing some of the apps ie. Document viewer [01:53] and way i can add these apps? [01:56] MacLaren, you tries sudo apt-get install [01:56] tried* [01:56] sudo add-apt-repository ppa:ubuntu-touch-coreapps-drivers/collection [01:56] sudo add-apt-repository ppa:ubuntu-touch-coreapps-drivers/daily [01:56] sudo apt-get install touch-coreapps touch-collection [01:56] within Ubuntu the terminal app? in 13.10? [01:56] yup [01:56] don't forget to update obviouusly [01:56] i would like to, but it asks for a root password [01:56] phablet is pw [01:56] i dont know thats -_- [01:57] user password [01:57] ok [01:57] lemme try what you guys said [01:57] there is no root password [02:11] nope,the document viewer and other missing apps are still not there, rebooting now [02:12] i take that back -_- [02:12] reboot did the trick, sorry [02:13] another question, any way to get music/contact on this? [02:26] the music app still dosent work :/ === duflu_ is now known as duflu [02:57] Install ubuntu touch on toro | http://askubuntu.com/q/340268 [03:14] hi [03:14] busy === duflu_ is now known as duflu === Namidairo`bnc is now known as Namidairo [05:40] ugh, can someone please just gather the info you need for sticking Ubuntu on a tf300, instead of linking half a dozen xda-developers posts written by people who don't understand Linux.... [05:40] (I guess I'll do it on the wiki [05:41] also, how easy is it to stick another window manager on ubuntu touch installations ? a tf300 is not handicapped due to lack of a touchpad and keyboard [06:22] ikarus_, i think with mir it would be relatively easy [06:22] it would probably be just a matter of starting mir then starting a window manager [06:23] and getting mir to work on ubuntu touch isn't too hard [06:23] i'd test myself but I'd need to reflash my nexus 4 [06:26] discopig: thing is, no one but Ubuntu uses Mir, so neither do the window managers I want, just get me a good old X11 session [06:33] b [06:33] how does one close/kill an application under Ubuntu touch? [06:33] is there a gui way or do you have to use the terminal? [06:47] Hi guys, just wondering if someone can help me with my nexus 10 ubuntu installation when I try to deploy the image to the device it pops up with (FAILED (remote: signature verification failed!)) [06:47] [06:48] anyone able to help? === smartboyhw_ is now known as smartboyhw [07:16] good morning [07:54] tvoss: hi, I've been testing the location stuff on the weekend [07:55] mzanetti, working? [07:55] tvoss: in general, works quite nicely, but I found 2 issues I think [07:55] mzanetti, shoot [07:55] mzanetti: got sample qml code? [07:55] tvoss: QGeoPositionInfoSource::setInterval() doesn't seem to be working. The source trows positioninfo every half a second. [07:55] mzanetti, yeah, known issue [07:55] mzanetti: the core apps devs could really benefit from some sample code to implement location detection in their apps [07:56] popey, qtlocation examples are a good place to start [07:56] tvoss: the other is that I had lots of crashes when opening the device [07:56] if you can point me at a specific one I can paste into a new qml project I'd appreciate it ☻ [07:56] mzanetti, how do you mean opening the device? [07:57] (and it work) [07:57] tvoss: when creating the QGeoPositionInforSource object [07:57] tvoss: I think it happens when 2 application try to access it at the same time [07:58] mzanetti, hmmm ... there is an open issue where the default source selection is not deterministic. Let me see if it helps when we force it to the ubuntu location provider [07:58] popey: well... its so simple... the doc really should be enough [07:58] yeah, people say that [07:58] and none, _none_ of the examples we ship work [07:58] i filed bugs [07:58] really? [07:58] popey, http://qt.developpez.com/doc/5.0-snapshot/declarative-flickr/ [07:58] yes [07:58] popey, flickr works fo rme [07:59] bug 1214369 [07:59] popey: what I think is wea more important, is to tell people that they should stop the source when its not needed etc [07:59] bug 1214369 in qtlocation-opensource-src (Ubuntu) "Examples in qtlocation5-examples don't work" [Undecided,Confirmed] https://launchpad.net/bugs/1214369 [07:59] bug 1214368 [07:59] Error: Launchpad bug 1214368 could not be found [07:59] bah [07:59] "qml_location_flickr crashed with SIGSEGV in g_type_check_instance()" [07:59] popey: ah... yeah, the location examples only work since last thursday [07:59] popey: the map doesn't crash any more since last weekend, and the positioninfo started working end of last week only [08:00] super! [08:02] thanks chaps, will re-try with an up to date image [08:03] popey: in case you're interested: http://gitorious.org/getmewheels/getmewheels2/source/1442af229209bbaa2ae177c7752cf566b6711d37: [08:04] ooh, nice! [08:04] is that like the Zipcar? [08:04] * mzanetti googles tipcar [08:04] * mzanetti googles zipcar [08:04] hourly rental of cars nearby [08:05] popey: nope. much cooler [08:05] hehe [08:05] popey: there are like 250 cars distributed over the whole city [08:05] popey: you can just jump on and off however you want. leaving the car wherever you want (as long as within the city boundries) [08:06] you dont have to take it back to its home? [08:06] no [08:06] that _is_ cool! [08:06] there would end up being a pile of cars outside my house though :D [08:06] there's enough people that would drive them back to the city center [08:06] and then taking the cab home because they're drunk [08:07] thats what I do at least :D [08:07] hah ☻ [08:07] this app shows you a map with all the cars so can easily find them. and you can book them for half a hour so noone can steal it from you [08:08] omg! they have them in the uk [08:08] yep. in london so far [08:09] it started off here in Ulm 3 years ago... when I wrote the app, only Ulm and Austin-Texas were supported. by now its like 15 cities all over the globe. and new ones are appearing every 2 months or so [08:09] That's great, hadn't heard of it. Ta! === schwuk_away is now known as schwuk [08:35] diwic, hi, do you have a moment please? [08:37] mamenyaka, hi [08:38] diwic, for the n8000, sinks are detected, no sound [08:38] diwic, HiFi file: http://paste.ubuntu.com/6054406/ [08:40] mamenyaka, there were some .state files in there too, right? [08:40] mpt: Hi, happy Monday! Check https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone - should the "Switching from/to" titles be sentence case? [08:40] mamenyaka, in the link you posted a few days ago [08:41] diwic, yes [08:41] diwic, the link: https://code.google.com/p/opensgn/source/browse/data/n8000/usr/share/alsa/ucm/Midas_WM1811/ [08:42] mamenyaka, perhaps you could look at that file, and for every control in there, change it manually to what the state file says [08:42] mamenyaka, and see if that can make sound work [08:43] diwic, can you give me an example? [08:45] mamenyaka, let's try something else. I assume PulseAudio is running on the HiFi profile. Run "alsactl store -f /tmp/speaker.state" [08:45] mamenyaka, then diff /tmp/speaker.state against init.state and see what differences you find [08:45] diwic, okay, give me a moment [08:46] diwic, just downloading the 0902 iamge [08:48] mpt: Moving from #-desktop - are the "two fields" there an entry and confirmation text entry? [08:49] If so, how should we give feedback when the entries don't match? [08:50] diwic, a question regarding my other device with no h2w/state; shouldn't the default state be the speakers? [08:51] mamenyaka, the default is to remember what you have previously [08:51] and if there is no previous? [08:51] s/have/had [08:51] mamenyaka, then it should pick the one with highest priority [08:52] can I change the priority? [08:52] it showed as I remember 100 for both === chriadam is now known as chriadam|away [08:53] mamenyaka, try adding "PlaybackPriority 200" in the "Value" section for speakers [08:53] mamenyaka, just below "PlaybackChannels" [08:54] diwic, thank you, I will try it later, now installing for the n8000 [09:14] diwic, alsactl is in which package? [09:14] mamenyaka, alsa-utils, it is pre-installed [09:15] ogra_, thank you, but it doesn't show up [09:15] oh, sorry [09:15] it doesn't show up as phablet user [09:16] ?? [09:16] $ alsactl [09:16] -su: alsactl: command not found [09:16] surely does ... unless oyu messed up your path [09:16] dont ever use su [09:16] oh now [09:16] sudo -u phablet -i [09:16] oh [09:16] thank you [09:17] cjwatson, do you know whats the reason that we dont adjust the path and environment with su ? [09:18] diwic, no speaker.state file [09:19] ogra_: use "su -" rather than su [09:19] mamenyaka, weird, did it perhaps save /var/lib/alsa/asound.state [09:19] defined interface since forever [09:19] diwic, empty dir [09:19] I used su - phablet [09:20] cjwatson, right, but why dont we just use the proper user PATH that we use everywhere else ? (sudo and login set it properly) [09:20] that's odd, it should, I'll have a look in a bit [09:20] without having to use a switch [09:20] mamenyaka, any errors? [09:20] ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [09:20] ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games [09:20] from login.defs [09:20] diwic, paplay runs fine [09:21] err - that's a regression, I'm sure [09:21] k, i thought there was probably a decision i missed :) [09:21] https://wiki.ubuntu.com/OneTruePath [09:21] yeah [09:21] perhaps su has lost pam_env or something [09:22] mamenyaka, it runs fine on the N4 under the phablet user [09:22] mamenyaka, did you run exactly "alsactl store -f /tmp/speaker.state" ? [09:23] ok, for those here who care about PPAs, I think we have now actually managed to patch things up so that the build farm will spend less time at half capacity [09:23] mamenyaka, no need to su to anything else [09:23] diwic, I can try running it, but I have no speaker.state file, checked tmp [09:23] so the current hideous queue should manage to drain [09:23] mamenyaka, it will create the speaker.state file [09:23] yay [09:23] nono, that su thing was only for switching to phablet, now I know the right way to do that [09:23] diwic, [09:23] diwic, okay [09:24] that I didn't know, sorry [09:24] so now I compare [09:24] mamenyaka, compare speaker.state with init.state you found on the opensgn website [09:25] diwic, doing that right now [09:26] diwic, quite a lot of differences [09:29] diwic, if you are interested, here's the output: http://paste.ubuntu.com/6054522/ [09:31] mamenyaka, always run diff with the -u switch [09:31] mamenyaka, then it becomes more readable :-) [09:31] diwic, I just used Meld to compare, but thanks :) [09:32] diwic, yes, this is more friendly: http://paste.ubuntu.com/6054528/ [09:33] mamenyaka, e g, "Speaker Mixer Volume" should probably be turned up, since it is '3' on init.state and '0' on speaker.state? [09:33] mamenyaka, and 'Speaker Reference' [09:33] mamenyaka, and 'DAC1 Switch' and 'DAC2 Switch' [09:34] mamenyaka, and 'SPKR DAC2 Switch' [09:35] diwic, where do I need to edit? [09:35] mamenyaka, and 'SPKR DAC1 Switch' and 'SPKL DAC1 Switch' and 'SPKL DAC2 Switch' [09:35] or how do I overwrite it? [09:35] with my init.state === jamesh_ is now known as jamesh [09:36] mamenyaka, either in EnableSequence for Speaker or in the EnableSequence for the HiFi verb, depending on whether you need it for headphones too, or not [09:37] diwic, what is the command to call the init.state? [09:38] mamenyaka, "alsactl restore -f /path/to/init.state" [09:39] diwic, should I worry? alsactl: set_control:1325: failed to obtain info for control #150 (No such file or directory) [09:40] diwic, but still no sound [09:41] mamenyaka, okay, you can take a new state (alsactl store -f /tmp/foo.state) to verify that the values changed to what you expected [09:44] diwic, no, looks like still the same [09:45] diwic, this is what I get on restore: http://paste.ubuntu.com/6054567/ [09:46] diwic, the diff: http://paste.ubuntu.com/6054571/ === vrruiz_ is now known as rvr [09:54] mamenyaka, so, hopefully it's only about setting up the mixer correctly, but we can't know for sure. You can use amixer, alsamixer and alsactl to get and set the current mixer values until you get something working. [09:55] mamenyaka, if you need to do something more than just setting up the mixer, that would probably be hiding in the audio HAL code, if you have access to that. [09:55] diwic, thank you, I will try my best [09:56] ogra_: hi. One thing I ran into when getting mediascanner running on the phone is that we don't support XDG user dirs out of the box. I filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1219348 about it, which is hopefully the right place [09:56] Launchpad bug 1219348 in ubuntu-touch-session (Ubuntu) "Image doesn't support XDG User DIrs spec" [Undecided,New] [09:56] diwic, with amixer, do I need to manually set everything_ [09:56] ? [09:56] mamenyaka, once you get things working, you should modify the UCM files to do the same. [09:56] jamesh, if your service runs as the user you should get the dirs i think [09:57] seb128, ^^^ ? [09:58] ogra_: there was no ~/.config/user-dirs.dirs file, so it wasn't working. [09:58] ogra_, jamesh: in the latest discussions it was not clear they wanted to support customisable/translatables dirs in touch [09:58] that adds complexity and overhead [09:58] especially for the app isolation/apparmor [09:58] who does that discussion ? [09:58] lool jdstrand tvoss [09:59] oSoMoN: hello. any idea what could be wrong on the maguro tests failing? [09:59] i think the mediascanner part is rather a system service, isnt it ?? [09:59] seb128: if we don't support customisable user dirs, we could still provide the config file pointing at the non-translated dirs [09:59] jamesh, that would work for me [09:59] asac: hi, I’m investigating [09:59] ogra_, it is, or more precisely, a session service [09:59] that way code that is written against the spec would still work [09:59] tvoss, ah, thanks [09:59] asac: mmm, looks like they didn’t run at all [10:00] oSoMoN: webbrowser didnt [10:00] the rest did [10:00] http://reports.qa.ubuntu.com/smokeng/saucy/image/3906/camera-app-autopilot/329637/ [10:00] camera [10:00] something fishy with a PID [10:00] but had failures it didnt have on mako [10:00] oSoMoN: we will retry webbrowser [10:00] psivaa: can you do that? [10:00] asac: tests for today's image have started to run [10:01] asac: i'll re-run webbrowser if today's one fails too [10:01] psivaa: ok [10:03] asac: all the failing tests for camera-app seem to have this error message: Camera error: "Unable to connect to camera" [10:04] ogra_: ^^ that feels like us? [10:04] ogra_: did we change anything? when was the last test success there? [10:05] asac, no idea when the last success was there, but rsalveti changed some bots on the android side iirc [10:05] along with the switch to pulse [10:05] s/bots/bits/ [10:05] Morning all [10:07] hello [10:07] where can check support CPU list [10:11] dholbach: it's nice to be able to install new packages that were uploaded since friday :-) [10:11] I tried the lighbulb game [10:11] works on read-only image [10:11] there are a bunch of small bugs in the user experience, but it works [10:11] kokoye2007, cortex A9 and above CPUs are supported by ubuntu touch [10:12] yey i have A9 [10:12] (technically you can run on A8 too, but single core wont be fun to use) [10:16] thx ogra_ [10:16] MTK6589T is can't ? [10:20] nerochiaro: I filed https://bugs.launchpad.net/ubuntu-ui-extras/+bug/1219765, can you please have a look? [10:20] Launchpad bug 1219765 in Ubuntu UI Toolkit Extras "qtdeclarative5-ubuntu-ui-extras0.1 doesn’t install assets" [Undecided,New] [10:21] oSoMoN: looking === mpt_ is now known as mpt [10:22] nerochiaro: also filed https://bugs.launchpad.net/ubuntu-ui-extras/+bug/1219766 [10:22] Launchpad bug 1219766 in Ubuntu UI Toolkit Extras "Share.qml: Binding loop detected for property "height"" [Undecided,New] [10:23] oSoMoN: the first one is a good catch. the second one i noticed too but from looking into it for a while but IIRC could not find where the loop came from [10:23] nerochiaro: at least you can confirm it, right? [10:23] oSoMoN: yeah [10:23] thanks [10:26] hi guys, I've been testing ubuntu touch for a bit on my nexus 4 and last night the battery was almost empty so overnight my phone ran out of juice. I found it shut down this morning but now it doesn't do anything. If I try to boot the screen just stays black. I cannot even get into the bootloader. Do you guys have any idea what might by causing this? Thanks [10:27] jantjeman, iirc you need to charge it for a while, then unplug the cable and hold all three buttons for 1min (not less !) to get it out of that state [10:28] ogra, thank you, I will try that right away! [10:28] and also always use the wall charger [10:28] a USB port will only provide 500mA, thats as much as the device draws [10:29] (or nearly at least) [10:31] OK, I'm going to charge it for a while with the charger, it's always been plugged in to the computer. I'll get back to you if it works out OK. [10:34] jantjeman: I've seen that too, needs a big fat charge [10:35] popey: OK, I'll leave it plugged in a couple of hours then :) [10:39] diwic, how to set up priority for speaker to be greater then headset for apq... ? [10:40] mamenyaka, try adding "PlaybackPriority 200" in the "Value" section for speakers [10:40] mamenyaka, just below "PlaybackChannels" [10:40] ogra_, wanna upload another alsa-lib ? [10:41] Value { [10:41] PlaybackChannels "2" [10:41] PlaybackPriority 200 [10:41] } [10:41] right [10:41] or should it be "200" ? [10:41] "200" probably [10:41] I think both is okay actually [10:42] diwic, a little later, yes [10:43] ogra_, yeah, no hurries. Just a little higher gain on the N4 speaker and N7 fixup [10:43] so nothing urgent [10:43] diwic, great! thank you! [10:45] diwic, can I MR this change? [10:45] diwic, well, Music app is not working, when I pless play, it just ends in a fraction of a second [10:46] diwic, but videos work with sound [10:51] mamenyaka, hmm, yes, I think we could merge an increase in priority [10:51] for speaker [10:51] mamenyaka, at least for now [10:52] diwic, could you do it? [10:52] yes [10:53] diwic, thank you! do you know anything about the Music app? [10:53] mamenyaka, it works here, I tested it this morning (N4, 0901.1 image) [10:53] diwic, logcat shows nothing [10:54] diwic, it worked like a week ago with the same file [10:54] diwic, any way I could degub? [10:54] mamenyaka, mp3 files do not work by default [10:54] oh [10:54] it isn't an mp3 file? [10:54] it's an mp3 file [10:54] that explains [10:54] try ogg [10:54] patents and stuff [10:56] ogg working fine, thank you [10:57] hello [10:58] ogra_, do you have any idea why the sintel video laggs like hell, but other work fine? [10:58] because that coded runs software rendered atm [10:58] will change this week once the new gstreamer stuff lands [10:58] *codec [11:00] ogra_, great! [11:00] diwic, thank you for all your help! [11:01] anyone use eclipse? [11:02] mamenyaka, what's the name of the device with the apq sound card? [11:02] Sony Xperia Tablet Z [11:03] mamenyaka, ok, playbackprioirty merge is in, will be in next alsa-lib upload [11:03] diwic, thank you [11:03] yw [11:04] will there be a 09-02.1 image? [11:04] at 8pm UTC, yes [11:05] (unless asac cracks the whip to have it manually built earlier) [11:07] asac: oSoMoN: ogra_: the webbrowser tests in maguro are still failing. http://reports.qa.ubuntu.com/smokeng/saucy/image/3916/webbrowser-app-autopilot/ [11:07] i'm rerunning it again but this failure seems consistent [11:08] ogra_, thank you, I will test the change, just to be sure [11:08] psivaa: they’re not failing, they’re not even running… [11:08] anyone watching? http://www.youtube.com/watch?v=X2qOhDloy2w [11:10] gusch, nerochiaro: would one of you be available for a trivial review? https://code.launchpad.net/~osomon/webbrowser-app/increase-test-timeout/+merge/183425 [11:11] oSoMoN: ok [11:11] oSoMoN: the are running in fact but the results are not getting collected for some reason: https://jenkins.qa.ubuntu.com/job/saucy-touch-maguro-smoke-webbrowser-app-autopilot/108/consoleText [11:11] lool, it is :) [11:11] psivaa, funnily it passed on the last mako run [11:12] ogra_: not only in the last one, on mako it was passing even before. the failure is only seen in maguro [11:13] psivaa, ogra_: and they consistently pass locally on my maguro device [11:13] oSoMoN: it looks good to me, but I am not really sure what happens if the environment gets even slower [11:13] oSoMoN: sounds like keeping things together with duct tape ;) [11:14] nerochiaro: well then every single autopilot test out there will fail, for all applications :) [11:14] oSoMoN: so why your app needs a longer timeout and the others don't ? [11:15] shouldn't they all fail already ? [11:15] nerochiaro: because one of the tests requests loading a page that takes 8 seconds to load (by design), so that leaves only 2 seconds for the rest of the test to succeed, and in slow environments that might be a bit to short [11:16] nerochiaro: with this change, the test now has 12 seconds, more than enough [11:17] oSoMoN: excellent. approved [11:19] rachelliu: good morning, can I ask you a question about the camera app ? or should I refer to another designer for that ? [11:19] nerochiaro: hi! christina is working on the camera app [11:19] nerochiaro: what's the question? I can see if I have a quick answer! [11:19] hey nerochiaro :) [11:20] nerochiaro, how can i help? [11:20] christina: rachelliu: i spent some time looking into this bug https://bugs.launchpad.net/camera-app/+bug/1129132 but it seems that it's really hard to do what is requested there. so i was wondering if there was an alternative way [11:20] Launchpad bug 1129132 in camera-app "[camera] Fade out / in chrome between orientations" [Medium,Confirmed] [11:21] nerochiaro, i will take a look [11:21] christina: thank you :) [11:21] nerochiaro, as im picking this app up now, is this when you rotate the chrome disappears and then re-appear? [11:21] christina: yes, exactly [11:22] nerochiaro, ok :) [11:23] nerochiaro, do the chromes need to rotate to fit into landscape too? [11:23] for example [11:23] or stay the same? [11:24] on my samsung phone the UI elements stay in tehir position but the icons rotate to match the screen rotation [11:24] (in android) [11:24] christina: the icons inside the toolbar rotate, everything else just shifts between the two short edges [11:24] (top/bottom) [11:25] nerochiaro, would you want the bar to move to the bottom in landscape too ? [11:26] nerochiaro, it seems weird to have the zoom in/zoom out not part of the toolbar as it is in portrait [11:26] i thnk that makes pressing the shutter button a lot harder [11:26] ogra_: the yes, it is by design that none of the bars move to the right/left sides. they always stay either at top or at bottom side [11:27] well, in case of the cameria i think it makes sense to keep the shutter at the side [11:27] (in landscape that is) [11:27] christina: it was designed that way to make it easier to use, because when the phone is in landscape it is normally held with two hands [11:27] christina: ogra_: so basically with one hand you operate the zoom and with the other the shutter [11:28] yeah [11:28] i think that makes sense [11:28] nerochiaro, have we tried just making the toolbars stay visible when we switch? we can test if moving from bottom to top/bottom between orientation is too much [11:29] christina: you mean trying to have the bars visibly slide around the screen ? [11:29] christina: that should be doable, i'll give it a shot [11:29] nerochiaro, yes [11:30] christina: ok, i'll try and let you know [11:30] * ogra_ doesnt think thats a good idea [11:30] nerochiaro, and if we think when rotating is too much distortion we can try something else then [11:30] christina: sounds good. thanks [11:30] unlesss you probably have the shutter button in a corner [11:30] ogra_: why not ? [11:31] rsalveti, last week you asked me to look into the volume hotkeys. I'm not sure how that's expected to work on the phone. On the desktop, it passes through gnome-settings-daemon, which is not running on the phone. [11:31] nerochiaro, well, currently the shutter button stays at the same place on the screen ... physically ... if you start flipping the bar it will change position ... you wont find it blindly while atm you can (roughly) [11:32] nerochiaro, cool. let me know how you go then! [11:32] i think it iss easier if the one really iportant button does not change its physical position in this case [11:33] (i dont care about settings and the like at all, if i need to use these i'm not taking a snapshot, in snapshot mode i would like to trust my finger memory for quick actions) [11:33] ogra_: it will have to change position when you rotate the phone 180 [11:33] ogra_, can you get ubuntu-touch-settings added to the touch image? [11:34] seb128, yep [11:34] (you can too, as every core dev can :) ) [11:34] ogra_: sorry, i meant when you rotate between landscape and portrait [11:34] ogra_, thanks ;-) [11:34] ogra_: basically: in landscape the button is always on the right of the screen. in portrait it is always on the bottom of the screen. [11:34] ogra_, (yeah, I just don't have a checkout/didn't do it for a while, if it's easy for you to do I would appreciate you doing it) [11:34] nerochiaro, well, today the button stays where it is ... same position on the screen, no matter how you rotate [11:35] np [11:35] ogra_: i think we're saying the same thing [11:35] nerochiaro, right, it is always Xmm from the bottom of the case and in the center of the screen ... physicallz [11:35] k [11:35] ogra_: yeah, so you can always find it blind [11:35] right [11:36]