yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Alcolawl:
Yep. Just finished wrestling with this thing. I was on the 1.40 Firmware. Not sure if I should be or not, but after about 10 minutes of playing with this thing I've built a nice list of bugs so far:

Attempting to adjust the brightness level from the settings menu causes settings to crash

No Soft Button Navigation

No Status Bar

Pressing and holding the Power Button causes reboot

Volume Buttons don't work

Hard Reboot when attempting to wake the phone from sleep. (When the screen is off for more than a minute or two, waking the phone using the power button causes a reboot)

Updating to 2.7 Firmware did NOT fix any of these issues

I just want to say that I've been literally checking the forums every day waiting for this release. I'm so excited for this I couldn't resist flashing, even when I knew there'd be a fair amount of bugs. Great work, guys! I'll be updating the list with bugs I find as I go.

In the mean time, I've installed Simple Control from the play store to act as stand-in navigation buttons.

EDIT: I had to go back to a Sense ROM. The reboots when waking the phone were extremely annoying. Hopefully these can be sorted out in short order. Very excited for the future.
[One (M9) Original Android Development] simonbigwave:
+1 , and great effort by OP so far.
[One (M9) Original Android Development] jody04c:
No joy for me with test build
[One (M9) Original Android Development] varun.chitre15:
Hey there,

So, we did a bit of investigation on the issues reported here. It turns out this issue has been present since a long time, the thing is it shows it's face only when a clean install is performed. As we don't wipe our devices for every new build we make during our development process it didn't come to our attention until now.

We are working on finding out the root cause and will take time.

But

, I have found a workaround to this which will let you install and use CM just fine with no issues (except the 'broken' ones )! :)

This has been tested and works perfectly

Here's how to do it.

Steps involved:

1. Wipe /system /cache and factory reset

2. Flash this old June 02 build

3. Boot into system, setup your things.

4. Then flash the latest build (the one you downloaded) given in the OP

without wiping

anything. Just flash it on top.

5. Install gapps and you are good to go.
[One (M9) Original Android Development] jody04c:
Can confirm this works for me!! Nav Bar back as well as arrow keys and FC's in these first few mins are a thing of the past. Excellent so far :)
[One (M9) Original Android Development] gffmac:
Works great following the new instructions, gets very very hot for me. Hopefully thermals can be better more like the official htc rom.
[One (M9) Original Android Development] wlewin:
Hi there. I'm getting video issues on my device. Glitching/banding. Video linked.

https://www.youtube.com/watch?v=tULZTmFEEVY

Happens for a minute or two, and then the phone turns off without warning.

I followed the install instructions RE installing the 6/2 build first, then the beta 1 on top without wipe in order to fix status/nav bar. All that worked fine.
[One (M9) Original Android Development] Alcolawl:
After performing the steps above, everything seems to be working well (besides the broken stuff). However, my phone still reboots after going to sleep. For the passed hour, I've been trying different things to stop this from happening and haven't found anything yet. It seems that the phone is allowed to go to sleep ONCE before crashing. Ex. I'll restart the phone, let it sit for a minute and after 30 seconds the screen will go to sleep. I'll receive a text or something and check it out. After checking my notification, the screen will go to sleep after another 30 seconds of inactivity. If I try to wake the screen again, the phone restarts. I've been able to reproduce this several times. So, it seems you get one shot at letting the phone go to sleep and after that, something severely screws up and the phone essentially crashes.

EDIT: I should note that I faced this bug once before early last month when flashing a new ROM and it was due in part to having a kernel that was built off a different base than I was running. Maybe it has something to do with the fact that the big cores go to sleep when the screen goes off, and re-activate when the screen comes back on? Idk.

Back to a Sense ROM :(
[One (M9) Original Android Development] varun.chitre15:
Let it settle down, it's due to stressing cache generation process which happens on first boot. Not much can be done here from our side (except I can a custom kernel to deal with that ;) )

That's strange, none of us faced that. Get a dmesg and logcat when this happens.

Never had reboots personally.

What kind of reboots you have? Soft reboots or hard one?

See if you can get a pstore?

i.e Get all files from /sys/fs/pstore if any, right after you get a reboot.
[One (M9) Original Android Development] virajxp1:
What is the firmware base requirement to flash? If I flash on the 1.37 base?
[One (M9) Original Android Development] Alcolawl:
Already went back to a Sense ROM so the pstore files are probably gone. I did do some poking around in the filesystem to see if it made any error logs or something. There were 2-3 folders, one of them named something like "fataldevlog" that was chock full of Kmsg files and error reports I guess generated by the kernel. I tried to open them but it was all just garbage. Would those be of any help? The reboots were Hard Reboots by the way. The screen would remain black, then a few seconds later the phone would vibrate and boot back up.

I would absolutely test drive the s**t out of this ROM (and report any a bugs I encountered) if I could just figure out why these reboots are happening.
[One (M9) Original Android Development] iElvis:
What firmware are you on? This sounds exactly like the bug that caused reboots running a 1.40 kernel on 1.32 firmware. It's not clear from the OP which 5.0 base this is built on, so maybe you've got this same conflict going on.
[One (M9) Original Android Development] wlewin:
Left the phone off for prob 6 hours, then booted again. No gliches thus far. Maybe it was a heat thing?

Still having reboots on occasion when attempting to wake from sleep. I got logs for that at least.

logcat attached, that one I know.

dmesg is a new one to me. not sure if that captured the right moments, but it's there
[One (M9) Original Android Development] Alcolawl:
Agreed. Currently running Firmware 2.7.401.1. These reboots also occurred when running 1.40. Only thing I can think of is downgrading to 1.32 Firmware which is something I'm pretty reluctant to do.
[One (M9) Original Android Development] Galaxysm:
Just tried the rom!! It's amazing!! :D I missed having cm on my phone!!
[One (M9) Original Android Development] skulldreamz:
Can you explain what you did and what was so difficult to get the camera working? What relevance does your post have anything to do in this thread let alone this phones thread? Not cool. SMH
[One (M9) Original Android Development] Andrewbud:
It's clearly the result of huffing too much UV adhesive remover ;)
[One (M9) Original Android Development] simonbigwave:
LMAO. Agree.
[One (M9) Original Android Development] blackknightavalon:
What a coincidence! I got camera working on CM12.1 by switching to my Galaxy S5!

If you don't have any progress to add then stop commenting about your downgrade.
[One (M9) Original Android Development] :
"M-muh camera on muh phone which I begged to PURCHASE, werks"

Seriously GTFO with your bull****. You're not the only one on xda who wants the camera working on cm. :o
[One (M9) Original Android Development] dlads:
Seriously though, is there anything that can be used between two devices that are similar in terms of hardware? For the camera i mean
[One (M9) Original Android Development] bacon612:
AOSP/CM12.1 Camera bounty thread. Put your money where your mouth is, *****es...

http://xdaforums.com/one-m9/general/bounty-htc-one-m9-aosp-cm12-1-camera-t3193175
[One (M9) Original Android Development] jody04c:
Just a bit of harmless fun folks. No harm intended. It was refreshing to have a working CM12 with Camera ready as soon as I received my Oneplus 2. It's how things used to be with HTC when GPE Roms where available. I will keep the M9 and keep trying to help where possible to get a working camera with CM a reality.
[One (M9) Original Android Development] yellowsn0w:
How you liking it so far?
[One (M9) Original Android Development] jody04c:
Honestly think it's a very good device (irrespective of cost). The 4 gig of Ram helps with Multitasking and the detuned 810 has no issues with heat on heavy loads. Build is better with alloy frame etc.. The 1080 screen is fine and battery usage is better than my M9. It's just nice to have a nexus type device again free of heavy skins and laboriously slow development. I hear Paranoid Android will have a Rom out shortly which is great news. Camera is massively better than Oneplus One. Only gripe is speaker volume , poor compared to M9 but hey for half the money it's great!!!
[One (M9) Original Android Development] blackknightavalon:
I actually contributed to crowdfunding on both the Ubik Uno and the Saygus V Squared, both of which run plain vanilla, easily-rootable Android 5.1. I've asked the Ubik guys several times if they were going to release source to help out development but I've not received a reply yet.
[One (M9) Original Android Development] calebcabob:
There's a thread dedicated to getting the M9 camera working.

Go HERE AND HELP SUPPORT IT!!

We need more help!
[One (M9) Original Android Development] rSallyx:
Camera is now working sorta, any new updates on the rom?
[One (M9) Original Android Development] throcker:
as you might have read if you know camera is partially working, fix is on his way but unreleased from devs. we have just a "preview"

I think that roms will have a boost just once this fix will come out....

needless to say, development is stuck just like 4.4.4 days, when we were waiting for LP....
[One (M9) Original Android Development] throcker:
what's new in 18 oct build??
[One (M9) Original Android Development] djsubtronic:
It's from the future.
[One (M9) Original Android Development] throcker:
LOOOOOOOL sorry too much work hahaha
[One (M9) Original Android Development] djsubtronic:
The latest build in this thread is from July. You may want to check this thread for updated versions:

http://xdaforums.com/one-m9/orig-development/unofficial-cyanogenmod-12-1-t3214063
[One (M9) Original Android Development] jody04c:
Any word on official Cyanogenmod now that Camera fix has been implemented?
[One (M9) Original Android Development] rc420head:
Rashed is working on getting nightlies going, be patient he's really close

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] Leebert225:
Now that nightlies are up and running http://download.cyanogenmod.com/?device=himaul will there be an official thread created?

