yashsingh1/xdaforums huggingface dataset:
[Moto E Original Android Development] Adarsh1998:
http://review.cyanogenmod.org/#/c/107177/ read commit description
[Moto E Original Android Development] zeeshanhussain12:
Ashwin hav merged it in device tree.
[Moto E Original Android Development] Adarsh1998:
Where link?
[Moto E Original Android Development] zeeshanhussain12:
https://github.com/TheMuppets/proprietary_vendor_motorola

Check out [emoji4]
[Moto E Original Android Development] Adarsh1998:
Its merged now http://review.cyanogenmod.org/#/c/107177/
[Moto E Original Android Development] zeeshanhussain12:
I have seen, now we can expect fully stable cm [emoji12] lol
[Moto E Original Android Development] jonaaa:
I can confirm that Green Pixels and the Retry Bug is gone. I think we are clean of bugs for now, 100% stable ROM (maybe?), well done :good:.
[Moto E Original Android Development] sudheermbbs07:
There is considerable delay in connecting to WiFi which was not there in older builds(I am on 23rd Aug nightly).

Sent from Moto E using XDA Free mobile app
[Moto E Original Android Development] jonaaa:
No delay here, normal here...
[Moto E Original Android Development] Cheez2553:
Yeah,bug vanished here too!
[Moto E Original Android Development] :
Can anyone confirm if the voice bug has now gone? Can I now install YouTube or will it screw my calls?
[Moto E Original Android Development] jonaaa:
No problems here... YouTube is fine, the quality changing is fast...
[Moto E Original Android Development] naveenultimategamer:
Thanks all developers for this excellent build. No YT bug and sound bug during call
[Moto E Original Android Development] piyushkashyap216:
i am facing that call bug i am on 23rd aug nightly
[Moto E Original Android Development] Adarsh1998:
Bcoz youtube bug solved in 24th nightly
[Moto E Original Android Development] vinay001:
Im on 24th Nightly anyone have issues when call comes, for me display takes some time to turn on when call comes.....
[Moto E Original Android Development] piyushkashyap216:
CM 12.1 problem phone reboots while trying to uninstall app

i m on 25 aug nightly

edit

solved by wiping cache partition
[Moto E Original Android Development] shivamg95:
Random Reboots( not that power button issue)

I am facing random reboots on 24th aug nightly. Its not that power button issue. anyone else facing that?
[Moto E Original Android Development] Ujjawalsharma354:
Try out today's build.......its stable for that[emoji28]
[Moto E Original Android Development] naveenultimategamer:
No problem here. Try to install Latest nightly by wiping system, data and cache.
[Moto E Original Android Development] vinay001:
Facing Call issue taking time to turn on display when call comes its random a reboot fixes but it again goes to previous state.....
[Moto E Original Android Development] piyushkashyap216:
hey get this per app theme from cyanogen os

http://xdaforums.com/galaxy-note-3/themes-apps/app-themer-cm12-cos12-apps-one-plus-one-t3185622

:D
[Moto E Original Android Development] matt4321:
Please remember to use the English language in the forums!

At least use Google translate to aid you if you don't know English.

Forum moderator,

matt4321
[Moto E Original Android Development] vinay001:
so no one having call problems here i tried 23 and 24th build when call come display takes time to turn on , idk why, only i have flashed dolby atmos any compatibility issues with cm latest build coz there is some changes in audio config on latest cm dolby atmos patches audio config ...Anyone having tis issue....

A Reboot fixes the call delay but again it goes to previous state after some time......
[Moto E Original Android Development] Ujjawalsharma354:
Guys it vibrates on nitification
[Moto E Original Android Development] piyushkashyap216:
i am also facing call delay bug i am on 20150825 build
[Moto E Original Android Development] vinay001:
Im using 25th build, Yes i think i figured out the issue its related to proximity sensor i think, last time if some one calls if its in pocket the display wont turn on means if something is covered by proximity sensor display wont turn on but on latest build if someone calls display wont turn off if we cover proximity only it turns off when we pickup the call.... I think this is the issue it took three days to troubleshoot [MENTION=4913184]percy_g2[/MENTION] [MENTION=5426059]ashwin007[/MENTION] have a look i think proximity is broken in latest cm builds.....

---------- Post added at 08:10 PM ---------- Previous post was at 08:03 PM ----------

U on stock kernel or Zapdos coz zapdos had call delay issue???? im on stock....
[Moto E Original Android Development] stockuser:
Did you clean flash? Did you use TWRP 2.8.5.0?

CM12.1 can be flashed with 2.8.5.0? I got stuck in bootloop while clean flashing this ROM!

On a side note, good to see 3 Bongs carrying out a technical Adda.. ;)
[Moto E Original Android Development] @SidDev:
yes

2.8.5.0 can flash cm12.1

many are using it already.
[Moto E Original Android Development] stockuser:
I mean clean flash on stock KK bootloader? Coz 99% Moto E users here are on Lollipop bootloader.
[Moto E Original Android Development] Adarsh1998:
Not me and running fine, bootloader nothing to do with it...
[Moto E Original Android Development] @SidDev:
Motorola didn't update the boot loader after 4.4.4 kk update.

So bootloader not an issue.
[Moto E Original Android Development] prathameshmestry:
Bootloader can be updated only if u flash the soak test update through the updating process so the bootloader gets updated only by the soaktest zip..!! Its better to keep the bootloader to kk
[Moto E Original Android Development] @SidDev:
hey man

I was one of the insiders to get soak test first

they didn't do anything to bootloader with 5.0.2

the updated last with 4.4.4 OK update.
[Moto E Original Android Development] shekhutanwar:
Tested CM 12.1

I have tested latest CM 12.1 30th March Build. I have found that video recording is not fixed yet, and gps location icon is showing always in notification bar. Maybe GPS problem. Rest didn't encountered any other problem.
[Moto E Original Android Development] sagnik9:
Recording bug will be fixed in the next build.

Didn't face the GPS thing, working perfectly fine.

Hit Thanks if that was helpful
[Moto E Original Android Development] DAVI FELICIANO:
RIL and FC's is fixed?
[Moto E Original Android Development] sagnik9:
Yes

Use the q&a

Hit Thanks if that was helpful
[Moto E Original Android Development] ChaTy:
And what abt 2nd sim call reboot problem???
[Moto E Original Android Development] shekhutanwar:
And There is No FM Radio App i just noticed and gps icon fixed after flashing gapps for android 5.1 version.
[Moto E Original Android Development] xmetalcrisx:
So... What is the "REAL" changelog? I mean, the Post says:

Not Working /Issues

No video recording, even if app says it works. "fixed" :confused:

So, is this rom working? I can't use camera on CM12, i can use it for like 10 min, but it crashes, and what about CM12.1, the same bug?

Sorry for my bad english guys.
[Moto E Original Android Development] Yahzee Skellington:
...video recording is fixed. I tested it with both, the Google and the Motorola camera apps. BTW every nightly has worked fine for with the exception of those few known issues.

Also I'm still not able to change the volume of the ringtone and notification separately. Other than that, awesome job :D
[Moto E Original Android Development] ChaTy:
Bro, can u tell me whether sim2 call reboot problem is solved ?
[Moto E Original Android Development] Ar-Dinthalion:
Tested scritch 02-04 build, no more package install FC, as someone says, video recording fixed, I'm using 5.1 Gapps, a package made of my own, if you wanna download it here is the link (http://xdaforums.com/showthread.php?t=3070193

) and everything working fine and smooth
[Moto E Original Android Development] Yahzee Skellington:
...my Moto E only has one SIM, sorry
[Moto E Original Android Development] ChaTy:
ohh no problem buddy ! :)
[Moto E Original Android Development] piyushkashyap216:
having same issue with both kernels

and in my case i think its not proximity bug whether its covered or not screen takes time to wake
[Moto E Original Android Development] vinay001:
It must be proximity Ashwin must have a look...
[Moto E Original Android Development] ALPHAWolf96:
Another bug. confirmation ?

I just flashed the latest 26th august nightly and now I'm facing fc on opening chrome.

Fyi i wiped everything before flashing.

Can someone confirm this bug ?

[MENTION=4913184]percy_g2[/MENTION]

[IMG="here's a screenie"]http://i.imgur.com/YK8LMzv.jpg[/IMG]
[Moto E Original Android Development] vrishabhs09:
Try to move chrome in internal storage if you have move it to the sd card
[Moto E Original Android Development] ALPHAWolf96:
It's in internal memory only. I tried deleting its data n cache but it's still not working.

Any ideas ? [MENTION=3445372]scritch007[/MENTION]
[Moto E Original Android Development] sastredick:
I managed to install it, did not start, remained steady at boot, then I found a post by people with the same problem and they said to put before the 11 official or unofficial, then the 12 ☺
[Moto E Original Android Development] ALPHAWolf96:
Here's a logcat
[Moto E Original Android Development] ashwin007:
https://github.com/CyanogenMod/andr...mmit/8693a023a9e575aa58b945b5e8896c658552dcb4

Fixed by CM
[Moto E Original Android Development] NasiJagung:
sorry if im repost, but anyone happening lost root ??

and a signal wifi hotspot low than cm11...
[Moto E Original Android Development] rohitshakti:
I tried to connect my pen drive through the OTG cable but was not successful. Can anyone help...
[Moto E Original Android Development] Adarsh1998:
Usb otg not supported on moto e, hardware is not capable to do that
[Moto E Original Android Development] sastredick:
good day at all , in the weather,can you have your current location ( sorry for my english)
[Moto E Original Android Development] ALPHAWolf96:
Yes you can have your current location but your location must be set to high accuracy mode.

I prefer setting a custom location which u can access in the clock widget settings.

You dont have to tuen on location for that so it wont suck ur battery too.

Hit thanks if helped☺
[Moto E Original Android Development] vinay001:
[MENTION=4913184]percy_g2[/MENTION] [MENTION=3445372]scritch007[/MENTION] [MENTION=5426059]ashwin007[/MENTION] Latest CM builds takes time to wake up screen if some one calls, i think proximity sensor is broken because while covering proximity sensor screen should turn off when call comes but its not happening, only after attending the call screen is off please Check...... Sometimes a reboot fix this and it goes to previous state again...... I see some users reported this i tried CM 24,25 and 26 builds all have this problem.....

---------- Post added at 12:10 PM ---------- Previous post was at 11:42 AM ----------

New CM commit does this fix proximity issue...

Set mProximity to PROXIMITY_UNKNOWN on screen off

In the case where the screen was already off do to the proximity

sensor and the user presses the power button, we need to set

mProximity to PROXIMITY_UNKNOWN so that when the screen comes back

on and the proximity sensor is re-enabled it will be able to pick

up the change in proximity.
[Moto E Original Android Development] Rohitagni:
Where should we make this change?:confused:
[Moto E Original Android Development] ashwin007:
Got f2fs working .If at all anyone wants build I can share and [MENTION=6418968]vinay001[/MENTION] I will look into it so please don't spam.
[Moto E Original Android Development] Simomaster1:
I'm here if you need testers;)
[Moto E Original Android Development] vinay001:
Not spamming [MENTION=5426059]ashwin007[/MENTION] no one reported so :( sorry
[Moto E Original Android Development] rohitshakti:
I installed today's build i.e. 28th Aug. Even my screen comes up after 5-6 sec of incoming call.

Regards
[Moto E Original Android Development] @SidDev:
isn't it possible to make it f2fs by default in regular nightly? [MENTION=5426059]ashwin007[/MENTION]
[Moto E Original Android Development] ashwin007:
No ,until its thoroughly tested.
[Moto E Original Android Development] Simomaster1:
I don't know if you read before...but i want to test your built...thank for your work;). Can i help you testing this rom?
[Moto E Original Android Development] Adarsh1998:
Which recovery you used to format partition? 2.8.5.0? Or you updated 2.8.7? Becoz latest 2.8.7 recovery in your thread not supports f2fs.
[Moto E Original Android Development] Simomaster1:
2.8.5.0
[Moto E Original Android Development] ashwin007:
F2fs build:

1 use twrp recovery from here and format data partition to f2fs

https://www.androidfilehost.com/?fid=24052804347802919

2 Then install my unofficial build from here.

https://www.androidfilehost.com/?fid=24052804347802920

P.S this build runs new 3.4.108 kernel.
[Moto E Original Android Development] Simomaster1:
OMG!!! Thank thank thank!!:fingers-crossed::fingers-crossed: Today i will install it and tomorrow evening i will report my impressions:cowboy:
[Moto E Original Android Development] @SidDev:
2.8.7 supports f2fs

i dont know why you think old will support and not new.

I use a material design theme, there in change FS i can see f2fs,exFat and etc

---------- Post added at 07:38 PM ---------- Previous post was at 07:23 PM ----------

Read this:

Performance Benchmark

F2FS vs EXT4

http://xdaforums.com/showthread.php?t=2697069
[Moto E Original Android Development] Adarsh1998:
I too explored, many people out here also explored, f2fs not on 2.8.7 that's why [MENTION=5426059]ashwin007[/MENTION] made a new build today, that f2fs you see is probably theme error, how can f2fs not available on stock theme that visible on other themes? Its a theme error.
[Moto E Original Android Development] @SidDev:
See the screenshot
[Moto E Original Android Development] Adarsh1998:
Change the theme to default
[Moto E Original Android Development] robsonsilva:
To install do a full wipe traditional (sytem, date etc) then go in and wipe wipe advanced system and convert the date to f2fs and install and install the cm. If you do not start just go back in the recovery and reset default on wipe.

Links by ashwin007:

twrp: https://www.androidfilehost.com/?fid=24052804347802919

cm: https://www.androidfilehost.com/?fid=24052804347802920
[Moto E Original Android Development] Gaurav Shirke:
My phone is rebooting after updating to latest version of this month
[Moto E Original Android Development] Adarsh1998:
Only data or, cache also has supported?
[Moto E Original Android Development] Gaurav Shirke:
I want July builds plz how to download

---------- Post added at 06:47 PM ---------- Previous post was at 06:40 PM ----------

The lattest build has random reboot issue

---------- Post added at 06:55 PM ---------- Previous post was at 06:47 PM ----------

I was on largest build of 27th august my phone was rebooting and caller screen was not coming what to do

Sorry for english

---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------

Any one of you have old build which was stable
[Moto E Original Android Development] robsonsilva:
All it takes to convert the date and the sytem for f2fs. I tried to convert the cache plus the entered bootloop and only convert the system is asking to reset. Sorry for the text is poorly written by traslator not very good at forming words.
[Moto E Original Android Development] Simomaster1:
F2fs report

@ashwin007 I have tested your rom. At first boot i saw that the rom was very laggy but after installing kernel adiutor i changed I/O scheduler from fiops to noop and the problem was solved. The rom is very smooth and fast. Gaming is also smooth without lag. Games like asphalt 8 run very well. For battery life i need more time but yesterday evening battery life was great.

Thank for your work;)

I hope that can be useful to all;)
[Moto E Original Android Development] nilanko:
Is screen on delay upon incoming call fixed in 29th nightly?
[Moto E Original Android Development] vinay001:
i thought that only im having this well its not fixed i tried 29th build....
[Moto E Original Android Development] nilanko:
I too have huge time delay and I have newly flashed 24th nightly. I thought that proximity commit might have fixed it. Thank God I didn't download. I don't understand how properly working stuff break all of a sudden.
[Moto E Original Android Development] vinay001:
me too i think this related to proximity, this problem started frm 23rd Nightly....
[Moto E Original Android Development] nilanko:
Oh thanks for the info. [MENTION=6138124]Adarsh1998[/MENTION] says 28th nightly have no problem? Did you try 28th?
[Moto E Original Android Development] vinay001:
yes i tried i had problems, it happens after sometimes a reboot fix this and will go to previous state again.....
[Moto E Original Android Development] nilanko:
Nothing fixes mine. My mom thinks I'm purposely delaying picking up her call but unfortunately I can't make her understand that I'm using something called CyanogenMod and it has got a call bug lol :v
[Moto E Original Android Development] Rohitagni:
The same goes for mine... I have seen one thing though... If u just use ur phone a few seconds before the call comes... It wakes the screen normally.

I don't think that this bug has been solved.... Just clean installed the 29th nightly
[Moto E Original Android Development] piyushkashyap216:
that's not screen delay its call delay last night i noticed it

when i was using whatsapp suddenly phone starts ringing but no call notification after 3 or 4 sec i saw call notification

pls look into this bug [MENTION=5426059]ashwin007[/MENTION]
[Moto E Original Android Development] nilanko:
I only have 6-7 second delay for screen on otherwise the notification takes 1-2 seconds as usual. On KK things were much snappier.

---------- Post added at 08:10 PM ---------- Previous post was at 07:50 PM ----------

You're right man. I only get that screen on delay when I haven't used the phone for a long time. So can this be related to deep sleep/power suspend of the CPU? There was no such problem before though and this problem is not at all related to the kernel cuz its still there with zapdos.
[Moto E Original Android Development] vinay001:
but there is an issue related to proximity sensor, on old builds when call comes if u block proximity screen will turn off now its not like that it wont turn off only after attending the call it will turn off,and if its in pocket same issue screen wont turn off when call comes.... I think its related to proximity sensor ......
[Moto E Original Android Development] nilanko:
So we need to concentrate in 23rd nightly changelogs which are not even there on cmxlogs :rolleyes:

Whats this btw? http://review.cyanogenmod.org/#/c/106901/
[Moto E Original Android Development] vinay001:
im not sure tis all happend after 23rd or , this issue is irritating and i see reports random reboots in CM....
[Moto E Original Android Development] nilanko:
I faced a random reboot while using the music app :/ Things are getting irritating enough. Can we have full LP material UI and animations on KK? I seriously considering KK :/
[Moto E Original Android Development] paul_damian:
I've upgraded (actually a fresh install, with full wipes, because phone misbehave) a week ago from 20150726 nightly to 20150821 and I'm facing same call notification delay and random reboots. So the call notification delay is there prior to August 23rd...
[Moto E Original Android Development] Rohitagni:
CM Servers are busy?

I have been facing this issue since the day, Cyanogen Recoveries were made available for our device. Whenever I want to download over the CM Updater, I get horrible speeds...

Just take a look here:

However, if I download any other thing, say for example an app from the play store, or even a random apk, normal speeds are obtained

I'm sorry for being off-topic, but this is annoying.

[MENTION=6138124]Adarsh1998[/MENTION], [MENTION=5888184]nilanko[/MENTION] : Bros, have you guys noticed the same?

By the way, the latest nightlies are consuming a lot of battery and also there is the problem of random reboots (soft ones) for things like changing the current track.

EDIT:

Just take a look at the speed I am getting on my computer. Therefore, something is wrong with CM Updater app, not the servers :(
[Moto E Original Android Development] Adarsh1998:
What i can told about is, CM Updater always slow for me from first nightly of cm12, thats why i even didn't downloaded one nightly from updater, and about Apps download from Playstore is, Playstore acquires all of our download speed to download apps asap, that time we see that browsing experience bit lower, and also IDM on windows also downloads faster, issue with CM Updater maybe becoz they dont use Multi Threaded Download.
[Moto E Original Android Development] piyushkashyap216:
i am also facing random reboot (soft reboot) while using crome and music.

and management is also very poor.
[Moto E Original Android Development] zeeshanhussain12:
Use cyan delta to update [emoji16] [emoji16]
[Moto E Original Android Development] Rohitagni:
I have used it.... Consumes a lot of internal memory
[Moto E Original Android Development] Adarsh1998:
I used foldermount to mirror the folder of cyandelta long way back, guess what?!! Zip saved on SDcard!!!

Don't use Cyandelta, it has its own flaws, patching method it uses has lot of risk.
[Moto E Original Android Development] Rohitagni:
Yes... I guess IDM will remain the choice for me.

Also I have noticed a major thing today... There was no wiping of Dalvik Cache when I updated the phone via CM Updater which I do everyday. Don't know why, all the apps are working fine though :confused:
[Moto E Original Android Development] Adarsh1998:
Oh God, that happend you too? Happend me too on probably 22rd nightly something, update not cleared dalvik, and i even flashed xposed (flashing xposed clears dalvik automatically) and all dalvik cache linked to link2sd is also stayed intact.!!!
[Moto E Original Android Development] Rohitagni:
Yeah... Is it something serious to worry about? :confused:
[Moto E Original Android Development] Cheez2553:
Hey guys CM Updater is downloading at maximum speed here (1,7 MB/s).Also i recommend downloading the zip and wiping manually the dalvik(using TWRP Here,,are you guys on CM Recovery?)

Inviato dal mio Moto E utilizzando Tapatalk
[Moto E Original Android Development] Rohitagni:
Well it might be different for ur region... but here in India, something is wrong....

Don't know about others, but I use CM Recovery, it worked perfectly till yesterday, but today didnot wipe the Dalvik Cache
[Moto E Original Android Development] nilanko:
Lollipop is full of mysteries. Nobody knows why certain things happen lol [emoji14]
[Moto E Original Android Development] piyushkashyap216:
its server issue i have 5mps and in cm updater only 200 kbps:confused:
[Moto E Original Android Development] Cheez2553:
Most likely it's a problem of CM provider/host .I think we just need to wait

Inviato dal mio Moto E utilizzando Tapatalk

EDIT

It started to happen to me aswell
[Moto E Original Android Development] piyushkashyap216:
[MENTION=5426059]ashwin007[/MENTION] pls look into memory leak issue

system itself consuming 400 to 450 mb of ram and some times 500 mb ram

i observed that when only 100 mb ram is left system reboots itself so in my opinion system reboot is related to this memory leak bug pls check this.

see the screenshot is this normal?
[Moto E Original Android Development] Gaurav Shirke:
Is reboot issue and calling delay issues are solved in lattest built

---------- Post added at 10:59 AM ---------- Previous post was at 10:55 AM ----------

What is different in cm recovery and twrf recovery
[Moto E Original Android Development] Adarsh1998:
Yeah, me too have that memory leak issue, system leads to unresponsive and ram goes filling up (only 17mb of ram left) , only a hard reboot can solve, i didn't had that issue earlier, maybe one of the recent commits on kernel is the cause? [MENTION=5426059]ashwin007[/MENTION] [MENTION=4913184]percy_g2[/MENTION] please look into this if possible, we need stable build rather then f2fs.:)