Jump to content

Samsung Galaxy S8 & Dual Sim/Duos


Andrew Revering

Recommended Posts

Such a rogue update, haven't been updated since August and now we get one with an old security patch...
Yeah I'm looking forward to Android 8.0 and upload CA

Sent from my SM-G950U using Tapatalk

Link to comment
Share on other sites

Is there any way to force "band class 10" i.e. 800 MHz voice on the S8?

I see that you can disable BC10 under ##DATA#  but I would like to force it on.

The reason is that 1900 MHz voice calls here always warble slightly here  (occasional audio glitches and dropouts) on any phone.  We are surrounded by tall trees so maybe that is the problem.  Or it could be something else but it has been that way for years.

When I do get 800 MHz on a voice call, there is no such problem.  Actually I have another phone (a Tribute HD) that seems to like using BC 10.    Maybe I should just move my main number  over onto it.

I can use LTE Calling but I have a magic box so there is some latency and it can glitch sometimes too.

Thanks.

 

 

 

 

 

 

 

Edited by comintel
Link to comment
Share on other sites

Is there any way to force "band class 10" i.e. 800 MHz voice on the S8?
I see that you can disable BC10 under ##DATA#  but I would like to force it on.
The reason is that 1900 MHz voice calls here always warble slightly here  (occasional audio glitches and dropouts) on any phone.  We are surrounded by tall trees so maybe that is the problem.  Or it could be something else but it has been that way for years.
When I do get 800 MHz on a voice call, there is no such problem.  Actually I have another phone (a Tribute HD) that seems to like using BC 10.    Maybe I should just move my main number  over onto it.
I can use LTE Calling but I have a magic box so there is some latency and it can glitch sometimes too.
Thanks.
 
 
 
 
 
 
 
I don't think so... I have the same issue as you with 1900 not penetrating deep in to my house. 800 was always fine. I ended up switching the Magicbox out for an Airave 3 LTE as it also boosts the 1x Voice.

Sent from my SM-N950U using Tapatalk

Link to comment
Share on other sites

This is pretty weird.

I have been testing around town and my Samsung S8+ (prl is 56066) is always given 1XRTT for voice which is problematic at home  because it warbles and glitches every now and then duuring calls..

My LG LS676 Tribute HD (prl 55065), on the other hand, is always given 1X800 which is flawless.

It seems like to get consistent voice quality, I have to give up using my S8+ for calls!

Does this make any sense?

 

 

 

Link to comment
Share on other sites

Just now, Terrell352 said:

Can you still use it?? Also the November patch came with it.

Sent from my SM-G955U using Tapatalk
 

Can make call on Wi-Fi and hand off to LTE.  Unable to start calls on LTE though.

Link to comment
Share on other sites

2 hours ago, bucdenny said:

New update today?

LfBpCbq.jpgpDE7D1Y.jpg

Same update size this time with the 955U1 model.  

As for the VoLTE option, I reported it as broken via Samsung Members during Beta 2 and they said they'll look into it.

Link to comment
Share on other sites

On this new beta 3, I noticed my S8+ rather quickly switches when I am on B25 to B41.  I am seeing myself on B41 in areas where usually I see B25 with very strong signals.  

e.g. B25 with strong signals of RSRP of -55 to -65 (next to a macro site) with neighboring marco with B41 in the area of around RSRP -105, it will switch over to B41.  

Anyone seeing similar results?

  • Like 1
Link to comment
Share on other sites

On this new beta 3, I noticed my S8+ rather quickly switches when I am on B25 to B41.  I am seeing myself on B41 in areas where usually I see B25 with very strong signals.  
e.g. B25 with strong signals of RSRP of -55 to -65 (next to a macro site) with neighboring tower B41 in the area of around RSRP -105, it will switch over to B41.  
Anyone seeing similar results?
I am also.

Sent from my SM-G955U using Tapatalk

  • Like 1
Link to comment
Share on other sites

So, uh, how's that beta3 treating folks still??  I don't see how to re-enroll in the beta after rolling back. I would think they would let folks re-enroll though so they could try out features that had pushed them away, ie, more testers for actual problems. I guess not though.

Link to comment
Share on other sites

So, uh, how's that beta3 treating folks still??  I don't see how to re-enroll in the beta after rolling back. I would think they would let folks re-enroll though so they could try out features that had pushed them away, ie, more testers for actual problems. I guess not though.
It's better but there are still issues that they said they fixed like the youtube not loading issue that still is happening.

Sent from my SM-G955U using Tapatalk

  • Like 1
Link to comment
Share on other sites

9 hours ago, mmark27 said:

So, uh, how's that beta3 treating folks still??  I don't see how to re-enroll in the beta after rolling back. I would think they would let folks re-enroll though so they could try out features that had pushed them away, ie, more testers for actual problems. I guess not though.

It's been the most stable and smoothest one so far.  Besides quicker battery drain, which was expected, I'm having no issues.  Beta 3 finally fixed the microSD issue which was bugging me through Beta 1 and Beta 2.  

  • Like 1
Link to comment
Share on other sites

For those back on the non-oreo stable build, since the update to QJH firmware my wife's S8 and my folks' S8 actives (thankfully not my S8+) have been doing the cycling screen on thing when on the wireless charger. Meaning.....phone on wireless charger charges up to 100%, screen pops on. That's normal once. Then as the phone discharges and charges that little bit, the screen would never turn back on all night (nor would the charger light up). Now though, their phones will light up about every 10-30 seconds all night long. It seemed to do this with my wife's S8 while plugged in even. 

Some folks have been complaining about fast charging not working post update, but wasn't sure if anyone was also seeing this issue. It's probably the most annoying bug. The beta was doing it on my phone and was one of the reasons I rolled back to stable. Then the update came and their phones started doing it. 

Anyone else? 

Link to comment
Share on other sites

2 hours ago, mmark27 said:

For those back on the non-oreo stable build, since the update to QJH firmware my wife's S8 and my folks' S8 actives (thankfully not my S8+) have been doing the cycling screen on thing when on the wireless charger. Meaning.....phone on wireless charger charges up to 100%, screen pops on. That's normal once. Then as the phone discharges and charges that little bit, the screen would never turn back on all night (nor would the charger light up). Now though, their phones will light up about every 10-30 seconds all night long. It seemed to do this with my wife's S8 while plugged in even. 

Some folks have been complaining about fast charging not working post update, but wasn't sure if anyone was also seeing this issue. It's probably the most annoying bug. The beta was doing it on my phone and was one of the reasons I rolled back to stable. Then the update came and their phones started doing it. 

Anyone else? 

Never experienced that bug on the Oreo beta.  And I only use wireless charging (Seneo fast charger).

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...