Thanks for the awesome work all involved!
[One (M9) Original Android Development] grim489:
There is one.
[One (M9) Original Android Development] ilnessuno4691:
Where can you share the link?
[One (M9) Original Android Development] grim489:
It's on the Android development section. It's one of the top threads. Says official in the title
[One (M9) Original Android Development] varun.chitre15:
This is, here onwards, the official thread.
[One (M9) Original Android Development] djsubtronic:
Unfortunately the latest official nightly still has 100% wakelock even with Bluetooth off.
[One (M9) Original Android Development] djsubtronic:
Also, is anyone having bluetooth issues?
[One (M9) Original Android Development] throcker:
I made the thread to have a talk about the official nightlies provided by cyanogen, since there wasn't any....

I thought this and drsn0w thread was a self-building nightlies project (more or less customized) which could have its own bugs and issued, so I created a separate thread to talk about cm as it comes to us.

as now I really don't know if there is any difference between this thread and the one I started, if is just a double thread we can ask a moderator to delete mine, I don't want anyone to be confused or fight for who has the most official thread haha
[One (M9) Original Android Development] simonbigwave:
I agree we keep this [MENTION=4309448]varun.chitre15[/MENTION] thread as Official and not have any another.
[One (M9) Original Android Development] rodpgfx:
Guys what gapps are we using with this build?

---------- Post added at 06:50 AM ---------- Previous post was at 06:42 AM ----------

Is there no gestures with this build yet? Like draw Circle and V with screen off? The M9 had landscape mode quick camera, will you be able to get that working in CM?
[One (M9) Original Android Development] joekiddo:
http://opengapps.org/

Remember to use ARM64
[One (M9) Original Android Development] throcker:
totally agree, but I don't understand what you mean with official

my thread wasn't moved to general section because of this "official" thread decision, but because it was a thread to talk about official releases, not development (because I don't compile or nothing, I'm no dev, just mod user), and "talk" threads are not allowed in development section

ok, is correct. but since here under "download" we can find only a link to download.cyanogenmod hima section, isn't this just a talk thread like mine? or OP is involved directly in cyanogenmod team and this thread is made to merge code submitted by op?
[One (M9) Original Android Development] simonbigwave:
OP is a dev. suggest you look at the OP's signature is self-explanatory.
[One (M9) Original Android Development] ebautista:
Viber, messenger and skype calls cannot be heard by the other party when using headset.

Running on 2.10.401.1 firmware. International version.
[One (M9) Original Android Development] throcker:
perfect, looks like he is in cm official development. keep this up :)
[One (M9) Original Android Development] LuckyColdJohnson:
This is so awesome.........THANK YOU OP !!!!!
[One (M9) Original Android Development] Andrewbud:
I fixed Bluetooth by flashing chadouming's latest kernel.
[One (M9) Original Android Development] djsubtronic:
Link? I tried the latest one on the thread (in the download section) but that breaks WiFi. Also tried all three at the beta link but they are all constant hard reboots galore.
[One (M9) Original Android Development] rodpgfx:
Guys, will there be gestures added to this ROM eventually?
[One (M9) Original Android Development] Crimsonshadow774:
Disregard this post. Data issues were fixed by changing APN to T-Mobile US LTE IPv6.
[One (M9) Original Android Development] LuckyColdJohnson:
For some reason I'm losing phone signal x when I'm using GPS (Google Maps) Haven't noticed it when at home (not on maps of course) ..........I'm on At&t.....

About to look at my APN stteings

Update....Changed my APN to ATT Phone/phone from pta

will test tomorrow
[One (M9) Original Android Development] Tikerz:
Did you flash 1.3? I tried it and Bluetooth turns on but doesn't detect any signals.
[One (M9) Original Android Development] clever_man:
Kernel 1.3 doesn't fix problem with BT. What version you tried?
[One (M9) Original Android Development] Sedy-Emkill:
For Bluetooth issue:

With root file explorer (Fx File Explorer + root add-on) go into system/etc/firmware with write permissions

In the firmware folder you will find a file named BCM4356A2_* ,rename this file to BCM4354A2_*

That's all.. Please test :)
[One (M9) Original Android Development] clever_man:
It seem to work! Thanks!
[One (M9) Original Android Development] Gawain1986:
My Hero! :D BT now works as well as in Candy ROM
[One (M9) Original Android Development] Tikerz:
How in the world did you figure that out?
[One (M9) Original Android Development] 94tbird:
does anyone know if the nightlies support Sprint?
[One (M9) Original Android Development] rc420head:
From the candy commit? 14 days ago lol

https://github.com/TheMuppers/vendor_htc/commit/4e87930739fe8ab3f616c07d487eab01ede66fa8

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] Aldo101t:
not yet but I think someone is working on that.
[One (M9) Original Android Development] 94tbird:
ok cool thanks!
[One (M9) Original Android Development] Sedy-Emkill:
That's right.

Maybe you should update TheMuppets repo too ...
[One (M9) Original Android Development] rc420head:
Was submitted.... Guess they don't want it

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] throcker:
+1
[One (M9) Original Android Development] Louis118:
Can confirm Bluetooth is broken again with my lg g watch r

Setting it up on the android wear app, it connects but my phone then gets stuck on the connecting screen whilst my watch finishes set up. My phone now is permanently failing to reconnect to my watch.:good:
[One (M9) Original Android Development] dom_mnml:
.....try this..... :eek: have you??
[One (M9) Original Android Development] Rogi1997:
Do anyone elese have problems with usb otg? For me it won't work on 14.11 nightly
[One (M9) Original Android Development] clever_man:
Just'll try to read last posts.
[One (M9) Original Android Development] Tikerz:
I just scored a 59251 on AnTuTu Benchmark. Way higher than I could get on Sense.
[One (M9) Original Android Development] hallstevenson:
What about Verizon ? In case anyone knows....
[One (M9) Original Android Development] Tikerz:
Are you able to pair with anything? I couldn't pair to my car. Something about Bluetooth share force closes and borked it.
[One (M9) Original Android Development] rc420head:
That's because cm doesn't have the kernel commit, try using the kernel from candy

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] djsubtronic:
Using the bluetooth filename fix I was able to pair with my car without issue (stock CM kernel).
[One (M9) Original Android Development] Andrewbud:
It must have been a hallucination.
[One (M9) Original Android Development] Gawain1986:
With the file rename pairing works fine here... I just connected to my laptop no problem.

I did dirty-flash over Candy rom though... Maybe that's something
[One (M9) Original Android Development] Crimsonshadow774:
BT fix worked for me as well. Very much appreciated.
[One (M9) Original Android Development] markkenzy:
Please make this rom comes to Sprint M9.
[One (M9) Original Android Development] djsubtronic:
So far the only workaround for the 100% NFC wakelock is to delete /system/app/NfcNci. Are the devs aware of this bug?
[One (M9) Original Android Development] Rogi1997:
Do anyone else have issues with navbar in landscape mode?

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Original Android Development] computerslayer:
Normal behavior and appearance on my device in landscape mode. Maybe there is an app (or xposed mod) causing the issue for your device.
[One (M9) Original Android Development] Rogi1997:
I never installed xposed or any other apps (with root rights), that can causing this issue.... I just changed the buttons and all worked. Then i went to settings and restored original and it made funny things in landscape mode. I realy don't know why

(I use official 14.11.2015)

Update:

I fixed it by restarting my phone

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Original Android Development] Tikerz:
Why aren't there any builds after 11/14? I thought they were automated?
[One (M9) Original Android Development] djsubtronic:
Builds are failing.
[One (M9) Original Android Development] AusX10:
#### make completed successfully (01:17:39 (hh:mm:ss)) ####

