Develop Bugs

[Q] How to upgrade ROM and keep installed apps?

Since CM and Virtuous updates itself once every 2 weeks or so, I don't want to keep on reinstalling everything over and over and over again.
Is there a way to keep all my settings on all my apps AND have my ROM upgraded from CM 6.0 to 6.1?

Yes you can keep everything if you're upgrading from CM 6 to CM 6.1. When you flash from recovery, all you'll want to do is to wipe cache... you don't need to wipe the phone unless the upgrade is causing you trouble. When switching roms entirely, you may need to wipe the phone.
But I flash the nightlies all the time, and wiping the cache is sufficient.
If you are switching roms, use titanium backup. The batch operation definitely makes restoring apps and data quicker.

Same is true for virtuous. Only need wipe for major changes. If i remember right its major.minor.bugfix i forget the last one but anyway only wipe on the major updates.
Sent from my HTC Vision using XDA App

1. How do I wipe cache only?
I rebooted into recovery and i saw several wipe options but didn't know which one i had to wipe.
2. I was actually already at 6.1 RV3. Is there any point at all in upgrading to RV4? Or can I wait until it's at like 6.2 or something.

convolution said:
1. How do I wipe cache only?
I rebooted into recovery and i saw several wipe options but didn't know which one i had to wipe.
2. I was actually already at 6.1 RV3. Is there any point at all in upgrading to RV4? Or can I wait until it's at like 6.2 or something.
Click to expand...
Click to collapse
I cant answer number 1. Id guess if there is an option for wipe cache then select that. To answer number 2. RC4 will be more stable then RC3 or more features at least. If you dont want to help test these then i would wait until the official stable release. Fyi 6.1 has been released you should install that one.
Sent from my HTC Vision using XDA App

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick

What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed

Try a full wipe, cache, dalvik, and data. Then reflash the rom.

By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?

That's correct, just wipe dalvik and cache before doing so.

So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...

I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17

You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.

The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??

deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.

Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.

deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.

No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?

Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.

Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.

deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

[Q] Quick question

Say I want to flash a new version of the rom i'm using do I need to wipe everthing again?

After multiple updates it's usually a good idea for a full wipe. However just one update you'll be fine wiping cache and dalvik only. If you've flashed a custom kernel then you'll need to reflash that, along with any other mods you've made to the system.
Read the thread for the rom and double check that it isn't recommended to do a full wipe for this particular update. Also make a nandroid backup just in case you encounter any problems.
I only flash updates of the same rom, usually only wiping dalvik and cache. I do make sure to do a full wipe about once a month though. It keeps the phone running smoothly and helps weed out apps that I don't really use when I go to restore.
Supersonic Evo 4G | MIUI | Tapatalk

It's always recomended to do a full wipe unless the op says otherwise. Some ops will make patches that do not require full wipe. If you don't full wipe, don't complain about problems. It's the first thing you will be asked. Use Titanium Backup for your apps and wipe away. Always nandroid first just in case you make a mistake.

thanks for the great answers guys appreciate it

You're welcome, just trying to be helpful.

[Q] questions before rom flashing for the first time

I have been rooted for awhile now, but I have held off from flashing a rom. I don't want to introduce any problems as things work good for the most part. I am interested in flashing though mainly for better battery life as I have read about from various roms and to remove CIQ and bloat.
I am rooted on stock rom, made a backup with CWM, and used Titianium backup for my apps. I have been reading up on flashing roms, and I am confused about the wipe. Do some roms require different wiping than others? Aren't there like three different types of wipe from CWM? Does wiping erase data on the internal SD card?
Any things I need to look out for that could cause issues? Any recommendations on which rom would be best to try out first? Thanks for any tips.

bigcletus said:
I have been rooted for awhile now, but I have held off from flashing a rom. I don't want to introduce any problems as things work good for the most part. I am interested in flashing though mainly for better battery life as I have read about from various roms and to remove CIQ and bloat.
I am rooted on stock rom, made a backup with CWM, and used Titianium backup for my apps. I have been reading up on flashing roms, and I am confused about the wipe. Do some roms require different wiping than others? Aren't there like three different types of wipe from CWM? Does wiping erase data on the internal SD card?
Any things I need to look out for that could cause issues? Any recommendations on which rom would be best to try out first? Thanks for any tips.
Click to expand...
Click to collapse
Some ROMs wipe during the install , some ROMs don't ..
At the very least you should wipe your Dalvik cache ...
You can wipe your cache if you like, if you wipe anything else, it is up to you or up to the ROM ..
Honestly , if you are installing a completely different ROM a full wipe is usually best, if upgrading the same ROM, usually a Dalvik wipe is all you need ...
Some people , me included, are on the brave side and only wipe the Dalvik and give the ROM a shot, usually though I end up doing a full wipe ..
A good tip is also to run the "Fix Permissions" under advanced in CWM after flashing a ROM/Theme/MOD ..

Just follow the instructoins the dev has given. I always wipe before installing a custom rom to avoid problems later.
Sent from my SGH-T989 using XDA App

badaphooko01 said:
Just follow the instructoins the dev has given. I always wipe before installing a custom rom to avoid problems later.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
DITTO!! ... I should have added this to my post, this should be your first choice ...

[Q] CM7 Nightly #134, can't recieve MMS.

Hello everyone. I'm running CM7 Nightly #134 with Aeroevan's .7 BFS Kernel. It appears I'm unable to recieve MMS messages. I'm using handcent, and I do have the option on to "automatically retrieve messages" under the MMS category. Is there any fix/patch that I could apply to my phone? I'd rather not reflash another ROM onto it as I like how it is right now. Thanks!

You could look into on of the cm7.2 kangs builds I'm pretty sure you can flash them over whatever cm rom you're running just wipe dalvik. You'll need to flash the kernel again and be sure to make a back up

Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?

ma70ent said:
Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?
Click to expand...
Click to collapse
Correct... You'll need to reflash kernel, agps patch and gapps. Unless you're flashing my kang in which case you won't need to flash gapps. I have them included in the ROM. I would always suggest a dalvik wipe as well as cache but a full wipe "might not" be needed.
Just do a back up before flashing in case you have any issues.
Sent from my ADR6350 using xda premium

What's the difference between dalvik cache and normal cache? Also, is the MMS issue fixed in kangs/newer source builds? I'm hoping that flashing the newer stuff will not be in vain

ma70ent said:
Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?
Click to expand...
Click to collapse
Hey did you get your mms working on your phone? I'm having the same issue with cm7 and BFS Kernel on HTC aria. Can neither send nor receive.
Thanks!

When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application. Think of dalvik cache as Windows prefetch.
As far as mms.... It's working fine on my CM7 kang and I would assume the others as well. Once thing you can try though that worked on Eris when people had mms issues for one reason or another is:
1. Install Verizon Messages from the market and use that to send and receive a couple mms messages.
2. Once you confirm mms is working again you can uninstall it and go as normal.
Another option that takes a little more work is:
1. Make a nandroid backup of current ROM.
2. Install a stock based ROM.
3. Send and receive a few mms messages to verify everything is in working
order.
4. Install APN backup/restore from the market.
5. Open APN backup/restore and backup your APN's.
6. Restore backup you previously made.
7. Install and open APN backup/restore.
8. Restore APN's with the ones you backed up from stock.

@christophlend
Nope, haven't gotten it working yet.
@CondemnedSoul
Just wondering, why would installing Verizon Messages, then uninstalling it fix the problem? Is there something that gets activated/left over during this process that may / may not allow me to send MMS messages?
Also, I would definitely flash to your kang if I knew that all of my current settings/apps wouldn't be wiped out. If I could retain all of my current apps, and some of the more important settings, then I'd probably go for it.

ma70ent said:
@christophlend
Nope, haven't gotten it working yet.
@CondemnedSoul
Just wondering, why would installing Verizon Messages, then uninstalling it fix the problem? Is there something that gets activated/left over during this process that may / may not allow me to send MMS messages?
Also, I would definitely flash to your kang if I knew that all of my current settings/apps wouldn't be wiped out. If I could retain all of my current apps, and some of the more important settings, then I'd probably go for it.
Click to expand...
Click to collapse
The only thing I can figure the Verizon app does is reset your apns automatically vs restoring them from a stock ROM. We never quite figured out why it worked but 99% of the time it was successful when a few people had mms issues with a build. As far as your apps and settings going to my build... I can't promise a flash over will work. If you're on cm7.1 is suggest a full wipe of everything going to 7.2. You can always back up user apps and data with titanium backup and restore those however system settings would need to be reset manually. Restoring system data with ti backup is not recommended.
Sent from my ADR6350 using xda premium

Alright I'm gonna try installing the Verizon app. If that fails, I'll be doing a full wipe (I'm guessing wipe cache + wipe dalvik cache then flash is what you mean, yes) and use TiBu to reinstall the apps I had.
Thanks for all the help.

ma70ent said:
Alright I'm gonna try installing the Verizon app. If that fails, I'll be doing a full wipe (I'm guessing wipe cache + wipe dalvik cache then flash is what you mean, yes) and use TiBu to reinstall the apps I had.
Thanks for all the help.
Click to expand...
Click to collapse
Full wipe meaning data/factory reset, cache wipe then advanced-wipe dalvik.. yes.

CondemnedSoul said:
Full wipe meaning data/factory reset, cache wipe then advanced-wipe dalvik.. yes.
Click to expand...
Click to collapse
I've been meaning to ask this, what does the data/factory reset function do in CWM? And well, now that I know what wiping dalvik does, what does just wiping the "cache" do? What is stored in there?

Ok so I got MMS to send and recieve using Nightly #134. First I installed Verizon Messaging, then I read something on here about using GoSMS and configuring it manually....so now it works and its awesome. Just search for a CM 7.2 kang thread and GoSMS

CondemnedSoul said:
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application. Think of dalvik cache as Windows prefetch.
As far as mms.... It's working fine on my CM7 kang and I would assume the others as well. Once thing you can try though that worked on Eris when people had mms issues for one reason or another is:
1. Install Verizon Messages from the market and use that to send and receive a couple mms messages.
2. Once you confirm mms is working again you can uninstall it and go as normal.
Another option that takes a little more work is:
1. Make a nandroid backup of current ROM.
2. Install a stock based ROM.
3. Send and receive a few mms messages to verify everything is in working
order.
4. Install APN backup/restore from the market.
5. Open APN backup/restore and backup your APN's.
6. Restore backup you previously made.
7. Install and open APN backup/restore.
8. Restore APN's with the ones you backed up from stock.
Click to expand...
Click to collapse
Dude, you're a genius!! This fixed my wife's inc running CCM7 v15. I'm out of thanks, but I'll get ya tomorrow.
NOTE: When I uninstalled the VZW app, MMS stopped working again. So I reinstalled it and turned off all its notifications.