yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] KMino:
Just a question :) maybe bug..

Have been running 0.5.1.2 - 1200 on Simply Honey 5.1 for a while no problems. Flashed 0.5.1.3 - 1200 earlier today.

Any compatibility problems with JVR? As phone has been good untill tonight, gps, net, calls where fine. Used it for a bit when I got home, then plugged it in to charge on USB. Then the screen wouldn't turn on, battery had to come out. :(

No funky changes, same UV settings (actually milder than they where).

Anyway, cheers for reading all that keep up the brilliant stuff :)
[Galaxy S I9000 Android Development] existz:
It should be compatible, same as last test..only thing that changed in regards to rom/versioning was added JVT modules (mainly for RFS and FM).. but the other changes could effect how the CPU scales, putting less load on the CPU, in return spending more time at lower frequencies than before...try with no oc/uv, and make sure your not using any 3rd party scripts/tweaks..etc..or sleep profiles/screenstate scaling scripts. If it doesn't happen with no oc/uv and no scripts/tweaks, then something else is causing it.. if it does happen with 1ghz version and no UV, then let me know..but usually this is caused by unstable oc/uv (which can change from build to build) or some script/tweak
[Galaxy S I9000 Android Development] st4rk:
I haven't had any problems so far on latest kernel and JVR..
[Galaxy S I9000 Android Development] shaarky:
After one day - running very fine on JVT rom, with same OC/UV as on JVS before :-) Thank you
[Galaxy S I9000 Android Development] Andy3athlon:
Hi! I'm loving this kernel, with zram and bigmem finally got my galaxy working good in multitasking use! But I would like to try to push my processor a little bit more..any chance to have also a 1400-1500mhz version..? :p
[Galaxy S I9000 Android Development] Mangus_U*RA:
I think i've found a bug.

Usually at night I set my phone in airplane mode.

I've set it while the battery was at 92%, when I woke up this morning it was at 54%!!! Usually it consume just 1% of battery at night in airplane mode...

After a check with android status, there are no strange things running...

A look at battery usage, and I saw that the phone remained "active" all the time!!!

The "android system" resulted always active with over 70%.

With control freak I also niticed that it never went to deep sleep mode! While in airplane mode it remained always at 100Mhz.
[Galaxy S I9000 Android Development] pikachu01:
Try using BetterBatteryStats to root cause the problem. There might be some wakelock activity going on from an app.
[Galaxy S I9000 Android Development] Mangus_U*RA:
I'll try, but in the last few days I've changed only 2 things: kernel and modem (flashed jvt).

---------- Post added at 12:08 PM ---------- Previous post was at 11:29 AM ----------

for what I can see now with BBS, under "partial wake locks" I have more than 12 Hours for "notification service".
[Galaxy S I9000 Android Development] Mangus_U*RA:
flashed again both modem and kernel and now it seems fine...but i will monitor the battery.
[Galaxy S I9000 Android Development] pikachu01:
Not sure what notification service is, but it's app related. Try pinpointing what it is and then freeze the app and see if it happens again. Some badly coded apps sometimes don't work well with certain devices/ROMs.
[Galaxy S I9000 Android Development] Guto ViP:
Existz, have any possibility of do you make a Memory Freak version to use with another kernel? I mean... I'm using Mafalda kernel (based in Talon kernel) for I9000B, but i can't use Memory Freak config.
[Galaxy S I9000 Android Development] Nash123:
Love the new jvt-version. Big thx to all who made it possible.
[Galaxy S I9000 Android Development] existz:
I will check with shane87 and see, we originally made it only work with original Talon because with some Talon variants they change LMK settings, ..etc..etc.., and MemoryFreak is originally built and tested against Talon..so to keep it from causing issues (mainly Talon profile) we made it check kernel version.. You can have the dev of i9000b use the exact same kernel version name as talons and it should work then..
[Galaxy S I9000 Android Development] pikachu01:
Hey existz,

I think I found the cause of the memory leak. Can you do a:

echo 0 > /proc/sys/vm/overcommit_memory

After that, try your hardest to fill up the the memory by opening up as many apps as possible. See if you can trigger the lagginess or not. And yes, you won't get back the same memory even after you kill those tasks, as Android will fill it up the instant you kill those apps.

What's important though is that you won't feel lagginess anymore even though you constantly open/close apps and have your uptime > 48 hours without rebooting.
[Galaxy S I9000 Android Development] jeebspawnshop:
I just typed this in to my terminal - let's see how it goes.

Even if it does not work, I gotta thank you for helping, Pika ;)
[Galaxy S I9000 Android Development] existz:
0.5.1.4 Public Test

UPDATE

0.5.1.4

- updated scripts removed during install

- added newmail's deep sleep detection

- added smartass2 governor by Erasmux

NOTE

Added NewMail's Ondemand deep sleep detection patch, let me know how things

are performance/battery wise. Also added Smartassv2 governor, this is only for

you guys to play around with and test.

.if you have any issues then switch back to

ondemand before posting any issues

..Ondemand is still default and recommended
[Galaxy S I9000 Android Development] chiefy009:
Will test out smartass had that on my x10 and it was very good
[Galaxy S I9000 Android Development] existz:
Yea smartass done ok, with smartass2 its alittle different...With the original smartass there were issues with it scaling when oc'ed higher than 1.2ghz, so beware with v2, not sure if it happens with it also or not.. Also, ondemand should provide better performance than smartass2, and with the deep sleep detection patch from newmail, it should give better battery results also.., basically just added it for those who wanted to try it.. I currently use it on my Inspire and it does pretty good, but the scaling/frequencies are so much different than SGS, not sure how its going to work.. (Inspire uses 25-50 cpu steps, compared to 5 with SGS, the way everything is done on HTC is completely different, which smartass was originally wrote for, so it might not work as well )
[Galaxy S I9000 Android Development] chiefy009:
Smartassv2 performance is awesome very snappy and smooth will use all day tomorrow to assess battery life so far performance wise it is awesome
[Galaxy S I9000 Android Development] rodirodi:
Seams very promising so far! Thanks Pikachu!
[Galaxy S I9000 Android Development] Szighy:
shouldn't it say something in the emulator when I type in the code and press enter? I typed su, enter, then the code...

---------- Post added at 11:31 PM ---------- Previous post was at 11:30 PM ----------

hm... I find that ondemand is better
[Galaxy S I9000 Android Development] existz:
No, its not going to say anything after you enter the command and press enter, it will just drop down to the next line...you can do the following to see if it worked..

cat /proc/sys/vm/overcommit_memory
[Galaxy S I9000 Android Development] rodirodi:
Yes, it should be silent.

(oops.. already answered by existz :))
[Galaxy S I9000 Android Development] Tatsuya79:
0.5.1.4 Public Test - Neutral Colours Version
[Galaxy S I9000 Android Development] flolep:
So could you please analyze the new Pikachu's command and say what it does and if it is indeed resolving the famous talon memory leak and how easily and automatically it could be integrated to talon kernel?

Thanks in advance :-)
[Galaxy S I9000 Android Development] Szighy:
famous? it happened with every kernel I tried so far...
[Galaxy S I9000 Android Development] existz:
It is already in the kernel...your just changing a tunable variable.. all you have to do is create or add that command to an existing startup script for it to apply on boot.., but i have not looked into it, which i dont think overcommit_memory=1 (samsung default) is exactly whats causing the memory leak, so if anything setting overcommit_memory=0 is just helping keep the leak from being noticable.. Theres a very very good chance that the leak is caused from zram or swap support in the kernel (this much we have figured out already, kodos96 believed it was in zram), just dont know where yet.. Which theres probably quit a few swap/vm sysfs files that can be tuned to keep the leak from being as noticable, but it still does not fully eliminate the leak...but heres info on what your actually doing when you apply 0 to overcommit_memory
[Galaxy S I9000 Android Development] pikachu01:
Actually 0 is the default:

http://www.linuxinsight.com/proc_sys_vm_overcommit_memory.html
[Galaxy S I9000 Android Development] existz:
For linux yes, but if you look in init.rc it sets 1, so samsung/android default is 1 (on HTC Inspire 1 is default also)

Line 533

write /proc/sys/vm/overcommit_memory 1
[Galaxy S I9000 Android Development] pikachu01:
Ahh, k. That's why many people across kernels are getting memory leak issues?

Talon might be doing something extra in ZRAM that increases the likelihood of memory leaks. So far, reducing my LMK aggressiveness (40MB HiddenApp) and using overcommit_memory to 0 is smooth so far. This needs to be further tested though.
[Galaxy S I9000 Android Development] existz:
I doubt it, as most stock kernels (actually every SGS kernel besides Talon) are no-swap systems, so i doubt this option would have much effect... But we had done some extensive testing awhile back (me and kodos), and the memory leak is either a swap issue or zram issue, or both..as the problem does not happen with zram disabled, not just disabling userspace side..ie unloading the module, but actually disabled in the kernel source, (but also since zram was disabled .., there was no swap device/page, so swap was not actually being used), so some more testing needs to be done in that area (in swap/zram source)
[Galaxy S I9000 Android Development] pikachu01:
This doesn't discount the fact that some Semaphore kernel users are also getting lagginess after a few days of uptime.

It might be the same issue or different, but testing with this option off is seemingly preventing me from getting the memory leak issue. I'll test more of this, however I need other people to test this as well. :)
[Galaxy S I9000 Android Development] KMino:
Just flashed the latest kernel... Going to test that setting out this week :) MFreak settings, noop ondemand, 40, 160, 60. No OC/UV while I test aswell..
[Galaxy S I9000 Android Development] existz:
Ok, so i want to point out something before people start flooding in with this...

With the deep sleep detection patch, when it goes into suspend it will set cpu min=100 and max=800, keeping it from going over 800mhz during suspend..then once it resumes coming out of suspend, it sets cpu min=200 and max=1ghz..and then starts back over again when it goes back into suspend with min=100 max=800mhz.. But theres a mistake made on my part with the 1.2ghz versions, since theres no 1ghz step, it just stays at 800mhz..so you may notice that coming out of sleep that it doesnt go over 800mhz...i will have a fixed version up tomorrow (1:30am here), also you may notice that it uses 200mhz more, or does not drop down to 100mhz during use.. but note that this is only while its not in suspend, once the phone goes into suspend it will drop back down to 100mhz (this isnt really that big of a deal setting 200 as min freq when screen is on), plus when UVing most of you are running about the same voltages for 100 and 200mhz.. but it will drop back down to 100 once it goes into suspend/deep sleep.. im not sure if i like this yet or not, so theres a chance i might just revert the whole patch in tomorrows release...whats your guys thoughts?
[Galaxy S I9000 Android Development] existz:
Try using "Mount Manager" instead of CIFS manager

Also, yes BLN works ... but gingerbread bln is different than froyo bln...you have to have a patched services.jar for sms to work, or it will kill the notification when screen is turned on. There was some patched ones in Neldars thread..but if your rom does not have it, u will have to patch it yourself.
[Galaxy S I9000 Android Development] zs0mby:
reset your router !
[Galaxy S I9000 Android Development] existz:
1+ ..usually if wifi cannot obtain an IP, resetting your router will fix the issue.. I have a linksys I have to reset every couple days or it errors out, reboot router and it connects fine
[Galaxy S I9000 Android Development] Ernest05:
@Up

Don't working.

I flash kernel semaphore and wifi working ;/

But I want Talon's kernel...
[Galaxy S I9000 Android Development] existz:
Not sure what the problem is, wifi has always worked fine for me (except for my linksys which i have to reset every few days, but I also have a DLink linked to it and never have a problem connecting)

woohoo 2000th post
[Galaxy S I9000 Android Development] betoNL:
I dont know cause I dont care about BLN, but there is a free app on the market - NoLed-

which is working flawlessly with any kernel and its highly configurable

It uses dots on the stanby-screen instead of led and you can configure the size, amount (of dots), behaviour etc....

«»
[Galaxy S I9000 Android Development] zacharias.maladroit:
+1

on this one

I've reset it every day in late evening

this should prevent any speed or connection issues from the router's side
[Galaxy S I9000 Android Development] betoNL:
Cheers...

Talking about wifi, I am no Linux/Android expert, but the logic says that if many users DONT have any wifi issues whatsoever (like me) this problem cannot be kernel related...

Pl correct me if I am wrong

And last question:

Does system corruption afects wifi performance?

«»
[Galaxy S I9000 Android Development] existz:
Correct, well usually the way it goes is if most users do NOT experience issues, then usually its not kernel related, or atleast its something else triggering it (either be a certain app, setting ..etc mixed with the kernel).. but it could be possible having system corruption and it causing wifi or other issues..this has been the most sensitive source ive ever seen ..the smallest thing can trigger weird issues.

But those with wifi issues, if you can get me a logcat output or kmsg after it errors out...

adb pull /proc/kmsg

Cntrl + C
[Galaxy S I9000 Android Development] tomeks:
yes

1440mhz by script in init.d

#!/system/bin/sh

echo 1440000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

only this, no change of the default governance

and i write in previous post music player lock on 800mhz

will do some more tests

sent from my GalaxyS@JVP/talon
[Galaxy S I9000 Android Development] cink40:
Maybe if the guy would red just one page back, he would get an answer...

(BLN and Noled are not the same, not even close..My wife uses Noled on sgs2, i have bln on sgs1...)
[Galaxy S I9000 Android Development] Atom960i:
@existz

amazing kernel, tried to oc up to 1.6 GHz and it was stable as AK-47 :D

The most interesting is battery life: min freq is 400 MHz, max is 1.6 GHz and the phone has eaten 0% during 9 hours sleep.

The only question is about BLN - it won't be implemented?

All in all, you've done great job
[Galaxy S I9000 Android Development] cink40:
BLN IS WORKING

(sorry i had to shout, wrote that several times already...)
[Galaxy S I9000 Android Development] hackeron:
Printscreen or it didnt happen @ 9hours with no drain.

And what rom are you using?
[Galaxy S I9000 Android Development] JarradDD:
Love it. Using on JVP with 1.2 oc. No issues.
[Galaxy S I9000 Android Development] cink40:
@existz

I have a really big problem with this kernel (and Simply GS ROM): everything works flawlessly and faaaaaast, and good battery and i am afraid that i will be forced to stop flashing (nothing to gain anymre) :)

(for people with problems: on my phone wi-fi works, BT works, BLN Works without any problem...)
[Galaxy S I9000 Android Development] Fr4gg0r:
no recovery for me with latest kernel (1.2Ghz version) :rolleyes:

wifi problem also existing here
[Galaxy S I9000 Android Development] cink40:
what do you mean, you can not go in CWM recovery (works on mine) or you can nor restore? (i did not try...) (also 1.2 version)
[Galaxy S I9000 Android Development] Fr4gg0r:
it does not go beyond the talon logo, but this also happens on normal boot now. ^^
[Galaxy S I9000 Android Development] existz:
If you don't gave a recovery, then something else is wrong...try reflashing the kernel and make sure to flash with odin/heimdall
[Galaxy S I9000 Android Development] simone201:
That's why in Talon SH i have done a command to enable/disable zram, and the module is un-loaded by default...

No memory leak so far reported

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S I9000 Android Development] existz:
The problem is still able to be reproduced even if module is unloaded,.

Me and kodos was able to reproduce it even when zram module was disabled (enabled in kernel source), but problem did not happen if actually disabled in kernel source (zram/swap is stlil compiled against the kernel and certain variables set if enabled in the source), so theres a little difference between just not loading the module and actually disabling it.. But we are still unclear if its an issue with zram itself, or actual swap support.. But just keeping it from loading the module doesnt seem to help, memory leak will happen eventually..

And honestly, the extra benefits of ZRAM/Swap is def worth having to reboot daily, so as of now removing support is highly unlikely, thats why its taking so long to narrow it down and actually fix it instead of disabling it.. But all you have to do is just disable swap and zram support in kernel source and you def wont have memory leak issues...(you will also have to re-adjust LMK settings because current ones are setup for swap and zram)
[Galaxy S I9000 Android Development] pikachu01:
I'm for the sleep detection patch, with a scaling to max as opposed to just 1GHz (as 1GHz is the max). Not sure of the code itself, but I would think that we can modify the code a bit to include what's the max frequency and make it scale there when not in suspend. (Might be confusing but I think existz would get it :P)
[Galaxy S I9000 Android Development] simone201:
Strange, very strange.....

Until now no memory leak reports about Talon SH, neither me have noticed nothing....maybe is just placebo effect!

I will take a look at it more

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S I9000 Android Development] pikachu01:
It takes a very long time to reproduce the memory leak as the VM would need to be filled to the brim (unable to release memory) and Android would need to be starved of memory (have something loaded in the foreground, or something heavy lingering in the background). Plus Android OS will need to be in a state that it finds it hard to kill anything else.
[Galaxy S I9000 Android Development] existz:
Well the 1ghz was just an example, with the 1ghz version there should be no issue of it not jumping back up to max clock coming out of suspend, only 1.2ghz version should have this issue..since theres no 1ghz step in 1.2ghz version, when it checks to scale back up to 1ghz and its not there, it just stays at 800...which as i mentioned, this is an easy fix for the 1.2ghz, so it will basically do the same thing you wanted..with 1ghz version when it comes out of suspend it sets max clock back to 1ghz, then with 1.2ghz version it sets it to 1.2ghz (will be fixed in tomorrows release)..so it will set it based on what max clock is
[Galaxy S I9000 Android Development] flolep:
I'll for sure test it. Thanks to you and existz for these good discussions that can only help things go further...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pikachu01:
Wouldn't this increase the effort of maintaining two code bases for two different versions?
[Galaxy S I9000 Android Development] existz:
No, i actually have it defined in /arch/arm/mach-s5pv210/include/mach/voltages.h and can set it to define the new_policy.max...

For example, in voltage.h it defines TOPCPUFREQUENCY depending on which version is selected in Talon Menu Settings...so if 1.2ghz version is selected, it sets TOPCPUFREQUENCY 1200000, or if 1ghz version is selected it sets TOPCPUFREQUENCY 1000000... so in the the deep sleep detection code for when it resumes, I can just set new_policy.max=TOPCPUFREQUENCY ....that way depending on which version is set during compile, it sets the max policy based on it.., so it would be the exact same process when compiling 1ghz version or 1.2ghz version...

But the only problem with this is, if someone is oc'ing higher than whatever the max clock is for that version, for example they use tegrak oc app to oc to 1.3ghz with the 1.2ghz version, then this same problem is going to happen only for them...so anything other than what the kernel is set to will introduce problems.. Which ill try to figure out a way to set new_policy.max depending on scaling max freq... But ill probably revert the whole patch in the next release atleast until i can figure out a good solid way to do this, that way with future version of Talon and its oc module, we wont run back into this (if i decide to even keep the patch)..that way it just sets the new_policy.max depending on what the highest scaling frequency is, instead of a set frequency, so if max clock changes then so will it
[Galaxy S I9000 Android Development] mab71:
Errrrr.... Who am i, where am i??? LOL... just kidding guys...keep up the good work!!! you guys rock!!
[Galaxy S I9000 Android Development] pikachu01:
Cool :) Looking forward to the OC module with the sleep detection patch!
[Galaxy S I9000 Android Development] existz:
But like i mentioned, ill probably just revert the whole thing in next release, and depending on the reports of setting overcommit_memory to 0, if it clears things up then ill go ahead and set it 0 by default in the kernel..that way all the major stuff is out of the way and i can start on the oc module without having to worry about something new popping up :)
[Galaxy S I9000 Android Development] pikachu01:
I would prefer to have the sleep code though (it's more thought out well than OndemandX's). And it's faster to wake (OndemandX is slower to wake when getting a call)
[Galaxy S I9000 Android Development] Mangus_U*RA:
Could you provide even bigmem version? thanks! :)
[Galaxy S I9000 Android Development] simone201:
+1 for this

Looking forward to implementing the sleep code in a better way....

I will try something today as i have time, as i have some good ideas now!

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S I9000 Android Development] rodirodi:
+1 Existz please keep sleep code. I had sound stuttering problems before (with 100Mhz). And I'm not expecting real side effect on battery life when screen is on (100 and 200 Mhz both have low and pretty same UV values) .

"Must have" feature!
[Galaxy S I9000 Android Development] Tatsuya79:
No sorry, there will be a new version soon if you follow what Existz said.

I can confirm the 800mHz bug on the 1200 version.

Smartass was slower/same as ondemand from my experience.

I had CWM rebooting my phone while trying to flash back 0.5.1.3, I did it again without issue on the second try. Strange.
[Galaxy S I9000 Android Development] mucinch:
I came across these in the Nexus S thread, is it possible to implement some of these for SGS?

http://xdaforums.com/showthread.php?t=1276092

http://xdaforums.com/showthread.php?t=1288015

http://xdaforums.com/showthread.php?t=1036996

Is 880mHz a good compromise for people worrying about battery life? or do we need to increase the bus speed as specified in the thread for it to be effective? I apologize for my noobiness in advance!:D