271 replies to this topic

[heffzilla]

For what lol

Sent from my DROID RAZR HD using Tapatalk 2

Lol, you beat me to it

Apple blows

[Atomicdsm]

For what lol

Sent from my DROID RAZR HD using Tapatalk

To party.

[trebills]

For what lol

For camera to be working. I got a major jones. This ROM is wayyyy smoother than Moto's version of JB

[Hashcode]

Hello!

Small update: As 1 or 2 of you noticed when syncing down the sources used to build this ROM, CM has made some adjustments in their QCOM support. And that effectively breaks the build for the HD.

I spent a day analysing some potential bandaids to get the build up and running again, and then looked at the kernel and what it would take to get the device into a prime position to support AOSP in the best possible manner (not just for Android 4.2 but going forward).

My thoughts were:
To keep applying bandaids and avoid the larger issues with the camera and graphics driver compatibility issues, would end up taking a lot of time to support and the device would never really feel "right" due to lack of features.

So yesterday I began work on a NEW kernel straight from QCOM, essentially same "starting" kernel that the Nexus 4 developers based their work on.

They used a branch from the msm kernel: jb_2.5 And you can find these sources here:

Please Login or Register to see this Hidden Content

What does all of this mean?

I'm taking the device back down to the metal and rebuilding it using updated (Jellybean 4.2 compatible) drivers. In many cases there will still be Motorola files in play here (radio, and some proprietary camera files), but in many other cases, I can drop stock files in favor of QCOM supported drivers which will be easier to keep updated as time goes on (read: Android 5.0)

Why go through the trouble?

It's all about the best way to actually run Android on the device. When you're trying to make something like the camera work and it's dependant on a driver in the kernel running a certain way for the OS, then the obvious answer is change the kernel. By doing so you create a very "compatible" Android environment which is easy to build straight out of the box in CM and other ROM flavors.

And that's the end goal: End up with a well supported, easy to dev device, which doesn't require many Motorola binaries to stay up-to-date.

Does it boot yet? How is progress?

I literally just got started. The kernel doesn't boot at all yet and I'll need a few days of work before I can even try some early boot tests.

So what now?

I'll check in with more progress later, but the next steps are:

1. Finish integrating all of the device drivers into the new kernel. Some come straight from the old 3.0 kernel, some need to be re-worked against the newer kernel sources and some will be pulled from other kernels (or used as an example).
2. Port forward any Motorola specific changes to the kernel. For instance there are many modifications to the USB driver to handle Motorola specific functions like docks and other features. Same goes w/ the charger driver, HDMI and video drivers. All of these customizations may need to be adjusted as they get added to the new kernel.
3. Then I run many many boot tests. Each one usually ending in a big crash log which are scanned through looking for bugs to fix.

Usually after a hundred or so boots in step #3, Android can finally be loaded and then the larger part of debugging can begin.

So it will be a bit before there is a "new" CM build, but the hope is that it's something which can be merged into their official device list and supported for quite a while to come.

Thanks for being patient

[arcanexvi]

Hello!

Small update: As 1 or 2 of you noticed when syncing down the sources used to build this ROM, CM has made some adjustments in their QCOM support. And that effectively breaks the build for the HD.

I spent a day analysing some potential bandaids to get the build up and running again, and then looked at the kernel and what it would take to get the device into a prime position to support AOSP in the best possible manner (not just for Android 4.2 but going forward).

My thoughts were:
To keep applying bandaids and avoid the larger issues with the camera and graphics driver compatibility issues, would end up taking a lot of time to support and the device would never really feel "right" due to lack of features.

So yesterday I began work on a NEW kernel straight from QCOM, essentially same "starting" kernel that the Nexus 4 developers based their work on.

They used a branch from the msm kernel: jb_2.5 And you can find these sources here:

Please Login or Register to see this Hidden Content

What does all of this mean?

I'm taking the device back down to the metal and rebuilding it using updated (Jellybean 4.2 compatible) drivers. In many cases there will still be Motorola files in play here (radio, and some proprietary camera files), but in many other cases, I can drop stock files in favor of QCOM supported drivers which will be easier to keep updated as time goes on (read: Android 5.0)

Why go through the trouble?

It's all about the best way to actually run Android on the device. When you're trying to make something like the camera work and it's dependant on a driver in the kernel running a certain way for the OS, then the obvious answer is change the kernel. By doing so you create a very "compatible" Android environment which is easy to build straight out of the box in CM and other ROM flavors.

And that's the end goal: End up with a well supported, easy to dev device, which doesn't require many Motorola binaries to stay up-to-date.

Does it boot yet? How is progress?

I literally just got started. The kernel doesn't boot at all yet and I'll need a few days of work before I can even try some early boot tests.

So what now?

I'll check in with more progress later, but the next steps are:

1. Finish integrating all of the device drivers into the new kernel. Some come straight from the old 3.0 kernel, some need to be re-worked against the newer kernel sources and some will be pulled from other kernels (or used as an example).
2. Port forward any Motorola specific changes to the kernel. For instance there are many modifications to the USB driver to handle Motorola specific functions like docks and other features. Same goes w/ the charger driver, HDMI and video drivers. All of these customizations may need to be adjusted as they get added to the new kernel.
3. Then I run many many boot tests. Each one usually ending in a big crash log which are scanned through looking for bugs to fix.

Usually after a hundred or so boots in step #3, Android can finally be loaded and then the larger part of debugging can begin.

