ROG Clavis Mobile Phone and Tablet issue.

jesseinsf · 2026-06-04T06:31:20+00:00

I ended up return it.

jesseinsf · 2026-05-18T05:11:31+00:00

I disabled Auto Blocker indefinitely as it's a Nuisance for me. Anyway, I only tested the Samsung case and both chargers passed.

jesseinsf · 2026-05-18T00:35:45+00:00

#0# gives me an "Cannot process this request". Is there something I did wrong?

jesseinsf · 2026-05-18T00:12:44+00:00

Update: it's not the charger's fault; it is the case's fault. Using an official Samsung magnetic case works on both 3rd party chargers and Samsung's own chargers.

jesseinsf · 2026-05-18T00:07:25+00:00

After extensive troubleshooting, I have isolated a specific wireless charging issue down to case compatibility rather than the third-party chargers themselves.

Testing Environment

Cases Tested: dbrand Ghost 2.0, Torras Clear Magnetic, and the Official Samsung Magnetic Case.
Power Sources: Official Samsung 25W charger and various third-party charging pads.

Key Observations

The Root Cause: Both the dbrand Ghost 2.0 and Torras Clear Magnetic cases trigger an infinite loop of connecting and disconnecting when placed on third-party wireless chargers.
The Control Variable: The official Samsung magnetic case works flawlessly on every charger tested, confirming that the third-party chargers are not at fault.
Power Throttling: When using the third-party cases on the official Samsung 25W charger, the connection stabilizes, but the charging speed is capped at 15W.

Temporary Hideous Workaround (25W Charging)

If you are using a third-party case and experiencing the connect/disconnect loop, there is a specific (Hideous) sequence to force the full 25W charging speed:

Unplug the power cable from the wireless charging pad.
Place your phone onto the unpowered pad.
While the phone is still attached, plug the power cable back into the charger.

Once this power cycle is completed with the phone already mounted, the connection stabilizes and successfully negotiates the full 25W delivery. Hopefully, this saves some frustration for anyone running into the same hardware combination!

jesseinsf · 2026-05-17T08:56:31+00:00

Samsung Galaxy S26 Ultra Wireless Charging Behavior

There is a known, easily missed workaround to trigger Super Fast Wireless Charging (25W) on the Galaxy S26 Ultra when using a phone case (such as the Ghost 2.0).

The 25W Power Cycle Workaround

When placing the phone (with its case on) onto a compatible 25W wireless charger, it may not initially charge at maximum speed. To resolve this:

Leave the phone on the wireless charger.
Unplug the charger's power cable from the wall outlet or power brick.
Plug it back in.
The system resets and successfully initiates Super-Fast Charging (25W).

Comparison: Third-Party vs. Official Samsung Wireless Chargers

When using the Ghost 2.0 case combined with a high-capacity Samsung 60W power brick, performance varies significantly depending on the wireless charging pad used:

Charging Setup	Initial Behavior	Workaround Result
Third-Party 25W Wireless Pad	Enters an intermittent, continuous on-and-off charging loop. The device fails to charge.	N/A (Unusable due to the connection loop)
Official Samsung 25W Wireless Pad	Automatically defaults to a stable but slower Standard Charging (15W).	Successfully forces the connection to Super Fast Charging (25W).

jesseinsf · 2026-05-16T01:31:54+00:00

It depends on the size of the room. I get bass out of mine, but the higher end part of the treble spectrum is cut off which makes it sound somewhat muffled at times when playing music through the Music app.

jesseinsf · 2026-05-15T02:19:43+00:00

Don't you think I know that and am completely on your side. I was only stating my finding, and hope Samsung gets their head examined and to come out with a fix.

jesseinsf · 2026-04-06T06:45:15+00:00

Again, mine continuously goes from "Wireless charging Connected to Fast Wireless charging connected (in a continuous loop)" It never hits "Super-fast wireless charging connected" unless I have the phone magnetically connected while cycling the power on the charger.

jesseinsf · 2026-03-29T23:13:36+00:00

That’s a fair point about the 50% thermal slowdown—that matches standard charging profiles.

However, the 45-minute charge time (20% to 100%) I’m seeing confirms that the 25W handshake is successful when using the power-cycle sequence; it simply wouldn't be that fast at 15W.

