Comment

Don’t take the app that google suggests when typing your search in the play store. Do a real search and then choose opera beta for android. Should work on a tablet

about 23 hours ago on Opera for Android exits beta, ready to take on Chrome

Comment

Awesome “scientific” stuff there ;-) but hey, i have an iphone, had a blackberry and frequently use an android phone. It’s a miracle that i cam still walk, i guess

4 days ago on Apple pulls Bang With Friends hookup app from the App Store

Comment

Yup, his account name is tim_co*k. Not very creative, but it does the jobs

4 days ago on Apple pulls Bang With Friends hookup app from the App Store 3 recommends

Comment

Music matching is only available where music is available and possibly US only i believe

4 days ago on Google Play music matching 2 replies

Comment

I recommend rebooting the phone to get the new play store. Didn’t get it til i did that :)

5 days ago on The real reason there was no Android 4.3

Comment

Klav Kalash

7 days ago on Watch Google I/O 2013 Keynote video streaming here!

Comment

The fact of the matter is that every major player in the business had, at one point in recent years, a golden opportunity to make his messaging solution a de-facto standard, and all of them failed.

There was MSN Messenger, which had tons of users some years ago, but their mobile solution (on Windows Mobile) was just terrible. Google has Talk, which has a few users, uses an open standard and is available on almost any android phone – yet no one really uses it. Then there’s iMessage, which is a great service but limited to iOS. A stupid move by Apple, if you ask me. WhatsApp is an easy service without the need for registering an account, but it has proven to be poorly programmed and vulnerable to attacks, which definitely hurt their reputation. And Blackberry…well this story needs no telling.

Who will win this battle? Whoever gets my messages to the right people, without me having to bother how and on which messenger to send it

8 days ago on BBM coming to Android & iOS 2 replies 2 recommends

Comment

wtf is that? :D

8 days ago on Nice pics you took with your "horrible" Nexus 4 camera

Comment

Pull down the quick settings via a two finger swipe. Then click on the time in the top left corner. This will take you to time&date settings. Try fixing time and date, have a look at all the options (the last one sounds good). if that doesn’t fix it, come back and tell me ;)

8 days ago on Dates not displaying properly. 1 reply 1 recommend

Comment

looks into future while I agree that one-hand-usage on android could be improved and that there is redundancy in some places, I think devices like smart-watches and google glass will make this discussion obsolete in the near future.

Using a smartphone on the go with one hand is never perfect (getting it out of the bag/pocket,pinch-to-zoom, 2/3-finger-swiping, pulling out menus etc.). But what if you don’t have to get out your smartphone for the most frequent scenarios? That’s where smart watches and glass come in, and I’m looking forward to it.

9 days ago on Because of bigger phones, Android could use a redesign

Comment

Well, looks like it’ll be a decent implementation. However, I kind of lost my love for chatheads. I used them quite a bit with facebook messenger, but every once in a while they just get in my way or cover up buttons in an app, and this is starting to annoy me more than having to open the notifications to see my messages…

11 days ago on Chat Heads for any app 1 reply

Comment

I somewhat agree with you, and I’d LOVE to ignore all 2.3. devices. However, it’s hard to tell the guy you’re developing an app for that you won’t support 40% of devices ;-)

20 days ago on Ok Developers...Now can we get some better tablet support? 2 replies

Comment

yeah absolutely. that was kind of my point actually. I know that an experienced developer will have less roadblocks before getting a great UI from GB to Jelly Bean, from 3.5 inches to tablet dimensions. BUT it requires extra work, just like supporting older versions of android.

And while smartphone UI runs fine (but looks bad) on tablets, Apps with min. API >10 will not work at all on Gingerbread devices. That’s why many developers probably choose to get their devices on Gingerbread before developing a tablet specific UI.

But as ZenSoul pointed out above, the problem will solve itself when gingerbread “disappears” from the market. It’s hard to ignore 40% of devices because they’re old and make developing more difficult, but once Gingerbread is below 20%, there’s no reason to care anymore :)

20 days ago on Ok Developers...Now can we get some better tablet support? 1 reply

Comment

The thing is: Google wants us developers to develop one app for all the devices, preferably using fragments and different layouts for different screen sizes and orientations. However, with pre-Honeycomb devices still having a marketshare of almost 50% and having the desire to make an app for 90+% of devices, you cannot use these things easily (they have mostly been added with API 11 btw, so whether you’re going for API level 8 or 10 is not really important in that regard). You have to do so much extra work that it’s just a PITA.

And since android tablets are still pretty rare in comparison to android phones (even to gingerbread phones), it’s probably not the most important thing to make tablet interfaces for developers. They have to spend enough time getting their apps to work on GB.

Don’t get me wrong, i love android, but I’m just working on my first major android app (a web video series app that has to work with 2.3. and up) and i have such a hard time adding a tablet interface. I’m a poor java and android developer, that’s for sure, but I’m certainly not the only one who has to write so much extra code to support both legacy devices and tablets…

20 days ago on Ok Developers...Now can we get some better tablet support? 2 replies

Comment

As some who has just started developing for android, i can tell you that the problem is not necessarily the number of android tablets out there that stops me (and many other developers) from creating beautiful apps with beautiful tablet experiences.
The problem is that there’s still a TON of people on pre-Honeycomb devices, either on 2.2 or 2.3. Those devices have limited support for fragments (VERY important for tablets), many action bar elements and some beautiful UI elements etc. Sure, you can get it to work via support libraries etc. but many developers choose to go the easy way and develop for API level 8 (2.2). This basically gives you huge phone apps on a tablet…

The situation is getting a lot better though, and as soon as the vast majority of users is on 4.0 and up, even I – being the poor dev i am – can create great dynamic interfaces for phones/tablets :P

20 days ago on Ok Developers...Now can we get some better tablet support? 2 replies 1 recommend

Comment

sings I knew U was in trouble when i saw it….

20 days ago on EA Sports' 'Madden NFL' franchise to skip Wii U this year 2 replies 6 recommends

Comment

Yup! Those are great, and boy, i really don’t miss that cable going to my pocket :-D

23 days ago on why are there no decent android earphones with basic remote functionality? 1 reply

Comment

Great. Now let’s forbid Microsoft to promote Office365 in their office products, because their office suite has similar market share and they’re promoting their own service with it. Should link to google apps. #ijustdontgetit

27 days ago on Google offers to advertise rival services to allay EU antitrust concerns 1 reply 15 recommends

Comment

and what should they do other than what they’ve proposed in your opinion?

27 days ago on Google offers to advertise rival services to allay EU antitrust concerns 2 replies 8 recommends

Comment

Yeah, the charging issues you mentioned lead me to believe that your battery might be damaged. If betterbatterystats provides no wakelock issues, and if factory resetting the phone doesn’t work, you pretty much have to contact google to replace it.

29 days ago on Nexus 4 woes :( 1 reply