yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] hoangphamvm:
Is ota update work thanks
[One (M8) Original Android Development] LenAsh:
Moderator Note: Clean up - This thread is not the place to discuss the availability and costs of uSD cards...
[One (M8) Original Android Development] dnkjordan:
I was having GPS issues as well but, for some reason, your file didn't fix my problem. I also tried editing the conf file directly to replace UMTS with CMA and that didn't work either. In the end, I booted into GPE and got a GPS fix, then copied the gps.conf file from GPE and used it in CM 12.1. All good now.

Another endorsement for using multirom!

---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------

Is sweep to wake working for anyone? Mine will wake to the lock screen requiring an extra sweep to open. Minor inconvenience but I liked the feature in sense ROMs that allowed us to sweep up and bypass the lock screen, going straight to home.
[One (M8) Original Android Development] dasx86:
Looks like there might be a fix for this Bluetooth issue

https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-65819
[One (M8) Original Android Development] It IS Lupus:
What is the recommended firmware for lollipop? i'm currently on hboot 3.19.0.0000
[One (M8) Original Android Development] raneyden:
You should be good. I reverted to stock and pulled the OTA updates before I moved to CM 12.1, and I'm on hboot 3.19.0.0000, radio 1.12.20.1211, OS 4.17.605.5. Everything in CM has been working well.
[One (M8) Original Android Development] MacFett:
I have always had GPS issues with my m8 unless I'm on stock. I have had a gos.conf file I made on my usd card and I copy it over every time I flash.

This problem for me has gone back to cm11.
[One (M8) Original Android Development] garciaomar0203:
Cannot connect to the LTE network

When I am on wifi and get off of it I can't connect to the LTE network. I can't even get 2g or 3g. I have to restart my phone without the wifi on to get it to work. Any fix?
[One (M8) Original Android Development] debianmain1:
What I do is goto Mobile networks-Network operators-Choose automatically & that "generally" restarts my service -not every time, but its worth a shot.
[One (M8) Original Android Development] garciaomar0203:
I don't have that option I'm on Verizon ?
[One (M8) Original Android Development] raneyden:
Have you tried a full wipe and flash? I'm also on VZW, and I had a few connectivity issues when I dirty flashed from CM11 to 12.1; I eventually ended up doing a full wipe, updating my radio firmware to 1.12 (I think 1.16 is available now as well), and only restoring user apps from Titanium. It took a little time to get everything how I liked it again after the full wipe, but my wifi/LTE have been solid since.
[One (M8) Original Android Development] TheMabaet:
How to customize so that:

1. I can shrink the navigation buttons a bit like in Sense Toolbox?

2. Remove the root(#) symbol on the status bar?

3. Reduce the vibration strength?
[One (M8) Original Android Development] MacFett:
In developer options change root access to none.
[One (M8) Original Android Development] alien44:
When I updated CM to cm-12.1-20150513-NIGHTLY-m8 via CM updater, my phone get bootlop, when I try flash it again, twrp can't mound /data. I reflashed twrp, and nothing... Next try to fix data, using this tutorial: http://android-revolution-hd.blogspot.de/2013/10/fix-data-htc-one.html and nothing also.... Someone have the same problem with 13.05?
[One (M8) Original Android Development] garciaomar0203:
I haven't ever updated my radio firmware. Can you tell me where I can find this firmware?
[One (M8) Original Android Development] WoodmanMN:
I have an ATT HTC One M8, on the 3.19 bootloader, and using the stock Sense with root and TWRP installed everything works fine, Bluetooth, wifi, etc. I am not new to CyanogenMod, been using it since CM7 on an old Barnes and Noble Nook Color, but I am having all kinds of trouble with my bluetooth on all of the CM12.1 roms. I use my Plantronics PLT_M165 constantly, it attaches to my personal phone (ATT LG-G2 running CM12) just fine, and it attaches to my M8 under stock root fine, but when I go to CM12.1, I lose bluetooth completely after leaving the phone powered up for 12 hours or so. The bluetooth is turned off on the phone, and I cannot turn it back on, the switch just bounces right back to off. If I restart the phone, I can pair back up for approximately 5 minutes, and then bluetooth will once again turn itself off. If I power the phone off, then power it back on, I get the same result.

I am not running any third party kernels, no modifications other than running official CM12.1. I know it's a nightly, so it is by nature unstable, but does anyone have a workaround other than running stock Sense rom? I see a few others have similar issues with their phones in this thread, but haven't found any resolutions yet.

Other than the Bluetooth, the rom runs great on my phone. No issues, no lockups, just the bluetooth, which I need for work.

Thanks.

-Edit

Found an earlier post about clearing cache/data on the Bluetooth, I will try that. Also have been doing clean flashes of latest nightlies, I flashed 5/12 last night, but I see 5/13 has bluetooth changes, so I am attempting that now.
[One (M8) Original Android Development] benj!:
Getting System UI force close loops after 1305 update. Might be worth giving this one a swerve! :)
[One (M8) Original Android Development] chappellkm:
I second that. Went back to 5/12, will try again tomorrow.
[One (M8) Original Android Development] WoodmanMN:
I got that as well, went to recovery, cannot read or wipe data, system, etc.

And of course my backup was on internal storage...
[One (M8) Original Android Development] benj!:
Hmm, that's weird. Mine was fine, was able to reflash 1205 no problem.
[One (M8) Original Android Development] WoodmanMN:
Yeah, seems to be an HTC issue. Found a tutorial on how to fix it, but it's not working at this time. Kind of stuck. A few posts above mine is another person with a similar issue.

I am on ATT, what carrier are you running?
[One (M8) Original Android Development] benj!:
Mine's GSM. Haven't looked at the other fix, but can you reflash an RUU?
[One (M8) Original Android Development] WoodmanMN:
This fixed it for me, similar to what your link did, but "fixes" the data partition. All my data is intact even.

---------- Post added at 11:53 AM ---------- Previous post was at 11:53 AM ----------

I found a similar fix, see above. Thank you though.
[One (M8) Original Android Development] MacFett:
Use the RUU updater here:

http://xdaforums.com/verizon-htc-on...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
[One (M8) Original Android Development] JustMyUserName:
I tried the mkfs and fsck methods and I'm still unable to mount my data partition. Can anyone offer some help to get my data partition back? It would be greatly appreciated.

---------- Post added at 11:23 PM ---------- Previous post was at 10:52 PM ----------

Nevermind I was able to fix it myself. In case anyone else continues to have issues with the data partition not mounting here is what I did to fix it.

I downloaded this file - http://www.androidrevolution.org/downloader/download.php?file=fsck.ext4

I booted into to recovery and verified adb connectivity. I tried the steps on http://android-revolution-hd.blogspot.de/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html?m=1

Which did not work for me. I ended up having to do the following.

1. adb push fsck.ext4 /tmp

2. adb shell

3. chmod 777 /tmp/fsck.ext4

4. /tmp/fsck.ext4 -fn /dev/block/mmcblk0p49 (that reported several errors for me)

5.. /tmp/fsck.ext4 -fy /dev/block/mmcblk049

Using the "y" switch forced the script to fix all the errors it found. Afterwards in the shell I was able to run the mount /data command successfully. I then rebooted into recovery again and the data partition was mounted and intact. I then performed a factory reset and re-installed the rom/gapps/supersu and rebooted. The ROM booted successfully and I was able to access the files on my internal storage again.
[One (M8) Original Android Development] L1nuz:
So, I installed cm12.1 some builds ago and everything went fine.. except 4G LTE won't work. If I change to 3G preferred it connects to data network but with LTE preferred it only displays "!"

Since I haven't updated the phone since last year, I decided to flash the latest GPE RUU to get the latest firmware etc... done

Flashed to cm12.1 from there and the LTE was working for couple of hours and then it won't turn on again. When I revert back to GPE.. LTE is working like it should...

Since I can't be bothered anymore.. I decided to install the latest cm12 build but it can't be downloaded from the website.. anyone have one of the latest 12 build that I can have plz?

anyone else having 4G (LTE) issues?

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.23.213311491.A13G

(bootloader) version-main: 4.04.1700.4
[One (M8) Original Android Development] benj!:
LTE working fine here. Same hboot and radio versions as yours

Anyone taken the plunge with 1405 yet? Is the System UI FC fixed?

---------- Post added at 10:15 AM ---------- Previous post was at 10:08 AM ----------

To answer my own question: yes, it's fixed :P
[One (M8) Original Android Development] jschill31:
Hello,

So has anyone had success with getting BT to stay connected by this method? I do not think this is the issue we are having with the M8, I think ours is more kernel related. It would be nice to see some progress considering the CM tree affects so many custom roms.

Cheers
[One (M8) Original Android Development] Keithn:
I've said it before but I'm having zero issues with it as is.

The issue on the M8 seems to be related with device specific code in mix with firmware. I'm using the latest firmware with relevant pieces from 4.4.

Sent from my One M8
[One (M8) Original Android Development] benj!:
+1, I've not had any issues staying connected to bluetooth speakers or android wear watch
[One (M8) Original Android Development] jschill31:
Hello,

You are correct in that it does seem to be device specific in both our M8's & specific radio interfaces. The BT issue seems to be specifically related to certain indash radios and the A2DP codec. I have not seen any issues with BT headphones or staying connected to my smart watch. Also our M8's can have up to a 10% tollerance variance depending on when it was built. This all makes it difficult to track down, and also why there are some reporting no issues while others find it not usable. I am certainly interested in hearing if anyone has tried replacing the file referenced in the earlier post? I think all of us are using the same firmware but our internal components can be slightly different. This has been the case for every Android device I have owned in the past 5 years.

Cheers
[One (M8) Original Android Development] Keithn:
If it helps, I don't use wear or BT headphones, I only use BT in my car. I did have issues using the newest firmware (VZW) that most people are on. I had to use pieces from 4.4 or it would not stay connect properly and playback would stop etc. Figured it might be worth a try if the fix for the OPO doesn't work for you.

I've never seen anything with the SOC change on the same model device. Storage modules were as much as I've seen differ. Not saying you are wrong I've just never seen it.

https://drive.google.com/folder/d/0B46-y8opd1H-UThaMVZMVjhPWWc/edit here are the stripped down fw I've been using.

Sent from my One M8
[One (M8) Original Android Development] jtkes693:
Anyone still getting system ui fc on the 5-14 build
[One (M8) Original Android Development] riaan0010:
Did u get any
[One (M8) Original Android Development] benj!:
No, working fine now
[One (M8) Original Android Development] jschill31:
Hello,

I will take a look at it this weekend, traveling and away from my main PC. My reference to tolerance difference is within the same board and components. We have the same board and such, it is more a production thing. This is why some can peg their chip and others overheat. Same with sensors, our phones are the same but the sum of the whole makes up the tolerance difference. Typically this never is an issue
[One (M8) Original Android Development] jtkes693:
Yeah I figured out the blisspopkernel I had been using before 05-12 build was causing system ui fc for me. Stayed with stock kernel and problem was fixed for me
[One (M8) Original Android Development] Keithn:
Okay I understand. I guess I misread/misunderstood what you were saying at first. Hopefully that helps.

Sent from my One M8
[One (M8) Original Android Development] MacFett:
I know you said you fixed it, but had you tried the repair data partition in twrp? With my old m8 every second or third time I'd flash my data would become corrupt and I'd have to use that option to fix it, as such I didn't do much flashing with that one. This m8 hasn't had that problem yet.
[One (M8) Original Android Development] donlu30:
Keith, so in what order should these be applied. Probably doesn't matter, but what the heck....
[One (M8) Original Android Development] Keithn:
There isn't an order. The 5.1 is the same as in DigitalHigh's GPE thread, I made one for 4.4 and 5.0 using the same parts of the firmware.

I was on the most up to date firmware then flashed the 4.4 file in that folder. The others were mostly so I could swap back if I needed/wanted to.

Sent from my One M8
[One (M8) Original Android Development] JustMyUserName:
Yes I tried the repair data partition it would just continue to tell me it couldn't mount /data.
[One (M8) Original Android Development] jschill31:
Interesting...so I also missunderstood you as well. Are you saying that you combined the 4.4 firmware with what is needed from the 5.0 items (touch screen and wifi)? There were some changes to BT on the 5.0 firmware as well but is this what is causing the issue? So is your 5.0 pack the 5.0 firmware plus the 4.4 BT bits? This actually makes sense...I have not done anything with the 5.1 firmware floating around since we do not have official. Please indicate what type of indash you are connecting to and if it does audio, phone and phone book. I at first thought the issues were because of the phone book hand shake but on my Kenwood I can turn off each piece and only do audio which still causes mine to panic.

Thanks
[One (M8) Original Android Development] JustMyUserName:
Could you possibly point me to a link for flashing instructions? Or do I just put the corresponding .zip file on my sdcard and boot into bootloader? Or is it flashed through fastboot? Thanks for the info, the BT in my Mazdaspeed 3 has been cutting out every 20-30 seconds since I switched to 5.0 and above.
[One (M8) Original Android Development] Keithn:
Mine is an older head unit with a BT adapter so it doesn't do phone book stuff. I do have phone/audio out though and it was giving me issues on the newer firmware.

The firmware I linked isn't a full firmware. It wont affect the cell radios, adsp, hboot etc. if you look in the zip you can see. It is just select pieces from that firmware as is the 5.1. I started on the most up to date firmware then flashed the 4.4 from the folder on top.
[One (M8) Original Android Development] JustMyUserName:
My M8 has had the problem sporadically, but normally a few reboots would fix it. This time it just would not come back and the repair function in TWRP just kept repeating the could not mount /data error.
[One (M8) Original Android Development] Keithn:
You could do it using the sdcard just remove the version number "44" so it should be called 0P6BIMG.zip. hboot looks for that file on the sdcard and will attempt to flash if it sees it.
[One (M8) Original Android Development] JustMyUserName:
Do I want to flash the 5..1 zip first? I'm on a Verizon M8 if that makes any difference.
[One (M8) Original Android Development] Keithn:
Nope. It would actually be pointless since they contain the same files just from a different set of firmware. They are noted by the numbers in the front of the file name. I only had those in there so that if I wanted to use the 5.1 or the 5.0 I could flash back over the 4.4 parts with them easily. Hopefully that explains it better.
[One (M8) Original Android Development] JustMyUserName:
So if I'm understanding it correctly the files flash only the bluetooth and other related portions of the firmware to the version level indicated by the filename? The idea being if I'm having bluetooth issues on my build of 12.1 I could flash the 4.4 file and possibly get my bluetooth working correctly again until a more permanent fix is available?
[One (M8) Original Android Development] WoodmanMN:
This makes sense actually. My old M8 had no issues at all with bluetooth on cm12. I cracked the screen and sent it in for repair to HTC, and the one I received has bluetooth issues with cm12 and 12.1. If I run stock root, no problem. So my replacement must be using an older, refurbished main board, which accounts for the sudden change in behaviour.
[One (M8) Original Android Development] Keithn:
That is essentially what I tried to do. I couldn't find details of each file was specifically so I looked to see what firmware parts were required to make WiFi, BT, etc. work right on specific versions of GPE (so 5.1 for GPE 5.1 etc) and pulled those from the 4.4 firmware. It may contain something you may not specifically need, but it definitely has the BT related parts and fixed the BT issues I had. If it doesn't help you too, then can always go back to the 5.0 firmware and be where you started.
[One (M8) Original Android Development] JustMyUserName:
Unable to access microphone

Just wanted to reach out and see if anyone else is getting errors with Google Now/Ok Google functionality. I can't get the search to open by saying "OK Google", and when I open the search manually it shows what I said to search but then gives an error saying it can't access the search results. If I try to do the "OK Google" voice training, I get an error stating "Unable to Access Microphone. Please reboot your device." I'm running the 05/14/2015 nightly build for the M8. My M8 is a Verizon if that matters at all.
[One (M8) Original Android Development] Walhalla:
has someone else tried the 4.4.4 firmware for fixing his bluetooth issues? Has it worked them out?
[One (M8) Original Android Development] MacFett:
I'm back on the 28 APR nightly and have no problems with my Bluetooth.
[One (M8) Original Android Development] jcole20:
Edit: nevermind

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Original Android Development] WoodmanMN:
I'm planning on getting it on mine this week. Anyone know if you can flash s-on, factory unlocked, or do I have to relock firmware or pay to go s-on.
[One (M8) Original Android Development] debianmain1:
I'm S-off & factory unlocked & it works very well...... My wifes M7 is S-on & factory unlocked & working very well there....
[One (M8) Original Android Development] dreaming1reality:
Everybody just get on SkyDragon v9 w Sense 7.
[One (M8) Original Android Development] MacFett:
Is that a rom? I personally dislike sense very much and really like cm. For me, cm is working just fine.
[One (M8) Original Android Development] paul4762:
Anyone else having issues with some calls not coming in as well as group messages not downloading? I tried clean installs a few times but I'm stuck with no idea what to do.
[One (M8) Original Android Development] ECloud7:
I am having the exact same issue. Everything else in the rom is running smoothly except I can't receive calls. I tried some clean installs too with no luck.
[One (M8) Original Android Development] paul4762:
I set the network to 3G and it works fine. So there's an issue with the LTE. You might want to try 3G and see if that works for you as well.
[One (M8) Original Android Development] ECloud7:
When you set it to 3G does that take away the ability to use LTE?
[One (M8) Original Android Development] paul4762:
You can change it right back. If you go to settings then mobile networks you will see preferred network type
[One (M8) Original Android Development] ECloud7:
Oh got it so you can put it to 3g then change it right back and you receive calls for good? Or do I have to leave it in 3g to take calls and put it to LTE when I want to use LTE?
[One (M8) Original Android Development] jcole20:
So cm's stability has suddenly gone down a lot? Seems everyone is pointing to issues. Every time I've used recent builds (haven't updated in about a week) it's been solid except for sound.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Original Android Development] ned4spd8874:
T-Mobile + 12.1 (5/16 Nightly) = No Mobile Data

I just installed the 5/16 nightly this weekend; things were fine until today. All of a sudden, I'm getting an explanation on my mobile data signal. When I disconnect my wi-fi I have no mobile data at all. I can make phone calls however. Any idea on what's going on?

I did a new/fresh install. I came from VenomROM and wiped my phone before flashing Cyanogenmod.

EDIT: After playing around and trying every setting combination I could think of, I finally got it working after changing the APN to IPv6. Weird that the default setting wouldn't work though.
[One (M8) Original Android Development] Budske:
bluetooth issues

im having problems with the bluetooth.

it gets disabled even when im not using it and i cant re enable it, i have to force close bluetooth share to make it work, i cleared all the data of the bluetooth share app and it still happening.

im coming from a GPE rom (LolliGPE) and had no problems there. anyone know how i can fix this??

(my car doesnt have any contact sharing and i dont have anything connected to the phone via bluetooth)

i dont know exactly how to make a logcat, i downloaded catlog, but dont know what filter to use
[One (M8) Original Android Development] jcole20:
The exclamation on aosp means no mobile data. Data and cell service are different. Glad you got it worked out.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Original Android Development] genheals:
GPS, battery

I'm on the VZW M8 running the 5.0 stock firmware...anybody having issues with GPS lock? Also, the battery life is pretty horrific (8 hours max light use). Anybody experiencing similar concerns?
[One (M8) Original Android Development] shaunhoop1981:
I have come across from arhd and I am very happy. I have a international m8 latest firmware running 18th of may nightly, everything is smooth only issue was with media player two nightly ago and flash player in regards to browser but now is all good :)
[One (M8) Original Android Development] Keithn:
Usually you have to go back to sense and get a lock before flashing anything else if you are having issues with the GPS locking.

Sent from my HTC One_M8
[One (M8) Original Android Development] WoodmanMN:
It's an issue on a small percentage of m8's. No fix as of yet. You can flash a modified 4.4 firmware that has earlier bluetooth if you have s-off. Go back a few pages for the link.
[One (M8) Original Android Development] PlagueBoy:
I had this issue with my AT&T M8. I tried some clean installs and even SkyDragon GPE and still couldn't receive calls. After converting to GPE firmware, still having the issue, I realized that I was overlooking something, SuperSU.

In the end I was able to start receiving calls again when I was on GPE firmware and didn't install SuperSU but, instead, used the built in Root (Privacy Guard). Not sure if you are on AT&T but those two changes were the only two that made it possible for me to receive calls again.

Ever since I did the conversion and stopped installing SuperSU (yes I went back to the AT&T official firmware and still had the issue) my phone has been working properly again. I'm not implying anything about SuperSU, as it is an excellent app, just saying that it wasn't working with my setup for some reason.