yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix HD] mm166:
After 7/1 update all I see is black screen. Only 'Bootloader unlocked' screen is visible. After that there's only black screen. I can hear that my phone is working - it's making sounds what it normally would but screen is black. I guess I need to make a clean flash.
[Motorola Atrix HD] idontkn1:
Had the same problem and clean flash didn't work. I had to flash 6/30. I read on another thread that CM11 unified builds starting with 7/1 had to have the KK bootloader. I imagine that is affecting us. Looks like we are stuck at 6/30 until we branch back off unifieds or we get official KK.

Go Moto Labs go.
[Motorola Atrix HD] mm166:
Thanks for info.

Just dirty flashed 6/30 nightly since I don't want to restore all my data and everything is working great again. Can't wait for official KK.
[Motorola Atrix HD] mega_man:
so is the development for Atrix HD is dead until we get kk bootloader ?
[Motorola Atrix HD] idontkn1:
At least for the unified ROMs yes unless people more knowledgeable than me branch back off and start building HD only builds. I think AOSB was never unified so if that the status quo remains we at least have that. Does anyone know of any other nonunified builds that are still active?
[Motorola Atrix HD] arrrghhh:
Indeed, apologies for not making the announcement here.

CM has gone to the new KK bootloader/modem/kernel setup, which means I will be unable to support Carbon for the AtrixHD anymore - I do not own an AtrixHD, so even when the official KK does drop for the Atrix, Carbon will not support it.

It was fun while it lasted, I'm sure an unofficial Carbon will appear.
[Motorola Atrix HD] Arjomer:
That really sucks! Carbon was probably my favourite ROM :(.

Anyways thanks for all your work!
[Motorola Atrix HD] quasihellfish:
Ugh. After months of waiting on Motorola and then researching which ROM would make the most sense, I finally pulled the trigger on 6/29 and now the project is effectively dead 2 days later. Oh well, like you said, fun while it lasted.

Thanks for all your work [MENTION=420530]arrrghhh[/MENTION].

p.s. If anyone has any recommended settings for kernel/governor/scheduler settings for "normal" use, it would be appreciated. I'm thinking that's somehow related to my excessive battery use when screen is on.
[Motorola Atrix HD] LPMatt:
After doing research on the governors and schedulers available to us (using aaaargh's kernel), I discovered that Smartassv2 and noop make a nice, balanced combo. By balanced, I mean a good compromise between performance and battery life. It's been working well for me for a while now. Try a few combos and see what works best for you (a lot of guys around here seem to like Wheatley for a governor).

Oh, and 6/30 is the latest nightly that can still be used with our bootloader.

Sent From Here
[Motorola Atrix HD] mega_man:
can somene give me an logical explantion that why even after we get offical kk update and bootloaders why carbon wont support us again ?
[Motorola Atrix HD] arrrghhh:
Not sure what wasn't clear in my post, but I'll re-state it.

I don't own an AtrixHD. My device (Photon Q) isn't getting the KK update.

CM has gone to this new paradigm, which I am unable to support, as my device is not getting the new bootloader/kernel/modem setup. So while before, I was able to support these devices because they were basically all the same... I am now not able to support all these devices because they are now basically not all the same.

So I would essentially be supporting a device blind - much more blind than before. I didn't mind supporting it semi-blind as the devices were basically all the same. Now they are not, and I cannot support a device which is drastically different from my own blindly. I can't test new things, patches are not able to be vetted by me, etc etc.

Someone else will step up and make an unofficial Carbon I'm sure.
[Motorola Atrix HD] St.Noigel:
What about this information?
[Motorola Atrix HD] arrrghhh:
Interesting, we'll see what happens.
[Motorola Atrix HD] mega_man:
is this the death of this forum for atrix hd
[Motorola Atrix HD] quasihellfish:
Not if this info is true.

That, or someone needs to send [MENTION=420530]arrrghhh[/MENTION] an Atrix HD they're not using. :angel:
[Motorola Atrix HD] fallendown:
If I get enough money to make use of my OnePlus One invite, I'll gladly send [MENTION=420530]arrrghhh[/MENTION]h my Atrix HD :)
[Motorola Atrix HD] IronTechmonkey:
AOSB is nice on MB886 though AOSB 1.36 has wifi problems and all recent versions have spell check bug. Using CM M8 now but came here to check out Carbon nightly 6/30/14 to see what that has that CM doesn't.
[Motorola Atrix HD] IronTechmonkey:
Ha. Have we been window shopping the same ROMs? :)

I can see why Carbon is your favorite. I'm now now running Carbon moto_msm8960 6/30/14 nightly on MB886 with ART. It has great customization options, good performance, and in particular it does not contain a few glitches I've seen in other "combo" ROMs. During configuration and testing (after having been switched to ART) it did revert back to Dalvik during a manually induced reboot or while being charged while powered off, but after being set back to ART that has not happened again.

The only things I've seen in other ROMs that are "missing" in Carbon (perhaps for good reason) are: OTG mode (rear camera as live wallpaper), App Bar, and Split Window. Being a utilitarian minimalist I don't miss those things except for Split Window which Carbon makes up for with a stable implementation of Floating mode. Carbon is far more stable and less glitchy than other ROMs containing similar features and customization options.

The 6/30 nightly seems to fall into a magic window for CM derivatives (6/29/14 - 6/30/14 nightlies and CM M8); before the switch to KK bootloader but after the fix to the GFS wakelock issue.

In spite of the boot-loader induced pause in development. I'm quite happy with Carbon 6/30/14... as long as no change to something in the Googleverse triggers another problem (as was the case with GFS).

Thanks to the Carbon Devs!
[Motorola Atrix HD] bylithium:
Carbon was once the best ROM I've used, now I'm running sokp, I love it! That'd be awesome if carbon was for the jb BL after 7/1 ?
[Motorola Atrix HD] Arjomer:
Ikr! I might go back to that nightly because on the latest nightly of CM (with JB bootloaders) has some problems and I can't make ART work:(

It really sucks that we can't get latest nighties because of our JB bootloader. I guess if we don't get the KK update soon I might switch to a LG or HTC.
[Motorola Atrix HD] IronTechmonkey:
That's odd. I was running CM nightly 6/30/14 as well as M8 on ART with no problem. edit>> Different phone. Moto Atrix HD MB886 <<edit
[Motorola Atrix HD] quasihellfish:
After reading your post, I went and checked (because I'm on the exact same ROM/nightly) and sure enough, ART had reverted back to Dalvik. That's annoying. Setting it back to ART now to see what happens. "Android is upgrading..." :mad::mad:

Otherwise, agree with everything you said. I'm very happy with this ROM, even if it never gets updated, because everything seems to work just fine.
[Motorola Atrix HD] IronTechmonkey:
Eliminating potential causes unlikely to be common between us (Quick Boot app and TBU restore management) I wonder if Carbon's Persistence setting and Carbon Delta are committed to Dalvik and if playing with those settings had something to do with this. I've gotten through a few days without being spontaneously switched back to Dalvik but to be sure; I de-selected all networks in the Carbon delta (update) settings and then froze Carbon Delta and Carbon Stats with TBU.

Unfortunately I'm noticing high processor usage 20%-30% of System UI regardless of any of the aforementioned Carbon settings and freezes. This processor hog occurs at various points and is temporarily rectified by reboot. I don't know what is the cause although I suspect keyboard.

I notice higher than expected battery usage for the keyboard which has also crashed on a few occasions. In addition the keyboard will crash any time you try to invoke it after setting it’s Color scheme from white to blue. It would be a shame if this keyboard were a problem because I LOVE those left/right cursor controls. Ironically I'll be using Hacker's Keyboard (which I originally installed just for those cursor controls) to troubleshoot this. If I cant stop that processor drain I might be back on CM soon. Fingers crossed, as I'm digging Carbon.
[Motorola Atrix HD] arrrghhh:
Someone said the battery issues which show up as Keyguard is related to the 'seconds in statusbar' - even if it's disabled.

The option should probably just be scrapped entirely, as it seems to also break when am/pm is in use. I don't use the feature myself, and if it's causing issues it should be removed.

Of course, since there are no more official builds.... it doesn't really help you much :(
[Motorola Atrix HD] IronTechmonkey:
Thanks for that tip. I did have AM/PM and center clock enabled but disabling them did not fix, not that it would considering your description. For what it's worth; with or without the status clock or AM/PM enabled, here is how I can replicate the processor/battery drain and address it without a reboot.

To Replicate

- Drag the Notification Shade or Quick Settings Panel all the way down.

- Leave it down for a second or 2.

- Close Notification shade using Back Button (rather than swipe up - makes all the difference)

= System UI processor usage steady at about 30%

To Fix

- Drag the Notification Shade or Quick Settings Panel all the way down.

- Leave it down for a second or 2.

- Drag back up (rather than use Back button)

= System UI processor usage drops down to a reasonable 5%-10%

To Avoid

- Always drag quick settings panel and notification shade up rather than use back button.

Thanks again for the tip!

I'd otherwise never have followed this path to a workaround - albeit a workaround that requires a degree of OCD, but I got that covered:)
[Motorola Atrix HD] quasihellfish:
I un-selected all the networks for Carbon Delta back at the beginning of the month, as soon as I heard about the whole JB/KT bootloader issue with the unified ROMs. Honestly, no Atrix HD user should be trying to use Carbon Delta enabled at this point. No?

Also, while I have no empirical evidence of it, I think my Dalvik issue might have been a result of me playing around trying to get screen mirroring working with my Chromecast. There were some unsupported methods by a user elsewhere on XDA, and I tried it out. Phone acted very wonky after that; forced reboot, bad battery drains for a whole day, etc. Shortly after than incident is when I checked and found I was back on Dalvik. But to be fair, I hadn't looked at it for several days before that, so I have no way to be sure.

Regardless, I'll be watching a little closer now.
[Motorola Atrix HD] IronTechmonkey:
I was about to write an overlong reply that leaned towards the update system as cause while admitting that I also had no empirical evidence when...

I found that I can replicate this problem absolutely by charging the phone when powered off. When I disconnect the charger and power up phone it reverts to Dalvik on boot. Converting back to ART now. Icon rolling rolling rolling. Optimizing app X of Y.

Did you charge phone while powered off?
[Motorola Atrix HD] quasihellfish:
Yup, that must have been it. My battery ran all the way down last night to the point of the phone turning itself off. So I just plugged it in. When I powered it on this morning (while still plugged in) it started "Upgrading..." the apps. Checked, and I'm back on Dalvik.

Well I guess I won't be doing that again.

Good work.
[Motorola Atrix HD] IronTechmonkey:
LOL

Patient: "Doc, it hurts when I do this"

Doc: "Then don't do that!"

I wont be doing it again either but for other reasons. I cant keep up with the notification shade/back button induced processor jams in Carbon so I'm going back to CM M8. Will be back on Carbon in a nanosecond if an official MB886 AT&T KK OTA is actually released.

<edit>

Well, well, well. I figured I'd test in CM M8 and the same thing happens.

I certainly hope this is just a thing in custom ROMS and wont occur if and when an official AT&T, KK, MB886 OTA is released.

<edit>
[Motorola Atrix HD] arrrghhh:
On that note, bi-weekly builds of moto_msm8960_jbbl will start as of tonight.

You must be running the old 4.1.2 JB bootloader setup - this is basically for folks who can't upgrade to the new KK bootloader from moto for whatever reason.
[Motorola Atrix HD] IronTechmonkey:
Wahoo! Looking forward to getting back to some playtime testing in Carbon.
[Motorola Atrix HD] mauchito:
Hell yeah!! CarbonRom again!! :highfive:
[Motorola Atrix HD] IronTechmonkey:
Briefly tested CARBON-KK-NIGHTLY-20140802-0655-moto_msm8960 (JB bootloader)

Still experiencing this

- Drag the Notification Shade or Quick Settings Panel all the way down.

- Leave it down for a second or 2.

- Close Notification shade using Back Button (rather than swipe up - makes all the difference)

= System UI processor usage steady at about 30%

and this time around it is not quelled by swiping up.
[Motorola Atrix HD] arrrghhh:
I must've missed this "bug" last time around...

So a few questions - if you leave the notification bar down for less than a second (IE just immediately hit the 'back' button) does it happen? If you do NOT use the back button (IE just swipe up to get shade to disappear) does it happen?

I just tried this myself on my Photon Q, looking at 'top' in adb I don't see any high processor utilization. Tried to recreate it a few times, left the shade open for 10 sec or so on the last attempt, always using the 'back' button to clear the shade...

Is this issue specific to Carbon, or specific to the Atrix HD? In other words, does this happen on CM?

Of course I gotta ask - does it happen when you clean flash and don't install ANYTHING? As in, don't install gapps or any apps, just boot Android after clean flashing (also wipe system and reflash the ROM) and see if you can recreate.
[Motorola Atrix HD] IronTechmonkey:
No gripes. It wasn't like I submitted a proper report or anything. :)

It does not seem to matter how long the notification bar is down. Also, this time around using the back button instead of swiping shade up does not settle processor back down as it did the last time.

Have not seen this in any of the CM builds I've tried including the recent cm-11-20140802-NIGHTLY-moto_msm8960_jbbl. Although I did see flakiness around the StatusBar and NavBar in one of the first CM epinter 8960 jbbl nightlies to include center clock and left/right Navbar typing cursor arrow; that incident did not include high processor usage. Did not see it in a recent GZR/Validus 6 build tweaked for jbbl. Have seen this only in the 2 Carbon builds I've tested (CARBON-KK-NIGHTLY-20140630-1254-moto_msm8960 and CARBON-KK-NIGHTLY-20140802-0655-moto_msm8960).

Could be MB886 specific. I have noticed what seems to be bunching by phone models in some problem report categories, particularly wifi and GPS glitches but don't see how that would be related.

I hang my head in shame. This time I rushed right in, installed all my stuff and put settings in place before testing.

- I do always clean flash - using Philz Touch 6.19.3/Clockworkmod v6.0.4.7

- Use Watchdog to check the processor usage. I've not yet learned how to check processor usage through ADB but think it might be about time so I can test earlier in the build process.

- Using Gapps PC Micro 7/25/14

- Have never tested (this time or last time) without Gapps installed.

- Using Nova Launcher

- Using ART

Also for what it worth diagnostically, In both of the Carbon builds I’ve used (CARBON-KK-NIGHTLY-20140630-1254-moto_msm8960 and CARBON-KK-NIGHTLY-20140802-0655-moto_msm8960) I noticed that even when this condition is not in evidence, and when the phone is idle with screen on, SystemUI uses 3%-5% processor whereas in CM it uses less than 1%.

Will test again, getting rid of as many of the aforementioned variables as I can.

Thanks!
[Motorola Atrix HD] IronTechmonkey:
I am a bit lost about monitoring processor on clean/lean build via ADB but did gather helpful info in Settings – Performance from a clean build.

Clean install of only CARBON-KK-NIGHTLY-20140802-0655-moto_msm8960. No Gapps.

At idle with screen on; Core0 is at 384 MHz and Core1 is off line; as expected.

After swiping notification bar down then using Back button; Core0 is at 1134 MHz with occasional dips and Core1 stays offline. It does not seem to matter how long the notification bar is down before the back button is pressed.

Dragging notification bar down and dragging it back up settles the processor, whether dragged all the way down and left to sit for several seconds, or dragged part way down and immediately back up. Power button off and back on does not settle it down.

Apart from this glitch but likely related; In the default settings (CPU governor = interactive) Core0 never goes above 1134 MHz, as if that is Max even though Max speed is set at the expected 1512 MHz for this phone.

When I change CPU governor from interactive to ondemand the increased processor usage also occurs but along different processor speed stops. In this case Core0 runs through what seem to be more reasonable CPU speed steps ranging up to the expected max of 1512 MHz.

When I changed the CPU governor to powersave I get rapidly repeated toast notifications “Super user granted to input devices” each time I interact with the screen.

In all of these settings combinations notification bar down + back button causes the increased processor usage.

For what it might be worth by way of comparison, the GZR/Validus build I previously mentioned allowed one of the cores to overclock without regard to any cap, and processor monitoring utilities reported a 1801 MHz processor. Kinks in getting kernels to behave in jbbl or visa versa for this phone?
[Motorola Atrix HD] TecknoFreak:
Shoot.... I saw their git and yeah bro you right. Is I have to be honest. Im not a cm lover eventhough I thank them for what they did.

If is not aosp is not for me. Is just I love the feel that to me is smoother the cm11. But again is just me. Ever since skeevy got us the full_aosp from dhacker all my likes changed a mile. Lol
[Motorola Atrix HD] sickkside13:
Well so far so good I love how slowly but surely we are getting all this Roms on the Atrix HD
[Motorola Atrix HD] KrisM22:
Huge thanks for the tip on F-Droid and adaway - exactly what I wanted!
[Motorola Atrix HD] boredperson:
anyone else experiencing issues with the download section of the carbon site? There's no sidebar filled with devices for me to select...
[Motorola Atrix HD] KrisM22:
Yeah, it's been dysfunctional for a few hours. I assume they're updating it. -

EDIT: hey! we're getting a shiny new server!!!

read this http://carbon-rom.com/server-stuff/ from carbon github page.

EDIT2: they seem to be moving along very quickly! :D

EDIT3: it's done. at least for Atrix HD
[Motorola Atrix HD] Neighbor808:
Its very great to see my favorite ROM coming to KitKat on our phones. Will flash very soon. Excited!
[Motorola Atrix HD] Silentwidow:
Anyone got a mirror of the latest version ? It says they can be down for hours, or way longer lol
[Motorola Atrix HD] KrisM22:
sorry, it kicked out while I was away. Guess I can't do it.
[Motorola Atrix HD] antmiu2:
im I the only one that cant find the ROM?
[Motorola Atrix HD] KrisM22:
read the last 5 posts. They're fixing it.

nite.
[Motorola Atrix HD] arrrghhh:
lol...

Jeez guys.

http://oudhitsquad.com/arrrghhh/roms/carbon_kk/CARBON-KK-NIGHTLY-20140205-0852-mb886.zip
[Motorola Atrix HD] clockcycle:
Ill send you thanks for them, it seems they were jonsing as if its a drug..
[Motorola Atrix HD] jblaylock:
Best KK Rom I've used so far. I haven't tried PA, and maybe won't now.
[Motorola Atrix HD] mofotrucker:
well im having issue with my atrix hd... a day or so ago i flashed carbons nightly rom and it was sweet... till i flashed arrrghhh's kernel... my wifi quit.. so flahed back to stock and no dice. still don't work flashed a few other roms and no go... wifi wont turn on... did i break something on this fone, has anyone else had issues like mine or im i the only one having these issues... any help would me appreciated. thanks
[Motorola Atrix HD] mauchito:
Maybe you should check this thread: http://xdaforums.com/showthread.php?t=2469104
[Motorola Atrix HD] mofotrucker:
gona give a shot... thanks
[Motorola Atrix HD] mofotrucker:
IT WORKED.... thanks alot mauchito....
[Motorola Atrix HD] clockcycle:
20140205 seemed to be giving me data issues. Went back to a 20140131 backup and it works fine.
[Motorola Atrix HD] KrisM22:
Curious - what kind of data issues. I've noticed nothing, but I run with android firewall, system tuner pro, my data manager, betterbatterystats. Opera Mini is the only browser I use(vastly lower data usage). I freeze google play store when I'm not using it. I'm very attentive to data as I'm limited to 200MB/mo. I generally use avg 40MB/mo or less. I do all my heavy stuff on wifi(setting up ROM). This ROM rocks! :cool:
[Motorola Atrix HD] clockcycle:
I have LTE, on 20140131 I get normal speed just about everywhere. Doing the same with 20140205, it switches E 3G H+ LTE "trying" to load any pages. Play Store / browser gets "retry" no connection most of the time. Gonna back track backups between and try clean wipe installs.
[Motorola Atrix HD] arrrghhh:
Depends on what kernel they are using. Carbon just uses the CM kernel.

As for the sysUI issues, there's a lot of messiness in frameworks, so it's entirely possible - although I can't say I can recreate it exactly, there have been sysUI complaints for battery drain in the past.

As for your processor stats, you should be able to see how much time is spent in each state - go to 'performance' and either hit menu and 'switch to tabbed' or 'toggle drawer' - then go to 'time in state'. While 1134 is used on mine, 1512 is as well.

Anything above 1512 indicates a different kernel from the CM kernel.

Edit - lol, just read the thread... that ROM uses my kernel by default it seems.
[Motorola Atrix HD] IronTechmonkey:
Forehead slap, forgot about Time in State. With interactive governor on, pushing minimum CPU up to 1512MHz does force that step. Otherwise 1512Mhz is used very rarely after start-up, That's different than I remember for that governor in other builds but might not be a bad thing if it saves power. Although the maximum seems odd; minimum and deep sleep seem normal. I think that once the high processor usage state become set by circumstances it may abate when screen is off but persists when screen comes back on until swipe down/up.

Ahhhhh, such is the circle of life... or the kernel of life, as the case may be. Thanks!

<edit>Restored my CM installation and found that it too focuses on 1134MHz in the same way... which makes sense if they are using the same kernel. Having been on the ondemand governor for so long in a previous ROM I got turned around. Thanks again. <edit>
[Motorola Atrix HD] Jce9182:
So I'm on carbon ROMs website and I see a section labeled

moto_msm8960_jbbl. Is that short for jelly bean boot loader??? Last I remember is it went KK on 6-30
[Motorola Atrix HD] arrrghhh:
Read back a few posts.

http://xdaforums.com/showpost.php?p=54558047&postcount=574
[Motorola Atrix HD] Jce9182:
Thank you sir. My fault for not searching. Shame delta won't update this. I hate restoring apps. Takes forever. Might just make a updater zip of all my apps which in sure will also take forever.
[Motorola Atrix HD] Byakko Custom:
Why not dirty flash for now and when larger updates come, you can clean flash those.

53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
[Motorola Atrix HD] Jce9182:
I thought about that but i think its time for a fresh install.

Edit: definitly glad I did a clean flash. Didn't realize the problems I was having were as bad as they were. Up and running smooth again.