yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] stueycaster:
The Charge was doomed from the start. Samsung rushed an inferior product trying to have something for the emerging 4g network.

I had to use mine for a few days because my Note 2 was having a smashed screen repair. I don't like the Charge anymore.
[Verizon Droid Charge] usererror404:
Jesus ****, can you just change your name to Buzz Killington already?
[Verizon Droid Charge] kynalvarus:
Actually, I was working on this for a while on Sunday. It's not quite dead yet.
[Verizon Droid Charge] usererror404:
HOT DAMN. deafptl4ever, SUCK MY SUNSHINE.
[Verizon Droid Charge] kynalvarus:
You'll have me until mid-August at least. I'm waiting to see what the new model year of VZW handsets look like before moving on from the Charge, and we have likely August releases leaked by Moto, and IIRC HTC (though maybe HTC is September, and LG August. Can't remember.)
[Verizon Droid Charge] runningman04072013:
That's awesome!

And if you cannot cook something up, that's 100% okay as well. The Charge is a grandpa in today's market. One of the first 4G phones with a front facing camera.

I will also be looking at the newer devices coming out at the end of this summer, especially after the announcement of the new renewal programs.
[Verizon Droid Charge] JihadSquad:
HTC one on August 1, moto x on 22nd, Droid RAZR ultra and maxx probably past September, according to a leaked verizon road map on Reddit.
[Verizon Droid Charge] sshafranko:
So Kyna will we be blessed with a Lazarus recharged for the FP8 build? My wife and i used to run the Charge with Tweaked and PBJ back in the day and now our son and daughter have them. Running Eclipse on FP8 for now but could use a nice kernel. Fingers crossed.
[Verizon Droid Charge] kynalvarus:
Sorry about the continuing delays, but my Android build box is having problems. I had everything working properly in a Fedora Linux partition on my Toshiba laptop. However, the march forward of Linux versions has broken my laptop's fan control module, and it's no longer supported or updated. As a result, nearly every time I try to rebuild a kernel, it overheats and shuts down. :(

I'm setting up to migrate the whole build environment to a VMWare container so that I can move it to newer hardware without losing anything. I expect to have that done Saturday, so I can resume testing FP8 kernels after that.
[Verizon Droid Charge] sshafranko:
Thank you very much and sorry about your mishap. Hope it works out ok.

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Droid Charge] kynalvarus:
It's not really a mishap, just an annoyance. A full build takes 10-15 minutes of 100% CPU (on that system), and when the fan isn't working, even the external fan I have under the laptop just can't always keep the system below its hardware drop-dead cutoff of 90C. It's frustrating to have to wait for cooldown, then restart the system, sometimes multiple times, for each test. Getting everything virtualized will be better in the long run. It just takes a little setting up, to duplicate the partition scheme and then copy everything over from the old metal to the new virtual container.

I just hope that I got all the changed binaries in their correct place, this time... the last time I had time to work on this, it all got eaten up by overheat-crashes, so I never actually got a testable build to try. Keep your fingers crossed!
[Verizon Droid Charge] sshafranko:
I will. Thnx

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Droid Charge] jco23:
you, sir, are a trooper!

when you do unveil your glorious work, make it available for everyone except for deafptl4ever
[Verizon Droid Charge] jheide44:
/me crosses fingers

:)
[Verizon Droid Charge] kynalvarus:
The good news was that the virtualization of my build system went smoothly and successfully.

The bad news is that two more build attempts failed to boot on the FP8 Charge. I'm still hunting the cause(s).
[Verizon Droid Charge] sshafranko:
Glad to hear the good news. Fingers crossed for the bad news.

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Droid Charge] jco23:
curious to see if the kernel you create will automatically convert the system to EXT4? of course, I understand that first things first - just trying to get to boot....

thanks!
[Verizon Droid Charge] sshafranko:
Anu news kyna?

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Droid Charge] fxmech:
I am mainly posting to the thread to show my general interest in the project. My Charge is new to me, a stand-in for my Bionic that came swimming in the Gulf of Mexico with me.

I'll be loyal to my unlimited data plan, which will not continue if I get a 'deal' on new hardware upgrades.

I'm excited to try a custom kernel. The Bionic had a locked bootloader, so this is a luxury I have not been able to experience.

Can I downgrade to the FP5E update and maintain acceptable service through Verizon? Is it recommended versus the stock FP8/Tweaked 1.0 I'm currently running?

I would certainly enjoy having a faster filesystem...

Anybody with their Charge still active that's willing to advise on the matter?

Sent from my SCH-I510 hand-me-down
[Verizon Droid Charge] mddexter:
I suggest you Odin to stock, take the OTA's to FP8E, and run tweaked lite. It is faster than FP5E and more stable. Here is a link to tweaked lite.

http://xdaforums.com/showthread.php?p=46316387
[Verizon Droid Charge] chefthomas99:
Like a boss. :thumbup:
[Verizon Droid Charge] kynalvarus:
There are free Fast Charge apps in the Play Store. Look for ones that specify needing a fast charge kernel, my patch complies with that community standard.
[Verizon Droid Charge] kynalvarus:
Visiting my in-laws, no time to code right now. Sorry... will do soonest.
[Verizon Droid Charge] Son of Cicero:
Is there away to undo this change?
[Verizon Droid Charge] kynalvarus:
rm /system/lib/modules
[Verizon Droid Charge] kynalvarus:
S39force_fast_charge:

#!/system/bin/sh
#Script to activate force_fast_charge on boot via init.d

busybox echo 1 > /sys/kernel/fast_charge/force_fast_charge

That should make fast charging active by default on boot.
[Verizon Droid Charge] deafptl4ever:
Poor guy, with your in laws!!! I would rather eat snails raw than be stuck with my in laws. My visits with them are short and sweet. LOL

Sent from my Verizon Galaxy Tab 2 7.0 LTE by Premium XDA application. Capize???
[Verizon Droid Charge] stueycaster:
Do you do this in terminal?
[Verizon Droid Charge] dSlice:
No, use Script Manager and make a new script in the init.d folder. Using what was posted.

Sent from my N7 powered by AOSPA and M+ Kernel.
[Verizon Droid Charge] stueycaster:
I don't know how to do this. I tried this:

I opened SManager Ads

Navigated to init.d folder

Pressed the plus and typed in: S39force_fast_charge

Then it came back with this:

Could someone please tell this newb what to do from here?
[Verizon Droid Charge] bvsbutthd101:
Gotta press "Brick" to continue like it says.
[Verizon Droid Charge] je2854:
just scary just reading this, although amusing and funny at the same time!
[Verizon Droid Charge] dwitherell:
I'll get a file up tonight that people can get via tweaktools
[Verizon Droid Charge] lukegman:
turned on zram...going to give it a try
[Verizon Droid Charge] stueycaster:
Ok I pressed " Brick" and it put a file in. But then I couldn't figure out how to add the script to the file. I'd really like to know how to do this. My newbness bothers me so I try to learn all I can.
[Verizon Droid Charge] lukegman:
rather than start a new folder yu can add

#Script to activate force_fast_charge on boot via init.d

busybox echo 1 > /sys/kernel/fast_charge/force_fast_charge

to the bottom of one your init.d scripts... basically your asking busybox to change the 0 to a 1 at start up in the force_fast_charge file...from what I gather from reading the scripts the # is just for titles... if you do make a new file using script manager go to the init.d folder and

press menu... more... advanced... mount system as rw...press menu again... New script... put your file name...write script... save... then long press the file and set properties ... reboot

properties look like

xxx

x x

x x

I hope this is my last edit
[Verizon Droid Charge] dwitherell:
...and done :)
[Verizon Droid Charge] lukegman:
now stueycaster doesn't have to play with scripts?...
[Verizon Droid Charge] stueycaster:
I wasn't having much luck figuring it out on my own. I'll learn it someday though. Thanks. Actually I like playing with scripts. SManager is a little weird though.

I was able to make a file that had the right script in it. It just didn't become an init.d script. If I had got the permissions right would it have worked? Also I couldn't figure out how to set it to R/W with SManager. I set it to R/W in Root Explorer then switched to SManager.
[Verizon Droid Charge] stueycaster:
If I would have had time to deal with this I probably could have done it with these instructions. Thanks man. :D

I saved your instructions for the next time. Thanks again.

