Related
Hi: I've super-upgraded to TuMa 1.3 with very good happy time till now!
Many thanks guys, especially Tuma!!
i just have one problem, when typing on my keyboard, sometimes, not all the time, keys stick and after pressing a key i get something likeeeeeee thissssssssssssssssssssssssssssssssssssssssssssssssssssssss
or, even worse, the backspace key gets stucked the same way and it erases all EAAARRRHHHGGGG!!!
is this fixable??, is anyone else having this problem???
I use the keyboard big deal...
Have the exact same problem with helmi 1.3
tehCORE said:
Have the exact same problem with helmi 1.3
Click to expand...
Click to collapse
So, I see now that upgrading (something I had planned) to helmi 1.3 doesn't repair this problem. I would like to know where this problem originates to find a solution. I'm using now Pocket Hack MAster with the device running at 597 Mhz and the problem is still there! :evil:
Some advice??
EDIT: I've removed the CPU Meter on the upper bar. It seems to work faster and better. Still waiting to see if the problem arises again..
i'm on helmi_c 1.1b and have this problem too. May be that is hardware problem or driver time bomb?
change the keyboard repeat settings, and delay settings, I have had this problem with every wm5 rom, and by changing the settings it appears to fix this prob.
tesing.. thanks for reply...
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
I've had success with changing the keyboard repeat settings but it comes back eventially. I've had the problem on every WM5 ROM, but less-so on the most recent Helmi ROMs with the AKU update.
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
I'm now using Pocket Hack Master with the feature of using different speeds for different apps. It happens less, so, could be the driver priority on CPU intensive apps. Because the SMS app now seems to need more CPU power than before :? :? (bar & text space redraw or something), it is one of the apps I've selected to run at 590 Mhz:shock:.
Black6spdZ said:
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Click to expand...
Click to collapse
I'm having this problem with other programs also (i.e.: Softmaker TextMaker, Pocket MindMap). Also, someone said that when using the e-mail (nor the SMS) part of the program the problem doesn't happens.. I've not tried myself as I don't currently use e-mail on my device.
xykosomatik said:
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
Click to expand...
Click to collapse
Please, xykosomatik, confirm so. I would be eager to upgrade if this problem is solved on this ROM, as I use the keyboard typing 80% of the time on my device.
Thanks all.
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
It seemed to make an improvement for me, but time will tell. This issue seems to come and go on my phone.
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Tuatara said:
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
Click to expand...
Click to collapse
maybe we could do a compromise, i little higher than the OS priority
the keyboard problem is really annoying
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
*sigh* ... why do people still keep punching in random numbers into the registry without checking what the values could or should be? *sigh*
Black6spdZ said:
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Click to expand...
Click to collapse
gh0st said:
maybe we could do a compromise, i little higher than the OS priority
Click to expand...
Click to collapse
Ok ... before this gets out of hand, and other people start doing "silly" and "stupid" things with Priority256 ... especially without understanding what you're changing, READ THIS! Otherwise you WILL cause untold problems for your device.
http://msdn.microsoft.com/library/d...html/wce50conRealTimePrioritySystemLevels.asp
To give you the comparison for Windows XP ... just open Task Manager, select an application which is using 100% CPU, running at Normal Priority, and switch it to Real-Time. Then enjoy how "responsive" the one application is (unless it's accessing the video display and/or disk - i.e. try doing it to an explorer window file copy! ;-)). You'll enjoy a "locked" machine, and admire how you're unable to do anything else - even open the start menu! You may have to hard-reset your machine depending on the application you choose to make Real-Time.
THANKFULLY ... the Keyboard Driver (QwertyKey) has a FORCED time-delay in it (debounce delay) which ensures it can not take 100% CPU time, and through this ... and ONLY through this fact, it hasn't killed your device. Had you done this to ANY other device driver, I'm sure your device would need a hard-reset, and you could start re-installing everything again.
By raising the priority above everything ... ALL you are doing is making the QwertyKey device driver get serviced AHEAD of any other pending interrupt. While this MAY make a slight difference, it will only do so at the expense of EVERYTHING else in the OS. (Like WiFi, Network, USB, ActiveSync, Memory Management, Compaction, etc ...)
gh0st said:
the keyboard problem is really annoying
Click to expand...
Click to collapse
Yes, I have had the same issue, but there is a LIMIT to which you can go with the driver Priority in order to "fix" what is fundamentally a hardware and driver problem.
gh0st said:
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
Click to expand...
Click to collapse
In my testing, and throughout the TuMa ROMs I've used 0x81 - or a priority of 129. This was carefully chosen to be below the Wave device (which was or should be set at 0x80 or 128 for best performance on the BA - again due to driver issues), so that sounds/rings happen at a higher priority than the keyboard. Yes, this is eventhough BOTH Priority256 values for these drivers were tweaked above the default recommendations from MSDN.
If you're finding that the keyboard is causing you grief, you could try inverting these two devices, and setting the keyboard HIGHER than the sound driver - i.e. to 0x7F or 127, and see if the system sound servicing is the cause of the keyboard stuttering delay. However, you may introduce stuttering into the sound output at this point ... i.e. even when you're NOT using the keyboard (which is most of the time).
At the ABSOLUTE HIGHEST level I would even consider, would be just below that of the touch-screen (0x6D). At this level (or above) would cause handwriting recognition issues, as the touch-screen would not be serviced at the correct rate to track the line drawings.
Never even consider going above the Power Manager Resume Priority Level ... if the driver supports power management, and is taking too much CPU, then the power management thread will never be able to "shut it down", and/or wake it up ... ever. Result = lockup.
So ... in summary:
QwertyKey: 0x81 ... or 0x7F to invert priorities
Wave Device: 0x80
I'd still like to test all this with the latest AKU3.x ROMs and see if the Priority settings are still valid, but for the moment, I'll assume that they are.
Good luck to anyone using priorities outside "sane" values ... you will create "priority inversion" conditions, where a driver is waiting on another driver to run, but it never will, since the priorities are reversed. You have been warned ... but enjoy playing with it anyways. Device recovery is only a hard-reset away.
Thanks for clearing this up Tuatara, good post!
oops! i'm reverting the priority values....
Thanks for the post, @Tuatara. it was very enlightening.
Hello everyone ,
Does someone experiences the same problems as seen in this thread for the Touch HD?
http://forum.xda-developers.com/showthread.php?t=446440
Click to expand...
Click to collapse
To sum up, there's little 'freezes' lasting 4-5 seconds where the screen doesn't respond to any inputs.
It occurs randomly and without reason.
HTC released an hotfix regarding this problem, that can be found here:
http://www.htc.com/www/SupportDownload.aspx?p_id=179&cat=0&dl_id=448
Click to expand...
Click to collapse
However, this is for the Blackstone. When executed on the X1, there is a message box saying
"Please use the correct device to install this hotfix program"
The fix can be extracted and there's a _setup.xml that seems to tell what the .exe does;
I was wondering if it were possible to port it for the X1 as the Blackstone and the X1 are somewhat similar?
NB:
Hard resets didn't helped neither, freezes are also present.
I'm using this:
ROM Version: 1.02.933.3
ROM Date: 08/29/08
Radio Version: 1.06.25.29
Software Version: R1AA017
I also have these freezes occasionally.
I managed to install the files from the hotfix the other night, (because, well because I like to experiment) I spent 5 times as long removing them.
The display inverted, but not the calibration!
ill change the cab info install at your own risk.
however i do not have this issue. I have an issue of after long idels of not using my x1 at work the screen will apear to be cracked but the images are really cracked. a soft reset fixes this issue. (this is ment for a seperate thread) just giving you info on other display bugs on the x1
also can you upload the cab as the htc site will not allow me to download it.
My issue is actually with the camera... if you leave the Camera application on a long time, like 20-30 minutes idle, it will eventually crash, and it will say Camera.exe has stopped responding (or something like that, asking if you want to send a report to MIcrosoft)
just get freezes when i use the HTC album. other then that, nope.
Here's the .exe (renamed to .cab since xda seems to block .exe),
for those who can't manage to download it.
@Shadowmike
Thanks for your help
Sorry to go off topic a little :
Regarding your idle screen problems, I don't have any of it (maybe because I'm experimenting tweaks with it a lot so don't have time to idle really long )
May it be related to GWES:
http://msdn.microsoft.com/en-us/library/aa925858.aspx
Click to expand...
Click to collapse
To sum up, there's an interesting registry value named PORepaint that can take values from 0 to 3.
The key I would change may be:
HKLM\System\GWE\PORepaint
The factory default on my X1 is 0 but for your problem, I would set it's value to 2.
Personal Feedback:
When you press the ON button in order to wake the screen, the screen goes blanks for few milliseconds (blank flash), but it's repainting the entire area.
No major speed issues noticed between 0 and 2 values.
Hope this helps
I have the same problem with my X1, using the latest R2 rom (generic UK). It annoys the most when playing games like Bejeweled 2 and the screen suddenly freeze for a few seconds although the game and time keep running in the background and when it stop freezing I already lose time/points. It also happens with every other game I tried playing, even after hard reset. Any fix available yet?
doclucas said:
I have the same problem with my X1, using the latest R2 rom (generic UK). It annoys the most when playing games like Bejeweled 2 and the screen suddenly freeze for a few seconds although the game and time keep running in the background and when it stop freezing I already lose time/points. It also happens with every other game I tried playing, even after hard reset. Any fix available yet?
Click to expand...
Click to collapse
Exactly what I get. It is most encountered in games where you touch the screen rapidly. Suddenly the whole OS freezes for 5-6 seconds then continues for some time until you get it again. It is very annoying.
Exactly. It happens ONLY with rapid screen presses. I observed this when typing.
Yes. This happens to my X1 also. It is possible to reliably replicate this bug.
The shadowmike's Cab didn't do anything usefull. So the HTC's Hotfix for the HD doesn't apply
Anyway, I made a Video describing this bug:
http://www.youtube.com/watch?v=2cOhX8yY5Yk
Hm.. Yesterday right after I did that video, I flashed my X1 with the newest official ROM (version 1.03.931.8 (dated 12/21/08)) from this site. Then, I installed the shadowmike's cab. After the soft reset, the problem hasn't (yet) surfaced (plus the system seems more responsive). Fingers crossed .
Edit: Nope.. False alarm. It still happens. Though rarely..
yup...
it happens...
doesn't really concerns me though...this is windows mobile anyway
pikipirs said:
Yes. This happens to my X1 also. It is possible to reliably replicate this bug.
The shadowmike's Cab didn't do anything usefull. So the HTC's Hotfix for the HD doesn't apply
Anyway, I made a Video describing this bug:
http://www.youtube.com/watch?v=2cOhX8yY5Yk
Click to expand...
Click to collapse
Youtube a$$hole$ seem to have removed your video for some reason, was a good one though, wonder if they get commission from SE. Maybe you can post it on a different video site...
shadowmike said:
ill change the cab info install at your own risk.
however i do not have this issue. I have an issue of after long idels of not using my x1 at work the screen will apear to be cracked but the images are really cracked. a soft reset fixes this issue. (this is ment for a seperate thread) just giving you info on other display bugs on the x1
also can you upload the cab as the htc site will not allow me to download it.
Click to expand...
Click to collapse
Thx a lot for having uploaded cabs as I have sometmes the freezing issue also from my side on my X1
doclucas said:
Youtube a$$hole$ seem to have removed your video for some reason, was a good one though, wonder if they get commission from SE. Maybe you can post it on a different video site...
Click to expand...
Click to collapse
Strange.. I can still access and see the video (no cookies works too). Does the video still appear deleted? Or was it just a glitch
Aye, same here... Mostly when playing insaniquarium. I just tried the .cab fix, didn't fix anything for me
SquidgyB said:
Aye, same here... Mostly when playing insaniquarium. I just tried the .cab fix, didn't fix anything for me
Click to expand...
Click to collapse
it happens to me as well...i think this generic bug in x1.
So how do I reliably test the bug ? It happens to me sometimes, but I did not find the pattern yet.
Watch my video (top of this page) to see how I did it (I've shot myself (with a camera ) couple of times doing it).
If that doesn't work, try to load some app. Like any game that somehow reacts to your touch (even Bejeweled works). Then try touching really fast and repeatedly. It shoud happen.
Here's a sound recording of me tapping a jewl in Bejeweled (i'm really hitting the display, do it more gently). It should give you an idea how fast you need to tap. Right before 0:06 the screen stopped responding, i did 4 taps to verify, and then another, and then it started responding again (3 more taps). Sometimes all it takes is 5 seconds (like it did here), but other times, your hand will start to hurt before it happens. Just rest a little bit and then try it again.
Hiho,
I've been working on getting the panel to unblank faster, not stall to unblank and to not show distortions on unblank (which also happens sometimes).
Please report your experience on blanking/unblanking the panel using the given packages. If you are unsure which one to use, use the dualdie one!
For dualdie (most common) devices: here
For monodie (rare) devices: here
Please report your device (topa100, topa210,...).
If some lone Rhodium user comes by, don't hesitate to test if this breaks the known behaviour on your devices. (From the code, pretty nothing should work for rhods. Please confirm nothing is broken.)
Update: The code has been committed to gitorious. Fetch newer builds from the autobuild service. Thanks to everyone who tested!
Hi,
Kernel is booting fine on my topa100. The lights on the buttons light up immeadtly. Screen doesn't wake always fast. I normally wake up with power and menu button for unlock. This goes realy fast.
Regards,
Bart
bheremans said:
Hi,
Kernel is booting fine on my topa100. The lights on the buttons light up immeadtly. Screen doesn't wake always fast. I normally wake up with power and menu button for unlock. This goes realy fast.
Regards,
Bart
Click to expand...
Click to collapse
But the time from pressing power until the LCD is unblanked is seriously faster now compared to regular kernels, no?
Sent from my MSM using XDA App
TOPA160
boots fine, see this is new 28 package,
freaking, apocalyptic, incredible fast screen.
would almost never think about that fast.
thank you very much. all i need now is a better battery or power management and HW3D working.
I've got a monodie device, the zimage & modules seem to work fine for me but I don't notice any speed difference on unblanking. So I guess if it works well for dualdie devices we know that it won't upset those of us with monodie devices.
shavenyaknz said:
I've got a monodie device, the zimage & modules seem to work fine for me but I don't notice any speed difference on unblanking. So I guess if it works well for dualdie devices we know that it won't upset those of us with monodie devices.
Click to expand...
Click to collapse
Haha, just fooled myself. At least the last package for monodie devices which was posted in the dedicated thread already contained the panel fixes, so you won't really notice a difference. Be told that it took approximately 2 to 3 seconds to unblank before So just go on using the kernel posted here until the monodie issue has been solved.
mweirauch said:
At least the last package for monodie devices which was posted in the dedicated thread already contained the panel fixes, so you won't really notice a difference.
Click to expand...
Click to collapse
Ah, tricky. Thanks for looking out for us monodie guys.
For me (my TOPA200) it's different. Most times it's really fast, sometimes the screen left black and I must press home button a second time.
No other (new) problems at this time.
Greetings and thanks for your great work
shavenyaknz said:
Ah, tricky. Thanks for looking out for us monodie guys.
Click to expand...
Click to collapse
I still "owe" you guys a proper fix. Cotulla - one of the HD2 kernel devs - might need this for the HD2, too. So I see a chance we can find a way of getting the required changes/extensions into HaRET.
cheesy33 said:
For me (my TOPA200) it's different. Most times it's really fast, sometimes the screen left black and I must press home button a second time.
No other (new) problems at this time.
Greetings and thanks for your great work
Click to expand...
Click to collapse
Yap, when device is in idle sleep mode, it shortly wakes (red LED) and sleeps (green LED) immedeately. Only pressing home button helps. But If I recall correctly, that also happened with the old panel setup/init code, it just took longer to fail waking up the lcd panel. I wouldn't clarify this as a regression as it also happened before, just "behaved" a tad bit different due to the long panel waking times. Another issue to be sorted out later ...
Topa 100
Wow, it is awesome.
I never feel the screen wake up that fast before. However, the screen left black and I need to press home button a second time.
You did a very good work and keep it up.
Tested on my Topa100.
"monodie" version cannot create data.img and crashed, "dualdie" booted and now wakeup works much faster.
Thanks!
TOPA100
Dualdie works perfect and gives a much faster feeling!
Thanks for this update!
This dualdie package works fine on my topa100 device.
The screen tuens on incredibly fast, just like(or even faster than) what the WinMo does!
If I "actively" turn on and switch off the LCD, the LCD would react very fast (i.e what I have mentioned above).
However, if the device is standby for about 10sec or longer, usually, the LCD would not turn on. In this situation, i need to press the power again and the LCD turns on immediately.
Also, i found that, in this kernel, pressing the power key would have a higher chances to turn on the LCD than pressing the "end call" key.
Thanks for these positive replies peeps!
I also can observe that it won't power on when in "pm idle sleep mode". When holding end-key for a little bit longer it awakes. Using the home button immediately gets it out of sleep correctly.
I am not quite sure this is a regression or not, but I am of the opinion that this also happened with the old (slow) panel init code, just wasn't as present that much.
Will take a look.
I tried your package on my pure(topa210) and it worked great! Before it took almost 5 secs to unblank, now only 1 or 2 secs!
Very good job, the dualdie version works prety well, wakes the display very fast, but if i continuously lock then wake up few times it will stuck on the blank screen for some secs, then after works again.
monodie or dualdie?
I've got a T5353 TOPA100 but how do I know if I've got a dualdie or monodie device?
Edit: Is this fix ever going to end up in the main build?
stijnr said:
I've got a T5353 TOPA100 but how do I know if I've got a dualdie or monodie device?
Edit: Is this fix ever going to end up in the main build?
Click to expand...
Click to collapse
First try to dualdie version, if that doesn't work out, you got one of the more rare monodie devices.
The panel fix is going to end up in the kernel when I find the time committing it gitirious.org had some problems at the start of the weekend...
I had a similar problem(but worse) sometimes when using the stock rom.
I've replaced the stock rom and been using CM10.1 on emmc.
Sometimes when playing games the touch screen may become unresponsive but the 3 standard buttons still would work.
(as well as the hardware buttons.)
When this happens I'm not able to click on any of the icons on the home screen. (none of the control buttons work in game, either.)
I wonder if this is a hardware problem, CM10 problem, or a problem with the coding of the game (dungeon hunter 4.)
The problem actually does not last. Nook HD+ recovers by itself after about 1 minute.
Else, I could also click on the power button to turn off display and turn it back on.
Once it's back on everything is working including the in-game controls.
Does anyone have a similar problem?
I doubt this could be a bug in the game (Dungeon Hunter 4). The game is very buggy but when I play it on Nexus 7, I never experienced any control button issues. (Though it does crash "a lot" and sometimes more often than on the Nook HD+)
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
ndttung8487 said:
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
Click to expand...
Click to collapse
Thanks. I appreciate your help. I had this problem again today and I noticed the available ram was indeed quite low at the time.
Although it seemed unresponsive, it seemed more like being extremely slow.
Somehow if I turn off the display and turn it backs on it gets a bit better.
I suspect dungeon hunter 4 has a memory leaking problem. (memory not released completely if reload an area many times.)
I tend to have this problem if I load a lot of data in the game several times.
Strangely this does not occur on Nexus 7 based on the latest patch.
I searched in xda and it seemed last year Nexus 7 also had the same problem especially when playing certain games.
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Here is his topic: http://forum.xda-developers.com/showthread.php?t=2263553
ndttung8487 said:
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Click to expand...
Click to collapse
Thanks. I deleted the game as it is very buggy, crashes often and with many in game bugs. I'm finally done with it.
If I encounter the same issue with other apps I'll definitely upload the log.
I had it on all roms
Hi,
No, you are not alone. The issue occurred on all roms I used so far.
Indeed it mostly shows up in games, though I think I noticed it in other apps too occasionally.
I usually use the power button, but I'll try clearing the memory in the future...
M.
Hello everybody.
I just got myself an P880 a few days ago. All in all, I am rather content, but there is something that bothers me sorely: the lock screen lag. There is a delay of about 3 seconds between pressing the power button and the screen coming to life. I've had this on stock ICS, stock JB and now on CM 10.1.2. I tried different lock screen and also no lock screens - all to no avail. I even checked another P880 (it was running stock ICS) and it was the same story there. Yet I can't really find anyone else reporting this problem, so maybe I'm doing something wrong? I don't know!
I took a video of my old SGS and the P880 next to each other: youtu.be/RyrgdiLGhoU
All hints and suggestions are appreciated!
lukedoe said:
Hello everybody.
I just got myself an P880 a few days ago. All in all, I am rather content, but there is something that bothers me sorely: the lock screen lag. There is a delay of about 3 seconds between pressing the power button and the screen coming to life. I've had this on stock ICS, stock JB and now on CM 10.1.2. I tried different lock screen and also no lock screens - all to no avail. I even checked another P880 (it was running stock ICS) and it was the same story there. Yet I can't really find anyone else reporting this problem, so maybe I'm doing something wrong? I don't know!
I took a video of my old SGS and the P880 next to each other: youtu.be/RyrgdiLGhoU
All hints and suggestions are appreciated!
Click to expand...
Click to collapse
There is no real answer to this question, my 4x is fine, perhaps half a second delay from pressing the lock button to seeing my lockscreen.
However there are many contributing factors to what could cause this, for example the phone may be locking to a certain frequency too low and it's finding it hard to come back from, if you lock the screen whilst on a RAM hogging app it will also lag, background processes will also slow it down, for example, always clear your recent apps (Long hold Home button) and clear them, if you have root access (jb only i think) Then try using greenify and freezing background apps you dont want either running/receiving notifications from.
If you are still on stock you may want to remove bloatware (apps you don't use) Which will also be churning away in the background slowing down your phone, make sure in your settings you will also have that there is no delay and that lock button INSTANTLY locks the phone and then try again and post back if it's helped or not, if not then we should start looking at other factors it could be, perhaps a week tegra variant and we should look into a custom kernel and raising the minimum frequency a tad and seeing whether or not that will help.
my device has same problem and it's very annoying
hassan1990 said:
my device has same problem and it's very annoying
Click to expand...
Click to collapse
What was the point of this post? Contribute to troubleshooting the problem if you can, but simply posting a "Me too" is no use anyone.
penguin449 said:
However there are many contributing factors to what could cause this, for example the phone may be locking to a certain frequency too low and it's finding it hard to come back from, if you lock the screen whilst on a RAM hogging app it will also lag, background processes will also slow it down, for example, always clear your recent apps (Long hold Home button) and clear them, if you have root access (jb only i think) Then try using greenify and freezing background apps you dont want either running/receiving notifications from.
Click to expand...
Click to collapse
I maybe should have mentioned that it isn't every time that there is this delay, maybe every second time on average - sometimes more often, sometimes not at all.
Having had this problem with different firmwares and also with a cleanly wiped phone, even with a fresh install of CM when I hadn't even flashed the Gapps package, makes me think that this very likely isn'ta bloatware issue.
Changing the CPU governor to performance had no effect either.
hassan1990 said:
my device has same problem and it's very annoying
Click to expand...
Click to collapse
Edit: Never mind what i had written here, I was confused. But yeah, I welcome any information that helps us close in on the problem.
SimonTS said:
What was the point of this post? Contribute to troubleshooting the problem if you can, but simply posting a "Me too" is no use anyone.
Click to expand...
Click to collapse
Equally this post was just as useless! Try what i mentioned above and let us know how it is afterwards, THEN ask other questions
penguin449 said:
Equally this post was just as useless! Try what i mentioned above and let us know how it is afterwards, THEN ask other questions
Click to expand...
Click to collapse
I don't have this problem or I would assist in trying to troubleshoot it. You may not have noticed but I don't tend to ask questions because I am very good at reading and most things have been discussed and answered.