yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
There were a several reasons why not to implement this feature:

1) there are no settings that fit everyone. Personally, I don't need this, as with my usage I don't change my current config. As a side note, I also don't see any reason why to decrease max CPU freq since the phone anyway working only 0.5-3% of the overall time at this freq.

2) because of 1) I wouldn't probably really test a different configs, as I wouldn't use them :)

3) since the current kernel is supposed to work on different OS versions, it would be a pain to implement these profiles in every ramdisk. Now, with the support of an external *.rc script, it would be quite easily to implement this feature without actually touching any ramdisk, but because of 1) and 2) it's not implemented yet :D .

4) and yes, as for me it's annoying to set profile every time the phone is rebooted.
[Galaxy Ace II Android Development] bebolint98:
I didn't said that not possible to configure CPU-GPU frequency in your kernel.I write the sentence bad ,I meant that who use Chrono kernel probably use the CK Settings app also.It's like the novathor setting to your kernel.I use interactive gov. because for me the dynamic gov. have a worse graphical performance for example in 3d games.
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, what if someone needs to set higher GPU freq, or someone's phone, contrary, can't handle too high CPU/GPU freq? I believe it's not that way CPU/GPU freq should be managed, I was talking about this.

I do agree, there is no point to use overclocked GPU freq most the time, but overclocking CPU can't hurt much (if a phone can handle it, of course), at least using governor Dynamic, since the max CPU freq usage is negligible, unless you run some resource-hungry app.

As an example, the difference in power consumption between configs CPU 200-800 MHz and CPU 200-1100 MHz is insignificant. Why is that? Because of tunable power_optimal_freq(which is set to 800 MHz), CPU at once won't run at higher freqs longer than oc_freq_boost_ms. Did you disable this feature of Dynamic governor?

I can talk only about myself. I'm not a "fan" of a heavy apps or 3D games, so I prefer GPU to underclock/undervolt rather than overclock. My config is GPU 256/400 MHz, CPU 200-1200 MHz (heavily undervolted).

Ok, this is exactly what I answered about, above.
[Galaxy Ace II Android Development] ace2nutzer:
Yeb... it's disabled .. because i really don't like to have that delay ... if the power is needed then it should switch immediately higher ... not after xxx ms. This is just an performance "brake".. nothing else.

hmm okay if really so, than CM Perf. profiles is not appropriate for u. But if u don't use such heavy app and u don't play hard 3d games then using 1200Mhz is almost not needed. For u the Stock freqs (balanced) are probably more than enough.

As for power consumption between 800Mhz and 1200Mhz .. we (u i and mkaluza) did already power consumptions measurements for every CPU Freq ... (just search here on the thread, or my thread)

If i remember me correctly, the difference between 800 and 1200Mhz is quite big. So that it's really not worth to use higher freq. than 800Mhz at all ... but ... just for extreme apps there is no way to make it running properly with 800Mhz Dualcore ... (yes.. not quadcore)
[Galaxy Ace II Android Development] shaqman89:
Have anyone tried sending/uploading a video from Instagram or Whatsapp with CK kernel 3.10? It strangely fails or causes a reboot in my case. I'll check the logs a bit later, but just wondering if someone else has tried it.

The video was a mov format, 16 seconds long, with a size of 21 MB.
[Galaxy Ace II Android Development] ChronoMonochrome:
I think you misunderstood how this feature works. It's not a delay after which governor will switch to the maximum freq, it's a maximum time which CPU at once will stay at max freq. Thus, normally it can't use max freq for a long time or stuck at max freq forever unless some app forcing this.

And again, I didn't say that 1200 MHz == 800 MHz in terms of the battery usage. I only say that it doesn't matter, set you 200-800 MHz or 200 - X MHz (X here is any freq that higher than 800 MHz), if governor uses mostly only freqs that is not higher than power_optimal_freq, that is, 800 MHz. Setting 200-1200 MHz, on other hand, allows not to sacrifice the performance, when it's needed.

Is R3.10 only build version, on which this behaviour occurs?
[Galaxy Ace II Android Development] ace2nutzer:
Be sure that i know how dynamic gov. works ... the most tunables and features are just always for power-saving and not performance..

I'm here in order to improve performance... not to decrease it ;)

and yes this is what i mean ... and what i don't like. It reduces the Performance a lot ! With that behaviour it works most of time on that power optimal freq 800Mhz .. and the 1200Mhz are almost never used .. even when running AntuTu it stays painfully most of time @ 800Mhz !

