yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] soko3:
I have deep sleep... As i said, i have screen-on problems...

First hour - perfect.. Just 14-15% battery... I usually read something via Opera mini or Facebook app (minimum brightness, cpu speed mostly on 100 MHz).

And then, it's horrible...

At night, it goes to deep sleep.. just one or two times awake for minute, to sync Facebook...

CPU UV: -62.5

GPU UV: -62.5...

[MENTION=4947931]Rox[/MENTION], sometimes i'm wondering if undervolting actually works... i have tried several apps for undervolting, and none of them actually works on my device
[Galaxy Ace II Android Development] judas1977:
...so info, that you mentioned, is in the SECOND post?

So i'm sayin' that options i mentioned before are not working on my 4.3 ROM. And that's why i asked [MENTION=4947931]Rox[/MENTION], not just anybody..
[Galaxy Ace II Android Development] TPD-21:
Yes that's strange friends. I've tried to copy the url link of the OP through xda mobile app, but when I double-check the link instead turned to the last post. I'm sorry. :D Well, please be continued consultation with the concerned. ;)
[Galaxy Ace II Android Development] Asus-Tek:
I used chrono kernel and I set min 100Mhz and this freq si buggy for me. Deep sleep works very bad. You set min freq 200Mhz. Maybe this freq is buggy in this last build.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah.. Mali auto gpu boost, works fine.. but the up and downa threshold is setted very high.. for minimal power consumption.. but to high.. the freq. get to low or never in the next level.. so u need to decrase that Values..

I can not suggest to use MaliBoost.. because it's useless.. *

But if u love it anyway:

Mali boost Delay: 0

up threshold: 64

down threshold: 8

High Load freq: 600Mhz

Low load freq: 400Mhz

* But as is said.. it's not really usefull, because when u set static GPU clock @ 600Mhz.. and when the Display shows not moving Thinks..like home screen etc.. and u don't scroll anything.. the GPU runs @ 0Mhz ! If u don't believe that amazing thing: check this with ADB ;)

And if u haven't checked the GPU Halfspeed option, the GPU runs anyway @ Halfspeed when CPU Clock is actually running between 200 - 400Mhz ! Only from 600 Mhz and up, the GPU Runs at Fullspeed !

I hope u understand this... not really complicated :o
[Galaxy Ace II Android Development] judas1977:
@up

So you, generally, recommend setting static value, right?

Thx, i'll check that (i don't need that OC very much, anyway:))
[Galaxy Ace II Android Development] ace2nutzer:
Yeah, is much better, and the UI is faster.. no lags.
[Galaxy Ace II Android Development] soko3:
Cpu min. freq. set to 200 MHz and battery life is normal again.
[MENTION=228037]100[/MENTION] MHz something is buggy and draining battery too fast...

hope it will be fixed in next version
[Galaxy Ace II Android Development] ramanmono:
Hello, I have had a simple G-router at home, but recently have replaced it with a AC-router. But my link rate is still max 54mbps, which is a G speed. Shouldn't it be 65-75mbps when close to my router? Or if it supports channel bonding max 150mbps even?
[Galaxy Ace II Android Development] ace2nutzer:
Chech in NT-APP under "Network" ---> WLAN, and uncheck: "Wi-Fi PM_MAX Mode"

For Users they wanna have an absoulutely smooth UI, they can watch in my Signature, for Settings... but if u don't like to set CPU Min @ 600Mhz instead rather @ 200Mhz due to save Battery, they can make an init.d script to allow Full GPU Speed on 200 - 400 Mhz.. that helps for smoothness.

#!/system/bin/sh
sleep 90
# Disable GPU Halfspeed on CPU 200-400Mhz

echo 100 > /debug/prcmu/ape_opp

Note 1: This has nothing to do with deep sleep, screen off and screen on (IDLE) power consumption.. !

Note 2: If u have already another init.d script with an sleep 90 command... it's enough to have one script with one sleep 90 command.. but make sure that the script with the sleep command will be execute at first of all scripts.. order depends on names of the scripts ....

