[device-port] [potter] Moto G5 Plus

[UniversalSuperBox]

Tree: halium-7.1

The tree can be synced by running ./halium/devices/setup potter.

• [x] Create manifest
• [x] Boot image and system image build successfully
• [x] Device boots into rootfs, usb: Manufacturer: GNU/Linux Device appears in dmesg on host.
• [x] LXC container starts and does not crash
• [ ] libhybris tests
  • [ ] test_gps
  • [ ] test_hwcomposer
  • [x] test_lights
  • [x] test_vibrator
  • [ ] test_wifi
  • [ ] test_sensors
  • [ ] test_audio
  • [ ] test_camera
  • [ ] test_input
  • [ ] test_nfc
• [ ] test_recorder

When building (after running ./halium/devices/setup potter), replace vendor/motorola/potter/potter-vendor.mk with the following file: potter-vendor.mk.txt. Note that I've removed the Bluetooth libraries for now since they're causing build headaches.

Depending on how setup decides to touch vendor/motorola/potter/potter/Android.mk, you may also need to replace it with the following file: Android.mk.txt

At the moment, many tests are broken on 7.1 CAF devices, which potter happens to be. I've been testing using the Ubuntu Touch rootfs and find that Wi-Fi, display, and input work well.

[reivilibre]

Hello there.

Please would you be able to point me to some information about what a

7.1 CAF device

is? I'm trying to port the Moto G5 (cedric), which I reckon is probably similar to potter given it's the non-plus version. I have the same set of working and non-working (typically segfaulting) tests as you in the Halium reference rootfs.

If you wouldn't mind also answering, do you know what about Ubuntu Touch makes it work compared to the Halium reference rootfs?

Many thanks.

[jbruechert]

It's probably a caf libhybris build in Ubuntu Touch (caf is android with Quallcom changes which makes it incompatible with other generic devices). You can also try caf libhybris in the reference rootfs, there is an additional repository available on repo.halium.org.

[raveesh-me]

I have never ported anything before, have a Moto G5 Plus, and will love to work on this provided some guidance.

The most I have done so far is recover a soft brick, unlock bootloader and install lots of custom ROMs for the past 7 years or so.

Let me know if I can take this ahead

[raveesh-me]

At the moment, many tests are broken on 7.1 CAF devices, which potter happens to be. I've been testing using the Ubuntu Touch rootfs and find that Wi-Fi, display, and input work well.

Has the situation changed?

[luka177]

hi how did you get ubuntu touch working? on cedric ending with: [ 3.155571,4] initrd: checking mount label mmcblk0p37 [ 3.156621,4] initrd: mounting /dev/mmcblk0p37 as /root/android//boot [ 3.159370,1] mount: mounting /dev/mmcblk0p37 on /root/android//boot failed: No such device [ 3.164387,4] initrd: checking mount label mmcblk0p38 [ 3.165441,4] initrd: mounting /dev/mmcblk0p38 as /root/android//recovery [ 3.168128,1] mount: mounting /dev/mmcblk0p38 on /root/android//recovery failed: No such device [ 3.173081,4] initrd: checking mount label misc [ 3.173788,4] initrd: mounting /dev/disk/by-partlabel/misc as /root/android//misc [ 3.176426,1] mount: mounting /dev/disk/by-partlabel/misc on /root/android//misc failed: No such device [ 3.183966,4] initrd: checking mount label mmc_host*

run-init: opening console: No such device [ 3.252073,7] Target filesystem doesn't have requested /sbin/init. [ 3.252783,0] run-init: opening console: No such device [ 3.253598,0] run-init: opening console: No such device [ 3.254383,0] run-init: opening console: No such device [ 3.255163,0] run-init: opening console: No such device [ 3.255966,0] run-init: opening console: No such device [ 3.257074,7] No init found. Try passing init= bootarg.

[UniversalSuperBox]

cedric is a different device than potter, but it appears that you have a fairly common problem. Try unsetting console= in your device cmdline. Please join us on any of the "Getting help" channels in the UBports documentation for more help: https://docs.ubports.com/en/latest/porting/introduction.html

[luka177]

thanks helped

[Darin755]

I am trying to build halium for potter. I downloaded the source and changed out the potter-vendor.mk and the android.mk files. The system.img built successfully but the hybris-boot.img did not. The error was potter does not have mountpoint fixup data. Does anyone know how to fix this?