yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] tomcat-:
yeap, it was the same problem on 12.1.

Another thing to note is when i go on camera mode i can take 2 photos and then the camera app switches off to main screen..! I don't think it's my settings of the camera?
[One (M8) Android Development] JoostA:
Saturday I updated to cm-13.0.20160729-NIGHTLY. However it appeared this build did not recognize my 32 Mb SD card. In my case I use it as ¨internal memory¨. Furthermore: the phone is encrypted under Android.

I had to switch off the phone, take out the SD card and re-insert it when the phone was re-started. In the options menu I then could see the SD card was found, checked and mounted.

I then reverted to my previous build (that still was on the SD card). In my case 13.0.20160723-NGHTLY (I nowadays only update once a week).

The SD card mounted without a hitch.

Then I tried cm-13.0.20160728-NGHTLY. However it shows exactly the same problem as cm-13.0.20160729-NIGHTLY.

So I now went back to cm-13.0.20160723-NIGHTLY that shows no problems at all.

Anybody that can replicate the problem ?

Edit 31 July: In the changelog for cm-13.0.20160730-NIGHTLY there is a reference to "mountservice Don't nuke all volumes when decrypting".

I am not a very technical person , but my guess from reading the code is that it is possible that the SD card was not mounted properly when decrypting the phone (as said before mine is encrypted). Whatever the reason: it is working properly again -:)
[One (M8) Android Development] gazzacbr:
Hi, still working great for me.

Question, I see the nightly builds and usually try them but how to tell what the changes are?
[One (M8) Android Development] bgcngm:
There you go: https://www.cmxlog.com/13/m8d.
[One (M8) Android Development] gazzacbr:
Thanks, really appreciate the great work you are doing for our under supported phone. [emoji106]

This is so light compared to the HTC bloat ware that I never used.

I couldn't go back to a single sim phone now, it's just so convenient. Although I can see that companies would rather sell 2 phones than one [emoji6]
[One (M8) Android Development] KaRLiKCZ:
Phone reboot

Hi All,

I have very often phone reboot after when trying to make second call.

When phone reboot I can make one call. But when I start second call e.g. after half hour the phone in the time when it should establish call just reboot. After reboot it is the same. I can make a call and when I try to make second call later, phone reboot.

Couple times I have luck and i can make more calls.

Does anyone of you have the same problem?

Do you have any idea how to solve it?

I have nightlies at the moment and this start before about week. Don't know exactly :(

Thanks for your ideas.
[One (M8) Android Development] bgcngm:
Are you using any third party dialer? If you can reproduce the issue as you say, then take a log. I'm sure that's an isolated issue.
[One (M8) Android Development] KaRLiKCZ:
Yes, I'm using drupe dialer.

With which SW I should take a log? It is not problem if log is after reboot of phone?
[One (M8) Android Development] bgcngm:
Grant it permissions then.
[One (M8) Android Development] bgcngm:
Question is: does stock Phone app works fine? No one else complains and I never had such issue, so that's likely a problem of the 3rd-party app.
[One (M8) Android Development] KaRLiKCZ:
After two days with standard dialer I have no problems. So problems comes from drupe.

Thank for easy identification. Will try contact them.
[One (M8) Android Development] vuvkar:
Is there any news about connectivity issues? In road it says no sim. Thanks.
[One (M8) Android Development] MotoE2014:
Because if I post a kernel , the new build the kernel is removed ? There is a solution to this problem ?
[One (M8) Android Development] bgcngm:
Can you rephrase that? I can't understand what your problem is.
[One (M8) Android Development] MotoE2014:
go forth the CM14 for htc m8 ??
[One (M8) Android Development] Eurofighter_ty:
This thread is also for the normal single sim M8?
[One (M8) Android Development] bgcngm:
No, only Dual SIM. This is the thread you're looking for.
[One (M8) Android Development] gazzacbr:
Hi,

I cannot seem to connect my vpn. Same one works on laptop and wifes iPhone.

Is there any problems? Does someone else have a vpn connection with this rom?

Thanks
[One (M8) Android Development] co2-guy:
I just tested vpn with NeoRouter and L2TP. Both worked fine :)

I'm on 20160904-Nightly btw...
[One (M8) Android Development] gazzacbr:
Hi, [MENTION=2188734]co2-guy[/MENTION]: thanks for checking.

I turned off the AFWall+ firewall, restarted and now it works.

Edit: question was off topic really
[One (M8) Android Development] gazzacbr:
Hi, anyone have the dual cameras working? I have the HTC camera and gallery apps but dual effects never work
[One (M8) Android Development] bgcngm:
Disable Xposed. No one else complains about standard dialer. This is not an issue I will look at.
[One (M8) Android Development] bgcngm:
Dual camera is disabled for M8 / M8 Dual SIM in CM, so only one rear camera is used.
[One (M8) Android Development] vuvkar:
Signal is not stable especially while driving, the only solution is restart. Is there any fix? :/ Thanks developers.
[One (M8) Android Development] gazzacbr:
Ok, thanks. Does disabled mean disabled or is it that no one has got both cameras to work?
[One (M8) Android Development] menaaboud:
Network connectivity issue still present in last nighty builds also last stable.

can you help please ?

Turning on Network Data Connection. and using the Internet on cellular makes the phone not be able to make phone calls but it seems that i can receive phone calls even when cellular is reported offline or when airplane mode is on.

thank you for the effort (Y)

---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------

Can you help me go back to stock rom ?
[One (M8) Android Development] JoostA:
Recent compatibility issues with Xposed Framework

Although I guess I know what the developers think of this (which is: there is no support) I want to share the following with those interested.

As far as I know at the moment the Xposed framework does not work together with cm-13.0-20161114-NIGHTLY-m8d.zip (most recent), and cm-13.0-20161112-NIGHTLY-m8d.zip (previous one). It does work however with cm-13.0-20161107-NIGHTLY-m8d.zip (the one preceding the other two). It does not matter whether you install all files together (in TWRP :"adding more Zip's") or separately. Nor does it help to empty the Dalvik cache.

When trying to install the two "non-compatible" builds of Cyanogenmod, your phone will not re-start at all. It will (as far as I know now, I did not want to wait longer than 30 minutes...) remain in an infinite start mode showing only the Cyanogenmod face.

Luckily it can be interrupted manually in the usual way (search the internet if you don't know how) , so that it is possible to return to recovery and re-install the desired CM 13.0 file. That is: the first two mentioned (1114 & 1112)should be installed without installing the Xposed framework, the third (1107) may be installed together with the Xposed framework. You may then use your phone normally again.

I guess this is some glitch, as there has never been an issue between CM 13.0 and Xposed (the one issue mentioned in this thread once before, at least did not exist on my phone).

I will edit this post as soon as I know how to fix the problem or whenever the problem has gone away in a new nightly build (which happens from time to time with this kind of anomalies).

Greetz
[One (M8) Android Development] bgcngm:
Is anyone still using M8 Dual SIM? I have finally managed to work on cm-14.1 bringup and everything seems to be working pretty good. Just wondering if I should create a new development thread or if there's no longer interest.
[One (M8) Android Development] Martin1979:
Hi,

first of all thanks a lot for your work.

I am still using M8d.

Creating a new 14.1 thread would be perfekt.
[One (M8) Android Development] JoostA:
Well, as you can see in my previous post I am still using it. (And checking in on an almost daily basis).

It is just because of Cyanogenmod that I use my HTC . The original HTC software was really awful and was a disgrace to the phone. I saw the new CM 14 build somewhere already , and creating a new thread would really be apprciated. When al is working well as you said, of course I will soon start to use it as well (the HTC is being used privately and for buisiness, so some stability is necessary).

By the way: I am even still using my Galaxy Tab 2.0 (P-3110), running on Cyanogenmod 11 (Android 4.4.4.), that has being security patched up until now. That too It is still very productive and working without a hitch. No reason whatsoever to exhange that. Same is true for the HTC. I will keep that as long as it is reasonably up-to-date.

Greetz
[One (M8) Android Development] fizbanrapper:
I've been getting quite a few requests. Definitely worth a thread!
[One (M8) Android Development] bgcngm:
Are you getting requests for the dual SIM variant? That's quite strange. I would expect users to use this thread to express their "whishes".
[One (M8) Android Development] :
There are quite a few requests in the CM 14 build thread for the dual SIM variant
[One (M8) Android Development] co2-guy:
Please do :)
[One (M8) Android Development] JensL76:
Yes, please. It's the last HTC flagship with dual sim sold in Germany.
[One (M8) Android Development] backtrack292:
please do , i can't wait to c cm 14 on my m8 ds
[One (M8) Android Development] medomeyi:
Please do we are waiting[emoji4]
[One (M8) Android Development] bgcngm:
Okay, new thread for M8 Dual SIM only is here: http://xdaforums.com/htc-one-m8/development/rom-cyanogenmod-14-1-htc-one-m8-dual-sim-t3507192.
[One (M8) Android Development] gazzacbr:
Hi, off topic a bit but anyone know how to change the soft keys on this rom? SoftkeyZ says it doesn't work.

