yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] galaxy1039:
Tethering issue

Hi, I'm having WiFi and Bluetooth tethering issues with SlimRom/Semaphore3.0.0 ROM.

Could anybody confirm if Semaphore TUN module is required for WiFi and/or BT tethering to work properly??

The issue is that tethering sometimes work, sometimes doesn't. What it always happens is that I loose Internet access in the mobile after using tethering. If anybody has any idea why this work, please share.

Thanks!
[Galaxy S I9000 Android Development] bialabs:
hello Stratosk is possible that the phone is more responsive with 's' version, hugemem patch and bigmem disabled (397mb ram) and not with s version, hugemem patch and bigmem enabled (409mb)?

Is only my feeling? Thank you
[Galaxy S I9000 Android Development] :
just installed last version! Stable as never, i'm happy! I'm searching for a nexus 4 :D
[Galaxy S I9000 Android Development] gajahwhite:
is it ok if put semaphore manager app in greenify list?
[Galaxy S I9000 Android Development] khankk42:
put it nothing will happen
[Galaxy S I9000 Android Development] stratosk:
I really don't know.

I think that you should not feel any difference between them, in normal operation.

Bigmem just reserves less memory for video driver to be used for recording. So I don't think that will make any difference in smoothness.
[Galaxy S I9000 Android Development] s30ckf:
New version of Semaphore Manager is released, thanks Stratosk.
[Galaxy S I9000 Android Development] iulian vu:
After each reebot ,I/o is going back to noop. How can I keep Row ?I,m using Semaphore Manager.If I'm using Ns Tools, I can,t Set Governor.
[Galaxy S I9000 Android Development] mamoto66:
Semaphore manager,selected "Apply on Boot"may be the solution.
[Galaxy S I9000 Android Development] stratosk:
I will check it. Maybe it's a bug in Semaphore Manager
[Galaxy S I9000 Android Development] gajahwhite:
no prob with mine.. but i dont use Ns Tools...
[Galaxy S I9000 Android Development] Abyv:
Thanks to you stratosk for all the kernels you gave us. I sold my device today and hope to see you in another section. Thanks again.
[Galaxy S I9000 Android Development] stratosk:
Thank you my friend! I hope you to enjoy your new device!

Thanks for your support!
[Galaxy S I9000 Android Development] CatalystWon:
We like the version change and just consumed 1,000 copies:p. For sure we will consume more when 4.0.0 arrives :p:p !
[Galaxy S I9000 Android Development] tsatomas:
For nstools you must fix its permissions. Use the app fix permissions.(or maybe from recovery fix).
[Galaxy S I9000 Android Development] KSLevel11:
[MENTION=3750240]stratosk[/MENTION]

It is possible that reduced number of framebuffers causes less smoother UI? Because I feel that with stock cm10.1 kernel, UI is smoother than with semaphore. Especially visible in app drawer.

Greetings

Wysłane z mojego GT-I9000 za pomocą Tapatalk 4
[Galaxy S I9000 Android Development] stratosk:
I really don't know. I have to check it.
[Galaxy S I9000 Android Development] KSLevel11:
And please let us know, thanks.

Wysłane z mojego GT-I9000 za pomocą Tapatalk 4
[Galaxy S I9000 Android Development] s3icc0:
Any chance of support for the upcomming nexus 5?
[Galaxy S I9000 Android Development] juliatan:
Difference battery time CM- and Semaphore-kernel?

I have been using CM 10.1.2 for more than a week now. Although the rom works smooth and stable, I am not very happy about the batterytime while using the phone with its original kernel. The same problem I had with CM 10.0 stable until I changed to Semaphore kernel. Batterytime became a lot better then.

That's why I wonder if same as CM 10.0 batterytime gets better with CM 10.1.x stable after changing to Semaphore?

Why I first ask instead of just trying? With Titanium restores causing hard and soft reboots with CM's based on Android 4.2.x these days experimenting, changing rom, etc. gets to time consuming when having to install all apps and setting them up all over again. Or perhaps someone knows where to download the original kernel of CM 10.1.x stable in case wanting to go back without starting from scratch. Although with the experience of CM 10.0 and the much better performance with Semaphore back then, that probably will not be neccesary.

Thanks for the great work
[Galaxy S I9000 Android Development] AusMatt:
Its best to only restore data with TB. Google can restore your set of apps without much intervention. Its probably best to test with a limited set of apps anyway.

As for the CM10.1.x kernel... The best option is to just reflash the ROM to get it back. You don't have to wipe your sdcard (and hence apps).
[Galaxy S I9000 Android Development] Opuz Klass:
Please delete!

Thanks!

Sent from my GT-I9000
[Galaxy S I9000 Android Development] weazie:
Hi Stratosk,

Maybe this had been asked before, but how to enable kernel samepage merging? Is it implemented?

Thank you for your answer,

weazie
[Galaxy S I9000 Android Development] YouRQXXL:
Forget it :(
[Galaxy S I9000 Android Development] stratosk:
The only link to kernel source that I can find is one to my sources.

So, I can't be sure if the dev changed something.

If he didn't change anything then MMS issue is not kernel related (?)
[Galaxy S I9000 Android Development] grinder777:
Ask him what if did... would be nice to know :)

SGS - Devil 4.2 - Black Beast - Cobalt Sam-X - Thnx2all
[Galaxy S I9000 Android Development] dark_knight35:
This doesn't make sense to me. On a bunch of ROMs it works with a few kernels and doesn't with the others, and now on one ROM it works with a kernel with which it didn't work on other ROMs and just because of that you claim it to be a ROM issue. I wonder that you didn't notice yourself that you're talking nonsense :p.

Little side note: Cyan, Lantrop and Gear are based on Semaphore...
[Galaxy S I9000 Android Development] ts1506:
Well, correction. Latrop is based on CM kernel. So, if it has the issue too, Semaphore base is not to be blamed.
[Galaxy S I9000 Android Development] YouRQXXL:
Forget of all i wrote.

I was wrong, sad but true :(
[Galaxy S I9000 Android Development] juliatan:
Thanks for response

So if only flash(same) rom apps are still there and working? No wiping dalvik or cache needed? Hope these questions are not too silly.

Probably it won't be necessary. Battery live with original CM-kernel is too bad in comparence with the past CM and Slim Bean with Semaphore. Sleep mode is oké (1 percent after 8 hours sleep). But while using ridiculously fast and phone almost always hot. During workout earlier 45 minutes of music from around 90 to low 30 percent. Have to bring loader to work since CM 10.1.2. (CM 10.0 had same problem before Semaphore)

Kind regards
[Galaxy S I9000 Android Development] AusMatt:
Flashing ROM does not affect apps. I've been running nightlys for months without wipe or davlik wipe. The last time I full wiped was early in CM10.0 (I.e. I didn't full wipe when going from 10.0 to 10.1).

There are several possible reasons for heat and hence power drain. One is bad reception on mobile signal. Another is apps keeping phone awake due to activity (checking things to notify you). If you're seeing differences with just kernel change but same apps, then test with a few kernels and different governors and schedulers.
[Galaxy S I9000 Android Development] s3icc0:
Hey me neither :) I did full wipe before flashing CM10 but going from CM10 to CM 10.1 without any wipe. Wiping is for cowards :) Sometimes I am thinking I will wipe the device to get more speed for few weeks - but I will wipe with official CM10.2 :)
[Galaxy S I9000 Android Development] ElmirBuljubasic:
Wiping is for cowards? People wipe becouse they want to be without bugs in new rom.
[Galaxy S I9000 Android Development] alcurtis93:
Me too cm10 with semaphore and ram manager on balanced setting makes my s1 quicker than my girlfriends s3 on cm9 8)
[Galaxy S I9000 Android Development] groksteady:
Anyone having strange behavior on the powered-off charging animation? I saw in the changelog for 2.0.6 that it should be working. For me, it does initially. From powered off, a blank/gray battery blinks once, and then goes into the usual battery with some amount of green. But after the screen goes off, clicking home or power or volume won't bring it back. I also can't boot the phone while plugged in. Wondering if it's me, and I should reflash. This is on CM10 20120820.

And thanks Stratosk -- great work, again. All my usual options are working great.
[Galaxy S I9000 Android Development] vega1979:
Hi Stratosk,

I tried to install the new kernel on slimbean 2.0.1 via recovery (using the zip file) but after I installed the kernel 2.0.6 I got stuck on the boot with the logo....I also tried by using Odin but the result is the same. It does not boot. I had to reinstall 2.0.3 to have the phone booting. Is this kernel supposed to work also with slim bean 2.0.1?

Did this happen only to me?

Cheers,
[Galaxy S I9000 Android Development] jacobuscuracao:
being faster than your girlfriend is not always better ...
[Galaxy S I9000 Android Development] fatino:
I had some problems with Devil kernel, some reboots wierd stuff so Im back with Semaphore. I miss one thing. Could you please add stronger wifi support like on Devil kernel? On Semaphore it acts like powersave. On Devil I get better reception.
[Galaxy S I9000 Android Development] jacobuscuracao:
ok maybe this is a weird question (to you) BUT why would you power off your phone? Isn't that like ... dying a little bit inside?
[Galaxy S I9000 Android Development] groksteady:
hah -- it's not a regular occurrence. it just happened that i ran the battery to zero because i was too lazy to fish out the charger from my bag. i let it sit powered-off and charging a while, and then noticed it.
[Galaxy S I9000 Android Development] downhere:
Just read one page before - there is your answer :)
[Galaxy S I9000 Android Development] DerTeufel1980:
I have noticed the same on my new kernel. I guess it is the lpm "fix" from cm team, cause it was working before.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] jeozme:
haha, dude you are on the wrong rom :eek:

Sent from my phone.
[Galaxy S I9000 Android Development] philidor:
Nightly with 2.0.6s... cm nightly work with big memory ?
[Galaxy S I9000 Android Development] cink40:
Yes, but should be patched. search this thread for zip.

Tapatalked
[Galaxy S I9000 Android Development] jv.batista:
going to try the 2.0.6s in cm10. lets see how it goes...
[Galaxy S I9000 Android Development] JJustin:
Which patch are you guys using? Is it this one? http://xdaforums.com/showthread.php?t=1815849

I am on CM10, 820 nightly, 2.0.6s, and patched with above, and cannot get my 720p videos to play. :(
[Galaxy S I9000 Android Development] slaj76:
Try 21 page of this thread.
[Galaxy S I9000 Android Development] kathees:
stratosk,

Can you help me explain new CM10 partition layout?
[Galaxy S I9000 Android Development] alcurtis93:
Very true mate ;)
[Galaxy S I9000 Android Development] stratosk:
I'm not sure that this is the reason. I think I had this issue before.
[Galaxy S I9000 Android Development] thestudent00:
Just search the cm10 thread pawitp explains there already. If u doesnt understand there than ask again. System and Data have been swaped to gain more speed, cause now data is on the faster but smaller nand.
[Galaxy S I9000 Android Development] abellimz:
Wow semaphore 2.0.6 is really very fast :thumbup:

Sent from my GT-I9000
[Galaxy S I9000 Android Development] jugster:
[MENTION=3750240]stratosk[/MENTION]

New linaro tool chain released.

Signature? Signature!
[Galaxy S I9000 Android Development] fishears:
Its like washing your hands after you use the toilet: You don't have to, but its cleaner if you do ;)

sent from somewhere..
[Galaxy S I9000 Android Development] s3icc0:
The cowards thing ... it was kind of a joke :) so don't get rude :)
[Galaxy S I9000 Android Development] vankd:
Has someone the fix to record / reproduce in 720p with bigmem activated for this kernel in cm10.1.2?

Sorry for my bad english.

Thx
[Galaxy S I9000 Android Development] stratosk:
There is no fix. With bigmem enabled you can't record 720p. This was made in purpose for more available memory.
[Galaxy S I9000 Android Development] everb00b:
I'm facing a slight issue.

