yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] nkirk:
Thank you for your personal views on the mater. However there are devices which are stabler at much higher frequencies (Like mine) At your quoted frequencies you are missing out a lot in performance.

GPU at 640 will not yield much performance at games. Infact it will cause poor performance due to the unnecessary heat generated and cause thermal shutdowns..sudden reboots etc.

Why you see the frequency jumping around is the thermal protection kicking in.

I run mine at 533MHz@1025 mv. CPU at 1704@1350 mv. Super stable with no errors, reboots, corrupted data or apps getting killed/stopping randomly.

Increased CPU clock is easily felt when browsing. It helps a great deal to other CPU heavy tasks by offering quick frequency bursts.

Battery life is another story altogether :D

I wish the availability of the frequently so that better devices could make use of it.
[Galaxy S III Android Development] EP21:
Throtling aside the frequency variation happens even when the device is cold 20-30c ambient, battery reports 25-35c (need to play for at least 30min on charger for the battery to reach +44c.

Also the performance boost is notable in gaming (20-60fps asphalt troughout 90% of available tracks and conditions). I do agree that cpu oc is better for web browsing (which i do quite a lot), i prefer gpu oc since archies optimizations and other magical stuff since 4.0.4 have removed the need for a 1.6ghz cpu down to a 1.2ghz (i actually see the diference, since i've had the device since august 2012), and yes, i do agree that 640 is a less stable frequency than 533, but it's the last frequency for me that is 90% stable(sometimes i get a gpu stop for 5-10sec, but it happens every 20-40min while gaming or a bit more offten when 7x24 without a rebot) and is used only when gaming. If anyone wants pm me for my cpu and gpu config.
[Galaxy S III Android Development] nowismine:
Just a confirmation that it's fine with B14.

I tried wiping system and flashin B13 then ArchiKernel and behaviour was the same, but worked with B14.

System un****ed. Happy now :)
[Galaxy S III Android Development] JustArchi:
As I said, we're approaching 2.0 stable release.

This is supposed to be final test release (#2), 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. Added workaround for bluetooth deadlocks found in AOSP Lollipops. This change is in AOSP variant only, as other variants do not suffer from that problem.

2. Added a possibility to change wi-fi MAC address (thanks to siracuervo)

3. Fixed LZO stock kernels failing with flashing AK 2.0 (test from users pending, I'm still not sure if I won't have to force GZIP due to kernel size, you tell me, with proper logs if needed)

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] zapty:
Error Log for build #2 : https://drive.google.com/file/d/0B89wPY4DjNucRzdTTm5wNDd4R1U/view?usp=docslist_api
[MENTION=5161352]JustArchi[/MENTION] flashing the kernel still produces the same error as before ..

but now when i reboot it goes into bootloop , and by bootlopp i mean it loops the Galaxy SIII screen and then shuts down and again boota and so on.

Best of luck with squashing this bug !!

:)
[Galaxy S III Android Development] JustArchi:
As I initially thought kernel is too large to be flashed onto the block with lzo. I'll need to change compression of that to gzip.
[Galaxy S III Android Development] VanXamar:
By the way since I flashed your latest AK I have no more problems with Bluetooth calling distortion... I don't have to switch to 2g anymore... Hoping it stays that way:D... Build 14.:D
[Galaxy S III Android Development] brianelv:
When I try to enable Swap with the external SD Card Synapse throws an error.

I'm using Archidroid 3.1.1 Experimental with the latest ArchiKernel posted here a few days ago.

I tried with FAT32 and EXT4.

Any solutions? Thanks :o
[Galaxy S III Android Development] odyss199:
i have the same error but swap is not making a big difference, instead enable zram and set it to 200 MB per block
[Galaxy S III Android Development] The Funky Pear:
Good evening to all.

Can anyone help me for a configuration to achieve very low cpu and battery temperature?

I dont care about performance,i just need my phone cool

