yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] xo.en:
Holy crap, this is insane :)

p.s. oh no, performance control is not able to control cpu anymore;/ ...but chronokernel, can manage this...can i add additional governors/i/o modules with it for latest kernel? Will it work?

I feel off my chair seeing how browsers work now. Oo. This thing is faster than my laptop now, lol. Shame that i am not able to get >1.2ghz anymore, but...

This is unreal. I wonder, how battery will behave(on polishvodka's kernel i had c.a. 11-14% loss, daily, at 800mhz). So far, it is not good, battery loss is fatally big(did not make recharge cycle curing yet).

btw chronokernel crashes when i choose i/o settings, hm. is there newer version than 0.97? Is ddr control planned for chronokernel app?

ehh, p.s.: i have promo text for this version:

"Canabalt had never been so smooth."

2d performance was always issue with this machine(besides ONE build of 4.2.x slimmerbean).

I definitely can see cure for this with this kernel...i wonder, what EXACTLY is responsible, as it could be used for older, typical kernels for those, who not need nothing fancy, imho.

Definitely, solution is there, i can see it.

At the same time, i cannot understand, why 3d performance is...HALVED.

HALVED.

At all tests it is almost HALF of what i remember. Huh? It's matter of some kind of forced Vsync?

You know, i am not playing much 3d games(ONLY emulators, usually driven by 2d), but..this caught my attention.

Something troubles me - i have s6d - and i NEVER been able to oc gpu, i wonder, if it is related? OC of gpu is not working, can someone cofirm this?

Btw - 50hz + uae4all2...if it works...:D

Yup, it seems that 50hz works fine with Amiga emulator(s6d)..ok, need another beer now(and usbhost)..this is ****in' insane(700mhz + FS1 in emu still does the job :) )..

http://s23.postimg.org/emb0x7k5n/Screenshot_2015_03_17_23_36_31.png

Now it is time for Desert Dream by Kefrens(and then its remake for c64 :D )..

...tomorrow i will be grumpy, as usual, i am afraid...but holy f, if anyone uses emulators, and PAL soft- check 50hz...

http://s3.postimg.org/s4wy8caar/xoen_Screenshot_2015_03_19_16_09_39.png

...off to see 9fingers now.

btw, i'd recommend postimg as host for screenshots - somehow ics are not dissaearing so far(for years) from there.

Also, it may save xdadev overloaded servers, too.
[Galaxy Ace II Android Development] ChronoMonochrome:
Have you tried to clear data of app? Otherwise, post logcat, please. P.s. 0.9.7.5 is available, maybe mars_army will upload it soon here, otherwise I'll do it.

Maybe you're talking about touchbooster, because even with lower GPU settings it works pretty smooth.

Did you use Dynamic governor when testing 3D performance? It's not a very good in gaming performance or benchmarking. Though, it was never for me halved too. (tested Dynamic/Interactive in nenamark right now - results are 41.6 and 51.6 fps respectively - GPU 400-715 MHz, DDR 798 MHz).
[Galaxy Ace II Android Development] nikolas1274:
I have problem with wakekocks too, it does not go too deep sleep at R2.21.1.

Any suggestion?
[Galaxy Ace II Android Development] monstro78:
Personally I have better performance and smoothness with 2.20. Last version seems not so fast... I have not tested 2.21.
[Galaxy Ace II Android Development] ace2nutzer:
Check this and report what u see in:

/sys/kernel/debug/suspend/deepsleep_failed
/sys/kernel/debug/suspend/sleep_failed
/sys/kernel/debug/suspend/deepsleep
/sys/kernel/debug/suspend/sleep
/sys/kernel/debug/suspend/enable
[Galaxy Ace II Android Development] sleepless9:
Wakelock problem and wifi on latest kernel

I am also experiencing battery drain in TC CM11 due to system.update.service in Google Play Services after upgrading to R2.21 (checked with Wakelock Detector). With R2.21.1 the problem remains but I managed to work around it using App Ops (everything else I tried only worked until reboot).

Anyway, I had to downgrade the kernel because R2.21.1 is breaking the wifi driver. Trying to insmod manually gives the following error in dmesg:

[ 1577.319091] dhd: disagrees about version of symbol sched_setscheduler

[ 1577.319122] dhd: Unknown symbol sched_setscheduler (err -22)

[ 1577.319183] dhd: disagrees about version of symbol wake_up_process

[ 1577.319183] dhd: Unknown symbol wake_up_process (err -22)

It makes some sense since the changes were in the schedulers (but why would wifi depend on an io scheduler?) and the wake_up_process may relate to the wakelock problem. I hope this log helps solving it for the next stable release.
[Galaxy Ace II Android Development] nikolas1274:
Here it is
[Galaxy Ace II Android Development] ChronoMonochrome:
Why do you relate this to kernel? Wakelocks is a crapware problem, not a kernel. Can't imagine how can kernel cause problems which actually does Google apps services. But maybe later I will be able to write a black list for a wakelocks to prevent some annoying apps from keeping the phone awake.

Not sure, whether it has something to do I/O scheds. For me wifi works as well as with previous builds. Check, whether /system has enough space for modules.

Enabling zram by default with swappiness=100 was a hasty decision. I also confirm a bit lagginess, when zram block is almost full. Try to disable it.
[Galaxy Ace II Android Development] Alucard:
Please someone help me,wich version is for stock JB and wich for kk roms?
[Galaxy Ace II Android Development] sleepless9:
I don't get it either. I just didn't have such problems with R2.17 and previous kernels. It started yesterday, right after flashing R2.21. I made some tests for a few hours, then downgraded to R2.17 and problem was gone. I flashed the R2.21 again, problem was there. Anyway it is not of importance because the App Ops solution worked well.

It has about 40MB free space now. Is this ok? Also, the flashing with TWRP was successful. Wouldn't it fail if low space was an issue?
[Galaxy Ace II Android Development] ChronoMonochrome:
Don't have any ideas then. Maybe it's better to ask google devs :laugh:

40Mb should be enough. Can't be sure whether low space will cause fail when flashing - since I've done repartition I never had problems with low space on /system.
[Galaxy Ace II Android Development] xo.en:
..Chrono, what is this: i fully charged machine, refreshed battery stats and - voila - suddenly from 100% machine says i have 92% of battery load. In 2 seconds it fell from 100% to 92%. Old kernels max load was 95% real, here's 92%...

Hm, while i was writing this, it dropped in minute to 91% :S

Damn, it is really creepy - i say it again - day before yesterday i was on polishvodka kernrel - performance was great. And listen to me - machine lost up to 11% for whole day at same conditions as today. From 86% to 75% for WHOLE DAY.

With this kernel and same settings it loses charge literally on my eyes, this is totally different behaviour than i would expect, damn..

I mean, allright, i am not familiar with your kernel dymanics - because it is all about dymanics - but...isnt it too much loss? -196mA, imho is...quite devastating at idle usage(chronokernel measure)? Again - i have weird feeling, that UV is NOT working here, i set -50mah to -19mah depending on cpu mhz, it seems to have totally adverse results(?).

With Vodkas kernel i even did not try UV, and it worked miracles, here it simply is draining as hell.

Or...this totally magical i/o governor takes so much(i can see how BIG real gain that gov has, but...)?

F, i may be drunk, but i am not seeing things, i set up machine to as same setup i was using for months i could here.

Battery drain is tremendous - what do you think, is is that that insane fluidity of 2d that i was talking about that takes that energy?

(i can provide Vodka's kernel to comare that drain, difference is insane :S.

(sorry for my english - i should, as my ex-premier - Tusk - polish my english..but you know, he earns little more and hes feed well, ****ing traitor he is, Merkel handkerchief, focker).

btw, is it big strain on you making different hwmem versions to test?

You know - i will have big concern now - i saw how 50hz lcd effect works - every emulator of OLD machines(PAL) seems to LOVE it, fluidity is just insane. But wtf is with this batt drain :( ?
[Galaxy Ace II Android Development] ace2nutzer:
looks normal.. then it's not kernel fault.. it's like always Google Play Services and the Google Search engine...

Personally i've freezed the Google Search App ;)
[Galaxy Ace II Android Development] nikolas1274:
Thanks
[Galaxy Ace II Android Development] Ave_Hornet:
Before you go to the wave of criticism that ChronoKernel dont go into DeepSleep : D

CM12 solution provides for it because now I'm using: > I admit that the work can also on CM11 but settings may vary away from those at the CM12

>>>>>> the things we enter into Settings> Privacy >privacy protection > press menu button > select ' show applications built into the system '> looking for " google services play ' hold long on it > uncheck ' wake up ',' do not fall asleep ' , ' autostart ' <<<<<<< and the same goes for the shop play .for me it works and my Ace goes into DeepSleep as it should

Greet
[Galaxy Ace II Android Development] ChronoMonochrome:
Percentage drop right after recharge is a really annoying thing, and I'm not sure where's it came from. Later I'll look into it.

No big battery drain for me - attached screenshot below - Dynamic/FIOPS. Check whether CPU voltage applied correctly - I remember report that something causes CPU overvolt by default (I'm not sure what it's - since I use init.d script for UV).

Not a difficult for me - but since I've identified that lower hwmem causes some problems with apps like FC, it makes less sense to test it again.
[Galaxy Ace II Android Development] xo.en:
Chrono, your drain measures are about 100mah LESS than mine. Am i missing something, or is it s6d...present for christmasS?

Like i told you - UV seems to not work for my machine at all(i already lessen cpu to -50ma, and gpu to - 25ma). IT seems to not work, dammit.

Btw yup, i am at dynamic/fiops.

Indeed, fiops makes miracles( i am not using card swap, usually i am, but for tests i am not swapping).

I mean - difference from vodkas kernel WITHOUT UV..:S Really, difference is ter-ry-fying(dividing of this word varies from school to school :) - these rules applies in my laguague too, it is funny, to some extend). Not that is visible, or, significant, or, measruable, difference is ter-ry-fy-ing.

you know, guys - my machine was swimming/bathing below 05.metre once, for some time i thought, that it may have some influence on overall battery usage(how sweet was seeeing working screen on bed of my bathtub...it just worked).

But since this ridiculous accident machine hold current perfectly).

So, different kernel is not related to this occurence.

Then, logic says - why vodkas kernel has ZERO unusual drain?

Ok, more beer, and time for BubbleBobble on c64.

Man, you made long journey with this kernel, i admire it.

Hm, thing dropped from -192 to -121ma, now i am not sure, if it is typical drain for a2 at 800 mhz(whatever cpu/i/o gov is)...i stopped with 624xscale cpu, that used -32 idle at 624x480...:)

My posting is not thought as harasaement(msg to post viewers) - i just trying to test this kernel for first time.

Anyway, i'd better shut the f up.
[Galaxy Ace II Android Development] monstro78:
OK that's funny... I enable zram from chronoapp, reboot and then lagginess gone. Device is fast and smooth now, but I check CPU statistics and I also have deep sleep issue...
[Galaxy Ace II Android Development] ChronoMonochrome:
Right now checked kernel defaults - it's just 4mah more than before in idle. Have no idea about this unusual drain. And cannot relate this to s6d - so far nobody reported about such problems like that battery drain. Maybe dmesg log can sched some light.

What do you mean by that it doesn't work? IMO, -50 mA is too low to even notice any gain from it (esp. in idle). As I said, even extremal UV(like in my case) doesn't show any difference with no tweaking at all when is in idle. But it can do more difference when CPU/GPU are more loaded.
[Galaxy Ace II Android Development] ace2nutzer:
Set min CPU Freq @ 200Mhz and Phone in Offline... then Brightness @ 10% then u should have 95mA Power consumption.

(u need to wait some seconds.. then it'll go to 95mA .. if u're scrolling or checking the Value very fast.. then CPU load is high.. and the mA Value is over 150 - 200mA .. and this is fully normal !

Memorize this in your brain: It has nearly nothing to do wit UV ! No matter if CPU or GPU !

Power consumption are coming from other Kernel Settings,, like Min CPU / GPU Freq, and DDR/APE for IDLE ---> 25/25 or 50/50 or 100/100 %

And other Kernel Configurations like, I/O Sched, CPU Gov, WQ_Power_efficient, Sched_mc_powersavings, Enabled or disabled SPI_CRC, FSync Mode and and and ..

Every Kernel (even from same developer) version have different configurations....

The Other big Problem is when users are switching between different kernels, and don't uninstall the Old Kernel.. I mean: Chrono-APP, NT-APP ... and also init.d scripts ! That all is responsible for big confusion and malfunction.. so that at the end no matter wich kernel u'll install, u'll have still problems cause of dirty installation and kernel misconfiguration ....

I'll make a uninstall_ace2nutzer_kernel.zip for recovery for

painful

uninstalling like Chrono said :D
[Galaxy Ace II Android Development] xo.en:
Wise words...

Hm... you know - i see it as interesting journey....interesting journey, that is.
[Galaxy Ace II Android Development] greeceeeee:
i tried it but it doesn 't work,the value still the same....
[Galaxy Ace II Android Development] ace2nutzer:
U really don't need to change any Voltages.. this is not a Toy. ;) Let just Kernel defaults... they are already optimized for good stability and also powersaving ... only in very rare cases, if u've stability problems.. then it makes sense to increase the voltages over init.d scripts.. that's it !

After executing the command for new Voltages they are directly valid.. no need to reboot. just do echo .... in term. emu.

The other possible Thing: the last time i've tested Chrono Kernel here, i've see that min cpu freq by kernel default is 400Mhz but it's showing anyway as 200Mhz ! That Config will cause high battery draining on suspend because on 400Mhz APE/DDR is running @ 50% instead of 25% for screen off.

(in my kernel min cpu is also 400Mhz.. but DDR/APE is 25% for screen off) - I think Chrono u can fix this in CPU Table simply.
[Galaxy Ace II Android Development] ChronoMonochrome:
Dammit, that's what I forget about, since I never used default preferences. Though, this can't explain huge battery drain (and can't cause it) - as I previosly saw - it's about 4mah more than usually.
[Galaxy Ace II Android Development] shaqman89:
In all fairness, that is actually a possibility :D

Or to be exact, google is not entirely clean of any faults.

But, considering the next tests I did:

- I flashed 2.20 back (the last kernel I used that have no deepsleep issues), the issue persist.

- I flashed 2.21, issue seems to persist for a moment

- Now using 2.21.1, no issues with deep sleep.

This might indicate a configuration issue. Maybe something just didn't played well at first.

We have to admit, we have come a long way with (like so many has pointed out) so many combination of configuration that makes it not that simple to really determine the cause of an issue.

[MENTION=5933530]xo.en[/MENTION]

I haven't per se used PolishVodka's kernel recently, but in my case battery life has been the best on the 2.21.1 of chrono's.

If in your case you literally thought that the percentage are falling, I thought my battery indicator was broken since it did not move even a percent after more than an hour. I haven't experienced that kind of battery efficiency before in my phone.

[MENTION=5695278]ChronoMonochrome[/MENTION]

After using the kernel for > 2 days, I could confirm that it becomes lag after a day or so, and true that there are (strangely) some battery drops.

In addition about HWMEM, is it still possible for us to flash the Memory repartition on your latest kernel's?

I didn't experienced any FC's when using 68, or 72, so I think it'll be a good idea to make that as an option. Not that I am complaining about bad experience in multitasking.
[Galaxy Ace II Android Development] ace2nutzer:
I don't think it's possible, because Mem part. is writed in bootloader.. and the kernel can override that kernel command line... that command line is coded in kernel... u can simply download the kernel sources from Chrono Repo. and edit the HWMEM @ what u want and just compiling the kernel.. that's it !
[Galaxy Ace II Android Development] ayas02:
until R2.21.1.1 i cant still playing game with ipega (i meant all button doesnt work) maybe [MENTION=5695278]ChronoMonochrome[/MENTION] can implement BT Driver from old build

thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
Uploaded R2.21.2. Mainly it's various fixes:

- re-enabled 200 and 300 MHz to recover APE=25 and DDR=25 for screen off. It's a lesser evil than with 400 MHz but APE50 and DDR50, hope, later I'll rework this part of LiveOPP completely, cause now I'm out of time.

- reverted some changes in abb-charger to fix issue with charge drop

- removed 60++ Hz mode for LCDCLK. Interface renamed to lcdclk from mcde_cldclk. I noticed that somehow 60++ Hz was used by default, more strangely, that this caused bootloop for me.

- HID drivers now compiled built-in, to fix not working UHID

- uploaded also version with hwmem 68M.
[Galaxy Ace II Android Development] ace2nutzer:
Right, but just changing APE/DDR 50% @ 25% for the 400Mhz step is the same, bro ;)
[Galaxy Ace II Android Development] ayas02:
really chrono?
[Galaxy Ace II Android Development] ChronoMonochrome:
Not a same, you're talking about two different sets. In case to prevent any possible problems with it I use simplest variant. This just is to avoid configuring APE/DDR for those who don't use 400 MHz as min freq.
[Galaxy Ace II Android Development] ayas02:
Great thanks for fix HID but lcdclk still blink when i set 60 and 60+ how can i fixed it [MENTION=235339]chrono[/MENTION]

thannks
[Galaxy Ace II Android Development] ace2nutzer:
Hmm... this is usually also no problem...

u've now this:

with min 200: Screen ON DDR/APE 50% due to lcd requirement and 25% for screen OFF.

with min 400: Screen ON DDR/APE 50% due to lcd requirement and 50% for screen OFF.

If u use my idea, then u've also with min 400, 25% for screen OFF ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
But on yours build min freq=200 MHz is not possible, or am I wrong? Okay, user can tweak liveopp step to use 200 MHz, but we again came to fact, that it also requires some changes, which are non-obvious for someone.

Anyway, it's possible to use minimum APE/DDR stats with don't matter which min CPU freq(whether 200 MHz, 400 MHz or whatever), with no tweaking anything. And it should be more less easy in realization, later I'll do so.
[Galaxy Ace II Android Development] shaqman89:
Logcat issue

Has anyone tried using logcat on ART with latest builds? I remember that it had worked before, but that has been a while.

In my case logcat seems a bit strange in the sense that it does contains logs, but does not contains anything about the applications that I am trying to debug.

I have put logger.ko in autoload folder, and judging by /dev/log/main it sure looks like it's working.

Anyone else experiencing this?
[Galaxy Ace II Android Development] fluffi444:
I can speak only for myself - I never had problems with 60++ - And I set this for standrad with init.d here...

But because of DDR 975 the LCD-clk could be a bit lower than the value you have on DDR 798... We saw recently that DDR OC is connected to LCD clk.

And if you want to ask.... Yes - I see the difference between 60+ and 60++ :D And I like it...

Or is there a way to use this "custom -2" trigger in LCDCLK?
[Galaxy Ace II Android Development] ChronoMonochrome:
For me this causes horizontal lines in the bottom of the screen sometimes.

echo lcdclk=66560000 > /sys/kernel/mcde/lcdclk
[Galaxy Ace II Android Development] fluffi444:
Yes - but keep in mind that if DDR OC (975) is used the LCD is lower as with 798... Therefore users with 975ers can use 60++ more often/quite save..

60++ = 66560000 @ DDR 798 (correct?)

60++ = 60960000 @ DDR 975 (proved by me)

But anyway - thank for the custom way - this also solve my needs :)
[Galaxy Ace II Android Development] ayas02:
im try set all of lcdclk from 60++ until 40mhz and i think 40 , 45 and default 60(echo -2) is stable of lcdclk :)
[Galaxy Ace II Android Development] S.AMU:
Does someone of you have a problem with GPS?

