Related
Hi all,
I've been trying to change the font on my Captivate with no luck tonight. I sideloaded some Vibrant FlipFont apk's from this thread
They show up fine on the font menu, I can see the font preview, but when I select the font and restart my phone as suggested, the fonts are still the default.
I'm running the stock firmware, and I'm rooted, sideload enabled, and one-click lag fixed (ext2). Any ideas on what might be holding me back?
Thanks
I had the same problem, its the lagfix(ext2) specifically that ext2 fix, Remove the lagfix and the font will change, I dont know if they've fixed that problem yet, but they are aware of it.
Thanks, Nammyczc! Removing the ext2 lagfix did fix the problem. Is there a lagfix that you've found that allows for font changes?
It seems, (from reading other ppls experience) the ext3-4 lagfixes dont have this problem. I personally haven't tried those two but from what I read ppl dont have problems changing fonts with those.
Using the Tautama ext 4 lagfix right now. Fonts work fine. Plus the ext 4 is supposed to be better somehow based on the comments in the lagfix post.
Sent from my Samsung Captivate via XDA app
can anyone please elaborate on if there truly is any difference between the 2 lagfixes
i realize they are made by two different guys, and that it also depends on the actual rom , but isnt it just converting file systems to ext4 extnj or rfs.
Does one convert better or perform better, bc of a cleanup code ? i dunno just trying to pick a kernal and right now the only thing im weighing on is voodoo or ulf..
The newest voodoo is the best. Out converts the most stuff to ext4.
Sent from my Captivate.
MikeyMike01 said:
The newest voodoo is the best. Out converts the most stuff to ext4.
Sent from my Captivate.
Click to expand...
Click to collapse
Can you be more specific? Which file systems do not get converted using ULF?
heres what i do know ulf never auto enables on first boot,
vodoo converts everything to ext 4
ulf you literally have to go into recovery and convert every file system yourself,
i was looking more along the lines of actual
performance and cleanup,
like is there any ulf residue on boots and at startup bc you have to convert post boot,
just an example, looking for real differences
If memory serves me voodoo converts system while the other does not.
Sent from my Captivate.
seanzscreams said:
heres what i do know ulf never auto enables on first boot,
Click to expand...
Click to collapse
Completely untrue.
The ROM maker can enable or disable any lag fix at first boot if he chooses too.
Sent from my Captivate.
He's just humoring you. Everytime he uses serendipity, he gets so angry that he punches his cat in the face
As long as he's not punching someones salad.
Sent from my Captivate.
I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???
Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!
I was just wanted to make sure i did this the right way to change from ext4 to rfs file formate is just disable voodo lagfix and then flash cwm and thats it.Anybody please correct me if I'm wrong .
Yep, by disabling voodoo u'll go back to rfs but imo the cwm flash after that was unnecessary.
Thanks alot i thought that was right i wanted to make sure before I flashed a new rom I need to be on rfs for the rom I'm gonna flash.
Sent from my SAMSUNG-SGH-I897 using xda premium
I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.
OwenW71 said:
I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.
Click to expand...
Click to collapse
Did you reboot?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, then checked mount in terminal. The Cognition kernel did not use Voodoo, so the 'disable-lagfix' is not going to get the job done, I think.
That is a beta kernel, from what I remember it had trouble converting back to rfs from ext4. You'll have to flash back to a "stock" firmware with either a 1 click or using a .pit along with the firmware .tar with Odin/heimdall to repartition your file system.
Yikes. Since I'm stuck on EXT4, will my TiBu data backups be any good once I'm up and running on RFS?
Doesn't matter, your backup is fine.
1. Another easy way is to download the "voodoo control app" from the market. It will let you toggle rfs / ext4 from there and reports on current file system.
If I am not mistaken, this portion of the app is free..........but it is worth buying if you do a lot of ext4 stuff.
If you are on a GB ROM from KH3 on, ext4 is kind of unecessary, since rfs makes no difference in "laggy-ness"
Cognition 5 isn't voodoo. I don't remember if you can change it on CWM. Check in CWM if there is an option to switch to rfs or disable lag fix, if not you need to use ODIN back to "stock". Doesn't matter wich leaked firmware you use.
+1
FOR COGNITION:
prbassplayer is correct
See here http://forum.xda-developers.com/showpost.php?p=16664289&postcount=2818
You have to go back to stock.
Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.
prbassplayer said:
Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.
Click to expand...
Click to collapse
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.
chappatti said:
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.
Click to expand...
Click to collapse
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...
studacris said:
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...
Click to expand...
Click to collapse
Well, I am lazy..... And first timers can be comfortable !
Also its in CWM anyways. I have paid for sound, so I have control over conversions on it. But as Studa said it isn't needed.
Can anyone help me disable voodoo lagfix? I've been searching but can't find instructions on how to.
I'm currently on Serendipity 7 and want to try the leaked Gingerbread 2.3.4. I've read to disable Voodoo lagfix first.
I've checked in recovery and there are not settings to disable.
Any help is appreciated.
Also, does Voodoo need to be disabled when switching between roms? I've gone back and forth from Serendipity 6.4 and 7 to stock with no issues. Maybe i'm reading too much but just want to be sure.
I'm not running Serendipity so it might be different but, open your app drawer look for an app with lagfix control , open hit disable lagfix , then hit reboot.
As for disabling it flashing between roms ? That will be explained on the OPs installation page whether you have to or not .
That app is Voodoo Control, where u'll find Lagfix preferences, uncheck all and reboot.
Ok thanks,
Just to be sure under lagfix preferences uncheck Ext4 coversion and ext4/system and lagfix debug mode. Mine has ext4 conversion and ext4/sys is checked.
Then just reboot and it's disabled?
You don't need the app st all, in. your sdcard there will be a folder named voodoo, in that folder make a new file (or folder doesn't matter) and name it disable-lagfix and then reboot. That is all the app does.
Yep , only those 2 are suppose to be checked if u have it enabled. U can use the method suggested by studa or the voodoo control app.
P.S. that new sig of urs is freakin' awesome studa