yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] fonz93:
Battery drain has been fixed the 24th of july (only 22 and 23 nightlies were affected), there is no battery drain after that date because there aren't relevant commits and changes that could cause it. Peoples reporting battery drain should look at their use and apps before posting... I've never had any battery drain (i didn't install 22 and 23 nightlies, because i read the changelog and i knew that there could be problems), because when i use the phone, i know what i am installing/doing. I often read about people saying: "yesterday's nightly was good and today's nightly is so bad" and then i look the changelog and there aren't device specific changes nor other commits that can cause battery drain or bad performances, then i decided to don't trust those peoples and try the new nightly myself ;)

Anyway, for your information, i am running latest nightly and i haven't faced any problem
[Moto G Original Android Development] knizmi:
This!!

The ROM is perfectly stable and most of the nightliy changes bring exactly zero changes that affect performance or battery life. Once in a while there are hiccpus here and there (like the governor update in 7/22), but they get sorted out really quickly.

Thanks to Luca and a couple of other maitainers this device has one of the best maitained device trees and there are hardly any areas where CM for Moto G could get better.
[Moto G Original Android Development] InsaneMad:
Me too...

07-30 16:43:44.502 F/Environment(931): java.lang.Throwable
07-30 16:43:44.502 F/Environment(931):	at android.os.Environment.throwIfUserRequired(Environment.java:891)
07-30 16:43:44.502 F/Environment(931):	at android.os.Environment.getSecondaryStorageDirectory(Environment.java:443)
07-30 16:43:44.502 F/Environment(931):	at android.os.Environment.getSecondaryStorageState(Environment.java:769)
07-30 16:43:44.502 F/Environment(931):	at com.android.server.pm.PackageManagerService.getInstallLocation(PackageManagerService.java:14198)
07-30 16:43:44.502 F/Environment(931):	at com.android.server.pm.PackageManagerService.installPackageAsUser(PackageManagerService.java:8895)
07-30 16:43:44.502 F/Environment(931):	at com.android.server.pm.PackageManagerService.installPackage(PackageManagerService.java:8848)
07-30 16:43:44.502 F/Environment(931):	at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:850)
07-30 16:43:44.502 F/Environment(931):	at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:2025)
07-30 16:43:44.502 F/Environment(931):	at android.os.Binder.execTransact(Binder.java:446)
07-30 16:43:44.517 F/Environment(931): Path requests must specify a user by using UserEnvironment
07-30 16:43:44.517 F/Environment(931): java.lang.Throwable
07-30 16:43:44.517 F/Environment(931):	at android.os.Environment.throwIfUserRequired(Environment.java:891)
07-30 16:43:44.517 F/Environment(931):	at android.os.Environment.getSecondaryStorageDirectory(Environment.java:443)
07-30 16:43:44.517 F/Environment(931):	at android.os.Environment.getSecondaryStorageState(Environment.java:769)
07-30 16:43:44.517 F/Environment(931):	at com.android.server.pm.PackageManagerService.getInstallLocation(PackageManagerService.java:14198)
07-30 16:43:44.517 F/Environment(931):	at com.android.server.pm.PackageManagerService.installPackageAsUser(PackageManagerService.java:8898)
07-30 16:43:44.517 F/Environment(931):	at com.android.server.pm.PackageManagerService.installPackage(PackageManagerService.java:8848)
07-30 16:43:44.517 F/Environment(931):	at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:850)
07-30 16:43:44.517 F/Environment(931):	at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:2025)
07-30 16:43:44.517 F/Environment(931):	at android.os.Binder.execTransact(Binder.java:446)
07-30 16:43:45.968 E/Vold (226): Error creating imagefile (Read-only file system)
07-30 16:43:45.969 E/Vold (226): ASEC image file creation failed (Read-only file system)
07-30 16:43:45.970 E/PackageHelper(16238): Failed to create secure container smdl25713216.tmp
[Moto G Original Android Development] fonz93:
Finally someone useful :), maintaners will read this logcat and if they can, will explain the problem, meanwhile, can you check if in settings/apps, did you try to change the app installation path?

As explained here:

http://stackoverflow.com/questions/30276876/error-creating-imagefile-read-only-file-system

There could be some problem in identifying the default path for apps, there are some suggestions there, i don't know if they work, but it's a start, also, if you didn't and if you can do it, i suggest you to wipe /data, in these cases it's the clean and safe way.

This can be useful, too:

http://xdaforums.com/showpost.php?p=58409922&postcount=4845
[Moto G Original Android Development] InsaneMad:
Thank you for your answer. I didn't find this option in the settings. I don't want to wipe the data, but if I have to do ... hahaha
[Moto G Original Android Development] TakipSiLim:
Hi. Does CM supports usb DAC audio? I searched this thread but no results. thanks!
[Moto G Original Android Development] unqualified:
When using the Waze app, I've been getting a pop up error saying "com.motorola.motgeofencesvc has stopped" a few minutes after hitting the road.

Not a big deal, as the app still works after the bug notification, but here's a link to another thread on the Moto Maxx where the dev is aware and planning to fix for that device http://xdaforums.com/showpost.php?p=61970635&postcount=567
[Moto G Original Android Development] riyosakura:
I got bug with system profile on 08/01 build.

Here is how to reproduce it :

1. Set security on lockscreen, pin or pattern.

2. Create profile1 with set use system default on lock screen mode. Create profile2 with set dont use pin on lock screen mode.

3. Use profile1, pattern or pin still enable on lock screen.

4. Use profile2, pattern or pin still enable on lockscreen.

Expected behaviour :

It should disabled pattern or pin on profile 2, since dont use pin or password is used on lockscreen mode.

Anyone got this problem? Please try it and report here. Thanks.
[Moto G Original Android Development] UltraMaks:
Perfectly stable? Where is a snapshot?

No any for 12, nor for 12.1 branches... Very stable :)
[Moto G Original Android Development] the_poolee:
Soft reboots on new app launch

I had not tried any app installs since some time but when I last checked on 31/07 nightly, any new apps launched will trigger a soft reboot. I tried moving to latest 04/08 nightly but problem persists. Clearing cache in the process allowed me to launch the apps installed before. So is this a problem with the package installer as well??? Many people have been reporting this but most are saying this is a one-off problem. I'll post a log if I knew how since the log will be interrupted in between by the restart. Ideas?
[Moto G Original Android Development] christianvari:
When we will get snapshot or stable?
[Moto G Original Android Development] LeithJones:
Dialer issue

I'm using a simcard that only works for data in my single-sim xt1032. Calling and texting have been disabled by the provider at my request.

I have VoIP service configured through the stock dialer. Whenever I try to pull up my call history the dialer app crashes. I've been using dialer as a voip softphone since the whatsapp voip issue was fixed a few months ago. As far as I can recall, this has been the case since I switched from ZoIPer to dialer.

The crash doesn't seem dependent on the state of any radio, and it happens with no sim installed as well. I've also tried disabling the voip account and it still crashes when I look at the history.

log with radios off attached.

Any help would be great,

Thanks

edit: uploaded more acceptible logcat to another post
[Moto G Original Android Development] fonz93:
This will probably be skipped until you post a new logcat without xposed installed on your phone
[Moto G Original Android Development] LeithJones:
Just removed xposed. Same problem confirmed. Will upload logcat when I get to my computer

edit: logcat uploaded

edit: removed email and glsuser account ID from attachment
[Moto G Original Android Development] InsaneMad:
Hey Guys,

for anyone who was in trouble with package installer, after some research I found out what the problem was, for some reason, the installation path has been changed to external, you can use this command to confirm:

pm get-install-location

To solve just use a terminal or adb shell using root to set it to auto:

pm set-install-location 0

.
[Moto G Original Android Development] the_poolee:
Thanks buddy.... Somebody had mentioned about the storage location change a few posts back but no foolproof method to get rid off. So, finally something useful....

edit: can' t set to default location. adb shell crops up a Java security exception saying Package android doesn't belong to 2000

edit:well, tried with local terminal with su access granted at first. then gave in the command and done, new apps work like a charm... :good:
[Moto G Original Android Development] riyosakura:
No one?
[Moto G Original Android Development] Altomugriento:
Cyanogenmod version 12-1-20150808

TWRP 2.8.7.0

WIPES before install: ALL partitions WIPED

Settings , DATA USAGE, then FORCE CLOSE

unfortunately, settings has stopped

thanks for your help, sorry for my horrible english

EDIT: using Paranoid android now, same error !!!

EDIT 2: returned to a ROM 5.0.2 (Retail US 5.0.2 Stock ROM (Optimized) v1.3 (317mb)

DATA USAGE work again..... GRRRRR

thanks again
[Moto G Original Android Development] :
Using CM 12.1 8/4 nightly, TWRP 2.8.7.0, XT1032.

And I've never had force close on data usage on any nightly. Like others have said, try starting fresh from stock rom and reflash CM.

All I ever do before installing new nightly is TWRP-factory reset (data, cache, and Dalvik). After install I'll format data to get the space back rom and gapps took up.
[Moto G Original Android Development] LeithJones:
I just tried and I'm getting a lock for owner and no lock for the new user, as expected. Maybe post a logcat.

I'm on the august 7 nightly
[Moto G Original Android Development] Altomugriento:
Thanks a LOT for your answer

Here was my steps prior to install CM

ROM: 5.0.2 stock for my country

1 Unlock bootloader

2 Install TWRP 2.8.7.0

3 wipe exact like you say

4 install CM 12.1

5 wipe again

6 gapps minimal for 5.1

7 wipe again

Reboot

All perfect, except data usage

Can you please, point me to a exact procedure to return to a stock ROM?

Is really necessary ? Can i do the procedure again from this Custom rom ?

( USA 5.0.2, MODED VER 1.2)

thanks!

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Original Android Development] :
I have no idea why data usage doesn't work for you. When I need to restart fresh, I'll do advance wipe and delete everything and flash stock retail rom (untouched).

Only thing I do different than what you've done is that I use CM gapps and not gapps minimal.
[Moto G Original Android Development] tzzeri:
Do you have any themes applied?
[Moto G Original Android Development] LeithJones:
I don't.
[Moto G Original Android Development] christianvari:
I installed the last nightly with a clear installation and i found 3 bugs:

- Automatic mode in LiveDisplay doesn't work. It doesn't recognize if is day or night.

- In "app" section i found options for sd card but our phone doesn't have a sd card slot

- Battery drain in more than stock
[Moto G Original Android Development] enban:
As at least one more person, I can notice that the notification led stays on without blinking independently of the choosen options (blink duration and rate). Any workaround? I'm using 0808 version.

Thanks
[Moto G Original Android Development] Altomugriento:
Just one questión:

How do you return to stock?

Using TWRP?

Thanks

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Original Android Development] LeithJones:
http://xdaforums.com/showthread.php?t=2542219

I don't know of a way to use twrp, but if you follow the instructions in the linked post using the latest stock ROM for your region it should get you there.

On my device, I had to use:

Mfastboot flash system system.img_sparsechunk.0

Mfastboot flash system system.img_sparsechunk.1

Mfastboot flash system system.img_sparsechunk.2

Instead of the listed:

Mfastboot flash system system.img_sparsechunk1

Mfastboot flash system system.img_sparsechunk2

Mfastboot flash system system.img_sparsechunk3

So your mileage may vary.
[Moto G Original Android Development] Altomugriento:
Thanks for your time.

I am follow that Link, posting results later

