yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M9)] sharkie405:
So as far as the 5/4 nightly...

I had the same problems with the quick settings. Well, let me start back further. For some reason earlier on, I'd flash a nightly by downloading the zip from the website and then wiping my phone clean and then installing the nightly. When I did this, starting with around the 5/1 nightly, I started having the missing quick settings & notification pull down issue. However, I some point I stopped being stupid and realized that I didn't need to wipe my phone just to install a new nightly. Dirty flashing in this instance would be fine. So, after dirty flashing, I no longer had the missing quick settings and notification pull down issue. But, with nightlies 5/3 & 5/4, I had an issue where Google Play Services and Google Play were missing, even though they had been there before flashing a nightly. Obviously, without Google Play Services, almost all Google apps stop working properly. My first thought was OK, I'll just download Google Play Services from somewhere and install it, but another bug I found was that I was unable to install any apks at all, so I was stuck at that point.

Tonight I wiped my phone yet again, and installed the 5/4 nightly cleanly. And again I had the missing quick settings and notification pull down, but I didn't have Google issues because I'd flashed the GAPPS zip right after the nightly flash. However, tonight I was able to fix the quick settings and notification pull down by installing a theme. I had seen this mentioned around as a fix before, but it never worked. For some reason, tonight it worked on the 5/4 nightly.

It still sucks that I can't just download and install the nightlies the way they were met to be installed through the phone because, for some reason on my phone, it breaks Google.

All in all, however, I have to say, this ROM is becoming more trouble than it's worth, for me and my phone anyway. I love the idea of having a clean version of Android running on my phone, and there are many things about CM that I love, and I course I love being on 6.0, but it's like I have to jump through hoops just to get major simple things functioning properly. I'll be honest, it's kind of a disappointment for CM, and not what I remember his ROMS being like back in the day.
[Verizon HTC One (M9)] RyanCanning:
I agree that the nightlies haven't been the most stable thing, but they are nightlies and they haven't been out for the Verizon M9 for very long (I also noticed that it's not an "unknown device" on the download page anymore so that's good) so I have faith that they'll eventually be pretty stable like they were on my M8
[Verizon HTC One (M9)] mikelikesbikes:
Running 5-8 nightly, working notifications, quick settings, and turn by turn GPS. No simultaneous voice/data, but that's to be expected.
[Verizon HTC One (M9)] Flyhalf205:
Same here. Everything works great for me. I wish there was a way to get simultaneous voice/data.
[Verizon HTC One (M9)] popularbelief420:
running 5-15 nightly. no cellular data. everything else works fine. im on straight talk using a cdma sim if that helps.
[Verizon HTC One (M9)] RyanCanning:
I'm also on today's nightly (5/15) and my cellular data is working, but I'm on Verizon
[Verizon HTC One (M9)] popularbelief420:
going to try a few switches i saw on candy rom to get cell data working and report back i really want this rom to work 100% daily driver for me.
[Verizon HTC One (M9)] Flyhalf205:
If still not working can you get a logcat of it booting and a couple minutes in after it boots.
[Verizon HTC One (M9)] mmurphyj93:
Can anyone confirm if GPS is working? I haven't had turn by turn directions on any of these. If so, let me know which nightly you're on. Thanks.
[Verizon HTC One (M9)] Flyhalf205:
GPS works fine for me. I'm on 5-16 about to flash 5-19
[Verizon HTC One (M9)] mmurphyj93:
Ok, thanks. I'm doing a clean flash of 5/19. We'll see how it goes.
[Verizon HTC One (M9)] Flyhalf205:
On previous HTC phones you had to verify you got a lock on a Sense rom and then restore to CM and GPS would work.
[Verizon HTC One (M9)] mmurphyj93:
Still nothing. I'm on the latest firmware. I guess I'll try flashing a Sense rom and getting a lock. Just to cover all my bases, I should be flashing an ARM64 gapps, correct?
[Verizon HTC One (M9)] sharkie405:
Yes
[Verizon HTC One (M9)] mmurphyj93:
Seems to have worked. Thanks for the tip!
[Verizon HTC One (M9)] thicklizard:
Has cm13 started using the new MM kernel source?
[Verizon HTC One (M9)] tomraedisk:
Data works fine for me and boots right up. I'm having an issue with trying to use it as mass storage. When i switch it over it totally disappears from the computer.
[Verizon HTC One (M9)] Flyhalf205:
See this post. http://xdaforums.com/showpost.php?p=66539050&postcount=53 I'm hoping to look into this problem.
[Verizon HTC One (M9)] mmurphyj93:
Hey guys,

I'm getting a reboot when I try to call someone. It happens exactly when I hit the dial button after typing in a number. I'm on the 5/19 nightly.
[Verizon HTC One (M9)] Flyhalf205:
I'm on 6-7 nightly and calling people is working just fine. I think I remember that build having issues You need to update.
[Verizon HTC One (M9)] Flyhalf205:
Yay!!
[Verizon HTC One (M9)] haztv:
I'm having an issue flashing this. I keep getting a red message saying error executing updater binary is anyone else having this issue? I'm on the latest firmware using twrp
[Verizon HTC One (M9)] Flyhalf205:
What TWRP version?
[Verizon HTC One (M9)] haztv:
2.8.7.0.
[Verizon HTC One (M9)] Flyhalf205:
That is probably your problem. Upgrade to 3.0.2
[Verizon HTC One (M9)] haztv:
Will do. Thank you
[Verizon HTC One (M9)] MrTrip:
I don't seem to have the enhanced calling option... Verizon right?

Edit: Well crud, seems this is abandon? https://review.cyanogenmod.org/#/c/137865/
[Verizon HTC One (M9)] Flyhalf205:
Yeah still being worked on.
[Verizon HTC One (M9)] MrTrip:
Well this is the last active ROM for the M9 being worked on now... :( kind of sad to see it dwindle so fast...
[Verizon HTC One (M9)] :
What Gapps package is supported/recommended, as using 6.x ARMx64 Full from open gapps causes setup wizard to crash immediately upon booting the phone.

Process:

Wipe all

Install ROM

Boot

Cyan setup

Reboot to Recovery

Flash gapps

Reboot

Setup wizard insta-crash (repeatedly).

This same behavior occurrs when I queue multiple zips such as Cyan, Gapps, then SuperSU.

Thoughts? (I may have just figured my own issue out... would wiping dalvik/cache after installing rom/gapps cause an issue? Never did on the SGS3, LGG3 or SG Captivate...)
[Verizon HTC One (M9)] Flyhalf205:
I use nano gapps. Which is auto selected when you go to the gapps link in the OP. You need to wipe all, flash rom, flash gapps, reboot to rom. I just tried that and it worked just fine. You don't need to flash supersu. Root is always built into cm.
[Verizon HTC One (M9)] :
Yes, root is always built into CM, but I find that the controls are rather lack luster and I trust SuperSU's binaries and app to control what I need to control. That said, I believe the issue was due to flashing the rom, then gapps, then wiping cache/dalvik. It seems something may be stored in cache that the gapps are reliant upon, as that is the only time I have Setup Wizard crashing. It's odd, to say the least.
[Verizon HTC One (M9)] TBova2002:
I had this problem yesterday, if you flash CM and then gapps before booting, everything works fine. If you flash CM, boot and let it config, then go back to recovery and flash gapps (any package) it gives you problems and looping setup wizard crashes.
[Verizon HTC One (M9)] Flyhalf205:
I had ran the RUU to fix an encryption problem I ran into with TWRP. When I flashed CM back I could not get a GPS lock... To fix you will need to flash or restore to a Sense rom and get a GPS lock in Maps and restore or flash back to CM and it works perfectly.
[Verizon HTC One (M9)] Flyhalf205:
Starting with todays build 8-15-2016, dt2w should be working :)
[Verizon HTC One (M9)] tmillz:
This rom is working great so thanks for all the hard work.

