Hello,
Is there a possibility to disable the delay that I have from the moment I press the unlock button to the moment the screen turns on?
At the moment I have 2.5 seconds delay from the moment I push the button until the screen turns on.
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
larry200ro said:
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
Click to expand...
Click to collapse
My phone has the same behaviour and the "problem" (if you want to call it a problem) is also described in some german forums - so no, it seems that this is absolutely ordinary.
I had the chance to compare it with a I9000 and the I9000 will outperformance the I9001 at this point, but nonetheless for me it is not really disturbing or so.
any updates on this one? Can someone please help? It's driving me crazy
Hy
I've read about the same problem on a hungarian forum, but I don't have it, mine turns on in less then a secound.
I think if this is such a common problem, Samsung will fix it. Maybe write them a mail.
When the screen has been turned off for a long time, the first unlock takes a lot longer than the following unlocks. For me, I think the 'cold' unlock is 2.5 seconds while a 'warm' unlock is just 1 second.
But yeah, this clearly is a standard problem. Let's hope Samsung brings out a firmware update soon to fix issues like these.
Mine has same "problem". It seems that the phone is in somekind of sleep.
i believe that problem is fixed in 2.3.4. Try flashing that and i hope you won't have that problem...i mean this is how it works:
1. I9000 uses SGX540 which uses less ram for its vram so you have around 250mb+ free ram
2. I9001 uses Adreno 205 which uses a lot of ram for its vram so that you have about 120mb left only
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Unfortunately it is not fixed with 2.3.4 as I still have the issue.
I will try your suggestion with the CPU frequency
shad0wboss said:
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Click to expand...
Click to collapse
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Edit:
Even with 1.4Ghz as frequency there is a delay, not that long but still about 1,5 sec.
reneph said:
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
Click to expand...
Click to collapse
yup it will...then you should wait for a better custom rom with all those JIT and ram compress tweaks enabled and then you can enjoy the speed.
To be honest if you guys want your problems to be fixed, do support the devs as much as possible in this thread
Psyco_01 said:
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Click to expand...
Click to collapse
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
reneph said:
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
Click to expand...
Click to collapse
mate, you can never have performance with battery conversations...it's inversely proportional.
1. Set maximum value to 1 ghz with minimum of above 245
2. Do a hard reset from going into settings -> privacy -> factory reset because i just did it recently and my phone's running much faster.
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
larry200ro said:
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
Click to expand...
Click to collapse
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Csapi007 said:
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Click to expand...
Click to collapse
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
shad0wboss said:
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
Click to expand...
Click to collapse
No, I mean getting the battery out and then putting it back.
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
Interesting....what version of android do you have (also kernel)
Mine reacts slower if I leave it longer. (samsung explanation "It is because the phone is entering in some kind of sleep state"). When I said that Galaxy s2 reacts instantly the answer was that Galaxy S2 has a better microprocesor and has a different platform.. hmmm
If you find this useful, press the Thank you button
Csapi007 said:
No, I mean getting the battery out and then putting it back.
Click to expand...
Click to collapse
well, i've done that a couple of time already without knowing it being a fix for random shutdowns...but really it's a bit annoying, it just turns off by itself..
Related
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.
Hi ppl !
Prabobly i have solved problem with unlock lag. Fix is simple and you dont have flash anything. Just setup nexus wallpaper for me it worked like a charm.
Sent By Reverse Osmosis
It's not a solution.
Setting up a live wallpaper will make your processor run quicker (so it will drain your battery much quicker), the same way the screen unlocks instantly when music is playing.
so there is no solution fot this "problem" yet???
No, there is no solutions as this cannot be thought as a problem. When the screen shuts down, it takes a few seconds for the phone to fall in a deep sleep. This is a built-in feature which helps to save battery when screen is off.
Friends of me just bought this phone and also had this lag problem. So i rooted their galaxys and changed the governor with set cpu from ondemand to performance. Unlock lag reduced from 4 seconds to 1 second, and also after unlock the phone is instantly fast. I know performance governor leads to more power consumption, but we think a phone with 1,4gHz shouldn't be that slow.
I changed lock screen to golocker and lag is now significantly lower. I also use golauncher so it may have affection to golockers' performance. No issues for double locking or battery drain.
Cheers
The solution is simple, turn off your power save mode
doesn't help here....
And again, it's been established already that turning power save off doesn't help.
Placebo effect at most.
Read the previous topics before posting
I have a same problem, still no solution ?
While the Galaxy S, there was no problem.
Envoyé à partir de mon GT-I9001 utilisant Tapatalk
Since i use go-locker, in have noticably less lags.
Tapatalked from my Samsung Galaxy S Plus
Strangely enough, Golocker does speed it up a little, it went from 3 to 2 seconds.
But it still lags.
It lower your processer when your phone is idle make it less battery consuming. Unless you root your phone and use app to stop the deep sleep mode and keep phone speed always at 1.4. Otherwise nothing can do I think. Cause the phone need boot up the speed everytime you unlock making it [email protected]@At least you know it help you save.battery
Sent from my GT-I9001 using Tapatalk
I changed the lowest clocks from 123mhz to 246mhz. Seems more responsive. Used CPU Master (free).
F-B said:
I changed the lowest clocks from 123mhz to 246mhz. Seems more responsive. Used CPU Master (free).
Click to expand...
Click to collapse
The standard-setting for the minimum clock is at 244mhz. So this probably wont help anyone.
Also my lag is gone by using Go Launcher and Go Lockscreen!!!
Great (Best i think) Launcher anyway
Sh0rty007 said:
Also my lag is gone by using Go Launcher and Go Lockscreen!!!
Great (Best i think) Launcher anyway
Click to expand...
Click to collapse
Is the same for me, with go launcher and locker, the lag is gone
No difference ... ='(
Not going against the waking from deep sleep theory, i also always thought this was how it worked.
What puzzles me, however, is how the iphone doesn't seem to suffer from this for some reason and still performs as fast with perfectly acceptable battery time.
But i got it better by changing my lockscreen, that actually helps. Phone needs to load up the lockscreen when you wake it up so a simpler lockscreen will also help with better results by loading faster. You'll notice the screen starts responding faster. I found the most common one, the sliding tab the fastest while the ring one, to be a bit slower. I also found the go lockscreen to be faster than the "ring" one but not as fast as the basic sliding tab.
Btw im using a I9000 with CM7 stable but the "problem" still applies.
Turning off the power save option did help for me.
Galaxy S Plus GT-i9001 with Stock Android 2.3.6
Hello, I have noticed that my device has taken a long time to respond by pressing the unlock button. I've tried to give a full wipe, install other roms and the problem continues ... Anyone have an idea what I can do to solve it? thanks!!
how long?
if its like a second, its normal
if more, you might want to see the minimum frequency, governor etc
what rom are you on?
theaks30 said:
if its like a second, its normal
if more, you might want to see the minimum frequency, governor etc
what rom are you on?
Click to expand...
Click to collapse
I tried a lot of rom... with all of them I had this problem... I`m using now the MercurySandwich ROM, at times it unlocks in a second, but sometimes it takes too long... about 30 seconds or more... even I need to press the unlock button more than 1 time...
try changing the governor to smartass and disable DVFS
try zeus
Normaly it's unlocked in much less than a second, but I already had it a few times that it takes some seconds. ROM doesn't really seem to make a difference, even if I had the feeling that it happend more on CM7 than other OS. Seems to be not directly a HW thing, but normaly it's: press the button and it's unlocked directly.
As i said, try changing your governor etc. There is a thread in the question and answers section itself, search for it. Its pretty recent
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
baconbeacon said:
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
Click to expand...
Click to collapse
did u tryed to install a custom rom? or a stock but flashing a kernel?
op3n said:
did u tryed to install a custom rom? or a stock but flashing a kernel?
Click to expand...
Click to collapse
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
baconbeacon said:
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
Click to expand...
Click to collapse
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
op3n said:
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
Click to expand...
Click to collapse
Well, if that's normal, this shouldn't be an issue. Though I do wonder where's the big little concept gone.
Did it ever occur to you guys that it might be dynamic hotplugging and a specific configuration/setup is being used ?
Or is it in your case really being buggy and broken ?
You left something working in the background and monitored how the cores behaved ?
Using different apps ? (say: kernel adiutor [or kernel adiutor mod], EX Kernel Manager, CPU Z, etc.)
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
I am out of things to try on this thing, I bought it used in February and ever since upgrading to Pie the phone will beginning shutting down during use, even while only watching youtube. Something is causing the cores to ramp up to 100%, it begins to warm up but not overheat and then shuts down usually around 70c I believe, no overheating message just straight cuts power. The only way to get it to power back on is to cool it down in front of a fan or car AC for a minute or so, then it will stay on and I can watch the CPU usage drop after a few minutes and then I can use it again. I have factory reset, cleared cash but the issue remains. As Android no longer allows seeing what is using CPU I have no way of trying to figure this out further. Any ideas?
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
I havent tried this, kind of terrifies me. I have touched firmware since my S3. lol kind of afraid it might shut down while doing this and brick it
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Click to expand...
Click to collapse
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.
drosenberg85 said:
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.
Click to expand...
Click to collapse
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.
MrMike2182 said:
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.
Click to expand...
Click to collapse
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?
drosenberg85 said:
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?
Click to expand...
Click to collapse
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.
MrMike2182 said:
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.
Click to expand...
Click to collapse
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out
drosenberg85 said:
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out
Click to expand...
Click to collapse
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
Happy Thanksgiving bro!
Same to you bro
Sent from my SM-A205G using Tapatalk
MrMike2182 said:
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..
Click to expand...
Click to collapse
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol
drosenberg85 said:
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol
Click to expand...
Click to collapse
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?
MrMike2182 said:
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?
Click to expand...
Click to collapse
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol
drosenberg85 said:
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol
Click to expand...
Click to collapse
Then get away from that version just go back one lol.
MrMike2182 said:
Then get away from that version just go back one lol.
Click to expand...
Click to collapse
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?
drosenberg85 said:
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?
Click to expand...
Click to collapse
Yep definitely hardware! You need a new phone or board!