yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Bejda:
Well it's on-screen softkeys,when device is running.

Navigation bar with back,home,recents and menu when available buttons.
[Galaxy S I9000 Android Development] franzyroy:
So it would be in case the rom do not have this option?
[Galaxy S I9000 Android Development] Bejda:
Yeah,it's the build.prop tweak so you get a big 48dpi NavBar if not set in rom framework.
[Galaxy S I9000 Android Development] kasper_h:
Busy with TWRP backup/restore. Didn't solve it yet, but found a few leads. Anyway, here is the latest update.

Changelog 0.318 compared to previous release (0.316)

-Update to v3.0.80

-Small upstream CWM updates

-Minor TWRP updates (backup/restore still not functional)

Download (TWO flavours can be download: CMC=CM stock colour or VC=Voodoo Colour :)):

http://rootaxbox.no-ip.org/kasper_h/kernels/JB42/

For those who want to theme it even further, Bejda made a Mackay splash screen!

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

For those who want to theme TWRP (or simply get rid of the orange ;)), erpurohit made a TWRP theme:

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

This version can only be used on JB4.2-based ROMs
[Galaxy S I9000 Android Development] sandman303:
hope the best luck with twrp restore!:)

Sent from Tapatalk.......SO!
[Galaxy S I9000 Android Development] Blackherted:
Can't wait for the fix for the restore in twrp... thanks for the new version kasper!
[Galaxy S I9000 Android Development] sandman303:
yes

Sent from Tapatalk.......SO!
[Galaxy S I9000 Android Development] kasper_h:
At least I now know exactly the source of the TWRP backup problem (restore is fine). I just have to find a work around to solve it :)
[Galaxy S I9000 Android Development] sandman303:
yeah its not backing up datadata up properly that's why I'm on 293.

Sent From Tapatalk 4.........SO!
[Galaxy S I9000 Android Development] AusMatt:
Mackay kernel is performing very well with CM 10.1 nightly builds. I was previously using Semaphore but lately it seems a bit slow.

My podcasts (using PocketCasts) would stutter with Semaphore when using other foreground processes (such as gmail and games).

This does not happen with Mackay.

Kasper, maybe you could give Stratosk some advice ?

What is the key to the speed of Mackay ?
[Galaxy S I9000 Android Development] kasper_h:
Yeah, I know ;)

And I could off course revert every single patch in TWRP for the last two months one-by-one, but that is a boring job. So I have gone through them and found one I think to be guilty :)
[Galaxy S I9000 Android Development] Rebel2k:
Hope you'll find this nasty guilty change! :)
[Galaxy S I9000 Android Development] kasper_h:
New version 0.230!

Download (Four flavours can be download: VC=Voodoo Colour, BLN=BLN :)):

http://rootaxbox.no-ip.org/kasper_h/kernels/JB42/

Changelog 0.230 compared to previous release (0.220)

More free RAM (396MB)

Updated code of interactive governor
[Galaxy S I9000 Android Development] sasha4fierce:
can i flas this on c-rom bean 4.2.1?
[Galaxy S I9000 Android Development] Fenvarien:
Great kernel! Speed, stability and battery life are really impressive :)
[Galaxy S I9000 Android Development] DerRomtester:
Can you make a edition for fishears pls?

---------- Post added at 02:49 AM ---------- Previous post was at 02:11 AM ----------

Kasper_h do you know cocore kernel? This kernel is for i9070.If you want to add some governeurs (22 gouverneurs) you should look in this thread.
[Galaxy S I9000 Android Development] Flith:
Where can I turn on SmartassV2 governon?
[Galaxy S I9000 Android Development] GrippingSphere:
Via NSTools downloadable from Play Store
[Galaxy S I9000 Android Development] Rootax:
Or the performances settings in cm10.1
[Galaxy S I9000 Android Development] iulian vu:
I'M on Helly bean 4.2.1 with Mackay Kernel . How can I put Smartass ? I installed NSTools , but in CPU settings it says not available . What can I do?
[Galaxy S I9000 Android Development] GrippingSphere:
Usually 'fixing permissions" through CWM will fix the problem.

Or you can select the CPU Governor (and the I/O scheduler) via Settings/Performance
[Galaxy S I9000 Android Development] kasper_h:
Best way to set governors is Settings>Performance (If you don't see the, go to About Phone and click 7 times on build number).
[Galaxy S I9000 Android Development] kasper_h:
I already build four version, I am not planning to build more versions.

I don't see the advantage of so many governors. I am actually thinking of reducing the available governors....
[Galaxy S I9000 Android Development] iulian vu:
Thank you
[Galaxy S I9000 Android Development] Flith:
Thanks guys. Another question. What about "Deep Indle", how can I turn it on?
[Galaxy S I9000 Android Development] kasper_h:
You can't because it is not included (on purpose: to many stability issues related to it).
[Galaxy S I9000 Android Development] saszseb:
And on AOSP ROMs like Elite's ones?

Use Voltage Control! :)
[Galaxy S I9000 Android Development] sasha4fierce:
I have it street fighter IV and plays smooth with devil kernel... now i flashed your kernel and game wont start, what happen?
[Galaxy S I9000 Android Development] saszseb:
I run MC4 without lags.
[Galaxy S I9000 Android Development] Dustman317:
i want to tell a question at everyone here

does your phone support 1400 mhz OC ? because my phone freeze at this frequency and the changelog say that 1400 mhz OC is supported

sorry for my bad english

---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------

Can you give me a download link because every versions that i've downloaded doesn't start on my phone
[Galaxy S I9000 Android Development] saszseb:
MC4?

I've bought it from Gameloft.
[Galaxy S I9000 Android Development] AusMatt:
Mystery solved. It's just the choice of default scheduler and governor.

I've configured Semaphore to use Ondemand and ROW and my podcast stuttering issue is gone.

Sorry to Stratosk for my ill conceived comment.
[Galaxy S I9000 Android Development] gverma1:
Only 394mb RAM without bigmem enabled

Hi kasper_h. In your kernel version 0.316, the available RAM has gone down from 397mb to 394mb. Any idea why this happened? Has this been rectified in 0.318? Thanks
[Galaxy S I9000 Android Development] kasper_h:
This is probably related to the new toolchain. Linaro toolchains in general result in slightly less available memory. In the end, I don't care about the absolute number of MBs, it's about the fluidity of the system, and for me it feels slightly better with the new toolchain.
[Galaxy S I9000 Android Development] ts1506:
Even my kernel's RAM went down from 410 to 409mb, but in normal mode it is still 397mb.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
I see you take care of this 1 mb as if its your kid :D
[Galaxy S I9000 Android Development] sandman303:
+1

Sent From Tapatalk 4.........SO!
[Galaxy S I9000 Android Development] dejan-:
0.316 eated my battery or at 0.318 i have feeling now that has less consumption?! ...anyway...good work
[Galaxy S I9000 Android Development] aliver.dun:
Hi dev,

Is it possible for you to make one kernel for Captivate,you kernel is so nice,thanks you...
[Galaxy S I9000 Android Development] jupiter5700:
Hi, kasper_h! Are you have any plane to add some futures to your kernel? For example 'game_mem' when full disable camera, disable radio module and other android process to extremaly free memory?

And can you tell me where CMC module is find? In kernel or in external rom module?
[Galaxy S I9000 Android Development] kasper_h:
I have deliberately chosen for only one memory config. Make multiple mem configs complicate things, so I will no do that. I also only spend my time on things I find interesting myself, because my time for developing is limited. Gaming is not among the uses for my phone.

CMC is build into the kernel. That is why you need a separate CMC and VC kernel.
[Galaxy S I9000 Android Development] jupiter5700:
Ok, i understood you position.

And about CMC. Minor trouble with brightnes ajustment i think. When brightness level is lower 25% then screen to be some green-yellowish colored. On all i9000 devices with CM that i saw. It cince CM9 i think. I need to correct RGB gamma to exclude this effect.

May be exist a simple way to fix this trouble by change any bites in kernel? )
[Galaxy S I9000 Android Development] kasper_h:
Every screen is different. That is why the screen tuning option exists. There are no settings that are perfect for everyone.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] alb3rtt:
Doesn't happen to me but you could fix it by tweaking the gamma and colors in settings/advanced. It might be just that the devices that you saw had a degraded amoled screen because amoled is organic (hence the o in the name) and that means it breaks down and degrades over time, giving bad screen quality when the phone gets old. My device has bad whites but with cmc I can tweak the gamma and colors to make it white again.
[Galaxy S I9000 Android Development] jupiter5700:
As i sayd i saw this effect not only on my i9000. And second, if i set 100% brightness, then turn brightness to low settings by Screen Ajustment application (free at google play) is no green-yellowish effect. I'm not talking about 100% accuracy of white balance, but CM brightness tune is bad keep color balance, not so accuracy like Screen Adjustment for example and not so accuracy like on stock samsung roms.
[Galaxy S I9000 Android Development] thETImo:
Flash the VC version. Via Voodoo Sound -app you can adjust the screen gamma very easily. ;)
[Galaxy S I9000 Android Development] jupiter5700:
I know it. ;) And now i using VC based kernel.

