yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] MrBrady:
I've been playing around with a few Nougat ROMs the past few days: Pure Nexus, NitrogenOS and Uberstock. By far, my favorite is NitrogenOS. It's a little buggy and doesn't pass SafetyNet (no Android Pay, etc), so unfortunately I couldn't stick with it at the moment. The UI was unbelievably smooth. I don't know what makes NitrogenOS so different from other ROMs, but it's like glass compared to a somewhat stuttering UI on other AOSP ROMs.

Uberstock was nice, but I'm back on Pure Nexus now. Hopefully it will be updated soon. I see a ton of new commits over the past few days.

What makes all these ROMs significantly better is the use of The Flash's new kernel. It's running great so far and sleeps like a baby overnight. Quite an amazing kernel for a first release, but I have no doubt he knows what he's doing: http://xdaforums.com/nexus-6/development/kernel-flash-kernel-v1-0-october-11th-t3478123
[Nexus 6  General] NLBeev:
Since I've used now Nougat several days I got different thoughts.

First I noticed that Nougat consumed more battery power and the layout of the keyboard has changed. So typing errors.

I prefer a dark mode and therefore I use blacked out apps of TBO or dark layers.

After activating Google Assistant the search bar became white again (was made transparent).

That's why I installed the Nova Launcher.

No more pesky search bar and better

Icons and lots of options for desktop and drawer.

The Nova Launcher works very well with Nougat and the launcher changed for 60-70% my thoughts.

I keep using Nougat with Nova and apps with a dark/black background.
[Nexus 6  General] dahawthorne:
I have N with Nova as well, and I agree Nova's excellent. I haven't had any difference in battery life. I don't think I'm a heavy user - the usual fiddling, checking emails/updates/news regularly, ebook reading, BubbleUpnp casting to TV - but it's rare that I fall below 40% by the end of the day. So many people report different battery life that it's probably a device-specific configuration thing rather than the generic device.
[Nexus 6  General] NLBeev:
Agree. I could be too early to say something about battery life. Trying new launcher and features consumed more battery power.
[Nexus 6  General] alexcolka:
Did exactly as you did, same results, I was missing the fluidity of marshmallow. I think I'm going to stay with 6.0.1 until 7.1 is officially released for Nexus 6 and showing in my system update notification, no forced flashes, no beta programs, nada.
[Nexus 6  General] droidstyle:
I will say after a week or so now on N battery life for me is better then M. My only issue is I get connectivity issues with Pandora.
[Nexus 6  General] 9wire:
From what I've been reading all the N ROMs have issues from not booting to BT issues to apn's and others. I'm pretty happy on pure m, don't see anything on nougat worth the trouble.
[Nexus 6  General] zelendel:
The only roms that have that issue are cm based roms. But then they have had BT issues for years. I am running DU based on aosp 7.0 and no issues at all so far.
[Nexus 6  General] istperson:
I don't know what people are talking about. I've installed Nougat on my N6, and recently on my 6P, and neither had any connectivity issues. Some people had these after the OTA, but upgrading to a new version is always risky that some bad settings get stuck that will disrupt the the new system apps' normal work. But it works for the 85% who leave everything on defaults, and only use their phones with zero customization.

So if you upgrade a whole version, save your data, and do a factory reset.
[Nexus 6  General] khanam:
I can second the flash kernel observation. Astonishing battery life on pure nougat and flash kernel
[Nexus 6  General] Tillmorn:
My biggest complaint is the new notification cards. They work well on the lock screen and seem to offer more functionality from their Marshmallow counterparts. However, I personally think they are a little too big in comparison. Add to that the fact that they lag ever so slightly when swiping them away when on the homescreen (this is on Pure Nexus, no idea if it's the same for all Nougat builds). Between those two things I actually find myself a little annoyed with them and wishing for the Marshmallow notifications.

Only other things are notification lights and status bar customization, but I know that will come in later builds so I can be patient about that. Otherwise, I like Nougat. My phone feels significantly snappier in comparison to Marshmallow. In a lot of ways, it feels like a brand new phone to me. And that's coming from a guy who started late with the Nexus 6 (around February of this year). Coming from a G3, even with a ROM, to stock Marshmallow and then Pure Nexus was just a night and day difference in performance. I've managed to find that feeling again with Nougat, thus staving off my desire to "upgrade" devices for another year. So overall I am very happy with it.
[Nexus 6  General] mchlbenner:
Hi

Personally I have tried 7.0 and 6.0.1 and come a conclusion that I still prefer 5.1.1 carbon so I keep coming back it so I have decided to not mess with those other roms.
[Nexus 6  General] NLBeev:
After upgrading to Nougat I saw some changes:

- keyboard layout,

- some layers didn't work,

- resizing the display,

- saturation of the colors can be changed.

But the user interface is about the same. Icons are still rather big, a white background and a pesky search bar.

For me the real change happened after installing the Nova Launcher and dark layers.

Nova is the the real change for me. Night mode, no search bar, smaller icons, editable icon names.
[Nexus 6  General] mchlbenner:


The pac-rom I use cm theme engine no layers I never liked layers as you said layers did not always work.

I meant pac-rom not carbon.

Only advantages of 7.0 to me is faster installing apps and faster booting up time.
[Nexus 6  General] istperson:
Yeah, they fixed it in the Pixel launcher. Only the main screen has the search bar.
[Nexus 6  General] Larzzzz82:
I was always having Bluetooth issues on MM. On 7.0 now for a few days, not 1 issue with Bluetooth and battery live for me seems better
[Nexus 6  General] holeindalip:
Layers got deprecated so its. No longer supported that's why it doesn't work
[Nexus 6  General] NLBeev:
Yes, especially the layers for system apps.
[Nexus 6  General] doitright:
If you're having a problem with the first two, then its an issue with those applications doing something stupid... and I can tell you exactly what it is:

Android N alters the selinux policy so that a REGULAR untrusted application can no longer read the device's root directory (and several other directories that previously would be readable). There really is no reason why they should be able to read those directories anyway. So what is going on is that those first two complaints are about programs that are SO poorly written, that they try to read the root directory BEFORE jumping into root, which is pretty silly since they both REQUIRE root.

As far as xposed goes... you have source code that is trivial to build on a Nexus, why would you want it?
[Nexus 6  General] najoor:
No. Stupid is a subjective term. The apps are fine.

I disagree with you.

As far as R/W goes: When a process gains root privileges it should have access to (almost) everything, and modify partitions after mounting them for write. The exceptions are (should be) a few select partitions such as the bootloader and the kernel. Otherwise there is no point in gaining root. It has been like that since the beginning of unix/linux, as long as I remember.

As far as Read-only goes: There is a point to be made about why a partition like /data should not even be readable (for security of the personal data) and google plugged that hole in Jelly Bean. But there is absolutely no reason why /system, which is a standard image of the OS, should not be readable. This is just paranoid security. Google should not have changed this.

I am sorry but that is not true. Adaway alters /system/etc/host file. To do that, it needs R/W access to /system. In all previous versions of android Adaway could alter the host file, which means it obtained root before attempting to alter, until now. So your assertion that adaway is "SO poorly written, that [it tries] to read the root directory BEFORE jumping into root" is just not correct.

The reason Adaway and many other root programs do not work anymore is that Google is shifting away from toolbox towards toybox. Toolbox used to be the facility for /system mount support and now all of a sudden it isn't, so perfectly well written apps will stop working because google decided to change the way things are done. There is some good education here: https://plus.google.com/+Chainfire/posts/dGPQytapwe3

I like facts. Words like "stupid" and "silly" (if one has to use them) should be backed up by facts not guesswork, especially when we talk about apps that are brilliantly written and have helped millions of people.
[Nexus 6  General] ttabbal:
Not everything xposed modifies is system level. You can use xposed to change various apps as well. It can be very useful for some people.
[Nexus 6  General] istperson:
Even on MM you can't normally mount system as rw, not even as root.
[Nexus 6  General] najoor:
Yes, you can:

su
mount -o rw,remount /system
[Nexus 6  General] istperson:
No, on stock, you can't. It does not remount it rw just having root.

It was a new sepolicy change, and a lot of people failed when they've tried to change their build.props. Search for "marshmallow and build.prop". For a while the only way was to pull it in TWRP, modify it, and push it back.
[Nexus 6  General] najoor:
Ok, because I always give myself room for error I went back and checked, and I was right: The command works and you can get RW access.

The reason people could not edit the build.prop was because in /system there is only about zero to 15 MB free. So there is no room to make changes to the build.prop. This has nothing to do with whether the mount command works or not; the partition is just full. Please see Chainfire's post at: http://xdaforums.com/showpost.php?p=64208563&postcount=3393

After mounting /system for RW if you remove a few apps to get about 30 MB of free space you can then modify build.props. Believe me, I have done that.
[Nexus 6  General] istperson:
I believe you. Initially I used TWRP to pull and push, then I already had my own AOSP build, and never tried stock again. So I believed those who said it was the selinux.

On the the other hand on Nougat I managed to flash the Pixel launcher and wallpaper app as system apps, and there's still some free space both on the N6 and the 6P.
[Nexus 6  General] nutpn:
Thats the way I felt about 5.1 Lollipop. LOL I'm still running the last beanstown 5.1 . But I guess I better step up to the plate.
[Nexus 6  General] pjsnyc:
I've been running stock since I got my replacement phone about a year ago. After waiting it out a bit, I decided to take the plunge about a week ago and update OTA to Nougat. Aside from some random SMS issues a few days after the update (that I believe is Sprint's fault), I havent experienced any issues with connectivity at all. Calls work fine. Data works fine. Wifi connects fine to both work and home. Bluetooth works fine. Battery life and snappiness seems about the same.

