[APP][4.0.3+ & GB][XPOSED] BootManager

Search This thread

2_i

Member
May 22, 2013
30
3
Have you also updated Xposed to the new 2.6? In it's thread are some more reports about reboots

Let's see, I only looked at the version backwards and first suspected another, newly installed Xposed module, and even Xposed installer, to be the culprit. However, by the second day I isolated the issue to be that of the Manager. Maybe the update times could be of help. The first time I went into the reboot loop was after an update on Fri 5/16 at about 1pm and next on Sat 5/17 about 10am, both EST, upon fresh download from the Repository.

---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------

Have you also updated Xposed to the new 2.6? In it's thread are some more reports about reboots

OK, I guess at first I did not fully understand the question, thrown off by the 2.0.6 <-> 2.6 correspondence. Yes, I updated and now run Xposed Installer 2.6, but on its own it does not give me problems. I am for the second day on that version and past several reboots. Normally, that is not yet enough to tell that e-thing is fine, but there are no red flags.
 

defim

Senior Member
Feb 18, 2012
2,744
1,487
@2_i;52748504: Take a look into the logfile of Xposed, it should tell you what causes it. With "Xposed 2.6" there where some API changes and not all modules works with these. I've updated all my modules, so i think Xposed itself or another module is the culprit.
 

2_i

Member
May 22, 2013
30
3
@2_i;52748504: Take a look into the logfile of Xposed, it should tell you what causes it. With "Xposed 2.6" there where some API changes and not all modules works with these. I've updated all my modules, so i think Xposed itself or another module is the culprit.

BootManager 2.0.5 is active and works fine with Xposed 2.6. I look at the log, but the only info I have is since the tonight's nightly reboot. One problem is that after the reboot loop I need to do a full-scale restoration from a backup, so I am not sure any log can survive that. Maybe I can access files in the recovery mode, but never tried that yet. In the current log, I only have some at.dalvik.system.NativeStart.run java.lang.IllegalAccessEception: access to field not allowed, but am not even sure that is even related to the Xposed Framework. I think I'll just try to sit it out, putting off the updates for a while and retrying only right after a complete backup.
 

claytonjn

Senior Member
Nov 3, 2011
1,561
836
claytonjamesphotography.webs.com
BootManager 2.0.5 is active and works fine with Xposed 2.6. I look at the log, but the only info I have is since the tonight's nightly reboot. One problem is that after the reboot loop I need to do a full-scale restoration from a backup, so I am not sure any log can survive that. Maybe I can access files in the recovery mode, but never tried that yet. In the current log, I only have some at.dalvik.system.NativeStart.run java.lang.IllegalAccessEception: access to field not allowed, but am not even sure that is even related to the Xposed Framework. I think I'll just try to sit it out, putting off the updates for a while and retrying only right after a complete backup.

Everything found in the log file you get to through the Xposed app is related to Xposed. You should not be seeing any errors in there, if you are then there is a module you have installed that is incompatible with your ROM. Some errors you may only see once when Xposed first loads, if that is the case you can probably ignore the error and everything will be fine, however if you have errors repeating continuously it will use a lot of resources and (unless rovo89 changed this behavior in 2.6) will cause the log file to grow until it is so big the app can no longer parse the contents in which case only a reboot will clear it.
 
  • Like
Reactions: 2_i

2_i

Member
May 22, 2013
30
3
Everything found in the log file you get to through the Xposed app is related to Xposed. You should not be seeing any errors in there, if you are then there is a module you have installed that is incompatible with your ROM. Some errors you may only see once when Xposed first loads, if that is the case you can probably ignore the error and everything will be fine, however if you have errors repeating continuously it will use a lot of resources and (unless rovo89 changed this behavior in 2.6) will cause the log file to grow until it is so big the app can no longer parse the contents in which case only a reboot will clear it.

OK, this becomes clearer and clearer. Indeed, I have a set of messages repeating themselves with that particular error, making the log file very very long. The module that these seem to be associated with is XuiMod, though XposedBridge is mentioned there too. I suppose I should disable XuiMod and see whether those errors in the log clear. Yes?
 

claytonjn

Senior Member
Nov 3, 2011
1,561
836
claytonjamesphotography.webs.com
OK, this becomes clearer and clearer. Indeed, I have a set of messages repeating themselves with that particular error, making the log file very very long. The module that these seem to be associated with is XuiMod, though XposedBridge is mentioned there too. I suppose I should disable XuiMod and see whether those errors in the log clear. Yes?

Yeah, if you explicitly see XuiMod in the errors start by just disabling that and reboot. Then if the errors go away I would try wiping data for XuiMod and enabling it again. If the errors don't come back after a reboot then it's a particular setting in XuiMod that's incompatible, so once you figure out what that is you could use other features without issue.

This is a little off-topic for this thread though, so if you have any more questions feel free to send me a PM.
 

defim

Senior Member
Feb 18, 2012
2,744
1,487
BootManager 2.0.5 is active and works fine with Xposed 2.6. I look at the log, but the only info I have is since the tonight's nightly reboot. One problem is that after the reboot loop I need to do a full-scale restoration from a backup, so I am not sure any log can survive that. Maybe I can access files in the recovery mode, but never tried that yet. In the current log, I only have some at.dalvik.system.NativeStart.run java.lang.IllegalAccessEception: access to field not allowed, but am not even sure that is even related to the Xposed Framework. I think I'll just try to sit it out, putting off the updates for a while and retrying only right after a complete backup.

BootManager 2.0.5 does nothing together with new Xpose 2.6! You need the newer version. Why? Xposed API changes causes the "IllegalAccessEception" Errors. To fix this, some setAccessible() command are needed for each moule -> only with latest BootManager.
All the other modules which writes these IllegalAccessEception are not compatible with Xposed 2.6 and may crash something, even reboot you phone. Ask in the related threads of the modules
@JamMasterClay: Yes a little off-topic here, but was expected after the short beta time of Xposed 2.6 and a hard cut in the Xposed API which make many modules (invisible for the user) incompatible
 

2_i

Member
May 22, 2013
30
3
BootManager 2.0.5 does nothing together with new Xpose 2.6! You need the newer version. Why? Xposed API changes causes the "IllegalAccessEception" Errors. To fix this, some setAccessible() command are needed for each moule -> only with latest BootManager.

OK, after I disabled XuiMod, error messages disappeared. Wiping data did not help. Reactivated XuiMode still gave rise to the errors, so I disabled it for good. After a full backup, I updated and activated BootManager to 2.0.7, all under Xposed 2.6, and now it works. Thanks a lot for the help.
 
Last edited:

defim

Senior Member
Feb 18, 2012
2,744
1,487
OK, after I disabled XuiMod, error messages disappeared. Wiping data did not help. Reactivated XuiMode still gave rise to the errors, so I disabled it for good. After a full backup, I updated and activated BootManager to 2.0.7, all under Xposed 2.6, and now it works. Thanks a lot for the help.

:good: Thanks for reporting. Please dont forget to report it in the thread of XuiMode (i dont know & use it)
 

sanderg

Senior Member
Aug 17, 2009
342
83
power button stops functioning

With BootManager activated, my power button does not turn off the screen anymore.
HTC One, started with Android 4.4.2, issue remains on 4.4.3. Xposed 2.6.1.
Disabling the BootManager module fixes the issue.
I'm not blocking system stuff.

I searched the thread but could not find a related post.
 

defim

Senior Member
Feb 18, 2012
2,744
1,487
With BootManager activated, my power button does not turn off the screen anymore.
HTC One, started with Android 4.4.2, issue remains on 4.4.3. Xposed 2.6.1.
Disabling the BootManager module fixes the issue.
I'm not blocking system stuff.

I searched the thread but could not find a related post.

Are you really sure that your problem is related to this? Maybe you have blocked an app which handles you power button. Does the problem does also occur if you have enabled this module, but no app is selected (=all are allowed)?
 

HassanM

Senior Member
Aug 29, 2012
1,599
625
@defim

Mate I installed BootManager-activated the module-rebooted...
Seems to be working fine... But now I got BootManager-Donator... I installed it but nothing happens. .. I just get a blank screen when I launch the Donator... To explain u more as to what I get, ive attached a screen shot. .. Plz have a look at it and kindly advise. ..

Thanks in advance....

Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
 

Attachments

  • uploadfromtaptalk1404931514184.jpg
    uploadfromtaptalk1404931514184.jpg
    25.1 KB · Views: 207

defim

Senior Member
Feb 18, 2012
2,744
1,487
@defim

Mate I installed BootManager-activated the module-rebooted...
Seems to be working fine... But now I got BootManager-Donator... I installed it but nothing happens. .. I just get a blank screen when I launch the Donator... To explain u more as to what I get, ive attached a screen shot. .. Plz have a look at it and kindly advise. ..

Thanks in advance....

The "Donator" does unlock the apps BootManager & ReciververStop. So you have to install the both too.
You could see that the Donator-App is detected e.g. in "about" view
 

HassanM

Senior Member
Aug 29, 2012
1,599
625
The "Donator" does unlock the apps BootManager & ReciververStop. So you have to install the both too.
You could see that the Donator-App is detected e.g. in "about" view

Thanks for replying. .. As I mentioned earlier Ive already installed and activated the BootManager module... Now I also installed (as advised) the ReceiverStop as well... Now both of them (BootManager and ReceiverStop) are installed and also activated in the Xposed Installer. ..

Somehow Im still getting the same screen when I launch BootManager-Donator as posted earlier... Same situation....

Plz advise....
Thanks

Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
 

defim

Senior Member
Feb 18, 2012
2,744
1,487
Thanks for replying. .. As I mentioned earlier Ive already installed and activated the BootManager module... Now I also installed (as advised) the ReceiverStop as well... Now both of them (BootManager and ReceiverStop) are installed and also activated in the Xposed Installer. ..

Somehow Im still getting the same screen when I launch BootManager-Donator as posted earlier... Same situation....

Plz advise....
Thanks

Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik

The donator app is a "unlocker" or "key" app. It has no other screen. If BootManager detect that the donator is installed, it switches from "free" to "donator", see it's menu>about
Btw, you don't need ReceiverStop, but the donator unlocks it also
 

HassanM

Senior Member
Aug 29, 2012
1,599
625
The donator app is a "unlocker" or "key" app. It has no other screen. If BootManager detect that the donator is installed, it switches from "free" to "donator", see it's menu>about
Btw, you don't need ReceiverStop, but the donator unlocks it also

Thanks for replying... I have donator installed somehow its still showing as "free"... Attached are the 2 screen shots...

mubypere.jpg
unehusa5.jpg


Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
 

HassanM

Senior Member
Aug 29, 2012
1,599
625
@HassanM: Please try to restart the app, by menu>exit and then start it again. Maybe a reboot is required

Thanks for replying. ... I rebpoted couple of times but unfortunately its the same.... Really frustrating. ...
Plz advise...

Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
 

Top Liked Posts

  • There are no posts matching your filters.
  • 119
    Run only the apps you want at system start.
    With this app modul you could prevent selected apps of running on system startup. Only apps with the permission BOOT_COMPLETED are shown in the list. System apps are marked with an exclamation mark.
    To restrict system apps you have to donate. ReceiverStop accepts this donate key too!

    Important:
    This app needs the Xposed Framework. The framework requires root access for installation. Don't forget to enable the module in Xposed. You can grab it here: Xposed Installer

    Donation:
    • No self-promotion in the app.
    • System apps could also be selected
    • You support this app and further development!
    Website: http://tinyurl.com/p2lsmou
    Play Store: http://tinyurl.com/nfd3ftm
    Xposed Repository: http://tinyurl.com/ogfq3t7
    Changelog: http://tinyurl.com/k75vfbv


    My personal intension to create this app:
    IMHO the best way to prevent apps from beeing executed at sytsem startup is with Xposed - and there was now module/app available. So i created one :)

    Translation:
    You could find here a interface to translate the english strings: http://tinyurl.com/okycacj
    A free account of www.oneskyapp.com is required to edit. Additional, please attach your email address or send it via PM ;)


    Description for non-developers:
    Each app with permission "android.permission.RECEIVE_BOOT_COMPLETED" is placed in a (Windows slang) "startup folder". For my 200 installed apps that are about 33%. On system boot every of these apps gets started. Possible options:
    • app shows a notification
    • app starts a (hidden) service in background
    • app exits again (eg user has set an option)
    If you disable an app in the BootManager it does not get that event and is not started at next system boot.

    ReceiverStop
    An app still starts at system boot? Android has many other events which could start an app!
    Example: Skype has the permission "android.permission.MOUNT_UNMOUNT_FILESYSTEMS". This means, (again Windows slang) if you insert a DVD into you drive, "autorun" is executed and starts Skype.
    Note: As your sd-card is mostly always inserted, this could be used to start apps at system boot....

    Other triggers are: A BlueTooth device (dis-)connect, connection type changes (2g/3g/wlan) or power adapter is (un-)plugged.
    All these could be restriced with my other app "ReceiverStop". Be carefull and do not disable the wrong.
    Btw, ReceiverStop accepts also the donate key of BootManager.
    10
    @NeuDroid: You have other apps by me installed? Some are "patched"? Thats the problem.. All apps by the same developer (exactly with the same certifcate signed) can not have different signatures. Try to uninstall the modified :)
    @[email protected] & @svil3 Yes, I'm working on an update
    4
    @chester.anjan: As nobody complained, it seems :) Nougat support was added some weeks ago
    4
    I use multiple apps made by defim. It's one of the many reasons why I am still on Nougat. I would consider jumping ship and moving to Oreo if these apps by defim got updated.

    Me too. But since LineageOS moved all my devices to Oreo I had little choice if I still want to get updates ;).

    None the less it *is* possible to live without some of the Xposed modules I used. Defims Bootmanager and LightningWall are substitutable. (AFWall+ and AppOpps (mentioned two postings above). While AFWall+ has a supporting Xposed Module, AppOpps is more inconvinient if you do not want to purchase it. (But it is very cheap to buy ;)) You can override the autostart permission. But you have to do it app by app. If you use the payed version, you can sort by permission and add the autostart permission as a sorting option. Then it is quite as good as Boot Manager.

    But I still miss a working ProtectedApps. But Oreo has something now. And there is also a "fork" of Xprivacy (PrivacyLua) aviable.

    It would be really nice of defim[1] if he would clarify from time to time if he is still working on Oreo or if his modules are "dead". Right now it feels like rovos work on Xposed for Nougat and Oreo ;)

    [1] @defim: Please do not confuse it with a request for an ETA! But as a donator I think it would be fair to know if waiting for it is an option. I would rather not use your modules at all if you only continue developing because of your donators. Your software has done a good service for many years and that was much more worth for 10 € that most of the other software I paid for ;). But I would love to switch back to your modules - just because they are easy(er) to use than most other bloated Apps.
    3
    http://forum.xda-developers.com/showthread.php?p=58832262

    Good method for permanent permissive mode on boot. Works well with this module

    Sent from my Nexus 5

    Next release 3.1 does also support enforcing mode