Newroots 3D 2.03 Dialer issue - Verizon Droid Incredible 2

Too new to post in the dev forum, but hopefully someone from the adult table will be lurking over here and be able to help.
I work for a global company, so many of my contact phone numbers are formatted with at +1 XXX-XXX-XXX. Never been an issue with any of Newroot's earlier ROMS, or even with the earlier releases of this one, but now whenever I try to call one of those numbers I get a fast busy/call failed. When manually dialing without the +1, goes through no problem. Please tell me there is a fix other than manually revising thousands of phone numbers.

unregistered4 said:
Too new to post in the dev forum, but hopefully someone from the adult table will be lurking over here and be able to help.
I work for a global company, so many of my contact phone numbers are formatted with at +1 XXX-XXX-XXX. Never been an issue with any of Newroot's earlier ROMS, or even with the earlier releases of this one, but now whenever I try to call one of those numbers I get a fast busy/call failed. When manually dialing without the +1, goes through no problem. Please tell me there is a fix other than manually revising thousands of phone numbers.
Click to expand...
Click to collapse
You might want to go over to MikMik and ask this as i do not know if he checks this section. But from what i see is that with this version he has updated it to a world phone. this is something that he is still testing, so that might be the core of the issue. You might want to throw that out on in the Bug section of MikMik to see if it has something to do with that.
"Enabled world phone[should work with gsm kinda like cm7 you wont be able to switch back and forth like our stock rom but i think gsm will work... if someone will test and let me know that would be great"
Just a thought...because i dont see why it wouldnt work if you can dial it regularly but not when using your contacts.
Good Luck!

Related

Keyboard Numbers during phone calls - ATT WM6 ROM's

Has anyone been able to figure out why the ATT roms are experiencing the numlock situation when on a phone call. This seems to be the only issue I have experienced on this ROM but is quickly becoming a showstopper.
Number keys stuck while in-call. Doesn't seem to be resolved yet per the Pro's
"8/04/2007 Originally Posted by schaps
Not yet, this problem also occurs on official WM6 ROMs so it doesn't help me to focus the problem.
But for sure this issue is not caused by the keyboard driver."
Put me in the list of people wanting a fix for this. I hope someone figures it out. I often like to text while using my bluetooth, and I don't enjoy having to pull out my stylus to do so.
Just wishing the talented developers some luck in figuring out the problem!
Add me to the list too ... i've looked all over but hadn't found the fix. I remember seeing it somewhere when doing my WM5 ROM upgrade (a long time ago).
Any progress on this?
I'm using Shamanix's Ultimate 1.0.
I don't need to send SMS while calling but I've got the device locked and if I need to check the Calendar during incomming call for example, I need to type my password. Would be really nice to type on QWERTY instead by stylus.
thx
This has been Fixed In More than One Rom....TNT,Vp3g's plus other Roms... I"m going to be Compiliing a List soon of Roms that do and Do not have this Fix.... Certain Schaps Rom also have this Fixed as well but not all...sometimes either he forgets or They Fix interferes with other things onthe ROM not sure....
I can definitely vouch that it works correctly in vp3g's rom.
Would be nice to know what is causing this and how exactly they managed to get it to work so we can fix this on our ROMs.
the fix is already there.
http://forum.xda-developers.com/showpost.php?p=1562185&postcount=63

[Q] New ROM Issue Help Requested

