yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] PedroMedeiros:
[MENTION=1897326]googy_anas[/MENTION]

Under defaulf.profile configuration file under /data/.siyah I saw:

scheduler=cfq

int_scheduler=row

ext_scheduler=row

In applications like setcpu I saw scheduler configured as cfq. So, what means "scheduler=cfq" under stweaks configuration file? We can't change this value under stweaks application but we are able to change int and ext sdcards schedulers. I am confused!
[Galaxy S III Original Android Development] DaReDeViL:
Nope, no kernel features change, only few ramfs fixes. It's working correctly (except the bugs of cm10.2 of course)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] Scarface1991:
Wow fantastic news! :)
[Galaxy S III Original Android Development] DaReDeViL:
The scheduler=cfq is a useless parameter which I forgot to remove...

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] Scarface1991:
Will the new Kernel still work with CM10.1 or will it only be compatible with CM10.2?
[Galaxy S III Original Android Development] DaReDeViL:
For the moment, cm10.1 and cm10.2 use the same kernel, so they are both working well. Let's just hope it will stay that way because adding a separate support means a lot of work

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] DaReDeViL:
Actually, the problem I had to solve is the stopping of the process phone.android

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] Scarface1991:
I suppose you were able to solve it? :)

Gesendet von meinem GT-I9300 mit Tapatalk 4 Beta
[Galaxy S III Original Android Development] DaReDeViL:
Yeah, as I talk in the past ;)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] PedroMedeiros:
After set both int and ext storage schedulers to "row" and click on "set IO-Schedulers", SetCPU app shows row as activated!

But, whenever I reboot my phone, setCPU reports cfq.

I am on 1.6.1. Is that ok?
[Galaxy S III Original Android Development] DaReDeViL:
No, that's not ok! You just found a bug :(

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] andrewilley:
I've just done a quick one hour test, and deep sleep using 1.5.2 is a much healthier 95%, compared to barely 70% on 1.6.1. I'll hopefully have a more meaningful comparison in the morning, after a midnight-8am test as that's when a number of timed background tasks are also stopped on my phone.

But initial results do show that something has changed in more recent versions of the kernel that is causing what I think is some sort of Wi-Fi wakelock issue.

Andre
[Galaxy S III Original Android Development] DaReDeViL:
Check your pm, I'll send you a test version

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] PedroMedeiros:
we are here to help and report bugs ;)
[Galaxy S III Original Android Development] DaReDeViL:
Thank you (even if it gives more work to do -with pleasure-) ;)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] skassa22:
Someone have a problem with a cpu clock going down at 800mhz with a Samsung rom when the processor goes under stress?

Try antutu test 5 times better if overclock at 1600mhz and monitor cpu with a PERFMON apk.

I found another member "jmgg2k" have same problem and and these are his assumptions:

"i found that the real throttling problem is a security protocol that Samsung roms have. When the battery reach 41C the cpu throttles (no matter if its only at 60C cpu temp)

i dont know how to deactivate that protocol...but if you want, try CM10.1 or any other AOKP or AOSP roms and you´ll see that there is no cpu throttling unless the cpu reach 80C.

you´ll need "stability test" app (cpu stress testing, and you can watch battery temp), and "system tuner" app (to watch live cpu temp during the stress test)"
[Galaxy S III Original Android Development] andrewilley:
Thanks, I've just flashed it and I'll test it with overnight idle.

Andre
[Galaxy S III Original Android Development] andrewilley:
Thanks for the test version, I can confirm that the modified wi-fi driver solved the problem. 96% deep sleep during five hours overnight idle, and just 1%/hour battery drain. Thank you!

Andre
[Galaxy S III Original Android Development] MewCore:
Sweet f##k googy, I'm trying out this kernel and sound implementation is just superb, its like having new earphones! Crisp and powerful!
[Galaxy S III Original Android Development] jinosong:
That's great news. Hope to see the new version very soon.
[Galaxy S III Original Android Development] xclub_101:
Well, no longer in a boot loop

I managed to get the 1.6.1 build and - unlike the previous set of 3 consecutive builds that I tested before - this one managed to start fine. Power consumption seems a little worse (especially during night) and the colors are 'strange' - but other people already noted that.

In the meantime I must make another correction to one of my previous posts - some other poster here on xda sent me a pm with the news that finally CM managed to fix their stupid vold bugs and they are no longer damaging sectors on exFAT - and to my surprise that was true - only about 12 months after the initial reports of the bug - but at least it is fixed now! :rolleyes:
[Galaxy S III Original Android Development] FadeFx:
We all feel sorry for you that it took so long, i will ask codeworkx, probably you get a 50% refund of what you payed to use cyanogenmod.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] davtse:
hahahaha why stop at 50%! 100% or no go!
[Galaxy S III Original Android Development] mcbyte_it:
v1.6.0: colors washed out

Is it only me, or since the kernel v1.6.0 the screen colors seems a bit washed out? I went back to v1.5.8 and colors are back to being vivid, reflashed v1.6.1 and colors are again a bit dull.

Any way to fix this, maybe some options in STweaks?
[Galaxy S III Original Android Development] riso123:
Sorry if asked already, but anyone else get choppy sound when the phone is sleeping?
[Galaxy S III Original Android Development] dantheman122:
Turn off register hook and master sequence in mdnie tab.
[Galaxy S III Original Android Development] davtse:
master sequence. You can read up on it in the perseus thread. Disable it to get back samsung stock colours
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.6.2 ONLINE !!! ;)

[30/07] Version 1.6.2 :

- Fixed compatibility with

CM10.2

! :good: :good: :good:

- Linux : Updated to

Linux 3.0.88

:good:

- Updated Net drivers to match CM ones

- Stweaks : Fixed IO-schedulers reverting to cfq after reboot
[Galaxy S III Original Android Development] jinosong:
Awesome! Thanks for your great work.
[Galaxy S III Original Android Development] brujo55:
awesome,i try later in cm10.2
[Galaxy S III Original Android Development] andrewilley:
The colours are more ACCURATE and less over-saturated, if that's what you mean? It's like 'Movie' mode on TVs, less saturated and more realistic for watching in lower lighting conditions - but as that doesn't stand out in the showrooms, they provide default retina-searing 'Dynamic' modes too.

However I tend to agree with you that accuracy perhaps isn't all that desirable on a phone, where you may want the image to push through in bright sunlit conditions, so I turn it back to Samsung default via STweaks.

Andre
[Galaxy S III Original Android Development] TSO of Stormwind:
downgrade?

I went from siyah 1.9.1 default settngs to googy max 1.6.2 and my antutu decreased from 15800 to 11000... is that normal?
[Galaxy S III Original Android Development] MewCore:
Try zzmove balanced. Got me 16000+ at 1,4ghz
[Galaxy S III Original Android Development] xclub_101:
Right ...

Thank you for all your time you've spent working on this for us.
[Galaxy S III Original Android Development] Gassity:
Sure it is normal.

Synthetic tests mean nothing
[Galaxy S III Original Android Development] TSO of Stormwind:
I'm aware of that. Still it is a quite substantial loss.
[Galaxy S III Original Android Development] Kelgough:
hi all. can i install a cm10.2 like second ROM and Paranoid Android for first?

don't kill me for my english!!! XD
[Galaxy S III Original Android Development] davtse:
It's not just free, it's open source. If you can contribute to development by fixing the very things you're complaining about so rigorously, please do so. Otherwise, move along. We don't need another person clogging up the threads with useless ranting when there are other people who genuinely need help.
[Galaxy S III Original Android Development] dantheman122:
Just tried 1.6.2 on temaseks CM10.1 but wifi is saying Authentication Problem and won't connect. I did change my settings to Static IP to try something else but I put it back and still no luck. 1.6.1 was working but isn't when I go back to it, can try a reflash of rom to rewrite the wifi drivers then try again maybe?
[Galaxy S III Original Android Development] c0manche:
Getting 15147 on zzmoove-battery

15292 on zzmoove-ballanced and

15561 on zzmoove-performance

Thats good in my book
[Galaxy S III Original Android Development] peramikic:
I hate to shoot my self in the foot but this was last night on 1.6.1 on Tema's V116 and tweaked pegasusq UV/OC/ABB/greenify/freezing/no wallpaper...

I'll check 1.6.2 tonight but this is getting nandroided as my base
[Galaxy S III Original Android Development] PedroMedeiros:
With cpu@1600MHz on zzmove-performance and gpu@160-533MHz I got 16984 on antutu :D
[Galaxy S III Original Android Development] jinosong:
You turned off your data connection. Of course, you're going to see good battery life under those circumstances.
[Galaxy S III Original Android Development] PedroMedeiros:
I tested 1.6.2 and I saw that the io scheduler bug I reported yesterday was fixed :D

I duplicated default.profile to another file called powersave.profile. Now, by typing this code I can switch between profiles:

echo "powersave" > /data/.siyah/.active.profile
sh /res/uci.sh apply
echo "default" > /data/.siyah/.active.profile

with that, my phone always reboot with default.profile selected ;)

if I want to go back to my performance profile:

echo "default" > /data/.siyah/.active.profile
sh /res/uci.sh apply

Now I want to ask a question: Are you able to create a widget that on click it applies a stweaks profile? Alternatively, do you know any program who supports widgets that are able to execute shell scripts with root privileges? Thanks for your good work! :D

---------- Post added at 08:00 PM ---------- Previous post was at 07:46 PM ----------

I have good battery life with 1.6.1 (5h40m on screen, no wifi, no data, UV, cpu@1400 zzmove-battery, gpu@108-440) and with 1.6.2 the same time (5h30m - 5h45m).

One day, with perseus, I got 8h15m on screen with cpu@600 pegasusq, gpu@108-266, no data, no wifi, -100mV on CPU and GPU, other power-saving tweaks, now I prefer performance :D
[Galaxy S III Original Android Development] FadeFx:
You could do all this within tasker...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
Why search away when Stweaks can do the trick ... I think it's time for me to think about config profiles ;)
[Galaxy S III Original Android Development] FadeFx:
Sure this is an option, but can stweaks put a shortcut to profiles or even a widget to switch profiles? Tasker and shellscripts can do all that and more...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
The best combination is to have stweaks manage (set-modify-save) profiles and simplify application with tasker

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] TSO of Stormwind:
Does the kernel lower average auto-brightness? If that so, is there a way to put back to stock values/increase autobrightness?

Also why touch to wake instead of slide to wake? Having a gesture to wake the screen up without any physical button was the main purpose of the feature, to avoid wake-ups in your pocket...
[Galaxy S III Original Android Development] DirkStorck:
Hi. I think you could achieve this with SManager (ScriptManager).
[Galaxy S III Original Android Development] zodiaxe66:
[MENTION=4179740]droidphile[/MENTION] who made the stweaks-profile app, for backup & restore of profiles, will update/rebuild his app when he gets some spare time, maybe he will add a toggle profile widget if someone asked him..

I'm gonna suggest it in his thread..

V.162 seems great so far.just flashed it an hour ago..

For those who dislike the master sequence,download trickster mod app..

Set everything on except chroma saturation control turn off, factory cs on..

White color temp -on

And set offset to 7..

On my phone that setting is near perfect..
[Galaxy S III Original Android Development] PedroMedeiros:
I will try tasker, thanks ;)

Many people dislike master sequence (I love it!), so because of that kind of people I suggest to disable/untick register hook and master sequence by default on kernel configuration ;)
[Galaxy S III Original Android Development] Steccas:
Hi guys how can I toggle the mdnie sharpness ks? From 1.6.0 the option to disable them disappeared!
[Galaxy S III Original Android Development] DaReDeViL:
Hi dear users,

As you have surely noticed, Googy-Max kernel has been granted access to XDA's Development Database (DevDB). I hope you like the benefits of new project layout.

What's done so far :

- Imported the thread to the DevDB

- Download section open (Version 1.6.2 uploaded)

- Reviews section open ( [MENTION=4600457]rafaelpernil[/MENTION] already discovered it ;) )

- Changelog moved to the project's 1st reserved post

- "Donation" button updated with working paypal account

To do :

- "How-to" section

- "FAQ" section

Thank you ALL and thank you XDA !!! ;)
[Galaxy S III Original Android Development] FadeFx:
So finally we can donate to you? Expect some coffee soon. (I guess you don't drink beer...)

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] dyval:
A great developer loke you deserves it. Thank you Googy.:good:

---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------

You deserve it my friend. Thank you Googy.:good:
[Galaxy S III Original Android Development] DaReDeViL:
:angel: no, only coffee or Moroccan tea ;) (it's the thought that counts!) Thank you
[Galaxy S III Original Android Development] DaReDeViL:
Thank you :highfive:
[Galaxy S III Original Android Development] reinerlee:
There's a problem while using Zzmoove-performance, on 1.6.1

I've set my Max CPU @ 1600Mhz. no undervolting.

While I'm playing Real Racing 3 about 15mins, it's quite laggy, then when I jump out from there. And I checked on CpuSPY.

The only utilized clock speed was 800Mhz.

I wonder why it won't jump to 1600Mhz in such case.

No problem on Pegasusq. 1600mhz was running well.
[Galaxy S III Original Android Development] DaReDeViL:
Oh, that reminds me of the problem faced by [MENTION=4091828]skassa22[/MENTION] ! I didn't suggest him to change governor ... Nice find from you ;)

I wasn"t able to reproduce the problem with pegasusq, now I will test with zzmoove
[Galaxy S III Original Android Development] chrismast:
kernel running stable as always! gave you also a review ;). keep up the good work!
[Galaxy S III Original Android Development] tomi555:
I have a similar problem with 1.6.2. Dual-booting, primary rom Temasek's CM10.1 and wifi is working great, but on secondary Omega Rom, tried v43.1 and v43.8 wifi is very weak and cannot connect (Authentication error / Incorrect Password). Tried reflashing, wiping etc. but nothing helps.
[Galaxy S III Original Android Development] reinerlee:
Hey googy, I'm now having the same issue with PegasusQ.

- Set 1400mhz as max CPU. no undervolting.

- Set TouchBoost with 800Mhz/1200Mhz. even on 1200Mhz touch boost, the CPU just won't go over 800mhz. seems like the CPU just love sticking around 800mhz.

Update:

Just flash back to 1.6.0, everything's fine, the CPU able to push up to 1400mhz.

seems like the CPU Limit by Yan555 is locking the CPU.
[Galaxy S III Original Android Development] cKenny:
[MENTION=4600457]rafaelpernil[/MENTION]

dont leave the stars blank, color them if you really love this kernel :p
[Galaxy S III Original Android Development] Yank555:
I think you just run into thermal throttling, no matter what governor you use, once a certain internal temp is reached, Cpu will be throttled for the whole device to cool down. Depending on the governor this can happen slightly sooner or later.

Maybe playing with the device in a fridge might give you longer gaming sessions, but you might catch a cold, though :D

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta4b (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] reinerlee:
Not really, Even I've restart my phone, the temp is about 35'C.

I'm flashed back to GoogyMax 1.6.0, everything's fine at the moment.

I'm using PureHD 7.0 rom.
[Galaxy S III Original Android Development] Yank555:
What temp are you looking at, battery or cpu, those show different values.

Also rebooting will make it cool down as gpu can rest over the whole process.

Games that run fine for some time and then lag run into thermal throttling...

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta4b (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] reinerlee:
Yank555:

Nope, the game not running fine even from a cold start. just laggy and choppy.

In normal operation (not running any heaving apps) By right: if I enabled touchboost with 1200Mhz, the CPU should clock at 1200mhz when I touch the screen (If i'm not wrong :fingers-crossed: ). while i check on CPUspy, nope, not even 1 sec 1200mhz was activated.

As previous post, I've switched back to 1.6.0 which without the CPU limit, the CPU clock is alright, no problem for gaming, even after few races.
[Galaxy S III Original Android Development] Androguide.fr:
Awesome kernel, thanks a lot for your work.

I am trying to add support for the Ubuntu Touch builds I'm maintaining, however I noticed that your toolchain wasn't up-to-date in your repo (the linaro toolchain is still at 4.6.2).

Are you using the stock 4.7.3 linaro toolchain or did you do some ramblings/modifications? If you did, could you please upload it?

I'd also need some enlightenment on the dual-boot feature, can you please briefly explain how it works and where the related files live in the kernel tree, it would be very helpful.

Keep up the great work :good:
[Galaxy S III Original Android Development] FadeFx:
Donated: 1MT36742KF3727726

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Volpe92:
Hello, I wanted to offer my congratulations for this great kernel! :good::good::good:

And I wanted a help regarding the dualboot:

Practically can not seem to run WhatsApp on both rom, always asking me to verify the phone number, EVERY time I make reboot and choose to boot rom

thanks :)
[Galaxy S III Original Android Development] rafaelpernil:
I tried many times to give 5 stars in the review but I couldn't.

Enviado desde mi GT-I9300 usando Tapatalk 2

EDIT: I finally could do it but on my phone, on Dolphin Browser. On Google Chrome didn't worked.
[Galaxy S III Original Android Development] peramikic:
Here is a quick benchmark run on 1.6.1 an frequencies used. I'm OC'd to 1.6 CPU and 700 GPU but UV'd 125/100 CPU/GPU , withouth touchboost, no problem hitting all steps from
[Galaxy S III Original Android Development] skassa22:
I think that something can be done to adjust the cpu throttle through the kernel. the processor should go into the throttle at 78c but it goes much earlier with the rom samsung.The problem does not occur with the CM10 rom. the only one who has no problems is the siyah kernel 1.84 after this version the cpu throttle at 1000MHz until the last siyah 1.91. before Googy rewrite clock cpu routine the cpu throttle at 1000MHz but from 1.55 to 1.62 the cpu throttle at 800mhz. maybe it's something you find in samsung update source code.

Sorry for my english i translate with Google translator.

---------- Post added at 03:04 PM ---------- Previous post was at 02:58 PM ----------

Try the test with siyah kernel 1.84 and cpu no throttle. Same rom with any governor.

I found another member "jmgg2k" have same problem and and these are his assumptions:

"i found that the real throttling problem is a security protocol that Samsung roms have. When the battery reach 41C the cpu throttles (no matter if its only at 60C cpu temp)

i dont know how to deactivate that protocol...but if you want, try CM10.1 or any other AOKP or AOSP roms and you´ll see that there is no cpu throttling unless the cpu reach 80C.

you´ll need "stability test" app (cpu stress testing, and you can watch battery temp), and "system tuner" app (to watch live cpu temp during the stress test)"
[Galaxy S III Original Android Development] noobSU:
Ehm. Dual boot option. New to me :silly: Never tried Siyah nor Googy, Going to give a try to Googy Max now.

Anybody can tell me Basic things how to Dual boot? I have read somewhere is to hijack the recovery option in Stweaks? It'll hijack the recovery without flashing another recovery over it? Then i can Swap primary & secondary roms? over there or If using Dual boot but only one rom. How can i flash the 2nd rom? :s Confusing me. Sorry i did search but didn't find something well explained :s Didn't find FAQ as well.
[Galaxy S III Original Android Development] davtse:
Not a kernel issue. Whatsapp doesn't allow you to use it on more than one phone, and it recognises the dual ROMs as 2 phones.
[Galaxy S III Original Android Development] noobSU:
Need your help mate on my above post :D
[Galaxy S III Original Android Development] DaReDeViL:
Oh, thank you very much.

Unfortunately, I can't drink this coffee now, I have to wait for sundown (ramadan!) :D

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] noobSU:
Wow A Muslim Dev. :cool: Proud & Kudos.
[Galaxy S III Original Android Development] davtse:
Sorry man, don't dual boot. LOL. Someone else will have to help you with this. I used to with siyah on my s2 but whatsapp doesn't work for dual booting so i stopped. Anyway the s3 I always use googys kernels with has died :( so I won't be able to experiment as much as I would like to.
[Galaxy S III Original Android Development] DaReDeViL:
There's a workaround: install and activate whatsapp on 1st rom and back it up with titanium then, on 2nd rom, after removing installed whatsapp, restore backed up version.

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4 Beta
[Galaxy S III Original Android Development] fknpwned:
best kernel so far :)

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] davtse:
Ah yes, but somehow TB messes with GCM for whatsapp and other apps... Maybe its changed since the last time I tested it though.
[Galaxy S III Original Android Development] noobSU:
But afair somedays ago you were dual booting? & What? Your S3 has died? So don't you have s3 now? :eek:

---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------

GCM? A push service? If it is Actually that is not TB that messes up push notifications for the apps. TB just restore the app as it is it backed up. But C2DM works in the way that sometimes it itself messes up when the app is restored. It takes sometime to be register the newly restored app onto the servers. Sometimes First run do that. Sometimes It takes sometime. TB has nothing to do with it AFAIK.