Enjoy :D
[Galaxy Ace II Android Development] Kiras_PL:
@up i was a bit sceptic but it really helped :D no first lag after turning on the screeen :)
[Galaxy Ace II Android Development] measel:
still no new versions for the -P version right? buildbot still down?
[Galaxy Ace II Android Development] Rox:
Sorry i am trying to fix live streaming so i am just building test builds now. Maybe tomorrow ..
[Galaxy Ace II Android Development] ChronoMonochrome:
Hello, [MENTION=4947931]Rox[/MENTION] . Can you explain, how to properly make kernel for codina p? On my last builds NFC is working but phone is recognized as non-p. Thanks in advance.
[Galaxy Ace II Android Development] AndroidOwnsAll:
Installed this rom 2 days ago, didn't experience and problems until yesterday, every time screen kept freezing on the home screen, kernals are not useful. I did a clean install but like always. My driver is pri_lcd_we2401.0

I keep experiencing this problem with every 4.4 rom except AOSP
[Galaxy Ace II Android Development] V4lve:
Hi. The last version runs really smoothly but I am experiencing really big battery drop during use. Almost as quickly as it charges. But not during sleep. That's really good.
[Galaxy Ace II Android Development] soko3:
Set min.cpu freq. at 200 MHz... that solved my battery drop...

---------- Post added at 12:22 AM ---------- Previous post was at 12:18 AM ----------

i'm experiencing a lot of lag after killing an application with long pressing of back button (enabled from developer settings)...

reboot needed to bring things back to normal
[Galaxy Ace II Android Development] mcguolo:
It seems 100 Mhz frequency is consuming more juice than 200Mhz to me too. Can't figure out why. Maybe novathor cpu simply simulates that frequency using a higher frequency (or maybe uses always both cores at 100Mhz).

Or maybe since 100Mhz doesn't exists, it takes this value as 1000Mhz! :D

As for me, I couldn't be happier with my ace2, thanks to this ROM!
[Galaxy Ace II Android Development] fluffi444:
Maybe you can post the results of

cat sys/kernel/liveopp/arm_step00

Then we can see which Varm is used...

I use manual Varm's via init.d script and "my" Step00 (100Mhz) seams to be fine with Varm 0x10 (900000 uV)...

There is no unusal behaviour... But I have ChronoKernel running...

Codonap 06/07/2014

ChronoKernel 17/08/2014 F2FS
[Galaxy Ace II Android Development] mcguolo:
I'm using default kernel values:

cat /sys/kernel/liveopp/arm_step00
[LiveOPP ARM Step 0]

Set EXTARM: Enabled
Set PLLARM: Disabled
Set Voltage: Enabled
Frequency show: 100000 kHz
Frequency real: 99840 kHz
ArmFix: 0x00000582
ArmPLL: 0x00050168
ArmOPP: ARM_EXTCLK (0x07)
Varm: 1000000 uV (0x18)
Vbbx: 0xdb

cat /sys/kernel/liveopp/arm_step01
[LiveOPP ARM Step 1]

Set EXTARM: Disabled
Set PLLARM: Disabled
Set Voltage: Enabled
Frequency show: 200000 kHz
Frequency real: 199680 kHz
ArmFix: 0x00000581
ArmPLL: 0x00050168
ArmOPP: ARM_EXTCLK (0x07)
Varm: 1000000 uV (0x18)
Vbbx: 0xdb

It seems that both 100 and 200Mhz are using 0x18. Do you suggest to manually set 100Mzh Varm to a lower value?
[Galaxy Ace II Android Development] fluffi444:
Ok - looks OK for me. Have the same here (besides to my undervolting)

You must decide if you what to do undervolting...Nobody can say if your phone will work with 900000 uV (0x10) or any other uV.

Maybe the Phone if set to 100 MHz must clock higher to the next steps more often for its background tasks compared to 200 Mhz.

