yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Takuapina:
I've just installed this ROM and it's amazing how smooth it goes. However I'd like to know how can I change the screen RGB values and also the dpi.

One suggestion is that after long pressing the power buttom were available the complete silence function.

Thank you!
[Nexus 6 Android Development] michmeister:
Exactly what happened to me.
[Nexus 6 Android Development] Cincybearcatfan:
I need help with this. I am or was unlocked, rooted, encrypted with TWRP. I downloaded the zip and attempted to install it in recovery using TWRP. I wiped Data, Cache and Davlik. It attempted to install. It took me to a screen and asked for my Android password. I had no idea. I tried to use my Play Store password but it said that was wrong and took me back to recovery and attempted install again. Again it brought me back and asked for my Android password. I entered a 4 digit code that I often us to lock my phone. It said that was the correct password but I needed to wipe my partitions to decrypt. It said decryption successful, but in the process it wiped everything and I mean everything but TWRP from my phone. I have no recovery to go back to. I no longer have the file "Pure Shamu" on my phone to be installed.

I can get back into recovery. TWRP is working. I can even connect my phone to my laptop. My laptop recognizes it and I can open the drive on my laptop, but whenever I try to copy anything to my phone from my computer (i.e. a new copy of Pure Shamu) my laptop tells me "This device has either stopped working or has been disconnected" and it won't let me add anything to the hard drive of my N6.

Please help me figure out what to do from here.

I thought that maybe my drive wasn't mounted. Here is what is checked: System, Data, Cache and Firmware. I can't seem to get USB-OTG (whatever that is) to receive an X.
[Nexus 6 Android Development] ScottIsMyName:
When you're in recovery, try pushing the rom to your phone using adb:

adb push <rom file> /sdcard/.
adb push <gapps file> /sdcard/.
adb push <supersu file> /sdcard/.

Then flash all of the files in recovery once they're pushed
[Nexus 6 Android Development] Cincybearcatfan:
I was hoping to be able to do it without ADB commands because I can't seem to get that up and running on my laptop. Is there any other way?
[Nexus 6 Android Development] TheAnarchist1:
Folks, you are encrypted, use the link below to help you:

http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715

PS: Search is your friend ^_^

Just a friendly reminder

PS: Once you follow those steps, then do a data reset from within TWRP (type YES when it asks), and MTP will stop working quite as wonky.
[Nexus 6 Android Development] cr4ck3r4lif3:
Use this toolkit. It'll help you out.
http://xdaforums.com/showthread.php?t=2947452
[Nexus 6 Android Development] TheAnarchist1:
Do not use Toolkit. It will not help you inside of recovery, nor can you easily use adb in there either unless you do a sideload, which can be a bit iffy.
[Nexus 6 Android Development] Cincybearcatfan:
Thanks for the link, but that still doesn't help me. How do I get those files on my phone without ADB commands?
[Nexus 6 Android Development] TheAnarchist1:
What you need to do is boot into bootloader, and fastboot flash the modified boot, then fastboot format userdata. Go into TWRP, and select erase Data, type YES, unhook phone from usb, reboot recovery, and the file system should be rebuilt and MTP (file transfer in TWRP) should work again.

OR

You could just take a swing, boot into recovery, select wipe, then DATA, type YES, let it do its thing, and then reboot recovery, and it should work, you should be unencrypted. TWRP right now has a bit of a bug in it that makes MTP wonky with encryption present.

Seriously though dude...if I were you. I would not be playing around in this stuff without the SDK installed and adb/fastboot commands present. You are going to get yourself into a pickle.

Just a friendly warning. :o
[Nexus 6 Android Development] rebretz000:
All I was telling people is that they don't have to decrypt to flash the ROM if they don't want to. Especially if they want to flash on the go. It's not that big of deal. Think about it. The ecryption/decryption is in the boot.img. Change the boot image. That's how I figured it out. I decomplied/unzipped a ROM, removed the decrypted boot.img, and replaced it with the stock boot.img. Next logical step was to just try and flash a kernel before booting. Just because you couldn't do it and had issues doesn't mean it's not possible. I've not had one issue at all. No matter the ROM I was using or the carrier I was on at the time.

Curious as to why you are getting so mad about this? Sorry this works for me I guess.
[Nexus 6 Android Development] TheAnarchist1:
[MENTION=4733876]rebretz000[/MENTION]

Encryption causes a lot of trouble with TWRP MTP right now, for some reason, especially in the shift between. It is probably just good to remain unencrypted if you are going to crackflash in the long run. Its such a hassle but it creates a lot of issues when flashing between roms
[Nexus 6 Android Development] Cincybearcatfan:
Just got it up and running. Now hopefully this will be a lot easier.

---------- Post added at 02:55 PM ---------- Previous post was at 02:38 PM ----------

Up and running again. Thanks to everyone that helped out. This was much more cumbersome than when I used to flash ROMS daily with my Galaxy Nexus. I think it was because of the encryption. Normally, I'd flash into recovery, wipe data, cache and davlik, flash the new ROM and reboot and everything was fine. That was not my experience now.
[Nexus 6 Android Development] cr4ck3r4lif3:
The toolkit would have got your adb setup since you had issues, but sounds like you're good to go. Happy flashing!
[Nexus 6 Android Development] Takuapina:
Another thing that I've noticed is that both whatsapp and telegram icons doesn't show up the number of messages that you haven't read yet. This is more for european users I guess who use such apps. Would be nice to have this
[Nexus 6 Android Development] rugal316:
Hi can I flash this ROM on a lrx22c nexus 6, sorry for the noob

question
[Nexus 6 Android Development] RamOdin:
Hey [MENTION=4289339]error311[/MENTION].. Just curious, why did you remove long press to kill back?
[Nexus 6 Android Development] Spaten75:
Yes.

You can set your nav buttons however you want in the nav bar editor.
[Nexus 6 Android Development] Roland Deschain:
Anybody else seeing abnormally high battery drain from cell standby on 3.97? (Most of the time spent on Wi-Fi, too. Franco kernel r8.)
[Nexus 6 Android Development] michmeister:
Because you've said that a million times and without decrypting problems like above are happening. Stop trolling about no need to decrypt.
[Nexus 6 Android Development] digitalb0y:
I'm not mad, I'm just attempting to make sure information is accurate so people can make educated decisions about what they flash. You broke apart a rom and swapped out files AND flashed a custom kernel, neither of which are part of the procedure people are asking about, and you still keep telling people seemingly definitively that they can just leave their devices encrypted, no additional steps necessary. I am not saying you did anything wrong procedurally, and I'm not asking you to apologize for telling people what worked for you. I meant it when I said I was glad things worked for you. I'm just pointing out that when people say "do I need to decrypt," it's not accurate to say that if they follow the steps in the OP they won't have to decrypt. Some level of replacing the forced encryption is necessary.