Even if the phone opens chrome after 1 minute.
[Galaxy S III Android Development] shaarky:
[MENTION=5161352]JustArchi[/MENTION] , not sure I can have a wish for my brother, but if yes - is there anything significant missing to make your Kernel compatible with DSLR Controller from Chainfire ? Is it USB host ? Both combo ArchiDroid and ArchiKernel doesn't work. It's working with Boeffla, but would like to stay on ArchiDroid with ArchiKernel.

http://dslrcontroller.com/about.php

Requirements

An Android device with an ARMv7-A or newer CPU architecture (virtually all 1ghz+ devices)
Not rooted: Android 3.1 or higher with USB host kernel+API support
Rooted: Android 2.3.1 or higher with USB host kernel support
[Galaxy S III Android Development] JustArchi:
Support for USB OTG is already enabled in latest snapshot, and if you're using it (the version that comes with AD 3.1) then it should work already.

If you have it and it doesn't work, and if you wish to add support from me, please ask Chainfire with the link to my kernel config, what exactly his app needs from the kernel to be able to support his APK, as I didn't find any relevant info and I'm not going to play try-and-catch game with enabling all USB drivers.
[Galaxy S III Android Development] shaarky:
Thank you, sorry for one additional question, but then 3.1.1 Experimental (I know it is "experimental") with latest Kernel from your post above should work, right ? I can ask Chainfire, but I don't thing he will reply... still will try depends on your answer, thanks.
[Galaxy S III Android Development] JustArchi:
Yep.

I'm not going to guess by my own as I don't own your controller. You can also ask Andi.
[Galaxy S III Android Development] shaarky:
I'm sorry JustArchi, it actually works with latest version of DSLR Controller, which is also compatible with Android 5.0 - we realized it while testing via "lite" version Remote Release, . It is very hard to "navigate" with brother remotely. :o Thank you for all your replies. :good:
[Galaxy S III Android Development] The Funky Pear:
Downloads dont work. I download the latest archikernel posted with 9kb/s. I tried to download something else to check if it is internet related,but it isnt.
[Galaxy S III Android Development] JustArchi:
Swapon fails for whatever reason, I reproduced that issue and don't have any solution for now.
[Galaxy S III Android Development] The Funky Pear:
Bug report: vibration doesnt work or is very low
[Galaxy S III Android Development] JustArchi:
Stop bringing your ROM's issues here.
[Galaxy S III Android Development] The Funky Pear:
My rom is archidroid 1xx
[Galaxy S III Android Development] arminbih:
Using latest experimental with your week 16 and it is flying, I can't seem to notice the difference with KSM (kernel samepage merging) on or off, what do u recommend
[Galaxy S III Android Development] St3ve32:
If you turn it on, you'll get a bit more ram but also a lot of "can't connect to camera" errors. The latest archidroid experimental 3.1.3 has so much free memory that I can't find any single reason to turn KSM on :)

Odesláno z mého GT-I9300 pomocí Tapatalk
[Galaxy S III Android Development] Hamx5:
Hi, I'm using this kernel and I like it so much. But I have a small problem: video and audio streaming often plays faster then normal, without sound. I made a clean install.

Sorry for may bad english, I'm Italian
[Galaxy S III Android Development] DrmohamedShawky:
have strange issue with vibration

am on archiroid 1.7.18

i cleaned install it with stock kernel then flashed latest test kernel for sammy

i pressed once on test vibration in synapse and when i did that

my phone always have that hazy vibrations barley i can feel it

i set it to higher level then save

it works well for seconds then same error

flashed back stock kernel and it worked fine

kernel is pretty stable this is the only issue i faced till now
[Galaxy S III Android Development] JustArchi:
Good find. Haptic interface should be totally disabled for Samsung variant, as it's incompatible. You can change vibration settings in options. Will be fixed in next version.
[Galaxy S III Android Development] tokariew:
Archi on latest 3.1.3 vibration test end with fc

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] DrmohamedShawky:
+1
[Galaxy S III Android Development] Andreas21:
+1 same for change governor button innside zzmove tab.

Sent fra min GT-I9300 via Tapatalk
[Galaxy S III Android Development] The Funky Pear:
The Funny part is that i mentioned it a week ago and he said stop bringing you ROM issues here :p
[Galaxy S III Android Development] VanXamar:
W

Just relax... In a few days it will go back to zzmoove... Lol.

I had the same and now it fixed itself... Restart didn't help either. Dunno what happened. Something with synapse I think getting stuck on Pegasus or something.

Edit; I've been monitoring this issue for a quite a while... It looks like hotplugging get turned off... Example If I leave my phone idle with screen on it will stay on all 4 cores 200 mhz... No matter the governor that's active. no error what so ever in synapse. It boots up normally. I'll do a clean wipe again see if something went wrong. I'll report if it helped.

Edit2; till now no problem with hotplug after the clean install for the second time. Will report if it changes.

Edit3; d* it... Changed governor and

now no more hotplugging..all 4 cores up again running at the same speed. No matter what governor. So Clean install won't help... Something in synapse I guess. By the way I'm om 3.1.3. No other problems or reboots just this weird thing.
[Galaxy S III Android Development] hamza touati:
hello [MENTION=5161352]JustArchi[/MENTION] is there a stable version of archikernel 2.0
[Galaxy S III Android Development] St3ve32:
Not one with the "stable" mark, but the latest experimentals that can be found a few pages back are stable :)

Odesláno z mého GT-I9300 pomocí Tapatalk
[Galaxy S III Android Development] DMCrimson78:
Oops, wrong thread...
[Galaxy S III Android Development] hamza touati:
solution

