yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Mostafa Wael:
Lol you were the first kernel to support N7100 ports and you had your own ROM "Besonderes" as well as you are the one who fixed the auto-rotation problems and you now drop support :D

Anyways these N7100 ports are not that stable. RAM managements wasn't ideal at all. From QS to ArchiPort based ROMs it was never perfect.

Shame Samsung you dropped a great warrior in the nowadays mid-range phones. This phone was the king in a while ago :/

i will be waiting for the next big exclusive Bomb :)
[Galaxy S III Android Development] arter97:
sssssssssssssshhhhhhhhhhhhhh...........................
[Galaxy S III Android Development] arter97:
Because something BIGger is coming :)
[Galaxy S III Android Development] barani kumar:
finally.... sammy boy give us .........wat we want...

will wait "something bigger" :cool:
[Galaxy S III Android Development] HaarisTheBoss:
Is there an eta? Waiting for it impatiently ?
[Galaxy S III Android Development] iceman0826:
hehe i'm sorry at the same time (i realized my reply was kinda of cruel), it's just that i get angry when i see these kind of posts :D, the least we could do as a user (us) is to provide you with credible information as much as possible i.e. Kernel instabilities, bugs and things out of the ordinary of course with catlogs, kernel logs and other logs hehe.. :good:

i had a good guess of your upcoming surprise hehe..=p and i can't wait for the possibilities not only for the kernel hehe..=p i think we could finally have an official...............=p
[Galaxy S III Android Development] cangcan:
cant wait for it!! i wish i have 9gag@memes image gif like malachow has to express this feeling.. :D

btw [MENTION=4898097]arter97[/MENTION] i always see ur name in temasek twitter and it seems that you are in a good term with his HLTE rom..i hope that you can create the best kernel for temasek rom on s3 too..btw its not necessarily to be done, as we cant request anything..hopefully this upcoming version will gain more stability and will be more battery friendlier if the source from kitkat korean s3 taken.. :D:thumbup::thumbup:

p/s: i wish i know how to program or become a developer..i wish i can contribute some help too..but sadly all i know is just to use and to complain..sigh..
[Galaxy S III Android Development] GrayJack:
arter97

Taking into account Philz Recovery project has been stopped - are you going to continue the development based on some other recovery (TWRP for instance)?

And if no - possibly it could be good to update recovery to 6.57.9 sources?
[Galaxy S III Android Development] T0nyCr:
Somebody could help with porting of rom kit-kat 4.4.4 from S3 korean version [SHV-E210S] to our S3 GT-I9300... Could be on kernel development?
[Galaxy S III Android Development] regaber:
Respect to mikaillevist, but I think, with the experience of ArchiPort, the talented devs here will work on a port in a professional way and release a working beta when it is acceptable.... no need to push anyone :good:
[Galaxy S III Android Development] Mostafa Wael:
Well it will not be anytime before this nasty "deadlock" that happens when using any of the previously mentioned CPU governors is fixed. I just can't stand it. It lets my phone reboot in the middle of the call :laugh:

I am using stock pegasusq 100--1600 MHz and it is Okay for me until the new version. Or the new BIG THING! ;)

Just wanted to mention that so people don't wait for long and expect anything soon...

Cheers :D
[Galaxy S III Android Development] arter97:
back-to-n00t project now live!

Touchwiz Android 4.4.4 for Galaxy S3 3G

http://xdaforums.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
[Galaxy S III Android Development] Thecrazyskull:
Is this rom compatible with your (AMAZING) kernel?

EDIT: Just read OP its not compatible :( are you planning to support your rom?
[Galaxy S III Android Development] Mostafa Wael:
that is what i call a BIG DEAL :good:

This really deserves waiting :)

