yashsingh1/xdaforums huggingface dataset:
[Moto E Original Android Development] TigerKing:
I know how to use adb, I used it for other devices. But just this device I can't get into recovery using adb, using power menu, installing apps for booting into recovery.

---------- Post added at 21:20 ---------- Previous post was at 21:17 ----------

Yeah. It's weird problem. I think it's the build which causing problems. How do i clean install it again, from recovery??

Because I tried resetting, formatting, it didn't help either.
[Moto E Original Android Development] piku 123:
Strange I never faced this issue .
[Moto E Original Android Development] NE0HP:
QUOTE=amit.tiger12;67511804]i can't reboot to recovery from power menu (power off, reboot, screenshot menu) when device is on, power button + volume up + volume down is not working properly.

need help. asap.[/QUOTE]

Check this if you haven't enable it. Go to settings --> Button ----> Power Menu and enable Reboot Menu & other options that you would want.
[Moto E Original Android Development] TigerKing:
Check this if you haven't enable it. Go to settings --> Button ----> Power Menu and enable Reboot Menu & other options that you would want.[/QUOTE]

I know that power button>reboot>recovery,

Telling same thing that this is not working for me. I have to switch off device power button>power off.

And then after switching off power button + volume up + volume down for recovery menu.

Understood??
[Moto E Original Android Development] NE0HP:
I know that power button>reboot>recovery,

Telling same thing that this is not working for me. I have to switch off device power button>power off.

And then after switching off power button + volume up + volume down for recovery menu.

Understood??[/QUOTE]

Ok. If I understood properly then you're unable to go in to recovery from Fastboot mode!! Right? If it is then when you're in Fastboot mode just press volume down key to select recovery, then press Volume up(Don't press Power button) and leave. Be patient and It will boot in to recovery. That's it. Ignore if you've already done this.
[Moto E Original Android Development] ddamani9:
Does ur device boots into fastboot mode.?? If yes.. then u can flash rom from fastboot mode.. no need to go into recovery mode.. google it how to do it.. or elese try flashing latest twrp using "FLASHIFY" app from play store.. see if it works.. post ur results..
[Moto E Original Android Development] TigerKing:
Now that's headache telling again and again.

I can boot into fastboot, and then can boot into recovery from fastboot. This is the only way I have. for flashing yesterday's nightly and resetting/wiping/formatting data I used this method fastboot>recovery.

No other methods work for me booting into recovery, adb doesn't work, flashify doesn't work, advance power menu doesn't work.

Please don't ask again, only suggest help here.

Help for booting into recovery by adb, by flashify, by advance power menu.

P.S. - I can boot into recovery by fastboot mode only, not by other methods.

Ok. But as I said, I can boot into fastboot > then recovery,.

I will try flashing new nightly from fastboot. Will it be clean install??? Any steps you can provide, for clean install in fastboot mode, using adb???
[Moto E Original Android Development] surajsj:
Hey guys where to find boardconfig.mk file
[Moto E Original Android Development] prince trishi:
Not a good place to ask this question...but its present in

Device/motorola/condor/BoardConfig.mk
[Moto E Original Android Development] piku 123:
[/QUOTE]

You are doing all wrong.Turnoff your phone then press volume down then power wait for 10 sec release power.

Or you may go to developer option enable advance reboot.
[Moto E Original Android Development] ddamani9:
I recommend u to install stock first.. i had installed stock rom once on my moto g.. it was simple procedure.. no such thing such as clean install..as far as i know.. did u try flashing the twrp from flashify app.
[Moto E Original Android Development] pritesh1996:
moto e doesnt bootup after installing cm13 28th build. stuck in cm logo. what to do? installed cm13 as in thread.
[Moto E Original Android Development] ddamani9:
Again Wipe data, cache and dalvike n reboot.
[Moto E Original Android Development] pritesh1996:
tried but still stuck on cm logo.. plz help
[Moto E Original Android Development] tanqueta207:
Is this ROM good as daily driver? What are the mayor bugs? I read something about screen doesn't turn on on calls. Is that all bad about it? TIA!
[Moto E Original Android Development] hectorleriche:
Hello, anyone knows when it will appear cm14 ???
[Moto E Original Android Development] :
Thats a bit "off topic" for this thread.

CM14 will not appear until after Android N is official, and N won't be official until probably September (just a guess)

But

And its a big but.....

Will the first gen moto e get cm14???

I very much doubt it, because there is even doubt the second gen moto e will get it, if the hardware of the second gen can't handle N, there's no hope for the first gen, to be honest.

Who knows? I'm not an expert, and someone else will probably reply I'm very wrong.

This thread is Not really the place to discuss that or ask that question.

Please start a new thread.
[Moto E Original Android Development] starbright_:
Maybe Hardware will not support all new features, but I wouldn't think it is impossible to get CM14 even on Moto E 1st.

If bootloader is open. everything is possible - depending on motivation. ;)

