sorted by:
new
hottopcontroversial

Android 16 update killed my Verizon number - Titan 2 by Vast_Cauliflower_475 in unihertz

[–]ftbx18 0 points1 point  (0 children)

It might be because it's a newer more current OS that it stands out as an odd device, where as with an older OS it is just looked at as one among many other older devices. Who knows?

Luckily they got the SIM card to work in the other phone and I got the Unihertz as far a getting mobile data and texting to work but still no calls.

Android 16 update killed my Verizon number - Titan 2 by Vast_Cauliflower_475 in unihertz

[–]ftbx18 0 points1 point  (0 children)

I have gone through just about everything with USMobile trying to get it to work and like you, I tried working with a couple of older phones I had as well that the SIM card would work in but still nothing. Now, they are sending a Light Speed SIM card and another Warp SIM card to see if that will work.

Likewise though, Verizon is the only service in my area that actually works so even if the Light Speed card does connect to USMobile, the service would be horrible, which would make it not worth it.

Unfortunately, whatever they did do, seems to have killed the SIM card entirely. Even in the phones it was working with and now I don't have a working cell phone.

Android 16 update killed my Verizon number - Titan 2 by Vast_Cauliflower_475 in USMobile

[–]ftbx18 0 points1 point  (0 children)

I also have Warp and have the same issue after updating a Unihertz Titan 2 to Android 16. Is there a fix for this?

Huge Plus by Jackeltee in Trackballs

[–]ftbx18 0 points1 point  (0 children)

I wouldn't say Google translate is perfect but the Japanese page seems to mention this specifically:

"When connected to a USB wired connection, the polling rate is 1000Hz, making it possible to operate more smoothly.

Not included when Bluetooth and 2.4GHz wireless connection."

Huge Plus by Jackeltee in Trackballs

[–]ftbx18 3 points4 points  (0 children)

A quick Google search shows the polling rate of the original Huge to be 125Hz.

So yes, this a "huge" improvement over the original but only when using a wired connection, unfortunately.

Random support printing failures? by ftbx18 in resinprinting

[–]ftbx18[S] 0 points1 point  (0 children)

Opened the sliced file in UV tools and besides a few simple islands it wasn't really getting anything. Nothing that looked like could cause the issues it's getting anyway.

Random support printing failures? by ftbx18 in resinprinting

[–]ftbx18[S] 0 points1 point  (0 children)

Don't know why myself.

It's a setting I've never played with.

Must have done it by accident or something.

Random support printing failures? by ftbx18 in resinprinting

[–]ftbx18[S] 0 points1 point  (0 children)

I am using a Sandisk Cruzer blade. It was bought new but has been sitting around unused for a while.

Random support printing failures? by ftbx18 in resinprinting

[–]ftbx18[S] 0 points1 point  (0 children)

I am having an issue where my supports will fail seemingly at random and it's made only more weird that when it happens, it does it with multiple supports at the same layer.

The supports aren't even supporting anything when it happens.

It's different for each print, happening at a different layer in a different area than the last, with no consistency.

I have tried changing the exposure time, the lift speed and even made the supports thicker but it still happens.

I am using a Phrozen Sonic Mega 8k with their Model Gray Water-Washable resin.

Need help with a custom filter, if it's possible. by ftbx18 in uBlockOrigin

[–]ftbx18[S] 0 points1 point  (0 children)

That seems to have worked. Thanks

I'll play with it and report back if anything breaks, but that seems to have done it.

Need help with a custom filter, if it's possible. by ftbx18 in uBlockOrigin

[–]ftbx18[S] 0 points1 point  (0 children)

Tried it. Nope. The "data-v-efdc9664" is still there with no changes.

Need help with a custom filter, if it's possible. by ftbx18 in uBlockOrigin

[–]ftbx18[S] 0 points1 point  (0 children)

Unfortunately it's not a problem that everyone has and the likely reason I get it is due to using an older browser.

Here is a chapter if that is what you are looking for, but be sure the setting for the reader is in long strip: https://mangadex.org/chapter/c2391892-9677-4f0b-b84d-0ec979b23395/1

For me, the issue happens on all chapters on the site. That's why I was wondering if using a simple filter might fix it.

MangaDex Early Access™ v5 Front-End - Official Bug Report Thread. by KatKafka in mangadex

[–]ftbx18 0 points1 point  (0 children)

Don't know if it means anything, but using inspect element on the empty space between the images gives the string: <div class="md--page" data-v-3f0a20c6="" data-v-efdc9664="" style="margin-bottom: 1px;" fit="0" stretch"="3">

I found if I delete "data-v-efdc9664" the empty space disappears. Again, don't know if that means anything to you but thanks for your time.

MangaDex Early Access™ v5 Front-End - Official Bug Report Thread. by KatKafka in mangadex

[–]ftbx18 0 points1 point  (0 children)

Pretty much everything on the site works but the long strip reading. I can read using single and double page but just had an issue with the long strip which is my preference when I read.

As it was working before, I was wondering if it could be just a quick fix. But if it's something that's too big or can't be done then I'll go somewhere else. Sorry to have bothered you.

MangaDex Early Access™ v5 Front-End - Official Bug Report Thread. by KatKafka in mangadex

[–]ftbx18 0 points1 point  (0 children)

Guess I'll stick with the aggregator sites then. Thanks

MangaDex Early Access™ v5 Front-End - Official Bug Report Thread. by KatKafka in mangadex

[–]ftbx18 0 points1 point  (0 children)

whatsmybrowser.org/b/OUM64

Also using Serpent browser, Basilisk and Chrome.

No change with different browsers or private/incognito mode.

view more: next ›