yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] gothicVI:
You're welcome :p
[Galaxy Ace II Android Development] xo.en:
2.25 is funny - i lost 21% of battery for two days(+ typical 100%->95% drop) - some internet, some soft updates, one reboot to update scripts(this took most battery), few calls....

Of course, machine was mostly idle, phone was all the time on.

Still - no sound loss, no blackscreens, heavily modded, repacked slimkat onboard, viper with quality driver(no SOUND LOSS!).

Thx, Chrono.

btw, GPS works GREAT here.

This is so f.cking impressive...

Now, let me ask again - will 64gb sdcard work?

It is most important question, as i cannot afford buying useless device, if it is not going to work, you know..but i need that space.

Sidenote - mp3 tags REALLY can make batt drain, there are tools to fix them(what is shocking - on PC it may take HOURS to fix, and it is quite risky process, too - soft is making backups, but with 11k of files you may be drown with total mess as result).

I used one and weird mediaserver issue is gone so far(tried it with two totally different devices - both lost batt drain after this).

Thing seem to be related to erroneous codepages used in tags, nontypical symbols(including my country's letters, too).

Stupid mediaserver tries to work with these and fails, so then it starts again and again, and fails.

Bit of help is xposed module, that handles snd files with mediaserver differently, i used both methods(tag fixer and this module), problem is gone for me now, you know..no more 20-80% batt loss over night.

Upd: i gone for a walk today - suddenly realized i was wrong about batt usage - it seems i lost c.a. 12% for two days, 4 hours, alltogether.
[Galaxy Ace II Android Development] renčam:
Please what is the name of these two modules?
[Galaxy Ace II Android Development] manthes:
Sometimes i have black screen (not very often but it happens) with latest kernels and everytime i went back to 2.16.2
[Galaxy Ace II Android Development] fluffi444:
[MENTION=5695278]ChronoMonochrome[/MENTION] - Could you please take a look into enclosed logs?

Had a sudden reboot early today. (R2.22.5)

This time I think i could be kernel related:

Kernel panic - not syncing: Fatal exception

200-1200/ZENX/FIOPS
[Galaxy Ace II Android Development] ChronoMonochrome:
This has something to do with dhd.ko module. I'm afraid, I can do nearly nothing with this, except attempts to use dhd.ko, built from another sources.
[Galaxy Ace II Android Development] fluffi444:
Anyway - Thanks for the information. Good to know that it's WiFi related. It's the very first time that this occur. And maybe the last time :o
[Galaxy Ace II Android Development] ace2nutzer:
It's related to FIOPS Sched.. .. use better SIOPlus.. It's updated ... ;)

BUG: scheduling while atomic: ReaderThread/2897/0x00010003

and

<4>[ 80.675476] JBD: Spotted dirty metadata buffer (dev = mmcblk1p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

It has nothing to do with wifi.. and i don't think it was happened because the Phone had today a bad day .. :highfive:
[Galaxy Ace II Android Development] fluffi444:
Yeb - its on!

root@codinap:/ # cat /sys/kernel/pm_sync/pm_sync_active
cat /sys/kernel/pm_sync/pm_sync_active
1
[Galaxy Ace II Android Development] ChronoMonochrome:
Then I'm sad to tell that this is due to DDR overclock :(
[Galaxy Ace II Android Development] ace2nutzer:
Well then i was wrong...

But really sure that it isn't an issue with dynamic fsync or FUSE FS ?? Because that Error is also related to second partition on sdcard1 .. or i'm wrong ? :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I guess that second partition is used for second ROM. I don't think that FUSE FS can have something to do with ext4. I can't be so sure with dynamic fsync, but you can also see in the same backtrace fsync calls. Normally everything should be fine, but seems that fsync'd data were corrupted before sync. You can also see some unreachable data (many "*" symbols) - just after the 0x86000000 where occured this error "[226925.611846] Unable to handle kernel paging request at virtual address 86000000" - this may mean corruption of data in RAM.
[Galaxy Ace II Android Development] fluffi444:
Its and extra partition for Link2SD...

Anyway - thx to you both for looking so deeply into it...
[Galaxy Ace II Android Development] ace2nutzer:
No Problem, but i'm not sure if it's 100% related to DDR OC .. because of 200 - 1200Mhz .. well 1,2Ghz is surely stable for the most Phones, but the biggest Problem is still the Voltages for every Steps...

Maybe for u fluffi an test to find out if it's a problem with UV or just DDR...

Try this:

Test1: Everything same config, but all CPU Steps @ 0x37

Test2: Everything the same but without DDR oc ...

But if u'll have that reboot only 1 time per month, then it's really hard ... :(

btw: can u post your CPU Voltages here ?? (used by the random reboot)
[Galaxy Ace II Android Development] ChronoMonochrome:
I really don't like to annoy, but when reboot happens due to CPU voltage, there's no kernel panic. On other hand, every reboot that happened due to DDR OC (unless it didn't happen right after setting new PLLDDR value), is accompanied by error 'unable to handle kernel paging request'. Just believe me, I had a lot of such reboots in the past, when I tested PLLDDR OC.
[Galaxy Ace II Android Development] manthes:
Probably a more generic question but which gapps i have to install for a f2fs cm 10.1 rom?
[Galaxy Ace II Android Development] ace2nutzer:
install always the smallest gapps .. and there for CM 10.1 for android 4.2.2
[Galaxy Ace II Android Development] xo.en:
Guys, what's your opinion about camera battery usage?

I'd say it is insaneously high, what do you think(I lost c.a. 30% in HALF hour with brightness set to c.a.30%)?

I mean, cam was always taxing on this machine, but i have feeling that this kernel takes most of all.

btw, days are passing by, zero reboots, zero weird situations, zero blackscreens, zero sound loss - ondemandplus/tripndroid, 700mhz/480mhz.

Man, you made something really great :) ace2nutzer too, of course.

You deserve level(s) up. This is obvious.

upd: 2d,13h,16m - batt loss - 18%, lol.
[Galaxy Ace II Android Development] Devel0per95:
Guys anyone tried chronokernel on v5.1 (Lollipop)?

cuz i'm having some troubles when i install it :(
[Galaxy Ace II Android Development] Ave_Hornet:
I'm using it

what problem do you have? :D
[Galaxy Ace II Android Development] Devel0per95:
when i install it

it stuck on the boot animation :(

can u give me ur files plz :)
[Galaxy Ace II Android Development] Ave_Hornet:
u must wait abot 10 min to bootup the system

what files? O>o
[Galaxy Ace II Android Development] Devel0per95:
chronoK. files please

[MENTION=6227052]Ave_Hornet[/MENTION]
[Galaxy Ace II Android Development] manthes:
After installing slimbean 4.2 wifi is dead. I remember that with older kernels i didn't have this problem and that's why i am posting the question here. How can i fix it?
[Galaxy Ace II Android Development] ChronoMonochrome:
There are no problems with wifi on SlimBean 4.2. Check whether module dhd.ko is installed(this maybe not, if you haven't enough space on /system).
[Galaxy Ace II Android Development] manthes:
It didn't help. After converting to f2fs things stopped to be so simple as before.

However i tried to change refresh rate to 60+ to see if it will help for black screen but the result was to start blinkink the phone. The opposite that you mentioned in first page (s6d). I change for now to 40Hz without any problem
[Galaxy Ace II Android Development] ChronoMonochrome:
Unfortunately, I cannot provide a soltution which would work same on any device, and I believe that nobody can. There were already two different LCD displays(s6d, ws2401), and only few days ago it turned out that there is a third variant with lcdclk=30,72MHz by default(which type is still unknown, as GB and JB recognize it by different way). This mean that user has to play with lcdclk by himself. Sadly, but as is.

As for not working wifi - have you tried to use original slim bean ramdisk, as it's mentioned in OP (read unsupported ROMs spoiler)?
[Galaxy Ace II Android Development] manthes:
You mean this one? I didn't unterstand it

1. Install needed ROM first,

2. Type following command in terminal emulator:

Code:

cd /

find . -xdev | cpio -o -Hnewc | gzip -9 > /sdcard/x.y.z.cpio.gz

where x.y.z is OS version (for example - CM11-based ROM - 4.4.4.cpio.gz)

3. put this file in installer at osfiles/x.y.z/ (e.g. osfiles/4.4.4/4.4.4.cpio.gz)

4. install kernel

After a few hours with 40 Mhz i didn't find any problem with my s6d driver (no tearing etc). I added this line echo 4 > /sys/kernel/mcde/lcdclk to a file in init.d but i didn't load it at boot. With which command i can set custom refresh rate?
[Galaxy Ace II Android Development] ace2nutzer:
Nope, not sadly.. it's great ! :D :o

Now open all your Eyes Guys !

These Days i've played a bit with my new LCD --> S6D27A1 and i found some awesome things.. (on sources)

At least u was right, all S6D use by default 31Mhz ! , So it's really no wonder when a user have Screen blinking when he is trying to set LCD Freq @ 57Mhz --> 60+Hz :o

For me max. stable is 40Mhz... on 50Mhz i've screen freezes after some Hours of usage.. and on 57Mhz = Screen blinking !

Everything normal !!

With my old LCD --> WS2401 (stock 50Mhz) i was even able to set 80Mhz without any Problems ...

So i hope now it's clearly.. and bout Blackscreen.. i'm working on it... to fix that bug on the rest of users with that bug.. so leftovers .. u know ;)

EDIT: On GB a S6D LCD is recognized as WS2401 because there is no sources for S6D ;)

But if u take a look on same SYSFS .. there is a SYSFS wich is calling like this: LCD_Type or Panel_Type.. the u'll see for S6D: SHARP and for WS2401 --> SMD

This is possible because the most important differences are already coded in board_codina_mcde.c to separate S6D with WS2401 Settings ...

But this is not all.. on GB and JB there is also DIFFERENT AVS Files ! .. Therefore, at this point: never use any Voltages from the AVS File .. really nonsense ;)
[Galaxy Ace II Android Development] Vexylle:
Could somebody tell me a good power saving setting for this kernel?
[Galaxy Ace II Android Development] ChronoMonochrome:
That sounds much simplier then. Seems that best decision is to split lcdclk code again to s6d and ws2401, having default lcdclk frequencies. Surely, I'll try it, but for now I'm stuck a bit with ROM building(this just should be possible even on x86. Only annoying thing, that this is already taken upto 24hours, but at least so far I've dealt with all compiling errors :silly: ), so for now I only can give this suggestion.

This sounds very interesting! This means that PRCMU firmware storen just somewhere in firmware itself(maybe bootloader?), and not hardcoded in hardware as I thought before.
[Galaxy Ace II Android Development] xo.en:
Can I be more ridiculous, than this?

http://s18.postimg.org/lthla4215/Screenshot_2015_04_20_23_37_59444.png

:D

Btw, VERY interesting info, ace2nutzer.
[Galaxy Ace II Android Development] ChronoMonochrome:
What exactly is unclear? This probably is my bad english(I should rephrase some steps then) or maybe this manual itself isn't very user-friendly. Anyway I've uploaded bootscripts for slim 4.2.2 few days ago http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/DualBoot [WIP]/some stuff/4.2.2/slim.cpio.gz

I didn't write this before cause I was not able to find this link with lagging laptop, but now I write from mobile. As about lcdclk - post last_kmsg, and try to add sleep command before changing lcdclk.
[Galaxy Ace II Android Development] xo.en:
<remove, before this post lay an eggs..>
[Galaxy Ace II Android Development] ChronoMonochrome:
Is this problem? You've 26% battery loss after almost 4 days. It can't live forever without charge, it lasts maximum 10-12 days without using it almost at all. It doesn't appear to be an endless engine too ;)
[Galaxy Ace II Android Development] ace2nutzer:
Actually i really don't know where the AVS File is coming from ... really strange.. if u find this interesting.. i can give u more details:

Difference between Stock GB and Stock JB: Everything the same, but different varm 100 and varm max voltage !

varm100 from 0x26 (JB / CM11) @ 0x27 (GB) and varm max from 0x33 (JB / CM11) @ 0x31 (GB)

EDIT: On JB / CM 11 it'S already splitted .. only on GB it isn't splitted .. or what are u meaning ??
[Galaxy Ace II Android Development] ChronoMonochrome:
I said that this is interesting because, as you probably know, codina doesn't have MAX_ARM_OPP, when janice, for instance, has. Don't know yet, what's benefit from this(maybe better performance?), but it would be interesting to play with it :) But even if it's written in bootloader, we can forget about it, it doesn't worth to have hardbrick, trying mess with bootloader :)

Oh, I actually mean original lcdclk implementation in my kernel, as you can see, it was repeated twice in s6d and ws2401 driver just before this commit https://github.com/ChronoMonochrome/Chrono_Kernel/commit/1008a884190a43e35c3c66820dd48f6ded200ee6 . Of course, there are many other ways to set automatically lcdclk @ 30 MHz on s6d, but I believe, that this is an easiest.
[Galaxy Ace II Android Development] ace2nutzer:
Hmm to be honest i never had believe that we don't have MAX OPP .. because it's just same Hardware .. both U8500 ... And because we have MAX OPP on the AVS File, we have it :) And i don't know what'S the difference between 100 OPP and MAX OPP .. maybe more speed ? or maybe we can oc a bit more ? (but i don't think..)

btw: If i'm not wrong we're using for all steps ARM 100 OPP .. but why we don't use ARM 50 OPP for min CPU Freq ?? That should save power or not ?? I don't now if this is like VAPE 100 and 50 .. because on VAPE 50 not only GPU Freq is half ... but maybe on ARM 50 ONLY CPU Freq is half ?? If yes, then it's useless .. but who knows ? This is maybe the reason why on Stock JB Battery Life is better than CM 11 .. What do u think ?

Ahh jeahh okk, now i see.. hmm good idea @ s6d and ws24 source... very easy !! But usually if u do nothing .. then the S6D is running by default on the hardcoded freq on board_codina_mcde.c @ SHARP Freq... the WS2401 is running @ SMD freq ...

And even on the SYSFS for LCD CLK.. if u don't change anything.. (no init.d scripts for changing LCD freq..) then the interface is showing u the Kernel default LCD Freq ! if u see 4992000 then u've WS2401 .. but if u see 3072000 then it's S6D .. it's also simply or not ??
[Galaxy Ace II Android Development] ChronoMonochrome:
When arm50 used, we have in PLLARM additional divider 2 but as soon as multiplier exactly two times bigger than with arm100opp, cpufreq is same.

I remember that some tests, done in the past by mkaluza, has showed almost zero difference in power usage of different ARM OPP states. On stock every cpufreq was represent as different ARM OPP state(with different varm/vbbx/pll of course). So this may be just for convenience(changing just ARM OPP is simplier than manually update voltage, pll etc.

Yeah, that should be even simpliest. But I mean this too, saying about default lcdclk frequencies. then there's no need to change code to show correct lcdclk idx.
[Galaxy Ace II Android Development] ace2nutzer:
Yes i know that :)

Yeah, right now tested... my minimum cpu freq of 400Mhz .. @ 0x01 bit .. and zero difference on power drain .. :D

Yeah, only the Freq idx is messes then .. i can leave with it :o
[Galaxy Ace II Android Development] xo.en:
New screen:

http://s21.postimg.org/ozzeprujb/Screenshot_2015_04_22_13_05_37.png

Either i am dead, or i am dead AND you made nice ..kernel :)

btw - tripndroid i/o is the one. difference from fiops is quite..visible.

I will not post anything here since now...there is no need to, imho.
[Galaxy Ace II Android Development] MrBlackCore:
Trying to install r2.22.6 on PolishVodka latest cm12. After installing the kernel phones does not boot. Wtf am I doing wrong
[Galaxy Ace II Android Development] ChronoMonochrome:
Use build marked with "_selinux".
[Galaxy Ace II Android Development] S.AMU:
Same problem took me one hour yesterday :D

Somewhere in this thread chrono wrote that, but I saw it an hour to late...
[Galaxy Ace II Android Development] MrBlackCore:
I just flashed the latest cm12 and chronokernel but there is a big issue... When I Receive a call, the phone hangs up by itself. Any ideas?
[Galaxy Ace II Android Development] S.AMU:
I don't know. I didn't got a call until now :D

But outgoing call is working fine
[Galaxy Ace II Android Development] manthes:
I have a very strange problems with latest builds. If i make a call everything is fine. But if i receive a call and the other one close his phone first then i have black screen.

With 2.16.2 which i am using again it is ok

.....

and with 2.22.6selinux is ok
[Galaxy Ace II Android Development] ChronoMonochrome:
[MENTION=5151049]borkins[/MENTION], good job ! :good:

VBBX is used to decrease power consumption by allowing Varm to be lowered, and to improve stability. However, too high values itself can cause higher consumption, therefore vbbx should be selected considering cpufreq. As I said different vbbx support different minimal stable varm values. Here is example

a) varm=0x0c, vbbx=0x11 (-35 - -35 mA) - consumption with full load on 200 MHz

b) varm=0x05, vbbx=0xdb (-36 - -35 mA )

As can be seen, difference in power consumption between two sets vbbx/min varm is neglegeble... However it's only aspect of undervolting of vbbx. As about OV - I haven't seen any need to OV defaults, provided in kernel.
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=5151049]borkins[/MENTION] awesome script ! :good:

That looks like a program :o

Maybe here a small correction for the script to make it more precise and stable:

Don't allow to set varm bigger than 0x37 ... and max. Voltage on 0x37 is: 1,3875 V

But on Vape is 0x3F @ 1,4875 V

As u can see there is exactly 0,1 V difference between CPU and GPU Voltage ... maybe it's possible to "unlock" the other 0,1 V on CPU Voltage and we can OC more .. but maybe it's dangerous and i've already tried it to find something in source code.. but i didn't spent too much time for this Hack !
[Galaxy Ace II Android Development] ChronoMonochrome:
As about max varm, it's unknown yet what is maximum. 0x37 is maximum stable voltage for most codina phones, however, this does not necessarily mean, that everything above is less than 1,3875 V. But sure, it's better to mention somewhere in script that values above 0x37 aren't recomended, as usually don't allow OC higher.

Probably varm isn't limited till 0x3f, but everything above 0x37 usually cause reboot, maybe due to too high varm(some phones doesn't handle even 0x37).
[Galaxy Ace II Android Development] borkins:
Ok, guys! I set the max range to 0x37 ( 1387.5 mV ). The message "(!) Too high voltage..." will appear, when setting above that.
[Galaxy Ace II Android Development] ace2nutzer:
Hmm i don't think so, that sounds not logical.. the max stable is like u said @ 0x37 .. so if 0x38 is more voltage, then it should more stable.. and we can oc a bit more.. but nobody can.. cause 0x37 is end.

as u remember we did a Voltage showing correction in sources.. cause source defaults was something like: 1,3625 V .... as MAX.. and varm was 0x35 coded in sources.. now at least i, i've changed this to 0x37 and 1,3875 V .. it's exactly + 2 arm steps.. ---> + 25mV.

If it where Hardware Faults that the board can't hande higher Voltage than 1,38 V... for CPU / GPU , then we can't run GPU Clock @ 735Mhz @ 1,4875 V .. but we can... it's stable :)

---------- Post added at 01:29 AM ---------- Previous post was at 01:23 AM ----------

"Out of range" or "max. voltage on 0x37" or "max. stability on 0x37" would be better ... to say: too high voltage is definitely wrong ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
Higher voltage not always == better stability. There maybe software or hardware watchdog, that doesn't allow use higher voltage to prevent CPU against overheating. But okay, this is anyway matter of guessing, as nobody knows what exactly happens when voltage above 0x37 is used.

UPD. right now, just for sake of curiosity, I did simple test, same that I did before. Results as follows:

1) 1200 MHz, varm=0x37
instant current
-335 mA
average current
-341 mA

1) 1200 MHz, varm=0x3f
instant current
-350 mA
average current
-353 mA

Both test were done in app stability test. This is clear and simplest confirmation that varm isn't topped at 0x37, as 0x3f causes higher power consumption.
[Galaxy Ace II Android Development] manthes:
While phone is idle it has very good battery life with 2.22.6. After 7 hours and 20 minutes it drops 5%
[Galaxy Ace II Android Development] ace2nutzer:
Okay that sounds more logical, u're right, now i remember me, in the past i did always stability tests and @ 0x39 i had much more Battery temp as 0x36 ... but the fact is that 0x38 is already unstable. Something "resets" the Kernel .. i think u're right, there is some Watchdog in kernel or hardware that doesn't allow to use varm higher than 0x37.. But it's not according to too high temp. because reboots also happens when Phone is in idle and also deep sleep .. very cold ---> 22° C.

So what ? - it ends up that max stable is 0x37. ----> 1,3875 V. Maybe one day we found a way to disable that "lock" feature .. but as i said, it's then maybe really dangerous if the Phone don't shutdown when CPU Temp is too high... :highfive:
[Galaxy Ace II Android Development] fluffi444:
What a monster! Great work! :good:

I have one question which not related to your script actually.

Once I started the script via SManager no keyboard comes up.

I cannot enter any value. Had this issue for a longer time now.

I use Swiftkey (for a longer time now)

Maybe some of you knows to get the keyboard working in SManager. Longpress on screen and activating the keypad does not work...

Sorry to be offtopic.
[Galaxy Ace II Android Development] borkins:
The keyboard normally appear with a single tap at the center of the screen.
[Galaxy Ace II Android Development] fluffi444:
And that was not happen.. was! :) It was LuckyPatcher who "patched" SManager so "badly" that the keypad doesn't come up. Solved!
[Galaxy Ace II Android Development] xo.en:
Hahaha :D

not-so-lucky this time :)
[Galaxy Ace II Android Development] ace2nutzer:
lol :laugh:
[Galaxy Ace II Android Development] nikolas1274:
For does not work, I am taking an error after disclaimer, I have chronkernel 2.22.5, is that ok?