Update: My curiosity got the best of me. I removed the script that I got from Tweaktools and redid it using these instructions. It seems to have worked even though it kept saying I didn't have permissions to access or write. When I told it to open the file directly it went ahead and opened it and allowed me to edit and save. Then when I viewed it it all looked right. I reckon it's probably going to work.
[Verizon Droid Charge] lukegman:
yes... it will...if you don't like the message it says... X all the properties boxes... write your script... then reset your properties before rebooting
[Verizon Droid Charge] stueycaster:
That's good info. Thanks man.
[Verizon Droid Charge] kynalvarus:
Okay, folks - I'm back from vacation. I've been playing around with zram and swappiness settings, trying to find a sweet spot. So far I feel that anything much over 96MB does more harm than good. Obviously swappiness and minfree settings matter as well. Right now I'm running 80MB of zram swap with swappiness at 50, and minfree at 12,18,30,50,60,70. Swap is about 2/3 used, and performance is good. I've noted that the swap can make the phone act a bit weird right after boot, which I suspect is due to the system being under a lot of pressure from every single service starting at once while the virtual memory manager swaps like mad. Once the system settles down and the swap winds up mostly occupied by relatively inactive memory pages, it seems to run better.

So, what's next? The floor is open for bug reports and feature requests.
[Verizon Droid Charge] jco23:
thanks for your continued support!

I have noticed significant battery drainage recently (using the christmas kernel on EXT4). I also experience some lag - but I don't think any more than before.

right now, I'm testing the ability to convert back to RFS and then back to stock kernel.

in terms of suggestions, I think a kernel that automatically converts to EXT4/RFS (thus making IMO's kernel obsolete since it is EP4) with no blank screen during boot up would be my preference.
[Verizon Droid Charge] tmanschuette:
I saw something called SBC that seems interesting. It charges the battery slower, but more efficiently (like overnight charging). Maybe some more governors and schedulers to mess around with? Oh and almost forgot, what about the KSM? Kernel Samepage Merging? Orr is that a jellybean only option?

I also agree ^. Would be nice to be able to switch back and forth more efficiently/easily.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] lukegman:
how do you change the values for swap?... or is it preset?... i looked for an app... is there one for setting the zram?...and look at the cache in my phone... it stays that low...i would think caching more would be better... am I wrong?... and HAPPY NEW YEARS! :cool:
[Verizon Droid Charge] kvswim:
Pimp My ROM has an area for that I think. I too would like autoconversion with Voodoo Lagfix. Makes things simple for the noobs who want a file system that doesn't suck.

Maybe get with supercurio and bake a proper Voodoo Sound module into the kernel, even with Voodoo Sound Plus, the side loaded module isn't very good, it's basically amplifier control only. My OG Galaxy Tab has the same Wolfson DAC but sounds twice as good with DSPManager.
[Verizon Droid Charge] kynalvarus:
Interesting. This kernel does have the Voodoo sound v10 module baked in, which AFAICT is the same one that Voodoo Sound Plus installs. I'll have to see if there's a more recent version around.
[Verizon Droid Charge] tmanschuette:
My Voodoo is working fine, and its the free version.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] p2kmafia:
how do you check if zram is on or not? I've played with swap before and know that typing free into terminal shows you whats being used.

I have a class 10 sd card so I'm extremely interested in swap.
[Verizon Droid Charge] JihadSquad:
Hey kylnavarus would it be possible to hack up the battery driver to show charging current? Android devices show this but Samsung and Motorola remove the reading from the driver.
[Verizon Droid Charge] je2854:
can we use something like DarkTremors A2SD?

I use to use it on my OG EVO 4G. It helps move

swap and all that fancy jazz through the app itself.

It worked great. This is the version I used.

DarkTremor A2SD
[Verizon Droid Charge] crovax33:
What's everyone's battery life like with this kernel?

Since switching I am seeing an unprecedented level of drain. Probably been on it for 4 days now, and it's killing me with the low battery life (can't make it through the day with data turned on).
[Verizon Droid Charge] p2kmafia:
Same boat. Woke up 4 hours ago battery at 17%
[Verizon Droid Charge] Antoneus1231:
. :: TSM Tweaked 3.2 ext4 . Lazarus 1225 . ADW EX . Vanilla Bean :: .

Smartassv2 sio. 100 min 1200 max

This kernel does seem to be a little more "thirsty" when it comes to power compared to stock but not as bad as I've seen in the past. :thumbup:
[Verizon Droid Charge] Antoneus1231:
. :: TSM Tweaked 3.2 ext4 . Lazarus 1225 . ADW EX . Vanilla Bean :: .
[Verizon Droid Charge] je2854:
I have made a zram flashable. Instead of manually editing the files it will flash 32mb, 64mb or 96mb zram swap files where needed.

make sure you mount /data first. I have tried every file first (as I always do) before I uploaded them.

I see a difference after a couple of boots with each boot consisting of about 30-45 minutes of run time.
[Verizon Droid Charge] p2kmafia:
sweet! I appreciate it man. How do I know if it worked?
[Verizon Droid Charge] je2854:
there really isn't a way unless you go to /data/local/ and see that there is a "zram" file.

I flashed every single file to make sure and verify it works. Inside the file is the corresponding

number for the respective swap amount.
[Verizon Droid Charge] stueycaster:
The Lag Reducer made it to Life Hacker.

Seeder Kills Lag in Android
[Verizon Droid Charge] dSlice:
Any way to implement the ROW scheduler?... http://lwn.net/Articles/509829/ I'd be interested to see how our phone runs with it. It sounds promising.

Sent from my AOSPA N7 controlled by Metallice's a28 Kernel.
[Verizon Droid Charge] dSlice:
It just got debunked, it's on the home page of XDA.

http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/

Sent from my AOSPA N7 controlled by Metallice's a28 Kernel.
[Verizon Droid Charge] stueycaster:
I went to Tweaktools and did lag reducer undo and the S99rngd script is still in the init.d folder. Can I just delete that script and be alright?

According to the article it could run down your battery. Mine seems to be draining a little quicker than usual.
[Verizon Droid Charge] tmanschuette:
That's what I did. Do that and reboot. Init.d runs on start up, so if it's not there, it won't run.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] stueycaster:
Yeah I knew that. I don't know why I was being so wimpy except for my Charge is my only phone. Actually it has been acting a little strange lately.
[Verizon Droid Charge] tmanschuette:
Understandable

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
I'll have to see if it's compatible with the 2.6.35 kernel.
[Verizon Droid Charge] CalPolyRock:
Possible fix for slowness

So I've been pulling my hair our over the last few months. I could run the stock kernel but not PBJ or the latest Lararus kernels. On PBJ, things would come to a crawl, with major lag. On Lazarus, once apps started on boot it would quickly slow down to the point where it starved itself.

Monitoring logcat and dmesg during boot, Lazarus would start up fine, but then quickly run out of memory until the point where it would start to kill everything in sight, and eventually it would crash when it killed the acore. It appeared to be some type of memory leak?

I the past, I've done not only a cache wipes, but a complete factory wipe (when I moved to Tweak3). But, it didn't help. I tried dSlices tweaks and every other tweak, minfree setting, messed with autostart apps, app killers, etc.

Yesterday, I tried something that I wish I would have done earlier. I wiped my SD card. When you wipe cache, it doesn't appear to touch the SD card. (I could be wrong there). Either way, there's a lot of old stuff on the SD card.

Ever since that, Lazarus seems to be working great. After a few hours, I added the dSclice init.d and build.prop scripts. Still good. I woke up in the morning, still stable.

My theory is that the PBJ & Lazarus kernels looked at the SD card more than the stock kernels did. Maybe there was some config stuff or cached files in the /Android folder that was screwing stuff up? I also think that the PBJ/Lazarus kernels handle out of memory situations differently, whether it's simply the minfree & other kernel settings, or kernel code mods made by imnuts back in the day. Either way, with my old SD card in, the kernel would start running out of memory, start killing everything in sight, and eventually (apparently) itself.

I haven't seen a suggestion to wipe the SD card if things run very slow or come to a halt. So, for those who are having issues, even after a wipe, try this. Thanks.
[Verizon Droid Charge] kynalvarus:
I did notice that my phone got a lot happier after I did some cleanup on the SD card. I pulled it, ran a scandisk on it from a Windoze box, then wiped out a bunch of old files that hadn't been touched for months. A full wipe may not be necessary to see big improvements.
[Verizon Droid Charge] cujo6801:
Too funny I cleaned up my SD card last weak and noticed the same results ..

SENT FROM THE DOG POUND
[Verizon Droid Charge] Reilly1812:
That's why I clean up my app caches and anything else I can as much as possible. The more crap the system slogs through the worse the performance becomes. Kind of like windows running background indexing. Slows everything down and it gets worse with every GB of data stored. I/O on our phone, rfs or ext4, is less than stellar.

Still Charged Up
[Verizon Droid Charge] crovax33:
I am having serious stability problems with this kernel, on top of the terrible battery life. It has made the phone nearly unusable.

Is there any way to get the stock kernel back besides fully returning to stock and taking the OTA?
[Verizon Droid Charge] CalPolyRock:
Yes, there's a simple stock kernel only FP5 zip. I don't have time to look up the link but it's probably here and on rootz.

Still running the under appreciated Droid Charge with the appreciated Tweaked 3.2
[Verizon Droid Charge] dwitherell:
Check the OP of Tweaked - there's a link to the stock FP5 kernel there.
[Verizon Droid Charge] stueycaster:
Thanks for this. I didn't remember if I turned off indexing the last time I set-up my computer or not. Sure enough I hadn't.

---------- Post added at 07:59 AM ---------- Previous post was at 07:28 AM ----------

I did that a few months back. I removed about 10 GB of useless junk that had accumulated from flashing different roms and stuff plus a few movies. Now that I think about it, It's been running good ever since.
[Verizon Droid Charge] kynalvarus:
Sorry it's not working for you, but I can't help you without crash dumps.
[Verizon Droid Charge] lazarus0000:
For my part, I'm not seeing any difference between the Laz kernel and stock except for being able to use SetCPU & Voodoo Sound. Battery appears the same, no lag, etc... No problems noted @ all.

Occasional weird behavior but I attribute that to making demands on this phone that the hardware is ill equipped to handle.

Tweaked 3.2, Lazarus1225, rfs, Red JellyBean, ADW Launcher
[Verizon Droid Charge] je2854:
I have a 64GB SDXC Ultra Class 10 with sooo muchhh data

but I do not see any performance hit. Do you you

think it is because of the speed of the card? Or the type

of card it is?
[Verizon Droid Charge] cujo6801:
Probably both...

SENT FROM THE DOG POUND
[Verizon Droid Charge] crovax33:
It wasn't really crashing.

The issue I was having is that the radio was cutting out, and calling anyone would take up to 4 minutes for the dialer to actually go through and start calling. I would send a text and it would be 'pending' for ~4 minutes as well.

Plus I was losing battery life at a rate of up to ~20% an hour without any real use (no phone calls or browsing).

Returned to stock and it has been solid again.

Maybe I'm an isolated case, but this version didn't work for me. I'll try out the next iteration.
[Verizon Droid Charge] kynalvarus:
@crovax33, that's very interesting. Are you certain you're on the FP5E radios? You can check in Settings -> About Phone -> Baseband version. It should read "i510.06 V.FP5" on the first line. Also, are you running any tweaks that change the scanning intervals for networks? Many of these hit the build.prop, which is part of the ROM, not the kernel.

If that's not it, maybe there's something else going on in your configuration that's stressing these kernels. I once ran into an issue similar to what you describe. It turned out that I had a badly behaved app constantly hammering on my network connection, causing rapid battery drain and huge lag on any radio operations. I fixed the app and the problem cleared up.

Another time, I ran into issues with memory pressure that were causing me to miss text messages and phone calls. There were so many services constantly jumping up that memory would get low, and the OOM killer was zapping even essential services from time to time. I had to go through my widgets and services and pare down the ones I didn't really need, that time.

I don't know that either of these are happening to you, but they're possibilities. If you can extract a dmesg dump while or just after experiencing extreme dialer lag, that would go a long way to diagnosing the problem. You can run dmesg in a terminal emulator, or through adb shell, or through some apps - I know of one app called "Live Dmesg" that might work for you. Dmesg will tell us what the kernel is doing when it's struggling, including OOM kills and driver warnings.
[Verizon Droid Charge] kynalvarus:
Quick question for y'all: Dropbox doesn't give me any feedback on download attempts and number of downloads. Can any of you recommend a better file sharing solution?
[Verizon Droid Charge] dSlice:
GooManager...

App... https://play.google.com/store/apps/details?id=com.s0up.goomanager

Site... http://www.goo.im

Sent from my AOSPA N7 controlled by Metallice's a28 Kernel.
[Verizon Droid Charge] crovax33:
Interesting. I would be happy to do this if I experience the same issues with the next version. I know I was on FP5 kernel, because when going to tweaked 3 I returned to stock and took the OTAs. It says FP5 now under kernel # in about phone.

For now I am going on a business trip so I need the phone usable and can't return to the laz kernel to test.

Since returning to stock, my battery life is at least 3x better and all the radios have been working flawlessly. Again, may have been an isolated problem for me, but for now I'm just happy to feel confident I'll be able to call people again.