Hey there guys!
I'm a happy owner of oneplus for about 3 weeks now but I noticed that after a few days of usage the device slows down gradually, up to a point where using it is quite troublesome. Also the wake up button seems to fail at times, where I have to press it 3-4 times to wake up(today it failed to wake up and I had to restart it). Any idea what might be causing it? I'm on the CM11S newest update, no kernel changes whatsoever, interactive governor and TWRP installed.
Thanks in advance!
I'm running PA 5.1, facing a similar issue. Capacitative buttons light up immediately after pressing the power button (or double tap) but the screen lags for about 2 seconds.
Sounds like your cpu min frequency is set below 300
cameronmfjay said:
Sounds like your cpu min frequency is set below 300
Click to expand...
Click to collapse
That's impossible on stock.
cameronmfjay said:
Sounds like your cpu min frequency is set below 300
Click to expand...
Click to collapse
Nope. Done nothing of this sort. Moreover, the lag occurs only if I wake the phone after 3-4 minutes of screen off. If I wake it immediately after turning the screen off, there's no lag.
PS: I'm on AK Kernel 300.
Related
I am having a problem with my screen staying on long enough to unlock it. It also happens when in a call and I need to push a number. When I push power to unlock the screen, it only stays on for a fraction of a second then goes out. The bottom row of buttons stays light and will vibrate if i push them but nothing happens. It will do this over and over until finally it lets me unlock the phone. Also when I am on a call and remove the phone from my ear the screen does the same exact thing. Stays on only for a fraction of a second and so on........... This is my third G2X and my first one did this as well. I don't use any kind of lock screen app such as widget locker and when I do try it, it still does the same thing. Anyone have any Ideas???
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
jcbofkc said:
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
Click to expand...
Click to collapse
I do, and I use the same profile you mentioned. I am going to switch it now and try that. Thanks for your quick help!!
(Edit) Yes, that seems to be the culprit. I froze SetCPU for now and problem solved. Now I will change the settings to 312-216. Thanks Again
Happy to help. I am new to this android stuff, but I am beginning to figure things out through trial and error.
Mine are
general
1000max 216min
screen off
216/216
Running same settings as OP. Really love the extra battery life with the screen off profile.
The only problem I have with running that profile on screen off is sometimes when I get a call it takes too long for the phone to "wake up" and I end up missing the call. However since i adjusted it to min 600 (something) it hasn't been an issue.
dreggs said:
The only problem I have with running that profile on screen off is sometimes when I get a call it takes too long for the phone to "wake up" and I end up missing the call. However since i adjusted it to min 600 (something) it hasn't been an issue.
Click to expand...
Click to collapse
Same here. I also added an In Call profile so that when the screen turns off during a call it doesnt lower the CPU speed.
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Does it seem to happen at a certain time? After opening a certain app?
Does sound odd though.
The only certainty I can say is that it happens when no applications are open and the screen goes into lock mode. It also happens regardless of the launcher being used (I use FX, my brother uses HTC Rosie, the other uses Go).
gotpriest said:
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Click to expand...
Click to collapse
+1 I have this issue too...I lowered my overclock and it's been working fine since
Sent From My HTC Sensation 4G
I assume that is performed through SetCPU? Or Daemon.
In Daemon, there's only four options, Sleep and Wake Max, Sleep and Wake Min - how did you fix yours?
Anyone offer a tip on this?
I don't have SetCPU on my phone (looks like it was replaced?)
Don't want to bork my phone, just wondering how to dial down the overclock slightly to prevent this hard crash.
Thanks
ARHD has Daemon Tools I think, with this you can reduce your overclock.
However my suggestion would be to increase the Maximum sleep CPU speed. [Sleep Max]
I can't remember but I think be default it is at ~440MHz, increase it by around 600MHz and see if that fixes the problem. If so you can reduce it gradually to save battery, stopping if the problem redevelops.
Thankee very much!
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
tk_xda said:
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
Click to expand...
Click to collapse
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Grandelama said:
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Click to expand...
Click to collapse
Does this particular known issue apply if the screen turns off on its own due to inactivity time? What about if camera app is in background?
Does faux kernal need a camera fix similar to the one for bricked?
Hey guys,
I noticed another issue but don't know if it's rom-related.
When I push the power or volume-button to wake up the device, it sometimes takes 3-5 seconds until it wakes up and display powers on.
It seems that this issue is showing up more often than a few days before. I would say it happens every 5th to 8th time I wake up the device. :-/
Can anyone confirm this?
Check your minimum Clock speed i.e. in SetCPU or NoFrills what is the minimum speed the processor can run at?
If it's very low then increase it a little.
Minimum CPU-speed is 384Mhz set through SebastianFMs kernel I think. Will NoFrills overwrite kernel settings for testing?
From time to time, usually in the evening/night (?), I try to wake my screen up by either double-tapping it or by hitting the power button.
I can see the buttons back light going on, but the screen doesn't.
I have tried also to hit the power button and wait a little bit (about 5 seconds) with no luck.
I have also noticed that it takes something between 200ms and 600 ms for the screen to wake up, while for example on LG G2 d802 it took about 100ms (or even less).
My only option so far is to keep the power button pressed until I feel the rebooting vibration.
Uqbar said:
From time to time, usually in the evening/night (?), I try to wake my screen up by either double-tapping it or by hitting the power button.
I can see the buttons back light going on, but the screen doesn't.
I have tried also to hit the power button and wait a little bit (about 5 seconds) with no luck.
I have also noticed that it takes something between 200ms and 400 ms for the screen to wake up, while for example on LG G2 d802 it took about 100ms (or even less).
My only option so far is to keep the power button pressed until I feel the rebooting vibration.
Click to expand...
Click to collapse
Undervolting?
Any special settings?
Custom kernel?
Sent from my A0001 using XDA Free mobile app
DerRomtester said:
Undervolting?
Any special settings?
Custom kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
As far as "special setting" ... I don't knwo which is special and which is not.
Which setting are you talking about?
I am running the kernel that comes with the ROM itself, balanced profile, CPU "ondemand" scheduler, no overclocking, I/O "deadline" scheduler, 16bit transparencies ...
Home screen is just 1 screen handled by Apex Launcher with (again) no wallpaper.
In Settings-->Display I have enabled: touble tap wake, avoid accidetal wakes, automatic brightness with mean sensitivity.
The only "special" application I have is "Xposed framework" (Installer v2.6.1 STABLE) with one single module ("EnableCMCallRecording").
Everything else is just applications from the market.
Uqbar said:
As far as "special setting" ... I don't knwo which is special and which is not.
Which setting are you talking about?
I am running the kernel that comes with the ROM itself, balanced profile, CPU "ondemand" scheduler, no overclocking, I/O "deadline" scheduler, 16bit transparencies ...
Home screen is just 1 screen handled by Apex Launcher with (again) no wallpaper.
In Settings-->Display I have enabled: touble tap wake, avoid accidetal wakes, automatic brightness with mean sensitivity.
The only "special" application I have is "Xposed framework" (Installer v2.6.1 STABLE) with one single module ("EnableCMCallRecording").
Everything else is just applications from the market.
Click to expand...
Click to collapse
Ondemand is called unstable by some people. Could you try interactive and report back ?
I dont know if xposed is a problem but i think not.
I suggest wipe system and reinstall your rom.
And do not make any modifications in kernel settings or developments settings.
I hope this works for you.
DerRomtester said:
Ondemand is called unstable by some people. Could you try interactive and report back ?
Click to expand...
Click to collapse
I will try this. But never had issues with LG d802 w/ CM11M10 and CM11M11 there.
DerRomtester said:
I dont know if xposed is a problem but i think not.
Click to expand...
Click to collapse
I hope so. I do need the call recorder.
DerRomtester said:
I suggest wipe system and reinstall your rom.
Click to expand...
Click to collapse
That's the way I install ROMs: I never do "upgrades".
DerRomtester said:
And do not make any modifications in kernel settings or developments settings.
Click to expand...
Click to collapse
Do you think this is a device related issue or a more general one for M11/Nughtlies?
I am quite puzzled by this hint. The issue is not happening everytime the screen goes off. It happens at random, usually after long (>10 min) periods with the screen off, and never in the morning (after 6 to 7 hours of sleeping screen). Nonetheless I'll try it...
[UPDATE] As of 8:00pm my phone started with a slooow screen wakeup (~ 1000 ms).