Database Users

[Q] SystemUI crashes on phone calls

i am having this issue with receiving and making calls, the moment the screen is on, SystemUI will crash and reload.
The proximity sensor does not work after this, and i end up touching stuff with my cheek while talking.
I do have my doubts on xpose module S5 SystemUI Theme, but it all started randomly...
anyone having the same issue?
My Note 3 runs with Stock NG2, LeanKernel 3.6 and latest PhilZ CWM.

Yes! I have this issue as well. Not for outbound, but only for inbound. I use the Samsung flip cover, so I did not notice about the proximity sensor, but I just gave it a test and it shows identical behaviour. When receiving a call when screen is off, there is no problem at all, proximity also works.
I do not have the S5 SystemUI theme, and never used it.
Can't remember what I changed that could actually cause this. I have the following config:
Stock XXUEND3 (Latest PHN - The Netherlands firmware available)
Rooted with CF Autoroot
Running Ultimate Kernel v54 (but I had the issue already running stock kernel)
Connected with Gear 2
Frozen some Samsung bloatware with Titanium Backup
So I am following this thread!
Gerco

Well that's weird, Greenify keeps telling me it has problems hibernating com.sec.android.sviewcover, which i've disabled since i dont have one.
PS, to confirm your findings, i too had problems on stock kernel (*NG2 SEE) and i did wipe a lot of APK's, but most of them are non-samsung, i prefer RW rights over /system above scripting and debloating apps.
Do you by any chance have Xposed installed? if yes, what modules?
I've enabled the physical buttons for picking up and ending a call, if it wasnt up to them, i'd have to wait until the process re-opens so i can slide the thing...this is getting really annoying

I do have the Xposed framework loaded, with only Wanam Xposed active. I'll try to disable/remove Xposed and see if that makes things better.
<edit> Nope... Did not fix it... </edit>

Solved? I've this problem also with Galaxy S4 (I9505), i've disable Xposed, clean systemUI data, flash a stock rom (without wipe data)... still crash.

Had to wipe everything as i remember. The issue never came back.

PlutoDelic said:
Had to wipe everything as i remember. The issue never came back.
Click to expand...
Click to collapse
Thanks
Inviato dal mio GT-I9505 utilizzando Tapatalk

For me it worked again after I flashed a ROM update that became available for my region.
Sent from my SM-N9005 using XDA Free mobile app

Random reboot with lollipop 5.1

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.

Greetings.
Have you tried using any other kernel, eg. franco kernel?

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)

Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app

killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.

This does not happen at all to me(using stock 5.1 with Franco Kernel).

This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.

_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).

Your battery is dying, I've been getting the same problem until I replaced the battery today.

richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?

I've been getting the same issues on my N7 since updating.

regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....

ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.

gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.

_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks

I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.

Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng

gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.

I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk

Viper4android not working [LP]

Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance

This is what driver status says...
Btw im on lp 30b with stock kernel

I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you

Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you [emoji14]
Click to expand...
Click to collapse
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.

Alleks1802 said:
Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance
Click to expand...
Click to collapse
Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you
Click to expand...
Click to collapse
droidfan88 said:
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.
Click to expand...
Click to collapse
Check my guide for poweramp and v4a, it might just be the thing to fix it.

Thanks man. It turned out that somehow my selinux had become enforcing. Changed it to permissive and things work as expected.

Check ,,Use ,,NuPlayer'' '' in developer setting.
And install SELinux Enabler script via recovery : http://blastagator.ddns.net/dorimanx.php

I've had enough with the OS freezing on me, any ideas ?

Since I rooted my note 4, I have been having random freezes and it is frustrating. I installed SimplROM, Revolution, Note 5 Port ( Kyubi or something ) and finally a stock rooted rom ( bare developer's edition ) and my phone is the whole time freezing on me. I don't use social media so I am not having background heavy tasks running, always fully erased the phone's internal memory and cache before installing a new rom and yet I still get the crashes. I hve never had that before I rooted the phone. anyone experiencing this as well ?
my phone is a N910F

stilkus said:
Since I rooted my note 4, I have been having random freezes and it is frustrating. I installed SimplROM, Revolution, Note 5 Port ( Kyubi or something ) and finally a stock rooted rom ( bare developer's edition ) and my phone is the whole time freezing on me. I don't use social media so I am not having background heavy tasks running, always fully erased the phone's internal memory and cache before installing a new rom and yet I still get the crashes. I hve never had that before I rooted the phone. anyone experiencing this as well ?
my phone is a N910F
Click to expand...
Click to collapse
I am having the same problem, lagging all 5 sec when typing or swiping on homescreen. It just happens on Touchwiz roms. The Fingerprintsensor aint working either. I tried Stock Roms, Custom Roms.
Somebody said that they fixed it on the 910T with a puerto rico stockrom but no fix for 910F.
I just installed CM12.1 and no lag.
Waiting for marshmallow for fingerprintsensor support.
Hope i could help.

Akuma360 said:
I am having the same problem, lagging all 5 sec when typing or swiping on homescreen. It just happens on Touchwiz roms. The Fingerprintsensor aint working either. I tried Stock Roms, Custom Roms.
Somebody said that they fixed it on the 910T with a puerto rico stockrom but no fix for 910F.
I just installed CM12.1 and no lag.
Waiting for marshmallow for fingerprintsensor support.
Hope i could help.
Click to expand...
Click to collapse
Mine is actually working fine and it freezes without warning or in other words I can't point out exactly when it freezes, like sometimes the camera, drop down notification bar or even the task switcher. It is random, I tried yesterday some solution which I'm not sure exactly of it's outcome but so far no freezes. I changed the securestorage value in the build.prop to false which resulted in loosing my wireless password but after I retyped it again things were fine.

stilkus said:
Mine is actually working fine and it freezes without warning or in other words I can't point out exactly when it freezes, like sometimes the camera, drop down notification bar or even the task switcher. It is random, I tried yesterday some solution which I'm not sure exactly of it's outcome but so far no freezes. I changed the securestorage value in the build.prop to false which resulted in loosing my wireless password but after I retyped it again things were fine.
Click to expand...
Click to collapse
Hi,
souns like the S-Health and Privatemode error.
you fixed it with that method. You could also use the xposed module for S-Health to fix it.

Akuma360 said:
Hi,
souns like the S-Health and Privatemode error.
you fixed it with that method. You could also use the xposed module for S-Health to fix it.
Click to expand...
Click to collapse
could you please elbarate more with this xposed module fix ?

App Running on the Background Bug

For some reason an app, Clash Royale, for example, the one I where I encounter this problem commonly, sometimes still plays its music even when I am not using the app itself (using web, facebook, etc.). Does anyone here encounter this? I am running the latest version of stock with no root. Just worried that this might cause unintentional battery drain.
I did root before with the hope of fixing my Wi-fi battery drain problem through debloating. Finding out that debloating does not fix my problem, I went and downgraded my firmware to a lower version using files from sammobile hoping that the latest version was what was causing the problem. That still did not work unfortunately so I decided to just live with it (until I see what happens when I upgrade to Nougat) and go back to the latest firmware using the OTA Update. Pretty sure I did everything the right way but is there some chance that I kind of failed flashing in some way causing this to happen? I don't really remember if this actually happened before I rooted and I am not sure if its just a bug in the current version of the firmware.

Use greenify bro... It works with unrooted phones too... Use it to hibernate your unused app which sometimes running in the background....
Sent from my SM-G935F using Tapatalk