yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Nobody was insulting nobody; we were discussing the battery issue of the Gingerbread ROMs.

I think you were reading a different thread... :rolleyes:
[Galaxy S I9000 Android Development] jugster:
Sorry to have started this all... It has been interesting though... Just to recap: my phone was plugged in charging. I started using wifi tether. Phone told me it was full charged. It told me fully charged for a few hours while tethering. Upon removing USB cable I was greeted with 2% battery left in need of a full charge.

The battery indicator lied, or something else was wrong.

I'm certain there is a bug there somewhere.

Cheers,

J
[Galaxy S I9000 Android Development] robogo1982:
Guys, chill out. Or else...
[Galaxy S I9000 Android Development] DanDroidian:
EXACTLY! That is the bug that occurs sometimes! Using pikachu's theory, when u unplugged it, it SHOULD HAVE STILL have said 100%, but really be on 2%, thus appearing to go from 100% to 0% in a matter of minutes...
[Galaxy S I9000 Android Development] pikachu01:
The battery gauge will report out an accurate reading once you disconnect from the power supply.

Here's the commit that will fix it:

https://github.com/pikachu01/linux_gt-i9000-gb/commit/18fb4bb7eb3588b583bd38a380170925ff0f16bc
[Galaxy S I9000 Android Development] ZaneZam:
:eek:

A blind man once stepped on Chuck Norris' shoe. Chuck replied, "Don't you know who I am? I'm Chuck Norris!" The mere mention of his name cured this man blindness. Sadly the first, last, and only thing this man ever saw, was a fatal roundhouse delivered by Chuck Norris.

So watch out guys !! :D
[Galaxy S I9000 Android Development] sherpa25:
FWIW, no problem w/ my battery. Plug it in the evening and when I remove it in the morning, it stays at 100%, then goes down slowly as I use it. Wonder if it's Simplicity 2.1.1.
[Galaxy S I9000 Android Development] DanDroidian:
Exactly. Just like everyone else's phone, including mine. Pikachu has a special model that drains after reaching 100%, which he thinks is a feature.... Glad to hear that I'm not the only one with a normal phone, lol
[Galaxy S I9000 Android Development] jugster:
My model is the draining one. Albeit I actively used wifi tethering for a few hours. I did not leave my phone unused while I slept.

Could it be the reason we are seeing different results?
[Galaxy S I9000 Android Development] pikachu01:
You can check for the real battery indicator by using an app like battery calibrator that displays the current mV of your battery.

Check it after 4 hours of it hitting 100% (close to 4200mV). It should be something lesser like 3900ish mV but still reporting 100% and you are trolling again.

Attack the matter at hand, and not the person please.
[Galaxy S I9000 Android Development] djb77:
stratosk

Small request...

Could you update the Semaphore Manager in the Kernel to 0.73 please?
[Galaxy S I9000 Android Development] Rebel2k:
So here are the results after the flash of test 2 : it is still turning on in less than 3 seconds and detecting BT devices around! :) (now Kernel Version is correct in the phone properties ;))

No problem, it was a simple proposal to ease your work not to bother you. Good luck for your investigations! ;)
[Galaxy S I9000 Android Development] stratosk:
Thanks again.

OK, test 3. I enabled more things. But still, chainfire's apps not working properly.
[Galaxy S I9000 Android Development] stratosk:
No, It doesn't matter that you were on voodoo.

And, now works on normal 1.3.1??? That's strange.

Maybe if you clean dalvik and cache it will stop working...

Thanks for testing
[Galaxy S I9000 Android Development] Rebel2k:
Test 3 is conclusive. Everything is still working correctly: activating BT takes 3 seconds, and devices are discovered. I'm in for the test 4 ! ;)
[Galaxy S I9000 Android Development] stratosk:
quangmach gave me and idea.

Can you please flash normal 1.3.1? Please try it without cleaning anything.

If the BT still works then try to clean dalvik and cache.

In the mean time, I will prepare test 4 kernel.
[Galaxy S I9000 Android Development] Rebel2k:
I'll try it and give results in a few minutes.

RESULTS: I didn't wipe anything, flashed the "standard" 1.3.1 version, and BT WON'T turn on. So, you'll find the culprit for sure in the modifications you did in all test versions until test 3! :)
[Galaxy S I9000 Android Development] baba420:
Is it true that boot sound will be disabled after flashing this kernel on top of JVQ?
[Galaxy S I9000 Android Development] stratosk:
I actually I did the opposite. In test 1 I disabled a lot of stuff. Now, only a couple of things differs from normal 1.3.1.

Test 4 attached
[Galaxy S I9000 Android Development] stratosk:
Actually not only disabled. The boot sound will be deleted for making space in sytem partition.
[Galaxy S I9000 Android Development] MasterJam882:
what's really strange:

I don't have any problems with Bluetooth.

Tried all combinations:

-on alone

-on alone after restart

-on and wifi on

-on and wifi on after restart

-wifi on THEN bt on

All works.

After flashing, the first start takes lil bit long ~ about 10-15 secs but after that it starts in 3 secs finds all devices and works 100% with my in-car-bt.

Have standard JVQ with 1.3.1

So I don't know if u ppl can say that stratosk kernel is corrupt.
[Galaxy S I9000 Android Development] Rebel2k:
Sorry for the delay! Testing version test 4 right now!
[Galaxy S I9000 Android Development] Rebel2k:
Test 4 works again perfectly for the BT part! (flashed right after the 1.3.1 standard I kept from the last test - with not working BT)

Still there for the test 5 if you need! :)
[Galaxy S I9000 Android Development] stratosk:
You are very fast!

Test 5. Now chainfire's applications work.
[Galaxy S I9000 Android Development] quangmach:
On normal 1.3.1 for abit, sometimes it works but took a long time to officially enabled. Sometimes it doesnt. Its kind like time out to enable like i said before. Im gonna try your new build tomorrow. Now time to sleep. G9

I forgot to say, its something relate to chainfire. Come to his topic CF kernel, people complaining about BT problem now
[Galaxy S I9000 Android Development] Rebel2k:
Test 5 flashed, and the result is: FAIL, BT wont turns on with this last 5th test version (actually it turns on once, BUT it took really longer to turn on (around 15 seconds versus 3 on the 4 versions of test before)).

I confirm that CF-apps are working and detecting a 3.7 CF-kernel, but for your information I have no tweaks enabled in the "Tweaks" app. Do you want I turn some of them on?

Of course, still there for tests as long as you'll need me! :)
[Galaxy S I9000 Android Development] quangmach:
Hi,

I started to have BT now like me on normal 1.3.1. Can you tried restart few times with combining turn wifi bt on off respectively to see if its still working?

Its clearly can be see after you add back stuff of chainfire, the problem appeared
[Galaxy S I9000 Android Development] Rebel2k:
Wait! Indeed!

Test v5 is NOT working good!

I stopped wifi + BT, restarted, started wifi, and BT won't turn on...

EDIT: edited my previous post. It turned on only once in fact. Now, it is exactly the same as in the standard 1.3.1 version: very long time, no BT activation if wifi is started before BT.

Now, we need to understand why a bunch of tools are breaking the BT d-bus detection...
[Galaxy S I9000 Android Development] stratosk:
Rebel2k, quangmach your help much appreciated.

If you have time for a last test (6) and I will post the final results.
[Galaxy S I9000 Android Development] Rebel2k:
Of course I'll test it now! Results in a few minutes!
[Galaxy S I9000 Android Development] quangmach:
Lol your work makes me stay whole night. Cant wait to test it ;)
[Galaxy S I9000 Android Development] tomme45i:
I found a bug in recovery. When I choose "wipe data/factory reset" I have standard command: "-- Wiping data..." etc. Then, after "Data wipe complete." command, when I want choose file to flash by: "install zip from sdcard->choose zip sdcard" I have command: "No files found."! After rebooting recovery there is no problem, I can choose file that I want to flash.

I've tried also "mounts and storage->format /system" but after formatting done, and rebooting recovery I have:

E:failed to open /etc/recovery.fstab (No such file or directory)

E:unknown volume for path [/cache/recovery/command]

E:Can't mount /cache/recovery/command

E:unknown volume for path [/cache/recovery/log]

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:unknown volume for path [/cache/recovery/last_log]

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:unknown volume for path [/cache/recovery/command]
[Galaxy S I9000 Android Development] MasterJam882:
Had the same error yesterday as I wanted to flash ICS. Reboot solved the problem.

greetz
[Galaxy S I9000 Android Development] CheekyLord:
sorry..wrong thread..

Sent from my GT-I9000
[Galaxy S I9000 Android Development] tomme45i:
Thanks for reply, but rebooting give nothing in my case (I'm saying about "format /system" command). Only flashing new rom via ODIN can help. I tried it few times, and always have same result.
[Galaxy S I9000 Android Development] MasterJam882:
I meant the first part of ur post:

I found a bug in recovery. When I choose "wipe data/factory reset" I have standard command: "-- Wiping data..." etc. Then, after "Data wipe complete." command, when I want choose file to flash by: "install zip from sdcard->choose zip sdcard" I have command: "No files found."! After rebooting recovery there is no problem, I can choose file that I want to flash.

Second part didn't encounter to me so I can't make a statement to that.
[Galaxy S I9000 Android Development] O-T:
MasterJam

Have you tried to mount /sdcard after doing wipe data?

Don't know if /sdcard or /system get unmounted but you should have options to mount + umount both.
[Galaxy S I9000 Android Development] MasterJam882:
Didn't try because simple reboot solved my problem...never had that issue before and thought this would be nothing special but now another one had the problem maybe this could be a bug....
[Galaxy S I9000 Android Development] geokilla:
I had the same problem as well, and the way for me to fix it was to turn off the phone completely then boot into Recovery.

Anyone got the following problem I'm experiencing:

There seems to be a problem with Semaphore 2.5.0c. When uninstalling apps using TB, the apps are still leftover in the phone, even though 99% of the app is gone. It's been reported in the Apex thread and some people have said that switching over to Talon fixes the problem. I haven't tried it out myself yet.

I'm also getting boot loops when rebooting the phone without clearing cache. I have already flashed to stock prior to flashing the combo in my sig numerous times. This happened without ThunderBolt! tweaks as well so for sure it's not ThunderBolt! causing problems.

Edit: TB problem didn't happen again.
[Galaxy S I9000 Android Development] DanDroidian:
So, this is the last version of semaphore for gingerbread? 2.5.0?
[Galaxy S I9000 Android Development] vd69:
That's the end?
[Galaxy S I9000 Android Development] XuperLugia:
You should give an opportunity to CM9, no one get's back to stock after.
[Galaxy S I9000 Android Development] elhennig:
The current open bugs are still show stoppers IMO

But with the next build these might be solved and then....
[Galaxy S I9000 Android Development] malcho:
I think that build one kernel is job.Maintain two kernels is extra job.And all for free.It's not fair to demand stratosk to do extra job.

He already done much.
[Galaxy S I9000 Android Development] THUNDERASS:
kernel ll be support to nstools future?
[Galaxy S I9000 Android Development] DanDroidian:
How's the battery life, compared to stock ?
[Galaxy S I9000 Android Development] lord_danko:
Stratosk one a question. When from cwm select sdcard partition ext (512) and Swap 32mb the phone later does not begin remains in an infinite bucle in logo (galaxy s), I have proved it several times even with rom it cleans and formatting earlier the sdcard. Do you know for that? .I have the internal sdcard only.

Thanks
[Galaxy S I9000 Android Development] skodaslx:
+1

10char
[Galaxy S I9000 Android Development] vasra:
Had my first hard crash (blank black screen) yesterday on Samsung JVU and Sema 2.5.0bm.

-Pressed the power button to turn off display (worked)

-Tried to wake up the phone by pressing the power button (didn't work)

-Tried Home button, power again, waited, waited, waited, pressed again. Nothing worked

-Screen stayed black (didn't wake up)

-Had to pull the battery

It has been a *long* time since I've had a hard crash like this (maybe a year ago on some exotic kernel).

Of course, I cannot know for sure if it's due to the JVU firmware or due to Semaphore 2.5.0bm, but at least the combo isn't working 100% stable for me.

Just FYI, great kernel nevertheless (only one crash so far).
[Galaxy S I9000 Android Development] elhennig:
Pressing the power button for more than 8 secs should suffice...
[Galaxy S I9000 Android Development] rmean:
Do you UV?
[Galaxy S I9000 Android Development] dukuletz:
Hello, i'm using 2.4.0 now with stock JVT. Is it normal when using Ondemand and Smartass2 Governors the CPU speed is always at 800MHz-1GHz? Usage percentage is around 6% in standby.

I switched it to Conservative now, and it's ok, 100Mhz standby.
[Galaxy S I9000 Android Development] rmean:
smartass always scales that high while screen is on, providing great performance which has to be paid with battery life :)
[Galaxy S I9000 Android Development] vasra:
Nope.

No UV, no extra script, no startup/lockscreen/icon packs.

Just vanilla JVU + Semaphore. Absolutely nothing else. Standard clocks. Standard volts.

As for power button for 8secs, yes I know, didn't work (oddly enough).
[Galaxy S I9000 Android Development] ZACQ8:
compatible with any firmware?

Hi,

Please give me a quick answer, is the v2.5.0 is compatible with any versions of firmware?

Which are sutable kernals for my following versions of firmware

XXJVP & XWJW1

thanks.
[Galaxy S I9000 Android Development] Bubble-be:
Search !

(10char)
[Galaxy S I9000 Android Development] chavocarlos:
You must Folow This Tip :p

Yes it is compatible with all 2.3.x, you should use last one.

Sent from the center of the earth.
[Galaxy S I9000 Android Development] Bubble-be:
There, you spoiled it ! :D
[Galaxy S I9000 Android Development] vd69:
I can say that i am proud for you Strato.First for your origin and second for your achievements.I' ve been using your kernel as long as i have my SGS and i am very satisfied.

I have one last request and i know that your are a very beasy man.

Is it possible to make one version for latest JVU 1)whithout voodoo sound so that can be possible to record our calls and 2)correct the modprobe link issue so that the droidwall can apply the ip table rules.

Thanks for everything.
[Galaxy S I9000 Android Development] pikachu01:
You need to enable netfilter for the latter to work?
[Galaxy S I9000 Android Development] vd69:
no its not .I have netfilter enabled
[Galaxy S I9000 Android Development] pikachu01:
Hmm, weird. Back when I tried this kernel, droidwall worked fine :/

Probably stratosk can look more into this (though its improbable as he's mainly in ICS now)
[Galaxy S I9000 Android Development] stratosk:
Thanks my friend.

About the first one... I can't promise anything... :)

About the second the solution is very easy. We need to remove the modprobe link in /sbin.

You may try it using a root explorer. Maybe a workaround would be an init script that delete this link.

Yes, the problem is that with the new busybox I made a symbolic link from modprobe to busybox. Modprobe by default searches for modules /system/lib/modules. Unlinking modprobe solves this issue.
[Galaxy S I9000 Android Development] vd69:
What line should I erase?

Or must I erase it all ?what exactly do you mean?

How to unlink it?

Thanks.
[Galaxy S I9000 Android Development] stratosk:
You need to delete /sbin/modprobe file on every boot. Here is an unit script (untested - I'm not on my computer.

#!/system/bin/sh

mount -o remount,rw rootfs

rm /sbin/modprobe

Copy this to a file, copy to /etc/init.d give it executable permissions.
[Galaxy S I9000 Android Development] ZaneZam:
Hi all,

inspired from stratosk's post i did a little "quick'n dirty" addon pack for semaphore manager. The init script within this pack will delete the symlink "modprobe" on every boot so droidwall should work w/o problems, at least it did for me after using this addon pack! :)

For all who want to use it : as usual, just install it in semaphore manager and after that tick "Droidwall fix" under "Addon Tweaks". ;)

Enjoy!
[Galaxy S I9000 Android Development] jdwis:
hi

my galaxy i9000 original had froyo 2.2

i rooted it, then as per Darky's guide flashed first rom.

now it shows following details -

on *#1234#

pda - I9000XWJS8

PH - I9000XXJVE

CSC - I9000OXXJS1

Bld info - 2011.03

on settings>about phone

firmwr - 2.2.1

baseband - I9000XXJVE

Kernel - 2.6.32.9 ficeto@vpn#dark_core_1.4

bld no - darky's v9.5.xwjs8

Also the recovery originally was 3e, but just before flashing Darky's rom, as mentioned in his guide, thru Odin I installed and now my recovery says Dark Core Recovery

though it is very much similar to CWM, but i m not the expert.

having this details now, how can i flash this rom?

thanks
[Galaxy S I9000 Android Development] sefira:
This is a kernel...not a rom. Flash the tar file through Odin, set as PDA.
[Galaxy S I9000 Android Development] chavocarlos:
I think that you are still on froyo based ROM, this kernel will not work with your current ROM, this works with 2.3.x (gingerbread) ROMS. This kernel could be flashed with SGS kernel flasher (market) instead ODIN.

Sent from the center of the earth.
[Galaxy S I9000 Android Development] jdwis:
any link for the guide would really help please.
[Galaxy S I9000 Android Development] iHero96:
What about USB Host?
[Galaxy S I9000 Android Development] hackeron:
Ive gone back to JW1, can I use 2.5.0 version or is it better to stick with 2.4 ?
[Galaxy S I9000 Android Development] Ztrindberg:
I wonder the same?
[Galaxy S I9000 Android Development] stratosk:
I suggest you to use the latest version - 2.5.0
[Galaxy S I9000 Android Development] lejarton:
Hi, thx for this kernel, it is for me the better that I have tested !

The only thing I would have to know because it's on long time question for me...

I am on a Gingerreal rom on a JVS version, everything is working fine so I don't want upgrade it.

And my question is about knowing if I have only to choose the semaphore for JVS (1.7.5 if I remember) for better compatibility or if I can choose the very last Sempahore kernel even if I'm on a JVS ?

:)
[Galaxy S I9000 Android Development] woodworm01:
No microphone

