yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] freakymod2120:
Some "mystery" flashing CM11 and Sema-Kernel "s" in combination with BigMemLibs

Hi,

with the last nightlies of CM11 (with Sema-Kernel "s" and BigMemLibs) i have the mystery thing, that after flashing Sema-Kernel via Odin, activating BigMEM via s42_enable_bigmem-Script i have to install the KK44_BigMem_18-nov-13.zip more than one time with reboot between.

My steps are:

- Flashing CM11 via CWM-Recovery

- Reboot

- Activating USB-Debugging ==> Shutdown Device

- Flashing Sema-Kernel "s" via Odin and Reboot

- Deactivate USB-Debugging, enabling bigmem via Script S42 /res/scripts ==> /etc/init.d/

- Reboot in Recovery ==> flashing KK44_BigMem_18-nov-13.zip and then reboot ==> in the past i had the 408MB RAM, but now i have to

- boot again in Recovery ==> flash KK44_BigMem_18-nov-13.zip again and reboot an the it works ...

Has something changed in the last nightlies or i`m only a little to crazy now ...:angel:

Thanks all for reading and helping!!!:good::good:

Kind regards
[Galaxy S I9000 Android Development] Cu8eR:
Any update for kernel?
[Galaxy S I9000 Android Development] tetakpatak:
Why? Isn't it working perfectly fine?
[Galaxy S I9000 Android Development] everb00b:
Well it is, but pawitp added zram and ksm into CM11.

so maybe cm upstream sync.
[Galaxy S I9000 Android Development] AndroidBR:
Sorry but I was wondering... Is there a particular reason why you're doing all of this crazy stuff? Trying to brick your phone, eh? :confused:

Just flash flash everything under recovery with the zip files dude.

Flash CM11, then flash bigmem libs, then you flash Semaphore.

Why complicate things so much? :D
[Galaxy S I9000 Android Development] freakymod2120:
Hi,

thanks for your post.

Sorry i don`t know an other way like the descriped...the way you descripe is quite easier i will test it ...

I don`t know that i can flash Sema-Kernel via CWM...i only use it via Odin ...

Thanks for showing a better way ...:good::good:
[Galaxy S I9000 Android Development] gverma1:
To flash Sema via CWM, download ZIP file instead of TAR file to your phone internal SD Card.
[Galaxy S I9000 Android Development] freakymod2120:
I know thanks ...actually downloading last CM11 nightly and then i test it ...:good:

---------- Post added at 01:41 PM ---------- Previous post was at 01:05 PM ----------

Thanks a lot for showing me a new way of flashing easily all parts !!!

Works great :good::good:
[Galaxy S I9000 Android Development] rmsinaga:
Somehow after upgrading Semaphore Manager to 4.0.0 I have frequent FC of this app. I'm using I9000 with SlimKat RC3. Anybody have similar issue?
[Galaxy S I9000 Android Development] tetakpatak:
By simply flashing a Sema zip file in the recovery mode.

As stratosk doesn't mention that on his website as a possibility to flash the kernel, I also didn't try that way for quite a long time before I begun to think logically..... But I must admit, I enjoy to flash with Odin... I regret there isn't a flash counter.... I must be over 200 now, LOL :D
[Galaxy S I9000 Android Development] darckengel:
He also add CMA which allows to have 417mb free memory without losing 720p recording and other videos features
[Galaxy S I9000 Android Development] everb00b:
Not correct, Pawitp tested cma but decided to stick with the original cm ram setting.

Bit he added ZRAM and KSM because those features are built-in kitkat.
[Galaxy S I9000 Android Development] GreenSGS:
Awesome Stratosk,Had a good vacation? after installing this kernel I get a feel that most of issues on CM 10 ROM are resolved and yet both are alpha builds. Once again bang on target. From where you get so much motivation?

I am 100% sure for me next phone would be a Google flagship device and I know yours too :) , let me know if you change plan.
[Galaxy S I9000 Android Development] stenc55:
I didn't say that you're responsible for partitioning. In fact, I installed laggy rom just to be able to test your kernel, because I love your work. And my observation was that laggy rom + your kernel still have lag. On ICS combination of your kernels and roms with lag usually resulted in smooth phone. In this case it didn't. That's all.

If it happened that you would build kernel that support /datadata I'm afraid I would not be able to hold phone. It would be so fast it would slip through my fingers.
[Galaxy S I9000 Android Development] yahyoh:
it's :highfive::highfive:
[Galaxy S I9000 Android Development] stratosk:
It should be on Settings->System-Advanced (galaxy S settings). Though I get FC using it. But it's there on ICS kernel (unreleased)

Pretty good, although I got a flu. But I will continue next week.

Thank you very much for your comments.

My motivation? I love Linux Kernel, I love Android, I love programming. But the main reason is everyone that supports this project = all of you. :)

Yes, I think my next device will be a Google one, but I will let you know my decision (when this will happen...)

Thanks for your comments my friend. I know I just clarified my decision about the no /datadata partition.

As pawitp said that /datadata is not responsible for the lags. I trust him and I believe that he will find the solution soon.
[Galaxy S I9000 Android Development] spacekobra:
Awesome! You guys have done a great job at making jb awesome for a phone that didn't even receive ics
[Galaxy S I9000 Android Development] ddd613:
Some rom can boot with no datadata version

On TAJB and other nexus port unable to flash datadata version

Sent from my GT-I9000 TAJB with devil3 1 RC5 no datadata inside
[Galaxy S I9000 Android Development] matt73300:
Hi,

if I want compile your kernel myself with last linaro toolchain, do I have to do some manipulations like for kernel 1.2.x ? (compile with gcc 4.4.3, copy a file, etc etc) ?

Thank's :)
[Galaxy S I9000 Android Development] stratosk:
No, thanks to pawitp you don't need to do anything. Just compile the latest source.
[Galaxy S I9000 Android Development] matt73300:
Ok, cool. I just compiled it (and now I could do a BBQ on my CPU :laugh:)

Now I will try it

Thank's man :good:
[Galaxy S I9000 Android Development] stratosk:
I think my laptop's CPU hates me. I don't know how it's still working. :laugh: Many times thermal protection shuts my old laptop down...
[Galaxy S I9000 Android Development] yahyoh:
maybe u should clean heat Vents or change cpu thermal :o
[Galaxy S I9000 Android Development] stratosk:
Yes, I try to clean them frequently. :) If there is a little dust it happens sometimes, if I use my laptop for other tasks during compilation.
[Galaxy S I9000 Android Development] GreenSGS:
Just back from vacation and caught flue still online on xda at MidNight. Prove you are human

3 + 4 = 21, 5 + 9 = 70 , 8+4 = ? :)
[Galaxy S I9000 Android Development] matt73300:
Hahaha! fortunately, my laptop's CPU is not bad, so the compilation is relatively quick. :D
[Galaxy S I9000 Android Development] stratosk:
:laugh:

I'm not good at these. I am always nervous when someone gives me such a test. :)

Anyway, good break from CWM6.

3 + 4 = 21, 5 + 9 = 70 , 8+4 = 96 ?

Is this correct? (means that I'm human???)
[Galaxy S I9000 Android Development] Silentbob999:
Nice lol, I think you got right answer. Never thought before that there was a logical resolution :P

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] parhelion69:
Maybe:

3 + 4 = 21 = 3*4 + 3^2

5 + 9 = 70 = 5*9 + 5^2

8+4 = 96 = 8*4 + 8^2
[Galaxy S I9000 Android Development] stratosk:
Yes, that was my thought. :)
[Galaxy S I9000 Android Development] rkaede:
damn. im not human then. im a simple man. 12 is the answer. LOL
[Galaxy S I9000 Android Development] TheeWolf:
A somewhat stupid question, but is there any difference to whether I'm flashing this kernel with ODIN or via recovery? Is one version better then the other? Or is the ODIN version intended so that you can flash it when having problems, i.e bootloops?
[Galaxy S I9000 Android Development] stratosk:
There is absolutely NO difference between tar and zip of the same version. Just flash the one that it is most convenient to you.
[Galaxy S I9000 Android Development] upichie:
Well it usually wouldn't stick when enabling it via the app (the check box was still checked, but the RAM wasn't there). But after running the terminal commands, it sticks. So I'm happy. :)
[Galaxy S I9000 Android Development] rajamahbub:
Smooth UI

Ok, what is smooth UI and what does it do? I am running JRO03L RC10 with no problem but when I tick smooth UI my media scanner misbehaves, no idea why??? Answer will be much appreciated.
[Galaxy S I9000 Android Development] Corvillus:
Yeah I've tried it and noticed bugs. The UI is plenty smooth without it anyway.
[Galaxy S I9000 Android Development] alexovy:
I think it should give you the butter fell when you browse through menus, but I get the felling it is smoother without it enabled. Is it just me?

Anyway, stratosk, may I tell you that on 2.0.6s I get stable phone on 1140 live oc, and on 1.3.0s ICS I was stable only at 1100 when I run Antutu or some demanding games.

Congrats and thank you!
[Galaxy S I9000 Android Development] rajamahbub:
Yeah you are right. It is smooth without it. I was just wondering why it was there anyway...!!

---------- Post added at 07:50 PM ---------- Previous post was at 07:46 PM ----------

I feel the same. It is smooth without it...Thanks...
[Galaxy S I9000 Android Development] stratosk:
Smooth UI has a very simple implementation.

Governors check if you touch the screen. If yes, they use maximum CPU frequency. I use it from day 1 without issues. Also, no reports about issues, until now.

I implemented smooth UI since ICS days. IMHO, helps a little for a smoother experience

Jelly Bean has extra features for smoothness, so maybe it makes no big difference.

Anyway, almost every feature in Semaphore is optional (and disabled by default). If you feel that you need it just enabled it. If not, keep it disabled.
[Galaxy S I9000 Android Development] pfoenix:
I noticed that when I install semaphore, my BLN stop working.Аny suggestions?
[Galaxy S I9000 Android Development] avoulk:
You can always enable it through NSTools
[Galaxy S I9000 Android Development] pfoenix:
Now it works.Thanks man, I did not know this trick:)
[Galaxy S I9000 Android Development] H-Body:
And that's why i like your kernel so much :) Fast & slim but with options to make it fit our needs!
[Galaxy S I9000 Android Development] monjovega:
Do you have to have NSTools together with Semaphore for it to work properly?
[Galaxy S I9000 Android Development] yahyoh:
don't use nstool :)

semaphore app is more than enough to control everything ;)
[Galaxy S I9000 Android Development] upichie:
Where's the option for BLN? I have to enable it through NSTools or BLN Control, otherwise it's off. How do you do it?
[Galaxy S I9000 Android Development] monjovega:
Thanks.. Another useful information.
[Galaxy S I9000 Android Development] yahyoh:
u can enable it via display setting on cm10 i think or via bln control or via script or idk :laugh:
[Galaxy S I9000 Android Development] TinyFeather:
Statosk, do you have plans to integrate fiops and/or row i/o scheduler?
[Galaxy S I9000 Android Development] Silentbob999:
With cm10 it does seem to work after flashing semaphore.

Is backlight notification is the same as BLN?

IF it's the same, nstool init.d show this :

echo 1 > /sys/class/misc/backlightnotification/enabled

You can create your own script for the semaphore script manager with that.

Maybe it's a start. The light stay on, no flash.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] DanielSanchez:
If you are on cm, you will need nstools for fast charge.
[Galaxy S I9000 Android Development] jugster:
As has been said again and again, zram is unlikely to make it to semaphore.

What benefits does ksm bring for applications not written for it?

AFAIK, applications need to a advice the kernel which pages can be merged to make use of this feature and I don't believe a lot of applications currently do that. Unless android applications do that on another level than ordinary Linux programs. Also after an application has adviced the kernel that a page is mergeable, the kernel needs to scan memory for candidates. This can again afaik, be a CPU hogging activity. So basically, this feature trades CPU power for memory.

In summary.

Zram: Probably not gonna make it to semaphore.

Ksm: Cool feature? Yes! Useful? Not so much. At least not for or particular platform which is already struggling cpu wise.

(CMA is cool though, I hope that leads somewhere eventually)

Signature? Signature!
[Galaxy S I9000 Android Development] darckengel:
Well, he added it long enough to inspire devs like diddhiys and kasper_h to add it in their kernel with success (even if mackay kernel currently have some problems with front camera with CMA, and video issues with CMA+KSM enabled).
[Galaxy S I9000 Android Development] everb00b:
I agree with you, I too hope to see CMA fully fixed and featured in our kernel.

I hope startos will take a glance at it to hear his opinion.
[Galaxy S I9000 Android Development] stratosk:
New version Semaphore Manager 4.1.0 (available soon on Google Play)

- Add more languages (Dutch, Croatian, French, German, Italian, Indonesian, Norwegian, Polish, Serbian, Spanish, Swedish, Russian) (credits to all XDA members that work on this, thanks crowdin.net for hosting Semaphore Manager project for free)

- Code improvements and bug fixes

- "touchwake disable" option in SAI is disabled if touchwake (in Tweaks) option is also disabled. This will probably avoid accidentally enabling touchwake after calls

- Touchwake and double tap to wake options are mutualy exclusive

- Fix pick up phone functionality

- Better handling of swipe
[Galaxy S I9000 Android Development] stratosk:
I think it's cool feature.

But unfortunately, at the present, I don't have free time to invest on this.
[Galaxy S I9000 Android Development] tetakpatak:
According to the logcat I've done on my phone, it seems to be just a minor setting thing rather than a bug.

JPEG encoder isn't saving the shots made with the front camera, while the back camera -important one- works great.
[Galaxy S I9000 Android Development] Cu8eR:
Double tap for sgs? Is it possible? Or at least cm sync
[Galaxy S I9000 Android Development] jugster:
It is certainly possible. The real question is how to do it without increasing the battery usage to much.

However, I've requested this way way before and at that time Stratosk was not interested and with his limited time I doubt that has changed recently.

Many people swear by it though, and I certainly like the feature.

Signature? Signature!
[Galaxy S I9000 Android Development] karan luniyal:
Hello noob here.

My cwm stucks on setting up kernel every time i try to flash plse help...

I mrunning stock jb..

Thnxx in advance...
[Galaxy S I9000 Android Development] tetakpatak:
Just in case you're still interested in it:

kasper_h has uploaded a hour ago the new build of Mackay Omni ROM with the new kernel (without CMA, zram & KSM updates, fix for colour problems)

The front camera works perfectly fine now.

I've just tried it :)
[Galaxy S I9000 Android Development] stratosk:
New version 3.4.1

- Merge changes from CM kernel (blue screen issue, JPEG memory optimization, initramfs thanks to pawitp)

- CWM 6.0.4.7
[Galaxy S I9000 Android Development] everb00b:
zram and ksm are not included?
[Galaxy S I9000 Android Development] stratosk:
I'm sorry, no.
[Galaxy S I9000 Android Development] HalphaZ:
Maybe I'm ot...

What are Good overvolt values for 20% liveoc? Does liveoc overclock even system bus And ram?

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] bhu1:
Unrelated, but would appreciate an answer - Is there a way to use USB OTG feature to connect a pen drive to the galaxy s ?
[Galaxy S I9000 Android Development] gverma1:
You will need externally powered USB drive so pen drive is out of the question.
[Galaxy S I9000 Android Development] ayed78:
I flash new kernel stuck at samsung logo
[Galaxy S I9000 Android Development] gverma1:
My flash went just fine. Am using it on SlimKat stable.
[Galaxy S I9000 Android Development] nestul:
Hello, I am using SlimKat/Semaphore right now. I would like to know if Semaphore supports true cd emulation for DriveDroid. If not, why? If there is a good reason some developers don't patch their kernels for this, i would like to know it, just curious... Thanks for your projects, stratosk.
[Galaxy S I9000 Android Development] 99x:
Not completely accurate, you can plug an OTG cable in to a powered USB hub, then plug the pen drive in to that.
[Galaxy S I9000 Android Development] Krimator:
yes!

I use since yesterday:cool:
[Galaxy S I9000 Android Development] stratosk:
I've never tested this. I guess it requires kernel patching? Honestly, I don't find it a useful feature. :)
[Galaxy S I9000 Android Development] nestul:
From the author post:

I use this for running livecds or install operating systems from my phone as a USB drive, I only copy the ISO file to my phone, mount it using drivedroid and reboot my PC. As the author says it can only mount hybrid isos, but by patching the kernel as mentioned above it is also possible to mount not hybrid isos such as MS Windows isos and other Linux based livecds I use effortlessly :)
[Galaxy S I9000 Android Development] Opuz Klass:
Hi [MENTION=3750240]stratosk[/MENTION],

Just to let you know AROMA fm is broken in this version... File not found @ /tmp/...

Thanks for the update, though! :)
[Galaxy S I9000 Android Development] AndroidBR:
Confirmed, cannot find tmp/aromafm.zip

For the ones that use AFM like myself, you can always download latest ".zip" file at the developers XDA thread while you wait for Stratos to resolve this issue.

Thanks for the kernel update Stratos! :thumbup:

;)
[Galaxy S I9000 Android Development] ts1506:
Its quite useful if you actually need it. Anyway, the needed patches (if you are interested) are here and here :)
[Galaxy S I9000 Android Development] dk147in:
Hi [MENTION=3750240]stratosk[/MENTION],

Good to see the new version 3.4.1, but in that some thing is still missing in camparison of the CM11 pawtip's kernel. Beacuse whenever i launh spirit FM then the vibrator stops working and the setting options for vibrator is also gone away and in phone ringer setting there won't be virator mode only mute or ring left. But it only happens when i launch spirit FM with your kernel however same version of spirit FM works fine with pawtips kernel.

I have tested it several times and the only indication of the issue is in the kernel is some where broken....pl fix that because I love semaphore kernel for its fast speed....

Thanks
[Galaxy S I9000 Android Development] ts1506:
Same issue is there in Mackay and CyanCore too. And last time I tried stock CM kernel, same issue was there too.

Its most probably an issue in Spirit FM app, roll back to an older version, it works fine.

I have the unlocked version, last version which didnt have issues is the Dec 5 for your reference. After that, all versions are having this vibrator issue.
[Galaxy S I9000 Android Development] HiKsFiles:
Just updated my good ol' i9000 to Android 4.4.2 Kit Kat (Slim Kat) and flashed the latest Semaphore kernel.

Gotta admit that even though this device isn't getting any younger, [MENTION=3750240]stratosk[/MENTION] kernel's have always been the best.

I can't even get as reliable a kernel on my Galaxy S3 i747m !!

Thanks yet another time around Stratos for all your good work ! :highfive:
[Galaxy S I9000 Android Development] cannondaleV2000:
Man run devil on that s3. Run it on my note 2 and its stable. I personally run cpu at 2ghz and gpu and 666mhz but you dknt need all that lol
[Galaxy S I9000 Android Development] stratosk:
New version 3.4.2

- Fix AromaFM execution issue in recovery
[Galaxy S I9000 Android Development] CatalystWon:
How to restore only CM-kernel?

A search did not reveal a clear answer.

I take weekly full CWM backups. When we're using Awesome-Semaphore kernel, how do we temporarily restore only the stock-CM-kernel if necessary for CM-bug testing and reporting? Re-flashing the entire ROM is

not

the desired response.

Thanks!
[Galaxy S I9000 Android Development] jugster:
Flashing only the kernel through cwm does not work?

Signature? Signature!
[Galaxy S I9000 Android Development] jugster:
The CROSS_COMPILE directive should reference the compiler you have installed. Obviously, you don't have that compiler installed. I think mostly because Stratosk uses official Linaro toolchain, and you are using something else. Here is the proper download link to the Linaro toolchain: http://releases.linaro.org/13.04/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux.tar.bz2

Your directive should read "arm-gnueabi-" because according to the ls, that is what you have installed.

So, this change would probably bring you closer to world domination: CROSS_COMPILE="arm-gnueabi-"

However, installing the linked toolchain will probably achieve the same.

Cheers,

J
[Galaxy S I9000 Android Development] hertzschi:
Thanks a lot :highfive:

I changed in sbuild.sh the associated line to

export CROSS_COMPILE=../toolchain/arm-linux-gnueabi-

and now it went through

Build completed in 2 minute(s) and 57 seconds.

:good:

Let's hope it boots :fingers-crossed:
[Galaxy S I9000 Android Development] CatalystWon:
So how then does one backup/restore the CM kernel?
[Galaxy S I9000 Android Development] jugster:
Ah, I see now what you mean. I didn't read properly.

Well, I suppose you can dump the contents from odin or heimdall and then flash it the same way again.

Have not really tried myself though.

Hope it works,

/J
[Galaxy S I9000 Android Development] fatino:
First of all It's the best kernel I've ever used on my SGS. It just has one problem. Earpiece volume is really low. It's really quiet and it's hard to hear people in result. On Mackay kernel it's really loud though. I can adjust it to my liking.

Could you please make earpiece volume higher? Maybe even configurable in semaphore settings.

Wysłane z mojego GT-I9000 przy użyciu Tapatalka
[Galaxy S I9000 Android Development] juliatan:
Isnt't the easiest way to get original kernel back to flash same rom you are using?

So in recovery wipe cache partition and wipe dalvik (and nothing else, so no factory reset and no format system). Then flash exactly same rom you are using. Reboot. After that all settings and installed apps preserved.

I would like to know if I am correct just in case of any future issue. Although I have never experienced an original kernel working better than newest Semaphore or Mackay kernel on my i9000.

(And by the way every original CM kernel worst of all kernels in my cases (Cm10/10.1/10.2). Much lag and battery drainer solved with Semaphore. I just stopped using CM totally anyway. CM-roms always got very slow after few weeks use and read tons of same experience with others using CM. Slim (with newest kernel) just keep on flying).

Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
[Galaxy S I9000 Android Development] tetakpatak:
This was very respectless to write. All we who use i9000 have very great respect for pawitp, also the developers of Mackay and Semaphore do.

Pawitp has to follow ceirtain development lines of the official CM's philosophy what you may not understand, but he helps the development of other custom kernels.
[Galaxy S I9000 Android Development] jugster:
Reflashing rom was not an option if you had read the original post.

Signature? Signature!
[Galaxy S I9000 Android Development] juliatan:
By no means I meant to be disrespectfull. CM off course base of most development which I am very gratefull for. However am I not allowed to a personal opinion shared by the way by many others? Political correctness and (self-) sensorship on xda like daily life in EU. Please spare me of such nonsense.

Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk

---------- Post added at 12:32 PM ---------- Previous post was at 12:19 PM ----------

Probably reading over it, but can't see it in original post. I'll keep it in mind anyway. Backed up everything with Titanium Pro so a fresh rom-flash and restoring not a problem when s hits the fan...

Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk