yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] Konpon96:
In CM build.prop file there are lines:

ro.product.model=XT1032
ro.product.brand=motorola
ro.product.name=XT1032
ro.product.device=xt1032
ro.product.board=MSM8226
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US

In stock build.prop there is:

ro.product.model=XT1032
ro.product.brand=motorola
ro.product.name=falcon_retgb
ro.product.device=falcon_umts
ro.product.board=MSM8226
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=GB

Will changing "ro.product.name" and "ro.product.device" variable values in CM file to stock ones make Motorola apps like Boot Services, Gallery and Camera available to download from Play Store? If not, what more should I change? Do I need also to copy com.motorola.*.jar files from stock /system/framework/ catalogue to CM one?
[Moto G Original Android Development] Doublepranks:
[devs][xt1033]

Stock 4.4 System Dump

http://xdaforums.com/showthread.php?t=2643283
[Moto G Original Android Development] Entropy512:
Battery estimation swinging wildly on reset is a hardware limitation. Seems like the G has a simplistic fuel gauge similar to the old Galaxy S2. The advantage of these fuel gauges is that you never need to perform a calibration cycle on them - they will always converge over time on their own (1-2 hours of normal usage). The disadvantage is they sometimes get thrown way off after a reset.

As to other criticisms of battery life - I'm using dhacker's kernel in an omni build I'm working on, and it seems almost like maybe something in the kernel isn't properly disabling a regulator on suspend, as drain when asleep seems much higher than it should be. That said, lots of qcoms behave badly when the SIM is removed so it could be that... With CM10.1 on the Xperia Z, battery life was WORSE when the device was in airplane mode with wifi turned on than with a SIM in - it should be much better!

Unfortunately power management issues like that are hell to debug...

I would personally recommend to dhacker that he not do this, since it's a workaround for a broken recovery.

While there was in the past a valid reason to have a recovery that reported as merely "falcon", with dhacker's libinit stuff, you can now have a unified recovery that properly reports as an individual variant. (I believe the recoveries dhacker posted are built with the new libinit stuff... but I'm not entirely sure.)

e.g. fix the recovery, not the package's asserts

The moto apps almost surely have dependencies on Moto customizations to the framework. If you copy the Moto framework JARs to CM you'll have a broken device.
[Moto G Original Android Development] Wechy77:
If i build pac unified falcon, my build.prop looks like this: Pastebin

and i have ro.build.product=falcon

So if falcon is not present in assert, i have status 7 error: This package is for 'xt1028, xt1031, xt1032, xt1033, xt1034, falcon_umts, falcon_umtsds, falcon_cdma, falcon_retuaws' devices; this is a falcon device

with PhilZ Touch recovery. With Dhacker's recovery there is no such a problem.

So what do you recommend for solution?
[Moto G Original Android Development] dhacker29:
Ask him to rebuild recovery with the current device tree
[Moto G Original Android Development] SWTR:
I only get freeze in youtube when I set HD. When I turn HD off the video will not freeze.
[Moto G Original Android Development] tschertel:
[MENTION=4112553]dhacker29[/MENTION], what's the difference between gapps you provided in first post and the one from CM wiki (http://wiki.cyanogenmod.org/w/Google_Apps)?
[Moto G Original Android Development] kellerman40:
Thats correct.
[Moto G Original Android Development] SeannyM:
The Cm one has more updated apps and no Experience launcher since CM now has Trebuchet.

Edit: I forgot, the CyanogenMod Gapps are compatible with ART runtime.
[Moto G Original Android Development] jharlap:
Building recovery?

[MENTION=4112553]dhacker29[/MENTION] thanks for all your work - it's amazing to see how your work seems to have sparked all the ROM variants to be able to build for Moto G.

I'm building the CM11 tree based on your work and I'm having a hard time getting recovery to work - I was hoping you could elaborate on how you're building recovery? I've tried CWM and TWRP and both times end up with something that doesn't work... I've been building an AOSP variant regularly for my work and I'll admit this is my first time with a bleeding edge device build and my first time trying to diagnose recovery at all. What I ultimately need is to be able to end up with a recovery image that lets the factory reset function (called by a Device Administration service for remote wipe) work.

The CWM build you linked to from first page doesn't seem to work (meaning the factory reset function doesn't work), while the TWRP build you posted there does although it has other issues as far as I can see - if there's some twist to get them to build that I'm missing, I'd be forever grateful - and if I can get my head around what's involved in making this work and can contribute anything back, I'd be happy to do so.

As a side note, I notice that unlike with AOSP the norm with CM11 seems to be to make otapackages and sideload them rather than create system images and flash them with fastboot - is there a reason for that? I've noticed that if I build CM11 using your device tree and try to fastboot flash the system.img, it fails - any idea why that would be?
[Moto G Original Android Development] dhacker29:
If you've synched cm-11 and added my device/kernel all you should need to do is make recoveryimage to get a working cwm.

I haven't tried flashing a system image but it "should" work are you using the moto "mfastboot" or the SDK one? The moto one splits the system image into 256 mb parts. Most custom roms are done as otapackage so that users can just flash in recovery without needing a computer.
[Moto G Original Android Development] tschertel:
So, it's totally safe use CM Gapps. Isn't?
[Moto G Original Android Development] Rokostar:
Will this Rom be official in the future ??
[Moto G Original Android Development] tschertel:
Yes.
[Moto G Original Android Development] core720:
Not more updates for moto x?
[Moto G Original Android Development] Wechy77:
CM link But they must merge it.
[Moto G Original Android Development] core720:
http://download.cyanogenmod.org/?device=xt1058

Old versions
[Moto G Original Android Development] kellerman40:
I tried Xposed with GravityBox on the latest build. Works nice, although I was unable to change the size of quick settings tiles as I like to have a lot of them. Not an issue, just mentioning.

I haven't also got any reboots with 06jan build jet.
[Moto G Original Android Development] lamaboy99:
cyanogenmod accounts

i get cyanogenmod accounts has stopped on boot after fresh install

never mind i fixed it by wiping the system partition then flashing the zip
[Moto G Original Android Development] :
Can someone sum up the bugs that are still in this Rom? Is it ready for daily use, because I need my phone to work.
[Moto G Original Android Development] denzel09:
[MENTION=4112553]dhacker29[/MENTION] can you update the changelog please?
[Moto G Original Android Development] tschertel:
I've tested 03-02 and 06-02 and both have bugs.

IMHO, 31-01 build is the best so far. I'm using it. It's almost bug free. No lock screen issue, no random reboots, no GPS issue and you can see your device's internal storage when connected to computer.

But, it's just MHO. :D
[Moto G Original Android Development] kellerman40:
I had random reboots with 31jan build I think. Now I haven't got any jet with 06feb build.

Take in mind that some people say that they have no such issues like lockscreen and youtube issue with the latest builds.

About summing up the issues, I did it in one of my posts for the 06feb build.
[Moto G Original Android Development] :
I guess I'll wait for the next build then, but thanks for your opinions ^^
[Moto G Original Android Development] OurJerry:
I'm on the 31 Jan, it's the best at the moment for me. It does have crashes with trebuchet when connected to gsm. The newer dates are a little better, but Youtube does not work right. And I'm a lot on Youtube. So I'm waiting for the next build, when that's fixed it will be such a good rom.

I use it as my daily rom, It's better than stock, everything works like it should. [MENTION=5117644]NonsensNinja[/MENTION]
[Moto G Original Android Development] kellerman40:
Yes you can try using 31jan build if you wont be changing your rom for a while.
[Moto G Original Android Development] :
I actually never use YouTube on my phone. Is mobile Hotspot / tethering working?
[Moto G Original Android Development] OurJerry:
I dont know, I never use that. [MENTION=5117644]NonsensNinja[/MENTION]
[Moto G Original Android Development] michalurban:
Compilation

Hi,

Im having trouble with "repo sync" when going with the razrqcom getting started guide. About 11GB of data downloaded ok but then ...

From https://android.googlesource.com/platform/prebuilts/qemu-kernel
* [new tag] android-4.4.2_r1 -> android-4.4.2_r1
* [new tag] android-4.4.1_r1 -> android-4.4.1_r1
* [new tag] android-4.4_r1.1 -> android-4.4_r1.1
* [new tag] android-4.4_r1.2 -> android-4.4_r1.2
* [new tag] android-cts-4.4_r1 -> android-cts-4.4_r1
* [new tag] android-sdk-4.4.2_r1 -> android-sdk-4.4.2_r1

And it's like this about at least an hour. Should I cancel it and run it again?
[Moto G Original Android Development] kellerman40:
Seems to work for me over wifi, it created the AP. Should work also via usb otherwise someone would have reported a problem already. The big issues are lockscreen freezing and youtube not working properly.

When it wont unlock, just relock it, wait for 1-2secs, then try to unlock, works every second time if I wait those 1-2secs. Sometimes the touch doesnt work when alarm is ringing and phone is waking (or perhaps with phonecalls too) - again same scenario - lock, wait, unlock. And youtube problems are only when watching videos in HD.

I simply use helium to backup apps to be prepared for a new build. All the contacts are synced in google and messages/call logs can be restored using helium as well. Then I'm left with setting some system settings. You can always do a cwm/twrp backup too :)
[Moto G Original Android Development] jharlap:
Thanks - I was more liberal with clobbering and tried again and now, as advertised, I do end up with a "working" cwm. I put the quotes there because while I can use the menu interface within recovery to wipe /data, if I run a factory reset from a running system (Settings -> Backup & reset -> Factory data reset) then it reboots to recovery (as it should) and then fails and gets stuck, with some snippets from /tmp/recovery.log as follows:

recovery filesystem table
=========================
0 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
1 /data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata 0
2 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
3 /fsg ext4 /dev/block/platform/msm_sdcc.1/by-name/fsg 0
4 /firmware ext4 /dev/block/platform/msm_sdcc.1/by-name/modem 0
5 /persist ext4 /dev/block/platform/msm_sdcc.1/by-name/persist 0
6 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
7 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
8 /modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem 0
9 /storage/usbdisk auto /devices/platform/msm_hsusb_host 0
10 none swap /dev/block/zram0 0
11 /tmp ramdisk ramdisk 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 usbdisk /storage/usbdisk 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Got arguments from /cache/recovery/command
I:Checking arguments.
/sbin/recovery: unrecognized option `--locale=en_US'

E:Invalid command argument
I:device_recovery_start()
Command: "/sbin/recovery" "--wipe_data" "--locale=en_US"

Formatting /data...

F2FS-tools: mkfs.f2fs Ver: 1.1.0 (2012-11-29)

Error: Device not specified

Usage: mkfs.f2fs [options] device
[options]:
-a heap-based allocation [default:1]
-d debug level [default:0]
-e [extension list] e.g. "mp3,gif,mov"
-l label
-o overprovision ratio [default:5]
-s # of segments per section [default:1]
-z # of sections per zone [default:1]
-t 0: nodiscard, 1: discard [default:1]

Any thoughts to get past this?
[Moto G Original Android Development] zamurai x:
sorry for the question. everything works now?
[Moto G Original Android Development] come2jojo:
Will be official someday?
[Moto G Original Android Development] denzel09:
Yes :highfive:
[Moto G Original Android Development] peter_baz:
first of all thank you for your work!

i seem to have a bug sometimes when i wake the screen,touch doesnt respond until i turn it on and off again.

2nd and more important i cant get any location access.via wireless nor via gps(gps searches but doesnt find any satt even though on stock it locks in under 10 sec)

i know what you wrote on OP and tried it with no luck.any other ideas?
[Moto G Original Android Development] kellerman40:
I know this thread is now a little long, but all the answers are there somewhere. Touch issue is a known bug and GPS can be fixed by restoring stock firmware, turning the gps on there and then flashing cm again (or restoring a backup). Search this thread. But the wifi/cell location still wont work.
[Moto G Original Android Development] denzel09:
It's not my work this rom man! :highfive:
[Moto G Original Android Development] jharlap:
Factory reset failing - a solution.

[MENTION=4112553]dhacker29[/MENTION] After some digging, I figured it out, but I don't get why this doesn't seem to be affecting other people or if it's just that no one else is using factory reset when running CWM with an f2fs formatted /data. Turns out that factory reset triggers roots.c to call make_f2fs_main with a faked argc/argv pair, and f2fs-tools uses getopt on them. The twist is that recovery.c also used getopt, so it got optind up to 3 and didn't reset it before calling make_f2fs_main, so when f2fs-tools tries to use getopt it is starting with a polluted state and thinks that no extra argumens were passed - and it expects one extra argument to specify the device to format.

One solution is simply to modify recovery.c as follows to reset optind after finishing the getopt loop

diff --git a/recovery.c b/recovery.c
index fcaf0a6..4ee94f5 100644
--- a/recovery.c
+++ b/recovery.c
@@ -1055,6 +1055,7 @@ main(int argc, char **argv) {
continue;
}
}
+ optind = 1;

struct selinux_opt seopts[] = {
{ SELABEL_OPT_PATH, "/file_contexts" }

Alternately, roots.c could import getopt.h and reset optind, or could use _system() instead of calling make_f2fs_main.

The reason that using the menu within recovery to wipe /data didn't exhibit this issue is that when you do that, instead of using make_f2fs_main it ends up calling format_unknown_device which uses rm -fr on a mounted partition to do the "format".

So the only remaining question is, should I be submitting a patch to CM to just reset optind in recovery.c as in the diff above, or some other approach, or would you rather deal with submitting patch yourself?
[Moto G Original Android Development] a6576171:
No network

I followed instructions here and I flashed back the stock rom, then activated gps there and reflashed all the cm11. The problem is, when I got back to stock, the network signal was lost, and it was saying that I had to insert sim card.

Does anybody knows what to do? Please...

EDIT: I reflashed stock rom and still not working... Can anybody help me?
[Moto G Original Android Development] kellerman40:
I had that when I was trying to restore backup which was made with 6.0.4.6 using PhilZ 6.0.4.7. Got no cell signal, apps were crashing, If I restored it using the old recovery, it would work I guess.
[Moto G Original Android Development] a6576171:
But I just recovered to the stock rom, and there I wasn't having signal as well. What should I do then? I'm afraid of reflashing and messing stuff a lot more :/ I'm sorry, I'm not that familiar with all this, but thanks already
[Moto G Original Android Development] tschertel:
If you have an XT1033, take a look at opening post.
[Moto G Original Android Development] kellerman40:
When I failed restoring the image, I simpy full wiped and flashed cm again. Just saying, had similar issues with stock backup there. But in my case it was 100% because of different recoveries.
[Moto G Original Android Development] a6576171:
I did take a look there, but I have XT1032 :/

that's why I'm worried, there's nothing about network drops on XT1032
[Moto G Original Android Development] tschertel:
After flashed stock rom, have you flashed CM again?
[Moto G Original Android Development] a6576171:
Yes, I flashed cm 2014-31-01 and gapps. But even before I reflashed CM (still on the stock rom I reflashed), the signal was lost. In fact, it happened from the first time I rebooted on stock rom, after flashed.

EDIT: When I try to connect manually, phone says "Your SIM card doesn't allow connections to this network." So I went to look for it on the internet, I found topics about it, but, they didn't really help (it was about typing on dialer *#*#4636#*#*, thn going to phone information, turn radio off then on back again, but no luck)

EDIT 2: My IMEI code is still here, so says *#06# on dialer
[Moto G Original Android Development] Entropy512:
Depending on how you added dhacker's repos to your local_manifest, some of the repos might require authentication with github.

I know for any repo I'm syncing via "private" connection methods that allow me to push to a repo, if I forget to ssh-add before syncing, it'll hang on those repos. In some cases, even though you don't have push access to those repos and are only using "public" functions, if you try to sync using certain methods, you still need to auth with github.

BTW, I saw some people claiming that they are having issues with YouTube freezing in HD - can you provide specific links? I'm unable to get YouTube to freeze in any configuration on Omni, which might give dhacker of some hints of where to look for differences/issues.

Also, dhacker: It does indeed turn out that lteOnCdmaDevice was the cause of the issues I was having with "No SIM Card" appearing on the lockscreen when in airplane mode that I mentioned on IRC. Turns out I forgot to clear out build.prop before rebuilding initially. lteOnCdmaDevice causes PhoneFactory (I think it was PhoneFactory, won't be able to look until I get home) to use CdmaLtePhone, which uses CdmaLteServiceStateTracker - which seems to mostly work on all variants but has some slightly odd side effects on GSM-only devices. Deleting this and moving the default_network settings to init_falcon.c for CDMA devices results in much more consistent operation in comparison to other GSM devices on my xt1034. I'll push a patch to my github repo tonight.
[Moto G Original Android Development] OurJerry:
Maybe flash a different stock.
[Moto G Original Android Development] a6576171:
I'll try it, thanks.
[Moto G Original Android Development] naramsim1:
GPS

Hi guys, i recently flashed this in my moto g:

cm-11-20140206-UNOFFICIAL-falcon.zip

Unfortunately GPS is not working at all; the trick of disabling and then enabling don't work... :(

I would know if in a previous release the GPS works...

Thanks

However, i want to thank so much dhacker for his work
[Moto G Original Android Development] djekan:
Flash again your moto g with stock ROM, install app GPS Fix from google play, enable your GPS a fix it, then reflash this ROM again, your GPS will works.

Sent from my Moto G
[Moto G Original Android Development] a6576171:
So, my phone's still without network connection. I Reflashed a couple of times the stock 4.3, but it simply won't recognize the network. I'm using brazilian retail device, which came with 4.3. I've been flashing releases from CM since the very first version, but, now, it made my network disappear. What can I do?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

EDIT: Sorry to bother you guys, Im a big time IMBECILE. I was looking through the stuff in the phone and realised that I had flashed the dual version of the moto g into my SINGLE version. So, thanks all you that helped before, I just fixed that stupidity of mine. Also, don't ever flash the dual version on single one or vice-versa, It messesw stuff up haha

ALso, i'm really happy I didn't screw up my phone.
[Moto G Original Android Development] dhacker29:
OK GPS hal has been updated with one that locks properly. What other issues are you guys having?
[Moto G Original Android Development] 1pilo:
thats good news.... thank you a lot for that

i'd say the other big issues are the lockscreen bug, the youtube bug and I don't know if fixed the Wifi/Cellular location

EDIT:

The 13.02 Build works really good! No bugs until now. And Wifi/Cellular positioning fixed!

Great work.
[Moto G Original Android Development] masatheboy:
Lock screen bug is only bug im having.
[Moto G Original Android Development] nickchk:
sorry to bother you bout this,but flashing over 4.4.2 xt1033 doesnt have ril. (the 4.4.2 modem dont help either),otherwise,it function greatly. :victory:

anyway,thanks for ur great effort.
[Moto G Original Android Development] iowaz:
Battery drain too fast(compared to stock)

Moto G(XT1032) :)

by now stock 4.4.2 <-> cm11(only testing)
[Moto G Original Android Development] OurJerry:
How is the Youtube bug now?

---------- Post added at 11:36 AM ---------- Previous post was at 11:21 AM ----------

GUYS YOUTUBE WORKS !!!!!

on 13 feb.
[Moto G Original Android Development] ekabon:
Guys, is it good enough for a daily driver now when GPS is fixed?
[Moto G Original Android Development] dhacker29:
Did you read the change log? GPS and YouTube are fixed. I see no issue as a daily driver other than sine devices still getting the occasional lockscreen touch issue. Where you have to relock and unlock again
[Moto G Original Android Development] tschertel:
I would say yes.

You can make calls, you can browse web, you can use GPS, no random reboots...

What else do you need?
[Moto G Original Android Development] kellerman40:
Touchscreen modules might be different for some and other devices. Mine for example becomes unusable when I plug my laptop besides my phone, no matter which charger I use. And mine has the lock issue. I'm gonna flash this soon! :)
[Moto G Original Android Development] ekabon:
What about battery life? A lot of people say its worse than stock:(
[Moto G Original Android Development] kellerman40:
Its ok to me. After one day of very light usage, I still have 80% the next morning.
[Moto G Original Android Development] will8578:
For me battery life is better than stock
[Moto G Original Android Development] ekabon:
Thanks guys, gonna try it out today ;)
[Moto G Original Android Development] kellerman40:
For those who think that battery is worse. Maybe it's some kind of placebo effect or something. Maybe you just use the phone more when having cyanogenmod on your device :laugh:

And dont expect the lockscreen to be fixed, it's the same. Can also confirm that youtube works and cell/wifi location + gps works perfffffectly. Superb work.
[Moto G Original Android Development] tschertel:
When I connect my phone to a computer, my phone appears but I can't access internal storage.

EDIT: This happens in Windows 7 32 bits, Windows 7 64 bits and Linux (Arch linux 64 bits).