While using Ondemand + ROW and Lock Min Freq 100Mhz.

Issue: screen-off, If i get a call it freezes the phone a the sound.

Currently using Ondemand + Noop and no lock, runs good.
[Galaxy S I9000 Android Development] juliatan:
CM 10.1.2 much better now with Semaphore

After flashing latest Semaphore kernel to my CM 10.1.2 rom, battery time is certainly better and phone also seems to get less often and less hot.

I had one littlle issue streaming music with ArmAmp from my Nas in lockscreen mode, but that was solved with enabling Wifi PM Fast via Semaphore Manager and now audio is not freezing but stable again when screen goes off.

Same as CM 10.0, using CM 10.1.x in my case only gets acceptable when using Semaphore kernel! Still moving to Slim Bean with Semaphore included standardly when its next stable (4.2.2) arrives.

Thanks again!
[Galaxy S I9000 Android Development] 1Ishara:
Hi i love this kernel but also i miss the twrp recovery on mckey kernel. So my problem is can i backup mckey kernel recovery and restore it to this kernel?? Or if cant is there any way to use twrp with this recovery??:)

Thanks:)

Sent from my GT-I9000
[Galaxy S I9000 Android Development] yfriday14:
Proximity sensor disable option?

Several of us have proximity sensor broken, which makes the phone impossible to be used for calling (broken proximity sensor freezes the phone for 32 seconds while calling).

Could be possible to add an option to disable just the Proximity sensor in kernel?
[Galaxy S I9000 Android Development] Tarun.bhandari:
New version for Cyanogen mod 10.2 (4.3) ?

Hi Startosk

Are you making a new version for Cyanogen mod 10.2 (4.3) (Pawitp already started working on 10.2 though it is not a nightly yet) ?

Thanks
[Galaxy S I9000 Android Development] iyahman:
THE question ^^
[Galaxy S I9000 Android Development] Opuz Klass:
For weeks I've had frequent system locks I didn't have never before (using Slim Bean ROMs). Locks were happening mainly using the Browser, Aquamail or using the Contacts...

Because of the way the locks were happening, I became more and more suspicious about something related with the GPU. I've checked changelog and noticed v3.0.0 introduced a new graphics driver... Changing kernel to previous v2.9.26 completely solved my system locks.

So, anyone else is having system locks with kernel v3.0.0?

Please report of you do!

Thanks!

Sent from my GT-I9000
[Galaxy S I9000 Android Development] stratosk:
Yes, it could be possible.

Though, I'm not sure that is proper way to add/remove drivers to support broken hardware.

Anyway, I could try to compile it as module, but I can't promise anything.

Hi,

No, I don't work on 4.3 for SGS. But, I think I will. :)

Could you please send a kmsg and logcat taken just after these locks? (you mean freezes?)
[Galaxy S I9000 Android Development] Alberto96:
Whats the name of proximity sensor driver? I cant find it :/
[Galaxy S I9000 Android Development] Torlugic:
Thanks!! Can't wait to try it out.
[Galaxy S I9000 Android Development] s3icc0:
light sensor

Hi, I've seen the proximity sensor discussion here and I have a question - my light sensor (or how it is called) can only determine two states - hi and low. i have this issue form the day I have this phone - therefore automatic contracting functions (even the improved in semaphore) are not working for me. Do you think there is a software sollution or the sensor is broken in my phone?
[Galaxy S I9000 Android Development] CatalystWon:
Has anyone tried LagFix (fstrim) with our device? Is it compatible with Semaphore?
[Galaxy S I9000 Android Development] grinder777:
It's working for system and data, but not for cache... with devil kernel...

SGS - Devil 4.2 - Black Beast - Cobalt Sam-X - Thnx2all
[Galaxy S I9000 Android Development] cannondaleV2000:
It doesn't work on cache at all as far as I know but cache isint used in jb so it doesn't really matter
[Galaxy S I9000 Android Development] KSLevel11:
http://xdaforums.com/showthread.php?p=44408197

Wysłane z mojego GT-I9000 za pomocą Tapatalk 4
[Galaxy S I9000 Android Development] TaMNoNa:
GPS have no signal

After I installed CM10.1 (Stable) + Semaphore 3.0.0 (from CM10, I did wipe data), I have no signal from GPS. My galaxy can't find even 1 satellite.

I tried to downgrade the kernel, so I installed Semaphore 2.9.26 and still, not working.

I tried to use those files: http://xdaforums.com/show...&postcount=230 and still not working.

I tried to change modem, not working.

I tried to clear the data on "Google Services Framework" (also tried to disable it), and still not working.

I did the hardware fix in the past.

The GPS worked fine before I moved from CM10 to CM10.1

Someone have another solution, or I have to go back to CM10?
[Galaxy S I9000 Android Development] panblock:
Try TopNTP from Play

Sent from a telephone booth...
[Galaxy S I9000 Android Development] :
Is there any possibility for this kernel to work on 4.3? Has anyone tried it yet?
[Galaxy S I9000 Android Development] ficko_98:
You will probably get bootloop.
[Galaxy S I9000 Android Development] idCyber:
I think there are 0% chances this 4.2.2 kernel will work on 4.3
[Galaxy S I9000 Android Development] knedlyk:
I tried, it doesn't work.

Вислано з мого GT-I9000 використовуючи програму xda app-developers.
[Galaxy S I9000 Android Development] Lorog:
Hi,

I have slim bean 4.2.2 build 8 and semaphore v3.0.0s with 409MB ram. I'd like to use liveoc, until now I was used to have 104% but lately I have fast reboot everytime I uninstall an app.

My processor is ARMv7 rev 2 (v7l).

Could it be due to changing from 397MB to 409MB ram? Or maybe is my cpu becoming unstable? So now I have 100% and it's ok for now.

What can I do to use liveoc? Do I have to change voltage too? How can I see my current voltage?

thanks
[Galaxy S I9000 Android Development] cannondaleV2000:
Yes its compitable

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

I would raise the voltage for 800mhz and 1000mhz or the L0 and L1 steps in the semaphore manager.
[Galaxy S I9000 Android Development] Giap:
Hi Stratos,

I'm on SB 4.2.8. After I switch off the phone, when I switch on again the phone sticks on Semaphore and dies not go ahead. I have to do several tentatives before to boot into SB. This happened also with 4.2.7. Have you an explanation and a fix? Thank you
[Galaxy S I9000 Android Development] twinky444:
It's a known bug of SlimBean that you may get a reboot when uninstalling an app, or when connecting the phone's storage to PC. Please, use SlimBean's thread for this, as it is not semaphore-related bug.
[Galaxy S I9000 Android Development] yfriday14:
The driver may be found in SGS i9000 in:

/system/lib/hw/sensors.aries.so

There are solutions, which disables the whole GP2A sensor, this also results all sensors are disabled, like accelerator sensor, which is good, and I would really need to use it.

The best solution would be to disable only the proximity sensor hardware in kernel itself, and leave the other sensors working.
[Galaxy S I9000 Android Development] Alberto96:
I need the Proximity Sensor name, not the library. Like yamaha ***** or bosch *****. Only with this i can make a proximity sensor switch
[Galaxy S I9000 Android Development] :
Voila, app: sensor readout from f-droid repo
[Galaxy S I9000 Android Development] yfriday14:
It would be a life saver, if you could make possible to disable proximity sensor hardware in kernel.

Currently I use a hacked /system/lib/hw/sensors.aries.so, but this way I losed in addition the proximity and light sensors, also the accelerometer, orientation, magnetic sensors, too.

AFAIK the proximity and light sensors are within the same hardware (GP2A), so if GP2A is disabled, I would lose both.

No problem, if I lose proximity and light sensors, but at least I could use accelerometer, orientation, magnetic sensors...

---------- Post added at 03:37 PM ---------- Previous post was at 03:21 PM ----------

