yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] jco23:
awesome - will test this.

will this support EXT4? and if so, will conversion to EXT4 be the same as before (http://xdaforums.com/showthread.php?t=1763951)

how about custom boot animations - as I'm installing this now, I do notice that there is no boot animation - just a blank screen for a bit.

also, per the install instructions, I presume we need to mount system within CWM first? I did wipe cache/dalvik just to be on the safe side.

I presume that if we lose root, we'll need to flash supersu again? edit: I did NOT lose root. but I have noticed the phone to be a bit sluggish. I'll give it some time though.

thanks!
[Verizon Droid Charge] kynalvarus:
EXT4 support is enabled. I have not tested it yet, but it's the same as it was before. If you do try it, let me know how it goes!

I think I'm going to try to pull in the full voodoo lagfix conversion script. It looks like the original supercurio source link at http://github.com/voodoo-project/lagfix is dead, though. I guess I'll probably have to diff out the changes from imoseyon's lean kernel repo, which appears to be over here: https://github.com/imoseyon/leanKernel-i500-gingerbread/tree/i510

The custom boot animations from Tweaked/Tweaktools are working for me. :)
[Verizon Droid Charge] jco23:
converting to EXT4 now...

success!

however, my phone is still sluggish. i did experience the same sluggishness when attempting to install 0524 charge kernel earlier this week.

hoping this goes away over time - perhaps I need to reflash tweak?

otherwise, everything seems to work - I will check my wifi when I get home.
[Verizon Droid Charge] SO_dank:
Ohhh buddy! ! Thanks bro...

Lost root just fyi
[Verizon Droid Charge] kynalvarus:
jco, I found that the "sio" io scheduler is great and super-fast on a fresh factory-wiped phone. However, if you've got a lot of memory contention, its lack of fairness tends to make the phone feel jerky and intermittently unresponsive. If you're like me and have five email accounts and half-a-dozen other background apps running all the time, you might get better results with cfq or bfq. Tegrak Overclock will let you switch and test on the fly. Give it a shot, let me know if it helps?
[Verizon Droid Charge] stueycaster:
I'm going to let you guys be my guinea pigs. Not only is my Charge my daily driver, it's my only driver. On EP4 and FP1 my phone definitely felt faster on EXT4. But then the FP5 update blew that right away. Now with dSlice's scripts and tweaks my phone is now the fastest it's ever been.
[Verizon Droid Charge] jco23:
hmm... perhaps.

anyhow, sluggish is gone now. zippier than ever! thanks!

next test is battery performance.... will report back on Monday.
[Verizon Droid Charge] tmanschuette:
With the boot animations, does yours give you a black screen for awhile and the do the boot animation real quick? I can change the boot animation, but I only get a split second of the animation then the slight vibration and it turns on. I had the same issue running 0524. Any way to remove that delay from Samsung logo to boot animation?

I never really noticed much of a difference between ext4 and rfs. I'd be willing to try it again though.

What do you mean by full voodoo? As far as I can tell it is working fine.

Maybe full voltage support? Add far as I can tell, the Charge only gets certain options in the Voltage Control app from the market. (See their pictures vs the actual app) Looks like it offers more customization that our kernel doesn't yet support.

Also it looks like a while back the Charge had the Fast Charge function? That would be nice :).

Also I heard of a thing called looping support. Have you heard of it? It allows you to run a different OS like Ubuntu or Back Track 5 on your phone! I know with our limited ram and only one processor, this could be slow, our not even worth it, but it might be something fun to play with.

Three are all just ideas, and I have no idea how to get them working. I just figured I would give you some options. I'm always willing to be the test dummy!

Thanks for your work and time.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
In order to have "full voltage support" you need an app that can tweak those parameters on the fly. The kernel has default voltage settings compiled in for each defined CPU level, and lots of extra levels defined over the stock. Without some interface for voltage adjustment, though, you're not going to have much control.

Regarding "Fast Charge" and looping support, I'm willing to look. Do you have links to more detail on these features?
[Verizon Droid Charge] shrike1978:
There's a couple of variants of fast charge. The most common (and safest) is to provide a way to allow any power source to be recognized as AC so the phone can pull as much power from the port as it will allow. This is usually controlled as a toggle app (such as this one) or as a CPU control app. You generally need to be able to enable/disable it because it generally (in my experience) disables USB connectivity when it's enable.

Loop device support allows for pseudo-devices (or virtual devices) to be created that can be mounted as a block device. Different OS's like Ubuntu require that it be supported because they use a .img file instead of a physical partition as disk, so they need a loop device to mount the image in.
[Verizon Droid Charge] thechaoz:
HDid

Did you reflash /factory wipe or did the phone just start running better? When I first installed tweaked 3.1 and slice tweaks it took a few days but phone is nice now... Never done this kernel thing before... Also to OP I believe I flashed CWM from odin using download method... If I'm mistaken will it just not flash correctly or could it cause trouble?
[Verizon Droid Charge] jco23:
nope. just ironed itself out. although, I do not recall the other kernels taking that long to smooth out while on FP1.

I have not done a factory reset in quite some time - but I am a frequent wiper of cache/dalvik when flashing stuff.

the process of flashing kernels via CWM is no really different than flashing a theme, mod, or ROM
[Verizon Droid Charge] lukegman:
thanks jco23... i haven't done ext4 that way since a long time ago with my fascinate... i still love the robot voice...mine Is zippy too...

i know the ext4 filing system is an upgraded filing system for Linux...so it has to be better right?

and first time ext4 converters... the Samsung logo will be there for a good fifteen minutes...and it will be a good wait b4 you hear the robot lady...
[Verizon Droid Charge] p2kmafia:
I've never had it that bad haha I was dreading a fresh install because then I'd have to convert to RFS and then back to ext4 and that woulda sucked
[Verizon Droid Charge] jco23:
Right. My phone was very sluggish at first. After an hour or so, it was fine.

Perhaps he should put that in the op.

tappin' that....
[Verizon Droid Charge] Antoneus1231:
Man. My phone was stock fp5 kernel w tweaked 3.1 and tegrak running at 1200 and nothing else (besides my apps). After I flashed 12-19 (it could have been the previous one) my phone was a hog and hung up for like 30-45 seconds all the time. Left it like that for half a day and it didn't recover. Finally I flashed stock back and it still didn't help. Probably user error. I factory reset and flashed 12-19 and things are back to the pbj I remember. Been up and running for 3 days now and still running smooth. Thanks for reviving this.

. :: TSM Tweaked 3.1 . PB&J . Vanilla Bean :: .
[Verizon Droid Charge] stueycaster:
Here's what it says:

"Linux version 2.6.35.7-FP5 (ryan@sigdrac) (gcc version 4.4.1 (Sourcery G== LITE 2010Q1-202) ) #3 PREEMPTWed Dec 19 12:19:03 EST 2012".

Don't ask me what all that means because I have no clue. I think it used to say Imnuts some where in the name. It must be Kynalvarus' kernel signature. Anyway the CPU is running at 1200 Mhz on SmartassV2. It can't do that stock.

I guess the important thing is it's running fine after a whole day. We'll see how it does in the future.
[Verizon Droid Charge] cujo6801:
Thats it...

SENT FROM THE DOG POUND
[Verizon Droid Charge] kynalvarus:
I've been running into a fair amount of sluggishness, what appears to be I/O problems with this set of kernels. So far the changes I've made have made it worse, which is why I haven't released any builds since 12/19. I'm trying to put together enough debugging tools to figure out why this is happening.
[Verizon Droid Charge] Antoneus1231:
Thanks for all your hard work! We all appreciate it. :thumbup:

. :: TSM Tweaked 3.1 . PB&J . Vanilla Bean :: .
[Verizon Droid Charge] cujo6801:
Not Me

I expect it... :p

SENT FROM THE DOG POUND
[Verizon Droid Charge] kynalvarus:
Then I wiped my dalvik cache, uninstalled a couple of bloated apps, reinstalled a bloaty game, and cleaned a whole bunch of abandoned garbage off my sdcard... and suddenly everything is running smooth. Android kernel development is turning out to be very good for my humility. I keep on getting to be wrong in public! :D
[Verizon Droid Charge] kynalvarus:
Found this as a possible source of hot boots : https://github.com/teamacid/android...mmit/d0073985308aae76deae3b94d85fd06d52118b63