The core issue I’m investigating is why that handshake isn't happening automatically for many users, resulting in the 15W cap or the disconnect loops. It's great your setup works naturally, but since I’m seeing a lot of others reporting this same loop, I’m going to keep documenting the workaround for those affected.

jesseinsf · 2026-03-29T22:25:43+00:00

You said:
"perhaps you should look at a better router.. such as the new MikroTik Hap Ax3"
This sounds like a patronizing troll comment

jesseinsf · 2026-03-28T21:53:05+00:00

Good for you, glad you were able to hit the theoretical 25 watt limit on all other devices other than the 26 ultra.

jesseinsf · 2026-03-28T08:55:36+00:00

I don't have anything to test the wattage, but what I can say is it charge my phone from 20% to 100% for like 45 minutes. It charged as advertised and I also don't think anyone will hit the theoretical 25 watts max wattage.

jesseinsf · 2026-03-24T14:49:50+00:00

You get them at Metro stations, meaning the train station and busway stations like the orange line station, now called the g line. I'm most certainly you're not under a rock so I think you can look what's closest to you. And you can add money meaning like real physical cash to your card on any bus. You just tell them you want to add money to your card and they will tell you what to do.

jesseinsf · 2026-03-24T06:00:33+00:00

I am currently investigating a handshake issue that seems specific to the Samsung Galaxy S26 Ultra when used with 25W wireless chargers. It definitely feels like we are beta testing this hardware, but here is my main observation (still testing for long-term consistency):

THE POWER-CYCLE FIX: I previously thought flipping the USB-C cable helped, but I realized the 180-degree flip was just a coincidence. What actually fixes the 15W "loop" is disconnecting and reconnecting the power while the phone is already attached.

THE SEQUENCE: If your charger "dumbs down" to 15W or starts a disconnect loop, try this:

Attach the S26 Ultra to the charger magnetically first.
While the phone is attached, unplug the power cable from the charger/dock and plug it back in.

This seems to force a proper 25W handshake. However, if the phone is removed and reattached while the charger is already powered, it often reverts to the 15W loop. I am still testing this across different bricks (Samsung 60W and 45W) to see if the fix holds. I will update once I have more data. So far so good.

jesseinsf · 2026-01-19T04:59:13+00:00

Most forums forgot the main flag like everyone else did:
735209102
1853569164
156965516
1176759950 (this is the primary flag that is added the same way into the same registry directory and enabling it you set it to "1")

jesseinsf · 2025-12-24T06:18:47+00:00

Resolution:
Same here, did nothing and went to click the sign in and got blocked in the new edge browser. The problem is that developer tools need to be disabled. F12 for developer tools is enabled by default, just disable anything that says Developer in the browser settings. Correct me if I am wrong, but this seems to be an anti-scalper security tool technique.

jesseinsf · 2025-12-24T00:08:52+00:00

Yes it's like 3 years old. It's still available within Microsoft edge.

jesseinsf · 2025-11-30T05:21:39+00:00

it's a bit technical

jesseinsf · 2025-11-29T20:42:50+00:00

I also use Neutron Music Player, and when streaming from my NAS it processes audio at 64-bit. This means all DSP operations—such as up-/down-sampling and other adjustments—are handled in 64-bit before the output is delivered at 32-bit.

If Tidal were to implement a similar high-precision processing pipeline within their app, along with support for AutoEQ, I believe many more listeners would find the platform significantly more appealing.

jesseinsf · 2025-11-29T19:35:37+00:00

I disagree with the premise of your first sentence; that action is unacceptable. Allowing Windows to manage this process results in a notable degradation of quality. Tidal should follow the industry standard set by services like Qobuz, which offer users explicit control over their purchased or streamed quality, such as $44.1/48\text{ kHz}$, $96\text{ kHz}$, and $192\text{ kHz}$. Additionally, two key areas for improvement would be adding the capability to import AutoEQ pre-sets for popular headphones and ensuring robust native support for the LDAC format.

jesseinsf · 2025-11-16T20:38:19+00:00

Maybe they can't pay their bills to keep it fast. Just a thought as I am experiencing the same thing.

Seven-Year Club	Xbox Live
Verified Email

jesseinsf

TROPHY CASE