On Thu, Nov 21, 2013 at 1:49 AM, Paul Larson wrote:
> http://paste.ubuntu.com/6451729/
>
All devices have a line like this?
[20678.650539] mdm_power_down_common: MDM2AP_STATUS never went low.
Doing a hard reset
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@list
Thanks. Now I can install the deb file. But still some
./build/tools/get-tarball-url.py is missing in this pack. Where can I get this
file? Below is the error message:
./build-emulator-sdcard.sh
+ OUT=out/target/product/generic/
+ [ ! -e out/target/product/generic//ubuntu-rootfs.tar.xz ]
+ ./bui
Hello,
The instructions in the wiki [1] now work for the AOSP 4.4 based tree. It
builds, but when booted on the Nexus 4 there are some Binder transaction
errors likely preventing anything but having the container started. The
hybris changes I did to adapt to 4.4 APIs definitely need more work but
On Thu, Nov 21, 2013 at 9:27 AM, Sergio Schvezov
wrote:
> On Thu, Nov 21, 2013 at 1:49 AM, Paul Larson
> wrote:
>>
>> http://paste.ubuntu.com/6451729/
>
> All devices have a line like this?
>
> [20678.650539] mdm_power_down_common: MDM2AP_STATUS never went low. Doing a
> hard reset
Seems so, but
Greetings,
According to the instructions in https://wiki.ubuntu.com/Touch/Building I need
2 zip files for recovery.
I can find files - e.g. trusty-preinstalled-touch-armel+mako.zip and
trusty-preinstalled-touch-armhf.zip.
I tried to correlate to the "out" tree but they have different structure
I've a look in lxc container android and logcat give me error:
E/linker ( 6379): linker.c:1095| ERROR: Library
'/system/lib/libubuntu_applicat
ion_api.so' not found
When I list dir /system/lib I have /system/lib/libubuntu_application_api.so
present
Does someone can help; I don't understand
One main problem is what does exactly phablet-flash do and how can we do same
for unsupported yet device?
Dmitry Smirnov a écrit :
>--
>Mailing list: https://launchpad.net/~ubuntu-phone
>Post to : ubuntu-phone@lists.launchpad.net
>Unsubscribe : https://launchpad.net/~ubuntu-phone
>More hel
Hi,
I also have the same problem and I do not yet overcome it (due to some lack
of time for this task).
You can refer https://lists.launchpad.net/ubuntu-phone/msg05006.html to get
some more info on it.
Per my understanding (probably not 100% correct) the process of deploying
Ubuntu is the followi
Hello,
I don't see recovery.img in my out directory.
I tried also building "official" mako - same problem.
In CM source tree I can do mka recoveryimage and it works fine - I see messages
related to "Making Recovery image...".
If I try this in UT tree I am getting "no rule" error.
What is causi
I have grabbed it from the link, and tried to install it. But still no luck.
Below is the error message:
sudo dpkg -i android-emulator_20131120-0225-0ubuntu2_i386.deb
dpkg: error processing android-emulator_20131120-0225-0ubuntu2_i386.deb
(--install):
parsing file '/var/lib/dpkg/tmp.ci/control
I spent some time using mako prebuilt images and my Nexus 4.
You need 3 img files, 2 zip files and 2 reboots in recovery mode to get to
working system.
I still don't know how to create the zip files - they're not created by
standard build and contain tgz.
My next step is to make working recovery
On Thu, Nov 21, 2013 at 11:07 AM, leon lee wrote:
> I have grabbed it from the link, and tried to install it. But still no luck.
> Below is the error message:
> sudo dpkg -i android-emulator_20131120-0225-0ubuntu2_i386.deb
> dpkg: error processing android-emulator_20131120-0225-0ubuntu2_i386.deb
>
12 matches
Mail list logo
