Develop Bugs

[Q] Incoming call lag problem in CM V7.1.0.1

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.

[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

Reason for Processor Speed as 800 MHz

Hi Wavers,
From last few days, I have read many posts saying “This Firmware is not final as Processor speed is still set to 800 MHz by SAMSUNG”.
So, I contacted Samsung via “Bada Developers” and asked them why they have set Processor speed as 800 MHz (i.e. whether Latest Firmware are final or not).
I got reply for one of the Bada Developer saying “800MHz on IDLE! If you start a Application or Game it goes up to 1GHz... (The same is on a Wave 3)”
That means, they have set Processor speed as 800 MHz only for idle state (No Application running) and it will goes up to 1GHz if you start Application or Game. And same is implemented for Wave 3.
So, I think SAMSUNG is right at least at this Time and Reason looks pretty logical.
Note: - I haven’t verified whether this is correct or not, as I haven’t flashed my wave 2 with latest firmware. Mods can verify this and let us know whether I and Samsung are right or not ;-)
Regards,
WaveGuru

hmmmmmmmmm
not totally true
i tried to check processor speed while game is running in the background and the highest number i got was 850 MHz only !!
Maybe Samsung missed something and limited speed to 850 only ?!
Best Regards

Tell that developer that he is dumbass. In idle mode ARM Clock goes to lowest possible frequency ~100MHz. But yeah, in many kernels I've been looking into it seems that they got upper limit of 800MHz.

Guys... i'm installing Zombie Infection via KIES right now and it shows 1000MHz. I didn't change anything in service menu. I have newest LA1 firmware. For me it usually shows 800MHz but it is enough to move upper beam and booom - it shows 950MHz right away. So i think the developer doesn't lie.

can you post which firmware version?

800MHz sounds reasonable on idle. Some droids (used to own an o2x, now I'm on a Wave 1) with go as low as 500 - 650 to up the powersaving. However, this causes the device to lag a bit when you wake it up. But that's very little inconvenience compared to the juice you're saving.
100MHz could be too slow when running background services such as radio, wifi, etc... I have no statistics though

kolo2x said:
100MHz could be too slow when running background services such as radio, wifi, etc... I have no statistics though
Click to expand...
Click to collapse
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.

Rebellos said:
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.
Click to expand...
Click to collapse
I've never used WinComm but it seems like a good tool. When you turn a phone off, you go in some "deep sleep" mode (yep it's not really off), which only runs the most basic of services. Services that poll your buttons or monitor certain interrupts that may cause your device to wake up such as some special alarms. Radio, wifi, and bluetooth are not among them. Embedded devices are required to drop their CPU frequencies drastically so you don't run out of battery.
Screen-off is another state that may just require disabling screen controllers, software renders, and the like. Some droids even turn off wifi on screen-off. I believe this is the idle state we're talking about.
From your observation, it seems the Wave's kernel is good at adjusting frequencies where needed. This could explain the good battery life this device has.
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
Rebellos said:
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.
Click to expand...
Click to collapse
My bad. I believe I've read your reply incorrectly. If WinComm says we're at 100~200 MHz on screen-off then maybe this is all it needs to keep radio, wifi, etc.
Good stuff!

More Govenors for CM7

Hi,
I was wondering if there was any effort to port the following governors to the Defy for CM7?
SmoothAss,
LagFree,
SmartassV2
I ask because I am using Smartass now and while it is great for the battery life(especially when you undervolt), it isn't as responsive when it needs to wake up on a call (screen stays black for 2-3 rings), and phone call processing can be kind of choppy when using HSPA (3G connection). Also sometimes the Mp3 playback skips when background data process goes off, or tower coverage changes.
---
I have seen SmartassV2 on Motorola DEXT and it rocks. 2 Days use worth of average phone use without charging.
Thanks in advance all.

tsurerb now
Any word on feasibility? Is this the wrong place to post this? I seem to have solved some of the problem by putting the first cpu setting at 400mhz. But it is apparent that the cpu never ramps to the second setting of 600mhz. I hear the newer governors solve these issues.

hi, dunno about supporting smartassv2, but you can set smt_sleep_max_freq to your clk2 speed, so in sleep smartass dont limit your defy to 300mhz. You dont be "saving" the batery charge like the smt_sleep_max_freq = clk1 but i think it will be better than having 400mhz in clk1

Is my Note 4 defective?

I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius

bucs9115 said:
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
Click to expand...
Click to collapse
Okay, so I got rid of my Note 4 so this is off of memory (full-disclosure). My Note 4 always ran pretty hot when it had to do anything. When flashing ROMs I'd be lucky if the CPU was below 70 C and any time I'd be playing a GPU intensive game it would get too hot to touch. I never had a lot of issues with the battery temp being too high though despite this.
As far as solutions go:
1) Screen res might help.....but I would try my other suggestions first
2) I wouldn't recommend disabling cores, it just makes the other two have to work harder to accomplish the same tasks and may be worse overall.
3) Kernel adiutor will allow you to do two things: adjust thermal throttling and adjust max GPU/CPU frequencies. I always reduced the max GPU frequency on this phone to lower the temps and adjusted thermal throttling to 55 C. The only CPU adjustments I did were to make sure the CPU wasn't overclocked.
4) I know you said it wasn't a rouge app, but get a task viewer (this is a good one) just to make sure (I had Nova taking 25% CPU usage in the background because I restored it from TiBu).
I saw your post in the NSeven thread and decided to respond, but please in the future try not to post errors in other threads unless you have the issue in that ROM. It sounds like you might have the same issue in that ROM as well, but you didn't say so in your post.

Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?

bucs9115 said:
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
Click to expand...
Click to collapse
You're welcome, and no worries for the post . As for your third point it would be really helpful if you tell me what you're running.
Could you list: kernel, ROM, root method, Android version, and any kernel mods (govtuner, skynet, etc)?
Also, does the same thing happen when you set a GPU max frequency? Have you tried having the settings run on boot and then reboot the phone?

Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol

bucs9115 said:
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
Click to expand...
Click to collapse
Since you're replying to both threads I'll keep my responses to your other Q&A thread to make life easier .