u/WhatsUpLabradog

I couldn't find a proper subreddit for such a question, so I'm asking here even though it's specifically a GI medical question rather than a braces one.

I had a spring around the premolars to maintain spacing between two teeth. It was fitted right at the end of the wire and it started popping off the past week as the teeth moved. I got it back into place on my own a couple of times and would usually take note not to chew over there, but I forgot about it while eating sushi earlier and noticed it popped out again. When I went to put it back in place I couldn't find the spring.

Because it was quite at the back of my mouth I'm not sure it could jump out of my mouth without me noticing, and thus although it doesn't seem that likely either I might have swallowed it without noticing because it got covered with sticky rice.

Should I, eh... monitor its hopeful exit the next few days? Most online sources just say that if the piece didn't go to the lungs or become lodged inside the throat then it should be fine, but I feel like it would bother me if I'm not 100% certain it passed through (and if I didn't actually ingest it then I will be left wondering).

What do you think? Thanks.

I don't know whether his closing comment is a true representation of reality or not, but his open, unfaltering appreciation of the most deranged type of dictators is pretty messed up.

I have this problem with my Poco X8 Pro Max, although I saw people mention this issue with other phones too (including a Pixel, which I mostly verified). Maybe it's not on all phones, I don't know.

This seems like HDR playback is made to affect the overall color space calculation in a very dumb way. I can watch something on YouTube or Netflix that is SDR-encoded and any UI element (including subtitles, ffs!) that is colored 255, 255, 255 in 8-bit RGB would correctly display as white as possible (for the current display brightness), but as soon as HDR content is loaded all of the white UI is transcoded as equal to maybe 127, 127, 127.

Even on full display brightness (which I don't use) it would often look gray, but either way the main issus is that it becomes illegible against pretty much any background other than black. If the background is half-bright then the UI would just invisibly blend-in, and if the background is very bright then the UI wouldn't be dark enough to discern (especially when UI elements sometimes have a soft shadow added to them, so you end up having a half-dark text surrounded by a black smudge surrounded by a white background).

Can I somehow force UI elements to render as bright as the HDR content? It seems like on different phones it might not behave exactly the same, because when I tested Netflix on a Pixel the subtitles were way too dark at app brightness <50% but became white at >50%, while on my Poco it remains gray throughout.

Thanks.

I tried making croissants a couple of days ago, but I used a "folding trick" to reduce the number of steps required. It still isn't very quick, but depending on the time given for proofing(s) and chilling a 53 layer croissant could be made in a long afternoon.

In this case I let the laminated dough rest overnight in fridge before rolling it out, shaping into croissants and proofing for another 2 hours, applying egg wash and baking for about 20 minutes at 190 °C.

The result wasn't bad, although the inner rolls didn't puff that much. It could be something with my rolling technique, because I mixed 50% whole wheat flour, or simply because it's quite hot here even with the AC running.

Anyway, I found it a bit too buttery for my taste, even though I looked at several recipes and I went with the lower end of what I read (but my specific recipe includes adjustments I made). These are the ingredients:

Per 100 grams of flour:
1 g dry yeast, bloomed in 10 g water with 1 g sugar
10 g sugar
2 g salt
25 g milk
25 g water
10 g butter

+ Lamination:
50 g butter mixed with 5 g flour

So the overall butter/dough ratio (including that mixed into the dough, and calculated against the full weight of the dough including the butter itself) is ~25%. Could that possibly be too much? Can I lower it?

And regarding the hydration, I'm not sure how to calculate it as there are different dry and wet components, so it might be between ~55% and 60% depending on how you look at it, which is apparently slightly high. Should I lower the water/milk?

Thanks.

What do you make of this? Another bout of Trump trying to preemptively soften the public's opinion about an up-and-coming new "war-winning deal"? Or rather that the bombings are expected to intensify?

Edit: another link to the clip if it doesn't play without an X account: https://xcancel.com/clashreport/status/2080019098742739271

I decided to get MCT oil after reading here how it helped some with dandruff/seborrheic dermatitis on the scalp.

I considered buying off of iHerb at first, but I found on some local health store organic 98% C8 oil for about the same price, and in a glass bottle. It says it's manufactured in Sri Lanka and the importer is some very local brand, so you can't find online reviews for it, but the bottle features several certifications which I hope have actually been verified.

Anyway, these are my questions:

1. It has a very faint coconut scent. Some sources say C8 oil should have no odor at all, although maybe it's faint enough that some would call it odorless (and otherwise it might be due to other coconut compounds found in the remnant 2%). But I also noticed that it does gain a bit of a different odor after being applied to the scalp/hair/skin, slightly "musty" for lack of a better descriptor. Does that sound normal for C8 oil?
2. Some sources say MCT (and C8 specifically) is "absorbed very quickly". The one I have does get absorbed eventually, but it seems to take a couple of hours. I applied a few milliliters across both the scalp and the face. Again, does that sound normal for C8? Perhaps the "very quick absorption" is overstated?

Thanks!

I decided to buy MCT after reading about its supposed effectiveness against seborrheic dermatitis/dandruff for people who weren't really responding to standard anti-fungal shampooing.

I looked on iHerb at first but then found a local health store that sells organic 98% caprylic acid MCT. It was just a bit cheaper compared to iHerb, so still rather expensive (≈ $30 for 500 ml). It says it is manufactured in Sri Lanka and there are a few local/international certification stickers on the bottle (which is mostly made of glass, another plus).

So I bought it for topical use, but I did taste a little bit and it does slightly taste of coconut, while a few online sources claim that "high quality C8/C10 MCT should be flavorless". It does not taste "goaty", though, which is another point they make about low quality MCT. It also slightly smells of coconut, but to an even lesser degree compared to the mild flavor.

So does it sound fine for real C8 MCT? Thank you in advance.

These observations come from UC Davis physiologist Dr. Keith Baar, who was recently interviewed by Jeremy Ethier (can't link because it auto-removes the post). The video recommends to either supplement your regular workout days with several sets of ~30 second holds or dedicate a specific day for such isometrics.

Is there any research about the possible benefits of doing very slow and controlled negative sets (e.g. 30 to 60 second pull-up descent)? I couldn't find anything other than videos about ending reps with at most 6 second eccentrics being either good for gains or an overkill.

Thanks.

New X8PM. How can I fix this? I know the description for Active nominally states "time on battery since it was last charged past 90%", but the system seemed to take into account that setting the charging mode to Battery Protection stops the charging at 80%.

But now it won't reset for the third 80% charge cycle in a row. I tried to clear the cache for the battery app, reboot the phone. Doesn't help.

Any solution? Thanks.

EDIT: Could it be that it requires to first have the phone discharge to at least 20% (or 19%)? Because I might have charged it from a bit higher on the recent charge cycles.

How can I fix this? I know the description for Active nominally states "time on battery since it was last charged past 90%", but the system seemed to take into account that setting the charging mode to Battery Protection stops the charging at 80%.

But now it won't reset for the third 80% charge cycle in a row. I tried to clear the cache for the battery app, reboot the phone. Doesn't help.

Any solution? Thanks.

I find the volume on this phone's speakers so high that I don't need it to ever get close to 100% even, and because of that it is sometimes a bit difficult to adjust to the best level when fiddling the slider at the lower end of its range.

So if the entire range of the slider would be limited to 100% it should decrease the difference between each step (slightly, at least, as 200% and 400% are just the last two steps).

Is that possible somewhere in the settings? Thanks.

I know you can manually adjust the slider while auto brightness is enabled, but it forgets your adjustment each time auto brightness is disabled.

I basically always prefer a lower screen brightness than the default auto value, both indoors and outdoors.

At nighttime indoors I usually prefer the lowest brightness (or close to it) so it doesn't become bothersome, and outdoors I rarely need the absolute max (which auto often chooses) and constant high brightness is a major factor in OLED burn-in. It should also logically drain battery faster, although when I checked with Amper I barely saw a difference between mA draw during lowest and highest brightness (it sometimes even read lower during highest brightness, which doesn't make sense).

I found a way to enable the Extra Dim setting on my Poco X8PM. It enables applying a constant dimming effect at the intensity of your choice, separate to the position of the brightness slider, but that has two issues:

1. It seems to work by compressing the dynamic range of the digital RGB bits, so the more intense the dimming setting is the more it can crush hues.
2. I suppose (but I'm not certain) that in OLED displays it reduces screen usage/wear practically the same as lowering the actual brightness slider, considering each pixel is its own light source as dictated by both the global brightness and the RGB data. But for LCD displays (nowadays almost exclusive to tablets) it won't reduce the intensity of the backlights, meaning it won't reduce power draw and the blacks will be whitewashed even more compared to actual lower brightness (as LCD black pixels can't effectively block all light).

Bottom line: it is a very simple feature to add as an extension of the auto brightness. I would even make it so one can either apply a uniform adjustment across the entire auto brightness range, or adjust more/less at dark/bright environments (for example, "dim more than usual when dark, maintain default brightness in daylight").

I know you can manually adjust the slider while auto brightness is enabled, but it forgets your adjustment each time auto brightness is disabled.

I basically always prefer a lower screen brightness than the default auto value, both indoors and outdoors.

At nighttime indoors I usually prefer the lowest brightness (or close to it) so it doesn't become bothersome, and outdoors I rarely need the absolute max (which auto often chooses) and constant high brightness is a major factor in OLED burn-in. It should also logically drain battery faster, although when I checked with Amper I barely saw a difference between mA draw during lowest and highest brightness (it sometimes even read lower during highest brightness, which doesn't make sense).

I found a way to enable the Extra Dim setting on my Poco X8PM. It enables applying a constant dimming effect at the intensity of your choice, separate to the position of the brightness slider, but that has two issues:

1. It seems to work by compressing the dynamic range of the digital RGB bits, so the more intense the dimming setting is the more it can crush hues.
2. I suppose (but I'm not certain) that in OLED displays it reduces screen usage/wear practically the same as lowering the actual brightness slider, considering each pixel is its own light source as dictated by both the global brightness and the RGB data. But for LCD displays (nowadays almost exclusive to tablets) it won't reduce the intensity of the backlights, meaning it won't reduce power draw and the blacks will be whitewashed even more compared to actual lower brightness (as LCD black pixels can't effectively block all light).

Bottom line: it is a very simple feature to add as an extension of the auto brightness. I would even make it so one can either apply a uniform adjustment across the entire auto brightness range, or adjust more/less at dark/bright environments (for example, "dim more than usual when dark, maintain default brightness in daylight").

I wanted to check that and DevCheck has been recommended by many people, but on my phone it doesn't show any temperature readings beyond battery.

The app doesn't notify about any issue, but according to the developer if the CPU temp field is missing then the OS is simply blocking access to the sensor.

Is that the right explanation or is it possibly something else? Thanks.

I was testing the camera on my new Poco X8PM and this strange bug happened.

I was capturing photos using the 50MP + RAW mode in the default camera app, and two of the photos captured one after the other won't get removed from the gallery.

I think I did apply a delete command to these two at first, but something happened and unlike the other image files (which I successfully removed) these two stuck. They show as thumbnails in the gallery, and I can click on them to load the images in full screen, but they won't zoom-in, and trying to either delete, edit, share them or even just access their file details returns the "wait until all photos are processed" message.

The image files actually no longer appear in the DCIM/Camera folder. I accessed the Gallery storage through Android's Files app and thought I removed different iterations of these in "gallery_disk_cache", but they still appear in the gallery.

Anyone familiar with this bug? How can I fix it?

Thanks.

EDIT: Okay, I got it fixed but I think this method wasn't possible at first. I wanted to delete them from the Camera app's browser (because I figured maybe the stuck "processing" status stems from there), but if I'm not mistaken when I tried that earlier I could only view images older than the bugged ones (after the new images that weren't bugged had already been deleted through the Gallery app).

Things I tried but are possibly not related to the solution: I rebooted my phone before deleting files inside the cache folder – images still stuck in the Gallery app. I rebooted again afterwards and that didn't help too.

But now I captured a new image and was able to browse backwards from it in the camera browser to reach the bugged images. I deleted them from there and now they're finally gone from the gallery.

Anyone has an idea why would that happen? I have a couple of different Google accounts associated with the same phone number. One of them was opened when I registered to some service and preferred to use a different email address and name.

As things go, I needed to access that Gmail again but forgot the exact address. I eventually recalled it on my own (and also managed to reset the password once I had the correct address), but for some reason Google would not recover my address even though I gave it the correct details.

If I give it the exact full name used for that specific account, after verifying my number it returns that error message. Actually, it does the same even if I try recovering my other addresses (under my real name, with the same phone number).

It used to work fine, so what might have gone wrong now? Thanks.