Re: [Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
On Fri, Jul 17, 2015 at 2:58 PM, Rodney Dawes rodney.da...@canonical.com wrote: If you really need to install some command line tools on your phone for some reason, or you need to compile something on your phone, the best way to do it, is with a chroot on the data partition, rather than by making the root partition, which has very limited space, writable. See my answer to this question[1] on Ask Ubuntu, for details on how to set up a chroot for doing such development work in. The only issue here is that you can't do sudo chroot from within the Terminal app itself, due to confinement rules, but it works fine over adb/ssh. I think not being able to run those tools from terminal app is quite a strong limitation...as you only usually use the terminal app when you *don't* have a laptop available (for whatever reason) [1] https://askubuntu.com/questions/620740 On Fri, 2015-07-17 at 14:34 +0100, John McAleely wrote: With the release of OTA-4 a few weeks ago, we received a few reports of problems where the handset would get stuck in a boot loop, or refuse to boot past the initial logo. One root cause we have established is when the system partition has run out of space. Given that the supported model for system updates is that only the system-image-updater writes to this space, it does not display a warning in the case when the disk has been filled by something else. We've got to this root cause unfortunately quite late in the ota-5 cycle, so we didn't have time to land any engineering fixes (indeed, we're still discussing what might be possible). Of course, if your system partition has been writable, I think you have taken on some measure of responsibility for looking after your phone, so can you do something before an OTA? Yes - you can check for a reasonable amount of free space. If you've made your system writable, I'm going to assume you can use terminal or adb on the command line. Use df to see how much space you have: $ df -h /dev/mmcblk0p6 2.0G 1.6G 460M 78% / more lines skipped You only need to be concerned with the space assigned to / (rightmost column). The other columns may differ on each machine. Here you can see the results from my machine, and from a 2G partition, around 460M is free. This will be fine for OTA update, since this machine has only ever had a read-only system partition. Specifying how much space you need for an OTA update is tricky - once you've made your disk writeable, maybe the OTA will need a different amount of space, because some of the files you've updated share footprint with OTA delivered files. If you use your system in a writeable mode, and have had OTA updates delivered successfully, please comment here with how much disk space you have/had free. J -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] [Call for testing] New Thumbnailer
Attention, I believe the change involved has broken Telegram. We were dynamically linking with libthumbnailer.so and making calls to thumbnailer.get_thumbnail from C++. The application will not start on rc-proposed. http://paste.ubuntu.com/11892354/ I'm asking in #unity-api, but have not yet received a reply. On Sat, Jun 27, 2015 at 5:53 AM, Michi Henning michi.henn...@canonical.com wrote: One more request: please test with *large* numbers of images/photos/videos/mp3. 2000 or more is good start. To avoid having to copy tons of videos, mp3s or jpg images, you can just make hard links to a single file. The name of the link is part of the cache key, so the effect is the same as having lots of separate files, and you don't have to copy hundreds of megabytes around that way. Cheers, Michi. On 27 Jun 2015, at 13:48 , Michi Henning michi.henn...@canonical.com wrote: On 27 Jun 2015, at 13:36 , Victor Thompson victor.thomp...@gmail.com wrote: Have there been any recent changes to the silo? Testing looked good the last time I personally checked, if there are deltas let me know and I'll test as well. The main delta is that, on Arm, we are now limiting the number of concurrent gstreamer pipelines to 1 because anything else is too risky. On other architectures, we use as many gstreamer pipelines as there are CPU cores. You should see around 780% CPU utilization on an 8-core machine with heavy workloads, such as thumbnailing a whole bunch of videos at once. Once the cache is hot, it delivers the thumbnails *very* fast. Please test your applications not only with a cold cache, but also a hot one; the way memory allocations happen is markedly different that way. If you want to clean the cache and start afresh, just run thumbnailer-admin clear That wipes the cache completely. You can see cache statistics by running thumbnailer-admin stats -v Please keep an eye out for requests with an invalid QSize (width or height == -1). Get rid of all of these. Instead, ask for the thumbnail in the size you need it. This drives the cache in the most efficient way possible. Your application must be prepared to handle a smaller thumbnail than what it asked for because we never up-scale. If original artwork is available only as 512 and you ask for 640, the actual thumbnail you get will be 512. You are guaranteed that you will never get something larger than what you ask for, unless you ask for (0,0), in which case we deliver full size. (Don't do this unless there is a good chance that you will need the same image again shortly; otherwise, it just eats space in the cache and makes it less effective.) Cheers, Michi. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp -- Software Engineer Professional and Engineering Services Canonical Ltd. Ubuntu - Linux for human beings | www.ubuntu.com -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
[Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
With the release of OTA-4 a few weeks ago, we received a few reports of problems where the handset would get stuck in a boot loop, or refuse to boot past the initial logo. One root cause we have established is when the system partition has run out of space. Given that the supported model for system updates is that only the system-image-updater writes to this space, it does not display a warning in the case when the disk has been filled by something else. We've got to this root cause unfortunately quite late in the ota-5 cycle, so we didn't have time to land any engineering fixes (indeed, we're still discussing what might be possible). Of course, if your system partition has been writable, I think you have taken on some measure of responsibility for looking after your phone, so can you do something before an OTA? Yes - you can check for a reasonable amount of free space. If you've made your system writable, I'm going to assume you can use terminal or adb on the command line. Use df to see how much space you have: $ df -h /dev/mmcblk0p6 2.0G 1.6G 460M 78% / more lines skipped You only need to be concerned with the space assigned to / (rightmost column). The other columns may differ on each machine. Here you can see the results from my machine, and from a 2G partition, around 460M is free. This will be fine for OTA update, since this machine has only ever had a read-only system partition. Specifying how much space you need for an OTA update is tricky - once you've made your disk writeable, maybe the OTA will need a different amount of space, because some of the files you've updated share footprint with OTA delivered files. If you use your system in a writeable mode, and have had OTA updates delivered successfully, please comment here with how much disk space you have/had free. J -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
If you really need to install some command line tools on your phone for some reason, or you need to compile something on your phone, the best way to do it, is with a chroot on the data partition, rather than by making the root partition, which has very limited space, writable. See my answer to this question[1] on Ask Ubuntu, for details on how to set up a chroot for doing such development work in. The only issue here is that you can't do sudo chroot from within the Terminal app itself, due to confinement rules, but it works fine over adb/ssh. [1] https://askubuntu.com/questions/620740 On Fri, 2015-07-17 at 14:34 +0100, John McAleely wrote: With the release of OTA-4 a few weeks ago, we received a few reports of problems where the handset would get stuck in a boot loop, or refuse to boot past the initial logo. One root cause we have established is when the system partition has run out of space. Given that the supported model for system updates is that only the system-image-updater writes to this space, it does not display a warning in the case when the disk has been filled by something else. We've got to this root cause unfortunately quite late in the ota-5 cycle, so we didn't have time to land any engineering fixes (indeed, we're still discussing what might be possible). Of course, if your system partition has been writable, I think you have taken on some measure of responsibility for looking after your phone, so can you do something before an OTA? Yes - you can check for a reasonable amount of free space. If you've made your system writable, I'm going to assume you can use terminal or adb on the command line. Use df to see how much space you have: $ df -h /dev/mmcblk0p6 2.0G 1.6G 460M 78% / more lines skipped You only need to be concerned with the space assigned to / (rightmost column). The other columns may differ on each machine. Here you can see the results from my machine, and from a 2G partition, around 460M is free. This will be fine for OTA update, since this machine has only ever had a read-only system partition. Specifying how much space you need for an OTA update is tricky - once you've made your disk writeable, maybe the OTA will need a different amount of space, because some of the files you've updated share footprint with OTA delivered files. If you use your system in a writeable mode, and have had OTA updates delivered successfully, please comment here with how much disk space you have/had free. J signature.asc Description: This is a digitally signed message part -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
On Fri, 2015-07-17 at 15:30 +0100, Andrea Bernabei wrote: On Fri, Jul 17, 2015 at 2:58 PM, Rodney Dawes rodney.da...@canonical.com wrote: If you really need to install some command line tools on your phone for some reason, or you need to compile something on your phone, the best way to do it, is with a chroot on the data partition, rather than by making the root partition, which has very limited space, writable. See my answer to this question[1] on Ask Ubuntu, for details on how to set up a chroot for doing such development work in. The only issue here is that you can't do sudo chroot from within the Terminal app itself, due to confinement rules, but it works fine over adb/ssh. I think not being able to run those tools from terminal app is quite a strong limitation...as you only usually use the terminal app when you *don't* have a laptop available (for whatever reason) It should still be possible to ssh localhost to chroot, or depending on the tools you need to run, you may be able to run them from the path in the chroot, without chrooting into the chroot. For example, you could run ./wily-chroot/usr/bin/ping if need be. [1] https://askubuntu.com/questions/620740 On Fri, 2015-07-17 at 14:34 +0100, John McAleely wrote: With the release of OTA-4 a few weeks ago, we received a few reports of problems where the handset would get stuck in a boot loop, or refuse to boot past the initial logo. One root cause we have established is when the system partition has run out of space. Given that the supported model for system updates is that only the system-image-updater writes to this space, it does not display a warning in the case when the disk has been filled by something else. We've got to this root cause unfortunately quite late in the ota-5 cycle, so we didn't have time to land any engineering fixes (indeed, we're still discussing what might be possible). Of course, if your system partition has been writable, I think you have taken on some measure of responsibility for looking after your phone, so can you do something before an OTA? Yes - you can check for a reasonable amount of free space. If you've made your system writable, I'm going to assume you can use terminal or adb on the command line. Use df to see how much space you have: $ df -h /dev/mmcblk0p6 2.0G 1.6G 460M 78% / more lines skipped You only need to be concerned with the space assigned to / (rightmost column). The other columns may differ on each machine. Here you can see the results from my machine, and from a 2G partition, around 460M is free. This will be fine for OTA update, since this machine has only ever had a read-only system partition. Specifying how much space you need for an OTA update is tricky - once you've made your disk writeable, maybe the OTA will need a different amount of space, because some of the files you've updated share footprint with OTA delivered files. If you use your system in a writeable mode, and have had OTA updates delivered successfully, please comment here with how much disk space you have/had free. J -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp signature.asc Description: This is a digitally signed message part -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
[Ubuntu-phone] Prevent suspending
From: c...@outlook.es To: ubuntu-phone@lists.launchpad.net Subject: Prevent suspendig Date: Fri, 17 Jul 2015 10:48:44 +0200 I'd like to know how to Prevent suspending an app with a command line instead using TweakGeek. Thanks, Cesar -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
[Ubuntu-phone] Prevent suspendig
I'd like to know how to Prevent suspending an app with a command line instead using TweakGeek. Thanks, Cesar -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
El viernes, 17 de julio de 2015 18:02:43 (CEST), John McAleely escribió: On 17 July 2015 at 15:56, Matthias Apitz g...@unixarea.de wrote: I do not have / writable: $ mount | fgrep ' / ' /dev/mmcblk0p6 on / type ext4 (ro,relatime,data=ordered) It is not meaningful to know the current status of the partition. If it has *ever* been writable, something may have filled it at that time. I understand, but I never installed something there. I made it once writeable for *seconds* to set a crontab entry for user phablet, nothing more. matthias -- Sent from my Ubuntu phone http://www.unixarea.de/ -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] posting images to social media on 15.10
It sounds like you've moved onto one of the development channels (those are the only ones that update the ubuntu image daily), and may have tumbled over this bug: https://bugs.launchpad.net/webapps-core/+bug/1474356 I'm not familiar with MultiROM Manager, or the N5 image channels, but you might prefer to use one of the more stable channels: https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/ J On 17 July 2015 at 00:25, Sameer Verma sve...@sfsu.edu wrote: I have two images on my Nexus 5, managed via the MultiROM Manager Android app. On the 15.04-based image, I can post images to Twitter and Facebook, but on the 15.10 image (which updates pretty much every day), it does not do so. It will take me as far as selecting the image, but won't return to the Twitter or Facebook app to post it. Is this expected, or am I missing something? cheers, Sameer -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] posting images to social media on 15.10
On 07/17/2015 03:38 AM, Roman Zonov wrote: Tried to find 15.10 channel, but didn't find it:( On the Nexus 5, which is not officially supported, Tassadar's servers must be used. He has not updated the build servers since all of the channel names changed. In MultiROM Manager on the Nexus 5, you'll find ubuntu-rtm/14.09 which is equivalent to the ubuntu-touch/stable/ubuntu (and features the OTAs as they are promoted, so this is 15.04). I believe that ubuntu-rtm/devel-proposed is a daily build of wily. I haven't worked with it in a while but I seem to recall that it wasn't very useful. Please note that wily is guaranteed to be broken more often than not, because it isn't the current development focus and vivid. Vivid is much better tested, but the non-stable channels are where developers land broken software so that they can integrate it and fix bugs so that it is no longer broken. If you're not actively troubleshooting and filing bug reports or writing code and submitting patches, you're probably better off on ubuntu-touch/stable/ubuntu. At the very least, you should expect to have a non-functional phone a considerable amount of the time when not on the stable channel. It's not suitable for primary phones. -- Nathan Haines Ubuntu - http://www.ubuntu.com/ -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] posting images to social media on 15.10
Tried to find 15.10 channel, but didn't find it:( 17.07.2015, 02:29, Sameer Verma sve...@sfsu.edu: I have two images on my Nexus 5, managed via the MultiROM Manager Android app. On the 15.04-based image, I can post images to Twitter and Facebook, but on the 15.10 image (which updates pretty much every day), it does not do so. It will take me as far as selecting the image, but won't return to the Twitter or Facebook app to post it. Is this expected, or am I missing something? cheers, Sameer -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp -- Best regards, Roman Zonov. VK: http://vk.com/zonov_roman Facebook: https://www.facebook.com/roman2861 Twitter: https://twitter.com/zonov_roman -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
[Ubuntu-phone] Landing team 17.07.15
Hello everyone, The OTA-5 arale customization hook fix is now in QA testing - we should have it ready for the release on Monday. The plan is to release the BQ updates on Monday morning and Meizu a bit later that day, giving more time in case the custom tarball operations take a bit longer. In the meantime landings continue. Wily awaits a big mir 0.14 release with multiple goodies - also targeted for vivid-overlay in the nearest future. A new nuntium fixing MMS with T-Mobile US networks and a new network-manager arrived in the overlay as well, both very important from the user-perspective. We also fixed the emulator image builds, although those still don't really work - but have the right developers working on getting that back up. Next week will be really exciting. Besides OTA-5, next week will also be the time when Bileto, the CI Train spreadsheet replacement, should go live in production. There will be a grace period when we support both, but afterwards we'll finally get rid of the 'temporary' automated spreadsheet solution. More news soon from Robert. Have a nice weekend! * What landed in our images: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch #69 rc-proposed/krillin - http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/69.commitlog * Smoke-testing results: devel : http://ci.ubuntu.com/smokeng/wily/touch/ rc : http://ci.ubuntu.com/smokeng/vivid/touch_stable/ #258 devel-proposed/mako - http://ci.ubuntu.com/smokeng/wily/touch/mako/258:20150717:20150708/13295/ #192 rc-proposed/mako - http://ci.ubuntu.com/smokeng/vivid/touch_stable/mako/192:20150717:20150210/13294/ * Some useful documentation: https://wiki.ubuntu.com/LandingTeam https://wiki.ubuntu.com/citrain/FAQ https://wiki.ubuntu.com/citrain/RTMLandingApproaches https://wiki.ubuntu.com/citrain/LandingProcess https://wiki.ubuntu.com/LandingTeam/Smoketesting http://developer.ubuntu.com/start/ubuntu-for-devices/image-channels/ http://people.canonical.com/~platform/citrain_dashboard/ http://people.canonical.com/~lzemczak/issues/ https://trello.com/b/AE3swczu/silo-testing * Blocking issues (stable): ** [vivid-overlay] unity8 fails to start on the emulator https://bugs.launchpad.net/bugs/1458694 ** Move from ota4 image to ota5 image doesn't update the override file for the favourite apps https://bugs.launchpad.net/bugs/1474739 * Blocking issues (devel): ** Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed https://bugs.launchpad.net/bugs/1425625 ** [vivid-overlay] unity8 fails to start on the emulator https://bugs.launchpad.net/bugs/1458694 ** location is inaccurate https://bugs.launchpad.net/bugs/1426307 = Merge requests present ** No data connection switching from 2G only to 3G https://bugs.launchpad.net/bugs/1461593 = Merge requests present ** Move from ota4 image to ota5 image doesn't update the override file for the favourite apps https://bugs.launchpad.net/bugs/1474739 * Known issues: None. * Issues not impacting user experience: None. Best regards, -- Łukasz 'sil2100' Zemczak Foundations Team lukasz.zemc...@canonical.com www.canonical.com -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] QML help
I tried your suggestion without luck.
If anyone can offer some advice on the following code.
http://paste.ubuntu.com/11893812/
I want to the label to stay above the keyboard. using anchor layout pushes
the whole page under the header and out of view.
Thanks,
Dan
On 14 July 2015 at 14:19, Mohamed MANSOUR med.mns...@gmail.com wrote:
hi , try to add property clip : true to the page member and i think
this will solve your problem
2015-07-14 13:08 GMT+02:00 Daniel Wood s.d.wood...@googlemail.com:
Hi,
Thanks for replying. I would like to keep the textfield above the
onscreenkeyboard so i used anchorToKeyboard: true in the mainview.
My expectation was that the label {id: rpm} would resize (shrink) and
the mainview would remain stationary.
I think I have misunderstood the use of anchorToKeyboard: true.
Thanks,
Dan
On 14 July 2015 at 12:03, Andrea Bernabei andrea.berna...@canonical.com
wrote:
Hi Daniel,
can you elaborate a bit more? I'm not sure I understood what your
current and expected layouts look like :)
On Sat, Jul 11, 2015 at 9:26 PM, Daniel Wood s.d.wood...@googlemail.com
wrote:
Anyone know why the page disappears under the header when the keyboard
pops out?
I would like to anchor the layout and let the rpm label resize.
http://paste.ubuntu.com/11863268/
Thanks,
Dan
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
--
*Mohamed MANSOUR*
Eléve Ingenieur à *EPI Sousse* http://www.episousse.com.tn/
Développeur .Net chez *MasterCom* http://www.mastercom-tn.com/
Fondateur de *GDG Monastir*
https://developers.google.com/groups/chapter/103429150782052657644/
med.mns...@gmail.com(+216) 52 958 794 0021652958794
http://twitter.com/medfredjmans
http://www.facebook.com/mansour.mohamed
http://tn.linkedin.com/pub/mohamed-mansour/76/498/25a/
https://plus.google.com/u/0/+MohamedMANSOURdev/posts
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] Made your system writeable? Is your disk full? OTA might break
On 17 July 2015 at 15:56, Matthias Apitz g...@unixarea.de wrote: I do not have / writable: $ mount | fgrep ' / ' /dev/mmcblk0p6 on / type ext4 (ro,relatime,data=ordered) It is not meaningful to know the current status of the partition. If it has *ever* been writable, something may have filled it at that time. Note that I believe users need to take explicit action with developer tools (ubuntu-device-flash or sudo on a handset that has had changes made from defaults - either install of terminal, or use of developer mode) to ever mark the partition writeable. $ df -h / Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p6 2,0G 1,6G 317M 84% / Why I see onl 84% free and both we have the same used space of 1,6G? I don't know. I observe that in both cases the maths df presents doesn't actually add up. (1.6+4.6 != 2 and 1.6 + 0.3 != 2). Will 317M still be fine? I think so. J -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
[Ubuntu-phone] chroot file systen on the data partition (was: Made your system writeable? Is your disk full? OTA might break)
El día Friday, July 17, 2015 a las 09:58:54AM -0400, Rodney Dawes escribió: If you really need to install some command line tools on your phone for some reason, or you need to compile something on your phone, the best way to do it, is with a chroot on the data partition, rather than by making the root partition, which has very limited space, writable. See my answer to this question[1] on Ask Ubuntu, for details on how to set up a chroot for doing such development work in. The only issue here is that you can't do sudo chroot from within the Terminal app itself, due to confinement rules, but it works fine over adb/ssh. [1] https://askubuntu.com/questions/620740 Hi Rodney, When I follow your steps in the above URL and unpack the tar archive into some dir with $ mkdir root $ cd root $ tar xzf ../vivid-preinstalled-touch-armhf.tar.gz it gives a lot of error messages of the type: ... tar: dev/ram14: Cannot mknod: Operation not permitted tar: dev/ram1: Cannot mknod: Operation not permitted tar: dev/mixer2: Cannot mknod: Operation not permitted tar: dev/sndstat: Cannot mknod: Operation not permitted tar: dev/audio: Cannot mknod: Operation not permitted ... Is this by intention to unpack the archive as unpriv user 'phablet' or shouldn't it better done as root or sudo? Thanks matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] [Call for testing] New Thumbnailer
We identified that the new thumbnailer does not provide the undocumented C++ thumbnailer API that the old one provided. This is only affecting Telegram on pre-OTA-6 images that have the new thumbnailer. OTA-5 is fine because it still has the old thumbnailer. Karni will be working next week with Michi and James to find the best solution so whatever version of Telegram we upload to the app store can be used both by OTA-5 with the old thumbnailer, and OTA-6 and forward with the new thumbnailer. cheers, -- alecu On Fri, Jul 17, 2015 at 8:47 AM, Michal Karnicki michal.karni...@canonical.com wrote: Attention, I believe the change involved has broken Telegram. We were dynamically linking with libthumbnailer.so and making calls to thumbnailer.get_thumbnail from C++. The application will not start on rc-proposed. http://paste.ubuntu.com/11892354/ I'm asking in #unity-api, but have not yet received a reply. On Sat, Jun 27, 2015 at 5:53 AM, Michi Henning michi.henn...@canonical.com wrote: One more request: please test with *large* numbers of images/photos/videos/mp3. 2000 or more is good start. To avoid having to copy tons of videos, mp3s or jpg images, you can just make hard links to a single file. The name of the link is part of the cache key, so the effect is the same as having lots of separate files, and you don't have to copy hundreds of megabytes around that way. Cheers, Michi. On 27 Jun 2015, at 13:48 , Michi Henning michi.henn...@canonical.com wrote: On 27 Jun 2015, at 13:36 , Victor Thompson victor.thomp...@gmail.com wrote: Have there been any recent changes to the silo? Testing looked good the last time I personally checked, if there are deltas let me know and I'll test as well. The main delta is that, on Arm, we are now limiting the number of concurrent gstreamer pipelines to 1 because anything else is too risky. On other architectures, we use as many gstreamer pipelines as there are CPU cores. You should see around 780% CPU utilization on an 8-core machine with heavy workloads, such as thumbnailing a whole bunch of videos at once. Once the cache is hot, it delivers the thumbnails *very* fast. Please test your applications not only with a cold cache, but also a hot one; the way memory allocations happen is markedly different that way. If you want to clean the cache and start afresh, just run thumbnailer-admin clear That wipes the cache completely. You can see cache statistics by running thumbnailer-admin stats -v Please keep an eye out for requests with an invalid QSize (width or height == -1). Get rid of all of these. Instead, ask for the thumbnail in the size you need it. This drives the cache in the most efficient way possible. Your application must be prepared to handle a smaller thumbnail than what it asked for because we never up-scale. If original artwork is available only as 512 and you ask for 640, the actual thumbnail you get will be 512. You are guaranteed that you will never get something larger than what you ask for, unless you ask for (0,0), in which case we deliver full size. (Don't do this unless there is a good chance that you will need the same image again shortly; otherwise, it just eats space in the cache and makes it less effective.) Cheers, Michi. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp -- Software Engineer Professional and Engineering Services Canonical Ltd. Ubuntu - Linux for human beings | www.ubuntu.com -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] [Design] removing scopes
Cool. So ebay and amazon scope has to be preinstalled to obtain priviledges. I bet for the same reason as in Ubuntu desktop where we badly need the amazon plugin to slow our system down. I can understand the photo scope but as some Internet reviews also confirm, ebay and amazon scope are pretty useless and I bet hardly anyone would install them. Gesendet über Yahoo Mail für Android Von:Jamie Strandboge ja...@canonical.com Datum:Do., 16. Juli 2015 um 15:03 Betreff:Re: [Ubuntu-phone] [Design] removing scopes On 07/15/2015 05:38 PM, Michi Henning wrote: On 16 Jul 2015, at 7:02 , Renato Filho renato.fi...@canonical.com wrote: Why we have so specific scopes as part of the image? Why we can not make all scopes as click? Some of the locally installed scopes have privileges that scopes installed from click packages cannot obtain. For example, the photo scope can look at your Pictures folder, which a click-installed scope cannot do. Actually, the permissions can be obtained-- use the unconfined template or read_path/write_path in the security manifest. This will trigger a manual review in the store of course (but as per store policy, Canonical-written scopes that do this can be accepted without much fuss). -- Jamie Strandboge http://www.ubuntu.com/ -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
