yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
We WILL resolve this issue.

OK, I will write down the facts. Correct me if I'm wrong:

1) Version 1.8.2, OC no reboots.

2) Version 1.8.2d, OC no reboots. But 1.8.2d (newmail's patch) it is not absolutely the same as 1.9.0 final (DVFS locks are missing). But it's the same with 1.9.0beta.

3) Version 1.9.0beta, OC reboots

4) Version 1.9.0, OC reboots

5) Version 1.9.0test, OC reboots. This version has the latency back to 40000

6) Version 1.9.0test2, OC reboots. This version has the 335MB available ram.

So, most probably as darckengel said it is not newmail's patch. 341MB also no problem.

Car dock support: I doubt about this causing problems.

Gzip compression: most Semaphore's initramfs versions were compressed with gzip. Kernel decompress this during boot and that's it. I don't think so.

Changes in initramfs: updated scripts, updated HM.Carbide's Semaphore app. I doubt because you don't use it before boot. (I mean they don't run as services).

I think we can try 2 more things:

1) A version with newmail's patch excluded. Pure ondemand.

2) A version without dock support.
[Galaxy S I9000 Android Development] mdv53:
@stratosk: Have you look at the headset feature? That when i use my headset the ringtone sound you can hear in my headset and not anymore on the phone speaker?
[Galaxy S I9000 Android Development] stratosk:
Yes, I looked at this with no luck.

But after a second though I don't know if this is very useful.

Suppose your forgot to remove the headset from the phone. Then you will never hear the ringtone.
[Galaxy S I9000 Android Development] darckengel:
There is a difference in newmails patch between 1.8.2d and 1.9.0beta: the way the OC freq is handled on screenstate switching...
[Galaxy S I9000 Android Development] stratosk:
Did you install JVT over 2.3.3? I remember similar issues when I upgraded from 2.3.3 to 2.3.4.

So, I always make a clean install changing ROM version.
[Galaxy S I9000 Android Development] stratosk:
Yes, you are right. I forgot about this. :)

But this is only a variable holding the latest max scaling frequency before suspend and restoring this during resume.
[Galaxy S I9000 Android Development] jocke_lulle:
Yes that is correct! I didnt try 1.9.0test2 (but GreenSGS did) as i tried the 1.9.0bm, but still you are correct about the reboot (I had this on 1.9.2bm too). Maybe i should test 1.8.2d with script a little more before I flash a new testversion just to be sure it works well?

No, i didnt install jvt over 2.3.3.
[Galaxy S I9000 Android Development] PatcheZ:
+1 for random freezes/reboots in both 1.9bm AND 1.9

1.2 ghz, noop, ondemand, no uv, default lmk setting

galaxyrom v7

sorry, too lazy to test the freezing as it's very inconvenient to have a frakked phone when you really need it working (eg. the 2 times it froze on me when using 1.9bm)

back to 1.82 for me as well.
[Galaxy S I9000 Android Development] GreenSGS:
I am still on 1.9.0 b,no reboot yet.trying many things to get one.

Edit: I was checking,.messages there I see,that I already had one with 1.9.0b.

Edit 2: I did test 1.9.0 test2, had reboot. Only 1.8.2 is without issues.
[Galaxy S I9000 Android Development] HM.Carbide:
Yes, 2.3.4 over 2.3.3.

Not really a problem, but it took longer than i thought originally.

Only wanted to figure out if it could be rom related.

But it seems not to be the problem.
[Galaxy S I9000 Android Development] stratosk:
Test version 3. newmail's patch excluded.
[Galaxy S I9000 Android Development] xenon_bn:
If i have JVT_1.8.2 can i install JVT_1.9.0 ? Can i overwrite 1.8.2 ?
[Galaxy S I9000 Android Development] stratosk:
Of course you can do this. Just flash it.
[Galaxy S I9000 Android Development] Steephig:
Got some random reboots as well unfortunately. Happens while phone is asleep, asleep while playing MP3's and while actively using it.

