yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DaReDeViL:
My settings are default ones

Yes you can hit apply and reboot or hit set zram and wait for 1 or 2 minutes without having to reboot !
[Galaxy S III Original Android Development] peramikic:
Try flashing the ROM again and then flash over the kernel. Devils kernel might have changed the drivers or something else.
[Galaxy S III Original Android Development] Olioaglio:
It won't change drivers.

Olioaglio
[Galaxy S III Original Android Development] ThePureHeart:
Mine are default for zram

The only thing I change for Googy-Max is mic sensitivity, speaker boost, turn off dynamic fsync. Everything else on default is perfect for me

Sent from ThePureHeart's I9300 Boss Edition

ParanoidAndroid | Googy-Max
[Galaxy S III Original Android Development] ho0o0o11111:
You don't need to press home button 4 times to get the negative effect.

negative effect:

!echo 1 > /sys/class/mdnie/mdnie/negative

Positive effect:

!echo 0 > /sys/class/mdnie/mdnie/negative

try to type them in app like emulator and you will see the change of your screen.

Use your way to handle these two commands then you can switch the state of screen between positive and negative in simply 1 click.

For me, I use Tasker + locale execute Plugin to make a menu/task to handle.

Have been using more than 1 year, no problem at all.

Hope this helps.

By the way, the negative effect is very useful especially when you are browsing web-page with many area in white.

This protect your eyes, and save battery too.

I like this function so much.
[Galaxy S III Original Android Development] Chaitanyapatel8880:
Anybody having problems in undervolting frequencies below 700MHz by -100 mV?...
[Galaxy S III Original Android Development] PIRATA!:
I am having lags now with Googy-Max kernel, and with Siyah I hadn't, so it might be a kernel fact.

The main difference between them is the ZRAM settings, that in Siyah was 500 with 100% of smoothness...while here in Googy-Max is 400 with 80%.

Do you know if there are some other differences between them?

---------- Post added at 08:46 AM ---------- Previous post was at 08:41 AM ----------

Interesting...I'll try to investigate on this and try out Tasker...but personally I loved the 4 way clicking! Much more simple and usable while navigating instead of having to put down browser, activate negative colors, and then restore browser.

About Tasker...I would like to use it to try this as you say, and also for other stuff of mine.

Can you point me to some guide about how to use it and set it correctly?

Personally I would like to understand how to run apps and then do/execute some particular action of that app just after a device boot...

Thank you.
[Galaxy S III Original Android Development] EzerchE:
Is there any update coming for latest CM Nightlies?
[Galaxy S III Original Android Development] llewelld:
Thanks. I have reverted to 1.7.4 and Bluetooth is perfect. V 1.7.5 & 1.7.6 both have a fault with bluetooth audio streaming.. 1.7.6 is much better (1.7.5 is terrible), but in 1.7.6 I get a click about once a minute, sometimes a bit less. Happy with 1.7.4 for now, it seems perfect for audio so I am happy!
[Galaxy S III Original Android Development] DerTeufel1980:
Wow, why does it take this long? Which commands get applied by it?

The time isn't even noticeable if I apply zram values in my app. Maybe there's something wrong, either the command, or the driver itself?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DaReDeViL:
You can check it in my github, here : https://github.com/googyanas/Ramfs/blob/master/res/customconfig/actions/zramapply
[Galaxy S III Original Android Development] DerTeufel1980:
Strange, those commands are similar to mine:

https://github.com/DerTeufel/DevilTools/commit/eb0a9ddd73e139bfaf2c257b3c1e5d0f80d85fe0

Maybe you should apply the commands one by one in terminal and see, if there is a problem with one of them. Have had this, too, with the zram reset command once.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] fndpena:
So I need to do this before flashing the kernel?

Then the latest nightlies will work as expected?
[Galaxy S III Original Android Development] Yank555:
Yes, but that's located in the ramfs, which is located in the boot image of the kernel. If you unpack and repack properly, then yes it should work.

JP.
[Galaxy S III Original Android Development] fndpena:
I would need to extract the boot.img, do the changes and flash it again, right?

I think I will wait for the proper update from googy_anas :)
[Galaxy S III Original Android Development] DaReDeViL:
Next version contains the proper fix (among other things) and should be released after confirmation of the beta team
[Galaxy S III Original Android Development] JustArchi:
I'm not a kernel specialist here but it may be cool (and faster) to call 4 indepdendent forks in background (&) and wait for them to finish (zram resets).

Should speed up things up to 4x, depending on cpu and implementation.

For example I put my AD Backend in the background to avoid slowing down the kernel and other init.d scripts while working as long as I want.
[Galaxy S III Original Android Development] kavsko:
Hell yeah! Nice news!

Just love your kernel Googy!

Thanks.
[Galaxy S III Original Android Development] Makrilli:
I've been running 1.6.7 since the day it came out @ 200-1600 mhz with 100mv undervolt with no problems. Altrough obviesly every chip is different :/ Many times with my old s2 people said with one version of kernel they could uv 100 mv and with other version they would have problems
[Galaxy S III Original Android Development] alirezaafkar:
I've many lags with this kennel on carbon rom
[Galaxy S III Original Android Development] JB-007:
I'm on wanamlite, uc @ 1ghz

I think this issue was introduced since 1.4.1, i never noticed this issue before.

I was on1.4.3 had it and back to 1.4.1 and still have it.

Cheers
[Galaxy S III Original Android Development] qtwrk:
If you ever looked my screenshots about CPU spy carefully, you will notice that CPU stages are 1200,1300,1400,1600.

Let's assume for second here, if, there is some thing overrided Stweak and set Max to 1600, there is NO REASON governor skip 1500 and directly from 1400 jump to 1600 ... no matter LulzactiveQ or PegasusQ or Zzmoove or whatever.

There is not even a second runs on 1500 , don't you think it's weird?
[Galaxy S III Original Android Development] reinerlee:
Haha, all the while using Siyah's 1200ma (On AC), 900ma (On USB),

everything's fine, tested with Perseus Kernel which on 2,100ma (On AC) and 1,200ma (On USB). was fine too, few cycles charging.

So I guess, 1500 / 1000 should be fine I guess ?

I'm a frequent on-screen user, so fast charging is very important to me though.

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

It happens to me many times which the clock speed was being skipped.
[Galaxy S III Original Android Development] FadeFx:
You are using an aosp rom, make sure you didn't set 1600mhz in system settings - performance - processor

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] kerrari:
Slow charging problem?

Hello people,

Could anyone tell me why I would be having drastically slow charging? Both on AC and USB.

Normally it would go from 1 percent to 100 in around an hour. But last night I left the phone for charging, it was showing 86 percent in the morning... not even reached 100.

Any ideas?
[Galaxy S III Original Android Development] FadeFx:
Did u try to charge slower, this could result in longer battery life...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] reinerlee:
I don't think this is useful for Lithium Ion battery.
[Galaxy S III Original Android Development] MrxSiN:
About that touch to wake, default is 20 second is quite long. It mean, start on a second that screen off, any touch on the screen will wake up the device within that 20 second. 5 or 10 second as default would be nice :)
[Galaxy S III Original Android Development] qtwrk:
I never saw it before, if you use your phone for while, you will see every stage will be used in one way or other, it just matter of time. But I never witness CPU frequency be skipped.

thanks for reminding , but I am using Sammy ROM.

I will try flash pure stock firmware tonight to see how it goes.
[Galaxy S III Original Android Development] DaReDeViL:
Cpu stepping to 1600 problem SOLVED. Will upload soon ...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
Unrelated :)

Problem fixed. A change I made was overriding cpu limit ...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] satriani-vai:
Bug with a touch to wake

I don't know if this has already been discussed, but there is an bug with a touch to wake while you calling.
[Galaxy S III Original Android Development] DaReDeViL:
Fixed 1.4.3 posted ;)
[Galaxy S III Original Android Development] red_guard:
really nice kernel, good work googy :)
[Galaxy S III Original Android Development] :
will you ever make mDNIe sharpness tweak ON by default?
[Galaxy S III Original Android Development] DaReDeViL:
It sounds like you are really angry !!!

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] :
No, no, no. please no. LOL
[Galaxy S III Original Android Development] DaReDeViL:
So please reformulate
[Galaxy S III Original Android Development] qtwrk:
It is not too much trouble to set it on manually! You have to open Stweak anyway after you flashed kernel.
[Galaxy S III Original Android Development] kavsko:
Keep up the good work Googy!
[Galaxy S III Original Android Development] DaReDeViL:
I'm not a kernel specialist too as learning stage never ends ;)

