[02:24] <hasan> Hi
[02:24] <hasan> I need your help!!
[02:27] <hasan> My E45 touch working wrong!!
[02:31] <learnbsd> hasan: ?  going to need more than 'working wrong'
[02:32] <hasan> I try reset my phone but in the wizard after reset when I click Next, the page back to older page!!
[02:34] <hasan> When I want moving app scope, apps that I won't touched has been opened!
[07:46] <Yinlux> Hi folks!
[07:47] <Yinlux> anyone here to help me with a bluetth prob
[07:47] <Yinlux> ?
[08:16] <Yinlux> Any bluetooth specialist here?
[08:16] <jgdx> Yinlux, you want to talk to koza, but not sure when he's online
[08:16] <Vincent_Chang> Hello there, I am new to this channel. I would like to ask if ubuntu phone can be used as TV platform ?
[08:16] <Yinlux> ok thx jgdx!
[08:17] <jgdx> Vincent_Chang, http://www.mythbuntu.org/ maybe? Idk
[08:18] <mcphail> Vincent_Chang: no, it can't. (At least, not in a way you'd be happy.)
[08:19] <Vincent_Chang> I am wondering if it supports IR or dpad interface.
[08:23] <Vincent_Chang> From the ubuntu official website, it supprots bluetooth hid devices like keyboard or month. So I resume it should be easy to support IR as well.
[08:33] <saidinesh5> Vincent_Chang: why not just use openelec, it supports both IR and dpad interfaces afaik
[08:34] <saidinesh5> guys , the phablet repos are still/again down. they were up for a brief while yesterday but went down again...
[08:35] <mcphail> Vincent_Chang: regardless of interface, Ubuntu Touch is not going to deliver much content for a TV service
[08:37] <Vincent_Chang> When you say interfaces, is it something related to DVB/ATSC/ISDB/DTMB ?
[08:40] <Vincent_Chang> openlec looks great
[08:40] <popey> Hm. My pro 5 is in a unity8 crash loop. Anyone else seen this with yesterdays rc-proposed OTA?
[08:40] <popey> unity8-dash seems to be constantly crashing
[08:41] <jgdx> popey, what rev is that?
[08:41] <Vincent_Chang> does it support TV framewoek Aka Android TV Input Manager
[08:42] <jgdx> popey, turbo was fine for me on 171, haven't tested 172
[08:42] <popey> jgdx: hard to say, I can barely get into it
[08:43] <popey> as soon as it starts, unity dies and apport eats the phone alive
[08:43] <popey> version version: 170
[08:43] <popey> think I might ubuntu-device-flash it
[08:44] <mcphail> popey: I updated my e4.5 last night. Got a black screen after update but all working after long press of power button
[08:44] <brunch875> mcphail: on rc-proposed?
[08:45] <popey> reboot isn't fixing this
[08:45] <brunch875> I have a krillin on proposed and it hasn't happened to me
[08:46] <mcphail> brunch875: yes
[08:46] <mcphail> popey: I haven't applied the update which was offered this morning
[08:46] <brunch875> I did experience a long wait on BQ logo
[08:47] <brunch875> which was about 1 minute. But then it rebooted itself
[09:00] <popey> adb reboot recover 'fixed' it
[09:00] <popey> and applied 171
[11:19] <divis1969> Hi, can someone clarify whether ubuntu touch can be ported as an ARM 64bit ?
[11:20] <lotuspsychje> divis1969: perhaps look at the porting guide, or the XDA forums?
[11:22] <mcphail> divis1969: I'm not sure any 64 bit ports are working yet. I think the tablet (which is a 32 bit device) runs a 32 bit image, but this might have changed
[11:22] <mcphail> *64 bit device
[11:22] <popey> Linux ubuntu-phablet 3.10.100-user-01771-g301b04f #1 SMP PREEMPT Wed Aug 24 03:30:19 UTC 2016 aarch64 aarch64 aarch64 GNU/Linux
[11:22] <popey> thats from a meizu pro 5 - a 64-bit kernel
[11:22] <mcphail> nice
[11:23] <mcphail> popey: is the tablet 64bit?
[11:23] <divis1969> what about executables in /system/bin? are those also aarch64?
[11:24] <popey> bq m10 is a 64-bit kernel too
[11:24] <popey> phablet@ubuntu-phablet:/system/bin$ file wpa_supplicant
[11:24] <popey> wpa_supplicant: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked (uses shared libs), stripped
[11:24] <popey> ^ pro 5
[11:25] <mcphail> Cool. I vaguely remember the tablet running as 32 bit at the start, but I might be mistaken
[11:25] <popey> i think we knew it was 64bit, but we didnt have a 64-bit image for it initially
[11:25] <popey> john-mcaleely knows more
[11:26] <divis1969> where is this device repository can be found?
[11:30] <lotuspsychje> divis1969: perhaps you should start with naming your device/type you want a port for?
[11:31] <divis1969> meizu m2 mini
[11:32] <popey> https://github.com/meizuosc/m576
[11:32] <popey> is that what you're after?
[11:35]  * lotuspsychje is curious about the OTA13
[11:35] <divis1969> that is the kernel only. I'm talking about something like device/meizu/pro5 where all that android staff (make files) for this device is located typically
[11:37] <popey> hm, I am sorry, i don't know where that lives
[11:38] <popey> john-mcaleely: may know
[11:38] <ogra_> i dont think these are available at all given they are under locked down licensing
[11:39] <divis1969> Is it possible that the kernel and some binaries from OEM are 64bit but ubuntu files (from http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/) are 32bit ?
[11:41] <divis1969> popey: could you please check for some other file (perhaps from /usr/bin) since wpa_supplicant seem built by android build system and can be provided by OEM?
[11:42] <popey> divis1969: sure, name any file
[11:44] <divis1969> I'm new to this ubuntu poring and do not know which files are in that xxx-preinstalled-touch-armhf.tar.gz
[11:44] <popey> -rwxr-xr-x 2 root root    116476 Nov  9  2015 zipinfo
[11:44] <popey> phablet@ubuntu-phablet:/usr/bin$ file zipinfo
[11:44] <popey> zipinfo: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=49dda1dc48f844e515eca477d300f9dda6336bf1, stripped
[11:45] <popey> so looks like 32-bit userspace
[11:45] <popey> \o/ confirmed bug 1611349
[11:45] <popey> bfiller: ^ one for you I guess :)
[11:45] <lotuspsychje> http://forum.xda-developers.com/ubuntu-touch
[11:47] <divis1969> popey: thanks a lot!
[11:47] <popey> divis1969: no problem
[11:50] <divis1969> popey: one more question. could you please check /system/bin for linkers? are there 2 (32 and 64)? I suppose those should be named linker32 and linker64 and perhaps a link linker to one of them
[11:50] <ogra_> popey, that will be hard to fix unless we change to not use vfat on the SD ;)
[11:50] <ogra_> (your camera bug)
[11:55] <popey> ogra_: why do you mention vfat?
[11:56] <popey> (read my comment)
[11:56] <popey> divis1969: phablet@ubuntu-phablet:/system/bin$ file linker
[11:56] <popey> linker: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), not stripped
[11:56] <popey> phablet@ubuntu-phablet:/system/bin$ file linker64
[11:56] <popey> linker64: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, not stripped
[11:57] <ogra_> popey, because the camera is allowed to write to the SD ... vfat has a 2G limit ...  32bit-systems use signed ints as position-parameters in fseek() ... on 32-bit architecture, that would yield a max filesize of 2^31 = 2GB
[11:57] <divis1969> popey: thanks a lot!
[11:58] <ogra_> popey, well, if the fs was patched to use  fseek64() then you'd have 4GB ;)
[12:03] <popey> ogra_: i can write 4GB to it, see my comment
[12:03] <ogra_> and you can then read all 4GB ?
[12:03] <popey> Well, it doesn't stop writing at 2GB, like the camera does
[12:22] <john-mcaleely> did you get all the questions answered popey divis1969 ?
[13:13] <dobey> mardy: hey, any idea why marcustomlinson would be getting a "blank ubuntu one window" when trying to add an account under unity8-desktop-session-mir?
[13:14] <kenvandine> seb128, could you give me a packaging review?
[13:14] <seb128> kenvandine, url?
[13:14] <kenvandine> seb128, libphonenumber in silo 7, it's a merge from debian to fix ftbfs and some changes to make it easier to MIR
[13:15] <kenvandine> https://requests.ci-train.ubuntu.com/#/ticket/1774
[13:15] <seb128> kenvandine, k, let me have a look
[13:15] <kenvandine> thx
[13:15] <kenvandine> i dropped the -java package
[13:15] <seb128> urg
[13:15] <seb128> not a small diff
[13:15] <kenvandine> and most of the java related build deps
[13:15] <kenvandine> i know
[13:15] <kenvandine> that's why i really wanted someone else to review it for me :)
[13:15] <seb128> ;-)
[13:15] <seb128> going to take me a bit longer than glancing
[13:16] <kenvandine> but... before it build depend for maven stuff and tomcat7
[13:16] <seb128> I'm going back to you in a bit
[13:16] <kenvandine> we would not want to move tomcat to main
[13:16] <kenvandine> seb128, understood, didn't expect quick :)
[13:16] <marcustomlinson> mardy: http://i.imgur.com/VB5qMOm.jpg
[13:16] <kenvandine> it still needs java at build time, but what's in main in fine
[13:17] <seb128> kenvandine, it's going to be this afternoon don't worry, it's just not a trivial on the side one so I finish what I'm doing and do that next
[13:19] <matv1> Ping KyleN
[13:20] <kyleN> hi matv1
[13:20] <matv1> kyleN hi iirc you are the man to see about scopes right
[13:20] <kyleN> matv1, good starting place :)
[13:21] <matv1> kyleN cool just a quick question. I saw that the swipe up functionality to activivate / deactivate scopes dont work in desktop mode
[13:22] <matv1> I coulndt really find a bug for that. I will report one. BUt if scopes will be redisigned in such a way that this becomes irrelevany I wont bother
[13:23] <matv1> kyleN your thoughts?
[13:25] <kyleN> matv1, are you referring to the case where you plug in a monitor and keyboard?
[13:25] <matv1> kyleN yes
[13:26] <kyleN> matv1 and are you referring to access the "Manage" page in which you can see all scopes and favorite or unfavorite them?
[13:27] <kyleN> accessING
[13:27] <dobey> accessING sounds like a trademarked banking feature ;)
[13:27] <matv1> kyleN correct: there is for some reason no way to grab and drag that little hint thing at the bottom up using a mouse
[13:28] <kyleN> matv1, good question. I need to defer here to someone with better insight into how one manages scopes in dekstop mode.
[13:29] <kyleN> hang on
[13:29] <matv1> dobey haha well it doesnt matter anyway. I wont do any online banking on my phone untill ogra_ says its okay
[13:29] <matv1> kyleN allright
[13:32] <kyleN> matv1, have you tried tapping the arrow instead of swiping it?
[13:32] <matv1> kyleN I am not sure. Should that work?
[13:32] <kyleN> matv1: i was told it should :)
[13:33] <matv1> i am not current behind a ut system
[13:33] <matv1> aha I will check later on
[13:33] <matv1> not very discoverable though :)
[13:33] <kyleN> matv1, it should react to mouse clicks AND to click and drag if your click and drag is done precisely
[13:34] <matv1> click and drag definitely doesnt
[13:34] <marcustomlinson> click and drag doesn't work no
[13:34] <marcustomlinson> touch drag
[13:34] <marcustomlinson> and mouse click
[13:34] <kyleN> ah, thanks marcustomlinson
[13:35] <matv1> right thanks both thats cleared up then
[13:35] <dobey> well that is confusing
[13:35] <matv1> dobey yes agreed but obviuously a design choice
[13:36] <dobey> i don't care who chose it :)
[13:37] <marcustomlinson> agreed, you click and drag to change scopes, but can't with the manage dash arrow
[13:38] <dobey> the point is that it's an inconsistency and is confusing; doesn't matter if it's a "design choice" or not. design do make mistakes :)
[13:40] <mardy> dobey, marcustomlinson: I wonder if it could be the same as bug 1618983, it was just filed today
[13:41] <mardy> dobey, marcustomlinson: looks like it's loading the XCB plugin for some reason
[13:43] <dobey> mardy: ah, sounds like that would do it. wonder why that's happening
[13:43] <mardy> marcustomlinson: can you get the logs with OAU_LOGGING_LEVEL=2 OAU_DAEMON_TIMEOUT=9999 online-accounts-service?
[13:43] <matv1> marcustomlinson kyleN but i will not be filing a bug then to add click and drag functionality. Unless you thinks it has merrit
[13:44] <kyleN> matv1, cool. it does not seem necessary at this point
[13:44] <dobey> mardy: i guess if both QPAs are installed, the X one is getting preferred for some reason?
[13:44] <matv1> kyleN ok thanks for your time
[13:44] <kyleN> you too!
[13:45] <mardy> dobey: the weird thing is that marcustomlinson said that facebook works
[13:46] <mardy> so it might be another issue
[13:46] <marcustomlinson> mardy: I'm still getting used to working in the unity8 session
[13:46] <marcustomlinson> re: getting logs
[13:47] <dobey> marcustomlinson: "screen $shell" is your friend when it comes to terminal in unity8
[13:47] <mardy> marcustomlinson: are you running it on bare metal, or did you succeed running it in virtualbox?
[13:47] <marcustomlinson> not vm
[13:47] <yahn> Is it possible to have GTK/QT theme support when an application is running using XMir?
[13:48] <marcustomlinson> dobey: "screen $shell"?
[13:49] <dobey> marcustomlinson: well, assuming the screen isn't a child of terminal app itself i guess. because switching apps under unity8 pauses the background apps and their children
[13:50] <dobey> marcustomlinson: ie if you run what mardy told you in terminal app, and then switch windows, it will be paused
[13:50] <marcustomlinson> I can't even install the terminal app :D
[13:50] <marcustomlinson> no U1 account
[13:51] <dobey> oh i guess there isn't a deb for it in the archive either, like some of the other apps have
[13:51] <dobey> meh :)
[13:56] <divis1969> john-mcaleely: well, that's enough for me to start. I've found that there the default 4.4.2 manifest branch (checked out by phablet-dev-bootstrap) does not have arm64 support, but I've found phablet-5.1.1_r36 and is trying to sync it at the moment
[14:03] <john-mcaleely> divis1969, awesome. When you have more questions, ondra will be a good place to ping. He's probably still afk this week though
[14:03] <divis1969> ok, thanks
[14:04] <marcustomlinson> mardy: https://pastebin.canonical.com/164515/
[14:14] <marcustomlinson> mardy: my ~/.local/share/accounts/qml-plugins/ folder is empty, is that bad?
[14:14] <marcustomlinson> mardy: line 50 of that log: file:///home/marcustomlinson/.local/share/accounts/qml-plugins/ubuntuone/Main.qml: File not found
[14:14] <mardy> marcustomlinson: no, it just means that you have not any plugins installed from click packages
[14:15] <mardy> marcustomlinson, dobey: the error is in the last line of the logs
[14:15]  * mardy check what that file says...
[14:18] <mardy> marcustomlinson: can you edit /usr/share/accounts/qml-plugins/ubuntuone/Main.qml and print the Loader's "status" as it changes?
[14:19] <mardy> marcustomlinson: also try commenting out line 45, it looks suspicious
[14:19] <mardy> (the sourceComponent one)
[14:21] <marcustomlinson> mardy: you're gonna have to help me with what you mean by print the Loader's "status" as it changes
[14:23] <mardy> marcustomlinson: add a line inside the Loader: onStatusChanged: console.log("loader status changed to " + status)
[14:28] <marcustomlinson> mardy: did what you said. log is exactly the same: https://pastebin.canonical.com/164524/
[14:32] <mardy> marcustomlinson: is it Qt 5.6 or 5.5?
[14:33] <dobey> oh yeah, maybe you need to dist-upgrade
[14:36] <mardy> dobey: the last line of marcustomlinson's logs doesn't appear on the phone
[14:37] <mardy> dobey: I suspect that that property binding happens to work in qt 5.5, but broke with 5.6
[14:37] <dobey> mardy: weren't you trying to land 5.6 to vivid too?
[14:37] <dobey> err, no not you
[14:37] <dobey> i think mirv was trying to land that to vivid too
[14:37] <mardy> dobey: indeed it's a bit surprising that it works at all... it requires the loader to have completed before the binding has evaluated, which is not a given
[14:37] <dobey> Mirv: ^^ do you have a vivid 5.6 silo?
[14:38] <mardy> dobey: unless marcustomlinson is already running yakkety, which AFAIK has qt 5.6 already
[14:38] <dobey> mardy: xenial-overlay has 5.6 too
[14:39] <mardy> dobey: right, so I suspect that it works on the phones because there we have 5.5, but it doesnt't work with 5.6
[14:39]  * mardy just guessing
[14:42] <marcustomlinson> mardy: I'm on Xenial + overlay
[14:43] <marcustomlinson> mardy: by the way, what's the easiest way to get my qt version?
[14:43] <marcustomlinson> usually do qmake -v, but don't have qmake installed
[14:43] <dobey> dpkg -l|grep qt5
[14:44] <dobey> i guess libqt5core5 or whatever is probably the most accurate one to look at
[14:44] <marcustomlinson> mardy, dobey: yeah 5.6
[14:44] <mardy> marcustomlinson: try changing line 26 to   contentHeight: (editPageLoader.status == Loader.Ready ? editPageLoader.item.height : 0) + keyboardSize
[14:45] <mardy> marcustomlinson: or maybe just   contentHeight: (editPageLoader.item ? editPageLoader.item.height : 0) + keyboardSize
[14:48] <marcustomlinson> mardy: after that change: https://pastebin.canonical.com/164526/
[14:48] <marcustomlinson> still blank
[14:53] <dobey> marcustomlinson: change that ": 0" to ": units.gu(60)" and see what happens
[14:55] <sil2100> dpm: hey!
[14:55] <dpm> o/
[14:56] <marcustomlinson> dobey: no difference
[14:57] <marcustomlinson> mardy: here's how to easily test this. Run normal unity7 desktop on Xenial+overlay. run "start smart-scopes-proxy", then "unity8-dash --mousetouch"
[14:57] <sil2100> dpm: we released a new sync-monitor that hopefully now installs the .mo files as required, I think upstreams have done everything that needed - could you check if the sync-monitor template is there?
[15:03] <dpm> sil2100, let me have a look
[15:03] <dobey> oh, lots of failed to build in the 5.6 backport silo
[15:04] <sil2100> dpm: thanks, I don't have much experience in how LP translations work, so I just trust upstreams here
[15:04] <dpm> sil2100, still no joy: https://translations.launchpad.net/ubuntu-rtm/15.04/+source/sync-monitor/+imports?field.filter_status=all&field.filter_extension=pot
[15:04] <dobey> so not easy to throw it on a phone and test yet :-/
[15:05] <sil2100> dpm: do you know what could be missing?
[15:05] <sil2100> dpm: we just pushed the sync-monitor package to the overlay with the .mo files installed
[15:05] <sil2100> I guess the LP trunk is also configured properly to export translations
[15:05] <sil2100> renatu, bfiller: ^
[15:05] <dpm> sil2100, it's not about the .mo files
[15:06] <dpm> sil2100, the package needs to create a .pot file when it's being built
[15:06] <dpm> that's what LP imports
[15:06] <sil2100> dpm: I think it was doing it already
[15:07] <dpm> sil2100, ah, wait a second... I think LP is showing an outdated date
[15:08] <sil2100> Building sync-monitor.pot... <- it builds it during build time, not sure what more is needed
[15:09] <dpm> sil2100, I got confused by LP showing an upload of 2015 there (https://translations.launchpad.net/ubuntu-rtm/15.04/+source/sync-monitor/+imports?field.filter_status=all&field.filter_extension=pot), but looking at the .pot file itself, it seems it's up-to-date
[15:09] <dpm> I'll just approve the template
[15:09] <sil2100> Ah :)
[15:09] <sil2100> dpm: thanks!
[15:09] <sil2100> renatu, bfiller: unping
[15:16] <dpm> sil2100, I'll wait until it's imported to double-check. It will still take a few minutes
[15:28] <mterry> kenvandine: just fyi, I put USS default-wallpaper and fix-highlight-color in a u8 silo we have going.  Nothing needed from you, just saying
[15:28] <kenvandine> mterry, cool, jgdx ^^ fyi
[16:00] <seb128> kenvandine, the libphonenumber update looks fine to me
[16:00] <kenvandine> seb128, excellent!
[16:01] <kenvandine> we have nothing that depends on that java package, we had just inherited it from debian
[16:15] <seb128> kenvandine, right, I had a look to that as well ;-)
[17:53] <Mirv> dobey: mardy: there is a vivid Qt 5.6 silo but it's unmaintained. it was only used to test 5.6 when xenial didn't yet boot on the phones. there's no plan of landing Qt 5.6 to vivid OTAs, the path of stable OTAs is (eventually) vivid+Qt5.4 -> xenial+Qt5.6
[17:58] <Mirv> dobey: mardy: if you hit any QDBus related issues still with 5.6 thanks to it being threaded now, you may be interested in how boiko fixed telepathy-qt http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
[17:58] <Mirv> and with that, good night
[18:04] <boiko> Mirv: it seems we still have more things to fix related to that, but that's the most common issue
[18:13] <timppa> Hello!
[18:14] <timppa> I've tried to ask at ubuntu-1 channel for help on Unity8 + Ubuntu1 account on laptop (16.10)... Anyone have ideas how can I add the account?
[18:24] <dobey> timppa: under unity8 it should just work. what problem are you having?
[19:14] <Flohack> Good Eve!
[19:15] <Flohack> I am porting for a new device. Unfortunately boot.img is too big. Somehow kernel got fatter than in CM build
[19:15] <Flohack> What can I disable in the kernel config that wont hurt too much
[19:15] <Flohack> And why do we need SELinux in?
[19:18] <dobey> Flohack: android bits need it i think.
[19:19] <Flohack> Hmm
[19:20] <Flohack> I need to shrink the kernel for about 790k
[19:20] <Flohack> This is a lot I think
[19:20] <popey> are wierd filesystems compiled in?
[19:21] <Flohack> I compared with CM build from which I am porting. It has the same fs configs and is smaller. So it must come either from kernel options or from a static driver but I dont see that
[19:24] <Michal_> Hello,  i want asi , aby body use meizu MX4?
[19:25] <Michal_> I want ask you, if anybody use mx4?
[19:26] <Flohack> Next question, did anyone ever have issues with that: /libnativehelper_intermediates/export_includes it says cannot find rule to make that target
[19:26] <Michal_> I thinking,  that i will buy it,  i want listen experience
[19:28] <Michal_> I use nexus 4 niw
[19:28] <Michal_> Now
[19:30] <Michal_> Nexus 4 vs mx4 ?
[19:30] <Flohack> Be patient. IRC is not so hot people are looking from time to time
[19:32] <Michal_> I am sorry, that i worry, but seller of mx4 don't want wait too long.
[19:44] <Michal_> Hello use sombidy mx4? I want know experience, bcs i want buy it.
[19:53] <Michal_> Hello use anybody mx4? Is it good phone with ut?
[19:57] <pmcgowan_> Michal_, the MX4 works fine it is one of the supported commercial phones
[19:59] <Michal_> I know, i use nexus 4, but still there some bugs, like overhiting, or browser hang up etc. I want know if mx4 is better
[20:01] <Michal_> Mean if mx4 is better ten nexus.
[20:02] <pmcgowan> mx4 has a bigger, nicer screen, faster processor, does 4G, but they are both fine imo
[20:03] <Michal_> I am sorry, what does fine imo mean?
[20:04] <ogra_> "imo" = in my opinion
[20:04] <Michal_> I see
[20:05]  * ogra_ wasnt a big fan of the mx4 ... the edge of the case goes slightly above the edge of the screen and is very sharp ... since all in ubuntu works with swipe gestures it isnt really pleasant to swipe on the screen edge 
[20:05] <pmcgowan> Michal_, I used the nexus4 for a long time too
[20:05] <pmcgowan> ogra_, that is true, the one thing I dont like
[20:05] <ogra_> i *love* the MXpro5 though
[20:06] <Michal_> So is it fully usefully for normal work? What about scroll in web briwser, hang up sometimes?
[20:06] <ogra_> the MX4 had two really awesome parts ... the audio chip is the best i have seen in a phone yet ... and the camera was actually better than the one in the mx5
[20:07] <Michal_>  I listen that pro 5 is best, but for me is too expensive
[20:07] <Michal_> That is why iam think about mx4
[20:08] <ogra_> well, try to get your hands on one and try the screen edge thing ... if you can live with that, take it ...
[20:08] <ogra_> not sure for how much longer the nexus will actually get official support ... it starts to show its age
[20:14] <Flohack> Another issue I have, compat-wireless is not fitting well into my tree. It ignores somehow the setup for arch and cross-compile
[20:14] <Flohack> Its in CM tree, where it works perfectly
[20:14] <Michal_> OK,  many thanks for informations. I will thinkin during night
[20:19] <dobey> hmm, well the scrolling in the browser hanging up sometimes is not entirely a hardware issue i don't think
[20:19] <dobey> or limited to the browser