I can't get Imoseyon's kernel to work with the 2.3.6 leak. Every time I flash it, I go to CWM, I mount system, wipe cache, wipe dalvik, and install the .zip. When I boot up, it shows 2.6.35.7-EP4 in about phone, which I think is stock. My overclock app shows 1.0GHz max and no smartass governor. How do I get it to work?
EDIT: I had no problems with the froyo leankernel, EP1W, or EP3HA kernels.
given that its only a hacked kernel and not official, that looks like what it should show.. if you're rooted it works, also you can check in root explorer by opening up the text file called 'kernel version'
also it may not be overclockable, even the EP3H one wasn't but I guess everyone figured out you could *force* overclock it with tegrak (and I wouldn't recommend doing that with any kernel)
blazing through on my 4G Droid Charge
anoninja118 said:
given that its only a hacked kernel and not official, that looks like what it should show.. if you're rooted it works, also you can check in root explorer by opening up the text file called 'kernel version'
also it may not be overclockable, even the EP3H one wasn't but I guess everyone figured out you could *force* overclock it with tegrak (and I wouldn't recommend doing that with any kernel)
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
Thanks it shows the right one. Also i can activate smartass through terminal emulator.
Sent from my SCH-I510 using XDA App
type su
then smartass enable
reboot
davwman said:
type su
then smartass enable
reboot
Click to expand...
Click to collapse
Yes i said in my last post that i did this.
Sent from my SCH-I510 using XDA App
Related
So I am trying to overclock my hero using setcpu, but there is an error message saying "could not read setcpu configs. Is your SD card unmounted from PC?" Any solutions? Also what are the clocking thresholds for our phones?
shahrukh817 said:
So I am trying to overclock my hero using setcpu, but there is an error message saying "could not read setcpu configs. Is your SD card unmounted from PC?" Any solutions? Also what are the clocking thresholds for our phones?
Click to expand...
Click to collapse
Are you using fresh toast v1.1 and did you scroll to the botton and select custom.. NOT htc hero
Jus10o said:
Are you using fresh toast v1.1 and did you scroll to the botton and select custom.. NOT htc hero
Click to expand...
Click to collapse
I'm using aloysius (I think its based off of damage). And i did click custom though
shahrukh817 said:
I'm using aloysius (I think its based off of damage). And i did click custom though
Click to expand...
Click to collapse
Then you cant use setcpu.. The only overclocking roms are fresh toast and one from darch.
only these 2 roms have the overclocking in them, not all sprint leaks have the oc.
this rom can be used with setcpu...
http://forum.xda-developers.com/showthread.php?t=665789
Jus10o said:
Then you cant use setcpu.. The only overclocking roms are fresh toast and one from darch.
only these 2 roms have the overclocking in them, not all sprint leaks have the oc.
this rom can be used with setcpu...
http://forum.xda-developers.com/showthread.php?t=665789
Click to expand...
Click to collapse
Understood, thanks!
I just installed this from the market but it's unable to get root. I uninstalled and re-installed for good measure, but still nothing. Any ideas?
HTC Hero, rooted (still shows the superuser app, i think that means I'm still rooted)
CM RC1
Decad3nce #11 kernel
tsm174 said:
I just installed this from the market but it's unable to get root. I uninstalled and re-installed for good measure, but still nothing. Any ideas?
HTC Hero, rooted (still shows the superuser app, i think that means I'm still rooted)
CM RC1
Decad3nce #11 kernel
Click to expand...
Click to collapse
You have to wait a few seconds before the superiser app pops up. I clicked too fast and it gave me problems. Slow down and see if that helps
Sent from my HERO200 using XDA App
smolck said:
You have to wait a few seconds before the superiser app pops up. I clicked too fast and it gave me problems. Slow down and see if that helps
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Thanks for your suggestion. When I click "Autodetect Speeds Recommended" , the "Requesting Root" popup opens with an OK button. Is it supposed to get root from that screen, or does it try to get root when I hit ok? If I sit on that screen for a few minutes, it doesn't do anything. If I hit ok, it immediately tells me it can't get root.
SetCPU Frequency Execution
I added a custom .txt file that's supposed to work for my CDMA HTC Hero.
After I found it in Device Selection, SetCPU allowed me to select overclocked speeds, but it doesn't show the speed as being applied. (Meaning, I have 600 MHz set as the maximum, but it never displays anything over 528 MHz in the large numbers at the top of the screen.)
Any advice?
Which kernel are you using?
Sent from my froyo using the xda app
I just flashed my first ROM, Damage Control 2.09.01 today.
The Kernel listed in my Settings is "2.6.29-bc0d2cff; [email protected] #1"
Any word on this? Am I being foolish? Do I need to just flash something different?
Why don't you try downloading one of decadance's kernels, I would go with a stable cfs version if you rely on GPS and the bfs if you don't and would prefer speed over navigation
Then try it again....
Sent from my froyo using the xda app
I have a .zip file that will remove the voltage scheduler if you have any saved on boot. A lot of users are using gingerbread ROMs that uses CWM3 including myself, but unfortunately this program only works with earlier versions of CWM. So I'm looking for a newer zip file that will remove voltage settings or if someone is savvy enough to update the script or whatever it is you have to do, it would be greatly appreciated.. the zip file I'm looking to use can be found in my sig. (schedule remover) ... thanks
cwm3 doesnt have
Advanced options > wipe voltage settings?
all the cwm 2.5 that we've been using for froyo do.
but check this out for converting cwm 2.5 zips to 3.0
CWM 2.5.x.x conversion to 3.0.0.x
I actually thought I remembered seeing that in the advanced options when you said that... but i just booted into recovery and its not there. I appreciate the reply.. i look into that link you provided.. thank you
Ummm what kernel are you using?
Talon most definitely has it.
studacris said:
Ummm what kernel are you using?
Talon most definitely has it.
Click to expand...
Click to collapse
escapists kernel. But that makes sense. That must have been where I saw it when I was using Talon. Thanks for confirming
Here is the initial release of my kernel. I'd like to have some other stuff fixed/working, but for now, this is it. I've made a lot of changes and I tried to list them all below, but I know there is stuff that I missed. Currently, the only issue that I know of is that the boot animation will be out of sync and may skip on boot. I have currently retained the stock boot animation, but custom boot animations are also possible if people would like them.
Also, while this kernel can work for recovery, I currently have not tested it, so recovery will remain what it is (ie. jt1134's CWM). I plan on testing recovery soon and releasing an updated Odin for it, as well as just having the kernel zip re-flash recovery.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0807
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB storage in recovery
0730
Custom boot animation support
Updated recovery
0710
Voodoo Sound V10
Updated CWM Recovery
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Test CWM and flash recovery partition
Smooth out boot animation
Get an overclocking kernel out
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Code:
2.6.32.9
[email protected] #1
Will this work with xxx ROM?
This will work with any currently available ROM that is posted here.
Can I overclock with this kernel?
No. Currently overclocking is not supported. I do plan on looking into implementing this in a future version though.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but do not use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not work properly on any SGS phone that I've seen.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
Code:
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info. If you need help, ask or join IRC.
If you would like something added to the FAQ, please post it in the following format:
Code:
[PLAIN][b]Put the question here[/b]
Put the answer here[/PLAIN]
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes, added installation instructions to OP
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Blanco954 said:
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
If you have lagfix enabled you just flash the voodoo kernel, or disable lagfix and flash non-voodoo kernel if you want RFS file system
Thanks Hopper. I will give this a try.
Sent from my SCH-I510 using XDA Premium App
Worked like a champ for me...thank you!
Sent from my SCH-I510 using Tapatalk
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Flash, flashed!
Thanks again, imnuts!
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
We currently have only one cwm which is jt's, so I don't quite understand what you mean.
froodyo said:
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
Click to expand...
Click to collapse
Thank you very much.
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Click to expand...
Click to collapse
Yes, lagfix is disabled the same way with any kernel that uses supercurio's Voodoo Lagfix.
froodyo said:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
Kernels are almost always independent of the ROM, so yes, you can install this regardless of what ROM you are running (Stock, debloated, something else). If/When we get a non-TouchWiz based ROM, this may change, but for now, you can use this with anything currently available.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
Click to expand...
Click to collapse
I set up novoodoo to try and avoid issues, so if you were on voodoo and didn't disable, the novoodoo should still work, but why risk it if you don't have to?
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Manjews said:
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Click to expand...
Click to collapse
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
hey i come from the fascinate and i love your work can't wait until you get voodoo sound working
i will be rooting a friends droid charge soon and then i will set him up with JT cwm voodoo and your kernel
glad to see some devs i already know working on the droid charge
khanfuze said:
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
Click to expand...
Click to collapse
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Manjews said:
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Click to expand...
Click to collapse
Good to hear Samsung released broken cpu governors again
Hi,
I am currently using the following:
OC Kernel based on Netarchy's overclock parameters
Primes! 1.8.4
Can I flash to "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 12" directly from the above?
Thanks,
1) kernel
2) yup. just make sure you get the kernel meant for prime.
3) remember to flush cache and dalvik.
Cool thanks, will try it tonight.
PS: Yeah I realized I got the spelling error after I hit submit.
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Fb's latest kernel is the most stable kernel as off now.
i would say go for fb's kernel
fb modified or i should say upgraded bhudven kernel...
and it got team acid splash screen which is a very nice touch
bark777 said:
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Click to expand...
Click to collapse
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
https://github.com/teamacid/android_kernel_galaxys4g/commits/sgs4g-aosp
FBis251 said:
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
Click to expand...
Click to collapse
Thank you JMW and FB.
Is this the normal message state?
CWM-based VooDoo LagFix Recovery v5.0.2.7
Voodoo lagfix is actually: disabled
......................next boot: enabled
Option:
/system lagfix conversion: yes
...................debug mode: no
I show this from a terminal session:
/system ext4 rw,
/cache ext4 rw
/data ext4 rw
I tried to disable VooDoo but it does not disable, do I need to start with VooDoo disabled from version 0.0.2d?
I went back to v0.0.2d and disabled VooDoo, then flashed v0.1.1 rc2. The conversion took place per the voice. But it still shows that it is disabled as above.
Bark, read the OP under Features
http://forum.xda-developers.com/showthread.php?t=1513287
The RC2 version of the kernel forces you onto ext4 (lagfix) since there's no real reason why you should stay on RFS (lagfix disabled).
Not sure why that was confusing to me, but I really appreciate your quick response. Thank you for straightening me out!
Whoops! I heard my phone rebooting as it sat on the table. I guess I'll go back to v0.0.2d.
I'm running stock GB with AS 14.1 and Tegrak UV/OC to 1.2.
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
FBis251 said:
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.[/url]
Click to expand...
Click to collapse
jigglynuts said:
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
Click to expand...
Click to collapse
Hello JN,
I'm going to chose oc/uv over the latest version of this kernel. I checked my settings and they are as suggested. I guess if the v0.0.2d kernel can tolerate my OC/UV settings and not reboot then I would deem it a tad more stable.
Since I can use the CWM5 version at will, I will use it to do backups. But I will use the v0.0.2d version daily as the OC'ing does make this device snappier. I don't understand the "ADB in recovery" part of the explanation, got to do some reading.
Do you overclock your phone, I would be interested in the setting you use.
Thanks!
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
JuLes' MostWanted said:
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Hello JMW,
That is interesting. I wonder if after some time the kernel adjusts something and then calls for a reboot.
I will go back and run the latest again and then give it some time based upon your input.
Thank you.
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
just for the record Bhudven and Fb nailed the values ;-)
JuLes' MostWanted said:
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
Click to expand...
Click to collapse
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
JuLes' MostWanted said:
just for the record Bhudven and Fb nailed the values ;-)
Click to expand...
Click to collapse
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
too bad i cannot provide logs.
as far as observe it always reboot once after i install the latest from fb....
note: before reboot, laggy
but all runs great after that reboot
i dunno why this happens but I think it a great thing
i just wanna make people aware of it.
damn this kernel diving must be mind boggling thats why I will stick to theme
bhundven said:
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
Click to expand...
Click to collapse
Thank you for your work, but can you please address why the kernels you released since you disabled Deep Idle and DMA Engines have random reboot issues. Many many people who have reverted back to the 2d kernel no longer have these issues.
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
I'm going to write a "stability" build of RC2 that just backs up your init.d on boot and wipes the directory. Bet you'll get rid of your reboots until you start messing with Tegrak and OC/UC/UV settings.
bhundven said:
No logs, nothing to fix.
Click to expand...
Click to collapse
I am so willing to submit logs, if I only knew how. I have read thousands of posts on this site and have learned a ton about my phone and how to upgrade it. But try as I may and I have tried, I cannot find a good reference document on collecting logs. I heard some people say I will run a logcat and I have downloaded log collector from the market.
I used to work in the field service arena and it was common that our customers would collect error data for us to use to find their problems, but they would always collect the wrong things until we gave them a list of what we needed and how to collect it. So I am sure that it is my noob searching that has made it difficult for me to throw a lasso around this issue, but if someone would direct me to a thread or give instructions I am sure it would help me and I think maybe some others too.
I would also like to thank the devs that replied in this thread. I'm sure there are better things to do then reply again to the reboot issues some are experiencing. I truly appreciate your time, offerings and effort.
Thx
FBis251 said:
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
Click to expand...
Click to collapse
I have no init scripts, no init.d directory, & do not oc/UV. I have the reboot issue. Bryan looked @ a logcat I took a while back but it held no clues. I'll see if I can find the time to install a kernel past 2d and troubleshoot.
Sent from my SGH-T959V using xda premium
Well if you DO wind up testing this, we needs these files:
hampsterblade said:
I'm currently looking through
/proc/last_kmsg
/data/tombstones/
/data/system/dropbox/
I just found something suspicious in system server wtf about the time the phone shut down
.
Here are the logs if anyone wants too look over.
Click to expand...
Click to collapse