yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] nodstuff:
Well ya, I was actually arguing FOR using 400-1400 instead of 100-1000, when I read it back there I noticed I didn't make that point.

Underclocking for me is worse than overclocking, I've felt that way since I had the nexus s. (Ezekeel (really good dev) managed to get deep idle working on the nexus s and did a big write up about race to idle and deep idle and it was very informative, it basically showed that higher clocks are better than limiting the CPU to lower ones) I'll try find it again. Watch this space :D

http://xdaforums.com/showthread.php?t=1297535

This is about deep idle mainly but he talks about race to idle.

I'm gonna try find the one about screen off Max frequency setting for lazy governor which also talks about race to idle.
[Galaxy S III Original Android Development] thyttel:
Yup not working here either!
[Galaxy S III Original Android Development] gokhanmoral:
I noticed that. I unintentionally disabled that one while disabling tuning.

added it back to beta6 just 10 mins ago.
[Galaxy S III Original Android Development] nfsmw_gr:
Yay!Great news!! :D

Did you had any time to check my post about hardware equalizer? :S
[Galaxy S III Original Android Development] gokhanmoral:
I need to cleanup some code to make it possible.

for now, hardware eq will be available only for headphones.

actually, speaker tuning was modifying hardware equalizer parameters, but there are some cases that needs to be handled more carefully. therefore I removed it temporarily.
[Galaxy S III Original Android Development] baste07:
is the download link for beta 6 out already?
[Galaxy S III Original Android Development] nfsmw_gr:
You are awesome mr gokhanmoral!

Thank you so much for your work! :)

As soon i get my new paypal i will donate to you asap! :D
[Galaxy S III Original Android Development] BoneMo:
not yet. wait:cowboy:
[Galaxy S III Original Android Development] gokhanmoral:
I need to test touch gpu boost a little more before I release it.
[Galaxy S III Original Android Development] maddler:
What about that fix for MTP and OSX? I've never been able to use MTP on my Mac, any chance it will work now? :)

Thx!
[Galaxy S III Original Android Development] bmwbasti:
Hi Gökhan,

any idea about the minimum brightness problem?
[Galaxy S III Original Android Development] bala_gamer:
Wow,touch gpu boost? What's that

《tapatalked from galaxy s3》

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------

Gokhan already replied it, unless some one with mac volunteers its not going to happen;)

《tapatalked from galaxy s3》
[Galaxy S III Original Android Development] gokhanmoral:
similar to cpu boost...

I noticed that after fixing gpu scaling down (after resume) problem, people started to complain about UI lags.

they also complain about UI lags when I remove resume freq (it sets gpu clock to 266MHz after idle)

if you set gpu lowest level to 266 all lags are gone.

so, I decided to make an optional parameter to change the freq on touch.

similar to cpu boost, gpu freq will be increased depending on the level you choose.
[Galaxy S III Original Android Development] Yank555:
Nope, have a read here : http://xdaforums.com/showthread.php?t=1814311

JP.
[Galaxy S III Original Android Development] Tungstwenty:
But for this example, what does it mean exactly to have the 34W / 24W / 1W in terms of frequencies?

My understanding is that when the cpu is running at a certain frequency, it will execute stuff until there's no more work. When that happens, it will "halt" (in the case of ARM it will be a "WFI - Wait For Interrupt" instruction) and start consuming the 1W you mention in the example, until some interrupt is raised (clock tick, for instance) and have the cpu resume, execute some more stuff, go back to sleep, etc. - yielding a CPU usage below 100%, and a consumption which is a mix of 34W and 1W.

If now we add DFVC to this, in addition to run/halt/run/halt we'll also have a periodic mechanism that will evaluate the average CPU usage and throttle the frequency up or down, perhaps leading it to a frequency where it only consumes 24W instead of 34W whenever it's not halted.

But this mechanism isn't instantaneous (unlike halting, I think) and therefore there's a latency there that will make the CPU hold a certain frequency for a certain period before deciding to increase or decrease the freq.

Going back to the mp3 example, it could be something like this:

- The CPU runs at full power (e.g. 1000Mhz) to decode the mp3 as fast as possible and load a certain RAM area for the sound device to use

- During that period, it might even be running without halts (100% usage)

- After those .25s, there's no longer any decoding to do but there's still "small stuff" to do every now and then. It might therefore throttle down to 200Mhz (as soon as the governor has a chance to do it), and then keep running/stopping/... and therefore alternating the consumption between 24W (or less) and 1W, very frequently.

mmm, I'm now back from lunch after writing the above and no longer know where I was heading to when writing it (and looking it up) :laugh:

Anyway, better to post it as is rather to throw it all away. Feel free to ignore :silly:
[Galaxy S III Original Android Development] radeonxt:
just as i thought.

you accidentally included disabling speaker amplifier along with speaker tuning.

thanks.

btw, my comment on speaker tuning.

as of beta4 speaker tuning version, it's good on default 57. on 63 it distorts.

using default 57 speaker amp and speaker tuning, the music is good when there is bass present but music sounds distorted when the music is finally on the part where the bass is resting(hehe) and it's just treble and audio of singer playing.
[Galaxy S III Original Android Development] DirkStorck:
Ahhhh OK. Thank you :)

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] nodstuff:
I think I know what you are saying here and here are my two cents:

As we know the CPU governor has thresholds which tell it when to bump up to a higher frequency and also when to drop down.

Say you use 200-1200mhz and you decode that mp3, the CPU will run at max until it had finished the task and then idle, the task of decoding will tax the CPU so that all thresholds are passed and it hits max frequency, when it stops it goes below thresholds until it hits a frequency when it is between up and down thresholds and then switches on and off really quickly as it is doing its task (idling) idle doesn't necessarily have to be at the minimum frequency, the CPU can be running at say 1200mhz and still be idling. (I read somewhere that the CPU switches on and off really fast, does a bit, switches off, does a bit switches off etc.)

If it is decoding an mp3 then chances are it will stay at the Max frequency it need to do the job as efficiently as possible, switch on and off and do whatever other meanial tasks it needs to do while it is doing that.

I don't even know if this makes sense but it makes sense in my head :D
[Galaxy S III Original Android Development] maddler:
"adb remount" not working on b5.

I was on b2 and quite sure it was working. Wasn't it?
[Galaxy S III Original Android Development] gokhanmoral:
try "adb root" first

beta5 is not insecure
[Galaxy S III Original Android Development] maddler:
maddler@lamorte ~/r/C/MacOS> adb root
restarting adbd as root
maddler@lamorte ~/r/C/MacOS> adb remount
remount failed: Operation not permitted

btw, not a big issue. I just wanted to be sure that wasn't a bug.

thx ;)
[Galaxy S III Original Android Development] bangrahman:
If I flash the ODIN version of the kernel, does it only flash the zImage? Because that's what I want to do.

If not, could someone be kind enough to explain how I do so?
[Galaxy S III Original Android Development] amg009:
Guys can somebody explain why this happens and any solutions??

I'm on 1.5b5...
[Galaxy S III Original Android Development] bala_gamer:
Beta 6 change log looks delicious :p

[ thanks for the fifth stepping gokhan

《tapatalked from galaxy s3》
[Galaxy S III Original Android Development] qwerty12:
Will this be fixed? I imagine that's what the toggle in STweaks is for
[Galaxy S III Original Android Development] gokhanmoral:
the old patched adbd had a problem with JB and I removed it together with that setting in STweaks.

I will make beta6 insecure, using the stock adbd.
[Galaxy S III Original Android Development] Carphedon:
It makes sense. I am thinking this: If you have alot of apps running in the background 200MHz might be nice, this background stuff can then run at low frequency because this prevents the cpu from idling, and at this freq it won't drain the battery to fast. But i keep my system very clean, almost no apps are running in the background and zero wake locks. Then it looks to me i could benefit from a higher minimum freq, system is more responsive, finishes tasks faster and as soon as it's done with what i want it to do the cpu goes to idle.

I am going to try this: 700 min - 1200 touch boost - 1700 max. I am curious what the battery life will be, it is fast though :P
[Galaxy S III Original Android Development] Tungstwenty:
If we consider the max CPU speed (the 34W consumption in the example) fixed, and eliminate throttling entirely, the CPU would be idling a lot more (because the CPU finishes the small tasks much faster), and you'd be seeing a very low % CPU usage. But the common perception is that it's not good to have the CPU running at full speed, even knowing that it will be most of the time halted on a WFI instruction and consuming the supposed 1W ...
[Galaxy S III Original Android Development] jody2k:
Glad you considered the opinions of your local audience :) looking forward to beta 6 cheers m8
[Galaxy S III Original Android Development] gaetanolip:
help please,

i lost my imei, now in \data\siyah i have to backup

1: efsdev-mmcblk0p3.img.gz

2: efsbackup.tar.gz

wich must restore and how????

I tried to restore the second one , i extracted the tar an found the efs folder, i restored it manually but didn't work becuse i have now tha 'fake ' imei'

how to restore the first one since it has img.gz extension???
[Galaxy S III Original Android Development] gokhanmoral:
in recovery:

gzip -d efsdev-mmcblk0p3.img.gz
cat efsdev-mmcblk0p3.img > /dev/block/mmcblk0p3

make sure that efs partition is not mounted
[Galaxy S III Original Android Development] Tungstwenty:
The contents of the files are the same, so if the backup was from the same period in time the outcome won't solve your problem.

That first file is an image of the /efs partition, which you can restore by issuing:

gzcat efsdev-mmcblk0p3.img.gz > /sdcard/temp_efs.img (to maintain the original file as is)
dd if=/sdcard/temp_efs.img of=/dev/block/mmcblk0p3

I'm not sure if this also needs a sync command to make sure everything is flushed, but it's something like that.

And bear in mind that this will completely replace the current contents. Perhaps the best is to run this from recovery, with /efs not mounted.
[Galaxy S III Original Android Development] gaetanolip:
thanks

but i don't understand.

how can in recovery use that script???

how can i assure efs partition in not mounted,

please help me!!!! my phone ha no more cellular function..
[Galaxy S III Original Android Development] jody2k:
For those wo are interested in equalizing the phone speaker, it works fine with dsp manager speaker tuning but speaker tuning need to be enabled in beta 4 with stweaks
[Galaxy S III Original Android Development] qwerty12:
Connect your phone to the computer in recovery mode and use ADB

Check in the "mounts & storage" menu of CWM (by default it is not mounted in recovery)
[Galaxy S III Original Android Development] ksilver89:
adb shell
[Galaxy S III Original Android Development] bernard134:
Do check on the loud volume when earphone is plug in. This issue is back on v1.5beta5 when its fix on v1.4

Hope GM can look into this issue.

Edited: saw the changelog for v1.5beta6, thanks GM.

---------- Post added at 11:45 PM ---------- Previous post was at 11:39 PM ----------

+1, same issue but i don't know what cause it. My also never show application under battery.
[Galaxy S III Original Android Development] Daelyn:
I ran a test on mine and came up with these for my GPU. I have not fiddled with the CPU voltages, except from using -100mV with 1600MHz as max.

160 @ 675mV (Step 1)

266 @ 775mV

275 @ 775mV (Step 2)

300 @ 800mV

333 @ 825mV

350 @ 850mV (Step 3)

440 @ 900mV

533 @ 975mV

600 @ 1025mV (Step 4)

640 @ 1050mV

666 @ 1050mV

700 @ 1075-1100mV

800 unstable up up to and including 1200mV.

These are quickly tested and will most likely have a small adjustments upward here and there.
[Galaxy S III Original Android Development] bala_gamer:
i think the frequency interval should be somewhat gradual. wont we feel a bit jerky when jumping from 3xx to 6xx ? just my thought
[Galaxy S III Original Android Development] b0gd4n:
I volunteer!
[Galaxy S III Original Android Development] bala_gamer:
seems gokhan already fixed that :) its been included in the changelog of beta 6
[Galaxy S III Original Android Development] box4m:
Is it possible/dangerous to increase maximum gamma for the screen?

Visibility outside is really bad with this screen i think. Perhaps higher maximum brightness can help, if it isnt dangerous for the screen.. The battery will drain more ofcourse.

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] b0gd4n:
Yeah, I just saw the change log as well :D
[Galaxy S III Original Android Development] Daelyn:
Maybe. I've barely had it for half an hour yet. I fiddled with the thresholds a bit, so it won't do step 4 until absolutely needed. I don't have any games to try with right now, so can't test it out properly
[Galaxy S III Original Android Development] bala_gamer:
m finding the below gpu steppings suit me better(with uv)... giving me great bench result + smoothness.

step 1 - 266mhz@875mv

step 2 - 350mhz@925mv

step 3 - 440mhz@975mv

step 4 - 600mhz@1050mv

as there is 5th stepping with beta6 ill add 533mhz@1000mv as step 4 :)

@ gokhanmoral

will love to save it as my personal profile :D but it needs your mercy :p
[Galaxy S III Original Android Development] nodstuff:
Gpu:

266 @ 775

300 @ 800

350 @ 825

440 @ 875 (testing 850mv as we speak)

CPU:

-100mv

400mhz-1600mhz.
[Galaxy S III Original Android Development] gaetanolip:
maybe you can help me.

