I used one of the latest nightlies after modifying the zip because I like the 2.7.1.1 twrp. It worked for me using my ultra but I kept having issues with google accounts/ services not responding
[CM11][Official] Cyanogenmod Support Dropped
- Thread starter Jaocagomez
- Start date
Latest Nightly Problems
Are you guys who are experiencing problems with the latest nightlies doing a "clean" install. That is, wiping data, cache, and dalvik cache? That might help.
Are you guys who are experiencing problems with the latest nightlies doing a "clean" install. That is, wiping data, cache, and dalvik cache? That might help.
No. I am deleting system cache and Dalvik. I don't have enough room to back up my phone.
Sent from my XT1080 using Tapatalk
Sent from my XT1080 using Tapatalk
crap, as always, last time i've bought photon 4g and hoped that cm will continue update, but it was a punch from motorola with no 4.x kernel, and now i've bought droid maxx with hope that i'll ever unlock the boot loader and flash cm... two fails from moto :crying:No more CM support.
This is beyond irratating. None of the nightlies work without signifigant errors and even the snapshot has some irratating bugs such as no speakerphone. So irritating. And no support now. Phhhhaaaahhhh so stupid.
The returning of the CM for moto droid's
http://forum.xda-developers.com/dro...d-2013-droid-ultra-family-cm11-ghost-t2911626
17 oct build, droid mini, wi-fi and signal strength; sound and buttons (with patch) works fine for me.
Last edited:
A built that is ready for testing: http://skrilax.droid-developers.org/cm-12-20150109-UNOFFICIAL-obake.zip - I mainly need to see, that in Settings >> About you see correctly model name (DROID Mini / DROID Ultra / DROID MAXX). Second thing to test is in-call audio, unfortunately, due to a CM bug, to hear something, right now you got to flip speaker on or off. Main thing to test afterwards, that for example toggling volume works (to see it loads correct libraries). And on DROID Mini, audio from media application as well.
See the Moto X thread for installation and issues (it's an early nightly, so there is bunch of them): http://forum.xda-developers.com/moto-x/development/rom-cyanogenmod-12-moto-x-t2995381
Note: If on VZW, use in fastboot mode "fastboot oem config carrier vzw" (default). On other carriers, use "fastboot oem config carrier gsm".
See the Moto X thread for installation and issues (it's an early nightly, so there is bunch of them): http://forum.xda-developers.com/moto-x/development/rom-cyanogenmod-12-moto-x-t2995381
Note: If on VZW, use in fastboot mode "fastboot oem config carrier vzw" (default). On other carriers, use "fastboot oem config carrier gsm".
Last edited:
I would assume we use the gapps on the moto x thread right?
Sent from my xt1030 using Tapatalk
Sent from my xt1030 using Tapatalk
I tried to install the package, and ran into a few snags caused by lack of an obake specific recovery. The Moto X TWRP doesn't provide any assert properties for Droids, so the initial assert will always fail. Moto X Philz will provide "ghost" as a property, and nothing else. This has been sufficient for us to install the ghost builds using Philz. However, since the new obake build doesn't look for "ghost", install fails.
So, until we have a proper obake recovery, the obake builds won't install.
I'll install with a modified script in a bit, and will update with my results.
Cheers!
Last edited:
Attached CM 5.0 recovery that I use.
EDIT: Updated 12/01 9 AM GMT+2 - uploaded correct recovery.
EDIT: Updated 12/01 9 AM GMT+2 - uploaded correct recovery.
Last edited:
Thank you... Would ghost twrp 2.8.3 work for the install? I know it works on my droid maxx otherwise... Its my recovery right now on my maxx
Based on the bootloop post I saw on the Moto X CM12 page, I got it to work after a lot of hurdles.
The below steps got it booting up (add gapps to step 3 if you want it to work)
1: install philz ghost recovery, and last CM11 Ghost build
2: Boot and finish initial setup in CM11.
3: Install CM recovery. Wipe cache. Install CM12 Obake build.
4: Reboot and wait... less than two minutes and "Android is upgrading..."
Initial findings:
Will test bluetooth and calling tomorrow. Too late to call anyone, and too cold and dark to go fiddling in my truck. =)
Cheers!
The below steps got it booting up (add gapps to step 3 if you want it to work)
1: install philz ghost recovery, and last CM11 Ghost build
2: Boot and finish initial setup in CM11.
3: Install CM recovery. Wipe cache. Install CM12 Obake build.
4: Reboot and wait... less than two minutes and "Android is upgrading..."
Initial findings:
- software buttons are properly disabled.
- hardware functions work as expected, lights and haptic feedback work.
- "com.android.phone has crashed" two or three times, and then a reboot. Repeats.
- External audio works. Vol+/- works. Tested with XiiaLive
- LTE connects without fiddling (carrier: gsm)
- Wireless connects without issue.
- Settings > About : shows DROID Mini
Will test bluetooth and calling tomorrow. Too late to call anyone, and too cold and dark to go fiddling in my truck. =)
Cheers!
Thanks for testing - yes about phone crashing, you MUST install gapps or CM12 will not work at this point. I will look into why software keys do not work for Droid Mini and post a new build (probably just missed its .kl / .idc file). Can you reboot, wait until it boots to homescreen, and post me a logcat (since those touch keys work on MAXX)?
In CM12 a bug for phone calls is that you must toggle speaker on/off to get incoming audio during call, that's what I found.
In CM12 a bug for phone calls is that you must toggle speaker on/off to get incoming audio during call, that's what I found.
Software keys are supposed to be disabled. That's a good thing. Sorry if I wasn't clear. =) I was comparing from what I saw in the Moto X roms. The hardware keys work properly. Sorry for the confusion.
I was able to test calling, and everything seems to work as expected (meaning toggle speakerphone to get audio). I'll hopefully be able to test Bluetooth later today.
Oh I see, yeah I misinterpreted that about soft keys. Very good then, so Mini is same shape as MAXX. Perfect
I'll post a new build with some bugfixes that came up during review and stuff I'd need to double check is OK.
I'll post a new build with some bugfixes that came up during review and stuff I'd need to double check is OK.
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone