just got my razr i here in the uk. love the device so far. fantastic form factor and importantly for me, a superb battery life one things nagging me though...is anyone else seeing a slight 'jerky' animation? i see it when swiping left to the 'quick settings' screen and when pressing the apps button. once in the apps though the left <> right swiping is perfect! pressing the home button from the home screen to show 'manage pages' too is pretty jerky or laggy but not sure if that is how it should be this guy sees it initailly when starting the game just before 4.00 mins in
http://www.youtube.com/watch?v=SILUVIwiNF0
but once the game is running all seems ok. this guy i can see it at 1.57 when he swipes left from the homescreen to the 'quick settings'
http://www.youtube.com/watch?v=4rfud0GFXRg&feature=related
seems like it occurs when at some places within the phone but not everywhere. have i been spoilt using a nexus for the past week running a silky smooth jellybean vs this running ics? or is it a defective unit?
I would say on mine there is the slightest pause when moving to the quick settings that I hadn't noticed before! I hope it doesn't bug me now!!
Going to the manage pages screen or indeed the "helicopter view" (pinch zoom on the homescreen) is really jerky. But I dont find any noticeable lag or jerkiness anywhere else. In fact I find the whole experience smoother and slicker than even my Nexus 7. The only better Android experience I had was Jelly Bean on the Galaxy Nexus which is super silky.
Jelly Bean is slightly faster at a number of things especially switching screen context as the CPU is ramped to a high clock speed as soon as you touch the screen. I noticed the improvement in opening things like the app drawer when I had my Galaxy Nexus and upgraded to JB.
The Jones said:
I would say on mine there is the slightest pause when moving to the quick settings that I hadn't noticed before! I hope it doesn't bug me now!!
Click to expand...
Click to collapse
ooops sorry about that! :laugh:well i've adjusted both 'window animation scale' and 'transition animation scale' from 1x to off and that certainly speeds the whole ics experience up so that is worth doing if you have not. hope it does not affect the phone in another adverse way though
alpha beta gaga said:
ooops sorry about that! :laugh:well i've adjusted both 'window animation scale' and 'transition animation scale' from 1x to off and that certainly speeds the whole ics experience up so that is worth doing if you have not. hope it does not affect the phone in another adverse way though
Click to expand...
Click to collapse
Does that not disbale animations?
don't think so. just seems to speed things up a touch.
This does indeed deactivate some Animations but only the ones Navigating in Apps or Settings and so on.
The actual Launcher Animation is not changed at all.
I have the same lag and its not so bad but still somehow annoying.
Didn't noticed that so much in all the test videos out there.
Someone tried to do a hard reset and start from scratch? Maybe fixes it.
The Jones said:
Does that not disbale animations?
Click to expand...
Click to collapse
I noticed really jerky animations on an M I saw at a Verizon kiosk, and the i seems to be fine from videos I see.
Since everybody seems to upbeat about the Nexus 4, here some things that REALLY piss me off.
For reference, I am coming from a DEFY / CM9 and have at the same time here a new HTC One S / CM10. And then there would be a Nexus 7, and a Kindle Fire / CM10/SGT7.
Why on earth couldn't they have the normal buttons on the bottom, and instead needed to waste precious screen real estate ? I do understand that a 7 inch tablet needs that as it's turned between landscape and portrait. But for a phone ... After all there is space on the device, which is unused now ...
This little microSIM tray is nifty. Especially if you are at an airport, just bought the prepaid microSIM and try to put it in. You have the tool with you, right ?
The new and improved camera app stinks like heck. The device support ISO settings, different focus modi, red-eye removal ... the works. But the default application fails to expose ANY of that. I cannot even set the JPEG quality level ... EPIC fail.
Tried to use 720p video recording ? 22fps stuttering ...
Lockscreen widgets ... why on earth would I want to have that ? And why couldn't there just be a simply settings entry to disable that ? (yes, I know that there is now an app out there that gets rid of it ...)
The good old clock. Nice work. Tons of features. Way too many. Why split this over-engineered mess into "Alarm" and "Watch" and whatever ?
Battery drain ... Looks like a lot of the new features (some which I cannot uninstall per default) are sucking up processor time, like the "Mediaserver" (got the same apps/settings as on CM9/CM10, where this does not happen).
This new pulldown quick settings is nifty. Takes me now 2 clicks and one slide to toggle wireless ... much improved over the one-click toggle in CM9/CM10 (and HTC Sense, and TouchWhiz, and ...).
Overall I feel that 4.2 is a step back from 4.1, because every new feature that should make up 4.2 seems to be more in the way than anything else. The toy needs sooo urgently CM10 it's not even funny.
I totally agree with all your points, it's definitely a turd. Wanna sell it?
To your first point, I have a feeling that Google will eventually rethink the use of on-screen buttons and come up with a solution that occupies less real estate. The back button is redundant and can easily be replaced in-app like the menu button was (e.g. click the icon in the upper-left corner to go back is already implemented in many apps) and its behavior is confusing and inconsistent; it's a carry-over from the past and poor UX design overall. The task switcher could quick easily become a hold and drag gesture from the home button or status bar with adding any additional steps to get to it.
Thinking something crazy like the tablet interface where the status bar moves to the bottom, gets a little wider, and houses the home button would be a good solution.
Why does... does... do you guys smell apples? I swear I think I do.
TheFiveDots said:
The back button is redundant and can easily be replaced in-app like the menu button was [...] and its behavior is confusing and inconsistent
Click to expand...
Click to collapse
What the... huh? Have you ever used android for longer than a few minutes?
The missing back button is the first thing I always cringe over whenever I have to handle an apple device at work, it's the best thing of the whole OS (well,at least it's pretty awesome)
And software buttons are the best solution in general, because they can hide and make place for more stuff on demand.
The "empty" space on the bottom of the nexus4 isn't because they thought they'd leave space there just for fun, there's space because it's needed for the hardware below.
If there were hardware buttons taking up the space the phone would be even bigger (or the screen smaller)
Instead of whinning about it why not try to do something about it.
Sent from Arkham
Yeah stop moaning and send it back.
Why keep a phone that "pisses" you off so much...
U mad bro?
Early adopter and complaining (very mad) that there are some updates needed............silly
Maybe u should sell it on eBay and make some money?
Or better......sell it to one of the great devs that are waiting for a device!!!!!!
Sent from my GT-I9450
muspel said:
What the... huh? Have you ever used android for longer than a few minutes?
The missing back button is the first thing I always cringe over whenever I have to handle an apple device at work, it's the best thing of the whole OS (well,at least it's pretty awesome)
And software buttons are the best solution in general, because they can hide and make place for more stuff on demand.
The "empty" space on the bottom of the nexus4 isn't because they thought they'd leave space there just for fun, there's space because it's needed for the hardware below.
If there were hardware buttons taking up the space the phone would be even bigger (or the screen smaller)
Click to expand...
Click to collapse
Yes. I have. Thanks for your assumptions though. Despite your "cringing", Apple's implementation of a dynamic "back button" at the top-left of nearly every iOS app is much more consistent and predictable.
On Android, sometimes the back button takes you back to the screen you were on previously on the same level, sometimes it takes you up a level, and sometimes it closes the app which is always surprising and annoying if you were not aware you were already at the root level. The home button closes an app, the back button doesn't need to. Google is even well aware of this unpredictably and has gone as far to draw up guidelines as to how it should be implemented, but many developers choose to ignore it.
Unpredictable behavior is bad UX design, plain and simple. Having a place in-app that takes you back and a hardware/software button that does the same is also redundant and unnecessary. Navigating an app should be natural and intuitive and all within the app, in my opinion. Hardware/software keys should be reserved for OS-level tasks like Home, Task Switching, etc.
I agree the software buttons are the best choice, but it would be nice to see them implemented in a much more dynamic and space-saving way.
The sim eject tool, aka paper clip.
TheFiveDots said:
To your first point, I have a feeling that Google will eventually rethink the use of on-screen buttons and come up with a solution that occupies less real estate. The back button is redundant and can easily be replaced in-app like the menu button was (e.g. click the icon in the upper-left corner to go back is already implemented in many apps) and its behavior is confusing and inconsistent; it's a carry-over from the past and poor UX design overall. The task switcher could quick easily become a hold and drag gesture from the home button or status bar with adding any additional steps to get to it.
Thinking something crazy like the tablet interface where the status bar moves to the bottom, gets a little wider, and houses the home button would be a good solution.
Click to expand...
Click to collapse
Yes, I was thinking that the merged tablet interface would be a cool idea for the "Nexus 4". With CM10/SGT7 on the KF you also get a nicer notification panel, which might be reasonable for a device of this size.
MonsieurJohnny said:
The sim eject tool, aka paper clip.
Click to expand...
Click to collapse
Doesn't work. Paperclip is too big for that one (at least the 3 different ones I tried).
woody296 said:
I totally agree with all your points, it's definitely a turd. Wanna sell it?
Click to expand...
Click to collapse
Actually I might do (or simply return it), but for different reasons than just the SW I was ranting about (and being disappointed for now). Of course many issues I cited will be fixed with a CM10.1 custom ROM in about 3 months ...
I disagree with the on screen buttons. I had the gs3 and it was terrible for accidentally catching the buttons. The bezel is there for a reason, Samsung put real buttons on the bezel and it's terrible. This is best of both worlds, if an watching a video I get the full screen as the buttons disappear, yet for everything else the screen is a great size.
Sent from my Nexus 4 using xda premium
I feel sorry for everyone and everything in your life.
I disagree. 4.2 is a major improvement, much faster and smoother. All these new things will be improved upon in future updates.
It sounds to me like some people would never be happy no matter what they do.
As for the on screen buttons, i love them after coming from a device that had a push button for home. It would be great though to make them autohide as they do for video.
sent via xda premium with nexus 7
Lol I love that all you fan boys bash the Op and make fun of him, but I hate to break it to you, everything in his post is true. The proper response is: "yes Google screwed some things up pretty badly here, but overall the good outweighs the bad."
Some of you people are worse than iSheep. No need to defend everything a company does. If you don't acknowledge the bad you basically give Google a license to never fix the problem it created because Google thinks you like those problems!
-Sent from my GS3 running CM10.-
I've been using it for a few days and I love the device . smoother than m gs3
Sent from my Nexus 4 using Tapatalk 2
This guy doesn't own one, he's just seen videos, it is pretty obvious.
People just love complaining, I think this is he's first android phone, probably bought it because it was so cheap, try to buy an iPhone for that price you'll probably just about pick up a second hand 4s, I've never seen a phone so cheap with so many features, first phone with 2gb ram, even the iPhone 5 has only 1gb ram.
send your phone back and go and buy an iPhone 4s from ebay!!!
I just upgraded from a Galaxy Tab (original) to a Nexus 7, and while most everything else is a sweet upgrade, scrolling has become a consistently frustrating experience.
On my Galaxy Tab (Gingerbread), scrolling is simple and intuitive. I "flick" my finger across the screen and it scrolls fast (even if it might be too fast sometimes) and the inertia continues the way I would expect (more like Froyo as opposed to iOS), and swiping scrolls as fast as I swipe no matter how long I press my finger to the screen. However, on the Nexus 7, if I flick, sometimes it flicks fast, sometimes it flicks very slow, and sometimes it comes to a dead stop when I release my finger. If I swipe, it behaves better, but doesn't seem to go the speed of my finger unless I hold it down longer. I feel like a little kid trying to get a toy to work. It's not intuitive, and I'm not sure if the problem is the design of Jelly Bean or the Nexus 7's hardware, or the device has a manufacturing defect. As a comparison, the homescreens flick and swipe appropriately most of the time. Apps seem to have the same scrolling frustrations for me as the browser and settings lists.
Can someone tell me how Jelly Bean is supposed to work with flicking and swiping? What about in apps like Chrome, games like Devil's Attorney, or settings lists? Also, the homescreens.
If can adjust Android's default scrolling speed and inertia (and swiping and flicking responsiveness) through root, I'll do that, but I'm not sure there's anything else I can do before that.
Just saw this today, have not tried it yet myself but it sounds like this is what you are looking for.
http://forum.xda-developers.com/showthread.php?t=2082060
Nexus 7 touch response FIX
Sent from my MB855 using Tapatalk 2
Hey everyone,
due to the high resolution and comparably large screen estate I would like to use a lower screen density of around 410dpi, instead of the stock 480. :fingers-crossed:
One example:
On my Galaxy Nexus I was used to having a 24dpi high navigation bar at the bottom of the screen.
It was small but still I was able to hit the buttons accurately.
Same goes for the small keys of my keyboard of choice, Swiftkey.
Since I am on the HTC One and I flashed a Custom ROM, which I am running on 410dpi and wanted that stock android navigation bar at the bottom even at 48dpi (which is like 1.7x the height of the one I was using on my Galaxy Nexus) I have trouble hitting the buttons.
This is very disappointing.
It feels like the Touch layer of the HTC One is not that accurate
Is it just me or is this a known problem?
(Couldn't find anything via search, though)
Any ideas what to do about it?
All the best and thanks in advance :good:
I don't see this at 360dpi which is what I have mine at, but I do see it at 240, but everything then is silly in size.
Have you enabled the show touches in dev options and checked where its actually pressing?
Always keep forgetting about that! Thanks!
That is pretty weird...the touch inputs seem to be quite accurate, though. (Debugging Tool)
But it doesn't recognize them in something like "the upper half of the navigation bar" :/
I quickly shot a Video (sorry not the best focus point )
One can clearly see that I am hitting the home button several times, but the input doesn't get recognized.
That is really really weird and unsatisfactory :/
I gave it a shot for you... It seems to work fine on 36dp and above. 30 and 24 exhibit the same behavior as your video.
FYI: I'm running SlimROM at 361dpi. That was the default for me when I went from ARHD 10.2 to Slim b6 and it has stuck with me since then. I tried to get the same look in RootBox but it didn't work the same, so I went back to SlimROM b6.8, and am now on SlimROM b7.
Thanks :good:
I am starting to believe that this is might be caused by the Logo-Button-Hack.
If you peek closely from the side under the tip of your finger touching the button and starting from the very bottom of the glass area there is just no response at all on the logo. It's like the first pixel of the screen are allocated to the logo-button and not the area below the screen.
Maybe an area of lets say 10-15 pixels height is used for that and therefore not any longer available for the nav bar.
Which doesn't really matter if you are hitting the comparably huge app-icons in the drawer otherwise
After a week of using the 6T, I noticed that my typing wasn't as accurate as it was on my Moto Z Play. My thumbs also were a little uncomfortable when typing for a while. I realized that because of the screen extending further down the screen on the 6T vs the MZP, I had to move my thumbs much more down the phone than before. After playing around with the floating function of the Google Keyboard, I found a position that is more comfortable (image attached), and my accuracy has improved as well. The keys are now in a more natural position, lining up right next to where my thumbs fall when holding the phone.
The other option is also holding the phone lower, thereby placing thumbs where the keyboard lies on this phone. The downside of that for me is that I have to shift my hands up and down the phone to get my thumbs to the top of the screen. Time will tell which solution I prefer.
Out of curiosity, I wanted to see if anyone else who is coming from a phone that had a much larger chin than the 6T has had the same challenges. It may be also that I'm just getting old, and my hands are less flexible.
how do you make the gboard float like that? I can't seem to find it in settings.
raing said:
how do you make the gboard float like that? I can't seem to find it in settings.
Click to expand...
Click to collapse
Tap the g in the upper left, then the triple dots top right, look in the lower right?
This will be a necessity for me if I ever talk myself into upgrading my MZP to a 6T as well. My stubby, clumsy thumbs will have nothing to do with a keyboard all the way at the bottom of the device.
Actually recently got rid of nav bar for gesture nav on the MZP, and this helps in that scenario too.
I just got my OP6T today and I'm pleasantly surprised by the phone. Maybe the screen is not as sharp as my previous U11 but the difference is quite small so I think I can live with that for now. The secondary thing is like the OP mentioned typing on the keyboard. I tried using the phone with gestures and even though its really easy to navigate around the UI, writing is just horrible. Space bar is so low that I have to hold the phone really low in order to right properly. With standard navigation bar everything is ok. Tried floating keyboard but its so weird to type and look down to see what you are writing.
Also it's so funny that everyone is chasing the 99% front display ratio but at the same time interaction with the phone suffers a lot and we have to find ways to go around obstacles created but those almost full front display phones.
I use Minuum keyboard with adjustable spacebar height independent of the adjustable keyboard height.