yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] stueycaster:
This is all I've done. I/O and governor are original. One thing I've been doing for quite a while now is run my CPU at 200 min'. Then I also use it to stream music into my car radio through a car dock a lot so I set it to run at 400 min' while it's connected to USB. That way I can run PowerAmp, Maps and sometimes Speaktoit Assistant simultaneously without problems. It seems to be running great to me.
[Verizon Droid Charge] dSlice:
I had to abort this kernel for the time being, things started acting weird. I forgot to grab a last kmesg before I reverted. I'll be watching the progress. Hopefully whatever was causing issues smooths itself out in a build or two.

Nothing against your work.
[Verizon Droid Charge] lukegman:
ok... One question...can you build it like the 0504 fp1 kernel... it was better than the 0524...the 0524 added low memory killer settings... and some back to stock boot settings... (from the change log)...
[Verizon Droid Charge] tmanschuette:
I doubt he would want to start over, but he may tweak this one for future builds to be how we all like. I'm sure ironing out bugs is his first priority, do if there is something specific you want changed just mention it. You never know what he will put in the upcoming build. ;)

Sent from my SCH-I510 using Xparent Red Tapatalk 2

---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------

Hey dSlice, do you think the low memory settings mentioned above are cladding with something in your tweaks? Since I disabled them my phone has been a little snappier, but I will try them again to make sure.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] SO_dank:
Stupid question when I installed this it took a while to boot I assumed it was ext4 convetsion but I'm not at ext4. Does this put you at ext4 or am I supposed to take another step.. thanks!
[Verizon Droid Charge] dSlice:
Nope, I tried it without them.

Sent from my N7 powered by AOSPA and M+ Kernel.
[Verizon Droid Charge] CrimsonKnight13:
Here's the kernel source repository

https://github.com/kynalvarus/sch-i510_kernel

Thanks to kynalvarus for reviving PBJ on FP5E!
[Verizon Droid Charge] kynalvarus:
No. I haven't integrated supercurio's voodoo lagfix converter yet. If you want ext4, you should install imoseyon's last kernel, let it convert, then install a FP5E kernel.
[Verizon Droid Charge] kynalvarus:
I'm pretty sure I've got the low power mode charging problem licked. I may have fast charging working as well, but the Samsung battery driver doesn't appear to export a charging current figure, so it's hard to be sure. I need to let my phone discharge and charge on AC, then again on USB with fast charge on, to see how the charge curves compare, before declaring success.

Feature requests are welcome. I can dig through the git logs to see what changed from 0504 to 0524, if enough people think that change was not a good one. Thoughts?
[Verizon Droid Charge] SO_dank:
Sorry just to clarify .. go imoseyon then this kernal and it will hold ext4 .. thanks awesome!!
[Verizon Droid Charge] jco23:
0504 kernel worked best for me. i think the most significant change was that the 0524 kernel allowed folks to flash back to stock easier. the lone drawback was an adjustment to the boot animation.
[Verizon Droid Charge] andrewjt19:
Always loved PBJ but didn't seem to work the best after FP5 (at least for my phone setup). Thanks a ton.
[Verizon Droid Charge] bvsbutthd101:
Tried using this kernel and my phone began to run sluggish. Flashed back to the stock kernel and it's running a little faster.
[Verizon Droid Charge] jco23:
how long did you give it? mine was sluggish at first, but smoothed out after about an hour or so.
[Verizon Droid Charge] jco23:
hmmm.. mobile data is not connecting. not sure if there is an outage in my area....
[Verizon Droid Charge] dSlice:
I had sane problem as well...
[Verizon Droid Charge] bvsbutthd101:
gave it a couple days.
[Verizon Droid Charge] kynalvarus:
I've occasionally had to go to airplane mode and back to get the mobile data working again. If someone can capture a dmesg and/or logcat of the problem before I do, that would be very helpful.
[Verizon Droid Charge] stueycaster:
I can't tell any difference. I guess probably this weekend I'll put it back to stock and see if I notice anything.

Update: I just switched to SmartassV2. Thanks tmanschuette.
[Verizon Droid Charge] tmanschuette:
Found this describing the different governors.

http://www.imoseyon.com/2011/10/cpu-governors.html?m=1

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
CPU governors and I/O schedulers are not the same. CPU governors ramp up the CPU clock when needed and down to save battery when not. I/O schedulers handle contention, primarily over the "disks" (which in phones are all varying forms of SD RAM.)
[Verizon Droid Charge] tmanschuette:
It's cool to learn all this stuff. I've got to say I haven't had any off the issues that the others are describing. Just converted to ext4 today, we'll see how that goes.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] ultimatdan:
Just about to try out the new kernel...I wiped the cache, then when i try to wipe dalvik i get this error message:

E:unknown volume for path [/sd-ext]

Any ideas why or how to fix it? I did mount/system but that didnt fix it either.

Thanks.

Oh btw on my Charge i'm using Tweaked 3.1, Jelly Bean theme with the stock FP5 kernel
[Verizon Droid Charge] jco23:
Normal.!

tappin' that....
[Verizon Droid Charge] je2854:
here is a COMPLETE list of governors and I/O Schedulers.

http://xdaforums.com/showthread.php?t=1369817
[Verizon Droid Charge] lukegman:
I remembered on the old 0524 kernel... set the memory to strict... over clock to 1400 and the phone really flies...it seems to still like it

MOST IMPORTANT PART IS THE STRICT SETTING... the 1400 just kills the battery fast
[Verizon Droid Charge] kynalvarus:
Luke, this sounds interesting, but I'm not sure what "set memory to strict" means. Is that a setting in an overclock app you use?
[Verizon Droid Charge] kynalvarus:
Let's talk lowmemorykiller settings for a bit, shall we?

FP5E Stock = 12M, 18M, 24M, 36M, 42M, 48M

PBJ (0504) 10M, 16M, 24M, 44M, 52M, 64M

PBJ (since 0524) = 12M, 18M, 24M, 50M, 60M, 70M

dSlice tweaks = 8M, 12M, 24M, 60M, 70M, 80M

So, it looks like the trend on this phone has been to get very aggressive on the three lower priority OOM categories, while staying near stock or even going below it on the three higher-priority categories. I found that my phone started getting hot boots with the lower-three settings below stock, so I've stopped doing that - and I won't ship a kernel with defaults lower than 12M, 18M, 24M in the first three slots. Anyone who wants that can use Auto Memory Manager or dSlice's tweaks to get it. That said, though, how aggressive do we really want to be on the last three slots? What do we all think is a good balance for defaults here, that will satisfy the less technical among us the best?

Also note, between PBJ0504 and PBJ0524 imnuts changed the setting of /proc/sys/vm/overcommit_memory (set in init.rc) from 0 to 1. This may account for some of the difference in feel that people are reporting. Shall I switch it back for a release and see how that goes? Or are you all feeling l33t enough to get a root shell on your phones and issuing "echo 0 > /proc/sys/vm/overcommit_memory" and seeing how that goes? ;)
[Verizon Droid Charge] kynalvarus:
I should point out that stock FP5E shipped with an init.rc command:

write /proc/sys/vm/overcommit_memory 1

so this was almost certainly inherited into PBJ from Samsung's shipped configs.
[Verizon Droid Charge] kynalvarus:
1219 release posted, see OP for links.
[Verizon Droid Charge] jco23:
does the 1219 release include this switch back?
[Verizon Droid Charge] knodalyte:
I happened to hit the OP again to do the download after reading the thread and found a brand new version. Installed and no problems so far (all of 10 minutes!). I have bumped my clock up to 1200 and voltage -50, let's see how that goes. Using Voltage Control only has 200 MHz increments, I would have tried 1100 first if I could.

Thanks to you and the other folks who are helping us keep this once killer device alive until we can upgrade (2/28/13, but who's counting?)
[Verizon Droid Charge] shrike1978:
I no longer have my Charge, so take all of this with a grain of salt, but I did a lot of experimenting with memfree when I had it, and, for me, this was a very hard phone to balance in that regard. On FP1, I tended toward leaving the bottom 3 numbers alone and putting the top ones around 60,70,80. If I got much lower than that, it would get sluggish on me. If I went much higher than that, it wouldn't multitask for crap.

However, like I said, I don't have my Charge anymore (and haven't since before FP5), so I don't know what the current status of things looks like. I'm just rambling from memory.
[Verizon Droid Charge] jco23:
hotboot right off the bat - but it could be b/c I had the phone docked, and it was trying to determine which dock app to use.
[Verizon Droid Charge] kynalvarus:
1219 has identical memory settings as the prior releases. I wanted to get the fast charge and low power mode fixes out there and testing. We can talk about default memory settings for the next release now.
[Verizon Droid Charge] jco23:
ok.

one thing I do notice in the positive is that my 4G signal is almost on max - yesterday, it was barely holding it.
[Verizon Droid Charge] kynalvarus:
I don't own any docks for the Charge, so I don't know how the fast charge patch will interact with them. I left the car dock code alone, but I did try patching the desk dock callback to respect fast charging mode. Any test reports from the desk dock would be very much appreciated.
[Verizon Droid Charge] kynalvarus:
That's good news.

One of the frustrating things about kernel development on this phone is the proprietary nature of the radio & RFS drivers. We can escape RFS by converting to ext4, but there's no workaround for the RIL drivers. I have to be careful what I change, lest I make something go wrong between the Samsung-shipped RIL kernel modules and the new kernel. In fact, I just finished a whole series of (failed) experiments to see if I could turn off certain debugging modes, in hopes of making a leaner kernel. Answer: nope. Phone refused to boot every single time.
[Verizon Droid Charge] jco23:
understood. I'm not concerned about a fast charge - as I think that could really be cheating the phone. it's kinda like a hangover. you can have all the remedies in the world, but the one that does the best is time.

I'm all for an EXT4-dedicated kernel. mostly for the boot animations. I think it's important to have them (as opposed to blank screens) so that when we flash something, we can see that the phone is actually thinking rather than a possible boot loop or being frozen.

I do notice that the boot animations are somewhat slower (aside from being delayed) that previous PBJs. But these are all minor issues - congrats and thanks on the custom kernel. well done!

---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------

aside from that one hotboot, nothing else different - haven't really noticed the fast charge yet. I'm using desk clock plus for my dock app - and I think it is causing some issues - but unrelated to your work.
[Verizon Droid Charge] kynalvarus:
Fast Charge ships turned off for safety. You have to affirmatively turn it on via a Fast Charge control app or by poking 1 into /sys/kernel/fast_charge/force_fast_charge before it will do anything at all. If you haven't done one of those things, it should not change anything about your phone's operation.
[Verizon Droid Charge] lukegman:
sorry... it's minfree values set by a memory management app... steps of 10...60 70 80...kind of like the values you are already experiencing good results...i have had better luck using an app and only using init.d when I was stuck with a stock kernel...as for undervolting...i tried it and didn't really see much difference...also... When stock I used tegrak for o/c because it works good with Samsung kernels... When using pb&j I use setCPU for o/c...it seems to work smoother when o/c and let's me go even higher values (most apps will only handle 1200 with setcpu I have gone up to 1400 with good results)...
[Verizon Droid Charge] kynalvarus:
I'm working with dwitherell to include a custom kernel with the next release of Tweaked 3.2. Honestly, I know very little about boot animations, how they work, where they're installed, etc. I'm hoping he can point me at the places within the Tweaked ROM where these files live, so we can figure out how to make a kernel that works with both mostly stock ROMs and heavily modded ones.
[Verizon Droid Charge] dSlice:
Time to try 1219... I'm not converting to EXT4, don't need to wipe the phone again, if I feel I need to go back...

UPDATE: So far so good... I'll keep testing...
[Verizon Droid Charge] tmanschuette:
On the topic of messing with memory,I have never had good luck with changing minfree values on my phone. The ones that shipped with dSlice Tweaks seemed a little smoother. Maybe it is just changing them manually versus them coming shipped in the Rom/kernel?

Sent from my SCH-I510 using Xparent Red Tapatalk 2

---------- Post added at 05:25 PM ---------- Previous post was at 05:02 PM ----------

I ran it. I guess we will see what happens? So far so good.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] stueycaster:
I was starting to notice a little slowness in my phone. Then a couple hours ago it locked up needing a battery pull to unlock it. I flashed 12-19 to try it out and hopefully fix it.
[Verizon Droid Charge] ultimatdan:
Boot loop'n

So, im having some trouble with these PBJ kernels 1213,1214, and 1219...not sure what the issue is but after flash one, then reboot and get past the samsung logo...it just keeps trying to boot up but doesnt. I tried wiping data/chache/dalvik and reflashing earlier today (used Tweaked 3.1 FP5 of course) then flashing PBJ again and the same thing ends up happening. Then I tried downloading and flashing Imoseyon's latest kernel (imoseyon_kernel_charge_gb_4.0.0.zip is the latest correct??) to get on EXT4. That kernel worked. ...but then when I try to flash PBJ 1214 or 1219 and I just keep having that same issue of the system not booting (boot looping?) after the samsung logo. I did mount/system and fix permissions during these installs as well. I had no problems when I originally grabbed the OTA FP5 update and rooted with Tweaked 3.1...so now im not sure what the deal is going to this new kernel.

