yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] hieupham:
Dear Boss,

I'm currently running Wanam 2.1 + flash manually LH1 modem + SpeedMod 1-6 Finale

Like the combo much, nearly no freeze and problems at all, on screen time is 4h+, 3G on - not best stat but is ok for me.

One very nice thing that I like about SpeedMod kernel is that they are not UV, OC etc etc, just lot of tweaks and also the most nice thing is that the colors are fixed (less over saturated in compared to the stock settings) and also the brightness settings.

Would like to ask - are the colors and brightness settings are included in your kernel?

I have not tried ur kernel yet but my friends did give positive feedbacks regarding 3.8 and not very good regarding 3.9beta1 as it's way hotter while the 3.8 has excelent bat. life and surprisingly COOL ! ^^

Thnx! :good:

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

As for me I can say that stock max brightness in Galaxy Note > Galaxy S2 > Galaxy S3 (the darkest one!) , so I'd say to leave the tweaked brightness because in some situations you'll defnly need MAX brightness (oh man the screen sucks badly under direct sun :cowboy:)

Imho the auto-brighness is handling quite well.
[Galaxy S III Android Development] harunjo:
hmm maybe i will create a voting for this..how about that guys?..after 2 weeks then we will know the result.
[Galaxy S III Android Development] hieupham:
The brightness yes for vote , no problem.

I like the colors tweaks so they become less-saturated and more naturally, all the stock SS tweaks are OMG! :eek:

And btw when the screen is less saturated you may not see the deffects (like the tint, let's say) or they become less visible lol :D

Regarding the targets of a good kernel as most peeps from my country (Vietnam) are:

- long battery life

- cool device

all other bonuses (like Voodoo sound etc etc) are subjective and all can live without them :good::D
[Galaxy S III Android Development] harunjo:
Temporarily for those who really need that brightness and sharpness tweak..then you can use v3.6..i think that version still stable for the last ROM

personally i hate that brightness tweak, I was always slide it to lowest brightness value...btw lets vote!
[Galaxy S III Android Development] korrel2008:
BTW nice signature you have Harunjo !
[Galaxy S III Android Development] ph3nom:
instead of vote, is it better to create 2 version?

I found my s3 auto brightness too dark during low light situation.

So i vote yes and maybe you can customize the auto brightness a lil to make it not to bright?

However, I like Hardcore sharpness.

Thx.
[Galaxy S III Android Development] MuertoKo:
+1 to this!

Too much brightness... maybe you could try it a little less bright bit still adding it? Who knows...

About sharpness that's a great tweak and improve experience while has null impact in battery life :)

Will try latest beta as soon as I reach home (GPRS connection sucks hard...)

Keep hard work harunjo! We all enjoy it :D
[Galaxy S III Android Development] spencer1208:
I totally agree with Andi.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] harunjo:
dude..that will waste my energy..as you can see , a lot version i must create before releasing it..but i really appreciatte your idea..
[Galaxy S III Android Development] samaxen:
I prefer stock brightness, but colour tweaks from hardcore to remove saturation is also good.
[Galaxy S III Android Development] ph3nom:
Sorry about that, well voting it is then. ;)
[Galaxy S III Android Development] hieupham:
would like to ask is the color tweaks (de-saturation) already applied in the kernels?

If yes then if I'm running Wanam 2.1 (LG9) + manually flashed the new LH1 + speedmod 1-6 kernel so I'm oke to flash the 3.6 -> 3.8 kernels?
[Galaxy S III Android Development] harunjo:
v36 is the latest galaxsih kernel who have that brightness and sharpness tweak from hardcore..

starting from v37 and the latest v39-beta-3 no tweak from hardcore..

if you come from different kernel then i suggest you to wipe cache partition and dalvix.

but if you come from same galaxsih kernel but different version..then no need to wipe..

basiclly just flash any kernel..if you feel funny behavior on your phone after flash it and then do wipe

BTW

Poll System have been create for that hardcore tweak

maybe i must change this kernel name to "Democracy" kernel, LOL (hmm good idea)
[Galaxy S III Android Development] harunjo:
no need to say sorry dude..no rules here, say anything you want to say..no newbie, all user is expert here LOL.
[Galaxy S III Android Development] hieupham:
Thnx! I like the desatured and more naturally looking colors much more! Yay! :D:good:

Btw the new toy is coming along with the expected Note2 :fingers-crossed:

According to the guys of GSMArena Samsung will update the Galaxy S III to Jelly Bean on August 29th.