hope the next version of your kernel supports your "ArterPort" :cool:
[Galaxy S III Android Development] itizar1:
is there any possibility to add FIOPS scheduler?
[Galaxy S III Android Development] arter97:
Some Korean user also reported the deadlock is reproducible with pegasusq :(
[Galaxy S III Android Development] arter97:
Nope. That requires block backport from Linux 3.3+ which reduces the overall stability of the kernel.
[Galaxy S III Android Development] Mostafa Wael:
Well it is a good and a bad news in the same time...

Good news is: deadlock is not related to interactive/intelliactive governors.

Bad news is: it is getting more complicated.

Now i think you have only one choice. Trial and error..

Where you have to plot the differences between version 2.2 and 3.1.1, then start with 2.2 and apply a commit once a time and then test... Of course you have to start with the most suspicious commit...

I hope i could help you.

Maybe testing (as long as you guarantee me that my phone won't explode or commit a suicide xD)

Wish you the best..

And i did my job spreading the "back-to-n00t project" ;)

---------- Post added at 12:46 PM ---------- Previous post was at 12:13 PM ----------

Congratulations [MENTION=4898097]arter97[/MENTION]
[Galaxy S III Android Development] kotobodj:
i'm flash kernel on my SHV-E210L , Blekota v7 lite . But no network , i'm lost imei . how i can fix ? thanks
[Galaxy S III Android Development] Rusl1TA:
Any advice to improve the battery life? I tried all governors, undervolt and setting but it still "eats" my battery in half day
[Galaxy S III Android Development] RReeD:
The link doesn't work,can u bring another one?
[Galaxy S III Android Development] Sachiru:
Re-calibrate your battery.
[Galaxy S III Android Development] arter97:
arter97.com is down due to overwhelming response of the back-to-n00t project.

I've asked the host to bring the server back online.

Meanwhile, sorry but you cannot use arter97.com. Please wait.
[Galaxy S III Android Development] GrayJack:
Dear arter97

For all last time I have used Devil kernel. I think AndreiLux is one of the best kernel developers for Sammy devices, so as Devil kernel was a good continuation of Perseus kernel - it was very well. I have no problem, but because DerTeufel1980 took a long pause in his development I decided to move to arter97 kernel.

I have installed it and used for a several days - and unfortunately there is a problem so I have to revert back. Let me explain.

I have used Devil3.4_0.1.4 with devilq governor, cfq scheduler and 50% zRAM (aggressiveness 100%). System partition is ext4, data and cache are f2fs.

So I have used Common SGS3 kernel Cleanup v.3 script (actually it was not necessary as Devil kernel shouldn't leave any traces - but just in case) and flashed both arter97 recovery and kernel.

When I start using arter97 the settings were default at first. But there were a big lags and hangs during the work - both with apps and system at all (including famous "system not responding"). The 100% way to hang the system was to start updating in Google Market. I have tried pegasusq, pegasysqplus, interactive governors, changing zRAM settings and disabling it at all, overclocking to 1600 MHz - it didn't help. BTW "system" took in memory about 60 Mb.

So I have return back to Devil kernel with wiping all traces from arter97. It is smooth and quick as it was before. I have tried to change governors from devilq to pegasusq and interactive - it is OK also: no hangs and no lags. I have looked into memory and found very little difference in comparison with the same situation with arter97 kernel.

Could you please explain the situation? I think your kernel is good and up-to-date, so possibly I have some traces or incorrect settings from Devil kernel I have to fix before changing kernel?

Possibly someone else in this forum has similar problem and know how to fix it?
[Galaxy S III Android Development] Lukijs:
Can anyone at least pm me the latest kernel?
[Galaxy S III Android Development] RReeD:
+1
[Galaxy S III Android Development] pricey2009:
Turn off intelli plug then you have no more freezes after phonecall. Works for me.
[Galaxy S III Android Development] Mostafa Wael:
can anyone tell me if arter97-kernel-v2.2 has "interactive" governor along with intelliplug?

if yes then this proves that the deadlock does relate to changes in "no-hotplug" governors, i mean like this commit:

that is just my opinion

maybe if arter managed to test a kernel build with those commits reverted then we will have a clear answer

i wish i could do... :/
[Galaxy S III Android Development] francescozanghetta:
+1

with artes97 recovery?

Many thanks
[Galaxy S III Android Development] GrayJack:
Just for those who tried arter97 kernel and want to revert back with cleaning traces.

I cannot remember who was the original developer of this script - anyway I have v.3, so I named this one v.4. All credits to initial developer of course.

Everything is same, but strings added:

ui_print("");
ui_print("--------------------------------------");
ui_print("- arter97 Kernel Clear Settings -");
ui_print("--------------------------------------");
ui_print("");

delete_recursive("/data/media/0/.arter97");
delete_recursive("/data/.arter97");
delete("/system/lib/egl/libGLESv2_mali.so");
delete("/system/lib/egl/libGLESv1_CM_mali.so");
delete("/system/lib/egl/libEGL_mali.so");
delete("/system/lib/libUMP.so");
delete("/system/lib/libMali.so");
delete("/system/bin/hostapd");
delete("/system/app/aTweaks.apk");
delete("/system/app/aSwitch.apk");
delete("/system/addon.d/97-kernel.sh");

Sure this script will clean other supported kernel traces also.
[Galaxy S III Android Development] NightSky256:
Can someone upload the kernel on mega or other?
[Galaxy S III Android Development] arter97:
arter97.com service is now not enough.

Due to overwhelming response and downloads with back-to-n00t, arter97 kernel, AOSP for ks01lte,

I have no choice left but to purchase a VPS server.

Your donation would help me a lot..

Thanks for your support :)
[Galaxy S III Android Development] Walkman8196:
Kernel/recovery/multiboot on mega in one .zip
[Galaxy S III Android Development] arter97:
Please remove it.

Read the OP before you do those kind of stuffs.
[Galaxy S III Android Development] NightSky256:
Removed. I don't want to argue
[Galaxy S III Android Development] arter97:
Thanks.

And it's not just me, it's also on the XDA forum rule.
[Galaxy S III Android Development] RReeD:
So we will not get a chance to give this kernel a try?
[Galaxy S III Android Development] arter97:
Seems like the server is now working
[Galaxy S III Android Development] NightSky256:
Now that i gave a try at this,

As any other "Mali" kernel there are ugly glitches on the image scroll component. We can notice it pe on Amazon app while scrolling through products images, or even in google search in some cases.

Apart of this, it's an extremely optimized kernel. Battery last a life compared to cm stock, I'm over a day with moderate use and a standard sized RAV battery.

The "interactive" governor works really good.

I'm in 200-1704 clock range. No hangs no reboots and no wakelocks.

I couldn't find any audio optimizations but I should search more... Anyway I didn't use them because they always have recording volume issues that breaks voice control usability.

It's a good work arter97. Keep going on.

Now that I've seen your work quality, You can count on my little help for your server :) let me understand how to...
[Galaxy S III Android Development] khanmein:
[MENTION=4898097]arter97[/MENTION] will u release CWM 6.0.5.1? thanks. bro ur recovery unable to detect/mount ext sd card at all
[Galaxy S III Android Development] jit1108:
Resurrection Remix RoM

Can I use this kernel for Resurrection Remix RoM , I am currently using this RoM [i9300] and want to test this kernel, please advice.
[Galaxy S III Android Development] boleguc:
Can I flash this kernel on shv e210s stock 4.4.4?
[Galaxy S III Android Development] MD500:
Which kernel? (No hangs no reboots and no wakelocks OHH!!) if samsumg releases korean sources is possible that this port will be the most port that note2 port! (i think)

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] NightSky256:
I was talkin' about this CM kernel. Non the two port.

Cm works simply better. Is lighter and the main and most important result is that if you open an app (eg. Spotify) leave it in background. Open a second app (eg. Strava or Runtastic). And in the meanwhile you open a third app (eg. OpenCamera to take a picture) the first app won't be killed by lmk.

1.0 gigs of ram is very few for a real usage of a tw ROM... And for real I talk about what I said... 3 "heavy" apps opened.

Maybe they will make miracles BTW :)

But for the moment the best choice for me is CM and Arter97 kernel.
[Galaxy S III Android Development] arter97:
I'm experimenting around a new server host.

It's located here in Korea, so I'd like to see everyone else's connection speed to here.

Please download any files from here:

http://esnw.kr:2029/browse/s3/ROM/

And comment down how are your speeds(in kB/s or MB/s).

Thanks :)
[Galaxy S III Android Development] yogareog:
Service error....
[Galaxy S III Android Development] ficko_98:
http://puu.sh/bSwNG/bb89841f3f.png slow :( usually my speed is around 700kb/s
[Galaxy S III Android Development] RReeD:
The latest version (i didn't try another one) shut off my phone after an incoming or outgoing call.

My galaxy is an international version,

Im using paranoinandroid rom version 4.6 Beta2

(Android 4.4.4)
[Galaxy S III Android Development] ASHLEY117:
disable intelli-plug in aTweaks. its solved this issue for me.
[Galaxy S III Android Development] Mostafa Wael:
use pegasusq or pegasusq+ or yankasusq or zzmoove for the moment until issue is fixed...
[Galaxy S III Android Development] ramansehra:
Deleted

---------- Post added at 05:31 PM ---------- Previous post was at 05:27 PM ----------

Agree bro..... Happened with me too.

And what about battery life?

Do you experience fast battery drain with arter kernel?
[Galaxy S III Android Development] Mostafa Wael:
Well with this kernel, archikernel & boeffla kernel i get ~3 hours 45 minutes.

But arter is the snappiest IMO with intelliactive and intelliplug, but sadly the cause the deadlock after call :(

So now i am on boeffla kernel until this issue is fixed.. ;)

Just because i formatted the phone yesterday and the file is deleted accidentally :o

ArchiDroid got boeffla kernel in the installer.

Tonight i will be installing (back-to-n00t) V2

Hope this kernel supports it ;)

Will test battery life with it tonight

