I've been searching forever, and now i'm starting this thread...
Is there a way to enable mic adjusting(gain) for outgoing calls on Dell Streak?
My mic volume is somewhat poor, the other one can hear me, but i need to speak a bit louder in order to hear me...I'm using CM7 with DSC Test 2 Kernel.
Any solution would be appreciated!
Thanks in advance!
From what i've read here, it has something to do with the kernel and libaudio.so, but i don't know how i could impelement this...
Use the DSC Gain app from the DSC ROM. I believe _n0p_ has made it available separately, and thus the ROM thread should have a link.
DSC Gain controls only output hardware controls for speaker, bt, and headset, not for mic gain, and that is what i really want, the thing that transmits the signal from the mic to the other side of the line when talking...
But thanks for reply anyways
mic voltage is already at maximum in the kernel. It has values 0-7 (0 is the highest), so i simply cannot set it any higher.
Could it be a problem from CM7?
I am planning to go back to DSC because of this and SMS problem, i'm starting to have problems with recieving messages, i had the problem of sending SMS's but solving by setting GSM only setting...
Also, should i try to clean the mic?
You didn't clean it?
Just kidding.
--
DSC won't help you with mic issue. I had complains about not hearing me from time to time since i got the Streak. Have tried orienting device so mic is close to mouth?
I have tried, and now it's a habit, i have found the best positions for both hands in order to get myself heard a bit...
How should i clean it? I'm not really gonna' try with a toothpick or something that could damage the mic for good...
So the best option seemed to be a software gain...
And here is where the help needs to kick in...
I was looking forever for something to help me in this...but i don't even know where to look... I read some problems on xda about CM7 having some problems on some phones with the mic, but obvious, the patches/hacks are not compatible...
So i'm looking to boost that signal... And won't stop )
I'd start with studying q6audio.c in kernel.
I'm going to look, hope i an make out something of it...
I'm a computer science student, but only 1st year...so i have much to learn, and all i know for now is some knowledge in C programming...
And big thanks! At least i have a lead
I found some interesting things in q6audio.c, one line (535) contains audio_tx_volume function, and after some studying, i found that tx is for all mic's and rx is for all speakers (tx - input / rx - output), well, this isn't much, but i posted again to ask something...also, i found something about "default.acdb" that file seemed to store something about those volumes, but i'm unable to find this file in streak, so is either renamed, or there is another way to handle the whole process...(i bet on renaming )...
After i make the changes, how can i implement them in streak?
Or, how can i make some changes in order to be implemented in streak?
Do i need to make the changes in another way somewhere in postboot?
(not really experienced in this kind of stuff..)
--Sorry for double-post, i didn't noticed --
Lexmazter said:
DSC Gain controls only output hardware controls for speaker, bt, and headset, not for mic gain, and that is what i really want, the thing that transmits the signal from the mic to the other side of the line when talking...
But thanks for reply anyways
Click to expand...
Click to collapse
Unfortunately I don't use DSC Gain despite using DSC 1.1. At least it didn't hurt to try it.
I hope there is a solution for you out there.
Fun, i beleive Tx stands for Transmit Data and Rx - for Recieve Data.
After some researching TX/RX stands for Transmitter/Receiver... So i think i'm getting closer and closer
I still don't know what to do with what i found, and i don't know how to implement something here... I'm scratching my head and scratching le Google ..After all this research if i can call it like this, i think the parameters and volumes are stored in the "default.acdb", which i can't find in streak, i've been studying online versions of "q6audio.c" (supernova-kernel-dz, HTC Desire GB open source kernel), now i'm trying to figure how to build something using instrutions provided on opensource.dell, and other places... I think this is a good place to really put me on the right path
Tx volume setting is not present in current kernel.
I've added it (and config parameter).
Currently testing.
Thanks for doing this for me... If i would know how to do it, i would have done it
Thanks a lot
I would like to help you, at least with the testing.
If you on DSC I can give the link.
I'm on CM7 Test 2 but i can flash DSC in a few moments (i use CM7 only because of rotation animation ) if this works only on DSC.
Or i could try to implement it in kernel for CM7... If you tell me how
CM7 needs additional changes.
http://n0p.8bit.fm/streak/DSC_Phoenix-U2.zip
Control value:
/sys/module/q6audio/parameters/tx_volume
I'm absolutely unsure if it works at all and which values should be set.
(set to 800 by default)
I'm now downloading DSC v1.0, i'm gonna flash it ant after that i'm going to play with the parameters, i think 1200 would be max (from what i've learned from q6audio.c)...
Testing in a few minutes...slow download
I've set it to 1800, testing.
Made a few calls, positive responce, but this might be placebo effect.
Related
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!
Hi all. Is there a way now how to have this in place? I tried to look in the options and check the internet, and even found a hilarious thread
Code:
http://talk.sonyericsson.com/message/77144 --> gave me a good laugh
But how to have this working? Of course it would be good to have the ringing low at first then if not picked up it increases in volume until answered or cut out. Heck, even the ancient dumb phones have this, why not a latest phone?
Are all android phones like this, needing an app for a simple basic feature?
Do we really need to manually modify a sound file and make it as a ringer to attain this?
Any inputs?
Nothing really? How do you guys manage to work around this? I'm sure at some point you thought about this?
Now while I like the "nature" theme of the SIII as much as the next guy, I've got one problem with it.
Like the title says, I really dislike the "plop" sound that you get when dialling, and would much prefer to have a proper (?) dialling tone, e.g. where each key has a different note.
Try as I might, I can't find any easy way to switch to dial tones like I had on my old SE X10, so unless someone out there's got a solution, I can see I'm going to end up switching off dial noises altogether.
+1
Why hasn't anyone answered this question? It's important to have these tones when calling an automated system.
Verizon
32gb
gentleart said:
+1
Why hasn't anyone answered this question? It's important to have these tones when calling an automated system.
Verizon
32gb
Click to expand...
Click to collapse
It does actually send the correct tone down the line, you just hear a different one locally. It's hard to say if there is an easy fix, because there should be a sound assignment to each key in the Phone apk or related, and if Sammy has replaced them all with a single one, it might not be so easily modified to point each button at a seperate sound.
All I can suggest is to get an alternative dialer, perhaps the AOSP one?
When I called my bank, it didn't work. I switched from short tones to long ones and it still didn't work.
If I can find a different dialer I guess I'll try it.
gentleart said:
When I called my bank, it didn't work. I switched from short tones to long ones and it still didn't work.
If I can find a different dialer I guess I'll try it.
Click to expand...
Click to collapse
That's very strange because it's practically a critical feature that the phone dialer can send DTMF tones. I use it regularly myself so I can promise you that it does work for some of us, it could very well be a problem with your bank. Try rip the phone apk out of a Cyanogen build or similar if there are no dependencies, or if you get a dialer from the play Store pay careful attention to how reliable it is and its permissions, just in case.
I asked this question weeks ago and no one has come up with any 'fix' for it...
The tones you hear when pressing a key have nothing to do with the tones the phone sends as described.
Try calling another phone and pressing the keys, you should hear a distinction between all single tones. (If not, please have your ears checked )
Did you have a good connection when calling the bank? The tones heavily rely on a halfway acceptable connection.
If you still want to hear distinct tones, try other diallers such as Go Dialler. They might be able to do it since it's onlce purely cosmetical.
It could be a problem on the bank's end because Google Voice works.
d4fseeker said:
The tones you hear when pressing a key have nothing to do with the tones the phone sends as described.
Try calling another phone and pressing the keys, you should hear a distinction between all single tones. Did you have a good connection when calling the bank? The tones heavily rely on a halfway acceptable connection. If you still want to hear distinct tones, try other diallers such as Go Dialler. They might be able to do it since it's onlce purely cosmetical.
Click to expand...
Click to collapse
I'm going to agree with what's said here - while plopping noise IS annoying, I've not had any problems with automated "Press 1 for ..., press 2 for ..., or wait on the line and an operator will assist you" services - they all seem to work. So, the problem - for me at least - is purely cosmetic.
I'd assumed that the plop had been part of the theme that Sammy had applied to the SIII, in which case an experienced themer should be able to undo this in favour of some a bit less crappy. Although not being a 'droid developer or themer myself (merely a user) I've no idea where to start looking for that kind of info - fingers crossed that it's in a configuration file somewhere in the system.
I have been annoyed by this also. I myself am so use to hearing dial tones, that I'm just missing the sound, and just want them back.
I found this, where a user replaced the waterdrop with DTMF tones........but its for the Galaxy s......Good news is the zip has all the tone .ogg's. Maybe someone can look and it and figure out a way to port?
http://forum.xda-developers.com/showthread.php?t=1361687
I'm also missing the well known DTMF tones and pissed about that bubbles.
"Nature inspired" concept and our device desing is very nice but this chage is absolutely stupid.
Nature don't has phones growing in trees an phone calling couldn't sound like a leaking tap.
Hope somebody was able to port this SII mod to our device...
Hi, Wizards:
I have a Galaxy Tab GT-P1000 running Overcome 3.3.1. On occasion, when all else seems quiet, the device will suddenly decide to play the /system/media/audio/notifications/12_Tweeters.ogg sound file (sounds something like a bird chirp), and I would like to find the application that causes this sound file to be played. I ran the Log Collector app (v1.1.0) and poured through its output, and that is how I determined which file is being played,
In the latest instance, the log shows:
09-06 08:40:24.230 I/MediaPlayer( 306): The actual path is:/system/media/audio/notifications/12_Tweeters.ogg.
Before that, I can see references to (306) like "KeyguardViewMediator" in the same second. In fact, there are hundreds of references to 306 within parentheses in the log, mostly involving Sensors and PowerManagerService BatteryService. But I don't see a way to trace back to the originator. (Frankly, I also don't have any indication that the '306' is important.)
How would I go about finding the reason that MediaPlayer was kicked off in the first place? (My goal is to find the application that suddenly decides to play this sound file, and to understand why it does so. After all, I'm being notified of something, right? Wouldn't it be swell to understand the reason for the notification, instead of just "Hey!" ?)
I've searched for general information on how to figure out what the Log is trying to tell me, but to no avail for something like this. Is there enough information in the typical Log Collector output to determine this information? If so, where can I read up on how to trace this? If not, then what might I do to trap/identify this?
I appreciate any pointers you may have on this.
delovelady said:
Hi, Wizards:
I have a Galaxy Tab GT-P1000 running Overcome 3.3.1. On occasion, when all else seems quiet, the device will suddenly decide to play the /system/media/audio/notifications/12_Tweeters.ogg sound file (sounds something like a bird chirp), and I would like to find the application that causes this sound file to be played. I ran the Log Collector app (v1.1.0) and poured through its output, and that is how I determined which file is being played,
In the latest instance, the log shows:
09-06 08:40:24.230 I/MediaPlayer( 306): The actual path is:/system/media/audio/notifications/12_Tweeters.ogg.
Before that, I can see references to (306) like "KeyguardViewMediator" in the same second. In fact, there are hundreds of references to 306 within parentheses in the log, mostly involving Sensors and PowerManagerService BatteryService. But I don't see a way to trace back to the originator. (Frankly, I also don't have any indication that the '306' is important.)
How would I go about finding the reason that MediaPlayer was kicked off in the first place? (My goal is to find the application that suddenly decides to play this sound file, and to understand why it does so. After all, I'm being notified of something, right? Wouldn't it be swell to understand the reason for the notification, instead of just "Hey!" ?)
I've searched for general information on how to figure out what the Log is trying to tell me, but to no avail for something like this. Is there enough information in the typical Log Collector output to determine this information? If so, where can I read up on how to trace this? If not, then what might I do to trap/identify this?
I appreciate any pointers you may have on this.
Click to expand...
Click to collapse
Log Collector should give you enough information to solve the problem. I suppose one simple and quick solution you could try is go into /system/media/audio/notifications/12_Tweeters.ogg and just delete the file. If you delete the file, then when it wants to play that sound it won't be able to because it doesn't exist, and then it shouldn't bother you anymore.
shimp208 said:
Log Collector should give you enough information to solve the problem.
Click to expand...
Click to collapse
That's encouraging. Sorry I wasn't clear. Where might I find out how to read the log in such a way?
shimp208 said:
I suppose one simple and quick solution you could try is go into /system/media/audio/notifications/12_Tweeters.ogg and just delete the file. If you delete the file, then when it wants to play that sound it won't be able to because it doesn't exist, and then it shouldn't bother you anymore.
Click to expand...
Click to collapse
Hmmm... to me, that sounds like "If the fire alarm bothers you, just remove the battery." I do appreciate your reply, but that doesn't that sound to me like a good idea since I don't know the cause... I do welcome advice regarding figuring out that cause.
I had a problem with audios starting to play randomly. Googling led to many possible causes.
The only one I remember is the fix that worked for me - simply installing and running once a program available free from the market called DisableAutoPlay.
It disables the feature where plugging headphones in causes auto-playing. Mind you I wasn't doing anything with headphones when my music started randomly, but apparently there can be some intermittent hardware malfunction that makes the phone think you are plugging headphones in (perhaps limited to Samsung phones like mine IIRC... I have an Infuse).
electricpete1 said:
I had a problem with audios starting to play randomly. Googling led to many possible causes.
The only one I remember is the fix that worked for me - simply installing and running once a program available free from the market called DisableAutoPlay.
It disables the feature where plugging headphones in causes auto-playing. Mind you I wasn't doing anything with headphones when my music started randomly, but apparently there can be some intermittent hardware malfunction that makes the phone think you are plugging headphones in (perhaps limited to Samsung phones like mine IIRC... I have an Infuse).
Click to expand...
Click to collapse
Thanks. I will keep that in mind if the time comes that I need to take such action.
I'm sorry I'm apparently expressing my intent so poorly. My goal, to be clear, is to find out WHY the alarm is sounding, not to prevent it. (I reserve the right to want to prevent it in the future, but right now the point remains.)
I will try to track down the author(s) of Log Collector and see where that leads me. If I find out anything useful, I will post back here.
delovelady said:
Thanks. I will keep that in mind if the time comes that I need to take such action.
I'm sorry I'm apparently expressing my intent so poorly. My goal, to be clear, is to find out WHY the alarm is sounding, not to prevent it. (I reserve the right to want to prevent it in the future, but right now the point remains.)
I will try to track down the author(s) of Log Collector and see where that leads me. If I find out anything useful, I will post back here.
Click to expand...
Click to collapse
Id also look into using logcat to try and solve your problem take a look at this guide to reading and writing logcat files.
Reading and Writing Logs in Android
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 ...