yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] bgcngm:
Correct, but that is already enabled for m8 and m8d as you can see here. The thing about call recording is that in some countries, this feature is not legally allowed, which could be the case for your country. See the entire commit here and you'll notice that for some MCC's the feature is not enabled. In case of my home country (Portugal), for example, it is disabled.
[One (M8) Android Development] co2-guy:
Thank's for clarifying that for me :)

I actually tried looking in htc_m8-common, but I see that was not the correct place :o

I checked and you are completely right (of course :)), call-recording is accessible from my phone, I just needed to activate it in the call menu.

EDIT: Although there's no sound recorded from the other end... Bummer :)
[One (M8) Android Development] bgcngm:
From none of the SIM cards?
[One (M8) Android Development] kruczjak:
Not working sound during call

Hi!

Does anybody has problem with sound during calls?

When I call to someone I can't hear and second person can't here me.

It happens on both SIM cards...

I'm attaching logcat during call (there are some android.os.DeadObjectException there)
[One (M8) Android Development] bgcngm:
No issues here, but when did it start? From that log I see that you have started a call from SIM which network mode is not LTE/3G (most likely SIM2). Is that correct? The exceptions on the log seem to be related to call recording. Did you enable that feature?
[One (M8) Android Development] co2-guy:
Just tried it from both sims. None of them records incoming audio. With 3rd party app CallRecorder, it records perfectly when I set it to CAF record mode. I have no idea what that means, but maybe someone else does :)
[One (M8) Android Development] kruczjak:
In fact it started long time ago (8.01 nightly worked, but when I've updated it to 14.01 it stopped).

Then I've flashed CM12.1 which works perfectly (I thought that this is only temporary) and tried to flash newest nightly yesterday.

I've tried LTE/3g and 2g. Nothing works. (Logs are from 2G SIM2)

Nope, I didn't enable call recording.

That's quite strange, becouse seconds ago, I've tried to enable it and when playing recording I can only here sound from my microphone. Nothing from second phone.

EDIT:

I've uploaded dmesg, maybe there is an error.
[One (M8) Android Development] bgcngm:
Can someone try the attached boot.img? Checking if it solves BT audio streaming issues based on this finding.

If you don't know what to do with the file, just leave it. For the rest:

fastboot flash boot boot.img

EDIT: File removed. Confirmed to be working.
[One (M8) Android Development] simonvfr:
Will test today and report. I see you're also getting same change tested on single SIM version. Here's hoping!
[One (M8) Android Development] bgcngm:
Yeap, I hope this time it is fixed for good.
[One (M8) Android Development] simonvfr:
Well, I have tried all I can to break it, but still streaming fine. I've switched between various bluetooth receivers, and done all the things that seemed to provoke problems.

I shall continue to test, but it really does seem this time it's fixed. Many thanks of course to [MENTION=7112923]p.a.n[/MENTION] , who provides a convincing reason as to why the problem could have occurred when bluetooth streaming, and to [MENTION=455439]bgcngm[/MENTION] for researching and bringing the solution to our devices!
[One (M8) Android Development] simonvfr:
Still working fine, and this has now gone long past the elapsed time where every CM13 build has given up on bluetooth streaming.

Oddly, it seems that there were fixes for 32-bit overflow in get_monotonic_boottime being applied within CM as long ago as the jellybean branch over 3 years ago - e.g. http://review.cyanogenmod.org/#/c/24856/ which seems to use a slightly simpler expression

I can fully understand how hard it would be to connect this to bluetooth streaming, but I'm surprised that something developed so long ago in AOSP has disappeared from CM13. Was it there in CM12 for our device?

I'm immensely grateful for the fix, which I assume can be included in future builds, just intrigued as to how the problem arose . . . . .
[One (M8) Android Development] bgcngm:
True, the fix was applied to AOSP long ago (almost 4 years, in fact), but was never applied to our kernel. Anyway, I have merged the change already. Thank you for the great feedback and for testing.
[One (M8) Android Development] bgcngm:
Can you double check with latest nightly?
[One (M8) Android Development] co2-guy:
Yes.

Just installed 20160216, wiped cache and tried calls on both sims. Nothing but a little static is recorded. :(
[One (M8) Android Development] bgcngm:
Okay, today or tomorrow I will do some tests and let you know. Probably the audio source is wrongly set for m8.
[One (M8) Android Development] bgcngm:
How do you enable call recording in the first place? I can't find the option.

EDIT: Nevermind, I found the option and got it fixed. Please try: https://mega.nz/#!a1xkGaJI!SWNL791_YelOrVjz8lFzirPbTP8l0LJwEyFuipK4BME
[One (M8) Android Development] bgcngm:
Getting back to your issue... What is the radio firmware version you have on your m8d? Did you clean flash CM13? Please get me the values of props persist.radio.prefer.network and persist.radio.prefer.nw.sub as well as the output of tinymix (requires su) in both cases: call using SIM1 and call using SIM2.
[One (M8) Android Development] co2-guy:
I just tried, and you did fix it :good:

Call recording now works for both sims :)

Now all it needs to be perfect, is to start recording automatic :victory:
[One (M8) Android Development] simonvfr:
17 Feb build - SIM problem

Installed 20160217 build and fails to recognise any SIMs when boot completes. In Settings/About Phone/Status it shows both SIMs as not inserted.

Tried twice, same result.

Back to 20160216 and all is well again. Guess I shall stick with this unless anyone else has succeeded with the build from 17 Feb.
[One (M8) Android Development] JoostA:
I can confirm, no SIMs recognised and no way to circumvent.
[One (M8) Android Development] bgcngm:
Seriously? I don't see any change that could cause it. Also haven't updated to the latest nightly.
[One (M8) Android Development] JoostA:
Running 13.0.20160216-NIGHTLY-md8 does not show this problem. I will try the next nightly when it shows up to see whether the problem disappears spontaneously. I am not a programmer at all, so I have no relevant clue at all as to how to solve this riddle. It could be related to some other program of course (e.g. Xposed installer or something like that) . Anyway: In a certain way it is a problem for me. I need both my SIM's: one is my office phone, the other one is private. I have no other phones to contact people. I'll keep you posted: I don't see many people reporting this problem.
[One (M8) Android Development] simonvfr:
In my case, I can be sure the problem was not caused by anything external like xposed, as I am running a clean installation. I am reassured not to be the only one with the issue!

EDIT To be absolutely clear, 20160216 has no problem. I plan to stick with it for now.
[One (M8) Android Development] bgcngm:
No network issues on latest (today's) nightly.
[One (M8) Android Development] simonvfr:
18 Feb nightly also working fine for me. No repeat of the SIM not found fault which I had with 17 Feb
[One (M8) Android Development] bgcngm:
That was very strange indeed. Well, let's move on.
[One (M8) Android Development] JoostA:
Agreed, solved.
[One (M8) Android Development] co2-guy:
Just to be clear, your fix will be included in the official nightly right? :)
[One (M8) Android Development] bgcngm:
Only once it is merged, but for now it is on hold: http://review.cyanogenmod.org/#/c/133164/. If you want to have call recording working you have to keep with my unofficial build for now.
[One (M8) Android Development] kruczjak:
Yes, clean flash.

Radio version: 1.24.30336021.13G_30.69.336021.00_F

[persist.radio.prefer.network]: [9]

[persist.radio.prefer.nw.sub]: [9]

And in attachments outputs from tinymix during calls :)

