yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] xdwxrd:
I have definitely noticed an improvement with the last couple of zcache versions, especially when switching between apps.

First of all, I'm convinced that the phone is generally much nippier with zcache enabled. I know you can't prove or disprove that a kernel 'feels' more responsive, and it's possible I'm just experiencing a placebo effect, but I imagine it's the difference between having 40 mb of free memory and ~60mb. The phone chugs far less frequently, even after several days of uptime.

And there is one verifiable concrete improvement which can't be dismissed as subjective: when opening the recent apps switcher the vertical list populates instantly, whereas on the non-zcache editions (and on the latest Trinity kernel) there's a one or two second delay before you can scroll up past the first four recent apps.

I'm on knzo's 4.1.2 MDO rom, and over the past few months I've tried zcache Marmite, Trinity (Alpha1c and Alpha0c builds, using the black screen fix since there's no CM version), and vanilla Marmite. I'm confident zcache Marmite is always quickest when switching apps and populating the recent apps list.
[Nexus S Android Development] :
That's really excellent descriptive and specific feedback, which is very much appreciated now that I don't own the device. :)

Anyone else care to flash back to a non zcache version to confirm?
[Nexus S Android Development] polobunny:
I don't know if you guys can use it, but on the S3 forums we often use Trickster Mod to manage our kernel settings, including zcache. Might be able to switch it on/off in an instant with it.
[Nexus S Android Development] :
It's not possible with the way I've coded it, it's permanently enabled
[Nexus S Android Development] polobunny:
Alrighty. You crafty rebel coder. :p
[Nexus S Android Development] :
Hehe, I do such dirty work...
[Nexus S Android Development] crinoz:
Bedalus, i use the last kernel with jellyshot. For the first time i am in a zone with umts 900, another crap motorola get the network, my nexus s 9023 doesnt.

Its possible that the radio in the kernel is for market external the europe and works in 850umts only? (In europe some channels of gsm 900 switch in the next months to umts 900, much better inside buildings)

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus S Android Development] apatal:
Being able to scale up to 100% is not necessarily a bad thing, as this will allow your phone to finish its task more quickly and with less CPU cycles. Search for the race-to-idle principle to get more information on this. :)

Sent from my Nexus S
[Nexus S Android Development] :
I found ondemand to be the most power saving governor in my studies. SmartassV2 best performing and most power-saving of the high performance governors, but it's not the first time I've heard reports of stuttering. I will check into the supplied parameters, which may be at fault.

It's true, I'm borrowing code from all over the place, but I'm not a dev, I'm an enthusiast. I wanted to make a kernel with only the attributes I personally value, but I'm happy to share!
[Nexus S Android Development] DaXmax:
Awwww, that sweet! :P :)
[Nexus S Android Development] :
Update coming, but no oc yet...
[Nexus S Android Development] :
Update is here: http://d-h.st/ZMF

v0.6 has MTP working (and probably PTP too), for ROMs that support it. Slim ICS for example! As far as I know, Krarvind is the one who made this work, with the help of another dev, so kudos to them.

What is MTP? Microsoft's Media Transfer Protocol. It allows for dramatically faster transfers too the phone, so it is really good when you are copying over films or mp3 folders. What's really good is that you can continue to use your apps while these transfers happen. Faster? More functional? You bet! The limitations are that it is relatively unsupported on non-Windows platforms. However, you can investigate these possibilities:

Ubuntu: here.

Mac: here.

Go to Settings>Storage>(Hit capacitive menu button)>USB Computer Connection to select.

Other tweaks

SmartassV2 values tweaked to what appears to make more mathematical sense.

Hopefully if there are any regular users of smartassV2, you can test this and see how it compares.
[Nexus S Android Development] madd0g:
Does it work on CM9 ?
[Nexus S Android Development] :
It's working for me. Wipe cache?
[Nexus S Android Development] :
I believe so... Go to Settings>Storage>(Hit capacitive menu button)>USB Computer Connection to select.

It should work! Let me know how it goes. Thanks!
[Nexus S Android Development] madd0g:
Now it's "Silverstone on telly" time, I'll let you know later, thanks :]
[Nexus S Android Development] DaXmax:
So the new marmite has 1.2ghz stub?
[Nexus S Android Development] :
I'm doing that in v0.7 which I'll work on later today.
[Nexus S Android Development] y3mita:
works fine now on .6 with daxmax ROM
[Nexus S Android Development] madd0g:
Well I'll be damned, MTP works on CM9, mounted correctly, could copy and delete a file to phone without issues from Windows7. Another point that I don't need to switch to GN. I'll stick to this kernel now then, thanks alot ! :]

P.S. Hope you'll continue with JB kernel :P

[edit] Only issue is, that after you connect with MTP once, it doesn't recognize the device at next USB connection, dunno if this is a MTP issue or this Nexus S implementation thing.
[Nexus S Android Development] Oodie:
I suggest that This thread should be moved to the Developer section .
[Nexus S Android Development] :
v0.7 is here: http://d-h.st/BPP

For daXmax, enjoy the 1.2Ghz!

But I won't be adding further, because I never personally use it.

Nice to hear that MTP/PTP is compatible with other ROMs. Just remember who we have to thank for this great innovation: thanks to krarvind and co.!
[Nexus S Android Development] DaXmax:
Thanks! Now we have M1200 and M1000 yay! ^^
[Nexus S Android Development] :
To be honest, i hadn't tested that. If you find a workaround let us know!

Edit: wait, i think i know how to fix this issue. I think you can either stick it in another port, or wipe a registry value... I'll look into it
[Nexus S Android Development] caliban2:
I can't thank you enough for including MTP-support! Finally, decent transfer speeds without booting to recovery. :) I also noticed a big increase in I/O-operations, coming vom matr1x-v22. Everything, but especially app-installation, app-start & loading of long lists is so much faster now.

But what the heck is this doing in general-section?! :confused:

---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------

Don't get this, works fine on every connect (XP and W7-machine).
[Nexus S Android Development] madd0g:
Yeah seems odd, I enabled UMS and it didn't recognize the phone, then I restored the nandroid with the stock CM9 kernel and even then it didn't recognize the phone. I rebooted Windows and UMS works now, so I guess it's a Windows issue. Going to flash this kernel again and do some more testing.
[Nexus S Android Development] :
Thanks!

Did you try disconnecting the cable, switching from mtp to usb, then reconnecting? And visa versa? Does it accept the different type of connection on the same usb port?
[Nexus S Android Development] :
This won't work because no matter what you set, those settings are stashed, and then new settings applied before the ui is suspended. Maybe try it with a different kernel, and see if it is stable at 400MHz. And check using CPUSpy that it is accumulating 400MHz time as you would expect.
[Nexus S Android Development] :
Jesus. Make sure you use Team Win Recovery Project to do at least one full backup including your efs folder, and backup your backup onto a computer. You don't want anything happening to your IMEI.

Is this with ICS?
[Nexus S Android Development] alen1901:
Doesnt nandroid backup with touch recovery backs up efs too? Yes, on cm9 rc2. Tommorrow i will backup efs with some tool. Strange thing is that there wasnt any kmsg. It was 0bytes. Also emtpy when i entered command in terminal emulator(nothing happend).

Sent from SpeedMachine i9023
[Nexus S Android Development] :
It's difficult to say what caused a reboot if there's no last_kmsg. It means that it the kernel was unable to handle whatever went wrong, and never reached the routine that backs up the logs.
[Nexus S Android Development] alen1901:
Now just wait for about 50,60 hours of phone usage, maybe it will happen again.

Sent from SpeedMachine i9023
[Nexus S Android Development] pan1980:
had no problems with matrix 22 and 400mhz screen off / performance gov during night.

this morning did a 2 hours music playback test without any problem too.

of course deep idle is enabled in nstools

i have to full charge the phone and repeat the music test with and without the screen off profile in airplane mode to see if there is any difference in battery performance.
[Nexus S Android Development] :
Yes, you can do that in other kernels, but check with CPUSpy to see if you actually do accumulate time only at the 400MHz step when the screen is off and music is playing, otherwise your SOP isn't working.

SOPs won't work with my kernel because of the way I programmed it.
[Nexus S Android Development] :
Here is v2.2 (TEST/EXPERIMENTAL): http://d-h.st/zGb

It is based on cm again (I found that using the air base seemed to cause frustrating lags. I'm sure r_data's own version is working well though - I probably did something wrong :p)

I've disabled the code that allows entry to DI mode, so even if you enable DI your phone won't be able to enter it. This is just a precaution against the crashes caused by DI at the moment.

KEEP DI DISABLED. Ok, it won't crash your phone if you accidentally enable it, but it will use more power because I didn't disable the code that fixes it at 800 MHz.

When thalamus has polished up IDLE2, I will apply his patch, then check by measuring the amps that it is indeed saving power (just as a secondary confirmation; if you follow his threads you can see evidence that his patch is already working well.)

I've also disabled BIGMEM for this one. I want to see if that is what prevents i9023 users from booting. Please test!

EDIT: Looks like thalamus has issued the entire patch: https://github.com/thalamus/android-kernel/commit/55ac0860cebac636159367d374cb9a7186874c06

...It's really interesting to see how he's coded this. I was looking for a way to modify my cpuidle.c code to enable DI if music was playing, which you can see here: https://github.com/bedalus/bedalusKERNEL/commit/9eb33ef1a9fb7fa652e87cef0ae4822cf54bd39f

...but thalamus approach was to modify the audio stream code to talk back to the idle code. Genius!

I've felt like quitting this project because my programming is so awful... but at the same time it's really interesting to have a go, then see how the professionals did it.
[Nexus S Android Development] N@th_OC:
That's great, keep thinking like that and your kernel will be one of the best.

"modify the audio stream code to talk back to the idle code": this man his incredible. I looked into his patch trying to understand how is working since yesterday, and it's really an impressive work.

I'll test your new kernel and give you feedback.

you think you'll relesase a kernel with the new IDLE2 patch today?
[Nexus S Android Development] :
I'm going to try, but I've only got an hour to do it... Like Jack Bauer.
[Nexus S Android Development] xjerlzx:
hey bedalus, just wana let u know I'm very pleased with ur v1.4d gives me more performance with similar battery life as compared to matrix =] keep up the work! very keen to try ur jelly bean kernel when restriction remix get into jelly bean.
[Nexus S Android Development] N@th_OC:
:D It's a mission for you bedalus!!

The world need your kernel to survive to the next 24 hours!
[Nexus S Android Development] polobunny:
I got my first SoD yersterday with DI enabled while I was viewing a flash animation. I was busy, set the phone down and the screen timeout came on so the screen turned off. Wasn't able to turn it back on but softkeys would react to my presses by lighting up.

Had to pull battery. Didn't grab kmsg and rebooted since then though. If it happens again i'll try to get a hold of it.

1.4d with cm9 07-23 nightly.
[Nexus S Android Development] tchaari:
Hi buddy,

Sorry I didn't checked my PM since 2 days (I wasn't in my town).

I tried your latest kernels v2.1 is booting fine on my SLCD but not v2.2...

In another topic, I think that this post from thalamus thread may interest you :

http://xdaforums.com/showpost.php?p=29355808&postcount=523

About Wifi, I tested something when I was away the last 2 days. With ICS, I used to lose 2 to 3% in 9 hours when the phone is idle. With JB, I lose from 4 to 5% in 9 hours. I just tried with Wifi disabled always in JB and guess what? I only lost 1% in 11 hours :confused:

I think that there is something wrong with Wifi in JB.
[Nexus S Android Development] :
Okay, I've applied that patch. Thanks!

I haven't looked closely at the wifi-drain. I have PM_FAST, so obviously that uses more.
[Nexus S Android Development] :
Here is v2.3: http://d-h.st/ecB (TEST: i9023 users avoid, sorry!)

-This one features the new IDLE2 code by _thalamus

-DI has been removed (Ezekeel's old version)

-I've also removed my tweak for fixed freq DI due to instability. I don't think I will ever get it to work properly

-based on cm kernel

TO-DO: Bring back bigmem. Figure out what i9023 needs for this to boot up.
[Nexus S Android Development] tchaari:
Nice, I'll wait for some i9023 love :)

I don't know if it will help but I just wanted to notice that thalamus kernel is booting fine on i9023.

When you will bring back bigmem, do you think that KSM is still needed?

I also forgot to mention that the wifi drain I noticed was with the stock JB kernel and not yours :)
[Nexus S Android Development] alen1901:
Someone said before that ksm is worse that bigmem. I dont use ksm on cm9, and i dont complain. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] :
I've always had it disabled. There's a CPU overhead if you use KSM.
[Nexus S Android Development] :
Link removed, still boots only for amoled.
[Nexus S Android Development] :
There's no radio firmware in the kernel. You might want to take a look at this thread though: http://xdaforums.com/showthread.php?t=1116884
[Nexus S Android Development] androidphone2012:
Indeed it is :good:
[Nexus S Android Development] iakoboss7:
this is with bigmem?
[Nexus S Android Development] androidphone2012:
Yeah, 410 MB
[Nexus S Android Development] leap_ahead:
I get 411mb
[Nexus S Android Development] .stendeck:
Okay, what's next about the test kernel? No official successor of 8.7? :)
[Nexus S Android Development] :
I still need more people to confirm about zcache improvements
[Nexus S Android Development] polobunny:
Here's a composition of my own, for the classic rap fans out there titled Linaro 4.8.2 Broke Things (sing on tune of Notorious B.I.G. - Hypnotize):

Beddy Beddy Beddy can't you see

Sometimes your mods just hypnotize me

And I just love your flashy ways

Guess that's why it's broke, and you're so mislaid

/exit
[Nexus S Android Development] crinoz:
Thank you for the tip :)

I have the right radio. Maybe the problem is another. I tried to find the code for the service mode to force the wdcma 900 frequency, but unlucky, i didn find it.

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus S Android Development] :
That's dope
[Nexus S Android Development] .stendeck:
Okay. Want to try again, so I'll run the new version some days.
[Nexus S Android Development] ej8989:
I did a quick A-B comparison on

performance

between your 7/17 kernel @ 1000mhz vs. another kernel i normally OC to 1320mhz and your kernel almost beats the crap out of it. Battery life? I don't know yet. Give me a few days.
[Nexus S Android Development] teoserio:
I'm running it over jellyshot and seems another little step forward to normal 8.7

Inviato dal mio Nexus S
[Nexus S Android Development] spider623:
2 days running and using mtp(remember i use ext4 for the storage) to test some apps, overload the phone, running igo primo and the new gmaps at the same time just to see which is better(igo is but v9 has some voice issues) and generally use it with almost full installation partition, it actually only lagged once but i was sideloading 1 gb using adb and i was also browsing music so yeah it works

out of topic are nexus 4 cursed to have slow delivery >.< in monday the 14 works days are over and the phone hasn't shipped yet caused the boxe had a broken seal and they didn't shipped >.< they will send me the screen protect for free though as an apology
[Nexus S Android Development] :
Looks like more people are in favour of zcache. Any disagree?
[Nexus S Android Development] leap_ahead:
NO
[Nexus S Android Development] kriout:
is the last zcache version the first one you release ( i think it should be the 20 of june ) i wanted to test it on miui v5
[Nexus S Android Development] leap_ahead:
The last 2 test kernel is zCache
[Nexus S Android Development] spider623:
Another 2 or 3 builds and you may end up with a new perfect code, btw any idea how hard patch fuse and ext4 on a closed source Rom like miui?
[Nexus S Android Development] ekerazha:
Yes, performances are worse because less RAM is available so it's easier for the phone to run out of memory and become laggy.
[Nexus S Android Development] Sucky1983:
I've been using the zcache kernel with unofficial carbon for quite a while now. The first zcache kernel was great, better multitasking and about 90-105 mb free ram for me.

With the latest kernel .86 zcache kernel some apps like tapatalk and tweetlanes give me a black screen for 2-5 seconds when starting after a while. this does not happen with the first zcache version.

Maybe it's my rom or configuration, I will do more testing with a fresh install in the next few days.
[Nexus S Android Development] Zahih:
IMHO, For my NS, Marmite 8.7 is more smoother than zcache version.
[Nexus S Android Development] BBuZZ:
I prefer 8.7 also

Sent from my Nexus S
[Nexus S Android Development] pan1980:
bedalus everything is fine with the zcahe kernel, i would dare to say that i prefer it over the normal 8.7.

i have a question though, is there anyway to edit any config file so that instead od 220 fsb use lets say 110 ?

i know my phone can handle 1300ΜΗz cpu, and i know it can handle up t 216 fsb, i want o overclock it but with 220 fsb its impossible whatever voltage i try.
[Nexus S Android Development] leap_ahead:
i don't think u can edit ...
[Nexus S Android Development] spider623:
Try setting it from devil tools or Rom toolbox(jrummy)
[Nexus S Android Development] leap_ahead:
[MENTION=4392547]VerminX[/MENTION] 1320mhz with that voltage 1475 arm & 1225 int I get reboot ...
[Nexus S Android Development] pan1980:
Neither gives any option for Iiveoc
[Nexus S Android Development] lagloose:
Bedalus, you perhaps should consider trying to implement/enable 'cleancache' in context with 'zcache'. Look here: http://git.kernel.org/cgit/linux/ke.../?id=4fe4746ab694690af9f2ccb80184f5c575917c7f and here: https://github.com/brandon14/bkerne...umentation/ABI/testing/sysfs-kernel-mm-zcache

Just an idea...

Greetz

(EDIT: Forget about it... :) obviously already enabled (noticed by calling 'dmesg')...
[Nexus S Android Development] .stendeck:
Now I've used latest test-kernel for ~4.5 days. Still okay, but after ~3 days it's often very sluggish and sometimes it's a pain to use only common tasks like answering the telephone. The days with a longer standby time are gone... the kernel is stable but now you have to reboot to sustain the fun of the phone. :(

Maybe a problem of 4.2.2, too. But couldn't remember that non-zcache version had the same results!?
[Nexus S Android Development] lagloose:
It's absolutely possible that this is caused by zcache which get's 'full' after a couple of days. It's quite similiar to zram/compcache. It gives you 'virtually' more RAM but slows things down as soon as the CPU has a lot to do with swapping and compressing/decompressing memory pages. I didn't have a look at the sources yet but maybe there's a way to force the kernel to 'free' pages as soon as they are not needed anymore. Another attempt could be to ensure that memory compression is only done for services and core apps. But all this is naked theory for now...

Greetz
[Nexus S Android Development] :
There's some really low level memory management functions in the zcache that I don't understand. It'd take me a long time to work it all out. It's taken the developer years to get it from staging into drivers, and I think he's still got plenty of ideas left to integrate, which are waaay beyond anything I understand right now. I think if zcache is causing the system to grind after a few days, then it's doing the opposite of what it's supposed to. Can anyone else confirm?
[Nexus S Android Development] teoserio:
My uptime is 124hours now, i'm running last zcache version you released paired to jelly shot 4.5

I don't feel the NS laggish nor different from when I was running non zcache version.

I think that roms aren't passive with their own tweaks

Inviato dal mio Nexus S
[Nexus S Android Development] .stendeck:
It's hard to find someone here, who uses one ROM/kernel combination for more than a day. ;) But I'm still in testing phase, so now I will retest with 8.7 for a period of 4 days.
[Nexus S Android Development] :
I forgot to say, zcache doesn't give you more RAM, it gives you compressed cache, so if any cache is accessed, once it is finished with, it is stored (in RAM) if it compresses to less than half its original size. This is only useful if that cache needs to be accessed again. It can be pulled from the compressed memory faster than if it needed to be read off the disk.

But it seems like a lot of apps use a lot of cache. I wrote a post about it in the thread not too long ago. So, in losing a little RAM, you gain speed when apps are using (or re-using) cache.
[Nexus S Android Development] polobunny:
I was about to chime in. zcache gives you less ram, but also less read/writes on physical media thus usually higher speed for cache operations. Disk read/writes are still the biggest bottleneck on a lot of devices.

I think we discussed the downside of it though, being that if the compressed data cannot be compressed small enough, it is simply discarded. That means that depending on what you are doing/the type of data needing cache, your phone could be compressing data and not using it at all. That ends up being a higher burden than not having zcache.

As for the lagging, this shouldn't happen. It would be worth checking if your ram isn't nearly full when this happens.

Bed, how much did you reserve for zcache? 10% (~40mb)?
[Nexus S Android Development] lagloose:
Yep, you are absolutely wright. I've read more about 'what zcache is' and hopefully understood now, what it really does. So i was a little too fast with my assertion... :)

However, i tried your zcache kernel with MIUI V5 which is (as you probably know) a really memory hog. I got a noticeable improvement in performance with your kernel. The whole ROM feels smoother. But after heavy playing around with browser, Google Maps and apps which use a lot of ram, the ROM got laggy. After a reboot everything was smooth again. Maybe that the cache which is compressed and stored in ram never gets released for some reason. But that's just a guess... Perhaps there's a flag or parameter in kernel config which controls when 'stored cache' is to be released.
[Nexus S Android Development] :
Did you say you were flashing back to v8.7 to confirm already? If not, would you mind giving it a go to confirm the behaviour is isolated to the zcache version?
[Nexus S Android Development] lagloose:
Sure. will try ASAP and report back here...
[Nexus S Android Development] spider623:
ok this is new, with the latest zram i can actually see the phone app echo from the last call i did every time i'm exiting an app :eek: