8
Plasma mobile

  1. xreactx
    Froyo Jan 27, 2017

    Last edited: Jan 30, 2017

    #21
    horst58 likes this.
  2. ati2k1
    Donut Jan 27, 2017

    ati2k1 , Jan 27, 2017 :
    soon can flash plasma than?:3
     

    #22
  3. xreactx
    Froyo Jan 27, 2017


    #23
  4. nobelium76
    KitKat Jan 27, 2017

    Last edited: Feb 13, 2017

    #24
  5. xreactx
    Froyo Jan 30, 2017

    xreactx , Jan 30, 2017 :
    Update: stripping down android 5.1.1 is currently in the works. I've compiled the ROM; however, it won't boot after install. The kernel seems to work on stable cm12.1 (allowing editing to the cgroup folder).
     

    #25
  6. xreactx
    Froyo Jan 31, 2017


    #26
    hjeko and horst58 like this.
  7. horst58
    Gingerbread Jan 31, 2017

    horst58 , Jan 31, 2017 :
    Exciting
     

    #27
  8. xreactx
    Froyo Feb 1, 2017

    xreactx , Feb 1, 2017 :
    Stripped CM12.1 and modified kernel made... But unable to adb shell into the device. I'll post the ROM and kernel shortly.
     

    #28
  9. xreactx
    Froyo Feb 1, 2017

  10. HypnZ__
    Froyo Feb 1, 2017

    HypnZ__ , Feb 1, 2017 :
    Hi need to install Rom and kernel only or need and firmware to be installed? I'm asking coz I'm at miui v8 now. Thx.
     

    #30
  11. xreactx
    Froyo Feb 1, 2017

    xreactx , Feb 1, 2017 :
    Both. CM is stripped to bare minimum (no GUI) and kernel has lxc added requirements.
     

    #31
  12. HypnZ__
    Froyo Feb 1, 2017

    HypnZ__ , Feb 1, 2017 :
    Thanks for replying mate but please can u tell which to install? Except CM and kernel I need something else to install?
     

    #32
  13. xreactx
    Froyo Feb 1, 2017


    #33
    horst58 likes this.
  14. xreactx
    Froyo Feb 2, 2017


    #34
    horst58 likes this.
  15. horst58
    Gingerbread Feb 2, 2017

    horst58 , Feb 2, 2017 :
    Is this the reason why the rom gets stuck at bootanimation?

    No succes here. adb doesn't give me any device.
    Is it possible to activate adb in stripped cm while building?
     
    Last edited: Feb 2, 2017

    #35
  16. xreactx
    Froyo Feb 2, 2017

    xreactx , Feb 2, 2017 :
    The stripped down version doesn't have any GUI, so it will look like it's stuck on the boot logo. I'm waiting on a response from KDE on the ADB issue. I tried doing the manual installation on a snapshot CM12.1 image and before issuing the "lxc-start" command I flashed the OTA file that compiled with my stripped version. After flashing I was able to ADB shell into my OPO, but LXC didn't start.
     

    #36
    horst58 and robthebold like this.
  17. horst58
    Gingerbread Feb 2, 2017

    horst58 , Feb 2, 2017 :
    I've tried several combinations of flashing (your image with your kernel, original snapshot and your kernel,...). When I was able to install manually via adb, I always get the same error. "lxc-start" couldn't be found.
     

    #37
  18. xreactx
    Froyo Feb 2, 2017

    xreactx , Feb 2, 2017 :
    I was able to get it to initially start with a PIE error. You may have to change the file permission to allow it to be executed.
     

    #38
    horst58 likes this.
  19. xreactx
    Froyo Feb 3, 2017

    xreactx , Feb 3, 2017 :
    I think I solved the PIE error. Now I'm running into linker errors.

    [email protected]:/ # lxc-start -n system -F
    WARNING: linker: lxc-start: unused DT entry: type 0x6ffffffe arg 0x87a8
    WARNING: linker: lxc-start: unused DT entry: type 0x6fffffff arg 0x1
    WARNING: linker: liblxc.so: unused DT entry: type 0x6ffffffe arg 0x7b70
    WARNING: linker: liblxc.so: unused DT entry: type 0x6fffffff arg 0x1
    WARNING: linker: libcap.so.2: unused DT entry: type 0x6ffffffe arg 0x7e0
    WARNING: linker: libcap.so.2: unused DT entry: type 0x6fffffff arg 0x1
    lxc-start: system: tools/lxc_start.c: main: 317 Executing '/sbin/init' with no configuration file may crash the host
     

    #39
    robthebold likes this.
  20. xreactx
    Froyo Feb 3, 2017