yashsingh1/xdaforums huggingface dataset:
[RAZR HD Android Development] taimur272:
Guys I wanted to ask an Q's . Does RAZR HD support double tap to wake feature if it does how cane we utilize that feature or enable it. As far as I know we need kernel support to enable this feature but don't know if our kernel supports it..
[RAZR HD Android Development] Zeljko1234:
Feature like that requires digitizer to be on all the time or at least be on frequently to detect double tap. Consequently drains battery. Power button on the side is not that far to reach ;)
[RAZR HD Android Development] taimur272:
But it's a nice feature to have in a phone my friend have it in his huewai honour 4c he can even draw gestures on off screen to open apps .. Does our digitizer supports this feature I mean can our digitizer work in low power mode so it can detect double tap
[RAZR HD Android Development] CWGSM3VO:
The kernel I ran on my EVO 3D had this feature. I grew to like it but when I got my HD, I forgot all about it. In truth though, I suspect it would be a battery drain on the HD although I think some newer devices have low-power panels to accomplish this (not 100% sure though).
[RAZR HD Android Development] IronTechmonkey:
More, and likely the last about auto brightness. The issue was not hardware but rather a change to the triggering and range used depending on suage scenario. http://xdaforums.com/showpost.php?p=63471948&postcount=375.
[RAZR HD Android Development] d5grvty:
Might be a bit of a dumb question but how do you use a custom alarm tone. I've tried placing both an mp3 and a ogg file in the system/media/alarms and while occasionally the file shows up, it never plays. Any ideas?

Thanks
[RAZR HD Android Development] IronTechmonkey:
I recall his being easier in previous iterations of CM but now, in order to play custom OGG files as alarm, with proper audio preview during selection, I had to do this: Copy ogg files to \system\media\audio\alarms. Change permissions on copied files to match existing native alarm ogg files, also changing owner to root. They will appear instantly for selection in the alarms app's ringtone section and... once the media scanner has run (as a result of restart or other trigger) the files that were copied will be shown in duplicate in the alarm app's ringtone list even if there is only one of each on the entire device. Either duplicate can be selected and will play, most likely because they are just different path links to the same files, although I don't understand why the native ogg alarm ringtones are not listed twice. If you don't set the permissions the files may appear and accept selection but will not play (at least not in preview). For good measure I also created ogg files with specification as similar to the native ones as possible.
[RAZR HD Android Development] CWGSM3VO:
I thought ringtones and such are to live (user-added) on the sdcard where permissions and such are a non-concern for users adding additional audio? There's a ringtone directory on both my sdcards, when I drop audio in there and mediaplayer picks it up, I see and can use it as I would expect.
[RAZR HD Android Development] IronTechmonkey:
Hmmm... I thought I tested for that in the internal SD card's \Alarms folder but either something has changed since I tested or I got lost while testing. Although the alarm app's ringtone list does not seem to show contents of the SD card's ringtone directory (which does work fine in the phone app), as you mention and as was the behavior in previous ROMs, copying either OGGs or MP3s into that alarms folder rather than \system\media\audio\alarms allows them to be selected in the Alarm app's ringtone list with proper audio preview without any fiddling with permissions .Apologies for what turned out to be false report.
[RAZR HD Android Development] CWGSM3VO:
This may help folks out with auto-brightness: http://review.cyanogenmod.org/#/c/114987/
[RAZR HD Android Development] IronTechmonkey:
Interesting. It looks some commit from July 2015 is preventing a sensor reading from being taken/used when auto-brightness is enabled.I suppose that it was not until the commit that increased sensitivity hit that a bad combination was reached, or maybe it's just that no-one noticed because auto-brightness was not that useful. In any event, will test it.
[RAZR HD Android Development] CWGSM3VO:
I noticed something similar with proximity/accelerometer sensors with regard to Ambient Display (the notification one) -- I don't see denials of any kind (mind you, I didn't look too hard) and it's been quite some time for this one. The idea is that when a user picks up the device with this feature enabled, it'll light up the screen and show whatever notifications are present. This stopped working some time ago.

Then I saw this commit:

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

Which is for CM13 / Motorola Shamu (nexus6) -- I haven't tried a similar patch in my local tree yet but it's worth investigating.

Sorry a bit off topic here but the point I'm trying to make here is that these things change and never seem to be re-visited :(
[RAZR HD Android Development] IronTechmonkey:
Indeed, and there is much to re-visit. I have a long list list of things that were once added to CM11 then lost, but am not allowed to file CM reports (MotoE official ROM but no snapshot yet) and this has made CM12.x much less complete than CM11 - and oddly less complete than the last time I tried CM12 on the AHD months ago. I'm preparing to clean flash ROM with new auto-brightness commit now. That other sensor stuff looks interesting as well, although I don't use those features. Merci.

[EDIT] In 10/27/15 nightly (Moto E), Auto-brightness working much better, but new FC when attempting to add QT tiles (confirmed in clean flash, ROM only, no settings changes) chased me back to previous nandroid. QT is the very last thing I configure and I did not catch this until 3 hours into the test Grrr..

[EDIT2 ] https://jira.cyanogenmod.org/browse/NIGHTLIES-1953 I voted for it and added confirmation of 10/21/15 as last known good.
[RAZR HD Android Development] CWGSM3VO:
I merged this patch into my source tree (which is almost identical) and now building -- see if it fixes Ambient Display or anything else.

EDIT: I should say, I merged anything that was missing but only changed a few existing items to match.

EDIT: Came across a Sony Z Ultra 4.4.4 post about this addition breaking sensors and to remove from sec_config, will try that if this fails.

EDIT: OK, I feel really stupid here. Built fine but still wasn't working. Googled around a bit and discovered a post on the CM forums about going into Settings->Gestures and sure enough, Ambient Display was enabled but hand-wave and pocket-mode were disabled. Re-enabled them, tested, works fine. What I need is someone with a stock build to see if they can repro this as well (and of course, you can turn it off after if you like....)
[RAZR HD Android Development] Zeljko1234:
Just to let you know that I still have razr, just really busy with rl. My another device (LG G pad) will taste MM soon, maybe today :)
[RAZR HD Android Development] danfeng:
Anyone having problems with update？

tried clean flash 20151029 build ，then update to 20151030 build， got the same error message

来自我的 DROID RAZR M 上的 Tapatalk
[RAZR HD Android Development] CWGSM3VO:
Something's not right here but I can't figure out what it is exactly. When you say clean flash, did you wipe internal storage as well?
[RAZR HD Android Development] danfeng:
yes ，wipe everything except external sd

来自我的 DROID RAZR M 上的 Tapatalk

---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------

Factory reset will solve the problem, but I can't update without making a factory reset since 20151020 build

来自我的 DROID RAZR M 上的 Tapatalk
[RAZR HD Android Development] Zeljko1234:
Motorola Moto X Force Expensive and in USA again available only in Verizon (Droid Turbo 2) but a worthy successor of our device.

[YOUTUBE]JJWmBFV2GHM[/YOUTUBE]
[RAZR HD Android Development] billycar11:
most likely will never get bootloader unlocked that's why i went nexus 6 last year first modern nexus on vzw
[RAZR HD Android Development] Zeljko1234:
Nexus doesn't have sd card. I bought Nexus (7) once and never again, even if will have huge internal memory. If gets broken for any reason, good bye my data or for someone even worse, service will have it.

For Verizon version you're probably right. Otherwise Moto became dev friendly, for example xt925 bl is officially unlockable and new phone as well. Also, Moto Android is almost stock. No need for custom rom, maybe only root.

Thanks for remind me to check about Moto X Play. Yes, it is unlockable :)
[RAZR HD Android Development] IronTechmonkey:
To one of your points about moto stock OS; the Moto E without provider branding has a very nice lean interface in spite of some Google bloat and a lack of some nice CM features, and it has an external SD (although a bad digitizer and a few other things weaken it). As to Moto allowing unlock, I thought that was only for non-US devices.
[RAZR HD Android Development] Zeljko1234:
Bad digitizer? What else?

Usually Moto makes deal with Verizon, AT&T... That's why unlocking bl is not available. Not sure about other carriers.

