Re: [Ubuntu-phone] Minimal partitions size.

[Florian Will]

Hi,


> I got some partitions size error, after a reboot or if I use apt-get
> upgrade I got "error : no space left on device"

See my old post [1] to this list about how to trim down the rootfs size.
Also, make sure to always "apt-get clean" after an upgrade. Regularly
delete stuff in /var/log in case you encountered some syslog-spamming
kernel bug like I do sometimes with my Desire Z.

Also, the currently published unflipped images have a broken
sources.list configuration AFAICT, since the unity-next PPA is missing,
so add the unity-next PPA before upgrading. Maybe this is fixed by now.

> Anybody knows how to fix it or the minimal size for /data and /system
> please.

The official minimum /data partition size is 3GB IIRC. However, I'm
successfully using Ubuntu Touch on my 1GB /data, with some modifications
for the way the image is flashed (extracting the tar.gz from /sdcard
instead of /data, I have a merge request on Launchpad that fixes this by
choosing the location depending on the free space in various locations,
but it's probably not getting pushed upstream due to lack of testing).

So while it's not officially supported, it's possible. :-)

Cheers,
Florian

[1] https://lists.launchpad.net/ubuntu-phone/msg02696.html

-- 
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] Flipped HTC Desire Z Port

[Florian Will]

Hi,

I've ported Ubuntu Touch with "flipped" containers (booting directly
into Ubuntu) to the Desire Z. First of all, thanks to #ubuntu-touch and
especially Oliver Grawert for helping me with some of the issues I
encountered. Device specific code is by the Andromadus team from XDA
Developers since there's no official CyanogenMod for this device. You
can check the port out at [1], it's linked as "flipped_vision" and the
page has some installation instructions / status information.

There's also the "unflipped" Port with less bugs and more
device-specific features by utopykzebulon.

[1] https://wiki.ubuntu.com/Touch/Devices


Although I have almost no experience with kernel building and low-level
things, here is my general advice for porting the flipped stuff:
 * There are apparently two different approaches for mounting the
flipped images, and it seems like my port uses the old-style approach.
 * The android_build repository on phablet.ubuntu.com has all the
required changes to create the android zip file. It downloads files for
a generic initramfs and puts them in
"out/target/product/devicename/ubuntu-root". I think that changes to
those files are not automatically put back into the ramdisk. (I've added
an additional step to repack the ramdisk after changing the ubuntu-root/
dir contents.) That ramdisk is then used to create boot.img instead of
the cyanogenmod ramdisk (which is used for android-boot.img).
 * The "scripts/touch" file in the ramdisk needs to figure out the data
partititon's device file name (like /dev/foo). It might fail for your
device and cause the boot process to fail. I've hard-coded the device
path for the Desire Z for now, maybe we can set this in the device
config at build time later.
 * If the initramfs script has problems finding the data partition, then
/usr/lib/lxc-android-config/update-fstab could have problems too.
 * /etc/init/lxc-android-boot.conf might be interesting as well.
 * The Ubuntu rootfs needs a udev rules file for your device. Check the
/usr/lib/lxc-android-config/70-*.rules files as an example. You can
create that file by looking at the ueventd*.rc files for your device
from cyanogenmod and transforming the /dev/ settings to udev syntax.
 * There are some requirements for the kernel config. For example, I had
boot failures before I enabled CONFIG_VT=y and CONFIG_VT_CONSOLE=y.
 * It's a good idea to check dmesg, logcat (you need to android-chroot
first) and the various log files in /var/log/upstart if there are problems.

Cheers,
Florian

-- 
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] Flipped Sony Tablet Z Port

[Florian Will]

Hi Andras (sorry, my keyboard layout won't let me type your name
correctly, and Thunderbird won't let me copy your name, so..),

This looks like the important part in your log:
> E/Adreno200-GSL(13249): :
open(/dev/kgsl-3d0) failed: errno 13. Permission denied

I guess you can fix it by adding a 70-devicename.rules file. There's
some info about how to create that file in the new porting guide [1].

[1] https://wiki.ubuntu.com/Touch/PortingFlippedInProgress

Cheers and good luck
Florian

-- 
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: mount issues

[Florian Will]

Hi everyone,

I'm having some trouble fixing mount problems and hope someone knows
what's wrong. These are the 3 main issues:


* My device appears to have no UDA, userdata, USERDATA or similar
symlink to the user partition device node in /dev. I only have
/dev/mmcblk0p26 and a symlink "/dev/block/179:26" to that device node.
In /dev/disk I have "by-id", "by-path" and "by-uuid" but nothing else,
i.e. no by-name or by-label or by-disklabel. blkid also prints no labels
for partitions. I suspect this is because of:
> /dev/mmcblk0: PTTYPE="dos"
(i.e. no gpt)

  => This is not a serious problem if bug #1199084 gets fixed (mount
support via cmdline parameters). Still, maybe there's a kernel config or
kernel patch to export partition labels to userspace? The kernel knows
about partition labels from reading an ATAG param and creates a
/proc/emmc file to list them.



* Because of that first problem, I hard-coded the userdata partition
path in scripts/touch in the initramfs. This works fine and the device
boots. The update-fstab script in /usr/lib/lxc-android-config then fails
because it can't find the userdata partition, so I manually updated the
/etc/fstab file:
> /dev/mmcblk0p26   /data   ext4noatime,nodiratime,errors=remount-ro
> 0   0
(similar for /system and a bind mount for /vendor)

Now things fail on boot, probably because that partition was already
mounted in the initramfs script.
> mount: /dev/mmcblk0p26 already mounted or /data busy
> mount: according to mtab, /dev/mmcblk0p26 is mounted on /
The android container fails to mount /data as well.

What's wrong with my setup? Something in the initramfs? Bad fstab? I've
heard that /etc/fstab is not even supposed to exist and that it should
*only* be at /data/ubuntu/etc/fstab.. So what's supposed to be at /
then, and how do I get it there? :)



* I'm not sure about this last point, maybe it's alright. When booting
Ubuntu Touch, the devices are at /dev/mmcblk0p[0-29]. In the android
container or when booting the recovery, I find them at
/dev/block/mmcblk0p[0-29]. Not sure if this is a problem, maybe udev
does things differently from whatever-android-uses-instead-of-udev.. :-)


It's surprising that my device actually boots up and has a usable GUI
with all those problems. I'm thankful for any help with this.

Cheers,
Florian

-- 
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] Request for help: test new phablet-flash

[Florian Will]

Am 09.08.2013 13:42, schrieb Daniel Holbach:
>> I'll give a try but also for HTC vision we have to extract ***.tar.gz on
>> /sdcard because we haven't enough space in /data but your script extract
>> it on /data... Will you do an update?
> 
> To me this sounds like two separate issues? One being the location and
> the second the space, right?

There are two issues:

 * By default, the ubuntu.zip provided by canonical will push the tar.gz
to /data, then extract it there. This is impossible in case of the
vision because /data can't store the tar.gz and the extracted rootfs at
the same time.

The modified ubuntu.zip for the vision that I provided for the
phablet-flash tool fixes this issue by dynamically searching through a
set of paths (/data, /sdcard, /ext/sdcard) and choosing one with
sufficient amount of free storage for the tar.gz. There's an open bug
report for this issue.

 * In most cases, /data only has a few hundred MiB of free space before
flashing the ubuntu.zip, but about 600-700mb of storage are required for
the ubuntu rootfs. The flash process does not fail in an obvious way in
that case, but the phone reboots to a black screen and ADB no longer
works (only in recovery). Workaround is to wipe /data before flashing,
but obviously I should add a check to the edify script so it shows an
error message when there's not enough free space. This should work and
wipe any user data before flashing:

phablet-flash community --wipe -d vision

Cheers,
Florian

-- 
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 packages and U1db.Database

[Florian Will]

For the click install, I use this: (from the top of my head)

click install --force-missing-framework --user=phablet file.click

Maybe that's not the officially recommended way, but it works.

Can't help you with your other problem.

Cheers
Florian

Sorry for the full quote below, I'm writing from android gmail app.
Am 22.08.2013 12:37 schrieb "Sam Segers" :

> Hi
>
> I'm developing an app for the Ubuntu App Showdown.
> I tried to use click package to see how it works but I run into a problem
> when I do 'click install ... .click':
>
> Traceback (most recent call last):
>   File "/usr/bin/click", line 65, in 
> sys.exit(main())
>   File "/usr/bin/click", line 60, in main
> mod.run(args)
>   File "/usr/lib/python3/dist-packages/click/commands/install.py", line
> 41, in run
> installer.install(package_path, user=options.user)
>   File "/usr/lib/python3/dist-packages/click/install.py", line 200, in
> install
> package_name, package_version = self.audit(path)
>   File "/usr/lib/python3/dist-packages/click/install.py", line 157, in
> audit
> return self.audit_control(package.control)
>   File "/usr/lib/python3/dist-packages/click/install.py", line 151, in
> audit_control
> 'Framework "%s" not present on system' % framework)
> ValueError: Framework "ubuntu-sdk-13.10" not present on system
>
>
> And my question for U1db.Database is what path I should use? Is there
> going to be any guidelines on which directory's to use?
>
>
> Sam Segers
>
> --
> 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] touch init script update list of data partition names

[Florian Will]

Hi Patrick,

Am 12.09.2013 22:04, schrieb Patrick Seemann:
> What is the preffered way of handling this issue?

Not sure if this is the best way to solve the issue in your case, but
you could try to add the "datapart=/dev/whatever" kernel cmdline
parameter. This should help with booting but still cause problems later
on, because there's a shell script that still needs to be adjusted.

See bug 1199084 (and note that it's only partially fixed yet):
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1199084

In the past, people on #ubuntu-touch have been fast to add new partition
names to that list, so you could try that too. With the release coming
very close now, they are pretty busy though.

Cheers,
Florian


-- 
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] script/touch and saucy-preinstalled-touch-armhf.zip

[Florian Will]

Hi Francois,

You may notice the touch script only checks if system.img exists, and
if it doesn't (which is the case for "cdimage"-style images, as
opposed to "system" images), it just skips most of the script and does
this instead:

# Old flipped model
elif [ -d /tmpmnt/ubuntu ]; then
mount --bind /tmpmnt/ubuntu ${rootmnt}
mountroot_status="$?"


Right now all ports use the "old" flipped model AFAIK, so you're fine
without system.img. Hope this helps! :)

Florian

2013/9/26 François Leblanc :
> Hello
>
> I get in trouble.
>
> script/touch try to mount system.img but I dont't see scripts in
> saucy-preinstalled-touch-armhf.zip creating this file system.img
>
> Moreover in saucy-preinstalled-touch-armhf.zip extracted and untar I have
> SWAP.swp file but touch script try to mount SWAP.img...
>
>
> I have certainly missed something...
>
> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/saucy-preinstalled-touch-armhf.zip
>
> and
>
> scripts/touch
>
> seems not made to work together...
>
> Where is my mistake?
>
> 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