Unfortunately, turning on this flag in defconfig produces a kernel that occasionally panics and reboots. It looks like the SVNET_WHITELIST feature is only partially implemented and not fully working in the kernel snapshot from Samsung FP5E.
[Verizon Droid Charge] tmanschuette:
So if you switch that to get rid of the hotboots, we get kernel panics instead?

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] kynalvarus:
Maybe, maybe not. Yesterday I cobbled together a patch to provide /sys/class/net/svnet0/whitelist, which was the sysfs file which was failing to be found by kernel/power/portlist.c. (portlist.c was the file that was #defined into place by CONFIG_SVNET_WHITELIST.) I grabbed a newer version of the Samsung svnet code from https://raw.github.com/teamacid/android_kernel_galaxys4gmtd/ics/drivers/misc/samsung_modemctl/svnet/. While it appeared to be from a 3.0 kernel, it was close enough to the 2.6.35 code that I could pull out the whitelist-related sysfs kobject and functions and paste them in such that they compile and link. I don't know if it *does* anything, but it hasn't crashed again, or hotbooted, since I loaded the patch on my phone..

I'm not sure I want to release this one yet, due to the expermental nature of the changes. If anyone really wants a peek at it, PM me and I'll send you a link.
[Verizon Droid Charge] kynalvarus:
Other changes in progress: I have zram running on the Charge kernel. It works fine for generating swap drives with a compressed memory file backing them. However, while the speed penalty is not nearly as bad as that of using a MMC-based swap partition, I think that most of you will not care for it. Perhaps if you're really multitasking hard and don't care about a little lag, you might like it? In any event, I'm kinda disappointed with the result, but I'll put it out there in the next release for you all to play with. It will ship turned off, and be easy to toggle on and off, no matter what.

I've got what I need (I think) to put supercurio's voodoo rfs->ext4 lagfix converter back into a kernel. Do people really want this?

I also figured out what imnuts did to make the Samsung boot animation vs AOSP boot animation startup script work no matter which animation provider and animation files were present. Unfortunately, I have not yet thought of any way to do it such that it won't lag at least a couple seconds on boot, without losing functionality or robustness. If we could be certain we always knew in advance which animation(s) were present, it could be faster. Having it be flexible is what slows it down, it seems. There's always tradeoffs, no?
[Verizon Droid Charge] jco23:
agreed.

I would like the converter back in the kernel (would be a huge step-saver).

regarding boot animations, I'm thinking that the majority (or at least plurality) of folks do not really care as much, as they'd rather the focus been on stability. given that boot animations are for a once every few days occurrence, this is more of a "nice-to-have-but-not-really-necessary" feature.

however, that being said - the slow boot animation is the only downer I have noticed from the 0524 and later kernels. So I'm not sure if you could build off from the 0504 kernel (let me know if you need it, and I'll post it for you).

thanks again for your support, and enjoy your holiday.
[Verizon Droid Charge] Antoneus1231:
I decongestant the ext converter. One question though. Is converting just as good as a full format and then installing?

As for the boot ani, I vote for whatever's most stable and fast.

Thanks for all the time you are investing on this and merry Christmas!

. :: TSM Tweaked 3.1 . PB&J . Vanilla Bean :: .
[Verizon Droid Charge] CalPolyRock:
Last time I tried ext4 it didn't make a noticeable difference. To me it's only worth trying if it's easy to convert back to rfs, since this is my daily phone and a complete wipe is avoided if possible.

My preferences in order:

Battery life

Stability

Speed

Phone calls: when I place a call, sometimes it takes literally 20-30 seconds before dialing

Multi tasking (including. memory mgmt). Apps like go sms close half the time I'm in them.

Not on the list: boot animation. Just far less important than everything else in my opinion.

Tweaked 3.1 w/ dSlice tweaks and 12/19 PBJ
[Verizon Droid Charge] kynalvarus:
24 hours running, 1 hotboot, no panics. Looking decent...
[Verizon Droid Charge] je2854:
1+

for me I see a really good performance boost. I guess as the saying goes YMMV.
[Verizon Droid Charge] kynalvarus:
Lazarus Recharged kernel has launched with a new thread!
[Verizon Droid Charge] kynalvarus:
I'll have to look at dSlice's work and see if any of it is appropriate for inclusion in a kernel distribution.
[Verizon Droid Charge] kynalvarus:
Re: fast charge, it looks like there's already a patch out there for Aries phones. This may work as-is, I'll give it a shot and let you know.

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

Re: loop device, I'm not as enthralled. The Charge is already old, relatively slow, memory-constrained and single-core CPU. This seems like a neat gee-whiz-wow factor sort of thing but I can't imagine doing much with it. Nevertheless, I think it's already enabled:

# ls /dev/block/loop*
/dev/block/loop0
/dev/block/loop1
/dev/block/loop2
/dev/block/loop3
/dev/block/loop4
/dev/block/loop5
/dev/block/loop6
/dev/block/loop7
/dev/block/loop8
/dev/block/loop9
/dev/block/loop10
/dev/block/loop11

If you want to try playing with it, feel free to let us know what you find. If I can help you out with a straightforward and/or trivial patch that doesn't break anything else, I'll be glad to include it.
[Verizon Droid Charge] kvswim:
I just gave you ALL of my thanks for today.
[Verizon Droid Charge] dSlice:
Yeah, I noticed that mine took a while to settle down as well.

I guess it got excited that it was let off the chain today. Lol

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks
[Verizon Droid Charge] elucid:
This is awesome. Lost root too, but no biggie, I'll just run the lost root fix.
[Verizon Droid Charge] tmanschuette:
Okay I have a few bugs to report.

1. Losing root every time I restart.

2. Hot boots (aka losing root again.)

These only started since I started running dslices tweaks and modified build.prop. Our at least that's when the hot boots started. The losing root started when I first installed it.

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] jco23:
hmmm... I never lost root nor had any hotboots - then again, I made sure to convert over to EXT4 quickly. I'm still on tweaked 3.1 with JB theme.

also, after I installed the kernel, I did fix permissions.
[Verizon Droid Charge] elucid:
What the the best method to EXT4 again? When I first did it, I used voodoo control app ;)
[Verizon Droid Charge] kynalvarus:
Figuring out the lost root thing is on top of my list to fix. After that are some feature enhancements.

I can't help with hot boots unless I have some idea what exact changes you made. AFAICT hot boots are caused by the "system" process being killed, either by a crash or OOM-kill. I was getting more hot boots with stock FP5E than I have with the 1213 kernel I published, so I can't be sure what your issue might be.
[Verizon Droid Charge] elucid:
I hope this helps: standard adb shell lost root fix did not work. I had to switch from using superSu to superuser (downloaded from the Play store). Now it is working fine!
[Verizon Droid Charge] jco23:
i think i've heard of others being successful with voodoo control app, but I did it the ol' fashion way (see my first post with the link on the 1st page of this thread).

just make sure to read through the instructions carefully. missing a step could cause a boot loop.
[Verizon Droid Charge] dSlice:
You have to remove root from the option in SuperSU that says to reinstall the app, it should be fine after that.

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks
[Verizon Droid Charge] lukegman:
never mind... lol
[Verizon Droid Charge] kynalvarus:
Looks like there was a script called install-root that's trying to re-root the phone and either failing or else conflicting with SuperSU on every reboot. I've turned it off for now, and intend to leave it off unless I can rewrite it to identify and capture the su binary that was already there, if there, and only restore that one. Building 1214 release now.
[Verizon Droid Charge] dragonstalker:
if everybody is losing root. You need to go back old school. Odin rewrites the entire framework. Whatever you did previously will be blown away unless you CWM a new rom. Get SUPERSU v.098. Odin your rom, then reroot. once you finish rooting, then flash supersu via recovery .zip. Sorry OP. This might mean you need to make an Odin Rom.

Hopefully this should give you perma root back. or atleast thats the way its set up to work. I dont have a charge to test this. But this always worked before.
[Verizon Droid Charge] tmanschuette:
Remove root? So you want me to click that Button then reinstall?

Sent from my SCH-I510 using Xparent Red Tapatalk 2
[Verizon Droid Charge] Mando83:
Has anyone tried that fast charge app? Wondering if it works with pbj kernel.
[Verizon Droid Charge] dSlice:
Just the one that says Reinstall.

Sent from my N7 powered by AOSPA and M+ Kernel.
[Verizon Droid Charge] kynalvarus:
Published 2012-12-14 revisions

1214 fixes are up in OP.
[Verizon Droid Charge] jco23:
Wifi works for me.

I just now got a hot boot. However, I do not have any supporting evidence aside from I just ended a call that I answered while in the middle of using another app - so I don't think I can finger the kernel as a suspect.

Battery life is typical thus far.

tappin' that....
[Verizon Droid Charge] elucid:
Everything is working great now: have root, WiFi, EXT4, voodoo sound, and no hotboots!

Very smooth! Thanks!!!
[Verizon Droid Charge] kynalvarus:
I have the fast charge patch in hand. Haven't had time to integrate it and do a test build yet. It's next on my list to do.
[Verizon Droid Charge] kynalvarus:
@elucid, just to confirm, that's on the 1214 build?
[Verizon Droid Charge] dSlice:
The 1214 build is much smoother than the 1213 one. Don't know if anything changed but, it feels like it is.

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks
[Verizon Droid Charge] lukegman:
the 1214 build is letting me keep root... i was trying a dirty flash of tweaked 3.1 but every time I cleaned cache in cwm I lost root with 1213...this time I kept it with 1214...also running ext4...
[Verizon Droid Charge] elucid:
It's actually the 12 13 build. Will try 12 14 soon.
[Verizon Droid Charge] je2854:
I am using tweaked 3.2b.... Wi-Fi will not fully connect. latest modem.
[Verizon Droid Charge] stueycaster:
Ok my curiosity got the best of me. I converted to EXT4 with the Imoseyon Kernel then flashed PB&J 12-14 and fixed permissions. Everything worked fine. Then I o/c'd it to 1200 Mhz with no u/ving, I don't plan to use a boot animation. Now to see if it improves.

Thanks for being my guinea pigs. Like I said, My Charge is my only phone.
[Verizon Droid Charge] kynalvarus:
I need to know which kernel build you're using. You're on the FP5E radios, can you confirm that? This kernel will probably only work with the FP5E radios, so double-checking is important.

Can you dump out a dmesg right after boot, and dmesg and logcat while you're trying to connect to WiFi?
[Verizon Droid Charge] kynalvarus:
I lightened the kernel a bit with extra symbol stripping and modularization of the logger which didn't need to be built-in. I've found that anything which reduces RAM pressure on this phone can make an outsized difference in its smoothness.
[Verizon Droid Charge] dSlice:
Data connects right away after turning Wifi off. That's a plus. In the 1213 one I had to toggle it on and off to get it to work.

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks
[Verizon Droid Charge] je2854:
This is what I'm using.
[Verizon Droid Charge] dSlice:
That's an old kernel...

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks
[Verizon Droid Charge] jco23:
Right. That's the tons it fp1 kernel. Make sure to use the file named 1214.

tappin' that....
[Verizon Droid Charge] je2854:
I understand that it's older BUT I have went from FP1 to FP5 and my Wi-Fi will not connect after.
[Verizon Droid Charge] cujo6801:
Are your radios fp5?

If yes go to wifi settings/advance and clear your proxy (if anything is in it)

If not, update your radios(modems)

SENT FROM THE DOG POUND
[Verizon Droid Charge] lukegman:
the 0501 kernel was a good one... is it easy to pack it the same way you did the 0524?...
[Verizon Droid Charge] je2854:
That is just it. I am all FP5 (right now except the kernel)...
[Verizon Droid Charge] stueycaster:
Did you check the proxy settings like Cujo suggested. It happened to a lot of us. Having FP5 across the board really runs good.
[Verizon Droid Charge] cujo6801:
The kernel has to be fp5 as well for wifi to work

SENT FROM THE DOG POUND
[Verizon Droid Charge] je2854:
No proxy is set as it was straight stock. Full wipe, install tweaked, full wipe, FP5 kernel, full wipe. It's ok. I'm not a debugger for a reason (;
[Verizon Droid Charge] SO_dank:
Thanks I was going nuts adb didn't work I was going to start fresh this morning... no need to noe :thumbup:
[Verizon Droid Charge] jco23:
i still experience occasional lag issues - and have to reboot (got a few hotboots). not sure if related to dslice's tweaks, but I was not experiencing these as often before. I'm going to give it one more day though - and then if I still have issues, then I may just re-flash tweak.

I'll see about getting an app to get a logcat so that i can provide more details.

on the surface though, do you think increasing the heap size from 48 to 64 could help?
[Verizon Droid Charge] kynalvarus:
The default heap size is set in the build.prop, not the kernel, so changing kernels shouldn't affect it. I keep mine at 48MB and I find that it works better, but some people have pushed theirs to 80 or 96. IMO it's memory leaks from bad configurations that cause these issues, so it may be time for you to do some logcat diving. If you can't find the culprit, you may need to wipe and reload.

If you do get a logcat, try to get kmsg/dmesg as well, please? Also, knowing which kernel build, which governor and I/O scheduler, and what level of OCing (if any) you are using would all be helpful.
[Verizon Droid Charge] jco23:
thanks - will do. for the record, I do not do any overclocking/undervolting/smartassing/governoring.....
[Verizon Droid Charge] dSlice:
I've been running I/O as CFQ, Governor as SmartassV2, Over clocked at 1.3 and Undervolted -50 through out.

No problems except some very minor hang-ups. I look forward to your future builds! :D

P.S. - The hang-ups I'm finding are when something is being privileged root access...

Sent from my Droid Charge running Tw3@3d 3.2b enhanced by dSlice's Scripts & Tweaks