[KERNEL] [3.1.10] Olympus (Atrix 4G) Kernel Project

Search This thread


Senior Member
Nov 20, 2012
Rio do Sul, SC
Is that Samsung kernel in 3.1 version, if it is higher, cut & paste won't work...

Yep, I know the drill. That was just an example, those changes come from AOSP's releases (at least most bcmdhd's changes are being pushed there directly by "some google guy"). I'll take a look on AOSP's tegra tree and see how things are going. If it's worth the trouble I'll try to merge myself and see if it gains anything.

BTW, I compiled our 3.1 straight from git using an updated toolchain and a minor tweaks and got a 20-hour uptime. Previously it would reboot every hour or so. Still can't say it's not a coincidence, for the weather is also cooler and most reboots seemed to happen to me when the phone gets hot. Will report back in a few days.


Senior Member
Mar 20, 2013
Sorry, I have every plan to upgrade to kernel;s BigPart v2 that ditches /preinstall to give /data an extra 300M space in KitKat v3 and install more apks than ever
Sorry, I have every plan to post Android L BigPart for Moto Atrix 4G here if I can manage to build from source
Last edited by a moderator:


Senior Member
Mar 20, 2013


Senior Member
May 17, 2013
No worry, I was just saying my plan to upgrade bigpart in V3 rom release, feel safe to test with current kernel and V2 :)

I am not sure if this post is better here or at the CM11 thread, but anyway, hopefully the following will be of interest to Z, @krystianp and others.

First, thanks to Z and K for their amazing work! And now...

I finally got around this evening to installing Z's CM11 v2 ROM. Taking care to not have cell and WiFi data on simultaneously, it has been running for four hours without reboots. So I've tried several of the things that were issues here on the kernel thread -- hoping this would help sort out what issues are kernel related and what are ROM related. What I have found so far is:

Skype: the proximity sensor problem is gone with CM11 -- Skype does not blank out when the screen turns off due to proximity. Great! On the other hand the intermittent white noise problem is still there; that is, at random, some calls work fine, while for some the other party (as indicated by the Skype test call) gets only static. So it seems the proximity sensor problem was ROM related, but white noise is kernel.

Stereo recording apps (e.g. RecForge II): as with CM10.1, there is a problem recognizing both microphones when set to stereo recording and "front microphone". Stereo recording worked fine in CM10 (which I believe had pre-3.1.10 kernel) but has not worked properly in CM10.1, and now not in CM11. Occasionally both mics are recognized, but usually not. Rear microphone setting usually does work in stereo. So my conclusion is that this is a problem with the kernel. Doesn't have the sped-up voice problem that was present in the July kernels on CM10.1

Google voice typing: Seems to work, as it was also with relatively recent kernels on CM10.1. But voice search causes google search to crash ("Unfortunately, Google Search has stopped"), whereas that worked with recent kernels on CM10.1, so apparently a ROM issue (and I think others have noted it and sent in the appropriate diagnostic files?).

Camera, and camera flash: seem to work about as on CM10.1

YouTube: current version from Play Store opens, can browse content, but crashes upon actually playing anything (as others have noted).

Modem: I had been having fairly frequent modem drops (with fairly quick restoration most of the time; but other times requiring turning on then off airplane mode) on CM10.1. With CM11, so far, the modem seems to stay solidly on. So apparently a ROM issue vs kernel issue.
  • Like
Reactions: asmaron and Mustkeg


Senior Member
Dec 26, 2012
Buenos Aires
The latest Kernels from THIS PAGE developed on 2014_09_12 doesn't seems to work at all, both CM9 & CM10.1, both given a complete shutdown after Motorola logo.

Sadly, i just wanted to test another kernel.


Senior Member
Nov 15, 2008
Puerto Montt
I've build two kernels (for cm9 and cm10.2) with some tweaks to wlan settings. Please check if waking from deepsleep works (in Skype and other apps). I hope kernel boots, i forgot to backup my scripts and I had to do it by hand (scripts are nice but makes you forget stuff :D)

Hi Krystianp. I'm back with more testings and have to questions:
- ¿Kernel development for AtrICS (and related) ROMs is done for now?

- I cannot change the shrking (for overscan canceling) at will in HDMI out (http://forum.xda-developers.com/showpost.php?p=54968810&postcount=1038), when Lapdock is enabled, the 1366x768 resolution without overscan is activated, so it appears shrinked. In HD Dock the history is different, because you can change resolution, and some resolutions has shrinked and others dont:

1080P, perfectly fit and sized in screen

720P, overscaned, need to be shriked
So it's like it's defined in some part of resolutions settings.
I try to edit the line "hdmi_overscan" in Settings.db but it does nothing, so I think it need a direct command to enable/disable shrink/overscan

- ¿Could you use USB Audio in AtrICS and related ROMs?, I couldnt get to work, try to put DockAudio.APK in AtrICS and ICSRom without success. It doesnt work in all docks (Car, Standard and HD)


Senior Member
Oct 23, 2012
Hello Krystian
Do you plan to update your kernel for next android 5.0 , perhaps i can fix the reboot problem of kitkat version ?
Best regards


Senior Member
Nov 15, 2008
Puerto Montt
Me 2. I realy need working lapdock for atrix 4g. Webtop 3.0 working perfect, but resolution kills my eyes:eek:
Where resolution problem? In kernel's or app's side?

Dont know yet, if you se the first image in my last post, when I plug the HD Dock in TV @1080P it fits perfectly, it looks awesome. Maybe it is pre-configured in the resolutions lists, and overide the Shrink option in menu.
Some months ago I read a post about resolutions, but didnt find it again to search the file source in the atrix, to see further and what can be changed. So probably I can be more ROM related. Unfortunaley, unpwn4par leave the proyect. :crying:


Jul 16, 2013
It's shrinked, the =1366x768 pixels are put in aprox. 1300x700 pixeles, thats why it looks bad and ilegible.
Different apps say that resolution is 1366x768.
If it 1300x700 , maybe kernel developer will fix wrong resolution? Or this settings is in app for mirroring?
Maybe autodetect resolution woks wron?


Senior Member
Nov 15, 2008
Puerto Montt
Different apps say that resolution is 1366x768.
If it 1300x700 , maybe kernel developer will fix wrong resolution? Or this settings is in app for mirroring?
Maybe autodetect resolution woks wron?

I mean physically shrinked. If you count the "black bars" you'll se youre are missing aprox. 1366-1300=66 pixels, please take a look in my other post of AtrICS about "overscan" it's better explained.
In summary it's a software shrinked/overscan phenomenon.
Best regards.

Top Liked Posts

  • There are no posts matching your filters.
  • 764
    Olympus Kernel Project

    Project manager: jjwatmyself
    Development: krystianp, lehjr, Epinter, and mmontuori.
    Testing: zeljko1234, Hai_Duong, upndwn4par, Cocolopes, firecode95, Matada02, IM_back!, sidVici0us, Grey.Mouser, and ovitz.

    Issue tracking: https://code.google.com/p/kernel-olympus/issues/list

    m1k3_ was nice enough to open an FAQ thread http://forum.xda-developers.com/showthread.php?p=40125786

    • Off-Topic posts are not allowed
    • Only posts related to this project are allowed
    This thread is under strict moderation with strict enforcement of the rules posted above.

    A lot of time is spent by the team developing and testing. Make sure to support us any any possible way.

    ROM Alpha Builds:
    CM9: http://forum.xda-developers.com/showthread.php?t=2286515
    CM10.1: http://forum.xda-developers.com/showthread.php?t=2060064

    The official project source code repository is here https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus

    The kernel code is provided as-is and you assume all responsibilities in compiling/running the kernel code. Under no circumstance, the authors assume any responsibility on damaging devices resulting in running code posted on and related to this thread.

    The code posted is considered in development stage, and may or may not work. Only testers are authorized to post bugs.

    If you think you have a solution to a problem, send us a pull request. We will gladly look at it and merge it if necessary...

    This is a big project, so it's broken down into milestones:
    • Logs via JTAG [complete]
    • Boot Kernel on Olympus [complete]
    • USB Drivers [complete]
    • Boot Android GUI [complete]
    • Audio drivers [complete]
    • Headphone Jack [complete]
    • Accelerometer [complete]
    • Touchscreen [complete]
    • Buttons Backlight [complete]
    • Hardware/3d acceleration [complete]
    • Buttons volume up+down and power [complete]
    • Wi-Fi Driver [complete]
    • Bluetooth Driver [complete]
    • HDMI [post-poned]
    • Modem Driver [complete]
    • Fingerprint Kernel Driver [complete]
    • Fingerprint ROM Libs+Framework [work in progress]
    • Proximity Sensor Driver [complete]
    • Light Sensor Driver [complete]
    • Compass Driver [complete]
    • GPS [complete]
    • Sleep/Wake-up [complete]
    • A/C Charging [complete]
    • USB Charging [complete]
    • Camera/Video Camera [complete]
    • Front Camera/Front Video Camera [complete]
    • Flash [work in progress]
    • ROM Assembly [complete]
    • Mobile / Cellular voice calling [complete]

    Videos (chronological order last=latest):

    Donors: Manzing, Zeljko(x3), tmz83, chronicfathead, techlegend, Grey.Mouser, Franklee99, sirianni, donk, ebswift, jhonnyx, sendust7, fedegin, ScottyTheEngineer, buffalo06, r3xx3r, andrea_marcello, TheOnePom, ticiano_arraes, snaker23, wm_newbie, Fuzzypits, livadaki, vladeco, johnagelo, Mustkeg, sxg75, DannyBiker(x2), vitis586, Dazzel, scanuto, c2lover, r3xx3r, LFCxda, Vazay, jagiho, gcam1964, Doug_M, fastrite, Rockado, ddementiev, Night Walker!, cavava, t0mahawk, tsdedst, rabby80, jorgeavm, tonglebeak, ProudGrognard, terraformer, moderaterain, chonkit, Nicki760(x2), mchinand, ParfenR, John`, yuric, ~kyle(x2), trogdan, jisse44, Loki149, cncrd, mapeterson, J252, rumcajsz, grafithaka, kav64, sqkid89, clemare, saldirai, damn909, Infected24, leandrolnh, banjo76, chronicfathead, drekkschleuder, KrisM22, therox, praded2007, Clifton90210, renatotec, rustutzman, unicycler, blttalas, DJ_Squizzy, unekock, Babanenbieger, Taffy1881, fahadsadah, achaw, rspaulo, tsdedst, raitchison, chrismen83, kur41, blah4, Jazviper, 3dfxvoodoo, toomaiv, BaruchRamos, trogdan, smashen, futuremax2k, cheveoner, KCKitsune, chonkit, wm_newbie, Big-Bob, lamandrion, tchcaphr, thewarhawk, lionelbac, nikidorian, syngamer96, Starbomba, mchinand, baraev, demir76, ahmetcan44, leandrolnh, gnnash, J252, imarmand, galrock, tekmad, KrisM22, mrtynl, mrbitman, netinetinet, toomaiv, Sass86, Taren21, akrz, celli123, rigues, parquet, samiam21, 3dfxvoodoo, matteoclc, c2lover, gscastor, Darkcrush, TouchMeBell, zansatsu, rustutzman, Beenees, aaaviad, kisposi, torque, pgsmith68, sabtheleo, magiin, vitis586, farran, ScottyTheEngineer, vicfuze, chrismen83, Daws72, cmenekay, czarcorp, ddementiev, cmenekay, falcomer, babSky, sirkha, xyzwqt, runekock, nanohcv, jonbruce, kaiwid23, maddoka, Richy87, effractor, Level99. (for missed donors, please provide your xda username, donations did not contain it).

    NOTE: by donating, you authorize your alias to be displayed as donors.

    Donations are completely your choice, if you decide to donate, we welcome it. However, under no circumstances we are soliciting you to donate.
    You can choose to donate to the developer or tester of your choice, we will handle donations internally.

    Blog Status provided by jjwatmyself:

    Update 4/25/2013:
    Greetings planet Atrix 4G. It's been a long road and I am writing on behalf of the Olympus Kernel development team who have informed me that a public alpha release is imminent. This is an exciting milestone because you too will be able to play Temple Run, watch AnTuTu draw 50,000 triangles, experience performance that blurs the lines between ginger, bread, butter, ice, cream, jelly and donuts. The key to this lime pie will be your understanding the current status and that there are risks. Call them the ten commandments or ten steps to having a finger print that may not work when we are done... or may be it will.

    1) The kernel project waives any and all responsibility for damage to any and all devices, including your iPhone, your car keys, and your homework and your Dad's plasma. The builds provided are alpha, and represent danger. Permanent damage may result.

    2) The public Alpha release will be based on CM9 (ICS 4.0), CM10 (JB 4.1) and available without restrictions. The developers plan to merge trees into the current CyanogenMod-Atrix and the release will follow quickly this work.

    3) The FAQ thread (http://forum.xda-developers.com/showthread.php?p=40125786) is the place to post any and all bugs, installation questions or concerns. "Bluetooth..." "Wifi..." "I flashed and I can't..." "What about finger print..." "Webtop..." "What happened to my battery? (Crying)" "I flashed and it says..." "Can you lend me $5..." "How do you spell ACDC..." all belong on the FAQ thread.

    4) The official testers are the gatekeepers for bug entry at http://code.google.com/p/kernel-olympus/. You can see who's who under the People link on the main page.

    5) New bugs are subject to acceptance. If the bug does not meet the requested criteria on the Google form, it will be deleted. This means that our testers all have very sharp pencils. They are literally Ninja Warriors with one or more Atrix 4G to burn.

    6) Priorities related to bug fixes, enhancements, direction of the project are determined by the developer team.

    7) This thread is under strict moderation and serves to provide communication updates on the Kernel development. Hit thanks with confidence.

    Update 4/27/2013 12 noon US eastern:
    Greetings Planet Atrix 4G. It's been a whirlwind for the team over the past 48 hours with much positive progress. Everyone is pulling hard and the team effort is really paying off. Yesterday, there was some major work on building accuracy on status of issues, and their prioritization. The priorities at the present time are working on understanding battery usage and classifying bugs. It's imperative to understand that this is an alpha rom and that it is not a daily driver. Seriously, this is for testing on your spare Atrix. Our testers have been known to use an XDA issued hard hat and goggles (that's Goggles, not Googles for the non English speakers). Alas, a public alpha link has not been posted for these reasons, but it is so very close. Plus the XDA issued hard hats are only available in pink. To the Android software developers in our Atrix 4G community, that are patiently waiting for news on this release, we are excited that the public release is so, so close and hope that this renewal in the foundation can become the basis for additional ROM development work. To our larger community, your support continues to be epic and it is your continued interest in the work of the project developers and testers that fuels many late nights and long days. Hold onto your seats, it's going to get faster and more furious! Planet Atrix 4G will truly be amongst us soon.

    Update 5/6/2013 9:30 pm US eastern:
    Greetings Planet Atrix 4G. Just a quick update (picture a whale coming up for air). The development team continues to make progress, as shown on the bugs site. The focus is now related to battery drain during deep sleep. We want our beloved Atrix 4G to be it's battery sipping self that we know it is (ref MROM CM7). It's a multipronged effort with all developers working as a team on this important optimization phase of the kernel development. Also, there is life to tend to, so we have to recognize that the amount of time that is available on any given week will vary. Each developer's commitment to the project objective continues to be monumental. The community's interest in the project continues to fuel their motivation and the excellence in their work. Let the good code flow and cheers to all.

    Update 5/9/2013: <-- That's U.S. of A. date format, for all you non-Yanks.
    Greetings Planet Atrix 4G. It turns out that our developers are thanking their lucky stars for their XDA issued hard hats and they tell me they make the world of difference. Something to do with keeping brain waves in and RF from nearby cell towers out. I never thought they'd take to them like this, so I guess I finally got one thing right. Anyway, you may be aware that the development has shifted from public to private. This is part of a strategy to curb additional, premature public release. Simply stated, the public alpha release has not taken place yet. The team recognizes that learning how to compile code, makes for a seriously fun and gratifying project. I know when I compiled code for the first time I shouted down the hall "Mum, look what I made!" and she shouted back "Oh honey, that's really good!" (ref Google Search 'really good'). So, back to the subject at hand, the various guides out there are intended for use with finished code, or code you wrote yourself. There is plenty of it out there to play with, but as of this writing, this Kernel isn't one of them. For those of you that understand all the inner workings of writing, dissecting and compiling code, we are flattered and tip our hard hats, in respect and appreciation, for your enthusiasm and interest on the project. Stay tuned and we promise that information on progress and status will continue to be published here. The code will eventually be made public again and the good times will roll once again. We hope that this information and feedback is well received. We're all here for the same reason and remember, Planet Atrix 4G will soon be amongst us.

    Update 5/10/2013 6:30 PM US eastern:
    Greetings Planet Atrix 4G. I have some wonderful news. :) At 6:00 PM US eastern time today, an Alpha release candidate (Alpha-RC1) was made available to the official test team. Their test results will become the basis for the decision for the public release. I know, I know, you're jumping and cheering and doing kart-wheels and shaking hands with your neighbor across the street (unbelievable but true). The developers on this project are a solid team and they have worked so many wonders on our little Atrix 4G. Our test team has been particularly patient, waiting for this release. Their expertise in leaving no stone unturned is something that will help take this kernel to levels that developers alone simply cannot accomplish. Please remember that our developers and testers need all the oxygen they can get and there efforts are focused on the above directive. It's only a matter of time before the Atrix 4G takes over this little green and blue planet. It won't be called Earth forever!

    Update 5/18/2013 1:30 PM US eastern:
    Greetings Planet Atrix 4G! One week has passed… it’s been fast… it’s been furious… and much has happened!! To recap, a mere one week ago, our test team was presented with our newest Alpha build. Internally we called it Alpha-RC1. This was the most current work, with contributions from all of our talented developers. Well, let me tell you, our test team performed like no other. These guys put the T, E, S and T into testing. It is my privilege to witness the powerful dynamic at play within this team. So, back to the opening statement, much has happened! After last weekend, the test results were reviewed by the developers and testers. Their input steered the decision that the build would not be released. This was because we knew that the threads would become flooded with feedback on items we were well aware of. So as the week unfolded, an in-between kernel-update was released to the testers. It was called debug, despite having nothing to do with debug. Much was learned from this. Hot on the heels of debug, Alpha-RC2 was provided by the developers for testing. It is currently being taken for a spin and detailed analysis of performance, in many areas, is being conducted. This began a mere eighteen hours ago. Some of our testers have not even got any sleep! I have been told that the XDA issued hard hats apparently double as a pillow. Yes, it’s been a fast and furious week. If there is ever a time to be inspired by the work of others, this is certainly ranking near the top of my list. All who are reading this, please remember: this is ‘Not a daily driver’; it is ‘For testing only’; and ‘This is an alpha’. We know that ‘Love of Atrix 4G is strong in you, it is’. Please read the following sentence twice. We are working through logistics and preparing for of a public release. YES, you heard me (long pause) we are almost there… IT is almost here… WE hope you are ready. IT will soon be amongst us!

    Update 5/19/2013 5:00 pm US eastern:
    Greetings Planet Atrix 4G. It is my privilege to be able to announce to you the first public release of the Ice Cream Sandwich & Jelly Bean Kernel for Atrix 4G. This marks the combined efforts of our developers, krystianp, lehjr, Epinter, mmontuori, and testers, zeljko1234, Hai_Duong, upndwn4par, Cocolopes, firecode95, Matada02, IM_back!, sidVici0us, Grey.Mouser, ovitz, who have worked countless hours, regardless of hour of day. It is through our community’s continued and combined interest, support and enjoyment of this epic Tegra 2 device, that this release IS NOW AMONGST US. The public Alpha will be available soon as a CM9 and CM10.1 release, each having a dedicated thread. We will announce their going live here. We invite you to download and very carefully test. I would like to take this opportunity to congratulate the team and thank the community, as we celebrate together.

    Update 7/10/2013:
    Greetings Planet Atrix 4G. Much time has passed since the last update and we are all still here. Although there has been a slow down in activity, there has been continuous communication within the team. Just recently, Krystian produced two test kernels in order to understand some specific issues related to voltage changes under specific scenarios: with and without SD, wifi, Gps, while recording video, etc. These tests were designed to demonstrate hardware variations amongst the many manufacturing runs, where there were either component level differences, or components with differing tolerances. In addition, you may have seen the videos posted on YouTube, by Krystian, demonstrating improvements in device performance. The progress is consistent and with that said, we have an announcement.

    Effective immediately the source code, that was private has been migrated into the public realm. There are two branches:
    - CM 10.1 (4.2 JB) branch
    - ICS (4.0 ICS) branch

    The team is excited about this news, and we hope you are too. We believe that this provides a good foundation for many more advances in the future.

    XDA:DevDB Information
    [KERNEL] [3.1.10] Olympus (Atrix 4G) Kernel Project, a Kernel for the Motorola Atrix 4G

    mmontuori, krystianp
    Kernel Special Features:

    Version Information
    Status: Alpha

    Created 2013-10-06
    Last Updated 2013-10-07
    Update 04/21/2013:

    There has been lots of activity on the development and testing front over the past few days and I have become acclimated with much progress made prior to my joining. I found myself drawing a comparison to a relay race. For example, just yesterday Epinter revealed the results of working some of his usual magic and the day before mmontuori was doing the same. The testers continue to jump on testing as each cm9 and cm10 alpha build gets refreshed. Something to note is that the initial boot logo (M) is improved and progress is being made in the wake issues.

    There is no eta on the public beta (I was paid extra to write that) but at this rate I won't be surprised if I am asked by the team to read from a different sheet of music soon. It's fast and furious in the kitchen readers, so stay tuned please.

    Please remember that this thread is under strict moderation. Use the thanks button, and express your reactions in the general area please.

    More to follow and thank you for your continued support. :)

    Sent from my MB860 using Tapatalk 2
    Odp: Olympus ICS/JB Kernel Port

    Usb works :)

    Sent from my MB860 using xda app-developers app
    Next Phase... Exciting!!!

    We just finished clearing out the process for the first release path, the only item left out for now, it's the fingerprint driver, mainly because it also requires ROM changes in order to work, so for now, we decided to post-pone that feature until the second development cycle.

    Soon, we are going to declare a code freeze, meaning no more changes unless there is a bug report associated with it. This is a normal step in code development methodologies to maintain bugs and features under control. With code freezes also code changes are much smaller and targeted only to address problems. Easier to troubleshoot.

    I am really excited about how fast things are moving lately...