Using SIO and SmartAss2 on BigMem.

Some mild UV, -150 for 100MHz, all others -50. First I thought the reboots were related to too low voltage, but don't think so any more. Happens now at voltages that were stable before.

I have a feeling 1.8.2 had less reboots, but I can't quantify that.

Updated with stock JVT with full BL from Froyo.

Then updated to DocRom from Romkitchen JVT.
[Galaxy S I9000 Android Development] DocMarc73:
As long as you undervolt or overclock, there's no logic to blame it to the kernel. It has been often repeated: check without oc or uv! Otherwise those posts are useless!

No offend.
[Galaxy S I9000 Android Development] Steephig:
No offence taken.

However, I'm not blaming anything, only stating my findings. And that's why I added that previously those voltages were stable.
[Galaxy S I9000 Android Development] stratosk:
I agree with DocMarc73 about undervolting. -150mV at 100MHz. I wouldn't say that this is so mild.

Start with no uV at all. IF it is stable then start to decrease uV settings.

As I said in previous post newmail's patch changed the behavior of frequency states. So, your old settings maybe not stable.

In my opinion 1200MHz should be stable in 90-95% of devices. But in all version I had reports about instabilities in 1200MHz.

We examine the case that some people was stable in 1200Mhz in 1.8.2 and not in latest version.
[Galaxy S I9000 Android Development] kaynpayn:
Hey, love this kernel, everything works as it should except one thing, BLN and text messages.

I'm on stock jvt, flashed semaphore (first 1.9.0 and much later 1.8.2) and installed bln free from market. Also converted to ext4 with suggested app.

Used handcent and bln used to work randomly. Sometimes it would light up but sometimes it would do nothing.

Thinking handcent might be the culprit (has similar issue with cm7) i uninstalled it but got worse with stock messaging app - won't work at all. Same with go sms pro.

It does work, however if I test it from inside the bln app.

I've searched a bit around this thread, I even tried replacing the lights.s5pc110.so file as suggested in this thread a while back, but no go.

Any ideas? Thanks in advance.
[Galaxy S I9000 Android Development] stratosk:
Hi,

BLN does not work on stock SMS unless you use some fixes (services file).

Please flash the attached file. It's for odex (stock is odex) roms

Edit:

lights.s5pc110.so is replaced by the kernel. You don't need to do this.
[Galaxy S I9000 Android Development] kaynpayn:
Thank you for such a quick reply, that worked perfectly.

Sorry to have bothered you over such a quick and simple fix. :)

Amazing work mate, as always :)
[Galaxy S I9000 Android Development] jna9000:
I hav eto correct that after using 1.9.0 for 4 or 5 days now my battery lie has rised a lot.

Changing every night (I use my phone as an alarm clock), I have around 50% at night, which is much more that I had before.

Today, I stopped charging at 6 a.m, and used the phone quite heavily (Apps as well as calls), and now - >17hrs later - I'm still at 48%. That is great! Thank you Stratosk for tjis great work!
[Galaxy S I9000 Android Development] djb77:
Hi, just a couple of quick questions / suggestions regarding ClockWorkMod in this kernel.

- Is it CWM2 / CWM3 compatible? Havent seen any info about this

- Is it possible to remove all the "no" options in wipe cache / wipe data, and just have one?

Thanks :)
[Galaxy S I9000 Android Development] Bogie1:
@Stratosk, first of all I would like to tell you that you build an Awesome Kernel. I have been running it now for at least a week or more now and it's really amazing, Thank you for all your efforts. My phone is very stable with no SOD's or random re-boots at all.

This may be a stupid question (also I guess I should have ask in your captivate section) but I am going to ask it anyway lol. I am running Mosaic 8 (JVT 2.3.5) from The Collective on my Captivate and I too have been having BLN issues (not working at all). I use Handcent and Go SMS Pro. I see you said that this was for odex (stock roms) but do you think it would work on my system? Would it mess up anything else? I am fairly new to this so, please forgive me for this newbe-ish question.

