yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DeadPicsel:
I love you googy_anas :)

---------- Post added at 07:54 PM ---------- Previous post was at 07:44 PM ----------

Hang on a minute. Am I missing something, like the download link lol. :)
[Galaxy S III Original Android Development] riso123:
Just flagged 7.7 and my device from first looks feels much more fluid and responsive again!
[Galaxy S III Original Android Development] DeadPicsel:
I take it back I have found it lol :) .
[Galaxy S III Original Android Development] ucarcamagno:
What governor is suggested in last version for performace, without tweaking default? And for performance and battery life?
[Galaxy S III Original Android Development] arbi97:
Always use Pegasusq Governor ( standart ), CFQ ( Int. and Ext ) with 1024Kb buffer ( both ), ZRam 600 Mb. Works great, no problems, no lags)))

EDIT: Use CM 10.2 Nightly
[Galaxy S III Original Android Development] Chaitanyapatel8880:
I have seen a lot of dev threads but i never had thus much fun being on this thread in a any other threads i have visited... Thank you guys... And most importantly googy... ;)

If my post had helped you than please press Thanks button. It might be very little for you but VERY BIG for me.
[Galaxy S III Original Android Development] n. tympanicus:
does 1.7.7 works with latest cm?
[Galaxy S III Original Android Development] JustArchi:
It does.
[Galaxy S III Original Android Development] dollyaja:
Does this setting goes well for sammy rom? I'm on omega now

sent from my GT-i9300 with OMEGA rom
[Galaxy S III Original Android Development] reinerlee:
I couldn't understand this. can you please explain more ?

What if I use ROM like crDroid. which based on (cm 10.3). is this still supported ?

THanks.
[Galaxy S III Original Android Development] FadeFx:
It should, if it does not, its rom devs fault as they tend to use extended frameworks that need to be loaded in init, but do not follow a standard naming convention (framework2). If your desired rom does not work, while it should as it is cm10.2 based, go to the roms thread and complain about this there.

Crdroid does work afaik.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] reinerlee:
Ah, ok, I understood now, thanks for the explanation.
[Galaxy S III Original Android Development] FadeFx:
You are welcome and allowed to hit that respective button...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] reinerlee:
Done !
[Galaxy S III Original Android Development] ric69:
I'm using 1.7 since yesterday with neatrom 4.1.2 and pacman on second rom, it's really an excellent kernel Googy thanks for sharing your work :good: Battery life is very good

Is it normal that Stweaks takes 30/40 seconds to open with 1st rom and only 10s for second ?
[Galaxy S III Original Android Development] tracemonkey:
On 1.7.7 with latest cm 10.2 nightly. Just noticed that after reboot i got a popup that gapps force closed. No actual issue with running any Google app. popup happens only one time shortly after booting.
[Galaxy S III Original Android Development] FadeFx:
;)

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] derfo:
Omega AOKP v11

There is some incompatibility with Omega AOKP v11 and Googy Max 1.7.6. Get error (continuous) of process com.android.phone has stopped. Got the error message even with a clean full wipe install. I have posted this in the ROM thread but posting here in case anyone using Omega AOKP v11 wants to update the kernel to Googy Max.
[Galaxy S III Original Android Development] PjotrFias:
Try 1.7.7
[Galaxy S III Original Android Development] cheese458:
do people here have gentle fair sleepers on or off?
[Galaxy S III Original Android Development] Ctrl+A:
Works very well on latest liquid smooth 4.3.1 ! :D

Thank you googy!
[Galaxy S III Original Android Development] DaReDeViL:
1.7.7 is working well ...
[Galaxy S III Original Android Development] DeadPicsel:
What's the best settings to have if you want no lag and high performance? I'm new to Kernels but after playing with a few this one by far is the best.
[Galaxy S III Original Android Development] dodsble:
Does not work with newest cm 10.2 nightly at all!!!

1.77 Makes the rom laggy always rebooting etc. Then i tried cm10.2 nightly 26.10 without googy max only with stock kernel and it is fine!

On top with googy max 1.77 on cm10.2 many apps crashed all the time..
[Galaxy S III Original Android Development] amppen:
Sounds rather curious :silly:

