I can't figure out why the Facebook App on the N10 acts differently than on my N7 and N4.
For example I can't access my timeline by clicking on my profile as usual, instead it only shows a protocol of my last actions/activities.
It doesn't seem normal to me, is it a bug on the N10 out is it a crappy feature?
cgorki said:
I can't figure out why the Facebook App on the N10 acts differently than on my N7 and N4.
For example I can't access my timeline by clicking on my profile as usual, instead it only shows a protocol of my last actions/activities.
It doesn't seem normal to me, is it a bug on the N10 out is it a crappy feature?
Click to expand...
Click to collapse
Same issue here. Pictures are missing too.
I've tried to force it to a different layout or size with Paranoid Android, but no joy
Try Friendcaster instead?
Friendcaster FTW :good:. It works perfectly, loads fast, runs great, and looks beautiful on the Nexus 10. I enjoyed it so much more over the official Facebook app that I decided to buy the ad free version .
Never even installed it, just got used to using the web version on my X2 cause the app sucks
What is facebook? Isn't every one on G+? Buahaha!!!!
I reported it two days ago. Been fixed today...
Problem with Friendcaster and other third party apps is that if any of your friends have set their privacy settings to not allow use of their timeline by third party apps, you won't see their posts.
Updated Facebook app today is way faster sometimes, but I'm also getting long hangs I never got before when tapping on notifications.
I generally on the N10 just look at FB in Chrome. Wish they'd get a tablet app out!
Sent from my Nexus 10 using Tapatalk 2
The latest update 121312 is really good... best version of FB app ever for Android.
Am I also supposed to get huge images in the timeline???
I've had nothing but horrible experiences with chrome on droid (lag everywhere including just simply bringing up bookmarks, sucking power/background data), was wondering if anyone with the new N7 + 4.3 could comment on its performance in its newest incarnation
For me occasional freezes and lock ups on this site.
Sent from my Nexus 7 using xda premium
I want to know the experiences with Chrome in this Nexus 7-2013. I the chrome is always slowest that all other browser, also the native Android browser is better.
It’s is a bad port of the desktop version. Its improvement every version, but it’s not yet ready to production.
Bugs:
The all refresh web pages, start page, the slow Omnibar, slow loading web pages.
On initial page loads after reboot it is reasonably fast.
My problems with it are
1) eventually using it relates to my tablet rebooting
2) page loading slows down over time
3) tabs get hung over time
4) when tabs hang it pegs my broadband at 100% utilization
Because of these reason I just stopped using it and happily my random reboots went away. I can start using it again and my random reboots will return within a day. So high correlation, but I cannot point to causation. The core reboot problem is in the Android OS, but Chrome seems to be the most apt and triggering the problem (for my usage patterns)
It's certainly not as fast as I'd like it to be. As has already been said, it's pretty quick on a fresh boot, and as long as you don't have too many tabs open it seems to do pretty well overall (better than the original Nexus 7 at least). I've never had it cause a random reboot, but I have had Chrome crash on me once. Happier with it than I was, but hopefully they get it working better soon...
To clarify, the "random" reboot for me isn't always in Chrome (or it wouldn't be random). It is sometimes in Chrome, but usually somewhere else, commonly just the tablet sitting there idling. It always happens sometime after Chrome tabs start getting jumpy or hang. It never happens before then. After I stopped using Chrome, the reboots went away completely. Before I used to use Chrome, Maps, and play videos. Now I use Opera Mini, Maps, and play videos.
For *my usage* there is a high correlation with using Chrome, but I cannot point to causation.
It feels like the core problem is in the Android OS, so I'm sure there are other apps that can trigger the random reboot, but for my usage pattern Chrome is the one that shows very high correlation.
It is even possible the core problem is in the networking layer or wireless network driver as when Chrome started getting jumpy, I noticed my other network apps would get jumpy. When I stopped using Chrome, all the other network apps I thought I was having issues with seem to be running without any jumpiness anymore (this points to a core Android problem being triggered, since it affected multiple apps)
It will definitely need an update down the road. I feel it get laggy then not being as quick after awhile, and it isn't crazy about this site.
(although to be fair this site seems to have issues with all different browsers lately, even my desktop Chrome and Firefox)
I've been using Firefox, and trying Boat Browser in the meanwhile.
The problem may be with Chrome itself. I'm no Apple fan but I received a new iPad 3rd Generation last December and was using it for bedtime surfing. Safari just sucked so I installed Chrome which was infinitely better. But after the updates in the months following it really became unbearable to use. I ordered my Nexus 7 on July 26 after a seriously horrendous attempt to type a five line reply to a post on this site (which I blame on the fundamentally flawed iOS operating system and its inability to deal properly with form input fields). I've been using Chrome on my N7 for a few days now and though the experience is much improved I find there's a problem with Chrome itself on the tablet. The most annoying issue is how it will freeze up; when that happens you can navigate away from the browser and do anything else but when you return to it maybe five minutes later it is still locked up. This freeze may affect a single tab or all browser sessions (I usually have multiple windows open).
stevemw said:
The most annoying issue is how it will freeze up; when that happens you can navigate away from the browser and do anything else but when you return to it maybe five minutes later it is still locked up. This freeze may affect a single tab or all browser sessions (I usually have multiple windows open).
Click to expand...
Click to collapse
Yeah, it is a pain. I had to use the recently used button to swipe away Chrome all the time and then usually it started working again. Sometimes I had to force close it.
However you lose your context so it got quite annoying. I just stopped using Chrome.
Yeah same here its awful. Flash the AOSP browser or get an AOSP ROM.
sfhub said:
Yeah, it is a pain. I had to use the recently used button to swipe away Chrome all the time and then usually it started working again. Sometimes I had to force close it.
However you lose your context so it got quite annoying. I just stopped using Chrome.
Click to expand...
Click to collapse
I found using recent apps to swipe away the app frequently did no good. When the browser reopened the same tabs would be opened and the pages still frozen. I've spent the last half hour trying to find a decent browser and they all have something I don't like. The old stock browser like on the Samsung Galaxy Nexus was so much better.
What browser are you using now?
stevemw said:
I found using recent apps to swipe away the app frequently did no good. When the browser reopened the same tabs would be opened and the pages still frozen. I've spent the last half hour trying to find a decent browser and they all have something I don't like. The old stock browser like on the Samsung Galaxy Nexus was so much better.
What browser are you using now?
Click to expand...
Click to collapse
I'm using opera mini because I got used to it on questionable phone data connections.
Instead of swiping away, tap and hold the app, choose app info, then force close. That always works to get chrome unhung and working but you do lose your tabs.
stevemw said:
For me occasional freezes and lock ups on this site.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same, but only on the XDA Forums.
I can confirm with latest OTA and everything on my new Nexus 7 that Chrome is the culprit for reboots. It is also still a very laggy browser compared to others (especially compared to the AOSP browser). You can really tell when browsing, scrolling, panning, zooming around on Desktop web pages where Chrome will chug and the AOSP browser will do it all smoothly.
With that said, I rooted the device, and flashed the AOSP browser, and stopped using Chrome. No more lag, random reboots, just very smooth and crisp web browsing.
sfhub said:
I'm using opera mini because I got used to it on questionable phone data connections.
Instead of swiping away, tap and hold the app, choose app info, then force close. That always works to get chrome unhung and working but you do lose your tabs.
Click to expand...
Click to collapse
Thanks.
Sent from my Nexus 7 using Tapatalk 4 Beta
Has anybody been using this browser on Nexus 4? I started and I really like it; less hangups than chrome, better interface (I like the disappearing url bar) than dolphin imo.
However, I noticed that it seems to be giving a wakelock any time a page has been opened, but the window has not been cleared from the recent apps list (this is all according to BBS).
I was just wondering if other N4 users had experienced this or used this app, and what your opinion on it was. Also, is there a different browser for the N4 you guys would recommend?
danageis said:
Has anybody been using this browser on Nexus 4? I started and I really like it; less hangups than chrome, better interface (I like the disappearing url bar) than dolphin imo.
However, I noticed that it seems to be giving a wakelock any time a page has been opened, but the window has not been cleared from the recent apps list (this is all according to BBS).
I was just wondering if other N4 users had experienced this or used this app, and what your opinion on it was. Also, is there a different browser for the N4 you guys would recommend?
Click to expand...
Click to collapse
I use Boat Browser, supports flash player and loading time is quick imo. Also has a very nice UI.
Go launcher team...
Sent from my Nexus 4 using xda app-developers app
I`m a next browser user. Realy like it, fast and easy to use. And when i browse the web i get a popup message to use tapatalk if the web site support it. I know chrome also got this, but i find it not to work so well.
Yes, i have noticed that it got some wake locks. But not for long, its also possible to exit the app easy from setting menu
Sent from my Nexus 7 using Tapatalk 2
I had been using Next for a while now. But a couple days ago I replaced it with Firefox because Next had trouble downloading some files from Drive. If there was other aberrant behavior it wasn't noticable to me in use.
I use Chrome, but you can try Firefox or Opera. Every browser has its own advantages and disadvantages.
This is an interesting thing I found in my Exynos powered Note 4. The OS itself is fine, there is no lag in opening apps or navigating through TouchWiz. However if you open any apps that use fancy animations, they lag like there's no tomorrow! For example open the Google Play Newsstand app and you'll see that the app is heavy on animations, and they're all extremely laggy. The same goes for the Facebook Groups app. Is this a KitKat thing that will be resolved in the Lollipop update?
ammarmalik said:
This is an interesting thing I found in my Exynos powered Note 4. The OS itself is fine, there is no lag in opening apps or navigating through TouchWiz. However if you open any apps that use fancy animations, they lag like there's no tomorrow! For example open the Google Play Newsstand app and you'll see that the app is heavy on animations, and they're all extremely laggy. The same goes for the Facebook Groups app. Is this a KitKat thing that will be resolved in the Lollipop update?
Click to expand...
Click to collapse
Should be. Because all new-style apps uses new CS-styles. And KitKat doesn't have good optimisation for it. But Lollipop does.
This is pretty much my only real problem on my Nexus 4. My phone just doesn't like the Google Maps app. Every time I start it up, it crashes within three seconds. I noticed that this problem began appearing since I switched to ART when I was on Kitkat 4.4.4. On Dalvik the app runs fine. Somehow waters also look very distorted on my phone no matter what the runtime or Android version it's running. In the logcat it's printing stuff about some libraries (libGLESv2_adreno.so and libandroid_runtime.so).
Has anyone experienced this before and know a fix to this problem? Thanks in advance.
Sent from my Nexus 4 using XDA Free mobile app
Same problem. Started with latest maps update. Still happening with a fresh install of a new rom.
Beat guess is low system memory as lollipop takes more space.