Service background crash

[Felipe França]

Hi,

My service background stop when my app starts. I'm using buildozer last version, python-for-android master, kivy 1.10.0, bootstrap sdl2
I call my service as follows:

    from android import AndroidService
    service = AndroidService('My service', 'running...')
    service.start('service started')
    self.service = service

and log is: 

I/python (11309): [INFO ] [Kivy ] v1.10.0
I/python (11309): [INFO ] [Python ] v2.7.2 (default, Aug 2 2017, 14:30:39) 
I/python (11309): [GCC 4.9.x 20150123 (prerelease)]
I/python (11309): [INFO ] [Factory ] 194 symbols loaded
I/python (11309): [INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_gif (img_pil, img_ffpyplayer ignored)
I/python (11309): [INFO ] [Text ] Provider: sdl2
I/python (11309): [INFO ] [OSC ] using <thread> for socket
I/python (11309): [INFO ] [Window ] Provider: sdl2
I/python (11309): [INFO ] [GL ] Using the "OpenGL ES 2" graphics system
I/python (11309): [INFO ] [GL ] Backend used <gl>
I/python (11309): [INFO ] [GL ] OpenGL version <OpenGL ES 3.0 V@84.0 AU@ (CL@)>
I/python (11309): [INFO ] [GL ] OpenGL vendor <Qualcomm>
I/python (11309): [INFO ] [GL ] OpenGL renderer <Adreno (TM) 305>
I/python (11309): [INFO ] [GL ] OpenGL parsed version: 3, 0
I/python (11309): [INFO ] [GL ] Texture max size <4096>
I/python (11309): [INFO ] [GL ] Texture max units <16>
I/python (11309): [INFO ] [Window ] auto add sdl2 input provider
I/python (11309): [INFO ] [Window ] virtual keyboard not allowed, single mode, not docked
I/python (11309): android
I/python (11309): [INFO ] [GL ] NPOT texture support is available
I/python (11309): [WARNING] [Base ] Unknown <android> provider
I/python (11309): [INFO ] [OSC ] listening for Tuio on 127.0.0.1:3002
I/python (11309): [INFO ] [Base ] Start application main loop

When the app starts, a popup appears saying that the service has stopped but the app run normally, any idea of ​​what is happening?

[ZenCODE]

Is this log from the service or the app? Try and add logging to the service so you can see if it starts and crashes, or just does not start....

[Felipe França]

Hi ZenCODE,

Is this log from the service or the app?

No, this log is from the main app.

The service is not create a log, it is not starting.

[ZenCODE]

Well, the fact that is says it stopped implies that it must have started, not? You can't really stop something that has not started. Or does the start call fail? You don't mention exactly when this error occurs or when the pop appears. That might us narrow the problem down.