yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
Slim comes with inline build of Semaphore. Did you flash again Semaphore?

If yes, please try to delete ansi_kprng.ko file in /system/lib/modules and reboot.
[Galaxy S I9000 Android Development] RivalComp:
Of course I did the kernel flash. I did what you've said. Everything is working now. Thank you! :thumbup: :beer:
[Galaxy S I9000 Android Development] stratosk:
Inline kernel of Slim and Semaphore is the same code. But due to different magic number in modules (version), they can't be loaded.

I will implement a different way to check if Semaphore is installed and update the modules.
[Galaxy S I9000 Android Development] RivalComp:
Modules' date were 2008, now they are 2012. :eek: Now I know the magic, next time I will know what to do... :) Thanks again.
[Galaxy S I9000 Android Development] cha-ka-lak:
Bluetooth DUP profile

I fail while trying to use my SGS as a modem by utilizing the DUN bluetooth profile. According to Samsung, DUN is part of the phone's original technical specifications. I'm currently on SlimBean 2.9 including Semaphone 2.5.0s.

Is this a kernel issue? Anyone got this working?

Thanks in advance.

(Sorry if this question has been asked before. I could not find any threads by searching.)

Edit 2012/11/08 - The profile is called DUN (not DUP). I found an app that solves my issue by emulating the DUN profile ("BlueDUN" in Android store). :)
[Galaxy S I9000 Android Development] jugster:
Slimbean is not made by samsung. Don't take anything for granted.

/J

Signature? Signature!
[Galaxy S I9000 Android Development] cha-ka-lak:
I'm certainly aware of this.

But I suppose bluetooth profile support are a kernel issue - that's why I'm raising this question in this thread and not in the Slimbean one.

I referred to the Samsung specs only to clarify that the hardware is capable of the DUP profile.
[Galaxy S I9000 Android Development] everlethal:
Hi people

I saw radio fm modul in semaphore app.

What's this?

Can i listen Fm Radio if i enable this or it's something else ?
[Galaxy S I9000 Android Development] Starsream88:
Enable it in semaphore manager and then install an app for that (Spirit Fm as exemple)
[Galaxy S I9000 Android Development] everlethal:
Thanks mate,

I already have Spirit FM installed and it's working without enable this modul. That's why i was wondering.

So should i enable it or it doesn't matter if it working ?
[Galaxy S I9000 Android Development] superkoal:
Was answered by stratosk a few pages back (and probably about 100 times in the history of semaphore):

Yes it's the radio FM module. And no, you don't have to enable it, because SpiritFM loads the module itself.
[Galaxy S I9000 Android Development] bitblaster:
Yes Stratosk, it happens to me too with touchwake and "end_call_on_power_button" activated.

Just try this:

place (or receive) a call. Wait till the display turns off by its timeout (during the call). Then touch the screen... The call drops.

Let me explain my theory.

But to be clear in this and in the next messages, let's define the 2 proximity sensor's power states: PROX_ON and PROX_OFF.

Then, when PROX_ON, the sensor can be in 2 sensing states: PROX_NEAR and PROX_FAR.

It seems we have such a faulty behaviour because the kernel disables touchwake when PROX_ON. So, when the screen goes off by its own timeout, the sensor will be powered down (PROX_OFF) and the kernel re-enables touchwake.

I think there is not a simple way to solve this unless you're able to intercept the start and the end of a call at the kernel level.

However there could be a tricky way:

1) Disable touchwake on PROX_ON, just like you do now.

2) If PROX_OFF while display is off AND touchwake is off, don't enable touchwake (THIS IS THE MOST IMPORTANT POINT!)

3) If PROX_OFF while display is on AND touchwake is off, enable touchwake, just like you do now (normal call ending)

4) If display turns on while PROX_OFF (the normal behaviour at the end of a call and during normal phone usage), just ensure that touchwake is on.

The last point could be a problem from the performance point of view, as it will be executed always, even when not after a call (since we don't know when a call ends).

Also note that during a call while PROX_NEAR, the display switches off but the sensor power remains PROX_ON (obviously).
[Galaxy S I9000 Android Development] Starsream88:
Same issu for me, i flashed semaphore 2.5s but governor and io scheduler dont stick. Searched the file you mentioned but can't find it :confused:

Any help stratos please ? Thank you

Edit : issu solved, didn't find ansi_kprng.ko, found another one ansi_cprng.ko and i deleted it, reboot and it's working again :)
[Galaxy S I9000 Android Development] Toldo:
I was wondering if it is possible to add the ablitity to show battery current (in mV) in compatible apps (like Current Widget)? I know it's kernel stuff because I had the same problem on Galaxy Tab and it was resolved in the kernel.
[Galaxy S I9000 Android Development] stratosk:
The problem is that I can't reproduce the issue. It happened to me a couple of times.

I guess it's timing issue. I have to check again.

BTW, I disable touchwake when PROX_NEAR (and of course PROX_ON).

Anyway, thanks for your feedback.

Can you point to a commit or at least the kernel? Maybe, I can check it.
[Galaxy S I9000 Android Development] adytum:
Not sure if I understand you correctly, but that works fine with the widget of the app galaxy nexus fast charge from market. Gets you fast charge toggle too!

Sent from horseback.
[Galaxy S I9000 Android Development] Toldo:
Here's the github but I don't know which commit it is (but I will find out if you won't find it):

https://github.com/ryrzy/p75xx_ICS
[Galaxy S I9000 Android Development] tusko5:
Like you, I was concerned about smoothness, but after some days working with a big swapfile (512MB, overkill, it only uses around 128MB right now) in a SD class 6 card, I can say that no smoothness is lost.
[Galaxy S I9000 Android Development] stratosk:
I can't find any commit related with this.

Maybe this kernel's driver just support this feature.
[Galaxy S I9000 Android Development] Toldo:
Ryrzy is my good friend. I asked him which one is it and as soon as he replies me, I'll provide it to you.
[Galaxy S I9000 Android Development] superkoal:
Current would be amps then...
[Galaxy S I9000 Android Development] Brignoud:
Endless Bootloop Experienced this afternoon

These are the steps I followed

Rebooting Recovery

Cleared Cache

Cleared Dalvik (2 times!!)

Occasionally runned Aroma

Reboot and recovery lost (stuck on semaphore log for some time before rebooted)

Same solution as otherwise reported:flashed Devil (latest 1.81) via Odin and recovery recovered.

Reflashed Semaphore via recovery(!)
[Galaxy S I9000 Android Development] everlethal:
Same thing, same solution.
[Galaxy S I9000 Android Development] NDeaz:
Hey, why when I turn on swap command

swapon / dev/block/mmcblk1p2, terminal

writes an error "swapon / dev/block/

mmcblk1p2: function not implemented"?

Thanks.
[Galaxy S I9000 Android Development] saszseb:
Do you use "2.5.0ts" version?
[Galaxy S I9000 Android Development] NDeaz:
By the way, can somehow increase the multiplier overclocking?

Previously used 1200mHz + 114% liveoc (1368mHz)

Everything was great.
[Galaxy S I9000 Android Development] Jens1969:
Does anyone know, how to read/print/get the actual voltage the the kernel is running with (in real-time)?
[Galaxy S I9000 Android Development] Toldo:
I'm on SlimBean 2.9 with 2.5.0s, and I had no problem for two days (discharging cycle) but after charging now the phone mostly doesn't go into deep idle (only for couple of ms). What's more, phone sometimes reboots to recovery by itsself. I didn't install anything new, so it looks like it happened after charging (lol).

//And on the previous case with the battery current, it is (somewhere) inside the following commit: https://github.com/ryrzy/p75xx_ICS/commit/082d0d46703ed4c3c78252d017478bca28d612c8
[Galaxy S I9000 Android Development] loserrahul:
could not thank enough in the past to stratosk...

today 8 thanks for u ...

thanx for this awesome masterpiece kernel..

no complain at all...
[Galaxy S I9000 Android Development] AndroidBR:
Stratos my friend! How's it going?

Man, I just can't find Semaphore's manager on today's CM10...

I've flashed Semaphore twice and still can't find it... :(
[Galaxy S I9000 Android Development] Midomad:
Install it from play store!

Regards

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] Brignoud:
Suddenly I've lost USB mode

Tried restoring, debug info to see what's happen but everithing I have nothing obteied but the notification message and still no USB mode to connect to PC
[Galaxy S I9000 Android Development] AndroidBR:
Wow, that's different! Thanks for the reply. But is this how we're supposed to control the kernel now? Shouldn't it be part of the kernel .zip file (with the manager app included) like it was in the past?
[Galaxy S I9000 Android Development] Gvdn:
No
[Galaxy S I9000 Android Development] stratosk:
Thanks for feedback.

I will try to reproduce it.

No, only LiveOC is supported by Semaphore (100-120%)

If you don't want to use an app, please run this on a terminal emulator:

cat /sys/devices/virtual/misc/customvoltage/arm_volt.

In next version of Semaphore Manager you will be able to see and change the voltages.

Thanks so much my friend. :)
[Galaxy S I9000 Android Development] Brignoud:
Please, how to reactivate USB connection to PC?

Notification drawer no more show it even after unpluging and pluging cable.

_____________

Ok, I got it.

Reset to normal view (I was in tablet UI mode) and removed theme(probably not relevant) reset to normal.

I'm on Slim
[Galaxy S I9000 Android Development] mindphaser2k9:
Most probably that is the ROM problem. Reflash your ROM.
[Galaxy S I9000 Android Development] Jacktheskipper:
CM10 sometimes has this problem for me, the solution has always been (really!) to pull the battery out while phone was running ... on next boot it worked again like a charm!
[Galaxy S I9000 Android Development] Toldo:
It's getting on my nerves a bit. Since today the phone keeps not getting into deep idle. I tried reflashing kernel, reflashing rom, wiping Semaphore manager settings, wiping init.d and also cache and dalvik cache. I checked better battery stats for any suspicious app but found nothing. I had two day running with no issue and now this stuff. I didn't make a full wipe though because I didn't have time. Everything that I did was flashing SlimBean 2.8 from stock - still no issue, then in the mean time I flashed the 2.9 with newer kernel version - still no issue for two days (one battery cycle). Then I charged, and after another day it started... Sorry for so long feedback but I had to lay out some anger that I collected while trying to figure it out.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] AusMatt:
I'm now using a 512MB swap partition on my external micro SD card and am finding it great. I'm very keen to see swap continue as a feature of Semaphore as that's the way we can keep this capable device running for even longer.

Stratosk had mentioned that kswapd would be running for any swap enabled kernel and he saw this as an overhead. I would have thought that there should be no need to start kswapd until a swap partition is actually enabled with the swapon command. Maybe this would also require some kernel change.

If I un-mount my external micro SD card things will go badly unless swapoff is run first. Does this happen automatically or will I have to manually run the swapoff command before un-mounting ? I suppose it's the ROM and not the kernel that would need to automatically handle this.

I'll write an init.d script to swapon soon as I don't want a full blown app for this simple task.

Loving CM10 and Semaphore 2.5 even more now.
[Galaxy S I9000 Android Development] rmsinaga:
Hi stratosk,

Out of curiosity, how did you define the default tweak values in all governors in your kernel? Did you make some tests before? If not, what’s the basis?

Thank you.
[Galaxy S I9000 Android Development] NDeaz:
And it will remain so, or plans to do as before?

Sorry for my english ...
[Galaxy S I9000 Android Development] superkoal:
1) install Better Battery stats

2) See if your phone enters deep sleep

3) disable deep idle and check again

4) start debugging by finding out what the options in better battery stats mean.

(there are several nice xda threads for this, don't ask here)

It's probably an app you installed, maybe a sync problem with gapps.
[Galaxy S I9000 Android Development] Toldo:
I did all that and found nothing. Phone goes into deep sleep but no deep idle. Statistics show only idle mode, no top on nor top off. And I have sync turned off, as well as any connection (I preferably use wifi when needed). After erasing Semaphore Manager settings and setting up again deep idle works for some time.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] Al3cks:
I also tried a 512MB swap partition on a Class 10 16GB SanDisk SD. Performance was better compared to when I tried this on a Calss 4 SD, but the problem was that sometimes I was having issues with the phone slowly waking up. I was pressing the power button, and the screen came on after 5 to 10 seconds, making me think that it entered in a SoD state. It's great to do all that multi tasking (5-10 tabs open in browser, Play Store, file browser, Gmail, Maps, SMS, Currents and so on) but you don't need this all the time. Plus the SD card gets worn out relatively quickly.

I've done some searching around and found a forum where some guys tested multiple Class 10 16GB SanDisks by doing continuous read/write operations in a very comprehensive way (checking data integrity at each cycle) and the cards started showing data corruption after only 1 and a half months. It may not be the case with swap, but this was just to show how fragile these cards are when it comes to continuous operation (which is what happens with swap).

Plus, swap starts to suffer from fragmentation, as data is written sequentially where it finds space, like a HDD, when you delete data, it starts writing in the gaps found, and this degrades performance over time; a restart, or swapoff -a, swapon -a command refreshes this, but still...

Anyway, I settled for 26% zRAM instead, and it may have a hiccup here and there, but it's more stable. So my opinion on these extended RAM options is that they should be provided as modules for the user to enable via script or Semaphore App. It's the best way to de-bloat the kernel and I thank you Stratos for this ideea :).
[Galaxy S I9000 Android Development] superkoal:
Deep Idle is known to be not 100 percent stable, stratosk said himself that he's not giving any guarantee for it working correctly.

Also it's potential to really save energy is not proven, there's even a thread where somebody did measurements that prove it doesn't save anything.

So as long as your phone goes into deep sleep you're perfectly fine if you just disable deep idle...
[Galaxy S I9000 Android Development] saszseb:
No prob here. I've done some backups on different ROMs then did a restore and never had any of bootloops.
[Galaxy S I9000 Android Development] stratosk:
Hi,

In ondemand, yes. I tested it extensively. I also introduced a new tunable (momentum).

In other governors I left the default values unchanged.
[Galaxy S I9000 Android Development] NightmareCC:
I changed my ondemand values to get more performance (hopefully).

My values now look as follow:

Sampling down factor - 2

Sampling rate - 20000

Up threshold - 70

Sampling down max momentum - 16

I'm using this with smooth ui without oc and noop scheduler.

My rom is slimbean. I run this setting for about an hour and it looks promising but I think battery life will be pretty bad.

SwiftKeyed in Tapatalk from a slim SGS
[Galaxy S I9000 Android Development] stratosk:
Actually the changes are in sampling down factor and up threshold.

sampling down factor from 4 to 2. Maybe, a little bit better battery.

Sampling down factor determine the time that the CPU will remain in max frequency. factor 4 means that it will stay 20000 * 4 = 80000us = 0.08sec.

factor 2 means that it will remain for 0.04s before ondemand samples again for CPU load.

Up threshold from 85 to 70. More aggressive value. Snappier phone. Worse battery.
[Galaxy S I9000 Android Development] NightmareCC:
There is a great thread explaining all the values and there effects to the phone http://xdaforums.com/showthread.php?t=1369817

For all of you guys who wondering how to configure your kernel settings!

SwiftKeyed in Tapatalk from a slim SGS
[Galaxy S I9000 Android Development] nyloncrack:
My backups work fine. No bootloops here.
[Galaxy S I9000 Android Development] karol1981:
+1 every time when i go to recovery and trying reboot system now i had a bootloop, phone try start ,3 loop and back to recovery ,reboot system now-> starting normally.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] AusMatt:
I've cut it back now to 256MB as it only got up to about 170MB usage with my common app usage.

I've got a Sandisk 32GB (class 6 I think). It would be interesting to know if anyone has actually worn out an SD card with swap.
[Galaxy S I9000 Android Development] RivalComp:
Current technology allows 100 000 write cycles. Hundred thousand. Let's count it on a 32 GB SD card. Ok, worst case scenario, let it be only 1 000 write cycles: you can write 1 000 x 32 GB on the card. This means 32 000 GB of data. This means you have to write all 32 GB of data every day to wear it out in 2,7 years. But you have to write 32 GB data _every day_!

SD card's controller spreads data on the whole surface to not wearing out one spot. My wife's dad has a 512 MB card for about 10 years now. He's a photographer and he uses this card in his camera day to day. No problem with the card to this time.

I don't understand when someone worrying about SD card's lifetime.

And it's getting cheaper and cheaper. How much did an i9000 cost? How much does a new SD card cost?

This is my opinion... :)
[Galaxy S I9000 Android Development] elhennig:
I don't either.

At the end of the day it would still be a good excuse to get a new, bigger and faster replacement. Unfortunately it never will get that far because of wearing down the card.
[Galaxy S I9000 Android Development] sUsH667:
i use the same sdcard WITH swap nearly since i got my i9000 (or better: since swap is somehow available for that device) and NEVER had any negative results with it til today.

from time to time i use this same sdcard with an sdcard-reader for running an os or for watching movies from it, and doing that i also never realized ANY negative results that may have been rooted in swap-usage.

and btw, best argument is really the price of an sdcard nowadays.

with 16gb cards starting at around 10 dollars, it isn't even worth the discussion, even if it would really wear the sdcard down in relevant time.

just my thoughts though...

greetz,

sUsH
[Galaxy S I9000 Android Development] Downloadaholik:
this kernel is great using it with x-bean 3.0 its a match made in heave

but the problem is when i try to set the OC to 120%, apps keeps crashing and sometimes the phone reboots into recovery ??

the thing is before they crash the run extra smooth (games and such)

when i turn it down to say 110% its ok but sometimes the apps lags and if i want to avoid that i need to start the apps after reboot
[Galaxy S I9000 Android Development] thETImo:
The Dev Himself has recommended the OC to be kept in 114% somewhere inside this thread. And with me, it seems to be the best choice too. :good:
[Galaxy S I9000 Android Development] 99x:
Hi Stratosk, thanks for your hard work, one question regarding the voltages and Live OC, will we be able to use Live OC and undervolt L0 and L1 frequency steps? My device is capable of lower volts while OC, but currently the kernel automatically sets default volts when Live OC is applied. :good:
[Galaxy S I9000 Android Development] superkoal:
Seriously? :banghead:
[Galaxy S I9000 Android Development] Al3cks:
That's what info I found on the internet, but since you said you are using it for a long time the I'll keep testing. How long anyway?

What size is your swap partition, what swappiness value are you using.

Thanks.
[Galaxy S I9000 Android Development] test123456789012:
Hi Stratosk,

I just wanted to report that 2.5.0ts is really, really stable now, having changed OC to 114. :) ZRAM seems to bring no real advantages for me as a light user (mainly texts, whatsapp, browsing). My phone closes big apps like chrome anyway. But the kernel is so smooth, stable and fast! Did you change anything else compared to 2.5.0s? Well, I hope you will keep the option to enable swap/ZRAM for those who apparently can't live without it. I certainly can. Regards!
[Galaxy S I9000 Android Development] erpurohit:
seem I am missing something here....where is the link to ts version....
[Galaxy S I9000 Android Development] stratospr:
Here you go: http://xdaforums.com/showpost.php?p=33478042&postcount=2731
[Galaxy S I9000 Android Development] Toldo:
Strange report on my no-deep-idle issue: fully wiped, installed all my apps (that I had before) and flashed 2.5.0 version (with no s). Sleeps (deep idles) like a baby now.
[Galaxy S I9000 Android Development] stratosk:
Yes, we will be able to use custom voltage for every frequency.
[Galaxy S I9000 Android Development] AlexandreT:
My phone is also very stable with Swap activated, not any slower at all. What I am seeing is that, like you, big apps keep getting closed despite having plenty of space to keep them in Swap. Is there anything I can do to prevent this or is this just how Android works with Swap?
[Galaxy S I9000 Android Development] AusMatt:
As stated before, I'm now using a 256MB swap partition which seems to me more than enough.

Overall the phone is much faster and smoother than before as it's really noticeable that I'm smoothly switching between apps and I no longer get the delay when the launcher has to restart after a game when I press the home key.

I haven't yet seen the big app closing thing. Can you give some examples ?

I think I should get a couple more I9000 while they are still around cheap on eBay (about $60 - $90) as it's now a great little phone.

Thanks to Pawtip and Stratosk for a job well done.

Please keep swap as a permanent feature (I do not care for ZRAM).

P.S. I'm using Semaphore 2.5.0t version.
[Galaxy S I9000 Android Development] stratosk:
Hello,

I'm reading the changelog and I can't find a noticeable related change about your first issue. Is it possible to get a logcat?

About the second issue, you could try to decrease BT volume from in-call volume settings (Settings->Advanced->In call volume controls).
[Galaxy S I9000 Android Development] shiyou:
why do i always get bootloop when i decide to wipe cache and dalvik?
[Galaxy S I9000 Android Development] stratosk:
I wish I could reproduce bootloop issue. Maybe, I could resolve it.
[Galaxy S I9000 Android Development] kernelfreak:
i have also cm10, and i don't have this behaviour...
[Galaxy S I9000 Android Development] hansare:
Why is the CWM-recovery subscreen "choose backup format" almost the same as the former screen "backup and restore"?
[Galaxy S I9000 Android Development] Ledanur:
If I apply a liveOC value, do I need to adjust the tune-ables in the governors?

I increased the liveOC to 117% and I'm using SmartAssV2, do I need change the governor in any way for it to apply to the current frequency levels?
[Galaxy S I9000 Android Development] AlexandreT:
I notice it with Arcane Empires, it takes about 90-100mb of memory. Without Swap I always have to restart the game to enter it. With Swap, most times I can reenter the game from memory, which is much faster than fully booting the game but sometimes even with Swap the game gets closed by the system, despite still having free Swap memory.