yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] formula91:
ART is working great for me so far minus some slowly updated apps. No conclusions about battery life or performance, however.

Quick question, it seems that tap to pay in conjunction with Google Wallet is not working on CM11. As some of you may know, KitKat no longer requires a secure element to allow paying with NFC anymore because it has host card emulation built in. This is the most exciting thing about upgrading to KitKat in my opinion!!

I remember tap to pay being available for CM11 nightlies way back in January... Why is it gone? Was it ever working in the first place? How can I get it working again? Why is it that when I boot into Sense 5.5 (ViperROM 5.0.0 w/ ElementalX Kernel), tap to pay is available, but it is not on CM11?

At first I thought it's because Google Wallet thought that my phone and CM11 were international variants and therefore unusable (US Only), but it doesn't seem like that's the problem.

Can anyone possibly give me some answers?
[One (M7) Original Android Development] tiny4579:
The AOSP NFC statck doesn't have the proper code for HCE. GPE and sense have it since they don't use the open source NFC NXP code.

It was removed because it was determined it doesn't actually work in AOSP. Can you confirm that Tap and Pay actually worked on earlier builds and not just showing up in settings?
[One (M7) Original Android Development] formula91:
Thanks for a prompt answer. That's a real shame to hear. From the sounds of it, it looks like they won't figure out a solution any time soon. I hope they figure it out. I assume the issue with the open source stack is that I causes problems with aosp roms. That or in typical cm11 fashion, they want to code their own solutions.
[One (M7) Original Android Development] dlbarron:
I get the same thing usually when connected to my car with bluetooth.
[One (M7) Original Android Development] sectorek:
dont know why but my battery life sux! :(
[One (M7) Original Android Development] sabret00the:
Makes sense as it happens for me when the aux lead is plugged in.
[One (M7) Original Android Development] tiny4579:
A forewarning:

You may not want to flash 3/4 when it's built. The qcril merge happened today for CM11, and that seems to have broken RIL for m7. I've let the maintainers know and they will be looking into it but no guarantees a fix will be merged prior to the next nightly.
[One (M7) Original Android Development] tjsooley:
I have no issues on the newest nightly
[One (M7) Original Android Development] tiny4579:
The merge was after the current nightly that's why there are no issues. I'm just trying to warn so we don't see a bunch of people reporting issues on the next build. I hope it's fixed tonight but we shall see.
[One (M7) Original Android Development] sectorek:
Any idea what is going on?

I'm loosing like 25% or even more battery over the few hours at night.
[One (M7) Original Android Development] tiny4579:
Can't tell for sure with just this screenshot but Android OS is a general category. My guess would be a partial or kernel wakelock. Try BetterBatteryStats to get more details.
[One (M7) Original Android Development] sectorek:
Im trying BatterBatteryStats. If it's kernel wakelock is there something i can do?
[One (M7) Original Android Development] tiny4579:
Usually not but it also depends on the wakelock.
[One (M7) Original Android Development] sectorek:
so here are next screenshots.

10% in 30mins...?

http://i.imgur.com/dxAE9TC.png

http://i.imgur.com/NqtrTwE.png

Is there something I can do? And why I have so high battery usage when this rom is working for others?
[One (M7) Original Android Development] tiny4579:
That is pretty high. Msm_hsic_host is modem related. Do you have an app trying to sync data and failing?

Also check partial wakelocks.
[One (M7) Original Android Development] sectorek:
Well for testing I turned off e-mail synchronization, but I don't know how to check application logs...

Here are my Partial wakelocks.

http://i.imgur.com/0HYvH8Q.png
[One (M7) Original Android Development] cschmitt:
[MENTION=1904386]sectorek[/MENTION], I have a high msm_hsic_host wakelock as well, and partial wakelock appears to be google services or google search box. I'm seeing 6.5% / hour drain overnight in deep sleep. Usually runs about 3 to 3.5% which is a pretty good indication that its radio related.

Started sometime after 02/27 build and first appeared on 03/02 build (didn't build anything in between.)
[One (M7) Original Android Development] sectorek:
Thanks for answer cschmitt. At least I'm not alone with this problem, but anyway it's nothing good either. If nothing will change my battery will last for maximum 10 hours because every hour I'm loosing 10%. That sux!

Now I wonder what can I do to fix this battery drain. Maybe move to other ROM? Maybe should I try other Kernel?
[One (M7) Original Android Development] cschmitt:
Something has changed in one of the recent nightlies that has caused it. We just need to narrow down the cause and fix it.

I'm going back to 02/27 build for the day to verify that sleep idle is ~ 3.5% an hour and will begin looking forward for commits that might be the cause.
[One (M7) Original Android Development] sectorek:
cheers! so I'm looking forward for your fix! :good:

Edit:

I'm using version from 02/26. So I think *battery drain commit* was made even earlier, but maybe I'm wrong!
[One (M7) Original Android Development] cschmitt:
Thanks for the info, maybe it is earlier than 2/26. As for a fix, don't hold your breath-- I have a day job.
[One (M7) Original Android Development] sectorek:
We all do ;) No problem. At least there is a light in the tunnel :good:
[One (M7) Original Android Development] cschmitt:
Which radio are you on?

4T.24.3218.09 here.
[One (M7) Original Android Development] Thyria:
Is there a fix coming in for the reboot problems? I'm looking forward to it since one week. :(
[One (M7) Original Android Development] tjsooley:
I would try a factory reset. I had some random reboots about 3 weeks ago and a factory reset did the trick
[One (M7) Original Android Development] Pard0ned:
What are people's opinions then on the m3 release? All good? Anyone having any issues or anything?

I just flashed this myself on an unlocked and soffed HTC one last night. Only thing I've really noticed is that going from, say tapatalk back to the home screen, there's a bit of a delay.

Everything else seems to work fine for me. Although I'd be interested to read other people's experiences of this. ?
[One (M7) Original Android Development] cschmitt:
Went back to 02/27 build, sleeping like a baby now: 3.3% per hour over last 1.5 hours compared to 6.5% on 03/02 or later.

Same radio, same data partition (just dirty flashed back) so I'm fairly certain its something between the last commit of my 02/27 build: http://review.cyanogenmod.org/#/c/59909/ and last commit of my 03/02 build: http://review.cyanogenmod.org/#/c/60412/ There's only 13 changes in gerrit between them, shouldn't be too difficult to figure out.
[One (M7) Original Android Development] sectorek:
If this is info from About phone / Baseband version then this is: 4A.17.3520.14 :)
[One (M7) Original Android Development] psychomaniac189:
So you mean the 5th? Cuz ROMs say they are built on the 5th but if you check the change log all the changes are from the previous date. Am I correct? I'm seriously not sure
[One (M7) Original Android Development] tiny4579:
I mean the 3/4 nightly but the date on AOSP ROMs is based on UTC usually which is why night builds show the next date. In this case i mean the 3/4 build which popped up late last night shortly after midnight.
[One (M7) Original Android Development] tiny4579:
I'd look at telephony first if the drain seems quicker:

