Re: [Ubuntu-phone] DO NOT UPGRADE PHONE & image server taken down temporarily

2014-10-11 Thread Vojtech Bocek
I've just removed the broken image (version 82) from my s-i.tasemnice.eu server (the one for hammerhead and deb). The same thing applies - if you've already downloaded it, don't install it. It _should_ be safe to update to version 81 though. Fixed image will appear on tasemnice automatically once

Re: [Ubuntu-phone] #292 Mako

2014-04-12 Thread Vojtech Bocek
This is fixed in MultiROM v23. If you have any unbootable Ubuntu Touch installations, install v23 and then go to recovery, Advanced -> MultiROM -> List ROMs -> *ubuntu* -> Re-patch init. If anybody is using images from my system-image.tasemnice.eu without multirom, versions 290 to 292 are broken a

[Ubuntu-phone] Custom system-image server for deb (Nexus 7 2013, 4G)

2014-03-14 Thread Vojtech Bocek
Hi, rsalveti pushed changes for the 4G version of Nexus 7, deb, to gerrit, but I've been told there won't be deb images on s-i.ubuntu.com. So, I've set-up my s-i.tasemnice.eu to build them alongside the hammerhead images. People are reporting that the mobile data work, although the GUI to set APN i

[Ubuntu-phone] Custom system-image server for Nexus 5

2014-03-03 Thread Vojtech Bocek
Since Nexus 5 images are not build on system-image.ubuntu.com, but the code is in the official repositories and since it is possible to make your own system-image server[1], I figured why not make one for hammerhead :) * Address: http://system-image.tasemnice.eu * Channels: trusty and trusty-propo

Re: [Ubuntu-phone] multi-rom

2014-02-24 Thread Vojtech Bocek
The updates work with MultiROM if Ubuntu is installed via the MultiROM Mgr app[1]. It installs images from system-image, and works for mako and grouper. I'll add support for the new flo (and hammerhead, I hope) images in a few days. Updates won't work with the images that you've installed from ZIP

Re: [Ubuntu-phone] Call for testing: experimental 4.4.2 based images

2014-02-05 Thread Vojtech Bocek
ore the path in some file, then it would be okay with whitespaces. But, to be honest, this is not very high on my imaginary TODO list - just type Ubuntu-Touch in there. 2014-02-05 Davide Depau : > > On Feb 5, 2014 1:50 AM, Vojtech Bocek wrote: >> >> Yeah, adding support for si

Re: [Ubuntu-phone] Call for testing: experimental 4.4.2 based images

2014-02-04 Thread Vojtech Bocek
eas it is not feasible to do so for updates via apt-get). 2014-02-05 Davide Depau : > On 02/04/2014 01:25 PM, Vojtech Bocek wrote: > >> MultiROM indeed supports these testing images. Make sure you have the >> latest MultiROM and recovery (I've just released new one) and

Re: [Ubuntu-phone] Call for testing: experimental 4.4.2 based images

2014-02-04 Thread Vojtech Bocek
MultiROM indeed supports these testing images. Make sure you have the latest MultiROM and recovery (I've just released new one) and follow instructions in the XDA thread[1], under "Adding ROMs" -> "3. Ubuntu Touch". [1]: http://forum.xda-developers.com/showthread.php?t=2457063 PS: Sorry to Davide

[Ubuntu-phone] [PATCH 1/2] [PATCH] UBUNTU: Support copying of atags in the decompressor.

2013-02-22 Thread Vojtech Bocek
php?t=1266827 [2] Original repository: http://git.io/EXpn2A Signed-off-by: Vojtech Bocek --- arch/arm/boot/compressed/Makefile |3 +++ arch/arm/boot/compressed/head.S | 44 - arch/arm/boot/compressed/misc.c | 22 +++ 3 files change

[Ubuntu-phone] [PATCH 2/2] [PATCH] UBUNTU: Enable caching and buffering of whole RAM in the decompressor

2013-02-22 Thread Vojtech Bocek
dboot: http://forum.xda-developers.com/showthread.php?t=1266827 [2] Original repository: http://git.io/EXpn2A Signed-off-by: Vojtech Bocek --- arch/arm/boot/compressed/head.S |6 ++ arch/arm/mach-tegra/include/mach/memory.h |4 2 files changed, 10 insertions(+) diff --

[Ubuntu-phone] [PATCH 0/2] Add support for kexec-hardboot to Nexus 7 kernel

2013-02-22 Thread Vojtech Bocek
Patches are for Nexus 7 (ie. grouper/tilapia) device, the repo name is android_kernel_asus_grouper. These two patches allows Nexus 7's kernel to be booted via kexec-hardboot method[1]. In short, kexec-hardboot is like normal exec, but does full reboot of the device, so that drivers are properly in