Related
This might be a bit long winded, but I'll get there eventually. I have had all the MPx series phones, I had the MPx200 and hated it. The MPx220 was buggy until I just recently put the latest firmware on it, but really there are much better clamshell style smartphones out there. Now I'm playing around with the MPx (or MPx 300) and running headlong into the RAM limitations.
I've tried many many memory freeing programs, and systematically went through startup folders and file folders deleting stuff, locking the phone up, resetting, loading from backup, or reflashing and reloading from backup. Basically I've got as much out of it as I can. And, to be honest with respect to RAM, I am ok within the confines of the on board memory.
Then I see an ebay ad for a MPx200 with WM05:
http://cgi.ebay.com/MPX200-UNLOCKED...ryZ64355QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
And apparently someone has figured out how to use the SD card for a portion of the OS's RAM or ROM files in addition to getting WM 05 to run on the MPx200. So, I got to thinking, well why not do that with the -300 as well. I contacted that seller and a couple others on ebay, with no responses. So, I went searching other forums and was eventually led here.
If you made it this far, congrats. Now for the questions:
1) Do any of you know the background to that WM 05 upgrade to the MPx200? Was it someone here who figured it out? I searched but turned up nothing.
2) I'm a newbie when it comes to coding cell phone stuff, no idea on apps or whatever... I learned programming with Fortran77 for god's sake... lol. Anyway, I see all the apps and ROMS for the HTC phones and was wondering if the tools would work for the Moto phone as well, or am I barking up the wrong tree? Basically I'm toying with the idea of cooking up a WM05 or 06 for my MPx300. Yes, I understand I might brick the thing. I've come to terms with that.
Thanks all. I appreciate any input you all might have.
"and running headlong into the RAM limitations."
sorry cant help you but if you manage
you may be the first person in history who
fixed ram limitations by getting a newer microsoft operating system
LOL. I hear that. (but isn't crossbow actually better on RAM/ROM allocation than 05 was?)
But did you look at the link? On edit: that auction no longer explains that the phone will shut down if you remove the card while it is on because the new OS requires more memory and it was taken from the card. From the description it looks like the newer OS is using the SD card for a portion of its RAM... I realize that isn't a built in kind of thing, but was fishing here hoping someone knew enough to help me do this, or point me in the direction of someone who could... if not actually finding the person who figured it out.
Anyway, I realize this is primarily a HTC kind of site, I've been looking around on PPC addicts for a while, and it seems to me that the level of coding modification and experiance here is much greater than there, hence my asking over here.
Anyway, appreciate any or all help. Heck, even just thoughts about this at this point would be useful.
Here we go...
http://www.howardforums.com/showthread.php?t=785800&highlight=MPx200
Post number 14.
Hello Everyone,
I just got the Arrive and I'm loving it, but something weird is happening. For some reason, when I'm writing a txt, it just flat out stops at 160 characters and doesn't continue the message with an auto-split.
I called into Sprint, HTC, and Windows Phone support and they all think" woah, that's weird" and the majority of tech support didn't even know it had launched already. I also read the manual from Sprint, HTC, and from Microsoft stating that 160+ characters will be auto-split.
Since the phone is so new, as well as NoDo and such, I have not seen anything about this issue and it's driving me mad. My only theory is that for some unknown reason Microsoft limited the txt messaging in CDMA WP7 to 160 because CDMA doesn't handle 160+ characters well. If this is the case, WTF?!
I know there are very few of you who have an Arrive, but anybody have this same problem? Anybody have any ideas on how to fix this?
The only workaround I have is sending the message incomplete and continuing it with another (and that makes me feel like I'm using my old Nokia with Snake. I haven't had a phone that couldn't handle more than 160 characters before)
Mine does the same thing, while it is a little annoying until it get resolved sending it parts is the only work around.
Well that's lame.
Why does it seem like Microsoft is just dropping the ball with the basics on Windows Phone 7? I love the OS to pieces and I really like the phone, but these little nuances (along with simple things like changing colors, custom ringtones, group contacts, etc) are just plain unacceptable.
Also, I noticed something about the Arrive.
The OS version is 7.0.7389.0
but the NoDo being pushed today is 7.0.7390.0
That 0.0.0001.0 Might be all the difference, at least I hope so. It means a posibility of a tiny update
I wouldn't count on any updates in the forseeable future. And FWIW the manual for the phone says that it will break up messages longer than 160 characters, so this definitely sounds like a bug.
-R
I just learned this might be unique only to the Arrive
It is, I have the arrive and buddy has focus with nodo, his splits texts fine.
ScottSUmmers said:
I just learned this might be unique only to the Arrive
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
It must be all Arrives, because mine does the same thing. It's very annoying when you're used to having your texts auto-split. My Touch Pro 2 split text messages just fine, so I see no reason that it should be a problem with the Arrive. Hopefully this gets fixed soon.
Sent from my T7575 using XDA Windows Phone 7 App
My Arrive does the same thing. Of course, I didn't read the manual, so I wasn't aware that it was supposed to work differently (but had expected it to since even my WM5.0 Cingular 8125 did it).
And I've already heard that the .0001 isn't significant in terms of build number. CDMA vs GSM difference only.
Its an issue with Microsoft not implementing proper code for CDMA text splitting its annoying but they'll fix it.
Hi, I am an employee of Sprint. The HTC Arrive was intended to allow users to exceed 160 characters by automatically creating a new message after 160 characters is exceeded. This is explained on pg. 83 of the HTC Arrive User Guide. Currently the device will not allow users to exceed the 160 character limit. This has been recognized as a known issue and Sprint has asked Microsoft to address this issue in a future update.
Looks like it wasn't fixed in Mango. At least not for me
...
I am so tempted to ditch my Arrive right *now*. Sprint/HTC has been notified many times over about this issue. They had time to fix it. There is no excuse for this.
EDIT: Anyone know if Verizon HTC Trophy owners are having the same limit? I'm hearing *nothing* from that sector.
Chris-h11 said:
Looks like it wasn't fixed in Mango. At least not for me
Click to expand...
Click to collapse
It wasn't. This was the single thing I was most looking forward to. If they didn't update it with Mango, I suspect it will never be fixed.
I really hope that Sprint releases a new device, as I am ready a Windows Phone variant of the Galaxy SII.
Got the update notification. Updated, and sure enough, that limit is still there.
I don't think any words can sum up how much rage I am feeling right now. I really just want to throw caution to the wind and grab a Photon 4G.
To note: If this limit was stated clearly in the manual, I wouldn't have a problem with it. It is the fact that this is a feature that is SUPPOSED TO EXIST, but does not.
I son't understand why you're all raging of such a simple thing, I rarely need to write more than 160 chars in an SMS (a 1 minute call would be cheaper for me in that case ), but yeah it's apparently an Arrive-only bug because I don't have it in my HTC 7 Pro.
hassanselim0 said:
I son't understand why you're all raging of such a simple thing, I rarely need to write more than 160 chars in an SMS (a 1 minute call would be cheaper for me in that case ), but yeah it's apparently an Arrive-only bug because I don't have it in my HTC 7 Pro.
Click to expand...
Click to collapse
Correct...last we knew it was a Sprint firmware issue as you can now type more than 160 chars but the phone won't send it. I haven't been over to BUZZ in a while but try seeing if the Buzz About Wireless people are talking about it since that's Sprint offical forum
The 7 Pro won't have an issue because it's GSM, and GSM can support it no problem.
Only the 7 Pro (US Cellular) and Arrive will have this issue.
And I regularly send messages that get close to or go over 160 characters, and rarely make phone calls. So for me, this is a pretty big deal.
EDIT: Got one person saying this isn't an issue on the CDMA Trophy:
http://forum.xda-developers.com/showthread.php?t=1280146
If this is the case, it's HTC/Sprint's problem, not Microsoft's.
EDIT: Got first-hand confirmation that this is now HTC/Sprint's problem:
http://www.flickr.com/photos/anticitizen/6193110593/
That is a CDMA Trophy, doing a messaging split. I sent it to myself, and sure enough, it came through as two messages, but it did come through.
Btw, bump, just in case no one saw my edits. (Since they're a tad significant)
Yet another edit: Reached out to HTC over this. Gist of the response from them: We have no updates coming to fix any of the issues with the Arrive.
Going to give this one last bump, because seriously, this problem is really, really irritating.
I have some communication with HTC, but all I'm getting from them is "We'll notify you when we have more information!" Listen, I don't want more information. I just want to know if some kind of fix is being worked on. Or if they're going to get around to it. It's getting infuriating to wait on this.
Is there any known way of cracking the NAND protection on this phone yet?
Or if not, does anyone know where I should look for the latest news on rooting this Japanese-only phone?
I've been looking all over the internet for months and turned up nothing. I could really do with some help here please guys!
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Sent from my SH-03C using Tapatalk
Sharpen3d said:
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Click to expand...
Click to collapse
Not at all, thanks for the great info!
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Sharpen3d said:
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Click to expand...
Click to collapse
I'm a bit hesitant to use untested methods. This is my first Android phone and I have never rooted a phone before so it would be wise for me to wait for someone else to find a reliable way first.
I have flashed many older phones and PSPs in the past but this scene is quite new to me.
I am still checking many Japanese sites daily for news of a root. I will send you a PM if I find anything
figured to bump the thread as I`m also a Lynx3D owner looking for root access and a way around the NAND protection. I would be nice to free up this phone .
I'm still searching daily but it seems to be impossible, I'm not sure if it will ever be rooted.
Never mind though, at least we get android 2.2 this month
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Sharpen3d said:
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Click to expand...
Click to collapse
That certainly gives me hope, looking forward to 2.2 even more now!
And Docomo have announced that 2.2 is coming this month (May). It has been widely reported and they confirmed it in the Docomo shop this morning for me
Despite my better judgement, I went ahead and ran the is03break on my phone yesterday. Not only was it not successful (ran until it timed out) but it managed to adjust my settings enough that my phone wasn't able to see the cellular network, effectively destroying it's "phone" capabilities. I was able to hard reset it through psneuter/adb and now it's back to normal, but it was definitely a bit of a scare.
When 2.2 comes out, I may give it another go, but in the meantime I'll just play nice. Docomo staff confirmed 2.2 is coming before the end of May, and there's a chance we'll need to do it through the PC like the AU folk had to.
Looks like the update may well have been delayed until next month -
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26client%3Dfirefox-a%26hs%3DG75%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://juggly.cn/androidrumors&usg=ALkJrhgmfYRu8El9AjAHz_UeNb1s85EhZw
This is getting a bit much now. 6 months I've been waiting for them to update this phone. I'm considering taking it back and demanding a refund.
For what it's worth, even if there's a delay, at least it's a bit more definitive than things have been. Way back in March when the Quake hit, we were told it was being delayed from March to "Summer." Then they really brought it forward for May, which I don't really consider summer. That rumor blog (and remember, the key word there is rumor) suggests it will be delayed until early June. Worst case scenario, that means that, instead of getting it this week, we receive it in two weeks. I agree it's a pain in the ass, and the fact remains that, stuck at 2.1, we can't use a lot of conventional rooting tools (not to mention run flash, do App2SD, JIT, etc). But returning the phone at this point accomplishes next to nothing. The summer Docomo lineup is a bit underwhelming, in my opinion. You're paying for the camera, and the phone is attached to that. Even if you get the Galaxy S (a really nice phone, no doubt) it's starting to become a bit older. IF we can hold on till SH-03C receives 2.2, I honestly believe a world of possibilities open up. This community may not be large, but we can still tout a 3D phone proudly, and getting 2.2 really legitimizes its abilities.
Just be patient man.
Yeah, you are right.
I'm just getting frustrated at having to keep deleting applications. I'm really looking forward to using flash, bumping up the CPU and trying out that new Tegra app for playing Tegra games!
I'm just really hoping for App2SD. This is getting severely limiting. Additionally, I'm pretty sure that rooting will become significantly more likely once we're up on 2.2. I'm confident that, once we get to Froyo, our phones might be able to piggyback on methods utilitized by other NAND locked phones (example: EVO) that have been successfully rooted.
I just want to uninstall that stupid 3D golf game. It takes up so much memory it's insane.
This sounds promising -
"May 27, 2011
The previous model, LYNX 3D SH-03C in Android 2.2 update seems to be out soon. The details will be announced separately, "there is no update, that will never" Yes."
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3D5Ye%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://ch00288.kitaguni.tv/e1805281.html&usg=ALkJrhgPutM5T2orqoipGRQTi3kSISqnlg
The woman at the Docomo helpline, having started to recognize my voice, totally leveled with me. The update was planned for the end of this month, and they got screwed in timing. They hope for the first weeks of June, but it may be even later than that. Truth be told, I bought my SH-03c aftermarket, so I can't return it even if I wanted to. But I'm not bailing. I'm confident we will see the update before the 15th, and, really, as long as it doesn't start malfunctioning, I can wait.
More rumors, looks like July 7th is the day -
"NTT DoCoMo's "Galaxy S SC-02B", "Galaxy Tab Sc-01C", "LYNX 3D SH-03C" on the OS version is effective from June 7, "will" is a rumor.
According to rumors, the version of June 07, Galaxy S Tab and the Android 2.3 (Gingerbread) to, LYNX 3D SH-03C is Android 2.2 (Froyo) is going to be provided.
LYNX 3D SH-03C
Changes as part of the Android 2.2
-Flash Player 10.1 or later for
- Micro SD card can move the app (the app only support)
- Respond to voice the character input
- Application for Automatic Updates to bulk update
- The application "search" and "News and Weather," in some of the sharp changes in their own additional
- Launch applications list "end all" button added
- Power management notification bar menu (Wi-Fi or BT) is added
- Supports multi-line display in the profile email address and telephone chat
- Added ability to integrate similar contacts in the phone book
- Added the ability to transmit infrared applications infrared receiver
- Change the background color
- Change display Antenapikuto
- Text resize cursor display
- Improved slightly phenomenon events
How to update, download the update tool from the site WEB Sharp, PC and USB connection seems the only way to do. "
http://translate.google.com/translate?hl=en&sl=ja&u=http://maruta.be/news_japan_2100/828&ei=Pq7jTdb4DYuSuwP4x_D0Bg&sa=X&oi=translate&ct=result&resnum=8&ved=0CG4Q7gEwBw&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3Dvf4%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns
That makes a ton of sense. June 7th is when Nintendo is launching a huge update for their platforms as well, and Japan seems to like to do a ton of updates all together.
I want this so badly, I can't believe it's going to be another week.
The product page for the SH-03C over at nttDOCOMO just went 404. I really hope it's because they're busy updating with new information, and not because I'm going to be furiously angry.
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Wifi Calling! Maybe
To follow up on the question I posted earlier:
Benjam'in said:
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Click to expand...
Click to collapse
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
To follow up on my earlier post:
Benjam'in said:
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
Click to expand...
Click to collapse
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Benjam'in said:
To follow up on my earlier post:
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Click to expand...
Click to collapse
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
compu829 said:
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
Click to expand...
Click to collapse
Yes I wanted to make sure it had wifi calling before I bought it. (Thank God I know a Tmobile Reseller) - he let me play with the phone till I found out what was going on, also let me talk to someone knowledgeable (Dealer Line).
TMO did happen to land the Lumia 925 (Release in July sometime, Nokia's current flagship phone) which is what I will probably go with, although they haven't mention whether it will have the wifi calling or not, but the Lumia 521 (or something close to that, crappier version of current lumia's) will be released with wifi calling.
Which makes me hope/assume they would put it on the Lumia 925.
Good Luck to you though.
-Benjam'in
Thanks. I actually got a good deal on a sealed, NIB 8x on eBay. I desperately needed to replace my iPhone 3GS and I didn't want to go with the iPhone 5. I am guessing when the next update comes, it will have Wi-Fi calling. I heard it was in beta, and still has a major bug with "Wi-Fi only" mode (I'm guessing that's why they pulled it).
The 925 looks pretty damn sexy, though!
---------- Post added at 07:33 PM ---------- Previous post was at 06:55 PM ----------
I was actually just reading the Windows blog about the Lumia 521, and it says that WiFi calling will be delivered to those devices OTA starting on 5/20. Maybe it will get delivered to other devices as well? *crosses fingers*
Source:
http://blogs.windows.com/windows_ph...an-you-buy-for-under-150-answer-not-much.aspx
Hey there y'all!
I have a messy situation right here, looked for answers all around and coulndn't get a clue anywhere... so I'll try to explain in the clearest way possible my weird issue... (sorry for my English, will try my best to be rightfully understood)
Six days ago, I got this cute Samsung Galaxy S Fascinate SCH-i500, my cousin sent it over from the States down here to Mayan lands of Mexico... I had ZERO knowledge on Android, and in these past six days (including it's sleepless nights, and mostly thanks to this amazing forum with tons of useful resources and really helpful, cooperative people) I just learnt a WHOLE LOT about the marvels of Android devices...
First, I started rooting my SCH-i500 succesfully (yay!), then came the attempt of activation with the only local CDMA Carrier (Iusacell) and the equipment's "Homologation" (that's the term they use here for the programming cellular hospitals and workshops have to do to one's device in order to function properly with the carrier's infrastructure, no need to say this is something a little bit dumb, I consider the carrier should help their customers, specially the new ones, to set-up their data plans... I found out about carriers like Cricket who even help you with a flashing tool, if I'm not misunderstanding, to get your cellphone working with them), well, voice activation was pretty neat, 5 minutes and I had a line... be it a MDN, a MIN and the correct HomeSID for my area, and then came the "hard" part for the newbie... After trying to and succesfully figuring out how to use QPST, and hours of desperate search for faulty info on latinamerica carriers to dump to my Fascinate, I did it, for some reason I changed my ROM to "powerwashed_20_b3_Full_ec09modem.tar" and began working with it, it wasn't until today that I got 1X connection with my carrier, it was awfully slow!! managed my way to get 3G, and I DID! But it was still clumsy, only green arrow sending a lot of data and no orange incoming data to my device... which was desperating because the carrier said "they don't guarantee the phone is going to work being from another country, but I had to try and pay for a pre-paid data plan in order to make my tests... well, I knew something was not going well with the data I was using to fill the required fields in QPST... went back to my stock VZW ROM and went over and over the process of reprogramming my phone's service... I found out that VZW settings were somehow stuck to the phone, and no matter how many times I entered the info, it wasn't changing to my carriers info, I used first QPST 2.7 build 323 to fill up what was needed, uninstalled and then switched to build 215 (as I read around here) in order to get the PPP settings to stick to the device and override the Verizon old settings... and then was the nasty "nightmare-ish" moment I could never foresee... QPST threw a pop-up window marking an error, saying I was using the wrong SPC, and that I needed it for writing the QPST info to the device, THE SPC CHANGED!!! It just pops me out (in QPST as well as in the ##DATA# or anywhere in the phone) the sign: "INVALID LOCK CODE". Is that even possible? So sorry for being ignorant, but couldn't find an answer that could really solve the problem... yes, I tried CDMA Workshop with no luck at all... my cellphone actually lost contact with the carrier and had to go to the PowerWashed custom mentioned above (Im still in the network, but can't do any significant change without the SPC code)... so, any kind suggestions?? any expert around looking for helping a fast-learning noobster like me?
Hope there's something silly I'm missing because of ignorance or something like that (nothing "deadly" for the device)
Thanks a lot in advance for taking the kind time to read my long query, and for any help your knowledge may allow me to get out of the unpleasant issue
Have a great day!
My bad! I'm sorry...
Just 5 minutes ago I found this... https://play.google.com/store/apps/details?id=com.patternedsoftware.getmymsl&hl=es
and this as well... http://forum.xda-developers.com/showthread.php?t=2546659
Won't delete it, perhaps someone will suffer from the same someday (I just hope they're not as half as desperate to get their devices working properly, lol!) Sorry!
Still...
dnuuk said:
it wasn't until today that I got 1X connection with my carrier, it was awfully slow!! managed my way to get 3G, and I DID! But it was still clumsy, only green arrow sending a lot of data and no orange incoming data to my device...
Click to expand...
Click to collapse
Still, any help on this Issue could help me a lot though, thanks a zillion!