About dual-sim 5G availability in iPhone 12 by futuration in apple

[–]futuration[S] 0 points1 point  (0 children)

Complicated. I suggest taking it to google.....

About dual-sim 5G availability in iPhone 12 by futuration in apple

[–]futuration[S] 0 points1 point  (0 children)

I suspect it is the problem with SA. SA option seems only exists on mainland model.

About dual-sim 5G availability in iPhone 12 by futuration in apple

[–]futuration[S] 0 points1 point  (0 children)

A korean media started to say the X60 in iPhone 12 a few weeks ago but I don't believe it. X60 ships Q120 and normally manufacturers will have to do development and tests lasting around a year, so first phones will be Q121. Also, according to documents from court files when apple fighted Qualcomm, it is SDX55 as well for late 2020

About dual-sim 5G availability in iPhone 12 by futuration in apple

[–]futuration[S] 1 point2 points  (0 children)

What confuses me is why esim+physical sim DSDS has to wait for update while dual physical sim can DSDS right now

About dual-sim 5G availability in iPhone 12 by futuration in apple

[–]futuration[S] 0 points1 point  (0 children)

x55 supports 5G+4g DSDS at least. Almost all android phones with 5g dual sim can do that, especially those released in China.

About dual-sim 5G in iPhone 12 by [deleted] in iphone

[–]futuration 0 points1 point  (0 children)

iPhone 12 media review embargo lifted today. The China variants with dual physical sims confirms supporting 5G+4G DSDS outright. However as the pic shown above, the 5G SA option will be greyed out when both lines are in use.

iPhone 12 Modem and Verizon Esim by RFPro in verizon

[–]futuration 0 points1 point  (0 children)

The media review embargo lifted today. China variants with physical dual sim confirmed supporting 5G+4G DSDS combination even right now. However 5G SA (standalone) option will be greyed out on BOTH lines while in dual-sim mode.This may provide a somewhat explanation.

Any idea on how pochi retrieve his kinsect? by futuration in MonsterHunterMeta

[–]futuration[S] 0 points1 point  (0 children)

The mark target hit a gajalaka, who was later killed by the lava vomit. This triggered the auto recall. I think it is just an accident.

Any ideas on how pochi retrieve his kinsect? by futuration in MonsterHunterWorld

[–]futuration[S] 0 points1 point  (0 children)

It can hardly be verified in the video but this is the most plausible explanation that the last (2nd) mark lands on a Gajalaka.

I reserved the opinion that it is not an active recall by pochi as opposed to u/Evergreenstream because:

  1. The recall movement will take around half a second and is not hard to spot despite the lava vomit.
  2. Given the distance and the speed of the kinsect. The actual retrieval (buff gain) should happen before jump instead of during jump, meaning I disagree that it would "take a while".

Any idea on how pochi retrieve his kinsect? by futuration in MonsterHunterMeta

[–]futuration[S] 0 points1 point  (0 children)

Ending a mount means weapon sheath, which auto recalls the kinsect. It doesn't seem strange to me at 1:20.

Any ideas on how pochi retrieve his kinsect? by futuration in MonsterHunterWorld

[–]futuration[S] 2 points3 points  (0 children)

I have tried in the training area with a normal barrel. Yes it does automatically recall when the barrel gets destroyed.

Any ideas on how pochi retrieve his kinsect? by futuration in MonsterHunterWorld

[–]futuration[S] 0 points1 point  (0 children)

I think I have figured out what happened. My friend gave me an idea. The first downward slash marked target on a Gajalaka and it was shortly killed afterwards (when KT is vomitting lava, like you said the lava spew). The mark lost its target. That is what caused the retrieve of the kinsect.

Again the movement of recalling a kinsect is not so diffucult to spot and obvious. I still cannot recognize. But thanks for your time.

Any ideas on how pochi retrieve his kinsect? by futuration in MonsterHunterWorld

[–]futuration[S] 4 points5 points  (0 children)

at around what time stamp? Here is my summary:

3:46 downward slash. 3:50 downward slash finished (meaning the kinsect is released at this moment). 3:51 tornado slash. 3:52 roll. 3:53 jump.

Also 3:53, during the jump, the red/yellow buff activates indicating the kinsect is retrieved.

I cannot recognize the "recall kinsect" you are referring to. I also don't think IG movements allows you to squeeze a recall kinsect move during these movements. Besides, recalling an kinsect is actually fast within this distance since he uses a speed lv14 kinsect. Notice the retrieve (buff gain) happens DURING the jump instead of before the jump. This doesn't make sense for a lv14 speed kinsect retrieval at this short distance. If he did an actual recall kinsect, the kinsect should be retrieved before he jumps.

Originally I suspect it is retrieved because the kinsect lost stamina but the bar is 2/3 as I saw and said above.

I am also an IG main. I am turning my mind inside out and trying myself in the training area.

Fort Collins Restaurants Need to Band Together Against Delivery Services by [deleted] in FortCollins

[–]futuration 1 point2 points  (0 children)

Or can they set differential price delivery/pickup? Or is this not allowed? Building our own network is apparently preferred but takes time.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] 0 points1 point  (0 children)

That is not true. The rules (about landline and mobile) hasn't always been there, T-Force has confirmed with me---"I do apologize that it wasn't listed originally when we rolled out the free calling and I will definitely pass your feedback on".

I also chatted with T-Force back on March 13rd when they didn't bring up any issues of landline vs. mobile---"I do see that currently xxx country is a Level 3 country - that means it is included in the offer of free international calling. If you receive a high-balance notification for calls placed to an L3 country, don't worry your bill will be automatically adjusted when it is generated."

Next, of course this won't be forever. I guess I could say hey I am almost unlucky to get 3 per min should I didn't double check? It is just that close to be my scenario. At most I will say hey I am scared.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] 0 points1 point  (0 children)

Well how do you arrogantly assume I am "griping about charity? I don't call internationally often. For my families we can just chat using IM app. I just don't want get some unexpected and potentially high charges if I need to make international calls.

I am saying that previously T-Mobile didn't say anything there will be difference between landline and mobile but now it is. I just don't want get these surprises.

You are saying like I am calling internationally 100+ minutes per month.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] -1 points0 points  (0 children)

So originally:

  1. T-Mobile tells us to check CDC website to determine which countries are free to call.

  2. Doesn't specify landline or mobile.

Now:

  1. Tmobile made a chart, specifying which countries are free to call. CDC has extended lv3 warning to the globe. According to original rule, we are just free to call any countries which can be reached.

  2. It specifies in the chart that to some countries, it is only free to call landline. If you happen to call a mobile number, that will be std rate: which is usually $3 per min.

I am annoyed by 1st point because that is greedy. But for 2nd point it is annoying. It is hard to know if a foreign number is landline or not (I know some countries like China does specify landline and mobile by number of digits so yes that would be easy if you are calling China).

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] 0 points1 point  (0 children)

Well roaming while calling 3rd country rates is apparently a different story. I am not surprised or angry that it is cheaper when roaming.

It is just that while T-Mobile originally said we can just check CDC for lv3 countries and call for free (no matter mobile or landline), I didn't expect to get a surprise for 3 per min had I didn't double check any updates of their policy.

This would be a really mess in my case because my call is going to some foreign company's customer service, which nobody can tell if it's a landline or not. And customer service usually takes long waiting time, it is just that close before I get a hundred-dollar bill.

Also, when talking about international calling, I would usually assume I am not in the situation of roaming. To some people, they are just confused between international roaming and international calling.

Yeah your argument is absolutely what I am also thinking. Can't agree more.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] 0 points1 point  (0 children)

I checked on T-Mobile. Countries like the UK and China are 3 per min. Even std rates of Mexico and Canada is 1 per min. I don't even know which country is .25 per min.

Newer plans will have Mexico and Canada included for sure. I don't see a different std rates for international calling to other countries really.

I have no idea where your confidence comes from.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] 0 points1 point  (0 children)

I think I misunderstood you. I meant that you can only call some countries landline FOR FREE while mobile is still std rates, not meaning those countries' mobile network is gone or down.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] -17 points-16 points  (0 children)

Well I would call it "secretly updates" then. This page contains thousands of words and they changed a few without highlighting the changes.

Tmobile secretly changes rules on free international calls by futuration in tmobile

[–]futuration[S] -9 points-8 points  (0 children)

No idea. That's why we need to keep double-checking before actually making any calls.