So I've been trying to enter some of the 'Secret codes' from this page and have run into a weird problem. Basically some of the codes work (Not very many, IMEI being one that does) but the majority do nothing. The dialer simply sits there and when I then call the number, which I realise shouldn't be necessary, I get an error of Invalid MMI or connection problem.
There have been a significant amount of threads on XDA and the web but the most relevant ones seem to be from Galaxy Nexus owners. This thread for example highlights my problem exactly so it may be something to do with ICS/CM9 that I've overlooked. Another user in the fast dormancy thread also has the same issue so I don't think it's an isolated issue. I've also taken the following steps to try and resolve the issue (Worked for other devices/threads I came across):
- Turn off DTFM tones in Phone - Settings. I don't have this option.
- Turn off touch pad tones. Doesn't work.
- Turn off Speaker phone before entering codes. I don't have this option from within the phone app.
Has anyone else ran into this or know of any solution? Any help would be appreciated
Same here, using official Samsung ROM
It's because you use a custom ROM which does not have the Samsung dialer (or a service linked to this dialer).
In other terms, only Samsung dialer can "read" these secret codes.
Nojevah said:
It's because you use a custom ROM which does not have the Samsung dialer (or a service linked to this dialer).
In other terms, only Samsung dialer can "read" these secret codes.
Click to expand...
Click to collapse
Until I began using CM9 recently I only ever used stock based ROMs and couldn't get the codes working. A user above me seems to be the same. Some of the samsung specific codes did work from memory but a vast majority of them didn't. Seems to be hit or miss :/
Hollow.Droid said:
Until I began using CM9 recently I only ever used stock based ROMs and couldn't get the codes working. A user above me seems to be the same. Some of the samsung specific codes did work from memory but a vast majority of them didn't. Seems to be hit or miss :/
Click to expand...
Click to collapse
Thats what i found some work some don't even tried SGS tools etc .
I belive the posted codes came from SGS not SGS2 . Possible a difference ???
jje
I had misread your first post. Sorry. :/
Indeed, if you have one secret code working, it means you use Samsung dialer.
I guess Samsung did not implement all functionalities behind these codes. I don't think there's a workaround, but maybe I'm missing something.
Hollow.Droid said:
So I've been trying to enter some of the 'Secret codes' from this page and have run into a weird problem. Basically some of the codes work (Not very many, IMEI being one that does) but the majority do nothing. The dialer simply sits there and when I then call the number, which I realise shouldn't be necessary, I get an error of Invalid MMI or connection problem.
There have been a significant amount of threads on XDA and the web but the most relevant ones seem to be from Galaxy Nexus owners. This thread for example highlights my problem exactly so it may be something to do with ICS/CM9 that I've overlooked. Another user in the fast dormancy thread also has the same issue so I don't think it's an isolated issue. I've also taken the following steps to try and resolve the issue (Worked for other devices/threads I came across):
- Turn off DTFM tones in Phone - Settings. I don't have this option.
- Turn off touch pad tones. Doesn't work.
- Turn off Speaker phone before entering codes. I don't have this option from within the phone app.
Has anyone else ran into this or know of any solution? Any help would be appreciated
Click to expand...
Click to collapse
Just to let you know, I have had this issue since day one with CM9 (December). I have read and read and re-read and nothing is working. Afew codes are working, but no more. I have added * and/or # etc.. Nothing work. The best example is the Fast Dormancy one. But others do the same. Some people says its because we don't have stock ICS Dialer. Dont know what to do if you find, pls let me know.
Related
In LG Optimus One endcall function does not work, so do not work correctly call blocker apps. Can this be fixed in a custom ROM?
telephonyService.endCall() function BUG
Hi everyone!
I confirm that there is a bug with telephonyService.endCall() function which consist in passing call to this function to nowhere, thus making ALL call blocking software useless, because they can't discard unwanted calls.
Can anyone fix this problem? I believe in you, GURU, take a look on this problem please.
With respect and hope, Max.
I really think this topic deserves a bump. And a solution.
Same problem here. End call function simply doesn't do anything on this phone making call blockers completely useless. I tried all O1 roms and even the original rom with the latest update and still doesn't work. Every call blocker says that call was blocked while you are watching it ringing.
By the way until someone comes with a fix, i found a temporary solution which requires Tasker or Settings Profile application.
If you want to send the blocked number to the voicemail, simply program Tasker to switch to airplane mode on and off or if you want to do the pick up and hang up action program Tasker to accept the call first then switch to airplane mode on and off.
As you can tell it will disconnect you from your network temporarily but Tasker is quite fast doing it so you will be on again very quickly. Putting your phone into airplane mode will end the call very quickly which call blockers can't do for this phone right now. You can do all these with Settings Profile too with the same steps.
Until a software fix, any other ideas are more than welcome.
(Unknown and private number value for Tasker is 0).
I have had the same problem and confirmed with Tasker developer that this is bug in LG Optimus One. Airplane mode is good solution if you do not protect your sim card with pin code. Else, after airplane mode is switched on and off, you will be prompted to insert pin and until you do so, your phone will not be reachable
I would prefer different solution...
I think we need to ask the guru to fix this problem. I said two weeks ago with mik_os about this issue, he replied that he might look, if not occupied by another.
Bump
This is something that is important as we cannot handle unknown calls.
If anybody has some solution, it would be appreciated.
I'm working on that.
For now I'd found by debugging phone with adb that endcall function really do something, but it seems that at the wrong time:
[ 02-16 20:27:52.451 1589:0x635 D/PhoneInterfaceManager ]
[PhoneIntfMgr] CMD_END_CALL: no call to hang up
Click to expand...
Click to collapse
That message appeared two seconds after we got the call (it's a mystery what phone was doing during those 2 secs), but before the framework starts to search corresponding contact to the calling number.
May be we have to wait several seconds after we get the call to invoke the encall() function again?
I'm a starter with android and I have not so much time for that, but I'm now trying to write a little program that will invoke endcall() function any time a want to prove/disprove my theory.
If anyone had written such program already, you can share sources with me to let me test that condition, or try it yourself.
UPDATE:
I've just tested it: there is no matter when you invoke endcall() function, the result is the same "[PhoneIntfMgr] CMD_END_CALL: no call to hang up". So digging deeper.
Last information from Android sources (how it should be in Android and doesn't work on our phone):
method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java
Digging deeper...
First of all, that's environment I have:
- LGP500 device )
- "void" custom firmware
As I mentioned before, method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java.
To check what's wrong I tracked that method to Phone.apk in /system/app/ directory of "void" custom firmware, which was grabbed from original LGP500 2.2 firmware, unpacked it and dedexed classes.dex file from it. To my great surprise I've found that it really omits call to hangup method of PhoneUtils class and do many things, that doesn't cross with Android sources. So LG programmers did their own "Android" with their own bugs. I have to say that it omits call to hangup method only for GSM call, but it has to be done for CDMA calls well.
I'll try to build Phone.apk from Android sources. This may take a while (maybe a week or so). Or maybe I'll edit dex file and repack Phone.apk with a new one. We'll see when I finally get some sleep
FYI, there is another way to block calls by diverting some call numbers to voice-mail. This is built-in Android function. That could be done in your phonebook by selecting a contact, pressing menu button, selecting options and checking "Incoming calls, Send calls directly to voicemail" checkbox. This way works more quickly than any other methods, used in callblocker software. So blocked caller immediately hear busy tone. I'll dig in sources how it works and maybe will find a better way for callblocking software.
Sorry for my English.
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
vault1965 said:
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Of course I need help. What kind of help can you offer? Do you know how to build Android on Ubuntu 10.10? I've read couple of articles about that, but still it would be great if somebody familiar with that can join that topic. I'm familiar with linux only in network services administration and a little with programming in couple of languages.
BTW, I've found another bug in our LG firmware - Skype (and another one program, that I can't remember name of) can't switch sound to speaker. Instead it always playing sound (I mean voice of person you're talking with) through loud speaker. And again I think the problem is somewhere in standard *.apk files, which are Android framework.
Had anybody tried gingerbread?
Had anybody tried gingerbread from that topic http://forum.xda-developers.com/showthread.php?t=909242 ? Does it solve the problem? I'm currently reading that topic when I have time (there are a lot of words not in my native language) to decide whether it worth to be deployed on my device. Because of that currently I had stopped further investigation to solve the problem on froyo.
If anybody has some experience with that gingerbread build, let us know please.
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
vault1965 said:
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
Click to expand...
Click to collapse
Hardware EndCall works on our froyo with key remap also. I was asking is it API "endcall" function working (you can test it with simple "CallFilter" program from the market)?
BTW, that API works fine on Nexus One recently upgraded to gingerbread. So information about removing call api's is a fake. Also I can refute that information as I saw this API's in gingerbread sources with my own eyes.
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
cigman said:
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
Click to expand...
Click to collapse
Thanks for information.
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Sent from my LG-P500 using XDA App
migueel said:
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Click to expand...
Click to collapse
Try Gingerbread at http://forum.xda-developers.com/showthread.php?t=909242
It has to solve the problem
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?
Anyone know how to enable "Find My Mobile" on the GT10.1? When i check the box for Remote Controls, it pops up a ID/Password box but I'm only able to enter the password portion. Entering any password whether correct or not gives a "Processing failed" message.
On samsungdive, my account login works just fine.
has anyone been successful?
I'm able to log in at the settings page but I don't know where to go on Samsung's web site to track my phone.
TabGuy said:
I'm able to log in at the settings page but I don't know where to go on Samsung's web site to track my phone.
Click to expand...
Click to collapse
samsungdive.com
So when you enable "Remote Control", do you get a popup window for ID/Password? If so, can you enter both ID and Password or just Password?
flintdragon said:
samsungdive.com
So when you enable "Remote Control", do you get a popup window for ID/Password? If so, can you enter both ID and Password or just Password?
Click to expand...
Click to collapse
I saw that in your original post but it looked like an autocorrect error. What an odd domain name.
Anyway, I was able to log in. Here are the results...
- Find my mobile: Worked perfectly. Saw my exact location. The Satellite overlay showed the building and my exact location within the building where my Tab is located.
- Track my Mobile: I didn't try it. Assuming that it could find me perfectly I expect it could also track me.
- Ring my Mobile: Mixed results. Yes, it rang my Tab and yes, it played a sound even though I had muted the Tab. However, it played a single "bong" (is that the default ring tone?) only once. It never repeated for the entire minute as promised. If I had lost the Tab and was trying to find it in some other room I'd be very disappointed. My advice, keep the other "find my device" software installed that plays a siren.
- Lock my mobile: Works perfectly. I was using the Tab in an unlocked state and it locked the Tab using the background of the regular lock screen. This is important to me because on the regular lock screen I have my contact information. It asks for the pin that I entered on the SamsungDive site and then unlocked the device.
- Wipe my mobile: Didn't try it. For obvious reasons. But considering everything else worked, I'm going to take a leap of faith and assume this works also.
I'd say I'm 80% satisfied.
Good to hear that it should work. Bad for me that it doesn't.
Anyone else have the same problem as I?
tried Samsung DIVE yesterday and today and it didnt work with the Tab 10.1
it worked fine with my Galaxy S II though
I'm in EXACTLY the same boat as flintdragon, to the letter.
looks like a long dead thread but I thought I would add the current samsung site info
as of 7/7/2013 you can log in to the samsung account site that has things like find my mobile here:::
https://account.samsung.com/account/check.do
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
Hello fellow poco lovers. I used Mint mobile in the US which uses T-mobile's towers. I'm able to makes calls and send/receive texts, but the mobile network sucks. The poco only has 1 wireless band to work in the US with mint so while I'm driving around delivering pizzas I lose internet a lot and sometimes very difficult to get reconnected. I've found a few temporary fixes but those temporary fixes have become more more less reliable.
I found this guide to add wireless bands to any phone with a Qualcomm chip on xda and it inspired me to root my phone. https://forum.xda-developers.com/t/guide-add-all-gsm-and-lte-bands-to-your-phone.2886059/
After about 2 weeks of unlocking bootloader>flashing twrp>flashing magisk>flashing a custom rom>getting the right gapps> soft bricking my phone flashing gapps>reflashed custom rom from sd card>reflashed gapps from sd card>reflashed magisk from sd card>flashed kernel from SD card(yes all in that order)
So in that guide I posted above it mentions a hidden USB settings menu by dialing *#0808#. (I know the guide uses a code for a Samsung phone but Xiaomi's code is the same)
When I type this in the dialer I get a message saying "USSD code running..." then a message that says "connection problem or invalid MMI code"
I even downloaded 4 different hidden menu apps and found the USB settings but I get errors trying to load it as well.
I have LineageOS 19.1 and NGK.
I guess my question is, are the dial codes/hidden menu apps not working because I soft bricked my phone at one point, or am I missing something?
After finding as much info as I can, I guess phones lose access to dial codes and hidden menus when on custom roms and kernels. It looks like some phones have a solution but I couldn't find anything for Xiaomi/Poco f1.
I'm gonna try a few more things and will update this post when I get more info.
Thank you for your time