yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] IanTester:
No, the situation with ARM systems is very different. There's been a lot of work done over the last few years (after Linus threw a fit) to try to unify Linux kernels for ARM hardware. The big problem is that a lot of the peripherals in a SoC are not enumeratible. You know how you can see what PCI/USB/etc devices are connected to your PC? Well, that's not the situation in an ARM SoC. The only way for the kernel to know what is hooked up, and where (memory, interrupts, etc), is to be given the information in a "board file" by the bootloader.

At least, that's what many developers are working on. I don't know how much of the "board file" system was already in place for the 2.6.3x kernel we're currently using, and how much came later.
[Atrix 4G Android Development] mvniekerk:
TL;DR : The approach is to gut out Xoom specifics with Atrix ones, with enough Xoom-iness that the thing boots up.

The DD-the-bootloader will not work, as the GPIO (general input-output) lines of the Atrix and the Xoom differs - you could seriously damage your hardware if a line is pulled high on something that is not suppose to have a voltage applied to it...

A Lesson On Kernel Drivers:

On platform init (where I think most of the work should be done), you ramp up your voltages and start up your clocks. After that, you register your platform data.

What are the platform data, you might ask?

A C struct, with names of peripherals and maybe some parameters.

The kernel, upon run-time, registers a list of drivers, handling certain peripherals (identified by their names).

So, when the kernel runs through this c-struct of peripherals and looks for a suiting driver (by comparing, you guessed it, their names).

If a suitable driver was found, then the parameters are passed to the driver, and the driver's init function is run. The driver, in turn, returns whether or not the driver was correctly inited... Most of the time upon errors your board crashes. F-offs into oblivion.

Lesson done.

So, the Galaxy R question. A good one - as far as I know there aren't that much kernel fiddling done between ICS and JB, and as both the Atrix and the R uses the same SOC, it would be a more natural fit.

A good argument then for the R's code. But - it is not a Nexus device, as the Xoom is. Goodness, a Tegra2/Moto device without being shafted, don't hear about that too much often òÓ

So, low hanging fruit, then, the Galaxy R... I'm going to stick to my guns with the Xoom, as it is more supported (no official we're-hitting-JB-for-the-R from Sammie's side). For now, at least.
[Atrix 4G Android Development] Franklee99:
What a f-ing legend.. wait for it.. dary statement! You rock man!

And bonus kernel lessons.. sweet!

Cheers to you.
[Atrix 4G Android Development] v-stromer:
Just a suggestion but you might won't to look at the advent vega.

It was one of the first tegra 2 tablets to be released.

It came with android 2.2 and was never updated, but the devs did a great job getting bits and pieces from the xoom and other tablets,

It did take a long time but they did it.

First with honeycomb then ics.

Right now I'm running jelly bean on it and it works great.

Some of the hard work might have been done and it might be a bit easier than starting from scratch.

Like I said just a suggestion.
[Atrix 4G Android Development] Bert.C:
Is this still of no use? Even though we now have the proper libs?

... http://xdaforums.com/showthread.php?t=1876421
[Atrix 4G Android Development] diditst:
Thanks, This thread good for learning,

As a newbe, I have question what is relation between kernel and android version from google?

Thanks from newbe
[Atrix 4G Android Development] Zeljko1234:
v-stromer, thank you for really useful suggestion. I suppose that all code is available and developers are willing to share and cooperate?
[Atrix 4G Android Development] v-stromer:
Well over on modaco and tableroms there is still active development going on but not so much on xda.

But I don't see why not the devs over there are very helpful.

modaco has the source code posted.

http://www.modaco.com/forum/474-advent-vega-vegamodacocom/

http://www.tabletroms.com/forums/vega-rom-development/

Thanks hope you guys do it :)
[Atrix 4G Android Development] mvniekerk:
Stage one of copying the files into the olympus specific ones finished.

The kernel compiles. Will not bring it near my hardware though...

What I've done is to copy all the board-stingray-* to board-olympus-* and made sure the configs line up. Change some STINGRAY configs to OLYMPUS.

Just an update for y'all. For warm and fuzzies.
[Atrix 4G Android Development] Rhadamg:
I'm not afraid to test it on mine. Well... if possible, take a look at voltages to check if they match to the correct values of Atrix and let me know. I'll be glad to test here.
[Atrix 4G Android Development] mvniekerk:
That is a very, very bad idea.
[Atrix 4G Android Development] Vanilla2001:
I like this way, really much... Keep us up to date!
[Atrix 4G Android Development] Kahbrohn:
"Mommy... Daddy... Where do baby Atrixes come from???"

OP... Kudos to you for this project. I may not be able to follow 10% of what you are saying but I understand what you are trying to do. Thanks for keeping the Atrix "alive", if not interesting. If you ever get to a stage where testers are needed, let me know.

Uncle Kah
[Atrix 4G Android Development] xangma:
Got a Xoom and an Atrix, so if there is anything you need me to do, just let me know.
[Atrix 4G Android Development] stlifey:
http://sourceforge.net/motorola/atrix

Maybe moto need some pressure? Don't forget the GPL,we need kernel source of leak 2.6.39 kernel
[Atrix 4G Android Development] antmiu2:
dont know if this is relevant or not but the Samsung Captivate Glide also has a tegra 2 chip and its updated to ICS!!
[Atrix 4G Android Development] Zeljko1234:
I'm not sure that Motorola must release source for leaked kernel, only for official release.
[Atrix 4G Android Development] mvniekerk:
As far as I know, if it is shipped / sold to customers, then it must by opened. If it is internally used/tested, not.
[Atrix 4G Android Development] dedebekri:
Is there any progress on your porting project? Just curious :D
[Atrix 4G Android Development] mvniekerk:
Nope, maybe tomorrow another hour in it.
[Atrix 4G Android Development] dedebekri:
Looking forward to your good news, thank you.
[Atrix 4G Android Development] Hai_Duong:
Great to hear that is going on. Truly the Devs are really the only hope when the smartphone is going to be dead.. I got my Atrix 2weeks now and wait because there is more hope to get a perfect-stock (maybe better) ICS :D
[Atrix 4G Android Development] Pistolaobr:
Hey dude, the kernel + libs from the leaked Motorola rom ICS v6.7.119, is running flawless on atrix tegrapart ATT, however, on our atrix bell tegrapart 1100 and D00, it makes the smartphone restarts when we have sdcard inserted, prox sensor is bugged, the CPU clock is crasy, goes up and down all the time, and the screen is shaking in some cases, and the battery burns like a frying pan, all seems to be energy related, cause if we, bell atrix users, plug the atrix in the wall charger, all thouse bugs disappear.

Well, I'm begging you here, please, please, please, can you make us a unified ICS kernel based on the leaked v6.7.119 (AtrICS rom), so we can at least use the leaked version on bell atrix without bugs. Many thanks man, it should require a lot less work than porting xoom kernel to atrix.

And I will donate of course.
[Atrix 4G Android Development] Zeljko1234:
I must add that screen shakes on ATT version. Probably not so bad but always after long period of inactivity.

With rest I agree :)
[Atrix 4G Android Development] ticiano_arraes:
Since we dont have the source code from the kernel, I dont think this is possible
[Atrix 4G Android Development] Zeljko1234:
Everything is possible. What do you think, who makes Motorola kernel? Aliens? :D

Of course, it will be much easier with source or technical documentation.
[Atrix 4G Android Development] ticiano_arraes:
A team of devs with the necessary tools. I'm not saying it's impossible to make everythink work, I'm saying it's impossible to edit the kernel without the source because it is. If we want to edit this kernel, we need to someone leak the source or develop a new one
[Atrix 4G Android Development] Jotokun:
No. Motorola made the Motorola kernel. Without source code, its 100% useless for any serious project because it cant be modified. At least, not without a crapload of reverse engineering. The goal of this project is to get us an AOSP friendly kernel that'll last us a while and will be easily updatable. Hacking a compiled binary might eventually yield a sloppy CM10 that works alright, but that's where things would stop.

I mean no disrespect to those trying to make a usable rom out of it, and hope the battery issue and screen shaking gets worked out. But its only a temporary solution. Even if we did get it working perfectly, it would be better to start on this now rather than when we'll really need it.

Long term, this is a far better solution. Probably is an easier one as well as anyone working on it isnt completely blind.
[Atrix 4G Android Development] Zeljko1234:
It's possible with dis-assembler but is hard. I saw only one guy on xda who did such thing, snq-. If we have problem with voltage, clock, power management settings in kernel or similar this approach could work.

But all you have right. Source or new kernel will be much better solution.
[Atrix 4G Android Development] Cocolopes:
Sorry if this is not useful. But I remember that in my DEFY with bootloader locked (so no customs kernel) we could have undervolting skills and much more using files *.ko or modules or something like that.

Sorry if I can not give accurate information.
[Atrix 4G Android Development] Zeljko1234:
I appreciate any suggestion :)
[Atrix 4G Android Development] Lexord:
So have someone tried something?

Sent from my MB860
[Atrix 4G Android Development] Cocolopes:
I ask quarxs for some help in undervolting and here is the conversation:

I dont realy know what are the hooks...but if someone understand maybe we can do something :p

I dont know where to share this info....sorry if is off topic

Edit: http://en.m.wikipedia.org/wiki/Hooking#section_2 now I understand about the hooks!

from the (m)ATRIX...
[Atrix 4G Android Development] Zeljko1234:
Please explain why is "very irrelevant". He's trying to help and every suggestion, every dig, could be useful.
[Atrix 4G Android Development] ravilov:
Do you know something we don't? Please share.
[Atrix 4G Android Development] voncount:
Yes, your post and mine now are irrelevant.
[Atrix 4G Android Development] Hairo The Blue Mage:
don't get me wrong, but i don't feel this thread is going anywhere...
[Atrix 4G Android Development] Zeljko1234:
Don't get me wrong but why did you make discouraging post? What do you expect? Porting kernel in few days? Do you understand how hard it is and how many knowledge required?

This tread is made by guy who has knowledge and willing to use it. If you cannot contribute just follow without posting, please.
[Atrix 4G Android Development] Hairo The Blue Mage:
i was not talking about the kernel porting, it was for the "irrelevant" thing, my intention wasn't discouraging, sorry about that...
[Atrix 4G Android Development] Zeljko1234:
OK, then :)
[Atrix 4G Android Development] mvniekerk:
Seems as though (according to the different hardware revisions) there are different SDRAM timings, on different sized RAM chips (this is on the XOOM). And all of this is set in a neat struct.

Now where do these timings gets set for the Atrix... A lot of things can go gloriously wrong if these are set incorrectly (especially if it overclocks our RAM chips into kingdom come). Hope it is set in the bootloader, will relieve a lot of work.

Investigation ensues...

For an update - I'm renaming a lot of Xoom symbols to Atrix (thus stingray -> atrix), commenting out hardware revision stuff out where I go.

And for those who are waiting for a new kernel by the end of this week, keep on waiting... I'll update this thread on progress.
[Atrix 4G Android Development] grim_ripper:
Just out of curiosity, how does webtop come into the picture eventually?
[Atrix 4G Android Development] mvniekerk:
Does the Xoom have a webtop? Then, no, really. Unless there are others to take up that, but I don't have a webtop, so cannot test jack.
[Atrix 4G Android Development] cupidstunt:
Have you tried speaking to clemsyn. He had some reference to memory timings in his kernel thread.

http://xdaforums.com/showthread.php?t=1354502
[Atrix 4G Android Development] syngamer96:
Some suggestions.....

So, as far as this thread goes, we have clemsyn, faux123, mmontuori, quarxs and snq- who might be able to help us in terms of creating the kernel, be it from a knowledge or physical work perspective.

Our dear mvniekerk, also clarify with a few devs from the samdroid forums, like tom3q, voku1987, Xmister, gotenks and criminal. Tom3q especially, he managed a 3.0++ kernel for the crappier Samsung phones like the Spica etc. If I'm not wrong, he's here at xda, although I think all of them are as well, maybe under a different name.

From the Samdroid forums: http://forum.samdroid.net/f53/howto-cross-compiling-android-kernel-5086/#post150345

This comes from voku1987, where he says cross compiling a kernel can be done through a Linux platform. Although he did mention Ubuntu, Debian etc, I'm guessing we can cross compile I'm that manner or use some of it to help us. Not sure any of it can be used though, just trying to suggest. Hope this helps in some way.
[Atrix 4G Android Development] nicks90:
has anyone approached championswimmer, who runs the kernel kitchen? He might have some advice and help.
[Atrix 4G Android Development] Franklee99:
Have you? :)

Seriously though, if you think you know someone who could assist, ask them to contact the main developer here etc.

I'm sure any offers of assistance would be considered. :)
[Atrix 4G Android Development] Zeljko1234:
Maybe could be useful LG Optimus 2X ICS Kernel Source Code. At least to find out proper hardware access.
[Atrix 4G Android Development] syngamer96:
I agree. Certain things can be cross-used with our atrix. But, so does the other Tegra 2 phones and the Xoom, only just not to a far extent. We should also keep in mind that we have to scan the respective hardware used, such as the ram chip, processor model (AP20H and all the other blahblah) and all the other tiny little bits that the kernel has to order around lol.

My exams are ending soon, and I'll have a bit more time off to inspect based on articles, FCC filings and all the other data regarding these devices to look for clues. I'm no developer, but I do intend for our devices to work like the newer phones on the market :D
[Atrix 4G Android Development] Pistolaobr:
Yeah, do you think that it could help:

www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU660

At least it would give some help on the kernel since it is the same tegra2 chipset.
[Atrix 4G Android Development] Zeljko1234:
Maybe mvniekerk could gather all the pieces of code and make the kernel. He's following the thread :)
[Atrix 4G Android Development] mmontuori:
Reaching out

Just to let everyone know, I've already reached out to mvniekerk. Sadly did not succeed. All it matters for now is that a new kernel can potentially arrive, and that mvniekerk has the time to work on it.

This makes me happy either way, helping or not, it does not matter...
[Atrix 4G Android Development] Zeljko1234:
Makes me happy to
[Atrix 4G Android Development] marcovrv:
mvniekerk was quite specific in his (long term) objective: "fork" an Atrix 4G kernel from Xoom kernel source since the "Xoom" is a Nexus device (supported directly by Google) and should have more upgrade life than any other device (so long, just a couple of old Nexus devices stopped being supported by Google). This would also mean almost "automatic" pure AOSP updated releases for the Atrix 4G. As I undertand it, the deviation from AOSP code should be kept at the minimum possible, so any inclusion of foreign code must be taken as an absolute last resort.

The other approach is to adapt similar phones' kernels to the Atrix, but this path might end once the respective manufacturers stop support. Maybe none of these AP20H phones will get past stock ICS. However, as mvniekerk said, this is "low hanging fruit" and it might worth the try by other developers as an interim, short term, solution.

I would like to view this as two development threads from the Atrix Rebirth Project POV: 1) short term "LHF" kernel and 2) long term "AOSP synced" kernel.
[Atrix 4G Android Development] deathscream:
Samsung galaxy R , another tegra 2 device , has the same architecture as atrix 4g.

The kernel source is here https://github.com/ardatdat/GalaxyR-i9103-Kernel
[Atrix 4G Android Development] syngamer96:
Duuudee... this has been discussed millions of times.... chill, let the devs do their work with all this... there's nothing much we can do to use other devices as our source of code. We know the processor is the same blahblahblah, but other aspects like the ram chip, camera and whatnot, ESPECIALLY the fingerprint scanner, might be different. So, until each piece is clarifies, chillax and wait ;)
[Atrix 4G Android Development] Franklee99:
Preaching patience in a smart phone forum... Good luck with that. Jk ;)
[Atrix 4G Android Development] Zeljko1234:
Patience is fine, same as every suggestion. Comments that something is useless is actually useless :)
[Atrix 4G Android Development] syngamer96:
Haha, one simply does not preach patience without being patient himself. Uselessness simply implies, well, uselessness. K lol I'm being a dumbass here. Let's just enjoy the wait and live life to the fullest while waiting eh?

:D :D :D

Anyway, I think if there is a need for me to pick up coding, I'll probably do so, but when I learn one chapter, you guys will probably get to a stable Key Lime Pie build, complete with a stable kernel haha :)
[Atrix 4G Android Development] ravilov:
LOL. Just as people were talking about patience...
[Atrix 4G Android Development] Jotokun:
Think of it this way... if there's progress, you WILL hear about it one way or another. If smaller progress, the OP may make a post. If bigger progress, you'll see other threads about it or roms getting a major usability boost. Think like the ICS leak... people kept asking, but they didn't need to because when it happened a billion new threads were made about it.

Asking just adds needless clutter to a thread. It also disappoints those who see it bumped and check the new posts for genuine progress or worthwhile discussion.
[Atrix 4G Android Development] ravilov:
Exactly.

Plus, people kept asking for the leak, but it's not like them asking constantly actually speeded up anything. Pretty sure the leak would've been leaked whenever it was leaked either way.

Also...

That's a contradiction in terms. If you were indeed patient, you would be able to restrain yourself from asking. The mere fact you asked means you are (or are getting) impatient.

Just saying.
[Atrix 4G Android Development] mvniekerk:
I got a day job you guys. I'm still on it. These me too posts are muddying up the water.

Actually looking at the LG P990 code now as it is a later version of the kernel than the Galaxy R.

Keep it real stalkers
[Atrix 4G Android Development] greenolive:
You post a lot.
[Atrix 4G Android Development] Cab121:
If i remember correctly a hook or hooks is a code used to short cut a code string to another one. Much like a shortcut. Could be wrong but if you can do that the it doses matter what boots.

Been a while since i dabbled with that.
[Atrix 4G Android Development] ravilov:
Huh? So? Is there some quota on posts?
[Atrix 4G Android Development] Zeljko1234:
Could you please look at the LGSU660 (Optimus-2X) kernel source?

Latest Atrix makefile:

VERSION = 2

PATCHLEVEL = 6

SUBLEVEL = 32

EXTRAVERSION = .9

Latest LGSU660 makefile:

VERSION = 2

PATCHLEVEL = 6

SUBLEVEL = 39

EXTRAVERSION = .4

Interesting date of LG kernel:

#

# Automatically generated make config: don't edit

# Linux/arm 2.6.39.4 Kernel Configuration

# Wed Oct 24 21:07:17 2012

For someone as you, should be posible to adapt LG kernel for Atrix.

Direct links:

http://sourceforge.net/projects/atrix.motorola/files/latest/download?source=files

http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU660
[Atrix 4G Android Development] attrixnor:
correct me if im wrong , but the 2.6.39 kernel work with the tegra driver

because the screen work of atrix is ok and 2D work too. but the mistake is the hardware acceleration..

so i suppose that the actual driver use from the leak isn't good or finish ?? or possibility : a specific information (driver , files , id ...)is missed on the kernel because it's strange that this HW doesn't work now from the leak,

if it come from motorola , ics was promise soon so if this leak was too bad , it doesn't come to us ???
[Atrix 4G Android Development] Ilkinansr92:
???????????????????????????WATTT?????????????????? :confused: :eek:
[Atrix 4G Android Development] attrixnor:
resume : why HW acceleration don't work
[Atrix 4G Android Development] Zeljko1234:
Of course could be that we have unfinished libs, but libs came from nVidia. Libs work with other Tegra devices. Libs from other devices work with our leaked kernel but with the same bug, screen tearing. So we blame kernel. In my opinion, some settings, voltages etc. are wrong in our kernel. Because we don't have source, we cannot easy find a bug. I suppose, kernel source from LG is possible to adapt for Atrix.

One of developers could say more :)
[Atrix 4G Android Development] tpr0:
The Tegra 2 layers are always different from each phone...

For example:

The O2X kernel uses I2C communication to the DAC, + the DAC layer of that SoC tegra 2 is modified by LG =! Atrix DAC layer...

^ that is one of the simplest incompatibilities...

I don't there is anyway are around it, porting/using lib from A to B, hope it is possible....
[Atrix 4G Android Development] Zeljko1234:
I remember that epinter tested libs from another phone. I think from Galaxy R and it works but with the same screen tearing bug.
[Atrix 4G Android Development] attrixnor:
.........................................
[Atrix 4G Android Development] AkaGrey:
Yes but with our kernel

Inviato dal mio MB860 con Tapatalk 2
[Atrix 4G Android Development] Cab121:
The battery life problem is a symptom of a much larger bug. The logic board heats up. In some cases way to much. The misuse of voltage by the rouge kernel is the primary cause of this but most of us are well aware of this. The side effect of voltage running through the logic board unthrotled drains the battery quickly. So again a kernel is the solution here. Sorry folks.
[Atrix 4G Android Development] attrixnor:
it's more clear now

thanks for this reply
[Atrix 4G Android Development] ingelectronico:
I remember when I had a Motorola Milestone phone and there was a trick to change the processor frequency and voltage sets by editing a couple of text files somewhere in the system tree.

I'll try to find the patch method and post it for someone to check whether is possible to replicate in our atrix.

Best regards.

---------- Post added at 11:23 AM ---------- Previous post was at 11:19 AM ----------

This is the link to the milestone overclock project page

Http://code.google.com/p/milestone-overclock/
[Atrix 4G Android Development] Cocolopes:
We have to use kernel modules or kernels hooks

http://code.google.com/p/milestone-overclock/wiki/KernelModule

I said this before...but I think is not possible. :(