yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] andip71:
Good morning,

finally found something with latest kernel version (which was also there before when I remember correctly). Not big issue, but still.

When I enter CWM, connect from PC to the phone via "adb shell", I perfectly get an adb shell.

Now when I try to become superuser by typing "su" in the adb shell, I only get an error message saying "segmentation fault". Thats it.

Can someone reproduce this as well?

And if so, is there a workaround or fix for it?

Or is it even not supposed to work at all? Hm, not sure as it might be I am already having su rights in an adb shell.

Thanks

Andi
[Galaxy S I9000 Android Development] sirbrian:
Finally no reboot since installing 1.9.1 last night.

After flashing to 1.9.1, I did a cache wipe and delvik wipe too.

No freezes, music skipping, or even reboo for the whole 1st half of the day already....UNTIL I started using Google Map (6.0) again and all hell again, freezes and reboots. I have been having this problem since last few updates of Google Map..don't know why
[Galaxy S I9000 Android Development] stratosk:
Good morning,

I haven't test it on earlier versions.

But, I also get a segmentation fault. I think this because su binary tries to 'ask' permissions from superuser.apk (maybe I'm wrong on this).

Anyway being in an adb shell from recovery run this:

~ # whoami

the answer is:

root

So, I think is OK. :)
[Galaxy S I9000 Android Development] andip71:
Thanks Stratosk.

Then I was just too stupid with what I planned to do via adb shell. I thought it might be I was no superuser. Ok, next time I will try again (when an app is going crazy again that I want to rename :-)

Andi
[Galaxy S I9000 Android Development] stratosk:
I also tested in 1.8.2.

Same results.

So, you are already root on adb shell on recovery, no need to run su before.
[Galaxy S I9000 Android Development] PIRATA!:
Ok...but what do I have to look exactly to underhand what is drawing my battery? In other words..wig do I have to settle the app and witch page shows me exactly what consumes more battery? I found the asp not that intuitive...

Thank you.
[Galaxy S I9000 Android Development] fxba77:
I came from DarkyCore 4.1 JVT with lagfix on/ext 4.... yesterday i flashed semaphore 1.9.1 with lagfix on/ext 4. After flashed it with semaphore 1.9.1, have i automatically ext 4 or i must convert it to ext4 again?
[Galaxy S I9000 Android Development] danieldmm:
No. Semaphore it's compatible with EXT4...

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] stratosk:
No, you are on ext4. No need to do anything else.
[Galaxy S I9000 Android Development] johnsin5393:
hi, stratosk.

i have a doubt on install semaphore v1.9.1.

do i need to download and install the script manager v0.62 before/after install v1.9.1?

and may i know how to use the script manager as well too?

thank you
[Galaxy S I9000 Android Development] fxba77:
if i want to change it back to RFS. How should I do that?

Thanks
[Galaxy S I9000 Android Development] danieldmm:
Use EXT4 apk by ChainFire.

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] andip71:
Again with Chainfires ext4 app.

The app can convert from RFS to ext4, but also vice versa.

Open the app, clock on convert to RFS, phone will reboot and convert back.

Just make sure you have enough free space on /system partition (at least 20-30 MB), otherwise the conversion might fail. I had that once and had to reflash everything from scratch.

Cheers

Andi
[Galaxy S I9000 Android Development] HM.Carbide:
No there is no need to download it seperately. The script manager v0.62 is included in v1.9.1.

After installing the kernel, the app is installed. Just start it, and select your preferred settings.

If you want reset to kernel default settings, there is also an option in Misc section - configuration.

If you want to overclock, please try first the test options in Misc section. They will be resetted on reboot.

If the overclock setting is stable for you, you can select the overclock option in kernel features section. Then it is permanent, even after reboot.
[Galaxy S I9000 Android Development] .:Crack:.:
Hey stratosk.

could you change the busybox to /system/xbin instead of /sbin/ ?

impossible to Update it/use some scripts...
[Galaxy S I9000 Android Development] DaRkMyk:
@stratosk I just updated to 1.9.1 and some of my videos aren't working anymore via HW decoding. It was playing fine before I upgraded.

I'll give more details when I get home.

I Swyped this on my Galaxy S

Update1: here's the Media info:

The sound works, but there is no video.

General
Complete name : Last EXILE - Ep 06 [L-E&R-B].avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 166 MiB
Duration : 24mn 24s
Overall bit rate : 949 Kbps
Writing application : Nandub v1.0rc2
Writing library : Nandub build 1853/release

