I'm on a VZW tab and when apps force close, I get the 1 vibration followed by a succession of quick vibrations, then the popup notification of an app force closing.
However, twice now, my tab has had the vibrations as if an app is going to force close, but no window pops up. On top of that, the vibrations just repeat in that order over and over again approx every 30 sec. I've had to reboot each time to get this to stop. I've tried the built in task manager to kill all running apps, but only launcher pro is showing. I've tried using ATK to kill everything running also, but that doesn't help.
Has anyone ever had an issue remotely like this?
I have the 2 vibration isue but not the other.
Sent from my GT-P1000 using XDA App
i also had the vibration force closing issue when i was on stock froyo.
but when i upgraded to overcome rom and also the gingerbread stock rom.
apps became more stable and has less forcecloses than before.
there was a significant improvement.
are you still on stock froyo?
Yes i recomend upgrading to 2.3.3
My tmobile tab used to do that on 2.2. A little less on 2.2.1
Havent seen it yet on 2.3.3
Ifyou dont want 2.3.3, and i wouldnt blame you, go the overcome route.
Don't Panic
peacekeeper05 said:
i also had the vibration force closing issue when i was on stock froyo.
but when i upgraded to overcome rom and also the gingerbread stock rom.
apps became more stable and has less forcecloses than before.
there was a significant improvement.
are you still on stock froyo?
Click to expand...
Click to collapse
I am rooted, but still on stock froyo.
Sent from my SCH-I800 using Tapatalk
ssserpentine said:
Yes i recomend upgrading to 2.3.3
My tmobile tab used to do that on 2.2. A little less on 2.2.1
Havent seen it yet on 2.3.3
Ifyou dont want 2.3.3, and i wouldnt blame you, go the overcome route.
Don't Panic
Click to expand...
Click to collapse
I'll have to see what the best GB rom is for the VZW tab. Then netflix would likely work also!
Sent from my SCH-I800 using Tapatalk
my tab did the same thing today twice in a row. this is the first time it has done it i rebooted then hasent done it again
Solved!!!
So this issue has been getting progressively worse, so I went through app by app in the application and service menu and started force stopping them one by one. Turns out it was lookout mobile's background service causing this. The service, not the app, kept force closing and restarting, hence the force close vibrations, but no popup.
I uninstalled and reinstalled it clean and will continue to monitor. So far the issue has not returned.
update: after a reboot, the issue came back, so i just uninstalled completely. After a reboot, no issue.
Related
Hi All
I have yesterday updated my T-Mobile UK Galaxy S to Froyo using the regedit method.
All seemed good and I was very pleased with myself for doing it!
But....
Since the upgrade I have had many Force Close's and there seems to be a fair amount of lag.
The main issue is the messaging app opens but when you go to open a message it FC's.
I am running Launcher Pro so will try running standard Samsung launcher for a bit.
Anyone else had this?
Do a factory reset!!
Yeah I too had loads of problems after the upgrade like you. Very slow, crashing, reboots. Although TWlauncher never worked properly for me before, even on 2.1.
Did a factory reset using the 3button reboot and it's been fine since. I was surprised that this didn't clear the memory card, so still have all my files - which I wasn't expecting.
Thanks guys that did the trick.
And forced me into a bit of phone housekeeping as well!
After using my tab for 5-10min after a restart, my tab become very slow, to the point of it being unusable. I haven't installed any new apps, just updated some from marketplace, which I deleted. It started this morning. I'm running stock jjb Tmo usa. My tab is also rooted just to freeze some application with T. Backup.
Anyone else experience this? What could I try?
Sent from my SGH-T849 using Tapatalk
install advanced task killer and check what you have running. Kill some apps and see which helps.
once you have found the cause uninstall it and find alternative, If its a system app freeze it or uninstall it with systemapp remover.
I hardreset my tab yesterday, I kept some apps using titanium backup, only the important stuff and I have to say, it's way much faster.
I had several lags and crashes but now Im good
Ok I did a hard reset and my tab was working fine for a few days and now it's back doing the same, going really really slow after a few min of using it. I killed all apps and not even a spec faster... Is it my tab? Should I format internal SD card?
Sent from my HTC Glacier using Tapatalk
nysoprano said:
Ok I did a hard reset and my tab was working fine for a few days and now it's back doing the same, going really really slow after a few min of using it. I killed all apps and not even a spec faster... Is it my tab? Should I format internal SD card?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Sorry to say but don't use Task Killer. It won't help since it only lists what is residing in memory without any other useful info on what to kill.
The most you can do with it , is blindly killing them which doesn't help with the performance or might break something else. The best alternative is Active Apps or watchdog lite which monitors application's CPU usage.
A tip if you just start Android,
Try to use back button ( Close Application) rather than Home ( Put application on standby mode). If you forgot to close applications, try to use Active Apps / Samsung Task Manager to see if anything is left running and close them.
Hope this helps.
Nope, still getting random slow downs. Anyone using launcher pro? After reset, my tab slows down after a few hours. Slow to the point of not being able to do anything but restart.
Sent from my SGH-T849 using Tapatalk
nysoprano said:
Nope, still getting random slow downs. Anyone using launcher pro? After reset, my tab slows down after a few hours. Slow to the point of not being able to do anything but restart.
Sent from my SGH-T849 using Tapatalk
Click to expand...
Click to collapse
Had my Tab for several months now using Launcher Pro and various roms without the problems you're having.
Are you using a custom kernel with overclocking and profiles? If so try reverting to stock speed (1000MHz) without profiles.
You could also try a full wipe and reinstall rom without any apps and see what happens. If ok install apps one at a time and test and see which app, if any, causes the problem
look in errlog
download error log from marked and see if u have continues errors.. close any 3d party apps and start the logger, then start any 3rd party 1by1 and see if it generates errors..
I'm running pure stock, us tmo jjb rom. I'm rooted but left rom alone. No overclocking either.
I downloaded log toast, anything special i should look out for? There's a lot of info, don't know what to make of it.
If It keeps happening, might just install new rom.
Sent from my SGH-T849 using Tapatalk
Ok so i installed log toast and i was monitoring all the errors on my tab. After a fresh restart, i was looking at this thing get errors for:
E BluetoothAudioGateway.cpp(2573)
Pollhup detected
It kept showing over and over and over, but no slow down...I think it was because i had bluetooth turned on.
So right when it started to slowdown really bad, keep in mind that i kept it on the home screen and wasn't using it, just connected to charger and that's it, i started getting a new error message:
E IMGSRV(2497)
PVRSRVEventObjectWait Timeout!
Anyone know what this means??
nysoprano said:
Ok so i installed log toast and i was monitoring all the errors on my tab. After a fresh restart, i was looking at this thing get errors for:
E BluetoothAudioGateway.cpp(2573)
Pollhup detected
It kept showing over and over and over, but no slow down...I think it was because i had bluetooth turned on.
So right when it started to slowdown really bad, keep in mind that i kept it on the home screen and wasn't using it, just connected to charger and that's it, i started getting a new error message:
E IMGSRV(2497)
PVRSRVEventObjectWait Timeout!
Anyone know what this means??
Click to expand...
Click to collapse
maybe the rom that you have now has defects which is quite common. if I were you I would flash to overcome version which runs better or return that to samsung for checking.
Sent from my GT-P1000 using Tapatalk
It's weird I have been experiencing the same type of things. I'm on defualt Verizon rom with superoneclick rooting. Everything else is stock. Started happening yesterday. Maybe it is linked to the update Verizon pushed out? I'm going to start looking into whether I received the update or not and work from there? Keep us posted nysoprano.
elnews said:
maybe the rom that you have now has defects which is quite common. if I were you I would flash to overcome version which runs better or return that to samsung for checking.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
tried searching for both ure errors, came up blank, even if they would repeat endlessly it would not slow the system down that mutch. U tried a factory data reset right? guess u could flash a alternative kernel/rom and look for same trouble if so u would assume hw problems? sorry for no straight answer.
Is Advanced task killer rubbish?
TheATHEiST said:
install advanced task killer and check what you have running. Kill some apps and see which helps.
once you have found the cause uninstall it and find alternative, If its a system app freeze it or uninstall it with systemapp remover.
Click to expand...
Click to collapse
Actually my experience with Advance Task Killer (ATK) is that there is never a remarkable improvement! When you kill apps listed as running sometimes freed memory report seem to be temperamental - reduced, no change, increase...
The shocking thing is that killed processes quickly reappears in the list again!
Is there a better app than ATK out there that truly terminates and frees memory?
Ta.
nysoprano said:
Ok so i installed log toast and i was monitoring all the errors on my tab. After a fresh restart, i was looking at this thing get errors for:
E BluetoothAudioGateway.cpp(2573)
Pollhup detected
It kept showing over and over and over, but no slow down...I think it was because i had bluetooth turned on.
So right when it started to slowdown really bad, keep in mind that i kept it on the home screen and wasn't using it, just connected to charger and that's it, i started getting a new error message:
E IMGSRV(2497)
PVRSRVEventObjectWait Timeout!
Anyone know what this means??
Click to expand...
Click to collapse
I am having the identical issue. I have a completely stock AT&T tab (no root, no overclocking, no custom ROM, etc.) I have turned off Bluetooth, and it seems to have fixed the issue. Possibly a Samsung Bluetooth bug?
Hey all,
I am currently running my VZW Galaxy Tab with a stock 2.2 Froyo build that is rooted and running Boushh's KhasMek Kernel V5.
Ever since I installed that kernel, I have been experiencing constant force closes. It's really not any one app either, it is most of them. So far, I have put the freeze (via Titanium Backup) on all the apps that have FC'd a lot that I don't use. Maps was one of the biggest culprits. Facebook FCs a lot as well, and the only way to fix it is to go into app management and clear data. Similar issues with random games and such as well.
I have tried uninstalling and reinstalling multiple apps, and this helps for a time, but doesn't last too long. I have tried switching launchers, just in case it was somehow related, but it doesn't seem to be.
Basically, whenever I leave the tablet on idle for more than a few minutes, when I unlock it something hangs and I get an FC of a random app.
And a lot of times, it just does the single vibrate, followed by two quick ones, and nothing comes up as having FC. But, in the mean time, the tablet is unusable until it hits the second set of vibrations.
This is extremely annoying and is preventing usage of the tablet for periods of time. So, I am wondering, is anyone else experiencing this? If so, what have you done to fix it? At this point, I am inclined to just revert back to stock, though I would rather not.
Thanks for any insight.
As of now, I am constantly getting
com.google.process.gapps
force closing.
okay so i have installed JVQ on my phone seemingly successfully except after about a day of having the ROM installed I have started getting issues such as force closes. I cannot remember what forcecloses off the top of my head but also problems with messaging, quite frequently i will open it up and it will just shutdown no forcle close nothing and i will have to keep clicking messaging and it will show me all my threads not load peoples names then close. same with my dialler i will open it, have enough time to type a few numbers then it will close, no force close notification though. Also randomly my phone will freeze and i will either have to take out the battery or wait till the screen timer runs out and it goes black then turn the screen on, which usually doesn't work. The browser also sometimes forcecloses. I had some troubles a while ago with partitions which i never resolved i don't think but when i installed this rom (i have re-installed a few times) i tick repartition and it repartitions it supposably. I JUST WANT A FLAWLESS ROM WHERE I CAN MESSAGE, DOWNLOAD APPS, HAVE GOOD BATTERY, NO MASSIVE OR FREQUENT LAG AND NOT HAVE INTERNET ISSUES, GOOD RECEPTION AND NO RANDOM INTERNET ISSUES SUCH AS DATA CONNECTION NOT WORKING FOR NO REASON. Sorry for the long post I just wanted to thoroughly give information first go as it's urgent, driving me mad! I haven't had an almost flawless ROM apart from the ROM the phone come with.. which is now goone and 2.1 doesn't work with all apps
Try any custom rom blockbuster or hybrid rom much stable then that
Sent from my GT-I9000 using XDA App
I've tried darkys I just wantthe most stableand best battery rom is that what you'd recommend? Also does my problem seem like its flashed wrong? Caused by root or partition problem?
Did u use a pit file when u ticked repartition?
As for a rom, blockbuster is good, but I would recommend milkyS - you can flask this rom with Odin, full flashing instructions included with download. Very fast, very stable.
Sent from my Galaxy S using XDA Premium App
yeah i did man could that be why??
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?