Related
I know that there are some ROMs that this software is included.
In my ROM this software is not included.
Where can I find this software?
amitbsh said:
I know that there are some ROMs that this software is included.
Click to expand...
Click to collapse
I believe HTC is the only company where this is not possible
If you found a software or ROM i would be appreciate if you post the software here.
The only way you can record a call on the HD is if you use the speaker and some third party software such as Isecretary or Resco Audio Recorder.
I don't have the software, but I have read in one of the forums that this software exists in some of the HD ROMs.
i think that this forum is exactly the one for this purpose.
There are a lot of members form a lot of places, and we will find the member that has this software.
From what I've heard, ICR (In Call Recording) was included in preproduction ROMs only. It would be good to know that somebody got it, at least to check if it's worth anything. Anyway, I wonder why HTC decided to exclude this soft from production ROM...
Works fine
I use Resco Audio recorder. Works fine
zSpinner said:
I use Resco Audio recorder. Works fine
Click to expand...
Click to collapse
Are you saying that you can record the income voice as well as your out going voice on a call and then play it back.
As I known, the ICR application is only valid in CHS ROM or with CHS pim.vol.
MDAIIIUser said:
Are you saying that you can record the income voice as well as your out going voice on a call and then play it back.
Click to expand...
Click to collapse
From Resco Website:
"Record and organize every incoming or outgoing call."
Program startup and recording of whole phone call. Store to a special subfolder and name the recorded file with caller/callee's name.
(Both sides recording is hardware dependent. If your recording contains voice of one side only, it is not due to the program's failure.)
huanggx said:
As I known, the ICR application is only valid in CHS ROM or with CHS pim.vol.
Click to expand...
Click to collapse
So you can verify it exists? Is the ROM out there?
Surur
surur said:
So you can verify it exists? Is the ROM out there?
Surur
Click to expand...
Click to collapse
Sure, it exists. The official ROM is not released yet.
If someone has the non official ROM that includes this software we can extract it form there.
Yes, please! If somebody would be able to get the original ICR software from HTC, this would be really great! The hardware obviously supports recording both parties (or HTC wouldn't have included the SW in the first ROMs) and with the currently available 3rd party apps, you either have to turn the speakerphone on to hear the other person, or he's way to slient to understand properly. With HTC's software, both callers should be audible perfectly.
Regards!
I would have thought that if the HTC software was "market ready" they would have put it in the 1.14 rom. As they have not I can only think that it will generate more support calls than anything else.
My thoughts anyway nothing confirmed
MDAIIIUser said:
I would have thought that if the HTC software was "market ready" they would have put it in the 1.14 rom. As they have not I can only think that it will generate more support calls than anything else.
My thoughts anyway nothing confirmed
Click to expand...
Click to collapse
It may be more to do with the law than technology.
Surur
tkalli said:
From Resco Website:
"Record and organize every incoming or outgoing call."
Program startup and recording of whole phone call. Store to a special subfolder and name the recorded file with caller/callee's name.
(Both sides recording is hardware dependent. If your recording contains voice of one side only, it is not due to the program's failure.)
Click to expand...
Click to collapse
If I understand correct, it is a cooced ROM, wich is able to record both party by a phone calling - with 3rd party program: resco audio recorder.
I used the original 1.14.401 ROM with this program, and i could hear only my voice. With an other PDA - Samsung Omnia - i recorded both party with succes.
The program Audio Notes Touch is able to record both party, but the voice of caller is very quiet.
Well I have downloaded the resco version 4.51 and you can hardly hear the incoming side on my HD.
Well I think by the law, its not legal to record any phone conversation without the permission of the persons involved.
However the development of such a program may be easy, releasing it to public has to asure legal purposes.
So therefore, I don't think any of that HTC releasing or some ROM having it is true.
MDAIIIUser said:
Well I have downloaded the resco version 4.51 and you can hardly hear the incoming side on my HD.
Click to expand...
Click to collapse
What is your ROM version?
atomikpt said:
Well I think by the law, its not legal to record any phone conversation without the permission of the persons involved.
However the development of such a program may be easy, releasing it to public has to asure legal purposes.
So therefore, I don't think any of that HTC releasing or some ROM having it is true.
Click to expand...
Click to collapse
I don't think it is so. By other producers - like f.e. Samsung - it makes no problem. So I think the reason should be something else.
Hello,
I develop one program for call with the video.
It's possible to invoke by program a phone call via an intent :
Intent intent = new Intent(Intent.ACTION_CALL, Uri.parse(url));
where the url contents the phone number.
How to specify that we want to make a video Call on 3G-UMTS and not a vocal call.
Assuming that we have the right phone, the right OS version, the right operator.
I don't think there is a public API (read: a generic action *) for that yet. Very strange but true. Video calling on mobile phones has been possible for more than 10 years, but Android doesn't support this generically yet.
edit: There is an issue open on this on AOSP. All we can do is chime in and ask for vendors and Google to make this public.
*: Using an explicit intent (with full component class) may be seen as code hijacking, some developers / companies don't take kindly to that, so be careful!
damn I need this function bec I am deaf. I need damn it..
Yes therefore made for the time Android is the manufacturers who have developed this module, so you do not know how they can proceed to make a video call.
And excuse me for my English, I'm French and I do not speak it very well
kkm883 said:
damn I need this function bec I am deaf. I need damn it..
Click to expand...
Click to collapse
Well, stupid question maybe, but why not just use the stock dialer?
Or doen't video call work while on 3G? In that case there's very little you can do about it, because your mobile operator has to support video calling (some don't). If anything, keep trying new Fring & Sipdroid versions until there is one that works on the SGS...
miki4242 said:
Well, stupid question maybe, but why not just use the stock dialer?
Or doen't video call work while on 3G? In that case there's very little you can do about it, because your mobile operator has to support video calling (some don't). If anything, keep trying new Fring & Sipdroid versions until there is one that works on the SGS...
Click to expand...
Click to collapse
Fring now works on the SGS, they fixed it. Get the latest version from the market.
Edit:
Not working yet.
The phone app will crash when your record is stopped.
Created .3gp files are empty.
See page 2 for logs.
This is "our" Phone.apk modified, not the asian one.
Also tried with the asian libs, but they seem to be the same.
Btw: Who added [Hack] to the title ._. ..
Cool, thanks for your effort. I'll wait for someone to check it out
Fr4gg0r said:
I extracted the Phone.apk from Asian Firmware from samfirmware.com..
and I think it supports the sound recoring we know the asian firmwares have.
Click to expand...
Click to collapse
I too so thought.. but imho that's record videocall
thanks for the effort
I did the same thing with the korean phone.apk (deodex and replace original files). it didn't work either, just FCs.
I still believe the Korean phones have the hardware needed to record phone audio. Until someone gets this to work
According to this thread :
http://forum.xda-developers.com/showpost.php?p=9088397&postcount=32
call recording is allowed by hardware. If there's a developer to a find a solution for it, he'll be taking some of the bounty supercurio was looking for in his months-old thread about sound tweaks, that seems not supported now.
Call recording is a must feature for quite few of us.
I dont believe its disabled in hardware. (expensive solution)
I think its disabled in kernel code. (cheap one)
xan said:
I dont believe its disabled in hardware. (expensive solution)
I think its disabled in kernel code. (cheap one)
Click to expand...
Click to collapse
+1
cheap phones have this function is standard
and 500 € phone, could`t cause harware issue
half of samsungs code consists of appending strings for logging.
need this functions too
Don't want to promise anything, but I'm quite excited at the moment...
At the moment it crashes when saving the record.
Saved .3gp files empty.
continue m8,we do not hurry
maybe the interaction with native driver fails, not sure about it. Hoping it's not.
Posting your log might help.
Heck even dmesg might.
I am willing to donate for this feature if we could get it to work.
Daneshm90 said:
Posting your log might help.
Click to expand...
Click to collapse
yup.
http://pastebin.com/qWwVieX3
It obviously already crashes before hitting "stop":
11-30 14:28:35.801: WARN/audio_input(2821): numOfBytes (0) <= 0.
11-30 14:28:35.801: VERBOSE/AudioRecord(2821): stop
11-30 14:28:35.805: DEBUG/AudioHardwareALSA(2821): Entering AudioStreamInALSA::standby
11-30 14:28:35.813: VERBOSE/AudioRecord(2821): stop
11-30 14:28:39.933: ERROR/imdg81(3109): IsShutDownStarted()
11-30 14:28:39.933: INFO/KeyInputQueue(3109): Input event
11-30 14:28:39.941: DEBUG/InCallScreen(16029): simService - SMS Services
11-30 14:28:39.941: DEBUG/PhoneNumberUtils(16029): ril.ecclist0 112/0,112,911
11-30 14:28:39.941: VERBOSE/WindowManager(3109): Dsptch to Window{48f22dd8 com.android.phone/com.android.phone.InCallScreen paused=false}
Click to expand...
Click to collapse
Edit: Seems to be a native or even hardware problem, so I'm out at this point.
Btw: Samsung called setAudioEncoder and passed 3, whereas the docs only specify 0 and 1, tried both but did not help.
I've attached the apk.
push
asdf
Hi!
call recording on sgh-m100s works different. as you can see in the wm8994 initialization code (wm8994-aries.c).
see: hxxp://forum.xda-developers.com/showthread.php?t=842740
you won't be able to record through the means you specified.
i was able to change the wm8994 code in jpm firmware (latest available on opensource.samsung.com) to the sgh-m100s one to record but video call recording was broken. so that is not the way i prefer.
another interesting class is inside libaudio.so. it's called voicecallrecorder which seems to record through the svnet0 interface (ipc to radio).
it could be an option to write the necessary jni classes for that.
kr
David
Any news yet? It's a good idea if it can be made to work.
I have a Samsung Galaxy SIII and just made my first NFC-steps using some Samsung TecTiles tabs.
After trying a few NFC apps from the Google play, I have a few basic questions.
While basic functions like p.ex. switching Bluetooth are available in all apps, other functions like p.ex. showing a pop-up, text-to-speech or calendar functions are only available in only in one particular app.
Is there a predefined set of nfc-functions for any given android version or the app-author is basically free to program any function he can think of?
I tried to import a tag in one app which i previously have written with another app. This didn't always succeed. I could understand that there is a problem with importing special functions which are unknow to an app, but at least the basic tag and the basic functions should be recognised by all nfc-apps.
As the nfc-apps progress, will we see new functions/possibilities or will it stay about at the present level as the available functions are limited by android?
My device is locked, mainly because it was mandatory by a VPN installation.
Is there a way to unlock it 'automatically' thru NFC? I know this can be a security issue, but it would be so handy just p.ex. to put the phone in the car-holder and it would automatically go to the home screen or the car screen, and also during driving its annoying when the device has a time lock and needs to be unlocked in the middle of an intersection......
What is the power consumption of the nfc-module in the S3?
Thanks for your input.
Rgds
sansibar said:
I have a Samsung Galaxy SIII and just made my first NFC-steps using some Samsung TecTiles tabs.
After trying a few NFC apps from the Google play, I have a few basic questions.
While basic functions like p.ex. switching Bluetooth are available in all apps, other functions like p.ex. showing a pop-up, text-to-speech or calendar functions are only available in only in one particular app.
Click to expand...
Click to collapse
I think, I know which app you mean
Is there a predefined set of nfc-functions for any given android version or the app-author is basically free to program any function he can think of?
Click to expand...
Click to collapse
There is a set of predefined nfc-functions, (like open a webpage, vcard, open an app..) but this set is very very limited and even the mentioned Bluetooth function is not included .... in fact, bluetooth needs a little hacking, because the official api does not support to turn on bluetooth without asking the user .....so basically a developer can (/ has to!) implement every function he wants, but in reality a lot of functions are blocked on non-rooted devices, because android defined them as security related....
I tried to import a tag in one app which i previously have written with another app. This didn't always succeed. I could understand that there is a problem with importing special functions which are unknow to an app, but at least the basic tag and the basic functions should be recognised by all nfc-apps.
Click to expand...
Click to collapse
As mentioned the basic set is very limited.... it´s based on the nfc forum specifications and using nfc to control your device, is something these guys never had in mind ....so, sure you could use some standard nfc writer and write a webpage on a tag..... and this should be something every nfc device (not only android, but also blackberry, windows phone etc...) could handle .... but if you want to control your device, you need a more sophisticated app .... and there is no way to import a tag from one app to another ...
As the nfc-apps progress, will we see new functions/possibilities or will it stay about at the present level as the available functions are limited by android?
Click to expand...
Click to collapse
The functions are limited by android .... and my feeling is, that with every android update it get´s more limited! --> on Gingerbread, nfc was enabled while screen was off --> a function they skipped with ICS (ok, again, on a rooted device you could change the NFC.apk, to re-enable it) ... the last JB update declared the airplane modes as a security feature ... so no luck with airplane mode since 4.2 ...only to mention 2 examples ...don´t get me wrong, I don´t think it will stay at the present level, but it´s definitiv not in googles focus yet .... personally, I have a lot of new functions and use cases on my ToDo list, so I would say it´s just the beginning
My device is locked, mainly because it was mandatory by a VPN installation.
Is there a way to unlock it 'automatically' thru NFC? I know this can be a security issue, but it would be so handy just p.ex. to put the phone in the car-holder and it would automatically go to the home screen or the car screen, and also during driving its annoying when the device has a time lock and needs to be unlocked in the middle of an intersection......
Click to expand...
Click to collapse
yep, but again some hacking is envolved ... root your phone, change the nfc.apk, etc. ...I think there are several threads regarding this topic available ....
EDIT: Link added: http://forum.xda-developers.com/showthread.php?t=1853721
What is the power consumption of the nfc-module in the S3?
Click to expand...
Click to collapse
Forget it .... it doesn´t make a significant difference, if you have NFC enabled or disabled ....
Thanks for your input.
Rgds
Click to expand...
Click to collapse
no problem
I tried a number of things to get the Google dialer without success.
For now work with kk dialer, has anyone any idea how to get rid the TrueCaller?
Just don't use TrueCaller?
r25txe said:
Just don't use TrueCaller?
Click to expand...
Click to collapse
Thanks for nothing .
I have said that I have kk dialer, to install Google dialer am looking.
Open up the dialler and go to settings, the three dots, The top option is Truecaller you can turn it off
nikoslikos said:
Thanks for nothing .
I have said that I have kk dialer, to install Google dialer am looking.
Click to expand...
Click to collapse
I gave you the advice you wanted about Truecaller. As the previous poster stated, you can disable it, or, as I advised, simply not use it. Getting offended because someone took the time out to respond is terrible manners.
You may need to be rooted to remove it and we do not know if you are rooted. We don't know if you are running a Lollipop or Marshamallow ROM either. You have not helped us to help you by not giving us your platform information.
Have you tried to install the Google Dialer from the modular GApps thread?
Be warned that they are targeted to 32bit ROMs. Do a backup!
You could also try CM Next dialer from CM C-Apps package. This also includes Truecaller, but it is trivial to disable it.
I am rooted and am on stock TOS208G with trucaller uninstalled. I replaced with caller ID & call recorder app https://play.google.com/store/apps/details?id=com.callapp.contacts that I prefer.
I have found the phone does not display whose calling via contacts only by the true caller ap. Have I installed something in error or got a setting wrong please?
Trucaller help in many ways
r25txe said:
Just don't use TrueCaller?
Click to expand...
Click to collapse
It helps in many way to find out spam caller, customer care calls,
and know the number location carrier etc etc
thunderbolt9148 said:
It helps in many way to find out spam caller, customer care calls,
and know the number location carrier etc etc
Click to expand...
Click to collapse
Understood, but the poster doesn't want to use it.
r25txe said:
Understood, but the poster doesn't want to use it.
Click to expand...
Click to collapse
From what I have found, there is no caller id system on the phone without having one of the various true caller id apps installed.
image45 said:
From what I have found, there is no caller id system on the phone without having one of the various true caller id apps installed.
Click to expand...
Click to collapse
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
I think True Caller is still on my Swift, so I will test this later.
Sent from my P00A using XDA Labs
r25txe said:
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
I think True Caller is still on my Swift, so I will test this later.
Click to expand...
Click to collapse
Uninstall true caller id and see for yourself then, you don't have to trust the contents of members post if you so choose.
image45 said:
Uninstall true caller id and see for yourself then, you don't have to trust the contents of members post if you so choose.
Click to expand...
Click to collapse
I don't have TrueCaller on my device afterall. The dialer is the stock Android dialer and my caller ID works without issues.
What's the packagename for TrueCaller?
Sent from my P00A using XDA Labs
I wonder if I can restart this discussion here -- I want to turn off TrueCaller, but in Google Play it says it's a System App and it does not appear at all under any name in the Settings - Apps listing (no matter whether showing or hiding system apps). What other options do I have?
I'm on Android 7.1.2. My TrueCaller has no options to either turn it off or to turn off the notifications it brings up (which is my main reason for wanting to get rid of it: for something that's blocking spam, it spams me far too much with stuff that I don't want it to do).
r25txe said:
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
Click to expand...
Click to collapse
This should indeed be the case. Unfortunately, for us Swift (1st gen) users at least, this is now broken.
When Wileyfox migrated from CyanogenMod to Android they broke a few things along the way as well as doing a deal with the Devil aka Truecaller.
Unless your device is Truecaller enabled then caller ID simply will not work. We've tested at least two dozen dialers and contact managers (all from Google Play) and not one of them works with the Swift in its current firmware state. We even installed the APK of the Google Phone dialer (provided by WF themselves and which according to Google Play is incompatible anyway) and even this does not work.
Besides, how many dialers does a mobile ecosystem need anyway? One has to ask themselves why there are so many and why they nearly always require OTA registration to do what they offer....
But that's another matter altogether.
There are other issues too such as SMS alerts going off at full volume in the earpiece during an active voicecall; or the persistence of 'charge mode' when connecting via USB, even though MTP has been set in the developer options or from the status pull-down.
One thing it tells us is that the Swift cannot be running stock Android - otherwise these problems just would not happen. If not that, then it is that WF don't have a proper working build process or test protocol.
Either way, the Swift is damaged goods now and it might seem WF are prepared to kick it into the kerb. Probably the best option now is to try Lineage, assuming owners are savvy and even want to.
On the other hand we could band together to oblige WF to get an update released. We have been trying for months to get their attention, both before and since their buyout by STK. For those who are minded to, perhaps you would like to add your support by liking the following Facebook post:-
https://www.facebook.com/officialwileyfox/posts/1872330073078309
If enough give it the thumbs up then WF may be moved to respond. Please support this initiative if you can.
Thanks.
gktscrk said:
I wonder if I can restart this discussion here -- I want to turn off TrueCaller, but in Google Play it says it's a System App and it does not appear at all under any name in the Settings - Apps listing (no matter whether showing or hiding system apps). What other options do I have?
I'm on Android 7.1.2. My TrueCaller has no options to either turn it off or to turn off the notifications it brings up (which is my main reason for wanting to get rid of it: for something that's blocking spam, it spams me far too much with stuff that I don't want it to do).
Click to expand...
Click to collapse
We think we have found a solution:-
It ought to be possible to disable Truecaller but not remove it entirely unless your phone is rooted and have other management tools. We have managed this is on our own device which is totally stock and never been tinkered with (7.1.2 Nougat, Build No: TOS257G – N2G48B).
Secondly, installing another dialler from Google Play or via APK will work but it's almost 100% likely that a further setting will need to be made: setting as the default phone app.
This can be done in two ways:-
i) Settings->Apps->Configure Apps (Gear icon in top bar).
ii) From the app drawer, drag the dialler app icon to the "App Info" drop zone at the top of the screen. Scroll down to the setting that says "Phone App" - it should be yes or no.
See attached screenshots for reference.
It seems to us that many owners think their Swift can't be used with any dialler other than Truecaller, when in fact they can; the mistake is on the part of the firmware which won't recognise another dialler by default and hence breaks the contact ID display when incoming calls are received (not to be confused with caller ID).
Hopefully this serves as a solution. :good: