I have to make a "kiosk mode" application, 24 hours run, it is advisable to put a timer of 500 milliseconds in the service module? Or is it better to use the StartServiceAt
I put timers in services, since I'm sure that the event is fired when It's need. I have a small APP to serve incoming SMS and store in DB. It have been running for months with no problem. But I built the logic on a service, so it can work also in background.
Services are made to be reliable. So what's the problem with "StartServiceAt"? Add a "#StartAtBoot" so nothing can go wrong (even if the device reboots).
Services are made to be reliable. So what's the problem with "StartServiceAt"? Add a "#StartAtBoot" so nothing can go wrong (even if the device reboots).
Yes I already know that.
But I have read some very expert people post, they recommend not put a timer on a service module.
And seeing one in the application of the kiosk, I thought maybe something has changed in B4A and no longer give problems
I put timers in services, since I'm sure that the event is fired when It's need. I have a small APP to serve incoming SMS and store in DB. It have been running for months with no problem. But I built the logic on a service, so it can work also in background.
Be aware that the OS of a kiosk must be able to run ininterrupted for months. I have been writing them on XP platforms about 10 years ago. They were reliable but once or twice every year they were unresponsible. I had to produce an external watchdog to reset the malfunctioning hardware. I don't know if Android hardware/OS is worth of such use... How many times a month do you need to reset your smartphone?