yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] Doublepranks:
How about performance guys? Last build I flashed ( few weeks ago) had terrible UI hick ups and lags behind the stock firmware.

How is that feel now?
[Moto G Original Android Development] tschertel:
I've never seen any UI lag or hicks.

Edit: I'm using Nova Launcher. What launcher are you using?
[Moto G Original Android Development] kellerman40:
No such issue for me. Connects well on Windows 8 x64, it's probably not a computer problem. Sometimes this happens when you put a security lock on device and connect USB cable to unlocked device.
[Moto G Original Android Development] Haggster66:
Hi all,

Is the screen now turning off like on stock and GPE ROMs when closing the flip case?
[Moto G Original Android Development] xheon:
Can I install this on jelly bean, I heard that fixes the bootloop on some devices
[Moto G Original Android Development] tschertel:
Holly cow.. I unlocked my phone then plugged it to my computer and it works.

Thanks a lot [MENTION=5698110]kellerman40[/MENTION]!
[Moto G Original Android Development] kellerman40:
Nothing about that in the changelog.

No problems, it's just a security feature ;)
[Moto G Original Android Development] synescu:
this build is fantastic never had the lock screen bug with any cm build
[Moto G Original Android Development] anerik:
That's true, i don't think anybody can say this isn't a daily...
[Moto G Original Android Development] kellerman40:
Mind sharing your baseband version? Mine is MSM8626BP_1032.340.63.00R and I'm having the touch issue. Maybe it's related to that?
[Moto G Original Android Development] synescu:
Same as you
[Moto G Original Android Development] tschertel:
Mine is MSM8626BP_1032.355.66.00R and I have lock screen problem...
[Moto G Original Android Development] kellerman40:
I guess then the touchscreen or some other things on its board differs around devices.

By the way I flashed the latest gapps and works fine. Doesnt include the google launcher, only trebuchet, so that's nice.
[Moto G Original Android Development] OurJerry:
I too have the lockscreen problem, it's really bad in this build. 31 jan was perfect.
[Moto G Original Android Development] kellerman40:
Same, I think that no one had that with 31jan build. Just lock, wait 1-2secs, relock and it will respond again.

After flashed cm and gapps I flashed this. Still works if you need additional dictionaries for text input. Just remove the unneeded ones from the zip and flash.
[Moto G Original Android Development] tschertel:
Is this CM build from [MENTION=4112553]dhacker29[/MENTION] ART compatible?

I'm asking this because I'm using gapps from cm project and I'd like to know if ART is already in use in my phone. Do I need to activate ART somewhere?
[Moto G Original Android Development] synescu:
this build is still fantastic bat the lock screen bug is here tho
[Moto G Original Android Development] michael_ch:
Build instructions?

[MENTION=4112553]dhacker29[/MENTION] Can you provide me with some minimal build instructions? I tried using the manifests from https://github.com/razrqcom-dev-team/android_local_razrqcom, but I think it's broken. Also I guess that you merged the device trees into a single one (falcon), so I added the repository (https://github.com/razrqcom-dev-team/android_device_motorola_falcon) but the build fails at a very early stage now...

Thanks for any pointers!
[Moto G Original Android Development] syl0n:
Any update on XT1033 Doublepranks? Its still not working. At least update the first post and remove the false hope for new flashers.
[Moto G Original Android Development] anerik:
It's a bit more complicated doing falcon cause you need additional commits depending on what rom you're aiming to build
[Moto G Original Android Development] Hubik82:
I have XT1032. I've unlocked bootloader, root the device, flash recovery from first post. Then installed latest zip (cm-11-20140213-UNOFFICIAL-falcon.zip) and gaaps. But phone is stuck on boot screen?

Any advice?
[Moto G Original Android Development] ownjoouk:
I had the lock screen bug and GPS and YouTube so went back to infusion for a bit.

Noticed today YouTube and GPS was fixed so came back to cm.

Have to say this is now near perfect and in about 9 hours I haven't had any problems with my lockscreen.
[Moto G Original Android Development] anerik:
I haven't had the ls bug in my life. Could it be it only happens on cm? or cm based
[Moto G Original Android Development] peter_baz:
wipe cache/data from recovery
[Moto G Original Android Development] ownjoouk:
I did just activate pattern lockscreen and BOOM. Lock screen didn't respond yet all day with just swipe Lock screen I have had no problems.

