yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Neural_oD:
[MENTION=5561469]Yeti47[/MENTION] thanks for the quick reply....usually I read the first post - but in this case - I didn't :p - just picked up a few pages ago.....

:good:
[Galaxy S III Android Development] Alastal:
KSM enabled gives me a great performance boost and multitasking

however the camera sometimes doesn't work " I know experimental"

and when open the camera flash it won't close until reboot the device

but the strange thing that happen when I watch a video file inside "whatsapp", whatsapp will freeze for around 30 seconds!

if I changed the values of ksm is it safe? or will it solve the strange freezing issue? anyone tried that?

btw I am not using my camera , so I have no problems with camera issues :)
[Galaxy S III Android Development] Andii S.:
every reboot wifi passwords are gone slimkat 9.0, ArchiKernel V1.7.2
[Galaxy S III Android Development] ste22032:
This is not kernel related, but ROM related.
[Galaxy S III Android Development] Andii S.:
with stock and yank kernel I don't have this issue

Send with a Lollipoped GT-I9300
[Galaxy S III Android Development] JustArchi:
Then use stock kernel and stop reporting ROM bugs here.
[Galaxy S III Android Development] JustArchi:
KSM cures our little memory issue but due to exynos it causes other weird issues related to exynos memory regions.

I left it as an option, because maybe in future somebody will be able to fix it. Until then, it's marked as experimental, it's known to cause issues, and I can only suggest leaving it off.
[Galaxy S III Android Development] arter97:
KSM barely saves tens of MB memory. It's not a ground breaking solution for i9300 lacking memory.
[Galaxy S III Android Development] Alastal:
So only thing we have to wait if someone want to look at KSM issues :)

btw Arter97 I was using it and it gives me a great performance boost "multitasking is bad even with its on but better than off"

but I have to switch if off because of whatsapp issues!
[Galaxy S III Android Development] Andii S.:
Rom bug ??? its only with your kernel all other kernels dont have this issue.
[Galaxy S III Android Development] FadeFx:
I use archi kernel on cm12.1 and dont see this issue, also it seems you are the only one with that problem, so maybe user error?

tapatalked from lollipopped i9300
[Galaxy S III Android Development] Andii S.:
i flashed slimkat 9 (clean) booted up,...setup,...connected to my wifi,...flashed archi KK ,...reboot wifi gone,...wifi setup,...reboot wifi gone,...what user error???
[Galaxy S III Android Development] FadeFx:
ah, its a kitkat rom, i can not discuss the kk kernel as i am on lollipop...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] EP21:
Still rom issues. Have AD 3.0.2 (kitkat based) with AK 1.7.2 and have no problems at all.
[Galaxy S III Android Development] Andii S.:
if it is a rom issue, why it's only with this kernel?

Send with a Lollipoped GT-I9300
[Galaxy S III Android Development] JustArchi:
Because if you didn't notice yet, AK uses latest sources and N7100 base, which doesn't go well with 3 years old ROM sources (regarding device support).

You can either accept that fact, switch the ROM or keep complaining.
[Galaxy S III Android Development] Andii S.:
would it help when I use a older version of your kk kernel?

Send with a Lollipoped GT-I9300
[Galaxy S III Android Development] Sn33z3x:
Can i use this for m440s. i saw a cm12 5.1 rom for m440s using this kernel
[Galaxy S III Android Development] JustArchi:
No, AK is compatible only with i9300, flashing it on any other device will most likely result with a brick.
[Galaxy S III Android Development] arter97:
If you want to add m440s support, forcing ro.hardware to smdk4412 will do.

Since the cmdline is being appended from the bootloader, that gets overridden.
[Galaxy S III Android Development] JustArchi:
We're approaching stable release of AK 2.0.

Which variant of sammy base you want to test firstly? SAMSUNG (i9300) or SAMSUNG_KOR (n7100 ports)?

I'll have new test releases soon.
[Galaxy S III Android Development] St3ve32:
Great news! And probably the n7100 version as its better compatible with lollipop roms? :)
[Galaxy S III Android Development] EP21:
Will there be a CM11 version?
[Galaxy S III Android Development] zapty:
Samsung KK (back to n00t port from E210S )
[Galaxy S III Android Development] dmukhin:
Does i9300 mean based on latest i9300 source release (kernel for stock 4.3) and another is based on latest Note 2 (for its stock 4.4)? Are both compatible with CM12.1? If so, is there any potential reason why i9300 could be better? Thnks
[Galaxy S III Android Development] D00ky:
None of them. My vote goes to AD 1.7.18
[Galaxy S III Android Development] EP21:
So basically i9300. AD 1.7.18 is i9300 based.
[Galaxy S III Android Development] D00ky:
You are right. My mistake.
[Galaxy S III Android Development] VanXamar:
If you're going to make both... Put them both up. :D lol

Enough flashoholics in the house that will try them both :cool:

My choice will go to n7100... Good experience with it.

By the way in synapse when I try to change lmk value with the arrows it adds up way too little MB. The sliders work fine. It wasn't like that on the previous experimental. Or is it a feature?

Anyways love your work... Thanks ;)
[Galaxy S III Android Development] kbhuvi:
Hi

Which version of this kernel should i use on a custom rom based on 4.3 tw

regards
[Galaxy S III Android Development] malachow:
Here:

The last option, SAMSUNG, is what you're looking for.
[Galaxy S III Android Development] JustArchi:
As I said, we're approaching 2.0 stable release.

This is supposed to be final test release, and so, I also brought other variants.

1. Don't flash on previous line of ArchiKernels (1.X), or any custom kernel. Flash this on stock kernel [ONLY], or previous 2.0 test version (28 Feb+).

2. If you have 2.0 test version (28 Feb+) already, you should clear Synapse's data prior to flashing to avoid conflicts. You can do so through Settings -> Applications -> All -> Synapse -> Clear data

3. This is a test release, expect bugs.

4. This is based on N7100 sources.

Fast changelog:

1. Updated ZZMoove to 1.0 beta7a

2. ArchiToolchain GCC 5.2

3. Fixed dm-crypt not working (CM 10.2 Regression)

As always, there are currently 4 variants.

They're divided into two categories, AOSP and SAMSUNG. As you should know already, AOSP variants are for AOSP ROMs, such as CyanogenMod, OmniROM, while SAMSUNG variants are for Sammy ROMs, such as original pure stocks, N7100 ports etc.

AOSP:

a) AOSP - For AOSP ROMs with 29 version of MALI blobs. Should work with all Lollipop ROMs based on my CyanogenMod sources (e.g. AD 3.1) and other similar ones (such as NamelessROM)

b) AOSP-OLD - For AOSP ROMs with 23 version of MALI blobs. Should work with older KK ROMs such as CyanogenMod 11

If you by any chance select wrong AOSP variant, don't panic, as the only thing you'll get will be black screen on ROM boot, just flash other variant afterwards.

Side note: Both AOSP variants have enforcing SELinux enabled. If kernel stops booting at Samsung Galaxy S3 logo, then it means that your ROM doesn't have proper SELinux security context (doesn't support enforcing SELinux), and as this is potential security issue, I do not plan supporting non-SELinux ROMs anymore. Latest CM11, and CM12.1 (from me) have proper SELinux contexts.

SAMSUNG:

b) SAMSUNG - For Samsung ROMs with 23 version of MALI blobs. Should work with all pure stocks from Samsung for i9300, and also N7100 ports.

b) SAMSUNG-NEW - For Samsung ROMs with 29 version of MALI blobs. Should work with all ported ROMs based on Korean SGS3 ROM (e.g. back-to-n00t and derivatives)

Similarly to above, if you flash wrong variant (black screen), just flash correct one.

All variants apart from AOSP one are untested by me, as the only ROM I'm using is AD 3.1. However they're all based on the same sources, they should work properly, but that's what test release is - you tell me.

All ArchiKernels include my own AnyKernel flashing method, they do not suffer from being "outdated" in terms of ramdisk updates. That's why AK can support nearly any ROM, as long as variant matches.

Have fun :).
[Galaxy S III Android Development] Blackyyy:
Installed ArchiKernel_150804_034807-AOSP on Dokdo-Project 6.5.2, it is amazing fast :)

But why I can't configure with Synapse? Message: No UCI support detected.

Edit: Okay after I start a second time it asked for root, now it works.

Thank you a lot :*
[Galaxy S III Android Development] St3ve32:
Hi Archi! I just flashed the new version, it's awesome as always. But is it better than the previous test version? Well how should I know?! You've made it so difficult to spot differences as the rom+kernel are already so very fast! :D but I guess it's even smoother, but remember - it's just a guess! :D

EDIT: no, it's actually really better! Apps starting faster and are more responsive :)

Odesláno z mého GT-I9300 pomocí Tapatalk
[Galaxy S III Android Development] zapty:
Not able to install on back to noot v9 !!
[MENTION=5161352]JustArchi[/MENTION] it shows error just after lollipop rom detectd even on 4.4.4
[Galaxy S III Android Development] JustArchi:
If you don't post log then don't expect your issue to get fixed. I do not plan wondering what is it, AK installer should already tell you what you need to do.
[Galaxy S III Android Development] ZjemCiKolege:
spam delete
[Galaxy S III Android Development] zapty:
Sorry Sir ,

Here is the log file that was produced during flashing !!

BTW i tried re flashing the ROM clean , still shows the same error !
[Galaxy S III Android Development] JustArchi:
Much better.

Alright, send me boot.img of your ROM and tell me what recovery you're using.

Either ramdisk is in some unknown format (unlikely) or your recovery is missing required tools to parse it (likely).
[Galaxy S III Android Development] nowismine:
Hey

Flashed over Build 13 of CM12.1

Synapse will not start, error: JSON configuration parse error.

Logcat attached.

Thanks
[Galaxy S III Android Development] zapty:
I am using philz recovery , and sorry a noob here dont know how to extract boot.img , maybe you ca help me with that ..
[Galaxy S III Android Development] JustArchi:
Then change it, because most likely your ROM is using LZO ramdisk and philz can't understand that. Latest TWRP works fine.

/data/.ArchiKernel/ArchiKernel.log

Although I'd try a reboot first.
[Galaxy S III Android Development] nowismine:
Hmmm... No such path, no such file... What am I missing!?

Already cleared synapse data, rebooted, cleared cache... No go
[Galaxy S III Android Development] JustArchi:
You tell me. I don't have such issues. Try through terminal, /data/.ArchiKernel is hidden.
[Galaxy S III Android Development] nowismine:
Could it be because i was setting selinux to permissive upon boot?

Ran ArchiKernel-Init manually which i saw created the folder in the first place so now it seems to work.

Will check if init runs on next boot.
[Galaxy S III Android Development] JustArchi:
ArchiKernel-Init should be run automatically by kernel through init.rc.

You can check if ArchiKernel-Init is added to the /init.rc file on bottom.
[Galaxy S III Android Development] nowismine:
Nope, not there.

Do i just add it or should i try to flash again ?
[Galaxy S III Android Development] JustArchi:
Flash again, this should not happen, installer for some reason detected that you're updating the kernel and did not append service init.

It checks if "ArchiKernel-Init" string exists in init.rc, and if not, it's appended.

Also check /tmp/ArchiKernel.log after flashing (before rebooting).
[Galaxy S III Android Development] zapty:
[MENTION=5161352]JustArchi[/MENTION] help !!

Changed the recovery to twrp ... Still shows error : devices resources busy

And then on boot synapse is installed but no kernel ..
[Galaxy S III Android Development] JustArchi:
Which part of "send log or didn't happen" you did not understand?

I'm seriously annoyed when people ignore my instructions and want to use my projects.
[Galaxy S III Android Development] zapty:
I just gave you the logs ..

The same log file was created again ..

Ditto..
[Galaxy S III Android Development] JustArchi:
I asked you to send me boot.img as well. You can extract it from your ROM zip.
[Galaxy S III Android Development] zapty:
here lies the boot image ...

www.arter97.com/browse/S3/ROM/back-to-n00t/kernel/

sorry couldn't upload the file itself as for my slow internet connection right now .
[Galaxy S III Android Development] JustArchi:
As expected, that ramdisk is in LZO format your recovery does not support.
[Galaxy S III Android Development] zapty:
tried philz ,CWM and twrp... what else is left ..
[Galaxy S III Android Development] nowismine:
Something is definitely rotten.. Or it might just be me.

Deleted .archikernel folder, reflashed, log looks ok after reflash, init.rc has the archikernel-init lines, but the .archikernel folder does not get created,.. So i am assuming at least something is not running correctly.

Left it on sel enforcing now.

If you have any other thoughts and think this is worth pursuing... Let me know

Thanks
[Galaxy S III Android Development] JustArchi:
Just tested with TWRP and works fine.
[Galaxy S III Android Development] JustArchi:
You're the first one to report that problem, and if service from init.rc doesn't get executed then you have much deeper problems than just AK not working.
[Galaxy S III Android Development] JustArchi:
Alright, I found a reason. Hold on, fix pending :).
[Galaxy S III Android Development] nowismine:
I kinda felt that coming..

Guessing you won't find it amusing if I raise this on the CM 12.1 thread, will you ? :)

Thanks for the pointers though and your work!
[Galaxy S III Android Development] JustArchi:
The thing is you won't get any help from me there as well because I never seen similar issue and it sounds like you really ****ed up your system. Can't reproduce = can't help :).
[Galaxy S III Android Development] JustArchi:
Go ahead and test this one, there shouldn't be any issue anymore.
[Galaxy S III Android Development] sensasian:
Some people just dont wanna share things

Its a shame though, no offence too Arte
[Galaxy S III Android Development] IlBella95:
Download link?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] MARKBOARD NETSET:
Great thread i hope one day i'll see my galaxy tab 2 P3100 led by this kernel at 3.4.xx or upper :D good luck devs

Once again open source meant for Care&Share so be collaborative in way to respect dev's credits and permissions.
[Galaxy S III Android Development] JustArchi:
V1.1.1 is here -> http://xdaforums.com/devdb/project/?id=4627#downloads

Bugfix release to 1.1.1.

Fast changelog:

Please check if exFAT still works. Flash this if you have problem with 1.1 release. More will come soon. New CPU topology is something new, as I didn't find it in any other kernel.
[Galaxy S III Android Development] szotaa:
Correct me if Im wrong but camera drivers are part of linux kernel. Since linux kernel is opensourced, samsung have to release compilable code which will give us same product as they use in their stock roms - I mean bugless camera. I wonder if there exist any organisation or foundation which checks if companies obey the GPL.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] microcens:
what about video recording issue in 1.1.1 ver?
[Galaxy S III Android Development] @non4:
Flashing now, will tell you if it still exists ;)

Update: Problem still there

Sent while my supervisor wasn't looking
[Galaxy S III Android Development] habylab:
Thanks for the update! Hopefully my camera will work now.

Here is a link to the download section, for those on mobile: http://xdaforums.com/devdb/project/?id=4627#downloads

Sent from my Linaro SM'd CM11 Galaxy S3, with arter's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] mrjoy:
Thanx for new version. Could we get chnagelogs for new version 1.1.1 plz?

Sorry i got the changelohgs. Thanx agaian
[Galaxy S III Android Development] arter97:
Sad to see this story ended up in a public post.

Now everyone will call me a selfish ***hole.

I had said "But I'd still love to help you out." and kindly suggested you to checkout DerTeufel's Git first.

I said I'm not comfortable just with sharing Git, exposing commits, I did not said I won't help you in any possible ways.

You said yourself :

Then you'll know better than anyone that my kernel is indeed U13 based kernel.

(Such as mdnie tunning is now written in "tuning", and the new arch/arm/mach-exynos/sec-switch_max77693.c etc.)

I'd like to ask you too, to edit OP and correct that statement.
[Galaxy S III Android Development] beeeto:
You said by yourself mate, maybe you just don't have XDA spirit and Archi's way of work (He shares god damn everything on his GitHub). But its ok I think, just don't come and spam on his thread or users (like me) will jump of you and eat you alive. We support Archi for a reason, and we all respect him for his professional and valuable work made here on XDA. And of course, everything he makes its shared and can be found on githubs open to everybody (Yeah, that goes even for you, unfair, right?)

Move along buddy.
[Galaxy S III Android Development] arter97:
Why do you think I came here?

If I don't and don't explain why I don't make my Git public, you guys will just continue to think I'm an ass****.

I respect GPL and uploads the kernel source, just not the Git commits.

You wanna hear why?

Because I already had three experiences with it, other devs shamelessly copies off my work and put it in theirs without proper permissions or credits. I'm glad to tell you there's two kernels out here already.

Everyone should know "'Opensource' does not mean 'no-respect'".

I know very well JustArchi don't do stuffs like this, but it'll be unfair to just allow him to access my Git while others can't.

I am a newbie developer here, and if some giant copies off my work, no one will notice and I'll be completely buried. (Which I had already gone through)

I don't want that to happen again.
[Galaxy S III Android Development] itizar1:
[MENTION=5161352]JustArchi[/MENTION], isn't there any possibility about merging f2fs?

i am thinking about flashing your kernel in future, please don't make me format my phone again :)
[Galaxy S III Android Development] beeeto:
Its OK for me mate. I think its a risk every dev take, not only you. That's how XDA works and it has been created on a base that everybody is building on the same house to make Android even better than it is already.

Stealing work is something against XDA open source spirit. It happens? Of course it does. But what if all devs think like you? There would be no improvement, no advances, there it would only be just 1 rom. The rom of the dev with the biggest knowledge. I have seen Archi start from zero, he started to compile his roms on Temasek base and ARHD, Wanam, not having as half of knowledge as he does know. Now he's creating and buliding new improvements for our device, and he share damn everything no matter what.

That's what makes XDA great. Being afraid of your work being stolen is not part of that spirit, its an exception of the rule. It happens here and everywhere, you should deal with that and do your best to accuse the guilty, not hide your work from all of us.

Just my 0,2 cents, not going to offtopic any longer.
[Galaxy S III Android Development] habylab:
Anyone else having camera issues? Or is it just me? I cannot open any camera app at all, nothing comes up. I've tried restarts and camera restarts too.
[Galaxy S III Android Development] JustArchi:
DerTeufel's kernel is not based purely on U13 sources like mine and yours. It's your decision and I must respect that, regardless if I like it or not. I don't want to start drama here, I said the truth. I.e. some users have camera problems (those with "bad" SGS3s) and I can't fix them because I don't know what's the root of this issue, if you managed to fix it, that's great, you're doing it for the community, don't you? We're not here to improve our CVs, gain fame or make money from open-source projects. Personally I think that sharing your work would only make things better for you, but I'm not here to tell you what's right and what's not. I've also started from scratch, as pointed above by some user. I did not have even one percent of knowledge I have now, I was nobody, check my registration date, it's not a famous 2007 or earlier, it's not even 2012. I joined exda about one and a half year ago, that's recent, isn't it? And now? I'm considered as one of the "head devs" for dying i9300, I'm doing working ports of N7100 ROMs and I'm also helping where I can. This does not only include my github and everything what is open-source on it along with history, it also includes i.e. pointing you at libsgcc.so dependency, which also fixed signal bar in your own ROM.

It's your choice whether you want to join happy developer community and make SGS3 better, or you don't. But don't blame me for community reaction for that decision.
[Galaxy S III Android Development] RushaPoiL:
You both are amazing ex-noob devs, you both want the same thing : to make me (and my GS3) happy, so....

[IMG="stop arguing"]http://i.imgur.com/OBYL4Ai.jpg[/IMG]
[Galaxy S III Android Development] DaReDeViL:
oooooo la laaaa ! What's happening here ?

You guys are both right in each one's pov. No need to debate on basic principles.

Sharing sources isn't only an obligation in open source world, but also a way to allow people verify there's nothing harmful in the code.

Plus, the main goal of most devs here is to have a good compiled ROM/kernel and share it with others, regardless of any return (thanks, donations, fame, glory ...)

finally, as I always say, a knowledge that can't be shared is a dying useless knowledge !

just my 2 cents (and half) ... [emoji6]

So guys, please bypass this situation and move on together to give new breath to i9300 as a lot of users count on you BOTH !!!!!

Envoyé de mon GT-I9505G en utilisant Tapatalk
[Galaxy S III Android Development] marcero:
Mimimi

[emoji24][emoji24][emoji24][emoji24]
[Galaxy S III Android Development] kicker63:
It work's fine on TWRP 2.8.7.0 you can find it here:
[Galaxy S III Android Development] zapty:
nope still not working .. still the same issue tried twrp , philz ...

downloaded 2 times to check

clean flashed ..
[Galaxy S III Android Development] JustArchi:
Log.
[Galaxy S III Android Development] zapty:
here is the log file. i think uts the same error as before the ramdisk problem.

https://drive.google.com/file/d/0B89wPY4DjNucZHVOQjdha1NtUXM/view?usp=docslist_api
[Galaxy S III Android Development] JustArchi:
No, it's not. That will be fixed later.
[Galaxy S III Android Development] zapty:
so a stable build straight away ?
[Galaxy S III Android Development] nkirk:
Hi JustArchi, a minor bug and a minor feature request. On boeflea equalizer band 4 will not register minus adjustments. If I select -1, it will move the slider to +1 itself.

Could you add 1704MHz step to the CPU frequency table? I have been using it stable for ages without any instability. I'm sure many do too. That's the only thing missing in your kernel. May be you can remove an unused frequency and sneak this in. :D
[Galaxy S III Android Development] DMCrimson78:
So, correct me if I'm wrong, but is this flashable straight on top of latest AD experimental? Then just wipe Synapse's data and good to go :) I saw a post mentioning it earlier, but wasn't able to find it.
[Galaxy S III Android Development] EP21:
Personaly i'm using 1200mhz and though it does have a few jitters (wish 1300mhz was brought back) it's smooth, plus, most of my games don't take too much of an advantage of higher clocks (asphalt 8 usually jumps between 500 and 1200mhz). Also with current gpu config of 640mhz@1087.5mV 1.6ghz isn't super stable (tried a variety of voltages between 1.3V and 1.4v). So unless you're playing fpse or ppsspp in software rendering (most games support hardware and 1.2ghz is enough for gta2 )