3 ms·

Let me guess: Android fan tries Nexus, doesn't like it switches to iPhone, etc. etc.? Somehow I don't think "Android fan tries new Android phone and likes it" w

by dwyer 15y ago

Let me guess: Android fan tries Nexus, doesn't like it switches to iPhone, etc. etc.? Somehow I don't think "Android fan tries new Android phone and likes it" would be as newsworthy.

mdwrigh2 15y ago
No, he's still using Android, he's just underwhelmed by the Galaxy Nexus.
- Symmetry 15y ago
  I was a bit underwhelmed too. Both because the menu button isn't always in the same place anymore, and because the back button doesn't interact in the expected way with the new way of switching apps.
  - chimeracoder 15y ago
    Could you elaborate on the latter? I'm currently on an Incredible (CM 7 - so Gingerbread), and the back button is the third from left (home, menu, back, search), and the back button has unpredictable functionality (depending on the application).
    - Symmetry 15y ago
      Lets say I open up the web browser, then I use the application selector to go to my Twitter app. If I hit back I'll go to the homescreen, rather than the web browser. The app selection button somehow flushes out the entire back stack, which is really, really annoying. As to unpredictability regarding views within apps, its a bit worse but not hugely different.
      - chimeracoder 15y ago
        I'm confused - I thought they were trying to get devs to standardize that, and that they also changed things in ICS? The way it currently is (for me on Gingerbread) that some apps have the back button go back to the previous view, but some go to the homescreen. And if I (say) open a browser link in an app, the back button will take me back to the application. (That may also be app-specific, but I just tried it out with one app). So what's different on the Nexus, and what part of that is ICS-specific changes (as opposed to things that app developers have to implement independently)? (Apologies for the confusion, but I still haven't seen an ICS device, and I don't develop for Android, so my knowledge of this is fairly passive, as a consumer).
nextparadigms 15y ago
Not really. He's just going to wait for an ICS phone with better hardware. I kind of have to agree with him. I've been disappointed with Google's decision for the 2nd year in a row to allow Samsung to make the "Nexus" devices as just upgraded (if that) versions of their Galaxy S phones. I don't mind Samsung building them (although I really hope they are coming out with a new build material this year, other than plastic), I just mind that the Nexus phones, the ones that are supposed to set the standard in the industry, are just rehashed Galaxy S devices from half a year earlier, in both hardware specs and looks (other than the HD resolution). I would prefer if Google waited until a new chip generation was available to put it in their Nexus devices, rather than use one that's already been on the market for the past 6 months or more. This has been really disappointing, and I think a lot of Android fans agree with me here. For example, if it's expected for a quad core chip to arrive on the market for the first time in March or April, then make sure the Nexus is the first or one of the very first to use it. If it's expected for Cortex A15 to arrive in phones sometime by the end of the year, make sure Nexus is one of the very first to use it, and so on. Make the industry follow Nexus, and not Nexus follow the industry as it's been the case with the past 2 generations. I know Google cares more about being the one with the latest major Android version, but it would really help if it was the one with the latest technologies, too. I don't want to have to choose between the latest hardware and the latest software. Not to mention that Nexus is a device that is targeted at early adopters, so you're kind of screwing early adopters there when you don't offer them the latest hardware technology, too. I'm hoping Google buying Motorola means they will finally combine the two, and offer the latest stock Android versions on the latest hardware. Also, since he mentions it, I have a tiny issue with ICS. Why not actually close the apps from the multi-tasking list if you're going to "bother" to remove them from the list? It kind of seems like a pointless action to just remove it from the list to make it "cleaner" (why?), instead of actually closing them.

by dwyer 15y ago

Let me guess: Android fan tries Nexus, doesn't like it switches to iPhone, etc. etc.? Somehow I don't think "Android fan tries new Android phone and likes it" would be as newsworthy.

mdwrigh2 15y ago

No, he's still using Android, he's just underwhelmed by the Galaxy Nexus.

Symmetry 15y ago
I was a bit underwhelmed too. Both because the menu button isn't always in the same place anymore, and because the back button doesn't interact in the expected way with the new way of switching apps.
- chimeracoder 15y ago
  Could you elaborate on the latter? I'm currently on an Incredible (CM 7 - so Gingerbread), and the back button is the third from left (home, menu, back, search), and the back button has unpredictable functionality (depending on the application).
  - Symmetry 15y ago
    Lets say I open up the web browser, then I use the application selector to go to my Twitter app. If I hit back I'll go to the homescreen, rather than the web browser. The app selection button somehow flushes out the entire back stack, which is really, really annoying. As to unpredictability regarding views within apps, its a bit worse but not hugely different.
    - chimeracoder 15y ago
      I'm confused - I thought they were trying to get devs to standardize that, and that they also changed things in ICS? The way it currently is (for me on Gingerbread) that some apps have the back button go back to the previous view, but some go to the homescreen. And if I (say) open a browser link in an app, the back button will take me back to the application. (That may also be app-specific, but I just tried it out with one app). So what's different on the Nexus, and what part of that is ICS-specific changes (as opposed to things that app developers have to implement independently)? (Apologies for the confusion, but I still haven't seen an ICS device, and I don't develop for Android, so my knowledge of this is fairly passive, as a consumer).

nextparadigms 15y ago

Not really. He's just going to wait for an ICS phone with better hardware. I kind of have to agree with him. I've been disappointed with Google's decision for the 2nd year in a row to allow Samsung to make the "Nexus" devices as just upgraded (if that) versions of their Galaxy S phones. I don't mind Samsung building them (although I really hope they are coming out with a new build material this year, other than plastic), I just mind that the Nexus phones, the ones that are supposed to set the standard in the industry, are just rehashed Galaxy S devices from half a year earlier, in both hardware specs and looks (other than the HD resolution). I would prefer if Google waited until a new chip generation was available to put it in their Nexus devices, rather than use one that's already been on the market for the past 6 months or more. This has been really disappointing, and I think a lot of Android fans agree with me here. For example, if it's expected for a quad core chip to arrive on the market for the first time in March or April, then make sure the Nexus is the first or one of the very first to use it. If it's expected for Cortex A15 to arrive in phones sometime by the end of the year, make sure Nexus is one of the very first to use it, and so on. Make the industry follow Nexus, and not Nexus follow the industry as it's been the case with the past 2 generations. I know Google cares more about being the one with the latest major Android version, but it would really help if it was the one with the latest technologies, too. I don't want to have to choose between the latest hardware and the latest software. Not to mention that Nexus is a device that is targeted at early adopters, so you're kind of screwing early adopters there when you don't offer them the latest hardware technology, too. I'm hoping Google buying Motorola means they will finally combine the two, and offer the latest stock Android versions on the latest hardware. Also, since he mentions it, I have a tiny issue with ICS. Why not actually close the apps from the multi-tasking list if you're going to "bother" to remove them from the list? It kind of seems like a pointless action to just remove it from the list to make it "cleaner" (why?), instead of actually closing them.