Search results

Any idea what's going to happen now with development that CM is officially gone?

Thank you for this! Flashed on my D2SPR and 3G works fine, no LTE for some reason though even when flashing fixes. No crashes, good battery life, everything seems to work great. :D

Hm? Really? I am not seeing that. Would be great if D2SPR did get 14 though, considering the other variants have gotten Android N.

I know development has stopped for M on OctOS for this device, whoever, how is battery life/SoT?

Ambient Display doesn't appear to be activating for me, any idea?

Huh, alright. I guess when I get it tomorrow I'll just check for root, and go from there. If it's rooted I may just have to deal with it.

Well, I appear to be getting different answers from varying people then. This is going to be a pain I can see, I heard Kies' "Software Upgrade and Preparation" tool, it could bring me back to stock everything. If I can't get SafetyNet to pass, then it'll defeat the entire purpose of me getting...

No no, I understand that. I only asked if the stock recovery would return because I have no use of a custom recovery. I'd prefer to just go 100% stock.

Alright! If I flash back to stock, will that remove custom recovery as well?

So basically, I'd activate the phone, flash back to stock. Then Flash an APN fix in recovery? Would the flashing work in a stock recovery?

I'm just now ordering an S3 from Freedompop, my understanding is they use their own custom ROM for the FP Apps, etc. If I flash back to Samsung Stock Firmware, and run a PRL Update, etc, will I still have a connection on Stock?

How is battery life/SoT on this ROM?

Everything appeared modified, it appears to have an issue with the updater_script and also with two filed requiring mounting. It builds entirely fine though.

I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.

Yes, but you can't build MIUI from CM without dealing with several rejects. Stock Moto Firmware has certain changes that can also cause some issues. It's a bit of touch and go when it comes to setting it up. Someone with more experience in MIUI will have to take up such a project.

Please wait until I update the link, there was a name change required for the device and it won't flash. This new build should hopefully resolve that issue though. :) ---------- Post added at 03:34 PM ---------- Previous post was at 02:51 PM ---------- One of the main issues with the Moto E is...

Hm, any rejects or anything out of the ordinary? ---------- Post added at 02:15 PM ---------- Previous post was at 02:00 PM ---------- Build is COMPLETE. I'll provide a link to those who want one when it is finished/uploaded. ---------- Post added at 02:33 PM ---------- Previous post was...

Did it get stuck at building or booting?

Beginning the Surnia Build now, Angler build was successful with no Rejects, we'll see how this build goes for Surnia. EDIT: Noticing Some Warnings already, will see how this effects the build process, if it does in any way. If this does build successfully, would someone mind testing it for me...

As soon as the Angler Test build completes successfully with no rejects, I'll immediately push to the Surnia build. :)

UPDATE: Test Building for Angler to make sure everything is sync'd as necessary, then will start the process for Surnia, and see where we get with that, if a build does go through successfully, I may need someone to help test it.

Started syncing about 30 minutes ago, almost wrapped up now and I'll start a build hopefully.

Also downloading Repo's, I'll take a look into it.

Is Now on Tap usable? I would like to be able to use it.

Does the issue of data not connecting after so many times of being turned on/off exist in the latest build as it does in AOSP?

Has anyone tried flashing OpenGApps aside from Pico? I want to make sure it'll work properly.

Wow! That's amazing work! Great news for those who couldn't use their data. :D

Perhaps a bit later I can look into compiling a build. I'll keep you informed.

I am on the Boost Mobile XT1526 and can confirm data is working on my device.

Thanks for your continued work on this! Downloading now, will let you know if I find anything out of the ordinary. ---------- Post added at 12:20 PM ---------- Previous post was at 12:11 PM ---------- So far everything works great on XT1526, Data works, seems more stable so far. I'll post an...

Anyone on XT1526 confirm sim still not showing? Ironically I was mistaken on my device being dual sim. Its a single sim XT1526. But CM14 won't detect mine. EDIT: I'm also noticing my baseband version is "Unknown", perhaps the baseband wasn't flashed properly?

Quick reply, I will try to get logs in a moment, error still persists for no SIM on CDMA Variants (Boost Mobile XT1526), camera works now, however. So far it appears SD card is working normally.

Yes, this problem is specifically on the CDMA variants to my knowledge. ---------- Post added at 06:32 PM ---------- Previous post was at 06:09 PM ---------- Awesome work! Can't wait to see what comes in the future!

Of course if it'll stop the error. ---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ---------- This worked! My friend you are a genius! Thank you so much!

The whole point of doing this process is to be presented with a mute notification icon so the force close option goes away and you can use your phone freely. However I haven't been presented that.

I force closed, cleared data, for all the apps with cell phone icon, and I've gone through this process several times, I've clicked close app hundreds of times but it won't show a thing. :( ---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ---------- I will try...

Still tried everything suggested and it won't present me with a mute option...

So I followed your instructions and sadly I'm not seeing it either... .-. I got it to say com.android.phone keeps stopping. But no mute until device restarts comes. Is the reason I'm not seeing it because I flashed GApps Micro instead of Pico?

As I said, you'd have to try AOSP (this build), and his CM14 build. Trust me you'll see the difference. I've tried both, and AOSP isn't even usable as a daily driver yet, while his CM14 is already considered stable in many respects.

In most respects, yes, not in this case however. If you were to try the two builds on the same device, you'd see drastic improvements for stability and usability on the CM14 build.

Yeah, the only concern for me is this the fact that this is a daily driver for me, however, I don't use data as much as I do wifi, so it won't necessarily be an issue, but it will be something nice to have in the future.

Thanks for informing me of that! That is a life saver for using the ROM on the dual sim variant without having the popup. :P

Well, currently, the maintainer of this AOSP Rom has also released a CyanogenMod Build for the Moto E LTE, so that's two ROM's to support, he has already claimed he is busy. As for the SIM issue, AOSP (this build) recognizes my SIM, however, his CM14 build which is more stable, doesn't. That's...

This actually recognized that there was a SIM in my XT1526, I wish this was still being supported, I hope CM14 will resolve that issue soon.

How would I be able to grab those logs? This is the first time I'd be having to do so.

I'm on XT1526 as well. If that's the case, then that's really a shame, oh well.

I get that as well. Did I miss something during the install, or?

My Recovery didn't change after I flashed the ROM. Could be a variety of reasons why it did it.

Will do! I'm noticing whenever I close an app some moments where it'll sit there at the recents menu for about 5 seconds after I've closed the app. It appears if you set the CPU past the 990MHz range it seems to struggle to keep up with certain system tasks, or returning home. EDIT: I've done...

The Youtube App still won't work properly, however, the YT Gaming App works just fine.