i have 3 efs backup

1: efsdev-mmcblk0p3.img.gz 04/08/2012 siyah automatic backup

2: efsbackup.tar.gz 04/08/2012 siyah automatic backup

3: efsdev-mmcblk0p3.img.gz 06/07/2012 my backup of a stock rom

Now, what must restore? why have i2 different 'devblock' of nfs partition? which is right , how can i check what is curren efs block???

please
[Galaxy S III Original Android Development] bala_gamer:
this can be added as smooth-powersaver profile :D

edit: i highly doubt every device can handle this extreme uv. i got artifacts witth 775mv
[Galaxy S III Original Android Development] Chillz88:
Which benchmark do you use to test it?
[Galaxy S III Original Android Development] bala_gamer:
use glbench egypt hd, basemark and nenamark
[Galaxy S III Original Android Development] Daelyn:
I just don't get why people are so fixated on benchmark results? I downloaded glbench only to push the gpu an hour ago and I haven't even done a full run on Egypt HD. Who cares what FPS I get? Nobody, not even myself. Usability and rapidness can't be benchmarked.

And that damn whining about battery life. I will go crazy soon.
[Galaxy S III Original Android Development] nodstuff:
Ya I got artifacts with 440 @ 850 so back to 875mv.

875 works perfectly though.

Ran two Egypt HD benches and got 57fps.

It strange because GTAIII runs no prob on 850 but Egypt bench gives artifacts.
[Galaxy S III Original Android Development] Sangrias:
Issue gone after flashing beta5.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] bala_gamer:
benchmark pushes the gpu to its max potential thus we can figure out the potential safe settings for oc/uv. its a tool, benchies are so good to find a stable settings.

if you oc you gpu and start playing a game or some gpu intensive tasks without testing you may end up with loss of data.
[Galaxy S III Original Android Development] SirCanealot:
Woooo! So the 54mhz and 108mhz gpu steps will be much more usable!

Will be interesting to see if it can jump from 54mz to 166mhz fast enough to not lag too much :p

Awesome work!
[Galaxy S III Original Android Development] nodstuff:
Well Egypt bench is just to stress the gpu to test voltages (for me anyway) and to see if they have negatively affected performances.

And a positive of undervolting is less heat which leads to less power loss and not being throttled and more comfortable to hold.
[Galaxy S III Original Android Development] bala_gamer:
i think you meant egypt classic for 57 fps right ? :p

egypt hd needs more vertex processing power , hence the artifacts
[Galaxy S III Original Android Development] Tungstwenty:
1 and 2 are backups of the same information, only in different formats.

Since 3 is older, there's a chance it might be a backup of when the imei was still ok, so you should probably restore that and see how it goes.

- Boot in recovery

- Go to mounts and make sure /efs is NOT mounted, and that the place where those files are IS mounted (/data ???)

- Connect USB cable to PC

- On a command prompt / terminal, execute "adb shell" (you must have adb on your computer, search for instructions if needed). If it doesn't connect, wait a minute or so before retrying

- Once the shell is opened, use the commands mentioned before to write back the backup contents onto the partition: unpack the file to a temporary file + copy the entire file contents (it's an IMaGe) back to the mmcblk0p3 partition
[Galaxy S III Original Android Development] nodstuff:
*selffacepalm*

D'oh! :D

Ya that's what I meant!!
[Galaxy S III Original Android Development] x10i DauL:
what´s the best scheduler for saving battery over night?

any advice would be much appreciated!

Best regards!
[Galaxy S III Original Android Development] T.K.B:
Well here's an interesting analogy to this: a friend of mine at university is never happy getting just an A in a course- he wants to get the highest in his class or even 100%; and he weeps and bites his nails if that doesn't happen lol. But how many companies would even care about how high/low of an A you scored when they look to hire you?? An A is an A - nuff said. Capability is all that matters in the end.
[Galaxy S III Original Android Development] :
best scheduler would be "no wakelocks".

on a side note, keep everything as default. that would be the best.
[Galaxy S III Original Android Development] Geo1997:
Great kernel but

Apps are missng in battery stats ...

I try to delete cache of Syscope but still missing...

What is the problem ?

And don't know why after some hours my free RAM decreases to 30-50MB and the phone lags totally, have to reboot it... any idea ?

Thx
[Galaxy S III Original Android Development] jesus_c:
Same problems...
[Galaxy S III Original Android Development] paranoid2007:
Same issue here.
[Galaxy S III Original Android Development] Carphedon:
I only get 440 stable @ 900 so 875 is nice :). If you get 57 frames at egypt bench it's not HD though. The HD benchmark should be around 19, even with OC. You need GLBenchmark 2.5 not 2.1.5 or you ticked egypt classic. Try the HD benchmark and see if it is still stable.

* i see bala_gamer already mentioned it, sorry! :)
[Galaxy S III Original Android Development] EdgaBimbam:
No problem with ram, this kernel is like project butter with battery stats, yeh no appz in the list
[Galaxy S III Original Android Development] bordikun:
+1 can only see the 4 main apps in the battery stats list.

and no problem on my ram too, 150-200mb free ram always.

Sent from xda premium powered by GT-I9300 :D
[Galaxy S III Original Android Development] Geo1997:
:laugh: okkk

an app to see simply the battery stats ? because betterbatterystats is a bit too complicated :/
[Galaxy S III Original Android Development] rlorange:
There is is! Dead space full game resume as it was in memory plus Google earth. If you home button out of an app taking a large chunk of men its copied to the swap file partition as a Linux swap at the end of sdcard. You have to relaunch from task manager and wait for swap copy to memory lags to smooth out.

Unlike zram which compreses chached

apps in ram a swap partition on your sdcard is treated like an extra place to store suspended apps. Even big open games

---------- Post added at 04:45 AM ---------- Previous post was at 04:23 AM ----------

no you need a script or app search for the script version the dev is a great teacher too.
[Galaxy S III Original Android Development] graffixnyc:
Hmmm I'm seeing apps in my bat stats. Usually there are more but I just charged/rebooted my phone. running wanam 2.0
[Galaxy S III Original Android Development] gokhanmoral:
v.1.5beta6 is uploaded to http://d-h.st/users/siyah/s3
[Galaxy S III Original Android Development] Chris_84:
Thank you so much Gokhan!

Edit: The kernel running so smooth so far. The fifth step and gpu boost are awesome!
[Galaxy S III Original Android Development] qwerty12:
ro.secure, which is what's changed with beta6, has no effect on the Samsung adbd - check the strings, you'll see that there's no reference to it. If you look at https://github.com/android/platform_system_core/blob/master/adb/adb.c#L898 from the AOSP JB source, you'll see that adbd can be configured to always drop root privileges, which is what Samsung has done here.

Since I don't care for third-party builds of Jelly Bean, I'll repack the ramfs myself.
[Galaxy S III Original Android Development] gokhanmoral:
I like to have silence in the thread after a release

which means I can sleep well, without thinking the reason of the bugs :)

I removed staycount's from STweaks interface which was only slowing down the loading of the app and nobody was changing them. they are all set to 0 as in stock now and you can use scripts if you want to change them.

and for touchboost, it stays at the selected level at least 1 second after you touch the screen.

it locks the lower level only. so, the gpu will be able to scale up freely but not scale lower than the lock level.

and just like cpu freq lock, it will be held as long as you keep your finger on the screen.
[Galaxy S III Original Android Development] bigr1979:
Thanks for the new kernel, running great so far, apart from... speaker is distorting quite a lot, is there away to remove the eq preset for the speaker ?

(anyone else getting this ? I am starting to worry that my speaker is knackered)
[Galaxy S III Original Android Development] gokhanmoral:
hmm, that part I did not test. putting it to my todo list and will test it in the next build and make sure that the kernel is insecure.
[Galaxy S III Original Android Development] bala_gamer:
for the 1st time ever got 59.1 fps with nenamark, but the bigger point is the fps is much consistent and always at 60 mark..... great release....
[Galaxy S III Original Android Development] Daelyn:
* Lost GPU Scaling stay counts.

* Also having issues getting it to ramp up to fifth gpu frequently step. Fiddling with load thresholds made it work, but not satisfactory. Can't get it too back down from 4th step now although I've resetted thresholds. Really weird behavior.

Will reset and reboot to check what's going on.

Edit: reset settings and got GPU to ramp down but it's still a bit cranky in how it behaves. How's it behaving for you guys?
[Galaxy S III Original Android Development] gokhanmoral:
you can decrease the speaker amplification by the highest eq amount, or until you don't have distortion.
[Galaxy S III Original Android Development] TheMathMan:
Yep I agree. No mediascanner here...

No SD in and no media loaded. Been up and running for 20mins and firing at 1200 minimum.
[Galaxy S III Original Android Development] benkizz:
I've waited 30 min and it still stuck at 800,1000,1100,1200...