I did a bit research, but not sure how detailed info do you need.

Quoting what I found.

GP2A Proximity Sensor, Sharp

http://www.digikey.com/product-detail/en/GP2AP002S00F/425-2785-2-ND/3247985

Manufacturer: Sharp Microelectronics

Manufacturer Part Number: GP2AP002S00F

Description:	PROXIMITY SENSOR 25MM

http://www.digikey.com/catalog/en/partgroup/ga1a-and-gp2a/26402

http://ichulu.com/product/gp2a200lcs0f.html

Samsung Model	GT-I9000 Sensors:

http://specdevice.com/showdevice.php?iid=242

SMB380 3-axis Accelerometer (Bosch Sensortec); range: 0...19,613; resolution: 0,038 (0,195%); power: 0,2mA;

MS3C 3-axis Magnetic field sensor (Yamaha ); range: 0...2000; resolution: 0,001 (0%); power: 6,8mA;

GP2A Light sensor (Sharp); range: 0...10240; resolution: 1 (0,01%); power: 0,75mA;

GP2A Proximity sensor (Sharp); range: 0...5; resolution: 5 (100%); power: 0,75mA;
[Galaxy S I9000 Android Development] Alberto96:
Thanks a lot, it will be a bit difficult because if i disable proximity also light sensor will be disabled (same sensor module :( ). I will try to set something in sysfs.
[Galaxy S I9000 Android Development] stratosk:
The driver code is located in drivers/input/misc/gp2a.c
[Galaxy S I9000 Android Development] Alberto96:
Yeh I know. I already found it.

UPDATE: im trying to compile 2 modules for gp2a sensor. One with only light feature enabled and another one with standard features. Testing...

UPDATE 2: Compiled fine, now testing feature with phone. This can be useful also for users that doesnt have both sensors working (light & proximity).

UPDATE 3: Nothing. This method isnt working. :( Searching some other method.
[Galaxy S I9000 Android Development] s3icc0:
I would like to flash CM10.2 but without Semaphore I will not give it a go. So my question is not when but is: Are you working on 4.3 kernel?

Thanks

Disclaimer: This question is not asking ETA ... just a survey
[Galaxy S I9000 Android Development] severin333:
Hello S3icc0, maybe the answer is here :
[Galaxy S I9000 Android Development] stratosk:
I'm working on it.

I had some issues and I had some bad luck, but I'm working on it.
[Galaxy S I9000 Android Development] severin333:
Good luck then, we are looking forward this new kernel !

Many thanks for still supporting our old device, even though you've got a new one :)
[Galaxy S I9000 Android Development] Alberto96:
Ok. Working method found. I will replace sensors.aries.so at every boot (based on user choice).

Example :

user have gp2a full working -> original sensors.aries.so (it will renamed to sensors.aries.so.bak)

user with proximity sensor broken -> limited sensors.aries.so

user with full gp2a sensor broken -> limited x2 sensors.aries.so

I need just to check if kernel size can contain all this libraries.

[MENTION=3750240]stratosk[/MENTION] : if you need this files, contact me via pm. Also, I saw that you are having problems for 4.3 kernel. Unfortunately me too. [MENTION=4196889]DerTeufel1980[/MENTION] is helping me for this.
[Galaxy S I9000 Android Development] SferaDev:
Hey stratosk we talked via mail some weeks ago! I'm finally using your kernel as prebuilt. And with the 4.3 arrival I made a poll with what kernel to use on 4.3, you're winning on the results due your stable stats. So I will wait to your kernel to release a new build. Also during this time I'm enjoying my vacations!

Thanks for your work, if you need any help just PM me.

Sent by the force with my Paranoid device!
[Galaxy S I9000 Android Development] stratosk:
Thanks.

I'm not going to provide extra libs with the kernel. I will check if the drivers misbehaves on hardware fault and I will try to do something there.
[Galaxy S I9000 Android Development] stratosk:
Could you please send a kmsg while the proximity sensor is active?

Also during your test, please try to cover and uncover the sensor.

EDIT: Also a logcat, please.