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

you can find here logcat and dmesg dump when i try to connect a wifi nextwork with MH1

dmesg: http://pastebin.com/Vsvgwnk0

logcat: http://www.sendspace.com/file/rzer94

here you can find a cwm version of rooted stock MH1:

http://server01.xdafileserver.nl/index.php?dir=Ultimarom%2FStock

sry for sendspace link but logcat dump was to big for pastebin.
[Galaxy S III Original Android Development] peramikic:
Zram is @ 4x200 80%

OC @ 1600 with UV and ABB

GPU OC to 700

Pegasus tweaked for hotpluging

All frequencies tested for stability

I have ran this setup since 1.6.5 with no problems. I'll attach the profile if you need it

It could be zram ...
[Galaxy S III Original Android Development] xclub_101:
Those are very classic signs of memory shortage and huge amount of swapping towards zram, which tends to suggest an overload and possibly some form of memory leak. On i9300 with normal memory content and current compression algorithms I believe the max. amount of usable zram is around 400-500 mb anyway.

In the meantime I have finished my test with 4*100 @ 90% and the problem was still there but a lot more subdued, instead of 24h to reach heavy swapping I got closer to 48h.

My personal feeling is that there is a very serious memory leak (possibly related to zram but is not excluded to be from some de-allocation in the dalvik vm or at least related to something like that through heap fragmentation) - I have seen previously in many configurations the very same problem. Before 1.7.2 (where my optimum setup seems to be 4*100 @ 90%) I was using 1.7.0 with 400 @ 90% and the leak was only becoming noticeable after more than half of a week- this is very consistent with the idea of a leak that now is becoming 4 times more aggressive (since now we have the swapping in parallel execution but also have the leaks too) - I will do a new test for a few days in that older configuration (1.7.0 with 400 @ 90%) and I will post the results.
[Galaxy S III Original Android Development] shassino:
Same issue with XXEMG6
[Galaxy S III Original Android Development] noobSU:
Updated the kernel. Lost my profile.
[Galaxy S III Original Android Development] hisee:
Can any one share cpu-uv setting? I never playd wid this setting
[Galaxy S III Original Android Development] peramikic:
This is very subjective since chips have different tolerance so they are binned in ASV groups. So what works for me may put you in boot loop. My suggestion is set -50 global via steaks run for few days then try 75 again few day, try to stress the phone. Then if OK try 100. If you get reboots back down to previous level. You can look under my posts here, I posted my profile but it is heavy OC/UV/ABB for ASV3 and might cause boot loops

One note on UV...it will not save you any battery...not reality. I will let you OC for less power so there is that but biggest benefit is heat reduction which prevents throttling.
[Galaxy S III Original Android Development] hisee:
Can't find profile... Can u guide which r the stff that help to increase battery life, inc performance.. Governor setting
[Galaxy S III Original Android Development] peramikic:
Your #1 battery drain is the screen so either drop the brightness to low or if you use auto then adjust the curve to lower values . also go with dark theme as amoled as screens light up individual pixels so more black on screen means less power. I use cm10 blackedout theme + backedout apps and no wallpaper.

As far as idle drain lookup Greenify app here on XDA. It let's you hibernate apps after 5 min screen off. The donate version is particularly awesome as it let's you get rid of apps like Facebook without loosing ability to receive messages...read the app thread for in depth explanation.

After that is done you can use betterbatterystats app to see if you have any runaway processes on the kernel level that need to be addressed

Last thing is apps that use WiFi/3g in background presenting you phone from sleeping properly. They need to be dealt on case by case basis like changing their sync intervals to longer period or to manual. Greenify can help a bit since hibernated apps can't use data until you start them

To maintain the battery saving with little performance loss use zzmoove governer with balanced profile until you read the first post in zzmoove thread several times :D once you get a grasp of concepts like hot plugging you can tweak the values to you liking even on other governers

This should get you 80% of maximum battery saving...and keep you busy for a while... The other 20% might very well push you over the edge to a path of daily BBS log comparisons, location and time based profiles, activity based governor switching etc...

If the first thing you do when you wake up is check the BBS or wake lock detector, you crossed that line...welcome to the dark side...we run out of cookies but we do have some mean tasker profiles ;)

TL; DR http://xdaforums.com/showthread.php?p=44938158
[Galaxy S III Original Android Development] hisee:
I am using neon theme rest i am doing all above stuff except greenify donate ver and governers tweaks
[Galaxy S III Original Android Development] peramikic:
:thumbup:

Time to jump over to the dark side then :D
[Galaxy S III Original Android Development] DaReDeViL:
Phewwww. If I ever wanted to be so precise I would surely be faaaar away from such explanation. I think if you allow it, I will paste it in the faq. ;)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] hisee:
But still gets only 2-2.30hra scree on :( still dark side is far away
[Galaxy S III Original Android Development] MrxSiN:
5 hours and a half screen time on 1.7.2. Good :D
[Galaxy S III Original Android Development] peramikic:
Go ahead, nobody reads it anyway :p But I'll know where to find it for future reference
[Galaxy S III Original Android Development] FadeFx:
Lol... you may be right...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] zadusimple:
Well I am a big fan of this kernel. One issue, sound quality while using voice recorder or while sending voice messages via what's app is not so good compared to stock kernel. I mean recording audio is not of good quality. AM I doing something wrong? Please advise.

Sent from a better Galaxy designed for humans!
[Galaxy S III Original Android Development] FadeFx:
Try adjusting mic input gain...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] mitchpunk:
[MENTION=3253628]zadusimple[/MENTION] adjust the mic level down to 21 or so.

That should be better...

Closer to stock.

Sent from my Paranoid GT-I9300
[Galaxy S III Original Android Development] W@r10ck:
OMG! The sound is amazing :)

:thumbup:
[Galaxy S III Original Android Development] habylab:
Settings? :D

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Galaxy S III Original Android Development] Handeman707:
Is there a goofy kernel cleaner something?

Tapatalk version 2
[Galaxy S III Original Android Development] amppen:
:D I'd rather use a non-goofy one.

Jokes aside, I think there is not. I try to watch this kernel pretty closely.
[Galaxy S III Original Android Development] DaReDeViL:
Huh? Goofy ? The one from Walt Disney ? :p

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] zodiaxe66:
Goofy, noo...he's more like gyro gearloose:silly:
[Galaxy S III Original Android Development] drdax:
Gotta say ...love this kernel
[Galaxy S III Original Android Development] drmjp93:
I have battery drain problem, can any one experienced give me tips to do my battery save?

ParanoidAndroid | i9300

www.dadabhagwan.org
[Galaxy S III Original Android Development] querotequila:
Googy,

I ask before but I didn't get a reply ...

Do you would do the custom LED controls like Perseus kernel, please? :fingers-crossed:

The LED fading combo it is already there, but I miss the Blinking control.

Sometimes I think I lost some notification and I have to look a little bit longer to see if is blinking!

I like to adjust to a quicker blinking pattern.

Sorry to bother you again!

Thanks for your great work!

I love your kernel!
[Galaxy S III Original Android Development] DirkStorck:
[MENTION=1897326]googy_anas[/MENTION]:

Is this something you could add in your kernel or isn't it relevant for our device ?

l2_hsic fix P4 (GT-P7500, GT-P7501) running CM10.1

Thank you!
[Galaxy S III Original Android Development] MakDroid:
Well, I am not that experienced but i have enough to help you out. I too had battery drain problems with this kernel while using Wanamlite ROM but I realized that tweaking stweaks very much leads to this(We could have changed some settings by mistake that caused battery drain). I would suggest to do a full wipe then install the ROM you wish then the latest kernel. I personally prefer pegasusQ governor in stweaks. Its the best combination of battery and performance! Btw i live near you only! :D
[Galaxy S III Original Android Development] drmjp93:
Next to my apartment?

Settings areas per yours.. But battery gets drained more than cm kernel...

There must be another way but I can't figure out... :(

CyanogenMod 10.2 | Googy-Max

www.dadabhagwan.org
[Galaxy S III Original Android Development] ThePureHeart:
Post an idle BetterBatteryStats log and someone can help you find out what's eating your battery.

To learn how, check the BetterBatteryStats thread.

Sent from ThePureHeart's I9300 Boss Edition

ParanoidAndroid | Googy-Max
[Galaxy S III Original Android Development] xclub_101:
Evolution in time of values reported for swap by "free"?

Has anyone checked the evolution in time of the values reported for swap (zram) by the "free" command?

If from a terminal or adb command line you issue the free command you get to see the swap, which in this configuration is about zram.

I suspect there is a memory leak somewhere in zram or in the cross-operation between zram and dalvik vm - the leak is very small and takes a lot to accumulate, - on devices with 1 GB of RAM by going in parallel at 4x the change becomes clearly visible after 24 hours and requires a full reboot after at most 48 hours. With non-parallel zram (and same values of swap and swappiness) it only needs a full reboot after a week or so.
[Galaxy S III Original Android Development] DaReDeViL:
I noticed that too and I am testing some new stuff to see if it gets better ... Thanks for reporting ;)
[Galaxy S III Original Android Development] habylab:
Most likely a stupid question : I see in stweaks, firstly 2 bugs. I see hotplug sleep 3 times. Disable hotplug sleep drop down and then 2 hotplug sleep slider?! Also, down threshold of 4th core is Max of 70, ideally, I'd like 80 if possible?

Also, here may be the stupid bit... I see legacy mode is enabled by default. I googled to try and find out about it, and saw something on Google preview about how you inverted the values. Surely I'd want legacy mode off? So does enable, if inverted, cause it to be disabled? Same goes for disable hotplug sleep, surely I'd want that disabled?

Edit: I also can't find an up threshold sleep setting. This is vital, as I get call cut outs frequently.

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Galaxy S III Original Android Development] DaReDeViL:
These values, as far as I remember (I am away from my laptop), are inverted like you guessed. But I will check again once I get home.

About the other possible wrong tunables, I will take a look at them and correct them, if necessary, within the next version.

Thank you for the report ;)
[Galaxy S III Original Android Development] habylab:
No problem, and thank you! Also, no up threshold sleep setting or am I blind?!

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Galaxy S III Original Android Development] DaReDeViL:
Surely you're not blind or you need stable updated dual-boot glasses :p

I'll check that too ... ;)

Thx
[Galaxy S III Original Android Development] beginnerteur:
Why no CPU OC up to 1,8 GHz?

PS: Very nice and useful kernel! Thank you guys :good:
[Galaxy S III Original Android Development] qtwrk:
Because 1.6 is fast enough, you don't actually need a 300 km/h car while you already have a 250 km/h car although your highway limit is 120 km/h :p
[Galaxy S III Original Android Development] Simone.:
+1 :good:

on a previous version of siyah kernel it was possible to boot more than 2 ROMs.

Are there any chance to see than on googy ?

Tnks
[Galaxy S III Original Android Development] Scarface1991:
1,6 ghz is fast enough and also I think that 1,8 ghz would produce too much heat.
[Galaxy S III Original Android Development] stevvie:
End then there's the extra battery drain just for an extra 200Mhz, that only will really be seen in benchmarks :)
[Galaxy S III Original Android Development] DaReDeViL:
The siyah mod app should still work with googymax because it plays with the .secondrom folder not with the kernel itself

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] noobSU:
Are there any limits for the storage in sd card? Or in ROM partition for 2nd rom?
[Galaxy S III Original Android Development] DaReDeViL:
The secondrom filesystem is placed in internal storage

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] djclark25:
Hi there.

I am using a version of MIUI from the forums here, that is based on CM10.1. I have installed 1.7.2 and i have a problem where, once touched, the hardware buttons stay permanently lit.

Using 1.7.1 this doesnt happen. I see in the changelog there is " CM10.2 : Fixed keys backlight disabling" Has this somehow caused the issue in MIUI?
[Galaxy S III Original Android Development] falconhawk81:
Hi googy, yesterday i want to make a backup of EFS becouse i unlock my phone, and flash the kernel again but dont make a new files from efs, is that right? Thanks for a wonderful kernel!
[Galaxy S III Original Android Development] peramikic:
Yup the old cm10.1 and the new 10.2 method for controlling back light are incompatible for now
[Galaxy S III Original Android Development] Olioaglio:
[MENTION=1897326]googy_anas[/MENTION]

Please would you also increase the tunables for zzmoove down threshold hotplug?

As for yank battery extreme they should be:

zzmoove - down threshold hotplug1 set to 65.

zzmoove - down threshold hotplug2 set to 75.

zzmoove - down threshold hotplug3 set to 85.

which is not possible because the corresponding sliders are limited to 70.

Thanks, Olioaglio
[Galaxy S III Original Android Development] Viper_21:
Hi,

I am finding that Touch-to-Wake has a considerable drain on battery, far more than Siyah's slide-to-wake.

1. Can you recommend any other settings in STweaks that will lessen the drain while the Touch-to-Wake is enabled?

2. The screen text under the Touch-to-Wake setting says that the default delay is 20ms; however the slider only allows increments of seconds. How can I manually return it to 20ms?

3. [feature request] I would like a "configurable" shortcut to STweaks that would allow me to set one of the three profiles. This would allow me to automatically set a given STweaks profile via EasyProfiles or Tasker. My main use case here would be disable Touch-to-Wake at nighttime when my device is set to night mode. I also an app called Secure Settings - perhaps the profiles are reachable through there?

Thanks.

-viper21
[Galaxy S III Original Android Development] Yank555:
How long did you set it to ?

TTW will set a wakelock, hence prevent the device from sleeping and keep the touch screen operational for the given amount of time you set.

If you set it to 0, it will be "forever", hence battery drain is a certainty, then.

But used correctly, there's no battery drain worth mentioning using it.

I keep it set to 5 seconds, as I use it simply when reading takes me a little longer so I can wake the device by touching the screen rather the having to aim and press the Home or Power hardware key.

But there are other uses, with longer time settings, of course. It all depends what you want to use it for.

But 20ms makes pretty little sense to me to be honest, nobody reacts fast enough to touch the screen within such a tiny timeframe :eek:

JP.
[Galaxy S III Original Android Development] zodiaxe66:
Use k-tool or andromizer from market to back-up EFS(imei) folder,then kopi/sent your back-up to your PC or dropbox so you always got a safe storage back-up of your EFS folder..
[Galaxy S III Original Android Development] peramikic:
Hey [MENTION=1897326]googy_anas[/MENTION] i got another log for you although this one is a little unsettling since the phone just shutdown on it's own while i was editing some photos, plugged in and did not restart... I can't see anything wrong in the log though, maybe you can...

http://pastebin.com/ZuBVcURb

Edit make that twice now, same conditions... i'll attach another last_kmesg

http://pastebin.com/k2msxctP
[Galaxy S III Original Android Development] drmjp93:
I have been experiencing heat on playing game for even 15 min with no sound, least brightness, temp was 51°C, later I reduced the CPU TO dual core with 1 ghz.. Should be alert?

CyanogenMod 10.2 | Googy-Max

www.dadabhagwan.org
[Galaxy S III Original Android Development] Viper_21:
Typically I have been using "0" (forever) delay since the max limit of 60 seconds is way too short for me - I mostly use TTW in the car when listening to music, which means I use it normally once every 2-3 tracks (approx. every 2-15 minutes).

Would the developer of Googy Max consider increasing the max limit to a range of minutes (like 10 or 20 or more) and not just to 60 seconds?

Another useful feature would be to keep TTW on regardless of the delay setting while the phone is being charged.

I am still keen to hear if there is a way to set a shortcut to activate one of the STweaks profiles?

-Viper21
[Galaxy S III Original Android Development] FadeFx:
I think using tasker i could build you an app that changes the value to 0 when the device is connected to charger and back to a choosen value when unplugged. Probably it would be even possible to set longer delay than using stweaks, but i am not sure about that.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] trein91:
Is it possible for you to set "ignore unstable power detection and the 100ma safety margin" ala Perseus kernel (AndreiLux) and later on used by other kernels based off it like Devil Kernel, Temasek Kernel etc?

Issue is that my phone tends to charge at only 100mAh sometimes when charging via USB, even when I set it to 900mAh+.
[Galaxy S III Original Android Development] Volpe92:
[MENTION=1546289]googy[/MENTION], I just can not run whatsapp with dualboot! the method on the front page is not working! :silly:

please do something :)
[Galaxy S III Original Android Development] peramikic:
[MENTION=1897326]googy_anas[/MENTION]

Got another crash with reboot. Same modules as last time put panic was on null pointer to virtual address this time...I'm leaning towards zram more and more

http://pastebin.com/KYyEJYrE
[Galaxy S III Original Android Development] DaReDeViL:
Please reset stweaks settings then reboot and keep default values for one day or two.

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] habylab:
Anything Googy or still looking? No rush!
[Galaxy S III Original Android Development] DaReDeViL:
Just finished "looking" at barça-ajax now I'll start looking into the kernel ... ;)

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Original Android Development] habylab:
Why not let Arsenal? Carzorla to the left of me, ozil to the right, stuck in the middle giroud!
[Galaxy S III Original Android Development] DaReDeViL:
Just to see how the duo messi-neymar is evolving ... and because I am a Barça fan !!!
[Galaxy S III Original Android Development] DaReDeViL:
Maaaaan, you are far from being blind, you were right all the way, except for up threshold sleep which is already there and default is 90 !

Back to "looking" mode :p
[Galaxy S III Original Android Development] DaReDeViL:
Done ! All maxed to 100
[Galaxy S III Original Android Development] Viper_21:
[MENTION=2446031]FadeFx[/MENTION]: Thanks for the kind offer. Before we go down that path I'd like to hear from googy_anas if there is a possibility to enhance STweaks to extend the delay of the TTW max limit and to provide an Android shortcut to a selectable STweaks profile.

-Viper21
[Galaxy S III Original Android Development] DaReDeViL:
Stweaks app doesn't allow multiple scales on a slider, so raising the max value to, let's say, 600s it will be really really difficult to precisely set any value.

I think FadeFx's idea is good or you can also try to disable screen timeout in your rom settings when you use your phone asa music player while driving.
[Galaxy S III Original Android Development] Viper_21:
Would it not be possible to change the measurement unit of the delay slider from seconds to minutes? Not sure if everyone already using TTW would be in agreement with this though. :fingers-crossed:

I prefer not to have screen on all the time in the car. A 45 minute drive to my work with screen on all the time would be too expensive on the battery. :crying:

With your deep knowledge of the kernel, would FadeFX also theoretically be able to create a Tasker plug-in that could activate a user-selected profile in STweaks for whatever condition the user decides?

-Viper21
[Galaxy S III Original Android Development] DaReDeViL:
It's on my todo list :cool:

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] MrxSiN:
possible to dual boot 2 AOSP rom?
[Galaxy S III Original Android Development] peramikic:
Yes, I got ASOPA 3.5 AND CM10.1
[Galaxy S III Original Android Development] tintin1503:
I've gotta admit that this version 1.4.1 is the smoothest of all.

And what have you done to the sound man, the difference is clearly visible.

Using Sammy 4.1.2 + CM 10.1 with amazing battery life and performance.

Hatsoff to the master !
[Galaxy S III Original Android Development] arhant:
dude i dont care oc or not..

but the sound==wow..!

and can you add screen calibration to it..the master sequence..

perfect kernel..
[Galaxy S III Original Android Development] tracemonkey:
Just switched over from siyah. This is good work! I agree with the previous comments about sound.

I'm dual booting stock 4.1.2 as primary with cm 10.1 nightlies as secondary. What I'd love to see is a way to use cyandelta (or similar approach) to keep my secondary on the latest nightly as efficiently as possible.

Cheers

TM
[Galaxy S III Original Android Development] suemer:
Excellent performance with cm 10.1 and stock 4.1.2... - really good job.

i have tried the new version sammy 4.2.2 - for now and for me very laggy...
[Galaxy S III Original Android Development] x3sed:
Thanks. I just installed your kernel. I don't know yet about its performance. But since the feedbacks are quite good. I guess it's gonna be smooth.

I'll give a little review after 2 or 3 days. Your updates are so fast that i don't think I'll have enough time for a 2, 3 battery cycles :D

Keep up the good work and banzai to Moroccan devs ;)
[Galaxy S III Original Android Development] andrewilley:
Sorry, but LOL. :)

Andre
[Galaxy S III Original Android Development] FPSKunal:
The best way to sync app data between 1st and 2nd ROM is. First boot into your 1st ROM and use titanium to backup app and data and once it is done copy the titanium folder and paste it into sdcard/o and then boot into 2nd ROM and install titanium and titanium will automatically detect the folder and then you can restore app and data. For whatsapp you can't do that because you can use whatsapp only on one ROM because whatsapp will ask to verify your number each time you boot into one of the ROMs as whatsapp uses your phone number for registration.

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2