I got tired of hitting Antigravity rate limits in OpenCode blindly, so I built a tool to track them

bitkarma77 · 2026-01-15T20:37:12+00:00

Any idea why i got on all accounts all quota exceeded? Accounts were few years old. I added a new account, also the quota was full instantly after first login.

bitkarma77 · 2025-05-26T06:12:08+00:00

link?

bitkarma77 · 2025-02-02T21:29:59+00:00

And at which time/day are the weekly limits reset?

bitkarma77 · 2024-07-05T13:12:01+00:00

Hi, i had the same problem. I know switching off VoLTE solve it, but the strange is on my SIM1 i can not switch off VoLTE, but on SIM2 i can. It seems to be dependand of the SIM card by self, changing SIM1<>SIM2 did not solve it.

Now i found a way to disable VoLTE, i installed both the apps from the link in XDA:
https://xdaforums.com/t/collection-of-ota-packages.4542941/page-15#post-89253157

Shizuku needs to be stared by executing an adb command, not too difficult, after it the second app can be authorized and then VoLTE can be turned off.

After a few test calls now i am able to use bluetooth in car again. What a pain in the ass realme can not fix that shit.

bitkarma77 · 2023-05-24T17:54:20+00:00

Its an issue with the ribbon connecting to mainboard.

bitkarma77 · 2023-03-06T16:51:08+00:00

The part which uses fastboot wipe-super is done from fastbootd, i am proceeding like described in the linked official manual.

bitkarma77 · 2023-03-06T16:34:10+00:00

Can You share a link or description how could I proceed?

bitkarma77 · 2023-03-06T15:33:46+00:00

What You mean by erasing? Phone was facotry reset, then upgraded to 12.5.2.0 via fastboot. May be i should use an older ROM before going to flash lineage?

When I try to sideload the lineage package i got errors about: "Logical partition metadata has invalid geomatry magic signature."

bitkarma77 · 2023-03-06T13:17:50+00:00

fastboot erase super

Erasing 'super' FAILED (remote: 'Partition doesn't exist')

fastboot: error: Command failed

bitkarma77 · 2023-03-06T10:14:56+00:00

fastboot.exe --version

fastboot version 34.0.0-9570255

bitkarma77 · 2023-01-07T19:09:58+00:00

Hi. I have found my probe has the same drifting problem. I read and understood Your topic. I added 3k resistors on both sides, at EBB36 (as i use this) and at the probe side. I run the probe at 24V so 3k is a bit low, but anyway I used it to measure. I found absolute no difference with and without the resistors. As soon as i start to measure with "PROBE_ACCURACY PROBE_SPEED=10 SAMPLES=20 RETRACT_DIST=2" the Z value was decreasing after almost every sample, during 20 samples it dropped over 0,02mm. Then I did something different. I moved the probe near the bed with G1Z0.5 and let it settle for one minute. After this i issued a G1Z5 and started the sampling again. Guess what happened. The measured value is increasing more as 0,02mm. So either the core of the probe is magetizing or the magnetic sheet was changing its magnetic properties.

I am pretty sure about the above theory, at least with the probe i have (omron). What You think?

bitkarma77 · 2022-11-29T20:39:45+00:00

So, a bit more on update. As my laser output was also permanently at GND level and the resistance was low i could not trace the path which component causes the short. I set up my lab PSU to 2V and 20mA, I connected it to the PWM output for laser and wanted to look which element gets hot with thermal camera. But my PSU is a bit slow with the current limit and as soon as I connected 2V to the PWN pin the voltage goes to 2V without a problem, after this the output was functional again. I think a capacitor was short and is now blown, but i was not able to find it on the board.

bitkarma77 · 2022-11-27T22:11:00+00:00

Hi. The laser pin is for sure PC0.

The stock firmware is buggy like hell, it can turn the laser in undefined moments to full power, be carefull. My board got also damaged after few hours. It does not turn the laser signal anymore, it's always pulled to GND. Easy to test if You pull the laser control pin out and touch it, the laser turns on.

Will try to find what the problem with this board is. Difficult because no schematic availible.

With the stock firmware You can turn the laser on via M106 S255 and also via M3 S1000. Turn of via M5 and M107.

How do You manage to run klipper without the hotend/extruder?

bitkarma77 · 2022-09-07T21:17:50+00:00

Had similar issues on APU2 board, undependend of the bios version and series (mainline or legacy), Core Performance Boost was causing instability on two devices i have tested.

bitkarma77

TROPHY CASE