yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] manthes:
Again black screen with all universal kernels. The problem has started with 1.5 build
[Galaxy Ace II Android Development] shaqman89:
I just noticed that offline charging only shows a loading image, not the percentage. Anyone else having this?

I am using the latest 2.6.1 kernel.

---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------

What governor are you using?

I noticed that using zenx with static gpu helps a bit on this.

---------- Post added at 11:24 AM ---------- Previous post was at 11:22 AM ----------

What governor are you using?

I noticed that using zenx with static gpu helps a bit on this.

---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------

Are you using the Universal kernel (latest version)?

I believe that having the ability to choose your own recovery is one of the advantages of using the Universal version
[Galaxy Ace II Android Development] Andrewbons:
I'm using the latest version, but i tried previous versions too. It's a well known TWRP bug, someone says to change filesystem but it won't fix that for me (as for lots of other users). I said it lots of times but always ignored :\
[Galaxy Ace II Android Development] shaqman89:
I see that the Cwm version only supports ext4 for now. Well, I guess we have to wait for someone who could support it. For the moment, I am quite happy with TWRP.
[Galaxy Ace II Android Development] Andrewbons:
It's not true. There are older chrono kernel (4.3 version) with CWM with F2FS support. I have a odin version, i have to flash my device everytime i want to install something. It's a pain in the *** because i have 4.4.4
[Galaxy Ace II Android Development] matthias1976:
i only got blackscreenbug in early CM 11 versions.

i setted deepest sleep state on 5, after setting deepest sleep state on 4 it works fine.

for me loading animation with percentages showing.

all normal
[Galaxy Ace II Android Development] manthes:
I use 4.2 rom and pegasusq. But the problem started with build 1.5 so i went back to 1.3
[Galaxy Ace II Android Development] vacziferi:
2 random reboots within 1 hour, after installation of kernel 2.6.1 :confused: :(

https://www.dropbox.com/s/1ec5kfc0e7flr6o/last_kmsg_1116_2.txt?dl=0
[Galaxy Ace II Android Development] lars85destroyer:
Any changelog for 2.6.1 ?
[Galaxy Ace II Android Development] monstro78:
I have this and I use 2.6
[Galaxy Ace II Android Development] ChronoMonochrome:
Sry, I forgot that stock needs BT_MGMT support. It's absolutely useless on custom ROMs, so I disabled it. Will upload build for stock soon.

Have anyone tried increase Mali voltage?

echo 0x18 > /sys/kernel/mali/mali_gpu_vape_50opp

Please try and report.

https://drive.google.com/folderview?id=0B_OwIFfWQnj_NTZMN1NoaXdROUE&usp=sharing

Have you seen this folder?

about full f2fs support in CWM - sorry, don't have time to test it.
[Galaxy Ace II Android Development] S.AMU:
Same here, but I'm running 2.4 twrp fullf2s
[Galaxy Ace II Android Development] tofueatsbread:
I thought cm removed it or smth? XD i dont read threads recently idk..
[Galaxy Ace II Android Development] ace2nutzer:
@up

Yes.. but if we use Ramdisk from Rox 20140706 .. then batt. percent on offline works :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Redownload and reinstall boot scripts for 4.4.x. (kernel/ramdisks/4.4.x.cpio.zip)
[Galaxy Ace II Android Development] riyosakura:
there cwm full f2fs file. is it for codina?

how to make it flashable?? just replace on any recovery zip??
[Galaxy Ace II Android Development] matthias1976:
dont really understand what is set here.

can someone explain please ?
[Galaxy Ace II Android Development] shaqman89:
I am trying it now. I'll report back after a few hours or at least a day to see whether it's really gone or not.

Btw, that code should be

echo 0x18 > /sys/kernel/mali/mali_gpu_vape_50_opp
[Galaxy Ace II Android Development] fluffi444:
R2.6.1 / CodinaP

Smoothness is back again! Completely! Fast and stable here! Nothing to complain!

Good idea to set APE_OPP 100 for the middle Steps 13-19.
[Galaxy Ace II Android Development] ChronoMonochrome:
How about battery lifetime? I don't know if it's just for me, but since I did this change, it drains battery too fast...
[Galaxy Ace II Android Development] fluffi444:
Nothing special (up to now) - But I have installed it yesterday. I would need some more days to compare during general use.

BUT: I've no problem if you what to change it back - As I know the "smoothness-trigger" init.d will be a good solution for me.... :highfive:
[Galaxy Ace II Android Development] Andrewbons:
I did few tests with 2.6

-Battery life is a bit better than 2.5, but still worse than 2.3. Right now i've got 12 hours, 2 hours screen on, no WIFI, 3g always on, few minutes gaming and music. It's a good point so far ;) (i've made it in time from 8:30am to 7:00 pm, from university and back home, still 20% left)

-No reboots, no freeze, not even one issue. Fast and stable (finally XD)

-Since 2.6 i removed both CPU and GPU UV. I tried to test battery life with my usual -100mv UV, but since i set it i had black screen issue (i still have it, but i just have to wait 10 seconds to wake it up normally. With UV i can't wake it up, i have to force reboot).

-With 2.6 i've noticed lower kernel wakelocks, dunno if it's due to no UV, i can't compare with UV because it freeze my phone.

Right now i have android 4.4.4 (last novafusion build) 200-800mhz, interactive, SioPlus, no UV, no screen off custom freq, static GPU 400mhz, 2450mah battery, full F2FS.

I hope you can improve more and more your kernel, but right now i can say i'm almost happy :P If you can make a CWM with full F2FS or if you can explain me how to build it myself (i can't understand those cpio files), i will be happy :)
[Galaxy Ace II Android Development] ChronoMonochrome:
All right, 2.3 has 50 mA as termination current, 2.5 - 150 mA, and 2.6 - 100 mA as default value. For better battery lifetime, you can decrease termination current a bit more, as mentioned in OP.
[Galaxy Ace II Android Development] Andrewbons:
Does a too low value damage battery? And how can it damage? I would try something without any big risk
[Galaxy Ace II Android Development] ChronoMonochrome:
Actually damages only slow charging.

It's already in "ramdisks" folder.
[Galaxy Ace II Android Development] shaqman89:
True. It really drains too fast.

Overnight I could lose around 20% with this version.

I agree with fluffi. This one is really fast and smooth. Way more stable than before, but I think I still get some reboots.

It seems I got one reboot last night. Here is the log:

https://docs.google.com/file/d/0Bzo3MSxg_YFCT2doMUx6cFBoNkk/edit?usp=docslist_api

The black screen seems too dissappear after the fix you gave ChronoMonochrome :)

Keep up the good work :)
[Galaxy Ace II Android Development] ChronoMonochrome:
It drains battery even if you don't use phone? Then problem probably not is in kernel... I had similar problem, it seemed some wakelocks don't allowed phone to go to sleep(irrespective of using DeepSleep battery saver). Only solution that I found is wipe data, and remove some faulty apps.,.

It seems there is no kernel panic. That may mean reboot happened because of CPU voltage/max frequency.

:good: but I want to get as more confirmations as possible :) then I can write fix just in kernel.
[Galaxy Ace II Android Development] matthias1976:
was that in planemode !?

for me there is more power needed that ooooooold 13.05 TC Stock Version.

phone often awake without screen on.

Deep Sleep (): 1 h 47 m 18 s (6438 s) Ratio: 84,9%

Awake (): 5 m 27 s (327 s) Ratio: 4,8%

Screen On (): 12 s (12 s) Ratio: 0,2%

big difference between awake and screen on

kernel wakelocks

"radio-interface" (): 3 m 26 s (206 s) Cnt:wc/ec)66/5/0 3,1%

"secril_fd-interface" (): 1 m 27 s (87 s) Cnt:wc/ec)23/0/0 1,2%

"PowerManagerService.WakeLocks" (): 1 m 17 s (77 s) Cnt:wc/ec)124/0/0 1,1%

everytime other order of kernel wakelocks

partial wakelocks

GpsLocationProvider (Android-System): 16 s (16 s) Count:9 0,2%

Checkin Service (Google-Dienste): 15 s (15 s) Count:80 0,2%

AudioMix (1013): 10 s (10 s) Count:4 0,2%

nothin special here i think

in planemode phone sleep well.

ok radio interface, wlan , when phone online needs power. but in old version of TC CM11 the phone sleeps much better when online.

from 1 hour deepsleep with screen off maybe 30 seconds awake time.
[Galaxy Ace II Android Development] manthes:
For me it didn't work. Black screen exists for every version after build 1.5
[Galaxy Ace II Android Development] ChronoMonochrome:
try

echo 0x1a > /sys/kernel/mali/mali_gpu_vape_50_opp

.
[Galaxy Ace II Android Development] manthes:
Correct me if i am wrong but i have to write it to terminal emulator and after that to reboot. Ok? :o
[Galaxy Ace II Android Development] ace2nutzer:
@up

type in term. .. don't reboot.. after reboot u need to execute this command again !

For executing this command at every boot.. just write this in an existing script in /system/etc/init.d

But before u do this @ init.d .. try if it helps.. / fix the bug, otherwise it's unneeded to write this in init.d ;)
[Galaxy Ace II Android Development] manthes:
Ok. So i will try it without reboot but because the problem happens randomly i will wait for 2 days first to see if it happens or not and then i will report
[Galaxy Ace II Android Development] S.AMU:
Can someone explain me, why logcat is not working?

When i type "adb logcat" on the pc it only says: "Unable to open log device /dev/log/main: No such file or directory"

When I try to use Catlog on my phone there is only an endless loading circle and nothing else.

Also there is no folder "log" in /dev.

Is it possible that this is due to twrp? Because for repartitioning I also had to install cwm to get adb working correctly in recovery.
[Galaxy Ace II Android Development] fluffi444:
I guess you are using Universal Kernel?!

Then you have to put logger.ko

from

/system/lib/modules

to

/system/lib/modules/autoload

ADB is working (with latest recovery.cpio) also..

- You habe to enable MTP (Menu: mounts) - You must see "disabe" then its enabled - To be sure de- and reactivate it...

- Then plug USB cable

- and (most important) wait long time untill 8160/8160P is shown in Windows Explorer

- Then ADB is also active and ADB SHELL (with SU) is fully working

BUT: You are right if you say that PARTED is not availbale in TWRP- Therefore for repartitioning CWM is recommended. But this has nothing to do with ADB itself...
[Galaxy Ace II Android Development] shaqman89:
I was wondering about this before, but since I usually use adb via wifi, it never really bothered me.

I tried the steps, but I still couldn't find it in Windows Explorer or ADB. Checking from device manager, it still shows unknown device. Am I understanding this wrong?
[Galaxy Ace II Android Development] matthias1976:
for me must be shown as "Android Samsung ADB Interface"
[Galaxy Ace II Android Development] manthes:
It didn't help. I am back to 1.3 which didn't have blackscreen
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, I remember old fix from R1.3. That one didn't solve the problem completely, but helped a lot in past. I'll reimplement it in a separate kernel version for s6d, because it also causes screen tearing on ws2401.
[Galaxy Ace II Android Development] strangebro:
i found out that every time i reboot the cpu governor changes to performance, it takes a while until ZenX appear on the options.

i use kernel version 2.6.1. The rom i used is CM 11 TC lastest bulid by ace2nutzer
[Galaxy Ace II Android Development] shaqman89:
Isn't this normal? From what I understand, the values are set by an init.d script, so depending on when that script is triggered, the configuration would always be default for a few seconds after reboots. This also applies to min & max frequency and some other configurations.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build is up!

Changelog:

many various commits from Linux 3.3 (thanks [MENTION=3332811]faux123[/MENTION])

improved hotplugging mechanism

updated RCU system

kernel scheduler

memory management

etc...

LiveOPP:

recalibrate varm and vbbx on boot (better stability)

added interface to OC some clocks that depends on PLLDDR

echo on > /sys/kernel/liveopp/pllddr_cross_clocks

Note that settings still experimental, so don't wonder if it reboot when you enabling it. Its stability mostly depends on PLLDDR

and also on GPU frequency.

reimplemented sweep2wake and doubletap2wake (thanks [MENTION=4400604]Meticulus[/MENTION])

to enable type:

s2w:

echo 1 > /sys/module/sweep2wake/parameters/enable
echo 1 > /sys/module/sweep2wake/parameters/use_wakelock

dt2w:

echo 1 > /sys/module/doubletap2wake/parameters/enable
echo 1 > /sys/module/doubletap2wake/parameters/use_wakelock

enabled UKSM (thanks [MENTION=4832589]cocafe[/MENTION])

- better RAM performance with tiny cost CPU. Boot time will be increased by 3 sec, it's ok.

disabled ZRAM by default. As it turned out, current implementation is not effective.

Maybe I'll port it to Linux 3.2 to compile it with option ZRAM_FOR_ANDROID.

uploaded kernel for s6d.

Please test and report if blackscreen issue still exists.

If you use f2fs kernel please download and reinstall recovery (otherwise TWRP/CWM loop will occur) from here https://drive.google.com/folderview?id=0B_OwIFfWQnj_RHBoeVJ4R2JTNDA&usp=sharing , also will upload on FTP in few hours.
[Galaxy Ace II Android Development] monstro78:
I'm on f2fs. First kernel and then recovery???

Downloading now...
[Galaxy Ace II Android Development] manthes:
It is the first time that i have so much screen tearing that i can't test for black screen. I installed standard 2.7 build to see if i have luck with blackscreen
[Galaxy Ace II Android Development] ChronoMonochrome:
There was nothing to do with s6d in this build... will provide another fix for s6d(just don't remember which changes I did to fix it in R1.3).

UPD. new build for s6d, changelog:

- removed MCDE patch (previous fix, that caused tearings)

- removed old codina tearings fix (it's odd, but so far I can't notice any tearings even on ws2401 - CM11)

https://drive.google.com/file/d/0B_OwIFfWQnj_MmtZUk1WU2hYWDg/view?usp=sharing

Please test this build even you've ws2401. If nobody will have tearing problem, then this change could be merged to main build.

UPD2.

Maybe it's too fast, I uploaded new build(no s6d) with minor fixes:

- fixed pllddr_cross_clocks instability

- removed unneeded DDR_50_OPP requirement on screen on (should prolong battery lifetime).

Actually reason for new build was there, I noticed that DDR spends too much time in 50OPP state(it's unneeded in idle, but when not in idle, ddr_opp will be dynamically changed by LiveOPP), probably I found one more leftover that came from ST-Ericcson...

Google Drive
[Galaxy Ace II Android Development] Andrewbons:
testing 2.7.1 with s6d (i have that driver).

Bug: can't flash CWM full F2FS, it says "aborted". TWRP is correct. Can you fix CWM? It's better (ace2nutzer has it working)
[Galaxy Ace II Android Development] tofueatsbread:
splashscreen bootloop
[Galaxy Ace II Android Development] ChronoMonochrome:
Oh, maybe uploaded wrong file, will reupload it asap.
[Galaxy Ace II Android Development] str3tch72:
So ext4 version working properly?
[Galaxy Ace II Android Development] heml0ck:
is this ok for stock?
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't use ext4, but since between f2fs difference only in ramdisk, it should work too.

It's not fully compatible with stock, BT(and probably WiFi) doesn't work. Version for stock will be uploaded later.
[Galaxy Ace II Android Development] ace2nutzer:
Have this new hotplug driver real powersave feature? :)
[Galaxy Ace II Android Development] manthes:
I have this problem with 2.7 and ace2nutzer rom also. With oldest kernels (non universal) it didn't happen
[Galaxy Ace II Android Development] lars85destroyer:
I'm on 2.6.1 full F2FS, so I have to flash "twrp_f2fs_p_2.8.0.0_for_R2.7.zip"?
[Galaxy Ace II Android Development] fluffi444:
Dont flash the file itself... depack... rename file to recovery.cpio... and put this into the former flashable zip file.
[Galaxy Ace II Android Development] lars85destroyer:
There's a new file, what do I have to do with it ? twrp_full_f2fs_2.7.1.0.cpio
[Galaxy Ace II Android Development] Andrewbons:
I've downloaded cwm F2FS cpio, i did what you said but still i have "installation aborted". What is the right flashable i have to modify? I've used CWM for ext4, just replaced recovery.cpio with f2fs
[Galaxy Ace II Android Development] ace2nutzer:
Nope.. on latest CM 11 modified by me or latest kernel.. the default Governor is CONSERVATIVE during booting + CWM..

That means it'll save Battery when u do something with cwm.. because min. freq. is 200Mhz and max. 800

By default TC Kernel.. it was PERFORMANCE.. with this gov.. in the past during booting + CWM.. the freq. was always @ 1Ghz :)
[Galaxy Ace II Android Development] lars85destroyer:
Interactive wouldn't be better ?
[Galaxy Ace II Android Development] ace2nutzer:
INTERACTIVE is setted by default after boot.

CONSERVATIVE is better on CWM due to more Powersave.. also it's used on LPM Charging instead of POWERSAVE..
[Galaxy Ace II Android Development] manthes:
I can't use your kernels because of blackscreen (cwm and lock screen) that's why i said that with chrono kernels it looses governor settings
[Galaxy Ace II Android Development] ace2nutzer:
Even with 19/11 Kernel by me ? @ Blackscreen
[Galaxy Ace II Android Development] manthes:
I tried your rom as it was without installing kernel. I have black screen after 30 minutes and of course also on recovery. That's why i install again chrono kernel but it has this problem i said.
[Galaxy Ace II Android Development] ace2nutzer:
U mean 18/11 ??

If yes, why u don't post this in my Thread ? How can i improve /debug Kernel when noboby reports some issues ? ;)

Now u don't need to post it also in my kernelthread.. because now i know that.. thanks for report ;)

I'll see what i can do :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I didn't test it yet. This is not new driver - there's actually only some(of many) commits from tuna kernel.
[Galaxy Ace II Android Development] ace2nutzer:
I hope i'll have real hotplugging.. then I'll merge it too.. otherwise only lags and slows up the device.. u know that all :)

But then it's better to hotplug cpu1 ondemand even on screen off... not static hotplugged cpu1 all the time on screen off.. because that will cause sound stuttering. Without real Hotplug the difference is only ~ 35mA @ 30mA on screen off. And in IDLE @ min. freq.. the Performance in latency until cpu1 is online and until the freq. can switched up is half.. not really convenient.
[Galaxy Ace II Android Development] riyosakura:
Im using 2.7.2 kernel. And it oftenly get freeze the phone. I've got the freeze 3 times until i reverted back to 2.6.1 kernel. Im not taking logcat though. Did anyone here got the same problem with me?

Edit:

Or maybe this gonna explain something? https://docs.google.com/file/d/0B_n5KTaAFShoSV9lTmE5Sk1WRE0/edit?usp=docslist_api
[Galaxy Ace II Android Development] ChronoMonochrome:
Maybe recalibrated varm/vbbx voltages cause it. That's what I was afraid of...

UPD. please post your avs data:

no needed, found it in last_kmsg

UPD2. btw, it seems you're using uncompatible modules (maybe from previous version?)

[ 8.396362] j4fs: disagrees about version of symbol module_layout
[ 8.403564] param: disagrees about version of symbol module_layout
[Galaxy Ace II Android Development] BastiZ:
Could you also include OndemandPlus governor? Its best on Galaxy Nexus (tuna) devices. May be here as well.

Github link

.
[Galaxy Ace II Android Development] zwliew:
Just a quick note:

What I've learnt from some intense testing is that hotplugging on dual core phones(especially weak cortex-a9 ones like on SGA2) is really not viable and worth it in the long run. Hot(un)plugging is a very costly operation in terms of latency, overhead and power.

On a dual core 1.7GHz Krait 300 phone(my moto x), there is still mpdecision-style hot plugging, but CPU1 is still being hotplugged on every touch input. This is how Qualcomm ensures smooth 60fps performance, by rendering CPU1 online almost all the time.

On a dual core 800MHz Cortex-A9 phone(galaxy ace 2), CPU1 is never hot(un)plugged to ensure the same smooth performance. I feel that it should stay this way. Using a hotpluggi g governor like AbyssPlug is useless as the CPU load is so high almost all the time, that CPU1 will be onlined almost as soon as it is offlined. As I mentioned before, hotplugging is very costly. This behavior of hotplugging CPU1 will be detrimental in the long run.

Now this brings me to unplugging CPU1 on suspend. I've experimented with this too, and it seems that CPU0 can't even handle audio well on suspend. Ace2nutzer mentioned somewhere about hot(un)plugging(read: hot(un)plugging instead of just unplugging) CPU1 on suspend instead. This is useless too due to reasons stated in the previous paragraph.

TL;DR: I believe it is better to leave CPU1 online all the time than to hot(un)plug it. An idle core still spends less power than a busy core.
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for link, will include it in the next build :)
[Galaxy Ace II Android Development] ace2nutzer:
This is exactly what i mean zwliew :)

Usually turning off 1 of 2 Cores should save battery.. but only on "real unplugging" U8500 don't have this feature. The CPU1 have then 0Mhz but it's still attached on the Supply and it draws anyway power.. here counts only the varm and the actually cpu usage...

user: mkaluza did some current measurements on his janice device.. very usefull.. he did much work.... check:

https://github.com/mkaluza/i9070_kernel_CoCore-E/wiki/Janice-power-usage

But fortunately i found an great APP:

https://play.google.com/store/apps/details?id=com.manor.currentwidget&hl=de

With that we can see the actually current consumption when the Cable in unplugged and when the charger is plugged we can see the actually charging current !! It's very usefull.. u need only to set the update interval @ "3" for faster actualizing the Value.

It's incredible .. but this "cheap" App helped me to fix slow charging on my kernel.. because i messed something with input / output current in abb-charger.. now it works.

Now for all they think "forget it, this app is not precise" . I need to say: nope.. :) It works perfectly... I programmed in abb-charger (board-codina-bm.c) 100mA for termination_current.. and exactly @ 100mA from the Widget the Charger stop charging and it shows 100% :good:

No with this app i found out that it's no matter on wich Freq. the CPU is running when the following things are NOT changed:

- varm

- vbbx

- APE / DDR OPP

- GPU Freq.

I did Various Tests with min. CPU 50Mhz - 400Mhz .. because i use the same Voltages for 50 - 400Mhz.. and i was really wondering.. but absoulutely no difference in Power consumption ! Now I'm using Min 400Mhz for CPU and GPU ! - Yes, for GPU the same.. i use the same Voltage for 192 - 400Mhz.. and here also no difference. :laugh: :good:

And .... using an Wallpaper with dark colours.. will also save Power..... look at the Screenshots... i did one with blue Background.. and one with "black" Background .. As u can see .. with the dark Homescreen.. it need less currency. - Due to this, i use in some Apps (if possible) always the Dark Theme :cool:
[Galaxy Ace II Android Development] zizoumadrid:
thank's for this information

now will save more power with dark theme in poweramp :laugh: :good:
[Galaxy Ace II Android Development] manthes:
I see that kernels have different reaction depending on the rom i use.

Latest kernel was loosing governor setting with a ace2nutzer rom but not with Carbon rom (however it looses frequency setting). Also i don't see until now blackscreen but i had with cm 10.1 and cm 10.2 roms