I recently rooted my phone with Tweaked V2.2 (which I'm currently using with Transparent ICS, which looks and works amazing, by the way. Thanks for that!). It does occasionally start to lag over time and the battery starts dropping fast (which, realistically, is probably an app I have on there, I'll need to sort out which one it is later). I'm trying to look at ways to optimize the phone and I have read a decent amount about Voodoo lagfix helping with lag and battery life.
The question I had was, does Tweaked V2.2 w/PBJ come with Lagfix installed or is it something I need to add/activate? I apologize in advance if this is kind of a stupid question or if there's a fundamental understand I'm missing. I'm by no means a master with all this stuff and I'm still in the learning stage of all that I can do with a rooted device.
Thanks in advance!
jbrookley said:
I recently rooted my phone with Tweaked V2.2 (which I'm currently using with Transparent ICS, which looks and works amazing, by the way. Thanks for that!). It does occasionally start to lag over time and the battery starts dropping fast (which, realistically, is probably an app I have on there, I'll need to sort out which one it is later). I'm trying to look at ways to optimize the phone and I have read a decent amount about Voodoo lagfix helping with lag and battery life.
The question I had was, does Tweaked V2.2 w/PBJ come with Lagfix installed or is it something I need to add/activate? I apologize in advance if this is kind of a stupid question or if there's a fundamental understand I'm missing. I'm by no means a master with all this stuff and I'm still in the learning stage of all that I can do with a rooted device.
Thanks in advance!
Click to expand...
Click to collapse
I'm actually wondering the same thing. I just flashed to imoseyon's 4.0 kernel so i could convert to ext4 but im not to sure how? Does it do it automatically or is there anything i have to do? I plan to flash back to PBJ kernel after. (I'm really just trying to get wifi to work w Tweaked v2.2) but my phone is also very laggy as well.
As long as you don't have the file /sdcard/voodoo/disable_lagfix, it will automatically convert to ext4 on first boot. To be sure, install Voodoo Sound and check the options. There should be a lagfix section in the app if you are running a compatible kernel (imoseyon is the only one for GB).
If you flashed the version of Tweaked that is labeled as having ext4 conversion included, you shouldn't need this. You can always check your status by running terminal emulator, and typing 'su', followed by 'mount'. Scroll up in the list and find /system, /data, /cache, and /dbdata. They should be ext4 if you're converted. The rest will still be rfs.
shrike1978 said:
As long as you don't have the file /sdcard/voodoo/disable_lagfix, it will automatically convert to ext4 on first boot. To be sure, install Voodoo Sound and check the options. There should be a lagfix section in the app if you are running a compatible kernel (imoseyon is the only one for GB).
If you flashed the version of Tweaked that is labeled as having ext4 conversion included, you shouldn't need this. You can always check your status by running terminal emulator, and typing 'su', followed by 'mount'. Scroll up in the list and find /system, /data, /cache, and /dbdata. They should be ext4 if you're converted. The rest will still be rfs.
Click to expand...
Click to collapse
shrike is rarely wrong, however, I'm not so sure that installing the EXT4 version of Tweaked 2.2 will convert you from RFS to EXT4 (not saying that he is wrong, just don't know that is the case). the conversion takes places at the kernel level (I think). IMO's kernel makes the conversion (to/from EXT4/RFS), and I don't think dwith included that kernel is his ROM package (I could be wrong though).
if you want to convert from RFS to EXT4, try my guide posted here: http://forum.xda-developers.com/showthread.php?t=1763951
but first, make sure which version you have based upon shrike's recommendations.
jco23 said:
shrike is rarely wrong...
Click to expand...
Click to collapse
Yeah he's correct on this. The ext4 zip of the rom, from a /system perspective, is identical to the rom-only and with-kernel zips. The ext4 version does include a kernel (the same as what is in the with-kernel version), but it also includes the tools and script needed to format the usually-formatted partitions as ext4. The only difference between the ext4 and the with-kernel zips is the fact that the ext4 version has the formatting stuffs included.
Oops I made a dumb post.
Thanks for the help. Of course, after the matter, I found a detailed guide on google.If any other noob needs help just search "tonsit ext4" and it should be one of the first results from chargeforums, a post by jco on 10th July, 2012.
Related
Anybody know what file system the (untouched) Nexus S might be rocking? RFS?
no.........
demo23019 said:
no.........
Click to expand...
Click to collapse
Is that "no" as in "nobody knows," or is it "no" as in "it is not RFS"?
no its not sporting RFS
Its completely stock 2.3 samsung has no involvement in software
Aqua1ung said:
Is that "no" as in "nobody knows," or is it "no" as in "it is not RFS"?
Click to expand...
Click to collapse
A rep from Google already said, they are using ext4.
http://forum.xda-developers.com/showpost.php?p=9627089&postcount=49
If it's not RFS then I guess the dream of Gingerbread being easily ported to other Galaxy S phones is dead. At least I think that's the case.
Dougefresh91 said:
If it's not RFS then I guess the dream of Gingerbread being easily ported to other Galaxy S phones is dead. At least I think that's the case.
Click to expand...
Click to collapse
Why? We already have Voodoo, that does the same thing in Froyo. The way the Nexus S is set up in terms of filesystem is very similar to the way a Galaxy S running Voodoo is set up. There are some differences in how the partitions are set up and yaffs being used on /cache. But the overall differences very small, and minor changes in the init scripts on the ramdisk packed in the kernel will take care of all the mounting.
I have my Vibrant converted to ext4 with the Obsidian ROM, but that only changes a partition as far as I know, not the whole phones data. Not sure about VooDoo as it would never work on my device.
Some people have been speculating that it'd be easy to get a Nexus S ROM ported over since they're both on T-Mob. I was assuming that since the file systems are different that this isn't the case. Look at how much trouble they're having getting the Cyanogen Mod working on the Vibrant.
Believe me, I'd love it if it really is a simple process for devs, but I have a feeling that that's not going to be the case. Again, I'm just speculating, I'm no dev.
I don't think it will be that difficult, because file systems can be changed - indeed, there are already lagfix kernels for the Galaxy S which eliminate the use of RFS entirely. Provided the kernel has support for ext4, the partition can just be formatted that way and mounted appropriately.
I hope you're right. If so then there's no reason at all for me to trade in my Vibrant for the NS. Lord only knows when Samsung will get it's act together concerning updates, so I think this is my only hope of ever seeing Gingerbread on this phone.
rajendra82 said:
Why? We already have Voodoo, that does the same thing in Froyo. The way the Nexus S is set up in terms of filesystem is very similar to the way a Galaxy S running Voodoo is set up. There are some differences in how the partitions are set up and yaffs being used on /cache. But the overall differences very small, and minor changes in the init scripts on the ramdisk packed in the kernel will take care of all the mounting.
Click to expand...
Click to collapse
YAFFS/YAFFS2 and JFFS etc are flash file systems. Not file systems for operating systems. You still require ext/rfs/fat32 etc for the OS to work with. They mount on a yaffs/etc partition so ext/etc do not have to worry about the intricacies of flash.
Voodoo confused a lot of things for a lot of people.
SpeeDemon said:
YAFFS/YAFFS2 and JFFS etc are flash file systems. Not file systems for operating systems. You still require ext/rfs/fat32 etc for the OS to work with. They mount on a yaffs/etc partition so ext/etc do not have to worry about the intricacies of flash.
Voodoo confused a lot of things for a lot of people.
Click to expand...
Click to collapse
Not to offend you, but you only have little knowledge, and that is a dangerous thing. There is no such distinction as file system for operating system versus flash file system. Linux kernel supports a variety of file systems. Some file systems are optimized and written specifically for flash media (e.g., YAFFS2), some are written for hard drives but could work on flash media too (e.g., fat32, ext4, jfs), some are only suitable for disk based media. The operating system partition can be mounted on any partition with a file system that the kernel recognizes. Ext2/Ext3/Ext4 have been the native file systems of Linux, but there have been a lot of machines with no use of any of them. It is up to the root user to choose what the file system of any partition is. The init script in the ramdisk packed with kernel calls the commands to mount the file systems. All Voodoo lag fix did was to convert some of the partitions mounted as RFS out of the box to ext4, and then allowed them to be mounted natively at boot time. The end result is nearly the same approach being taken by Google in the Nexus S out of the box. One of the differences in how the Nexus S or a Galaxy S running the latest Voodoo is set up is the /cache partition, which is set up as ext4 by default on Voodoo+ Galaxy S, and yaffs2 on the Nexus S. Both partitions are on flash media, but since the chip used in Galaxy S does wear leveling in the firmware, we can't use yaffs2 on /cache. Voodoo might have confused some people, but it sounds like you were confused well before that came out.
rajendra82 said:
Not to offend you, but you only have little knowledge, and that is a dangerous thing. There is no such distinction as file system for operating system versus flash file system. Linux kernel supports a variety of file systems. Some file systems are optimized and written specifically for flash media (e.g., YAFFS2), some are written for hard drives but could work on flash media too (e.g., fat32, ext4, jfs), some are only suitable for disk based media. The operating system partition can be mounted on any partition with a file system that the kernel recognizes. Ext2/Ext3/Ext4 have been the native file systems of Linux, but there have been a lot of machines with no use of any of them. It is up to the root user to choose what the file system of any partition is. The init script in the ramdisk packed with kernel calls the commands to mount the file systems. All Voodoo lag fix did was to convert some of the partitions mounted as RFS out of the box to ext4, and then allowed them to be mounted natively at boot time. The end result is nearly the same approach being taken by Google in the Nexus S out of the box. One of the differences in how the Nexus S or a Galaxy S running the latest Voodoo is set up is the /cache partition, which is set up as ext4 by default on Voodoo+ Galaxy S, and yaffs2 on the Nexus S. Both partitions are on flash media, but since the chip used in Galaxy S does wear leveling in the firmware, we can't use yaffs2 on /cache. Voodoo might have confused some people, but it sounds like you were confused well before that came out.
Click to expand...
Click to collapse
Except that ext4 support didn't exist in the .29 kernel used in Android 2.1 - you seem to think it magically just works, because it works.
SpeeDemon said:
Except that ext4 support didn't exist in the .29 kernel used in Android 2.1 - you seem to think it magically just works, because it works.
Click to expand...
Click to collapse
I know that supercurio patched in native ext4 support in Eclair, and it didn't just magically appear. The Froyo kernels do support ext4 natively though, so a simple script injection enables Voodoo. Since Gingerbread kernels from Google will also suport it (as Nexus S will actually use it), why can't another script injection work again to enable a Gingerbread kernel to work with Galaxy S.
Am I right in thinking that supercurio is a dev?
bedalus said:
Am I right in thinking that supercurio is a dev?
Click to expand...
Click to collapse
You do know this thread is more than a couple of months old, right?
Anyway, to answer your question: yes, supercurio is a dev.
Sent from my Nexus S using Tapatalk
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
flyinj54 said:
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
Click to expand...
Click to collapse
use the voodoo control app to disable lagfix on next boot, that should work but I've never used it myself
flyinj54 said:
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
Click to expand...
Click to collapse
All methods to disable lagfix create the disable-lagfix file which is checked by the init script to determine if lagfix is to be disabled.
There is the Voodoo control app that makes the creation of the file convenient and mostly noob proof.
However, the actual conversion is done exactly the same regardless of the method that the file is created.
There are a couple of issues with the actual conversion to be aware of.
The first is that the conversion of the cache partition always fails.
The second is that the data partition is formatted differently than Samsung's rfs format.(4k vs 16k clusters)
Bottom line is that you end up with a somewhat borked set of filesystems.
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger
Would the safest bet be when flashing let's say a stock ROM back on the phone to not disable the lagfix and flash the Pit file and let's say ee4 to have the file system converted back?
Sent from my SCH-I510 using Tapatalk
flyinj54 said:
Would the safest bet be when flashing let's say a stock ROM back on the phone to not disable the lagfix and flash the Pit file and let's say ee4 to have the file system converted back?
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
yeah EE4 with PIT is probably your safest bet
blazing through on my 4G Droid Charge
I see some developers recommended disabling lagfix before installing their package. This doesn't make much sense to be since disabling the lagfix borks your file system.
Try to help me in this scenario. Lets say i'm running gummycharge 2.0 with their included Imo Voodoo Kernel v2.3.2 which has converted my file system to ext4. Now I want to switch to the infinity rom. Can I just do my normal cwr of wiping data, cache, and davlik without changing the kernel from rom to rom? I guess my question is can I use one kernel to run on any rom I want to install or must the kernel be changed based on the rom? I see that the infinity rom has their own kernel but lets say I just want to run the kernel that came with gummy.
Ok so now I want to get back to stock because lets say I have a problem that needs warranty attention. Just Odin the pit and ee4 and my file system will be back to rfs without having to disable voodoo lagfix and bork my system correct?
Thanks for help trying to learn the most I can before switching back to ext4 with my prior bad experience.
flyinj54 said:
I see some developers recommended disabling lagfix before installing their package. This doesn't make much sense to be since disabling the lagfix borks your file system.
Try to help me in this scenario. Lets say i'm running gummycharge 2.0 with their included Imo Voodoo Kernel v2.3.2 which has converted my file system to ext4. Now I want to switch to the infinity rom. Can I just do my normal cwr of wiping data, cache, and davlik without changing the kernel from rom to rom? I guess my question is can I use one kernel to run on any rom I want to install or must the kernel be changed based on the rom? I see that the infinity rom has their own kernel but lets say I just want to run the kernel that came with gummy.
Ok so now I want to get back to stock because lets say I have a problem that needs warranty attention. Just Odin the pit and ee4 and my file system will be back to rfs without having to disable voodoo lagfix and bork my system correct?
Thanks for help trying to learn the most I can before switching back to ext4 with my prior bad experience.
Click to expand...
Click to collapse
yes you got it correct, for the most part roms can be flashed over one another and the kernel will simply stay the same or get updated if its newer... so yes your example of Gummy to Infinity will work, I've done it numerous times myself
second issue of using EE4 and PIT to get to stock for verizon is also correct, it is your safest and most fool proof bet even verizon won't be able to tell it was modded (some people say they can, or look at the sd card for clues but its debatable)
edit: also the kernels are build specific so only GB ones with GB roms and froyo with froyo roms etc.. don't flash a froyo rom over a GB one with a GB kernel running, I think you'd need to disable voodoo lagfix first for that
blazing through on my 4G Droid Charge
Here is the next version of my HTC Evo Shift Sense kernel. It was built from the 2.3 gingerbread source. It should be stable and smooth as that was my main goal with this. I usually dont come here to XDA as often, so you may receive better support for questions/concerns here at SDX
Kernel Features:
Undervolted
Overclocked to 1.92Ghz
Interactive governor added
Smartass governor added
Enabled powersave governor
Faster charging over USB (Still slower than AC Wall charger)
BFQ (Budget Fair Queuing) i/o scheduler
Full bash mod (Gives you working directory, command history, tab completion and a shameless plug of my kernel in the shell )
Enabled ext4 filesystem support
Included HAVS/SVS support for Vipermod or incredicontrol (thanks to cayniarb and his tiamat kernel for guidance)
Init.d scripts supported (needs testing)
Default Settings:
Max Frequency = 1.209GHz
Min Frequency = 245MHz
Governor = Interactive
I/O Scheduler = BFQ
Download a cpu control application like No-Frills/SetCPU from the market for editing these settings.
Information:
The bash mod is something that cloverdale proved was what people liked so I went ahead and edited the ramdisk and zip to set that up so thanks to him for that.
After playing with the frequency table a bit, I changed methods this time and used the CM method for overclock on this phone. Its a method I saw several developers use while on 2.2 and seemed a bit cleaner than the method that I had originally set up. Thanks to toast, for the implementation of that.
This is still something I want to improve so I really need some feedback as to what you guys want to see. I will try my best to fulfill all logical suggestions.
With the bash mod, if you flash a kernel over this, it may (depending on the script method) remove the nice pretty text for the shell. It will still be functional as that part is installed to the phone itself. I will post up a 'bash removal' zip to restore back to default eventually
Ext4 FS has been added. It requires you to convert your filesystem from ext3 to ext4. Ive made it pretty simple for you to do with a script inside of a flashable zip. If something goes wrong, please let me know.
HAVS/SVS passes the VDD (Voltage draw for each frequency) values to userspace, meaning that they can be set by the user. While nothing NEEDS to be done for it to work, users now of the option of tweaking the voltages just a bit in order to increase their battery life. This was tested with the free application 'incredicontrol' from the market. ANY and ALL bug reported due to the fact that you dropped the voltages a bit to much will be ignored. This is DUE AT OWN RISK. I can tell you that from my experience, dropping down 50mv is about as far as you can go on my kernel. Good luck.
To anyone wanting to learn how to start getting into development, Please email, PM, or find me on irc #gen-dev, #sdx-developers, #htc-evo-3d on irc.freenode.net. I will teach you whatever I can as best I can. It is the only way to progress the development community. Ive spent hours teaching several over the past week and countless hours in the past. Please do not hesitate to ask.
Kingdom ROM Users:
Thanks to nfinitefx45 for letting me know what had to be changed in the ramdisk, I now have a new zip for this ROM that includes the full bash mod.
Downloads:
all downloads can be found here
Installation:
EXT3:
1. Download and place on SD card
2. Boot into recovery and make a back up if required
3. Flash zip
4. Reboot
EXT4:
1. Download both the ext4 kernel and ext4 conversion zip and place both on SD card
2. Boot into recovery and make a nandroid backup (very important)
3. Flash EXT4_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext4 kernel.
6. Reboot
Returning to EXT3:
1. Download ext3 conversion zip and have an ext3 kernel. Ensure both are on the SD card
2. Reboot into recovery and make a nandroid backup (very important)
3. Flash EXT3_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext3 kernel
6. Reboot
FAQ:
Q: What is EXT4?
A: Ext 4 is the newest version of the extended filesystem. It is mainly used as the default linux filesystem in most distros. It has improved read and write speeds over the previous versions (ext3 and ext2) It should provide slight speed improvements over the default filesystem on the shift, ext3.
Q: Why do I have to 'convert' my filesystem and is it necessary?
A: My ext4 kernel will only mount system, data, cache, and devlog partitions as ext4. It is not 100% necessary to convert the existing filesystem to ext4 as ext4 is backwards compatible, meaning it can mount ext3 partitions as ext4. By converting it to true ext4, you will be able to take full advantage of ext4 speed.
Q: Will this affect the way I flash ROMs and modifications?
A: In theory, no. The ROM should flash like normal but if they do have a custom kernel included, it will be necessary to flash an ext4 kernel after the ROM.
Q: Is this safe?
A: While working with partitions and their filesystem is considered risky on any account, I have made the conversion zips as simple and as safe as I possibly can. If any corruption does occur, it is usually fixable but should not happen in the short life of these devices.
Q: Does this change the way the backup and restore functions work in CWM or TWRP?
A: No, it should not effect the way the recoveries backup and restore data. There have been some notification of the 'wipe' functions in 'mounts and storage' reformatting back to ext3 but, you should be able to just flash the conversion zip again to return to ext4.
Q: I want to use a different kernel that is not ext4.
A: You will need to flash the EXT3 conversion zip to return your partitions to ext3. Then flash like normal.
Q: AOSP ROMs are on ext4, why do they not require the conversion?
A: While this was an option, I felt it best to do ext4 100%. An ext3 partition can be mounted as ext4 and it will provide some speed enhancements but, it is not full ext4. AOSP roms are simply mounting the ext3 partitions as ext4 which is fine, just not my preferred method.
Q: Will this effect my sdcard in anyway
A: No it will not.
Q: What do I do if something goes horribly wrong and my phone is stuck in a bootloop and I cant pull it out?
A: This is a help forum, post your issues and I or another helpful person will help you. If you are not receiving help, PM me or email me at [email protected] and I will get back to you.
Click to expand...
Click to collapse
Changelog:
11/11: Added support for HAVS/SVS. Re-worked clock table and added 1.9ghz. Enabled init.d scripts. Finished tweaking smartass governor.
11/03: Added EXT4 version of both kernels. Added bash mod to Kingdom ROM version.
11/02: Initial Release v1.5
Source available at https://github.com/dodgejcr/speedy-2.6.35
Thanks to all the people in the huddle that tested this before release to ensure it was up to standards (especially strapped and crump). Big thanks to joeykrim for his FlashimageGUI app that made testing 20 or so kernels over the past day or two less of a headache
Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium
For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps
nfinitefx45 said:
For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps
Click to expand...
Click to collapse
Sweet thanks. I had planed on either asking you today or tearing down your ramdisk to find it. Saved me time. If I add any more tweaks to the ramdisk ill be sure to add this. Much apreciated
Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?
jesusice said:
Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?
Click to expand...
Click to collapse
Been working on one for a while now. Cant seem to make myself happy with it but I have yet to stop. With this one done and out of the way, maybe I switch over to AOSP and whip something up for that. LOL Who knows
You the man Dodge. Thanks for all the work, been running smooth so far.
Sent from my PG06100 using Tapatalk
been running for two days, smooth as buttermilk.
Thanks for the fix dodge! Runnin great nice and smooth, hope you tweak it up and add nfinite's fix in. As soon as I come up with some ideas will drop'em on ya. Enjoy the movie! Lol
Sent from my AT100 using Tapatalk
-somebody- said:
been running for two days, smooth as buttermilk.
Click to expand...
Click to collapse
+1... Never disappointed with your kernels...
Sent from my PG06100 using Tapatalk
Ext4 support for filesystem
Sent from my PH44100 using XDA App
nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
+ 1 on the ext4 support dodge!
Sent from my AT100 using Tapatalk
nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming
modmouse78 said:
Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
touche, seems to run quicker than x99 at 1.2 ondemand governor
dodgejcr said:
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming
Click to expand...
Click to collapse
Enable call recording.
jesusice said:
Enable call recording.
Click to expand...
Click to collapse
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad
You do know J this is a sese kernel! You lost or forget what thread you're in ? Lol jk
Sent from my PH44100 using Tapatalk
dodgejcr said:
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad
Click to expand...
Click to collapse
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium
sparksco said:
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
being that the shift doesnt have a front facing camera video calling is kinda pointless (just my opinion)
Check in the dhd and dz threads as there source is very similar to ours
Sent from my PH44100 using XDA App
I recently updated my Captivate to GB uckk4, and was successful in ROOTING it. But I cannot get CWM and Voodoo Lagfix installed. Does anyone have a simple link for a flash for Odin, to install both?
First, questions go in the questions section. (mods have been alerted to move it)
Second, you need to flash a new Kernel that has those two options in it (Corn, Samuri, etc). Make sure you are downloading the KK4 kernel
[KERNEL][KK4][1/23/11] Corn Kernel v7.05 from Source (OC, BLN, Voodoo Sound, ... it does not come with voodoo lag fix, they oped to use ext 4 , ext 2 and RFS formating, read the OP .
aww.W.T.F? said:
[KERNEL][KK4][1/23/11] Corn Kernel v7.05 from Source (OC, BLN, Voodoo Sound, ... it does not come with voodoo lag fix, they oped to use ext 4 , ext 2 and RFS formating, read the OP .
Click to expand...
Click to collapse
No more Voodoo by default. You can still format in ext4 (Voodoo Lagfix)
From the Voodoo Project:
By replacing the faulty RFS filesystem with the Linux-standard Ext4 filesystem, Voodoo lagfix simply restores I/O performance and global user experience of the Galaxy S to what it should have been to begin with.
And the performance level is awesome!
Click to expand...
Click to collapse
Thanks for playing today's puzzler.
Thanks Red, I learned something new today.
aww.W.T.F? said:
Thanks Red, I learned something new today.
Click to expand...
Click to collapse
I try to do the same thing. Work is slow right now so I get to read ALOT. I still have many unanswered questions though.
Very sorry about posting in the wrong section
Thanks guys, for the quick answers, and info on Corn
Thread closed
Hopefully one of the things learned today is to post questions in Q&A, where they belong.
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