Why do you use another than the listed config?

EDIT: sorry, i imagine why: because your original stock firmware have this files ( system.img_sparsechunk.0, etc etc) instead of system.img_sparsechunk1
[Moto G Original Android Development] alfick3:
Because it depends on the firmware you download. You have to extract the files from the firmware and see what files are in your firmware. His fw files had the dot zero and dot one etc. You have to set what is in your fw and adjust accordingly.
[Moto G Original Android Development] Rezakorn:
Excellent! The camera works great now! ( Google cam, not official CM12). Thanks
[Moto G Original Android Development] Shub77:
[MENTION=5354072]knizmi[/MENTION] I can confirm your kernel is ok, my camera worked flawlessy all day long, I have taken pictures with many camera apps, included whatzapp internal one. Thank you very much! :)
[Moto G Original Android Development] d33dvb:
On xt1034 the camera has no problems for me.
[Moto G Original Android Development] srisurya95:
Thanks dude
[Moto G Original Android Development] gearguy365:
after flashing this, how can i go back to stock cm12 kernel if i want to?

also does flashing official firmware replace previously flashed kernels with stock moto g kernel?
[Moto G Original Android Development] KDB223:
[MENTION=5354072]knizmi[/MENTION] , I don't know why I didn't try your kernel before! No more camera problems, everything works great! Thanks a lot for this!
[Moto G Original Android Development] IGGYVIP:
camera bug easy to fix ?

anyone still has problems with camera without knizmi's kernel ?

check if fixed after patching sdcard in TWRP manager app for me it works even with stock camera

(after applying patch and rebooting)

can anyone confirm ? (since i have not preformed clean install in a long time)
[Moto G Original Android Development] andromobilogy:
I just saw today the inbuild ROM Updater is working again :D
[Moto G Original Android Development] zpmarcos:
XDA forums is so slow for the last days that I can't download the kernel...

Can someone please upload to other site? Thanks
[Moto G Original Android Development] knizmi:
Come on, it´s 5 MB. XDA can do about 40 KB/s, so it takes about two minutes do download.
[Moto G Original Android Development] zpmarcos:
It's taking me 1 hour and 40minutes and then I get error! XDA is really really slow here!
[Moto G Original Android Development] Shometsu:
CMDA/xt1031

Can anyone notify me when the data is working for the xt1031 model?
[Moto G Original Android Development] Shub77:
Wait for someone else to confirm these checksums ( [MENTION=5354072]knizmi[/MENTION] ):

File: CM12_kernel.zip

CRC-32: 4045d725

MD4: 0b79a5ce898706631ca8e3f0d54ec540

MD5: 5b600b501790bb9cb5b0e8dc55e907cb

SHA-1: 637a6333c3d2082bd990ec0b5a67680321eb8adb

http://www14.zippyshare.com/v/w5zsg1q1/file.html
[Moto G Original Android Development] indrasatrya:
here sir https://www.sendspace.com/file/ry9vkr :D
[Moto G Original Android Development] zpmarcos:
Thank you good sirs!

Im going to test it for like 24h and then I'll give you my feedback!

Best Regards
[Moto G Original Android Development] knizmi:
Good news - KSM is soon going to be disabled upstream (still in the kernel, but off by default), so there will be no need to do anything after installing CM (flashing modified kernel is not the only way, just one of the options). The patch is currently in Gerrit and is likely to be soon accepted and mergerd into CM source.

Gerrit change: http://review.cyanogenmod.org/#/c/85586/

---------- Post added at 06:53 PM ---------- Previous post was at 06:45 PM ----------

Not on my Linux machine right now, but I´m sure those are okay ;)
[Moto G Original Android Development] FabioSan:
I hope into a re-integration of vibration control... It is horrible at the moment..
[Moto G Original Android Development] itouchables:
It's in Sound&Notification --> Other sounds --> Vibrator intensity
[Moto G Original Android Development] FabioSan:
What? I haven't see it ._.
[Moto G Original Android Development] itouchables:
I'm on the latest nightly ( cm-12-20150115-NIGHTLY)