Re: [Ubuntu-phone] compile error: 'RLOGD' was not declared in this scope (hardware/samsung/ril/xmm6260/libril/ril.cpp)

[Florian Will]

Hi Marcel,

something is strange with your source tree -- android_system_core was
last changed ~1 month ago (by Ricardo Salveti de Araujo), and the most
recent cyanogen commit in the android_system_core ubuntu repo is from
july [1].

[1] 
http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_system_core.git;a=shortlog;h=refs/heads/phablet-saucy

Are you sure that your manifest is correct and everything synced?

Cheers,
Florian

-- 
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] compile error: 'RLOGD' was not declared in this scope (hardware/samsung/ril/xmm6260/libril/ril.cpp)

[Florian Will]

Sorry, I misread your post. I stand corrected. :-)

Florian

-- 
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][ubuntu core apps][whatsapp]

[Florian Will]

Am 29.09.2013 12:48 schrieb "Jodie Robinson" :
>
> I seem to remember reading a thread in this list about no app being able
to run in the background, so how would WhatsApp get any messages when
you're doing something else?
> I'm not familiar with any touch code, but I see this as a problem, or am
I missing something?

I think you're right. The Ubuntu music app for example needs a special
whitelist exception so it keeps running if the user switches apps. So
whatsapp for 13.10 would be very limited I guess.

> Also I would expect whatsapp to be ported over sometime anyway.

If Ubuntu touch gains some decent market share, I believe whatsapp will
offer an official app soon. Gaining that market share might take some time
though..

Cheers
Florian
-- 
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, initramfs-tools] initrd: Couldn't find data partition.

[Florian Will]

Pass datapart=/dev/mmcblk0p6 on the kernel cmdline.

See my post from a few weeks ago on this list for more info, I'm on my
phone right now. :)
Am 09.10.2013 02:55 schrieb "Marcel Partap" :

> D'OH!..
> praise # adb wait-for-device && beep ^^
> Well so although the device is not proceeding beyond the samsung logo,
> adb is up after all. Must have been a slack data cable before..
> > # ls -la /dev/disk/by-name/
> > lrwxrwxrwx115 ES -> ../../mmcblk0p1
> > lrwxrwxrwx115 MC -> ../../mmcblk0p5
> > lrwxrwxrwx115 MM -> ../../mmcblk0p7
> > lrwxrwxrwx115 SS -> ../../mmcblk0p8
> > lrwxrwxrwx115 LX -> ../../mmcblk0p9
> > lrwxrwxrwx115 AP -> ../../mmcblk0p2
> > lrwxrwxrwx115 IS -> ../../mmcblk0p4
> > lrwxrwxrwx115 CC -> ../../mmcblk0p3
> > lrwxrwxrwx115 UA -> ../../mmcblk0p6
> anyway so it seems I'm at the same point Patrick Seemann is.. how to
> change the scripts/touch file to accept UA as partition name?
> #Regards/Marcel^^
>
> --
> 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] Installing click packages without Ubuntu-one

[Florian Will]

Hi,

Additionally, I'd like to be able to install click packages using the
file manager GUI. Just like apks in Android (if you enable that
feature, which is also a security risk if you don't know what you're
doing).

Last time I tried it didn't work, but it was a few weeks ago.

Cheers,
Florian

2013/10/14 Nicolas Delvaux :
> Hi everyone,
>
> I'm enjoying Ubuntu Touch on my Nexus4 so far, except for one detail.
> I noticed that it is required to be connected to an Ubuntu-One account
> in order to be able to install any app.
>
> Is this a bug or a feature?
>
> I understand that it could be needed to buy apps. But for the free ones
> I don't see why it should be a requirement (and it adds one more privacy
> concern).
>
> Thank you for your work.
>
> Cheers,
> Nicolas
>
> --
> 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] Thoughts on inhibiting app suspend via application lifecycle

[Florian Will]

Hi,

Am 25.10.2013 19:48, schrieb Thomas Voß:
> One thing that strikes me: Instead of trying to solve the problem a
> lot of "won't work" statements are made in this thread, going along
> with a request for removing all of the lifecycle policies. And to be
> clear: With strict policies in place, it is always possible to find an
> example that breaks. So I think we can stop collecting breaking
> examples here.

I disagree. If you want Ubuntu Touch to be successful, you need users.
And users want apps. In order to be able to offer a rich selection of
apps, you also need app developers. Limiting app developers to basically
create wrappers around system services might alienate them.

Sure, in order to avoid the android background service mess, a strict
lifecycle policy is required and I like most of your ideas. Create
powerful system services that make it possible to do stuff easily and in
a power-efficient way.

But there *are* apps where "one size fits all" doesn't work and
something like an actual background service (or wakelock & no suspend)
is required. Any app developer who whishes to create such an app will be
unhappy and might consider not creating anything for Ubuntu Touch at all.

The more "breaking examples" we can enumerate, the more app developers
are possibly affected. Let me add one breaking example that sells (from
my "poor student" POV) relatively well on Google Play and had more than
200k downlods and a rating of 4.5/5 in the short time span when it was a
free download, so there is an interested user base for something like that.

The app takes a file produced by some other popular app. That file grows
larger than a few MBs quite fast. The file's content is analyzed and the
app creates statistics based on the file contents. Since that process
can easily take a few minutes (sometimes 20 minutes) even on modern
hardware, it is done in a background process while holding a (partial)
wakelock. Every night the statistics are updated (taking <1 min
usually), triggered by an alarm and while holding a (partial) wakelock.

The only possible solution for this on Ubuntu Touch? "Please wait. ETA:
20 mins. Also, please touch the display once every 30 sec and don't
leave this app. Thank you."


I suggest allowing background services, but only if the developer can
state a very good reason when doing the upload and generally advice
against using it whenever possible. This would need some kind of
pre-approval so dev work is not wasted in case the approval fails. I
think most apps work without the background service, so it's not a lot
of review work. Also, if a background service is active, indicate that
to the user (or maybe only after ~30sec of activity) and allow them to
cancel the operation and disable background work for that app.

Cheers,
Florian

-- 
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] Thoughts on inhibiting app suspend via application lifecycle

[Florian Will]

Hi Rick,

Am 27.10.2013 16:25, schrieb Rick Spencer:
> This sounds kind of far fetched. Who would do something like this on
> their phone? 

More than 200k android users who downloaded the app that I described. I
don't think "it's a phone!" is a valid excuse for not allowing any CPU
intensive task in a sane way. Maybe I want to mine bitcoins on my phone
while I'm asleep and it's connected to the charger? (Okay now this is
really hypothetical..)

> I think it's fair to point out apps that simply won't work for users
> (Spotify for example), but we shouldn't optimize for entirely
> hypothetical situations.

I described such an app in my mail from earlier today, and it's in fact
not at all hypthetical, but you can download this app for android if
you'd like to.

To be more clear, the file being parsed by the app I described contains
a history of messages exchanged using an instant messenger app.
Apparently, there's a user base interested in statistics about their
chat history.

I realize this specifc app won't work for at least one other (good)
reason on Ubuntu Touch. The confinement won't allow my app to access
files created by another app without the user's explicit agreement,
which is not required on Android for files on SD. But that is not my
point. I just want to be able to use the CPU in my phone if I ever feel
the need to do so. And I also want to allow others to use any CPU
intensive apps I created if they like it. :-)

I'm fine with restrictive defaults and requiring user effort to allow
"possibly unwanted things going on in the background" for specific apps,
but I don't agree with making those *possibly* unwanted things generally
impossible. I consider my phone to a computing device after all.

Cheers,
Florian

-- 
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] Queries about performance on some phone.

[Florian Will]

Am 28.10.2013 09:27 schrieb "François Leblanc" :

> How does it run for over device? It's fluently? Responsive? Fast?

On HTC vision (desire z) it's not too bad. Scrolling is not as smooth as it
is in android and app launches takes a few seconds... But nothing takes 10
or even 15 seconds. And that phone is old. Alright, the first boot does
take longer than 15 seconds, more like 5 minutes.

Have you checked top to see if something is burning CPU cycles?

Cheers,
Florian
-- 
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

[Florian Will]

(writing from my phone)

I'm not sure if this is still true, but a few weeks ago porters were
recommended to just use the old "cdimage-style" flipped model. It means to
just have the extractes rootfs files in /data/ubuntu and the Android
system.img copied in there, which happens automatically when flashing the
rootfs in ubuntu_deploy.sh. The system partition just contains android
stuff with the usual ubuntu patches.

The new "system-img-style" (it's called something like that but not exactly
that iirc) requires a special server to allow OTA updates. That server also
converts the files available at cdimage.ubuntu.com to something different.
It was supposed to be ready for testing with ports soonish, but so far I
haven't heard any news about it. That server also changes the way swap
works afaik.

I think the "supporting ports" thing is something that some of the
canonical employees consider important, so depending on who is responsible
for some feature, you may get a fast  response on IRC. (otoh, some
employees would love to drop deprecated stuff like surfaceflinger, which is
still absolutely required for some ports but slows ubuntu development
speed.  I.e. some of them dont care about ports at all, so..  Good luck. )

Cheers
Florian

Am 18.11.2013 09:56 schrieb "François Leblanc" :
>
>
> I agree this is not clear for me too.
>
> I notice some differences betwen using ubuntu dir and system.img in the
structure of files and even if it is more simple to use dir ubuntu it is
quite difficult to understand how system.img must be.
>
> According to touch script in build kernel they are some files that must
be present but I don't find any documentation  about this, system.img for
example to be put in /var/lib/lxc/android/system.img, swap file is named
SWAP.swp in touch script and SWAP.img in
trusty-touch-preinstalled-armhf.zip ...
>
> Regards,
> François.
>
>
>
>
>
> 2013/11/18 Dmitry Smirnov 
>>
>> Sorry for bothering you again, but I did not understand what is meant to
be new and old flipped models.
>> 'touch' script is using /data/ubuntu as an old model (where /data is the
'userdata' partition).
>> At the same time ubuntu_deploy.sh (included into cdimage.ubuntu.comzips) 
>> unpacks tar.gz into /data/ubuntu.
>> So, there is some mismatch, right?
>>
>> How this cdimage zip is supposed to be deployed for new flipped model?
>>
>>
>>
>>
>> 2013/11/6 Oliver Grawert 
>>>
>>> hi,
>>> Am Mittwoch, den 06.11.2013, 12:49 +0200 schrieb Jani Monoses:
>>> > 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
>>>
>>> the cdimage-legacy install variant is still available in phablet-flash,
>>> it installs the mobile world congress demo from feb. which has pretty
>>> pictures instead of apps.
>>>
>>> we stopped building such images long ago ;)
>>>
>>> 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
>
-- 
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] Connect to phone from Mac

[Florian Will]

There's a good reason why Google switched from mass storage to mtp. This is
even more true for ubuntu touch.

For mass storage, you need a FAT partition (most devices don't support ext4
etc.). So ubuntu touch would have to switch to FAT for the home partition
(or keep ext4 and make it impossible to mount anywhere but Linux desktops).
And since you can't mount the same FAT partition on two devices at the same
time, it's impossible to access files in your home dir when it's mounted on
a PC.

IMHO, mtp is a much better way to access files on devices. Unless there are
hacks to solve the partition type issue.
-- 
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] How to create Android/Ubuntu zip files when building from source?

[Florian Will]

Once your cyanogen/android parts build correctly, it's quite easy actually:
flash the cm-date-unofficial.zip created during compile (it's in
out/target/product/devicename/), then flash the trusty-preinstalled-armhf
zip file. Then you may have to adjust all kinds of things in android or
ubuntu parts to make it work with your device, i.e. even the boot might
fail. This still works for me as of November 19.

This is not the new "systemimg" style, but it's the old-style "cdimage" way
of setting up things. It's still a flipped container model though, not the
very old "unflipped"  model. Afaik, it's still recommended for ports to use
cdimage style (but I'm possibly not very up to date regarding this).

Cheers
Florian
-- 
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] UT music app cannot find mp3 on desktop

[Florian Will]

Hi Sayantan,

Am 01.12.2013 11:34, schrieb Sayantan Das:
> How do I get the app to recognize the files, or maybe change the path of
> the folder?

I've never used it on the desktop, but I think I remember the music-app
uses the grilo media scanner to find music (just like gnome-music does).

Unfortunately I don't remember how to get grilo to work. Maybe google
can help. I think after installing grilo, you need to start an initial
scan..

Cheers,
Florian

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

[Florian Will]

Hi,

2014/1/16 Chris Wayne 

> After some digging around the system, the following types of
> device-specific files are currently living in our rootfs:
>
>- upstart jobs in /etc/init
>- udev rules (in /etc/udev/rules.d and /lib/udev/rules.d)
>- ubuntu-touch-session configs (basically just telling the system the
>number of pixels in a GU IIRC) (in /etc/ubuntu-touch-session.d/)
>- lxc container configs (in /var/lib/lxc/android/pre-start.d and
>/usr/lib/lxc-android-config/)
>- powerd configs (/usr/share/powerd/device_configs/)
>- apparmor policies (/usr/share/apparmor/hardware/)
>- binaries/scripts (i.e. /usr/bin/brcm_patchram_plus)
>- ofono plugins/configs (not in the image now, but there will likely
>be device/modem-specific files for these in the future AIUI)
>
>
I realize this won't help with finding a solution, but for completeness
sake, let me add three more things to this list that I (as a porter) change
in the rootfs:
 * Alsa ucm files for msm-audio in /usr/share/alsa/ucm (I'm not sure if the
same files can be used for all devices using the msm chipset, may need to
be adapted for each device?)
 * /etc/fstab to specify the system partition device node because
auto-detection fails for some devices (possible fix is
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1199084
 )
 * /home/phablet/.display-mir to enable Mir by default (I've seen a script
that does this for official devices, but the device names are hard coded so
a rootfs change is needed anyway if you don't want surfaceflinger)

There are more rootfs changes in my port, but those are related to my
hardware not meeting the Ubuntu Touch minimum requirements. I.e. deleting
the 9mb /var/log/lastlog file, removing apt caches, removing apt package
lists, removing some icon sets and a help language pack to free up space,
and changing the recovery flash script to use sdcard instead of /data for a
temporary file.

Cheers,
Florian
-- 
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] Problems with UCM audio config

[Florian Will]

Hi,

Am 29.01.2014 22:54, schrieb f69m:
> Any ideas?
> Anything would be helpful: how to get more verbose logging from the UCM
> handlers,

Maybe I can help with that:
Check the exec lines in [1], works for me to get some logging at least.
Well, it worked when I created those ucm files, maybe it has stopped
working for some reason.

[1]
https://github.com/w-flo/rootfs-modifier/blob/master/replacements/targz/usr/share/alsa/ucm/msm-audio/HiFi

Cheers,
Florian

-- 
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] 154 image - mako doesn't boot

[Florian Will]

Hi Elad,

2014-02-01 Elad Avron :
> If you install a valid image (one that boots) and then try to upgrade using
> apt-get, next boot will again hank on the blank backlit screen.

Using apt-get to upgrade is not supported (and in fact, with official
"system-image" supported devices you can't even use it because / is
read-only).

Sometimes you're lucky and apt-get upgrade works, but sometimes it fails.

For "system-image" devices, the system-settings update feature works.
For other devices, you need to reflash manually.

Cheers,
Florian

-- 
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]Need help

[Florian Will]

Hi Lukas,

Sounds like you need to extract proprietary files from a working phone.
Cyanogenmod usually has a script to pull those files via adb.

I don't remember the exact steps, but Google / the cyanogenmod wiki should
help.

Cheers,
Florian
Am 03.02.2014 11:45 schrieb "Lukas Krotovic" :

> Hi,
> I'm trying to port Ubuntu Touch to Samsung Galaxy W but I got this error:
>
> make: *** No rule to make target `vendor/samsung/ancora/proprietary/bin/rild',
> needed by `/ubuntu-phone/out/target/product/ancora/system/bin/rild'.
>  Stop.
>
> What can I do?
>
> 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
>
-- 
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] universe vs. main packages in the image

[Florian Will]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Am 30.01.2014 16:20, schrieb Oliver Grawert:
> i started with assembling a list of the packages that come from
> universe today: grilo-plugins-0.2 grilo-plugins-0.2-mediascanner

I've been following the grilo MIR bug - it's exactly 1 year old now.

https://bugs.launchpad.net/ubuntu/+source/grilo/+bug/1116098

So no need to file a new bug for grilo I guess.

And I have my hopes up to finally have grilo enabled in
rhythmbox/totem so I can finally use my DLNA share without
recompiling. :-)

Cheers,
Florian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS8lwuAAoJEMCEdH2UCvz22YUH/iXc0wrfo2l+r2gFzXv9j9LL
iMl5BOzf/1EdrWmPJ25V4JtNa7/sy/melkc4GmM8Qz6ZUMlsk4A8WN1LTSUmeevi
swfrloefyabBcDBuYX8vm5ktN+68iBjB6ipV53QdCIX3vArBcll9cx7GYfuWXerZ
XDaid531AVfSuxFL2VQd3exZSCfXAxQffykRLuaRmA5B2dz72HgcYnxQo/oc7/12
rOWAuMzlGsQZf2sSNPqXnuiceavhgdLpYUjZpTTWcWgCzV7TfNfs+zEeXzvy2PF0
hEKg0RU0KaCg+pRFa1RLyvPeaHw+hWHjBFfo3ekTfMCqG8V0owKS3k/EFXv2/8c=
=tIos
-END PGP SIGNATURE-

-- 
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] No more custom home screen backgrounds?

[Florian Will]

The fixed bug appears to be about brightness settings getting lost after
screen turns off.

The non-customizable background is probably a design decision because it
"strengthens the ubuntu brand" or something like that.
Am 26.03.2014 19:12 schrieb "Alex Chiang" :

> On Wed, Mar 26, 2014 at 9:28 AM, Jamie Strandboge 
> wrote:
> > On 03/26/2014 10:12 AM, Jason Warner wrote:
> > ...
> >> On Tue, Mar 25, 2014 at 10:37 AM, Iain Lane  >> > wrote:
> >>
> >>   - Is there any chance we can have this feature back please? I for
> one
> >> enjoy the ability to customise the appearance of my phone and
> I'm
> >> pretty sad that this has gone away.
> >>
> >> I'm in this camp as well. I know I've changed my iOS or Android
> background to
> >> something rather unpleasant and quickly changed it to something else.
> >>
> >
> > +1
> >
> > Changing the background is a simple customization that can have a big
> impact on
> > people's impression of the phone.
>
> Guys -- rsalveti already said it was Just a Bug (5 mails back) and
> that a fix is in CI train already.
>
> --
> 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] Building for HTC Desire HD (ace)

[Florian Will]

Hi,

Am 01.05.2014 15:48, schrieb Adam Pigg:
> 1) the file is only 27mb, i must be missing something??

That sounds about right, I have ~30MB for the Desire Z. Remember it only
contains hardware abstraction layer components, no dalvik etc.

> 2) the /boot on the ace i 4mb.  The boot.img is 5.1mb.  Is there any way
> to shrink the boot.img?  Re-partitioning the ace isnt straight forward,
> i cant find anyone who has done it before.

Same issue with Desire Z. I managed to shrink the kernel size
considerably by changing kernel compression to XZ and disabling a lot of
kernel features. Now I don't have IPv6 (I might have disabled bluetooth
as well?) and a bunch of other stuff, but at least it can boot.

The "kernel" file in out/target/product/vision is now only 1.9MB, but
that still was not enough. I also had to remove libcrypto.so from the
initrd because it's really huge. That breaks adbd, so I removed that as
well.

In order to do early boot debugging, I remember had to use adbd once. I
think I disabled printk support in the kernel in order to make it even
smaller than 1.9MB so libcrypto would fit into /boot. Or maybe I
disabled some safety checks in boot.img creation that require some free
space left, or maybe both.. I don't remember.

See this file to remove adbd and libcrypto.so: [It also changes the
touch boot script to use the correct partitions, you probably don't want
that part.]
https://github.com/w-flo/android_device_htc_vision/blob/ubuntu-system-image/shbootimg.mk

Regards,
Florian

-- 
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] Building for HTC Desire HD (ace)

[Florian Will]

Hey,

Please note that all of my Ubuntu Touch knowledge is a few months old
already, so parts of this mail might be out of date.


Am 01.05.2014 16:32, schrieb Adam Pigg:
> Where are the other parts of ubuntu downloaded from for installation,
> are they just .zip files to install from recovery?

They used to be flashable zip files (actually, just one zip file) called
the "ubuntu rootfs". I haven't used the flashable zip in a long time,
not sure if it still works, but I guess so:

http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/

If the ace has similar flash size specs compared to the vision, that
might be a problem. About half a year ago (?), the size of ubuntu's
rootfs from that zip file was pretty close to 100% of my /data size. I
guess it's even larger now.

To add insult to injury, there is bug 1145984: The zip file contains a
.tar.gz file which is extracted to /data first, then the .tar.gz is
extracted to /data as well, then the .tar.gz is removed. Obviously that
won't work with our low-spec devices with smallish /data, but there is
some free space on /data after flashing (because the .tar.gz was
removed). So you might think that everything worked fine, when in fact
the .tar.gz extraction failed badly and most of the rootfs files are
missing.

You might want to repartition the SD card and mount /data from there,
that way I managed to get system-image (see below) working. I also had
to mount /cache from the SD card though. Or maybe you can modify the
flash script to unpack the .tar.gz file to /mnt/sdcard instead of /data,
I have a modification like that in my rootfs-modifier repo on github.
You might also want to manually remove stuff from the .tar.gz so the
files fit onto your /data partition.


The modern way of installing the rootfs and device-specific tarball is
through the system-image mechanism that also provides OTA updates (which
are mostly broken sometimes on devices with low RAM unless bug 1271684
was fixed in ubuntu system image). It requires that you repack your zip
using some new tools that I haven't tried yet (I played with
system-image before the community-friendly system image server was
introduced). For system-image you'll need the ubuntu-specific recovery
that was probably built alongside your device-specific 27MB zip file
(recovery.img). The recovery GUI fails to work correctly on the vision,
but the automatic flash process still works fine.

Have fun!
Florian

-- 
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] Renaming to: Ubuntu App Launch

[Florian Will]

Hey,


2014-05-22 18:13 GMT+02:00 Ted Gould :
> If you have a dependency that you know of that I'm unlikely to find,
please mention it.

You will probably find this sooner or later in the security tests:

http://ci.ubuntu.com/smokeng/utopic/touch/mako/65:20140604.1:20140530/8401/security/1210870/

Regards
Florian
-- 
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] Background services: a problem that we need to face

[Florian Will]

Without long-running network connections, XMPP is at risk as well. Just
like IRC, you'd need a proxy or control the XMPP server to be able to send
push notifications. I guess there are a few more use cases where push
notifications won't cut it.

Generally, control and transparency are important to me. Control:
allow/disallow apps to use long-running background services. Transparency:
Be able to check if apps use the background service, for how long do they
use it, how many processor cycles are used for it, etc. Maybe even
notifications that display daily/weekly summaries of background task usage.

Obviously, most users are not interested in control and transparency, they
just want a phone that works and lasts long with a single charge. So I do
accept the very strict and conservative Ubuntu Touch approach. Nobody uses
XMPP or IRC anyways, and WhatsApp will happily send push notifications. I'd
still love to have the control in some kind of experts mode that doesn't
involve recompiling the Ubuntu stack.

Otherwise, a one-off app that simply requires a background task could
probably abuse push notifications and have a server send a new push
notification every minute to be able to do some processing. Or set a
geofence with the smallest possible radius, now really wasting energy. Or
abuse one of the other services. It's difficult to come up with apps that
require this. However, I could imagine apps that need to do some processing
that takes longer than a few seconds (like processing data that was
collected on the phone, maybe through sensors or from the internet, to
create statistics based on that data). Right now, the user is forced to
keep the app open and the screen active, or lifecycle policy will pause the
processing. I'm sure there are more use-cases that can't be solved using a
generic service.
-- 
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] Wiping phone after testing

[Florian Will]

Am 02.07.2014 09:50, schrieb Martin Pitt:

Hi,
> I've heard that we have some magic with using 
> /cache/recovery/ubuntu_commands. There's nothing in the wiki, just 
> some allusions that it exists [2].

I'm sure an ubuntu recovery developer could shed some more light on
this (stgraber?). AFAIK, the script processing that ubuntu_commands
file is in the recovery git repo, the latest of which is probably this
one:

https://code-review.phablet.ubuntu.com/gitweb?p=aosp/platform/bootable/recovery.git;a=blob;f=system-image-upgrader;h=035625b1bc5e0b4580c85b2998d96ca8d6f11851;hb=refs/heads/phablet-4.4.1_r1

So it seems like only format, mount, unmount and update commands are
supported. Maybe you can get away with simply formatting data (see
line 147 of that script) to reset everything? Sounds like that should
reset everything to its clean state.

And it looks like you can do that without requiring a valid signature
(update requires a valid signature, and you probably don't want to
distribute the ubuntu image signing key with the SDK..). Unless the
ubuntu_commands file needs to have a valid signature that is checked
from C code, which I doubt.

Regards
Florian

-- 
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] [Development] Trimming down initial rootfs size

[Florian Will]

[Resending because my earlier mail was probably rejected due to using a
bad mail address]


Hi everyone,

I know this is probably not a priority with the development currently
mainly focused on getting features ready. And in the future, it might
even be less important because devices will have more storage capacity.
So I'm prepared for answers like "Nope, sorry!".

But still, I'm currently testing Ubuntu Touch on my old smartphone, and
the /data partition of that device is only 1gb. The default way of
installing the root file system on /data fails with that device, because
the extracted rootfs and the tarball don't fit within /data at the same
time. I have posted a merge request for the tarball creation scripts [1]
that fixes this problem by storing the .tar.gz on /sdcard, maybe this
can be used as the default for future tarballs? It would definitely make
life easier for anyone aiming to provide images for older devices with
small /data.


Another problem is that /data quickly reaches a point where it has
almost no free space left when using the device (because of logs etc.).
A few problems I've had were actually caused by this, like some
networking tools (wpa_supplicant? network manager?) refusing to connect
to wifi when df shows that there is less than 100mb storage capacity
available on /data.

I've looked through the rootfs.tar.gz and noticed a few "low-hanging
fruits" for trimming down the size. There are probably more. Do you
think it's worthwile to care about them? Or is it considered a very low
priority, as long as it is okay on the officially supported devices?

Examples that are probably free of negative side-effects:
  * /var/log: 9mb lastlog and other logs that could be rm-ed before the
tarball is created
  * /etc/apt/sources.list: Disable the source package archive, so there
are fewer big files in /var/lib/apt/lists (I don't think there are a lot
of use-cases where this needs to be enabled, also speeds up apt-get
updates I guess)
  * /usr/share/icons: Not sure if the Humanity icons are needed at all
(14mb). I guess the svg icons for Ubuntu Touch are required, otherwise
they could be removed to save another 10mb.

Example that has negative effects on performance:
  * Disable binary apt caches and delete /var/cache/apt/*.bin as
described in [2]. Performance for apt operations will suffer, but it
reduces rootfs size by almost 50mb.

Of course, after installing the rootfs, a whole lot of space can be
reclaimed by uninstalling the demo-* packages. These are probably
supposed to be included with the official rootfs though. :-)

Cheers,
Florian

[1]
https://code.launchpad.net/~florian-will/touch-preview-images/phablet-build-scripts-extract-from-sdcard/+merge/172300
[2] https://wiki.ubuntu.com/ReducingDiskFootprint#Disable_apt_caches

-- 
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] Trimming down initial rootfs size

[Florian Will]

Hi Sam,

Thanks for your hint! And I'm really sorry for spamming your inbox. I
finally noticed that I was clicking the wrong button in Thunderbird all
the time. Now this reply should actually go to the list as well...

Am 02.07.2013 22:10, schrieb Sam Segers:
> until I found it I needed:
> run_program("/sbin/mount","/ext/sdcard");
> and not
> run_program("/sbin/mount","/sdcard");

That's a problem. /ext/sdcard is not listed in fstab in my recovery
(4ext for Desire Z). I was hoping that /sdcard is universal, but
apparently not!

I guess that using something like
  if /data is larger than THRESHOLD mb: use /data
  else if /sdcard is in fstab: mount and use /sdcard
  else if /ext/sdcard is in fstab: mount and use /ext/sdcard
  else if /whatever/other/recoveries/use is in fstab: [..]
  else: error()
could solve the problem, but it's just too much for my shell scripting
skills. ;-)

Cheers,
Florian

-- 
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] HTC Desire Z Porting.

[Florian Will]

I can't reply to the original mail because I was not subscribed at that
time. Also, I'm sorry for spamming your Inbox, Nicholas. This reply
should finally go to the list.

>> http://pastebin.com/7FWmRa9w

Not sure what the problem is there.

>> and also can you tell me if for the HTC Desire Z We have to flash the
>> normal
>> saucy-preinstalled-phablet-armhf.zip

I think that this is the correct zip file, the other one
(*-touch-armhf.zip) is probably the "flipped" image, where android runs
inside a container? I'm not sure, but the one you linked above works for
me with some modifications, see my recent mail to this list about
trimming the rootfs size.

BTW, I have wifi working using the most recent Andromadus (Flinny et
al.) repositories and some small changes. I have pushed my repos to
github [1]. I might post a flashable zip to XDA, but am still hoping for
Ubuntu to create zip files that can be flashed without modification,
because I don't really want to upload a 300+mb file using my 50kb/s
internet connection.. :-)

Cheers,
Florian

[1] https://github.com/w-flo/android/blob/master/default.xml

-- 
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] Compiling armhf binaries for a phone target - toolchain from where?

[Florian Will]

Sorry, forgot to send this to the list as well. Second try.

I've had success compiling my packaged app for armhf using pbuilder-dist.
It uses virtualization, so it's rather slow.

Creating a Debian source package with qt c++ compiling support involves
some googling, but debhelper supports it and it's not really difficult.

The resulting deb file works on my phone. Not sure how c++ code will be
handled with click packages, AFAIK they will land soon and apt will no
longer work, unless you enable developer mode.

Cheers
Am 15.07.2013 12:20 schrieb "John McAleely" :

> Hi,
>
> I have some C/C++ code that (eventually) I want to run on an Ubuntu Touch
> phone or tablet.
>
> This may be some sort of interim step before achieving Qt/QML nirvana, or
> this may be a subsystem a Qt app will depend on (I'm doing some early
> experimentation, and may yet be chasing the wrong ideas).
>
> I'm not (for the sake of this question) planning to build the Android
> underpinnings, so one of my start points has been not to assume I have that
> source tree available (I understand it may have some toolchains in it). Is
> that wise?
>
> I believe I need a toolchain to compile this code, and I have (at least)
> three options presented in chats/wikis/docs I've googled/assumed might work:
>
>  (1) Compile on the device itself
>  (2) Install the Ubuntu SDK
>  (3) Install a cross-compilation toolchain on my (amd64) Ubuntu dev machine
>
> I can succeed at (1), by installing whatever defaults build-essential
> requires.
>
> I'm not sure if (2) should succeed - it's not clear to me if the Ubuntu
> SDK does or will recommend/install a c/c++ toolchain. The one I installed
> today doesn't appear to. Will it at some point? Did I just not see the one
> it did install?
>
> for (3), if I try:
>
> # apt-get install crossbuild-essential-armhf
>
> I get:
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies.
>  crossbuild-essential-armhf : Depends: libc6-dev:armhf but it is not
> installable
> E: Unable to correct problems, you have held broken packages.
>
> My initial troubleshooting (I'm definitely inexperienced in Ubuntu package
> matters) hasn't turned up a way to proceed past that error yet.
>
> So, which is the most pragmatic way to proceed? I'm keen to get a cross
> compilation toolchain working. Should I be?
>
> In the future, what will the options be to compile C/C++ for touch devices?
>
> Thanks!
>
> J
>
> --
> Mailing list: 
> https://launchpad.net/~ubuntu-**phone
> Post to : 
> ubuntu-phone@lists.launchpad.**net
> Unsubscribe : 
> https://launchpad.net/~ubuntu-**phone
> More help   : 
> https://help.launchpad.net/**ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp