I'd like to thank everyone involved in making Tuma 1.3 work.
I have had it installed for over a week. But now decided to go back to WM2003SE. This is because whenever I'm making calls on Tuma 1.3, I seem to have dial number 3 times before getting connected, then once connected, I tend to lose the call after 1minute. I don't know if anyone else has got the same problem.
I have tried upgrading the radio to no avail. I even reflashed my device hoping the problem is an installation error, but nothing has worked so far. Any ideas?
Cytrax
I'm having the exact same problem with calls dropping... It drops out between 1 minute and 1 minute 15s on every single call since I upgraded a few hours ago...
Otherwise it looks like a great build, would love to keep it if I can get it working with stable calls...
Related
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.
I have searched around and found no fix for my problem so far. Hopefully someone can help me out. I bought my Diamond used a few weeks ago and it came installed with a newer version of a Dutty ROM on it (not sure the exact version but I can retrieve it if needed) and it has seemingly worked fine. But the last couple days I have noticed that when anyone calls my phone, i touch the answer button and the phone acts like i pushed the deny/busy button and just sends my call to voicemail. No matter what I do every call now goes to voicemail. I havent tried actually pressing the busy button in stead while a call is coming, but I may try that to see if its switched or something. I tried a soft reset and didnt help... any suggestions for this strange problem????
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840
Hello all,
i spent quite some time researching my issue and found out that there is a bunch o people with this problem. The downside is, none of the recomended fixes seem to work.
Description: I recently got a S4 active i9295 with stock rom. Everything clean, nothing custom on it(i belive). For a couple of hours it worked like a charm, then, when i want to call someone, the transition from contacts to dialing screen lags a bit and then it goes into dialing and thats about it. Nothing else happens from there on. I loose signal and it keeps showing that it dials (i let it like this for about 15 minutes and nothing happend). I cannot end the call, it remains stuck in "dialing" mode, i can use all the other functions though. After a restart it works again. Same goes for sending SMS. The icon spins and spins but never sends the SMS, only after a reboot. Also when someone calls me, they get a "no answer" signal and my phone just looks ok, like normal standby but when i want to call back, it freezes at dialing.
I tried 3-4 different stock 4.4.2 roms, hard reset, wipe/clear cache, safe mode... It works fine for 15-20 calls/2-3 hours and then it does it again. After that point it only gets worse and it happens more frequently.
Any ideas on what could cause this or how to permanently fix it? Unfortunately, returning the phone is not really an option.
Thanks to all, best regards.
No one?
Hello guys
Ran into a snafu yesterday, clicked home a N6 demo-ex from one of the internetstores here, it was cheap and I've always wanted one. Of course it came with a pre-unlocked bootloader and everything else you'd expect from a used Nexus, but I wasn't too bothered about that, I would have unlocked it myself anyways. Flashed MM on it as soon as the images were available. I played around with it for a few more hours, then late last night I decided I should move my simcard to the N6 and try Speedtest and a few other goodies. Speedtest went just fine, got the usual 64 Mbit over LTE, then .. I'll call my automated bank just to check the earpiece and speakers. "Dial .... call ended". Try again. "Dial... call ended". Put the simcard back into my Nexus 5, dialed the same number, worked perfectly. Back into the N6, same number, it dials, then just as it's supposed to start ringing, "call ended". Has anyone got any ideas as to what could be wrong here?
Done so far to find the error:
*Reboot *duh*
*Reflash MM
*Flashed 5.1.1, thinking it was a new modem and my simcard didnt like it. Sim is about 2 weeks old by the way.
*A couple of factory resets, just to be sure
This is the very last Nexus 6 these guys had on the shelves so I would really, really rather not have to return it but of course a phone that you can't use for phonecalls .. I already own a Nexus 7, don't need a miniversion of it. Bright ideas or even far fetched guesses appreciated!
Hey bud, I had a similar issue with my phone as well and the way to fix it is by rebooting exactly 6 times in a row....literally. Power on, power off power on power off etc........ Ive encountered that issue several times, it usually happens when i left my phone die and then reboot after full charge. I could only use data, no voice/text and sometimes it would be backwards, no data, voice text only