kasper_h, is it possible to use exFAT 64Gb microSD-CARD on our i9000 or exist hardware limits?
[Galaxy S I9000 Android Development] alb3rtt:
People have used 64gb sd cards on our phone so it should work. Try formatting it to fat32 though because im not sure about exfat.
[Galaxy S I9000 Android Development] jupiter5700:
I have no 64gb sd card yet. I must be sure that it work properly on my device before i will purchase it.
[Galaxy S I9000 Android Development] idCyber:
Samsung's hardware specification for i9000 states that the limit is at 32GB microSDCard. So I dunno if i9000 could handle 64GB microSDCard.
[Galaxy S I9000 Android Development] thETImo:
Also I'm planning to get a 64GB SD. I know a few people who have successfully used it for a while now. :good:
[Galaxy S I9000 Android Development] alb3rtt:
It will work.
[Galaxy S I9000 Android Development] kasper_h:
New kernel version 0.321:

http://rootaxbox.no-ip.org/kasper_h/kernels/JB42/test/

This one should solve the TWRP backup/restore bug. I revert almost all patches between 2.5.0.0 and 2.4.4.0 (as can be seen in the recovery title).

I hope others can check as well. I checked myself and had a successful backup&restore.
[Galaxy S I9000 Android Development] derboedi:
So now we should be able to backup data using TWRP but it's still not compatible with CWM backups, right?
[Galaxy S I9000 Android Development] kasper_h:
Exactly, within twrp it should all work, but cwm and twrp are not compatible with each other. I have a patch to solve this in twrp (enabling cwm restore) but this is still faulty...

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] tsatomas:
Hi Kasper, I tested and confirm v0.321 twrp backup/restore work fine. thank you.
[Galaxy S I9000 Android Development] kasper_h:
Thanks for testing. Tonight I also tried another full backup&restore and a data backup&restore, and both went fine.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] sandman303:
ok so it does work but is there any chance of having 2.5.0.0? thanks.

Sent From Tapatalk 4.........SO!
[Galaxy S I9000 Android Development] kasper_h:
Why do you want 2.5.0.0? There are no killer features making it that much better. I will manually merge bugfixes.

The main difference with 2.4.4.0 is the way partitions are dealt with. This actually causes the problem for our phone. So upgrading is impossible atm: it simply will not work.

In addition, I also tried to manually revert single patch sets, but this did not work: there were many patch sets dealing with partition handling. And when revert only that set of patches, recovery would not boot anymore. This shows the inter-dependencies of the different patch-sets. And this makes it impossible to make a partly update from 2.4.4.0 to 2.5.0.0

I reported this to the twrp team (and our phone is not the only one with this problem). So I hope it will be solved in a next twrp release.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] kasper_h:
I recently received several pm's from different people about the use of different recoveries in one kernel. The most recent actually asks almost all questions, so I will (anonymously) give here the pm & my answers. I hope this answers everyone's questions, so there is no need anymore to send me pm's about this issue.

1. No: recovery ramdisk is only used if booting into recovery. So when booting normally into the ROM it does not make a difference

2. Yes: this is the clear advantage of a kernel with only one recovery image: bootup would be 2 second quicker (yes: 2 seconds only, is that gonna save your life? :))

3. No: as mentioned in point 1, the recovery ramdisk is only used when booting into recovery. So when the ROM itself runs normally, the normal ramdisk is in use, which is the same for any CM10.1 kernel.

4. No: there are three ramdisks (cwm, twrp, rom) merged in one boot image. One can't simply remove something to get rid of TWRP (or CWM).

Some additional points:

-I made separate CWM & TWRP kernel in the past. This took much more time to compile and had more risks associated with it (I did not test all four (and at a certain point 8) kernels whether they worked). Now that I build only two kernels, I test them both before release. So I will stick to the current system.

-I also have received the question whether I could make CWM the default recovery, with an option to switch to TWRP in Mackay Settings. I myself prefer TWRP (now that backup&restore works fine, there is no real need for CWM anymore), so I like the system to boot into TWRP by default.
[Galaxy S I9000 Android Development] thETImo:
So is the 3.2.1 kernel final now? Considering it's in the test-folder to be downloaded. ;)
[Galaxy S I9000 Android Development] kasper_h:
I put it in the test folder because TWRP was at that point only tested by me. It seems to work fine now. But during the weekend, I will probably compile a new kernel & ROM, which will end up in the regular spot.
[Galaxy S I9000 Android Development] purpleraintoxicity:
I know ill probably get lots of fire now, but I'm a devil user :) . is there any option to enable swap in mackay?
[Galaxy S I9000 Android Development] kasper_h:
I have disabled swap because it caused unexplained slowdowns, so I decided to leave it out...

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] purpleraintoxicity:
ok.

cause we don't have much ram and that's slows down my phone even more :)

thank you
[Galaxy S I9000 Android Development] alb3rtt:
True but Swap GREATLY reduces I/O speeds and that is our real problem. Getting a *bit* more ram just to kill your I/O speeds even more is not worth it at all. zRam, Swap and KSM is not recommended on our phone because they use more CPU but Swap lowers performance the most out of the three. On PC, it works well. On android, its not recommended. Also, if you want to free up your ram, use SuperNexus or any other super clean AOSP rom or CM10.0. I'm using CM10.0 and I usually have around 180MB of free ram.
[Galaxy S I9000 Android Development] ts1506:
KSM and UKSM work pretty good , it does use a bit of CPU power , but end effect is good enough.

On the flip side , ZRAM and SWAP absolutely kill our phones.
[Galaxy S I9000 Android Development] alb3rtt:
My experience with KSM and UKSM was bad. I felt more stutters in animations and scolling and I feel like its not worth the trade off.
[Galaxy S I9000 Android Development] purpleraintoxicity:
good to know. even though I am currently use swap ans the phone is super snappy.

I will see what I can do to reduce ram usage.

cm10 was great but I really like cm10.1 features
[Galaxy S I9000 Android Development] GrippingSphere:
Reporting on the bright side:

TWRP backup & restore are confirmed working fine on the latest kernel 0.321.

Tried backing-up on internal and external SD and used back-up custom name - all worked fine.

Didn't use compression and MD5 verification.

Good work kasper. Awesome kernel.
[Galaxy S I9000 Android Development] kasper_h:
Thanks for the confirmation!
[Galaxy S I9000 Android Development] kasper_h:
For me it also caused more harm than pleasure. And I know I got some messages from other with the same issue. So I decided to simply disable it to get rid of the complaints :)
[Galaxy S I9000 Android Development] kasper_h:
New build online!

Changelog 0.322 compared to previous release (0.318)

-TWRP downgrade to 2.4.4.0 codebase (to make backup/restore functional again)

-CWM upgrade to 6.0.3.2

Download (TWO flavours can be download: CMC=CM stock colour or VC=Voodoo Colour :)):

http://rootaxbox.no-ip.org/kasper_h/kernels/JB42/

For those who want to theme it even further, Bejda made a Mackay splash screen!

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

For those who want to theme TWRP (or simply get rid of the orange ;)), erpurohit made a TWRP theme:

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

This version can only be used on JB4.2-based ROMs

FAQ

Q. I can't change governor in NStools (or any similar app)

A. Go to recovery, mount data & datadata partition, then fix permission. You can also install the fix permissions app to this for you: http://bit.ly/YxPgLD

Q. Process x (e.g. mediaserver/phone) is eating 50+% of my battery, what should I do?

A. Go to settings>apps>all and find the app which is causing the battery drain. Then delete app data and reboot phone. If it does not help, you can combine this step with clearing dalvik cache.
[Galaxy S I9000 Android Development] Blackherted:
Thanks kasper! 2 questions...

If i already have 0.321 and use TWRP there's no need for me to update right?

second, about what you said in the subject of the media server... when i open the apps in the settings>apps>all... how can i know which app is causing the drain?
[Galaxy S I9000 Android Development] franzyroy:
I think this will better, the 0.321 release was an intermediate version (I think). Certainly there are some corrections.
[Galaxy S I9000 Android Development] kasper_h:
TWRP is the same between 0.321 & 0.322. Only update is in CWM. I still have some work planned for TWRP, but I will do that in the next few days.
[Galaxy S I9000 Android Development] mamoto66:
Kasper, a question please.Think this rom and kernel is still room for improvement?or only updated because continues to update CM,That may have room for improvement?Thanks.Saludos desde España HTCmania.

Sorry,for bad English.
[Galaxy S I9000 Android Development] jupiter5700:
Hi, kasper_h! Could you add live OC support in to you kernel?

Thank.
[Galaxy S I9000 Android Development] Blackherted:
Could you plesae answer my second question? :)
[Galaxy S I9000 Android Development] kasper_h:
No, Discussed long time ago. I don't like live OC, as caused stability issues for me, even when set to 100% (so no OC).

I did not understand the question well. You just look for the app name in Settings>Battery, and then look up the same app in Settings>Apps>All...
[Galaxy S I9000 Android Development] Blackherted:
yea but what should i look for? how will i know which apps cause this battery drain?
[Galaxy S I9000 Android Development] kasper_h:
You just look for the app name in Settings>Battery -> top of the list :)
[Galaxy S I9000 Android Development] Bejda:
I think a monitoring app even if it's a running process itself is a must have.

Any apps with quick access to processes running, a cpu witness in status bar is a good thing too imo.

There's Wakelock Detector app too which is a little more user friendly than BetterBatteryStats.

It worth it to not stay with a gone wild media storage (normal after boot but shouldn't stay..and sometimes does) ,download manager,protected drm content or else harassing cpu up to a constant 80/100%.
[Galaxy S I9000 Android Development] Blackherted:
I do it, but every time i boot the media is awake for like 8-10 mins using the full cpu speed... i thought something was wrong but what your are saying is that it's normal? (it goes down after that time)
[Galaxy S I9000 Android Development] Bejda:
If it's the whole media storage thing yes,but it shouldn't stay eternally on top.

Other processes can trigger media storage and keep staying active like download manager and drm protected content.

Anyway any quick access to what's happening on our phones,manage unwanted processes or produce logcats and all is good.
[Galaxy S I9000 Android Development] jupiter5700:
It is crazy mediascanner create huge thumbnails file, i think. You can see it huge file in sdcard0/DCIM/.thumbnails/ folder. Normally every time when this file is deleted it created again when phone started, and by some other events. But sometimes mediascanner becomes crazy, and started every phone starts, i think it a bug.
[Galaxy S I9000 Android Development] Rokostar:
I like your kernel it gives good gaming power but why you dont include touch wake thats a very amazing feature
[Galaxy S I9000 Android Development] Bejda:
Replace .thumbnails folder with a .thumbnails file is the workaround for this,definitely.
[Galaxy S I9000 Android Development] kasper_h:
It is included....

Mackay settings in Mackay ROM can activate it.

Pawitp recently mentioned that this is a complicated general issue that is not easy to really solve.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] GrippingSphere:
Confirmed. Touch wake also works on other Roms. Can be activated via NSTools or flashing ariesparts2.zip.
[Galaxy S I9000 Android Development] Bejda:
Yep it seemed (i understood nothing lol),btw we can see he shown some interest for the submitted patch [MENTION=4794588]jupiter5700[/MENTION] linked in cm10.1 thread..let's see what will happens.

But as workaround i've been using "replace DCIM/.thumbnails/.thumdata***" method for a long time and it was for sure better but it happened somehow that my blank .thumbdata*** file was sometimes deleted and another big .thumbdata*** recreated.

Now i use "replace DCIM/.thumbnails folder with a .thumbnails file" method [MENTION=4823985]ts1506[/MENTION] once mentionned and it seems really definitely "solved" for me + for now i didn't see any downside using that trick.

So even if the patch solves for real the issue and let us having a normal .thumbdata** file i think i'll let it run for a while to see how it behaves now but will be probably soon back using the trick..sd space is so precious for me ;)
[Galaxy S I9000 Android Development] thETImo:
Anyone switched recently eg. from a 16GB SD to 32 GB one? How much longer the media scanning takes? Is it twice as long as before or something else?

I understand we usually have the same amount of data immediately after the switch.

Sent from my Nokia RinGo far far away...
[Galaxy S I9000 Android Development] dark_knight35:
I don't seem to have that file :confused:
[Galaxy S I9000 Android Development] dejan-:
What's that Touch wake for?
[Galaxy S I9000 Android Development] thETImo:
You touch the screen and the phone wakes up. You figure out the way it serves you best. When using a holster like me, it's not very practical...

Sent from my Nokia RinGo far far away...
[Galaxy S I9000 Android Development] dejan-:
hmm i'm touching the screen and nothing happens ? ...how should that touch wake work ? :o ...but more important question...what's good for ?
[Galaxy S I9000 Android Development] kasper_h:
I think that if you don't understand why to use it you should not :)

It only works if you enable the feature explicitly, and it only works for a predefined time period (in ms).
[Galaxy S I9000 Android Development] dejan-:
i won't use it...but i like to understand and know all the features that rom gives...u know....to understand what and why ...