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

Android Update 4.4.2...FAIL

zonxwedop

Lurker
Seriously Android?!?! I have the Droid RAZR Maxx HD (which really has nothing to do with the operating system, I was just informed that I should post what device I have in order to post this on the correct forum). The new "upgrade" SUCKS! Worst OS so far by far. I have a great idea, lets take the things that make sense to the average practical user...swype, low battery usage, keyboard arrow keys, being able to do a newline in the text message instead of a built in smiley face key, set the sound easily and it STAY at that LOUD sound, ability to turn off sound without having to type in the password to unlock the phone, ability to turn off alarm clock with a button press and not the screen swipe, THE OLD AND PERFECT GOOGLE EFFING MAPS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! THE MAPS THAT WORKED LIKE A CHARM AND HAD PERFECT NAVIGATION!!!!!!!!!!!!!!! THE MAPS THAT ACTUALLY WORKED AND DIDNT TAKE FOREVER!!!!!!!!!...and get rid of them! And for what?!?! So you can see the album cover of the band that is currently playing on your phone? Not saying that isnt a cool or good idea, just saying there are WAY more important and USEFUL things to do with an update than that. Why cant an update be an update, that is, leave the things the way they are and add to it? What ever happened to the "If it aint broke, DONT FIX IT" mentality? I understand updates are important. You dont want to just sit there with your product and do nothing. But that doesnt mean you need to get rid of key functionality and limit the phone's ability to be elite!

This new update makes me either want to punch babies or go to IOS!!! And I HATE Apple with a passion. Here is some code to demonstrate what I am talking about. Please paste this into a c++ Main.cpp and compile and run with the argument of "TRUE" if you received the new update and "FALSE" if you did not receive the new update to see what im talking about:

Code:
#include <iostream>
#include <string.h>
#include <string>

bool receivedNewUpdate = false;
const std::string USAGE_MESSAGE = "USAGE: <program> TRUE/FALSE";

bool gotPwnedByAndroid() {
   
   if(receivedNewUpdate) {
      return true;
   }

   return false;
}

int main(int argumentCount, char* arguments[]) {

   if(argumentCount != 1) {
      std::cout << USAGE_MESSAGE << std::endl;
      return 0;
   }

   if(strcmp(arguments[1], "TRUE") == 0) {
      receivedNewUpdate = true;
   }
   else if(strcmp(arguments[1], "FALSE") == 0) {
      receivedNewUpdate = false;
   }
   else {
      std::cout << USAGE_MESSAGE << std::endl;
      return 0;
   }

   if(gotPwnedByAndroid()) {
      std::cout << "ANDROID JUST PWNED YOU!!! Now you must decide whether or not you will switch to an iPhone (God forbid) or punch babies because of the suckyness of this update!!!" << std::endl;
   }
   else {
      std::cout << "Don't worry, you will be much happier without this ******** update. It sucks. It is terrible. You will not hate things as much because you will not have to get frustrated from your phone being a POS" << std::endl;
   }

   return 0;
}
 
Welcome to Android Forums.

I moved this thread to the forum dedicated to discussing your phone. This is where you will find the most people using your phone and sharing your experiences.

... Thom
 
I completely agree and furthermore add I don't like it. I don't like it at all. After doing a factory data reset I still only get about 1 day out of my Droid RAZR MAXX HD... Lititerally half of what I was getting before. I use my phone constantly for personal use and for work and need a phone that lasts a long time. Especially when I travel to China 6 or 7 times per year, after 36 to 40 hours of travel and phone calls and listening to music I would like my phone to still be kicking like it was before the update, but now I have to stand there like a goober with an iphone and charge it when I get off the plane if I need to call my ride. Perhaps I will go buy an 8000mAh portable battery... yes, for those of you who know about portable batteries, that's what it takes to charge these phones, you can charge an iphone 3 times off of that, or 1.5 of the newest ipads, pretty insane. I would be completely fine with that if it wasn't for the fact that it dies in less than 24 hours, I typically have about 20% or less when I go to bed, forcing me to charge it every night now. The maps update is the most infuriating though. Why the hell I can't just press the navigate button and only say my destination once and have it go to it anymore bugs the crap out of me. Before this update I would press the voice command button on the screen with less than a mile before what I thought might be my turn if I was going somewhere new, and it would quickly route me and let me know if I was going the right way. But now, if I am less than 5 miles away I pretty much will pull over to make sure I don't miss my turn if I am unsure.
 
I do know, with 4.4.3, there were a lot of bug fixes. One in particular was battery usage being addressed from user complaints. My N10 had 4.4.2 and just upgraded to 4.4.3 and I will say the battery usage is better but again it is not a phone.
 
KitKat is actually a LOT better performance-wise if you can get it working the way you'd like. Most people have gotten the same, if not better, battery life results, but it usually requires an FDR, which you've already done.

Check your battery stats. You might have an app that's eating up your battery. Mine was due to WiFi having issues, which after an FDR, fixed it.

Also, some other phones (not specifically the XT926) have had an issue with the camera draining the battery. I haven't seen that with my phone, but that's something else that's supposed to be fixed.

Also, using the SmartActions app to set various settings based on where you are or if you are charging or not helps a lot. I have mine set up as follows:

  1. Brightness setting set to automatic by default. Gives the best display based on your lighting conditions (darker it is, the lower the brightness).
  2. Default for WiFi is off when I'm not at home or work.
  3. GPS is always on (which DOES drain battery, but not too much). This is so it can determine if I'm at home or work.
  4. Home setting - When it senses I'm at home, it turns on Wifi.
  5. Work setting - When it senses I'm at work, it turns on Wifi.
  6. Not charging - sets screen display timeout to 15 seconds and sets the screen to Smart setting which uses the least amount of battery.
  7. Charging - Sets screen setting to automatic brightness.
With these settings, I definitely get about 36 hours or more with moderate use of my phone. Mind you, my phone is a RAZR HD, not a MAXX HD. If I didn't use it at all, I'm sure I could get over 48 hours, but I have to use my phone.

But, one thing you cannot complain about with this update is that you can now unlock your bootloader if you haven't done so before.

Yes, you heard me correctly. For some reason or another, when Motorola built this latest code base, they re-introduced the exploit that allowed unlocking of the bootloader, which was lost once the 9.18 OTA came out last year.

So, go here -> [ROOT/UNLOCK] RAZR HD/M build 183 kitkat Towel Root - VZW Droid Razr/Razr Maxx HD Development [XT926] - DroidRzr.com

Follow the directions and unlock your bootloader if you haven't done so yet. You won't be sorry and you'll NEVER lose root again. Plus, it does give you a path to downgrade back to JB, but you have to follow directions carefully due to some of the trusted zone partitions being updated which cannot be downgraded even with an unlocked phone without a signed image from Motorola. Once you've unlocked your phone, use SamuriHL's House of Moto tool to downgrade back to JB. Go here for instructions -> House of Moto [2.3] - SamuriHL's House Of Moto - DroidRzr.com

Remember, you must have upgraded your phone to Kit Kat in order to unlock the bootloader.

Do this NOW because there is another OTA coming that is sure to fix the latest root exploit (Towelroot) and probably will fix the unlocking exploit. Once that happens, there is NO way to go back to reintroduce the exploit without Motorola possibly releasing another OTA that re-introduces it. But, I would say this next OTA (after the Kit Kat OTA) will be the final one, so unlock now or forever hold your peace and don't whine that you missed the boat. The Moto Gods have smilled down upon you and given you a second chance on unlocking your phone, so take it now. :)
 
What are the advantages and disadvantages of unlocking the bootloader? I've Googled it, and I'm still not sure I understand what I'm doing. Does this enable installing customs ROM's, and does it void the warranty on the Razr Maxx?
 
Yes and Yes. It allows custom roms and yes it voids the warranty. There are also apps that require root, or super user, access as well.
 
I think I'll leave well enough alone. With my luck I'd just brick the phone.

A quick question first:

Do you root your phone?

If so, you've already voided your warranty.

Also, many people have turned in their unlocked phones and got a replacement without any charge, so don't avoid unlocking because of that.

Also, you cannot brick your phone attempting to unlock this phone with the Motopocalypse tool. It either will work or it won't.

But, yes, once you are unlocked, you can run custom ROMS using TWRP or CWM custom recoveries AND they can be different kernels. People were running CWM11 (kit kat) on this phone before the official KK OTA came out.

Currently, there aren't any custom ROMs running on the KK OTA, but the devs are hard at work on them (CWM is once that sorta works, but has some issues but the devs are working on it).

Also, once unlocked, you NEVER have to wait for a root exploit again. You can just sideload it using a custom recovery like TWRP or CWM. And believe me, another OTA is coming to patch some issues and you can bet your bottom dollar that Moto will patch the Towelroot exploit AND patch the bootloader unlock exploit. Not sure how they made the mistake of patching that back in, but now is the time to take advantage of it.

Besides, this phone is 2 years old now. Having the bootloader unlocked has extended the life of the phone so that eventually, you can get different version of android on it as the devs keep building off of the newer AOSP source code trees.

Again, you can't brick your phone attempting to unlock it. The exploit either works (based on the version you have on your phone) or it doesn't.
 
Thanks for the information, bolski.

No problem.

Many of us are on a mission to get everyone to unlock their bootloaders. Moto gave everyone a gift when they released the exploit they patched back in version 9.18 of this phone which removed said exploit.

It's a gift from the Moto gods that everyone needs to take advantage of right now.
 
I'm about to sell my RMHD due to a move to ATT. No sim in the phone but can connect via wifi. Can it do whatever is needed to unlock bootloader?
 
So is there any chance of getting the Nav back or the ability to write to the SD card? I have to admit that I would have never done this update had I known about this. I updated google maps about 5 or 6 months ago when I was still on the old OS and lost nav. I started searching and found where I could just uninstall the updates to google maps, and it would work again. I tried that now but it looks like the OS update completely got rid of it. :(
 
ever since I did this update my phone has lost the ability to read my incoming texts when it is in my nav dock. the bluetooth connection is spotty as well
Before the KK update if I had an incoming text while I was driving (phone in nav dock) it would announce incoming text from____ say listen to hear the message. It no longer does this..so much for hands free....

also the BT connection has reverted back to dropping out/skipping while Im listening to music in the car.....
 
I do not use BT for music but it is no issue for voice etc. in my car. I am sure this though is much lower bandwidth over the BT than music.

In NJ while in a vehicle ALL texting is banned. The law states all texting devices are not permitted to be used and that would mean hands free or otherwise. Texting includes both replying or sending a message or reviewing an incoming message. Hands free voice communication is fine (as in a phone call). I've included a link below for NJ but each state may be different.

For myself I would never use text in a car or on a bike, no matter what the device can or can not do. The consequences are not worth it.

New Jersey Text Messaging and Cell Phone Laws | DrivingLaws.org
 
It requires a Root under kitkat, which can be done here at your own risks...

[ROOT/UNLOCK] 4.4.2 182/183 RAZR HD/M *ONLY* - VZW Droid Razr/Razr Maxx HD Development [XT926] - DroidRzr.com

Then you can modify your settings for the wifi tethering under here...

Wifi tether solution for rooted XT926 on KitKat - Page 2 - XDA Forum

Now it's on to finding another ROM.

Don't be discouraged about the rooting and unlocking. Just try downloading and installing the software they tell you to, you are completely safe until you connect your phone via USB to the PC and then hit enter under the cmd prompt window.

If you made it THAT far, you should be fine. I didn't need the stock USB cable like he recommended.
 
It requires a Root under kitkat, which can be done here at your own risks...

[ROOT/UNLOCK] 4.4.2 182/183 RAZR HD/M *ONLY* - VZW Droid Razr/Razr Maxx HD Development [XT926] - DroidRzr.com

Then you can modify your settings for the wifi tethering under here...

Wifi tether solution for rooted XT926 on KitKat - Page 2 - XDA Forum

Now it's on to finding another ROM.

Don't be discouraged about the rooting and unlocking. Just try downloading and installing the software they tell you to, you are completely safe until you connect your phone via USB to the PC and then hit enter under the cmd prompt window.

If you made it THAT far, you should be fine. I didn't need the stock USB cable like he recommended.

Ok this is a fix for the wifi hot spot not the BT correct?
 
Ok this is a fix for the wifi hot spot not the BT correct?


True. The second link is a wifi tether fix on a rooted Verizon Razr Maxx (and maybe a couple other Razrs) for its lost FoxFi ability to tether. Although the first link will not only root the phone, but also unlock it.

I can only vouch both links working on a Verizon Razr Maxx HD XT926.
 
So is there any chance of getting the Nav back or the ability to write to the SD card? I have to admit that I would have never done this update had I known about this. I updated google maps about 5 or 6 months ago when I was still on the old OS and lost nav. I started searching and found where I could just uninstall the updates to google maps, and it would work again. I tried that now but it looks like the OS update completely got rid of it. :(

Yes simple fix when rooted. Install Xposed framework and the SD fix.

UNLOCK YOUR BOOTLOADER EVERYONE! What warranty? The phone is over one year old. When Moto updates stop coming you will be SOL if the bootloader is still locked. No Android L for you then. Phone insurance doesn't care if you are rooted or have a developer phone. Unlocked bootloader is a dev phone.
 
Yes simple fix when rooted. Install Xposed framework and the SD fix.

UNLOCK YOUR BOOTLOADER EVERYONE! What warranty? The phone is over one year old. When Moto updates stop coming you will be SOL if the bootloader is still locked. No Android L for you then. Phone insurance doesn't care if you are rooted or have a developer phone. Unlocked bootloader is a dev phone.

Mine will not be over one year till 11/2014.
 
Mine will not be over one year till 11/2014.

Have you rooted? If so, you already voided your warranty and they tell if it was rooted or not by booting the phone into normal recovery. The qe code will tell them if it's ever been rooted. 0/0 means it's never been rooted. 0/1 means it's not currently rooted, but it has been before.

So, if you've rooted, you've voided your warranty.

But, many have turned their unlocked/rooted phones in for warranty replacements and they received a new phone free of charge, covered under warranty.

Since this phone is 2 years old, don't expect much support anyways, so you might as well unlock it now, especially if it's less than a year old for you. That will ensure it can run the latest kernels regardless of what the official stock kernel is.
 
Have you rooted? If so, you already voided your warranty and they tell if it was rooted or not by booting the phone into normal recovery. The qe code will tell them if it's ever been rooted. 0/0 means it's never been rooted. 0/1 means it's not currently rooted, but it has been before.

So, if you've rooted, you've voided your warranty.

But, many have turned their unlocked/rooted phones in for warranty replacements and they received a new phone free of charge, covered under warranty.

Since this phone is 2 years old, don't expect much support anyways, so you might as well unlock it now, especially if it's less than a year old for you. That will ensure it can run the latest kernels regardless of what the official stock kernel is.

I really do not need the current OS, I use it just as a phone. I did though unlock it just because I could understanding I may have lost the balance of my warranty. I would not recommend others to do it though.

99% of the users out there will never take advantage of benefits from a rooted phone. This is myself included too. My only main reason to drive me is that 4.4.2 sucks battery life like nobody's business. I may, and repeat may, like 4.4.4 or better as with my Nexus 10 this vastly improved battery life from 4.4.3.. There is no guaranty either that someone will get a newer Android Version available but without the unlock there is a guaranty I can't get it on here if it becomes available in other than an OTA and good luck there.
 
Back
Top Bottom