yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] JustArchi:
Ouh, It should be easy to fix, my script should handle lzop as well with some little modifications, will see how far we can go with it. Great that you found out what were wrong! :)
[Galaxy S III Android Development] cba1986:
Hey [MENTION=5161352]JustArchi[/MENTION]

Take a look at this:

http://xdaforums.com/showpost.php?p=56569791&postcount=621
[Galaxy S III Android Development] JustArchi:
Want to be a guinea pig? :D

Edit: Going further, there's no similar entry for mach-midas (SGS3). So actually your post covers only that particular device.
[Galaxy S III Android Development] cba1986:
Of course. my i9300 is two and half years old. it had a long life :D
[Galaxy S III Android Development] JustArchi:
We have that already btw.
[Galaxy S III Android Development] Mostafa Wael:
[MENTION=5161352]JustArchi[/MENTION]

So you see that this Panel Overclocking is not possible for our S3 (i9300)

Sorry but I don't understand the Terminal thing.

:D

Maybe a small explanation please, we like to learn. It is human nature :)

---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------

@Moster2

Great great work hard worker

I really appreciate your contribution in this kernel

Thanks for figuring out the problem with back-to-n00t V5 ROMs

IMO the thanks button isn't enough for you :D Nor JustArchi too :D
[Galaxy S III Android Development] JustArchi:
What you want to overclock? Refresh rate of the display? It's 60.0+ KHz for SGS3, not 57. What you want to overclock it to? 65? What does it give for you? Nothing, smoother doesn't mean better. The final effect will be that you will get even less screen on time because display will be refreshed more often. Human eye barely can spot a difference in 50+ FPS, and you want to overclock 60 to 65, just for the lulz. Is this science?

You're getting excited for nothing. Overclocking refresh rate was there since first CRT monitors, and it's nothing new that you can do it. The thing is that you won't get much, up to A FEW KHzes more for the cost of custom refresh rate, worse battery life and god knows what the hell will break with AOSP and exynos.

Not even mentioning that SGS3 doesn't have .freq property, and we're not using mach-u1 but mach-midas.
[Galaxy S III Android Development] Mostafa Wael:
Oh I see

Thanks for explaining :)
[Galaxy S III Android Development] rutz@8038:
[MENTION=5161352]JustArchi[/MENTION]

Firstly, thanks for the kernel.. Gives the best battery life as compared to others..

I'm noticing camera not connecting issues though since 1.5.2..

To verify.. I switched back to stock kernel and everything worked fine.. Switched to Archikernel and camera again couldn't connect or work..

Tried on Omni.. Cyanogen.. Temasek.. Carbon just to be sure..

Any solutions?
[Galaxy S III Android Development] nightwing90:
The camera failure issue is not related to kernel. Just download Restart Camera apk by Temasek and install,grant superuser access and that's it :cool:
[Galaxy S III Android Development] racky29:
Ive been using CM11 nightly Official

I decided to try archikernel 1.5.3

Now the same problem as come back as with archidroid/archikernel

With charger in, Shutdown wont shutdown only reboots phone
[Galaxy S III Android Development] Sargos76:
my doesn't shut down to charging or not!

SGS3 GT-I9300 / ArchiDroid 1.7.18
[Galaxy S III Android Development] JustArchi:
And I already said that it's not my fault that CM relies on LPM implementation from 2-3 years ago. AK is "too new" to work properly with outdated CM while in bootloader mode. And I don't want to include workarounds for that situation, as it's not the kernel which is faulty. In fact, all currently included workarounds (such as this one or that one) should be reverted at some stage, if there would be someone who fixed all upstream CM problems...
[Galaxy S III Android Development] GeeckoDev:
Just passing by. Panel overclocking isn't about smoothness but rather lowering input lag.

Going from 57hz to 62hz on the Note makes a freaking huge difference in responsiveness (input lag drops by a little more than 1ms). Please experiment, I'm interested about how far the i9300 screen can go.

Seeing your screenshot in the earlier post : gralloc reports 60.51hz because of a bug. It should be 60.00hz. I think this could be the cause of frame skips.
[Galaxy S III Android Development] JustArchi:
This doesn't change the fact that i9300 doesn't have .freq property. It's not as single as changing one line (we use mach-midas). Also, I don't think that lowering input lag by one to two miliseconds makes a "huge difference".
[Galaxy S III Android Development] GeeckoDev:
It's right there. Give it a try before making assumptions :)

Edit: you'll have to check logcat to see what gralloc reports.
[Galaxy S III Android Development] JustArchi:
Alright then, will make some test builds soon.
[Galaxy S III Android Development] GeeckoDev:
Cool! Please give me some feedback once you're done :highfive:
[Galaxy S III Android Development] JustArchi:
AK users will give you that, hope they won't fry their panels :p.
[Galaxy S III Android Development] GeeckoDev:
I actually tried 75hz and 65hz on my phone. It just desyncs. Screen gets white after a while, but it doesn't break anything.

Your point about "custom" refresh rates might be valid. At first, I just wanted to get 60hz on the Note... well, I've been using a 62hz build on my phone for one full day and it's even better. Didn't test games though, that's what I'm afraid of. I think most developers assume that the device runs at 60fps.

Edit: also, I can't get past 59hz on AOSP and 62hz is the limit on Touchwiz roms. Still can't explain it :rolleyes:
[Galaxy S III Android Development] JustArchi:
I see a point in overclocking 57 to 60. But past 60... I'm not sure. I'll make my mind after first tests.
[Galaxy S III Android Development] GeeckoDev:
Yep, my thoughts exactly.
[Galaxy S III Android Development] simplicio11:
Any news on upstreaming to Linux 3.2, 3.4, 3.10?

Thanks for your awesome kernel!
[Galaxy S III Android Development] Mostafa Wael:
I think he is very busy to work on it now.

He is working hardly to bring up a brand new ArchiDroid 3.X to a stable state, plus , in the WIP android Lollipop world by arter97, he is working to build an alpha CM12

So maybe next year?!

JustArchi will give better info on that
[Galaxy S III Android Development] JustArchi:
It's close to impossible, I can't bring it even on 3.1 level. I dropped upstreaming until I have load of free time and nothing to do.

https://github.com/JustArchi/ArchiKernel/commits/m0-up
[Galaxy S III Android Development] you_man:
Hi guys. I am leaving on a business trip and so I need to get the most out of your phone battery life can be time.

So the question to you (there is no possibility to check and compare).

From a technical point of view, for the same kernel config Boeffla and Archi which of the kernel give a better battery life?
[Galaxy S III Android Development] JustArchi:
https://github.com/JustArchi/ArchiKernel/commit/3a2da1e0aa72f11c106b15ac683aa29ef3f50959

Now it should work properly :).
[Galaxy S III Android Development] JustArchi:
Could someone check this on back-to-n00t? I'm too lazy to flash the whole ROM today.

If flashing fails, please attach log as instructed.
[Galaxy S III Android Development] marenp:
It can be flashed over boeffla?
[Galaxy S III Android Development] JustArchi:
No, always flash over stock kernel, unless developer specify in the post that test kernel doesn't use anykernel method. This one does.
[Galaxy S III Android Development] @non4:
Never use an anykernel over another custom kernel. Causes so many headaches. Symptoms include cursing the developer, then eventually yourself for not reading the OP
[Galaxy S III Android Development] Yeti47:
Seems to work fine. Flashed fine and everything seems to work. Will use it for thr rest of the day and let you know. Silence means all is good.

Thanks :)
[Galaxy S III Android Development] Yeti47:
Only slight issue on this ROM is that stweaks forgets all my settings on reboot. When you apply any change, it shows the value as $. Not too concerned with that though as seems stable enough and assume this is a simple fix when released officially. Tried the other apk versions from your other Samsung kernels, but no change, so assume it needs a tweak for this rom... Thanks for creating this port!
[Galaxy S III Android Development] JustArchi:
ArchiKernel V1.5.4

Download, changelog, and cookies

Have fun.
[Galaxy S III Android Development] Moster2:
The rom is missing busybox. Install it from playstore

https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
[Galaxy S III Android Development] Yeti47:
Thanks, reflashed the Rom and forgot to reinstall it. Cheers :)
[Galaxy S III Android Development] lmulli:
Doesn't work for me on Archidroid 3. I get a boot loop where it just brings up the initial white Samsung graphics and keeps on rebooting to that. Flashing back to 1.5.2 doesn't work either. I have had to reinstall Archidroid 3 again in order to get the phone to work.
[Galaxy S III Android Development] JustArchi:
Works fine for me on latest experimental.
[Galaxy S III Android Development] Sargos76:
all ok on 1.7.18

SGS3 GT-I9300 / ArchiDroid 1.7.18
[Galaxy S III Android Development] vldesco:
Make sure that the current kernel is the stock kernel (included with ROM) or previous AK version, if you were using any other kernel, you must reflash AD (expert mode) with stock Kernel and then flash the new AK.
[Galaxy S III Android Development] lmulli:
It was on AK 1.5.2. No biggie. I've wiped the device completely anyway - it was time for a late spring clean in any case!!
[Galaxy S III Android Development] microcens:
i just flash 1.5.4 kernel over 1.5.2.

in the drop down menu in settings it says thereis no gsm network...
[Galaxy S III Android Development] abhibnl:
I'm no expert man but afaik, kernel has nothing to do with network settings. Though it has wifi modules so wifi can be an issue but gsm network?

Sent from Galaxy S3 Powered by AD 1.x + Boeffla
[Galaxy S III Android Development] JustArchi:
Kernel has nothing to do with the GSM.
[Galaxy S III Android Development] kenzolo:
[MENTION=5161352]JustArchi[/MENTION]

Where I can check in the source of the rom the mali driver version?

EDIT!

SOLVED
[Galaxy S III Android Development] EP21:
Are you planing to bump up the driver version?
[Galaxy S III Android Development] JustArchi:
You can't.

It's a library of /system/lib/libMali.so

On boot dmesg/logcat always says the API version, so you can also check that.
[Galaxy S III Android Development] giovag7:
Deleted
[Galaxy S III Android Development] FireBlazeGT:
[MENTION=5161352]JustArchi[/MENTION]

Stweak app is buggy!

Everytime I open the app, it shows that option to apply or discard... and on every boot the values gets restored!

All the GPUFREQ values are set at 700MHz , touchboost at 1200MHz and etc etc...

Please help!!!
[Galaxy S III Android Development] JustArchi:
You didn't say anything new.

Use other apps or echo values directly if you don't like STweaks.
[Galaxy S III Android Development] FireBlazeGT:
Ok! Any Config app recommendation?
[Galaxy S III Android Development] JustArchi:
Trickster mod.
[Galaxy S III Android Development] FireBlazeGT:
Okay Thanks Bro :)
[Galaxy S III Android Development] Poesini:
Hello guys,

I dont have an S3, but I was trying to compile my kernel sources for OnePlus One, but I wanted to make some experiments and when trying to add LTO to my kernel source, it comes up with this:

In file included from include/linux/topology.h:32:0,

from include/linux/sched.h:77,

from arch/arm/kernel/asm-offsets.c:13:

include/linux/mmzone.h:357:32: error: ‘MAX_NR_ZONES’ undeclared here (not in a function)

unsigned long lowmem_reserve[MAX_NR_ZONES];

Does anyone know why is this happening?

Thank you very much guys
[Galaxy S III Android Development] Moster2:
Stweaks is not buggy. Your rom is missing busybox.

