• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Motorola releases 4.4 for Verizon Moto X

Yes, Google changed that in KitKat. The explanation was two fold: first, people never understood the difference between a white and tinted icon. The second was that showing network activity in the status bar icon was using enough CPU that it was worth scrapping.

If you pull down the notification panel and press the settings icon in the upper right, I believe that the WiFi and mobile network icons will be tinted when you are connected to Google services and will also show network activity. (That's the case with KitKat on the Nexus 5; I don't have a Moto X with KitKat to see at the moment.)


I cant sort of understand the color thing, but I dont buy the CPU usage excuse.

I cant even imagine how they would have profiled it.
 
Upvote 0

Oh I believed you, just not Google about the amount of CPU / GPU used to render those little things being significant, relatively speaking.



Dan Sandler's quote actually alludes to what the real reasons are (IMO)

We could have more aggressively cached the bitmaps (rather than creating new BitmapDrawables from resource IDs every time, which was causing the relayout)
Avoiding re-layout is like "Android dev 101".

but that would still have left all the drawing—multiple times per second in some cases
It only needs to redraw as often as it polls (if even that). They could have set the polling interval to whatever they wanted. That thing already polls based on WiFi signal strength. And I dont think these arrows polled more than every half second or so.


Sounds like they noticed it was badly programmed and yanked the feature rather than fix it, which is disappointing.

Maybe it was, as he says "visual noise for nerds" but I think it was very helpful to know if something was working. It's not like it was giving us the CPU frequency or battery temp which are more esoteric. Knowing if data is transferring is generally pretty pertinent.

Not a huge deal at the end of the day, but it's a tiny step backwards towards the lowest common denominator of "just make it good enough for the average non-technical user".
 
Upvote 0
Personally I really miss it already. I work as a consultant and go back and forth from WiFi to Data all day long...I found it very handy to see the blue color on quick glance to know if I had data connectivity or not.

Not a huge deal in the long run, I'm sure, but so far I'd have to say it's the one giant change I've noticed in KitKat and I think it's a step backward.

Oh, that and I've always loved a weather/clock widget called Fancy Widgets that the devs have stopped updating a while ago. This update finally broke that widget for me as well.
 
  • Like
Reactions: Trooper
Upvote 0
Not a huge deal at the end of the day, but it's a tiny step backwards towards the lowest common denominator of "just make it good enough for the average non-technical user".
I'd have to agree, only I'd say it's one of those things that you came to appreciate, without thinking about it too much.

It makes me wonder how the OS handles live backgrounds and/or widgets, if this was taxing in some way.
 
  • Like
Reactions: alostpacket
Upvote 0
Great post; thanks.

Maybe it was, as he says "visual noise for nerds" but I think it was very helpful to know if something was working. It's not like it was giving us the CPU frequency or battery temp which are more esoteric. Knowing if data is transferring is generally pretty pertinent.

I actually like what iOS does - it just has a rotating circle dot icon when data is transferring. It doesn't matter which interface. I think I'd prefer at least something like that; I don't need to know which interface is transferring. I just want to know that something is happening.
 
  • Like
Reactions: alostpacket
Upvote 0
First VZW, now the others... After finding that the update was releasing for the other carriers, I went into settings, did the "check for updates", and was pleasantly surprised to see the attached. That was fast.
 

Attachments

  • Screenshot_2013-11-22-08-45-56.png
    Screenshot_2013-11-22-08-45-56.png
    115.9 KB · Views: 70
Upvote 0
After small little bugfix ota it's not a huge deal, but after large Android OS changing updates I would consider it almost necessary. There's a reason why people who flash custom roms always factory reset/wipe data whenever they change roms.

Agreed, which is why I mentioned it. Going to kitkat is a big deal. I did one on mine, however lock screen lag is still there. :(

Waiting on Motorola now.
 
Upvote 0
Just did, though I don't think that I should have to do that.

Thanks

Justin

It is amazing that they don't make it part of the update process with each major upgrade that they release (like GB to ICS, ICS to JB, or JB to KK). Without it people run into screwy problems days, weeks, or months after the update and then have to react in crisis mode.

For minor bug fixes in that are updating the same major version the FDR might not be needed. (On the Bionic it was always needed.)

My suggestion is to always plan out and execute the FDR on every major (letter change) upgrade.

... Thom
 
  • Like
Reactions: Trooper
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones