Second lesson learnt

[udg]

Hi all,
it took me a full day to accomplish a simple task: an home widget needing Internet access soon after reboot (or device power on).
Tried several code variations, tips, tricks, whatever. And an infinite sequence of reboots.
Then I tried the "failing" code on a different device..and it worked!

And it came the epiphany !

Check the damned Energy Saving stuff. Sure enough the "failure" lied there. Switching off the "optimization", deleting my app from the "bad guys" list..and it started working as designed!

So, the lesson I learned was: check the Energy Savings if your app behaves strangely on a specific device.

"Wait a minute" , a voice from the back of the room
"Which is the first lesson ?"

Oh, right. In my case is " when something doesn't work on your PC, check the firewall rules". I use to set very strict rules and it happens that my habit strikes me from time to time...

 

[rabbitBUSH]

Check the damned Energy Saving stuff.

I heard that the AI is Hugely energy hungry - so don't try that next time - it will fail - its a simple task......

 

[udg]

No worries about AI energy requirements.
The pendulum is swinging from private/personal/local to common/shared/remote, so next generations devices will be just simple connecting stuff to our "private" area on super-mega remote infrastructures powered by nuclear plants and supervised by real AI.

Meanwhile any challenge is good to exercise our NI (natural intelligence) or BI (biological intelligence); feel free to choose the definition you like most while keeping on solving daily problems without the so called AI (at least the "toys" they're showing us).

 

[rabbitBUSH]

As long as the "real" AI clubs the black hat hackers in the brain - then paragraph 1 - well - AI would need to scan and crosscheck a bazillion logs ....but I digress..

Im waiting for the NI-BI-AI (nibbyeye) powered by hydrogen then won't need nuclear.

But it is interesting what you point out - that it's sometimes baffling what can throw a project into an error-hunting loop.

 

[KMatle]

Check the damned Energy Saving stuff. Sure enough the "failure" lied there. Switching off the "optimization", deleting my app from the "bad guys" list..and it started working as designed!

I remember the times when WhatsApp (was quite new then) had the same problem on "newer" devices. A lot of complaints about not receiving push notifications. Had the same issue and came to the same point. When dealing with FCM messages in my own apps I (of course) forgot about the energy saving and spent hours of analyzing