yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] tintin1503:
Running Archiport 4.4.2 preview2 + arter97 kernel [MENTION=5301607]170[/MENTION]0 mhz (phone is asv6) (Governor - YankasusQ, Scheduler-FIOPS).

I always get over 10.5K on 4.4.2 port even when running on stock config without any overclocking.
[Galaxy S III Android Development] iceman0826:
ah.. yes the great arter97 kernel..i'm itching to try this kernel but i'm torn between the TWO :confused:

boeffla's kernel and arter97's kernel.

though my device is e210s (Korean s3) and someone just made a working boeffla kernel for 4.4 roms here xdaforums.com/galaxy-s3/general/official-korean-sgs-iii-shw-m440s-shv-t1749214/page434

so my question is what's the difference between a "ported" kernel (e.g. boeffla ported to e210s) from a native kernel like yours since you've made this kernel specially for korean s3's ? :D
[Galaxy S III Android Development] Mostafa Wael:
http://xdaforums.com/showpost.php?p=52671887&postcount=910

Can you please base on the ramdisk of ArchiPort preview 3?

That is Archi's advice :D
[Galaxy S III Android Development] arter97:
It'll be almost the same. But most porters forget to turn off CONFIG_DMA_CMA while porting to e210.

If CONFIG_DMA_CMA is turned on for e210, the RAM efficiency will be bad.
[Galaxy S III Android Development] arter97:
My kernel ramdisk is based on ported ROM made by Korean developers.

GPS is "already" working with our ROM,

Securestorage issue has been "already" fixed.

I think you'll have no probs with my kernel & latest ArchiPort.
[Galaxy S III Android Development] Mostafa Wael:
You mean that there is no problems with flashing your kernel with ArchiPort Preview 3!?

Okay will try.

By the way i would like ypu to look in that issue.

I am on Archidroid 2.4.4 experimental "one of the fastest ROM in the AOSP World"

And after i flashed your kernel i see the ROM is so laggy but it is respondive and fast but hey the animations are too laggy.

Can you please look in that?

Thanks for your hard work and support :)

EDIT: i think this lags come from a specific CPU governor, probably yankasusq or Zzmoove battery.

I will take a look and tell u. Now i am on pegasusq+ and everything is OK with no lags.
[Galaxy S III Android Development] p33k:
Thanks for the kernel! I have been on stock since kernel converter for m440s quit working a month or two ago. Eagerly will be going back to a cm11 variant with your kernel.

Sent from my SHW-M440S
[Galaxy S III Android Development] MrAlez:
[MENTION=4898097]arter97[/MENTION], i have a question can i use this kernel with patched modems? some users like me, have to use [MENTION=346607]zuluman[/MENTION] patch to get signal to work, in jb or other roms, just a question
[Galaxy S III Android Development] jinosong:
Amazing kernel. Could we see the matter sequence sometime in the future?
[Galaxy S III Android Development] popoyaya:
Hi Arter, amazing work on this kernel. It fixes all the sensors in Archiport and is super fast, but is not perfect for this rom. It breaks developer options unless usb storiage is set to camera mode. This was a problem with Archi's original kernel until he fixed the ramdisc (redoing it for i9300). Also some graphical glitches. Archi was getting a lot of logcat errors before redoing the ramdisc. Would it be possible to do a version of yours based on Archi's ramdisc?
[Galaxy S III Android Development] rascal0pl:
Anyone ? :(
[Galaxy S III Android Development] arter97:
"You mean that there is no problems with flashing your kernel with ArchiPort Preview 3!?"

Yes. It should.

"EDIT: i think this lags come from a specific CPU governor, probably yankasusq or Zzmoove battery."

YankasusQ and ZZmoove is mostly focused on battery instead of performance.
[Galaxy S III Android Development] arter97:
Use converter rev3. rev4 is causing some issues, and not recommended.

I've seen no Koreans complaining with rev3.
[Galaxy S III Android Development] arter97:
I got no idea :(
[Galaxy S III Android Development] arter97:
Master sequence?

I am gonna take a look at it when I have time.
[Galaxy S III Android Development] Mostafa Wael:
Aren't you working in team with Archi?

I think so....

Well thanks for the tip :)

Also i heard that your kernel fixes some sensors so many thanks for that :good:
[Galaxy S III Android Development] arter97:
"It fixes all the sensors in Archiport"

Auto rotation is fixed?

"It breaks developer options unless usb storiage is set to camera mode."

I don't understand. Please elaborate.

"This was a problem with Archi's original kernel until he fixed the ramdisc (redoing it for i9300)"

We are focusing this kernel's 4.4 ramdisk for our Korean ROM, not ArchiPort.

Our Korean ROM doesn't have any of the issues you've listed.

"Also some graphical glitches"

To fully fix this issue, we need KitKat kernel source for N7100, which is currently not available.
[Galaxy S III Android Development] arter97:
Nope, our Korean developers are working together with me.
[Galaxy S III Android Development] arter97:
Devil recovery shouldn't be used with my kernel's dual-boot method.
[Galaxy S III Android Development] p33k:
Thanks, I found this digging around your files. I don't think you had made the one that is posted on the m440s section of the korean s3 page that gives an error during conversion now. I will test it out also along with your kernel. After testing I will update the m440s section with yours (giving credit and linking to here). Thanks again.

Sent from my SHW-M440S
[Galaxy S III Android Development] Mostafa Wael:
What do you mean?
[Galaxy S III Android Development] arter97:
My interactive:

4. removed trace calls

My intelliactive:

2. two phase scheduling (idle/busy phases to prevent from jumping directly to

max freq

3. Checks for offline cpus and short circuits some unnecessary checks to

improve code execution paths

4. removed trace calls
[Galaxy S III Android Development] arter97:
Version 3.1.1 is now live!
[Galaxy S III Android Development] MEHDIMYADI:
thanks for v3.1.1 :highfive:

- OK . i hope fix Low Power Mode soon

- for camera issue, i flash any kernel for archiport 4.4.2 and the problem was the poor quality camera !

My question is you have the base kernel Archi Port or org sammy source ? , I think the low quality problem of the camera's is from ARCHi kernel port !

I'm currently using the your kernel , I feel a problem low quality camera improved ! but I'm not sure !

however thanks for ur prefect kernel ! :good:
[Galaxy S III Android Development] arter97:
Both mine and ArchiPort's kernel are using the same Sammy source base.

I think it's just a placebo, the camera quality should be the same.
[Galaxy S III Android Development] Thecrazyskull:
i really like your kernel on ArchiPort but screen mirroring isn't working and there are (still) graphical glitches, those are little cute ones but noticeable and very anoying.

i don't face those problems on boeffla or agni kernel but i really preffer your kernel above all!
[Galaxy S III Android Development] Lexxx47:
Can I flash this on Blekota S5 Lite ROM?
[Galaxy S III Android Development] boosha:
[MENTION=5060769]Mostafa Wael[/MENTION], What is the best Settings for Battery and Performance for Liquidsmooth rom 4.4.4 ?

Thanks in Advance
[Galaxy S III Android Development] Mostafa Wael:
Okay i am still testing best battery-saving governor between "modded OnDemand, intelliactive, interactive"

My CPU scaling is 200 MHz --> 1600 MHz and intelliPlug profile is Eco without touch-boost. This extra OC has very small ignorable hit on battery and is rock stable but it also finishes tasks faster than stock 1400 MHz

As for storage i use "deadline" governor for both internal and external storages. Read-ahead buffer is 128/256 for internal/external storages. Dynamic Fsync is turned on and i unchecked the SdcardFS box due to foldermount working only with the older Sdcard wrapping-system...

I think nothing else i can share that has an effect on battery...

Anyways, concerning the CPU governor showdown, i am still investigating but here is what i know so far:

Theoritically, interactive governor was introduced to be more battery-wise than OnDemand, so it gives smoother UI and more battery-saving experience than Ondemad.

But it has some strict policies that forces the CPU to jump to max frequency where it is not needed, so intelliactive comes to the rescue, where it has "two phase scheduling" (idle/busy phases) to prevent from jumping directly to max frequency AND Checks for offline cpus and short circuits some unnecessary checks to improve code execution paths

So this may give you the following summary theory-wise:

1.intelliactive

2.interactive

3.OnDemand

in terms of battery life

But real life experience is set to be different as not all people have the same usage. For me i have been dealing with OnDemand for quite a while as i was using boeffla and modded it to suit my usage "alot of soundcloud streaming and video playing as well as chatting and internet surfing, no graphics-intensive games though" thanks to [MENTION=2069027]metalgearhathaway[/MENTION] so "Ondemand for me according to my usage" but to have a fair test i need to have some more charge cycles with the other governors...

You can tell me your usage also of it differs.

Sorry for long posts but that is the way i like to explain things in full details for people to have the full image.
[Galaxy S III Android Development] Mostafa Wael:
hey guys,

can anyone advice me what AOSP ROM suggested.

I know ArchiDroid 2.X is the most optimised ROM for our S3 but since arter97, the second-to-none developer, gives us the opportunity to dualboot two ROMs on the phone, so i may try another ROM that has a bunch of features. and btw it is not a must that it is based on CM...

Sorry for OT, but i just want a friendly advice :)

Or maybe arter97 can build his own AOSP ROM to the GT-I9300 ?

I do not know but this project of the kernel is amazing and i like it. I hope that this project keeps getting bigger and bigger :highfive:

And speaking of dualboot, [MENTION=4898097]arter97[/MENTION] can you please add a link to [MENTION=5314272]Darkened_Sky[/MENTION] "secrec" post?

version 3.1.1 works quite well :victory:
[Galaxy S III Android Development] clarionero:
Hi. I have unplugged the phone and disabled the boost options. But 3.1.1 version continue with 100% one core cpu usage. Thank you.
[Galaxy S III Android Development] arter97:
My own ROM is on plan.. no ETA :)

And what do you mean by secrec?
[Galaxy S III Android Development] arter97:
I need more info,

what ROM are you using and what do you mean by "100% one core cpu usage"? 1400 MHz?
[Galaxy S III Android Development] mikaillevist:
Linux Kernel Device Driver r4p1-01rel0

Released : 07 July 2014

Please try add to new driver ? :)
[Galaxy S III Android Development] Mostafa Wael:
From a while ago before 3.0 Darkened_Sky has released a tool to manage your 2nd ROM via terminal emulator.

Secrec stands for SECondary RECovery tool.

I will point to you on it when i am back home.. :)

And thanks for developing an AOSP ROM. :highfive:
[Galaxy S III Android Development] lgumo01:
I've got the same situation. No deep sleep witch this kernel on Net 8.0 with super clean instalation and the same with dirty one... 100% activity.

Edit.

Nevermind, didnt read about 3.1.1 sorry.

Wysłane z GT-I9300
[Galaxy S III Android Development] clarionero:
Hi. My ROM is Archidroid 2.5.3, and yes, a core is ever at 100% at 1400.
[Galaxy S III Android Development] Sachiru:
BTW, do you plan on adding TRIM/fsTRIM support for f2fs partitions? So that we can use TRIM utilities (LagFix) on them?
[Galaxy S III Android Development] arter97:
Try chaning the governors
[Galaxy S III Android Development] arter97:
Absolutely unnecessary for my kernel both ext4 and f2fs.

Both are mounted with discard option which makes LagFix unneeded and f2fs already has a triffic trim handler within the kernel.

Read the LagFix app description.
[Galaxy S III Android Development] boosha:
Thanks for all this information, i tried intelliactive governor, 128/256 for internal/external storages, deadline governor for both internal and external storages and other than that was default, but i have lost 3% in less than 15 minutes while i wasn't using phone so i will trying other Settings and See.

Sorry for Bad English
[Galaxy S III Android Development] arter97:
I've mentioned about this a couple of pages back.
[Galaxy S III Android Development] Mostafa Wael:
Okay grab a BBS log and post here.

Also if this happened after a fresh boot then it's normal as "media scanner" will run for a while at max freq and "RILJ" wakelock keeps the phone from sleeping as it still settles up the network, so you may try again. So far I did a test between OnDemand and Intelliactive for 10% and the results were:

OnDemand --> 15 minutes 23 seconds screen-on time

Intelliactive --> 25 minutes 40 seconds screen-on time

So intelliactive seems to be better

Will test with interactive and tell u.

---------- Post added at 12:04 PM ---------- Previous post was at 11:48 AM ----------

Yesterday I encountered a random reboot immediately after the call ended 2 times.

The screen just didn't turn on and then the splash screen "samsung galaxy S3"

I will try to up the minimum freq to 200 MHz instead..

---------- Post added at 12:05 PM ---------- Previous post was at 12:04 PM ----------

May be you could write it with big red letters in OP :)
[Galaxy S III Android Development] arter97:
I did too experienced the call issue(deadlock).

Sounds quite hard to fix, I think it "may"be related to the interactive governor instead of pegasusq.. :(

Thanks for the benchmark, I'll look forward on comparing interactive vs intelliactive :)
[Galaxy S III Android Development] Mostafa Wael:
Is there anything i could help you with this deadlock issue?

Logcat? Or anything else?

Btw intelliactive is rocking :good:
[Galaxy S III Android Development] Xhemal1325:
Which version of kernel is stable ?

I see that 3.0... kenls have diferent problems ?
[Galaxy S III Android Development] Thecrazyskull:
[MENTION=4898097]arter97[/MENTION] sorry for bothering you again but i really want this awesome kernel to work properly on ArchiPort (like boeffla and agni kernel does), that means no graphical glitches and working screen mirroring so i would be really disapointed if you won't continue with making this kernel working perfect for ArchiPort.

Many thanks in advance.
[Galaxy S III Android Development] arter97:
Maybe you can try using pegasusq back for a couple of days..

As I don't use my S3 as my daily driver, it's now getting harder to testdrive for daily activities.

If you can, please try pegasusq(even though it suck.. :P) and see if the deadlock is reproducible.

When I tried to dump logs, nothing appeared to be interesting..
[Galaxy S III Android Development] arter97:
Some are loving 3.1.1 as it's working flawlessly with appreciatively reduced lags,

some are downgrading to 2.2 as it's buggy-less for some people.
[Galaxy S III Android Development] arter97:
I heard lots of graphical issues with my kernel. And I'm fully acknowledging it.

But instead of "hey arter, I'm experiencing graphical glitches!",

I need "hey arter, you may try this or this, maybe your source code here, or you can tryout this commit".

I really cannot solve this by my own.
[Galaxy S III Android Development] Mostafa Wael:
Deadlock due to interactive/intelliactive governor confirmed!! :(

Just had a call while using intelliactive and it rebooted, although I was using 200 MHz as lower freq..

Then I changed to stock laggy Pegasusq and it went normal..

Maybe i can test the ondemand governor. I think we might get results similar to interactive/intelliactive with performance-tweaked OnDemand, but we need to prove that this issue is unproducable with OnDemand

Mind that, there is intelliplug which may be a factor also...

I was using intelliactive with "Conservative" intelliplug profile.
[Galaxy S III Android Development] rascal0pl:
Not ever happened on this kernel.
[Galaxy S III Android Development] Xhemal1325:
Guys why after i flash this kernel my touch ket light duration gets automaticly changed to 1.5 sec, and if i set it to always on, dont work, it stays 1.5 sec, can someone tell me how to change it to always ok ? :rolleyes:

This is second time i ask and no answer ?! [MENTION=4898097]arter97[/MENTION] meaby u could help me ?
[Galaxy S III Android Development] Thecrazyskull:
Alright thanks man i ask help from lord boeffla because he fixed all the issues i mentioned in his kernel for ArchiPort.

But thank you verry much for answering
[Galaxy S III Android Development] andip71:
Arter, just pm me if you need help here. I cannot give you a ready to use commit, as our kernels are quite different. But can tell you what I did.

Just be aware it was lots of merging work and conflict resolution. So it will probably also take you many hours of intensive work...

Andi
[Galaxy S III Android Development] Mostafa Wael:
Can you tell me your

FULL

settings in aTweaks??!

I wanna try again

I really hope that the "deadlock" is unrelated to interactive/intelliactive, because battery life and performance rocks, especially with intelliactive :D :p
[Galaxy S III Android Development] arter97:
Yes I think we should try ondemand too.

Pegasusq is a fork of ondemand.
[Galaxy S III Android Development] arter97:
I let it not applicable since I can't figure out how to support both Sammy and AOSP.
[Galaxy S III Android Development] arter97:
Please don't tell me that you guys did a hybrid merge with N7100?
[Galaxy S III Android Development] Mostafa Wael:
Will try and tell i tonight :)

---------- Post added at 12:14 PM ---------- Previous post was at 11:36 AM ----------

OnDemand is bulletproof.

Just had a call right now. And it worked well.

So what we are having now is OnDemand gov with intelliplug. It is like twekaing the hotplug policy of pegasusq to Performance, Balance (default), Conservative, Eco, Eco extreme and also touchboost. Not Bad :/

EDIT: well not that bulletproof sadly

It happened again.

But what is noticed that it is less frequently with OnDemand :rolleyes:

If the 2.2 release was stable enough

Then it should be something not related with governors or intelliplug, as 2.2 has those governors as well if i remember correctly...

I will take a break. Need some time for studying and swimming :p championship is around the corners :D
[Galaxy S III Android Development] cangcan:
if these two famous i9300 kernel developers join venture, it would be epic and imba :eek::D
[Galaxy S III Android Development] Xhemal1325:
thanks sir, could u tell me how can i change it, is there any config at build prop to change or something ?, i just want them to stay always on :confused:
[Galaxy S III Android Development] arter97:
Thanks..!

You have said that pegasusq is bulletproof, am I right?
[Galaxy S III Android Development] arter97:
We are already sharing commits and infos :)
[Galaxy S III Android Development] arter97:
I don't think you can change it at all.
[Galaxy S III Android Development] Xhemal1325:
I have hardware problems with my back button, if it stays to 1.5 sec, it dont even work, but with touch light always on it works great :(, if u will make a new build please make it changable :), if its possible :D
[Galaxy S III Android Development] arter97:
I'll look into this when I have time later.
[Galaxy S III Android Development] arter97:
PhilZ Touch recovery developer [MENTION=4666971]Phil3759[/MENTION] is retiring.

http://xdaforums.com/showpost.php?p=55442799&postcount=5448

Sad to see this happen, PhilZ Touch recovery was and is the only recovery I'm comfortable with, a recovery with potentials, a full, proper f2fs support with universal devices support.

This developer deserves a donation, a big one.

Please consider donating to him if you can anyway possible.
[Galaxy S III Android Development] Mostafa Wael:
Yeah..

Did you have something rather than that?

Anyways I just changed ROM to Carbon and will test again.

But when i am back.

Please give me like another day or two.

I just wanna be sure and i like to be 100% sure that the info i say is correct and actual. :)
[Galaxy S III Android Development] george stamatos:
And for me pegasusq works fine,no reboots, no call blackouts
[Galaxy S III Android Development] andip71:
Well... Yes.

Just I used n8000 sources as I was anyway working on my n8000 kk kernel. So it was a bit easier for me in terms of efforts.

Exactly. And this is what opensource is about. People working together. [emoji3]

Andi
[Galaxy S III Android Development] Xhemal1325:
well wtf,! When i put my phone to charge, kernel gets crazy, 4 cpu cores go to 1.40 ghz, and governor : performance, LOL, even when i unplug it stays the same i must change the governor to A tweaks !! :(, can someone tell me how to change settings, like when i put phone to charge do not change governor ? :D

, My phone just gets hot :(
[Galaxy S III Android Development] iceman0826:
this shows how irresponsible you are when it comes to flashing things, and NOT reading the documentations regarding the use of the kernel :mad:

well wtf! the KERNEL is not CRAZY, it's the user (YOU), you don't even knew that there's a setting in the atweaks where the kernel switches to performance mode once you charge your phone! (you can switch it on or off!) i had enough reading of your dumb posts on KOREAN S3 E210S thread, and now you're plaguing this thread, and discrediting the kernel that it has a problem, when the problem is the user (YOU).

PLS. do us a favor, could you just think before you even type and post here?
[Galaxy S III Android Development] Xhemal1325:
U didnt even read all what i wrote !, LOL i asked how to change it on A tweaks, ? since i couldnt find that option , I asked for help, not telling me how dump A Im !

EDIT : FIXED IT, THANKS FOR HELP :)

Sorry for my dump posts
[Galaxy S III Android Development] arter97:
Hmmmm.. so merging with KK kernel is necessary.. I see.

I think I know a better way.. stay tuned :)
[Galaxy S III Android Development] arter97:
Thanks man lol
[Galaxy S III Android Development] rascal0pl:
Governor : Interactive

1704MHz - 200MHz

Intelli plug ECO Extreme

Touchbost - yes

No undervolt

Scheduler:

Int: ROW

Ext: DEADLINE

I/O and rest on this page default

Bost boot - 1704

PowerBoost -> yes
[Galaxy S III Android Development] arter97:
Dropping support for N7100 KK ROMs altogether in future versions.

Because something bigger is coming.
[Galaxy S III Android Development] Mostafa Wael:
Thanks bro :)

Will test it.

Already i am using interactive to see how much SOT will it have in 10%

---------- Post added at 12:42 PM ---------- Previous post was at 12:10 PM ----------

Well i remember my benchmark results were:

OnDemand = ~15 minutes

Intelliactive = ~ 25 minutes

AND here comes the champion...

Interactive = ~ 26 minutes

All tests were done with NO UnderVolting, same intelliplug profile, CPU Scaling is 200 --> 1600 MHz

Conclusion:

Both interactive and intelliactive are better than OnDemand in terms of battery life, but interactive provides a smoother UI will having the same battery life of intelliactive (or even better!)

But,..

There is always a catch :(

Sadly i had that call blackout "deadlock" bug with any of these governors and it was gone with Pegasusq.

Hope [MENTION=4898097]arter97[/MENTION] has anything to say regarding this wicked deadlock and has the fix in next version..

Also i will be posting the best CPU settings after a couple of days were it has a balance between smooth UI and great battery life.

arter if you feel my posts are a nuisance please tell me.

I just wanna help people get the most out of that mighty kernel :) and help you too of course :D
[Galaxy S III Android Development] max20091:
official 4.4.4 for korean phones

I just found the update 4.4.4 for SHV-E210K/L/S at sammobile so do you want to try update this?