yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] CalPolyRock:
I've experienced all of the problems you describe on both the stock and Lazarus kernels. Everything from the radio cutting in & out, to the annoying phone call delay, to missing text messages.

My opinion is that the stock kernel comes with much more conservative and fault tolerant settings. While the Lazarus kernel is optimized and tweaked for speed, the tradeoff seems to make it much more sensitive to worst case low memory conditions.

I think it really comes down to low memory, which eventually hits a critical point where things go haywire, as critical services start to get killed.

Ever since I cleared my SD card, the Lazarus kernel has been pretty good for me. I've removed Go SMS to reduce my memory footprint. I notice the radio go in and out on some heavy apps like Waze, which again points to memory. But overall, I've been able to stick with Lazarus for almost a week.

So, since all things point to memory, I'm wondering if the zram stuff may increase stability (less OOM killing processes) while adding a slight performance hit? I haven't tried that yet.
[Verizon Droid Charge] kynalvarus:
Thanks, dSlice, I just signed up with them and credited you with the recommendation. Hopefully they approve me. :cool:
[Verizon Droid Charge] kynalvarus:
Could be, @CalPolyRock. I have been running with 80MB zram and vm.swappiness at 10, and have had a good balanced performance. I really wouldn't recommend setting swappiness high, as you'd rather the phone not use it unless it's pretty sure the page is inactive. However, I do think it makes a difference.

All you have to do to turn on my zram settings is `echo 80 > /data/local/usezram` then reboot. My script in /sbin/add_zram will do the rest. To get rid of it, just delete /data/local/usezram and reboot.

Also, I think the PimpMyRom app has support for zram but I haven't tested it yet so I can't give directions. If someone wants to give it a shot and report back, I'd love to have that feedback.
[Verizon Droid Charge] thechaoz:
So other then my micro usb port going to out (got two new batteries and a wall charger from ebay which will have to do for now) I'm pretty happy right now. I'm on tweaked 3.1 with dsclice tweaks and stock fp5. My most import thing with these phones is battery, stability, then performance. One thing that drives me nuts is almost daily I miss texts and pictures and sending text messages get "stuck" with the arrow going and going (gosms) and never sending until I reboot or delete message and try resending.

Is there any signal/battery/stability advantage to being on laz/tweaked 3.2 or should I just stay put for the time being? Was stoked about lag reducer which I don't have too much of but heard it's been debunked.
[Verizon Droid Charge] CalPolyRock:
For the SMS issue, install Ghostly SMS from the Google Play. This seemed to work even on my bad days with the old PBJ kernel.

I used GoSMS for a long time. I think part of the problem was that it was fighting to not get killed by the OOM killer and therefore put more stress on the system. I'd be texting and it would exit out while texting or while reading a text. Clearly, it's a heavyweight app, as much of the Go products seem to be. Although I like the themes and pop up text window, I've decided to stick with stock SMS because of the lack of RAM on the Charge.

Lazarus seems to be more fluid and stable after I wiped my SD card and removed Go SMS.

The cool thing about the kernels is that you can very quickly swap them by simply installing the ZIP and wipe dalvik cache to be safe. I can switch from stock to Lazarus and back to stock in <10 min. So, you don't have much of a risk to try it out and see how it does. Just keep both the stock zip and lazaruth zip on your SD card.

As far as battery goes, I've accepted that it sucks and I'm willing to put up with it as long as I have a stable and reasonably smooth phone. I also carry a spare battery when I won't be near a charger for a 1/2 day or more.
[Verizon Droid Charge] thechaoz:
Thanks. Once I got my new batteries from ebay my battery life is def much better so I'm chalking it up to the battery that came with the phone was really old. I've tweaked everything you can (no widgets, autoruns, no synce, better battery stats, removed facebook etc). It's unfortunate that the micro charging port got loose and can't really be used now but with a battery charger and 3 batteries I guess I can live with it, I'm not going to begin to tear apart the phone. I found mobiletechvideos will do it for $35 so I might consider it.

I'll give those a shot, thanks a bunch
[Verizon Droid Charge] tmanschuette:
Just so you know I am trying it from PMR, and I haven't noticed much of a change. I don't want to get anywhere near the higher setting for it.. It only comes with two settings so, it's probably better to do it the other way.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
@tmanschuette, what do you see in /proc/meminfo when running zram through PMR? Do you have a directory /sys/block/zram0, and if so, what do you get if you run `cat /sys/block/zram0/disksize` for their 64MB setting?
[Verizon Droid Charge] kynalvarus:
Here's something I just tried, it seemed to help a bit.

http://code.google.com/p/android/issues/detail?id=37199

I put a .nomedia file in each of a few big sdcard directories that will never have media files, like TitaniumBackup, clockworkmod, newsrob, openfeint, and my eBook dirs (whose covers I don't want in my Gallery.) Media scanning is now quicker and the phone seems a little more responsive in general.
[Verizon Droid Charge] tmanschuette:
Here is the meminfo:

MemTotal: 383744 kB

MemFree: 7184 kB

Buffers: 11640 kB

Cached: 60168 kB

SwapCached: 0 kB

Active: 268876 kB

Inactive: 47244 kB

Active(anon): 236196 kB

Inactive(anon): 13320 kB

Active(file): 32680 kB

Inactive(file): 33924 kB

Unevictable: 4280 kB

Mlocked: 0 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 248600 kB

Mapped: 50204 kB

Shmem: 924 kB

Slab: 12272 kB

SReclaimable: 3768 kB

SUnreclaim: 8504 kB

KernelStack: 4888 kB

PageTables: 13456 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 191872 kB

Committed_AS: 2393656 kB

VmallocTotal: 327680 kB

VmallocUsed: 77164 kB

VmallocChunk: 196612 kB

But I didn't have the zram file.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
It looks like it did nothing to generate swap, because you don't have a positive number under SwapTotal or SwapFree. It's possible that PMR expects a later version of zram than the one I found which works under kernel 2.6.35, one with a different interface.
[Verizon Droid Charge] kynalvarus:
Here's mine for reference, with `echo 80 > /data/local/usezram`. I'm going to knock it down to 64MB soon, since I only seem to be using about 40MB of swap most of the time.

# cat /proc/meminfo
MemTotal: 383740 kB
MemFree: 2920 kB
Buffers: 2712 kB
Cached: 63912 kB
SwapCached: 21708 kB
Active: 140404 kB
Inactive: 144552 kB
Active(anon): 110072 kB
Inactive(anon): 112832 kB
Active(file): 30332 kB
Inactive(file): 31720 kB
Unevictable: 4256 kB
Mlocked: 0 kB
SwapTotal: 81916 kB
SwapFree: 48524 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 212792 kB
Mapped: 48844 kB
Shmem: 316 kB
Slab: 13448 kB
SReclaimable: 2968 kB
SUnreclaim: 10480 kB
KernelStack: 6024 kB
PageTables: 17296 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 273784 kB
Committed_AS: 3052416 kB
VmallocTotal: 327680 kB
VmallocUsed: 88612 kB
VmallocChunk: 197636 kB
[Verizon Droid Charge] tmanschuette:
Well looks like one more thing debunked ;). I really don't use heavy apps on my phone, so I really don't have a use for it, but I am glad I could help :)

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] dSlice:
Then you could just put everything in there. I think they even have a notification feature in the app that tells the user theirs an update. Which is pretty cool.
[Verizon Droid Charge] kynalvarus:
I dropped all the GO products last month, after the GO Launcher decided it would rather display silly Christmas-themed animations and slow my phone to a crawl (without being asked) rather than do its primary job. I'm using the LauncherAdvanced beta now and it's much lighter and faster.
[Verizon Droid Charge] jco23:
curious to see if there will be any further updates to this kernel? i was experiencing some significant battery drain and lag while on the 1225 kernel and EXT4. after switching back to stock and RFS, battery is back to normal and no lag. however, my 4G connection is not nearly as strong (but still functional).

thanks!
[Verizon Droid Charge] kynalvarus:
I've been doing some experiments and evaluating for performance and stability. We'll have another release soon, never fear.

BTW, did you clear your Dalvik cache after installing the 1225 kernel? I'm really starting to wonder about it, and there may be enough differences between Stock and custom that the apps have to be recompiled for proper operation after the switch.

Also, I do think that the custom kernel is a bit heavier on memory than stock is. I may not be seeing the same lag issues you are, because I'm running 64MB or 80MB if swap on zram and relieving the memory pressure a bit. I strongly recommend that people try this out before flashing back to stock.
[Verizon Droid Charge] lukegman:
@ kynalvarus.... how do I set the swappiness?... well I have run every script... set my zram to 74...activated swap...tried pimp my rom...looked for a swappiness file to check for my settings... but most importantly I looked to see swap in the memory info... still two goose eggs...so as bad as I want to give it a try... and doing the dance and making a little love to my phone... it seems it will not happen for me because I am incapable of making it happen... oh... and extensive app searching...did I say I tried that route too?... lol!
[Verizon Droid Charge] kynalvarus:
$ su
# echo 10 > /proc/sys/vm/swappiness

will set your swappiness to 10 of 100. This is a good setting for near-real-time VM, as it make the memory manager only swap when it's not very busy otherwise.

The current kernel defaults swappiness to zero. The next kernel release will, in addition, automatically set swappiness to 10 when usezram is active.
[Verizon Droid Charge] jco23:
I did clear Dalvik and all - in fact, I flashed this kernel during the same session as flashing tweaked 3.2.

thanks for your follow up!
[Verizon Droid Charge] CalPolyRock:
Don't forget to do this:

su
mount -o rw,remount /dev/block/stl10 /system
ln -s /lib/modules /system/lib/modules

I didn't know it wasn't enabled until I looked at /proc/meminfo and didn't see the swap being used. After manually trying to run the add_zram script, I saw the mod probe error which caused me to reread the thread.
[Verizon Droid Charge] kynalvarus:
Right, the fix for that is still not released. Time to fix that!
[Verizon Droid Charge] lukegman:
thanks...i was not adding a space in a part of the script...and repeated it (same mistake) over and over :banghead: so now that I have it and know it's working let's see how it goes...
[Verizon Droid Charge] lazarus0000:
64 GB SD for this phone? That works? Samsung says that the phone only supports 32. But I've heard that updates can change that. Are you using more than 32 GB of data on it?

Tweaked 3.2, Lazarus1225, rfs, Red JellyBean, ADW Launcher

---------- Post added at 06:41 PM ---------- Previous post was at 06:33 PM ----------

.no media?

How do I do that? Is it just a text file that I insert into the top directory of each app that I don't want indexed? Do I use a text editor?

Tweaked 3.2, Lazarus1225, rfs, Red JellyBean, ADW Launcher
[Verizon Droid Charge] kynalvarus:
I did it in adb shell, by doing, for example:

cd /sdcard/TitaniumBackup
touch .nomedia

and repeating for every directory that will never have music, video, or gallery pictures in it.

NB: that's ".nomedia" with no spaces and a single period as the first character.

I'm sure you could do this with any app or file manager program that would let you save a new empty file named .nomedia into your directories. You could also do it by mounting the sdcard through USB to another PC and then creating the files via CLI or GUI there. I'm a longtime Linux user, though, and command line interfaces just come naturally to me after all these years. `touch` creates an empty file if none with that name exists, and updates its modified datestamp to right now if it does exist. It's handy for this sort of thing.
[Verizon Droid Charge] lukegman:
I like the command line in the adb shell...as for the zram... so far I have gotten way past the normal freeze spot in my game ski Safari (which always freezes in the same spot) and I have tried alot of changes trying to get it to work...the lag in my dialer is noticeably better... and my app drawer is behaving better... so far so good...

that is what it looked like using the diskinfo app
[Verizon Droid Charge] lukegman:
I think you should make one with it all on I changed swappiness to 20...much better...i haven't got over 40 mb yet... best thing is I started adding tweaks... the tweaks are getting better results... so same tweaks... faster phone...i think a lot of users would try it if you made the kernel with zram on and set with your presets...basically making the kernel better...
[Verizon Droid Charge] kynalvarus:
The reason I'm cautious with zram is that I crashed my phone a number of times by trying to change its settings after boot. Once zygote runs and all the apps and widgets start their services, there usually isn't enough free memory left to allocate a new zram device. Trying to do so and failing causes kernel panics.

Swappiness, OTOH, is safe to change at any time. However, the effect of increasing swappiness is to make the virtual memory manager more aggressive. This means that it will be more likely to grab any given inactive memory page and move it to swap. However, if it grabs a page based on too short of a period of inactivity, then that page will get swapped back very soon and CPU will have been wasted in both directions. Swap helps when the extra virtual memory permits seldom-used programs and cache to stay "in memory" without being killed by the low memory killer, when the cost of frequently restarting them is higher than the cost of swapping them in and out as needed.

Stock linux ships with swappiness at 60. Most of the advice I've had on real-time sensitive Linux recommends a setting of 10, and that's what I use when building database servers or real-time servers for audio/video processing. Settings higher than 10 may work better for some people but worse for others.

In the end, I'm just one guy with one phone and one configuration. I can't possibly test every reasonable combination of settings, tweaks, apps, and usage patterns. I really appreciate it when people like @lukegman try things and report back their results in detail, so please keep up the sharing!
[Verizon Droid Charge] kynalvarus:
Oh, BTW, goo.im approved my request to share files through them. New release later today. Thanks for the recommendation, @dSlice!
[Verizon Droid Charge] dSlice:
I'm glad I could help.

Sent from my AOSPA N7 controlled by Metallice's a28 Kernel.
[Verizon Droid Charge] kynalvarus:
New release posted in OP.
[Verizon Droid Charge] lukegman:
how much later... lol...actually can you show me the script to change zram to 42 kb?... i am trying to trim it closest to the highest it has gotten so there won't be free space with left over file info...
[Verizon Droid Charge] kynalvarus:
echo 42 > /data/local/usezram
[Verizon Droid Charge] kynalvarus:
I noticed this discussion on Charge Forums about battery life - what do you all think of this hypothesis?
[Verizon Droid Charge] kvswim:
This is probably the wrong area to post this, but bass boost doesn't work at all in Voodoo Sound Plus.
[Verizon Droid Charge] tmanschuette:
Try using the free one. The paid one tries to install the sound driver itself, but the kernel already supports it. That's all I can think of, considering I'm using the free one with no problems.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kvswim:
Un installed plus, rebooted, and tried again. It works!
[Verizon Droid Charge] je2854:
I had made flashable zram file with 32, 64, 96MB available that does all the work for you,... check them out.

---------- Post added at 11:54 PM ---------- Previous post was at 11:50 PM ----------

I guess you are asking me this... I have partitioned as follows:

FAT32, EXT4, SWAP

FAT32 = 51200

EXT4 = 6144

SWAP = 8192GB

but I had also used Linux to make the partitions manually... might have done something to do to make it work...
[Verizon Droid Charge] lukegman:
I think sure... alot of discussion is about partial wakeloks...apps (social and free) that do alot of things in the background killing the battery...i don't know if it's your experimental fix... or the apps...now alot of people are talking about wifi robbing battery...as for battery... i went the fixing apps route and kept the 1225...i can remember bone stock cooking in my pocket while words with friends was reeking havoc... SHRIKE led me to better battery stats...very good at finding your problems (apps and other things)

---------- Post added at 09:02 AM ---------- Previous post was at 08:56 AM ----------
[Verizon Droid Charge] jco23:
I too noticed significant battery life decrease on 1225 when compared to the others. regarding hotboots, I still get them from time to time on the stock kernel, so I'm not so sure that it is entirely related to the kernel.
[Verizon Droid Charge] kynalvarus:
The stock kernel has the same bug that causes the hotboots.
[Verizon Droid Charge] dwitherell:
I was going to put those up on tweaktools, but I got to thinking...

I may just add in an option in tweaktools to create those without needing to go into recovery... I know little of the mechanics behind this stuff but would it be a good idea to allow some end-user flexibility in the value? Meaning instead of just 32/64/96, allowing someone to enter in a value (with the don't-be-stupid-about-this warning, or prehaps a limited range (and if so what should it be) where if you go out of bounds in either direction (in case a negative number is put in I suppose?) a preset min or max would be used in its stead)... thoughts?
[Verizon Droid Charge] lukegman:
I think you have good thoughts...swappiness values too... With enable and disable...haven't had the phone store more than 42 mb in the swap file no matter how big it is... so...
[Verizon Droid Charge] kynalvarus:
The interface I created will take any number, no matter how stupid. You just create a file called /data/local/usezram. In it should be a single number. I recommend not going higher than 128, and negative numbers will probably boot-loop your phone. If you set a tweaktools script to permit a minimum allowed of 16 and a max of 128 that would probably cover every reasonable use case. Disabling the system means deleting the file entirely, not putting 0 in the file - though putting 0 in the file probably wouldn't crash anything, it would likely not make anything better and could make some performance worse.

I have personally found that my phone rarely uses 64MB of swap no matter what I do, but it has come close.

A better interface for controlling this is a good idea. I'd rather not put it in the build.prop because the ROM and kernel are not tightly linked. /default.prop is normally not editable by the user. I chose /data/local because it was the same place imnuts put his similar control file for his swap experiments.
[Verizon Droid Charge] je2854:
because of it is his kernel and I have not gotten as far as dev'ing as he has. I think he has a good idea.

If possible make minimum and maximum with a do not be stupid with this post (could cause severe reactions)

before and then an option to completely disable or enable. One of the reasons I was thinking it would be

a good idea to have these is that it is fool proof and even a kid to do this without thinking, Think crapple)

the normal being the 64MB (as everybody seems to like that one better). But kynalvarus has a valid point :b
[Verizon Droid Charge] mrtruckincowboy:
I have lag on the new kernel update went back to 12-25
[Verizon Droid Charge] kynalvarus:
Did you clear your dalvik cache after flashing?
[Verizon Droid Charge] kynalvarus:
More on the battery issue - I just rebooted my Charge and the battery percentage jumped from 24% to 70%. Either this battery is shot, or something's going on with battery level measurement. I wonder if the SVNET_WHITELIST change in the kernel power section (it links into kernel/power/wakelock.c) invalidates the old battery statistics? Anyone else seeing what looks like fast drain that disappears right after reboot?

(P.S. I have a new battery on the way, so I'll be able to test that shortly.)
[Verizon Droid Charge] jco23:
I did notice an odd jump when converting back to stock. Prior to the conversion process, my battery power was around 40%. after installing the imosyen EP4 kernel to convert from EXT4 to RFS, I noticed my battery display at about 70%. then, when flashing stock kernel, it went back down to about 40%.

perhaps there could be some validity to the battery calibration (although, I believe that all it does is wipe the battery stats file, which is what the system should do after completely charging up).
[Verizon Droid Charge] JihadSquad:
Whenever I flash a new kernel the battery level is always wonky until I discharge the battery as far as it can go (idle until it shuts off and then keep trying to boot it until it stops responding). I then bump charge the sh*t out of it so that the phone "learns" the min and max of your battery.
[Verizon Droid Charge] kvswim:
Useless technique of you have multiple batteries, as many of us do.
[Verizon Droid Charge] lukegman:
ok...i am using Tasker so that when my screen is off my data is off...

still losing 10 percent an hour...
[Verizon Droid Charge] JihadSquad:
Facepalm... Still it stops the battery from jumping around on me.
[Verizon Droid Charge] xdadevnube:
Interestingly, I was able to use CIFS (using CIFSManager app from Play Store) with earlier versions of Lazarus and one of the PBJ kernels (dunno which one, and but I think 5/24/12).

I just did a clean wipe and tried loading up CIFS with no luck. I think one of the other kernels on my last setup left a kernel module leftover or something.

I get the error "No Such Device", which generally indicates lack of kernel support.

Does anybody know if the kernel is working with CIFS?
[Verizon Droid Charge] kynalvarus:
CIFS kernel support is still present in /lib/modules/cifs.ko. I was able to open a Terminal session and do

$ su
# insmod /lib/modules/cifs.ko
# lsmod

and the module loaded correctly. However, it was not automatically inserted on startup. @xdadevnube, if you do the above insmod procedure, does your app work again?
[Verizon Droid Charge] xdadevnube:
Sweet! I loaded via insmod in the CIFSManager settings. The start on boot setting is checked.

We're good to go. I should've tried that earlier, but I don't believe I had to after having flashed every FP1 and FP5 PBJ kernel variant as well as Imoseyon 4.0 kernel on that older version of tweaked.

Now I'm running the latest version of tweaked and Lazarus without issue. Thanks!

small doni sent your way.
[Verizon Droid Charge] kvswim:
Can we get a separate, in depth guide to enable swap? I read through the OP and I still don't quite understand.