And depending on the Governor you use this can go up quite fast upwards (to higher Mhz and voltages)...

And setted on 200Mhz more background tasks can be done with 200 Mhz directly (without clocking higher)

Just an Idea....
[Galaxy Ace II Android Development] mcguolo:
I'm using interactive governor, and your idea could be right. Maybe at 100mhz the phone takes more time to do some tasks, then jumps at 200mhz, doing the same things in more time, consuming more battery juice.

The fact is I noticed battery life is better with min freq at 200mhz than 100mhz. But I don't use sleep or tap to wake, and my phone is in deep sleep most of the time when I'm not using it. I'm going to activate double tap 2 wake to try if 100mhz is better than 200mhz in that case.

But I am now wondering, what is the advantage of 100mhz if it uses the same Voltage than 200mhz (just out of curiosity - and ignorance :) ).
[Galaxy Ace II Android Development] Asus-Tek:
How to change my lockscreen picture? I use picture from my gallery a change my picture but lockscreen have stock picture :(
[Galaxy Ace II Android Development] MarquesYOLO:
Use Gravitybox, for me option in themes provocate FC.
[Galaxy Ace II Android Development] S.AMU:
I think it was in

Settings --> themes
[Galaxy Ace II Android Development] soko3:
deleted (i'm stupid man)
[Galaxy Ace II Android Development] Asus-Tek:
My problem with lockscreen picture is solved :)
[Galaxy Ace II Android Development] ace2nutzer:
YES !!! U Are absoulutely right !! This is my experience and theory too !

If u wanna have the minimum power consumption, use: ONDEMAND Governor and NOOP I/O

CPU Min 100Mhz...

pegasusq, abyssplug, interactive.. and the other Gov. are optimized for min. 200 Mhz. - u can use it even with 100Mhz.. but u need to change some Values with init.d script.. but that will make the UI very laggy !

I suggest to use an Gov. that allow to set the 100Mhz only for screen OFF and reduces max. Freq.. like 400Mhz or max. 600Mhz ! ! Its very usefull if u often wanna listening FM Radio or play mp3's. And for normal usage min 200.

[MENTION=4832589]cocafe[/MENTION] [MENTION=4947931]Rox[/MENTION], [MENTION=5604178]zwliew[/MENTION] [MENTION=5695278]ChronoMonochrome[/MENTION] @ Team Canjica @ all other Dev. and freaky Users !

Please read the following text carefully.. this is very important for future Builds..

UV is not really needed... i can tell u straight as I said a few weeks ago that too much UV will destroy your Phone !

My Phone is now half destroyed with that UV.. But i admitted i have really hard UV the CPU.. !

At the beginn my phone Runs very stable with UV and OC.. and min. 200Mhz and max. 1150MHz. !

And now ?? Now it's running only at that Config stable:

Min. 200 ... max 800Mhz with NO UV !! 200 - 800 with SAME Voltage..: varm=0x26 !! < ---- Stock Voltage for my CPU Stepping.

But the CPU Run it anyway stable with 1150MHz... but ONLY with tihs Config:

Performance Gov. 1150Mhz max. with varm=0x39 --- max. Voltage....

What is broken ?? - I really don't know.. but i think any Voltages Capacitors that gives some buffer Supply for the CPU Voltage Regulator !!

What destroy the Voltage Regulator ?? - Much UV alone is NOT the Problem ! The Problem is as i said:

the Problem is it's too much stress for the Voltage Regulator when it must regulate the Voltage (under LOAD!!) 1000 Times / Minute.. from 0,85V to 1,41 V .. tihis is too much diffference...

THEREFORE:

Who does not want to destroy his phone .. set the varm @ 0x39 to all Steps and find out wich CPU freq max is stable.. then test at this freq what is the min. Voltage for stable running .. and set this Voltage for ALL Steps ! This is very easy, fast, stable and SAFE !

Example u have found out that your max. stable freq is 1150Mhz @ min. cpu Voltage 0x37.. then set the varm=0x37 for all steps...(with init.d script..) that's all !

With this Method i'm sure we all can use the extended Steps absoulutely stable !! This will saves Battery ! Especially the 100Mhz step.

If anyboby don't know how it works exactly.. just post here .. if so many people don't know about that stuf.. i can make a little thread (how-to)

But come one.. we are here on an developers forum :D So not Noob forum ! Just a joke ! Ok.. so u know ... i can help u !

PEACE !
[Galaxy Ace II Android Development] ChronoMonochrome:
[MENTION=5840412]ace2nutzer[/MENTION], are you sure that 1.4V voltage will not destroy phone? I know, on stock voltage is same for all steps, but it's only 1.05-1.15V.
[Galaxy Ace II Android Development] ace2nutzer:
Yes! I Run the Phone with CPU / GPU stability test for more than 3 hours with these Config:

1150MHz @ 0x39

GPU @ 600Mhz @ 1,30 V !

And nothing happend.. very stable !

Really? 200Mhz and 100Mhz step is running @ 1,00 V and 1Ghz @ 1,28V by default.. but i spoke about custom UV and if the user do OC higher than 1Ghz.. then the Voltage Difference is very big.

But i really don't know if 1,00V - 1,28 V is still dangerous .. !! i Think 0,28V difference is still much...

Perhaps 0,05V difference is harmless.. but this is very useless.. it makes not significant differences in battery draining. :cowboy:
[Galaxy Ace II Android Development] soko3:
sorry if it's offtopic, but can somebody explain me connection between cpu freqency and cpu voltage and power consumption...

is there any formula for calculating how much power every step uses on our nt chip?
[Galaxy Ace II Android Development] ace2nutzer:
Sure, no problem..i've posted this here for a couple of weeks ago.

But these Values are with extremely UV !

U Can measure this at yourself with Curennt widget.. or better with an multimeter directly on batterys.

This is only for power users... a wrong handle can damage the phone when u causing a short circuit or connecting the phone with wrong polarity.

http://xdaforums.com/showpost.php?p=53278530&postcount=4111

As u can see, 200 and 400 Mhz have in IDLE the same current.. because it runs at the same Voltage :)

But Power Consumption is not only from actually freq. and Voltage.. but many more on actually CPU Load !

Ex.: 800: 116 | 200

That means @ 800Mhz static Clock.. for ex. with max. 800Mhz @ performance... the total consumption of the phone in idle is: 116mA and @ 100% load (CPU+GPU) it's 200mA ! And this Values contains Display power consumption, GPU, and the NovaThor SoC Board.

And as u can see, the mostly Difference in power consumption is in 100% load..(95-300mA) so beetween 200MHz and 1150Mhz.. in idle it's only 77-136mA
[Galaxy Ace II Android Development] soko3:
found something that P=c*f*V^2

where c is capacitance, f frequency and V voltage...

and considering this, 200 mhz step uses double the power 100mhz step using...

so, i would like to configure what the fffff is going on with my phone

with ondemand, cpu is going at fullspeed too often and battery consumption is higher

conservative governor looks buggy, because it never goes to 200 mhz (it's on 400 mhz most of the time)

only abbysplug works fine for me, but with it, 100 mhz step is wasting a lot of battery

have someone any idea why?

almost forgotten:

i have rocket player running in background, and facebok active and even on incomming messages and nottifications, phone is working on 100 mhz (it's powerful enough to handle it without going to higher frequency)...
[Galaxy Ace II Android Development] ace2nutzer:
on interactive gov. u can decide what is max. cpu freq. for lock screen and max. freq. for sync etc...

And for all the other governors u can change some Gov. Values in kernel to change how fast the freq. is switching up.

It's for every Gov. the same.. but they have different Values...

For example: Conservative is very slow.. that the reason why this is very laggy but that have a good battery life..

sampling_rate ------> 200000 -------> very slow

is how often the kernel check if is needed to increase / decrase freq.

up_threshold ----------> 80 --------> that means 80%

= this Value can be setted from 5% - 99%... that means that by 80% cpu load for ex. by min. cpu fre. 200Mhz the freq. is switching up.

For pegasusq:

sampling_rate ----> 50000

up_threshold ---> 75

as u can see, pegasusq gov. is faster and switch the freq. still at 75% load up. that the reason why pegasusq is switching often to the max. freq.

but if u don't like it.. just make init.d script.. it's very simple !

ondemand:

sampling_rate ----> 40000

up_threshold -------> 95

ondemand is fast and at the same time use the min. freq. up to 95% .. this is the reason why with ondemand cpu is running most of the time @ 200Mhz.

etc.. etc ... this is not all... just take a look into the Gov. folder.. u can change it all..

IMHO the best gov for the mostly customization ist interactive.. because u can set the lock scree freq. and different sync freq... and freq. when u touching the screen... i mean it's setted by default to 600Mhz.. because the UI needs min. 600Mhz to run completely lagfree.

But i never tested the extended steps.. because codinap build from TC never had this... perhaps with 500Mhz the UI is running lagfree too.. i don't now.. but 100 - 400Mhz is to little for the UI.
[Galaxy Ace II Android Development] monstro78:
I think its how we use the device.

If someone listen music or radio FM or browsing then its better to have min 100.

I personally have min 400 max 1150 because I want a "snappy" device.

When I try to oc GPU to 600 I had rebouts. No uv.

And more thing... Rox we will have a new build at next couple of days?? Sorry no eta I just want to try something...

Sent from my GT-I8160 using TC's CM 11
[Galaxy Ace II Android Development] crester:
Hi.

Mine is not entering in deep sleep

I cannot imagine why.

Could you help me with this?

Enviado desde mi Z5 usando Tapatalk 2
[Galaxy Ace II Android Development] ChronoMonochrome:
One user PMed me workaround for deep sleep:
[Galaxy Ace II Android Development] ace2nutzer:
hahahahha He will a good dev
[Galaxy Ace II Android Development] ChronoMonochrome:
ofc, we know bln doesn't allow phone to sleep. :) But it's weird thing that deep sleep works only after reboot.
[Galaxy Ace II Android Development] ace2nutzer:
Nope.. when disabling Double tap 2 wake and swype2wake .. the deep sleep is working normal without reboot !

I use this Widget script with SManager:

#!/system/bin/sh

# Comfort Control

SYSFS="/sys/kernel/bt404"

if grep -q "on" $SYSFS/doubletap2wake
then
echo off > $SYSFS/doubletap2wake
echo -e "\n\n DoubleTap2Wake, BLN and WAKELOCK OFF \n\n"
exit 0
else
echo on > $SYSFS/doubletap2wake
echo -e "\n\n DoubleTap2Wake, BLN and WAKELOCK ON !!! \n\n"
exit 1
fi
[Galaxy Ace II Android Development] DaSuperGrover:
Also my deep sleep works well.

Since I changed from interactive to ondemand my battery life is much better, still not like it used to be on older builds.

Cpu settings are 100 min, 800max
[Galaxy Ace II Android Development] ace2nutzer:
Yes as is said...

Compare screen on with awake...
[Galaxy Ace II Android Development] zizoumadrid:
what is the best build stock rom 4.1.2

last build I8160XXNB1 ?

or another build ?

need help pls

thank's
[Galaxy Ace II Android Development] burkitt:
stock sucks.

but as far as i know xxnb1 slovakia is the best.

i would rather use LS or CM11
[Galaxy Ace II Android Development] zizoumadrid:
anyone have idea about that ?
[Galaxy Ace II Android Development] MarquesYOLO:
I have one soft-reboot using Twitter app, app collapsed and reboot occurs. No UV
[Galaxy Ace II Android Development] monstro78:
@up

Read from chrono kernel thread second post how to post a log after random reboot

Sent from my GT-I8160
[Galaxy Ace II Android Development] MarquesYOLO:
@up Thanks for the info.

I have the logcat but i don't know how upload it here with tapatalk, I can not find the option.
[Galaxy Ace II Android Development] denisq:
I am using the chrono kernel which is by default using the pegasusq governor. Following the discussions in this thread I would like to permenantly change to interactive with min 200mhz. I can temporarily change the governor with SetCPU app but it won't stick and goes back to pegasusq after a while (not necessarily a reboot). What is the best way to change the governor?
[Galaxy Ace II Android Development] ChronoMonochrome:
Afaik my kernel doesn't uses pegasusq as default governor. I can guess u uses performance profiles. Do not use them to be able to change governor.
[Galaxy Ace II Android Development] denisq:
I am using the 29/07 kernel, supposed to be stable. Maybe pegasusq was still default? However, I was not aware of performance profiles and just discovered that I could set the governor there (instead of 3rd party apps like SetCPU).

Seeking for battery lifetime and minimum UI smoothness (no gaming or so), can we agree that interactif with min 200mhz is the optimal setting? Or is there a better setting with your kernel, ChronoMonochrome?
[Galaxy Ace II Android Development] ace2nutzer:
If smoothness is not important.. but good battery life, use "ondemand" gov. and "noop" I/O

For Smoothness: interactive or lagfree, but even "noop" I/O :D

unmodified "pegasusq" is crappy because that have high battery draining and is not smooth.
[Galaxy Ace II Android Development] botid:
Has anyone ever got issues with his playlists emptying? Mine frequently end up empty and y was wondering if it could be linked to the partition swap?

Fyi, my songs are located on the (physical) external sd card (32gb)
[Galaxy Ace II Android Development] Rox:
Keep calm. Just hold on...

Dont mix with it...
[Galaxy Ace II Android Development] Rox:
Keep calm guys. Dont spam here ;) a lots of next pages of this thread are reserved for developing, helping, support and also jokes in future ;)
[Galaxy Ace II Android Development] Towle:
Thread has been cleaned. Please stay on topic. If there is any concern of kanging, that is between the developers and shouldn't be talked about in the thread(s). To the developers, feel free to contact any one of us moderators if there are any concerns that need to be addressed.

Thanks,

Towle
[Galaxy Ace II Android Development] crashdjent:
I see some good news on 1st page...

Sent from my GT-I8160 with Tapatalk
[Galaxy Ace II Android Development] str3tch72:
Really good :)

? Wysłane z Ace'a II ?
[Galaxy Ace II Android Development] chosenroyal:
Now that just put a smile on my face! :) in fact a grin... :D :good: Happy dev is progressing~! Thank God!
[Galaxy Ace II Android Development] j800r:
I wouldn't hold my breath, it's not like Maclaw has given permission for his fixes to be used or anything.

This isn't gonna end well for us as the users. Either TC CM will never implement OMX fix or Maclaw will tone down (if not completely stop) development for the device.

I'm trying to hard not to get involved with all the drama but one thing I liked about Maclaw's CM11 is that it was ready to use as a daily driver (not perfect, but all primary features were working) and also the fact that there was a new release with updated sources DAILY almost without fail. What I didn't like is he was happy to use TC sources as a starting block but then closed any changes/fixes he made. However, from a competition standpoint I can see why.

If TC CM11 publishes fixed OMX without Maclaw's permission he's forced to change his business model entirely and likely would partially remove his feet from the Ace II waters leaving us with just TC to carry the touch. TC ROMs are great, but with more top-rate devs out there (forget business models) there's more choice and better experience for us as consumers.

We'll see what happens but at the moment it's just empty promises. We all just need to be patient and see how all this rubbish turns out. I'd love a fixed TC build of the ROM, but I've also enjoyed my experience using Maclaw CM11 builds until this drama kicked off and threw things into chaos.
[Galaxy Ace II Android Development] pinhead97:
Do you always write in essays? Whenever I see a post from you it is commonly quite long :p I kinda get what you are saying though