I'm having an issue running postgresql inside Linux Deploy, Kali. The error it gives is unable to write to shared memory, function not implemented.

Postgresql and metasploit framework work fine on the stock Verizon rom and kernel. I've searched all around the web for an answers. /dev/shm is mounted and I've tried changing shmmaxx/min with no luck. It just works on stock, and doesn't on CM. I'm wondering if someone knows why this might be happening? I've compiled the latest CM too to see if I can investigate. I think it has to do with POSIX kernel support.
[Verizon HTC One (M9)] tmillz:
I figured it out. The key to getting shmget to work in Linux deploy is to rebuild the kernel with SYSVIPC enabled. I thought I'd post it here in case someone stumbles across this issue.
[Verizon HTC One (M9)] lehthanis:
So I have both an m8 and an m9. Someone in the viper one thread for the m8 posted a file that was an adsp-bs that could be flashed to allow boomsound support. It works great on my m8. I was wondering if anyone has pulled an adsp from the m9 and made a flashable boomsound driver for cm13 m9?
[Verizon HTC One (M9)] thicklizard:
Got a link to said zip
[Verizon HTC One (M9)] lehthanis:
Yup, here it is. http://xdaforums.com/showthread.php?p=68306013

Are you going to see if it works for m9?
[Verizon HTC One (M9)] thicklizard:
No its firmware. I don't think this method would help the m9. Basically it's just a firmware update zip. If you are on the latest firmware it is irrelevant. Basically it's flashing the GSM version of the adsp. I don't think it will help because there isn't a device variant that actually has good audio on aosp rom. Just my opinion and I could very well be wrong.
[Verizon HTC One (M9)] lehthanis:
Well the adsp flashed on cm on my m8 seemed to work great. I'm just wondering if there's an m9 equivalent?
[Verizon HTC One (M9)] weinberk:
I'm (sadly) often in a 3G only area and see 3107 as the carrier on the lock screen. I know this was discussed back in March (And was supposed to be fixed), but I still see 3107, not Verizon. Purely cosmetic.
[Verizon HTC One (M9)] BungeBash:
Using the latest official cm13 build, bluetooth does not detect my car UConnect bluetooth so I am unable to pair. This is my first install of CM on this device so maybe it's never worked? But that would be a huge loss...
[Verizon HTC One (M9)] lehthanis:
Anyone have any more thoughts on improving speaker quality above 50% volume in cm? The boomsound adsp for the m8 from viper worked on the m8. I'd like to try the same for the m9 if possible.
[Verizon HTC One (M9)] mister.robot:
am I the only one that notices that the only rom that utilizes the selfie cam properly is stock? I tried a few roms that made my selfie cam take pics like a crappy galaxy S5. but when i use a stock rom it takes the crisp pictures i love
[Verizon HTC One (M9)] BungeBash:
It might've been said before but I can't use voice and data simultaneous after installing this on my Verizon HTC M9. I tried selecting different APNs and it doesn't work. HD Calling was and still is enabled on my account.
[Verizon HTC One (M9)] MARKREIF:
Has anyone experienced GPS issues and found a fix? None of my navigation apps are functioning properly.
[Verizon HTC One (M9)] MARKREIF:
I came from Viper 5.0 to the latest build. No GPS. Best to flash and older build? Can it be a dirty flash?
[Verizon HTC One (M9)] Flyhalf205:
HD Calling on CM on HTC devices does not work.

