yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Yank555:
Cough, cough you seem to have a pretty bad memory for someone telling others what I did on my kernel repeatedly... CMA_DMA is still active in my kernel, never tuned it off, except for one single subversion to check something long long time ago.

Oh and, cough, cough, you didn't look well enough obviously, the sources of my kernel up to how it was last published on xda have always stayed publicly available (expected you to find that one, without needing a hint, hint, github doesn't have the monopoly on online git repo offerings, repo created 2013-03-07).

And in the meantime --> I have zCache and CMA_DMA working just fine, since I never turned off CMA_DMA, yes I upstreamed properly past .39 keeping CMA_DMA working fine from the first time as well, btw, the commit was easy and is still there for anyone to use.

Now back to topic :

What's your take on the fact that other swap kinds seem not to be affected by your guess (the memory leak) ?

JP.

PS: I agree that the 50 apps JKay thingy is no good idea.
[Galaxy S III Original Android Development] romskii:
What do you mean by 50 apps Jkay thingy?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
With JKay framework you can increase to have up to 50 apps in memory.

JP.
[Galaxy S III Original Android Development] AndreiLux:
Google doesn't know about it (Edit: I'm wrong, Perka mentioned the link 3 days ago on Twitter!); on Android-Hilfe you don't even link the source, and since you have a neat private forum to keep things hidden (Hello, Chad Goodman v2), you should excuse me for my lacking darknet detection skills, and maybe you should reconsider your definition of "publicly available".

That being said, I remember you disabling CMA DMA, I didn't bother to follow all of the many source rebases your did on every source drop, so I said I could have been mistaken.

Anyway you just said yourself that you never reached zRAM saturation (>90% virtual disk use). So I don't know if the problem actually doesn't exist or you simply weren't able to trigger it; the 50 app limit helps a lot in that regard.
[Galaxy S III Original Android Development] rlorange:
How did I miss this new kernel? Lol!

Man could you compile the next version with 4 zram devices? Running 4 parallel swaps is much faster as I discovered with my swap control app and would love to try it with zram...

Maybe leave just one device switched on by default
[Galaxy S III Original Android Development] Yank555:
You can proud yourself for being the reason for this, since you obviously have a history of not being able to mind your own business, like 99.99% of others do... but I won't get into debating your social skills, again ;) And don't say now I'm taking it to a personal level, you've started calling me Chad, that's a door you pushed open...

And by being on the internet, it is pretty public, except if there is more than one such internet I don't know of ??

That being said, you prove it once again, instead of helping in the zRam issue, your post is again mostly about attacking someone, me here, not that I'm not impressed I seem to matter that much in your mind that you spend so much time thinking about me obviously :D

Eventually we can discuss the topic at hand again. The thing is, people running into this issue do not all use JKay, nor do those using it have 50 app limit mod necessarily activated.

Also to reach saturation, something must be preventing it to be freed up, as I can't reach saturation because zRam swap is freed up all the time as well for me... and I've seen this happen on Sammy ROMs and CM ROMs.

So what I was trying to want to grasp is what else could trigger memory filling up like this, and as it seems to happen only when swap lies on zRam ? So I suppose the issue cannot be memory mgmt itself, else it would happen all the time, with any kind of swap, or even without any swap at all.

Compression algo cannot be a cause, since this happened as well using LZO as Snappy (correct me if I'm wrong here), at least on both I see no difference on my end, neither prior to updating LZO nor afterwards, so that makes 2 1/2 different compression libs.

Now, I'd really appreciate it if we could focus on this issue, rather than being a public laundry service to entertain the gallery here (again and again, it's slowly losing the fun of it by getting older) :rolleyes: So if you have nothing constructive to contribute, as well avoid posting altogether. Thanx.

JP.

Sent from my SlimBean 5 / Yank555.lu CM10.1 kernel v1.5n-beta6 (Linux 3.0.78) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] mitky82:
Can you post in first post versions with and without zram. Thanks ;)

GT-I9300 XXEMC3
[Galaxy S III Original Android Development] inscythe:
The downside is as I mentioned earlier, some extra CPU load. Depending on your own usage pattern, there might be some lag as well, as the fetching also takes a while as the data from the zram is decompressed before being used. In my case, if the suspended apps are recalled after a long while, or after using a relatively RAM-heavy operations, there will be some noticeable lag due to jumping to heavy zram usage.

Disk size is basically the size of contents that you can try to compress into the zram partition. Swappiness is the measure of how often you should put data into the zram partition. So, some rule of thumb, when you are roughly using most of the RAM as zram, you can even put 100% swappiness.

Since zram is all done within the RAM space, it won't affect SD card like swap does.

Googy-max is using 300MB with 80% swappiness by default. Try and play around as you use. Googy's using pretty fast compression method as well, so it is one of the best kernel to use zram with...
[Galaxy S III Original Android Development] mikailmohammed:
Hey how is this kernel working for you?
[Galaxy S III Original Android Development] Scarface1991:
[MENTION=1897326]googy_anas[/MENTION]

Will you switch to the Wolfson Audio engine on the next version? I mean since the Poll is going more and more towards Wolfson?
[Galaxy S III Original Android Development] SuperAce609:
I see. Thanks a lot. Just set it to 600MB to see if anything changes. I'll keep setting it higher and see what happens. Anything you specifically recommend?

---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------

This kernel is a definite upgrade from Boeffla. Even on default Pegasus q, it felt slow. But not here. Now trying to see how the zram works. Thanks for recommending

When applying the zram, a blank box appears at the bottom, right? Or should there be something in it.
[Galaxy S III Original Android Development] brunodu91:
I feel that this kernel is lot of battery drain !

Nothing awesome.

Row and smooze and 400 zram with 80%

No undervolting

Why in deepsleep is run on 800mhz too ?

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] SuperAce609:
Did you just flash it? The performance is really good.
[Galaxy S III Original Android Development] brunodu91:
No i flash it this morning

Why there is activity on 800 mhz ? I let mine phone sleeping few hours.....!

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] DaReDeViL:
Check BBS as you surely have an app causing wakelock and preventing the phone from going to deep sleep

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] DaReDeViL:
I need to solve the problem with cm where all the engines get broken after a while...

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] brunodu91:
OK i Will check this immediatly but i dont instal or modified anything before or after flashing this kernel this morning

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] DaReDeViL:
If you're using slim bean, some users reported also bad behavior with my kernel as the rom itself contains some tweaks not all compatible with the kernel. For good experience i recommend using stock cm

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] brunodu91:
Oups ! Thx googy !

Too bah because i feel that my phone is less hot when i use it a long time with yours kernel !

Googy

What is the Best set with my rom and zzmoove ? Row ? Cfq, deadline, noop ? For usage soft, no game and look for good battery saving ? Better deepsleep ?

Thx

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] SuperAce609:
What version of Stweaks are you using? Looks really cool.
[Galaxy S III Original Android Development] DaReDeViL:
The default settings are best balanced for good performance and battery life. There are no magic values to set, you need to try and find what suits your needs

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] brunodu91:
I try lutzactiveq and row X2

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] maazy:
Great kernel
[Galaxy S III Original Android Development] SuperAce609:
Weird, I just got a freeze and a reboot when playing Collapse. I have zram on 100% swap 1200MB. OC to 1600 stock voltage.

Also, after flashing this kernel I'm unable to switch keyboards unless I reboot. Anyone? I'm using Ultima rom V13.
[Galaxy S III Original Android Development] SuperAce609:
And now I can't switch keyboards at ALL. Is there something I can do?
[Galaxy S III Original Android Development] Siberian Tiger:
Try to reset settings to default and see if these issues persist. If not then change your settings :)
[Galaxy S III Original Android Development] SuperAce609:
You mean Stweak settings? But I've only messed with the zram though. And what type of settings do you mean? I ticked off one of the keyboards from the list in settings and it doesn't even change. It stays on after I go back to it. Not even the voice keyboard works.

Should I have deleted a type of cache before or after flashing kernel?

I can't check a keyboard even after installing a new one. It's as if all keyboard settings are blocked.
[Galaxy S III Original Android Development] :
@[MENTION=1897326]googy_anas[/MENTION]: what about bfq 6r2 scheduler? i'm running ubuntu 13.04 with a custom kernel with bfq and the performance is fine so far... did you update the row scheduler in the past 3 weeks?
[Galaxy S III Original Android Development] cKenny:
i know my question is silly, but please help to answer.

I'm using siyah kernel 1.8.9 with 1st rom sammy 4.1.1 2nd rom cm10.

recently cm10.1 m snapshot version was out and i happily flash it into my 2nd rom, and then it become unbootable.

for some reason, I cannot update sammy 4.1.2 on my 1st rom.

so my question is, is it possible for my S3 to have googy kernel with 1st rom sammy 4.1.1 + 2nd rom cm10.1?

if the answer is yes, do i need to do any setting other than flash the googy kernel?

Thanks.
[Galaxy S III Original Android Development] qtwrk:
Just follow the instructions
[Galaxy S III Original Android Development] peramikic:
Your phone was in deep sleep only 42% of the time, just because the screen us off it doesn't mean that it's sleeping. Check the kernel and partial wake locks in BBS to see what is keeping it awake, or try wake lock detector from the play store

Also, let one cycle pass after new flash for phone to "settle down" and use minimum 4 hours for accumulating stats in BBS
[Galaxy S III Original Android Development] SuperAce609:
So no one can help me with my keyboard problem?
[Galaxy S III Original Android Development] cKenny:
erm.. need to know whether i can have sammy 4.1.1 + cm10.1 with googy or not ...
[Galaxy S III Original Android Development] MuertoKo:
FIRST sentence in the FIRST post:

This kernel is ONLY for SAMSUNG 4.1.2 ROMS OR CM10.1 (or both ) !!!

Assuming you refer to 4.1.2....

So as the previous poster said, READ!
[Galaxy S III Original Android Development] DaReDeViL:
No, I really didn't have time to pick some new updates as I was most focusing on the audio bug on CM ...

Man, your problem is in no way related to kernel
[Galaxy S III Original Android Development] cKenny:
i did read that, just hoping someone will tell me yes it works / no it don't, in a nice way.

assuming you did read my post which stated i couldn't update my sammy rom 4.1.1 to 4.1.2 for some reason...

anyway, thanks for reply.
[Galaxy S III Original Android Development] MuertoKo:
Still, if you read it you should know it won't... And you must be able to update to 4.1.2 otherwise return your device to warranty, you will end up with a hard brick using 4.1.1... That easy

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] xperiax10mini:
Nice features !! , thank you Googy anas and thank you very much by your supporting and updating of the great scoobydoo sound engine, which gives your kernel unparalleled added value and makes your kernel even more special than it already is. The high-quality things should never change. On a good foundation you're building exceptional kernel . Awesome work

19/07] Version 1.5.7 :

- Linux : Updated to Linux 3.0.86

- ScoobyDoo Sound 1.1 : Fixed problem of Engine breaking on CM10.1

- ZZMoove : Updated to 0.6 (Thx ZaneZam & Yank555)http://xdaforums.com/editpost.php?do=editpost&p=43749612

- Stweaks : New Tabs for governors settings (ZZMoove - PegasusQ - LulzactiveQ)

- Vibrator : Added support for vibration intensity setting & added to stweaks-misc

- CM10.1 : Added SELinux support

- USB gadget: use two luns on devices with two cards

- UMS: Added cdrom option to UMS-lun-devices with 2048 block size

- Fixed adb and usb-debugging problems
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.5.7 ONLINE !!! ;)

[19/07] Version 1.5.7 :

- Linux : Updated to

Linux 3.0.86

:good:

- ScoobyDoo Sound 1.1 : Fixed problem of Engine breaking on CM10.1

- ZZMoove : Updated to 0.6 (Thx ZaneZam & Yank555)

- Stweaks : New Tabs for governors settings (ZZMoove - PegasusQ - LulzactiveQ)

- Vibrator : Added support for vibration intensity setting & added to stweaks-misc

- CM10.1 : Added SELinux support

- USB gadget: use two luns on devices with two cards

- UMS: Added cdrom option to UMS-lun-devices with 2048 block size

- Fixed adb and usb-debugging problems

Happy flashing and happy ramadan for muslims ;)
[Galaxy S III Original Android Development] DaReDeViL:
1.5.7 removed, no display on sammy ... please stay tuned for some minutes ... ;)
[Galaxy S III Original Android Development] riso123:
Ha ha! Was just about to ask if this was a known bug ;)
[Galaxy S III Original Android Development] xperiax10mini:
I have flashed 1.5.7 and now no display is black :( and and the recovery dont load :SSSS

can someone please help me?
[Galaxy S III Original Android Development] DaReDeViL:
Don't worry, just keep pressing up-vol + home + power, your phone will reboot to recovery

PS : corrected 1.5.7 uploading ...
[Galaxy S III Original Android Development] ThePureHeart:
I'm so glad I'm not using a Sammy ROM :P

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DaReDeViL:
VERSION 1.5.7 fixed and re-uplaoded
[Galaxy S III Original Android Development] brujo55:
is possible add fiops schduler?

i have now devil kernel in my s3 but want to try new googy kernel,but after flashing my rom not boot,why?

yes, i use kernel scrip s cleaner,nothing change.
[Galaxy S III Original Android Development] DaReDeViL:
please re-download 1.5.7, the first uploaded one was faulty
[Galaxy S III Original Android Development] spoonymoon:
Holy crap

You cant be serious goggyPlz be MUCH more careful and test test your releases first

Regards
[Galaxy S III Original Android Development] riso123:
Hey bud. Using the newely uploaded version that corrected the display, it now plays the samsung boot sound etc but wont go further than the boot display...
[Galaxy S III Original Android Development] DaReDeViL:
Holy ****

YOU can't be serious !!! When did I brick your phone or other users digitizers ??????? You are mistaken and should test what you want to say before typing it !!! Please be MUCH more careful

Regards !!!!!
[Galaxy S III Original Android Development] DaReDeViL:
Try to wipe dalvik cache
[Galaxy S III Original Android Development] riso123:
Else unable to fully boot past the Samsung boot logo in latest reupload?
[Galaxy S III Original Android Development] DaReDeViL:
Did you wipe dalvik cache?

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] tracemonkey:
1.5.7 working fine here
[Galaxy S III Original Android Development] davtse:
1) he has a team of brave beta testers that actually do test his releases. They can't test for every bug.

2) devs are people who make mistakes as well. No one is forcing anyone else to flash anything against their will.

3) everything on xda comes at a risk. If you don't want to take a chance, stick to stock. You can't have your cake and eat it.

Yes, I've bricked my s3 twice before and had to pay for repair as well. Its a small price to pay for cutting edge development.
[Galaxy S III Original Android Development] DaReDeViL:
Plus he is completely out of bounds, the problem he had with broken display was with another kernel (AGNi), not even mine, see here http://xdaforums.com/showthread.php?p=42380321#post42380321

[MENTION=4240596]spoonymoon[/MENTION] : if I were you, I would at least apologize ;) but I will live without it anyway ! :cool:

EDIT : I just got my screen replaced after shock damage, I think I should also blame you for that too !
[Galaxy S III Original Android Development] riso123:
Not to worry, it started working randomly now :s

Thanks loads.
[Galaxy S III Original Android Development] brujo55:
yeah,googy your kernel working like a charm!

also please consider fiops scheduler for next update!

thx
[Galaxy S III Original Android Development] DaReDeViL:
Great then, sorry for inconvenience

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] mdacic:
Will you also implement Color Calibration from Perseus kernel?
[Galaxy S III Original Android Development] _MirageX_:
1.5.7 changelog just made me... oh well Thanks a lot for this fantastic kernel once more.
[Galaxy S III Original Android Development] DaReDeViL:
We'll see, thx

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] DaReDeViL:
Come on, appreciate what you've got now :p

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] xclub_101:
1.5.7 still not working on Sammy :(

1.5.7 still not working on Sammy - reboots after a few seconds before I get to even enter the SIM PIN (both 1st and 2nd ROM).
[Galaxy S III Original Android Development] DaReDeViL:
Please go back to 1.5.6 and re-download 1.5.7
[Galaxy S III Original Android Development] xclub_101:
It seems to be the latest one :(

I already went back to 1.5.4 (which was the last one that was usable for me).

The one that I have has this MD5

Googy-Max-Kernel_1.5.7_CWM.zip 6be2218e6bd0ce2744424e50d6473d0c

and re-downloading it does not change anything in the MD5.
[Galaxy S III Original Android Development] brujo55:
ahhhhhhhhhh! magnific work.

1.5.7 is more faster and battery friendly.zzomoove 0.6 + tab settings awesome.

tested in my emulators.

large life to googy kernel.
[Galaxy S III Original Android Development] DaReDeViL:
I suppose 1.5.4 boots normally for you?

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] spoonymoon:
Ohh sorry goggy it wasent you but psndna88 agni kernels dev.

Again sorry sorry: P and thx so much for your nice kernel and great work - use it always nearly

Ps is 1.57 fixed for flashing now?
[Galaxy S III Original Android Development] xclub_101:
Yes, that one is booting OK both my current Sammy ROMs. My only complaint on that one is that sometimes after a boot the microphone is not quite working, but that is something that always starts working after a 2nd reset. (I test with stock voice recorder).
[Galaxy S III Original Android Development] DaReDeViL:
That's great from you, forget about the misunderstanding

Ps: it's googy not goggy :)

Ps2 : yes 1.5.7 is good now

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] robinlei78:
Does the new release actually work on omega rom 43.7???
[Galaxy S III Original Android Development] lukaaa47:
is selinux fully implemented or there are more commits to come?
[Galaxy S III Original Android Development] DaReDeViL:
SELinux is implemented now on kernel side, but in CM10.1 it is getting worked on ...
[Galaxy S III Original Android Development] xperiax10mini:
THANK YOU GOOGY :)

every things working now perfectly. 1. 5.7 fixed . is even more smooth , is clearly noticeable . Magnific work . Awesome new tabs in stweak , amazing

I hope that all people that use this awesome kernel from Googy , will be happy , because thanks to Googy anas our S3 phones are much better than they would , even better than some S4 :p
[Galaxy S III Original Android Development] lukaaa47:
so i cannot see predefined profiles for zzmove like on temaseks kernel, what profile would it be on default.. battery, optimized or performance?
[Galaxy S III Original Android Development] DaReDeViL:
The settings are all set to default values

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] brunodu91:
How to set this ? Could you explain to us googy ?

Thx

Envoyé depuis mon galaxy s3, rom slim bean à jour..... / 4.2.2 , Kernel stock , nova launcher, thème élégance orange ... via tapatalk 4
[Galaxy S III Original Android Development] Chlorophyll:
1.5.5 fine for me.

hi author.my s3 running slimbean

wen i flashed 1.5.6 i had errros with sound engine,so went back to 1.5.5 which is fine for me.

now 1.5.7 released gonna flash it.hope everything wil be fine.
[Galaxy S III Original Android Development] JB-007:
Hi Googy

Just download and install 1.5.7 on Wanamlite 6.6 but unfortunately doesn't work. I'm not able to boot with the latest version, got device reboot at device startup.

Try to re download, wipe cache and dalwik cache but no success....

Something strange, when back on 1.5.6 i lost all my wifi passwords and settings.

Cheers
[Galaxy S III Original Android Development] SuperAce609:
Should we ever wipe anything before flashing the kernel? I installed 1.5.7 & .6 without doing so. Will that generate any problems?
[Galaxy S III Original Android Development] beardymarrow:
There's no need to do any wipes, not even dalvik when flashing a kernel.

"There are only 10 types of people in the world, those who understand binary, and those who don't."
[Galaxy S III Original Android Development] SuperAce609:
Thanks. But I've noticed my phone is constantly around 110-115°F after flashing this kernel during normal use. Am I the only one?

I used Boeffla before this one.
[Galaxy S III Original Android Development] agentg1001:
I've noticed this too
[Galaxy S III Original Android Development] SuperAce609:
Yeah I just realized I had 1.5.6 yesterday and that didn't happen. Switching back until further notice

Edit: flashed back the previous version and played Sims for a while and temperature did not go past 111°F. I was doing more than with the new version and the temperature was actually lower.
[Galaxy S III Original Android Development] _MirageX_:
audio not fixed, still front mic does not hear any sound, at least with soundhound and a recorder app.
[Galaxy S III Original Android Development] ThePureHeart:
Anas, how comes some tunables are missing?

Sent from ThePureHeart's I9300 Boss Edition