(it's on current [19.02.2016] clean flashed nightly)
[One (M8) Android Development] bgcngm:
Something wrong there - SIM1 and SIM2 network modes can't be LTE at the same time.

Please do one more thing. Change SIM1 network mode to 2G, then SIM2 network mode to LTE or 3G. Then go back in the reversed order: SIM2 -> 2G and SIM1 -> LTE. Then try calling again and get me again the values of those props.
[One (M8) Android Development] kruczjak:
LOL :D

It started to work after these changes...

Thanks :)

Values have changed to:

[persist.radio.prefer.network]: [9]

[persist.radio.prefer.nw.sub]: [1]
[One (M8) Android Development] bgcngm:
That was clearly an undefined and invalid state which was causing audio routing not to work properly. That should never happen in the first place, but I'm sure it won't happen again, at least until you wipe your phone again.
[One (M8) Android Development] bgcngm:
Next nightly will include the fix. I have just merged the change.
[One (M8) Android Development] simonvfr:
This set me thinking. Both my SIMs are showing as LTE preferred:

And yet I cannot follow the instructions above, because while SIM1 allows a choice of LTE/3G/2G, for SIM2 there is no 2G option:

If I set SIM1 to 2G, then I can no longer revert it to 3G or LTE (presumably there is, sensibly, a block on setting both SIMs to 3G/LTE). Because I can't set SIM2 to 2G, SIM1 remains stuck on 2G. To overcome this I had to reboot with only SIM1 inserted. I could then set it to LTE, shut down, insert SIM2 and reboot. So, I am back at the original setting with both SIMs set to prefer LTE.

