yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] kamieniarz:
I can't even instal the newest version (attachment from 1st post) couse it shows me an error about space on phone :/

Over 5 GB of free space and phone can't handle it? Damn...
[Paid Software Announcement and Discussion] prdog1:
That is an internal storage problem on device. Not the app. :cool:
[Paid Software Announcement and Discussion] kamieniarz:
Any help then?
[Paid Software Announcement and Discussion] prdog1:
Save what you need and wipe (format) the storage. :cool:
[Paid Software Announcement and Discussion] kamieniarz:
Are you kidding me? O.o That rly sucks then... Are you sure there isn't any easier way ?
[Paid Software Announcement and Discussion] prdog1:
Sounds like storage is corrupt to me or don't actually have 5 GB. This usually is caused by CM zero folder or recovery backups. Don't know what device, rom or recovery you are using. See it all the time with people coming from AOSP base back to TW. :cool:
[Paid Software Announcement and Discussion] kamieniarz:
Well I've got GT-I9505 with UBMGA. I had v1.4.4 and I wanted to install the newest version but I couldn't rewrite it so I uninstalled it to instal the newest one and now I have this stupid error :(
[Paid Software Announcement and Discussion] rootlinux:
What error is it giving you exactly?
[Paid Software Announcement and Discussion] kamieniarz:
Actually error is gone and app was installed successfully :D

I had an error about no space left and I was asked to uninstall some apps to make this space (when I had over 5GB of space).

The only thing I did was uninstalling old TubeMate version (due to I installed the newest one) and after that I tried to install CallRecorder with success :)

PS I don't know if my issue had anything to do with TubeMate but I'm just saying what happend.

Anyway thanks for help ;) I'll test this version and think about buying it :)
[Paid Software Announcement and Discussion] rootlinux:
Is it error 52 I think?

Check device storage to be sure you have space.

If you do and you uninstalled a prior version and get that error don't worry.

Most will say factory reset to clear internal storage.

If you are getting that error it is an easy fix without wiping storage.

From a root file browser go to root and the /data/data

Look for the folder linked to call recorder.

Delete that folder.

The app will then install.

What appears to be happening is the data gets left over and the device thinks it is installed and will not let you install again.

Since the app isn't installed you can't uninstall it either.

By deleting that left over data it will allow you to install again.

This will work for any app getting that error.

It started with Android 4.3.

---------- Post added at 07:01 PM ---------- Previous post was at 06:59 PM ----------

Strike previous post then. :)
[Paid Software Announcement and Discussion] kamieniarz:
I'm pretty sure that one day this post will save my life from irritation :D Thanks!
[Paid Software Announcement and Discussion] rootlinux:
I actually think the error is 24. :)

Yeah it is 24.

I may make a thread about it if there isn't one already.
[Paid Software Announcement and Discussion] BLADESMAN1889:
Guys,

Just be grateful that the app works on our device. On my previous phone I tried well over a dozen with no joy.

Considering how few other recorders (1 other as far as I'm aware) actually work at all, I'm not so sure that getting Bluetooth direct recording will be the Devs priority.

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Paid Software Announcement and Discussion] Nx6:
I'm grateful that the developer seems to spend a lot of time on developing a great application. However, please realize that he is selling this as a commercial product. It's not an open source project. As such, each of us gets to decide whether we think that the asking price is matched by the functionality that the app would provide to us personally. In my case, I've only gotten microphone recording to work, so at the moment it provides no more functionality to me than other, free apps. However, if better recording options were to become available, then the app would become worth purchasing. For me personally, once again.

Indeed, this information should be very important to the developer. "What can I improve to sell more copies of my app?" I sure would appreciate that information in his shoes.

And why wouldn't Bluetooth call recording be a priority? It would be a unique feature, and could very well warrant an even higher price, perhaps as an add-on or a Bluetooth edition or whatever. I'm not saying it would be easy to implement but it should be possible with root.
[Paid Software Announcement and Discussion] BLADESMAN1889:
My point being that there are no other apps that can record [apart from mp3In Call Recorder - via mic] even from mic unless I'm mistaken.

Given how many phones that are running Android, the % that have a working Call Recorder must be 5%.

It is the Holy Grail (hence the asking price) & my only point was that given the price - a totally justified one at that - the Devs priority must be to get the app working on as many devices as possible.

**Question**

How to tell if the recording is from mic or phone line ? What makes the difference ?

@ Skvalex,

PS, It is wrong of me to 'assume' to know what the Devs priority is with regards to the app or financial gain.

Thanks for your hard work.

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Paid Software Announcement and Discussion] Xoib:
The request from N4 owner are not the BT compatibility, but just the phone line recording capability. Because from the mic it's unusable. I use the earphones wire in the daily stuff so from recording from the mic is even more useless in this case.
[Paid Software Announcement and Discussion] fz798:
OK so I *think* I have this a little streamlined, I took the latest nightly and got Viper back fairly easily: try this and see if it works for you:

(I modded my nightly zip before flashing to include devil tools apk so just need to restore settings from within DT app after flash, easy. I also added in the two Viper apk files to the nightly, not sure that was necessary)

1. Nandroid (unspoken)

2. Dirty flash nightly + Devil kernel together, using TWRP, wipe cache and Dalvik.

3. First thing after flashing, open SuperSU and allow it to update binary using TWRP

4. After the SU binary update, open CR and be greeted with "ALSA not installed", use play store install, although it just opens the app, click OK to "install".

5. Now that SU binary is updated and ALSA has been reinstalled, open Viper and allow it to install the driver... BAM! worked fine for both Vipers

While still not hands-off updating for nightlies, that made it far less painful than having to remove/reinstall ALSA/CR/Vipers/drivers

HTH
[Paid Software Announcement and Discussion] proyect:
with kernel vanir doesn't work

http://xdaforums.com/showthread.php?t=2162937

http://www.emccann.net/jimsth/le_kernel/experimental/?C=M;O=D
[Paid Software Announcement and Discussion] love4chat:
Please add Samsung Galaxy Core I8262 & Galaxy S Duos to the device list...

Thanks For the Awesome App!!!
[Paid Software Announcement and Discussion] joebrit:
nexus 4 delay

I have a rooted nexus 4 (4.3 jwr66y) recording on standard api, default source, 0.3s delay. Has anyone had a problem with the nexus 4 doing this:

On an outgoing call, a toast message showing callrecorder given access for an interactive shell, but the recording not starting. Then after 8 seconds, a toast message saying "kill -9" then what looks like a different number each time (process number)? Then the recording starts. I've tried different delays, 0s and I can't hear the other person's voice on the recording, any higher than 0.3s just increases the delay above 8 seconds. Not a massive problem maybe but an annoyance.

EDIT: Latest update seems to fix this issue. Thanks.
[Paid Software Announcement and Discussion] davidlaugor:
With any kernel for 4.3 for htc one m7 it is working?

Enviado desde mi HTC One usando Tapatalk 2

---------- Post added at 04:09 PM ---------- Previous post was at 04:08 PM ----------

For android 4.3

Enviado desde mi HTC One usando Tapatalk 2
[Paid Software Announcement and Discussion] eyecon82:
Doesn't work in my sprint s4 stock rooted
[Paid Software Announcement and Discussion] srynoname:
skvalex, there is one important problem with firmware updates:

the alsa app remains installed, but the system files installed by alsa get removed, so call recorder can't record anything. however as a user one isn't informed about the missing alsa files until opening teh call recorder app. so after a firmware upgrade it often hapens to me that calls get not recorded and i don't notice that. please add a boot up service that checks for missing alsa system files and if necessary adds a hint to the status bar that alsa files need to be reinstalled!

same maybe for super su upgrade on android 4.3, maybe one could check if this requirement is fullfilled with a service.
[Paid Software Announcement and Discussion] lyrebird:
I am on the same side as you. For me, recording via bluetooth and wired headphone is very important, since important calls could come at any time. For htc one m7, i found that this app does no more than many other free apps. If this function is included, I will buy this app immediately.
[Paid Software Announcement and Discussion] prdog1:
That is problem with dirty flashing and not an app problem. That is user error. :cool:
[Paid Software Announcement and Discussion] Nx6:
Thanks for the support.

Sorry for coming on a bit strong before, I just got upset at feeling attacked for voicing my opinion in what I felt was a positive and constructive manner. Bygones.

I'm still surprised though at the lack of a fully featured call recorder for Android. it's something that I would expect a strong demand for in business settings. As others have pointed out, coming from a feature phone background you could have an expectation that this would be natively supported. I at times have a hard time remembering exactly what was said in a conversation with a customer or contractor and being able to go back to an old (or recent for that matter) recording can be invaluable.

Of course I can't be sure, but I don't find it hard to believe that a professional recording solution with the correct feature set and marketing could command a fairly hefty price and be quite successful.
[Paid Software Announcement and Discussion] prdog1:
The reason for not being supported by Google and many carriers is because of legal liabilities. Call recording is not legal in all jurisdictions thus it is up to us and the devs to try and circumvent the code that is placed by Android, carriers and the chip makers to block it. :cool:
[Paid Software Announcement and Discussion] Biker1:
I am not speaking on anyone's behalf, but I would venture to guess that:

- having a Call recording app that works across all platforms with all features operational is daunting at best. There are so many different devices, ROMs, Kernels, features, possible conflicts with certain settings, Samsung trying it's best to lock the call recording feature accessibility down, etc.

When the S4 became available, we were waiting quite awhile for call recording to be available to us, which it eventually was through the hard work of Skvalex and others. And that's only one device.

In addition, while call recording is indispensable to some, including myself, forttherreasons youdstate and others, I think its still a niche feature, and there are a limited number of people who require or would want it.

While I think about it, it may be possible to have call recording capability work on All phones, across all platforms, under all conditions with all features operational, but even if possible, it would most likely require a whole lotta money for equipment, personal, and untold amount of man/woman hours. And this is not feasibly for the aforementioned reasons.

Even if the above was possible, the cost of the app would most likely be exponentially higher, and the specialized niche would be further reduced.

In addition, think about all the apps out there whose call recording is extremely limited, and how many Developers discontinued development on these projects for reasons already mentioned.

I applaud Skvalex for his persistence with CallRecorder, and getting it to work across more platform, and have more features than with any other call recording application I've seen to date.

Plus the support Skvalex offers for CallRecorder is top notch :good:

I know the above is coming from an extremely satisfied poster, but nevertheless, the above is quite true......
[Paid Software Announcement and Discussion] BLADESMAN1889:
Hey,

I never meant to come across as attacking you. Sorry if it caused you any offence. I was just trying to do the same as yourself - put a constructive point across.

Also I am rather biased as I don't use BT. ;)

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Paid Software Announcement and Discussion] 2anyone:
:( wipe system & data, flash cm10.2 on Samsung Galaxy S3, intall AlaxMixer & Call Recorder 1.45.

Call Recording keep FC.

So I believe this is something wrong in: AlsaMixer/Call Recording/CM10.2(superuser)
[Paid Software Announcement and Discussion] prdog1:
Need to update to SuperSU. Kousch's SU don't work with with Call Recorder. :cool:
[Paid Software Announcement and Discussion] 2anyone:
How to install SuperSu in CM10.2 (superuser system built)?

Is that possible SuperSu & Superuser can work together in cm10.2? because I can't uninstall/root remove SuperUser from CM10.2 which is system level build. :(

I tried install SuperSu before, but SuperSu can't install something Bin files. :( Any suggestion?

thank you. [MENTION=4538493]prdog1[/MENTION]
[Paid Software Announcement and Discussion] prdog1:
Search this forum. It is a known problem and is documented. may have to use full SuperSU with binary from website. :cool:

Edit: See this post. PM and maybe this user can help you. http://xdaforums.com/showpost.php?p=44952427&postcount=2072
[Paid Software Announcement and Discussion] 2anyone:
Thanks [MENTION=4538493]prdog1[/MENTION], I refer the advice of [MENTION=5109905]Noob-superuser[/MENTION] and here is the little bit detailed solution if someone met same problem to install SuperSu in CM10.2:

After install SuperSu from Google Play, it will ask you update some binary file.

It seems will failed when you use normal update mode. if so, and you are using CWM / TRMP recovery, then you can try CWM/TRMP way to install binary SuperSu needs.

After you successfully installed SuperSu, it takeover all the actions which system-build Superuser did, no conflict happens.

it works for me, hope this note helps someone would like to install SuperSu in CM10.2.

:)
[Paid Software Announcement and Discussion] prdog1:
Yes. SU needs to be installed from recovery under the radar and to system. Glad you got it. Both of us learned as I never run AOSP. I want all I pay $700 for to work. :cool:
[Paid Software Announcement and Discussion] davidlaugor:
But any kernel works woth callrecorder for arhd 20.1, android 4.3, for htc one m7 2way recording? I ve been testing for a long time with no results at the moment...

Thanks!

Enviado desde mi HTC One usando Tapatalk 2
[Paid Software Announcement and Discussion] Triplo:
Why doesn't call recorder works in my Samsung galaxy chat?

It records sounds but cannot play properly.

:confused:
[Paid Software Announcement and Discussion] prdog1:
It is a phone call recorder. Not a chat recorder. Be more specific. :cool:
[Paid Software Announcement and Discussion] Triplo:
I know mate :sly:

Samsung Galaxy Chat is a mobile device model name.
[Paid Software Announcement and Discussion] prdog1:
Kewl. Look for the closest known device that has equivalent specs and go from there. :cool:
[Paid Software Announcement and Discussion] Triplo:
I don't get what you mean.If I root it will I be able to record calls in it?

Btw All the Galaxy Chat devices have this problem.
[Paid Software Announcement and Discussion] prdog1:
Skvalek is one of the most outstanding devs I have known. Must understand he can't test every device out there. He basically tries to cover Device catagories.. Although he doesn't have the device to test he makes work on a lot because they run same specs. Same processor, same firmware ect. Making work on custom roms and AOSP builds make it even harder. Closer to stock you are the better chance of it working. That being said. Should root anyway if can whether call recorder works or not. There are more advantages to root than call recording. There is always a free trial and a beta version in this thread to test. Best chance of making work on any device is flash the beta and send Skvalex a log. The logging is built in. With a log he can see whether he can make work for a particular device or he needs more info. This app is only as good as His years of experience in cal recording and the info we feed him. I have used for several years and never seen any better. It still only as good as the data we feed him. :cool:
[Paid Software Announcement and Discussion] thorazine74:
Is this combination of i9100 + CM10.1 definitely abandoned to be supported ? This never worked for me since moving to JB, worked perfectly in ICS, though with custom kernel sound libs.

I understand this is not possible in JB with the new sound drivers, but neither alsa mode is working, only some default mode that I think records from mic only (mostly useless unless using speakerphone).
[Paid Software Announcement and Discussion] prdog1:
All you can do is send Skvalex the logs. That all he can work off. CM is not stock and it is actually up to CM developers to make work. CM don't care. They have too many devices they porting to and all buggy. None ever stable and everything on device that you payed for don't work. Yall are happy with buggy rom but want Call Recorder to be perfect. Makes no sense. :cool:
[Paid Software Announcement and Discussion] tigro11:
on the terminal s6810p not record.
[Paid Software Announcement and Discussion] noobSU:
Who says that? CM is as stable as google android is. Buy nexus & try CM. Its all about device specifics. It is because of CM that, we're tasting vanilla android. (Including myself, in my Exynoss sgs3) The guys behind CM do their hard to give us stable builds. But because of what is not in their hands & impossible. We can't call CM buggy or blame CM in anyway.

No hard feelings :)
[Paid Software Announcement and Discussion] BLADESMAN1889:
+1

Custom roms from the likes of CM, AOKP, PA have come a long way in the 3yrs since I've been using Android.

Take the 4.3 update, roms are already running smooth & except for maybe 2/3 small bugs which will be fixed soon enough they are no worse than running stock.

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Paid Software Announcement and Discussion] thorazine74:
I won't bother to comment on the open source bashing, but saying that CM developers should change system so an app works...

I don't want CR to be perfect, if dev doesn't have time to support all of the many devices I could understand but we are talking a popular device with the de facto standard custom rom.
[Paid Software Announcement and Discussion] prdog1:
If it comes down to dependence on the homebuilt kernel or RIL then it does fall to the CM team. Get more done if send Skvalex the logs. :cool:
[Paid Software Announcement and Discussion] palvik:
Hi all! I may confirm that this app is working fine on Samsung Galaxy S4 Active I9295 with firmware I9295XXUAMH2:

Model: GT-I9295

Country: Nordic countries

Version: Android 4.2.2

Changelist: 957941

Build date: Mon, 05 Aug 2013 00:37:37 +0000

Product Code: NEE

PDA: I9295XXUAMH2

CSC: I9295OXXAMH2

MODEM: I9295XXUAMH2

You have to select Galaxy S4 in devices. I checked the application and it worked fine - I may hear both sides. You don't need root or any other modification of the phone!. Just install it from the Market.

Unfortunately, I am using another application right now because CallRecording is missing some features important for me.
[Paid Software Announcement and Discussion] srynoname:
I am using the *official* cyanogenmod upgrade mechanism, everything works fine except the call recorder stuff. some kind of error handling from the call recorder side would be useful.
[Paid Software Announcement and Discussion] skvalex:
version 1.4.6 beta03:

- after-call dialog will ask about each recording (not only about the last recording as it was before)
[Paid Software Announcement and Discussion] ocujos:
CallRecorder only works on CM10. I've tested CR on all Note N7000 CM10.1 & 10.2 ROMs and couldn't get it to work with recording from line.

My conclusion is that until there is a compatible kernel, CR will never work on CM.
[Paid Software Announcement and Discussion] Biker1:
Hope all is well.

Thanks for the update which is much appreciated.

Your support of CallRecorder is exemplary :good:
[Paid Software Announcement and Discussion] sjamie:
Which features are missing and which app are you now using?
[Paid Software Announcement and Discussion] palvik:
Number based recording. The CallRecorder allows select numbers only from contact list or not from contact list. The Total Recall S2/S3/S4 is more flexible here. it allows to record conversations with selected people from contact list plus all others.
[Paid Software Announcement and Discussion] skvalex:
In Call Recorder you can set default action for outgoing/incoming calls in the settings -> recording as well as set exceptions
[Paid Software Announcement and Discussion] palvik:
So I may record all except some numbers from contact list? Thanks. I didn't see it in the free version. I will give a try later.
[Paid Software Announcement and Discussion] thorazine74:
It sounds like CM team explicitly blocked call recording in 10.1, is there any source for this? I tried to search for commits in this matter but couldn't find any on Gerrit.

Besides even with other kernels like siyah or dorimanx call recorder fails the same...

Do you also need kernel support for alsa mode? I found it weird that even though 10.2 uses native alsa sound drivers we couldn't get it to work.
[Paid Software Announcement and Discussion] Xoib:
Yeah it need the 2-way kernel patch for real call recording.

It's a headache for Nexus 4 owner...
[Paid Software Announcement and Discussion] srynoname:
Call recorder works fine for me on 10.1.3-RC2 at galaxy nexus. note that the alsa app needs to be opened to reinstall the alsa system files that were lost during firmware upgrade. let me know if that was the problem for you.
[Paid Software Announcement and Discussion] bender5:
Recordinglength 1 sec?

I'm trying the app with my Desire HD. The phone has Android Revoultion HD (6.3.3) installed with Kernel 2.6.35.14 (obviously the same as in 7.3 or 9.0).

If I choose Kernel as recording option, I don`t get any files.

By using ALSA & *.wav the files have a length of just 1 sec although the phonecall lasts longer.

API with Uplink & Downlink is the same like ALSA.

All Calls tried were outgoing calls.

Any idea?
[Paid Software Announcement and Discussion] tk_xda:
Does this app work well on AT&T Motorola Atrix HD recording internally rather than microphone only?
[Paid Software Announcement and Discussion] thorazine74:
I assumed (because you can choose modes) ALSA mode worked independently, without relying on specific kernel, by routing audio with alsa mixer. Am I wrong?

Besides at least for I9100 in CM9 ICS you didnt need a real kernel patch, just to replace 2 sound system library files. I understand this is not posible in CM10.1 as sound system moved from Samsung to native ALSA sound drivers, so ALSA mode in Call Recorder does not work with CM10.1 I9100 ALSA implementation?
[Paid Software Announcement and Discussion] skvalex:
Root access will be needed at all.
[Paid Software Announcement and Discussion] OmenHTX:
thanks for aps
[Paid Software Announcement and Discussion] wdailly:
Call Recorder Root Permissions

Perhaps I am missing something... but CallRecorder does NOT allow be to change the Root Access in the preferences menu.

I am using a Google Nexus S Phone.

Just updated to OS to Android 4.0.4

Thanks for any help...

Wouter