Re: [Ubuntu-phone] Policy: filing bugs against Ubuntu packages instead of upstream projects

[Thomi Richards]

Hi,


On Tue, Nov 26, 2013 at 2:44 PM, Ursula Junque  wrote:

>
> If upstreams don't oppose to that, bugs should only be filed against
> Ubuntu packages, discouraging the direct upstream reporting.
>


I think the distinction between upstream and distro is a useful one, and
I'd be sad if we started treating them as one and the same (or created a
blanket rule about where bugs should be reported, which is effectively the
same thing, in my mind).

I also believe that the correct place for almost all bugs to be filed is
against the upstream projects itself (at least, for the core
Canonical/Ubuntu projects - I assume we're having this conversation in the
context of canonical-sponsored Ubuntu Touch projects).

I suspect one of the issues is that it's easy to miss bugs filed against
the Ubuntu package only. Is there an easy tweak we can make to launchpad so
these bugs are more visible? Or perhaps there's already a way, but I just
don't know about it?

Cheers,
-- 
Thomi Richards
thomi.richa...@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] emulator graphics failed

[Shuduo Sang]

Maybe just need a little patient. The emulator takes about 3~4 minutes
to show up graphic UI on my laptop.

On Mon, Nov 25, 2013 at 10:28 PM, leon lee  wrote:
> Hi, guys. I still have issue with the emulator graphics. I notice that
> there's something like "AppArmor not available as kernel LSM." Is it the
> reason for black screen? What should I check.
>
> init: cannot find '/sbin/adbd', disabling 'adbd'
> init: cannot find '/sbin/adbd', disabling 'adbd'
>  * Starting AppArmor profiles
> * AppArmor not available as kernel LSM.
>
> [fail]
>  * Setting up X socket directories...[
> OK ]
>
>
> To: leon lee 
> From: Chris Wayne 
> Date: Fri, 22 Nov 2013 10:45:33 -0500
> Cc: ubuntu-phone 
> In-reply-to: 
>
> There's no surfaceflinger because it's running Mir :)  The first boot takes
> quite awhile before graphics show up (it took me a couple minutes at least)
>
>
> On Fri, Nov 22, 2013 at 10:39 AM, leon lee  wrote:
>
>> My emulator still has no graphics. And no surfaceflinger in the "ps -ef".
>> Below is my log. Hope someone could help me.
>>
>> emulator$ ./run-emulator.sh
>> emulator: autoconfig: -ramdisk out/target/product/generic/ramdisk.img
>> emulator: autoconfig: -datadir out/target/product/generic
>> emulator: Found target ABI=armeabi-v7a, architecture=arm
>> emulator: Found target API level: 17
>> emulator: using core hw config path:
>> out/target/product/generic/hardware-qemu.ini
>> emulator: keyset loaded from: /home/leon/.android/default.keyset
>> emulator: trying to load skin file
>> 'development/tools/emulator/skins/WVGA800/layout'
>> emulator: skin network speed: 'full'
>> emulator: skin network delay: 'none'
>> emulator: Using initial system image:
>> out/target/product/generic/system.img
>> emulator: WARNING: system partition size adjusted to match image file (300
>> MB > 200 MB)
>>
>> emulator: autoconfig: -initdata out/target/product/generic/userdata.img
>> emulator: WARNING: data partition size adjusted to match image file (300
>> MB > 200 MB)
>>
>> emulator: Physical RAM size: 512MB
>>
>> emulator: Found target ABI=armeabi-v7a
>> emulator: Auto-config: -qemu -cpu cortex-a8
>> Content of hardware configuration file:
>>   hw.cpu.arch = arm
>>   hw.cpu.model = cortex-a8
>>   hw.ramSize = 512
>>   hw.screen = touch
>>   hw.mainKeys = yes
>>   hw.trackBall = yes
>>   hw.keyboard = no
>>   hw.keyboard.lid = no
>>   hw.keyboard.charmap = qwerty2
>>   hw.dPad = yes
>>   hw.gsmModem = yes
>>   hw.gps = yes
>>   hw.battery = yes
>>   hw.accelerometer = yes
>>   hw.audioInput = yes
>>   hw.audioOutput = yes
>>   hw.sdCard = yes
>>   hw.sdCard.path = out/target/product/generic/sdcard.img
>>   disk.cachePartition = yes
>>   disk.cachePartition.path = out/target/product/generic/cache.img
>>   disk.cachePartition.size = 66m
>>   hw.lcd.width = 480
>>   hw.lcd.height = 800
>>   hw.lcd.depth = 16
>>   hw.lcd.density = 160
>>   hw.lcd.backlight = yes
>>   hw.gpu.enabled = yes
>>   hw.camera.back = emulated
>>   hw.camera.front = none
>>   vm.heapSize = 48
>>   hw.sensors.proximity = yes
>>   hw.sensors.magnetic_field = yes
>>   hw.sensors.orientation = yes
>>   hw.sensors.temperature = yes
>>   hw.useext4 = yes
>>   kernel.path = out/target/product/generic/ubuntu/kernel/vmlinuz
>>   kernel.parameters =  androidboot.console=ttyS2
>>   disk.ramdisk.path = out/target/product/generic/ramdisk.img
>>   disk.systemPartition.initPath = out/target/product/generic/system.img
>>   disk.systemPartition.size = 300m
>>   disk.dataPartition.path =
>> out/target/product/generic/out/target/product/generic/userdata.img
>>   disk.dataPartition.size = 300m
>>   avd.name = 
>> .
>> QEMU options list:
>> emulator: argv[00] = "out/host/linux-x86/bin//emulator-arm"
>> emulator: argv[01] = "-show-kernel"
>> emulator: argv[02] = "-serial"
>> emulator: argv[03] = "stdio"
>> emulator: argv[04] = "-cpu"
>> emulator: argv[05] = "cortex-a9"
>> emulator: argv[06] = "-append"
>> emulator: argv[07] = "apparmor=0"
>> emulator: argv[08] = "-android-hw"
>> emulator: argv[09] = "out/target/product/generic/hardware-qemu.ini"
>> Concatenated QEMU options:
>>  out/host/linux-x86/bin//emulator-arm -show-kernel -serial stdio -cpu
>> cortex-a9 -append apparmor=0 -android-hw
>> out/target/product/generic/hardware-qemu.ini
>> emulator: registered 'boot-properties' qemud service
>> emulator: nand_add_dev:
>>
>> system,size=0x12c0,initfile=out/target/product/generic/system.img,pagesize=512,extrasize=0
>> emulator: mapping 'system' NAND image to /tmp/android-leon/emulator-OHbu0L
>> WARNING: Data partition already in use. Changes will not persist!
>> emulator: nand_add_dev: userdata,size=0x12c0,pagesize=512,extrasize=0
>> emulator: mapping 'userdata' NAND image to
>> /tmp/android-leon/emulator-PWk0i7
>> emulator: registered 'boot-properties' qemud service
>> emulator: Adding boot property: 'dalvik.vm.heapsize' = '48m'
>> emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
>> emulator: Adding boot property

