|
Huge difference between 2GB and 3GB of RAM right now, despite the fact that android is supposed to use the optimal amount depending on how much RAM you have. 2GB is definitely a deal breaker for the supposed google flagship.
If you don't multitask I suppose 2GB is fine, enough to run all apps smoothly. However the 4GB I have on my Zenfone 2 is just a multitasking dream while 3GB on the Galaxy S6 is enough for a few apps to run concurrently without any closing to free up RAM for others. Take a look at this multitasking shootout between the S6, Note Edge, and Zenfone 2.
www.youtube.com
|
On September 29 2015 01:33 Excalibur_Z wrote: I'm super, super wary of devices from Asus, Lenovo, even Huawei pre-Nexus 6P. It's not that their hardware is weak by comparison, they're actually quite comparable. It's that they don't have the market share, and therefore influence, necessary to pressure developers into maintaining compatibility with their device, so on the Google Play Store, a lot of those budget devices tend to go blacklisted. It's kind of an unfortunate reality with any smartphone marketplace: if you're a developer using some mainstream API that's not compatible with some chipset, then you have no choice but to exclude devices under that chipset (there was a huge high-profile debacle over this exact thing with the Tegra 2, so a lot of those really nice devices had to miss out on some great apps). When your market is dominated by Samsung/Nexus/top-end iPhones, you have to support those or you're not going to recoup on your investment. If that means having to exclude some Asus Transformer tablets which are great despite some niche incompatibility, then that's the way it's going to be =( I will keep my eye on that new Asus device though, just in case.
Could you elaborate further on your point? Are you saying the play store doesn't work on certain devices from smaller manufacturers just all together? I thought android was supposed to be a lot more modular than ios and supports a full range of devices by default?
I'm only planning to use my current zenfone 2 for about ~3 years anyway, so could I expect the possibility of my phone failing to open the play store sometime into the future?
|
I guess he is talking about some apps not being developed for some "obscure" processors like the Atom
Im pretty sure most apps and the mainstream ones would have no problems tho, but its still a possibility
|
On September 30 2015 05:16 EngrishTeacher wrote:Huge difference between 2GB and 3GB of RAM right now, despite the fact that android is supposed to use the optimal amount depending on how much RAM you have. 2GB is definitely a deal breaker for the supposed google flagship. If you don't multitask I suppose 2GB is fine, enough to run all apps smoothly. However the 4GB I have on my Zenfone 2 is just a multitasking dream while 3GB on the Galaxy S6 is enough for a few apps to run concurrently without any closing to free up RAM for others. Take a look at this multitasking shootout between the S6, Note Edge, and Zenfone 2. www.youtube.com That is easily one of the least useful tests of a phone I have ever seen.
Normal apps (that is, things that aren't written in C++ and don't request a large memory heap) get locked to a maximum amount of memory. If they exceed that amount of memory, they will crash. This amount is set by the OS (and therefore changeable by the device manufacturer to suit their device's needs). The default value in Lollipop was something like ~116MB. If we take a 2GB device, even if we knock off 512MB of ram for the OS (which is definitely high at this point), that leaves 1536 / 116 = ~13 fully allocated processes. Do you use 13 apps at once that all allocate the maximum possible memory? I reeeeeally doubt it.
Is more RAM nice? Sure, of course. Should having only 2GB of RAM be a dealbreaker? Probably not.
|
United States12240 Posts
On September 30 2015 05:21 EngrishTeacher wrote:Show nested quote +On September 29 2015 01:33 Excalibur_Z wrote: I'm super, super wary of devices from Asus, Lenovo, even Huawei pre-Nexus 6P. It's not that their hardware is weak by comparison, they're actually quite comparable. It's that they don't have the market share, and therefore influence, necessary to pressure developers into maintaining compatibility with their device, so on the Google Play Store, a lot of those budget devices tend to go blacklisted. It's kind of an unfortunate reality with any smartphone marketplace: if you're a developer using some mainstream API that's not compatible with some chipset, then you have no choice but to exclude devices under that chipset (there was a huge high-profile debacle over this exact thing with the Tegra 2, so a lot of those really nice devices had to miss out on some great apps). When your market is dominated by Samsung/Nexus/top-end iPhones, you have to support those or you're not going to recoup on your investment. If that means having to exclude some Asus Transformer tablets which are great despite some niche incompatibility, then that's the way it's going to be =( I will keep my eye on that new Asus device though, just in case. Could you elaborate further on your point? Are you saying the play store doesn't work on certain devices from smaller manufacturers just all together? I thought android was supposed to be a lot more modular than ios and supports a full range of devices by default? I'm only planning to use my current zenfone 2 for about ~3 years anyway, so could I expect the possibility of my phone failing to open the play store sometime into the future?
It's not that the Play Store itself doesn't work, it works on all devices all the time. The apps on the Play Store are just made by developers, and those will have varying levels of support based on the capabilities of the dev team. Those capabilities can range from in-house device inventory (if a dev team has direct access to a device and can reproduce the issue, they are more likely to discover a solution and verify any fix attempt) to engine/library usage to OS/resolution requirements to bugfix ROI/management, there are just so many factors.
Some development software (or rather, the renderer utilized) is just incompatible with some hardware. If you have a device with a Tegra 3 and the render method you're using for your app or game requires an ARMv7 NEON coprocessor for whatever reason (usually to boost performance), then the device will fail to render and you'll get a black screen or a crash on launch. It's no different from the Wild West era of PC gaming, where you couldn't run an OpenGL game on your ATI Rage II+ because that GPU didn't support OpenGL (it had its own proprietary renderer) and your 3Dfx OpenGL card couldn't run PowerVR-specific games.
Now, the question is how do you manage the issues? You have to sort them by priority: - Hardware incompatibility, like the Tegra 3 example I gave above. This is a hard stop. You'd basically have to rewrite your entire engine to get this to run. Not feasible. Solution: blacklist that family of devices in the Play Store (this makes your app invisible to those devices, and if for some reason they can access the page such as via direct link, it tells the user the device is incompatible) - OS incompatibility. Some older OS versions don't support some of the newer engines out there. Solution: blacklist all devices below your minimum API Level. - Poor Performance. Some device specs may be too low to properly run your game. Maybe they strain the hardware too much and crash, or just run at a low framerate. Solution: run a cost-benefit analysis of doing a performance improvement pass on your next update, or if it's not feasible, blacklist the affected devices.
This problem isn't limited to Android, by the way. Many older iPhones can't run the newest and most hardware-intensive games. However, Apple doesn't allow developers to exclude support simply due to poor performance, or even due to crashes. Instead, they only allow exclusion based upon OS level and certain hardware requirements. So, your app has to support iOS 8+ or 7+ or 6+ or whatever you choose. One really egregious and unscrupulous example that a lot of developers use is to claim their game or app requires the front-facing camera only found on iPhone 4S and above, even if it doesn't, just so the poorer-specced iPhone 4 gets excluded from the supported device list.
So, if you're developing an app, it makes financial sense to just target the devices that have the greatest market share. Not necessarily to only focus on those devices, but at least to prioritize them to make sure they're supported. Would you rather have the 1% of users running the Galaxy S II to tell you that "your app crashes and sucks, do not download, 1 star", or the 20% of users running the Galaxy S 6? It's a numbers game. Some developers have the capability through various means to support a wide range of devices, others do not. At least if you have a flagship device you can feel safe that developers are bending over backwards to make sure their app is compatible.
|
Lalalaland34496 Posts
On September 30 2015 01:36 Faruko wrote: NEXUS 6P: 1440P AMOLED; Snpadragon 810; 2Gb Ram; 16/32/64gb 32GB $499 64GB $549 128GB $649
NEXUS 5X: 1080P IPS LCD; Snapdragon 808; 2Gb Ram; 16/32gb 16GB $379 32GB $429 Nexus 6P has 3GB of RAM.
|
fixed !
I think the old Nexus 6 with its reduced price of $350 feels like a much much better option than the new Nexus phones
|
at this point if you don't care about screen size & huawei making the hardware i'm certain that the n6p 32gb is a farrrr better deal than the n5x.
On September 30 2015 11:48 tec27 wrote:Show nested quote +On September 30 2015 05:16 EngrishTeacher wrote:Huge difference between 2GB and 3GB of RAM right now, despite the fact that android is supposed to use the optimal amount depending on how much RAM you have. 2GB is definitely a deal breaker for the supposed google flagship. If you don't multitask I suppose 2GB is fine, enough to run all apps smoothly. However the 4GB I have on my Zenfone 2 is just a multitasking dream while 3GB on the Galaxy S6 is enough for a few apps to run concurrently without any closing to free up RAM for others. Take a look at this multitasking shootout between the S6, Note Edge, and Zenfone 2. www.youtube.com That is easily one of the least useful tests of a phone I have ever seen. Normal apps (that is, things that aren't written in C++ and don't request a large memory heap) get locked to a maximum amount of memory. If they exceed that amount of memory, they will crash. This amount is set by the OS (and therefore changeable by the device manufacturer to suit their device's needs). The default value in Lollipop was something like ~116MB. If we take a 2GB device, even if we knock off 512MB of ram for the OS (which is definitely high at this point), that leaves 1536 / 116 = ~13 fully allocated processes. Do you use 13 apps at once that all allocate the maximum possible memory? I reeeeeally doubt it. Is more RAM nice? Sure, of course. Should having only 2GB of RAM be a dealbreaker? Probably not. i agree that it's a dumb test and all that video shows is that having more ram = more ability to multitask like 10 different videogames being played at once.
but i'm pretty sure the rest of your information is misleading simply because everything i've read & experienced suggests that android min/maxes its ram usage, and a simple look into your running/cached apps will disprove the ram allocation figure you threw out. i have 5 tabs open in my chrome and it's taking up 210mb, and one of my messaging apps is taking up 175 cached.
|
I dont see any reason to get the 5X considering theres the X Pure Edition (if you are looking for a Stock Android experience), higher resolution, bigger screen (in a not much bigger phone), more ram, pure android, same price, SD card, etc... i mean the X Pure has a half inch extra of screen but the size of the phone its less than .3 inches bigger (5.79 vs 6.06); the only 2 things you are missing are Wireless charging and fingerprint, i dont really care about the later and the former its soooo slow, i dont see why would anyone use wireless charging when theres turbo charger...
The 6P doesnt have a comparable phone in its price point and specs tho, not one that i remember.
|
fingerprint sensor is actually pretty useful since i used to not have a lock screen 12 hours into my ios expierence and the sensor is incredibly fast and mostly accurate
Carriers won't be carrying the X pure edition so there's that
|
|
|
in freedom land yes Nexus phones afaik have always been available through carriers in Canadia
|
First 24 hours with the x pure. It's a little heavier than I thought it would be, but not too heavy to be an issue. I paid the extra 25 for the wood backing. Definitely worth it, it feels great. The front facing stereo speakers work pretty well. Not amazing and can get muddy and distorted if you crank it too much. Can't comment on battery life just yet. Will update in about a week.
|
Today im ordering the X Pure :D
|
So it's been almost 2 weeks since I got my Note 5. Hard to say if I'm really happy with it or not since I dont have time to abuse or tinker around with it, but so far so good, everything is smooth, even lagwiz.
One problem though, is that the battery acts very weird. I leave my phone on battery saving mode overnight (9hrs) and it lost more than 30% (90->60%) sometimes. Then I just continue using it for the day without charging, mostly facebook and browsing TL, reddit, and battery only drops 30% (60-30%) with battery saving mode OFF, wifi/data on, etc. I dont even know T_T
|
Lalalaland34496 Posts
It sounds like something is draining your battery overnight. Check your battery usage in the mornings when you wake up.
|
All this capitalism and globalization and for what ?
for my fucking credit card not being acepted by Motorola because im from Chile ;_; !!!!!
This is racist...
Oh well, will have to accept the Amazon boring one ;_;
|
On October 01 2015 23:50 Firebolt145 wrote: It sounds like something is draining your battery overnight. Check your battery usage in the mornings when you wake up.
Ok will check again next morning. Normally I only check for abnormal usage, which has none. Other than that, the culprit is likely either power saving mode or alarm clock T_T
|
I finally flashed my Xiaomi Redmi Note 2 into a Miui 7 cooked rom without all the shit the chinese reseller put in and must say Im delighted how fluid it works.
Would recommend.
|
Lalalaland34496 Posts
On October 02 2015 02:42 bluegarfield wrote:Show nested quote +On October 01 2015 23:50 Firebolt145 wrote: It sounds like something is draining your battery overnight. Check your battery usage in the mornings when you wake up. Ok will check again next morning. Normally I only check for abnormal usage, which has none. Other than that, the culprit is likely either power saving mode or alarm clock T_T Something is definitely draining your battery if it's draining 30% overnight. Maybe it's something running too many wake locks, who knows.
Anyway the 6P looks incredible. I only hope Samsung implements Marshmallow on their phones quickly so I don't regret buying them.
|
|
|
|
|
|