Related
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
I'm a serious and long term tester of custom ROMs for various devices, but more recently the 1st gen (Condor) and 2nd gen (Surnia) moto e.
I'm looking for your experiences, comments, tips and tricks of stock firmware (lollipop and marshmallow) verses the many custom ROMs available for the 2nd gen moto e.
Tell me what you find the best ROM.
What's the most stable? Has the best battery life?
What ROM can you make lots of modifications without affecting performance?
What's the worst ROMs? What ROMs have the most bugs?
This is not a post asking for your opinions so I can go out to find the best ROM, personally I have found what I consider the best ROM/set up/configuration for my E2 and am looking to see if other users agree with me.
Many thanks
Sent from my XT1524 using XDA-Developers mobile app
I personally fell in love with the Stock ROM on my XT1521 it has the best performance and is extremely stable. Some may have had issues because they flashed the stock ROM on some other device rather than the device this ROM was made for. Though it has been reported that the UK version has started to receive the 6.0 update. I request everybody to downgrade to the 5.0.2 stock ROM and update to 6.0 through the OTA update.
Again this is my experience and don't bash me for this.
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
I personally fell in love with the Stock ROM on my XT1521 it has the best performance and is extremely stable. Some may have had issues because they flashed the stock ROM on some other device rather than the device this ROM was made for. Though it has been reported that the UK version has started to receive the 6.0 update. I request everybody to downgrade to the 5.0.2 stock ROM and update to 6.0 through the OTA update.
Again this is my experience and don't bash me for this.
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
I won't bash you, your reply is exactly the reply I wanted.
Personally, I'm having better luck right now with the stock rom, but my personal preference is the last build of CM12.1 (17th April security update)
3 day battery life, very fast and the most stable my moto e has ever been.
Less luck with my 1st gen moto e, currently running CM13, it's laggy and very unstable
Sent from my KAZAM Trooper 455 using XDA-Developers mobile app
ivan39 said:
I won't bash you, your reply is exactly the reply I wanted.
Personally, I'm having better luck right now with the stock rom, but my personal preference is the last build of CM12.1 (17th April security update)
3 day battery life, very fast and the most stable my moto e has ever been.
Less luck with my 1st gen moto e, currently running CM13, it's laggy and very unstable
Sent from my KAZAM Trooper 455 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did u get the official 6.0 update???
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
Did u get the official 6.0 update???
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
No, I just flashed it from the firmware thread here, only after cm13 played hell with me!
Sent from my XT1524 using XDA-Developers mobile app
ivan39 said:
No, I just flashed it from the firmware thread here, only after cm13 played hell with me!
Sent from my XT1524 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just try and flash the 5.0.2 Stock ROM for ur model no. and see if u received the 6.0 update cause someone posted that they received it. Also in the past when I tried the stock ROM designed for another model I didn't get great performance but when I flashed the stock ROM designed for my model no. I got the desired performance.
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
Just try and flash the 5.0.2 Stock ROM for ur model no. and see if u received the 6.0 update cause someone posted that they received it. Also in the past when I tried the stock ROM designed for another model I didn't get great performance but when I flashed the stock ROM designed for my model no. I got the desired performance.
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
I apologise for not explaining this fully, meaning you made a completely unnecessary and incorrect reply (only because I gave you incomplete information)
So let me explain fully.
My moto e had issues around the 05/04 build of CM13.
After an upgrade from 04/04 to 05/04 via "dirty" flash (only wiping dalvik and cache) the moto e "hung" and got stuck on the "splash" screen and would not boot.
Returning to twrp to wipe system/data/internal storage was futile, it still would not boot past the Motorola boot logo.
Several people suggested I return my moto e to stock, so I duly returned it to stock BY FLASHING THE EU RETAIL 5.0.2 FIRMWARE FOR XT1524-(the variant of moto e I have)
This was completely unsuccessful as although I returned to stock, I left the bootloader unlocked and re rooted and reflashed twrp as soon as I had successfully returned the device to stock.
After booting into 5.0.2 I checked everything was fully working but found the device to be very slow, extremely laggy and stuttery.
Further research suggested UK users who had manually flashed the 5.1.1 update (you must remember UK has NEVER been offered the 5.1.1 update, as Motorola announced in December 2015 UK was skipping 5.1.1 to go straight to 6.0) got the OTA update after successfully flashing said 5.1.1 EU firmware.
This was again unsuccessful, with the device not quite as slow and laggy as 5.0.2 but now was running a firmware it should NOT have ever received.
Concerned this was my issue and sceptical of the advice I had received about the 5.1.1 firmware, I flashed the EU retail 6.0 stock ROM
I found it
Slow
Battery intensive
Laggy and stuttery, there was no fluidity, the screen movements were at best "jerky"
Ringtone volume reduced to the point I missed incoming calls.
Random reboots.
One point I must make to you and anyone else reading this is to
NEVER FLASH FIRMWARE FOR ANOTHER DEVICE OR FLASH INCOMPATIBLE/FIRMWARE NOT DESIGNED FOR YOUR DEVICE.
That is a very big no no and should not be attempted for any reason.
For example, if I flashed firmware for an XT1521 on my XT1524, I would permanently brick my device.
Same if I flashed XT1527 or XT1523 firmware.
No one should be attempting to flash incompatible firmware.
And to someone who messaged me asking if he could flash a "no carrier" firmware from an XT1526 on to an XT1524 to make this a no carrier unlocked device is simply "NO!"
Flashing a no carrier firmware on a carrier locked device will brick it.
Flashing XT1526 firmware on an XT1524 will brick it.
There may not seem much difference between these variants of devices but I'm told they are quite different, that's why they are numbered in such a way to make them different to the continents for which they are designed for.
This is not my opinion, this is fact, openly found here on XDA and read many times after people have knowingly flashed the wrong firmware on the wrong device and suffered a permanent brick!
I'm pretty sure most of my problems came from flashing 5.0.2 and 5.1.1, and since I had upgraded to 6.0.1 running CM13, I simply made the problem worse but not downgrading modem/bootloader.
I hope this explains my situation fully, but I've found the last security update to CM12.1 (17/04) the most stable custom ROM available for Surnia although I am now back and happy finally with CM13.
Regards.
Sent from my XT1524 using XDA-Developers mobile app
Cm13 22/04 is very good, just as good as CM12.1 17/04 that I came from (clean install, not using any mods other than squid kernel)
Do not use open gapps with CM13, squid has posted various warnings over the past several days to avoid using them as they have broken cm13.
I'm using caf 6.0.1 rom, before I was using aosp 5.1.1 with squid kernel and imo those are the best roms. Sure they don't have any custom features but they don't have every day updates (like cm) too so everything is pretty much polished with decent package of gapps. Both roms are fully stable and basically bug free. I wouldn't change my caf for any other rom.
@ivan39 you're not right. I remember that when there was no 5.1 update in Europe you could easily flash us firmware on Xt1524 changing only one radio file. BTW bugs that you had on stock 6.0 are probably caused by bad flash/not clean flash or something. It's impossible that stock firmware causes random reboots.
Thanks for that, I did not know its possible to flash US firmware on XT1524, so I stand corrected and hanging head in shame.....
Really, thanks for the info, something else I've learned.
Ref 6.0 stock, I assumed a bad flash, reflashed 3 times over 3 days, made no difference.
Agree with everything you said and will definitely look at the roms you mentioned
have you made full wipe after flash?
iks8 said:
have you made full wipe after flash?
Click to expand...
Click to collapse
Yes.
Stock 6.0 wasn't for me.
Back on Cm13
ivan39 said:
I'm a serious and long term tester of custom ROMs for various devices, but more recently the 1st gen (Condor) and 2nd gen (Surnia) moto e.
Click to expand...
Click to collapse
First of all, thanks for your contributions towards the device and the community, Moto E is an underdog but potent device which can really use a helping hand from enthusiasts like us
ivan39 said:
I'm looking for your experiences, comments, tips and tricks of stock firmware (lollipop and marshmallow) verses the many custom ROMs available for the 2nd gen moto e.
Tell me what you find the best ROM.
What's the most stable? Has the best battery life?
What ROM can you make lots of modifications without affecting performance?
What's the worst ROMs? What ROMs have the most bugs?
This is not a post asking for your opinions so I can go out to find the best ROM, personally I have found what I consider the best ROM/set up/configuration for my E2 and am looking to see if other users agree with me.
Click to expand...
Click to collapse
Stock vs Custom ROMs (CM in my case)
My device originally came with Android 5.0, but by that time CM 12.1 (5.1 based) was already available. The jump from Stock 5.0 to CM 12.1 was NOT very exciting. There was an immediate performance drop at the cost of added features. I moved back and forth between Stock and CM just to realise that CM 12.1 RAM usage was way higher than Stock 5.0 RAM usage. I stuck to CM 12.1 due to the extra features and over time, learnet to live with the performance drop.
A few months back, I thought of giving Stock ROM another try, and by that time Stock 5.1 had arrived. Going back to Stock 5.1, to my surprise, I found that the snappiness of Stock 5.0 was gone. I realised that between 5.0 and 5.1, something fundamental changed at Stock ROM/Kernel level and now the Stock 5.1 RAM usage was equal to CM 12.1 RAM usage. That also explained my initial experience, where CM 12.1 RAM overhead was simply because of AOSP 5.1 changes, and not CM additions. At this point, it was only sensible to stick to CM 12.1 as performance drop from Stock 5.1 was minimal.
Recently I tried Stock 6.0, but IMHO it feels rushed, it exists only for the sake of existing. Moreover, I can not believe Motorola/Lenovo can be serious about the software of their lowest-end nearing-end-of-life phone. They had to release 6.0 only to avoid lawsuits for false update promises (made in advertising and on retail boxes).
A final point: I'd prefer CM over Stock any given day simply because of community involvement in development, testing and bug fixing. Being Open Source and hugely popular, CM bugs are reported and fixed much much faster than AOSP bugs. You might say that AOSP is also Open Source, but it's only one way. You can fork, but they don't accept changes back. Overall, I have HUGE trust in CM community than AOSP/OEMs which are only concerned about making more and more money.
Choosing between various Custom ROMs
Most Custom ROMs are developed only in following 2 ways:
AOSP/CAF based
CM based (which is itself AOSP/CAF based)
Type 1 ROMs simply can not match the community involvement and release frequency of CM. Most ROMs I've seen fade away after 1-2 months of updates/support while CM keeps going forever. I see added features only as extra bits that has to be maintained. Moreover, most of the extra features of Type 1 ROMs are already in CM, or available as Xposed modules, or available as root-supported apps. So these ROMs don't bring anything extra to table.
Type 2 ROMs also fail to match the release frequency and long time updates/support offered by CM. Moreover, the added features are also questionable for the same reasons as stated above.
A valid point for considering any custom ROM except CM would either be totally reskinned ROMs, or the ones which are based on other AOSP forks (MIUI etc.). Personally, I fail to see the point of reskinned ROMs. Once you start installing Play Store Apps, you'll quickly realise that Play Store Apps are based on Material (AOSP) UI guidelines. Hence, you'll end up with a system where user apps looks/behave completely different from System apps. That's too much of an eyesore for me.
Some say that ROM X is much faster that CM, but I'm yet to see such a ROM. Benchmarks aside, I've tried almost all ROMs available in our forums and their real world performance is more of the same. For a ROM X claiming to be faster than CM, I'd be very interested to see which code changes have resulted in such a gain and if so, why they haven't been added to CM already.
---
So that's what I think. Let me know what do you guys think. Thanks for raising such a discussion
---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------
ivan39 said:
last build of CM12.1 (17th April security update)
Click to expand...
Click to collapse
https://download.cyanogenmod.org/?device=surnia only shows last 5 builds, where can I download this one? I'm still on 0324 build
gameSTICKER said:
First of all, thanks for your contributions towards the device and the community, Moto E is an underdog but potent device which can really use a helping hand from enthusiasts like us
Stock vs Custom ROMs (CM in my case)
My device originally came with Android 5.0, but by that time CM 12.1 (5.1 based) was already available. The jump from Stock 5.0 to CM 12.1 was NOT very exciting. There was an immediate performance drop at the cost of added features. I moved back and forth between Stock and CM just to realise that CM 12.1 RAM usage was way higher than Stock 5.0 RAM usage. I stuck to CM 12.1 due to the extra features and over time, learnet to live with the performance drop.
A few months back, I thought of giving Stock ROM another try, and by that time Stock 5.1 had arrived. Going back to Stock 5.1, to my surprise, I found that the snappiness of Stock 5.0 was gone. I realised that between 5.0 and 5.1, something fundamental changed at Stock ROM/Kernel level and now the Stock 5.1 RAM usage was equal to CM 12.1 RAM usage. That also explained my initial experience, where CM 12.1 RAM overhead was simply because of AOSP 5.1 changes, and not CM additions. At this point, it was only sensible to stick to CM 12.1 as performance drop from Stock 5.1 was minimal.
Recently I tried Stock 6.0, but IMHO it feels rushed, it exists only for the sake of existing. Moreover, I can not believe Motorola/Lenovo can be serious about the software of their lowest-end nearing-end-of-life phone. They had to release 6.0 only to avoid lawsuits for false update promises (made in advertising and on retail boxes).
A final point: I'd prefer CM over Stock any given day simply because of community involvement in development, testing and bug fixing. Being Open Source and hugely popular, CM bugs are reported and fixed much much faster than AOSP bugs. You might say that AOSP is also Open Source, but it's only one way. You can fork, but they don't accept changes back. Overall, I have HUGE trust in CM community than AOSP/OEMs which are only concerned about making more and more money.
Choosing between various Custom ROMs
Most Custom ROMs are developed only in following 2 ways:
AOSP/CAF based
CM based (which is itself AOSP/CAF based)
Type 1 ROMs simply can not match the community involvement and release frequency of CM. Most ROMs I've seen fade away after 1-2 months of updates/support while CM keeps going forever. I see added features only as extra bits that has to be maintained. Moreover, most of the extra features of Type 1 ROMs are already in CM, or available as Xposed modules, or available as root-supported apps. So these ROMs don't bring anything extra to table.
Type 2 ROMs also fail to match the release frequency and long time updates/support offered by CM. Moreover, the added features are also questionable for the same reasons as stated above.
A valid point for considering any custom ROM except CM would either be totally reskinned ROMs, or the ones which are based on other AOSP forks (MIUI etc.). Personally, I fail to see the point of reskinned ROMs. Once you start installing Play Store Apps, you'll quickly realise that Play Store Apps are based on Material (AOSP) UI guidelines. Hence, you'll end up with a system where user apps looks/behave completely different from System apps. That's too much of an eyesore for me.
Some say that ROM X is much faster that CM, but I'm yet to see such a ROM. Benchmarks aside, I've tried almost all ROMs available in our forums and their real world performance is more of the same. For a ROM X claiming to be faster than CM, I'd be very interested to see which code changes have resulted in such a gain and if so, why they haven't been added to CM already.
---
So that's what I think. Let me know what do you guys think. Thanks for raising such a discussion
---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------
https://download.cyanogenmod.org/?device=surnia only shows last 5 builds, where can I download this one? I'm still on 0324 build
Click to expand...
Click to collapse
Have a look on the cm12.1 thread, I'll post you a link
CM12.1-unoffical-20160417
Wow, thanks for such a detailed reply, I really appreciate you taking the time to offer your experiences!
Stock 6.0 in my experience was awful, I hated it, and can say nothing good about it, even though many users have disagreed with me or told me I'm wrong or did not install it properly.......yeah.....right.......
CM13 is better than it has been of late but just lacks a bit of "polish"
Its way more stable now but it still seems to have "hizzy" fits for no reason, or go totally bonkers for no obvious reason......
Let me take time to say I have been using xposed and various customisation yo make my moto e more like the android n developer preview, and these mods where just a little bit too much for it, it would run fast, fine with no issues for 24-36 hours and then just give up and take over 20 minutes to load a web page or drop a call I was making several times before connecting on the third or four attempt.
Things were better when these mods were removed, but still not learning my lesson, I started experimenting with various launchers and lockscreens just because I love to customise my phone.
Again, this has not helped in my quest to find the ultimate user experience for my E2.
CM12.1
I've found this the most stable, fluid and "fastest" ROM of all.
I agree no ROM is faster than another, but everything just happens a bit faster in the ROM than others.
This ROM is my back up, fail safe and emergency, if I get a bad nightly with CM13 or CM13 misbehaves, I just drop back.
In my experience the difference in looks and behaviour between CM12.1 and CM13 is negligible.
The only difference I see is the adaptive storage in CM13.
Other ROMs.
I found resurrection remix a very good ROM, again, it would work flawlessly for several days and then just go stupid, in the end I gave up using it because it was no better or worse than CM13 (being CM13 based)
No other ROM I tested came close to CM but I have to mention Tipsy OS as a very good rom!
I have a 1st gen moto e that was my original personal daily driver until my work phone (given to me by my employers-A Sony Xperia M2) updated to lollipop and the touchscreen failed.
So my E1 took on the duty of becoming my work phone, I had to get it unlocked from Tesco to take my work Vodafone sim, but at a small cost.
My wife brought me the E2 last December as an early Christmas present (I suspect because it had £20 off the retail price hahaha) and I lost no time modding it, unlocking the bootloader, flashing twrp and installing CM12.1 within the first 24 hours of getting it home.
The E2 is way better than the E1 but the E1 copes with damp and dusty conditions at work, runs CM13 by squid flawlessly and even though its nowhere near as fast or fluid as the E2, it just copes with CM13.
The E2 copes better with anything you throw at it. I'm not a fan overlayed ROMs either but I'm running Xpirits excellent port of sense 7 and blinkfeed on my E2, and its totally fine.
I just wish the ringtone was louder on the E2, I have modded mp3s with various apps but I find them too distorted to use as ringtones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Blinkfeed/sense 7 port by Xpirit on my moto E 2nd gen [emoji41]
Here my take on this subject:
I feel as if the moto e is better now with running cm13 on mine. Stock wasn't bad, just I never been a big fan of xposed(shocker I know) and the longevity of the phone increases for me as I can run the latest android os thanks to the hard work of the devs.
Now I haven't flashed another rom except stock MM. but I feel very contempt for now with cm13 and how it performs for my needs with this phone. Last part off topic:
I also feel as if this could be the last moto e from Motorola(lenova whatever blah) and I also feel like that the moto g will just come in cheaper models that will replace the e. So this phone could be the last of a solid running android phone with stock android under 5inch that's actually worth the money!
Sent from my XT1526 using XDA-Developers mobile app
For me, nothing beats stock 6.0 with squid kernel. I've tried CM13 but the battery life wasnt even similar to stock 6.0 (yes, also with squid kernel installed). I dont play games, i only care about battery life and stock 6.0 is the best for that (at least for me).
pd: CM12.1 and stock 5.1.1 are great too if i install squid kernel + xposed + greenify + powernap. Stock 6.0 doesnt need so much work to give me great battery life.
903tex said:
Here my take on this subject:
I feel as if the moto e is better now with running cm13 on mine. Stock wasn't bad, just I never been a big fan of xposed(shocker I know) and the longevity of the phone increases for me as I can run the latest android os thanks to the hard work of the devs.
Now I haven't flashed another rom except stock MM. but I feel very contempt for now with cm13 and how it performs for my needs with this phone. Last part off topic:
I also feel as if this could be the last moto e from Motorola(lenova whatever blah) and I also feel like that the moto g will just come in cheaper models that will replace the e. So this phone could be the last of a solid running android phone with stock android under 5inch that's actually worth the money!
Sent from my XT1526 using XDA-Developers mobile app
Click to expand...
Click to collapse
I always use the Stock ROM since I faced serious issues with CM13 (But that's another story). I think the official firmware is much more stable compared to CM13, moreover it has Moto display and the audio effects EQ I can't live without. There will be a next Moto e (that's what the rumours suggest. Search Motorola affinity on the web) though it has been reported that it will feature a mediatek chip. This means ROM development will be slow and there will never be official CM13 on that device.(Since Cyanogenmod officially support only snapdragon chips).
Sent from my MotoE2(4G-LTE) using Tapatalk
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
I'm not sure what the holdup is on the
Official Lineage Verizon builds for the G3,
(as of this writing that directory is still empty), but I just switched over to Verizon with their new Unlimited data plan and I decided to build my own this morning. I saw that a few people had been wanting this, so I figured I'd put it up here.
** Note that I compiled this with 'export WITH_SU=true' so there is no need to use the 'addonsu-arm-signed.zip' (root addon) that they provide, as it's built into this rom already.
LineageOS:
Lineage-14.1-Verizon-vs985
GApps: (ARM, 7.1, Nano)
http://opengapps.org/
have bugs?
ngato35 said:
have bugs?
Click to expand...
Click to collapse
sure, it has plenty of bugs, but no more than any other current lineage 14.1 build (I've tested lineage on a samsung galaxy s5, htc one m8, lg g3 (ls990), lg g3 (d851), and an lg g3 (d855)... this build works virtually identical to those.
cm13 is still the best way to go for now if you need stability, i just wish miracast worked better... lineage 14.1 did improve miracast quite a bit, but theres other problems... like conflicts with certain apps (like power toggles, the hotspot won't function properly, you have to enable that via lineage menus, might be an issue with their new su/root implementation) stuff like that.
but... it runs just as well as any of the 'official' builds if that helps answer your question
good work thank you
Upload
Thank you for this, been waiting.
Uploaded with Banks Dynamic Mini Gapps and 35B modem. Everything is clean and seems to be working great. Will you continue to keep it updated with the latest from lineage as they continue to update the rom.
Great rom, but when I enable encryption and reboot the phone hangs on the LG logo and bootloops.
Edit: Encryption is broken in Lineage 14.1 currently
the bot builds on fridays
Been using 307 Rom for two days and am impressed. Great battery life, smooth, and good calling on 35b.
Thanks for your work.
looks like it's finally been added to the official builds,
i'll continue to do builds of lineage 13.0 for this phone, as thats what i'm using,
but no sense in continuing this thread....
here's the first official build:
https://lineageos.mirrorhub.io/full/vs985/20170310/lineage-14.1-20170310-nightly-vs985-signed.zip
Bailx said:
looks like it's finally been added to the official builds,
i'll continue to do builds of lineage 13.0 for this phone, as thats what i'm using,
but no sense in continuing this thread....
here's the first official build:
https://lineageos.mirrorhub.io/full/vs985/20170310/lineage-14.1-20170310-nightly-vs985-signed.zip
Click to expand...
Click to collapse
Has anyone used the official build for the G3?
My fiance has one, and I may steal her phone and flash it. Battery life would be nice, as well as getting rid of the VZ bloat. Any bugs? App compatibility? Thanks!
yes im using nice rom
I have used Bailx 304 and 307 roms, and loaded the official Lineage 310 rom today. Lineage had done a great job with 14.1 with excellent battery life, smoothness, and speed. I have tried all the 7.1 roms for the G-3, and all are exceptional in how far they have come with reliability. I basically use my phone for that purpose, a few texts, and a few photos, so I'm not much into a lot of mods. The only one I really use is Nova Launcher to set up the way I like. The Gapps I used were the Banks Dynamic Mini and by the time I had finished setting my phone up I had used 5.9 gig of 32.
any chance these builds can have volte on vs985? Is that feasible at all? Please let me know.
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?