yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Darkened_Sky:
I have a question about this:

I understand that it is not possible to make a nandroid backup of only the second rom, but as the second rom slot is directly on the /data partition, it should be backuped together with the primary rom if we do a normal nandroid backup. And if we restore this backup it should restore primary and secondary rom together.

Or am I missing something?
[Galaxy S III Android Development] arter97:
Correct. You can also just move /data/arter97_secondrom to another place and install another 2nd ROM, and triple, or quad multi-boot.

Although it'll be inconvenient.
[Galaxy S III Android Development] arter97:
Such a shame that some devs actually thinks upstreaming our S3 kernel to higher major versions of Linux kernel is possible.

Don't expect 3.4, 3.10 or 3.14 kernel from the developer community.

I call that "A total nonsense".

Unless Samsung officially works for it, releases it, it'll be IMPOSSIBLE.
[Galaxy S III Android Development] Mostafa Wael:
[MENTION=4898097]arter97[/MENTION]

Is you philz recovery able to convert from F2FS back to the normal EXT4

safely

?

Or is it only one way from EXT4 to F2FS?

Thanks.
[Galaxy S III Android Development] psndna88:
total rebase to 3.4 or up is not practically possible

unless u have the resources and data needed for it which only samsung has.

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v101 (4.4.3) + AGNi pureCM v2.8.1 kernel with ART
[Galaxy S III Android Development] arter97:
It should. But with no guarantees.

I haven't tested it.
[Galaxy S III Android Development] arter97:
'nuff said.
[Galaxy S III Android Development] trein91:
Curious. Is undervolting under consideration?

Sent from my Galaxy S3
[Galaxy S III Android Development] arter97:
No. And it'll never be.
[Galaxy S III Android Development] trein91:
Oh =(. I thought you would. Since Andreilux already cleared that abb =/= replacement for UV. And that UV = free battery life. But eh Nvm

Sent from my Galaxy S3
[Galaxy S III Android Development] habylab:
It is his choice! I'm just grateful for the kernel.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Yes, I've misunderstood about the ABB stuffs, but he haven't said UV = more battery life still.
[Galaxy S III Android Development] trein91:
Yes he did. (UV) is a disadvantage free method of gaining power efficiency

xdaforums.com/showpost.php?p=36508702&postcount=1773

Sent from my Galaxy S3
[Galaxy S III Android Development] rick0025:
i wanna try f2fs but im afraid im not getting back to ext4 :(
[MENTION=663773]arter[/MENTION]

can you guide me if i wanna revert back?
[Galaxy S III Android Development] habylab:
What release of r3p2 does this kernel have? Rel3 or 4? I've seen 4 elsewhere. Switched back to yours as camera was not working elsewhere and I have not noticed any difference in smoothness, so was just wondering!

Sent from my Linaro SM'd CM11 Galaxy S3. A proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Pretty straight forward.

Select ext4 instead of f2fs on that switching guide.
[Galaxy S III Android Development] arter97:
U mean Mali?

It'll be almost impossible to have Mali r4xx driver.. can you give me the link?
[Galaxy S III Android Development] arter97:
Have been playing around dt2w.

Main benefits of dt2w is the allowance of deep sleep.

But dt2w during deep sleep is not working with our S3(mms_ts).

Let me go digging in a bit more..
[Galaxy S III Android Development] junepedit:
[MENTION=4898097]arter97[/MENTION]，now i use slimrom+arter97 kernel 2.1.3 on my E210K，there are some problems

1. sometimes the machine is too hot，especially after use camera，where is the problem slimrom or kernel?

2. after flight mode, mobile data losed,how to repair？

my friend and i love your awsome work ！
[Galaxy S III Android Development] arter97:
Both seems it's a ROM side problem.

Our Korean ROM, which I have cooperated in, has the airplane mode issue fixed.

Ask that ROM's developer.
[Galaxy S III Android Development] habylab:
Yes Mali, and Boeffla mentions it here:

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-omni/omni11/changelog.htm
[Galaxy S III Android Development] arter97:
I'm not seeing anything Mali related on ArchiKernel's github(which is based on the same source drop as mine).

So, if I'm correct, mine should also be the latest.

I'll double check when I have time.
[Galaxy S III Android Development] rick0025:
forgot to edit..i found it a while ago..im using f2fs now and seems great..thanks to your kernel..
[Galaxy S III Android Development] floxigen:
Is there a way to control charging current and ignoring unstable power like in boeffla ?
[Galaxy S III Android Development] Darkened_Sky:
yes both are available in atweaks.
[Galaxy S III Android Development] floxigen:
Ok Thanks ! So ... Lets go to F2FS !
[Galaxy S III Android Development] justforreply:
Kernel Stability

The kernel is more stable in this version ?

I see on the frist post the removal of UKSM solve almost all kernel panics happened with previous versions.

It improve the stability too, because on v2.1.1, my phone get buggy many times, eg: when I press home button launcher reloads, many apps buggy and freeze.

This bugs made me replace my kernel to yank kernel, but I like to have dual boot on my phone.

I use glamour s5 rom, anything as improved in stability and ram usage for this rom?
[Galaxy S III Android Development] solar666:
archi said something different as I asked him in his thread.

Can you clarify?
[Galaxy S III Android Development] habylab:
Excellent. What do you think of his GitHub, much for nothing? I have tried and found it smooth, but could be a placebo. Are his optimisations necessary or any good?

Edit: your op says r3p2, so I'm assuming not updated! Also, what is Firelock?!

Clarification would be nice!

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Latest 2.1.3 should be rock stable.

Please attach kernel log if you're having issues.

I cannot help you if you don't.
[Galaxy S III Android Development] arter97:
In old days, arter97 kernel 1.x days, I was also using dat crazy amounts of optimization flags and ended up with audio, video issues.

I'm sure JustArchi would have this kinda issues solved, he's a hardcore optimize analyzer xD

Anyways, I'd like to still point out my kernel is using hard-float, which I think is more benefical than all those optimization flags.

Still, ArchiKernel is very nice in terms of compiler optimizations.

Now I found my kernel is using r3p2-rel03. It's interesting to hear someone is now using r3p2-rel04, but I cannot find any sources(Github + Samsung OSRC) with Mali r3p2-rel04.

Firelock is a aggressive core saving feature, it turns down every core except cpu0 when CPU has entered min freq.

http://xdaforums.com/galaxy-s3/development/kernel-archikernel-v1-0-power-hands-t2785337/post53628302
[Galaxy S III Android Development] supreethms:
[MENTION=4898097]arter97[/MENTION] , i just tried your kernel on Paranoid Android RC2.

I have only one main feature missing in your kernel.

Can you please add "intelliactive" governor? It makes my phone smoother than ever. :P

Please.
[Galaxy S III Android Development] arter97:
http://xdaforums.com/showpost.php?p=52947052&postcount=342
[Galaxy S III Android Development] george stamatos:
One question Arter97, if i copy the hole second rom file to xternSD and put it back after a full wipe in 1st rom, will it work?

Love your kernel, thanks in advance
[Galaxy S III Android Development] arter97:
No. Permissions and symlinks will get corrupted.
[Galaxy S III Android Development] george stamatos:
Copy inside SD, in a place that not getting wiped, it also get corrupted ;
[Galaxy S III Android Development] arter97:
That's normal too.
[Galaxy S III Android Development] bj4ever:
You could try to tar second ROM on extSd and then extract data back,mabye this way could work
[Galaxy S III Android Development] supreethms:
Thanks for pointing me to that. But.. I used to use it on boeffla kernel and it used to be smooth. Much better than zzmoove or pegasusq or any other. That was the only governor for which i had a good review. Hence, i requested for it.
[Galaxy S III Android Development] arter97:
I just knew AndiP71 ported it.

It's still Qualcomm optimized governor. I doubt it has auto hotplugging.

Check if when you use intelliactive with boeffla kernel, all cores active.
[Galaxy S III Android Development] bornlivedie:
Yeah, Intelliactive is one of the governors that yield the best performance and battery life.

Besides, music skips with other governors, including zanezam's.
[Galaxy S III Android Development] arter97:
I doubt it'll yield the best battery life. What I meant from the previous post, using intelliactive with Exynos will end up in hotplug issues, thus cpu cores will be wasted.
[Galaxy S III Android Development] cba1986:
It happened to me when using agnis kernel. cores doesn't plug in or doesn't plug out.
[Galaxy S III Android Development] arter97:
Thanks for confirming.

Yea, I expected that :(
[Galaxy S III Android Development] habylab:
No point porting it, personally. Googy tried to but scraped it for this very reason.

Edit: saw this in my ROM thread. Noticed it has updated Mali drivers at the bottom? May help [MENTION=4898097]arter97[/MENTION]

Don't expect fireworks but still...N7100's KitKat blobs are coming... :fingers-crossed:

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] supreethms:
Well. I used intelliactive on the previous kernels.

Yes. The cores don't sleep. They are all awake at all the times. :P

But that's something that kept the phone so smooth. Trust me, i have never ever experienced a single lag on AOSP with that governor.

Battery is not bad. I get 3+ hours of screen time. And.. While sleeping, 2-3 % drop in my 6 hours(max) sleep.

You can just add it and give a warning on the OP saying that this governor might have a bad effect. That way, the people who want a fully working update-13 based kernel can use it with intelliactive and others who prefer other governors can continue with that.

That's all i request.

Or, [MENTION=947981]Lord Boeffla[/MENTION] could clear our doubts here. :)
[Galaxy S III Android Development] bornlivedie:
It's been like that since forever... maybe they'll merge it this time, who knows.
[Galaxy S III Android Development] habylab:
Who knows!

I've used 100mhz as my minimum today, worked well!

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
That'll be Mali r3p2-rel03 which my kernel already has(since mine's based on Update 13.)

See? Yes, we're miles ahead where CM is catching up behind xD

OP :

I took a look at JustArchi's r3p2-rel04.

Seems very promising, but I'm worried about the blobs compatibilities. JustArchi has applied r3p2-rel04 changes taken from generic Mali driver from ARM. Only kernel source is new and our blobs are old. There might be some issues. I'll hold it back off for now.
[Galaxy S III Android Development] arter97:
1. It's Qualcomm SoC optimized governor.

2. It does not has hotplugging algorithm.

Those two will actually make the battery worse. I'm kinda surprised to see a positive review.

Just go with pegasusq and lock it's hotplug to 4 if you want a similar effect.

I don't want to port intelli** governor for above two reasons.
[Galaxy S III Android Development] bornlivedie:
Just found a great replacement: lulzactiveq

It's flying now!
[Galaxy S III Android Development] arter97:
Hmm. If I remember correctly, pegasusq outperforms lulzactiveq.
[Galaxy S III Android Development] bornlivedie:
Stop criticizing my governors :(

Going to try that one later.
[Galaxy S III Android Development] andip71:
Well, as many times in life, there is a discrapency between theory on paper and real life experience.

I also though at the beginning - wow, intelliactive does only rarely plug CPUs, so it will be quite bad for battery consumption. However, this is the theory on paper. My real life experience was also, the effect was there but not major significant.

This, by the way, applies also to other governors like ondemand, smartassv2, wheatley... which do not use hot plugging at all (unless enabled on global level). Also with them battery life was not as bad as expected.

So it seems, not having hot plugging of CPUs is a bit overrated and not that bad. Plugging CPUs on and off apparently comes with some good overhead, so the savings are not as big as expected.

By the way: The cores do indeed sleep when the device goes into deep sleep. The plugging issue is only there when the device is being used. But as said, effect seems to be minimal.

I know, this is not at all a scientific explanation now. But real life experience is always more important than theory on paper (my opinion).

That is why I decided to keep this governor in my kernel at least (along with others that seem to be not optimized but working fine like mentioned above).

Andi
[Galaxy S III Android Development] Andr3y29:
I understood almost nothing of what you guys talked above :(

So, what is the governor you recommend for battery saving ?
[Galaxy S III Android Development] habylab:
[MENTION=4898097]arter97[/MENTION]

Archi has just said this. I thought you had done this maybe before?:

V1.1.1 is here -> http://xdaforums.com/devdb/project/?id=4627#downloads

Bugfix release to 1.1.1.

Fast changelog:

New CPU topology is something new, as I didn't find it in any other kernel.

Is he the first to have the new CPU topology?

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Stock, default pegasusq.

Or ZZmoove by [MENTION=3279788]ZaneZam[/MENTION]
[Galaxy S III Android Development] arter97:
I wrote him a long letter why I don't want to open up my entire Git repository access.

But the source code is open and available for everyone.

I also had said I want to help out. Since my kernel is also implementing multi-booting handling from DerTeufel, I suggested him to check it out first.

I can't really find out why he said "Let's say that arter doesn't want to be too helpful."

My kernel's ARM Topology is updated, but I can't remember which version(revision) it's updated to.

But ArchiKernel's new Topology commits looks familiar.
[Galaxy S III Android Development] arter97:
I guess now the entire XDA knows what's happening.

Here's the PM I sent to JustArchi :
[Galaxy S III Android Development] habylab:
That's perfectly understandable. It happens with the touch CM recovery that is on here (I've forgotten the name), as CM will just take his touch code and then no-one will use his work.

I understand the Mali thing now too. Your stance makes sense to me.

A shame that most other devs just focus on their work and appreciate other work, whereas Archi just seems to post potentially wrong statements (like him being the only one to use that kernel source) to gain users.

Each for their own though, don't want anyone to leave or quit!

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] regaber:
[MENTION=4898097]arter97[/MENTION] , I would understand if you don't want to talk about this anymore, but if I may... I think you are now recognized by all I9300 users as a great and innovative kernel developer. Maybe it felt wrong for you to openly share your work when you started here, but the time is different now, and it would only be the next proper step to open your Git and share the love.

Some developers here may seem a bit rude sometimes, but I think it's only because they passionately want this community to work in a proper way so everyone can move forward together. With a public Git, you can show everyone that you achieved a result in a new clever way. Then, proper credit is given, and people don't forget who contributed to making our device even better.

Anyway, keep up the good work, it is appreciated by more people than you think !

PS [MENTION=3262915]habylab[/MENTION] : let's try not to create bad blood between Devs, problems often come from misunderstanding, we're all adults :angel:
[Galaxy S III Android Development] habylab:
Well, it is his choice! Wouldn't think any better or worse if he changed it or kept it! P.s. [MENTION=5349514]regaber[/MENTION] I mentioned that in my posts!

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] supreethms:
Unfortunately, i am not able to set hotplug_lock to 4. Each time i set it, it shows a toast notification that it is set to "-1" and then i close and open aTweaks app only to that the value is still at 0. :(
[Galaxy S III Android Development] Mostafa Wael:
[MENTION=4898097]arter97[/MENTION] [MENTION=5161352]JustArchi[/MENTION]

i may have been so offensive in my late comments, but there is one thing i would like to say

you guys are making history.

you made our S3s breathe again.

And as mentioned before 90% of the problems are from misunderstanding, so let's pass this problem and chill out. You brought the mighty touchwiz battery-life to AOSP!!! i think that is a great milestone that was achieved by both of you that has been a long time not solved.

and i would like to remember you some quite good things.

arter solved the rotation problem in Archi's port

AND

archi solved the signal bar problem in arter's ROM

so both of you helped each other in your ROMs

why don't you continue helping each others?? i am 100% sure that when, for example, arter help Archi in something, everybody including Archi himself will respect arter's work and progress

and the other way around

that's is XDA

i am not saying or forcing you to open up your git to the public, that's is your decision not anybody else, but i am sure that after a while you may change your mind.

from the point of the "arter is not helpful" i do not see that at all

i remember when the ArchiPort project began, arter97 kernel was the first one to support that project and offer the dualboot option

So

to sum up in a nutshell, with no offence, let's pass this problem of misunderstanding and continue on improving our S3s and refresh them and do what samsung say's "it's impossible"

any improvement done in either kernel is good for us and for the community

sorry for long post and off-topic but that was a must for everyone to know!

P.S. if there any info wrong here correct me.

and i am not accusing or insulting anybody so let's be cool here :)

Remember that english language is not everyone's mother language :angel:

---------- Post added at 11:09 PM ---------- Previous post was at 10:57 PM ----------

now let's get back in the work now

i have a question:

since our kernel supports the knock-on feature

can we get the knock code while screen is OFF with this kernel?

that will be amazing!!!!

thanks
[Galaxy S III Android Development] JustArchi:
I told you that I don't want to start a drama. I asked for one or two things, because as I heard arter's kernel is the only kernel apart from mine which is not based on smdk sources and work with AOSP. I've always been helpful, from my very first days on xda up to this moment. All my projects are open source, everybody is able to see what my projects include and what is exactly changing between them. Without Linus Torvalds, sharing his Linux kernel and making it open-source this wouldn't been even possible, so I think that it's the proper thing to improve the linux kernel and share the changes, so other can look at them and improve them.

The first rule of mine existing on xda is to learn, improve and share. This was the case with ArchiKitchen, ArchiDroid, ArchiKernel and ArchiPort. I do something for myself, share it with the community and I really don't care about million of ArchiPort forks and custom ROMs which exist right now (more than 20+), as long as they contain proper info about original author.

It's rare that I'm asking somebody for help, but when I do, I always make sure to give proper credits and thank for the helpful hand. If you're not living under the rock, you know that I did contribute to many projects, including [MENTION=947981]Lord Boeffla[/MENTION] Boeffla Kernel, [MENTION=3279788]ZaneZam[/MENTION] ZZMoove, [MENTION=3443334]Kryten2k35[/MENTION] UltimaROM, hundred of ROMs based on my ArchiKitchen, hundred of AOSP ROMs compiled with my optimizations, and a dozen of ROMs based on ArchiPort.

I didn't make ANY of these contributions for the fame, money, or whatever reason you want to put here. I did it for the community, for YOU. So other developers can include it in their own projects, make them better, this is what whole xda is about.

It's arter's decision whether he wants to cooperate and join our happy sharing xda family or not. I won't beg for the fixes. Just don't be shocked if I decide to act the same. Do whatever you want arter, it's your kernel and your decision.

That's pretty much EOT for me.
[Galaxy S III Android Development] DaReDeViL:
may I ask for a favor ? please also count Googy-Max2 kernel with the ones based on update13 as I rebased it loooong time ago and also managed to be the first to make cm camera work flawlessly (even video recording) while reintroducing dual boot from scratch ...

Don't believe me, just check my public github ;)

Envoyé de mon GT-I9505G en utilisant Tapatalk
[Galaxy S III Android Development] habylab:
Well, this escalated quickly.

Kernel working well with Linaro CM. Faultless really.

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Okay.

After a second thought, yes, I'm releasing my Git repository open for everyone.

You guys are right. It's about the entire community, not me.

It's the entire community we want to improve, not a specific one or a group.

I'd like to contribute to the community.

I'd like to see other developers take commits from this repository and make things better.

The Git is at https://bitbucket.org/arter97/arter97-i9300-release

So,
[MENTION=5161352]JustArchi[/MENTION] , go fix your kernel's camera issue and delight the users.
[MENTION=947981]Lord Boeffla[/MENTION] , let's both work on improving Knock-On(or dt2w).
[MENTION=5270463]beeeto[/MENTION] , thanks for persuading me.

We love XDA.

We love to share things and make things better.

Me too. I love to apply things from other developers.

But with proper credits.

I'd like to see other developers take commits from this repository and make things better.

Contribute to the entire community.

But with proper credits.

'Opensource' does not mean 'no-respect'.

Leave credits to original author.

That's all I want.

Thanks for your support.
[Galaxy S III Android Development] arter97:
I've noticed it just now.

I'll try to fix it for my next version..

:(
[Galaxy S III Android Development] arter97:
Thank you for your kind words :)

I'm now releasing Git for everyone to browse.

PS: Maybe I'm lacking XDA spirit... Am I the only one who's not an adult here? :P
[Galaxy S III Android Development] arter97:
Not anytime soon.

That should work with the ROM together, thus very hard.

The kernel alone would require a heck of a lot of work, which I cannot do it myself.
[Galaxy S III Android Development] beeeto:
Great news. This say a lot good things about you buddy, not everyone can think twice about their statements.

Sir, you have now gained my respect. (And surely other XDA fellows think the same way)

Kudos to you.
[Galaxy S III Android Development] george stamatos:
Respect...
[Galaxy S III Android Development] scvblur:
Hi, would like to check if I flash this kernel with AOSP ROM, would the network bands in shv-e210s be upgraded to Intl' version bands so that it works with other countries 3G like Malaysia? My shv-e210s only hook up to 2G at Malaysia. Tried the hidden code but to no avail. Please advise. Thanks!
[Galaxy S III Android Development] rochlind:
Thanks for your support man!!!!