yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] FuryriderX:
Tried this, still have the problem BlockbusterF reports. BLN app is fine, but no LED notifications! It seems as if when you click the 'test' button, it automatically clears the moment you press the power button. What is this services.jar that was also mentioned? Is it required? Its not in res/misc
[Galaxy S I9000 Android Development] BlockbusterF:
OK I've got it working know. Manally installed the liblights and deactivatet the scheduler in BLN app.

The second was stupid by me :D

Now BLN works. Thank you very much for this kernel. My device also works at 1.2GHz without a problem.
[Galaxy S I9000 Android Development] pikachu01:
This needs to go in the development section once TS has enough posts.
[Galaxy S I9000 Android Development] dmatusek76:
Can i use Pimp My Cpu for oc/uv ?
[Galaxy S I9000 Android Development] stratosk:
You may try it and send us your feedback.
[Galaxy S I9000 Android Development] stratosk:
No, it is not included in the kernel's initramfs.

According to Neldar:

"The modification of the services.jar gives only a better compatibility with some apps."
[Galaxy S I9000 Android Development] stratosk:
New update that resolves the lights.s5pc110.so installation issue.

No need to update of you don't have problem with the BLN.
[Galaxy S I9000 Android Development] allotrios:
thanks patrioti

i hope you are not paok :P
[Galaxy S I9000 Android Development] stratosk:
Unfortunately I am PAOK ;)
[Galaxy S I9000 Android Development] allotrios:
boooooooooo :P
[Galaxy S I9000 Android Development] Vampiro2000:
Everything works except BLN for SMS... What can I do?

Thanks
[Galaxy S I9000 Android Development] FuryriderX:
Are you using the stock messaging app? Enable the LED notification. Then it should.

Otherwise, download sms notifier from the market and use the LED notifications from it (thats what i used to have to do)

EDIT:

Downloaded the 1.0.1 kernel, installed with Neldar flasher - BLN Pro reports enabled, good - disabled scheduler, but still didnt see lights when i clicked 'test notification'. BUT - after i enabled blinking, it worked! I disabled the blinking and it still kept working.

THANK YOU!!!

....now if only you could dig out the 340mb of ram that the other developers have somehow found haha
[Galaxy S I9000 Android Development] caravagio:
lagfix

can i install this kernel if i have lagfix installed?
[Galaxy S I9000 Android Development] dmatusek76:
still no luck with bln control free, olny Pro version is working
[Galaxy S I9000 Android Development] fenerbuuh:
thanks for the kernel, working good with bln pro
[Galaxy S I9000 Android Development] aahz123:
Tried pimp my cpu and it worked just fine. The following settings were completely stable for me.

1200 Mhz - 1250mV ie -25mV

1000 Mhz - 1225 mV ie -50mV

800 Mhz - 1150 mV ie -50mV

400 Mhz - 975 mV ie -75mV

200 Mhz - 875 mv ie -75mV

100 Mhz - 850 mV ie -100mV
[Galaxy S I9000 Android Development] stratosk:
I don't think that you will have problem.

But make a backup before, just in case.
[Galaxy S I9000 Android Development] hellfirez1714:
This kernel supports JVP?

thanks.
[Galaxy S I9000 Android Development] stratosk:
I didn't test it yet...
[Galaxy S I9000 Android Development] stratosk:
This is quite weird... As you mentioned in your previous post the problem was in the cf-root initramfs.

After many tests, I realized that something goes wrong in a chainfire's script that do some 'setprop'. I just remarked some of them and the problem 'magically' resolved. At least for me in stock rom.

There is a problem with wifi and BT for some people using custom roms but I believe that it is not related.
[Galaxy S I9000 Android Development] KiRAdot47:
so, planning on any new improvements?
[Galaxy S I9000 Android Development] habylab:
Read his post, said he is preparing something interesting.

Sent from my ever changing Galaxy S
[Galaxy S I9000 Android Development] ktuluz:
I am on stock deodexed rom and still have bt issue. Not sure whats going on.
[Galaxy S I9000 Android Development] stratosk:
New test version (JVP_1.3.0a).