So the question is are those with the issue using pattern or swipe?
[Moto G Original Android Development] nits05:
is a bug I had in all roms I installed. Finally solved with build 13/2 of CM11 :fingers-crossed:
[Moto G Original Android Development] Hubik82:
I have realized what was the problem - before installing CM phone downloaded OTA update and bootloader version was 4.4.2 so probably that was the point. I've downgraded to stock 4.3 and now CM installed without problems and working perfectly!
[Moto G Original Android Development] kellerman40:
I haven't got the lockscreen bug not even once using the pink kernel. If it shows up, I'll try to enable doubletap2wake and see what happens then.
[Moto G Original Android Development] stefanthehuman:
Hey guys, on these installs do you recommend dirty flashes (updating) or just clean flashes?

Thanks!:D
[Moto G Original Android Development] a6576171:
Hello, mates.

Just so you know, I get flickering on chrome every time I go to the tab animation and move the tabs (the one that appears upon tapping on that button located upper right, which shows a number related to the pages open in background). Besides YouTube and lockscreen, that seems to be the only bug I've found so far, now that GPS is ok.

By the way, I used to have an Atrix 4G and was using CM 10.2 from krystianp's kernel port project on it. Back then, I used to have waaaaay more bugs than that, and I still used that as a daily driver. So far, this ROM is nearly perfect, therefore I'm really optimistic about a future bug-free version, which I wasn't back then, because bugs are getting fixed almost by the release. You get so easily used to things that work, ain't it? :)

Keep up, people. We all hate stock ROMs.
[Moto G Original Android Development] 1pilo:
With this new build I'm having the issue/bug that I can't get network when I'm in roaming. It shows me no connection.

Some others having that issue. Bad that I'm using this phone also abroad ^^

EDIT:

Strange, after a reboot it worked. No problem guys ^^
[Moto G Original Android Development] dhacker29:
Major kernel update in new build just posted
[Moto G Original Android Development] michalurban:
I would also like to hear the official :laugh: opinion on this. As for myself, I follow this road:

1) Dirty flash - CM then GAPPS

2) when having problems, factory reset

3) when still having problems, factory reset + format / system, flash again

Thanks a lot! Could you post changelog, please? :)
[Moto G Original Android Development] Wechy77:
Take a look at github
[Moto G Original Android Development] ekabon:
Flashed it yesterday. So far got one reboot, lock screen bug 3-4 times and when I woke up in the morning the phone was off... I guess some deep sleep issues...
[Moto G Original Android Development] michalurban:
Which version? I dont know which timezone youre in but here Ive got 14th February and the last version is 0214 ... :)
[Moto G Original Android Development] TangerineTractor:
Same for me. Downloaded latest this morning. Unusable.
[Moto G Original Android Development] kellerman40:
Try yesterdays build if you haven't. It's almost perfect.
[Moto G Original Android Development] michalurban:
I find no difference (from the users point of view) between 0213 and 0214 ... Ive got about 2 lockscreen issues per hour and higher standby battery drain (compared to stock). Apart from that both ROMs seems ok to me ...
[Moto G Original Android Development] TangerineTractor:
My test was 13 build, might try 14, but other reports are no change.

Same issue on Liquid Smooth latest, but the latest Jellystalk has no problems at all, and I set up an identical configuration in all of them.
[Moto G Original Android Development] OurJerry:
I dirty flashed 14 feb and I have no problems whatsoever. Maybe the lockscreen bug, but I havent had it since I flashed it a few hours ago.
[Moto G Original Android Development] michalurban:
Im curious - you who tried the pink kernel, is it more battery-friendly? And what about the lockscreen bug?
[Moto G Original Android Development] kellerman40:
The bug is still there and there is overclock, but it doesnt give any performance boost. And dunno about battery.
[Moto G Original Android Development] ekabon:
I flashed it 02.13 that is why I wrote "yesterday", child of nature ;)
[Moto G Original Android Development] mccbrandon:
My battery has gone down from 100 to 70 in 1 hour of Playing smash the office with pink kernel
[Moto G Original Android Development] kellerman40:
Hey, what scores did you get with antutu? I got only 16521 with the latest overclocked one. I'm waiting for a new build. :)

And doubletap2wake could sometimes not work due to cm lockscreen bug (maybe).
[Moto G Original Android Development] mccbrandon:
I got 15785 with ART, on previous pink kernel I got 17400 ish
[Moto G Original Android Development] kellerman40:
Interesting, I got my score with dalvik. Does ART run stable on cm?
[Moto G Original Android Development] mccbrandon:
I'm on Slimkat, but I think it worked fine when I was on cm
[Moto G Original Android Development] tschertel:
How can I enable ART on CM?
[Moto G Original Android Development] kellerman40:
Go to settings -> developer options and find 'select runtime'. You have to enable developer settings first.
[Moto G Original Android Development] tschertel:
I don't have "developer options" option here.
[Moto G Original Android Development] kellerman40:
I got 16637 with ART and 11feb pink kernel. And 16675 with the 13feb pink kernel.
[Moto G Original Android Development] mccbrandon:
Go to about phone, then tap build number a few times (8 I think) then go back and it will be there

---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------

Interesting...
[Moto G Original Android Development] tschertel:
Thanks.

Once upon a time I did it on my old device. I just forgot bout it. :cool:
[Moto G Original Android Development] kellerman40:
But I think I had more fps in the opengl test with feb11 kernel than feb13 kernel. But runs a lot smoother with art.
[Moto G Original Android Development] mccbrandon:
I agree
[Moto G Original Android Development] TangerineTractor:
tried the latest build, (14th) still getting lots of screen lockups on wakeup, too many to be ignorable.
[Moto G Original Android Development] ares93:
Could you please add "falcon" as a device? Editing the update script at every update is seriously bugging me.
[Moto G Original Android Development] chaz3:
Installing the Feb 14 build :)
[Moto G Original Android Development] jamesro1208:
What recovery are you using? If you are using Philz, then you need to update to the newest version that fixes this problem.
[Moto G Original Android Development] dhacker29:
Ate you using the newest recovery?
[Moto G Original Android Development] chaz3:
Trebuchet settings are finally available and working :) Everything seems snappy so far. A good start.
[Moto G Original Android Development] Doublepranks:
[MENTION=4112553]dhacker29[/MENTION]

Anything new on the XT1033? Need help or something?
[Moto G Original Android Development] dhacker29:
I'll be on irc later and I'll try to work on 1033
[Moto G Original Android Development] Doublepranks:
Fine, i will be there too just in case you need any assistance.
[Moto G Original Android Development] SWTR:
It sucks when your teacher took your Moto G away till tuesday:( And there are so many nice updates, I hate thid old HTC.
[Moto G Original Android Development] chaz3:
Still getting lock screen freezes.
[Moto G Original Android Development] nits05:
After upgrading from the build of the 13/2 lock screen problems continued.

Then I did a clean install with full wipe and format system. 8 hours of moderate use and no problems with the lock screen.
[Moto G Original Android Development] Entropy512:
You need a fixed recovery.

BTW, dhacker, Brinly Taylor (uberlaggydarwin) has an xt1033 (like myself, first Moto after a pile of Sonys) and is likely going to be doing some bringup work on his. He's primarily going to be doing Omni, but anything he discovers we'll make sure to share with you. :) Hopefully we'll be able to work on it a bit this weekend. (It's always faster when a developer has the device. :) )
[Moto G Original Android Development] SeannyM:
nvm removed
[Moto G Original Android Development] dhacker29:
Agreed I'll be around irc to help
[Moto G Original Android Development] ggfool:
great work!

i did a cache/dalvik cache wipe and flashed the 14/2 build (from 13/2) and have not had any lock screen freezing since (probably been about 6 hours now) i spent at least 10 minutes just locking and unlocking the device as well.

this build seems perfect so far!
[Moto G Original Android Development] michalurban:
Lockscreen problem is the only one for me since 0213 and 0214 ... apart from that this ROM is perfect!
[Moto G Original Android Development] kellerman40:
Sometimes it works, sometimes it doesn't. If you lock / unlock a lot in a short period of time, you probably won't get the issue. It comes when you least expect it :D
[Moto G Original Android Development] Mattpadge:
Isnt booting for me, stucked at boot animation.
[Moto G Original Android Development] xheon:
Lockscreen bug is what is holding me to flash this ROM, will it be possible to fix this issue in the future?
[Moto G Original Android Development] dhacker29:
For those having the no boot issue it is due to the way some 4.3 roms handled the data partition as in kernel emulation. The easiest fix is to copy everything form your internal storage/sd and then format /data and data/media in recovery and it will boot.
[Moto G Original Android Development] thebestiam:
Does this work with Boost Mobile of Moto G? Model XT1031
[Moto G Original Android Development] dhacker29:
I have it set up so that it "should" but I haven't had anyone confirm. I would appreciate if you'd try it
[Moto G Original Android Development] thebestiam:
There's ton's of files O.o. Which one do i download? Soo confusee.
[Moto G Original Android Development] dhacker29:
The newest one by date :) http://androidhosting.org/Devs/Dhacker29/MotoG/cm/cm-11-20140215-UNOFFICIAL-falcon.zip
[Moto G Original Android Development] michalurban:
After two days with CM11 (one with 0213, second with 0214) I can say its fine! :) Good battery life and only one major bug - the lockscreen bug.

Apart from that I found only few minor things - for example when setting sound for Facebook Messenger the sounds dont play (using the system app for choosing sounds), when in options for launchers my APex settings wont launch when trying to do so = not important things.

If the 0215 version should fix the lockscreen bug then Im happy! And even now I decided to use CM11 as my daily driver. Great job, Dhacker!!!!! :good: :)
[Moto G Original Android Development] chaz3:
Wow, dhacker29 is on fire :D

Guess I'll clean flash the new build. Hopefully the lock screen issues will be solved.
[Moto G Original Android Development] OurJerry:
[MENTION=4112553]dhacker29[/MENTION] did something change with the touchscreen? because I had this on a stock rom, the touchscreen is really choppy now, i cannot scrol fast anymore, sometimes it thinks I'm selecting an app when i want to scroll left and right, it's horrible.

I had this on stock too, and it dissapeared with cyanogenmod, but now with 15 feb I have it again. Changed back to 14 feb and everything is fine again.

(clean flash)

---------- Post added at 12:35 PM ---------- Previous post was at 12:19 PM ----------

[MENTION=4112553]dhacker29[/MENTION] I found out what the touch screen issue was, I think all the moto G's or most have it when it's connected with the usb data cable. The touchscreen gets unresponsive. so it has nothing to do with cyanogenmod or stock roms, it;s a hardware problem.

thanks, feb 15 works fine now.
[Moto G Original Android Development] kellerman40:
[MENTION=4821729]OurJerry[/MENTION] if you are connecting it to a laptop, try disconnecting it from AC and then check the touchscreen. :D This has nothing to do with the rom. The problem is caused by some electric interference which could be caused by laptops AC adapter (I have that problem, I even cant connect a charger side to side with my laptop in one power socket) or other interference within your electric installation.

And the touchscreen bug seems to be gone, haven't got it one within a hour now :) I would say that this is completely usable now.
[Moto G Original Android Development] Munszu:
Booting

Could you give me a hand with this? I couldn't mount the sd storage so I couldn't copy files from there. I did format /data and data/media, but the phone is still stuck at the CM boot logo.
[Moto G Original Android Development] xheon:
Yes, and can you be a little more specific in what to do and how to do it please. Tnx
[Moto G Original Android Development] qamartheone:
which gapps is the recommended one ? the op linked one or the newest one from cm itself ?
[Moto G Original Android Development] SeannyM:
I would recommend the CyanogenMod Gapps due to the fact that they are compatible with ART runtime and they are more up to date.
[Moto G Original Android Development] ekabon:
Two batteries!)
[Moto G Original Android Development] kellerman40:
Yes and they work well with the latest build.
[Moto G Original Android Development] andpizzolato:
Anyone with the latest build that can verify if the USB connection is working? :good:
[Moto G Original Android Development] ares93:
Ta, guys. I was under the impression that I was running the newest version of Philz. Turns out I accidentally flashed the same version I was already running. My bad.
[Moto G Original Android Development] qamartheone:
if thats the case..then may i know why the gapps link hasnt been updated with the new ones in the OP ?
[Moto G Original Android Development] peter_baz:
you installed gravity box or some other xposed mod?thats your 2nd battery

new bug?

i think that in call speaker is linked with media volume and not with in call volume as its supposed to be...
[Moto G Original Android Development] :
My phone does'nt get past the bootanimation.

Do I need to flash a new kernel, or what?

Or does first boot just take veeeeery long?
[Moto G Original Android Development] masatheboy:
Im not having any lock screen issues with nevest build. AWESOME! Thanks for your hard work. Now this is perfect. :good:
[Moto G Original Android Development] ekabon:
Great rom, mate! Battery life is great, GPS works fine, and so far no LS freeze... Thanks for the great job! Which kernel would you recommend to use with your ROM, pink or faux?
[Moto G Original Android Development] SeannyM:
faux's kernel is only for stock and pink's kernel is only for cyanogenmod.
[Moto G Original Android Development] ekabon:
Thanks for saving me some time ;)
[Moto G Original Android Development] chaz3:
Flashed the Feb 15 build. Haven't encountered any lock screen freezes, I will notify if these show up. So far this is brilliant! I can't even think of much else to improve anymore :D
[Moto G Original Android Development] OurJerry:
Yes :D it's perfect now, only thing is to update to the new Cyanogenmod source so now and then. yeaahhh !! I'm so happy now :)

yes I made a bug report for the whole of cyanogenmod, but maybe you too can take a look and tell me is this easy to implement?

https://jira.cyanogenmod.org/browse/CYAN-3467
[Moto G Original Android Development] kellerman40:
DSP Manager doesnt work properly. I'm using Viper4Android, it works system wide and is much much better. Really I can't find any other not-working thing. Dunno whats about the flipcover issue.
[Moto G Original Android Development] michalurban:
Is the Philz CWM recovery compatible now? There used to be a problem with the device name ... or something like that. :) If it is compatible, can anyone present here a link, please?
[Moto G Original Android Development] anerik:
It is. Search for it, it's on the original development section
[Moto G Original Android Development] michalurban:
Thanks, I found this (http://xdaforums.com/showthread.php?t=2639583) link ... thats the one I used to download Philz CWM before. :)

I was only unsure about the versions because I had believed the compatible version had been released like yesterday but the newest version is philz_touch_6.13.9-falcon.zip from 11.2.2014 ...

So, this is the right version, yes?
[Moto G Original Android Development] dhacker29:
I assume you have an app or mod interfering this isn't a cm issue I've tried all battery settings
[Moto G Original Android Development] dhacker29:
Because I am lazy :D
[Moto G Original Android Development] ekabon:
Its gone with the latest release, thanx;)
[Moto G Original Android Development] dhacker29:
Does faux have an aosp kernel? And really that's up to you as far as what you like.
[Moto G Original Android Development] denzel09:
Faux kernel works only on stock. Atm at least.
[Moto G Original Android Development] dhacker29:
I think it's doable but I'm not the java monkey for that task :)
[Moto G Original Android Development] dhacker29:
I've been discussing with cm how to handle the new soundfx drivers
[Moto G Original Android Development] andpizzolato:
[MENTION=4112553]dhacker29[/MENTION] Do you have any news about the bug with the connection between the device and the PC/Mac? Is MTP fully working now?
[Moto G Original Android Development] dhacker29:
I don't have a Mac or windows. It works fine in Linux. Send more details and a logcat of failed connection. I didn't find anything in the last one I got
[Moto G Original Android Development] Entropy512:
Holy crap you were fast with this... I was hoping to do SOME of the bringup work on omni myself but wound up tied up this weekend. :(
[Moto G Original Android Development] anerik:
AOSP kernels will NOT work on a cm rom! Stop trying to install faux kernel!! About the rom, i'm back on stock until the major bugs are fixed
[Moto G Original Android Development] krucymucy:
I only tried that because of the CPU frequencies "bug". Now I know it doesn't work. Live and learn they say.
[Moto G Original Android Development] dhacker29:
You've tested this and it actually fixes the issue because it appears to be just another way of doing the same thing? In well aware of the thermal-engine issues. It's most lonely a permission issue. Had to sleep though
[Moto G Original Android Development] dhacker29:
Yes it's on the list to look at
[Moto G Original Android Development] captivatingtab:
I'm not sure what I'm doing wrong...

US GSM Moto G 16gb unlocked BL and CWM installed and I'm trying with the XT1034 version...

Wipe data/Factory reset

Wipe Cache

Wipe Dalvik Cache

Flash ROM

Flash Gapps from OP

Reboot

The phone gets stuck on the CM boot animation and won't boot up.

Is there anything else I should be doing?

I've downloaded the ROM 3 times and still won't boot.
[Moto G Original Android Development] ownjoouk:
Is it just me or is WiFi hotspot broken?
[Moto G Original Android Development] herbesi01:
That happened me too, but XT-1032
[Moto G Original Android Development] StrangerWeather:
Works for me, using it right now!
[Moto G Original Android Development] mathm2013:
CM doesn't accept bug reports on ART, i think.
[Moto G Original Android Development] swirly05:
USB to PC working for everyone?? I have a macbook, don't believe that matters but eh...
[Moto G Original Android Development] chrisund123:
Worked OK for me on Ubuntu earlier.
[Moto G Original Android Development] 903tex:
So is this build safe to run or should I wait?
[Moto G Original Android Development] dhacker29:
WiFi hotspot works with no security haven't tested wpa yet