I got the OTA update this morning and my Sense UI has forced close twice now. This never happened before the update. Is anyone else having rhis problem? I will have to just shut off Sense till 2.1 comes out if it happens again.
View 3 Replies
I did the offical Froyo update on my phone this afternoon. It was stock with the latest OTA update 1.47. Followed the directions for the update and it went by smoothly until after I tried setting up my phone (Google account). I did a hard reset and everything was fine until a few minutes ago. I was able to sign into my Google, Facebook and Aim accounts. It is now back to an endless loop of trying to load Sense and force closing. Of course I can do another hard rest but is it too early to assume the force close loop problem will return? My phone is not functioning and I cannot even go into the setting to turn of Sense.
View 1 Replies View RelatedJust did the OTA froyo update from O2 last night. All appeared to go well and successful, past the point where I heard other people's got stuck.But when I slide down the slider and put in my password, it gets stuck in a force close loop for com.htc.launcher. Seems to not be able to open sense and keeps looping round.I saw a post from someone saying they had that problem, but then they just hit the search button and got the quicksearch, went to settings, then cleared the data for the appropriate application and then it worked fine.But when I hit the search button, nothing happens. If I hold it down, I get the google voice search, but I can't seem to get to settings from there.Does anyone know another method to get into settings as I'm hopeful this will fix my problem as suggested by some others. I'd much rather that than take it back to O2.
View 1 Replies View Relatedanyone else having this problem after the update to 2.1. When I had 1.5 it NEVER force closed. Any idea's what I can do? Yes I did the hard rest after the update.
View 11 Replies View RelatedI am running the OTA version of Froyo on my non-rooted Desire and I am finding that the HTC Sense UI seems to force close about once a week. The main culprit seems to be the HTC News widget as it most often seems to occur whilst I am reading my news each morning.Anyone else experienced this or know the solution?
View 3 Replies View RelatedMy HTC Sense is force closing every 5 minutes or so. I have battery pulled, uninstalled software, etc. I am about to do a factory reset but is there any software that is known to cause this problem (so I can avoid it on the second go around)?
Note: It appears to happen when i go to 'change the scene' to something else. When the screen reloads it just goes into an endless cycle of 'HTC Sense Force Close'.
Not sure what I after I rooted my phone but HTC Sense keeps either reloading itself everytime almost everytime i hit the home button from an App (a popup box will come up saying reloading, and my home screen is blank, then stuff appears slowly)OR In the middle of whatever app, i'll get an "HTC sense com.application bla bla force close wait ".Anyone know what I could of done to screw this up?
View 2 Replies View RelatedIt isn't easy to summarize the problem in the title.So in 1.5 or 2.1 v1 or v2, it was very rare for the Sense UI Home app to have to re-launch.By this I mean when you click the home or back button to return to your Home screen, instead of seeing the home screen you see the black screen with HTC on it, then you wait while it loads the Home application.This very rarley happened before v1.3. Now it seems to happen at least once or twice a day.I don't have more apps installed than I did before, I shouldn't be any more out of memery than I was before.
View 5 Replies View RelatedI am having problems running the youtube app... Whenever it is opened it force closes itself. It was working fine, though now it isn't... I tried clearing the cache and the only thing that helps is a restart, though once Youtube is closed (ATK) then it doesn't boot up all the time. It seems to be random...
View 1 Replies View RelatedI have been running the old leaked version of 2.1 on my phone since the day it was leaked. Today I installed the "new" leak, and now when I restart my phone I get an error saying, "the process com.htc.bg has to close due to an unexpected error." Then it makes me force close the process. My questions are, 1) does anyone know what this process is for? and 2) How do you suggest I fix this issue? Should I re-download from a different mirror? I have already tried re-flashing the zip that I have on my sd card.
View 14 Replies View RelatedSometimes, after the phone has been in sleep mode for awhile, when I hit the power button to wake it back up and then the menu button (or swipe) to open the screen, I get that circular bar pattern followed by what look like the browser trying to launch. The screen is white, with a white address bar area, too. Then that screen goes back to the circular bar pattern, followed by the white browser screen again, after which it just closes. Very odd. Doesn't do it all the time. Seems to be random. And after a hard reset, sometimes the first time or two I use the browser, it just force closes on me. Again, doesn't do it all the time. (At first I thought I accidentally hit the home button, or something, but I didn't.)
View 5 Replies View RelatedHas anyone else experienced the problems with HTC Sense force closing and being extremely laggy after installing the android 2.2 update?
View 1 Replies View RelatedFirst off, i use chomp for my messaging. Whenever I get an MMS and hit download it downloads the photo and right before it shows it I get a notification saying that "messages needs to force close" then the photo will pop up in chomp with no problems.
View 4 Replies View RelatedMy calendar has started to "force close" about 1 time per day now. the problem started about 1 week ago. anyone else have this issue?
View 2 Replies View RelatedI don't know what the deal is lately, but when I try to delete text messages, it just will NOT do it. It looks like it is "working" on it forever, then it goes to force close!
View 4 Replies View RelatedI keep trying to attach pictures using Handcent. Keeps telling me pictures are too large and resizing. Then it always force closes handcent. I increased maximum MMS size to 1M. Never had this problem til after the update. Have done a factory reset. Only thing I have not done is uninstall Handcent and reinstall. Anybody else having his issue?
View 6 Replies View RelatedAnyone else having issues with the phone and a system error message with something about com.htc.provider and it only gives you the option of a "force close" button. Sometimes that is all that happens and once you hit the force close the message goes away, at least for a while. Other times when this happens it deletes all of your text strings. I have 2 lines and 2 droids, both were having the same issue, did the factory resets, went to the store with both and finally gave in and took 2 refurbished phones to try and fix issue, both refurbished phones started doing the same thing immediately. I am in process of arguing with verizon about not wanting another eris to replace these.
View 4 Replies View RelatedNo not the OTA. My Helix Launcher decided to force close ALOT. Back to back. I rebooted my phone to no avail. I pulled the battery and nothing was fixed. I tried to pull the app drawer and select the Uninstaller app, but it would force closed before I could open it.
Then I had a revelation: I have the Market as one of my shortcut apps on my Helix dock. I opened it up and went to my downloads, and opened the Uninstaller app. Uninstalled Helix, and now I am good to go.
I tried to switch from 5 screens down to 3 and it all started.
I keep getting this message, "The process com.htc.provider has stopped unexpectedly. Please try again." followed by a box to 'force close.'
I seem to remember it wanted to update about a week ago, so I hit ok and then the update failed. It has not asked to try and update again since then....
The phone will display this message upon start up and also will occur at other seemingly random times.
The phone works fine after pressing force close but does anyone know how to stop this annoyance?
I rooted my managers phone and gave her 0.5.3 back when it was the standard fresh rom. Well last night she used fresh updater I believe to go to 3.1.0.2, which I know requires a wipe but she isn't exactly savvy on all of this. In any event, after the update the phone does not load the launcher. Upon unlocking the phone it is stuck in the com.htc.launcher has stopped unexpectedly. And after force close it loops this error. I can only see the lock screen or access the phone's SD card from my PC, I can change options such as "charge only" "disk drive" "usb debugging" but that's about it. Other than that I can get to Amon Ra recovery.What are my options for helping her out with this?
View 10 Replies View RelatedJust had the 2.2 upgrade via Vodafone & can`t compose a message. Comes up with "The application HTC_IME mod (process jonasl.ime) has stopped unexpectedly. Please try again". Anyone had the same problem or know a cure??
View 1 Replies View RelatedEvery day, at random times, I get an error message for com.smithmicro.DM. It forces closure. This happens several times every day. This problem began when I completed my Froyo OTA update. I don't notice any 'symptoms' following the message but still, I don't think this error should be occurring.
View 1 Replies View RelatedI have an android app I am just experimenting things on and I cannot seem to figure out why my app force closes when I update a TextView via a while loop. When I comment out the updateText method it runs fine.
CODE:....................
I've noticed my Nexus acting a bit buggy since the 2.2.1 update. Lots of force closes with the launcher. (which is exactly why I shredded and burned my old MyTouch for). After FINALLY getting a THIRD 16 gig card, after the other two got "damaged" costing me so far 25-30 gigs of content, I loading it up with movies and songs for my vacation. I go to reboot and it keeps looping the boot animation but wont boot up. Getting really close to kissing Android good bye as I've had NOTHING but bugs and damaged SD cards and an overall terrible user experience for a year and a half with two phones. I know we're only really two years into development but how much longer do we have to wait for a finished product that I don't have to keep making excuses for? More to the point WTF is going on with the boot loader on my phone and how do I fix it?
View 2 Replies View RelatedJust an FYI - don't update to the latest Facebook App version. It force closes every time even after reboots & reinstalls.
View 10 Replies View RelatedI don't know why. Install the package directly won't have any problem. But will fail because of Force Close if update the old package. the log is:
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): Caused by: android.view.InflateException: Binary XML file line #5: Error inflating class java.lang.reflect.Constructor
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.createView(LayoutInflater.java:512)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:562)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.rInflate(LayoutInflater.java:617)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.inflate(LayoutInflater.java:407)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.inflate(LayoutInflater.java:320)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.inflate(LayoutInflater.java:276)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:318)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.app.Activity.setContentView(Activity.java:1631)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.yidongsoft.ultraNoteEnhancedRegister.StartUI.setupWidgets(StartUI.java:237)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.yidongsoft.ultraNoteEnhancedRegister.StartUI.initialize(StartUI.java:129)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.yidongsoft.ultraNoteEnhancedRegister.StartUI.checkPassword(StartUI.java:591)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at com.yidongsoft.ultraNoteEnhancedRegister.StartUI.onCreate(StartUI.java:112)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1132)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2231)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): ... 11 more
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): Caused by: java.lang.reflect.InvocationTargetException
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.widget.ExpandableListView.<init>(ExpandableListView.java:198)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at java.lang.reflect.Constructor.constructNative(Native Method)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at java.lang.reflect.Constructor.newInstance(Constructor.java:446)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.view.LayoutInflater.createView(LayoutInflater.java:499)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): ... 25 more
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): Caused by: android.content.res.Resources$NotFoundException: File res/drawable-480x320/list_selector_background.xml from drawable resource ID #0x7f020005
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.Resources.loadDrawable(Resources.java:1625)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.TypedArray.getDrawable(TypedArray.java:548)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.widget.ListView.<init>(ListView.java:160)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.widget.ExpandableListView.<init>(ExpandableListView.java:202)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): ... 29 more
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): Caused by: android.content.res.Resources$NotFoundException: File res/drawable-480x320/list_selector_background.xml from xml type drawable resource ID #0x7f020005
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.Resources.loadXmlResourceParser(Resources.java:1843)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.Resources.loadDrawable(Resources.java:1620)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): ... 32 more
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): Caused by: java.io.FileNotFoundException: res/drawable-480x320/list_selector_background.xml
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:471)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): at android.content.res.Resources.loadXmlResourceParser(Resources.java:1825)
09-02 18:19:20.922: ERROR/AndroidRuntime(1659): ... 33 more
The file not found seems android embedded resources. Can any one explain why? I am using HTC Magic, official rom 1.5
I'm on orange, and I've just updated from 1.15.61.10 1.22.61.1 then to 2.17.61.2 (2.2 - froyo). After updating I've been getting quite a few process.android.acore force close messages. This error message was coming up during anything and everything I was doing. So I've done a factory reset, but after that, I'm still getting the messages. Maybe not so frequently but still getting them.
View 1 Replies View RelatedI own an xperia mini pro and I can replicate the issue always now. When I get an incoming call while the screen is off, if you slide out the keyboard (without opening the screen lock), immediately I get a Force close error for com.android.phone. I have Lookout Mobile security along with SayMyName installed. I have tried removing both, but the problem does not seem to go off. I am using Zeam as my home screen. On FC, SayMyName continues to call out the caller (or number if its not recognized), but the phone application crashes and on closing the FC pop up, the GSM mobile connection reinitiates (I am not in 3G).
Its just like when you switch on the phone after a shutdown. I have even tried changing home screen (ADW same problem), but seems like this issue persists. The problem is I keep my phone in a pouch attached to my belt and when I get a call, many times while bringing out the phone, the sliding of the keyboard happens and I get an FC. Then, there is no way to make out who had called and its very irritating (the call log does not register the call due to the FC).
Just recently update my phone to the latest build. Now TrackID force closes every time I try to use it. Is anybody else having this issue. or bet yet a solution? I have tried re-installing update.
View 6 Replies View RelatedI did the manual update and now when it boots up I do not get any network connection. When I go to the network connections it says that I am connected to the verizon network. But it will not show the bars or the 3G it just shows an x I am new to android. I used to update my Blackberry all the time I never had these issues. How do I get it back to 2.1 if I cannot get this fixed.
Also I went into my SD & Phone Storage Folder. And none of my SD or Phone Storage is available as if they r not even there. Now I am getting a window that pops up saying: Sorry System is not Responding force close/wait