yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] arter97:
It's normal. /system is being replaced with /data/arter97_secondrom/system while multi-boot.zip is in effect.
[Galaxy S III Android Development] _Negan_:
Hi arter, where can I read please changelog of 2.0? Thanks
[Galaxy S III Android Development] dheeraj (dhlalit11):
This version is the initial release for public so everything written is a changelog
[Galaxy S III Android Development] arter97:
+1
[Galaxy S III Android Development] arter97:
The initial version's changelog = features.

The version name 2.0 is only for Koreans to not get confused.
[Galaxy S III Android Development] buick1356:
ok.but second rom cannot be installed.gives error.please clearly explain how to install second rom.

thanks
[Galaxy S III Android Development] arter97:
1. Enter recovery

2. Flash multi-boot.zip

3. Flash your ROM zip

Please explain your error.
[Galaxy S III Android Development] buick1356:
error installing ......... .(name of zip file with path).I use multiboot 1.2 with your kernel.also I wasnot able 5o create multiboot in 4.3 rom.previously I was able to multiboot in 4.1.2 very easily.:(
[Galaxy S III Android Development] arter97:
What recovery are you using?
[Galaxy S III Android Development] buick1356:
twrp 2.7, cwm 6.0.2.7 , philz 6.00.8 , devil 4.3
[Galaxy S III Android Development] truereason7:
Very Great

very good !:D:D:D

this kernel app have UMS MOD??:confused:
[Galaxy S III Android Development] dheeraj (dhlalit11):
+1 for UMS mode, really need it if we are working with old XP Pc, if you want then you can take source of boeffla kernel

And dont you think multi-boot.zip should contain some lines to link the /secondrom/data partition to /data

Beacuse if any package is flashing to data partition then it will not be flashed to 2nd rom
[Galaxy S III Android Development] arter97:
Try using the latest CWM
[Galaxy S III Android Development] arter97:
What does it do?
[Galaxy S III Android Development] arter97:
Ah, right! I should link some more to /data. Thanks for the idea.
[Galaxy S III Android Development] noypitoits:
for korean variants

working flawlessly on my shv e210k running 4.3 by davidsv with proxyme. on my case latest twrp & philtouch justarchi doesnt work. so i tried the latest cwm touch.& it works as expected, including multiboot. & flashes almost cm11 roms with no problem. the only problem I'm facing is almost cm11 roms cannot connect to wifi or drop my signal from full to out of coverage. kinda off topic but can I ask sir [MENTION=4898097]arter97[/MENTION] what cm11 rom can you suggest for our e210k? thanks mate! & sorry for this.:fingers-crossed:
[Galaxy S III Android Development] SweetCupcake:
Where can i install the 2 rom? In the recovery have not a slot for 2 rom?!

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] arter97:
Our Korean forum has it.

Go check achonapp.com or develoid.com
[Galaxy S III Android Development] arter97:
Read the OP
[Galaxy S III Android Development] Mostafa Wael:
+1

and i found a strange thing in the /system/app

all the APKs are placed in a folder of the same name.

Example: if you are looking for Apollo app, you will find it in /system/app/

Apollo

/Apollo.apk instead of /system/app/Apollo.apk

all apps are done the same except aTweaks and aSwitch

aSwitch is working fine but aTweaks is not working, can not pass the loading... popup

and Heads up!!! External storage is broken with current 4.0-beta1 please [MENTION=4898097]arter97[/MENTION] fix it in next beta :) :angel:

---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------

Samsung has divided the S3 phones into ASV Levels from 1 to 7

1 is of lowest quality (needs higher voltage to be applied at each step after the 900 MHz and cannot endure undervolting or overclocking)

7 is of best quality (needs lower voltage to be applied at each step after 900 MHz and can endure serious undervolting and overclocking)

Mine is 6/7 so i can endure only overclocking to 1704 MHz and undervloting to -75 mv on each step

My friend has a 7/7 device and can endure Overclocking up to 1.8 GHz and on Devil kernel he was running on even 1.9 GHz with no problems

Another friend of mine has a 2/7 device and can barely endure overclocking to 1.6 GHz and undervolting is not endurable on the phone when heavy using it

How do you know your ASV Level? well i knew it from Boeffla-Config App when i had Boeffla kernel installed.

that is why he included 1.8 GHz
[Galaxy S III Android Development] Wyneg:
Dump kernel logs

hi!

How i can dump kernel logs? While I used 4.0 beta I had reboots and cell phone even turn off by itself. I want to help posting that logs.

Thanks!
[Galaxy S III Android Development] CyberianIce:
Bug Report

I would like to report an bug in this kernel or its aTweaks:

I got often negative mode enabled by itself (after finishing phone call, or after closing SMS or other apps). I would normally submit logcat but I can predict when this will occur or why. I thing it's up to mDNIe hijack.

EDIT: I am using CM11 M12 but with CM11 M11 I got same problem with this kernel only.
[Galaxy S III Android Development] arter97:
Few devices out there "can" handle it. Not all.
[Galaxy S III Android Development] arter97:
I'll reimplement log dumper later.
[Galaxy S III Android Development] arter97:
Lollipop is not all that ready :(
[Galaxy S III Android Development] CyberianIce:
Is there any way to disable this feature somehow, as it is shown not just useless but also frustrating IMPO?
[Galaxy S III Android Development] Wyneg:
That is what I need, to report reboots and turn off of the device ;)
[Galaxy S III Android Development] b0mb:
What tool is best for configuring this kernel?
[Galaxy S III Android Development] Lukijs:
The one that comes with kernel
[Galaxy S III Android Development] d1rekt0r:
SD Card not recognized on android 5 Nameless rom
[Galaxy S III Android Development] rahulbalmuri:
Is this kernel compatible with Dirty unicorns 8.0 (4.4.4 Kitkat).. First post says so.. but somewhere in middle someone posted it will be tested on Dirty unicorns.. i do not want to mess up my ROM.. thts the reason I am asking this question.
[Galaxy S III Android Development] Mostafa Wael:
DU is based on omnirom right ?

i think it is 99.9% compatible
[Galaxy S III Android Development] rahulbalmuri:
Yes its based on OMNI have been using.. Boeffla OMNI version.. and its stable.. So you say I can give a try to arter kernel?
[Galaxy S III Android Development] Almin94:
Disable zram

Hello

How to disable zram on Samsung based rom?
[Galaxy S III Android Development] exwan:
Arter has remove zram in version 4.0
[Galaxy S III Android Development] senaferdy79:
don't think, just do it ;)
[Galaxy S III Android Development] arter97:
ROW I/O scheduler will be removed as of version 4.0-beta2.

This was also the culprit of overall instability of the device.
[Galaxy S III Android Development] flither:
Just for correcting - there are 12 ASV levels for S3 - from 0 to 11, mine is 8 f.e. :good:
[Galaxy S III Android Development] arter97:
4.0-beta2 is now live!

4.0-beta2

Major speed improvements via new ARM instructions set

interactive CPU governor re-based to android-3.4

(Fixes frequency stuck issue)

ZZmoove v1.0-beta2

ROW I/O scheduler removed

Misc block commits reverted

(Improves overall stability)

f2fs reworked from ground-up

(Stability, performance improvements)

Automatic kernel panic log dumper now stores log on /sdcard/arter97

RTL8187 support added (integrated)

SHV-E210L radio issues fixed

External storage support for Android 5.0 Lollipop enabled
[Galaxy S III Android Development] arter97:
For those who want to help me improve stability of this kernel,

please check /sdcard/arter97 periodically and see if there's any log.

If there is, please upload here or send it to me : qkrwngud825@gmail.com
[Galaxy S III Android Development] Mostafa Wael:
thanks bro

never knew it

a phone with ASV 11 will be f*cking beast !!!!

---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------

thanks great dev :good:

will certainly try it out right NOW!!!
[Galaxy S III Android Development] arter97:
Aaand.. beta3 will have that vnswap switch.. :)

Didn't have time to do with beta2.. forgive me xD
[Galaxy S III Android Development] exwan:
Betae is not now right? Im just about to flash beta2.
[Galaxy S III Android Development] Mostafa Wael:
no problem mate

also is the problem with aTweaks in lollipop fixed?
[Galaxy S III Android Development] w7rw7r:
I can install this , my rom is cm11 4.4.4
[Galaxy S III Android Development] Almin94:
aTweaks now work?
[Galaxy S III Android Development] exwan:
Arter could you add reading ASV level in beta3?
[Galaxy S III Android Development] fdkgenie:
From changelog of 4.0-beta1:

That means we can only use your 4.0 kernel on AOSP roms, not stock-based roms anymore?
[Galaxy S III Android Development] Mostafa Wael:
no he means ArchiPort and QS will not be supported anymore because of back-to-n00t ROM by arter97

so stock ported android 4.4.4 based ROMs will work supposedly
[Galaxy S III Android Development] Zwulf:
[MENTION=5044592]Almin94[/MENTION]

No, aTweaks sadly doesn't work yet. But you can easily tune it with Kernel Tweaker.

https://play.google.com/store/apps/details?id=com.dsht.kerneltweaker&hl=en

Tapagetalkt via Nameless 2.0 vom i9300
[Galaxy S III Android Development] fdkgenie:
And does it work on CM12 Alpha 1 or Nameless 2.0-Alpha with my Korean S3 (E210S)?
[Galaxy S III Android Development] Almin94:
Kernel Tweaker won't allow me to change Display settings to Standard colors which I prefer, also cpu voltage and much other stuff.
[Galaxy S III Android Development] Arifcatalyst:
Exfat not supported yet ?
[Galaxy S III Android Development] rascal0pl:
is it compatible with nameless 5.0 alpha (beta1 was useless with this rom, everything FCs) ?

EDIT:

Everything seems to be ok. Expect not launching atweaks
[Galaxy S III Android Development] Mostafa Wael:
well for me it is extra compatible :cowboy:

and with external storage working, everything is awesome except for the not-working mobile data which will be fixed in next ALPHA2
[Galaxy S III Android Development] Arifcatalyst:
Is exfat supported?

which format are you using.
[Galaxy S III Android Development] Mostafa Wael:
i am using vfat 16 GB

working :good:
[Galaxy S III Android Development] GrayJack:
Just curious why don't you use latest sources from Philz (6.59.0) for your recovery?

Some compatibility issues?
[Galaxy S III Android Development] Mostafa Wael:
anyone facing sudden reboot when screen goes off with latest 4.0-beta2 kernel ??
[Galaxy S III Android Development] Lukijs:
Working good for few last hours here on PA
[Galaxy S III Android Development] Mostafa Wael:
ohh sorry my bad i forgot to mention that the problem is in nameless 2.0 lollipop :D

Anyway, it is magically fixed by turning the WiFi on (don't know how??!!)
[Galaxy S III Android Development] rascal0pl:
Yes, after using it ~4 hours I must say that it is very unstable on nameless, my favourite apps are crashing (most of them while scrolling something). Reverted backup with stock "nameless" kernel.
[Galaxy S III Android Development] Mostafa Wael:
can you identify which mali drivers is

currently

used by nameless stock kernel?

for me there was an app causing this instability

now everything is good with arter97 kernel

don't know, may be our phones are very excited because of lollipop :p

and may be the FCs caused by the apps are due to their incompatibility with lollipop :confused:

Anyway, let's keep an eye on it and see what will happen tomorrow/next month ....

But seriously, lollipop deserves the work done by developer

my phone was never smooth and snappy as now

lollipop + arter97 kernel is the ultimate speed and smoothness for me
[Galaxy S III Android Development] itizar1:
[MENTION=4898097]arter97[/MENTION] version 4 beta 2 is really good except atweaks issue, also it can't mount my exfat-formatted microsd card

can you add exfat support for next beta (if problem is that)? i really need it
[Galaxy S III Android Development] arter97:
I cannot follow up with all the PhilZ releases.

I update recovery when I have time. This time, 6.59 seems minor.
[Galaxy S III Android Development] arter97:
ExFAT problem is the ROM thing.
[Galaxy S III Android Development] fcaronte:
For me exfat sd is work on beta 2....

[MENTION=4898097]arter97[/MENTION]

I have questions.... How to make 3 boot? I try this:

1- install second Rom

2- go to first Rom and rename the "arter97_secondrom" folder

3- make another second rom

But to swith from second to third I must manually rename folder....

There is Another way?

(yes usually not need more than 2 boot)

How much space we have for other Rom and how to see remain space?

Is the performance of various boot same or first boot is better?
[Galaxy S III Android Development] leonardoaraujo:
hello, good evening !!

I got this message:

mount: failed to mount / dev / block / mmcblk0p9 at / system: no such file or direc ...

install arter97 recovery

reboot recovery

all wipes format

install back-to n00t rom

install arter97 kernel

reboot to recovery

install arter multiboot

install nameless lolipop rom... get this mensage...
[Galaxy S III Android Development] Wyneg:
Hi all!

Dump log work automatically? I have folder .arter97 but I can't see any log file...

Thank you, [MENTION=4898097]arter97[/MENTION]
[Galaxy S III Android Development] exwan:
Only work if your phone auto reboot i think.
[Galaxy S III Android Development] Mika83AC:
[MENTION=4898097]arter97[/MENTION] do you think it's possible for you to change your kernel without enermous effort, so that we might be able to install the current lollipop test builds as second rom? As is understood, until now it can only be installed as first rom.
[Galaxy S III Android Development] Lukijs:
You didnt understand correctly everyone is booting it as second, read few pages back
[Galaxy S III Android Development] Mika83AC:
May you give me a link to the corresponding post? Mostafa Wael gave a detailed description about how to install lollipop once (!) as second rom, but i can't find anything about having lollipop as a continuous updatable second rom. And that's what I think everybody needs, because no one wants to perform a 20 minute procedure just to check out a new lollipop build. :)
[Galaxy S III Android Development] prabhjots:
I think it should be fixed in another release for nameless, I saw a gerrit edit that talked about doing away with "block based install" (which, I'm guessing, is causing the install as 2nd ROM to fail)
[Galaxy S III Android Development] Mika83AC:
Ah, okay, i'll try it with namless rom. Until now i always tried it with cm12 :) thx
[Galaxy S III Android Development] prabhjots:
No it doesn't work as of now with nameless too, they havent merged it yet, i think.
[Galaxy S III Android Development] Mika83AC:
yes, it seems not to be merged, right. tried some minutes ago with todays build, but cannot be installed ;)
[Galaxy S III Android Development] Mostafa Wael:
BTW Lollipop is hyper right now, i mean that it will get alot of updates so why should we install it as a 2nd ROM ??

