yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] Sdobron:
You realize fast charge (or quick charge 2.0) is hardware dependent right?
[X 2014 Original Android Development] kackburt:
anyone tried specific IR sensors to get a certain result like triggering ambient display? In my testing only the one's at the top of the phone actually trigger ambient display. Dunno if it's supposed to be that way, but as far as I remember Moto Display got triggered everywhere.

btw. I am on nightly 20150518

keep up the good work!
[X 2014 Original Android Development] enochpc:
Many pages back crpalmer pointed out that they got ambient display working but only on some of the sensors. Still works pretty well, just need to get into the habit of swiping at the top of the phone. I find the improvements cm makes on this phone are so great the few little set backs are well worth it.
[X 2014 Original Android Development] crpalmer:
All the sensors work. Look in Settings >> Gestures to make sure you have all the options that you want enabled.
[X 2014 Original Android Development] aishokry:
[MENTION=3857343]crpalmer[/MENTION] How come there hasn't been any new builds since the 18th? Is Jenkins sick?
[X 2014 Original Android Development] kackburt:
They all seem to be working, because I can see them light up, but not all trigger the ambient display screen. Only the one at the top right as far as my device is concerned. Nothing to worry though - just wanted to mention it.

Cheers
[X 2014 Original Android Development] iPwn_:
That's because only one of them is a sensor. The three that glow are transmitters for IR light so your hand can reflect it and the sensor can detect the motion.
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] is attentive display (looking at phone won't shut it off) possible since you got IR sensors working?

P.S. if you already saw this question in the cm12.0 thread, I deleted it since I put it in the wrong section

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
Yes. As soon as the fix build is done and I sanity check it, I'll be stopping these unofficial builds.

Amusingly, I got the email asking for people to set their device readiness for the 12.1 builds about 5 minutes after I created this thread. I guess I just needed a little more patience...
[X 2014 Original Android Development] sudhamsu:
It probably doesn't work with the IR sensors. From my crude experiments - like covering the sensors and front camera separately - I found that the covering the front camera affects it, while covering the sensors changes nothing. So, I would say Moto just implemented a low-power facial analysis using the front camera.
[X 2014 Original Android Development] 0.0:
I read arstechnica's article about the feature and they stated that it first uses the IR sensors to see if there is anything within its range. If so, the front camera is activated and scans for a face. Motorola states it allows for better battery life. I guess the IR sensors is not used how I thought for facial recognition

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
This seemed like more fun than what I was planning on doing this morning... Do you want to build with these two commits:

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

(and the one that one depends on) and let me know how that works for you? The other commit makes the amount of haptic feedback for the camera/torch actions configurable so feel free to test that one too while you're at it...

Edit: In case you didn't notice, the AD mode is disabled by default, you need to enable it in the gestures settings.
[X 2014 Original Android Development] sudhamsu:
Makes sense.

Awesome!

Is this implementation like Moto's? As in, does it look for a face through the front cam? (Just curious, as the code in the commit doesn't suggest this.) Or are you just looking for an object through the IR sensors? (Which makes some sense too. And this just might avert the inaccuracy of the front cam method - sometimes it just couldn't recognize me.)
[X 2014 Original Android Development] aamzalag:
Ambient display being unusual

Hey [MENTION=3857343]crpalmer[/MENTION] , im not sure if this is intended behavior, but i noticed since the ir sensor activation for waving over the screen to pulse, if im connected to bluetooth in my car and i use the nav system to skip tracks, play or pause, the screen turns on anytime an action is sent. Previously it would simply change the song or play/pause.

Just wanted to see if anyone else has the same thing, and if its intended or not?
[X 2014 Original Android Development] 0.0:
I shall test it and let you know how it goes as soon as I can

Also, like sudhamsu, I am also wondering if it uses the front camera to detect a face after detecting an object with the IR sensors
[X 2014 Original Android Development] Flamehell:
[MENTION=3857343]crpalmer[/MENTION] Sorry mate,i saw from the link of your unofficial build that there is a version of today,17-04...can we flash it?Is a new version without some bugs?Tnx a lot :)
[X 2014 Original Android Development] crpalmer:
No, I'm just using the IR sensors for a quick and easy version of it. Hopefully it will work well enough.

