Develop Bugs

[UTIL][DISCONT'D] CFLagFix 1.90 (ext2+ext3+resize+uninst support)

THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632

Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.

CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."

lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.

Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.

This looks so awesome! Thank you!
Any chance for open sourcing this?

installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .

Not bad though i see one problem... it's windows only ^^

select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?

just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro

veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!

RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.

veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )

Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.

well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!

Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?

I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?

Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved

I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...

Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!

Having problem ? Look here first

This was the kernel thread but it is so full of question that it was renamed to Question and answer!
before ask search in the forum.

Guide to install:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)
If you have "install module error" please install the android update on sourceforge. Read more here:
http://forum.xda-developers.com/showthread.php?t=848921

Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time Thanks for all your efforts.

I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.

Here for testing...
Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.

Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please

-Arturo- said:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Click to expand...
Click to collapse
Ok scratch that looks like the problem has been caused by having data on ext2 partition.

The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?

Hi
the problem is I do not belong here
I tried several variants android
the Caller ID does not work
basic configuration of network settings, but it is not good
if you want to set up an error message is incorrect sim, and it is no longer a network
something that is not a solution?

L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.
I'm thinking two changes for battery code:
a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.
b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.

@L1q1d
This is a nice idea to make this thread for kaiser users.
Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.
Keep going on your nice work for kaiser

l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.
Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?

Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App

n2rjt said:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.
I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.
About the 4th partition....you mean swap, right?
When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?

The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.

n2rjt said:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
Click to expand...
Click to collapse
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
Sent from my Full Android on Vogue using XDA App

lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.

Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.

Bug: white screen, Android still alive
How I got a white screen:
AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.
I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.
Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.
Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.
That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.
Edit: can recover by using Fn- keypad right soft key.

Battery issues?
If anyone has battery issues, please open a terminal, and type this:
> dmesg | grep ds2746 > /sdcard/dmesg.log
and send the dmesg.log file.
Thanks!

Some applications and files disappear from SD card after SAFELY removal in Windows 7

Good afternoon, dear xda-developers forum members.
I really hope to find some help here.
In last two months I had the following issues:
1. This one happened two times already: after using my phone as a flash in windows 7 and "safely removal" of it, all my applications which were installed on SD card were saying that "Application is no longer installed" when I tried to run it, although other documents and files were readable from ASTRO File Manager, i.e. SD card was mounted. In Settings->Applications all these applications had black icons with SD card image on it and rather with package name than regular application name(for example com.navitel instead of regular Navitel, etc.). I've restored all these applications from Titanium Backup, but I'm afraid that there is something more disappeared also which I don't know about.
2. My "Android" folder on sd card became a file with weird contents(this folder was used for NFS Shift data only). I couldn't restore it. Again: if this folder corrupted, then there is definitely something else also corrupted.
After I saw these things for the first time, I used Windows checkdisk with auto-fix errors. It found a lot of files and put it into "FOUND.000" directory. I recognized in these files few apk-files of installed applications from SD and also few images from my SD. Then I restored applications to SD card and for some time it seemed ok. But one time it happened again.
My assumption is that Android fails to re-mount SD card after I disconnect it from PC.
I don't know what to do... is it Android bug or is it Desire bug or what? I swear that I ALWAYS make "safe USB removal" in Windows before disconnect the USB-cable and I ALWAYS wait for the message "It's now safe to disconnect your device".
I'm very disappointed with all that Please, advise me something useful...
P.S.: If needed I can give you any debug information you want, I'm a programmer, so I've been around

You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after. What version of Android are you running?

GoogleJelly said:
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after.
Click to expand...
Click to collapse
I will, but strange that it happened, because I formatted the flash before using it for the first time...
I have two assumptions:
Maybe I shouldn't press power button to switch the screen off just after disconnecting USB cable from PC. I was doing that as a habit, because every time you disconnect your phone from PC, the screen turns on.
Maybe I shouldn't try to run application which is installed on SD just after disconnecting phone from PC. Maybe I should have waited for a minute. I've tried to do it once, because I wanted to see the result as soon as possible, so the phone said that "Application is no longer installed", I though that Android haven't mount SD yet and tried later. It worked. But next time when I used USB cable, all SD-card apps became uninstalled.
GoogleJelly said:
What version of Android are you running?
Click to expand...
Click to collapse
I'm sorry, forgot to mention. I'm using HTC Desire with Android 2.2(2.10.405.2).

Fast Boot option may be the culprit
In case anyone checks this old thread...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:

CWM NEOFroyo v0.1 fastest build yet (updated8/21/11))

This is a complete package just unzip folder on sd card.
Here is original thread by neopeek
people having wifi problems check the original thread they have a fix
This is the CWM 1.9 thread wich is included in folder already
Using starfox test kernel from XDA (Rhodium only)
EDIT: per starfox dont use test kernels use his new vanilla stable kernel
GAPPS already included.
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word
DOWNLOAD

Sure, I'll bite. I've got an extra micro-sd card here. What's the worst that could happen?

It's a pretty fast build, I tried it on Neopeeks site.
It is MDPI, so the look of it isn't quite as crisp... (you can see what I mean by the notification bar 3g, etc...lower resolution basically) but I was impressed by the speed. All the animations, etc are disabled by default and I believe that's Zeam that is the default launcher... it is quite snappy out of the box.

what tweaks you did?

no tweaks just put it together

This version is the fastest thing I've tried (probably due to mdpi-gapps), but I have two major issues.
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
2) Camera is tremendously unstable. Most of the times it crashes bringing down the entire OS or if I am lucky it will crash the camera app and refuse to start again until a reboot.
Of course there are random hiccups here and there (like most builds), but it is quite close replacing WM for every day usage.

XavierGr said:
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
Click to expand...
Click to collapse
This is actually not that unusual... I would get this on my epic4g... which is an android phone .

If you don't mind, please use the vanilla kernel that I posted instead of the testing kernel. While I don't mind that it is being bundled, the [Test] kernel was never meant to be used for long term, and is liable to include stuff that is unstable and/or changed on my whim. The vanilla kernel contains some of the tweaks that I consider to be stable and is based on known autobuild releases+supports all devices. Thanks.
http://forum.xda-developers.com/showthread.php?t=1221499
-- Starfox

you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?

anish88 said:
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
Click to expand...
Click to collapse
There's nothing stopping you from doing that.
Including testing stuff into a public build is never a good idea. I wouldn't appreciate anything I distribute for testing to be put into a build. It's meant for testing, so anyone that installs/uses it should know full well what they're getting into. Placing it into a build circumvents that, and everyone ends up using it unknowingly.

To everybody with wi-fi issue:
I've done a small fix
http://www.multiupload.com/7NSGZQZXPC
(wich is in the first post of this thread on neopeek.com)
This will fix if your problem isn't the kernel

wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.

nekikekec said:
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
Click to expand...
Click to collapse
What problem did you have exactly and what do you mean by updating wifi-nvram?
I also have a wifi problem specifically with this build but can't solve it.
(Wifi works only once per boot)

after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here

nekikekec said:
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
Click to expand...
Click to collapse
That didn't work for me at all.

Can't get CWM working
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh

nileshvedi said:
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
Click to expand...
Click to collapse
Did you set all your partitions as primary?

vzihome said:
Did you set all your partitions as primary?
Click to expand...
Click to collapse
Yes I did that too....
SD Card (All Partitions Primary)
Partition 1: 6.4 GB - FAT32
Partition 2: System - 300 MB - EXT2
Partition 1: Data - 300 MB - EXT2
Partition 1: Cache - 300 MB - EXT2
I put the npkboot folder with startup for RHOD100 on the SD Card (Root) and the NeoFroyo Zip also on the root.
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Run Haret from SD Card through File Explorer & press Volume Down - Result: Frozen Screen!!!
Does not enter into CWM recovery...
Are all the steps above right.
Regards,

nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
WHY?
CWM rootfs works only in npkboot.

nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
I'm a little confused with what you did.
Basically just unzip his folder you downloaded and then move the Entire npkboot folder to the root of ur sd card.
So there will be nothing on your sd card except the folder. Inside that folder will be everything just as you unzipped it. So for example haret would be at "Sdcard/npkboot/haret.exe". Then just switch/edit the startup.txt in the npkboot folder for your phone and boot into CWM.
You don't need to move anything outside of his npkboot folder that you unzipped.

