I've been using the nightly CM10.1 builds for a while now and it has always worked but lately when I tried to call someone I didn't hear the ringing before the call goes through and I can't hear them talking either but the speaker plays music and videos fine and I want to know how to fix this so I can call people normally again.
I have tried megawiping and reflashing, also going back to stock and starting again and other various methods like trying without gapps but I can't seem to get it to work and I really need it to cause its the only phone I can currently use but I found it was weird because this only occurs to my phone when running CM10.1 but calling works normally on stock and CM9.
LittleDoggy said:
I've been using the nightly CM10.1 builds for a while now and it has always worked but lately when I tried to call someone I didn't hear the ringing before the call goes through and I can't hear them talking either but the speaker plays music and videos fine and I want to know how to fix this so I can call people normally again.
I have tried megawiping and reflashing, also going back to stock and starting again and other various methods like trying without gapps but I can't seem to get it to work and I really need it to cause its the only phone I can currently use but I found it was weird because this only occurs to my phone when running CM10.1 but calling works normally on stock and CM9.
Click to expand...
Click to collapse
Could be your modem, try flashing a new one in CMW!
squ89r97 said:
Could be your modem, try flashing a new one in CMW!
Click to expand...
Click to collapse
I tried that and unfortunately that doesn't improve anything.
LittleDoggy said:
I tried that and unfortunately that doesn't improve anything.
Click to expand...
Click to collapse
Hmmmm, restore to your earlier backup, or try posting the question in the CM10.1 Q&A thread.
squ89r97 said:
Hmmmm, restore to your earlier backup, or try posting the question in the CM10.1 Q&A thread.
Click to expand...
Click to collapse
I tried that as well and if you mean the thread on xda then I have posted my problem in the discussion thread and I was planning on asking on the CM forums about this problem.
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
qtwrk said:
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The weird thing was I could get the phone/dialer working but it wouldn't work if I reboot my phone or change any of the settings like turning off animations.
qtwrk said:
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
squ89r97 said:
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
Click to expand...
Click to collapse
This seems to fix my issue for the time being but i'm still unsure if it is a permanent solution but thanks for helping
squ89r97 said:
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
Click to expand...
Click to collapse
i flashed stock 4.0.4 , stock 4.1.2 , CM10, CM 10.1, every ROM i can think of ...not good at all
qtwrk said:
i flashed stock 4.0.4 , stock 4.1.2 , CM10, CM 10.1, every ROM i can think of ...not good at all
Click to expand...
Click to collapse
Reset counter, flash stock, service center it is!
Sent from my GT-I9300 using xda app-developers app
squ89r97 said:
Reset counter, flash stock, service center it is!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
really strange it is.
as Viber works , so i consider it not as a hardware problem but call just doesn't have any sound !!! nor otherside can hear me ...
maybe replace motherboard will fix it ...
cannot hear when calling
Anyone have the solution yet?
it just happened to me to with AOKP (the last version - JB-MR1 Milestone 1)
Everything works fine, in a middle of a call the phone restarted and now there is no sound
Edit:
After a few full wipes and refreshing all is working good now.
Possible solution
Check my post here
Thanks but I already solved it...
Sent from my GT-I9300 using Tapatalk 2
No sound while calling
itaysp said:
Thanks but I already solved it...
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Hey, can you please tell how were you able to solve it? I'm facing the same problem since yesterday.
Related
*EDIT So many are having the FC issues, I am pulling it for now.
Sorry I guess 3 phones tested was not enough.
Will try to work out the kinks and get it back up soon.
I didn't do anything here except include Fennys new Phone APK and Qwerty KB fix. All the Kernel work is Fenny.
Thanks to Vlara and Howtomen for Putting the rom together with Fennys new Kernel which inclues the HW button fix.
Thanks also to Vlara for Deodexing.
The screen wake issue has yet to be resolved.
Other than that everything seems to be working fine.
All of Samsungs Bloatware is still there, including TouchWiz.
To adjust the Keyboard to the QWERTY android version from the QWERTZ Samsung Version, goto Language and Input, select Default, then English (US) Android Keyboard.
There is an issue with the kernel right now where you have to manually hash your restores, or they will not work.
Thanks again to FennyFatal, Vlara, and Howtomen!
URL REMOVED FOR NOW
Could use a mirror or two if anyone is interested! Please!
Updates will go here.
First!
(10 char)
Wrong section but ok lol
It has begun!!!!! ICS ROMs are coming!!!
Sent from my SAMSUNG-SGH-I777 using Tapatalk
howtomen said:
Wrong section but ok lol
Click to expand...
Click to collapse
Didn't realize ported meant Hellraised and not based, oops.
Nice, wonder how many would prefer this over CM9/AOKP since TW is rather hated.
howtomen said:
Wrong section but ok lol
Click to expand...
Click to collapse
Still considered port since nothing major has changed other than kernel, Red said it himself.
LiLChris06 said:
Still considered port since nothing major has changed other than kernel, Red said it himself.
Click to expand...
Click to collapse
I knew it! Either way, just thought people might want a taste of stock, anyone trying it let me know if it works okay for you. Worked fine for me.
Does this have the flashing screen issue or USB issue?
Sent from my GT-I9100
Andrew149 said:
Does this have the flashing screen issue or USB issue?
Sent from my GT-I9100
Click to expand...
Click to collapse
Yea as it says in the OP, the Screen Wake issue has not yet been resolved. Fenny and Entropy are working on it though. Pretty sure USB Mounting is still borked as well.
Hoorah
Sent from my GT-I9100 using Tapatalk
Also is this xxlpq. In other words the real official update?
Sent from my GT-I9100 using Tapatalk
I can't get it to boot. After flashing, reboot goes back into recovery.
Can someone post this kernel please?
Sent from my SGH-I777 using Tapatalk
Ran into a bug. When booted the phone and messaging apps keep force closing
Sent from my GT-I9100 using Tapatalk
stone_ship said:
I can't get it to boot. After flashing, reboot goes back into recovery.
Click to expand...
Click to collapse
me too
Force Close
Unable to use this ROM, set up fc's on Phone and Messaging constantly making set up impossible.
Skipping set up and going straight to the phone didnt help either. Any action (open an app, settings etc) is receive with "Phone has stopped responding" or "TWLauncher has stopped responding".
Can not hold a cell or wifi signal.
Flashed twice, same results each time.
Can we get a new phone.apk?
I can't get pass the "Galaxy SII" boot screen... :-(
How do you extract the kernel? I think its just the flash image and z image right?
Sent from my GT-I9100 using Tapatalk
so this is the same thing that's in aokp thread? heh...
I recently bought an international GT-I9300 Galaxy s3. I am facing few problems. I get a 3-4 seconds lag when I open dialer contacts and messaging app but once i have opened them it seems like they stay in memory for some time and open instantly but after some time i get this horrible lag again. Is my phone normal? I searched the forums and some people are facing this while others not. Secondly whenever I charge my s3 through the AC adaptor, galaxy s3 shows as charging (USB). Then i unplug and plug again after few tries it shows charging (AC). Is my phone faulty or is this a software bugs? Any fixes to these problems? I am on everything stock and unrooted JB 4.1.1 I9300XXDLID. Thanks
Hello, first of all, did you buy it brand new? First, I trying turning of s voice as it is know to cause lags. Then I can developer options change the windows a d transition animation scale to 0.5. See if it gets better, it could just be that there are some bugs! I
Sent from my GT-I9300 using xda app-developers app
Yes brand new with official damsung warranty. I have changes the animations and transition to 0.5 and disabled s voice.. Still the lag is present. Any solution? Should I send it to Samsung?
Are there any other lags beside the dialer and the messaging app?
Sent from my GT-I9300 using xda app-developers app
saaj2000 said:
Are there any other lags beside the dialer and the messaging app?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
None. The lag is present only on dialer contacts and sometimes messaging.
Ok, I think that it's just a big with the jelly bean... It should be fixed soon!
Sent from my GT-I9300 using xda app-developers app
saaj2000 said:
Ok, I think that it's just a big with the jelly bean... It should be fixed soon!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I hope so. Thanks for your help
Charging problem fixed. Both the Samsung usb cables were crap.. Tried a new one and works well. Samsung should fix the dialer/contacts lag now or i will never buy a Samsung phone Again! Anyone knows how to submit this bug to Samsung?
just flash aokp or some stock AOSP jb rom
paintball23456 said:
just flash aokp or some stock AOSP jb rom
Click to expand...
Click to collapse
Sorry for being a noob but this is my first Android phone and I have heard rooting/flashing voids warranty so I don't wanna risk it. I prefer doing it the simple way. Samsung should fix this bug soon.
there are ways to reset the flash counter..search the forum for triangle away. I flashed my S3 with many different custom ROMs. My phone earphone jack had some problem. I used triangle away, flash to stock ROM and bring it to Samsung for warranty. No problem with that..or maybe they didn't check thoroughly..:highfive:
farrukh494 said:
Sorry for being a noob but this is my first Android phone and I have heard rooting/flashing voids warranty so I don't wanna risk it. I prefer doing it the simple way. Samsung should fix this bug soon.
Click to expand...
Click to collapse
oh ok, a different version of sammy Jb will probaly fix the problem.
paintball23456 said:
oh ok, a different version of sammy Jb will probaly fix the problem.
Click to expand...
Click to collapse
All problems fixed. There was a problem with ota update. I resolved it by reinstalling the firmware through KIES firmware upgrade and initialization option. No lags in dialer contacts so far and blue Samsung logo on boot has come back. Thanks everyone. This thread can be closed.
Update: dialer and contacts lag still present
Hi all
Anyone experienced the occasional dialer screen messed up after a call?
See attached screencapture.
rekenaar00 said:
Hi all
Anyone experienced the occasional dialer screen messed up after a call?
See attached screencapture.
Click to expand...
Click to collapse
Wow...never seen THAT before.
Sent from my GT-I9300 using xda app-developers app
Dafuq happened there. Sorry man, never seen that
Woah bro. I have no idea what's up with your dialer. Are you on stock firmware and kernel? No root? No mods?
It only happened 2 or three times and I cannot reproduce at will.
First time was on stock rom without root.
Last time (screencapture 18/12/2012), was on sotmax_Ultimate_stock_V10_XXELKC_Aroma, but it was not a clean flash. I kept apps and data when I converted to sotmax rom. So it must be something carried over.
But happening very seldom, so not a big issue where I would want to risk a clean factory wipe.
Just hoped someone seen it as well.
Happened to me aswell today but exiting and reentering the Dialer sorted it out.
I'm on a clean install of crDroid 8.2!
so I am not alone :laugh:
same, here, exit and reopen fixed it immediately.
This has happened to me on various Sammy based ROMs all JB but different versions.
I really wouldn't worry about it to much, killing the app and opening works again.
Must be something with the dialer. The only thing I will say is that I did have all the motion stuff turned on.
Sent from my GT-I9300 using xda premium
Hello XDA. This ROM (rootbox 3.9.1) is supposed to be stable, but when I turn on flash or automatic flash and I touch to focus then shoot, the camera app lags and force closes (and doesn't take the picture). This is annoying in so many ways, and makes it virtually impossible for me to take pictures in low light. Please help me address this issue for it is killing me and I don't feel like downloading a whole new ROM, flashing it and reorganizing all my settings all over again just to fix this issue. I also had this issue with CM10.1 (but that was normal, cause it is a nightly).
Anybody else have this issue? And possibly a fix?
Thanks in advance.
Also: inb4 "search the official root box thread". I did, and nobody seems to have this issue.
Sent from my GT-I9300 using xda app-developers app
Marcellff said:
Hello XDA. This ROM (rootbox 3.9.1) is supposed to be stable, but when I turn on flash or automatic flash and I touch to focus then shoot, the camera app lags and force closes (and doesn't take the picture). This is annoying in so many ways, and makes it virtually impossible for me to take pictures in low light. Please help me address this issue for it is killing me and I don't feel like downloading a whole new ROM, flashing it and reorganizing all my settings all over again just to fix this issue. I also had this issue with CM10.1 (but that was normal, cause it is a nightly).
Anybody else have this issue? And possibly a fix?
Thanks in advance.
Also: inb4 "search the official root box thread". I did, and nobody seems to have this issue.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
As far as I know this issue was fixed a couple of days ago in the CM Nightlies so maybe the Vanilla Rootbox base hasn't been updated yet or you aren't using their latest update.
Scarface1991 said:
As far as I know this issue was fixed a couple of days ago in the CM Nightlies so maybe the Vanilla Rootbox base hasn't been updated yet or you aren't using their latest update.
Click to expand...
Click to collapse
3.9.1 is the latest as far as I know. I installed it a couple days ago.
Sent from my GT-I9300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2179233&page=66
Top post works for me hope it helps
neilster2020 said:
http://forum.xda-developers.com/showthread.php?t=2179233&page=66
Top post works for me hope it helps
Click to expand...
Click to collapse
Didn't work. what version of this aosp camera are you using? And with what ROM? I got the latest version. And it still crashes.
Sent from my GT-I9300 using xda app-developers app
Actually I've found a way to bypass this problem. If I turn on the volume key to take pictures function, autofocus with flash on and take the picture with the volume key, it doesn't crash. I guess I'll just have to live with it like this for now, oh well.
OK now how do I close this thread? Or there's no such thing? Can any mod or janitor or whatever help me out here? I'm new here
Sent from my GT-I9300 using xda app-developers app
I recently installed Cyanogen mod 11 on my Droid DNA.
Overall I'm loving the look and feel of Cyanogen mod, but I'm running in to some minor issues with maximum volume. For some reason the max volume for the speakers is now much quieter than it was before.
I've tried various solutions, one of which is here, I found the file they talk about but I have no "Speaker" section, just many variations.
Has anyone else had this issue? Does anybody know how I could force the max volume to be louder out of my speakers? I'm using YouTube videos as a reference.
I am running it and don't have this issue. Is your speaker partially blown or anything. Is there any physical damage on the phone.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Nope, no damage to the phone. And when I revert to the stock ROM the sound is perfectly fine.
That's strange. Maybe I'm just not used to it. I haven't noticed.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Yeah with me it was a big difference, I might try going through the sound config file on my phone and upping all the volumes by a few percent to see if that helps.
Jaggar345 said:
I am running it and don't have this issue. Is your speaker partially blown or anything. Is there any physical damage on the phone.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using Cyanogenmod? If so what version/nightly?
Anselm09 said:
Are you using Cyanogenmod? If so what version/nightly?
Click to expand...
Click to collapse
Snapshot 5. I haven't noticed the issue buy I really don't use the external speaker very often.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Snapshot 5. I haven't noticed the issue buy I really don't use the external speaker very often.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I did a clean install and made sure to install snapshot 5, and everything works perfectly now! Speakers are just fine which is great news.
Thanks for the help.
Anselm09 said:
Well, I did a clean install and made sure to install snapshot 5, and everything works perfectly now! Speakers are just fine which is great news.
Thanks for the help.
Click to expand...
Click to collapse
Glad to hear it. We're you running a nightly build before?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Glad to hear it. We're you running a nightly build before?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I believe I was accidentally using a nightly instead of a snapshot.
However a couple days after I fixed this issue CM updated to a newer snapshot, and the sound is broken again. Do you think I should report this as a bug? Or just wait for the newest update?
Anselm09 said:
Yeah I believe I was accidentally using a nightly instead of a snapshot.
However a couple days after I fixed this issue CM updated to a newer snapshot, and the sound is broken again. Do you think I should report this as a bug? Or just wait for the newest update?
Click to expand...
Click to collapse
If you did a clean install and it's on a snapshot you can report a bug. But if you didn't do a clean install do that first and then if it's still there report the bug.
Please press the thanks button if I have helped you in anyway.
Jaggar345 said:
If you did a clean install and it's on a snapshot you can report a bug. But if you didn't do a clean install do that first and then if it's still there report the bug.
Please press the thanks button if I have helped you in anyway.
Click to expand...
Click to collapse
It says all bug reports require a logcat, should I just run some sound apps then include the logcat?
Where's the thanks button?
Natural Log Sound Output decay
I recently installed "Dna Official Stock Kitkat - Rooted" for HTC Droid DNA by "santod040"
All sound files... alarms, ringtones, streaming start out fine then drop volume speaker output to near nothing
Anselm09 said:
For some reason the max volume for the speakers is now much quieter than it was before.
Has anyone else had this issue?
Click to expand...
Click to collapse
Me; I know the ROM is not cwm but stock 4.4.2 KitKat
Anselm09 said:
Does anybody know how I could force the max volume to be louder out of my speakers?
Click to expand...
Click to collapse
I flushed and am trying cm-10.2.1-dlx.zip to test speaker output; might give vipor rom a try as well
The handset is S-OFF, ROOTED, & CWM touch 6.0.4.5, with "Dna Official Stock Kitkat - Rooted" 4.4.2; Yes, sound was fine before the OTA notice came through prompting using santod040 packages.
Much Thanks to all lead to the lite..
viper4android Disables LPA
The only time I had ever had an issue was flashing a nightly dirty. I managed to recover the audio by installing viper4android.apk. The newer versions of V4A automatically detects if LPA (low powered audio) is enabled. It will give you an option to disable it, just tick that yes please button. Usually LPA only affects things like bluetooth audio so it wouldn't drain the battery as fast, but I know with previous CM versions they had a bluetooth audio issue. Most likely completely unrelated but there might have been a WIP that caused things to be construed. If another rom version works then i'd recommend just installing a stable release.
REMEMBER ~ you are able if you run stable :good:
This actually worked for me!
I downloaded Viper For Android, installed the updated drivers it recommended, then turned on "eXtra-Loud" for the phone speaker.
Audio is now just as loud as before.
Where's the thanks button? So that I can give you thanks.
WestTexasCoder said:
The only time I had ever had an issue was flashing a nightly dirty. I managed to recover the audio by installing viper4android.apk. The newer versions of V4A automatically detects if LPA (low powered audio) is enabled. It will give you an option to disable it, just tick that yes please button. Usually LPA only affects things like bluetooth audio so it wouldn't drain the battery as fast, but I know with previous CM versions they had a bluetooth audio issue. Most likely completely unrelated but there might have been a WIP that caused things to be construed. If another rom version works then i'd recommend just installing a stable release.
REMEMBER ~ you are able if you run stable :good:
Click to expand...
Click to collapse
Just wanted to pipe in with something that may be others source of low volume issues. I have had low volume on my stock Droid DNA for quite some time and really beat my head against the wall trying to figure it out. Turns out it was very simple for me but not terribly obvious. Get your phone out and look at the speaker grill (just below the Beats Audio logo on the back). Does it look a bit clogged? Mine was completely clogged (I don't use a case). I took out a toothbrush I use just for cleaning and cleared it up and my audio is nice and loud now. Just wanted to pass on this simple fix to try so others would see it.
Viper has been abandoned; what's a good ROM now?
Sent from my Nexus 6 using XDA Free mobile app