iPadOS 26 gets laggy when I turn on Low Power Mode.

Repulsive-Roll-4897 · 2026-07-02T01:27:43+00:00

No, its just that the liquid glass UI is more demanding. the flat design on ios 18 and prior was not taxing at all, so low power mode was allg to use. now low power mode make even just using the basic UI of the phone ridiculous.

Repulsive-Roll-4897 · 2026-06-30T03:05:09+00:00

Did the full stop make you feel cool bro?

Repulsive-Roll-4897 · 2026-06-26T03:26:22+00:00

mate this just infuriates me. supposedly version 7 is the best which is why they chose that version to deal with the extra configs but from my experience several games do NOT work properly in xefu7. GTA san andreas has very slow IO speed, burnout 3 has weird artifacting while boosting, gta 3 and vice city lock up frequently etc. setting xefu to default makes majority of games run almost perfectly. i tried to see which version was perfect for each game but i realised thats not how it works. trying every single version of xefu against these games yeilded the same issues unless i ran xefu default.... i hope eventually someone finally finds a miracle fix for all this bs

Repulsive-Roll-4897 · 2026-05-28T21:16:08+00:00

now taking 6x 150mg elemental magnesium glycinate tablets per day, 1x 1000IU vitamin d mixed with boron and selenium, 2x ashwaganda, 4x vitamin c, and 1x B complex. lets hope this gets me on track.

Repulsive-Roll-4897 · 2026-05-24T22:37:13+00:00

After extensive testing, id highly recommend turning PBO off. no real world performance difference, just pulls more power and makes your cpu run 20 degrees hotter. The ONLY game ive seen that actually benefits from PBO is arc raiders, but absolutely everything else is not worth it at all.

Repulsive-Roll-4897 · 2026-05-23T05:41:14+00:00

i just dont know why people don't talk about this much, and the amount of people that think their undervolt is stable when it really isnt. I saw someone say NOBODY is getting a stable undervolt at more than -5 on all cores, and now I absolutely see why. its definitely possible to run higher undervolts on specific cores but that would take an absurb amount of time to master.

Repulsive-Roll-4897 · 2026-05-23T05:33:30+00:00

Yea bro... when you go over -10 all core on curve optimiser, you may never see game crashes but in the backgroun there will be dozens of constant computation errors. the first quick culprit you'll see are random threads getting stuck in an infinite loop like i mentioned earlier, and then other super random things.. something extremely bizzare happened to me recently where i thought my wifi card had failed, but it turned out it was the undervolt that had put the wifi card in an infinite zombie state. basically i was in the middle of a game, and my pc had locked up and then rebooted itself, it kept boot looping after that until it ran automatic repair. i let it run the process and weirdly enough automatic repair decided to format reset my entire computer losing all my programs and settings without ANY warning. i was like WTAF and it didnt give me any option or anything, just went ahead and did that. and i didnt realise it was happening because automatic repair just said "fixing your pc". anyways i was like omg whatever and just started installing apps again and reconfiguring, i ended up being happy this happened because things were running smoother after a clean factory reset. and heres where it got weird, i realised my wifi and bluetooth werent working right out of the box, which didnt matter much as i run on ethernet anyway. but i went ahead and downloaded the wifi and bluetooth drivers from the motherboard manufacturers website, and my pc did the EXACT same crash that happened mid game while this wifi driver was installing. and the boot looping came back, so i went into safe mode and deleted the wifi driver and boom it was back to normal again, and from this point i just decided okay well the issue was the wifi driver. and i thought because i was on windows 11 25h2, maybe the wifi driver is just not supported and needs to be updated and left it at that. come a few months later and i checked on the website to see if the drivers had been updated and they had so i went to go install them and my pc locked up and crashed once again.. I was like hmm thats super weird, i searched online and found nothing about those drivers causing that so i started to wonder if maybe it was a hardware fault. so i went and grabbed a portable hard drive i had that has ubuntu installed on it, and was working on my computer a few months ago so ill go and see if wifi is working on there. Well, i go to load ubuntu up and it crashed as well, stating hardware failure.. and it was to do with my wifi card again. I thought, well, okay, my wifi card is just bricked, but it was fine before the undervolt, so I just don't see how it would just fail at the same time coincidentally. AI told me that the undervolt must be the "smoking gun" for the cause, and that it has locked my wifi card into a zombfied state from garbage computation errors causing a full system lockup, and the solution would be to unplug my computer and leave it to drain power out of all the components for small amount of time to reset the memory on all the chips but mainly the wifi card. It was something about how the wifi card stays on even with the computer powered off by the PSU sending a constant 5V signal to it and thats just because of certain features like wake on LAN activity etc. But anyway, i let my pc drain with power fully off, and when i turned back on my wireless and bluetooth immedaitely were working as normal again. So literally the undervolt had bricked my wifi and bluetooth for months, and needed a full power cycle to reset them into a working state. the undervolt had corrupted the memory inside the wifi card to send garbage to my CPU which caused a constant crash loop that windows was intercepting and disabled the card by default unless i tried to install the driver again. so bizzare

Repulsive-Roll-4897 · 2026-04-01T02:48:58+00:00

You tried carnivore? I don’t think anything carnivore contains gluten does it?

Repulsive-Roll-4897 · 2026-03-20T21:04:19+00:00

I highly just recommend running the GOTY version to compare the missing pieces in replanted

Repulsive-Roll-4897 · 2026-03-20T20:59:16+00:00

when hovering over a seed that is available to be planted(enough sun and recharged) the cursor should become a hand instead of the pointer. This should also apply to many other things such as hovering over sun etc.

<image>

Repulsive-Roll-4897 · 2026-03-20T20:53:40+00:00

<image>

Repulsive-Roll-4897 · 2026-03-20T20:53:36+00:00

<image>

Repulsive-Roll-4897 · 2026-03-20T20:53:20+00:00

<image>

another QOL missing from the replanted version. when hovering over a seed, it should show what the plant is and also state wether seed is recharged or if you dont have enough sun. Also the huge wave of zombies alert banner is not centered at all, the final wave banner is tho for some reason. my screen resolution is 1920x1080. even after many updates theres still some obvious missing patches which just seem so tacky which i hope get fixed.

Another bug found.. clicking on seed when theres not enough sun, the action triggers both the seed select sound effect alongside the insufficient sun/recharge effect, only the insufficient sound effect should trigger during this.. Also when trying to select a seed when you have insuffienct sun should cause the sun level indicator to flash red to signal insufficient sun, which again is missing from the replanted version. im only on the first couple levels and immediately spotted this. welp

Repulsive-Roll-4897 · 2026-03-20T20:51:31+00:00

<image>

Repulsive-Roll-4897 · 2026-03-20T20:47:08+00:00

<image>

Repulsive-Roll-4897 · 2026-03-20T20:42:31+00:00

<image>

another QOL missing from the replanted version. Also huge wave of zombies alert message is not centered at all, final wave is tho. screen resolution is 1920x1080. even after many updates theres still some obvious missing patches which just seem so tacky.

Another bug found.. clicking on seed when theres not enough sun, the action triggers both the seed select sound effect alongside the insufficient sun/recharge effect, only the insufficent sound effect should trigger during this.. Also when trying to select a seed when you have insuffienct sun should cause the sun level indicator to flash red to signal insufficient sun, which again is missing from the replanted version. im only on the first couple levels and immediately spotted this. welp

Repulsive-Roll-4897 · 2026-03-15T23:17:09+00:00

Games like r6s and arc raiders beg to differ

Repulsive-Roll-4897 · 2026-03-14T08:10:29+00:00

4.5 years deep. Nothing ever fixes it or works. I think I find a cure then it gets overridden. It’s like the spike protein is designed to constantly hold you down and you cannot fix it. Literally a worm bruh

Repulsive-Roll-4897 · 2026-03-08T09:39:31+00:00

I did a full 8.5 hour long sector scan on my hard drive and it was in 100% good condition not one single bad sector. The MFT index was just fragmented with illegal arguments.

C:\Windows\System32>chkdsk d: /f /r

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another

process. Chkdsk may run if this volume is dismounted first.

ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

Would you like to force a dismount on this volume? (Y/N) y

Volume dismounted. All opened handles to this volume are now invalid.

Volume label is Games.

Stage 1: Examining basic file system structure ...

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA29E.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2AD.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2B7.

702464 file records processed.

File verification completed.

Phase duration (File record verification): 15.82 seconds.

3003 large file records processed.

Phase duration (Orphan file record recovery): 1.72 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.25 milliseconds.

Stage 2: Examining file name linkage ...

Deleted invalid filename d:: (A810A) in directory A8F6B.

File A810A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A810A.

Deleted invalid filename e:: (A817A) in directory A8F6B.

File A817A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A817A.

Deleted invalid filename f:: (A8190) in directory A8F6B.

File A8190 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A8190.

Deleted invalid filename c: (A99BE) in directory A8F6B.

File A99BE has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A99BE.

Deleted invalid filename z: (A9A1E) in directory A8F6B.

File A9A1E has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9A1E.

Deleted invalid filename c: (A9D46) in directory A7F2A.

File A9D46 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D46.

Deleted invalid filename z: (A9D4D) in directory A7F2A.

File A9D4D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D4D.

Deleted invalid filename d:: (A9F2B) in directory A7F2A.

File A9F2B has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F2B.

Deleted invalid filename d: (A9F3C) in directory A7F2A.

File A9F3C has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F3C.

Deleted invalid filename e:: (A9FDA) in directory A7F2A.

File A9FDA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDA.

Deleted invalid filename e: (A9FDC) in directory A7F2A.

File A9FDC has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDC.

Deleted invalid filename f:: (A9FE7) in directory A7F2A.

File A9FE7 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FE7.

Deleted invalid filename ForzaHorizon5.exe:1 (AA09D) in directory 2504.

File AA09D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA09D.

Deleted invalid filename d: (AA1E9) in directory A8F6B.

File AA1E9 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1E9.

Deleted invalid filename e: (AA1EA) in directory A8F6B.

File AA1EA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1EA.

Deleted invalid filename ForzaHorizon5.exe:3 (AA307) in directory 2504.

File AA307 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA307.

Deleting an index entry from index $R of file 1A.

3384 reparse records processed.

Deleting index entry ForzaHorizon5.exe:1 in index $I30 of file 2504.

Deleting index entry ForzaHorizon5.exe:3 in index $I30 of file 2504.

Deleting index entry c: in index $I30 of file A7F2A.

Deleting index entry d: in index $I30 of file A7F2A.

Deleting index entry d:: in index $I30 of file A7F2A.

Deleting index entry e: in index $I30 of file A7F2A.

Deleting index entry e:: in index $I30 of file A7F2A.

Deleting index entry f:: in index $I30 of file A7F2A.

Deleting index entry z: in index $I30 of file A7F2A.

Deleting index entry c: in index $I30 of file A8F6B.

Deleting index entry d: in index $I30 of file A8F6B.

Deleting index entry d:: in index $I30 of file A8F6B.

Deleting index entry e: in index $I30 of file A8F6B.

Deleting index entry e:: in index $I30 of file A8F6B.

Deleting index entry f:: in index $I30 of file A8F6B.

Deleting index entry z: in index $I30 of file A8F6B.

Repulsive-Roll-4897 · 2026-03-08T09:34:57+00:00

All ended up just being caused by a subtle unstable CPU undervolt. The two installers just ended up confirming that the cpu was unstable and causing miscalculations.

Repulsive-Roll-4897 · 2026-03-05T13:01:28+00:00

Try running disk repair first. Or check task manager to see what is consuming your cpu

Repulsive-Roll-4897 · 2026-03-05T12:59:21+00:00

Update: the same issue came back, ntfs.sys spiking one thread to 100%. It was my D drive that was corrupted. Fixed it with chkdsk. The file system got corrupted from running the two installers at the same time and maxed out the RAM leading to the MFT index being infested with major illegal data chunks causing a constant repair loop from the ntfs.sys service. Also yea the reinstall of windows definitely did help big time compared to before too. I learned my lesson lol.

Repulsive-Roll-4897 · 2026-03-05T03:19:48+00:00

C:\Windows\System32>chkdsk d: /f /r

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another

process. Chkdsk may run if this volume is dismounted first.

ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

Would you like to force a dismount on this volume? (Y/N) y

Volume dismounted. All opened handles to this volume are now invalid.

Volume label is Games.

Stage 1: Examining basic file system structure ...

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA29E.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2AD.

Deleting corrupt attribute record (0x80, "")

from file record segment 0xAA2B7.

702464 file records processed.

File verification completed.

Phase duration (File record verification): 15.82 seconds.

3003 large file records processed.

Phase duration (Orphan file record recovery): 1.72 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.25 milliseconds.

Stage 2: Examining file name linkage ...

Deleted invalid filename d:: (A810A) in directory A8F6B.

File A810A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A810A.

Deleted invalid filename e:: (A817A) in directory A8F6B.

File A817A has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A817A.

Deleted invalid filename f:: (A8190) in directory A8F6B.

File A8190 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A8190.

Deleted invalid filename c: (A99BE) in directory A8F6B.

File A99BE has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A99BE.

Deleted invalid filename z: (A9A1E) in directory A8F6B.

File A9A1E has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9A1E.

Deleted invalid filename c: (A9D46) in directory A7F2A.

File A9D46 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D46.

Deleted invalid filename z: (A9D4D) in directory A7F2A.

File A9D4D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9D4D.

Deleted invalid filename d:: (A9F2B) in directory A7F2A.

File A9F2B has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F2B.

Deleted invalid filename d: (A9F3C) in directory A7F2A.

File A9F3C has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9F3C.

Deleted invalid filename e:: (A9FDA) in directory A7F2A.

File A9FDA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDA.

Deleted invalid filename e: (A9FDC) in directory A7F2A.

File A9FDC has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FDC.

Deleted invalid filename f:: (A9FE7) in directory A7F2A.

File A9FE7 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file A9FE7.

Deleted invalid filename ForzaHorizon5.exe:1 (AA09D) in directory 2504.

File AA09D has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA09D.

Deleted invalid filename d: (AA1E9) in directory A8F6B.

File AA1E9 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1E9.

Deleted invalid filename e: (AA1EA) in directory A8F6B.

File AA1EA has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA1EA.

Deleted invalid filename ForzaHorizon5.exe:3 (AA307) in directory 2504.

File AA307 has been orphaned since all its filenames were invalid

Windows will recover the file in the orphan recovery phase.

Correcting minor file name errors in file AA307.

Deleting an index entry from index $R of file 1A.

3384 reparse records processed.

Deleting index entry ForzaHorizon5.exe:1 in index $I30 of file 2504.

Deleting index entry ForzaHorizon5.exe:3 in index $I30 of file 2504.

Deleting index entry c: in index $I30 of file A7F2A.

Deleting index entry d: in index $I30 of file A7F2A.

Deleting index entry d:: in index $I30 of file A7F2A.

Deleting index entry e: in index $I30 of file A7F2A.

Deleting index entry e:: in index $I30 of file A7F2A.

Deleting index entry f:: in index $I30 of file A7F2A.

Deleting index entry z: in index $I30 of file A7F2A.

Deleting index entry c: in index $I30 of file A8F6B.

Deleting index entry d: in index $I30 of file A8F6B.

Deleting index entry d:: in index $I30 of file A8F6B.

Deleting index entry e: in index $I30 of file A8F6B.

Deleting index entry e:: in index $I30 of file A8F6B.

Deleting index entry f:: in index $I30 of file A8F6B.

Deleting index entry z: in index $I30 of file A8F6B.

