yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] STAticKY:
Chrome can be quite the hogger of memory.... Especially woth a multitude of tabs open..And if zram is enabled and after filling up the ram and zram with a considerable ammount of data, data has to be swapped around between ram and zram causing these lags possibly as chrome will have likely been put into swap and need to be swapped back out...
[Galaxy S III Original Android Development] romskii:
no i'm using Boat Browser, Chrome is too hungry for me :D

+1 STAticKY
[Galaxy S III Original Android Development] TigerCourage:
WiFi Hotspot does not work on AOSP roms with this kernel.

Now that you guys mention it, I do notice some lags in the animations but they are not actually lags, the animations just sometimes get slower. In 1.0 and 1.1.0 the animations were really fast.
[Galaxy S III Original Android Development] STAticKY:
What you just described is pretty much the definition of lag. http://en.m.wikipedia.org/wiki/Lag

Edit: or maby latency is the more fitting term...
[Galaxy S III Original Android Development] DaReDeViL:
I also have those glitches on apex widgets menu, even on stock kernel.

About wlan hotspot, I have no way to test it on stock cm as I have my cm installed as 2nd rom. But I am pretty sure it didn't work when i was on stock cm. I also checked by the cm thread and found no confirmation about working hotspot either ...
[Galaxy S III Original Android Development] romskii:
like i said, i think it's apex related.

Testing at home again hotspot with different systems.
[Galaxy S III Original Android Development] Tuga2010:
yes , I though on that to .

I think is some sort of zram swapp ram problem related . I´ve tried from another persperctiv , to tweak in GPU ( only for discart this option ) , and the result was very satisfied at first, not such glitches , but after some time , my phone was to warm , and instable, so I have to revert.
[Galaxy S III Original Android Development] STAticKY:
Have you enabled force gpu renderimg. Makes certain thinhs alot smoother...
[Galaxy S III Original Android Development] tracemonkey:
Yes, I cloned 1st to 2nd. Before that I had been messing with various ROMs based on Sammy 4.1.2, last one was Pardus
[Galaxy S III Original Android Development] DaReDeViL:
Does 2nd rom reach bootanimation ? or is it stuck at googy-kernel logo ?
[Galaxy S III Original Android Development] MrxSiN:
[MENTION=1897326]googy_anas[/MENTION] doest the misbehaving sounds fix in 1.5.1?
[Galaxy S III Original Android Development] tracemonkey:
2nd rom fails to boot

stuck at googy-kernel logo, "Booting the secondary ROM...."
[Galaxy S III Original Android Development] DaReDeViL:
please verify in the 1st rom (which you cloned to 2nd rom) if this file exist /system/framework/framework2.jar
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.5.1 ONLINE !!! ;)

[23/06] Version 1.5.1 :

- Lots of modifications to arm_mach-exynos / cpufreq / kernel => Smoothness is back !!! :good:

- Re-introduced simple OC up to 1.6 Ghz

- OC is applied after init process (boot forced at 1.4 Ghz)

- Small tweaks to lulzactiveq
[Galaxy S III Original Android Development] DaReDeViL:
not yet ... I didn't look at it as I was focusing on kernel performance (which is now optimal)
[Galaxy S III Original Android Development] noskojv:
.

googy_anas

You will be working on the kernel with dualboot after the official firmware 4.2.2 ?
[Galaxy S III Original Android Development] DaReDeViL:
99% sure

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] qtwrk:
What's other 1% that prevent you from doing so? :D:D:D
[Galaxy S III Original Android Development] noskojv:
Well done , good job . :good:
[Galaxy S III Original Android Development] tracemonkey:
no, framework2.jar is not in 1st rom. I have framework-res.apk and framework.jar

update:

I quickly flashed back to siyah 1.9.1. 2nd rom still would not boot. Then I formatted and wiped 2nd ROM and re-did the clone of 1st to 2nd. Siyah booted it fine. Then reflashed back to googy-max 1.5.1 test and both 1st and 2nd boot fine. So it's an issue with 2nd rom unbootable when installing 2nd rom with your kernel in place. didn't this come up a while ago? I wasn't making many changes then so didn't notice it.
[Galaxy S III Original Android Development] brujo55:
1.5.1 working like a charm,thx googy.:good:
[Galaxy S III Original Android Development] DaReDeViL:
That means I must rewrite the detection procedure of installed roms which actually relies on verifying the presence of some specific files

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] tracemonkey:
enlighten me - how come it will boot the 2nd rom IF I install it using siyah?
[Galaxy S III Original Android Development] DaReDeViL:
Did you try doing it from scratch with googy-max?

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] romskii:
This is a powerful release! :) my fav is lulzactiveq
[Galaxy S III Original Android Development] Chlorophyll:
jus now flashed googy kernel on my s3 slombean rom.but donno how to access tweaks.pls anyone help me how to accesss to tweaks settings.

