Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,717
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by ingenium

  1. Yes I noticed the same thing in Emeryville and Oakland near the Bay Bridge. You should contact Sprint's customer support. Tell them you are having audio quality issues and you want to file a ticket.

    I posted on their support forum about a week ago telling them the issue and giving them site IDs. Never got a response. But yeah I should call them as well and open a ticket.

     

    Sent from my SPH-L720 using Tapatalk

     

     

  2. Has anyone else noticed issues with 1x 800 in the area? In Emeryville ever since they turned on 1x 800 around Thanksgiving, my call quality has been horrible (cutting out constantly) and texting very unreliable (get stuck sending, sending multiple copies, etc). I have a non-triband Galaxy S4, so it's not a CSFB issue. I verified that calls were indeed using the HD voice codec as well.

     

    I modified my PRL to prioritize 1900 over 800 for SID 4183, and the problems went away. My phone is connecting to the same towers as it did for 1x 800 according to Signal Check Pro. So the only difference is 1900 vs 800.

     

    Is anyone else seeing this? What could be the reason for it?

     

    Sent from my SPH-L720 using Tapatalk

     

     

  3. This makes sense, but then why does the phone connect to 1x 800 when it drops to 3G on 1900 in the same area? Sent from my Nexus 5 using Tapatalk

    The network may just move the phone to 800mhz for some reason.

     

    Or it's prioritized in the PRL. It seems some official PRLs keep 1x 800 and 1x 1900 at the same priority, but my current stock PRL has 1x 800 at a higher priority than 1x 1900. So I always connect to 1x 800 even if it's a weaker signal than 1900 (800 is only on some of the towers in my area).

     

    I do notice that 1x 800 seems to cut out more during calls, even with a signal stronger than - 78db according to Signal Check Pro... Not sure why this happens, but I get better call quality on 1900.

     

    Sometimes the 800 signal is practically unusable with the audio cutting out a lot, but my phone usually switches over to 1900 after a minute or so on the call if 800 is too weak.

     

    So it's not necessarily a bad thing your phone is using 1900, sometimes it's actually better.

     

    Sent from my SPH-L720 using Tapatalk

     

     

  4. EDIT: I think i misunderstood your question.... For the handsets it requires new hardware, for the tower it is just software.

     

    Nope, LTE-Advanced requires a modem that can support it. Currently Qualcomm has 2 modems that support LTE-Advanced: the MDM9625 and MDM9225. Also, those modems only support LTE-Advanced carrier aggregation over 2 10Mhz carriers. The upcomming Snapdragon 805 chip includes the MDM9x35 series modem that has full LTE-Advanced capability.

    So does that mean if Sprint's version of the Galaxy S5 ends up having a Snapdragon 805 that it will, at least eventually, be able to use LTE-A and/or carrier aggregation?

  5. I haven't noticed speed issues, but I've been having SMS issues (my roommate has the same issue, different phone). Basically texts get stuck sending. You can try resending it all you want but it won't send unless you change it somehow. Just adding an extra space somewhere is enough to cause it to send right away.

     

    It's been happening for about 2 weeks now, pretty frustrating.

     

    Sent from my SPH-L720 using Tapatalk

     

     

  6. Does anyone know why some towers have 1x 800 but haven't had LTE added yet? There are quite a few in Emeryville, west Berkeley by the freeway, and Oakland near MacArthur BART that have 1x 800 but no LTE. Is this just because they haven't upgraded the backhaul yet for some reason?

  7. The issue is that the nearby towers are broadcasting at 800Mhz. The current PRLs (as of 54016/55016/56016) always prioritize 800Mhz over 1900Mhz, so it won't switch to 1900Mhz unless the 800Mhz tower tells it to, or the signal is non-existent (like how the phone hangs onto a Sprint signal until it can't anymore before roaming).

     

    Airaves seem to only broadcast a 1900Mhz signal. There's a rumor that a software update is being pushed out (though it has supposedly been pushing "soon" since August...) to make it broadcast an 800Mhz beacon telling the phone to switch to 1900Mhz, but to my knowledge this hasn't happened yet. I ended up modifying my PRL to put my airave at the top of my region above the 800Mhz towers (http://s4gru.com/index.php?/topic/2440-airave-evo-4g-lte-data-connection-but-not-voice/&do=findComment&comment=60555) and it worked great. If you use that guide, be sure to get the correct info for your airave and local towers (I used https://play.google.com/store/apps/details?id=com.blueline.signalchecklite).

     

    On the Galaxy S4, you don't even need root or the MSL to write the PRL, it can be stored on the SD card and written using a hidden interface. Other phones may be similar.

  8. OK, so I've verified that 850MHz WCDMA/HSPA+ indeed works, but you have to force it. For some reason it really wants to use GSM/EDGE. I had to go into the Testing service menu (normally *#*#4636#*#* in the dialer, but Samsung disabled it. I used a Nova Launcher shortcut, or there are apps in the Play Store to access it) and force it to only use WCDMA (selecting WCDMA preferred doesn't work, it will still choose GSM over WCDMA). 

     

    2013-07-27 01.27.26.png 2013-07-27 01.27.47.png 2013-07-25 12.12.34.png

     

    That all said, I wasn't able to get SMS working for some reason. I could receive messages just fine, and make and receive phone calls just fine, but I got an error any time I tried sending a text. In the attached screenshot I was trying to activate a higher speed data package. I think it may have had something to do with the carrier though (in this case the Costa Rican carrier Kolbi), because I put the SIM in my 3G Nexus 7 and installed an SMS application and got the exact same error. I read that the usual reason was the Message Center/SMSC wasn't set properly, but I verified that wasn't the cause. 

    2013-07-25 13.49.07.png

  9. Did you make the build prop edits I suggested in an earlier post? When I did those and had my foreign SIM in (Orange - IL), I was able to access the APN Menu and make changes to get Data working. When I got home and had my Sprint SIM in I noticed the menu was gone. Unfortunately I left the SIM for my brother who is staying longer (he has an iPhone) so I can't put it in again to see if the APN Menu is enabled to confirm my theory.

     

    I think it has to be an android thing, in <4.0 APN editing was available unrooted but now it seems to have been disabled. Was also a much easier process to unlock foreign SIMs using the iPhone over GS4. I guess iPhone is just significantly more user friendly for using an international SIMs. I dont travel often so this isnt a deal breaker for me. 

     

    Also was easy enough to get phone working again back in the US. Just wish I didn't have to call sprint to do it..

     

    Oh nice! I hadn't seen your post about the build.prop edits. It worked flawlessly for me. I use Nova Launcher rather than the Touchwiz launcher, so I was able to add a shortcut on my homescreen to access the APN settings with the Sprint SIM in. I can switch between any of the 5 built in Sprint APNs (4 domestic, 1 for global roaming), and the ability to add new APNs is no longer greyed out. Thanks!

  10. Rooting was easy and it wasn't too difficult to change the apn once rooted. I also have an unlocked iPhone 4S on Verizon and the process was much much simpler for the iPhone. Literally popped the sim in and you're good to go.

     

    Sprint/Samsung need to enable auto updating of APN's with a new SIM card like the iPhone or at least enable users to manually update without rooting.

     

    When I got back to the US my apn menu disappeared even though it was working when I was out of the country, must need a foreign sim in for that menu to show up even while rooted. Not getting data connection at all in the US now. Will try to flash back to stock and report how it goes.

     

    What ROM were you using? Just stock rooted, or one of the customized ROMs?

  11. What you are trying to do is not possible without rooting in the MDL and MDC firmware versions. However, there's a new firmware with a lot of updates that came out yesterday and it's possible that Sprint enabled APN access in it.

     

    Just updated to MF9, and the APN settings are still greyed out. 

  12. APNs are stored as an XML configuration file, if I remember correctly.

     

    It should be under /etc/apns-conf.xml

     

    Those are the system APNs, the ones that come pre-configured and will remain after a factory reset. When the user adds an APN it can't be stored in that file since it doesn't persist with a factory reset (and I believe /etc is mounted read-only). It appears that there are 2 locations for APNs, one for system provided APNs and one for user provided ones. I THINK that /etc/apns-conf.xml is used to initially generate /data/data/com.android.providers.telephony/databases/telephony.db. On my Nexus 7 at least, when I manually added an APN it showed up in this database and not /etc/apns-conf.xml. 

     

    The question is though will just adding the APN to this database be sufficient for it to show up and be used? I think it is, but I won't have the opportunity to test it until the end of the month. I'll be traveling to a country with UMTS/HSPA 850, so I'll report back if I was able to get data to work.

  13. I found a sqlite database file that looks like it has the APN information in it. Would it be possible to just edit this (with root) and add the APNs manually? I don't currently have a 3rd party SIM and I'm in the US, so I don't think added APNs would even show up in the list if the MCC/MNC doesn't match a signal it sees. 

     

    The file in question is /data/data/com.android.providers.telephony/databases/telephony.db

     

×
×
  • Create New...