https://github.com/CyanogenMod/android_packages_services_Telephony/commits/cm-11.0

https://github.com/CyanogenMod/android_frameworks_opt_telephony/commits/cm-11.0

qcril was merged recently so that may have an impact.
[One (M7) Original Android Development] cschmitt:
Did a sanity check : factory reset and flashed 0304 official. Sleep idle seems to be fine. I've had weird things happen before after 30 or 40 dirty flashes, must have been the case here as well -- at least I can't reproduce the battery drain.
[One (M7) Original Android Development] AJ:
quick question to anyone using ART :

how are you guys made the switch ?

when i switch i get bombarded by error massages & can't do anything .
[One (M7) Original Android Development] qixiixiq:
3/4 nightly

Nightlies were running great until today. After flashing ive done full factory resets as well as reflashing rom and latest PA gapps but with every boot i am getting stuck in the "Unfortunately Phone has Stopped" error - any ideas about this?

===========

Edit: Wiped all data, factory reset twice and went back to 2/28 nightly and the device seems to be fine now.
[One (M7) Original Android Development] sabret00the:
No errors here.
[One (M7) Original Android Development] AJ:
take a look , it's the same massage over & over again , it doesn't go away ,

i can barely switch to dalvik
[One (M7) Original Android Development] sabret00the:
You have a bad GApps, upgrade and you should be fine. http://wiki.cyanogenmod.org/w/Google_Apps
[One (M7) Original Android Development] AJ:
thanks man :good:
[One (M7) Original Android Development] sabret00the:
Just seen that RC1 is due to be released on Friday. I'm not sure which kernel they're gonna use.
[One (M7) Original Android Development] pavik62:
Where information?
[One (M7) Original Android Development] sectorek:
I'll try to flash new version. Thanks for help anyway!
[One (M7) Original Android Development] tiny4579:
Look at my post earlier. I warned 3/4 would be an issue.
[One (M7) Original Android Development] tiny4579:
How is it working for you I'm curious since the errors I was getting in my build late on 3/3 were related to the ril merge as acknowledged by the CM team?
[One (M7) Original Android Development] psychomaniac189:
Weird. My phone seems to be running fine. I'm running 3/04.
[One (M7) Original Android Development] sabret00the:
20140305 is out.
[One (M7) Original Android Development] pigr8:
where did you get this information from?
[One (M7) Original Android Development] qixiixiq:
Did you have art enabled? It was enabled on my phone when everything went haywire after the 3/4 installation.
[One (M7) Original Android Development] sabret00the:
One of the maintainers let slip in another thread. I'm not sure if it'll happen, but he said Friday, so let's hope it's true as that means it'll be all hands on bug fixing.
[One (M7) Original Android Development] psychomaniac189:
No and I never plan to either.
[One (M7) Original Android Development] tjsooley:
No issues on 3/5 nightley. On Dalvik
[One (M7) Original Android Development] snachez:
Anyone able to offer advice on how to remove the "emergency call" button on the lockscreen ?
[One (M7) Original Android Development] pavik62:
Decompile framework-res.apk. framework-res.apk/res/values/strings.

