Galaxy Nexus working on Ting (M370)

In summary, Yes, I finally got it and I will document my experiences in any one wants to know how I did it.  I took some notes so that shouldn't be too hard.

Things to note:

  • I only have 1x data mode working and I suspect that is because the M370 is the donor.  Correct me if I'm wrong, please.
  • visual voicemail nor any VM notifications don't work; maybe related to the 3G provisioning issue.
  • Everything else works fine; but damn 1x data is slow.
  • Android 4.1.1 is really nice, shame Ting can't offer gnex officially.

That said; I'm not sure I'm going to keep this set-up; that 1x data is killing me.  If I'm correct and it is the donor phone profile limiting the data, I would need a donor phone like the conquer or something to achieve 3G at least.  I have a Conquer on my account, perhaps I'll try it once that phone is no longer in use.

Documentation to come if it's desired.  Meanwhile, any thoughts on the CDMA-1xRTT:7 data issue?  Is it indeed due to the donor phone data profile or can a tweak be made to get me 3G?

Update: ** Don't attempt this.  Your resources are better spent towards one of the other smart phones that TIng will have available shortly.  The Gnex has a VIA chipset so none of the usual flashing software works (QPST/QXDM, CDMA workshop, DFS CDMA Tool) because those tools are meant for qualcom chipsets.  There is only one piece of software called ETS that works with VIA chips to write data to the phone.**

The issue is getting profile 0 (3G) written to the phone; it's problematic and poorly documented.  The process is fairly easy up to that point.  There is one Ting user that claims to have working 3G; I'd ask him to please clearly document how that was accomplished.  ETS claims the data is written but it doesn't seem to take effect.

I've gone thru enough research, trial/error and a small amount of frustration to feel confident in my conclusion.   Find another toy to play with; this is not the droid you seek ;-)

 

0

Comments

17 comments
  • Sagi,

    The M370 does work as a 3G donor phone. You need to get the HA and AAA secret passwords for data profile 0. The steps for doing so are outlined here: https://help.ting.com/entries/21798151-samsung-m370-donor-phone-getting-the-aaa-shared-and-ha-shared-passwords for instructions on how to get.

    0
    Comment actions Permalink
  • Hmm, I wonder if ,it's because I used only dfs to pull the profile information? I never used QXDM, I wonder if DFS didn't give me everything or I simply overlooked somthing.

    0
    Comment actions Permalink
  • Nope, they match.  I pulled the data with QXDM and it matches what I pulled with DFS.  As far as I know, I have provisioned both profiles correctly.  Hopefully Joey will respond this week if he sees my post in his thread.

    0
    Comment actions Permalink
  • Congrats Sagi! I will do some digging and see if I can shed some light on this issue.

    0
    Comment actions Permalink
  • Meh, I'm not that concerned about it.  I'm having other issues with the phone (GPS, VVM for example) that may drive me back to my E4GT until I can muster the dollars to settle on an S3 for a long while.  While I really liked the Gnex (it was my favorite) I'm not interested in spending who knows how many more hours across X days for more tweaking.  I've got to get back to my music and web development education.

    On a Gnex flashed with donor, using google voicemail is best.  Carrier VM doesn't work correctly as far as displaying reliable notifications of new messages.  I sort of miss VVM, I used them both on the other phone.  The GPS issue is specific to Android 4.1.1, there is a small tweak that you can do that should fix it.  I know the GPS on this phone was fine when I had an ICS build on it.  3G is the big issue, everything else is a "take or leave" sort of thing.

    0
    Comment actions Permalink
  • I can tell you that 3G should work from a network perspective. Unofficially of course! ;)

    What issues are you having with GPS / VMM? Can you provide more detail?

    Thanks!

    0
    Comment actions Permalink
  • Hello Sagi,

    I can confirm that I have 3G using the M370 as a donor phone.  I used the Sprint Evo 4G as a donor phone.

    Boy, I can tell you that it took me almost a week of trying different things.  During that time, the "1x" data connection just about made me quit.

    Hang in there.  You will get 3G and notice a big difference in data speeds when you get it.

    Here is the link that Aaron posted above.

    https://help.ting.com/entries/21798151-samsung-m370-donor-phone-getting-the-aaa-shared-and-ha-shared-passwords

    Questions:

    1) Did you get Profile-0 and Profile-1 passwords extracted?

    2) Were they different?

     

    I will be going to work shortly, but will check here as time permits to answer your questions. 

    0
    Comment actions Permalink
  • Yeah, I'm certain I have the profiles extracted correctly.  I checked with two different programs.  Unfortunately, I can't use those same programs to write the profiles to the Gnex.  That is because of the modem chipset being a VIA; one has to use something called ETS and at first it was awful.  I got the hang of it and was able to enter the profiles and the HA and AAA passwords.  No 3G.  The HA passwords were different for both profiles but the AAA were the same; I may have that reversed in my memory.  There are so many commands in that ETS program it's entirely possible I missed something.  I've gone over all available information, 3G should be working but it isn't.  Clearly, I've missed something or goofed some where.

    Scott:  I had to download another version of the visual voicemail app that didn't have the redraw issues.   That part is fine now and the app seems to function as intended.  However, VVM doesn't update when new messages are deposited into VM.  I had to tell android to use carrier VM but the notification that there is a new VM is always there, even when there isn't.

    The GPS issue relates to the phone seeing the sats but not locking.  It has to be something with the rom I'm using because it was fine earlier.  The tweaks suggested aren't working though.  I went thru the nonsense of having a goofy GPS on my other phone.  If I can't get it working on the rom I finally intend to use; I'll just drop the issue entirely and go back to my old phone.

    0
    Comment actions Permalink
  • Scott Allan:  I got 3G now, as far as the icon is concerned but the download speeds are awful.  As slow as it was before; could be the area, I'm not sure.  The data rate listed in the about section is listed as 1xRTT:6 instead of 7.  I'll have to give it more time to see if it gets any better.  In this room I know my Ting S2 performed much better on 3G; I guess that is the trade off for going donor?   It's slow enough that getting directions and what not seems to be spotty.  Wasn't that way on the old phone.   Could just be hardware differences in the Gnex radio vs S2. I dunno.

      I had to use odin to do a stock restore of FC12 firmware.  After reboot, I found I had 3g and didn't have to do anything else.  I then allowed the phone to do it's network updates so now I have a stock Sprint Gnex fully updated via OTA releases from sprint.  The GPS is fine as well; the JB rom I was using must have been the issue; I'm not certain.

    What isn't working is new voicemail notifications.  Not by the default anroid caller app nor by the visual VM app.  I even tried sending a message to activate@vvm.sprint.com from the VVM app; didn't seem to help.  I had thought that would correct itself once 3G was provisioned correctly, guess not.

    0
    Comment actions Permalink
  • I believe visual voicemail is a sprint app that only works with sprint service.

    0
    Comment actions Permalink
  • Perhaps, though technically we are using Sprint service.  Even so, I should still get notification from the android system itself if not the VVM app.  I got no indication there is a new VM from anything.

    0
    Comment actions Permalink
  • @Sagi,

    Your 3G icon story sounds familiar.

    I also recall thinking that I had 3G because the 3G icon showed up. That was before I had correctly set the Profile-0 password.

    I found that when running the HTC stock Sense ROM, it always showed a 3G icon even if connected to 1x.

    However, when I flashed an ICS Cyanogen Mod ROM, it does show a "1x" icon or a "3G" icon depending on the actual data connection.

    One way you can test you data connection speed is to run the SpeedTest.net app, I found that I had 1x speeds.

    https://play.google.com/store/apps/details?id=org.zwanoo.android.speedtest&feature=nav_result#?t=W251bGwsMSwyLDNd

    My SpeedTest results were for 1x data were:  60kbps to 100kbps download

    After finding and setting the Profile-0 passwords for 3G data, my new speeds are now:  400kbps to 600kbps 

    Joe...

    0
    Comment actions Permalink
  • I found and verified the AAA password for profile 0 via DFS and QXDM, I made sure they matched and I wrote them to the Gnex the only way available.  If the issue is that the AAA isn't being written when the program says it is, there isn't anything I can do about it.  As I said, the galaxy nexus works on a VIA chipset.  None of the nice tools that work on the qualcom phones (most of them) work on the Gnex.

    The M370 as a donor phone is excellent and will work well for anyone qualcom based phone.  

    There are too many people having issues with getting 3G working with donor phones; I suspect there is something not clear or wrong with the process of writing the donated profile 0 to the phone.  There was one Ting user that claimed to have 3G working; I'd like to know how they did it.  I'm betting VM won't work correctly without a properly provisioned 3G profile these days.  It's not really an issue because not Gnex users are on a GSM network, for good reason.

    Ah well,  I tried though it sucks I wasted a fair bit of time and money in the process.  I was certain I would be able to do it.  Dunno, it should work but it doesn't and I'm certain (as best as I can tell) it's not a mistake on my part.  I've checked too many times to think that now.

    0
    Comment actions Permalink
  • @Sagi:

    Sounds like you have been very thorough.

    I agree with you it must be something in the way the HA/AAA Shared passwords are not being written to the GNex.

    Wish I had one to help you with it.

    I am sure some one else here will chime in with some ideas.  

    0
    Comment actions Permalink
  • 1) Have you looked over the information in this thread regarding VIA chipset CDMA repair? It looks like there is a way to change BOTH profile 0 and 1 HA/AAA passwords on the device itself: http://forum.xda-developers.com/showthread.php?t=1696621

    2) What PRL are you using? If you have the 3G icon but still 1X data, it could be a PRL issue. The thread above also shows how to manually update a PRL. I am on 60687 on my Nexus S from a M370 hermit crab.

    0
    Comment actions Permalink
  • Sorry, it may not be on the device itself. I'm not familiar with this chipset, but maybe this info can help you determine if the phone actually saved the profile passwords.

    0
    Comment actions Permalink
  • I never manually updated the PRL.  I did exchange several private messages with the thread starter after going thru that whole thread.  To which post numbers were you referring when you made your suggestion?

    FYI, yes you can change the data profile manually from the phone directly.  It's handy but the passwords are not in plain text so I could never tell if they were correct save by trusting what that ETS program was telling me.  I never tried entering them that way into the phone.  Perhaps I'll try again next week along with manually updating the profile.

    0
    Comment actions Permalink

Please sign in to leave a comment.