Re: [Ubuntu-phone] QProcess, and a QML/JavaScript only alternative?

[Penk Chen]

Hi,

It's easy to write a plugin of invokable like this:

Q_INVOKABLE void execCommand(const QString &msg) {
  QProcess::startDetached(msg);
}

Best,
penk


On Tue, Nov 26, 2013 at 8:58 AM, Israel  wrote:

> Is there work going on to integrate something like QProcess into
> QML/JavaScript.  I'd really like to run some external programs (festival
> for one, and to make a few nice configuration programs for the
> in-process LXQt version of Lubuntu) as I'd rather the program be
> smaller, as both phone and Lubuntu generally want smaller programs,
> rather than full-on C++ code (if avoidable)
> Any help with this, would be appreciated
>
> --
> Regards
>
>
> --
> 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] Policy: filing bugs against Ubuntu packages instead of upstream projects

[Ursula Junque]

Hi all,

There was a long discussion this afternoon on #ubuntu-ci-eng about the
policy to file bugs when dogfooding Ubuntu Touch. We noticed some bugs were
being filed only against upstream projects, and this caused at least one
regression bug to go unnoticed in this latest image. That happened because
the bug was reported against an upstream project, as previously instructed
in the Avengers wiki page (which was fixed) [1], but the landing team was
monitoring bugs on Ubuntu packages. Also some developers noted that for
some projects they don't look for bugs in Ubuntu packages, only upstream
projects.

If upstreams don't oppose to that, bugs should only be filed against Ubuntu
packages, discouraging the direct upstream reporting. Once we have an
agreement, we need to document this to prevent all the confusion to happen
again, and then discuss what to do with the previously reported bugs.
Oliver (ogra) said there was an email some time ago to direct people to
file bugs only against Ubuntu packages but no one seems to find it, feel
free to point that out if you think that's relevant.

After a brief discussion with the CI and the QA teams, I've created the
touch-packages [2] team in Launchpad and subscribed it to all packages
currently seeded in the ubuntu-touch image [3]. This subscription will be
maintained with a script, as packages are often added and removed from the
seeds. With that is possible to have a good list of issues the images
contain, and which bugs should be fixed first. I created one report as an
example of what data we can have [4], let me know if you want that (or
something along those lines) to be updated regularly so I can set a cronjob.

Cheers,

[1] https://wiki.ubuntu.com/Avengers
[2] https://launchpad.net/~touch-packages
[3] https://bugs.launchpad.net/~touch-packages/+packagebugs
[4] http://people.canonical.com/~ursula/seeded-touch-packages-bugs.html

-- 
Ursinha (Ursula Junque)
ursi...@ursinha.net
ursi...@ubuntu.com
--
Ubuntu - I am because we are
--
Linux user #289453 - Ubuntu user #31144
-- 
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] QProcess, and a QML/JavaScript only alternative?

[Israel]

Is there work going on to integrate something like QProcess into
QML/JavaScript.  I'd really like to run some external programs (festival
for one, and to make a few nice configuration programs for the
in-process LXQt version of Lubuntu) as I'd rather the program be
smaller, as both phone and Lubuntu generally want smaller programs,
rather than full-on C++ code (if avoidable)
Any help with this, would be appreciated

-- 
Regards


-- 
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] [Click] Valid architecture values

[Robert Schroll]

Thanks!

On Mon, Nov 25, 2013 at 9:23 PM, Robert Park 
 wrote:

I'd like to see that... anything that makes packaging even easier than
clicks can only be good ;-)

Here's the script, updated with your input: 
https://github.com/rschroll/beru/blob/restricted/makeclick.sh
It is very simple, but if anyone wants to use it as a jumping-off point 
for their own project, please go ahead.


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] [Click] Valid architecture values

[Robert Park]

On Mon, Nov 25, 2013 at 4:10 PM, Robert Schroll  wrote:
> What are the valid values for the architecture key in a manifest file in a
> click package?  I know it's "armhf" for arm devices.  What about for x86 and
> x86_64 devices?

