We have a rooted Galaxy S4 Active and its been having some strange issues that I can't figure out.
The phone was recently ( a few weeks ago) wiped completely and flashed to NE3 via odin, then updated following the how-to to OC7.
Everything was fine for a while, and outside of a few default apps on the phone getting updates, no extra software has been installed. But within the last few days, the phone has been freezing/lagging on the lock screen. Its set up to use a pattern lock. If you fail the pattern, the phone sometimes will hang for a really long time before clearing the pattern and allowing you to reenter it. Even after entering the right pattern, the phone still hangs for a bit before actually unlocking. But after this period of time is over, the phone behaves fine, even on the lock screen. It feels like the phone is getting hung up on some process for a time, and then after it recovers everything runs fine. This doesn't seem to happen unless the lock screen is up, however, so seems suspect.
Anyway any ideas?
Hello, check the reply on my post http://forum.xda-developers.com/galaxy-s4-active/help/root-active-s4-i537ucucoc6-t3240300
I'm not sure that helps? The phone is already rooted and running OC7.
The problem is that some of the system settings menus and the lock screen tend to lag a good bit. Sometimes if you enter the wrong pattern in the lock, it will just stay frozen for some time before you can attempt again, other times if you are in the settings menu it will lag between setting screens.
alloraprime said:
I'm not sure that helps? The phone is already rooted and running OC7.
Click to expand...
Click to collapse
First try clearing cache and dalvik, this can be done with flashfire or in stock recovery. If that doesn't help, try flashing Galaxy Mod and see if that improves anything. Finally, are you on stock OC7, or deodexed OC7? Maybe you ought to try the other
Related
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
Weird situation started tonight. Phone is my sons and is completely stock. If i pop the battery out and boot it, i am able to get in from lockscreen and use the phone without issue. If i let the screen timeout or lock it the screen will not respond to touch what so ever essentially locking me out of the phone unless i pop the battery again. Ive tried the basics, hard reset, changing lock screen settings. Any ideas? Even with a reset im leaning towards a software issue as it works fine once i do get in. I appreciate any input, thanks
Had a simular issue mine was caused with an issue regarding superuser permissions and my set cpu enabling when screen timed out. Seemed my cet cpu wasn't getting superuser and wasn't abling my phone to turn on.
Sent from my DROID3 using XDA App
ryfhoff said:
Weird situation started tonight. Phone is my sons and is completely stock. If i pop the battery out and boot it, i am able to get in from lockscreen and use the phone without issue. If i let the screen timeout or lock it the screen will not respond to touch what so ever essentially locking me out of the phone unless i pop the battery again. Ive tried the basics, hard reset, changing lock screen settings. Any ideas? Even with a reset im leaning towards a software issue as it works fine once i do get in. I appreciate any input, thanks
Click to expand...
Click to collapse
Restore using a SBF, if you look under the general tab, probably page 2, look for my fast/easy unbrick. This can be applied to a unbricked device as it restores EVERYTHING back to 5.6.890 (leaves SD cards alone though). That should fix your problem.
So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).
Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?
It may be formatting and encrypting your data partition.
Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.
Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???
frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.
[SOLVED]Screen On Skips Notifications&Time Screen, goes straight toDraw Your Pattern
I need help. So, I did a nandroid backup, then reset and restored the nandroid backup, just to get rid of the tons of gigabytes of junk that i can never find out where it is that all my Android devices tend to clump up over time without me ever knowing why. (I've searched and searched the entire root and every folder and found absolutely nothing but that's not why I've come with questions today. If you have a quick answer on that too it'd also really help though).
Anyway, after the restore, my phone has started doing this weird thing where, when i turn on the screen, whether it's double tap to wake or on button, it shows a short flash of the notifications and time screen and then skips to the "Draw Your Pattern" screen. It's so annoying. I hate always having to unlock the phone just to see what time it is without having to read in the blink of an eye and wonder "wait did i read that right?". It's also made it really annoying because i used to be able to shut up alarms and reminders from the lock screen but now i have to unlock the phone and annoy other people for that much longer (especially when my phone lags).
Also, I've tried putting lock screen on "swipe to unlock" mode, and it works fine that way. The time and notifications show on the lock screen. But i can't just not have a pattern or etc on my phone.
I'm on rooted oxygen OS 3.5.3 with elemental x Kernel (it solved a bunch of Wi-Fi issues i was having with stock kernel). oh, and after the nandroid restore my phone is encrypted... I don't remember if it was or wasn't before. But just now when i forced restarted it for crashing so long and hard it asked me to "draw my pattern to start android" which it had never done before. Thankfully i knew my pattern unlike the other people searching about it online. Oh, and also, when i restored the nandroid backup, it also forgot my pattern and apparently replaced it with some nonsensical one. Seems to be a common bug with restoring from nandroid on twrp according to searches. Thankfully i also had a fingerprint so i was able to use that and then delete the files with the pattern lock and all that stored in the phone so i could set my pattern again. I honestly don't remember if the lock screen skipped to the draw your pattern screen before i deleted the lock screen files and set a new pattern. It was a long while ago and i was so frustrated at the time for having an unknown pattern that i wasn't thinking about whether i was having this issue or not ?. I don't know if any of this has to do with the problem I'm currently having, but i just thought I'd mention them just in case someone notices a correlation.
Thanks so much everybody!
Turns out at Some point i had accidentally flipped on Gravitybox's Direct Unlock feature which skips straight to the security challenge.