The basic idea behind this version is to compile many features as modules.

The result is smaller footprint in memory and (I think) faster kernel.

Scripts need to be done to enable some functionality. For example to enable/disable netfilter or logcat. But you can always load the modules through a terminal emulator.

Use this version only for test
[Galaxy S I9000 Android Development] habylab:
Oohhhh sounds great. Hopefully this will be awesome! Recommended Juwes memory script or not?

Sent from my ever changing Galaxy S
[Galaxy S I9000 Android Development] MasterJam882:
Do I understand this correct?:

New kernel has differnent modules for differnet functions.

So I can decide what function I need and load my modules?

For example if I want ur kernel so bad because of stability and OC/UV but don't need BLN?
[Galaxy S I9000 Android Development] stratosk:
Sorry, I didn't try Juwes memory script. I always want 'clear' phone to test the capabilities of the kernel. Please try it and send us feedback.
[Galaxy S I9000 Android Development] stratosk:
At this moment only the functions I mentioned in the first post.

For example I noticed that all kernels (including mine before this version) support extended netfilter support (firewall) that is needed only in large servers. I don' t use firewall in my phone. It's just a phone. But anyway if you want to use it you may load the modules. ;)

For the OC/UV and BLN you have to enable it to use it anyway.

In the future I will examine more parts of the kernel that could be build as modules.
[Galaxy S I9000 Android Development] ktuluz:
1.3.0a Seems to have fixed the issues i was having starting BT, BT working.. wifi also working at same time. CIFS working.. havent tested GPS. but the system itself (responsiveness) seems really Smooth. Thanks for the Work Put into this Kernel. Running well atm.@ 1200mhz no UV

cheers
[Galaxy S I9000 Android Development] MasterJam882:
@stratosk

just wanted to ask what u think about this whole smartass cpu governor?

Do u think it's a gd thing and considering to bring it in ur kernels or do u think it's a waste of time?
[Galaxy S I9000 Android Development] Rootax:
I love the idea of modules.

Do you think, in later versions, that modules could be enable/disable via a GUI ?

Thx a lot :)
[Galaxy S I9000 Android Development] minishe:
Excuse me, can I use this kernel to replace the talon kernel by ODIN?
[Galaxy S I9000 Android Development] theos0o:
Yes, you can.
[Galaxy S I9000 Android Development] klaona:
JVP 1.3.0a

JVP_1.3.0a works great until now. Very fast quadrant <2750 :)
[Galaxy S I9000 Android Development] MasterJam882:
Just wanted to push a lil bit that 2.3.4 JVQ was just leaked.

Maybe u take a look ;-)
[Galaxy S I9000 Android Development] habylab:
1.3 is great, but please add back conservative scaling as it is much better for battery I find. Maybe look at smartass governor too?

Sent from my ever changing Galaxy S
[Galaxy S I9000 Android Development] stratosk:
I didn't have the opportunity to to try it. Maybe I will.

But I trust the standard linux kernel code (ondemand, conservative) which works on million systems. On the other hand there is always space for something new.
[Galaxy S I9000 Android Development] stratosk:
Yes, this is a way. Or maybe with boot scripts.
[Galaxy S I9000 Android Development] stratosk:
You could try this (untested)

Create an init script (put it /system/etc/init.d) with the following:

#!/system/bin/sh

insmod /lib/modules/cpufreq_conservative.ko

echo conservative >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 10 >/sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

echo 40 >/sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold

echo 90 >/sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold

echo 0 >/sys/devices/system/cpu/cpu0/cpufreq/conservative/ignore_nice_load

This should load module and set the conservative cpu governor with the same chainfire tweaks.
[Galaxy S I9000 Android Development] Rebel2k:
Hum, I would rather say: hardcore thinks it comes from there but he's trying to find out the exact reason. It might be not related with that at all!
[Galaxy S I9000 Android Development] stratosk:
Yes, sometimes. When I am not so bored. :) (because I usually flash test versions)

I use 25,25,25,50,75
[Galaxy S I9000 Android Development] stratosk:
Do you mean from MDNIE or from compiler flags?

Anyway he knows better than me. :)
[Galaxy S I9000 Android Development] jocke_lulle:
Just wanted to tell you that I have never experienced any black screen with semaphore kernel=) ive been using it since v1.6.

Before that I used speedmod but then I had some black screens.

I just wanted you to now that for me this kernel works great!

Thank you
[Galaxy S I9000 Android Development] Rebel2k:
I was speaking of MDNIE. And generally, he's searching for the guilty code portion at the moment as he's done several versions in order to fix it those last days. Hope he will definitely find what is not perfect for everybody to profit of it! :)
[Galaxy S I9000 Android Development] $omator:
well i can add that it was happening diring i think all gb firmwares till jvs and stopped on jvt - samsung devs seems to pinpointed that one bug :)

(leaveing phone fc aside:)
[Galaxy S I9000 Android Development] stratosk:
Yes, I hope that too! And I think he will. :)
[Galaxy S I9000 Android Development] stratosk:
It never happened to me. I thought it was kernel related.
[Galaxy S I9000 Android Development] $omator:
well i am well known for not flashing custom kernels (cfroot)

and spotted that several times on every single one - was a rare but still happened

sometimes while i was still on not touched device waiting on chainfire to push updte for particular kernel

well maybe it will strike me now on jvt but it was quite some time since flashing and still no problem
[Galaxy S I9000 Android Development] stratosk:
Do you mean that you had BSOD on cfroot?
[Galaxy S I9000 Android Development] $omator:
and on not cfrooted also
[Galaxy S I9000 Android Development] ZaneZam:
And leaving the charging bug aside! ;-)
[Galaxy S I9000 Android Development] HM.Carbide:
Which launcher do you use?

Which lockscreen do you use?
[Galaxy S I9000 Android Development] $omator:
touchwizz3
[Galaxy S I9000 Android Development] stef_ladefense:
hi,

is there a version of busybox installed with this kernel? if so what version?

If update it, before I put SU or Busybox?

thx

Stef
[Galaxy S I9000 Android Development] stratosk:
hi,

yes, busybox 1.16.2. Su and superuser application are also bundled with the kernel.
[Galaxy S I9000 Android Development] stef_ladefense:
thx

ok, busybox is in /sbin ?

in my cwm script there "set_perm_recursive(0, 0, 0755, 0644, "/system/app");"

and once I go to "system / app", no change permissions ??
[Galaxy S I9000 Android Development] $omator:
o dear god, IT DOES WORK. maybe you not monted to write ? =)
[Galaxy S I9000 Android Development] stef_ladefense:
with this ?

"run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/stl9", "/system"); "
[Galaxy S I9000 Android Development] $omator:
'whatever fuels your engine' _recursive is essential in you earlier posts

this means like i said you already everythin within /system/ directory tree including /app/ also

why you cant make it work is beyond my understanding :)

you have working script you break it ;d
[Galaxy S I9000 Android Development] Jackmax32:
The lowest brightness on this kernel is not as bright as it is on Darkcore n Galaxian..

But its the best except for the brightness part..

Could u plz do something about it on ur nxt release..Jst a little request..
[Galaxy S I9000 Android Development] stef_ladefense:
the only change is the mount method !

i use : "run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/stl9", "/system"); "

and not work for change permissions

but your is ok : "run_program("/sbin/mount", "/system");"

sorry for this

Stef
[Galaxy S I9000 Android Development] rmean:
Use voodoo control to adjust display properties ;)
[Galaxy S I9000 Android Development] mmjuban:
latest on JVQ

Can I safely use that latest kernel JVT_1.8.0 on a stock JVQ ROM?
[Galaxy S I9000 Android Development] XuperLugia:
Yes you can :)
[Galaxy S I9000 Android Development] LordVetinari:
BSOD

I have no idea if the Black screen of death is related to custom kernels, but I get one at least once a day, some times 2 to 3 times a day. I rarely got it on pre-Semaphore 1.8 kernels and I can't say that .8 caused it because the BSOD started becoming more frequent after my phone started experiencing the Android OS battery drain and I had to do a full wipe / clean & reinstall.

