Post Reply

[DEV] AOSP IceCreamSandwich 4.0.4 | MoltenMotherBoard (RC9 20130616)

1st October 2012, 12:55 PM   |  #1  
MoltenMotherBoard's Avatar
OP Member
Flag Rome
Thanks Meter: 298
 
58 posts
Join Date:Joined: Feb 2013
Donate to Me
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!

For general discussions, bug reports and FAQ, write HERE!

Credits:
Screens:


Downloads:
Full sources:
Changelog:
  • 20130722
    • Code updates
  • RC9 | 20130616
    • USB and Wifi thetering fixed (broken till RC7)
    • Gapps updated to 2013.06.14
    • ADB icon hided
    • Hacked again AudioFilter.csv
    • Tethering improvements
    • Added new libs to manage partitions
    • Code updates
  • RC8 | 20130607
    • New kernel
    • New proprietary Bootsplash
    • Improved AudioFilter.csv
    • Code updates
  • RC7 | 20130511
    • Fixed UMS on new kernel
    • Added log Banner
    • New support for init.d scripts
    • Switched to Stock kernel
    • Added support for 4.7 GCC version and subsequent
    • Adjusted doubled props
    • Code updates
  • RC6 | 20130501
    • Settings: excluded System updates
    • Settings: excluded Bluetooth tethering
    • Launcher: 3 homescreens
    • MMS: Avatar showed in notification bar
    • Improved Camera effects
    • Included LiveWallpapersPicker
    • Code updates
  • RC5 | 20130403
    • Excluded WiFi Direct (not GIO compatible feature)
    • Excluded camcorder frame interval (not GIO compatible feature)
    • Excluded camcorder effects (not GIO compatible feature)
    • Increased SMS lenght from 8 to 100 (before converting to MMS)
    • Included 800MHz CPU speed
    • Re-included some UI sounds
    • Adjusted Camera layout
    • Usable without SIM card (after 1st boot - as we provide SetupWizard that needs it, not our fault)
    • Fixed Bluetooth issues (it broke after RC3)
    • Some changes for Dalvik and Battery life
    • Fixed Photo Editor (thank to vutaluk1995)
    • Fixed WiFi Tethering
    • Code updates
  • RC4 | 20130308
    • Switched to WEXT WiFi drivers
    • Fixed GPS (it broke after RC2)
    • Enabled Init.d support by default
    • Fixed GooglePlay Store - Error 491
    • Used Tiny_aosp.mk build config
    • Fixed RIL
    • Added AD-HOC network supports
    • Fixed YouTube reboots
    • Code updates
  • RC3 | 20130224
    • Fixed camcorder
    • Added GPS.conf mod
    • Added Ringtones loop
    • New updated specific Samsung libs
    • Added MMB-Vendor repo
    • Included Google vendor (Gapps on sources)
    • Code updates
  • RC2 | 20130127
    • Modded Hosts file (now no ads)
    • MMS: now with 'new-line' button
    • Added Superuser as default
    • Added apns-config.xml
    • Camera fixed in sources
    • Code updates
  • RC1 | 20130117
    • Fixed USB Mode
    • Cleaned init.rc
    • Fixed all display related lags
    • Added full support for QCom hardware devices
    • Cleaned Framework from other devices specifications
    • Fixed Browser
    • Fixed Camera (with erikcas CM9 prebuilts)
    • Added full support for Legacy Qualcomm OMX IL libs
    • Great improvements in Framework
    • Code updates
  • BETA3 | 20130103
    • Fixed WiFi
    • Fixed Display issues
    • Fixed GPS
    • Fixed compass
    • Force enabled Surface dithering
    • Code updates
  • BETA2 | 20121225
    • Added SU binaries (rooted by default)
    • Improvements in the framework
    • Improvements in display
    • Code updates
  • BETA1 | 20121215
    • First booting build

Issues:
  • -----

Do you want to report an issue? Do it here!

General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama
Last edited by MoltenMotherBoard; 19th July 2014 at 03:19 PM.
The Following 71 Users Say Thank You to MoltenMotherBoard For This Useful Post: [ View ]
1st October 2012, 01:20 PM   |  #2  
p4c0_00's Avatar
Member
Flag Rome
Thanks Meter: 57
 
38 posts
Join Date:Joined: Feb 2012
More
AOSP:

Quote:
Originally Posted by XDA-Developers

The Android Open Source Project (AOSP), led by Google, is tasked with the maintenance and further development of Android. If you find a custom ROM that is based on AOSP, that means it will be closer to the original, vanilla Android created by Google rather than the bloated software created by Samsung, HTC, LG, and Motorola.

Quote:
Originally Posted by SearchConsumerization

The Android Open Source Project (AOSP) is an initiative created to guide development of the Android mobile platform. The Android platform consists of the operating system (OS), middleware and integral mobile applications.

The AOSP is overseen by the Open Handset Alliance (OHA), a Google-led coalition of over 30 wireless carriers, semiconductor companies, handset manufacturers and software companies. The purpose of the OHA is to further the development of open source standards for mobile devices.

The OHA member list includes Qualcomm, Broadcom, HTC, Intel, Samsung, Motorola, Sprint, Texas Instruments and Japanese wireless carriers KDDI and NTT DoCoMo. Companies that are conspicuously absent from the OHA member list include Nokia, Symbian, Apple, RIM, Microsoft, Verizon and Cingular.

Quote:
Originally Posted by AndroidCentral

AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.

For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for Android Open Source Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.

The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse.

Any of us can download and build the AOSP. We can even stay compliant with the ACP and contact Google about including their applications. Yes, any of us could build our own device using the AOSP code in our garage or basement with Google's full blessing. That's the beauty of the AOSP, and we wouldn't want it any other way.

Last edited by p4c0_00; 8th December 2012 at 10:42 AM.
The Following 14 Users Say Thank You to p4c0_00 For This Useful Post: [ View ]
1st October 2012, 01:33 PM   |  #3  
bgm92's Avatar
Senior Member
Flag Chitila
Thanks Meter: 49
 
176 posts
Join Date:Joined: Mar 2012
More
So this will be AOSP based, and not CM9 based? If so, CAN'T WAIT!
The Following 2 Users Say Thank You to bgm92 For This Useful Post: [ View ]
DQiB
1st October 2012, 01:44 PM   |  #4  
Guest
Thanks Meter: 0
 
n/a posts
it is AOSP, not AOSP based
Or CM9 or anything
EDIT: Hope it will not end like Maclaw´s never released AOSP Project
Last edited by DQiB; 1st October 2012 at 01:47 PM.
The Following 2 Users Say Thank You to For This Useful Post: [ View ]
1st October 2012, 02:39 PM   |  #5  
EvilKing009's Avatar
Senior Member
Flag Hyderabad
Thanks Meter: 367
 
946 posts
Join Date:Joined: Feb 2012
More
Amazing,first AOSP for our gio.
The Following 2 Users Say Thank You to EvilKing009 For This Useful Post: [ View ]
1st October 2012, 02:54 PM   |  #6  
marcin1147's Avatar
Senior Member
Thanks Meter: 2,116
 
366 posts
Join Date:Joined: Dec 2011
Donate to Me
More
Not second but first. We had working closed-alpha of our AOSP ROM.
The Following 2 Users Say Thank You to marcin1147 For This Useful Post: [ View ]
1st October 2012, 02:56 PM   |  #7  
belyava's Avatar
Senior Member
Flag Odessa
Thanks Meter: 331
 
516 posts
Join Date:Joined: Jul 2011
More
great! but why not JB?
The Following User Says Thank You to belyava For This Useful Post: [ View ]
1st October 2012, 03:00 PM   |  #8  
mackief's Avatar
Senior Member
Flag Rome
Thanks Meter: 999
 
1,374 posts
Join Date:Joined: Mar 2012
Donate to Me
More
Quote:
Originally Posted by belyava

great! but why not JB?

We prefer make a previous working version before making another.
That's like building ICS earlier than GB!? What the sense?

If we'll succeed to build AOSP ICS for GIO, then (maybe) we'll do the same with AOSP JB.
The Following 6 Users Say Thank You to mackief For This Useful Post: [ View ]
1st October 2012, 03:01 PM   |  #9  
Msilviu's Avatar
Senior Member
Flag Onesti
Thanks Meter: 40
 
211 posts
Join Date:Joined: Mar 2012
More
Cuz jellybean is very buggy and ics is much stable


Sent from my GT-S5660 using Tapatalk 2
The Following 2 Users Say Thank You to Msilviu For This Useful Post: [ View ]
1st October 2012, 03:10 PM   |  #10  
EvilKing009's Avatar
Senior Member
Flag Hyderabad
Thanks Meter: 367
 
946 posts
Join Date:Joined: Feb 2012
More
Quote:
Originally Posted by marcin1147

Not second but first. We had working closed-alpha of our AOSP ROM.

actually you are right.it is second aosp rom.

The Following User Says Thank You to EvilKing009 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes