yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] damccull:
Oh, I didn't know the issue was that serious. I thought it was just a one time thing. Any idea how to track it down? In still running victara cm12.1 and is he willing to help. I don't notice the problem really though. I'll reboot right now and check.
[X 2014 Original Android Development] felipevsw:
It usually happens after the device is on for a while, like later in the day, and after the battery is below 40%. But yesterday night the battery was ~90% and it was already yellow...
[X 2014 Original Android Development] damccull:
How yellow? Just a barely noticeable tint I'd need to compare to a piece of paper? Or obviously, easily recognizable yellow?
[X 2014 Original Android Development] ntmmtn:
Hello,I want ask you.

I get a XT1085,This is china ver of MOTO X 2014.

I want convert to XT1092 from XT1085 without gpt.bin & motoboot.img(I recognize this is not exactly XT1092, am I light?)

And then flash CM12 or CM12.1.

rom I have is

XT1085(this is rom on my MOTO X 2014)

LXE22.92-18

5.0.2：GPT=2,Bootloader=0×6012

XT1092

RETGBALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml.zip

5.0.0：GPT=2,Bootloader=0×6011

Is this possible to do it? any brick possible?

Xt1085 Red & Gold is Cool. But Chinese rom is there are any good cause no google services.

So please tell me. If you know about.

Thank you!
[X 2014 Original Android Development] felipevsw:
Hurt-your-eyes yellow! Everything that's supposed to be white. And it gets yellower as the time passes.
[X 2014 Original Android Development] crpalmer:
Does this start happening somewhere around sundown? What you describe as it, it sounds rather like you enabled automatic night and day adjustment in live display...
[X 2014 Original Android Development] dg4prez:
That's what I was thinking. I'll betcha that's it.
[X 2014 Original Android Development] felipevsw:
Come to think of it, I believe I had enabled that.

I'll install it again tonight and pay attention to this setting in particular, then I'll keep monitoring it to see if it happens again when it's off.

Thanks for pointing it out! I'd hate to leave CM.
[X 2014 Original Android Development] dg4prez:
You can adjust the temperature settings so that you get the effect without so much yellow, too. I like the idea of it but can't stand the color temp.
[X 2014 Original Android Development] gtriamy:
Anyone have any problems with 20150606? I'll boot up, cache will rebuild, boot into the launcher and at some point it will freeze with the screen off and i'll have to force reboot and then it restarts rebuilding the cache. Somethings gone wrong but I can't figure it out. I'm going to try to reflash the latest update. Any Ideas?
[X 2014 Original Android Development] Maelfus:
0606 is broken, you'll want to flash to an older version until a new nightly is built.
[X 2014 Original Android Development] armandocorti:
Many of us had The same problem i go back 04 June till The next release

Enviado desde mi victara mediante Tapatalk
[X 2014 Original Android Development] craftyguy:
I was also experiencing this boot loop, but it seems to be resolved now with the June 09 nightly (at least for me)
[X 2014 Original Android Development] EvilEvo:
The newest ROM successfully unlocked GPS for me and I can verify I get a lock with a GPS fix/lock app, but Google Maps refuses to find my location. I've cleared cache and data for Maps which didn't help at all.

Any ideas?
[X 2014 Original Android Development] nerotix:
Try to get a logcat when running maps, and upload this here, so [MENTION=3857343]crpalmer[/MENTION] can find the issue and he'll prolly fix it, he's a god.

Edit: easiest way to get a logcat is by ADB connecting your phone to your computer and make sure its connected with ADB by typing: "adb devices" if it shows your phone as connect you're good to go. Run google map and try to get a location, now type "adb logcat > logcat.txt" run this for 20/30 seconds, so enough info will get logged and it should create a file in the same location as you adb folder called logcat.txt, upload this here. Hope my short guide will help you out. PS All command are done without the double quote's (" ").
[X 2014 Original Android Development] felipevsw:
[MENTION=3965058]dg4prez[/MENTION] and [MENTION=3857343]crpalmer[/MENTION] I believe that was it! The livedisplay mode set to automatic. I've disabled it and now I have to wear my sunglasses to look at my phone's screen so white it is! Thanks for the tips!
[X 2014 Original Android Development] damccull:
Good to know!
[X 2014 Original Android Development] EvilEvo:
I pulled a log but then fixed it myself after looking through it. Forgot I turned off location access for Google Play Services, I guess they switched Maps over to using that instead of requesting location on it's own, because it used to work before (WiFi location, cell location)

So I can confirm those fixes do fix GPS, I just dirty flashed the new nightly and GPS was working.

Thanks CRPalmer!!
[X 2014 Original Android Development] Silencer-22:
Bug

Gestures - Wave. It is working even if trigger is on "off" position.
[X 2014 Original Android Development] Sdobron:
Dirty flash doesn't confirm anything
[X 2014 Original Android Development] EvilEvo:
And why is that? I was on the previous nightly, and GPS wasn't working. I didn't come from stock with a GPS lock prior.

So I went from CM12.1 with non-working GPS to CM12.1 with working GPS just by flashing the Nightly that had the fixes.
[X 2014 Original Android Development] Sdobron:
Post wasn't clear! If that's the case then yes. It confirms.
[X 2014 Original Android Development] Spin_spinning:
Ambient Display

First off, thanks to all of you for making and improving this ROM (obviously our gracious host crpalmer deserves lots).

I switched from unlocked stock to this CM12.1 and have very few complaints.

I do however, have one. It's about ambient display - it's just too easy to wake up the device and with a minor touch, activate all of the display. I don't have a clear solution, but I feel Motorola's implementation of Active Display (where you had to precisely drag a point to a point, i.e. a straight line) is more robust.

With CM12.1, I already had several butt-mails, butt-IMs and butt-notes that were thankfully never sent, but still in the late draft stage. That's to say, things could have gotten way worse.

Is it possible to keep the display deactivated until the swipe-up is complete? Are there any other ways to unlock the phone that I can't think of?
[X 2014 Original Android Development] :
build problems

When i try to build cm12.1 from source, i always get the same error.

while extracting the proprietary blobs, i get remote object '/system/bin/dbvc_atvc_property_set' does not exist and when building the rom i get an error with no ruleset defined for the same path. can anyone help me with this?
[X 2014 Original Android Development] nerotix:
use adb root before executing the ./extract-files script, a tip from crpalmer.

Make sure you're in the proper folder/path.
[X 2014 Original Android Development] :
Thank you so much, it seems like its working now!
[X 2014 Original Android Development] Gafanhotz:
Sadly CM uses Google implementation of Ambient Display and they never touched it, I think it's safe to say that it can't/won't be changed so soon. :/
[X 2014 Original Android Development] orangestrawberry:
Looking to come back to cm12.1. Earlier builds had issues with call quality with others not able to hear me properly. Anyone know if this had been solved?
[X 2014 Original Android Development] :
I have no problems with call quality, everything works fine
[X 2014 Original Android Development] orangestrawberry:
Thanks I'll give it go now
[X 2014 Original Android Development] orangestrawberry:
Yeah. Just tested and same problem of choppy call quality for others hearing exists. No problem with stock. Any ideas anyone?
[X 2014 Original Android Development] thefroyo:
First of all, the quality of recent nightlies is very good! Thx for this great job!

Does anyone have experience with encrypting the phone? I am asking, because I was among the first to try it on my old motog - the experience was less than great (nearly bricked my phone)...
[X 2014 Original Android Development] xKroniK13x:
Try an AOSP ROM.
[X 2014 Original Android Development] Spin_spinning:
Hmm, that might be true... but something must be there! We have the black and white 'preview‘ of Ambient Display, that must be something someone made? Or is that behavior stock on OLED-phones? (That would be news to me, but I like learning new things :) )

I guess the step from the black and white to the full Ambient Display (AD for simplicity's sake) is what's bothering me - it's just very easy to trigger the full-color AD. Moto uses their own preview-equivalent with a very specific trigger area, which from a usability perspective is definitely superior (no/fewer involuntary unlocks).

I guess I'll have to keep dreaming for now..?
[X 2014 Original Android Development] Silencer-22:
Maybe it is ROM related, but I have Xiaomi Pistons V2 and V3 and on Moto X 2014 wiith CM 12.1 the functions keys doesn't work (only play/pause key works). On my old Galaxy S2 with CM 11 on board keys to volume up/down/change track works well, but not on Moto X with CM 12.1. I don't know how to tag it: bug? feature request? any solution? :confused:

I found this change for CM11: http://review.cyanogenmod.org/#/c/73042/1 [MENTION=3857343]crpalmer[/MENTION] is there any posibility to merge it to CM1 12.1? Thank you.
[X 2014 Original Android Development] Gafanhotz:
Well, for clarity: The behavior you see on CM is the same for stock AOSP on supported OLED screens. They didn't touched that and probably never will, as I said up there.

Also, the screen going full color for a few seconds isn't that battery draining, you should be worried about signal quality and wakelocks caused by badly developed apps. At least with me it doesn't make any difference. The battery life still better than stock.
[X 2014 Original Android Development] nabor:
Sorry I am a little busy these days and attached the logs late. I was trying to figure out the meaning of the logs, however it's too complex for me :(. Hopping you can help me ;)

I guess the incoming call issue is because of a notification residents. And about the quick wake-up issue, you may start digging from "com.tencent.mobileqq" and "com.nianticproject.ingress". Thanks a lot:o
[X 2014 Original Android Development] Spin_spinning:
Oh okay. Wow, that's good news for all them Samsung users. Or maybe not news to them, but anyway. Good to hear.

Thanks for the explanation.

Yes, I get that. The problem is that the screen going full color for a few seconds is not the end of it. It proceeds to unlock, write a Textsecure message and then head into settings, until I check for time and realize something's very strange.

Or it plays a youtube video in my pocket. Or.

I've already put in an unlock code. But with on-body detection it stays unlocked, obviously. Also, with Wear, a phone would stay unlocked. I simply think this is going to stay a problem unless addressed.
[X 2014 Original Android Development] rafael.fessel:
Camera next

Any chance to get this working on our devices?

I got one from oneplus one (stock apk) almost everything works without the panorama!

Trier the v22 port with extra features but when i shot with flash... Got force close.

This camera is so much better than original one....

Tks
[X 2014 Original Android Development] folkg:
This is also a problem for me. I went for a run the other day with my phone in my arm band, and when I pulled it out after the run all kinds of mischief had been created.

Is there any way to turn off the ambient display setting from the commandline? I could at least solve this aspect with a tasker task while running, I couldn't find the setting in the "secure settings" plugin.
[X 2014 Original Android Development] sudhamsu:
Can someone help me with this error I get while trying to build CM?

It stops after this:

make: *** No rule to make target `vendor/motorola/victara/proprietary/bin/dbvc_atvc_property_set', needed by `/home/sudhamsu/android/system/out/target/product/victara/system/bin/dbvc_atvc_property_set'. Stop.
make: *** Waiting for unfinished jobs....

#### make failed to build some targets (42:28 (mm:ss)) ####

I'm following the CM wiki guide. I tried "brunch victara" first. Then "breakfast" then "mka" separately; that fails too - I guess "brunch" is equivalent to "breakfast" then "mka".

I had to extract proprietary blobs from the device like the CM wiki guide suggests. I suppose this won't get me any related makefiles, would it? Are the makefiles what I need to solve the above issue?

EDIT: Just found this - http://xdaforums.com/showpost.php?p=60059514&postcount=665

Should have searched before I posted. Looks like the same problem. Will leave this here for future experimenters.
[X 2014 Original Android Development] notanoob:
Could you point me to the apk I need one please
[X 2014 Original Android Development] rafael.fessel:
[MENTION=4534805]notanoob[/MENTION]

2 apks. Stock and moded version...

on the stock, panorama get force close... moded version got the same erro including when taking a picture with flash
[X 2014 Original Android Development] murso74:
Damn active display is destroying my battery
[X 2014 Original Android Development] Gafanhotz:
Are you referring to the one that activates screen when it's off? It actually has no impact on battery life. But you can still deactivate it.
[X 2014 Original Android Development] murso74:
according to wakelock detector, its keeping my phone awake about a third of the time.
[X 2014 Original Android Development] crpalmer:
Is your screen on time about a third of the time and do you have user aware display enabled? That takes a wakelock while it detects that there is an object in front of the screen....
[X 2014 Original Android Development] murso74:
no, don't have user aware enabled. when i pull up wakelock detector, it tells me that DreamManagerService is keeping my phone awake about half the time.... googled it, aparently they use dream manager for the screen saver, that i dont' have enabled, and also for the active display. probably a google issue... moto's active display never gave me this problem.
[X 2014 Original Android Development] Spin_spinning:
In recent days, I get a couple of "Hangouts has stopped working - Ok - Report" prompts. I have hangouts disabled because I dislike it so much (please don't discuss this, it's final).

Flashed via gapps gapps-lpmr1-20150503-signed.zip.

Any ideas? =)
[X 2014 Original Android Development] Gafanhotz:
You're not the only one, no one discusses this over why it's bad. :)

You can remove the APK from the system and see if it solves for you.
[X 2014 Original Android Development] raptir:
Does it work on the Moto X stock? None of my wired headset controls work on my Moto X even running stock.
[X 2014 Original Android Development] :
I usually flash CM from internal storage. Let's say I want to wipe all partitions, including internal storage; according to the WiKi, I can send the zip from my PC to the device while it's in recovery mode:

adb push cm.zip /sdcard/

I see on my Moto X 2014 that internal storage is called "storage", so should I push the zip like this?

adb push cm.zip /storage/

I'm not an expert at flashing yet, and I would just like to know all the alternative ways to flash a ROM, in case something ever goes wrong (I know how to flash full firmware).

Thank you for your help!
[X 2014 Original Android Development] damccull:
Actually in this case you should side load the ROM. After wiping partitions, in your custom recovery there should be an option to sideload. Enable that, then from computer:

adb sideload path/to/ROM.zip
[X 2014 Original Android Development] :
Thank you, I just wasn't sure how the sideload method was used. :good:
[X 2014 Original Android Development] Nicolae-Daniel:
Isn't it easier to copy files from pc? TWRP mounts virtual SD card.
[X 2014 Original Android Development] tebower:
Has anyone had an issue with incoming calls? My first flash was the 6/15 nightly, and I turned off "heads up" notifications. On that build, I would instead see the full-screen slider for answering calls. On subsequent builds, I no longer saw the full screen slider to answer calls. So I was stuck with literally no way to pick up a call (no heads up, no full screen slider). Has this issue been resolved in the newest build?
[X 2014 Original Android Development] thefroyo:
Reboot loop on cm-12.1-20150623-NIGHTLY-victara

I have just updated to cm-12.1-20150623-NIGHTLY-victara. I get constant immediate reboots after startup (cannot even enter PIN to unlock SIM card). I guess I have to downgrade to a previous version.
[X 2014 Original Android Development] raptir:
I just installed the June 23rd release without issue. I installed using the gapps linked on the CM site. Couple things I ran into so far, and this is my first time installing CM on this device so they may be known things.

Setup process was a bit glitchy. When I connected to a WiFi network it went to the "Checking info..." screen like I had logged into my Google account, then booted me back to the WiFi screen. Other weird graphical glitches too, and the soft keys seemed to be overlapping the screen despite not being visible, making some stuff hard to tap.

The ROM defaulted to the T-Mobile IPv4 APN, which will not let me connect to data. I switched to IPv6 once I got it setup, but that could be an issue if you wanted to setup the phone without WiFi.
[X 2014 Original Android Development] craftyguy:
I've been experiencing this problem for some time now (reproducible on the 0623 nightly) where Wifi will lose its data connection, causing a bang to appear next to the wifi icon in the status bar. It occurs on pretty much every Wifi network I've connected to (open hotspots, WPA hotspots, etc), after it has been connected for some amount (1hr?) of time. If I disable then enable the wifi radio on the phone, it will come right back up.

[MENTION=3857343]crpalmer[/MENTION], have you seen this? I'll try to grab logcat output the next time it happens.
[X 2014 Original Android Development] thefroyo:
Strange, downgrading and upgrading to cm-12.1-20150623-NIGHTLY solved the issue for me.
[X 2014 Original Android Development] craftyguy:
Here's the logcat output and a screenshot showing the wifi icon with a bang. Please let me know if you need me to collect any more information!
[X 2014 Original Android Development] raptir:
Just to make sure I'm clear, the issue occurs if you're connected for about an hour, whether you're actively using it or not? I'll test it out tonight.
[X 2014 Original Android Development] craftyguy:
I stated an hour, but honestly it seems to be anywhere from 30min to a couple of hours.. I haven't measured it. The flow goes something like this:

1) connect to wifi network

2) use device

3) device goes to sleep (i have "keep wifi enabled when screen is off" enabled)

4) repeat 2 & 3 some number of times (this is the uncertainty of "30min to couple of hours")

5) notice that eventually when I wake the device up to use it, there's no wifi data connection
[X 2014 Original Android Development] crpalmer:
Do you have an idea of when this started or has this always been a problem?
[X 2014 Original Android Development] craftyguy:
It hasn't always been a problem, but unfortunately I do not recall exactly when it started. I do remember a couple of weeks ago there were a number of wifi changes/fixed checked in and I was experiencing the problem then because I was hoping they would have fixed this issue (though none of them called out this problem specifically). If I had to guess, I'd say it has been happening for about a month.. sadly this is the first chance I've had to sit down and report it :(
[X 2014 Original Android Development] crpalmer:
Next time it happens, can you grab a logcat and a radio log? I am not having the same problem but I have seen related problems reported on other devices.
[X 2014 Original Android Development] craftyguy:
Sure thing. I have logcat posted in my earlier post here

How do I capture the Wifi radio log?
[X 2014 Original Android Development] crpalmer:
logcat -b radio will get you the radio log. That's the one that is more likely to be interesting for something like this but you really need both to try to correlate what happens in each.
[X 2014 Original Android Development] craftyguy:
I managed to hit this again today, logcat and radio log are attached in the zip file. Unfortunately I'm not able to catch the problem immediately after it happens since it seems to occur when the device is asleep... I see the bang when I wake it up.
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION] btw about the reboot issue with watching video's I might have an awkward way to reproduce it.. but what uses a lot of embedded video's? And where is a lot from? the answer is: watch some p*rn and you'll have your phone reboot pretty quickly. Not the nicest solution but I tried it.. for research purposes.
[X 2014 Original Android Development] crpalmer:
Urg. I have scripts that generate logs for me and I forgot to mention that you should include -v time in the logcat command to include the timestamps which I need to actually match up what happens in the two logs. Could you please grab another pair of logs when it happens again?

FYI, I can see in the logcat that it fails to do the captive portal check (aka, "do I have internet connectivity") but the logcat doesn't say much about why...
[X 2014 Original Android Development] :
I take it this is a snapshot of CM 12.0 Lollipop 5.0.2:

cm-12-20150626-SNAPSHOT-YNG4NAO0A0-victara.zip

OK, I just read the blog:

http://www.cyanogenmod.org/blog/releases-11-12-final
[X 2014 Original Android Development] ThaSik1:
Can confirm, research has shown this means of testing has led to numerous frustrating reboots
[X 2014 Original Android Development] tebower:
Has no one also experienced the disappearance of the "slide to answer" screen for incoming calls? No responses were received. I flashed the latest nightly and it still doesn't work. Last build I tested that it worked on was 6/15.
[X 2014 Original Android Development] nanca:
Did you try a clean install? Working fine for me... :)
[X 2014 Original Android Development] 0.0:
Does the latest patch turn off the attentive display while on the lockscreen, since I do not think keeping your phone awake while looking at it on the lockscreen is needed?

I will test as soon as I can. It's getting late where I live, so it will take awhile for me to do so
[X 2014 Original Android Development] crpalmer:
Oh, right, I forgot to mention that one. It actually adds a lot of complexity because I need to determine on SCREEN_ON that keyguard is enabled and then wait for another intent to tell me that keyguard has been disabled. While a good suggestion, it's something I would need to look at later rather than break everything now.
[X 2014 Original Android Development] Flamehell:
[MENTION=3857343]crpalmer[/MENTION] mate sorry,wave to silence it doesn t work for me....clean install but i tryed 5 times and it doesn t work......any suggestions?
[X 2014 Original Android Development] crpalmer:
One a different topic, the next build (check the cmxlog to see if your build has the commit or not) will add WIIMOTE support. Or, well, it might. I can't test it but I pulled the commits from bacon and theoretically it should work (if bacon's even works).

If someone can test and let me know either way if it works, that would be helpful.
[X 2014 Original Android Development] crpalmer:
Are you trying to silence an alarm? It only works for phone calls...

If it's really not working, get a logcat (with -v time!) so I can see what's happening when you try to silence an incoming call.
[X 2014 Original Android Development] Flamehell:
I m trying to silence a call....when is coming,i start to wave on the screen,the screen becomes black(off)but is still ringing....that's it....:)

---------- Post added at 12:13 PM ---------- Previous post was at 12:01 PM ----------

[MENTION=3857343]crpalmer[/MENTION] i found which is the point...if a call is coming,if you wave your hand from left to right,it doesn t work....from right to left,it works!!:)