hey,
I have been using the Vanir ROM (http://forum.xda-developers.com/showthread.php?t=2609285). First I need to say that i runs very good and smoothly.
But I think I have found a bug because after some time (I don't know the exact time. Sometimes after hours, sometimes after a reboot) a melody starts playing on my phone. It isn't very loud an I hardly notice it when I am outside. I tried muting all sounds and the melody is uneffected. It seems like the melody is set to one specific volume. The melody just stops when I open the notifications bar or if i receive a phone call.
I did a factory reset and wiped all of my data when i installed the Vanir ROM.
Any suggestions? Have you had that problem too or am I the only one?
This is very annoying because I always keep my phone next to me even at night and the melody is loud enough to wake me up.
I never ever heard of such a behavior? I used Vanir long enough that I would've noticed a melody at least at night as I have not the best sleep.
I only could think of an app that is malware infected or something like that.
Did you try to wipe system as well? And do try to not change anything at all and see if it happens again and try to grab a logcat.
Sent from my LG-P880 using XDA Premium 4 mobile app
I had the melody again and when i looked at my phone I got a new SMS. I think that caused the melody althought my sound was turned off. But still I have a bug that the melody does not stop. It is an infinite loop that just stops if I open the notification bar or if i get a phone call.
I wiped my system as well when i installed vanir. I think I will wipe my system and do a factory reset and download the ROM again.
funboy0_0 said:
I had the melody again and when i looked at my phone I got a new SMS. I think that caused the melody althought my sound was turned off. But still I have a bug that the melody does not stop. It is an infinite loop that just stops if I open the notification bar or if i get a phone call.
I wiped my system as well when i installed vanir. I think I will wipe my system and do a factory reset and download the ROM again.
Click to expand...
Click to collapse
Ekk.. That makes me chill... It seems like a Ghost movie.
Sent from my LG-P880 using XDA Premium 4 mobile app
Related
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
My phone stopped vibrating on notifications and incoming calls for some reason. So did my brothers at the same time. It'll still vibrates on screen unlock and haptic feedback. I have my e-mail set to vibrate only, sometime it'll vibrate, but more often than not, it wont. But never for notifications or calls. And yes i checked all the settings i could. (That i know of)
It first started when we switched to aosp mod from cm 6.1. So I tried flashing back to cm6.1(jaybob version) hoping it would fix, but it didn't. Yes, I did all the full wipes and everything. I really don't wanna RUU to see if its the phone or just the roms. I mean, it happened to my brothers phone at the same time, that can't just be coincidence.
Has anyone else seen this? or know what iI can try before I RUU?
i downloaded an app called sound manager. its free on the market. in there i clicked menu, vibrate settings. i enabled all the vibrate settings. tested it, then deleted the app. that reenabled my vibrations for messages and calls.
MrDowntown12 said:
My phone stopped vibrating on notifications and incoming calls for some reason. So did my brothers at the same time. It'll still vibrates on screen unlock and haptic feedback. I have my e-mail set to vibrate only, sometime it'll vibrate, but more often than not, it wont. But never for notifications or calls. And yes i checked all the settings i could. (That i know of)
It first started when we switched to aosp mod from cm 6.1. So I tried flashing back to cm6.1(jaybob version) hoping it would fix, but it didn't. Yes, I did all the full wipes and everything. I really don't wanna RUU to see if its the phone or just the roms. I mean, it happened to my brothers phone at the same time, that can't just be coincidence.
Has anyone else seen this? or know what iI can try before I RUU?
Click to expand...
Click to collapse
on aospMOD go into sound settings and for vibrate make sure you have it set to something other than never
Tried both of those suggestions and neither worked. Vibrate was set to always already.
I don't understand cause haptic feedback works but the actual vibrating will not.
Sent from my HERO200 using XDA App
This is apparently a common enough thing from what I've seen on line, but every solution I find involves the person having used a profile switcher or their calender to signify being unavailable. I do not use either type of program. I almost never silence my phone. (in the movie theater or similar, yes, but otherwise never) Does anyone have any idea what it could be? It;s only been happening since the OTA update to .217 ICS. It's getting thoroughly aggravating missing calls and texts, as I'm sure you can imagine... Thank you to anyone with ideas/suggestions.
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Could it be a Smart Actions setting?
Settings are all fine yet it does randomly put itself on silent mode no vibration and you have to turn it back to vibration via settings volume rocker just puts it back on silent....
Sent from my DROID4 using xda app-developers app
The Magician Type 0 said:
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
The Kraken! said:
Could it be a Smart Actions setting?
Click to expand...
Click to collapse
If it keeps happening tomorrow, I will do a full factory reset. Hoping I won't have to though. It's a pain in the rear to restore everything... It isn't a smart action thing because I have that app frozen, good thought though. Thank you all for the responses.
I tried a fr from recovery menu never froze apps nor rooted this d4 didn't help...
Sent from my DROID4 using xda app-developers app
Update
I've found that it is only doing it with phone calls now. I cannot find a setting in the phone app or the system settings that is set to mute, but it keeps happening. Also, after using the lock screen to unmute it, I have to turn up the volume manually. The lock screen thing only bumps it up to the minimum volume level... Anything else come to mind before i do a full FR? I'd really rather avoid it if I can... Thanks again.
Now I've got one worse. Did a FR, no go. Tried to update to Eclipse, and messed it up. Had to .sbf back to factory. EVEN AFTER the .sbf, still having the same issue with it muting while recieving a call.... (i.e. goes on vibrate instead of ringing....) Any ideas ANYONE???!!?!?!?
Honestly, this sounds like a hardware issue to me. If I understand correctly, it sounds like the phone keeps going to silent (or vibrate after ICS)?
My guess after all your software troubleshooting is that your volume down key is either physically or electronically damaged, and periodically decreases itself. You might want to try remapping the volume button or something to see if that solves the problem. Of course, after that you don't have any volume buttons, which stink.
Aside, the physical buttons (power, volume) on the D4 really stink. They are very mushy and almost flush with the case, poor design if you ask me.
That thought crossed my mind also, but it only happens on an incoming call, and I can adjust the volume up and down in every app. If I don't receive a call all day, there is no problem, texts & emails work fine. I've even had a friend sit with me and text me (sound worked) then call me (muted as it received the call) and all it did was vibrate, no ringtone. I have who is it and thought it might be that, but un-installed it and no change... I'm totally out of ideas...
Thank you for the ideas, unfortunately nothing has worked so far. Any further ideas will be much appreciated. Thanks again.
Finally figured it out. Apparently it had to do with some stetting that Who Is It made. I had it set to announce the caller, which apparently doesn't work now. When I un-installed who is it nothing changed, so I re-installed it and on a whim disabled the announce feature, and it's been ringing fine since. I believe it was some sort of setting because after disabling the announcement, I un-installed who is it again, and the phone would ring without a problem. No Idea what setting it was. Thanks to veryone for the help.
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.
I'm no longer getting vibrations on my wrist with my Gear Live. I haven't touched anything, but they just stopped. The motor does work however, I've tested it using the Phone Finder app. I've tried resetting the device, restarting the device, and making sure that it's not on mute. I can't seem to find settings for this anywhere; could someone help me out?
Edit: I love how as soon as I post this, vibration starts working again..
Could it be that certain apps aren't getting the thing to vibrate, but others are? Anyone else getting vibration notifications with Textra?
I swear vibration didn't work every time. It's so faint though that even when it does, I don't notice it
Sent from my GT-I9505 using XDA Premium 4 mobile app
DrawnToLife said:
I'm no longer getting vibrations on my wrist with my Gear Live. I haven't touched anything, but they just stopped. The motor does work however, I've tested it using the Phone Finder app. I've tried resetting the device, restarting the device, and making sure that it's not on mute. I can't seem to find settings for this anywhere; could someone help me out?
Edit: I love how as soon as I post this, vibration starts working again..
Could it be that certain apps aren't getting the thing to vibrate, but others are? Anyone else getting vibration notifications with Textra?
Click to expand...
Click to collapse
Do you get Textra to work without. Contact + ?
Watch not vibrating for text messages
I noticed my Gear Live wasn't vibrating for text messages. It seemed random whether or not it vibrated for text messages. It vibrated normally for all other notifications. I have now discovered (and I believe and hope it's a software issue) that my watch will vibrate every time for incoming texts if and only if my phone is set to silent or ring mode. If the phone is set to vibrate, my watch will not vibrate for incoming texts. My Phone is a Samsung Galaxy S4 on the Verizon network running Android 4.4.2. I have tried rebooting, powering down andback on, and even a factory reset all resulting in no change of behavior. Is this similar to what you were experiencing? Anyone else experiencing this?
Text message vibration not working
I also noticed I'm not getting a vibration for text messages. Not sure why, I've had the watch for a week now and this just started a day or so ago. I've also restarted and reset to factory settings with no luck. If anyone knows of the issue, please post. Thanks!
UPDATE
MikeyFlo727 said:
I also noticed I'm not getting a vibration for text messages. Not sure why, I've had the watch for a week now and this just started a day or so ago. I've also restarted and reset to factory settings with no luck. If anyone knows of the issue, please post. Thanks!
Click to expand...
Click to collapse
Not sure if it's a permanent fix or not, but I actually shut my phone down completely (Samsung GS4) and turned it back on. I did a couple test text messages and the watch is picking up the messages and vibrating again. Again, this could just be a band-aid but it did seem to work.