yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] TangerineTractor:
Finally managed to install some custoom ROMS afer a week of trying... secret was to factory reset to 4.3, then CWM and flash from there, not let it ota to 4.4 first!

Anyhow, this seems pretty good for what I want, ie not full of flashy gimmicky bits, nice and clean, fast, smooth. Battery seems good so far. The only issue is no GPS.
[Moto G Original Android Development] chaz3:
I did a full wipe to the February 6th build and am testing. Will let you know if the battery improved :)
[Moto G Original Android Development] mccbrandon:
What kernel can I use with CyanogenMod

sent from my moto g xt1032
[Moto G Original Android Development] OurJerry:
Yes the GPS is not working. In maps its looking for my location, but it never finds it.
[Moto G Original Android Development] chaz3:
The February 6th build:

*Getting occasional lock screen unresponsiveness, never had this with earlier builds. Fairly annoying. Locking/unlocking fixes this.

*Battery life doesn't seem to be improved. It really may be a CM11 issue.

I'll keep on at it. Thanks again, dhacker29
[Moto G Original Android Development] SWTR:
I only can surf in the internet with H+ and Edge. When I have 3G it changes to H+ but sometimes this change took very long and I can't send messages in whatsapp till it change to H+.
[Moto G Original Android Development] thiagoserrao:
Moto is now seeding Kitkat dualsim, maybe we can have a full CM11 with dualsim working *-*.

Hope see this soon =)

http://xdaforums.com/showthread.php?t=2638606
[Moto G Original Android Development] tonynothing:
Same lock screen unresponsiveness issue.
[Moto G Original Android Development] tschertel:
Is 31-01 the best build so far?
[Moto G Original Android Development] SWTR:
and youtube movies does hang..

Gesendet von meinem Moto G mit Tapatalk 2
[Moto G Original Android Development] chaz3:
I fiddled around with the Phone information section of the Android service menu (*#*#4636#*#*) and my battery life seems to have returned to stock levels or at least improved noticeably :eek:

I wish I knew what exactly fixed the issue. I disabled the radio and turned it back on as well as changed the network type (currently GSM auto) in the process. I wouldn't change these settings in hope of an easy battery boost. But there was clearly something wrong with my system previously.
[Moto G Original Android Development] OurJerry:
the 6 Feb build is really buggy in Youtube and movies watched in the browser. There is something wrong with it. Also the homescreen makes a second empty homescreen sometimes.

---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------

I've heard that using the 4.3 bootloader it will work.

Or like me I have the 4.4 bootloader. I flashed stock rom, let it boot, and then flash your Cyanogenmod, and DO NOT DO A WIPE CACHE.

and then it will boot.
[Moto G Original Android Development] SeannyM:
I wish I could have posted earlier, but I was recently away for about a week and I left running the jan 31 build. When I arrived, I noticed that I could not connect to roaming services and only emergency calls were available. My friends/family could connect to roaming fine. Cant test with new builds though (i'm back now), so i dont know if it was fixed yet or not.

Sent from my Moto G
[Moto G Original Android Development] SWTR:
Have it sometimes too. I get no radio reception. Restart the phone fix it.

Gesendet von meinem Moto G mit Tapatalk 2
[Moto G Original Android Development] a6576171:
Sometimes, on every build I've tested so far, battery drops insanely, usually after a reboot. I woke up this morning and started to read some news and when I decided to reboot the phone, it had 89%, and suddenly when it booted up, dropped under 49%. Also, this build is laggier than some others I've tested too.
[Moto G Original Android Development] SeannyM:
I can only not connect when roaming, restarted many times with no result. As soon as I got back I was connected again.

Sent from my Moto G
[Moto G Original Android Development] ximmox:
Was on the build from the 30th (build #2) since it came out, had zero problems and everything worked for a week perfectly.

I haven't changed anything, out of the blue Location Services are not working anymore. GPS works, energysaving Location is activated in the settings, but all apps that need it tell me to switch them on because they seem to be deactivated (switched in on and off several times, rebooted with them on and off, no change).

Anything else I can try besides another factory reset?
[Moto G Original Android Development] iowaz:
Build 06/02/2014

XT1032

- No lags(launcher, games, nothing)

- Netflix works fine(I think it was working already)

- GPS isn't working(I think I let it off on stock rom, anyway, I don't use it)

- Battery Drain is a little bitter faster than stock(I think something about 20%-30% more fast)

Thanks again [MENTION=4112553]dhacker29[/MENTION]

* Anyone know where the CWM backup's are located?
[Moto G Original Android Development] Doublepranks:
I'd not consider 20-30 percent additional battery drain " A Little bit" It's quite a lot actually.

best way to go is to capture screen of battery usage and compare the data.

Back ups are at /mnt/shell/emulated/clockworkmod/
[Moto G Original Android Development] 1pilo:
Build 06.02.2014

XT1032 Retail De

I had some issues in the first build too. Then a I flashed stock ROM 4.4.2 again and installed the new build of 06.02.2014

Now my personal experiences:

- GPS: GPS works, but it works definitely as good as in stock ROM. It takes much longer to search for my location and the SNR of the single

satellites is quite bad.

- Battery: I had a dirty installation of the previous build where the batterylife was really really bad. Now with the new build and a clean installation the batterylife is quite good again, but I would say a bit lower than with stock ROM.

- Freezing: The touch in the lockscreen is still freezing sometimes. Relock and unlock again and it works. A bit annoying, but it works.

- Youtube/Videos: working really good. had no issues.

Thats it.
[Moto G Original Android Development] a6576171:
Stuck on bootscreen

I had the official firmware on, then I got the OTA 4.4.2. So, as my bootloader was already unlocked, I made a full wipe and flashed both rom and gapps. But now my phone is stuck on the bootscreen, the one that says cyanogenmod with the blue arrow. What do I do? :/
[Moto G Original Android Development] nickchk:
flash from 4.4.2 asian retail(xt1033),no ril, still no ril after flashing the 4.4.2 modem :( looks like i have to use gb retail instead.
[Moto G Original Android Development] Doublepranks:
What variant have you flashed? cm11 falcon or cm 11 xt1032?
[Moto G Original Android Development] nickchk:
lastest build, cm11 falcon
[Moto G Original Android Development] kellerman40:
With latest build. 06feb CURRENTLY

Big battery drain with clock (was not happening with 03feb build)

Still the lockscreen issue

Still youtube videos doesnt work properly

Still DSP and Apollo like not to work well together

The flip cover issue (I'm not affected, because I dont have one :D )

Still wifi/cell location (battery saving location) doesnt seem to work

Didn't mention the fixed things here tho... Did a full wipe before flashing. xt1032 (UK, had Tesco 4.3->4.4.2 previously). Used CWM 6.0.4.6, now using PhilZ 6.0.4.7.

As far as I can make/recieve phonecalls and text, I'm sticking with the latest builds. Can post logcat output if necessary.

Keep up the good work!
[Moto G Original Android Development] SeannyM:
Just flashed feb 6 build on my XT1032, and here are my results:

-Location working fine

-Lockscreen touch always working (tried 15-20 times in a row)

-YouTube/Netflix working fine

-Performance great, slightly better than jan 31 build

-Haven't tried battery life yet, but so far seems fine

Overall, I find this build is the best build yet. I don't know why other people are having problems, all I did was flash and wipe cache like I do every new build.
[Moto G Original Android Development] Doublepranks:
They tend to dirty flash new builds to avoid redownloading stuff again, which is the reason for all their problems. IMO.

Enviado de meu XT1033 usando Tapatalk
[Moto G Original Android Development] chaz3:
I wiped data and /system, cleared cache and dalvik cache and had these problems. I lost all traces of my old OS. I have to admit, oddly enough the contents of my sd card remained undeleted somehow, but I couldn't even figure out how to get rid of them.
[Moto G Original Android Development] kellerman40:
Same as [MENTION=5708942]chaz3[/MENTION] here. Wow, then is there really something i'm doing wrong? I use PhilZ CWM for flashing. First I do a factory reset (wipe data/factory reset), then wipe cache (wipe cache partition) from main menu. Then I format system and data. Haven't wiped dalvik's cache from advanced menu tho... Should I do that maybe? But dalvik-cache resides under /data I think.... Or is there anything else I'm missing or not wiping?

Never dirty flashed a build.

Couldnt it be an issue with recovery? For example when I have done the wipe, install rom and go to /data/system, I see dropbox folders, but I dont even have that installed. I also have older files there than the date of install.
[Moto G Original Android Development] a6576171:
Did the same, but I did wipe the dalvik cache. Weird, GPS doesn't work for me either.
[Moto G Original Android Development] kellerman40:
I'll try restoring stock 4.4.2 backup and then flash latest CM build tomorrow. GPS started working for me when I did that, but I also wiped /data then for the first time. So I'm not sure if the one thing or the other (or both :D ) helped. I'm thinking that something isnt being wiped correctly. I could try to check if the partitions are wiped with aroma FM.
[Moto G Original Android Development] OurJerry:
You can fix the GPS by making a backup of this Rom.

Installing the stock rom, going to google maps and find your location with accuracy set to high.

Then restore the backup of CM11 and you'll be all set.

thank you.
[Moto G Original Android Development] Wechy77:
[MENTION=4112553]dhacker29[/MENTION]:

can you make ota compatible with falcon? I mean when I use PhilZ recovery I got a status 7 error: abort("This package is for 'xt1028,xt1031,xt1032,xt1033,xt1034,falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws' devices; this is a falcon device) , and I think the devices are listed and defined here https://github.com/razrqcom-dev-team/android_device_motorola_msm8226-common/blob/cm-11.0/BoardConfigCommon.mk#L81

I can solve my problem, by editing the updater-script, but it would be great if you could do it.
[Moto G Original Android Development] mashaal95:
Having the same problem here!
[Moto G Original Android Development] Wechy77:
Copy out the updater-srcipt from cm zip. (META-INF\com\google\android\updater-script)

Edit it with notepad++ adding falcon as a device

like this

assert(getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" ||
getprop("ro.product.device") == "xt1032" || getprop("ro.build.product") == "xt1032" ||
getprop("ro.product.device") == "xt1033" || getprop("ro.build.product") == "xt1033" ||
getprop("ro.product.device") == "xt1034" || getprop("ro.build.product") == "xt1034" ||
[COLOR="Red"] getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || [/COLOR]
getprop("ro.product.device") == "falcon_umts" || getprop("ro.build.product") == "falcon_umts" ||
getprop("ro.product.device") == "falcon_umtsds" || getprop("ro.build.product") == "falcon_umtsds" ||
getprop("ro.product.device") == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma" ||
getprop("ro.product.device") == "falcon_retuaws" || getprop("ro.build.product") == "falcon_retuaws" || abort("This package is for \"xt1031,xt1032,xt1033,xt1034,[COLOR="red"]falcon[/COLOR],falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

There are two edits, highlighted with red.

copy back, overwrining old and and it should work.
[Moto G Original Android Development] kellerman40:
Which bootloader do you have? 4.3 or 4.4 one? Also what kind of rom you had in stock? Dont you format /system or /data or just wipe cache and do factory reset? What recovery are you using?

Maybe the people who have all working had some kind of specific official rom previously (maybe we need retail rom first???). I had Tesco branded unlocked device.

For what I can see, there are few people with fine-working 06feb build even after full wipe. And the GPS working only after setting it on with the stock FW is also wierd.

Is it worth to restore stock cwm backup and then try wiping everything and installing cm11?
[Moto G Original Android Development] mashaal95:
Getting stuck at the bootlogo guys, any advice? :)
[Moto G Original Android Development] jon_ybanez:
not yet ready for daily usage

came from stock 4.4.2. wiped cache/data/dalvik. no GPS issues, YouTube played fine.

major issue for me was the lock issue.

i really enjoyed CM Profiles & tell the phone to disable lockscreen when connected to my home WiFi.

with the lock issue, no matter how many times i turn screen off/on, i never get to homescreen.

i've tried waiting & letting screen timeout, but issue remains.

only workaround is too reboot phone.

hopefully, this and any other issues other people experience get worked out, i really enjoy the work CM & the OP have put into the ROM.
[Moto G Original Android Development] kellerman40:
Interesting that some people dont have these issues. But we do have them.

I was thinking about flashing stock UK 4.4.2 fully. But I don't know if it will be worth doing that.

Ehh, I'll restore my stock 4.4.2, then will try to flash CM. It's too terrifying to flash the whole rom and all partitions to 4.4.2 right now :D

Interesting [MENTION=2140887]jon_ybanez[/MENTION] . I can still unlock the screen after letting screen to time out for a while, GPS works. Altrough youtube doesnt work for me.
[Moto G Original Android Development] OurJerry:
With the new build sometimes the touch screen does not work, A quick lock and unlock makes it work again.
[Moto G Original Android Development] ares93:
I don't think its a ROM issue, I tried to recreate the issue on my two other phones with the help of clean installs and cwm backups and it was a nogo.

Like a bunch of other bugs in this ROM, the TS seems to be device specific. It might work perfectly for some people and run horribly for others. My amazon 8 runs it quite well, but on my tesco 8 and amazon 16 it has more bugs than a three day old muffin in the woods.

I just can't explain it.
[Moto G Original Android Development] kellerman40:
Maybe the solution is to convert Tesco version to Retail?
[Moto G Original Android Development] OurJerry:
Yes I agree with you [MENTION=1425077]ares93[/MENTION] there is a lot of quality differences between devices.

But I didn't have this bug on the 2 feb build, only with the 6 feb build, and it's when it's locked to the pin lockscreen. I cannot enter anything, I relock and open again and the touchscreen works again. Maybe some way to make a lolcat but I don't know how we can find the bug. must be a bug because on stock it doesn't happen.

But we're still young with this device and already have cm11 working almost perfectly even camera so I'm not worried that much. I'm happy :)

I do wish for a little overclock to 1,4 GHZ I think 1,6 GHZ is asking a little to much. But 1,4 or 1,3 with undervolt to stock 1,2 values should work in my gut feeling.
[Moto G Original Android Development] Wechy77:
I was on 4.4.2 us retail version, so not the stock rom from you come is the issue. It's something after 2. feb build that makes lockscreen freezing sometimes. I have it in about 20%, when I power on the phone.

But form me this is the only 1 issue. So I'm happy with my cm11 based rom.
[Moto G Original Android Development] anerik:
That's weird i never got that in my life
[Moto G Original Android Development] kellerman40:
For the people who have problems, 31jan build is way to go for now. It wont have touch problems or youtube problems. Only reboot problems or some other... But with 6feb build I haven't got any reboots till now.

I'm trying to get to know more about the device and it's filesystem.

https://github.com/razrqcom-dev-tea...26-common/blob/cm-11.0/rootdir/etc/fstab.qcom

these are the all mountpoints?

What are persist and fsg?
[Moto G Original Android Development] ares93:
Considering that phone has been unlocked and flashed a dozen times over with four different kernels, I think the stock rom is a moot point.
[Moto G Original Android Development] kellerman40:
I have tried 30jan#2, 31jan, 3feb and 6feb builds. All after wiping /system, /data, /cache... 31jan build works without yt and touch glitches, I can flash it now and it wont have those issues.
[Moto G Original Android Development] Cameron581:
What now? Why would you remove it? You should know the risks when installing a custom ROM it's made by a man who knows what he is doing he wouldn't be on the cm team if he didn't (not for us for other devices hints why I wanted to know his plans on making us official for he is on the group and is a big contributer) its just that the device might overheat but you would notice it would you not?
[Moto G Original Android Development] a1Pha:
Since the kernel is based on official sources this should not brick your device. Basically the CPU is running at full power within the vendor specified parameters. So yeah, it gets hot - but it won't get hotter than what Qualcomm allows it to be.
[Moto G Original Android Development] PloniAlmoni:
Someone said that it could fry the CPU, as such it's alpha, and XDA Developer's Forum rules state that for public forums one shouldn't post a ROM that damages devices in ordinary use. Hopefully the ROM will soon be updated though, and I agree with you that he knows what he's doing so I have every confidence that will happen, but in the meantime, maybe the links should be removed. I've already restored to stock.
[Moto G Original Android Development] josalaito:
I am not saying that, rom works fine and overheating problems can be solved with cpu tunners(Like no frills cpu)

Enviado desde mi XT1034 usando Tapatalk 2
[Moto G Original Android Development] PloniAlmoni:
Thanks for the clarification. :) Sorry for being a bit alarmed over this.
[Moto G Original Android Development] Cameron581:
Its a stable ROM its not going to cause damage if it does you knew the risk and even cyanogenmod says it we are not liable
[Moto G Original Android Development] k-kuchen:
It is available in F-Droid
[Moto G Original Android Development] bunnahabhain:
Hey thanks! Will look 4 it ☺
[Moto G Original Android Development] PloniAlmoni:
I know nobody is liable, if this were a ROM that fries devices though, it'd be ethical to remove it from a public forum. Apparently it's not though, so carry on. :)
[Moto G Original Android Development] japoina92:
forgive my previous comment, it's just a form of expression, I meant that it would feel warmer than normal. but we will not burn because the CPU used are official sources. also said that the CPU temperature is not controlled, so put that also captures taking a logcat on my Moto G.

forgive the misunderstanding. CM11 soon be much more stable!
[Moto G Original Android Development] krucymucy:
How did you guys flashed this ROM? I tried flashing it from TWRP but it doesn't work.
[Moto G Original Android Development] a1Pha:
Tried using CWM?
[Moto G Original Android Development] chrisund123:
I had no issue flashing from CWM using my usual method:

backup

wipe data

install rom

install gapps

reboot
[Moto G Original Android Development] krucymucy:
Jp, CWM worked. But I still prefer TWRP because of the touch solution.

Thanks.
[Moto G Original Android Development] mosfet321:
FC when I open PowerAMP or Apollo and the headphones are connected :rolleyes:

Solution: Open PowerAMP or Apollo without connecting the headphones, then connect them and everything works fine. :good:

THX fot CM11 :victory:
[Moto G Original Android Development] krucymucy:
ADB working for you guys?
[Moto G Original Android Development] Tomsgt:
in case anyone wants to see the install and CM11 running check out this video i did on it

Moto G CM11 Rom Install

[YOUTUBE]http://youtu.be/jbQP0ZC7jtU[/YOUTUBE]

Awesome work David like always thanks
[Moto G Original Android Development] chrisund123:
Working fine for me!
[Moto G Original Android Development] krucymucy:
I've tried flashing faux kernel, but I ended with loop restarting. Even if I turned device off it just kept turning on.

I made it to stock recovery so I'll flash stock 4.4.2 on and try again later.
[Moto G Original Android Development] lukas033:
Does ART runtime work?
[Moto G Original Android Development] TangerineTractor:
Got the latest version writing all perfectly, very smooth.. GPS working too...

The only thing I did differently from an earlier flash is to use a different gapps... the a new one dated 7 Feb, I used the stock one from the link below, then removed anything I didn't want.

http://goo.im/devs/paranoidandroid/roms/gapps
[Moto G Original Android Development] OurJerry:
[MENTION=5698110]kellerman40[/MENTION] thank you so much. With 31 jan I can finally watch Youtube.
[Moto G Original Android Development] kellerman40:
No problems. If our phones are similar then you could get random reboots in a few days, the min frequency could reset sometimes, also the notification sound bug. That is what I had with that build.

By the way mine was a Tesco 8GB model unlocked.
[Moto G Original Android Development] xtugap:
The max freq are fixed?
[Moto G Original Android Development] SeannyM:
The minimum frequency reseting to 1094 has been fixed in the latest update, I saw the commit on GitHub.
[Moto G Original Android Development] kellerman40:
It is indeed.
[Moto G Original Android Development] xtugap:
When I try the last CM build I can't do a UC, the max freq go back to the stock freq (1190Mhz) few seconds later. The same on the stock ROM+faux kernel and slimKat. On PA apparently works fine.
[Moto G Original Android Development] SeannyM:
Just tested and it does seem to be an issue, but I will never underclock anyways so it doesn't affect me.
[Moto G Original Android Development] iKarlito:
Why is that touchscreen issue not a rom problem? GPS and lockscreen got fixed and both problems came back with the latest build...

Written with Tapatalk PRO on my Moto G
[Moto G Original Android Development] 1pilo:
Can someone confirm that the Wifi/Cellular positioning isn't working in the 06. Feb build? GPS works quite fine but isn't that fast.
[Moto G Original Android Development] kellerman40:
Yes, I mentioned it a lot of times somewhere here.
[Moto G Original Android Development] SeannyM:
It was wprkinf for me at first but stopped working a little while ago.

Sent from my Moto G
[Moto G Original Android Development] kellerman40:
As the device is underclocked by default, It would be ok and acceptable to get a tiny OC ability in future. Like 1.4GHz.
[Moto G Original Android Development] kickokim:
Sorry for the question but I couldn't find the answer in the thread. From what I seem to understand it's now possible to install cwm with a locked bootloader. But can I install roms with my bootloader locked? Can I install this rom?
[Moto G Original Android Development] kellerman40:
You can install only motorola original firmware with locked bootloader. When it boots it checks md5sums of the partitions when the bootloader ir locked. If it wont match official firmware then it wont boot.
[Moto G Original Android Development] jharlap:
If you want to install a rom you'll need to unlock your bootloader.