Video
ID : 0
Format : MPEG-4 Visual
Codec ID : DIV3
Codec ID/Hint : DivX 3 Low
Duration : 24mn 24s
Bit rate : 840 Kbps
Width : 640 pixels
Height : 360 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.152
Stream size : 147 MiB (89%)

Audio
ID : 1
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Mode : Joint stereo
Mode extension : MS Stereo
Codec ID : 55
Codec ID/Hint : MP3
Duration : 24mn 24s
Bit rate mode : Constant
Bit rate : 96.0 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 16.8 MiB (10%)
Alignment : Aligned on interleaves
Interleave, duration : 24 ms (0.58 video frame)
Interleave, preload duration : 480 ms
Writing library : LAME3.93
Encoding settings : -m j -V 4 -q 0 -lowpass 11.8 -b 96

Update2:

I went back to 1.8.2 and the video plays fine.

Update3:

Re-flashed 1.9.1 the playback problem went back :(

Update4:

same issues with 1.9.0
[Galaxy S I9000 Android Development] stratosk:
Can you please upload the video somewhere to download it.

Also, which media player do you use?

I would be happy if you can test it on 1.9.0.
[Galaxy S I9000 Android Development] DaRkMyk:
I just updated my post, same issues with 1.9.0

I tried on MXVideoPlayer, MVideoPlayer & RockPlayer...

I'm currently uploading the vid....
[Galaxy S I9000 Android Development] stratosk:
Thanks for testing this.

I will check it and let you know.
[Galaxy S I9000 Android Development] DaRkMyk:
Here's the video:

http://www.filesonic.com/file/4069749895

just to be clear on the prob, the video does not work on HW Decoding, sound does. SW Decoding is fine on MX & RockPlayer.

Thanks

Update: Tested other videos with AVC, XVID & DivX 5 Codecs, all played well. so the issue might be only on DivX 3 codec.
[Galaxy S I9000 Android Development] DarknessWarrior:
hey guys, i bet this was answered a lot of times, but what is the best scheduler for 1.9.1: SIO, Noop or Deadline?

i get the highest quadrant score with deadline...
[Galaxy S I9000 Android Development] stratosk:
OK, I confirm this.

I suspected that was the biggest memory since 1.9.0. I found the problem. You may use the attached version with 340MB (was 341).

We lose 1MB available memory, we gain hardware video decoding in a specific video format. I don't know which is better. :)

@all

Please for your opinion about this for next version.
[Galaxy S I9000 Android Development] DaRkMyk:
Thanks stratosk,

Yap, the video is now working.. sorry for the trouble for just one video codec.

anyways, I don't think that's a big issue though, we can still use SW decoding for those ancient codecs.

That's what I get from watching old anime.. :D
[Galaxy S I9000 Android Development] stratosk:
No problem.

Anyway, it was educational. I learned something. :)
[Galaxy S I9000 Android Development] DocMarc73:
I prefer FULL functionality, regardless of available memory.

For memory freaks theres still the bm version!
[Galaxy S I9000 Android Development] andip71:
+1

I also prefer full functionality on video playback, especially because I use it alot when in the airplane. And I am flying quote often.

Good question however is: How is the BM version behaving? Does it work on BM or as well not?

Thanks

Andi
[Galaxy S I9000 Android Development] andip71:
I think there is nothing like a "best" scheduler.

Every scheduler has its pros and cons and it really is a question of personal preference and where your focus is.

I am for example a big supporter of deadline, but currently running on SIO. Noop was never what I liked, do not know why. But everyone has a different opinion, so I would recommend you run on each scheduler for a couple of days and notice the differences.

Then select the one you think or feel it is the best for you.

Some posts above there is a link posted by Stratosk that explains the technical differences.

But if someone can give you a definite recommendation I would be curious for the arguments :-)
[Galaxy S I9000 Android Development] stratosk:
OK, I think I will include this mini fix in next version. But please note that you have to search a lot to find this kind of videos (after many thousands downloads this was the first report). And you will still be able to watch them using software decoder.

But, I think I agree with you that everything must be in place. And after all we are talking for 1MB.

I also agree with Andi's post. Everyone has his taste about this.

Noop is the default Semaphore's scheduler. I use it for months and I like it because is the most simple. My second choice SIO.
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Exactly that! I never ever watched a video on my phone, still theorically I think everything should "be in place" as you said; the kernel should be as fully innocuous as possible, so my vote is:

