Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.

Wow, in just three goes the iris scanner went twice as fast

Shame you still have to first wake, then swipe up before it activates--could be so much faster. However I do concede it could be useful in a pinch for the occasional time when your hands aren't dry or are covered. Just wish the implementation was better is all.
 
  • Like
Reactions: THE JUICEMAN
Only one more week. Starting to get anxious, especially seeing the unboxing videos start to pop up on YouTube. The all black one just looks so slick.
Hopefully we will start getting shipping notices this weekend or Monday!
[doublepost=1471004521][/doublepost]
Comparison Note 5 vs Note 7

Man that all black Note 7 looks sick!
 
  • Like
Reactions: THE JUICEMAN
Sorry but the ram management is nothing to do with Google I'm afraid. Samsung seems to employ a lack of optimisation in regards to the snapdragon in the USA version.

The exynos version of the S7/S7e did not have issues memory management wise and we're able to keep far more apps open despite sharing the same amount of ram as the snapdragon version. You can easily get a dozen or more apps open on the exynos variant and flick between them without reloading.

You would therefore be led to believe that perhaps it's the Qualcomm snapdragon at fault but... HTC / LG and others are using the same snapdragon 820 and likewise as the exynos, do not have the issue opening and storing apps in the background. Indeed I managed to get 18 apps open and going between them on my HTC 10 without a single refresh.

Therefore the only explanation has to be laid at Samsung's feet for this one. Whether they originally designed and optimised the current Grace UI / TW OS for the exynos and then failed to put the same amount of optimisation into it when it comes to the snapdragon, only Samsung know. But it does stand as a curious discrepancy.

The blame however can certainly not be a laid at Google, or singled out to Qualcomm otherwise both the Samsung exynos variants and other snapdragon 820 handsets would suffer exactly the same issue, which they simply do not.

I've seen the issues on non Samsung devices..
 
I've seen the issues on non Samsung devices..

And ???

We're they running the Snapdragon 820 and 4gb ram ? Running Marshmallow 6 and upwards ?

The only other manufacturer with 'acknowledged' ram issues on the Snapdragon 820 was OnePlus 3. It certainly had ram management issues with the 820 & 6gb ram, because of what OnePlus themselves chose to do with the kernel - which actually gimped it's ram performance to save battery. They have gone someway to rectifying it now, but it's still not utilising the same common parameters that Google utilise and other manufacturers stick by.

So even in that instance Google are NOT to blame.

So please continue and explain just how Google are to blame as you assert in your earlier post ?
 
WIN_20160812_11_45_33_Pro.jpg


My cases and screen protectors for my note 7 if anyones interested :) Probably spent no more than £10 on the whole lot. In past experience the best screen protectors I've had were from Poundland :D
 
WIN_20160812_11_45_33_Pro.jpg


My cases and screen protectors for my note 7 if anyones interested :) Probably spent no more than £10 on the whole lot. In past experience the best screen protectors I've had were from Poundland :D

Nice! How's the neo hybrid back feel? Slippery? Or grippy?
 
  • Like
Reactions: MRU
Tried ordering sim free but carphone warehouse woman said they don't have any prices for a few weeks. Odd
 
Tried ordering sim free but carphone warehouse woman said they don't have any prices for a few weeks. Odd

Yeah they do that here a lot with new phones that the first few weeks tend to only be carrier locked models as essentially the carriers are given priority over sim free purchasers. You usually have to wait a few weeks for popular handsets for them to be available on PAYG here let alone Sim free.
 
Yeah they do that here a lot with new phones that the first few weeks tend to only be carrier locked models as essentially the carriers are given priority over sim free purchasers. You usually have to wait a few weeks for popular handsets for them to be available on PAYG here let alone Sim free.
I thought somebody here ordered one for £699 that's why I thought it was strange.

Would of gone with carphone warehouse for the free VR. Unlocked mobiles are selling it for £674 but no VR
 
I thought somebody here ordered one for £699 that's why I thought it was strange.

Would of gone with carphone warehouse for the free VR. Unlocked mobiles are selling it for £674 but no VR

Maybe the one they went with was PAYG rather than Sim Free ? (so still essentially locked to a carrier).
 
This seems promising:

http://m.koreatimes.co.kr/phone/news/view.jsp?req_newsidx=211688

So hopefully that means we get it by the end of the year.


In fairness we have heard that before and similar time scales. They never usually pan out or if they do end up being just one territory with one CSC model identifier version. I would expect Nougat possibly Feb or March realistically. That being said, with TW having majority of features Nougat is bringing to the table, it's not as important an upgrade compared to devices that run a much closer to Stock or completely stock OS.
 
  • Like
Reactions: Fernandez21
In fairness we have heard that before and similar time scales. They never usually pan out or if they do end up being just one territory with one CSC model identifier version. I would expect Nougat possibly Feb or March realistically. That being said, with TW having majority of features Nougat is bringing to the table, it's not as important an upgrade compared to devices that run a much closer to Stock or completely stock OS.

Maybe when the S8 launches, the Note 7 will get updated in other regions. That's my guess.
 
  • Like
Reactions: tbayrgs and MRU
In fairness we have heard that before and similar time scales. They never usually pan out or if they do end up being just one territory with one CSC model identifier version. I would expect Nougat possibly Feb or March realistically. That being said, with TW having majority of features Nougat is bringing to the table, it's not as important an upgrade compared to devices that run a much closer to Stock or completely stock OS.
^^^^^ this is big^^^^ Slimmer faster TW with a lot of Nougats features out of the box. But i still want to hold Samsung to getting Nougat out by years end or in January.
 
  • Like
Reactions: MRU
Tried ordering sim free but carphone warehouse woman said they don't have any prices for a few weeks. Odd

I've ordered a sim free one from them and VR for £699. The first time I rang they told me the same. The second time I rang I was able to buy one. I also went to a store y'day to try and order one and they told me the same (though they didn't even know they'd started taking orders). The store also said the VR was for contracts only.
 
I've ordered a sim free one from them and VR for £699. The first time I rang they told me the same. The second time I rang I was able to buy one. I also went to a store y'day to try and order one and they told me the same (though they didn't even know they'd started taking orders). The store also said the VR was for contracts only.
Interesting so VR won't be given to those who buy sim free?

Might buy from unlocked mobiles then in that case
 
^^^^^ this is big^^^^ Slimmer faster TW with a lot of Nougats features out of the box. But i still want to hold Samsung to getting Nougat out by years end or in January.
I'm curious how they're handling multi-window in Nougat. Ideally it'll be compatible with both Samsung version and Googles, but wondering if they pick one or the other? Or maybe only select API and only some apps become compatible?
 
  • Like
Reactions: jamezr
I'm curious how they're handling multi-window in Nougat. Ideally it'll be compatible with both Samsung version and Googles, but wondering if they pick one or the other? Or maybe only select API and only some apps become compatible?

Never thought of that. Would/could Samsung actually block some of the functionality of Android--in this case native multi-window? I guess they probably could considering they blocked use of adoptable storage. If they didn't block it, how would it work for apps that are coded for both? In theory, Google's implementation if far more widespread, not requiring as much for devs to implement, correct?
 
  • Like
Reactions: jamezr
And ???

We're they running the Snapdragon 820 and 4gb ram ? Running Marshmallow 6 and upwards ?

The only other manufacturer with 'acknowledged' ram issues on the Snapdragon 820 was OnePlus 3. It certainly had ram management issues with the 820 & 6gb ram, because of what OnePlus themselves chose to do with the kernel - which actually gimped it's ram performance to save battery. They have gone someway to rectifying it now, but it's still not utilising the same common parameters that Google utilise and other manufacturers stick by.
So even in that instance Google are NOT to blame.
So please continue and explain just how Google are to blame as you assert in your earlier post ?

When I say Google should try to fix this it's because it's up to the application developer to play nice with the OS, and you can and you will have differrent results trying to multitask with specific applications. In order to be valid, a test would need to open the same applications on every phones you want to test and have the same OS version. Even at that point, it still won't be accurate.

I currently have Samsung Gear processes that aren't active by default, so when I test mine and another without, the results will vary. If you have a lot of background services, it will affect overall memory and impact the test.

Switching Apps
Instead of using swap space when the user switches between apps, Android keeps processes that are not hosting a foreground ("user visible") app component in a least-recently used (LRU) cache. For example, when the user first launches an app, a process is created for it, but when the user leaves the app, that process does not quit. The system keeps the process cached, so if the user later returns to the app, the process is reused for faster app switching.

If your app has a cached process and it retains memory that it currently does not need, then your app—even while the user is not using it—is constraining the system's overall performance. So, as the system runs low on memory, it may kill processes in the LRU cache beginning with the process least recently used, but also giving some consideration toward which processes are most memory intensive. To keep your process cached as long as possible, follow the advice in the following sections about when to release your references.

More information about how processes are cached while not running in the foreground and how Android decides which ones can be killed is available in the Processes and Threads guide

iOS handle processes differently, so my Google suggestion was more related to finding alternatives that doesn't involve the developer.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.