i have fond the solution for this problem (all cores stay on ) you have to go to settings in synapse and disable ''''' apply on boot ''''''' :cool:
[Galaxy S III Android Development] VanXamar:
Thanks I'll try. I'm now on 3.1.4. Ex. And the problem is almost gone. Only sometimes it happens.

But if you don't apply at boot your settings don't stick right? Like lmk values and stuff.
[Galaxy S III Android Development] JustArchi:
ArchiKernel V2.0

Download, changelog, and cookies

ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.

AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.

AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.

SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)

SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port

ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
[Galaxy S III Android Development] rpdroky:
Thank you sir ! Yre the greatest :cool:
[Galaxy S III Android Development] EP21:
Can i flash this on top of the AK build that came with stable 3.1.3 ?
[Galaxy S III Android Development] JustArchi:
Most likely.
[Galaxy S III Android Development] huongthanh8690:
Hi Archi : can use on S3 korea E210S :D
[Galaxy S III Android Development] konohanz:
I think you can use between SAMSUNG and SAMSUNG_NEW base on ROM you're using, whether it was JB or KK.
[Galaxy S III Android Development] cashflow67:
It depends on Rom version, not variant! If you use 4.4.4-4.4.3 use SAMSUNG_NEW

If you use 4.4.2(QS Port(N7100 based), Use SAMSUNG!
[Galaxy S III Android Development] huongthanh8690:
Thanks reply , i tried 2 version , but failed :(
[Galaxy S III Android Development] cashflow67:
Ask JustArchi. Tag him like that [MENTION=5161352]JustArchi[/MENTION]
[Galaxy S III Android Development] zapty:
[MENTION=5161352]JustArchi[/MENTION] finally successfully flashed on back to noot but the vibration isn't working and synapse shows nothing no settings at all...
[Galaxy S III Android Development] Chimbat:
Obviously the new kernel 2.0 is working fine with AD 3.1.4 on my I9300.

Thanks.
[Galaxy S III Android Development] tokict:
Of course it will not work. Archikernel work only for i9300.
[Galaxy S III Android Development] sleeper994:
I flashed Archi kernel 2.0 on my s3 running ArchiDroid 3.1.4, but the fwifi seem not to be working, as I can't switch it on. Maybe its problem cause I was running Boeffla before flashing ArchiKernel?
[Galaxy S III Android Development] myshakugan:
Not maybe, it's definitely due to the fact that you installed it on top of boeffla. You need to be on stock kernel before flashing AK. Read the OP for instructions.
[Galaxy S III Android Development] Jorge R:
Very good kernel , I thank my phone has many developers. But will return to boeffla ( uber ) or agni , I feel that this kernel has more power . Still kernel arch is in its early versions , and have problems with vibration .

Archi force, I never saw a developer as committed as you and others
[Galaxy S III Android Development] Minto107:
No you can't. You should have M440S. E210S=I9305 M440S=I9300

Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
[Galaxy S III Android Development] JustArchi:
Vibration issue will be fixed in 2.0.1, and affects only sammy kernels.
[Galaxy S III Android Development] The Funky Pear:
Greetings,archi.

Just a quick question- which are the key points to look to compare a kernel with another?? Where to look? Ram management? Laggs? Battery life?thanks!!
[Galaxy S III Android Development] ravitez86:
Installed V2.0 on archidroid 3.1.3 still now no issues :)

awesome battery life...!

79%-38% in 24 hrs

1hr screen on time..!
[Galaxy S III Android Development] renierx:
Negative equalizer band gains in Boeffla sound

Thanks for the ArchiKernel V2.0, still using its Samsung variant with Archidroid 1.7.18. I like the Synapse app settings, but cannot set negative equalizer band gains in Boeffla sound. They are reverted into positive (absolute) values immediately after pressing apply button. Anybody can confirm this?
[Galaxy S III Android Development] Metaldroidiano:
installed 3.0 on stock sammy 4.3. Everythings ok except as you know vibration. I like very much synapse app, i disinstall stweaks. It's more easy.

Very appreciate more i\o scheduler, and cpu governor profile.

Waiting 3.0.1 for vibration, pretty urgent cause i use always phone in silent mode
[Galaxy S III Android Development] tandrcak90:
I have glitches on markox cm11 with this kernel,a lot of graphical glitches...
[Galaxy S III Android Development] Busaton:
Works on SlimLP?
[Galaxy S III Android Development] EP21:
Yes, for me to the negative band settings revert to same values except positive (turns from -5 to +5). Am using AD 3.1.3 with AK 2.0
[Galaxy S III Android Development] cashflow67:
[MENTION=5161352]JustArchi[/MENTION],

Can you update your zzmove sources with new zzmove sources? I think there are problems on zzmove governor profiles. Zanezam Battery Plus must be bat saver and fast setting, but I suffer so many lags. My Rom is QS Port for i9300 OE1(4.4.2), Your latest kernel v2.0(SAMSUNG)
[Galaxy S III Android Development] JustArchi:
ZZmoove is already in latest version.
[Galaxy S III Android Development] Leang Vannak:
thank for the latest kernel. it is very awesome.
[Galaxy S III Android Development] renierx:
[MENTION=2767810]EP21[/MENTION], Thanks for confirmation.
[MENTION=5161352]JustArchi[/MENTION], can you please look at it?
[Galaxy S III Android Development] jasi275:
Got in boot loop by flashing archi kernal 2 aosp on temasek v17. When the phone boots on lock screen it reboots again.
[Galaxy S III Android Development] kicker63:
Flash stock kernel from temasek v17, then flash archikernel 2.0
[Galaxy S III Android Development] VanXamar:
It happened again today (after few days) after I manually restarted my phone ... Your workaround worked. But I had to start synapse manually 2 choose governor zzmoove again and turn boeffla sound on again. I'm on v2.0 ak. AD 3.1.4.

Maybe delaying synapse a few seconds more to start would solve this.
[Galaxy S III Android Development] mahe.:
[MENTION=5161352]JustArchi[/MENTION],

Any word on profile switcher addtion to synapse(or we need to use stweeks?). I use to switch between pegasusq and zzmoove regularly according to my need. So just thought of asking this (may be i am use to this feature from boeffla config app. Sorry for that).
[Galaxy S III Android Development] jonners59:
I need a steer, and please, apologies for my ignorance.

I have an i9300 that has been wiped of all Samsung and I am currently running Revolutionary S5 ROM with 3.0.31-2454463 dpi@DELL314 #1 kernel, which I believe is the stock for this ROM.

I want to try out your ArchiDroid_V3.1 ROM and the ArchiKernel_V2.0 with it. I was concerned by the warning on the first page about installing this kernel over an existing kernel and potentially bricking my phone. Would it be safe to install, or should I wipe the phone or should I avoid doing anything and just install the new ROM??? I am using TWRP v2.8.6.1 recovery
[Galaxy S III Android Development] EP21:
If you're switching roms do a clean flash(wipe evetything except bootloader(recovery), efs(aka modem, aka ril), exsd. (Think that's all here)

If you want to try the kernel make sure you have the defaul one of your rom, no wipes needed (i think).
[Galaxy S III Android Development] jonners59:
"If you're switching roms do a clean flash(wipe evetything except bootloader(recovery), efs(aka modem, aka ril), exsd. (Think that's all here)

If you want to try the kernel make sure you have the defaul one of your rom, no wipes needed (i think)."

Yes, but this is what worries me. "........ make sure you have the defaul one of your rom, ......." It is not clear what this means exactly. I wiped my phone completely when I installed Revolution ROM... So the original Kernel does NOT exist any more, it only has the one that came with Revolution. So, if I flash THIS kernel will it brick my phone or not, or is the kernel I have OK, is that what it means?

The rest I am fine with......
[Galaxy S III Android Development] D00ky:
When you've flashed Revolution ROM it's also installed it's own kernel. If you haven't flashed any custom kernel after that you are good to go.
[Galaxy S III Android Development] jonners59:
EXCELLENT..... That's all I needed to know.

I am going to finish re-installing Revolution and then back it up, move the backup to an SD Card and then try the new kernel and Archi..... Thank you!
[Galaxy S III Android Development] JustArchi:
I'm not Synapse developer, you should contact with AndreiLux for such requests.

Will do when I have some time.
[Galaxy S III Android Development] mahe.:
Thanks Archi. [MENTION=4167023]AndreiLux[/MENTION] any plans to bring profile switcher in synapse?
[Galaxy S III Android Development] JustArchi:
ArchiKernel V2.0.1

Download, changelog, and cookies

ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.

AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.

AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.

SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)

SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port

ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
[Galaxy S III Android Development] The Funky Pear:
hello,can you tell me what is the entropy collection from internal storage I/O operations option??should i disable it?because you say improves i/o speed for the cost of lower kernels entropy pool.what is entropy poool?
[Galaxy S III Android Development] thommy200:
Sharpness tweak

Why is there no screen sharpness tweak present in synapse?
[Galaxy S III Android Development] :
Just a reminder,

Stay on topic and don't ask for ETA's.

Thank you.

The_Merovingian

Forum Moderator
[Galaxy S III Android Development] Daniel Bostan:
after flashing this kernel on my i9300 with slimlp 0.8, I can't manage to make the incall speaker to work. basically, when making a call, I can't hear anything... any workarounds?
[Galaxy S III Android Development] lxender:
when flashing the 2.0 kernel on 4.4 AOSP rom. The screen keep flickering. why this happen?
[Galaxy S III Android Development] Chimbat:
You installed the aosp_old kernel over stock kernel and you wiped the synapse data, right?
[Galaxy S III Android Development] JustArchi:
Because the ROM uses broken HWC or logic, and AK never supported and never will support broken ROMs.
[Galaxy S III Android Development] sassinapoli:
I've bootloop when flash this kernel on kk 4.4.2 miui rom.

This: http://xdaforums.com/showthread.php?t=3130847

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] marenp:
That rom doesnt support custom kernel.