I am occasionally having an issue where the System UI stops responding and I have to reboot the phone, I've attached a logcat
Related
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 I was messing around with the developer settings and turned on "Force RTL layout direction". This caused my phone to crash and for the error message to pop up "Unfortunately, system UI has stopped". I have tried rebooting multiple times and clearing the cache as some suggested but this doesn't seem to work. I was wondering if there are any other options instead of a factory reboot and if not, can I backup my phone from the recovery mode or using a USB connected to my laptop. Thanks!
see here:
PSA: Do not enable force RTL Layout in 5.1
http://forum.xda-developers.com/droid-turbo/general/psa-enable-force-rtl-layout-5-1-t3149244
on the last page is a solution that worked for someone, but most have to do a factory reset.
First time after updating the binary file system was crash and not run at all. After I reinstall system, some time ago I was rotted it and install SuperSU, it's again says "бинарный файл требует обновления" so I update it and after system is launch but there is many bugs happaned. First, after that phone became selfreboot sometimes without my permission. Second, it's... discharging... when it's connected to a charger. Third, some icons on the main screen became to dessapiar sometimes. 4th it's often writes that some app has ben stopped. Can I back the old binary file? I don't have much time to reinstall the system again
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
(system SurfaceFlinger : Attempt to update InputPolicyFlags without permission ACCESS_SURFACE_FLINGER)
It apears to be trigered by hwcomposer process accesing to surface flinger as system user without SURFACE_FLINGER permission being declared on the rom.
To reproduce install this app then you will see hw composer errors whe it updates.
Logcat Reader Professional - Apps on Google Play
Android's most advanced log reader
play.google.com
Also can scrooll arround in launcher with adb logcat.
I tracked the bug downloading A12 surfaceflinger impl and tracing binder calls and results that hwcomposer is runing as user system (ps -Af) which doesn't have surface sflinger specific permission, it needs to run as graphics user, that's the one with that permission (/system/etc/permission/platform.xml)