yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Darkened_Sky:
well with this kernel with pegasusqplus and 100mhz min frequency, I get ~5 hours screen on time, with (for me) normal tasks like surfing, chatting, music listening, permanent tasker background service and a quite bad network coverage in my region which also causes higher consumption

with "harder" tasks over day like gaming, script testing and frequent switches between my two ROMs I get ~3 and half hours screen on time

I am sure you'll like it, but maybe you need more than one full recharge to see the full potential
[Galaxy S III Android Development] Mostafa Wael:
ohhh that's freaking me out!!

my usage is surfing chatting and music streaming via SoundCloud as well as some deep sleep

so we are looking at 4.5 hours screen-on-time??

thanks alot!!! you made my day
[Galaxy S III Android Development] Kapiljhajhria:
This app not working for me. Cant find any other app as well. Can you suggest some other app. i use Kali linux.
[Galaxy S III Android Development] arter97:
So. I have two good news and one bad news.

1. (Good) School exams are over :P (until September or October)

2. (Bad) I need my S3's motherboard and touchscreen replaced. Both are dead.

3. (Good) They're still in warranty date. I maybe able to get a free replacement :)

(If not, this "might" be the end of my kernel.. idk)
[Galaxy S III Android Development] Darkened_Sky:
script updated http://xdaforums.com/showpost.php?p=53922457&postcount=854

onandroid script no longer needed for any command and no other third party dependencies anymore (well except this kernel :laugh: )

also simplified script code

also I decided to rename it to secrec as now it is a full second rom recovery tool
[Galaxy S III Android Development] Mostafa Wael:
so now i faced a strange problem

well it is not harmful but it is just very annoying

i was testing the battery life of this kernel, so i was looking frequently at the screen-on-time from the settings

then i installed "Xblast tools" xposed module which of course needs a reboot to be activated

then i rebooted without problems

but then when i messed up with another module "xui" where it required a reboot to apply changes, i rebooted

But...

when i opened the screen-on-time in the settings i saw that is re-winded back 30 minutes

it was "3 hours 10 minutes" screen-on-time

then it became "2 hours 33 minutes" screen-on-time

and total time for charge cycle also re-winded back 30 minutes

it was "17 hours"

then it became "16 hours 31 minutes"

strange right???

right now i am pissed off as i was testing the maximum screen-on-time i can reach with that beast and better-battery-stats can't keep stats from before a reboot

so is this normal? is it even kernel-related?

thanks :D

---------- Post added at 04:14 PM ---------- Previous post was at 03:15 PM ----------

my friend is going to test second-ROM installation tonight

so can you tell me what i need so far?

what are restrictions? i saw from some posts previously that AROMA-installer ROMs cannot be flashed as a secondary ROM, is that fixed?

and i am thinking about writing a step-by step tutorial for those who want to try it, are you interested? [MENTION=4898097]arter97[/MENTION] [MENTION=5314272]Darkened_Sky[/MENTION]
[Galaxy S III Android Development] JustArchi:
What happened? :crying:
[Galaxy S III Android Development] Darkened_Sky:
damn (have completely overseen your post sorry) :(

really hope you get your free replacement by warranty

but congrats to your accomplished exams
[Galaxy S III Android Development] habylab:
That suckssssss.

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] abhibnl:
And how.did that happen? Probably during an experiment!![emoji50]

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] arter97:
That should be ROM related not the kernel.

I still haven't figured out how to nail the root cause of multi-boot.zip compatibility issues.
[Galaxy S III Android Development] arter97:
EFS is dead. Not the files within, but the partition itself. It has made stock kernel unable to mount /data(since /efs mount fails, all entries behind it fails) resulting in boot-loop.

So I was trying out Triangle away for root counter reset, but due to Korean variant's bug with Triangle away, the touch sensors are dead.

Lol
[Galaxy S III Android Development] JustArchi:
You could boot recovery (it actually doesn't care about mounts at all) and fix all partitions through reformatting, like mke2fs -t ext4 /dev/block/efspartition. This would fix it :p. I corrupted my /data on my Xperia M and fixed it the same way.
[Galaxy S III Android Development] vyp54:
I have empathy for number 2. I've had 2 screens, 1 camera module and 1 motherboard replaced while warranty was still worthy. I know we are not living in the same country (or on the same continent xD) but if it's of any consolation they did it all for free.

I wanted to ask a question about charging rates support or future implementation but it's no use until we get the service status of your S3.

Hope all ends weel. :highfive:
[Galaxy S III Android Development] arter97:
Yup, definitely! If only there wasn't "input/output error" that is!

(And I'm just about 99% sure you know what that means xD)
[Galaxy S III Android Development] arter97:
Yes I also think it'll gonna be free....

And what do you mean by charging rates?
[Galaxy S III Android Development] Darkened_Sky:
as a workaroud for aroma based roms as second ROM you could:

1) make a nandroid of your current ROM

2) flash your desired aroma based ROM as primary ROM

3) boot it one time and lokk if everything works

4) make a nandroid backup of it

5) restore your old nandroid backup of your first rom

6) use my script to extract the newer nandroid backup to your second rom slot with the "nan" command
[Galaxy S III Android Development] vyp54:
My apology for bad choice of words. I was aiming at kernel control over charging current: ignoring safety margins, unstable current and control over the current itself - like the options present in Boeffla kernel. I'm talking about myself now, but I've read that other people have troubles with charging since the charging rate is around 200mA for all of us with faulty (OEM) chargers. The phone uses more power than the charger provides and you cannot even charge it to 100% when it's turned off for 8 hours.

And for the people that have normal chargers - it's also a nifty feature since you can increase the current a bit and profit by saving time. I kept mine on 1300mA and never had overheating or problems with OEM charger (except it being faulty in the first place) or OEM battery.

Is this hard to implement and what's your policy on this?
[Galaxy S III Android Development] -MaD-:
It would be nice to see this in your own thread.

Thanks for the work!

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] arter97:
I don't remember mentioning those power controls in the OP but mine already has power controls by AndreiLux.

Ignoring margins and setting currents.

Higher mA on USB is applied by default(1000mA).
[Galaxy S III Android Development] vyp54:
I'm asking because I haven't found it in the OP. That's great. I will definitely give your kernel a try as soon as I grab some free time.

One more question though: are you a fan of f2fs¿ I haven't tried it for now since I was okay with ext4. Is it really worth it¿ I will be running AOSP based ROM so I dont need /cache, just /data. You mentioned that /system should be left on ext4¿ Android doesn't handle f2fs too well¿
[Galaxy S III Android Development] arter97:
Honestly, I'd recommend f2fs not for speed but for stability. When I was using ext4, I experienced many data corruptions such as boot-loop or some app's data missing. Now with f2fs, I haven't experienced it since 2013.08 which is super awesome.

So here's my opinion : f2fs is not only faster(fio benchmark showed 2x speed improvements) but also stabler than ext4.

It totally worth it, go for it!

There is not a single issue with Android side. Not one.
[Galaxy S III Android Development] arter97:
Managed to get a free board replacement. Too bad it's running Android 4.3 which has KNOX on our Korean variant.

Gotta break KNOX Warrenty before starting development.. XD

They somehow managed to get screen back and running without a replacement :)
[Galaxy S III Android Development] Mostafa Wael:
wtf?? you have knox???

i guess you have to be more careful as when breaking knox warranty while developing they will never ever replace anything under warranty

here in Egypt they are dumbasses and don't understand anything :laugh::laugh:
[Galaxy S III Android Development] eamon.ash:
[MENTION=4898097]arter97[/MENTION] Hey can I ask a question.. in the archi ports there is a problem.. when you connect the charger and the phone is off the phone boot up again. . Is this problem solved in this kernel

Thanx
[Galaxy S III Android Development] arter97:
We can get free replacements even after KNOX Warrenty has void(at least in Korea).
[Galaxy S III Android Development] arter97:
Disable power-boost and let's see what happens.
[Galaxy S III Android Development] eamon.ash:
You mean after install your kernel I disable power boost from the control app.. sorry I 'm new in kernel thing
[Galaxy S III Android Development] vyp54:
In the first post you suggest to switch only /cache and /data to f2fs. System is kept on ext4. I don't get why not to format /system to f2fs also since it's faster and more stable thank ext4. :confused:

Does switching to f2fs mean that ROMs with hardswap (i.e. Archidroid) will also hardswap faster than on ext4?

I guess in Croatia they have stocked up on old motherboards so KNOX is a still unknown entity here. xD

Sorry for OT.

---------- Post added at 09:36 PM ---------- Previous post was at 09:36 PM ----------

Yep, you disable it, reboot and try if the problem persists.
[Galaxy S III Android Development] mischa_martin:
[MENTION=4898097]arter97[/MENTION]

Are there any plans of fixing sdcardfs to work with Foldermount?

Because I really love your Kernel (Mostly because its based on Samsung Sources and its stability :D)

But I can´t use it because I need to use Foldermount because all of my important data (whatsapp images etc.) are on my externalsd and get mounted to internal for whatsapp to work.

If you are not planning to change it could you tell me some advantages of the new sdcardfs?

thanks in advance

mischa_martin
[Galaxy S III Android Development] Mostafa Wael:
hey

if i plan to stick for ext4 for a while, can i still use your recovery without formatting to f2fs??

and if i want to restore an old ext4 backup for my ROM, can i restore it normally through your recovery after formatting f2fs?

thanks a lot

as i am comfortable with your kernel as a daily driver so i am considering a move to f2fs...
[Galaxy S III Android Development] arter97:
Of course. Switching to f2fs on /system is also beneficial except it requires support from ROM side(updater-script) which is kind of a pain if you're planning to non-f2fs supported ROM(like official CM). So I'd just stick with ext4 on /system since there's not a lot of read&write on /system.
[Galaxy S III Android Development] arter97:
Read the OP about the benefits of using sdcardfs. I'm planning to add a switch for going back to fuse(old, non-sdcardfs implementation) in aTweaks. Seems like even the Foldermount developer has not been able to fix sdcardfs to use with Foldermount.
[Galaxy S III Android Development] arter97:
Yes. ext4 should be fully functional on my recovery as well.
[Galaxy S III Android Development] vyp54:
Thanks for all the answers, I've really learned something. I will report the user experience after I grab time from the still ongoing exams. :/
[Galaxy S III Android Development] mischa_martin:
That would be great. :)

I also think that the battery improvment of sdcardfs is minmal because I haven't noticed anything special between battery life in yours and justarchis kernel.

thanks in advance

mischa_martin
[Galaxy S III Android Development] arter97:
Small changes makes a difference.

There's a reason why Samsung put efforts in making it.

It'll benefit in battery, performance and reducing RAM usage.
[Galaxy S III Android Development] cba1986:
[MENTION=4898097]arter97[/MENTION] do you remember the log attached in a tweet about a camera error in temaseks latest ROM v112 that use the latest kk blobs?

It seems is kernel related. Now i am using agni 2.8.3 kernel and the camera bug is gone.
[Galaxy S III Android Development] mischa_martin:
Okay I understand.

Does anybody know if mounting via init.d script works?

I don't really want to try it myself because I have to give up my current (perfect) configuration.
[Galaxy S III Android Development] Darkened_Sky:
not really. just tried to bind my screenshot folder to external sd card. seemed to work as the file explorer is able to see the files on external sdcard as well as on the original screenshot folder (before the command I moved my screenshots to the external sd), but I am not able then to make new screenshots. The same is for example with internal download folder.

i tried it with "mount -o bind" as well as with "ln -s" . both with the same problem. But I personally don't really care for it. I also think the new sdcardfs is more worth..

btw. something else:

I finalized my second rom recovery script, I don't think that I will add more things in future (no ideas left that interest me :silly:)
[Galaxy S III Android Development] Mostafa Wael:
so now i want to run AD 1.7.16 as 2nd ROM

here is what i am going to do:

1) backup current ROM

2) flash Darkened_Sky script

3) then flash AD 1.7.16

4) flash arter97 kernel

5) reflash Darkened_Sky script

6) backup the newly installed AD 1.7.16

7) open terminal emulator and type "nan"

8) restore the old nandroid backup

can anybody confirm if this is the right way, or i am missing something?
[Galaxy S III Android Development] Darkened_Sky:
by doing step 8 your data partition gets overwritten and your second rom will be lost. first do your step 8 then 7. and 2 and 5 are not needed. simply flash my script before restoring the nandroid backup as second rom. doing it the way I described it here is absolutely sufficient.

btw. for using my script you have to type: su - enter - secrec -enter - nan - enter - choose your backup (make sure that your backup is on external sd card)
[Galaxy S III Android Development] Mostafa Wael:
thanks for confirming

tomorrow i will test this method and report if there were any errors encountered or not...

btw can i use this method to dialboot ArchiPort beta 1 or it also cannot be done by using this way?

i read previously that archiPort is not supported to be dualbooted by using the multiboot.zip file

thanks again
[Galaxy S III Android Development] arter97:
Ah sorry, not yet.

I'll make sure I do later.
[Galaxy S III Android Development] Darkened_Sky:
i have tested archiport as second rom with this method. it worked.
[Galaxy S III Android Development] Mostafa Wael:
so now i converted to f2fs

and i must say the dedicated recovery arter made is IDEAL and EXCELLENT. no errors. simple. reliable. it is indescribable :)

thanks arter for this piece of art.

now converting to f2fs is much easier, unlike the old days when we were converting using devil touch. yeah you made it much easier :good: :good: :good:

---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------

does this kernel have the extra 533 MHz like most of the kernels have?

and if not can you please include it?

thanks alot!
[Galaxy S III Android Development] Mostafa Wael:
and now i played with Darkened_Sky script and dualboot with AD 1.7.16 is successful :D :victory:

but i am not a fan of dualboot so i removed it :)

thanks for you

this kernel has everything i want

f2fs / stability / dualboot / CPU OC

i don't think there is anything else that i want

waiting for the next version

i want to see what arter will amuse all of us with in the next version

and as for the second ROM recovery script i also see that it is finalized and has nothing else to be included

it is just perfect

just to make sure

this script does not require the onandroid script to be installed ANYMORE?

i mean precisely the f2s command does not require the onandroid script in the latest version?
[Galaxy S III Android Development] Darkened_Sky:
yes not needed anymore, script is now fully working without any additional script. the basic how it works is that it makes a tar of your first roms system/data/cache and directly pipes them into the extraction of the tar to second rom slot.

In older versions I needed the onandroid script for tar-ing the primary ROM, because when I have done it without it, the second rom bootlooped. But my failure was, not to exclude data/media (onandroid script did it, and that was the reason why I used it, until I discovered my mistake). And now without the onandroid script it's working way faster because I can directly pipe. :cool:

btw thanks for the feedback

But let us not talk anymore about my script here. It should only be a help for those who like/need dualbooting like me. In fact this is a kernel development thread :angel:
[Galaxy S III Android Development] Mostafa Wael:
yeah i noticed that i have talked about it too much, sorry for that :angel:

apart from the question i asked, i just wanted to verify to everyone that it is working as it should perfectly

in other words i want to clarify that it has been tested :highfive:
[Galaxy S III Android Development] vyp54:
When switching to f2fs - I format data and cache in f2fs, flash ROM, flash your kernel and then boot?
[Galaxy S III Android Development] Kapiljhajhria:
UMS mode issue.

i tried f2fs format and really felt the improvement. but biggest drawback is that i am not able to use USB MASS STORAGE mode. tried few apps but they didn't work.

also tried to mount my card as usb from recovery but that also did nothing.

official CWM, philz and TWRP recovery can mount external card as USB from recovery fine. but not the custom recovery provided in OP.

any help? maybe OP can fix the recovery or if anyone can give me a link to an app which works.

or if maybe i am doing something wrong?

help?
[Galaxy S III Android Development] Louis235:
When I change my present Kernel (Boeffla) to this one, is it necessary to clean the Kernel before? Don't want to reflash the whole ROM but try this Kernel and Dualboot.

Thanks in advance
[Galaxy S III Android Development] Mostafa Wael:
Though it is presented in a nice, easy-to-do way in the OP,

move every bit of personal data file; like music and photos, from your internal storage before proceeding!!!!!!

1) nandroid backup your current ROM to external sdcard using the f2fs-dedicated recovery made by arter97

2) after backup is finished, go to "Mounts and Storage" option

3) navigate downwards till you reach "Toggle ext4 <--> f2fs migration"

4) go upwards and "format /cache" --> select f2fs and confirm

5) afterwards got to

"format /data and /data/media"

and confirm to format device, then select f2fs and confirm again

---------------------------Now you finished formatting the partitions to f2fs, the next step is optional just if you want to restore your data again, or in case you don't have a backup of your apps like titanium backup for instance----------

6) restore your previous backup of the ROM

that's it and your done

---------- Post added at 01:58 AM ---------- Previous post was at 01:27 AM ----------

Well it is recommended when coming from any other kernel to clean the device from the previous kernel's traces, if the kernel dev provides you a cleaner script that needs to be flashed before flashing any other kernel, and i don't think that Lord Boeffla has uploaded a cleaner script for his kernel, as his scripts are boeffla-kernel specific which means, that it does not do any effect to the phone unless there is a boeffla kernel installed on the device

so in this case there is no cleaning required, just flash and go ahead :good:

---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------

hey guys i have a question:

which is better in terms of battery life? pegasusqplus with SCHED_MC=2

or

Zzmoove moderate ??

and which has a deeper sleep?
[Galaxy S III Android Development] ulixess:
[MENTION=5060769]Mostafa Wael[/MENTION] thanks for your nice how to :)

I've got a question: Can I flash any Rom through the new Recovery by arter while on f2fs or do I have to make a nandroid backup and flash this nandroid back like on old devil f2fs?

I mean, in devil, we were not able to flash a new Rom while using f2fs.

EDIT

I did some research and read that only formating /data and /cache does not require a special flash method since /system is still on ext4.

But if I format /system to f2fs, I've to modify the updater-script in order to mount /system properly.

Does anybody know the exact change in updater-script?
[Galaxy S III Android Development] pricey2009:
Is there any chance we could have a dark theme for atweaks?
[Galaxy S III Android Development] vyp54:
Thanks for the info, but that did not answe my question. I've found out myself what to do after a few bootloops. :silly:
[Galaxy S III Android Development] Mostafa Wael:
nah that's not my area :silly:

but installation of ROM is normal don't worry

for example i just installed a new ROM today and also i installed a new 2nd ROM normally using the workaround

---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------

what do you mean? are you ok now?

i didn't think i was that unclear, sorry :D

tell me what you did? "if you like"
[Galaxy S III Android Development] vyp54:
No, no it was clear, but I've used ext4 before and never f2fs. I also repartitioned the memory and the ROM I use doesn't support f2fs (ROM's kernel that is).

I've tried it and it's: 1.Repartition, 2.Format to f2fs, 3. Flash ROM, 4. Flash Arter's kernel before first boot (or it won't boot).

I, along with /cache and /data, also tried to format /system to f2fs but that's a no no, since the ROM cannot boot even on Arter's kernel.
[Galaxy S III Android Development] Mostafa Wael:
could you please tell me what are the pros of repartitioning?

or give me a link to it...
[Galaxy S III Android Development] vboyhn:
http://xdaforums.com/showthread.php?t=2762594

Model: GT-I9300

Rom: Blekota beta 5.1

Kernel: Boeffla 6.0 beta 4
[Galaxy S III Android Development] george stamatos:
Hi arter97, can't install 14/7 cm11 nightly as second rom, says can't install incompatible data over bla-bla... I think you have to update your recovery. Thanks in advance
[Galaxy S III Android Development] Darkened_Sky:
are you on f2fs? if not you can use each recovery you want, even if you want to flash second rom. if it still fails with other recovery then problem lies somewhere else (in my opinion it is not because of recovery, as it is one of the latest philz touch)

are you sure that maybe your nightly wasn't maybe a bad download?

also I think a recovery log would be helpful.
[Galaxy S III Android Development] Dabidue:
Nice, stable and fast kernel so far, thank you for the excellent work.:good:

But one thing should been added in my opinion: please add a tunable background cache cleaning and a corresponding tab in the aTweaks, so that one can delay or fasten the time until cache will be cleaned. Else, it would be great to set configurable parameters like the amount of cache to clean and clean by fifo principle.

At least, zram compresses 4k only and then seems to stop. Does zram feature correspond to swapping and the swap file? :confused:

Where can I choose the name and location of a swapping file and can it be located on the sd card instead of internal memory?

Anyone out there experienced problems activating 1.8ghz as max freq?
[Galaxy S III Android Development] george stamatos:
No f2fs...