Hi guys, first off:
thanks for that great forum which helped me getting started with flashing custom roms / getting root access etc...
When searching for my problem i found out that it is called the "Hello Hello bug".
So basically when anyone calls me and i am answering the phone the first 2 seconds or so my microphone doesnt seem to work (the person on the other side does not hear me).
I thought that this bug would be fixed in the new custom roms. i tried CM 10.1 Jellybro (http://forum.xda-developers.com/showthread.php?t=2015081) but even with this up-to-date rom i am getting the same bug.
As i couldnt find anything to fix this bug i was wondering if you guys have the same problem or if anyone knows how i can get around this issue?!
Best regards,
r3try
I have that problem. I just wait for a second and then say "hello". That seems to be working out pretty well.
Not sure on a legitimate fix though. I think it has to do with the images that the devs have to work on. Hopefully it'll be fixed in an upcoming new patch.
Known issue, will eventually be fixed.
AW: [Q] Hello Hello Bug
Try call delay patch from play store.
https://play.google.com/store/apps/details?id=cz.byteworks.cdp
Sent from my Nexus 4 using xda premium
scherfa said:
Try call delay patch from play store.
Click to expand...
Click to collapse
i already tried that before.. didnt change anything for me! (thanks for the tip though)
btw: that image verification is driving me crazy.. im trying to read what the image says for like 15 times now -.- (should those be any words, or are those just random letters? cant believe there is no better solution out there *sigh*)
so, the new update is coming soon (some of you might already have it) and i was wondering if you guys know if the new version fixes either the "hello hello bug" or the bug where you cant hear the caller at all on some calls?
Those bugs are really driving me crazy and i'm really wondering how its possible for a telephone to have so many bugs in the most basic functionality of all - TALKING TO PEOPLE!
any insights / suggestions?
r3try said:
so, the new update is coming soon (some of you might already have it) and i was wondering if you guys know if the new version fixes either the "hello hello bug" or the bug where you cant hear the caller at all on some calls?
Those bugs are really driving me crazy and i'm really wondering how its possible for a telephone to have so many bugs in the most basic functionality of all - TALKING TO PEOPLE!
any insights / suggestions?
Click to expand...
Click to collapse
For me the bug is fixed on 4.2.2.
El Daddy said:
For me the bug is fixed on 4.2.2.
Click to expand...
Click to collapse
niiiiiiice, now im really looking forward to the new version!
thx for the info
the version 4.2.2 doesnt resolve the hello hello bug for me...
do i have a chance on making it work by changing my kernel or the rom? i dont know what is the most likely cause for this.
I have exactly the same problem, no solution yet.
4.2.2 latest stable CM
same here.. problem still persists, allthough i feel like it happens fewer than before...
Hi, I have the same problem. Is there any way now to solve it? Did appear maybe any solution for that?
Nexus4 Rooted
Related
Hey guys,
I noticed something rather strange, when I wake the phone up while its locked, the homescreen appears for a split of a second then the lock screen comes on.
Its not annoying but im wondering why that happens ? does it happen to you as well ???
ZaZu90 said:
Hey guys,
I noticed something rather strange, when open the phone while its locked, the homescreen appears for a split second then the lock screen comes on.
Its not annoying but im wondering why that happens ? does it happen to you as well ???
Click to expand...
Click to collapse
I get it occassionaly, yeah. It's never bothered me though.
This is the kind of thing that HTC will hotfix, while we wait for proper ROM releases and fixes of larger scale issues
yeah i get this too, its actually kinda annoying -_-
But im sure it will be fixed soon in a rom update from HTC.
Thanks for the info guys, I thought i was the only one with that glitch
Anyone got any news when will they release a new patch ?? Is there a website I can follow where they announce such statements ??
On a sidenote, how can I check my ROM version ? Is it the 1.488 one ?? Whats the latest available ?
Hi Guys I have the T-mobile G2 running stock software-hasn't been rooted or anything. I've noticed that the phone will stop audiable notifiations and vibrate on then for unknown reason. It does that eventually every time after reboot, the only way to fix it is to reboot the phone or if I receive incoming call it will resume the notifying and the vibration on the notifications again. It is rather weird and If you guys know what might be causing it or how to fix it please let me know. I know there are more people out there having the same issue. I wonder why is noone complaining about it?
Thank you.
Have you tried to disable "Power Saver"? (Menu-Settings-Power Saver)
Sent from my HTC Vision using XDA App
AllWin said:
Have you tried to disable "Power Saver"? (Menu-Settings-Power Saver)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I do not have such an option on my phone-I have the T-mobile G2 not the Desire Z-maybe there is a difference there in the options menu...I don't run the HTC sense version....
Root your phone, flash some DZ ROM and then do what i said before
Now seriously. Sorry, that was my bad..
Does anyone think this is an issue worth looking into? If anyone has the same issue please advise if you have found a way to fix it. It does look like software issue to me just don't know what is causing it....
Come on guys, does anyone have the same issue? Any way to fix that without rooting and using a custom ROM?
Help is appreciated...
Pecata said:
Come on guys, does anyone have the same issue? Any way to fix that without rooting and using a custom ROM?
Help is appreciated...
Click to expand...
Click to collapse
This used to happen to me all the time... on a few different stock android devices.
Notifications would just stop working. NO sound. I would go into Handcent and do a "Test Notification" and there would be no sound.
Always happened after having the phone on for several hours. I just got in the habit of rebooting daily. Currently I'm on Cyanogen Mod and haven't noticed an issue recently.
But like I said it has happened to me on 4 android devices all running various versions of Android.. so I'm guessing it's an app combo that I have.
I'm on CM6 and this happens to me randomly too
Yep, mine doesn't vibrate on sms notifications. Vibrates for incoming calls ok though. I only noticed it a few days ago. Hmmmm,.... Using CM6.1
I see, I am also guessing it's software related just don't know what is causing it...
The strange part is that when I reboot the phone shortly after it will stop notifying me or vibrating on notifications and after I receive a call it will start working normally again-until the next reboot-it is weird...
HTC G2
Pecata said:
Does anyone think this is an issue worth looking into? If anyone has the same issue please advise if you have found a way to fix it. It does look like software issue to me just don't know what is causing it....
Click to expand...
Click to collapse
Hi there Everyone, I do feel that this is somewhat of an issue,
I have HTC G2 t-mobile running Cyangenmode 7-10 Rc
My issue of no sound notifications started after I updated the Rom
I was running 2.2.1 now it is 2.3.4.
I keep getting DSP manager error, and this will pop up when I make a phone call or if I have an in coming call. (and I hear some static noise) that part is not as annoying as the fact
Some times during the week (when I am at work and need the phone to be quiet) I will get actually get sound, and then on the weekend I don't
Not sure what is going on. with this I have been looking on line to find a solution I have tried a few but still no luck, Any input would be greatly appreciated.
Blessings from Moondaughter6
Anyone have any idea how to solve "delay in MIC" after answering? Delay is about 1 second. When I press Answer and say Hello, person on the other side didn't hear what I said, I have to say again... Some first calls I didn't know is it something with my phone or network, or caller...
Regards from Dubrovnik
I have the same problem...
Funnily but that seems to happen to me all the time but I didn't really register it until you posted it on here.
Maybe It's because I rarely use it to make voice calls but I always find myself having to say "Hello, Hello" as they never hear the first hello.
Guys, I'm happy now... I'm not alone
Dejo, hvala
Same problem here ? Do you think its hardware or software related ?
Same thing here.
I find myself waiting a second or two before saying hello or i get exactly as described.
Anyone knows who, MS or Samsung, and where would be best to ask about this problem ?
Noticed the same problem!
S1eepy said:
Anyone knows who, MS or Samsung, and where would be best to ask about this problem ?
Click to expand...
Click to collapse
Samsung. If it's not being reported for other phones, then it's likely not the OS itself.
same problem.
Now I wait 1 second before speak...
Same. Wife explained it to me a while back after I got pissed off at her for not talking after I answered. haha
I was surprised today as I answered the phone and said hello straight away and got a reply - I was actually heard.
I am not sure If this was due to upgrading to the newest rom - including the firmware.
I've noticed this as well (JK1 firmware)
Cool, that's good news Let's hope it'll be included in a subsequent official Zune-distributed release
This happened to me also, but since upgrading to the I8700XXKC1 XXKB2 firmware it seems to have been resolved. (It's also resolved the issue of the notification sounds occasionally 'breaking' - I haven't seen that mentioned anywahere else.
Thanks for the feedback. Sorry I didn't quite follow the upgrade procedure. Is it possible to flash the firmware without erasing all the user data?
Unfortunately not, but almost all data on the phone is cloud based or can by synced via zune anyway. You'll just need to connect to your accounts and reinstall all your apps again (which is the biggest pain about the process).
So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.
Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.
Hello all,
I have a question and if some one can help me i would be very grateful
I have the Samsung Note 3 SM-N9005, and i am using the Cyanogenmod 11 on it, but i am experiencing some sound statics that are very annoying in general. Basically when the phone uses the speakers the sound in most of the cases is awful with static distortion.
Does any one has any solution to this, or ideas how to fix it ? i tried the latest nightly builds (till 01.05.2014) and nothing helped even if in those builds it was written that they have fixed the sound static distortion.
Thanks allot for any help given!
tixoo said:
Hello all,
I have a question and if some one can help me i would be very grateful
I have the Samsung Note 3 SM-N9005, and i am using the Cyanogenmod 11 on it, but i am experiencing some sound statics that are very annoying in general. Basically when the phone uses the speakers the sound in most of the cases is awful with static distortion.
Does any one has any solution to this, or ideas how to fix it ? i tried the latest nightly builds (till 01.05.2014) and nothing helped even if in those builds it was written that they have fixed the sound static distortion.
Thanks allot for any help given!
Click to expand...
Click to collapse
I have tried many versions of cm11 and have always experienced this problem with the sound.. i think we will just have to wait for a fix
Sent from my SM-N9005
celderic said:
I have tried many versions of cm11 and have always experienced this problem with the sound.. i think we will just have to wait for a fix
Sent from my SM-N9005
Click to expand...
Click to collapse
Dang, i was hoping for a solution ... dony really want to go back to TW honestly, but this ia killing me from inside.
Do you think that a stable update will fix it only or a nightly can do the trick to?
Dang
It's like that in cm roms since 1800.
Try turning off all system sounds, sometimes it helps.
Sent from my N9005
tixoo said:
Dang, i was hoping for a solution ... dony really want to go back to TW honestly, but this ia killing me from inside.
Do you think that a stable update will fix it only or a nightly can do the trick to?
Dang
Click to expand...
Click to collapse
Well in this cas how should my phone ring if i have them all off?)
System sounds...
Unlock sound, keyboard sound, dialpad sound, screen touch sound,...
Sent from my N9005
Dejan Sathanas said:
System sounds...
Unlock sound, keyboard sound, dialpad sound, screen touch sound,...
Sent from my N9005
Click to expand...
Click to collapse
Will try, will see what happens
It works, for now at least, but it works!
I dont see what those sounds have to do with the speakers in general but ... bugs are bugs i guess.
Any ideas of when they will fix this? I actualy love these sounds
Ps: you can leave the click sounds, the problem is with the lock/unlick sound(at least for now i did not have problems, but will continue testing)
Don't ask me, because i don't know why, but it's like that and that's the way it is.
As i told you, this is a bug since forever. Don't think a proper fix is coming soon.
Sent from my N9005
Dejan Sathanas said:
Don't ask me, because i don't know why, but it's like that and that's the way it is.
As i told you, this is a bug since forever. Don't think a proper fix is coming soon.
Sent from my N9005
Click to expand...
Click to collapse
Ah well, at least its better now, thank you for the help, one more bug to fix and the rom is good to work as a daily driver
Cyanogenmod 11 sound fault temporary solution??
An alternative temporary solution is to download an equalizer app. Drop all the controls down to zero and then bring them back up one by one. I had a sound issue with just one app on my Samsung galaxy ace II so this might work on your note 3. Ran the equalizer, ran the app, no more screeching or buzzing. When equalizer off, app on its own reproduces sound problems. Several equalizer apps I tried seemed to do the trick. DSP allows you to disable and enable when required. This is my first post and as a noobie I read the terms and conditions first; but I apologize if I have still not followed protocol. Hope this is still relevant.
I had that issue too. Not really sure if it has a permanent fix; it kinda came and went away on its own.
Anyone else experiencing this issue? When I'm listening to music and I get sound notification from whatsapp for example, it becomes distorted for a good five seconds atleast (the music and the notification) and maybe even longer sometimes. I'm using the latest nightly and still experiencing this issue
Flash Temasek's unofficial CM build. He builds from official CM sources and then adds some useful features. A lot of problems in regular CM are fixed in his builds, including broken sound.