Database Users

Very odd issue?

Recently every couple hours the phone runs at like 2fps. All animations run about that speed but don't freeze. It also causes my soft keys to stop vibrating on touch and accelerometer locks. Any ideas?
Sent from my MB520 using xda premium

zachthepack said:
Recently every couple hours the phone runs at like 2fps. All animations run about that speed but don't freeze. It also causes my soft keys to stop vibrating on touch and accelerometer locks. Any ideas?
Sent from my MB520 using xda premium
Click to expand...
Click to collapse
What rom are you using?
There is maybe somthing running in the backgroud which does that!

I wondered that but nothing was ever in the runnin list but nothing I stopped helped. If it keeps up I suppose i'll factory reset and then possibly sbf. On cm7. Flashin new nightly over didn't help. We will see.
Sent from my MB520 using xda premium

Im running cm7 nightly now and not having any issues at all. does it happen at any certain time or after you use a certain app or something?

Usually happens after I wake the phone after a couple hours. Seems to have gone though.
Sent from my MB520 using xda premium

I would say if it keeps up maybe try factory reset then if that don't help a sbf might be in order.
Sent from my MB520 using xda premium

zachthepack said:
I wondered that but nothing was ever in the runnin list but nothing I stopped helped. If it keeps up I suppose i'll factory reset and then possibly sbf. On cm7. Flashin new nightly over didn't help. We will see.
Sent from my MB520 using xda premium
Click to expand...
Click to collapse
Did you manage to get it fix?

I uninstalled go sms and friendcaster(most recent installed) and it hasn't happened since. Weird. We'll see if it fixed it otherwise i'll just sbf.
Sent from my MB520 using xda premium

zachthepack said:
I uninstalled go sms and friendcaster(most recent installed) and it hasn't happened since. Weird. We'll see if it fixed it otherwise i'll just sbf.
Sent from my MB520 using xda premium
Click to expand...
Click to collapse
I use gosms myself and haven't had any issues like the ones you've been experiencing. Never used friendcaster.

After a whole day it finally happened again! Oh well will flash sbf once we get outta hospital.
Sent from my MB520 using xda premium

What are you overclock settings?

1ghz on demand. Trying fiddling with it while it was acting up to no avail. Not trying to be lazy I just am curious what happened. Going home tomorrow. Will flash. Hope its not hardware.
Sent from my MB520 using xda premium

marquae11 said:
What are you overclock settings?
Click to expand...
Click to collapse
1100mhz (1.1 GHZ) smartass!

[Q] Anyone else having these issues?

This just started happening the other day. Randomly during the day it will not allow me to adjust the volume ( ie from vibrate to loud). The status bar moves when i move them but it doesn't actually do anything. Also when this starts happening, voice input no longer works. I cant do voice text voice searches etc etc.
I have to shut it down and restart it, then everything will work again. But it only lasts for a few hours and then i have to do it again.
I am stock and not rooted.
Thoughts?

It doesn't happen to me on my modded and tweaked Slim Bean Beta2. I would recommend doing a factory reset and see if that fixes your problem.
Sent from my Nexus 4 using xda premium

Maybe you have apps installed that control or manage audio
Sent from my GT-I9300 using xda premium

android88 said:
It doesn't happen to me on my modded and tweaked Slim Bean Beta2. I would recommend doing a factory reset and see if that fixes your problem.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Could i use this backup utility found here http://forum.xda-developers.com/showthread.php?p=36499906
factory reset my phone and then install that backup or would that defeat the purpose of resetting it.
I am not a pro at this obviously, i just do not want to lose all my apps and settings i have. Or would they just reinstall once i linked the phone back to my google account?

Benconquerer said:
Maybe you have apps installed that control or manage audio
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I did have one, but i uninstalled it and still having the same issues.

I'm having the same issue, stock ROM rooted with franco kernel.
Not only that, but the volume gets very low almost inaudible and I end up having to reboot the phone.
I don't have any audio apps installed, noticed this while watching YouTube.
Thus far have not found a solution
Sent from my Nexus 4 using xda app-developers app

now it is not happening anymore and hasn't happened since Saturday.
Weird.
Will repost later if it starts acting up again.

MF9 ramdom reboots

Ok so I have a problem I am pure stock never rooted my S4 and after I took the MF9 update my phone will get stuck in a bootloop untill I turn on wifi or airplane mode as soon as I connect to data it will happen again reboot I flashed the MDL modem and firmware through odin and it stops it will let me be on data with no problems but as soon as I go back to MF9 same problems happen. Is anyone else having this problem and is there a fix
Sent from my SPH-L720 using xda app-developers app

budde2 said:
Ok so I have a problem I am pure stock never rooted my S4 and after I took the MF9 update my phone will get stuck in a bootloop untill I turn on wifi or airplane mode as soon as I connect to data it will happen again reboot I flashed the MDL modem and firmware through odin and it stops it will let me be on data with no problems but as soon as I go back to MF9 same problems happen. Is anyone else having this problem and is there a fix
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Sounds like it is time for a call to Sprint and make them fix it. What I would do if not rooted.

CCallahan said:
Sounds like it is time for a call to Sprint and make them fix it. What I would do if not rooted.
Click to expand...
Click to collapse
Whats wven more messed up is I have had 3 replacement phones and everyone has this problem i wonder if because the network is so unstable in my area right now if that could cause this to happen?
Sent from my SPH-L720 using xda app-developers app

budde2 said:
Whats wven more messed up is I have had 3 replacement phones and everyone has this problem i wonder if because the network is so unstable in my area right now if that could cause this to happen?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
If your network was unstable you wouldnt be able to get any signal at all but it wouldnt make your phone reboot. Have you tried factory reseting your phone??
Sent from my SPH-L720

ROMANTiC KiD said:
If your network was unstable you wouldnt be able to get any signal at all but it wouldnt make your phone reboot. Have you tried factory reseting your phone??
Sent from my SPH-L720
Click to expand...
Click to collapse
Yeah several times just did one and as soon as it connects to data it reboots. Damn I hate this ****
Sent from my SPH-L720 using xda app-developers app

Whatever is going on its in the kernel i flashed the MDB kernel and everything is working perfectly the only problem im having know is my phone says custom software.
Sent from my SPH-L720 using xda app-developers app

Dude you ain't the only one. The MF9 update has been a major pain the @$$ for a lottt of people. I wonder if Sprint is working on a new update. Hopefully push it out before the end of September. Although I am really liking MF9, I am probably in the minority. My device is smooth as hell and great battery life. Just yesterday I went 20hrs with 3hrs of on screen time!

Im having a similar problem. Random reboots when data is connected. I first thought it was the connection in my area that was causing the problem to (NV just started in Cleveland) until I encountered reboots while on WiFi. It doesn't matter what app I'm using as long is it uses the internet connection my phone may freeze vibrate two to three times then reboot. I even reapplied the MF9 update and the same problem exist.
I'm completely stock!
Thank You Based God!

Joe0113 said:
Dude you ain't the only one. The MF9 update has been a major pain the @$$ for a lottt of people. I wonder if Sprint is working on a new update. Hopefully push it out before the end of September. Although I am really liking MF9, I am probably in the minority. My device is smooth as hell and great battery life. Just yesterday I went 20hrs with 3hrs of on screen time!
Click to expand...
Click to collapse
We must be lucky. I keep reading about all these issues, but MF9 had been awesome for me. Not a single problem, and definitely much better than MDL.
Sent from my SPH-L720 using xda premium

maxpower7 said:
We must be lucky. I keep reading about all these issues, but MF9 had been awesome for me. Not a single problem, and definitely much better than MDL.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
+1 on that. Been on MF9 stock rooted since I got the phone a couple weeks ago and all has been well. I wonder if it could be a hardware issue mixed with something thats in the MF9 update. Sound crazy to anyone?
Sent from my SPH-L720 using xda premium

Yeah it looks like it is for sure the MF9 kernel I flashed mdl kernel and everything is good on that kernel. As soon as I odin mf9 and connect to data it happens again thanks for all the responses
Sent from my SPH-L720 using xda app-developers app

MF9 has given me one reboot so far. Battery life is way better than previously.
Sent from my SPH-L720 using Tapatalk 4

tenaciousj said:
MF9 has given me one reboot so far. Battery life is way better than previously.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
Yeah its seems my problem is isolated. I cant find anyone other than 1-2 other people with this problem. I am back on MDL and everything is working perfect. I get my new device on fri I hope it has no problems
Sent from my SPH-L720 using xda app-developers app

Check your source for the MF9 kernel you have and try downloading and installing a different one.

budde2 said:
Yeah its seems my problem is isolated. I cant find anyone other than 1-2 other people with this problem. I am back on MDL and everything is working perfect. I get my new device on fri I hope it has no problems
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
+1 I went back to MDC. Let it update to MDL then let it update to MF9. Same issue. So I just Odined MDL and left it alone.
Thank You Based God!

amwworks said:
+1 I went back to MDC. Let it update to MDL then let it update to MF9. Same issue. So I just Odined MDL and left it alone.
Thank You Based God!
Click to expand...
Click to collapse
That's what I did si mdl works perfect. I will have a new phone hopefully today or Monday
Sent from my SPH-L720 using xda app-developers app

Ok so I go a new device a brand new S4 and still this one does the same **** what the **** is going on this is the 4th one I give up
Sent from my SPH-L720 using xda app-developers app

Lock screen and Knock On Solution

Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.

It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.

So the knock on feature is supposed to be more reliable if I do this?

in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.

Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!

in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.

Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app

dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.

Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app

Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....

Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app

Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app

Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks

I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app

I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4

Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app

wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.

jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.

episodes of screen unresponsiveness after updating to kitkat

Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.

nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
Hello, I have been experiencing moments of "freezing" or unresponsiveness as well.
For me, it seemed to be due to chrome or using power saving mode. (People in another forum were blaming their droid maxxs freezing problem on chrome) I disabled chrome and disabled power saving mode.
Then I started using opera. I experienced another moment of unresponsiveness using opera without the power saving mode.
I was thinking back to the first times that it happened and it seemed to be paired to the wifi download and upload symbol being active in upload and download activity.
I know that correlation does not mean causation, but I think it is worth exploring if the network activity is causing it to somehow hang.
This bizzar occurance made me perform a factory wipe leading to another round of issues involving processing err_0000, but that is another story; sadly, it didn't even fix the issue.
OP, are you still experiencing the moments of unresponsiveness? If you are, have you noticed the events that are correlated with the event?
Has anybody else experienced this or found a remedy?
It could be one of the apps from the play store that is not playing nice with kitkat, but due to the multitude of other issues, I'd say it is a kitkat or touchwiz flaw.
Thanks for any help.
Lago

nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
I had an issue with screen not responding sometimes .....I figured out it was due to the flip case (original by Samsung). Although lately I haven't experienced that either.
Try using the original non flip case and see if you still have the issue.
Sent from my SM-N9005 using XDA Premium 4 mobile app

pac-mannan said:
Try using the original non flip case and see if you still have the issue.
Click to expand...
Click to collapse
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app

lagoboss said:
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app

pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If your phone isnt hanging up and freezing, that gives me hope. I'll gsm reset, clear the cache and then flash.
Thanks
Sent from my SM-N900 using xda app-developers app

pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just cleared the cache, factory wiped, and installed the Russian update N900XXUDNC4 and so far, the phone is a lot smoother. No hangups in the browser yet, but time will tell lol.
It is annoying setting up the phone like new lol. I'll update the post as to if I have moments of freezing or the screen becoming unresponsive.
Sent from my SM-N900 using xda app-developers app

Cheers mate..do tell me how the battery is..if its good I might flash Russian as well ,currently have but flashed
Sent from my SM-N9005 using XDA Premium 4 mobile app

Had this problem too, as well as lots of lag. Reflashed and did a factory reset. Took care of both.
Sent from my SM-N900W8 using xda app-developers app

Battery life is looking good. Power Saving off, bluetooth on and connected to my smart watch.
I made one short call. I don't talk on the phone that much. I mostly use it for Internet browsing, music, and instant messaging/texting. I'll update on Tuesday when I have a full day at school.
Keep in mind though that the n9005 is the lte version. I have a n900, the non lte international variant; our battery life may be different.
Edit: 4/20/2014 same charge 70% 1 day 6 hours bluetooth, wifi, gps, and 1 Gmail account in sync.
Sent from my SM-N900 using xda app-developers app

Even I experienced the same. My phone came with Kitkat installed. Freezing happens when a webpage is loading or the time i turn on Sync etc. strange thing is phone seems smooter when power save mode turned on.

I think it may be a problem that was not fixed until the March 31st 2014 KitKat build. I have been using Chrome heavily since I installed the most recent official rom; I have not experienced any lag or hanging system wide or in the browser. It reminds me of 4.3.
When I wiped and reinstalled the previous rom, I noticed the lag and unresponsiveness right away.
I'm going to use the browser heavily next week. If I have no issues, I think it may be safe to say that the bug was fixed in the latest kitkat with March 31st 2014 build date.
People with lag, do you have the lte variant or the regular SM-N900? I'm starting to think only the SM-N900 are being impacted by sour Sammy updates.
And if you guys wipe your phones, make sure to turn reactivation lock off because it could cause an error that will not recognize your real Sammy account and password. This phone has become stressful; I'm not updating it again lol
Sent from my SM-N900 using xda app-developers app

I just experienced another moment of unresponsiveness using the google search box within the chrome app running DNC4 :/ Going to try the latest Russian KitKat
Sent from my SM-N900 using XDA Free mobile app