Hi, I'm a noob here, and I'm trying to port ubuntu touch developer preview
to Lenovo K860 (Stuttgart). I'm using CM 10.1 as the base. I've followed
everything in the guide except the apparmor stuff and patches from
Touch/AndroidDevel (Do I need to do that too? Because I downloaded the repo
from pha
As the title says. Can anybody tell me what's ubuntu touch's ramdisk
compression format? The one that we can get by splitting boot.img. The
boot.img-ramdisk.gz. Because I can't extract it with gzip, 7z, xz, winrar,
and lzma. I also want to know if my boot.img's ramdisk is corrupt since it
won't boo
Hi,
So I've been wondering, in the ramdisk, the init (at premount line) runs
the script in /scripts/init-premount, but the premount folder in scripts
folder is local-premount, and there's no init-premount folder or file. Was
it really meant to be like this?
Thanks
Rizqi
--
Mailing list: https://
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 lat
- "The device is in a bootloop or hangs on boot not showing up with adb
shell: boot into recovery mode and adb pull /proc/last_kmsg to check the
previous dmesg. Do not power off the device between the hang and booting
into recovery as that likely leads to losing the ramconsole contents
Hello,
So there are two zips for ubuntu touch, one for android side and one for
ubuntu side. Do they have to be flashed with autodeploy or is it alright if
I just flash them normally with ubuntu touch recovery?
Thanks,
Rizqi
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubun
Hello,
So my device is using an uboot ramdisk for the boot.img, so should the
ramdisk in /system/boot on the android side be an uboot ramdisk or normal
ramdisk?
Thanks,
Rizqi
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https:/
AFAIK, the ramdisk in the boot.img is ubuntu's initrd, and it's generic. It
was downloaded during the build process.
After the init, it will load android's ramdisk, which is in /system/boot of
the zip built from the source. It will run android under lxc container.
And this is the point of flipped c
.
>
> And I didnt build from source for this particular phone I'm just mix n
> matching files from another devices port and adding my own changes here and
> there for experiments
>
> So far I get adb . Just added sh so i now have adb shell
>
> Battery died so now I
So my device actually has hardcoded console=ttySAC3,115200n8 and
androidboot.console=ttySAC3 in the bootloader.
I've tried overriding it but it doesn't seem to work. It still loads
ttySAC3 after tty1 and use it as the main console.
What can I do to make it set tty1 as the only console?
--
Mailing
CCing ubuntu-phone
On Sat, Dec 14, 2013 at 7:54 PM, Reezqy Gilla wrote:
> And also, it has console=tty1 and androiboot.console=tty1 after the
> ttySAC3 arguments. But it still loads ttySAC3 after tty1.
>
> Rizqi
>
>
> On Sat, Dec 14, 2013 at 7:53 PM, Reezqy Gilla wr
11 matches
Mail list logo