>
New Topic
>
Reply<
Esato Forum Index
>
General discussions >
Rumours
> Dell developing Google Android handset
Bookmark topic
Residentevil Posts: > 500
It is not about efficiency, customer satisfaction or functionality. It is who makes money
--
Posted: 2008-05-19 07:00:48
Edit :
Quote
I just want to see how it all turns out for Google. By it's open-source nature, it seems very messy. Device driver issues, UI inconsistencies, lack of powerful yet CPU efficient apps, etc. Seems great for techies, but, off-putting to non-technical users. I'm sure these issues will be addressed, but how? Since other platforms already have access to Google app API's (such as maps/search), what is Android's trump card?
--
Posted: 2008-05-19 08:31:30
Edit :
Quote
Licensing from the short term perspective. But regarding long term benefits, its a fact that the future of computing is in handhelds, so this is google's first step into the world of handhelds.
Android is'nt on top of a VM, android is the name for the package, you have a Linux kernal with a Virtual Machine on top of it.
Of course the Dalvik Java on the Android is a bit slower than native, but it can be implemented well eg: Blackberry uses a complete Java application. Google have made certain modifications to the JVM to make it a lot more efficient than the usual JVM.
Video of Quake on an underclocked MSM7200 better than any WIndows phone out there.
http://www.gsmarena.com/android_os_shows_new_tricks-news-446.php
--
Posted: 2008-05-19 09:56:16
Edit :
Quote
On 2008-05-19 08:31:30, WhyBe wrote:
I just want to see how it all turns out for Google. By it's open-source nature, it seems very messy. Device driver issues, UI inconsistencies, lack of powerful yet CPU efficient apps, etc. Seems great for techies, but, off-putting to non-technical users. I'm sure these issues will be addressed, but how? Since other platforms already have access to Google app API's (such as maps/search), what is Android's trump card?
Are you talking about Android or WM? Inefficent apps and missing drivers sound more WM to me than Android
. Android is actually more efficent from an end user point of view, more security and no resource leaks.
OpenSource, messy LOL, what a bloody joke
! What UI inconsistencies?, and I fail to understand how you came to that conclusion without seeing a final product. How do you solve driver issues? by writing the drivers, thats upto the manufacturer and not your problem or mine. But if I wanted to port Android for a device not running android then I'd have to program the drivers.
If Maps and search is all you use in Google thats fine, use something else then. There are quite a few users who would like VOIP via Gtalk, there gmail, google docs etc..
ANdroid is targeted more towards the end user as Symbian is, its meant to give an intuitive experience to the user, and the best part is the modders to can have their fun with it. So in reality its targeting a whole lot more users than any single platform till date. But that is to be seen if the sources are released or not.
BTW The reason Quake plays on a 300Mhz MSM7200 processor on Android is because:
1. It is less resource hungry than WM, a 400 Mhz processor of the smae MSM7200 cannot play quake at 30fps more like 9-15fps.
2. It ACTUALLY has the drivers working
[ This Message was edited by: aksd on 2008-05-19 09:11 ]
--
Posted: 2008-05-19 10:02:11
Edit :
Quote
On 2008-05-19 10:02:11, aksd wrote:
Are you talking about Android or WM? Inefficent apps and missing drivers sound more WM to me than Android
. Android is actually more efficent from an end user point of view, more security and no resource leaks.
OpenSource, messy LOL, what a bloody joke
! What UI inconsistencies?, and I fail to understand how you came to that conclusion without seeing a final product. How do you solve driver issues? by writing the drivers, thats upto the manufacturer and not your problem or mine. But if I wanted to port Android for a device not running android then I'd have to program the drivers.
If Maps and search is all you use in Google thats fine, use something else then. There are quite a few users who would like VOIP via Gtalk, there gmail, google docs etc..
ANdroid is targeted more towards the end user as Symbian is, its meant to give an intuitive experience to the user, and the best part is the modders to can have their fun with it. So in reality its targeting a whole lot more users than any single platform till date. But that is to be seen if the sources are released or not.
BTW The reason Quake plays on a 300Mhz MSM7200 processor on Android is because:
1. It is less resource hungry than WM, a 400 Mhz processor of the smae MSM7200 cannot play quake at 30fps more like 9-15fps.
2. It ACTUALLY has the drivers working
Maybe I'm not understanding what is meant by "open-source". When I hear open-source, it reminds me of 10 contractors trying to build the same house
. Are we talking open (source) to all of the Google partners or open to all of the bedroom programmers? I was assuming the latter. Therefore, I was saying
messy in terms of the OS code coming from so many different authors with their own ideas of how the UI should be. Is there going to be a governing body for "quality control?"
Aren't all of Google app API's available to other platforms? I was just wondering what sort of exclusive features would be on Android that would compel manufacturers to adopt it in their hardware.
By inefficient, I mean the whole Java to Android to Chipset translations that have to take place. Or is one of those steps compiled instead of translated? I mean, all else being equal, compiled code is always faster than translated code, right?
Thanks for answering,
sorry to be so lengthy
--
Posted: 2008-05-19 11:53:37
Edit :
Quote
Those "bed room" programmers are the ones who'll be getting WM7 on the Xperia, if its possible. THose bedroom programmers are the ones releasing apps worth releasing not the manufacturer remember that. The source code is expected to be open to all.
Suppose HTC and Samsung release two Android phones, they're running a standardized OS by Google, but it can be altered with the usual apps etc.. or particular hardware optimization and software localizations, just like WM, BUT if theres an issue with the software say the P990 was android and the memeor leak was'nt being addressed by SE then you'd have a few hundrer devs working on fixing it, wheather you want to install the fix or not is upto you. Just like any other software. The "bed room" programmers over at xda-dev have actually made WM phones worth owning, there are fixes for SDHC on devices that do not have it, finger friendly apps and the works.
Once you buy your X1 trust me, its those bed room programmers you'll be thankful to.
Theres no such thing as translation, Java program is complied and then byte code is
interpreted, but the Dalvik VM works a little different you can actually run multiple instances of the VM which is not possible on a JVM, read up on google about it or you can look
http://www.dalvikvm.com/ and here
http://en.wikipedia.org/wiki/Dalvik_virtual_machine for a little info. The slight delay wont even be noticable, like a blackberry, nobody says a blackberry is slow now do they? And the entire OS is in Java
Like I said, Android is something special because it is opensource and because of its strange Java implementation. Its extremely resource efficent therefore you're going to have an extremely quick phone, the interface is quite friendly and theres going to be more choice for the end user, more choice is actually better for the market, it keeps the market on its toes, if any other manufacturer was on the same level as Nokia from a tech point of view we would'nt have this hardware lull that we've been having for the bast few months.
--
Posted: 2008-05-19 15:44:55
Edit :
Quote
...Suppose HTC and Samsung release two Android phones, they're running a standardized OS by Google, but it can be altered with the usual apps etc.. or particular hardware optimization and software localizations, just like WM, BUT if theres an issue with the software say the P990 was android and the memeor leak was'nt being addressed by SE then you'd have a few hundrer devs working on fixing it, wheather you want to install the fix or not is upto you.
This was where I was not understanding--of those "100 devs" working on the fix and assuming they are all taking different approaches to the fix, wouldn't there be a potential for "breaking" the system because a particular software may not be compatible with one of the particular fixes? Or would the 100 devs all agree on the best fix and only implement that 1 fix?
Also, I didn't mean bedroom programmer in a negative way. I just meant the guys that don't work for any of the participating corporations...the do-it-yourself-ers.
Thanks
[ This Message was edited by: WhyBe on 2008-05-19 15:50 ]
--
Posted: 2008-05-19 16:19:58
Edit :
Quote
They'd all work together through Mailing lists, you can check out the Android Mailing list as an example. Or sometimes 1 person fixes it and another builds up on it so on....but the reason for making things opensource is to have more developers working on it, its always benefical to have several perspectives in solving a problem.
Sometimes, those bedroom programmers are secretly working for the parent company
--
Posted: 2008-05-19 16:26:02
Edit :
Quote
Gotcha, thanks.
--
Posted: 2008-05-19 20:46:07
Edit :
Quote
@aksd,
i was unaware that you do not like to smile.
--
Posted: 2008-07-12 21:59:24
Edit :
Quote
New Topic
Reply