[Q]Phone randomly shuts down using Virtuous Unity 2.35

For a few weeks i have been getting these total random shut downs of my DHD running the latest Virtuous Unity 2.35.
I saw that happening live 2 times on specific occasions/functionality calls:
1)After switching the DHD on and inserting the PIN to unlock the sim card...few secs and BAM....everything goes down. This happens from time to time.
2)Few secs after running the camera app...some loading goes on and BAM...here we go again...cell goes off
What the hell is happening, should i worry about the phone hardware or is it some wipe/format i didn't do properly prior to flashing the rom.
The problem is i noticed it also with other custom roms...but with those it never happened while i was using it, instead it happened getting the phone out of my small shoulder bag.
I am really afraid my cell has something wrong with the hardware...i was angry as hell and i tried to do some "heavy shakin" to see if the battery was not retained to its place as it should have but nothing happened...cell always on...
What should i do?
PS: i must say i tried almost 15 roms last 2 weeks but always used the related full wipe files/used a decent format/wipe procedure.
plz help me
---------------------------------------
Some tech stuff maybe you need to know
Device: Desire HD
Rom: (current) Virtuous Unity 2.35 (those days i flashed more than 10 roms, MIUI included)
Status: S-OFF HBOOT-0.85.2007 (CID-11111111)
Radio: 26.09.04.11_M2
RIL: 2.2.0131HM
Kernel: Stock that comes with VU
So that you know that's what i always did prior to flashing any ROM (currently using 4EXTRecovery 2.1.3 RC2) :
1)format system
2)format cache
3)format data
4)wipe data/factory reset
5)FLASH ROM
--------------------------------------
EDIT1: I noticed, just to keep you posted, that on the recovery menu the SD appear to be "not well partitioned", i don't know if it may be the cause.

Do you have app2ext working?
I'm guessing here. Try backing up your SDcard on a pc (preferably via cardreader) and giving it a thorough format with one partition only. You may need to delete the partitions first. I can't tell you how unless I know your operating system. If you continue having the shutdown issue afterwards you would be able to cross out SDcard problems at least.

Hi ROBINGAZI, thanks for your fast reply.
ehm, what is exactly app2ext?
I don't have a card reader right now, does it really change if I mount the SD via the phone? Anyways, i got a machine running WIN 7 x64.
hope this step will clear out the problem

Plug your phone to the computer as disk drive.
copy everything you have on the sdcard to a directory in your computer.
then click start>control panel>administrative tools> computer management.
a window will appear and you should see "storage"
in storage you will find "disk management".
you should be able to see your phone's SDcard there. right click and then delete the partition into unallocated space. Then right click and create a partition (fat32). format the partition.
if needed remount the sdcard to your computer (not the phone)
copy only one zip file (the rom you want to flash) to the SDcard (preferably something reliable like stock or something very close to stock).
unplug the phone and reboot into recovery. Do a full wipe...format everything apart from the sdcard if you think it is proper.
flash the rom and see what happens.
this way you can at least rule out the SDcard for causing your problems.
PS: Dont restore via nandroid...you could be putting the problem back into your phone.
BTW: Does your phone shut down properly or the screen goes blank like it would if you unplug a computer. Anyway make sure you dont just have a loose battery cover or battery before you try this out.

Thanks again.
Yeah my phone screen just goes blank like it would if you remove the battery from it while on.
I restored the SD card and it works properly. installed Revolution HD 5.2.6
As i stated earlier i also tried to shake the phone to see if the battery had some kind of faulty retention system but the phone stays on.
So i really can't understand what is the problem.
PS: I was curious, is there an application that tells you the entire life of a battery? meaning since when it started to operate?

NEW UPDATE ABOUT THE MATTER:
It's DEFINITELY the battery...i don't know why, i don't know with what criteria but it's the battery.
Yesterday i switched it with my brother's phone, obviously another DHD. Since then i have had absolutely no problem of any sort. He, instead, is experiencing random shut downs...
i think that the "problem is sloved" so to speak
the question about the battery app remains...or maybe there is a way to see the battery entire life cycle with a system file.