I am not trying to single you out or make any personal comments. I'm simply trying to correct disinformation for the benefit of those asking. Coming from stock, rooting, then flashing this rom, then gapps, then SU, will result in an error caused by not being able to decrypt userdata at startup. At some point during or prior to the procedure of installing this rom, you need to flash a boot.img that disables the forced encryption setting. Whether you do that with a custom kernel or something else, it's not an unnecessary step, and depending on how you do it, it results in an unencrypted device which can then be encrypted again if you want.
[Nexus 6 Android Development] rebretz000:
So by me telling people I have no issues and I'm still encrypted is trolling? Okay I get it. Sorry. Did not know.
[Nexus 6 Android Development] sykopompos:
Actually, the change is a tiny one in the fstab from forceencrypt to encryptable so (I'm 99.999999% sure that is the method error used for the rom) there is no need to decrypt at all unless you want to because that change supports encryption on or off.

It is in his change log that he changed it to encryptable so I could be mistaken if there is something else at play here and if so, then excuse me
[Nexus 6 Android Development] Spaten75:
One thing i don't understand which I think is confusing a lot of people...Could someone explain why unencrypting is necessary (without flashing a different kernel or replacing the boot.img) in order to flash this ROM? It seems counterintuitive that having your data encrypted is less compatible.
[Nexus 6 Android Development] digitalb0y:
It's not that you can't be encrypted, it's that there's some strange behavior with the software encryption as it ships on the device. The first paragraph at this link says:

Flashing the boot image in that thread disables the forceencryption option (and also decrypts the device). It doesn't mean you can't be encrypted. You can re-encrypt from there if you want, but the forceencryption option is what needs to be replaced.

---------- Post added at 02:54 PM ---------- Previous post was at 02:40 PM ----------

True, it's just that the method for changing forceencrypt to encryptable that is linked by error and followed by most people here decrypts the device. All I've been communicating is that at some step, the forceencrypt option needs to be replaced. Saying that leaving things as they are and flashing this rom is not going to cause problems with the encryption is inaccurate.
[Nexus 6 Android Development] sykopompos:
I had no problems flashing aosp with encryptable in the fstab. I just decided to go unencrypted afterwards in the long run as a developer and flashing so much on my device
[Nexus 6 Android Development] digitalb0y:
Hi [MENTION=4289339]error311[/MENTION],

I don't want to sound demanding but I've seen a few requests for additional Quick Options tiles and thought I'd ask about the one I miss most: toggling screen lock. Would adding this sooner or later be too much of an issue? Thanks either way!
[Nexus 6 Android Development] lensgrabber:
Just want to make verify others are seeing this too. I'm on 3.97 w/ Franco R9. Landscape mode makes the nav bar go away. No matter what I try, including enabling/disabling both landscape and portrait navbars and resizing both landscape/portrait navbars, I can't get anything in landscape. Portrait works fine. I've tried setting the density back to stock from the 420 that I usually use. No luck. Is this part of what others are seeing with the navbar problems or am I chasing another problem? I'm also seeing priority mode come on at boot and throughout the day. That is probably a rogue app that just needs to be tracked down though.

Cheers,

Robert
[Nexus 6 Android Development] dipstik:
same setup as you and im not having that problem. i was having a problem with videos getting stuck in portrait or landscape, but a reboot fixed it.
[Nexus 6 Android Development] rebretz000:
Last time, never said leaving alone as flashing as is. Gave specific steps. Same thing with flashing rom, people don't read properly, own fault.
[Nexus 6 Android Development] digitalb0y:
Your exact words:

You didn't indicate that you thought "correct steps" are different from simply flashing this rom, gapps, and su., as the OP here suggests. Sorry if you think I shouldn't be making it clear that additional steps are needed. Knowing ahead of time would have saved me a few minutes and an extra flash and reboot, and people here are asking about this a lot. You think what you said was accurate, I think it was misleading. Regardless of who thinks what, the point is that users will need to do something to replace the forceencryption option, which in all likelihood will at least temporarily decrypt their devices, and that's a more accurate answer than "nope, encryption won't be an issue." No personal attack intended and that's the last I'll say about this.
[Nexus 6 Android Development] rugal316:
Hi

Great ROM, is there a way to change or add reverse phone number search for UK instead of the us?
[Nexus 6 Android Development] rebretz000:
If you or michmeister would have bothered searching I did post the steps I took. Rule of flashing.. Read and search. No one is responsible but yourself.

Sent from my Nexus 7²
[Nexus 6 Android Development] michmeister:
I do read, trolling again? This ROM is amazing I flashed before the op mentionef the force encrypt link so I ran into trouble because I wasnt decrypted. I read every page of this thread. And I don't troll with wrong misguided info like yourself.
[Nexus 6 Android Development] makeshiftharmony:
T T T
[Nexus 6 Android Development] 414isaiah:
will you two stop the bickering please, its annoying, thanks.
[Nexus 6 Android Development] michmeister:
Yes I will sorry.
[Nexus 6 Android Development] jayharper08:
Guys, I do not like coming into a thread of the rom I'm running and seeing nothing but jabs at each other, and I'm sure no one else does. If you want to argue, take it to PM. It's disrespectful to [MENTION=4289339]error311[/MENTION] and everyone who doesn't care to see it in a development thread. Thank you. ;)
[Nexus 6 Android Development] Quacker:
I really don't want to belabor this argument in this topic but it has confused me. Does anyone other than the two posters here who are clearly passionate about the encryption issue have a definitive answer? Can I flash the ROM and gapps and root as instructed while still encrypted?

I am interested in this ROM but I'm not interested in decrypting my device. I didn't see anything in the install instructions or the OP that says decrypting is required so I figured I was good to go. The only reference is: FORCEENCRYPT replaced with ENCRYPTABLE. What exactly does this mean in terms of the installation procedure?

Thanks!
[Nexus 6 Android Development] rudydimacali:
I actually finally got my Shamu last night after coming from a G3, and I was able to install the ROM and gapps and root, WHILE being encrypted. I used Wug's Nexus Root Toolkit to unlock my bootloader and install TWRP, and while still encrypted, got Pure Shamu, gapps, and root all working perfectly completely set up with custom DPI and the works to my liking.

Unfortunately, once I learned about encryption on the N6, I had to go back and spend another couple hours redoing my phone because I removed the encryption then re-flashed everything, but yes, in my experience, I had the ROM and gapps and root working while encrypted. I did check in settings to see if I was encrypted.
[Nexus 6 Android Development] digitalb0y:
The link in post #8 should cover everything you would need to do, since you're likely already unlocked and rooted if you're considering a custom rom. Flashing the boot.img from that thread is the only additional step, so I would do that and then come back here to follow error311's advice for flashing this rom. Your device will be unencrypted on your first boot of Pure Shamu, but you can turn encryption right back on if you like.

As some have pointed out, you can also set the encryptable option by flashing a custom kernel, but I'm not sure that is documented quite as well, and involves no fewer steps than the above.
[Nexus 6 Android Development] sykopompos:
Since you guys are griping, I figured I distract you guys with something you might not know.

In the 1/8 build, error added in 5 commits for fixes for runtime resource overlays, that was meant for a project that I and other have been working on

It is a direct competitor to the cm theme engine for aosp but entirely supported by aosp as a method for OEMS to provide themes and we tweaked it to work for the community. Right now the project is still a baby and just getting started but I figured I let you guys know that you are supported with those commits with it.

Link for the beta testing community, you gotta request to join and then you can opt to be a beta tester

https://plus.google.com/118195502410326243266/posts/JPdEBJdrKdF

Ps there is also 2 other cool apps there in beta testing that you can check out too, RomMate and a new File Manager
[Nexus 6 Android Development] n80k:
Wow. I dug into those posts on google+ a bit and if I'm not mistaken this means that you guys are in the process of bringing native theming to lollipop 5.1 (presumably) and beyond? And these commits let us test it out in the meantime?
[Nexus 6 Android Development] moopile:
I don't think anyone is "trolling" (probably one of the strongest forum insults). The method [MENTION=4733876]rebretz000[/MENTION] describes has allegedly worked for several people in this thread, and [MENTION=4289339]error311[/MENTION] even referred to [MENTION=2942485]Cy_n_ic[/MENTION] 's post where he describes the same method. I agree that Error and others have suggested the method of decrypting first as that is what most people want and seems to be the best way without using a separate kernel. I am not arguing the pros/cons of encrypted vs decrypted. I'm not saying rebretz000's method works. I'm just saying I don't see "trolling" going on. Just a difference in opinion on how something can be done. If that method works for those wishing/needing to remain encrypted without having to backup/restore encrypted data between each flash and then re-encrypting it after the flash, I don't see the problem with the information being made available. I did search the entire thread and found a few people it worked for and 1 who said it caused a problem. Instead of arguing, it may be best to just remind people to backup their data before trying either method then let them see which works best for them.

I believe both sides of the argument were trying to look out for peoples best interest and I appreciate the enthusiasm. I just hate to see it devolve into name-calling. I'm sorry if this adds to the clutter, but until rebretz000's method is proven false, I think having both sides available can only help the community.

Good luck everyone and happy flashing.
[Nexus 6 Android Development] sykopompos:
Basically yes. There will be about 1 or 2 more for roms but then everything is themable
[Nexus 6 Android Development] mikkelwe:
I've been reading some of the posts about encryption vs no encryption using this rom. At the moment I have pure shamu b3.97 installed without encryption but would like to enable encryption because of the security benefits. Reading your posts it seems if you enable encrytion you won't be able to upgrade pure shamu without having to disable encryption again and thus having to go over the tedious backup/restore/reincrypt routine unless you flash another kernel first, Is that correct?
[Nexus 6 Android Development] moopile:
Tbh, I don't have a clue. I don't think you can't just dirty flash the rom alone. I assume, as you speculated, you would need to flash one of the suggested kernels. Theoretically something like: BACKUP, wipe, flash ROM, flash gapps, flash root, then flash kernel.