Any thoughts would be great, thanks!
[Verizon Droid Charge] lukegman:
this kernel I have had lags after cleaning caches...A simple reboot seems to work best.

---------- Post added at 04:03 AM ---------- Previous post was at 03:53 AM ----------

get a good app killer... before I added it my phone had 5 programs running and was multitasking too much...froze up...i use active apps widget (just to see how many apps running) and auto killer memory optimizer (set my minfree if yu have something else) ...this also helps my keyboard which was lagging bad (and yes it's swift key... lol).. also I run o/c minimum at 200 after reading your post.. but I run it all the time... good results... thanks
[Verizon Droid Charge] jco23:
Are you able to flash any of the older pbj kernels? If still boot loop, I would suggest flashing via Odin.

tappin' that....
[Verizon Droid Charge] kynalvarus:
Assuming you have a recent CWM Recovery 5 and a computer with ADB, do this, please:

Install the latest kernel (1219).

Let it boot-loop at least once.

Three-finger-salute back to recovery. (Power + Vol Up + Home, let go of Power but keep holding the other 2 about 3 seconds after the Samsung logo appears)

Mount /system in recovery (look under the mounts menu).

Connect USB cable to a computer with ADB available.

Issue the command "adb shell cat /proc/last_kmsg > 1219_kmsg.txt"

PM me the kernel message file you just created.

This has to be done in the recovery boot immediately after the boot loop, because booting to the recovery kernel counts as a kernel boot and the next boot after flashing a working main kernel won't have the crash info buffered in /proc/last_kmsg anymore. You'll know you have the right report if you see words in it like "BUG," "oops," "trace," and/or "panic." Near the end it should mention that it's going to reboot in five seconds.

BTW, this is the trick I used to get the PBJ kernels working again at all. Without this technique to get crash logs, I'd never have figured out what was going on. ;) I really do need this crash dump to be able to help you, though. So far you're the only one who has reported total inability to use this kernel, and I can't find out what's different about your phone without it. There might be personally identifiable info in that dump, though, so don't post it on the thread, just PM it to me. Thanks!
[Verizon Droid Charge] kynalvarus:
I've needed a near-daily reboot of this phone since we went to Gingerbread, no matter which ROM or kernel I've had on it. There's something leaky in the works, but I've no idea what. When the phone starts getting laggy I just restart it and go do something else for a bit. I'd love to track down the issue, but so far I don't even know exactly where to look.
[Verizon Droid Charge] jco23:
Interesting. I've gone days - even a week or so in between boots (on all kernels and both partitions). Although I have not given FP5 pbj Much time, I'm confident that this will be just as successful.

tappin' that....
[Verizon Droid Charge] stueycaster:
I've mentioned before that my Charge is my only phone. Also my wife has health issues. I went back to FP5 stock. When I get my income tax return I plan to get a new phone and keep my Charge for playing with development.
[Verizon Droid Charge] kynalvarus:
Honestly, jco, I think that there's a significant variance in hardware quality in most smartphones. Someone was posting earlier about getting OC to 1400MHz to work great, but I've had two Charges (one when it came out, one warranty replacement) and neither could stay stable at 1300MHz. I suspect that a lot of the differing results we get have to do with very slight differences in hardware stability. That's why I need kmsg/dmesg dumps when things go wrong - because my phone may just not have the same issue, or may be robust in an area where someone else's is fragile.
[Verizon Droid Charge] kynalvarus:
By the way, imnuts is still out there developing PBJ kernels for newer devices. Therefore, I don't want to poach on his namespace any longer, lest there be confusion. The next release of this kernel will be named something else, to distinguish it from other people's work.

My ideas so far for names:

"No Kernel For Old Phones" (HT the Coen Brothers, "No Country For Old Men")

"Gingerbread Hospice" (keeping your old phone comfy until you replace it on contract expiration next year, but kinda grim)

"Lazarus Kernel" (back from the dead!)

"Eleventh Hour Recharge"

"No Jellybean For You" (because Samsung won't release the driver source code)

Any other ones? Which do you like?
[Verizon Droid Charge] xdadevnube:
I haven't had any issues since I installed this over the only FP1 PBJ kernel I could find that supports CIFS. I was seriously stoked to discover that a new kernel with CIFS support is released. Awesome!

Also, I wasn't sure if I was supposed to wipe cache and dalvik, but it is working fine even though I didn't wipe.
[Verizon Droid Charge] cujo6801:
Lazarus Kernel...

Great name..

Gets my vote

SENT FROM THE DOG POUND
[Verizon Droid Charge] coopman999:
Crouching phone hidden kernel.
[Verizon Droid Charge] lukegman:
setcpu is the only app I can get to 1400...others I can't get past 1200...i don't kno why but I can do whatever you need to find out why... logs or whatever...i really haven't had any issues except lag after cleaning caches in cwm...not sure how to help you with that
[Verizon Droid Charge] jco23:
Frankenstein

KY Jelly

GSpot
[Verizon Droid Charge] Reilly1812:
Lazarus

Still Charged Up
[Verizon Droid Charge] kynalvarus:
Just curious, what are you using CIFS for? I've got the support in the kernel but I don't think I've ever used it for anything yet.
[Verizon Droid Charge] apena325:
+1 to Lazarus
[Verizon Droid Charge] Malave:
Lazarus is apt with the incredible work you've done.
[Verizon Droid Charge] dSlice:
So far so good! I think you fixed the issues.

Sent from my N7 powered by AOSPA and M+ Kernel.
[Verizon Droid Charge] dwitherell:
Hmm...

Yeah, Lazarus has my vote
[Verizon Droid Charge] tmanschuette:
+1 on Lazarus. Loving quick charge support. 65% charge in an hour? That's crazy!

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] dSlice:
Laz...
[Verizon Droid Charge] lazarus0000:
My vote is for "Lazarus Kernel"

I'm just saying.... :D
[Verizon Droid Charge] mad3963:
+1
[Verizon Droid Charge] ultimatdan:
Didnt try any of the older PBJ kernels besides 1213, 1214, and 1219. Which ones are those? Am I able to flash via odin with the zip file in the PDA box... or is there a fancy way of flashing a kernel file thats different than flashing a rom in odin? Thanks.

---------- Post added at 09:30 PM ---------- Previous post was at 09:21 PM ----------

Thanks for the response. I havent used ADB before though, is that an app from the store or something I run on my pc when the phone is connected?
[Verizon Droid Charge] xdadevnube:
I use it to mount Windows shares over Wifi to the SDcard. This way files from the computer show up as though they were stored on the phone. I can mount terabytes of stuff to the phone so music players and video players can see it.

I use a netbook with virtual infrastructure mode enabled to wirelessly share the netbook files when traveling.

Let me if you need more info.
[Verizon Droid Charge] kynalvarus:
I'm not set up to build ODIN packages right now. I'm only distributing via CWM installer packages, meant to be loaded in CWM Recovery 5.

You can get instructions on how to put ADB on your PC here. It runs on your PC and connects to the phone via USB Debugging (which has to be turned on in settings.)
[Verizon Droid Charge] cujo6801:
I'm just glad you didn't say you where going to sue him if he uses it...lol

SENT FROM THE DOG POUND
[Verizon Droid Charge] ultimatdan:
Awesome thanks, i'll try that out and get back to you! Just wondering...is there a way for me to revert back from Imoseyon's latest kernel (imoseyon_kernel_charge_gb_4.0.0.zip) that im using now to the stock FP5 kernel that came with Tweaked 3.1 without having to wipe/reflash everything and start from scratch again? I tried just flashing the stock FP5 kernel over it but it kept boot looping so i ended up flashing imoseyon's again.
[Verizon Droid Charge] cujo6801:
Yep...flash imnuts kernel reboot..then flash the stock kernel...

You might lost root..

If you do just flash tweaked again over the top(dirty)

No need to wipe...

Your probably ext4 .

So you'll have to convert back to rfs first for stock kernel to work..

SENT FROM THE DOG POUND
[Verizon Droid Charge] stueycaster:
If I can use this to access files on my computer I'll be trying it out.

Here you go making this kernel super appealing just when I'm trying to stop being such a flash-aholic. I was going to try to stay on stock kernel. Oh well.
[Verizon Droid Charge] Antoneus1231:
I use the smb add-on module for astro file manager to see my files on windows networks over wifi. I'll have to check how cifs compares. Anyone know? I use samba file share to see my phone files on my computer over wifi. Will cifs combine the two?

. :: TSM Tweaked 3.1 . PB&J . Vanilla Bean :: .
[Verizon Droid Charge] je2854:
I have made an ODIN package with MD5 of the latest kernel.

Just unzip it from the 7z archive and then throw it in the PDA

slot of ODIN 1.85 (or 1.83) and your good to go on FP5 PBJ 1219.

Make sure and wipe the caches before you say your having troubles.