Clicks are a subset of debian packages, so it would be i386 and amd64.

> (Yes, I know there's no need for anything other than arm right now.  I have
> a little script that assembles click packages, and I figured I might as well
> get it right now.)

I'd like to see that... anything that makes packaging even easier than
clicks can only be good ;-)

-- 
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] [Click] Valid architecture values

[Robert Schroll]

Hi all,

What are the valid values for the architecture key in a manifest file 
in a click package?  I know it's "armhf" for arm devices.  What about 
for x86 and x86_64 devices?


(Yes, I know there's no need for anything other than arm right now.  I 
have a little script that assembles click packages, and I figured I 
might as well get it right now.)


Thanks,
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

[Ubuntu-phone] Porting Ubuntu Touch, stuck at splash.

[Reezqy Gilla]

Hi,
As the title says, I'm trying to port Ubuntu Touch, to Lenovo K860
(Stuttgart)
And here I am having a problem, the boot stucks at splash screen.

I'm building the android system with the latest porting and building guide.
It's based on CM10.1.
And I just save the apparmor and audiomixer for later.
The compile process (brunch) goes just fine without any error.

And my flashing steps are :
1. Flash recovery
2. Flash the android system via recovery
3. Flash the ubuntu image via recovery (tried the sauce and trusty one)

And when I rebooted it, it stucked at splash screen.
The adbd didn't even start, so maybe the init didn't run into panic, or it
can't run the panic scripts for some reason.

At first, after the splash screen the screen goes black and then it goes
back to splash screen, it happens a few times and then it finally stucks.
Maybe it did run into panic afterall, and rebooted because of it, and it
stopped doing that for some reason but can't continue the init.

And then I edited the init to make it start adbd, just above the
"maybe_break top" line.
And I'm finally able to access kmsg, which I attached here.
There's no last_kmsg in /proc, and I can't do adb logcat either.
And with this kmsg I was using trusty image.
Even though I was building the android system with phablet-saucy (the one
in the guide)

So, can anyone please read the kmsg and point where the problem it? Thanks.

And I've got a few other questions too.
1. Does the build from phablet-saucy (last synced 3 weeks ago) use
/data/ubuntu or /data/system.img?
2. Is that build made for saucy or trusty?

Thanks,

Rizqi
-- 
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] [DEVELOPMENT][xt907][Porting] Build error

[András Mamenyák]

Hi!

In "device/motorola/qcom-common/modules/nfc/nfc.mk", comment out the
following:

"frameworks/base/nfc-extras/com.android.nfc_extras.xml" (just to be sure,
maybe you can leave this as it is)

"Nfc \
 Tag \
 com.android.nfc_extras"



On Sun, Nov 24, 2013 at 4:17 PM, Eamon Cusic, Jr. wrote:

> Hello all,
> I called brunch xt907 and go the following error: (please excuse the
> length, I figured the entire output might be helpful)
>
> techieelf@eUbuntu:~/phablet$ brunch xt907
> including vendor/cm/vendorsetup.sh
> Looking for dependencies
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=4.2.2
> CM_VERSION=10.1-20131124-UNOFFICIAL-xt907
> TARGET_PRODUCT=cm_xt907
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-3.11.0-14-generic-x86_64-with-Ubuntu-13.10-saucy
> HOST_BUILD_TYPE=release
> BUILD_ID=JDQ39E
> OUT_DIR=/home/techieelf/phablet/out
> 
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=4.2.2
> CM_VERSION=10.1-20131124-UNOFFICIAL-xt907
> TARGET_PRODUCT=cm_xt907
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-3.11.0-14-generic-x86_64-with-Ubuntu-13.10-saucy
> HOST_BUILD_TYPE=release
> BUILD_ID=JDQ39E
> OUT_DIR=/home/techieelf/phablet/out
> 
> build/core/Makefile:44: warning: overriding commands for target
> `/home/techieelf/phablet/out/target/product/xt907/system/etc/mkshrc'
> build/core/base_rules.mk:502: warning: ignoring old commands for target
> `/home/techieelf/phablet/out/target/product/xt907/system/etc/mkshrc'
> build/core/Makefile:44: warning: overriding commands for target
> `/home/techieelf/phablet/out/target/product/xt907/system/lib/egl/egl.cfg'
> build/core/base_rules.mk:502: warning: ignoring old commands for target
> `/home/techieelf/phablet/out/target/product/xt907/system/lib/egl/egl.cfg'
> No private recovery resources for TARGET_DEVICE xt907
> make -C kernel/motorola/msm8960-common
> O=/home/techieelf/phablet/out/target/product/xt907/obj/KERNEL_OBJ
> ARCH=arm CROSS_COMPILE="
>
> /home/techieelf/phablet/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-"
> headers_install
> Install: /home/techieelf/phablet/out/host/linux-x86/bin/acp
> make[1]: Entering directory
> `/home/techieelf/phablet/kernel/motorola/msm8960-common'
> target asm: libpng <=
> external/libpng/contrib/pngneon/png_read_filter_row_neon.s
> target StaticLib: libpixelflinger_static
>
> (/home/techieelf/phablet/out/target/product/xt907/obj/STATIC_LIBRARIES/libpixelflinger_static_intermediates/libpixelflinger_static.a)
> target thumb C: libpng <= external/libpng/png.c
> target thumb C: libpng <= external/libpng/pngerror.c
> target thumb C: libpng <= external/libpng/pnggccrd.c
> target thumb C: libpng <= external/libpng/pngget.c
> target thumb C: libpng <= external/libpng/pngmem.c
> target thumb C: libpng <= external/libpng/pngpread.c
> target thumb C: libpng <= external/libpng/pngread.c
> target thumb C: libpng <= external/libpng/pngrio.c
> target thumb C: libpng <= external/libpng/pngrtran.c
> target thumb C: libpng <= external/libpng/pngrutil.c
> target thumb C: libpng <= external/libpng/pngset.c
> target thumb C: libpng <= external/libpng/pngtrans.c
> target thumb C: libpng <= external/libpng/pngvcrd.c
> target thumb C: libpng <= external/libpng/pngwio.c
> target thumb C: libpng <= external/libpng/pngwrite.c
> target thumb C: libpng <= external/libpng/pngwtran.c
> target thumb C: libpng <= external/libpng/pngwutil.c
> target StaticLib: libstdc++
>
> (/home/techieelf/phablet/out/target/product/xt907/obj/STATIC_LIBRARIES/libstdc++_intermediates/libstdc++.a)
> target StaticLib: libz
>
> (/home/techieelf/phablet/out/target/product/xt907/obj/STATIC_LIBRARIES/libz_intermediates/libz.a)
> target StaticLib: liblog
>
> (/home/techieelf/phablet/out/target/product/xt907/obj/STATIC_LIBRARIES/liblog_intermediates/liblog.a)
> target StaticLib: libcutils
>
> (/home/techieelf/phablet/out/target/product/xt907/obj/STATIC_LIBRARIES/libcutils_intermediates/libcutils.a)
> target arm C: libm <= bionic/libm/src/e_fmodf.c
> target arm C: libm <= bionic/libm/src/e_gamma.c
> target arm C: libm <= bionic/libm/src/e_gamma_r.c
> target arm C: libm <= bionic/libm/src/e_gammaf.c
> target arm C: libm <= bionic/libm/src/e_gammaf_r.c
> target arm C: libm <= bionic/libm/src/e_hypot.c
> target arm C: libm <= bionic/libm/src/e_hypotf.c
> target arm C: libm <= bionic/libm/src/e_j0.c
> target arm C: libm <= bionic/libm/src/e_j0f.c
> target arm C: libm <= bionic/libm/src/e_j1.c
> target arm C: libm <= bionic/libm/src/e_j1f.c
> target arm C: libm <= bionic/libm/src/e_jn.c
> bionic/libm/src/e_j0.c: 

Re: [Ubuntu-phone] Ubuntu Touch does not connect to saved wifi on reboot

[Vinay Simha]

thanks sayantan.
On 26 Nov 2013 00:56, "Sayantan Das"  wrote:

> Hi Vinay,
>
> Please find attached the dmesg
>
> Regards,
>
> *Sayantan Das*
>
> --
> Use Linux. Be free !
> http://www.tuxtrix.com
>  
>
>
> On 26 November 2013 00:43, Vinay Simha  wrote:
>
>> HI Sayantan,
>>
>> Could you please provide the kernel dmesg log of the ported UT on nexus
>> 4. It would be helpful for us to fix our porting on apq8064 ifc6410 board.
>>
>>  Regards,
>> Vinay Simha BN
>>
>>
>> On Tue, Nov 26, 2013 at 12:33 AM, Sayantan Das wrote:
>>
>>> Hi ,
>>>
>>> I am currently running UT Trusty (r28 ) on my nexus 4. I have noticed
>>> that after rebooting the phone, wifi does not connect automatically. The
>>> wifi details are saved as far as I can understand, as every time I connect
>>> to the same wifi, it adds a suffix 1,2 ,3 and so on to the wifi connection
>>> name . Yet on reboot, it does not connect to the available wifi.
>>>
>>>
>>> Regards,
>>>
>>> *Sayantan Das*
>>>
>>> --
>>> Use Linux. Be free !
>>> http://www.tuxtrix.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
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Vinay Simha.B.N.
>>
>>
>
-- 
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

[Ivo Stoyanov]

It's not that simple. What you see is only the first phase - initrd.
I am going thru the hoops for 2 weeks already.

See my thread about similar "learning pain" porting issues.

https://lists.launchpad.net/ubuntu-phone/msg05218.html



>
> From: Dmitry Smirnov 
>To: ubuntu-phone@lists.launchpad.net 
>Sent: Tuesday, November 5, 2013 8:36 AM
>Subject: [Ubuntu-phone] Porting issues
> 
>
>
>Hi,
>
>
>I'm trying to port ubuntu-touch to some specific 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)
>
>
>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] CM 10.2 base for Nexus 7 (2013)

[Robert Park]

Oh, sorry. That I don't know anything about.

On Mon, Nov 25, 2013 at 10:27 AM, Sayantan Das  wrote:
> Hi Robert,
>
> I was talking about the 2013 version of Nexus 7. I have also noticed that
> the UT wiki page also says that Nexus 7 2013 is not supported.
>
> Regards,
> Sayantan
>
> On 25 Nov 2013 22:25, "Robert Park"  wrote:
>>
>> The issues you are seeing with Ubuntu not working very well on a Nexus
>> 7 are due to the fact that Mir does not support that hardware very
>> well, not because of the version of cyanogenmod used as a base. See
>> this bug for a workaround:
>>
>> https://bugs.launchpad.net/mir/+bug/1238695
>>
>> On Mon, Nov 25, 2013 at 2:07 AM, Sayantan Das 
>> wrote:
>> > Hi,
>> >
>> > Any idea if Ubuntu Touch will be based on CM10.2? The current base does
>> > not
>> > seem to run well on Nexus 7 (2013).
>> > I was looking into this thread, and the project seems to be abandoned.
>> > http://forum.xda-developers.com/showthread.php?t=2404708
>> >
>> >
>> >
>> > Regards,
>> >
>> > Sayantan Das
>> >
>> > --
>> > Use Linux. Be free !
>> > http://www.tuxtrix.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

Re: [Ubuntu-phone] Ubuntu Touch does not connect to saved wifi on reboot

[Vinay Simha]

HI Sayantan,

Could you please provide the kernel dmesg log of the ported UT on nexus 4.
It would be helpful for us to fix our porting on apq8064 ifc6410 board.

Regards,
Vinay Simha BN


On Tue, Nov 26, 2013 at 12:33 AM, Sayantan Das  wrote:

> Hi ,
>
> I am currently running UT Trusty (r28 ) on my nexus 4. I have noticed that
> after rebooting the phone, wifi does not connect automatically. The wifi
> details are saved as far as I can understand, as every time I connect to
> the same wifi, it adds a suffix 1,2 ,3 and so on to the wifi connection
> name . Yet on reboot, it does not connect to the available wifi.
>
>
> Regards,
>
> *Sayantan Das*
>
> --
> Use Linux. Be free !
> http://www.tuxtrix.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
>
>


-- 
Regards,

Vinay Simha.B.N.
-- 
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] Ubuntu Touch does not connect to saved wifi on reboot

[Sayantan Das]

Hi ,

I am currently running UT Trusty (r28 ) on my nexus 4. I have noticed that
after rebooting the phone, wifi does not connect automatically. The wifi
details are saved as far as I can understand, as every time I connect to
the same wifi, it adds a suffix 1,2 ,3 and so on to the wifi connection
name . Yet on reboot, it does not connect to the available wifi.


Regards,

*Sayantan Das*

--
Use Linux. Be free !
http://www.tuxtrix.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] CM 10.2 base for Nexus 7 (2013)

[Sayantan Das]

Hi Robert,

I was talking about the 2013 version of Nexus 7. I have also noticed that
the UT wiki page also says that Nexus 7 2013 is not supported.

Regards,
Sayantan
On 25 Nov 2013 22:25, "Robert Park"  wrote:

> The issues you are seeing with Ubuntu not working very well on a Nexus
> 7 are due to the fact that Mir does not support that hardware very
> well, not because of the version of cyanogenmod used as a base. See
> this bug for a workaround:
>
> https://bugs.launchpad.net/mir/+bug/1238695
>
> On Mon, Nov 25, 2013 at 2:07 AM, Sayantan Das 
> wrote:
> > Hi,
> >
> > Any idea if Ubuntu Touch will be based on CM10.2? The current base does
> not
> > seem to run well on Nexus 7 (2013).
> > I was looking into this thread, and the project seems to be abandoned.
> > http://forum.xda-developers.com/showthread.php?t=2404708
> >
> >
> >
> > Regards,
> >
> > Sayantan Das
> >
> > --
> > Use Linux. Be free !
> > http://www.tuxtrix.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

Re: [Ubuntu-phone] CM 10.2 base for Nexus 7 (2013)

[Robert Park]

The issues you are seeing with Ubuntu not working very well on a Nexus
7 are due to the fact that Mir does not support that hardware very
well, not because of the version of cyanogenmod used as a base. See
this bug for a workaround:

https://bugs.launchpad.net/mir/+bug/1238695

On Mon, Nov 25, 2013 at 2:07 AM, Sayantan Das  wrote:
> Hi,
>
> Any idea if Ubuntu Touch will be based on CM10.2? The current base does not
> seem to run well on Nexus 7 (2013).
> I was looking into this thread, and the project seems to be abandoned.
> http://forum.xda-developers.com/showthread.php?t=2404708
>
>
>
> Regards,
>
> Sayantan Das
>
> --
> Use Linux. Be free !
> http://www.tuxtrix.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

Re: [Ubuntu-phone] Fwd: [DEVELOPMENT] libubuntu_application_api.so not found

[François Leblanc]

Ah ok.

Build for crespo device (nexus S) using cm 10.1 and trusty preinstalled
daily from 25/11/2013
(not sure of the date) trying to port flipped so I've installed all in
system.img and put android system.img on /var/lib/lxc/android/system.img
and android-ramdisk on /boot

Ubuntu start can access with adb but have a black screen.

When I run lxc-console -n android -t0 I can do logcat where I can see the
message
linker.c (1095): /system/lib/libubuntu_application_api.so not found

Like I guess that communication betwen android firmeware and ubuntu is
crucial
I try first to correct this. /system/lib/libubuntu_application_api.so is
present and I can stat it
it is regular file.

I've a look on jb, linker.c and try to add some trace but unfortunatly I've
no more informations on logcat and I can't find why.. It's why I need some
help.

I'm not english speaker it's maybe why I have some trouble to explain
exactly what happen .

Regards


2013/11/25 Loïc Minier 

> On Mon, Nov 25, 2013, François Leblanc wrote:
> > I'm surprise because I think this is core of porting...
> >
> > Ubuntu kernel talk to android with turn in lxc container for working with
> > device spécifics firmware (sensors, etc...) and I guess that
> communication
> > between unbuntu and android use libubuntu_application_api.so.
> >
> > It's what I think it's working (perhhaps wrong don't knwon)
> >
> > All porters should know  how this communication it's working, at least
> > ubuntu developpers should know what is libubuntu_application_api.so is
> > for...
>
> First, not all developers know all details about all components; second,
> it's the description of the issue you are experiencing/reporting that
> isn't clear.
>
> I'm running the public pre-built Nexus 4 images of Ubuntu for phones and
> these work; maybe you should explain what you're trying to achieve:
> which images you're trying to build, for which device.  Which version of
> the source code are you basing on?  Where are you at?  etc.
>
> I dont know whether I or anyone will be able to help you, but from your
> original email I couldn't tell what you were trying to achieve, which is
> why I suggested you should clarify.
>
> --
> Loïc Minier
>
-- 
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] Fwd: [DEVELOPMENT] libubuntu_application_api.so not found

[Loïc Minier]

On Mon, Nov 25, 2013, François Leblanc wrote:
> I'm surprise because I think this is core of porting...
> 
> Ubuntu kernel talk to android with turn in lxc container for working with
> device spécifics firmware (sensors, etc...) and I guess that communication
> between unbuntu and android use libubuntu_application_api.so.
> 
> It's what I think it's working (perhhaps wrong don't knwon)
> 
> All porters should know  how this communication it's working, at least
> ubuntu developpers should know what is libubuntu_application_api.so is
> for...

First, not all developers know all details about all components; second,
it's the description of the issue you are experiencing/reporting that
isn't clear.

I'm running the public pre-built Nexus 4 images of Ubuntu for phones and
these work; maybe you should explain what you're trying to achieve:
which images you're trying to build, for which device.  Which version of
the source code are you basing on?  Where are you at?  etc.

I dont know whether I or anyone will be able to help you, but from your
original email I couldn't tell what you were trying to achieve, which is
why I suggested you should clarify.

-- 
Loïc Minier

-- 
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 plan 25.11.12 special episode

[Didier Roche]

Hey guys,

Trusty image #28 is now available. \o/

Granted that we didn't promote an image for quite a few days/weeks, we had to 
resolve that situation.
Especially now that the CI infrastructure move is mostly over, everything is 
operational, great work guys!
Raring to deliver the new promoted image, we looked at the Unity8 crashes we 
saw in images 27 and 28, and we ensured it only happens on exit, so didn't 
impact user experience as itself.
Only fixing this crash will mean diving deep into Qt 5.0 while we are moving to 
Qt 5.2, and getting a reliable stacktrace is hard as the phone is shutting down 
before the debug collect is over.
Noting that the remaining autopilot test failures are false positives from the 
core applicaitons we ship, we confirm manually that they all work as expected.
In those terms, we decide that we can promote image 28 with a sense of 
proudness, knowing all the issues we encountered in the past few weeks.
Meanwhile, we still work on resuming landing more and more packages (Mir stack, 
autopilot, qtubuntu in the coming one for instance) to wake up the engine, and 
be on a fast path again.
On the coming days, you can expect to get promoted images in a way faster 
cadence, now that everything is up again.

Another goal is to have again all tests green, and we have the core apps team 
furiously working on that.
Green image again? "Allons-y!"

Maybe we'll already be there in the next couple of images, "who knows..."
Didier


*Vwrorrrp Vwrorrrp Vwrorrrp Vwrorrrp*

-- 
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] Fwd: [DEVELOPMENT] libubuntu_application_api.so not found

[François Leblanc]

I'm surprise because I think this is core of porting...

Ubuntu kernel talk to android with turn in lxc container for working with
device spécifics firmware (sensors, etc...) and I guess that communication
between unbuntu and android use libubuntu_application_api.so.

It's what I think it's working (perhhaps wrong don't knwon)

All porters should know  how this communication it's working, at least
ubuntu developpers should know what is libubuntu_application_api.so is
for...

Regards


2013/11/25 Loïc Minier 

> On Mon, Nov 25, 2013, François Leblanc wrote:
> > Nobody for help please?
>
> I guess the original request wasn't specific enough for anyone to
> comment: what are you trying to do, where/what did you start from?
>
> >
> > -- Forwarded message --
> > From: François Leblanc 
> > Date: 2013/11/24
> > Subject: [DEVELOPMENT] libubuntu_application_api.so not found
> > To: ubuntu-phone 
> >
> >
> > Hello
> >
> > Logcat -d show /system/lib/libubuntu_application_api.so not found.
> >
> > File is present and is regular.
> >
> >
> > I attempt to trace modifying sources but seems that package is reloaded
> on
> > build since any modification not taken account .
> >
> >
> > Any idea on why lib is not found by linker.c or how to trace problem is
> > welcome, very welcome.
> >
> >
> > Regards.
>
> > --
> > 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
>
>
> --
> Loïc Minier
>
-- 
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] Fwd: [DEVELOPMENT] libubuntu_application_api.so not found

[Loïc Minier]

On Mon, Nov 25, 2013, François Leblanc wrote:
> Nobody for help please?

I guess the original request wasn't specific enough for anyone to
comment: what are you trying to do, where/what did you start from?

> 
> -- Forwarded message --
> From: François Leblanc 
> Date: 2013/11/24
> Subject: [DEVELOPMENT] libubuntu_application_api.so not found
> To: ubuntu-phone 
> 
> 
> Hello
> 
> Logcat -d show /system/lib/libubuntu_application_api.so not found.
> 
> File is present and is regular.
> 
> 
> I attempt to trace modifying sources but seems that package is reloaded on
> build since any modification not taken account .
> 
> 
> Any idea on why lib is not found by linker.c or how to trace problem is
> welcome, very welcome.
> 
> 
> Regards.

> -- 
> 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


-- 
Loïc Minier

-- 
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] Fwd: [DEVELOPMENT] libubuntu_application_api.so not found

[François Leblanc]

Nobody for help please?

-- Forwarded message --
From: François Leblanc 
Date: 2013/11/24
Subject: [DEVELOPMENT] libubuntu_application_api.so not found
To: ubuntu-phone 


Hello

Logcat -d show /system/lib/libubuntu_application_api.so not found.

File is present and is regular.


I attempt to trace modifying sources but seems that package is reloaded on
build since any modification not taken account .


Any idea on why lib is not found by linker.c or how to trace problem is
welcome, very welcome.


Regards.
-- 
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] Reply: follow instructions to build emulator onpreciseamd64 but fail at build-emulator-sdcard.sh

[leon lee]

That's weird. Please check if you have the ./build/tools/get-tarball-url.py
If yes, check if it's executable.
If yes, then try run the script again.
If still no luck, then... I don't get it.



-- Original --
Sender: "István Szőllősi";
Send time: Sunday, Nov 24, 2013 9:26 PM
To: "leon lee"; 
Cc: "Shuduo Sang"; 
"ubuntu-phone"; 
Subject: Re: [Ubuntu-phone] follow instructions to build emulator 
onpreciseamd64 but fail at build-emulator-sdcard.sh



"Python3 is already the newest version."


2013/11/24 leon lee 
 I had the same issue before. It's simple. Just install python3 would remove 
it. get-tarball-url.py is written in python3.
 



-- Original --
 From:  "István Szőllősi";
Date:  Nov 24, 2013
To:  "Shuduo Sang"; 
 Cc:  "ubuntu-phone"; 
Subject:  Re: [Ubuntu-phone] follow instructions to build emulator on 
preciseamd64 but fail at build-emulator-sdcard.sh
 


Same error here!


2013/11/24 Shuduo Sang 
 Hi,
 
 I just follow https://wiki.ubuntu.com/Touch/Emulator and build it from
 scratch then I meet error output as below:
 
 $ ./build/tools/build-emulator-sdcard.sh
 + OUT=out/target/product/generic/
 + [ ! -e out/target/product/generic//ubuntu-rootfs.tar.xz ]
 + ./build/tools/get-tarball-url.py
 ./build/tools/build-emulator-sdcard.sh: 1:
 ./build/tools/build-emulator-sdcard.sh:
 ./build/tools/get-tarball-url.py: not found
 + wget -O out/target/product/generic//ubuntu-rootfs.tar.xz
 wget: missing URL
 Usage: wget [OPTION]... [URL]...
 
 Try `wget --help' for more options.
 
 
 
 What I should to do now?
 
 BTW, If I want to copy executable emulator after I build it out, what
 files need be copied to?
 
 
 Thanks,
 Shuduo
 
 --
 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] auto update not working (14.04)

[Nekhelesh Ramananthan]

Hi Sayantan,

I read your instruction on Muktware and checked out the app on the play
store. It seems like an easy way to get both android and ubuntu touch on
your phone. Nice work!

@Oli, Check out
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr on
the play store. It makes installing ubuntu touch pleasantly easy.

Regards,
Nekhelesh

On Sun, Nov 24, 2013 at 3:01 PM, Sayantan Das  wrote:

> Thanks Oli.
> I hear what you are saying. I will have to flash it every week then.
> However, for me, this is the best way to keep my work and hobby on the same
> phone :)
>
>
> Regards,
>
> *Sayantan Das*
>
> --
> Use Linux. Be free !
> http://www.tuxtrix.com
>  
>
>
> On 24 November 2013 15:58, Oliver Grawert  wrote:
>
>> hi,
>> On So, 2013-11-24 at 12:46 +0530, Sayantan Das wrote:
>> > Hi all,
>> >
>> >
>> > I am currently running Ubuntu Touch using MultiRom on my Nexus 4. I
>> > installed the 14.04 (r10) build . The install went fine, and I can
>> > access everything. However, I am not able to update the to latest
>> > builds. It keeps saying no updates available when I try to update via
>> > the system settings update option.
>> >
>> >
>> >  Any ideas how to get that working?
>> >
>> you would have to switch to the devel-proposed channel instead of using
>> devel. there was no devel release in a while because the quality of the
>> images in devel-proposed (from where they migrate) was not good enough.
>>
>> http://ci.ubuntu.com/smokeng/trusty/touch/ has the automated test
>> results of all our builds ... the failure rate for the next released
>> devel image needs to be at least on par with image 10 before we let it
>> into the channel.
>>
>> that said though, i am not sure our update mechanism will get along with
>> multirom images, dual booting is not in our focus at all currently.
>>
>> 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

Re: [Ubuntu-phone] Fwd: Re: Desktop file parsing - lets standardize

[Ryan Lortie]

hi Gerry,

Thanks for the mails.

On Tue, Nov 12, 2013, at 11:24, Gerry Boland wrote:
>  Original Message 
> From: Thomas Voß 
>
> What is the underlying technology used for the cache and how will it
> be exposed to the rest of the system?

The cache is a simple binary format that is easy to read.  There are no
library dependencies for consuming it.  The reader side is more or less
contained in this 600 lines of .c:

  https://github.com/desrt/desktop-file-index/blob/master/dfi-reader.c

The goal was to keep it easy to consume by various desktops without
needing to use 3rd party libraries -- this is why we didn't use GVDB
(for example).

The most complicated data structure contained in it is sorted lists.  We
use binary search for lookups.  This is largely consistent with the
design goal of wanting to do prefix matching for things like mime types
(and particularly) user-initiated application searches.  We can
binary-search for the prefix and iterate through the list until we hit
an item that doesn't have the prefix.

The result is pretty fast -- searching through applications takes
single-digit microseconds on my machine.

An additional goal of the cache file is saner treatment of translations.
 The current situation on Ubuntu is a pretty huge disaster.  We ship a
patch to GLib (which will never go upstream) that allows us to have the
translations split out of desktop files and put in gettext files.  The
reason here is to facilitate language packs: if we don't install the
language pack for language X then we don't have its translation in the
original desktop file.  The savings here are substantial when multiplied
by ~300 language packs...

The problem is that the reader needs to mmap the gettext .mo file for
every single desktop file it opens in order to lookup the translations. 
When iterating all the desktop files on your system (for example, as
Unity does) this gets pretty ridiculous.  It doesn't help that these
files can never be unmapped.  If you're using your system in non-English
take a look at the number of .mo files currently mapped into various
processes that use desktop files... For example, I notice that the .mo
from gnome-control-center (just to take one) ends up being used from
gnome-session, bamf, compiz, update-manager, and the application scope. 
The application scope has 88 .mo files mapped into it...

The desktop file index will try to resolve this situation by having all
of the translation mapping done at the time that the cache is built (ie:
all languages in the same file).  This produces a very large file if you
have a lot of language packs installed, but the builder is careful to
group languages together -- so you'll only end up faulting in the
portion of the file that corresponds to your current locale.  I've done
some testing to see which pages actually end up in the kernel page cache
and it's very small.

> If we want to standardize, I would propose to look at the
> implementation that is the most toolkit-/runtime-agnostic one, with
> the fewest dependencies to make sure that higher levels of the stack
> can easily consume it. Ideally something with a very simple API (and
> desktop file parsing is not rocket science, so it should be fairly
> small).

I'm not sure you could call GLib toolkit-agnostic (since it's pretty
clearly tied with Gtk) but it's also designed to be used on its own and
to be very easy to bind (and has more bindings than any other library I
know).  I'd also argue that it's essentially 'no additional dependency'
since we already have it on Ubuntu and it won't be going anywhere for a
very long time...

