yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] mitchpunk:
Googy my apologies! Last time I mentioned the notification sound and incoming calls breaking the audio.

I was distracted.

It was actually the mic! What was breaking my audio.

Here's an example

I had music playing on speaker and I was also using my keyboard when I accidentally touched the voice input key ...

So the mic thingy came up and the audio stopped, but then the audio didn't came back when I closed the voice input.

I paused and pressed play again and no sound would come up. Killed the music app and reopened and still not sound would come out until I rebooted my device.

I don't know if anyone else experienced this but it happened to me a couple of times

Sent from my GS3 Paranoid GT-I9300
[Galaxy S III Original Android Development] Perka:
Yea well, I have my init.d scripts and they dont work with this kernel, works fine with yanks and my own. :P
[Galaxy S III Original Android Development] FadeFx:
Thanx, we will have a look at this...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Chlorophyll:
Hi dude. Am with u. Had da same issue really bothering me lotttt.. Very badly

Hope this week be fixed in 1.6.9

This s my sincere request to take care od this issue.
[Galaxy S III Original Android Development] hisee:
Any one interested to help me.. Asking this qus from last3-4 days havnt got ans :(

While trying to swipe rom i am getting error 'nt enough space' available 0.00mb amd needed 0.00mb...
[Galaxy S III Original Android Development] iBuzman:
Sry mate; I've swapped back and forward two or three times now without any problems, so not sure what's happening. (I know this post isn't helpful but I thought someone should reply after 3 days of asking :)

Sent from another Galaxy...
[Galaxy S III Original Android Development] FadeFx:
You need up to 4 gig of space on your internal sdcard to swap roms, if there is not enough space you get that warning, it just does not display the correct numbers.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] PedroMedeiros:
You're welcome m8! ;)
[Galaxy S III Original Android Development] noel8211:
Hey googy-anas and fellow xda'ers. Congratulations on such a great kernel and a continuation of gokhans excellent work but I have a small problem. Hopefully someone can help me but I can't open Stweaks app to customise the kernel. I am using the latest version of the kernel and the last cm10.1 nightly. I have never had this problem before and a bit perplexed why its happening now. It just says 'unexpected error'. Any help will be appreciated guys and cheers in advance
[Galaxy S III Original Android Development] davtse:
go to /data and delete /data/.googy and /data/.siyah.

reboot to recovery and reflash kernel. Should fix that error
[Galaxy S III Original Android Development] PedroMedeiros:
Here with sammy stock 4.1.2, CM10.1 (slimbean 4.2.2 stable) and CM10.2 (slimbean 4.3 beta2) all works fine!

I have ticked register hook and master sequence and tweaked some values like in perseus to get natural colours (calibrated with professional equipment as said in perseus thread)...

So, your issue could be rom related...

---------- Post added at 01:39 PM ---------- Previous post was at 12:57 PM ----------

[MENTION=1897326]googy_anas[/MENTION] I know you are in holidays (real life ahah), I just want to share three bugs that I found:

When I set cpu max freq to 800 MHz (my battery profile), your patch to cpu freq goes above max freq does not work (sometimes cpu goes up to 1000 MHz or 1100 MHz, I saw that with perfmon and cpuspy). However, it works fine when I set cpu max freq to 1400MHz (it does not hit 1600 MHz cpu freq step :good:)

Sometimes (occurs randomly) when I apply a custom stweaks profile with pegasusq as cpu governor, cpu max online cores set to dual core mode and cpu max freq to 800 MHz, my system freezes and I am obligated to do a forced reboot by pressing power buttom continuously. I think it is related to cpu max cores limit, the issue does not occur when I have all 4 cores unlocked (quad core mode enabled). I hope you could look at that cause when I play games like real racing 3, I want to enable battery profile to avoid high battery drain (yes, it runs fine in dual core mode ahah :D)

In CM10.2 (slimbean 4.3 beta2) zram settings are not applied on boot, I needed to open stweaks and click on setzram button (I am not sure if it is rom related, does other people using cm10.2 have this issue?)

I am using googy max 1.6.8 and sammy stock 4.1.2

Now, lets make some useful publicity (already said before)... For the ones who want perfil-fast-switch without opening STweaks click here: I know, I am smart ahah :D

Anyone could said me how some people are getting ~18900 on antutu? I am able to get only ~17900 with slimbean rom :good:
[Galaxy S III Original Android Development] dantheman122:
Hey Googy, the latest kernel is running perfectly for me. Just a small feature request if possibly, could you implement the softkey backlight control from Yank (which Tema implemented too) if possible? It allows you to set it so that softkey backlights only turn on when touched, not when the screen is touched.

This is the post from Tema http://xdaforums.com/showpost.php?p=44006179&postcount=24898

and Yank http://yank555-lu.net/viewtopic.php?f=18&t=25&p=3149&hilit=Hardwarekeys#p3149

Obviously no pressure but just quite a handy feature :)
[Galaxy S III Original Android Development] kenji1996:
16575 on antutu Nice one xD
[Galaxy S III Original Android Development] kasperok:
+1:good:

anyway.. I'm on 1.6.8.. just noticed that for me it is working that way. Backlight softkey do not light up touching the screen but only if I use them.

I'm using Omega v43.7 XXEMF6

:D

tnx
[Galaxy S III Original Android Development] cink40:
Which Rom? on cm10.2 softkeys lights up when touching the screen...
[Galaxy S III Original Android Development] imjustafq:
sry for the wrong question. but.. what custom kernel can i use for me7?

Sent from my GT-I9300
[Galaxy S III Original Android Development] shoxyy:
Yo googy,

newest kernel running great but i found a little bug on the wolfson sound. If you use presets the graphic eq is still on top of the preset eq.
[Galaxy S III Original Android Development] PedroMedeiros:
Samsung did not release kernel sources neither an official 4.2.2 firmware release. So, you need to wait till Samsung release 4.2.2 sources for developers...

Ok man! CM10.2 have some issues with googy kernel (if you can't live with that, use previous CM versions). I installed a cm 10.2 based rom (slim bean 4.3 beta 2) and zram settings was not applied with phone boot (which isn't an issue with sammy or cm10.1). We all know about CM 10.2 external sdcard bug in googy... And with that CM 10.2 based rom, I unchecked master sequence and register hook and I got stock colours. So, it seemed to work for me! Anyway, I use my display with natural colours, everything works normal here.
[Galaxy S III Original Android Development] mitchpunk:
Haha my colors look pretty normal as well!

Unchecked master sequence and register hook.

And it's all good !

I've barely had any problems with googy expect for the current audio breaking issue.

Check your screen settings on advanced options maybe!

Sent from my GS3 Paranoid GT-I9300
[Galaxy S III Original Android Development] llcoolveer:
Or just uninstal Stweaks reboot and down a new one from Play...:good:
[Galaxy S III Original Android Development] DaReDeViL:
Zram can be applied at boot if you activate it from cm settings-memory-zram ;)
[Galaxy S III Original Android Development] droid_junkie:
Update CWM recovery

I'm having a few questions regarding updating recover.

ROM Manager does not seem to work for me. I don't know if this an issue due to the dual boot or due to wifi via proxy. So, my question is, how do I update to the lattest version of CWM recovery.

Do I need to take any additional steps while removing this kernel? I want to install a new rom and would like to install this kernel later. How do I go back to single boot?
[Galaxy S III Original Android Development] PedroMedeiros:
Just uninstall rom manager! You don't need it. Just install a nice recovery like this one: http://d-h.st/users/philz_touch/?fld_id=16049#files and enter in recovery mode to backup/install your rom! It supports many features like android 4.1.*/4.2.*/4.3 internal sdcard location, you can choose /sdcard for 4.1 roms or /sdcard/0/ for 4.2 up...

It only supports your primary dual boot rom (it's usable for the ones who have dual boot and for the ones who don't)!

Anytime you want to backup/install your second rom, just go to stweaks, dual boot tab and select boot into 2nd rom utils...

Edit: if you just want the original cwm backup recovery (without rom manager) just download it here: http://xdaforums.com/showthread.php?t=2200501
[Galaxy S III Original Android Development] Chaitanyapatel8880:
I am not having any issue with audio breaking. I am using Sammy and googy 168

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] inscythe:
Actually, I have the audio breaking issue, however only on the wolfson engine. Ever since I changed to Scoobydoo, barring some audio skips when turning on wifi, it has been smooth sailing...

Maybe I'll try switching back to wolfson to get the logs and kmsg when it does happen, but it is quite random and rare...

Configuration is on my signature...

EDIT: for the benefit of those who read this on Tapatalk, I'm running XXEMG4 deodexed stock (only with some bloatware frozen). Also more details: the symptom appeared both times for me after the phone running for a couple of days or so without restart. When I plugged in my earphones, my music player (Poweramp) will appear to be playing a song, but the play time froze, no sound came out, and music control (play/pause, etc) didn't seem to work. Unplugging the earphone kept the music player still in a limbo state and the phone became very unresponsive, taking few seconds for any taps/button presses to register. The volume control also froze whenever it was invoked after the initial freezing started. Soft reboot was still possible, and the audio behaved normally for a couple of days before appearing again.
[Galaxy S III Original Android Development] Scarface1991:
It's a huge difference if you use CM or Sammy. Googy already said that CM handles Audio differently than Sammy resulting in breaking the engine sometimes. Googy made huge improvements by enforcing the wolfson sound engine but sometimes even if rarely it still breaks.

Try this and see if it breaks the scoobydoo and wolfson sound engine:
[Galaxy S III Original Android Development] qtwrk:
Any information on incoming release? :p
[Galaxy S III Original Android Development] DaReDeViL:
Updated linux & better memory and zram management

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] mitchpunk:
I'm pretty sure he'll update as soon as he can.

Let's let him enjoy his holidays haha

Sent from my GS3 Paranoid GT-I9300
[Galaxy S III Original Android Development] inscythe:
I suspect you didn't read my post in the forum page, so you couldn't see my signature. Well, I'm actually on stock XXEMG4 deodexed. I have put more details in my last post.

Anyway, I will switch back to Wolfson and see whether I can reproduce the bug and maybe grab a last_kmsg. Anything that can help googy in improving this kernel :D
[Galaxy S III Original Android Development] FadeFx:
Even thou anas is on holidays, there are betas coming up on a daily basis, so be sure there will be a release when the quirks got fixed.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] qtwrk:
Oops, didn't know that he is in holiday :p
[Galaxy S III Original Android Development] chris-s:
Hi all,

Would you please tell me if there is still a Wifi Tether issue with Googy and CM 10.2 ?

The Wifi Tether is a very important feature for me.

Thanks
[Galaxy S III Original Android Development] DaReDeViL:
Well I just discovered that there is a real life version 1.1 beta dual boot linaro 4.9 .... testing now :p

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] DaReDeViL:
No problem, wifi tethering has been fixed long time ago
[Galaxy S III Original Android Development] androidbpb:
Googy...here are some observations of mine:

1. If flashing history is like: Stock rom --> Siyah Kernel 1.9.1--> Googy Max 1.6.8 : Camera not working (camera failed)

but if : Stock rom --> Siyah Kernel 1.9.1--> Googy Max 1.6.7 --> Googy Max 1.6.8 : Camera works

2. I am facing in-call issue : that means when I am on all default settings in stweaks (as I always do), sometimes person on the other side can not hear me (may be mic related issue). It happens to me very often while this was not the case with stock kernel.

3. Heating problem: while I am on stock rom or another boot with CM rom, using internet data or playing games like 'temple run' causes significant heating in a very shot time interval. Which I think should not be like this.

I hope you can confirm some of these issues and do the needful in future versions.

Thanks in advance.

PS: If you want to give suggestions, you are welcome, but if you are a critic then please just do not comment.
[Galaxy S III Original Android Development] chris-s:
OK thanks, I haven't found this information by searching keyword "tether" into this topic.

and many thanks for continuing Siyah.
[Galaxy S III Original Android Development] Olioaglio:
Zzmoove 0.7a released :D
[Galaxy S III Original Android Development] DaReDeViL:
Included, thanks ;)
[Galaxy S III Original Android Development] SignalX:
Using Googy kernel with SlimBean 4.2.2 build 5 as primary and MIUIv5 4.1.1 v3.5.3 as secondary rom

everything works perfect! love it

once again, thx master
[Galaxy S III Original Android Development] imepv7:
Thanks for another dual boot kernel! Before I try this out I'm wondering if you were able to fix the Wi-Fi tether issue from GokhanMoral's kernel?
[Galaxy S III Original Android Development] matrixios:
Battery brain or not???

Sent from high speed Temasek cm10.1 Samsung s3 Power Horse
[Galaxy S III Original Android Development] DaReDeViL:
No not yet. But soon i will try to ...
[Galaxy S III Original Android Development] qtwrk:
Been using it for 2 hours, Kill 40% battery , not significantly good nor bad compared to others

estimated battery duration time very alike to Siyah I feel, will continue to test it.
[Galaxy S III Original Android Development] DaReDeViL:
It depends on your usage ;)

So far, my battery drains a little bit slower than usual. (on CM right now)
[Galaxy S III Original Android Development] qtwrk:
Yes, I know, and I didn't mean any disrespect.

Here is my report

Been using it over 3 hours and 16 minutes with Wi-Fi, background music all the way, 2 hours and 45 minutes screen on time, battery from 95% down to 23%, basically not big fluctuations with Siyah 1.91, all same settings as it is same in Stweak...

And it is normal for me with my heavy usage.

Some little things.

1. I witness screen automatic turn on by itself, but it also could be that I accidentally slide the screen as I enabled slide2wake, no big deal.

2. I am experiencing huge laggy from time to time. I am not saying it's related to kernel, but today, the only thing I have done is switch from Siyah to Googy, didn't do anything else like install or uninstall apps, mods. just some chatting, electric book, and web page browsing which is my daily usage . So you may wanna look into it.

It seems lags when I browse webpage in Wikipedia maybe some other pages but I just didn't remember it... , I do that every day, but didn't get lagged before with Siyah ,

And also get lagged when I unlock screen, Jkay framework with ink effects,

The ripple effect looks like get "jam " or "stuck " for a second or 2.

Those lags are not very frequently appear, it could be a problem with background apps, but who knows...

Sorry, can't exactly express my report with my bad English...
[Galaxy S III Original Android Development] DaReDeViL:
No disrespect in your 2 posts ;) just feedbacks to make things evolve.

You know. The kernel is practically identical to siyah base except the few compilation optimizations i made and the linux update to 3.0.77 !

So the next step is to make it better ... With the help of your feedbacks :thumbup:

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] mitky82:
Work fine with stock and cm rom for now.

why some kernel have 839ram, other have 833

GT-I9300 XXEMC3
[Galaxy S III Original Android Development] qtwrk:
Yes, well, looking forward to it :thumbup:
[Galaxy S III Original Android Development] sevenup30:
Got black screen when booting 2nd ROM with carbon as primary. 2nd ROM was miui or omega !
[Galaxy S III Original Android Development] jjpro45:
How about support for the I9305 :good:
[Galaxy S III Original Android Development] mitky82:
For people with not enought internal storage space, directory bind installed on second rom emulate 0 folder from external sd card greatest

GT-I9300 XXEMC3
[Galaxy S III Original Android Development] sungc007:
Is there a way to change wifi mac address?

Recent boeffla kernel has implemented about how to change custom mac address to /drivers/net/wireless/bcmdhd folder... it seems like the changed files are dhd_custom_se.c and dhd_sec_feature.h.... I don't have a capability to build the kernel...so I hope you can consider the function for your next build.
[Galaxy S III Original Android Development] nhb13612:
After 12 hours, everything's still running smoothly and fast. Even my battery is charging faster (I've been having a slow battery charging problem the last two weeks). Please keep updating and continue with your good work.
[Galaxy S III Original Android Development] 4l3gU:
Great great great...and now all the last update... the dream continues...;);)

★★ oihcceps ollad klatapat noc otaivnI★★★
[Galaxy S III Original Android Development] PedroJuuu:
Why when my phone is on vibrate and I reboot it, boot sound sounds?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Gonnelli1355:
Is this kernel working with Sammy leak 4.2.1??

Thanks for answers

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] DaReDeViL:
I think it's normal :cool:

No sammy 4.2.1. Only sammy 4.1.2 and cm10.1
[Galaxy S III Original Android Development] romskii:
I think some battery tweaks from Googy Kernel 1.5.x have to come to Max kernel :)

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] xclub_101:
1.4.0 has lots of problems :(

On my i9300 1.4.0 seems to have lots of audio problems :(

The speaker seems to work, but volume was lower than in 1.3.3 ; however the headphones get correctly detected but get no output - silent ; also by accident (but a fortuitos one, since I got to fix things back) somebody called me on the phone and I also could not hear anything at all (he later told me he was hearing me).

I have reverted back to 1.3.3 and things are back to normal.

Another note - a LOT of settings seem to never be preserved when moving from 1.3.3 to 1.4.0 or in reverse - is that a good thing? Also there are some defaults that are questionable - like the 900 mAh on USB, but also are we certain that cfq is the best default i/o scheduler? Is pegasusq better than lulzactiveq?
[Galaxy S III Original Android Development] DaReDeViL:
What rom are you using ?

I'm on stock xxemd2 and cm10.1 and everything is working as it should

Please try to reset to defaults in STweaks app and reboot, as the config file structure has changed.
[Galaxy S III Original Android Development] papyzebike:
Hello , first mr googy many thanks for your wonderful kernel ...but i don t get on the internet to find a comprehensive topic and date extweaks.

i am under official miui v5 (jro03c 4.1.1) with googy max.Is that someone could advise me extweaks adjustement (settings) only for the performance ?

many thanks in advance for your help
[Galaxy S III Original Android Development] DaReDeViL:
I must partially disagree with you when you say the interface structure is very different as I find them quite close to each other, especially for what concerns your app, the control system is quite the same if you change "scoobydoo_sound" with "boeffla_sound"

for example, to set headphone volume level :

Voodoo : echo 55 > /sys/class/misc/scoobydoo_sound/headphone_amplifier_level

Boeffla : echo 55 55 > /sys/class/misc/boeffla_sound/headphone_volume

You can set in your app a detection mechanism of implemented sound engine to be able to send the corresponding commands ;)
[Galaxy S III Original Android Development] papyzebike:
[MENTION=1546289]googy[/MENTION] anas :

Hello , first mr googy many thanks for your wonderful kernel ...but i don t get on the internet to find a comprehensive topic and date extweaks.

i am under official miui v5 (jro03c 4.1.1) with googy max. could you advise me extweaks adjustement (settings) only for the better performance ?

many thanks in advance for your help
[Galaxy S III Original Android Development] DaReDeViL:
One more thing for people having low sound volume, please change the audio setting to any config and apply then set audio as you like and apply again. This has to be done only once for the new settings to stick.
[Galaxy S III Original Android Development] FadeFx:
Guys, i don't think there is any difference in sound quality bitween boeffla and scoobydoo sound, as both are just interfaces to the audio chip which controls the sound output. However, as the developer of scoobycontrol, which btw gives even more freedom to control the eq settings, i am bound to scoobydoo sound interface and ask you to at least give option to choose which interface to use. Otherwise I'd have to either stay on 1.3.3, or switch kernel again.

Btw, there seems to be a bit of missconception about what an equalizer should do among most of us here.

As you may know from your car stereo or home entertainment system which most likely have some eq presets to choose from they are called after some music styles like rock, classic, electronic and so on, this is because different styles of music have different affordments to the output so they sound good, and then there is also differences in speakers (in our case headphones most of the time) and finally personal preference. All these points lead me to build scoobycontrol, because i wanted to be in control of the hardware i use as much as possible. Sure, there may be advantages to boeffla against scoobydoo in terms of channel wise volume control, which may make sense to people that have one ear that is weaker than the other, and it would be possible to adapt my app to boeffla as well, but only with a looot of work as the interface structure is very different from voodoo.

I know, but the differences are so significant that I'd have to redo a lot of the app as i was not prepared for such a step when i started and my 'code' is not that perfect that i can easily adjust to change the filenames otf. I was thinking to do a boeffla port a while ago, but didn't go at it because of those massive changes. I know that this is my own fault, but as an excuse i have to say that this was an experiment when it began and mainly meant to go as a proove of concept than the full fledged app that it is now...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] andrewilley:
I actually WANT a low sound volume on my headphones, as setting the analogue amp gain to anything above about 40 results in an audible background hiss which is extremely annoying when listening to music quietly in bed at night. Do I gather that the latest update to this kernel will break scoobycontrol by the way, as I use that to set the gain level? If so, I'll stick with 1.3.3.

Andre
[Galaxy S III Original Android Development] MrxSiN:
new mali driver implemented?