Related
I have created this topic to try and get all feedback specific to this upgrade into one place.
So if you have comments, issues, problems, opinions or just plain questions about this upgrade, post them here.
great job dcs.
let me be the first to post and it's regarding Incoming MSG.
When i first got my unit from Philippines, it was loaded with 1.66WWE and with this version i was able to select preloaded or customized WAV as incoming SMS tone. But it went missing when i upgraded to Waxx's 1.72 and even now to the latest o2 UK 1.72. Anyone else experiencing this?
lazzy said:
great job dcs.
let me be the first to post and it's regarding Incoming MSG.
When i first got my unit from Philippines, it was loaded with 1.66WWE and with this version i was able to select preloaded or customized WAV as incoming SMS tone. But it went missing when i upgraded to Waxx's 1.72 and even now to the latest o2 UK 1.72. Anyone else experiencing this?
Click to expand...
Click to collapse
I am able to do this. From the Phone app. Use Tool/Options/Phone and tap Other Settings button. then use the Notifications tab.
Latest ROM upgrade??
I have read the o2 blurb, but can other o2 uk user tell me, what do I really get from this upgrade that makes it worth all the hassle of resetting my device and re-installing all of the hardware please?
Many Thanks
Pete
NB post here or as a private message thx
dcs,
finally after flashing it again this time with
ROM 1.72
Radio 1.17
ExtRom 1.17.181 (modified by ZeroXtreme for Asia) http://forum.xda-developers.com/viewtopic.php?t=12547
i am able to select WAV as incoming msg tone. not too sure what happened.
Re: Latest ROM upgrade??
peterbutler19 said:
I have read the o2 blurb, but can other o2 uk user tell me, what do I really get from this upgrade that makes it worth all the hassle of resetting my device and re-installing all of the hardware please?
Many Thanks
Pete
NB post here or as a private message thx
Click to expand...
Click to collapse
Personally, I find the performance to be improved and also stability. Also, when a call comes in, the Answer button on the dialog works, which didn't before. As part of the extended ROM, O2 have provided improved video streaming over GPRS plus video for MMS (I haven't used either yet). The OS itself has the Microsoft user update 2 included. Of course, the 181 release also has Blackberry included.
lazzy said:
dcs,
finally after flashing it again this time with
ROM 1.72
Radio 1.17
ExtRom 1.17.181 (modified by ZeroXtreme for Asia) http://forum.xda-developers.com/viewtopic.php?t=12547
i am able to select WAV as incoming msg tone. not too sure what happened.
Click to expand...
Click to collapse
OK. Strange, but at least you are sorted
Edit: Maybe it is something in O2 Active that causes the problem? I have uninstalled it, so perhaps I am unaffected. Could other people with O2 Active still installed throw light on this?
msn
Hi, I have installed the new rom (1.72.187). Everything is ok but Messenger. I can surf web sites using gprs and wifi but i cant connect msn. I always get the same error. "Logon to MSN Messenger failed because the service temporarily unavailable." But i can connect with my laptop. Any idea? thanks....
dcs,
have you tried Battery Pack Pro v1.1.10 on this? The last time i used this with 1.66WWE, i keep getting total blackout on my XDA2 with Bluetooth light steady blue and i hard to perform hard-reset. since then i was afraid to try again.
Re: msn
dherrero said:
Hi, I have installed the new rom (1.72.187). Everything is ok but Messenger. I can surf web sites using gprs and wifi but i cant connect msn. I always get the same error. "Logon to MSN Messenger failed because the service temporarily unavailable." But i can connect with my laptop. Any idea? thanks....
Click to expand...
Click to collapse
Have you applied the latest patch from Microsoft? Take a look here: http://www.microsoft.com/windowsmobile/downloads/msnmessenger/pocketpc.mspx
It does state that you cannot access the service unless it is applied. Quote: "Customers without the updated software will not have access to the Service until the download has been completed."
lazzy said:
dcs,
have you tried Battery Pack Pro v1.1.10 on this? The last time i used this with 1.66WWE, i keep getting total blackout on my XDA2 with Bluetooth light steady blue and i hard to perform hard-reset. since then i was afraid to try again.
Click to expand...
Click to collapse
No, sorry. I have never used it.
Anyone else used it?
Battary Pack
Dear
dcs,
have you tried Battery Pack Pro v1.1.10 on this? The last time i used this with 1.66WWE, i keep getting total blackout on my XDA2 with Bluetooth light steady blue and i hard to perform hard-reset. since then i was afraid to try again.
Click to expand...
Click to collapse
I also have identical experience using the Battery Pack Pro v1.1.10 on 1.60 WWE. Being scared to have a try on 1.72. Should anyone pioneer on this, please also let me know. Thanks
Blackberry?
I'm trying to understand what the benefits of having Blackberry are. The Blackberry website says you get all the stuff which I'm sure I already have with my XDA. Things like e-mail and IE. Except for my e-mail which is blocked by my ISP, Plus.net (I can only view/download e-mails, not send new ones).
What's the big improvement I'm supposed to get with Blackberry? :?
lazzy said:
dcs,
have you tried Battery Pack Pro v1.1.10 on this? The last time i used this with 1.66WWE, i keep getting total blackout on my XDA2 with Bluetooth light steady blue and i hard to perform hard-reset. since then i was afraid to try again.
Click to expand...
Click to collapse
I am running v1.1.1 with no problems on the v1.72 Rom. Worked fine with 1.60 also but no experience of v1.66.
have already installed New ROM 1.72.187
in this ROM, i think it work faster than 1.60 but liked other 1.72 ROM from T-mobile.
In the Ext ROM ,it doesn't include some software such as GPRS monitor.
Now ,I desired to cook it.
More stable without question. Only thing that I have found is that the O2 logo can't be moved. Dam thing stuck in middle of title bar. BT Tools works ok. Better wapsupport for o2 active, though XDA seems to forget it's connected and will drop connection and reconnect when conecting to O2's wap service.
Still it's a worthwile update.
I am having problems with Fonix voice dial. When I adda voice tag I get an error that it cannot update, hard or soft reset doesnt help. Also if I restore my backup using the built in backup program I find that streaming video and blackberry programs both vanish from my xda 2.
Feed back
looking good so far. I have added all my apps including BPP 1.1.1 and everything works fine.
SRS now works as well whereas before it trashed my xda II
I am from Asia but installed this UK o2 ROM and found its totally working good.
However, one thing is the autoconfig function has gone.
Anyone knows how to get this from the previous AISA rom?
Blackberry Config
Anyone been successful with this yet?
Ive activated the install and the BB client tries to connect somewhere over GPRS, but eventually suspends itself.
Ive got access to our Corporate BES so should be able to get it working. However, there seems to be some mention in the ROM upgrade guide about a desktop client manager (needed on PC to download the policy).
Ive seen posts that say O2 is not making it availble until Jan 05 - anyone confirm?
Oh, and Im actually using Vodafone
I'm using an Imate & Vodafone SIM, and when o2 released their new update which included Blackberry support I upgraded my device. Everything worked perfectly, I travelled to the Far East and Blackberry functioned correctly.
When I returned I decided to upgrade to 2003SE V2.06 and installed Blackberry, it didn't work. I then downgraded to 2003SE V2.02 and installed Blackberry, still not working.
So today I reverted back to the o2 V1.72 update, still not working, and the Blackberry Server is showing 'Illegal PIN Number'.
This is just a warning that the SE update may screw Blackberry up, or o2 & RIM have noticed that everyone is using their software and started to block non o2 devices that are running the software.
Hi,
Same message on my BES: 'Illegal PIN Number' and BBY not working. But I have it till the first time trying to connect, one month ago..
The client connects, gets an IP address and disconnects displaying the 'not connected' icon. However, the client receives Policy and Services from Server.
I still haven't found a solution... Any help welcome.
Serge
Eaxactly the same as I'm getting, I'm going to try the suggestion about removing the user from the BES, deleting settings on the XDA & Docuements & Settings and see if this works.
My initial thought was that the PIN number had changed but that does not seem to be the case.
a18041967 said:
...removing the user from the BES, deleting settings on the XDA & Docuements & Settings and see if this works...
Click to expand...
Click to collapse
I allready tried that with no success. Tell me if it works for you...
Serge
t-mobile
Strangely enough same problem happened to me today. I called t-mobile they reproivisioned ... n othing etc. All of a sudden this afternoon it's working again?
I've tried everything, and still no joy, I emailed RIM and they just referred me to Vodafone, carefully ignoring the question about 'Illegal handheld PIN'.
Just out of interest, what is the PIN number of your devices, my only thought now is that we all have the same PIN, mine is 613F1E63. If this is the case then the upgrade has screwed our device ID's.
If not then there's a way of identifing the network from the PIN, and a block has been put on none o2 devices.
I've had a thought, what versions of BES are people running, we're runing V3.6 Sp2, the latest is 3.6 sp4 so I'm wondering if there maybe something in sp3 or 4 that fixes the Illegal Handheld PIN problem?
Is it possible to confirm BES versions an if the Blackberry client is working.
Sorry, I'll be at office only next week.
I'll then tell you my BES version. I think this is a good idea.
Serge
HI there.
I've been having the same problem, with the Australian Telstra network- I get the "illegal pin" response from the sever, even though the XDA connects OK (the server notes that it is is contact with the XDA)
Has anyone found a fix? Not sure if the culprit is Telstra blocking PIN's that are generated by devices that are not supported, such as the XDAII
dchalmers said:
HI there.
I've been having the same problem, with the Australian Telstra network- I get the "illegal pin" response from the sever, even though the XDA connects OK (the server notes that it is is contact with the XDA)
Has anyone found a fix? Not sure if the culprit is Telstra blocking PIN's that are generated by devices that are not supported, such as the XDAII
Click to expand...
Click to collapse
Actually, all blocking happens at the master RIM relay in Canada. RIM regularly sweep their system for 'illegal' devices and software versions. So hacking the software out of 1.72.181 and putting it into a dodgy 2.02 build qualifies as 'illegal'. BAM - your PIN is blocked by RIM.
Changing your software afterwards back to 1.72.181 wont work, because the PIN is still blocked. You then need to call your mobile provider and beg them to get it unblocked.
:?
Thanks for that.
My original ROM was 1.66- are you saying that I have to go back to this version and then install the BB app, and then beg the mobile provider? If they re-set the PIN, will that get caught up in a sweep?
Cheers
dchalmers said:
Thanks for that.
My original ROM was 1.66- are you saying that I have to go back to this version and then install the BB app, and then beg the mobile provider? If they re-set the PIN, will that get caught up in a sweep?
Cheers
Click to expand...
Click to collapse
172181 is what O2 released - go back to that one and let the begging begin....
Southern_Man said:
dchalmers said:
Thanks for that.
My original ROM was 1.66- are you saying that I have to go back to this version and then install the BB app, and then beg the mobile provider? If they re-set the PIN, will that get caught up in a sweep?
Cheers
Click to expand...
Click to collapse
172181 is what O2 released - go back to that one and let the begging begin....
Click to expand...
Click to collapse
Interesting. Sorry for all of the questions. Will removing and re-adding the user from the BES once 1.72 is installed suffice, or does it have to be re-set by the carrier?
Thanks again
Thanks for the advice- am up and running now.
Sync with the server is a bit dodgy, but have 1.72 installed and BB up and running- thanks for the help.
Cheers[/quote]
172181 is what O2 released - go back to that one and let the begging begin....[/quote]
Interesting. Sorry for all of the questions. Will removing and re-adding the user from the BES once 1.72 is installed suffice, or does it have to be re-set by the carrier?
Thanks again[/quote]
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
1) I dont think that was ever a default thing? Did you install something and forget? have a cooked rom? There are A2DP solutions in this forum, "Use the Search luke."
2) No, its shagged. I installed the windowslive50.cab file I had on universal, it works now.
3) No idea, mine works fine. Hard reset? Check your sim?
I can get online with my WLM but it does sometimes take a resync of the whole account to do it.
Skype did say (unless changed recently) that they were still working on transferring calls to bt headsets. Which means, currently, that it does not work through anything other than headphones and the mic on the phone.
Comm Manager
Hello,
It is possible to change the green color from the Comm Manager ?
Thanks
French Keyboard
I have upgraded my french Advantage and all is OK apart for keyboard layout. On my old Universal (also french keyboard) I had changes the registry for hklm/software/oem/qwerty layout to 1040C (hex) and it had worked.
On the advantage this does not seem to change anything, any ideas?
Also has anyone got integrated VoIP working? I have used a CAB file from Universal to activate it and SIP Config Tool to do the set up but it does not allow me to select VoIP from today menu.
Anyone got this set up and working? Integrated VoIP is the reason I upgraded to WM6!
Messenger Etc....
Live Messenger stops working correctly after a soft reset. Initially it works fine. Contacts show as offline, although they are still able to contact me and vice-versa.
As far as I can ascertain push email still functions correctly.
I cannot confirm whether this is related to MS's side (rather than the program) as I haven't had chance to check if anyone else experiences the same problems.
Have tried installing the separate CAB file but I am subsequently told that I do not have the necessary permissions (or something like that).
This comes from tests on a T-Mobile branded Ameo (not the brand new one I'm selling, if anyone decides to cross-check!)
I haven't come across any other problems. Seems a bit less laggy than the original T-Mobile ROM, loads up web pages slightly faster too it seems.
No other issues as yet.
Ive had no probs at all since installing the messenger cab.
Still using it now.
Do we know what version of WLM is on this new ROM?
I've pulled \windows\wlmmessenger.exe to desktop and looked at the Version tab...10.6.28.2700 is what comes out.
Pyrofer - can you do the same on your cabbed version and let me know what the version number says? Not always an accurate guide but worth a shot. Also the digital signature is 3rd May 07.
Cheers
Ant
EDIT - never mind, just seen ur post in general Athena tab...10.6.0026.1400
I wonder what is different? If anything? I also wonder whether this is actually a final release of the ROM that's just been leaked early, as WLM is a pretty central component to web using Athena owners (myself very much included) and for it not to work after a soft reset...hmm.
Hi royalmail,
I've got exactly the same problem you mention about the phone.
I was unable to answer calls.
So I belive you've use the second file to upgrade to WM6 (HTC001 ... with ipl...).
You have to go back to WM5 WWE using the last ROM posted in the Athena upload folder in the XDA FTP. After flashing your Athena to WM5, Use the first ROM posted (the one with a readme file included).
And voila! No problem at all since I've done it this morning, everything works fine!
Hope this helps!
Hi Thibale,
I flashed with the t-mobile version. the phone dead only once so far, though i am not sure it's caused by WM6. Anyway, thx for sharing your info.
royalmail said:
1. A2DP icon missing
I want to re-direct skype audio to my bluetooth earphone. How can I do that?
2. I can not login MSN/windows alive though skype can login without any problem via WIFI. Seems MSN try to get online through different connection setting? how/where can I define the connection setting for MSN?
3. Phone module die without any sign. All incoming call is diverted to voice mail automatically until soft reset. As if the phone is switched off.
(I am not sure whether this is WM6 related)
this means you might miss important call without any sign!
Does anybody have same experience?
Click to expand...
Click to collapse
See if this helps
http://www.silentservices.de/btIO.html
Also, read through the forum regarding some of your other issues.
Try to disable your GPRS and see if your calls start coming through.
Pyrofer said:
Ive had no probs at all since installing the messenger cab.
Still using it now.
Click to expand...
Click to collapse
Thanks for all the input.
@Pyrofer, could u upload yr WLM5.cab here? thanks in advance.
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?
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.