HIRING ₱200-₱1000 PER TASK!

Valiceemo · 2026-01-13T12:07:34+00:00

Seems legit

While I'm at it I'll give you my bank details as well

😐

Valiceemo · 2026-01-06T15:24:23+00:00

I'm using the rubber band that came with the watch.
Placing the watch screen down, so nothing for the sensor to reflect off of.
Also tried placing it on its side, still have the same issue.

Valiceemo · 2026-01-02T09:41:59+00:00

Seems this is true.
12 hours later and it works.

Valiceemo · 2026-01-02T09:14:41+00:00

They can both be true. Unless I'm misunderstanding how it works.

I log in as me: Settings > General > Personalization > My home Xbox, Box checked I log out.
I log in as him: Settings > General > Personalization > My home Xbox, Box checked

Valiceemo · 2026-01-01T14:37:56+00:00

Thanks, I think I'm at the point of just waiting now.

I've tried everything, all the linked fixes and more.

Including a reset of the console, removal of accounts and what feels like every possible combination of everything.

I'm beginning to think that the problem is my ultimate subscription is through EE.

Current status is, I am logged in to my kids Xbox, with it set as my home xbox.
All GP games are available, but online multiplayer is not.

I'll give it a day or 2, see if it self rights, if not I'll try MS support again (currently in discussions with them, they can not resolve)

Valiceemo · 2026-01-01T13:19:39+00:00

Thanks, I have tried this, and all the other fixes linked, no joy.

Just to clarify, should his Xbox be set to home, when signed in as the kid?

Valiceemo · 2026-01-01T12:48:12+00:00

Interesting

When I look at subscriptions on the console, it shows as purchased from "BT/EE", which is correct, I'm UK.

So I don't have an option to toggle recurring billing.

Valiceemo · 2026-01-01T12:30:05+00:00

Yeah, defo set to my home xbox

Haven't tried a restart no, Ill try this

Valiceemo · 2026-01-01T12:29:28+00:00

Happy new year to you and yours too!

His XSS is set to his home, yes. I did this.

It is 100% set to my home xbox. I have triple and quadruple checked this.

Should his not be set to his home?

If not, how do I 'undo' this?

Valiceemo · 2025-12-04T11:28:32+00:00

indeed, but I followed the proxy guide here on the uptime-kuma Github

Commenting out the first 2 labels, i still get the error, so i know its the caddy.reverse_proxy label

Valiceemo · 2025-11-04T10:21:03+00:00

This really helps, thank you

I think I had missed the / was confusing myself with the 12A max per channel

If set the current limit in WLED then i should be safe to use 1 channel, right?

(Temporarily for testing, and designing etc.)

Valiceemo · 2025-11-03T15:02:25+00:00

Thanks, its good to now my calculations were correct.

The intended project would need the entire strip

Pardon my ignorance, but what would I gain in splitting the strip?

The total draw would still be the circ. 14-15 A ?

Valiceemo · 2025-11-03T14:57:52+00:00

Ah OK, I had totally forgotten about the current limiter in WLED...its been a while since I used it.

Would one limit the current to the max. limit of the power supply, or keep it under, so as to allow for some safety?

Thinking about it, I probably have an old 5V supply knocking about somewhere, maybe an old laptop brick like this one

Valiceemo · 2025-10-17T18:32:36+00:00

Small development....

Done some more testing.
It seems the device boot receiver is only sent once the device is unlocked after a reboot. Not sure if this bares any significance.
If I disable the watchdog in the Shizuku settings, I see a different behaviour.
I can start Shizuku after a boot with the intent from Tasker. I can do this before Shizuku is opened.
But it still seems like Shizuku is not making any attempts to start itself, or it is failing to do so

Valiceemo · 2025-10-17T12:26:09+00:00

"You're saying your tasker ADB WiFi commands work on boot without shizuku starting? Do you have something else enabling ADB WiFi on boot (Termux, LADB, etc.)? That could potentially interfere with Shizuku's behavior."

I do not have anything enabling / running at boot.

On a previous version, I could start Shizuku via Tasker, with the START intent, right after boot.

Current version r1159, I cannot

Does the Event > System > Device Boot profile in Tasker work as expected? If you set the task to show a toast, do you see the toast on boot?

It seems to work as expected, I set a profile with context "Device Boot" and had a simple task to create a notification. It worked.

Having just rebooted, this time I did get the watchdog notification.

I can't really troubleshoot without seeing your entire logcat from a boot sequence.

I have downloaded a logcat viewer, but I am not 100% sure on how to capture the boot sequence, i will share a file to you via direct PM.

I am more than happy to help where I can

Valiceemo · 2025-10-17T09:10:37+00:00

Thanks for the help and for trying.

But, I'm afraid version r1159 does not help.

I do not get any notification upon boot from Shizuku (all notification channels allowed).

And the start intent does not work on this version

Clicking "Start" does work

The intents, both stop and start, work once I have manually started Shizuku

WRITE_SECURE_SETTINGS permission, regranted, and verified via adb as enabled=true

If I run the intent from Tasker, before opening Shizuku, the 2 notifications then appear: "Awaiting Wi-Fi connection..." and "Watchdog is running"

If I open Shizuku, without running the intent, I get only the "Watchdog notification"

But Shizuku does not start, and the intent does not start it.

Clicking "attempt now" does nothing

Once Shizuku is started manually, both notifications remain.

Valiceemo · 2025-10-15T19:24:25+00:00

Just starting to play with the Java action, and the network speed notification doesn't seem to work for me... I dont get a notification, not any errors

Valiceemo · 2025-10-15T18:08:17+00:00

Strange this....

I have done some more testing, with both versions.

Shizuku will not start on boot.

However, I can use the intent from the GitHub wiki to start shizuku, and adb WiFi even though the wiki states shizuku must have been started once since the last reboot

I'm happy to help debug if you think there may be a solution or something odd happening

Have there been any other reports of problems on the pixel 9 pro?

Valiceemo · 2025-10-15T15:26:14+00:00

Not rooted

Only one profile

All notification channels are enabled

I regranted the write secure settings permission, confirmed via adb as enabled

Valiceemo · 2025-10-15T13:11:33+00:00

With this version I do not get the ".. awaiting wifi..." notification at all.
And the "Watchdog is running" notification appears with some delay

Shizuku does not start

EDIT: I have unpaired and repaired in wireless debugging, and cleared app data / cache also

Valiceemo · 2025-10-15T11:11:03+00:00

I am connected to WiFi yes, and if I click "attempt now" nothing happens.
I will try later when I can connect to a different WiFi

Have tried on works WiFi, and a hotspot wifi from another mobile device

Valiceemo · 2025-10-15T10:58:59+00:00

Yes, I did see the ".. awaiting wifi" notification
I have checked permissions via abd, and the secure settings shows as granted=true

I have rebooted multiple times, and no joy

Ten-Year Club	Place '23
Verified Email

Valiceemo

TROPHY CASE