So it will be a bit before there is a "new" CM build, but the hope is that it's something which can be merged into their official device list and supported for quite a while to come.

Thanks for being patient

Awesome to see you returning to our favorite device ;-) thank you for the update. You flying solo on this?

Sent from my DROID RAZR HD using Tapatalk 2

[Darbness]

So yesterday I began work on a NEW kernel straight from QCOM, essentially same "starting" kernel that the Nexus 4 developers based their work on.

So it will be a bit before there is a "new" CM build, but the hope is that it's something which can be merged into their official device list and supported for quite a while to come.

Thanks for being patient

Thanks for all your hard work.

I was just wondering if the kernel would be compatible with xt925

[koftheworld]

Hello!

Small update: As 1 or 2 of you noticed when syncing down the sources used to build this ROM, CM has made some adjustments in their QCOM support. And that effectively breaks the build for the HD.

I spent a day analysing some potential bandaids to get the build up and running again, and then looked at the kernel and what it would take to get the device into a prime position to support AOSP in the best possible manner (not just for Android 4.2 but going forward).

My thoughts were:
To keep applying bandaids and avoid the larger issues with the camera and graphics driver compatibility issues, would end up taking a lot of time to support and the device would never really feel "right" due to lack of features.

So yesterday I began work on a NEW kernel straight from QCOM, essentially same "starting" kernel that the Nexus 4 developers based their work on.

They used a branch from the msm kernel: jb_2.5 And you can find these sources here:

Please Login or Register to see this Hidden Content

What does all of this mean?

I'm taking the device back down to the metal and rebuilding it using updated (Jellybean 4.2 compatible) drivers. In many cases there will still be Motorola files in play here (radio, and some proprietary camera files), but in many other cases, I can drop stock files in favor of QCOM supported drivers which will be easier to keep updated as time goes on (read: Android 5.0)

Why go through the trouble?

It's all about the best way to actually run Android on the device. When you're trying to make something like the camera work and it's dependant on a driver in the kernel running a certain way for the OS, then the obvious answer is change the kernel. By doing so you create a very "compatible" Android environment which is easy to build straight out of the box in CM and other ROM flavors.

And that's the end goal: End up with a well supported, easy to dev device, which doesn't require many Motorola binaries to stay up-to-date.

Does it boot yet? How is progress?

I literally just got started. The kernel doesn't boot at all yet and I'll need a few days of work before I can even try some early boot tests.

So what now?

I'll check in with more progress later, but the next steps are:

1. Finish integrating all of the device drivers into the new kernel. Some come straight from the old 3.0 kernel, some need to be re-worked against the newer kernel sources and some will be pulled from other kernels (or used as an example).
2. Port forward any Motorola specific changes to the kernel. For instance there are many modifications to the USB driver to handle Motorola specific functions like docks and other features. Same goes w/ the charger driver, HDMI and video drivers. All of these customizations may need to be adjusted as they get added to the new kernel.
3. Then I run many many boot tests. Each one usually ending in a big crash log which are scanned through looking for bugs to fix.

Usually after a hundred or so boots in step #3, Android can finally be loaded and then the larger part of debugging can begin.

So it will be a bit before there is a "new" CM build, but the hope is that it's something which can be merged into their official device list and supported for quite a while to come.

Thanks for being patient

Thank you for the thoroughness of the explanation and your hard work. Don't hesitate to ask for community support for anything.

Sent from my DROID RAZR HD using Tapatalk 2

[jld]

That is great news. We appreciate all the hard work for sure!

[deeje]

Sweet thank you for all your hard-work man. Do you know if it'll be compatible with the atrix hd after all is said and done?

[jasonjw12]

Has anyone had a problem getting the Google music app to display the music you have in your account?

I've tried clearing the cache/data of the app and logging back in but it still shows nothing.

Sent from my XT926 using Tapatalk 2

[skinien]

Hello!

Small update: As 1 or 2 of you noticed when syncing down the sources used to build this ROM, CM has made some adjustments in their QCOM support. And that effectively breaks the build for the HD.

...

Thanks for the update, man! I appreciate the fact that you're choosing to do things the "right" way.

[Hashcode]

Thanks for all your hard work.

I was just wondering if the kernel would be compatible with xt925

Yes, in theory, the new kernel should work with all the new qcom devices:
RAZR-HD (925/926)
RAZR-M
Atrix-HD
Photon
etc

Sent from my DROID RAZR HD using Tapatalk 2

[dmartelle54]

You are a gentleman and a scholar!

Sent from my XT926 using Tapatalk 2

[desireaftergod]

You are a gentleman and a scholar!
+1
Sent from my XT926 using Tapatalk 2

Sent from my DROID RAZR HD using Tapatalk 2

[animez]

Great to hear you've decided to take the approach you are Hashcode. I would much rather wait a bit longer (even much longer) for a great kernel.

I can't wait to be running a stable fully functioning CM 10.1, this phone will be amazing then.

Sent from my DROID RAZR MAXX HD

[themrgoats]

Thanks so much man. This is extremely exciting news.

[eogans09]

Hello!

Small update: As 1 or 2 of you noticed when syncing down the sources used to build this ROM, CM has made some adjustments in their QCOM support. And that effectively breaks the build for the HD.

Thanks for being patient

I already wanna know where your DONATE button is...

[power9999]

Been testing this version does not work but GSM data ie 3G

[SquireSCA]

Very interested to see where this leads!