Soak test for Droid Maxx

So what the heck is the point of the update then?

To fix bugs, I hope. The differences between AOSP 4.4 and 4.4.1 and 4.4.2 were not Android API updates - they were just a couple of bug fix updates. I don't care if they call it 4.4 or 4.4.2 or 4.4.47, I just care about the bugs getting fixed. If the home key bug, and the share bug, and the BT issues are not fixed - then, yeah, it was a waste of time.
 
Did anyone get the update last night? Email said it was supposed to come last night.

Sent from my Droid Maxx using Tapatalk 4
 
To fix bugs, I hope. The differences between AOSP 4.4 and 4.4.1 and 4.4.2 were not Android API updates - they were just a couple of bug fix updates. I don't care if they call it 4.4 or 4.4.2 or 4.4.47, I just care about the bugs getting fixed. If the home key bug, and the share bug, and the BT issues are not fixed - then, yeah, it was a waste of time.
Exactly... I dont care about baseband updates if it doesnt fix anything. I guess Verizon bloatloader is not compatible. lol
 
To fix bugs, I hope. The differences between AOSP 4.4 and 4.4.1 and 4.4.2 were not Android API updates - they were just a couple of bug fix updates. I don't care if they call it 4.4 or 4.4.2 or 4.4.47, I just care about the bugs getting fixed. If the home key bug, and the share bug, and the BT issues are not fixed - then, yeah, it was a waste of time.

Hopefully you are right.
 
To fix bugs, I hope. The differences between AOSP 4.4 and 4.4.1 and 4.4.2 were not Android API updates - they were just a couple of bug fix updates. I don't care if they call it 4.4 or 4.4.2 or 4.4.47, I just care about the bugs getting fixed. If the home key bug, and the share bug, and the BT issues are not fixed - then, yeah, it was a waste of time.

I see a lot of people saying the home button thing is a bug. Please explain to me why this is a bug. I always thought of the main home screen as "the" home screen. That's exactly why in basically every launcher you can choose which home screen is considered "the" home screen. Setting that screen has the sole purpose of getting to it by pressing the home button. So why do people not expect to be taken to that screen when they press the button designed to take them there?

Posted via Android Central App
 
Has anyone gotten the update yet? Email said last night, but still haven't seen anything.
 
I see a lot of people saying the home button thing is a bug. Please explain to me why this is a bug. I always thought of the main home screen as "the" home screen. That's exactly why in basically every launcher you can choose which home screen is considered "the" home screen. Setting that screen has the sole purpose of getting to it by pressing the home button. So why do people not expect to be taken to that screen when they press the button designed to take them there?

Posted via Android Central App

I think because previous versions of Android on Motorola would return them to their last used home screen. It doesn't really affect me as I only use 3 screens. One to the left is calender, main is circles and a few folders, right is music search and data usage (just for the heck of it even though I have unlimited)

Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
 
I see a lot of people saying the home button thing is a bug. Please explain to me why this is a bug. I always thought of the main home screen as "the" home screen. That's exactly why in basically every launcher you can choose which home screen is considered "the" home screen. Setting that screen has the sole purpose of getting to it by pressing the home button. So why do people not expect to be taken to that screen when they press the button designed to take them there?

Posted via Android Central App

Because it didn't work that way before the last update, and it doesn't work that way on stock android. And because it is registering as a double touch of the home button, it messes up some third party launchers/apps.
 
I see a lot of people saying the home button thing is a bug. Please explain to me why this is a bug. I always thought of the main home screen as "the" home screen. That's exactly why in basically every launcher you can choose which home screen is considered "the" home screen. Setting that screen has the sole purpose of getting to it by pressing the home button. So why do people not expect to be taken to that screen when they press the button designed to take them there?

Posted via Android Central App


Because pressing home should take you back to the last screen you were on, not the main home screen. My phone, I have my weather app and texting/FB/etc. apps on the main home screen. If I scroll to the right, it's all my bookmarked URLs and video services like WatchESPN and NBC Extra. If I am on that screen, and enter an app, then press home, I go back to my main home screen with the weather app. That one press of the home button should take me back to that bookmarked URLs and video services screen, though. I shouldn't go back to the main home screen unless I hit home a second time. Therefore, this is a bug. Home is simply to take you back to your collage of screens where you choose apps and such, not to auto-take you to the main home screen. And given KitKat introduced this bug (it wasn't like this before the KitKat update; it worked how it was supposed to), it needs to be fixed.
 
The share bug is what is pissing me off. I want to share a quick pic with my girlfriend? Nope. Its stuck on sharing to instagram. Want to send a pic from the browser through email? Nope. Its stuck on sending through Hangouts. Want to share a video from Youtube to Facebook? Nope. Its stuck on sending the video to Hangouts. Reset the preferences and reload all the bloatware you disabled.
 
I see a lot of people saying the home button thing is a bug. Please explain to me why this is a bug. I always thought of the main home screen as "the" home screen. That's exactly why in basically every launcher you can choose which home screen is considered "the" home screen. Setting that screen has the sole purpose of getting to it by pressing the home button. So why do people not expect to be taken to that screen when they press the button designed to take them there?

Posted via Android Central App

Imagine this scenario:

Use a launcher which allows you to change what the Home button does when you are already on the main home screen. Set it to anything, really (a good example is to show the home screen thumbnails to choose a screen to go to).

Now, from an app, hit home. You are brought to the home screen thumbnails, rather than the main home screen. This is because the home button brought you to the home screen, but then an additional press was processed, and it then executes whatever you have assigned to the home button press (thumbnails screen in this case). This is not useful behavior.

You may need to experience this first-hand to fully understand the difficulty.

Even without using that kind of setup, this problem is still a bit of an annoyance, because as others have stated no Android version has ever worked this way. Hence the reason we call it a bug.

Sent from my XT1080 using Tapatalk
 
The only thing I really care about at this point, is getting the Bluetooth fix.

It will never happen, but the coolest change would be if they somehow slipped by Verizon away for foxfi to work again.

Sent from my Nexus 7 using Tapatalk
 
Imagine this scenario:

Use a launcher which allows you to change what the Home button does when you are already on the main home screen. Set it to anything, really (a good example is to show the home screen thumbnails to choose a screen to go to).

Now, from an app, hit home. You are brought to the home screen thumbnails, rather than the main home screen. This is because the home button brought you to the home screen, but then an additional press was processed, and it then executes whatever you have assigned to the home button press (thumbnails screen in this case). This is not useful behavior.

You may need to experience this first-hand to fully understand the difficulty.

Even without using that kind of setup, this problem is still a bit of an annoyance, because as others have stated no Android version has ever worked this way. Hence the reason we call it a bug.

Sent from my XT1080 using Tapatalk

This makes more sense to me, the idea that the problem is that pressing home makes custom home button actions in third party launchers not work. I see that a few people have stated that previous versions of android did not have the current home button behavior. I suppose I never realized it because I keep my home screen count minimal. But for those who feel this is a problem and are not using third party launchers, I have a simple solution for you: put your most common stuff on the "home" home screen. It sounds like the frustration might be this: using an app, press home, go to the main home screen, then have to scroll to another home screen to do whatever you want to do. If that's the case, put your most common stuff on that main home screen.

Think of it this way: I personally would be annoyed if the home button did what all these people want it to do. I prefer to have the home button take me to my main home screen because that's where I keep my most commonly used items.

Put another way, would all those folks who don't like the current setup still be annoyed if they actually did want to go to their main home screen and then have to scroll to it when a home press didn't take them there?

I saw somebody said stock android doesn't do this. Can we verify that is true for 4.4? If somebody is testing this on a nexus (stock android) that's not a true test because the nexus has 4.4.2 right?

Posted via Android Central App
 
But for those who feel this is a problem and are not using third party launchers, I have a simple solution for you: put your most common stuff on the "home" home screen. It sounds like the frustration might be this: using an app, press home, go to the main home screen, then have to scroll to another home screen to do whatever you want to do. If that's the case, put your most common stuff on that main home screen.

What do you think I am doing now? My main home screen is FULL with stuff I use a LOT and that is before I go to quick launch URLs and the video services one screen to the right, which I also use a LOT. So your resolution proposal is a no-go here. I liberally use the content on two screens a lot. If I didn't use some items, I wouldn't have the shortcuts there.
 
What do you think I am doing now? My main home screen is FULL with stuff I use a LOT and that is before I go to quick launch URLs and the video services one screen to the right, which I also use a LOT. So your resolution proposal is a no-go here. I liberally use the content on two screens a lot. If I didn't use some items, I wouldn't have the shortcuts there.

Then fixing the bug wouldn't help you anyway because you'll always be taken to a home screen that doesn't have apps that you use frequently. If you use more than one home screen a lot this is always going to be a problem regardless of what home screen it takes you to. And even if you use the example presented earlier where you use a third party launcher and set the home button to bring up the thumbnails of all the home screens it's still an extra step to get where you want, it's just a button press instead of a swipe.

I guess I just don't understand why, if you want to be taken back to a particular screen each time, set that one to be the main screen.

There's no right or wrong here, if it bugs you (no pun intended) then I can see how it's frustrating. But it doesn't bother me, and probably plenty of other people too. It just doesn't seem to be much of a bug, which usually implies more serious negative effects, like the sharing bug, which is likely a problem for many people because it's not a preference thing.

Posted via Android Central App
 
A single press registering as a double press is a bug and a PITA bug. This should be addressed and rather easily. If it works a certain way on all Android variants but the MAXX it needs to be fixed. This is not a "feature" of the MAXX or a benefit.
 

Forum statistics

Threads
957,019
Messages
6,971,053
Members
3,163,685
Latest member
drakenhu1