My set up is:

1200 (no uv)

Smartass V2

No-op

LMK 60 (from Thunderbolt)

SD-Card read ahead 1024 (Thunderbolt)

i9000 remount script at start up (Thunderbolt)

S98CFSStock at start up as well (Thunderbolt)

Thank you and keep up the Great Work!!!
[Galaxy S I9000 Android Development] GreenSGS:
:( reboot on test 3. Its worst than 1.9.0b. More frequent reboots.

Back to 1.8.2.
[Galaxy S I9000 Android Development] jocke_lulle:
I also had reboots with test3. one last night opening messages and one this morning listening to music and reading document with thinkfree office :(
[Galaxy S I9000 Android Development] Sys81:
Wads the diff between normal one and with bm one?
[Galaxy S I9000 Android Development] stratosk:
Thanks for your feedback.

This fix works only on odexed roms. I'm sorry if mosaic is an odexed one. If yes, I think it should work. If no, you may search this thread there is also a fix for deodexed.

Please be sure to have a backup because flashing this.
[Galaxy S I9000 Android Development] stratosk:
With bm you get 353MB available RAM but it breaks 720p video recording. That's the only difference.
[Galaxy S I9000 Android Development] darckengel:
@stratosk:

As the last stable is 1.8.2d maybe we can use it as base test and add the 1.9.0 features 1 by 1 till it begins to cause the reboots (and first adding the oc support to get rid of the screenstate script)
[Galaxy S I9000 Android Development] Bogie1:
Thanks for the reply. I will search and see if I can find it. What's strange (I forgot to mention this earlier) is that BLN works for missed calls and when I test the Led Notification within the BLN app it works. I guess it might be something in the messaging apps that is not allowing it to work as well. Anyway, thanks again for the reply.
[Galaxy S I9000 Android Development] stratosk:
This is normal. BLN does not work with stock SMS until you install these fixes.
[Galaxy S I9000 Android Development] stratosk:
Yes, maybe this is a good idea. I'm not quite sure if I can easy roll back all the changes to 1.8.2d.

I wish I had a device with these symptoms to examine the issue.
[Galaxy S I9000 Android Development] pikachu01:
stratosk, could it be due to Linaro GCC version? Or mistakenly using the Captivate build options?
[Galaxy S I9000 Android Development] darckengel:
Yes it's very annoying as the main new features are not the cause of the problem ..

I don't know how github works, but if it handles versionning it should be able to gives you a 1.8.2 version of the source code which it could be used as base test.
[Galaxy S I9000 Android Development] PIRATA!:
Ok guys... I was using Semaphore 1.8.2 with Darky 10.2.2 and it was just great: more smooth and better battery life!!

Now I'm on Ficeto's JVT that self installs with DarkCore 4.1...Abba I have to say that the phone was quite smooth and with not bad battery life...

I say "was" because now I am with Smartphone 1.9.0 and it is smooth the DarkCore...but it is bad in Barry life!!!

Settings in the Semaphore script app are the same as those I was using with 1.8.2... Recommended settings with Net support for wifi...nothing else!!!

Any suggestions???

Ps: to revert back to DarkCore, should I disable the Semaphore scripts (and how do I do it!!) so to not interfere with the other kernel??
[Galaxy S I9000 Android Development] kg3:
Currently running smartassv2 and simple i/o (everything else in semaphore is stock), and was playing Pro Evo Soccer 2012 when the phone got home and was lagging bad during gameplay until the screen went off and the phone was unusable. Had to pull the battery. Anyone had this issue? Is conservative and SIO a good combination for performance and battery?
[Galaxy S I9000 Android Development] darckengel:
For gaming, you should try bm version with on demand. On demand still have good battery life no need to go on conservative.
[Galaxy S I9000 Android Development] danieldmm:
Using Semaphore 1.9.0+ThunderBolt 2.1.3, no problems so far. Its like a gluve in my Rom RV3. My and the users that already downloaded have no issues. Before say that its Kernel Problem please check if its not ROM PROBLEM. Loosing 3% battery at night its aceptable. Big Thanks Strastosk for the version 1.9.0, i think its the best kernel you have made...

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] stratosk:
I use the same linaro toolchain since 1.8.0

If there was problem with captivate changes we will have problems all of us. And all changes for captivate are conditionally compiled.

Anyways, I will try to build more test versions to investigate this.
[Galaxy S I9000 Android Development] jocke_lulle:
Thanks for really listening to our problems! But i want to say to you: I can live with this problem as oc is not a must for me. It is probably a lot of work for you and especially when only a few of us seem to have this problem. So I hope you dont sacrifice to much of your time trying to fix :) Thanks again.
[Galaxy S I9000 Android Development] stratosk:
I spent most of my free time since June to this kernel. So, no problem.

