For example if I send a hangout message, press home and get a reply, there's no sound some of the time. If hangout is the front app there is never any sound. Highly annoying.
My phone is rooted but with stock ROM. Is this the normal behaviour of Hangout?
Not having this issue on Cataclysm stock based ROM. Tested many times with several people with hangouts on and phone on as well as with screen off. Noise comes through. When did you first start noticing the issue?
Yesterday. The day after I got the phone. I have unlocked it and the reset it did didn't change anything.
I just did a small test and I have the exact same problem on my Nexus 7 (stock) and on my old phone (kitkat ROM on an HTC one s). None of them had the problem before the test when they were both running CM11 nightly. Seems it is a kitkat bug? Wonder what causes it. That's strange..
Just to be clear, if you are looking at hangout when a chat message or SMS comes in, you hear a sound?
Sent from my Nexus 7.
Only common denominator I can think of is Nova Launcher..
Sent from my Nexus 7
Related
Has anybody tried out ARHD and decided it wasn't for them because something wasn't functioning properly (camera, camcorder, maps, MMS, GPS, etc.)? This is my experience every time I try out a new ROM, and I have returned to stock again and again.
Getting curious about ARHD (particularly because it's so popular), but thought I'd save myself the trouble if other people have had this experience.
Is it as reliable for a daily driver as stock?
It's based on stock, so yes. I found no errors so far.
davebugyi said:
It's based on stock, so yes. I found no errors so far.
Click to expand...
Click to collapse
The only bugs I've found are the ones that are present in the Stock release i.e. the Browser not opening links properly and the Exchange sync time not staying put.
Hardware wise everything worked, I had a the issue with WiFi not staying off but that occurs with Stock as well and there's a fix for it now that seems to sort it.
Nothing so bad that i have gone back to stock
I have a few problems with the messaging app:
If someone sends me a phonenumber in a text, and i click it, it opens the phone app and should automatically enter the number so i can call it, but the it just opens the app without the number.
The messaging app sometimes opens very slowly (10-15 seconds after the icon is clicked)
Even with the right settings from my phone network provider, MMS is unable to download pictures.
Other problems:
Sometimes the phone is slow after it comes out of sleep (lockscreen in nonresponsive or lagging)
Very very slow boot of camera app (Not really sure if this was a problem in the stock version..
All of this is something i have chosen to live with because i love the rest of the ROM.. Im just hoping this is fixed in later releases
SecherFault said:
Nothing so bad that i have gone back to stock
I have a few problems with the messaging app:
If someone sends me a phonenumber in a text, and i click it, it opens the phone app and should automatically enter the number so i can call it, but the it just opens the app without the number.
The messaging app sometimes opens very slowly (10-15 seconds after the icon is clicked)
Even with the right settings from my phone network provider, MMS is unable to download pictures.
Other problems:
Sometimes the phone is slow after it comes out of sleep (lockscreen in nonresponsive or lagging)
Very very slow boot of camera app (Not really sure if this was a problem in the stock version..
All of this is something i have chosen to live with because i love the rest of the ROM.. Im just hoping this is fixed in later releases
Click to expand...
Click to collapse
Yikes! Yeah I'm not interested if MMS doesn't work. Have other people experienced this?
I'm giving ARHD an extensive try now that we are running ICS. can't say I have come across that issue with the MMS. In fact, the only issue I have had is with WiFi not staying off. At first I thought it was an issue with ARHD, but learned that we have the same problem stock. I'm loving the ROM. I would love to ditch Sense though!
Sent from my HTC Sensation 4G using xda premium
GoodbyeSky said:
Yikes! Yeah I'm not interested if MMS doesn't work. Have other people experienced this?
Click to expand...
Click to collapse
MMS worked fine for me. Maybe SecherFault should check their APN's (if they haven't already) as that's usually the cause of MMS not working.
Iv'e been using ARHD for a while. Pretty solid and fast. One thing I've realized is that my call volume. Whenever I'm in a call, the volume sounds crackly, like the gain is too high. I turn the volume almost all the way down. It's not my phone because I've used other ROMs and haven't had the same problem. Anyone know a fix?
I recently wiped and flashed both my and my fiance's phones. Both the exact same phone, and I used the exact same install method and rom. (CyanogenMod 9) They should both be the exact same... right?! Well having two issues which only work on my phone, not my fiance's.
ISSUE 1
So I am aware that the Samsung Galaxy S 4G has a known issue with sending long texts which popup with a triangle saying something like "cannot send message". In the past, we've split messages using Go SMS pro. I recently found an app called "BIG SMS" and it fixed my phone so now I can send loooong sms messages like normal and with any app! I installed it on my fiance's phone and her's shows the triangle, it goes away, then shows it was sent and received but nobody ever actually gets it?! What does that mean and why would it not work on her phone?
ISSUE 2
My fiance mentioned to me the other day when she turns down her audio using the phone's side rocker, it goes from low volume to mute and stops without going to vibrate. On my phone, I go from low volume, to vibrate, to mute... Where's that option on her phone?
For your first issue, you would have to install another modem. KG4 is the way to go for long messages. Here's a thread with modems that are compatible with the SGS4G. http://forum.xda-developers.com/showthread.php?t=1192436
For issue two, does your fiancee have a different phone than you?
Thanks for the quick reply! No idea how installing a new modem works but I'll definitely look into it. We both have the Samsung Galaxy S 4G, and I flashed the exact same rom using the same methods, and installed the same apps. ONLY difference between our phones is that we just got hers and mine I bought when they first came out.
Installing a new modem is as simple as flashing it through a recovery mode. That's very odd how her phone goes to silent by the volume buttons. I have the same phone and cannot do that and neither can you.
Does she have vibrate off or intensity set all the way low? Maybe.
cm-9-20130227-UNOFFICIAL-galaxys4gmtd.zip
That is the mod I installed for both of us. I was used to the old android so now that we're on ICS, I'm not as familiar so I have yet to even find the intensity option. Under sound, we have the vibrate and ring turned on if that helps... That's about the only option I even see for vibrate without it being inside an app.
I'm having this issue where the phone doesn't react properly to an incoming call (stock ROM, unrooted).
The phone rings, but the dialer screen with the controls to answer the call does not come up. It doesn't help if the screen is already on, I'm just staring at my home screen while it rings. There's also no call icon in the notification bar. When the caller hangs up, I immediately get a missed call notification.
Rebooting the phone solves the problem for a while, but then it comes back. I tried reverting to the stock dialer with no luck. I'm thinking of reverting to the stock launcher as well, but I'm not sure it has anything to do with it. Other than that I'm running out of ideas.
I've searched the web and it looks like people are experiencing all sorts of variations on this problem, but not the exact same thing, and in any case I haven't seen anyone post a tested workaround.
Has anyone encountered something like this and maybe knows of a solution?
Did you try clearing the data of the phone app in settings > apps?
If not, try that
Sent from my Nexus 5 using Tapatalk
I have had a GS2, GNex, N4 and now a N5 and started having this issue since the nexus 4, can’t remember exactly when it started but I think it was around android 4.3 because I remember hoping that an update to the OS would fix this and when 4.4 came the issue still happened.
The issue is that I use the back button to exit out of apps completely but sometimes and I believe that it is completely random, when I open let’s say whatsapp and I press back to exit out of it, it sometimes opens another app that was on my recent apps list and then exits out of it by itself, this happens even if whatsapp was the only app open, is not like I went from a random app to whatsapp and I was backing out of whatsapp to these other app and this other app just blinks and closes out.
Anybody has this issue?
Here is a video showing the issue: http://www.youtube.com/watch?v=mU0n0j9LUCw
I get this often. No fix that I'm aware of :/.
moisesgl said:
I have had a GS2, GNex, N4 and now a N5 and started having this issue since the nexus 4, can’t remember exactly when it started but I think it was around android 4.3 because I remember hoping that an update to the OS would fix this and when 4.4 came the issue still happened.
The issue is that I use the back button to exit out of apps completely but sometimes and I believe that it is completely random, when I open let’s say whatsapp and I press back to exit out of it, it sometimes opens another app that was on my recent apps list and then exits out of it by itself, this happens even if whatsapp was the only app open, is not like I went from a random app to whatsapp and I was backing out of whatsapp to these other app and this other app just blinks and closes out.
Anybody has this issue?
Here is a video showing the issue: http://www.youtube.com/watch?v=mU0n0j9LUCw
Click to expand...
Click to collapse
frigidazzi said:
I get this often. No fix that I'm aware of :/.
Click to expand...
Click to collapse
Is this an android issue? or could it be our config? can anyone say they do not experience this issue?
I don't recall having this on my nexus 4, and I don't recall having this on my nexus 7. I'll have to pay more attention on my nexus 7 and update of I see it.
Yes, most probably it's a KitKat issue. I'm facing this problem as well and there was a big thread about this issue and there were many people with this problem :cyclops:
I face this problem on stock rom as well as on a custom rom..
vin4yak said:
Yes, most probably it's a KitKat issue. I'm facing this problem as well and there was a big thread about this issue and there were many people with this problem :cyclops:
I face this problem on stock rom as well as on a custom rom..
Click to expand...
Click to collapse
oops, must have missed it. thanks for the info
I'm having the exact same issue on my Nexus 5. I happened on my Nexus 4 as well, so definitely an Android issue.
And you are right about it starting when Android 4.3 was released. I have been waiting patiently for a fix for a while now..
Sent from my Nexus 5 using XDA Free mobile app
I can't believe this problem still exists on Android 5.0!
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
idiopathic said:
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
Click to expand...
Click to collapse
I don't have this issue. maybe you had a bad install
I have the same problem on my N4, I installed the factory image two days ago, but just today I have this problem. When I turn on the screen, the call appears as a notification on the lockscreen, and I have to double tap it to answer it
I have the same issue. I installed the OTA. I had security certificates before which forced me to use a pin lock lock screen (My exchange account requires it). I installed a MOD to remove it so I thought that might be what was causing my problem. I removed the MOD by disabling the exchange APP but it didn't resolve it.
I have the same issue on about 50% of my incoming calls
Sent from my Nexus 7 using Tapatalk
I have this same issue. I even had it on the developers version. I also thought when you got text messages, emails, and other messages. You would get a black and white notification if you moved you hand over the phone. That doesn't work for me either. i have a Nexus 5 Build LRX21O. I installed it with the Nexus Root Toolkit.
I have the same issue on my Nexus 4 side loaded with Android 5.0 Lollipop. The screen won't turn on for any interactive incoming notifications like Phone Calls, Alarm calls..
It's an annoyance as you need to double tap the notification to answer, and the only way to go to speaker phone is to answer -> unlock -> Tap speaker
I checked around and my colleagues who use a Nexus 5 don't have this issue (OTA or Sideloaded). So I think this issue could be with a Nexus 4 build only (selectively that too). I am the only one who've posted this on reddit too.
/r/nexus4/comments/2mjoz7/screen_wont_turn_on_for_incoming_phone_calls/
I can also confirm this bug ... on Nexus 5 with LRX21O.
Same problem!
I have the same problem on my G3, but i didn't even installed Lollipop yet.
Same on my Nexus 5 with LRX21O.
I am having the same problem with my nexus 4, after a clean flash..
I unlocked the bootloader which triggered a full factory-reset and this issue went away on my Nexus 4 which is smoother than before.
I wanted to download a full ROM (since the issue was with OTA update), so was doing a bootloader unlock for the same. But i didn't even have to load up the full ROM as the issue went away.. :laugh:
jsgraphicart said:
I don't have this issue. maybe you had a bad install
Click to expand...
Click to collapse
after i updating my nexus 5 to android 5 during call screen doesn't auto turn off when i covered the screen sensor?
I noticed this too,not on all incoming calls, but on 1 out of 3 the screen stays black.
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
gnanaswaroop said:
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
Click to expand...
Click to collapse
I made a clean install (wiped everything) and the problem appeared.
I don't think it is a matter of dirty flash..
I also have this problem after installing from ZIP stock ROM (with format all things before).
Then I took a Google image and install it with ADB.
Now I don't have this problem.
screen doesn't turn off
My screen didn't turn off during phone calls with the developer preview and still doesn't with the official factory image from Google.
This is coming from a full flash via fastboot... Don't think this is a dirty flash issue.
Very annoying... No clue how this could be released.
It appears our problems are not related but I was able to fix mine
Nexus 5
OTA Flash
screen is blank for incoming calls and alarms, not periodic
I don't know which app specifically that was causing the problem but the problem went away after I uninstalled a bunch of apps. I am most suspect of a screen brightness app I was using to make the screen more dim than the default setting.