Everytings works fine except for the telephone microphone. Everytime I answer the telephone I first have to put it on loudspeaker before anyone hears me and when I put off the loudspeaker again, it keeps working fine till the next call.

Anyone any idea how to fix this?

Galaxy S

pda: XWJW1

Phone: JVT

CSC: JV5
[Galaxy S I9000 Android Development] Black Rose:
I'm using Semaphore 2.5.0sc with JW1, works great.
[Galaxy S I9000 Android Development] daigoro64:
Same here with Semaphore v2.5.0.
[Galaxy S I9000 Android Development] GirlKillu:
Since this Kernel is for any 2.3.x , does it also support CM7? since its not a samsung based rom, i just want to make sure.
[Galaxy S I9000 Android Development] woodworm01:
No microphone

Today I flashed te Semaphore Kernel 2.4.0 and seems to work ok. There's only one problem, when I receive a phonecall the microphone doesn't work so the other side can,t hear me. When I activate the loudspeaker the mic suddenly works again and when I deactivate the loudspeaker the microphone keeps working.

Does anyone have a solution for this problem?

Woodworm

Galaxy S

pda: XWJW1

Phone: JVT

CSC: JV5
[Galaxy S I9000 Android Development] O-T:
Only Samsung based 2.3.x

Some candidates here: http://xdaforums.com/showthread.php?p=14273101
[Galaxy S I9000 Android Development] Raider0001:
where can i get cifs.ko and slow-work.ko for XWJW1 Semaphore kernel JW1 2.4.0 ?
[Galaxy S I9000 Android Development] O-T:
2.5.0 kernel:

/lib/modules/cifs.ko

No idea where to find slow-work.ko
[Galaxy S I9000 Android Development] ArctiX:
Oh, accidentally clicked post in tapatalk ;P

Was about to flash this kernel ;)
[Galaxy S I9000 Android Development] depika:
Γεια σας παιδιά

Μία ερώτηση.

Κατέβασα από το samfirmaware το Gingerbread.XXJVU και το έκανα flash με το Odin.

Τώρα για το kernel πρέπει να χρησιμοποιήσω την ίδια έκδοση? π.χ. για την περίπτωση μου είναι το Semaphore_kernel_JVU_2.5.0beta.tar ?

Έχω μπερδευτεί ως προς αυτό το θέμα σχετικά με το ποιο είναι το σωστό αρχείο.

Ευχαριστώ

Δέσποινα

Αθήνα
[Galaxy S I9000 Android Development] zsandras:
Have you installed the InCallRecorder.apk? It could make a same problem on Gingerbread.
[Galaxy S I9000 Android Development] vd69:
Οχι το Semaphore_kernel_JVU_2.5.0beta.tar αλλά το

Semaphore_2.5.0sc.tar

Καλή τύχη Δέσποινα.
[Galaxy S I9000 Android Development] mdacic:
STRATOSK thank you for this great kernel. I'm using JW1_2.4.0 with darkyrom 10.4.2. Works like a charm.

1. I love your brightness driver!!!

2. Did anybody test under-volting and what are the best settings for Galaxy S i9000? Are any noticeable battery savings achieved by under-volting?

3. Maybe we could get some under-volting scripts (with various settings)?

Thank you and continue great work...
[Galaxy S I9000 Android Development] HM.Carbide:
There are already undervolting scripts in Semaphore Script Manager Thread in OP.

Use first the uv in misc section, this will be reverted on boot.

If you have a stable setting, you can choose the uv setting in kernel features.
[Galaxy S I9000 Android Development] woodworm01:
Thanks for the reply, and no I haven't installed the incallrecorder.apk but I have TotalRecall installed. Could that be the problem? I will deinstal totalrecall and see if that solves the problem.

I have deleted TotalRecall and that solved the problem, Thanks a lot. You made me a happy man.
[Galaxy S I9000 Android Development] mdacic:
Thank you HM.Carbide. I have found the scripts and activated the test one (the most undervolted one)...

I hope there will be battery savings...

Did anybody actually measure how much battery is saved by undervolting?
[Galaxy S I9000 Android Development] kohkohnut:
Hi

I am about to use Semaphore for the first time. And my only previous experience with a custom kernel was Speedmod which is not updated anymore. Before I take the plunge, can somebody tell me what are the existing issues/bugs with Semaphore? For example BSODs or it breaks some system apps.

There are simply too many posts for me to go through and I hope someone would be kind enough to tell me so that I know what I am getting myself into.
[Galaxy S I9000 Android Development] anuj_blaster:
i have flashed.. CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip

on my GTI9000 2.3.6

now if i want to flash... Semaphore_2.5.0scbm.tar

- do i need factory reset?

- do i need to convert all ext4 to rfs?

in all.. what should i be doing if i have already flashed something before?

Thanks in Adv :)
[Galaxy S I9000 Android Development] mdacic:
Just flash the kernel on top of that. No factory reset needed, nor converting ext4.

I flashed through darky OTA app, but there are also other OTA apps, so can flash it directly from the phone... Just follow the instructions on semaphore site and it will work.

---------- Post added at 10:14 AM ---------- Previous post was at 10:08 AM ----------

Everything works great...

Using scripts by hm.carbide you can greatly customize and improve the kernel. I'm absolutely satisfied!

I measured 2% overnight battery loss (for 9 hours). Phone is on wcdma only and packet data disabled...

Today I'll measure battery loss while listening 1h to audiobook...