I've just updated my Galaxy Note to stock ICS (LPY) following the instructions at Update galaxy note official ics 4.0 (stock). It's working fine, but I've just noticed a FC when receiving a call while the phone is the car dock (landscape mode). Is anyone else having this problem? Any workarounds?
Thanks a lot!
mine is fine...i wiped...flashed...and wiped... havent seen the "bug" some have had... im stock...
same problem here. i'm gonna try "factory reset".
Related
I just flashed the ROM to stock XXJPU 2.2.1..
Everything's outstanding except the incoming call ringtone and vibration..
Whenever someone calls me up, the ringtone sounds for some miliseconds.. and then it's just gone... no vibration in silent mode.. no ringtone in general mode..
I never faced this problem before but facing this after I flashed to XXJPU..
Any solution?
Very strange, I haven't had this happen at all and I'm using JPU.
Ahh..
The message notification is working like a charm but the problem is with incoming calls only :S
Checked all the volumes, ringtones, nothing works. Even the vibration mode is not working.. Phone remains silent while someone calls me up.
wow...
maybe u have the bad firmware... so where can u download this firmware.... any links? and do i need the password on the zip file???
Both my girlfriend and myself have a similar problem, oddly enough we have different firmware and models. Call ringtones and message alerts rarely work. E-mail notifications and such are fine. I've got an 16 GB Australian GT-I9000 (Optus) running JPU. However my girlfriend has a 8 GB GT-I9000 (International) running the latest official (Kies) firmware, JPO.
We're both with different telecomm providers so I don't think it's a network related issue. I'm a little surprised to find that so few other people have the same problem. I'm a bit busy of late but I'll see what I can find out. If anyone else has any information please don't hesitate to share it.
I have exactly the same problem, since I upgraded to JPU. With my previous upgrades, I had no problem so it seems to be a JPU's bug. But, why only some of us are concerned ?
What could I do ? Any ideas ??
manu_katz said:
I have exactly the same problem, since I upgraded to JPU. With my previous upgrades, I had no problem so it seems to be a JPU's bug. But, why only some of us are concerned ?
What could I do ? Any ideas ??
Click to expand...
Click to collapse
I just "fixed" mine somehow by fiddling with settings. I probably shouldn't have done so as now I don't actually know what the problem was (so I can't make a real fix). However, I just tried reselecting my call ringtone, message ringtone, changed my volume up and down, turned silent on and then back off a couple times and enabled vibrate for all calls (not just on silent). Then the next time I got a SMS it worked. I don't know if it will stay working though.
Thanx for answering ! Me, I have no problem with SMS notification. Only calls ring. But, I will follow your note : play with volumes, mp3, sounds, notification modes, ...
I just notice that an icon appeared just a semi-second after a call arrives : that's the "Silent mode activated" icon (an HP with a slash on it !). But I'm not in silent mode !
I had this problem, so I re-flashed and only restored apps and not system data, everything is fine now.
Hey, that's fine, I've found the reason why my phone stopped to ring : an app not compatible with version 2.2.1 called NetQin Mobile Manager v3.2 ! I just uninstalled it and my phone found back his voice ! lol !
Hallo mij Galaxy stops during most of the calls after about 30 of 40 seconds. When I call again the problem doesn't appear again.
It has the latest Android 2.2. firmware. The problem occurs also with the 2.1 firmware.
Who knows the solutions of this irritating problem?
Thanks
Is anyone out there having problems with vibration notification?
Mine seems to not work anymore. I have the hong Kong rom.
I was trying to use smart vibrator and vibration notify and found out none of my vibration notifys work at all. and yes, I do have it turned on in sound settings .
- Frank
ChodTheWacko said:
Is anyone out there having problems with vibration notification?
Mine seems to not work anymore. I have the hong Kong rom.
I was trying to use smart vibrator and vibration notify and found out none of my vibration notifys work at all. and yes, I do have it turned on in sound settings .
- Frank
Click to expand...
Click to collapse
Did you figure this out? I'm having the same problem. My vibrate notification just stopped working.
ChodTheWacko said:
Is anyone out there having problems with vibration notification?
Mine seems to not work anymore. I have the hong Kong rom.
I was trying to use smart vibrator and vibration notify and found out none of my vibration notifys work at all. and yes, I do have it turned on in sound settings .
- Frank
Click to expand...
Click to collapse
I have a same problem here,
I am using Cassie's XtraLiteRom KL3 ThunderBolted! V4
Everything good but today I just notice that my vibration is not working anymore.
Please help!
I have the AT&T version and I'm having the same issue. After a factory reset the vibration for notifications works again but then eventually stops working again...
no vibration
Mine stopped working recently. Not sure how to fix it. Is it something I installed? It does not vibrate for incoming texts or phone calls.
Flashing a stock ROM fixed this for me. I've seen others say that fixing permissions or wiping dalvik will fix too.
Only time this happens to me is when flashing ROMs
I'm sure this makes no difference but when I flash a ROM, I leave those bottom settings under Sound as the defaults. Aka haptic on.
I'm running the stock AT&T ROM. Do I need to be rooted to wipe the dalvik cache? What does "fix the permissions" mean? THANX!
nettech_gt said:
I'm running the stock AT&T ROM. Do I need to be rooted to wipe the dalvik cache? What does "fix the permissions" mean? THANX!
Click to expand...
Click to collapse
That shouldn't happen running bone stock. Try a factory reset first if you have not done so already. Don't install any apps. Run the phone for a day. If your issue returns I would swap the phone out for a replacement.
The haptic motors in every Android device I've ever owned has done some weird thing or another. I stopped using it. Why blow the motor out early? Vibrate on silent for notifications I found to be sufficient. At first I was put off by changing my using habits but disabling haptic feedback has grown on me.
EDIT: I see you did a factory reset and it came back. I'd exchange for a different handset. Just me though. Someone here might have another solution
THANKS!!!!
;/
It's old topic, I know, but Im bumping it. Vibrations in external apps like facebook messenger or kakaotalk doesnt work for me, but for normal messages, phone calls etc it works, so I doubt its fault of phone. And in my Galaxy Ace before I had same issue, but it just stopped working after some update from devs of this apps i said. Though it would be strange that only few people has such problems. I think its something about settings or w/e, can anybody help here in this thread without saying 'factory reset or exchange phone' ?
Thanks <3
/stock ICS
If I make a call, or somebody calls me when Galaxy Note is in car mode (and being charged), the phone hangs with an error saying something like "...android.phone.com". This has caused me miss lots of phone calls during driving and now I cannot put my phone into car mode with this risk. This started to happen after I upgraded to ICS 4.0.3....is there any fix to this?
zamane said:
If I make a call, or somebody calls me when Galaxy Note is in car mode (and being charged), the phone hangs with an error saying something like "...android.phone.com". This has caused me miss lots of phone calls during driving and now I cannot put my phone into car mode with this risk. This started to happen after I upgraded to ICS 4.0.3....is there any fix to this?
Click to expand...
Click to collapse
any answer for that?.......i have the same issue and i didn't found anny solve...
Had similar problem in 4.03, resolved with 4.04.
Sent from my GT-N7000 using xda app-developers app
Hello. I am using Samsung Galaxy Note 9 (Exynos Variant) running Android 10. After updating to Android 10 I am facing a peculiar problem. Swipe Down for Notification not working randomly.
It's like when I changed the wallpaper or changing Theme from Galaxy Theme App it stops working sometimes.
Or even just a normal reboot will make it stop working.
Also when I optimised my device from device care it will stop working.
Now the only option I have to make it work is to reboot the device but there is no guarantee that after reboot it will work.
After updating my device to Android 10 I have done a full factory reset as well.
So anyone facing this kind of issue???
Also can anyone help me with a solution???
Thanks in Advance.
suvadeep. paul said:
Hello. I am using Samsung Galaxy Note 9 (Exynos Variant) running Android 10. After updating to Android 10 I am facing a peculiar problem. Swipe Down for Notification not working randomly.
It's like when I changed the wallpaper or changing Theme from Galaxy Theme App it stops working sometimes.
Or even just a normal reboot will make it stop working.
Also when I optimised my device from device care it will stop working.
Now the only option I have to make it work is to reboot the device but there is no guarantee that after reboot it will work.
After updating my device to Android 10 I have done a full factory reset as well.
So anyone facing this kind of issue???
Also can anyone help me with a solution???
Thanks in Advance.
Click to expand...
Click to collapse
Noticed this also. Not sure why it happens for me though. Note9 512GB N960U
I haven't seen this specific issue but I find that the Samsung gestures (the swipe from the bottom of the screen ones) sometimes just stop working in Android 10 / OneUI2.0
I noticed that also once or twice, after reboot back to normal.
I don't use any gestures for nav etc. Only swipe up and down ones. Not sure if this info makes any difference.
Will see if I do anything that triggers this bug.
Are you using GoodLock? TaskChanger, specifically?
Turn it off, then on again. This fixed it for me.
Sent from my SM-N960F using Tapatalk