Find the line:

<string name="lockscreen_emergency_call">Emergency call</string>

Change to:

<string name="lockscreen_emergency_call"></string>

This must be done in the folder for your language. Russian example in the folder value-ru. That can be set via Recovery
[One (M7) Original Android Development] qixiixiq:
ART

What do you have against ART? :confused: i didnt see a huge boost in performance with ART enabled but battery life was certainly better.
[One (M7) Original Android Development] sabret00the:
After clearing data on the email app, battery drain is down from 19.5% an hour to 6.5%
[One (M7) Original Android Development] psychomaniac189:
All I hear are problems like you had said. I need a phone to work 24/7. No apps force closing. I'm new to ART.
[One (M7) Original Android Development] tiny4579:
[MENTION=4513061]cschmitt[/MENTION],

This could help with radio wakelock issues possibly:

http://review.cyanogenmod.org/#/c/60683/

I'm really not sure why some are and others aren't having phone crash on the 3/4 build. Maybe I need a data wipe if it still happens.
[One (M7) Original Android Development] tiny4579:
Very few apps are broken on ART, but ART is still in a sort of developmental stage and not 100% ready for primetime. When or if ART gets Google's blessing, it would then be supported by CM.
[One (M7) Original Android Development] cschmitt:
A full reset fixed the battery drain issue for me. Didn't experience any issues on 3/4 and 3/5 after that.

Going from 3/4 to a previous build did cause acore and dialer crashes, probably because of the Google Dialer commit.
[One (M7) Original Android Development] pavik62:
Yes, in Russia we all complain Google Dialer commit. Installing 3/4 and 3/5 all wipe
[One (M7) Original Android Development] qixiixiq:
Google dialer issue?

Any idea what the disclaimer on the PA Gapps page is about warning that CM is especially vulnerable to issues with the dialer?

The dialer worked great with all night lies prior to 3/3. Any idea about a workaround? I want to test the latest night lies but really need that dialer.

Thanks
[One (M7) Original Android Development] tiny4579:
To fix dialer i just had to wipe contacts storage (com.android.providers.contacts).

The phone crashes I'm having are only on my personal builds as nightlies are working fine. I'm trying to figure that part out.
[One (M7) Original Android Development] cschmitt:
I've found that clearing ccache and rebuilding has mysteriously resolved things when I've encountered weird issues with my builds.
[One (M7) Original Android Development] tiny4579:
This might have done the trick as I was trying out stable/cm-11.0 earlier.

repo init -b cm-11.0 -m default.xml to make sure everything was switched back to the latest. I didn't rebuild ccache but did a clobber build. Back in business.

On another note, track metadata not working I have a feeling is related to a merge early on. It doesn't seem that anyone has time to fix it so I've been looking at what I might be able to revert to pinpoint the cause.
[One (M7) Original Android Development] cschmitt:
Just tested with my MW600 and track data is displaying (on 3/6.)
[One (M7) Original Android Development] tiny4579:
Has it always worked for you on CM11 though? I've heard reports of people with car units that have worked fine the whole time on CM11 and others where it didn't work at all. It depends on the features I guess of the car unit. If this is now working with the latest nightly for you, then awesome.
[One (M7) Original Android Development] cschmitt:
If have a Sony MW600 headset that displays track data and I believe that it has always worked on CM11.

My car doesn't display track data, it's an older version of Sync and only displays 'Media Stream'.

BT streaming skips more frequently on the msm8960 kernel it seems.
[One (M7) Original Android Development] Jediritter:
Hello,

i just flashed the new nightly on a fresh unlocked HTC One.

I did change the display, due to my old broken display.

After the flash reboot, all I see is a grey screen after the HTC Logo.. does anyone know this problem?

This display worked with the original firmware.
[One (M7) Original Android Development] Thyria:
Factory reset didn't resolve the problem. Has anybody else this problem?
[One (M7) Original Android Development] tjsooley:
Strange, No issues on any nightly in the past 2 weeks for me.
[One (M7) Original Android Development] Thyria:
I'm getting this kmsg http://pastebin.com/niRmGNCz

Edit: updated. Wrong pastie first x(
[One (M7) Original Android Development] tiny4579:
Not sure the cause from the last_kmsg you have there. I think you're missing the reboot reason there. Try getting about 20 lines both before and after. I've had a reboot a while back and mine was modem/radio related. Are you on the latest radio available for your carrier or a recent radio?
[One (M7) Original Android Development] Thyria:
I just downloaded the new radio, goin to flash it in a minute. Appreciate it your help. Thank you.

Edit: Flashed. Going to take a look now how it develops. Will report back.
[One (M7) Original Android Development] alibabar1991:
i got this phone and i think its rooted or theres some fault google apps not downloading anything ? its openning when i slect the app to instal it doesnt downloads ??? whats the reason and can it be fixed or should get my phone back as i exchanged it with someone

. Phone is not doubt fast and camera is good but what do you say bro ??

thanks
[One (M7) Original Android Development] sabret00the:
Am I the only one that the spell check isn't working for? Talking about the red underline
[One (M7) Original Android Development] Pard0ned:
That's more than likely a Google play error.

Wipe dalvik and normal cache. Also, play store data and play services data.
[One (M7) Original Android Development] cschmitt:
Mi speal chack werks fime.

Seriously, that whole last sentence was underlined in red.
[One (M7) Original Android Development] sabret00the:
May be time to do a clean install for me then.

Actually wait, are you on ART?
[One (M7) Original Android Development] cschmitt:
Nope, still dalvik.
[One (M7) Original Android Development] sabret00the:
That could be the issue, I'll jump back over to Dalvik and see if the functionality is restored.
[One (M7) Original Android Development] sabret00the:
Even on Dalvik there's a problem
[One (M7) Original Android Development] cschmitt:
Just tested on ART and spell check is working here.
[One (M7) Original Android Development] sabret00the:
Do you know the app name? Maybe I can clear data? It's really not a good time for a full wipe for me.
[One (M7) Original Android Development] dansharpy:
Just flashed 17/3 nightley and still getting force close on com.android.phone is there any workaround for this yet or do I need to go back to 2/3?
[One (M7) Original Android Development] sabret00the:
Didn't you say it started after you tried to flash the Google dialer?
[One (M7) Original Android Development] tiny4579:
I was having this issue but only with self builds until I cleaned up my local build tree properly. I was able to flash the 3/3 and 3/5 nightly fine. I didn't test other nightlies after 3/2 since the merge since I mainly flash my own builds.

I still would get the force close but only when long pressing the LTE toggle (which isn't quite working yet to begin with).

Unfortunately, I'm unaware of a workaround. Do you have the same issue on a clean flash? Also, if you're familiar with adb, can you grab a logcat?
[One (M7) Original Android Development] ZeroCool11:
I have a problem with my phone, when i'm on a call sometimes the Proximity Sensor doesn't work and the screen starts pressing itself with my ear, so yesterday i turned off the alarm and i got up late :/ so does someone knows a fix for that??? i'm on CM11-20140227-NIGHTLY-m7 ... thanks
[One (M7) Original Android Development] Pard0ned:
Anyone using cm11 on the gpe firmware?

Just wondering if the GPE firmware is more suitable for aosp etc.

Anyone know?
[One (M7) Original Android Development] sabret00the:
GPE fixed some of the problems that this ROM was having.
[One (M7) Original Android Development] Pard0ned:
Like what? I just flashed the gpe firmware and already missing CM.
[One (M7) Original Android Development] sabret00the:
Flash CyanogenMod then. FIRMWARE != ROM
[One (M7) Original Android Development] Pard0ned:
Don't know what you're meaning. Should I have flashed cm before the gpe firmware?
[One (M7) Original Android Development] tiny4579:
Order doesn't matter. They are completely separate.
[One (M7) Original Android Development] Pard0ned:
Just gave the m3 release a go again. And it does seem smoother with the gpe firmware. Might just be placebo though. Is anyone else using cm11 with the gpe firmware?

Sent from my CyanogenModded HTC One
[One (M7) Original Android Development] sabret00the:
So it was M4 not RC1. Apparently CyanogenMod are just the slowest of all the vendors and I jumped the gun assuming stable would mean RC1, my apologies. Go grab the M4 release.
[One (M7) Original Android Development] nonmindo:
Anyone else experiencing really low Ringtone / Notification volume? I have it set to max volume and it is at least 1/3 quieter than it was on ARHD....like if its in my pocket on full volume and there is ANYTHING making noise going on when the notification comes through, I'll miss the call or text

3/7 nightly, stock CM kernel
[One (M7) Original Android Development] Pard0ned:
Doesn't appear to be out yet for m7. :(
[One (M7) Original Android Development] pigr8:
will be pushed soon
[One (M7) Original Android Development] :
M4 is on the way - this Weekend ?

Look at on the Feature/update list :highfive:
[One (M7) Original Android Development] Pard0ned:
It should be out later today really. The builds are getting pushed to the relevant servers now apparently.
[One (M7) Original Android Development] sabret00the:
I can't get past this bit on the Android Easter Egg, anyone else?
[One (M7) Original Android Development] pavik62:
Long press in the centre Android
[One (M7) Original Android Development] sabret00the:
Here's the CyanogenMod Easter Egg
[One (M7) Original Android Development] raydekok:
long time that i flashed cyanogen. how is batt. life? like the standard sense roms?
[One (M7) Original Android Development] tiny4579:
It didn't seem too bad to me. I didn't notice any skips both to and from work over bluetooth. You were using the default governor and performance profile, correct?

Also, for the track data issue in cars, I updated the JIRA ticket - CYAN-3154 - with a change that could be reverted to see if it could possibly fix it for us with this issue. I was having issues reverting it since there were a lot of changes to AVRCP after that commit and trying to revert broke the build.
[One (M7) Original Android Development] cschmitt:
I think I was using CFQ and ondemand, will try the defaults. The skipping does seem to be somewhat device dependent, it happens more frequently with my headset than in the car.
[One (M7) Original Android Development] superleeds27:
M4 is up.
[One (M7) Original Android Development] KillerBeaver:
M4 bootlooping for me when phone apk crashed. Has anyone else had this problem, or did I just get a bad download?
[One (M7) Original Android Development] superleeds27:
So far so good for me.
[One (M7) Original Android Development] KillerBeaver:
Are you using ART?
[One (M7) Original Android Development] cschmitt:
Same here, went back to 0307. Using ART.
[One (M7) Original Android Development] sweetnsour:
Using ART, but no crashes for me. Updated from the last snapshot (M3).
[One (M7) Original Android Development] KillerBeaver:
the MD5 matches. Maybe i'll download M3 and try updating to the M4.
[One (M7) Original Android Development] tiny4579:
It probably has something to do with updating from a nightly. I think M4 is still using the older kernel. If the database versions are older which can happen if it is built off an older state, the critical apps can crash resulting in an bootloop. I am using a nightly right now so I'm not sure if it's the M build or the upgrade path.
[One (M7) Original Android Development] cschmitt:
M4 may not have the Google Dialer commit, going back to a build that doesn't include it will cause acore crashes. A number of other devices are having similar issues with the build.
[One (M7) Original Android Development] tiny4579:
I was able to backtrack builds and fix the acore crashing by wiping contacts storage. The hint to do that was logcat pointed to a database version issue with com.android.providers.contacts.

Also, the Google Dialer commit as it shows on gerrit wasn't actually merged if you check the comments even though it says merged as status.
[One (M7) Original Android Development] Thyria:
Updated to latest radio. Still reboots. I don't get what it could be. Going to try another rom. :(
[One (M7) Original Android Development] tiny4579:
Can you try a last_kmsg again? Is it a soft or hard reboot?