Honestly though, I think that it's probably better that way than what Moto did (except for being able to talk about how awesome the feature is). I don't really want to have to be staring at my phone to keep it on, just holding it up to me should be enough, and I worry that even with the IR sensor + camera, you're definitely burning some processing power each time you trigger it and you're burning this processing power while someone is most likely actively using their phone.

But, we'll see how it works out. I do need a different name though to avoid confusion with the real moto feature.
[X 2014 Original Android Development] crpalmer:
It's a nightly build, so it has more commits made to it that weren't in the previous one, I can't promise it removes bugs and doesn't add new ones though!

It's good to install or you can just wait for the first official nightly to make it out of the auto-build machines.
[X 2014 Original Android Development] Flamehell:
I saw now that on Jenkins there is the official one in 4 or 5 hours....so i will wait that one...tnx a lot mate for your work!!:)
[X 2014 Original Android Development] 0.0:
I was thinking that if the phone is on the table, then staring at it, say when reading, will keep it awake. With the current method, I would need to be holding it to be sure that it is awake? Whatever you method you choose, I'm fine with it

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
Moto's version is stricter than my version (it needs the IR sensor to say that some object is in front of the screen and then it uses the camera to see if that object looks like a face). This implementation simply checks that there is something, anything, in front of the phone. That's why I added the stow sensor check in my second PS.
[X 2014 Original Android Development] 0.0:
How you implemented it makes sense. I wasn't exactly sure how Moto implemented it and how strict theirs were. I will also think of a better name for the feature (but I am bad with names so that may not happen)
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] I tried out the attentive display. It's good so far. I only tried patch set 2.

However, would it be better if you don't allow attentive display while on the lockscreen? I don't see the point of having it scanning while on the lockscreen.

Another suggestion is instead of having the IR sensors and stow thing always on, would it be better if it scans maybe 5 seconds before the screen timeout begins? Will that help in the battery life?

I still think the using the front facing camera would be better. Another scenario: next to your friend, you're on your phone then you turn your head to talk to your friend or vice versa. When your head is away, it would be better if the display be allowed to turn off since you're not looking at the phone. The current implementation still detects an object even when your head is turned, thus leaving the display on

Since we are on the topic of attentive display, it would be cool if the IR sensors (or front camera if you decide to use that instead) allows the screen timeout to be, say, cut in half when you're not looking at the screen. That's another Moto battery saving feature

sent from my Moto X Pure Edition
[X 2014 Original Android Development] sudhamsu:
First two points make sense.

But I would disagree on the third one - for two reasons. One, it'll use extra processing power and battery. Two, the facial recognition part is not as accurate as it needs to be, and honestly, with the way I usually hold me device the front cam would probably never find my face. Also, I sometimes keep the phone on a table and read, and my face won't be directly above it, so the front cam won't it - but maybe it won't find any object through IR sensors either.

If you insist on having the facial recognition, then I would say let it be optional. Let the user choose for or against it in the settings.

