130 replies to this topic

[animez]

Shut up and take our money!

Please Login or Register to see this Hidden Content

 

Please Login or Register to see this Hidden Content

  13.67KB   181 downloads

[llawen]

Still hard to grasp. Unlocked boot loaders....and now custom kernels. That was just a wish at one time.

Sent from my DROID RAZR HD using Tapatalk 2

[koftheworld]

Hi Guys,
 
I thought I would get a thread going on this as I'm moving along (rather slowly -- I'll admit) on developing a new kernel for the Motorola QCOM phones.  Obviously I will be testing it against the RAZR-HD, but if done correctly it should support RAZR-M, Atrix-HD and Photon Q.
 
Why a new kernel?
For full Android 4.2.x support we need to migrate to a fully redeveloped video system which include vsync, fencing and other major changes from the 3.0 kernel.  We have tried to backport some of these changes with some success but in the meantime it's causing other side effects.  Along with the video driver updates are camera subsystem and many many other updates.
For the future of the device we want to stay as close to Nexus type devices so that we can compile AOSP out of the box so to speak.  N4 (Mako) uses a 3.4 kernel based on the same exact branch that I'm using from Code Aurora Forums (CAF).
 
What sources am I using?
 
I've started on the CAF base branch "jb_2.5" used to bring up the Nexus 4 device:

Please Login or Register to see this Hidden Content

 
 
And the new kernel source is on github under a "razrqcom-dev-team" where Pinter and DHacker and others can all join in:

Please Login or Register to see this Hidden Content

 
[NOTE] I have NOT posted my local changes to that kernel yet.  It's the CAF sources + 2-3 commits I cherry-picked in, currently.
 
 
Current Status:
[DONE] Add all new drivers from the Motorola JB kernel posted on Sourceforge.net
[DONE] Patch existing code with Motorola specific changes (in a minimal sort of way -- only what is absolutely required here)
[DONE] Fix compile errors
[IN-PROGRESS] Boot testing using a recovery.  Have to get far enough to where I'm seeing a ram-console "last_kmsg".
1-by-1 debug each driver using last_kmsg to where we get a fully functioning recovery build.  This includes using binaries like evtest to debug touchscreen events, and other sensors.
Change over to a full Android build using CM sources which are fully patched up against CAF's latest sources: includes new hardware drivers for video, camera, audio and others.
Debug the Android boot using strace and other binaries till it's solid enough to start using specific apps to play test and debug issues.
Once I get to a point where I can post a full dmesg, I'll add that to this post (for those that are curious).
 
Thanks for being patient.

Good on fixing number 3 btw hash.

sent from my xt926 RAZR maxx hd

[BootAnimator]

Just out of curiosity, will it require Moto to release some of their source to get everything working properly? Not really literate in kernel info. Or is it more of the hardware side of things that need to be released? Like needing QComm source? For video fixes...etc. or can that all be fixed with newly written code.....or.....?

[RikRong]

It's nice to see the words "kernel" and "development" together on a Motorola forum.  Good work Hash.  

[megahertz1970]

I so can't wait for this. Got a little taste of it running the PACMAN ROM for a night. Love the customization it has but it wouldn't send picture messages which is a deal breaker for me. Other than that it almost seemed good enough to be a daily driver. Keep up the good work! You'll get it eventually. I wish I knew how to do this stuff and had the time I would help.

[RikRong]

I so can't wait for this. Got a little taste of it running the PACMAN ROM for a night. Love the customization it has but it wouldn't send picture messages which is a deal breaker for me. Other than that it almost seemed good enough to be a daily driver. Keep up the good work! You'll get it eventually. I wish I knew how to do this stuff and had the time I would help.

I was able to pull a MMS.apk off of XDA and replaced the one that was included in a CM build I was using.  It worked like a charm.  

[sfg]

I so can't wait for this. Got a little taste of it running the PACMAN ROM for a night. Love the customization it has but it wouldn't send picture messages which is a deal breaker for me. Other than that it almost seemed good enough to be a daily driver. Keep up the good work! You'll get it eventually. I wish I knew how to do this stuff and had the time I would help.

I was able to pull a MMS.apk off of XDA and replaced the one that was included in a CM build I was using.  It worked like a charm.  

Can you share it please

Sent from my XT926 using Tapatalk 2

[RikRong]

Can you share it please

Sent from my XT926 using Tapatalk 2

 

This is the one I used when I was on Trippin' Bean.  Marxman incorporated it and there were no problems with MMS after that (as far as I know).  I know it's in the ATT forum, but it worked perfectly for me. 

Please Login or Register to see this Hidden Content

[Hashcode]

Got my initial Motorola changes for 3.4 updated to github:

Please Login or Register to see this Hidden Content

 

 

Took a while, now back to debugging the initial boot sequence.

[eck79]

Hash, really appreciate your work. Equally as important we really appreciate you keeping us up to date. So much easier to be patient and supporting when you've taken the extra time to update the OP as you have. You're going above an beyond! Fantastic!

[desireaftergod]

Hash, really appreciate your work. Equally as important we really appreciate you keeping us up to date. So much easier to be patient and supporting when you've taken the extra time to update the OP as you have. You're going above an beyond! Fantastic!

1

[jpmorris123]

Thanks for updating the OP.  It's great for us non-devs to get a peek at the steps for building a kernel.

[rebretz000]

<br />Ignore me. I a moron<br /><br /><br />Sent from my DROID RAZR HD using Tapatalk 2<br />

[Hashcode]

Motorola releases source on sourceforge.net/motorola.  They are actually quite good about it.

 

The source for the xt925 and xt926 is shared.

[divadem]

First and foremost I want to thank you Hashcode for taking your time to make this kernel from the ground up. I have no idea what that entails but your work gives me a very general idea of what is going on and the time and effort put into this is amazing. Thanks, my Razr HD would be very boring without you.

Would an app like PGM Galaxy Nexus (which enables slide to wake without touching the power button) be possible on the kernel you are building? Any plans to put in this awesome feature? I sorely miss this useful feature on my nexus and would gladly purchase an app( or other support) to enable this premium feature on your custom kernel in the future. I don't know how difficult this would be but I hope you consider it.

My Reasons for Slidetowake include:

- Great for waking your phone with any hand, no need to stretch fingers.
- Save stress on mechanical buttons
-Easier to unlock phone while it's lying on surface without grasping phone.
-possibly better for left handers.
-iPhones can't do it, they still use mechanical means of waking phone, same circle button used since the first iPhone( let's use capacitive ).

This can be achieved with minimal battery drain for those wondering.

Here is a link to the app that and those features that I and I'm sure many others would find usfeul on this phone.

Please Login or Register to see this Hidden Content

Thanks.

[Narffran]

Use Smart Screen On from Google Play. You don't even need to touch the device just swipe your hand past the sensor.

Sent from my Nexus 7 using Tapatalk 2

[Hashcode]

Updated the #2 post w/ the first bootlogs of the kernel.

[th3drow]

Really excited for this would be great to have 4.2 up and running with everything working