yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] cujo6801:
Checked my wifi it's okay

SENT FROM THE DOG POUND
[Verizon Droid Charge] landshark68:
Not sure if this will be the same issue we had with the Fascinate, but for a while with the Fascinate we had to go into CWM, mounts and storage, and mount datadata and data in order for fix permissions to work. If you didn't do that the fix permissions would take the amount of time you are describing. One you mounted datadata and data and ran the fix permissions script it would be at least a few minutes before the Done..... pops up. Unfortunately I just tried running the fix permissions, got the same quick result as you, then mounted datadata and data, ran it again, and got the done message in the same amount of time. I remember running the fix permissions script on the Fascinate in both CWM and terminal emulator, and when they worked, the process took a few minutes. I don't know enough to know whether this is working on the Charge just wanted to pass along this info on my previous experience on the Fassy and the results I just got.
[Verizon Droid Charge] landshark68:
Disable-logcat worked exactly as it should when I ran it in terminal emulator. Got the "Logcat will be disabled after reboot" message, rebooted no problem. Also, my wifi is just fine after running this script and rebooting. Connected to my home wifi network with no problems. Just FYI imnuts, after flashing the 08/07 kernel, my back button did not work in CWM. I scrolled through the menu three times and got the back button disabled message, made a selection, tried the back button, no workie. Scrolled through the menu three times again, got the back button enabled message, made a selection, tried back button, no dice. Flashed the 07/31 kernel, and now back button works in CWM.
[Verizon Droid Charge] 24BlackMamba:
what does disabling logcat do?
[Verizon Droid Charge] imnuts:
Just rebooted to recovery, and both the back button, and the Go Back menu option were both working for me.

It may free up some system resources. If you don't know what it does or what you're doing, my advice is to just leave it as is until you do know. Search around for what logcat does and can do as far as debugging, and also learn how and when to use it before disabling it.
[Verizon Droid Charge] landshark68:
I'll try flashing the kernel again
[Verizon Droid Charge] hazard209:
Just flashed the new update. Thanks for all the hard work Imnuts!
[Verizon Droid Charge] Piercing Heavens:
Every thing is working for me. No issues. Thank you for the updated kernel.
[Verizon Droid Charge] fz798:
Yea, the 0807 update killed my WiFi too. I flashed back to 0710 and it's fixed.
[Verizon Droid Charge] rj57:
Wifi is working fine for me with the new kernel. I am running the stock EE4 ROM.

Sent from my SCH-I510
[Verizon Droid Charge] laughingmom:
No wifi issues for me with 0807 and Humblecomb 1.51.
[Verizon Droid Charge] fz798:
Based on a suggestion in the Humble thread, I wiped cache and Dalvik (but not data), then flashed 0807 again, and sure enough, WiFi works now.
[Verizon Droid Charge] rj57:
I've been playing with this for a day and the swap partition definitely seems to help when I am using a few apps at the same time. No more slow refreshes of GO launcher when I go back to a home screen.:) Thanks imnuts for all of your work on this kernel.

I have had a couple of times that the phone rebooted and lost root when I was uninstalling some apps. In both cases, I had to boot into recovery and clear cache to get root back. I am still not sure if it is the kernel (0807 voodoo) or if something else is going on as I don't see anyting that jumps out at me in the logs. I am on stock EE4 and have lagfix enabled.
[Verizon Droid Charge] putney1477:
Currently running humblecomb. I'd like to flash this kernel and nitros eclipse....

do I flash the kernel or rom first?
[Verizon Droid Charge] anoninja118:
doesn't matter, however if you want the most recent CWM to do all your wiping/flashing I would suggest kernel first
[Verizon Droid Charge] neyenlives:
Same, no wifi problems here.

I read through 10 or more pages of this thread, the OP says this kernel is undervolted but doesn't say by how much? Anyone know?
[Verizon Droid Charge] anoninja118:
if its like his Fassy ones its -50 across the board

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] thelandon:
Like some others have posted, redownloading, and reflashing the 8-7-11 kernel fixed my wifi issue, but may have caused some others?

Today, my phone, out of nowhere, went crazy. Out of nowhere, I started getting a bunch of force closes and weird ring that would not stop (not related to my phone ring tone). I was able to boot into recovery, wiped cache and dalvick, then reinstalled the kernel and reboot. Force close(s) and the persistent ring came back. Dangit!