Despite what I say above about reading the desktop file index boiling
down to about 600 lines of .c, handling desktop files is a very
complicated affair.  There are a lot of non-trivial details of the
specification and it's non-trivial to get them right against the wide
number of applications in the wild.  There are also considerations like
Ubuntu's language pack handling that we'd have to patch into the new
solution.  Reading the keyfile contents is really only a small part of
dealing with this.

> -  Original Message 
> From: Ted Gould 
> 
> I don't think that the cache is really useful for our use-cases.  If we
> do want a cache, I think it'd be better to add a Click desktop hook and
> cache what is specifically needed for that case.  For instance, the
> shell needs an icon and name cache, it doesn't need the other data.
> Same for scopes, the exec line is mostly useless, but breaking down the
> fields into the indexer at install time would save time when searching.

glick works by extracting desktop files from the app bundle as they're
installed and running update-desktop-database on them.  This will soon
result in the regeneration of the desktop index as well.  I assume that
Click does (or should do) something similar to this.

There's no need to invent additional magic here specifically for the
case of app bundles...

> It seems

Re: [Ubuntu-phone] Porting need assistance

[Ryan.]

Found.my problem.
Need to select.fallback branch how do I do this.

Screen attached

"Ryan."  wrote:
>Thanks for replys but I'm all so confused by this device and any repo I
>find. I may have more.success porting.to my s4 but I dont want to brick
>it
>
>Lukas Krotovic  wrote:
>>Hi,
>>when your phone isn't on breakfast list, you need to edit
>>local_manifest.xml
>>See this guide:
>>http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests
>>There you need to enclose all needed repos with CM, that can be found
>>on 
>>github. Then sync the repo.
>>
>>Good luck,
>>Lukas
>>
>>
>>On 23.11.2013 11:59, Ryan. wrote:
>>> Hi I'm trying to port to Atrix 4g ... codename Olympus.
>>> I've setup the env but when I get to breakfast codename It can't
>find
>>
>>> olympus and I have no idea how to add this into repo so it syncs and
>
>>> I'm able to continue.
>>>
>>> All help is appreciated
>>> -- 
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>>
>>>
>>
>>
>>
>>
>>
>>-- 
>>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
>
>-- 
>Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
>
>-- 
>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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
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] modifying environment

[Alex Kilimnik]

Hi Everyone,

I wish to make some modification to the Unity environment and am
having difficulty finding documentation on how to do so. I would like
to modify the environment so that an application starts up and is the
only application accessible. This would mean that I would have to
uninstall the existing applications to limit access. Can anyone point
me in the right direction? Thanks in advance.

Take Care,
Alex

-- 
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] Porting issues

[Dmitry Smirnov]

Hi,

I'm trying to port ubuntu-touch to some specific 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)

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

[Ubuntu-phone] CM 10.2 base for Nexus 7 (2013)

[Sayantan Das]

Hi,

Any idea if Ubuntu Touch will be based on CM10.2? The current base does not
seem to run well on Nexus 7 (2013).
I was looking into this thread, and the project seems to be abandoned.
http://forum.xda-developers.com/showthread.php?t=2404708



Regards,

*Sayantan Das*

--
Use Linux. Be free !
http://www.tuxtrix.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