Thanks
[One (M8) Android Development] simonvfr:
Bluetooth issues

I'm finding that Bluetooth audio streaming disconnects at variable intervals (every 10 minutes or so). Switching bluetooth device on/off reconnects, as does on/off of Bluetooth in M8 settings.

This has been commented on on other device forums, so not just an issue for M8D. However, it might be useful to note if you are considering a nightly installation.

EDIT: Problem seems to have been fixed with the significant Bluetooth/Wifi changes in 2015-12-10 build. Stable connection to handsfree is now maintained. :) Further Bluetooth changes to come, but this now seems stable enough to be my daily driver. Looking forward to restoration of MSIM features that are missing. Good work [MENTION=455439]bgcngm[/MENTION] and the CM team!
[One (M8) Android Development] bgcngm:
Indeed, the last build includes an update to WiFi and BT. Gladly it solves the reported connection issues. :)
[One (M8) Android Development] simonvfr:
Unfortunately, Bluetooth streaming is broken again for me in 11 Dec build. Stutters and hesitates within seconds of starting. Reverted to 10 Dec and all ok. Tried 11 Dec again - same problem. I'm now back on 10 Dec, streaming happily.

EDIT : False alarm? See two following posts
[One (M8) Android Development] bgcngm:
Strange, look here.
[One (M8) Android Development] simonvfr:
Strange indeed. Having looked at the positive comment in the single sim M8 thread, I tried flashing a third time.

And, it now seems to be working fine!

Very pleasing, but puzzling. I had been messing with various forms of streaming and there may have been some odd interactions. This time I had Catlog running and ready to record a log of the faults. And nothing has happened. So, I withdraw my report of a fault . . . .

I'll monitor and if fault recurs I'll get a log if at all possible. No time in next couple of days to attempt a full replication of the circumstances which seemed to produce the fault before.

Sorry if I was raising concern unnecessarily!
[One (M8) Android Development] simonvfr:
Bluetooth fault replicated!

Out for walk, Bluetooth streaming perfect. On return to house, Wi-Fi reconnected automatically, and Bluetooth started stuttering and pausing (at much the same time, assume must be connected? )

This time I have some log info. I have a fuller log from earlier if this does not give any useful information. This was taken during the problem.

https://onedrive.live.com/redir?res...9981&authkey=!AF78NkRGFSYXgU4&ithint=file,txt
[One (M8) Android Development] juaanito:
Is boom sound available with this rom?
[One (M8) Android Development] simonvfr:
No, but there is an equaliser, and sound quality is good.
[One (M8) Android Development] simonvfr:
Giving up for now

I've run every nightly since the launch, and found much to like. However, the continued failure of audio streaming on Bluetooth is a killer for me. I've posted a log, hoped for developments, and watched the changelog with interest. Today, however, I have given up - and reverted to the final nightly of 12.1.

I shall continue to monitor the forum and the changelog, and as soon as there is a fix for 'audio congestion' that causes Bluetooth to stutter and stick, then I shall be back!
[One (M8) Android Development] judasith:
Mobile Data Connection Issue on DWGL

First of all, thanks very much for this port! Even with our M8 DUGL or DWGL (my case) we can finally get all the awesomeness of CM 13!

I'd like to report an issue and also ask to our fellow boardmembers if they know any solutions or get the same problem:

- The mobile DATA connections (for both cards) are stuck to EDGE, even under 3G or HDSPA or LTE coverage.

- When I go in the settings, "Cellular Networks" panel, the setting "Preferred Network Type" is locked on "LTE (recommended)", and I cannot select any other option (3G, 2G)

I have a M8_DWGL, with the latest LP firmware, I am upgrading to every Nightly, currently on 25/12.

On the other only custom ROM I used in the past, Maximus HD 3.0.1, the HDSPA and LTE connections work, so it is not an hardware issue.

Please help! It's the only downside to an otherwise awesome ROM.

Thanks,

Jack
[One (M8) Android Development] huoqianyu:
TEST

来自我的 HTC M8d 上的 Tapatalk

---------- Post added at 02:53 AM ---------- Previous post was at 02:50 AM ----------

Hello developer, I got a problem answering the phone. When phone call in, the circle on screen works bad because I slide it to the answer icon, it doesnt work.

Also I found out the sdcard (both internal Storge and ext sdcard)always dont mount when connecting to computer.

Im using m8dwg(China Telecom Ver.).

来自我的 HTC M8d 上的 Tapatalk
[One (M8) Android Development] bgcngm:
Willing to try a test build? :p

Flash next nightly and that should be fixed. ;)
[One (M8) Android Development] simonvfr:
Certainly! May not be able to try it till Thursday as I only have flaky internet access till then.
[One (M8) Android Development] huoqianyu:
is the problem of cannot answer phone be solved?
[One (M8) Android Development] bgcngm:
I don't know what your problem is and without any log, I'm not able to do anything at all.
[One (M8) Android Development] bgcngm:
Before anything else, can you confirm this?

And by the way, more and more dual SIM features are being (re-)added to CM. If I remember correctly, this was one of the things you wanted.
[One (M8) Android Development] simonvfr:
I've seen some optimistic comments earlier on the single sim forum suggesting it was fixed, and they proved to be premature.

But I'll try it out on Friday if nothing contradictory appears before then (you'll understand it's a bit of a pain moving backwards and forwards between 12.1 and 13 for test purposes).

Yes, separate ring tones was something I wanted to see restored. And with this to come in the next nightly, it might even work! ;)
[One (M8) Android Development] simonvfr:
It seems that I was right in suggesting that optimism about bluetooth was premature. Perhaps it would be sensible for me to try your test build when it's ready?
[One (M8) Android Development] bgcngm:
Yeah, I'll try to build it tomorrow and then I'll share it here for you to test.
[One (M8) Android Development] simonvfr:
Thanks a lot. Whenever you have the time. Your work is much appreciated - and if you find a solution to this issue there will be many joining me in thanking you!
[One (M8) Android Development] bgcngm:
There you go: https://mega.nz/#!GswgzaxC!7ICplZt_NJDP6P0NvXfpXVNZ7Wz1LsDsB9c5sxy6E9Y.
[One (M8) Android Development] simonvfr:
Installed and testing. Bluetooth streaming is running. I'll update in due course, as the problems before have often taken a while to become evident. Thanks, and fingers crossed!

Edit (after 4 hours): running well, with a couple of hours streaming to Bluetooth speaker, and a couple to Bluetooth hands-free. Will continue to test throughout the day.
[One (M8) Android Development] simonvfr:
I really thought you had it cracked. But no, the stuttering problem has come back. Present with both headset and speaker. Persists across source apps until reboot.

Log link attached here
[One (M8) Android Development] bgcngm:
Sorry to hear that. Out of ideas right now.
[One (M8) Android Development] simonvfr:
No worries. Thanks for trying. I'm back to 12.1 for now, as Bluetooth streaming is central to my use of the phone. Happy to test another solution if you come up with anything in the future!
[One (M8) Android Development] piratoes:
Same probleme here :) :confused:
[One (M8) Android Development] bgcngm:
Yeah, Dual SIM and regular M8 has some issues with BT audio streaming. Not sure about other CM13 supported devices.
[One (M8) Android Development] piratoes:
It looks like this is just a CM Problem. Right?
[One (M8) Android Development] bgcngm:
Not sure if it affects all CM devices or not.
[One (M8) Android Development] bgcngm:
It seems that the Android 6.0 OTA update is rolling out now. If someone manages to get the update, please share firmware.zip here. I want to flash the latest radio.
[One (M8) Android Development] simonvfr:
It seems to be out today in Germany. Seems to be a two part download, which is interesting. I guess all will be come clear shortly.
[One (M8) Android Development] bgcngm:
Nevermind, got it from here. Seems that the baseband firmware version remains the same.
[One (M8) Android Development] bgcngm:
Could you please try this hacky workaround?
[One (M8) Android Development] simonvfr:
I'll have a go at the weekend
[One (M8) Android Development] simonvfr:
Ok, have started the test process. Because there is uncertainty around this, I am trying to be systematic. I have moved back to the CM13 branch and updated to the latest nightly. I intend to test run this for a while to replicate the Bluetooth streaming problem. Only when that occurs will I try out the hack of copying the two Bluetooth files from recovery. Then I'll run again till problem occurs (or doesn't :) )

I'll report as each stage completes. Whole process could take a day or so.

EDIT: Two hours of bluetooth streaming to speaker (not handsfree) with 24 Jan nightly. No congestion. I can see why there are so often reports that everything is fixed! I'll now move to trying handsfree streaming.

EDIT 2: Within seconds of starting Play Music streaming to hands-free, the stuttering began. Usual log errors of multiple like this

01-24 14:03:00.876 E/bt_btif (5420): ## Audio Congestion (iterations:51 > max (3))

01-24 14:03:01.008 E/bt_btif (5420): [media task tx timer] ts 11009307114, diff : 04296008, queue sz 0

01-24 14:03:01.008 E/bt_btif (5420): ## Audio Congestion (iterations:44 > max (3))

01-24 14:03:06.899 E/bt_btif (5420): [media task tx timer] ts 11010902534, diff : 00750924, queue sz 0

So, it seems the problem does still exist in the latest nightly. I shall now try copying in the two hack files, and repeat testing.

EDIT 3: After following the instructions exactly, I could not find the destination folders for copying. I rebooted and checked they existed using ES FileExplorer. Then I realised that the vital part of Mount System was missing from the instructions, lol. Meanwhile I checked, and found that Play Music would now stream to the hands-free. Could it be that changing bluetooth destination kicks this off? Anyway, back to recovery, mount system and copy the hack files. Reboot and start streaming - which works, but then that proves nothing! I shall report later whether I can provoke the same fault. . . . . .

EDIT 4: Sadly, I can report that the problem is NOT fixed by this hack. Streamed fine to speaker for a while. I then switched off bluetooth on speaker, and connected Sony hands-free. Started streaming, and same congestion, with same logcat errors was apparent within seconds.

Back to 12.1 for me, still awaiting a solution. I haven't the technical knowledge, but it really does seem to be related to changing from one bluetooth device to another (same has happened before when connecting to car system). I might be clutching at straws, but could this commit due in the next nightly be relevant?
[One (M8) Android Development] simonvfr:
Sad to say, I was clutching at straws. 25 Jan nightly ran bluetooth streaming for a couple of hours. But it didn't last. Congestion has reoccurred. Damn! Back to 12.1, with much gnashing of teeth. There's lots to like about CM13, but I can't use it yet without a bluetooth fix.
[One (M8) Android Development] Simply_S:
I'm back :D

I spent a lot of time running 12.1 but ran into two issues that became more and more frequent : random reboots and the loss of all network settings. I therefore decided to leap forwards to 13.0

I took a few shortcuts and my advice to other would be *not* to do so. Follow the instructions, wipe and do a full reinstall with an appropriate Gapps (super in my case). So a couple of reinstalls later, here I am.

Generally very happy but two issues, one of which I can live with, the other not :

- have to toggle airplane mode on/off after boot before it will connect to the mobile network (livable)

- my mobile network will only connect on EDGE and it is too S-L-O-W

So my question is which nightly are you referring to that has fixed this ? I am running 20160126

As always, appreciate the work and the support

UPDATE : I have another issue, and not a small one. Although I can make an receive calls, and I hear dial tones, I can't hear my correspondent and they can't hear me. You would have imagined this would be one of the first things I tried but ... it wasn't. Baseband version is 1.24.30336021.13G_30.69.336021.00_F
[One (M8) Android Development] simonvfr:
I have dirty flashed in and out of 13 from 12.1 three times in the last few days, testing new builds for the bluetooth streaming bug that has kept me from changing permanently to 13 (see posts above). I have never had the two problems you describe (nor on any of the earlier 13.1 builds. I have had instant mobile network connection on boot, and had 3G/LTE depending on local availability. No idea what is causing your problem (sorry!) but I can definitely assure you that it's not inherent to the 13 nightlies.
[One (M8) Android Development] Simply_S:
Good morning,

Far from me to suggest that it was inherent to the CM13 nightlies

I'm wondering if it's not more to do with the setup of the network operator (in my case Proximus). The Access Point has to be corrected as by default it is set to a Canadian operator, and the Bearer settings are "Unspecified" (I have tried selecting LTE but it makes no difference)

It would be nice if someone could point out what I could fiddle with to try to sort it out because apart from this, it's looking great
[One (M8) Android Development] simonvfr:
Did you try flashing it? The version is reported as 6.16.401.101 which is not the same as with the Lolipop version? Or am I missing something? Still searching for something to help with Bluetooth a2dp problems.
[One (M8) Android Development] ayysir:
has data been fixed? cant get data working on 1/26 nightly.. baseband 1.23
[One (M8) Android Development] co2-guy:
Call recording re-added, but...

So call recording was re-added in cm13 nightlies from 20160212, but as far as I can see, it need's to be enabled on per device basis, like this: http://review.cyanogenmod.org/#/c/130743/

I am not clever enough to begin commiting to the repository, so can anyone with the know-how help with this? :cowboy:

Thanks

co2-guy