yashsingh1/xdaforums huggingface dataset:
[Moto E Original Android Development] :
The open gapps problem was a problem with open gapps breaking CM13, nothing to do with CM13.

As far as I'm aware, open gapps is now fixed (01/05 build onwards) and should be fine, remember other gapps packages apart from open are available!

I don't use open gapps so I can't really comment.
[Moto E Original Android Development] tanayM:
which is the best kernel for better battery life? there so many custom kernels available..
[Moto E Original Android Development] hetor99:
The best kernel for now, is clarity kernel, it have dt2w (doubble tap to wake), intelliplug, underclock and other nice tweaks

Search it on the original development thread

Sorry for my english :p
[Moto E Original Android Development] rahul casey:
normally i use picco open gapps, coz its small size so is thr any other gapps which provide picco?
[Moto E Original Android Development] :
Yes, search XDA, I use the A gapps pico package, its available here on XDA

Search google apps 6.0 minimal
[Moto E Original Android Development] avi_wizard:
[MENTION=6485916]squid2[/MENTION] : I see a few commits related to MotoDoze. What is this feature?

Are you trying to port Marshmallow's Doze feature for our device?
[Moto E Original Android Development] Adi!@#:
Doze is already there in every marshmallow based ROM
[Moto E Original Android Development] ALPHAWolf96:
Motodoze and basic "doze" are different in nature. Motodoze refers to the gestures feature where you wave your hand to wake up the device whereas doze which is a marshmallow battery saving feature ( missing for condor due to absence of significant motion sensor). It's funny why Motorola named the feature as doze to complicate things. The commits you have been seeing is about cmactions which bring more gesture functionalities to otus with which the device will wake up as soon as you pick it up to bring more stock like feel to the device.

Hope this clears all your confusion.
[Moto E Original Android Development] Adi!@#:
Yes dude ! Thanks for the explanation. [emoji4]
[Moto E Original Android Development] harsh.:
Hey all,

Anyone having the issue of not showing contact name when that person calls u or u call that person..its condor issue ???? Cz I'm not having any problem like this.on 20160501nightly. If the issue is solved in any of next nightlies please name it. :p friend's is killing both me n my friend .
[Moto E Original Android Development] rohitshakti:
Can we do dirty flashing of CM13 ?
[Moto E Original Android Development] harsh.:
Yes u can... If u are already on cm13 already
[Moto E Original Android Development] sziraqui:
Look I have flashed this rom (build April 30) on three different condors. I flashed ROM+gapps in one session and wiped system, data, cache and dalvik. On first boot it goes in a bootloop (on all three condors) Restarting the device by holding down power button for 10 secs makes everything fine. All the three phones are running smoothly.

1. With philz 6.5.79 over stock deodexed 5.1

2. With TWRP 2.8.7 over pure stock 5.1.1

3. With TWRP 2.8.7 over highly debloated deodexed 5.1.

Again, ON FIRST BOOT IT GOES IN A BOOTLOOP, JUST RESTARTING THE DEVICE MAKES EVERYTHING NORMAL
[Moto E Original Android Development] harsh.:
Ty for help:D but started mob with cm13 ;) I was on stock 4.4.4 with unlocked bootloader so 1st flashed cm11 then 13 :p and it's running quit good
[Moto E Original Android Development] sziraqui:
You were on kitkat!! Dude you should have told this before posting any issues. I SUGGEST you to upgrade your bootloader. Moto e got a new bootloader with lollipop. Flash COMPLETE stock ROM (gpt, motoboot, and everything) to keep your phone alive and open to future development.
[Moto E Original Android Development] harsh.:
Now I'm with cm13.. Still I need to update it ? If yes, could u please share link for everything I need to do!
[Moto E Original Android Development] sziraqui:
If you never updated to stock lollipop, you need to update.

Follow this- (this is same as unbricking) link given is for 5.1

Hitting thanks button won't harm you :p
[Moto E Original Android Development] harsh.:
Definitely bro thank you.. Sry out of 8 thanks as limit :p will do flashing and will tell u about it as cmlpted ;) [MENTION=6211994]sziraqui[/MENTION]

One more thing I get lots n lots of FC's no matter what I try.. Sometime from YouTube ,google play service etc... What's wrong ? :confused:
[Moto E Original Android Development] sziraqui:
April 30 build is most stable according to me. No FCs, no bugs noticed yet. I am even using my external sdcard as internal (class 4, 16gb SanDisk). All apps are running as if my internal was 18gb out of the box. You may try that build

OR

Wipe userdata, cache and dalvik after flashing.
[Moto E Original Android Development] Kesava 91:
97% Ram memory filled

I am using moto e 1st gen,recently i had flashed my moto with cm13-6.0.1-nightly-condor with Gapps-micro .

my bug is mobile ram memory is almost full so system working little slow .please help me out to reduce the RAM memory without deleting apps

---------- Post added at 04:34 AM ---------- Previous post was at 04:31 AM ----------

had an another problem "unfortunately,google play services has stopped" this message is popping when i open any google related apps like gmail,playstore etc. in moto e xt1022
[Moto E Original Android Development] :
Ram

Nothing you can do about that, my moto e xt1021 has only 85mb free ram.

My second gen moto e runs cm13 too and that only has 100 mb free ram that's just how cm13 handles ram, other roms can handle it better, some ROMs are even worse than that.

All I can suggest is keep your installed apps to the bear minimum, unneeded apps like xposed, Facebook, custom themes or launchers ect only take up valuable space and resources, if u don't need it, don't install it.

I like to customise my moto e but flashing unneeded mods and themes or several launchers will only cause the device to slow down and use ram more intensively, so I don't now do it.

Google errors.

This is possibly either a gapps issue, or an installation error.

Make sure you always flash gapps in twrp at the same time as flashing the rom-Never reboot into android and then back to recovery to flash gapps, as that will produce the errors you describe

This is something I've come across both here and in the second gen moto e forum, some users have adopted an unusual, unorthodox and incorrect flashing procedure by flashing the ROM, rebooting into android to check if everything is working, then going back to recovery to install gapps.

However much both myself and other users advise this procedure is incorrect and will cause errors it still happens, so make sure you install gapps correctly and this will avoid most errors ;)

You can also try a different gapps package, there are many packages available and not just from open, remember you will have to perform a clean flash if you change gapps, and when flashing in twrp, flash the rom first, select add more zips, flash any kernel/mods, then select add more zips, select your gapps and then swipe to confirm flash in that order, reboot and your Google errors should have gone.
[Moto E Original Android Development] Kesava 91:
thank u.. i will try this
[Moto E Original Android Development] :
The best kernel for now, is clarity kernel, it have dt2w (doubble tap to wake), intelliplug, underclock and other nice tweaks

Search it on the original development thread

Sorry but if you feel you need s custom kernel then its your choice to flash one.

If you have no idea about kernels and what they do, don't bother.

I personally don't use a custom kernel on my moto e, but the choice is yours, if you feel its a benefit, go for it :)
[Moto E Original Android Development] sziraqui:
I get 300-400MB RAM free though I have many new apps installed. I am using April 30 build. I flashed rom and gapps in one session. CM handles RAM very well.
[Moto E Original Android Development] :
I just have nova launcher installed, no other apps or mods, I tried a custom kernel made no difference.

Seems some people are reporting high ram consumption, whilst others like you are not, I suspect how we use/what gapps we use ect is a factor.

Just because I have high ram consumption doesn't mean cm13 is a bad ROM, on the contrary, cm13 is the best all round for my moto e 1st gen.

I've stopped using cm13 on my second gen moto e and use another ROM that is a little more stable, but that's not for this thread, I'm just trying to make the point that ram consumption will vary with use and apps installed, and even though my ram consumption is high, my moto e keeps plodding on with little lag or slow down.
[Moto E Original Android Development] Kesava 91:
ram problem

hey thanks for reply can u please tell me which custom rom are using, and kernal version and gapps.(moto e xt1022)..plzzzz
[Moto E Original Android Development] sziraqui:
Everyone here is talking about cm13, I think its obvious that I am using cm13 build of April 30.

Gapps link given in OP, kernel version also given in OP
[Moto E Original Android Development] Kesava 91:
RAM error fixed
[Moto E Original Android Development] ALPHAWolf96:
[MENTION=6485916]squid2[/MENTION] So I was testing sound output on different ROMs since three days. Clean flashing every ROM and gapps. I was using cm13 4th may build and sound output quality on my Edifier Bluetooth speakers wasn't something that I should praise. I was at 67% and audio was audible but was lacking a lot on quality( tested on poweramp and eleven). The bass got overpowering sometimes and i wasn't even able to hear vocals.

