yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] niki101:
How my screen doesn't eat much battery:

What I do to save battery is turn down my screen light intensity to very low levels by changing the R,G,B values to 30/100 in the settings> display> LiveDisplay> Color calibration. This really acts as a big plus during night (many users install apps like dimly etc. to handle this). So I think my screen utilizes much lesser power than most others. Hence, cpu using the battery is the major concern - for me. Most of the time, when screen is on but no other activity is taking place, the phone tends to use 787Mhz which in normal cases is ~20% of the time (stats in kernel auidtor). However, if you set the minimum to 300Mhz I think it can really save up a lot of juice. And this whole thing does make sense too. Because majority of the time what many might be doing is just reading or seeing screen (not actually tapping/scrolling which happens for only fraction of seconds).

Battery life based on usage:

Rarely- 2 days,

Average- 20hrs,

Moderately Intense- 5hrs,

Highly Intense (i think)- 2hrs

Relevant info:

Device- Moto G falcon

ROM- CM 14 nightly 20161123

Battery mode: Balanced/Efficient

CPU governor- On Demand

CPU management apps- ROM toolbox lite, Kernel auidtor, L root .. and Oh! "Greenify"

If anyone knows other better ways/tricks, please share. :)
[Moto G Original Android Development] kamesh_kraken:
Go to that thread. Watch the video. It's simple.

---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------

It's working. So, why not?

---------- Post added at 01:43 PM ---------- Previous post was at 01:40 PM ----------

It's available now 30/11.
[Moto G Original Android Development] Sound Anarchist:
I've wiped system, cache and dalvik-cache. Then proceeded flashing the zips.

I managed to fix the issues I had by updating (or reinstalling) the apps from the Play store.

I also had issues with apps that use my gmail accounts credentials for login (Ingress, IFTTT, etc), while some Google apps that don't use my accounts were working. So I think that the bug lays somewhere in the use of the google account for login in apps.
[Moto G Original Android Development] kamesh_kraken:
I updated it using CM Updater. I'm on 30/11 build. It's smooth and flawless than other build. And the Pixel Animated Navigation bar is working. See the previous page for the Navigation bar link!

CMBugReport still crashes.
[Moto G Original Android Development] jawr:
I repeat my question, does anyone has usb tethering working? Could someone please check that and give me an reply?

Thanks and regards
[Moto G Original Android Development] kamesh_kraken:
It's working on 30/11 build. I confirm.
[Moto G Original Android Development] matmutant:
I am tempted to answer "your arguments are invalid", but I will take time to answer fully later today

For now I ask you to read a little about Falcon's screen technology and how it works

The only thing I agree is about usage: every user is different, I don't read on my device so I am either scrolling or typing most of the time... But when I read and don't need fancy graphics I set the device in powersave :cool:
[Moto G Original Android Development] vkp1997:
To all my friends at XDA, Here You GO :

Pixel Navigation Bar animation for falcon, right from its own Systemui.apk:laugh::laugh::cool::cool:

Everything is working.

https://drive.google.com/open?id=0B8iuKPeUl0SgblV6eUpmTHVBdnc

AMBIENT DISPLAY WORKING.

THANKS TO [MENTION=7868666]Tintumonn[/MENTION] for help.....

I couldn't have done this without his help

Note:- This System apk is from 30 november build.

i dont know wheteher it will work in builds before 30 November.

Go to http://xdaforums.com/moto-g/general/cm-14-1-pixel-nav-animation-button-moto-t3509255/

For more details...
[Moto G Original Android Development] niki101:
A quick Solution to your problem is- Reinstall those apps from play store.

Find them - Uninstall them - Install them again.

You wont get error messages then. :)
[Moto G Original Android Development] fxcatalyst:
I flashed the updates through twrp and never flashed gapps each time . After flashing update, just wipe cache & dalvik. It worked for me Every time..:)
[Moto G Original Android Development] captpksingh:
d

In TWRP you have options in setting to choose after flashing. You can set it once and thereafter twrp will take care.
[Moto G Original Android Development] Allstargaurav:
Ota update is not available for me

Anyone know how to fix it
[Moto G Original Android Development] abegc:
i want to revert back from stock kitkat optimized rom to cm14.1 nightly build, i format data and flash cm14.1, it boot properly, but it shows that (no external storage available ), i cant find any system file/folder when i open the file manager. my play store keep crashing whenever i want to install apps, and i suspect that i have been messing with partition (i think). please anyone know how to fix this? currently have no phone to use.. :(
[Moto G Original Android Development] karthikkh20:
It s saying corrupt... Unable to install
[Moto G Original Android Development] Subinsmani:
Sry plz will u elloborate what problm...

set from moto g 2015 ussing taptalk
[Moto G Original Android Development] karthikkh20:
Let me take a SS
[Moto G Original Android Development] vkp1997:
It's not an app to install. Follow the XDA link in quoted post for tutorial.
[Moto G Original Android Development] Subinsmani:
Ohhh ya...

Now get the prblm...

My friend this is not an app.. this is system file...

No need to install manually it decompile automaticallly...

set from moto g 2015 ussing taptalk
[Moto G Original Android Development] karthikkh20:
I am getting...Package is corrupt error while installing the apk
[Moto G Original Android Development] Subinsmani:
Bro pease follow our xda form and watch video were we make for u only... U will follow them or i have give u all step by step on that form please follow..

set from moto g 2015 ussing taptalk
[Moto G Original Android Development] karthikkh20:
Wow... Working great.. Thank You
[Moto G Original Android Development] karthikkh20:
Do I have to do this for every nightly update ?
[Moto G Original Android Development] Subinsmani:
Ha ha ha Yah,,,

So u can Make one flashible zip then no need to do same process only u have to flash from TWRP recovery
[Moto G Original Android Development] captpksingh:
May I request you to kindly make one flashible zip for us please.
[Moto G Original Android Development] Subinsmani:
Sry i havent ur model for testing and all...

If u have any flashible zip file plz give me... Will try to make flashible zip file too..

set from moto g 2015 ussing taptalk
[Moto G Original Android Development] captpksingh:
Is there any means of stopping Mobile Broadcast message? It's very irritating.
[Moto G Original Android Development] Subinsmani:
Long press ur mobile broadcasting from n9tificatin..

Go to more setting then click mobile broadcasting the go to permission dissable permission from there thats it..

set from moto g 2015 ussing taptalk
[Moto G Original Android Development] captpksingh:
Thanks a lot. I'm only using "MotocamByTheroyalseeker_v3" zip file apart from ROM.
[Moto G Original Android Development] matmutant:
I am lacking both time and available data, but here is a start :

screen technology : IPS

- Contrary to AMOLED, the backlight is made of a few LEDs on one side of the screen that diffuse white light through a specific material to the LCD chips.

==> on the attached pictures you can see the ripped-off back-light LEDs placed where they should be under the screen (actual Falcon screen and back-light LEDs), and some close-up picture so you can see one of them better

- OK LCD chips needs voltage/current get into transmissive state, but that's absolutely negligible compared to the high power LEDs used for the back-light.

- Using color calibration to 'dim' color intensity won't save juice (but reduce eyestrain, I agrees and use livedisplay nightmode feature), if you are trying to reduce back-light with it won't work, if you think it will reduce power used by the LCDs.. I really doubt it. at best you won't get better battery life.

CPU :

(this is where I need more data and time to explain better

- I can't find it but afaik, CPU voltage has only two stages on our device: either something like 1140mV (from 300 to 787MHz) or 1150mV (from 998 to 1190MHz)

- I can't compare CM13 and CM14.1 with my devices as I don't have the same usage on both (one is for sms/calls/3g, the other one is for games/videos/music), so if I show you my own comparison graphs you will assume CM14.1 is always at high freqs, but that's my usage that bias the results.

-If you want some accurate data, what you can do is the following:

reboot and use your device for a full battery cycle with your 300MHz settings, when at 10%:

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

copy paste the values here.

Do the same with default 787MHz settings

I'll make the graphs from your raw data :)
[Moto G Original Android Development] captpksingh:
Thank you very much for your support. I did as suggested however I didn't get disable permission option instead I'm getting option for choosing different level of importance. Sorry I'm unable to upload screenshot.
[Moto G Original Android Development] niki101:
you clearly have more info + knowledge than me. I assumed i was helping out by telling the user side experience and also that light intensity is directly proportional to battery usage (which I still do believe but I agree that it may be complicated).

But on my sde as well, lack of time due to my exams wont allow me to check for these things. May be later I will try it out to check and see. I will share if find something interesting. but obviously you know all of it already.

Keep up the good work!

---------- Post added at 07:34 PM ---------- Previous post was at 07:28 PM ----------

long press on that notification. > more settings > press 2-3times on the name/heading- "mobile broadcast". permissions' page will open up. (u can also select level 0 notification for it to disable it popping up)
[Moto G Original Android Development] captpksingh:
Thanks once again. I'm waiting for next mobile broadcast message to appear so that I may do the needful.
[Moto G Original Android Development] matmutant:
I am always happy to discuss with someone that take time to argument instead of complaining, that's mostly why I took time to answer you :)

(and btw I agree about the light intensity and battery life -which is obvious for back-light-, though when dimming using the calibration tool you only darken the colored pixel (LCD) on the actual screen not the back-light itself, so less light come to your eyes, but the same amount light is emitted from the LEDs it just doesn't pass through the LCD, to illustrate that, turn back-light to maximum and set the calibration tool to 10%, the grayish color you see is from light that leaks through the darken LCD chips -which also explains the "bad" grey to grey contrast IPS has compared to Amoled-)
[Moto G Original Android Development] aouerfelli:
This is a very mature way to handle the issue, which is rarely seen in the XDA community. Just wanted to thank you for that.
[Moto G Original Android Development] tpa-moto:
You might also wanna throw in

cat /sys/devices/system/cpu/cpu*/cpuidle/state*/time

Anyway, there are three main voltages (SVS, NOMINAL, TURBO, called corner voltages). Each frequency is associated to a corner and its is further adjusted depending on the current stability of the CPU and on some factory determined values that are stored inside some e-fuses.

You can see the initial values and the limits of each corner voltage reading the dmesg:

dmesg | grep cpr_pvs_init
[ 0.440976,0] cpr_pvs_init: pvs voltage: [1140000 1140000 1150000] uV
[ 0.441176,0] cpr_pvs_init: ceiling voltage: [1140000 1150000 1280000] uV
[ 0.441414,0] cpr_pvs_init: floor voltage: [1140000 1140000 1140000] uV

The first line reports the initial voltages, one per corner, the second and the third lines report the upper and lower limits respectively.

If I remember correctly the first corner voltage is for the frequencies up to 600MHz, the second one for those up to 1.1GHz and the last one for 1.2GHz.

If you wonder why the floor voltage is 1.14V for all the three corners, well, that's because some devices can't handle anything lower than that and so Motorola set that limit. 1.14V is quite a high value, so high that the first corner voltage is basically fixed and the second one is quite limited. Also, because of this high value it's almost guaranteed that the CPU uses the same voltage for all the frequencies up to 787MHz, if not for all of them. This is also one of the reason why using it as min frequency is not so detrimental.

That said, the power consumption can be greater or smaller depending on a lot of factors that can't be determined without testing.

There are also several power profiles, just use them. You don't like the 787MHz limit while the screen is on? Switch to "Efficiency". You want performance without killing the battery? Keep using "Balanced". If you really can't stand any profile and want to manage everything on your own, remove or rename /system/lib/hw/power.msm8226.so.

You could also do some rough measures by reading the output of /sys/class/power_supply/battery/current_now, which tells you the amount of current that flows out of the battery. If you do some tests in a controlled manner, you could get an idea of the actual power consumption.
[Moto G Original Android Development] matmutant:
Thank you for this post, you've filled in the gap I left in my explanation!

I totally forgot to talk about efficiency mode and didn't remember voltage were displayed in the dmesg :silly:

:good:
[Moto G Original Android Development] zeratos:
Is there a way to enable tri state location on the status bar?
[Moto G Original Android Development] BryanByteZ:
So let's see if the noob here understand it all

The min/max bright of the screen is irrelevant? It will take the same power on min and on max?

And a personal doubt, what consume more power 1 core at high freq or 4 cores at low freqs?
[Moto G Original Android Development] tpa-moto:
No, the LEDs are dimmed using PWM. Basically the backlight is turned on and off very quickly. When you lower the brightness, you increase the amount of time the backlight is kept off.
[Moto G Original Android Development] abegc:
i want to revert back from stock kitkat optimized rom to cm14.1 nightly build, i format data and flash cm14.1, it boot properly, but it shows that (no external storage available ), i cant find any system file/folder when i open the file manager. my play store keep crashing whenever i want to install apps, and i suspect that i have been messing with partition (i think). please anyone know how to fix this?
[Moto G Original Android Development] Aguys:
Finally, SuperSU works without killing modem, yey! I'm on latest nightly. Download here...;)
[Moto G Original Android Development] vkp1997:
You can do this for few nightlies, I think.....untill there are some major changes to system framework in CyanogenMod. Always keep a nandroid backup. And i'll update the apk if something major changes....

And one more thing... Please don't discuss these things here. I request you to discuss these things in the thread I mentioned in my previous posts...

http://xdaforums.com/moto-g/general/cm-14-1-pixel-nav-animation-button-moto-t3509255/
[Moto G Original Android Development] Raju-Kol:
The battery saver mode is draining more battery, yesterday it got to 5% from 12% in just 2hrs. I'm on 25.11 build, will install 30.11 build and twrp 3.0.2-2.
[Moto G Original Android Development] mohitvshah123:
One problem i find is that all these roms become laggy aftee 3-4 days of usage. Anything can be done to reduce those?
[Moto G Original Android Development] pierremg:
Messaging app still crashing sometimes without even using it. CM Bug report I preferred removing it permanently using gapps-config.
[Moto G Original Android Development] matmutant:
No,

Don't confuse

- back-light brightness (working as tpa-moto explained) and

- the color calibration tool that only set the relative transmittance of the LCD red, green and blue channels (not touching the back-light brightness behind at all)

+1

Voltage-wise 1 core at 1150mV compared to 4 cores at 1140mV...

But I have no idea how much current one core at 1190MHz draws compared to 4 cores at 787MHz...
[Moto G Original Android Development] :
Some dual SIM issues:

SIM preferences reset on reboot (from "SIM2" or "Always ask" to "SIM1")

No ringtone per SIM, only one ringtone for both.

Just flashed 01122016.

Also encryption fails.
[Moto G Original Android Development] fxcatalyst:
Is there any way to disable the second sim. I use both sims.? But only need one at a time.
[Moto G Original Android Development] koshikas:
not possible on any post lollipop custom ROMs
[Moto G Original Android Development] tpa-moto:
https://github.com/CyanogenMod/andr...se/core/res/res/xml/power_profile.xml#L34-L42 (mA per CPU frequency)

But I really doubt those are correct, probably Motorola just put some standard values for msm8226. I know they did proper measurements for msm8974 and the final values were quite different from the ones they originally used (https://github.com/MotorolaMobilityLLC/kernel-msm/commit/5f7d4850c80f3a3db4434019bcd33f9a77ffb54f) . I'd expect the same to be true for msm8226.
[Moto G Original Android Development] captpksingh:
I feel that your suggestion has helped me to get rid of the problem. I haven't received anymore broadcast message since last 7hrs.

Thank you very much. God bless you. ?
[Moto G Original Android Development] allrightlite:
That can be normal on this phone, when your battery is under 30%, because the battery is not new. Between 30 to 90% you shouldn't have this "feature" ;)
[Moto G Original Android Development] hardrockskull:
Can someone tell me why is this happening ??? I flashed the 30/11 update and flashed Gapps of 25/11 and after the phone got booted the some of the Google apps started crashing I deleted them but what is the solution and reason for this too happen have a done a mistake in flashing? Or new rom is not compatible with the existing apps? And also earlier when I used flash a ROM the data was wiped out but after 7.0 all data is still there can someone explain this also why is it happening even though I did a clean flash
[Moto G Original Android Development] matmutant:
That's why I said 'no idea' :)

and the useless conclusion about cores and power : (which 100% irrelevant here)

But IF the linked values are "accurate" (in factor, not in absolute) this gives something like:

4 cores at 787MHz = 4*83 = 332

(or 4*106 = 424 with msm8974 values)

1 core at 1190MHz = 115

(or 167)

In both case the 4 cores would be more power angry that 1
[Moto G Original Android Development] allrightlite:
This happen when you clean flash. Don't know why. I have 3011 dirty flash and no crashing gapps. Just cm-bugreport crashes all the time. You should reinstall the gapps with Play Store. But I don't know the reason for this bug.
[Moto G Original Android Development] Northwinds:
Hi there

I am on a moto g (1st edition) and started using your build a couple of months back and really happy with it, so many thanks!

Only problem is that after a recent nightly update Google Services keeps crashing and I'm now unable to use anything related.

My version now is: 14.1-20161123-NIGHTLY-falcon

Is there a newer version that might fix this or should I revert to an earlier one?

Many thanks.

Cheers!
[Moto G Original Android Development] allrightlite:
On 2511/3011 nightly I don't see any crashing on Play Service. You should update
[Moto G Original Android Development] Allstargaurav:
How to free up system space and uninstall stock cm apps?
[Moto G Original Android Development] matmutant:
1- Why do you need to free up /system space?

2- you can do this on install using the gapps custom script (see OP)
[Moto G Original Android Development] andromobilogy:
Gapps nano works well too.
[Moto G Original Android Development] matmutant:
[FIX] Swipe writing not working after Upgrade

Here is a fix for a known issue that pops up from time to time: AOSP keyboard swipe feature not working.

The following lib is needed to make it work again :

http://xdaforums.com/devdb/project/dl/?id=21432

to "install" it:

Connect your device to PC (with ADB access enabled)

Verify PC has acces :

adb devices

Mount /system as rw :

adb remount

Push the file :

adb push [source directory]/libjni_latinimegoogle.so /system/lib/libjni_latinimegoogle.so

Reboot :

adb reboot

Enjoy!

To make it survive dirty updates, you will need an addon.d shell script that automates the process instead of re-pushing the lib ad nauseam (find it here)

to "install" it:

Connect your device to PC (with ADB access enabled)

Verify PC has acces :

adb devices

Mount /system as rw :

adb remount

Push the file :

adb push [source directory]/90-latinimegoogle.sh /system/addon.d/90-latinimegoogle.sh

Make it executable and check the result:

adb shell

su

cd /system/addon.d

chmod +x 90-latinimegoogle.sh

ls -la

Expected output:

-rwxr-xr-x 1 root root 682 2009-01-01 09:00 50-cm.sh
-rwxr-xr-x 1 root root 7602 2016-11-09 14:55 70-gapps.sh
-rwxr-xr-x 1 root root 733 2016-11-28 19:10 90-latinimegoogle.sh
-rwxr-xr-x 1 root root 132 2009-01-01 09:00 blacklist

Test it by applying OTA update ;)

Enjoy!

Thank you [MENTION=4610254]CMNein[/MENTION] for the addon.d tip (http://xdaforums.com/galaxy-nexus/general/tutorial-cm9-cm10-cm10-1-script-t1617356)

PS: one can simply edit the 70-gapps.sh or 50-cm.sh addon.d and add the file path there... I just think an external dedicated script is cleaner.
[Moto G Original Android Development] NoUseToRush:
clean installed "abyss kernel 4.00 ", "cm-14.1-20161109-NIGHTLY-falcon" and "open_gapps-arm-7.1-pico-20161110" in a single shot using TWRP 3.0.

Took a few minutes and the result is just great: no bugs up to now. Happy, very happy How could one imagine to run nougat on Moto G?:good:

Thanks matmutant
[Moto G Original Android Development] peninsula33:
Please can you make an update for Turkey timezone.

In Turkey, we won't use DST anymore. We will use UTC+3 whole of year.

And a quetion:

I am using cm13 nightly 20161108. I have had a problem since maybe nightly 20160915 about duplicate notification when i use greenify boost mode. i think that GCM makes this problem. I tried wiping everything(system, cache,data, internal storage). If i will install CM14.1, will the problem still?
[Moto G Original Android Development] matmutant:
I don't really see the use of greenify anymore, more conflict risk than actual beneficial effects ... :cool:
[Moto G Original Android Development] peninsula33:
What about scrren time on cm14.1 without Greenify?

I am taking four to four and a half hours screen time with greenify while 3g is open everytime.
[Moto G Original Android Development] DPX:
I guess I'll get around 5,5h sot without greenify (atm 54% left and sot 2,75h). WLAN on most of the time (I only left the house for 2h today so I used 3g), mainly using whatsapp, chrome and from time to time some other apps.
[Moto G Original Android Development] ArjunSindhya:
Using latest nano gapps, but the usual setup procedure is missing, the restore apps screen is not shown and is replaced by some CM "help improve cyanogenmod" screen.
[Moto G Original Android Development] karthikkh20:
CM update working for anyone ?
[Moto G Original Android Development] giboto91:
Thanks dev, my moto g still alive
[Moto G Original Android Development] triggerlord:
I'm currently running this on the CDMA variant of the falcon. Everything seems to work. I flashed the MMS fix and now the service is working too.
[Moto G Original Android Development] Chaninoza:
clean flashed, everythings seems to be working (do not have any sim available to test calls)