HELP!!! PROBLEMS with WM6 Crossbow Underground Edition???? - G4

Here's some of the problems that I am having....
1. When using phone, I occasionally cant hang up - whether I use the screen button or the pushbutton - the only thing that lets me end the call is a soft reset. Imagine!!!
2. Yesterday, for no reason, the ringtone for an incoming call played 2x faster than it should have (ie. the speed of the song was doubled)
3. Just after I notice the ringtone song issue, I tried to use voice dial, and the prompts for voice dial were also playing twice as fast, a soft reset seemed to have fixed the problem... lets see if it happens again.
4. After installing WM6 Crossbow Underground, I was having problems not getting ANY calls, so I upgraded the Radio Rom to 2.61.11 and it seemed to work, BUT then I started noticing that I was getting SOME CALLS AND NOT AL CALLS, so I switched back to 2.25.11 Radio Rom
5. Under Regional Settings > Time ...I tried to switch to 24HR mode and using it for a while, I went back in to revert back to the 12HR mode but it wouldn't let me switch back to 12 hour mode.
6. When I touch the screen to Turn ON Flight Mode (shut off the radio), and then touch the screen to Turn OFF the Flight Mode, the dialogue STILL says Turn ON Flight Mode, even though its already ON (it should change to say, Turn OFF Flight Mode).
7. I was just on the phone with someone when a text msg arrived, and it booted me off the call I was on (it hung up).
8. When on a call, I touched the Mute botton on the screen to MUTE the call, but when I tried to UNmute the call it wouldn't let me.
9. Did anyone notice that the SIMPLE LOCK (4 digits) now requires you to click on the unlock button after entering the code? WM5 didn't require this, if you entered the right 4 digits, you were in, without having to press anything else.
10. When I am on a call, and another call comes in (call waiting), I cannot answer or ignore the other call... it doesn't respond to me whether using the touchscreen or the buttons.
And there's MORE that I will post another time.
Any suggestions or solutions, to these problems?

Actually I would recomend you upgrade to Most Beautiful version
I used Underground version, and Office Mobile doesn't work too
Everything is ok here with MB (search with this and you'll find it in piratebay under applications) version

Where is the "Most beautiful edtion"?

ANTC said:
Where is the "Most beautiful edtion"?
Click to expand...
Click to collapse
Uhhhhh, I think he said "you'll find it in piratebay under applications" didn't he?

find it here
here you go link for the rom you want andmany others
http://rapidshare.com/users/EXGZ7T

do you still need to apply the battey leak patch and the other extra stuff you had to do with underground

Related

[Q] Galaxy S 2 Phone Options Displaying Incorrect Information Ref: Silent Mode On/Off

Hi, Have had Galaxy S 2 for 5 weeks, it was working properly up until the screen failed last week, went off for official repair, came back fixed, all good I thought....But a New Issue Has Manifested
The methods of toggling through having sound on or in silent mode are giving false indications......
In phone options, which are entered by a long press on the power button, the first option is silent mode on / off, but the phone is doing the exact opposite to what it says! I have missed a couple of important calls because I checked the phone status this morning when I came out of a meeting, it said "Silent Mode On" So I hit it to activate Silent mode off, which it displayed, however, got to office and 2 calls had been missed, the phone was not ringing out at all...! (Even though it was displaying silent mode off) when I toggled bact to silent mode on, it would then ring???!???
I have soft reset, hard reset, and neither has made a difference. Now, do I send phone back again and be without it for 10-12 days, or is there a simple fix/issue I am missing here? If it was a Nokia, I would have re-installed the firmware as the next action, but cannot work out how to do this on a Samsung Galaxy S 2.
If I choose phone update in about phone, it tells me no new updates available.. There does not seem to be a re-install existing firmware route to take.
Please advise?
Thanks in anticipation;
skthecat
factory restore reinstalls the existing firmware .
jje
Hmm, well it cannot be that then, can it... Any ideas why phone is "Cross Wired" for want of a better explanation for the Silent On / Off reversal?
Cheers;
skthecat

[Q] GS3 waits up to two minutes before placing a call

My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.

MROM-Olympus Issues

Hello guys, I would have posted this directly to the MROM thread but I can't due to not having 10 posts....so I'm posting here and hoping somebody can help me or draw attention from someone in that thread that is running this rom. I'm having a few issues with this ROM that are leaving me unable to use my phone at times and others that are just annoying.
[ROM] MROM-Olympus [CM7] build:20130330
Problems with the Phone function:
1. The biggest problem for me is sometimes trying to dial or receive calls stops working, and you don't know this, when everything else on the phone is functioning fine. A reboot will allow the phone to be able to dial out and receive calls once again. I have not noticed any patterns ...just when I get ready to make a phone call it says "dialing" and then after a few seconds a beep and it hangs up. Also as noted when this happens I'm unable to receive calls and everyone gets my voice mail. It was doing this after a install and without anything else being installed...I do feel that it's gotten worse as in happening more often but that could just be my frustration making it seem that way.
2. Another phone issue since day one: Sometimes after dialing a number the screen goes off and pressing the power button may or may not bring the screen back on or if it does the screen comes on for a split second then goes back off. It's impossible to end a call this way or to enable speaker phone, look up contacts. When it's functioning correctly a call is made then the screen goes off when i place the phone close to my ear and comes back on when i take it away. A reboot fixes this issue usually for awhile, I've also had to take the battery out twice because the power button did nothing.
Problems with the wifi tethering function:
3. Wifi tethering works but I've noticed problems on upstream packets. On 4G the phone can hit 5-6 Mbps down and 1.5 Mbps up on T-mobile. I've ran test via "speedtest dot net" which they have an android app so you can test your data speed right from the phone. Now when I connect "wifi tether" my computer to it and run the test from the computer I get the 5-6 Mbps down but the upload test takes forever to start and when it does I usually get anything from 25-220 Kbps. I performed this from linux, windows and an android tablet ..all report slow upload speeds while the phone directly running the same tests get very good performance. I'm wondering if this could be a issue with the wifi driver or possible kernel issue of sorts.
I choose this rom because from what I read it was one of the most stable and everything on the phone works which is the most important thing to me.
Thanks in advance!
Happened again today, phone uptime was 17hrs. I'd made a few phone calls and received one, pulled the phone out of my pocket to make another latter and it did it's thing where it says dialing .....a few seconds then the beep like when you hangup and then back to the contacts. I checked this time the status and it showed in service and data connected. I was also able to txt and browse the internet just not make or receive calls until a reboot.

Phone dialer delay/lag when hanging up

Been having this for a while now. When you come off a phone call, and I hang up via the red hang up button, it takes 4 to 6 th sometimes 8 seconds to actually hang up.
If the other party didn't hang up, they could hear everything I say even after I press the hang up button.
I have tried Google dialer and it's not there but stock dialer is needed for a lot of dual SIM functions.
Any advice please?
Maybe try clear cache of the app
Reboot Removes Delay
everybodylovesfebs said:
Been having this for a while now. When you come off a phone call, and I hang up via the red hang up button, it takes 4 to 6 th sometimes 8 seconds to actually hang up.
If the other party didn't hang up, they could hear everything I say even after I press the hang up button.
I have tried Google dialer and it's not there but stock dialer is needed for a lot of dual SIM functions.
Any advice please?
Click to expand...
Click to collapse
Hi
I am having the same problem and just started looking for help. The only thing that stops this is a reboot of my phone. Gradually on a scale of calls made/received (not sure if it matters which), the length of time to hang up the call increases. When it gets to "painful" levels I restart the phone and it's nearly instantaneous again.
This is a bug in the stock LG dialer. Mine started after the latest Oreo update. Pre-update, I didn't notice any real issues.
This is driving me nuts as well. Has anyone found a fix for this? In my case even restart didn't fix it. The red hangup button is taking ages to respond and the call doesn't hangup until the other party hangs up

Car Bluetooth fails to dial, then dials

Hi. Little issue I'm trying to get solved. When trying to make a call from in car steering wheel controls (simply press phone icon and dial a number from the phone book / history) the screen shows dial up failed , then after a moment it starts to dial the number. So it works but it's annoying as it can take a little bit of time , and it's when I go to check the phone it starts to work.
I'm on miui by xiaomi.eu 12.5.4 stable. I haven't and don't really want to factory reset. I have unpaired and repaired the phone to the car.
It used to work on previous miui ROM.
Has anyone had same issue or found a fix?

Categories

Resources