Tapatalked
[Galaxy S III Original Android Development] DeadPicsel:
I will admit mine is laggy and keeps restarting, but I'm not running a leaked cm10.2 l. I think I'm going to try a clean install, unless anyone can think of anything. :)
[Galaxy S III Original Android Development] tracemonkey:
My experience is totally different. I'm running with 1.7.7 and the cm 10.2 nightly dated 10/27 (which is the latest I can see in cmupdater). The only issue I've noticed is the minor one I posted about previously.
[Galaxy S III Original Android Development] FadeFx:
Id suggest to boot to recovery and clear cache and dalvik cache and try again.

Probably because this is a galaxy s3 kernel, not nexus7...

Just kidding, same as above

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DeadPicsel:
I've cleared cache and dalvik cache and I'll see how I get on. Two devices and one account lol, made me chuckle tho :)
[Galaxy S III Original Android Development] Antidote03:
Amazing ,Everything running smooth ultimarom frist second Rom temasek v65.

Thank you googy
[Galaxy S III Original Android Development] MrMastodon:
Q: When using other applications to change governor, which of the zzmove's is it that shows up in the choices? There is only one...

The reason why I'm asking is that I want to use tasker to change governor to pegasusq when i stream music on BT, and back to zzmove when done. It would be nice to know which one of them in using :D
[Galaxy S III Original Android Development] NHNXDA:
It does state only for 4.1.2 Samsung, whereas we use the 1.7.5 googy kernel max on slimroms 4.3 without issues, so question is, can we use the 1.7.7 version on the I9300 with slimroms as previous 1.7.5.

TIA.
[Galaxy S III Original Android Development] davtse:
Working perfectly fine (slimroms+1.7.7)
[Galaxy S III Original Android Development] FadeFx:
There is only one zzmoove, the others are preset settings for preformance, battery and balanced

_________________________

tapatalked from GalaxyS3

---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------

Where does it state that? Most likely it is meant that no samsung 4.2.2 roms are supported.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] 2rgman:
i'm on Temasek v66 & GoogyMax 1.7.7, everything work great!! thanks googy!!!
[Galaxy S III Original Android Development] NHNXDA:
Post 1 of the thread

---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------

Thanks for the info, is that on an I9300?
[Galaxy S III Original Android Development] Hoschi:
Carbon 10/28 and Googy-Max 1.7.7: simply perfect! Thanks :)
[Galaxy S III Original Android Development] a_prabhu7:
Enjoying fusion with googy max 1.7.7 thanks bro
[Galaxy S III Original Android Development] adnan7khan:
+1 same here.. . (Rom) temasek v 66 with (kernel) 1.7.7

[MENTION=1897326]googy_anas[/MENTION] Only thing i wana ask ..if you could plz add more steps for vibration >?

10 is kinda too much for me though, if you could consider it.. thankx :)
[Galaxy S III Original Android Development] xclub_101:
Seems to be working fine so far :good: , tomorrow I'll also report on the battery consumption over night.
[Galaxy S III Original Android Development] FadeFx:
Then you didnt read that correctly, there it states it is only for 4.1.2 OR cm10.X/AOSP 4.X

Aokp is cm based as well btw

_________________________

tapatalked from GalaxyS3​
[Galaxy S III Original Android Development] NHNXDA:
Fella, with respect, go to post 1 & check yourself, it doesn't state AOSP 4.x in the title or 1.7.7 text that I can see, as I wouldn't of asked if I was there.

Anyway I have installed updated kernel & latest build 2 of slimrom without issues.
[Galaxy S III Original Android Development] FadeFx:
Fact is that all aosp roms for the i9300 are based on cm kernel port and thus run on googy_max kernel. Rhere has been a problem with cretain roms on 1.7.6 lately as the rom devs started to include additional framework files that needed to be included in init which did not follow a common naming convention and thus would have made it neccessary to build compatibility for every single rom into each custom kernel, but afaik these problems are solved as well already and if not, it is in the responsibility of the rom dev to rename these framework files to follow the framework2 naming convention.

Other than that, all that sentence wants to say is that samsung 4.2.2 based roms are NOT supported by rhis kernel.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] JB-007:
Hi

after reboot, i/o sched comes back to cfq even if i set to another value.

I use sammy rom, Wanamlite 6.8.

Cheers
[Galaxy S III Original Android Development] MrMastodon:
Ah, thanks. It just looks like 4 different zzmoove governors in the extweaks menu. Then I assume it will jump back to my preferred zzmoove settings when tasker is changing governor to zzmoove again.
[Galaxy S III Original Android Development] JB-007:
I forgot to specify, stweak shows the right values after reboot but seems not be effective. I checked via setcpu app to have actual value.
[Galaxy S III Original Android Development] PIRATA!:
What is this patch all about, please?

About the kernel...I've read that someone says something about that undervolts....

Is the Googy-Max kernel undervolted by default??

I am having a little bit of lags and slowing down if the phone since I've flashed last Googy coming from last Siyah.

Can you please tell which are the defaults on the Siyah kernel so to use them as base for setting for my Googy-Max as its better?

What about the the smoothness value in the ZRAM?

And what about the buffer's Kb?? Why so like that??

Thank you.
[Galaxy S III Original Android Development] FadeFx:
Try disabling zram and check if lags persist.

The patch is only about applying zram settings without locking stweaks for minutes ...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] kasperok:
exfat support

Missing exfat support (my 64Gb!:crying:) using any 4.3.1 based rom as secondary. Fat32 is working fine..

Anyone else can confirm?

Is that a kernel issue?

thanks

EDIT: Solved. Removing and reinserting my 64Gb in the slot made the magic!
[Galaxy S III Original Android Development] rafaelpernil:
I'm using a 64GB microSD formatted in ExFat on CM10.2 as 2nd rom without problems.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] kasperok:
Solved.:good:

Solved. Removing and reinserting my 64Gb in the slot made the magic!

The strange thing is that the primary rom had no problems reading the exfat sdcard before removing! mah..:o

Thank You
[Galaxy S III Original Android Development] PIRATA!:
Disabling it?!? Everyone has it and I also had it with Siyah...isn't it better to have it??

And this patch..where can I find it??
[Galaxy S III Original Android Development] FadeFx:
You had non working zram with siyah... also i suggested to disable it to see if it makes a difference for you. I dont use zram and my phone is flying

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] chrismast:
Never used zram as I got lags, no problems without it so far.

Sent from my Nexus 7 (2013)
[Galaxy S III Original Android Development] 2rgman:
Same here, never used zram and have no lags as CM has amazing ram managment
[Galaxy S III Original Android Development] XPLOSIV10:
Back to Stock Kernel..Googy Max f*ck my microphone, i have to reboot my phone always before i can make a call because only then my microphone working fine :mad:
[Galaxy S III Original Android Development] PIRATA!:
So in Siyah I never used ZRAM?!??

Was it not working?!???

Btw...I have problems with CRT lock screen, even playing around with them FB EARLYSUSPEND DELAY...while with Siyah I was able to handle it putting it to 0...but no CRT effect then...

What can I do?
[Galaxy S III Original Android Development] FadeFx:
Disable dac direct in sound engine tab and you will be fine. Its a nearly forgotten old bug...

_________________________

tapatalked from GalaxyS3

---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------

It was not really working. I mean it did work, but in an ineffective way iirc. Howewer, anas could say more but he has more important stuff to do.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] tmac31:
guys actually zram works awesome and gives great improvement on multitasking. and it doesnt slow phone at all. but;

it slows down when you start to open too many apps (if you dont use zram you cant open this much app anyway). but you actualy just see difference at app calling from ram it can make 1 sec delay but its better than starting from 0 to load. and it doesnt slow phone at usage of an app.

and there is another thing LMK still does its job BUT with zram phone think it still has ram to open and dont close apps fast so you need to close your apps sometimes.

at multitasking side i can keep real racing 3 browser phone app and launcher on ram without any performance problem(xposed app settings help too). if you are on a sammy rom without zram you can just open real racing 3 and launcher will probably redraw after you quit game and i even see rr3 crash cuz of low ram alone. so zram helps multitasking alot but if you dont need to open some apps together you wont need zram and dont use it.

so there isnt a 1 true about zram it depends on user. on a sammy rom and 1gb ram phone zram is must for me .
[Galaxy S III Original Android Development] piyiotisk:
i have a mic problem on some AOSP roms. When i made a call the mic is working ok but when i try an app lets say Shazam or viber etc. my mic is only working on second try. Is there a fix for this?
[Galaxy S III Original Android Development] FadeFx:
Are you on latest googy_max AND a recent aosp rom? Afaik that bug was solved already...

_________________________

tapatalked from GalaxyS3

---------- Post added at 12:42 AM ---------- Previous post was at 12:32 AM ----------

[MENTION=3278619]PIRATA![/MENTION] crt off animation is working well here, even with early suspend delay set to 0, seems the bug in cm code that required this setting was solved silently.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] blackrose1:
Can i use 1.7.7 on miui Dagutt 4.2.2 base on CM 10.1?

(( هرچه بگندد، نمکش میزنند((@)) وای ب روزی که بگندد نمک ))
[Galaxy S III Original Android Development] XPLOSIV10:
not really, everything was disabled. even on the stock driver I had this trouble. when it comes to the microphone googy is simply the latest sh*t. sorry for the direct words, but it is a long known problem-and there is still no solution.
[Galaxy S III Original Android Development] jumpers:
Since last update, getting memory leaks, apps killed un memory, slow device, freezes. Trying without GoogyMax, but ont sûre from where Côme thé problem

Zram enabled, with 4 disks, and 1200mb total size. And 80% smoothness.

edit : swithched to Temasek's Kernel, no more memory issues. [MENTION=1897326]googy_anas[/MENTION], please fix this, missing dualboot options, and ScoobydooSound engine. :( using Googy Max since months without issues, but, 1.7.7 update is problematic. :(
[Galaxy S III Original Android Development] peramikic:
This was fixed on the CM level about a month ago

http://review.cyanogenmod.org/#/c/51085/

http://review.cyanogenmod.org/#/c/51157/

what rom are you on?
[Galaxy S III Original Android Development] piyiotisk:
i had this problem on PA 3.99 rc2 and on liquidsmooth 2.10 and 2.12
[Galaxy S III Original Android Development] DaReDeViL:
Well, you really wear correctly your nickname XPLOSIV10.

When you say googy is the latest sh*t you mean me or the kernel ? Or better, both with the same price, huh ?

Anyway, my github is open to public. Go ahead and fix it then come back feed my ignorance !

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] qtwrk:
I'd say your phone and its microphone are unique piece of sh*t, or they start act like piece sh*t just because they have piece of sh*t owner.

If you don't like it, get the f*uck out of here, no one here is putting a gun in your head and forcing you use it, here is XDA, not your sh*t place, development may or may not contain a bug, that's why it is a development, even something good as Microsoft, Adobe, Sun or whatever software you name it, always has bug here or there.

Be thankful or be silent.

And now go home ask your mama to teach you how to be a human being instead of like a piece of sh*t
[Galaxy S III Original Android Development] peramikic:
Yeah PA is build date Sep 21st so it won't have those included, don't know about the other 2... check their build dates, but they also might not have ported the commits from the CM tree. In any case was rom level issue not kernel
[Galaxy S III Original Android Development] padraigdoran:
I'm trying to play Galaxy on Fire 2 HD but the game is laggy as hell, can't play it properly at all. This is even with zzmove performance and CPU set to 1600MHz. Running latest CM10.2 nightly with latest Googy-max kernel. Any ideas?
[Galaxy S III Original Android Development] XPLOSIV10:
I mean the kernel :o
[Galaxy S III Original Android Development] chrismast:
still doesn't make your behavior better...as you might know googy (and other devs on XDA) are investing their free time that they could spend with other things. they spend it for you, for me, for anyone that wants to try their development which might include bugs. Hence calling something s*it only because it does not work for you (and maybe someone else) but for other users it does is not really a polite way of recognizing someones free time investment into the project. but maybe you just have been drunk when writing your comment :), just my two cents :)
[Galaxy S III Original Android Development] PIRATA!:
Mm...

Any way you let it work correctly??

Interesting... I'll read it as I'll have a couple of finites. ;)

Btw...I have problems with CRT lock screen, even playing around with them FB EARLYSUSPEND DELAY...while with Siyah I was able to handle it putting it to 0...but no CRT effect then...

What can I do?
[Galaxy S III Original Android Development] verifyfx:
Have you considered an unofficial nightly release?

I am using pa_i9300-3.99-RC2-20131010 and got no problem at all

http://www.abun880007.co.uk/i9300downloads.html
[Galaxy S III Original Android Development] FadeFx:
I am not sure, maybe we could just remove that defect option...

I still dont get what problem you have there nor what u want to achieve, please describe a bit better, just repeating the same rubbish wont help.

_________________________

tapatalked from GalaxyS3

---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------

Easiest solution for all of us is you flash stock kernel and bother samsung that your piece of sh*t does not do what you want it to do, or you test flight mode of your piece of sh*t out of the window....

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] cKenny:
:good: best solution, so far. :laugh:
[Galaxy S III Original Android Development] PIRATA!:
I imagine you don't have any problem with CRT effect, otherwise you would understand right away.

When I press the power button to turn off my screen, it does not always go off the same way:

-when I turn off my screen, it comes on again just for a bit, then it goes off again, and after another bit I can hear the screen-off water sound;

-the effect described up here does not have the same timings every time. Some times it's 2 sec/1 sec, usually if I repeat it is 1 sec/less then 1 sec, and if I repeat it again the screen does not turn on again but the sound is still delayed;

-if I turn it on for watching what time is it, or to pull down the menu for example to enable/disable something, then if I press the power button again to turn the screen off without unlocking the screen, it goes off for a bit and then it turns on again and I see my unlock screen time upon the main twlauncher screen in transparency, and after another bit it appears the unlock screen with screen on as usual as when you want to turn it on...while I was trying to turn the screen off! If I repeat this, it goes finally off after 3 or 5 times I do that;

-to turn it off right away, I must unlock my screen and then turn off screen/unlock. Now it goes off at first time! I noticed that when the screen is going if correctly, the CRT effect it takes a little bit longer to make the animation, while when I was getting all the other situation, the CRT effect was faster;

-with Siyah I had similar problem, but it was related only to 3 tries, and at the third was going off. I had fixed it by putting at 0 the FB timing. No CRT effect in that situation, but at least it was turning off and on as supposed. With Googy-Max the FB timing does not effect enough to fix this. If I put it at 0, I still get CRT effect with similar problems as if I chose any other different FB timing in STweaks settings.

Now...does someone have something similar? Can someone please help?

Thank you.
[Galaxy S III Original Android Development] Arfman:
I can't use any of the latest CM nightlies, constantly getting the process com.android.phone has stopped. CM 10.2, Gapps for Android 4.3, Googy Kernel 1.7.7. Tried Googy kernel 1.7.4 and 1.7.2, nothing works anymore.
[Galaxy S III Original Android Development] davi_ssilva:
Yes, I had the exact same issue, but i assumed that it was caused by myself.

I was using Omega Rom and since I don't remember if I installed the transparent status bar mod AFTER or BEFORE I installed the CRT OFF mod, I thought it was that issue that broke my CRT OFF effect.

So I decided to update my rom to v50.1 (I was previously in v 49) and then install everything in the right order (the CRT OFF mid must be installed AFTER all the other mods). But then I didn't find a transparent status bar mod compatible with v50.1, so I couldn't test if my theory was right.

---------- Post added at 09:04 AM ---------- Previous post was at 08:17 AM ----------

Nope, just tried now without installing any status bar m mode, just the CRT OFF effect, and I keep having the same problem. So I guess it's kernel related indeed. Or it's just omega' s rom related, because I didn't test with any different rom.
[Galaxy S III Original Android Development] FileFixer:
I have a same issue with crt off on Foxhound 2.7 and Googy Max kernel before few version later till new 1.7.7 but I ignore it.

It is not crutial matter error for me. Just press twice power button or menu button and power off work.;)
[Galaxy S III Original Android Development] PIRATA!:
It looks like I'm not the only one.

I'm thinking on removing the CRT effect. DarkyROM has this capability (provides in a folder stored in the sdcard all the files to replace in /system/ for each mod..and I have only to manually replace them and reboot to have same rom with no CRT)

....but I like the CRT effect!!!!! Any possible solution to try???
[Galaxy S III Original Android Development] larryk:
Why not just install "Screen Off and Lock" by Katecca from Google Play and use it's CRT off, and then use the button on the screen to shut the screen off rather that pressing the power button, Much less wear and tear on the physical button...
[Galaxy S III Original Android Development] davi_ssilva:
Because I prefer to turn off my screen using only a physical button...