yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] simonvfr:
Thanks, this version flashed and booted fine. All seems ok so far.

I'll report any issues over the next week, and not flash any nightlies in the meantime. My experience may not be normal, as I am roaming currently with SIM1 on to UK networks. Not had any disconnections anyway since coming to UK 3 days ago. Whole disconnection business, with SIM slots then showing empty until reboot, seems very unpredictable!
[One (M8) Android Development] bgcngm:
Did you notice the camera issue? I have re-uploaded the fixed package (see my previous post).
[One (M8) Android Development] simonvfr:
Just found the camera not working problem! Is the fix at the same address as the last one?
[One (M8) Android Development] bgcngm:
No, new link is this one. Sorry for the inconvenience.
[One (M8) Android Development] simonvfr:
No worries. Thanks for your continuing work. I'll flash the mended version when I am back on wifi.

EDIT Latest version flashed, and camera working again
[One (M8) Android Development] dohtune:
Not sure this is coming in time... I did a clean install of the new build. More stable but had network disconnection after receiving a call. Also noticed I could not launch the camera.

Does the new package also resolve the network disconnection above?
[One (M8) Android Development] wushi8:
Hi,I am from China,I very like CM ROM,since I know HTC M8D can flash CM ROM,I flash cm rom right now,I will report any bug what I have find!

1.NFC problem,I use NFC-SIM instead of BEIJING public transportation card,but I can't use with cm-12.1-20150926-NIGHTLY-m8d.zip。

2.high power, official sense rom use 3%-5% one night,But cm rom use 10%-12% one night.
[One (M8) Android Development] Simply_S:
Quick update from my side.

Enabled encryption today with no issues at all.

However, I had network disconnects. Lots of them.

I have noticed several things :

- it would appear that they occur mainly in areas of low coverage. I had a lot in the métro and inside a building

- even if there is no network, SMSes and data still work ! this came as a surprise

Am now flashing this build to see if it solves it. I am considering that since it is a nightly it can be dirty flashed. Hope I'm right, please advise if not

Thx
[One (M8) Android Development] simonvfr:
First, if you mean the experimental build designed to address disconnection, then it can be dirty flashed like a nightly. I've more been up some 40 hours on a dirty flash since the latest version.

Second, your points about disconnection and weak signal are interesting. Thinking back, my disconnections have all been either at a point where switching from one cell to another would occur, or in areas where I know switching between 2g and 3g might happen. Since last week, roaming in the uk, where strong 3g signal has been pretty constant (albeit from different providers) I have had no disconnections. You say you continue to get data and sms when disconnected - my earlier disconnections have led to SIM slots showing in menu as empty, and no sms, data or calls possible.
[One (M8) Android Development] bgcngm:
Quite strange that you find that disconnections are somehow related to low coverage. Usually, at work, I have to go to an area with low to no coverage and never had this kind of disconnection issues. I mean, I get the "No service" message, but then when I'm back to a good coverage area, the phone recovers by itself and never had to reboot phone.

The only thing that will eventually help me to rule out this issue is a radio logcat:

adb logcat -b radio > radio.log

Please note that it only makes sense to log shortly after a network disconnection issue.
[One (M8) Android Development] simonvfr:
Ok, I'll try for a log if I get another disconnection. Is there a way to take this log on the phone rather than from computer? All my disconnections have occurred away from home, and reluctant to leave phone out of action till return.
[One (M8) Android Development] bgcngm:
There are several logcat apps on the Play Store, but make sure you filter for radio, as I mentioned.
[One (M8) Android Development] Simply_S:
Idem ditto.

Successfully dirty flashed last night, but the issue is still there. I have the same issue in that my disconnects never occur at home where I have the adb tool available so will find a logcat on Google Play

No camera issues, nothing erlse new to report except one thing that I may just not have noticed before

Google Now serach often fails with "Oops something went wrong" and "Retry" despite the fact that connectivity is there. Anyone else had this ?
[One (M8) Android Development] simonvfr:
I've found this logcat app good, because it has an easy option to take only the modem (radio) log: https://play.google.com/store/apps/details?id=com.tortel.syslog

No Google Now problem here . . . .
[One (M8) Android Development] Simply_S:
OK, got a logcat capture as it dropped this evening. Let me know if it helps. Hope so :D
[One (M8) Android Development] bgcngm:
One thing I have noticed from that log right way after opening it was that you have slot0 in nwMode 1 (GSM) and slot1 in nwMode 9 (LTE). Can you put it the other way round, eventually by exchanging SIM cards? I mean, this is just for testing purposes. Remember that in stock ROM, the SIM 2 only works in GSM. Maybe this is the problem here and it could make sense why I have got no problems so far, because I use it exactly like that: SIM 1 set as LTE (recommended) and SIM 2 set as 2G.
[One (M8) Android Development] simonvfr:
I can see what you're getting at there. However, mine is set as LTE for SIM 1 and also for SIM 2 (shows as current 2G). My suspicion is that the hardware only allows 2G on SIM 2 anyway, even though CM seems to give the choice? In other words, is the apparent choice meaningful? I've set mine now to force 2G on SIM 2, as this SIM is used only for incoming calls/text anyway.

Mind you, I am now up to 69 hours on the experimental build with no disconnection.

I see the latest nightly has many changes from the MSM8974-common repo. Would I benefit from flashing that rather than sticking with the experimental build? What would be better for you in gaining potential disconnection logcat information?
[One (M8) Android Development] bgcngm:
Yes, maybe the hardware doesn't really "like" the user to set SIM 2 network mode to any other mode than 2G. CM allows that, by default, but eventually I'll have to restrict to 2G only, if we conclude that this is causing the disconnection issues.

You can go ahead and flash the new nightly, because I am realizing that the changes I did for the experimental build have no effect when it comes to fixing the disconnection issues. You can still provide a radio log with the new nightly.

By the way, I was mainly the one behind that change related to the switch to the new device_htc_msm8974-common repo, but it doesn't really add or change anything right now. It was just put in place for future development and the advantage is that there is now a repository that is common to all HTC devices based on MSM8974 SoC.
[One (M8) Android Development] bgcngm:
No more comments to that? Can the rest of the users (that were having network disconnection issues) confirm if the same set up was being used, that is SIM 1 network mode set to 2G and SIM 2 network mode set to LTE or 3G? If that is the case, please force SIM 2 network mode to be always 2G and let me know if disconnection issues remain.
[One (M8) Android Development] dohtune:
Thanks for the all the work you are putting into fixing the issues so far. I have clean-flashed with the latest nightly build and set SIM1 (LTE recommended) and SIM2 (2G). Got network disconnection after about an hour. Subsequent reboots result in network disconnection after about 5 - 15 mins. See log attached.

Happy to test further. Thanks again.
[One (M8) Android Development] bgcngm:
Not good to hear that as I was really expecting that it could be the reason of the disconnection issues. As far as it concerns to your log, something must have happened because it doesn't include as much information as before.
[One (M8) Android Development] dohtune:
Was hoping I would report back with good news myself. I restored back to Maximus ROM but more than happy to re-flash and send you another log file if you so require.
[One (M8) Android Development] simonvfr:
Such a pain for you - and a mystery! I've now had no disconnections for about 10 days. This may be chance. Or perhaps because I am roaming on SIM1 in the UK, instead of using in France as normal. Or because I have switched off (fake) LTE on SIM2.

Can I check the nature of the disconnections you were getting? When disconnect occurred, if you opened settings/SIM cards, did it show the two SIM slots as empty? This is what I had each time I disconnected, and only cured by a reboot, but I never had them more than once a day. Just wanting to check we are describing the same problem . . . . .
[One (M8) Android Development] dohtune:
In settings/SIM cards, it shows the two SIM slots as empty - it's the same problem we are describing. Don't understand why I am still having the random network disconnection on mine.
[One (M8) Android Development] simonvfr:
Strange. I'm no expert, but there's very little in your last log - except it shows the disconnection! I'm hoping that [MENTION=455439]bgcngm[/MENTION] and colleagues might be able to work out something, and I shall supply logs if I do get more disconnections. It doesn't seem hardware related - as both you and I have entirely disconnection free experiences with Maximus (which for these purposes is essentially stock) on the same hardware.
[One (M8) Android Development] Simply_S:
Sorry for the delay. I was at home yesterday and so "well covered" :)

