I just finished running a backup and installing the Bali Kernel. The back up went good as well as installing the Bali Kernel. So all is running fine except for one small thing. I had a missed call just before running my back up. For some reason every time I reboot my phone, I keep getting a missed call notification. I clear it each time. But it just comes back on reboot. How can I get rid of this for good?
I had a problem like that except it was with both a missed call and a text notification. I deleted the history on both and they went away. If it persists beyond that, maybe you have to clear the cache and re-flash or something, but I wouldn't know.
Related
I have Galaxy S with Android 2.3.4 JVR and it works like a charm - with this one exception: sometimes (too often) phone, contacts and messages (sms) keep closing. This happens usually within a second or two after opening up them. There's no force close message, it just returns to the home screen without any warning. If I reopen it, it usually does the same a couple of times, but eventually I get it to open.
At first I thought this must be a memory issue. However, I have Autokiller installed (my phone is rooted) and I have usually >100M free memory. Then I thought it must be Autokiller killing the dialer, contacts or messages apps. BUT: this happened also before I had Autokiller installed, so it can't be that either. The strangest thing is that I tried installing GO SMS Pro and GO Contacts + Dialer, and even they do the same thing occasionally (close immediately after I open them), so it isn't a problem with apps either.
I am bedazzled here, could somebody please help me? This starts to get really annoying, since the dialer, contacts and messages are the feature you normally use most in your phone!
I have the exact same problem! Somebody, please help
the phone app and etc. seem to be corrupt or something
try reflashing.If you keep getting the problem then revert back to your previous rom =/
Is there any way to try to replace only the phone etc. apps without flashing the whole rom?
from my experience no but you can try replacing phone.apk sms.apk etc with the previous rom's apps
The funny thing is that I have a stock 2.3.4 JVR, so it should be stable.
Plus, did I mention that this happens only sometimes? Sometimes they work ok. But this happens often enough to be annoying. You know, when you would have to make a quick phone call you have to open the phone app like 3-4 times, only then you're able to make it. I wondered if the the problem could still be in the dialer, contacts and messaging apps even if the problem occurred only sometimes?
In addition, the calendar app has done this a couple of times. Could it be that there's a conflicting app that's causing this? If so, do you have any suggestion what it would be?
Autokiller made my phone do some really funny stuff. After installing it i was having random reboots and apps crashing so i uninstalled and problem solved. You said it was happening before you installed it though so im just guessing that you need to either wipe cache and dalvik then reboot or do a full wipe and reinstall of your rom. When you do the full wipe go into mounts and storage and wipe system too
Hi and thanks for your comment. What are the effects of wiping the cache and the dalvik cache? Do I lose important data? Or can I do it safely? Sorry, I'm a bit of a n00b with android. I suppose you wipe the cache in download mode, right?
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Whitest said:
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
Click to expand...
Click to collapse
earthman5678 said:
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Click to expand...
Click to collapse
Okay, that sounds interesting - though I am not sure wheter a widget could cause this...
I am still running JVU but now with Galaxian Kernel instead of Chainfires root Kernel - flashed with SGS Kernel Flasher and still got root - and it runs very stable and fast 'till now. No more closing of phone, contacts and messages so far -.- since 2 days.
I'll tell you when it happens again, but so far it seemed to be a kernel issue for me...
I've been having the same issues with my Samsung SideKick 4G. messages would keep closing as I was typing them, I would lag and the key I pressed would "press again" like 15 more times, sometimes I just couldn't open a conversation, other times I couldnt answer phone calls cause the UI lagged.
That was all on stock firmware, and I got fed up with it so I tried to flash a custom ROM on it, and before I did that I had it OC'd to 1.2GHz which was actually pretty great. Needless to say, I screwed up on flashing the ROM and now I'm looking for firmware to odin back to stock. =\
Seems to be somewhat common but no fix to be found...
Using CM7.1
Was working perfectly for a month.
Seemed to happen out of no where, no new apps installed or settings changed. The phone will vibrate for incoming calls, haptic, everything except SMS.
Using GoSMS but it does the same with the stock messanging app. Vibration is turned on in all the system and messanging settings. In fact, when I test settings in GoSMS it reports "vibration on".
Tried clearing the dalvik cache and tried installing this app but it won't show anywhere in the app drawer and I can't find it anywhere on the phone despite the market saying its installed. Unfortunate becasue it seems this app was designed for this very issue with desire/insprire.
Anyone have a fix for this or a method I could get the above app to install properly?
Thanks.
edit.....It's looking like an app issue......
never mind on the rom repair part....sorry
mods can delete....g
Gregsarg was actually probably right the first time. It doesn't seem to be an APP issue (as all MMS apps have the same lack of vibrate), but a broader issue.
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
I also tried the GoodVibrations.apk and it only shows in airdroid, mybackup, and managing all apps... It doesn't even have the 'open' command on the market menu after installing it >.>
Wulamoc said:
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
Click to expand...
Click to collapse
Thanks. Unfortunately I didn't see this suggestion before it was edited out. What exactly is meant by install CM7 on top of itself? Through clockwork I presume?
Yeah, just flash the SAME rom again (after backing up AND without wiping anything), and your settings should stay in place.
There is also a setting in the stock CM sms app that controls vibration, which is turned off by default.
Yeah vibrate in the stock SMS program is on. While I haven't gotten around to reflashing just yet I have noticed a few other things that lead me to believe its a ROM issue. Sometimes when I put the phone on silent it turns off all system vibrations even after coming off silent. I have to go back in and turn vibration back on. This is intermittent. Also, out of the blue the phone started vibrating during calls, come to find out "vibrate every 45 seconds during outgoing calls" was magically turned on.
It WILL vibrate when an SMS arrives if I'm on a call. Swell.
Flashed the new 7.2 nightly and the problem still exists. Everything remained intact after the flash so I figure I'll just do a full wipe/factory reset and flash the new nightly again and start over. Hopefully whatever caused this won't carry over with titanium restoring apps.
Do the full wipe, install the rom... then get a friend to send you text messages BEFORE you restore from Titanium, and then after....
Easy to isolate if you're carrying the issue from ROM to ROM.
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now..
*signed
mrrick said:
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now
Click to expand...
Click to collapse
That did it thanks! Saved me from having to do a full wipe. Phone is back to vibrating with SMS and I can change the vibration pattern. Nice.
Cool, glad it worked for you. I really wish I knew what happened though, it's kind of bugging me.
Meh, technology..
*signed
Well I'll add this... Out of curiosity I removed the vibrate tools app and everything is still operating as designed. So whatever that app turned on has stuck.
So I've had a recurring issue. Seems to be happening with any and all JB Sense ROMs really.
After fresh installing a ROM my phone would be working perfectly fine. Then some time after that, any time I receive a call the phone will lock up after I choose to pick up or right after I click send if I'm dialing out. No matter what, I will have not be able to hear anything. No dial tone, no voicemail, no voice on the end of the line. Sometimes a cache/dalvik wipe will fix this, most times it doesn't.
Another problem I've been having is that sometimes volume just stops working completely. No notification sounds, no ringtones, no key presses. Again, sometimes a cache wipe will fix this. Most times it doesn't. Usually these two problems come hand in hand.
EDIT: When I try to search something by voice on Google Now/Search, that also fails. So Mic seems to be an issue as well. But only when everything else is messed up.
I've posted this question on several ROM threads but no help so far. Any help with these problems would be greatly appreciated.
The specs: Rooted stock ICS on SCH-I535 (Verizon). So, I was experiencing the copy-paste crash described here, and used this solution to solve it. Ever since that fix, the phone process crashes when making a call. Here's what happens.
1. Open stock dialer, make call. Call connects, but screen is black.
2. Message that com.android.phone has stopped comes up. I click "ok."
3. Icon in menubar disappears and reappears. When pulling down the menubar, the call info is there. Selecting the call (via the green phone icon) brings me back to the black screen, and the stopped message reappears. I can end the call using the controls there, though.
4. Bringing up the Phone app while on the call brings me back to the stock dialer screen, but hitting keypad buttons there doesn't affect the call that I'm on. (i.e., if I'm in an automated system call, there are no keytones received by that system.)
5. When call is ended, it doesn't show up in my Recent Calls list.
I tried installing Dialer One, and get the same results.
Should I just wiped the Dalvik cache again in CWM and see what happens? Other ideas?
I was going to finally upgrade to JB and root (while we're at it, does OTA rootkeeper work here?) anyways, but don't really have time before I'm about to travel again. Any bandaids to fix this in the meantime would be great. Thanks in advance.
How did you fix this???
Were you abke to fix this??
ferkis said:
Were you abke to fix this??
Click to expand...
Click to collapse
Yeah, but I had to do a factory reset and re-root, then use Titanium to restore my backed-up apps.
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.