Develop Bugs

Fresh Rom...somethings not right...help plz

ok new guy here..well not that new i used the how to that toast made then did the various AmonRA-sp updates all the way up to fresh 3.0
heres the problem (so far):
1.market opens then immediately closes, though this isnt a force close...?idk?
2. my contacts are there but they arent: people isnt working it force closes on me and i i cant recover any phone numbers through google or my sdcard backup.
well those are my problems, again im running the latest Fresh rom used Amon RA and did the apps2sd(the right way)
im really at a loss here fellas, i dont know what to do but im not gonna do anything until i can get some insight into this debacle.
thanks in advance

easy answer.... do it all again
or
dont use fresh
use Evio 1.1 or 1.2
i have tried most of the popular roms and this is by far the best, including the best battery life, stability, compatability, etc.
screw the havs and crap.. i tried those and got the worst battery life EVER from those. 6 hours tops... Evio i can go 2-3 times that, true... i get far farrr better battery life out of a pseudo stock rom than i do all the custom "stuff"
just flash with another rom... fresh is unique in itself and doesnt always play nice with certain other add-on's (from what i have read)
that is why in other threads you see custom builds for people using "fresh roms"
why mess with something that is so unique it requires its own builds for certain things.

so do i have to do apps2sd again

Just wipe your cache and davlick cache

have you tried wiping your cache & dalvik-cache and flashing gapps?

no not yet....gapps? where can i find that...forgive me i dont use forums ever lol

okay tried wiping both caches....same results.
how do i flash gapps? i searched the forums and all i get is the Fresh 3.xxx thread titled GApps and no source on the file itself.

OP of CM6. Just flash from recovery. You shouldn't need to wipe anything. But if you're gonna, just cache and dalvik.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
OP of CM6. Just flash from recovery. You shouldn't need to wipe anything. But if you're gonna, just cache and dalvik.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
flash teh rom? ok then will do!

No, there's a separate download for gapps. Sorry, I could've been more specific.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
No, there's a separate download for gapps. Sorry, I could've been more specific.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
okay that was what i was searching for...where is that download link located? searcdh function seems to not be helpful

It's in the CM6 OP just below the rom download link. Should say something like gapps8172010.
Sent from my FROYO'D EVO using xda app

nope didi all three and still no market and com.w/e.people still force closes.
i dont have time for this so im flashing back to 1.0.1
thanks for the effort

MIUI Force close

I'm running the latest version of Clockworkmod which looks like it is most likely my problem for constant force closes on all my apps but i'm wondering if i can downgrade clockworkmod version to fix this if rom manager and all my other apps keep force closing? Any suggestions would be VERY appreciated. Sorry if this is posted somewhere else also I tried a search but didn't see any solutions.

I think you and I might have the same problem going on. All of my apps are force closing, but I am not sure if mine has to do with clock work mod or not. I still have not found a solution to my problem.

This may seem obvious to you and I apologize if it does but, did you wipe data and cache prior to flashing MIUI? I was running it recently without any issues at all. And I keep the latest version of CWM. It's an excellent rom. Smooth as butter.
Edit: I was running MIUI 1.2.19 with invisiblek, #28, by the way.
Sent from my ADR6300 using XDA App

There is some speculation that CWM3 isn't wiping as well as CWM2 did... I can certainly confirm that it does not seem to clean everything out for a new MIUI install. On MIUI forums you can find a script to wipe everything first, or you can just open the "mounts" section and manually format /boot and /system. This seems to do the trick.

igknighted said:
There is some speculation that CWM3 isn't wiping as well as CWM2 did... I can certainly confirm that it does not seem to clean everything out for a new MIUI install. On MIUI forums you can find a script to wipe everything first, or you can just open the "mounts" section and manually format /boot and /system. This seems to do the trick.
Click to expand...
Click to collapse
I can't say I've had any issues, personally but, I've definitely seen several comments about this around the forums. I plan on flashing back to MIUI soon. Just to be safe, I'll be looking for that script before I do it. Thanks for the heads up.
Sent from my ADR6300 using XDA App

The way I solved my mass force close issue was to do a factory reset and then flash the rom I wanted. Maybe that will solve your problem also?

I ended up just uninstalling and reinstalling an app a couple times and it started working just fine, another question though. What's the best version of miui? And also what are the miui ports for? New to this Rom but its pretty seemless
Sent from my ADR6300 using XDA App

Alright so this is odd, just updated to 1.1.28.1 version and none of my apps whether from the market or SD card will work on the first install, I must uninstall then reinstall for them to work. Anyone else have this going on? I guess its not a HUGE deal but still just weird
Sent from my HTC Incredible using XDA App

It seems likely that cwr 3 is a pos that is causing all these issues. I have started manually wiping everything needed to be wiped in mounts and my problems went away. Another alternative is to go back to cwr 2.5
Sent from my desire z inc port.

slong427 said:
I ended up just uninstalling and reinstalling an app a couple times and it started working just fine, another question though. What's the best version of miui? And also what are the miui ports for? New to this Rom but its pretty seemless
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
MIUI Ports are the current versions of MIUI. The person who was creating the Inc builds used to be NIX, but when he passed the torch to Warttack, they needed to call it something different in ROM Manager (different packager, different section I guess). So basically, you should always be using the latest in MIUI Ports.

Everything is force closing on my nook color cm7 SD card. I am not much of a techie...any help would be appreciated. thank you.

Try fix permissions in ROM manager. You should post this in the nook color forum though.
Sent from my ADR6300 using XDA App

Phone freeze when installing apps

When I update apps or install new ones in the install process the phone basically locks up. Before and after it zips through like nothing is wrong.
Thoughts or suggestions?
I have done a wipe of the cache and I have even tested on fresh installs. This is a consistent issue across the synergy roms and even the short stint I was on the 3.0 nightlies. I also always to a 100% wipe and clear when I install roms btw.
Running Synergy RC2-Godmode

I would post this on the synergy thread to see what they come up with, but maybe you should try just running rsl 1 non-godmode. Might fix your problem.

have you tried fixing permissions with rom manager or amon ra(in amon ra it says fix missmatches)

I'll try the permissions. As for the version of Rom I have tried both. I am thinking its possibly hardware?
Sent from my PC36100 using XDA Premium App

i have this problem too,
how we solve it ?

If you can't run AOSP.... Freezes, lock-ups

I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.
Edit:
In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.
If you choose to format the SD card, be sure to back up your important files first.
If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.

i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.

sjpritch25 said:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
Click to expand...
Click to collapse
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Edit: if you experienced this it may help to figure it out

JAS_21 said:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Click to expand...
Click to collapse
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium

xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I've seen more than one user with the issue. One is a long time forum member.

xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from

I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.
I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.
I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.
I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.
All sense ROMS work.
I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.
I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.
Sorry for all the info. I just tried to give as much detail as possible.
Hope this helps,
Matt

Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.
Also, if anyone has a fix it can be posted here.

I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.

dch921 said:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
Click to expand...
Click to collapse
Were you running a sense ROM before Miui?

I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.
Sent from my mobile typewriter.

Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium

ftmaniac948 said:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.

It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem

Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?

stelv said:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
Click to expand...
Click to collapse
No, you should be fine.
Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also

JAS_21 said:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Click to expand...
Click to collapse
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium

For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me

ftmaniac948 said:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.
Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.

Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.

[Q] [Help] Constant force closing on certain ROMS

So I've got a strange one for you...
Here is what I CAN do:
I can ODIN back to stock 4.0 or 4.1 without issues
I can flash AOKP and Liquid Smooth roms without issues
Here is what I CAN'T do:
I can't install Cyanogenmod10, Hellfire, and Paranoid based Roms without continual systemui.exe force close errors and many many gapps force closures as well. It makes the ROM no longer usable.
I always factory wipe and clear both cache when flashing a new or different ROM. (I've done the whole "fix permissions" thing too, seems to make it worse)
I've even ODIN'ed back to stock and reflash to see if that fixed anything... NOPE!
I'm at a loss for what I've done to get these errors...
1. I have edited some files for the Google Wallet to work, but I no longer care about Google Wallet. Not sure if this would be a cause but its something right?!
I've been at this since G1 days, and I've never run into anything like this before.
Appreciate whatever assistance you can provide.

Have you tried a different gapps file? I've been seeing a lot of issues with different ones
Sent from my SGH-T999 using Tapatalk 2

bfranklin1986 said:
Have you tried a different gapps file? I've been seeing a lot of issues with different ones
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I always flash the Gapps that is associated with the ROM. Usually a dev recommends or modifies one to use.