yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix HD] [] AL []:
Still on my dirty nightly flashing back and I've unexpectedly found a way to reproduce the issues that I've reported having 2-3 posts above:

- get this app : https://play.google.com/store/apps/details?id=com.steel89ita.themedebugger

- make sure your debugger options are ON and that you have the "Advanced reboot" option checked;

- In the phone's Settings/Buttons/Power menu: checked all the options as seen here:

- start that app play with it, and press the dropdown button (three dots icon on the top-right of activity bar) and select "Restart SystemUI" option (you'll have to grant a one time only or other SU right to the app for it to do the UI restart);

Now longpress your power button and check if all options are displayed - especially the Expanded desktop toggle?

Now select the Reboot option and what do you see? Is the options for bootloader, recovery etc in there or you just get "Your phone will reboot"?

To bring everything back (edited:) the way it should, I've found that the easiest way is to simply make sure your lookscreen is on, turn off the screen, switch on and slide or swipe/enter your code. Done!

So something behaves funny with SystemUI it seems.

And I've seen experienced all this before, like months ago and with a few different nightly builds. I've then blamed it on wrong downloads/bad luck/bad flashing/... but it was the same thing I believe now...

To be digged into more later....

Hopefully, this could bring some insight on something that's being going wrong with something as essential as the SystemUI app....
[Motorola Atrix HD] IronTechmonkey:
This bit is interesting but not entirely surprising. I've seen other cases where some form of interaction with the lock screen reset a problem condition which might otherwise be reset by force stop/restart system GUI (different ROM status bar clock disappearing). BTW I recognize that diamond pattern background from your theme which I've tested briefly.
[Motorola Atrix HD] marknoll:
Deleted
[Motorola Atrix HD] sobitthen:
Yes, nighties were working fine then one flash lost ability to MMS, came back in one of them, but have not been able to with any stability.

Just ordered new SIM since I had punched this one out myself and thought perhaps it was damaged, and it was using the old Straight Talk APN settings and now on the new settings, didn't make any difference.

On another forum where users were reporting same issues with nightlies, some had MMS that worked, others, the majority, did not, they were going to compile a list of which ones worked to determine why, and to use for their MMS needs.

Is there a stable KitKat version out here that MMS still works with? I would even try a 5.0 variant since bought a 12000mAH battery back-up. Got this gal who wants to send pics at odd hours and when I don't reply, she goes elsewhere so need this MMS.. :cool:
[Motorola Atrix HD] [] AL []:
I don't use MMS much I admit, but that said, I've never had a problem with them on CM11.

My only "complaint" about that has been that as opposed to how it was for me on CM7, to receive them, phone data connection has to be ON. So it works fine on any build, just leave your data always ON if you don't want to miss your pics. And needles to say whitelist the app in your firewall if you use one...
[Motorola Atrix HD] marknoll:
Anyone know what could cause the phone to reboot instead of shutting down? I go to shut it down and all it does is reboot..any ideas?

---------- Post added at 11:58 AM ---------- Previous post was at 11:19 AM ----------

I think its recovery related. I originally flashed cm 11 with cwm 6.0.4. Now with 6.0.5.1, this started happening. This happened on my inspire as well
[Motorola Atrix HD] mrroks:
the currently CM11 Nightlies are alot laggy and glitchii plus the battery backup is also not good ... im stick with MOKEE's History build (its the last smooth battery friendly but that doesnt means its bugfree) :(
[Motorola Atrix HD] Aingaran:
Can you give the link???
[Motorola Atrix HD] IronTechmonkey:
This is just not true in general. Recent msm8960 jbbl nightlies have been rock solid and smooth on AHD. Rarely any lag when there is not some app demanding high processor use (using ART).

Maybe CM11 on Dalvik just feels laggier than L on ART. To get a good comparison you'd have to compare KK on ART to Lollipop.
[Motorola Atrix HD] mrroks:
So ART working in CM11 ? i havent tried it yet.. , plus im generally saying im not comapring a rom with orher rom , and i had no apps installed for your info , at some places my mobile just gets hang/lag/glitch which is not presnt in other roms ...

---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------

MOKEE's moto_msm8960_jbbl
[Motorola Atrix HD] IronTechmonkey:
Yes, ART on CM11. It runs quite well, interface performance is smoother, battery a bit better and apps open faster. Downside is that installing apps, running TiBU or nandroids all take longer. Also, Google Sheets and Docs work very poorly on CM11 in ART which is odd because they should work on Lollipop in ART (I've not tested that).
[Motorola Atrix HD] marknoll:
These give a status seven error.
[Motorola Atrix HD] mrroks:
worked fine for me..

using Philz recovery :confused:
[Motorola Atrix HD] IronTechmonkey:
I know that since the multi ROM thread I created for mijuu, mokee and others has been closed it may be hard to share information about mokee but please don't hijack the CM thread to do so.

For that you could create and maintain a thread dedicated to Mokee. :)

---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------

My previous post was intended to be in response to this. Please check it out.
[Motorola Atrix HD] marknoll:
Sorry about that. I was just responding to the previous post regarding mokee..
[Motorola Atrix HD] mrroks:
and i was sharing which i was facing in CM11 , that was it .. :)
[Motorola Atrix HD] IronTechmonkey:
No worries, and I'm not trying to be a forum cop. Perhaps sour grapes about the closing of that other thread has me being overprotective of CM :)
[Motorola Atrix HD] sobitthen:
So you are on a vanilla CM11 such as cm-11-20150209-nightly-moto_msm8960_jbbl or something else?

I tried various GAPPS from full to micro and while it was fun to see all my old Messenger threads, none allowed me to MMS on Straight Talk...
[Motorola Atrix HD] [] AL []:
yes, I've tried other roms, but always came back to CM11 as you've stated. I think that I'm still on 20141223, but I doubt that newer nightly builds would be any different for MMS.

I don't know anything about Straight Talk and gapps package shouldn't matter since it has nothing to do with Mms.apk.

If there's anything, it could be on your phone service provider side maybe...
[Motorola Atrix HD] IronTechmonkey:
2/16/15 nightly looking OK in broad strokes.

cm-11-20150216-NIGHTLY-moto_msm8960_jbbl

pa_gapps-modular-nano-4.4.4-20150215-signed

AHD/MB886, Philz Touch 6.43.6/Clockworkmod v6.0.4.8

Phone, GPS, Sensors, BT, Wifi, LTE, Charge while powered off, Mic, External speaker, audio out all OK

Did not mess with Camera, Messaging, HDMI out.

Installation was hitchier than usual and I had to hard reboot once or twice which is exceedingly rare during these test builds but it settled down. Could have been due to new Gapps package speaking of which; Google apps behaving marginally better under ART but that might be due to the newer Gapps package used.

Also a general question

Is there a way to use an activity, shortcut, keycode, or command to invoke Clock sub functions: Stopwatch, Countdown, Clock, Alarms?

That fact that RetroClock widget takes you directly to Alarms implies that this should be doable but I’ve never found a way to do so for Countdown Timer and Stopwatch even with the hundreds of activities made available through Nova launcher.

---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------

Since the circumstances that cause that oddness with the Power/Reboot menus is so unique (and therefore easy for me to avoid) I did not test for it.

“Doc, it hurts when I do this”

“Then don’t do that!”

Easy for me to say, being a non-themer :).

---------- Post added at 05:24 PM ---------- Previous post was at 05:15 PM ----------

Echoing the experience of [] AL [] and others; I’ve found CM’s native Messaging app to be unreliable for sending MMS messages with picture attachments, particularly on a phone that I run with data off by default. I've found that 8SMS is more forgiving in that regard and when a message with a pictures attachment arrives when data is off 8SMS is more likely to let me turn on data and successfully download the attachment. Sounds like you use more MMS features than me but 8SMS is good for basic messaging (although seemingly at the end of it’s Development road).

For what it is worth, there was one Messaging related commit in the 2/16/15 nightly but it only has to do with marking one or all conversations as read. http://review.cyanogenmod.org/#/c/85320/.

