Emme Developer Well-Known Member Licensed User Longtime User Dec 5, 2018 #1 Hi to all! As wrote in Android documentation: "Apps that target Android 8.0 or higher can no longer register broadcast receivers for implicit broadcasts in their manifest. An implicit broadcast is a broadcast that does not target that app specifically", applications can't now listen to new paired device (or unpaired). Is possibile to achieve this thing (like we are using inplicit intent) without using job scheduler? (Job scheduler as i understood can scan devices every 15m) Thanks to all
Hi to all! As wrote in Android documentation: "Apps that target Android 8.0 or higher can no longer register broadcast receivers for implicit broadcasts in their manifest. An implicit broadcast is a broadcast that does not target that app specifically", applications can't now listen to new paired device (or unpaired). Is possibile to achieve this thing (like we are using inplicit intent) without using job scheduler? (Job scheduler as i understood can scan devices every 15m) Thanks to all
DonManfred Expert Licensed User Longtime User Dec 6, 2018 #2 Emme Developer said: applications can't now listen to new paired device (or unpaired) Click to expand... Why they can´t? Do you get any error? Upvote 0
Emme Developer said: applications can't now listen to new paired device (or unpaired) Click to expand... Why they can´t? Do you get any error?
Erel B4X founder Staff member Licensed User Longtime User Dec 6, 2018 #3 BluetoothAdmin will work. If you want to discover devices while the app is in the background then you need to use a foreground service. Example: https://www.b4x.com/android/forum/threads/background-location-tracking.99873/ Upvote 0
BluetoothAdmin will work. If you want to discover devices while the app is in the background then you need to use a foreground service. Example: https://www.b4x.com/android/forum/threads/background-location-tracking.99873/
Emme Developer Well-Known Member Licensed User Longtime User Dec 7, 2018 #4 DonManfred said: Why they can´t? Do you get any error? Click to expand... Intent is not recognized by application Erel said: BluetoothAdmin will work. If you want to discover devices while the app is in the background then you need to use a foreground service. Example: https://www.b4x.com/android/forum/threads/background-location-tracking.99873/ Click to expand... I Need to recognize It in background, but this mean that i need to show a persistent notification (am i wrong?) and this is not wonderful for a good UI in my app Upvote 0
DonManfred said: Why they can´t? Do you get any error? Click to expand... Intent is not recognized by application Erel said: BluetoothAdmin will work. If you want to discover devices while the app is in the background then you need to use a foreground service. Example: https://www.b4x.com/android/forum/threads/background-location-tracking.99873/ Click to expand... I Need to recognize It in background, but this mean that i need to show a persistent notification (am i wrong?) and this is not wonderful for a good UI in my app
Erel B4X founder Staff member Licensed User Longtime User Dec 9, 2018 #5 Emme Developer said: but this mean that i need to show a persistent notification (am i wrong?) and this is not wonderful for a good UI in my app Click to expand... You are not wrong. However there is no other way to do it. Upvote 0
Emme Developer said: but this mean that i need to show a persistent notification (am i wrong?) and this is not wonderful for a good UI in my app Click to expand... You are not wrong. However there is no other way to do it.
Tempomaster Active Member Licensed User Longtime User Jan 16, 2019 #6 Hello, I have recently received more and more reports that the startup with Bluetoth on my app Tempomaster no longer works. Since I do not use this autostart myself, I checked it. On my smartphone with Android 8.0 also happened nothing more. I bought the phone with Android 7, there was everything right with the startup. The updates were done automatically. I use the autostart from the following article: https://www.b4x.com/android/forum/t...-are-connected-to-bluetooth.16555/#post-96237 I found the solution of the problem rather by accident. I tried this example and put it into my project: https://www.b4x.com/android/forum/t...matic-bluetooth-device-bonding.25675/#content Suddenly, the service S2 logged back with log messages. This one was not started before. I had adopted a manifest entry of the new example in my project: Code: Copy AddPermission (android.permission.BLUETOOTH) AddPermission (android.permission.BLUETOOTH_ADMIN) The second line is the added entry. That was the whole art. The Bluetoth autostart now works as usual. Best regards, Gunnar Last edited: Jan 16, 2019 Upvote 0
Hello, I have recently received more and more reports that the startup with Bluetoth on my app Tempomaster no longer works. Since I do not use this autostart myself, I checked it. On my smartphone with Android 8.0 also happened nothing more. I bought the phone with Android 7, there was everything right with the startup. The updates were done automatically. I use the autostart from the following article: https://www.b4x.com/android/forum/t...-are-connected-to-bluetooth.16555/#post-96237 I found the solution of the problem rather by accident. I tried this example and put it into my project: https://www.b4x.com/android/forum/t...matic-bluetooth-device-bonding.25675/#content Suddenly, the service S2 logged back with log messages. This one was not started before. I had adopted a manifest entry of the new example in my project: Code: Copy AddPermission (android.permission.BLUETOOTH) AddPermission (android.permission.BLUETOOTH_ADMIN) The second line is the added entry. That was the whole art. The Bluetoth autostart now works as usual. Best regards, Gunnar
