yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] bgcngm:
Thank you for your donation! I was very happy when I fixed the incall audio problem and can only think why haven't I tried to bring CM into this phone before. Anyway, it's here and let Android M come. :)

This change here is yet to be merged and could be the solution for your problem. How experienced are you with adb? Are you able to push one file to the phone in order to make some tests? If so, please grab this file, save to your computer and push it from recovery:

adb shell mount system
adb push android.hardware.sensor.stepcounter.xml /system/etc/permissions/
adb reboot

Test and let me know if it works.

No idea, but you seem to have m8, not m8dug. So, wrong thread?
[One (M8) Android Development] simonvfr:
Thanks for the suggestion. I pushed the file successfully:

C:\adb>adb shell mount system

C:\adb>adb push android.hardware.sensor.stepcounter.xml /system/etc/permissions/
90 KB/s (830 bytes in 0.008s)

C:\adb>adb reboot

C:\adb>

But it's not a success. Fitbit now doesn't even recognise the M8 as a device.

On the other hand, another pedometer app I am testing (WalkLogger) now offers an option to use the "hardware step counter". As it didn't offer this option before, I guess this shows the file push worked! Unfortunately, with this option selected, WalkLogger no longer registers any steps. Switching the option off makes it work again.

So, I guess I conclude that the M8 doesn't have a hardware step counter? And that Fitbit might have been using the accelerometer, but using some code in the HTC rom that is not replicated in CM?

Happy to try any other ideas :)

Can I check - the next time I flash a nightly, will it overwrite the permissions and delete the stepcounter?
[One (M8) Android Development] bgcngm:
First of all, thank you for testing that. As far as it concerns to Fitbit, I guess you are right and maybe HTC has some proprietary code to deal with it. Let's see if someone comes up with a solution for that.

I think that on the next nightly, that permission will be removed. Otherwise, if you notice it stays there, just delete the file using a file manager with root access.
[One (M8) Android Development] consuldore:
Just had another service dropout.

As you can see in the screenshot.

This happens every other day.

Is there a log file I can look for to get an idea what's going wrong?
[One (M8) Android Development] bgcngm:
You forgot to attach the screenshot. On the moment you see that connection was dropped you can take a generic log as well as radio log:

adb logcat > log.txt
adb logcat -b radio > radio_log.txt

There must be something special about maybe the networks you are connected. As I said, I'm on the same firmware version and never had such issue. Even to add to that, I'm actually away on a business trip, so I'm roaming and everything is working perfectly.

Did you make a clean install when the first nightly came out? That's highly recommended, to erase the data from alpha and beta releases.
[One (M8) Android Development] bgcngm:
Actually, many sites do point out that m8 has a step counter, part of its smart sensor hub (here for example). By the way, did you try Google Fit already?
[One (M8) Android Development] simonvfr:
Interesting! Yes, tried Google Fit - says it cannot detect activity with this device.

I am currently trying WalkLogger, which is highly rated in the play store. It seems to be doing pretty much as well as Fitbit did. Certainly better than other step counters I have tried on the M8. But as I said, it reports that there is no usable hardware counter available, even with the permissions pushed.
[One (M8) Android Development] Pelly1982:
Hi,

I recently installed the official 12.0 release of this rom on my M8 and was wondering if it is worth while jumping over to the 12.1 nightly? Are there many major improvements from 12.0 to 12.1?

Thanks
[One (M8) Android Development] simonvfr:
I suspect you are asking in the wrong forum - this is for the dual SIM version of the M8, and there never was a 12.0 for the dual SIM.
[One (M8) Android Development] Pelly1982:
Yes, I misread the title. Thanks.
[One (M8) Android Development] simonvfr:
Having just flashed 2 Sep nightly, I can confirm that permission file is gone - presumably the whole folder is overwritten.

Further checking on specs seems to confirm that the M8 doesn't have a specific stepcounter. It has a multi-axis accelerometer in the sensor hub, and the accelerometer permission enables access to this. I suspect that Fitbit merely amended their app to include reading the internal sensor, but only with the M8. They would not want to do this normally, as it clearly would undermine the market for their own devices, the simpler of which are little more than accelerometers in a case with some memory and bluetooth. There must be something in the stock ROM that identifies the phone to the app and enables its ability to work without a separate Fitbit device.

Since losing the Fitbit functionality, I have been messing with a range of stepcounter apps. The better ones seem to function exactly as the Fitbit app (with different interfaces of course, but with the same data).

So, apart from the loss of continuity with the data stored in my Fitbit account over the last 12 months, I am no worse off.

And, of course, I have the pleasure of using CM12.1 ! :)
[One (M8) Android Development] DvDongeren:
Does cm12.1 has mirrorlink? I can't find a solid answer anywhere. Searching settings does not come up with any result so i'm guessing not?
[One (M8) Android Development] consuldore:
And it happened again.

So this time I was able to grab a log from the radio.

But seriously I have no idea what i'm looking at. :(

SIM 1 is an German o2 card

SIM 2 is an Australian Telstra card
[One (M8) Android Development] k.electron:
can i install this on a verizon variant with s-off? getting tired of HTC not updating stuff.

are there any gotchas to installing it on verizon?
[One (M8) Android Development] bgcngm:
This is for dual SIM only, read first post carefully.
[One (M8) Android Development] k.electron:
my bad. sorry about that. is there a cm thread for the regular m8?
[One (M8) Android Development] bgcngm:
Don't know. Use forum search.
[One (M8) Android Development] simonvfr:
This is the forum for all single SIM M8 versions and CM12.1: http://xdaforums.com/htc-one-m8/orig-development/rom-cyanogenmod-12-1-nightlies-htc-one-t3087480

Given the repeated postings by people who are looking for single SIM info, perhaps worth having a note in the OP? [MENTION=455439]bgcngm[/MENTION]
[One (M8) Android Development] bgcngm:
Thread title updated to make it more clear that this is only M8 Dual SIM related.
[One (M8) Android Development] simonvfr:
HTC Camera and gallery

I've not been very impressed with the CM camera, and having tried out some of my other favourites, I thought of trying the HTC stock camera and gallery. I was going to restore from one of my backups, then just on chance I tried installing the two apps from the Play Store.

Surprisingly, they both installed and work!

I'm very pleased, with only one problem - I can't get the HTC Camera to save to external SD. This used to work fine with the Sense ROM, and I'm familiar with how to set it up - but no storage option appears in the apps General Settings. Any thoughts?
[One (M8) Android Development] Captain_Throwback:
Only way that'll work is with Xposed and the Sensify module.
[One (M8) Android Development] simonvfr:
Thanks very much for this. As the British saying goes, seems like a sledgehammer to crack a nut (not having found need for xposed since leaving sense and installing CM12.1), but I've done it.

After the necessary reboots etc, and setting sdcard address in Sensify to /storage/sdcard1 the Camera app now obviously has permission to use an SDcard, but reports that I haven't got one installed.

Other apps are having no problem accessing the sdcard. Sorry if I am missing something simple, but any further help would be much appreciated!
[One (M8) Android Development] Captain_Throwback:
The HTC Camera app has to be installed in system/priv-app for it to work fully.
[One (M8) Android Development] simonvfr:
OK . . . . . But how? This doesn't seem to be documented in the thread for Sensify.

In danger of going too far off topic for this thread, but if there's a simple explanation, I'd appreciate it
[One (M8) Android Development] Captain_Throwback:
Copy/paste should work fine.
[One (M8) Android Development] bgcngm:
I haven't forgot about you. The plan is to add some changes to the device tree and then build a release for you to test during about one week. If I am right, it should be able to solve your problem.
[One (M8) Android Development] simonvfr:
Strangely I have had both SIM disconnect this afternoon. In area of known good signal, and reconnect on reboot. Couldn't get a log as I was driving. On latest nightly. Happy to help with testing if wanted.
[One (M8) Android Development] bgcngm:
Okay, guys... please try the attached boot image. Flash it through fastboot mode, leave that boot image for about a week (either don't apply any OTA update or flash this once again every time you apply the OTA update).

The command to flash through recovery mode is:

fastboot flash boot boot.img

Basically, it includes some additional RIL-related build properties found on stock that weren't before merged to CM. I am also testing, just checking if it doesn't break anything else.
[One (M8) Android Development] simonvfr:
Flashed OK and rebooted

C:\adb>adb reboot bootloader

C:\adb>fastboot flash boot boot.img
target reported max download size of 1826418688 bytes
sending 'boot' (10086 KB)...
OKAY [ 1.000s]
writing 'boot'...
OKAY [ 0.488s]
finished. total time: 1.496s

C:\adb>

On reboot, phone displayed toast message which VoiceNotify read as "Phone, restricted access changed". Then very quickly (felt much quicker than before) logged on to network with both SIMs. Phone working correctly, it seems.

I'll report (and try to log) any network errors or other issues.
[One (M8) Android Development] bgcngm:
I was not looking to the phone during the reboot after I flash the boot image, but I guess that the toast you mention should have also appeared on mine. Did a second reboot just to see if it appeared again, but it does not. I also have a felling that network registration took less time, but could be a placebo effect.
[One (M8) Android Development] consuldore:
OK, just flashed the latest build and this boot.img. I'll report back in a few days.
[One (M8) Android Development] simonvfr:
[MENTION=455439]bgcngm[/MENTION] OK, first network failure. SIM1 has lost data connection and is stuck. SIM1 status shows "Mobile network state Connecting".

Switching on/off airplane mode does not help. Neither SIM connects.

After reboot, still no data connection (both SIMs showing exclamation mark in status bar)

Finally, turn mobile data off/on and connectivity is restored on both SIMs.

Of course problem could be coincidental, I have no way of linking it to the flashed boot.img . . . .

Debug log at OneDrive. Is this the right sort of log?
[One (M8) Android Development] simonvfr:
Now second network failure. This one just like the original which prompted me to install the boot.img patch attempt.

Screen grab of SIM1 status attached

Bug report here (again, not sure this is right sort of bug report - it was taken with CM Developer options)

While in the crashed state, touching the mobile data quick setting tile takes me to the WiFi data usage, rather than the mobile data usage as normal. Long press does take me to SIM card settings.

Trying to make phone call gives error "Mobile Network not available"

Switching on/off Aeroplane mode does not lead to connection.

WiFi mode works as normal.

The only way to get network connectivity back seems to be a reboot.

Beginning to think a week's testing not needed - there's a problem which is not solved.

Anything more I can do to provide info? I'm going to flash the 10 Sep nightly when it's available, because I see a number of M8 specific changes in 9/10 Sep builds, but I am happy to reapply the boot.img if wanted.
[One (M8) Android Development] bgcngm:
Well, I can get anything from that log. But I agree, we should update to the next nightly. I'm using an old one along with the boot image compiled by myself and experienced two random reboots (one yesterday and one today), but no network problem.
[One (M8) Android Development] bgcngm:
The new nighly is out now, but the download page has changed to: https://download.cyanogenmod.org/?device=m8d. The reason is that device codename was changed from m8dug to m8d. Had to become a more generic name because the ROM now supports both dual SIM variants: m8dug and m8dwg. :)

EDIT: Important to mention that the phone will not find new OTA updates for those that are still running a m8dug nighly. The update package will have to be downloaded from the site and flashed manually from recovery.
[One (M8) Android Development] simonvfr:
New nightly seems broken! After manual flash, no SIM detected . . . . and only showing one SIM icon :(

I've reverted to 7 SEP build and all is normal. Guess I'll wait for a new changed build . . . . .
[One (M8) Android Development] bgcngm:
It seems we have flashed it at the same time. I had to revert to the 9 Sep. build. Please let me check what went wrong there, after I am back home.
[One (M8) Android Development] simonvfr:
Thanks. I'll wait for further info from you before flashing any new build
[One (M8) Android Development] bgcngm:
I have found the problem and already submitted the fix to be merged. Probably next nightly will include the fix and everything will be back to normal. I have it already working. ;)
[One (M8) Android Development] simonvfr:
From the change log it looks like it didn't make it to the 12/9 nightly? Don't want to make large download and flash till I am confident the fix is there . . . . . .
[One (M8) Android Development] bgcngm:
The fix is there, but you can't notice. You can download and install it.
[One (M8) Android Development] simonvfr:
Thanks - I can confirm that 12 Sep works fine again
[One (M8) Android Development] genderblurr:
This will work with Sprint right? Also is it sense or GPE based?
[One (M8) Android Development] bgcngm:
Seriously? This is CyanogenMod and only for M8 Dual SIM variants.
[One (M8) Android Development] aLDoom:
Hello. I have a question regarding telephony when there is no WIFI.

I have a Samsung S5 Dual Sim phone and when I tried it (CM12.1), I had one major issue with the telephony/data service. When no WiFi is available and 3G/LTE is on (primary SIM), my secondary SIM is unable to receive or place phone calls. The primary sim functions normally (data/voice). When data is disabled, the 2nd SIM works. When WIFI is connected, the 2nd line can receive and place calls. Keep in mind, the signal bars on both SIMS are always on.

Does your M8D have the same issue?

Thanks in advance.
[One (M8) Android Development] genderblurr:
Well OP says all variants so I wanted to be sure. There have been once that didn't need a GPE conversion in the past.
[One (M8) Android Development] bgcngm:
Not at all and I can give you my example. I use a data SIM only in slot 1 and another SIM only for voice calls on slot 2. The SIM on slot 2 can receive / place calls anytime, while on WiFi or on mobile data (enabled on slot 1).

Sorry, that has just been corrected. I was a leftover from my last edit of the OP. By the way, you are looking for this and I can tell you it works with Sprint.
[One (M8) Android Development] simonvfr:
[MENTION=455439]bgcngm[/MENTION] Although the download link in the OP is correct and works, I see that the main official download page (https://download.cyanogenmod.org/) still has index link on left to the old version (m8dug)
[One (M8) Android Development] bgcngm:
Yeah, I know that. I have reported and am still waiting for someone to fix it. The builds for m8d are appearing at the bottom of the page.
[One (M8) Android Development] L_E:
Thanks for that important info, was wondering, why nighlys stopped at 09.09... BTW thanks again for your work!
[One (M8) Android Development] bgcngm:
Any update from those that were having random network disconnection issues?
[One (M8) Android Development] simonvfr:
I did not reflash the boot.img after the 12 Sep nightly. And I have had no recurrence of the network disconnection by both sims that could only be solved by reboot.

Coincidence? Who knows. Problem is that this problem seemed oddly erratic and unpredictable. For me, it's gone away for now.

Would you want me to flash the boot.img again? Or should we just wait and see if there's any recurrence?
[One (M8) Android Development] consuldore:
Since I flashed the m8d nightly 20150912 the problem seems to be gone. But it's to soon to be certain. With the older versions the dropouts happened sometimes twice a day or once a week.

I'll report back if it's happens again or it not in a few day's.

Thanks again for all the hard work.
[One (M8) Android Development] consuldore:
Speaking of the devil ...

Just had my first connection error.

Same as before, only a reboot could solve it.
[One (M8) Android Development] bgcngm:
Sadly, I have no idea what it could be. :( I may have to revisit stock RIL-related properties to see if anything could be missing.
[One (M8) Android Development] bgcngm:
By the way, most should already know, but you can see m8d nigthlies changelog here. :)
[One (M8) Android Development] Simply_S:
Encryption and backup

Hi,

*Very* tempted to try this but a couple of questions before taking the plunge :

- My GSM has to be encrypted (work restrictions) but I read conflicting information about whether or not this is possible with CM 12.1. Can standard Android encryption be applied and if so what precautions should be taken ?

- Obviously wiping the data is a big step and always worried that I will have forgotten to backup that one song/photo etc. Titanium backup seems to be the most popular but a proper T*backup requires root and most rooting procedures that I have read send you down the TWRP road which (unless I am thoroughly confused) mean you have already S-OFFed and thus lost data

Can one of you please put my mind to rest and point me in the right direction for answers ?

TIA
[One (M8) Android Development] bgcngm:
Well, in terms of encryption you are good to go. The stock HTC ROM's, based on Sense UI, have a special HTC encryption. In case of CM, it uses standard Android encryption. I can tell you I have the same restrictions at work and phone storage has to be encrypted. No problem with that.

As far as it concerns to data wiping, that is something that you really can't avoid. You can backup all your photos/music or whatever you have in the internal storage. Easily connect to the computer, copy all contents from the internal storage to the computer to later put back on the phone. In terms of application data, I advise you not to backup in case of system applications. You can use Titanium Backup (needs root) for example to backup some games and third-party apps.

I see your concerns about turning S-OFF and loosing data if you eventually unlock bootloader through the official HTC method. However, and as far as I know, actually you can only use SunShine S-OFF, which does not wipe any data.
[One (M8) Android Development] Simply_S:
Thanks for the reply.

Reassured about encryption and the backup, but your reply (and indeed your first post) seem to indicate that S-OFF isn't a requirement. The Cyanogenmod wiki gives :

Unlock + S-OFF + Install TWRP + Install CM + install Gapps

Whereas you would seem to indicate that the S-OFF step can be skipped

Is that right ?

---------- Post added at 03:58 PM ---------- Previous post was at 03:55 PM ----------

P.S. And should I remove encryption before installing (which will wipe data anyway :()
[One (M8) Android Development] bgcngm:
Ahhhh, just realized that such information on wiki needs an update because it was an integral copy of m8 wiki.

Nevertheless, you are confused with the Unlock / S-OFF part of the wiki. You can simply unlock bootloader via official HTC-Dev method and that is fine for flashing recovery and installing CM afterwards. S-OFF is a step forward if you want for example to downgrade firmware at any time, but at the same time allows you to unlock bootloader. Personally, I would recommend to do it, even if it was just for unlocking bootloader without wiping data right away.
[One (M8) Android Development] bgcngm:
Let me clarify once again: you must wipe data in any case, before installing CM. Once you do that from TWRP recovery, data partition will be formatted and encryption (in this case, HTC encryption) will be removed. Then you can encrypt storage again after CM loads.

The suggestion regarding turning S-OFF using SunShine S-OFF was just for you to keep userdata, be able to flash TWRP recovery, root and install Titanium Backup to make any backup.
[One (M8) Android Development] dohtune:
[MENTION=1253094]bgn[/MENTION]cgn I'm new to this thread but I've been following your work and want say a big thank you for all the work done. I installed the nightly for 150915 and I've been experiencing network disconnections within 10 minutes of reboot. Reading through the thread, I understand this is a known issue. Have you had any luck with nailing this? How can I be of help in testing any possible fixes?
[One (M8) Android Development] bgcngm:
Can you please confirm your baseband version?
[One (M8) Android Development] dohtune:
My baseband version is 1.24.30336021.13G_30.69.336021.00_F
[One (M8) Android Development] Simply_S:
Quick update.

Took the plunge and with nightly 20/09/15 and followed the excellent instructions and guidance given here. Everything went very smoothly and I am very happy with the result.

A few caveats :

- do *not* take the backup with HTC Sync Manager (as I did :(). As far as I can make out, it cannot connect to CM so it is impossible to restore your data afterwards

- one minor incident after the first flash when the screen started flashing purple. Didn't prevent the mobile from functioning and cleared after a reboot and hasn't come back since

- I have had one GSM network disconnect - both cards - that was also cleared by a reboot. It happened several hours after the upgrade. Both SIM slots showed as "Empty SIM" and the little switch couldn't be moved to activate them. Tried aeroplane mode on/off but that didn't work. Only solution was to reboot. Baseband version is 1.24.30336021.13G_30.69.336021.00_F

ROM is very smooth and battery usage seems very good. These were the two primary issues that I had with the device that encouraged me to flash.

Haven't tried encryption yet but not expecting any issues. FYI, I did not disable encryption before flashing as I has suggested I might, and I haven't yet S-OFFed

Big thanks to [MENTION=1253094]bgn[/MENTION]cgn for all his hard work
[One (M8) Android Development] bgcngm:
Guys, please try this test build a let me know if you still have random network disconnections.
[One (M8) Android Development] simonvfr:
Dowloaded and flashed ok. On reboot, usual boot animation, followed by usual app optimisation, but then stuck on "Android is starting..." and would not progress.

I have had to force shutdown and reboot into recovery. Now reflashing 20150923 nightly . . . .

Happy to retry . . . .

I followed my usual dirty flash routine. Didn't want to factory reset and have to reinstall everything. Was this necessary?
[One (M8) Android Development] dohtune:
I did a clean install and got stuck on "Android is starting" too. Forced shutdown and wiped cache/dalvik, had the same error.
[One (M8) Android Development] bgcngm:
Let me double check. I'll re-upload the build for testing later.
[One (M8) Android Development] bgcngm:
Here it is the new build for testing. It works because I also flashed, despite the fact that I don't have network disconnection issues.