anyone else experiencing this?
it takes my phone a good 2-2.5 seconds to wake up (screen to turn on) after i press the home button.
is this normal?
Which firmware? And are you running a custom lockscreen? It might also happen if you are running lots of apps (But I am guessing)
i'm using a korean anycall m110s on firmware dh19.
no custom lock screen and the only app running in task manager is launcher pro.
mines about half a second regardless of running apps, on JM1
steveohan said:
anyone else experiencing this?
it takes my phone a good 2-2.5 seconds to wake up (screen to turn on) after i press the home button.
is this normal?
Click to expand...
Click to collapse
Not normal, but it happens to me sometimes as well. Sometimes it takes so long for the screen to accept input that the phone goes back to sleep before I can enter my passphrase on the lockscreen!
I suspect most of the time it's probably some poorly written widget that's updating itself or the like. Check your widgets and see if any of them (like Beautiful Widgets) have a "refresh data on wakeup" type setting that may be keeping the system busy while waking the screen.
Try removing all widgets and adding back one by one after you see that the last one added doesn't cause the problem.
I've also noticed that with certain music playing apps running, the system is often very difficult to wake up.
did you try turning off media scanning?
it makes a hell lot of a difference
i've tried all suggestions and still no luck....
i have no idea what's causing this. my other friends who have galaxy's dont have this problem.
any recommendations??
as a quick update: with the music app running w/ music playing, there is zero lag when waking up the phone via the home button...
is there a solution to this?
I'm experiencing the same thing, it is so frustrating!
I tried several roms, samsung based, AOKP, AOSP, stock...on all there is a lag...
tried a fresh install without restoring apps, tried it without installing anything and no luck
I can not believe that a high end phone like the sg2 has a bug like this, surely there must be a solution to this??
edit
just realized this is for I9000, I have I9100
Dont worry i think.The same thing happens on my s3 also galaxy note is the same screen wakes up after 2-3 seconds ..
But interesting thing is,my i9000 wakes up just about half sec )
GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
Related
So, I downloaded and launched it perfectly... everything so far i tried is working fine except the lock screen... Some times when i press the Cancel key the button lights lid up but there is nothing on the screen and sometimes it appear the lock screen but nothing happen....
Do someone have any solution to this...
Thank you.
I have the same problem. I have been reading that possibly going back to an older kernel / roofs fixes this problem but have not seen and confirmed reports.
Can anyone confirm this and what version?
Thanks
Same problem at me. Both builds are running very fine for some tine but after that are running slow.I don't know why. Maybe is somehow related with the lockscreen problem?
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
+1 one for me... I have got a TOPA100, it's almost impossible to wake up the device, sometimes the lockscreen is visible, but it's impossible to move the unlock slider. Usually I need about 10 times and something around 5 Minutes to wake up the device.
Same problem here, would be great if this can be fixed...
RaZz0r12 said:
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
Click to expand...
Click to collapse
For me it's the same and the battery runs only for one hour, I think a (system?)process is running with 100% CPU time. I am new to android, so I don't know where to look.
Same here on an AT&T Pure. Sure would love to get this fixed however I'm reasonably noob to the Android world (not completely novice to linux in general, and I have successfully flashed my AT&T TyTN II thanks to this site.) Fixing this would be a huge help!
Thanks
More specifically on my device I encounter. The following:
- Turn screen off via end button.
- Turn on screen via call button.
HW button lights come on for a few seconds then cut themselves off.
Screen does not turn on at this point.
- Turn on screen via call button again
- Screen comes on with HW button lights
about half the time screen is unresponsive and will not all me to unlock with swipe of finger
Other times will accept input and unlock to the home screen
When unresponsive repeating entire process above will likely allow me to unlock successfully.
Thanks!
Sent from my AT&T Pure using XDA App
same
my screen never wakes up
end up using soft reset to windows mobile
(it could be something to do with startup??)
Hi everyone,
some days ago, I've got a new display into my phone. It is working fine and everything is running good except two things:
- The phone app does hang during an outgoing call. I cannot hang up the call, because there is a black screen, or the phone does not accept input either. When the screen keeps black, I can go back to the home screen pressing the middle button. But in the "system tray" there is no phone symbol. The behavior is changing from call to call. Sometimes the process crashes.
- When the phone is not used for some seconds or minutes it takes up to ten seconds to see someting after pressing the middle button. An interesting aspect is that when the mp3 player is running, there is no delay. Whenn I press the middle button the screen comes back immedialtely.
I have the Firmware 2.2.1 running and executed a hardware reset two times.
Has someone an idea what I can do to bring the phone app to work properly and to decrease the delay when I want to get the from out of the "sleeping mode".
Please excuse my bad english, I hope you got me right
What do you mean by a new Display...I assume you mean a new ROM or kernel and not actually replacing the screen.
Are you using any sort of app that controls or underclocks the CPU such as SetCPU? I used that app for a while to underclock the CPU while the screen was off and it caused the sort of hanging when answering calls that you described.
Also if this is a new kernel confirm that is is not underclocking or using UV to lower the voltage.
Thank you for your reply.
I replaced the display for hardware damage reason. No new kernel or something like that.
I've done 2 hardware resets. So I just have some standard apps on my phone.
Is there some app wich dispays the voltage and frequency of the cpu?
Ok guys, the problem is "solved".
I thought, that I would have to live with my delay und phone problems forever
But this weekend, my phone decided to workl properly as before. There is no delay when bringing back the screen from sleep and no process hanging up anymore. I did not invest more energy to solve that problem.
I dont know what happened internally, but I am extremly happy now
Hi!
I've trying to figure out why apps like Active Notifications and Floating Touched doesn't work the way it should.
I'm running stock and I'm rooted.
Floating Tougher has an option to lock screen when button is pressed on screen. However when this button is pressed the screen goes dark and flickers and then turns on again. At first I thought there was a problem with the app do I didn't think much about it.
NotifyX and Active Notifications etc. doesn't work either. When I lock my screen there's a brief moment, 6-7 seconds, under this moment the screen stays lock but then turns on to show the notification screen by the app.
I've uninstalled most of my downloaded apps but the problem still persists. I've checked wakelocks but couldn't find anything worth checking out.
Anybody else with the same problem or maybe even a solution?
Thanks!
Sent from my GT-I9305N!
I have a strange problem, well a few. If I lock my phone (C6903) using the physical button I can't unlock it again. I try for about 5-10 minutes sometimes and it just wont work. If I hold it down I can feel it vibrate as if it's bringing up the power menu but the screen just stays black. Eventually it will randomly wake up then I can play around as normal. If I leave it to lock itself I can unlock every time, fist time no worries. This is what pointed me to it being a SW problem rather than a hardware problem.
I also noticed that when I do have the screen turning off in the dark, I can see that the screen is still lit up! Just it is black, not completely asleep. It's really quite bright when I have it next to the bed. Also when I am outside I can't see the screen at all really, even with the brightness turned right up.
It's really strange all these happened about the same time. I figured maybe it was a ROM problem and a fresh install of stock ROM would help. Tried it and at first most of these problems went, just the fact I still couldn't really see the screen in the sun. I tried another ROM and at first was just the same but then these problems started again.
Has anyone had any or all of these problems or got any ideas what it could be? I am left thinking now that the problem is more likely hardware related as the problems are so sporadic and happen whatever I have installed.
Any help / suggestions would be appreciated but I have the feeling I will have to just admit the phone is dogged
You say that most of the problems desapararecen to install a new ROM, it is likely that installing something extra to be the cause, I was introduced me something similar with Expoxed Notifications Module.
Try a clean installation without installing test applications to determine if the problem recurs.
Thanks, yes I guess I will try that, bit of a pain having to reinstall apps after every install and restoring messages etc so I might just put up for now.
I also have realised that the screen not turning on and the screen staying on but black happen at different times. i.e. I can now randomly turn the screen on and off no problem (don't think I have installed or deleted any apps or changed anything), but the screen stays awake when off. When I was last not able to turn the screen back on after turning off the screen actually went to sleep. Very strange
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.