yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] droidfrsh:
no, just the stock touchwiz launcher. odd, it works in every screen except the home screen, even settings menu. i only uninstalled the blatant bloat such as blockbuster/rhapsody etc. maybe it has to do with the voodoo lagfix
[Verizon Droid Charge] DeathWalking:
Touchwiz doesn't rotate the homescreen afaik.
[Verizon Droid Charge] suzook:
LMAO....I was just about to post this.
[Verizon Droid Charge] droidfrsh:
Doh, thanks
[Verizon Droid Charge] vc66:
Been using this kernel for a day or so...no restarts, fast phone, great battery life... Nice job, imnuts.
[Verizon Droid Charge] distortedloop:
imnuts-

I mentioned this to supercurio in the voodoo chat room on irc, but we're not sure if it's a voodoo in general issue, or just on your kernel, so bringing it up here as an fyi.

The problem is related to the sdcard. I replaced the Class 2 card in the phone with a new Class 10. I copied over my contents from the class 2 to the class 10, swapped cards rebooted. Thought everything was fine, but a lot of apps (but not all) started complaining about no sdcard.

I reformatted, rebooted, copied over, etc. same problem.

Root Explorer showed the folder /sdcard, but the only sub-folder folder on it was /Voodoo and the log entries for the reboots since swapping cards. Oddly, the MyFiles app that comes with the phone saw the /sdcard contents no issues.

I checked the /mnt folder and there was a /mnt/sdcard, so I looked in it and it had all the sdcard files on it that were supposed to be there.

I think what happened is somehow Voodoo looked for the sdcard on boot-up before it was mounted properly, and since it couldn't find it to write the Voodoo log entries, it created a /sdcard folder on the internal storage; then when the system went to mount the real sdcard, it couldn't because it was there as a folder in the "/" directory. I used Root Explorer to delete that folder, rebooted, and sdcard mounted normally.

Seems like probably a rare problem, but could be an issue for others in the future.

supercurio's thoughts:

[09:39am] supercurio: DistortedLoop, its possible the card is mounted 2 times, something like that

[09:40am] supercurio: maybe mounted in pre-init and then mounted a second time by Android
[Verizon Droid Charge] bash_array:
Shouldn't voodoo be shut off before any sdcard swapping occurs?
[Verizon Droid Charge] distortedloop:
Why? Other than the log file and the disable indicator Voodoo has nothing to do with the sdcard.

At any rate, this is a problem unique to the Charge in my experience. I've swapped cards on a voodoo-enabled i9000 without issue.
[Verizon Droid Charge] jdkzombie:
hmmm....i may be a total d bag for both asking this and inquiring if its possible. but what controls the GPU? is there a way to increase its performance?

other than that, voodoo sound control is always a plus on the addition list in my eyes. but at your discretion of course. :)
[Verizon Droid Charge] hokulus:
I seem to be getting more frequent random restarts with the 6/2 version. Sound works great though!
[Verizon Droid Charge] RaptorMD:
hokulus - are you runnning an OC/UV on this via setcpu or another utitlity? Curious.
[Verizon Droid Charge] hokulus:
Negative - no voltage modification or under/overclocking of any kind.

When I say more frequent its up to 3-4 per day from the once per day on the first Imnuts kernel.
[Verizon Droid Charge] teddykgb715:
I'm having the same problem, at least 3 today and yesterday each.
[Verizon Droid Charge] bash_array:
Guys, i had the random reboot problem constantly like you do.... its stock ed1 that is the issue.

I can confidently tell you i haven't had one reboot since going to droidxcon's altered beast rom. It is amazing. You can run peanut butter jelly kernel or any kernel with it!!! Try it. You won't regret it. See the altered beast forum if you don't believe me
[Verizon Droid Charge] imnuts:
"My phone reboots" is not a valid bug report. Please provide me with as much information as possible or else I cannot fix the problem, nor will I even look into it. If I can't easily replicate it on a daily basis, then it is something specific to you. I have not had any random reboots yet using this kernel or my ROM, so from my perspective, there is nothing wrong.
[Verizon Droid Charge] bash_array:
please back this up
[Verizon Droid Charge] ZeppelinJ0:
Do you guys enable lagfix on /system?
[Verizon Droid Charge] boostedjti:
While I agree slandering them may be bad, you're way off on assuming people don't know how to flash software.

I do get the random reboots but only after flashing this. I'm working on trying to figure out why and that will result in a logcat but until then just kind of stuck...
[Verizon Droid Charge] bash_array:
This kernel IS NOT THE PROBLEM!!!!
[Verizon Droid Charge] bash_array:
Yes. Works great
[Verizon Droid Charge] bash_array:
Try flashing altered beast and then peanut butter jelly. Im running that now. Been running peanut butter since day one with no issues. Altered beast is very fast... you won't be disappointed
[Verizon Droid Charge] will2live:
I'm having no issue with this kernel either. Why folks are having reboots make no sense to me. Sounds more of an app issue on the device then a kernel prob.

However before I flashed this kernel I had some reboot issue. Come to find it was setCPU causing them. So if any of you folks are having issue and have setCPU install remove it and see what you get. Specially if you are trying to use Profiles which is a bad plan. I did have so so luck with setCPU but you can not set anything lower the 400Mhz or it will cause reboot issue. Specifically if you set a battery < then whatever and have it clock down. Example I had one set to clock down when it hit 25% and every single time as soon as it got under 25% with the slower speed setting it would reboot. As soon as I removed it and hit 25% everythign still worked like a charm.
[Verizon Droid Charge] pestilent:
Has anyone noticed what kind of impact the undervolting has on battery life? I am currently running jt1134's Voodoo Kernel, so I'm interested to hear what people that have run both think in general, but particularly with battery life.
[Verizon Droid Charge] bash_array:
Honestly... no joke. I am seeing awesome battery savings to the tune of 2 hours I only used up 6% battery under light use. Under heavy video and sound streaming in another 2 hour period it still only used about 15%.

Battery saving tips:

1. Leave your screen brightness low while inside at work or home

2. Use wifi whenever possible

3. Turn off wifi while on 3g so the wifi radio doesn't keep searching (searches every 30 seconds for a signal)

4. Tell your apps to update every hour or 2 instead of every 15 minutes
[Verizon Droid Charge] imnuts:
For the people experiencing several issues, are you all using XDA App? I remember a few months ago that several Fascinate people were getting severe battery drain and lag, and the cause of it was XDA App not closing properly. It would sit in the background and keep running and use a significant amount of CPU time.
[Verizon Droid Charge] bash_array:
Interesting... i am using the xda app premium. I will keep an eye out.
[Verizon Droid Charge] pestilent:
Sounds promising.

I don't have to many things updating on my phone and most are set to 4 hours+. For me the big battery killer i that I'm syncing two exchange accounts (built in and touchdown).

As far as the reboot issues that people are complaining about.. does anyone know if the same people have seen issues with multiple kernels? I haven't had any issues with my current, so I'm hesitant to switch.
[Verizon Droid Charge] boostedjti:
First you attempt to insult me, then offer a "solution"? Really? I'm 100% positive my phone didn't random reboot before this kernel. I'm also 100% positive I haven't downloaded any new apps. I also don't use setCPU. Any more stabs you care to make?

And as I stated, I'm not blaming imnuts here. In typical fashion, I don't wipe data/cache. Maybe that is part of the problem. I'm not certain. I am trying to figure out the reason why though.
[Verizon Droid Charge] bash_array:
Stop posting your opinions until you come with concrete evidence that proves your claim that actually helps people solve a problem.
[Verizon Droid Charge] warriorprophet:
First is it an SDHC v2 or v3 class 10 card? I've had alot of problems with v2/class10 in galaxy phones come to me.

If it is v3: unmount it in the settings/SD & Storage menu, remove battery, reboot in to clockwork recovery, make sure it shows unmounted there as well, remove the card, boot normally, reinstall card.

That fixed mine after I did the same as you described.
[Verizon Droid Charge] boostedjti:
You don't have to curse to insult anyone. Just read your posts, again.

And frankly, I think my phrasing was fine. I stated I had the reboot issue. I stated I was working on getting a log. I'm just not going to suck up to imnuts over it. He's a great dev and I've used his fascinate kernels but never for more than a few days. I have my preferences and that's that.

That being said, I strictly use this for voodoo sound. I own the plus app but still no support outside of this. I also have a personal preference of setting my own uv/oc. But I'm definately pleased with his work. I enjoy this kernel and have been working on trying to force the random reboot to help find a solution or at the least the culprit.

I also use tapatalk, not the xda app. Will check my sdcard.
[Verizon Droid Charge] bash_array:
Please flash back to stock ed1, then flash altered beast then flash peanut butter jelly kernel. Im really curious to see if your reboots stop. I promise this setup is amazing... just try it. You won't be sorry
[Verizon Droid Charge] bash_array:
Here is my current up time on altered beast with pbj kernel.from imnuts. It was 36 hours but i booted into cwm to clear cache.
[Verizon Droid Charge] pestilent:
I'm going to be a bit of a Samsung noob here, but what are the best practice steps to installing this kernel over jt's?

My phone is stock ED2 with replacement kernel. I really just want to leave my phone as-is aside from kernel change.
[Verizon Droid Charge] distortedloop:
Both of you need to just drop it.... Please.
[Verizon Droid Charge] distortedloop:
Not sure if it's v2 or v3, not even sure how to check that.

You had the same problem I did? Exactly the same? Did you have a /sdcard folder created in the "/" folder of the internal storage space that contained nothing but the Voodoo folder and its logs?

I'll keep your suggestion in mind if it happens again, but I'm not sure it's the same issue I had.

Thanks.
[Verizon Droid Charge] hokulus:
Random Reboots and Accusations of libel?

I will endeavor to provide you with any information that I can gather. What sort of info would you like me to provide? I'd be more than happy to oblige. I'm not sure what that other guy is talking about with regard to insulting people whoever they may be, I'm looking for other people with "the reboot problem" in an effort to share info and potentially find a common solution.

My upgrade path was as follows(never having cleared cache or data):

stock

ed2 unrooted

ed1 rooted downgrade

jt's kernels(all up to and including v4)

jt's cwm

ed2 OTA

imnuts peanut v1

imnuts peanut v2

I do not currently nor have I ever had setCPU installed. I have not OC'd nor ov/uv'd the cpu either. Since Imnuts's v2 kernel I've had voodoo control installed so that I can use the voodoo sound options. I've had the lagfix enabled since I installed v1 of JT's kernel. I can get you a list of all the apps I have installed if you like, or provide you with details of what was going on at the time of each reboot. At this time its happening 3-5 times daily, during the full range of possible activities. Each time this occurs, the screen will activate itself if off and the phone with sit frozen with the screen brightness at maximum(regardless of setting) before rebooting itself. Upon rebooting it appears to bypass the initial "SAMSUNG" logo as is par for the course with a manual reboot and goes straight to the boot animation. It seems to take significantly less time to start up after one of these reboots than a standard reboot, becoming usable again after mere seconds. The reboots occur at *seemingly* random times, often while the phone is sitting idle and screen off on my desk. Sometimes it will happen during a voice call or as I navigate a menu, etc. It rarely seems to occur while I'm actually using the phone, rather just after I finish a text or other activity or while idle. Again, if there are any additional details you would care for me to provide such that it can be considered a legitimate bug report I would be happy to respond promptly.

Thanks, Imnuts, for all of your hard work as I stated in one of my previous posts. This is in no way a personal attack or an attack on your reputation as a developer, I really can't figure out why some have interpreted it as such. So, don't report problems for fear of getting flamed or ruining reps? It's nothing more than constructive feedback during the normal course of the problem solving process.
[Verizon Droid Charge] fyodor32768:
Thanks

Just wanted to say thanks-I'm getting excellent battery life with this kernel
[Verizon Droid Charge] imnuts:
hokulus: it sounds more like you are getting "hot boots" and not a reboot. If that is the case, can you get a logcat just after it happens and send it to me? That will help narrow down what is causing it. Also, have you tried a factory reset? If it is an application problem, then a factory reset should fix it. I'm unsure why it may only manifest itself with my kernel and not stock, it could be that something that is related to debugging or error detection/prevention is in the stock kernel and I disabled it to get things going a little quicker, and it was preventing the problem from showing itself.
[Verizon Droid Charge] boostedjti:
After your phone reboots perform a logcat. But you'll need it in a .txt format so from terminal (on the phone; terminal emulator) you'll do this:

Su

Logcat > /sdcard/logcat.txt

Then just upload that file.
[Verizon Droid Charge] hokulus:
Sure, I'd be happy to provide you with a logcat. Ironically, it hasn't happened in a few hours which is unusual but my usage has been rather light today. At any rate, I have performed several factory resets but not since before my first flash because the sales clerks at vzw took it upon themselves to put 250 of someone else's contacts in it. As soon as it reboots tonight I will be sending you that text file.

EDIT: I forgot to mention I am not using the XDA app, nor has it ever been installed.
[Verizon Droid Charge] hokulus:
Thanks for the info, I have some limited linux experience from years back (circa Slackware 2.1!) so I am marginally familiar with certain command line functions and operators. Not much has changed it seems, but you saved me the time of checking on that!
[Verizon Droid Charge] neemo6:
If I have jt's kernel do I remove that kernel or do I just flash through odin on top of the already installed jt kernel?
[Verizon Droid Charge] davey11:
This is a cwm installed file. zip files = cwm. And yes you install on top of jts kernel.
[Verizon Droid Charge] neemo6:
Does this kernel work with the new EE4 ota update? Or do we have to wait for this to get updated as well?
[Verizon Droid Charge] imnuts:
It should work for most usage, though DroidXCon has had issues with SD Card being set as read-only with a custom kernel on EE4. I'll update it when I get a chance after the new source is released.
[Verizon Droid Charge] DroidXcon:
ok Kejar found a fix for the readonly bit but there is still a matter of mounting as soon as we plug in

the other problem im getting is my filesystem wont convert. and i cant force it with either imnuts CWM or jts. any ideas
[Verizon Droid Charge] siphyn:
What is the fix for the sdcard? Did you delete the disable-lagfix file in the voodoo folder if there is one? I had to do that before mine would convert the FS.

Beamed from my SCH-I510

Edit: Disregard, I see Kejar came out with a fix in another post.
[Verizon Droid Charge] neemo6:
Should we expect a EE4 update to this kernel anytime soon?
[Verizon Droid Charge] hokulus:
logcats

I have 2 logcats from 2 separate reboots: one in the morning and one in the afternoon. I haven't applied the new OTA update so still running the same kernel and rom as before. I hope these help you Imnuts, if you need anything more don't hesitate to ask and I will provide you with whatever you require. Thank you again for all of your hard work, it's very much appreciated by the entire community.

XDA limits text file attachments to ~88k so I 7z'd both text files as they were somewhat large.
[Verizon Droid Charge] s44:
Just curious... have you found/disabled a tether module? Or are VZ/Samsung planning to add it in a OTA after they shut down the free hotspot promo?
[Verizon Droid Charge] imnuts:
As soon as Samsung releases the EE4 source, I'll be able to update. Until then, this kernel will still work with EE4.

I'll look at it then, thank you for the logs. Hopefully we can figure out what is causing the problem.

There is a tether module, but I don't know if it is active ATM. Given that tethering is free right now, I'll look into it more later.
[Verizon Droid Charge] RaptorMD:
How long did it take Samsung to release the ED2 source or didn't they since EE4 came so quickly? I have read in some places the mfg's claim they have X amount of days and others see it as Y amount of days due to the GPU license.

I mean Samsung sent the Cyanogenmod group a SGS2 to get rolling you would think they would get moving in general.
[Verizon Droid Charge] tarheelmike:
I am soooooooooooooooooo confused. If I install PBJ kernel on a newly activated device will this root the phone?
[Verizon Droid Charge] LANAtron:
Can I take this to mean that you flashed the non-voodoo kernel, and then tried unsuccessfully to convert to ext4? So. I should be ok running ee4 with lagfix already enabled and flashing the voodoo version of this kernel?

Thanks!

Update: I flashed the voodoo kernel while running EE4 with lagfix already enabled and am having 0 issues.
[Verizon Droid Charge] bash_array:
Any update for next release of pbj?
[Verizon Droid Charge] elucid:
This kernel is working flawlessly. No reboots and ruins smooth.
[Verizon Droid Charge] DeathWalking:
Also looking forward to this.
[Verizon Droid Charge] bash_array:
Same here
[Verizon Droid Charge] neemo6:
Anyone running this with EE4 update? Are the EE4 fixes still applied?
[Verizon Droid Charge] stang68x:
Hmm...I'm on GummyCHARGED 1.5 using this the Non-Lagfix version of this kernel. I want to use the LagFix-Enabled one now so I just flashed VoodooEnabled.zip in CWM and it didn't do it via the initial bootup. I then booted back into CWM and it isn't letting me enable it. When I try it still says Next Bootup: Disabled.

Any ideas?
[Verizon Droid Charge] asenduk:
i think imnuts is waiting for the ee4 source code
[Verizon Droid Charge] hokulus:
Imnuts: after all of the reboot issues I was having before, the phone has not rebooted once since installing EE4. I'm not sure if this is due to EE4 itself or the upgrade path I followed to achieve it. I first disabled the lagfix, flashed ED1 rooted odin, accepted the OTA to EE4 directly from ED1. Then I flashed jt's v4 kernel and enabled the lagfix again. I then flashed your CWM and finally your v602 PBJT kernel. I did all of this stuff late Friday night and I haven't had a reboot since, and the battery life seems even better. Confirmed your kernel took hold via the about dialog in settings. I also wiped my dalvik cache via CWM after all of these steps... Not sure which of these fixed it, but it sure seems to be working now even though I'm running the same stuff as before for the most part. Only difference being ED2->EE4 now and I was running JT's CWM and now I'm on yours.
[Verizon Droid Charge] chadness:
Pretty much the same here, though I loaded CWM, then the kernel.
[Verizon Droid Charge] chadness:
Go on to your SD Card and look for a Voodoo folder. If there is a lagfix-disabled file or folder in there, delete it, then reboot.
[Verizon Droid Charge] stang68x:
Ok, I found the file in the Voodoo folder and deleted it, then rebooted. Didn't boot into Clockwork, just a straight boot and it still isn't enabled, at least not according to my Quadrant score. In Terminal, I am typing Mount and I am not seeing any useful information either. I went back into the Voodoo folder and the "lagfix-disabled" file reappeared. Any ideas?
[Verizon Droid Charge] chadness:
Delete it again, and reflash CWM and the kernel.

Or, maybe delete it again, then go back in to CWM and see what it says?
[Verizon Droid Charge] distortedloop:
There's an issue with the Voodoo kernels that has bit me twice which might be affecting you.

If there's any problem at all mounting the physical sdcard, the voodoo kernels put a folder into the root directory named /sdcard that contains the /voodoo folder and nothing else. This prevents the real sdcard from mounting with the /sdcard alias. It also means that if you have this issue, any changes you make to try to enable or disable voodoo by changing files on the physical sdcard won't be caught by the kernel at boot up.

Grab root explorer or anything else that lets you browse the /sdcard folder. If the only thing in there is voodoo stuff, you've got the bug and need to delete that folder. I did it by just using root explorer to delete it and then rebooted. I think imnuts posted some instructions in the OP along those lines.
[Verizon Droid Charge] stang68x:
Thank you, that worked! When I rebooted the woman's voice came on saying all of that stuff and that lagfix was enabled. Woo!
[Verizon Droid Charge] stang68x:
So now my SD card isn't being read on the computer. How can I fix this without the help of a PC? Can I fix it right from the phone? Thanks, guys, you're help is much appreciated.
[Verizon Droid Charge] distortedloop:
Did you see this thread?

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

[Fix]EE4 sdcard write protection for root users

That might fix you up. It's doable from the phone only via clockwork recovery if you have it installed.
[Verizon Droid Charge] stang68x:
That looks like it could fix my problem but I won't know until I get home. I have to take out my SD card and put the .zip file onto the card via a card reader since my phone can't do it!

Thanks :)
[Verizon Droid Charge] rdearth53:
Hey imnuts, not toto be pushy or anything, but is an.OC kernel going to be available from you soon? Thanks!
[Verizon Droid Charge] distortedloop:
You can't just download to the phone direct?

Maybe I misunderstood your problem... the phone itself should be able to read and write to the sdcard. It's just that the PC can't mount as writable that that fix addresses.

If the phone can't see the sdcard, you've got a different problem.
[Verizon Droid Charge] stang68x:
For some reason, I wasn't able to move the .zip from my Downloads folder to the root of the card. I figured that was part of the issue. I just flashed the .zip now and all seems to be working!
[Verizon Droid Charge] distortedloop:
Glad you're working again.

For future reference, zips don't have to be in the root of the sdcard to flash them with CWR. You can navigate to any folder with the "install zip from sdcard" option.

Only update.zip from OTA needs be in root

Sent from Thunderbolt
[Verizon Droid Charge] bash_array:
Is there an update for this kernel coming soon? Do you have an ETA?
[Verizon Droid Charge] RichardZu:
I habe EE4 debloated rom. Is this kernal better than the one that comes with ED2 ROOT.
[Verizon Droid Charge] mms2020:
I had stock ED1 and updated to EE4 OTA. Never got any update notification for ED2. I followed the instructions and installed the PBJT kernel thru CWM. I used the 0602_charge_novoodoo.zip. I did not install any ROM as I just wanted a rooted stock EE4. The process went well. However, when I try to use the Titanium Back up, it gives me a message that my phone is not rooted. So I tried to install the 0602_charge_voodoo.zip but with same results. It seems that I can not get the root. Am I missing any thing? Thanks