I updated from the cm updater app
[Moto G Original Android Development] Altomugriento:
Thanks!! you response arrive in the exact moment i figure why (editing my post)

really thanks man
[Moto G Original Android Development] aqswde123:
This ROM is close to perfect, except for one thing the black screen when I turn on the screen. It happens atleast 2-3 times a day for me and i just long press the power button and reboot.

I seems to usually happen when,

1. There is a Missed call notification waiting and i turn on the screen.

2. When I am on a call using handsfree (during which the the screen is off) and the other person disconnects the call before I do.
[Moto G Original Android Development] ANDROIDRAZRM:
How well does CM12.1 work on the XT1031 at this point? I'm currently on stock 4.4.4 but I want to patch the stagefright exploit since it appears Motorola is never going to release lollipop for this phone. I just want everything to work.
[Moto G Original Android Development] ankur.walia:
Is this stagefright thing for real?
[Moto G Original Android Development] nuange:
Yes it is! But it is as every other breach we know we can't do anything to that, instead of waiting for the right update
[Moto G Original Android Development] Altomugriento:
OK here are my results:

my ROM shows the same files plus this one: mfastboot flash system system.img_sparsechunk.3

now, i returned to STOCK !

just one more question: RED TRIANGLE wen i try to access in the recovery

Thanks to all

UPDATE : instaled TWRP 2.8.6.0 , flicker screen when boot to recovery ...????? MY GOD!!!

now installed TWRP 2.8.7.0 and works fine

I do not know what to do
[Moto G Original Android Development] alfick3:
That's because when you flashed the stock fw, you over wrote your custom recovery with the stock recovery. If you want TWRP, you'll have to flash it again.
[Moto G Original Android Development] Altomugriento:
UPDATE : instaled TWRP 2.8.6.0 , flicker screen when boot to recovery ..

.............Mod Edit.............
[Moto G Original Android Development] alfick3:
[MENTION=5511342]Altomugriento[/MENTION] don't forget to hit the thanks button. :)
[Moto G Original Android Development] Clark Joseph Kent:
So much thought went into your post....well. You should of stopped here...Next time just say thank you or how about this, take up Development, since this is a Development and do for yourself.

But nevertheless, thank you.
[Moto G Original Android Development] Altomugriento:
tested three roms:

AOSP (5.1.1) CM 12.1 (5.1) and Paranoid Android (5.1.), Cyanogenmod obviously is not the problem, its Android 5.1.1

and SORRY Judge Joseph Dredd and anyone who was offended by my post, was not my intention
[Moto G Original Android Development] KapilFaujdar:
A workaround for black screen:

Press power button, you will see black screen. Now scroll down from status bar. Now you got your screen back to work.

This works fine for me. Never had to reboot.
[Moto G Original Android Development] Alberto97:
Fixes for stagefright issue has been pushed to CM sources a month ago
[Moto G Original Android Development] bloodhound42:
Android r12 released and its all around Internet that it's major update from Google. CM can u merge it as ur on r6 itself from long time
[Moto G Original Android Development] goldiman:
Hello when I go to security in settings the settings app crash, anyone have an idea how to fix this?

thank you :)
[Moto G Original Android Development] bogante:
Not happen to me