Also, if you are on AT&T and use 4g/LTE by default, try setting the phone to use "WCDMA - only" at least for testing. AT&T had bad issues (at least in my area) with missed calls and missed messages which were worked around by forcing WCDMA (and are the reason I'm now on T-mobile).
[Motorola Atrix HD] [] AL []:
Yes it would be nice if Nova could be set to input new direct activities. Something like adding a code shortcut as oppose to just pre-configured activities or single apps. I've just recently installed a very simple app to take me directly to the vpn settings screen instead of going through: Settings/More...

/VPN so basically saving me one click. But it is more convenient for me to press one desktop icon then "connect" than the normal steps. But that being said, I'm afraid that it is not a direct CM 'issue' but rather a Nova launcher (or the default Trebuchet) one...

As per the disappearing power menu options, I'd say that for me, this is easily "fixable" (a simple toggle of the auto-lock power widget) but NOT avoidable. As mentioned before, the auto-lock state is being overrun by an unknown trigger and at random. So if one chose to turn off lockscreen lock, it might just automatically "re-lock" even if the power widget is still showing as not locked.

So really, there are two issues here: the explained power menu options disappearing on their own and the power widget not being displayed in the proper current state.

What I've suggested (the theme debugger app and anything theme related really) as nothing to do with the actual issues and was only meant as a quick bug triggering purpose.

We all use and set our phones differently, but I personally like being able to use the auto-lock power widget to turn lockscreen protection ON and OFF and wouldn't want to always have to run with or without it. But then again, now that I solely use the built-in vpn, I might have to live with the "bugs" or move to 'always lock after screen is turned off' mode since having lockscreen security set is a prerequisite for it. I guess that I should give it a try anyway to see if power menu options still disappear like so...
[Motorola Atrix HD] epinter:
CM12

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.zip
[Motorola Atrix HD] marknoll:
Cwm 6.0.5.1
[Motorola Atrix HD] IronTechmonkey:
Took this for a quick spin on AHD/MB886, Philz Touch 6.43.6/Clockworkmod v6.0.4.8, pa_gapps-modular-nano-5.0.1-20150215-signed.

Installed fine and runs quite smoothly although I did not test all components before walking it back. I forgot that updating the SuperSU binary is not always friendly on L and that it is better flashed from recovery.

One minor change from CM11/KK; No setting to toggle autosync other than power widget? The autosync setting that was once in Settings - Data Usage - Menu is gone, relocated, or I missed something.

One scare along the way; After wiping data in preparation for restoring KK, recovery was unable to mount SD external card upon which nandroids reside until a forced hardware reboot back into recovery. Not a ROM problem - this might have been due to the failed attempt to let SU update binary through recovery, but I was able to successfully retore nandroid of CM11 2/16/15 msm8960 jbbl nightly with no loss of data or problems with internal or external SDs.

Looks good so far except for the fact that Lollipop just does not look good IMO - Radio button screen tap functionality with slider animations on white backgrounds? Yuck.

Will try to test in more depth (and with flashable SuperSU file in place) later.

[EDIT - not sure if we should create a new thread for this or if the plan is just to roll the CM11 threads over to CM12 at some point... although they may overlap for a while.]
[Motorola Atrix HD] kabaldan:
Please don't use SuperSU, it does not help the CM12 debugging at all (and it's been already reported as a cause of battery drain). The CM built-in su can be easily enabled under Developer options>Root access, it works just fine.
[Motorola Atrix HD] IronTechmonkey:
Did not realize that, and will test CM12 without SuperSU. In CM11 under ART I had to use SuperSU to keep TiBU in line and just followed that path. Thanks for the information.
[Motorola Atrix HD] ssuds:
Awesome [MENTION=3721576]epinter[/MENTION]!

Is this built straight off the official CM source or does it have extra bits coming from other repos? If it is just straight from source I would guess this would be very close if not identical to the builds I've been putting out from the official source here which have been working fairly well for a few weeks now. I had talked with David a few weeks back about becoming the AHD maintainer since none of you had an MB886 but hadn't heard from him in a while, so I was just curious.
[Motorola Atrix HD] IronTechmonkey:
cm-12-20150217-NIGHTLY-mb886-epinter

pa_gapps-modular-nano-5.0.1-20150215-signed

OK dug a little deeper. Runs very smooth. TiBU OK with native permissions which do behave better than SuperSU. TiBU still gave it's customary warning about switching to SuperSU, but unlike in CM11 native SU was able to handle the TiBU restore.

Mobile data (only tested 3G) Wifi, GPS, phone, Speaker, Mic, OK.

Minor oddities:

- Double notifications for "background data disabled". Witnessed only during in my first test with SuperSU (in case that was a factor) and when using Tasker/Secure settings toggles to enable/disable background data.

- Notification volume slider not available until "Link ringtone & notifications" was toggled on then off again.

- Notification light and Battery light lack color configuration.

- Battery Light lacks other custom options (greyed out)

- Pound sign icon in upper right of notification area?

- Recents showing remnant services or cached items such as package manager. I actually like this as it informs what the system is doing beyond direct user interaction but it can be confusing in regards to clearing recents; Sometimes clearing Recents leaves things behind to be cleared again. This may have to do with the new functionality of recents persisting through reboots.

Lollipop gripes and CM feature desires.

- Status bar battery icon in text mode does not indicate charging while other status bar battery icons do.

- No more screen off animation setting (electron beam, fade or none)

- No setting to force expanded sound panel

- Navigation ring now forces center button to be something other than none. Boo-gle!

Did not have a chance to test some of the more potentially hardware exclusive things like camera and HDMI out (my holy grail), or battery consumption.
[Motorola Atrix HD] palmbeach05:
HDMI confirmed working
[Motorola Atrix HD] palmbeach05:
Official CM12 for our device is now up (posted at 10:21 AM CST, ROM uploaded 8:00 AM CST)
[Motorola Atrix HD] sobitthen:
I see no more CM11 for us...

Tried to check in on the nightlies and got this message:

err01: Device incorrect or not supported. Device may have been transitioned to CM12 nightlies.

Guess time to hunt to see which CM12 I need to use and hope I have correct recovery to use it...

Bought an LG G2 and moving my son to this Atrix HD and giving my elderly mother my son's Atrix2 that is stock in lieu of her getting a SOS necklace.

Which CM12 is fully stable and functional I hope to soon find out..
[Motorola Atrix HD] Justatechie:
I successfully flashed the official nightly 2/19 build to the atrix hd. Im using philz

Antutu Benchmark: 19,496

So far almost everything works,

Best surprise is that Moving apps into SD card work like a charm. (Great job Team)

Bugs: Screen Mirroring from Cast Screen/Chromecast does not work Ends up with an AV Source error -38

Basically the same bug originally, other logs before all say the same thing that ends up with that same error.

So a nice present with our first official nightly.
[Motorola Atrix HD] sobitthen:
What did you come from, not the CM11 nightly direct to this?

It must work with the JBBL?

And I would only assume you choose the method to flash a new ROM if coming from CM11, correct?

Just making sure they don't try to come from CM11 if not possible, I chose the option to install new ROM which is under factory reset, flashed ROM, flashed GAPPS, wiped cache, instructions from another thread, and up and running and MMS is working, sweet.. Had the CM account and all my Lollipop capable apps downloaded on their own.. everything is good so far, I like...
[Motorola Atrix HD] Justatechie:
With philz I use the option to wipe to "Clean flash to new ROM". I should have elaborated that.

I didn't need to worry about flashing it over from a kitkat rom because I use titanium back up to back up apps except for system apps.

I actually enjoy using this rom, its more stable than last time but I prefer mijuus 2/3 build. (I want his next update soon, after a fix from bluedroid has been applied recently)

Now I have been tempted to record both of screen mirroring actions through a log cat to document its behavior, but lately I dont have enough time to do so.
[Motorola Atrix HD] IronTechmonkey:
CM has rolled out MB886 JBBL Lollipop on the same page as the old device specific MB886 for CM11 here: http://download.cyanogenmod.org/?device=mb886 (That page has not been used since April of 2014 when the devices were merged into the MSM8960 shared ROM). Here is the changelog page for it: http://www.cmxlog.com/12/mb886/. The new device specific MB886 Lollipop is 2/19 and is probably similar to the 2/17 epinter one posted a few pages back which I tested and which ran quite smoothly.

Wahoo. Much thanks [MENTION=3721576]epinter[/MENTION] and [MENTION=2218140]kabaldan[/MENTION] et al.

The changelog page for CM11 msm8960 jbbl (http://www.cmxlog.com/11/moto_msm8960_jbbl/) does seem to be dead but nightlys up to 2/16 are still available http://download.cyanogenmod.org/?device=moto_msm8960_jbbl. This implies that there will not be a CM11 M13 and perhaps that there wont even be any more nightlies for CM11 MSM8960 JBBL.
[Motorola Atrix HD] marknoll:
I just went to cyanogen updates and saw this too...should we install this? Seems kind of weird to go from cm 11 to cm 12 with an update. What u think irontech?

---------- Post added at 12:01 PM ---------- Previous post was at 11:45 AM ----------

Aww. What the heck. .I did the reboot and install..bad choice. .tons of force closes and no responding. Messaging has stopped...launcher has stopped...ugh. Restore! Lol
[Motorola Atrix HD] palmbeach05:
Do a full wipe including system. Then flash CM12.

Also, can anyone confirm that the stock music player in CM12 has some fc's or freeze up the system?
[Motorola Atrix HD] marknoll:
Yea. That's how I wipe. Not really intrigued by cm 12 anyways. I guess I'm stuck on cm 11 2-18-15. Since there are no longer gonna be updates for cm 11
[Motorola Atrix HD] IronTechmonkey:
Assuming we're talking about the native CM updater on the phone; I've seen a commit or 2 that seems related to updating from CM11 to CM12 but…

… I clean flash even from one nightly to the next within the same version and would certainly do the same with this. If there ever is a time to clean flash (which for me is every time:)) it is between major versions.

The same version of Philz/CWM that I had been using worked fine for flashing this and restoring CM11 KK.

The jump from CM11 to CM12 is not surprising. There was a similar progression when the bootloader split occurred.

epinter came out of nowhere dropping a very stable pre-official jbbl build which was turned into official nightlies shortly thereafter. It seems like a similar progression is happening now.
[Motorola Atrix HD] marknoll:
No..not the native updater. I mean in about phone CyanogenMod updates. It went from 2-18 cm 11 to cm12

---------- Post added at 02:03 AM ---------- Previous post was at 02:01 AM ----------

---------- Post added at 02:04 AM ---------- Previous post was at 02:03 AM ----------
[Motorola Atrix HD] IronTechmonkey:
That is what I was referring to. "Native" in computer tech parlance equals "built in" as opposed to downloading from PC to external SD and flashing through recovery.

That is the behaviour we might expect to see if the updater takes us from CM11 to CM12 but... Still safer to clean flash unless specifically testing the updater.
[Motorola Atrix HD] marknoll:
Oh. I thought u meant native recovery. The option in dev ops about updating recovery with updates.
[Motorola Atrix HD] IronTechmonkey:
Good point. That would also be a feature native to CM. Still I'd clean flash when making the CM11 to CM12 jump.
[Motorola Atrix HD] marknoll:
I did. Not bad. Still don't like the idea that some modules won't work on xposed on lollipoo
[Motorola Atrix HD] IronTechmonkey:
LOL, I have no sympathy for Xposed. I'm not knocking what it can do but it seems as if Xposed and the Devs that built dependency on it into ROMS kept on going in the face of an increasing likelihood that Xposed was not going to keep up with ART for the jump to Lollipop.

---------- Post added at 12:18 AM ---------- Previous post was at 12:16 AM ----------

Will test for this in my next round in a day or so. Thanks for flagging it - I'd have otherwise not noticed since I go straight to Poweramp.
[Motorola Atrix HD] marknoll:
Hey guys. I need help. I was on cm 12 and browser force closed and froze my phone. I went to fastboot to try and access recovery. Not responding. Tried a hard reset. No luck. Now its stuck in a botloop. What do I do?

---------- Post added at 01:43 PM ---------- Previous post was at 01:34 PM ----------

Nvm. I accessed recovery with power vol up and down buttons. Whew. Close call. Cm 12 doesn't like my device. Ugh
[Motorola Atrix HD] palmbeach05:
Had the same issue on my Tab Pro (also running CM12 nightlies). I asked over there and I got a response. If anyone experiences FCs with the music player, go Settings>Apps>All and find Media Storage. Wipe that and reboot. Fixes the issues.
[Motorola Atrix HD] marknoll:
Are there known issues with browser? It fc a few times before it froze it
[Motorola Atrix HD] arnold80:
I've also random reboots with the CM12 build of 19th february. It happens in spotify, when i download and play songs at the same time or using the Browser. It seems that high usage of CPU and RAM could be responsible for that.

WLAN, Camera, Bluetooth, Screen, etc. everythings work without errors. If the random reboots were solved it would be a nice daily driver.
[Motorola Atrix HD] marknoll:
U got lucky. Mine stuck in a boot loop. I had to hard reset and access recovery.
[Motorola Atrix HD] IronTechmonkey:
Shame on me for not logging this but I had to abruptly abandon test so just FYI 2/21/15 nightly Messaging FC after changing to dark theme, and maybe other times too as I had immediately switched to dark theme. On a minor side note I'm still perplexed about what is meant by "dark theme" in messaging as nothing ever seemed to change with that setting even in CM11.
[Motorola Atrix HD] marknoll:
I found a way to access performance profiles. With tasker. Also, gesture typing doesn't work on keyboard(swype)