Jump to content

Milky_Pimms

Members
 View Profile  See their activity

  • Content Count

    32

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by Milky_Pimms

    UBports releases on GitLab for the Pro1x

    in General Discussion

    Posted · Edited by Milky_Pimms
    more info

    Job #747420433 devel-flashable

    Works; 3G LTE, WiFi, Video captcha for camera, VM's, SMS texts, Ubuntu touch System updates. Waydroid; worked first time use with wayland installer via app store (buggy) Able to install F-droid and Fennec fox and use's 🤩 .

    Broken; backlit keyboard, camera button on the phone, MMS text messages more than likely APN settings.

    Pro1x Pocket VMs app UBports

    in Support

    Posted

    Pocket VMs work on one the many new GitLab Release's. What I don't understand is the: (guest not initialized display yet) error message. 

    A arm ISO of Debian wiil boot to the installer but will not install. (Display not active)  error message.

    Bar that I can daily drive UBport thanks to the whole team.

    Please help.. (M_P)

    Pro1x with SailfishOS

    in General Discussion

    Posted · Edited by Milky_Pimms

    Android Support untested

    Set password for dev mode needed for sudo

    Turn on 3-party installs

    once installed https://repo.sailfishos.org/obs/sailfishos:/chum//4.4.0.72_aarch64//aarch64/sailfishos-chum-gui-0.5.0-1.6.1.jolla.aarch64.rpm

    Open CHUM install Waydroid

    Open Terminal use devel-su for root

    run waydroid init

    https://together.jolla.com/question/184233/solved-auth-failed-for-root-user-or-devel-su-in-terminal-app/

    https://forum.sailfishos.org/t/announcing-sailfishos-chum-gui-0-3/9839

    https://chumrpm.netlify.app/

    (M_P)

    • Thanks 1

    [Guide] Fixing issues with Ubuntu Touch

    in How Tos

    Posted

    @Zahkc I would like to-do the keyboard fix. I've move the file's to .local/share and ran script 

    [email protected]:~/.local/share$ InstallSliderDaemon.sh
    -bash: InstallSliderDaemon.sh: command not found
    [email protected]:~/.local/share$ ./InstallSliderDaemon.sh
    -bash: ./InstallSliderDaemon.sh: Permission denied
    phab[email protected]:~/.local/share$ sudo ./InstallSliderDaemon.sh
    sudo: ./InstallSliderDaemon.sh: command not found

    Sorry I'm a noob.. Do I need to install python and how..

    I've tried apt and apt-get 🥴

    Thanks for your time

    (M_P)

    Pro1-X with Ubuntu Touch

    in Pro1 - Thoughts & questions

    Posted · Edited by Milky_Pimms
    update moblie data working

    DO NOT USE #2985035568 devel-flashable-focal

    Re-flashed and works well so far used #2985035565 devel-flashable

    https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/jobs

    1. Reboot to bootloader, format userdata (if switching from Android) and flash recovery.img from the build artifacts, then reboot to fastbootd mode: 
    sudo fastboot format:ext4 userdata
sudo fastboot --set-active=a
sudo fastboot flash recovery out/recovery.img
sudo fastboot reboot fastboot
    1. Flash system.img and boot.img, then reboot: 
    sudo fastboot flash system_a out/system.img
sudo fastboot flash boot_a out/boot.img
sudo fastboot flash dtbo_a out/dtbo.img
sudo fastboot reboot

    Terminal, WiFi, location, bluetooth, app store, are there

    No moblie data out of the box (should be a easy fix) will update

    (Update) just change APN settings to suit carrier and good to go.

    • Thanks 2

    Pro1-X with Ubuntu Touch

    in Pro1 - Thoughts & questions

    Posted · Edited by Milky_Pimms
    I'm a noob

    Thanks @zstas

     #2985035568 devel-flashable-focal  Helium 11 20220806 UBports Recovery failed the format data/factory reset. How did you flash regular the build is based on 16.04 IIRC once ubuntu 20.04  was all ready installed?

    WiFi is broken, no back light for keyboard, no mobile data, no terminal, no UBport app shop. I see there a some fixes but no terminal to use and no mobile/data or WiFi to download.. SSH or adb to fix ahhhh... I'm not that smart. I will try maybe. 🤕 

    (M_P)

    Known hardware that works for flashing

    in Support

    Posted

    11 hours ago, VaZso said:

    Under Linux, basically lsusb helps.
    You may find your root HUBs sitting on a "BUS" (lsusb | grep root), then you may find devices connected to a specific bus.
    Try to connect the phone to a bus which does not have other devices connected or to a bus which has the least devices connected.
    It will help.

    Good advice @VaZso I still think hardware weirdness going on as well. 

    @fedora ~]$ lsusb
    Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 005 Device 003: ID 1b1c:1b3d Corsair Corsair Corsair Gaming K55 RGB Keyboard
    Bus 005 Device 002: ID 1b1c:1b3c Corsair Corsair Gaming HARPOON RGB Mouse
    Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 003: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
    Bus 003 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 002: ID 047f:c05e Plantronics, Inc. RIG WD1
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     

    The only USB Bus which is not shared is (Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub and Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub )  As well lsusb is not telling the truth. The ports are USB 3.2 Gen 2, AMD's broken thunderbolt. 

    On top KVM was passing-on qualcomm-device when in firehose boot mode and I had not add the hardware. 

    Any-who a list keeps it easy (a no brainer) to help noobs like me.

    (M_P)

    Pro1-X with Ubuntu Touch

    in Pro1 - Thoughts & questions

    Posted · Edited by Milky_Pimms
    spelling

    Hi all, Can someone please explain the differences between devel-flashable-focal and    
    devel-flashable

    I flashed devel-flashable-focal no UBports app repo store and terminal 🤔

    I followed the steps on GitLab page. On Fedora used sudo for fastboot commands, USB 2 port on a ROG micro ATX (B550-i) the BIOS USB flash back port.  

    Using Fedora on a x570 no USB ports would work, no USB 2 ports only headers on board (it would connect and give the sense it should). Firehose for flash back was the same.

    Thanks for all for the help

    (M_P)

     

    Pro1-X with Ubuntu Touch

    in Pro1 - Thoughts & questions

    Posted

    @esialb

    On 7/31/2022 at 12:06 PM, esialb said: 
    
unzip artifacts.zip
cd out
fastboot flash boot_a boot.img
fastboot set_active a
fastboot flash userdata userdata.img
fastboot set_active a
fastboot continue

    In the current GitLab release there is no userdata.img only: boot.img, dtbo.img, recovery.img, systerm.img

    Could you please have a second look.

    I can't install UBports at this stage.

    (M_P)

    Pro1-X with Ubuntu Touch

    in Pro1 - Thoughts & questions

    Posted

    Can some let me know please if i need to enter recovery mode to format userdata than follow steps?

    1. Reboot to bootloader, format userdata (if switching from Android) and flash recovery.img from the build artifacts, then reboot to fastbootd mode: 
    fastboot format:ext4 userdata
fastboot --set-active=a
fastboot flash recovery out/recovery.img
fastboot reboot fastboot
    1. Flash system.img and boot.img, then reboot: 
    fastboot flash system_a out/system.img
fastboot flash boot_a out/boot.img
fastboot flash dtbo_a out/dtbo.img
fastboot reboot

     

    fastboot format:ext4 userdata not working for me.

    fastboot format:ext4 userdata
    Warning: userdata type is f2fs, but ext4 was requested for formatting.
    /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
    fastboot: error: Cannot generate image for userdata

    Thanks (M_P)

    Pro1X won't boot after flashing Pro1 image

    in Support

    Posted · Edited by Milky_Pimms
    more info

    Got there in the end.. I put the comms problem down as Windows version and or CPU architect using USB 3.0 port. Bear-metal with up to update win10 and Intel HQ7700 got me over the line. My ferdora rig is packing a Ryzen 7 3000.   

    Let's see how I got with UBports..

    Thank all for all your input

    (M_P)

    • Like 1
    • Thanks 1
×
×
  • Create New...

Important Information

Terms

  I accept