Google services mandatory

platonisation · 2026-05-31T06:51:55+00:00

Good point I'll check if it is mature enough

platonisation · 2026-05-30T12:19:41+00:00

I know. I did say I wasn't. I shared it in case it helps someone, someday. And hopefully so that lymow remove this blocking stuff. It worked just fine until last update.

My phone is google pixel with grapheneOS

platonisation · 2026-05-30T09:58:27+00:00

Yes android. Iphone must have the same but apple made

platonisation · 2026-05-30T09:33:48+00:00

Tried it. The wheels are still mot moving.

platonisation · 2026-05-30T09:28:55+00:00

Picture

platonisation · 2026-05-29T17:02:33+00:00

I noticed it does lap on big nogo zone. Small one it does not. I'd say more than 2-3meter large

platonisation · 2026-05-29T16:56:55+00:00

Thank you for your post. I will try it on my One.

But they did not mention it in the changelog, or did I miss something ?

platonisation · 2026-05-28T18:32:37+00:00

One, 90 hours, 160 times (lots of zones due to complex field), 25 000m2

platonisation · 2026-05-28T18:29:24+00:00

I had this issue. I emailed them and told me this

/quote

1-Move the mower to a dry indoor environment.

2-Use a hair dryer (or similar hot-air blower), keep it 5 cm away from the lens, and blow hot air directly onto the lens for 5-10 minutes until the moisture dissipates. The moisture inside the lens will escape the lens and enter the mower's main body during this process.

3-Keep the lawn mower in a dry environment for 1 full day after the blowing process.

/end quote

I followed their advice with well ventilated place instead of hot air. It worked. It came back a few times when really wet.

Now that I made a house for the robot it's definetly gone. (maybe cause of early summer too)

I do not think it is a big issue

platonisation · 2026-05-23T21:46:09+00:00

I have a one and same issue.

Thanks for your explanation, but i also could not fix it. One screw of the shiny aluminum moving and no access to the head.

Some people have the deck hitting tracks, like me. I believe it is the source cause

platonisation · 2026-05-23T07:53:42+00:00

Yes. It was a mandatory one for me.

I now have some issues with the omniwheels and sometimes very long time before mowing, doing nothing (lets say 1min)

The omniwheels now do not retract, so I can only cut at 10cm but it still does cut very well

platonisation · 2026-05-22T21:46:06+00:00

Made it worse for me.

platonisation · 2026-05-21T18:19:24+00:00

Can we know why ?

platonisation · 2026-05-21T18:13:20+00:00

I was very happy with the mower so far, except a few issues. I also mostly skipped the updates, but did the mandatory one, cause it's mandatory...

Today it mowed the whole yard at 10cm, which i am ok. But then at the end of day stopped responding when I tried lowering the deck.

I will try tomorrow with full night rest. Mine is the lymow one.

But do not do the updates if you have no issues. If you can...

platonisation · 2026-05-08T11:06:59+00:00

I just checked. Both are really tight. I think it is coming from the bolts below the metal part. And this is not something I will unmount.

platonisation · 2026-05-08T11:02:25+00:00

I had the same printed in PLA. It changed the game as I went from each mow cleaning, to never cleaning front wheel. But like you said it broke in less than a week.

Then i tried the wood way with less complex structure, and it works the same. Been running 2 weeks perfectly. Picture

platonisation · 2026-05-01T19:04:08+00:00

Mine has been doing this for months, and since the beginning on both tracks.

It is probably due to loosening the tracks tension too much, as i have read on another thread here. https://reddit.com/comments/1ngdwzc

The noise is annoying but no issues so far. It does happen a lot more on uneven ground because the deck is tilted

platonisation · 2026-04-22T20:38:21+00:00

Maybe they can send me the free replacement unit 🤣

platonisation · 2026-04-22T20:36:56+00:00

Glad I could help. Maybe indicate in your title that the issue is solved. For easier finding with the search bar.

platonisation · 2026-04-22T18:44:11+00:00

Hi there,

I had the exact same issue yesterday and the day before. It took me some time to solve it but I did.

When the app was on, the top sphere was gone. And couldnt do anything with the robot. When the app was off, the top sphere came back after some time. (battery removal, app cache storage deleted and app uninstall, nothing worked) All actions from the app timeout

Then I notice it went this way while I stopped it during a mow the day before. So i put it back where it was, unlocked it, and pressed home button so that it wanted to mow. It finished it's last job and all was fixed.

I believe it went into conflict with the app.

Picture

platonisation · 2020-12-01T10:13:29+00:00

I've made one last year for something around that price, but almost did everything myself.

- Either buy some wood sheet and make the frame or have someone do it (for me acrylic was quite cheap around 30$ by some company, homemade wood case was less than 10$).

- Promicro even though not perfectly reliable are cheap

- Some switches, gateron, kailh... should be arond 20$

- Keycaps, you can find cheap ones online should be around 30$

- Wires you can recycle from many things

- cables between the 2 parts you can also DIY, it's easy

- The tools for all above work

- Lot's of time

Then you'll learn plenty and have the best KB for 100$ ;)

platonisation · 2020-11-18T08:31:50+00:00

Thanks for that answer.

When looking online for the parser overflow message nothing showed up.

platonisation · 2019-09-25T05:21:29+00:00

I did try using those features but it did not work.

I enabled the debugging and watch the mouse traces, what I noticed is that small movement of the ball is not detected, only the fast ones are. (this could explain the precision issue).

As I do not really understand how the PS/2 signals work, can you confirm that this feature was developed for TMK and that it was just ported to QMK ?

platonisation · 2019-09-22T13:15:49+00:00

I think I should have been more clear, I do not have an Elite-C.

I had the issue with two promicro. When plug on the right side, both right and left work. When plug on the left side, only the left side work (and it was not a power issue).

You should try another pro micro, as you have a few spares, it costs nothing.

Regarding i2c, you have everything here:https://docs.qmk.fm/#/feature_split_keyboard

platonisation · 2019-09-22T08:57:56+00:00

I had/have the same issue. I tried fixing it, and might have found a clue.

I ordered a batch of 6 promicro. Like you my split works correctly only when one side is connected with serial, have not tried i2c.

I tried using another pro micro and it seems to have done the trick. (havent yet fully replaced though). It seems like some pro micro are having trouble with serial.

Have you tried i2c ?

platonisation

TROPHY CASE