---------- Post added at 08:14 AM ---------- Previous post was at 08:05 AM ----------

Do you using SD-card as internal memory?

I have the problem, that after reboot the icon of firefox in lower line disappears. It is an app moved to SD.

Also, it seems that after update or restoring of an image, that icons of those apps that are on SD, disappear.

I am the only one with this issue? Is this a general CM issue?

Checked with CM13 160614.
[Moto E Original Android Development] :
I have the luxury of owning both 1st gen and second gen moto E's.

The first gen is my "work" phone.

The second gen is my daily driver/personal phone.

Both run CM13.

Both have xposed and run custom kernels and far from standard set ups.

I follow this thread and the second gen thread for both moto e, and the majority of people are saying that the second gen moto e would never be able to run certain aspects of CM14, infact the second gen would never ever see a FULLY working port, rather, we may see some testing/experimental releases but they are likely to be very buggy and not very stable, and don't work......

My point is, if the second gen moto e community has already resigned to the fact that the "Otus" (3g moto e) and "surnia" (4g moto e) will never be able to run a fully working port of CM14/android N, how on earth are you expecting the "condor" to be able to run it with lesser hardware?

Just because we have an unlocked bootloader doesn't mean we can magically run Android N, the Condors hardware is the problem, its hardware means its just as unlikely to see a fully working port or Android N.

I made the point in my last reply that I'm not an expert on this and you or others having half hearted unrealistic hopes isn't going to get you or anyone else CM14/Android N, especially when people who have far more knowledge in programming and knowledge of hardware and its constraints than me are saying even though getting N to partially work on our devices may not be impossible, its unlikely any developer would want to port it to our devices, because of those hardware constraints.

You may want to have a read of the "will the Surnia (moto e 4g 2015 2nd gen) get Android N? thread in the second gen moto e thread here on XDA, but I Also suggest we ALL stop discussing THAT subject here and urge anyone wanting to discuss the possibility of the 1st gen moto e (condor) getting android N/CM14 to start a new thread and discuss it there.

Regards.
[Moto E Original Android Development] xxcas1:
I'm not sure about this... but the only lack in this rom is Doze mode, right? I mean condor doesn't have proximity sensor

Android Nougat is so different compared with Marshmallow? They look very similar

All Android version are very similar. i don't find major changes between KitKat or Lollipop and Marshmallow

I don't know... maybe there will not be a official CM release but maybe we can expect a unofficial one?
[Moto E Original Android Development] starbright_:
I agree we should stop discussion here. It doesn't make sense. This is thread of CM13!
[Moto E Original Android Development] athujoshi:
How to update?I have adapted sd on .do we have to turn that off before updating?please help.I am on 3rd march release.
[Moto E Original Android Development] :
What he said. I'll start a new thread if you really want me too and want to discuss that possibility, but let's keep to topic and JUST discuss CM13 here.

Regards
[Moto E Original Android Development] piku 123:
BUG:

Navigation Bar turning into black if i use any other wallpaper other than stock .
[Moto E Original Android Development] sandravictoria:
I managed to successfully install cm13 from http://get.cm. Everything is fantastic, but I cannot get any GPS fix. I have updated to new lollipop radio-firmware too http://xdaforums.com/showpost.php?p=62077542&postcount=1 I checked with lollipop stock (EU optimised xt1021) - GPS works perfectly, but I cannot get it in cm-13. I tried also:

