No denying the S4 was a dreadful experience. Mine lasted 3 months before the iPhone 5S replaced it.
GPE was lovely & super speedy by comparison - truly was night and day the difference between the two.
No denying the S4 was a dreadful experience. Mine lasted 3 months before the iPhone 5S replaced it.
The GS4 was an amazing phone for its time. But only if you replaced TW with GPE.No denying the S4 was a dreadful experience. Mine lasted 3 months before the iPhone 5S replaced it.
A type of lag, and it's consequences ... :
http://superpowered.com/androidaudiopathlatency/#axzz3XTduabxD
Crazy to think of all the billions Google is leaving on the table.A type of lag, and it's consequences ... :
http://superpowered.com/androidaudiopathlatency/#axzz3XTduabxD
My S4 was definitely quite laggy, but it's just so interesting how massive the difference between the super flagship G3 and the Z3 Compact.
The S6 Edge was very fast and responsive, but in a more horsepower way, and doesn't seem as naturally light/quick as the Z3C.
The Is weird, didn't Samsung say it doesn't lag like 5 times at they s6 conference ....
its is weird...my S6 edge doesn't lag at all. Neither does my Note 4.
I have had lag on my 6+ and so has others here and in the iphone section...weird how that works.....
I've been a user of both OS's and never really experience this "lag" everyone talks about.
However, I was thinking, could it be the difference of animation that creates an illusion of lag? Apple has a fade-on-to-screen animation when opening an app while android varies depending on launcher?
I truly wonder why some experience it and others don't.
No some of us have known all to well for a long time - but are often told were 'just imagining it' if we complain ...
The biggest difference I saw was when I had both the Galaxy S4 with TW and GPE. The difference in performance / ram management / lag and fluidity - was astronomical.
So I've been on an LG G3 since just after it came out. I love the thing, but am selling it whilst the price is decent.
Picked up a cheap Z3 Compact yesterday as an interim device and wow. Just wow. I FINALLY understand what certain posters have been talking about with the dreaded LAG.
Using the devices side by side is just a night and day difference. This is using the exact same parameters, Google Now launcher, and I even took the micro SD card from the G3 and put it in the Z3C.
The Z3C is SO much faster, and what I thought was just "the occasional tiny bit of lag" on the G3 is actually not the case, I understand the complaints now. The Z3 Compact just flies in comparison, the only thing that is slightly slow is the camera, still figuring it out.
But OK, I get it, I finally get it! Has anyone else had any similar awakenings?
Any device is capable of lag. No device is flawless, there is no perfect device. EVERY DEVICE HAS ISSUES.
The $64k question, are you keeping it??
I had a play with it today at a Verizon store, I like it but so much space wasted on the device cause of the bezels and navigation buttons.
I didn't mess around with it that long but it did seem snappy and I was surprised how light it felt given its weight. I very much liked the display.
It seems that 4G LTE devices are good to go on prepaid accounts, my Note 4 and Moto X 2014 for example and I bet the Sony would work too.
No.
I'm going to assess my options over the next month with the G4, the S6 and perhaps even iPhone 6.
I may just keep the Z3 Compact as backup/holiday phone because I didn't pay much for it and like so much about it!
To set the record straight: my replacement S6 hardly lags. Nothing like my first unit -- I really don't know what happened there.
: thumbs up :
waterproof and small size makes it a good backup for sure, how much did u pay? I've seen reports that it is pretty fragile, which is a shame, would be great for beach, outdoor stuff etc
Huh. Both of mine lagged the same way you described yours did. Did you install the same apps as last time? Anything you did differently with this one? Maybe there's a way to fix the lag on mine.
Exactly, waterproof, nice size, very solid battery life as well.
Only paid £150 for it.
Can't stand the glass back - it slides all over the place, seems fragile (actually already had a small crack as I bought it 2nd hand) and obviously I'd have to wack a case on it (will look this weekend).
The other problem: the speakers really are poor. Not when listening to music, but when listening to podcasts. Awful, honestly. Can barely hear it on full volume around the house.
Otherwise I think it's a great phone, really hope that Sony continue with a Z4 Compact later this year.
I don't know. Google Keyboard now works smoother. It doesn't "catch up" like it used to. Once or twice I noticed backspacing can still do the "catch up" thing, but it wasn't as often as the first unit. I've left my long press duration at the default 300 ms (whereas before it was lower, like 280ms). I no longer get the "phantom long press" on the space bar anymore.
Opening and switching apps don't hang anymore either. The app switcher itself can sometimes take a SPLIT second longer than I know it can do, but I chock that up to TouchWiz idiosyncrasy. Sometimes it's instant, and sometimes it's a hair slower. No biggie here.
The biggest improvement is the fingerprint scanner. It is so much faster now. Almost instantaneous. Don't know really what the difference was.
In fact, to be honest. It could totally be a placebo effect thing. Maybe I'm more conditioned for the S6 now that it's a second unit. Maybe I know what to expect and how to prepare and set up the device. For example, maybe I got my thumbs more covered when inputting my fingerprints, etc. So... to be honest, who knows. The device does seem to be smoother and more stable to me. Also, the battery life of this unit is also better (though Play Services and Google OS are still top runners. Not sure what's going on there). Overall, I feel more confident about this device.
So... don't know. Take that for what you will.
Nope. Its the usual trope as soon as anyone mentions lag on android instead of discussing it the defences go up and iOS is spat out.
Some Android devices lag - a physical delay between pressing an icon or object on screen and the resulting launch/animation that follows.
Heck YouTube app itself has long been a notable example of an app on nearly all android devices where there is a physical delay when pressing icon and app launches.
Some Android Skins lag more than others not just in launching apps but in general UI fluidity.
Its just the way it is. Things are improving with raw horsepower doing the work on non stock devices. But it still rears its ugly head...
04-26 14:31:31.163 D/audio_hw_primary( 354): disable_audio_route: reset and update mixer path: audio-record
04-26 14:31:31.165 D/audio_hw_primary( 354): disable_snd_device: snd_device(55: voice-rec-mic)
04-26 14:31:31.167 V/WindowManager( 802): addAppToken: AppWindowToken{29c8296c token=Token{d82221f ActivityRecord{8891be u0 com.google.android.youtube/com.google.android.apps.youtube.app.WatchWhileActivity t5172}}} to stack=1 task=5172 at 1
04-26 14:31:31.169 I/SoundTriggerHwService::Module( 354): void android::SoundTriggerHwService::Module::onCallbackEvent(const android::sp<android::SoundTriggerHwService::CallbackEvent>&) mClient == 0
04-26 14:31:31.173 I/HotwordRecognitionRnr( 6307): Hotword detection finished
04-26 14:31:31.173 I/HotwordRecognitionRnr( 6307): Stopping hotword detection.
04-26 14:31:31.547 I/System.out(32231): YouTube MDX: Media route button available: false
04-26 14:31:31.606 I/System.out(32231): YouTube MDX: Media route button available: false
04-26 14:31:31.633 W/System.err(32231): YouTube MDX: Unknown type of route info: MediaRouter.RouteInfo{ uniqueId=android/tg:DEFAULT_ROUTE, name=Phone, description=null, enabled=true, connecting=false, playbackType=0, playbackStream=3, volumeHandling=1, volume=8, volumeMax=15, presentationDisplayId=-1, extras=null, providerPackageName=android }
04-26 14:31:31.633 I/System.out(32231): YouTube MDX: Media route button available: false
04-26 14:31:31.805 D/OpenGLRenderer(32231): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-26 14:31:31.809 D/Atlas (32231): Validating map...
04-26 14:31:31.910 I/art ( 802): Explicit concurrent mark sweep GC freed 12680(657KB) AllocSpace objects, 0(0B) LOS objects, 24% free, 48MB/64MB, paused 2.415ms total 91.111ms
04-26 14:31:31.915 V/WindowManager( 802): Based on layer: Adding window Window{17fe4a22 u0 com.google.android.youtube/com.google.android.apps.youtube.app.WatchWhileActivity} at 18 of 24
04-26 14:31:31.938 W/ActivityManager( 802): Permission Denial: Accessing service ComponentInfo{com.google.android.music/com.google.android.music.dial.DialMediaRouteProviderService} from pid=32231, uid=10085 that is not exported from uid 10065
04-26 14:31:31.940 E/YouTube (32231): (unknown) Media progress reported outside media playback: NEW
04-26 14:31:31.994 I/Adreno (32231): EGLInit: QTI Build: 01/29/15, 1bccc5d, I0ba6dce82d
04-26 14:31:32.003 I/OpenGLRenderer(32231): Initialized EGL, version 1.4
04-26 14:31:32.011 D/OpenGLRenderer(32231): Enabling debug mode 0
04-26 14:31:32.049 I/System.out(32231): YouTube MDX: MDX video stage moved to NEW
04-26 14:31:32.049 I/System.out(32231): YouTube MDX: MDX video player state moved to UNSTARTED
04-26 14:31:32.051 I/System.out(32231): YouTube MDX: MDX ad player state moved to UNSTARTED
04-26 14:31:32.105 I/ActivityManager( 802): Displayed com.google.android.youtube/com.google.android.apps.youtube.app.WatchWhileActivity: +921ms (total +998ms)
04-26 14:31:32.105 I/System.out(32231): YouTube MDX: Media route button available: false
04-26 14:31:32.106 W/YouTube (32231): apps.youtube.app.ui.MediaRouteButtonCompat.c:82 Could not find field mRemoteIndicator
04-26 14:31:32.106 W/YouTube (32231): java.lang.NoSuchFieldException: mRemoteIndicator
04-26 14:31:32.106 W/YouTube (32231): at java.lang.Class.getDeclaredField(Class.java:890)
04-26 14:31:32.106 W/YouTube (32231): at com.google.android.apps.youtube.app.ui.MediaRouteButtonCompat.c(SourceFile:77)
04-26 14:31:32.106 W/YouTube (32231): at com.google.android.apps.youtube.app.ui.MediaRouteButtonCompat.b(SourceFile:41)
04-26 14:31:32.106 W/YouTube (32231): at cie.a(SourceFile:47)
04-26 14:31:32.106 W/YouTube (32231): at chu.a(SourceFile:98)
04-26 14:31:32.106 W/YouTube (32231): at bny.onCreateOptionsMenu(SourceFile:156)
04-26 14:31:32.106 W/YouTube (32231): at android.app.Activity.onCreatePanelMenu(Activity.java:2823)
04-26 14:31:32.106 W/YouTube (32231): at s.onCreatePanelMenu(SourceFile:275)
04-26 14:31:32.106 W/YouTube (32231): at kj.a(SourceFile:276)
04-26 14:31:32.106 W/YouTube (32231): at kl.a(SourceFile:79)
04-26 14:31:32.106 W/YouTube (32231): at vs.a(SourceFile:49)
04-26 14:31:32.106 W/YouTube (32231): at mg.e(SourceFile:459)
04-26 14:31:32.106 W/YouTube (32231): at mh.run(SourceFile:69)
04-26 14:31:32.106 W/YouTube (32231): at android.os.Handler.handleCallback(Handler.java:739)
04-26 14:31:32.106 W/YouTube (32231): at android.os.Handler.dispatchMessage(Handler.java:95)
04-26 14:31:32.106 W/YouTube (32231): at android.os.Looper.loop(Looper.java:135)
04-26 14:31:32.106 W/YouTube (32231): at android.app.ActivityThread.main(ActivityThread.java:5254)
04-26 14:31:32.106 W/YouTube (32231): at java.lang.reflect.Method.invoke(Native Method)
04-26 14:31:32.106 W/YouTube (32231): at java.lang.reflect.Method.invoke(Method.java:372)
04-26 14:31:32.106 W/YouTube (32231): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
04-26 14:31:32.106 W/YouTube (32231): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
04-26 14:31:32.119 W/CastMediaRouteProvider( 2828): Invalid control category: MDX_MEDIA_ROUTE_CONTROL_CATEGORY
04-26 14:31:32.147 I/System.out(32231): YouTube MDX: Media route button available: true
04-26 14:31:32.147 I/System.out(32231): YouTube MDX: Media route button available: true
04-26 14:31:32.148 I/System.out(32231): YouTube MDX: Media route button available: true
04-26 14:31:32.667 E/WifiStateMachine( 802): WifiStateMachine CMD_START_SCAN source 10011 txSuccessRate=2.82 rxSuccessRate=2.32 targetRoamBSSID=any RSSI=-61
04-26 14:31:32.685 E/WifiStateMachine( 802): WifiStateMachine CMD_START_SCAN source 10011 txSuccessRate=34.91 rxSuccessRate=32.66 targetRoamBSSID=any RSSI=-61
04-26 14:31:32.970 I/System.out(32231): YouTube MDX: Media route button available: true
04-26 14:31:33.069 E/Ticker (32231): In action: browse, ticks can't be marked in the past
04-26 14:31:33.069 E/Ticker (32231): In action: browse, ticks can't be marked in the past
04-26 14:31:33.221 I/System.out(32231): YouTube MDX: add available CastV2 route: com.google.android.gms/.cast.media.CastMediaRouteProviderService:3f76ce8efe59d3e9155e099da4033847
04-26 14:31:33.222 I/System.out(32231): YouTube MDX: Media route button available: true
04-26 14:31:34.274 D/audio_hw_primary( 354): disable_audio_route: reset and update mixer path: low-latency-playback speaker
04-26 14:31:34.279 D/audio_hw_primary( 354): disable_snd_device: snd_device(2: speaker)
Anyone have any solution to the lag beside getting another phone?
Anyone have any solution to the lag beside getting another phone?
No some of us have known all to well for a long time - but are often told were 'just imagining it' if we complain ...
The biggest difference I saw was when I had both the Galaxy S4 with TW and GPE. The difference in performance / ram management / lag and fluidity - was astronomical.
They work....but the promise of the extensions and future functionality has not evolved. With Android widgets you can create a widget from just about any app you install. then you can place it in the place it will be the most useful to you.