yashsingh1/xdaforums huggingface dataset:
[Galaxy S Advance I9070 Original Android Developmen] #Henkate:
Right now I'm on vanir ( I'm still using first or second build) and is the only kk rom in which camcorder is not so darker if you put exposure +2 (at least for me! ), but in the evening in door is very darker and i think wasn't same on jb, i don't remember very well. I record videos rarelly,but when i want to do it i don't want a darker video.That's why I'm using vanir...

But i would prefer jb instead kk because i don't use all customisation options. I used AOSP once and it was very laggy, but wasn't latest version. And with some tweaks + debloating, jb can get lower ram consumption too.

I took some videos with my cat and dog using vanir. I'm gonna upload all today or tomorrow.I already uploaded some of them, and i noticed something. The Christmas tree was darker in my video (you couldn't see the green color properly) and after i uploaded it to youtube i could see Christmas properly. I think the quality of video was downgraded when i uploaded it, as im able to watch it on 360p max and it was recorded 720p.

I will wait for jb version, i don't care how much time will take you because i won't get new phone soon due money :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Man! You've got a smart dog :) Mine can't even make me a coffee, not to mention using a phone ;P

Seems like a problem with colorspace... the same thing sometimes happen with jpegs - depending on the viewer they are brighter and more vivid or dim and pale.

[QOUTE]

I will wait for jb version, i don't care how much time will take you because i won't get new phone soon due money :)[/QUOTE]

ok :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Ok, here's a draft.

https://github.com/mkaluza/project-zen/wiki/Janice-performance-settings
[Galaxy S Advance I9070 Original Android Developmen] nss357:
Here are some stats (battery life and cpu states)

My voltages:

Liveopp (200 min 1000 max)
200 0x0c
300 0x0d
400 0x0e
500 0x15
600 0x1a
700 0x1e
800 0x21
900 0x28
1000 0x2b

Mali
low 299520 (idx 2) 0x18
high 399360 (idx 5) 0x1b

On r3:

Dynamic setup (the rest are r3 default)

up_threshold 97
down_differential 5
sampling_down_factor 1

BBS dump:

Deep Sleep (): 1 h 36 m 52 s 32.9%
Awake (): 3 h 17 m 38 s 67.1%
Screen On (): 3 h 16 m 33 s 66.7%
Wifi On (): 3 h 12 m 49 s 65.5%
Wifi Running (): 3 h 12 m 45 s 65.5%
No Data Connection (): 4 h 54 m 30 s 100.0%
No or Unknown Signal (): 4 h 54 m 30 s 100.0%
Screen dark (): 3 h 16 m 33 s 66.7%

1 GHz (): 26 m 56 s 9.1%
900 MHz (): 6 m 5 s 2.1%
800 MHz (): 5 m 59 s 2.0%
700 MHz (): 6 m 52 s 2.3%
600 MHz (): 8 m 55 s 3.0%
500 MHz (): 13 m 36 s 4.6%
400 MHz (): 36 m 12.2%
300 MHz (): 16 m 2 s 5.4%
200 MHz (): 1 h 17 m 10 s 26.2%
Deep Sleep (): 1 h 36 m 52 s 32.9%

On r4.2:

Dynamic setup (the rest are r4.2 default)

up_threshold 95
down_differential 5
sampling_down_factor 1
high_freq_sampling_up_factor 5

BBS dump:

Deep Sleep (): 0.0%
Awake (): 3 h 27 m 3 s 100.0%
Screen On (): 3 h 27 m 3 s 100.0%
Wifi On (): 3 h 25 m 21 s 99.2%
Wifi Running (): 3 h 25 m 19 s 99.2%
No Data Connection (): 3 h 27 m 3 s 100.0%
No or Unknown Signal (): 3 h 27 m 3 s 100.0%
Screen dark (): 3 h 27 m 3 s 100.0%

1 GHz (): 12 m 19 s 6.0%
900 MHz (): 6 m 56 s 3.4%
800 MHz (): 14 m 22 s 6.9%
700 MHz (): 10 m 10 s 4.9%
600 MHz (): 11 m 26 s 5.5%
500 MHz (): 14 m 47 s 7.1%
400 MHz (): 23 m 17 s 11.2%
300 MHz (): 17 m 20 s 8.4%
200 MHz (): 1 h 36 m 23 s 46.6%
Deep Sleep (): 0.0%