We of SamMobile reported this sometime ago already.

Samsung is waiting on the certification of Jelly Bean by Google but this looks fine.

If everything goes by plan, we will see the first Jelly Bean updates for the Galaxy S III by the end of August.

Samsung will try to release this update the fastest way as possible.

In the first place Europe and Asia will get the update.

You will be able to use OTA (over the air) or Samsung’s own update program called KIES or of course ODIN for the diehard flasher!

Make sure you keep your eyes on our website or on one of our twitter channels.

http://www.sammobile.com/2012/08/14/jelly-bean-for-galaxy-s-iii-end-of-august/
[Galaxy S III Android Development] harunjo:
and then i will stop work until samsung release their JB kernel source lol
[Galaxy S III Android Development] hieupham:
right haha, vote poll for 2 weeks as you told us before and in 2 weeks the BIG event from samsung lol :p:p:p

i think that the de-saturation feature is a top-notch and should be applied in every kernel, as of brightness the poll results will show ^^

btw u'r one of very few devs that answers this quick and almost to every post from the followers, starting to like you and about to flash the kernel to stay connected and update the testing experiences :good ::D unf. i'm in VN so no paypal system in here for beer :victory:
[Galaxy S III Android Development] harunjo:
see the vote due date dude..i already state 7 days from now...so you can have the vote result soon...1 week before JB :laugh:

and also i dont like paypal and beer..i only drink glenlivet for weekend only
[Galaxy S III Android Development] Sad56:
For me i don't care of hardcore mod :p

Kernel is ok like he is.

I prefer one who's smooth, speed, and battery friendly.

Like your's :thumbup:

Also criskelo rom integrate bravia engine mod. Screen and brightness is ok in this amazing phone. Don't need more and more tweaks in my opinion.

And finally I think all this mods being dead and new coming with jellybean. ;)

Envoyé depuis la galaxy Addict via Tapatalk
[Galaxy S III Android Development] philliplavelle:
Weird CPU issue

I've been watching this thread for days and just decided to install your kernel v3.8 because of all the good reviews.

I'm running Wanamlite and was using Phenomenal 3.0 (normal). When watching my phone using CPU Spy, it rarely used to use 1.4GHz and tended to stay around 200MHZ/500MHZ when listening to music etc.

Since installing your kernel, it seems to be permanently at 1.4GHz - even when the phone is either not being used or is being used for light, basic tasks. Is this normal?

Thanks

PS. I should point out that I am running modem XXBLG9.

---------- Post added at 07:36 PM ---------- Previous post was at 06:54 PM ----------

My apologies.. my modem is XXLH1. My bad.

Just to follow this up, the phone does eventually go into a deep sleep mode after a while but is also going into full 1.4GHz mode very easily.

It doesn't seem to get too hot but I just worry if having it in almost constant 1.4GHz mode is bad for it ultimately and will do any damage.

Sorry for all the questions.. I'm new to the world of installing custom ROMS and kernels :)
[Galaxy S III Android Development] harunjo:
dear philip..i suggest you flash v39-beta1 if v38 is not work for you..also go to recovery and wipe cache partition and also dalvik cache.

s3 cpu can go to 1700, and actually have 1500 mhz max..its been underclock by samsung to 1400 mhz, do not worry too much..you will only lost battery life if you always get max speed..but for me its also not normal if your cpu never have a deep sleep..so again please do wipe.
[Galaxy S III Android Development] philliplavelle:
Thanks.. I did do that but I'll try again with the beta
[Galaxy S III Android Development] walda:
my voteing:

important:

battery life

smoothness

cool device

unimportant:

brightness/color tweaks

sound tweaks

:)

... tapat*lked
[Galaxy S III Android Development] spencer1208:
Hello harunjo.

Just reflashed my phone from scratch.

I am missing the sdwatcher binary tweak in v3.8 kernel and i believe some earlier version too.

Is this tweak still applicable and if yes can you please provide binary.

Please advice. Thanks in advance

Spencer

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] harunjo:
as far i know , most custom rom already include that tweak on their rom..but i will also attached that file to first page soon
[Galaxy S III Android Development] harunjo:
please vote using xda web version bro..that pooling system is not worked with tapatalk or xda app
[Galaxy S III Android Development] hieupham:
And btw I want to ask - after shutting the screen off and after a while on again, it takes like 2 secs for the screen to turn on into the lockscreen (with water ripple effect) - is that normal? I have read several sources saying this is caused by the special design of the Exynos CPU

I can see the HTC devices (from HTC Desire to HTC One X that I've chances to test) turn on instantly, even the S2 turns on the screen very fast.

Any ideas?
[Galaxy S III Android Development] harunjo:
you could try 39-beta4...if that behavior is still exist, than maybe its native exynos behavior.
[Galaxy S III Android Development] 6pudu5:
I was distracted a moment :laugh: and is already arrived a new beta :good::good:

Great Job harunjo. Thank very much.
[Galaxy S III Android Development] harunjo:
hi 6pudu5 welcome..i think this is your first comment here..so far i only see your thanks without your comment lol
[Galaxy S III Android Development] harunjo:
dear spencer,

you can download sdwatcher binary from this thread first page.
[Galaxy S III Android Development] 6pudu5:
@harunjo, don't write often, but i had already commented on, see #39 ;), among the first to use your work :good:
[Galaxy S III Android Development] spencer1208:
Thanks a lot.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] hieupham:
Even after disabling the S-Voice app ("Samsung Galaxy S III tip: disable S Voice for better home button response") the screen would not turn on instantly.

Will try your brand new kernel now :D

Btw I find that Fruit ninja is not very fluid and smooth in S3 in compared to HTC and even s2 - there is for sure some latency in S3 and the "cuts" are not blade-smooth :D For example once you start the game and choose game mode (for example: "Classic") to start the game, the 1st fruit and bomb that opens the game will hang (freeze) for like 1 second, after that they drop off and the game begins , doh :D

---------- Post added at 08:39 AM ---------- Previous post was at 08:25 AM ----------

As for me I really care about the color tweaks (sharpness and less-saturation), not that much care about brightness.

Because the stock colors of S3 is ok, maybe the colors POP-out yes but I don't like in some photos peoples skins are way tooooooo red = lobster skins :D = not natural

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

I have just flashed your kernel and I believe this is native Exynos behaivor coz its the same, taking 1-2 sec for the screen to turn on. Will shoot a feedback of 3.9beta 4 soon.
[Galaxy S III Android Development] MuertoKo:
No lag here using this kernel beta 4 :)

About the unlock lag, yes it is there for all S3.. hope some device could sort it some day! For me most annoying issue on S3 so far...
[Galaxy S III Android Development] harunjo:
how about network speed? are you notice some improvement there?
[Galaxy S III Android Development] ongchonghian:
dude, you are crazily fast in dishing out betas ;) i remembered flashing your 39b3 just this morning, before leaving for work.

Anyway, my personal take on 39b3 is this: it does not conserve battery as well as 3.7 or 2.6p. i am typically at the 60-70% mark (which translate to about 2 hours 15mins of screen on time) on a normal work day at about 1800HRS. However, my day today on 39b3 drops to about 40% (around 2hours 15mins of screen on time as well) at about 1800HRS.

Will give 39b4 a go tmw. No news is good news from me :)
[Galaxy S III Android Development] hieupham:
I mean some lag at the beginning of the game Fruit Ninja, not while using the fone :P
[Galaxy S III Android Development] jothi2lingam:
Using galasih 3.7....No lag at all playing fruit ninja
[Galaxy S III Android Development] samaxen:
Same for me, I feel 3.7 was the best till now. Though 3.9b1 was very good.
[Galaxy S III Android Development] walda:
oops, didnt see it. done. :good::cowboy:
[Galaxy S III Android Development] harunjo:
sorry for rush update, i just cannot stand, if there something did not go well .
[Galaxy S III Android Development] ph3nom:
I love it when you update your kernel and there is something new, you explain it for those who don't understand it. appreciate it Harunjo, Keep up the great work.

Downloading the new Beta

My review for beta 3: it seems battery drain not very good on this one, i lost about 9% when i left my phone for 8 hours. I said this because when i use siyah i can get away with 5-6%. (don't want to compare your kernel to other kernel, it just an input for next improvement)
[Galaxy S III Android Development] harunjo:
the beta version is experimental version for me..thats why your critics , suggestions and usage report is important to me..after all beta is out (usually 4 beta version have been released)..then i will release the stable version..who can be flash by all users.

beta version is only flash for those who willing to try and feel each steps of kernel development..and you can test it together with me..so beta have very2 dynamic situation and feel.

thats why i always give credit to beta tester here...your review is very important for stable release. :good:

my v39-beta4 review:

CPU behavior almost same like 39-beta1.....standby is good...lost about 4% , device standby for about 6 hours without no activity, 3G connection is always active..

after that 6 hours of standby, i was use my phone quite heavy..now my battery is 42% left , screen on record is 3 h 27m and 37s..

total this devices operating for about 14 hours , 14minute and 12 sec.

i see improvement for network speed..specially when browsing...
[Galaxy S III Android Development] diddsen:
@harunjo

why using only sio?

and uv... what mv you set?

---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------

ok, uv i see on v3.4 changelog ;)

i testing now beta4... so far looks good

only smoothness i find the stock the best.

---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------

btw... i use wanamlite and he implement a script for kerneltuning.

he said that compatible to other kernels... what do you think about?
[Galaxy S III Android Development] samaxen:
I agree with you 3.7 was the best, though 3.9beta1 is also good.

Though testing beta4 now
[Galaxy S III Android Development] harunjo:
because SIO is best for battery life..alot discussion here, find couple page back from here.

and about wanam tweak..you can find this tweak script at /system/etc/init.d

v37, 39beta1, 39-beta4 = 85

Samsung stock = 85

up_threshold - Measured as percentage, this is the load on CPU at which governor scales CPU Up. Lower value - early scale up, and vice-verse.

UNIT: Percentage

my value for 37, 39beta1, 39-beta4 is: 50000

Samsung stock is also 50000

sampling_rate - Measured in uS and actual meaning being Sampling Interval, this factor is used to determine how often the governor should poll for CPU usage in terms of frequency and load percentage to make scaling decisions - either scale CPU Up or scale it Down.

UNIT: Miscroseconds

v37, 39beta1, 39-beta4 = 2

Samsung stock = 2

sampling_down_factor - Acts as a multiplier to sampling interval for re-evaluating the load when CPU is truly busy and is on highest clock frequency (policy max). Setting to 1 makes no difference and causes CPU to immediately scale down from highest frequency. Sampling down factor is not valid for lower frequencies and low load conditions. Note that CPU is scaled up to max frequency when max_load_freq is greater than up_threshold*current frequency. (or to cur_freq + (freq_step * policy.max_freq) whichever is smaller) Max_load_freq is an arbitrary frequency calculated as the maximum of load_frequencies. Load_frequency is an arbitrary frequency which describes the frequency the device theoretically needs to handle 100% load, calculated as load*average_frequency.

UNIT: Positive Integer

Samsung stock value is 5

v37, 39beta1, 39-beta4 =5

down_differential - After spending sampling_down_factor*sampling_rate micro seconds at maximum frequency on high load, governor samples the load again to calculate an approx target frequency to scale-down-to which should not trigger up_threshold in the next sample. (Triggering up threshold may cause jumping to max frequency again). Down_differential also act as the factor which prevent aggressive scale down. Max_load_freq is checked against (up_threshold - down_differential) * current frequency. If found to be smaller, CPU is scaled down to a target frequency as described above.

UNIT: Positive Integer

about

setprop pm.sleep_mode 1

and

ro.ril.disable.power.collapse

since i dont deal with those tweak in kernel..you can compare them to stock build.prop value..

pm.sleep_mode=0 -> Power Collapse Suspend

pm.sleep_mode=1 -> Power Collapse

pm.sleep_mode=2 -> Apps Sleep

pm.sleep_mode=3 -> Slow Clock and Wait for Interrupt

pm.sleep_mode=4 -> Wait for Interrupt
[Galaxy S III Android Development] MuertoKo:
Can't test properly on speed now as I'm on vacation on a poor coverage zone, but for now it's working nice and fast so maybe due to beta 4 update :D
[Galaxy S III Android Development] jothi2lingam:
Harunjo v3.8 beta4 look better... But can you increase bit the smoothness... Bcos slightly lag sometimes when swiping home screens...... Battery not tat gud as in v3.7
[Galaxy S III Android Development] diddsen:
can confirm... smoother is stock (scrolling)

i concrete tested by switching to stock.
[Galaxy S III Android Development] harunjo:
check your rom tweak first..i didnt got lag when using beta4.

maybe in the future i will remove totaly undervolt from kernel and let see how it will perform
[Galaxy S III Android Development] jothi2lingam:
I'm using Foxhound 1.4.3. Where to find the rom tweak bro
[Galaxy S III Android Development] harunjo:
read my post here:

http://xdaforums.com/showpost.php?p=30248961&postcount=750

my battery is great here with v39-beta4 using wanam lite ROM with some of that rom tweak removed
[Galaxy S III Android Development] jothi2lingam:
Thanks..I checked but got text format of 99SuperCharger only.....!
[Galaxy S III Android Development] harunjo:
99 supercharger is have a lot tweak on it..check it and learn how that script will impact on your rom performance and battery

if you unsure..just remove it using root explorer

testing 39-beta5 here ...

with undervolt removed and also init.d support is removed.

so without init.d, i hope it can guarantee there is no excessive tweak after the ROM loading

i will upload it if i found it stable enough for beta version,

i expect this beta5 kernel is more smooth than stock and have better battery life than stock

edit: yes its feel smoother than ever...lets test this beta5 battery
[Galaxy S III Android Development] samaxen:
Bro please don't remove init.d support I am using external2internal tweak with this.

Thanks,
[Galaxy S III Android Development] ongchonghian:
i like that attitude :)
[Galaxy S III Android Development] harunjo:
always mounting your app to external SD is also eat battery alot my brother...

maybe i must open the vote again for this lol

or maybe better to create init.d but only support for that specific external2internal tweak?
[Galaxy S III Android Development] harunjo:
sorry double post
[Galaxy S III Android Development] harunjo:
triple post damnn
[Galaxy S III Android Development] samaxen:
For me I never felt extra battery consumption from the time I used the script with your kernel.

Though I am using other scripts as well such as zipalign apks at boot time. In my opinion It is always beneficial to keep the init.d support :)
[Galaxy S III Android Development] harunjo:
try without it....your phone battery will much better.

btw..modified the init.d script for file in 11* only..other will reject by init.d script

is it ok?
[Galaxy S III Android Development] ongchonghian:
Btw I noticed there is this tweaked sd watcher in celogeek. What's that for? I thought it was already incorporated since 2.6p?
[Galaxy S III Android Development] harunjo:
yes i was removed it..to decrease kernel size.
[Galaxy S III Android Development] hieupham:
After playing with this kernel for a while (beya 4) i have not seen any major problems. May be the pages scrolling are not as very fast and smooth, i think is caused by UV, but in general no problems detected.

Maybe the device is a bit hot when being loaded (yes, for example facebooking with 3g)

Fruit ninja game has latency at the very beginning of a new game for like 2-3 secs

Still testing.
[Galaxy S III Android Development] harunjo:
fruit ninja is light game..it even run smooth wih my old nexus one..so why heavy 3d game like gameloft nova 3 can start without latency...base on that logic..i assume fruit ninja is not running well with our s3 hardware

and for smoothness....UnderVoltage is main problem for smoothness.thats why i will remove that UV tweak for next galaxsih kernel version.

same logic like...you have a ferari car, you decrease its power..and you are expecting for good acceleration after you decrease that ferari power..

you can not get all with UV.

but without UV , i believe its posible to get better battery life and smoothness like stock
[Galaxy S III Android Development] walda:
but without UV... hmm...

maybe you could add support for UV Apps then, so everyone can decide for its own. i would miss the UV thing, i think.

... tapat*lked
[Galaxy S III Android Development] harunjo:
done brother..just wait for brand new v39 concept.
[Galaxy S III Android Development] harunjo:
v39-beta5

v39-beta5 online

-remove fixed UnderVolt tweak default totally.

-add cpu voltage control support so you can adjust your cpu voltage dynamicly,thanks to andreilux

you can use voltage control app from google play
[Galaxy S III Android Development] ph3nom:
Can't change voltage with set cpu. with Voltage ctrl can't change too, after reboot setting won't stick

also, my 1400mhz showing 1212500 mv instead of 1225000mv
[Galaxy S III Android Development] DannySchaukens:
Sooooooo f*cking fast and smooth !!!! Test battery...
[Galaxy S III Android Development] PacketJ:
This is what I'm suggesting from the start. Nice to see this
[Galaxy S III Android Development] jothi2lingam:
Samsung GALAXY S III Android 4.1 Jelly Bean Update Video & Change-log Here http://bit.ly/OYT3rt
[Galaxy S III Android Development] harunjo:
i just missed something..i will fix it later thx for info
[Galaxy S III Android Development] hieupham:
Using Beta4 for 1 day.

As for previous post no major problems detected, my on screen was 2h30++ with 3G and web surfing, FB etc etc, the battery was like 35% so that was pretty OK, after that I went to sleep (3G on, autosync off, apps off)

Today I woke up and the battery dropped to 13 % dunno yet what might caused the problem, might be frequent wakes