I'll try that asap, THANKS :highfive:
[Galaxy S III Original Android Development] JustArchi:
https://github.com/googyanas/Ramfs/pull/2 - should work but you need to test it yourself. In worst scenario you'll wait 3 minutes.
[Galaxy S III Original Android Development] shitman66:
1.7.6 doesn't compatible with the lastest cm 10.2.

It's force close phone.apk.

Will a new one fixed it? :eek:
[Galaxy S III Original Android Development] shorty1483:
Perhaps you should read the last page...
[Galaxy S III Original Android Development] shitman66:
I's read it. Or I'm missing to the point of that reply?
[Galaxy S III Original Android Development] Gambit14:
http://xdaforums.com/showthread.php?p=46769780
[Galaxy S III Original Android Development] fndpena:
Last page???

We are talking about this in the last 5 pages... Hehe :p
[Galaxy S III Original Android Development] Chaitanyapatel8880:
Thanks man...

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] pradeepb:
I am on Samsung custom ROM 4.2.2.. Can install this kernal and flash cm10.2 ROM as second rom? Kindly reply .. :)
[Galaxy S III Original Android Development] Chaitanyapatel8880:
4.2.2 is not yet supported by any kernels ... Until sources are released...

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] FadeFx:
And it most likely will never be, as samsung is going to release 4.3 in near future and 4.2.2 will not get an official release at all

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] JustArchi:
[MENTION=1897326]googy_anas[/MENTION]

I see you've merged my commit. I'm glad if it helped, at least a bit :).
[Galaxy S III Original Android Development] DaReDeViL:
:highfive:

Merged but not tested yet even though I am sure your patch will make things better.

Thank you very much ;)
[Galaxy S III Original Android Development] JustArchi:
Please do so, as outputs of my commands may differ from yours and then you need to adjust values in ifs. It works on my side, but I'm not sure if it will for everyone. I tried to make it as compatible as I could.

Hope it will :).
[Galaxy S III Original Android Development] BLEK0TA:
plz can someone put here antutu 3.4 results? only from these version antutu.. thanks
[Galaxy S III Original Android Development] Antidote03:
i see the process com.android.phone has stopped in Temasek Rom v64

Waiting the new version of googy kernel to adapt to the ramfs change CM did :D
[Galaxy S III Original Android Development] JAlfredoP:
Me too, same issue whit the phone
[Galaxy S III Original Android Development] llewelld:
Hi Guys,

I'm posting this here, as this very weird stuff has just started happening to my phone since installing this Kernel - it may be pure co-incidence but I would love any confirmation from any experts..