The main problem is... me. :) I WANT to know what causes this issue? I don't mind if I can't fix it. But at least I want to know.
[Galaxy S I9000 Android Development] GreenSGS:
That's why semaphore is top kernel.

I am also back on 1.8.2.will move up again when I install a clean ROM.

BTW, semaphore app is also changed from 0,5 to 0,6 version,Is anything there to check.wild guess.
[Galaxy S I9000 Android Development] logpc:
Since i wiped dalvik cache and cache partition, i don't have no more reboot since yesterday with 1.9.0 (1200 MHz, ondemand/noop).
[Galaxy S I9000 Android Development] darckengel:
Interresting.

But i suppose that greenSGS and jocke_lulle also did it when they tested the kernels?
[Galaxy S I9000 Android Development] GreenSGS:
No I didn't clear cache before only dalvik cache removed,just did and flashing 1.9.0 again,let see.
[Galaxy S I9000 Android Development] darckengel:
I doubt that cleaning cache really changes anything, the main one is dalvik.

If you did it, i think you will have the same results.
[Galaxy S I9000 Android Development] GreenSGS:
Ah, no hope then but I wait anyways.

1.8.2 works like a charm.
[Galaxy S I9000 Android Development] PIRATA!:
......you are on JVT with Semaphore 1.8.2 ?!?? Isn't it incompatible???

I am on Ficeto's JVT with Semaphore 1.9.0 and don't have any reboots or lags.....only some extra battery drawing that I hadn't when on DarkCore 4.1 that came with rom.....but for the other features and speed Semaphore is still n.1!!

Why don't you guys put DarkCore and convert file system with that, and then put Semaphore on a rom that was using previously DarkCore?? I have tried Semaphore 1.8.2 and 1.9.0 and never had instability problems.....

Only thing much more battery drawing with last Semaphore 1.9.0 then 1.8.2...
[Galaxy S I9000 Android Development] stratosk:
1.8.2 was also built with JVT's initramfs. Anyway Semaphore kernel generally is compatible with all Gingerbread versions.

About battery, let it complete a few cycles charging/discharging.

You may also convert you filesystem to ext4 using chainfire's ext4 application.
[Galaxy S I9000 Android Development] GTRSkyR34:
I have 1.8.0 on Darky 10.2.2, wich should I update 1.9.0 or 1.8.2? Wich is better?
[Galaxy S I9000 Android Development] stratosk:
In my opinion 1.9.0 is better. :)
[Galaxy S I9000 Android Development] milro1970:
Problem: Always reverts to OnDemand Governor

Hi.

Semaphore is great.... Great performance, great battery life and, best of all for me, i can use it for days without performance drop and thus no need to reboot the phone... But, I have one problem: whenever i try to set a governor other than OnDemand, the phone always reverts to OnDemand. This happens after the display turns off (automatically or manually). When I turn it back on the governor is set back to... OnDemand! I observed this behavior when I was on 1.5.1 version of semaphore and the same happens now that i am on 1.9.0.

...I am on Simplicity 1.5.1 ROM
[Galaxy S I9000 Android Development] stratosk:
Hi,

How do you check the governor is used?
[Galaxy S I9000 Android Development] darckengel:
Remove your screenstate scaling script from init.d directory
[Galaxy S I9000 Android Development] ZaneZam:
Aye! The best evaar! :) Thx 4 that!

Btw. I'm running 1.9.0bm since you released it w/o problems. Ondemand/sio no oc/uv + thunderbolt 2.1.3 + cleared cache/dalvik after install as this is my habit since my froyo/speedmod times. ;)

Guess i have to try oc to needle this rebootdevil, will let u know if something bad happens. Ticking oc 1200 now... ;-)
[Galaxy S I9000 Android Development] flolep:
Yes. Or edit it to have the governor you want in awake mode...

To have more info, I suggest you to go grab some information in Thunderbolt pikachu's thread...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] flolep:
Yeah, I want to "needle" it too.

I remember when I first flashed 1.9, I put smartassV2 and sio and had overclocked from 800 MHz min to 1200 mhz max.

And I remember that this configuration wasn't stable for me as I had what we can call "reboots" or "freezes" after some time of use.

So I went back to the good ole combo ondemand + noop and since then, no reboot nor freeze anymore...

I didn't take these reboots very seriously and just thought there was a problem in the configuration with the linked variables oc, uv, governor, scheduler.

But as I see people having the same troubles here, it makes me curious to see if it happens again if I put back smartassV2 and sio.

That's what I did so I will report if I have a reboot.

In the meantime, thanks again stratosk for all your work... This kernel is really awesome, performance, battery and stability wise...

Take care.

+ +

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Silver-Hawk:
Hi

I'm still relatively new to using kernels other than the ones bundled with the ROM's...

I've been using CF ROOT kernel (v3.7, JVP based) for a long time now, and wanted to try out Semaphore now..

Can I flash this JVT based Kernel on my current JVP based ROM safely?? :confused:
[Galaxy S I9000 Android Development] sbnaul:
Yea... U can flash..
[Galaxy S I9000 Android Development] jdogzilla:
Unmounted my SD card and drag/lag has more-or-less gone. So I'm not sure that it had anything to do with the ROM, since previous other ROM also would give me a drag after a few days. Thanks anyway :-)
[Galaxy S I9000 Android Development] PIRATA!:
Mmmh..I think that completing a few battery cycles charging/discharging as you say doesn't fuzz the gap!! I have to charge my phone twice a day and I'm in this situation since a week our so...... Any suggestion?

I'd like to revert back to another kind of kernel just to see if it is really a problem with my installation of my Semaphore 1.9.0......so should I empty the /system/etc/init.d folder from the Semaphore scripts???

---------- Post added at 09:40 AM ---------- Previous post was at 09:35 AM ----------

I missed the part where you guys say that the BM version is better because released without problems....!!!! What is this all about???

Other thing.....what is this "thunderbolt" you guys some time mention???

EDIT!! ah...it is a package of scripts... But are they compatible for using WITH the Semaphore scripts??? Aren't there any double repetition in some scripts that mess one with the other???

Please let me know because I'd like to try this Thunderbolt!!

Thank you.

---------- Post added at 09:54 AM ---------- Previous post was at 09:40 AM ----------

Ps: in the Semaphore script app UPDATE1 that is downloadable from the related thread, I read in the changelog that default kernel scheduler seems to be smoother than chainfires settings.....but is it also more unstable or what?? Is it good to give it a try?? In my case of battery drawing, when I was on Semaphore 1.8.2 using Recommended, the scheduler was default on chainfires.....

Could this option be related to some how of battery drowning problem???
[Galaxy S I9000 Android Development] hackeron:
Learn som forums manners pls. Why do you have to type ???? and !!!! after every question.. And all the answers is available if you can use your eyes and the search function..
[Galaxy S I9000 Android Development] darckengel:
You may have a problem with your sd card...

Try to reformat it and make a checkdisk.

---------- Post added at 11:03 AM ---------- Previous post was at 10:15 AM ----------

Twice a day... your problem is not kernel related, you should have some apps which avoid the phone to go into deep iddle state, check your battery stats to see what process drains your battery, use betterbatterystats to check wakelocks.
[Galaxy S I9000 Android Development] ZaneZam:
+1
[Galaxy S I9000 Android Development] danieldmm:
I me serving My RV3 blunded with Semaphore 1.9.0 with ThunderBolt 2.1.3, no issues at wall, my phone is responding great and battery it's great.

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] vladbaca:
I'm currently running Simplicity 1.6.1, with normal semaphore 1.9.0 (JVT) kernel. Everything's fine and dandy, except for the Mobile AP tether.

I have enabled the semaphore netfilter modules, but whenever I start up the mobile AP and try to connect with my laptop to the created network, it either hangs (without really connecting to the AP) or connects, but with limited internet access. The USB tethering works fine, however.

So what am I doing wrong? Mobile AP used to work when I was on DarkyROM so it must be a ROM/kernel problem. Might there be any conflict between semaphore and simplicity? (note: I've tried enabling mobile AP with the netfilter modules disabled; it gives me an error in this case)
[Galaxy S I9000 Android Development] darckengel:
Can you try cleaning busybox via the semaphore app please.
[Galaxy S I9000 Android Development] yoghi90:
green flash

when i turn off the phone's screen, i see a green flash on on the screen. This problem can be resolved changing gamma colors in default 2.3.3, but the colours become too faded. Would suffice to solve the problem of the green flash turning off the screen. According to me this is the only problem of this kernel.
[Galaxy S I9000 Android Development] darckengel:
It's for all kernel using voodoo colors,

Set colors to default stock, disable auto brightness, reboot, and after set your colors as you want and you can enable autobrightness
[Galaxy S I9000 Android Development] vladbaca:
I tried that just now. It's still not working :(
[Galaxy S I9000 Android Development] darckengel:
You have rebooted your phone?

If it doesn't work, i have no idea, i don't use this feature, but people doesn't seem to have problems with that ...
[Galaxy S I9000 Android Development] gabytzuuuz:
I have a small issue....Idon't undestand how the multitasking works and i think it's kernel related.I'm using Simplicity 1.5.1 and,for exemple,if I play Angry Brirds and I press home buton to write a message when I wont to come back in AB the app it's colosed :( . From semaphore i set to 32MB-multitasking. Android it's about multitasking.....but i can't use it.

Any suggestinons ?
[Galaxy S I9000 Android Development] Steephig:
Ok, I had missed that, makes sense.

Started from scratch and indeed no reboots anymore, but less UV now. Oh well, you get some, you lose some.
[Galaxy S I9000 Android Development] HM.Carbide:
Please look, if there are memory settings in /data/local.prop or in /system/build.prop

Also, if there are scripts in init.d, sometimes there are also scripts in /data

Some roms have memory tweaks bundled.

Guess you have one of them.
[Galaxy S I9000 Android Development] stratosk:
Have you ever had problems with DNS on previous versions?

Anyone else with the same issue?
[Galaxy S I9000 Android Development] truden:
Tethering

Tethering (Mobile AP) doesn't work with JVP_1.3.0a on JVP.

Gives Error.
[Galaxy S I9000 Android Development] hendex:
Can i flash jvq if im on jvp baseband?
[Galaxy S I9000 Android Development] stratosk:
Try to copy the attached script in /system/etc/init.d/ to load the netfilter modules.

Remove the txt extension and give the script executable permissions.