real	77m38.526s

user	1077m39.968s

sys	92m21.093s

Adding build to GetCM

python /opt/jenkins/android/workspace/android/build_env/add_build.py --file /opt/jenkins/android/workspace/android/archive/cm-12.1-20151120-NIGHTLY-himaul.zip --buildprop /opt/jenkins/android/workspace/android/archive/build.prop --buildnumber 135520 --releasetype CM_NIGHTLY

/opt/jenkins/android/workspace/android/archive/core.xml: No such file or directory

Build timed out (after 90 minutes). Marking the build as aborted.

Build was aborted

lost connection

Finished: ABORTED
[One (M9) Original Android Development] Andrewbud:
New build Bork's Bluetooth
[One (M9) Original Android Development] varun.chitre15:
RIL and Audio is broken. Once that's fixed, everyone will have the treat :)
[One (M9) Original Android Development] Andrewbud:
Forgive my ignorance. The HTC A9 Android 6.0 source code has been released. Does that make any difference to M9 development?
[One (M9) Original Android Development] ShotSkydiver:
I don't think we'll see functional builds of 6.0 until HTC releases their Marshmallow update for M9, but I hope I'm wrong because that could be a month off.

So, I got a notification on my phone that there was finally a new nightly built for M9, does it break anything or is it a solid update? I'm kind of scared to update because everything is running great on my phone with the Nov. 14th nightly.
[One (M9) Original Android Development] Andrewbud:
Its fine other than bluetooth. The rename fix works though.
[One (M9) Original Android Development] ShotSkydiver:
So, would it be eventually feasible to port over the HTC features from the M8 GPE ROM (such as BoomSound, dot view cover support, motion gestures, etc.) or is it just too difficult to do? All I miss from the Sense ROM are BoomSound and the screen wake gestures, so that would be pretty great to have.
[One (M9) Original Android Development] DeeZZ_NuuZZ:
boomsound will not work, since m8 boomsound is based ond older libs like SRS etc and m9 boomsound on dolby, which is completely different. dot view cover has changed too, so it won'T work really. motion gesture don't know. maybe same, maybe not, but fore gesture support you need a kernel with that.
[One (M9) Original Android Development] rc420head:
Here's s cm dotcase I pulled from candy5, it works fine on candy5 but I haven't tested it on cm-12.1. Let me know, if it works I'll submit to Gerrit.

https://copy.com/FqvGUSFYiUUGrAXg

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] Snookers:
I haven't been able to get V4A to work. I recall reading a post saying that they're working on getting AudioFX working, but I'm not 100% sure that's what they said.
[One (M9) Original Android Development] Rogi1997:
IR is not working for me

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Original Android Development] vrxj81:
IR and BT not working here.
[One (M9) Original Android Development] Andrewbud:
The fix is a few pages back
[One (M9) Original Android Development] slartyxxx:
IR fix too?
[One (M9) Original Android Development] philicibine:
Bluetooth still borked on today's build ?
[One (M9) Original Android Development] Andrewbud:
All you have to do is rename 1 file to fix it
[One (M9) Original Android Development] philicibine:
Tried that after several flashes. It works for a while but always stops working. With my watch anyway.

Even with the fix it doesn't work for playing music in my car
[One (M9) Original Android Development] faun_h:
Working fine here with my bluetooth headphones

Using the 21/11 build with the kernel from Candy5

---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------

and flash a kernel with the required fix, unless that's been merged
[One (M9) Original Android Development] sghurrie:
Same here. I get "Bluetooth Share has stopped" every couple hours which turns bluetooth off regardless if I'm connected to a device or not.
[One (M9) Original Android Development] rc420head:
Flashing candy5 kernel should fix that

------------------------------------

CandySiX coming soon
[One (M9) Original Android Development] Louis118:
Link to download JUST the kernel?
[One (M9) Original Android Development] stargaterules:
every time i try and install this rom i get "assert failed, hima .verify trustzone......error executing updaterbinary in zip".

any help is appreciated.
[One (M9) Original Android Development] scott7175:
When I flash this on T-Mobile I have no data I'm up to date on everything
[One (M9) Original Android Development] grim489:
Did you try the ipv6 apn?