Attached is a screenshot from BetterBatteryStats after BSOD. I don't know how to get a logcat log with the screen off.

So all I can say for certain is I get the BSOD a lot. I'm currently downloading the newly released XXJVT. I hope that it would fix my issue but I'm not holding my breath.

Let me know if you need me to test anything.

Thanks,

LV.
[Galaxy S I9000 Android Development] pikachu01:
jbd2 seems to be a swap/journaling related process:

http://askubuntu.com/questions/3019...d-jbd2-sdb2-8-from-causing-gui-unresponsivene

Seems to be the same issue here.
[Galaxy S I9000 Android Development] snipke:
How can i remove the semaphore kernel, i flasht other kernel but in my apps the semaphore is still dare.

Grtz
[Galaxy S I9000 Android Development] LordVetinari:
Sigh. I've just gotten another BSOD with XXJVT. I'll try to do an ADB session...
[Galaxy S I9000 Android Development] pikachu01:
Try looking at your BetterBatterystats to see if jbd is indeed using up a lot of battery (hence it getting stuck and consuming a lot of battery)
[Galaxy S I9000 Android Development] LordVetinari:
Indeed. Top says:

CPU: 0.0% usr 100% sys 0.0% nic 0.0% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 3.00 3.01 2.59 2/525 5005
←[7m PID PPID USER STAT VSZ %MEM %CPU COMMAND←[0m
75 2 root RW 0 0.0 99.2 [jbd2/stl10-8]
566 91 system S 240m 68.0 0.2 system_server
5005 5000 root R 1660 0.4 0.2 /sbin/ext/busybox /sbin/top
682 91 radio S 181m 51.5 0.0 com.android.phone
740 91 app_13 S 166m 47.3 0.0 com.google.process.gapps
1586 91 app_80 S 162m 46.0 0.0 com.whatsapp
1492 91 app_79 S 159m 45.2 0.0 android.process.acore
1553 91 app_49 S 159m 45.1 0.0 com.android.vending
2033 91 app_102 S 158m 44.8 0.0 com.google.android.apps.plus
2187 91 app_90 S 155m 43.9 0.0 com.google.android.apps.maps
1631 91 app_90 S 154m 43.7 0.0 com.google.android.apps.maps:NetworkLo
854 91 app_9 S 151m 42.8 0.0 android.process.acore
4777 91 app_98 S 149m 42.4 0.0 com.asksven.betterbatterystats
1855 91 app_82 S 147m 41.9 0.0 com.latedroid.juicedefender
678 91 app_30 S 144m 41.0 0.0 com.swype.android.inputmethod
662 91 system S 143m 40.7 0.0 com.android.systemui
683 91 app_34 S 140m 39.9 0.0 android.process.media
3492 91 app_9 S 139m 39.6 0.0 com.sec.android.provider.logsprovider
1780 91 system S 139m 39.4 0.0 com.android.settings
^C023 91 app_113 S 138m 39.4 0.0 com.google.android.apps.uploader

I probably can't kill it. *Thinks*
[Galaxy S I9000 Android Development] Ashtrix:
Do we have CM7/MiUi support :rolleyes:..!?
[Galaxy S I9000 Android Development] pikachu01:
What tweaks that you enabled in your Semaphore kernel?

Any external tweaks like Juwe's RAM script or ThunderBolt!?

Any tweaks in using the tweaks app or HM.carbide's Semaphore app?
[Galaxy S I9000 Android Development] dani_z:
unfortunately not :rolleyes:
[Galaxy S I9000 Android Development] LordVetinari:
I only have 50MB Cache enabled. Logger and Netfilter also, of course. Not Juwe's RAM script or Thunderbolt.

I'm looking through the logs now. I managed to do a logcat and bugreport, so lets see...

LV.
[Galaxy S I9000 Android Development] pikachu01:
Hmm, if that's the case, what is your lagfix configuration?

Are you using ext4 all the way or ext4 on /data /dbdata and /cache, while /system is rfs?

Or are you using rfs completely?
[Galaxy S I9000 Android Development] LordVetinari:
I'm using ext4 on all the filesystems. I can try and run on rfs for a day or two and check if it still happens?

LV
[Galaxy S I9000 Android Development] Ashtrix:
well that's sad....:mad:.!

So, all ROM's other than CM7 and MiUi have support am i right ??...!
[Galaxy S I9000 Android Development] pikachu01:
Please do. Awaiting your results :)
[Galaxy S I9000 Android Development] Difusal:
HI!

any improvements with the WIFI problem (constant reconnections) in JVS and JVT? Is it kernel related or not?

Thanks
[Galaxy S I9000 Android Development] stratosk:
Hi,

This problem is not kernel related. I can reproduce it on stock kernel too.
[Galaxy S I9000 Android Development] stratosk:
Can you please check the space left on /dbdata partition?

I think you will not have problem on rfs with jbd2. jbd2 is ext4 related.
[Galaxy S I9000 Android Development] malcho:
BSOD yes it happens to me butt only after flash new rom.I mean every new flash(JV...)I had one bsod on semaphore on first day butt after that nothing.

BSOD happens to me also when i flash some custom theme butt that's rare.

I don't know.Maybe some badly written app causing this.
[Galaxy S I9000 Android Development] Difusal:
Thanks! So we'll just have to wait for JVU or ICS and pray for the problem to be fixed in that update, right?
[Galaxy S I9000 Android Development] stratosk:
Actually it does not happens to everybody and as a workaround you can use static IP in your phone (this is what I do).
[Galaxy S I9000 Android Development] Difusal:
I think I'll just wait since I'm good with JVQ until there is a fix. The blue glow effect and page loop aren't things I can't live without
[Galaxy S I9000 Android Development] corgar:
for who got bsod can i ask what launcher you use? Launcherpro is still bugged and cause a lot of bsod.
[Galaxy S I9000 Android Development] ZaneZam:
Or if you have the possibility you can set the router's dhcp lease time to < infinite, that worked for me.
[Galaxy S I9000 Android Development] :
Use root explorer or file expert or similar and delete /system/app/Semaphore.apk

tapatalked...
[Galaxy S I9000 Android Development] s3icc0:
Noticed that the semaphore app is changing screen orientation even when i have automatic orientation off....
[Galaxy S I9000 Android Development] HM.Carbide:
Thanks for report, i will check this for next version.
[Galaxy S I9000 Android Development] LordVetinari:
According to Ext4 Tool i Have 122.6MB free on /dbdata. I'm on RFS now, so for Ext4 it might be *slightly* different.

I'm using Go Launcher Ex. If I still get any BSODs with RFS, I'll try TW Launcher.

LV.
[Galaxy S I9000 Android Development] demonstone:
I use Go Launcher EX too, and I have had 2 BSODs yesterday... hmmm... ¬¬ suspicious, I have never had it while using TW3
[Galaxy S I9000 Android Development] vasilp:
I have JVS_1.7.5 currently on my phone and works perferct.

I want to update to 1.8, is it safe to flash JVT_1.8.0 version over the stock JVS ? ... I can't see the JVT firmware in the samfirmware.com website.
[Galaxy S I9000 Android Development] dani_z:
Go launcher is very RAM hungry ...
[Galaxy S I9000 Android Development] demonstone:
Indeed, and battery too... turning back to tw3.
[Galaxy S I9000 Android Development] stratosk:
Yes, it's safe to flash the latest version. I think you may find JVT on sammobile.com
[Galaxy S I9000 Android Development] malcho:
Like i said buggy apps causing BSOD.
[Galaxy S I9000 Android Development] $omator:
pre JVT firmwares without kernel/root - bsod

JVT firmware without kernel/root - no bsod

as jvt went public there will be probably latest code push soon

so all them custom kernels can go realy JVT not only 'working on JVT'

and that will fix the issue
[Galaxy S I9000 Android Development] Mangus_U*RA:
go launcher ex here and no bsod in months...

Last time I got a bsod I was using launcherpro
[Galaxy S I9000 Android Development] mialwe:
Don't know if this helps as I'm not using Semaphore but Go Launcher since Froyo days - and not a single SOD (JPY,JSD,JVO?,JVQ,JVT).
[Galaxy S I9000 Android Development] McDown:
Hey stratosk, I have a minor but annoying issue with Voodoo sound control panel. Headphone amplifier settings revert to default every time I reboot the phone. Is there config file I can set it manually so it doesn't revert by itself?
[Galaxy S I9000 Android Development] a g bell:
oops

hi,sorry if this is little of topic but just flashed 1.8BM had a busybox issue so thought lets delete the busybox not in the kernal anyway managed to delete all files in system/bin.yeah I know dumb ass,now my phone only boots into recovery mode now saying unknown volume for path[/data]cant mount cache recovery cant open cache recovery.I am guessing the only way back is to reflash a rom BUT I have used chainfires ext4 app to convert to ext4 so is it safe/ok to flash a standard rom again using odin ????MY phone does still go into download mode.
[Galaxy S I9000 Android Development] Perka:
Just flash with odin, u will end up on rfs, so yea its safe.

Edit, try flashing a no wipe custom rom first ;-)
[Galaxy S I9000 Android Development] danieldmm:
I think you must use pit file and re partition ticket, cause you may end whith boot loop if you flash stock rom and kernel, stock kernel dont suport ext4 and if you dont use the pit file you will stay in ext4...

Sorry for the english and correcte me if aime wrong.

Cheers
[Galaxy S I9000 Android Development] a g bell:
thanks for fast reply cant flash no wipe from recovery nothing works/mounts should I FLASH one of yours or stock or it wont make a diffrence.?
[Galaxy S I9000 Android Development] edmondt:
Great Kernel :) Would it be possible to improve the battery charge rate? I've been trying the GalaxyEE kernel and it does charge quicker :):)
[Galaxy S I9000 Android Development] Perka:
When flashing a stock fw with odin it will convert to rfs. ie no bootloop

Seems ut only option is to flash stock fw with odin, or hemdall.
[Galaxy S I9000 Android Development] Perka:
Ok, can you show me where you read it?

Anyway, flashing with pit will partition your internal sd card, and if you havent flashed a different pit, no need to repart.

Hope it can help some ppl ;-)
[Galaxy S I9000 Android Development] stratosk:
Thanks.

Sorry, I will not change this.
[Galaxy S I9000 Android Development] danieldmm:
Link Here

Cheers
[Galaxy S I9000 Android Development] demonstone:
Omg, thx to God... Galaxyan's dev is being burned because of this reason by some people.

Sent from nobody knows where
[Galaxy S I9000 Android Development] LordVetinari:
It's note been a day without a BSOD. Things are looking good! I'll report back tomorrow on if anything intresting happened.

LV.

--

I might be wrong. You might be crazy.
[Galaxy S I9000 Android Development] danieldmm:
Hi Stratosk, i dont now if you remember my problem with market >30 Mb and script Semaphore not working, i think that the cause was really BusyBox...

how i fix: I deleted all related with the BusyBox in mine Custom ROM and deleted in script the installation of BusyBox, flashed ROM.

Result: All running well and Script in Semaphore cache 50 is WORKING.

Cheers
[Galaxy S I9000 Android Development] stratosk:
Hi,

I guess it's voodoo control application issue. You may try to create an init script:

#!/system/bin/sh

echo x > /sys/devices/virtual/misc/voodoo_sound/headphone_amplifier_level

where

0 <= x <= 62

Please note that x = 0 equals to -57db and x = 62 equals to 5 db
[Galaxy S I9000 Android Development] gsw5700:
Hmmm, been trying RAM manager app on 1.8 bm, without kernel/ dirty tweaks, does seem to make phone more responsive, tell me what you think folks

Sent using TCP/IP
[Galaxy S I9000 Android Development] stratosk:
I don't know if he knows what he is doing (possibly yes). But I don't do changes that i don't know exactly what they will affect, in case I suspect that maybe not safe. In this case i don't know why samsung capped charging current.
[Galaxy S I9000 Android Development] stratosk:
Hi, thanks for reporting this. It seems that most issues with init scripts are busybox related. :)