yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] cool_ravi78:
This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (kk), which is designed to increase performance and reliability over stock Android for your device.

#include

/*

* Your warranty is now void.

*

* I am not responsible for bricked devices, dead SD cards,

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if

you point the finger at me for messing up your device, I will laugh at you.

*

ROM INFO:-

This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (kk), which is designed to increase performance and reliability over stock Android for your device.

#include

/*

* Your warranty is now void.

*

* I am not responsible for bricked devices, dead SD cards,

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if

you point the finger at me for messing up your device, I will laugh at you.

*

THIS ROM MADE BY SIR BY VIỆT TRƯƠNG U GUYS CAN VIEW HIS PROFILE ON FACEBOOK HERE, I M JUST WRITING THIS ON BEHALF OF HIM

https://www.facebook.com/viet.truong.3517

ROM INFO:-

1. MIUI V6 (4.4.2) (BY VIỆT TRƯƠNG) fb profile link of devloper of this rom

https://www.facebook.com/viet.truong.3517

DOWNLAOD LINK:----

https://drive.google.com/file/d/0B99EcV9JTTQfcVZqNnZCNFVvbUE/view?usp=sharing

ROOT ZIP:-

https://www.copy.com/s/1HAA98Vz9rFdb7uw

INSTRUCTION>>>

- Make sure you're running a proper working CWM TWRP or CTR

- Copy ZIPs to your SDCard

- Boot into Recovery

- Wipe Data/Factory Reset"

- Wipe Cache

- Clear delvik cache

- Flash zip from SDCard

- Reboot

-FLASH ROOT ZIP IF U WANNA ROOT FOR LINK SEE ABOVE

SS
[Miscellaneous Android Development] Yogendra Kher:
This rom is flashable to gionee M2?
[Miscellaneous Android Development] Damionix:
Bluetooth Audio Issues

Everything seems to be working except for Car Bluetooth.

It pairs fine with no issues. However, the problem I have is when I try to make a call.

It says "Unfortunately Bluetooth Share has stopped working" and it disconnects and hands the call back to the phone's speakers.

Any fix for this?

Thanks.
[Miscellaneous Android Development] Moynia:
Great ROM, made my BLU Studio Energy run much better, and is much smoother than the stock ROM. The only problem I have with the device is that video playback does not work. Youtube videos and all gifs from any website will not load correctly and look like a jumbled mess. Other than that I have had no problems with the ROM.
[Miscellaneous Android Development] ashish_zarekar:
can any one provide me root zip
[Miscellaneous Android Development] Bu2ng03:
good day how many mins it takes to boot
[Xposed General] josiphgorgis:
Hey i just installed the latest version of Android Revolution HD

I try to install xposed but for some reason its not compatible is there any way to make it compatible? it said yet not compatible with Android SDK 21
[Xposed General] kingvortex:
See the pinned thread here for information on Lollipop compatibility. :)

Sent from my C6603
[Xposed General] Sartharon:
Here is an other post from rovo posted today in an other thread :) time to get excited :))

Here's the link http://xdaforums.com/showthread.php?p=58751037
[Miscellaneous Android Development] cool_ravi78:
This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (kk), which is designed to increase performance and reliability over stock Android for your device.

#include

/*

* Your warranty is now void.

*

* I am not responsible for bricked devices, dead SD cards,

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if

you point the finger at me for messing up your device, I will laugh at you.

*

ROM INFO:-

This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (kk), which is designed to increase performance and reliability over stock Android for your device.

#include

/*

* Your warranty is now void.

*

* I am not responsible for bricked devices, dead SD cards,

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if

you point the finger at me for messing up your device, I will laugh at you.

*

THIS ROM MADE BY SIR BY VIỆT TRƯƠNG U GUYS CAN VIEW HIS PROFILE ON FACEBOOK HERE, I M JUST WRITING THIS ON BEHALF OF HIM

https://www.facebook.com/viet.truong.3517

ROM INFO:-

1. Freeme Os BY Việt Trương fb profile link of devloper of this rom

https://www.facebook.com/viet.truong.3517

DOWNLAOD LINK:----

https://drive.google.com/file/d/0B99EcV9JTTQfcUJwcUlMZmducTA/view

ROOT ZIP:-

https://www.copy.com/s/1HAA98Vz9rFdb7uw

INSTRUCTION>>>

- Make sure you're running a proper working CWM TWRP or CTR

- Copy ZIPs to your SDCard

- Boot into Recovery

- Wipe Data/Factory Reset"

- Wipe Cache

- Clear delvik cache

- Flash zip from SDCard

- Reboot

-FLASH ROOT ZIP IF U WANNA ROOT FOR LINK SEE ABOVE

SS
[Hisense Sero 7 Pro Questions & Answers] InfamousGam3r:
View attachment 3155405

View attachment 3155406

View attachment 3155407Hi, I recently attempted to fix my Hisense Sero 7 Pro tablet Micro USB Port, I got the old port off, but it looked like the pins were still on the board? ._. So I pit the soldering iron to the pins on the board and I think I may have just screwed the whole thing up.. I ordered a replacement part, but its no use to me if I can't use the board anymore.. I took pics, any help would be nice. I have I think .8mm solder and a 30w soldering iron with the small tip.
[Hisense Sero 7 Pro Questions & Answers] Volfanoftwins:
Same here

I have a Sero pro that is not charging. I think the USB port is messed up. Not sure how to fix it. Never soldered something this small.
[Hisense Sero 7 Pro Questions & Answers] ryancell:
I just wanted to post this up for anyone who may have had issues with their sero 7 pro's. I have 2 units for my kids, which after many times of charging have had broken/faulty usb connections. In a desperate attempt to keep the same table w/ their games/save progress intact I searched for a way to fix the units. Finding my basic soldering skills not good enough I went to ebay. I found a guy who repaired both my kids tablets (as well as my nexus 7 tablet) for a reasonable cost and shipped them back to me very quickly.

If anybody needs a usb repair, tell him Ryan sent you and he'll fix you up too! Now my kids are back on track & their units are fully charged as they should with a new usb port!

http://www.ebay.com/usr/myers-mydevicerepair
[Hisense Sero 7 Pro Questions & Answers] rewind22x:
Successfully used myers to repair 2 of my Sero 7 Pros. Would use him again. Thanks for the tip!
[Galaxy Note II Q&A, Help & Troubleshooting] ralph1968:
Hello guys

i have some problems with sidesync it connects and shows up right but i can't operate with touch from tablet or even mouse from pc.

Is anybody here who has it running correctly?

Please help....
[Galaxy Note II Q&A, Help & Troubleshooting] ugbatur:
any body help!!

ı try many rom but this problem continuing.

please help us!
[Moto E Original Android Development] ashwin007:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.

At this point,I need support from any dev willing to work for this project.My trees are here.

https://github.com/ashwinr64/android_device_motorola_condor/

https://github.com/ashwinr64/android_kernel_motorola_msm8610

https://github.com/ashwinr64/android_vendor_motorola_condor

Btw,no hard feelings for anyone out there including [MENTION=5874764]#buzz[/MENTION]

I hope we can port LP very easily soon.
[Moto E Original Android Development] gaurav2009:
First thanks o.o
[Moto E Original Android Development] Brawn_Sg:
Why dont u use philz touch recovery or CWm for flashing

on cm and twrp recovery I also sometimes get those errors
[Moto E Original Android Development] ashwin007:
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.

I will be trying a clean build 2day.
[Moto E Original Android Development] ace312:
Which version of cwm recovery is in the build?
[Moto E Original Android Development] goutamniwas:
gud work

[MENTION=5426059]ashwin007[/MENTION] is it compiling ? (kernel source )

Edit :

This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0

check if some commits are missing
[Moto E Original Android Development] ashwin007:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock

Could you do me a favour?

Can you build twrp from kk tree using my fstab in

My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!

BTW I love your t2u.amazing!!!!

P.s:even my native place is Coimbatore.

EDIT:Well [MENTION=6024615]ace312[/MENTION] its no more cwm in cm tree.its cyanogen recovery made by cm
[Moto E Original Android Development] goutamniwas:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying::rolleyes:

bw tat means u cant install it anyway ?

also thanks much for the complements
[Moto E Original Android Development] ashwin007:
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.
[Moto E Original Android Development] GeekyDroid:
Hey,

Why don't you flash system.img and boot.img with fastboot?
[Moto E Original Android Development] sw33ty4ppu:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.

CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.

Sorry [MENTION=5426059]ashwin007[/MENTION] for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
[Moto E Original Android Development] ashwin007:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do

Sw33ty4ppu not a problem.I think you have helped many of them.
[Moto E Original Android Development] ace312:
okay. it's been months I left ROM development. Sorry about that.
[Moto E Original Android Development] GeekyDroid:
Well, sorry I thought it is less than 215MB. I didn't think of it.
[Moto E Original Android Development] Zeroemd:
My last device was a motorola defy and developer [MENTION=513620]Quarx[/MENTION] has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.

Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.
[Moto E Original Android Development] prince trishi:
Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!! :D:D:D

•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•
[Moto E Original Android Development] dchatterjee172:
see the attachment...

Lolipop is more closer...
[Moto E Original Android Development] ashwin007:
This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.
[Moto E Original Android Development] Jamiéric GS:
http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1
[Moto E Original Android Development] Gandalf:
I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:

Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.

If you have a question, SEARCH FIRST, per the Forum Rules
[Moto E Original Android Development] mits619:
Lollipop /vendor/bin/lib files and boot.img

[MENTION=4584140]cybojenix[/MENTION] [MENTION=5426059]ashwin007[/MENTION] [MENTION=4913184]percy_g2[/MENTION] [MENTION=5874764]#buzz[/MENTION]

Pulled from phone

Here are the /vendor, /lib and /bin files pulled from 5.0.2 : here

And boot.img : here
[Moto E Original Android Development] scritch007:
Good news lollipop by motorola never comes alone

Hi all,

I decided to give cm12 a try for the moto. Based on [MENTION=4913184]percy_g2[/MENTION]

So here is the first screen shot of this build. It's very early stage, but it's still a good news.

Unexpected reboots, no wifi, no data...

Some of the changes are already on my github but not all of them.

I need to get a little bit more of information regardings the partitions.

Can some of you paste the result of cat /proc/partitions please. From KK and from lollipop.

Thanks in advance, and I hope I can fix most of the issues first before releasing this version.
[Moto E Original Android Development] hussain59:
Thank's for ur effort buddy
[Moto E Original Android Development] chemicalrage:
Here's Kitkat,

root@condor_umtsds:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

7 0 30177 loop0
179 0 3866624 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2350464 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 30915584 mmcblk1
179 65 30914560 mmcblk1p1
254 0 30177 dm-0
[Moto E Original Android Development] Rio257:
lolipop

u0_a148@condor_umtsds:/ $ cat /proc/partitions
major minor #blocks name

7 0 2092 loop0
7 1 5224 loop1
7 2 37604 loop2
7 3 4180 loop3
7 4 10448 loop4
7 5 7312 loop5
7 6 27160 loop6
7 7 26112 loop7
253 0 262144 zram0
179 0 3825664 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2309504 mmcblk0p36
179 32 1024 mmcblk0rpmb
179 64 30915584 mmcblk1
179 65 29676544 mmcblk1p1
179 66 1230848 mmcblk1p2
254 0 2092 dm-0
254 1 5224 dm-1
254 2 37604 dm-2
254 3 4180 dm-3
254 4 10448 dm-4
254 5 7312 dm-5
254 6 27160 dm-6
254 7 26112 dm-7
7 8 2092 loop8
254 8 2092 dm-8
7 10 13580 loop10
254 10 13580 dm-10
7 11 5224 loop11
254 11 5224 dm-11
7 12 17760 loop12
254 12 17760 dm-12
7 13 17760 loop13
254 13 17760 dm-13
7 14 8356 loop14
254 14 8356 dm-14
7 15 26112 loop15
254 15 26112 dm-15
7 16 5224 loop16
254 16 5224 dm-16
7 17 19848 loop17
254 17 19848 dm-17
7 18 7312 loop18
254 18 7312 dm-18
7 19 16712 loop19
254 19 16712 dm-19
7 20 32380 loop20
254 20 32380 dm-20
7 21 21936 loop21
254 21 21936 dm-21
7 22 6268 loop22
254 22 6268 dm-22
7 23 18804 loop23
254 23 18804 dm-23
7 24 13580 loop24
254 24 13580 dm-24
7 25 4180 loop25
254 25 4180 dm-25
7 26 5224 loop26
254 26 5224 dm-26
7 27 6268 loop27
254 27 6268 dm-27
7 28 22980 loop28
254 28 22980 dm-28
7 29 41780 loop29
254 29 41780 dm-29
[Moto E Original Android Development] rekoilchafe:
Here's for Lollipop
[Moto E Original Android Development] mits619:
Here is the detailed partion details pulled from lollipop :

lrwxrwxrwx root root 1970-01-01 05:55 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 05:55 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 05:55 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 05:55 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 05:55 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 05:55 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 05:55 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 05:55 dhob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 05:55 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 05:55 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 05:55 hob -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 05:55 kpan -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 05:55 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 05:55 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 05:55 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 05:55 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 05:55 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 05:55 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 05:55 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 05:55 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 05:55 pds -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 05:55 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 05:55 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 05:55 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 05:55 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 05:55 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 05:55 sdi -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 05:55 sdiBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 05:55 sp -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 05:55 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 05:55 system -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 05:55 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 05:55 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 05:55 userdata -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 05:55 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 05:55 utagsBackup -> /dev/block/mmcblk0p15
[Moto E Original Android Development] scritch007:
Thanks all that will be enough. It's the same as mine. So I can set correctly the values.
[Moto E Original Android Development] GeekyDroid:
Well, that's really great! Thanks for your efforts. But may I ask you how you got it booting and what recovery did you use? Because on your github you haven't done any changes in kernel although I thought that we had conflicts in kernel.
[Moto E Original Android Development] scritch007:
For the recovery I'm using openrecovery-twrp-2.7.1.0-condor.img . I got the cyanogen recovery booting, but it doesn't allow backup/restore so for now on I'm using this recovery I found on the XDA Moto E forum

Ok so regarding the kernel, you can check in the branch new-cm-12.0 branch which is percy's branch + git am from falcon kernel. THis was the first kernel that I used to build the rom.

I had to patch a little the build/core/Makefile so that instead of building new lollipop flashable zip, it uses the KK zip. But I think that setting correctly the partition values, will allow flashing with the new lollipop style, this is why I asked for the /proc/partitions, in order to be sure that I updated correctly the partitions values in the android_device_motorola_condor.

This was kind of fast, I actually got a build booting pretty easily, but no display. I tried ashwin's kernel, but same issue, I just figured it out last night what was the problem with the display, and I cherry picked a few new commits to fix this. So this morning I had a booting build with display.

Since the reboot is caused when the phone isn't used and tries to do something before normally turning off the screen and so on , I didn't push this new branch. I got to fix some minor (let's hope so) changes in the init/ramdisk and test that before, to fix audio and RIL and I hope wifi too.

Only problem is that I don't have that much time, and my laptop is not very fast to create nice full builds. My current is mostly some patches hand made for now, with some adb push :) and small zip updater.

I'll try to provide a flashable zip tomorrow, for those who want to give it a try, let's hope it will be more usable then it's current state.
[Moto E Original Android Development] #buzz:
Thanks for sharing your amazing work. I have been trying hard for building Slim rom 5.0.2 for this device and I couldn't boot the rom. The kernel proved a hard time for me. I didn't think of using the patch from falcon. Your patches and commits on the trees is really helpful for me to continue with my work. Now that Percy started back his work on making the rom more stable, we can expect some stable build from him. If I have time, I will start weeklies (hopefully, if I get back my build server). Your contribution is really a milestone for the development on this device.
[Moto E Original Android Development] scritch007:
Hi [MENTION=236331]buzz[/MENTION]

Thanks for your post

I wasn't clear enough in my previous post. The exemple of the new-cm-12.0 branch was just to show that I had done something to get the kernel booting. The correct kernel is now pushed on github and in the cm-12.0 branch.

No need to look at my github anymore, you can check percy's one, all the fixes will now go in his repositories. We'll be working together in order to bring a cm12 as stable as possible, although I believe that he's gonna fixe all the issues before I even have time to work a little bit on this ;)
[Moto E Original Android Development] love4chat:
Lets Go With MOTO,Thanks for building CM12 for MOTO E!
[Moto E Original Android Development] GeekyDroid:
Well, as I'm not an advanced user, I barely can help you in fixing bugs. But when you fix "all"(let's say almost all) bugs, I'll try to build some ROMs so we get more ROMs than this "lame" CM12. Also, [MENTION=5874764]#buzz[/MENTION] if you have problems finding a build server, contact me, I have a PC which builds fast, so you just have to tell me what patches you did and I'll apply them. Just leave the rest to me. :) This goes to everyone. So if anyone here got a slow PC or slow internet connection, I'll be here to provide you a free service. :p :good:
[Moto E Original Android Development] prathameshmestry:
Great work bro...!! Thanx for developing cm12 for moto e...!! ????
[Moto E Original Android Development] #buzz:
Here's preview of PAC MAN 5.0.2 made by myself! :)

Thank you scritch007 for the awesome work on kernel!