So here's a new one, a keyguard/lockscreen missing problem - Sprint Samsung Galaxy Note 3

OK, here's the situation. sometime last night my phone decided it was going to play a late April fool's joke on me. I had set it down, and the screen timed out as usual. Only when I hit the power button again, it came right back to the home screen instead of the lock screen. Granted I only have it set to swipe, but that's beside the point (I think). I thought it's been a while since I rebooted, maybe that'll help. When it came back up, straight to the home screen again, only this time was way interesting! Not only did the lock screen get skipped, I had no haptic feedback like usual, the home button wasn't working for short press or long press, and with it plugged in and notifications waiting turning the screen off by the power button didn't do anything as far as the notification light.
Now here's the kicker: DOUBLE pressing the home button and bringing up the s-voice actually worked, and after that everything else worked too! Only thing is the problem comes back after every reboot so far. Oh and I've lost the ability to write to the external SD card. I've even tried reauthorizing it, no joy.
Anybody got any ideas about what I could try? If not, at least I hope I made some of you start or end the day with a chuckle and a solid Wtf? ?
My next step is gonna be clearing the dalvik/art from twrp.. Worst case scenario I factory reset and restore my week old backup..
I'm running stock rooted 5.0 with ph1 as my latest update. And if somebody is interested enough to want a logcat from boot to couple minutes in, I'll reboot now, capture the log and post it in a few.
Confused but amused,
I am
The Dude

The log.. I had Logcat Extreme running at info priority, and stopped it after around 8 minutes and just under 22,000 lines. Is that a lot? It seems like a lot. There are a couple power button hits, a menu and a back button press, and also at the end is where I double pressed home and got things back to normal..
Yes, I use xposed, minminguard, unbeloved hosts, and lucky patcher. You'll see them in the log, as well as my Wi-Fi ssid.. I dunno what else might be in there.. Hopefully nothing juicy though. Lol
If there's a way to filter stuff out, or just log the important things let me know and I'll give it another go.

Related

[Q] NT not waking up from sleep without a reboot.

I've had this problem with both a rooted tablet with an extra launcher ontop of the B&N one, and now that I've put CM7 Final on it. Basically, it'll go to sleep after not being used for a few minutes, and then when I try to get it back on, it won't come back. The N button, or the power button, neither works, and I have to hard reboot it (hold the power button a while) to get back into it.
It doesn't happen every time, there doesn't even seem to be any rhyme or reason towards why it happens. Sometimes it'll just be sitting on the desktop when it happens, other times I'll have had a book open when it happens. Other times, it will come right back as soon as I push a button.
It's getting really frustrating, honestly. Is there any way to prevent this?
There's been some discussion of this (SOD = Sleep of Death) in the CM7 threads. You should look there for more info. I think searching for "wakelock" will find you what you need... I think that's what it's called. It's an interim fix.
I have been seeing this same thing. I originally thought it was something I loaded so completely unrooted it and let it run for a bit and rerooted it to find it is now doing it again. will look into what CRE mentioned
Only real thing I can find doing a lot of searching and reading is this ...
http://forum.xda-developers.com/showpost.php?p=23410167&postcount=103
Wake Lock app
Yeah, im having the same problem! It happens for me everytime. Im going to install that Wake Lock App tonight, see if it helps... my only concern is that will it drain battery life?
cheers steve
Weird as hell. Mine has not done this for a few days now. I do notice it happens when my WiFi is acting up.
last time it happened to me I had it sitting on the charger while I slept and I had left the wifi enabled.
I wonder if this is something to to do with the wifi sleep policy. I know on my android phone there is an advanced settings to access this.
any more issues with this? I have since been making sure to keep my wifi off when not in use, but I did have this happen once again when the battery was below 30% and sitting idle for a while.
I've had a similar issue where I need to hit the power button two or three times to get it to boot up on my CM7 Final internal build and I can't change the "go to sleep" settiing.
Posted from Spaceball One
apart from finding that Wake Lock app... Has anyone found a more permanent fix for the SOD issue?
I tried this and it seems to have worked as I haven't had the problem since I made this change.
Go to: Settings>Wireless & networks>Wi-Fi Settings. When you are in the Wi-Fi Settings screen, touch the Menu button in the status bar. It will bring up a dialog box. Select "Advanced" and on the Advanced screen touch Wi-Fi Sleep policy. That will pop up another dialog box and you select the "Never" radio button.

