yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] dongfangri:
Samsung (or Google?) is stupid for battery charing. They should learn how battery charging works on laptop:

Once the charger is pluged into the phone, the charger will supply the power, whether the battery is full or not. This will make the phone work as long as possible while the charger is unpluged.
[Galaxy S I9000 Android Development] pikachu01:
Well, Samsung doesn't have the luxury for that. To have that kind of form factor, they can only build the voltage regulator direct to the battery :/
[Galaxy S I9000 Android Development] jna9000:
It surely is a bug. Charging needs to start at one time again to prevent power failiure. Every dumb battery powered device works like this for decades, but this very smart phone can't? Sorry...

One side note: I usually start to charge around 10pm, unplugging at 7am (I usw the SGS as an alarm clock, so I charge it every night). It usually is close to 100% when plugging off. However, sometimes at weekend I go to bed even earlier but stand up later - in these cases the power drops (a bit) more, like 93-95%.

On the other hand, I suspect the phone not to take 9 hours to charge (but to lose more power than 2% at night), so this bug isn't there always.

BTW: Is this related to the kernel at all? I saw the bug with other kernels (including Stock) as well, so maybe we are off topic here....
[Galaxy S I9000 Android Development] pikachu01:
As mentioned, the battery indicator lies to you when plugged into the charger.

Yeah, if the charging is dumb, then throw away that dumb phone and get a 3310? :P
[Galaxy S I9000 Android Development] jugster:
I guess the questions are:

Are we satisfied with that?

Can it be changed to behave more intelligently?
[Galaxy S I9000 Android Development] pikachu01:
I believe that most won't be satisfied with that, but it can be alleviated by either:

- living with it, charging again when your battery falls and try not to introduce wakelocks when phone is charging and you're sleeping.

- hacking the kernel to trickle charge (which deteriorates the battery life somewhat).
[Galaxy S I9000 Android Development] Aron1980:
NVM wrong section XD
[Galaxy S I9000 Android Development] sbnaul:
Hey guys in Android Terminal Emulator with this

su
recovery

i enter recovery but on every hardware button click, many color patches cme on the screen... Going into recovery using button combo, everything wrks like butter... Doesnt bother me mch but just felt like checking with the rest...
[Galaxy S I9000 Android Development] stratosk:
You should use:

su
reboot recovery

But, I don't recommend it, because it immediately reboots the device without shutdown properly. This may lead in filesystem corruption.
[Galaxy S I9000 Android Development] sbnaul:
Thanks... Wud keep ur tip in mind...
[Galaxy S I9000 Android Development] andip71:
Hi Stratosk,

yes, I had that corruption already sometimes :confused:

Is there a way to reboot safely from a terminal session (or via a script) into recovery?

Many thanks

Andi
[Galaxy S I9000 Android Development] HerrDesRinges:
AVRCP 1.3

Hello together!

A few days ago, on the german "GoaTool" board (board for the well known custom rom "GoaTrip") someone askes, if it is possibel to put the AVRCP 1.3 (Audio Video Remote Control Profile) - a bluetooth protocoll - into the semaphore kernel...

On stock rom, the SGS1 only supports AVRCP 1.0 , but the SGS II supports version 1.3, which has so nice features like transfer the title, artist etc. via bluetooth for example to your radio in your car.

Is it possible to transfer the bluetooth part of the SGS II kernel to a future release of the great semaphore kernel for our SGS1?

Thank you for your support!!!
[Galaxy S I9000 Android Development] jugster:
That sounds strange, most won't like it, but it helps living with it? Is there another choice?

I believe trickle charge is not necessary. The phone seem to think it is ready to be charged when it passes the 15% barrier, why can't the software let the charger know that it accepts charging when that limit is passed. The charging process would then be fully charged -> 15% left, start charging -> fully charged. Much like if a real person was in charge (no pun intended).

Also, that the indicator shows 100% when the cable is in is a bug no matter which way you look at it.
[Galaxy S I9000 Android Development] MasterJam882:
This would be just awesome and for me the best tweak for the sgs, besides ext4, out there.

Would also like to know if this is possible.

Greetz

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] stratosk:
Let's go ICS :)

http://xdaforums.com/showthread.php?t=1468795
[Galaxy S I9000 Android Development] Fenvarien:
Thank you Stratosk, that's just fantastic. Now I will finally switch to ICS and can still use the great Semaphore features!

... using tapatalk
[Galaxy S I9000 Android Development] a g bell:
@stratosk are you moving to ics or continuing with Gingerbread development?
[Galaxy S I9000 Android Development] stratosk:
Personally I use ICS and I will not go back. Sorry, but I can't wait Samsung.

I'm not sure if I can maintain both ICS and Gingerbread versions.

I will try, if I have time, but I can't promise anything.
[Galaxy S I9000 Android Development] Syntaxer:
Which ICS are you using ? :)
[Galaxy S I9000 Android Development] stratosk:
I built Semaphore_ICS for CM9, tested there.
[Galaxy S I9000 Android Development] ZaneZam:
Hi Stratosk,

yeah maybe we will get some kind of ICS on I9000 from samsung when android 6.0 releases, who knows! :)

So you are now on that CM9 Alpha build 15. Well,

are all these issues still present in build 15?

(http://xdaforums.com/showthread.php?t=1363593) :

Known Issues

Camera does not support scene modes

FM Radio does not work.

Phone unnecessarily gets data connection on device encryption password enter screen.

Cannot format external SD *

Android OS battery usage display higher than normal.

Sometime wrong SMS selected for forwarding

Format internal instead of external SD when requested to format ext. SD

Transfer speed slows down when screen off

Gallery face glow FCs

Screenshot shutter sound

Camera crashes when changing resolution

TV Out using HW-decoding (probably won't be fixed)

Sim Toolkit (probably won't be fixed)

No camera focus mode setting

Back camera does not record geotagging

Compass doesn't work in Google Maps v6

Unable to dial "0001" in some regions

Regression in BUILD 15: Superuser application crashes (fix)

Regression in BUILD 15: Data Roaming enabled by default

Slow USB transfer speed for some people

If so, then that is too much for me atm! :(

It would be great if you find some time to throw in some new versions of Semaphore for GB!

Anyway, i will stay on GB for now and my phone stays available for you to test new versions! ;)
[Galaxy S I9000 Android Development] malcho:
I think it's time for stratosk to move on and make new stuff.Gingerbread is good but it's time to go on.

Midnight kernel is great alternative.Also galaxian.

Stratosk i completly support you you make a right desicion.
[Galaxy S I9000 Android Development] DocMarc73:
What is that supposed to mean???
[Galaxy S I9000 Android Development] ZaneZam:
No doubt, i definitively support his decision too, and i would follow him right now if there wouldn't be that big Issue (for me!) list! ;) maybe there will be a build of CM9 with which i can live in the future, i will stay tuned in any case! :)
[Galaxy S I9000 Android Development] pxrave:
so no futher development of sema 2.3 :( i hope you can implenting the galaxian colors ;)

and give us some updates because ics have to much non working functions, i hope there will fixed soon ;) i think i will try ics in summer
[Galaxy S I9000 Android Development] Fenvarien:
I switched to ICS B15 today and really don't regret it! Build 15 is very stable and I did not encounter any bugs so far. Only Superuser FC, which is quite easy to solve. Semaphore ICS works great :-)

... using tapatalk
[Galaxy S I9000 Android Development] stratosk:
I didn't say I will stop it. Depends on my free time. I do this for free. I will also have to work on my real job for living.

About, galaxian colors: please search this thread. I already answered this. I am not going to implement galaxian colors in Semaphore.

I didn't noticed problems on daily use. Not so many non working functions actually:

TV Out using HW-decoding (probably won't be fixed)

Sim Toolkit (probably won't be fixed)

Cannot format external SD *

Android OS battery usage display higher than normal.

Screenshot shutter sound

Back camera does not record geotagging

I say, who cares. And it's still alpha version...

We can enumerate a lots of bugs in GB Samsung's roms...

who cares.
[Galaxy S I9000 Android Development] a g bell:
HMM lcs cm9 here l come then gingerbread is stale
[Galaxy S I9000 Android Development] nguyen47:
Please , don't leave us until CM9 gets official :(
[Galaxy S I9000 Android Development] Shuryou:
The known issues list is larger than that in their official thread (like, twice), I've not tried it myself because of that. Also, many of the bugs that are present now will be there forever if Samsung doesn't release the drivers of the device (which I don't think they will).

I've always used your kernel, so maybe I give ICS a go with Semaphore someday.
[Galaxy S I9000 Android Development] BrenMcgee:
Hey guys,

I know this may be a bit of a stupid/basic question, but I haven't found the answer yet. I am running a stock JVQ with a rooted voodoo kernel. Can I flash this kernel no worries? I am planning on put a new rom on so I want to put this kernel on with the new CWM first. Will be using Odin.

Sorry for such a basic question, I just couldn't seem to find an answer.
[Galaxy S I9000 Android Development] sefira:
Yes you can. Flash as PDA.
[Galaxy S I9000 Android Development] BrenMcgee:
Thanks for that mate, appreciate it.
[Galaxy S I9000 Android Development] Bubble-be:
I can surely understand your move and to be fair: there's not much left to do in the GB kernel.

Thanks for providing a great kernel and I'll see you on the other side when ICS has come of age.
[Galaxy S I9000 Android Development] pxrave:
hey mate i saw in your ics thread oc to 1100? can you do this whit this kernel too?
[Galaxy S I9000 Android Development] Shuryou:
It's already done, go into Semaphore app, "kernel features".

You can go even higher than that, it's on the first post.
[Galaxy S I9000 Android Development] spambayes:
Hi Stratosk,

Is it possible to incorporate the necessary changes eg., kernel patches in Semaphore to allow for 2-way call recording?

Although there are quite a few call recording apps on the Market, they only work well on patched kernels or ROMs with built-in support for this feature.

Could you take a quick look at http://j.mp/xcgSIs and http://j.mp/wC2Qbq ?

I've found some patches at http://code.google.com/p/2-way-call-recording/source/browse/#svn/patches . Not sure if they're of any relevance.

Thanks.
[Galaxy S I9000 Android Development] pikachu01:
Yeah, it's a bug which has been fixed by TalonDev :)

About the charging barrier of 15%, if the phone drops 15% of battery per hour, in 9 hours, you'll be charging your phone 9 times (which reduces your battery life 9 times as fast?).

You need to get rid of the wakelocks dropping your phone by 15% in an hour still right?
[Galaxy S I9000 Android Development] jugster:
I didn't mean it should charge when it had dropped 15%, I meant it should charge when it had dropped _to_ 15% left. So each time the battery has 15% left it should charge right? That is what any human would do anyway.

I mean what if you use your phone as a gps device and have a drive that will take 12 hours. Right now when it is plugged in it would charge to full, then it would start using battery until depleted which is long before my drive is finished. If it started charging when at 15% it could easily do that drive albeit with a couple of charge cycles, but hey it would work and that is what any user would expect!
[Galaxy S I9000 Android Development] Coolgreek:
They're not relevant as they concern other phones and not sgs! On sgs all attempts for call recording on Gingerbread 2.3.x roms (so far) have failed!!! There were some devs working on fixing that but at no good. More here!

PS: Strato good to know we will still have your kernel even after upgrading to ICS... Great news (so good actually that i am really thinking on upgrading too)! However as ICS is still in heavy development i will wait for a bit longer before i try...
[Galaxy S I9000 Android Development] pikachu01:
Ahh, I thought it was the other way around. Sorry for the misunderstanding.

Well, it could be done if Stratosk wants to do it :)
[Galaxy S I9000 Android Development] ngenhit:
That list of patches are for qualcomm devices , as noted by the author.

I wouldn't bet on this to work for our phones, unless somebody study the korean kernels source (if they are published ) . ;-).
[Galaxy S I9000 Android Development] DanDroidian:
I wouldn't discuss charging a galaxy s with pikachu, he is still under the false impression that once a galaxy s reaches 100% full, it will then start to drain to 0% even if it remains plugged in....
[Galaxy S I9000 Android Development] DanDroidian:
So, 2.5.0 will most likely be the last semaphore kernel for Ginger Bread?
[Galaxy S I9000 Android Development] pikachu01:
Umm, that's the fact actually. Your post is very close to trolling. :/
[Galaxy S I9000 Android Development] MasterJam882:
Ur right saying it's fact but nevertheless it's a bug.

Every other electronical device which can be charged WILL charge as long as it is plugged in. And this was the case. with sgs on earlier versions too.

So ppl are right when they say this is a bug introduced in gb. Ur right saying that it is a protection for overloading and I would never say something against that statement BUT battery should charge again after reaching 80% and so on or even when 15% are reached. But not charging at all after 100% and using battery till it's empty is wrong and a bug.

As said before, every electronical device such as phones, gps and so on would be unusable after many hours though they are plugged?!

But I'm glad too see that theres finally a solution for it made by ezekeel which forces the phone to hold ur defined limit - 'battery life extender'

Greetz

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] pikachu01:
Yes, as I've mentioned, Semaphore can implement this if Stratosk deems so. But note that if your battery drains more than 50% in just a few hours while plugged in, the problem lies in the wakelocks, not the charger.

Solving the wakelock would in turn, make your phone sleep better, reduces drain while charging and you would possibly won't ever need a recharging fix.
[Galaxy S I9000 Android Development] MasterJam882:
Thats another problem which many users have here - totally right and I agree with u here! This one and the above mentioned fact brings many ppl here in trouble.

Greetz

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] ZaneZam:
That's the point! I couldn't have said it any better. ;)
[Galaxy S I9000 Android Development] MasterJam882:
Here's another very interesting tweak for all who have wifi problems:

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

Would be great if this could be implemented together with the new voodoo color(no green flash anymore).

and this posted by HerrdesRinges:

greetz
[Galaxy S I9000 Android Development] pikachu01:
I think that requires it to be bundled in to a ROM as it's a framework setting.
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Yeah... I've tried it, in several threads, and all he says is "remove the wakelocks" (WHEN I HAVE NONE, WITH A STOCK JUST FLASHED AND DE-BLOATED) and "that's how it works... and it's OK, it's the expected behavior!". :rolleyes:

I really thinks he works for Samsung, becase every battery device in humans history doesn't work like that :p

---------- Post added at 11:24 AM ---------- Previous post was at 11:19 AM ----------

Here I go again...

It doesn't matter if the problem is in the wakelocks or that I left a 720p video playing on full volume in a loop!

The user still expects and needs to have the phone on 100% (95~97%) after unplugging in the morning! Do you really expect that an average guy who bought the phone and doesn't care for researching it, has to look into the system level wakelocks and troubleshoot them in order to have his phone charged OK??? :O
[Galaxy S I9000 Android Development] pikachu01:
Don't blame me. I work for Intel, not Samsung. I'm only giving you this advice for free. Don't point your anger at me when I say this as it's pointless and trollish. If you want, build your own kernel and fix this yourself.
[Galaxy S I9000 Android Development] DanDroidian:
It is NOT a fact! If it were a fact I would be unable to get up and use it (screen on with 3G web surfing)for OVER 3 HOURS plugged in, then unplug it, and get ANOTHER 5 HOURS of "use/screen on" out of it before it drains again! IMPOSSIBLE!
[Galaxy S I9000 Android Development] pikachu01:
As I've mentioned, your 100% isn't really 100% and your gauge is lying to you. :/
[Galaxy S I9000 Android Development] MasterJam882:
@Dan_Aykroyd

As I mentioned above:

it's the combination of this bug AND the wakelocks so pikachu is not wrong with his statement and you aren't wrong.

It's normal that battery never gets charged to 100% and it's normal that after 100% battery gets used BUT the bug is that there's no limit where battery will get charged again while plugged and it goes down to 0%

I totally agree with u that for a standard user who has no clue about all that stuff this bug is a absolute no-go and has to be fixed in the future!

A battery driven device has to stay at least in a certain range (90-99%) when plugged from the charger no matter how much I used it.

So I would say 90% would be the limit while device is on charge so that when 90% reached because of usage the phone gets charged again to 100% and so on till u remove from charger. This would ensure the user always stays in above mentioned range.

But nevertheless the real existing wakelocks on some devices have to be removed also for best user experience.

greetz
[Galaxy S I9000 Android Development] chavocarlos:
Back to stock

Hey guys,

Back to stock and send a mail to Samsung, don't blame devevelopers that want to share his work for free, that share the works that they consider great to share.

Nobody limits you to back to stock, go on.
[Galaxy S I9000 Android Development] DanDroidian:
Probably right (about him being on Samsung's payroll). He even went as far as to call me a troll. I've never been called that in my life, lol!

I've experienced that bug, usually if I unplug it when it's near 100%, use it A LITTLE, and then charge it again, and then after several hours unplug it, and THEN it will show something like 85% the moment I unplug it, and I believe THAT % is correct, but THAT is the bug for letting it drain that fair in the first place while plugged in....

Anyways, my previous post proves to myself (and hopefully has happed to others, which should prove the same thing) that his "theory" just isn't possible..... Maybe I have a special model, lol....
[Galaxy S I9000 Android Development] pikachu01:
Yes, but one could argue that, if you lose 10% per hour when plugged in, you would in theory recharge a total of 9 times if you slept for 9 hours, which is 9 times more than the average times you're charging the battery.

I'm not arguing for the sake of arguing. I'm only pointing out the facts that are in the source code itself. How you interpret my "facts" is just your point of view. I don't work for Samsung, nor I receive money for defending Samsung or their phones. So stop with the trollish behaviour and do something that benefits this community other than yapping about boohoo I wanna stay plugged in etc.

---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------

As I've mentioned, check for wakelocks and see what's draining your phone. Post your logs in the BetterBatteryStats thread. Have you done that? If not, why come here and argue your way out? If you are right and it's a bug? Prove it with a BetterBatteryStats log. I'm only interpreting what's in the code, I'm not winning money by proving that I'm right .... zzzzzzzzz
[Galaxy S I9000 Android Development] DanDroidian:
LoL, I only have this "bug" once in a blue moon. No big deal! Again, it almost always works like every other phone/electronic I've had.

I use it hours on end while in bed and plugged in (and that is after it has reached 100% many hours ago).

I finally get out of bed and unplug it late in the afternoon, and it almost always says 99-100%.

I can then get several more hours of screen use out of it before getting home at 5am again on weekends.

(i'm American, but live a crazy life out here in Cambodia, and sometimes my phone has been on 100% over 10 hours before I drag myself outta bed and do it all over again, and I've NEVER had it drain abnormally quick after unplugging it when it said 100%. I feel they reading must be accurate)
[Galaxy S I9000 Android Development] pikachu01:
It's actually inaccurate. If you want accuracy, use TalonDev kernel for a while. It has a patch that actually shows the battery drain. :)
[Galaxy S I9000 Android Development] DanDroidian:
Again, I have no wakelock/drain problems! Wakelocks, wakelocks....aaaghhh!
[Galaxy S I9000 Android Development] pikachu01:
There are a few ways your battery can drain (while plugged in or not):

- Lattitude

- Location check in app

- Facebook app (when you first sign in and try to sync)

- Facebook app (after you've just added a whole tonne of friends and it tries to sync)

- Facebook app (after you've initiated a chat and left the window open)

- Any messenger based apps (wakelocks so that it'll receive instant messages the moment it comes in)

- Any messenger based apps that have ping (constantly wakes up the phone to check for messages)

- Email app (downloading huge mail?)

- Samsung apps (for no frickin reason it will wake up your phone. Suggest to freeze or remove them altogether, i.e. Chaton, Samsung whatever Hub).

- Some games (that syncs or have background services)

It's either of these, and some of these only happens some of the time, which would explain your wakelocks.
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Sorry again pikachu, I wasn't angered at you, just debating about the subject. I'm sorry if my message offended you, it wasn't the intention, you've always stayed calm, so thanks :)

About the above list:

- I don't have enabled any Latitude and Location app

- I don't have installed the Facebook app

- I don't have installed any messenger apps

- I have the Gmail stock app

- I've uninstalled (Titanium Backup) all the system, bloated Samsung apps (plus others)

- I've only the Game Dev Story game, which has no services or intents that run randomly

I know what you say it's right (that the phone stops charging after 100%) and that if you have wakelocks it will drain faster. What I can't accept is the fact that the phone doesn't resumes charging after some value (80%?), because you might say that's to prevent battery wastage, but in any case it's the same thing that a user do afterwards: in the morning, when the phone is 20%, I have to unplug-plug in order to toggle the charging circle.

Thanks,
[Galaxy S I9000 Android Development] pikachu01:
If that is not the case, then there might be something else either kernel related or app related that hung while having the wakelock. A BetterBatteryStats log would suffice.

Sorry about flipping off. I'm usually unhappy when users try to point the argument towards the person rather than the matter at hand. How good of an argument doesn't depend on who the person is, rather how much sane facts are presented.
[Galaxy S I9000 Android Development] Nergla:
Hey - keep this correspondence on topic please - I just had to wade through 4 pages of you insulting each other - pse use PM for that
[Galaxy S I9000 Android Development] stratosk:
Everybody, please stay calm and on topic. :)