I have a GS3 i9350, that has just started doing some weird stuff. Currently, I cant turn it on at all (tried 2 different batteries both that have some charge, (have unplugged the battery), and when I connect a charger, even this doesn't change anything. (no led light comes on).

It did this last week, and I thought I must have water damaged it. (maybe sweat in pocket etc) - didnt really get it wet as such.

Two days after the first time, it came back on... I was actually just about to list it on ebay as damaged spares, but it fired back up and worked great.

Then yesterday after a full day of working great, I put it on flight mode last night, and this morning, it wouldnt turn on, and it wont charge..

very weird. Have tried a 2nd battery to no avail.

The issue has co-incided with me changing the kernel to Googy max (running PA 3.99rc2) (currently 75mv undervolted), but if this was causing it to not turn on (would the charge light still come on even if it wouldn't boot ? )

A bit bizzare.. Does it just seem like an intermittent hardware fault or could software kernel / undervolt issue?

FYI I was able to run for most of a full day @ 75mv undervolt with no issues at all.

Have also pulled apart and made sure all ribbon cables etc are securly connected / screen etc, no clear signs of anything wrong.

Thanks.
[Galaxy S III Original Android Development] jinosong:
Just switch to another kernel to see if it's the kernel or not. Most likely, it'll be a hardware issue.
[Galaxy S III Original Android Development] pricey2009:
I don't think this kernel works for the i9350. . Try a kernel made for that version perhaps
[Galaxy S III Original Android Development] llewelld:
Sorry that was a typo - i9300

The kernel was working for a whole day.. before this happened.

The problem is, I cant get into anything, ie, Screen wont turn on, cant access recovery, no led when I plug usb or direct charger...

If I cant get into recovery, would that eliminate the kernel undervolting issue - ie.. does the kernel get used to get into recovery? assuming it doesnt..??
[Galaxy S III Original Android Development] Maplobats:
Not sure what a i9350 is, but this kernel is for the i9300, so unless that is what you actually have, using the wrong kernel might very well be the problem.

Edit: just saw your reply, it certainly does seem like a hardware issue.
[Galaxy S III Original Android Development] JustArchi:
Undervolt does not apply when you're turning on your phone, as it's bootloader which turns the device on and loads the kernel. Kernel can apply anything after it has been loaded by bootloader. Recovery is static image loaded directly through bootloader, it does not utilize rom kernel (only small indepdendent recovery kernel).

Whatever happened to your phone, Googy's kernel wasn't a problem. If bootloader doesn't pop up (yes, samsung galaxy s3 logo) then you either screwed up hardware or hard bricked it by flashing wrong bootloader, eventually your eMMC card is dead (f.e. through sudden death).

However kernel is a very important and powerful thing in your phone. Yes, it can damage phone both from overvolting and undervolting. In OC your cpu may literally burn while in uV you can get very unstable CPU and nobody knows if something bad couldn't happen directly from that.
[Galaxy S III Original Android Development] llewelld:
Just so odd that it didnt work for a few days, then worked for a few days.. now back to not switching on..

time for a nexus 5...
[Galaxy S III Original Android Development] stevae:
everything has been working fine, but lately it seems that my phone takes a longer than normal time to switch from one app to another, or to close or open an app. i am on a s3 i9300, using the latest omega rom. i have run a clean up program to see if that was the problem, but still runs slower than normal. anyone have any ideas of how i can fix this, or what might be causing it?
[Galaxy S III Original Android Development] xclub_101:
What is your uptime? (Settings -> About > Status)

Do you have zram enabled?
[Galaxy S III Original Android Development] ric69:
Thanks for info :good: Same problem with last Nightly here on 2nd rom
[Galaxy S III Original Android Development] earthman5678:
Welcome to SDS. The eMMC die on you. Could you tell me if you ever update your bootloader to JB's? Or you been running on ICS bootloader all this while?
[Galaxy S III Original Android Development] jumpers:
update please. :(

since 22/10/13, googy-max kernel cause a com.android.phone forceclose, please update. :(
[Galaxy S III Original Android Development] chrismast:
i doubt that this is connected to the kernel, what ROM etc. are you using? did you clean flash it etc?
[Galaxy S III Original Android Development] JustArchi:
It is. Googy's ramfs is outdated and doesn't work with any CM releases 23.10.13+.
[Galaxy S III Original Android Development] amppen:
It's funny how things get "outdated" here in custom firmware world. If you're using stock you're lucky if you get a couple of updates in a year, but here it takes just a few days to have your ramfs, Linux version and whatnot to become yesterday.

Patience is a virtue ;)

(...I know [MENTION=5161352]JustArchi[/MENTION] didn't mean it like that when he said outdated, I'm just saying)

Tapatalked
[Galaxy S III Original Android Development] DaReDeViL:
can you pm me justarchi's gps coordinates? ;)

I am coming for dinner... :p

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] JustArchi:
https://github.com/googyanas/Ramfs/pull/3

Don't nuke me :angel:
[Galaxy S III Original Android Development] DaReDeViL:
The first patch did speed things up but somehow considerably slowed stweaks loading!

I reverted the first patch then made the swapoff and swapon commands in parallel and now it's perfect

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] jstegeman:
Call volume boost (like in sammy ROM's default-gain.conf)

Hello,

Sorry if this is answered in here already - I did try searching and didn't find anything.

I'm hard of hearing - so I generally like to boost the call volume on my phone. I've been using derivatives of Sammy ROM's, and the standard way to fix the volume there is to edit the default-gain.conf file - works great. I'm now trying ParanoidAndroid with this kernel - is there any way to increase the call volume (not speaker calls or headset calls or bluetooth calls - just calls when using the thing like a normal phone)? I've poked around in STweaks and didn't see anything obvious.

Thanks,

John
[Galaxy S III Original Android Development] FadeFx:
Afaik there is currently no way, but probably anas can add this, we will see.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Nichie:
+1 to this. Unlikely we will see official sources for 4.2.2 since Samsung said they will be skipping it for 4.3.

No point for them to create sources for something they are not going to develop
[Galaxy S III Original Android Development] Kord:
Currently, we have leak of Android 4.3 for AT&T version - > http://www.sammobile.com/2013/10/26/android-4-3-leaks-for-a-bunch-of-att-samsung-devices-galaxy-s3-note-ii-s4-and-s4-active/

I'm convinced, we can expect Android 4.3 for international version of SIII in a few days :good:
[Galaxy S III Original Android Development] Rambooka:
Is there any chance of this kernel finding its way onto the s4 ? I really miss the the dual booting my s3 had...
[Galaxy S III Original Android Development] Nichie:
Hope so too!

S4 in my country got the 4.3 update already
[Galaxy S III Original Android Development] FadeFx:
A leak is no help at all, as they dont release kernel sources before official release and we can not build a custom kernel without sources. Same situation as 4.2.2 currently.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Kord:
I know, but 4.3 is confirmed, not like 4.2.2

We can expect sources quickly if leaks are present :)
[Galaxy S III Original Android Development] zodiaxe66:
your kernel is not working at all and I'm really dissatisfied with your kernel..

when I put my phone in flight mode, it doesn't take of (in any direction) and when I try to throw it,it crashes immediately after.not good

please fix

Edit: otherwise everything else is working just fine:D
[Galaxy S III Original Android Development] PIRATA!:
What is this patch all about, please?

About the kernel...I've read that someone says something about that undervolts....

Is the Googy-Max kernel undervolted by default??

I am having a little bit of lags and slowing down if the phone since I've flashed last Googy coming from last Siyah.
[Galaxy S III Original Android Development] DaReDeViL:
Thank you

I just hope you can afford taking the responsibility of me having a heartattack because of you :p

Sent from my Googy-Max powered S3 ...
[Galaxy S III Original Android Development] stevae:
i did have zram enabled, but have since disabled it. i restart my phone often, so don't have an answer for that. (settings, about, status????)
[Galaxy S III Original Android Development] chrismast:
How many cores heartattack? :)
[Galaxy S III Original Android Development] xclub_101:
After some time since last boot (for me 2-3 days) and with zram (but I have not tested without in a long time, it might be possible to be the same without zram) the phone also becomes slow (and during the 4th day usually it reboots by itself). The fix is to reboot every 3 days or so - something that anyway most people do.

Other things that can slow-down the phone - many programs running in the background (especially the media scanner), and in time a certain degree of free-space fragmentation on the flsh (which is why you should ALWAYS have at least 4 GB of free space on internal flash).
[Galaxy S III Original Android Development] jumpers:
what means EOL ?

release 1.7.7 update please. :(
[Galaxy S III Original Android Development] JustArchi:
End Of Life.
[Galaxy S III Original Android Development] Olioaglio:
And what is EOL? Hope not this great kernel?
[Galaxy S III Original Android Development] JustArchi:
No, probably he means linux kernel branch.

Version 3.0.101 is the last version of linux 3.0.X branch. This branch is now EOL'ed, that means you won't see updated upstream anymore.
[Galaxy S III Original Android Development] dheeraj (dhlalit11):
A small request

Can you please (in the next version) increase the amount of luminance which will be shaved off

From 128 to something like 180 or 200

Highly required for night usage

And Waiting for the new upload
[Galaxy S III Original Android Development] amppen:
You've already tuned low end autobrightness to zero value at ROM settings?

Tapatalked
[Galaxy S III Original Android Development] dheeraj (dhlalit11):
Didn't get you

Can you explain what you are trying to explain
[Galaxy S III Original Android Development] FadeFx:
Only available in cm based roms, not in samsung roms.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.7.7 ONLINE !!!

- Linux: Updated to

Linux 3.0.101 (EOL)

- Ramfs(cm10.2): Updated to latest cm10.2 ramfs & Fix BT tether (thx cm)

- Reverted Optimized memcopy mechanism (causing lags)

- Stweaks: Corrected some typos (thx FadeFx)

- Stweaks: Disabled all optional features by default (mdnie, dyn_fsync, touch2wake, zram)

- Ramfs: Added support for standard framework2.jar

Happy flashing :D