Just a personal preference, but if you like the way Nougat handles notifications, then its worth the update. If you dont like it, then its not worth the update from what I can tell. Also - if it breaks any of your apps (which thankfully it didnt for me), then yeah hold off on Nougat.

Just my 2 cents.
[Nexus 6  General] doitright:
When the application is doing something that is not defined by the API, then it is breaking rules and BEING STUPID. This is not subjective, this is factual.

Believe whatever you want to believe, but you cannot agree or disagree with fact. Fact is fact.

Two things to say to you about this;

1) Once it jumps to root, it DOES have access. I was talking about BEFORE switching user. One of the STUPID things that they do, is try to read the root directory BEFORE switching to root.

2) User privileges are entirely SEPARATE from selinux. Selinux can (and should) block ROOT access to certain things. If the root user happens to be operating within a restrictive context, then it is totally appropriate for it to be restricted within that context. If the root user is operating within an UNRESTRICTED context, then the root user has absolute control over everything. When I built my policy for https://github.com/seSuperuser/AOSP-SU-PATCH , my objective was to make the root user *nearly* unrestricted. One limitation I placed on the root user's context was that it would NOT have the ability to alter the selinux policy, the objective here is to be able to protect certain partitions (boot, recovery, etc.) from being silently modified by rogue applications that you happen to give root access to.

I said the ROOT directory, not system.

And there are tons of reasons to avoid making certain things readable, such as preventing bad things from scanning for (and exploiting) security vulnerabilities.

You aren't listening.

If it DID switch to root and a correct context, then it CAN write to that file.

This is a fact.

It is crashing because it is making assumptions that violate the API.

Neither toolbox NOR toybox were EVER intended for user applications to make use of! They are utilities that the SYSTEM uses. Stupid assumption for the application to use it. The application has no way to know if it is available, or if it behaves in the expected manner. For the application to be written correctly, it MUST NOT MAKE ASSUMPTIONS THAT VIOLATE THE API! In other words, either include its own utilities, or add a dependency on something else that provides them.

You apparently lack the capacity to understand facts.
[Nexus 6  General] najoor:
Calm down mister. Sure. You have all the facts and I am incapable of understanding them. Now that it's out of the way you can stop insulting me and get back to a technical conversation. I am sure there are people here with higher intellectual capacities than myself who will understand your facts.
[Nexus 6  General] lloydsw:
I like the quicker boot & longer battery life. What I don't like: while the hotspot always turns on, it doesn't always give an IP address, forcing me to power off/on to get it working.
[Nexus 6  General] doitright:
Quit being a wannabe condescending douchebag. Don't ARGUE with what you DON'T UNDERSTAND. When you don't understand something *ASK FOR CLARIFICATION* instead.
[Nexus 6  General] dahawthorne:
Doitright, you'll make enough enemies throughout your life just in day to day living. You really don't have to go out of your way to make more.

You're a great contributor to the site with your alternative root method, which I use myself, but seriously, tone down the unnecessary aggression...
[Nexus 6  General] najoor:
It never seizes to amaze me how xda can bring out a side of a person that you may never get to see in real life.

I guess it is the safety of not being forced to look into someone's eyes and insult them in their face that makes us feel we can say whatever we want online.

(Of course I am talking about myself being a condescending douchebag.)
[Nexus 6  General] Meowdib:
I'm staying on Marshmallow until 7.1.
[Nexus 6  General] d4ndr0id:
Nougat has my vote. More refined and a solid performer. Just waiting for xposed now.
[Nexus 6  General] NOSTALGIA:
No trash talking.. Not preferred here [MENTION=703985]xda..[/MENTION]..
[Nexus 6  General] shadowcore:
I'll be holding out of nougat until xposed is released or google stops updating nexus 6.

I was impressed by nougat changes and personally found nogat preview to be better then MM stock..

If google really keeps supporting nexus 6, google will gain my respect and my next phone might be a pixel device.
[Nexus 6  General] bads3ctor:
The hotspot hack only works up to 6.0.1 so I'm staying with it. I have the free 6GB Ringplus plan and can't live without the hotspot feature. From my understanding, the hotspot hack does not work on 7.0 on the Sprint network.
[Nexus 6  General] :
I may return to MM, having problems with GPS on Nougat. Haven't had time to look into possible solutions, but I have never had issues before.

Otherwise Nougat is ok, but certainly I dont find anything special about it personally. :)
[Nexus 6  General] OKAstro:
I've tried several custom Nougat ROMs and none of them have all the features I have on Pure Nexus Marshmallow (yet). I expect future releases will have them, and will probably settle on Pure Nexus Nougat when they're added.. Features missing include: Text Only Battery, Long Press Back to Kill, Add 4th button to Navigation Bar (Settings/Menu), and a few others I've gotten spoiled by.
[Nexus 6  General] ooofest:
I was on the Nougat beta 5 preview and it seemed stable enough at the time, good speed, etc. The notification changes weren't really my bag, but I was adjusting. Programs I use where notifications matter (e.g., my POP3 email) already had custom notification capabilities running on Marshmallow - the Nougat changes didn't really add much for me.

I've since gone back to Marshmallow and am not feeling that something is missing. Still running unrooted and entirely stock.

Given that Google (or Verizon?) hasn't seen fit to send the OTA my way yet, and given that custom N ROMs that I read about sound to be in growth phases at this time, I'm not seeing the need to install TWRP and slap on a custom or stock N ROM . . . will wait for the OTA.

- ooofest
[Remix OS for PC] Dunard:
Using Remix_OS_for_PC_Android_M_64bit_B2016092201. Those just auto close. Nothing loaded.

No issue running on the Remix_OS_for_PC_64bit_B2016071101.

Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
[Remix OS for PC] Dunard:
Mage and Minions have a see through graphics. Also some of the sounds is missing.
[ZenFone 2 Q&A, Help & Troubleshooting] reikred:
I have a Zenfone 2 ze551ml that is getting sluggish. Many of my apps are on the external sdcard, which is a 128GB U1/class10 microSD card. I'm using link2sd for these apps.

My question is what experience people may have with using an U3 microSD card? Does U3 improve the overall speed of the phone much when many apps are linked to the external card? I do not have an U3 card to test with, so whatever data or impressions you may have is useful. Of course, the more scientific the results, the better.

I have been using busybox.top to see (via ssh login) what the phone is doing under load.

Mem: 1934648K used, 71860K free, 0K shrd, 28480K buff, 497300K cached

CPU: 40.8% usr 33.0% sys 4.5% nic 6.2% idle 10.9% io 2.0% irq 2.2% sirq

The io number is often small, but I probably does not include IO *wait* time, so I do not know how significant the number is. The "top" numbers are all over the place, from second to second, so I do not think they tell me much, but I have a strange hunch that the sdcard is one of the bottlenecks. Using 497MB of RAM as disk cache might occur whether or not the sdcard is fast. Another example of some "top" numbers, after a reboot.

Mem: 1935396K used, 71112K free, 0K shrd, 14932K buff, 392356K cached

CPU: 32.0% usr 22.9% sys 3.1% nic 15.1% idle 24.5% io 1.2% irq 0.9% sirq

Load average: 13.97 5.47 2.02 4/1903 5604

PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND

1933 319 app_207 R 1578m 80.4 1 20.8 {facebook.katana} com.facebook.katana

678 319 system S < 1474m 75.1 2 13.9 system_server
[ZenFone 2 Q&A, Help & Troubleshooting] chiudikas:
As a rule, the bigger the card, the slower it is, compared to the same series cards but smaller size.

I use 32GB card Kingston microSDHC 32GB UHS-I U3 (r/w;90/80MB/s), when i just installed it around 6 months ago it showed around 100MB/s speeds.

p.s. it gets worse over time.
[ZenFone 2 Q&A, Help & Troubleshooting] reikred:
Bump, anyone with specific experience in a general feeling or measurement of phone speeding up when switching from U1 to U3 speed class sdcard? I know a U3 card will have better IO benchmarks, but the real the question is how much does it affect performance of the phone overall.
[ZenFone 2 Q&A, Help & Troubleshooting] reikred:
I can report back that I bought a Netac 128GB micro-SD UHS-I class U3 card, and I have been using it in my phone for a while.

I would say that operations that involve the external U3 card are definitely faster, although I have not run a benchmark yet (having other problems at the moment, may get back to this later). Anyway, I think the U3 card was worth paying a bit extra ($49 U3 versus $40 or so for a U1, I think).
[Nexus 6 Q&A, Help & Troubleshooting] slender troll01:
Since the first Nougat dev build, I've been running stock unlocked Android. However, I haven't been able to keep my recovery installed, and I've had to reflash it via my computer every time I wanted to be able to flash things via TWRP. In addition, nothing I flash (except when I root the device, for some reason) survives the reboot into system, even if it was a successful flash. Any help is appreciated.

Nexus 6

Stock Android 7.0 Nougat

Unlocked, but not rooted
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
The system will rewrite the recovery partition every time you boot it up. You need to make an edit to system partition to prevent that from happening. Specifically, the script at /system/bin/install-recovery.sh.

Now of course you are *also* having problems getting changes to the system partition to stick. This is due to dm-verity running on that partition. In order to cancel that, you need to modify the initrd image (part of the boot image). Specifically, remove the verity parameter from the fstab for system partition.
[Nexus 6 Q&A, Help & Troubleshooting] biglil1:
I've never made an edit to the recovery.sh file but I've always ran a noforce nonverify boot img and TWRP always stuck for me. I read that when you allow TWRP to modify system that it automatically edits this file which I do. Is this way it's sticking? I never had any problems and it seems a lot of "TWRP not sticking" threads are popping up.
[Nexus 6 Q&A, Help & Troubleshooting] slender troll01:
Could you explain how to do all of that? I have no idea what to edit or where those things are.
[Note 7 Questions & Answers] spleenandcigars:
Does anyone knows what conditions the cellphones were at the moment of the combustion? I've read that it had something related to the low battery, but what else? Intense CPU/GPU consume, uptime, heavy use or deep state?
[Note 7 Questions & Answers] Kansatsusha:
heat ? pressure? no room to expand under heated pressure??
[Note 7 Questions & Answers] spleenandcigars:
Ain't that easily fixed after some max clock limiter?
[T-Mobile Note 7  Guides, News, & Discussion] tnick84:
Very simple work-around to be able to use Gear VR on your Note 7. YOU MUST BE ROOTED IN ORDER FOR THIS TO WORK.

1. Open system/ build.prop with a root browser

2. Edit. ro.product.model=SM-N930T ------> SM-G935T

3. REBOOT! Profit.

I would highly suggest changing to SM-G935T ONLY when you are about to use Gear VR. Then change it back to SM-N930T and reboot when you are finished. It may cause issues with Note 7 related files of you do not

******DISCLAIMER******

I AM NOT RESPONSIBLE IF THE NOTE 7 BLOWS UP RENDERING YOU BLIND OR ANY OTHER BODILY HARM

PLEASE CALL 1-800-SAMSUNG IF DISABLING INJURY OCCURS

*************************

ENJOY!
[T-Mobile Note 7  Guides, News, & Discussion] Briankbl:
I want to stay stock for Samsung Pay, so I guess my Gear VR is officially a paper weight...
[T-Mobile Note 7  Guides, News, & Discussion] seh6183:
There was an update to the VR apk that blocked the note7 off the list of compatible devices. We need to find someone with the older apk so we can sideload it.
[T-Mobile Note 7  Guides, News, & Discussion] Kilroy672:
I thought I had the older version of Oculus but I don't...:mad: I looked under my settings and I have. 2.15.4...I also had my auto updates enabled...again...:::mad: