• FlippyLevel 6 - Platinum Elite Member

    • Post #707
    • Edited

    Like if I am doing this for a friend [just to remove browser and add apps] and I dont want him to mess around with root access, I can uninstall Magisk right away? its just for doing extra stuff, correct?

      Flippy You'd want to flash back the stock boot.img to remove magisk and the ability to install packages. magisk cannot be removed on its own. A new boot.img would need to be made. It so far hasn't seemed useful. Either want both to have development of a ROM, or neither when a ROM is made for end users.

        neutronscott I'd imagine if some could choose to install apks without flashing a modified root image, they'd go for it as rooting opens the device up to more/deeper attacks w malicious apps (esp w the nature of people just grabbing modified apks off the net for these). But if its the only way, so be it. 🙂

            sappypappy The last sentence of you post is spot on! Although people like [Login to see the link] are posting firmwares with preinstalled apps that don't require any mod boot img

              If you uninstalled chromium, here is a mod launcher and app drawer. To install app drawer, simply install as user. To install launcher you must first uninstall launcher3 then install this as a data app. To be safe you may want to backup stock launcher in case something goes wrong. You can also set button mapper to launch button mapper in case you have no launcher. But i don't think you will have issues.
              [Login to see the link]

                Biden2020prez I put neutronscott 's grab in /data/local/tmp and with the MacroDroid app created boot up as a trigger for:

                cd /data/local/tmp
                nohup /data/local/tmp/grab /dev/input/event1 &

                and now on bootup Quickdial is remapped to toggle virtual mouse

                      sappypappy To unlock the Package Manager we set a SystemProperty during boot initialization using resetprop provided by magisk. The other way to do this is modifying the fairly big super image. This is because Android 11 doesn't read .rc files during the boot ramdisk.

                      Another option is building a binary like Magisk that only does that one thing. I don't see the utility to do this myself unfortunately.

                          • NNECLevel 1 - Junior Member

                            • Post #716
                            • Edited

                            dovwcom under what action catagory do i set this? never mind i figured it out! thanks!

                                after over 600 posts it gets a little confusing for somone that wasnt following the whole conversation. would it be possible that someone can come out with so to speak a "verdict" of what can be done and how?

                                  neutronscott Thanks. Yeah, the workarounds would prob be worse than the boot img way. If it could be enabled via ADB somehow before each apk install, but I don't think that's possible.

                                    Biden2020prez NEC I thought it was better because after reboot toggling is a simple one press with Quickdial - but Quickdial is not very reachable and the nohup shell script sometimes stops and so it's both better and cleaner to use button mapper to set one trigger for enabling mouse and another to disable as suggested on this thread

                                    • NEC replied to this.

                                          I successfully paired and used a Bluetooth keyboard-mouse combo (it has a touchpad).
                                          What's interesting to note, is that although it takes over the system mouse, meaning, if the mouse had already been activated, then the touchpad just controlled that cursor, it has a much broader range. Meaning, it can reach till the top of the screen.

                                            • NNECLevel 1 - Junior Member

                                              • Post #724

                                              dovwcom do i need to download a separate button mapper or will i be able to set it in macrodroid?

                                                  NEC You can set macro droid to launch mouse when you open certain apps, but i preferred the button thing.

                                                      NEC Biden2020prez when I used grab and the shell script for it I didn't need to use button mapper at all and I set bootup as the trigger for my script which was much more practical for me than using an app as a trigger - not using button mapper was initially an advantage because I couldn't get button mapper to work without installing a4f's Voice Assistant because there were missing accessibility settings without it so there's a potential bloat and battery hit if you're not interested in running the Voice Assistant otherwise (Edit: I now see that you can use [Login to see the link] 's accessibility [Login to see the link] with a-one 's permissions).

                                                      As above in practice I found the Quickdial solution difficult - especially when reaching to the back of the phone wasn't possible when it was mounted in my car to use for Waze. As far as using the Favorites star button with event2 in [Login to see the link]'s script for whatever reason that would only toggle once and then not work any more for me.

                                                      I especially found the Change Resolution app to be a game changer in using apps on the phone (use with care - at one point I mistakenly set the resolution backwards and my phone became totally unusable with the default Launcher launcher3 constantly crashing even after reboots and uninstalling the resolution changer did not help at all - I only managed to eventually rescue my phone by using adb to set the screen resolution to a valid size) so that I use the notification area to switch between a default of 240x320 for phone calls and 321x428 for app use (including texting - for which I use Textra with Microsoft swiftkey - EDIT: MS swiftkey disables secret codes so removed it and at same time removed Textra also because it needed mouse toggling in middle of use - for me that's not worth the hassle) when I want to use the launcher list apps such as Waze and not only are some of the otherwise unavailable settings now reachable but the apps become much more usable - especially Waze and not to mention button mapper and Microsoft swiftkey the last of which I installed because I don't like kt9 especially not the limited version of it on the t408dl and without the screen resolution app MS swiftkey is otherwise completely unusable.