Incompetence has indeed been displayed. Issue was unrelated to Xposted: Twilight overlay (screen filter for eye strain at night) was conflicting with apk installer.
-----
Disclaimer: I am new here and may display incompetence.
Since updating to version 2.6.1 today, I have been unable to install modules (or re-install the old framework). Downloading works fine, unknown sources is enabled, but upon tapping install I am unable to proceed past the permissions list page; tapping "Install" in the bottom right does nothing. The cancel button works fine.
Disabling all modules and rebooting did not solve the problem. Might this be related to the "UI Improvements" in 2.6.1? Is it some other issue?
If it is a UI issue, what would be the best course of action here other than a backup restore (seems like overkill) seeing as I am unable to tap install to downgrade to 2.6?
Running Sense 5 based 4.2.2 ROM on an HTC One X+
Thanks!
Hey folks,
since yesterday I have a serious problem with my Xperia Z3 compact D5803:
After waking up my phone from Stamina it just crashed.
Then it was stuck in a boot loop.
With TWRP I was able to (temporary) fix the boot loop:
- Advanced -> Fix Permission (also SElinux)
- Mount -> System
- Advanced -> File Manager -> Copy build.prop to /system
- Reboot: System
However the system was very laggy, running hot and had a high battery drainage (like 1 percent per minute). In OS Monitor I saw dhd_dpc had around 20% CPU usage (which is related to WiFi), so I disabled WiFi, which fixed these issues.
However after reactivating WiFi system crashed and again stuck in boot loop. And now I can't even fix the boot loop....
So what do the experts say:
a) Is this software or hardware related? (Notice: While the system was laggy, I was still able to download data via WiFi, so the antenna cannot be broken completely)
b) What can I try to fix the boot loop?
c) I guess last resort is factory reset. What else can I try before that?
Thanks!
Anyone?
Unless you say what you actually did to break the device, you're really not going to get much help. Once you own up to what you did to it, perhaps someone can figure out how to fix it.
If you've messed up the ROM, a factory reset isn't going to fix it. You'll need to reflash.
As discussed on IRC, I did nothing on the ROM or the system at all!
However apparently my try on fixing the boot loop, with copying a backup of the build.prop, did in fact broke the boot due to wrong permissions. I was able to fix this with a chmod 0644 on the build.prop.
Now the phone boots fine so far and isn't laggy anymore, however I have still problem with high battery drainage. The phone merely lasts one day...
Under battery usage it is just listing "Android system" as main appliance.
So I hope this is somehow software related and will go with a re-flash. Also then I can use this opportunity to update to 5.1.1 - at least something....
So here is the issue.... I have a droid turbo running Resurrection Remix. I used the aroma installer to slim down the gapps installed and maximize space. All of my apps install just fine except, a game Clash of lords 2. Also i have noticed that in my outlook app i can't press on hyperlinks from emails. Any thoughts?
Im having a hell of a time with random parse errors, permission errors on apps... Narrowed my issue down to cm root option and SU not getting along, happend after flashing beta SuperSU, fixing to full wipe and test drive latest CM 13, I've yet to recover 4G and also my GPS locks when I'm sitting still, but if I travel it gets lost....
I have no proof of this, but this has been happening on my Note 4 (SM-N910T) ever since v13.3, and now on v14.0. I also bought a Huawei Honor 6X about a week ago, it's now happening there too. I didn't feel that this was worth posting about, figuring it might be device-specific or ROM-specific. But now that it's happening on 2 devices I've changed my mind.
Note 4:
Android 7.1.2 (CMRemix)
Xposed unofficial by PurifyOS (system mode)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Honor 6X:
Android 7.1.2 (Resurrection Remix)
Xposed (systemless Magisk version)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Description of the issue:
After powering on/rebooting, I can't open system Settings app for up to a minute or so. It just hangs on a white screen. It then either gives a message stating that Settings isn't responding, or, if I manually close Settings with the Recent button then try to reopen it, it repeats the same behavior but will eventually open. Sometimes I need to access Settings immediately after boot to make changes. Device is otherwise responsive, Magisk appears to work fine.
I have tried clean ROM installs on both devices, with full wipes beforehand, and latest stable Magisk. I've also tried with and without Xposed, results are the same. This didn't happen before v13.3, v11.x and v12.x didn't exhibit this behavior. But back this I was using systemless SuperSU in conjunction with Magisk. I suspect that MagiskSU may be the culprit.
MagiskSU is also noticeably slower (when compared to SuperSU or non-Magisk Phh's Superuser) at responding to SU requests, even with a setting of auto-grant and the lowest possible timeout (10 seconds), and global mount namespace. This may be due to the fact that does more than just rooting, it is logical to assume that it has more background processes running since it is also a systemless framework, whereas the other 2 solutions only manage root access.
Last, my file managers oftentimes won't let me delete/modify certain files/folders in the system partition, with a message like "device or resource busy", or flat-out denying access. System is remounted as RW. This only happens with Magisk, but never with SuperSU or Phh. I do use Magisk for systemless mods, but sometimes I want to make direct midifications to /system. Magisk, as a root solution, shouldn't be denying my ability to do this, since I own my devices, not Magisk.
Right now I'm primarily concerned with the Settings issue, but I figured the other issues are worth mentioning. I'm still on the fence, I may return to SuperSU, or Phh, trying Magisk again after a few more stable releases. But if this can be resolved then I'll give it another chance.
I'm posting the logs for my Honor 6X, one is the Magisk log from /cache, the other is /data/anr/traces.txt. Attempts to get a logcat during boot were unsuccessful.
Thanks for any help!
Magisk saves a log during boot that you might find useful. It's /data/magisk_debug.log. A logcat from when the device has booted up and you're trying to open up the Settings might also be interesting.
Have you tried on a stock ROM? Both those ROMs you're using are related and may have similar ROM specific issues...
dont open setting immediately after reboot. open it after a minute. not really a problem
It is not Magisk problem that cause this problem but it is the rom...i'm also using RR 7.1.2 on bacon and Magisk v14 and have no problem at all but we bacon user does encountered this problem in RR build in July and the devs fixed this on August build....
Sent from my A0001 using Tapatalk
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
AnonVendetta said:
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
Click to expand...
Click to collapse
There have been issues previously, where it seems like it's a Magisk thing but it's really a ROM issue. Some things Magisk does (and it does a few more things than just root your device) can sometimes bring problems out into the light...
I believe bacon refers to the OnePlus One (Nexus devices are all named after aquatic creatures). Looking in the RR thread over in those forums I'd guess you'll find your information somewhere around here: https://forum.xda-developers.com/on...tion-remix-t3507102/post73283623#post73283623
About your logs: I'm not too good at reading logcats, so no help from me there. But, I see something there in your Magisk log... Have you tried disabling Xposed?
There are things going on when a device with Magisk starts, so depending on your setup it might take a short while (30-ish seconds for me on my daily driver) before root requests start being accepted. If the ROM settings require root, that might be the reason why it won't open straight away when booting up your device.
OK, back again, Xposed disabled this time in the app (but still installed), so not active.
Here is the full changelog on the build where the devs fixed the issues on settings freeze/fc on startup....
https://forum.xda-developers.com/showthread.php?p=73304715
Sent from my A0001 using Tapatalk
Hi,
I have a Nokia 7 Plus TA-1046 running official Android Pie 9.0 with September 2018 patch level and build number 00WW_3_22C. The bootloader is unlocked.
Upon booting a patched boot.img using MagiskManager 6.0 canary build with a debug version of Magisk 17.3 canary build as well, the system experiences some system glitches as follows:
1) Vibration intensity for haptic feedback is increased
2) Certain system gestures become unavailable like Lift to check phone or Swipe up from home
3) Double tap to wake becomes unavailable
4) Some other glitches I may have missed
The thing is that as soon as the system is restarted, said glitches disappear and the system returns to normal. The same is also observed even when Direct Install Magisk to the system after achieving root privileges and then uninstalling afterwards. No modules were used nor installed upon testing.
This did not happen back when the system was running Android Oreo 8.1. It seems that having Magisk is causing glitches to this system running Pie, at least on this hardware.
I could not zero in on where the issue may be, so perhaps someone would be able to guide me on troubleshooting this further. I'm attaching the debug logs upon patching the boot.img and booting it subsequently via fastboot.
I could also provide screenies for the missing gestures before and after applying the Magisk patch.
-ianp
EDIT: The XDA labs is having a hard time uploading and attaching a sub 10kb log file to this post, so I am providing a pastebin link to the install and run logs.
Install: https://pastebin.com/ZTAxxG50
Run: https://pastebin.com/15XCZ0Sc