I know this has been mentioned before, but the only thing that was mentioned, was the sim card. well i'm getting CONSTANT dropped calls now. i'm on the phone, and suddenly i hear nothing, then the phone drops the call, and i notice the signal strength and data indicator have x's by em (usually meaning flight mode). after a few seconds, the signal goes back to normal. this has happened at least 30 times in the past couple weeks, if not more. i even thought that it could be the sim card i was using (GEMPLUS), so i switched with a 3G one from Cingular, and at first i thought everything was ok, but now it's happening more and more often. i know it's not the network, as i haven't had this problem until flashing with summiter's 2.17 rom. i'm at a loss, but i guess i'm just waiting for cingular's updated rom that could fix this...
I would reflash it. Mine was having problems signing into the data service. Everytime I would disconnect from Activesync cable it would try a bunch of times to sign in but could not. I would have to go into comm manager and turn the phone off and back on and it would sign on. Reflashed and my problems went away. Does not make sence my it would take 2 flashes to get it right but so far so good.
the only plug-in i'm using is pocket weather, but i don't see how that would put the phone back into flight mode, while in a call. reflashing is SUCH a pain in the ass but i guess i'll do it if that's the last resort.
Hi, I've owned my tytn II for a few months and in the last couple of weeks, the phone has been acting really odd. I have tried to make a call and it gives me the dreaded "beep beep beep" and ends the call every time i try. I've noticed this though; If i turn the phone off and back on, then as soon as it gets signal (like 3 minutes after load up??), i can make a call ... Then i cant make another after that ... Then if i send a text, as soon as i receive the "sms sent" notification, I can call again, if i try immediately.
It seemed like a software issue, so selected "clear storage" from the settings menu and still get the same problem. I've tried changing from my virgin sim to my vodafone sim and get the same problem. To make maters far worse, as well as not being able to dial out, nobody can dial in; it goes straight to voicemail. I am showing average to good reception when this happens.
One thing i have noticed since the problem started is that the "G" symbol at the top of the phone is now showing "3G", but i haven't changed area and don't recall it saying 3G before. I haven't changed any settings and haven't got any new software ... Its at factory standard, 100%.
Does anyone know what I should do as I'm getting ready to brick the phone just for the sake of it. I've had the Wizard for over 2 years and I never had 2 restore it once ... this phone is REALLY bugging me. I'm honestly thinking of keeping the wizard and selling this one on ebay for say £180 or something, just to get rid of it.
Also, I've noticed the battery is draining faster recently. The phone is about 5 months old.
sa_rulz said:
Hi, I've owned my tytn II for a few months and in the last couple of weeks, the phone has been acting really odd. I have tried to make a call and it gives me the dreaded "beep beep beep" and ends the call every time i try. I've noticed this though; If i turn the phone off and back on, then as soon as it gets signal (like 3 minutes after load up??), i can make a call ... Then i cant make another after that ... Then if i send a text, as soon as i receive the "sms sent" notification, I can call again, if i try immediately.
It seemed like a software issue, so selected "clear storage" from the settings menu and still get the same problem. I've tried changing from my virgin sim to my vodafone sim and get the same problem. To make maters far worse, as well as not being able to dial out, nobody can dial in; it goes straight to voicemail. I am showing average to good reception when this happens.
One thing i have noticed since the problem started is that the "G" symbol at the top of the phone is now showing "3G", but i haven't changed area and don't recall it saying 3G before. I haven't changed any settings and haven't got any new software ... Its at factory standard, 100%.
Does anyone know what I should do as I'm getting ready to brick the phone just for the sake of it. I've had the Wizard for over 2 years and I never had 2 restore it once ... this phone is REALLY bugging me. I'm honestly thinking of keeping the wizard and selling this one on ebay for say £180 or something, just to get rid of it.
Also, I've noticed the battery is draining faster recently. The phone is about 5 months old.
Click to expand...
Click to collapse
Did u try to turn of the 3g reception?
If no, try to turn it of in settings/personal/phone/band and in network type select GSM(or in comm manager turn the 3G off).
Mikulec, you are a god ... I guess i'm just getting angry at the phone because I haven't even started playing with it yet and its just so much more tempermental than my old wizard. It was to the point that I am still using the wizard as my main phone and the newer tytn II just sits at home all day! As it appears so far though, it definitely has worked, so thank you.
sa_rulz said:
Mikulec, you are a god ... I guess i'm just getting angry at the phone because I haven't even started playing with it yet and its just so much more tempermental than my old wizard. It was to the point that I am still using the wizard as my main phone and the newer tytn II just sits at home all day! As it appears so far though, it definitely has worked, so thank you.
Click to expand...
Click to collapse
happy to help u bro, the kaiser is a good toy, u just need to play with it.
This along with the faster battery drain is the first sign of a radio hardware failure. If in a few weeks you start losing network even with 3G off, or can feel your phone gets warm even on standby then you'll already know what to do... send it for repair.
When I send it in for repair, do I need to install the normal rom/etc? Before I installed the rom (http://forum.xda-developers.com/showthread.php?t=416278), I had no issues whatsoever. Will they actually replace what they need to even if it is working under the stock rom?
Actually, I just checked with 3G off, and I'm still getting the same 3 beeps. Anyone know what's up?
When I send it in for repair, do I need to install the normal rom/etc?
Click to expand...
Click to collapse
My friend that has kaiser also and usually flash his phone once or twice a week and had it repaired alot and they have never said anything about his ROM
but then we live in Sweden and maybe we have other rules then you have
It's better to restore original ROM and SPL (there's a guide in the Wiki for that) before sending it back. Once you've done that you can check if it works again - obviously if it does with the original ROM then don't send it back.
Hoping someone can help
Recently got a new Diamond after my old one suffered a killer blow when I slipped on some ice,
I unlocked and installed firmware 1.93.405.1 WWE and radio is 1.20.OliNex
Recently the phone has started to crash every other phonecall or so, for no apparent reason it just resets itself why you are on the phone, also seems phone part just cuts out and you get no signal report but in comm manager its still running, so case of restarting the phone before signal comes up
ANy ideas, since flashign it only apps I installed was calendar+ and tomtom just like on old one and had no problems at all
thanks
Hi everybody.
I'm having this strange issue since FROYO update (first one that came with radio). Everytime I put a new update (or anything involving going to Recovery), when my phone boots up, I can get no sound during a call (I can't hear and can't be heard also) and more, the proximity sensor is not working either (screen remains lighted when close to ear).
If I put the phone on speaker, I can hear the other and I can be heard. Looks like the upper part of the phone is not working. The only solution I found until now is to turn the phone off, take out the battery for a minute or two and then, when I start the phone, everything is back on its track.
I've tried everything, going back to stock, getting the new (now old) FRF85b signed from Google (with radio in it). I received no errors during updates, I did wipe everthing, but the problem is still there.
Today I've updated to FRF91 and after the phone booted up, same problem.
Could be the radio of FROYO? Anyone else have this issue?
Regards,
Alin.
I'm having this exact same problem and I'm kind of freaking out because I have an unlocks bootloader and no warranty, however this just happened to Me today and I've been on froyo for almost two months
ok so i just solved my problem... by smacking the speaker end of my phone on my hand a few times..
Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.