Long story short, I had to do a full wipe, and reinstall both Eclipse 1.3.1 and the 8-7-11 kernel. I wish I had a logcat, but the phone was soooo uncooperative, that I couldn't access the app.
[Verizon Droid Charge] neyenlives:
right on, thats what i run when i use voltage control on a configurable kernel anyways, sweet :D
[Verizon Droid Charge] neyenlives:
What are the exact steps to use, in the terminal emulator app on the device, in order to capture the logcat dump? The instructions in the op are a bit vague and seem to require a computer. It would seem beneficial to all parties involved to have a way to easily get the dump on the device without a computer.

For instance, since installing this kernel I do have one issue. When watching a movie on Netflix after several minutes it locks up and reboots on its own. What steps, what commands, and in what order do I need to perform in order to give the dev what they need to see why it is happening without a computer handy using just terminal and root explorer?

Thanks.
[Verizon Droid Charge] anoninja118:
blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] aznxk3vi17:
Ever since installing 807, I've been getting tons of random reboots and launcher home screen redraws. I'm not sure what I'm doing to cause this, but should I try clearing something? Cache or data? It's re-drawing almost after every time I exit a program that takes even a little RAM.

Sent from my SCH-I510
[Verizon Droid Charge] ldeveraux:
old versions?

Every so often my data will drop out for a minute or so. Really annoying when in the middle of doing something. Where can I find old versions of the kernel? I want to go back to the 0710 version, as I've read here that seems to be the most stable.
[Verizon Droid Charge] neyenlives:
That happens on all of these Charges no matter what firmware they have, even stock I was seeing that behaviour.
[Verizon Droid Charge] ldeveraux:
Strange. I never saw a drop until i did the upgrade. Either way, id still wonder if there was a stockpile of the older kernels somewhere.
[Verizon Droid Charge] neyenlives:
bumpitty bump
[Verizon Droid Charge] anoninja118:
hmm I don't exactly know, I'd like to know this as well.. I know doing this will dump a logcat text file to your sd card, but I don't know when the logcat starts or ends:

su

logcat > /sdcard/logfile.txt

I also know doing the command below will give you a running logcat you can read but its kinda useless to track app issues or force closes since obviously the terminal emulator is running (useful maybe for looking at rogue apps or running processes):

su

logcat

edit: IMO its just easier to use ADB

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] jkalbere:
No root after flashing novodoo 807

moved my post to general since it was a question, not sure if it is a problem with the kernel
[Verizon Droid Charge] neyenlives:
i am not usually in a situation when i can use ADB......this can be done on the phone, just need to be patient, someone who knows will tell us
[Verizon Droid Charge] hoppermi:
download alogcat from the market. It can get logcat from anything not related to boot, it's free and easy to use
[Verizon Droid Charge] neyenlives:
of course i didnt check the market for an app to do that...lol, thanks, works well
[Verizon Droid Charge] rj57:
I would start with clearing cache. Clearing data will do a factory reset.

Sent from my SCH-I510
[Verizon Droid Charge] aznxk3vi17:
I tried this and the problems persisted. I re-flashed 731 and will see if that fixes the problems. If not, I'm not sure what to do... Maybe I'll start fresh from stock and work my way back to gummy 1.91.

Sent from my SCH-I510
[Verizon Droid Charge] tommytorpedo:
Hello, love your work. I am having an issue. I was using UOT Kitchen (http://uot.dakra.lt) because I am trying change the boot animation and it doesn't work. The Battery mods works fine but the boot animation will not take. Any suggestions? Please help.
[Verizon Droid Charge] putney1477:
Quick question about the restore back to stock. Its zipped, when I need it, and eventually I will, do I "extract here" first. or do I just flash in odin as a zip?
[Verizon Droid Charge] kvswim:
Odins aren't zips, so obviously you have to extract first...plus you can't even put a zip in the PDA section.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] putney1477:
Ok thanks. Just wanted to ask before I did anything drastic lol.
[Verizon Droid Charge] xdadevnube:
Quick question. Does the ROM (Gummy1.91 for me) require a reflash with CWR in order to take advantage of the /preinstall space? Is there a way to verify that the space is working properly on the new kernel?

Thanks for all your hard work, love the banana reference!
[Verizon Droid Charge] putney1477:
Mine stopped working too, but I did a battery pull and all is well with wifi and 8/7
[Verizon Droid Charge] emtee_skull:
Here's how I changed mine.

Use a root file explorer. I use ES File Explorer free from market. My instructions will be based on ES.

Load the bootanimation.zip file of your choice onto the sd card.

Open ES and touch the sd card icon on the top left row to switch to internal ram.

navigate to system/media.

In this folder there is 2 files:

bootsamsung.qmg

bootsamsungloop.qmg

Long press both of these files and rename then to:

bootsamsung.qmg.bak

bootsamsungloop.qmg.bak

Then navigate back to the SD card by the top left home icon.

Scroll to your bootanimation file. Longpress and copy. A pullup menu will appear at bottom of screen.

Touch the sdcard icon again to get to internal ram.

Navigate back to system/media.

Press the pullup menu then select the copied filed. It will now be copied to that folder. Reboot to test if it worked.

Good luck.

(thanks to ijustdontcare)

(thanks to imnuts and others I can't remember reading to learn how to do this)
[Verizon Droid Charge] anoninja118:
I believe you need to find the "PowerOn.wav" file as well and rename or remove it so you don't hear "DROOOOOID" when you boot up... I don't remdmber where it is though, /data/etc maybe?
[Verizon Droid Charge] tommytorpedo:
Yes that happens to mine all the time. Never happened when it was stock. Weird
[Verizon Droid Charge] khanfuze:
Actually scaling mode must have been my problem too.

I freeze and restart when I use 200 conservative with the "screen off" profile.
[Verizon Droid Charge] imnuts:
See the FAQ. Profiles in SetCPU have not worked on any SGS phone that I have seen and cause freezes/lockups/reboots
[Verizon Droid Charge] suzook:
I am amazed at how people will just flash something, but NOT read the FAQ, and comments:confused:
[Verizon Droid Charge] imnuts:
I didn't have the FAQ up at first, I added that a few hours later, so I'll let the first few pass :p
[Verizon Droid Charge] Black-Falcon:
So if I flashed ROM Manager's CWM, will I still be able to flash this kernel properly?
[Verizon Droid Charge] burningembers:
You, sir, are amazing. Thank you!
[Verizon Droid Charge] imnuts:
If you didn't flash anything in Odin, then the ROM Manager flash won't work as the "flash" that it does is download an update.zip to the root of the SDCard.
[Verizon Droid Charge] Black-Falcon:
Ah, I see what you're saying; makes sense how it works now. So should I just delete that update.zip and it'll be all good?

(foolish me went through Rom manager and told it to boot into recovery to see if it would work, seems like it's stuck at the "SAMSUNG" image. Any tips?)

Flashed the most-recent ODIN with the CWM, worked (thank god)
[Verizon Droid Charge] yyhd:
installed the zip. so far everything seems to be running smooth.
[Verizon Droid Charge] RaptorMD:
One question I have is if you flash the voodoo kernel, and decide later to restore to stock, I know we first have to disable voodoo, but then how do we restore the kernel to stock?

I know we now have a stock rooted ED1 ROM, but given my current Charge's state I am really going slow.
[Verizon Droid Charge] DroidXcon:
Thanks for this , i am having a custom boot ani made and was afraid i wasnt going to be able to run it. Glad we pushed to get you a phone :D
[Verizon Droid Charge] boostedjti:
Odds of voltage control being baked in?
[Verizon Droid Charge] imnuts:
Current kernel does stock boot animations, but this can be changed to custom then if wanted (or both maybe?)

This will come with overclocking then and I was looking into the edits that need to be made earlier today.
[Verizon Droid Charge] khanfuze:
I've had restarts not using profiles in ondemand mode. I thought it could be the sd problem but it did it again with no card. Setting back to conservative.

Anything else I should do like remove Setcpu or hard reset?
[Verizon Droid Charge] boostedjti:
Nemesis got it from the genocide kernels from the epic 4g side. Tried contacting either of them? May be easier but I'm no dev lol
[Verizon Droid Charge] imnuts:
I'll remove OnDemand from the next release then :) So far, it seems that conservative is the only real option for the cpu governor, but IMO, it works just fine.

I have a test OC kernel+source now. Nemesis made the edits to the Charge source based on his initial stuff for the Fascinate, and I now have an OC branch. It just needs to have some bugs worked out as far as stability goes, and it should be good then. No ETA as I don't know how long it will take to get stable.
[Verizon Droid Charge] PorscheGuy:
I was running the V4 debloated ROM and flashed this kernel earlier today. I use WiFi at home and after flashing the kernel even though I'm on WiFi my 3G keeps popping up in the notification bar for 5 to 10 seconds and then going away. I reflashed V4 debloated to return to the "stock" kernel and the problem went away. It didn't seem to hurt anything but just an FYI...
[Verizon Droid Charge] DroidXcon:
oh i thought you meant it already did the custom boot, but yeah if you can make one up to support custom that would be greatly appreciated
[Verizon Droid Charge] teddykgb715:
EDIT: It doesn't look like reflashing the rom over-wrote this kernel. It's supposed to isn't it?

During the past 2 days I've had 3 restarts using this kernel. All 3 were when I was actively playing a game or using another app.

I'll be reflashing the debloated rom to get that kernel back for now. But I'll be back!
[Verizon Droid Charge] asenduk:
i had 2 yesterday and already 2 today!

playing wwf and while browsing

:(
[Verizon Droid Charge] dwitherell:
I believe it's in /system/etc.
[Verizon Droid Charge] emtee_skull:
I didn't change that and it doesn't play. I assumed it was because the instructions to play that sound was in the bootsamsung.qmg file.

But if you need to disable the sound yes it's in /system/etc/PowerOn.wav
[Verizon Droid Charge] tommytorpedo:
I noticed a significant decrease in battery. And sometimes my widgets take a while to come back....once I exit an app. Im not sure if flashing the kernel caused the issues but that's the latest thing I did. Anyone else experiencing this? I'm def running smoother, about 20 more mbs of ram....i like it.
[Verizon Droid Charge] geicogecko:
I have the same question. I'm not sure if I am a total noob, or did something wrong.

I installed the non-voodoo PBJ kernel using the latest CWM, but kept the phone on stock EE4. I don't have root, though. Is there something else I have to do to achieve root? ADB commands, term commands, etc.? Following the How-to that chadness posted a few months back, I didn't think anything else had to be done. Just flash the kernel and you should have root.
[Verizon Droid Charge] anoninja118:
sometimes the kernel doesn't make the root stick, flash this superuser .zip in CWM and enjoy root :)
[Verizon Droid Charge] geicogecko:
Awesome, that worked. Thank you to all of you for supporting the noobs. :)
[Verizon Droid Charge] omghi2u:
great kernel!
[Verizon Droid Charge] vcravin:
gingerbread?

do these kernals work on gingerbread??
[Verizon Droid Charge] JOrtenzi:
Considering the thread title says FROYO, take a guess...
[Verizon Droid Charge] kyler13:
I've been on GB for a good month now with two different ROMs: one EP1W-based and the other EP3H-based. Not particularly pleased with the day-to-day peformance of these GB builds. The EP1W ROM was okay, but the modem was horrible. The EP3H ROM seems not as good, but the modem is better. I miss the couple months i was on EE4 with the PBJ kernel and I think I'm going back to it this weekend. Best one out there, IMO. Hope immnuts gives us a GB PBJ kernel whenever Verizon decides to push it out to us officially.
[Verizon Droid Charge] #warden:
I am a n00b and I successfully rooted my device about 36 hours ago, but it wasn't without complications. I would like to mention what happened to me so that it may help others.

I have an OTA updated EE4 stock (factory) rom. I used ODIN to flash the CWD and then I used CWD to install the "0807_charge_voodoo" kernel. It went amazingly smooth. The only thing that I had to do was to install the superuser app from the marketplace. Everything else worked fine for the first 12 hours. I rebooted several times, and then I got my first text message.

I heard the text message notification sound and I dragged the green text message indicator puzzle piece over to unlock the phone. It was this moment that the phone "went crazy", as mentioned by another poster a few pages back in this thread. I got error messages stacked on top of one another mentioning "Force closing" of the programs. The phone became unstable and I rebooted. The error messages came back. I didn't know what to do, but I started making a list of the error messages that I was receiving and I noticed that these programs, or almost all of them, I thought, were the ones that I had "moved to SD card" previously. So I thought that there may be a broken link regarding the programs starting between the internal and external storage. I instinctively started re-installing the programs. One by one, the error messages started disappearing. I got all the programs reinstalled and the error messages have subsided. The system was becoming "stable" again.

Then I noticed that I have a wifi issue. On about every third boot, the wifi will not come on. I reboot and it comes on. The 3G works okay and I have not tried 4G, yet. (The closest city with 4G is about 30 miles away.) I will try to clear the cache and pull the battery to see if this helps.

I have also noticed an increase in battery use (or battery drainage), I think. Before I report something that is useless or wrong, may I ask - should I wipe the battery stats or do anything to reset the battery use?

For anyone contemplating this... the ODIN flashing went fine. I did one thing that really helped me. I had previously installed Apps List Backup and it made reinstalling all the apps easier. I used ASTRO file manager to backup the apps, but their reinstalls didn't seem to work, I guess since they were backed up while they were installed to the sd card. Either way, I re-installed the paid apps from, I think it was my google account sync, and it was pretty easy.

Overall, I am pleased with the new and rooted kernel, so far that is. I will play with it, but I hope that it doesn't crash like this again. If it does, it will be my responsibility, nobody else. I have read the universal disclaimer.

In summary, let me ask two questions:

Should I wipe the battery stats or do anything to reset the battery use?

Should I have cleared the cache/davlik or anything prior to the flashing that could have prevented this problem?
[Verizon Droid Charge] dwitherell:
It wouldn't be a bad idea to wipe battery stats - although if you do you should wait until you are 100% charged (maybe even 100% when the phone is off). Then do a few cycles of complete-drain-then-full-charge and you should be good to go. It's also worth mentioning that it may take a few days for things to "settle" battery-wise - it's not uncommon (at least in my experience) for battery performance to be pretty variable for a bit after flashing.

Yes, I believe the consensus is that it's a good idea to wipe cache/dalvik before flashing a kernel. In my experience when I do so I have had little to no problems afterwards.
[Verizon Droid Charge] khalilcr:
Delete
[Verizon Droid Charge] charlie_c:
This thread is for a FROYO kernel. You're posting a link to a GB kernel. Why?
[Verizon Droid Charge] khalilcr:
It was the only pbj thread I found on development forums ... I might have overlooked something... I apologize if I did.
[Verizon Droid Charge] charlie_c:
There is no developer thread on XDA for the Gingerbread-based PBJ kernel as far as I'm aware, which was intentional on the developers part. The only thread is on Rootzwiki, which is where all developer support and updates to the kernel will be. I doubt there are many people still on Froyo, but the main issue is that what you posted a link to is incompatible with what this thread is about. If someone looking for this thread downloads the kernel you linked to, their phone will stop working.
[Verizon Droid Charge] tintn00:
Thanks khalilcr. I would not have known about the new PBJ kernel if it wasn't for your post/link.
[Verizon Droid Charge] imnuts:
Unless it is stated, a ROM does not include a kernel. ROM is just that, a ROM, and is the files contained in /system. ROM Authors usually state when the kernel is included, and ATM, the AC Odin and ED1 Odin are the only ROMs that will reflash the kernel.
[Verizon Droid Charge] teddykgb715:
Thank you for the education. :)
[Verizon Droid Charge] RichardZu:
I was getting better battery life with the deoxed rom kernal. Y am.I.getting worse with this
[Verizon Droid Charge] hokulus:
No restarts on this kernel for the last 24 hours or so, but I haven't had a chance to engage in heavy usage yet. For this reason I cannot comment on battery life either, though it looks to be roughly on par with jt's v4 kernel.
[Verizon Droid Charge] bash_array:
I am getting awesom battery life on this kernel/
[Verizon Droid Charge] hoppermi:
Here's my day.
[Verizon Droid Charge] hokulus:
After a few more days of usage I have experienced 3 reboots in 2 days under both heavy and light usage, once during a voice call. After each reboot my bluetooth earpiece wont function even though it lists as paired and connected unless I do a manual reboot. All things considered I'm probably going to leave it on, its snappy as hell and the battery life is indeed nice. Thank you!
[Verizon Droid Charge] imnuts:
Updated the kernel last night, just got around to updating the OP. Hoping to test out recovery this weekend then. Enjoy :)
[Verizon Droid Charge] dspolen:
flashed alittle while ago....thank you
[Verizon Droid Charge] Manjews:
I hope you know how much we all love you.
[Verizon Droid Charge] droidfrsh:
I'm unable to use the accelerometer at the home screen to tilt, kernel related? Auto rotation is on.
[Verizon Droid Charge] khanfuze:
I bought Voodoo control plus. I'll let you know how the bass boost sounds on my Grado RS1s. Also donated ;-)
[Verizon Droid Charge] asenduk:
mine works, make sure you have auto rotation on..

(pull down status bar)
[Verizon Droid Charge] droidfrsh:
is this your upgrade flowchart?

ed1->accept update->kernel v4 flash->voodoochargecwm-2 install-> peanut butter jelly kernel install....?

also, accelerometer works in youtube or other apps, however not at my home screen. could be some bloatware i removed...
[Verizon Droid Charge] asenduk:
are you using launcherpro?

if so, you might need to enable the auto rotation option from the launcher pro settings