thank u
[Galaxy S III Original Android Development] DaReDeViL:
Just use stweaks (available on play store)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] tracemonkey:
tested again.

flashed googy-max 1.5.1 final first. still running cm10.1 nightly on 1st rom (with no /system/framework/framework2.jar). completely removed 2nd rom. flashed pardus rom (4.1.2 version) on 2nd rom. rebooted, chose to boot 2nd rom, booted fine!

not sure what it was - whether due to 1.5.1 test version or state of 2nd rom, but back to normal now.

normal being AWESOME by the way!
[Galaxy S III Original Android Development] DaReDeViL:
I suspect a broken fs on 2nd rom. Anyway I'm glad you made it.

To definitely get rid of this stuff, I'm planning to build a standalone recovery...

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] Chlorophyll:
jus now installed STWEAKS

one more doubt pls clarify

in the audio settings it showing left n right EXT.SPEAKER settings.BUT S3 HAD ONLY ONE SPEAKER.

then how to keep settings at this level?

also i set speaker boost to 7.is this enough?i want my s3 give cal n sms tones louder than usual.

n wat r da safe levels for charging ?pls specify values for usb n direct charging?in settings it showing not more than 1000 is good but in ur 1st post u specified some other value.pls clarify me.

dont mind for too much doubts.thank u
[Galaxy S III Original Android Development] DaReDeViL:
The speaker L & R volumes are for the source audio stereo channels before they get downmixed to single channel (for one speaker)

Boosting level to 7 may give sound distortion but that also depends on the state of your speaker

Charging values are already set to what's recommended, setting them to more can be harmful to your phone or charger or usb port (or all of them)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] zodiaxe66:
A completely rebuild(based on cwm,ofcause) standalone recovery or rebuild GM's hijack,to a newer version:good:

Really love GM's touch recovery,its nice,neat and stable.

You done such an awesome job carrying on his kernel and a new matching recovery would complete googy-max
[Galaxy S III Original Android Development] Gassity:
[MENTION=1897326]googy_anas[/MENTION] mate, is it possible to bring back a good old "tweak sound" in sTweaks?

Also I have one big issue since 1.4.8 - during a night my phone turns off by itself sometimes.

Installing the kernel from the scratch every time
[Galaxy S III Original Android Development] lukaaa47:
hi, possible to implement DIGITAL SCREEN BRIGHTNESS > BRIGHTNESS REDUCTION (0-128)like on temaseks kernel,it really helps with battery saving....
[Galaxy S III Original Android Development] funeralcrows:
Me too, I'm waiting eagerly until the day AndreiLux's screen customization options are ported by [MENTION=1897326]googy_anas[/MENTION] =D
[Galaxy S III Original Android Development] hemal_4404:
V1.5.1 is awesome. In terms of Battery, smoothness and Performance it is ultimate. In terms of sound quality, there is some distortion and not clear as it has to be.

Overall 5 ***** rating to the kernel and Dev.
[Galaxy S III Original Android Development] mikailmohammed:
compared to siyah 1.9.1 how is the rom in terms of performance, battery and sound quality?
[Galaxy S III Original Android Development] inscythe:
Awesome! So far so good, and performance is great as expected. I was totally thinking that you would include the Zzmoove update 0.5.1b, but it's fine... Kinda switching between lulz and zz to find the right governor... So I guess I'll try lulz for now.

So googy, which gov that you personally use?
[Galaxy S III Original Android Development] musmax:
Can someone explain me as I do to make to recognize the wi fi to the second rom?

Thanks.
[Galaxy S III Original Android Development] mikailmohammed:
Can someone explain to me what each governor does? Also my speaker sounds a bit distorted now. I am coming from siyah kernel 1.9.1.

Sent from your toilet
[Galaxy S III Original Android Development] inscythe:
Governor essentially controls your CPU behaviour, when to speed up, when to slow down, when to turn on/off cores, etc. It also controls the LCD frequency. The audio distortion is probably because of the audio amplification or equalizer settings, try toning it down in stweaks...
[Galaxy S III Original Android Development] hisee:
This kernel come with default settings or with changes like oc, uv,? Asking coz I notice usb charger mv is set to 800 which is not default so may i know which setting has been change
[Galaxy S III Original Android Development] mikailmohammed:
I know what a governor does i want to know what the different ones included in the rom does. For example like hotplug will give you more battery life but slower speeds.
[Galaxy S III Original Android Development] nightwing90:
No. Mostly are of default settings but few changes already applied when OUT OF BOX. like the audio tuning is set to 2(Default is 0). Also USB charging to 800(Default is 475). Normally for USB charging i set for 500. coz read some where that need USB 3.0 for more value than 500 mv. Also compared to Siyah kernel's default the gpu voltage is also changed a bit different :good:
[Galaxy S III Original Android Development] STAticKY:
Now days boards like mine are able to supply at lease 1.5 amps from special high current USB 2 ports.. I charge mine at 2amps from the wall and USB...

TP.
[Galaxy S III Original Android Development] nightwing90:
Mate me just explained the safer side. That's all :D

Also which rom are you using with this kernel :confused:
[Galaxy S III Original Android Development] hisee:
Is that safe or will have sum effect?
[Galaxy S III Original Android Development] mikailmohammed:
Does the gpu voltage affect the battery life compared to siyah's?
[Galaxy S III Original Android Development] STAticKY:
I understand. I just thought I'd put in my 2 cents about higher charging rates.. I'm using temaseks rom with his kernel too. Was previously using this kernel on his ROM bit I just can't live without the screen calibration..

TP.
[Galaxy S III Original Android Development] nightwing90:
Which, abt USB settings?? I would leave it at default settings. They are infact amazing. Any more and you would fry your s3 chip or damage your battery.

1000 mA for direct current (from Charger) is fine and 475 mA for USB charger is also fine since maximum power output a USB 2.0 can give is 500 mA. You can change this to 500 if you like. USB 3.0 Gives 900 so you can set it to 899 if your PC has USB 3.0 Port ONLY

---------- Post added at 08:34 AM ---------- Previous post was at 08:31 AM ----------

