yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] alfick3:
Well, for one thing, if you tap on the name of the upgrade when you check for upgrades, it'll give you the change log.
[Moto G Original Android Development] Raju-Kol:
Check what's new in the latest builds on https://www.cmxlog.com/13/falcon/
[Moto G Original Android Development] Gill Android:
Thanks for the reply. I updated from 12.1 to 13 wiping Cache and Dalvic. I didn't wiped Data because I was afraid the ROM zip will get deleted as it was in Internal. Can I wipe data without any issues?
[Moto G Original Android Development] razor001_:
It will be fine.. Wipe Data erase App aplications and its data only... so make a back up of your apps if you don't want to download them again.

If my memory its good I think that Internal memory appears as userdata on recovery. Update your recovery too if your using something less than 2.8 of Twrp. And make sure you downloaded the right Gapps for CM13.

Edit: just checked and Internal memory appears as Internal Storage on TWRP 3.0 and up
[Moto G Original Android Development] Gill Android:
Thanks for your suggestions. I went ahead and made a Clean install and now I am facing ZERO problems at all. ROM is smooth as butter. I suggest other members also to always make a clean flash. It is worth the effort.
[Moto G Original Android Development] hal9008:
The same happens here, the power button stop working very often. I do not believe that in my case is hardware failure, because the double-click open the camera normally.

After restart (with an software), the button power return to work.

I suspect the MX-Player may be causing it.
[Moto G Original Android Development] razor001_:
I have exactly this problem, but I always thought that its was my button fault so never report it in the past... And I don't think that MX-Player is the cause because I don't have it installed on my device. And as you said a reboot in my case through X-posed installer and its fine but it fails again after some hours maybe 18hrs to a day after the last reboot.

Edit: Something that I noted is that this happens more frequently when using stock kernel... When I was using [MENTION=4723408]hurtsky[/MENTION] Kernel it happened but its less likely to occur.

PD... I stopped using Hurtsky kernel after the last couple of commit changes that were made recently.
[Moto G Original Android Development] Raju-Kol:
Is it me or did anyone else also faced this?

It seems to be the 2nd time that the battery saver is not working properly, last night I was watching YouTube and when the battery went to 15%, I turned the screen off and went to bed. Today morning I found out that the mobile is off, battery got all drained.
[Moto G Original Android Development] UltraMaks:
OK, now I have it again (I used to think that the issue had gone but now it's back again)

Yesterday I restarted the phone to make it sleep correctly, today I charged it up to 100% and then the phone was awake all the time... (at about 6 hours)

Look at the screenshots. Can you find the root cause of this issue?
[Moto G Original Android Development] moralesnery:
Go to Settings > Privacy > Privacy > 3 dot menú > Check "Show built in apps" > Find "Google Play Services" and keep it pressed > Look for "Keep awake" permission and disable it > Reboot.

That worked for me some months ago when I was having the same problem.
[Moto G Original Android Development] koshikas:
dude i think you have taken the 'kernel wakelock' screenshot (reads as taken when the phone was only awake 18%) at a different time with other screenshots, that doesnt to do well to do good checkup. looks like the phone has been awake for 6+ hours (72%). no regular apps (including google play service) have misbehaved.
[Moto G Original Android Development] UltraMaks:
No, I did all the screenshots at one time. I do not know why it shows different time usages

The problem here is that I can reboot the phone and take statistics, but after reboot it starts working OK. So I need to reboot it, take new statistics, charge it and see if it starts "not sleeping. So I just rebooted the phone and started charge it again to see if the issue comes again. if yes - I'll take other screenshots

---------- Post added at 01:20 PM ---------- Previous post was at 01:18 PM ----------

It's set up as "disabled by battery optimization" so it's all ok here
[Moto G Original Android Development] moralesnery:
I don't want to hide the drawer button, just move it to the lower-right side of the screen (old Touchwiz style). Protected Apps won't let you do that, sorry if I was unclear.
[Moto G Original Android Development] UltraMaks:
about reboots.. sometimes (not very often) my phone also reboots. Just now it rebooted, I tried to create logfile and found out interesting...

I wonder why do I have 2 records from 06:51 time and then only the records after the phone started booting? Where are all the logs that should have been created before reboot?
[Moto G Original Android Development] Elador:
I updated from 13062016 or so to 24062016 today and now got Google Play Services force close all the time, the system is not usable anymore (i.e. several close popups per second). Wiping cache & dalvik cache doesn't help. Interestingly what also happened is that the AOSP apps weirdly appeared again so I had 2 calculators (i.e. 1 from AOSP, 1 from Google), 2 "Clock" apps, etc. I uninstalled them but the Play services keeps crashing. I got Play services 9.2.56, which seems to be the newest.

Any ideas?
[Moto G Original Android Development] virajmalia:
Is there a chance that cyanogenmod is working on Android N beta?
[Moto G Original Android Development] alfick3:
Not until the source is released.
[Moto G Original Android Development] Choochter:
Do a clean install
[Moto G Original Android Development] AndroidHtc101:
Elador, I had this same problem. With the latest builds you need to Clean Install something about the rom increasing in size. Also flash xposed again and Gapps.
[Moto G Original Android Development] samkpo:
Also use a small gapps package, micro or smaller, it's quite well explained a couple of posts back

Enviado desde mi Moto G mediante Tapatalk
[Moto G Original Android Development] obbies:
I didn't manage to make gapps work. it force close all the time making the phone unusable.

I Flashed cm-13.0-20160626-NIGHTLY-falcon.zip.

I tried a clean install (wipe everything in TWRP) before applying cm13 then gapps => same results.
[Moto G Original Android Development] Choochter:
Did you reboot between flashing ROM and Gapps? Don't (if you did) - flash both, then reboot.
[Moto G Original Android Development] zeratos:
I am on the 20160624 build and I don't have any problems with it, did a clean flash and using xposed.
[Moto G Original Android Development] UltraMaks:
I wonder, why my phone shows different free space in PC's Computer and in Total Commander?
[Moto G Original Android Development] methuselah:
Damn that screen on time is t

Real ?? It's marvellous your falcon is giving this much of sot
[Moto G Original Android Development] zeratos:
Yes, it's real, that's why I attached the screenshots, with the last 4 percent it ended up giving like 8 hours of screen time and I never turned on the battery saver thing.
[Moto G Original Android Development] Eurofighter_ty:
[MENTION=5075128]LuK1337[/MENTION]

Factory reset protection can be implemented on our device ?
[Moto G Original Android Development] methuselah:
Thank you for continuous support for this device ... We are thankful to you continuous development...
[Moto G Original Android Development] UltraMaks:
Now here it is again. Charged the phone, unplugged, and for almost all 4 hours after this it stayed awake...

Any thoughts of why it can be?

PS as soon as I have restarted it - it started sleep well
[Moto G Original Android Development] moralesnery:
Hey there, you can't set Google's Factory Reset Protection on the phone BUUUUUT you can root and then install Cerberus, installed as a system-app will survive a factory reset and help you locate the phone.
[Moto G Original Android Development] karthikkh20:
N for Nougat
[Moto G Original Android Development] methuselah:
I know ! That already . but as luk said there was no need to say again
[Moto G Original Android Development] osrox:
Hi,

I had installed this rom in Jan'16 on my father's work phone.

& He hasn't updated it, till now.

Is the latest build, stable enough, to be flashed.

As i don't want him to face any issues with phone, while doing any important office work, in day to day usage !

If there are any bugs, kindly let me know.
[Moto G Original Android Development] sathvik07:
Yes it is stable.....no bugs....
[Moto G Original Android Development] Okruzam:
Some apps like google+ and Vodafone app are not compatible, why?

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] UltraMaks:
Why don't I have options for reboot? And how can I remove Owner and Guest from this Power Menu?

Developer options is ON, advanced reboot is on, so what is wrong here?
[Moto G Original Android Development] karthikkh20:
Where can the reboot option be displayed if there is no space there... Try to remove some option with the help of "+" option u might find reboot option...

Looks like ur using some launcher or xposed module.
[Moto G Original Android Development] razor001_:
Go to settings > buttons > power menu then select reboot menu and deselect change profile. :good:
[Moto G Original Android Development] UltraMaks:
Thanks, I was looking where can I find this settings.. I do not know why but my phone started to unlock very often in my pocket (calling numbers, sending messages, launching apps, modifying settings). As i understand this is due to my Guestures enabled but earlier I did not have such problems. Seems like my touchscreen became very sensitive )
[Moto G Original Android Development] Forever Alone:
Kernel won't compile !!

Hey guys Im new to kernel building but I tried building falcon_defconfig from CM's source code using Linaro 4.6.2 and got this stupid error :

arch/arm/mach-msm/msm_watchdog_v2.c: In function 'init_watchdog_work':

arch/arm/mach-msm/msm_watchdog_v2.c:902:3: warning: 'tzbsp_cpu_count' may be used uninitialized in this function [-Wuninitialized]

error, forbidden warning: msm_watchdog_v2.c:902

scripts/Makefile.build:307: recipe for target 'arch/arm/mach-msm/msm_watchdog_v2.o' failed

make[1]: *** [arch/arm/mach-msm/msm_watchdog_v2.o] Error 1

Makefile:955: recipe for target 'arch/arm/mach-msm' failed

make: *** [arch/arm/mach-msm] Error 2

make: *** Waiting for unfinished jobs....

How to fix this? Or can someone link me any 'working' toolchain?? I just want to compile kernel.
[Moto G Original Android Development] moralesnery:
Disable motion-detection gestures then.. your battery life will be increased and won't have that kind of problems.
[Moto G Original Android Development] UltraMaks:
There is no such option. Only "Ambient Display". "Hand wave" and "Pocket".

It's easier for me to put pattern for unlocking as I have forgotten what it means to use power button :)
[Moto G Original Android Development] FernandoJjr:
today build already have July patch?
[Moto G Original Android Development] koshikas:
nope, google has not officially released it yet
[Moto G Original Android Development] razor001_:
This behavior now it's normal, that's because some days ago, CM team did a revert on a commit that check if proximity sensor was covered before turning on the screen. :crying:
[Moto G Original Android Development] ReOmbra:
Someone think that will be useful (for battery saving) make an option in gestures ( hand wave, pocket mode) to wake up the phone only when arrive a notification?
[Moto G Original Android Development] Eurofighter_ty:
[MENTION=5075128]LuK1337[/MENTION] [MENTION=5778309]luca020400[/MENTION]

When I restore a TWRP backup just the system partition I get: extractTarFork() process ended with ERROR: 255.

I post here beacuse there is no official TWRP thread. The TWRP is 3.0 get from the TWRP website.
[Moto G Original Android Development] LuK1337:
Your backup is ducked.
[Moto G Original Android Development] gioyocho:
hey all. i have 3. questions.

1. how i change my application menu? i mean there is alphabetical design on cm13 and i don't like it

2. i get update notifications often, when it will be stable?

3. "every power on" time there is attention, that buttloader is unlocked. is it ok?

thanks, peace

oh sorry. i wrote in wrong section, i have moto g 2015
[Moto G Original Android Development] UltraMaks:
Did not catch what you mean exactly. Now I see that the phone gets unlocked even when it is in my pocket that is not correct behavior (I guess)

I wonder why they did it?
[Moto G Original Android Development] razor001_:
Well, before the revert every time you pressed the power button the phone checked that the proximity sensor wasn't covered, If covered then screen wont turn on, unless double press of power button (this is the camera gesture). They did a a revert of this commit https://review.cyanogenmod.org/#/c/146191 .

So this is a normal behavior for now until they find another way to fix it... If you want to avoid it then disable motion gesture (Ambient Display).

Edit: the latest Nightly with that commit is "cm-13.0-20160701-NIGHTLY-falcon.zip" but download link is not available anymore on CM Servers... Maybe other XDA user has it and can Upload it for you if you want it.
[Moto G Original Android Development] sevenrock:
Bulletin was released: https://source.android.com/security/bulletin/2016-07-01.html
[Moto G Original Android Development] moso11:
Found it on Reddit.

Is Falcon gonna get some love this time?
[Moto G Original Android Development] UltraMaks:
You know what, I have 20160628 build and when I cover (by my finger) the proximity sensor and press Power button my display does not turn on, so I'm ok with it...

I think the problem in the fact, that when I put my phone into my pocket display gets turned on somehow and then it gets unlocked and starts pressing all the buttons and touchscreen by material of my pocket. Strange... 1 month ago I did not have this issue, but now I have it almost everyday if I use "Ambient display"

to all

guys, I'm totally confused with my issue that I already raised many times (the issue is: when the phone is charging and then I disconnect it from the charger sometimes (about 50%) it cannot go to sleep. The only workaround here is to reboot the phone and then it starts sleep as it should)

This is the last message that I post here but did not received any ideas. I do not know what can I do and who can I ask if not here... Any ideas why the phone stays awake after charge (not always, only about 50% cases) but everything gets settled after reboot??? I've been dying of seeing this issue for months but I've been using CM for years and only several last months I have this problem :eek:
[Moto G Original Android Development] moso11:
I am also facing this Ambient Display 'bug'. I haven't find any workaround for it. I had to disable both pocket mode and hand wave.
[Moto G Original Android Development] tlwhitec:
Seems not entirely falcon-specific I saw similar complaints here. Sadly I don't see any real solution or root cause. Could that airplane mode workaround help? Have you already reported this on CM's jira?
[Moto G Original Android Development] UltraMaks:
Hmmmm. I will check if airplane on/off can help and let you know

No I have not posted anything on jira as I think it's only for cool developers. But if I can do it, send me a link I will try to report this issue :)
[Moto G Original Android Development] koshikas:
here is a test you can try. keep "Ambient Display" enabled, and cover the proximity sensor and let a notification arrive and see whether the display lights up or not. I'm pretty sure the proximity check is not working (atleast with Ambient Display) because of the temporary revert of functionality.

i missed this. there is nothing wrong in the stats shown. usually the phone is kept awake when you plug in the charger (or any USB power source). the wakelock is named as qpnp-charger-*******. i dont see that in your stat. and it should be released when you unplug. i have had similar issues of the same wakelock keeping my phone awake in the past, which i was able to always fix by wiping cache/dalvik cache in the recovery.
[Moto G Original Android Development] UltraMaks:
It works! If I keep the sensor closed by my finger the display does not light up (stays black). As soon as I put my finger off - it lights up

Almost every week I update my firmware by wiping system, cache/dalvik (no data wipe), installing a new .zip and zip of opengapps pico software, so the fix of wiping cache/dalvik is not my case :(

But even if the problem in some qpnp-charger-****** (just checked my kernel wakelock log - no any qpnp-charger-******* name there....) daemon it's definitely a firmware problem and why only me is facing this issue?
[Moto G Original Android Development] koshikas:
i think its because of the "wake phone when you take it out of pocket" feature in ambient display. if there is a control feature to disable it (wake phone when you take it out of pocket), try it with it disabled. frankly i've run into the same issues you have when i was using the same feature in CM11/CM12 (much worse with lockscreen UI freezes), keeping the phone in my pocket with other stuff. most of the time it requires the proximity sensor covered perfectly , which will hardly be the case if you have stuff in there. have only used it when i keep the phone on desk ever since.

do you dirty flash or clean flash?
[Moto G Original Android Development] UltraMaks:
I do not understand you thoughts. If I disable ambient display - there are no any issues at all. The display turns on only when I press power button. I have issues only when Ambient display is on, and removing my phone out of the pocket I see that there a numbers of applications are running and some settings are open. This means that the phone was unlocked somehow in my pocket.

already told: wipe system, cache, dalvick cache then installed new .zip firmware and new .zip of opengapps pico software
[Moto G Original Android Development] koshikas:
what i meant was on few ambient display implementations, they have a separate control to disable "wake phone on taking out of pocket". clearly yours only have feature to enable or disable ambient display only, so it doesnt apply to your case. i'm afraid i dont see how you can get this fixed if you keep it on and in your pocket.

as for the charger wakelock, it can be a hardware failure.
[Moto G Original Android Development] UltraMaks:
That's it... seems like the phone lights up the screen in my pocket somehow and then it gets unlocked etc... mystics :)

Agree, but this is what I wanted to clarify somehow...
[Moto G Original Android Development] sinedoOo:
Can you recommend me one of latest builds that doesn't suffer for any essential bugs? For daily use?
[Moto G Original Android Development] evil_cherokee:
Is there any?
[Moto G Original Android Development] karthikkh20:
Anybody tried the C-Apps released yesterday for M
[Moto G Original Android Development] razor001_:
The latest nightly + latest Opengapps with a Clean Flash and you'll be really happy with it as a daily driver... Whenever you wanna update just do a Clean Update and you're done.
[Moto G Original Android Development] UltraMaks:
So again, yesterday I charged my phone (not at 100%), left in airplane mode for the night and now you can see this

Despite the fact that the phone was in arplane mode and was not used at all the discharge process was very fast. I also included all screenshots from the Wakelock Detector (Kernel wakelocks) to show all that could lead to this issue. Any ideas? What the hell is keeping my phone "awaken" all the time after charging??? Maybe it's time to make a clean install wiping all the data and reinstalling from scratch and applying one by one all my personal data/programms to see what can cause this?
[Moto G Original Android Development] UltraMaks:
Admins, pls delete this post -> double quote
[Moto G Original Android Development] Mendibil:
Nobody?

I'm gonna give them a try, and I'll post.
[Moto G Original Android Development] koshikas:
i thought you said you always clean flashed, rechecked and then saw you always leave the 'data' intact (which makes it a dirty flash). could very well be the reason to this issue. inbetween minor changes in nightlies keeping 'data' is fine, but then after awhile you may run into issues of this sort. and again whatever that is keeping the phone is not reflected in the wakelock stats.
[Moto G Original Android Development] UltraMaks:
So all I wonder - is HOW to find the root casue of this "keeping the phone awaken"??? If there is no any kernel wakelocks cause this - what can ot be?
[Moto G Original Android Development] Mendibil:
CApps installed and working fine. Totally recommended, they look really nice, much better than the stock ones.

I still have a question about them. Do we have to flash the zip everytime we want to update them?

Thanks in advance to the one(s) who answer.
[Moto G Original Android Development] navaneethkom:
No need to flash it again once you done it.Just like the gapps.
[Moto G Original Android Development] Mendibil:
Maybe i've not explained clearly my question, so I'll try again.

What I want to know is how do we update the apps included in the CApps package, since they are not available in the Play Store. Do we have to flash de CApps zip everytime an app gets an update?

Thanks for your answer.
[Moto G Original Android Development] navaneethkom:
C-apps zip wont get updated I think.They did only one relase of the package for cm12.1 and hope there will not be any further update for cm13.
[Moto G Original Android Development] ch@ts:
Does the cyanogen dialer show ads like the true caller dialer it's based on?
[Moto G Original Android Development] luca020400:
No it isn't going to happen anytime
[Moto G Original Android Development] ch@ts:
Thanks for the quick reply!
[Moto G Original Android Development] duluc:
I just flashed CM13 to my trusty Moto G backup phone (my LG G4 went bootloop), after around 2 years, and I want to comment how smooth and stable CM has become. Congrats guys. Keep it up!
[Moto G Original Android Development] arjun1459:
does new build contains cynogen mods too ????????????
[Moto G Original Android Development] alfick3:
What?
[Moto G Original Android Development] Dariovsky:
Hi everybody! I'm pretty sure that this isn't a CM-related problem, but I need your help, people!

In my house there are two XT1032, one owned by my mom the other one by my little brother; both running the latest CM13 nightly

Today my brother came to me and said that the WiFi was pretty poor on his phone. I took the phone and installed WiFi Analyzer and, in fact, the phone only can reach our network, meanwhile the cell of my mom can reach our network and the networks of our neighbors

So I made a quick test: At the same distance from the router his phone can get 2 Mbps of link speed, meanwhile my mom's phone get 65 Mbps of link speed

I thought that could be a bad radio firmware, so I flashed the latest one and no improvement :(

Then I tried backing up the /persist folder from my mother's phone and restored on my brother's phone and no improvement at all

What else can I do? Try another Radio Firmware? Maybe EU instead of US? Maybe is a hardware related problem, in that case, where is exactly the WiFi antenna on the moto g? Is there a way to improve the signal?

Please please help me, and thanks you all for you time, my friends :)
[Moto G Original Android Development] RobotG97:
May I have the link for the CApps zip, please ?

Thanks.
[Moto G Original Android Development] arjun1459:
https://www.youtube.com/watch?v=hDiZ_sXxBDo

talking about this
[Moto G Original Android Development] koshikas:
dude the mods are for CyanogenOS and this is CyanogenMod. while they are related, they are not the same.

Edit: did bit of research. it seems if you have C-Apps running with CyanogenMod you can use these mods
[Moto G Original Android Development] alfick3:
Goto the cyanogenmod website
[Moto G Original Android Development] koshikas:
https://cyngn.com/c-apps
[Moto G Original Android Development] RobotG97:
Thanks a lot. :)