×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Agora Android Phone Delayed By Glitches

timothy posted more than 5 years ago | from the to-not-get-what-you-don't-pay-for dept.

Cellphones 84

An anonymous reader points out this report at News.com.au which says that "THE first Australian 'Google phone' set to go on sale within weeks has been delayed indefinitely, with the manufacturer Kogan forced to refund early buyers. In a statement released this afternoon, the company said the delay was 'due to future interoperability issues.'The Agora reached a very late stage of development, manufacturing had commenced and we were within days of shipping the product to customers,' company founder Ruslan Kogan said in a statement."

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered

84 comments

Damn it! (1)

Aladrin (926209) | more than 5 years ago | (#26480559)

I noticed the low screen resolution, but didn't think it would really be a problem... In fact, I thought it led to the phone being so cheap.

My current phone is dying, too... I was really looking forward to getting my Agora Pro at the end of the month.

Re:Damn it! (1)

aliquis (678370) | more than 5 years ago | (#26480631)

Glad I held my purchase =P

Both for this reason and because it's always risky to be the first one to buy a thing in case it sucks. It's better to let someone else try it out for you first :)

Re:Damn it! (1)

phatsphere (642799) | more than 5 years ago | (#26480769)

Glad I held my purchase =P

i think there is a refund, so no real damage ... but i hope for an update to this story, i.e. a new delivery date.

Re:Damn it! (3, Informative)

Aladrin (926209) | more than 5 years ago | (#26480815)

phatsphere's correct. All the pre-orders are being refunded within the next 7 days, so none of us are out anything.

I will admit that I was taking a big chance on a company I'd never heard of with a product that was a lot cheaper than I thought it should be. I doubt the next version of the phone will be so cheap, now.

I really wish they'd just sold me the phone... Or given me the option.

Re:Damn it! (2, Insightful)

aliquis (678370) | more than 5 years ago | (#26480969)

I don't think 400 dollar is that cheap, with shipping and Swedish VAT it will become a quite normal price for a decent phone over here, not at all unreasonable.

Cheaper than a phone and 24 months subscription cost for a huge volume subscription? Yes, but not very cheap for the hardware in question.

Re:Damn it! (0)

Anonymous Coward | more than 5 years ago | (#26481717)

It seemed kinda cheap for us. The iPhone/G1/N96 type phones all run AU$800-$1100 so the Kogan for $399 without contract looked like a deal. If you could live without the gps/wifi the lower spec model was $299 I think.

Re:Damn it! (1)

aliquis (678370) | more than 5 years ago | (#26481989)

Oh, it was AUD? I never even thought about it.

(399 + 48) * Australian dollar = 2 438.45127 Swedish kronor
(2 438 * 1.25) + 125 = 3 172.5

That puts it on pair with Sony-Ericsson c902 and Nokia N82 and just below w902 and N95.

Re:Damn it! (3, Informative)

Evanisincontrol (830057) | more than 5 years ago | (#26482011)

It was $399/$299 (for the high-end/low-end models respectively) in Australian. That meant it was ~$250/$190 in U.S. dollars.

Re:Damn it! (1)

Aladrin (926209) | more than 5 years ago | (#26484457)

As the others have noted, it was AUD, not USD. That made the pro $250 plus shipping, which was another $50. $300 for a phone that did (almost) everything I wanted is very reasonable. My last couple phones cost more than that.

Almost: It had no accelerometer. That's a huge feature for me.

Re:Damn it! (1)

aliquis (678370) | more than 5 years ago | (#26484807)

Wasn't it 299 or 399 + shipping (or including australian shipping, cost 48 aud or something for shipping to Sweden in any case, above those 299 or 399. Also I don't remember the extra features in pro but I would had paid 100 more to get them (GPS among other things, right?))

Re:Damn it! (2, Funny)

Anonymous Coward | more than 5 years ago | (#26480759)

My current phone is dying, too...

Please be responsible how you bury it. We have a global cooling crisis here in the US. The gallium arsenide in your cell phone adversely alters the magnetic convection current of the Earth once exposed to air. Please, be responsible.

--Sal Bore

New screen resolution a few days before release??? (2, Informative)

TheSunborn (68004) | more than 5 years ago | (#26480567)

From the annuncement:

Mr Kogan said one of the potential problems was applications with a higher resolution and screen size than what the Agora could handle.
"I now believe that in order to access all the Android platform has to offer, the Agora must be redesigned."

What?? I don't belive that someone a few days before release, find out that they need a higher resolution screen. I only thought the software business were that fucked.

Re:New screen resolution a few days before release (5, Insightful)

Aladrin (926209) | more than 5 years ago | (#26480781)

Why don't you believe it? I see 2 different ways this could happen:

1) Someone finds a few apps that don't work at low res at all... Good apps like Google Earth or something.

2) The programmers assure him that it can be handled right up until the end, when they are forced to admit they can't do it after all because they finally found the fatal flaw in the plan.

As a programmer, I've had both things happen to me during a project. The first is just oversight and the second is usually due to some asinine quirk in the API that can't be worked around.

Re:New screen resolution a few days before release (4, Funny)

Oswald (235719) | more than 5 years ago | (#26481003)

I think you just said, "Of course this can happen -- because even though its a device manufacturer, they still have to deal with the fucked up world of software." Nice rejoinder.

Re:New screen resolution a few days before release (3, Insightful)

itsdapead (734413) | more than 5 years ago | (#26481145)

The programmers assure him that it can be handled right up until the end, when they are forced to admit they can't do it after all because they finally found the fatal flaw in the plan.

Or, alternatively, 3 days before shipping, the Pointy Haired Boss is finally forced to accept that the "political and economic realities" he's been trying to explain to the programmers for the last 3 months really are less important than those silly, geeky "laws of physics" which the programmers keep babbling about, and that all the unpaid overtime in the world won't produce a software patch that puts more pixels on the LCD.

Re:New screen resolution a few days before release (2, Insightful)

AmberBlackCat (829689) | more than 5 years ago | (#26491695)

Regardless of whose fault it is, they did one thing right that no American company or Sony would ever do. That is, after they realized their product wasn't ready, they actually went back to the drawing board instead of shipping the thing anyway.

Re:New screen resolution a few days before release (1)

jcostantino (585892) | more than 5 years ago | (#26482127)

Google Earth? You're thinking of the iPhone, that isn't out for Android.

Re:New screen resolution a few days before release (0)

Anonymous Coward | more than 5 years ago | (#26483573)

But Android is open, and you can change the API and contribute the code back, so it must be the former option, oversight.

Re:New screen resolution a few days before release (1)

Aladrin (926209) | more than 5 years ago | (#26484553)

You're ignoring the fact that everyone is going to want Random App X to work on the phone out of the box. If they have to modify each app to work on their special copy of Android, that would be unacceptable to most of their customers.

Re:New screen resolution a few days before release (1)

CarpetShark (865376) | more than 5 years ago | (#26480971)

Considering that apple sold ibooks with 1024x768 resolution in the early OS X days, when that was about enough real estate to get a console window and a few icons on, I can believe it easily. The question for me is, which of these happened:

a) Google told them that they needed higher res, and they ignored it. Then they finally realised Google were right.

b) Google didn't specify android's resolution requirements highly enough, and devs went ahead and created an ad-hoc standard with the res they needed to make decent apps.

The first would be a bad sign for the phone maker. The second would be a bad sign for the whole platform.

Yeah, I could look up the android specs and see which it is, but frankly I don't care that much about android. Not yet, anyway.

Re:New screen resolution a few days before release (0)

Anonymous Coward | more than 5 years ago | (#26481241)

Considering that apple sold ibooks with 1024x768 resolution in the early OS X days, when that was about enough real estate to get a console window and a few icons on, I can believe it easily.

You do realize that *everything* that the first few iterations of OS X did fit perfectly fine into that 1024x768 resolution (not sure about the last few versions). That's why it was an officially supported resolution. It's similar to how XP and Vista have minimum requirements of 800x600. This sounds like Google has set minimum application resolution requirements as well as minimum device resolution requirements. It sounds like Agora built their phone to the min app resolution spec.

Re:New screen resolution a few days before release (0, Flamebait)

jimicus (737525) | more than 5 years ago | (#26481439)

It's similar to how XP and Vista have minimum requirements of 800x600.

Truly, spoken like a man who has never tried to run a recent Microsoft OS at the minimum resolution.

Re:New screen resolution a few days before release (0)

Anonymous Coward | more than 5 years ago | (#26481719)

Oh, no doubt it sucks. But at least all the system dialogs and buttons fit on the screen.

Re:New screen resolution a few days before release (1)

itsdapead (734413) | more than 5 years ago | (#26481301)

Considering that apple sold ibooks with 1024x768 resolution in the early OS X days, when that was about enough real estate to get a console window and a few icons on, I can believe it easily.

I've just tried and you can fit 4 OSX terminals on a 1024x768 display. If a slashdotter can't do it with 4 parallel bash sessions it isn't worth doing.

When I were a lad, we ran GUIs on 640x256 in 256 colours and we was grateful for it. Heck, people run Linux/Gnome on EEEPC 700s!

Re:New screen resolution a few days before release (1)

thegoldenear (323630) | more than 5 years ago | (#26482787)

Heck, people run Linux/Gnome on EEEPC 700s!

Yeah but not everything works. Thunderbird & Lightning is unusable.

Pete Boyd

Re:New screen resolution a few days before release (0)

Anonymous Coward | more than 5 years ago | (#26485495)

Try Thunderbolt & Lightning... supposed to work better! :-p

Re:New screen resolution a few days before release (1)

itsdapead (734413) | more than 5 years ago | (#26486993)

Yeah but not everything works. Thunderbird & Lightning is unusable.

I've used Thunderbird on an EEE 701 and I think "unusable" is going a bit too far. Main problem ISTR is that, for the account setup dialogues, you need to know the alt-drag trick to pan the window around the screen - but once it was set up it was OK. Evolution on EasyPeasy [geteasypeasy.com] <SideshowBob>(shudder)</SideshowBob> is the same.

Of course, if Asus hadn't drunk the Kool Aid and lost interest in Linux on the EEE, tightening up the dialogue boxes on the key apps would hardly take a Manhattan Project.

Where's the surprise? (1)

TheMeuge (645043) | more than 5 years ago | (#26481513)

When I first saw the announcements about this phone... from a manufacturer nobody heard of, with a very rapid release schedule, and a set pricing scheme, but only a 3D rendering of the product, to me it screamed "scam". Now, I couldn't say whether it was a scam that was aimed at customer money, or investor money, but the outcome does not surprise me at all. After all, if it sounds too good to be true, it probably is.

Re:Where's the surprise? (0)

Anonymous Coward | more than 5 years ago | (#26481563)

The phone was demonstrated. Either Engadget or Gizmodo saw it, can't remember which, and published photos of the actual device.

Re:Where's the surprise? (0)

Anonymous Coward | more than 5 years ago | (#26481859)

Actually I don't think they ever got their hands on one, it was more a spec review. I guess to photos must have been provided by Kogan.

Re:New screen resolution a few days before release (1, Funny)

Anonymous Coward | more than 5 years ago | (#26485041)

>> the Agora must be redesigned

And possibly renamed to "Depois". :-)

Good... (1, Troll)

tcdk (173945) | more than 5 years ago | (#26480575)

... nice to see somebody who don't just ship the product and then hope to fix issues with later software updates. I was going to mention the IPhone here, but I actually couldn't think of a phone that didn't have issues on initial release. So I won't.... Oh, I guess I already did...

Re:Good... (0)

Anonymous Coward | more than 5 years ago | (#26480613)

Did you really want to kill your karma/flamebait that bad?

Should we remind you of the inability of people to even use their phone for about 3 days after purchase with the iphone, or the pricing fiasco?

Are you an iRetard?

Re:Good... (0)

Anonymous Coward | more than 5 years ago | (#26481409)

Wow. Aren't we angry? I had no intentions of trolling anybody. That you, and whoever modded me troll, thinks that was what I was doing, speak volumes about the anger levels out there....

This is why I support Microsoft (-1)

Anonymous Coward | more than 5 years ago | (#26480667)

Fighting the evil G$$Gle empire!

Re:This is why I support Microsoft (0)

Anonymous Coward | more than 5 years ago | (#26480727)

giigle? he he he

Re:This is why I support Microsoft (1)

orclevegam (940336) | more than 5 years ago | (#26481617)

Haven't you heard? They're not evil, they're morally ambiguous. Remember, when picking your corporate overlord, pick the low-evil choice, because if you don't they'll know about it (and where you live... and oh, I see you're doing a search for... my, you really should have that looked at by a professional).

Real Story? (3, Insightful)

Idiomatick (976696) | more than 5 years ago | (#26480723)

What's the real story? Nobody goes into production without atleast you know having 1 prototype... They could have tried it first... It like a pretty serious obvious issue if it causes indefinite delays...

Re:Real Story? (2, Insightful)

Anonymous Coward | more than 5 years ago | (#26480777)

something is the matter. The original design of the phone was OK'd for production and no one ever took a look at what everyone else's minimum screen size/resolution or checked the spec sheet for max supported resolution? Engineers should never have overlooked something so obvious. This smells like fiasco to me. If it was an "honest" mistake, I really hope no one is dumb enough to buy one.. A company that fucked up will certainly not be responsible with my money.

Re:Real Story? (1)

morgan_greywolf (835522) | more than 5 years ago | (#26481021)

Engineers should never have overlooked something so obvious.

I don't think it was overlooked. Based on what this guy said [slashdot.org], I think maybe something changed at the last minute. Maybe they couldn't get the screens they originally spec'd and changed to an alternate source just before production? I've heard that this happens a lot in the cellphone/smartphone business.

Re:Real Story? (0)

Anonymous Coward | more than 5 years ago | (#26481235)

You actually thought that AC post was from someone in this company? Hahaha oh wow you're fucking gullible.

Re:Real Story? (1)

morgan_greywolf (835522) | more than 5 years ago | (#26482263)

Not necessarily, no, but I acknowledge the possibility since the story was submitted an anonymous reader. Maybe the submitter and that poster weren't the same guy, but even so, what does the AC have to gain by lying? Nothing that I can see other than maybe he gets his jollies off misleading other people.

As always, you are expected to take everything you read on the Intarwebs with a grain of salt.

For all I, you and the rest of Slashdot knows, Kogan is lying about the reason it is issuing refunds and delaying manufacturing.

Re:Real Story? (0)

Anonymous Coward | more than 5 years ago | (#26481033)

Ok if you'd advanced purchased or you've bought stock it's 'your money'. However if you buy over the counter or your product is delivered then your money becomes their money.

I follow the rest of your argument, but given that the company is refunding purchasers money (ie: being responsible), I fail to see how you came to the conclusion that the company would not be responsible with 'your' money?

Re:Real Story? (0)

Anonymous Coward | more than 5 years ago | (#26481207)

what I meant to convey is that as a hopeless consumer I need to buy a great many things, but if at all possible, I try to buy products from companies that might do something productive with my money, rather than make some sort of horrible decision like pull a product shortly before launch because of the "small" oversight of minimum screen requirements. If they re-release a new version in the future, I'd feel the fool if I gave them a chance to piss away money that used to be mine on hopeless endeavors.

nested quote FAIL (here with substitution) (0)

Anonymous Coward | more than 5 years ago | (#26480779)

An anonymous reader points out this report at News.com.au which says that

[[THE first Australian ((Google phone)) set to go on sale within weeks has been delayed indefinitely, with the manufacturer Kogan forced to refund early buyers. In a statement released this afternoon, the company said the delay was ((due to future interoperability issues.)) The Agora reached a very late stage of development, manufacturing had commenced and we were within days of shipping the product to customers,]] company founder Ruslan Kogan said in a statement.]]

Figured it wouldn't come out on my birthday. (1)

kiehlster (844523) | more than 5 years ago | (#26480871)

I have to say January 29th has had quite the jaded history [history.com] including the death of Robert Frost and GWB's declaring the "axis of evil". At least we can celebrate the inception of the first baseball hall of famers. Now add to the list, "this is the day the agora android was suppose to release, but failed citing future interoperability."

how it happened (5, Interesting)

Anonymous Coward | more than 5 years ago | (#26480909)

A couple of guys came from Google. Our CEO had been waiting for them by the door. someone says they went straight to a meeting room and were there for less than 20 minutes. no one saw them leave, but as soon as they were gone our CEO called a meeting. He looked very pale. he said: "I've halted the production on the Android phones." he said we were not to ship any of the products that have already rolled off. he told us to cancel all orders and refund all pre-orders. then he left the building with the marketing director.

Our CEO has not been back since then. This must be big.

Re:how it happened (1, Funny)

Anonymous Coward | more than 5 years ago | (#26480997)

Funny thing is... one of those Google guys reportedly threw a chair.

Re:how it happened (0)

Anonymous Coward | more than 5 years ago | (#26481337)

Yeah, I believe that ANONYMOUS COWARD actually works for Kogan the manufacturer of said phone.

Sarcasim overload. Going down for reboot... ... system rebooted.

Not only that but he gives sufficient evidence for the CEO to track him down to a group of people at a meeting.

Real likely.

Sarcasim overload, going down for reboot...

Re:how it happened (1)

Zebedeu (739988) | more than 5 years ago | (#26481817)

Man, you never know when 2 guys from Google come out of nowhere and have a 20-minute meeting with your CEO and your project gets canned.
It's all so mysterious that you don't even see them leave!

And it could happen anytime!

Buy Microsoft.

Re:how it happened (0)

Anonymous Coward | more than 5 years ago | (#26482043)

This sounds like something that could be marketed. I've been on plenty of projects that I've wished someone would can. Between the developers I'm sure we could scrape together $1000 to pay a couple guys from Google to stop by and cause the CEO to kill the project.

Re:how it happened (1)

Zebedeu (739988) | more than 5 years ago | (#26482193)

1000$ isn't a lot, if you consider paying those two guys (they are expensive because they are actually ninjas who are able to leave undetected), travel expenses, plus the time which is 20 minutes + however long it takes the guys to get there.

On the other hand I'm sure that some companies with deep pockets would love to be able to cancel their rivals' projects, so you might be onto something here.

Man, we could be rich!

Re:how it happened (1)

youngdev (1238812) | more than 5 years ago | (#26482851)

Are you really a Kogan employee? My suspicion of this post is almost overwhelming. If so give us more details.

Re:how it happened (1)

Locutus (9039) | more than 5 years ago | (#26486185)

ya, Microsoft purchased Google. But really, wouldn't this make more sense if those two guys were MSiBs? That CEO was already quite friendly with Steve Ballmer so it was quite a surprise they'd announce an Android phone in the first place.

LoB

Re:how it happened (1)

Yfrwlf (998822) | more than 5 years ago | (#26490987)

If this is true, and somehow Google decided not to allow Android on the phone (without forking/renaming it or whatnot), for whatever reason, it's too bad they didn't pick something else to put on it like OpenMoko or whatnot. They obviously already had the drivers for it, so there wouldn't have been an issue there.

Regardless, it's sad that programs aren't being programmed to be flexible enough to support most any screen resolution. When working with phones, being able to support small resolutions should be a topic of interest.

They werenâ(TM)t very experienced with the re (1)

Rick Richardson (87058) | more than 5 years ago | (#26480935)

"I emailed the company about this charge and received confirmation that it was indeed not a scam and the device was going to be shipped in January. It looks like they did try hard to get a device out, but they werenâ(TM)t very experienced with the requirements and were designing a device that did not fit the minimum specs for an Android phone."

Why not release it? (4, Insightful)

Lord Byron II (671689) | more than 5 years ago | (#26481055)

Release it and then just patch it repeatedly for months on end, fixing some things and breaking others in the process. Eventually, say the phone is past the end-of-life and instead of fixing anything, suggest that your customers buy your newest phone.

This seems to work for most other businesses.

Re:Why not release it? (2, Informative)

Tamran (1424955) | more than 5 years ago | (#26481075)

What kind of software patches increase screen resolution?

Re:Why not release it? (1)

gEvil (beta) (945888) | more than 5 years ago | (#26481461)

What kind of software patches increase screen resolution?

How dare you question him!?! Can't you see that his UID is less than half yours? He clearly knows more about this stuff than you.

Re:Why not release it? (2, Informative)

Cysgod (21531) | more than 5 years ago | (#26481959)

What kind of software patches increase screen resolution?

How dare you question him!?! Can't you see that his UID is less than half yours? He clearly knows more about this stuff than you.

Clearly. Through empirical evidence we can see that the cutoff is not half your UID, but an order of magnitude less.
_..-* The More You Know

Slightly more seriously, who puts something like a phone up for sale without testing with some engineering prototypes first? And then still has not tested with prototypes before going to manufacture?

Presuming gross ignorance rather than malice as the culprit here seems to stretch credibility some. Does Australia have class-action lawsuits? If so, several lawyers will probably make some money on this.

Re:Why not release it? (1)

gEvil (beta) (945888) | more than 5 years ago | (#26482481)

Clearly. Through empirical evidence we can see that the cutoff is not half your UID, but an order of magnitude less.
_..-* The More You Know


Wait a second. Are we saying that Taco is omniscient?!? *shudder*

Re:Why not release it? (1)

Cysgod (21531) | more than 5 years ago | (#26484697)

Clearly. Through empirical evidence we can see that the cutoff is not half your UID, but an order of magnitude less.

_..-* The More You Know

Wait a second. Are we saying that Taco is omniscient?!? *shudder*

Unfortunately for him, the counter can overflow.

Re:Why not release it? (0)

Anonymous Coward | more than 5 years ago | (#26488767)

well, firstly if you release the phone with software running at a "lower than max" software resolution (upscaled to the screen) you can release a patch that "unlocks the screen's true potential" and then you can have another patch that gives you a desktop that's bigger than the screen but downscales using some pixel blending techniques, maybe you could call that the "eXtended View" patch.
Finally you can patch so that there's a "eXtended Virtual Rez" mode that has a software resolution bigger than the screen that you can scroll/page around on.

None of these software resolutions have to be visible to the application running, just the phone OS.

Re:Why not release it? (1)

recharged95 (782975) | more than 5 years ago | (#26484863)

According to the FTA, when does high resolution apps create "interoperability" issues? When I hear that word, I'm think ok, MS Dll vs. elf or XML vs. Binary (hard problems but can be fixed). And when does high resolution apps stop a phone's basic function? Android has no minimium resolution requirements, maybe some apps do, but not the OS.

.

ok, so it can't run Google Apps or Google Earth, you have the source, prevent a use to start those apps (or diasble/remove them) and write your own email client and so forth, or have a group of F/OSS guys do it for you in the Android Market or go the webOS route and push the users onto the browser. That is a no brainer and exercising the true benefit of opensource. I'm sure the details of this decision will get this guy in legal hot water.

do not want (0)

Anonymous Coward | more than 5 years ago | (#26481105)

I didn't want one anyways, with the iPhone available and all.

Re:do not want (0)

tolan-b (230077) | more than 5 years ago | (#26481281)

That's a useful and insightful comment, I'm sure we'll all sleep easier now that we know something you didn't want to buy.

phew!

Re:do not want (0)

Anonymous Coward | more than 5 years ago | (#26483693)

...interesting perspective considering we are discussing the failure of a phone nobody wants to buy. har har har

Speculation: cutting their losses (1)

colonslash (544210) | more than 5 years ago | (#26481555)

My guess is that they feel their product wouldn't be competitive with the soon to be released in Australia G1, and they don't want to support just a handful of customers- that doesn't give them economies of scale.

I've made an Android app, and I was dreading trying to make it usable for the smaller screen (although I have found the Android layout model very flexible).

Re:Speculation: cutting their losses (0)

Anonymous Coward | more than 5 years ago | (#26482029)

I dunno maybe, but I think that they were targeting a totally different price point, so they still could of been very competitive.

The G1 rumours only started this week with no confirmed deal, but i'll bet my arse they'll be hideously expensive or contract only if it does happen. You just know they are going to gouge us six ways...

Aussies (1)

revjtanton (1179893) | more than 5 years ago | (#26482329)

Well Australia was a prison colony...maybe they were just sticking to their roots and trying to rip off Europeans and nerdy American types using T-Mobile or AT&T? Either way I blame Hugh Jackman for this. WOLVERINE!!!!

Maybe the hardware is just agoraphobic (2, Funny)

ruiner13 (527499) | more than 5 years ago | (#26482505)

And doesn't want to go outside where it can meet up with nice hot little software numbers. Just maybe.

Just plain bad business (2, Insightful)

recharged95 (782975) | more than 5 years ago | (#26484675)

This will kill Kogan's company.

.

He brings back the old x86 days when off-brand companies like his tout 'cold fusion' and deliver vaporware.

.

Really a total disservice to the F/OSS community. I was worried about Koolu, but because they published their modifed stack and distro it showed commitment and was acceptable for them to be late to delivery (and they still are late though after promising a Dec release date). Kogan has done no such thing, just demo-ing a phone mockup at trade shows...

.

Kogan, having a closed demo strategy (no beta testers?), holding to all the press releases, tech details and tooling around with a single phone that for all I know was showing a flash app is asking for some major b*tchslapping from the community. And now abrupt about the details of shutting down production & refunds, providing zero details is an insult to the Android community. If Google was involved and led to a legal issue, okay, mentioned it at least, but if it was technical, the community deserves to know the details.

This is not good for the Android community and [we] sure better find out why production was stopped. Was this:

  • A h/w technical issue? (resolution problem? okay, postpone final and release a handful in beta! This is where the F/OSS community can help...)
  • A software issue? (releasing it with RC28?, or some huge bug?, okay, publish YOUR Android portion of your stack and we'll [the community] will fix it! F/OSS is all about helping or at least free advice)
  • A design issue? (you guys forked the Android stack?--big no no at this time).
  • A legal issue? (hackibility, Google, MS)?
  • A F/OSS issue? (not following the license)
  • Lying about features? (ok, now you screwed up!)
  • Vaporware that would damage the Android brand?

Resolutions (1)

CopaceticOpus (965603) | more than 5 years ago | (#26484877)

The page with details about the phone is still in Google's cache [74.125.95.132].

The Agora display specs: "2.5-inch TFT-LCD flat touch-sensitive screen with 262K QVGA (320 X 240 pixel) resolution."

This is a significant drop from the G1: "3.2 in (81 mm) HVGA (480×320) (180 ppi) 65K color capacitive touchscreen."

Still, if there is a minimum resolution for Android, you'd think that would have been discovered as an issue long before the manufacturing stage. Perhaps the problem is that app developers have assumed that any phone released after the G1 would have matching or better specs.

Re:Resolutions (1)

Microlith (54737) | more than 5 years ago | (#26485105)

Perhaps the problem is that app developers have assumed that any phone released after the G1 would have matching or better specs.

I'd certainly hope that all subsequent phones released after the G1 meet or exceed its specs. Random, weird screen resolutions and wild hardware differences only promise to stick Android with the same issues Windows Mobile suffers from having PC-like diversity in hardware: app development and support becomes a nightmare.

This is one reason that developers have jumped on the iPhone bandwagon, it's like developing for a console where all the hardware is reasonably expected to have the same features.

Re:Resolutions (1, Interesting)

Anonymous Coward | more than 5 years ago | (#26492965)

I'm working day to day with the Android SDK and Emulator. The Eclipse plugin ships configured for QVGA-L (320x240) and QVGA-P (240x320) in addition to the HVGA resolutions.

I have wondered if I really needed to worry about the lower rez models, this is another thing helping me lean in the direction of HVGA or higher. Wonder what else will happen in this space this year.

Re:Resolutions (0)

Anonymous Coward | more than 5 years ago | (#26494893)

The page with details about the phone is still in Google's cache [74.125.95.132].

The Agora display specs: "2.5-inch TFT-LCD flat touch-sensitive screen with 262K QVGA (320 X 240 pixel) resolution."

This is a significant drop from the G1: "3.2 in (81 mm) HVGA (480×320) (180 ppi) 65K color capacitive touchscreen."

Still, if there is a minimum resolution for Android, you'd think that would have been discovered as an issue long before the manufacturing stage. Perhaps the problem is that app developers have assumed that any phone released after the G1 would have matching or better specs.

hehe... look at the last image in the set - the screen cuts off the image.

so Microsoft paid them $10 million to tie them to (1)

Locutus (9039) | more than 5 years ago | (#26485001)

Windows. ;-) Didn't I read that this telecom was already in bed with Microsoft and even had the CEO or some other big-wig dissing on Google and Android?

Money talks so don't put it out of your head that there wasn't some kickbacks from Microsoft to keep them tied to Microsoft. We know Microsoft has bank accounts and/or budgets setup just for funding these kinds of things.

LoB

Can you say Woot.com (0)

Anonymous Coward | more than 5 years ago | (#26485059)

Wonder how many of these have already been made, would be awesome for woot offs.

Fail. (1)

cyn1c77 (928549) | more than 5 years ago | (#26493011)

"THE first Australian 'Google phone' set to go on sale within weeks has been delayed indefinitely, with the manufacturer Kogan forced to refund early buyers. In a statement released this afternoon, the company said the delay was 'due to future interoperability issues.'The Agora reached a very late stage of development, manufacturing had commenced and we were within days of shipping the product to customers,' company founder Ruslan Kogan said in a statement."

Future interoperability issues? What the fuck does that mean? That it won't run Duke Nukem Forever?

Let me translate: We advertised a vaporware product and then took money from a lot of people to build a it. Then we designed the phone. Then we tried to build it and realized we didn't have a clue.

Fail.

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...