Enviado desde mi Moto G mediante Tapatalk
[Moto G Original Android Development] goldiman:
I did a full wipe and flashed the last update but I still have this issue :(

Another suggestion?
[Moto G Original Android Development] moralesnery:
Wipe DATA, DALVIK, CACHE and SYSTEM partitions from "Advanced wipe" while on TWRP (don't wipe internal storage). Reboot to TWRP again, flash the lastest nightly, gapps if you want and the problem should dissappear.
[Moto G Original Android Development] kingkong13:
Anyone else got connection issues over the last days? My phone asks me a couple of times a day to reenter my PIN. Problem started Monday when I was on August 1. Updated to August 10 and today to August 12. Problem still occurs.

Edit: seems it was my sim card which apparently moved a little bit
[Moto G Original Android Development] UltraMaks:
Seems like the battery drain is back in the build cm-12.1-20150811-NIGHTLY-falcon.zip

Take a look at the scrrenshot? even in the Flight Mode last night it continued to "eat battery". Can anyone confirm?
[Moto G Original Android Development] riyosakura:
Im not asking about user, but profile. Try system profile.

Try create 2 profile as i suggest.
[Moto G Original Android Development] unqualified:
FYI, I finally grabbed a logcat yesterday. Here's what I think is the relevant portion:

08-12 17:04:04.923 E/JavaBinder(12182): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
08-12 17:04:04.923 E/JavaBinder(12182): java.lang.VerifyError: Rejecting class com.motorola.motgeofencesvc.MotGeoFenceStateMachine because it failed compile-time verification (declaration of 'com.motorola.motgeofencesvc.MotGeoFenceStateMachine' appears in /system/app/MotGeoFenceSvc/MotGeoFenceSvc.apk)
08-12 17:04:04.923 E/JavaBinder(12182):	at com.motorola.motgeofencesvc.MotGeoFenceSvc$1.setGeoFence(MotGeoFenceSvc.java:60)
08-12 17:04:04.923 E/JavaBinder(12182):	at android.location.IGeoFencer$Stub.onTransact(IGeoFencer.java:60)
08-12 17:04:04.923 E/JavaBinder(12182):	at android.os.Binder.execTransact(Binder.java:446)
08-12 17:04:04.927 E/AndroidRuntime(12182): FATAL EXCEPTION: Binder_1
08-12 17:04:04.927 E/AndroidRuntime(12182): Process: com.motorola.process.system, PID: 12182
08-12 17:04:04.927 E/AndroidRuntime(12182): java.lang.VerifyError: Rejecting class com.motorola.motgeofencesvc.MotGeoFenceStateMachine because it failed compile-time verification (declaration of 'com.motorola.motgeofencesvc.MotGeoFenceStateMachine' appears in /system/app/MotGeoFenceSvc/MotGeoFenceSvc.apk)
08-12 17:04:04.927 E/AndroidRuntime(12182):	at com.motorola.motgeofencesvc.MotGeoFenceSvc$1.setGeoFence(MotGeoFenceSvc.java:60)
08-12 17:04:04.927 E/AndroidRuntime(12182):	at android.location.IGeoFencer$Stub.onTransact(IGeoFencer.java:60)
08-12 17:04:04.927 E/AndroidRuntime(12182):	at android.os.Binder.execTransact(Binder.java:446)
08-12 17:04:11.280 W/ActivityManager(842): Scheduling restart of crashed service
[Moto G Original Android Development] UltraMaks:
Just did to cm-12.1-20150813-NIGHTLY-falcon.zip. We'll see how it goes on this build :)

I wonder what is this in the next column (Cyanogen Recovery) - cm-12.1-20150813-NIGHTLY-falcon-recovery.img and do I need to install it together with this CM's build?
[Moto G Original Android Development] phate89:
Hi..I have a problem. I installed the 30/7 build and it works well. I'm now trying to update to a recent build. I have twrp 2.8.6.0. I'm trying to use cmupdater but I have 2 problems:

1) auto install doesn't work. I have to select zip file manually

2) when I install it manually I get a zip corrupted error executing the updater script. I know wiping system can solve it but why do I need to do it? Several people here doesn't need to

Inviato dal mio SM-G920F utilizzando Tapatalk
[Moto G Original Android Development] jonnug:
Can confirm. Been meaning to mention this. Really gets on my tits.

Love using Waze, especially as Google Maps hammers so much RAM.