Related
I've put 026 on my phone twice now, with 2 seperate downloads (incase one was corrupt) but it always crashes apps, like timescape, the web browser, the market, even the uninstall app and many others...
Anyone else get this, or have a fix? I dont get it with 024, but would prefer to use 026 because it seems a little faster.
same thing happened to me after I stopped some of the apps from startup. that gave me about 180mb free though, but nearly all the apps were crashing, they were not force closing but simply vanishing. then I enabled everything while booting and everything was fine. so now am trying to stop one service or app one at a time to find which one of them is causing this.
Sent from my X10i using Tapatalk
Hmm i dont have any app killer installed though... but i did have one installed before flashing. But flashing would have completely removed it?
The very first time i started the phone after going to 026 i got this crashing, which happens exactly how it does with you.
nope, very first time I installed 026 everything was fine, only issue I had was when I used the app "my backup pro" to restore my messages, contacts etc, somehow my phone started sending messages again, the same ones that I already had sent in the last 4 months,I had to delete all the threads quickly or there were about 2000 messages which could have been sent.
then I started with the boot manager and disabled nearly everything, that's when vanishing of the apps started, nothing before that. but I guess its working fine now. am only disabling apps I installed, not touching anything I don't know, phone seems to be working fine.
Sent from my X10i using Tapatalk
I also experience this constant crashing of apps.
Sent from my X10i using Tapatalk
guys, try not to kill all the services, instead eliminate them one by one to find which one is crashing your phone. mine seems to be working fine now
Sent from my X10i using Tapatalk
Running th3ory 1.6.5, phone apk fc almost every time I use it after call, sometimes the radio shuts down showing no signal? Any ideas?
Sent from my ADR6400L using XDA App
by any chance do u have facebook and twitter synced to your account? i heard one of these causes this problem. i used to have this same exact problem too but once i removed these syncing accounts from my phone it was fine
Ill give that a try. Thanks
Sent from my ADR6400L using XDA App
No luck, radio stills goes no service an phone fc's...
Sent from my ADR6400L using XDA App
Did you use titanium?
THUNDERBOLT
No, I don't use titanium. I've tried all kinda things, no change.
Sent from my ADR6400L using XDA App
Do a full wipe. Data, cache, and dalvic. Check the md5 on the rom. Reflash. It's easier then trying to track down the bug.
I am having the same problem, and its driving me crazy. On BAMF 2.0.5 or 2.1, no problems, anything else and phone force closes on every call. Ive changed radios, stopped syncs, removed programs. Would really like some help to figure out what it is...
Have you tried aligning applications and fixing permissions. I was having similar problems and after doing those two things I realized my problems had disappeared. I'm thinking there's other issues there, but might as well take a shot at it.
I have tried, but i think i just figured it out. I removed twitter but didnt unsync the htc sense twitter. The force closing (now that I think about it) doesnt happen all the time, it just seems like it because its only when my wife calls me.
I unlinked her twitter account, and now seems to be working fine?
im having same problems. the radio does die out right when its crashing. could this have anything to do with this phones ability to do simultaneous data and phone? I will try to remove and unlink the twitter but I believe it was crashing with only my google account linked,
it appears to be sense 3.0 which is the problem for me. I wiped and flashed a senseless version and a sense 2.0 version and neither has the problem. On any rom with sense 3 or hybrid my phone dialer crashes upon calling?
I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Suboof said:
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Click to expand...
Click to collapse
Yes, I performed a full wipe before flashing the ROM, assuming that means data/factory reset, cache, dalvik cache, battery stats...did that three times. Not sure if I am supposed to do it more. Also checked the md5, downloaded and flashed it twice more after the first time, and still can't get it to work.
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Suboof said:
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Click to expand...
Click to collapse
Never mind, I thought I got it working, but after playing a song, it crashed. I might just go back to stock rom, not a really big issue.
hksg said:
I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Click to expand...
Click to collapse
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
I am running bamf 2.0 - 5 and it works for me.
Although it Sometimes makes my phones signal drop to 1x so maybe flash a new radio?
THUNDERBOLT
poisonj5 said:
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
Click to expand...
Click to collapse
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
hksg said:
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
Click to expand...
Click to collapse
same for me. I'll be going back to stock or another ROM until this gets solved
theredspecial said:
same for me. I'll be going back to stock or another ROM until this gets solved
Click to expand...
Click to collapse
ATM, I am using Lighting Rom 3.3.1, which is a Froyo ROM, but I might try one of the other Gingerbread ROM's available. But I really did love that DasBamf ROM, and the issue seems to be amongst just a few of us.
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
I can confirm I'm having the same issue with BAMF 2.1 stripped. I tried reloading the rom without wiping and fixing permissions and still getting a force close when I attempt to play anything from the cloud.
Sent from my ADR6400L using XDA Premium App
hksg said:
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
Click to expand...
Click to collapse
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
FreemanB said:
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
Click to expand...
Click to collapse
It was indeed the HTC Music app that is the known issue. I posted in the thread, and I provided a logcat, so hopefully someone with more experience than me can understand it.
I'm having the same issue on DAS BAMF 2.1 on latest lean kernel.
I can get it working 99% of the time with wifi only. If i use 3g or 4g the app force closes. I've tried different kernels as well.
Anyone else able to confirm if this issue is wifi/3g/4g related? Im able to use the player only if I use wifi.
Maybe this can help the devs push out a patch in 2.2
I am using it right now on RC3
Sent from my ADR6400L using XDA Premium App
I'm also able to get it to work if i wirelessly tether to another thunderbolt. Only time I have an issue is if I'm using the 3g/4g radio.
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
BlackHoleSlam said:
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I mean I can access music.google.com from the browser but that kind of defeats the purpose of the app/widget.
My friend who has the same rom isn't getting the issue.
PLEASE NOTE: This patch addresses application force closes on newer google maps applications (5.5-5.7) running on gingerbread-based ROMs for the ERIS. This does not address reboots/restarts (see http://forum.xda-developers.com/showthread.php?t=1157099 for progress on this other problem)
After extensive testing on CondemnedCM7 V15, I believe that the Navigation force closes many of us experience on the newest maps version is fixable (at least on Condemned's ROM; GSB users report that problems still remain) by rolling back google maps framework files to a version used for Android 2.2 ROMS. I have been testing since last week and have not had a single navigation force close. My longest test was 1 hour 10 mins with multiple reroutes and no force close. One known issue, Map application (not navigation) will unexpectedly close (that is, will not offer a force close but will shut down) randomly while using the search box. I have not been able to consistently reproduce this
I am attaching two zip files flashable from AmonRa Recovery if you would like to try the fix. The first replaces the current maps framework with the froyo framework. The second rolls back the change to the latest gingerbread framework.
If you are using maps 5.2 which CS included in the system apps for v15 and are happy with the result, then you do not need to flash this file. If you would like to use the newest maps app (5.7), you may wish to try this.
In theory, this fix would work on an AOSP or Cyanogen gingerbread ROM, so if folks on other devices are having similar problems, they may want to try.
Good luck everyone!
NOTE: this is repeated from CondemnedSoul's CM7 thread. The attachments can be found there: http://forum.xda-developers.com/showpost.php?p=15978440&postcount=535
Thanks for everything your doing on this issue.
I upgraded to 5.7 and flashed the patch. Ran Nav for 30 minutes and all was fine. Not sure when I can test longer but if I do I'll let you know the results.
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Glad its working for someone other than me!
Sent from my ERIS using XDA App
I can't believe no one else is trying it and letting you know their results.
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
klobkelosh said:
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Or the only ones that use that ROM lol
Lol!
Sent from my ERIS using XDA App
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
klobkelosh said:
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Have to go get it myself.
klob, will upgrading to 5.8 overwrite the fix files, or should I have run the unfix before upgrading?
Either way all I did was upgrade and so far Nav has been running for 40 minutes. Not driving anywhere, just have Nav running while I'm in the house.
Upgrading maps app will not affect the fix, so if you want to find out if it works with stock gapps, you'll need to flash the unfix. Also, bftb0 on the gsb thread has demonstrated that desktop navigation is not a good test for force closes. I'd get it on the road to be sure.
My commute starts in about 15 minutes. I'll report back soon...
Sent from my ERIS using XDA App
Update: it seems google had fixed whatever was misbehaving in maps 5.7. No force closes on my commute.
Sent from my ERIS using XDA App
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Sir_Eagle said:
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Click to expand...
Click to collapse
Odd. I just full wipe installed ccm16sth with 5.8 maps and navigation worked fine. One thing I did was disable text to speech, maybe that's the culprit? You can disable by renaming system/lib/libtts.so.
Sent from my ERIS using XDA App
klobkelosh said:
You can disable by renaming system/lib/libtts.so.
Click to expand...
Click to collapse
I don't have that file, got libttspico.so and libttssynthproxy.so.
Sorry, its the libttspico.so file
Sent from my ERIS using XDA App
GPS files the culprit?
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
aceof89 said:
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
Click to expand...
Click to collapse
I tried Telenav with the same force close issue too
Sir_Eagle said:
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Click to expand...
Click to collapse
Something I noticed... making me wonder if it's memory allocation issue... after a reboot, going right into Nav, it still force closes but not until 30+ minutes,
If I haven't rebooted in a while and have been running other apps like, gmail, exchange, facebook, and the going driving with NAV the reboot happens right away
I've tried everything I can think of or find in this subject but I can't figure it out.
I'm getting FCs all over and seemingly randomly.
There's no one program doing it either.
I've used cyanogen 7 7/17 version with glitch kernel (both 11 and 12) and the v3 kernel. Maybe the stock but I don't remember.
Also flashed the dl09 or which ever radio was recommended for cm7 on the ROM list sticky.
Tried the nighties and am on not the recent one but the one right before it with stock and glitch 11 and 12. Also tried before and after v6 super charger which seemed to make my launcher before faster and without the stopped responding dialog.
I also use the ultimate kernel removing script between kernels.
Here's what I've already done to try to fix it:
Wipe big 3. fives it for awhile then starts up in force.
Wiped to stock 2 or 3 times. Still happens.
Fixed permissions. Works longest so far but still starts up again later.
Wipe cache and data in manage applications settings menu for creasing programs. Works for a while usually but then goes
back to crashing.
I followed ask instructions to install everything properly.
The only thing is that
do I need a special bootloader with nighties and stock kernel?
What am I missing here? It seems like it's related to wifi because I can keep things stable a little longer with wifi off but it is not always 100%. Definitely related to internet. Also seems like the cache reaches 2-3 megs when programs crash
browser seems to be more likely to crash. Will crash constantly and I'll open up Firefox or opera wends everything is peachy. I think neither ox those browsers crash from what I can tell.
Oh and could it be gapps somehow. I'm not sure but it might be a case built that all the crashing programs are gapps.
I've tried the new version 2.2.5 I think posted somewhere and the original 2.2.3 I think. I'm pretty sure they both crash.
I'm maybe to frustrated to see what's right in front of me and I maybe have forgotten an important detail so please forgive and I'll be happy to provide any info.
This is near perfect and that's the thing that's holding me back right now.
Anyone else have this happen to them? Any advise?
Sent from my SCH-I500 using xda premium
How did you originally come to cm7..ie. What was your previous rom and kernel prior to making the switch?
What steps did you take to get to
mtd format?
And lastly I read your whole OP but am still unsure if you've tried Odin'ing a stock VZW official rom to start from scratch? (ie. Eb01,dl09, or ed05)
Edit: Also did you restore any apps or system data via titanium backup?
Sent from my SCH-I500 using XDA App
I've come to cm7 at least twice from a stock froyo ROM. I followed the directions in the sticky exactly. At least twice.
I did restore titanium but not from non-mtd. I reinstalled every app one by one after upgrading.
I'm thinking it might be the wrong gapps. If browser is a part of gapps, I'd betting on it then. It seems the fc's might all be related to
the various gapps.
That's the only thing that I can think if that I haven't tried.
Sent from my SCH-I500 using xda premium
Here's the latest gapps.zip includes market...don't know if you've tried this oneand I don't think it contains anything for the browser, but i'm not sure...its for Mtd builds.
http://forum.xda-developers.com/showthread.php?t=1191063
Edit: i'm also assuming you've ran fix permissions via cwm or terminal emulator right?
Sent from my SCH-I500 using XDA App
I'm making you assume a lot, sorry. Yeah. Did all that.
I'm trying to isolate it. I'm seeing that the force closings are maybe not so random.
It's the browser, google services framework and programs that I guess rely on browser. They are programs that access the http protocol. Reddit/f5, Chan browser etc. I've yet to have a program crash that was not accessing the internet like chuzzle.
Gmail does sometimes too.
Anyway, if they fc I go into manage applications and usually clear cache for the offending program Anne it works again until the cache gets up around 2 or 3 megs give or take.
I know people have been complaining about the data cutting in and out on this ROM so maybe that's involved.
I originally thought it was wifi because it seemed to only happen on wifi but i'm getting it on 3g but not as often.
I'm thinking that the data appears to be on but isn't and it's confusing programs but then there would be others with the problem. The other theory is that my cache space is fried.
Sent from my SCH-I500 using xda premium
In case someone finds this buried down here with the same issue, here's how I think I fixed it.
Wipe data again. Make sure you let the gapp installer install everything itself.
Titanium backup: restore missing apps (double check for went google apps) and data. Or hand install your apps and restore data.
I have the install location set to original.
That seemed to work even with the seeming wifi cut out and the whole thing.
I also didn't install Firefox or opera this time. That shouldn't be the problem but i'm recording it here anyway just in case.
Good luck
Sent from my SCH-I500 using xda premium