I've been reading myself silly trying to figure this out & my attempts at Searching haven't helped, probably because I'm not fluent enough to use the correct terms. In spite of having this device for several months, I've never learned as much as I'd like. Anyway . . .
I finally flashed the newest stock ROM from HTC several days ago. The process seemed to go fine with one exception: I keep getting a notification that I have a new Voicemail when I don't. I check -- no new Voicemail. I Dismiss, but the the notification keeps coming back periodically. Suggestions?
Other than that, things seemed to go smoothly, and I started slowly getting things back the way I like them. After reading & making sure I understood (or so I thought), I installed the .NET 3.5 Framework so I could use Crud Scraper to get rid of the stuff I clearly remembered using it for.
The .NET part went fine, and then I did the soft reset . . . and lost My Location on the Today screen that shows my weather. It now says I'm in Seattle, which I'm not -- I'm over a mountain range & about 350 miles east of Seattle. When I try to change the location, it doesn't find my town or anything in my area, for that matter..
The mysteriously (to me) reappearing Voicemail Notification is bad enough, but I really rely on the weather, particularly this time of year, and it's driving me crazy that I can't figure this out. Suggestions?
TIA
Did you try looking at the several threads on this ROM in the Rom Development forum? There's a fix in one of them for this problem.
For which problem? And, do you have any idea what thread?
And, yes, I did look in the thread I found (New ATT Tilt2 ROM) -- I believe I read every post before I flashed the latest ROM, even though much of it was over my head. That's where I learned that I had to install .NET 3.5 & reboot before CrudScraper would work.
I recall several people mentioning that the My Location worked flawlessly & how great it was having the location, and I read where one or two people seemed to be having the same weather problem I'm having, but I didn't see an answer. I read in one of the forums that there seems to be a bug (although not confined to the latest ROM) in certain parts of the world, and I read a thread where there seemed to by a problem with My Location in a cooked ROM that might or might not have been related to GPS not working. I read something else where My Location wouldn't work with 3G, only with Wi-Fi, so I tried that, even though My Location was working just fine after I flashed to the latest ROM -- that didn't help.
So, it's not like I'm asking because I hadn't already tried to find solutions myself. I'm not doubting that there are answers to both of my issues but rather that after spending several hours over the weekend trying to find the solutions, I've been miserably unsuccessful. Otherwise, I wouldn't have asked.
sslund said:
For which problem? And, do you have any idea what thread?
And, yes, I did look in the thread I found (New ATT Tilt2 ROM) -- I believe I read every post before I flashed the latest ROM, even though much of it was over my head. That's where I learned that I had to install .NET 3.5 & reboot before CrudScraper would work.
I recall several people mentioning that the My Location worked flawlessly & how great it was having the location, and I read where one or two people seemed to be having the same weather problem I'm having, but I didn't see an answer. I read in one of the forums that there seems to be a bug (although not confined to the latest ROM) in certain parts of the world, and I read a thread where there seemed to by a problem with My Location in a cooked ROM that might or might not have been related to GPS not working. I read something else where My Location wouldn't work with 3G, only with Wi-Fi, so I tried that, even though My Location was working just fine after I flashed to the latest ROM -- that didn't help.
So, it's not like I'm asking because I hadn't already tried to find solutions myself. I'm not doubting that there are answers to both of my issues but rather that after spending several hours over the weekend trying to find the solutions, I've been miserably unsuccessful. Otherwise, I wouldn't have asked.
Click to expand...
Click to collapse
For the My Location feature, only part of the service is understood. For the most part, the location is determined by the cell towers your device connects to. It depends on where you are as well as the signal strength. Sometimes the request is not sent or received to/from the tower(s). It is more accurate usually when 3G is turned off. The alternative is to add your city manually. If the location servers can't figure out where you are, then it won't work.
Normally the stock ROMs fix this and work wonderfully after flashing. The best solution to this is to turn off 3G to get a fix or find your city manually.
cajunflavoredbob said:
For the My Location feature, only part of the service is understood. For the most part, the location is determined by the cell towers your device connects to. It depends on where you are as well as the signal strength. Sometimes the request is not sent or received to/from the tower(s). It is more accurate usually when 3G is turned off. The alternative is to add your city manually. If the location servers can't figure out where you are, then it won't work.
Normally the stock ROMs fix this and work wonderfully after flashing. The best solution to this is to turn off 3G to get a fix or find your city manually.
Click to expand...
Click to collapse
I'm feeling really stupid here, but being a glutton for punishment, I'll keep trying.
Is it possible that maybe there was something wrong with the towers here that just happened to coincide with the soft reboot after installing .NET? The reason I ask is that My Location is now correct. Yay! That would be just my luck: bad timing.
Any suggestions about the incorrect Voice Mail notification? It for sure comes back each time I power up the phone. It seems to me it also reappears at other times, but I'm not positive about that -- I'm going to try to pay better attention.
sslund said:
I'm feeling really stupid here, but being a glutton for punishment, I'll keep trying.
Is it possible that maybe there was something wrong with the towers here that just happened to coincide with the soft reboot after installing .NET? The reason I ask is that My Location is now correct. Yay! That would be just my luck: bad timing.
Any suggestions about the incorrect Voice Mail notification? It for sure comes back each time I power up the phone. It seems to me it also reappears at other times, but I'm not positive about that -- I'm going to try to pay better attention.
Click to expand...
Click to collapse
Make sure to install .NET CF 3.5 to the device and not the storage card. You'll then need to restart, if it doesn't ask you to do so. You then need to force it to use 3.5 over 2.0. Use a registry editor and navigate to HKLM/Software/Microsoft/.NETCompactFramework. Change the DWORD data of entry 2.0.7045.00 from 1 to 0. Then change the DWORD data of entry 3.5.7283.00 from 0 to 1 and then reset. This disables 2.0 and enables 3.5.
For a decent registry editor that can be used from the PC side, check out CERegEditor if you don't already have an editor of choice.
For the voicemail problem, there are two known solutions. You can either have someone call and leave you a voicemail. You would then check it and delete it. You can also simply call your provider and have them reset your voicemail account. Either one should work.
If neither of those options works for/appeals to you, you can give this a shot. There are no guarantees that it won't come back after a soft reset, though. Using a Registry editor, navigate to the following keys:
HKCU\System\State\Messages\vmail\Line1\Unread
HKCU\System\State\Messages\vmail\Line2\Unread
HKCU\System\State\Messages\vmail\Total\Unread
There should be a value name "Count" with a REG_DWORD value
Change value to 0 in decimal or 00 in Hex.
It should remove voicemail notification icon from the taskbar.
cajunflavoredbob said:
Make sure to install .NET CF 3.5 to the device and not the storage card. You'll then need to restart, if it doesn't ask you to do so. You then need to force it to use 3.5 over 2.0. Use a registry editor and navigate to HKLM/Software/Microsoft/.NETCompactFramework. Change the DWORD data of entry 2.0.7045.00 from 1 to 0. Then change the DWORD data of entry 3.5.7283.00 from 0 to 1 and then reset. This disables 2.0 and enables 3.5.
For a decent registry editor that can be used from the PC side, check out CERegEditor if you don't already have an editor of choice.
For the voicemail problem, there are two known solutions. You can either have someone call and leave you a voicemail. You would then check it and delete it. You can also simply call your provider and have them reset your voicemail account. Either one should work.
Click to expand...
Click to collapse
Many thanks! For the Voicemail, I used method one, and it worked
And, thanks for the instructions (and the reg edit program suggestion) to force use of .NET CF 3.5 because I missed that part -- yikes.
I'm on a dedicated mission to cut down on the elecronics I have to carry around, so I need to learn more about the features of the Tilt2 because if I can just figure things out (which I've not forced myself to do), the Tilt2 will, I think, be able to replace my PDA & iPhone.
Anyway, thanks again for your help!

[Q] Rebooting on NO network-Logcat

Guys, I am having this problem of random rebooting. I first thought it was random but then noticed that whatever ROM I use, this reboot happens when network signal is lost.
Now i read every thread and discussion google could give me on this problem but cant seem to figure out how this happens. I wanted to substantiate my find, hence ran logcat for few hours. Now i cant seem to understand what it means.
Can anyone please take a look at the attached text file or reason out how and why this happens. Is there a pattern I am missing?. All i notice is that my phone vibrates in my pocket after an hour when it is preparing the SD card after a reboot. Thats it
Thanks in advance.
Someone
Sent from my ME525 using XDA App
OK I found that defy is rebooting on no network and I was able to replicate the same situation. Is there any fix to this issue. Can anyone look into the code and tell me a tweak where the phone reboots because there is very less or no signal. It happens even if phone is kept in 2G/3G/Automatic.
Here is similar thread in motorola support forums
https://supportforums.motorola.com/thread/40973?start=0&tstart=5
Have noticed posts about this -- and in fact it's not restricted to Defy by any means, though overall not that common. Even the Nokia N8 forums occasionally mention the problem. The most successful cure seems to be swapping out the SIM. This does not appear to work for everyone, but generally people are so imprecise on forums it's really hard to know if they just pulled a SIM from another phone (so, being as old or even older than the one they were using), or used a new one. So, if you have not already, I would get a new SIM, "approved" by your carrier and try it. Otherwise I would return the phone.
Thanks mate. Yes I read a lot about sim being changed but no where did I see it being solved. I have spoken to motorola support and plan to send it next week. Anyway I will change the type of sim once to see if it makes a difference. I hate my phone being ripped open here because I have very less confidence in these authorised centres who deal with every damn phone.
Thanks again.

Speech-to-text problem in new OTA 4.24??

Has anyone noticed that in the new OTA 4.24 that the speech-to-text function has become worthless/unusable? Worked fine in Froyo, but now speech-to-text is borked in GB????!!?!?! Has anyone found a fix?
Let me clarify. I'm using essentially the stock OTA rooted and deodexed. Perhaps the trouble came with the deodexing, I am unsure. Anyone running a 4.24 based deodexed ROM having trouble? You hit the mic icon, speak, and it basically acts like it didn't pick up any sound.
Ive been on the OTA since it came out and I have had no problems with this function. I use it frequently to send text messages should I happen to be driving. With the exception of the occasional misunderstood word, i never have problems. I use it to search the web, to navigate, all without consequence.
Perhaps rather than bashing the entirety of this function and assuming there is a fix for something that may only be your problem or your configuration, you could provide us with some examples of what youre trying to accomplish/say and what the end result is?
usafmaverick said:
Ive been on the OTA since it came out and I have had no problems with this function. I use it frequently to send text messages should I happen to be driving. With the exception of the occasional misunderstood word, i never have problems. I use it to search the web, to navigate, all without consequence.
Perhaps rather than bashing the entirety of this function and assuming there is a fix for something that may only be your problem or your configuration, you could provide us with some examples of what youre trying to accomplish/say and what the end result is?
Click to expand...
Click to collapse
Ha...this is hilarius...a Junior member with 14 posts is trying to school a Recognized Develepor. I am pretty sure he doesn't have a config issue. I have had the same issue myself but only while driving, really wierd.
Steely man how are ya!
I have also not had any speech to text issues and I am completely unrooted s on and all. No wayback home yet...
does it always not work or only in some applications.
"This works written by voice to text"
Hehe
Sent from my PC36100 using Tapatalk
tommytomatoe said:
Steely man how are ya!
I have also not had any speech to text issues and I am completely unrooted s on and all. No wayback home yet...
does it always not work or only in some applications.
Click to expand...
Click to collapse
It doesn't work for **** in any application. You hit the microphone and the pop-up windows comes up as normal and says speak now, but unless you literally yell at the phone it doesn't pick up anything.
I had an issue with no speech to text on the previous version of Fresh, finally updated to the 4.2 today and the problem went away.
Dunno.
the 14 post guy does have a valid point. The amount of posts you have on this forum mean NOTHING on how smart you are. lol. sorry guys. but it is true. for example, just because someone has worked for IBM for 20 years doesn't make him knowledgeable on any part of IBM. Just means someone was stupid enough to pay him for 20 years. lol
But need exact examples of exactly what's going on. Maybe when you trained your phone, it lost those settings after the update? retrain it.
REMEMBER EVERYONE, if you're saying "offensive" words on it, by default it blocks it.
If the personalized recognition is unchecked, then the settings didn't carry over from one to another. WHICH GUESS WHAT! THEY DIDN'T! HAHAHA. checking mine now, and all the settings didn't stick. also, the training for the skype didn't make it over too which has been messing up my writing on this phone.
runcool said:
the 14 post guy does have a valid point. The amount of posts you have on this forum mean NOTHING on how smart you are. lol. sorry guys. but it is true. for example, just because someone has worked for IBM for 20 years doesn't make him knowledgeable on any part of IBM. Just means someone was stupid enough to pay him for 20 years. lol
But need exact examples of exactly what's going on. Maybe when you trained your phone, it lost those settings after the update? retrain it.
REMEMBER EVERYONE, if you're saying "offensive" words on it, by default it blocks it.
If the personalized recognition is unchecked, then the settings didn't carry over from one to another. WHICH GUESS WHAT! THEY DIDN'T! HAHAHA. checking mine now, and all the settings didn't stick. also, the training for the skype didn't make it over too which has been messing up my writing on this phone.
Click to expand...
Click to collapse
Thanks, but I'm not a dumbass. Perhaps you should look at the threads I've created before providing any further commentary.
I don't see anywhere in this thread where I had a problem with 'training' 'offensive words' or any other 'settings' as you have mentioned. Please read more carefully in the future and refrain from posting unless you have an answer to the question posed.
Mine works if there is no back ground noise but if there is the slightest noise forget it it just says no voice heard my wife also has the same problem. But with here Russian accent it never gets the words right anyway. At least I know I'm not the only one.
Sent from my PC36100 using XDA App
I seem to only have problem while using it in my messenger app. That being said, I am using Swype and just chalked up my problems to using that keyboard because it works fine with the voice search app?
pennie77 said:
Mine works if there is no back ground noise but if there is the slightest noise forget it it just says no voice heard my wife also has the same problem. But with here Russian accent it never gets the words right anyway. At least I know I'm not the only one.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Exactly the problem, it acts like it doesn't pick up any speech at all.
If you have this problem and have found a solution, please PM me.
This thread is now closed to prevent noobs, trolls, and flamers from clogging it up.
If a solution is found, I will post it.

