yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] xclub_101:
Maybe try EMF1 modem (if you have a full EFS backup from before going to the new format).
[Galaxy S III Original Android Development] daniel98:
Thanks. I will try it
[Galaxy S III Original Android Development] Volpe92:
+1

However, with the latest 1.7.5 I had a decrease in the rate of charge of the battery!

That is, it is slower to load.

Last thing you can increase the time of opening of the application sTweaks?

I know that this application was created to siyah kernel but I hope something can be done :)
[Galaxy S III Original Android Development] Olioaglio:
Stweaks load up time depending on amount of features kernel offers. So it is long load time with much kernel features. Think the only way to speed up loading would be a rewrite of Stweaks itself.

Olioaglio
[Galaxy S III Original Android Development] xclub_101:
+1 on that, I know that with sTweaks it is all about getting each feature and when there are a huge lot of those it takes longer but with the exact same kernel sTweaks starts (much?) faster in cm 10.3 than in sammy ROMs, so some gains might still be possible without replacing that protocol/app.

But IMHO it is more important to try to fix the touch-to-wake thing in calls since that results in hanging the call.
[Galaxy S III Original Android Development] Nichie:
Don't think this has been covered yet and didn't get a reply to my previous question.

How does the TRIM function work? Does it run automatically (when?) or does it need to be manually executed (how?).

Thanks!
[Galaxy S III Original Android Development] jumpers:
i have 2 questions :

1 : how to make my settings "permanent" ? (restoring after a nightly update from CM), i need to reconfigure all my settings after all CM flashs, thats very boring. :(

2 : where can i find good values and settings for color tuning ? colors are very crappy, my i9000 has better colors, WTF ?

thanks for replies.
[Galaxy S III Original Android Development] popoyaya:
I'm getting no caller id display with latest version on Omega Rom v49. I tried reinstalling stock kernel and caller id was back. Then back to Googymax and caller id is gone again.
[Galaxy S III Original Android Development] Gambit14:
I found THIS around in the forum, maybe it can help :)
[Galaxy S III Original Android Development] jumpers:
i dont have this settings in stweaks. :/
[Galaxy S III Original Android Development] Gambit14:
Aren't them same as mdnie options in googymax? :confused:
[Galaxy S III Original Android Development] jumpers:
i need new eyes, found the options later after posting. but, after modifying settings, it seems not so better. :(
[Galaxy S III Original Android Development] swent:
2: Colors are not crappy, with the color calibration engine built into this kernel, it has been set up to provide most natural colors. Yes, indeed this means that the colors will not look as vibrant and bright as stock. But thats intentional. There is nothing wrong or broken with the colors here. If you want to revert back to stock colors, just disable the mdnie register hook, that should do the trick (I hope).
[Galaxy S III Original Android Development] jumpers:
seems crappy for me. :D

tryied, but, white color like "blanc cassé", not real white, i dont know if you see what i mean.
[Galaxy S III Original Android Development] Code124Y:
i know what u mean, try yo increase the value under *Colour temperature* starting point is 6500K , change the 0 to 20K, and its white will be more white~

Sent from S3, power By Temasek'Rom and Kernel!
[Galaxy S III Original Android Development] jumpers:
better, but not realy perfect. must be tested on a stock rom, if there are real differences. :s
[Galaxy S III Original Android Development] Code124Y:
the rest can be tune your self anyway~

Sent from S3, power By Temasek'Rom and Kernel!
[Galaxy S III Original Android Development] ajayverma99:
i m trying to install PAC MAN ROM as secondary rom but it cant boot stuck on Pac man LOGO..

Tried FUSION rom latest builds. But same Stuck on ROM LOGO.

But Latest AOKP ROM working fine..

All three ROM Version 4.3.1

Please help .. Kernel using 1.7.5 GOOGY MAX

---------- Post added at 08:04 AM ---------- Previous post was at 07:20 AM ----------

One more After fresh install both roms working fine with default kernel but when i install to Googy max 1.7.5 again stuck on ROM LOGO

---------- Post added at 08:26 AM ---------- Previous post was at 08:04 AM ----------

Tried Only work on AOKP ROM 4.3.1 not on others..
[Galaxy S III Original Android Development] hisee:
Its working on temasek rom...

Even i trd on fusion rom its nt working
[Galaxy S III Original Android Development] ajayverma99:
So where is the problem in ROMS or KERNEL ?
[Galaxy S III Original Android Development] hisee:
Even i also dont knw.. But mostly its rom
[Galaxy S III Original Android Development] ajayverma99:
Two Roms with same problem .....?
[Galaxy S III Original Android Development] trein91:
Can't seem to turn off zram somehow. Unticking the box, and setting it manually to 0 zram size in the default.profile wont work. When I check using an app called "Zram Status" it still shows around 227MB zram. Weird as hell.
[Galaxy S III Original Android Development] qtwrk:
Reboot, and default profile is balance...
[Galaxy S III Original Android Development] ric69:
I tried ROM1 Neat Rom 4.1 and ROM2 CM 10.2 Nightly --> stuck at boot of 2nd rom here too

[edit] after a lot of test, it's working (don't ask me why it didn't work first)
[Galaxy S III Original Android Development] andrewwright:
I'm still on 1.7.3 and have alliance 4.1.2 stock custom and aokp 4.3 running ok.

1st rom alliance rom beta

2nd rom aokp 4.3 unofficial
[Galaxy S III Original Android Development] ajayverma99:
Dev please fix this issue.....

---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------

Some Problem in 1.7.5
[Galaxy S III Original Android Development] Maplobats:
I'm also having this problem with the latest fusion/PA/pacman roms. I am on a sammy rom for now unfortunately with no secondary for the time being. But I'll give up my preferred rom in order to keep this kernel. And it has been kind of amusing getting reacquainted with a sammy rom, there are some nice things about it. I might even keep it as secondary when I can get fusion or paranoid booting again.

Love your kernel, Googy! So much good work being done here.!:good:
[Galaxy S III Original Android Development] FadeFx:
That is quite strange, i run omega v49(first) and hellybean(second) without any issue. I suggest do a nandroid backup of your second rom from dualboot recovery and then a factory reset. If you get ot to work this way you can use titanium backup to extract your apps and data from nandroid.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] ajayverma99:
I have tried googy kernel 1.7.5 on single... Pac man, PA, Fusion. Without dual boot... But still stuck on Logo.... Work fine with default kernel...
[Galaxy S III Original Android Development] popoyaya:
Sorry if this has been answered before but I couldn't find anything. Is it possible to remove the Googymax splash boot screen?
[Galaxy S III Original Android Development] ajayverma99:
Try stweaks. App to remove
[Galaxy S III Original Android Development] FadeFx:
Abd you can not boot your second rom? Even after going to dualboot recovery dualboot options and format second rom data?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] ajayverma99:
I have tried with dual boot and without dual boot... But nothing happen....
[Galaxy S III Original Android Development] wollax:
... strange .... with rootbox as second I can install and use it without any problem .... I also made the exchange trick between first and second and then back again ... everything working fine.
[Galaxy S III Original Android Development] FadeFx:
My guess is you are doing something wrong, i cant say what, but ...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] xclub_101:
Things to keep in mind:

- many ROMs don't install OK when installed from externalSD

- some aroma ROMs don't install OK when installed as second.

Safest approach is to to install as first, get something running very well (in my case a Sammy) clone that to 2nd (and make it default). Then experiment from time to time with something else as first. Of course that writing a non-dual-boot kernel will make the 2nd ROM no longer accessible, but installing Googy back should fix things.

Some care is needed if one ROM is 4.1.x and another is 4.2.x or newer - you might end up with two different copies of the Googy settings, one in the root of the internal card partition, another one inside folder /0 which is the new point that gets mounted in android >= 4.2.
[Galaxy S III Original Android Development] FadeFx:
And NEVER install samy based 4 2.2 rom

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Maplobats:
Same issue here. I haven't done anything differently from what I have done nearly 100 times before. Fusion rom in particular wouldn't boot as primary, as secondary, as only rom after superwipe... I tried all of the usual things. The rom dev says it must be the kernel, but I'm not so sure that it is. I went back to an older version of that rom, and it works fine, just like it always has for me.

For now it has been fun going back to a sammy rom and re-discovering some of the cool features it has, and I got the older fusion as secondary.

Not blaming the kernel at all, but I'm also pretty sure I am not doing anything wrong.

Again, awesome kernel, and I'd rather change rom than kernel.
[Galaxy S III Original Android Development] Chugfrenzy:
Latest pac man nightly requires the kernel to add framework-pac to it's boot class or it won't boot. Any chance this could be added to this kernel cos I'm missing the dual boot like crazy? :)
[Galaxy S III Original Android Development] Millenium3:
Yeah guys... there's no issue with Pac-man ROM, only the framework-pac has to be added to the boot class of this kernel.

Surfing on XDA from Tapatalk in I9300. now Free[/QUOTE]

Surfing on XDA from Tapatalk in I9300. now Free
[Galaxy S III Original Android Development] Maplobats:
Surfing on XDA from Tapatalk in I9300. now Free[/QUOTE]

I suspect this will be the issue with fusion rom too.
[Galaxy S III Original Android Development] Andro Boy:
Thank you veeeeeeeeeeeeery much man , it's really awesome kernel :)

make it better and better ;)

Hope it can support 4.2.2 ROMs or the next 4.3 KitKat :D
[Galaxy S III Original Android Development] ajayverma99:
I do not have problem in previous build of ROMS. I m talking about new build Android 4.3.1 .

And Rootbox is based on 4.2.2. .....

---------- Post added at 04:52 AM ---------- Previous post was at 04:50 AM ----------

Yes ... My Phone stuck on ROM LOGO (START UP ) as second ROM.
[Galaxy S III Original Android Development] Pinage:
ANyone encounter problem whereby the phone get hot easily when playing games like miniclip pool? Previously I don't have such issues. Currently using 1.7.5 and slimbean 4.3.
[Galaxy S III Original Android Development] jumpers:
installed the I9300XXUFME7 rom as second rom, but, it's sloooooow. unusable. cannot configure the device, cannot set my pin due to slowness. how to fix, i want a stock rom as SECOND rom. :(
[Galaxy S III Original Android Development] Kelgough:
I all . i have a question for you.... Can I install miui official ROM like second ROM?? It's based on android 4.1.1.

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Original Android Development] ktmbikerman:
that's because I9300XXUFME7 is 4.2.2 which is not supported by this kernel
[Galaxy S III Original Android Development] jumpers:
ah ****. :( flashing a 4.1.2 rom. :/ UFME7 seems a good rom. :(
[Galaxy S III Original Android Development] Chlorophyll:
wen 4.7.6 gonna come out DEAR AUTHOR?
[Galaxy S III Original Android Development] asdf20:
Yes, you can. I've installed it once.
[Galaxy S III Original Android Development] sizzlers:
Can you guys implemented the zzmove yank battery and zzmoveyank extreme battery ?? in the zzmove profiles
[Galaxy S III Original Android Development] ajayverma99:
Dev please fix... 4.3.1. Boot issue....
[Galaxy S III Original Android Development] Nichie:
Please read. For 4.1.2 only
[Galaxy S III Original Android Development] ajayverma99:
Are u joking....? This kernal support. 4.12. And cm10.2.... This. Is Googy max.. Not Googy simple...
[Galaxy S III Original Android Development] cba1986:
I am using this kernel without a problem in latest Temasek (V57).

This kernel does not support fusion's like PAC-MAN.
[Galaxy S III Original Android Development] ajayverma99:
I know.. Its working on some 4.3.1 Roms... But not working. On fusion, Pac man and Pa latest builds....
[Galaxy S III Original Android Development] StephenC82:
I'm also using 4.3.1 with this kernel no problems.
[Galaxy S III Original Android Development] ajayverma99:
Which Rom?
[Galaxy S III Original Android Development] StephenC82:
Cm10.2
[Galaxy S III Original Android Development] ajayverma99:
Good... I have currently running aokp 4.3.1 latest build but i have to install fusion and pac man rom......
[Galaxy S III Original Android Development] Kelgough:
But I have see a WiFi issue... You have this problem?

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Original Android Development] cba1986:
Because those ROMS require some modifications on the kernel side due to framework changes.
[Galaxy S III Original Android Development] asdf20:
No. Wifi worked perfectly.
[Galaxy S III Original Android Development] elhugo3:
I'm on slim bean 4.3.1 -1.8 and everything ok

Enviado desde mi GT-I9300 usando Tapatalk now Free
[Galaxy S III Original Android Development] kokomen:
No probam support...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Nichie:
If you are using CM rom then say so. Don't just say 4.3.1
[Galaxy S III Original Android Development] nnchoudhari:
Read 2 posts above yours. Its rom issue. Probam is based on pacman so need additional framework file to work with the kernel.
[Galaxy S III Original Android Development] davtse:
at this point 4.3 means CM/AOSP/AOKP roms. The official samsung Rom hasn't been launched yet.
[Galaxy S III Original Android Development] danielbr14:
Hi . i have a problem with stweaks and i was wondering if you could help me. i have installed googy max and every thing went fine but when i luanch stweaks it says "unexpected error" if you could help me that would be great.
[Galaxy S III Original Android Development] 4rch0:
have you the latest busybox?
[Galaxy S III Original Android Development] ronmq:
Um..... I was using this kernel with Probam for more than 1 week without boot problems... Worked perfect. Just flashed PROBAM, regular reboot. After that, from recovery I installed the kernel and no problems at all.
[Galaxy S III Original Android Development] danielbr14:
i am using cm 10.1 and i dont have any problem with the kernel it is just that the app(stweaks ) doesnt work and i dont know why . so i cant change the settings.
[Galaxy S III Original Android Development] FadeFx:
Do not install any busybox, the kernel brings its own version that is needed for stweaks to work.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] danielbr14:
Good to know. But now i dont know how to uninstall it . and i tried to throw the busybox installer. Any guides or somthing that can help me ?
[Galaxy S III Original Android Development] FadeFx:
Uninstall the busybox installer and reboot

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] danielbr14:
Thank you ! You hrlped me alot ;)
[Galaxy S III Original Android Development] jinosong:
Anyone else experience a click noise during startup? I disabled the startup sound so I can finally hear it. It's new because I never heard it before.
[Galaxy S III Original Android Development] ktmbikerman:
I think there may be some confusion when changing to this kernel from another kernel or visa versa

Always flash the rom again before flashing a new kernel, otherwise you will end up with a boot loop.
[Galaxy S III Original Android Development] kokomen:
I think its depends if the Rom flshed has its own kernel, so you cant flash it again. Am I wrong?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] ktmbikerman:
The rom will always have its own kernel... the custom kernel overwrites the roms kernel, but you cannot change the kernel safely without flashing the rom first (it might work, but chances are good that it wont)
[Galaxy S III Original Android Development] Maplobats:
Just to be clear, are you saying to reflash the ROM again before flashing this (or any custom) kernel? I've never heard of this, and I've never done it...generally without problems.
[Galaxy S III Original Android Development] salman_dude:
pac man rom doesn't work with this kernel

i tried on 2nd rom stuck at startup

then i tried on 1st rom work perfect but googy kernel no more then again i flashed googy kernel>pac man stuck at startup

may be this kernel not supported for pac man
[Galaxy S III Original Android Development] ktmbikerman:
That's correct... If you've never had problems you're lucky. An example would be if you flash Temasek's Rom and Temasek's custom Kernel and want to change to Googy's Kernel... if you flash Googy's Kernel directly on the Temasek Rom and Temasek custom Kernel, you'll bootloop. Temasek himself has also highlighted this.

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

Did you follow the procedure on Post 3?

DUAL-BOOT :

IMPORTANT : It is highly recommended to have Sammy as 1st rom and CM as 2nd (best stable combination) !!!

- Install 1st rom the usual way

- Flash Googy-Max Kernel

- Install stweaks from PlayStore

- Go to Dual Boot tab and reboot into 2nd rom utils (the phone should reboot immediately to "special recovery")

- On "special recovery" Go to dual boot options

- If it's the first time you install a 2nd rom, you must initialize the filesystem by wiping 2nd rom

- Always on "special recovery" Dual Boot options, flash all needed zips

- Reboot and enjoy!
[Galaxy S III Original Android Development] janika25:
Not support :(

I try, but no work
[Galaxy S III Original Android Development] FadeFx:
Just wait, pac rom support is planed but not yet implemented. However, we already know what to do, so if it doesnt break anything it will be in next version.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] janika25:
I look forward cheers!
[Galaxy S III Original Android Development] DienoX:
[MENTION=1897326]googy_anas[/MENTION] the next version will complicated on GCC 4.8.2?

http://www.phoronix.com/scan.php?page=news_item&px=MTQ4NzA
[Galaxy S III Original Android Development] salman_dude:
ok i want to flash pac on 2nd rom but can't,we'll wait for next version
[Galaxy S III Original Android Development] IamIrene:
noob question

can dual boot MIUI as secondary ROM ?
[Galaxy S III Original Android Development] davtse:
What is the MIUI base? Stock sammy or Cm? In both cases it should be no problem, as long as it's within the Roms supported in OP.
[Galaxy S III Original Android Development] IamIrene:
both also not belong

MIUI is look like below link

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

its 4.2.2
[Galaxy S III Original Android Development] -lorenzo-:
maybe a noob question... i followed the tutorial in 1st page (install sammy, root, flash googy kernel and wipe 2nd rom before installing) and successfully installed cm10.2... i got stuck updating cm, i used CyanDelta updater and got a bootloop... is there a way to change rom to boot in this cases? for the moment i just reinstalled all and waiting to get again cm

ty in advance and thanks to googy for all the efforts, it's a fantastic kernel, i like so much profiles and the possibility to choose sound engine :) keep up!
[Galaxy S III Original Android Development] sewer56lol:
Yeah the current 1.7.5 is not the best option for PAC.....
[Galaxy S III Original Android Development] Chlorophyll:
am experiencing wifi disconnectivity frequently.hope this wil be fixed soon in the new version
[Galaxy S III Original Android Development] FadeFx:
And what makes you think its a kernel issue?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] funeralcrows:
Because my WiFi keeps reconnecting to the same hotspot every 5 or 10 minutes too. Could be an issue. Or maybe just me and him.
[Galaxy S III Original Android Development] Chlorophyll:
S am with u.. Same here.. Same issue. Someothrr guys also complained abt this few days back

Pls fix this in da next release. It's really annoying

tapatalked :) :) GalaxyS3 ;)
[Galaxy S III Original Android Development] daniel98:
I dont think thats because of the kernels. I have the S3 from the latest batch and wifi doesnt connect for me. I think samsung did some minor modifications to the S3 in the latest production batches
[Galaxy S III Original Android Development] davtse:
In the OP of that thread, the add-on is a Googy-max kernel, so I'm assuming it can be used.
[Galaxy S III Original Android Development] churrolakra:
Hi [MENTION=1897326]googy_anas[/MENTION] and everyone

I really love the kernel, awesome features, and most important, it keeps our s3 support alive :D

I ve used siyah since I ve bought the phone. I ve switched to googy because of cm 10.2 support and the new features.

However, I find the kernel laggy on gaming.

I ve run many test. Using Return to castle wolfenstein port, Nova 3, and GTA VC (+fps meter). While on googy there is allways some fps decrease and games dont run perfectly smooth all the time. Its very strange because both kernels share a lot. I ve configured both kernels with almost exactly the same stweaks options, and on siyah games runs perfect while in googy fps decrease.

I am missing something? What would you recomend me to do? I want to switch to googy but this is keeping me on siyah.

Maybe zram, swap, or something like this is causing this?

it has happened to me with LOTS of googy max different versions, not only 1.7.5

Thanks in advance and keep with the good work! (sory for my english)
[Galaxy S III Original Android Development] FileFixer:
Try to disable zram, OC to 1600 MHz and UV to -50mV. Anyway... GENTLE FAIR SLEEPERS to be disable like Android logger and use zzmove-performance as governor.
[Galaxy S III Original Android Development] nkirk:
Disable zram. you will be good to go.

//nkirk
[Galaxy S III Original Android Development] janika25:
When is the next one?
[Galaxy S III Original Android Development] FadeFx:
Dont ask!!!

You should know that this is the forbidden question...

But soon...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] qtwrk:
Same here, I am pretty sure, as matter of fact, 100% sure... I don't have any other CPU application to override Stweak. But it just went up to 1600, for only 2 seconds indicated by CPU Spy

As for aggressive governor as LulzactiveQ, there is no reason it would only up to 1600 first only 2 second while it run on 1400 about 3 minutes... that doesn't make sense...

And please forgive my greediness, is it too much ask for both slide2wake and touch wake? :p
[Galaxy S III Original Android Development] nhb13612:
Only two cores are running (cores 1 & 4) at all times. Cores 2 & 3 are always offline with the latest build.

Edit: Sorry, my bad. I should have waited for everything to stabilize first. All 4 cores are running now.
[Galaxy S III Original Android Development] D@vIcHoJD:
I not have this problem, the cores working when is necessary.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] guastucci:
How zzmove governor works? Thanks.