Develop Bugs

Cyanogen for Hero?

Hi all
Does anyone know if the Cyanogen ROM will be availeble for the HERO? Just saw this video http://www.youtube.com/watch?v=3HVBVlAui3s&feature=player_embedded#!
where the G1 has it. Is has some nice features. Like:
Switching music with the volume keys
Syncing with facebook (i know some have this feature)
Switching music with the volume keys

There already is a Cyanogen port for the Hero, but it's not being developed anymore. I found it at modaco forums.

torstenk said:
Switching music with the volume keys
Syncing with facebook (i know some have this feature)
Click to expand...
Click to collapse
Is that all it has? Because I would expect every Hero rom to be able to sync with facebook, as it is a standard android feature. The switching music with volume keys would be annoying i think, but if it is a feature you would like try asking a dev to help you out or create an optional file to move keys around, its probably not that hard, but not something every user would want.

Well of course it has a lot of other features. Otherwise google would not try to lock down his ROMS. It is also very popular among users. I ahve read an article on Engadget that 30.000 users uses his ROM. So of course it has a lot of other features

Fact is, there's no up to date Cyanogen port for the Hero, magic volume music buttons or not. I'd hazard a guess that it'd be easier for benhaam or nprussell to implement this feature than to attempt to build the whole ROM for this purpose. But it'd be way down anyone's list of 'useful/required features'.

Problem is in Lox vendor tree, which doesn't work anymore. If there is working vendor thee for hero, it is easy to build from cyanogen sources.

It is a matter of delayed 2.1 update (God bless you HTC!). We are all waiting for official sources and vendor overlay.
May be MaXo64 could "Legoconstruct" some features from Cyanogen into his briliant aHero ROM.

hey 3 questions:
1. What is vendor overlay?
2. Why do we need htc's source if it's for 2.1 sense? Isn't The magic and the Hero the same hardware mostly?
3. Historically did htc publish their source after publishing the official rom?

Vendor specific drivers, modules and libraries for hardware. This code is closed and it is a property of HTC. For example code for video card or for GPS chip.
They have to publish source codes according to Android licence.

art_sn00p said:
They have to publish source codes according to Android licence.
Click to expand...
Click to collapse
This is a slightly misleading statement - there is *nothing* in the "Android License" which requires source code to be released because there is no such thing as an "Android License"
You are thinking of the linux kernel, which is released under the GPL. HTC have to release their modifications to the kernel, but this quite separate from the rest of Android which is released under the Apache Software License and is not a "copyleft" license.
This is why HTC do not have to release the source code for Sense UI.
Regards,
Dave

Nevertheless, we do not need Sense UI sources. It is mere a graphical enhancement. Linux kernel, right, is under GPLv2. And hardware specific kernel modules are kernel modification. So they have to ))
But it is not forbidden for HTC never produce update for Hero. No new kernel, no new sources )

art_sn00p said:
Nevertheless, we do not need Sense UI sources. It is mere a graphical enhancement. Linux kernel, right, is under GPLv2. And hardware specific kernel modules are kernel modification. So they have to ))
But it is not forbidden for HTC never produce update for Hero. No new kernel, no new sources )
Click to expand...
Click to collapse
I need Sense UI sources
I bet I could sell it back to HTC for a rouble or two!

Haha. Seriously though, that's what baksmali is for

[ROM][Themed+Modded AOKP][UPDATED NEWS!] ░⋮ AOKPCB R2.1 Beta 2 ⋮░ Circuit Boards!

[ROM][Themed+Modded AOKP][UPDATED NEWS!] ░⋮ AOKPCB R2.1 Beta 2 ⋮░ Circuit Boards!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is AOKPCB?
"This project is a representation of the benefits that open source brings. Using the Android ROM source of Team AOKP, we bring you a rock-solid, feature-rich ROM, topped off with a serving of PCB goodness that gives your device a very unique look.
We plan on adding more features and modifications as the ROM progresses, so feel free to leave us suggestions and feedback via the forum threads or join us on IRC."
-Team Broccoli
How does it look?
more screenshots...
Features:
A solid, clean ROM, built from AOKP Source
Custom made Android 8-bit Arcade bootanimation
Latest Apex + Nova Launchers (choose whichever you'd like as default)
File Manager & Dev Tools built-in
AOKPCB Wallpapers App with many custom PCB wallies by scar45
Live Wallpaper (WIP)
Custom Boot Sound to match Android 8-bit Arcade bootanimation
Extra Bacon
Fueled with Broccoli
Latest PCB Blue Theme + Companion App built-in with following elements:
Extensive SystemUI + framework-res edits
Background on Status + Navigation Bars
Notification pulldown menu + list items styled extensively
New Status Bar icons (Wi-Fi, BT, others coloured ICS blue)
New Circle Battery Icon with improved charging animation (0% [ red --> yellow --> green --> blue ] 100%)
Background image behind Navbar softkeys (on touch, if not overridden by ROM Control)
All Popups/Dialog boxes styled, and orange changed to ICS blue
New icons in Settings and ROM Control
Phone keypad buttons styled
Custom PCB default keyboard (LatinIME)
Contacts slightly modded with blue PCB header
Android Robot replaces default unknown caller/contact
Latest news from Team Broccoli:
23.10.2012
scar45 said:
"remicks and I have surely been busy over the past few months, as we had put a LOT of work into AOKPCB and then our personal lives ended up needing some attention (damn real life). Just thought I should say that yes, we stopped AOKPCB for ICS since JB was on the way, and when Goo.IM went down, it took all of the AOKPCB ROMs we built with it That was the only spot we had been hosting them unfortunately…
If all goes well though, we are planning on releasing AOKPCB for JB, however as AOKP JB is quite young (we base our source from theirs), we’re going to wait a little bit until more devices are added, and things get stable. Our team is a fraction of the size of Team Kang, so it’d be much tougher for us to manage an early ROM at this point.
It’s in the cards though, so as soon as it can be done, IT WILL BE!!!!
So glad that it seemed to be a success, Team Broccoli wants to thank everyone, especially the users, for your support and bigups.
Don’t forget to keep checking back, or subscribe to our RSS feed above!
Thanks or being patient everyone!"
source
Click to expand...
Click to collapse
24.07.2012
scar45 said:
Hey ALL,
I apologize for not keeping everyone informed. As it stands now, the plan is to get a final R3 (ICS) release out, however our repo is currently borked (I know, just before the last ICS release!). We're trying to get it fixed up (remicks is really, he's great with our builds), but hopefully that will happen soon. Afterwards, it's kind of up in the air for what we're going to do with JB. remicks and I have started working on Project FNV, which is a different type of ROM, being built by the community, however there is still a chance that we will make AOKPCB(ean) the way we like it, and keep Project FNV true to it's goal of being a community ROM.
It's obviously a LOT of work to maintain two ROMs, including websites, social media efforts, etc., but we're doing our best. We really love giving back to the community in this way, and it is more than amazing to hear good feedback. At the very least, when Theme Chooser arrives on Jelly Bean ROMs, you'll be able to use my PCB Themes as I will port them over ASAP. Again, I would love to keep AOKPCB going, however the team still has to discuss this past our plans for an R3 ICS release.
Hope that kind of clears the air a bit, and please don't consider this to be a "we're quitting" message. Life is crazy for many people, and lately things are no different for most of our team. We hope you'll understand, and keep watching this thread, the PCB Mini-site, and its RSS feed for future updates!
Click to expand...
Click to collapse
30.06.2012
scar45 said:
Hey all, I know things have been slow lately, but Broccoli is cooking up and we should be resuming nightlies as soon as possible. In the meantime, for our next release, you can expect updated PCB Blue elements[...].
Thanks for your patience during these less than ideal times, but rest assured we'll always be taking care of our work to do with this project. Stay tuned for more!
Click to expand...
Click to collapse
30.05.2012
scar45 said:
OK all, teeny tiny post to let you know that we just dropped R2 on the scene. I am out of steam completely as it has been a lot of work for us over the past few days. We'll be in touch, but new nightlies may not appear for the next few days (not much will change, as R2 has a slew of goodies for your enjoyment!)
Cheers, and please spread the word + let us know your experience with R2!
Click to expand...
Click to collapse
28.05.2012
remicks said:
Just a heads up for you guys, gonna be starting testing for our R2 release here very soon. New builds should be going up within the next few hours, so keep your eyes peeled!
Click to expand...
Click to collapse
23.05.2012
remicks said:
NEWS: Bacon is cooking, nothing real special for now, just testing a build cycle to see if I fixed a major problem
NEWS: Fixed a bunch of devices so they're able to build now, still have a couple giving me headaches but will get those sorted out this weekend hopefully.
Click to expand...
Click to collapse
21.05.2012
remicks said:
NEWS: Did a test cycle of the builds, lots of failures ... will fix them as I get time this week, gonna be real busy with family obligations though so it may take a few days. Sorry for the delay, we will be up and running again asap
Click to expand...
Click to collapse
17.05.2012
remicks said:
NEWS: I will be taking a short break from nightlies as I attempt to integrate a couple new "under the hood" features into AOKPCB. Those of you with OFFICIAL devices are encouraged to PM me and/or come by our IRC channel to help with testing this weekend. Sorry for the interruption in builds but I want to make this as stable as possible before I run a full build cycle again. Thank you for your patience and your support!
Click to expand...
Click to collapse
OFFICIAL R2:
"Today we bring you our second Official Release! This has been about a month in the making and includes all of the changes from our Nightlies. You’ll also notice that there are MANY more devices that we now build AOKPCB for. Please continue to give us feedback as we are building these ‘blind’ (we don’t have the actual devices), so tester feedback really helps.
Note that you should perform a full-wipe, as there have been some core changes. You could try a dirty-flash, but we wouldn’t recommend it for R2.
The changelog below contains everything that has been added to R2 of AOKPCB, and as it stands, R2 is based from AOKP Build 37 (+ newer commits).
Thanks to testers and everyone who gave feedback!"
-scar45
Changelog for OFFICIAL R2:
Latest AOKP Merges from AOKP Gerrit
Latest CM9 Merges for applicable tracked repos
Added New Lockscreen Music Controls (MarcLandis)
Added Selectable 2-8 Target Lockscreens (Pick how many you want!) (SteveSpear)
Added AOKPCB Wallpaper App (cr5315)
Added PCB Live Wallpaper (work-in-progress)
Added AOSP Music player from source
Added Glitch inline kernel building (sixstringsg)
Added custom boot sound to go with 8-bit Boot Animation (credits for boot sound: “The Scene Is Dead” – Dubmood^RAZOR1911)
Added File Manager (built from source)
Added DSP Manager (built from source)
Added Dev Tools (built from source)
Enabled Purgeable Assets (better ram management) and Sleep Mode (power saving)
Updated to Latest Apex Launcher
Updated to latest version of Terminal Emulator
Merged “T-Mobile Theme Engine” which allows for user-selectable themes similar to the old CM7 utility
Updated About Phone info and ROM Manager info to reflect AOKPCB/Team Broccoli
Updated build naming to reflect R2 Official release
Removed MusicFX (conflicts with DSP Manager)
Removed Nova Launcher
Removed Trebuchet (Tablets)
[PCB Theme] Styled the LatinIME keyboard
[PCB Theme] Styled the slider toggles (system-wide)
[PCB Theme] Added new softkeys with ‘PCB spotlight’ effect
[PCB Theme] Added PCB icon for “Themes” within Settings
[PCB Theme] Removed navigation bar background for compatibility with Theme Chooser version
[PCB Theme] Fixed null/no-signal icon (was originally stock icon if you didn’t have reception at all)
[PCB Theme] Fixed a few HDPI issues with Popup/Dialog boxes and Bottom Menu graphic glitches
[PCB Theme] Fixed a few notification pulldown images to be more flexible to custom toggle/weather/etc. layouts
Changelog for Beta-Releases & Nightlies:
20120610
Goo.IM support finished, you can now use GooManager to download AOKPCB nightlies/officials from the “Browse Compatible ROMs” section.
Latest AOKP merges (Linaro not included)
We may or may not be merging linaro into the AOKPCB build cycle, this will depend on further testing.
20120605
Nothing big, just latest AOKP merges and integrated GooManager app
20120528
R2 Beta Release!!! We’re almost there folks!
Removed Nova Launcher
Removed Trebuchet
Updated Terminal Emulator to newest version
New Lockscreen Music Controls
Latest AOKP merges
Updated About Phone info and ROM Manager info to reflect AOKPCB/Team Broccoli
Updated build naming to reflect R2 Beta release
Please test this build as much as possible, I would like to squash any bugs I can in the build before releasing R2. Nightlies will stop for a few days while this release is tested, if any bugs arise they will be squashed in test builds among our test group. Thank you for your patience.
20120526
A whole bunch of post-build 37 fixes from AOKP gerrit & more AOKP merges (see gerrit.aokp.co for more info)
Added AOSP Music app
Re-added Apex Launcher
20120524
Latest applicable AOKP/CM9 upstream merges
Removed CM Music (for now)
Updated Nova Launcher, removed Apex (for now)
Theme improvements
Updated version to build 37 to sync with AOKP build structure
Fixed naming scheme of zip files to end confusion about build number
Most cherry picks have been merged now, still using inline kernel building
A bunch more stuff I can’t remember right now, but all of it is good!
20120515
Removed prebuilt AOKPCB Wallpaper app in favor of source built
Merged latest AOKP commits (jpeg-turbo & SwagPapers included!)
Merged applicable CM9 commits (DSP Manager stuff mostly)
Updated version to build 36 to sync with AOKP build structure
20120513
Removed MusicFX in favor of DSP Manager (please report any bugs)
Removed prebuilt Dev Tools in favor of source built
Added CM9 Music app from source (please report any bugs)
Merged latest applicable AOKP/CM9 upstream commits
NOTE: BusyBox 1.20 has been causing issues for some users, you can find a working BusyBox 1.19.4 flashable zip in the download section. I will work on getting this incorporated at least until the issues with 1.20 are worked out.
20120512
Merged “T-Mobile Theme Engine” which allows for user-selectable themes similar to the old CM7 utility
(PCB Themes coming soon to the T-Mobile Theme Engine!)
Added PCB icon for “Themes” within Settings
Merged latest AOKP upstream commits
Added Glitch inline kernel building for SGS series phones (captivate/galaxys etc.)
Fixed a small issue within the LatinIME Keyboard theme (small ‘text hints’ were too dark in top-right corner of top row of keys)
20120507
Styled the LatinIME keyboard! (fixes/optimizations still may need to be made)
PCB Wallpaper App added
PCB Live Wallpaper added (work-in-progress)
Latest Apex + Nova Launchers are included
File Manager built from source
DSP Manager built from source
Fixed null/no-signal icon (was originally stock icon if you didn’t have reception at all)
Fixed a few HDPI issues with Popup/Dialog boxes and Bottom Menu graphic glitches
Optimized certain images (signal strength, etc.) with thanks to chevycam94’s effort
20120501
Second nightly build
Again, probably not much new, and note that if there are no nightly changelogs for a particular day, it just means there were no notable changes
Also, comments will be enabled for nightly builds so issues can be tracked easily
20120429
First nightly!
Not much would be different from R1-M5
Links
The one & only Team Broccoli Mini-Site!
Team Broccoli IRC-Channel
Thread here on XDA in the Theme-Section
German AOKPCB-Thread @german Android-Forum android-hilfe.de
Video-Overview at Youtube by Blueberry
Beta2 of R2.1 (MD5 for this: 3b25f0c8d2b249f94267f577dd6d3f71)
Official R2 (MD5 for this: f488a59501f4e33290faf8e1295e54d7)
GApps (MD5 for them: 7c524e1e078164f681e0aa6753180b2c)
BusyBox 1.19.4 CWM-flashable, credits to xda-member wraithdu
Here you will find Addons for the two different SD-Layouts, credits for that go to Bejda for finding them (and more ) & Smartg2os for providing them...
Installation:
Flash this as you would a normal ROM .zip! More instructions coming soon.
GApps are not included, download and flash them after the ROM!
This thread is presented by me with kind permission of Team Broccoli-member remicks.
Team Broccoli is a fresh collaboration of Android enthusiasts:
scar45
remicks
cr5315
sixstringsg
Contributors and thanks to:
Team Kang
Donators everywhere
ex0a
J2
+ more to be added, chat with us on IRC if you would like to help out
UOT Kitchen for their circle battery icons
Some other icons were obtained at IconFinder
hostedWithGeeks for the excellent hosting experience/service
Don't forget to hit the Thanks-Button or donate if you can!
Disclaimer:
Flash this at your own risk! Team Broccoli & me are NOT responsible for any damage caused to your device, however we do use AOKPCB ourselves. Always perform a NANDROID backup + Cache / Dalvik Cache wipe (at the least) before installing. Also, PM a Team Broccoli-member before you rip out any of their resources if you wanted to use them in your own theme/project. They can be accommodating so long as you get in touch first!