In stock image "Gallery", when zooming a pic, screen goes black

In stock image "Gallery", when zooming a pic, screen goes black .
After the ICS update, the image gallery also suffered a problem. Sometimes while viewing a pic and you double tap to zoom in, suddenly the screen goes black...no pic. Start to zoom back out and the image comes back..zoom in again..image black screen again. This happens with random pics and wont fix itself unless you Force Stop the app in Control panel. It wont always be the same pics..anyone else get this? Its not important, I just wondered if this is just something on my phone..
After updating to the OTA, everyone has problems until they do a factory reset. It clears out all the GB crap that messes it up.
Backup your data and then power off your phone. Take out the battery and put it back in. Then press power and volume down until you see he white screen. Use the volume keys to highlight and power to select "factory reset".
Forgot I wrote this, sorry. Already did a reset long ago as per suggestions by others for other problems since the update. So the problem never fixed itself. Its some crap with ICS. Its annoying because now I keep getting this problem.
Has anyone else experienced this before?
Ok..obviously nobody knows about this. I'm going to take a short video and i'll have it up within a couple days. This photo browser is pissing me off! Is there a better or just as good (FREE) app out there in the market or on XDA? Something that doesnt have this bullsh** problem in it? Thanks ahead of time for any replies.

[Q] Wake issue during phone calls

I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.

[Q] Samsung Note 3 Lollipop Issues (Sprint Stock Build)

So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
jcohenlv said:
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
Click to expand...
Click to collapse
I can't say I had any problems like this. I was running Stock rooted OC5 for a while and had really no problems with it. I didn't have any pattern or pin unlock though, so maybe it would have been different? I would have stayed stock but my Flashaholic took hold and made to start trying out other ROMs.
As for rooting, I have found it very easy to root this phone. I haven't had a problem either using auto-root or flashing superSU.
Factory reset is easy.
w7excursion said:
Factory reset is easy.
Click to expand...
Click to collapse
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
jdelano said:
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
Click to expand...
Click to collapse
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
jcohenlv said:
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
Click to expand...
Click to collapse
Glad to hear that, I hope it stays that way
You should read more before trying to root

S6 won't respond then will, just received it today.

Today I got my phone in. I was on the first set up page and it wouldn't respond to any of my touches. The buttons would glow like I was touching them but it wouldn't type or input. I soft reset it. It worked when I used assist touch. I hard reset it, wiped cache and factory reset. It fixed and I installed all my apps and when I plugged it into the charger it stopped working again. I can open the camera by double pressing the home button to unlock my phone but i can't open anything. It will glow like I'm pressing it but it won't open. I can pull down my notifications bar but none of my toggles or setting icon will work, again, they will glow just not open. I came back to my room and randomly it was working again, after 5 mins it stopped again.
Thank you for your attention.
ATT 64 GB
Galaxy S6 (not edge)
I don't know if this is the cause/solution to your problem, but I know S Voice can cause lag issues. By default, double pressing the home button (when device is unlocked) opens the S Voice. Frankly, it's redundant and pointless, as it's a mediocre attempt at Google Now. Open it, then go into the settings, and disable it. It causes lag because it's waiting to see if you're going to press it again or not.
But if that doesn't fix it, and it's doing that stuff before you've even set it up, I'd tend to think you've got a faulty unit. The capacitive buttons are part of the screen/digitizer, so maybe you've got a bum one.

Categories

Resources