@Flohack On OPO6, under the new version 440, I find the following. The date still reverts to June 1970 i.e. the choice of using the auntomatic from the Router does not work. Also, pressing the restart button just closes down the phone and it never restarts.

@Marc_Flender Yes, the camera is not working yet. @TheVancedGamer was working on it when he had time.

@arubislander said in 6P not installable anymore?: @Inali said in 6P not installable anymore?: -Install TWRP recovery -Boot TWRP and delete ALL partitions Is this a required step based on the instructions? If so, what instructions are you following? As far as I know the UBports installer does not create partitions, it expects them to be laid out in the correct way as in the stock install. I found it on other posts regarding the installer not working correctly. I also tried this without wiping partitions and the result is always the same. It runs the script, boots to UT recovery, and does nothing forever. Cannot figure out why. Seems to be a common issue as there are tons of threads about the exact same issue on the same phone.

Please see https://forums.ubports.com/topic/8858/ota-25-hotfix/10 A new RC has roll out that should fix the boot issue. Also for device that have fingerprint, please check if no regression.

FYI I made this PR https://github.com/Aarontheissueguy/WaydroidHelper/pull/24 to mitigate issues with outdated Wydroid packages in the future. My Pixel 2 issue was simply that I installed Waydroid during a timeframe where it was kinda broken, but to fix it a manual intervention was necessary. I hope when this PR is merged we will simply tell users to uninstall/reinstall Waydroid and all is fine. And there might be more users out there that have a broken install right now

Please remember this thread is about testing the release candidate channel for what will become OTA-24. All other results on any other channel are off topic here, but feel free to start another thread to discuss those if needed. And also please keep the discussion in this thread to differences / regressions as compared to OTA-23. Any bugs already present in OTA-23 and still present in OTA-24 but not on the OTA-24 tracker, are likewise off topic.

@domubpkm Hello, this RC is the final candidate for OTA-24

@demone said in Double-Tap 2 Wake: On OP3 touch buttons are used to aces drawer on Lomiri. Like the one on my MX4, usefull, i use it often

@flohack I rebooted the phone and the bluetooth didn't work. I rebooted again and the bluetooth was working again. It is a little flunky if it woks or not. I have a bluetooth keyboard it was a long time since it worked with my phone. I tried to connect to the keyboard just now and the phone hard crashed, it rebooted, no changes there :smiling_face:

@flohack said in Installer config for FP4 in final tests: Aaand it has landed! Happy Installation! Next step, the support of Waydroid

@TheVancedGamer Sorry. I somehow mamaged to downvote your post. Fat fingers on a small screen. I have upvoted to remove the downvote

Hey! Tested AetherCast today with Microsoft Wireless Display Adapter (first version) and it actually works very well, no matter what apps were used. Truly a long -awaited feature

@hackersarchangel Apologies for the very late reply, but were you using the Microsoft 4k adapter? I've yet to get my Pixel 2 to connect. It drops after a few minutes without ever getting video up.

@fungie No I mean there are workaround, but MTP MUST work in both ways so we have a bug here... Thanks everyone for testing!

@naizena Check this thread out - link.

@rocket2nfinity awts too bad i'm in philippines,

To some extent it depends on the actual goal. Is this intended as a test harness for an app in a controlled environment? Or as a means of automation on a desktop? Faking udev ought to work across different compositors. The virtual keyboard extensions might work for some compositors but different compositors support different protocol extensions. (E.g. Mir supports virtual_keyboard_unstable_v1 but not org_kde_kwin_fake_input.) If this is just for an application test harness, then it should be possible to test against a specific, even a bespoke, compositor. This could be complicated for most people I know as they have employers, and work (especially paid) outside that raises contract concerns. Maybe ask on the wayland-devel mailing list?

@acidlake I know its either network or wifi. I tried to commit a change for less wakeup in WiFi, could you try devel channel to see if that makes a difference? Thanks!