yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] andTab:
Did you enable encryption? Any issues/problems? Have you done a ROM upgrade since then (e.g. flash a Feb 16 version of Candysix over Feb 14 version)?

Sorry for the off topic question - which version of TWRP does support encryption?

Last but not least: does anyone know what the Fast Angler ZIP files are here: https://temp.bbqdroid.org/

They look like Kernels but I suspect that Angler is the codename for a different device ...
[One (M9) Android Development] weinberk:
I've only tried with official builds, beta 2 being the latest and it definitely doesn't work.

See http://xdaforums.com/showpost.php?p=65090338&postcount=343

TWRP 3.0.0-1 now supports encryption on the M9.
[One (M9) Android Development] andTab:
Cool. Will definitely upgrade to that version and will anxiously wait for a version that supports encryption.

BTW - Here are the bugs that I have encountered so far:

- Camera with storage on SD card enabled (and using SD card as an external storage device) - cannot take more than 1 photo without the camera app crashing (and the 2nd photo being "lost"); workaround is to open the gallery app from the little preview at which point it is possible to take a 2nd photo. Maybe some kind of write issue?

- 2 days ago my phone rebooted in the middle of the night and got stuck on the boot screen. Forcing the phone off (hold power + volume up), I was able to restart normally. No idea what caused this.

Also: some apps have issues using the SD card due to Google's weird implementation of read/write access (e.g. Syncthing) - it is possible to get a fix implemented? This is really stupid on Google's part and I have no idea how they could break SD card functionality like this. I have sneaking suspicion that issue #1 above may also be related to this.
[One (M9) Android Development] weinberk:
Note, the TWRP dev for the M9 doesn't think that 3.0.0-1 will work with the lollipop firmware. [MENTION=3472611]dottat[/MENTION] might a MM firmware be available from you?

Related question, if a Lollipop firmware works with this Marshmallow rom, would the converse likely be true??
[One (M9) Android Development] dottat:
Santod posted the mm firmware.
[One (M9) Android Development] Icemaine:
I can confirm the new marshmallow firmware pulled from the OTA worked fine for me.
[One (M9) Android Development] weinberk:
Thanks. Trying to get that going but htc_Fastboot is complaining:

sending 'zip'... (48120 KB) FAILED (data size is too large(48120 KB) for device to download ZIP file '3.37.605.7_NoBoot-NoRecovery_firmware.zip'

Need to figure out what's what there. Odd.
[One (M9) Android Development] weinberk:
Sorry for my late reply. I've seen the same thing with VZ on Candy5.
[One (M9) Android Development] LTKred:
Angler??

Hey, anyone know what the "Angler" builds are on https://temp.bbqdroid.org... are they for the M9 or a different device?
[One (M9) Android Development] thicklizard:
Angler is the nexus 6p
[One (M9) Android Development] bacon612:
OK guys

Himaul

https://www.dropbox.com/s/h6rupqfv0uurime/CandySiX-1.1-himaul-UNOFFICIAL-0220.zip?dl=0

Himawl

https://www.dropbox.com/s/16zar0qllpks6fu/CandySiX-1.1-himawl-UNOFFICIAL-0221.zip?dl=0

Himaul tested. Working well for me. Himawl, no idea. Let me know.
[One (M9) Android Development] weinberk:
[MENTION=5349944]calebcabob[/MENTION] figured I'd give you an update about encryption, this time using the Marshmallow firmware instead of Lollipop.

I updated my VZW m9 to the MM firmware by [MENTION=1331268]santod040[/MENTION] while I was running Candy5. From recovery, I then installed beta2 of CandySix. Started fine. No gapps, no xposed, just the rom. I immediately went to security and encryption. I clicked encrypt phone and it restarted. It gave the warning that it takes a long time and is irreversable, but did NOT ask me to select a pin. [ I think this is okay, MM doesn't require a pin - how it knows how to decrypt is beyond me ] The phone quickly reboots, CandySix logo to your spinning spiral animation and it goes right back into the rom. I't maybe a 15 second startup. The phone says "encrypted" under settings but TWRP doesn't prompt for a pin, and CAN see everything in data. I don't remember if I tried this no-pin encryption with the LP firmware and CandySix.

To continue testing, I factory reset, started candysix. This time I entered screen a lock pin first, then went to encryption. This time is asks me to confirm the lock pin (that's as expected). The restart process is still super quick (probably because there's basically no data to encrypt yet), but it then hangs on Starting Apps.

As a final test, I repeated the firth method, encrypting without first selecting a pin. After reboot, in settings it said encrypted (good). THEN I went and entered a pin. TWRP still didn't ask for a pin and can see everything in data (my sample photo). CandySix boots without hanging on starting apps, but I suspect that the phone isn't really encrypted (or could it be encrypted with a key that can be unlocked with no pin ????)

Whatever the case, there doesn't seem to be the ability to properly encrypt the data with the current beta2, even with the Marshmallow firmware.
[One (M9) Android Development] santod040:
Which version of Twrp are you using?

I know that anything prior to 3.0.0-1 doesn't support Aosp encryption.

But 3.0.0-1 does, which is the version I included in the firmware zip that includes Twrp.

Just throwing this info out there, as I can't say as though I've tested it personally.

I just know that was a feature added in that specific Twrp build for this phone, since Captain_Throwback told me this personally when he had me test that build.

**Edit

Just read back a few posts, looks like this has already been mentioned...

Just saw myself mentioned and thought I'd chime in while mobile.

Guess I should have read back first.
[One (M9) Android Development] weinberk:
I'll try to give this a go shortly. Is there a change log?

Question: I see that you've got these releases listed as unofficial. Are you part of this team, or "just" building from github source and making that available? (if you're building, are you changing anything? Would love also to know if you're using a guide so that maybe I could build myself).

I ask, because I want to have a clear understanding of what's what, who is who, where the ROM that I'm flashing comes from, what's changed, etc.

Can you explain where you fit into this wonderful world of Candy?

Thanks!
[One (M9) Android Development] Icemaine:
That is odd. Here are the steps I used 1. I went back to my backed up system image. 2. downloaded the ota 3. pulled the ota off of my device 4. extracted the firmware.zip 5. followed the firmware flashing instructions 6. flashed the recovery back to twrp the flash removed, then factory reset to solve slow boots and bootloops. My device remains soff and unlocked. I didn't even have to use my clip.
[One (M9) Android Development] weinberk:
odds and ends

[MENTION=5349944]calebcabob[/MENTION], requests, based on my very limited use of beta2:

1) Allow camera to have video settings changed from 4k. I don't need/want 4k video, but changing to regular HD FC's right away and then FC's the camera app at startup every time. Clearing app data and leaving it at 4k is the only fix I know.

2) Don't forget to add the exchange services and email app back.

2) Is there a way to stop the phone from telling you that the sd card is in as portable storage? Once you say, this one is portable storage and not to encrypt it making it internal only, I don't see a reason to tell you each startup.

---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------

Glad to see that I'm not the only one with occasional "missed what you said before" posts.... I'm so appreciative of your efforts here. You're almost always quick to respond and if that means that you might ask something that's been answered already, so be it!

I'm using 3.0.0-2 now. [MENTION=1162986]Captain_Throwback[/MENTION] worked his butt off, I think largely because of my near begging, to get TWRP to support encryption. However, it's not TWRP where the issue lies, it's the ROM. Even with the 2.x versions that didn't support encryption on the m9 at all, encryption still worked within Candy5. Granted, you couldn't view data in TWRP nor would TWRP accept your pin, but you could still flash. TWRP 3.0.0 stopped prompting for the pin since it wasn't going to work. Then 3.0.0-1 supported decryption, but it had to be with MM firmware (or it wouldn't even boot into recovery).

---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------

Thanks for chiming in. That's essentially what I did, but started with the zip from the firmware thread. Tried several times with a couple different fastboot exe's. Ultimately worked. Had to be something on my end.
[One (M9) Android Development] rc420head:
Yes he is member of candy team, one of the original hima testers and is now running builds as me and op don't use hima as daily driver therefor don't run hima builds on regular basis, I have ok'ed his builds to be official in the future. Changelog should be linked in op.

On another note I see cm is doing a kernel rebase on newest source, once it's ready we will use it In new builds
[One (M9) Android Development] PrizmaticSmoke:
Himawl build is working great so far for me on latest firmware, thanks!:good:
[One (M9) Android Development] bacon612:
I am just a tester for gsm candy. I am willing to build here and there. I can't promise any dev changes but will continue to build updates
[One (M9) Android Development] rc420head:
As far as encryption I'll be honest Idk whats up with it, when I get time I'll look into it (sooner than later). I would guess we need some source side commits (assuming cm has it working?) if you see any commits related to it feel free to link them.

Sent from LG h811 running CandySiX
[One (M9) Android Development] calebcabob:
[MENTION=360274]weinberk[/MENTION]

Sorry I haven't been in here a whole lot lately - just been very busy. To answer your questions...I have no idea about the sd card encryption that you're referring to. If you are able to find some commits related to what you're talking about, share them here - maybe they can be added.

Email/exchange has already been added back.

As far as the SD card notification you're talking about, have you tried long-pressing it and selecting the (i) symbol? It should bring you to the area where you can toggle "block all notifications".
[One (M9) Android Development] weinberk:
Excellent!

Heh! Not "just" a tester, but also a builder - and that's greatly appreciated!

I really don't know if it's working in CM - there's no way for me to try being that I have a Verizon model.

Glad you apologized. It's unacceptable for you to do anything but update this ROM. You owe it to us. Oh wait, no you don't!!!!!!!! :D

From what I've been reading, the SD card apparently is encrypted if you choose to have it initialized as an extension to internal storage. I haven't tested this - I want to keep my sd card able to move from device to device. That's what I mean by sd encryption. What I was really asking is why the phone has this burning desire to give you the option to make it internal storage every time. I HAD not been able to make it stop, I'd swipe it away, but it would come back after reboot. I just restarted to show you a screenshot, and what do you know? It's gone. I really didn't do anything different. I'll let you know if it comes back...

---------- Post added at 03:17 PM ---------- Previous post was at 02:48 PM ----------

Curious, did you try encryption? (don't if you haven't unless you're confident in your backup)

---------- Post added at 03:32 PM ---------- Previous post was at 03:17 PM ----------

Just tried unofficial 1.1. Same experience with the encryption attempt. We figured that this would be the case, but wanted to share my experience.

It does appear to encrypt. TWRP asks for PW and if entered correctly can read internal data. But the ROM won't finish booting. Hangs at CandySIX is.... starting apps....

Also, camera app, if you change from 4k video to HD, it crashes as before.
[One (M9) Android Development] andTab:
Where did you find unofficial 1.1?
[One (M9) Android Development] liam_davenport:
Few posts above you ^^
[One (M9) Android Development] artizanoil:
Does it matter if you are on LP or MM firmware for the unofficial 1.1?
[One (M9) Android Development] liam_davenport:
Not tried it with LP myself but I'd use MM to be safe
[One (M9) Android Development] calebcabob:
Any verizon M9 users in here not on the latest firmware?
[One (M9) Android Development] artizanoil:
I'm still using the LP Firmware with the 0116 rom

---------- Post added at 08:05 ---------- Previous post was at 08:01 ----------
[One (M9) Android Development] weinberk:
I'm MM now, but can go back to LP if you need testing on my VZW m9.

(You might want to update the initial post to reference the MM firmware, at least as an option)
[One (M9) Android Development] weinberk:
Encryption in CM13

Apparently encryption in CM13 doesn't work either:

http://xdaforums.com/showpost.php?p=65485701&postcount=312 :(
[One (M9) Android Development] sherry478:
can someone list down the thing working and not working in this rom?
[One (M9) Android Development] rc420head:
Not working AFAIK

Dt2w

Encryption

Some media apps (Pandora) won't play through speakers

Anything other than 4k video recording crashes cam

Off the top of my head that's it

Sent from LG h811 running CandySiX
[One (M9) Android Development] bacon612:
That 1.1 unofficial that I posted should work on either firmware. Will be one of the last that will too. Newer version will require mm firmware but there are bugs being worked out.
[One (M9) Android Development] andTab:
Expanded list:

Dt2w

Encryption

Some media apps (Pandora) won't play through speakers

Camera:

- Anything other than 4k video recording crashes cam

- saving to SD card crashes cam when trying to take a second photo (workaround is to open gallery app from preview, see photo, go back to camera)

- Flash option appears disabled with no way to enable camera flash
[One (M9) Android Development] PrizmaticSmoke:
The last 2 items you listed are not issues for me at all on the latest unofficial 1.1 that was posted a couple of days ago. Saving to either internal memory or SD card works fine, I can snap away with no crashes on either option. Flash also works fine - I can change it to off, on, or auto as desired (it's on auto by default), and it works just fine for me when set to either auto or on. I don't recall these being issues for me on the previous 1/25 official build either (I snap a lot of pics of my kids and would have noticed either issue fairly quickly).
[One (M9) Android Development] andTab:
Sadly, I have yet to see a reputable source for downloading 1.1 ...

Bugs are definitely there and survived multiple flashes and wipes. Google camera works fine.

Do you use sd as portable or internal?
[One (M9) Android Development] calebcabob:
Doesn't work that way. Also, it's broken on every non-stock based ROM for M9 still.
[One (M9) Android Development] calebcabob:
Thanks. I sent you a PM
[One (M9) Android Development] bahuy2003:
When do we have a new build?
[One (M9) Android Development] rc420head:
Never thanks for asking

Sent from LG h811 running CandySiX
[One (M9) Android Development] andTab:
Don't think it's an unfair question given the 1.0 and 1.1 builds poster for all the other devices and there aren't even any unofficial builds posted at temp.bbqdroid.com.

No need to be rude about it.
[One (M9) Android Development] rc420head:
You won't find any hima builds there anymore, he's moved on to different device, we are having problems with hima right now, do you want 1.1 release that's broke so then you have something new to complain about?

Sent from LG h811 running CandySiX
[One (M9) Android Development] NoSpamDan:
Aaaaah, the irony...

It's not a formal rule here but it's rude to ask for ETAs. It will most of the time draw a rude response and summon the trolls. :eek:

You've been around long enough to know this.
[One (M9) Android Development] andTab:
Considering he said he would post new builds ... and then there was no news or anything, asking what is going on is justified. The response was rude and uncalled for.
[One (M9) Android Development] NoSpamDan:
Nope, ask for an ETA, and you will almost always get flamed. VERY tame response from what I've seen.

Maybe try a different approach next time, like not asking for an ETA. :rolleyes:

I'm sure [MENTION=5349944]calebcabob[/MENTION] will post updates here whenever he's ready. You just have to be patient...

Cheers!
[One (M9) Android Development] hallstevenson:
I'm sure he didn't say when they would be available. They're done when they're done ... if he chooses to build them. He can change his mind too and not do them at all.

He isn't paid (by you or anyone) to do these things on a schedule or at all.
[One (M9) Android Development] andTab:
If caleb says he will drop some builds "this week" and then nothing is posted, it's only fair to ask what's going on.

But sure ... go ahead and defend a bully who is just rude and unhelpful.

Besides: if he hadn't asked, we wouldn't know (1) that Chad has dropped support for doing M9 builds, (2) that there are some issues with the latest builds, and (3) that support amongst the Candy-team for the M9 is a low priority.
[One (M9) Android Development] rc420head:
No m9 isn't low priority it's just that my job you know what pays my bills and feeds my family is higher priority and I've been super busy with that. I made snappy remark because I felt like being a dbag and it was funny. I plan to work on this tonight along with fixing VoLTE, caf kernel for g4, and making sure all my device tress are up to date. After working a 60 hour week hopefully I can get half of that at least started before I fall asleep at me computer like I did last night.

Sent from LG h811 running CandySiX
[One (M9) Android Development] hallstevenson:
No, it's not "fair to ask". You sit and wait. Nothing more.
[One (M9) Android Development] rc420head:
Ok let's all calm down, group hug! Lol we will work on this tonight, for now I'll revert all the mm blobs and kernel until we can get them working properly so op can get some builds for you guys, we work as a team so sometimes our schedules don't line up.

Sent from LG h811 running CandySiX
[One (M9) Android Development] Cryosx:
What you did was within reason, don't know why people getting mad at you for that. Someone says' X is going to happen, doesn't deliver/nothing happens, you naturally want to know what's going on.
[One (M9) Android Development] FNGHobo:
Guys stop arguing you sound like a bunch of kids. Let's all just agree this is the best ROM on the m9 and give our thanks.
[One (M9) Android Development] NoSpamDan:
No place for name-calling, bud. I'm sorry if my response(s) hurt your feelings. I do agree that it's fair to ask what's going on, however it's clear you don't see that the way you asked your original question was "rude and unhelpful". Let's at least agree to be done with this already. :rolleyes:

Sorry for the OT everyone... You are in good hands with the Candy Team... I am aware that they have been working on issues with hima, and I'm sure it's just a matter of time and patience here. :good:
[One (M9) Android Development] calebcabob:
Something personal also came up on my end and to be honest, rushing back here to answer to anyone with the audacity to bug me about it (on the 7th day) was the last thing on my mind. So, anyone who is gonna ask for ETA's can go flash another ROM. Not trying to be harsh but I mean, there's a reason why it's one of the few rules on XDA. After [MENTION=5066258]rc420head[/MENTION] graciously posted an explanation, and even said he'd spend some time with it tonight, you insisted to go on with this whole thing. So here's a new update:

As of now there's no date set for when you might have the opportunity to flash CandySiX's next build. That's enough about this now.
[One (M9) Android Development] artizanoil:
I flashed the unofficial 1.1 on LP firmware and everything t

Seems to be working great for what I use the phone for. Thanks again
[One (M9) Android Development] hallstevenson:
As it should be. You work on it, finish it, etc when you feel like it. I mean, what do people think, they can get their $ back that they paid you? [emoji12]
[One (M9) Android Development] jbfountain:
I've never used this rom, but I've been keeping up with everything. I've always enjoyed reading this thread, but it's starting to sound like a "Team of Vipers" if you get my drift. I'm talking about everyone not the development team. I hope everyone has this out of their system and this thread can be enjoyable to read again.

Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
[One (M9) Android Development] ricjuh:
Currently running this ROM with much joy. Sorry to hear about all the difficulties in development. I hope we will see new releases soon!
[One (M9) Android Development] weinberk:
FYI for those of you who want to record video in a resolution other than 4k. (which is a bug that exists on all releases so far, including the unofficial 1.1)

I gave the "HTC m9 Marshmallow Camera and Gallery for CandySix" a whirl and it seems to work quite well.

http://xdaforums.com/one-m9/themes-apps/htc-m9-marshmallow-campack-candysix-t3300228

Thank you [MENTION=2401586]jsaxon2[/MENTION]

---------- Post added at 02:48 PM ---------- Previous post was at 02:01 PM ----------

I'm a Verizon M9 user, and before that I was a Verizon M8 user (CM12.1). The Cyanogenmod M8 builds are "universal," meaning that they'll work on any carrier / phone variant. One download no matter if you have a Verizon M8 or the GSM only version. Was nice AND it helped to insure that if you popped out the Verizon sim and stuck in an AT&T sim, or an international sim if you were travelling, that you'd get full service. I know that the cyanogenmod team stopped the universal builds for new devices., don't know why.

I'm wondering:

1) What do you do to change the himaul (GSM) code base to compile for the himawl (Verizon)?

2) Might you consider a universal CandySix rom to make it easier for those of us to use multiple sim cards to switch carriers every now and again? (I tried with an AT&T sim in my Verizon phone - voice worked, data did not).

Thanks
[One (M9) Android Development] rc420head:
M8 was last universal rom cm will make, they separate the different variants to help with crossover problems

Sent from LG h811 running CandySiX
[One (M9) Android Development] weinberk:
Okay, but someone on the Candy team was able to take the CM base for the himaul and get it working on the himawl. Wouldn't it be beneficial to all if instead of separating it out it was an additive feature so that the Verizon (And eventually Sprint) M9 can run on any network? I'm clearly not a dev on this project, but I feel like if the CM team could do it for he m8, the Candy team should be able to do it for the M9, hence the question and suggestion.... Plus, once done, that means there'd only need to be one build compiled on your end.
[One (M9) Android Development] rc420head:
Your missing the point, they each run better separated

Sent from LG h811 running CandySiX
[One (M9) Android Development] weinberk:
OH - I didn't get that at all from your original reply. Thanks for the clarification.

Is there documentation / notes available for what's necessary to make a himaul ROM work on the himawl? I ask because I might >NEED< to have a more GSM/LTE version on my himawl. I doesn't make sense for a universal Candy rom if they don't run as well, but I might need to deal with that and build myself. Or maybe I need to get another phone for use internationally.
[One (M9) Android Development] bacon612:
Here is a lepian gsm build a built a bit ago. Working well for me so far. Vzw in the oven...

Thank [MENTION=5066258]rc420head[/MENTION] for unbungling the bungle so we can party again

https://www.androidfilehost.com/?fid=24438995911967669
[One (M9) Android Development] Roobwz:
I gotta say that this rom is amazing. Glad I had the guts to try it. Not missing my Nexus anymore lol. Good job!