[Q] Contacts Not Showing in 2.3.4 beta 4.5 ROM - Atrix 4G Q&A, Help & Troubleshooting

Although I when I use the dialer and actually begin dialing a number the matched contact appears, I cant see my "contacts" anywhere else -- in the app or in the contacts portion of the dialer.
I saw in the development thread that some people were having this problem, but the only solution seemed to be to watch what you freeze with TiBu. However, I'm on a fresh flash of beta 4.5, and have frozen nothing.
Any ideas? I don't know if this matters, but in settings-->accounts, it shows my Google account, but it is not under "motoblur" accounts.
Thanks in advance.

I had this problem. What I did to fix it was flash a fresh system.img of someone on the same build as me. Sounds like your /system might be fudged.
Find someone using the same kernel&version and try that.
Edit: if nothing else works, a factory reset will work, but that may cause problems, idk ()

Yea did you reset and wipe your data before loading the new rom?
I had same problem when I didn't wipe once I did and reinstalled 2.3.4 it worked fine.
Sent from my MB860 using XDA Premium App

Yeah I wiped furiously when I originally installed it and when I reflashed. Quick question, when you re-install, did you sbf back to 1.8.3, or did you just reinstall the zip with CWM? I just reinstalled the zip so maybe I should try a clean install.
Sent from my MB860 using XDA App

Related

Can't install or update apps!

Okay I can't seem to install any new apps or update any existing ones on my phone. I'm able to download them, but once it tries to install its always unsuccessful. Don't get mad if this is the wrong thread. I'm new to this but usually find answers to my problems with someone else's topic. Except for this one here. Any help?
Sent from my FroyoEris using XDA App
Try clearing system cache, reboot into recovery and clear dalvik cache, then reboot.
How do you clear system cache? Searched under settings could not find anything.
I've has the same problem. Lasted about two days. The apps would download but would stick on installing forever and would eventually fail. My solution was logging into Google on the phones browser. It seems like my account timed out on my phone, and after logging out and then back in, my market began to work perfectly again. You can also try what was posted above. Are you rooted? Cause of you aren't, then you won't be able to do those things said above. Good luck, hope this helps.
Sent from my nonsensikal froyo using XDA App
Tried clearing cache and signing in and out of Google. Neither worked. I have opera set up as default browser, tried with both opera & phones regular browser. Still nothing. Yes I'm rooted, running kaosfroyo v34.
Sent from my FroyoEris using XDA App
Try a factory/data reset. Sounds like your only option.
Reflash after that to make sure it loaded correctly.
A simple flash over to KaosFroyo V 37 fixed the problem. Thanks for the suggestions.
Sent from my FroyoEris using XDA App
Clear data for the market in settings. That usually works for me. If it doesn't, you can install the apps manually by using a file system manger (Linda File Manager, Root Explorer, etc.). The .apk should be in the download folder on the sd.
Sent from my ERIS using XDA App
Ok so I've tried all suggestions and nothing has seemed to work. I figured, why not try a new rom? So I flashed over to Vanilla Tazz. Seemed ok at first. Was able to update apps and download some new ones. Emphasis on SOME. Cannot for the life of me get back AndroZip which is my favorite file manager. Even backed it up with Titanium before all this started happening but still could not restore it. And now with Vanilla all you get is the crappy Android keyboard. So I download the HTC ime keypoard apk. Can't install that either. Try to download eoeAppInstaller to do so, can't install that. This is really, really, really pissing me off. Is a factory reset my only hope?
Sent from my VANILLA TAZZ using XDA App
Did you do a full wipe before installing the new rom? Try doing a dalvik wipe and rebooting. It shouldn't affect the current rom you're in.
Also, it sounds like whatever problem you had in the old rom was carried to the new one. Did you use titanium to restore any apps or settings? If so, you may have "restored" the problem.
Sent from my ERIS using XDA App
Have you messed with any system apps? Like moving the market to the sd card?
Sent from my ERIS using XDA App
I backed up my kaos rom and wiped all data and cache before flashing vanilla tazz. Just wiped dalvik but still no luck.
I used titanium to restore apps but no settings. And no I haven't messed with system apps. Should I try moving to sd?
Sent from my VANILLA TAZZ using XDA App
I had a problen with my FB not syncing with contacts (across several roms). Turns out something I was restoring with Titanium (not the FB app) was causing it. It'll be a pain in the rear, but you probably need to do a full wipe, flash a clean rom, and set everything up manually. OR you could probably nand restore to a rom BEFORE you were having this problem, create a Titanium back up, wipe, flash the new rom, and restore Titanium.
Hopefully, this will straighten things out for ya!
Sent from my ERIS using XDA App
Full wipe as in factory reset right? Will that unroot the phone as well, basically forcing me to start from scratch?
Sent from my VANILLA TAZZ using XDA App
Tried nand restore but kept getting an error and could not complete.
Sent from my VANILLA TAZZ using XDA App
Full wipe for "rooters" means wipe data, dalvik, and ext (if sd card is partitioned).
Have you renamed your nandroid? If so, remove any spaces and try again.
Sent from my ERIS using XDA App

Front Facing Camera and 2.3.4

I've installed KennethPenn's ROM for 2.3.4 and loving it, however whenever I try to change my camera to front facing mode, it fails and causes the camera to FC.
Is anyone else seeing this issue or is it possible that I simply have a defective/corrupted com.camera module?
TIA for any advice/solutions.
im runnings kens rom, faux kernal, and front facing camera works fine...have your tried using QIK and see if it fc's?
I hate to say, but it works fine for me also.
No issues with mine either....did you freeze anything?
Sent from my MB860 using Tapatalk
OK...thanks. I'm reflashing the ROM now. I hadn't seen others complain about it, so I figured it was likely just me.
Love 2.3.4!
Hmmm....after fresh flash, I still can't get the front facing camera to work. Fails and FC. I'll have to look into after I restore things.
I just verified that my front facing camera has no issues on KP's 2.3.4 beta 3.
Just tested. Working fine for me on beta 4.5
Sent from my MB860 using XDA Premium App
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Maybe you missed something. Here are the instructions I followed on 3 occasions now to flash 2.3.4 beta 3:
reboot into CWM
do a complete wipe( this order, DALVIK, CACHE, factory)
install beta 3
do another complete wipe
install the root zip
reboot and quickly press up to start in RSD mode
flash the new radio reboot in CWM
wipe cache and dalvik
Maybe following this procedure will help you.
<edit> If you follow this, and get reboots when installing apps from the Market, what worked for me was boot into CWM, wipe Dalvik, cache, and factory reset, install root.zip again, then wipe Dalvik, cache, and factory reset again, then reboot. Should fix that issue.
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
carlharsch said:
I'll give it a try.
I think when I restored from Ti b/u, it just rewrote the fault. I'll uncheck the camera app for the next restore
What do you mean by install beta 3 do wipe then install root.zip ???? I only have beta 4.5.
Click to expand...
Click to collapse
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Well...reinstalled with lots of cache wipes, and first thing I did was (after initial motoblur stuff) to try the camera....no dice. Looks as if it's bad.
I think going back to stock and calling Moto for a replacement might be in order
carlharsch said:
OK...so apparently I have a corrupted file for my camera app or a hardware issue. Any thoughts on how to repair/replace?
Error: The application Camera (process com.motorola.Camera) has stopped unexpectedly. Please try again.
The regular camera seems to be working fine, otherwise. Just freezes when I go to front cam (same thing happens in QIK), then I get the error.
Used KennethPenn's Rom .... going back to 1.83 safe?
Click to expand...
Click to collapse
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
dLo GSR said:
you shouldn't restore ANY of your system apps from TiBu if going between OS versions.
Click to expand...
Click to collapse
Agree with above completely! This is what caused me to have FCs with the contact manager. When I used TiBu to restore, I only restored my apps + data, not system apps. Worked like a charm.
Magnetox said:
Why dont you just take the data/app com.motorola.Camera
and the system/app/BlurCamera.apk
and system/app/BlurCamera.odex
from one of these peoples working phones, then paste them into their according directories on your phone. Should fix it.
Edit: also, you will probably need system/framework/com.motorola.hardware.frontcamera
Click to expand...
Click to collapse
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
carlharsch said:
I could try that.
Anyone with a working copy of Ken's 2.3.4 want to email me the files?
Click to expand...
Click to collapse
I would either pm ken or pm one of the people on the first page ( or all of them! Haha ) asking for the specific files. I would but im on bell.
Cheers
Did you search logcat and dmesg? Probably there is some info about what is the problem.
Enviado desde mi MB860 usando Tapatalk
After several more reinstalls, I "believe" I have it working again.

Insufficient storage available (market install)

I'm running the latest 3.0.27 (I think) market and I am unable to install anything, it will go through the download and then say insufficient storage available. I have 1.27 GB left on internal and am having no other issues... anybody know how to fix this or anybody else getting this?
(I lost gmail in some flash problems, gonna take it out of a rom zip I suppose but market won't let me get it the easy way or get anything else.)
Sent from my MIUI SCH-i500
sageDieu said:
I'm running the latest 3.0.27 (I think) market and I am unable to install anything, it will go through the download and then say insufficient storage available. I have 1.27 GB left on internal and am having no other issues... anybody know how to fix this or anybody else getting this?
(I lost gmail in some flash problems, gonna take it out of a rom zip I suppose but market won't let me get it the easy way or get anything else.)
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Wipe cache Partition and reboot
Sent from my SCH-I500 using XDA Premium App
Didn't work
Sent from my MIUI SCH-i500
Hmm.. Try clearing the app data.
Sent from my I500 using XDA Premium App
waiting for the new miui to see if that helps things, if I still have issues I will pursue this.
Sent from my MIUI SCH-i500
i'm actually having the same issue. my market seemed to update itself and now i can't actually update anything else and get the same error. does anyone have any other suggestions?
were you able to fix yours?
When this happens to me and it does quite frequently one of two things usually works.
1) go back into the market and tell the app to update again
2) if that doesn't work uninstall and reinstall the app
One of these two options gets the app to download and install for me
edit: just reread your op try in this case I wood suggest wiping everything and flashing the rom again
I also have this issue. It is really annoying.
Sent from my SCH-I500 using XDA App
sageDieu said:
I'm running the latest 3.0.27 (I think) market and I am unable to install anything, it will go through the download and then say insufficient storage available. I have 1.27 GB left on internal and am having no other issues... anybody know how to fix this or anybody else getting this?
(I lost gmail in some flash problems, gonna take it out of a rom zip I suppose but market won't let me get it the easy way or get anything else.)
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Any chance you flashed a new rom before this. I had this problem twice and both times it was when I flashed a nonvoodoo rom the voodoo conversion didn't happen. Just an ideal.
I am on gingerbread, no voodoo. I resolved the problem by doing a full data wipe/factory reset before updating MIUI. Everything works great now!
dood. ..did you happen to grab a logcat? I had this happen in cm7and realized that even though I had 1.3gb internal free, the /datadata partition was full.,
I never had this issue before that, and it even made apps start to fc! I checked by issuing the command df from term.
I moved a bunch of apps to sd, a feature of android I've never had to use until I upgraded(sounds more like a downgrade, I know) to gb! it worker but I still only have limited space (14% free) there while my /data partition has 1.3gb free...
I have never seen this before and my only clue from logcat where to even look was disk i/o errors.
Sent from my SCH-I500 using XDA Premium App
Wipe cache and dalvik. Should fix it. If not wipe big three and that should do it.
This was a big problem a while back and it was caused by not wiping cache after new rom install.
Sent from my SCH-I500 using XDA Premium App

[Q] DX2 CM7 Occasional VZNAVIGATOR Force-Closes?

Searched high and low on XDA and Google and could not find anything related to my particular issue. I'm running CM7 RC1 with Gingerbread 2.3.7 It seems like the problem is mostly occurring when I long press a contact to call or message, not when I take the longer route and tap the contact photo to the right on the contact info, then tap the phone icon and select which number to call....However I slightly remember there being a setting in the "CyanogenMod Settings" that stated something like "this setting may cause a lot of FCs" I just can't remember which setting it was... Here is the FC I'm getting:
The application VZ Navigator (process com.vznaigator.DROIDX2) has stopped unexpectedly. Please try again.
"Yes I am a noob to XDA but I have a lot of experience and understanding of flashing roms and what not, been flashing since HTC Dream."
Wipe dalvik cache in recovery.
Thank You!!
Thanks for the reply! I will try that, one question though. During the CM7 Install dragon said to wipe dalvik cache, can't remember when exactly in the install he said to do so but I followed the instructions EXACTLY, since then haven't had any problems whatsoever but this...Anyway, when I boot into recovery it doesn't actually said "dalvik cache" it just says "wipe cache partition". Is that the same thing? Also, I just recently flashed CM7 for the second or 3rd time as I had a problem with my primary gmail password yada yada...so now I have everything set up how I want in and now I'm moving on to Titanium Backup settings and freezing some apps (I am aware of which one I should and should not freeze) but being that I don't even use VZNAVIGATOR wouldn't it be wise to just freeze it? Thanks again so much for your help, wiping cache now....
To wipe dalvik cache go into the advanced section in bsr... Dalvik cache is listed there.
Sent from my MB870 using XDA
Wiped Cache Partition
So I booted into recovery and wiped the cache partition and rebooted. Everything seemed fine except that my roaming triangle icon was blinking so I connected to my wifi and my service came back. Then I did the *228 thing and updated my roaming capabilities, all is well with the service now. After that before I tried exiting out of my contact/dialer etc. I got the VZNAVIGATOR FC again. Going to try to freeze it in TB. Anymore suggestions would be much appreciated.
Dalvik Cache
Ok got your reply post about Dalvik location, wiping now, thanks again!!!
CM7 Android Recovery
when I open the CM7 Android Recovery app, (I already have it installed) and tap Recovery Mode, the phone shuts off and doesn't boot into recovery mode. So even after I manually power it up and open the CM7 Android Recovery
app and try to install first, then tap recovery mode, it does the same thing...any ideas??
My Apologies...
Sorry for all the questions. I research XDA and found that I need to have it plugged into the A/C. So now I was able to boot into recovery and wipe the Dalvik Cache. Thanks so much again, I will repost if it works.
Problem Solved!!
Thanks for the useful information! Very much appreciated.
Personally I would get rid of VZ Navigation and use Google navigation its much better. That's just my 2 cents!
Sent from my DROID X2 using XDA
Triscuit said:
Personally I would get rid of VZ Navigation and use Google navigation its much better. That's just my 2 cents!
Sent from my DROID X2 using XDA
Click to expand...
Click to collapse
He wasn't using VZ Navigator, it's just that if you flash over something (in this case the stock rom) without wiping the dalvik cache, there are bits of apps left over that you will see spontaneously force closing.

[Q] Push not working

Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
budisuharto said:
Hello guys
I need your help here. So I flashed this new ROM, and the Google Push service seemed to have stopped working completely.
1. Gmail not pushing.
2. K9 push not working
3. Google play store not pushing as well
I have played around (sync on,etc) but I can't seem to find what's wrong with it. So I tried to restore a previous Nandroid backup, but the md5 checksum was mismatched!
I then tried to wipe everything, reflash new ROM etc, and yet the Google Push services aren't working as well.
Can anyone help? I am stuck, I can't go back due to md5 checksum error, and I can't move forward because I don't get Google Push services
Click to expand...
Click to collapse
go to settings , accounts , Google delete it , then log in again
Yup, done that, still doesn't work. Plus k9 push isn't working either, it seems that the whole push function is completely broken
Sent from my GT-I9300 using xda app-developers app
Push seems an issue with XXDLI8 (at least in HyperGalaxy 1.8), just revert back to XXDLI7.
Yup I read about that too. The thing is I'm still on ICS, and I have never flashed a jb rom before. The error happened when I flashed hyper galaxy 0.7, which is a ics build.
I have given up on that rom, and I'm not on other rom and the push problem persists. I'm not sure what I did wrong, it's like the problem sticks despite me wiping cache, and everything else.
Sent from my GT-I9300 using xda app-developers app
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
j0ep0 said:
Maybe you can supply some more info, like what ROM and version are yiu using now, which baseband and what install procedure did you follow exactly?
Click to expand...
Click to collapse
Sure, here it goes. I have been flashing ROMs etc since 2010, so I am quite familiar with the concept, but this baffles me, before I can't seem to wipe everything clean and restart from point zero, because the problem sticks even after a new ROM is flashed. Is there more to this? Like modem/baseband etc? Thanks in advance for your help!
Baseband I9300XXLH1
Kernel Siyah s3 v 1.5 beta 4
Build no IMM76D.I9300XXBLG9
WanamLite ROM XXBLG V2.2
Thank you!!!
Ok I got it figured out already.
Previously I was on a full feature rom, then I flashed to a stripped down rom. I was short of a few apps, so i flashed additional apps, extracted from titanium etc, without checking their compatibility etc.
When I flash a new rom after that, I'll restore all system data via titanium, and that's why the problem persists. If I flash a new rom without restoring system data, then it's fine.
It's strange though, you'd think that titanium would be able to pick up on that if they aren't compatible.
Anyway problem solved and thanks for your kind assistance!
Sent from my GT-I9300 using xda app-developers app
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
jaidev.s said:
well happy that you found out a solution. generally titanium backup is used only for restoring apps not for system settings
Click to expand...
Click to collapse
Yea I realised that with SGS 3. With HTC Desire on Froyo/GB, the issue was nearly non existent, I never had a single issue, be it from Sense to AOSP, back to Sense etc.
Flashing is quite a pain then, if system apps can't be restored via Titanium, having to re apply settings like ringtones, widgets etc?
u can make a nandroid backup and restore
do kernels affect push ?
sorry to bring up an old thread, but i didn't want to open a new one just for this
i've recently flashed Perseus 24.2 over Omega 27.2 and noticed that Push notifications dont work when the phone is sleeping.
to get it working, i have to open up the app (eg. Whatsapp, hotmail) and i get all of them at once.
did a nandroid rollback to stock kernel and it was working fine
Q. is there a specific setting to kernels that may affect push?
probably Android ID problem
i didn't want to open a new thread for same kind of problem.
Problem occured when i fresh install DLIB (with wipes and everything). After installation complete, i've restored apps + systemdata with titanium. While restoring, it asked me to whether use new android id or restore the old one in backup. I choose to restore old one. then problems started.
- I can't use Google Play on the web. It says "there is no phone connected to this google account"
- none of my notifications are working. and i assume it is about android id. (today using Titanium i switched to new android id but nothing changed)
any guesses?

Categories

Resources