yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] baraev:
$ export PATH=/data/local/bin:$PATH

$su

#dmesg | grep LPDDR2

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR0: 0x0018 (0x1818)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR1: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR2: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR3: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR4: 0x0003 (0x0303)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR5: 0x0003 (0x0303)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR6: 0x0001 (0x0101)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR7: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR8: 0x0054 (0x5454)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR9: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR10: 0x0000 (0x0000)

<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR11: 0x0000 (0x0000)

#
[Atrix 4G Android Development] AeroMiku:
your dmesg log same as mine :D
[Atrix 4G Android Development] totoro1233:
root@olympus:/ # dmesg | grep LPDDR2

dmesg | grep LPDDR2

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR0: 0x0018 (0x1818)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR1: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR2: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR3: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR4: 0x0003 (0x0303)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR5: 0x0003 (0x0303)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR6: 0x0001 (0x0101)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR7: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR8: 0x0054 (0x5454)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR9: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR10: 0x0000 (0x0000)

<6>[ 0.000000,0] mot_parse_atag_motorola: LPDDR2 MR11: 0x0000 (0x0000)

this is my atrix elpida 40nm :D
[Atrix 4G Android Development] karakuzu06:
First thx all developers for their hard work,

I have checked issue tracking from this link https://code.google.com/p/kernel-olympus/issues/list and it seems that most of the bugs are same as that rom's kernel bugs. So I wonder even if we can solve most of the bugs is there any chance we can hit wall and cannot do anythig? (like camera bugs and so on)
[Atrix 4G Android Development] cpanos:
"that rom's kernel" bugs were unsolvable because there was no source code. This kernel is written by the devs, so dont worry, bugs will be addressed! They havent even finished adding all the drivers!

We (users) need to do two things on our side: a) be patient, b) support the devs (financially for those who can)!
[Atrix 4G Android Development] Clark Joseph Kent:
Members any type of Off Topic regarding April Fool's jokes of any nature will be DELETED on site.

Please report any type of Posting. There is an Off Topic Forum use it, Thank you for your time in this Matter.

Thread Cleaned.
[Atrix 4G Android Development] mmontuori:
Alpha Testing

Hi,

Just wanted to give you a quick update on the alpha testing. While I have not had time today to follow and work on the progress, the team has been busy, development and testing are working hard for you. Overall It's going pretty good, we have about 22 issues to address as posted in the issue database.

So we can say: we are 22 issues away from releasing a public beta.
[Atrix 4G Android Development] mmontuori:
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...
[Atrix 4G Android Development] mmontuori:
As we get closer to release, I went back in time with this impossible project... all the hurdles that the team had to overcome step by step and it is purely amazing that we made it to the stages we are currently.

But thanks to everyone for getting us to this point... especially to our amazing Krystianp....
[Atrix 4G Android Development] upndwn4par:
Truly an amazing effort. The team should be very proud of their work. :good:

The kernel is impressive. I hope everyone is able to temper their excitement and expectations since there is still work to do. But again, the kernel is impressive.

I could not get an accurate read on battery life due to some battery calibration issues, but it is way better than the leaked ICS kernel. I wouldn't say as good as CM7, but very good.

Were any of the testers those that previously experienced screen tearing? If so, was the issue resolved with the new kernel?
[Atrix 4G Android Development] krystianp:
I was having screen tearing issue. Generally anyone with WAR=1 (on leaked):

[ 0.222901,0] mot_panel_setup_dc: type=40, fast=1, SMD=3, TMD=0, WAR=1

should experience screen tearing at some point. Zeljko1234 had this issue even on our kernel. It's been fixed by now but it's not yet in git repo.
[Atrix 4G Android Development] sidVici0us:
To create the boot.img I follow the krystian instructions that came in this post http://xdaforums.com/showpost.php?p=38734398&postcount=708

steps were:

1. compile the kernel

2. copy the zImage and create the boot.img with the ramdisk come in zip in krystian post

3. Replace ko files of the modules that were in the zip (I eliminated those who could not be replaced with those compiled in the code)

5. rezip kernel_flasheable.zip

6. copy the zip to flash with clockwork ( all wipes )

7. reboot and fingers crossed

8. wait (small hope when the 2 logos appeared green)

9. Remove the battery and flash epinter CM10

10. go to sleep;)

Tomorrow I will try with ICS MROM to try start the gui

The time now is 2am and I have to be in the office at 8am, but I work as software development I can do it from the PC at work.

Thank you so much for responding! I will keep trying until it works or leaving the public beta version.

Greetings.
[Atrix 4G Android Development] Alex740il:
According to https://github.com/CyanogenMod-Atri...mmit/a8cfc72033a426206c1aa2fe88adaf0c8d262840 A/C Charge works (committed about an hour ago). :D:D:D:D:D I am hoping within a week should have a stable public release.. ;)
[Atrix 4G Android Development] sidVici0us:
New commit few minutes ago, bt fix!!!!

https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/commits/master

making and flashing ....
[Atrix 4G Android Development] sidVici0us:
You should review your thread reading lessons. What I did was install the new kernel 3.1.10 in MROM-ICS, so perfect working is about the kernel functions ( with reported bugs presents ). I use MROM as base rom to install my own compilation of kernel.

Moreover the version of MROM-ics originally comes with the 2.6 kernel no leaked kernel.

Placebo my panties :)
[Atrix 4G Android Development] jhonnyx:
Man, if you read properly, this thread is NOT about MROM ICS but a Dev-powered kernel compiled. User said he compiled the kernel found in the sources of the github by the kernel team and tried it with MROM ICS, so, in theory and practice it's NOT the leaked kernel.

If i'm not clear I suggest you read the entire thread to see what this project is about. Specially 1st post or, else, go to the discussion thread.

So the ecuation should be:

Rom + compiled boot image + brain = not-leaked kernel running with MROM ICS flavoured.

(oh yeah, baby, smooth as silk) (???)
[Atrix 4G Android Development] TravisAntonio:
This will be not too good for some users, but,

Will we be able to overclock the GPU now that the kernel is fully customizable?

Like rising voltages, or change speed of the GPU processor clock.
[Atrix 4G Android Development] mmontuori:
Overclocking is just a tweak, once is stable, yes you will be able to do so...
[Atrix 4G Android Development] mmontuori:
Overclocking

As I stated before, overclocking is just a tweak. We will tune the kernel once is stable, we have the default values in the kernel at the moment. For now is good.

Please keep the conversation about overclocking in the discussion thread...
[Atrix 4G Android Development] eagleeyetom:
Thread massively cleaned. Please keep it on topic and use discussion thread when your post is not related to development. Making comments like "thanks, can't wait" is just cluttering the thread and makes it harder to read.

Thanks!
[Atrix 4G Android Development] Chairsofter1138:
I realize that I'm adding to	the mess, but could somebody please start issuing bans to repeat offenders? I'm getting really tired having to read through all this crap to check in on the status of the project.
[Atrix 4G Android Development] eagleeyetom:
If the OP requests strict moderation, we can be stricter.
[Atrix 4G Android Development] rspaulo:
Wifi driver: [complete]

Nice!!!
[Atrix 4G Android Development] Andy:
I suggest you read the last few posts in a thread before you add your own. Failing to do so may in future limit your ability to post.

No more warnings.
[Atrix 4G Android Development] jorno88:
I built the kernel 3 times but always results in no signal. i'm on baseband N_01-100.00R and running MROM-ICS, tegrapart d00

Do you guys know what I could've done wrong? To my knowledge, signal should work...

bit more info: i flashed using krystian's zip file, did not update the ramdisk, only kernel and modules.

built from latest source with mrom defconfig

hare are 2 screencaptures:
[Atrix 4G Android Development] m1k3_:
I think the modules from modem have to be made apart from the kernel itself.

Sorry for bad english.
[Atrix 4G Android Development] eagleeyetom:
Guys and gals, the OP of this thread decided that strict moderation will take place. As moderators we agree with him and supports his decision, so there are the rules:

From now on, every unrelated posts will be deleted and possible warning infractions given. Please keep it on topic as much as you only can.

Thank you for understanding and cooperation.

Tom

Sony/LG/Motorola XDA Moderator
[Atrix 4G Android Development] mmontuori:
Testers

From this point moving forward, atrix4g18 is not an official tester anymore. But he is still providing the valuable off-topic thread.
[Atrix 4G Android Development] attrixnor:
Hello Devteam,

is there status update on issues list and driver listed ?

because i think there is not up to date (ex Defect - Accepted	- Battery Does Not Charge)

Thanks

Edit : i know it's not the most important , but for user who want to see the news :D it will be good
[Atrix 4G Android Development] mmontuori:
We have a new team member: sidVici0us.
[Atrix 4G Android Development] abaithad:
I got the same issue than you, try using MROM ICS-05-11-12 instead of the version dated on 14-11 it should fix it.
[Atrix 4G Android Development] IM_back!:
try a different radio it dosent work for me with N_01-100.00R either, ATT radios work fine
[Atrix 4G Android Development] blttalas:
try Atrix-MROM-ICS-20121105
[Atrix 4G Android Development] blttalas:
Issue

here is the signal bug
[Atrix 4G Android Development] Matada02:
We know this bug and the team is working on it.
[Atrix 4G Android Development] mmontuori:
Remember to keep the information in the bug database... posting about bugs here is counterproductive...
[Atrix 4G Android Development] blttalas:
BUG SOLVED

installition radios doesnt effect

install old mrom ics working perfect
[Atrix 4G Android Development] mmontuori:
Please PM me on this, I am not clear on this...
[Atrix 4G Android Development] blttalas:
PM sent
[Atrix 4G Android Development] dark_prince:
Just a thought about HWA (seeing its status as Partial)

Have you looked into Open-source Tegra Driver Grate?

https://github.com/grate-driver

My apologies if its not development related.
[Atrix 4G Android Development] mmontuori:
FAQ Thread

m1k3_ was nice enough to open an FAQ thread: http://xdaforums.com/showthread.php?p=40125786
[Atrix 4G Android Development] krystianp:
HWA is working but few apps shows some glitches (mxplayer). This needs to be fixed but it's not the highest priority for now. This issue wasn't addressed yet. That's why HWA still has "partial" status.
[Atrix 4G Android Development] scanuto:
Is it possible to use these open source drivers in the actual kernel?
[Atrix 4G Android Development] ravilov:
Why? Do you think they would be any better than what the kernel team came up with?

Those are kinda generic tegra drivers, I'm sure what the boys put together works better.

Plus, Krystian just said their own drivers work just fine, only some finetuning remains.

The team has known about these open-source drivers for a long time, I'm sure they used what was usable from them.

BTW this kernel is open-source too, you are free to try out these drivers yourself if you really want to. ;)
[Atrix 4G Android Development] shadowed87:
Yes the open source drivers are known for a long time but I guess the curiosity is due to the new 3D support that has just been added, which in the long term can lead to better maintainability, I guess...But of course the track they're following is the best one, it shouldn't be any need to look into the open source ones, now.
[Atrix 4G Android Development] epinter:
Why bluetooth is marked as work in progress ? What is missing ?
[Atrix 4G Android Development] sidVici0us:
For this problem, I also happened to the last alpha given by the development team.

Calling with Bluetooth speaker connected cause Freeze and reboot
[Atrix 4G Android Development] epinter:
Tested sending files and it works. I will test a call with bluetooth. thanks.
[Atrix 4G Android Development] mmontuori:
Epinter has been part of the team from the beginning, he was playing a passive role, we were in communication often, but now he is fully part of it...
[Atrix 4G Android Development] mmontuori:
Hi everyone. We are now looking for a project manager to help us with the management part of this project. Feel free to apply, only experienced people please...
[Atrix 4G Android Development] mmontuori:
Project Manager

Thanks to everyone for the interest in becoming a project manager. It was a difficult choice... but at the end we had to make a choice... jjwatmyself is the new project manager... help me congratulate him...
[Atrix 4G Android Development] sidVici0us:
Welcome to the team!!!!
[Atrix 4G Android Development] eZdubzitmk4:
What did you base your decision off of if you don't mind me asking?
[Atrix 4G Android Development] atrix4g18:
http://xdaforums.com/showthread.php?t=2193886

jjwat is a good choice.
[Atrix 4G Android Development] crazymania56:
JJwat welcome dude :victory:

Thx for taking care of us and management of the team :victory:

(LOL, I wanted to Say Thx from beginning :silly: )
[Atrix 4G Android Development] affiatic:
usb mass storage

I see the mass storage in bug list. I don't know if this helps or works with this kernal but with my galaxy note to use mass storage and transfer files to and from PC I have to use recovery (I use latest twrp). Sorry if this is unhelpful as I don't understand most of the project ( other than the goal you are trying to achieve)
[Atrix 4G Android Development] epinter:
Welcome jjwatmyself !
[Atrix 4G Android Development] jjwatmyself:
I'm thrilled to have been entrusted with this responsibility and thank you to all for your ongoing support and encouragement. Much has already been accomplished by the team and I'll work hard to maintain the course through to completion. Stay tuned for updates on the new Atrix 4G Kernel.
[Atrix 4G Android Development] joeygee23:
Congrats!

Pleasure meeting you and happy to have donated an Atrix to your efforts! Small world! 10 miles apart! Keep up the good work.
[Atrix 4G Android Development] xuefer:
the stock battd seems to read battery mA fine in epiter's cm10 (not kernel 3.x) rom

stop battd; start battd; sleep 1; cat /data/battd/powerup

measured: 4171 mV, 207 mA

C/5 table: 4243 mV, 100%

adjusted: 4243 mV

stored: 4218 mV, 100%

while i don't have yet a chance to try this ICS/JB kernel, i don't see any lead in the 3.x source providing current_now for battery. it's for charger only

it maybe too early to ask this feature request, but would really be nice to add ensure providing the feature for reading AC/USB/Battery current_now from /sys/***/cpcap***/current_now
[Atrix 4G Android Development] draxx31:
For bug, please use bug reporting on issue tracking code hosted in google code. Not here...

The link is in the first mmontuori's post.
[Atrix 4G Android Development] mmontuori:
Battd works fine on both cm9 and cm10. The kernel does provide the current_now for both usb and ac...
[Atrix 4G Android Development] jjwatmyself:
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. :)
[Atrix 4G Android Development] mmontuori:
The original intent of this project is not to get blur working, but to have a fully functional cyanogen ICS/JB.

I am going to try to answer your question in a way that it could clear some things for all users hopefully... worrying about the details at this point is useless, we just don't know what is going to happen. We have to first port the kernel code so that the Atrix accepts it and boots successfully. That is the most important phase right now, after that is successful, we don't know what's going to work and not work after the boot.

If we get a kernel ported and make it to the point that everything works but HDMI and WebTop, I would consider this a success, those problems will be handled as bugs.

Hope I answered your questions...
[Atrix 4G Android Development] upndwn4par:
Might not be a bad idea to add that info to the OP to avoid repeat questions and prevent false hopes for those wanting full blur functionality.
[Atrix 4G Android Development] Xehon91:
P3 club
[Atrix 4G Android Development] todobarato:
Hello,

I am in the P3 club too....but my wife have one new Atrix where was impossible to unlock the boot loader...I will check what for a version she have.
[Atrix 4G Android Development] krystianp:
It depends how much of blur related code from gb kernel is in ics leaked kernel. If it's the same or close then it should be possible if it rewriten and new then i don't think we'll get it. But as mmontuori said lets not go that far yet, we haven't even booted it yet.
[Atrix 4G Android Development] Zeljko1234:
IMHO, if we get working 3.1.10 kernel and then MROM JB I'll be happy :)

btw, P3 Olympus hardware
[Atrix 4G Android Development] VipeRsan:
And where you want get fingerprint drivers?
[Atrix 4G Android Development] vicfuze:
I am in to help test boot on AT&T Atrix. Part and rev below. ICSrom worked great for me except for the screen wakeup issues that forced me back to GB.

tegrapart=mbr:1100:100:800,

atag_revision=83f0
[Atrix 4G Android Development] Zeljko1234:
From leaked ICS.

Again, thread is about kernel. Please stay on topic and support developers work. Don't dream about something if primary thing (kernel) doesn't work.
[Atrix 4G Android Development] Lexord:
Please after this post, remember to keep the thread only with important info, so just post what is requested and useful. Thanks

Sent desde mi MB860
[Atrix 4G Android Development] ranjithkumar1201:
Thank you for you're hard work hope you guys succeed :thumbup:
[Atrix 4G Android Development] mmontuori:
Donations

For I would like to thank anyone donating to us for kernel development. I would like for everyone to know, that any donation made to me regarding Kernel development will be split with the development team.
[Atrix 4G Android Development] blttalas:
i want to help but i am a newbie
[Atrix 4G Android Development] Zeljko1234:
Then read post above your and donate few bucks ;)
[Atrix 4G Android Development] bigron77:
Mine shows atag_rev= 0x82d0

Tegra part= d00
[Atrix 4G Android Development] integraletotale:
tegrapart=mbr:d00:100:800

atag_revision=83f0
[Atrix 4G Android Development] Bert.C:
Can you get a dmesg log please?
[Atrix 4G Android Development] cailloup:
Willing to help, but I also have the useless

tegrapart=mbr:1100:100:800

atag_revision=83f0

rev P3
[Atrix 4G Android Development] krystianp:
There's no need for dmesg logs for now. I'm gathering information about used revisions, but when we make kernel boot, then we gonna need them to support as many revisions as necessary.

EDIT:

When the right time comes, we gonna publish our debuging kernel, so ppl with different revisions can get their logs with informations important to us. Casual dmesg log from any revision looks the same (from hardware programming point).
[Atrix 4G Android Development] bigron77:
This is my kernel log from the Getlogs app, i hope this helps...
[Atrix 4G Android Development] Menthis:
Dear dev team, you know why kernel has black screen after sleeping?Thank.
[Atrix 4G Android Development] blttalas:
Screen never opens when screen off (when calling) i must remove the battery

Can i write it to issue list?
[Atrix 4G Android Development] krystianp:
I know you all want to help. But until we have public release, for bug reports we have testing team. Not every git commit is treated as a fix or new feature. Sometimes they BREAK stuff. Sometimes they are work in progress. Keep that in mind when you test it. Testing team doesn't work on new kernel every new commit but rather after some time when we expect few things to work better. That is the reason why we work in closed enviroment for now. It helps us focus on real issues. Of course feel free to test it but please try to suppress your need to report bugs for now. You can of course help us developing and if you know what needs to be fixed feel free to do so that is more than welcome. I can't work 24/7 so sometimes commits are only a way to backup my code.
[Atrix 4G Android Development] mmontuori:
New Tester

We have a new test member. Grey.Mouser. Help me congratulate him...
[Atrix 4G Android Development] NooBs7yL3:
he has done a vary good work with the NottachTrix, hope he does the same with the test members :thumbup:

Inviato dal mio MB860 con Tapatalk 2
[Atrix 4G Android Development] atrix4g18:
Come here to congratulate him.

Since I already have this post: I agree; glad he is on the testing team.
[Atrix 4G Android Development] jjwatmyself:
Blogging it out...

See post #1 for an exciting update. :highfive:
[Atrix 4G Android Development] Xerox98:
Does this mean that a public beta is nearing? Because that update looks like a preparation for a public beta release!

I am not asking for an ETA, merely just if that post is meaning that the beta is nearing..

* Off-topic*

I would also like to say that I have been following this thread since day 1 and the progress that has happened here is AMAZING. This thread alone has stopped me multiple times from buying a Nexus 4, just the thought that one day this phone will have a fully working CM10.1 is holding me back, because I know that this will happen.. I would donate, but PayPal is not currently in my country.

All of the best.

Xerox98.
[Atrix 4G Android Development] cailloup:
If you really need it in other words: yes, a public

alpha

is

nearing