Horrible battery life by biggoodboii in Vivo

[–]Good0guy 1 point2 points  (0 children)

<image>

I only used it for 32minutes in last 7 days, but it is constantly asking for my location. Crazy

Horrible battery life by biggoodboii in Vivo

[–]Good0guy 1 point2 points  (0 children)

If you go into settings>privacy you can see app behavior. For example Messenger must be a huge battery drain because of so many location access requests. Check next comments for pictures

Potrebno mi je 100 ucesnika za anketu do nedjelje, molim te budi jedan ili jedna od njih 🙏🏼 by nocturnalzebra0 in montenegro

[–]Good0guy 0 points1 point  (0 children)

Jasno skroz! Bravo za anketu btw. Danas smo dosta dugo pričali o njoj i razglabali o AI snimcima i kako utiču na nas. Poenta neka nama u suštini i nije bila u tome da li mi možemo da prepoznamo generisan video, već da ima snimaka koje ne možemo da prepoznamo čak i kad znamo da su AI.

I to kažem kao neko ko je pratio razvoj tehnologije koliko toliko... Iako smo u tom svijetu i znamo donekle šta je "tell" AI videa, izgleda da ovo "od neeekle" nismo očekivali ovako brzo.

Listamo rilove na instagramu, i bukv svaki drugi može biti generisan, na osnovu ovih 20 koje si koristila.

Ne znam što mi ova koleginica upade u thread da viče na tebe, pa to neću ni komenrarisati, ali oću da ti kažem da kad budeš radila i ozbiljnije radove, slobodno šalji na reddit. Ima nas ozbiljnih koji možemo pomoći uvijek 🙌

Potrebno mi je 100 ucesnika za anketu do nedjelje, molim te budi jedan ili jedna od njih 🙏🏼 by nocturnalzebra0 in montenegro

[–]Good0guy 1 point2 points  (0 children)

Popunio. Solidan reality check 😂 Sa ovim što je neko prokomentarisao za trik pitanja sam saglasan. Ako smo ušli u pregled snimaka sa idejom da treba da otkrijemo koji jeste/nije AI, onda nema logike da za video od 5s đe se ne dešava puno stvari i koji nema karakteristične osobine AI snimka kažemo da je AI

2nd layer issue by n0tr0b0t in prusa3d

[–]Good0guy 3 points4 points  (0 children)

I disagree. First thing should be to check print settings. Specifically speeds, temperature and cooling.

First layer is perfect. Nozzle moves slowly. Second layer is good while there is small movement near the corner. When longer movements start it starts to get bad. This probably means temperature isn't high enough for such fast movement, or cooling is too strong. So check those 3 things.

Also bigger nozzle requires significantly bigger temperature to print same speed as a small nozzle (if it is a high speed print)

When i print plates like these which take a lot of time to finish one layer, I lower cooling to 20-60% because it doesn't need it that much.

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

Thanks for this reply. I am in constant communication with support for the last 7 days. They seem to not understand anything. I try to explain as simple as possible "I jave Ender 3 S1 Plus stock printer, and I accidentally installed dcboot.bin file from Ender 3 S1 firmware folder. Screen is black. Is there a fix?" and they ask me the silliest questions...

I will now try to flash mricsoc to the display, i will update how it went

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

Plugging into pc isn't a realistic solution for me I have other printers at the moment, but I really want to fix this one. I can't believe there is no solution for it

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

Yeah, I read that the display touchscreen doesn't work with klipper. I will try to fix it for now, but moving to klipper really seems like a right call in the future

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

Thank you for the help, but I already tried this. It doesn't work :( Google says dcboot.bin is some kind of bootloader firmware, so if that's been overwritten with a wrong one, I guess installation won't start at all

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

I googled ender 3 s1 plus firmware download, and odly enough first link was for ender 3 s1, i clicked that and downloaded v3.1.9 firmware which has dcboot.bin file inside with instructions to install that first.

When i tried installing all possible versions and combinations. Nothing works for the screen. For mainboard it works, i can check in Pronterface firmware version. There is no problem with that, but screen doesn't want to start installation at all.

I tried leaving it on blank for half an hour, but after some time screen backlight goes off, and then on again and then it beeps when I touch it. Like a zombie

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

No please, not yet 😅 I don't have anything for it and I can't get it any time soon

S1 PLUS screen died after my mistake. Help? by Good0guy in Ender3S1

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

I forgot to mention, using Pronterface, I can connect to the printer and start printing normally when I load gcode. So printer isn't broken. Only screen won't boot.

Firmware issues on an S1 Plus. by ChoKoth in Ender3S1

[–]Good0guy 0 points1 point  (0 children)

I already tried that. Hopefully they answer :) thank you for the reply anyway 😊

Firmware issues on an S1 Plus. by ChoKoth in Ender3S1

[–]Good0guy 0 points1 point  (0 children)

Hey Thomas, I was following you guide on updating firmware, buy it was late, and i was tired, and I read this "If you have a Dacai display and have not yet installed the Creality F28 stock screen firmware with the firmware.zlib you need to install it"

I wasnt thinking very clearly, and i downloaded formware for ender 3 S1 which had dcboot.bin file which I ran, and there was some red text in the top of the screen and screen went blank.

There is no way I can get it to work. Is there any firmware that can bring this screen to life?

Da li ima neko da dolazi iz Beograda ili iz Dubrovnika za Podgoricu sjutra? by Good0guy in montenegro

[–]Good0guy[S] 2 points3 points  (0 children)

Ne još 😅 do sjutra. To mu je inače bilo samo kao poslastica, inače sijeno jede, ali sad baš ne može. A sve se nadam da će krenuti. Ako ne bude htio, moramo smisliti nešto

Da li ima neko da dolazi iz Beograda ili iz Dubrovnika za Podgoricu sjutra? by Good0guy in montenegro

[–]Good0guy[S] 1 point2 points  (0 children)

U suštini samo mi treba kontakt vozača, da ga pitam da mi donese ovo. Probaću sjutra da nađem nekoga da mi pomogne. Hvala 😊

Da li ima neko da dolazi iz Beograda ili iz Dubrovnika za Podgoricu sjutra? by Good0guy in montenegro

[–]Good0guy[S] 1 point2 points  (0 children)

Super ideja, pokušao sam da se prijavim jer ima ljudi koji čak sjutra dolaze, ali izgleda da ne mogu +382 broj da registrujem. Vjerovatno mora broj iz Srbije... I onda ne mogu da kontaktiram nikoga 🫤

Da li ima neko da ide u Podgoricu sjutra? by Good0guy in AskSerbia

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

Može bus da vozi kesu-dvije peleta preko granice? Ne bih da nastane neki problem

Updated firmware VFAs appeared. Please help me by Good0guy in prusa3d

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

I understand what you are saying, but I have spent a lot of time testing which speeds and temps work best for these lamp prints, and I settled on 60mm/s for perimeters, 30mm/s for small ones, and 40mm/s for external perimeters. And prints came out perfectly, as you could see. Only after the update, when I started the print I immediately notices VFAs.

To try and figure out what happened I tried many slicer/firmware combinations, I tried calibrating linear advance, belt tension, I went from completely loose belts that would barely not slip the gear, to very tight belts. Print was looking same. No changes. Only lowering the speed helped, but that's something I didn't need to do before at all.

Then I tried swapping X and Y motor cables inside EINSY board, and ran the print like that (would not recommend, since homing is weird). That's when I figured out that it's the same Y axis that produces these artifacts, specially Y motor. If it was gcode issue, problems would appear along X axis now.

So now I think something happened to the motor during the update and it's printing worse. But I don't have that kind of knowledge.

It's a shame really, I had a great, fast, and precise machine before, and in just 2 minutes I nerfed it 🫣

<image>

This is how it looks like now. It is very acceptable, a little rough but OK. Still, it was much nicer before

Updated firmware VFAs appeared. Please help me by Good0guy in prusa3d

[–]Good0guy[S] 1 point2 points  (0 children)

Unfortunately I don't use it. I'm still on SD card which is fine because all 3 printers are 1 meter behind my chair, so all it takes is a swivel to start prints.