dling...
Gesendet von meinem GT-I9000 mit Tapatalk 2

Looks good, maybe gonna try..
What's different between this and AOKP? (except the theme)

finally its here ^^ good work guys!!

boris0711 said:
Looks good, maybe gonna try..
What's different between this and AOKP? (except the theme)
Click to expand...
Click to collapse
added features to op.

Of course i must try this....

aokp base
What is the base (aokp) used for this rom?

Flashing and will report back, if anything out of the ordinary should happen

WOW.I have seen while ago this ROM for Google Nexus and this is are great news about that its it ported to Galaxy S. I'm also excited because I am an electronic engineer . I will tested it few days and give a feedback.

What kernel is included? Official AOKP comes with Glitch ics kernel? I don't see any mentions about Glitch/Sixstring on the credits.
The theme is nice.

Moudii said:
What kernel is included? Official AOKP comes with Glitch ics kernel? I don't see any mentions about Glitch/Sixstring on the credits.
The theme is nice.
Click to expand...
Click to collapse
Glitch on this rom!!..

anarkia1976 said:
What is the base (aokp) used for this rom?
Click to expand...
Click to collapse
+1 ....

Moudii said:
What kernel is included? Official AOKP comes with Glitch ics kernel? I don't see any mentions about Glitch/Sixstring on the credits.
Click to expand...
Click to collapse
aren't glitch/sixstring members of team kang? Oo

which build is it made of?
asked in the original thread:
sUsH667 said:
as the nightlies are built from day to day, am i right that AOKPCB is always from the latest AOKP-build, meaning if i download AOKPCB today and the newest AOKP-build til today is b35, the downloaded AOKPCB is b35, too?
hope you understand what i mean, lol...
greetz,
sUSH
Click to expand...
Click to collapse
remicks said:
That is correct, but since I build nightlies more often than the build number changes I just leave them labeled by date.
Click to expand...
Click to collapse
think that makes it clear.
i think the kernel is the one which gets built if you build AOKP, cause AOKPCB is built from source.
another thing i want to make clear: i am NOT the maker of this rom! questions are best asked in the original thread to the original makers, but i will try to answer as many of them as possible, hope you understand...
greetz,
sUsH

Greatly themed rom. Btw, I think roman have asked all unofficial rom devs to not add new features in their rom that are going to be added in next builds and are already in source. Hope u can do something about it just in respect to roman.

bhu1 said:
Greatly themed rom. Btw, I think roman have asked all unofficial rom devs to not add new features in their rom that are going to be added in next builds and are already in source. Hope u can do something about it just in respect to roman.
Click to expand...
Click to collapse
i'm not such an expert, but how should a rom-maker do this if he builds from source? sync the source, check a list what is new in it and delete it? not build from latest source? or are all rom-makers doomed to do their roms with 7zip from the latest released official build by exchanging files?
don't get me wrong, i'm just interested, how what roman probably said, could be followed in real life.
anyway, thx for your suggestion and i will report it to the makers if i have time, because (AGAIN) i am not the maker, i made this thread to spread their work and have it it present in our sgs-forum, too, and to quote myself:
sUsH667 said:
questions are best asked in the original thread to the original makers, but i will try to answer as many of them as possible, hope you understand...
Click to expand...
Click to collapse
hope you understand,
greetz,
sUsH

Wow thanks for porting this, love the theme! I'm too lazy to wipe data right now though, so restored from nandroid, coming from Infinitum LBR 1.0 broke a few things
Will probably flash latest nightly this weekend or whenever I have the time.

From Source.
I RESPECT your work and all the team, i think That source is public and free for all.
Thanks so much for the excellent work.

sUsH667 said:
i'm not such an expert, but how should a rom-maker do this if he builds from source? sync the source, check a list what is new in it and delete it? not build from latest source? or are all rom-makers doomed to do their roms with 7zip from the latest released official build by exchanging files?
don't get me wrong, i'm just interested, how what roman probably said, could be followed in real life.
anyway, thx for your suggestion and i will report it to the makers if i have time, because (AGAIN) i am not the maker, i made this thread to spread their work and have it it present in our sgs-forum, too, and to quote myself:
hope you understand,
greetz,
sUsH
Click to expand...
Click to collapse
ignore that guy mate. He was jealous because your rom is better look than his rom. am i right?
Sent from my GT-I9000 using xda premium

I think ... You are right.
Sent from my GT-I9000 using XDA

[ROM] CyanogenMod 9 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
Jellaxy Team (in particular erikcas for CM9 / ICS sources and support)
MoltenMotherBoard team!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Changelog:
Nightlies
Code updates
20140927
Huge sources cleanup
Code updates from AOSP, CyanogenMod
20130722
Code updates from AOSP, CyanogenMod
20130627
New framework
Changes in Settings app
Removed MovieEditor
Various optimizations
Code updates from AOSP, CyanogenMod
20130618
Excluded Bluetooth Tether in Settings app (feature not properly working on GIO, hardware-level cause)
Excluded WiFi Direct in Settings app (feature not properly working on GIO, hardware-level cause)
Excluded CM Updates in Settings app (feature not needed and forcing closes)
USB and Wifi tethering fixed
Gapps updated to 2013.06.14
Fixed Bluetooth issues (it didn't receive files, beacuse of missing prebuilt configurations files)
Improved S2E usage
Improved Camera effects
Included MMB banner
Hacked hosts file (no more Ads)
ADB icon hided
Fixed AudioFilter.csv (it made some audio lags)
Code updates from AOSP, CyanogenMod
20130610
First release
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0

CyanogenMod
What is CyanogenMod?
CyanogenMod is an open source replacement firmware for smart phones and tablet computers based on the Android mobile operating system. It is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
It offers features and options not found in the official firmware distributed by mobile device vendors. Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, revoking application permissions, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as Wi-Fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. According to its developers, CyanogenMod does not contain spyware or bloatware. CyanogenMod is also stated to increase performance and reliability compared with official firmware releases.
Although only a subset of total CyanogenMod users elect to report their use of the firmware, as of 30 May 2013, CyanogenMod has recorded over 5.1 million active installs on a multitude of devices.

Looking forward to see Firefox OS on our precious Gio Good Luck!

Good luck macief

mackief said:
Hi guys! Me and my team are working hard to port B2G on our Gio. At the moment we're on holiday, so in these days we'll try to fix lot of things, but we cant upload the package. We'll do it on Saturday, when we'll in Rome again!
Team:
- mackief
- p4c0
Thanks:
- Lemmymet
- MaclawStudios
Click to expand...
Click to collapse
You mean today? Cause today is Saturday

bgm92 said:
You mean today? Cause today is Saturday
Click to expand...
Click to collapse
sunday

Nope guys.. Saturday, the next...
Sorry, you've to wait a week!

Isnt this againts the rules ? Coming soon threads
Sent from my GT-S5830 using xda premium

CoolCatGetHome said:
Isnt this againts the rules ? Coming soon threads
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
not if they are good enough to develop, like cm9 and jelly bean threads were, as moderator told me

not if they are good enough to develop, like cm9 and jelly bean threads were, as moderator told me
Click to expand...
Click to collapse
erm.. When are threads 'good enough to develop' and how can you know that before anything is released?

MerynGoesAndroid said:
erm.. When are threads 'good enough to develop' and how can you know that before anything is released?
Click to expand...
Click to collapse
Threads with AOSP and latest android version roms or simular like other OS ports
Example
-cm9
-cm7
-any jellybean related
- AOSP
-more
Just not the roms were somebody adds a few apks and removes some and gives it a theme but makes a thread without a download link
Sent from my GT-S5660 using xda premium

Just got a build with working RIL, things not working:
-Camera
-video playback
Maybe some more things, used parts of cm9 to get device tree and armv6 working
I'm on holidays now, can't upload it the coming 3 weeks
Sent from my B2G webbrowser

lemmymet said:
Just got a build with working RIL, things not working:
-Camera
-video playback
Maybe some more things, used parts of cm9 to get device tree and armv6 working
I'm on holidays now, can't upload it the coming 3 weeks
Sent from my B2G webbrowser
Click to expand...
Click to collapse
Great work mate!
I'll publish here my package on Saturday! Maybe we can help each other!
Let me know bro!

Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )

csoulr666 said:
Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )
Click to expand...
Click to collapse
If he's not having a device like yours, how is he gonna make it work for that device? :|

csoulr666 said:
Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )
Click to expand...
Click to collapse
Maybe I can try to do it, but I cant do my best as I'll do for the Gio, because I don't have the device!

bgm92 said:
If he's not having a device like yours, how is he gonna make it work for that device? :|
Click to expand...
Click to collapse
That makes no sense.
What about cm9 builds for fit, mini by maclaw?
They didnt had it.
Phiexz releasing roms and kernels etc for devices he doesnt have
You just need to know watcha doing
Sent from my GT-S5660 using xda premium

Ya actually, you can develop for other devices. You just need the Device's sources and a friend to test that on their device

Peteragent5 said:
Ya actually, you can develop for other devices. You just need the Device's sources and a friend to test that on their device
Click to expand...
Click to collapse
Yeah someone you can PM who can test it before releasing unless you want spam
Sent from my GT-S5660 using xda premium

I can test........ That's the main reason I posted here.... I am ready to make my WFS a guinea pig for the sake of other WFS'S

[DEV] AOSP ICS 4.0.4 by MaclawStudio

Hello guys!
Ok, as we said, we’re back with new ROM – ICS AOSP.
Don’t worry, we’ll provide you other ROMs as soon, as it possible. It's just the beginning.
Changelog (RC1):
- finally fixed location
- finally fixed GPS
- some improvements in camera HAL
- camera preview is now H/W rendered
- fixed signal lost issues
- fixed lost SMS issues
- fixed samsung sim toolkit (if you want to try, please install Stk.apk)
- fixed battery drain
- fixed gallery crash in some cases
- new RIL
Changelog (beta 3):
- fixed tethering
- fixed google location services
- fixed network location services
- wifi improvements
- performance improvements:
* added jit compiler
* added entropy performance hack
* improved dalvik parameters
Changelog (beta 2):
- fixed all timezone and calendar bugs
- fixed framework damaged by beta1
- fixed Netlink errors in logcat
- fixed gps and compass
- fixed bluetooth config
- fixed a2dp
- improved updater
- improved ramdisk
Changelog (beta 1):
- fixed bluetooth (with working deep)
- fixed logcat spam
- added tweak to hide reboot menu ( http://forum.xda-developers.com/showthread.php?p=35512923 )
- added tweak to force launcher rotation ( http://forum.xda-developers.com/showthread.php?p=35512923 )
- partially fixed videorecording
- added missing daemons and services
- fixed wallpapers size (now it looks just gorgeous)
- reduced Launcher size to by a 6MB
- fixed librs crash (live wallpapers)
- fixed YT reboots
- fixed proximity
Changelog (alpha 1):
- first release
What isn’t working (will be fixed soon):
- Video recording in stock app (try I
Download it now on Mod Edit: Links removed as Ad fly links are not allowed - see rule 13.
I’d be glad, if you would share links to our download page, instead of direct links to download.
Also would be great, if you wouldn’t create the mirrors.
Thanks.
Guys who made it happen:
- Macław
- Marcin1147
Thanks for help from:
- tom3q
- Trybicki
- ganster41
Cheers guys, I hope you’ll enjoy our return!
MaclawStudio team
EDIT1: About GPL
As you can see @andyharney has checked sources and reopened all closed threads.
Kernel sources were available on GitHub FOR A MONTHS.
And YES, kernel wasn't modified since CM9 RC2. It's the same old kernel.
Here comes the link: https://github.com/MaclawStudios/android_kernel_maclawstudios
You can also apply 2.6.35.7 to 2.6.35.14 patch if you want: http://forum.xda-developers.com/attachment.php?attachmentid=779403&d=1321023939
Also, I noticed that some of you are doing everything to destroy our work, and that's why we aren't publishing device profile sources. By the way we don't have to do this. We've developed device profile from scratch on closed license and we just won't publish it, just like Samsung. You can still use our old device profile or Jellaxy one.
EDIT2: About Deep Sleep in Beta 3
I noticed some people experiencing issue with deep sleep after installing the update. If you are affected by bug, please turn off Google location services. We’ll try to fix it in next release.
EDIT3: About something called "Seeder"
Please, don't use famous app/hack called "Seeder". We did a quick research and /dev/random isn't used in android frameworks anywhere. Seeder will improve performance ONLY in some custom apps or cryptography functions, and that's why... we've integrated seeder tweaks in beta3. Installing "Seeder" would only decrease your phone's performance because it will work in background and waste your RAM.
EDIT4: Bugtracker
Please, use bugtracker if you want to report a bug:
https://github.com/MaclawStudios/aosp/issues

Yay! First!
Sent from my BlackBerry 9300 using Tapatalk

What kernel is this running on?

Compiled by themselve I guess
Sent from my GT-S5660 using xda app-developers app

Good job! For alpha1 version sounds great! Downloading it right now!
By the way, at the moment this AOSP it's better than erikas's one

it works great for me so far
deepsleep is working, yt hq is smooth
everything is butter smooth
notification toggles are not part of aosp i guess (better make use of widgets then)
no random reboots
does it support a2sd ext or i have to take my chances
good work!

yuvalrozin said:
What kernel is this running on?
Click to expand...
Click to collapse
2.6.35.14 by MaclawStudio
The same is in CM9 RC2

Excuse me is someone would consider this blasphemy or something,
but can Maclaw's kernel run Erikas' roms and the other way around?

Cpu performans setting nothing
Natification panel buyon nothing
GT-S5660 cihazımdan Tapatalk 2 ile gönderildi

It looks great, and works great!!!! Thank you very very much!
Note: You must wipe data and cache after flashing this rom! Doesn't matter if you do this before or after flashing, but mandatory before booting! I looked intro updater-script and there is no wiping of data&cache

m.ali.ozkaya said:
Cpu performans setting nothing
Natification panel buyon nothing
Click to expand...
Click to collapse
Because it's AOSP. Clean Android straight from Google. Without any mods. Stock as hell. The same as on Galaxy Nexus.

marcin1147 said:
Because it's AOSP. Clean Android straight from Google. Without any mods. Stock as hell. The same as on Galaxy Nexus.
Click to expand...
Click to collapse
I guess he'll have to install NoFrills CPU application for CPU freq setting
It's smooth as hell Thank you again!

marcin1147 said:
Because it's AOSP. Clean Android straight from Google. Without any mods. Stock as hell. The same as on Galaxy Nexus.
Click to expand...
Click to collapse
great news.. video recording and bluetooth fix would be perfect..
Waiting
thank you marcin and maclaw..

A mini-bug I've found:
When you try to enter the "Select time zone" menu from "Date & Time", nothing happens - you get back to Settings menu
Also, I don't think this is a bug, but there are not status bar toggles Please implement this, even if maybe it's not AOSP - think that if Samsung would release ICS for Gio, there would be status bar toggles, as in Gingerbread stock rom.

bad work!
- random reoboots/hot reboots, nothing stable for me ...
- you modded the rom, it isn´t a clean aosp!
* You added Superuser
* You added Reboot Option in Power Menu
* You changed Bootanimation (Normal AOSP uses one in framework-res.apk)
* You added GApps ...
Normal AOSP Size is around 100 mb, so why urs is around 120 mb?
sry but AOSP means for me, that nothing will be customized, pls marcin, i know you are a gr8 developer but provide flashable packages for extra stuff! and not customize it in rom directly

It's great as it is! What difference is if you install GApps later or if it comes preinstalled? Same goes for SU!

bgm92 said:
It's great as it is! What difference is if you install GApps later or if it comes preinstalled? Same goes for SU!
Click to expand...
Click to collapse
Maybe he wants AOSP like Galaxy Nexus have! Btw, it also have gapps preinstalled, and about SU, I agreed if he wants AOSP like Nexus.
Oh, I know, about Gapps: he don't want to waste his bandwidth maybe!

AngSanley said:
Maybe he wants AOSP like Galaxy Nexus have! Btw, it also have gapps preinstalled, and about SU, I agreed if he wants AOSP like Nexus.
Oh, I know, about Gapps: he don't want to waste his bandwidth maybe!
Click to expand...
Click to collapse
do never try to kid me -.-
i have a monster computer and can build aosp in around 13 minutes
Also my bandwith is the best one here i think, with around 32 mb download per second, so i wont/cant waste my bandwith!

OldDroid said:
do never try to kid me -.-
i have a monster computer and can build aosp in around 13 minutes
Also my bandwith is the best one here i think, with around 32 mb download per second, so i wont/cant waste my bandwith!
Click to expand...
Click to collapse
So why u don't want included gapps?
Sent from my brain.

OldDroid said:
do never try to kid me -.-
i have a monster computer and can build aosp in around 13 minutes
Also my bandwith is the best one here i think, with around 32 mb download per second, so i wont/cant waste my bandwith!
Click to expand...
Click to collapse
You don't have to use our ROM. You can build your own ROM if you want

[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)

[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use mobile data as much as you; you get the idea.
NOTE: FML is built and tested on the Verizon Galaxy Nexus variant, also known as toro. The GSM Galaxy Nexus variant (the one pertaining to the forum section you're currently in), also known as maguro, is extremely similar in hardware to the Verizon Galaxy Nexus, however I'm not able to test these builds personally. There aren't any code changes between builds for toro and maguro so that I know there shouldn't be any huge issues, but things specific to maguro I'll need feedback on to make sure they're working OK.
[#HowTo]
Latest Build​KitKat/ROM Stable: omni-4.4.4-20140705-maguro-FML.zip (159.07 MB)
KitKat/TWRP Stable: fml-twrp-2.7.1.0-20140705-maguro.img (8.58 MB)
KitKat/ROM Beta: omni-4.4.4-20141015-maguro-FML.zip (160.13 MB)
KitKat/ROM Beta Hotfix: boot.img (4.83MB)
Hotfix Info: The latest beta had a bug on maguro causing the radio to be a jerk and not work. Flashing this boot.img will resolve that issue. If you'd rather not flash it with fastboot like is normally done for .img files, you can use the Flashify app for it, or you can open up the ROM zip and replace the boot.img in there with the hotfix.
Lollipop/ROM Beta: FML-AOSP-5.0-20150108-maguro.zip (194.45 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues:
- Camera can be a little touchy, but it generally works.
- Long SMS messages fail to send, fix is on-the-way though.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues​- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2014-07-05
Beta Release Date: 2015-01-08
Created 2014-05-27
Last Updated 2015-01-08

Changelog, News, Etc.​
Lollipop Beta Changelogs:
2015/01/08
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.
2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
(v3): Fixed VYL00M eMMC bootlooping.
Older Builds:
2014/11/16
- Fixed the RIL.
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
- Built the ROM with "WITH_DEXPREOPT" set to true.
This basically just adds the ".odex" files to /system. With ART this is important because it cuts down on those lengthy boot-up times because instead of compiling the apps' code on the device, it now compiles it on my computer when I build the ROM instead.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Rather than use Lollipop's eye-hurting bright white theme on this screen, I've switched it back to the classic, darker theme.
2014/11/09
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place... or not, for some people. I'm fairly confident this should fix the VYL00M eMMC issue.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.
KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.
NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff!
KitKat Stable Changelogs:
2014/07/05 (Operation: Streamline)
ROM: Synced with OmniROM's latest changes as of around 6:30 AM 2014/07/05 UTC.
ROM/Build: Fully updated to AOSP 4.4.4 (specifically, the android-4.4.4_r1 tag), which really doesn't change much though...
ROM/Build: Stopped including the unused (as far as I can tell) dock.png in /system/vendor/res/images/dock/
ROM/Build: Leveraged a feature added to updater-script creation by OmniROM which coincidentally makes the ROM flashable on any format of /system partition, beit F2FS, EXT4, exFAT, whatever.
ROM/Build: Stopped including Voice Dialer. Voice Dialer is just an unpolished piece of junk which really isn't used ever since Google Now.
ROM/Build: Stopped including 0xBenchmark.
ROM/Core: A number of changes added for completely seamless and simultaneous F2FS and EXT4 support.
ROM/General: Switched to the Android KitKat boot animation, which takes up nearly 4MB less space than OmniROM's boot animation.
ROM/General: Used OptiPNG heavily on numerous things in an effort to save space.
ROM/Kernel: Added F2FS support, nearly 500 commits were merged in for this.
ROM/Kernel: Relaxed BIGMEM a bit to hopefully fix Camera crashing for some users. (Only a 4MB difference BTW)
ROM/Kernel: Optimized CPU L2 cache settings slightly.
TWRP: Added support for seamless and simultaneous F2FS and EXT4.
I'm forgetting a number of things and I'm not going into as much detail on some of this as I'd like to. Frankly, I'm exhausted. Maybe I'll expand on this tomorrow. Maybe.
Oh I also submitted 8 things to the OmniROM Gerrit. One has been merged so far, the others probably will probably be merged in the next day or two.
Older Builds:
2014/06/05 v2 (Operation: Chocoholic)
ROM: Synced with OmniROM's latest changes as of around 10:00 PM 2014/06/05 UTC.
V2 just fixes a bug where Dialer would crash upon entering the Call Log.
2014/06/05 (Operation: Chocoholic)
ROM: Synced with OmniROM's latest changes as of around 7:00 AM 2014/06/05 UTC.
ROM: Fully updated to AOSP 4.4.3 (specifically, the android-4.4.3_r1.1 tag).
ROM/Build: Removed some duplicate alarm and notification sounds in my never-ending effort to slim down the build size.
ROM/General: A few things were added to accommodate building for the Kindle Fire HD 7" that might spill over into the Galaxy Nexus builds (no harm, if anything an improvement).
Wanted to get an Android 4.4.3 build out ASAP, so this build doesn't have much in terms of changes/fixes from myself. This weekend I'll be going on vacation, and after I get back I'm planning on adding F2FS support finally. :good:
BTW, you might want to make sure you have the 4.4.3 GApps.
2014/05/31 (Operation: Jackpot)
ROM: Synced with OmniROM's latest changes as of around 11:30 PM 2014/05/31 UTC.
ROM/ART: Pulled in some things from AOSP's master branch to hopefully decrease initial boot-up time for ART.
ROM/Build: Fixed some more instances of code being compiled/optimized for a generic ARM CPU instead of the Cortex-A9 specifically.
ROM/Build: Included some requested translations.
ROM/Build: Found a fix by PrimeDirective to build frameworks/base/core with -fstrict-aliasing.
ROM/Dalvik: Pulled in some things from AOSP's master branch to increase overall speed for Dalvik.
ROM/General: Fixed a bug where overclocking would revert when the screen was turned off.
ROM/General: Added battery charging LED support.
ROM/General: Fixed notification LED flash interval being way too long by default.
ROM/General: Experimental improvements for GPS. (See: GitHub Commit)
ROM/Kernel: Added the "purple tint fix" commit.
ROM/Settings: Fixed Settings not being translated.
Quite the changelog here! ART is feeling a little snappier in this build but Dalvik might still be faster!
2014/05/26 (Operation: Maguro)
ROM: Initial maguro build.
After the great number of improvements I made in the most recent build I did for toro, I figured it was perfect timing to get maguro up and running.
If you'd like to have a look at the toro stuff, it's here: http://forum.xda-developers.com/devdb/project/?id=1098
Let me know if there's any issues!
To-Do.​Slim down the build by putting less used stock applications into a separate flashable .zip, such as Browser.
Experiments I'm Looking Into​Creating Black Holes with my phone's ridiculously awesome speed.

Developer Info​This is a little section I'm gonna set up explaining things in more technicalish and "down-and-dirty" details of sorts for developers interested in this project and potentially incorporating it into their projects.
The only thing I ask is to make a little "Thank You" section in your main post like I have here and credit at least me and Linaro, and also credit anybody else's work I have used if you use it as well. I'd also appreciate it if you could maybe link my name to this thread or my user profile here on XDA, but that part isn't a requirement.
All of my work can be found on my GitHub. Please note that any commits on my GitHub that are after the most recent build of FML should be considered experimental and potentially not working at all. I develop on the fly and often times things on my GitHub aren't finished and fully tested unless they have made their way into an official build of FML.
Please pay no attention to where it says a repository was forked from. Often times I'll have forks that I just re-use to avoid duplicate and unnecessary extra repos. For example, in repos forked from CyanogenMod you might notice the default branch is actually something like "omni-4.4" indicating that branch is based from OmniROM and not CyanogenMod.
The best place to keep track of what parts of the Android source code that needs patches is the manifest.
All About Strict Aliasing!​One of the big things Linaro does with improving Android's performance is fixing violations of what's known as "the strict aliasing rule."
A pointer is said to alias another pointer when they both refer to the same location of memory. This is OK and not an uncommon thing to do. The strict aliasing rule is that pointers of different types should never refer to the same location of memory (aka alias each other). Things like this are just fine and dandy:
Code:
void pointlessFunction( uint32_t foo )
{
uint32_t* const bar = (uint32_t*)&foo;
}
That's alright, as foo and bar are the same type. Note that it's also OK if the only difference between foo and bar is signedness (e.x. uint32_t and int32_t).
Now this...
Code:
void anotherPointlessFunction( uint32_t foo )
{
uint16_t* const bar = (uint16_t*)&foo;
}
...this is a problem. foo and bar are NOT the same type. This is a violation of strict aliasing.
Strict aliasing allows a compiler to make some assumptions when compiling and optimizing code that it otherwise couldn't. This is a good read about the benefits of it.
Here's a few examples of fixing strict aliasing violations:
DSPManager
frameworks/av
bionic
Note that not everything is fixable, or worth fixing. Sometimes you'll just have to add -fno-strict-aliasing to the problematic section and call it a day:
frameworks/base
Of Unicorns and Compilers...​This section will delve into compilers and flags for them. The "Of Unicorns" part is in reference to the amount of false information, misconceptions, and mythical beliefs regarding these things. One thing in particular is the common belief that throwing every flag possible at the compiler results in better/faster binaries. That couldn't be further from the truth, and is something that actually took me quite some time to properly understand myself (in part because the misconceptions are more common than the actual truth!). In this section I will mainly be referencing the GCC compiler, as that's what is currently used for the majority of Android and most Linux systems as a whole. The other compiler that is making quite a run at GCC is Clang, so first I will talk about GCC vs Clang quickly:
GCC vs. Clang
GCC is currently (~May 2014) the most common compiler used for Linux and Linux-based systems (which includes Android). GCC was first released in 1987, as the "GNU C Compiler." Not long after its release, it was extended to support C++ as well, and over time many different languages and platforms became supported by GCC so it is now called the "GNU Compiler Collection." Over all this time, GCC became more and more difficult to maintain. As time passes on, fewer and fewer people have been able to get their foot in the door to work on GCC as it just became so... bloated.
Eventually, somebody finally got the guts (or resources, rather) to take on GCC and make a competing compiler. Clang was born.
Clang is a front-end for LLVM. Initially, LLVM was going to make use of GCC's front-end for making a C/C++/etc. compiler using LLVM's back-end, however this was just too cumbersome of a task due to GCC's difficult-to-work-with codebase, which was what sparked Clang instead.
Fun fact: Clang 1.0 was released in 2009. It was first open-sourced in 2007. That's 20 years after GCC's inception, but yet Clang has managed to tear GCC's usage apart. However to be fair, LLVM's initial release was 2003, but that's still a decade and a half head-start given to GCC!
As of GCC 4.8 vs. LLVM/Clang 3.4, it's kind of a toss-up between the two. In some cases GCC has better binary results and in other cases Clang has better binary results, however Clang outshines GCC in areas other than the resulting compiled code:
1. Clang is faster and uses fewer resources than GCC when compiling. It's usually a safe bet that Clang is going to be at least 50% (1.5x) faster than GCC when compiling, whilst also somehow using less RAM and disk space than GCC. For those of you that like being eco-friendly, just imagine the amount of energy this saves!
2. Clang has generally been ahead-of-the-game when it comes to supporting C++ standards. Current example: Clang has been C++14 feature-complete since the end of 2013, while GCC (even in 4.9!) is not.
Thanks to the competition from Clang, GCC has also been stepping up its game as well too. All-in-all this has been a win-win for everybody so far.
Flags.
Aaand here we go on compiler flags. For this I'll be referencing the GCC documentation on "GCC command options", here: https://gcc.gnu.org/onlinedocs/gcc/index.html#toc_Invoking-GCC
Of particular interest in this section will be "Options That Control Optimization", but other sections are often overlooked which can be of use, I'll explain those later though.
The first thing you'll see in the "Options That Control Optimization" section are the -O options. These are general optimization levels that give you a sensible default to work with.
First off is -O0. This is the default, and doesn't turn on any optimization options. This is generally only used for debugging code, as some optimizations can interfere with that.
Next would be -O1. This enables some optimizations to reduce code size and improve speed, without increasing the time it takes to compile code significantly.
After that is -O2. This is what is generally used for most program compiling, as it enables plenty of optimizations and these ones generally don't cause problems/bugs with the resulting binaries whilst greatly improving speed.
Then there are some non-numbered ones which I'll go over:
-Os is somewhere between -O1 and -O2. It enables most of -O2's options, but disables some that can increase the size of the resulting binaries. This can be of great use when dealing with smaller embedded systems where space is generally preferred over speed. It's closer to -O2 than -O1...
-Og is useful for debugging purposes. It enables a few optimizations that generally don't effect ability to debug code, so devs don't have to deal with the slowness of -O0 as much as usual.
And then there's the almighty -O3...
-O3 enables some extra optimizations that -O2 does not. The drawbacks are increased compile time, increased binary size, and the possibility for some bugs. In many cases, -O3 might not improve speed over -O2 whatsoever. In other cases it can be helpful, but it is nothing compared to the differences between -O1 and -O2.
Android generally uses -O2 by default. It's safe and fast enough for most cases. -Os is also used for any Thumb instruction-set code for ARM, as Thumb is generally meant for reduced size and complexity from what I can tell.
There's also a flag kinda above -O3, which is -Ofast. The problem with -Ofast is that it can cause huge problems for any code that makes the (correct!) assumption about some math stuff, so it is generally avoided.
Then there are some flags that aren't enabled by any optimization level. This is not without reason: these flags are, generally, useless. They increase compile time by a ridiculous amount, and their effects on the resulting binaries might be absolutely nothing. Zilch. Nadda. Even for something as large as Android, these flags can still do nothing. If these flags can have a speed-up, it's generally not without risk, and they should be kept to specific use-cases rather than used on every single thing.
These flags can be considered about the equivalent of using the "placebo" profile for h264 video encoding. It has a less-than 1% improvement in the resulting quality, yet can take twice as long to render (or, in this case, compile). And they are pretty much exactly what the placebo profile for h264 encoding is, a placebo effect. You will not find a measurable increase in speed, and the risks associated with it are generally not worth it!
There is an exception to that though: -flto. This enables Link-Time Optimization, and can have huge impacts on both the speed of the binaries as well as even a reduction in their size! LTO can be viewed as this: when the compiler is truckin along compiling things, it generally only sees bits and pieces of the project at hand. LTO allows the compiler to view how everything works together rather than just each individual part, and in doing so it can find HUGE improvements! When LTO was in its infancy with GCC, it was pretty unstable, but with GCC 4.8 and above it can be used reliably. It's also advised to use the -fuse-linker-plugin flag when using LTO as well (read the docs on that).
Here is my work on using LTO with Android, it's more involved than simply adding it with all the other flags which is why you'll generally hear the people that are making use of the "unicorn flags" say it doesn't work...
https://github.com/MWisBest/android_build/commit/c1b041c32572b6ee1bbb17b1fa8c038c5e9fde1f
https://github.com/MWisBest/android_build/commit/95bb49b613424b70af3e820748724fb92ef35b5e
https://github.com/MWisBest/android_build/commit/d2c13f1c35cfa9c114a69c74cfb1c2631643eebc
Ignore the things in the last couple commits there that aren't related to LTO...
But like I said, it's more involved than just throwing the flags blindly at the compiler, there are a few other fixes required to get a successful build with LTO:
https://github.com/MWisBest/android_bionic/commit/3b3f59a173a7cc4ff3a1cec4456a99108ce08092
And then it also has to be disabled in ART, that fix courtesy of @metalspring : https://github.com/MWisBest/android_art/commit/9ed3774fcba75077e098720406d261b79bd9baa9
// To be continued.
Small but Helpful Things​I thought I'd put some simple little things here that can be immensely helpful to devs. Most of these they'll probably know already, but some won't and when I learned these things they had a profound impact on development. At the very least it can be a helpful reminder/reference sort of thing.
Properly Logging Builds
This is something I finally figured out not long ago that has had a huge impact on debugging problems...
I'm not all that great with bash but I generally understood redirecting the output of a program to a file. However, when I tried the usual:
Code:
make -jX otapackage > buildlog.txt
, not everything was going to the file. Eventually I learned that just using ">" only redirects stdout, and not stderr which was where all the warnings and errors went to. To get around that, there's a couple options. One, you can redirect stdout and stderr to separate files, like so:
Code:
make -jX otapackage 1> buildstdout.txt 2> buildstderr.txt
, or the other option is to just lump them all into a single file using:
Code:
make -jX otapackage > buildlog.txt 2>&1
This post is a WIP...

As you may or may not have read in the OP, this ROM was built and tested on the Verizon Galaxy Nexus only for about 9 months. I don't own a GSM Galaxy Nexus, so I'm not able to fully test these GSM builds, however the differences between the two are minimal and everything should work OK.
As the Verizon Galaxy Nexus is pretty much only in the USA, one thing I did to reduce the size of the ROM was to cut back on some of the translations. I've kept what I thought were fairly common languages (including outside the USA). Since I've now expanded to the GSM Galaxy Nexus, which is more international, there's a chance that a language you need might be missing. Please just let me know what you need and I'll be more than happy to include it.

Downloading....perfect timing...i am rom hopping for a while and excited to try this, skimmed last few pages of your toro thread :good:
why not take a look at the recent thumb flag optimisation commits that claimed 6x speeds recently...

You have written that you have built CM 10.2 FML version. Is it compatible with maguro? Where can I find it and flash it over my phone just to see it?

pvkiniyan95 said:
Downloading....perfect timing...i am rom hopping for a while and excited to try this, skimmed last few pages of your toro thread :good:
why not take a look at the recent thumb flag optimisation commits that claimed 6x speeds recently...
Click to expand...
Click to collapse
Yeah I replied to that thread... it's bogus, unsafe, and unprofessional. FML was far beyond that stuff since its inception and it has only gotten better since.
qtoo941 said:
You have written that you have built CM 10.2 FML version. Is it compatible with maguro? Where can I find it and flash it over my phone just to see it?
Click to expand...
Click to collapse
This right here is the first build I've done that's maguro compatible, and there's been lots of improvements since when this ROM was based off of CM so even if it'd work on maguro it's not really worth trying at this point. Sorry!

Wow, amazing, i was waiting for this! OmniMetal is a wonderful ROM but we can't except that metalspring will be doing regulary updates since he has a new phone.

This might be the quickest ROM my maguro has ever seen. I can't even believe how fast Chrome opens.

Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?
Thank you

ahmadairfan said:
Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?
Thank you
Click to expand...
Click to collapse
Only ART! Feel the smoothness

ahmadairfan said:
Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?
Thank you
Click to expand...
Click to collapse
pianistaPL said:
Only ART! Feel the smoothness
Click to expand...
Click to collapse
Dalvik! MWis pimped it the **** out!
MWisBest said:
I'm extremely impressed with ART and I know it's Android's future. They will not be including Dalvik in 4.5 based on what I'm seeing in AOSP's master branch currently. I don't think ART will be the default in 4.4.3, there's a number of changes they'd need for that to happen and at this point in 4.4's lifecycle I think it's too late for a major change such as that, but 4.5 and onwards it will be the go-to thing yes.
I'm also extremely happy with how fast Dalvik is in this last build though... here's my observations on it:
Going from a previous build to the new build (after running Dalvik on both), it feels as if I switched from Dalvik to ART but with a 10x faster bootup due to not going through all the ART compilation, not to mention the space saved over ART too.
After that experience, I think this whole ART thing might've been unnecessary or at least would've been delayed if Android wasn't compiled like it's the stone age.
Funny you mention the dalvik-cache thing, it's actually multi-threaded so it is indeed about a 2x speed improvement, nice observation.
Click to expand...
Click to collapse

Ok, end of speaking, phone charged, let's try this ROM!
Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
OK, i guess i can't, after boot with ART i get pernamently SystemUI FC So this is a good reason to try this super fast dalvik

pianistaPL said:
Ok, end of speaking, phone charged, let's try this ROM!
Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
OK, i guess i can't, after boot with ART i get pernamently SystemUI FC So this is a good reason to try this super fast dalvik
Click to expand...
Click to collapse
thanks for that...u saved my time

gonna flash this B*tch tonite! the changelog looks impressive. one question though do i need to flash the twrp recovery in the OP as well before flashing the ROM. Thanks!

Very fast on dalvik but phone gets mini freeze when i tap recent apps button and when i tap home button (when i have some app opened)
I haven't recent apps buttom freeze/lag only when i am on home screen.
Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka

Hi MWisBest, could you please add Spanish language support for this ROM? I'm very impressed with your work, and I'd like to have it translated.
Thank you very much in advance!.
Enviado desde mi Nexus 7 mediante Tapatalk

ahmadairfan said:
Downloading!
What do you recommend guys, Dalvik or ART?
I've been always using ART before and then I read replies in toro thread, most likely chooses Dalvik eh?
Thank you
Click to expand...
Click to collapse
pianistaPL said:
Only ART! Feel the smoothness
Click to expand...
Click to collapse
osm0sis said:
Dalvik! MWis pimped it the **** out!
Click to expand...
Click to collapse
^What he said. At the very least give Dalvik a try.
pianistaPL said:
Ok, end of speaking, phone charged, let's try this ROM!
Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
@MWisBest Can i let set DexOpt to /cache if i use Banks Core Gapps and i want change to ART?
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
OK, i guess i can't, after boot with ART i get pernamently SystemUI FC So this is a good reason to try this super fast dalvik
Click to expand...
Click to collapse
That sounds like the issue you'd run into with a GApps package that's too large, if you want to use a GApps package that large with ART you'll have to disable the DexOpt to /cache thing before switching to ART.
pvkiniyan95 said:
thanks for that...u saved my time
Click to expand...
Click to collapse
See above.
gautam_nexus said:
gonna flash this B*tch tonite! the changelog looks impressive. one question though do i need to flash the twrp recovery in the OP as well before flashing the ROM. Thanks!
Click to expand...
Click to collapse
The recovery build is not required, I just figured I'd start uploading them as 1. It's built automatically, and 2. I use it myself.
pianistaPL said:
Very fast on dalvik but phone gets mini freeze when i tap recent apps button and when i tap home button (when i have some app opened)
I haven't recent apps buttom freeze/lag only when i am on home screen.
Click to expand...
Click to collapse
I'll certainly have a look at that and see what's causing it. The Recents issue might be due to the code regarding if OmniSwitch should be opened instead of the usual Recents, as I'm not getting that lag with OmniSwitch enabled as Recents.
mosca_ said:
Hi MWisBest, could you please add Spanish language support for this ROM? I'm very impressed with your work, and I'd like to have it translated.
Thank you very much in advance!.
Click to expand...
Click to collapse
Crap! I do have Spanish included, but the furthest I had gone with testing that stuff was to simply make sure they were listed in "Settings --> Language & input --> Language", which does have Español listed, however I clicked on it now after your post and there are some things that are missing translations, most notably: Settings!!
The good news is that I recently figured out how to properly log my builds, and sure enough I've found some warnings about translations not being included, so I should be able to track down what's causing this and have it fixed for the next build.

MWisBest said:
^What he said. At the very least give Dalvik a try.
That sounds like the issue you'd run into with a GApps package that's too large, if you want to use a GApps package that large with ART you'll have to disable the DexOpt to /cache thing before switching to ART.
See above.
The recovery build is not required, I just figured I'd start uploading them as 1. It's built automatically, and 2. I use it myself.
I'll certainly have a look at that and see what's causing it. The Recents issue might be due to the code regarding if OmniSwitch should be opened instead of the usual Recents, as I'm not getting that lag with OmniSwitch enabled as Recents.
Crap! I do have Spanish included, but the furthest I had gone with testing that stuff was to simply make sure they were listed in "Settings --> Language & input --> Language", which does have Español listed, however I clicked on it now after your post and there are some things that are missing translations, most notably: Settings!!
The good news is that I recently figured out how to properly log my builds, and sure enough I've found some warnings about translations not being included, so I should be able to track down what's causing this and have it fixed for the next build.
Click to expand...
Click to collapse
Polish language doesn't have translated settings too So i'm waiting for new version, thanks

pianistaPL said:
Polish language doesn't have translated settings too So i'm waiting for new version, thanks
Click to expand...
Click to collapse
Thanks for the heads-up, looks like it's ALL the translations for Settings, dang!