yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] robbieas:
Wanted to confirm that this too has appeared to resolve my proximity/black-screen-on-calls issue. It works like it is supposed to now. I'm on the 11/16 build.

This appears to be a nice find, thanks for sharing!
[Nexus 6 Android Development] D0CTOR:
Thanks for the suggestion [MENTION=3200478]Woody[/MENTION], as that was my first thing I tried, however there's nothing in that directory!

I uninstalled the theme from the phone, and rebooted. Reinstalled it, and the same thing. Can't seem to find the files anywhere using Root Explorer. I'm not a noob on this stuff, but it's got me baffled...

I installed the "Layers Manager (Depreciated), and it doesn't know that I even have the theme (Dark Material - Blacked Out) installed. Same for the Substratum app.

Got any more ideas???

TIA,

Doc
[Nexus 6 Android Development] rignfool:
Isn't Dark Material-Blacked Out a CMTE theme?

Also...

Go to /data/resource-cache/ and remove all the files there as well...

Also...

Update... You're missing out on all the good stuff ;)
[Nexus 6 Android Development] clothednblack:
New version of TWRP is out

https://dl.twrp.me/shamu/

Just installed it using flashify and works.

That is all......
[Nexus 6 Android Development] djcsurf:
I'm UK user running latest build. I installed MyEE app but it won't open, doesn't FC it just says SORRY CANT OPEN or something similar. I asked on EE community and another member posted it works fine for them on stock nougat. Can anyone confirm what happens for them using PN, thanks [MENTION=4395895]BeansTown106[/MENTION]
[Nexus 6 Android Development] The Doctor04:
Flashed with TWRP itself and it worked fine as well

Thanks for the heads up!
[Nexus 6 Android Development] khw1959:
Did the same this morning with no issues.
[Nexus 6 Android Development] Fouad Aslam:
Hi, I was in the UK a few weeks ago and used a PAYG EE simm and also installed the EE app on PN 7.0. Worked fine. Might take a little time and a reboot or so, but it did work so hopefully it will for you too.
[Nexus 6 Android Development] SyNoriixX:
Will the next update be 7.0 or 7.1.1?
[Nexus 6 Android Development] nathanchance:
7.1.1
[Nexus 6 Android Development] SyNoriixX:
Now i'm excited. :D
[Nexus 6 Android Development] imarq24:
Really noon question but I forgot how to freakish

Flash TWRP IMG...
[Nexus 6 Android Development] michierusama:
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
[Nexus 6 Android Development] Pkt_Lnt:
https://www.xda-developers.com/how-to-install-twrp/
[Nexus 6 Android Development] Markeee:
The Dec. update just came out below link and for "shamu" Nexus 6 it's still 7.0.0 (NBD91U)

https://developers.google.com/android/images
[Nexus 6 Android Development] Pkt_Lnt:
Bet Beans does not build from images, but from source.
[Nexus 6 Android Development] clothednblack:
I used "Flashify" from the app store, it will download and flash it for you but twrp manager works too
[Nexus 6 Android Development] Markeee:
What does that mean ?

Does that mean Beans next release will be from 7.1.1 ?
[Nexus 6 Android Development] Pkt_Lnt:
You posted a link to Google images. Beans does use those. He uses source code to build. They are much different, and too big a subject for here. Google can answer that if you are burning to know, be ready for a long read. :good: Nexus 6 images are out, Nexus 6 source for 7.1.1 may not be released, but Beans can use something like 6P source to build for Nexus 6.

The Flash already posted the answer that the next PN version will be 7.1.1, that is what you quoted above.
[Nexus 6 Android Development] Markeee:
Ok sounds good hope your right next up 7.1.1 I'm excited :)
[Nexus 6 Android Development] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=69978716&postcount=31624
[Nexus 6 Android Development] Markeee:
Yeah saw that post already friend thank you
[Nexus 6 Android Development] imarq24:
What does this mean and how do I correct it
[Nexus 6 Android Development] Grubling:
Something to do with a Dolby sound mod, I'd suppose. Do you have V4A or Arise mods installed? If so, I'd remove them and see if it persists.
[Nexus 6 Android Development] dynamo147:
Question everyone, I'm running our latest PN and latest full gapps with elemental x kernel and I get reboots now and again, but after these reboots some of my apps seem to think I'm a first time user. Google maps will let me know navigation is in beta and that a new traffic feature is added, Google keyboard will revert my preferences and start vibrating per press and change my image. Chrome will ask me to sign in and sync up with my pass phrase - just weird things, any idea what's happening?
[Nexus 6 Android Development] Gveric:
I would suggest doing a full wipe and reinstall. No clue what's going on there. Make sure you're using the most recent Gapps.
[Nexus 6 Android Development] NoLips:
Do a dirty flash with only the rom [link Post#4] and SuperSU.... no gapps and kernel.

See if the problem still persists > no? then your problem lies in the elemental x kernel or it's settings. Still have random reboots? then probably the Gapps you are using are the problem.

If you are doing a full wipe then you have a big change that the combination of Gapps, kernel and settings brings you back to square one..... the option above rules out kernel and rom in combination with the Gapps.

Hope this helps you to rule out what causes this.
[Nexus 6 Android Development] bobdallama:
Does anyone else have an issue with phh superuser losing root periodically? I have to reflash the zips (magisk and phh) in TWRP, but even then sometimes I will not have root when I reboot.

Apart from that I'm loving this build and look forward to 7.1
[Nexus 6 Android Development] DSDONE:
As am I looking forward to 7.1

Tapatalkin'
[Nexus 6 Android Development] Strephon Alkhalikoi:
You're not the only one. In the nearly six years I have used Android devices I have never had Google apps so troublesome as to render the entire device virtually unusable, so the forthcoming 7.1.1 update had better fix everything wrong with 7.0, because as far as I'm concerned, 7.0 is entirely too buggy to use.

Just to make things clear, this is not the fault of the Pure Nexus team. When the team first released the Android 7.0 version of Pure Nexus, I accused the ROM of being the problem, when in truth the Pure Nexus ROM without Google apps works perfectly. There is absolutely no reason however that I shouldn't be able to apply a theme (Spectrum/Domination), use my favorite launcher (Nova), or use my favorite file manager (my modded ES File Explorer) on this ROM, except for the fact that Google can't code to save their lives. Apparently, I cannot sideload or even update any apps or Google voice commands (OK Google) break so badly that only a factory reset will fix it.

It's so bad that not even a nandroid backup works. Like I said earlier, it's not Pure Nexus' fault, but thanks to Google's ham-fisted coding I'm being driven away from AOSP. Unless of course I go back to the Android 6.0.1, where everything worked without having to jump through hoops. So stick a fork in me. I'm done.
[Nexus 6 Android Development] Nucleotide:
You sir must be doing a lot more to your device then just trying to apply a theme. Mine is rock solid - not a single issue in sight so it's neither the ROM or Google Apps (the recommend ones) otherwise I too would be having issues - along with most people in this thread. Oh, and I use Nova without an issue also. The File Manager shouldn't have any bearing on anything.

So whatever you're doing, I sense you aren't providing the full story.

As for Google not being able to code to save their lives - I don't think I've seen a more ridiculous comment on the internet... ever! I guess Android is a pretty ****ty feat of coding. Maybe you belong on iOS? Perhaps it's much better suited to you. :laugh: :laugh:
[Nexus 6 Android Development] Strephon Alkhalikoi:
Considering that I was using this build up until yesterday without issue, your senses are misleading you. But you believe whatever the hell you want. I don't place much stock in your opinion, especially if the best you can come up with is "switch to iOS".

I'm not the only one who feels Google has coding problems. The author of Domination no longer supports stock ROMs because Google's coding is that badly screwed up. My issues today only enhance that belief.
[Nexus 6 Android Development] Nucleotide:
You can also beleive whatever you want. Quite simply though, if you're so upset with Android and Google's 'apparent' lack of coding ability, switch to iOS. Pretty simple, really. It's pretty clear you have no idea what you're doing with Android and if you're having problems with such simple issues such as using a specific launcher or running another file manager.

Wow! You and one other person beleive Google can't code for ****. Whatever shall we do. I guess we are all screwed now. :laugh: :laugh: :rolleyes:
[Nexus 6 Android Development] christianpeso:
So you use a 3rd party launcher, a 3rd party file manager, and a theme manager that Google has completely nothing to do with that integrates within the whole entire OS, but yet you blame Google for poor coding? Come on bro.
[Nexus 6 Android Development] xshallowgrave:
Is there a way to enable a system wide dark mode? I can't find anything in the settings.
[Nexus 6 Android Development] Pkt_Lnt:
Substratum

https://play.google.com/store/apps/details?id=projekt.substratum&hl=en

http://xdaforums.com/android/themes/projekt-substratum-t3423623

https://www.xda-developers.com/layers-manager-is-being-deprecated-in-favor-of-substratum/
[Nexus 6 Android Development] Strephon Alkhalikoi:
[MENTION=615468]christianpeso[/MENTION]: You have a point regarding substratum. However, the launcher and file manager do not integrate with the system and yet installing them breaks the Google App? That is a problem that does not happen on stock. So I yet again have to resort to handicapping myself by using a stock ROM, because it works. I can freely use both launcher and file manager without the Google App breaking. I haven't tried theming yet, but I expect things to work there as well.

As to the poster before you who thinks I don't know what I'm doing, his opinions are irrelevant and the personal attacks unwarranted. My record on this site speaks for itself.
[Nexus 6 Android Development] DSDONE:
My device was working with no issues either... I just went to 7.1 to see what the big deal was... I'm sorry that you experienced so many issues...

Tapatalkin'
[Nexus 6 Android Development] Nucleotide:
Not a very good record if you can't even get a launcher to work. A launcher, mind you, that works flawlessly for pretty much everyone else - stock, custom or otherwise. In fact, I don't think I've ever seen anyone in here complain about not being able to use Nova, ever. The launcher simply does not break anything, and neither should your file manager. So again, whatever is happening is a result of something you've done - whether it be applying incompatible theme or perhaps you've modified something else that isn't playing nice.

Assuming you did a clean wipe and are using the most recent ROM and 'recommend' Gapps, there shouldn't be any issues - period.

:rolleyes: :rolleyes:
[Nexus 6 Android Development] bitemeoftn:
So I refresh the page and get excited to see a few new pages have come up; hoping it was something new or a fix for a problem. No! It's almost three pages of people bickering back and forth about useless stuff. Message each other to argue please and thank you in advance.
[Nexus 6 Android Development] Strephon Alkhalikoi:
I thought the problem might be with my device, so to test I flashed a stock ROM. Not only are Nova and ES working flawlessly, so are Google voice commands. Since according to you I have absolutely no clue as to what I'm doing, how do you explain the fact that everything is working as expected on the stock ROM and not Pure Nexus?

I can't explain it and am not even going to try. All I know is that on a clean install with both ROMs, voice commands work on Pure Nexus only as long as you don't install certain apps, update others, or reboot; while on a stock ROM voice commands work flawlessly with any app I want (including themes) installed.
[Nexus 6 Android Development] kwdan:
So, Based on this statement... The "Rom" must be running exceptionally well for the majority of the users?
[Nexus 6 Android Development] Strephon Alkhalikoi:
I honestly will say the ROM is great. The issues I encountered with voice commands not working are not unique to Pure Nexus in that they happen on other AOSP ROMs, e.g. Nitrogen, as well. Other Pure Nexus users have encountered the voice command issue on the Google+ community wall, but apparently I'm the only one with such drastic issues that I can't even use an AOSP ROM unless I either forego voice commands or forego Google apps entirely.
[Nexus 6 Android Development] S0UTHPAWK1LLA:
[MENTION=4702180]streph[/MENTION]on.. I agree that something isn't kosher with the always on feature. As you know, I had it working fine previously. After updating I had issues.. even after un-theming everything. Not that it'll work for you, but in my case this time I got it to work by turning off the swipe up multi window feature. It was the only setting I messed with and as soon as I turned it off, went back wiped data on the Google app.. always on was back to working. Maybe coincidence? IDK..but I'd tried everything beforehand to re-enable it to no avail.
[Nexus 6 Android Development] kwdan:
I am currently on a different rom. this Okay Google discussion is happening over there also. I have it working and it's been working for me through 3 dirty flashes of that Rom. I set it up on the initial setup of the ROM, never cleared google app data, only modified build prop. Try that on your next clean flash and see if it works for you on this Rom. I'm using open gapps stock 7.1.
[Nexus 6 Android Development] Strephon Alkhalikoi:
I never even turned the multi-window gesture on, and in fact did a clean reinstall after I saw the app had failed, to no avail. It's the things we are having to do to get this to work consistently that really triggers my OCD, and the responsibility for it lies at Google's feet, not the Pure Nexus team.

Like you, I had it working fine myself prior to my latest rant. The only thing I can think of is that the Google app updated and in doing so broke everything. And if the situation is that fragile, for reliability reasons I have to stick closer to stock for now, or fall to the dark side and use an even more buggy CyanogenMod.
[Nexus 6 Android Development] ktmom:
Does this happen when the battery is low? Say maybe under 30%? Try deleting the boatloader logs. This was touched on in this thread.
[Nexus 6 Android Development] Woody:
The horror. The horror.

I'm pretty busy tonight and going to a hockey game tomorrow night, but if you want to hop on a hangouts chats during the day, I'll help you work through some things. I'm totally up-to-date (as far as all apks, certain ThemeReady.apks, Substratum themes, Play Services, Google.apk, Nova) and all is working fine for me. I have always-on working through Nova (tried it this morning after reading all that bickering), no issues with Root Explorer or Solid Explorer getting or keeping root functionalities (I don't and won't use ES, sorry) and all my themes are working (Domination, Spectrum, SwiftDark, personals). If it turns out it is a theming issue, we'll get Davey and a few TBO guys on the chat too.

I know that your profile says Vulcan, but I know where you really are ;), so whatever time works for you will work for me too. If not, that is ok. I know that both you and [MENTION=4117576]Nucleotide[/MENTION] have been around the block a few times and we've all shared device forums in the past, so it has to be something small that is causing these issues. Not really something to flame over, so let's move on from that and work the problem and not each other.

If anyone else has some solution, please don't hesitate to help. After all, Rule 10 is Help Others If you Can.
[Nexus 6 Android Development] Strephon Alkhalikoi:
I don't think it was a theme issue. I specifically did NOT theme the Google app, and everything worked just fine up until yesterday. Currently I'm using Dan's stock lite ROM, and other than not being able to theme the system (known issue with substratum and the November update), everything works, including theming the Google app. On a side note, the copy of ES I use is the one in my signature, not the current product. Thus, no ads or malware.

I really think this is a bug in the Google app itself that only appears on AOSP. Someone who doesn't use voice commands won't notice anything amiss. Apps function properly, and updates happen. It's when you want to use voice commands that you run into trouble with app incompatibility issues with AOSP, the Google app, and everything else.
[Nexus 6 Android Development] brightjh01:
I am using the latest Pure Nexus (20161116) online N6 with Mini dynamic GApps all works great. Modified build.prop. to use Google Assistant
[Nexus 6 Android Development] kwdan:
I think there must be something else in your set up. I'm using a transparent magpie theme with the Google app themed. It's working for me. I'm using open gapps stock. I hope we can narrow down why it's not working for you This could help a lot of people.
[Nexus 6 Android Development] mpgolfpro:
Just wondering if anyone could provide me with a little assistance regarding Snapchat. I have been using it with little to no problems until this morning when I had to restart my phone and log back in to Snapchat. At this time it won't let me log in and I keep getting an error message. I have requested support from Snapchat and they say its because my device is rooted. Not sire why this is happening now all of a sudden when I have been rooted the entire time. I researched the issue and it looks to be a problem normally with root and exposed, however I don't have exposed installed. Anyone heard of this problem or have any ideas? I have uninstalled and reinstalled the app like 5 times. Thanks for the help!
[Nexus 6 Android Development] Strephon Alkhalikoi:
My setup is fairly bland. Not a lot of customization. Not even a custom kernel. Other than substratum, Domination and Spectrum, I use Nova and the glasklart theme. Root is SuperSU 2.78 SR5. AdAway installed systemless along woth busybox. Storage was encrypted from day 1 and I never changed it.
[Nexus 6 Android Development] kwdan:
I use Nova Prime or transparent pixel launcher(as system app) superSu SR5, whatever kernel that comes with rom, adaway, magpie, spectrum, and material glass( little bit of each one at the same time), whatever BusyBox that comes with rom( never installed separately). I know that if you theme Google drive with magpie it wouldn't open for me, so maybe it's a theme breaking it?
[Nexus 6 Android Development] Strephon Alkhalikoi:
Possible. I didn't theme the Google app as its colors were hard-coded and I don't generally use team blackout's apps. On the clean install without restoring apps, installing ES and rebooting broke the Google App. One thing I did notice with Pure Nexus is that unlike the stock ROM, there is no warning to go to a quiet place before it dumps you into the recording screen. On the stock ROMs it always tosses up that warning.
[Nexus 6 Android Development] forgottenhacker:
Hey if you are rooted the Snapchat doesn't work....you will need to unroot, sign in,then root. Snapchat can also see if you have exposed so root cloak doesn't work...after rebooting I would suggest to take a titanium backup as you can restore the backup of the already logged in Snapchat if you do ever get logged out again.
[Nexus 6 Android Development] kwdan:
You modified the Es app correct? Maybe that's what's breaking it for you. I've themed my google app, system and more with stock gapps( not team blackout).
[Nexus 6 Android Development] Strephon Alkhalikoi:
The modded ES has been exhaustively tested. If there were issues, the over 500 users of the modified app would have said something by now on the thread where I make the app available. That doesn't count the half dozen devices I personally installed the app on nor does it count the developer incorporating the app into his Note 4 ROM. Since the mod itself was to change hard-coded root paths in pre-malware versions of the app so systemless root worked, it's unlikely that the mod would break anything.
[Nexus 6 Android Development] bobdallama:
So I'm gonna ask again, just to be sure...

No issues with phh superuser losing root privileges periodically for anyone other than me? Using magisk v9, and when it fails I have to reflash both zips. Even then sometimes it takes multiple attempts before it sticks.
[Nexus 6 Android Development] Pkt_Lnt:
I use phh superuser for many months now, on last MM PN release and two N PN releases, never lost root. Do not use Magisk..
[Nexus 6 Android Development] bobdallama:
I use magiskhide so Android pay works...if there's a better way, I'm all ears
[Nexus 6 Android Development] Pkt_Lnt:
No idea. I don't screw with the Android Pay cat and mouse game. Waste of my time, when I can pull out my wallet and swipe a card. Not interested in spending hours flashing and reflashing to get it to **maybe** work once or twice before Google blocks it on their end.
[Nexus 6 Android Development] bobdallama:
Yeah, I'm definitely leaning that way.
[Nexus 6 Android Development] Nucleotide:
Be that as it may, have you actually removed your modified version of ES and tested? So clean install, recommended Gapps, etc. Don't install anything else at this point - especially ES, AdAway or busybox. I'm not actually sure why you are installing busybox anyway considering it comes with the ROM - unless you're doing something specific/out of the ordinary with it, in which case resulting in yet another possible cause for your issue.

Someone above suggested it could be your version of ES but it seems like you are making assumptions that because it's your app, there can't possibly be anything wrong with it.

There are plenty of people so far running very similar setups to yours (looking at the comments). The only difference being that they don't appear to be using your modified version of ES.

Go back to basics and work your way forward without making assumptions. Some apps are tested by tens of thousands of people and still break stuff so making the assumption that your measly 500~ users is enough to ensure everything is 100% perfect is not the way to do things.

Honestly, I want to help you solve this ****ty issue, and hope that it does get resolved - no one likes having issues with their device. But you've got to take a step back sometimes and look at things a little more objectively. :highfive:
[Nexus 6 Android Development] ktmom:
I have this problem also. Very similar set-up. I don't use ES, modified or not :). Otherwise, same song different verse.

Got google anywhere working with dynamic mini, themed and Nova (beta) and an update blew it out of the water. I've been fussing with this all afternoon. Removed themes, selected Now launcher and still couldn't get it to work. Then I went in FC and deleted all data from the Google app. Got the new "go to a quiet place" set-up for voice training. Switched back to Nova, still worked. Added themes, still worked. Rebooted a few times worked, but then stopped working. I had been playing with theming in between.

This time I just FC and cleared all data from the Google app. Still with all of my set-up the way I want with Nova as the launcher. Again I got the new "quiet place" warning and was able to enable the always on feature again.

Dunno how long it'll last, but maybe it'll help you.
[Nexus 6 Android Development] kwdan:
You have assistant working with screen off? And every screen?
[Nexus 6 Android Development] ktmom:
Not assistant. Ok Google anywhere. But yes, screen off, screen locked and in any app I've tried.