yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] romskii:
But bad you're using an iPad :D

tapatalked with Galaxy S3
[Galaxy S III Original Android Development] Scarface1991:
[MENTION=1897326]googy_anas[/MENTION]

Temasek included some nice improvements into his kernel which should improve smoothness and battery life. Maybe it would fit good into your Kernel too?
[Galaxy S III Original Android Development] DaReDeViL:
Thanks for informing me. I have already picked the commits and alpha testing now ... ;)

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] davi_ssilva:
Hahaha, well it was a gift, so what could I do? :laugh:
[Galaxy S III Original Android Development] DaReDeViL:
Huh ? iShît in my thread ?

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] davi_ssilva:
LOL!

Sorry, Googy, but regecting this gift would let a beautiful girlfriend very sad, hahaha...:D
[Galaxy S III Original Android Development] smala:
Hi, I've noticed rhar eith thus kernel i can't collect/see my data connection stats. With other kernels, like boeffla, i see full stats.

Edit: why i can't upload screenshots with tapatalk...?!

Inviato dal mio GT-I9300
[Galaxy S III Original Android Development] caalca:
I am having problems with my 32gb se card since I updated to 1.7.7. Everything else is working perfect on CM 10.1 stable. Sometimes I can't open my photos on my SD card and I can't explore it with any explorer.

How can I solve the sd card problem?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] Scarface1991:
[MENTION=1897326]googy_anas[/MENTION]

Any noticeable improvements with the new commits?
[Galaxy S III Original Android Development] FileFixer:
SanDisk 32gb mobile ultra class 10?
[Galaxy S III Original Android Development] DaReDeViL:
Not really but it's too early anyway, at least on my side. Waiting for beta team's feedback ...

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] xewier:
CM 10.1.3 compatible?
[Galaxy S III Original Android Development] smala:
bump. attached sample snapshot of the issue.

myROM is:Android revolution HD v.29 (based on latest 4.1.2 samsung)

if i revert to boeffla kernel (wipe cache+dalvik) i can collect 3g stats.

anyone experiencing this issue?
[Galaxy S III Original Android Development] kasperok:
I'm here again. I've tried many 10.2 rom (Fusion, Temasek, cDroid, etc..) as secondary rom and each time I get the same problem with my external sdcard (Sandisk 64GB exfat formatted).

The external sdcard is not recognized. But if I remove and reinsert the card with smartphone still on, sometimes it work and after a while the sdcard is mounted normally.

I noticed that during the external sdcard is not recognized even the developer option menu seem to be inaccessible, frozen.. but removing the sdcard make the developer option menu appear immediately.

Maybe could be something related to my Sandisk card.. but the strange thing is that I have no problem with my primary ROM (4.1.2 Samsung based).

Any clue!?

Thanks anyway..
[Galaxy S III Original Android Development] llewelld:
Just wanted to follow up in case it helps anyone.

I was running Paranoid Android 3.99 with Googy Max. Due to bluetooth issues (Which exist up to 1.7.6 and I will assume 1.7.7 but not confirmed), I reverted back to 1.7.4 - which is much better at streaming bluetooth audio).

After running for a day my phone went flat. Then, my phone would not charge. Not via usb, not by direct charger. I have 2 batteries. I then took the phone to a few phone shops and tested other charged batteries, still the phone would not power up (no light when charging, nothing on the screen) - even when dropping in pre-charged batteries. I posted a few days ago in this thread about this..

After reading about some weird stuff of this problem, I tried every conceivable combination of usb cable (I have about 4 and charger / usb port). For a some weird reason, 1 cable with only 1 of the front usb ports of my PC would allow the phone to charge. Any other usb port or cable - the phone would not come or (or the charging led would not light up).

Since finding this one USB port / cable combo that worked - the phone charged, then I reflashed back to Ugly Omega v50.1 - and now the phone works... charges off any port cable etc.

- The only thing I did was a 75mv undervolt. (the rest os stweaks settings I left stock).

Does this seem weird that a undevolt setting could cause the phone not to be charging.. (I had tested multiple reboots with that undervolt and had run a whole day without a problem until the battery went flat ?

My biggest hope is that the bluetooth streaming bug is at least acknowledged with this Kernel.

keep up the good work!
[Galaxy S III Original Android Development] dyval:
Yes. I'm using it. :good:
[Galaxy S III Original Android Development] Philthy82:
Is a version of this available for the i9305?
[Galaxy S III Original Android Development] cKenny:
bro, the bluetooth streaming issue has been fixed in 1.7.7 :)
[Galaxy S III Original Android Development] FadeFx:
No, the 9305 has completely different cpu....

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] qtwrk:
All hail the Exynos

来自 GT-I9300 上的 Tapatalk now Free
[Galaxy S III Original Android Development] Yank555:
Not quite ;)

It has the very same Exynos, but has 2Gb of RAM, an LTE modem instead of 3g and lacks FM radio. That's about the difference. Oh and a completely different partition table, and that's the main reason not to flash an i9300 kernel on a i9305 device, if it were to actually really flash, god knows what partition would be overwritten...

But it's not too complicated to recompile a i9300 kernel for i9305, you need a few changes to defconfig (maybe some codereview on sound engine to remove the FM related detection code), use a corresponding ramfs and a corresponding flashing zip, and you're good.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.2-beta2 kernel.
[Galaxy S III Original Android Development] xclub_101:
What does it mean 'proudly eFused'? "Knox 0x01 and still prout of it" or somebody managed to reverse-engineer the way how Samsung resets the Knox flag?
[Galaxy S III Original Android Development] Yank555:
You got that right, eFused = Knox Warrenty at 0x1, and yes I couldn't care any less about Samsung's sh*tty way of scr*wing their customers, so I'm proud to have a device with a blown eFuse ;)

eFuse blown is blown, there is no going back.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.2-beta2 kernel.
[Galaxy S III Original Android Development] PIRATA!:
Same for me: want to use my damn button because I have it!

And that app is not working good either, with my animation, and its animation it's not the same as Samsung!

I want this to work as Samsung, otherwise I would buy another phone, no?

The thing that I don't understand for now, that are the most important, more then CRT effect, is that I have a lot of lags!! ...and with the last Siyah I hadn't!!

Why could this happen? I have disabled ZRAM. Things are a little bit better..but not perfect as before....and I would not like to go back to Siyah as I am using the new sound engine in this kernel.
[Galaxy S III Original Android Development] xclub_101:
There is somewhere in the S4 forum I think one report that Samsung themselves can revert the Knox flag from 1 to 0 (and in the process wipe everything and write stock stuff), so even if an eFuse might be involved the Knox flag itself might not be a direct value of it (and instead more something like the state of the efuses corresponds to some signature in some other place in the bootloader).

---------- Post added at 01:51 PM ---------- Previous post was at 01:47 PM ----------

Hmm, I have seen something similar yet with strange differences - but the sum of our reports might give us the correct clue of what is happening!

It seems that your problem is exFAT under 10.2 (as secondary) but the same card works perfectly under Sammy 4.1.2 (as primary).

In my experience the exFAT seems to work OK on Omega AOKP v10 and v11 (both 4.3.1) itself but in over 90% of the cases when I reboot from 4.3.1 to 4.1.2 the exFAT "hangs" during the initial fsck.exfat (I can see the icon saying "verifying card" or something similar in notification bar and I can see from adb a process running fsck.exfat; also this explain why if you go in Settings/Storage things seem to get locked and after some time the system restarts). My initial impression was that the problem was related to v11 not closing stuff correctly on the card since with v10 I have never seen that problem, but now things seem to be more complex than that :rolleyes:

Here are some more info - fsck.exfat in both my 4.1.2 and 4.3.1 is listed as v1.2.2 so it seemed a little strange that one appears to work better than other.

Once the problem (let's call it "dirty exfat") takes place it does not go away easy - even multiple (2-3) restarts on 4.1.2 alone does not fix it. Also restarts with 1.7.5 (where I never saw the problem before, and I was on that version for 2+ weeks since I skipped 1.7.6) or as far back as Siyah 1.9.1 does not fix the problem.

Even stranger - the problem in 4.1.2 seems to "go away" for the next reboot if I go into recovery (Philz touch) and then over adb I manually run fsck.exfat (which is an older v1.0.0 there) like

fsck.exfat /dev/block/mmcblk1p1

and which finds no problem; this could suggest that there could be some dirty flag that is cleared this way.

However it might be also possible that the dirty flag is "triggered" by something else - for instance on my microSD the "normal" (when everything works fine and nothing is "dirty") time for "verifying SD card" at the very start is in the order of 10-15 seconds and I wonder if for instance something else tries to go to the microSD (like the MTP part or the media scanner) during those initial 10-15 seconds it might hang the fsck process that is running in the background.
[Galaxy S III Original Android Development] Yank555:
Interesting ... though bootloader is closed source, so hard to get behind this :(

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.2-beta2 kernel.
[Galaxy S III Original Android Development] FadeFx:
I thought the 9305 has the qualcom cpu

_________________________

tapatalked from GalaxyS3

---------- Post added at 02:11 PM ---------- Previous post was at 02:09 PM ----------

Id prefere to have an open qualcom cpu and get cm the day it us released instead of having that exynos thing that samsuck refuses to release propper sources.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Arfman:
Meanwhile, CM10.2 still refuses to boot in dual boot mode with the latest Googy kernel. Can someone confirm this is being worked on?

(you get constant process com.android.phone has stopped working errors)
[Galaxy S III Original Android Development] Yank555:
Amen to that, that's why the n9005 was acceptable for me, even if I'l likely stay on TW on this one, too much to lose going AOSP...

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.2-beta2 kernel.
[Galaxy S III Original Android Development] rascal0pl:
Could you tell me why sound quality is terrible now? (in recorded videos)

Sound is so distortoied even when I have set mic sensitivity to 3:

http://www.youtube.com/watch?v=pxAmFVu6tDQ

It is much worse than on stock kernel :(

Older version of this kernel http://www.youtube.com/watch?v=enuXsR41m_s (the same place, and soundsystem... (and more difficult shooting conditions - phone was set on bass speaker) - sound is clear and almost without distortion - mic sensitivity - 4.

One more http://www.youtube.com/watch?v=GBbsI_HHfeA (even older version of this kernel - version for stock rom, the same place and soundsystem)
[Galaxy S III Original Android Development] DaReDeViL:
Can you please specify which rom & sound engine you use ?

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] rascal0pl:
ROM = Stock 4.1.2 / Fusion 4.3.1 - It doesn't matter which one, I tested it at home today also (Fusion = primary rom, stock - secondary), and results are like above.

Sound engine - Wolfson/Scooby - like as above.
[Galaxy S III Original Android Development] jinosong:
Streaming bluetooth? I thought it was Bluetooth tethering that was fixed?

Can you clarify?

Edit: Streaming audio has indeed improved. This is great. Thanks!
[Galaxy S III Original Android Development] FadeFx:
I never tested bluetooth tether yet as if i need to tether i use either wifi or usb. Doesnt it work with bt?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] jinosong:
FYI, Bluetooth fix includes streaming audio. I can now stream audio at normal rates via Bluetooth.
[Galaxy S III Original Android Development] FadeFx:
I knew that

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Richard_10:
I have a problem with crt -off animation. I tried change the delay to 0 then gradually change it to 300. Not visual changes, still the same problem. I have a bright flash right before the animation.

I'm on googy-max 1.7.7 and slimbean 4.3.1 stable build 2
[Galaxy S III Original Android Development] chrismast:
I got the same setup and CRT works normal, what bright flash are you talking about? (if it is the one I got as well, I guess it's normal?)
[Galaxy S III Original Android Development] Richard_10:
Believe me it is not. It like the whole screen get white before the animation starts. Any tip please ?
[Galaxy S III Original Android Development] chrismast:
I didn't change any settings hence fear I am of no help to you :(. Maybe googy or someone with more knowledge might help.
[Galaxy S III Original Android Development] Richard_10:
Thank you anyway :)
[Galaxy S III Original Android Development] salman_dude:
how to decrease brightness from kernel setting,

from system setting brightness is very low & auto brightness is off still brightness is high
[Galaxy S III Original Android Development] FadeFx:
Open stweaks go to mdnie tab and raise brightness reduction value and takeover point a bit. You need to have register hook and master sequence enabled...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] tracemonkey:
I've also turned my brightness down manually and found that reduction and takeover point in stweaks makes no difference at all.
[Galaxy S III Original Android Development] davtse:
Something to look forward to in the coming update. :thumbup::D
[Galaxy S III Original Android Development] FadeFx:
You had register hook and master sequence enabled? What rom are u on?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Galaid:
omnirom

Hi [MENTION=1546289]googy[/MENTION],

do you plan to support kitkat? It would be nice to see how OmniROM progresses, and still keep cm10.1 as primary rom.

Br
​
[Galaxy S III Original Android Development] FadeFx:
Absolutely no 4.4 build out there to support yet.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] caalca:
It is a 32gb Kingston class 4. Any idea why my SD card doesn't works well with this kernel?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] romskii:
What do you mean?

tapatalked with Galaxy S3
[Galaxy S III Original Android Development] qtwrk:
we can say the kernel is fine , would you mind to try use Card Reader on computer to see if there is any physical problem on the card ?
[Galaxy S III Original Android Development] jinosong:
When's it coming out? I can't wait!
[Galaxy S III Original Android Development] tracemonkey:
Yes and yes. CM10.2
[Galaxy S III Original Android Development] FadeFx:
For me changes are clearly visible with similar configuration.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Mostafa Wael:
android 4.3 leak is out!!

hey googy,

thnxx alot for the amazing kernel.

Just wanted to ask if the kernel will support the android 4.3 leak within the next update?? I hope so

Mostafa wael :)
[Galaxy S III Original Android Development] Millenium3:
Nope, there's no source available for leaks

Surfing on XDA from Tapatalk in I9300.
[Galaxy S III Original Android Development] romskii:
Remember, never for the Sammy leaks, only official ROM's

tapatalked with Galaxy S3
[Galaxy S III Original Android Development] FadeFx:
And even this will take its time as most of the time the sources are released a bit later...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
Nice way of suggesting ;)

Anyway i deeply analyzed the code and made some modifications anf fixed some problems. Now googymax is 'flying'. Stay tuned. 1.1.0 is on its way ... (still testing)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Tuga2010:
I've tested your kernel and i find it very food and stable .

Even so i've i found some lags and glitchs closing some apps .

I'm on CM10.1 nightly , with lulzactiveq as governor and row as scheduler.

I prefer performance to battery life , and thats because i'm using those options in stweaks.

Hop e you tweak even more to performance and it will be my daily driver kernel :)

Regards
[Galaxy S III Original Android Development] romskii:
Some days with your kernel and i have a good feeling. It's like the first release for the sammy ROMs. I'm really looking forward :)

Ah and slide to wake works with this kernel, just enabled the option via Stweaks BUT it only works for me right after i've lockt the device, after ~ one minute screen off slide to wake is not working.

Sound on this kernel is amazing, like boeffla :)
[Galaxy S III Original Android Development] tintin1503:
Super excited to see the idea of Siyah being taken forward.

Googy kernel was one of my favorite kernel along with Shark kernel and now this one is gonna be my most preferred one
[Galaxy S III Original Android Development] Tuga2010:
Consider to implement zzmoove governor .

Here is ther source code : https://github.com/andip71/boeffla-kernel-jb-u10-s3/commit/abfd81492260d0076748b3ee1e91b0dc045003e9

regards
[Galaxy S III Original Android Development] DaReDeViL:
It's already implemented in Googy Kernel. On max kernel it will implemented but after successfully optimizing the kernel itself. Addons will follow ;)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] romskii:
my experience on googy kernel is that his tweaked pegasusq is much better than zzmove!
[Galaxy S III Original Android Development] Tuga2010:
It depends what you´ve tweaked . I suggested only to have the option to choose.

For me , tweaked to performance , the governor lulzactiveq is even better than those two you´ve mencioned . ;)
[Galaxy S III Original Android Development] TigerCourage:
wohoooo, I'm totally trying this now. Finally an alternative with Dual Boot to Siyah kernel and a very updated one too!!

Thanks!
[Galaxy S III Original Android Development] musmax:
I'm sorry, how do I put 2 ROMS?

Thank you
[Galaxy S III Original Android Development] romskii:
Lulzactiveq is his next project

Go to STweaks App. After reboot to the recovery from the STweaks App go to dual boot menu and flash it

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] musmax:
...I don't have STweaks App.
[Galaxy S III Original Android Development] 4l3gU:
Search on play store...is free...;)

★★ oihcceps ollad klatapat noc otaivnI★★★
[Galaxy S III Original Android Development] musmax:
Thanks.
[Galaxy S III Original Android Development] rafaelpernil:
[MENTION=1897326]googy_anas[/MENTION]: I've been using this kernel two days and I find it very fast, very smooth and sounds similar to Boeffla Sound. But drains battery just a bit faster than your Googy Kernel (Not Max) and I prefer Boeffla Sound interface (Mainly because "Headphone Amp Hack" function and because the better sound quality (IMHO)). So, could you change sound system to Boeffla Sound? And as a mate said: Could you include battery saving "tweaks" from Googy kernel?

For the moment, works perfect. My daily kernel. Just only those little suggestions.

Keep working ;) ( You became the developer that updates more a kernel in less time :good: )

P.D. I forgot, I'm on UltimaROM v12.0 (Based on Sammy 4.1.2)

Regards :ok:

P.D. Sorry about ":ok:". In other forums is shown as :good:

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] DaReDeViL:
You should test the version 1.1.0 !!! :cool:
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.1.0 ONLINE !!! ;)
[Galaxy S III Original Android Development] rafaelpernil:
Thank you!! I'm going to test right now :good:
[Galaxy S III Original Android Development] romskii:
Battery life is amazing Googy!

I've started at about 75% with test version.

I was 2 hours on GPS with Google Navigation. Taken lots of photos, Browsing, listening to music (amazing sound! :cool: )

Downloading through WLAN new ROM builds.

No problems, smooth, stable, very fast and amazing battery life.

A worthy successor to your first kernel

Edit: Sry I didn't mentioned, I have a 4400mAh battery :D

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] rafaelpernil:
[MENTION=1897326]googy_anas[/MENTION] About random entropy. I found a method (In Lonas kernel) which generates more entropy http://billauer.co.il/frandom.html . It's called frandom and generates random entropy much faster than urandom (Default in Linux). I don't know so much about linux, but may interest you.

Regards :good:
[Galaxy S III Original Android Development] DaReDeViL:
It's not too much trouble for me either but the way it's asked ... :(

Anyway, it will be done on next release ;)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
[MENTION=4251861]qtwrk[/MENTION]. How is cpu limit now ?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Kord:
Hmm, actually I'm experienced this too, m8 :)

Probably script identify turning screen off by proximity sensor like normal automatic turning off - that's my opinion.
[Galaxy S III Original Android Development] qtwrk:
Haha, did you mean he missed the word "please" or such?

Been running fixed kernel about half hour, CPU spy shows no sign of 1600, everything is good now ;)

---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------

I think, it's probably due to how the screen is off,

If you use Jkay framework or some one click lockscreen apps/widget you will see how different it is.

If you lock screen by pressing power button, touch wake won't respond, but if you use "soft" way to lock screen, the touch wake will relight the screen, that's probably what's going on with touch wake while in calling situation as dialer lock screen "softly"...
[Galaxy S III Original Android Development] Cunhaad:
Sound recording

Hi, thanks a lot for your work, it´s really nice to have someone using gokhanmoral's base. :good::good:

I've had this problem with Siyah Kernel also, don't know if you can help me but here it goes: 2 problems

1 - Sound recording is inconsistent, for ex. call recording apps, works, then after some time it just records scrambled... reboot, it works again, some thing if you're using a sound recording app (i use Hi-Q Mp3 Recorder), but it happens with all others...

2 - When working, recording quality in loud environments it's totally distorted, it records fine in low and mid volume, but if it's too loud it creates a lot of distortion, i've tested several kernels and roms, this happens pretty much in all except the samsung original (this one recordes just perfect). Every weekend i need to do recordings in very loud environments, i love AOSP roms, so i have to change to the original on the weekends just to be able to record what i need...

Do you think you can help?

Thanks a lot!