[EHS6] no startup JRC and user MIDlet | Thales IoT Developer Community
September 7, 2015 - 2:58pm, 1594 views
Currently I have deployed around 1000+ EHS6 based terminals, almost without, problems. On very small occasions I get terminals returned for RMA with the following problem;
1. The JRC MIDlet did not start anymore.
2. My own MIDLet did not start anymore.
3. The terminal did have a backup battery, which runs the terminal for a day, after powerloss.
4. Global and userware AutoStart are active.
Last week, the same problem in the field. The terminal did not start any MIDlet. After reboot, AT+CFUN=1,1, power off + restart button, etc. Replaced the terminal. And after a few days ****** on my desk, I powered it on and now it looks like to work correctly!
What could be the cause? And what could prevent the start of the JRC?
Is there a way the MIDLets always will try to start? (So not a finite amount)
Thnx, Mark.
Hello,
The autostart function should always start the MIDlets if the global austostart is enabled and MIDlet autostart is enabled.
You can configure the autostart delay. Additionally you can set the order and the restart ***** (in the jad file) - if the MIDlet terminates non gracefully because of some problem it is automatically restarted and if the ***** is exceeded the whole module is rebooted.
Do you have terminals that did not get back to work? Is there any output on System.out or other interfaces? Any "^SYSINFO:" outputs?
Is it possible to start these MIDlets manualy?
Have you tried to do firmware update? Can you send the AT^SCFG? and ATI1 outputs from such a terminal?
If the same terminal is working correctly after some time or taken from the field to the office then maybe there is some hardware problem or power supply problem.
If you have returned these terminals and they still don't work correctly the Gemalto engineers should be able to get some error logs.
So the it would be the best to talk to technical support in order to clarify the problem.
Regards,
Bartłomiej