P.S. my battery is 25 months old battery so if you are talking about a new battery then maybe you can get around 5 hours+ Screen-On-Time :)

P.S.: you can already crack the 4 hours screen on time with using the stock 1.4 GHz. I am having this awesome battery life while overclocking to 1.6 GHz :)
[Galaxy S III Android Development] cangcan:
ive read back to noot thread just now..it seems that even arter kernel does not support the rom yet..correct me if im wrong..
[Galaxy S III Android Development] Mostafa Wael:
Yup

But it will certainly support it soon.
[Galaxy S III Android Development] ramansehra:
I have tested this on two different ROMs, my phone can't go in deep sleep mode.

Even disabled the manual mode in screen settings.
[Galaxy S III Android Development] Mostafa Wael:
Okay, mind that after boot it takes up to maximum 5 minutes for your phone to "settle down"

grab a BBS Log to look at the "partial wakelocks" and talk

If you found "RILJ" or "MediaScanner Service" topping your BBS, then give it some more time. If it is related to google apps "wake.com.google.blablabla" or "...gms..." then try to change Gapps.

also make sure you are using the 3.1.1 version NOT 3.1

Go Ahead! :)
[Galaxy S III Android Development] huzzam:
won't boot — incompatible with encrypted device???

Hi--

I've tried installing Arter kernel versions 2.2 and 3.1.1 on top of a nightly CyanogenMod KitKat (cm-11-20140928-NIGHTLY-i9300, which was running stably). In both cases (2.2 & 3.1.1) I can not boot up afterwards. It gets stuck at the initial boot animation (which continues to cycle).

I have an encrypted device, and previously after ~30 seconds of boot animation, I'm asked for my password, then the boot animation would return. In this case, I'm never even being asked for my password.

Is the kernel incompatible with encrypted devices, or have I done something else wrong?

Thanks for your work!

Peter in Istanbul
[Galaxy S III Android Development] Mostafa Wael:
Well i have no ideas about encrypted devices sorrily, could you try to decrypt iy in any way before flashing the kernel? And 3.1.1 is stable enough, unless you use interactive/intelliactive/ondemand/smartassv2 with intelliplug, you will face the deadlock after the call. If you use 3.1.1, then make sure you are on pegasusq, zzmoove, pegasusq+, yankasusq.
[Galaxy S III Android Development] arter97:
Encryption is not supported because of hybrid support of f2fs.

I'm planning to look further into this later.
[Galaxy S III Android Development] Mostafa Wael:
Well i remember that psndna88 had that problem, it was because of /system and /data being on different FileSystems. The workaround for that of course was formatting both partitions to the same FileSystem "/system and /data must be both on f2fs or both on ext4"

However he managed to fix it. You may get in contact with each other.

Btw, did you manage to fix the deadlock? Or was the back-to-n00t project busying you a lot? No ETA of course i am just asking about progress :D

Keep it up :)

i flashed your back-to-n00t v2 and it was amazing, but i had RAM Management problems so i went back to AOSP. Looks like i hate Touchwiz so much :laugh: No way all must agree, even with not-working H/W composer, AOSP is snappier and lighter :)

Btw, AD 3.0.0 + arter97 kernel 3.1.1 = best combo for performance/battery balance. Using Zzmoove-Yank Battery and OC up to 1.6 GHz and my phone is still bloody snappy here. :D :D It is too quick for a S3 :laugh: Battery life benchmarks was: 26 minutes 41 seconds SOT within 10% battery drain. Impressive!!! By calculations it shows a 4 hours 7.5 minutes screen-on-time on a 26-months-old battery! Well Done :)
[Galaxy S III Android Development] arter97:
I think I already can fix encryption(still with hybrid f2fs support)without anyone's help.. lol

I also don't use Touchwiz. Back-to-n00t is just for people digging stock ROM.

And btw, what do you mean by "a working H/W composer"?
[Galaxy S III Android Development] george stamatos:
I think he's talking about Nameless rom, who has working H/W composer
[Galaxy S III Android Development] Mostafa Wael:
Exactly

One of the most famous problems in AOSP ROMs for the galaxy S3 is the broken H/W composer (H/W stands for hardware), which means that 2D acceleration is handled by the CPU, not the GPU as in stock ROMs. This results in little lags (like when you pull the notification bar) and of course affects the battery life. That's why when you underclock the GPU steps in CM11 for instance, it will do nothing, but on nameless ROM, which has this H/W composer working, if you underclocked/overclocked the GPU, you will feel that the UI is getting more laggy/smoother.

Why is this happening? I guess you may have a right doubt in this question as being a kernel developer, it is all because of Samsung! They almost never release proper sources for their exynos crap, at least on the S3 (don't know about the newer devices).

So you think now "why Nameless ROM is the only ROM having this fixed??!"

Nameless ROM is based on hardkernel/Odroid. To be honest i do not know where did they came up with this, but in short, they use updated r4p0 mali drivers which was released and became open source from a while. Merging this r4p0 mali drivers fixed the H/W composer.

For more explanation on how they came up with the r4p0 drivers:

As in the quote i thought samsung pushed them open-source accidentally :laugh:

Hope i helped you :)
[Galaxy S III Android Development] arter97:
I knew they were using Hardkernel's software(and I actually own an ODROID U3).

But since its DVFS is somewhat different and "maybe" not mobile-optimized, I'm not using it.

And are you sure about 2D being handled by the CPU for rest of the AOSPs?
[Galaxy S III Android Development] Mostafa Wael:
Well that is what i read every now and then in the threads. I read this in ArchiKernel thread, if i remember well.

he said: "finally we can let the CPU breathe"

So i think this confirms it.
[Galaxy S III Android Development] jit1108:
Guide How to install 2nd ROM

I am already on arter97 3.11 also installed arter97-multi-boot and latest arter97 -Philz_touch_recovery.

Please elaborate and guide how to install 2nd ROM.

In this throughout thread no one has guided how to install 2nd ROM on this kernel (dual_boot).
[Galaxy S III Android Development] Moster2:
He misunderstood that. Currently it goes through opengl all the time. A working hw composer can help to offload and directly draw 2d layers.
[Galaxy S III Android Development] Mostafa Wael:
ohh thanks Moster :D

i am still a beginner ;)

is there anything else wrong?

---------- Post added at 02:35 PM ---------- Previous post was at 02:24 PM ----------

here you go:

-1- Boot into recovery and flash latest arter97_Philz_recovery.zip (optional, but recommended to be sure everything works well)

-2- reboot recovery to be on the arter97-modified philz recovery

3- flash the 3.1.1 kernel

-4- reboot system

-5- setup your phone's settings in aTweaks

-6- reboot recovery

-7- flash the

LATEST

multiboot.zip (i can't remember the version now, but it is the latest! :D )

-8- then after you flash the multiboot.zip, flash the ROM file;

if it is AOSP then flash the ROM.zip followed by the Gapps.zip and then followed by anything-you-want-to-be-in-2nd-ROM.zip

if it is an AROMA installer equipped ROM, no worries. Just flash them as if you are flashing them normally...

-9- that's it! Voila! Enjoy your phone dual-booting.

to switch from 1st ROM to 2nd ROM and vice versa, open aSwitch and select "Reboot in 1st/2nd ROM"

If you are facing a bootloop in the 2nd ROM for any reason, just reflash the arter97-3.1.1 kernel.zip and you will be booting back to your 1st ROM.

Hope i helped you enough :)
[Galaxy S III Android Development] Moster2:
Everything is fine ;)
[Galaxy S III Android Development] arter97:
Yeah I thought using the CPU for 2D is.. erm.. no.

Anyways, thanks for the info.

I'll probably test those out soon.
[Galaxy S III Android Development] arter97:
For those who experienced shutdowns during phone calls, what ROM were you using then?
[Galaxy S III Android Development] dash87:
I tested on Carbon, liquid, and temasek. All had the issue with reboot after voice call. Any ideas when a fix is coming?

Sent from my SHV-E210S
[Galaxy S III Android Development] arter97:
Root cause is still unknown.
[Galaxy S III Android Development] arter97:
Any Touchwiz users having the same problem?
[Galaxy S III Android Development] hansonchen:
Working fine with archidroid 1.7.18 with f2fs. No shutdowns or strange issue, just the dead sleep but a tweak on the cpu solved it.

[MENTION=4898097]arter97[/MENTION], can the under volting numbers be simplified instead of 1400000uV, etc.. a bit confusing and include steps like -50, -100, etc. (Boeffla)?
[Galaxy S III Android Development] arter97:
Yeah maybe I should do that.
[Galaxy S III Android Development] cba1986:
Temasek's
[Galaxy S III Android Development] Mostafa Wael:
ArchiDroid 3.0.0/2.5.3

And Carbon ROM

It happens while using Interactive/intelliactive/ondemand governor along with intelliplug. PegasusQ and PegasusQ+ are bulletproof for me. Zzmoove is also perfect.

:)

I will try to test AD 1.7.18 with this kernel and tell you.

Currently i am testing battery life.

Oh and zRAM is a major problem here. I am running low in RAM while using this kernel... :/