[Q] Incoming call lag problem in CM V7.1.0.1 - Wildfire Q&A, Help & Troubleshooting

Does anyone already install the newly released CM 7.1.0.1 ? in my HTC Wildfire the incoming call is somewhat lagging around 1 sec. I dont know whether is it becoz of my mobile or heavy graphics in CM7. anyone find solution for this lagging problem ?

It's actually far better than in previous versions, which used to lag by about 4-6 seconds. A few things which have helped:
- Keep min CPU frequency at 352MHz
- Keep CPU goverenor at Interactive / Ondemand
- MOST IMPORTANT (From my testings anyway) - If you don't use a cover, this problem doesn't arise (Lag is near zero). The cover blocks the proximity sensor, hence, the screen is turned off initially, and when the cover is removed, it will definitely take some time for the screen to turn on, which gives rise to the lag.

That's useful info. I'll try it.

Related

!!!SOLVED!!!: Stable HangUPs in 3D CPU intense games on all ROMs

Hey guys,
i got stable hung ups in 3D intense games (asphalt5, dungeon hunter 3D, crusade of destiny)
some 3-10 mins of play and bang! you got complete stall - have to plug out the battery to reboot.
all other games (2D arcades, tetrises, arcanoids, pacmans) are working quite stable.
i've already tried almost all available ROMS (except stock non rooted one, btw - i dont want to update HBOOT to 0.8, full reset with wiping all the caches inc. dalvik and ext3 part before each ROM.)
pays ROM (several vers)
MCR r2-r3.1 (with richard's kernel either with OCUV or with OC only or without any UVOC and with original MCK 1.1 kernel)
amer_mod des final
all are behaving the same....
what the heck? My phone is generic and certified for Russia (PCT) and it's from white shipment.
the only idea i have is slow SD, cause i use the one which was with the phone - 4GB class2 SD.
please ideas? i wanna play some time not only tetris!
just noticed one moment. it happenes not only in 3D games, it also happenes when using the phone intensively, i.e. now I got stable instant reboot when using internal browser (even with pictures and flash turned off) and opera beta for android. the most interesting part is that just before reboot the back bottom part of the phone becomes noticeable warmer, let's say about 40°c and then instant reboot. (just as it is in 3d games) I use Richards OC only (no UV) kernel v14 with Max freq. set to 998 and MCR r3.1 (everything was wiped upon flash)
Re: Stable HangUPs in 3D CPU intense games on all ROMs
Maybe its some kind of thermal protection of the cpu?
-------------------------------------
Sent via the XDA Tapatalk App
i thought so too...
does any one knows some king of CPU thermal monitoring tool with logs for android?
Happens to me as well. The phone heats up like crazy particularly on badly coded games like the ones gameloft released. For example polarbit's armaggedon squadron runs perfectly well for any amount of time but realfootball for example causes the phone to overheat.
They really botched their ports.
just did a thermal monitoring with tempmonitor lite - but on Desite it only monitors BATTERY temp - it's about 32-33 degrees - so far i found no CPU temp mon which works. and still phone reboots during hard flash playing in about 10 mins with battery temp about 32-33 degrees. i also noticed an infinite boot loop when turning on the phone with AC plugged in. (it starting to load sense and just after SD card preparing notification STABLE instant reboot, though it may not be related)
will try to use stock ROM today (i still have the very first nandroid backup)
Try to uv without oc...should get the temps down.
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Prema999 said:
Try to uv without oc...should get the temps down.
Click to expand...
Click to collapse
UV only kernel reported to have some stability probs....
when u use OC only kernel and, as in my case, set up max. freq to 998 it literally means that you just dont user any OC. so overclocking is not the issue...
jaymit said:
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Click to expand...
Click to collapse
My phone reboots when I'm playing robo wars, when the battery is LOWish and Im charging the phone at the same time. No battery warning, just reboots. If I have a good charge on the phone, and am charging then it seems fine. This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
gunja99 said:
This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
Click to expand...
Click to collapse
i got complete lock ups with only one game (heard rumors about it's bad coding style) the rest issues just reboots the phone. also i noticed that it reboots more frequent when using the phone and it's connected to charger simultaneously.
!!!UPDATE!!! 27.06.10
got back my Desire from the service after 10 days. They've changed motherboard (IMEI also changed) and no more overheating problems!!! HOORAAAY!!!!!!
It's working now even under high load!!!!

[Q]How to wake up w/o battery removal?

How to wake up the phone without battery removal? I have Virtuous 1.0.1 ROM with advanced kernel and from time to time I have wake up issue. I would like to avoid removing battery because I have otterbox case on my phone.
Do you know any other way to wake up yhe phone?
Well if you can't wake it up with the button on top it is a problem. Are you overclocked? Try lowering it.
Sent from my T-Mobile G2
Open the keyboard....lol
Sent from my HTC Vision using XDA Premium App
wake up
I have seen the same behaviour with the stock htc latest (1.82.whatever).
top switch -- othing
opening kbd -- noting.
only a removal of the battery seems to help.
Of course it hasn't happened in a convenient place e.g. to see if I can still access it or if charging works etc.
If u installed trackpad wakeup, it seems to distort virtuous roms and keep the device from waking up all together.....there are posts about it in the developers forum
Sent from my HTC Vision using XDA Premium App
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
There are 2 distinct "screen on" issues with slightly similar symptoms.
One is the "screen wake issue" what is common with Virtuous, and typically caused by certain combinations of overclocking, and screen off profiles.
The screen wake issue is very well discussed in the Virtuous thread, and commonly/easily solved with the proper screen off settings.
http://forum.xda-developers.com/showthread.php?t=967153
But the screen wake issue, as far as I have experienced, manifests with screen sometimes flickering on for a second, and sometimes responding to multiple presses of the power button, or by opening the keyboard. There is a different issue, some have called "SOD" (screen of death) where the phone seems completely dead until you pull the battery and reboot. This seems to be more what you are describing, but I'm not sure. The cause of the SOD has not conclusively been discovered, and there is currently no known surefire solution. But it may be hardware and GPS related, maybe kernel related. Personally, I've experienced this across several custom ROMs (Virtuous, CM7), kernels, as well as stock. The only luck I have had, is that the stock DZ ROM with the Godspeed kernel is the only combination which seems completely free of SODs. One person sent his phone into HTC due to SODs, and they said it was caused by a faulty GPRS module, and fixed it by replacing the mainboard. Another person send this phone in, and it was returned untouched, with the same problem still present.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
http://forum.xda-developers.com/showthread.php?t=908095
shortlived said:
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
KCRic said:
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
Click to expand...
Click to collapse
I had the screen wake issue on Virtuous, with NO screen off profile and OC'ed to 1 GHz. Making a screen off profile, but leaving a wide range for the CPU speed (not underclocking it) and interactive governor solved the issue in my case.
That might work better since most people I've seen tend to use the conservative or powersave gov. in their screen off profile. I'll correct myself too, what I said was from a CM standpoint since I've yet to use Virtuous.
Yeah, the screen wake issue on Virtuous is different from the one on CM7. If I remember properly, on Virtuous, using the advanced kernel results in screen wake issues for everyone or most people, unless you make some SetCPU/CPU Tuner setting adjustments.
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
qzfive said:
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
Click to expand...
Click to collapse
Completly agree.
I am shocked and appauled that most don't seem to understand that the os and it does not matter which(I.e. android,ios,windows) or platform (I.e. smartphone,tablet,desktop,etc) when you overclock more than just ur cpu speed is changed. If u have any experiance overclocking cpus on your home computer, you know u cannot let your system hibernate because it will not wake up. All operating systems allow the cpu to completly turn of in hibernation until it recieves an electrical pulse from the board. But if ur cpu goes from off to high it pulls way to much electricity and can't process then commands because all the recouces went to waking. If you have sleep parameters set with a narrower range the system will have enough resources left to process ur intial command...when it comes to sleep to wake there are no in between frequencies.
Sent from my HTC Vision using XDA Premium App

[Q] Screen won't wake due to OC

ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/

[Q] Unbelievably slow answer screen appearing

Hello folks,
first post, pleasure to be part of the group
Arc LT15i, 2.3.4, doomkernel#11, 4.0.2.A.0.42
more than 10 seconds to wait to be able to answer a call
takes 3-4 sec to light the screen (it's an eternity when you have to answer), and often first appears the unlock screen, then after seconds the sliding green botton.
really sorry for the noobhood, but any ideas?
thanks a lot
Cavin
I updated my phone to latest official firmware and i alos have this lag, but not that much. It takes 2 seconds for the screen to show who is calling and to be able to answer it, and it takes around 0,5 seconds when pressing the unlock button to light up the screen.
same problem when i was using stock rom
but when i moved onto MIUI,the phone is pretty fast and answer screen appears pretty quickly
Which CPU scheduler are you using? I have seen that using smartass or other schedulers which reduce the clockspeed on standby can reduce the responsetime of the answer screen.
setxperia raise the clockspeed on incomming call to make the response a bit better.... ;-)
Sent from my MT15i using Tapatalk
Thanks guys for answering
You're right! It's due to the clock's settings. May be, i'll come back to the former firmware any hints?
upgrading clock's frequencies works well, but drains battery faster (and this setup requires already a lot of energy ).
using "no lock" app, gains few secs
last night came up with the same good idea of using the incall profile
i noticed that using a too low min clock freq, the device is less reactive, although using "interactive", "smartassv2" or "ondemand". "scary" profile seems to work slightly better on incall reactivity. any experience?
Thanks
Cavin
If you use smartass (v1/v2), there's no need to set any profiles for screen off. The governor will stick to the lowest available frequency.
Smartass v1 used to have wake issues (on HTC Desire, at least), but v2 seems to be fine, I'm using it on the Arc S, I haven't experienced any lags with either stock or CM7 ROMs.
I'm not familiar with Setxperia and its settings, though, could something be set wrong, causing poor performance? Just a guess...
thanks
i noticed some lags with a very low min clock (e.g. 122), disappearing setting min at 8-900mhz (max 1.2ghz)
actually dunno why, but if i succeede in changing the rom discovering what to wipe, gonna tell you more
Cavin

[Q] Phone App wake up problem

Hi all
I'm experiencing issue with phone app. As you know, in call, the screen turns off when the phone detects something on the glass. The Note II is pretty fast to do that. But when you want to open contacts, or record the phone call, or find a mail without hanging up, it takes 3 seconds for the screen to switch on. Really annoying.
Sometimes it works pretty perfect, sometime not. I don't think it is a hardware problem.
3 seconds is pretty short but very long when you are in a hurry.
Is anybody else experiencing this kind of problem ?
I've tried to change the CPU governor and also the CPU idling rules.
=_=_=_ OMEGA 7.3 / redpill or Perseus
I've also flashed the stock kernel XXDLJ2 (seems to be a "little" more responsive)
Maybe I'm missing a tweak in stweaks that could solve this problem (ie: no underclock when calling or more CPU power....)
Thank you for help

Categories

Resources