Next I tested the quality on stock ROM on my other condor. And I can say that audio is just perfect. volume was just at 30% and of perfect quality. High, lows everything perfect. So I thought it might be some driver issues since it was a stock lollipop ROM.

So finally I flashed the last cm12.1 build available for condor and bamm! Awesome quality! Those thumping beats were just enough to impress my ears. Volume was at just 27% and sound was bliss.

So I guess, the lollipop roms have much better sound quality than mm ROMs.

At last, i returned back to cm13 again because of it's smoothness n other stuff.

Again, I thank you a lot for your hard work on this device and I'm completely happy with cm13. It's just perfect but an improved audio quality will be an icing on the cake.?

Ps- I tested the sound with eleven and poweramp( which I've been using since my first android) with audiofx and viper4android.
[Moto E Original Android Development] Josiley:
Only here that the sd card is incompatible ? He was formatted as internal memory.
[Moto E Original Android Development] Rohitagni:
I have the Clarity Kernel (DT2W version, enforcing) installed, and haven't tweaked any of the Kernel settings.

I use my phone for only calls, WhatsApp, Facebook (via the messenger), and some light gaming.

This is the RAM usage I am getting and it's pretty good IMO.

P.S. Facebook Messenger is the only app that utilizes 100+ MB of RAM, try to stop the app and its processes or use Facebook lite to get a better experience.
[Moto E Original Android Development] :
That's a very good comparison.

Good to know.

I don't use Facebook or Facebook messenger on my condor, I use metal.

The proof is there for everyone to see, I'm managing my ram more now by uninstalling unnecessary apps and now have over 200mb free ram.
[Moto E Original Android Development] rahul casey:
http://www.paranoidandroid.co/files/sliders/PAPie.jpg

what is it? a widget? seem super
[Moto E Original Android Development] EnricoBarsanti:
It's called pie controll (as it seems a slice of pie/cake), it's usually used as a navigation bar with more function.

It's usually built in the roms as a feature, but you can try it with some play store apps like this One

https://play.google.com/store/apps/...ntrol&pcampaignid=APPU_1__HAwV82jAsn4aLGRrogD
[Moto E Original Android Development] speedmaster57:
does someone know how to make apps go on adopted sd automatic
[Moto E Original Android Development] ashum0758:
Hey pal I'm curious to know how can I install Motorola Apps (Gallery and camera apps) in CM 13. However, I did install Moto camera app from play store but moto gallery is appearing as incompatible with my device(Moto E 2014).
[Moto E Original Android Development] TigerKing:
You can't move or install one or two apps on sd card.. In Android 6.0

Either you can use internal storage for apps or external sd card as internal storage for apps.

---------- Post added at 07:15 ---------- Previous post was at 07:13 ----------

Can anyone tell me how to solve power button problem??? Is this hardware or software fault??

I can try both. Need help..
[Moto E Original Android Development] drs22:
It's a hardware problem
[Moto E Original Android Development] TigerKing:
OK. I know how to assemble and disassemble mobiles, so can you please tell me what i need to do??

Power key replacement?? Or any temporary modification??
[Moto E Original Android Development] drs22:
For permanent soln: change your motherboard

For temporary soln: use volume keys to wake up your phone. If you have a custom ROM, then flash a custom kernel such as clarity and enable double tap to wake
[Moto E Original Android Development] TigerKing:
Changing motherboard will cost me lot, instead of that i can buy new device.
[Moto E Original Android Development] rahul casey:
iam using 20160507 build, suddenly my motorola camera stops capturing photos, wen tapping the screen to take a photo a round circle is seen rotating in center thats all and i need to close the camera and open again. video capturing is working but not capturing photo, even the exposure control is not working
[Moto E Original Android Development] rian_tama:
Have you tried to clear data and cache on camera?
[Moto E Original Android Development] rahul casey:
i even uninstalled the camera using a root explorer, and then flashed again, still not working :( , it used to work in earlier cm13 version,

anyway is there any other camera which can be used for condor ?
[Moto E Original Android Development] rohitshakti:
I did dirty flashing of CM13 ROM of 8th May but since the time I had flashed the ROM, I am not getting 3G connection speed on my mobile else I am just able to see the E mark on the phone and secondly I am getting a message on the screen on every reboot that my ROM is unstable and lastly my music device is not working and the error message is flashing after every few minutes. Are these bugs ?
[Moto E Original Android Development] rian_tama:
I'm using stock motorola camera on cm13. From this thread
[Moto E Original Android Development] hetor99:
the cyanogenmod 13 rom for moto e have code that enable the download of motorola camera from the playstore, download from it
[Moto E Original Android Development] :
I think that's what he meant, he is using the Motorola camera.........

As for this code, Ive never heard that mentioned before or am I sure it even exists (please correct me if I'm wrong) but the Motorola camera can be downloaded by anyone, not just by anyone using a moto e on cm13.....

I'm using the Motorola camera on my second gen moto e (running CM13, and that was downloaded from play store) but it won't work on my 1st gen moto e (on cm13)

So if there was a secret code to allow me to install the camera from play store, it should work on my XT1021 condor is that what you are saying?

Unfortunately, I'm getting "your device is not compatible with this version" error.
[Moto E Original Android Development] rian_tama:
Yes this is what I mean. I'm getting "your device is not compatible with this version" on playstore before, and that's why I downloaded motorola camera from the other way. After that I can update motorola camera from playstore.
[Moto E Original Android Development] :
I can try that, thank you :)
[Moto E Original Android Development] hetor99:
I'm on the build 20161105 without mods or custom kernel and i can download the motorola camera and update it
[Moto E Original Android Development] rohitshakti:
Any taken on the above ? Please help....

Meanwhile today I tried to install CM13 ROM of 11th May, 2016 with open gapps 6.0 ARM but after the installation, the phone didnot boot and I had to restore it to earlier date.
[Moto E Original Android Development] :
Perform a fresh install and report back.

Wipe everything
[Moto E Original Android Development] Skyther_k:
play store and gapps are not working

keeps on showing google play services have stopped working

any solutions???

I've tried pico package from gapps dot org

I'm on 5 may build
[Moto E Original Android Development] rahul casey:
:(, i used both 20160507 and 20160511 and my motorola camera is not working when taking photo, and i went back to 20160427 and thankfuly moto camera works fine on that version :)
[Moto E Original Android Development] :
Try a different gapps package, but you must clean install cm13 and flash gapps in the same session as flashing cm13 ( by that I mean its become increasingly apparent that some people have adopted an unorthodox and completely incorrect method of installing gapps.

They flash the ROM, reboot into android, check its working fine, then reboot back into recovery to flash gapps.

This will cause the errors you describe)

There are many gapps packages, many people use open gapps, but I don't, I use A gapps.

Try another package and report back.
[Moto E Original Android Development] TheKsprx:
Hello, I had the same problem with FC's everywhere, I followed these steps as told by someone in the Moto G CM13 thread.

For a clean install wich is recomended do this:

1. Wipe dalvik, cache ,data and system (you may discard data for dirty install or update)

2. Install ROM (don't reboot just yet, instead select wipe dalvik and cache)

3. Go back without leaving TWRP and install GAPPS (I used Open GAPPS pico) wipe dalvik and cache again

Now you can reboot system and voila!! all is working perfectly.

p.s. I could not belive how I did not think about doing that when I was dealing with those FC in the rom. Hope it helps you.
[Moto E Original Android Development] ALPHAWolf96:
So finally after a week of my exams, I clean flashed 14-05 build with 04-05 open gapps. Everything was working but as soon as as homescreen popped up, I noticed something unusual. See that big fat battery icon ? It have a huge padding. Moreover the text is misaligned and also translucent now rather then pure white. So it turns to black on a black background making it barely visible. Can't complain on the build. It seems smooth as usual. Didn't faced any Ps fcs or duplicate contacts problem which some users were complaining about.

So a little Heads up- if you're about to flash the 14th build and didn't liked that icon, DON'T.
[Moto E Original Android Development] zeeshanhussain12:
Cm added it and they are still working on improving it
[Moto E Original Android Development] ALPHAWolf96:
Yeah I found that out too. Still hoping they don't start using this big icon coz the older one was way cooler.
[Moto E Original Android Development] :
I found the battery icon text bug. When is the circle icon, it shows an abnormal alignment and size.
[Moto E Original Android Development] zeeshanhussain12:
They added a battery vector drawable AFAIK so it will be good if.a theme can reduce them
[Moto E Original Android Development] :
This is and has always been the recommended way to flash, so if you were so surprised it worked for you, what procedure did you use before you found this official way really works and had errors everywhere?

The installation procedure for ROM, gapps and any modifications is well documented and keeps being repeated here time and time again.

Any other method used to flash gapps is not recommended and results in the errors that are described here time and time again.

There has recently been a great number of users reporting force close of google apps or errors during initial set up, not only in this thread but in the second gen moto e thread, and other device forums.

For some strange reason, new and unofficial gapps flashing methods have emerged, with users reporting a genuine 100% failure rate........

Anyone adopting these unusual or unorthodox methods to flash gapps is risking errors and is also is not keeping to the devs installation instructions.

Failure to follow installation instructions will result in errors and may lead to (in the worst case scenario) no developer support in the event of problems.

I'm glad you posted these instructions, I've been telling every man and His dog in these forums recently that gapps MUST be flashed at the same time as the ROM and you should NEVER reboot into android to reboot back to recovery to flash gapps.

That method is totally incorrect and does nothing other than to cause errors and people testing these ROMs to blame the rom and not consider their own foolhardy actions.

I'm sorry if some people are reading this thinking "OMG, he's off on one again....."

No one has ever said these other installation methods are right or wrong, but I personally feel rather sorry for the devs when people complain google this and google that won't work, and blame the ROM or the developer rather than follow the developers own instructions which are put there for a reason, not for fun!

Let's follow the developers instructions and enjoy their work without errors.

Happy flashing.
[Moto E Original Android Development] faroukalfan04:
Anyone use "gltools" here?
[Moto E Original Android Development] TheKsprx:
I don't really know if you did not like my post or what but anyway, if you check in OP and other threads, the how to install methods are slightly different. As you can see in my last post there are additional steps,you wipe cache and dalvik after every flash. You are asking the way I was doing it, well I followed the OP instructions. I'm not saying OP is wrong neither devs of course,but that this has worked in my case.

Apart from that I agree with you, some people don't like to read through posts and guides, and then they report false bugs wich are coming from a bad installation.
[Moto E Original Android Development] :
Far from not liking your post, I LOVED your post, its great, and its good to refresh everyone's memory from time to time.

I totally agree there has been many false reporting of issues due to installation errors, and one thing I've found is a lack of understanding as to why it is so important to flash in the way you posted.

There was a minority saying in a couple of posts that they choose to flash how they choose and people telling them different are just scaremongering.

I respect everyone's opinion and if they adopt differing flashing methods that's their choice, I personally would follow the procedure you posted, that is the developers recommendations, and I appreciate it can differ for other devices or firmware.

As testers of these ROMs it is our responsibility to follow the installation instructions we are given.

Please accept my apology if I said anything that may be considered too patronising to you or anyone else, it was not my intention, I thank you for your post and totally, wholeheartedly and 100% agree with all of it :)
[Moto E Original Android Development] TheKsprx:
Don't worry we are on the same page then. I'm really thankful to all devs and people willing to help others, like I've seen your posts in this thread. :good:

About the rom, will test it and see how it goes with sd internal .
[Moto E Original Android Development] Joline:
I've followed exactly the same procedure (using cm-13.0-20160514-NIGHTLY-condor.zip), but unfortunatelly the devices stucks while displaying the CM bootlogo. :(

I've flashed with TWRP and also with Philz but change. Also I've tried to use a different CM version (cm-12.1-20160110-NIGHTLY-condor.zip). But all the time the same thing: After reboot the CM logo comes up and stay for a long time with no change. I've waited for at least one hour. There is no change, if I flash GApps (open_gapps-arm-6.0-pico-20160504.zip / open_gapps-arm-6.0-pico-20160515.zip) or not.

With TWRP I've created a backup of my old system (rooted stock 4.4.4) and I'm able to restore this with success. Btw, some month ago I've unlocked the bootloader and rooted the device.

I've attached the TWRP logfile. Does anybody have an idea, what could be wrong here?