I had this issue when I ran the RUU. You need to flash back to a stock rom. Set location mode to high accuracy. Turn off WiFi. Open up Maps and get a lock
[Verizon HTC One (M9)] BungeBash:
So I'm assuming there is a fix on the horizon?
[Verizon HTC One (M9)] MARKREIF:
What's the difference between the initial flash from Viper 5.0 and reflashing a "stock" ROM note. Seems redundant
[Verizon HTC One (M9)] Flyhalf205:
Hopefully. I've been trying to get it to work but with no luck. Now focus has switched over to cm-14..
[Verizon HTC One (M9)] Flyhalf205:
You could call it redundant but it has been proven to work on a stock rom. It may very well work on Viper but no one has reported its success before.
[Verizon HTC One (M9)] MARKREIF:
OK so to confirm....I do a clean flash of a rooted stock ROM, lock a nav app to the GPS and then wipe all and follow with a clean flash of CM. Correct?
[Verizon HTC One (M9)] Flyhalf205:
yes... another way is If you already have stuff setup on a CM rom. You can backup your CM. wipe. flash stock rom. turn on high accuracy and get a lock on maps with WiFi off. and then restore your backup.
[Verizon HTC One (M9)] MARKREIF:
Ok thanks
[Verizon HTC One (M9)] MARKREIF:
Worked like a charm thanks again
[Verizon HTC One (M9)] MARKREIF:
Deleted
[Verizon HTC One (M9)] Flyhalf205:
If anyone still uses this. We haven't had a nightly in a while so I built this one here for catch up on all the missing commits. I have included the fix for MTP.

https://www.androidfilehost.com/?fid=385035244224408341
[Verizon HTC One (M9)] Dayliter:
Working Great! Thanks

Working Great! Thanks been using is fast and smooth
[Verizon HTC One (M9)] tst1212:
Thanks, works well.

So would I be correct in assuming this is the end to the Verizon m9. Are there any plans to move this to LineageOS?
[Verizon HTC One (M9)] Flyhalf205:
I can build a Lineage 13.0 but it will be no different than what is in the OP. Here is the list of commits that are different in my custom build with the MTP fix... https://review.lineageos.org/#/q/topic:rebrand-13

Right now we can't move forward to 14.1 because camera is completely broken. Flashlight doesn't even work.

I will however add himawl back to the weekly build schedule for lineage-13. And I am still learning on how to fix advanced calling.
[Verizon HTC One (M9)] Flyhalf205:
Updated the OP with latest unofficial lineageos build.
[Verizon HTC One (M9)] lithophone:
Is it safe to dirty flash the new LineageOS ROM if I'm currently on your previous unofficial CM update from 12/28?
[Verizon HTC One (M9)] Flyhalf205:
Yes it is safe.. There is no code changes in the build. Just switching out the rom name.
[Verizon HTC One (M9)] Be6i4:
Which Recovery is recommended for this ROM? Is TWRP ok to use?
[Verizon HTC One (M9)] Flyhalf205:
The latest TWRP.
[Verizon HTC One (M9)] Dayliter:
I Love this Rom except my camera force closes after a photo or too

everything else is working GREAT! ill keep my eye out for the Fix --Thanks

for the Good work.
[Verizon HTC One (M9)] Flyhalf205:
Interesting. I have not had any issues with camera crashing. Is this after a fresh install or a continue nightly?
[Verizon HTC One (M9)] weinberk:
[MENTION=3082717]Flyhalf205[/MENTION]-

https://www.androidfilehost.com/?w=files&flid=137301&sort_by=date&sort_dir=DESC shows a couple CM14 builds from the end of 2016. I've not tried yet. Questions:

1) Everything I've read seems to suggest that Lineage will be MM based. Is there a play (which I think translates into "do you have a plan") to give us the gift of Nugat?

2) If I give the CM14 roms a go, what's the recommended firmware?

3) Mostly unrelated - I like my device encrypted. I'm just afraid of leaving somewhere like a cab and by the time I wipe the phone (if that even works) someone who has found it causes a mess. I can encrypt with CM13, but TWRP won't decrypt yet. Apparently, it only works with Sense (??). Do you have experience with this? Coordinate with [MENTION=2605798]nkk71[/MENTION]??

Thanks for all you do for us.
[Verizon HTC One (M9)] Flyhalf205:
We are still on 13.0 until HTC decides to release the new kernel source that may help us upgrade to 14.1. 14.1 as of right now does not have working camera or camcorder. And even if you encrypt your stuff. Anyone can get to your information in TWRP...
[Verizon HTC One (M9)] weinberk:
Fingers crossed on HTC's release of the kernel source then.

I'm not sure what you mean about encryption and TWRP giving anyone access. If data like email, facebook passwords, contacts, etc is saved in internal storage (not the external sd card) and the device is encrypted, how would someone access the UNencrypted data? Sure, android devices don't use a TPM chip or anything, but wouldn't decryption require brute forcing the 4 (or larger) digit pin? Encrypted storage can't be mounted in TWRP as far as I know. Hope it doesn't come across like I'm disputing what you're saying, I'm just asking for clarification.

I've always asked for TWRP to enforce a policy that would wipe a device if more than X attempts are made. Does that stop someone from doing an offline attack? Nope, but it's better than nothing. - sorry to digress.

I'm so thankful that you've taken the initiative to keep the cm legacy alive for our phones. We'd be lost without you. Any idea on when we'll see official weeklies (nightlies?) and an updater?
[Verizon HTC One (M9)] Dayliter:
lineage-13.0-20170115-UNOFFICIAL-himawl.zip --i did a dirty flash from the cm-13 ---but if its just me ill try clean and see what happens -Thanks
[Verizon HTC One (M9)] Be6i4:
Thanks man. It's weird, but I couldn't make anything. I discovered from a lot of posts here, that Verizon M9 running 6.0 can't be unlocked without java card. It's weird, because phone is S-OFF and you can't unlock the bootloader. :(

Thanks again!!
[Verizon HTC One (M9)] Flyhalf205:
New build out. Just a few upstream fixes.
[Verizon HTC One (M9)] redwolves:
I get "No Mirrors found." on AFH.

Never mind. I got it.
[Verizon HTC One (M9)] Flyhalf205:
New build posted. Updated to January security patch level.
[Verizon HTC One (M9)] Gmoney1988:
I am assuming this ROM doesn't have advanced calling/wifi calling? And I lose LTE when I make a call? Awesome ROM BTW I love it. Just saw your previous post about advanced calling hope there is a fix soon.
[Verizon HTC One (M9)] weinberk:
Correct assumption. CM12 and CM13 didn't have the advanced calling / wifi calling (no VoLTE) either.

The old Verizon M8 had the ability to make calls and use LTE data at the same time, but that's because (as it was described to me) the m8 that phone had 2 radios. Calls would go over 1xRTT and the lte radio would stay working for data. I miss that...
[Verizon HTC One (M9)] blconway:
Also experiencing camera crash when switched to front facing camera and video. Have to quickly change back to either rear facing or camera mode before app crashes in order to use it. May be an app setting, will investigate further and respond back if I find anything. On 2-3-17 build.
[Verizon HTC One (M9)] lj50036:
Drive ? Sunshine can unlock the bootloader and s-offf HTC M9's now ???

Going to give this rom a go, it has to be better the stock right. :D

Thx Josh
[Verizon HTC One (M9)] blconway:
I could be wrong, but I felt like I read only the java card or xtc2clip can unlock Verizon version.

Edit: A quick google search confirms I am probably wrong.
[Verizon HTC One (M9)] lj50036:
Yep, if you look here, version 3.3 added support for himawl.. :)

http://theroot.ninja/download.html

Thx Josh
[Verizon HTC One (M9)] SWEVEX:
Music can't be adjusted by EQ
[Verizon HTC One (M9)] weinberk:
March 3 update, device encryption broken?

[MENTION=3082717]Flyhalf205[/MENTION],

Thanks for your continued work in support of our beloved Verizon m9's.

Did something change with device encryption in your March 3 build? I've hit a pretty major snag, that makes this version unusable. Coming from the Feb 3 version, working quite well on an encrypted phone, I updated to the March 3 Lineage release that you built. The update seemed to work - I'm using TWRP 3.1 (which now supports encryption btw). Upon boot, it does just 2 or 3 preparing xxxx" (or maybe it's "starting xxx") and then prompts for the pin. No matter how many times I try, it says its incorrect and I obviously can't get past that point. Fortunately, reflashing the Feb 3 build works, and I'm once again able to access the installation.

The changelog doesn't show anything that I can determine to be useful.

Hoping you can help.

Thanks again
[Verizon HTC One (M9)] Flyhalf205:
Nothing to my knowledge has changed. I've always had bad luck with encrypting and having to start over on my phone.
[Verizon HTC One (M9)] weinberk:
I've never had a problem before with CM13. Even with TWRP being previously unable to decrypt data it was still able to update the rom.

It seems like (and please don't hesitate to correct me if I'm off base) that if going from your Feb release to the March release won't accept the pin, but going back to Feb works that there's either:

1) Something wrong with the March built or

2) Something wrong with the Feb or previous build that allows encryption to work but in a way that was broken and was then fixed in the month between the 2 builds.

Any suggestions on how we can get to the bottom of this. I've finally got my phone in a sweet spot and I'd hate to start over, but I don't really want to stay on an older ROM.

I'm going to try backing up data in TWRP then flashing March, but I don't know if that'll work.

Thanks
[Verizon HTC One (M9)] weinberk:
Also, totally nitpicky, but for years, if CM/Lineage is on a Verizon 3G network in most areas that I've seen it, it shows "3107" at the network name instead of "Verizon 3G" or "Verizon Wireless." Years ago it was fixed, but I don't know how or where. Is that something that you can look into [MENTION=3082717]Flyhalf205[/MENTION]? Thanks
[Verizon HTC One (M9)] weinberk:
I decided to start fresh. Wiped everything, installed one of the stock(ish) roms from [MENTION=1331268]santod040[/MENTION]. All was fine including encryption, and GPS started working again (common error that I get about once every 3-4 months and temporarily installing stock fixes it).

With TWRP 3.1.0 installed, I then installed your March 3 Lineage build. It installed fine. GPS works great. Got it configured and then tried to encrypt. It shows the green android guy on the black background at reboot for about 2 seconds, then the Lineage boot animation for a short while, then it restarts. It then boots, seemingly normally, as if I didn't tell it to encrypt.

I tried the same process with other versions of TWRP, including the one that was originally used to encrypt my previous install of your February 3 LineageOS build. No luck, same problems.

I then flashed the Feb 3 build again. I tried encrypting again, and it seemed to worked just fine. Android guy flashes for a second or two, lineageos boot animation, starting apps, then green android guy and encrypting (NOT an hour, just a minute or two). System restarts and prompts me for decryption pin as expected.

Upgrading that to March 3, doesn't accept the pin. It boots, seemingly normally, prompts for the pin, but keeps telling me that it is wrong.

I restarted into recovery, entered the pin (more than 4 digits fyi) flashed Feb 3 over the March 3 installation that won't accept the pin, and poof, I'm back to an encrypted working phone, just with the older rom.

I don't know enough to say for sure, but it sure seems like a bug with your March 3 LineageOS build, either with something that changed in code or with the build itself.

So now what? No encryption unfortunately just isn't an option for me :(

Thanks
[Verizon HTC One (M9)] Flyhalf205:
I uploaded a new rom with February security patch level. I'll check the encryption on that in a few minutes.
[Verizon HTC One (M9)] Flyhalf205:
No idea to be honest. I use to get that a few months ago but I can't reproduce the issue and I've traveled a lot over the past few months.

We have about 3 guys looking into camera issue on lineage 14.1 So hopefully soon that can get resolved but fix these weird issues.
[Verizon HTC One (M9)] weinberk:
I wonder if it's just >some< Verizon 3g towers - or you're travelling to areas that have been upgraded to LTE. I see it less and less and less, but consistently in a few areas around me that I know are fringe 3G areas. Totally just aesthetics.

FYI, I'm in no rush for 14.1 - not until xposed comes out for it.
[Verizon HTC One (M9)] Flyhalf205:
[MENTION=360274]weinberk[/MENTION]

I can't get any build to encrypt. Just reboots as soon as I hit encrypt phone.