So with the new power_optimal_freq and high_freq_sampling_up_factor on r4.2, the cpu spent a lot less on max freq (1000mhz in my case). Both are tested with the same usage, 100%-4% with wifi on all the time, surfing mostly with tapatalk and browser. On stock vanir kernel, the max that I get doing the test is around 3h5mins something on interactive. Dynamic definitely saved some more juice, can save a lot more if tuned to a really power saving mode I guess.

So for now, I'm happy with it :)
[Galaxy S Advance I9070 Original Android Developmen] nss357:
[MENTION=3329816]mkaluza[/MENTION] I got another question, what's mmc_arm_khz and wlan_arm_khz is for?
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
when prcmu-qos code detects that wlan or mmc is busy, it sets this freq as minimum required for cpu, and also it boosts ddr and ape to 100, so it's essentialy a mmc/wlan boost (which makes sense, esp if someone is using 100 as min freq)
[Galaxy S Advance I9070 Original Android Developmen] nss357:
Ok then, gonna try the setup based on the wiki that you posted a couple posts back, and see how it goes.
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Happy New Year guys ;) and happy hacking ;)
[Galaxy S Advance I9070 Original Android Developmen] pictorul20:
hahaaa. Thank you and also Happy New Year To the developers who made the best roms for our phone. ( btw , on 31 was my birthay hi-hi so yeah it`s double celebration ) All the best wishes in the new 2015 year!
[Galaxy S Advance I9070 Original Android Developmen] nss357:
^ the whole world celebrate your birthday :p

May the new year brings more joy and happiness to everyone!
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
JB version

Ok guys. Here's an experimental JB version.

Unfortunately I'm too lazy to port this stuff back onto Cocafe's kernel, but I think that those two kernels are so similar, that this should work. It's a r4.2 debug build bundled with JB ramdisk from Cocafe's kernel. I haven't tested it because I don't want to reflash my rom.

WARNING

It's NOT TESTED, so I don't even know if it boots. If you can't handle a bootloop and/or flash kernel with odin/heimdal then DON'T TOUCH THIS. You have been warned...

If something goes wrong, try to gather as much info as possible - /proc/last_kmsg and logcat. The more info you give me, the bigger the possibility to solve the problem. Simple "doesn't work" will not get you even "I'm sorry" response... It's a dev/hacking forum - handle it...

If it works, next build will just be multirom (it'll be able to load a ramdisk from /system or /data partition, so if it detects a ramdisk archive, it'll just boot that instead of the default one) - that's the only way I'll be able to support it in the long run. As a bonus it'll allow you to change ramdisk/recovery at will without flashing anything.

http://www.mediafire.com/?ir944plxbinhd

flash zImage with dd/ukf, copy zip contents to /system/lib/modules

It'll be nice if a tester volunteered first because if it doesn't work, there's no point for everyone to flash it.
[Galaxy S Advance I9070 Original Android Developmen] turbare:
Hi mkaluza, just wanted to say hi, and thanks.

Installed this kernel couple of minutes ago on Vanir, as I was having drain issues, not sure why, but the phone was going into deep sleep properly.

Anyway, currently testing it, and very happy someone is still devving around :)

Will try the settings you posted on the wiki as well, as soon as I figure out how.

Thanks again, and all the best!

---------- Post added at 03:46 PM ---------- Previous post was at 03:08 PM ----------

Concerning this part, how can I change these settings? Would I need to do it in some sort of command line like adb, or are there some settings I'm missing?

If I recall well, I think I've read that you've removed NovaThor from apps, and have something else instead. I still seem to have the NovaThor thingie. Should it have been remove automatically when I installed the kernel via CWM, or do I need to manually remove?

PS: In the meantime, drain seems to be over after I flashed your kernel, no more Android OS on top of the drain! Yay! :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
There are many reasons for batt drain - if it goes to deep sleep, then maybe something is waking it. Check your system for some crapware ;) Log in with adb and launch "busybox top", then press "h" to see threads. And take a look what's on top and how much cpu is idle (top of the screen) - idle should be around 90%, if it is less, than look at the programs using cpu.

Anyway - the dynamic governor that comes with this kernel should help you either way - it was designed with crapware in mind :) Just enable it and leave with default settings - they are quite optimal and you should get around 3-5 hours SOT (depending on how old is your batt) and quite a lot of standby time.

Also fine-tuning screen auto-brightness helps with batt life (and using dark themes where possible).

Post your results here ;)
[Galaxy S Advance I9070 Original Android Developmen] turbare:
My phrasing was wrong, I was getting a drain with the Vanir default kernel, always had Android OS using more battery than the screen, classic scenario :)

After flashing your kernel that drain is gone, so I'm happy :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Ok, cool :) but actually I have Kernel (Android OS) and Android System as two top positions most of the time and that's not wrong by itself. But debugging batt drain is a veeery long story... Anyway - I'm happy it works for you :)
[Galaxy S Advance I9070 Original Android Developmen] samcool55:
So, i installed the kernel on carbonROM. And it works, sort of. I do have the wifi issue and i'm not familiar with adb or anything, so i will go back to the kernel that came with carbonROM.

It worked well for the rest and i forgot to reset the OC settings, turns out it wasn't an issue, it just got reset and i could use everything.

Also it would be nice to explain how to enable the dynamic governor, is it just the governor called dynamic or is there something special i need to activate?

This kernel just feels a bit above my level and i don't feel comfortable using it. So i won't use it anymore.... Sorry

Looks promising and i was suprised that it worked for the rest just fine.
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
You can ask in Carbon Rom thread if anyone is using it (it had almost 200 downloads, so there's a chance). I'll be happy to apply any fixes, but I need someone to help me debugging it - I can't install every rom that's out there...

The kernel is a bit dev oriented - it's in the process of user-proofing, but I need users to participate in it ;) Your input is valuable :) Thanks :)

As for dynamic gov - that's it's name :) Actually in the next build it'll be enabled by default, so no need to worry about it.
[Galaxy S Advance I9070 Original Android Developmen] samcool55:
I'm happy to hear that you want to fix things. Is there anything i can do to help? Posting logs from programs or something? I'm not really familiar with anything so i'm just wondering if i can help :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
yes, you can - you can send me your original kernel image from carbon (so I don't have to download it all just for the kernel). I'll pm you my email. I'll have a look at it and maybe I'll be able to spot the difference that makes wifi fail. The other thing you can send me is /system/build.prop file.

And if you could familiarize yourself with adb and manage to login as root, you can help even more, but it might be difficult for you, so no pressure - see this guide https://github.com/mkaluza/Samsung_STE_Kernel/wiki/Debugging-not-working-wifi
[Galaxy S Advance I9070 Original Android Developmen] samcool55:
So, i will send you the build.prop and the kernel soon.

About the ADB stuff, well it failed here, sort of. I wasn't able to get the .zip files.

First time it said Zip not found or something and the second time i wasn't in my phone anymore, i stopped the connection i think. But i was able to get a log from all the errors, not sure if it's useful, but i will send that too.

But, actually the best part: wifi works! I have absolutely no clue how it got fixed. but i just did some stuff from the link and horaay, it came to life! So for now, i will run the newest kernel :) I do run the debug version now, but i will stick with it, it works and i don't want to ruin it :D

Anyway, great job about the kernel, it's working perfectly now!
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Another happy user ;) it must be the permissions as it's the only thing that the "stuff from the link" changes. Probably need a better update script...

Thanks for the files btw ;)
[Galaxy S Advance I9070 Original Android Developmen] errorsys:
Maybe it's something with my phone only (?), but when I use dynamic governor the lowest frequency is always about 400 MHz (with interactive it drops to my minimal frequency 100 MHz when phone is not in use).

Sometimes dynamic governor modifies my minimal freq boundary, changing it to 400 MHz which I cannot modify (after changing to 100 it automatically gets back 400). After reboot it comes back to normal.

I have installed vanir_janice_4.4.4.112414 + mk-kernel-r4.2-release-CWM.
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
That's weird...

First thing - try disabling input boost freq (set to zero) in dynamic gov and make sure that mxt touchboost is disabled.

But there are many things that can interfere...unfortunately I can't help you much... other people use it and it works as advertised, so it's probably something you have on your phone...

Look for any turners, startup scripts etc...
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Flash 4.2.2 release - dynamic gov could have a bug before. Always flash newest stable release, especially if it has minor version numbers changed. These are bugfixes
[Galaxy S Advance I9070 Original Android Developmen] pizzadox11:
its working on i9070p?
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Don't know - I have non-P version
[Galaxy S Advance I9070 Original Android Developmen] samcool55:
Installing it now! I also saw the 400mhz bug, also my overclock resetted (i had it on 1150Mhz, went back to 1000mhz)

I had also some issues with the memory getting full and eating more power. So i restart my phone now every 2 days, not an issue for me, just something i wanted to let you know.

I will update now, if i have still some issues over a couple of days, i will let you know

edit: also something tiny i discovered, it charges very slowly. Still not sure if settings are wrong or charger is faulty, i will do some more testing first :)

Again, i had these issues with R4.2.1, i will post a new comment over a couple of days when i used 5.1.0 for a while to let you know if stuff is changed or not. :)

edit 2: ram useage is still quite high, almost 400mb used while nothing is open. when i check the apps that are running about 100-150mb is used by apps and almost 300mb is just permanently used, that's quite a lot, could it be the kernel?
[Galaxy S Advance I9070 Original Android Developmen] ChronoMonochrome:
I don't know, if it's helpful, but some people experienced same problem on original kernel from TC.
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
As for the 400 Mhz bug - check touchboost settings and report back. If you use dynamic governor, touchboost frequency should be set to zero or 100000 - dynamic governor has it's own touchboost.

It never happened to me on 4.2.2 - earlier versions could have issues with this.

I don't know about the memory - I changed nothing, so it should work the same way as the original tc kernel...
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
F2FS

[MENTION=5743624]pictorul20[/MENTION] asked for f2fs module, so r5.2.0 is just that - it has btrfs, logfs nilfs2 and f2fs built as modules. Apart from that there's nothing new, so no need to flash it if you have r5.1.

Using ramdisk overlay feature you should be able to add scripts to support those fs. I don't need them, so I won't write them, but if someone makes use of it and prepares some reasonable scripts, tools and manual, I'll be happy to include them in the build.

This is untested - f2fs module loads and that's all I checked. I took it from [MENTION=5695278]ChronoMonochrome[/MENTION] kernel - just the first commit, because others didn't build. When anyone will be using this, I can think of upgrading it to some more recent version, but until then I don't care much. I've heard that it had data integrity/safety issues, so I won't be using it anyway.

Happy hacking ;)

EDIT:

You may try and search this thread for some f2fs stuff

http://xdaforums.com/galaxy-ace/ace-2-develop/custom-kernel-t2793420/

that platform is very similar to ours, so f2fs stuff from there should work.
[Galaxy S Advance I9070 Original Android Developmen] ChronoMonochrome:
Other commits won't work on LK 3.0.x - because I entirely updated VFS to LK 3.2, I had to make also some compatibility fixes to F2FS.
[Galaxy S Advance I9070 Original Android Developmen] samcool55:
Soo i used r5.1.0 since yesterday and i'm going back to the older one. There's for some weird reason a lot more battery drain and i can't get through a full day anymore, very annoying. I'm now 18 hours on the battery and it's 3% so it will die soon. Ram useage did got a bit better but it's still too much. And i also had 1 random reboot, but it was launched during an app that has issues with loading. So it could be the app itself. Not sure what caused it.

edit: i think there's something wrong with the battery stuff, it went from 3% to 17% in 6 minutes and it charges normally from that point. Not sure what's going on?

Also 5.2.0 seems to be released, i will give that one a chance first :)
[Galaxy S Advance I9070 Original Android Developmen] ChronoMonochrome:
Original percentage showing actually sucks :( I remember same problems on every kernel for ace2 I've used. It doesn't happen always, however, only from time to time. And showing charge sometimes drops by 5-15% after reboot, this is really annoying thing.
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
That's weird guys... I haven't had any of the problems you mentioned. Battery percentage may be fixed by resetting calibration data... I've seen Vanir boot scripts do it somewhere and my battery indicator is very linear and reliable.

Higher battery drain is even more weird as not much changed in that matter in r5 - this release was more for LVM than anything else...
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Here's a short description of initramfs overlay feature

https://github.com/mkaluza/Samsung_STE_Kernel/wiki/Initramfs-overlay
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
JB version

Ok guys, another approach to JB for you [MENTION=5812391]jadega[/MENTION] [MENTION=3873311]Force.[/MENTION] I don't know if it works, but it shouldn't do you any harm.

- Go to https://www.mediafire.com/folder/6f21rvacfapcy/ramdisks and get the JB-stock-CoCore-cwm-6.0.3.4.boot.cpio.gz archive.

- Rename it to boot.cpio.gz and put in /efs dir.

- Go to recovery and flash r5.2.0.

- pray...;) just kidding :) if it doesn't boot, then just enter recovery (which should work) and flash your orig kernel back.

And report back how it went.

[MENTION=5695278]ChronoMonochrome[/MENTION]

Did you do anything special with the kernel to make it universal? Or do you just swap ramdisks?
[Galaxy S Advance I9070 Original Android Developmen] ChronoMonochrome:
I moved some files from *.cpio to separate partition, (init.samsungcodina.rc, fstab.samsungcodina and device_tunables.rc from boot.cpio, and default.prop from recovery). init.samsungcodina.rc and default.prop are different for p and non-p version, it installs according to phone model from default.prop. fstab.samsungcodina generates automatically after installation (probably would be better to generate it after each boot, but I was too lazy :) ).
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
Ok;) nice work ;) but for some time now I've been thinking about it and my conclusion is that in the long term it should be easier to extract Samsung changes and then forward-port them. Then we could rebase them on every kernel we like (adjusting them for me internal API changes of course). I'll try to do this with android 3.0 branch to get a working 3.0.72 android kernel with Samsung patches over it and see how much time it takes.
[Galaxy S Advance I9070 Original Android Developmen] ChronoMonochrome:
Hm, good idea, I'm already doing that :) . Here patch that was obtained from compare linux 3.0.31 with samsung 3.0.31 sources, and it's not such big as I expected. I'm not very familiar with binary diff, but I hope following command was correct

it's not correct, since it doesn't show content of new files. Will redo this patch using git.

diff -r linux-3.0.31 samsung-3.0.31 > linux_3.0.31_vs_samsung_3.0.31.patch

where samsung-3.0.31 is Samsung_STE_Kernel repo from first commit.

It remains only download clean 3.4.y sources and apply this patch + some compatibility fixes from ST-Ericsson. :)
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
not so fast... ;) by saying it's not that hard I didn't mean it's that easy either ;) 500k zip of diffs is a fu...n amount of code... Having one big blob of a diff isn't worth much, but:

There are 2 types of changes in kernel from samsung:

1. things that were added

2. things that were modified/removed

#1 include:

1.1 all samsung and ste stuff

1.2 some new features from later kernels

#2 include:

2.1 things authored by samsung/ste

2.2 merges from somewhere in android/lk

This distinction is important because those things have to be treated in different way (and it'll be nice to have them as separate commits/patches). The reason for this is that all 1.2, 2.2, and some 1.1 (and mayby a bit of 2.1) will be found in later kernel versions and will cause conflicts - therefore it would be nice to have more smaller patches that we can either reject entirely if they are already included or easily modify to apply cleanly.

The good thing is that most of the changes fall into #1 (almost 900k lines) - what's left is 51k inserts and 33k deletes, but this can be further reduced.

To make this process easier, fork and clone android kernel repo and add as one of the remotes ste kernel repo (or the other way around, but I think this one will be smaller to clone - android kernel repo is bigger). It'll allow you to use many cool git features like these (sam/master is orig samsung source code, 3_0_31 is a commit on android-3.0 branch):

all changes:

git diff --stat 3_0_31..sam/master | tail -n1

2839 files changed, 948595 insertions(+), 32739 deletions(-)

additions only:

git diff --stat --diff-filter=A 3_0_31..sam/master | tail -n1

1927 files changed, 897602 insertions(+)

the rest:

git diff --stat --diff-filter=M,D 3_0_31..sam/master | tail -n1

912 files changed, 50993 insertions(+), 32739 deletions(-)

That looks better already... almost 2k files are new files, so we can just include them (in chunks - some of them may fall into #1.2 - this way it'll be easier to rebase it over 3.3/3.4) with acompanying Makefile/Kconfig entries (which will reduce "the rest" numbers more) and forget about them.

Using scripts we can search android repo for each file from 'the rest' and check if there exists a version identical to samsung file - if yes, this will mean we can just ignore those, because they are just backports.

Then for the remaining files we can use script again to find a version that is most similar to samsung version - this way we might filter out backports (and things that samsung/ste merged into mainline) to get (hopefully) only changes that are nowhere to be found in android.

And then we're left with stuff that's need to be taken care of - split it into smaller patches and try to apply over 3.0.72 and see what blows up. Repeat until done ;)

Last one is the hard part, because it can't really be automated...

Hopefully above two procedures will reduce 'the rest' to some manageable size, because 900+ files is a lot of code to look at...
[Galaxy S Advance I9070 Original Android Developmen] mkaluza:
my first guess is that wifi driver can be a pain... a lot of things are changing there...