Jump to content

Ivaylo Hubanov

Members
  • Content Count

    35
  • Joined

  • Last visited

Posts posted by Ivaylo Hubanov

  1. On 10/9/2022 at 11:07 PM, eugenio said:

    Which image did you try? Official Waydroid images don't support Halium 11 devices yet, so you have to use a custom built one:

     

    https://github.com/UbuntuTouch-vayu/waydroid_11/releases/tag/1.0

     

    These are the instructions as provided by Verevka86, which compiled the images linked above:

     

     

    On the OG Pro1 instead, everything is available from the Droidian repositories:

     

    
    sudo apt install waydroid waydroid-vendor-28

     

    Man, you are awesome!!! It works!

    However I'm able to use it only in landscape mode... anyone have the same issue?

  2. 38 minutes ago, suicidal_orange said:

    No experience here but just read the instructions and as I read it you run an app not Waydroid itself.  Is this what you are doing?  I'm very confused by the really - either something happens or it doesn't.  (Apologies if this is because English isn't your first language)

    Another test, run "waydroid session stop" - if you don't get an error it was running. 

    $ waydroid status
    Session:	RUNNING
    Container:	RUNNING
    Vendor type:	HALIUM_11
    Session user:	droidian(32011)
    Wayland display:	wayland-0
    
    $ waydroid show-full-ui
    [12:36:04] Failed to get service waydroidplatform, trying again...
    [12:36:05] Failed to get service waydroidplatform, trying again...
    [12:36:06] Failed to get service waydroidplatform, trying again...
    [12:36:07] Failed to get service waydroidplatform, trying again...
    [12:36:08] Failed to get service waydroidplatform, trying again...
    [12:36:09] Failed to get service waydroidplatform, trying again...
    ... forever

    Tried waiting more than 10 minutes as suggested in some posts that it might take up to minute or two...

  3. On 8/18/2022 at 5:29 PM, matf-kabouik said:

    I have Droidian on a Pro1 since last year, and on a Pro1x since last night. Droidian hasn't been a daily driver for me (mostly due to battery life and the fact that I'm not friend with the ergonomics of Phosh) so I don't know everything about it, but feel free to ask questions.

    I have played with it somewhat actively last year to get alternate WMs working (Sway doable with some work, and with issues, i3wm doable too with a X hack), LXC (doable with Sway as WM but the keyboard mapping caused issues for my keybindings), Waydroid (Droidian may have the best support for it), or simply installing native Debian programs. Not much "real use" experience with Phosh, however.

    So far, the experience looks fairly similar on Pro1x, I'd rate the two ports as almost equivalent (with more things being experimental on Halium 11, though), but I haven't spent much time on it yet.

    Hey man,

    Can you help me out with running Waydroid on my Pro1X with Droidian?

    Simple apt install waydroid works and I can see Waydroid's icon, but when I tap on it, nothing really happens. Any advise will be much appreciated!

    Thanks.

  4. 11 hours ago, Hook said:

    This was happening to me on the PinePhone with Phosh.  I found instructions for editing the Phoc.ini file to change the default number.  I would imagine there is probably some similar ini file for Droidian, but don't know.

    Can find instructions you used for PinePhone? Might be usefull to find the file.

  5. Hey guys,

    droidian is awesome! I even  managed to disable haptic feedback, as i'm using the phone overnight while the baby is sleeping and the noise from vibration is waking him up. However, I'm still having issues making droidian to remember my Displays>Scale factor. Every time when I reboot, it gets reset back to 300% which is kind of too big for me. Any ideas why this change is not permanent will be much appreciated!

  6. My physical keyboard backlight does not light on automatically when I open the keyboard... I've found how to manually switch it on/off by echoing 1/0 in /sys/class/leds/:kbd_backlight/brightness

    But now I need to find out how to detect when the keyboard is open or closed...

  7. Hey guys,

    I'm experiencing some issues with connectivity at all...

    WiFi gets 2-5% packet loss and avg 35-40ms latency when pinging my home gateway... Compared to my old Android device where I get 0% loss and 20-25ms avg latency by holding both next to each other for the test...

    Also switching from WiFi to LTE sometimes require turning off mobile data and then back on... To restore connectivity... Strange is that when I switch to LTE and browsers show no connection... I can ping google.com from termux... (Which indicates name resolution and connection are fine) maybe network translation is the issue here and not doing it's switch properly?

    Also using my mobile as phone for conversations gives me awful experience... One one of the SIM cards stops working after 15-30 minutes and doesn't seem to have connection even though the range indicator is present and with good range...

    What also catch my attention is when I'm out without WiFi connection... Both range indicators show full range but there is small x in the bottom right of each... Even though the LTE indication is present and there is data connection...

    Any advices are much appreciated...

    Already tried few times the "network reset" option in Android on both SIM cards...

     

  8. Would be nice to disable fingerprint reader while it is not required for unlock or authenticate...

    I'm having trouble when holding the phone with right hand and typing on the keyboard... My palm seems to trigger fingerprint reads all the time which causes flickering and strange behavior.

    I know it's the perfect place for landscape mode, but come on... It's a mobile after all... I would really like to not use the physical keyboard, just to say hi to someone or type short answers like Yes, No...

    Also I don't see any good reason for keeping active this sensor all the time while it's not even required.

    • Like 1
  9. 7 hours ago, steeb said:

    I wrote a quick and dirty guide on re-flashing the stock ROM for macOS and Linux. It got a little buried in another thread so I thought I'd post it here for posterity.

    flashing_pro1-x.pdf 58.51 kB · 3 downloads

    Nice work just one clarification you might want to update the guide...

    To me this command doesn't execute:

    edl --loader=prog_firehose_ddr.elf reset reboot

    So I use "edl --loader=prog_firehose_ddr.elf reset" instead... I think the reboot at the end is not necessary and I'm not  sure if it properly executes on any device at all 🤔

    • Like 1
  10. Hello,

    I'm facing an issue after restore my device from Ubuntu Touch. It seems my partition table is not properly restored and my stock android now shows 8gig storage...

    Used this guide to flash Ubuntu Touch:

     

    Then this guide to revert back to stock:

     

    Anyone knows how to restore partition sizes properly?

     

     

  11. 3 hours ago, mosen said:

    @Ivaylo Hubanov That is an indicator for the sideload mode not being started in recovery.
    There should be an option in the recovery menu that says along the lines "sideload using/via adb".
    If you select that, the screen will change to black and only show some white text saying something like push .zip now and showing the command how to do so. (the adb sideload image.file one)
    When you start sideloading from your computer using this command, it will show progress on the device screen.

    @mosenok, so while stuck in the boot logo I was trying to restart the phone, but dropped the button before it actually restart and it seems something triggered in the background and phone booted android properly!!! 🎆🎉🙈

    So now I'm on the backup step then going back to try and flash Ubuntu Touch 🥵

    • Like 2
    • Haha 1
  12. 8 hours ago, mosen said:

    @Ivaylo HubanovAnother idea. Since your device boots into the F(x) logo and gets stuck there, it is in a state already where OTA changes can influence the boot process.
    Can you try sideloading an OTA update via adb in the recovery mode?
    Download a beta OTA from here (not GMS certified) Please note the beta disclaimer.
    Set device into recovery mode by holding vol down button on reboot.
    At the dead droid, push pwr btn and vol buttons to activate the menu.
    Choose sideload via adb.
    Push the downloaded .zip file using:

    
    adb sideload merged-qssi_bengal-ota.zip

    And reboot.

    This is what I get:

    ```

    # adb sideload merged-qssi_bengal-ota.zip

    adb: sideload connection failed: device unauthorized

    This adb server's $ADB_VENDOR_KEYS is not se

    Try 'adb kill-server' if that seems wrong

    Otherwise check for a confirmation dialog on your device

    adb: trying pre-KitKat sideload method..

    adb: pre-KitKat sideload connection failed: device unauthorized

    This adb server's $ADB_VENDOR_KEYS is not se

    Try 'adb kill-server' if that seems wrong

    Otherwise check for a confirmation dialog on your device.

  13. @mosenwell all seems fine then with me... Only last step fail so I remove reboot at the end of command...

    However I already did flash my device more than 10 times now and result is still the same... Stuck on the F(x)tec logo...

    Really open for more brave ideas... I only got my device yesterday... Waiting for it more than a year, just checked it was working fine with android then tried flashing Ubuntu Touch via UBports which failed and I'm stuck now... 🙈

    If I can make it work with Ubuntu Touch that will be just fine... Was trying to restore stock firmware after I read about that it is a good idea to do some backup first... Is it really so important to make this backup or maybe I can try flash Ubuntu Touch directly somehow... 🤔

    I don't need android... Ordered this phone because I read it will be Ubuntu Touch compatible 😄

    • Like 2
×
×
  • Create New...

Important Information

Terms