Push registrations for Bluetooth MIDlet turns off in the latest S60 3rd Edition devices (Known Issue)
Push registrations for Bluetooth are turned off in S60 devices if the device is turned off.
Starting from MIDP 2.0, MIDlets can use push registry to set themselves up to be launched automatically if the underlying implementation supports push operations. MIDlets can be activated by incoming connections if they first register with push registry, either statically or dynamically.
In S60 3rd Edition FP2 and S60 5th Edition, both static and dynamic registrations for Bluetooth connections will be set off if the device is turned off.
How to reproduce
To test this issue, you need two S60 devices.
The issue can be reproduced by testing static push registration as follows:
1. Include a Bluetooth connection string for static push registration in the JAD of a test MIDlet, for example:
2. Install and launch the test MIDlet. The push registration will be performed.
3. To perform device and service search, install a Bluetooth MIDlet to another S60 device and launch the application. You can use, for example, the MIDlet for S60 devices in the 'Supplementary material' section of CS001213 - Discovering Bluetooth services in Java ME.
4. Once completed, check that the list of discovered services includes the connection string (either the full string or just the name; for example, the example MIDlet returns 'Service -pushTest').
5. Turn off the device with the static registration and turn it on again.
6. Repeat device and service search with the other device.
7. The connection string (see step 4.) is now missing from the S60 device.
No solution expected for S60 3rd Edition FP2 and S60 5th Edition devices.