Also, to [MENTION=3857343]crpalmer[/MENTION], and others as well, does it make sense to have a feature which would allow me to wave my hand over the phone moments after it goes dark to wake it up back up? Consider this scenario - I'm reading something on the display with the device on a table, and there's nothing above it for the IR sensors or the front cam to sense. I'm sure this scenario is quite common. So, now the display goes dark after the timeout, but I'm still reading. This has happened with me many times, and I find myself waving over the screen to bring it back up. See, when the display goes dark, there's a certain time lag before the lockscreen is invoked. Before that happens, if you press the power button you can go back to the same screen that was on before the screen went dark. Similarly, couldn't we use the IR sensors and a hand-wave to wake up the device before the screen is locked? (The current implementation of the attentive display/wave-to-wake may or may not solve this case, I haven't been able to try it. If anyone can confirm if this case get's addressed by default then that's great.)

Also, for the name, how's "User-aware Display"? It's simple, and possibly the feature's intent is also communicated with this name.
[X 2014 Original Android Development] 0.0:
An option for the front camera works. Hopefully my first two points and the last point (last sentence) can be implemented.

With the current implementation of attentive display, it does stay awake and the screen is lit as long there is an object (your head) in the IR sensors range. However, [MENTION=3857343]crpalmer[/MENTION] when I pull away from the IR sensors and it is past the screen timeout (mine is set to 15 seconds), it automatically shuts the display off. That's too quick imo. Could there be a ~2 second delay after pulling away from the IR sensors? Does that make sense?

As for the name, how about "Awareness Display" instead?
[X 2014 Original Android Development] crpalmer:
Camera: I am not going to implement the camera right now for a couple of reasons. First, I'm lazy and that's a lot of work... Second, I worry about the value received vs. the power consumed. If it's not 100% reliable then I feel like it's worse than not having it at all as predictable software provides a better user-experience.

User-aware display: thanks, I like that name.

Wave to wake-up: I don't think that this is possible because android doesn't tell you whether or not the screen was turned off due to timeout or due to user interactive. If it's due to user interaction, it would be nearly impossible to turn off your phone if the IR sensors could turn it back on again immediately! I actually just added a patch in there to not let them trigger a doze immediately after it turns off as I find that I'm dozing in my pocket a lot.

Delay turning the screen off: good suggestion. I added a 3 second delay (with a dimmed screen) before it turns off. That makes it much more useful and I think reduces some of the need for the wave to wake up. I found I was doing the same thing as you yesterday (after it timed out waving my hand at the phone) and with the dim it gives me feedback that lets me keep the phone on and now I don't feel like I need that as much.

Can you please retest with the current set of patches (go to this commit in gerrit and then use the "checkout" to get it as well as the dependent commits)?
[X 2014 Original Android Development] felipevsw:
Just to let you know the new build, 0521, is fine to flash. No errors so far.
[X 2014 Original Android Development] aishokry:
Thanks! Love the vibration intensity control.
[X 2014 Original Android Development] abhay6547:
How's the performance? The last couple nightlies were terrible for me, lot's of lag and home screen redraws.
[X 2014 Original Android Development] Abhiraj4u:
Go for it

Performance is good.

This nightly seems stable, no lags or redraws, battery seems better.
[X 2014 Original Android Development] gopik5:
flashed 2105...seems good..will test and update
[X 2014 Original Android Development] endursa:
I recently got told that i am hardly understandable while calling someone! this is a really wierd issue and not easy to reconstruct/debug. But j get told that i sound like ali mumble really hard and am quite silently speaking! Did anyine else experience this?

I never experienced this while back at stock. Maybe it has something todo with noice cancelation?
[X 2014 Original Android Development] felipevsw:
Battery life is great and performance is good.
[X 2014 Original Android Development] orangestrawberry:
Exactly same issue for me a few pages back. No response from anyone so have to go back to stock.

Can't have a custom ROM if no one can hear me!
[X 2014 Original Android Development] endursa:
I switched to Nexus experience rom, and it seems to work better!
[X 2014 Original Android Development] iPwn_:
Has anyone had issues with System UI randomly crashing inside certain apps and freezing the whole phone for 5-10 seconds?

And it seems to freeze perpetually.

The only way I can recover control of the phone is by turning off the screen and turning it back on while holding the volume button down. Then it will actually take me back to the lock screen and restart System UI instead of taking me back to the frozen app.

I'll try to pull a log next time it happens.
[X 2014 Original Android Development] crpalmer:
Can't fix bugs without logs.
[X 2014 Original Android Development] endursa:
crpalmer, help me to help you, do you need logs while a phone call with audio issues are ongoing? Or how protocol this behaviour? I am really lost on that issue here

---------- Post added at 05:35 PM ---------- Previous post was at 05:15 PM ----------

Ok i just called myself from another phone and listened to myself speak on the other phone (kinda crazy ?)

Conclusion is that the mic record volume is so low that sometimes it does not trigger at all.

Only thing that helped was me speaking really loud!

I do not know if this is just a call record setting kernel problem or my microphone could maybe be defect? Or maybe it has something to do with noise cancellation? Would be really cool if you could tell me what you need to debug/fix this!

I'll try, to go back to stock to check if my mic is defective tomorrow,
[X 2014 Original Android Development] crpalmer:
I have no idea what your problem could be either. I tested speakerphone and handset calls this morning with no issues.

Try making a call and then grabbing all of the dmesg (kernel log), logcat and radio log and I can see if it says anything.

What model phone do you have?

Have you ever installed the 5.1 soak (which may have updated some firmware)? If not, have you ever installed stock 5.0 (to get the latest official firmware)?
[X 2014 Original Android Development] endursa:
ok i'll try taking logs while calling.

i have the european version Xt1092 and i never tried any 5.1 soak files, i just flashed RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC and then went on to using cm12/cm12.1 (also same with nx rom but i guess it's based on your device tree anyways :))

i also just tried comparing mixer_path files with 5.0 stock, but they are identical!
[X 2014 Original Android Development] endursa:
after some googling and research i found that One plus one had the same problems and it was fixed in the mixer_paths.xml file!

i took a look at the file and changed one line and now it seems to work properly!

i edited line 45

<ctl name="DEC4 Volume" value="84" />

to

<ctl name="DEC4 Volume" value="99" />

and no i can even whisper and the other end understands me properly :)
[X 2014 Original Android Development] 0.0:
could you add the changes you made to your post? it is not showing up
[X 2014 Original Android Development] endursa:
i have no idea what happend, but the code brackets where empty maybe tapatalk edit did not work :D

but you can see them now (at least i can )
[X 2014 Original Android Development] alvareo:
I had this same confusion. [MENTION=2019427]kackburt[/MENTION], if you place your hand over the bottom sensors at a distance of about 10 cm or less, you'll see it light up. Covering them doesn't work as they need to bounce and go to the top.
[X 2014 Original Android Development] alvareo:
Hey, just got another of those random soft reboots. Logcat is attached.
[X 2014 Original Android Development] orangestrawberry:
Hi. Was it just this line? Did you have to do anything else?
[X 2014 Original Android Development] felipevsw:
Anyone else also troubled with the white-kinda-yellow? Or is it just me?

I mean, anything that's supposed to be white like background, keyboard, clock on the top bar isn't really white... It's kinda yellow.

Besides this, this rom is great!
[X 2014 Original Android Development] alvareo:
That's due to the AMOLED screen and has always been the case on this phone
[X 2014 Original Android Development] felipevsw:
I see.. So if it's due to hardware it also happens on stock? I don't remember having this problem on stock.

Anyways, a restart makes it go away for a while.
[X 2014 Original Android Development] alvareo:
I did notice it on stock. I can even notice it on the boot screen.
[X 2014 Original Android Development] felipevsw:
I didn't use stock for more than two weeks actually, since I couldn't live without CM :D
[X 2014 Original Android Development] iPwn_:
Use the LiveDisplay calibration settings under Settings > Display.

Turn green down to ~90% and red to somewhere between 90 and 95% based on what you like.
[X 2014 Original Android Development] alvareo:
Damn, didn't know this was added. Either way, I use the Render Kernel now
[X 2014 Original Android Development] halfsoul:
Question about the fix: Does it need to be done only one time before/during the initial CM flash, and then GPS permanently works thereafter?

Or do folks have to do the GPS rain dance (backup, flash stock, gps fix, restore CM) every time they want to use GPS?

It is inconceivable why this isn't listed as a known issue. It fits the literal definition of a known issue.

The only possible explanation is that it is being omitted for nefarious reasons (hidden intentionally, vindictive/conniving, etc); I do not want to believe this is true about crpalmer, he seems great and I appreciate his efforts tremendously. It makes no sense at all that he would want to intentionally mislead people, but what other possible reason could there be??

All questions, comments, and discussion about GPS could be silenced with one post.

BTW, seeking to give the benefit of the doubt...

It's not listed on the CM wiki page for known issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_victara

(this appears to be the community's shortfall, since anyone can update the wiki page unlike the OP in this thread)

Nor is the fix in the CM wiki page for installation instructions: http://wiki.cyanogenmod.org/w/Install_CM_for_victara
[X 2014 Original Android Development] alvareo:
Yes, before flashing the ROM you use that app and when it tells you it did a fix, flash the ROM normally and you'll have GPS until you flash your internal storage, which you probably won't do.
[X 2014 Original Android Development] halfsoul:
Okay, thanks. More searching using keywords from the above found this:

What is it about /data/media that is important for preserving GPS functionality?
[X 2014 Original Android Development] alvareo:
/data/media AKA internal storage AKA SD card is where, basically, GPS compatibility is stored. Along with your files, of course.
[X 2014 Original Android Development] Silencer-22:
Could you provide dl link to this app? I really need GPS and on CM 12.1 it is fixing but only in one point, and if I move somewhere GPS do not track after me so navigation/endomondo/strava are useless...
[X 2014 Original Android Development] crpalmer:
How's the noise on the line when you are in a nosiy environment. I would expect that to kill noise suppression.

Where do you see this "Fix" for the one plus one? The official builds have a dec4 volume of 84.

Are you using a case on your phone that could be blocking the speaker?
[X 2014 Original Android Development] meexx:
Hi, i use the last nithgly, and i have with whattsapp problems. When my phone goes to standby and then i becomes no whatsapp massages, when i unlock then comes the massages. Have other Users also this problem ? I have a clean install without any mods or so, last nithgly and Gapps from CM wiki and then whattsapp install

Greeting Ralf and sorry for my bad englisch
[X 2014 Original Android Development] alvareo:
Though it hasn't happened to me, this seems to be a widespread issue and I doubt everyone with it happened to put a mic-blocking case on their phone at the same time they flashed CM

---------- Post added at 10:49 AM ---------- Previous post was at 10:46 AM ----------

It's GpsFix on the Play Store. By the way, flashing and reflashing via Nandroid backups doesn't seem to work.
[X 2014 Original Android Development] Silencer-22:
It doesn't work. 15 minutes of working and there is no fix. It looks like GPS module is pretty broken and should be fixed...
[X 2014 Original Android Development] nerotix:
@ everyone, for some reason the weather shows in Fahrenheit for me.. I can't seem to find how to change it to celsius.. anyone an idea? See screenshot.
[X 2014 Original Android Development] alvareo:
You flashed everything but internal storage, went back to stock 5.0 and GpsFix didn't work?
[X 2014 Original Android Development] Sgace:
You tried adding weatherwidget to your homescreen, edit its settings and reboot your device?

Cheers
[X 2014 Original Android Development] nerotix:
that worked, thanks!
[X 2014 Original Android Development] Sgace:
You're welcome. Glad it worked out for you.

Cheers
[X 2014 Original Android Development] felipevsw:
There's no need to be this exact app. You can get a GPS fix with any app, even Google Maps. I used "GPS Status and Toolbox" app.
[X 2014 Original Android Development] damccull:
Is the GPS issue still an issue? I just flashed but I'm feeling that I may need to go back to stock if that's the case. Sadly, GPS is very important to me, and a deal breaker if it doesn't work yet. Is there anything I can do as a consumer of CM to help get the GPS and other proprietary hardware working with CM? For instance, the low-power display hardware for notifications and such.

Also, is this a place to add suggestions? I tried adding one to cm jira but they have no way to add suggestions for 12 yet. Seems silly, considering 12 is most likely where we'll see improvements at this point.
[X 2014 Original Android Development] crpalmer:
GPS works perfectly with this ROM if you acquire a lock in stock before flashing this ROM.

Searching a thread a very useful tool when you have an issue that has been asked and answered several times...
[X 2014 Original Android Development] alvareo:
And how will people know that if you refuse to put it in the OP for no reason whatsoever? Jesus, man, how hard can it be? Do you enjoy knowing that people will have to do the flashing procedure twice?
[X 2014 Original Android Development] crpalmer:
[MENTION=4652666]alvareo[/MENTION], to quote the OP: