yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Mostafa Wael:
yeah me

but,

each device has its own maximum frequency that can endure, for example, i have max stable is 1.7 GHz as 1.8 GHz give me random reboots.

some devices can only endure 1,6 GHz which most devices can endure

a minority can endure only overclocking to 1.5 GHz or even 1.4 GHz only

this differs from one mobile to other according to build quality. i remember this has something to do with ASV Level, but i don't remember exactly.

ASV level is something like an indication of your build quality. it is out of 7. the higher the ASV level, the more overclocking and undervolting your device can endure.

P.S. i am not an expert, so please if there is anything wrong, correct me so me and the other people can learn something new :highfive:

---------- Post added at 07:39 PM ---------- Previous post was at 07:00 PM ----------

hey guys,

so as mentioned before i formatted to f2fs and wanted to dualboot an aroma-installer ROM so i used the workaround by using secrec script

i made all the steps until the "nan" command part

it produced an error: can't pipe system.ext4 to /data/arter97_secondrom

no such directory

so i created a folder in the /data and named it "arter97_secondrom" and tried again and it worked

but i think that when flashing this kernel, such a directory must be created automatically

so [MENTION=4898097]arter97[/MENTION] can you take a look at it?

other than that kernel works perfectly

i am having the best combo of battery life and smoothness with Zzmoove moderate @ 1.4 GHz

waiting for next version :D
[Galaxy S III Android Development] Dabidue:
Although the cache would be cleaned, the ram wouldn't been free in the same time. :confused:

Perhaps that could been done by a configurable tunable timer?
[Galaxy S III Android Development] Darkened_Sky:
nope my fault. normally directories are created when multi-boot.zip is flashed, and if it was never flashed then the directories are not available. But now my script checks if they are available and creates them if needed.
[Galaxy S III Android Development] Mostafa Wael:
so you uploaded now a fixed version of the script attached to your post?
[Galaxy S III Android Development] Darkened_Sky:
yup
[Galaxy S III Android Development] Mostafa Wael:
[MENTION=4898097]arter97[/MENTION] i searched for the quote where i asked you if i want to change back to ext4 and you said that it is untested, now i want to confirm that also changing from f2fs to ext4 is also compatible with your recovery, so rest assured you can say that ext4 <--> f2fs is FULLY TESTED on my responsibility :highfive: as well as the dualboot script created by [MENTION=5314272]Darkened_Sky[/MENTION]

now i am going to make a battery life test accross all the kernels with the same configuration "Zzmoove- moderate" @1.4 GHz and no zRAM

this will take some time

will be back with the test results

but i think the lead will be for one of the newest kernels so far, i guess everybody has an idea what 2 U13 kernels are in the battle now ;)

---------- Post added at 12:54 AM ---------- Previous post was at 12:26 AM ----------

ohh just 1 more question

the script pipes the backup into the 2nd ROM, but is there any restrictions on the backup in terms of the recovery used?

in explanation, can it pipe a backup made through:

1. Any recovery (doesn't matter even if it is TWRP or CWM)

2. only CWM and any recovery based on it (example "philz" and "official CWM available for our device through ROM Manager" and "CM recovery which is updated every time you install a CM nightly by enabling that option in developer settings")

3. only philz (doesn't matter whether it's arter's recovery or official philz recovery found in his thread or philz recovery made by justarchi)

4. only arter's recovery

i think that's an extremely important question. in my test i used arter's recovery of course as i was on f2fs timely
[Galaxy S III Android Development] Darkened_Sky:
cwm and everything based on it (philz and arter's philz) should be fine. your current filesystem should also be no problem. script will find the correct files.

never used twrp and I have no intention to ever do it, so don't even know in which formats the nandroid backups are made and how they are named. if they are uncompressed tar and there is a system, data and cache part, then it should be fine as well. if not, then not ;)
[Galaxy S III Android Development] Mostafa Wael:
so up till now it is number 2

but i will test it after my battery life test

it worth a test
[Galaxy S III Android Development] pricey2009:
F2FS causes too many problems on Liquidsmooth.. such as camera not working, youtube not loading and others..

I am going back to ext4 now as I couldn't see any improvements anyway..
[Galaxy S III Android Development] vyp54:
Camera is dying on Archidroid aswell. Are you sure your camera died because of F2FS?
[Galaxy S III Android Development] pricey2009:
Yup since I changed back to ext4 no issues..
[Galaxy S III Android Development] Mostafa Wael:
okay i can't tell now but i am on ext4 no issues at all on ArchiKernel_V1.3

i flashed the CM camera fix by that contains the CM11S camera app

i just can't remember the author now

back to the topic, i also never had issues with arter kernel on ext4

i will tell you tomorrow as i am making a battery life test accross all the kernels and tomorrow is arter97's turn where i will format system to f2fs and test it.

wait till tomorrow.

you can see my ROM in my signature down developed by [MENTION=1597520]Markox89[/MENTION]
[Galaxy S III Android Development] pricey2009:
Definatly because of f2fs, I tried it again by installing fresh ROM on f2fs format and those issues came straight back.. No more f2fs for me thanks.
[Galaxy S III Android Development] vladakster:
Does anyone have a problem with write permission on sd-ext? After every reboot, I have to manually change permission to enable writing to sd-ext. After that everything is okay. I installed Archi's port after a full wipe, latest kernel and recovery.
[Galaxy S III Android Development] Mostafa Wael:
i don't know what now, but i am currently backing up my ROM to external sdcard and it is backing up "Keychain" (a file in /data partition that i don't know) for about 3 minutes. never seen your recovery taking such a long time to backup a file in /data. the android robot is still spinning its gear in its back but hey what is going on here?

is it freezed?
[Galaxy S III Android Development] rick0025:
it also happend to me yesterday..it stuck..so i force reboot then delete the backup that stuck then backup again and it goes fine
[Galaxy S III Android Development] GR0S:
Video lags as hell on PA Stable. Using pegasusq governor and bfq IO sched.
[Galaxy S III Android Development] Mosh Edd:
Seriously!!! :eek: go report that to PA not here. :rolleyes:
[Galaxy S III Android Development] SaschaKH:
I don't OC but I'm told that every S3 runs without any problems at 1500 MHz and nearly every at 1600 MHz, most even have np with 1700 MHz but 1800 MHz is to much for a lot. The problem is when you OC you often have to OV too and that can lead to a temperature problem, i.e. your S3 can get burning hot.

The ASV level stands for that, if you have a high ASV level you can UV and / or OC more. Low ASV level means you need higher voltage to run stable.
[Galaxy S III Android Development] vyp54:
Please do post results, I'm keen to see if there's a difference between Archi's and Arter's since they are both Samsung based.

Was your /system on F2FS too, or just /data and /cache? I will revert fresh to ext4 and report. I hope I solve my problems like you did. :fingers-crossed:

OV along with OC should be automatic, no? Since [MENTION=4898097]arter97[/MENTION] didn't give us the option to OV/UV by ourselves there should be (by logic) and automated OV when you select values that are higher than stock. :confused:

Where can this ASV level be checked? And what are the refferent values?
[Galaxy S III Android Development] george stamatos:
Only SlimKat is possible to flash as second rom, cm and cm based get error 7, i ll try Omni in a while

Omni 16/7 installed ok
[Galaxy S III Android Development] Mostafa Wael:
well up till now arter's kernel is doing a good job, but ArchiKernel has better graphics performance (to be honest it is a slight difference)

in AnTuTu Benchmarks the 3D graphics test hit a maximum of 29.6 fps in ArchiKernel, but only 27.3 fps in arter kernel.

does arter kernel has the latest r3p2-rel4 mali drivers?

if not then i will be waiting for it in the next (mighty) version

for camera problems in f2fs, i verify that when opening the camera app it hangs for 10 sec then opens normally only, but sometimes playing videos online returns me an error "Sorry this video can't be played" which needs to be solved temporarily with the famous "Restart Camera" app by temasek.

battery test continues...
[Galaxy S III Android Development] Darkened_Sky:
well probably cm changed something in their updater-script, that it is not possible anymore to be flashed mith the multi-boot.zip. It seems to have the same problem as the stock ROMs (also error 7 when flashed with multi-boot.zip)

In the past I modified the updater script (of stock roms but it should also work for cm) so that it does not need the multi-boot.zip, then it will be directly flashed to the second ROM slot.

you simply have to replace all extractions to /system with /data/arter97_secondrom/system (same thing for the symlinks) and you should delete the lines where system and/or data are formated/wiped, and also delete the line which extracts the boot.img
[Galaxy S III Android Development] Mostafa Wael:
but we can still install CM ROMs as 2nd ROM using the same way used with Aroma-installer Stock ROMs, using your secrec script, right?

btw [MENTION=4898097]arter97[/MENTION] where are you great dev, hope everything is fine.... :fingers-crossed:
[Galaxy S III Android Development] arter97:
I'm currently busy with S4 which is my daily driver.

I'll get back on S3 ASAP.

I will update multi-boot.zip also.

And guys, U sure the Camera issue is because of f2fs?

Because it sounds kinda ridiculous.
[Galaxy S III Android Development] Mostafa Wael:
ladies and gentlemen,

i would like to announce the result of my battery life test for both kernels now.

Both kernels of course had the enough juice to continue the whole day without charging, but....

arter kernel: total time - - > after 16 hours sharp of usage has residual charge of 14% and screen-on-time of

2 hours 57 minutes

which is perfect :good: :good:

ArchiKernel: total time - - > after 16 hours sharp of usage has residual charge of 8% and screen-on-time of

2 hours 39 minutes

which is also good and enough for a full day usage :good:

Note that:

*total time is the same

*deep sleep times are quite similar

*gaming times was also quite similar and also the same games.

*ROM used was the same

*setting for CPU was the same "Zzmoove - moderate @ 1400 MHz and no zRAM no UV or OC no nothing!"

here you are.

Conclusion:

Both kernels gave enough battery life for a whole day usage as well as letting my phone as smooth as butter. but arter kernel slightly beats the competition, which I think because of some batter life optimisations being added like "firelock" and the 100 MHz (although this 100 MHz wasn't used alot)

Anyways wish you all guys the better experience with your phone with either kernels, both will make your phone literally fly!!!!!

no offence.

Enjoy everybody
[Galaxy S III Android Development] SaschaKH:
Ups to slow, please delete.
[Galaxy S III Android Development] boosha:
Stupid question,,, What is the f2fs ?? ... What is the benefits of using it ??

And if i want to use it how i can ,, Now I'm on Blekota S5 Lite 4.4.2

Thanks in advance
[Galaxy S III Android Development] arter97:
Google about f2fs. Read the OP how to apply it.
[Galaxy S III Android Development] cba1986:
I don't think that the problem with the camera is f2fs related. Currently i am using agni kernel with f2fs with 0 problems. I think that the problem has something to do with re-introduction of the samsung camera wrapper in CM and the kk blobs introduced also by CM in the latest updates.
[Galaxy S III Android Development] xpmode:
See if these steps fix camera on F2FS:

1. Switch all partitions to ext4.

2. Install ROM but do not install any kernel.

3. Boot the device, and take some pictures with the camera.

4. Install arter kernel.

5. Boot again and take some more pictures.

6. Take a nandroid backup to external SD card.

7. Format to f2fs.

8. Restore the backup.
[Galaxy S III Android Development] vyp54:
If [MENTION=4898097]arter97[/MENTION] is considering a new version with new MALI drivers, might I suggest having a look at latest wifi drivers also? At the Archikernel topic everyone reported slight or noticeable improvement. Here's the quote from the dev:

I would try it, but I've lost interest in F2FS since not only camera has issues but also Gallery cannot show anything and FC, I have problems playing online videos "Sorry, this video could not be played" and so on...

As a great dev JustArchi said - it causes many (even unvisible) bugs and I've realised this in my own experience. For me the extra speed you get is not that great and it definitely loses all when opposed to having system stability on EXT4.
[Galaxy S III Android Development] psndna88:
f2fs and camera has no relation .

ive never had any cam issues with my f2fs on any rom.

Sent from F2FS FORMATED I9300 LS-KK-v3.2-2014-07-15 (4.4.4) + AGNi pureCM v2.8.4 kernel with ART
[Galaxy S III Android Development] cba1986:
There is no problem with f2fs and the camera. I am using without any problem on agni kernel + v115
[Galaxy S III Android Development] Mostafa Wael:
arter can you please look into that request in the coming version..?

(*) add an extra 533 MHz in GPU

(*) update to latest r3p2-rel4 mali drivers

(*) update to latest wifi drivers

thanks alot for this beast. it took the lead in my battery life test. but improving the Graphical performance is necessary also..

wish you to be back asap
[Galaxy S III Android Development] Mostafa Wael:
seems like my request didn't take that interest....
[Galaxy S III Android Development] Mostafa Wael:
does the "Firelock" work with all governors? or with PegasusQ+ governor only??

sorry for asking too many questions... :D
[Galaxy S III Android Development] vyp54:
As it turns out f2fs does cause bugs for me. I've fresh installed on ext4 and gallery is working, camera is snapping and videos are playing. :highfive:
[Galaxy S III Android Development] arter97:
GPU OC : As I stated on the OP, I'm not interested in GPU OC just like CPU UV. I don't really like the GPU OC implemented on our i9300 and it seems to cause more issues than it should be. Yank555-lu also had said he won't be taking any bug reports if user happened to be using GPU OC.

New Mali r3p2-rel04 : This one also, as I stated in the previous post(I think you've seen it), because of the blobs are rel03, I'm not comfortable in doing so. Kernels which are using rel04 is using incompatible "old" blobs and just hoping that it won't cause any issues.

I'm aware of the Graphics performance issue with my kernel. I'd like to find out the root cause and match the performance with the stock i9300 kernel, not by adding OC or hacking Mali drivers.

New bcmdhd drivers : My 1.x kernel also had an updated Wi-Fi drivers from i9500 and it turns out to be a beast. Fast. But it consumed more battery and caused more wakelocks. I'll wait until some other Samsung's official kernel which uses the same Wi-Fi chip as i9300 gets updated, not just port other chips driver.
[Galaxy S III Android Development] arter97:
PegasusQ and + and YankasusQ.
[Galaxy S III Android Development] mrjoy:
+1

---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------

You mean after flashing multi-boot.zip then the rom would goto 2nd system partition automatically without any doing other steps? And whenever if we want to flash any file on 2nd rom then we have to flash multi-boot.zip file too every time?
[Galaxy S III Android Development] arter97:
I'll take a look at it again. Mine and the Korean models has 2GB of RAM, so didn't think about RAM getting insufficient :(
[Galaxy S III Android Development] arter97:
Yes and yes.
[Galaxy S III Android Development] mrjoy:
Yes i understood everything & i successfully flashed 2nd rom too. Its really very fast than creating img system partition as other recovery needs.:laugh: but one question that after flashing multi-boot.zip file it does not create img system partition?, mean is it directly installs to sdcard & in which path?
[Galaxy S III Android Development] arter97:
The 2nd-ROM slot is placed on /data/arter97_secondrom
[Galaxy S III Android Development] george stamatos:
Thank you for your help. I am gonna try and report.
[Galaxy S III Android Development] Elimn8r:
I had the same problem on the same recovery. Everything else seemed to flash except the boot image so i extracted it and used flashify to flash the boot image
[Galaxy S III Android Development] arter97:
Thanks for your effort for making user more convenient, but as I've mentioned on the OP :

"Do not redistribute, modify, fetch, extract files used within this project or integrate with other files without my permissions.

Making mirrors, re-uploading to another servers are strictly prohibited with no exceptions."

I'd like you to take the Dropbox file down.. sorry!
[Galaxy S III Android Development] tintin1503:
Really cutting edge feature rich kernel I must say and on the top of that even supports the 4.4.2 archiport. Hatsoff to you Bro for this great work.Hope to see your work progress even more.

I know benchmarks doesn't mean much but still here is something extraordinary I just got.

.

Archiport 4.4.2 + arter97 kernel running [MENTION=5301607]170[/MENTION]0 mhz. My S3 is flying literally.
[Galaxy S III Android Development] Mostafa Wael:
So now may i know if anybody managed to flash the .zip file successfully from recovery "traditionally like flashing any other zip"?

Please let me know which recovery successfully managed to do this?

Also i will try to flash it over stock omni kernel and philz recovery 6.41.5 by justarchi and report.

Also it would be nice if a link to the recovery is included.

And it may be nicer if this recovery is mentioned in the OP.

Thanks everybody :)
[Galaxy S III Android Development] arter97:
I've only seen Antutu benchmarks around my kernel, not Quadrant.

So it's not too shabby? :)
[Galaxy S III Android Development] arter97:
Seems somehow everyone is having problem with "PhilZ recovery by JustArchi".

I'll have another look, meanwhile, you can install another recovery and install my kernel..
[Galaxy S III Android Development] Mostafa Wael:
Like TWRP 2.6.3.1 for example?

If only TWRP 2.7 is working please guide me to the direct download link for the TWRP.zip file

Thank you so much and congratulations for publishing your first kernel :)
[Galaxy S III Android Development] nik60:
hi,

there isn't TWRP zip

only tar for ODIN

install "GooManager" from play store ...open...click right soft touch.. and choose "install OpenRecoveryScript" and wait download ...installation is auto....no need reboot

wait until popup say "recovery has been installed"

2-method---TWRP manager from play store
[Galaxy S III Android Development] tintin1503:
Here is a link to TWRP 2.7 zip file

http://xdaforums.com/showthread.php?p=50943534
[Galaxy S III Android Development] spoonymoon:
Just use devil's recovery works flawless

But remember to flash as kernel/recovery/modem option

:)
[Galaxy S III Android Development] Mostafa Wael:
So now if i want to dualboot the archiport all what i have to do is to flash the "multi-ROM.zip" followed by the archiport.zip file and it is done right?

Also i have flashed your kernel successfully with TWRP 2.6.3.1

Kernel is smooth and responsive and full of features.

However i am missing the GPU Overclocking and the undervolting feature "well not so much :) "

I would like you to take a look.

However you made a perfect start with this kernel, that's great!!
[Galaxy S III Android Development] Madness.:
Touch2Wake isn't auto activates itself on reboot. Please fix it.

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] szunyi77:
Hello, I am currently Sokp 4.4.2 rom and want to try the kernel. Includes interface? Or to use trickster mod? Thank you

Sorry for my bad english..
[Galaxy S III Android Development] tintin1503:
^^ Kernel includes it's own tweak application aTweaks which is based on stweaks automatically installed on flashing.

---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------

[MENTION=4898097]arter97[/MENTION] Had a similar experience please have a look.
[Galaxy S III Android Development] arter97:
Can I ask you some logs with f2fs?
[Galaxy S III Android Development] Mostafa Wael:
okay so you see that the "graphics performance issue" is not because this kernel is using r3p2-rel3 instead of the newer r3p2-rel4.

maybe you can take a look in the GPU thresholds? i. e. the time exactly when the GPU frequency step changes from one to other?

anyway that was just a suggestion and i am not putting any pressure. your kernel gives me the best battery life and multitasking and that's fair enough for me. :good:

i hope you can figure out the root issue of the low graphics performance in the next version

about the WIFI: also it is okay as i tried ArchiKernel "the newer version with the newer WIFI drivers" and i do not feel any improvement... so it seems that it does nothing but consuming more battery.

last question: which governor do you suggest to use to give better battery life? PegasusQ or PegasusQ+ or YankasusQ?

thanks alot for your support [MENTION=4898097]arter97[/MENTION] and i am sorry if I sound annoying to you, but english is not my mother language
[Galaxy S III Android Development] arter97:
I haven't touched anything related to GPU frequency scaling.. so it maybe hard to find out, to fix.

Also it maybe not fixed with the next version since it's a bit off from my priority list.

YankasusQ is ultimate for battery, it clocks down, turns off the CPU cores more aggressively compared to every other governors.

So of course, it'll drain back a lot of performance.

So, YankasusQ is for anyone who thinks full performance of i9300 is a waste and cares deeply about battery.

PegasusQ + is... a PegasusQ based governor but contains a lot of code changes from AndreiLux.

I'm not really sure if those changes are all that beneficial, so I'd let users to choose it or not.

And lastly, go ahead and keep poking me!

New ideas, suggestions are always fresh and keeps me motivated and not annoying at all! :D
[Galaxy S III Android Development] arter97:
I've just bought a new domain and registered a new hosting service for all of my projects.

Hopefully it's fast enough to ditch mega.co.nz..

My plan for next version is implementing a easy upgrade solution integrated to aTweaks.

So that users can launch aTweaks and upgrade the kernel right there with just one click :)
[Galaxy S III Android Development] george stamatos:
Please fix cm install in second rom.........

When you have time of course, and congrats of your new domain
[Galaxy S III Android Development] arter97:
Will do ;)
[Galaxy S III Android Development] Mostafa Wael:
Maybe a Poll will show me, you and us if this changes are necessary? ;)

IMO I guess that these changes are necessary, otherwise why most kernels have this governor included?? :)

maybe another battery life test will show us ;)
[Galaxy S III Android Development] pricey2009:
Could we also have a dark theme for atweaks? Thanks buddy! :D
[Galaxy S III Android Development] xpmode:
Holo Themer Xposed module can help you with that.
[Galaxy S III Android Development] pricey2009:
I don't like to use xposed though..

I have had bad experiences with it..