Galaxy S6 Active all day
Google Nexus 5x and 6P
541–550 of 568 posts
Re: Google Nexus 5x and 6P
#542Earlier quoted context omitted.
The thing is, internal storage isn't necessarily faster. Sure, it is on the top tier $750 and up premium-priced phones like the iPhone 6s (which has very fast internal storage). But we're talking about a much less expensive phone here. Let's compare: 64GB Nexus 6P: $549 64GB iPhone 6S+: $849 So, you really shouldn't expect the Nexus 6P to be using the top-tier internal storage solutions Samsung rolls out as used in t…
and are around 3x faster than the internal storage in my Nexus 6. They're hitting 95 MB/s read, 90 MB/s write now. Even the Moto G has that read speed. More expensive phones are much faster... http://www.anandtech.com/show/9525/the-moto-g-2015-review/3 Also, I wonder what SD read/write speeds are in practice.
Not quite. A more recent chart comparing them is here: http://anandtech.com/show/9662/iphone-6s-and-iphone-6s-plus-...
Note that everything tested is below the 90 MB/s sequential write speed of a high-end microSD except the iPhone 6s Plus.
From a review, here's the numbers on the 64Gb Sandisk Extreme Pro microSD using CrystalDiskMark:
Sequential Read : 95.325 MB/s
Sequential Write : 90.660 MB/s
Random Read 512KB : 89.314 MB/s
Random Write 512KB : 75.971 MB/s
Random Read 4KB (QD=1) : 7.492 MB/s [ 1829.0 IOPS]
Random Write 4KB (QD=1) : 2.441 MB/s [ 595.9 IOPS]
Random Read 4KB (QD=32) : 7.472 MB/s [ 1824.3 IOPS]
Random Write 4KB (QD=32) : 2.380 MB/s [ 581.0 IOPS]
Note that Ars Technica is using Sequential Read/Write values on 256K which is flawed. It should be larger to be accurate.
Re: Google Nexus 5x and 6P
#543Earlier quoted context omitted.
What can the bank app do? Mine can only deposit and view accounts, not withdraw or transfer. Open access to it would be weird, but not much worse than someone fishing my ATM receipts out of the trash to see my balance.
It's Bank of America, so it's about as feature-filled as a banking app gets. You can do all the normal stuff like check balances and deposit checks, but you can also open new accounts (including credit cards) and transfer money (between other accounts you own or to other people outside the bank). And yes, the app has the ability to add new transfer recipients, which only needs their email address or phone number. The…
This is scary enough I'm uninstalling my app just incase they add these "features" in an update. Thanks. Oh well, no big loss.
Re: Google Nexus 5x and 6P
#544Earlier quoted context omitted.
Well, if android phones still had the ability to masquerade as a USB drive (in order to move files/photos/whatever) on and off, then I could see leaving the SD card in place forever. But android phones don't currently have the ability to behave as a simple USB drive when you plug them into the computer. So if you're even a little bit discerning, and you refuse to install silly helper apps and photo-importers and andr…
As far as I can tell, the decision to remove Mass Storage had two main drivers: * The removal of SD cards from mainstream phones * The use of ext4 as a main filesystem on a lot of phones. The removal of SD cards meant that you could no longer "unmount" part of the phone filesystem to present it as a mass storage device. The use of ext4 meant that many OSes had no idea how to mount the storage, even if you presented i…
My impression was that the loss of mass storage was due to a licensing issue with fat32, wherein android (google) had to pay some little license fee to MS for each copy ...
Re: Google Nexus 5x and 6P
#545I am finally in the market for a new mobile phone - my trusty MOTO FONE (F3)[1] finally died after three years. One of my absolute no-compromise feature needs is removable media ... an SD card slot that can accept the new 128 GB cards. This is because my current music collection is 68 GB in size and carrying the entire collection is one of my use-cases. But ... I also want a non-crapware, pure android phone, and the…
Let me ask you a question - how long would it take you to listen to 68 GB or 128 GB of music? My hypothesis is, you don't actually need 68 GB of music around with you. In fact, it doesn't confer any meaningful advnatages. Using http://www.richardfarrar.com/song-capacity-calculator-for-mp... , I can see that 64 GB of music at 256 KBps is around 559 hours of music - I really doubt you'd listen to any meaningful portion…
"Let me ask you a question - how long would it take you to listen to 68 GB or 128 GB of music?"
I think you misunderstood ...
Of course I will never listen to 68 GB of music.
My entire music collection currently weighs in at 68 GB, and the use case is to have that entire collection with me. I cannot predict what I will want to listen to at any given moment and it would be a long and error-prone process to try to cull it in advance (especially if I have to cull it in half to get below 32 GB).
So I will probably listen to 3-4 GB of music in total every year (or whatever) - I just can't predict which 3-4.
Since I am above the 64 GB mark, I would need a 128 GB sd card, which are available. Further, I see the LG G4 has a 128 GB capable sd card slot and appears to be a fairly nice phone overall, so I think my dollar votes are going there.
Re: Google Nexus 5x and 6P
#546Earlier quoted context omitted.
"You have zero expertise to be saying this." This is 100% false. I do bringup on these platforms. I know a lot about them. "I'm going to favor the industry's interpretation of this a bit more than your anecdotal, occasional compiler-writer knowledge. " Dude, i literally do the toolchain bringup on these platforms you claim i have no knowledge of. This is not "anecdotal occasional compiler-writer knowledge". This is "…
This thread should embarrass you. Christ, I'm embarrassed for you . I linked multiple real world demonstrations (both the technical data, and actual observations of these cores in practice) of how big little is used for power consumption, including specific details of the core power profiles. You still allude to your great, clearly laughable, expertise and actually continue arguing this. Remarkable. You are a Hacker…
I'm not sure how many experts in how many areas of the actual phones and phone oses we are talking about have to keep telling you you are wrong before you start believing it (so far, looking at this thread, it stands at 3), but given your demeanor, as i stated, i don't really have an interest in continuing this conversation.
The fact that your response to someone like swetland is "Not to mention that their comment is simply dated and wrong now regardless." is hilariously arrogant and amazing.
I'll just continue to find it funny that you want to cite chip manufacturers (who uh, might be slightly self-serving in selling their architectures, and produce zero actual phones except for samsung. Except, of course, that the division of samsung that produces the phones is separate and does not really talk to the chip making division. I'm sure you know this), when i am talking about the actual qualification and testing of real world phones, and not "whatever random crap they made up to put in their marketing material".
You can try to gussy that up as "actual field observations of SOC vendors" or whatever, but that just shows further ignorance in how SOC vendors actually operate.
Again, I urge you: Buy an evaluation board or two. They are cheap. Put an OS on them. Try out what you claim is true. Measure the power draw. I think you will be surprised.
Have a good one!
Re: Google Nexus 5x and 6P
#547And the reference to Google-Fi is buried at the bottom of the page. Seems like they'd want to promote this feature heavily. Makes me wary of their support.
They do work with Fi: https://fi.google.com/about/
I suppose Google-Fi is still in it early, water-testing stages and they're trying to be careful not to imply that the new phones only work with Google-Fi. Still, I'm ever wary of adopting an innovation from Google. I don't change carriers often and I'd prefer not to adopt Google-Fi, only to have it be shelved a year later.
Re: Google Nexus 5x and 6P
#548Earlier quoted context omitted.
It's called long-press, a touch-screen UI pattern that has been around since at least Pocket PC, carried through on Android, and is only now appearing on iOS. Just like with right click, Apple is late to the contextual menu party.
Long-press is a different thing, and something iOS has had from the day 1 (obvious example is rearranging home screen). 3D Touch is about how much force you use, not how long you touch for.
The point is that contextual gestures are nothing new, regardless of how they are performed.
Re: Google Nexus 5x and 6P
#549Earlier quoted context omitted.
Maybe stop sitting on your phone? I've got a nexus 6 in my front pocket and it doesn't affect the way I sit. There isn't a huge market for small portable phones because most people shelling out $500+ for a smart phone want to actually use it as a smart phone. They play games, watch shows and movies, read full novels, and browse the web. These are all experiences that are enhanced by having a larger screen. My wife up…
Maybe we are all fatties that can't fit a big phone in our pocket. Or, don't use the phone that much but like access to a decent browser and apps when we do need them. I have a 4, but actually miss my ancient G2 with an actual keyboard. Damn you kids and your touch screens, you ruined everything!
What does being fat have to do with fitting a large phone in your pocket?
I totally understand why some people want a small phone. But the "I mostly make calls and only occasionally need a browser/apps" is becoming a very niche market.
Re: Google Nexus 5x and 6P
#550Earlier quoted context omitted.
This thread should embarrass you. Christ, I'm embarrassed for you . I linked multiple real world demonstrations (both the technical data, and actual observations of these cores in practice) of how big little is used for power consumption, including specific details of the core power profiles. You still allude to your great, clearly laughable, expertise and actually continue arguing this. Remarkable. You are a Hacker…
I'm not sure how many experts in how many areas of the actual phones and phone oses we are talking about have to keep telling you you are wrong before you start believing it (so far, looking at this thread, it stands at 3), but given your demeanor, as i stated, i don't really have an interest in continuing this conversation. The fact that your response to someone like swetland is "Not to mention that their comment is…
I have never commented on HN before, but this thread drew me to actually create an account. It is a great example of a conversation gone awry, and people putting personalities over facts.
As someone who works on scheduling code in one of the aforementioned architectures, inversionOf is correct on all counts, at least in regards to these architectures and power to performance. They may be rude and obnoxious, but your claims through this thread have been entirely off the mark and do not serve the community well.
Workloads are monitored for intensity. If they fall low enough they are migrated to the little core because it offers a much better total performance per unit of work. The frequency of the cores (whether big or little) are adjusted to fit the workload. If the workload is really low, we put the core to sleep. Sleep is, exactly as stated, the last possible, coarsest measure.
Sleep is not a replacement for frequency scaling. Frequency scaling achieves a half measure of what core migration achieves.
You don't have to believe my credentials, but you claim that "3 experts" have supported your stance. That simply isn't true. No one who works on scheduling algorithms for these platforms would support your claims.