I have a question about the OP
"Also - if you are flashing the CWM package that comes with my attempt at a repacked kernel, MAKE SURE voodoo lagfix is completely disabled (i.e. /data, /dbdata, /cache, and /system all need to be rfs, i.e. NOT ext4) BEFORE flashing!!!"
I am running Humble 5.0 and have the Voodoo control app installed. Were I to CWM the repacked kernel flash, can someone spell out for me exactly what I would need to do to not screw things up?
Hmm... Any other info with this? I haven't encountered this issue myself. For example, has it always done this? How did you flash it, and coming from what? Have you tried clearing data or uninstalling/reinstalling?
TweakStock v1.0 + experimental repacked EP4D kernel
Added busybox /
There's No busybox added in this one had to get if from the market
Hmm... Can others verify this as well? I haven't had issues with this, but then again I haven't gone out of my way to test it specifically either... Was there something you were trying to do that you couldn't because of no busybox?
To switch back from EXT4 you can use the Voodoo Control App from the market. Once in there click on lagfix preferences and uncheck both boxes. On your next reboot it will undo the lagfix.
or you can use a file manager and go to sd card/voodoo folder and create a file with the title:
disable_lagfix
then restart and listen for the robot voices as it disables voodoo
TweakStock v1.0 + experimental repacked EP4D kernel
Added busybox /
There's No busybox added in this one had to get if from the market
I think Busybox is there, but I had some issues with run-parts support during the brief period I was running imo for init.d, so I loaded 1.19.3 from jrummy's Busybox Installer.
Titanium Backup asked for it when I clicked it to Restore but once I got busybox from the market all was fine.
That is interesting - I followed the instructions linked in the OP (from this thread) so I just assumed it worked lol. Maybe its a version issue? Interesting... sorry about that. I'll have to test that out at some point in the near future to see what's going on I suppose.
That is interesting - I followed the instructions linked in the OP (from this thread) so I just assumed it worked lol. Maybe its a version issue? Interesting... sorry about that. I'll have to test that out at some point in the near future to see what's going on I suppose.
Do we need Busybox for anything initially (e.g. root)? If not, maybe it's just easier to instruct people to DL Jrummy's Busybox Installer from the Market to add whatever versions of Busybox they need.
No Biggie got it up and running, I did have a strange thing happen when I deleted batterystats.bin right after I deleted it I went to reboot the power stats were displaying like this
Po w er O ff
R s ta rt
Re c ove ry
and so on the letters were spaced out, once I hit reboot I got a boot-loop I did a battery pull same issue a boot-loop so I wiped cache and re-flashed
all ok now. will try that again later to see if it happens again. maybe next month or so. never had that happen before.
Looks great! If I'm going to flash Odin package with repacked kernel do I need to disable lagfix or not?
I'm coming from humble 5.0. Any gotchas?
Sent from my SCH-I510 using Tapatalk
Good call - sounds like a plan for those that encounter issues.
That is really weird - never seen anything like that before, though I haven't calibrated in quite some time. Easy way to get around the issue - flash something (and wipe data beforehand) with a near full battery. Does near the same thing in my experience.
In theory it shouldn't matter with the ODIN, so feel free to test that out if you so desire That being said the more cautious approach would likely be disabling lagfix prior to flashing in ODIN.
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
It's all good. I'm just big into the mods and stuff that sets a custom phone out from the rest.
Sent from my SCH-I510 using XDA App