I proceeded according to instructions and swapped the 2 SIM cards (pity this because I was looking forward to no longer having to fiddle with nano SIMs with my fat fingers). Both SIMs are set to LTE recommended. SIM1 is on my home network, SIM2 is roaming from a foreign network and they are both connected to the same local network (Proximus and Proximus as Vodafone partner)

The good news is ... no disconnects, even on the métro !!!!

However, I have noticed that SIM1 stays on 2G after going through a poor coverage area and never "recovers" to LTE without a reboot :(. This is a real downer

Other issue encountered today, several calls (in/out) where I couldn't hear my correspondent after picking up and he couldn't hear me. Ended up rebooting and it was OK. Don't think it's ROM related but thought it worth mentioning in case others face the same issue

UPDATE

Just tried to reanimate LTE by fiddling with the network settings on SIM1. Switched it to 3G and then back to LTE, then turned mobile data off and ... full network disconnect. Sorry, no log because I wasn't expecting that :(. Definitely looks as though network disconnects are related to data network switching

UPDATE2

Have had 3 network disconnects since, despite being at home where all was well yesterday. Last one was so quick I didn't even have time to launch logcat after rebooting

UPDATE3

So ...

Since last night, no way of keeping a network. Last drop is in the larger of the two files in the attached zip

This morning, I had an idea and turned mobile data off. Sure enough, even in the métro, kept my connection. However, seconds after turning it on again ... bang. Smaller of the two files

For what it's worth :

I also tried a soft reboot, whereafter it told me that I only had one SIM card inserted. Hard rebooted and then it did indeed see the two, but told me that SIM cards had changed. Thinking (hoping ?) that something might have changed, I checked the SIM cards (nothing to be reconfigured) and tuned mobile data back on. Result ? Bang !

Hope the logs and this info might help you delve further.

In response to another question asked, my SIM cards always show as empty after losing connectivity

So it looks like I'm going to spend the day without mobile data :)
[One (M8) Android Development] bgcngm:
Another experimental build if you may. Download from here.
[One (M8) Android Development] Simply_S:
Some early feedback.

Dirty flashed, held my breath and turned logcat and mobile data back on. Initially seemed OK, but after a while, started getting disconnects again. Traditional logfiles attached.

Strangely only had one disconnect in the métro and it appeared to "recover" correctly from 2G--> 4G

Thanks for your help
[One (M8) Android Development] consuldore:
Something I've noticed the other day when I was using my phone as a hotspot to connect my laptop to the internet was that with this setup you can reproduce this bug in minutes. It was not possible to download bigger files.

So the problem seem mobile data related. Since I'm using WiFi now most of the time I did not had another dropout.
[One (M8) Android Development] bgcngm:
Okay, I had an idea that is to use radio blobs from standard m8. Let's see how it goes. Here is another experimental build. Please provide feedback only using this build.
[One (M8) Android Development] Simply_S:
Thanks for the very quick feedback.

Dirty flashed, up and running with logcat. Will give feedback ASAP but will only be back on my "usual route" on Monday so that's when we'll have "comparable" data
[One (M8) Android Development] dohtune:
Dirty flashed. 2 hours and counting... Wow! This is the longest I've done without network disconnection. You may have resolved the problem! Will provide update subsequently. Thanks for all the effort!
[One (M8) Android Development] Simply_S:
Yup. Me too, no disconnects yet. Have been in some low coverage areas but so far, so good. Keep you posted
[One (M8) Android Development] simonvfr:
Back from two days travelling 800 km round the UK, during which I have experience huge data problems, with multiple disconnects (especially when trying to use a tablet for sat nav on phone's hotspot). Horrible experience.

Now back in area of good stable coverage, and I have flashed the new experimental build. All seems good - but based only on a morning's use in an area where problems were not occurring before I went travelling. As the saying goes, absence of evidence of problems is not evidence of absence of problems.

Still, others' reports are encouraging - and I'll keep fingers crossed that no-one reports the dreaded empty-SIM disconnect!
[One (M8) Android Development] fade2blak:
Hello - I tried to flash this rom on my M8_DUGL phone, it says its incompatible as my phone is M8.. What could be wrong? Is there a difference between M8DUGL and M8_DUGL?

Thanks.
[One (M8) Android Development] bgcngm:
Please provide the output of 'fastboot getvar all'.
[One (M8) Android Development] fade2blak:
INFOversion: 0.5

INFOversion-bootloader: 3.18.0.0000

INFOversion-baseband: 1.18.30306251.05G

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main:

INFOversion-misc: PVT SHIP S-OFF

INFOserialno: HT474WM00685

INFOimei: 352202060653500

INFOimei2: 352202060653510

INFOmeid: 00000000000000

INFOproduct: m8_dugl

INFOplatform: hTCBmsm8974

INFOmodelid: 0P6B64000

INFOcidnum: HTC__J15

INFObattery-status: good

INFObattery-voltage: 0mV

INFOpartition-layout: Generic

INFOsecurity: off

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: 6b903f73

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!
[One (M8) Android Development] bgcngm:
Probably you have an old recovery. Install the latest TWRP recovery and try again. By the way, I see your phone's baseband version and hboot is old. Make sure you upgrade to the latest firmware.
[One (M8) Android Development] fade2blak:
Thanks for your quick response. I did try to install the latest TWRP but it won't let me get into recovery.. I had to get back to the old version to be able to access recovery.. probably because my firmware is old? I will try flash the latest firmware and then flash latest TWRP again..

Cheers..
[One (M8) Android Development] bgcngm:
Yes, that's the reason then. You must upgrade firmware first.
[One (M8) Android Development] Simply_S:
OK, looking good

Flashed on Staurday, have been through my usual commute this morning, no disconnects and ramping up and down 2G-4G nicely

On Saturday, I was in a place with very poor coverage, next to my wife who has an identical phone running stock. We both had disconnects and both recovered in the same way with 1 exception. My second SIM slot (roaming) disconnected and I had to switch the SIM off and on again to recover, but I think we can consider this as exceptional circumstances

I think you've cracked it
[One (M8) Android Development] simonvfr:
This is very encouraging! The one disconnection you report seems to be of a different sort - one SIM only, and recoverable without reboot.

Hard to prove an intermittent fault is cured, but the continuing lack of disconnect reports is striking. :)
[One (M8) Android Development] bgcngm:
I like feedback so far, but it is too early to celebrate. :p
[One (M8) Android Development] simonvfr:
Is it time for just a little celebration?
[One (M8) Android Development] bgcngm:
You all need to tell me. I guess that no news is good news, but I'm not sure if all users that were previously reporting the issues have tested the latest experimental build.
[One (M8) Android Development] simonvfr:
Let's see if we can get some response. People may have been waiting for a disconnect to report.

If you've installed the latest experimental build (see this post from 2 October) ) then please let [MENTION=455439]bgcngm[/MENTION] know how it's going.

My report: 3 days, mostly strong signal, no disconnects, no other problems noted
[One (M8) Android Development] bgcngm:
Calling out at least: [MENTION=5831291]dohtune[/MENTION], [MENTION=544247]Simply_S[/MENTION], [MENTION=277544]consuldore[/MENTION]
[One (M8) Android Development] bgcngm:
If it wasn't the damn NFC thing, I could apply for the next CM stable release. But I'm really stuck bringing up NFC for m8d. :(
[One (M8) Android Development] simonvfr:
To be honest, I had not realised NFC was not working! I never use it, and switched it off as soon as I first installed CM :)

It must be frustrating, and it would be good to complete the feature set and be able to have a stable release. Is there no clue from how this was resolved for the single SIM version? (Sorry if this is just too obvious - I guess you would have started there! Still, if using the radio blobs from single SIM has helped (perhaps) resolve our disconnection issue . . . . . )
[One (M8) Android Development] bgcngm:
Yeah, it's really a pity that I can't apply for a stable release only because of the non-working NFC. The single SIM m8 has exactly the same pn544 chip, but running a different firmware than ours, it seems. Although, I don't know how that could be a problem. I was really hoping that [MENTION=5314976]uberlaggydarwin[/MENTION] could give us a help as he will face the same problem when porting CM to e8.
[One (M8) Android Development] dohtune:
Apologies for the delay...simonvfr is right...there's been no network disconnection since I flashed the experimental build. [MENTION=455439]bgcngm[/MENTION]...thank you!
[One (M8) Android Development] Simply_S:
Idem ditto. Sorry for the late reply.

Been running happily (very happily) with no disconnects since last Saturday when I flashed the experimental version.

I'm no expert, in fact about as far from an expert as you can get, but if there's anything I can do to help find out what's wrong with NFC let me know

You deserve to get to a stable build
[One (M8) Android Development] wushi8:
Hi, I am using NFC every day,and I have report bug about NFC in #115 floor,and I am very glad report any bug and logs to you.

NFC bug:

M8D can normal read BEIJING public transportation card money. But M8D+NFC SIM can't use in BEIJING subway and bus, I have test a lot of times in cm-12.1-20150926-NIGHTLY-m8d.zip.

can you know NFC SIM? NFC SIM is a sim card with nfc, NFC SIM+M8D can insead public transportation card.

my english is so pool ,sorry!

my device:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.15.30.0303

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HC49GMY00723

(bootloader) imei: 351565060941876

(bootloader) imei2: 351565060941884

(bootloader) meid: A1000037D2B4F2

(bootloader) product: m8_dwgl

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B41000

(bootloader) cidnum: HTCCN702

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: ec89ae73

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[One (M8) Android Development] bgcngm:
Really?!? :confused: Is embedded NFC working on m8dwg? Could you please take a logcat filtered by 'NFC'? Should be something like this.

I'm sorry, but I can't do anything about the issue of the SIM with NFC. As you see, I don't even know how to fix NFC on m8dug. :(
[One (M8) Android Development] wushi8:
yes,if I hold a public transportation card near back of phone,I can hear sound ,and I can see balance! But NFC SIM can't use in subway.

logcat:

I/NfcService( 1032): Enabling NFC

D/NFCJNI ( 1032): Start Initialization

D/WirelessSettings(25295): onPreferenceTreeClick: preference=NFC 允许手机在接触其他设备时交换数据

D/StrictMode( 1313): Wrote violation #1 of 2: 14740 bytes

D/StrictMode( 738): Wrote violation #1 of 2: 16784 bytes

E/NFC-HCI ( 1032): Could not open /vendor/firmware/libpn544_fw.so or /system/lib/libpn544_fw.so

W/ActivityManager( 738): getRunningAppProcesses: caller 10063 is using old GET_TASKS but privileged; allowing

W/NFC ( 1032): Firmware image not available: this device might be running old NFC firmware!

D/NFCJNI ( 1032): NFC capabilities: HAL = 8150100, FW = b10129, HW = 620003, Model = 1, HCI = 1, Full_FW = 1, Rev = 41, FW Update Info = 0

D/NFCJNI ( 1032): phLibNfc_SE_GetSecureElementList()

D/NFCJNI ( 1032):

D/NFCJNI ( 1032): > Number of Secure Element(s) : 2

D/NFCJNI ( 1032): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef

D/NFCJNI ( 1032): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]

D/NFCJNI ( 1032): phLibNfc_SE_GetSecureElementList(): UICC detected, handle=0xabcdf0

D/NFCJNI ( 1032): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]

I/NFCJNI ( 1032): NFC Initialized