Leave it at 340 MB with the HW decoder working (even though I'll STILL never watch a video on the phone :D)

After all... is only 1 MB :p
[Galaxy S I9000 Android Development] stratosk:
Thanks for your feedback.

Just a small correction. HW decoding IS working on most video formats. OK, DaRkMyk found (thanks!) one that doesn't work. :)
[Galaxy S I9000 Android Development] Siberian Tiger:
Thank you stratosk for your hard work,stable as rock,running stock JVT without

lagfix so smooth.:D

I want to ask you something,maybe silly,but i'd like to learn.

Why we don't use CWM 4x or 5x thanks :)
[Galaxy S I9000 Android Development] stratosk:
It's not silly. At the present I don't compile my own CWM. I use cfroot's one as is.

Maybe in a future version... :)
[Galaxy S I9000 Android Development] danieldmm:
+1 , after all I it's only 1Mb but 1Mb that can make the difference :D

Sticked to 1.9.1m version.

Thanks Stratosk

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] andip71:
I think this could be one of the next big improvements to compile your own CWM and put some nice features in that makes life easier (cleaning init.d in case of bootloops, playing bootanimation also when dalvik cache gets rebuilt and so on).

Would make an already great product even better :)
[Galaxy S I9000 Android Development] HiKsFiles:
Agreed! :)

10chars
[Galaxy S I9000 Android Development] DarknessWarrior:
i couldnt find those links, but i will try them out,

another question, smartassV2 is the most "pushy" governor, right?

i don't really care for battery life (if it lasts atleast 1 day im fine with it, i don't mind charging it everynight), i prefer smoothness and performance, should i stick with smartassV2 or choose some other governor?
[Galaxy S I9000 Android Development] andip71:
Hi,

on the governour it is more easy. It is safe to say, between ondemand, conservative and SmartassV2, the smartass governour gives you the most responsiveness and performance.

So SmartassV2 + SIO are an almost perfect combination in my opinion - as long as you dont care about battery life as you said.

Because my experiments showed, smartass uses much more often 800 MHz CPU frequency compared to when ondemand usese 400 MHz while doing the same stuff (watching videos).

Hope that helps

Andi
[Galaxy S I9000 Android Development] DarknessWarrior:
thanks, i will try it, atm i have smartassV2 and NOOP and the phone looks really fast (even tho it has less quadrant score than before), i will try different combinations to find the best one for me :D

thanks for the quick response and thanks stratosk for your work on this kernel, it is pretty awesome! kudos!

EDIT: just tested the SmartassV2 + SIO combo and i have to agree, it is a lot faster scrolling the menus and home screens and the phone feels a lot more responsive! Thanks
[Galaxy S I9000 Android Development] pikachu01:
@All,

If you want an explanation of the I/O schedulers, you can refer to my sig (Android Optimization Tips, CTRL-F for "Scheduler")
[Galaxy S I9000 Android Development] johnsin5393:
hi, stratosk

could you explain where should i move the SemaphoreScripts folder in sd card that you provide on script manager v0.62.apk site?

do i need to use R.E explorer to setting it?

thank you
[Galaxy S I9000 Android Development] cooldoc007:
hi.. jus had a reboot today..on 1.9.1 normal version.. have not oc/uv.. jus selected the recommended profile.. and was not doin anything while the reboot occured..jus thought i should let ya know..
[Galaxy S I9000 Android Development] DarknessWarrior:
thanks for the info pikachu!

that clarified things for me..

i also checked your thunderbolt tweaks... im tempted to use them..
[Galaxy S I9000 Android Development] HM.Carbide:
All scripts posted on script manager thread are already included in the kernel.

So there is no need to copy them to sdcard.

If there will be new scripts (and there will be :) ), look at first post in script manager app. The scripts have to be in:

/mnt/sdcard/SemaphoreScripts/*
[Galaxy S I9000 Android Development] stratosk:
Hi,

I think there will be more conflicts with other busybox versions if I'll do this.

Why is impossible to use some scripts?
[Galaxy S I9000 Android Development] johan81:
If anyone here uses 4 tab unlock screen, that is known to cause reboots as well, just trying to localize the culprit :)
[Galaxy S I9000 Android Development] GreenSGS:
There are no reboots in this kernel.semaphore 1.9.1 is stable.
[Galaxy S I9000 Android Development] pikachu01:
If you decide to use ThunderBolt!, then untick all the Semaphore app tweaks except netfilter/smartassV2/OC/UV/CIFS/TUN etc
[Galaxy S I9000 Android Development] xenon_bn:
Is Semaphore kernel compatible with XFJVA ? Or just JVT ?
[Galaxy S I9000 Android Development] pikachu01:
It works with both :)
[Galaxy S I9000 Android Development] johan81:
I agree, was just trying to help people out that do have reboots. With Juwe's ROM I had reboots all the time, in the end it was all due to 4 tab unlock screen. Could be the same for people having issues with rebooting galaxy S phones and Semaphore.
[Galaxy S I9000 Android Development] mickeko:
There are no *known* problems that cause a reboot. You can't know for sure that nothing in the code can end up with the phone rebooting. Perfect code is something that skilled programmers work toward, it's not something anyone really expect to achieve. Specially not when someone else is providing the original source.

Don't make unrealistic claims.

Sent from my tellyphone...
[Galaxy S I9000 Android Development] pikachu01:
Hey stratosk,

Just wanted to do an experiment here.

What do you get when you do:

echo $PATH
[Galaxy S I9000 Android Development] stratosk:
Hi,

From adb shell:

# echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[Galaxy S I9000 Android Development] pikachu01:
Can you do that from the script manager console?
[Galaxy S I9000 Android Development] stratosk:
I don't use Script manager app. But I guess it adds something to your path? Terminal emulator also adds /data/local/bin
[Galaxy S I9000 Android Development] danieldmm:
It's give the same..

Look screenshot.

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] gsw5700:
Stratosk, semaphore 1.9.1 bm is awesome dude, very responsive, fluid and rock solid, excellent work, really appreciate your hard work

Sent using TCP/IP
[Galaxy S I9000 Android Development] BlueKnight83:
Hi to all..

whit default Voodoo Color setting i have the green flash artefact light on screen when turn off the screen. This effect disappear when in Semaphore App i set Voodoo Color to Dark preset.

My problem is that when i turn off smartphone and then on, the modify in setting has disappear and i have green flash light effect.

There is a method to save Voodoo color setting?

Thank you
[Galaxy S I9000 Android Development] HM.Carbide:
Thanks for the info!

I thought, that i made permanent settings. But it will be only permanent, if voodoo control app is installed.

It was not easy to find out how voodoo color is restored after reboot.

There are 2 solutions for your problem:

1) install the voodoo control app.

2) copy the enable_color* scripts to /mnt/sdcard/SemaphoreScripts.

Then the voodoo color option will appear also in AddOn section in app. If you then select darker it will be permanent.
[Galaxy S I9000 Android Development] krosscheck:
I havn't a folder semaphorescripts, is it a prob?

I flashed 1.9.1 new...

Sent from my "Iphone-Killer" GT-I9000
[Galaxy S I9000 Android Development] HM.Carbide:
No problem. The app supports the installation of additional features, or to replace existing features.

Therefore it is possible to place that scripts in a folder named SemaphoreScripts on sdcard.

It has to be created manually. But it should be easy, as it could be done on a pc or notebook, when phone is connected.
[Galaxy S I9000 Android Development] BlueKnight83:
Thank you for your reply..

i tried whit Voodoo app + Semaphore App and Voodoo Darker setting .. every time i restart phone the color are the one setting in Voodoo App and not the one i choose. I try different combination..but nothing, i don't find i solution.

So i delete Voodoo App and insert scrip in SemaphoreSript.. now seem to work, but sometimes all the setting in Voodoo App reset themself.
[Galaxy S I9000 Android Development] HM.Carbide:
Which Rom do you have?

Which version of Voodoo Control app?

As both apps are writing into the same config files, the last profile set will win, could it be, that you changed a setting in voodoo control app, or did you just open it to view the setting?
[Galaxy S I9000 Android Development] psyren:
My CWM was broken after flashing the newest release (non-BM). I tried using the Semaphore app to do a busybox clean, rebooted, then rebooted again into recovery, but it still gives me this:

E:unknown volume for path [/data]

E:unknown volume for path [/data]

E:Unable process volume! Skipping...

Checking /cache

E:unknown volume for path [/cache]

... etc..

I tried reflashing the kernel, with no luck. Any ideas on how to fix this?

EDIT: after flashing the kernel for the first time, I installed the newest busybox (1.19.3 to /sbin, removing the old version that was there). Things seemed to run ok after that, with the exception of Script Manager.
[Galaxy S I9000 Android Development] vanisleryan:
is it necesary to undo lag fix before flashing 1.9.1...currently on 1.8.0? Thanks
[Galaxy S I9000 Android Development] GreenSGS:
No. just flash.
[Galaxy S I9000 Android Development] pikachu01:
Looks like its a Script Manager problem. Thanks!
[Galaxy S I9000 Android Development] zion12:
Just curious to know why dock station support and bootloop detection were removed.

Thanks,
[Galaxy S I9000 Android Development] HM.Carbide:
Bootloop detection is not removed. You can now disable/enable it in semaphore script manager.
[Galaxy S I9000 Android Development] hackeron:
Ive used a couple of kernels like talon, semaphore, speedmod lately.. and I live in a room outside the main house (router in main house) so the wifi signal is very poor.

I rarely get any wifi-signal at all it usually just toggles between H and 3g..

But then I installed cf-root and suddenly noticed that I had 1 dot signal on wifi almost all the time. So it seems that my wifi manages to connect better with my current setup which is:

Cf-root, stock JVT odex, and $omators stock+.

I just wonder if you guys have noticed similar things. And what is different from cf-root and the other kernels when it comes to the WIFI module.
[Galaxy S I9000 Android Development] stratosk:
I don't know if there is a difference in WiFi signal between CFroot and other kernels.

But I do know that Chainfire uses stock kernel. He make changes only in initramfs.

The kernel source code that is available is from JVQ. So, maybe this is the deterrence.
[Galaxy S I9000 Android Development] yihinlau:
how can i get the bootup sound back ?

cuz click the "bootup sound" option in the semaphore application doesn't work at all

thanks.
[Galaxy S I9000 Android Development] stratosk:
The "Startup sound" option works only if your sounds previously backed up during Semaphore kernel installation.

If the sounds are already deleted from earlier versions of this kernel (or from other kernels) this option can't find the backed up sounds and can't restore them.
[Galaxy S I9000 Android Development] HM.Carbide:
Also flashing cfroot first will delete boot sound without back up.
[Galaxy S I9000 Android Development] Rosk1:
i installed it first before a month and i must say, great kernel!

good job stratosk!
[Galaxy S I9000 Android Development] sas_sas:
trouble w/ 1.9.1/ not flashing

Ths Stratosk.

I am one of Semaphore kernel users. I am always happy w/ them..

Till 1.9.1 I have never had any trouble. Sure I use odin to flash them..

Tried two times and the same problem..

But there must be something wrong somewhere.

Though I see "added" mark after connecting my SGS in download mode, when I start to flash, it does not run and not continue. Just types a couple of lines.

The Last line I think it was "..... setup". Do not remember the whole line sorry.

Thanks to My USB Jig I was able to reflash with 1.9.0.

while all previous Semophore kernels were okey, why 1.9.1 has such problem.

Inside tar file there is zImage (file 7.757 kb size) like all the others..

My present Rom is GingerReal 1.1.9 with semaphore 1.9.0.

Any comment..???
[Galaxy S I9000 Android Development] Namiga:
I also got this problem some time ago. But I flashed JVT and started again :)
[Galaxy S I9000 Android Development] stratosk:
Maybe corrupted file?

Can you please check the md5sum of the file you downloaded?

If not, please try to download again the file.

Also, if the problem persists try to flash with ODIN or heimdall.
[Galaxy S I9000 Android Development] stratosk:
Replacing the busybox in /sbin you just break important things in kernel's functionality.

Busybox in /sbin MUST remain as is.
[Galaxy S I9000 Android Development] Namiga:
Thx for the info, stratosk :)

I´m always learning
[Galaxy S I9000 Android Development] stratosk:
I'm also always learning, my friend. At least I'm trying. :)
[Galaxy S I9000 Android Development] moegrave:
/bow

Just wanted to say thanks for the hard work, stratosk. :D

I am currently on your 1.9.1s ;)

Big fan of your constantly improving work and humbly impressed by your upstanding attitude. Just wanted to say, thanks!
[Galaxy S I9000 Android Development] corgar:
what if i remove the busybox inside a rom? 1.15 inside this kernel is full or got only base commands? i'm asking because i want to delete busybox 1.17 inside my rom. the 1.15 got the run-parts?

Inviato dal mio Transformer TF101G