Yank555.lu Android Stuff

Likely Ondemand will be a little more easily scaling, which may make up for what's missing, but from what I read, the issue is in the ROM, not the kernel.

But as I said, I can't comment that much except as to say this is something I've been reading accross devices, so it's very likely a ROM thing in that case...

Anyway, happy to fix it in the kernel if you can point me to what has to be done, or someone that has found the (technical) cause.

JP.

mikkysati wrote:
It is not.

Utkarsh explained it a little bit on XDA and it not related to CPU or Governor.

It's fixed on Omni. I listened to more than 2hs of music and did sttuter just once but that was me, I think. On other AOSP roms it would stutter every 15 or so seconds... very annoying.

I have tested the latest nightly(omni) music stops one or two times in one song during screen off. I don't know the problem is in rom or kernel as audio stutters in CM, omni and slimkat(with and without custom kernel). I havn't tried other roms.
But it is strange I havn't faced any stuttering in Ondemand governor[/quote]


I am starting to wonder if all this doesn't have to do with the bitrate, higher bitrate, higher cpu usage to decode. The complaint is common, "Audio stutters on screen off", yet I have had none of these issues using Omni, I actually ditched slim because it would stutter like crazy, even stop playing till I unlock the screen. Yet nowhere does anyone provide any info on the music: format, bitrate, file size etc.

When I get a call I can hear it, but the screen is going very late awake. So I can't accept the phone call. It's about 10seconds.

---------------
gesendet vom Barhocker

TylonHH wrote:When I get a call I can hear it, but the screen is going very late awake. So I can't accept the phone call. It's about 10seconds.

That is the price for using CPU screen off frequency limitation. You can increase the value (up to the same as screen on) until you get an acceptable response.

JP.

Hey yank, first of all thanks for the kernel i just flashed it (CM11) and it seems awesome, will report back after some usage.

But the thing that annoys me the most is the screen wake up delay (sometimes it's instant and sometimes it takes a few seconds).
Any workaround for that?

Maybe the post above yours will help

---------------
gesendet vom Barhocker

i tried that already, cranked it up to 600 Mhz. still getting delays :/

i flashed CM11 just because of this delay, i was hoping the delay would be completely gone.

As far as I know you will always have a delay on non sammy roms. Because Samsung didn't published the mali driver.
You didn't had that delay on CM before?

---------------
gesendet vom Barhocker

Hopesfall wrote:i tried that already, cranked it up to 600 Mhz. still getting delays :/

i flashed CM11 just because of this delay, i was hoping the delay would be completely gone.

Well a few things to consider :

1) stock screen off max is 1400

2) the wakeup lag is inherent to the Exynos platform (don't have it on Qualcomm)

3) governors behave differently, some rev up faster than others

Unfortunately there is no perfect medicine for wakeup lag, once the device is in deep sleep, it will not wake up instantly, and some battery saving additions may contribute to make it worse.

You need to find a balance that is acceptable for you, it will not likely get perfect on the i9300 ...

I've added a "wakeup kick" in my Note 3 kernel, which boosts scaling min for a certain time on wakeup, could help ... I'll try to port it to i9300 when I have spare time, but I don't think it will help, as I'm afraid it will be too late when it'll be activated (cf. point 2 above).

JP.

TylonHH wrote:As far as I know you will always have a delay on non sammy roms. Because Samsung didn't published the mali driver.
You didn't had that delay on CM before?

---------------
gesendet vom Barhocker

The delay is also present on Sammy ROMs, in fact, I found AOSP to be better in that regard already.

JP.