Database Develop

[SOLUTION] "Android.process.acore" FC problem? Yet another solution. (LCD Density)

[SOLUTION] "Android.process.acore" FC problem? Yet another solution. (LCD Density)
Hey guys,
For the last 4 days straight I've been pulling my hair out like mad trying to figure out what on Earth was making my Contacts shortcut on my Galaxy S GT-I9000 go mental and tell me that Android.process.acore was dead and must close (on startup of Contacts.apk).
Like 95% of the freaks here, I mess with my Android ALL THE TIME. Adding new widgets, making things look better, customised to my personal taste - you know, we all do it. Now, 4 days ago, I changed a few things and started getting the Android.process.acore FC error whenever I tried to access my Contacts. After a bit of looking around google and XDA, it seemed that the one cause was from having synced your facebook contacts to your phone and having an incorrect birthday. Now, I don't remember syncing any new contacts as I've had problems in the past with the sync program (not related to this).
To rid of this problem, I read that backing up then deleting the Contacts.apk & ContactsStorage.apk cache would solve all my problems; well, it didn't. Even having an empty Contacts file would still bring up the FC error. So after a few dozen attempts, I reflashed back to a stock rom and low and behold, Contact.apk would load up. HORRAH. Thinking it was just Android being silly, I restored my NAND and go back into things. Contacts.apk still working, nice; I'll just restore my widgets and background etc.... BAM, Android.process.acore FC again, what the? Nothing would open that damn thing again.
Ok, Reflashed back to stock; this time, restored using Titanium Backup. Nice! Contacts are back and working; just setup my widgets and Background again... BAM, Android.process.acore DEAD.
Now, after trying each widget one by one to see which one was killing Android.process.acore, nothing changed... no widgets killed it... was still working....
HUH?
Ok, continue using Phone - BAM, dead!!! ARGGHH
Then I came up with an idea. I had been using LCD Density Change. Now, I've had it on a value of 200 for months now with no problems at all... what was my setting at the moment? 180.
Yes guys, CONTACTS.APK HATES a LCD Density value of 180!!!
Can anyone else replicate this problem at all? I haven't tried any other values yet to see what works/doesn't work.
I'm using the lastest LauncherPro Plus & LCD Density Changer 5.1.
Hope this helps some people

thanks for the post i also have the same problem on my captivate

Lcd den dosent work on froyo...
Sent from my GT-I9000 using XDA App

Hana. Sorry. This happened to me ages ago and its a known problem which is even in lcd densitys faq. Contacts wont work below 200. I have since replaced my phone/contacts app with youlu free from market. Atakephone is also another good replacemnt
Sent from my GT-I9000 using Tapatalk

okpc said:
Lcd den dosent work on froyo...
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
5.1 works fine on froyo
Sent from my GT-I9000 using Tapatalk

I can reproduce the problem on values 180 and 181 (haven't tried others yet). I don't have any problem though with a density value of 191 (my "default" density).
I suggest trying different values (maybe go lower, maybe go higher).
It is a well known problem that some apps FC on some specific density values. The "famous" FC is the FC-ing of the TWLauncher when you set it to a density of (I believe) 120 or lower. Please don't try this at home If you start up with that density and use TWLauncher as the default launcher all you can do is restore a nandroid or reflash the firmware. (that's why I explicitely advice in the help file of the Density Changer to first do a preview before saving the density as the system density)
@okpc Why would you say that? I also had some comments on the market saying that it doesn't work on Froyo. I never had any problem on any Samsung firmware Froyo version with it. Do you run a custom rom or kernel?
Note that different kernels can totally change the way rooting apps work on your device (and i mean totally). Or did you installed busybox? Note that all rooting methods install busybox by default except SuperOneClick... Second note: busybox installed by TitaniumBackup can't be used by other apps.

im getting this same issue but have not messed with the lcd density... i actually changed it to 225 to see if it would effect the contacts problem... but nah it didn't
i installed the contact.apk from sgs tools... but that didn't help still a FC when clicking it.

same problem on 180 density, but on 182 it working

DAMN IT. running KINGSROM HYBRID 3D and i have that problem. OVER AND OVER its acore acore acore acore FC FC FC FC. AAHH!!?!?!?!
difference between your problem and mine, mine keeps rebooting, and rebooting, and rebooting, never letting the home screen boot.
now i suggest, FCUK LCD CHANGER.

[Q] SPB Shell 3d v1.0.1

I have tried to run SPB Shell 3D v1.0.1 on my Nexus One quite a few times, but it closes automatically every time after starting. It is just me or has anyone else faced the same problem? Solutions?
I'm running MIUI Gingerbread 1.3.25

sohaibma said:
I have tried to run SPB Shell 3D v1.0.1 on my Nexus One quite a few times, but it closes automatically every time after starting. It is just me or has anyone else faced the same problem? Solutions?
I'm running MIUI Gingerbread 1.3.25
Click to expand...
Click to collapse
Hi,
Is it crashing (Force close) or just closing? Please send me a PM.
Thanks!

Mine on cm7 device not recognize error. Wat a waste
Sent from my Nexus One using Tapatalk

sohaibma said:
I have tried to run SPB Shell 3D v1.0.1 on my Nexus One quite a few times, but it closes automatically every time after starting. It is just me or has anyone else faced the same problem? Solutions?
I'm running MIUI Gingerbread 1.3.25
Click to expand...
Click to collapse
I have the same issue. Since I'm also using MIUI 1.3.25 it will most likely be a MIUI compatibility issue.
@nonpafos it just closes after a black screen(1 or 2 seconds) and returns to the last opened application. Haven't tried viewing logs though because I wanted to get a refund in time

I'm using it with MovieStars latest MIUI ROM and it works perfectly fine...

Mostly working for me, it froze at one point and my N1 rebooted and then got stuck in a bootloop, had to delete the /data/data/*spb* files. Seems ok now other than the icons in the "favourites" widget all show up as black squares at fullsize, but they're there when minimised.
Pretty cool, it's a bit impractical to use on a screen as small as the N1, it's much nicer using it on my Galaxy Tab.
I'm using the latest gigglebread fw & Pershoot kernel.

sohaibma said:
I have tried to run SPB Shell 3D v1.0.1 on my Nexus One quite a few times, but it closes automatically every time after starting. It is just me or has anyone else faced the same problem? Solutions?
I'm running MIUI Gingerbread 1.3.25
Click to expand...
Click to collapse
I'm having the same issue on my N1 running the Kang-O-Rama ROM (based on CM7). I've contacted SPB's support on the issue and they are working through it... not making a lot of progress on it yet, but I'll give them a little bit of time.
Are you running an a2sd implementation? I have noticed that if i move/rebuild my dalvik-cache to /sd-ext, the Shell will load and run (though very poorly). With the dalvik-cache on internal storage (/data), the application fails to launch. I don't have enough free space left on my /sd-ext partition to move the dalvik-cache there for good though

Had a N1 with CM7 RC4 & WN kernal, same issue.

Same issue on CM7 fresh install and MIUIFormel.

same issue here
i flashed the latest miui rom last night (1.4) and have the same issue as everyone here, screen goes black for a second then back to the other apps :-(
shame. Luckily I got my refund back in time. when I see this has been fixed I might give it another try.
cheers
D

I have the latest MIUI rom and it works perfectly fine for me...

Is there any way I can add a city to the weather widget? Maybe editing a file...
Nearest city is about 90 km from where I live...

The latest version in the Market (1.0.3) solved my black screen issue, and the Shell runs quite well on my device. I'm very impressed with SPB's support as well.
Maybe not worth the fifteen bucks, but I'm pleased anyway.

No animation

I just installed CM 7.0.0 using ROM manager on a nook color that was previously running manualnooter. When I rebooted i got the initial Nook phrase, then the screen went almost black. At first, I thought it was locked up. However, I came back to the NC a few minutes later and pressed the N button and low and behold everything was there.
I rebooted a second time to see if it did it again. It did. Notification is telling me the start up time was 44 sec though it seemed like longer.
Can anyone tell me how to get the animation back and maybe what happened to it? Thanks

I can confirm this issue with a friends device.
She bought her nook color with firmware 1.1 pre installed and 1.2 was just released, so I did a manual update and tested it. Then put my sd with rom manager and flashed a cm7 nightly (cant remember which) + gapps + 1.3 OC kernel.
Its exactly the same issue and I want to add that it gives the sensation it is doing nothing, so you may press random buttons and suddenly you are able to unlock the device after some time.
When I get the chance I will install a newer version, or maybe this awesome cm7 build for kernel .32 I'm using on my device, and report to you guys.
Any ideas?
Sent from my NookColor using XDA App

Same Issue
I have the same issue, except I previously used autorooter instead of manual rooting. Any suggestions?

I've had issues with the boot animation not working before as well - it all seems to depend on the exact combination of ROM, kernel and (maybe not) google apps. With the latest CM7 nightly for Nook Color, the Dalingrin OC emmc kernel from 5/23 and the google apps from 03/07, the boot animation works fine.
The previous combination that I used - CM7 7.0.3 stable, older OC kernel and same Google apps didn't give me the boot animation...
Besides all of the that, the combination I listed above seems to give the best overall experience as well (at least so far). Everything works perfectly without any lag anywhere! Try it out...

Well, I went ahead and istalled CM7 7.0.2 stable and got the animation back. Now my problem is the little apps icon that appears at the bottom of the home screen is missing. The only way I can get to my apps is to open Marketplace and go to MY apps. They are there and seem to work. Can someone help me get the Apps icon back? Thanks

I figured I might fix this by installing a different launcher, so I installed Zeam Launcher. It seems to work oK. However, the original ADW launcher is still missing the My Apps icon in the lower box.
I tought perhaps if I reinstalled ADW, it work repair the problem. I did that and now I have two entries for ADW when I press the N key. One works fine but the other still has the missing icon.
I then decided that maybe I could uninstall the one giving me a problem. When I went to Android Assistant to uninstall ADW, I only saw one entry.
So, my question now is how to get rid of the extra ADW install. Thanks
Or how to get the my apps icon back in the main Dock at the bottom

[Q] Honeystreak HD7

Love the new ROM, but Market only works/installs apps through browser is there gonna be an actual market app with an icon?

My Market Icon
I installed [ROM][RC2] HoneyStreak HD7 V1.5 (3.1) and the Market icon was there because I downloaded from the market. The next time after I rebooted, I lost the Market icon. It disappeared and has never come back. I have also lost other icons. I'm not sure how to fix this. Everything worked good on RC1. I need help.

No icons and WiFi with HC
Since I've installed HC RC2, I keep losing my icons. Every time I start back up, I have to set up the WiFi again. This never happened before. Help!!!

Are you sure it's not just a display issue. Some of the icons get cut off on rc2. Try going to menu/settings/applications/manageapplications and scroll through to see if they're there.
Sent from my HTC Vision using XDA Premium App

My Icons are Back with RC3
After I installed RC3, all my missing Icons returned. I'm still testing but everything looks good so far. Compared to other tablets, this DS7 seems very fast.

I 've been having market issues too. Waiting to install hangs a lot but it works off and on... works more often than not so its not a complaint. Maybe my network. Also a couple reboots and no Bluetooth... not that I use it. Very happy with rc3.
Sent from my streak 7 using XDA App

Maps 6.x crash

I'm running CM7.1 stable, and I'm noticing that the latest 6.x versions of Google Maps crash HARD. No idea why. Was able to revert to a backup of 5.9.0, which still runs pretty smoothly.
Sent from my Nook Color!

Updated to maps 6.x and it was unresponsive when the map displayed location. Reverted back to maps 5.x from Titanium Backup.

Okay. Glad it's not just me!
Sent from my HTC Glacier using Tapatalk

Start 6.0, it crashed and FC'ed all the times.
I updated to 6.0.1, to 6.0.3, still no go.
I guess, reverse back to v. 5.12 is the best.

Same here, reverted back to 5.11 from TB.

cmstlist said:
I'm running CM7.1 stable, and I'm noticing that the latest 6.x versions of Google Maps crash HARD. No idea why. Was able to revert to a backup of 5.9.0, which still runs pretty smoothly.
Sent from my Nook Color!
Click to expand...
Click to collapse
Exact same thing here, with CM7.1 and Maps 6.0. I found Maps 5.10 online, D/L/ed and installed it. All 's fine now.

I am running the MiRaGe CM7.2 on my NC, Maps 6.0.3 works fine. FYI.

CM7.1 and maps 6.x crash for me aswell

In my Viewpad 10S (3.2) is the same, the solution is uninstall the update to the lower one.
Don't update to 6.0

hmm does anyone know if the ownhere/brutall maps fc aswell?

I've encountered the same problem described here. Today I tried to change the LCD resolution setting from 160 DPI to 240 DPI and it seems the FC issue gets better. The new problem is the icons on the status bar is getting larger and occupying all the space. Therefore the clock could not be read anymore. Is there any trick to tweak the icon size on high DPI setting?