https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
[Galaxy S III Android Development] FireBlazeGT:
Oh yeah man! You are right! Now it works fine :)
[Galaxy S III Android Development] itizar1:
does r4p0 one include gralloc and hw composer fixes of nameless?
[Galaxy S III Android Development] JustArchi:
This is the kernel, hwcomposer and gralloc are ROM things.
[Galaxy S III Android Development] Code124Y:
WoW... didnt know that... maybe we are reading from different kernel thread and misunderstanding over here...

ops... N7000 thread lol! someone bring this info to andi thread lol....
[Galaxy S III Android Development] Maddinuser:
How do I flash AK on top of Arter97 Kernel?

Even when I install Archidroid 3 again it does not boot (Stock or Archikernel selected). It's also not booting if I install AK after new installation.

I've also tried "Ultima Stock Kernel" before flashing, does not boot. (read it in Arters thread).

Flashing Arter Kernel after all that and I can boot...

I want to avoid Full wipe. Thanks!
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
When we get this kernel for android 5.0?
[Galaxy S III Android Development] JustArchi:
Upstreaming to Linux 3.0.101 didn't help either.

This is dead end for me until someone finds out what's wrong. Probably AOSP for I9300 highly relies on some outdated component that Sammy changed somewhere between Update 7 and 13. Honestly I don't care at the moment, if stock works fine then CM/Omni should fix this issue.
[Galaxy S III Android Development] beeeto:
Darn, sorry to hear that buddy, your kernel was pretty impressive. Sad news to hear this is a dead end. Hope we get better news soon.

Kudos.
[Galaxy S III Android Development] JustArchi:
ArchiKernel V1.1 released. http://xdaforums.com/devdb/project/dl/?id=6995&task=get. You should still consider this as a "preview", however it works pretty stable if you keep in mind known bugs.

Changelog:

Notice on exFAT:

Kernel has now built-in support for exFAT filesystem. This benefits AOSP while keeping Sammy (comming soon) happy. For AOSP, this fixes exFAT, as ROM can now use both native exFAT support as well as FUSE implementation. exFAT has been tested on CyanogenMod and works properly, however OmniROM doesn't like it for some reason, and I'm not going to look why so, because it's FUSE bug as built-in exfat support can't conflict with it due to the fact that kernel has only additional ability to parse exfat filesystem when such is called. This is probably connected (AGAIN) with some dirty workarounds to make it work across all smdk4x12 devices and I'm saying "hell no". CyanogenMod does it in proper way.

Notice on SCHED_MC and SCHED_SMT:

Multi-core scheduler support improves the CPU scheduler's decision

making when dealing with multi-core CPU chips at a cost of slightly

increased overhead in some places.

Improves the CPU scheduler's decision making when dealing with

MultiThreading at a cost of slightly increased overhead in some

places.

This should potentially make the system more snappy.
[Galaxy S III Android Development] Andr3y29:
It is OK if we flash over the existing ArchiKernel or should we flash the rom again?
[Galaxy S III Android Development] Curst:
I flashed it on top of 1.0 on my CM11-M7 and it booted just fine here.
[Galaxy S III Android Development] JustArchi:
Yes, it's fine. ArchiKernel "takes" ramdisk from currently flashed kernel. So if AK 1.0 took ramdisk from stock, and now AK 1.1 takes ramdisk from AK 1.0, it will still be stock ramdisk :).
[Galaxy S III Android Development] d1rekt0r:
Have you attempted to upstream kernel higher than 3.0.101 ?Is it possible at all ?
[Galaxy S III Android Development] JustArchi:
I tried and I'm afraid to tell you that it's not possible. Technically yes, it's possible, but amount of conflicts is too damn high to even consider merging.

Samsung modified kernel sources too much. In fact, it's not 3.0.31 or 3.0.101, it has random commits from every branch.

Upstreaming Linux kernel over 3.0.x would result in unstability at best, kernel panics at worst.
[Galaxy S III Android Development] habylab:
Ah okay, might want to take out that you may have done that in the future in your OP!

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] shabtab:
Any idea on how to fix the sharpness??

and even the backlight on buttons,, they wont turn off until the screen does...

vibration level also very strong and as no more tweakable by cm after today's update any help would be appreciated...
[Galaxy S III Android Development] zadusimple:
Hi [MENTION=5161352]JustArchi[/MENTION], does the latest version fixes video recording issue? Also, will 1.1 effect battery life compared to version 1.0

Sent from a better Galaxy designed for humans!
[Galaxy S III Android Development] _moelle:
For now, I tried SOKP, ArchiDroid and newest Temasek V101, everytime clean install und everytime reboot while starting camera app :( ...is there any solution? am i the only one facing this problem`?
[Galaxy S III Android Development] HammDefy:
The same reboots with Omni....

S3/Omni 4.4.3
[Galaxy S III Android Development] djpetros24:
Very Good job my friend

I tested now the 1.1 version with archidroid 2.4.6 and i told only this....issss PERFECT the battery and the camera....! JustArchi you are the King of S3
[Galaxy S III Android Development] habylab:
Hi there,

Quite hard to get this from a mobile device. A link in the OP to the download XDA link would be great. I can't connect to download either, always unsuccessful on my device. Is there a mirror, do you allow mirrors at all?

Thank you

Edit: just connected. I know you include a link in the thread posts of changelogs now, I see that! :)

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] vldesco:
[MENTION=5161352]JustArchi[/MENTION], updated to v.1.1 today and was using a lot in the morning, I put the phone to charge and continue using it (as usually I do), but now it is very hot, CoolTool reported upto 47°c (116 °F), the processor must be over 50°C. This didn't happen with V1.0 (nor kernel6 what I am using since weekend)

Using zzmoove, and in CPU info (that printed over screen) I see that cores 1,2 and 3 goes to idle.

I didn't change anything in the ROM Settings => Perfomance screen

What can I see to avoid this?
[Galaxy S III Android Development] JustArchi:
Probably connected with new experimental functions. Could you tell me what exactly happens? Didn't face this issue.
[Galaxy S III Android Development] Moster2:
Vibration settings cannot work since this kernel does not provide functions to do that. Does not have anything to do with todays update
[Galaxy S III Android Development] vldesco:
First, I am in AD 2.4.6, (back from 2.4.7 experimental with dirty flash), choose rom stock kernel. then flash ArchiKernel v.1.0...this morning flashed V1.1.

My usual phone usage is : read some newspaper (from Chrome), Twitter and facebook, as I didn't charge it overnight, It was below 40% battery when arrived to my work, and put to charge...received some phone calls, some whatsapp, follow world cup from twitter (I can't use my padTV while charging), and I feel the phone very hot, feel my fingertips burning, when touch the screen and back of phone too.

Left the phone (when sent my previous message), and now it is 35°c

Let me know if I must sent you some log it happen again.
[Galaxy S III Android Development] JustArchi:
CoolTool would show you frequencies, hence it's included by default in my AD ROM.

Move to "performance" options and check what's going on in terms of CPU.
[Galaxy S III Android Development] Sargos76:
full wipe(do a backup first) and then flash the AD 3.0, be careful with dirty flashing you may soft brick your phone.
[Galaxy S III Android Development] Maddinuser:
Thanks, but no wipe is required.

I got the solution in the arter thread:

"flash ArchiDroid with bare bones preset

boot up

ensure that stock kernel is present under "Kernel Version"

reboot recovery and install ArchiDroid normally then with no wipes

then flash your desired kernel"
[Galaxy S III Android Development] nightwing90:
At least just wait for stable build of rom based on 5.0. Then ask about kernel :eek:
[Galaxy S III Android Development] abhibnl:
When the right time, along with a properly working build will come, we shall see a AK kernel for lollipop. Atleast wait for a beta build first.

Sent from Galaxy S3 Powered by Nameless KK + AK
[Galaxy S III Android Development] BLooD_LorD:
Hello. Anyone tryed this kernel on latest PA rom?

Or maybe someone could tell wich version should i install?

i'm using PA 4.6 BETA 5
[Galaxy S III Android Development] ste22032:
Never tryed on PA, only on ArchiDroid, but I'm sure you will be satisfied using this amazing kernel as well. Be careful to flash the correct version for your ROM, that is the AOSP one :).
[Galaxy S III Android Development] BLooD_LorD:
yep, i got it, thanks! :) But what version of AOSP version should i use? R4P0 or regular one? ;)
[Galaxy S III Android Development] ste22032:
AOSP, regular one ;).
[Galaxy S III Android Development] BLooD_LorD:
I've installed this kernel on PA 4.6 Beta 5. I've choose AOSP regular one version. It works perfect, no errors, or fc. Sound quality is excellent. Battery life improved.

So if anyone would like to try it on PA, i definitely recommend it!:p
[Galaxy S III Android Development] you_man:
Hi guys. I can not install the AK after Boeffla, phone goes into a cyclic reboot.

The instructions Archi writes that need to first establish the stock kernel.

Give please stock kernel.

p.s. I use ArchiDroid 2.5.2
[Galaxy S III Android Development] Buckycasuals:
You need to reflash the entire rom before you can flash ArchiKernel. That way you will have stock kernel pre-installed.
[Galaxy S III Android Development] you_man:
There is no possibility to do it. Need separately stock kernel to install cwm.
[Galaxy S III Android Development] Buckycasuals:
Closed chapter :p
[Galaxy S III Android Development] you_man:
We learn from [MENTION=5161352]JustArchi[/MENTION], [MENTION=4604352]Moster2[/MENTION]
[Galaxy S III Android Development] JustArchi:
ArchiKernel V1.6

Download, changelog, and cookies

Have fun, and remember to flash R4P0 on CM12 (Alpha).
[Galaxy S III Android Development] abhibnl:
Flashed v1.6 on the top of 1.5.4 r4p0, restarted the phone and it showed me the initial setup screen like a fresh installation of rom. Well that was weird. Now everytime i reboot my phone, it shows process.media is forced close. Can u guide me what kind of log should i provide to help solve this bug since it happens aftr a reboot. Reveted back to v1.5.4 but process.android.media has stopped still happens.

Sent from Galaxy S3 Powered by Nameless KK + AK
[Galaxy S III Android Development] Darell3:
Has anyone tested this on the new ALPHA3 build of CM12?
[Galaxy S III Android Development] cangcan:
i flashed AK 1.6 Samsung on newly full wiped clean install AD1.7.18 just now and it started to lag and super slow right from the boot animation screen until it booted up..already tweak the kernel using stweak but still lags..something is wrong..gonna try to get a logcat if possible..so sad i didnt get the chance to feel L1/L2 cache optimization super fast speed yet..:(
[Galaxy S III Android Development] dmukhin:
Flashed 1.6 on stock 4.3 with 1.5.4 and phone starts to lag as hell and get very hot. Hardly get reboot it to recovery and flash 1.5.4 back
[Galaxy S III Android Development] marenp:
Same thing happened for me also on NeatROM 4.3 and on AD 1.7.18.... need to do clean flash with stock kernel....
[Galaxy S III Android Development] JustArchi:
Does flashing AK on top of stock kernel fix this issue?

Nobody experienced anything similar on AOSP ROMs, and there's no logical way that sammy ROM could cause problems. There were no sammy-specific commits since a long time.
[Galaxy S III Android Development] EP21:
So you flashed 1.6 on 1.5.4, unexpected behavior is probable.
[Galaxy S III Android Development] susbiction:
me to after Flashed 1.6 on stock 4.3 The phone starts to lag as hell and get very hot. Hardly get reboot it to recovery and flash 1.5.4 back