My defy is gone to meet his maker

Well, I thought I'd let you guys know, my defy went to the official motorola service, now, before someone starts posting "room full of people who cares" pics, I'll tell you what where it's symptoms and maybe you can tell me if any had any similar issues.
A little background:
I'm in Argentina, and I got my defy from "Personal" ( that's the carrier) which has a 2.2.1 rom ( if I'm not wrong )
I used it for a bit and it was working so well that I didn't feel the need to mess with it.
Then, I started missing some stuff and I decided to install CM7 (rc1, v2), to see how it performed.
All good, for a while, but then, the following started happening:
- 5~8 times out of ten, sms's wouldn't go out ( and I had to re-send them until they did )
- I got delays on getting messages, and on other people receiving them.
- Sometimes I wouldn't get to answer a call, just got a "missed call notification SMS"
- Sometimes calls would drop when answering them
- FM radio started being CRAP, and getting either stuck on, or wouldn't turn on after being interrupted by other notifications.
- frecuent freezing .
I guessed it was CM7, so, deceided to get back to stock, and maybe rooting, just for kicks.
I went back to stock, but the problems kept happening.
And that's why I sent it to service.
Anyone got any similar issues?
I wounder if you had forgot ‘full wipe’?
This sounds like an intermittent connection somewhere in the phone hardware.
davenaughty said:
I wounder if you had forgot ‘full wipe’?
Click to expand...
Click to collapse
lol, of course I did wipe, I didn't got into GREAT detail of everything i did because it would be WAY to boring, but, I did tried a lot of stuff before sending it back.
I kind of know my way around android, but I don't blame you for asking, I've seen a lot of uninformed posts around here ( nothing wrong with that, not everyone has time, the patience, or the interest to spend HOURS figuring stuff out, and learning about android )
juried said:
This sounds like an intermittent connection somewhere in the phone hardware.
Click to expand...
Click to collapse
Yup, I also thought it could be either a SEVERE overage problem ( like a signal black hole in my apartment) , or a defective sim card , but I'm using my old HTC G1 for now, and it's working great, so, both of those are out.
Maybe ,your phone’s baceband does not fit for the sevice,download some app to change the baseband.
Many peope have the same problem reflected by forum in my conutry as far as i know. Most of them solve the problem by changing baceband.
(My english is so bad...but I really want to help you.)
davenaughty said:
Maybe ,your phone’s baceband does not fit for the sevice,download some app to change the baseband.
Many peope have the same problem reflected by forum in my conutry as far as i know. Most of them solve the problem by changing baceband.
(My english is so bad...but I really want to help you.)
Click to expand...
Click to collapse
If the baseband was incorrect, it wouldn't get signal at all.
Plus, the phone was bought in argentina, so the argentina stock rom for the carrier HAS the right baseband, and I still got issues.
I have no other explanation for it than faulty hardware.
Thanks, though, I know you're trying to help ; )

Categories

Resources