This is like having a Lamborghini but u never give full-gas :cool:
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, then it's just a matter of preferences. I don't remember when it was needed for me to use CPU at max freq a lot time at once nor to run antutu. I believe, for such cases it's more appropriate to use another governors, since as you noted, performance (and especially in 3D games) decreases a lot. I didn't get it to work properly even with oc_boost_delay_ms feature disabled, in my case it was not as good as with governor Interactive/Performance. Did you do anything else in order to improve 3D performace when using Dynamic?
[Galaxy Ace II Android Development] ace2nutzer:
Nope, it's not needed to switch gov :) as i said dynamic performs better than interactive. (if tuned) ...

I'm really happy that i don't need to use interactive gov. anymore!

If u want to improve 3D speed, just compare the source of (my) dynamic gov, mali.platform.c (MaliAutoBoost), Also the Mali Utilization values and the DDR/APE Setting in the CPU Table .. where u can find the voltages too.. (i don't remember actually the filename since it's long time ago that i didn't change something there :D )

Also i've some tunables in ramdisk .. for just in case .. but i don't know if they really affect 3D speed... i think they almost improves I/O Speed:

write /sys/block/mmcblk0/queue/read_ahead_kb 512
write /sys/block/mmcblk0/queue/max_sectors_kb 4095
write /sys/block/mmcblk0boot0/queue/read_ahead_kb 512
write /sys/block/mmcblk0boot0/queue/max_sectors_kb 4095
write /sys/block/mmcblk0boot1/queue/read_ahead_kb 512
write /sys/block/mmcblk0boot1/queue/max_sectors_kb 4095
write /sys/block/mmcblk1/queue/read_ahead_kb 512
write /sys/block/mmcblk1/queue/max_sectors_kb 4095
write /sys/block/ram0/queue/read_ahead_kb 512
write /sys/block/ram1/queue/read_ahead_kb 512
write /sys/block/ram2/queue/read_ahead_kb 512
write /sys/block/ram3/queue/read_ahead_kb 512
write /sys/block/ram4/queue/read_ahead_kb 512
write /sys/block/ram5/queue/read_ahead_kb 512
write /sys/block/ram6/queue/read_ahead_kb 512
write /sys/block/ram7/queue/read_ahead_kb 512
write /sys/block/ram8/queue/read_ahead_kb 512
write /sys/block/ram9/queue/read_ahead_kb 512
write /sys/block/ram10/queue/read_ahead_kb 512
write /sys/block/ram11/queue/read_ahead_kb 512
write /sys/block/ram12/queue/read_ahead_kb 512
write /sys/block/ram13/queue/read_ahead_kb 512
write /sys/block/ram14/queue/read_ahead_kb 512
write /sys/block/ram15/queue/read_ahead_kb 512
write /sys/module/lowmemorykiller/parameters/minfree 10240,12800,15360,17920,30720,38400
write /proc/sys/net/ipv4/tcp_timestamps 0
write /sys/module/mali/parameters/pre_allocated_memory_size_max 33554432

Enjoy ! :highfive:

EDIT:

also it's very important to use APE/DDR 50% for screen ON .... otherwise u'll have always problems with 3D/2D Games ...

Just use only 25% for screen OFF .. it can't hurt ;)

Also make sure that min GPU Freq is not lower than 300Mhz when running @ APE100 ....

When is on IDLE --> APE 50% .. GPU freq is only half = 150Mhz...

But only if something is redrawing the screen ... for example: charging animation !

If the screen is completely freezed .. but ON ... and u don't touch them .. then GPU Clock is insanely @ 0Mhz !!!
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm not sure if it has something to do with DDR/APE.. since after switching to Interactive it was working better. Not that I need improved 3D performance, I was asking mostly out of curiosity. But anyway thanks, I'll compare Dynamic governor sources.

Quite a lot of optimizations here :) I think I need to check this ramdisk as well :)
[Galaxy Ace II Android Development] shaqman89:
I'm not sure yet. I tried 3.10 both debug and non debug version, both give same result. Strangely, I didn't saw anything weird in logcat. Just some calls to omx codec something and then nothing.

Say, which log is best to debug this? Whenever I try to open the video, it loads for a moment and then it reboots.
[Galaxy Ace II Android Development] ChronoMonochrome:
Try this build http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/chrono_kernel_r3.10.1.zip

I suspect the recent binder driver update. Since I saw some errors in logs about binder, I reverted this update. Also, logs now should provide more information, because of re-enabled debugging features.

P.s. I think last_kmsg should be more informative than logcat here.
[Galaxy Ace II Android Development] PolishVodka:
Chrono

As I know, our camera sensor is Samsung S5K4ECGX 5MP and driver for it is U8500 MMIO DRIVER, but can we use this one? http://code.metager.de/source/xref/linux/stable/drivers/media/i2c/s5k4ecgx.c

I'm asking because hardware is the same like on Nexus S, so after changing camera driver in kernel, can we use camera hal from Nexus instead our outdated blob? Is any chance to working this?
[Galaxy Ace II Android Development] ChronoMonochrome:
This sounds interesting to me. Yes, I think it's possible theoretically, but practically it might be not so easy. First of all, I have some doubts about which drivers to replace instead of this one from tuna. We have camera drivers in drivers/staging/mmio folder, which nexus s apparently doesn't use, but there are some more drivers such as microphone driver etc, and also present some samsung device-specific changes, which of course will absent in that driver from nexus s. Anyway, I think it worth trying.

EDIT.

Just found that using this driver requires some board specific changes, we can't use which. Although the camera module is same, GPIO isn't..
[Galaxy Ace II Android Development] shaqman89:
I tried it, but it's still happening. The only difference I notice it that, now the reboots doesn't occur as much, but sometimes is replaced with a freeze which I have to force restart the phone by long pressing the power button.

Here are some of the logs from the tests. It's incremental by number: https://drive.google.com/folderview?id=0Bzo3MSxg_YFCdEYweXc3M0hJMjA&usp=sharing

Last kmsg: https://drive.google.com/open?id=0Bzo3MSxg_YFCdVVfQ0ZkNUY4ZTQ

Last Logcat before it rebooted while trying to send a video: https://drive.google.com/open?id=0Bzo3MSxg_YFCYm5DUTNjS0ZTczA

The video I was trying to send: https://drive.google.com/open?id=0Bzo3MSxg_YFCWGFFbEl2bktXTFU

Furthermore, I tried sending another video, that I recieved from whatsapp to another contact works. But the video in question itself is also sendable since trying to send it from another device (Xperia C with ArchiDroid's KK) works, so I'm sure the video itself is okay.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, the binder driver is an issue here, last_kmsg you sent confirmed this.. Can you try R3.5 - this is a nearest build with a different binder driver. Which ROM you are currently using? Can you check if this issue is also exist on ace2nutzer's kernel?

P.s. according to the log, the data on your external sdcard might be corrupted.

BTW. why you are using PLLDDR OC init.d script even though it causes reboots? Also, GPU config you are using isn't stable.
[Galaxy Ace II Android Development] shaqman89:
Just tried out 3.5.1, but unfortunately can't get it to boot. Here is the last_kmsg for that:https://drive.google.com/open?id=0Bzo3MSxg_YFCUlRXNnVnaVMyaGs

After that, I tried using ace2nutzer kernel 20151108 version, and it seems to work better. I mean better as in to say no reboots happen, though it still failed to send the video, both in Instagram and Whatsapp. The log is saying something like path not found. Full logcat is here: https://drive.google.com/open?id=0Bzo3MSxg_YFCenRZTmZ1MjBrVm8

About OC_DDR, it usually works stable in my case. I do admit that during testing this out, it casues a reboot twice, thus the three last attempts , I tried after removing the script. On the GPU, I believe I set everything at default in CK. I only played around with the IO parts. Could you point out exactly what configuration is unstable?

Strangely I haven't had any issues with the current configuration. But it did went wayhire after the instagram issue.

When you say external storage, what does that actually mean if I swap memories? I did thought of data corruption, thus I did a chkdsk to the extenal memory card and found nothing.

Currently I am using the latest build of your Vanir. Judging by the error you mentioned, seems like a combination of a bad configuration (which I'm not sure where it is set) and corruption. Would it be better if I just do a clean install?
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, my bad. On r3.9 module pn544.ko was added to the autoload list, but r3.5.1 doesn't handle extraneous modules-leftovers from another builds(particularly, this is leftover from r3.10). Wipe out /ramdisk/modules/autoload and /ramdisk/modules/ folder before you install this version.

According to the GPU errors from the log, 730MHz is too high freq for this device. Usually nothing bad can happen, just it will cause freezes and glitches.

I was judging by these errors:

[ 55.833923] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x900
[ 55.834106] mmcblk1: error -70 transferring data, sector 10999664, nr 16, cmd response 0x0, card status 0x0

This not necessarily means that the data is corrupt, but could be a reason for kernel crashes. I don't think clean install is needed as errors anyway were from external sdcard and not internal.
[Galaxy Ace II Android Development] shaqman89:
Okay, now it works like ace's kernel. No reboots, but still failed in sending. Checkin in the logcat, it still shows similar entries. Could it be a ROM issue, rather than kernel issue?

Very strange. 730MHz is a very old configuration. A month ago, since I don't play much games anymore, I've set it to default (480 MHz) so it doesn't consumes too much power. True, I didn't check whether it was applied correctly, but I assumed CK set it properly. Nevertheless, it didn't cause any glitches I know, so far.
[Galaxy Ace II Android Development] ChronoMonochrome:
It's fairly enough difficult to say if it's ROM or kernel issue, both of ROM and kernel could be a problem. The faulting driver is still very buggy, unfortunately, fixes from upstream doesn't seem to be very helpful.
[Galaxy Ace II Android Development] shaqman89:
It seems it's also happening on AICP with CK 3.5.1.

Update: It seems related to some codec or something. Specifically, when the video format was mov, it had the issues I mentioned, but as soon as I convert it to mp4, it worked flawlessly.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R3.11 is UP!

Changelog:

some config optimization

applied ux500 some mainstream patches to machine-specific code

zram:

optimized for better compression speed and ratio

used two compression streams instead of a multiple zram blocks

set zram size to 385Mb and swappiness to 100

limited compressed memory page size to 1365 bytes

(this parameter is accesible via /sys/module/parameters/max_zpage_size, should be between 0 and 4096)

Zram might be less swappy(even with swappiness set to 100%), but should guarantee better compression ratio (not higher than 1/3). This is achieved by selective pages compression: only pages with compression ratio not higher than 1/3 will be stored in zram block. Because of this limitation, swappiness is set to 100. This is better than having 30% swappiness without limitation on compressed page size, as allows to compress as many empty(or almost empty) pages as possible. For more details, refer this commit.

Enjoy this build!
[Galaxy Ace II Android Development] TheLiquidGuy:
So, I have a problem with TC's 4.4.4. I have installed chrono kernel r3.10 and I brought back performance governor and I/O scheduler tripndroid with 1.2Ghz and it is stable but something is wrong with the battery. The last few times when I had installed 4.4.4 always was doing so. When the phone is locked and something is draining battery. Over 40% for 1 night without touching the phone and around lunch the next day it is like 15% or so. When I was on LP I had the same apps but I didn't have the issue. Please help me!
[Galaxy Ace II Android Development] junnickbefore14:
After I flashed the latest kernel, the value of max_comp_streams is still 1..

I'm using your Omni rom 5.1.1

Am I missing something?
[Galaxy Ace II Android Development] ChronoMonochrome:
Not sure what the problem is, recently I faced exactly problem like described here, on both 4.4.4 and 5.1.1. Check if there were wakelocks. Dmesg logs also could be useful. In my case there weren't any wakelocks that would keep the phone awake. On omni 5.1.1 this issue went away for me after I restored old nand backup.

My bad, this is because of wrong zram configuration order, will fix in the next release.
[Galaxy Ace II Android Development] junnickbefore14:
You mean that the parameter set by init.d script?
[Galaxy Ace II Android Development] ChronoMonochrome:
This parameter should be set once after zram module is loaded, but not after zram size is set.
[Galaxy Ace II Android Development] junnickbefore14:
Great!!

Now I have 2 streams

Thanks Chrono!!

You made my day
[Galaxy Ace II Android Development] TheLiquidGuy:
Something is keeping the device awake and I don't know what. Tell me how to get these Dmesg logs and I will get them for you to help me because this is so annoying. I cannot rely on my phone because of this battert :( :( EDIT: Look this screenshot - I barely touched the phone and the battery dropped from 100% to 86% in 2 hours.
[Galaxy Ace II Android Development] gothicVI:
You could try batter battery stats to find out. There's a paid version on Google play store and a free one for the xda community in the development thread in this forum.

Gesendet von meinem XT1072 mit Tapatalk
[Galaxy Ace II Android Development] xo.en:
Guys, I have problem with restoring backup under twrp:

e:cannot restore system mounted read only

What can I do?

I am trying to restore my vanir and after flashing ressurection rom I am unable to...
[Galaxy Ace II Android Development] ChronoMonochrome:
Which version of TWRP you're using? If 2.8.7.0, then downgrade first to 2.8.6.0, this bug appeared in 2.8.7.0.
[Galaxy Ace II Android Development] xo.en:
Which kernel of yours has this one version?

btw, older kernels(i mean twrp) cannot see my backup at all....I am absolutely sure, that I managed to restore this specific backup some way before..now I am stuck...damn.
[Galaxy Ace II Android Development] ChronoMonochrome:
Can't remember, which version is the latest that has TWRP recovery, since a while CK builds comes with Philz as default recovery. Furthermore, installing those old versions likely will require manual cleaning up leftover autoload modules. Why just not to proceed installation from TWRP topic?
[Galaxy Ace II Android Development] xo.en:
What...topic..I ran into problem using your kernel...I REALLY need to restore my backup...

I never ran ito such issues before.

HMM, I do not understand - every kernel I am flashing has philz recovery, so, how I got TWRP before?

Help, I really need to restore twrp backup...
[Galaxy Ace II Android Development] Culateralligator:
Not sure I understand well.

A different way to get TWRP is, for example,flashing Sergeyl CM12. Then you can restore your backup.
[Galaxy Ace II Android Development] shaqman89:
Latest kernel is also using Philz recovery. So I'm sure you didn't get TWRP from Chrono's kernel.
[Galaxy Ace II Android Development] borkins:
Hi! Try flashing this.
[Galaxy Ace II Android Development] gothicVI:
Is there a specific reason for this? I'd prefer TWRP to be the default one since there are way more possibilities and less trouble as e.g. with xposed framework.

Gesendet von meinem XT1072 mit Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
Personally I prefer and use TWRP too, but it was easier to integrate Philz, since it use generic fstab(so there is no need to support the internal fstab as TWRP require). It's not difficult at all, though, just flash zip with TWRP once, this recovery won't be overriden by kernel installer(unless user delete recovery file), so I don't care much about TWRP integration to this kernel.
[Galaxy Ace II Android Development] TheLiquidGuy:
Today I almost didn't touch the phone. Look what I got from Better Battery Stats. My phone doesn't go in deep sleed mode. Something is holding the phone awake and the processor is running at 1200mhz all the time. Here some screenshots. [MENTION=5695278]ChronoMonochrome[/MENTION] please help!
[Galaxy Ace II Android Development] Ave_Hornet:
[MENTION=6700131]TheLiquidGuy[/MENTION]

Facebook, Google play services.
[Galaxy Ace II Android Development] TheLiquidGuy:
Did you even read what I said yesterday? I had teh same apps in LP and I didnt have the problem.So it is not it!
[Galaxy Ace II Android Development] ace2nutzer:
turn wifi on (with working internet) and reboot the phone .. then let it for 10 minutes with screen on .. or plug the charger in order to keep the phone on wakelock ...

Google Play Services + Facebook will access to the internet in order to do somewhat .. (update, sync etc..)

After this the Phone will go normally into deep sleep.

If u've always no internet connections .. then some apps try to make something with internet .. which isn't there .. and that cause high cpu load and wakelock.

What also can help: try to open "Play" and try to update some apps manually ...

For me those steps helped to solve wakelock issue !
[Galaxy Ace II Android Development] TheLiquidGuy:
Thanks! I will give it a try! :highfive:

Edit: Not working. Still draining battery. I do not know what to do now. :(
[Galaxy Ace II Android Development] xo.en:
Thanks mate, will do.
[Galaxy Ace II Android Development] ace2nutzer:
Try this steps:

- find out which app is causing that high load by typing "top" on term. emulator.

- delete that (bad) app, or try first wipe data of this app.

- Check again with "top" ...

- No way ? - Then make sure to use Dalvik on Kit-Kat based ROM's ... also it's better to use ext4 instead f2fs.

Usage of TOP ....

after u've started "top" on terminal.. then long tap on the text and choose: "Send control key" .. now press "c" on your keyboard..

Now hide keyboard (1x back button) and scroll up .... u need to find the beginning (first line) of the showing processes .. because it's sorted from high to low cpu usage !

( u can see for every line (process, app etc.) the CPU% load .... )

That's it ! :highfive:
[Galaxy Ace II Android Development] bebolint98:
Somebody know a good fm radio app which is work offline? I only found the Spirit but it's not give sound In the speaker only in the headset.
[Galaxy Ace II Android Development] Culateralligator:
Yesterday I flashed Chrono kernel 2.24.7 cause I was going to install Sergeyl CM13 and .... I found 2.8.6.0 TWRP! I wasn't using it, as I have Vanir + Ace2Nutzer with CWM.

That was not a problem, cause rom was succesfully installed. But before that, I was curious and I took a look at my old TWRP backups and non of them appeared. Then I flashed TWRP 2.8.7.0 and appeared only 2 of the 3 I have.

Very extrange, isn't it?
[Galaxy Ace II Android Development] xo.en:
Yup, it happens from version to version, it seems...weird.