I'm just slowly investigating what's going to my (maybe ours) next phone. Looking for longest possible battery life, sd card, good camera and other nice goodies. Insane resolution is not on the feature list, more on disadvantage.
[RAZR HD Android Development] IronTechmonkey:
At the risk of going a bit further OT: The Moto E 3G is is a very low end device with a small screen made of the hard pyrex type glass, with no flash for camera and an LED that the stock system does not even use (although CM does use the LED). Most folks from the MSM8960 family would consider it a letdown. That said, it was a pleasant surprise considering it was the first android I found (at Best Buy in store) on the day my AHD died and it cost less than $100. As for the digitizer, it experiences massive bounce back when scrolling lists in stock and CM (until CM partially fixed it). It is also prone to interpreting taps as swipes which is very frustrating on a small screen. I suspect that a poor choice of hardware, screen size and dpi settings make it nearly impossible to manage programmatically. Also, Moto betrayed a promise to update this device in an even worse way than they abandoned previous devices... and that is saying something. So bad in that regard that I started an on-line petition to call Moto out on the failure to update Moto E as well as their absence of any sensible methodology for updating ,and repeated betrayed promises to update other devices. another thing to consider is that there are 12 Moto E models spanning 2 generations (10 of them in the newest generation), many regions and different hardware configurations, which significantly dilutes CM and other independent development. that is another thing that would disappoint people from MSM8960 which has had very stout dev for a long time.
[RAZR HD Android Development] Zeljko1234:
Well for less than $100 is hard to expect and offer much. Probably Moto wish to get rid of it and forget what they done. Not excuse, of course but understandable.

Didn't investigate much but hope that more expensive series have better support.
[RAZR HD Android Development] IronTechmonkey:
Yep, and if Best buy had the refurbished Droids in store instead of just on-line I might actually be posting on-topic in this forum :). Thanks (out of officials).
[RAZR HD Android Development] Thibault1171:
I saw it on a french website, it seems to be really resistant. But some people are afraid of the Snapdragon 810 (heat).
[RAZR HD Android Development] Zeljko1234:
I'm also concerned about 810. Is 820 out already? If yes, probably would be better choice. Anyway, lets wait for review and maybe for price drop. Otherwise X Play looks as good option.
[RAZR HD Android Development] Zeljko1234:
Finally had time to flash MM (AOSP) on my tablet. First impression is really, really good. Everything works, subjectively smoother, no big visual changes (finally status bar and tiles can be edited in experimental settings), looks like that new battery optimization really works (funny is that only one app is not optimized, Google Play Service).

Looking forwards to see MM on Razr.
[RAZR HD Android Development] Thibault1171:
It's good to know.

Maybe, one day, Google'll get rid of this cr4ppy app or fix it.
[RAZR HD Android Development] Zeljko1234:
Never will get rid of it. Became core of Android and closed source. Probably will get bigger over time. Only hope that will not drain battery at least on stock and aosp. CM will probably have problems and have to find workaround as they always do.
[RAZR HD Android Development] Thibault1171:
Yep. Recently I've pulled back from my drawer my old HTC Wildfire (Buzz). Install CM7 (or any other ROM), gapps, and you'll get no space to install anything else, thanks to Play Service. Fortunately, we don't have this issue on our daily devices.
[RAZR HD Android Development] Zeljko1234:
Just have gapps ready for MM :)

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[RAZR HD Android Development] Zeljko1234:
Look what I found in bestbuy. Feeling in the hand is really nice, works smooth... It's full of Verizon bloadware but all can be disabled. And according seller, can be used with any (nano) sim card.
[RAZR HD Android Development] Zeljko1234:
[YOUTUBE]W9D1n5roKbA[/YOUTUBE]
[RAZR HD Android Development] Thibault1171:
CNN also made this kind of video.

It seems to be really resistant. Maybe it's a good option, but I'll keep my XT925 as it still working well.
[RAZR HD Android Development] CWGSM3VO:
As is mine :) Besides, as my old tired story goes; my wife gets a new phone before I do so I have to make-do ;)
[RAZR HD Android Development] CWGSM3VO:
A good deal of security related patches made their way into the 11-03 official build. Settings>About Phone now displays Nov 1st, 2015 as security patch level for the device.

I have to say I'm pleased that CM has taken a serious focus on delivering secure builds (as far as what's publicly known, anyways. Nobody is any better really ie: Microsoft, Apple, etc). I posted a while back about CVE-6602 (iirc) which that particular CM build wasn't vulnerable (at the time, the latest Android exploit). I tested my Wife's Xperia T Bond Edition running 4.3 and it's vulnerable on several of the exploits. Unfortunately, CM dropped support for that phone (and I haven't seen any CM12+ builds in it's forums here on XDA) around CM10 or so. In her case, it's better for her to buy a new device, something more supportable. Too bad too, it has nice hardware in it but the OEM Android sucks, bad.
[RAZR HD Android Development] Zeljko1234:
As I wrote in the first post about Droid 2 Turbo or X Force, it's new, too expensive now but probably the best successor of our current device. I don't like OLED, unnecessary high resolution and 810 is reported as problematic. Let's see reviews, especially user reviews and is bl unlockable (probably not for Droid but could be for X Force).

Would be just awesome that we all move to the same device. I get used to nice community.
[RAZR HD Android Development] niksy+:
Ugh... I'd flippin LOVE to have this bad boy :) But it's definitely out of my price range... I'm more thinking about the first Turbo or the Ultra, and that won't happen in less than a few months, anyway.

But it seems that this thing is actually what Moto claims it to be. Which is incredible, IMO.

Here it faces the iPhone 6S - https://www.youtube.com/watch?v=JbQjJxtR2Hw
[RAZR HD Android Development] IronTechmonkey:
Are you sure they ended up in 11/3? I'm speaking from different device (Moto E otus), but yesterday I flashed 11/3 which still has 10/1 as most recent security patch level, and the security commits seemed to have landed in 11/4 nightly at least for my device. That security based obsolescence is a big downside of the droid-i-verse and contributor to landfill. It is nice to see CM focus on this so we can have greater security without boogle's onerousness Thanks for the mini-educatiuon about security which may have induced a second day of clean flashing here.
[RAZR HD Android Development] Zeljko1234:
Hopefully price will drope (not as second hand device with broken screen :D) and maybe, just maybe will have nice discount on Black Friday :fingers-crossed: But that will be Verizon version with all bloadware and most probably locked bl :(
[RAZR HD Android Development] rahimali:
Going slightly off-topic but it might not entirely be the fault of CM developers for dropping support for that phone as sony has been absolutely atrocious about releasing source code for their devices. My first android was a model 2011 sony Xperia Mini (MDPI) device and sony never released the source code entirely so the camera never functioned properly beyond ice cream sandwich (had a pink/purple hue because sony never released camera libs)
[RAZR HD Android Development] CWGSM3VO:
Yeah, different devices will build at different times. In CM's case, all devices appear to be built alphabetically. The HD is usually the last-ish device to be built and so it will be at a different time code-wise. In my case, my 11-04 build is actually 11-03 due to time when I built it but it usually either has more commits than official or sometimes, less (not very often). Since O comes before X, yours builds at an earlier time code-wise and thus would most likely be in 11-04 ;)

Agreed. Google has gotten a lot better on this front however as most of the patches came from Google (some didn't) that I've seen. Not sure if it's an M-backport or not however. Nevertheless, CM seems to keep on top of it and I'm glad as while I don't have exactly sensitive information on my device it's nice that only I and Google can see it (for the most part) and I'm OK with that.
[RAZR HD Android Development] IronTechmonkey:
Forehead slap; that's where I went wrong. Thank you. I actually did look up the build order assuming just that but still had old msm8960 terminology on the brain. Bad autopilot, and I just picked the wrong day to do a clean flash.

[EDIT] 11/4 did indeed have 11/1 security level but a new USB charging commit introduced a new issue with off-line charging. Just in case it happens in your ROM also: Off-line charging changes usb computer connection setting to "charging only" which in turn disables USB debugging. After using off-line charging both of those settings must be changed back manually.
[RAZR HD Android Development] CWGSM3VO:
What is offline charging? I've been using USB for adb/charging without issue here.
[RAZR HD Android Development] IronTechmonkey:
Off-line charging is the term (new to me) that CM uses to describe charging while powered off.
[RAZR HD Android Development] lcc014:
That is no good. ::( I do "offline charging" every other night.
[RAZR HD Android Development] IronTechmonkey:
I don't use it regularly but do test it during clean flashes. Where this issue might be hardware specific I've verified it only on Moto E Otus.
[RAZR HD Android Development] CWGSM3VO:
I'll try this out today.
[RAZR HD Android Development] Thibault1171:
Is it stable enough for daily use ? (no major issue, no freeze,..) I'm still running 09/21 and I think it's time to update :D
[RAZR HD Android Development] CWGSM3VO:
As I just mentioned to [MENTION=4890649]juanepichio[/MENTION], I'm one of the few folks who don't have issues. 99% of the time, CM12.1 for XT925 is a flawless experience for me. Make a nandroid and try it for yourself :) I have heard that some folks have been having issues with dirty flashing and in most cases (my experience) is due to the distance build-wise between current and what's being flashed and the CM update process can't account for things that far out of whack so it's my belief that old/stale data causes most upgrade issues.

Now if it's an issue from a clean flash, that's another matter.

EDIT: As an afterthought, I would say if you're currently running a build that is 1+ months older than what you plan to flash, you're better off to clean install. Most of you know I'm not a big fan of TiBU restores because it has the potential to restore old/stale data compared to the newer build but that's a discussion for another day...
[RAZR HD Android Development] IronTechmonkey:
Indeed. dirty flashing (and xposed) seem to account for the vast majority of false "ROM issue" reports
[RAZR HD Android Development] IronTechmonkey:
Dont bother with this with your devices. I've heard from the otus dev it seems to be otus specific including the new commit for it.
[RAZR HD Android Development] CWGSM3VO:
Not 100% sure but I think this commit today:

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

May allow me to turn on Network Time & Date again. Will have to test after building.

EDIT: meh, build broke in some java bits for a live wallpaper :( May have to switch back to Oracle Java but I suspect it may result in the same thing.

EDIT: Interesting, it built with Oracle Java. Testing.
[RAZR HD Android Development] Thibault1171:
[MENTION=4418762]CWGSM3VO[/MENTION] Thank's, I'll certainly clean flash tomorrow. Your post totally make sense, you should quote it in the first topic's message.
[RAZR HD Android Development] CWGSM3VO:
Network Date & Time no longer interfere with alarms. Both of mine yesterday went off like clockwork and the one for Monday is scheduled as it should be. I believe it's the aforementioned commit but it might have been fixed earlier by something else (not that I noticed).

Anyways, updating OP :)
[RAZR HD Android Development] Thibault1171:
Clean flashed 11/03 today, no problem so far. Still a little "thing": after clean flash, I had to delete a dozen of APN (from my carrier and a bunch of MVNO) and manually add the 2 APN my carrier really need. Someone already mentioned it a while ago
[RAZR HD Android Development] CWGSM3VO:
So I noticed today that dhacker had merged kernel 3.4.110 into CM-13.0

I just built CM-12.1 with this kernel, so far, so good (currently, CM-12.1 kernel is 3.4.108)

I've also decided to fire up my git again :)
[RAZR HD Android Development] Zeljko1234:
Good news that dhacker rides again :)
[RAZR HD Android Development] amedeh123:
Dunno what kind of black magic you do on your builds, but they are way smoother than stock.

Looking forward to cm13. Im eager to try doze

And happy to know dhacker still plays with his RHD :)
[RAZR HD Android Development] CWGSM3VO:
After more testing, appears I was wrong. Network Date & Time still break alarms :(

EDIT: Working on figuring out RTC.

EDIT: So after plenty of trial and error, I finally gave up. I learned a few things along the way:

1 - newer android kernels use the android alarm wakeup mechanism instead of rtc although it appears it can be backed or supported by rtc if desired. based on what I've read, this seems like a good fix. Unfortunately, all the squashed commits I could find seemed kernel specific or device specific (I couldn't find anything generic enough or complete enough to build). This requires someone with more skill than I and most likely, would be a requirement or at least recommendation for CM13. Given time, I might be able to retro-fit it or find the magic commit.

2 - QCOM + RTC = modem. Simple as that. I kept approaching this from the Linux perspective instead of device-specific. QCTimeServiceDaemon + friends do all the magic. End of story. Right or wrong.
[RAZR HD Android Development] Thibault1171:
Hi, have you guys seen this CM post?
[RAZR HD Android Development] Zeljko1234:
AudioFX is in CM anyway, themes too (maybe not the same), etc. Only dialer is maybe interesting. I was hopping for CM13 announcement.
[RAZR HD Android Development] Thibault1171:
No, not yet, sorry.
[RAZR HD Android Development] CWGSM3VO:
The dialer app has been a source of a lot of controversy as it publishes contacts/phone details to a 3rd party they've partnered with. For someone with privacy concerns, this could be an issue.
[RAZR HD Android Development] Zeljko1234:
Stock LP dialer is cr.. in (almost) any way.
[RAZR HD Android Development] md07:
but we can flash official C-app pack for CM12.1. And allmost worked perfectly !

https://cyngn.com/c-apps