I'm running a ROM Based on Quarx's JB (Moto Ice Gun) on my Defy+.
Whenever I try to put a call on hold and answer another incoming call, the interface freezes, the Phone App hangs and I can't make/recieve calls unless I reboot.
I'm sure that this is not ROM specific, and I've been having for quite a while on many different ROMs. Is this the bug or am I the only one facing this?
Works pefectly on GB Based Roms though
Edit: Ok, I did a full wipe + minimal gapps + JellyX (cfs) and it seems to be working right now. It feels a whole lot smoother too. Sorry for the inconvenience.
Related
I have just upgraded my Defy MB525 (green lens) to Jelly Bean 4.1.2, using CyanogenMod's Quarks.ru 2012-09-24 nightly build (the last one made for the MB525). It's working like a charm, the system is very smooth and bug-free, and I've noticed that battery life is longer, too. I'm loving it, except that predictably, I lost the ability to record calls (yes, it is legal here, that feature has helped me in more than one instance, and it is important for me).
Formerly, I used my carrier's official version of Froyo, with two modifications: it was rooted, and I replaced a system module with a Chinese Android version to enable call recording, as I saw this tip in various forums. It worked perfectly, with Sanity recording all incoming and outgoing calls crisply both ways. Now Sanity has stopped working; it tries to record the call, but it sends a message saying that it couldn't. I can make it record from the microphone, but then it only records what I say, not what the other person said on the call.
I won't risk using that Chinese module again, because it's an old tip and it was a Froyo module. Most certainly, it won't work with Jelly Bean and may even break the system. I have only found tips to enable call recording on Samsung phones, and an old one for Gingerbread on the Defy+ (MB526) with the warning that it caused phones with Ice Cream Sandwich not to boot. Not only is the MB526 a different model, but if ICS won't boot with that modification, so won't Jelly Bean.
Does anyone know how to restore full call recording capability to my phone? Thanks a lot.
You need to flash this http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip
It says it's for MB526 but it's for both MB525 and MB526.
Make a data wipe before flashing, you don't need to flash anything else, you can flash the gapps.
Once done, go-to Phone, press menu button, go-to settings, and find the option to enable call recording. The recorded files are stored in /sdcard/CallRecording
Sent from my MB526 using xda premium
Thanks a lot, hackergnome. :good: I'm going to try it and will post the results after it's done.
Call recording still not working after update
Well, I flashed the 2013-04-09 ROM, and thanks again to hackergnome for it, because I had Android 4.1.1 and now I have 4.1.2. I wish there was a 4.2 ROM that worked on the MB525.
I had two little scares while doing it. The first was that CyanogenMod reboots twice right after updating to 4.1.2, and both reboots take a very long time, with the LED lit in red, a behaviour I had never seen before. I almost panicked, but waited, and in the end the system booted fine.
The second scare was that until 4.1.1, there was a language choice option on first boot with all available languages. Now it's limited to English (UK and US) and Spanish, so for a moment I thought that Brazilian Portuguese was not available in this distribution. I'm fluent in English and have a reasonable working knowledge of Spanish (plus, there are some spelling and grammar mistakes in the PT-BR localization); I could use either language in the interface, but there are regional settings and utilities such as T9 and dictionary that are handy to have in the language I use most. Fortunately, Brazilian Portuguese was still available after boot in the phone's Settings.
Unfortunately, call recording is still not working. After configured to do so, the native phone feature only records the first 2 to 5 seconds (average 3 seconds) of both incoming and outgoing calls. Sanity was still unable to record calls (whether or not native call recording was enabled). After I uninstalled Sanity (thinking that one app might be interfering with the other), the native app still records only the first few seconds of each call.
Any hints? Thanks.
Working so-so after exploring further apps
I kept researching and found that some people had success installing Alsa Mixer. Supposedly, it has the same effect as that Chinese libaudio version had on Froyo, and makes call recording apps work. Here, it didn't work, and Alsa Mixer itself only presented a blank screen. I uninstalled it. I'm only mentioning this because other users may find the same tip. Don't waste your time with it - it may work with other phones, but not the Defy with CM10.
So, I kept trying the many call recording apps available from Google Play. User comments show that they all have an erratic record, working on some phones and not on others, so it's a matter of trial and error. I finally succeeded with Call Recorder by Clever Mobile (there are many apps all named "Call Recorder," so you have to differentiate them by the developer). Sound quality isn't the best (especially on the other party's side) and you have to make sure the app is on every time you turn on the phone. It doesn't register whether the call is inbound or outbound in the file name and doesn't register the phone number either; in fact, all file names are "Unknown." But at least it's working. The app is free with a small ad banner; there is a paid version without ads.
I really miss Sanity's options, flawless operation and crisp recordings that I used to enjoy when I was on Froyo. A pity that it doesn't work on Jelly Bean (at least not on the Defy with CM10). Sanity's development was stopped 2 years ago, so a new working version won't be coming. But now at least I can explore other options, knowing that I'll always be able to come back to Clever Mobile's solution if they don't work. I can't do it now due to time constraints, but if I find a better app, I'll post it here, so others with the same phone, OS and problem can use it as a reference.
Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.
In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.
i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:
Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.
Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk
I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6
I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app
Good morning, I've a strange audio problem, on stock or custom rom stock based the volume lower itself even if is set on the max level, otherwise if I install for instance the alpha of the cyanogenmod everything works perfectly, do you know where the problem is located? and how can I solve it?
Cyano is too still too unstable and not ready for a daily usage (GPS almost broken, 4g rarely works, random reboots etc...) so I would like to go back to stock but with this volume issue it's impossible, please help me... :crying:
Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...
Hello everyone!
Recently I installed RR 5.8.5 (android 7.12 nougat), along with nano Gapps and a custom kernel (Raiden Kernel at first, then switched over to HYPER n UPSTREAM). Everything is running smoothly, except during calls.
The problem is that when I have a bluetooth device connected (and acting as phone audio), if I try to switch from bluetooth audio to handheld from the in-call menu, my phone freezes and I have to restart it. It's really annoying and any help with the issue will be appreciated!
There was another occasion where something similar happened, I just couldn't close the call. It kept running in the background even though the other person had closed it and eventually my phone froze again.
Happens under both kernels, which is why I think it's from the OS. I'm a bit of a flash-noob, so I don't know how to get crash logs and stuff like that, so if you need any, you'd have to tell me how to get them.