Because since some time I'm getting about 8-10 visible sattelites, but they only lock in for 2sec every 3-5minutes.

First I thought its a problem on cm12, but I'm having the same on carbon and cm11. All of them running with chronokernel
[Galaxy Ace II Android Development] xo.en:
<erm, post removed to prevent confusion>
[Galaxy Ace II Android Development] S.AMU:
So here is the gps.conf file:

NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_2=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_3=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
SUPL_HOST=supl.google.com
SUPL_PORT=7276
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_USER_PLANE=TRUE
DEFAULT_SSL_ENABLE=FALSE
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_TLS_HOST=FQDN
REPORT_POSITION_USE_SUPL_REFLOC=1

and that is the gps.xml:

<?xml version="1.0" encoding="utf-8"?>
<glgps xmlns="http://www.glpals.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.glpals.com/glconfig.xsd" >
<!--HAL Confguration -->
<hal
acPortName="/dev/ttyAMA1"
lBaudRate="115200"
gpioNStdbyPath="/sys/class/sec/gps/GPS_ON_OFF/value"
gpioNResetPath="/sys/class/sec/gps/GPS_nRST/value"
gpioDelayMs="250"
acNvStoDir="/data/"
FactoryTestFilePath="/data/"

acLogDirectory="/sdcard/gps/broadcom/"

TISEnabled="true"
LPmode="false"
cp-cold-start="false"
cp-guard-time-sec="1"

arp-supl-enable="true"
arp-supl-cap-msb="true"
arp-supl-cap-msa="true"
arp-supl-cap-ecid="false"
arp-supl-use-apn="false"
acSuplServer="supl.google.com"
SuplPort="7276"
tlsCertPath="/system/bin/gps.cer"
tlsEnable="false"
ReAidingIntervalSec="1200"
SuplUT1Seconds="20"
SuplUT2Seconds="20"
SuplUT3Seconds="20"
SuplVersion="1"

LbsEnable="true"
LbsLocal="false"
LbsServer="BCMLS2.glpals.com"
LbsPort="7275"
LbsSyncLto="false"
SyncLto="true"
ltoFileName="lto2.dat"
acLtoDir="/data/gps/"
LbsSyncLtoThresholdDays="1"
LbsTAC="10101222"
LbsWlanEnable="false"

IgnoreJniTime="true"
AssertEnabled="false"

SensorsEnable="false"
/>

<gll
LogPriMask="LOG_INFO"
LogFacMask="LOG_GLLAPI | LOG_NMEA | LOG_RAWDATA"
FrqPlan="FRQ_PLAN_26MHZ_2PPM"
RfType="GL_RF_47511_BRCM_EXT_LNA"
WarmStandbyTimeout1Seconds="10"
WarmStandbyTimeout2Seconds="15"
>
</gll>
<gll_features
EnableLowPowerEls="false"
EnableLowPowerPmm="true"
/>

</glgps>

I didn't found the file /system/etc/sirfgps.conf and also, ma data folder in data/gps was already empty.

And what do you mean with never use wifi? Do you mean I should turn off wifi because f the agps data or simply because it's interfering with GPS? Because I have no mobile internet connection for the next three months at least.

I'm goint to try your attached files now. Will report later

Edit: now gps is copletely dead :D
[Galaxy Ace II Android Development] ace2nutzer:
Yeah it's right, 200Mhz isn't present in my Kernel since i'm was able to measure power consumption with "current widget", i just see that the difference from 200 @ 400Mhz is only approx: 2 - 4mA.

In my Case kernel default is:

Screen off: APE/DDR 25% with min 400Mhz

Screen on: APE/DDR 50% with min 400Mhz

Screen on with some load (scrolling etc.): APE/DDR 100% by CPU 600Mhz and higher (if load is bigger)

I'm using that config for months and nobody is complaining about bad performance, laggs or bad battery lifetime :)