[ROM] CM 11.0 (Android 4.4) for AtrixHD
- Thread starter epinter
- Start date
-
- Tags
- development
I'm out of thanks buttons but thanks for posting this here... was thinking about that. Freeze google play service is my only thought. I'll test later.
(info - 6.1.11 is offending version.) EDIT: fixed in CM11N 10-06-14 msn8960 jbbl
Last edited:
Device Development Dead??
I recently noticed there are no significant development for this device! Is this device dead?
I recently noticed there are no significant development for this device! Is this device dead?
No. I'm using mine right now!
p.s. You're looking in the wrong place. Don't look for MB886. All latest CM for AtrixHD and related devices is here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
Passing along some info from the RazrHD thread http://xdaforums.com/showthread.php?t=2518701 to the AHD people (even though most are probably already monitoring that thread
).
There was apparently a Google Services wakelock battery drain issue in JBBL nighties from about 10/1/14 - 10/5/14. The problem is not in the 10/6/14 nightly which is looking good. AHD/MB886, JBBL Philz Touch 6.19.3, PA Micro Gapps 9/1/14
).There was apparently a Google Services wakelock battery drain issue in JBBL nighties from about 10/1/14 - 10/5/14. The problem is not in the 10/6/14 nightly which is looking good. AHD/MB886, JBBL Philz Touch 6.19.3, PA Micro Gapps 9/1/14
Passing along some info from the RazrHD thread http://xdaforums.com/showthread.php?t=2518701 to the AHD people (even though most are probably already monitoring that thread
There was apparently a Google Services wakelock battery drain issue in JBBL nighties from about 10/1/14 - 10/5/14. The problem is not in the 10/6/14 nightly which is looking good. AHD/MB886, JBBL Philz Touch 6.19.3, PA Micro Gapps 9/1/14
JBBL: 10-03 to 10-05 inclusive had the wakelock issue. Don't know about 10-02. 10-01 did not. 10-06 rocks!
Last edited:
Prepare to not be shocked. M11 Snapshot looking good. No GPS/WIFI Google Play Service or any other wakelock.
AHD/MB886, Philz Touch 6.19.3, pa_gapps-modular-nano-4.4.4-20141008
Also…
CM11 M11 Android 4.4.4
Now that’s good version number alliteration!
[EDIT] Stealing from the RazrHD thread again. A nasty camera hardware bug:
DONT DO THIS: set flash to on, takepic, set flash to off, take pic, some kind of camera hardware crash.
Seems avoidable but it's nasty. Read more about it at RazrHD thread.
AHD/MB886, Philz Touch 6.19.3, pa_gapps-modular-nano-4.4.4-20141008
Also…
CM11 M11 Android 4.4.4
Now that’s good version number alliteration!
[EDIT] Stealing from the RazrHD thread again. A nasty camera hardware bug:
DONT DO THIS: set flash to on, takepic, set flash to off, take pic, some kind of camera hardware crash.
Seems avoidable but it's nasty. Read more about it at RazrHD thread.
Last edited:
Is snapshot close to a stable version. Snap shot sounds to me like a nightly. I assume snapshots are constituted as stable?
Your going to make me say "go do some research" if you keep it up. Oh, there I've done said it already
Snapshot is usualy more stable with development frozen at a certain period and a few patches added. This time around there turns out to be a camera bug in the M11 snapshot build that is not in recent nightlies.![[] AL []](/data/avatars/s/3703/3703649.jpg?1600603343){kind=avatar}
I just posted in THE other thread, but experienced that camera problem on Oct 5th nightly...
Cheers
/AL
No problem. I did look it up. Thanks again !Your going to make me say "go do some research" if you keep it up. Oh, there I've done said it already
Flashed the 10-6 nightly,and upon reboot it said in a toast.."settings granted by superuser?" Wth. Never seen that before
Sent from my ATRIX HD
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
Sent from my ATRIX HD
Sent from my ATRIX HD
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
Sent from my ATRIX HD
as per RHD CM11 thread, (sorry no link... tapatalk is not individual post sharing friendly...) camera should be fix on Oct. 10 th (or following...).
I'm on that nightly and have no issues with the camera. May be a KKBL problem...
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
30This is a CM11.0 (Jelly Bean, Android 4.4) ROM for Atrix HD.
This rom should work with a unlocked bootloader.
DEVELOPERS (razrqcom-dev-team):
EPinter - Kernel Development, Build Setup, XT925 & MB886 Support
DHacker - Kernel Development, Build Setup, XT926 Support
Hashcode - Kernel Development, Build Setup, XT926 Support
Nadlabak - Kernel Development, Build Setup, XT897 Support
Skrilax_CZ - Kernel Development, Build Setup, XT897 Support
Download links and information about what is working can be found on the website:
http://www.linuxmobile.org/razrhd/cm11
Instructions:
Download the zip (cm-11-*-UNOFFICIAL-epinter-mb886.zip) and copy to your sdcard.
Boot into recovery.
Backup your firmware and data!
Format /system.
Install the firmware (install zip from...).
Install gapps (install zip from...).
Wipe data/cache
Reboot.
Developers builds:
Epinter: http://goo.im/devs/epinter
DHacker: http://androidhosting.org/Devs/Dhacker29/8CM12
Little Off-Topic
This CM12 build is specific for MB886. Nobody from our team has a MB886 to test, so we will need somebody to test. I strongly recommend a full backup(including media).
https://goo.im/devs/epinter/cm-12-20150217-NIGHTLY-mb886-epinter.zip7
Everyone with JellyBean firmware/bootloader should use moto_msm8960_jbbl builds. Users who updated to KitKat firmware/bootloader need to use the moto_msm8960 builds. Thanks to kabaldan for setting up the build.6
It's not newest. It's 11/21.
Here (dropbox):
11/24:cm-11-20131124-NIGHTLY-mb886-epinter
11/25: cm-11-20131125-NIGHTLY-mb886-epinter MD5: 8E329B39B56D1D589E51DD52E42113B2
11/27: cm-11-20131127-NIGHTLY-mb886-epinter5
Zero. Zilch. A big 'ole goose egg.
Take a look at the JBBL Github page.... There isn't even a CM12 branch yet. It's possible that kaldaban is testing/developing JBBL privately, but I wouldn't hold my breath for a xmas miracle. I doubt dhacker would even bother with JBBL, and Epinter has no commits since January, so we're effectively down to only two MSM8960 heavy lifters. For JBBL, it's just Kaldaban as a one-man team (with an occasional contributor here or there).
Some oceanside-dwelling users would have you believe that getting LP is trivial, our device can easily run it, we don't even need the KK bootloader, just look at the A4G! Ah yes, but such claims ignore the realities of having "super" developers (i.e. giants whose shoulders all of our ROM builders stand upon). The A4G has Quarx. We lost Hashcode and (ostensibly) Epinter. Dhacker had conflicts and quit CM, but then he unexpectedly came back and single-handedly brought CM12 to KKBL. Kaldaban seems to be another one, but who knows how much longer CM12 would have taken if it wasn't for Dhacker. And now everyone wanting JBBL LP is waiting on kaldaban (one guy!) to do the immensely difficult task of figuring out how to remove and work around all of the KKBL-dependent code in CM12.
So in conclusion, don't go around asking what's taking so long, making comparisons to other devices, or talking about porting CM12/KKBL to JBBL like it's some walk in the park for the "devs." I'll bet that many users didn't even know about our current developer situation! Be respectful, patient and grateful that they're even doing this. Without their device trees, the non-CM ROM builders wouldn't be able to do anything! Oh, and you can't forget about Dan Rosenberg for the bootloader exploit unlock.
