Ok so have really disturbing problem with a new SGS2. When i receive a txt message, i might get the same messages multiple times (record 17 times), and sometimes phone doesn't notify me about new message before i personally open the screen and start using the phone! Firmware causing this? Modem? Kernel?
I'd be really really happy to get help for this one!!
is it an imported device? sounds like your carriers settings are wrong. do you have the same problem with mms?
Sent from my GT-I9100
No it's not imported.. Bought from DNA (Finnish mobile operator), and carrier settings seems to be correct.. And as far as i've noticed same thing appears also with mms..
you'll might want to try to do a soft reset of the phone to the factory defaults to see if it helps? else if you can actually try to flash your phone with either the stock ROMs or custom ROMs.. hope this reslove your problems.
Ok now after i've tried every single thing, the device has been changed to new one. Possisble that modem component was broken and causing these problems.
Related
Hello
I have a problem, that seems to be related to the 2.1 update, since I haven't had this problem before. I've flashed both with versions from here and generic nordic version so I have tested several times from scratch.
I have roomies with the same phonemodel and carrier that have no problems. One of them use 1.6 and one 2.1.
My problem seems to be that the phone can't save and decide what NW to choose. Often I can have several text message dropping in at once several hours late. Often when I try to call I have to try up to ten times before the call connect, and most of the time when people call me they get I'm not available.
Seems it's no change if I kill everything non standard or even directly after re-flash. Do anyone of you know these problems and have an idea if it could be HW, SW or perhaps sim releated?
Since my roomies have the same phone and came carrier I doubt it's the carrier itself causing this. Both GSM and 3G coverage is great in the area. It can be noted that if I manage to get the 3G connection running, talking over SIP is 100%, but over GSM the receiver can have problems hearing me and sometimes I get this robotvoice.
So, for me it seems the radio firmware can be a bit off here, but is there anyway I can replace this separately or do you know of any fix that resolve the NW carrier settings that the phone seem to forget?
i seem to be having the same problem regarding delayed sms messages...
can anybody help please?
why not switch phones with your room mates and see if the problems follows the phone or the sim.
Mine is actually worse. SMSes doesn't even reach my phone. It happen twice already ( once in 1.6 and the second time in 2.1) Both time I solve the issue by reinstalling the phone software via pc suite. You should do the same
I have the same problem, i reinstalled the Cyanogen using xrec, and problem still exists.
Maybe anyone have some hints how to solve it?
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Ive got an unlocked Atrix too and now in Germany, I have the same problem. Motorola should definitely look into this.
Here's a quick fix for it thou, (not permanent)....
1. type *#*#4636#*#* on the dialer
2. Chose Phone Information
3. Set preferred network to GSM only
Viola...its fixed
problem with this fix is that you wont be able to use your 3G network but the dialer should be working.
Thanks Nazrin (for both replies) !!
It sure did the trick, though no data access is not acceptable on a phone like this!!!
So this meens that all unlocked Atrix's in european GSM networks have the same problems? Haven't seen any others reporting this and there are quite a few in use I've noted in other forums.
Was thinking of trying to have mine replaced (which probably won't be easy and take long time...) but that won't change anything then??
We have to wait for the european version of Atrix rom I suppose??
Any others with the same problem??
No problems buddy, glad it worked..and i have to agree with you..this bug is unacceptable...it seems the phone just ***** up everytime it calls on utms (3g)...im sure there is more people with this problem...
Sent from my Supercharged MOTO ATX
I have the same problem
Hi guys, I have the same exact issue (I'm also in Belgium, on Mobistar). I'm somewhat glad to hear this is a generic issue, and not an issue with my specific phone. At least I can be fairly certain replacing it won't solve this issue then.
I made another post here before I came across this one, has a bit more info: we are seeing modem panics when using 3G + outbound call. I've also contacted Motorola support to no avail:
http://forum.xda-developers.com/showthread.php?t=1028771
You can also read there that I tried another operator, and it did not crash with that one (although 3G did disconnect).
Hopefully Motorola/Qualcomm will start to notice the bug when they release the phone globally, and release a fix.
Either that, or we all have phones from the same bad batch
This bug is really bad for users in europe....cant call on utms...
I really hope motorola takes this seriously cos if there's no fix via software updates then its moto gone for me
Guys, you are all on unlocked att atrix right? I do believe it is a simmiliar software glitch/bug/lock that you have porblems using it on non att networks as the problem with the wifi that it stops working for some of us (check the thread about it for more info). As all suggests there it is a config file problem, unfortunately i or anyone else doesnt know yet which one....
Yeah maybe..but funny thing is wifi is working without a glitch...will have to read that forum later...
Workaround options
So, since it seems we're not gonna get this fixed until there is a new radio/modem firmware available for flashing (and even then..), I've been looking for a workaround.
Found two potential applications that could do what we need: disable data completely when making an outgoing call, or switch to 2G:
- Sanity
- Superpower
I've tested the first (Sanity), and it does not work (fully). It does seem to disable data, but the bands aren't switched so our problem remains. I've contacted the developer here: http://tagliamonte.net/forum/thread-10.html. He seems to be very responsive, so given enough interest, I think he would add the functionality we require.
The second app I only came across today, and have not tried yet. It does not have a function to specifically switch bands when making an outgoing call, but it has a trigger for "Foreground application", so if we make that the dialer/contacts... Question remains if it will be able to do the switch.
Hopefully one of these will lead to a decent workaround for all of us!
Well done unknown...i will try these apps... but the real fix should be from moto...im always reading the net for anything that can solve this issue
reboots on incoming and outgoing calls
Same in Russia on Megafon network, I had to enter 4636 menu and use it as "GSM only". Even this does not fully solve problems, e.g. call forwarding does not show the new destination number while it does actually make the phone divert calls correctly.
My hope is that UK release will trigger new software version which will address this issue. ANYONE has news on this?
FIXED!
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
_unknown said:
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
Click to expand...
Click to collapse
Worked for me as well..brilliant!!!! its working here in germany.....but I wonder the telstra radio will work in my home country with frequencies of 900/2100
Motorola Atrix restart when placing a call
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
No answer
Why I never got an answer of any post I did?
There is something wrong?
Eli
elijacob said:
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
Click to expand...
Click to collapse
Forget about those ways
klingsurf said:
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Click to expand...
Click to collapse
[Sorry for problem in speaking]
i had that problem too , im using CM13 with Marshmallow Version of android
So . the easy way is :
***** search "Default" in settings. then choose " System dialer" as Default ! just it ****
but if there is no search bar in your setting . try this patch:
Android 6 : Setting/Apps then click the setting icon on top(may be diffrent in your case) , then Click on "default ...." then choose " System dialer" as Default! :fingers-crossed:
but in some cases that it didnt work . they have to reinstall gapps .
Or in official Roms , reset will be usefull
any quastions?
i have the galaxy for 5 monthes now..
switched tons or ROMs and kernels.
since i tried the 2.3.5 androidmeda(i think it started there) i have a problem answering my phone.
when someone call me i can slide it right in order to answer, the phone stop the ringtone like i answered but i cant hear anything hile the other side think someone answered him as he doesn't hear the tome anymore.
i tried to go back to KG5 but i cant get rid of it.
it got better as i changed the modem(used to be on KI4) to KE4 and KG5(the rom im with right now but its not good.i can answer but it takes 5-10 seconds before i see the call screen and able to talk properly.
tryied androidmeda,cognition,batista,xpower(the used to be),villain and so. none helped so i guess its not ROM related exactly.
Maybe some data was changed (such as the opening after trying androidmeda-the white turning cube and the android character insted of the samsung s 2 pic).
i tried various MODEMS in order to solve it but no progress yet.
anyone familiar with this problem?anyway to solve it?
Sounds like a hardware problem more than a rom problem. You have tried all them custom roms do its quite odd. Id say trying to go back to a full stock rom if you haddent already and maybe test out other voice features on the phone like voice record and the google voice search thing.
Sent from my GT-I9100 using XDA App
Hi guys
I have a really annoying issue with my galaxy s2. It seems to be stuck on emergency calls only and will not let me send texts, call people, etc. I have tried everything- restore stock firmware, factory reset, repair apps and nothing has worked. My IMEI number is not null and it matches the one on my phones box. I dont know what else to try so any help would be very much appreciated
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
MistahBungle said:
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
Click to expand...
Click to collapse
I checked and there is no carrier issue and it works fine in other phones
In case and if you're using stock firmware:
1. Boot into Recovery Mode
2. Perform a full factory reset by wiping /data partition.
3. Reboot and see if it fixes the problem
However, try and use a custom firmware in case your OS is causing the problem. When it comes to me, the hardware doesn't have to be necessarily damaged or affected in such a case since the phone app is on emergency calls, so it's fully accessible. I recommend checking the app settings again (maybe tapped on something accidently), but nevertheless, I prefer trying a custom Rom to verify that it's a software issue, or simply flash your stock firmware through ODIN to fix any issue if persisted.
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.