Symptom: With the new evo based kernels there is too much mic gain and the remote party you are calling hears too much background noise and complains they can't understand you, or they think you are outside in a noisy place while you are indoors in a reasonably quiet place.
The fix is to use rootexplorer or similar file manager to rename default.acdb file in /system/etc/firmware (rename to any name you want, you can always rename it back) then reboot.
- Don't do this if you have a nexus one based kernel.
- BEWARE, if you rename default.acdb file you may start getting robo voice, depending on your winmo rom.
Renaming the file is all that is needed if you don't get robot voice.
If you get robo voice you need to change your winmo rom that has intentially older oem drivers (even if it is new base)
VBN Roms newest version works fine.
http://forum.xda-developers.com/showthread.php?t=776971
Energy roms are also fine.
Miri's newest rom doesn't work. (has robo voice) (Keep in mind that this rom does not have robo voice with the default.acdb untouched)
If you have another winmo rom that doesn't have robo voice please post and I will add it here. Don't forget radio version please.
Please test and provide feedback about winmo roms, call quality and robo voice.
IF YOU WANT TO TEST BY YOURSELF call another phone that you hold on your ear and put hd2 on a table or something. And tap your nails to a hard surface within 1 meter range. You will hear a lot of banging as if it is not your nails but a hammer. Then rename the defaut.acdb file and reboot. Test again and you will see the background noise (mic gain) is lowered to winmo levels and your nails sound like nails! And of course when you talk to
someone they will understand you clearly.
Credit goes to Cotulla, and a few people in htc-linux chat on netripper irc(log) and lippa from shubcraft thread.
Integrating this to android builds would be good development move.
Popular kernel info:
hastarins newer kernels, michyprimas r1 kernel, huanyus newer kernels are evo based.
michyprimas r11 is nexus one based.
if you have camera flash problems, you have an evo kernel.
EDIT: With some configurations, robo voice may only be present in first call only. And again with some configurations you may get system not responding: wait error on startup. Try: search and find new htcleo.acdb file and put it in the same folder as new kernels look for that filename.
Great post! I suspect a few have had this problem. I for one suffered this when using ANY EVO kernel. Now just to get BT working and its nearly perfect!
Great job buddy! Worked flawlessly! No more "speak slowly and NOT loudly please" comments from the people i call... I had VBN as Winmo so no robo voice...
Thanks again...
awesome
Great job! Worked perfect for me.
Kernel Help
What Kernel are you guys using? I've been trying some recent ones but they have not booted successfully. I've been using the desire Z build but I am going to give shubcraft's build another try.
what is that screen shot for?
No robo voice with leaked T-Mo 2.14 rom.
justwonder said:
what is that screen shot for?
Click to expand...
Click to collapse
Quadrant advanced benchmark. On the Desire Z build. Shubcraft was like 1400, the Z was 1897
After a full day of talking, every person I call is happy now. (They used to curse me ) No adverse effects.
i have the exact same problem weird noise and echo coming in the other end and people complaining they don't hear !! (not robo voice)
but there is no "firmware" folder all i got is "PPP" folder and a file named "AudioBTID"
i already searched the forum for 2 days and couldn't find a solution ..
tried several radios and several WM Roms with no luck i updated the kernal to the Evo latest 9th OCT and it didn't fix the problem ..
please guide me to a solution ..
D69K said:
i have the exact same problem weird noise and echo coming in the other end and people complaining they don't hear !! (not robo voice)
but there is no "firmware" folder all i got is "PPP" folder and a file named "AudioBTID"
i already searched the forum for 2 days and couldn't find a solution ..
tried several radios and several WM Roms with no luck i updated the kernal to the Evo latest 9th OCT and it didn't fix the problem ..
please guide me to a solution ..
Click to expand...
Click to collapse
Try:
Update your su binary through superuser app settings TWICE.
Use rootexplorer app and search the filename (default.acdb)
What is your build BTW?
updated SU binary and everytime i run root explorer it force close ..??!!
i already granted the access via superuser and it doesn't work ...
i am using "shubCRAFT" 1.5
thanks for your help
@D69K
Can you try this:
Open up terminal emulator and enter these commands:
su
chmod 777 /system
mount -o remount rw /system
and try to see with Astro file manaeger if you could now see the contents of /system/etc/firmware.
Thanks!
Mic gain problem is fixed by it. No robot voice. T-mobile 2.14 rom
But there is error report about android.pocess.media stopped, and some media player cannot open due to this... I'm using mattc 1.8 with michy's R1 EVO kernel...
Thnx
This fix. Seem to be working great.
Been about 4 days of usage now, everybody is happy.
If you get android system not responding on bootup (with some builds) just tap wait. It will work normally.
Thanks a lot
Thanks, I it works perfect.
T-MO HD2, Miris 20.0 Radio 2.11 Android 2.2.1
By the way the EVO kernel now has a good camera flash (since 10/17?), just as the Nexus kernel.
Thanks.
Hi,
I noticed that my phone having background noise issue after upgraded to the latest mdeejay desire Rom version 2.6, so I try to use the method suggested in this post to fix it but seems there are actually two default.acdb, one is in /system/etc/firmware while the other one is in /etc/firmware. I am wondering which one I should rename or I need to rename both?
I tried to rename the one in /system/etc/firmware but seems still got heavy background noise. I am with radio 2.15 also tried radio 2.14.
Thanks for help in advance.
Sent from my HTC HD2 T8585 using XDA App
I finally deleted both default.acdb and it seems like the noise reduced a lot, thanks!
I just wondering what will be affectes by deleting these files?
Sent from my HTC HD2 T8585 using XDA App
Related
OK guys,
Thanks to all hose who Beta tested the Neon WM6.1 Rom for the NEON.
I have just released V1:
Based on feedback from Beta testers this is the change log:
V1:
* Fixed HSPDA - When connection is idle 3G icon shows up, but when you use the connection it switches to HSPDA.
* Pagepool changed to 8mb
* Removed Diamond Dialer
* Kaiser Tweak
* Diamond USB to PC
* Reg Hack Hide Sim Contacts
* Reg Hack disable security warning
Important note: This Rom has only been tested with Radio 1.58.25.17. If you experience problems with your current Radio and this Rom you can download the Radio from the link at the bottom of the post.
These guys deserve a big thanks, Shortyboy and jcostanza4
Links
Public Beta: No longer supported, please update to V1 or V2
Radio 1.58.25.17 http://rapidshare.com/files/121638802/RUU_NEON_Radio_1.58.25.17.rar
NEON V1 http://rapidshare.com/files/127032001/Neon_WM6_1_RV1.rar
Pictures
Reserved for Updates
can somebody post this radio?
disflipissofresh said:
can somebody post this radio?
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?t=395384
freeze after flash
flash my one today and it freeze after loading into OS. You can't do anything except it need to soft reset and it start all over again. Have to flash it back to telstra ROM update.
avast detect trojan
could you give a quick scan with avast antivirus as this detect trojan when try to download
great !
did u have a link for the dialer !
Thx ?
i have an artemis !
Post #1 updated with new Rom.
thanks!
This worked perfectly with my Telstra HTC Touch dual (Neon) device.
For any other newbies like me, this is all I did-
Took my brand new Telstra Australia Touch Dual.
Installed the Neon Hard-spl here-
http://forum.xda-developers.com/showthread.php?t=377260&highlight=neon
Then just installed the rom in this thread. It works great, though i've lost my Office Mobile apps.
I had no sound at all on the first boot, but after reboot (and it does tell you to reboot again) everything was fine.
Thanks! And I look forward to trying your future releases.
woops one issue
An update on my install, I did actually end up having issues where as soon as a call was made or received all sound stopped working (which obviously makes calls a problem)
As per the original post, installing the updated Radio which took me from version .15 to .17 seems to have fixed this problem.
So are you saying that this ROM doesn't have
* video calling
* office apps
* or SOLITAIRE!?
Can they be installed afterwards or anything?
Cheers
jbng
Okay so I freaked a little when the camera stopped working and my guitar tuner wouldn't work, but it turned out I had to update the radio and that fixed both problems. It does seem to be smoother too.
Office apps are there, solitaire is there, but alas no video calling.
Can you get a third party app to do that, or will we have to re-flash the ROM if and when you add the 3G dialer?
I'm getting a bit sick of this hard reset rigmarole - although I am getting much more efficient at it!
Appreciate your work Seth - keep it up. BTW, the ROM update seems to have fixed my 'not waking up from standby' issues.
Cheers
jbng
You can use User Customization, works for me you only have to run it once after the hard reset and all you've configured will be setup. Maybe if Seth is really nice he will include it in his rom the next time so you don't have to run it manually. Check this thread: http://forum.xda-developers.com/showthread.php?t=366337&highlight=uc+junkies
jbngar said:
Okay so I freaked a little when the camera stopped working and my guitar tuner wouldn't work, but it turned out I had to update the radio and that fixed both problems. It does seem to be smoother too.
Office apps are there, solitaire is there, but alas no video calling.
Can you get a third party app to do that, or will we have to re-flash the ROM if and when you add the 3G dialer?
I'm getting a bit sick of this hard reset rigmarole - although I am getting much more efficient at it!
Appreciate your work Seth - keep it up. BTW, the ROM update seems to have fixed my 'not waking up from standby' issues.
Cheers
jbng
Click to expand...
Click to collapse
I'll try to make a cab for Video call now that i have figured out how to fix it.
You can always try my new Rom it has video dialing built in.
http://forum.xda-developers.com/showthread.php?t=403436
Thanks for all your work Seth
The ROM is working great - no lockups at all since installing it.
I seem to have conflicting information about Bluetooth being affected by radio ROMs - what's your opinion? The reason I ask is that my bluetooth range is pretty shocking (it won't even go through one thin wall in the next room) and I was thinking that maybe one of the newer radio roms might improve it.
Will the Niki roms on the radio page work in a Neon? Should 1.65x radios work with your ROMs? The 1.65s there seem to be from a Kaiser.
The other thing I've seen is a HTC-supplied 'bluetooth hotfix' for the TytnII - any opinion on that?
We'll hang out for your video calling CAB/ROM too. Not that I ever really video call, but if someone asks 'can you do video calling?' I want to be able to say that I can... ;-b
Actually that's a thing - if someone video calls ME, will I be able to answer with the current ROM?
Cheers mate
jbng
jbngar said:
Thanks for all your work Seth
The ROM is working great - no lockups at all since installing it.
I seem to have conflicting information about Bluetooth being affected by radio ROMs - what's your opinion? The reason I ask is that my bluetooth range is pretty shocking (it won't even go through one thin wall in the next room) and I was thinking that maybe one of the newer radio roms might improve it.
Will the Niki roms on the radio page work in a Neon? Should 1.65x radios work with your ROMs? The 1.65s there seem to be from a Kaiser.
The other thing I've seen is a HTC-supplied 'bluetooth hotfix' for the TytnII - any opinion on that?
We'll hang out for your video calling CAB/ROM too. Not that I ever really video call, but if someone asks 'can you do video calling?' I want to be able to say that I can... ;-b
Actually that's a thing - if someone video calls ME, will I be able to answer with the current ROM?
Cheers mate
jbng
Click to expand...
Click to collapse
See post 1 for the new Video Dialer.
In regards to the radios have a read here: http://forum.xda-developers.com/showthread.php?t=369502
I haven´t had much time to play with Radios. I´m using the radio of my post and my bluetooth is fine. The range is excellent, i live on the second floor and i still can get my cars bluetooth out the back in the carpark.
Hey Seth
VIDEO DIALER: didn't work. At all. I installed the cab, soft reset and had no phone dialer whatsoever. I don't mind reflashing the rom if that's what needs to be done - is the rom file on the front page updated with the video dialer? Or if the cab doesn't work will the rom not work too?
RADIO ROMS: it seems that the one you list is the best and latest for the Neon. The Niki ones and the Kaiser ones simply won't load. It's largely irrelevant anyway - because I don't think it's the phones problem...
BLUETOOTH: I faffed around for ages last night doing some tests with my dual and my decrepit old o2 mini (which used to have great bluetooth range) and it seems that the problem may be with the transmit power on my *computer* rather than on the dual. I left my dual next to my laptop at one end of the house, and then went to the other end of the house and did a search with the o2 mini. it found the dual but NOT the computer. I swapped phones and searched with the dual from the other end of the house and the same thing happened. So the phones have good range to each other, but they're both having trouble finding the computer.
I'm just waiting to get my hands on another laptop with bluetooth and then I can see if I need to call the good folk at Dell to replace my bluetooth module perhaps.
I'm also wondering if the laptop has gotten into its head that it's a 1m device instead of a 10m device. It's strange that I've only noticed it since getting my new phone, and now the old phone seems to have limited range too.
Anyways, blah blah blah - please let me know if you get any further with the video dialling in either the rom or the cab - and/or if there's anything you'd like me to test out for you.
Cheers
jbng
jbngar said:
Hey Seth
VIDEO DIALER: didn't work. At all. I installed the cab, soft reset and had no phone dialer whatsoever. I don't mind reflashing the rom if that's what needs to be done - is the rom file on the front page updated with the video dialer? Or if the cab doesn't work will the rom not work too?
RADIO ROMS: it seems that the one you list is the best and latest for the Neon. The Niki ones and the Kaiser ones simply won't load. It's largely irrelevant anyway - because I don't think it's the phones problem...
BLUETOOTH: I faffed around for ages last night doing some tests with my dual and my decrepit old o2 mini (which used to have great bluetooth range) and it seems that the problem may be with the transmit power on my *computer* rather than on the dual. I left my dual next to my laptop at one end of the house, and then went to the other end of the house and did a search with the o2 mini. it found the dual but NOT the computer. I swapped phones and searched with the dual from the other end of the house and the same thing happened. So the phones have good range to each other, but they're both having trouble finding the computer.
I'm just waiting to get my hands on another laptop with bluetooth and then I can see if I need to call the good folk at Dell to replace my bluetooth module perhaps.
I'm also wondering if the laptop has gotten into its head that it's a 1m device instead of a 10m device. It's strange that I've only noticed it since getting my new phone, and now the old phone seems to have limited range too.
Anyways, blah blah blah - please let me know if you get any further with the video dialling in either the rom or the cab - and/or if there's anything you'd like me to test out for you.
Cheers
jbng
Click to expand...
Click to collapse
I will do two things tonight.
1 - I'll flash this Rom back on my device, i'm currently using SETHS DIAMOND V2 Build 19214.1.0.4. And i'll try to work out why the Cab doesn't work.
I'll rebuild this rom and include the video dialer if point one fails.
Cheers
Hey Seth
In the interests of 'giving something back' - here's a handful of splash screens for the diamond and the neon for you to take or leave...
Your 'logo' is supposed to be a square ROM chip but with griddle lines over it (you're a chef, after all). It also happens to be an 'S'.
If you want any further tweaks or raw files let me know.
Cheers
jbng
PS. While we're on the subject of splash screens, I get an 'access denied' error when I try to replace the windows mobile startup .png file on your latest Neon ROM. Any ideas why that would be the case? With the previous ROM my file just copied straight over the top.
jbngar said:
Hey Seth
In the interests of 'giving something back' - here's a handful of splash screens for the diamond and the neon for you to take or leave...
Your 'logo' is supposed to be a square ROM chip but with griddle lines over it (you're a chef, after all). It also happens to be an 'S'.
If you want any further tweaks or raw files let me know.
Cheers
jbng
PS. While we're on the subject of splash screens, I get an 'access denied' error when I try to replace the windows mobile startup .png file on your latest Neon ROM. Any ideas why that would be the case? With the previous ROM my file just copied straight over the top.
Click to expand...
Click to collapse
Hi jbng,
Thanks for the wonderful images. The only program i know that can overwrite system files is Total commander. Just copy the file to your storage card and then use total commander to overwrite.
If that doesn´t work i posting 4 cabs on my latest Neon Rom for who ever wants to use your great artwork.
Regarding the Video dialer i just realized that RV1 has video calling, only the public beta didn´t. Please update your rom to either V1 or V"2.
Thanks
Hello!
I would like to get a copy of DCD's kitchen for his rom 3.2.0 and 3.2.2 (or the closest one to that).
The reason for that is that I want to compare what has changed between the two and hopefully locate the file that makes it so that skype 2.1.0.66 hasn't been working anymore since 3.2.x versions.
Somehow, DCD's site is down and I can't locate those files I need.
Any help?
Thanks!
i have the rom on my hard drive and 3.2.2 as a kitchen. if google dosnt find it i can send them to you
stanelie said:
Hello!
I would like to get a copy of DCD's kitchen for his rom 3.2.0 and 3.2.2 (or the closest one to that).
The reason for that is that I want to compare what has changed between the two and hopefully locate the file that makes it so that skype 2.1.0.66 hasn't been working anymore since 3.2.x versions.
Somehow, DCD's site is down and I can't locate those files I need.
Any help?
Thanks!
Click to expand...
Click to collapse
Here's a link to the last several Kitchens.....
http://dcd1182.n715dp.com/titan/kitchens/
stanelie said:
the file that makes it so that skype 2.1.0.66 hasn't been working anymore
Click to expand...
Click to collapse
is msxipkernel\nk.exe
Thanks DCD.
Is there an adverse effect in replacing that file in your newer rom? (aside from making skype work?)
Hum...
NK.exe is THE kernel...
Switching it might be a bad idea I guess, it might break lots of things?
Stuck on 3.2.0 until skype fixes their software I guess...
stanelie said:
Thanks DCD.
Is there an adverse effect in replacing that file in your newer rom? (aside from making skype work?)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2426507&postcount=46
Since dcd knows which file causes the issue and hasn't found a decent workaround/replacement for the file, I'd be willing to bet it isn't a "plug-in the file from a different WM version" fix. As I recall this was a pretty hot issue when WM6.1 surfaced and I believe the post below might say it best.
http://forum.ppcgeeks.com/showpost.php?p=434875&postcount=52
It seems Skype isn't interested in supporting our phone and they have the resources of eBay. If they wanted to support us (and a vast number of other phones,) they could..... but they don't. That's called a "marketing decision" when big corporations do it..... specifically, a "poor marketing decision."
I've seen services called "iSkoot" and "Nimbuzz" mentioned as alternatives.
Well,
I just tried both : Nimbuzz does not hear anything from my Titan's microphone and iSkoot wants to call their gateway with a regular phone call, which is long distance for me, so, it's out of the question.
I also do not get any audio with fring on my phone.
Any other ideas before I flash back to DCD 3.2.0?
imo, this was due to an idiotic/crappy/lazy slap wm6.0 code into wm6.1 platform builder move by HTC ... It worked, with some weird side effect on code that uses critical sections it seems... well, not all code... mainly multimedia apps (such as tcpmp). Unfortunately, until HTC fixes the kernel with the correct code, we are out of luck.
3.2.1 and above also broke SRS WOW
it seems the kernel update broke a few media apps...specifically the ones the tried to interface with the audio or mic
no2chem said:
imo, this was due to an idiotic/crappy/lazy slap wm6.0 code into wm6.1 platform builder move by HTC ... It worked, with some weird side effect on code that uses critical sections it seems... well, not all code... mainly multimedia apps (such as tcpmp). Unfortunately, until HTC fixes the kernel with the correct code, we are out of luck.
Click to expand...
Click to collapse
the kernels are device specific? i thought they're coded by microsoft and deployed by the manufactures like windows for PCs...that's news to me.
incubus26jc has released a Froyo (Androis 2.2) port for the vogue. This *might* as always work on nike. If you want to give it a shot, here's the original thread:
http://forum.xda-developers.com/showthread.php?t=712310
Btw: The vogue community is way faster than g1, still waiting for froyo to hit my device
i have try it, it works for me, and the same bug, difficult to receive call, no bluetooth, no camera. And with the newest kernel - broken sound. Can you fix that kernel?can we ask dzo to fix kernel for Nike user?is there a way to make bluetooth and camera working?
Yeah, lagloose already informed me about the kernel problems. I don't have much time coding atm, but i gave it a quick shot yesterday.
Havent tested it yet as my touch dual is somewhere in a drawer at home and i have to look for it .
If you want to give it a try and report back if it works:
http://84.23.71.227/kerneloftheday/zImage_audiotest
BTW, nice to hear that the rom is working.
€: In principle it should be possible to get the cam and bt to work. I tried to play around with BT, but I was not able to get it working. Must have missed something...
looks like you are the only one who can compile Nike kernel, just contact dzo, he doesn't have time to did it for Nike user, he asked me to find someone who know some C and linux box to make the kernel. maybe we can asked some tips from him and applied it on Nike kernel?
i think the first thing is to make receiving call working, it seems like when using android, it is difficult to make our phone ring when receiving call and why this made we can't use our phone with android.
hope you can spend sometime for this problem, i'm very appreciated your work for Nike communities... thank you very much
testing...
Mblaser, I tested the kernel, touchscren not work!
OK, I will try again tomorrow. Messed up my kernel autobuild and have to fix it first...
sound working for me, it's back to normal again although in highest volume level it is still too loud and the sound is a little broken, but seems find in lower sound level, maybe a little more adjustment to that will make it better.
and just find another thing, i have my receiving call problem solved even i'm activated vibrate function. for now hope mblaster and maxxd01 can make bluetooth and camera working in zimage kernel.
here is what i did:
1. update newest kernel using mblaster kernel with audio bug free from http://forum.xda-developers.com/showpost.php?p=7021840&postcount=3
2. using phone prioritizer from http://forum.xda-developers.com/showthread.php?t=558822
this will make android a much more usability
leonardoaraujo said:
Mblaser, I tested the kernel, touchscren not work!
Click to expand...
Click to collapse
Are you on nike100?
€: Kernel service up again with audio patch included. Hope verything works now. Niki100 version is also patched now, touchscreen problems seem to be vibration related on niki100 (thats why there is a vibration free version especially for theat phone).
http://84.23.71.227/kerneloftheday/
Sent from my Htcclay's SuperBad G1 using XDA App
€€: Let this thread sink, there is another one on the same topic here: http://forum.xda-developers.com/showthread.php?p=7037314#post7037314
If you have something to say, go and post there!
Has anyone got two way voice recording working on any of the ICS releases, whether a MOD or a 3rd Party app?
I tried a couple (killer mobile and call recorder) but no luck.
same here. call recorder always worked 100%
Anyone? Still can't find one that will work....aaarrrggg.
I would like to know too. I heard Samsung has removed the necessary call recording libraries in ICS. Hope that is not true.
afaik it will work soon, becuase the ics kernel sources are published today. that will grant many developers to fix everything which cant be fixed before. afaik the call recording problem inlcuded!
Looking forward to this. I loved that on GB. There is a tutorial @ "Original Android Development" category (for GB), maybe someone can start from there to make it work on ICS?
-Aeth.
aethery said:
Looking forward to this. I loved that on GB. There is a tutorial @ "Original Android Development" category (for GB), maybe someone can start from there to make it work on ICS?
-Aeth.
Click to expand...
Click to collapse
Where's the tutorial?
1+
Before I use CallRecorder but now it does not work ok
me too. that was very useful as it recorded automatically
I can confirm, call recorders does not work on ICS.
I tried almost all available from the market, but no success.
I need it too
Sent from my GT-I9100
This seems to be an useful thread - http://forum.xda-developers.com/showthread.php?t=1482721 - this actually points to a easy way of getting call recording functionality back!
Here's my understanding from the thread. Basically there are three files in /system/lib that are used for call recording API -
libaudioflinger.so
libaudio.so
libaudiopolicy.so
(It's interesting to note that out of these, only the first is there in ICS.)
If we copy the files from 2.3.6, and replace/add the files, there's a good chance that we will get back call recording. Now to get these files... does anybody have the older version, or know how to extract these files from the ROMs?
SOLVED XD - Need to know if it's reliable
Hi,
I have tried "Auto Call Recorder" (free) and seems to work ok.
Without any patchs or modifications on the rom it works ok recording from mic (depending on you it could be wnought or not).
QUESTION 1:
Someone could tell us if this program is realiable? (I mean, if we can trust in it).
Because it have several permissions that I'm not sure it should have or if it's neccesary.
It has 100.000 - 500.000 installations and 4 star score
How can we be sure if this program is not spying us?
RECORDING WITH API (not mic)
Here http://forum.xda-developers.com/showthread.php?t=1551353 I have found a thread where there are two ICS libs (different from the GB ones) that sould fix the problem and should allow to record from API, so we could get clear and loud sound.
Files are audio.primary.exynos4.so & audio_policy.exynos4.so in /system/lib/hw
Files can be downloaded from http://www.mediafire.com/?r2wgv821w1uutzd or from http://forum.xda-developers.com/attachment.php?attachmentid=955906&d=1332235902 (both are binary same)
QUESTION 2:
Again reliability.
Someone could tell us if this libs are realiable? (I mean, if we can trust in it).
I have downloaded "ZSLPE" that is supposed to have call recording and this libs are the same that the original in XXLPQ, and are different of the downloable ones that I say before (supposely patched).
If ZSLPE have call recording, why libs are the same that XXLPQ?
Where are this "patched" libs from?
Again the same question, are this "patched" libs reliable?
Perhaps I could be some paranoid, but I don't want a spy on my phone or something worse, and I want to be sure that all my phone conversations (or any other personal data) are not sent to anyone.
Probably is stupid to think that anyone could be interested in my bored conversations, but those are mine...
Greetings
^ Thanks given
For security concern, you may want to try out LBE Privacy Guard... I use it. It can help you to deny certain permissions for any program which you think has no business asking for the permission.
You may question that program more though, as it asks for a lot more permissions in return for the power!
Personally, I would trust the libraries and the auto call recorder - the permissions it asks seem legit. I checked the hack works with Total Recall too, so if you feel more comfortable you could use that.
hirak99 said:
I checked the hack works with Total Recall too, so if you feel more comfortable you could use that.
Click to expand...
Click to collapse
Could you explain what you mean by this I not sure I understand.
Thanks to everyone who has been responding it looks like we might not be too far away from call recording on ICS. WooHoo!
OzBoy1 said:
Could you explain what you mean by this I not sure I understand.
Thanks to everyone who has been responding it looks like we might not be too far away from call recording on ICS. WooHoo!
Click to expand...
Click to collapse
I installed the two .so files mentioned in this thread into /system/lib/hw -
http://forum.xda-developers.com/showthread.php?t=1551353&page=2
After a while this worked for me, for both Total Recall and Auto Call Recorder. I have DXLP7 with CFRoot LP7 kernel.
Alternatively, according to the same thread, in ZSLPE call recording works from start.
Let me know if that helps, or I can answer any other questions to get it working for you.
i installed resurrection rom 1.0 and when i tested it, it works. have to press record yourself mind.
tommo123 said:
i installed resurrection rom 1.0 and when i tested it, it works. have to press record yourself mind.
Click to expand...
Click to collapse
in phone settings - extend settings, you can set it automatic for incomming and outgoing calls. works like a charm here and records both sides (i'm using resurrection rom 1.0 too)
elroy944 said:
in phone settings - extend settings, you can set it automatic for incomming and outgoing calls. works like a charm here and records both sides (i'm using resurrection rom 1.0 too)
Click to expand...
Click to collapse
Does it work with bluetooth?
I can confirm that the call recording on Resurrection rom 1.0 works flawlessly.
Previously I tried some of the latest Energy ROMs and liked them for the speed, the lack of HTC messaging, the well organized Start Menu, etc. but had to move on to another ROM because I had serious audio problems with Energy. Problem present while making phone calls and also while listening to music/watching movies through headphone. While volume is below ~50% the sound is so dull and faded I hardly understand what my talk partner says. Above ~50% it turns to an extremely sharp tone with almost no bass that hurts my ears. Also the volume difference between the steps are very uneven.
Tried both 21916 and 29022 of the 'Standard Reference' series with radios 2.15.50.14 and 2.12.50.02_2 with the same result. Used HSPL4 and the SD card method.
Strange but I couldn't find anyone complaining about such problems in the ROM thread so it is absolutely possible that I'm missing something although stock 3.14, Laurentius and Artemis (this is my current) ROMs had perfect audio on this phone.
Anyone could point out what I'm doing wrong?
Come on guys, any thoughts?
Or nobody uses WinMo anymore?...
Still using it
Just stumped on your issue as not experienced any volume issue on more than 20 HD2 company handsets running Energy rom (older 23699build is one we use)
Don't know if any alterations to the audio para file where made in later builds of Energy so worth searching the thread on it.
You could copy the audio para file from Artemis & use it to replace the Energy rom one & see if makes any difference ...
Thanks for the hint, to be honest, this is the first time I hear about this file.
I've done some research in the forums, now I understand that it should be a file called audiopara.csv in the \Windows folder. The problem is that in Artemis ROM there is no such file there nor on the entire device. Tried to find it with Resco Explorer with displaying hidden/system files all enabled, but found nothing.
While searching I found some pretty unclear info about NRGZ and pyrorob trying to address some in-call background noise with these mods but trying to put the picture together from a topic of 3600+ pages gives me headache. I've never had such noise issues they mention.
I'd like to start flashing the ROM but without any possible solution in my hands it would be a waste of time so if you or anyone could give any further advice that'd be great.
As I didn't get an answer I started flashing Energy ROM again to see if anything goes different this time but no luck, audio is messed up just as like my previous try. Before that I digged out my old Diamond2 from below the dust which also had perfect audio. Searched for the audiopara.csv and found it, saved to my PC to be prepared. My idea was that I'll replace Energy's audiopara with this as a try if things go bad but I had no luck because - like Artemis - Energy doesn't have this file in \Windows or anywhere else.
As I had to flash something to use the phone I decided to try something new: I flashed HD2O's v22. Not really the thing I planned because I don't really like WM6.5.x but otherwise it's a surprise! Lightning speed, HTC Messaging is pretty usable and fast and have the best audio quality I've ever had on HD2 so it seems like I stick on that.
Then again I can state that Energy's last ROM is unusable this way, either it is a bug or they overadjusted something.
Had a look on my older 23699 Energy build & it has no audio para file so that seems normal on these builds.
I have not experienced sound issues on any HD2 we have on energy ROM & audio quality seems fine, no staff have complained either ...
Maybe an issue linked to HSPL & radio or Energy ROM flavour of build you use.
Had a search in the Energy ROM thread too but found nothing much relevent to this issue.
Hope the HD2O ROM stay good for you ...
Mister B said:
Had a look on my older 23699 Energy build & it has no audio para file so that seems normal on these builds.
I have not experienced sound issues on any HD2 we have on energy ROM & audio quality seems fine, no staff have complained either ...
Maybe an issue linked to HSPL & radio or Energy ROM flavour of build you use.
Had a search in the Energy ROM thread too but found nothing much relevent to this issue.
Hope the HD2O ROM stay good for you ...
Click to expand...
Click to collapse
Sadly no. After some weeks of usage problems started to appear, for example disabled vsync caused terrible tearing in Sense and in Opera (only sometimes, otherwise no). Cooked in uTask caused sense to stuck at "Launching Sense..." forever at bootup, also Opera stuck at its splash sometimes, etc. So I went back to Artemis, now with the latest v72 but the usual annoyances are still there, for example permanent "Bluetooth on." message in notifications causes notification icons in the top bar to group so there is no missed call or new text icon just a generic "new someting happened". WM taskbar pops up every now and then when I touch the clock in the corner even if it is disabled in Artemis Center. Today I traveled by train in low coverage areas, listened to music while browsing the internet and every time I left coverage then when it came back I got a message window "Bluetooth stereo headset connected" (I used a wired earphone ). If I connect my car bluetooth when the phone is in vibrate mode the volume become a complete mess, nothing selected on HTC volume screen and in reality this means "Silent" no ring nor vibration appears on incoming call. Although I didn't try all the roms out there it seems there is no usable cooked rom for the HD2 and this is rankling. I'm on the edge of flashing back the stock 3.14 and apply all the tweaks manually I tried before with success.
Anyways after this amount of squawking... You mentioned you use a previous release of Energy and don't have audio problems. Could you give me the version number of it? Do the older Energy ROMs available anywhere? Or maybe do you have that image file? I could give it a try...
straylight975 said:
Sadly no. After some weeks of usage problems started to appear, for example disabled vsync caused terrible tearing in Sense and in Opera (only sometimes, otherwise no). Cooked in uTask caused sense to stuck at "Launching Sense..." forever at bootup, also Opera stuck at its splash sometimes, etc. So I went back to Artemis, now with the latest v72 but the usual annoyances are still there, for example permanent "Bluetooth on." message in notifications causes notification icons in the top bar to group so there is no missed call or new text icon just a generic "new someting happened". WM taskbar pops up every now and then when I touch the clock in the corner even if it is disabled in Artemis Center. Today I traveled by train in low coverage areas, listened to music while browsing the internet and every time I left coverage then when it came back I got a message window "Bluetooth stereo headset connected" (I used a wired earphone ). If I connect my car bluetooth when the phone is in vibrate mode the volume become a complete mess, nothing selected on HTC volume screen and in reality this means "Silent" no ring nor vibration appears on incoming call. Although I didn't try all the roms out there it seems there is no usable cooked rom for the HD2 and this is rankling. I'm on the edge of flashing back the stock 3.14 and apply all the tweaks manually I tried before with success.
Anyways after this amount of squawking... You mentioned you use a previous release of Energy and don't have audio problems. Could you give me the version number of it? Do the older Energy ROMs available anywhere? Or maybe do you have that image file? I could give it a try...
Click to expand...
Click to collapse
We use the 23699 as was best WM build for our use & loaded software.
Use it on over 20 work HD2 handsets & with a few tweaks & bit of cleaning here & there is a rock solid performer ... will upload the image for you to try ...
Mister B said:
We use the 23699 as was best WM build for our use & loaded software.
Use it on over 20 work HD2 handsets & with a few tweaks & bit of cleaning here & there is a rock solid performer ... will upload the image for you to try ...
Click to expand...
Click to collapse
Thanks, I greatly appreciate your efforts! :good:
http://www.mediafire.com/?byc5347l2nd3ol4
Refer to the NRG thread for HSPL/Radio version & install tips etc. We always do a hard reset after the flash as tends to reduces possible issues.
I would test your audio issue before installing & setting up the ROM too much as I have not seen your audio issue on any of our HD2s on this ROM !
With a little work this is a great stable ROM ...
Mister B said:
http://www.mediafire.com/?byc5347l2nd3ol4
Refer to the NRG thread for HSPL/Radio version & install tips etc. We always do a hard reset after the flash as tends to reduces possible issues.
I would test your audio issue before installing & setting up the ROM too much as I have not seen your audio issue on any of our HD2s on this ROM !
With a little work this is a great stable ROM ...
Click to expand...
Click to collapse
Thank you sir, I tested it and I experienced the following: the audio issue is also there in this ROM but at a much much lower level, it is almost unnoticeable, I just hear it because my bad experiences with the latest Energy. Dinik's glass icons, keyboard, etc. is too much for me so after extensive googling I found the WM6.5 Standard version of the same Nov24 branch and it also seemed totally usable with good audio. But... in the meantime I read some other ROM's topic and found another promising one, CleanEX RV with 6.5 so now I'm testing that and put Energy as a 2nd best for spare. I'll see but I'm certain one of them will be my ultimate ROM. :good:
straylight975 said:
Thank you sir, I tested it and I experienced the following: the audio issue is also there in this ROM but at a much much lower level, it is almost unnoticeable, I just hear it because my bad experiences with the latest Energy. Dinik's glass icons, keyboard, etc. is too much for me so after extensive googling I found the WM6.5 Standard version of the same Nov24 branch and it also seemed totally usable with good audio. But... in the meantime I read some other ROM's topic and found another promising one, CleanEX RV with 6.5 so now I'm testing that and put Energy as a 2nd best for spare. I'll see but I'm certain one of them will be my ultimate ROM. :good:
Click to expand...
Click to collapse
Have changed a lot of icons within the Dinik ROM & we use Finger keyboard due to wide amount of language support including a very good Thai keyboard layout plus layout etc is customisable but over all find the dinik skinning good.
Believe we have the NRG 28244 reference from March but no others.
All builds from Nov24 onwards had serious issues for us & we found just spending time to enhance the 23699 build best option. Hope one of the 2 works out well for you, have not used/tested CleanEx RV so will be interested in your remarks ...