To all Wizard gurus,
I have recently flashed my G3 Wizard (T-Mobile MDA) with Windows Mobile 6.1 Octavioi ROM. I am very happy with the ROM, but I'm having a problem with others hearing me.
I think I've read somewhere here that you can adjust your microphone by modifying the registry or something, but I've been searching for literally hours and can't find any threads on this topic.
Also note that background noise seems to be OVER-emphasized while my voice seems very UNDER-emphasized.
PLEASE HELP; it would be great if I could get these settings adjusted and start really enjoying my phone.
For the sake of future searchers, I'm including some keywords below:
mic microphone adjust adjustment adjusting gain sensitivity volume increase decrease mouthpiece
hey, try to use battery-status and set application based overclocking
and put there phone and use 195MHz
i find that when i used overclocking a lot of people have problems to hear me clearly - and that option in b-s helped me - give it a try.
***UPDATE***
It looks as if I need an 'extended' version of this application to do application-specific overclocking. Does anyone know if Battery Status Extended is available for or compatible with the Wizard (running WM6)?
pleasehelp said:
Thank you for the tip; I downloaded Battery Status and installed it, and I have it actively working on my system, but for some reason I cannot access application-specific clock settings.
Can you either tell me how to do this, or show me a thread where I can find this information?
Thanks a mil...
Click to expand...
Click to collapse
pleasehelp said:
I think I've read somewhere here that you can adjust your microphone by modifying the registry or something, but I've been searching for literally hours and can't find any threads on this topic.
Click to expand...
Click to collapse
The registry changes suggested in this thread worked for me:
http://forum.xda-developers.com/showthread.php?t=256734
Specifically,
Originally Posted by smartphoneinfo
I found some keys. The keys:
\\\registry\HKLM\Software\HTC\AUDIOGAIN(x)\
Speaker uplink volume
Headset uplink volume
Where (x) is nothing or 0, 1, 2
My speuker uplink volume was set at 26, I change that with 50, I think my speaker goes a bit harder, but I'm not sure..
Does anyone know if it really works, or has different techhnics?
Click to expand...
Click to collapse
i've had problems with microphone in my wizard. basically, people complained, that they can't hear me very well. i also found these registry keys, did some tests and changed RECEIVE_UPLINK_VOLUME and EARPHONE_UPLINK_VOLUME values to CC. after that change, microphone sensitivity got better and didn't receive any more complaints.
Click to expand...
Click to collapse
Also looking for the same fix. It seems most people replied for a volume adjustment for the output and not mic adjustment for input being over sensitive (also causes feedback/screeching). Thanks.
"I CAN'T GET TO MY PHONE BEFORE IT GOES TO VOICEMAIL!" Sound familiar?
This thread is to discuss and discover/provide work-arounds (and potentally solutions) for the lag time between the initial ring from a caller and the incoming notifications on the android phone. Since there are other ways to make it possible to answer a call before it gets forwarded, other perspectives/ideas/questions/discussion are welcome here as well.
(Since I started the griping here I figure I better follow up.)
After a day or so of being opened, there are already several things we can do to help our phones ring faster posted in this thread. If something is confusing to you, please ask. If you click on the username of a post, you have the option to send a personal message. Unless you are darn sure other people have your question, please use this option. If it turns out your question would better suit this or any thread, you can paste your PM into the thread at any time.
I have to say this so I can rail on people: no matter how many Opening Posts say READ, READ, READ, the people who consistently don't read the thread haven't read the Opening Post, either. Don't be one of those people. The rest of us resent you for cluttering the thread, consequently creating even more clutter because there's too much crap for other people to read. We think you are being ignorant and selfish. This entire forum is public information; try to keep in mind your potential future boss might be checking this out to see how useful you might be in their workplace. So this, though probably not read by its intended audience, reserves for me the right to be even b****ier
In case anybody is inclined to test it, I already discovered that the phone doesn't ring when it's powered down....
The phone Prioritizer, combined with using ogg format, seems to do the best or me: I can't find it anywhere else. If I've posted this wrongly, please holler.
There was discussion going into the cupcake build about the latency increasing. I can't speculate on the cause of the latency, but it seems to have been going from the first OEM builds.
Delay in phone ring
Delayed phone ring (and even more delayed screen activation and caller ID) on incoming calls. Speaking for myself, callers hear a couple of rings before my ringtone starts to play. And there is another couple of seconds of delay beyond that before the screen lights up and the caller ID comes on.
I have been having this problem for the past, oh, ten or twenty updates. I have tried MANY things to fix it. If you hadn't already said that you always reinstall the radio when you flash, I was going to try that next in my quest for a solution. This ringtone delay problem is currently my number one irritation with my G1, and is at the TOP of my list of issues that I hope Cyanogen will address and conquer.
I have tried "renice -20" on the phone program, with no improvement. I have tried moving ringtones2SD from fat32, with no improvement. I have tried reformating all my custom ringtones as OGG, with no improvement. I have tried installing and uninstalling a variety of programs, with no improvement.
I am certain that Janis and I are not the only people with this problem. I have seen it mentioned by a lot of people in a variety of threads. I am glad to see a specific thread about this particular topicl If anyone has figured out a solution, please speak up. If no one has, perhaps reports from enough people will serve to convince developers to look into it more deeply. Anyone else have feedback?
I myself am curious to kno if there is any way to work on this. I have been a happy Rom switcher and each Rom has always given me 2 ring delays. The way I worked mine to get close to 1 ring is to constantly use a task killing APK, which I may add is tedious, and making sure I'm clocked 245min 584max
After I moved my ringtones from sdcard/audio/ringtones to sdcard/media/audio/ringtones a prescribed by Cyanogen when he originally took all the ringtones out, I had to re-pick my ringtone, as I would expect.
The odd thing is I also have to do it when I add (a) ringtone(s) to the folder or delete one or more. Can anyone shed any light for me on how the system/phone app references ringtones? Why would it lose a ringtone to reference just becuase I added one to the folder it's in?
How to test, or one way to do it
I use the home phone or skype, that way I can hear how many rings are actually happening for myself, count actual seconds (ear to the phone, eye on the clock), and I can see what order things happen. No one else,except you guys, has to bear with my hare-brained methods, either.
The last time I tested, the ring actually started before the caller ID popped up, but that was a first for me. Nothing happened until about the end of the second ring from the home phone.
Now I'm running Compcache 32mb, Linux partition swap 128mb, CPU 528/245.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
I don't think you will get rid of the 2 rings on the other end before the phone rings. That is probably just the network finding your phone. However, I have had issues with my phone vibrating 2 or 3 times before the ringtone would start playing. I turned off vibrate and it helped. Then I turned it back on and disabled Missed Call. Now there is barely one vibrate before the ringtone starts playing. I'm turning off Missed call until they have an update for it.
I also found that the battery status widget causes a huge delay if you have it set to update as soon as it changes. It checks everytime the phone comes on and that slows things way down. I set it to update every 60 seconds and it still had some delay but not as much.
bout time
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
SamCookD405 said:
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
Click to expand...
Click to collapse
This isn't a ROM problem, it is a phone resources problem. There is something dragging your phone down. It might be different for each one of us having issues.
Ditching userinint.sh
I rm'ed user.conf and userinit.sh to use Cyanogen's default compcache and default CPU scaling. I re-downloaded Swapper and set up to use my 128mb (overkill) linux partition.
I got lights & vibrate at the end of the first ring, I got caller ID and ring just about halfway into the second ring.
Using the attached user.conf I didn't get ring or caller ID until the end of the second ring, sometimes after.
So I installed missed call (donation) and maxed it out. No change. Still getting first response at the end of the first ring, and ring and caller ID about 1/2 way into the second ring.
Maxed out my CPU at 528/528 with SetCPU. Got about .1 of a second advance. It starts to ring and gave me caller ID about 1/4-1/3 of the way into the second ring. Hard to tell, but a bit earlier than 1/2. The second and third time I tried it, it wasn't as fast. Caller ID came up just barely into the 2nd ring, but ring didn't start until the end.
I think the first ring is network time. For the duration of it, I'm guessing, the call isn't at my G1 yet. This sucks.
I think the phone app is set to vibrate and light the phone first, and leaves time for this to happen. It may be because it's the fastest way to alert the user, since looking for ringtone, handling it and sending it can (doesn't always) take some time, it just uses the reliable method and then triggers the less reliable, already slower ring process.
So maybe Cyanogen, or anyone who's familiar with it, can see if this ring vs. vibrate lag can be eliminated. I'd rather have the phone look for a ring first.
But, if you need to get to calls that quickly, set it to vibrate for now?
I downloaded the ogg ring package from the custom userinit thread. Trying that next.
This doesn't contribute anything to the thread at all (except maybe encouragement) but I'm glad someone is bringing this annoying "feature" up for public discussion.
I keep myself updated with CM and kspec oreo as a theme. As it is right now, I get one ring and the call goes to voicemail. The caller ID display actually lights up after the call has been forwarded. Hope the culprit (if there is just one) is found soon.
There has been a parameter on some of my previous phones called slot index. It was available through a keypad menu, it set how often the phone polled the tower. It sped up the ring responce dramatically.
Tried the ogg files, woohoo!
I've got my CPU set to 528/384 with SetCPU, Linux partition swap 128mb with Swapper (I can set them on the fly without rebooting), and used the ogg files in media/audio/ringtones, and I get ring and caller ID at or before the beginning of the second ring, a split second after the vibrate started. I tried messing with CPU speeds, and it does seem to make a difference as to when the ring actually sounds. I'd say about 1/2 a ring between 245 idle and 528 idle with 528 max for both.
I also have my frequency scaling at 16. So I think that means if 16% of my CPU power is being used, it hops it up from min to max. OK, maybe not 16%, I don't know how the numbers translate, but 16 is low, so I'm running at 528 when a squirrel farts outside.
I have BatteryLife and Missed Call enabled.
So there's the pause after the first ring to deal with, but I really don't think it's the phone after this. maybe we need to join forces and barrage T-mobile with complaints. I mean, why have the ringing on the calling end start if the network isn't connected?
Well, at least we won't ever have to worry about appearing too desperate.
2 or 3 bars, so my signal isn't that great. I'm in the suburbs (not that I love it, but it's where I am).
I'd be very curious to find out if others who have their CPUs running high and are using ogg files are getting a different response. I'm also going to try it in different locations.
I am going to suggest to Cyanogen to include the ogg fles as part of his add-on collection.
Face of Ring
I think I may uninstall this, even though I love it. It bumped the ring to after the caller ID. Caller ID still popped up during the pause after the first ring, but the ring and vibrate didn't happen until mid 2nd ring.
(I'm using rings to measure because 1. it's easier 2. the rings/pauses are shorter than a second 3. in large part it's the caller experience we're concerned about. I don't have a stellar chronometer handy, either.)
Well, thanks for starting this thread, Janis. It's a common complaint across all builds. I've grudgingly resorted to calling my phone after every reboot, just to try to keep the ringtone and I'm guessing Phone.apk?? in memory for as long as it will stay in there. That definitely helps for awhile. I know we're trying to make these phones more into computers, but they're still phones and as such calling and communications should be the main priority. I've converted to .ogg, however they are larger files than the .mp3's I converted from. Maybe I should have used a smaller bitrate. Anyhow, it doesn't seem to make much of a difference. I've tried placing them in /sdcard/media/audio/* and /system/sd/media/audio/*. Does not seem to make much of a difference.
I want a hardware hack to increase the RAM...I hate the trade off we're facing. Losing physical keyboard to obtain greater memory. Or make a "Dream plus" with more RAM. I'd even be happy with just a slight increase in internal storage or none at all and more RAM. The devs here have done wonders with the hardware provided, and the implementation of apps to sd has really made this seemingly poor thought out device (in areas), one of the best. I remember, before I was brave enough to attempt apps to sd, having to decide which app to uninstall, just to make room for one I might want more. Seems like ages ago. While I'm reminiscing, I'd like to give a retro shout-out to Lucid and MarcusMaximus who were pioneers in this area and others.
Sorry, about the tangent...but we've made great strides on the computer end of this device...let's regress, so to speak, and make the phone the primary function, hopefully without backsliding on progress we've made on our phones as a mobile computing device.
EDIT: I've also uninstalled "AutoLock" for this reason, because I'd read somewhere that this may be the culprit...I may have seen positive results, or possibly just placebo.
I have the app "Caller Lookup" installed and have noticed tha that app comes up before caller id and or the ringtone. Its there after 1 or 2 vibrate pulses.
make sure T-mobile, or whomever, has your time-before-forwarding maxed
My poor 74-year-old mom was having a heckuva time getting to her phone in time. As per the instructions from a Tmobile service rep, we punched a # and some digits and got a 65 second ring time. This was a year ago or so. I was told that same week that if my OS on my WinMo phone couldn't do it, there was no way they could (there's a way to set it in WinMo), which was BS.
I know it takes network time/space/bandwidth to let it ring, and it's not paid time. I wonder, not to be a rabble rouser (heh), if we kept calling them, maybe hundreds of us if we could get it going, and made them spend more money on customer service than that bandwidth, if they'd bump that.
Anyone?
So I'm getting back into the smartphone game again after being away awhile and I got a Nexus S today basically free of cost, practically brand new without a mark on it. Previous owner had it as a temporary phone during a warranty repair job of his primary phone and when he picked up the repaired one they said he could keep the Nexus S (wish I could get that lucky).
Anyway, while I know there are a ton of different ROMs available for this fantastic (albeit older) device, here's what I really want and I'm not sure it's possible. I've used CM in the past on several devices and one of the things that I always loved first and foremost was the ability to change tracks during music playback by holding the volume up/down button(s) (long press as a short press adjusts the volume). Now, I'm not a coder, not a developer, not a ROM builder, etc - I basically enjoy the work of others provided by their ROMs and so on.
This time out I've decided to try and stick with a pure stock ROM (which I'm not sure of at the moment, the NS has 4.1.2 on it but I plan to do testing with the factory 4.0.4 and 4.1.1 images as well just to see what's going on). Since those are factory images they're obviously not rooted so I can use WugFresh's Nexus Toolkit to handle the rooting for me.
So here's my question: is the ability to use the volume controls for changing tracks during music playback (with the screen off) a ROM-specific thing or is it kernel-specific - I've never been able to find an accurate answer to this question and I've asked it several times on different forums over the past 4+ years and still nothing of substance has ever been given as a response.
I know that some music players advertise they can do it (I've seen PowerAMP mentioned a few times but it just doesn't appear to work for me, ever, on any device). Again, I'd prefer to stay stock as much as possible, save for rooting the device, and then hopefully find out either a) I have to use a custom ROM with this feature enabled in it, or b) it's kernel related and I can just install a custom kernel which I can tolerate since it'll help on several aspects.
Sorry to make this so wordy but that's just how I am.
tl;dr version: I want to remain as stock as possible, with root only, and be able to change tracks during audio/music playback with the screen off by using the volume control buttons. Is it possible with just installing a custom kernel (given this Nexus S is bootloader unlocked) or not?
Hopefully someone can offer an answer that'll put a smile on my face but, if not that's fine too I suppose, I can just drop back to CM10 (4.1.1) stable and stick with it, not sure 4.1.2 really does all that much to improve things and 4.2.2 apparently is just too big for the limited 512MB of RAM in this NS to be smooth sailing.
Thanks...
This feature is build in with the app "Uber Music" its a setting called "Use volume buttons to control media"
It works great and its awesome if you don't mind putting in a few dollars to get the app
Cheers,
Luke
UberMusic looks nice, sure, but it doesn't do what I was hoping it would (and was suggested in the post above). The setting preference says "Enable headset controls" and I already have that ability: I have a cord from Apple earbuds where I removed/desoldered the original factory earbuds (because they're crap) and then replaced them with a pair of Koss IEMs that I like. So even though the cord looks like I'm using Apple earbuds I'm not.
Having said that, I can already control the Play (single click), Pause (single click), and Next track (double click) functionality, but obviously the dedicated volume buttons on the remote don't work for whatever reason. The Nexus S has a proper TRRS jack but it seems like no Android phone makers care enough to actually allow for such volume control through that jack. And the typical triple click Previous track functionality doesn't work either, sadly (and that's with any remote I've ever tried, even earbuds/IEMs that claim to work or are "designed for Android."
So again, I'm trying to control changing tracks (Next and Previous) with the volume rocker on the phone itself and when the screen is off, that's it. Since the phone is in my hand 99% of the time and my thumb is on the volume rocker, it's infinitely more efficient to change tracks with a slight movement of the thumb than trying to grasp the inline remote and double click or whatever.
Sure is odd why this question is so difficult to get an answer to over the years...
Most custom roms support this. It's not a kernel thing afaik. You may be able to find a mod to get it working on stock. It seems like I've seen it before in the ns4g themes & mods but I could be wrong.
As for triple press on the headphones, it's always worked for me with poweramp on multiple headphones.
Sent from my Nexus S 4G using Tapatalk 2
Feature 1:
Lockscreen widget for music player lost the "Previous" button. I can skip a song, but I have to unlock the phone and navigate to the now playing screen to restart a track or go back to a previous one.
This was available in 4.4.4. It's a bit annoying, specially when you're driving.
Feature 2:
This might actually be a bug...
While playing music, incoming messages/call notifications do not play. The music merely lowers in volume. Again, while driving, I might not notice the 1 one second drop in music volume for a message, and sometimes I even miss a call.
On another note, I believe feature wise, Kitkat was the best(pratical and feature wise) rom we had. Had a few non Omni-related issues with Lollipop, most of them minor but still annoying.
Lockscreen is one for example. The default, unprotected Lollipop lockscreen is too easy to unlock. I found myself running out of money a few times because firefox was accidentally launched while the phone was in my pocket. Or sometimes the phone app calling random people.
[AltaiR] said:
Feature 1:
Lockscreen widget for music player lost the "Previous" button. I can skip a song, but I have to unlock the phone and navigate to the now playing screen to restart a track or go back to a previous one.
This was available in 4.4.4. It's a bit annoying, specially when you're driving.
Feature 2:
This might actually be a bug...
While playing music, incoming messages/call notifications do not play. The music merely lowers in volume. Again, while driving, I might not notice the 1 one second drop in music volume for a message, and sometimes I even miss a call.
On another note, I believe feature wise, Kitkat was the best(pratical and feature wise) rom we had. Had a few non Omni-related issues with Lollipop, most of them minor but still annoying.
Lockscreen is one for example. The default, unprotected Lollipop lockscreen is too easy to unlock. I found myself running out of money a few times because firefox was accidentally launched while the phone was in my pocket. Or sometimes the phone app calling random people.
Click to expand...
Click to collapse
2 sounds like it might be a bug, and it might be device-specific - you don't state which device you have.
It's not something I'd notice in my daily routine since I have an XM receiver in my car.
Entropy512 said:
2 sounds like it might be a bug, and it might be device-specific - you don't state which device you have.
It's not something I'd notice in my daily routine since I have an XM receiver in my car.
Click to expand...
Click to collapse
Thought so too...guess I'd best report it in the device specific thread.
Own a Nexus 5, as mentioned in my sig. I guess these days sigs are so full of meaningless stuff that we don't really bother checking em out anymore. Iirc, there was a guide somewhere teaching how to make a useful one.
[AltaiR] said:
Thought so too...guess I'd best report it in the device specific thread.
Own a Nexus 5, as mentioned in my sig. I guess these days sigs are so full of meaningless stuff that we don't really bother checking em out anymore. Iirc, there was a guide somewhere teaching how to make a useful one.
Click to expand...
Click to collapse
I stopped including my devices in my sig ages ago because it was frequently inaccurate/out-of-date and I always assume someone else's sig is wrong/don't even look at it for that reason.
Does it happen on stock? I'm not sure if this is a 5.x thing in general, a device-specific bug, or an Omni bug due to some of @maxwen 's volume control tweaks . I won't be able to experiment with it until I get back from vacation in mid-late September.