There is no general section for android hadrware so i thought i'd ask here, since it's somewhat related.
I own both Samsung Galaxy S and Tab, and being what it it SGS can't record worth s**t. Only caller side can be recorded, which is a pity.
Tab wont be used for this, i havent even tried recording with it.
I used to record calls with my old HTC Touch Pro, no problems. For some reason SGS cant.
So, my question is: which of the highest tier android phones can reliably record both sides of conversation ? Not the speakerphone way, but properly, taking audio from internal hardware...
I'm about to renew my contract and i'd rather pick something that can be used as a recorder...
I don't think any android phone can at the moment.
evilkorn said:
I don't think any android phone can at the moment.
Click to expand...
Click to collapse
Incorrect. MIUI ROMs have call recording built in.
MIUI for Galaxy S ? (UK)
5thAgent said:
Incorrect. MIUI ROMs have call recording built in.
Click to expand...
Click to collapse
NONSENSE. MIUI cannot make phones which can not by hardware record phone calls magically do so. IE: All or most HTC phones, and according to the OP, Samdung phones.
There are multiple apps out there for this functionality, but it will only record both sides of a phone call on a lot of phones if you use the speaker. It can't record the headset portion of the call, only that coming from the microphone.
well with the htc hero it is possible with a custom kernel
according to leedroid it is with a custom kernel possible with a Desire HD too, but not stable
Hey
There is a Chinese phone out there wich does have it stock. You can actually flash it on the galaxy s.
Don't know if you are afraid of flashing the phone, but darky s rom 9.3 has it integrated. It is still in beta though.
Look in the development section of the galaxy s forum. There is a callrecording topic wich explains it all.
Good luck
Sent from my GT-I9000 using XDA App
The HTC HD2 with almost any rooted rom will do it. The only problem is that if you make a call from the bluetooth using voice dial (or any 3rd party app) the audio is lost in the speaker or phone if you switch from bluetooth. The only way to ceoorect is to re-boot. Not very practicle, but perfect if you don't bluetooth voice dial.
Desire HD on CM7 nightly and LordMod kernel, see my signature.
Records both sides of the call. Some people report issues. My experience has been flawless.
Sent from my Desire HD using XDA App
Anyone having call quality issues? I have been making a lot of phone calls lately with my Inspire (rooted with Revolution 3.0) and the people on the other end either can't hear me well or the call drops. I know AT&T blows, but this seems much worse then my IP4.
Is there anything I can do to try and fix this.. or is it just the nature of the phone and/or network? I sounds fine on my end.
Thanks
ever since i rooted and flashed a cooked rom my call qaulity has gone down also on every rom ive tried.blows hard
There is a sound fix for the custom roms. It is in the dev forums. The problems come from using the desire HD roms on our phones. I believe that some of the custom roms have the fix baked in but just to make sure flash it through custom recovery. My call quality is now perfect. As far as other people not hearing you, I never had that issue and if you are having that it might be a manufacture defect or network based. The only issue regarding call quality is the tinny sound but like i said that is fixed with the CWM flashable zip.
I have been getting a lot of dropped calls using the stock ROM. I report every single one of them hoping that they will get the hint and do something about it lol
Sent from my Desire HD using XDA App
This issue, that while using WIFI calling my audio during calls is routed to the external speaker, rather than the earpiece, has plagued my phone for weeks.
It seems to have started on the first BALI kernel, though as per Honk, it shouldn't be his kernel causing the issue. Though some are not reliant on WIFI calling as I am, I know there are others plagued with this issue..
That being said I started this thread to see if we can figure out what the issue is and not clog up the Bali thread
here's some info I found on a CM7 forum albeit for a different device, ZTE Blade, though with a very similar issue with all VoIP calling being routed to speaker.
It seems they were having alot of trouble figuring it out as well, and i'm not sure I understand some of the fixes they were trying to implement. maybe it can help though..
http://code.google.com/p/cyanogenmod/issues/detail?id=2858
I guess I'm the only one w the issue.. back to the Bali thread lol
sent from my real Gs move in silence like lasagna
You're not the only one with the issue...just the only one that it's really bothering. I don't use wifi calling being in NYC so the coverage is fine.
But I described that issue in the bali thread along with others, and also noted some issues possibly related to it.... voice dialing doesn't work, bluetooth voice commands don't work.
I'm using a stock deodexed Whitehawk KD1. The ONLY thing I flashed was Bali, and the issue has ALWAYS existed in each of the Bali kernels. It HAS to be Bali.
Yeah it is definitely the bali kernel it wasnt there before i flashed thus kernel i usw it sometime but it really not that important always 4g whereever i am going in my city
Sent from my SGH-T959V using XDA Premium App
I wouldnt blame the kernel, still running stock and have the same issue. I think it's the free wifi apk. I never experienced it before I called t mob and asked for the "upgrade". now on incoming calls I get speaker connection and on out going calls the recieving end always complains about echo.
On the moon our weekend are so advanced they encompass the entire week
I've been having the same problem for the past few weeks. For me, it started when I switched from the stock rom to teamwhiskey's rom. Its very annoying.
Yeah the echo is a problem too but I attributed it to Bali as well.. when the phone was stock there was always a low volume issue.. maybe tmobile will upgrade the app
sent from my real Gs move in silence like lasagna
i tried it on a stock rom umm it does the same thing its not the rom its the app
No one said it was a rom.. its the kernel
sent from my real Gs move in silence like lasagna
Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App
RaverX3X said:
Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App
Click to expand...
Click to collapse
Its the kernel. Wifi calling works fine with stock kernel. this is a known issue with Bali kernels.
I'm running bali 3.1 uv never knew it was a issue... I actually didn't try it until I seen that it was a issue for some.
Sent from my SGH-T959V using XDA Premium App
I have the same issue....
Project-V w/ Bullet 1.42 v2.2
T-mobile SGS4G running Bali 3.3 kernel with no custom ROM.
When I flashed this kernel I also wiped dalvik, data, etc. for a nice clean flash. At first calls routed to the speaker phone, but after letting the phone sit and rebuild for 20 minutes or so, the problem went away.
(smint) said:
T-mobile SGS4G running Bali 3.3 kernel with no custom ROM.
When I flashed this kernel I also wiped dalvik, data, etc. for a nice clean flash. At first calls routed to the speaker phone, but after letting the phone sit and rebuild for 20 minutes or so, the problem went away.
Click to expand...
Click to collapse
Do you have the echo issue?
The echo issue is horrible.. all people do is complain that they can't hear a thing but their voices. Its hard when its an important phonecall
Shermer321 said:
Do you have the echo issue?
Click to expand...
Click to collapse
sent from my real Gs move in silence like lasagna
I can confirm this as well... routing to speaker on occasion and echoing
I live quite a ways out of town and so wifi calling is the only option for me. My service out here without wifi is absolute ****. Given that I work from home and I'm always on conference calls, this is a real problem. I flashed the 3.3 Bali today and can confirm that it's still happening. Are there any updates to this at all?
I think were SOL at this point.. hopefully when GB comes out with a new custom kernel it'll work properly
sent from my real Gs move in silence like lasagna
RaverX3X said:
Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App
Click to expand...
Click to collapse
Stock ROM, stock kernel does *not* do the same thing. I've flashed stock to bali to stock to bali to stock again, and *EVERY* time I flash Bali, the problem starts. EVERY time I replace bali with the stock kernel, the problem goes away. I get nearly no signal in my room, and I rely heavily on wifi calling. Without a fix for this problem, the bali kernel is basically useless to me. Whenever I turn on wifi, all my calls route through the speaker and the other end complains about a terrible echo.
This is clearly an issue between the kernel and the wifi calling app, and since the stock kernel works fine whereas the bali kernel doesn't, my thinking is someone should setup some kind of data gathering layer BETWEEN the kernel and the wifi calling app to figure out how/why the two kernels are handling the wifi calling app differently.
Either way, this is not happening on the stock-from-t-mobile rom+kernel.
If you are not getting a signal from your room, try switching modems.I never got signal in my apartment and I flashed to kf1 and I started getting full bars and 4g. The stock wifi app seems to be giving a lot of users problems. I'll look into an alternative app
Sent from my SGH-T959V using XDA Premium App
So, I have noticed audio issues for as long as I have owned my s3, which I have had since it was released on Verizon. Been flashing roms on it just as long, never really noticed any issues with audio that were a deal breaker. My ring tones would crackle and music on the headset would sound crappy on some roms.
But now, I am using my phone to stream over blue tooth and have noticed that the audio is completely intolerable... But only on touch wiz, when I use an aosp room (mostly carbon rom lately) blue tooth audio is perfect. I have data issues on aosp at times and hate not being able to use any of the very cool tw roms available.
Anyone have an idea why this would be different from aosp to tw, and more importantly is there any fix available for this?
I have read several threads on this forum and others and the consensus has been it is a hardware problem, but if that were the case why is aosp so good? I am really hoping there is a better answer than trying to get Verizon to warranty it and needing to wipe and return my phone to stock to do that.
Sent from my SCH-I535 using Tapatalk 2
troyzero said:
So, I have noticed audio issues for as long as I have owned my s3, which I have had since it was released on Verizon. Been flashing roms on it just as long, never really noticed any issues with audio that were a deal breaker. My ring tones would crackle and music on the headset would sound crappy on some roms.
But now, I am using my phone to stream over blue tooth and have noticed that the audio is completely intolerable... But only on touch wiz, when I use an aosp room (mostly carbon rom lately) blue tooth audio is perfect. I have data issues on aosp at times and hate not being able to use any of the very cool tw roms available.
Anyone have an idea why this would be different from aosp to tw, and more importantly is there any fix available for this?
I have read several threads on this forum and others and the consensus has been it is a hardware problem, but if that were the case why is aosp so good? I am really hoping there is a better answer than trying to get Verizon to warranty it and needing to wipe and return my phone to stock to do that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
FWIW, we had a lot of trouble with that when the voltages were set too low, if your kernel allows it maybe bump your voltages up?
I'll try that, buy I'm pretty sure it was doing it with the stock kernel on tw.
Sent from my SCH-I535 using Tapatalk 2
Hey, guys. I would *LOVE* to use a stock KitKat ROM variant on my Note 3, as it performs better and has some more useful features than what comes with CM11. However, I'm forced to use CM11 because my Bluetooth headphones (Jaybird Bluebuds) sound awful under stock. Everything sounds compressed and high notes in particular sound undersampled and robotic.
I've tried replacing the Bluetooth stack with the same one used in CM and AOSP ROMs to no avail, and I can't seem to find any settings that help with this issue.
Is anyone else having the same problem?
Having the same problem with my portable speaker. I've been searching for a solution with no avail.
I'm thinking of reporting this to samsung, but I don't know how.
Sent from my SM-N900 using xda app-developers app
My problem is the other way around, great sound on stock but my bluetooth speaker makes hissing and popping sounds with cm.
Sent from my SM-N9005