Jump to content

Google Nexus 5 by LG Preview (LG D820)


MacinJosh

Recommended Posts

Posted Image

 

These android kitkat bars are gonna be huge in Japan. I expect a green tea android kitkat bar to follow. They already make the flavor. They make about every other flavor. Maybe a key Lime Pie kit kat bar to make the disappointed happy.

 

Sent from my SPH-L710 using Tapatalk 4

 

 

  • Like 2
Link to comment
Share on other sites

It could be a political decision, retribution for VZW. Or it could be a technical reason, since band class 13 is the only one of the bunch that has an inverted FDD downlink/uplink.

 

AJ

Interestingly, if you look at the image in post #58, you'll see that the low band antenna on the the device is connected to a four position switch, with only 3 positions of which are being used (cellular+smr, gsm900, and LTE b17). Assuming the rest of the rf components can handle the inverted link setup, it shouldn't be difficult to adapt the design to add support for VZW's LTE band as well.

Edited by GoWireless
Link to comment
Share on other sites

I hope they are wrong but those @evleaks guys are pretty reliable.

Doesn't make any sense because of where the camera hole is situated. Plus, there is already an approval for a CDMA model that S4GRU covered on the front page that appears to be the "real" CDMA G2.

Link to comment
Share on other sites

Doesn't make any sense because of where the camera hole is situated. Plus, there is already an approval for a CDMA model that S4GRU covered on the front page that appears to be the "real" CDMA G2.

Maybe someone from Google is trying to use them to throw off the public since the FCC filing pretty much list all the specs.

Link to comment
Share on other sites

The evleaks info just doesn't make sense. The Sprint G2 already passed thru the FCC and this lacks Verizon LTE bands so it's obvioiusly not a VZW device. Also the screen size 4.96" vs 5.2", battery size 2300 vs 3000 mah, camera position and no backside power button.

 

I think Google is using evleaks for damage control. I'm not buying it. 

  • Like 5
Link to comment
Share on other sites

Evleaks is usually pretty solid, but they seem to be wrong on this one. It may not be a Nexus, but it definitely isn't the G2.

 

Sent from my SPH-L710 using Tapatalk 4

I agree, the evidence demonstrated here on S4GRU is more comprehensive and convincing. The evleaks screenshot may just have placeholder photos, it's not persuasive at all

 

Sent from my LG-LS970 using Tapatalk 4

 

 

Link to comment
Share on other sites

The reference to hammerhead and key Lime Pie is pretty convincing it's the nexus. And the wireless charging and non removable back. It's def not the g2. It may not be the nexus but it's def not the g2.

 

Sent from my SPH-L710 using Tapatalk 4

 

 

Link to comment
Share on other sites

As an aside, does anyone know of any upcoming Google events that would announce this phone if it was a new Nexus device?

 

Don't worry Google will host an event when the time is appropriate.  I would expect the event in early in November like last year with invites/leaks about the event to be announced in mid-late October.

Link to comment
Share on other sites

I have a very hard time believing evleaks this time. Someone paid them off to post that. The question is, why? Are they that mad that we pulled this off so well, putting 2 and 2 together with the video clip that Google outed the next Nexus and then the FCC outed the D820 only days later?

Link to comment
Share on other sites

I think it's time for a new article that calls out evleaks. Time for more traffic! :D

 

Whatever the hell evleaks is, it is probably wrong in this instance.  The circumstantial evidence that the LG D820 is a Nexus device is substantial, and the big tech press has largely agreed with our inductive inference.  That said, we have no further evidence with which to challenge evleaks' refutation.  So, there will be no article on that topic.

 

We do not have the resources, connections, and invitations that the big tech press does.  Yet, because we follow the FCC OET closely for future Sprint devices, we still broke the story on the potential Nexus 5.  That was our impressive win.  The big tech press, though, will tell the rest of the next Nexus story as it evolves.  We simply cannot compete with those big tech press advantages -- at least, not yet.

 

AJ

  • Like 2
Link to comment
Share on other sites

Whatever the hell evleaks is, it is probably wrong in this instance.

...

AJ

evleaks is pretty well known. I agree, I also think he is wrong this time.

 

 

http://www.androidpolice.com/2013/06/28/evleaks-revealed-android-polices-exclusive-interview-with-evan-blass-the-man-behind-evleaks/

 

 

Sent from my LG-LS970 using Tapatalk 4

 

Edited by djw39
  • Like 1
Link to comment
Share on other sites

evleaks is pretty well known. I agree, I also think he is wrong this time.

 

My advice to everyone.  If you want to be well known, use your own damn name.  What is the "evleaks" crap supposed to mean?  Yeah, I am known as "WiWavelength" around the Web, but I still sign every post, as I do not hide behind a nom de plume.

 

AJ

  • Like 2
Link to comment
Share on other sites

Well if he used his real name he wouldn't be much of a leaker. We'll not for long at least. :)

 

I highly doubt it.  I am not sure what the "ev" in "evleaks" is supposed to mean, but the name is obviously a copycat of WikiLeaks.

 

But these device leaks are not the kind of info that prompt law enforcement and/or prosecution.  If anything, the OEMs enjoy the fevered anticipation and free publicity.

 

AJ

Link to comment
Share on other sites

My advice to everyone.  If you want to be well known, use your own damn name.  What is the "evleaks" crap supposed to mean?  Yeah, I am known as "WiWavelength" around the Web, but I still sign every post, as I do not hide behind a nom de plume.

 

AJ

evleaks = name of the guy is Evan Bass.  ev is just his first two letter of first name.

Edited by tigmd99
Link to comment
Share on other sites

I highly doubt it. I am not sure what the "ev" in "evleaks" is supposed to mean, but the name is obviously a copycat of WikiLeaks.

 

But these device leaks are not the kind of info that prompt law enforcement and/or prosecution. If anything, the OEMs enjoy the fevered anticipation and free publicity.

 

AJ

I meant more like he wouldn't get as many leaks from his sources. But the article above reveals who he is finally. Ev stands for Evan. Interesting read. He still seems off on this one. Looks like he assumed 820 and 821 were the same thing.

 

Sent from my SPH-L710 using Tapatalk 4

 

 

Link to comment
Share on other sites

I highly doubt it. I am not sure what the "ev" in "evleaks" is supposed to mean, but the name is obviously a copycat of WikiLeaks.

 

But these device leaks are not the kind of info that prompt law enforcement and/or prosecution. If anything, the OEMs enjoy the fevered anticipation and free publicity.

 

AJ

Guys he is not secret, his name is Evan Blass and he is profiled at the link in my last post. He was a senior editor at Engadget and managing editor at pocketnow for many years.

 

Sent from my LG-LS970 using Tapatalk 4

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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