Hi everyone,
This is my first post, though I have been lurking for a while now. Does anyone know if google earth is coming anytime soon to android? The code is out there to make it available, the guys who were developing Enkin had a working client before they were mysteriously silenced by corporate confidentiality agreements.
Aleks
N.B. Thanks to everyone who has posted before for all the info on how to gain root and also to JF for his top quality builds.
i'm going to just (guess) say that google WILL make an official google earth app.
if they made one for the competing phone - iphone - then there is no way they wouold just skip over android. i'd say we can probably expect an android google earth app by summer.
Lurking is good! You gain knowledge of how the forum works. UK lurkers are better!
Anyway, from what I saw, Google Earth will be in the cupcake build, however that could just be me. If anyone will release it, it will be google, and most likely in an upgrade. It might be a push with the G1s graphics accelleration, and wouldn't work amazingly with the slow 3G data connection, I think google will do it eventually, if not in cupcake, then their next major build (cheesecake?, Vanilla Crazy cake?)
And yes, I made a portal reference that wasn't (as) obvious!
not my artical just found it orig web page
androidandmeDOTcom/2010/04/news/android-2-2-is-coming-what-features-do-you-want/
replace dot = .
Android 2.2 is coming. What features do you want?
By Taylor Wimberly on Apr 20267
The majority of Android phones are still running an outdated firmware, but that hasn’t slowed Google from advancing their mobile operating system. Everyone knows the next version of Android (codenamed Froyo) is on the way and the rumors (1, 2) are beginning to pick up that the Nexus One will receive it soon.
Based on the data from our analytics reports it appears Google has already begun testing on their next firmware – Android 2.2. Google engineers have routinely given codenames to future builds of Android (Eclair, Froyo, Gingerbread, etc.), but they don’t receive a point release till they are finalized and nearing distribution.
We have shared this reporting data before and people are always quick to point out that it can be easily faked, but I have spoke with additional sources familiar with the matter who confirmed Android 2.2 is currently being tested.
The feature set for Android 2.2 was frozen long ago, but it remains mostly unknown. Google decided last year that they would no longer publish public roadmaps for future versions of Android. Based on the information we can gather, it appears Android 2.2 will mainly focus on performance enhancements.
Some of the rumored features for Android 2.2 include:
•JIT compiler
•Free additional RAM
•OpenGL ES 2.0 enhancements
•Flash 10.1 support
•Fixed problem with “crazy screen” / Resolution of cross multitouch
•Activation of Color Trackball
•Enable FM radio
Some of these features are plausible and others we have no clue.
The JIT compiler has already been confirmed by Google and we expect to find out new details during Google I/O. Android engineers will be leading a discussion that informs devs how to test and tune their apps to work with the new compiler.
Additional free RAM should come thanks to the new Linux kernel being used in Froyo. Google is moving from 2.6.29 to the newer 2.6.32 which makes it possible to address the extra RAM. This has already been done in custom ROMs like CyanogenMod so expect this feature for sure.
I’m no expert on OpenGL, but it has long been rumored that Froyo (or a future build) will add new APIs to the Android NDK which will let Java devs have full access to the OpenGL ES 2.0 library.
Flash 10.1 is coming in the first half of the year. It is entirely possible it could be tied to a future Android firmware and be included with an OTA update.
We have already addressed the HTC touch sensor issues. It sounds like a future software update could be used to clean this up a little.
Multicolor trackball notifications are definitely coming. Android hackers like ChainsDD have already unlocked this feature for users of custom ROMs. Google advertised the multicolor trackball during its launch of the Nexus One, but the feature was cut from the final Android 2.1 build.
When it comes to the FM radio, I have no idea. Other HTC phones on a similar Snapdragon platform (Desire and Incredible) include the FM radio so it’s not out of the question that the N1 has it too.
I spoke with Google’s Eric Tseng during CES and he told me there were many secrets left in the Nexus One that we would discover later.
When is it Android 2.2 coming out?
Circle May 19th on your calendar. This is the opening day of Google I/O and I’m anticipating the release of Android 2.2 (and maybe the Flash 10.1 beta) will be tied to this event. Google has provided every developer attending the event a free Droid or Nexus One, so it is possible to see a simultaneous release on both devices.
I’m really curious how first generation devices are going to play with this release. We are expecting most phones to receive Android 2.1 this month, so it will be interesting to see how Froyo fits in. Some of the Android engineers have been talking about Froyo on the Google boards and it is unclear if the HTC Dream and Magic will be able to support it since they only have 192 MB of RAM.
p.s. if in wrong spot please move it im a tootal newb
I was just wondering if anyone had come across the Smart Wi-Fi app from Kineto that T-Mobile is purportedly testing now. Is there a more concrete timetable for release known. Also, I have heard conflicting information about the software requirements. I have read somewhere that it would run on any Android device with v. 1.5 or greater, but I have also heard that it requires special APIs that it needs to hook into so does that mean that the carrier would have to issue new builds of Android for each device with the APIs built in or did Google bake the APIs into Eclair or Froyo?
Anyone? I'm only gonna bump this once and if no one answers I'll take that as a confirmation that no one knows.
Ill throw down a bump on this.
Looks like they have officially put out the info. Now it is just waiting on T-mobile to push it out to users.
Funny thing is they say it is for Froyo, but Eclair is being showed on Vibrant as a demo.
http://www.kineto.com/press_releases/Kineto_Smart_Wifi_Android2_Froyo.php
Im kinda curious what this means exactly.
The press release doesn't seem to imply that this will be for one network or country, nor did the article that I read here.
Hopefully this will turn into something that'll be for any droid device. As someone who lives in a blackspot I would LOVE this kinda service. Here's hoping it gets into a release candidate soon. Wish they had opened it up to everyone rather than keeping in closed development tho, but oh well.
This would be a seriously amazing service and really boost android's rockingness.
I'd love to see if you could hack this to get true phone capability to wifi only tablets somehow *ponders*
Seems LG knows something Samsung doesn't? They say Google not allowing ui over lay on honeycomb at this time... Maybe vanilla 3.0 after all?
http://phandroid.com/2011/03/24/lg-says-google-wont-allow-custom-uis-on-honeycomb-samsung-says-huh/
Sent from my Tab using XDA Premium App
This is very interesting. Because Samsung was verrrryyyy careful to note that TouchWiz4.0 would be coming to "some devices" in "some markets". and wouldn't even hint at which those were.
Also it should be noted that they're calling TouchWiz4.0 a "UX" or User Experience, rather than a UI (User Interface). Although this is kinda stupid because they're re-skinning basic Honeycomb UI elements like the back/home/multitasking buttons and the entire settings menu, etc. Sounds like a UI more than a UX to me.
Sounds like they're going to try and develop TouchWiz4.0 and then fight Google on it. If anything, Google will push it back until they just include a few widgets and call it a day. I'm perfectly okay with this.
This sounds awesome btw, and I hope Google follows through with it. Its good for them to try and protect Android as a brand and keep it from getting bastardized by all the manufacturers and carriers.
You guys should remember that Samsung has previously squeezed through Google's rules. Google tried to stop Android from being put on tablets too early by not allowing GAPS (Google Apps, e.g. the Market) to be shipped on those devices, however there was an exception to this rule and surprisingly enough it was the original Galaxy Tab. I also believe the Notion Ink Adam had the market installed, but I don't know how they managed that one.
If what LG states is true, Samsung and maybe even other major manufactures like HTC do not have to follow this rule. I assure you, TouchWiz will somehow make it to these tabs somehow, Samsung seems to be special.
martonikaj said:
This sounds awesome btw, and I hope Google follows through with it. Its good for them to try and protect Android as a brand and keep it from getting bastardized by all the manufacturers and carriers.
Click to expand...
Click to collapse
I totally agree. I think it would be great for Google to be firm footed about this. It's mainly the UI customisation that has caused so many manufacturers to cancel or postpone Android OS updates. I don't care if a manufacturer can produce a better UI than stock, I'd still rather have stock so that OS updates can be more timely.
Manufacturers can still customise the UI/UX somewhat via the application layer and their own widgets. Look at Launcher Pro for example.
I think Google need to create a supported mechanism for manufacturers to customise/skin/theme Android via official API calls. This gives manufacturers the differentiation they want and keeps everyone working ontop of official API calls.
Google should simply require that any modifications to the stock Android Experience be made "optional" by the manufacturers. Everybody wins.
RickBaller said:
Google should simply require that any modifications to the stock Android Experience by made "optional" by the manufacturers. Everybody wins.
Click to expand...
Click to collapse
This. That way Samsung can advertise it all they want in promotional material etc., but there is a switch in the settings menu to turn it all back to stock. Maybe this will be Samsung's compromise, who knows. It sounds like Google would prefer if it was stock and no questions asked. Manufacturers can customize all they want with widgets and apps, just leave the OS stock!
What people don't realize is that as long as carriers have any part of the update process, you will always get updates late. Why do you think the iPhone has no carrier logo, no carrier apps, and all updates are through iTunes? Apple knows that carriers are slow as **** and mess up everything they touch.
ryude said:
What people don't realize is that as long as carriers have any part of the update process, you will always get updates late. Why do you think the iPhone has no carrier logo, no carrier apps, and all updates are through iTunes? Apple knows that carriers are slow as **** and mess up everything they touch.
Click to expand...
Click to collapse
Yeah I totally agree. Having firmware that toggles between stock and custom sounds like it will take even longer to release that the custom firmwares of today. The only way it could work is. If Samsung release them separately. Stock would be released first. They can then take as much time as they need to release their custom variant. That would be best of both worlds. Having said that I still think i'll be using home brew roms from xda as it will be tonnes better than what samsung produce.
Android should have a central repository like Ubuntu so it's always up to date on every device. Google made a mistake not doing something like that in the beginning. Now it's probably too late.
"An LG spokesperson." Yeah, dunno if I would actually believe this person. It's like asking a retail salesman at the store when the release date is for the new phone.
Also, do you guys really want to loose Touchwiz? Besides the rfs file system which is still yet unknown, I wouldn't mind Touchwiz if it includes all the codecs. The Vibrant was a beast of a media player right off the bat and if I get a tablet, I would want it to play anything from the get go. Although, the other topic posted a video saying the Touchwiz update would be optional so who knows.
DKYang said:
"An LG spokesperson." Yeah, dunno if I would actually believe this person. It's like asking a retail salesman at the store when the release date is for the new phone.
Also, do you guys really want to loose Touchwiz? Besides the rfs file system which is still yet unknown, I wouldn't mind Touchwiz if it includes all the codecs. The Vibrant was a beast of a media player right off the bat and if I get a tablet, I would want it to play anything from the get go. Although, the other topic posted a video saying the Touchwiz update would be optional so who knows.
Click to expand...
Click to collapse
That's a good point about the codec support. What's involved with Samsung adding codec support? Is it a case of just having the codec files added to the Android OS or does it require native modules to be installed within the Android OS? I guess it's the UI elements I have the most issues with TouchWiz. Non-UI elements that enhance the phone such as additional codecs are a welcome benefit. They probably add hardly any extra time to incorporate into a stock Android OS release.
Techno79 said:
That's a good point about the codec support. What's involved with Samsung adding codec support? Is it a case of just having the codec files added to the Android OS or does it require native modules to be installed within the Android OS? I guess it's the UI elements I have the most issues with TouchWiz. Non-UI elements that enhance the phone such as additional codecs are a welcome benefit. They probably add hardly any extra time to incorporate into a stock Android OS release.
Click to expand...
Click to collapse
I think he's just saying that Samsung has more incentive to add in the codec support if they're going to customize with TouchWiz4.0.
Although I'd like to see them add the codec support either way considering they could use it as a huge selling point.
It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...
The marshmallow update give me some new features and better battery life (though I do own the X Style, not pure). Unless you are dead set on being intentionally obtuse, then this isn't considered an alpha update.
Also the 6.0.1 update is quite minor, the largest change being some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's: http://www.androidheadlines.com/2015/12/google-posts-android-6-0-1-changelog.html
I know the label "alpha" is not not the official label for something like 6.0. But with so many substantial defects, and multiple forthcoming revisions to correct those defects a certainty, that's really what it is IMO. Maybe "public release alpha" would be a better description, since pre-release revisions go through even more defect-ridden levels including pre-release alpha, prior to public release.
Similar situation with previous Android versions, and in fact most software foisted on the public these days (I'm looking at you, Microsoft and Apple). Look at Lollipop and the multiple public release revisions it took to iron out most of the substantial defects, finally, with 5.1.1.
6.0.1 is not just "...some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's...", it also includes defect corrections. (Bluetooth, anyone?) And if the changelog doesn't list a significant number of defect corrections, that doesn't necessarily mean it is already polished at 6.0.1. The fragmented Android ecosystem and separation between Google, phone manufacturers, carriers, and users guarantees a plethora of various non-trivial defects in the ecosystem, many of which Google will address only slowly or even never for most phones.
For example, the memory leak defect in LP was not fixed until 5.1.1. How may revisions and months did that take? How many phones still run pre-5.5.1 with this defect?
One reason I bought the MXPE was the idea that it would be one of the first to get the updates. That turned out to be overly optimistic. It looks like Nexus is the only one still close enough to the source to get timely updates, and it also looks like Google is not pursuing Android defect corrections with any kind of urgency at all nowadays, maybe because the hardware ecosystem is becoming way too diverse to adequately support any more (or maybe because the profits roll in no matter what). Motorola phones, with the Moto alterations to Android, outsider status with carriers, and now hollowed-out Motorola support, appear to be no closer to adequate Android support from Google than any other non-Nexus phone.
"Obtuse"? A "bug" is a euphemism for a defect. Let's stop being obtuse, and call it what it is.
Any other info also appreciated.
You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.
MattBooth said:
You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.
Click to expand...
Click to collapse
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...
Tinkerer_ said:
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...
Click to expand...
Click to collapse
What ad hominem? Your uneducated state affects your ability to understand the nature of Android and software development. It's a perfectly legitimate response to your position. You lack the ability to understand and therefore your argument is flawed. I'm not attacking you, I actually tried to give you some insight into how it works, but you're not really interested and would rather insist on this "public beta" bull.
As far as fixing any "defects" you suppose, you haven't actually listed any so no-one is going to be able to help you with temporary work around without a list of what you feel is broken. I also showed you the changelog, so you can do your own homework to see if your supposed defects are fixed in 6.0.1.
The various hardware configurations doesn't even matter because Android is built to deal with it. So long as the hardware vendors of chips and modules support them properly and give out functioning binaries to OEM's, or proper source code, it's irrelevant. The exact opposite of what you said is true, Google has a very close relationship with it's partners (anyone signed up to their Google programs, to preinstall Google apps). The problem is carriers, who really shouldn't have a say in software on the phones, but that seems to be a chiefly North American problem.
Google doesn't need to have any connection to Android users as customers. Google does not sell Android, therefore you are not Google's customer unless you use a Nexus phone. Google sell the Google Experience, with the Nexus. You are Motorola's customer, and you are using Motorola's branched version of Android. Google doesn't owe Motorola any fixes or patches for their device. Motorola must maintain their own device tree and maintain their own relationships with their partners.
EDIT:
Also, Motorola's problem is resources. They have four version of the Moto X 2015 to deal with, three versions of the Moto X 2014, the new X Force, then the various versions of the G and E to deal with, along with two smart watches, and so forth. Their line up is increasing whist I imagine their development team is not. There was outrage (rightly so) when news broke that the Moto G 2015 wasn't getting the MM update, despite being a couple of months old, and Motorola listened and OTA's are rolling out.
I am asking if anyone can offer any info on anything being done to move toward MM revision with the many significant defects of 6.0 corrected. Read the forums, there are way too many defects with 6.0, it is patently a de facto public alpha, and we are tracking the usual pattern where it takes 3 to 5 revisions before an OS major rev is ironed out enough that upgrading will not cause more problems than it fixes.
There are always excuses made for why there are so many defects in software. There is a euphemism for "defect" everybody uses, "bug". Everyone has been making excuses for so long about shoddy workmanship and inadequate testing and correction of software, with the "bug" euphemism to minimize the reality that these are defects, that we are all just to suppose to accept systems ridden with faults without complaint. It's unacceptable. It can be done better. Part of why it doesn't get better is because everybody says "that's just the way it is, deal with it". With mountains of byzantine excuses and even ad hominem attacks (as here).
This thread was not started to start a tit for tat ad hominem back and forth, nor to post long essays detailing excuses for the pathetic status quo of the fragmented Android ecosystem with respect to defect causes and distributions. It was started looking for any info about work being done to fix the stock MM defects. Still seeking info.
TIA.
You should probably check the definition of ad hominem. There was no attack on you as a person, just pointing out that your uneducated state with regards to knowledge about software development affects your ability to call judgement on this.
But you haven't listened to a single word I've said and still maintain a shoddy position, so I would suggest to anyone else who reads this to simply ignore you as a troll.
Tinkerer_ said:
It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...
Click to expand...
Click to collapse
I think we'll close this debate. There are no real "Android" insiders on XDA, so asking for update info which is privy to Google is perhaps somewhat futile.
On a related note, XDA have a few dedicated "Android Fora", such as this complete Category where non-device specific discussion and indeed conjecture takes place. Perhaps you could take a look there and see what transpires?
Thanks