Slashdot Mirror
Google Releases Android 4.1 Source Code
Unlike previous releases, where months passed between Google announcing a new version and the code being released, Google has made good on their promise to release the source code to Jelly Bean in record time. Unfortunately, the gitweb instance on kernel.org is still down so you'll have to download the entire thing to take a peek. Hopefully the Cyanogenmod team will find time to start on a community enhanced version soon.
Is an option to add back the settings/menu button. I like having the settings always in a known and easy to reach place rather than depending on the app author to place it someplace convenient. And i wouldn't mind having the search button back either. Really the bottom button bar ought to be much more configurable than it is.
This Space Intentionally Left Blank
On Sprint, the Epic 4G Touch is still running Gingerbread. Sprint promised Ice Cream Sandwich months ago, yet we haven't seen anything yet.
What good are the new versions if we can't have them?
I want the ability to update my phone to the newest Android versions without rooting it.
This is already a really fast phone with ICS, and the Samsung touches are actually pretty nice, but I want to remove the ChatOn service (I'm getting spam messages) and I want Jelly Bean. I'm assuming Cynaogen will give me that option before Samsung/Sprint goes.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
CM9 just took sooo long. In fact the final release isn't out yet.
I just couldn't resist and put Jellybean on my Galaxy Nexus. But CyanogenMod still has a few features that are not incorporated into plain Android, nor are there apps for them. Not that I could find anyway. For example I want the battery in the status bar to show a percent number (there are apps that add that, but IN ADDITION to the regular battery), and I /love/ the Volume-Button-Long-Press-Skips-Tracks. Very very very useful while jogging. Oh and the power widgets in the pull-down, way better than the Power Control Widget.
CM9 took so long because they had to start from scratch. They are saying that CM10 should not be NEARLY as big a deal, so here's hoping!
In the land of the blind, the one-eyed man is kinky.
On the american version of the Galaxy S III and there is only the crappy sense roms out, nothing standard android like CM9/10, AOKP, whatever. Development seems slower than usual despite the fully unlocked bootloader etc. Maybe this will help!
It's easier to fight for one's principles than to live up to them.
So if Google took over the "pole position" hardware release with the Nexus 7, and they also release the Jelly Bean source code, does that mean that they're going to be the cleanest, easiest platform to hack?
I'm a bit worried now that I see that some of the media features won't be available on non-US devices; not because I'm overseas, but because that usually means the MAFIAA has some control over the hardware. I really want the little tablet, to replace my aging Nook Color. If it turns out there are bootloader lockin games being played, I'll be pretty much done with Android.
[
Slashdot, why is there no way to mark other users as spammers? It's really frustrating to have people like this pollute the message stream.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
It seems to make assumptions that are not valid, such as the host name being a valid RHS of email.
now we need to go OSS in diesel cars
I am actually surprised that Google does not have a dedicated development team working in co-operation with an independent mod group such as Cyanogenmod.
It is fairly clear that one of the greatest problems with Android is with version fragmentation. Mobile carriers have been very sluggish or outright hostile regarding major firmware upgrades on their handsets. It would be preferable for Google to ensure that carriers are contractually obligated to support OS upgrades for at least four or five years. But until that happens, throwing resources at the issue through a back door would be a nice thing.
http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html
The binaries for the Nexus S and Xoom are not available yet and won't be until the OTA update.
I tried compiling AOSP with android 4.1.1r1 checked out, adding the 4.0.4 vendor proprietary files, putting it on my phone, then flashing the ICS kernel, but it did not work.
Oh well. I'll be waiting.
I tried to find the installation instructions but could not find any on the CyanogenMod website. I found them on other sites but would rather find them next to the source.
Anyone with a link?
"Android is garbage designed "By Faggots, For Faggots" and it will never be as good as iOS"
Isn't it strange that iOS is included with hardware that is more designed than the OS... Go figure, wannabe.
As far as I know Android has massive issues with accessing the call voice stream. There have been bugs registered with hundreds of angry users yelling for better support for this.
Take a look at this: http://developer.android.com/reference/android/media/MediaRecorder.AudioSource.html
There are VOICE_DOWNLINK & VOICE_UPLINK streams, but people accessing them get exceptions instead of working streams most of the time...
Has JB improved that at all? I'll need to go test if my current phone has these streams working or not. And how about actually playing audio into the call? AFAIK old symbian phones had this.
--Coder
If you are volunteering to help with the Nexus One project, I'm sure they'll be happy to have you on board.
Just a note regarding legality- Android phones are sold all over the world, and plenty of countries allow recording calls. Calls are recorded in US in plenty of instances as well- in case you are talking to a broker, your call is recorded. Managers/sales people, etc record calls often. Nokia symbian phones did have this feature, and they were legally sold in US.
Answering machines also record calls all the time. Right now there is no possibility of implementing any of that on Android.
There might be an issue with security- an app could intercept your calls and send them to some 3rd party, but right now calls are handled by a binary blob- baseband firmware, which can also be hacked and forced to intercept your calls, even though it's more difficult.
--Coder
The Honeycomb source wasn't released because it was a mess, it's been explained to death. Every other version had its source code released in record time.
ICS was announced on October 19, 2012.
ICS source was released on November 14, 2012. LESS THAN A MONTH.
In addition - the first device to actually RECEIVE ICS did not become available until NOVEMBER 17. Yes, that's right, source was released THREE DAYS BEFORE the first device to receive ICS became available.
retrorocket.o not found, launch anyway?
and honeycomb never, that puts the average up quite a bit.
world was created 5 seconds before this post as it is.
That was a special exception that has been explained time and time again - Google didn't want people shoehorning it into phones.
retrorocket.o not found, launch anyway?
Still not an excuse.
You're being obtuse. The code in Honeycomb was broken, it was flat out broken. Would not work on phones at all (i.e 99.9% of Android devices that existed at the time). Code being non-functional is a perfectly valid reason not to release.
We hope your rules and wisdom choke you / Now we are one in everlasting peace
Thanks for that, I always thought that was to mark a post as a favorite or something along those lines! I guess it's an iconography hiccup then.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
"I don't know why you expect Google's official instructions to install Android be on the CyanogenMod website"
Thanks. After reading about the CyanogenMod I forgot about the articles' main focus... My fault.