fastboot erase modemst1
fastboot erase modemst2

Any other ideas?

SOLVED:

it was the new permissions system! Had to go to

Settings-> Apps->Gear-ConfigureApps -> App Permissions -> Location!
[Moto E Original Android Development] devxpy:
when are we getting a stable release?

after so many nightlies, can you give us a prediction as to when a stable version will be released? thanks! :D
[Moto E Original Android Development] xxcas1:
Nobody knows... maybe never.

Do not trust that.

Sometimes it is not necessary to wait for a "stable" version.

These Nightlies are very stable.
[Moto E Original Android Development] Rohitagni:
Are you absolutely sure of that? If so, what do you think makes the screen turn off, when u place the phone to your ear during a call? :rolleyes:
[Moto E Original Android Development] piku 123:
I think he wrongly mentioned proximity instead of motion detection.
[Moto E Original Android Development] devxpy:
bit laggy tho
[Moto E Original Android Development] TigerKing:
I think my moto e got into hard brick.

Problems occurred following manner

1. Can't boot into bootloader and recovery from advance reboot option while device is on.

Tried adb also.

2. After doing this

power button>reboot>bootloader/recovery

Device switch off and never turns on. No bootloader/recovery.

Same situation for adb.

3. So now device switched off, i try to boot into bootloader manually, by power button + volume down. But nothing happens. 99% failure, rarely this works. mostly boots into Normal mode while doing this.

Need help with this situation, I was trying to go back to stock (everything) but device not booting up in bootloader.

Managed to enter in bootloader, flashing stock solved every issue. Then again installed cm 13 latest nightly.

Now I can easily boot into bootloader and recovery from advance power menu and ADB.
[Moto E Original Android Development] rohitshakti:
+1

A stable release is the need of the hour.
[Moto E Original Android Development] piku 123:
Your phone is not hardbricked in case of hardbricked you can't even start your phone.

Use this guide to flash Stock

http://dev-viraj.blogspot.in/2015/02/flash-official-android-444-on-moto-e.html
[Moto E Original Android Development] :
This same discussion is going on in the Moto e 2015 2nd gen CM13 thread, people are asking for the "snapshot" builds.

I'm told that we unlikely to see the snapshot builds but we can see stable builds soon.

I don't flash every single nightly on my 1st gen moto e, I usually flash a newer build weekly, same on my second gen moto e, but this can have disadvantages.

1, a few days ago, i flashed a newer build of CM13 on my Condor and found it hesitant and very laggy, having to revert to an earlier build to retain stability.

2, I flashed a newer nightly on my second gen moto e yesterday, and ran into set up problems, namely with my preferred gapps package, a chance of gapps package eventually cured that problem.

3, Clean flash or dirty flash?

I always clean flash, who else does??

i believe it makes a noticeable difference in stability and performance.

4, with the amount of people testing these ROMs and their different preferred configurations/Set ups, sometimes its totally impossible solve someone's problem because of suspects like gapps, and mods like custom kernels and xposed modules, in other words, what works for me may be a complete disaster for someone else.

While I encourage and recommend these discussions, let's not get into asking or badgering the developer about stable builds, they will appear only when the dev thinks they are good enough.
[Moto E Original Android Development] vinay001:
Hi in CM 13 and Aosp Roms Dual Sim selection background is black, but in Dirty Unicorns(DU) Rom Dual sim selection background is transparent and it looks good, i have replaced CM dialer with DU so we get transparent background Can someone help me finding that Commit in Du Dialer git ....

https://github.com/DirtyUnicorns/android_packages_apps_Dialer/commits/m?page=1
[Moto E Original Android Development] starbright_:
The only way to come to a more stable release is listing bugs/issues and solve them, when they will confirmed by a second person. (this is to be sure that this is a common issue, not depending on personal situation).

As long as I know, there is no such list, nor someone maintaining it.

I can start with my two issues (based on 20160614)

-----------

1) Icons dissapear from the screen after reboot. This is for apps, that are moved to SD-card. My SD card is divided into two partitions, 3GB for internal usage and 26GB for data (music ....).

2) from time to time battery looses more power than normal. I found that android system itself is the reason, but I don't know what triggers this.

----------

So, now you can add more issue or confirm/not confirm the mentioned problems. Just copy only the list and change this.
[Moto E Original Android Development] treebaard:
Also experiencing #1 (using SD as internal, however), don't know about #2.
[Moto E Original Android Development] :
Not experienced #1 but I do not mess around making multiple partitions on my SD (I tried with my second gen moto e and had a corrupted SD)

I personally see no need to mess around with making extra partitions on my SD now, there is no performance gain what so ever to be had by doing that, and in my own experience, all that I achieved was to slow my device down and cause lag.

I do not set my SD as internal on my first gen moto e and now my second gen moto e, they are both set to portable.

I am not intending to criticize your actions, that is your choice, your right and preference, these comments are just my own observations by trying to be clever..........[emoji12]

Not experienced #2 either, my moto e first gen is my "work" phone, so to be fair and honest, its in my pocket more often than not.
[Moto E Original Android Development] kunalkabir01:
Go run towards the service center.. only if you device is in warranty..cuz your device is hard bricked now.. motherboard gone
[Moto E Original Android Development] TigerKing:
Please read properly, problem is solved now. This wasn't hard bricked. And motherboard is OK. Everything is fine now. Please always read full post.
[Moto E Original Android Development] starbright_:
I'm doing this (use SD as internal) not for performance reasons, but internal memory is out. Lucky you, if you don't have this problem. The issue is independent from splitting it to partitions, as [MENTION=6345524]treebaard[/MENTION] confirmed.

So it seems we are almost done, no further issues than this ?;)
[Moto E Original Android Development] :
None at all, and no mods installed (like xposed ect)
[Moto E Original Android Development] chtivain:
Hello,

I have a problem.

I had CM12 installed for several months and I wanted to install CM13 (by following the guide).

So by the application " TWRP manager ", I have to restart my phone on TWRP and I installed CM13.

Everything starts well, only I can't go in TWRP (to install Gapps).

I followed this tutorial (http://xdaforums.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971) to re-install TWRT, but when I choose recovery in "AP Fastboot Flash Mode", the screen becomes black and at the end of a few seconds the telephone reboot on CM13.

You would have a solution so that I can install Gapps on CM13 without having the recovery?

Thanks ;)

Edit : I puted "Usb debuging" on enable

edit 2 : try tuto from the start (unlock bootloader, tried the latest version of TWRT) => same problem, i can't enter in recovery mode.
[Moto E Original Android Development] mohitdm:
process system stopped working.

whenever the phone is in battery saver mode and it is rebooted, on boot up it shows "process system has stopped working."
[Moto E Original Android Development] :
You can't install gapps or CM13 Without a recovery.........

I would re do from the start, because its sounds like to me that twrp is not even installed, get rid of twrp manager and download twrp proper again from the post you followed, you have not done it properly, twrp should be flashed via adb/Fastboot, not from twrp manager, confirmation of that is I haven't seen Anyone else having that issue.

Re do again

Regards
[Moto E Original Android Development] -kcs_DipanshuPorwal:
I think u should try installing TWRP via adb here's a link for detailhttp://www.xda-developers.com/how-to-install-twrp/

You can use adb to install gapps too just Google it and you will find how to I'll try to provide u a xda link for that
[Moto E Original Android Development] chtivain:
Thanks it works ;)
[Moto E Original Android Development] TigerKing:
Installing recovery via TWRP manager create problems.

So use proper methods.
[Moto E Original Android Development] tkilla1979:
GPS problem - no stable GPS fix

Google Maps, Here and Waze don't get to keep a stable GPS signal. Flashed to stock. GPS worked again. Other attemps are like erase modemst1 and erase modemst2 in fastboot, reset AGPS do not work. Clean flashed other roms to.

Only a reboot of CM13 every time before using maps fixes the problem.

Am I the only one on this forum with these symptoms?
[Moto E Original Android Development] TigerKing:
Did you flash radios???
[Moto E Original Android Development] iscjarquin:
Calendar app (boxer and stock) are not working. They don't recognise the accounts, but mail apps do. I did a clean install with and without c-apps.
[Moto E Original Android Development] avi_wizard:
Has anyone installed the C-apps on their Moto E? Do they work?

They are available here: https://cyngn.com/c-apps
[Moto E Original Android Development] xxcas1:
Yes... i just flashed it for curiosity and they worked great

now i have two gallerys, two calendar and two mail apps. :rolleyes:
[Moto E Original Android Development] Mak7950:
GPS Issu

Few posts before there was this GPS issue, Is that fixed now and are there any major bugs in the rom, Planning to flash latest nightly. Thanks.! :)
[Moto E Original Android Development] :
This "GPS issue" only affected the poster using 3rd party apps.

I can give you my honest opinion that CM13 is completely stable with no bugs what so ever, but I have found the performance and stability is only affected by using certain gapps and certain 3rd party apps.

Let me give you a quick example.

I cannot get the official Facebook app to work, it crashes all the time.

Gmail gives me strange errors.

Google messenger is always force closing.

I changed from open gapps to a google minimal package and those problems went away (apart from Facebook)

I also have a second gen moto e, running CM13 by squid, and it had the same issues with the same google apps and the exact same problem with the Facebook app.

I changed the gapps package on that device and that is now fine too, apart from Facebook, I use Facebook lite with no issues!!!

Its impossible sometimes to give honest feed back in these forums because what works for me may not work for someone else.

Likewise, someone may have strange problems or a serious issue that doesn't affect the majority of other users.

For example, some people are using many customisations such as themes and xposed modules, and these can have a detrimental effect on overall performance, sometimes people are too quick to blame CM13 and neglect to inform others here of 3rd party apps/hacks/mods/and customisations.

I have found that using open gapps packages causes unusual behaviour from google apps, but others then post they have no issues, so I personally now do not use open gapps, you use what you want, but I advise you and anyone else not to use the latest open gapps, for me it gave strange problems, the earlier packages are fine.

I see no reason to discourage anyone trying or using CM13, its been a good daily driver for me for months.

Regards.
[Moto E Original Android Development] -kcs_DipanshuPorwal:
I've also flashed minimal gapps on cm13 n it works good for my XT1022.
[Moto E Original Android Development] ALPHAWolf96:
Don't know why but I'm not been able to download the latest nightly. Can anyone upload it somewhere else?
[Moto E Original Android Development] oduhart:
did you try with cmupdater or directly form cyanogenmod.org ?

from cyanogenmod.org it works flawlessly for me
[Moto E Original Android Development] ALPHAWolf96:
Since I'm not on cm right now so can't try cmupdater. I've been using the site since always but don't know now everytime i click on download it just fails.

Edit: Nvm. Got it to work now.
[Moto E Original Android Development] Mak7950:
Thank You. :)

---------- Post added at 06:22 AM ---------- Previous post was at 06:14 AM ----------

Thanks for your help, If you suggest not using GAPPS then is there any alternative for installing google apps and how do i install Playstore. :laugh:
[Moto E Original Android Development] :
Please read my post properly.....

I never suggested NOT installing gapps.

I suggested NOT installing gapps by open.

If you didnt know, There are many gapps packages, not just "open gapps"

Gapps come in all shapes and sizes and by many different sources, by many different providers.

I have found problems with open gapps, I now use this package.

http://xdaforums.com/showthread.php?t=3276606

Remember to flash these gapps straight after flashing CM13, don't reboot into CM13 then reboot to recovery to flash gapps, it wont work.

Hope that helps.
[Moto E Original Android Development] iscjarquin:
There is a thead here in XDA for minimal modular gapps.

xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

I've been using those gapps (you can choose which services you want) and it works perfectly for me (not even Facebook issue).

Good luck flashing.
[Moto E Original Android Development] :
My Facebook error is nothing to do with what gapps I use.

I'm using the exact same gapps as you, its working fine.

My Facebook problem is caused by being a Facebook beta tester and having a beta version that was bad, I have a newer Facebook version now and all working fine.
[Moto E Original Android Development] iscjarquin:
Oh, I see. Didn't know that...