I Think too much will affect.But in Default settings only few voltage changes will not. Also normally i play HD games (no OC). So i don't care about battery drain ;)
[Galaxy S III Original Android Development] hisee:
What about other setting? (which already changed when we flash this kernel)
[Galaxy S III Original Android Development] nightwing90:
Me just decide when Rom changes. When i am on Purelook HD the audio tuning is set to 0 coz A good sound mod(PureX Audio Walkman) is included in that rom. Also when on Omega the tuning is set to 1(really good) because when set to value 2 the clarity of the speakers is not good,distortion occurs :( ( Also i think that depends on Speakers current state).
[Galaxy S III Original Android Development] hisee:
So only 2 changes and other options r set to default only na

Where is the option for audio tuning?I am nt getting it (stweak - >audio)
[Galaxy S III Original Android Development] nightwing90:
Sorry my fault. that option was included in the previous versions 1.4 x . I think the new version was using another sound engine & that option must be removed. Sorry :D
[Galaxy S III Original Android Development] hisee:
When I play songs volume is cracking and if I change to Siyah it working perfectly :confused:
[Galaxy S III Original Android Development] nightwing90:
By observing the previous comments many users are said abt sound issue. Hope that OP [MENTION=1897326]googy_anas[/MENTION] will fix that soon. Or its up to you to change the kernel.

Also if you need better battery and sound try this kernel by the same OP. http://xdaforums.com/showthread.php?t=2242325

which included with Boeffla Sound mod to which is pretty good :o
[Galaxy S III Original Android Development] FadeFx:
As you might know, sound problems are mostly given on cm/aosp-based roms which that kernel does not support.

[MENTION=1897326]googy_anas[/MENTION] My feeling about current sound engine is quite ok, but i guess you will have the same problems with this as with boeffla, as they are essentially the same. I would still prefere scoobydoo sound with added mic gain and probably seperated volume for headphone amp. Seperate volume for speaker out does not make any sense, while it has an effect, i don't se a reason why anyone would want that.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] inscythe:
Sorry, I misunderstood your query. Zzmoove has a pretty comprehensive, separate thread here. Basically, it is a mix of hotplug and conservative governor with a faster scaling.

The other classic ones can be seen here. Quite an old thread, but it gives a fairly good outline.

There is no 'best' governor for everyone, but there might always be the governor that suits your usage pattern best. I suggest that you just try them one by one until you end up with your best choice. I'm running pegagusq when on Perseus kernel and lulzactiveq when on Siyah. Tried zzmoove for a while when I switched to googy-max, then went back to lulzactive for now as comparison. Pegasusq in googy-max is more or less similar in performance and battery life compared to the other custom kernels with my usage pattern, IMO.
[Galaxy S III Original Android Development] MrxSiN:
[MENTION=1897326]googy_anas[/MENTION] take a look at Gpu frequency. I set to minimum 200 mhz, but it shows 150 mhz. Only for 200, 266 have no problem.
[Galaxy S III Original Android Development] Andii S.:
im unable to connect to wifi at work, router: TP-Link TL-WR941ND

at home with the big brother (TL-WR1043ND) of this router all is good

Back to 1.5.0a for now ;(

edit: both routers have wpa2 and mac filter enabled
[Galaxy S III Original Android Development] ThePureHeart:
Look, there's a reason why samsung set the default value of charging to 475mA and 1A (usb and ac, respectively). These values will keep the battery healthy.

By going to the high values you have, you ARE damaging your battery and reducing its lifetime. I'd say what you are doing is safe, but not healthy for your battery. That's all.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] STAticKY:
I agree. I'm well aware of the risks. I was simply stating it was possible for those as brave as me :P on the power source side of things I'm fine and forever will be, but the battery, that's another story. It may be wearing it out faster, but its a stock standard battery, I got the phone second hand about 6 months after release, and a new battery costs peanuts. So for my fast lifestyle and high usage patterns, it works wonders for me.

TP.
[Galaxy S III Original Android Development] DaReDeViL:
Nice find ;) I'll look at it (It is related to the modified frequencies table)

PS : How do you monitor gpu freqs ?
[Galaxy S III Original Android Development] MrxSiN:
Cpu adjuster.
[Galaxy S III Original Android Development] FadeFx:
You could also use malistatus by balagamer

http://d-h.st/423

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] STAticKY:
Doesn't work for me on temaseks ROM. Does it work for you?

TP.
[Galaxy S III Original Android Development] tapsumbongs:
I experience really bad lags and stutters while playing games like temple run and hungry shark.. normal use such as browser and scrolling are very smooth. cpu and gpu settings are default and I'm using zzmoove. Please advice? Thanks :)
[Galaxy S III Original Android Development] qtwrk:
Sorry if I double reported,

I have witness again, the CPU jump frequency problem

I set Max to 1400 , but I saw 1600 in CPU spy.
[Galaxy S III Original Android Development] _MirageX_:
Can I ask why OC has been limited to 1600 ghz and Boot frequency to 1400? Didn't find anything with search.
[Galaxy S III Original Android Development] FadeFx:
Didn't try for a while but it used to work...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Leicxan:
same issue here . i limited max cpu frequency to 1400,but when i use cpu spy it shows 1600

i'm using version 1.5.1 now

sorry for my english
[Galaxy S III Original Android Development] mikailmohammed:
cpuz says the same thing at 1.6ghz. Rom is smooth and nice but audio needs to be fixed bit. Too much distortion.
[Galaxy S III Original Android Development] brujo55:
same problem whit audio.
[Galaxy S III Original Android Development] WiwiPouPou:
+1 your previous voodoo sound was the best!
[Galaxy S III Original Android Development] brujo55:
maybe other app override stweaks

if you are on cm/aosp/aokp

check rendimients in settings

mine working fine.
[Galaxy S III Original Android Development] mikailmohammed:
I have high battery drain. Does my phone needs to be accustomed to the kernel. I flashed last night.

Sent from your toilet
[Galaxy S III Original Android Development] qtwrk:
I am 100% sure there is no script nor apps that override the CPU setting, Max 1400 , CPU spy shows 1.5 minutes of 1600 in total 12 hours time, it's not big issue, but I thought it may be better report in.

As matter of fact same problem had been occurred before...
[Galaxy S III Original Android Development] musmax:
... Thanks for the replies.
[Galaxy S III Original Android Development] miwanr:
Install v1.4.6, it's the best for gaming IMO
[Galaxy S III Original Android Development] brujo55:
1.5.1 working fast whit ganstar vegas [gameloft] at very high graphics,0 lags.
[Galaxy S III Original Android Development] movrshakr:
I have been reading this thread for a while, thinking about installing it to get sound enhancement on my stock/rooted S3.

Originally had voodoo on an S1. GREAT! On S3, found I needed a kernel with scoobydoo in it. Now, am I reading that this has something (better?) than scoobydoo...but current version is downhill on sound (only reason I need the kernel)?
[Galaxy S III Original Android Development] mikailmohammed:
anyone else battery is draining plenty?
[Galaxy S III Original Android Development] FadeFx:
All those sound engines are based on scoobydoo sound but have extended capabilitys like separate l/r gain and mic gain control. Sound quality is only dependant on eq settings and eq band settings where the former can be configured by user, while the later has to be preconfigured in the kernel config. The problem with wolfsson sound interface (currently used in googy_Max) and boeffla sound (tested in an earlier version) is that with aosp based roms it is not stable in both cases, while scoobydoo is stable but not feature complete.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
No, on cm cpu there is no max freq override, only on sammy AND this is only kernel related... It should be fixed soon

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] DaReDeViL:
I think I should start a poll about preferred sound engine in googy-max...

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] nightwing90:
Can you mention the settings that made in STweaks ?? :confused:
[Galaxy S III Original Android Development] qtwrk:
What governor you use?
[Galaxy S III Original Android Development] qtwrk:
Gooooooooogy

I found a mistype in Stweak :D

As attached photo, the Max CPU was 1400 by default actually, but the description says 1600.
[Galaxy S III Original Android Development] nightwing90:
Governot : Lulzactiveq

io: cfq
[Galaxy S III Original Android Development] _MirageX_:
i've been misunderstood. I was asking why during boot cpu is limited to 1400 AND why maximum possible overclock has been limited to 1600 while i remember I can overclock to 1800 Mhz
[Galaxy S III Original Android Development] Leicxan:
i'm on sammy stock and no other script that override STweaks

this bug occurs on previous version
[Galaxy S III Original Android Development] MrxSiN:
Maybe because of many people not seem very stable on 1.8ghz
[Galaxy S III Original Android Development] davtse:
As the previous post states, anything above 1400 may be unstable for some users. Stability is very often stresed to the max during reboots, and while mostly useable in normal conditions, may cause bootloops for those devices that cant support it. I think it's a very good decision to limit the CPU to 1400mhz till after boot.
[Galaxy S III Original Android Development] FadeFx:
To test stability i use MediaConverter, this will show you what your CPU can handle...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] davtse:
That or anything else that stresses your CPU. But whatever works for you would suffice. Might I suggest to go one step further and plug in your s3 while you use your mediaconverter? *Most* instability will reveal itself that way. The exact science was discussed in a separate thread but I cant for the life of me recall where it is. I'll share it if I chance upon it again.
[Galaxy S III Original Android Development] giuseppe_g:
Best kernel setting for the latest version?
[Galaxy S III Original Android Development] FadeFx:
Give that a try, any stress test did not stress the CPU enough to crash, when MediaConverter still gave me a hot reboot... for my device that means everything above 1400mhz was unstable. I still use 1500 because in daily use i have no issues, but total stability means 1400mhz for me.

_________________________

tapatalked from GalaxyS3

---------- Post added at 08:20 PM ---------- Previous post was at 08:16 PM ----------

Find out yourselfs. This is highly depending on your usage and personal preference.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] brujo55:
undervolt -50uv

cpu oc 1.6ghz

zzmoove

gpu oc 266,350,440,533,600

scheduler int extorage row

scheduler ext extoraje row

zram 600,80%zwapines
[Galaxy S III Original Android Development] Gassity:
I use -100uv, other settings are the same

Audio:

Enable equalizer

63/63 for left and right

Speaker boost level: 7

Enable privacy mode

Use presets

Googy-max or pleasant for ears

Enable fll tuning and dac oversampling

Misc:

Disable android logger

And remove root lol)
[Galaxy S III Original Android Development] brujo55:
abb

1050,1050,1200,1200