Can someone please tell me why this graph is going ul and down? Shouldn't it just go down? I'm not charging it again and again.
RC3 is in preparation with a fix for stats not showing. The problem is very weird: the selected references are being nulled as if bbs was removed from memory without the app being notified of that. This is normally not possible as there are events fired before an app gets removed from memory. In the log I see reports of ActivityManager unloading bbs but the event is never called.
The workaround is to detect that state on resume and retrieve the default values for the spinners.
I am doing some testing on L and will release RC3 later today.
Edit: and BTW the limited unrooted feature set of BBS works fine on L. Rooting now to see how the rest goes
Read last page and this page. Issue is with new Google now launcher/ Google search 3.5 for some weird reason. A fix is being worked on since the Dev was able to recreate the issue on the L PreviewI'm running a Nexus 5 rooted on 4.4.4 with franco kernel and xposed + gesture navigation.
BBS worked fine till recently. Now when I open the app, I get a toast message that says "Selected 'from' or 'to' reference could not be loaded. Please refresh"
No matter what I do It won't load anything. No stats or change anything. I tried refreshing, uninstalling, clearing caches, even did a full wipe and reinstalled android. I have given BBS root access. The attached pic shows all I get.
Thank you
After hours of debugging and reading I finally have found the error related to the references / stats being lost on some devices / configurations.
And guess what?
It is not related to google search or google launcher
The root cause is a bug in BBS that always has been there......
In a nutshell: when BBS is started (onCreate) the references to be displayed are retrieved from the settings. After that there is a check to see if BBS was called from another place (e.g. from the widget) and passed parameters on the references (from/to) to display. The mechanism use for that is called an intent "extra". Now here starts the trouble. With most launchers this extra was null so BBS retrieved the settings, checked if extras were passed, didn't find anything and all was good.
Now with some launchers (google launcher) the extra is not null anymore so BBS read the references to be shown from the extra. Unfortunately the extra not being null does not mean that there are any references passed (in fact there are none) so BBS read from/to as null/null from the extra, causing the weird error messages and behavior.
The fix is:
- read values from settings
- if there is an extra
- check if the extra contains reference data
- if yes use then, if not discard <------ that was added
In other words, 8 hours of work to fix 3 lines of code.
TBH I have not checked yet if the launcher is allowed to pass an empty extra or if BBS is wrong..... the most important thing is that I found and removed the cause. RC3 coming in a few minutes
RC3 is up, hopefully fixing the problem certain users have had with references (and stats) being lost.
The update to the new SDK has broken my build workflow (new ant tools) and it will take me a while to fix that in order to build RC3 for gplay. Once you guys test I will fix it and release RC3 to the beta channel on gplay for testing the update process.
Looks like the partial wakelocks have changed unit from microseconds to milliseconds on the L preview
Not sure if it just needs more time, but so far nothing shows up under Alarms (Android L) Definitely have root, as the other stats show up. will install some apps that I know should create them and let it sit for a bit longer, see what happens.
Working on alarms currently: the format has changed so I need to adapt the parser accordingly
Oh, lol I should have known you were on top of it already, sorry about that!
After hours of debugging and reading I finally have found the error related to the references / stats being lost on some devices / configurations.
And guess what?
It is not related to google search or google launcher
The root cause is a bug in BBS that always has been there......
In a nutshell: when BBS is started (onCreate) the references to be displayed are retrieved from the settings. After that there is a check to see if BBS was called from another place (e.g. from the widget) and passed parameters on the references (from/to) to display. The mechanism use for that is called an intent "extra". Now here starts the trouble. With most launchers this extra was null so BBS retrieved the settings, checked if extras were passed, didn't find anything and all was good.
Now with some launchers (google launcher) the extra is not null anymore so BBS read the references to be shown from the extra. Unfortunately the extra not being null does not mean that there are any references passed (in fact there are none) so BBS read from/to as null/null from the extra, causing the weird error messages and behavior.
The fix is:
- read values from settings
- if there is an extra
- check if the extra contains reference data
- if yes use then, if not discard <------ that was added
In other words, 8 hours of work to fix 3 lines of code.
TBH I have not checked yet if the launcher is allowed to pass an empty extra or if BBS is wrong..... the most important thing is that I found and removed the cause. RC3 coming in a few minutes
Please read the last few pages to know why BBS doesn't work with Samsung devices.Hi all.
Please kindly help me solve this problem.
I used adb to grant full permissions as instructed by the application.
But I still can't use it when the app displays "Private APIs not grandted" like picture.
I'm using S22 ultra, Android 13, One UI 5.1
Many thanks
Check THIS post by the dev. Still remains unresolved. Unless the dev is able to come up with something, you are stuck.I used the Search dialog box to search for the same problem as mine but I couldn't find a way to solve it.
So is there no other way to use it on Samsung phones bro?
I feel very sad when I hear this. But anyway, thank you very much for your fast support. All the bestCheck THIS post by the dev. Still remains unresolved. Unless the dev is able to come up with something, you are stuck.
You you mind writing all that together (location settings, autostart settings) in one post. I'd like to add that to the FAQ