Re: [Ubuntu-phone] Find out if running on a phone
> > > Just try to exec getprop. It is only available on systems that are > > running an Android container. > > That's not working when confined, is it? > > What about passing an argument to the app only when called on the phone, via the desktop file in the click and checking for that argument? This is not what I use right now though in TextSecure (just check for /home/phablet, knowing I can add some more dirs to that check to increase the probability the app runs on the phone). -- 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] Find out if running on a phone
> > > You should not do that... Why do you even want to know? > > Whether the app is running on the phone vs desktop? * to use different QML since the same QML code cannot (yet) work on both * to use the content-hub for getting a file vs doing a regular file open dialog * to load contacts from the content-hub vs from another source that is desktop specific * to enable push notifications or not * to assume a different role (master or slave device of the same account) AIUI the convergence work will help with some of these but even that won't help if you want a backend part of the app to work both on the phone and desktops other that Ubuntu with the convergence supports installed (other linuxes, Windows maybe) So a way to distinguish between phone and desktop at runtime is essential. Whether it is a 100% working method via an official API or a good heuristic is not a major concern for me right now. Jani -- 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] Find out if running on a phone
On Mon, Jan 11, 2016 at 3:15 PM, Stephen M. Webb <stephen.w...@canonical.com > wrote: > On 16-01-11 06:57 AM, Jani Monoses wrote: > > > > You should not do that... Why do you even want to know? > > > > Whether the app is running on the phone vs desktop? > > > > * to use different QML since the same QML code cannot (yet) work on both > > * to use the content-hub for getting a file vs doing a regular file open > dialog > > * to load contacts from the content-hub vs from another source that is > desktop specific > > * to enable push notifications or not > > * to assume a different role (master or slave device of the same account) > > Just so you know, the difference between a desktop and a phone is that > when you unplug an external monitor and input > devices from your phone it is no longer a desktop, but a desktop stays a > desktop. > > If you're developing software *right now* making any other assumptions > about phone vs. desktop, you're writing bad code > and breaking things in a highly undesirable way. > > So for the issues in my list above what would be good code that does not break things in undesirable ways? -- 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] Detect WiFi/3G/roaming?
Apart from online and limitedBandwidth properties of the NetworkingStatus element is there a way to see if we're on WiFi or 3G from QML? thanks Jani -- 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 ContentStore example?
Thanks Robert, during my searches I have actually hit upon your bug an email thread on this list, which still had content hub related questions unanswered. I had even looked at beru sources on github but saw you do not actually use the ContentStore but build upon item.move(). cheers Jani On Fri, Oct 23, 2015 at 8:04 PM, Robert Schroll <rschr...@gmail.com> wrote: > On Fri, Oct 23, 2015 at 8:38 AM, Jani Monoses <jani.mono...@gmail.com> > wrote: > >> I have searched in vain for an example of a minimal use of ContentStore - >> such that imported files do not by default end up under ~/.cache where they >> will be deleted from. >> > > This may or may not be your problem but: There is a bug wherein a file > imported into a ContentStore with ContentType.All is sent to ~/.cache/ > instead of of ~/.local/share/. > https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429691 > > If that's not the problem, let me know. I have an example using the > ContentStore somewhere around here > > Robert > > -- 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 ContentStore example?
> > pull-import branch. I added it in this commit [4]. As you'll see, it's > pretty easy to use. You just need to create a ContentStore object and pass > it as an argument to the peer.request() calls. > > Thanks, I could not find which API call is passed the the store object :/ With this change the pull-imported file gets put in the right place, however duplicate imports get aborted. I already retry imports on aborts because they used to happen previously too for unknown reasons. Now if I try to import the same photo, it will abort with no additional information, and I am not sure how to pass which photo was picked back to the app. The use case is adding attachments to messages, so duplicates can occur, and importing is only a prerequisite of this. Can I get the URL of the picked item even when it aborted? ISRT the content hub silently handles duplicates, so I thought the import would succeed, it would just reuse/overwrite the previous file named the same. Jani -- 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] Popup menus for action buttons?
Thanks for the detailed answer Tim,
I was trying to emulate the way an Android app groups its actions, but I'll
think about alternative designs too.
And I'll likely give the new API a try as well once it's landed :)
Jani
On Thu, Oct 22, 2015 at 10:15 PM, Tim Peeters <tim.peet...@canonical.com>
wrote:
> Hello Jani,
>
> There was a design decision that we only have one "overflow button" (the
> button that opens the popover) on the right side in the header, and the
> other actions are in the header directly, so you may want to discuss with
> the designers if they have suggestions for your app how to group actions
> instead of having multiple overflows.
>
> Technically, with the "old" header (that you configure using Page.head) it
> is not possible to have multiple overflow popovers. However, I am currently
> finishing some work to have a new, more flexible, header API. That work
> should land by the end of this month.
>
> With the new API (you need at least
> qtdeclarative5-ubuntu-ui-toolkit-plugin
> version 1.3.1688+15.10.20151018.1-0ubuntu1 or even better the version that
> we will land next week), what you ask for is possible, but it requires some
> hacking around the default behavior of the actions in the header. I am not
> recommending this approach, but if you want to try it out for your app, you
> can start with this:
>
> import QtQuick 2.4
>
> import Ubuntu.Components 1.3
>
> import Ubuntu.Components.Popups 1.3
>
>
> MainView {
>
> width: 800
>
> height: 600
>
> Page {
>
> header: PageHeader {
>
> title: "Multiple overflows."
>
> trailingActionBar {
>
> actions: [
>
> Action {
>
> iconName: "settings"
>
> text: "list 1"
>
> },
>
> Action {
>
> iconName: "attachment"
>
> text: "list 2"
>
> }
>
> ]
>
>
> delegate: AbstractButton {
>
> id: button
>
> styleName: "IconButtonStyle"
>
> action: modelData
>
> height: parent ? parent.height : undefined
>
> onTriggered: {
>
> if (action.text == "list 1") {
>
> PopupUtils.open(popover1Component, button);
>
> } else if (action.text == "list 2") {
>
> PopupUtils.open(popover2Component, button);
>
> }
>
> }
>
> }
>
> }
>
>
> Action {
>
> id: action1a
>
> iconName: "settings"
>
> text: "1A"
>
> }
>
> Action {
>
> id: action2a
>
> iconName: "settings"
>
> text: "2A"
>
> }
>
> Component {
>
> id: popover1Component
>
> ActionSelectionPopover {
>
> id: popover1
>
> contentWidth: units.gu(20)
>
> actions: [action1a]
>
> }
>
> }
>
> Component {
>
> id: popover2Component
>
> ActionSelectionPopover {
>
> id: popover2
>
> actions: [action2a, action1a]
>
> contentWidth: units.gu(20)
>
> }
>
> }
>
> }
>
> }
>
> }
>
>
> Note that you need a super new version of the UI toolkit for this to work,
> since the Page.header property and PageHeader component were only
> introduced this week. This code can be a starting point, but it is probably
> not the optimal way to do things (for example you could have only one
> popover component that you configure to show different actions, and you
> could put that code in a separate qml file).
>
> An alternative to this, instead of using the leading ActionBar of the new
> PageHeader is to create your completely custom header in which you can put
> your own buttons that open the popovers, without making use of the
> toolkit-provided ActionBar where you have to use Actions to do it.
>
> After tomorrow, I will be on holidays so I will not be able to answer more
> of you
[Ubuntu-phone] Popup menus for action buttons?
Hello, what is the best way to make a custom menu like to the one that is created when the number of action buttons is too large to fit the header and several of them are grouped under a navigation icon? I'd like to use one when pressing an existing action button in the header, to group related actions. thanks Jani -- 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] Permissions dialog for address book contacts?
Hello, as it was brought up before on this list and elsewhere, regular apps do not have direct access to address book contacts, and for good reason. One can get vcards via the content hub interactively, whereas the avatars are not accessible even there, needing the QtContacts API. Was the possibility of allowing direct AddressBook DBus and QtContact accesses gated by a nice Allow/Deny dialog like we now have for the camera? This would be easier both for developers and friendlier for users IMHO. Am I missing a reason why this is not possible technically? thanks Jani -- 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] Permissions dialog for address book contacts?
> > Yes you can. > VCards contains the avatar encoded in a base64 string (VCARD > standard). You will need to parse the vcard and decode that on your > side. > If you are receiving vcards without avatar please report a bug. > You are right, thanks :) I did not see this before, I guess my contacts did not have avatars set in the address book, and a discussion from a few days back on this list made me think it is currently not supported. cheers Jani -- 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] API to get contact avatar?
Hi Kyle, are these scopes unconfined - their security manifest suggests so? From Renato's answer I gather the QtContacts is not accessible to regular 3rd party apps. thanks Jani On Mon, Oct 5, 2015 at 6:49 PM, knitzsche <kyle.nitzs...@canonical.com> wrote: > Hi Jani, > > My calls-scope and texts-scope both show the contact's avatar when there > is one. > > See around this: > http://bazaar.launchpad.net/~calls-scope-team/calls-scope/calls-scope-trunk/view/head:/src/query.cpp#L247 > > Cheers, > Kyle > > > On 10/02/2015 11:26 AM, Jani Monoses wrote: > > Hello, > > is there an API to get an address-book contact's avatar via the content > hub? > I know one can get a vcard's url that way, but that does not contain > avatar info. > > thanks > Jani > > > > > > -- 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] framework and security policy changelogs?
Hello, while wondering whether I should bump the framework version of an app from 14.10 to 15.04 and the security policy version from 1.2 to 1.3 (or even 15.1 as click-review suggests?) I could use some information on what had changed between these versions. Any pointers? thanks Jani -- 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] TextSecure client prerelease
Hello, here's an alpha release of a TextSecure client written in Go for interested developers and early users. https://github.com/janimo/textsecure-qml cheers, Jani -- 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] Removing old channels from the image server?
Hello, there are a few channels on the image server that are very likely not in use anymore and the removal of which is unlikely to affect anyone. Is there a plan on cleaning up the list? A mix of customization channels with no easy way to tell which is maintained, and old saucy channels are the ones that come to mind. http://system-image.ubuntu.com/ubuntu-touch/ thanks Jani -- 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] Kernel configuration check script
While the porting wikipage has most of the kernel config options needed by Ubuntu Touch listed, it can be error prone to add and check them being correctly enabled. This script can suggest whether anything is missing from a given config file (it can be a source controller defconfig, a generated .config or an uncompressed /proc/config.gz) https://gist.github.com/janimo/0d559c648ab8874b8fa9 -- 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] Skipping GPG verification in recovery
On Wed, May 14, 2014 at 12:30 AM, Ricardo Salveti de Araujo ricardo.salv...@canonical.com wrote: On Tue, May 13, 2014 at 7:02 AM, Jani Monoses jani.mono...@canonical.com wrote: Hello, during bringup and development it is helpful to skip image signature verification and not worry about setting up GPG keychains. A common way to do it is to just add a return 0 to the verify_signature() function to the local copy of system-image-upgrader. What do you think of this patch to allow this to be toggled by developers without having to change the script itself? Sounds fine, please push it to gerrit. Cheers, -- Ricardo Salveti de Araujo Done, thanks. -- 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] [ANN] Alternate local image server setup
Hello, for my use case of flashing custom device tarballs while keeping up with Ubuntu rootfs tarballs from various channels I used a server tool setup that is an alternative to the one backing system-image.ubuntu.com [1] The idea is to use a recent ubuntu-device-flash client (phablet-flash wont' work with this setup) and to point it to the URL served. Only the device tarball needs to be managed by you, the ubuntu and version tarball requests will be forwarded to the Ubuntu image server. GPG verification will need to be disabled in recovery[2] - this is for development only for now, for production you likely want to download and sign all images with your keys. Other porters may find this useful. The easiest way to start is * Make sure you have Go 1.2 installed and GOPATH set up * $ go get github.com/janimo/imageserver * $ imageserver The tool will suggest what to do in order to have a working setup, for details see https://github.com/janimo/imageserver/wiki/Documentation Once you have it running you can use something like ubuntu-device-flash --server=http://localhost:10080 feedback is welcome Jani [1] https://wiki.ubuntu.com/ImageBasedUpgrades/ServerSetup [2] For example by adding return 0 as the first line in the verify_signature() function in system-image-upgrader. -- 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] Upcoming renaming of all system-image channels
Let me know if you have any questions or concerns about this. nitpick: So is the 'Touch' in Ubuntu Touch still being used in some contexts? I get conflicting messages as to whether we drop it everywhere, in promotional material only or nowhere at all :) Jani -- 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] Device-Specific configs in debs
I also agree the Android build tree should have these even though they belong to the Ubuntu filesystem. The main reason is I am sure most OEMs (and even some of us) prefer copying a few files around and have as direct control over them as possible vs. building a .deb just for them with all the PPA/image build hooks/hack-to-deploy cycle latency. In this custom case the elegance of having source packages is trumped IMHO by pragmatism. One way of doing it is having them set as part of the install and upgrade steps. For the BQ we now unpack the Ubuntu zip and then have a script adb push over the dev specific files to the Ubuntu root. So it does not need to be bind mounted or copied at Ubuntu boot time, no Ubuntu side logic is needed. Something similar needs to be hooked into the system image upgrade, so they do not get lost. Again, I agree this is not very elegant, but seems the one that most 3rd parties could get on board with as it requires almost 0 Ubuntu dev specific knowledge. Jani On Tue, Mar 4, 2014 at 5:45 PM, Ondrej Kubik ondrej.ku...@canonical.comwrote: I think we agree here, have device specific files in android system.img and bind mount this wherever it is needed during boot, so Ubuntu can see it. Custom package should not have anything hw specific Cheers // Ondrej On Tuesday, February 11, 2014, Ricardo Salveti de Araujo ricardo.salv...@canonical.com wrote: On Mon, Feb 10, 2014 at 1:35 PM, Sergio Schvezov sergio.schve...@canonical.com wrote: On 10/02/14 12:20, Jamie Strandboge wrote: On 02/10/2014 08:56 AM, Chris Wayne wrote: Jamie, Thanks for reviving this, it definitely needs more action. I don't think the plan should be to move it into a different deb package shipped in the rootfs. I thought the plan was to ship everything device-specific in the device tarball? (That is after all, the whole purpose of this thread :) ) I don't have a strong opinion on this (though it sounds like others might), but for apparmor, I just need a decision on the directory and then I can move the existing hardware-specific policy to it. Do note, this directory must exist and will need to be created by apparmor-easyprof-ubuntu, which means that this directory will exist on all systems with apparmor-easyprof-ubuntu installed (ie, desktop systems with the sdk installed now and all desktop systems once we move to unity8). Would it be acceptable to make (some part of) /usr/share/apparmor/hardware/* read/write via /etc/system-image/writable-paths so the device tarball can unpack there or is there some hard requirement that it must live in /custom? (I'm not super keen on /custom on desktop systems, but maybe that is exactly what we want-- OEMs for desktop system could ship policy there too) I was hoping for /system/etc/apparmor and have it bundled in the device specific repo in the android build, but if it has exist on every install and must exist, then it doesn't seem that good. I would like to differentiate customization from hw enablement. Yeah, the ideal case here would be for the rules to be provided by the system.img (android rootfs), and linked at some known place when booting Ubuntu. Cheers, -- Ricardo Salveti de Araujo -- 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 -- 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] [Porting] How to create a system.img for your port
Thanks, I have added most of the info from your email in a new wikipage https://wiki.ubuntu.com/Touch/Deploying Please review it and feel free to contribute to it directly Jani On Tue, Jan 21, 2014 at 8:18 PM, f69m launch...@f69m.de wrote: Hello, As the official porting guide is a little incomplete concerning the latest changes, I decided to put together an email with my findings. In the following, I will describe, how to manually create a system.img for the new loop-mounted flipped container layout. Building the phablet-trusty Android tree for your device creates two files we need later: - The boot image with your kernel and the Ubuntu initrd. - The Android system image, including the Android initrd image as boot/android-ramdisk.img. You can find those files in the Android output directory out/target/product/DEVICE. In the following we will refer to them as boot.img and android-system.img respectively. Note that the system image is usually named system.img, but we don't want to confuse it with the Ubuntu Touch system image we are going to create. We also need the Ubuntu root filesystem that can be downloaded from https://system-image.ubuntu.com/. The Android tree contains the script build/tools/get-tarball-url.py that prints the full URL of the latest full image available. In the following we will refer to the downloaded file as ubuntu-rootfs.tar.xz. Now we start by allocating a huge sparse file and create an ext2 filesystem on it. Then we loop-mount the new image on directory system. Note that we can make it quite big with little cost, we are going to shrink it later. fallocate -l 2G system.img mke2fs -F system.img mkdir system sudo mount -o loop system.img system The following steps are all run as root using sudo, so all permissions are preserved and new files are created as root. We need to extract the Ubuntu root filesystem and drop the Android system image at the right place. sudo tar -xJ --numeric-owner -f ubuntu-rootfs.tar.xz system sudo cp android-system.img system/var/lib/lxc/android/system.img Now is the time to drop the device-specific configuration files. Make sure, they are also created by user root. Finally unmount the new image: sudo umount system rmdir system Now we shrink the new 2 GB filesystem to its minimal size. e2fsck -yf system.img resize2fs -M system.img e2fsck -yf system.img So far we have reduced the size of the filesystem, but not the size of the image file itself. Run dumpe2fs and look for the values Block size and Block count. Their product is the minimum image SIZE in bytes, we need for truncating the image file. dumpe2fs system.img | less truncate -s SIZE system.img The system.img is now fine for read-only mounting, but leaves no headroom for creating or editing files. If we want to mount the system image writable in developer mode, we should add some free space to it, say 500 MB: truncate -s +500M system.img resize2fs system.img e2fsck -yf system.img Now we can flash the boot.img mentioned above to the boot partition and and our new system.img to /data/system.img. Then reboot, and Ubuntu Touch should come up fine. That's it! Hope it helps other porters... -- 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] Multiple frameworks for apps
The code currently in lp:click, which will become version 0.4.14, extends the framework manifest field a bit to support this. With this, assuming appropriate declaration files in /usr/share/click/frameworks/, apps will be able to do something like this: frameworks: ubuntu-14.04-qml, ubuntu-14.04-html5 Should this be framework: ubuntu-14.04-qml, ubuntu-14.04-html5 that is the current manifest key name did not change to the plural form ? Jani -- 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] A Go tool for building click packages
Hello,
To learn some more Go and also about Click package internals I wrote a tool
that modulo bugs and a few corner cases replicates what the official click
build and click buildsource commands do
I only tested it very briefly and on a single package so far.
If you have Go installed and GOPATH set up, try it out:
$ go get github.com/janimo/goclick
[...]
$ goclick
Usage: goclick COMMAND [options]
Commands are as follows ('click COMMAND --help' for more):
build Build a Click package.
buildsource Build a Click source package.
contents Show the file-list contents of a Click package
file.
info Show manifest information for a Click package.
One use of such a tool is building Click packages by only installing a
single binary and no other deps. It depends on a call to du at the moment
but once that is gone it could in theory be used even on Windows.
Jani
--
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] [REMINDER] Filing bugs against the Android bits
Hello, until we have a better patch review and tracking system set up please use the android package in Ubuntu for filing bugs and sending patches against the Android components. https://bugs.launchpad.net/ubuntu/+source/android This is for generic Ubuntu changes and for the officially supported devices (Nexus + goldfish) and not for particular 3rd party device support. Those are not tracked in Launchpad and are still better served by their respective wikipages. -- 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] AOSP 4.4 based port status
Hello, The instructions in the wiki [1] now work for the AOSP 4.4 based tree. It builds, but when booted on the Nexus 4 there are some Binder transaction errors likely preventing anything but having the container started. The hybris changes I did to adapt to 4.4 APIs definitely need more work but probably other areas are missing bits. [1] https://wiki.ubuntu.com/Touch/AOSPBuild -- 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] [DOC] Porting to non-CyanogenMod trees
Hello, I started a wikipage on how to use our patches on Android trees that are based on AOSP, CodeAurora or others besides CyanogenMod. The information is not new but it had not been written up in a single place before. https://wiki.ubuntu.com/Touch/PortingNewTree Jani -- 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] AOSP based phablet branches
Hi, More progress has been made. This wikipage describes how to build and boot an AOSP 4.2.2 based system.img on the Nexus 4. https://wiki.ubuntu.com/Touch/AOSPBuild -- 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] AOSP based phablet branches
Hello, for those wanting to base their ports on AOSP instead of CyanogenMod there are now work in progress branches based on the android tags 4.2.2_r1 (builds fine) 4.3.1_r1 (builds apart from hybris) and 4.4_r1 (porting work in progress) The branch manifests include the ubuntu specific projects such as hybris, platform-api and external/gpg so that only vendor blobs need adding before starting a build. Here's how to check out the 4.2.2 based branch $mkdir phablet-4.2.2 cd $_ $repo init -u git://phablet.ubuntu.com/aosp/platform/manifest.git -b phablet-4.2.2_r1 (here you can optionally pass --reference /path/to/aosp/mirror) $repo sync -j 4 This is in an entirely separate AOSP based source tree, unlike the phablet-4.2.2_r1 branch that is piggybacked on the CyanogenMod based repository. Following AOSP assures we can always branch off the latest released version without waiting for CyanogenMod being available for that version first. Jani -- 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] Porting issues
Hi Dmitry, (adding back the list so others can follow and add more information) The system.img built from the AOSP-like source tree indeed now contains some Ubuntu components but that is ok, those are needed as the glue between Android and the Ubuntu system. And the image that you need to boot is the trusty-preinstalled-touch-armhf Ubuntu image from here http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ That boots as a regular Ubuntu desktop, but should have the android system.img under /var/lib/lxc/android so it can start it inside an LXC container. So the var/lib/lxc/android/system.img that is created should be the regular system.img under out/target/product/tilapia in your tree and then you need to copy it over the device in that location. Jani On Wed, Nov 6, 2013 at 10:15 AM, Dmitry Smirnov divis1...@gmail.com wrote: Hi Jani, ok, so the /data/system.img is the ububtu system image and it in turn should contain android's system image. The problem is that after I merged phablet, I do not have the 'pure' android system image - it already contains ubuntu and the android. Which components of the android image will be used by ubuntu? build.prop and fstab.device? BTW, as i said I use tilapia build for comparison, I did not realize when this var/lib/lxc/android/system.img is created (I looked in recovery scripts too). Is this some bug or should I use some other device (ex. mako) ? Dmitry 2013/11/6 Jani Monoses jani.mono...@canonical.com Hi, that system.img should be the one built from your CodeAurora tree and then turned into a regular ext4 image on your build machine $simg2img system.img new.img $resize2fs -M new.img In recovery mode #mkdir a #mount /data/system.img a On the host $adb push new.img /a/var/lib/lxc/android/system.img $adb reboot Jani On Wed, Nov 6, 2013 at 9:40 AM, Dmitry Smirnov divis1...@gmail.comwrote: Hi, I'm trying to port ubuntu-touch to a device but have issues with this. I've ported all the changes from phablet-saucy branch to my code base (non-CM, pure codeaurora). I decided to skip recovery procedures because I can build all the images (kernel, system, userdata, etc) and try to run the phone using just fastboot to flash the phone. The phone starts, initrd can run, but it fails to complete boot sequence: there is no /root/var/lib/lxc/android/system.img for ex. and I did not find who and when can generate it. I'm using pure phablet build for tilapia for comparison of the builds and also cannot find that /root/var/lib/lxc/android/system.img (even in recovery image) This causes device to be unrecognized (unknown) and probably causes some other steps to fail. Also, /root is read-only for some reason and I also suspect this prevents the system to boot: + mkdir -p /root/android mkdir: can't create directory '/root/android': Read-only file system What I'm doing wrong? WBR, Dmitry -- 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] Porting issues
Hi you need to download that exact zip from the Ubuntu servers. It is the full Ubuntu userland. the cm-...tilapia.zip is the Android side, same as system.img and boot.img but packaged in a zip for easy update via the recovery image. So the Ubuntu side is prrebuilt for armhf and should be almost identical for each device. On this page http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/ you can see boot, recovery and system.img files which are the regular ones built from an Android tree for all four supported Nexus devices. Then there is also http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/saucy-preinstalled-touch-armhf.tar.gzwhich is the Ubuntu rootfs and which is device independent. Also you do not fastboot flash system system.img . It is not the Android image that will be the rootfs. It is Ubuntu from the above zip, and the Android system.img lives under /var/lib/lxc/android and gets mounted only after the Ubuntu userland is booted up. So first you need to make sure you boot into Ubuntu and not Android. You have to use the ubuntu-touch-generic-initrd package as the initrd as seen in build/core/Makefile Jani On Wed, Nov 6, 2013 at 11:33 AM, Dmitry Smirnov divis1...@gmail.com wrote: One more question. Manual Download Installation section on https://wiki.ubuntu.com/Touch/Install mentions a saucy-preinstalled-touch-armel+grouper.zip as a second step in this process. In case of my own port, should it become something like cm-10.1-20131101-UNOFFICIAL-tilapia.zip which is generated by Android build? Also, it is unclear for me whether this step is really needed after fastbooting recovery, boot, system in the first step? 2013/11/6 Jani Monoses jani.mono...@canonical.com - Either way, you'll need the Ubuntu preinstalled image besides the one you're going to build with the instructions below. You can find the Ubuntu preinstalled images herehttp://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/ . Probably there should be some instructions where to put it (I mean for usual recovery procedure) I agree the documentation leaves a lot to be desired. I mostly inspected the installed software on a flashed nexus4 , but for people porting to new hardware without seeing Ubuntu on one of the supported devices the docs by themselves are indeed confusing. Jani -- 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] Porting issues
On Wed, Nov 6, 2013 at 12:26 PM, Dmitry Smirnov divis1...@gmail.com wrote: I'm sorry Jani, but I'm lost :-) Please correct me if I'm wrong. Sorry, I forgot to say that what I was talking about is the newer (so called flipped-image) method of running Ubuntu, where Android's system.img is inside an LXC container, and this is the default on Nexus devices. For porters of 3rd devices the previous method (un-flipped) can still be used, and that is indeed as you described, flashing the Android images as with regular Android and then provide the Ubuntu.zip image from cdimage.ubuntu.com and have recovery flash it. Then Android will boot as usual and Ubuntu will be inside a chroot. This is the legacy method (used by phablet-flash cdimage-legacy as well) . That Manual Download Installation tells about 3 steps: 1. Flash boot, recovery, system images. I presume these images should contains some phablet code (at least for recovery - support for autodeploy, otherwise next step could fail). This cannot be 'pure' CM/AOSP or vendor images. Thus I assume it is phablet-enabled Android side Right, phablet-enabled Android side. I think the phablet/cm-10.1 branch is more appropriate for this work, phablet/phablet-saucy may have an assumptions about flipped image and may not work in legacy mode. 2. Install some zip file for specific device. In case of 4 supported devices I can get it from cdimage.ubuntu.com. Alternatively, I can build it by myself (ex. for device that is not supported on cdimage.ubuntu.com, cm-..tilapia.zip) If you flashed boot/recovery and system.img you do not need this step. cm-...tilapia.zip is a way to update the existing boot and system.img on a device, but if you used fastboot already to flash those there is no need to. Alternately just flash recovery via fastboot and then autodeploy cm---tilapia.zip. These zips contain boot.img and content of system folder. At first glance these are the same boot.img and content of system.img in step #1 3. Install some zip which in turn contain device-independent tar.gz Right, this one requires autodeploy via recovery, it is not covered by the standard fastboot style upload methods. Step #2 seems unnecessary but does not impact the install procedure. Right. Jani 2013/11/6 Jani Monoses jani.mono...@canonical.com Hi you need to download that exact zip from the Ubuntu servers. It is the full Ubuntu userland. the cm-...tilapia.zip is the Android side, same as system.img and boot.img but packaged in a zip for easy update via the recovery image. So the Ubuntu side is prrebuilt for armhf and should be almost identical for each device. On this page http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/ you can see boot, recovery and system.img files which are the regular ones built from an Android tree for all four supported Nexus devices. Then there is also http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/20131018/saucy-preinstalled-touch-armhf.tar.gzwhich is the Ubuntu rootfs and which is device independent. Also you do not fastboot flash system system.img . It is not the Android image that will be the rootfs. It is Ubuntu from the above zip, and the Android system.img lives under /var/lib/lxc/android and gets mounted only after the Ubuntu userland is booted up. So first you need to make sure you boot into Ubuntu and not Android. You have to use the ubuntu-touch-generic-initrd package as the initrd as seen in build/core/Makefile Jani On Wed, Nov 6, 2013 at 11:33 AM, Dmitry Smirnov divis1...@gmail.comwrote: One more question. Manual Download Installation section on https://wiki.ubuntu.com/Touch/Install mentions a saucy-preinstalled-touch-armel+grouper.zip as a second step in this process. In case of my own port, should it become something like cm-10.1-20131101-UNOFFICIAL-tilapia.zip which is generated by Android build? Also, it is unclear for me whether this step is really needed after fastbooting recovery, boot, system in the first step? 2013/11/6 Jani Monoses jani.mono...@canonical.com - Either way, you'll need the Ubuntu preinstalled image besides the one you're going to build with the instructions below. You can find the Ubuntu preinstalled images herehttp://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/ . Probably there should be some instructions where to put it (I mean for usual recovery procedure) I agree the documentation leaves a lot to be desired. I mostly inspected the installed software on a flashed nexus4 , but for people porting to new hardware without seeing Ubuntu on one of the supported devices the docs by themselves are indeed confusing. Jani -- 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] Porting issues
unflipped will not work anymore, all the super evil hacks it used are gone from the rootfs since over 6 months, please only use (and recommend) the flipped method. From the recent thread on this list saying the cdimage-legacy option of phablet-flash is to be kept around I figured that unflipped images are still around Jani -- 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] Porting issues
Hi, while I have not tested it, I had a go at porting the recovery patches ported to AOSP 4.2.2 in the phablet-4.2.2_r1 branch of the main repositories and those may serve as a start for CodeAurora based trees. Jani On Wed, Nov 6, 2013 at 12:59 PM, Dmitry Smirnov divis1...@gmail.com wrote: Ok, thanks for clarifications! I see I need to finish porting phablet changes into recovery to make my life simpler :-) 2013/11/6 Jani Monoses jani.mono...@canonical.com unflipped will not work anymore, all the super evil hacks it used are gone from the rootfs since over 6 months, please only use (and recommend) the flipped method. From the recent thread on this list saying the cdimage-legacy option of phablet-flash is to be kept around I figured that unflipped images are still around Jani -- 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
[Ubuntu-phone] Patches against AOSP 4.2.2_r1
Hello, The phablet/phablet-4.2.2_r1 branches in the phablet repositories are adapted so they apply against a clean AOSP 4.2.2 tree. This is work in progress I am testing with Nexus 4. While it does not yet boot into Unity just into a shell it can help those basing their ports on something closer to AOSP than CyanogenMod. This set of scripts lets one export patches from and apply patches to AOSP like trees, for example getting the above mentioned phablet changes and applying them against vanilla AOSP. https://github.com/janimo/phablet-patches Jani -- 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] Porting issues
Hi, that system.img should be the one built from your CodeAurora tree and then turned into a regular ext4 image on your build machine $simg2img system.img new.img $resize2fs -M new.img In recovery mode #mkdir a #mount /data/system.img a On the host $adb push new.img /a/var/lib/lxc/android/system.img $adb reboot Jani On Wed, Nov 6, 2013 at 9:40 AM, Dmitry Smirnov divis1...@gmail.com wrote: Hi, I'm trying to port ubuntu-touch to a device but have issues with this. I've ported all the changes from phablet-saucy branch to my code base (non-CM, pure codeaurora). I decided to skip recovery procedures because I can build all the images (kernel, system, userdata, etc) and try to run the phone using just fastboot to flash the phone. The phone starts, initrd can run, but it fails to complete boot sequence: there is no /root/var/lib/lxc/android/system.img for ex. and I did not find who and when can generate it. I'm using pure phablet build for tilapia for comparison of the builds and also cannot find that /root/var/lib/lxc/android/system.img (even in recovery image) This causes device to be unrecognized (unknown) and probably causes some other steps to fail. Also, /root is read-only for some reason and I also suspect this prevents the system to boot: + mkdir -p /root/android mkdir: can't create directory '/root/android': Read-only file system What I'm doing wrong? WBR, Dmitry -- 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] Trusty image 10 (20131031.1) now available
Hi, how hard would it be to provide merged changelog files between released images as opposed to the separate daily builds? For regression testing it may help easily finding the changes that introduced a bug based only on users reporting the image number they were using. Jani On Mon, Nov 4, 2013 at 12:06 PM, Alan Pope alan.p...@canonical.com wrote: Hi, Trusty image #10 is now available. The following changelogs detail the updates since the last promoted image #5 (20131024). http://people.canonical.com/~j-lallement/touch/changes/20131025.html http://people.canonical.com/~j-lallement/touch/changes/20131029.html http://people.canonical.com/~j-lallement/touch/changes/20131029.1.html http://people.canonical.com/~j-lallement/touch/changes/20131031.html http://people.canonical.com/~j-lallement/touch/changes/20131031.1.html Please update your device and test. Cheers, -- Alan Pope Engineering Manager Canonical - Product Strategy +44 (0) 7973 620 164 alan.p...@canonical.com http://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 -- 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] Using repo only to get the Android sources
The modules ubuntu/platform-api and ubuntu/hybris have recently been mirrored into git repos, so all the tree can now be checked out using only the tools already familiar to Android ROM developers and builders, namely repo and git. ubuntu-dev-bootstrap is still a working wrapper but it is not as necessary as when it also made sure it checks out bzr branches. More details on how to check out the source tree and set up local AOSP and/or phablet mirrors are here https://wiki.ubuntu.com/Touch/AndroidDevel -- 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] Error when fetch libhybris and building libhybris
Hi what version of the ROM tree you have checked out? In the latest phablet-saucy envsetup.sh no longer pulls hybris, as the latter has its own git repo in ubuntu/hybris that is fetched by repo sync. So try updating to the latest tree first and see if you encounter any errors. Jani On Mon, Oct 14, 2013 at 10:21 AM, 彥瑾 coldnew...@gmail.com wrote: Hello everyone: I'm try to porting latest ubuntu touch for my tf700 tablet, when I use *source build/envsetup.sh* to fetch the libhybris library, it encountered error: * pull-lp-source: Downloading libhybris version saucy pull-lp-source: Error: Failed to download: https://launchpad.net/ubuntu/+archive/primary/+files/libhybris_saucy.dsc: 404 Not Found rm: cannot remove `libhybris*.tar.gz': No such file or directory rm: cannot remove `libhybris*.dsc': No such file or directory mv: cannot stat `libhybris*': No such file or directory* To prevent this error, I modify the build/envsetup.sh script, and change * HYBRIS_SRC_SERIES=saucy* to * HYBRIS_SRC_SERIES=0.1.0+git20130606+c5d897a-0ubuntu34* however, when I build the code, it stop shows error like: * ubuntu/hybris/compat/camera/camera_compatibility_layer.cpp:116:1: error: 'NativeBufferAlloc' does not name a type ubuntu/hybris/compat/camera/camera_compatibility_layer.cpp:119:1: error: 'NativeBufferAlloc' does not name a type ubuntu/hybris/compat/camera/camera_compatibility_layer.cpp:122:19: error: 'NativeBufferAlloc' has not been declared* How can I solve these problem for building ubuntu touch success? I know it's lack of document on how to porting it, but it's really wired that build failed on any ubuntu* source. -- 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
[Ubuntu-phone] [PATCH] Remove references to uchroot
These patches remove the uchroot git repo from the phablet-saucy manifest and the uchroot and ubuntu_chroot modules from the build list. They are not used in the flipped model which has been the default for a while and which is the only one supported in the phablet-saucy branch. 0001-Remove-references-to-unused-modules.patch Description: Binary data 0001-Remove-unused-uchroot-repo.patch Description: Binary data -- 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] Building i386 touch images locally?
As an experiment I'd like to get a local build of the daily Ubuntu touch images for i386. Can anyone get this working or reproduce an error? I get maliit-keyboard dependencies not found while debootstrapping. #!/bin/bash mkdir auto ln -sf /usr/share/livecd-rootfs/live-build/auto/* auto/ export PROJECT=ubuntu-touch SUITE=saucy ARCH=i386 PREINSTALLED=true IMAGEFORMAT=plain sudo lb clean lb config sudo lb build -- 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] Huawei Ascend P1 porting experience notes
Hello, I had a Huawei Ascend P1 (u9200) phone booting Ubuntu Touch a few months ago and managed to successfully update the port to use the latest sources today. My attempt to update to the new flipped model and to use the phablet-saucy branch of the Android ROM resulted in the following experiences, which I also summarized in the new porting wikipage. 1) No kernel config changes were needed, in particular I did not have to add CONFIG_VT, it works with it disabled. 2) The vpid kernel patch is not needed in the new container model, so it is no longer mentioned in the wiki either. 3) I had to pass console=ttyO0 instead of console=ttyGS2, the latter being whatever the original factory ROM used, and the former one of the few tty devices created by Ubuntu. 4) Udev rules were needed, generated from ueventd.rc as seen in the wikipage and added to the lxc-android-config package in saucy. 5) The device node for the GPU needed an explicit udev rule to allow non-root user access, or Unity would not start. 6) There appears to be a bug related to starting the Android sensorservice. If it fails to start for whatever reason, Unity won't start either. I worked around this by changing ystem/core/rootdir/init.rc to put sensorservice back into the main class instead of late_start. A proper solution is needed though as this affects multiple devices. 7) When logged into Ubuntu I found /usr/bin/test_sf , test_egl and the rest of the test apps there helpful. A problem that this port has in common with the initial one is that hardware vsync is not working well, making the UI very sluggish. Last time I worked around that by hardcoding software vsync in the SurfaceFlinger sources and this is what I resorted to now. This is intrusive and not upstreamable though, so a proper fix is needed here. cheers Jani -- 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] patch to fix the kernel cmdline handling
Do you have an udev rule setting the graphics related device node accessible by non-root too ? On Fri, Aug 2, 2013 at 11:21 PM, András Mamenyák mameny...@gmail.comwrote: And logcat: http://paste.ubuntu.com/5941366/ On Fri, Aug 2, 2013 at 10:05 PM, András Mamenyák mameny...@gmail.comwrote: IT WORKS! Thank you, my Note 10.1 saucy port now boots! But to a black screen... Please look at my dmesg: http://paste.ubuntu.com/5941329 On Fri, Aug 2, 2013 at 8:35 PM, Max Wällstedt max.wallst...@gmail.comwrote: Thanks, that worked, but I also had to unset CONFIG_CMDLINE_FORCE to get the recovery. I can however only boot into Ubuntu once. After the first reboot it only enters a state of black screen and no adb. Thanks for all your hard work on Ubuntu Touch and i9100, it really has moved things forward! 2013/8/2 Oliver Grawert o...@ubuntu.com hi, at http://paste.ubuntu.com/5939625/ is a patch that makes sure the kernel cmdline string is appended (instead of prepending it) to the bootloader args, this way we can put console=tty1 into the kernel cdmline string and have it override the console=ram the bootloader sets by default. using: CONFIG_CMDLINE_EXTEND=y CONFIG_CMDLINE=console=tty1 in cyanogenmod_i9100_defconfig with the patch will make recovery work again and let us boot into the flipped container without having to use something hardcoded. i'm CCing the mailing list since i can imagine that other samsung devices might have similar issues with hardcoded cmdlines in the bootloader. ciao oli -- 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 -- 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] Mirroring the repository
Hello, A new mirror manifest is now in place so local mirrors of the phablet tree can be created mkdir phablet-mirror cd phablet-mirror repo init -u git://phablet.ubuntu.com/CyanogenMod/mirror/manifest --mirror repo sync To init a working tree from a local mirror do repo init -u /path/to/phablet-mirror/Cyanogenmod/android.git -b phablet-saucy repo sync Jani -- 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] [PATCH] platform manifest fetch URL
Hi, Creating a new repo under mirror/manifest with master branch only containing the attached file will allow creating a local mirror of the phablet tree (passing reference is optional but helps share the majority of git objects with an AOSP mirror if you already have one locally) $mkdir phabletmirror; cd phabletmirror $repo init -u git://phablet.ubuntu.com/CyanogenMod/mirror/manifest --mirror --reference /path/to/aospmirror $repo sync then $mkdir phablet;cd phablet $repo init -u /path/to/phabletmirror -b phablet-saucy will check out a working tree of the phablet-saucy branch without accessing the network. The previous patch with the relative path will need applying to phablet-10.1 before checking out with -b phablet-10.1 can take advantage of a local mirror. Jani On Fri, Jul 26, 2013 at 4:32 PM, Jani Monoses j...@ubuntu.com wrote: In order for the phablet repo to work when mirrored [1], the manifest used to checkout a working tree needs to use relative paths and not a hardcoded URL. This is what the AOSP manifests have as well. This patch applies to both the saucy and the phablet-10.1 branches. Jani [1] http://source.android.com/source/downloading.html#using-a-local-mirror -- 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 ?xml version=1.0 encoding=UTF-8? manifest remote name=phablet fetch=../.. / default revision=master remote=phablet sync-j=1 / project name=CyanogenMod/android_build / project name=CyanogenMod/android / project name=CyanogenMod/mirror/manifest / project name=CyanogenMod/android_abi_cpp / project name=CyanogenMod/android_bionic / project name=CyanogenMod/android_bootable_diskinstaller / project name=CyanogenMod/android_bootable_recovery / project name=CyanogenMod/android_development / project name=CyanogenMod/android_device_common / project name=CyanogenMod/android_device_generic_armv7-a-neon / project name=CyanogenMod/android_device_generic_armv7-a / project name=CyanogenMod/android_device_generic_common / project name=CyanogenMod/android_device_generic_goldfish / project name=CyanogenMod/android_device_generic_mips / project name=CyanogenMod/android_device_generic_x86 / project name=CyanogenMod/android_device_sample / project name=CyanogenMod/android_device_ti_panda / project name=CyanogenMod/android_device_lge_mako / project name=CyanogenMod/android_device_samsung_maguro / project name=CyanogenMod/android_device_samsung_manta / project name=CyanogenMod/android_device_samsung_tuna / project name=CyanogenMod/android_external_aac / project name=CyanogenMod/android_external_bouncycastle / project name=CyanogenMod/android_external_bsdiff / project name=CyanogenMod/android_external_busybox / project name=CyanogenMod/android_external_bzip2 / project name=CyanogenMod/android_external_chromium / project name=CyanogenMod/android_external_e2fsprogs / project name=CyanogenMod/android_external_expat / project name=CyanogenMod/android_external_flac / project name=CyanogenMod/android_external_freetype / project name=CyanogenMod/android_external_gcc-demangle / project name=CyanogenMod/android_external_genext2fs / project name=CyanogenMod/android_external_giflib / project name=CyanogenMod/android_external_gpg / project name=CyanogenMod/android_external_gtest / project name=CyanogenMod/android_external_harfbuzz / project name=CyanogenMod/android_external_icu4c / project name=CyanogenMod/android_external_jhead / project name=CyanogenMod/android_external_jpeg / project name=CyanogenMod/android_external_kernel-headers / project name=CyanogenMod/android_external_liblzf / project name=CyanogenMod/android_external_libnl-headers / project name=CyanogenMod/android_external_libogg / project name=CyanogenMod/android_external_libpng / project name=CyanogenMod/android_external_libvpx / project name=CyanogenMod/android_external_mksh / project name=CyanogenMod/android_external_openssl / project name=CyanogenMod/android_external_protobuf / project name=CyanogenMod/android_external_safe-iop / project name=CyanogenMod/android_external_skia / project name=CyanogenMod/android_external_sonivox / project name=CyanogenMod/android_external_speex / project name=CyanogenMod/android_external_stlport / project name=CyanogenMod/android_external_strace / project name=CyanogenMod/android_external_tinyalsa / project name=CyanogenMod/android_external_tremolo / project name=CyanogenMod/android_external_webp / project name=CyanogenMod/android_external_webrtc / project name=CyanogenMod/android_external_wpa_supplicant_6 / project name=CyanogenMod/android_external_wpa_supplicant_8 / project name=CyanogenMod/android_external_wpa_supplicant_8_ti / project name=CyanogenMod/android_external_yaffs2 / project
Re: [Ubuntu-phone] Fwd: Remove TI/panda support
On Thu, Apr 18, 2013 at 2:15 PM, Jani Monoses j...@ubuntu.com wrote: device/ti/panda seems not to be needed by our official devices, this patch removes it from the default manifest What do we benefit from removing it? Seems to me like it doesn't impact anything by being there, but rather allows users to build for that device should they choose to. The impact while small is the extra repo fetched even when not needed so some network and disk overhead and the possible confusion while browsing the source tree. AIUI there was a push to remove git repos that are not used by default and this patch came in response to favorable comments specifically about removing panda. cheers Jani -- 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] Is uchroot deprecated?
Hello, are non-flipped images still supported in some way? I see uchroot in the repo manifest and the kernel patch to proc/ mentioned in the porting guide. thanks -- 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] Ebook reader?
on a more capable environment server-side. Qt Quick apps have the distinct advantage of being native and therefore having access to some native capability. Taking the example of Monocle that I mentioned, it's entirely possible to write an ebook reader in pure client-side JavaScript in modern browsers right now. I'd love to be able to work like that with Qt Quick; To what degree is 'first class support for HTML5 apps' is there today in Ubuntu Touch? Wouldn't an existing JavaScript ebook reader like the one you mention do what you want? In the long run it would seem strange to me to have both a JavaScript/HTML5 and a QML alternative written for many popular apps given that the former will need to work anyway on most platforms. Jani -- 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] [PATCH] Fix mako kernel build with stock gcc 4.7
I just saw that the nexus 4 image build uses the linux-nexus4 kernel package from the official raring archives, and that already has build fixes included. So never mind this patch :) On Wed, Apr 24, 2013 at 5:15 PM, Jani Monoses j...@ubuntu.com wrote: These two patches allow arm-linux-gnueabihf-gcc 4.7.3 from Ubuntu 13.04 to build a booting mako kernel image. Patch 1) scripts/gcc-wrapper is a python tool that is used in some Qualcomm/Code Aurora kernels containing a whitelist of warning messages generated during the build and fail on any non-listed one. gcc 4.7 triggers many new warnings so I rather disabled the wrapper itself. This way it is also in line with the rest of non-Qualcomm kernels trees. Patch 2) Do not specify the inline qualifier for some functions that cannot be inlined by 4.7 and thus break building. The Linaro 4.7.2 gcc bundled with the Ubuntu Touch sources fails though as it defaults to using the gold linker (and has no support for -fuse-ld=bfd as Linaro gcc 4.8.1 has) and the gold linker cannot correctly link the kernel at the moment. cheers Jani -- 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] [PATCH] Enable dumpsys
The dumpsys tool is useful for getting information about the state of SurfaceFlinger and other services and is helpful when porting to a new device and debugging various HAL components. This patch enables it in the build. thanks Jani 0001-Build-dumpsys-tool.patch Description: Binary data -- 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] [PATCH] Fix mako kernel build with stock gcc 4.7
These two patches allow arm-linux-gnueabihf-gcc 4.7.3 from Ubuntu 13.04 to build a booting mako kernel image. Patch 1) scripts/gcc-wrapper is a python tool that is used in some Qualcomm/Code Aurora kernels containing a whitelist of warning messages generated during the build and fail on any non-listed one. gcc 4.7 triggers many new warnings so I rather disabled the wrapper itself. This way it is also in line with the rest of non-Qualcomm kernels trees. Patch 2) Do not specify the inline qualifier for some functions that cannot be inlined by 4.7 and thus break building. The Linaro 4.7.2 gcc bundled with the Ubuntu Touch sources fails though as it defaults to using the gold linker (and has no support for -fuse-ld=bfd as Linaro gcc 4.8.1 has) and the gold linker cannot correctly link the kernel at the moment. cheers Jani 0001-Do-not-build-using-gcc-wrapper.py.patch Description: Binary data 0002-Fix-build-with-gcc-4.7.patch Description: Binary data -- 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] Choice of included ARM toolchains
I'm working on removing the not needed ones at least, but I'm not yet convinced that we should remove all and just reuse whatever is available in the archive (at least not at this point). I agree. I found the raring default cross-toolchain failed to build mako's kernel a while ago, and none but gcc-4.6 managed to build a bootable 3.0.8 based kernel for a Huawei device. Jani -- 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] [PATCH] Do not try starting vold, netd, keystore and app_process from init.rc
On Thu, Apr 18, 2013 at 4:59 PM, Ricardo Salveti de Araujo ricardo.salv...@canonical.com wrote: On 04/18/2013 10:55 AM, Sergio Schvezov wrote: On Thu, Apr 18, 2013 at 11:59:23AM +0300, Jani Monoses wrote: I attach a patch that disables starting these in init.rc to avoid such error messages. Any reason to comment instead of just remove? I would prefer removal myself. +1 to remove. I just followed what was done for bootanim, which is commented out in the same file, and for keeping the context handy in case there's a merge with upstream. I am fine with removing. I'm just not so sure about vold, as I remember people saying that it's needed for a few devices, need to investigate further. I just saw it is not built for mako, did not know we build different Android bits depending on target. Jani -- 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] Remove TI/panda support
device/ti/panda seems not to be needed by our official devices, this patch removes it from the default manifest 0001-Remove-device-ti-panda.patch Description: Binary data -- 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] You can now have breakfast to enable devices
I see the nexus device/ and kernel/ repos were removed and should be downloaded using breakfast. Is device/ti/panda still needed? Jani On Mon, Apr 15, 2013 at 10:43 PM, Sergio Schvezov sergio.schve...@canonical.com wrote: The device enabling has changed since we made the necessary mods to the roomservice tool, so now you don't need to go into the manifests and add any entries. breakfast and friends will do the right thing. Ricardo has already modified the wiki with this info[1] Cheers Sergio [1] https://wiki.ubuntu.com/Touch/Porting#Enabling_a_new_device -- 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] BOOT = BlackScreen, ADB working
On Mon, Apr 15, 2013 at 12:29 PM, Petr Bláha p...@p3t3.org wrote: Hi all, I am so tired with compilation and with this odd error with booting to BlackScreen. Yesterday I made big step back to determine what I am doing wrong. I have reinstalled my Ubuntu 12.10 on new partition and made upgrade of all components offered by Update manager. Then installed phablet development tools as describet at wiki.ubuntu.com/Touch. So I have really clear system and development environment with fres source codes as well. Next I made compilation of base system image for my Galaxy Nexus (magure). But this does not work. There is my logcat (stripped to show only messages around error) : http://pastebin.com/vgdFJcj4 Does the prebuilt image for maguro work for you if installed with phablet-flash? Did you add the vendor/samsung/maguro directory containing proprietary blobs to your build? Jani -- 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] Frequency of CyanogenMod syncs?
On Fri, Mar 22, 2013 at 2:40 PM, Sergio Schvezov sergio.schve...@canonical.com wrote: On Fri, Mar 22, 2013 at 02:41:51AM -0700, Christopher Noel Hesse wrote: I guess not. Furthermore I assume we already have the latest Android 4.2.1 codebase from CM-10.1. We don't do it automatically. If there is a good reason to though as when we upgraded from ICS to JB to get manta support, we will. Actually, upgrading to 4.2.2 wouldn't be that clever, because we would loose the ability to use usb debugging using adb before the first actual boot. There are other issues as well, APIs change and it needs to be worth it to move there. The reason I originally asked is not enough to balance the reasons for staying on 4.2.1 but I am mentioning it in case others encounter this issue. For Nexus devices Google only provides 4.2.2 factory images on their site https://developers.google.com/android/nexus/images And at least for the Nexus 4, those do not work with our current 4.2.1 based builds as some blobs have been removed. Also for the Nexus 4 adb pulling from a running devices does not succeed for two files so those need to be taken from a 3rd party like this https://github.com/gdetal/vendor_lge_mako Any build of the Ubuntu Touch sourcecode, even for already supported Nexus devices requires the person building get hold of the vendor blobs from elsewhere as they are not hosted along with the project. Jani -- 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] Frequency of CyanogenMod syncs?
Hello, looking at the helpful daily changelogs I see the so far empty field for Android repo sync, which makes sense as most development needs to happen on the Ubuntu side. Is the Android side updated when CM upstream makes milestone releases? thanks Jani -- 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