Actual connection is 3G/LTE on SIM1, depending on what is available. SIM2 actually connects on 2G.

As currently I only use SIM1 for data, whether roaming or not, this is not a problem for me. However, it's clearly not "right" :)

Any thoughts?
[One (M8) Android Development] JoostA:
(deleted)
[One (M8) Android Development] bgcngm:
No idea, sorry. What I can tell is that we are still using GPS/QMI/RIL blobs from L. For some reason, RIL is not yet working with M blobs.
[One (M8) Android Development] gazzacbr:
Hi, great work here bringing this to the dual sim and working great on my m8_dugl.

had to double take on the size of the zip (and check the sha 1). only 300mb! stock and maximus were 1.5GB.

both sims are working, my UK EE sim is roaming in slot 1 and my Etisalat is in slot 2

i was going to post here to say that wifi was on but could not connect to the internet, then i saw a hint somewhere that location needs to be on!!!!!! is that compulsory now?

titanium backup warns that SU binary might not be reliable. i tried flashing SuperSU but it boot looped and i had to recover from twrp backup. seems to be working fine as it is anyway.

having got the sd card write access sorted on kitkat it looks like another mess with marshmallow.

es file explorer can write to the card but not much else.

i want to put my iGO and backcountry navigator maps on the external card.

what it the get around for this?

i have xposed and tasker if that's what it takes.

thanks for the hard work.

oh, and does this kernel have otg Ethernet support?
[One (M8) Android Development] gazzacbr:
I have been googling like crazy and cant find an answer to have read write on my storage card.

using as 'internal storage' is not an option.

is there a real solution for this?

otherwise this will be a killer for marshmallow.
[One (M8) Android Development] gazzacbr:
Hi,

nothing happening here? had to unload and go back to lollipop

lack of sd card access was no good
[One (M8) Android Development] JoostA:
Just to mention: it appears cm-13.0.20160319-NIGHTLY has a bug in it preventing SIM 1 from being activated. SIM 2: no problems as far as I can see. For this moment I will revert to cm-13.0.20160318-NIGHTLY that has no problems with both SIMs and await the next nightly

Edit 1: after testing for 2 hours this is what I found out.

Flashing the previous nightly does not solve the problem. The problem persists (which I do not understand anyway, as far as I know there was no problem at all with the previous nightly) .

Anyway it can be solved easily, in both previous and current nightly.

In settings --> SIM cards choose settings SIM card 2. Choose last item (mobile providers) "choose a mobile provider".

Have you phone do a search for a mobile provider and when found check the correct one for your SIM. SIM 2 will than be registered in the mobile network and function normally.

Just to mention: when reading my message carefully you will see that initially I spoke about SIM 1 that was causing trouble, afterwards I spoke about SIM 2. To make things easy I could have changed the message. However: I really am not so sure that I was not right in my observations (my SIMs are from different operators, so it is rather easy to see which one is not functioning properly).

So I leave the inconsistency for now so others can check out whether I was right in my observation or not.

Although the problem can be solved easily I still think this is a bug, as it is impossible to start SIM 2 "on its own" as it used to do. Maybe more people discovered the same problem ?

Edit 2: Problem solved as of cm-13.0-20160323-NIGHTLY (and up)
[One (M8) Android Development] Trailerpark1:
Ps, i postet it in the 3 Threads, because i used evry of these roms.

Hello there,

i unlocked the bootloader, Rooted the device and installet twrp 3.0.0.1.

When i try to flash from my ex SD Card. Alls seems properly ok.

But when i start i will allways boot in unlocked bootloader. 'And in Recovery i see, no Custom Rom is installed.

What can i do?
[One (M8) Android Development] JoostA:
Imho this question has nothing to do with the topic here. Moreover the answer can easily be found here: https://twrp.me/devices/htconem8gsm.html. Search for the words: "Note many devices (...)".
[One (M8) Android Development] JoostA:
Do not install latest nightly cm- 13.0.20160401-NIGHLY-m8d.zip. Some error causes it to display the word "MOD" everywhere on you login screen and throughout your phone's menu. This bugs causes your display not to show numbers to enter you PIN code , just the word "MOD" all over. Upon entering your phone you will see the word mod everywhere, in your apps and in the menus.

This problem can be solved by re-flashing the previous nightly version.

How to do this when you do not see numbers (but just the word "MOD") ?

This is easy. Every number corresponds to letters:

1 = no numbers, =abc 3 =def 4=ghi 5 = jkl 6 = mno 7= pqrs 8=tuv 9=wxyz

You can still see these letters, so you now know the number you have to enter. This is especially important when you shuffle your pin code in your login screen, which is an safety feature that you may (or may not) have enabled. The feature is not available for the SIM pin screen. These screens use the standard screen.

Picturesof a standard phone keyboard of course also available on Google (images)!

After loggin in you can re flash the previous version of Cyanogenmod without problems.
[One (M8) Android Development] bgcngm:
It's not an error. Today's April fools.
[One (M8) Android Development] kazavfr:
Hi, I wanted to make some inquiries.

-is fully functional this rom?

Functions sense camera?

-What is your battery life?

Thank you
[One (M8) Android Development] simonvfr:
April 15 build - broken, don't flash

Beware, this build is broken, and you will enter a loop after flashing.

Seems that some changes to LiveDisplay have caused it. Should be fixed in the next build.

For now I would STRONGLY recommend, do not flash 20160415 build

EDIT This faulty build has been withdrawn and is no longer available for download.
[One (M8) Android Development] bgcngm:
Yeap, general issue affecting almost all CM builds.
[One (M8) Android Development] simonvfr:
17 April nightly is working fine for me
[One (M8) Android Development] simonvfr:
The 20160423 nightly is over 90MB bigger than any of the preceding nightlies. There's been no similar change in the nightly for M8 single SIM. And the changelog at https://www.cmxlog.com/13/m8d/ seems to be down.

I think I shall not install this one till I know why the sudden change in size . . . . . .
[One (M8) Android Development] bgcngm:
That's normal and this change explains why: http://review.cyanogenmod.org/#/c/141635/.
[One (M8) Android Development] bgcngm:
Guys, need your help testing this: https://mega.nz/#!ukwHHCwS!H6O-bJygW9rzOpVjmkBg2TScLB8zlN1F6ECe8mywBQM

It includes the latest M libraries, including GPS/QMI/RIL related ones which were still from L. Thoroughly test GPS and RIL (mobile data, phone calls, network mode switching) and provide feedback. Note that this is important for me to decide to go ahead and submit m8d to the next CM stable release.
[One (M8) Android Development] simonvfr:
Have installed and first tests all ok - gps first fix quick as normal, mobile data and phone calls fine. Haven't tried switching LTE/3g/2g as I still can't get a 2g option to appear for SIM 2.

Anything particular you want trying? Otherwise, I will run it till tomorrow and report.
[One (M8) Android Development] bgcngm:
How's that possible? That was unlocked long ago.
[One (M8) Android Development] simonvfr:
That change never worked for me. SIM 2 settings still offers choice of only LTE (Recommended) and 3G. On the unofficial SIM 2 was actually connecting as GSM. On official SIM 2 normally connects as EDGE.

Worse issue, which has led me to abandon trial and revert to official nightly. I experienced constant downloading, whether on Wi-Fi or mobile. Averaging around 100KB/s. Over an hour more than 100 MB. In data usage, it's recorded as being used by Android OS. Clearly not sustainable! Rebooting changed nothing. Back on official nightly and downloads have ceased.

No other problems noted. Noticed that SE Linux status was permissive on unofficial - assumed there was a reason for this?

Happy to experiment further . . . .
[One (M8) Android Development] bgcngm:
Which options appears for you using this test ROM in SIM1 and SIM2?

Yeah, I also noticed such issue. Phone keeps receiving requests to reset GPS properties and constantly generating traffic. Issue happened before when we tried to update GPS blobs from M (more here).
[One (M8) Android Development] simonvfr:
Same as with official nightly. 3 choices for SIM 1. Two choices for SIM 2 - i.e. LTE and 3G. I know only 2g is possible on SIM 2, and that's all I ever connect as, but the false choices remain as when I reported it ages ago.
[One (M8) Android Development] bgcngm:
That's damn strange. I have all options available: LTE, 3G and GSM. Same as SIM 1. And now it works fine changing network modes.

Is your device encrypted? If not, could you please backup your data with TWRP, wipe data to try a clean flash? Then you could simply restore.
[One (M8) Android Development] simonvfr:
Not encrypted. Have backed up, full wipe, clean flash of latest nightly.

Same result!

Now restored . . .

It's not a problem for me, but it is odd.
[One (M8) Android Development] bgcngm:
Really, really odd. But I see you clean flashed the nightly. Could you clean flash my test build to see if is there any difference?

EDIT: Could it be related to the SIM card that you have in slot 2? Can you exchange SIM cards just to see what happens?
[One (M8) Android Development] simonvfr:
Wiped, clean flashed your test build. Same result.

Now restoring. Will try various SIM swaps in a bit. Will be interesting first to try booting with no SIM in slot 2. My current SIM 2 runs on the O2 network, which ironically uses LTE band which the M8 can't receive . . . .
[One (M8) Android Development] bgcngm:
One more build: https://mega.nz/#!u1QHET4I!GvnhZKe_ElCmH-miFvWRlpn5uIDSyM8247gCWF0Z3-w. Abnormal background data consumption is fixed.
[One (M8) Android Development] simonvfr:
Working fine for me. GPS working and no abnormal data usage. Phone calls and data working as normal.

I'll continue to run this and report any issues.
[One (M8) Android Development] bgcngm:
So, did you try swapping SIM cards to see if GSM network mode becomes available for slot 2?
[One (M8) Android Development] simonvfr:
Problem pinned down (but not solved!).

It is the SIM. Swapping SIMs gives same odd result for network choice, but now for SIM1. SIM2 now works fine on 3G (which is a first for me, and an excellent surprise as I had really disliked the stock HTC inability to do more than 2G on SIM2).

I have also activated a new SIM (from the same provider) and it demonstrates the same problem whichever slot it's placed in - and indeed did so even when placed in the slot before activtion.

So, the problem lies with the SIM. Can't imagine this is intended behaviour! Nor can I imagine getting any sense out of the provider if I raise it with them . . .

I'll explore later with SIMs from other providers and see how they behave.
[One (M8) Android Development] bgcngm:
Yeah, using stock ROM you don't have such possibility. In CM12.1 this worked flawlessly, i.e. when switching SIM2 network mode to LTE/3G, SIM1 network mode was changing automatically to GSM. Right now, with the new RIL blobs from M, this seems to work again in CM13.0, but I am not totally sure because I'm not able to fully test as I don't have any data plan enabled on SIM2.
[One (M8) Android Development] bgcngm:
Once you have tested the latest build time enough, please also comment about battery life. It seems to me that it has improved a bit with the new RIL blobs.
[One (M8) Android Development] simonvfr:
Found a problem.

With this build (and its predecessor from a couple of days back) I cannot search for networks using settings/SIMcards/SIM1 settings/network operators Search starts, but ends after sometime with an error. Same is true of SIM2.

With all official nightlies I can search for networks from either SIM, and then select and register on any that will allow me.

Most people would not notice this, as default network for SIM is connected anyway, even when roaming. For me, because I always have one SIM roaming, I like to be able to choose network that provides best service. For example, in UK I choose EE rather than default of O2 because I then get LTE rather than max of 3G.
[One (M8) Android Development] ryansc375:
Close But No Cigar

Running the latest international firmware and TWRP, performed clean install with current micro-gapps but couldn't get 5-4-16 nightly to connect to T-Mobile data. In addition, the weather widget doesn't work and says there is no weather provider. Back to Sense for now...

Edit: So sorry guys! I missed that this was the forum for the M8 dual sim model. Please disregard my post. Thanks!
[One (M8) Android Development] bgcngm:
Okay, that one was rather easy to fix. I'll upload a new build in the afternoon.
[One (M8) Android Development] simonvfr:
Excellent, thanks. I'll test and feedback asap
[One (M8) Android Development] bgcngm:
One test I would like you to make: switch data from SIM1 (with network mode set to LTE) to SIM2. Go to Settings / SIM cards / Preferred SIM for Mobile data. Observe and check if SIM2 network mode changes automatically to LTE.

As I said, I can't do this test because data is blocked on my SIM2.
[One (M8) Android Development] bgcngm:
Someone from China or India can guide me where to get the latest M firmware for m8dwg variant? [MENTION=3717700]wushi8[/MENTION], maybe?
[One (M8) Android Development] wushi8:
hi ,you can download m8dwg 6.0 firmware from this site.

http://pan.baidu.com/s/1c2js5YK password：nof8
[One (M8) Android Development] simonvfr:
I'll see if I can test that with your new build coming this pm. Might not be simple because of my current SIM oddity where they are both set to LTE preferred. If necessary I can probably find another data enabled SIM to experiment with but that might take another day.
[One (M8) Android Development] bgcngm:
Wow, that was fast. Do you have the link to the full stock ROM? I need that as well.

Nevermind, I may get one as well from a friend.
[One (M8) Android Development] bgcngm:
Okay, here you go: https://mega.nz/#!L8I31DLB!xuBJxhwHoqBjuOieafoto6hw8-4qghMW7KyJvJufU5A.