Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Compiling Ubuntu Touch for Xiaomi Redmi 1s

    Porting
    xiaomi redmi 1s
    5
    7
    4813
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alexforsale last edited by NeoTheThird

      I'm compiling Ubuntu Touch for Redmi 1s, the build tree i'm using is from https://github.com/janimo/android/tree/phablet-cm-11.0 and with addition:
      https://github.com/alexforsale/android_device_xiaomi_armani/tree/phablet-4.4.2_r1
      https://github.com/alexforsale/proprietary_vendor_xiaomi/tree/phablet-4.4.2_r1
      https://github.com/alexforsale/android_kernel_xiaomi_armani/tree/phablet-4.4.2_r1

      the problem I'm having right now is the BOARD_KERNEL_CMDLINE defined is not passed to the kernel (my last kmsg http://paste.ubuntu.com/13100099/)

      I even try to change it from the kernel defconfig (CONFIG_CMDLINE) but it still didn't change

      1 Reply Last reply Reply Quote 0
      • mariogrip
        mariogrip Administrators last edited by

        try this tool to check the header of your bootimage

        wget https://dl.dropboxusercontent.com/u/56653875/ubuntu/boot_info && chmod +x boot_info
        ./boot_info boot.img
        

        and look if "Command line:" is correct.

        1 Reply Last reply Reply Quote 0
        • A
          alexforsale last edited by

          Hi Mario,

          I sort of figured out what's wrong, I've unpacked the boot.img using the unpackbootimg from the build, the command line paramater was actually empty. https://github.com/alexforsale/android_device_xiaomi_armani/commit/883d3f8c1c7e5eef97d4e4b21b0c2f5976ded8ac and the command line from BoardConfig.mk is now picked up, http://paste.ubuntu.com/13141705/

          now the device is detected from lsusb, but still no adb, i think the partitions are not mounted correctly

          pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt, i did try symlink the firmware in https://github.com/alexforsale/android_device_xiaomi_armani/blob/phablet-4.4.2_r1/Android.mk, the thing is, in the actual CM 11 this device doesn't have the symlink-ed firmware files in the /system/etc/firmware or system/vendor/firmware

          1 Reply Last reply Reply Quote 0
          • A
            alexforsale last edited by alexforsale

            update:

            I think it got past the mounting process, still no adb detected, but the /data/system-data/ starting to creating logs

            from /data/system-data/var/log

            • dmesg http://paste.ubuntu.com/13215412/
            • udev http://paste.ubuntu.com/13215420/

            from data/system-data/var/log/lxc

            • android.log http://paste.ubuntu.com/13215424/
            • lxc-monitord.log http://paste.ubuntu.com/13215431/

            from /data/system-data/var/log/lightdm

            • lightdm.log http://paste.ubuntu.com/13215438/
            • unity-system-compositor.log http://paste.ubuntu.com/13215440/

            also there's alot on /data/system-data/var/log/upstar, but I think this is troubling:
            lxc.log http://paste.ubuntu.com/13215449/

            1 Reply Last reply Reply Quote 0
            • Y
              ykapoor last edited by

              Anyone still working on this one?

              advocatux 1 Reply Last reply Reply Quote 0
              • advocatux
                advocatux @ykapoor last edited by

                @ykapoor I don't think so. There are some work in progress on other Xiaomi models though, as you can see at https://github.com/Halium/projectmanagement/issues?utf8=✓&q=is%3Aissue+is%3Aopen+xiaomi

                1 Reply Last reply Reply Quote 0
                • U
                  UniSuperBox last edited by

                  @ykapoor, please do not bring up very old threads. The last post here was over three years ago.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post