I really wish I had the time to return to full stock and experiment.
[Nexus 6 Android Development] Nacho~:
This ROM does NOT decrypt your phone, it just turns off FORCEENCRYPT meaning that if you are already decrypted, you will not have to decrypt again after flashing this ROM.

I have NEVER decrypted my phone and it runs perfectly with his ROM (3.97). rebretz000 is 100% correct in saying that, prior to first boot after flashing this ROM, an encrypted user should flash a kernel like Lean, Faux, or Franco. This will prevent that encryption password screen from coming up. After that, Everything will work as it normally would. Voila.
[Nexus 6 Android Development] duffman452001:
Having issues with the hotspot tethering in the last few builds (on VZW). My devices will connect to the hotspot,and traffic will pass for a few moments, and then it will stop working. It's been like this for the last couple builds. Any ideas?
[Nexus 6 Android Development] Spaten75:
And herein lies the trap/confusion. You can run the ROM but cannot use the stock kernel that comes with it. The question I have is why, when the OP of this thread states forceencrypt was changed to encryptable. What makes the stock kernel with that flag changed different from one of those other kernels?

Hmm, i may have just figured it out. Does flashing one of the other kernels not change the flag, then? Meaning if you are stock encrypted (with forceencyrpt) and flash this ROM and then one of those kernels, you cannot decrypt?
[Nexus 6 Android Development] mikkelwe:
Maybe so.

But why can't it access an already encrypted file system if encryption is enabled, though optional? I mean encryption is not stated to be disabled just optional, right?
[Nexus 6 Android Development] Spaten75:
Perhaps it has to do with what the flag was set to at the time of encryption?

I found some light reading on the subject:

http://source.android.com/devices/tech/security/encryption/index.html
[Nexus 6 Android Development] error311:
I recommend everyone to signup to this very nice to see their examples of what will come :)

Sorry I haven't posted I had a problem with my build which actually sykopompos helped me solve the problem I was having.

After that got fixed one of my memory sticks in my ubuntu machine went. Everything good now so finally can get back to working on those issues in b3.97.

I will post about encryption once I get home from work but the link posted above pretty much explains it all.
[Nexus 6 Android Development] sykopompos:
What flag do you guys keep talking about?????

No where in there does it say any if that other then the line that gets replaced in fstab?

I think you guys are all making a mountain out of a mole hill on a random thread of all things force encrypted vs being able to choose
[Nexus 6 Android Development] michaelnel:
Just updated to 3.97. Seems to work OK, except that the three soft keys at the bottom of the screen are absolutely TINY. So small they are difficult to select.
[Nexus 6 Android Development] saj2001ind:
just try readjusting it
[Nexus 6 Android Development] michaelnel:
Yep, adjusting it fixed it. Thanks, I did not know you could adjust them.
[Nexus 6 Android Development] ScottIsMyName:
No problems for me here. I'm also a VZW user and have tethered several GB's worth of data the last few days. I know it sounds silly, but have you tried a simple reboot, or toggling airplane mode?
[Nexus 6 Android Development] mikkelwe:
It would be nice too know the best approach to take if you like to enable encryption on this rom. Are you supposed to be able to upgrade and stay encrypted if you have encrypted data from the security settings or will you have to backup, wipe data, restore and re-encrypt every time you upgrade the rom or are you supposed to flash a custom kernel as some posts suggest? Maybe it's self explanatory to a developer but personally I find it rather confusing. The first time I flashed this rom I was surprised to be met by the dreaded password prompt after the first boot because I had wrongly assumed that since the rom supports encryption it would be able to use my encrypted data partition (stupid me!). After reading a bunch of posts I find out you should wipe data completely in twrp before flashing if you were already encrypted unless you also flash another kernel. I would just really like a recommendation for the best approach to use encryption with this rom without doing the tedios backup, wipe, restore, re-encrypt at every single update.

And thanks a bunch error311 for a really nice and neat rom! It's much appreciated.
[Nexus 6 Android Development] duffman452001:
I rebooted a few times. Strange thing is it worked just now when I tried it, but im also now in a 3g only area.