yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] vyp54:
I would gladly give them to you but I was so frustrated with everything being buggy that I wiped everything and went back to ext4 because I needed the phone to be functional. :silly:

My main 3 problems were:

-Camera couldn't connect almost half of the time. Sometimes it would display rather weird glitches in forms of rainbows and strings.

-Gallery would FC after viewing one pic or even if Gallery was launched within other app (such as file manager) and it would always display 0 pics/videos and 0 folders even though I've downloaded and even took some pictures.

-Online videos couldn't be played cca. half of the time, both stock and Opera browser would give the "Sorry, this video could not be played" (or something like that) error on Youtube/Vimeo/anyothersite.

I've reported this in my ROM's topic (Archidroid 2.5.1) and the main dev (JustArchi) sad he's not fond of F2FS since it causes too many (even unvisible) issues. I've decided to go back to ext4 and I can say that all my problems are gone now.

EDIT: +1 on the black themed aTweaks. Not big a deal but it would be nice.
[Galaxy S III Android Development] torsrex:
I just did some tests on the benefits of undervolting (since I saw you wouldn't consider adding it until someone did some tests on it).

So, here's what I did:

First I fullwiped the phone to f2fs using your modified recovery (system, cache, data (including sdcard) and preload). Then I flashed a fresh copy of archidroid. I chose devil kernel, 300 DPI, nova launcher, google keyboard and unchecked ArchiDroid OTA, Xposed framework, Update modem, titanium backup, greenify, lmt, mxplayer, betterbatterystats, cooltool, root browser, add build.prop tweaks and fix camera. Under bloatware, I only kept my files, samsung keystring and other, checked. I also did not enable swap of any kind.

After first boot, I skipped the setup wizard (meaning, I did not add any wifi networks, nor did I add any accounts). I also turned off wifi, screen rotation, auto sync, gps and put the phone on silent and in flight mode. Then I went to the settings and made sure nfc, sbeam, all the smart functions and those motion thingies were off. Next I went into display and turned on display battery percentage and turned off auto adjust tone. I then let the phone settle in for 20 minutes.

After that, I opened deviltools and disabled "touch boost status". I also made sure swap wasn't enabled. I then installed setcpu and stabilitytest v2.7 from a local copy on my external sdcard.

Within setcpu I set the governor to performance and the max frequency to 200mHz (I originally intended to run the tests at 1400mHz, but termal throttle kicked in and kinda ruined the test results, since it kicked in at different times when comparing uv to non uv tests). I then put the screen brightness to max and waited for the phone to fully charge. Immediately after I got the "fully charged "notification, I took it off the charger, opened stability test and ran the classic test till the battery dropped down to 5%.

It's also worth mentioning my device has an asv4 chip inside of it and that I kept the ambient room temperature at a constant 28 degrees celcius. The non uv-voltage for 200mHz on my phone is 900mV and the uv voltage is 713mV.

I ran these tests a couple of times and took an average. I inititally thought of providing battery graphs too, but I fullwiped again before I remembered to copy those graphs off to my computer.

While using uv, my phone lasted 5 hours 22 minutes and 53 seconds, before it hit 15 % and a total of 5 hours 51 minutes and 51 seconds, before it hit 5 %.

Without uv, my phone lasted 5 hours 3 minutes and 47 seconds, before it hit 15 % and a total of 5 hours 31 minutes and 12 seconds, before it hit 5 %.

Judging from this, I think it's safe to say there is a benefit from using undervolting. Around 19-20 minutes more definitely is worth undervolting in my opinion. It's still up to you whether you want to add that feature or not. ^^
[Galaxy S III Android Development] vyp54:
You are talking about Archidroid 1.x?

When i formatted /system to F2FS Archidroid 2.x wouldn't boot niether on Archi's or Arter's kernel. :confused:
[Galaxy S III Android Development] torsrex:
Yes, these tests were ran on ArchiDroid 1.7.16 STABLE. I haven't personally tested ArchiDroid 2.x, but I could give it a go and see if it boots for me.
[Galaxy S III Android Development] DualJoe:
Still the old bugs... Thanks for confirming they are still valid.

http://xdaforums.com/showthread.php?p=52107673#post52107673
[Galaxy S III Android Development] Mostafa Wael:
[MENTION=5314272]Darkened_Sky[/MENTION]

i found an idea that is a bit not important but it may be useful

can you add a command in your script to tell the status and information about the 2nd ROM

i mean the name or the android version.

in the old glorious days of siyah kernel when we used the built-in recovery there was an option to show the status of the 2nd ROM; if there is a 2nd ROM installed and something like its name and android version and "fingerprint"

how do you think?

just an idea
[Galaxy S III Android Development] Darkened_Sky:
done. script updated in this post.
[Galaxy S III Android Development] Mostafa Wael:
thanks mate. you rock :good: :good:
[Galaxy S III Android Development] lsalamun:
[MENTION=4898097]arter97[/MENTION] great job mate, i am currently testing your kernel for couple of hours and it's great, i'll decide to move on here if battery is close to boeffla, nevertheless your keren has a bright future, thanks for support! :)

Just one more thing, please patch your kernel so it can read patched modems without flashing init.d script to read them, boeffla has introduced that patch inside his kernel, maybe you can talk to him, this would be great so i don't have to flash init.d script over and over
[Galaxy S III Android Development] vyp54:
You can do so for your own liking because I'm done with F2FS, it caused way too many issues for me.

---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------

Battery should be better since this kernel is Samsung Update 13 based. With moderate usage on boeffla I would get cca. 3h screen time, and with arter97 I can get 4h+.
[Galaxy S III Android Development] lsalamun:
Isn't Boeffla 5.3 also update 13?

And depends on usage, with zzmoove moderate i get about 4:30 screen time (no gaming of course, just web, social).

But i am very curious about results in a few cycles.
[Galaxy S III Android Development] snow:
Will you integrate r4p0 driver (for Mali) in your kernel? :) I saw you already tried, but maybe some progress meanwhile? :)

Best Regards and Keep Up The Good Work! ;)
[Galaxy S III Android Development] torsrex:
I did not experience any issues using f2fs with arter97 kernel and archidroid 2.x, I cannot see how it's causing so much trouble for you, I've been running it since derteufel1980 first implemented it to his devil kernel and have yet to notice any. http://goo.gl/HW7L7I http://goo.gl/PC5Ctm

Archi's kernel won't work with f2fs, because it does not [currently] support f2fs.
[Galaxy S III Android Development] SaschaKH:
I think 5.x, 6.x and CM11ng are, but CM11 and OMNI not.
[Galaxy S III Android Development] vyp54:
Sorry, I forgot to mention I'm using AOSP based ROM. arter97/Archi kernel are Samsung based but can work on AOSP ROMs too. :)

---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------

I had trouble booting while /system was on F2FS but I resolved that later. What I did not resolve was mentioned all around issues that rendered my phone unusable for daily (or any other) basis. F2FS is an improvement, I confess that, but It's not so great that I'll be missing it. :rolleyes:
[Galaxy S III Android Development] Mostafa Wael:
hey guys,

so now i finally installed blekota s5 beta 5 as 2nd ROM using secrec script. but i noticed that it is always stuck at 1400 MHz "The maximum freq"

and also i encountered that sometimes after a while when i tap on the power button to wake up my device, it responses but the screen lights up with a black screen. the proof that it was responsing is that when i held the power button for 8 sec to restart, it vibrated..

Anyways, i noticed this bug only with blekota ROM and not with previous ultimaROM, and to be more specifically, after i restored

SOME

of my apps using helium. i tried to fetch a BBS log but when i installed BBS as a system app as required, it failed, and it was unusable. Kernel Wakelocks were not displayed, and there were no suspected Partial wakelocks. the longest time for a partial wakelock was only 25s "RILJ1"

so,...

can anyone help me with that?? is it a ROM issue? or restoring the apps was the issue? (mind that when i used ultimaROM as a 2nd ROM and restored the same apps, which were a total of 65 apps, nothing strange like this happened. it was also the same settings of the kernel used in aTweaks)

i have deleted the 2nd ROM now but for sure if you needed any logcats, I still have the ROM.zip file so for me it is easy to revert back.

Also if there is anything that need much more details and accuracy tell me

Meanwhile I will try to download another TW 4.4.2 ROM. Maybe it's ArchiPort turn now

About the pegasusq+ vs pegasusq comparison I noticed that the stock pegasusq is better in gaming and specially with this sched_mc setting turned off.

That's just for starters, I will investigate more soon.

I just noticed that pegasusq had an extra option than the pegasusq+ governor in aTweaks.. This "I/O is busy" option, which, as written in the app, improves system responsiveness. does that has any negative effect on battery life??

Thanks and waiting for the next mighty 2.1.4 version

Ahh also i will be very thankful if you let me know the progress done in the search for the root cause of a bit low graphical performance.

I wish you reached it and fixed it in a beta 2.1.3.x version :)

Thank you!
[Galaxy S III Android Development] lsalamun:
Ooh, then your battery life is really good :)

Till now, everything is great in this kernel, i just love the advanced mDNIe settings, just the patch for reading patched modems and it'll be my daily driver. :good:
[Galaxy S III Android Development] habylab:
RIL is a crappy android issue, will be gone in Android L.

Yes, it will be less battery that option, as read and write operations cause the CPU to ramp up. But, I'd say the trade off is worth it, depending on use.

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] Mostafa Wael:
so you suggest not to turn the "I/O is busy" option on? also do you suggest to use PegasusQ or PegasusQ+?

thanks?
[Galaxy S III Android Development] arter97:
Will keep this in my mind. Thanks for testing.
[Galaxy S III Android Development] arter97:
I really don't want to touch anything related to radio since I don't own an i9300. I don't want any users to experience radio/efs outage just because I did something stupid and did not test enough.
[Galaxy S III Android Development] arter97:
I'll try out that later, even if I do make it working with i9300, it'll probably not work with Android 4.3.

So, this is not on my priority list :(
[Galaxy S III Android Development] arter97:
AndreiLux's Perseus kernel does not has io_is_busy option(he removed it).

But it exists in the stock kernel and the stock value is actually "on". So I left it for the users to choose.

My recommendation is keeping it to "on".
[Galaxy S III Android Development] lsalamun:
I could be your tester for that, no problem, in fact this 'kernel patch' that is integrated into Boeffla cannot harm the radio/efs/phone in any way, if you can, please consult with [MENTION=1045701]LordBoeffla[/MENTION] about that, it could be great, Agni kernel has also that implemented i think, that patch is just for reading the patched modem, it bypasses signature verification for patched modems or something like that, it cannot harm users that don't use patched modems. :)
[Galaxy S III Android Development] Mostafa Wael:
so now i feel that PegasusQ is the right choice now! ??

as for sched_mc value, i suggest to turn it to "0" if you are in gaming and to "2" if you want a balance between battery saving and smoothness
[Galaxy S III Android Development] arter97:
Then let's wait for a reply...?
[Galaxy S III Android Development] arter97:
Are there any benchmark differences between sched_mc?
[Galaxy S III Android Development] lsalamun:
Yes, currently Andi is not available he is moving his home or something like that, when he'll be available you or I can send him a pm to see what can be done, then you can push me the test release and i'll check if it works correctly and i'll let you know :good:

One more thing, can you please let me know what are the benfits of Firelock i.e. what does it actually do?
[Galaxy S III Android Development] Mostafa Wael:
will make some benchmark tonight.

currently i am not at home..

now i am running with PegasusQ and sched_mc=0 and I/O is busy set on and i feel the device is performing better and there is no hit on the battery

when i am home tonight i will test with PegasusQ stock and sched_mc=0 one time then leave device for 5 minutes to lower temperature then test again with sched_mc=2 and will report the difference
[Galaxy S III Android Development] arter97:
Read the OP for Firelock.
[Galaxy S III Android Development] Angeloo95:
I installed the kernel of jamming very obvious how to solve?:(
[Galaxy S III Android Development] lsalamun:
Can you rephrase the question? What is your problem?
[Galaxy S III Android Development] Mostafa Wael:
so now i ran the benchmarks tests and i see that:

with

SCHED_MC=0

there is an obvious increase in Multitask / Runtime / CPU Float-point / CPU integer for around 500-800 points each

anyways the overall score was increased only 150 points as there was a slight drop in the rest "which is not a thing to look to"

pictures of the test runs will be attached tomorrow....
[Galaxy S III Android Development] lsalamun:
That is very low to even consider increase/decrease of performance, when i run 2 tests each agter another they can differ 500 points, for me, benchmarks are really not here to measure the performance:)
[Galaxy S III Android Development] Angeloo95:
lag and jamming system:(
[Galaxy S III Android Development] Mostafa Wael:
so you mean that this ~~500 difference in the CPU operations in the benchmarks is nonsense? okay

but i am having best battery life with PegasusQ "stock one" and minimum freq is 200 MHz not 100 MHz and "I/O is busy" set on and Sched_Mc is set to 2. it is a bit laggy but it is okay for me as long as it is better for battery life.

as for the PegasusQ vs PegasusQ+ battle, IMO PegasusQ is far much better in terms of battery life, and multitasking is very slightly better with PegasusQ+ governor, however PegasusQ performs far much better in gaming though

Conclusion

PegasusQ wins PegasusQ+

-->Notes<--

Sched_mc was set to 0 in both governors

in PegasusQ, the "I/O is busy" set on, as it is the default in stock kernel, according to [MENTION=4898097]arter97[/MENTION] quote.

Hope that i helped :D :highfive:
[Galaxy S III Android Development] Mostafa Wael:
getting more detailed in this point to clear out any confusion and describe my point of view;

when using 200 MHz as minimum frequency and leave screen on at home screen with the same governor and CPU settings, it jumps only from 200 MHz to 300 MHz and it is rarely also.

But,...

when setting 100 MHz as minimum frequency it keeps jumping more continuous to higher frequencies like 500 MHz or even 800 MHz

just lile this pattern: 5 steps to 1 high step

so what you think guys?

this is done with the help of CoolTool - for system stats
[Galaxy S III Android Development] lsalamun:
How about zzmoove moderate vs pegasusq?

---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------

Try changing your governor zo zzmoove in aTweaks and profile to moderate in zzmoove tab, apply and see if it makes difference.
[Galaxy S III Android Development] Mostafa Wael:
interesting :)

will do tomorrow....
[Galaxy S III Android Development] habylab:
Yes, would be interesting. This kernel doesn't have the improved beta version of zzmoove either!

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] Mostafa Wael:
excuse me for being a bit silly, but what do you exactly want/mean??

no offence :D
[Galaxy S III Android Development] habylab:
Just saying zzmoove has been improved since this last kernels release! But still a beta version, that is found in boeffla and Archi.

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] Mostafa Wael:
i really got confused with archikernel's releases. :confused:

i will wait till next archikernel version.

---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------

hey guys i want to ask,

when i charge the phone while enabling the "ignore unstable power" option i feel that the phone gets discharged faster

but when charging normally, it charges slower but battery life is far much better.

is that correct?
[Galaxy S III Android Development] max20091:
Yes, that is true. Fast charge make your phone hot and the battery will discharged, don't turn on ignore unstable power or your battery may explode :p

Tested by using an ipad charge and exploded when turn on ingnore unstable power
[Galaxy S III Android Development] max20091:
Is there any tips to improve battery using without lag? The screen eat so much battery.

Edit: just normal using like calling, browsing, not playing games or benchmark etc...
[Galaxy S III Android Development] szotaa:
Remove screen.

PS. Thats true
[Galaxy S III Android Development] max20091:
So what about kernel tweaks, any idea? Like set CPU governor, I/O governor, etc...

I found the problem, knock-on features eat my battery so much :D so I decide to turn off this.
[Galaxy S III Android Development] lsalamun:
Oh my, this has been answered like zillion times, try, test, try test, and...try. test.

Start with zzmoove/moderate and bfq/cfq/row/zen, they are quite snappy and battery friendly.
[Galaxy S III Android Development] Mostafa Wael:
my settings are as follows for those who cares:

Governor: PegasusQ

Sched_Mc: 2 as recommended

CPU scaling: 200 MHz --> 1400 MHz

extra tweaks for governor: turn "I/O is busy" on

I/O scheduler: noop & noop

Read-ahead: 256 & 512

Dynamic Fsync: on

Screen settings...

MDNIE scenario: UI

MDNIE Mode: Standard

Sharpness Tweak: enabled

zRAM: 150 MB

That's it!

with this setting i got 4 hours 24 minutes, usage was net-surfing, chatting, gmail, music playback, video playback and 35 minutes gaming "angry birds Go! & Fish out of Water"

[MENTION=5161352]JustArchi[/MENTION] Congratulations for being a Recognized Developer, wish you the best :good: :victory:
[Galaxy S III Android Development] max20091:
I have some question:

1. Why arter97 not set CPU speed from 100Mhz?

2. Is the most stable kernel is 2.1.2? (on the first post)

3. Does TRIM support on F2FS, If yes, how I can do that? Lagfix can't do that.
[Galaxy S III Android Development] arter97:
It varies from the charger. Get a good quality charger. I personally recommends Apple's official iPhone or iPad charger.
[Galaxy S III Android Development] arter97:
LoL bro.
[Galaxy S III Android Development] arter97:
1. Some "many" phones cannot handle 100 MHz.

2. 2.1.3

3. Trim is automatically enabled on f2fs with kernel side implementation. My kernel has also enabled trim on ext4 too. No need for LagFix app with my kernel.
[Galaxy S III Android Development] Mostafa Wael:
so you recommend to use an iPhone charger and don't turn that option on?

Honestly speaking i am a bit afraid now...
[Galaxy S III Android Development] arter97:
Yes. If you're in an emergency, turning on that option wouldn't matter much since iPhone charger is very good(and the actuall iPhone charges with its full current)
[Galaxy S III Android Development] max20091:
Normal USB port on PC: 0.5A

New Gigabyte or Asus USB port: 0.8 to 1A

Normal wall charge or iphone charge: 1 to 1.2A

Fast charge: 1.5A

Ipad or Tablet charge: 2A

You need to change from 1000 mA to 1500 mA in the setting.
[Galaxy S III Android Development] arter97:
Bro, stop giving everyone false information.

iPhone 1st generation ~ iPhone 5s is using 1A.

iPads newer than 2nd generation(beginning from 3rd generation; Retina display) are using 2.1A.

Recent generation motherboards > 2010 : 1A ~ (for external hard-drives)

Recent USB 3.0 motherboard > 1.5A ~ (for external hard-drives)

Old generation motherboard : Galaxy S3 can dynamically reduce charging ampere and matches the output of the motherboard.

Recent generation motherboards, iPhone, iPad charger : Galaxy S3 is happy and charges with 800mA(for extra threshold of safety). User can safely attempt to bring it up to 1A and its charging speed is very fast.

No need for 1.5A here :

1470mA is the max charging current recommended for our S3.
[Galaxy S III Android Development] max20091:
sorry, Im not edit my post yet because using a 1 core tablet from 2010 :p

Ipad 2 or older 2.1A, Ipad 3 or newer 2.4A

2.0 USB port: 500mA

3.0 USB port: 900mA

custom USB port (can found on newer gigabyte or asus motherboard): 1 to 1.5A

some external hard-drive model are using dual cable so it start at 1A to 1.5A:p
[Galaxy S III Android Development] vyp54:
I've tested many chargers on S3 and I've found out no matter what the charger says (1A, 1.2A, 1.5A or 2A) they all charge the same (+/- 5 to 10 percent). I've tried to charge it with my Note 10.1 2A official charger and the result was the same. There were also 220V and 12V chargers in the game. No matter what you put it on - the phone will always take the current it wants. Measured by Boeffla app and an ampermeter tool.

I've also split a USB cable to plug it directly into the tool too see if there is any difference in current while no device was attached. I got 0.65 to 0.7A on every charger I tried. So the conclusion is - set your charging rate between 1000mA and 1470mA. I've set mine to 1300mA with stock charger and it charges really fast. There may be a safety concern since S3 stock charger outputs 1000mA (says on the label) but I've had no problems so far.
[Galaxy S III Android Development] max20091:
Are you change from 1000 to 1300mA in atweaks? I think "ingore unstable power" like apple fake charger detector:p

And if I'm stuck at 2nd rom, how I can get back to 1st rom? Many users using SHV-E210K/S in XDA ask me about this.
[Galaxy S III Android Development] vyp54:
Yes, I changed to 1300mA in aTweaks + ignore unstable current + ignore safety margin. The current is 1300 all the time just like I want it to be.
[Galaxy S III Android Development] Mostafa Wael:
i think you can reflash the kernel, as it resets aSwitch so it is possible that it will force the phone to reboot to 1st ROM.. maybe arter can confirm that.
[Galaxy S III Android Development] jasonjdm:
More Smoothness and Audio refinement required

Hi arter97,

Thanks! for such a wonderful kernel. I'm using it on my SHV-E210K. I was testing this kernel as compared to Boeffla Kernel for 4.3 and 4.4.2 TW roms. I think in this kernel there is slight lag/glitch while using with the TW UI, also some audio tweaks required to make the music sound better on headphones. Would you please try to optimize it.
[Galaxy S III Android Development] Mostafa Wael:
1) you can use Boeffla sound app to enhance your audio quality

2) our dev is aware from the slightly poor graphical peeformance and is trying to fix it, but mind that TW 4.4.2 ROMs are out of comparison, even ArchiKernel which was supposed to be dedicated to it has some slight slight graphical glitches.
[Galaxy S III Android Development] MD500:
Arter97 recovery are based in philz touch recovery with latest version?(including f2fs tools?) will work with every kernel? If not which kernels?(arter97 and AGNI i mean?)

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] Mostafa Wael:
i think so...

well i didn't try it yet, and i don't think i will try it with another kernel :D