[Ubuntu-phone] [DEV] Porting Ubuntu Touch to K860 (Stuttgart)

[Reezqy Gilla]

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 phablet-saucy). The compile process goes just fine. But when I try to
boot it, it stucks at Lenovo logo (Splash screen). Adb doesn't detect it so
I don't know how to debug it. So, can anyone please tell me where the
problem possibly lies and how can I fix/'debug it? 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

[Ubuntu-phone] Ubuntu touch ramdisk compression format.

[Reezqy Gilla]

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 boot. (Stucks at splash screen) And adb won't detect my device.
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

[Ubuntu-phone] Init-premount or local-premount?

[Reezqy Gilla]

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

[Ubuntu-phone] console argument at boot cmdline

[Reezqy Gilla]

   - "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 . Make
   sure you have proper permissions in the ramdisk and /init can start. Make
   sure you have a valid console=... argument on the kernel command line."


"Booting by default into the Ubuntu rootfs

To run Android in a container Ubuntu needs to become the default system we
are booting to. This is achieved by using a generic Ubuntu initramfs in the
phones boot.img instead of the Android supplied one.

The initramfs script that manages the booting lives in the
*initramfs-tools-ubuntu-touch* package. To get a binary initrd.img the
*ubuntu-touch-generic-initrd* package exists, this will always contain
the latest
binary initrd.img based n the last *initramfs-tools-ubuntu-touch* package
in the Ubuntu archive.

People that are porting their devices to the Ubuntu Touch container model
should take into account that Ubuntus upstart is used as init system.
Upstart likes to have an actually existing device as /dev/console. Many
Android kernels do not provide this as default or even have something
like console=none
or console=ram hardcoded in their boot commandline arguments. Such
drawbacks in the kernel or commandline need to be fixed to be able to use
this model properly (here  is for example
a kernel patch used on the i9100 image to change the behavior of
CONFIG_CMDLINE_EXTEND ... now using this option appends the kernel cmdline
to the bootloader one instead of pre-pending, this way console=tty1 can be
handed over as the last cmdline argument and withCONFIG_VT_CONSOLE and
CONFIG_HW_CONSOLE set in the kernel config upstart is now happy)"


So I'm getting a stuck on boot (splash screen, more specificly), and adb
didn't detect my device. I've installed google android drivers and my
device's drivers. Is it relevant with the first quote?
If yes then does "valid console=... argument" means something like
"console=ttySAC3" (this is the default on my device's kernel cmdline),
"console=tty1" (this is the one written in the container article)
"console=" (empty) or just no "console" argument?
I have tried the kernel patch example and enabled CONFIG_CMDLINE_EXTEND,
and the /proc/cmdline now has two console arguments, the first one is
"console=ttySAC3,115200n8", and the last one is "console=tty1,115200n8" But
it still doesn't boot.
And what does it mean by proper permissions in the ramdisk?

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

[Ubuntu-phone] autodeploy or normal flash

[Reezqy Gilla]

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 : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] [Porting] About android-ramdisk.img

[Reezqy Gilla]

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://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Ramdisk

[Reezqy Gilla]

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 container. It loads ubuntu, then android
inside lxc.

CMIIW

Regards,
Rizqi
On Dec 9, 2013 7:44 AM, "Ryan."  wrote:

> Is the initramfs universal or build per device ?.
> Can someone provide me with a working one\?
> --
> 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
>
>
-- 
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] Ramdisk

[Reezqy Gilla]

Ubuntu's initramfs is meant to be universal. But some devices might need
some hack for it to work.

Regards,
Rizqi


On Mon, Dec 9, 2013 at 11:03 AM, Ryan.  wrote:

> Ok , just fyi, I knew it was on the boot.img which is why i asked , as
> each boot.img is different for each device.
>
> 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'm charging it lol
>
>
> Reezqy Gilla  wrote:
>>
>> 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 container. It loads ubuntu, then android
>> inside lxc.
>>
>> CMIIW
>>
>> Regards,
>> Rizqi
>> On Dec 9, 2013 7:44 AM, "Ryan."  wrote:
>>
>>> Is the initramfs universal or build per device ?.
>>> Can someone provide me with a working one\?
>>> --
>>> 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] console=tty1

[Reezqy Gilla]

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 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] console=tty1

[Reezqy Gilla]

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  wrote:
>
>> Oh right, I forgot to mention that I've done that.
>> Sorry,
>>
>> Rizqi
>>
>>
>> On Sat, Dec 14, 2013 at 6:35 PM, Oliver Grawert  wrote:
>>
>>> hi,
>>> Am Samstag, den 14.12.2013, 14:43 +0700 schrieb Reezqy Gilla:
>>> > 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?
>>>
>>> see https://wiki.ubuntu.com/Touch/ContainerArchitecture i linked an
>>> example kernel patch there that flips the chain of kernel options
>>> (putting bootloader options last) on a galaxy S2 port.
>>>
>>> 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