i see that installing it as a 1st ROM is far much better than installing it as a 2nd ROM

and here is a direct link for How to install a lollipop ROM as 2nd ROM not as a primary ROM... if it is of any use for you now
[Galaxy S III Android Development] Mika83AC:
I'd like to have my 99% stable daily driver as first rom so that i can use it without any restrictions or limitations. Something i've just for testing or following development is for me definetely a second rom :)

Why do you think it's better as first rom? only because it will get stable in the next one or two month? ;)

that was what we discussed already. with this solution the second rom isn't updatable, and so its high effort to check new builds.
[Galaxy S III Android Development] prabhjots:
The reason I want to install lollipop as a 2nd ROM is that it is unstable. Is there any fallback method to select from the recovery as to which ROM to boot into, if for some reason lollipop doesn't work long enough to boot into the other rom from aSwitch? Can you please guide? Thanks!
[Galaxy S III Android Development] Mostafa Wael:
well in arter97 kernel 1st and 2nd ROM does not have anything different

didn't face any limitations to 2nd ROM

to decide whether install the ROM to be installed as 1st ROM or 2nd ROM, just see the update criteria

lollipop will enter the beta/nightly phase, which means more frequently update plan

while KitKat will be entering the stable phase, which means less and less update plan

so i installed Lollipop as 1st ROM and then KitKat ArchiDroid 3.0.0 as 2nd ROM

---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------

you mean bootloop of 2nd ROM and you want to return to 1st ROM urgently ?

reflash arter97 kernel and it will boot in 1st ROM as it resets aSwitch

---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------

Anyway, what i see in Nameless ROM thread is people having random reboots with arter97 kernel

so maybe [MENTION=4898097]arter97[/MENTION] can look into the issue??

and BTW i can't find the kernel log dump in /sdcard/arter97 "no such folder is listed in ES File Explorer" and what i have is /sdcard/

.arter97

"it is a hidden folder with no kernel log dumps"
[Galaxy S III Android Development] prabhjots:
No, I mean if we follow your suggestion, and install Lollipop as 1st ROM, and stable Archidroid as 2nd ROM. If 1st ROM starts bootlooping, how to get to 2nd ROM as a fallback?

Also, I was unable to access the sdcard- external and internal while I was running Lollipop as 2nd ROM. Not sure if the same would be the case if Archi's KK would be running as 2nd ROM..
[Galaxy S III Android Development] Mostafa Wael:
did you update to latest 4.0-beta2 ? this fixes the external storage issue on lollipop ROMs

and i got your request now.

Okay the other way relies on that you have a nandroid backup of your 2nd ROM so if you are having bootloop in 1st ROM, then restore your nandroid of the 2nd ROM.

yeah it is not a practical way but that's what it goes with in Alpha ROMs :rolleyes: :silly:
[Galaxy S III Android Development] Mika83AC:
That's something i can agree to ;) And good to know that there aren't limitations in the second rom, wasn't sure about this.
[Galaxy S III Android Development] exwan:
Suddenly my cpu clock ia lock on 1400. I have wipe system, cache, dalvik. Reflash kernel. Still the same.

I cant post log as i cant find any folder like you said.

Change to boefla kernel with system, cache, dalvik wiped. Still the same.
[Galaxy S III Android Development] Mostafa Wael:
after a boot it will trigger a "MediaScanner" wakelock that keeps your phone at max frequency for some time

just give it a maximum 5 minutes time and you will be fine

use BBS to track wakelocks or use Wakelock Detector
[Galaxy S III Android Development] exwan:
It aint media scanner if it is lock a maximun clock for 30 minutes.
[Galaxy S III Android Development] Mostafa Wael:
try to cleanly flash the ROM again

85% of errors are fixed with a clean install
[Galaxy S III Android Development] rascal0pl:
No, it is not a app problem, I'm sure (stock browser? even stock browser from lollipop ? :P)

Mali driver in nameless lollipop is R4P0 , so I think it explains everything. Arter kernel on nameless 4.4.4 (which is using R4P0 too) is unstable too.
[Galaxy S III Android Development] Mostafa Wael:
i think i got it

arter uses R3P2 in his kernel, so it replaces R4P0 in the ROM with R3P2_API_29, which obviously breaks some things

and maybe newest nameless lollipop has some commits relying on R4P0 more which causes FCs

will cleanly install latest nameless with stock nameless kernel to see the differences
[Galaxy S III Android Development] rascal0pl:
System is not that smooth like it is with arter kernel, but is is much much more stable and there is no FCs at all.
[Galaxy S III Android Development] Mostafa Wael:
+1

i had the latest version cleanly installed and restored my apps

system is stable but not as quick and snappy as with arter97 kenel

ohh and i tried to dirty flash the nameless update on top of the old nameless alpha1 and i saw that arter97 kernel is sticking after reboot, i.e. the stock nameless kernel was NOT flashed!! (strange isn't it? may be due to block installation method?) and mobile data did not work

after cleanly installing the ROM with the Gapps it is working like never before, i just miss the snappiness in arter97 kernel :( :angel:

hope arter97 pushes a quick fix/update .... :fingers-crossed:

most probably your problem was kernel-sided i confirm here
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
I am getting random reboot in nameless ROM 2.0,any solution for this?
[Galaxy S III Android Development] supreethms:
No.

Wait for the developers to complete with whatever they are working on. It's a great thing that the devs like Archi and Arter or nameless group have been so fast with the work.

Let them focus on getting the ROM stable.
[Galaxy S III Android Development] Mostafa Wael:
just read my comment above yours

reading is a good skill to learn :rolleyes:
[Galaxy S III Android Development] szotaa:
[MENTION=4898097]arter97[/MENTION]

Gently asking you to take a look at this:

http://xdaforums.com/galaxy-note-2/devs-only/gt-i930x-hdmi-mhl-implementation-aosp-t2940110

I'm a noob so I cant verify whats that but if its something intresting maybe it would push fixing MHL on AOSP forward.

If its nothing new then sorry for wasting your time :)
[Galaxy S III Android Development] Mostafa Wael:
that is interesting !!
[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...

Posted this in AK thread, too. Don't know where the right place is...

I want to avoid Full wipe. Thanks!
[Galaxy S III Android Development] Mostafa Wael:
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] Sachiru:
Does the latest beta (4.0-beta2) support 4.3 Touchwiz-based ROMs, like 4.3 stock ROM or Android Revolution HD 52.0?
[Galaxy S III Android Development] nkirk:
yes
[Galaxy S III Android Development] Math_Apolo:
Sorry if it was answered before...

But I'm using now Boeffla Kernel and want to change to Arter97 Kernel.. Do I need an app for it, like Boeffla?

To change is simple, doing it by the philz recovery just selecting Arter kernel?

Thanks guys!
[Galaxy S III Android Development] Targaeryan:
When you flash the kernel, the app will be installed with it..
[Galaxy S III Android Development] Math_Apolo:
Thank you, And I can swap the kernel normally? From boeffla to Arter!?
[Galaxy S III Android Development] Targaeryan:
As far as I remember boeffla doesn't use modified ramdisk so you can flash arter on top of it.. But other kernel on top of arter you can't.. To be completely safe, better dirty flash your ROM and then arter..
[Galaxy S III Android Development] ZaneZam:
actually boeffla uses a modified Ramdisk but that doesn't matter here because the Ramdisk is build into the kernel image and gets rebuild every boot so u will have afters Ramdisk after flashing arters kernel. beside of that boeffla doesnt influence other kernels as it uses its own specific settings structure/handling and u even keep your boeffla settings after flashing another kernel as long as u keep boeffla app ;)

EDIT to be correct : as long as u keep the file /data/. boeffla the app can actually be uninstalled.