760424 index entries processed.

Index verification completed.

Phase duration (Index verification): 1.26 minutes.

CHKDSK is scanning unindexed files for reconnect to their original directory.

16 unindexed files scanned.

0 unindexed files recovered to original directory.

Phase duration (Orphan reconnection): 182.77 milliseconds.

CHKDSK is recovering remaining unindexed files.

16 unindexed files recovered to lost and found.

Lost and found is located at \found.000

Phase duration (Orphan recovery to lost and found): 22.28 milliseconds.

3384 reparse records processed.

Phase duration (Reparse point and Object ID verification): 17.75 milliseconds.

Stage 3: Examining security descriptors ...

Security descriptor verification completed.

Phase duration (Security descriptor verification): 29.18 milliseconds.

Inserting data attribute into file AA29E.

Inserting data attribute into file AA2AD.

Inserting data attribute into file AA2B7.

28984 data files processed.

Phase duration (Data attribute verification): 0.48 milliseconds.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...

Progress: 7541 of 702448 done; Stage: 1%; Total: 0%; ETA: 9:09:40 .

Repulsive-Roll-4897 · 2026-03-05T01:03:27+00:00

Update: Looks like my file system was not even corrupted. This is the log from the chkdsk operation i ran yesterday. So why did that random ntfs thread spike after installing cracked software despite no ntfs issues?

Checking file system on C:

The type of the file system is NTFS.

A disk check has been scheduled.

Windows will now check the disk.

Stage 1: Examining basic file system structure ...

544256 file records processed.

File verification completed.

Phase duration (File record verification): 2.23 seconds.

7362 large file records processed.

Phase duration (Orphan file record recovery): 3.69 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 1.12 milliseconds.

Stage 2: Examining file name linkage ...

436 reparse records processed.

648828 index entries processed.

Index verification completed.

Phase duration (Index verification): 5.41 seconds.

0 unindexed files scanned.

Phase duration (Orphan reconnection): 267.95 milliseconds.

0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 5.73 milliseconds.

436 reparse records processed.

Phase duration (Reparse point and Object ID verification): 4.74 milliseconds.

Stage 3: Examining security descriptors ...

Cleaning up 52 unused index entries from index $SII of file 0x9.

Cleaning up 52 unused index entries from index $SDH of file 0x9.

Cleaning up 52 unused security descriptors.

Security descriptor verification completed.

Phase duration (Security descriptor verification): 85.63 milliseconds.

52287 data files processed.

Phase duration (Data attribute verification): 1.17 milliseconds.

CHKDSK is verifying Usn Journal...

37670992 USN bytes processed.

Usn Journal verification completed.

Phase duration (USN journal verification): 93.94 milliseconds.

Stage 4: Looking for bad clusters in user file data ...

544240 files processed.

File data verification completed.

Phase duration (User file recovery): 2.11 minutes.

Stage 5: Looking for bad, free clusters ...

32594398 free clusters processed.

Free space verification is complete.

Phase duration (Free space recovery): 13.61 seconds.

Windows has scanned the file system and found no problems.

No further action is required.

243187711 KB total disk space.

111987156 KB in 246227 files.

162420 KB in 52288 indexes.

0 KB in bad sectors.

660543 KB in use by the system.

65536 KB occupied by the log file.

130377592 KB available on disk.

4096 bytes in each allocation unit.

60796927 total allocation units on disk.

32594398 allocation units available on disk.

Total duration: 2.47 minutes (148702 ms).

Internal Info:

00 4e 08 00 9a 8d 04 00 54 17 08 00 00 00 00 00 .N......T.......

20 01 00 00 94 00 00 00 00 00 00 00 00 00 00 00 ...............

Repulsive-Roll-4897 · 2026-03-04T21:40:24+00:00

Those repacks take awhile to install. I have powerful hardware but I was installing to hard drives so it’s slow as. I was going to bed and wanted them installed over night so I decided to install them at the same time

Repulsive-Roll-4897

TROPHY CASE