New “cupcake” update details have been announced on the Android project site. Apparently we will be getting a lot more than a few bug fixes and supposed security patches. Just what else is there, take a look after the jump.
Google has decided to tear into the camera and pull out video recording for all T-Mobile G1 owners. No longer will we be behind with the rest of the phones because the lack of basic features. The browser will be getting an inline find function that implements very selective copy and paste. There are also a few speed enhancements that may or may not be recognizable to the average user.
The rest of the updates are more for future devices as they are not G1 specific enhancements. One update that has us stumped is the addition of “Basic x86 support.” Another addition will be the framework that allows for simple system-wide on-screen input. There is also a note of faster MMS scrolling and the ability to save attachments from MMS, come on Google.
[Via AndroidProject]








and some people thought google was forgetting about its new baby android! this is all very very promising!
From http://source.android.com/roadmap:
During Android's transition to an open-source project, some development has continued to happen in a private branch. We are working to move the rest of these changes into the open as soon as possible, and all future open-source work will happen in the public git repositories. All changes that have already been submitted to the public repositories will be merged into the newer code base, so nothing should be lost.
The Android team has begun pushing these changes to the public git repositories, in the "cupcake" branch.
About this code drop:
The "cupcake" branch is a read-only mirror of the private Android branch.
cupcake is still very much a work in progress. It is a development branch, not a release.
The first drop is a large roll-up commit of all of the changes since release-1.0. We will transition to regular, smaller roll-up drops, ultimately pushing individual commits.
The cupcake branch will be merged into the master branch, so that all of the public patches can be used with the new code base. None of the commits in the public repositories will be lost, unless they no longer make sense or are obsoleted by the new code base. Due to the United States' holiday season, though, this may not be finished until early January.
To check out the cupcake branch:
mkdir cupcake # create a new client directory
cd cupcake
repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
repo sync
Notable changes introduced in cupcake:
Applications
MMS
New features
Save attachments from MMS.
Significant bug fixes
Faster conversation list scrolling
Email
Significant bug fixes
Accounts that were marked "never check" are not auto-checked.
Date & time displayed using user preference (e.g. 24 hr vs. AM/PM).
cc: displayed in message view.
Relaxed POP3 parser rules so it works with non-compliant email servers.
Password quoting bugs in IMAP. Makes it work for users with funny chars in their password (e.g. spaces).
Various sources of errors in auto & manual account setup.
Improvements on how we report various connection errors. Makes it much easier for user to diagnose failed account setups.
New-mail notifications for POP3 accounts.
Properly recover from POP3 connection failures, so that the next connection has a chance of working properly.
Remove automatic accounts setup entries that were broken or not testable. Minor fixes to a few of the remaining entries. Improvements to warning dialogs used for a few special cases.
New accounts are now set to check every 15 minutes (instead of defaulting to "never").
Fixed a bug causing approximately 1 in 25 outbound messages to freeze up the IMAP connection (to a Gmail based server) when transferred to the Sent folder. This broke the entire connection so new messages could not be downloaded either.
Unit test framework so Email can be extended & tested more reliably.
Fix IMAP manually-created accounts so message delete works properly.
Alarm Clock
Significant bug fixes
Alert now plays audio/vibe directly, rather than through AlarmManager. AlarmClock alert starts playing audio/vibe in its IntentReceiver, rather than on activity start. These changes should prevent alarms from being blocked by modal dialogs.
Package Installer
Significant bug fixes
Bugs related to replacing existing applications.
Settings
New features
New menu option to list running processes in Settings->ManageApplications.
Music
New features
Music playback fades in after suspending for phone call.
New media search intent allows for 3rd party apps to launch or respond to media searches based on artist, album, or title.
Affects: Music Player, YouTube, Browser applications.
Browser
New features
Updated WebKit browser core, synced with Nov 2008 WebKit version.
Support for new, optimized JavaScript engine (SquirrelFish).
Copy / paste is enabled in the browser. To copy with touch, press and hold the shift key and select the text. Releasing the shift key or ending the touch drag copies the text. To copy with the trackball, press and hold the shift key, move the cursor to the selection start, click the trackball, and move the trackball to the extend the selection. Releasing the shift key, or clicking the trackball a second time, copies the text.
Find is enabled in the browser. To find text, choose it from the menu and type the text to find.
Drawing has been sped up substantially by supporting partial content invalidates and partial screen invalidates. Pages with animations are 5x faster.
VoiceDialer
New features
VoiceDialer supports 'open app' command
Camera/Gallery
New features
Video recorder mode
Share intent for videos
Video thumbnails
Local file playback
Download manager
New features
Support for HTTP codes 301, 302, 303 and 307 (redirects).
HTTP code 503 is now handled, with support for retry-after in delay-seconds.
Downloads that were cleanly interrupted are now resumed instead of failing.
Applications can now pause their downloads.
Retry delays are now randomized.
Connectivity is now checked on all interfaces.
Downloads with invalid characters in file name can now be saved.
Framework
New features
Support of touch events in WebView.
New JavaScript engine (SquirrelFish) in WebView.
Input method framework, for soft keyboards and other on-screen input methods. Includes new APIs for applications to interact with input methods, and the ability for third party developers to write their own input methods.
Access to the raw audio data for playback and recording from application code.
New PendingIntent.FLAG_UPDATE_CURRENT option.
Support for top-level boolean resources.
Tactile feedback to the LockPatternView. Tactile feedback can be enabled/disabled by going to Settings > Security & location and then checking/unchecking "Use tactile feedback". Note that this can be used independently of the visual feedback of the lines ("Use visible pattern"). Thus it gives users a middle ground between showing the lines on the screen and having no feedback at all.
PackageManager changes to support un-installation of partially installed applications. Added new flag PackageManager.GET_UNINSTALLED_PACKAGES to include partially installed apps in all relevant PackageManager api's. ManageApplications screen now lists such partially installed apps and the user can uninstall these applications completely.
Support third party updates of system applications. New menu options in Settings->ManageApplications to list updated system applications.
Framework support to list current running processes. New API in ActivityManager.
Framework feature to declare required configurations by applications. New manifest attribute uses-configuration in android manifest.
Hardware accelerated video encode (video recorder) in opencore.
Simplified SREC speech recognition API available.
Streaming audio I/O for applications.
Significant bug fixes
Fixed issues with saving state in the view hierarchy, so that you can properly subclass from something like TextView and create your own state that inherits from that provided by TextView.
TextView now implements onKeyMultiple(), so that flinging the trackball will result in accelerated scrolling. This required some changes to movement methods, and included some improvements to the acceleration computed when flinging.
Framework bug fixes in PackageManager to share/un-share permissions for applications with shared uid's.
Significant rework of Settings->ManageApplications Performance and UI enhancements.
A number of settings in android.provider.Settings.System were moved to android.provider.Settings.Secure. Only system software can modify these settings. Additionally, a new permission, WRITE_SECURE_SETTINGS, is required to access these settings. The old constants in Settings.System have been deprecated. It is possible to read settings values via Settings.System using the deprecated constants. However, attempts to modify these settings via Settings.System will result in a log message and the setting value will be left unchanged.
Many bug fixes in the media framework
Bluetooth
New features
Support for A2DP & AVRCP profiles.
Significant bug fixes
First connection after pairing always fails on many carkits.
Mini Cooper and some late model BMW cars fail to use Bluetooth or take 2 minutes for Phone Book transfer.
System software
New features
New kernel based on Linux 2.6.27.
Improvements to the wakelock API.
Work to transition to the USB Gadget Framework underway.
Basic x86 support.
Radio & Telephony
New features
SIM Application Toolkit 1.0.
Green CALL button is no longer a shortcut for "add a new call". This has been a rarely used feature and confusing if triggered accidentally.
Longer in-call screen timeout when using the speakerphone.
"Show dialpad" / "Hide dialpad" item added to the in-call menu, to make it easier to discover the DTMF dialpad.
Significant bug fixes
An obscure case where the Phone UI could cause the device to not go to sleep on its own. This would happen if user bails out of the in-call screen by hitting HOME, followed by the call disconnecting remotely.
Don't allow a single tap to open the in-call dialpad. It is now required to touch and drag it. This makes it much harder to accidentally open the dialpad by touching the screen with your face.
Developer Tools
New features
Enable handset manufacturers to extend the Android SDK with add-ons. SDK add-ons will include:
system libraries to let developers use additional APIs provided by handset manufacturers or from other 3rd party vendors that handset manufacturers chose to include
emulator system images, skins, and hardware configuration to let developers test their applications on their Android implementation
This is work-in-progress. Please note that the latest Android SDK (Android 1.0 SDK, Release 2) is not compatible with the SDK plugin in the new branch, please use ADT 0.8.0. SDK add-on support is planned for future SDK release.
Build System
New features
The functions in build/envsetup.sh should be much more useful
http://tech.slashdot.org/article.pl?...59230&from=rss
Cool!
Edit: Thanks AlfSimen
,Michael Martin
Google And Blog
No more wired headphones..
I can use my Stereo Bluetooth headphones with G1.. One more slap on iPhones shiny face.. haha.. Yeetaaaaaa.. i am just excited..
It looks like people will have to start realizing the true benefit of the Android platform pretty soon.
No more wired headphones..
I can use my Stereo Bluetooth headphones with G1.. One more slap on iPhones shiny face.. haha.. Yeetaaaaaa.. i am just excited..
Good to know!
No more wired headphones..
I can use my Stereo Bluetooth headphones with G1.. One more slap on iPhones shiny face.. haha.. Yeetaaaaaa.. i am just excited..
Can't wait! A2DP is one feature I've really been waiting for!
can't wait for this to be released.
Speaking of complaining: did anyone spot an auto-rotate function fix to prevent Android from destroying the active process every time the screen is rotated?
all g1 users get the upgrade... unless otherwise note ie unlocked devices, developer devices etc... google tends to not play that game though
and since android is going to be a readily available free open source operating system, i can guarantee you it will show up on cheapie phones that can't afford an accelerometer in them, etc...
all g1 users get the upgrade... unless otherwise note ie unlocked devices, developer devices etc... google tends to not play that game though
rex2745, Where did you hear only new devices will work with a2dp??? Everything I have read said the ability was built in but due to time constraints and an unfinished bluetooth api, they had to pull it from the main branch.... It's just like multi-touch input... our G1 is capable, in fact, one hacker found some lines of code that were commented out in the source... He uncommented them, recompiled the kernal and was able to write some crude software proving the feasability of the G1 working with Multi-touch. Honestly, this is why I fell in love with this phone WAY before it came out! What other phone do you know of where developers are spending coutless hours to add features to existing hardware??? The iPhone has been out for more than 2 years and my wife's new G3 iPhone can't do video... But my G1 will soon!!!
Wooohooo!
On a side note, I can't believe the author of the article missed the A2DP feature... for me, this is the most exciting development of all!!!
still cant wait for this update though.
where are you getting that from?
still cant wait for this update though.
...but yeah, the auto-rotate function can get annoying to, if it reacts to very small changes in the phone's direction.
I knew Google wouldn't let us down.
http://weblog.infoworld.com/fatalexc..._client_g.html
Pretty cool **** actually
http://source.android.com/roadmap/cupcake
and filler
We will probably see the main framework updates that include the virtual keyboard and not the cupcake branch- especially since a lot of cupcake is not even ready for final code distribution.
Even some of the blogs and tech sites seem to have selective reading skills and assume things that will disappoint a lot of people that use a G1.
We will probably see the main framework updates that include the virtual keyboard and not the cupcake branch- especially since a lot of cupcake is not even ready for final code distribution.
Even some of the blogs and tech sites seem to have selective reading skills and assume things that will disappoint a lot of people that use a G1.
One always has the option of pulling the ripcord and reverting back to RC29 and the stock boot/recovery images, at which point the phone will accept OTAs.
LOL so I just read it and the first thing they mention was video recording LOL.
I've learned not to trust anything anyone on YOO TOOB says.
I see I see...
http://www.googleandblog.com/g1-cupc...released/3612/
See if this helps.
I like your name->picture by the way.
can't allow me to travel through time
doesn't print money
works poorly as an umbrella
should I go on?
can't allow me to travel through time
doesn't print money
works poorly as an umbrella
should I go on?
I'm taking this piece of crap back.
No Flash player! >.<
No Flash player! >.<
Let me know the next time you find a copy of Windows or Mac OS that includes flash.
No Flash player! >.<
Honestly, Flash is created by Adobe. Yes, they could bundle it, but it would no longer be a fully open source OS (or it'll have some serious hiccups, like other similar open source flash players have).
The best we'll get for flash is an add on, and it will only ever be Flash Lite due to cpu requirements.
I would actually hate to surf the web on my phone if Flash was enabled, could you imagine how slow it'll be and how much battery drainage will occur? Imagine a "punch the monkey" flash banner ad, sitting there wasting your b/w and cpu (especially minimized).
As far as multi-touch -- who really needs it? The zoom buttons are far more practical for the screen real estate (try multitouch on a rooted phone). I'm all for cool new animations and features and such, but I'd rather Google spend time fixing and adding features which really matter (such as improved exchange support for those business users).
// End of my rant